Make2Pack-- the 10,000 foot view

Morten Kristensen, NNE US Inc. "I wanted to call this 'Make2Pack for Dummies' but I decided not to imply that you all were."
  • why this presentation?
Make2Pack effort is well known, but the understanding of scope, ideas, benefits seem to be only for the few. This is a high level overview of scope ideas and benefits. We'll only at a high level touch on the technical aspects, and I hope this will provide for better undersnading of the effort, and acceptance of the standard when it is released. 2004: A group was formed to create a standard for recipe interfaces to equipment skids. The focus was changed to collaborate with OMAC who had PackML to create a standard for discrete production eqipment in line with S888. The working name for the standard became Make2Pack. 2005-2005: learning to speak the same languages, and draft a report and the way forwardl 2006: Make2Pack became an official s** part 5 standards committee, and in 2007 a draft standard was issued. Today's automation challenge
  • modular transparent, user driven-not programmer driven- software
  • integration, shop floor to executive floor and process to process has been the order of the day for several years
  • can be done with todays's technology and standards
  • however, in the fill/pack area lack of standardization results in one-offs
Process=Make This is fairly well covered with S88 and S95. but if you look at discrete finished goods production (=Pack), things are very different. The scope of Make2Pack:
  • refine S88 models across all types of manufacturing
  • encourage a layered hierarchical struture that provides modularity and common methods
  • develop a method or approach for the developent of a library of automation components
  • develop physical demo examples
  • refine the definition of modes
  • stay within the framework of S88
  • align with OMAC PackML standard
  • make the standard acceptable to both process/batch professionals and packaging professionals
Common Language:
  • initially a lot of misunderstanidngs betwen process and packaging people
  • after a while the understanding is there among the group
  • key for the standard is to convey this understanding
  • some terms will be new, adaption of the standard will reuire openness to changing terms
  • probably a little heavy on the S88 batch language, but there will be an attempt to conform
This standard is going to be ablout how to structure machine control software, how to interface, and will also apply to process. ISA S-88 adaptation to packaging. It is really clear that the Unit is equivalent to a Machine, a Process Cell is equivalent to a Packing line, an Equipment Module...etc. So it maps quite well to packaging. With a common language that provides for easier communication between end users, engineers, and OEM's in turn, we get a reduction of engineering time and cost, and in turn, reduced time to market Recipe driven software provides a platform for quicker product changeovers, and modularization leads to better software quality. A structured platform for easier integration, easier documentation, and formalized testing-- a key benefit for regulated industries like pharmaceuticals. Lower maintenance cost also comes with the modular software driven approach. Modular programming saves time and money over conventional programming: 4-5 weeks for program development vs. 1.5 weeks, for example. Financial benefits for End Users as well as OEMs in terms of: lower engineering cost reduced testing effort, etc. We still have to get the standard approved, getting wide spread acceptance and understanding and then the OEMs have to adopt it. Stay tuned to!