Program Financial Control And EAC Forecasting

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

The client operated a complex, multi-ship defense program within a major U.S. shipyard, delivering hulls with extensive systems integration, phased block construction, and rigorous naval certification requirements. The finance function was accountable for program financial control and EAC forecasting across multiple contracts and CLINs, under a combination of FPIF, FFP, and cost-plus task orders. Earned Value Management (EVM) existed in pockets, yet lacked full integration with Estimate to Complete (ETC) and Estimate at Completion (EAC) processes. Change order quantification and management reserve practices varied by program, creating volatility in forecasted margin and revenue recognition under ASC 606. We were engaged to integrate EVM with ETC/EAC, quantify change orders with defensible methods, and manage contingencies to protect program margin and forecast accuracy.

Key pain points included:

• Forecast bias and volatility: The monthly LRE/LRFS process produced EACs that oscillated by more than the program governance threshold, indicating inconsistent ETC methodologies and insufficient linkages to schedule performance. CPI trended below 0.92 in critical control accounts, and SPI remained under 0.95 in outfitting and test phases, eroding confidence in the forward view of cost and schedule.
• Fragmented cost/schedule integration: BCWS/BCWP/ACWP data were not consistently aligned at the Control Account (CA) and Work Package (WP) levels. Primavera P6 IMS status lagged by 2–4 weeks relative to cost accruals, impairing timely Earned Value calculations and causing EVMS surveillance findings related to data latency and lack of schedule traceability.
• Change order leakage: Engineering Change Proposals (ECPs), Requests for Equitable Adjustment (REAs), and contract mods accumulated in an unpriced backlog. Quantification lacked standardized Basis of Estimate (BOE) templates and discrete mapping to WBS/CLINs, delaying recoveries and obscuring true Variance at Completion (VAC). Unauthorized scope creep from customer-directed work was not consistently captured through Baseline Change Requests (BCRs).
• Contingency and MR management gaps: Management Reserve (MR) allocation and usage policies were not consistently applied. Risk-adjusted EACs did not incorporate a top-down contingency philosophy, and risk registers were not quantitatively linked to cost/schedule risk models (Monte Carlo/CSRA), limiting Joint Confidence Level (JCL) insights for governance.
• Compliance exposure: EVMS practices did not fully meet ANSI/EIA-748 guidelines across all guidelines, and IPMDAR submissions contained data quality flags (e.g., missing logic ties, excessive constraints, high negative float, out-of-sequence work). DCMA 14-point schedule metrics indicated issues with long lags, high invalid dates, and use of hard constraints.
• Revenue recognition misalignment: ASC 606 percentage-of-completion and cost-to-complete calculations diverged from the EVM view, creating reconciliation complexity between program finance and corporate accounting. Progress payment liquidation schedules under DFARS clauses were not tightly integrated with cash forecasting.
• Supplier cost visibility: Material progress and accruals for long-lead items lacked timely three-way match and milestone substantiation. Subcontractor EV data were not standardized, limiting incorporation of supplier performance into program EACs.
• Data and tooling fragmentation: EV data lived in Deltek Cobra for some programs and spreadsheets for others; cost actuals resided in SAP/Costpoint; schedules in P6; engineering release data in PLM; and progress in MES. The absence of a harmonized data model and canonical WBS/WAD mapping led to reconciliation work and manual offline adjustments.
• Capability and cadence: CAMs followed varying variance analysis depth and ETC methods (e.g., CPI-based, bottoms-up, blended). Monthly Program Management Reviews (PMRs) consumed significant time in debating data integrity rather than driving decision-oriented actions.

Plausible underperformance manifested in KPIs tied to this scope:

• Forecast Accuracy: MAPE of monthly EAC vs. subsequent close-out estimates exceeded the governance tolerance, creating executive concern over predictability.
• Margin at Completion Stability: Program margin forecasts exhibited adverse drift correlated to late-stage rework in integration and test, with MR depletion occurring earlier than planned.
• EVMS Health: CPI persisted below 0.95 for critical WPs; SPI recovery plans lacked measurable burn-down logic; DCMA 14-point metrics flagged >10% activities without successors/predecessors.
• Change Order Cycle Time: Average cycle time from ECP receipt to mod execution exceeded 120 days, straining working capital and obscuring true program economics.
• Cash and Working Capital: Misalignment of progress payment liquidation with cost curves increased net cash exposure and complicated treasury planning.
• Data Timeliness and Quality: IPMDAR data submissions required rework due to inconsistencies, driving administrative burden and potential customer scrutiny.

2) Project Objective

Primary objective: We integrated Earned Value Management with robust ETC/EAC forecasting, quantified change orders with defensible BOEs, and instituted disciplined contingency management to protect program margin and raise forecast accuracy across Shipbuilding & marine systems programs.

Secondary objectives:

• Performance: We aligned EV, schedule, and production control to enable earlier identification of CPI/SPI inflections, accelerating corrective action planning.
• Economics: We standardized EAC methodologies and change-order quantification to support timely recovery of costs, fee protection, and improved cash visibility.
• Compliance: We strengthened adherence to ANSI/EIA-748 and IPMDAR requirements, reducing surveillance findings and submission rework.
• Customer impact: We improved transparency and credibility of program performance narratives for customer PMOs, facilitating constructive resolution of scope and funding matters.
• Digital/data enablement: We implemented a harmonized data model linking ERP, EVMS, P6, MES, and PLM, enabling automated EV/EAC calculations and dashboards.
• Capability-building: We upskilled CAMs and program finance in variance analysis, ETC methods, and claims quantification, embedding a consistent operating rhythm.
• Governance: We instituted a Baseline Control Board and PMR cadence with clear decision gates, integrating risk/contingency and MR usage policies.

3) Methodology and Approach

Workstream 1: EVMS and Baseline Diagnostic

We conducted an end-to-end EVMS diagnostic against ANSI/EIA-748 guidelines, focusing on the baseline integrity, cost/schedule integration, and variance analysis rigor. Activities included:

• Baseline traceability: We reconciled Contract Budget Base (CBB), Performance Measurement Baseline (PMB), and Undistributed Budget (UB). We tested mapping from CLIN/SLIN to WBS/CA/WP and verified that work authorization documents (WADs) reflected approved scope.
• Schedule quality: We assessed the Integrated Master Schedule (IMS) using DCMA 14-point metrics in Primavera P6, identifying logic gaps, leads/lags misuse, constraints, and high float activities. We traced schedule activities to EV WPs to ensure one-to-one or many-to-one traceability where fit-for-purpose.
• Earned value techniques: We inventoried EV methods (0/100, 50/50, percent complete, weighted milestones, apportioned effort, LOE) by WP and evaluated appropriateness given the shipyard’s block construction and outfitting sequences. We recommended shifts from LOE to discrete measures where feasible.
• Data latency and integration: We mapped the data pipeline from MES time bookings and GR/IR postings in ERP (SAP/Costpoint), through EVMS (Deltek Cobra), to IPMDAR outputs. We measured cycle time from cost incurrence to EV availability, flagging reconciliation pain points.
• Variance management: We assessed CAM variance narratives for root-cause clarity (rate vs. usage vs. mix), corrective action specificity, and linkage to schedule and risk registers. We observed PMR and CCB forums to evaluate decision efficacy.

Tools and stakeholders:

• Tools: Deltek Cobra/Open Plan, Primavera P6, SAP/Costpoint reports, SQL data extracts, DCMA 14-point assessment scripts, IPMDAR JSON validators, BI prototypes.
• Stakeholders: Program Manager, PP&C lead, EVMS director, Program Controller, CAMs, Engineering Change Control, Supply Chain Finance, IT data architects.

This workstream established the baseline health and specific control gaps shaping forecast accuracy, enabling targeted remediation and prioritization.

Workstream 2: EAC/ETC Method Standardization and Integration

We designed and implemented a standardized EAC/ETC methodology integrated with EV metrics and schedule risk, balancing top-down and bottoms-up approaches. Activities included:

• Method taxonomy: We codified acceptable ETC methods (e.g., bottoms-up by WP, CPI/SPI-based, CPIcapped, TCPI target, linear productivity models) and decision rules for where to apply each, given phase (hull fabrication, outfitting, test/commissioning), EV technique, and data maturity.
• Forecast algorithms: We configured EAC calculation variants (EACc = ACWP + (BAC − BCWP)/(CPI × SPIf), EACb = ACWP + ETCbu, blended EAC using weighting by data confidence). We defined TCPI to PMB and to EAC guardrails and included rate/mix deflators tied to learning curve assumptions for repetitive blocks and work centers.
• Schedule-coupled ETC: We linked ETCs to the statused IMS via remaining durations and resource-loaded activities where available. For non-resource-loaded schedules, we derived expected hours from productivity curves and S-curves tied to physical progress milestones (e.g., keel laying, launch, dock trials).
• Risk-adjusted EAC: We integrated cost/schedule risk analysis (CSRA) through Monte Carlo simulation, translating schedule slippage into cost growth via time-dependent overheads and disruption factors. We generated confidence curves (P10/P50/P80) and mapped them to contingency guidance.
• Revenue recognition alignment: We reconciled EACs with ASC 606 cost-to-complete measures, documented adjustments, and defined a monthly tie-out protocol between program finance and corporate accounting.

Tools and stakeholders:

• Tools: Deltek Cobra configurations, custom Python/R scripts for CSRA, P6 risk add-ons, BI dashboards visualizing CPI/SPI trends, TCPI, and EAC variants.
• Stakeholders: Program Finance, PP&C, CAMs, Corporate Accounting, Internal Audit, Program Manager.

This workstream created a common forecasting language, enabling consistent EACs, transparent assumptions, and stronger governance over forecast changes.

Workstream 3: Change Order and Claims Quantification

We designed a disciplined change management and quantification process to accelerate recovery of scope changes and protect margin. Activities included:

• Change taxonomy and intake: We clarified definitions for ECP, REA, UCA, and directed work; established intake channels; and implemented an interim log capturing date, driver, technical scope, affected WBS/CLIN, and funding status.
• BOE standards: We instituted standardized BOE templates with labor, material, ODC, and rate assumptions, explicitly tied to WBS/WP, with clear basis (historical actuals, CERs, vendor quotes, learning curves). We added disruption/impact factors where justified (interference, rework, access constraints).
• Time-phasing and EV: We mapped change scope into the PMB via BCRs, with discrete time-phasing for BCWS and selected EV techniques. We ensured segregation of changes from MR and prevented commingling with base scope.
• Commercial alignment: We aligned quantification with contract clauses (e.g., FPIF share ratios, ceiling price, progress payment liquidation, EVMS reporting requirements) and prepared negotiation packages with traceable source data.
• Claims dashboard: We developed a change order pipeline dashboard tracking value, probability, cycle time, and funding implications, linking to EAC scenarios with and without recovery.

Tools and stakeholders:

• Tools: BOE templates, cost estimating relationships (CERs), vendor bid comps, BCR workflow in PPM/ALM tool, CRM/contracting trackers, BI dashboards.
• Stakeholders: Contracts, Program Finance, Engineering Change Control, Supply Chain, Legal, Program Manager.

This workstream introduced discipline to quantify and integrate changes swiftly, supporting timely customer engagement and fewer surprises in EACs.

Workstream 4: Contingency and Management Reserve Policy with Risk Integration

We formalized contingency and MR practices to ensure risk-adjusted EACs and disciplined margin protection. Activities included:

• Policy design: We drafted a policy distinguishing MR (budget within CBB) from contingency (governance construct for risk-adjusted EACs), defining thresholds for allocation, approval levels, and usage documentation.
• Risk linkage: We integrated the risk register (technical, schedule, supplier, quality) with quantitative cost impacts and probability distributions. We ran Monte Carlo to derive contingency levels by WBS/control account and consolidated at PMB level.
• Trigger and drawdown criteria: We established triggers for converting identified risks into BCRs and MR usage, with evidence requirements (e.g., risk realized, scope increase, rate changes). We set drawdown cadences and reporting in PMRs.
• JCL and decision gates: We presented JCL views for program governance, relating contingency to P-level targets and aligning with customer expectations for confidence levels.

Tools and stakeholders:

• Tools: Risk register in ARM/Active Risk/Excel, Monte Carlo (e.g., @RISK, Crystal Ball), EVMS for MR logging, governance playbooks.
• Stakeholders: Program Manager, Risk Manager, Program Finance, PP&C, Executive Governance, Customer PMO as appropriate.

This workstream enabled a transparent, quantitative approach to contingency that aligned risk appetite with forecast confidence and margin defense.

Workstream 5: Data Architecture, Systems Integration, and IPMDAR Automation

We built a lightweight data architecture to integrate ERP, EVMS, scheduling, MES, and PLM, enabling automated EV and EAC calculations and compliant IPMDAR submissions. Activities included:

• Canonical data model: We defined a canonical WBS/OBS/CA/WP schema with crosswalks to CLIN/SLIN and cost elements (labor, material, ODC), standardizing codes across SAP/Costpoint, Cobra, P6, MES, and PLM.
• Data pipelines: We implemented ETL routines pulling ACWP from ERP, BCWS/BCWP from Cobra, status from P6, time bookings from MES, and engineering release status from PLM. We established daily/weekly refreshes aligned to monthly close and EV cutoffs.
• Quality rules: We codified validation rules (e.g., WBS existence, period cutoffs, double-booking prevention, accrual lag checks, schedule logic tests). Exceptions fed a data quality dashboard for PP&C and Finance review.
• IPMDAR automation: We configured automated generation and validation of IPMDAR JSON files, including performance data, format 7 time-phased information, and narrative linkage, reducing rework and cycle time.
• BI dashboards: We delivered role-based dashboards for executives, PMs, and CAMs, visualizing CPI/SPI, TCPI, EAC variants, MR status, change order pipeline, supply chain EV, and cash/progress payment views.

Tools and stakeholders:

• Tools: Data lake/warehouse (SQL), ETL tools, BI platform, Cobra APIs, P6 XER parsing, IPMDAR validators.
• Stakeholders: IT Data Engineering, PP&C, Program Finance, EVMS team, Corporate Reporting.

This workstream reduced manual reconciliation, strengthened data governance, and created a single source of truth for program financial control.

Workstream 6: Governance, Cadence, and Decision Rights

We refreshed governance structures and operating rhythms to institutionalize disciplined financial control. Activities included:

• Baselines and change control: We chartered a Baseline Control Board (BCB) defining membership, inputs/outputs, and approval thresholds for BCRs, UB distribution, and MR usage.
• PMR cadence: We redesigned PMR agendas to prioritize decision items, trend analysis, and corrective actions. We implemented a monthly forecast gate with lock dates and exception-based reviews.
• Decision rights: We clarified decision matrices for PM, Controller, PP&C, Contracts, and CAMs, detailing who approves ETC method selection, forecast changes beyond thresholds, and change order values.
• IBR readiness: We prepared artifacts for customer Integrated Baseline Reviews, including WADs, BOEs, variance analysis, and schedule logic narratives, de-risking customer interactions.
• Compliance and audit trails: We standardized documentation for EV calculations, forecast justifications, MR logs, and IPMDAR submissions to streamline internal/external surveillance.

Stakeholders included Program Leadership, Finance, PP&C, Contracts, Engineering, Supply Chain, and Quality, with executive oversight from the A&D portfolio office.

Workstream 7: Capability Building and Change Management

We invested in people and process adoption to ensure sustainability. Activities included:

• CAM training: We delivered training on EV techniques, variance analysis, ETC methods, and BOE development, including examples from shipyard fabrication, outfitting, and test phases.
• Finance upskilling: We trained program controllers on EAC variants, TCPI interpretation, ASC 606 alignment, and progress payment mechanics tied to DFARS clauses.
• Playbooks and SOPs: We produced step-by-step SOPs for monthly close, EV cutoffs, forecast gates, BCR processing, MR usage, and IPMDAR preparation.
• Change adoption: We ran working sessions to align stakeholders on why-so/what-so of process changes, identified adoption risks, and set reinforcement mechanisms (coaching, governance checks, KPIs).

This workstream built confidence and consistency across teams, anchoring the new ways of working in daily routines.

Workstream 8: Pilot, Validation, and Scale

We piloted the integrated approach on a live hull and a representative set of CAs across fabrication, outfitting, and test. Activities included:

• Pilot scope: We selected control accounts with known performance challenges and supplier content, ensuring a cross-section of EV techniques and schedule characteristics.
• Parallel run: We ran the standardized ETC/EAC alongside the legacy process for two cycles, comparing variance narratives, data quality, cycle time, and decision clarity.
• Refinement: We captured lessons learned, tuned algorithms (e.g., CPI caps, productivity curves), adjusted dashboards, and refined governance thresholds.
• Scale plan: We phased rollout to remaining hulls/contracts with a structured onboarding plan, training waves, and hypercare support.

This pilot de-risked wide-scale adoption and provided evidence for executives to proceed with enterprise rollout.

4) Data Request

To execute the project effectively, we requested the following datasets and artifacts, with clarity on horizon, granularity, and known pitfalls:

• Commercial/Contract:
  • Contract award documents, CLIN/SLIN structure, FPIF parameters (target cost/price, share ratios, ceiling), progress payment clauses, delivery milestones.
  • All contract modifications, UCAs, ECPs, REAs, and associated correspondence; change logs with dates and funding status.
  • Horizon: Contract-to-date; cadence: updated upon each mod; granularity: CLIN/SLIN and WBS mapping.
  • Pitfalls: Incomplete CLIN-to-WBS crosswalks; unlogged customer-directed changes; missing fee/FPIF calculations in change estimates.
• Operational/Schedule:
  • Current and historical IMS from P6 (monthly status), including calendars, coding structures, and resource assignments where available.
  • DCMA 14-point metrics and schedule health assessments; logic exception reports.
  • Horizon: From program start to current month; granularity: activity-level with relationships and constraints.
  • Pitfalls: Out-of-date status vs. cost actuals; activities with missing predecessors/successors; excessive constraints; misalignment between WPs and P6 activities.
• EV/Cost Performance:
  • Cobra/Open Plan data for BCWS/BCWP/ACWP by CA/WP, including time-phased PMB, MR logs, and UB.
  • IPMDAR data submissions (JSON and narratives) or IPMR legacy formats; data dictionaries for EV fields.
  • Horizon: At least 18–24 months of monthly status to support trend analysis; granularity: CA and WP level.
  • Pitfalls: Manual overrides; late accruals; EV technique inconsistencies; LOE masking discrete performance issues.
• Financial/ERP:
  • GL extracts for program WBS elements; job cost details; purchase orders; goods receipts; accruals; overhead/burden rates; rate forecasts.
  • Progress payment billing and liquidation schedules; revenue recognition (ASC 606) calculations; cash forecasts.
  • Horizon: Life-to-date and 12–24 months outlook; granularity: cost element level (labor, material, ODC) by WBS/CA.
  • Pitfalls: Incorrect cost element mapping to EV cost classes; timing differences between ERP and EVMS cutoffs; misposted charges.
• Technical/Engineering:
  • PLM release status (drawings, BOMs), engineering change logs, configuration baselines, and effectivity by hull/block.
  • Test and certification plans, inspection points, and rework logs.
  • Horizon: Current and prior two releases; granularity: part/block/system level with WBS linkages.
  • Pitfalls: Missing effectivity alignment to WBS; late engineering release impacts not reflected in schedule/EV.
• Production/MES:
  • Time bookings by work center and WP; productivity metrics; scrap/rework; queue times; station utilization.
  • Horizon: Rolling 12–24 months; granularity: daily/weekly by WP and work center.
  • Pitfalls: Offline hours not coded to correct WBS; lag in timecard approvals; rework coded as base scope.
• Supply Chain:
  • Supplier delivery schedules; milestone acceptance; EV data from major subs where applicable; open commitments; variance to PO.
  • Horizon: Contract-to-date and next 12 months; granularity: PO line/milestone level mapped to WBS/CLIN.
  • Pitfalls: Lack of standardized EV from suppliers; milestone ambiguities; late AP accruals.
• Regulatory/ESG:
  • EVMS system description; prior DCMA surveillance reports; corrective action plans; audit logs.
  • Compliance documentation for IPMDAR submissions; cybersecurity and export control constraints affecting data sharing.
  • Pitfalls: Incomplete closure of prior findings; limited documentation of variance narratives and CAM interviews.
• People/Governance:
  • Org charts, OBS, CAM assignments, RACI matrices for PMR/BCB/IBR; SOPs for EV, forecasting, and change management.
  • Pitfalls: Ambiguous decision rights; inconsistent SOPs across programs.
• Systems:
  • ERP (SAP/Costpoint) schema, EVMS (Cobra) configuration, P6 calendars/codes, MES data structures, PLM part/WBS mappings, data lake schemas.
  • Pitfalls: Nonstandard master data; differing WBS depth by contract; lack of APIs or ETL pathways.

5) Questions for Client

• What level of forecast confidence (e.g., P50 vs. P80) does executive governance require for EACs at the program and portfolio level?
• How do you define acceptable monthly EAC movement thresholds, and what approval levels are expected when thresholds are exceeded?
• Which ETC methods are currently sanctioned, and where do you see the greatest gaps in consistency or credibility?
• What is your policy for MR allocation and usage, and how is it differentiated from contingency in governance and reporting?
• How aggressively do you pursue change order recovery (ECPs/REAs), and what is your risk tolerance for submitting claims based on disruption/inefficiency?
• What are the current DCMA or customer surveillance findings related to EVMS/IPMDAR, and where is remediation most urgent?
• How are ASC 606 revenue recognition and progress payment liquidation integrated with program EV/EAC, and where do reconciliations regularly break?
• What decision rights do Program Managers, Controllers, PP&C, and Contracts have over baseline changes, forecast adjustments, and claim valuations?
• Which systems (ERP, EVMS, P6, MES, PLM) are authoritative for each data element, and what are the typical data latency windows?
• What supply chain visibility do you require from major subcontractors (EV data, milestones), and how is that data validated?
• What capital or OPEX envelope exists for tooling and data integration to automate EV/EAC and IPMDAR processes?
• Where are the bottlenecks in BOE development for change orders, and which functions are most constrained in bandwidth (CAMs, Engineering, Contracts)?
• What is your target operating rhythm for PMRs and forecast gates, and which decision gates should be added or retired?
• Which benchmarks matter most for executive reporting (CPI/SPI thresholds, TCPI to EAC, MR burn profile, change order cycle time)?
• How should we phase rollout across hulls/contracts to balance risk, customer scrutiny, and internal capacity?

6) Interview Guide for Subject Matter Experts

Program Manager

• Where has forecast volatility historically originated (engineering release, outfitting productivity, test rework), and how do you prioritize corrective actions?
• How do you determine when to convert risks into BCRs or request MR usage, and what evidence thresholds are practical?
• Which decisions at PMRs consume the most time, and what data or analyses would accelerate those decisions?
• How do you balance customer pressure for schedule compression with margin protection across FPIF/FFP/CP contracts?
• What governance friction points exist between PP&C, Finance, and Contracts regarding baseline control and change order strategy?
• Which suppliers drive the most cost/schedule risk, and how do you incorporate their performance into the program’s EAC?

PP&C / EVMS Lead

• Which EV techniques are most misapplied in your current WPs, and where can LOE be converted to discrete measures?
• How do you perform schedule status, and what are the recurring DCMA 14-point issues that require structural fixes?
• What is the current process for aligning P6 activities to WPs/CA, and where does traceability fail?
• How do you validate BCWS/BCWP time-phasing against the IMS, and what is the typical lag from status to EV availability?
• Which CAM variance narratives consistently lack root cause clarity, and how can the standard be raised?
• What is your approach to IPMDAR preparation, and where do JSON validation errors typically occur?

Program Finance / Controller

• How are EACs assembled today (tools, steps, approvals), and which components drive the most manual effort or subjectivity?
• How do you reconcile EAC with ASC 606 revenue recognition and progress payment liquidations each month?
• What is your current MR policy in practice, and where has MR drifted into covering base work instead of realized risk?
• Which cost elements (labor, material, ODC) exhibit the greatest variance vs. plan, and how do you separate rate vs. usage effects?
• How do you forecast indirect rates and apply them to ETC/EAC, particularly with volume changes across hulls?
• What is your current dashboarding capability, and which KPIs would materially improve executive decision-making?

Contracts / Commercial

• What is the pipeline of pending ECPs/REAs, and where do negotiations stall (scope definition, pricing basis, funding availability)?
• How do you structure BOEs for claims, and what documentation is most persuasive to the customer ACO/PCO?
• What FPIF mechanics (share ratios, ceiling) require careful modeling in change order pricing to avoid margin dilution?
• How do progress payments interact with program cash flow, and where do timing mismatches create working capital stress?
• What customer reporting expectations exceed contract language, and how do they influence baseline or EAC decisions?
• How do you handle directed but unpriced work to ensure timely capture and visibility in EACs?

Engineering / Change Control

• How quickly are design changes propagated through PLM, and what effectivity practices ensure clean mapping to hulls/blocks/WBS?
• Which engineering change drivers historically create downstream rework or interference during outfitting?
• How do you estimate engineering and downstream impacts in BOEs, and what empirical data supports disruption factors?
• What is the current throughput of ECR/ECO workflows, and where are the bottlenecks?
• How do you coordinate with PP&C to ensure schedule reflects engineering release realities?
• Which design maturity gates should trigger EAC method changes (e.g., shifting from CPI-based to bottoms-up)?

Production Planning & Operations

• What productivity metrics by work center most reliably predict ETC (e.g., hours per ton of steel, outfitting hours per system)?
• Where do layout and access constraints most frequently cause rework, and how are those captured in variance analysis?
• How do MES time bookings map to WPs, and what are common coding errors?
• How do you plan and sequence block construction and outfitting to minimize interference, and how is that logic reflected in P6?
• What operational risks (labor availability, learning curve disruptions, facilities constraints) should be explicit in the risk register?
• How do you measure and forecast rework hours to avoid masking LOE productivity in EV calculations?

Supply Chain / Subcontracts

• Which suppliers provide EV-like status, and how do you validate their milestone claims against physical progress?
• How do you forecast supplier ETC/EAC for major subsystems, and how is that integrated into the program EAC?
• What are the lead time and material inflation dynamics, and how are those captured in rate and usage assumptions?
• Where do accruals regularly miss delivery timing, creating ACWP/EAC distortions?
• How are configuration changes communicated to suppliers, and how do they handle equitable adjustments?
• What visibility do you have into supplier capacity and risk, and how does that inform contingency levels?

7) Timeline

We executed a 12-week plan, organized into phases with explicit outcomes, critical path items, and decision gates tied to Program Financial Control and EAC Forecasting.

• Weeks 0–1: Mobilization and Data Ingestion
  • Outcomes: Access to ERP/EVMS/P6/MES/PLM; approval of data request; alignment on scope (hulls/contracts).
  • Critical path: Data permissions; initial data model crosswalks; agreement on governance sponsors.
  • Decision gate: Confirm pilot scope and reporting expectations (IPMDAR cadence, PMR artifacts).
• Weeks 2–3: EVMS and Baseline Diagnostic
  • Outcomes: Baseline integrity assessment; DCMA 14-point schedule analysis; EV technique inventory and appropriateness review; data latency map.
  • Critical path: Extraction of historical EV and schedule status; CAM variance narrative samples.
  • Decision gate: Prioritized remediation backlog; agreement on EV technique conversions and schedule fixes.
• Weeks 3–5: EAC/ETC Method Design and Prototyping
  • Outcomes: EAC variants defined; ETC method taxonomy and selection rules; initial TCPI targets; risk-adjusted EAC concept; ASC 606 tie-out protocol.
  • Critical path: Productivity model calibration; rate/mix assumptions; schedule-resource linkage feasibility.
  • Decision gate: Approve EAC/ETC standard and confidence level targets (e.g., P50 vs. P80 use cases).
• Weeks 4–6: Change Order Quantification Framework
  • Outcomes: BOE templates; change intake process; BCR workflow; commercial modeling for FPIF/FFP; change order pipeline dashboard prototype.
  • Critical path: Contracts alignment on templates; engineering support for effectivity and impact estimates.
  • Decision gate: Approve use of disruption factors and documentation standards for claims.
• Weeks 5–8: Data Architecture and IPMDAR Automation
  • Outcomes: Canonical data model; ETL pipelines; data quality rules; automated IPMDAR file generation and validation; role-based BI dashboards.
  • Critical path: API availability; data quality remediation; mapping of WBS/OBS across systems.
  • Decision gate: Approve dashboards for PMR and executive reporting; finalize submission workflow.
• Weeks 7–9: Governance and Operating Rhythm
  • Outcomes: Baseline Control Board charter; PMR agenda redesign; decision right matrices; IBR readiness checklist.
  • Critical path: Executive availability; alignment across PM, Finance, PP&C, Contracts.
  • Decision gate: Ratify governance artifacts; confirm approval thresholds for forecast changes and MR usage.
• Weeks 8–10: Pilot and Parallel Run
  • Outcomes: Pilot execution on selected CAs/hull; comparison of new vs. legacy forecasts; refinement of algorithms and dashboards.
  • Critical path: CAM bandwidth; data cut alignment; pilot monitoring.
  • Decision gate: Approve scale-up plan and change management support.
• Weeks 10–12: Scale Plan, Training, and Handoff
  • Outcomes: Training delivery for CAMs/Finance; SOP/playbook finalization; rollout roadmap with milestones; hypercare plan.
  • Critical path: Training schedules; documentation sign-off; change champion network.
  • Decision gate: Confirm handoff and governance of continuous improvement backlog.

8) Deliverables

• EVMS Diagnostic Report
  • Contents: Baseline integrity findings; DCMA 14-point results; EV technique assessment; data latency map; prioritized remediation actions.
  • Use: Guides corrective actions to strengthen EVMS and enable credible forecasting.
• EAC/ETC Forecasting Standard and Model
  • Contents: Method taxonomy; algorithm definitions (CPI/SPI-based, bottoms-up, blended); TCPI guardrails; productivity curves; rate/mix assumptions; risk-adjustment approach.
  • Use: Serves as the single source for forecast methodology, ensuring consistent EACs across programs.
• Risk-Adjusted EAC and Contingency Playbook
  • Contents: MR vs. contingency policy; risk register linkage; Monte Carlo/JCL guidance; triggers and drawdown rules; reporting templates.
  • Use: Aligns governance with risk appetite and standardizes margin protection practices.
• Change Order Quantification Toolkit
  • Contents: BOE templates; CERs; disruption factor library; pricing models including FPIF mechanics; BCR workflow; negotiation package checklist.
  • Use: Accelerates defensible pricing, reduces leakage, and ensures timely integration of changes into PMB and EAC.
• Integrated Data Model and ETL Specifications
  • Contents: Canonical WBS/OBS schema; crosswalks to CLIN/SLIN; data lineage; validation rules; API/ETL specifications.
  • Use: Enables automated, auditable integration of ERP, EVMS, P6, MES, and PLM data.
• IPMDAR Automation and Compliance Pack
  • Contents: Automated JSON generation scripts; validation results; submission SOP; mapping of data to IPMDAR formats and narratives.
  • Use: Streamlines monthly customer reporting and strengthens compliance posture.
• Executive and PMR Dashboards
  • Contents: CPI/SPI trends; TCPI to PMB/EAC; EAC variants; MR status; change order pipeline; supplier EV; progress payment and cash views.
  • Use: Provides decision-ready insights and supports governance cadences.
• Operating Rhythm and Governance Charter
  • Contents: PMR agendas; forecast gates; decision rights matrices; BCB charter; IBR readiness checklist.
  • Use: Institutionalizes consistent decision-making and accountability.
• Training Curriculum and CAM/Finance Job Aids
  • Contents: Slide decks; hands-on exercises; variance analysis guides; ETC method selection flowcharts; ASC 606 tie-out procedures.
  • Use: Builds capability and accelerates adoption across CAMs and finance teams.
• Investment Roadmap for Tools and Data Enablement
  • Contents: Prioritized enablers (EVMS configurations, data lake, BI enhancements); cost/benefit profiles; implementation sequencing; risk mitigations.
  • Use: Informs capital and OPEX planning to sustain automation and analytics.
• IBR Preparation Package
  • Contents: WADs; BOEs; variance narratives; schedule logic explanations; MR logs; data pedigree documentation.
  • Use: Positions the program for constructive customer engagement during baseline reviews.

9) Industry Insights

Shipbuilding and marine systems programs in Aerospace & Defense face unique financial control challenges: long construction cycles, heavy systems integration, multi-CLIN contracting, and demanding customer oversight. Trends and dynamics that informed our work included:

• Evolving customer reporting: IPMDAR replaced IPMR, raising expectations for machine-readable performance data and faster cycle times. Buyers scrutinized data lineage, logic quality, and narrative coherence, creating a premium on automated, validated submissions.
• Heightened EVMS scrutiny: DCMA surveillance tightened around ANSI/EIA-748 compliance, particularly cost/schedule integration, variance analysis quality, and timeliness. Programs demonstrated stronger positions when they could show robust CA/WP traceability, schedule health, and consistent EV techniques.
• Contracting mix and risk: FPIF mechanics demanded precise modeling of share ratios and ceiling exposure, especially as change orders accumulated. Cost-plus work required disciplined allowable cost tracking and timely UCA conversions. Fixed-price elements elevated the stakes on early CPI deterioration, making TCPI a central management metric.
• Digital shipyard transformation: Integration across PLM, MES, ERP, EVMS, and P6 advanced but remained uneven. Best-in-class shipyards established canonical WBS and digital threads from engineering release through production and test, enabling more accurate EV and ETC modeling tied to physical progress.
• Supply chain volatility: Inflation, long lead times, and capacity constraints in major subsystems (propulsion, combat systems, electronics) increased material variance and schedule risk. Programs benefited from structured supplier EV inputs or milestone-based status to inform EACs and contingency.
• Labor and learning curves: Skilled labor availability constrained productivity in welding, pipe-fitting, and electrical outfitting. Programs that captured learning curve effects at the block level and reflected them in ETC methods achieved more stable EACs and realistic TCPI targets.
• Revenue and cash dynamics: Under ASC 606, cost-to-complete alignment with EV/EAC became crucial for consistent revenue recognition. DFARS progress payments and milestone billings shaped cash profiles; misalignment with cost curves created working capital swings that required better integration of financial and EV data.
• What “good” looked like: Leading programs operated with CPI/SPI centered near 1.0 and held within ±0.05 control bands, maintained EAC forecast bias within ±5% at the program level, kept MR above pre-agreed floors with disciplined use cases, executed change order cycle times under 60–90 days for standard ECPs, and sustained DCMA 14-point metrics within acceptable thresholds (minimal constraints, robust logic ties, manageable float).
• Near-term disruptions: Increased adoption of model-based systems engineering (MBSE) and digital twins promised better predictability of integration and test. Cybersecurity requirements constrained data sharing with suppliers, requiring secure APIs and role-based access. Inflationary pressure necessitated dynamic rate forecasting embedded in ETC/EAC methods.

Implications for clients in Shipbuilding & marine systems:

• Integrate data, not just processes: A canonical data model and automated pipelines are essential to keep EV/EAC synchronized with schedule and actuals, reducing manual adjustments and compliance risk.
• Codify ETC methods by phase: Apply different ETC techniques by hull/phase and data confidence, anchored in productivity analytics and schedule logic.
• Quantify and integrate change fast: Standard BOEs, disciplined BCR workflows, and FPIF-aware pricing protect margin and clarity in EACs.
• Manage contingency with evidence: Risk-adjusted EACs tied to CSRA and JCL provide credible governance and align executive risk appetite to program realities.
• Elevate CAM capability: Consistent variance analysis and method discipline from CAMs underpin reliable forecasts and constructive PMRs.
• Automate compliance: IPMDAR automation reduces rework and supports transparent customer engagement, reinforcing trust and facilitating resolution of issues.

By aligning financial control, EVM, and forecasting discipline with the realities of shipyard production and complex naval integration, Finance leaders in Shipbuilding & marine systems strengthened predictability and safeguarded margin, creating a sustainable foundation for execution and stakeholder confidence.