The program
Project management includes infrastructure upgrades, retrofits, and expansions run inside a live building. The constraint is not the budget or the schedule; it is that the load never notices the work happening.
A project in an operating data hall has a second scope nobody writes down: keeping the facility up while you work on it. That scope is where the risk is.
Drawings, budget and schedule all describe what is being installed. Nothing describes what is running three meters away, which redundancy the work removes, or for how long. Whoever is on site plans the isolation the morning it happens.
New equipment arrives with no asset records, no procedures and no training, exactly like the original build. One retrofit undoes two years of data quality, and the first to find out is a technician holding a work order for an asset that is not in the system.
Work on a live plant gets planned around what it can never be allowed to interrupt. A project in an operating data hall is the same problem with a different load, and it is run the same way here.
Before the schedule exists, we write down what has to stay up, which redundancy each phase removes, and what the fallback is. We hold the trades to that document alongside the drawings.
The order of work comes off exposure to the load rather than off capital value or trade availability. Phases that reduce redundancy land where the site can carry them.
Every contractor on site works to the same permits, isolations, and evidence requirements your own team does. A vendor who is not held to the standard is a hole in it.
Asset records, procedures, and training land with the equipment rather than a quarter later. The retrofit leaves the operating program stronger than it found it.
We hold the project and the environment at once. The plan, the sequencing, and the evidence come from us; the building keeps running.
We do not publish a headline percentage for project work because the number that matters here is binary: the load either noticed or it did not. What is measurable is if the budget held, if the date held, and if operations could run the thing on the day it was handed over.
Uptime
Protected through every phase
Budget
And on schedule
Day One
Operable at handover
These are the questions a facilities lead asks before letting anyone near a live room.
We treat continuity as a written scope rather than an assumption. Every project in an operating hall carries a second scope nobody documents, which is keeping the facility up while you work on it. We write that one down, plan the isolations against it, and hold contingency for the parts that are not reversible.
Yes. Full lifecycle means planning, execution, and the improvement pass afterwards, with the trades run against the same operating standard the site runs to. A contractor working to their own method statement inside a live building is the risk the project was supposed to manage.
Infrastructure upgrades, retrofits, and expansions, scoped by risk to the live environment rather than by capital value. A small project on a single-corded load can carry more risk than a large one in an empty hall.
We compare them to the continuity scope first. A change that is trivial on paper can move an isolation into a window the load cannot survive, so the question is always what it does to uptime before what it does to schedule.
We provide one point of contact with real-time tracking and risk registers open to every stakeholder. Transparency is a deliverable here because the people who have to approve an isolation are rarely the people in the project meeting.
We manage delivery and we read the design from the operator's side: access, isolation, maintainability and whether the procedure can actually be performed on the equipment as drawn. That is the operational design review, and it is the cheapest place to catch something that would otherwise be found during the work.
It stops at a state the building can hold, which is planned for before the work starts. Every isolation has a defined position to return to because the risk in a live hall is not the pause, it is pausing somewhere the load cannot survive.
Not the question you have? Send it over, and one of the people who would actually run your site will answer it.
Ask an operatorA project is where the rest of the operating program gets tested. These three are what it hands back to.
Both routes start from that one question, and the answer is what sets the sequence, the isolation plan, and the contingency.
We take the scope you have and write the second one: what stays up, what each phase removes, and what happens if it does not come back. It usually changes the sequence and rarely changes the cost.
We scope it from the operating side first, so the plan is built around the load rather than fitted to it afterwards. This is the cheaper of the two places to start and almost nobody starts here.