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.
Make2Pack, ISA88 Part 5: Command (Requests) and Control
March 17, 2010
I really think that the Make2Pack effort is focused on how to interact with automation objects by knowing what commands are permitted and how to deliver those commands and how to “read” the status(es) provided by the automation objects independent of what control platform the objects exist within.
I have to ask “is it a Command or is it a Request”? In the end the automation object will have to evaluate the command and determine if it is valid, and from an authorized source. Based upon that determination the automation object will accept or reject, the request.
Providing a consistent method of interpreting the status of the all the “important” or “pertinent” statuses of the automation object are also a requirement that must be know and independent of the4 control platform.
Control is another topic that I know we will spend considerable time on. I really believe that we will find that this is primarily a core part of the Functional strategy and will not require a lot of effort on the part of Make2Pack.
Control in my thinking consists of the traditional interlocks and permissives (yet to be defined… I know) and parameters that are required to any and all Automation Objects.
Please comment on this or previous blogs. It helps with discussions and ISA88 Part 5 revisions. Thanks.
Posted by David Chappell on March 17, 2010