Industry Vocabulary Reference

Manufacturing, Supply Chain & Logistics

Manufacturing, supply chain, and logistics fields cover production orders, equipment, quality, shipment events, and maintenance. The vocabulary records context for policy evaluation and review.

Back to industry coverage library

This page shows selected examples and categories. Download the JSON for the complete vocabulary, including every field, permitted value, and policy pattern in this catalog.

How to use this reference

1. Start with the core file if you need the cross-industry governance baseline.
2. Choose an industry file for its workflow fields and permitted values.
3. Match the OTel attributes to the policy paths your rules use, then verify the recorded fields in a test session.

Catalog context

Trace a production or logistics workflow from its input through the resulting action. Include equipment or shipment identifiers only where they are needed and authorized.

Risk note: Telemetry is not a machine-safety control. Keep safety interlocks, operational authorization, and applicable product requirements separate from evidence collection.

Vocabulary file

• Download filename: 06_vertical_manufacturing_supply_chain_logistics.json
• Kind: vertical

OTel namespaces

Referenced standards

These references explain the catalog's context. A listed standard does not establish that a configured application meets its requirements.

• ISA-95 Part 1–6, Enterprise/Control System Integration (ANSI/ISA-95)
• ISA-95 Part 4, Objects and Attributes for Manufacturing Operations Management, ISA95JobOrderStateEnum (OPC Foundation reference implementation v1.0.0)
• ISA-88, Batch Control (ANSI/ISA-88), Equipment Procedural Elements and procedural state machine
• OPC UA Part 1–14, Unified Architecture (IEC 62541); OPC UA for ISA-95 companion spec
• IEC 62443-1-1 through 4-2, Industrial Automation and Control Systems (IACS) Cybersecurity
• IEC 62443-3-3, System Security Requirements and Security Levels (SL1–SL4)
• ISO 10218-1:2011 / ISO 10218-2:2011, Robots and robotic devices, Safety requirements
• ISO/TS 15066:2016, Robots and robotic devices, Collaborative robots (cobot safety)
• ISO 22400-1:2014 / ISO 22400-2:2014, Automation systems and integration, KPIs for MOM
• ISO 9001:2015, Quality Management Systems
• AS9100 Rev D, Quality Management Systems for Aviation, Space, and Defense
• IATF 16949:2016, Quality Management System for automotive production
• GS1 General Specifications v23, Barcodes, RFID, and data standards
• GS1 EPCIS 2.0 (CBV 2.0), Electronic Product Code Information Services
• GS1 EDI BMS eCom, Transport Status Condition codes
• UN/CEFACT CCTS, Core Components Technical Specification for trade documents
• WCO Harmonized System (HS) 2022, Tariff nomenclature
• EU Machinery Regulation (EU) 2023/1230, Replaces Machinery Directive 2006/42/EC (applicable from Jan 20 2027)
• EU AI Act (2024/1689) Annex I & III, AI systems in safety components of machinery
• EU Product Liability Directive (2024/2853), Revised liability for AI-integrated products (in force Dec 2024)
• EU CSRD (2022/2464), Corporate Sustainability Reporting Directive, supply chain due diligence
• EU Supply Chain Due Diligence Regulation (CSDDD) (2024/1760), in force Jul 2024, transposition by Jul 2027
• US CHIPS and Science Act (2022), Supply chain resilience reporting requirements
• US Uyghur Forced Labor Prevention Act (UFLPA 2021), Supply chain provenance traceability
• FDA 21 CFR Part 820, Quality System Regulation (medical devices); harmonised with ISO 13485:2016
• REACH Regulation (EC) No 1907/2006, Registration, Evaluation, Authorisation of Chemicals
• RoHS Directive 2011/65/EU, Restriction of Hazardous Substances in electrical/electronic equipment

Source references

• https://reference.opcfoundation.org/ISA95JOBCONTROL/v100/docs/6 
• https://www.iec.ch/homepage 
• https://www.gs1.org/standards/epcis 
• https://navigator.gs1.org/ 
• https://www.iso.org/standard/62091.html 
• https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32023R1230 
• https://www.dhs.gov/uflpa 
• https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/CFRSearch.cfm?CFRPart=820 

Subdomains

Implementation examples

• Manufacturing Operations Management (ISA-95 MOM): Job Order State. AI production scheduling agent creates job orders and advances state through the lifecycle. 'Aborted' state triggers automatic root cause analysis and material reconciliation workflow. 'Held' state triggers QA agent investigation before resumption is permitted. (Eu Machinery Reg 2023 1230: Job order state transitions driven by AI scheduling agents are in scope of EU Machinery Regulation (2023/1230) Article 9 if the AI system influences safety-critical work centre operations)
• Manufacturing Operations Management (ISA-95 MOM): ISA88 Batch Procedural Element State. Batch AI agent transitions a pharmaceutical batch procedure through ISA-88 states. 'Held' state is used for planned interruptions (e.g. IPC sampling); 'Aborted' state triggers FDA-required batch failure investigation and deviation report generation.
• Manufacturing Operations Management (ISA-95 MOM): Equipment Use State. AI OEE agent tracks equipment use state transitions to calculate availability. Autonomous work order generation triggers when predicted time-to-failure falls below threshold for critical equipment. (Iso 22400: ISO 22400-2, OEE availability calculation uses production, setup, maintenance, and down states)
• Manufacturing Operations Management (ISA-95 MOM): OEEPerformance Factor. AI OEE agent tags each autonomous improvement action with the targeted OEE factor. Vision inspection AI reducing defect rate tags actions as 'quality'. Predictive maintenance agent reducing unplanned downtime tags actions as 'availability'.

Control ideas

These patterns describe possible controls, not active rules. Confirm applicability, implement the control, and test its effect on the application.

Enforce before the action

Pass the request and your business action to this function. The core SDK checks policy before the action runs and again before its result is released. A deny or review decision means the action never runs.

import { Veriproof } from '@veriproof/sdk-core';
import type { GovernedResult, IndustryFact, JsonValue } from '@veriproof/sdk-core';

const veriproof = Veriproof.fromEnv();

export async function runProtectedAction<TInput extends JsonValue, TValue>(
  request: TInput,
  action: (input: TInput, signal: AbortSignal) => Promise<TValue>,
): Promise<GovernedResult<TValue, TInput>> {
  // Catalog values for this vertical. Replace them with facts from the current workflow.
  const industry: IndustryFact[] = [
    { attribute: "manufacturing.job_order.state", policyInput: "manufacturing_job_order_state", value: "waiting" },
    { attribute: "manufacturing.batch.procedural_element_state", policyInput: "manufacturing_batch_procedural_element_state", value: "idle" },
    { attribute: "manufacturing.equipment.use_state", policyInput: "manufacturing_equipment_use_state", value: "production" },
  ];

  // Policy runs before action() and again before the result is released.
  // A deny or review decision means action() never runs.
  return veriproof.govern(
    "manufacturing.supply.chain.logistics.evaluate",
    request,
    ({ input, signal }) => action(input, signal),
    { industry },
  );
}

• Replace the sample values with facts from the current workflow. Rules read them under input.snapshot.industry.
• Test both permitted and blocked actions. Confirm that a blocked action never reaches your business function.
• Only completed, completed_with_warning, and transformed results carry a released value.

For review decisions, follow the Human Review guide to configure continuation. Observe remains available when you need to record activity without enforcing a decision.

Set up the Manufacturing, Supply Chain & Logistics example. See the API reference for TypeScript, Python, or .NET.

Selected vocabulary categories

This page uses the vocabulary JSON distributed with the documentation. Check its version when comparing it with an installed SDK.

Download the vocabulary JSON for offline review or automated comparisons.

Use the SDK reference for configuration and supported APIs. Keep vocabulary selection separate from the compliance team's assessment of applicable requirements.