AI agents for manufacturing & supply chain

Planning, quality, and procurement — with autonomy that stops at the plant floor.

Manufacturing agents plan production, triage quality deviations, and draft purchase orders — while PLC setpoints stay locked, POs over threshold pend for approval, and every quality record seals into an ISO-ready trail.

Aligned with ISO 9001 · IEC 62443 · ISO 27001 · SOC 2

Oversight Modes
risk floorsuggest_onlydraftexecute_low_riskexecute_with_reviewautonomous
oversight ▸ risk gate is a floor — autonomy can only tighten it
The regulatory pressure

An agent that can draft a PO must never be able to touch a PLC.

Manufacturing automation spans two worlds: business systems where speed wins, and operational technology where a wrong write is a safety event. IEC 62443 draws that line for OT; ISO 9001 demands traceable quality records. Cortex keeps agents productive on the business side and physically fenced from the controls side.

ISO 9001IEC 62443ISO 27001SOC 2Export controlsNIST AI RMF
Regulatory pressure
ISO 9001IEC 62443ISO 27001SOC 2Export controlsNIST AI RMF
Typed objectsWorkOrder · BOM · Supplier · Shipment · QualityCheck
Restrictedplc_setpoint / supplier_rate_cardlocked
frameworks ▸ encoded as policy · gated · sealed
Use cases

The whole value chain, with the dangerous parts gated.

The catalog ships 12 manufacturing roles × 18 agent patterns — planners, quality engineers, buyers, logistics — wired to the ERP and MES stack you already run.

Production planning
  • Balances demand, capacity, and materials against typed WorkOrder and BOM objects — schedule changes propose-first, with the planner approving what ships.
  • Action Fabric
Quality triage
  • Classifies deviations, drafts CAPA records, and routes by severity — every disposition sealed into a quality trail an ISO 9001 auditor can walk.
  • Trust Ledger
Procurement
  • Drafts purchase orders and supplier communications — POs execute under your threshold and pend on the approval board above it.
  • Approval gates
Supply-chain visibility
  • Tracks shipments and inventory across systems, reconciles discrepancies, and forecasts under hard budget caps.
  • Cost governance
OT isolation
  • PLC setpoints and controls credentials are locked deny-by-default, and the MCP gateway firewalls every tool call away from the plant network.
  • MCP Gateway
Two worlds, one runtime

Fast on the ERP. Fenced from the PLC.

The same agent that drafts a PO in seconds cannot write a setpoint at all — OT properties are locked deny-by-default and the gateway firewalls the plant network away from every tool call. Business actions carry thresholds and approvals; controls actions simply don't exist for the agent.

  • plc_setpoint and controls credentials locked deny-by-default
  • POs over threshold pend on the approval board with full context
  • Quality records sealed into an ISO-walkable audit trail
  • Forecasting and optimization bounded by hard budget caps
Oversight Modes
risk floorsuggest_onlydraftexecute_low_riskexecute_with_reviewautonomous
oversight ▸ risk gate is a floor — autonomy can only tighten it
Prove it — don't just claim it

The verdicts a plant manager and an auditor will see.

Literal runtime responses — anything near the controls fails closed.

runtime · verdicts
PO $18,000over threshold · pendsHOLD · approval
PLC setpoint writeOT property · deny-by-default403 denied
Forecast overspendprojected > 30-day cap402 budget
CAPA recordclassified · sealed · traceable200 sealed
fail-closed ▸ challenge it and it denies, on the record
  1. 01

    Model the domain

    Map the work to typed ontology objects — WorkOrder, BOM, Supplier, Shipment, QualityCheck — with restricted fields like plc_setpoint / supplier_rate_card locked at the property level.

  2. 02

    Encode the rules

    Translate the obligations above into Policy-as-Code and Action Fabric approvals — the gates fail closed, returning a precise code, not a guess.

  3. 03

    Prove the outcome

    Every run lands in a hash-chained Trust Ledger with signed receipts and 10-hop provenance — a record you can hand the regulator.

100%PO actions recorded — executed, held, or blocked
5 modesAutonomy tuned per agent and action
10-hopProvenance on every quality record
8 gatesOn every run, business or analytical
Security & compliance

Respecting the line IEC 62443 draws between IT and OT.

OT isolation, PO thresholds, quality-trail sealing, and detection & response are shared across planning, quality, and procurement — mapped once to IEC 62443 zones and ISO 9001 records requirements. Aligned with, never claiming a certification you don't hold.

IEC 62443 · zonesISO 9001 · recordsISO 27001 · opsExport controlsSOC 2 · auditNIST AI RMF · Manage
FAQ

AI agents for manufacturing & supply chain — questions, answered.

Can an AI agent write to a PLC or change a machine setpoint?

No. OT properties like plc_setpoint are locked deny-by-default at the ontology level, and the MCP gateway firewalls every tool call away from the plant network — a controls write returns a 403 before any model output matters.

How are purchase orders kept under control?

POs are governed actions with risk tiers: under your threshold they execute and seal; above it they pend on an approval board with supplier, price, and BOM context. Either way the invocation ledger records the outcome.

Does Cortex support ISO 9001 quality records?

Quality dispositions and CAPA records are classified, cited, and sealed into a tamper-evident ledger with 10-hop provenance — a trail an ISO 9001 auditor can walk from record back to source reading.

How is export-controlled or supplier-sensitive data handled?

Sensitive fields — rate cards, controlled technical data — are locked at the property level, DLP screens every tool call in and out, and data-residency controls pin where tenant data lives. Deny is the default; access is the exception you grant.

More industries

One governed runtime, every regulated vertical.

The controls are the same — the obligations they satisfy differ. Explore another vertical, or see the full set.

Speed up the value chain — and never touch the plant floor.

See approval-gated POs, sealed quality trails, and OT isolation working against your own ERP and MES stack.