LLE/OFCI: The Most Under-Managed Schedule Risk in Major Projects

Ask a delivery team what sits on their critical path and they will talk about structure, services rough-in, or commissioning. Ask what actually moved their end date on the last project and the honest answer, more often than not, is a piece of equipment: a transformer that missed its vessel, a generator held at factory test, switchgear that arrived to a room that could not receive it. Long-lead equipment (LLE) and owner-furnished, contractor-installed items (OFCI) are the most consistently under-managed schedule risk in major projects — and on data centre programmes they are frequently the entire game.

Why it stays under-managed

Three structural reasons. First, split ownership: the owner buys it, the contractor installs it, and the gap between those obligations is exactly where slippage hides. An OFCI delivery date in a contract is a hope wearing a date's clothing unless somebody tracks the chain behind it. Second, tool blindness: scheduling tools represent equipment as a milestone — "chillers delivered" — which compresses a nine-month, multi-party pipeline into a single diamond nobody interrogates. Third, optimism at tender: market lead times are quoted at their best-case because the bid needs them to be, and the delivery team inherits the bet.

Milestones are not management

The fix begins with representation. Each significant package deserves its own logic chain in the programme: purchase order → design/submittal approvals → manufacture → factory acceptance test (FAT) → shipping → site receipt → installation readiness. Seven links, each owned, each dated, each capable of being early or late independently. When the chain exists in the logic, a FAT slip in month four visibly pushes an energisation gate in month eleven — while there is still time to resequence, split shipments, or negotiate factory slots.

On the Stack MEL01 and MEL02 campus we tracked LLE/OFCI from purchase order through FAT, shipping, and site receipt precisely so long-lead items drove the logic instead of surprising it — across successive stages where the same equipment classes repeated and the lessons compounded.

Receipt is not readiness

The second half of the discipline is on site. Equipment arriving is not equipment installed: the room must be ready — structurally complete, clean regime in force, access route intact, pads and services in position. "Delivered to a laydown yard" and "installable" can be months apart, and double-handling mission-critical plant is both a schedule and a warranty problem.

We treat area readiness as a measured state, not an assertion: room-by-room scope completion, weighted by activity, tested against entry criteria before a space is declared able to receive equipment. Pairing the equipment chain with the room chain is what turns a delivery schedule into an installation programme.

What good looks like

A programme that manages LLE/OFCI properly has four visible features. Every significant package has an end-to-end logic chain with named owners on both sides of the owner/contractor boundary. Vendor commitments are tracked against evidence — factory slots, shipping bookings — with escalation triggers, not just a monthly expediting report. Installation readiness is gated on measured area status. And the commissioning programme consumes the same chains, because a late chiller is not a delivery problem: it is an L3 test slot problem three months downstream.

None of this requires new software — it requires the programme to tell the truth about where its schedule risk actually lives. On mission-critical projects, that truth usually has a serial number.

Nomad SPS manages LLE/OFCI as first-class programme logic within project controls engagements on hyperscale and mission-critical programmes. If your end date depends on equipment, talk to us.