You bought the package, but not the operator.
Now you deal with the outcome. The outcome is downtime.
Five gaps between the system you installed and the building that has to operate it. Principal-led, every engagement.
For data center owners, operators, and the lenders and insurers behind them. You paid for a building full of automation. The question this page answers is whether anyone on your side can actually run it when it is tested for real.
Five gaps between install and operate.
Nobody on payroll is paid to run it.
You signed off on the EPMS, BMS, DCIM, automatic ATS, gen controls, switchgear automation. No one on your team owns that package on that site.
Automation hid the operator. It never replaced one.
You bought the monitoring. The alarms were never validated.
Uptime Institute says alarms have to be accurate and useful. On most sites they were never checked at commissioning. The dashboard looks live. Half the alarms are noise.
The one that matters is silent.
Your monthly test runs with no load on it.
A no-load run proves the engine turns over. It proves nothing about a real failover. OVH ran it that way for years, and no one on shift knew the manual transfer command.
The building can't be tested without dropping load.
No maintenance bypass. No redundant path. No A-side / B-side that lets a piece come down safely. Nobody, including you, will take the outage to find out.
Hope becomes the maintenance plan.
The grid is about to make all of this louder.
Forty data centers dropped in Virginia in 2024. NERC warns of a 15.7% peak demand increase against 115 GW of generator retirements. The package you bought has to operate through it.
Five ways to bring me in.
These are Ready Room engagements, the same interim-leadership rates, scoped to operating the package you already installed. In the data center set this is the run-the-building work. Winning the contract is Data Center Entry. Staffing the floor is the Bridge.
One pass on what is installed at one site versus what your bench can actually operate today. Records in, written brief out. Plus a thirty-minute call on what to push back on with your vendor, your commissioning agent, or your own ops director.
- Format
- Remote. Records in, brief out.
- Deliver
- One written read in language a board, lender, or insurer can act on.
- Use for
- New ownership. Before a board or insurer review. Before a vendor renewal. After a near-miss.
Your installed package, from EPMS to switchgear automation to UPS or DRUPS, mapped item by item against who on your staff is trained to operate each piece. Plus the testability map: which hard tests can run safely on your topology, and which can't.
- Format
- Mostly remote. One on-site if records are thin.
- Deliver
- Gap report. Testability map. Named operator-pathway sequence. 90-day priority sheet.
- Use for
- Post-incident reconstruction. Post-acquisition orientation. Before a major maintenance season.
Two weeks. Principal on site. I build the operator pathway for your specific package: site-specific runbook, vendor-cert sequence (Niagara, Johnson Controls, Automated Logic, your actual stack), MOP set for the hard tests. We rehearse one failover or black-start under load. Your bench leaves knowing how to keep the receipts current.
- Format
- Two weeks. Principal-led. Mostly on site.
- Deliver
- Site runbook. MOP set. Rehearsed failover or black-start record. Report template.
- Use for
- Flagship sites. Sites out of a near-miss. Sites preparing for a major change.
The fractional director-of-operations-integration seat you didn't fund when you bought the package. Monthly cadence with your owner or VP. Quarterly walk-down on a rotating set of sites. An operator retention plan that competes with the hyperscaler twelve-month poach. One signed voice when your lender, insurer, or board asks who owns the full sequence.
- Format
- Monthly retainer. Standing call, quarterly walk-down, on-call for cutover decisions.
- Deliver
- Quarterly review. Monthly summary. Refreshed operator-pathway sequence. Retention playbook.
- Use for
- Portfolios scaling to multi-site. An open or doubled-up director seat. Lender oversight requirements.
For windows where the cost of a wrong call exceeds the cost of a principal physically present. Commissioning handoff. Post-incident recovery. Grid-architecture upgrade. New region stand-up. Principal on site weekly, in client meetings, in hiring decisions, in the buildout of your first dedicated operator.
- Format
- Monthly retainer with weekly on-site cadence.
- Deliver
- Daily walk-down log on-site. Weekly written to the owner. Live decision support. Transition plan at close.
- Use for
- Pivots where one wrong call costs more than a principal on site.
Worldwide, travel and expenses at cost. Principal-led every engagement. No associates. No program-team handoff.
Sign personally or within 14 days, or we pass. No enterprise procurement-cycle engagements.
What I don't sell: audits, assessments, compliance-tool resale, service software, generic technician training, or strategy decks.
You bought the system. You can still build the operator.
Fifteen minutes. I'll tell you in five whether I can help. I'll tell you straight if I can't.
Send the Operating Gap →
