When a plant trips, the shutdown does not arrive as a single event - it arrives as a flood. Dozens of alarms latch within seconds as pressures fall, flows stop, and interlocks propagate, and the operator is left staring at a screen full of red with no obvious culprit. First-up capture cuts through that flood by identifying the one input that actually initiated the cascade. This guide explains what first-up logic does, how it freezes and flags the initiating signal, and how it relates to the first-out annunciator and first-out alarm concepts covered elsewhere.
First-Up Alarm in one line: A first-up alarm is the single input that a safety system identifies as the true initiator of a cascading trip - the first-in signal that started the shutdown before all the downstream consequences fired. First-up capture freezes and flags that initiating point so engineers know which sensor or interlock actually caused the trip, and it is tightly tied to sequence-of-events timestamping across the whole safety instrumented system.
A modern process trip is a chain reaction. A single high-pressure switch might de-energize a trip circuit, which closes shutdown valves, which collapses flow, which drops downstream pressures below their own low limits, which trips compressors, which fire still more alarms. Within a second or two, the annunciation shows twenty or forty active conditions - and every one of them is real. The problem is that only the very first condition was a cause; everything after it was a consequence of the shutdown already in progress.
Without first-up logic, an operator has no reliable way to separate the initiator from the followers. Priority, colour, and grouping all help, but they cannot tell you sequence. Two alarms that both read 'active' on the screen look identical whether one preceded the other by ten milliseconds or arrived in the same scan. Chasing the wrong one wastes hours during a restart, and it can hide a genuine equipment fault behind a wall of expected downstream trips.
First-up capture exists to answer the single most valuable question after any shutdown: what tripped first? By singling out the initiating input, it turns an intimidating cascade into a diagnosable event and points maintenance directly at the sensor, valve, or interlock that needs attention before the plant restarts.
The core mechanism is a latch-and-inhibit scheme. When the safety logic detects a trip condition, it captures the identity of that first input and then blocks any later inputs in the same group from claiming first-up status. The first-in signal is latched and flagged distinctly, while the crowd of consequential trips that follow are recorded as active but marked as secondary. The flag holds until an operator acknowledges and resets it, so the evidence survives the shutdown rather than being overwritten by the noise that came after.
What makes first-up trustworthy is the timestamp behind it. First-up capture is bound to sequence-of-events recording, where every relevant input is time-stamped at high resolution - often to the millisecond - at the point closest to the field. Because the initiating condition is genuinely earlier than its consequences, accurate timestamps let the logic resolve the true order even when several inputs change within a single controller scan. The first-up flag is, in effect, the earliest sequence-of-events record in the trip group.
This distinction between one flagged initiator and a time-ordered list of everything else is what separates first-up from a simple alarm summary. The summary tells you what is wrong now; first-up, backed by sequence of events, tells you what went wrong first.
First-up overlaps heavily with the first-out concept and the two terms are often used interchangeably, but there is a useful difference in scope. First-out logic, whether in a hardwired annunciator panel or an alarm system, classically flags the initiating alarm within one related group of windows or points on a piece of equipment. First-up, as used here, is framed around the trip initiator across the whole safety instrumented system and is defined by its dependence on sequence-of-events timestamping rather than by the display device. In practice they answer the same question - which one fired first - but first-up emphasises the plant-wide, time-stamped root trip signal rather than a single panel.
For that plant-wide view to work, the safety logic solver and the SCADA layer have to preserve order faithfully. The logic solver captures the first-in input and its timestamp at the source; the SCADA system then collects those records, sorts them by time, and presents the first-up point at the top of the sequence-of-events log. If timestamps were applied only when the message reached the server, network delay and polling jitter would scramble the order and the first-up flag would be meaningless - which is why the stamping has to happen close to the field.
A cloud SCADA platform such as Merobix reads the already-time-stamped trip records and the first-up flag from the logic solver, RTU, or safety PLC over an industrial protocol and presents the ordered sequence in a browser. It does not decide which input tripped first; that determination is made in the field device that owns the millisecond clock. What the cloud layer adds is reach - an engineer at another site or at home can open the sequence of events, see the flagged first-up cause at the top of the list, and direct the response without waiting to reach the control room.
They answer the same question - which alarm fired first in a cascade - and the terms are frequently treated as synonyms. First-out usually refers to flagging the initiating alarm within one related group, often on a specific annunciator panel or piece of equipment. First-up, as used here, emphasises the trip initiator across the whole safety system and its reliance on high-resolution sequence-of-events timestamps to resolve the true order.
Because the initiating input and its downstream consequences can all activate within a fraction of a second, sometimes inside a single controller scan. Only high-resolution timestamps applied close to the field can reliably prove which one was genuinely first. First-up capture is essentially the earliest sequence-of-events record in a trip group, so without accurate timestamping the flag would not be trustworthy.
The flag is latched so it survives the shutdown and holds until an operator acknowledges and clears it, which prevents the initiating cause from being overwritten by the many consequential trips that follow. That persistence is deliberate: engineers need the first-up evidence intact during the post-trip investigation and restart, not erased the moment the process starts recovering.
Safety & engineering notice. This article is general educational information, not site-specific engineering, safety, or legal advice, and it does not reflect any particular facility. Standards and regulations (for example OSHA, API, IEC, ISO, NFPA, NIST, and NERC CIP requirements) change and vary by edition, jurisdiction, and application. SCADA and remote monitoring cannot verify physical isolation, atmosphere, lockout/tagout, permit status, or a safe go/no-go decision. Qualified personnel must perform site-specific engineering, hazard analysis, and safety review, and confirm current requirements with the authority having jurisdiction, before acting.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.