Automation Glossary • First-Out Annunciator

What Is a First-Out Annunciator?

Merobix Engineering • • 8 min read

When a machine trips and a row of alarm windows all light up at once, which one caused it? A first-out annunciator answers that with hardware. This guide explains what an annunciator panel is, how first-out logic works in it, and why this classic control-room device still sits beside modern SCADA on critical equipment.

Back to Blog

First-Out Annunciator in one line: A first-out annunciator is an alarm annunciator panel that uses first-out (first-up) logic to distinguish the initiating alarm in a group from the alarms that follow. The annunciator itself is a panel of labeled illuminated windows, each tied to an alarm input; first-out logic makes the first window in a related group flash or display distinctly while later windows light steadily, so an operator can immediately see which condition tripped the equipment.

The Annunciator Panel

An annunciator is a panel of individual illuminated windows, each engraved with an alarm description such as Low Lube Oil Pressure or High Bearing Temperature. Each window is wired to a field contact; when that condition occurs, the window lights and an audible horn sounds. The operator presses acknowledge to silence the horn, and the window stays lit until the condition clears and is reset. This behavior - the alarm sequence - is defined by standards such as ISA-18.1, the long-standing annunciator sequence standard.

Annunciators are hardwired and independent of the control system, which is exactly why they persist. On a compressor package, engine, turbine, or fired heater, the annunciator gives a dedicated, always-visible indication of critical trip conditions that does not depend on a SCADA screen being on the right page or a computer being healthy. It is a simple, robust, purpose-built alarm display.

How First-Out Logic Works in the Panel

When a trip cascades, interlocks fire in quick succession and, without help, several annunciator windows light almost simultaneously - the operator cannot tell cause from effect. First-out logic solves this within a defined group of alarms: the first window to activate is made to flash or is otherwise displayed distinctly, while windows that activate afterward light with a steady, different indication. The panel latches that first-out state until it is acknowledged and reset, so the initiating alarm is preserved even after the dust settles.

The payoff is faster, correct diagnosis. On a gas-compression package, first-out indication tells the operator that high vibration tripped the unit first, rather than the low-suction-pressure alarm that merely followed - directing them to the real problem before a restart. In modern facilities this same first-out concept is also implemented in software within the SCADA and PLC, but the hardwired first-out annunciator remains common on critical rotating equipment because of its independence from the control system.

Specifying the Alarm Group and Field Contacts

First-out is only as good as the group behind it. Include the conditions that can genuinely initiate the trip - the process and machine-protection causes - and keep consequence alarms out of the group. If the shutdown itself closes a valve and kills flow, a low-flow alarm wired into the first-out group will race the true cause every time and sometimes win, which defeats the whole point. Build one group per protected machine or train, and review the grouping with operations: the people who respond to the panel are the best judges of which windows answer the question of what tripped the unit and which merely describe the aftermath.

Field contact selection matters as much as grouping. Wire inputs fail-safe wherever the equipment allows: a contact held closed in the healthy state, opening on alarm, means a broken wire or lost supply announces itself as an alarm instead of silently disabling a window. Match the annunciator's contact wetting voltage and input type to the field devices per the manufacturer's documentation, and keep true trip contacts separate from indication-only signals so a lamp problem can never be confused with a protection problem. Spare a few windows and inputs in the original specification; annunciator points, like panel rail, only ever get added.

ISA-18.1 Sequence Designations in Plain Terms

ISA-18.1 describes annunciator behavior as standard sequences identified by letter codes: automatic-reset, manual-reset, and ringback families, with first-out variants carrying an F designation and numbered options that select exactly how the first-out indication displays and resets. When you specify or replace a panel, the sequence designation is the contractual description of its behavior - two panels both labelled first-out can still behave differently on acknowledge and reset if their sequence options differ, which is exactly the kind of surprise operators hate.

Choose the reset philosophy deliberately rather than accepting a default. Decide whether the first-out indication clears on acknowledge or persists until a deliberate first-out reset, whether the horn re-sounds for new alarms while earlier ones stand, and whether a ringback indication announces conditions that have cleared. Whatever is chosen, keep it identical across every annunciator in the control room and write it into the alarm response procedures - a consistent sequence is learned once, an inconsistent one is relearned during every upset.

Testing a First-Out Panel

Test the sequence, not just the lamps. A first-out panel proves itself only when related inputs are exercised in order, with the machine isolated and the work coordinated with operations under site procedures:

  1. Run the lamp and horn test and replace any dead windows before functional testing.
  2. Trip each input individually and confirm the correct window, legend, and horn response.
  3. Trip two inputs in the same group in a known order and verify the first shows the first-out indication and the second shows the follower indication.
  4. Acknowledge and reset, confirming the behavior matches the specified ISA-18.1 sequence.
  5. Compare what the panel showed against what the control system recorded for the same test.
Repeat the two-input test with the order reversed; a panel that always names the same window first regardless of order has a wiring or logic fault worth finding before it misleads a real investigation.

First-Out, Sequence of Events, and the Wider Alarm System

The hardwired panel and the control system answer different questions and are strongest together. The annunciator names the initiating cause at a glance; the PLC or SCADA sequence-of-events record supplies the timestamps and the full ordering for the investigation file. After any trip, reconcile the two - if the panel's first-out disagrees with the recorded event order, one of them has a wiring, scan, or configuration problem worth finding before the next trip. The habit belongs to the same discipline as investigating an alarm flood: establish the true initiating event, then work forward.

Fold the annunciator into the site's alarm management rather than leaving it as an island. Its windows should appear in the master alarm database with response actions, its priorities should be consistent with the screen alarms, and its existence should be recorded in the site's alarm philosophy so future projects neither duplicate it nor quietly orphan it. When a legend card changes because the equipment changed, the documentation and operator training change with it - an annunciator window that no longer matches the plant is worse than none.

Frequently Asked Questions

What is the difference between a first-out annunciator and first-out logic in software?

The function is the same - identify the initiating alarm in a cascade. A first-out annunciator is a physical, hardwired panel of illuminated windows independent of the control system, common on critical machines. Software first-out logic performs the same identification inside the SCADA or PLC and presents it on a screen. Critical equipment often has both.

Why keep a hardwired annunciator when the SCADA already alarms?

Because the annunciator is independent of the control system. It gives a dedicated, always-visible indication of critical trip conditions that does not depend on a computer being healthy or a display being on the right page - a robustness that matters for machine protection on compressors, engines, turbines, and heaters.

Does Merobix replace a first-out annunciator?

Merobix complements it rather than replacing safety-related hardwired panels. Merobix can read the same alarm and trip status into its SCADA and apply first-out indication in software, giving remote operators the same insight while the independent hardwired annunciator stays in place for machine protection.

How close together can two alarms occur and still be discriminated?

That is a hardware property of the specific annunciator - its input scan and latch design set the discrimination resolution, so consult the manufacturer's data rather than assuming. When two windows in a group both claim first-out, or the result varies between identical tests, treat it as a sign the initiating events fall inside the panel's resolution, and lean on the control system's sequence-of-events timestamps for the true order.

Can first-out indication be added to an existing annunciator?

Sometimes. Many panels are built from sequence modules, and the manufacturer may offer the first-out sequence as a module or configuration change; the practical constraints are the wiring of the alarm group, the sequence the rest of the panel runs, and spare capacity. If the hardware cannot support it, the same function can be implemented in the PLC as a latched first-out flag per group and displayed in SCADA, while the panel keeps its existing role.

More in Alarms & Alarm Management
Set Up First-Out Alarm Detection  •  First-Out Alarm  •  Trip string and first-out logic  •  Tune Out Nuisance Alarms  •  Out-of-service alarm  •  All Alarms & Alarm Management →
Free SCADA operator training
Merobix University - 70 video lessons & 261 quiz questions, from first login to compliance reporting. No demo call required.
Start free →