← All examples

PLEXUS EXAMPLE · 07

Alarm list vs instrument index

Twelve alarms checked against the instrument index and the alarm philosophy: orphans, range clashes and priority drift flagged for review.

Input

ALARM LISTACD-ALM-0001

DCS alarm database extract, ACD-300-001

Revision
Rev B
Alarms
12
Scope
ACD-300-001
INSTRUMENT INDEXACD-REG-0001

Master Tag Registers, Instruments sheet

Revision
Rev 0
Filter
ACD-300-001
Instruments
10
Instrument existsEvery alarm references a live instrument in the index for this sheet.
Setpoint inside rangeSetpoints sit inside the calibrated range and clear of their trip setting.
Priority per BoDPriorities follow the BoD alarm philosophy: P1 pre-trip, P2 deviation, P3 advisory; alarms at 80% of the normal-to-trip gap.

The source documents are not shown: alarm databases and registers stay inside your project. The check below runs on a hypothetical plant (ACD), presented the way consistency results arrive.

What Plexus does

  1. 01Reads the alarm list and the instrument index into one structure.
  2. 02Checks each alarm against its instrument: existence, range and trip margin.
  3. 03Checks priorities against the BoD alarm philosophy.
  4. 04Marks each alarm pass, conflict or check; the engineer confirms and updates the alarm database.

Output

0 / 12 alarms checkedrun first, then export

This animation illustrates the Plexus workflow on a hypothetical plant (ACD). In the product, consistency checks run server-side and every value keeps provenance to its source document; an engineer reviews and confirms.

Source documents: ACD-ALM-0001 Rev B and ACD-REG-0001 Instruments sheet, hypothetical plant

AlarmInstrumentSetpointPriorityStatus

Manual: 2-4 hours
With Plexus: 10-20 min review (estimate, one-sheet alarm list against the instrument index)

Next exampleEquipment list vs datasheets