MES-ERP Cost Data Mapping Specification (OPC UA Ready)

At its core, this specification bridges the semantic and temporal gap between MES—where granular, event-driven production cost data (e.g., actual cycle time per unit, scrap quantity per operation, energy kWh per batch) is captured—and ERP—where aggregated, period-based cost objects (e.g., standard cost rollups, work-in-process valuations, variance analysis) reside. It achieves interoperability by defining OPC UA–compliant Address Space Models (ASMs) that map MES-native identifiers (e.g., ISA-95 OperationSegmentID, S88 BatchID) to ERP cost object hierarchies (e.g., SAP CK11N cost component structure, Oracle EBS Cost Type + Cost Element). Crucially, the specification incorporates time-series context awareness: it requires timestamped, versioned, and unit-normalized data exchange (e.g., converting MES-reported 'machine uptime seconds' into ERP-consumed 'standard labor hours' using configurable efficiency factors), enforced via OPC UA PubSub message schemas with embedded semantic annotations (e.g., using UA Model Design Language (MDL) and companion specifications like PLCopen XML or MTConnect-to-OPC UA mappings). Furthermore, it supports auditability through mandatory provenance metadata: each mapped cost value must carry traceable lineage—including source MES node ID, ERP target ledger account, mapping rule version, and transformation logic digest—encoded as OPC UA Custom Attributes or referenced via external digital twin registries. This enables closed-loop cost modeling: real-time shop-floor variances feed back into ERP standard cost updates, supporting dynamic pricing, profitability analytics by product-family-or-work-center, and regulatory compliance (e.g., FDA 21 CFR Part 11 electronic records validation).