How Construction ERP Connects Data Center Power Strategy to Procurement and Schedule Certainty
On a hyperscale data center campus, the schedule can be effectively lost before a single foundation is poured, not because of labor, weather, or permitting, but because a transformer with a 65-week lead time wasn’t released before the topology was finalized. Contractors who consistently deliver these programs on time have stopped treating electrical planning as a downstream activity. The decisions made in the first few months of engineering design determine whether the project hits its energization window or spends the back half chasing it.
Utility Path Is the First Constraint
Most construction schedules, even today, typically open with sitework, structure, and enclosure. On a data center program, that sequence never governs the job anymore. A site can check every box, such as real estate, permitting, logistics, but can still fail as a delivery plan if the utility path can’t support the required IT load or energization window. Interconnection timelines can take 18 to 36 months in constrained transmission corridors. When the interconnection process does not start early, no amount of field execution can make up for the lost time in design or construction. Utility coordination and substation planning define the construction schedule before the first major design package is released.
Electrical One-Line Drives More Than Design Intent
Once the utility path is confirmed, the electrical one-line begins driving decisions well beyond the electrical scope. Distributed redundant and block redundant topologies are evaluated early in design to meet the owner’s requirements for uptime and availability, as these choices directly determine transformer quantities, duct bank configuration, feeder routing, and the sequence in which data halls can be energized. When electrical topology is revised after the submittals are returned and factory slots are assigned, the downstream impact can be significant. Experienced design teams treat the electrical one-line as one of the precursors with direct consequences for preconstruction, procurement, project controls, and commissioning planning.
Procurement Runs While Design Is Still Moving
This is where data center work separates sharply from typical construction projects. Switchgear, generators, transformers and protective relays don’t move through the market on the same timeline, and none of them wait for design to be complete. Switchgear lead times are currently running 52 to 65 weeks and Medium-voltage transformers from manufacturers are at 60 weeks or beyond. In a multi-phase data center campus with phased data hall energizations, the lead times of this electrical equipment must be mapped against the energization sequence before the procurement strategy is set.
The risk concentrates at the intersection of late design changes and the factory slots committed by the equipment manufacturer. When a decision is made to change the topology during design, it not only extends the design deliverable schedule but also requires revised submittals and new factory configurations from the manufacturer. After a slot is secured from the manufacturer, the lead time clock doesn’t restart from the original date; it restarts from the date the revised submittal clears review. Depending on the manufacturer and the extent of the revision, this can mean anywhere from 4 to 8 additional weeks of schedule delay for equipment already on the critical path.
Electrical Design Impacts Site Civil Work and Startup
Medium-voltage power distribution isn’t just an electrical item anymore; it also drives site utility design, including duct bank cross-sections and manhole placement. Design changes to feeder routing on a campus with grading disrupts subcontractor construction sequencing and creates pressure on a turnover path that was already tight.
Energization compounds the site coordination issue in other ways. Energization is a continuous multi-step process that includes functional checklists, acceptance testing, and staged energization by data halls. After that, integrated systems testing across UPS, switchgear, generators, and BMS must be completed before IT capacity is revenue ready.
What ERP Actually Needs to Do
ERP earns its place in these programs when it does one specific thing well: it closes the gap between a design decision and its consequences during construction. When a topology revision changes transformer quantities on a job with a 60-week lead time, the procurement team needs to know within hours, not when the revised drawing set clears review few weeks later. Equipment quantities, commitment status, delivery dates, and installation sequence must live in the same system and be updated in near real-time as design decisions evolve.
The teams getting this right aren’t just running ERP as a back-office accounting tool; they’re using it as an active risk surface, something the various team members, such as a project manager, procurement lead, and project controls team, are all watching when the design model shifts. ERP doesn’t replace document control, BIM/VDC coordination, or CPM scheduling. But when it’s doing its job, it prevents a drawing revision from becoming an unplanned cost and delay event that nobody saw coming.
The Critical Path Runs Through Decisions
The contractors winning repeat work on hyperscale data centers understand that the critical path on these jobs runs through decisions, not just activities. You can have the crew, the material, and the access, but still miss the energization window because an electrical coordination study wasn’t issued in time for relay settings to be programmed and tested. Managing that exposure requires more than just setting up a successful construction schedule. It requires a team structure in which the electrical design, procurement, and project controls teams all solve the same problem concurrently from the utility path conversation through the final turnover package. On programs where energization represents tens of millions of dollars of revenue per month, that integration isn’t a process improvement. It’s the delivery model.
Venkatesh Janakiraman, PE, is an Associate Principal | Electrical Engineer at LJC/Clayco, where he leads electrical design for data center and mission-critical programs in the design-build delivery model. Â
