You've Already Planned Around Equipment That Wasn't Coming

You've Already Planned Around Equipment That Wasn't Coming

By John Crager, CMRP, SHRM-SCP | Next Shift Blog at WorkReady.works Published August 2026 | ~1,800 words | 8 min read

The vessel was fourteen months out.

Not fourteen months from fabrication start. Fourteen months from the day the PO cut, assuming the shop hit his own dates, which he wouldn't, and assuming the heavy haul permit cleared a route that crossed two counties and a bridge with a posted limit somebody was going to have to argue about.

Everything else on that job could move. Civil, structural, piping, electrical, insulation, scaffolding, all of it could be pushed, resequenced, double-shifted, or thrown more bodies. One item couldn't.

So you built the whole plan backward from a date you didn't control and couldn't buy your way out of. You found the float that was real and defended it for a year against every superintendent who wanted to borrow against it. You knew, in March, which slipped drawing was going to become a failed test in November. And when the shop finally called with the bad news, you had the recovery sequence roughed out before you hung up.

That's the job. Not the P6 file. The judgment underneath it.

Last week we made the case that data center work is infrastructure work, not tech work, and that the sector is actively recruiting out of oil and gas, utilities, mining, and the military. That post was for anybody in heavy industry. This one narrows to the people who plan, schedule, control cost, and coordinate the work, because there's a specific reason that group is in unusual demand right now.

The Skill Has a New Address

Data center construction is failing on execution, not on money.

The capital is not the constraint. Bloomberg reported in April that more than half of the U.S. data centers planned for 2026 are expected to slip or be canceled, with only about a third of this year's planned capacity actually under construction. Large power transformers that used to quote at twenty-four to thirty months now run three to five years. Grid interconnection queues have pushed past five (Bloomberg, 2026; DC Atlas, 2026).

Strip the industry off that and read it as a planning problem.

Fixed go-live date. One piece of equipment with a sixty-month lead sitting square on the critical path. Money that cannot compress the constraint. Multiple contractors converging on a facility that isn't finished when the building is standing, but when the systems have been tested, documented, and accepted by an operating group.

You have solved that. Repeatedly. It smelled like hydrocarbons and nobody wrote a Bloomberg story about it.

What Actually Crosses Over

The overlap is bigger than the vocabulary makes it look.

An integrated master schedule running design maturity through procurement, construction, testing, and turnover is a capital project schedule. Protecting energization, integrated systems testing, and go-live is protecting tie-ins, mechanical completion, and startup. Tracking a transformer with a four-year lead is tracking a reactor, a compressor, or a column with an eighteen-month fabrication window and a barge that only runs at certain river stages.

Contractor interface management, critical path and near-critical analysis, earned progress, change control, time impact analysis, cost and schedule integration, turnover package discipline. All of it moves across intact.

But the deliverables aren't what gets people hired. What gets people hired is the thing no software teaches and no course sells. Knowing when a schedule is green on the report and rotten underneath. Knowing which float is real and which is somebody's optimism. Knowing which risk deserves an executive in the room today rather than a line item in next month's variance report.

Mission-critical projects are short exactly that, and they know it. The labor shortage everyone writes about isn't only craft. It's the specialist bench: commissioning agents, controls people, high-voltage field talent, and the project controls professionals who hold a converging sequence together (Build, 2026).

What's Actually New

There's a real delta, and it's smaller than the postings imply.

The critical power path is theirs, not yours: utility service, substation, transformers, medium-voltage gear, switchgear, generators, UPS, transfer switches, distribution into the white space. So is the cooling path, meaning chillers, pumps, towers or dry coolers, CRAH and CRAC units, and the controls layer tying them together. The redundancy language matters because it drives sequencing and testing, so learn what N plus one, 2N, and concurrent maintainability change about an install order. Their commissioning ladder through integrated systems testing will feel familiar from startup work and sound foreign, since the names, gates, and documentation expectations are new. And modular delivery, where prefabricated electrical rooms and skids show up at a site that has to be ready the day the truck does, is a seam most heavy industry professionals have only touched the edge of.

Five topics. A few weeks of deliberate reading and conversation, not a credential program and not a career restart.

Sixty Days of Vocabulary Is the Whole On-Ramp

Nobody needs you to become an electrical engineer. You need enough fluency to read a project review package and know what you're looking at, plus enough vocabulary to ask a question that makes a hiring manager sit up.

Build a personal glossary and work it until it's automatic. Critical power path. Cooling path. White space and gray space. Long-lead equipment. Commissioning levels through integrated systems testing. Energization, mechanical completion, substantial completion, turnover, go-live. Redundancy tiers. Factory acceptance and site readiness.

Then trace the lifecycle end to end so you know where the pressure sits. Site and power, design and procurement, construction, energization, commissioning, turnover.

One insight in that sequence separates a credible candidate from a hopeful one. The project isn't done when the building is up. It's done when the systems are tested, integrated, documented, and accepted by operations. Anybody who has walked a unit back to startup already believes that in their bones. Say it in an interview using their words and you sound like somebody who's been there, because you have, just not there.

Don't Aim at the Hyperscaler First

Obvious target, worst opening move. Everybody applies there, the bar for prior mission-critical experience sits highest, and you'll be screened against candidates with three campuses behind them.

Go where the work actually lives. General contractors and EPC firms building the campuses. Owner's representative and program management shops. Engineering firms with a mission-critical practice. Commissioning providers, who are structurally short-handed right now. Electrical and mechanical specialty contractors. Modular and prefabrication suppliers. Colocation developers. And the utility, transmission, and power generation projects feeding the whole buildout, which may be the most natural landing spot of all for anybody carrying heavy industrial capital experience.

That route lets you learn the environment while still operating at a senior level, which beats taking a title cut to get a logo on your resume.

Build Proof, Not Interest

Everybody in that applicant stack says they're interested in data centers. Almost nobody shows up with something they made.

Build one sanitized artifact before you apply. A one-page milestone map for a hypothetical 50 to 100 MW build. A long-lead equipment risk register. A commissioning readiness map. Or the strongest of them, a single page showing how you'd recover after switchgear delivery slips ninety days.

Build that last one if you build nothing else. It answers the exact question the industry is currently failing to answer, and it puts your thinking on the table instead of your claims.

You aren't asserting you've delivered a hyperscale campus. You're showing how you'd think about theirs. Describe it in their terms and keep it precise, because a real number out of a refinery, a mine, or an LNG train carries further than any gesture at a data hall.

Lead with what you controlled, then translate: "I build and maintain integrated schedules for complex, safety-critical capital work, manage contractor interfaces and long-lead equipment risk, connect field progress to a defensible forecast, and support controlled commissioning and turnover. I'm now applying that discipline to mission-critical infrastructure."

Nothing in that sentence is a stretch. All of it is what they're short of.

The Bottom Line

Moving from a refinery, chemical plant, LNG facility, or pipeline into mission-critical infrastructure isn't a retreat from serious industrial work. It's a lateral move into another form of it, built around power, cooling, redundancy, speed, and disciplined execution.

The vessel that was fourteen months out taught you something the money in that sector cannot buy. How to build a credible plan around a constraint nobody can move, defend it for a year, and see the failure coming while there's still time to do something about it.

That's the skill. It travels.

Go learn their words for it.

Want the two-page Process Plants to Data Centers Transition Field Guide? Message me the word DATA CENTER and I'll send it over.

John Crager, CMRP, SHRM-SCP, is a heavy industry operations and planning professional with decades of experience in refinery and petrochemical environments. He is the author of Blue Collar Resume Mastery and Beyond Thank You for Your Service, available on Amazon, and writes about career navigation, credentials, and the future of the industrial workforce.

Follow the data. Trust the signal. Skip the noise.

→ Next in this series: Upskilling for the Energy Transition: What Skills Cross Over from Refining to Renewables

← Previously: You Scrolled Past It Because It Said Data Center