Shore power was never built to run your ship
Cold iron promises a clean, quiet pier. The standards that define it say otherwise, and the gap between what shore power provides and what a ship in repair actually needs is where the real costs hide.
NSTM Chapter 320 says it plainly: "The shore power system only has enough power to operate necessary machinery and provide lighting for habitability."¹ Not propulsion support. Not repair-period electrical loads. Habitability and necessary machinery. That single sentence, written into the Navy's own technical manual, is the whole argument for why so many pier-side power assumptions go wrong before a vessel ever ties up.
Shore power, in Navy parlance "cold iron," exists to let a ship shut down its own generators while alongside and draw electricity from the pier instead. The pitch is straightforward: quieter decks, no exhaust, lower fuel burn, less wear on shipboard machinery. All of that is true within the service's actual design envelope. The trouble starts when repair planners, estimators, or port engineers treat that envelope as broader than it is.
The standard everyone cites does not cover the case everyone means
IEC/IEEE 80005-1 is the governing commercial standard for high-voltage shore connection, and it is the document most people reach for when they want to talk about shore power authoritatively. It explicitly excludes power during dry docking and maintenance periods.² Read that again: the standard the commercial shipping world runs on does not address the ship repair condition at all.
That exclusion is not a drafting oversight. Dry dock and maintenance periods bring a different load profile entirely, one with welding sets, temporary lighting strings, portable ventilation, hydraulic power units, and test equipment cycling on and off in patterns that bear no resemblance to the steady hotel load 80005-1 was written around. A standard built for a vessel sitting quietly at a commercial berth cannot be assumed to cover a vessel torn open for repair work, because its own scope says it doesn't try to.
For a port engineer scoping an availability, this matters at the estimating stage, not after the fact. If the governing shore power standard disclaims the maintenance case, then whatever power arrangement gets used during that availability, whether it's shore power supplemented by portable generation, dedicated repair-period feeds, or something improvised, needs its own engineering basis. Citing 80005-1 as if it settles the question just moves the risk downstream to whoever discovers the gap during execution.
Hotel load is not repair load, and the numbers show why
The voltage figures reinforce the same point from a different angle. Pier nominal voltage runs 480V, ship nominal runs 450V, and the difference is a deliberate voltage-drop allowance built into the shore cable run.³ Note also that 450V is the distribution nominal aboard ship, while 440V is the utilization nominal, the voltage equipment is actually rated to see after internal drops. Three numbers, three distinct points in the system, each doing a specific job. Collapse them into one figure and the estimate built on top of it inherits the error.
None of this infrastructure was sized with repair-period loads in mind. It was sized, per NSTM 320, for necessary machinery and habitability lighting. A ship undergoing hull work, tank entry, or system teardown draws power in a completely different shape: intermittent, spiky, frequently exceeding what the habitability-era shore connection was ever asked to deliver. When that gap surfaces mid-availability, it does not show up as a clean line item. It shows up as a scheduling problem, a temporary power rental, or a fight over who scoped the deficiency.
When the shore side breaks, the cost is real and it is not small
Shore power infrastructure is aging Navy-wide, and the clearest data point is not naval but commercial: after the December 2023 storm damaged the Port of Hueneme's shore power system, the rebuild cost ran $30 to 40 million and took one to two years, during which ships at that port reverted to running their own diesels. The California Air Resources Board formally carved Hueneme out of its compliance dataset for the outage period.⁴
That is a commercial port, not a ship repair availability, and the distinction matters: different regulatory regime, different vessel mix, different failure mode. But the number is instructive because it is one of the only publicly documented instances where shore power unavailability comes with a price attached. It shows what happens when a system built to carry hotel load fails outright: the vessels underneath it do not go without power, they go back to diesel, and the infrastructure repair bill compounds on top of whatever fuel and machinery costs that reversion carries.
The Navy's own infrastructure investment pattern points the same direction. At Puget Sound Naval Shipyard, project P891 is increasing shore power capacity from 60 to 100 megavolt-amperes, a 67 percent jump, driven explicitly by Ford-class carrier power demand.⁵ That is a documented, funded admission that existing shore power capacity was undersized for the platforms the Navy is now bringing to the pier. It is the best-evidenced case of a Navy shore power shortfall being named and corrected, and it did not happen because someone wanted a nicer pier. It happened because the math stopped working.
Idle machinery has its own failure modes, and they are well documented
The flip side of the shore power question is what happens to the ship's own generators when they are not the ones carrying the load, or when they are run at low output because full hotel load isn't available from shore. Auxiliary engine load factor at berth runs 15 to 32 percent depending on vessel type.⁶ Set that against Caterpillar's own guidance, which treats 30 percent as a floor below which sustained operation causes problems, MAN's recommendation to load up the engine every second day if it's running under 20 to 25 percent load, and NTNU's formal definition of "low load" as anything under 40 percent.⁷
Below those thresholds, diesel engines do not simply idle harmlessly. The documented failure modes are wet stacking, carbon deposit buildup, liner polishing, turbocharger and exhaust fouling, oil dilution, and cylinder scuffing.⁸ Every one of those is a maintenance cost, and every one of them accrues quietly, off the fuel bill, off the shore power invoice, showing up instead as an unscheduled repair line months later. [VERIFY: whether MDEG's own repair scope data shows elevated rates of these specific failure modes on vessels with extended pier-side low-load generator operation.]
This is the real shape of the argument. Shore power's design limitation (hotel load only, no repair-period coverage) does not mean generators simply pick up the slack cleanly. If shore power is available but limited, and shipboard generators run at partial load to supplement it, or run intermittently because full shore capacity isn't there, the equipment absorbs wear that nobody priced into the availability. The debt does not disappear because it was not billed. It moves to wherever the low-load hours land.
What this means for the people scoping the work
For a port engineer building a repair availability plan, the practical takeaway is narrow but important: do not assume the shore power connection scopes the repair-period electrical load just because it exists at the pier. NSTM 320 tells you what it was built for, IEC/IEEE 80005-1 tells you what it explicitly does not cover, and the voltage figures tell you the system was engineered around habitability, not teardown work. If auxiliary generators are going to run at partial load during the availability because shore power cannot fully cover it, that is a machinery health decision, not a footnote, and it belongs in the maintenance risk register before the ship arrives, not after a liner shows unexpected wear.
The standards do not hide this. They state it directly. The gap only becomes a cost when nobody reads that far.
References
- NAVSEA S9086-KY-STM-010, Rev. 2 (NSTM Chapter 320).
- IEC/IEEE 80005-1:2019 Ed. 2.0.
- UFC 4-150-02; NSTM 320; MIL-STD-1399-300.
- Port of Hueneme; CARB 2024 enforcement data.
- NAVFAC Northwest, May 2025 (Puget Sound Naval Shipyard project P891).
- CARB hotelling methodology.
- Caterpillar 2013; MAN SL11-544; NTNU 2014.
- Caterpillar 2013; MAN SL11-544; NTNU 2014.