| # |
Root cause |
How it creates a late availability |
Waterfront signals that it is happening |
Most common knock-on effects |
| 1 |
Growth work discovered after induction
Scope expands after inspections open up systems.
|
Hidden corrosion, legacy repairs, or undocumented alterations turn “planned work” into “new work.” Engineering packages and material must be created mid-stream, which pushes critical path tasks right.
|
“New CFRs” accelerating, rising shop backlog, added testing requirements, and more hot work or structural replacement than the baseline assumed.
|
Schedule compression
Overtime surge
Rework risk
|
| 2 |
Material not kitted when labor is ready
Late parts convert planned labor into idle time and resequencing.
|
Work starts, then stops because parts, gaskets, valves, cables, or long lead electronics are not on hand. The yard resequences, but resequencing creates interference and quality issues.
|
“Waiting on material” becomes the dominant reason for task slippage, heavy expedite activity, and cannibalization pressure across platforms.
|
Labor overruns
Critical path slip
Supply chain
|
| 3 |
Workforce gaps and skill mix mismatch
Not just headcount, also the wrong mix of certified skills.
|
The plan assumes stable availability of welders, electricians, pipefitters, NDT, QA, and test personnel. When shortages hit, tasks queue behind scarce specialists and late-stage testing backs up.
|
Overtime dependence, high turnover, backlog in inspections and test, and repeated “handoff delays” between trades.
|
Extended duration
Quality escapes
Training burden
|
| 4 |
Planning quality and sequencing realism
Plans that look good on paper but fail on interference and access.
|
If the work package sequencing ignores access constraints or system dependencies, the yard spends time undoing and redoing set-ups, or waiting for other work to clear.
|
Frequent schedule reshuffles, high constraint logs, trades stepping on each other, and repeated “cannot access” work stops.
|
Inefficiency
Late test starts
Cost growth
|
| 5 |
Quality escapes and rework loops
Rework is the silent schedule killer during closeout.
|
Small workmanship issues compound. Fixing them late often requires reopening boundaries, retesting, and re-inspecting, which consumes the exact time the schedule cannot spare.
|
Punch lists ballooning, repeated test failures, repeat discrepancies on the same systems, and delayed acceptance events.
|
Delivery delay
Labor overruns
Inspection load
|
| 6 |
Testing, trials, and certification bottlenecks
Late-stage pipeline gets clogged when earlier work slips.
|
When installation tasks slip, commissioning and test events compress. Specialized test teams, labs, and certification authorities become the bottleneck, and failures trigger retest cycles.
|
“Test window missed,” limited availability of test assets, late software loads, and system integration failures discovered late.
|
Closeout drag
Retest churn
Integration
|
| 7 |
Drydock and waterfront capacity conflicts
Ships queue when dock windows are scarce or shift.
|
If the dock plan changes, a ship can lose its window or be forced into pierside work that is slower for certain tasks. The knock-on effect is stacked schedules across multiple hulls.
|
Ships waiting for dock space, more pierside substitutions, and shifting start dates that push other ships behind them.
|
Queueing
Interference
Facilities
|
| 8 |
Contract change churn and late engineering
Change orders and late design packages slow execution.
|
New requirements or late engineering packages introduce negotiation time, design time, and material lead time. That pushes critical work into the closeout window.
|
Increased RFIs, delayed drawings, work “on hold pending” approvals, and rapidly growing change logs.
|
Stop start work
Late critical path
Engineering
|
| 9 |
Government furnished equipment timing
Shipyard ready, but key equipment arrives late or incomplete.
|
Some systems depend on externally provided equipment or software baselines. If delivery or configuration lags, the yard cannot close compartments and cannot complete final integration.
|
Waiting on racks, sensors, software baselines, or install teams, plus integration tests that slip because inputs are not stable.
|
Closeout stall
Retest
Integration dependency
|
| 10 |
Parts data rights and OEM turnaround dependence
When tech data is restricted, repair timelines follow vendors.
|
If maintainers cannot fabricate, reverse engineer, or competitively repair parts, lead times expand and repairs queue behind sole-source capacity.
|
Repeated delays tied to specific components, limited alternate repair options, and prolonged waits for OEM repair or replacement.
|
Extended lead times
Higher unit cost
Readiness drag
|
| 11 |
Availability scope not matched to time and funding
Planned work exceeds the real execution envelope.
|
When the planned package is too ambitious, something gives: tasks are deferred, the schedule slips, or labor overruns spike. If deferrals grow, future availabilities inherit the debt.
|
Deferment lists growing, increased “work not authorized” items, and frequent rebaselining of the plan.
|
Backlog growth
Schedule reset
Funding pressure
|
| 12 |
Operational schedule churn and late induction shifts
Changes in deployment needs can distort maintenance start and finish windows.
|
When operational demand moves, ships can arrive later than planned or be forced into compressed windows. That can reduce planning quality and increase growth work surprises.
|
Induction date shifts, shortened planning time, and more “must complete” work pushed late into the timeline.
|
Compression
Higher rework
Readiness tradeoffs
|
