Program Recovery And Re-Baselining

The following discussion illustrates a project that is well suited to the capabilities of an independent consultant in the Umbrex Shipbuilding & marine systems Practice. This is an illustrative example. Umbrex consultants adapt their methodology, timeline, and deliverables to the specific needs of each client.

1) Client Situation

A major program within the Shipbuilding & marine systems sector sought support to execute Program Recovery and Re-Baselining under the Program & Portfolio Management capability. The client managed a multi-ship build with complex combat systems integration, modular block construction, and stringent naval certification milestones. The program operated under a mix of cost-plus and incentive-fee CLINs with full EVMS applicability and DCMA surveillance. We engaged after the program’s baseline credibility had eroded and customer confidence was at risk.

Core pain points were concentrated across schedule integrity, cost control, engineering release, supply chain, and governance:

• Schedule performance had deteriorated, with Integrated Master Schedule (IMS) diagnostics revealing a Schedule Performance Index (SPI) of 0.84 at program level and critical-path slippage of key hull erection and combat system activation milestones. DCMA 14-point schedule assessment flagged excessive lags, missing logic ties, negative float concentration, and high duration tasks exceeding best practices.
• Cost performance fell below plan, with a Cost Performance Index (CPI) of 0.89 and negative Variance at Completion (VAC) at several Control Accounts. Material cost growth accrued from out-of-sequence work and expediting premiums on long-lead components such as gearboxes, shaft lines, controllable-pitch propellers, and radar arrays.
• Engineering and design release lagged the production need date. Model-based definition (MBD) packages, hull form updates, and cableway routing drawings experienced churn, driving rework. Engineering maturity KPIs showed lower than expected A/B/C-level drawing release completion and a rising Engineering Change Notice (ECN) backlog affecting work package readiness.
• Long-lead procurement slipped, with supplier schedules for gas turbines, diesel generators, switchboards, and VLS modules not synchronized to the rephased build plan. MRP pegging showed material availability conflicts for critical outfitting sequences, contributing to outfitting out-of-sequence and increased touch labor hours.
• Production execution occurred out of sequence across block fabrication, panel line, pre-outfit, and final erection, with capacity constraints at blast/paint and limited dry dock windows. Baseline Execution Index (BEI) tracked below 0.95, signaling systemic inability to complete planned work packages as baselined.
• EVMS governance gaps emerged. The Program Management Baseline (PMB) was misaligned to current scope and actuals; Control Account Plans contained aged Planning Packages; and Management Reserve (MR) drawdown increased without a clear tie to risk burn-down. IPMDAR submissions were inconsistent in coding and did not reconcile seamlessly to accounting actuals.
• Contractual commitments were at risk. Customer Integrated Baseline Review (IBR) actions remained open. Schedule margin was largely consumed. The program lacked a coherent strategy to pursue an Over Target Baseline (OTB)/Over Target Schedule (OTS) reprogramming consistent with DFARS and customer expectations.
• Operational and quality issues amplified variance. Nonconformance Reports (NCRs) spiked in compartment outfitting, cable installations, and HVAC integration; rework labor hours inflated Estimate-to-Complete (ETC). Factory Acceptance Tests (FAT), Harbor Acceptance Tests (HAT), and Sea Acceptance Tests (SAT) were not fully reflected in the IMS logic and resource-loading.
• Digital thread fragmentation hampered decision-making. Primavera P6 IMS, Deltek Cobra EV, SAP ERP, Teamcenter PLM, and ShipConstructor/AVEVA models were not fully integrated, causing lagging data synchronization and coding misalignment across WBS, OBS, and charge numbers.
• External oversight pressure intensified. DCMA surveillance findings cited EVMS process nonconformities; NAVSEA oversight teams requested a credible re-baseline plan; and classification society (ABS) and regulatory milestones required more robust forward planning, especially ahead of trials and certifications.

Selected underperforming KPIs tied to the Program Recovery and Re-Baselining scope included: SPI below 0.90 for three consecutive months; CPI below 0.95 across multiple control accounts; CPLI (Critical Path Length Index) below 0.9; BEI and Weighted Milestone Index trending below 1.0; drawing release readiness at 70% against a 90% target at start of pre-outfit; schedule margin reduced to less than 1% of remaining duration; and IPMDAR reliability issues flagged by data quality checks.

2) Project Objective

Primary objective: Execute a program recovery and re-baseline that restored schedule credibility and contractual alignment by diagnosing slippage and cost overruns, redesigning work packages, re-phasing long-leads, and establishing an approved PMB that supported realistic delivery and fee attainment.

Secondary objectives:

• Stabilize performance by improving schedule integrity (logic, float management, resource calendars) to enable achievable SPI trajectory and critical-path control.
• Rebuild cost forecasts via bottom-up ETC/EAC that integrated risk exposure, productivity assumptions, and supplier commitments to inform fee negotiations and funding profiles.
• Reinforce compliance through EVMS remediation aligned to ANSI/EIA-748 and customer IPMDAR requirements, enabling clean surveillance and IBR closeout.
• Reduce operational risk by redesigning work packages for buildable sequences, eliminating out-of-sequence execution, and aligning engineering release to production need dates.
• Restore customer confidence with a coherent OTB/OTS strategy and a Baseline Change Proposal (BCP) package reflecting contract modifications and CLIN-level re-phasing.
• Accelerate time-to-value through long-lead material re-phasing, supplier recovery plans, and executable dock/yard campaigns synchronized to dry dock windows and certification gates.
• Enable digital transparency using integrated dashboards and data architecture improvements across P6, Cobra, ERP, PLM, and MES for near-real-time variance analysis.
• Build internal capabilities by upskilling Control Account Managers, schedulers, and IPT leads on schedule risk analysis, BOE standards, and change control discipline.

3) Methodology and Approach

Workstream 1: Rapid Program Diagnostic and Control Account Triage

We conducted a comprehensive diagnostic to establish a fact base on schedule, cost, scope, and risk. Activities included:

• EV analytics using Deltek Cobra and IPMDAR datasets to segment performance by WBS element, ship hull, build zone, and IPT. We analyzed CPI/SPI trends, TCPI, VAC, MR usage, and trend breakpoints.
• DCMA 14-point schedule assessment on the IMS (Primavera P6) to quantify missing logic, leads/lags, high-float anomalies, long durations, and invalid dates. We supplemented with the DCMA “tripwire” checks for negative float and out-of-sequence progress.
• Schedule Risk Analysis (SRA) using Monte Carlo simulation to quantify P50/P80 durations and identify risk drivers on the critical and near-critical paths, focusing on block erection, machinery alignment, and combat systems integration paths.
• Cost risk review to test EAC reasonableness by triangulating bottoms-up ETCs, regression-based productivity models, and risk-adjusted parametrics for recurring versus non-recurring elements.
• Quality and rework mapping through NCR datasets and MRB logs to trace systemic defect modes (e.g., cable damage, incorrect penetrations, insulation rework) back to work package design and engineering release practices.

Stakeholders engaged: Program Manager, EVMS Lead, Master Scheduler, CAMs across Hull, Outfit, Electrical, and Combat Systems, Finance, and DCMA liaison. The diagnostic enabled targeted triage by control account, clarifying where re-packaging and re-phasing would yield risk reduction and faster stabilization.

Workstream 2: IMS/IMP Rationalization and Critical Path Reconstruction

We rebuilt schedule integrity to restore credible plan logic. Activities included:

• IMP/IMS alignment to contract deliverables and certification gates (ABS/NAVSEA) ensuring that key events like compartment completion, compartment certification, dock trials, HAT/SAT, and shock trials were logically and resource linked.
• Logic restructuring: reduced open ends, eliminated hard constraints where possible, and established mandatory logic ties for engineering release, material availability, and work package predecessors.
• Resource calendars and shift patterns aligned to actual yard capacities, considering crane availability, blast/paint booth constraints, test resources, and dry dock windows.
• Rebuilt schedule margin and buffer strategy by inserting schedule reserve at the program and major deliverable levels, with explicit governance for drawdown and replenishment.
• Defined schedule coding standards (WBS, OBS, CLIN, hull, zone, system, stage-of-construction) to drive traceability and dashboarding, and cleaned activity IDs/descriptions to reflect standard naming conventions.

Tools applied: Primavera P6, DCMA 14-point checklists, SRA software, and custom logic density and path convergence analytics. Outcomes were designed to support a credible critical path, improved CPLI, and reduced hidden criticality.

Workstream 3: Bottom-up ETC/EAC and BOE Standardization

We re-estimated remaining work with defensible assumptions:

• ETC development at the work package and planning package levels with CAMs, converting aged Planning Packages into time-phased Work Packages with clear entry/exit criteria and resource loading.
• Basis of Estimate (BOE) standardization using historical learning curves, touch labor norms by stage-of-construction, and quality-adjusted productivity factors informed by rework incidence.
• EAC scenarios: base, risk-adjusted (P50/P80), and stretch (with identified accelerators). We linked EACs to risk registers and to supplier commitments captured in Long-Lead Recovery Plans.
• Indirects and fee modeling at the CLIN level, reflecting shifts in overhead absorption due to schedule re-phasing and yard utilization.
• ETC/EAC governance: instituted review cycles, CAM validations, and finance reconciliation to the general ledger and IPMDAR formats.

Stakeholders: CAMs, Finance, Estimating, EVMS, and Contracts. This workstream underpinned a realistic PMB and enabled coherent negotiation positions for OTB/OTS and contract mods.

Workstream 4: Work Package Redesign and Production Re-sequencing

We redesigned work packages to enable buildable, right-first-time execution:

• Decomposed mega work packages into manageable, zone-based packages aligned to hull blocks, systems, and compartments, sequencing pre-outfit before erection to minimize out-of-sequence activity.
• Introduced prerequisite readiness gates: engineering release maturity, material kitting completeness, prerequisite inspections, and tool/test equipment availability prior to work start authorization.
• Applied lean principles and Theory of Constraints to balance production lines across panel line, sub-assembly, block assembly, and grand block erection, with takt-aligned beats where feasible.
• Established clear handoffs and quality verification points to reduce rework, using go/no-go criteria embedded in the MES traveler and the IMS.
• Refined trials and activation sequences to reflect realistic commissioning logic for propulsion, power distribution, combat systems, and C5I networks, avoiding parallel critical activities competing for shared resources.

Stakeholders: Production Management, Yard Superintendents, QA/QC, Test & Trials, Engineering, and Planning. The redesigned packages were structured to improve BEI, increase predictability, and reduce cumulative schedule risk.

Workstream 5: Long-Lead Material Re-phasing and Supply Chain Recovery

We addressed supply-driven criticality through supplier engagement and MRP realignment:

• Mapped long-lead items (e.g., gas turbines, reduction gearboxes, shafts and bearings, CPP hubs, switchboards, integrated mast structures, sonar domes) to the re-phased IMS, establishing need-by dates and dock campaign alignment.
• Negotiated supplier recovery plans with fixed delivery windows, prioritized allocations, and penalty/expedite frameworks where contractually viable. We sequenced FATs to align with new activation plans.
• Cleaned MRP pegging and BOM effectivity in ERP and PLM to reconcile material demand signals to updated work package dates and drawing revisions.
• Launched obsolescence and configuration audits for electronics and software, ensuring COTS item availability matched cyber and export compliance requirements.
• Integrated vendor schedules into the IMS as external dependencies with risk profiles and monitored through supplier S-curves and milestone trackers.

Stakeholders: Supply Chain, Strategic Sourcing, Engineering, Quality, and key suppliers. These actions supported reduced schedule exposure from material shortages and helped protect critical dock and activation windows.

Workstream 6: Governance, OTB/OTS Strategy, and Baseline Change Control

We instituted governance to formalize re-baseline changes and ensure compliance:

• Defined an OTB/OTS strategy, aligning program leadership and Contracts on thresholds, approvals, and customer engagement protocols consistent with DFARS and customer guidelines.
• Developed a Baseline Change Proposal (BCP) package documenting scope, schedule, and cost adjustments by WBS and CLIN, including justifications, variance narratives, and impacts to fee and incentives.
• Refreshed the Change Control Board (CCB) charter, delineating criteria for baseline changes, MR allocations, and undistributed budget controls, with routine performance and risk reviews.
• Prepared for an Integrated Baseline Review (IBR) with CAM briefs, control account documentation, and risk-informed narratives tying IMS logic, budgets, and technical scope.
• Aligned IPMDAR reporting with the new PMB, ensuring data compliance and timely submissions.

Stakeholders: Program Management, Contracts, EVMS, Legal/Compliance, DCMA/NAVSEA customer teams. Governance enforcement supported transparency, audit readiness, and stakeholder alignment.

Workstream 7: Digital/Data Enablement and Performance Transparency

We enabled decision-quality data across the toolchain:

• Integrated P6, Cobra, SAP/Oracle ERP, MES, and PLM via a standard coding schema (WBS/OBS/CLIN/hull/zone) and automated data pipelines into a curated data mart.
• Deployed executive and CAM-level dashboards for SPI/CPI, BEI, CPLI, path metrics, risk burndown, material availability, and drawing release readiness, with drill-through to work packages and NCRs.
• Implemented data quality controls: schedule logic validators, EV variance reasonableness checks, and cross-ledger reconciliation scripts to reduce IPMDAR rework.
• Embedded SRA capability and scenario modeling to evaluate re-phasing options and supplier slips in near-real time.

Stakeholders: PMO, IT/Data, EVMS, Master Scheduling, and functional IPTs. These actions were designed to shorten the insight-to-decision cycle and to sustain PMB integrity.

Workstream 8: Change Management and Capability Building

We built enduring capability to sustain the re-baseline:

• Trained CAMs and schedulers on BOE standards, ETC/EAC development, DCMA 14-point remedies, and SRA fundamentals.
• Rolled out a PMB maintenance playbook covering work authorization, baseline control, MR management, and IPMDAR reporting hygiene.
• Stood up cadence: weekly control account huddles, monthly risk reviews, and quarterly governance checkpoints with customer alignment.

Stakeholders: PMO, Functional Managers, HR/Learning, and Customer representatives where appropriate. The change management approach reinforced process discipline and improved accountability.

4) Data Request

To execute the program recovery and re-baselining, we requested a comprehensive dataset with defined horizons and granularity. Typical requirements included:

• Commercial/Contract:
  • Contract and modifications (CLIN structure, incentives, penalties, options), SOWs, CDRLs, and current IPMDAR CDRL instructions; time horizon: program-to-date plus future period; granularity: CLIN/WBS/SLPP level.
  • Customer correspondence, IBR minutes, DCMA surveillance reports, corrective action plans.
  • Baseline Change Proposals and CCB logs, MR logs, work authorization documents (WADs), and WBS Dictionary.
• Operational/Schedule:
  • Primavera P6 IMS with full resource-loading, calendars, codes (WBS/OBS/hull/zone/system), and baselines (current PMB, previous iterations); horizons: program start to completion; granularity: activity-level with logic and progress.
  • IMP with milestone definitions and entry/exit criteria; schedule margin policy and current reserves; SRA models if available.
  • Dry dock schedules, crane plans, facility capacity calendars, and test resource plans.
• Financial/EV:
  • Deltek Cobra datasets (budgets, earned value, actuals), prior IPMR/IPMDAR files, performance reports, and EACs; horizons: monthly status history for 12–24 months; granularity: control account/work package.
  • General ledger actuals by cost element (labor, material, ODC, overhead), rate decks, indirect pools; reconciliation rules between ERP and EVMS.
  • ETC/EAC support and BOEs, MR transactions, UB balances, and fee models.
• Technical/Engineering:
  • Engineering release plans and status by drawing/model package (A/B/C-level), ECN/ECO logs, and model maturity metrics; horizons: current and 6–18 month look-ahead; granularity: system/zone/package.
  • BOMs and effectivity states from PLM (Teamcenter/Windchill) and CAD/ShipConstructor/AVEVA; configuration baselines and change control records.
  • Interface control documents, software/hardware baselines, cybersecurity requirements affecting COTS procurement.
• Supply Chain/Long-Leads:
  • Supplier schedules and commitments for long-lead items; FAT/HAT plans; purchase orders, lead times, and delivery performance; horizons: item-level through ship-level delivery; granularity: PO line/MRB lot.
  • MRP demand/supply snapshots, pegging reports, exceptions, and shortages; warehouse inventory status and kitting completion.
  • Obsolescence watch lists, export control classifications, and specialty metals compliance documentation.
• Quality/Test:
  • NCRs, MRB decisions, defect taxonomy, rework hours, first-pass yield; test procedures and readiness reviews for dock/sea trials; horizons: historical and forward test schedules; granularity: compartment/system/test item.
• People/Governance:
  • Organization charts, CAM assignments, staffing plans, labor calendars, overtime policies; union agreements affecting shifts.
  • Governance artifacts: CCB minutes, risk registers, risk scoring criteria, mitigation plans; training records on EVMS/scheduling.
• Systems/IT:
  • ERP (SAP/Oracle) cost and procurement modules; EVMS (Deltek Cobra), scheduling (P6), MES (iBASEt/Siemens Opcenter), PLM/CAD (Teamcenter, ShipConstructor, AVEVA); data lake schemas and integration maps.
  • Data dictionary and coding standards (WBS/OBS/charge codes), data quality issue logs, and access protocols.

Common data quality pitfalls we addressed included: inconsistent WBS across systems; outdated calendars in P6; control accounts with mixed scope; lagging actuals in EV; improperly coded material actuals; misaligned drawing effectivity to BOM; orphan activities without predecessors/successors; and IPMDAR files with header mismatches and missing mapping to GL accounts.

5) Questions for Client

• What is executive leadership’s appetite for an OTB/OTS reprogramming, and what thresholds require customer approval under the current contract?
• Which contractual milestones and incentives are non-negotiable in timing or performance criteria, and where is there flexibility through contract mods?
• What fee protection or reopener clauses exist at the CLIN level that could be influenced by a re-phased PMB?
• How much schedule margin is leadership willing to carry at program and major deliverable levels, and what governance will manage its use?
• Which long-lead commitments are truly fixed (tooling started, NRE sunk) versus open to re-phasing without prohibitive penalties?
• What are the current DCMA surveillance findings, and which EVMS corrective actions are prioritized for closure in the next 90 days?
• What risk tolerance exists for concurrent engineering and production, and where must we enforce strict readiness gates to avoid compounding rework?
• What capital and working capital constraints apply to supplier recoveries, expediting, and facility capacity adjustments (e.g., additional shifts, temporary facilities)?
• Which facility windows (dry dock, blast/paint booths, test ranges) are immovable, and how should the IMS be anchored to these constraints?
• What is the customer’s preferred cadence and format for re-baseline dialogue, and who are the decision-makers on the government side?
• What data granularity is leadership prepared to sustain in IPMDAR reporting post-re-baseline, and how will exceptions be governed?
• Where do CAMs and IPTs see chronic out-of-sequence drivers, and what thresholds should trigger automatic work stoppage or resequencing?
• What is the organization’s readiness for SRA-driven planning, and what tooling and training investments are acceptable to embed this capability?
• What are the cybersecurity/export control constraints on alternative sourcing for COTS electronics, and how do those constraints influence re-phasing?
• What role should classification society and NAVSEA representatives play during re-baseline design to preempt approval risks?

6) Interview Guide for Subject Matter Experts

Program Manager

• Which milestones define success from the customer’s perspective, and where have past negotiations yielded flexibility?
• How have prior baseline changes been justified, and what narratives resonated with DCMA and customer program offices?
• What governance or cultural barriers most impede disciplined change control and work authorization?
• Where do you see the largest disconnect between IMS logic and how the yard actually executes?
• What decision gates would you add or strengthen to prevent out-of-sequence work?
• How do you prefer to balance schedule margin between program-level and deliverable-level reserves?

Master Scheduler/Planning Lead

• Which IMS areas fail the DCMA 14-point most frequently, and what are the root causes?
• How are calendars, resource constraints, and shift patterns maintained, and where do they diverge from reality?
• Which paths consistently become near-critical due to path convergence, and how have you mitigated them?
• What level of activity granularity best supports CAM control without creating noise or maintenance burden?
• How are supplier schedules integrated, and what is the lag from supplier change to IMS update?
• What is the current practice for SRA and how are results used to shape the plan?

EVMS Lead/Finance

• Where do EV actuals most often deviate from GL postings, and how do you reconcile differences?
• Which control accounts exhibit chronic variance and why (e.g., estimating errors, scope creep, productivity drift)?
• How mature are BOEs by work package, and where do we rely on top-down allocations?
• What is the current MR management philosophy, and how are allocations tied to risk retirements?
• How robust are ETC/EAC processes, and what evidence supports the current EAC credibility?
• What IPMDAR data quality issues recur and how have you addressed them?

Engineering/Design Authority

• Which systems or zones have the highest design churn, and what drives late changes?
• How do drawing release plans align with production need dates, and what are the gating criteria?
• Where are model-to-BOM effectivity mismatches causing material or installation rework?
• What is the engineering readiness definition for authorizing a work package start?
• How are interface risks managed across hull, outfit, electrical, and combat systems?
• What bandwidth exists to accelerate reviews or simplify design to reduce cycle time?

Supply Chain/Procurement

• Which suppliers and commodities dominate schedule risk, and what commitments are currently binding?
• How do you monitor supplier schedules and FAT readiness, and how quickly do updates reach the IMS?
• Where is obsolescence or export control most acute, and what are approved alternates?
• How effective is MRP pegging and exception management, and where are the biggest data integrity gaps?
• What levers exist for recovery (dual-sourcing, lot splits, managed inventory) within contractual bounds?
• Which material kitting processes consistently miss completeness targets?

Production/Yard Operations

• Where do you encounter the most out-of-sequence work, and what upstream conditions cause it?
• Which facilities and resources are chronic bottlenecks, and what workarounds are in use?
• How reliable are work package travelers and readiness checks in preventing rework?
• What realistic shift patterns and overtime levels can be sustained without driving quality issues?
• Which safety or certification constraints limit resequencing flexibility?
• How do trial preparations interact with ongoing outfitting, and where do conflicts arise?

Quality/Test & Trials

• Which defect modes drive the most rework hours, and where can prevention gates be inserted?
• How aligned are FAT/HAT/SAT plans with the IMS logic and resource allocations?
• What is the first-pass yield trend by system, and what are root causes of failures?
• How are NCRs fed back into planning and engineering to adjust work package design?
• Which certifications (ABS/NAVSEA) have longest lead approvals and highest retest risk?
• Where do you see opportunities to consolidate tests or combine inspections without increasing risk?

Contracts/Customer Liaison

• What customer positions are fixed versus negotiable regarding re-baseline and incentives?
• Which prior BCPs were accepted or rejected and why?
• What documentation and evidence are critical to support OTB/OTS approval?
• How should IPMDAR reporting evolve post-re-baseline to meet customer expectations?
• What is the optimal cadence for stakeholder briefings and decision checkpoints?

7) Timeline

We executed a 12-week plan structured into phases with clear outcomes and decision gates. The cadence balanced rapid stabilization with sufficient rigor to support customer-facing approvals.

• Weeks 1–2: Discovery and Mobilization
  • Onboarded with PMO and functional leads; confirmed scope, governance, and access.
  • Data ingestion from P6, Cobra, ERP, PLM, MES, and supplier portals; established data pipelines and quality checks.
  • Rapid interviews with Program Manager, Master Scheduler, EVMS lead, and selected CAMs to confirm pain points and priorities.
  • Decision gate: confirm OTB/OTS feasibility exploration and agree target re-baseline approval window with customer.
• Weeks 3–4: Diagnostics and Triage
  • Completed DCMA 14-point, tripwire, and CPLI analytics; conducted SRA to identify risk drivers.
  • EV segmentation by WBS/CLIN/hull/zone; identified red control accounts for immediate intervention.
  • Assessed drawing release maturity and material availability alignment to current IMS.
  • Decision gate: agree priority paths and control accounts for redesign; lock provisional coding standards.
• Weeks 5–7: Design of Re-baseline and Work Package Redesign
  • Reconstructed critical path and near-critical paths; inserted schedule margin policy and buffers.
  • Redesigned work packages with readiness gates, resource loading, and realistic durations; converted Planning Packages to Work Packages.
  • Developed bottom-up ETC/EAC scenarios and BOEs; aligned with finance and CAMs.
  • Drafted long-lead recovery plans and supplier re-phasing options; initiated supplier dialogues.
  • Decision gate: leadership review of candidate PMB, select preferred scenario, authorize BCP drafting.
• Weeks 8–9: Supplier Alignment and Contract/Governance Preparation
  • Negotiated supplier delivery windows and FAT schedules; integrated external dependencies into IMS.
  • Finalized BCP package including scope, schedule, cost changes, and rationale; aligned on OTB/OTS approach if required.
  • Updated IPMDAR mapping; prepared CAMs for IBR artifacts and narratives.
  • Decision gate: internal approval of BCP and OTB/OTS proposal; schedule customer workshops.
• Week 10: Pilot and Validation
  • Piloted new work package design and readiness gates on selected blocks/compartments to validate assumptions and cycle times.
  • Ran SRA against the candidate PMB; refined buffers and risk mitigations.
  • Decision gate: freeze PMB candidate pending customer approval; finalize training plans.
• Weeks 11–12: Customer Engagement, Governance Setup, and Handoff
  • Conducted customer workshops to review BCP and OTB/OTS; supported negotiation sessions as requested by client leadership.
  • Implemented PMB in EVMS and IMS; updated change control and cadence; launched dashboards.
  • Delivered playbooks, training, and handover of data pipelines; agreed post-implementation support checkpoints.
  • Decision gate: confirm re-baseline activation and commence performance tracking under new PMB.

Critical path items included supplier commitment realignment, IPMDAR data remediation, dry dock schedule locks, and CAM ETC/EAC validation. Decision gates centered on OTB/OTS posture, PMB scenario selection, and customer approval sequencing.

8) Deliverables

• Program Recovery Diagnostic Report
  • Comprehensive analysis of schedule integrity, EV performance, engineering maturity, material readiness, and risk drivers; includes DCMA 14-point results, SRA outputs, and control account heat maps. Used to align leadership on priority interventions.
• Reconstructed IMS and IMP Alignment Package
  • Updated Primavera P6 IMS with corrected logic, resource calendars, coding standards, and explicit schedule margin; crosswalk to IMP and contractual milestones. Enables credible planning and customer dialogue.
• Bottom-up ETC/EAC and BOE Compendium
  • Consolidated ETC/EAC scenarios with BOEs by control account/work package; includes productivity assumptions, rate decks, and risk-adjusted cases. Supports financial planning and negotiation positions.
• Work Package Redesign Playbook
  • Standard work package templates with readiness gates, entry/exit criteria, traveler content, and quality checkpoints; sequencing guidelines by stage-of-construction and system. Used by CAMs and production planners.
• Long-Lead Re-phasing and Supplier Recovery Plans
  • Item-level re-phasing for critical components with aligned FAT schedules and delivery windows; supplier commitments and contingency triggers documented. Integrates into IMS as external dependencies.
• Risk Register and SRA Model
  • Updated qualitative and quantitative risk registers tied to IMS activities; Monte Carlo SRA model with configuration to refresh monthly. Supports buffer sizing and mitigation prioritization.
• Baseline Change Proposal (BCP) and OTB/OTS Dossier
  • Formal BCP document with scope, schedule, and cost changes mapped to WBS/CLIN; variance narratives, fee and incentive implications, and supporting evidence; includes OTB/OTS strategy and approval workflow.
• EVMS Compliance and IPMDAR Reporting Blueprint
  • Process updates and artifacts to align with ANSI/EIA-748 and IPMDAR data specifications; reconciliation procedures to GL; surveillance readiness checklist. Reduces audit risk and rework.
• Performance Management Dashboards
  • Executive and CAM-level dashboards for SPI/CPI, BEI, CPLI, critical path, material readiness, engineering release, and quality; drill-down to work package and NCRs. Enables proactive management.
• Governance and Change Control Charter
  • Refreshed CCB charter, MR policy, PMB maintenance procedures, and cadence calendar; decision rights and escalation pathways. Institutionalizes discipline.
• Training Curriculum and CAM Toolkit
  • Modules on BOE, ETC/EAC, schedule quality, SRA, and IPMDAR practices; CAM job aids and templates; assessment to confirm proficiency. Builds internal bench strength.
• Customer Engagement Brief and Negotiation Aids
  • Concise summaries for customer stakeholders explaining re-baseline rationale, risk posture, and approval ask; scenario comparisons and talking points. Supports constructive dialogue.

9) Industry Insights

The Shipbuilding & marine systems market within Aerospace & Defense has faced unprecedented complexity, supply chain fragility, and oversight intensity. These dynamics informed how we executed Program Recovery and Re-Baselining.

• Market dynamics and backlog pressure:
  • Backlogs grew as fleets recapitalized, stressing capacity across hull fabricators, propulsion OEMs, and electronics suppliers. Multi-ship, multi-yard programs amplified interdependencies and resource contention.
  • Inflation and rate volatility complicated ETC/EAC credibility; material price variability for steel, specialty metals, and electronics elevated cost risk and drove the need for dynamic EAC updates.
• Technology shifts and digital shipyard:
  • Model-based enterprise practices expanded, but digital thread gaps persisted between PLM/CAD, ERP/MRP, MES, and EVMS. Effective re-baselining depended on harmonized coding schemes and near-real-time data orchestration.
  • Advanced analytics for schedule risk and EV trending became essential; organizations that embedded SRA into monthly cadence managed buffers more effectively and reduced surprise slippage.
• Ecosystem and supplier constraints:
  • Forgings, castings, and power electronics capacity constrained lead times for propulsion and combat systems. Supplier schedules required tight integration into IMS with explicit risk profiles and contingency plans.
  • Qualification and FAT capacities at OEMs created gating risks; aligning test resources and inspectors in re-phasing was as critical as aligning deliveries.
• Regulations and standards:
  • EVMS compliance, IPMDAR adoption, and DCMA surveillance tightened. Programs that codified strong PMB discipline, MR policy, and data quality checks navigated surveillance with fewer disruptions.
  • NAVSEA and ABS certification pathways demanded that IMS logic reflect true technical sequences and witness points; re-baselining that did not embed certification logic suffered approval friction.
  • Cybersecurity and export controls constrained alternative sourcing for COTS electronics; early legal/compliance engagement reduced late-cycle sourcing surprises.
• Buyer behavior and expectations:
  • Government customers increasingly insisted on transparent risk quantification, buffer policy, and meaningful IBRs. Credibility hinged on defensible BOEs, realistic ETCs, and consistent IPMDARs.
  • Program offices favored re-baselines that protected key capability delivery dates, even at the expense of interim milestones, when backed by clear risk mitigation and supplier commitments.
• What “good” looks like in program recovery and re-baselining:
  • Schedule quality meets or exceeds DCMA 14-point thresholds (e.g., minimal missing logic, limited leads/lags, few long-duration tasks), with CPLI near 1.0 and controlled negative float.
  • SPI/CPI within a narrow band (approximately 0.98–1.02) at the program level over multiple cycles, with BEI around 1.0+ and variance narratives that reconcile to BOEs.
  • Engineering release gates tied to production need dates, with late-change rates contained and drawing release readiness above 90% entering pre-outfit phases.
  • Long-lead material readiness synchronized to activation sequences with FAT schedules embedded, and material kitting completeness consistently at target before work authorization.
  • Risk-aware PMB with explicit schedule margins sized via SRA (e.g., P70 anchor for major milestones), and buffer consumption governed through formal policy.
  • IPMDAR submissions consistent, reconciled to GL, and stable following re-baseline, enabling constructive customer oversight and faster closure of IBR actions.
• Near-term disruptions and implications:
  • Persistent supply chain fragility in specialty components will continue to pressure schedules; integrating supplier SRAs and dual-sourcing strategies into the PMB will remain important.
  • Workforce availability and skill mix in yards may constrain ramp-up plans; realistic calendars and shift models should be embedded during re-baseline rather than assumed.
  • Digital thread maturation will differentiate programs; investments that align WBS/OBS/CLIN coding across P6, EVMS, ERP, PLM, and MES will pay back through higher data fidelity and faster decision cycles.
  • Increased emphasis on cyber and software assurance for integrated combat systems will add test complexity; incorporating these verification activities into IMS logic will reduce late-stage discoveries.

Across the Shipbuilding & marine systems landscape, Program Recovery and Re-Baselining served as a critical lever to restore credibility and align execution to reality. Effective engagements anchored on rigorous diagnostics, executable production sequences, synchronized long-leads, and disciplined governance. The approach described here reflected best practices tailored to the operational and regulatory contours of naval shipbuilding and marine systems integration.