Emerson Exchange 365

Basic difference between Abort & Stop Command

hi experts,

can you tell what is the basic difference between ABORT & STOP Command in BOI (Batch Process)?

Why we always use Abort Command then Stop Command?

HP

Thanks,

HP

• batch process
• DeltaV

HP

• 17 May 2016 11:54 PM
• Cancel

5 Replies

• DBacker

  

  • 18 May 2016 1:08 AM

  Frequently the final control elements are set to the same passive state in the same order for HOLD, ABORT and STOP. In those cases there is no "functional" difference between HOLD, STOP and ABORT. There is an important difference in that you can restart only from HOLD. You cannot restart from Stop or Abort. Also, S88 requires Batch Header and Batch End information in addition to the code functioning correctly. Frequenlty the batch-end reporting for Stopped and Aborted Batches is inadvertently omitted. The Batch End information of a stopped or aborted batch could capture materials lost to a trashed batch or it could determine the most appropriate reprocessing Unit Procedure/Operation/Phase to recover the materials in process.

  • Cancel
• Steve Linehan

  

  • 18 May 2016 11:12 AM

  Traditionally in big machines a STOP was a controlled sequence to shutdown a system in an orderly fashion. Like closing your computer shut all the windows and then shutdown system. ABORT was when something was wrong and the system could not be shutdown. Like windows crash. This also uses an ABORT sequence but would not wait long times or wait for confirmation of valves closing etc. The implementation of ABORT and STOP varies between industries and even between site's in the same industry. Reach out to users within your industry to see how they are using these sequences. In some industries STOP of a phase or operation is a normal process event. ABORT is always a full stop now in every industry I have seen. The reason DeltaV has them programmable is the end user decides what these should do and how to program them.

  • Cancel
• gamella

  

  • 18 May 2016 12:07 PM

  There is a functional difference in DeltaV Batch when a transistion on recipe is configured to something different than transition related step "status complete".
  In this case, when that transition becomes TRUE the Batch Executive issues a STOP command to transition related step (it could be Unit Procedure, Operation or Phase, depending on which level that transition is).
  
  DeltaV Batch provides this Recipe flow control mechanism so STOP sequence must be configured properly to use this feature.

  • Cancel
• gamella

  

  • 18 May 2016 12:09 PM

  Note that when a transition on Recipe is forced (using BOI pfc view) a STOP command is sent to related recipe STEP by the batch executive.

  • Cancel
• MichaelP

  

  • 19 May 2016 2:06 PM

  When using active step change (batch control) - ASC - the batch sends a stop command to the step to be deactived.
  Also look to the Phase S88 model found at the top level of any phase. It will help explain the way the phase operates when it receives a "stop" or "abort".

  • Cancel