ISA-95 is a Nice Start - Apriso

More documents

Recommendations

Info

extend integration based on their needs. This need for flexibility is an important factor when utilizing XML to integrate disparate applications and when creating common information formats to share both the format and data on the World Wide Web, intranets and elsewhere. The standard does not focus on the need to rationalize disparate IT systems in the plant; but only on integrating information flows from whatever collection of systems that might exist. As any plant floor manager can attest to, trying to operate in a ‘real-time’ environment when commands and data must be reconciled from multiple, disparate systems is a huge problem. Compound this challenge with operations distributed over multiple locations and time zones, and you can forget about being responsive to shifting market conditions, supplier requirements and customer demands. Low Vendor Participation SAP has been the only enterprise software vendor to actively participate in ISA-95 activities. Despite their involvement, SAP now admits its SOA strategy is not driven by standards, further indicating the shortcomings of just relying on the standard for your application integration architecture and strategy. Next Steps for Manufacturers The ISA-95 standard combined with the functionality available within today’s Manufacturing Operations Management (MOM) software can provide a sound foundation for projects designed to integrate operational data into enterprise information flows. Best in class MOM providers can deliver not only data integration capabilities, but those of global visibility, centralized and local control and the efficient synchronization of material flows across the organization and into the supply chain. In order to achieve success, manufacturers simply need to view the ISA-95 as a starting point, and recognize that each integration Level within the Standard’s hierarchy mapping serves an important function. Select vendor products excel within their respective “Level,” but seldom can one vendor provide a single solution that is capable of delivering best in breed performance across each of the levels. For example, the program design and functional attributes of an ERP system works well for planning purposes, but seldom offers a viable solution for managing shop floor operations, with each of its highly data intensive functions. The following items should be considered when designing plant to enterprise integration, each of which falls beyond the scope of ISA-95. The end result can be a highly efficient, responsive manufacturing operations environment that connects disparate operations, provides real time visibility and control while delivering the necessary agility to respond to the constantly changing market and customer demand conditions. 10 Plant to Enterprise Integration: ISA-95 is a Nice Start
Systems’ Roles Each company may have a different view of which system should own various functions and master data. Some of this will be driven by the capabilities of current systems. For example, some companies want bill of materials (BOM) to reside in the MOM, while others may store it in PLM or ERP. What is critical is to select a MOM and ERP solution that supports the necessary flexibility you require, while being capable of also changing over time, as needed. There is no one right answer, but as a whole, your system design will need to address this vexing issue of achieving a “single version of the truth.” Where Business Logic Resides Many control and automation vendors promote the idea of putting more business logic into the controllers at Level 1 or Level 2. Alternatively, this logic may be programmed within your MOM system in Level 3. ISA-95 has no reference on where the “right” location is, so companies must decide whether they want a decentralized approach, or the easier maintenance of logic in a central application outside of an automation system. A plant where production changes or product re-configurations are infrequent, and when they do occur, the decision is typically best made by the local plant operators, may be best suited by locating their business logic within a PLC or other machine layer user interface. However, if production optimization or continuous improvement initiatives are planned on a multi-plant basis, the implementation of changes within the automation equipment at Layer 1 or 2 could be quite complicated and difficult to achieve across a geographically distributed production environment. For those who have programmed business logic into an OPC or SCADA device, the decision isn’t too difficult. This task must be completed multiple times through a typically difficult interface across the plant floor every time a product change or design update is required. If production is distributed across 15 different plants all over the world and your production floor has multi-vendor automation equipment, this task could take weeks. Alternately, there may be data collection triggers as part of your business logic or quality control program that could easily reside in either your ERP (Level 5) or MOM (Level 3). Manufacturers need to make this decision based on their own architecture, as well as be absolutely sure each selected vendor product can perform its function as part of the solution. Industry-Specific Capabilities This might include Automotive Just-in-Time or sequenced supply chain coordination for suppliers to ship in the right order and sequence to minimize or even eliminate idle inventory. The ISA-95 standards provides no guidance on how to best integrate to supplier systems to accomplish industry-specific objectives, based in part on the fact that the standards were not written for one particular industry. 11 Plant to Enterprise Integration: ISA-95 is a Nice Start
Page 1 and 2: Plant to Enterprise Integration: IS
Page 3 and 4: Executive Summary In a manufacturin
Page 5 and 6: MOM aggregates the vast quantities
Page 7 and 8: What you Need to Know about ISA-95
Page 9: with the use of a bill of materials
Page 13 and 14: Conclusion When addressing the chal
Page 15 and 16: Appendix Apriso and B2MML B2MML sta
Page 17 and 18: Apriso’s Alignment to ISA-95 Qual
Page 19: Apriso’s Alignment to ISA-95 Inve

ISA-95 is a Nice Start - Apriso

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?