Log In   |  Register Free Newsletter Subscription
Skip navigation
Zibb
Subscribe to Control Engineering
FirstLight
RSS
Email
Average Rating:
  • (4)
    Rate this:
  • ISA88 Part 1 Update: more useable, clearer, see new state diagram

    February 26, 2009
    See more of this proposed graphic, below
    ISA88 Part 1, excerpt of proposed state diagram

    This week a group of eight, with some phone input, worked to move the Part 1 update forward. This has lead to a major reorganization of the Part 1 document that many feel will make it much more understandable and useable, and I have to agree that it seems to be better organized and the concepts and relationships of the models clearer at first glance. See three diagrams below.

    Dennis Brandl has proposed adoption a new state diagram shown to represent procedural control. This is different than both the TR02 and Part 5 representations, and both groups are evaluating a final resolution that MUST become common between Part 1 and Part 5. (Note prior discussions about the Part 1 and Part 5 interactions.)

    Lots of discussion and learning, with a lot of effort around Procedures and Recipes were a significant part of the meeting. Stay tuned for more results! Three diagrams follow.


    ISA88 Technical report 02 state diagram for a unit/machine at the unit level, below
    ISA88 Technical report 02 state diagram for a unit/machine at the unit level

    S88 Part 1 proposed — State transition diagram for example states for procedural elements, below
    S88 Part 1 proposed — State transition diagram for example states for procedural elements

    S88 Current Part 5 proposed state diagram for the equipment phase, below
    S88 Current Part 5 proposed state diagram for the equipment phase

    Please post any thoughts or comments below, please, using the tool provided, or let an ISA88 committee member know, directly.

    Posted by David Chappell on February 26, 2009 | Comments (3)
    Average Rating:
  • (4)
    Rate this:

  • March 5, 2009
    In response to: ISA88 Part 1 Update: more useable, clearer, see new state diagram
    Francis commented:

    Dennis I dont know if you read the rest of my comment on my blog. Summarising, I can see that transient states are present, but what I am trying to say is why do they need to be exposed outside of the controlling object. So for example if a control recipe asks an EPE to run a phase, what does it care whether the phase is starting, running or stopping, pausing or paused ? Once it is pausing or paused that is all the control recipe needs to know until it is running again. What is the control recipe supposed to do with the transient information ? Propagating modes to other objects maybe, but that should be only what is reasonable in Recipe Control – the real time stuff should be down in basic control. And I suspect that the transient states are really about the real time world.


    March 4, 2009
    In response to: ISA88 Part 1 Update: more useable, clearer, see new state diagram
    Dennis Brandl commented:

    The transient states are there because the recipe is not in control, it is only requesting that the equipment perform the action (Start, Stop, Abort, ...). Because some of these can take time, there should be a state that shows that the action was started but has not yet completed. In many cases the transient states may not be used (because the action is essentially immediate) or goes by so fast that it is not seen (assuming some sort of polled scan of the state).


    March 2, 2009
    In response to: ISA88 Part 1 Update: more useable, clearer, see new state diagram
    Francis commented:

    Who needs the Transient Procedural States? I always work on the principle that the recipe controller (that handles the control recipe) is a transaction based sequencing and data handling system. It can tolerate short delays. It is in effect the process operator; it cares little about the equipment provided it can do what the recipe asks of it. It can request the equipment to do some process action, then wait until it has. Basic control that drives the equipment is real time and cannot tolerate such delays. The original Part 1 provides a lot of suggestions and some basic models that help to specify both the recipe and the basic control. And it shows how they can meet, via Procedural Entities. To interface the control recipe with the equipment, there must be EPE’s (Equipment Procedural Entities), typically phases, that actually execute the process action. But think about this – why should the recipe control have any real time capability other than being fast enough to avoid introducing significant delays Read more here www.s88control.blogspot.com/2009/03/who-needs-transient-procedural-states.html

    POST A COMMENT
    Display Name
    captcha

    Before submitting this form, please type the characters displayed above. Note the letters are case sensitive:

    Advertisement
    CtlEng_EngEdCenter_160x160
    Advertisement
    2010Sensors160x160
    NEWSLETTERS
    Weekly News
    Process Instrumentation & Sensors Monthly
    System Integration Monthly
    Process & Advanced Control Monthly
    Machine Control Monthly
    Information Control Monthly
    Product Review
    Sustainable Engineering
    Simplified Safety
    Fieldbus Facts
    PROFInews North American Edition



    Please read our Privacy Policy

    About Us   |   Advertising Info   |   Site Map   |   Contact Us   |   FREE Subscription   |   Useful Sites   |   RSS
    © 2010 Reed Business Information, a division of Reed Elsevier Inc. All rights reserved.
    Use of this Web site is subject to its Terms of Use | Privacy Policy