What exactly is the Automation Object that Make2Pack is trying to describe?

Three possible components make up a Make2Pack (M2P) Automation Object.

03/05/2010


There are three possible components that make up a Make2Pack (M2P) Automation Object. The Functional Strategy is always present while the Function and Recourse Managers are optional. If there are optional parts one might ask why have them at all as it may appear to add unnecessary complexity. This is a valid question and one that must be answered in such a way as to make their value unquestionable.

If you look at the current state of automobiles and consider that the windshield at one time did not exist as part of early automobiles, goggles worked just fine, thank you, and why have all the hassle of that extra weight and cleaning all that glass? Who now wants to revert to the goggles? I’m sure we can find some must the majority really wouldn’t like to deal with the “bugs in the teeth” issue.

Over the next few postings I hope to discuss this and other aspects of the Make2Pack work and how it relates to the ISA88 Part 5 draft underway.

Also read:

- Interdependence within ISA88; automation object and state diagram updates;
- ISA88 Part 5, draft 5: Resource manager allows one control to own another.

Please comment below and scroll through prior postings. Thanks.

Posted by David Chappell on March 5, 2010



No comments