ISA88 Part 5: State Diagram as an example rather than a normative requirement
As the ISA88 Part 1 work approaches completion it appears that the new procedural state diagram (see the example) will become an example and not a requirement.
As the ISA88 Part 1 work approaches completion it appears that the new procedural state diagram (see the example below that Make2Pack had been working with) will become an example and not a requirement.
As the Make2Pack work evolves I don’t think this will be an issue. I think that our contribution will be how to interact with ANY component.
This involves the command and status interaction and not necessarily the control components that drive the Functional Strategy.
Please add your comments to this or other postings, using the tool below.
Posted by David Chappell on March 17, 2010
|Search the online Automation Integrator Guide|
Case Study Database
Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.
These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.
Click here to visit the Case Study Database and upload your case study.