When manufacturers began integrating their islands of automation in the 1980s, the technology was brand-new so they didn’t have to worry about functionality overlap between new and existing systems. But today’s manufacturers do. For that reason, the model we used for moving from paper tags to computerized manufacturing intelligence systems won’t work for advancing today’s complex manufacturing systems.
A New Approach
We need a new paradigm for continuing to improve our capabilities in integrating and leveraging manufacturing data. It just doesn’t make sense to implement a comprehensive suite that significantly overlaps the functionality of an existing systems environment. Such an approach requires replacing existing functionality with similar functionality.
Instead, we need targeted apps that fill in missing functionality without replacing or duplicating existing functionality — much like smartphone apps. Such an approach to advancement may prove essential to maximizing ROI. That’s because many manufacturers have invested in intelligent assets and systems that offer up to a 30-year lifespan. Replacing these investments with new ones would not provide a viable financial return, but enhancing them would result in an attractive ROI.
Integration Through Enterprise Batch Records
There are several ways to take a component approach to advancing the connected enterprise. However, you should utilize the ISA 88 and 95 architecture guidelines for decisions on splitting functionality between information system components in a way that enables continued enhancements over time. In doing so I suggest that you enable data integration through a common architecture that uses a common data structure, rather than through a proprietary suite of products. For batch based manufacturers the most logical way to advance the connected enterprise is to use the batch record as the basis for all integration.
To be clear, I don’t mean just electronic batch records, which refer only to the information associated with the basic batching steps. I’m suggesting that we think about batch records from the overall enterprise perspective and use batch identity as the key for collecting and integrating all the information associated with a batch — including raw materials consumed, employees involved in production, production order and delivery. I refer to this approach as enterprise batch record (EBR), and I believe it’s the key to advancement.
I challenge today’s MES and MOM software suppliers to consider developing EBR-based solutions with independent apps — or other similar solutions — to help manufacturers advance their connected enterprise with high ROI.