Make2Pack, ISA88 Part 5: Command (Requests) and Control
How to interact with automation objects: Is it a command or request?
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
- Events & Awards
- Magazine Archives
- Digital Reports
- Global SI Database
- Oil & Gas Engineering
- Survey Prize Winners