About Equipment Sequence event processing

These steps describe how an event from a running
Equipment Sequence
 becomes a record that can be reported or analyzed:
  1. The
    Equipment Sequence
     program generates an event. These actions can generate an event:
    • An operator interacts with the
      Equipment Sequence
       or with a sequence element.
    • An operator changes the value of a sequencing parameter or a step tag.
    • An
      Equipment Phase
       interacts with a sequence element.
    • The sequencing engine changes an attribute of the
      Equipment Sequence
       or a sequence element.
    • The
      Equipment Phase
       changes the value of a step output tag.
  2. The
    ControlLogix
     controller publishes the event.
  3. The Sequence Manager Event Client Service, subscribed to the controller, receives the event and caches it as raw data in a file. Each
    Equipment Sequence
     that is running has its own raw data file.
  4. When an
    Equipment Sequence
     program generates an end-of-sequence event--when the sequence program is reset from the COMPLETE, STOPPED or ABORTED state--the Sequence Manager Event Client Service signals the Sequence Manager Event Archiving Service to process the raw event file.
  5. When it receives the signal from the client service that an
    Equipment Sequence
     is complete, the Sequence Manager Event Client service adds the raw event file name to the Sequence Manager Archiving Service’s work queue. The raw events are translated into event records by the Sequence Manager Event Archiving Service and are stored in an EVT file. The EVT file name is the unique identifier for that execution of the equipment sequence. Optionally, the archiving service stores the events in the BHBatchHIS table of the BatchHistoryEX database within
    PlantPAx
     Historian. Consult the
    PlantPAx Process Automation System Reference Manual
     , publication PROCES-RM001, for instructions on archiving events in
    PlantPAx
     Historian.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.