Before a compressor, pump, or fired heater is allowed to start, a whole checklist of conditions usually has to be satisfied at once. A startup permissive string is how that checklist is built into logic: a series chain of every required condition, wired so that only when all of them are true does the unit become ready to start. Just as important as blocking the start is telling the operator why they cannot start, which is why a good permissive string does not just say no, it names the one condition that is holding things up.
Startup permissive string in one line: A startup permissive string is the series chain of all the conditions that must be satisfied before a unit is allowed to start, built as a set of ANDed contacts so that a single unmet condition breaks the chain and blocks the start. It is surfaced to the operator as a ready-to-start indication, and well-designed strings also report which permissive is not met, so the operator knows exactly what to fix rather than facing a start button that simply refuses.
The string is a logical AND of many conditions, which in ladder logic looks like a row of normally-open contacts wired in series feeding a ready-to-start bit. Every condition must be true for current to reach the end of the rung. If any one contact is open, meaning that permissive is not satisfied, the whole chain is broken and the ready bit is off. That series structure is the natural, readable way to express all of these must be true at once, and it is why the pattern is called a string: it is a chain, and the chain is only as complete as its weakest link.
The conditions in the string are the concrete prerequisites for a safe start. For rotating equipment they typically include things like lube oil pressure established, seal or buffer systems proven, cooling available, valves in their correct startup lineup, no active shutdown latched, and any required upstream or downstream equipment already running. Each of these becomes one contact in the series chain. Adding a new prerequisite to the startup procedure means adding one more contact to the string, and removing one means the opposite, which keeps the logic a faithful mirror of the written procedure.
It is worth being clear that the string is about permission to start, not continuous protection. Once the unit is running, the run-time guards are the interlocks, which act on every scan; the permissive string has done its job at the moment the start is granted. Keeping that boundary clean matters, because a condition that only needs to be true at startup belongs in the string, while a condition that must hold the entire time the machine runs belongs in the trip logic. Mixing the two in one chain confuses both the operator and the next engineer to read the code.
The output of the string is a single ready-to-start signal that the operator can see. When every permissive is met, the indication is green and the start is enabled; when any is not, the indication tells the operator the unit is not ready. On its own, though, a bare not-ready light is frustrating, because a real startup string might have a dozen or more conditions and the operator has no way to know which one is the problem. The unit will not start and the display does not say why, which turns a straightforward startup into a hunt.
The solution is a first-not-met display, sometimes called a first-permissive-not-met indication. Instead of just reporting that the string is broken, the logic scans the conditions and reports the specific permissive, or the list of permissives, that are currently blocking the start. The operator reads seal gas pressure low or ready in ten seconds and goes straight to the actual obstacle rather than checking everything by hand. This turns the permissive string from a gate that merely refuses into a diagnostic aid that guides the operator through the startup.
Presenting the not-met reasons well is a real design task. Some systems highlight every unmet permissive so the operator sees the full remaining checklist, which is useful when several conditions are still coming up during a cold start. Others show only the first one in a defined priority order, to avoid overwhelming the operator, on the logic that fixing that one may clear several downstream conditions at once. Either way, the value is the same: the string does not just decide whether the unit may start, it explains itself, which is what makes it usable by the person actually pushing the button.
Picture starting a compressor in a gas plant. The permissive string might require lube oil pressure above its minimum, seal gas established across the seals, suction pressure within range, discharge path lined up, cooling water flowing, and no active trip latched. Each of these is one link in the series chain, and the ready-to-start bit only comes true when the last of them falls into place. During a cold start the operator watches the string fill in as each system comes up, and the first-not-met reason walks them through what is still pending.
This is where the interaction with the operator's screen matters. Rather than a single opaque not-ready state, the display shows the checklist: lube oil met, seal gas pending, suction met, and so on, so the operator can see the startup progressing and knows exactly what to attend to next. When the last permissive clears, ready-to-start appears and the operator can commit the start with confidence that the prerequisites are genuinely in place. The string has effectively encoded the plant's startup procedure into something the machine enforces and the operator can read.
For a remotely operated or lightly manned site, the permissive string and its not-met reasons are among the most valuable things to surface to a cloud dashboard. A remote operator deciding whether to start a compressor needs to see the same checklist a local operator would, so they are not commanding a start blindly. The string logic itself runs on the local controller so it enforces the prerequisites regardless of the link, and the dashboard mirrors the live state of each permissive and the reason the unit is not yet ready. That combination lets a start be initiated from a distance while still respecting every condition the procedure demands.
A permissive string is a set of conditions checked at startup to decide whether a unit may begin running, built as a series chain that must be fully satisfied to enable the start. An interlock is a condition checked continuously while the equipment runs and trips it if violated. The string gates the start; the interlock guards the run, and the two serve different moments in the equipment's life.
Because a bare not-ready indication does not tell the operator which of many conditions is blocking the start. A first-not-met display names the specific permissive, or lists all unmet ones, so the operator goes straight to the real obstacle instead of checking the whole chain by hand. It turns the string from something that merely refuses into a diagnostic aid that guides the startup.
It is a series chain of contacts, one per required condition, feeding a ready-to-start bit. Because the contacts are in series, current only reaches the end of the rung when every condition is true, so a single unmet permissive breaks the chain and blocks the start. Adding a prerequisite means adding one more contact, which keeps the logic a direct mirror of the written startup procedure.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.