ISA-95 / IEC 62264 Compliance Traceability¶

Overview¶

ISA-95 (IEC 62264) defines the interface between enterprise (Level 4), MES (Level 3), and control (Level 2) systems. Cloud-Native DCS implements the Level 2/3 boundary via the MES integration API (/api/v1/mes/).

Scope note: the rows below mostly read "Implemented", while the compliance index rates ISA-95 coverage "Low / Partial", and both are true. The rows track the narrow Level 2/3 exchange slice this product ships. The index rates breadth against the full ISA-95 standard (Parts 1–5), most of which is MES/ERP territory and out of scope for a DCS.

Standard: ANSI/ISA-95.00.01 through 95.00.05 (IEC 62264) Status: Phase 1 (REST API + API key auth + B2MML format)

Information Exchange Categories¶

ISA-95 defines four categories of information exchanged at the Level 3/4 boundary.

Category 1: Product Definition¶

ISA-95 Requirement	Implementation	Status
Product definition exchange	`GET /api/v1/mes/sites/{site}/product-definitions`	Implemented
Recipe-to-product mapping	MasterRecipe → ProductDefinitionDTO	Implemented
Bill of materials	Recipe formula materials → BOM items	Implemented
Process segments	Recipe procedure steps → process segments	Implemented
B2MML ProductDefinition	`?format=b2mml` content negotiation	Implemented
Lifecycle filtering	Only Effective recipes exposed to MES	Implemented

Category 2: Production Capability¶

ISA-95 Requirement	Implementation	Status
Equipment status reporting	`GET /api/v1/mes/sites/{site}/production-capability`	Implemented
Equipment availability	Derived from ISA-88 state machine states	Implemented
Capability declaration	Unit capabilities (from EquipmentCapability)	Implemented
Single equipment query	`GET /api/v1/mes/sites/{site}/equipment/{name}/status`	Implemented
B2MML ProductionCapability	`?format=b2mml` content negotiation	Implemented
Personnel capability	Not applicable (ISA-88 scope)	N/A

Category 3: Production Schedule¶

ISA-95 Requirement	Implementation	Status
Work order submission	`POST /api/v1/mes/sites/{site}/work-orders`	Implemented
Immediate dispatch	`?dispatch=immediate` → Batch CR, `Pending` until an operator issues Start	Implemented
Deferred dispatch mode	Not offered. `dispatch=immediate` is required, and any other value is refused with `400`	N/A
Work order identity	`workOrderID` → `Batch.spec.batchID`, unique within the site and enforced at admission; a resubmission returns the existing order with `200`, or `409` when its body differs (ADR 0051)	Implemented
Requested start time	`WorkOrderRequest.scheduledStartTime` → `Batch.spec.scheduledStartTime`, reported back and exported as the B2MML `ProductionRequest` `StartTime`. It is the plan and starts nothing: the batch waits for an operator Start whatever it says (ADR 0052)	Implemented
Work order listing	`GET /api/v1/mes/sites/{site}/work-orders`	Implemented
Work order status	`GET /api/v1/mes/sites/{site}/work-orders/{id}`	Implemented
Work order cancellation	`DELETE /api/v1/mes/sites/{site}/work-orders/{id}`, refused once the batch has begun executing	Implemented
B2MML ProductionSchedule	`?format=b2mml` content negotiation	Implemented
Parameter overrides	WorkOrderRequest.parameters → BatchParameterOverride	Implemented
Equipment requests	WorkOrderRequest.requestedEquipment → RequestedUnits	Implemented

Category 4: Production Performance¶

ISA-95 Requirement	Implementation	Status
Batch summary reporting	`GET /api/v1/mes/sites/{site}/production-performance`	Implemented
Full production record	`GET /api/v1/mes/sites/{site}/production-performance/{batchID}`	Implemented
Material consumption	MaterialTrace CRDs → materialInputs/materialOutputs	Implemented
Process parameters	BatchParameterOverride → parameter values	Implemented
Batch events	Batch.Status.Events → event timeline	Implemented
Audit trail	AuditRecord CRDs → correlated audit entries	Implemented
Historian data	Historian service → tag values, alarms, states	Implemented
B2MML ProductionPerformance	`?format=b2mml` content negotiation	Implemented
Electronic signature	BatchRecord finalization + e-signature	Implemented

Authentication¶

ISA-95 Requirement	Implementation	Status
Machine-to-machine auth	API key authentication (`Authorization: ApiKey <key>`)	Implemented
Key management	`POST/GET/DELETE /api/v1/mes/apikeys` (admin-only)	Implemented
Key scoping	Per-site scope restriction	Implemented
Secure key storage	SHA-256 hashed in K8s Secrets	Implemented
Human operator auth	OIDC Bearer tokens (unchanged)	Implemented

Data Format¶

ISA-95 Requirement	Implementation	Status
B2MML XML (ISA-95.05)	`?format=b2mml` or `Accept: application/xml`	Implemented (subset)
JSON REST API	Default format for all endpoints	Implemented
BatchML XML (ISA-88.04)	Existing `/api/v1/sites/{site}/batches/{name}/record?format=xml`	Implemented

Future Phases¶

Feature	ISA-95 Requirement	Status
Webhook event push	Production event notification	Planned (Phase 2)
MQTT bridge	Async message queue integration	Planned (Phase 3)
File-based exchange	B2MML XML drop folder for legacy MES	Planned (Phase 4)
Personnel model	Operator qualifications and availability	Not planned

Physical Hierarchy Alignment¶

Per ISA-TR-88.95.01 (ISA-88/ISA-95 alignment technical report):

ISA-88 Level	ISA-95 Level	DCS CRD
Enterprise	Enterprise	Enterprise (cluster-scoped)
Site	Site	Site (cluster-scoped)
Area	Area	Area
Process Cell	Work Center (batch)	ProcessCell
Unit	Work Unit (batch)	Unit
Control Module	Below ISA-95 scope	ControlModule