Standard Profits: Make2Pack and ISA88
David Chappell is chair of the Make2Pack/ISA88 Part 5 standards development effort, with Complete Manufacturing Automation Associates - LLC, and retired Proctor & Gamble section manager for batch technologies. Help ISA88 committee members increase dialog about, completion of, interest in, and use of Make2Pack. Join in with your comments or questions to help the standard along, on your way to gaining competitive advantage, reducing overall costs by half. David A. Chappell, Make2Pack chair, and other ISA88 Part 5 committee members provide intelligence and specific links for this effort, spanning OMAC, WBF, and ISA standards efforts.
NOTE: ISA grants permission to post portions of the ISA88 (or other applicable standards) in this blog for comments and discussions and postings (or comments) from this blog may be used for ISA and related standards development.
Comment on ISA88 Part 5 Draft definitions: Automation object, AO functional manager, device, others
October 25, 2010
Make2Pack ISA88 Part 5 conference call included discussion of definitions, perhaps particularly timely since the Pack Expo 2010 (www.packexpo.com) conference is so near. We’ve had a number of discussions as this draft has progressed about terminology, especially since that the terms people use from processing and packaging automation can differ.
Do these definitions work for you? (That’s the purpose of a standard, after all, to derive agreed upon language and framework that makes it easier to work with and integrate automation.)
Please comment, whether you agree or would revise: Would those people in your facility involved with automation and controls agree with them? Would you want to email them this link so they could comment, after you do? Look at the definitions below and post a comment (comments are reviewed weekly then made live) or email me directly using my contact info below. When commenting, it’s most helpful to provide a rewrite of how you think it should be, then explain why. A word about your background and what you do, would be helpful to provide context. Thanks!
For the purposes of this part of this draft, the following definitions apply. Definitions and concepts expressed in the Part 1 standard apply, except where differences are explicitly stated in this part.
3.1 Automation Object (AO)
– The grouping of engineered control components that will carry out the requirements of a module. This must consist of a functional strategy component and may consist of a function manager and a resource manager. An automation object provides public methods to interact with the functional strategy.
3.2 Automation Object Command Processor
– the functionality that will receive commands from a public source and evaluate them to determine what actions to take. Appropriate commands will be passed to the active functional strategy in whatever form the functional strategy requires. The command processor provides public status results of any requested activity.
3.3 Automation Object Function Manager
– if the AO functional strategy supports command and control capabilities in a public method the AO function manager provides the public interface and methods to process commands and manage control that is applied to the functional strategy.
3.4 Automation Object Functional Strategy
– The part of an AO that contains the module specific functionally engineered using vendor supplied tools and components native to a control environment to carry out the control required by an operating scheme. This AO component must as a minimum provide predefined information in a public way.
3.5 Automation Object Resource Manager
– if the AO has multiple functional strategies and/or supports multiple users/owners the AO resource manager will provide a public method to manage the other components of the AO to see the required functional strategy is active and the commands and control are accepted only from approved sources.
– A Device is a piece of physical equipment and has no control associated with it. Part 1 refers to this as a Control Module. When control is associated with a device it becomes a Control Module Entity.
Example – the valve body, actuator and limit switch are devices that when paired with the functional strategy of a control module form an on/off block valve.
Example – (pending, from Pierre)
3.7 Functional Strategy (FS)
– The actions required to carry out the control described by an operating scheme for any equipment or control module.
3.8 Mode of Action
– a functional strategy may support the part 1 defined modes of control, automatic, semi-automatic, manual. Other modes may also be supported, for example simulation. The mode of action is used to define the behavior of the functional strategy.
3.9 Mode of Control
– where an AO has more than one functional strategy and/or more than one source of command and control the mode of control will define the behavior of the entire automation object as to who or what can issue commands and which functional strategy will react to those commands.
David A. Chappell, Complete Manufacturing Automation associates - LLC
Not seeing the comments box? Click here to comment on ISA88 Part 5 definitions, and scroll to the bottom of the page.
Wednesday, 10-11-10 09:52
James, thanks for the observations! I'll take these back to the working group at our next meeting and let you know the results.
Saturday, 30-10-10 08:26
3.1 uses the undefined terms "module", "control components", and "public methods". These terms are not defined in S88.1 either. It is not clear from this definition whether these terms refer to physical, hardware, or software entities.
- In general, requirements should not be embedded in definitions. For instance, the requirement that an AO provide public methods to interact with the functional strategy is embedded in 3.1, the requirement that an AO FS provide public status results of any requested activity is embedded in 3.2, 3.3 is a pure requirement without definition, etc. Definitions should tell us what a thing is, not what it is required to do; normative requirements should be defined in other clauses. See ISO/IEC Directives, Part 2 (http://www.iec.ch/tiss/iec/Directives-Part2-Ed5.pdf), Annex D, in particular D.1.5, for detailed guidance.