Manufacturing Message Specification

Manufacturing Message Specification
Name	Manufacturing Message Specification
Developer	International Electrotechnical Commission; originally by Rockwell Automation and General Motors
Released	1990s
Latest release	IEC 62453 / IEC 61850-7-4 related updates
Programming language	C, C++, Java (programming language), C# (programming language)
Operating system	Linux, Windows NT, VxWorks
License	vendor-specific, open-source implementations under BSD and GPL

Manufacturing Message Specification is a technical standard defining a protocol and information model for data exchange between manufacturing devices, control systems, and enterprise applications. It provides an abstract object-oriented information model, a mapping to concrete protocols, and conformance classes used by vendors and integrators across industrial automation, process control, and supply-chain systems. The specification influenced interoperability efforts among programmable logic controllers, supervisory control and data acquisition systems, and manufacturing execution systems.

Overview

The specification establishes an information model composed of objects, attributes, services, and reports to represent devices such as Programmable logic controller, Distributed control system, Human–machine interface, and sensors. It specifies client-server interactions, publish-subscribe mechanisms, and a manufacturing-centric view that aligns device-level data with higher-level systems like Manufacturing Execution System and Enterprise resource planning. Conformance classes and profiles enable vendors such as Siemens, Schneider Electric, Rockwell Automation, and ABB to claim interoperability. The model influenced later standards including parts of IEC 61131 and ISA-95 frameworks used by integrators such as Honeywell and Emerson Electric.

History and Development

The standard originated in collaborative initiatives among manufacturers and automation vendors during the late 1980s and 1990s, driven by interoperability needs highlighted by firms like General Motors and consortiums such as the Open Group and ODVA. Early development involved members from International Electrotechnical Commission technical committees and stakeholder organizations including National Institute of Standards and Technology and industry representatives from Ford Motor Company and Procter & Gamble. Successive revisions addressed mappings to field-level protocols and integration with enterprise architectures promoted by World Wide Web Consortium and Object Management Group. Academic contributors from Massachusetts Institute of Technology and Carnegie Mellon University published evaluations comparing the specification to other models like OPC and Modbus in the 2000s.

Architecture and Protocols

The architecture defines an abstract object model with classes for logical devices, variables, and event reporting, and standard services for configuration, monitoring, and control. It specifies protocol mappings for connection-oriented and connectionless transports; implementers adopted mappings over TCP/IP, UDP, and serial links used in installations by General Electric and Mitsubishi Electric. Bindings and encodings reference technologies standardized by ISO/IEC and influenced by ASN.1 and XML Schema approaches used in W3C specifications. Conformance profiles categorize functionality into client, server, and translator roles enabling gateways between fieldbuses like Profibus, DeviceNet, and enterprise networks operated by Siemens and ABB.

Implementations and Tooling

Commercial and open-source stacks implement the model in languages such as Java (programming language), C++, and C# (programming language). Vendors including Rockwell Automation, Siemens, Schneider Electric, and ABB provide firmware and gateway appliances that map to popular field protocols from Yokogawa and Emerson Electric. Open-source projects hosted by communities around SourceForge and GitHub offer SDKs, test suites, and simulation tools used by research groups at ETH Zurich and Delft University of Technology. Conformance testing frameworks were developed in collaboration with laboratories such as Fraunhofer Society and TÜV Rheinland, and certification programs tied to trade associations like OPC Foundation and regional standards bodies.

Use Cases and Industry Adoption

Adoption spans discrete and process industries: automotive assembly lines at firms including Toyota, pharmaceutical manufacturing at Pfizer, and food-and-beverage plants operated by Nestlé. Use cases include telemetry aggregation from Programmable logic controller networks, batch management integration with Manufacturing Execution System deployments, and raw-material traceability aligning with regulations enforced by agencies such as U.S. Food and Drug Administration and European Medicines Agency. Integrators leverage translator gateways to bridge legacy fieldbuses from Rockwell Automation to ISA-95 aligned enterprise systems used by SAP SE and Oracle Corporation. Several utilities and infrastructure projects coordinated by organizations like Siemens and ABB used the specification alongside IEC 61850 for substation automation pilot projects.

Security and Interoperability Considerations

Security considerations focus on authentication, authorization, and secure transport layers; deployments often combine the specification with TLS or proprietary VPN solutions offered by vendors such as Cisco Systems and Juniper Networks. Interoperability challenges arise from optional features and vendor-specific extensions; industry consortia like ISA and IEC working groups recommend profiles and conformance testing to reduce integration risk. Cybersecurity incidents in industrial control systems involving Stuxnet and BlackEnergy highlighted the need for defense-in-depth, intrusion detection provided by firms like Dragos (company) and FireEye, and compliance with standards published by NIST and ENISA.

Category:Industrial automation standards