Are Your MES/MOM Skills Recognized?

Plant floor systems used to be simpler things: relay-driven machine logic, counters and gages that human operators could read and record values on their clipboards, control panels with numerous indicator lights showing what was happening at any given time.  But automation has evolved from those roots: industrial controllers have replaced relays, graphical HMIs with touch screens have replaced the lighted panels, and networks now exchange information between production equipment and enterprise systems – eliminating the need for a human with a clipboard, but also enabling new capabilities throughout the entire value chain.  This evolution has led to the development of a new body of knowledge, often referred to as Manufacturing Operations Management, or MOM. Many of today's industry initiatives – such as "smart manufacturing", "digital thread", "real-time enterprise", "connected enterprise", and "Industrie 4.0" – are deeply rooted in MOM.

What does this mean for leaders in the manufacturing space? In the current environment, executives need to ensure that both their internal people and external consultants are familiar with this evolving body of knowledge.  Just as with certifications such as Project Management Professional or Certified Business Analyst, hiring managers should be able to request candidates that are recognized by a professional body with extensive understanding of manufacturing operations management. Until recently, there haven't been good options available for identifying individuals with a solid understanding of MOM.  But on May 6^th 2015, MESA International announced a practitioner recognition program to do just that. MESA-recognized practitioners are members of the MESA organization who have not only completed an intensive MOM training program but who also regularly contribute to the ongoing growth of the body of knowledge through participation in MESA's committees and working groups.

So what are some of the things a MESA-recognized practitioner knows? Here's just a partial list:

• Manufacturing operations standards and relationships to strategic initiatives
• Adaptive manufacturing architecture
• The relationship of MES/MOM to continuous improvement and supply chain initiatives
• Transformation strategy including maturity and road mapping models
• MES/MOM implementation and governance
• Metrics frameworks
• MES/MOM justification
• MES/MOM project management techniques

Note these knowledge areas are different from what a typical controls engineer faces daily, but a MOM practitioner must have a working comprehension of the controls environment, continuous improvement practices, business processes (particularly in the areas of quality, safety, and maintenance) as well as an understanding of the IT landscape.

For a consultant (like myself), being a MESA-recognized practitioner will provide additional credibility beyond personal experience.  A MESA recognition carries a lot of weight; for those unfamiliar, MESA International is an association of manufacturing companies, solution providers, integrators, and consultants focused on delivering business results from manufacturing information technology. MESA is a recognized authority in this field; its white papers and other publications are frequently cited in trade publications, by industry analysts, and by a variety of consulting organizations. Their MES/MOM training is a comprehensive overview of the existing body of knowledge, and their committees and working groups are involved in the development and expansion of this knowledge.

The MESA-recognized practitioner program will establish an industry baseline for excellence in manufacturing operations management systems.  It will not only ensure that practitioners have been tested in the MES/MOM body of knowledge, but that they are also actively participating in the growth of that body. And that, in the long run, will be a very good thing for the industry.

An IIoT Nucleus - The Industrial Internet Reference Architecture

I just finished reading the Industrial Internet Consortium's (IIC) "Industrial Internet Reference Architecture" (or IIRA) document – all 101 pages – and it was much more than I expected. For those interested, IIC is a collaboration of solution providers, academics, and governments focused on meeting the needs of the industrial internet marketplace, particularly as related to the interoperability of components which make up current and future industrial internet systems. IIC is managed by the Object Management Group (OMG).

What is the IIRA?

When I first opened the IIRA document, I was anticipating something akin to the ISA99 reference model or Rockwell's "Reference Architectures for Manufacturing" – something that a manufacturer could customize and implement within their own enterprise. Instead, the IIC has put together an architecture targeting the entire industrial internet of things (IIoT) marketplace – both manufacturers and solution providers. This document establishes a common language and framework which – in their words – "transcend(s) today's available technologies" to create a shared understanding of how future technologies can interact with the industrial infrastructure. Instead of a Purdue-type model, think conventions, principles and practices for establishing an IIoT framework. Note that you will find models similar to Purdue and a tiered infrastructure within the reference architecture, so mapping between the existing body of knowledge (such as provided by MESA International's Global Education Program) and the IIRA will not be difficult.

The IIRA is multi-dimensional; it considers the architecture from four different points of view (business, usage, functional, and implementation) across a variety of concerns, including security, business context, automation/control, operations, and information management.

The document itself is clearly the work of many hands. The discussion of industrial internet system resilience has a distinct military influence, while the system composition discussion is definitely academic in nature. There are sections within the document regarding information security that bear the DNA of major players in the networking and IT industry, and discussions on control which come from companies with real-time automation experience. (It's geeky - I know - but I had fun guessing who wrote what.)

Why is the IIRA important?

The IIRA is not a specification, nor does it contain a list of applicable standards. Instead, it provides guidance for those designing solutions and establishing standards for the connected enterprise. Most importantly, it provides a common set of principles around which standards, requirements, specifications, and designs may be formed. Given the nature of the multi-vendor components which typically comprise a plant floor system, it's important to move beyond the discussion of physical characteristics (i.e. "Is it DIN-mountable?", "Does it have a RJ45 connection?", etc.) to the cyber characteristics ("Is the communication secure?", "Does it support Publish-Subscribe?", "Where does it reside in a 3-tier architecture?", etc.)  Pre-IIRA, implementers would be responsible for making components from multiple providers – if they needed to collaborate – work together through custom integration. IIRA creates an expectation that custom integration can be minimized or even eliminated by defining integrability, interoperability, and composability. 

Who should read it?

The Industrial Internet Reference Architecture is not something you're going to be able to digest in 10 to 15 minutes – it takes a fair commitment of time to read and comprehend (note to IIC – an executive overview PowerPoint might be in order). IIC's target audience includes component providers, system providers, and system implementers. I think the list should probably be a little broader, so here are my thoughts:

IIoT device OEMs: New devices, from industrial controllers to sensors to servo motors and everything in-between will be expected to collaborate with the larger industrial internet (or intranet for those excessively risk-averse) system.

Industrial Controls Providers: IIRA anticipates a transition from insular controls which currently dominate the market in discrete manufacturing to high-speed distributed controls.  This may indicate the need to enhance IEC 61131 or perhaps add IEC 61499 capabilities to existing automation controllers.

System Integrators: While the Purdue model is still valid, IIRA extends it and adds new perspectives – particularly in the area of security where the document stresses the need to include security by design instead of an afterthought.

Manufacturing System Consultants: Consultants need to be able to help guide manufacturers into this new industrial revolution and make the connections between the business perspectives and operations perspectives.

Control Engineers/Manufacturing Engineering Managers: Company executives are going to expect their engineering groups to be up-to-speed on the changing technology, and to interact with the marketplace to implement effective solutions.

IT analysts and managers: The convergence of information technology and operations technology that must take place for effect Industrial Internet Systems will require collaboration between the controls engineer on the plant floor and IT personnel. A shared understanding of the IIRA will help facilitate that collaboration.

Conclusion

The IIRA is – in my opinion – a much-needed addition to the overall body of knowledge in manufacturing operations management.  It will be a great help as principles and practices are developed around smart manufacturing concepts. I do hope though that there is enough interaction between groups such as MESA, SMLC, OMG/IIC, ISA, ISO and others to ensure a long-term consistent perspective is maintained.