[ OPERATING INTERSECTION ]
Operational readiness across the site
Why mechanically complete equipment is not yet a ready regulated operation.
What this page does not claim
SPEQ synthesis for education. Confirm applicable law, current guidance, standards editions, contractual duties, and organization-specific controls before making a regulated decision.
The seam below, its failure modes and its decision boundaries are SPEQ’s practitioner framing — not a regulatory requirement, and not an assessment of any organization.
OPERATING QUESTION
Are people, assets, systems, materials, methods, suppliers, evidence, and escalation ready together?
Capabilities in the same decision
Why this is hard
A capital project and a regulated operation are graded on different things, and the handover happens at the exact moment the grading changes. A project is graded on completion: a bounded scope, a fixed date, an asset that performs as specified while the people who built it are standing next to it. An operation is graded on repeatability: the same result on a Sunday night shift, with the second-string operator, a substitute reagent lot and an analyst who qualified last week. Nothing inside the project can test the operation’s claim, because the operation has not run yet — and nothing inside the operation can correct the project’s assumptions, because by then the project team has been reassigned. The second difficulty is arithmetic. Readiness is a conjunction, not a sum: seven functions each honestly ninety-five per cent there are not ninety-five per cent ready, they are stopped by whichever single condition is outstanding. Because each function reports against its own scope, the condition that stops the start-up is almost always the one sitting between two scopes — a reference standard the release method needs that no equipment package included, a spare with a fourteen-week lead time, a second qualified analyst. Every function is competent, every report is true, and the site is still not ready.
How it fails
Each of these happens with every function doing its own job correctly. That is what makes them seam failures rather than performance problems.
Readiness is averaged instead of conjoined
The readiness review collects a percentage from each function and shades the roll-up green once the average clears a threshold. Every input is honest. The arithmetic is not: readiness is a conjunction of independently owned conditions, so one uncalibrated instrument in the release-method chain stops the start as completely as an unfinished building. Averaging is precisely the operation that hides a single hard blocker inside a field of soft progress, and it hides it best in the final fortnight, when the average is highest and the blocker is most expensive to fix.
The punch list is closed by the team leaving
Outstanding items are dispositioned at handover under schedule pressure, by the organization that is about to depart, against the criterion that matters to them: is this acceptable in order to finish. The people who will live with an unreachable sample point, an unlabelled valve or a missing access platform were not the ones who accepted it. The workaround they then invent is undocumented by construction, and it resurfaces months later as a deviation whose real origin was a decision recorded as a closure.
Qualification ran with the vendor engineer present
The equipment performed faultlessly during qualification because the supplier’s commissioning specialist was there, made the small adjustments nobody wrote down, and handled the one recovery that occurred. The operating procedure was then written from the vendor manual rather than from what the specialist actually did. The first real test of the operation is a night-shift fault the qualification never rehearsed, met by staff who have seen the machine work and have never seen it fail.
The support tail sits in nobody’s budget
Spares, consumables, reference standards, calibration contracts, the maintenance agreement, the second trained analyst and the person who answers at two in the morning each sit just outside the capital scope and just inside an operating budget that has not started yet. No function is wrong about its boundary, which is why the gap survives every review: it is visible only to someone asked to describe the first year of running, and that question is rarely on the agenda.
What good looks like
Readiness is expressed as named conditions with named owners and binary answers rather than as a percentage — each condition either holds, with evidence attached, or does not. The function that will inherit the asset signs its acceptance, and that signature is separate from the one confirming the asset was built to specification. Conditions still open at start-up are not closed; they become dated, owned obligations with an interim control that the people running the process have been briefed on. Somewhere before the date there is a rehearsal that runs the process the way it will actually run — off-shift, with the staff who will do it, including at least one induced fault and one recovery — because a daylight walkthrough with the project team in the room tests the asset, not the operation. The first year of running is costed and assigned to a person before start-up rather than discovered after it. None of this rates an organization; it makes the conjunction visible while the weakest condition is still cheap to argue about.
Who decides what
Two decisions look like one and must not be. The delivering project owns the statement that the asset meets its specification. The receiving operating function owns whether it will take that asset into routine use, which turns on people, materials, methods and support the project never controlled — and where both are the same signature, the second decision has not been made. Quality owns whether the evidence supports regulated use, and that judgement is independent of the schedule that produced it. The laboratory owns its own ability to release, a routine blind spot because its constraint is analyst time and reference material rather than anything visible on the plant floor. The authority that must be named before the start date, never during it, is who may authorise starting with a condition unmet, and on what interim control. Where that authority is unnamed it is exercised by whoever carries the schedule, and the residual risk is accepted by nobody in particular.
Questions practitioners ask
Is operational readiness the same as qualification?
No. Qualification asks whether a system does what it was specified to do and keeps the evidence of it. Readiness asks whether the organization can run the process that system enables, repeatedly, with the staff, materials, methods and support it actually has on the day. A fully qualified line with one trained analyst and no spares is qualified and not ready, and the two questions are answered by different people looking at different things.
Can a site start with open punch items?
Frequently it must, and a rule that forbids it produces closure by reclassification rather than by resolution. What matters is that each open item carries a risk classification, a named owner, a date and an interim control the operating staff have been briefed on — and that the decision to start with it open was taken by the function inheriting the item rather than by the one handing it over.
Who declares that a site is ready?
No single function can, because the answer is a conjunction of conditions no one function can see. Each owner declares the condition they hold and shows what makes it true; a named accountable person for the site declares the composite and is answerable for whatever was waived; and Quality holds a separate judgement about regulated use that is not one vote inside that composite.
Why is readiness harder when an existing site adds a process?
Because the project looks smaller and the conjunction is not. Buildings, utilities and the quality system already exist, so attention concentrates on the new equipment — while the binding constraint is usually the support functions, already fully loaded, whose extra demand arrives as a stream of small requests rather than as a line item anyone approved. Brownfield readiness fails on capacity far more often than on capability.
Critical handoffs
- Project delivery establishes complete and accepted assets.
- Quality and validation establish fit-for-use evidence.
- Operations, laboratory, supply, and support functions demonstrate sustained readiness.
Shared evidence
- System turnover and punch-list closure
- Qualification and training status
- Material, method, maintenance, and support readiness