You are on page 1of 2

OMAC MOTION FOR PACKAGING GROUP Connectivity and Architecture Subteam PackML V3 - Packaging Machinery Language group CHARTER

Mission: The broad mission of PackML is to develop common machine operational guidelines, control software design structure (e.g. state machine), and naming conventions for communications between production machinery.
User Benefits: Consistent operational state and modes Enable faster root cause analysis Uniform machine control, look and feel. OEM Benefits: Faster development time Greater reuse of programming Shorter debug time Control Provider Benefits Less training Uniform libraries More opportunity / less dependence on User standards Performance / capability based decision making Tags that provide flexible machine measurements (OEE) Provides for quicker machine integration Less downtime Reduces cost of ownership Reduces need for supervisory systems Allows machines to be redeployed Easier validation Less operation and maintenance training Greater flexibility & scalability Less training Easier sales support Consistent end user specs IP differentiation Robust programming

Objectives: The objective of PackML version 3.0 is to update the existing guidelines to include: Addition modes of operation (e.g. semi-automatic, manual) o Address special situations (e.g. washouts, threading, ) o Address the modifications with PackTags Clarify critical nomenclature and definitions, such as modes and states. Backward compatibility with past PackML guidelines 1. Harmonization with other software methodology efforts such as the Weinstephan State Model, Make2Pack,S88 & S95 and others Through this work End-Users, OEMs, and technology providers will gain 1. Templates that promote common programming methods and terminology. 2. Common operator visualization template to promote commonly used operating methods. 3. Common template of naming conventions for tags that can be used for control and information systems across the plant floor. Background: Commonality in the way machines talk is identified as being key to increased productivity across the plant floor, OEM shop, and in control vendor equipment. One problem in the packaging industry is that there are no agreed-upon, global specifications or standards. The lack of commonality can be illustrated with respect to a packaging machine language, by stating, If a machine state is on, is that the same as running? A machine could be on, but not stopped. There is a need to speak the same language at the most fundamental level before we can solve industry-wide connectivity issues. The PackML (Packaging Machinery Language) team was formed in February of 2001 to meet this challenge. This initiative

promotes improved horizontal integration (ie. machine-to-machine, machine system-to-process) and vertical integration (machine & machine systems to-plant/enterprise information systems.. PackML has evolved into an operational and software architecture guideline that explains the functional terminology of a machine, which is generally described in terms of modes and states. It harmonizes some of S-88 into discrete machines, and gives Make2Pack a software foundation under which to build. PackML also provides a communication guideline in PackTags for consistent naming conventions to measure OEE and for plant ERP systems. PackML has been deployed by a number of end-users and OEMs. Some of the feedback from their work is PackML has a number of gaps which needs to be addressed which drove the need for a version 3. It is desired by those who have deployed PackML v1 and v2 that v3 has backward compatibility. Strategy: 1 2. Collect feedback from existing PackML users and technology providers Understand (ie naming conventions, state procedures as distributed layers of automation below PackML, etc) and harmonize with other software methodology efforts a. Build relationship with the Weinstephan group b. Communicate with the Make2Pack team c. Gain insight from technology providers who have already develop PackML templates 3. Harmonize with the others teams in the OPW which are coordinating various other aspects of packaging guidelines. 4. Drive consistent definitions of data elements. Examples are total run time, total productive time, total downtime, wastage, efficiency, etc. 5. Develop consistent methods for reporting mode and state conditions. 6. Develop a common set of well-defined naming conventions that OMAC can recommend as guidelines based on past work and new naming conventions. 7. Identify the steps required to make PackML an ISA and IEC standard. 8. Develop templates of examples for OEMs and end users 9. Leverage exposure of PackML at PackExpo and other venues 10. Define typical states, and correlate to PackTags for reporting 11. Build PackTag scheme to follow mode definitions 12. Describe Mode Manager functionality Initial PackML Requirements: Line type definitions (Complete) o A clear definition of the line types in common use defining a complete set from the standalone unit to the fully integrated and automated system unit. Machine state names and definitions o These will define the machine states that will be represented within machinery for communication with host and peer systems providing state logic. Examples are stopped, running, paused, etc. Tag names and definitions/data sets. o These will include the fundamental names of the data elements (or tags) as well as the data types, values, ranges and where necessary data structures. Machine Mode names and definitions o These will define the machine mode that will be represented within machinery for communication with host and peer systems providing state logic. Examples are stopped, running, paused, etc. Other machinery o Visualization (data mapping) Higher level information and control systems o Parameter downloading o SCADA