When something goes wrong on a compressor package, the shutdown that follows is not a single blunt stop. Different faults call for different responses, some cutting fuel and opening recycle, others also blowing the machine down or keeping the cooler running afterward, and each carries a severity. A unit shutdown key is the package-level table that maps every trip initiator to exactly what it does and how serious it is. This page defines the shutdown key, explains its severity classes and run-on outputs, and describes how first-out identification helps operators read what happened.
Unit Shutdown Key in one line: A compressor unit shutdown key is the package-level cause-and-effect table that maps each trip initiator on a single compressor to the actions it triggers and its severity class. For every initiator it lists the outputs, such as cutting fuel, opening the recycle valve, blowing the machine down, or keeping the cooler running on after the stop, and it assigns a severity class that sets how far the shutdown goes. Operators read this key on the HMI alongside first-out identification, which flags the initiator that fired first so they know the real cause among the cascade of alarms.
The shutdown key is organized as a matrix of initiators against effects for one machine. Down one side are the trip initiators, the specific conditions that can shut the unit down, such as high discharge temperature, low lube oil pressure, high vibration, an axial position excursion, a fuel gas pressure fault, or a manual trip. Across the other side are the effects, the outputs the system can drive, such as tripping the driver, cutting fuel, opening the recycle valve, closing block valves, initiating blowdown, and holding the cooler running. Each initiator's row marks which effects it commands, so a single glance shows exactly what any given trip does to the machine.
Not every trip does the same thing, and that is the point of the key. A minor process excursion might trip the driver and open recycle but leave the machine blocked in at settle-out with its inventory intact, ready for a quick restart. A serious mechanical fault or a fire signal might do all of that and also blow the machine down to depressurize it. By reading across an initiator's row, an operator or engineer sees the full consequence of that specific fault, which matters because the appropriate response and the appropriate recovery differ from one initiator to the next.
Because the machine's response differs by severity, the key groups initiators into severity classes, often labeled with letters or levels. A higher class drives more effects and a more thorough shutdown, while a lower class does a gentler stop. The class captures the philosophy that a fault threatening the machine or safety warrants a deeper, faster shutdown than a routine process trip, and it lets the many initiators be understood as a handful of consistent shutdown behaviors rather than dozens of unrelated ones. The class an initiator carries tells you at a glance how hard the machine is being stopped.
Some effects in the key are not about stopping things but about keeping something running after the stop, which is what run-on outputs describe. The most common is the cooler or the auxiliary lube oil pump running on after the compressor trips: the machine has just been full of hot gas and its bearings are hot, so continuing to cool and lubricate for a period after the stop protects the equipment as it winds down and soaks. The shutdown key shows these run-on outputs explicitly, because an operator seeing a fan still turning or a pump still running after a trip needs to know that is intended post-trip behavior, not a fault.
Run-on is timed and conditional, and the key captures that logic. A post-trip lube pump might run for a set period or until bearing temperatures fall, and a cooler might run on to bring the process side down before it too stops. These outputs are part of the cause-and-effect because they are consequences of the shutdown just as much as the trips are, and leaving them out would make the machine's behavior after a trip seem mysterious. Showing them keeps the key a complete account of everything the shutdown does, during and after the stop.
The key also distinguishes a driver trip from a full unit trip, because they are not the same event. Tripping only the driver stops the machine turning but may leave the rest of the package in a controlled state, whereas a full unit shutdown drives the broader set of effects across the whole package. Some initiators trip only the driver, others escalate to a unit shutdown, and the key makes the distinction visible so operators understand whether just the prime mover stopped or the entire package sequenced down. This clarity matters during recovery, since restarting from a driver trip is a different proposition than recovering from a full unit shutdown.
When a compressor trips, it rarely trips on just one alarm. The initiating fault causes the machine to stop, and stopping causes a whole cascade of secondary conditions to go into alarm, so within a second the operator can be facing a screen full of active alarms, most of them consequences rather than causes. First-out identification cuts through this by capturing and flagging the initiator that fired first, the one that actually caused the shutdown, so the operator can tell the root cause from the follow-on noise. Without first-out, diagnosing a trip means guessing which of many simultaneous alarms came first.
The shutdown key and first-out work together on the HMI. The key tells the operator what each initiator does and how severe it is, and first-out tells them which initiator did it this time. Reading the two together, an operator sees that the machine tripped on, say, high vibration, a class that also opened recycle and ran the lube pump on, and immediately understands both the cause and the full set of actions the trip took. This turns a confusing wall of alarms into a clear story: this fired first, it is this severity, and here is everything it did.
For remote and unattended stations, the shutdown key and first-out are what make a distant trip explainable rather than a mystery. A dispatcher who cannot walk up to the machine relies entirely on the telemetered first-out cause and the known effects of that initiator to understand why a unit is down and what state it is in. A monitoring platform such as Merobix records the first-out cause and the shutdown class for every trip across the fleet, so recurring initiators, machines that trip more often on the same cause, or a drift toward more severe shutdowns all surface as patterns. Turning each trip into a logged first-out with its severity and effects lets operators move from reacting to individual events to spotting the machine or the fault that keeps coming back.
It is a package-level cause-and-effect table that maps each trip initiator on one compressor to the actions it triggers and its severity class. For every initiator it lists the outputs, such as cutting fuel, opening recycle, closing block valves, blowing down, or running the cooler on, and assigns a severity class that sets how far the shutdown goes. Reading across an initiator's row shows exactly what that fault does to the machine, which is what operators and engineers need to understand a trip.
A run-on output keeps something running after the compressor stops, most often the cooler fans or the auxiliary lube oil pump. The machine has just been full of hot gas with hot bearings, so continuing to cool and lubricate for a period after the trip protects the equipment as it winds down and soaks. The shutdown key shows these run-on outputs explicitly, so an operator seeing a fan or pump still running after a trip knows it is intended post-trip behavior rather than a fault.
When a compressor trips, the initiating fault causes a cascade of secondary alarms, so the screen fills with active alarms that are mostly consequences rather than causes. First-out identification captures and flags the initiator that fired first, the one that actually caused the shutdown, so the operator can tell the root cause from the follow-on noise. Read together with the shutdown key, it tells the operator both what tripped the machine and everything that trip did.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.