Skip to main content

Data centers

A data center doesn’t fall behind during construction: it falls behind at handover

How to coordinate design, construction and commissioning when every day of delay comes at a price.

Roberto Rivera · · 5 min read

A data center can be 95% built and still be useless. The building is there, the equipment is there, and it still can’t take a single server, because it has yet to prove that everything works together: that the generators kick in when the power goes out, that the cooling holds up under load and that the control system sees what it needs to see.

That last stretch is called commissioning. I know it from a different kind of building: I spent years coordinating the handover to operations of ultra-luxury hotels and industrial plants. That’s where I learned that a project almost never stalls for lack of work. It stalls because someone is waiting on someone else, and nobody sees it in time.

In a data center the problem is the same, only more expensive.

What’s being built in Mexico

Mexico has 279 MW of data center capacity in operation, and 202 MW of it is in Querétaro, according to the 2026 report by the Mexican Data Center Association (MEXDC). That state alone has another 181 MW under construction, and the projects announced there through 2031 are expected to add 1,192 MW, with US$20.6 billion in direct investment (Expansión, October 19, 2026 (opens in a new tab), in Spanish).

Put another way: Querétaro alone plans to add, in five years, more than four times the capacity operating in the entire country today. A single campus announced in the state has six buildings and close to 1,000 MW of electrical capacity (Intelligent CIO, October 19, 2026 (opens in a new tab)).

That means many projects at once, with the same contractors, the same equipment suppliers and the same handful of specialists. Builders are no longer running a project: they’re running a portfolio.

Where it gets stuck

Data center commissioning is usually organized into five levels. The names vary with each owner’s specification, but the order is this (Archdesk (opens in a new tab)):

  1. Factory acceptance testing (FAT). Major equipment (UPS units, switchgear, generators, chillers) is tested before it ships.
  2. Site acceptance testing (SAT). The team checks that what arrived is what was tested, and that it was installed correctly before it’s energized.
  3. Pre-functional testing. Each piece of equipment starts up, runs, alarms and reports on its own.
  4. Functional testing. Each complete system is tested under controlled conditions.
  5. Integrated systems testing (IST). The whole building is tested as a single system, including a simulated utility outage.

Each level is the gate to the next. An open item from level 3 that nobody closed shows up as a failure at level 5, when fixing it costs a weekend of repeated tests and several days on the calendar.

What rarely gets said is that the gates don’t get stuck on tests alone. They get stuck on dependencies between people who don’t talk to each other every day:

  • The electrical contractor can’t energize because the control drawing isn’t approved.
  • The test team can’t go in because a calibration certificate is missing from the file.
  • Engineering won’t release a change because it’s waiting on an answer from the owner.
  • The equipment supplier already tested at the factory, but the report never reached the person who needs it on site.

None of these is a technical failure. They’re holdups. And on most projects they live in emails, in messages and in the coordinator’s head.

How I would coordinate it with CxOps

CxOps is the platform I built for that problem. It was born in hospitality and real estate development, and it hasn’t been used on a data center yet. What follows is how I would apply it, with what it does today.

One place for every project. CxOps has two platforms built on the same structure. Portfolio tracks the design deliverables: architecture, engineering and cost estimating, each with its status. Construction tracks every building system, from pre-commissioning to handover. Whoever is in charge sees every project in a gallery and drills into the one that’s in trouble.

Each company builds its own structure. In Construction, each system (medium voltage, generators, UPS, cooling, controls, fire detection) has its own tree, up to eight levels deep, with its subsystems and equipment. If the list already exists in Excel, you paste it in and the hierarchy is kept.

The five levels fit into three phases. Tests live in the app’s three handover phases: pre-commissioning, for each piece of equipment on its own; commissioning, for equipment integrated into its system; and handover, for turnover to the operator. Each test has its own code and group, and each company names its own groups: levels 1 to 3 fit as pre-commissioning groups, and levels 4 and 5 as commissioning groups.

What isn’t measured counts as zero. A system with no progress entered doesn’t show up as “awaiting update”: it shows up at zero. That way the project’s percentage isn’t inflated by work nobody has checked.

“Blocked by.” This is the piece that matters most here. When an item or a test can’t move forward, it’s marked as blocked, along with what it’s waiting on: a drawing, a study, a construction item, or something outside the platform, like a decision from the owner. The block stays in view of whoever has to clear it and whoever is in charge, with the number of days it has been stalled. Only the person who raised it can mark it resolved.

On a data center project, that answers the question that today takes a meeting to answer: what’s holding up the next gate, and who owns it?

Evidence next to every item. Factory reports, certificates and signed test protocols are uploaded to the item or test they belong to. Open issues are raised as tickets, which aren’t deleted: they’re resolved, and reopening one means writing down why.

The owner gets a view. The client, its commissioning agent or an auditor sign in as guests: they see only their projects, can’t change anything and have access until the date they’re given.

A report for leadership. Each project generates an executive report as a PDF, with progress and what’s blocked or overdue.

What CxOps is not

It doesn’t replace the commissioning agent or their test program. Specialized platforms already exist for running each level’s protocols, equipment by equipment, and data center owners usually require their own.

CxOps works one layer up. Those platforms answer whether a piece of equipment passed its test. CxOps answers why the test hasn’t started, who owns the open item and how many projects in the portfolio are in the same spot. And it works in both Spanish and English, so the builder, the contractors and the project management team who have to deliver can each work in their own language.

If you build data centers

I’m looking for the first companies willing to try it on a real project. If you build, oversee or coordinate data centers in Mexico, I’ll walk you through it in 20 minutes with a sample project, and you tell me where it doesn’t fit your operation.

← All articles