Shipyard Operating Model And Organization Design

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

We supported a shipbuilding and marine systems client that required a comprehensive redesign of the shipyard operating model and organization design. The mandate focused on establishing a program-centric matrix with integrated product teams (IPTs), clarifying design authority, optimizing spans and layers, and codifying role charters to accelerate decision-making and strengthen accountability. The yard was executing multi-vessel programs with complex systems integration, subject to naval/military standards and classification society requirements, and operating under Earned Value Management (EVM) oversight with Integrated Master Schedules (IMS). The current-state assessment revealed specific pain points across operations, engineering, program management, compliance, and digital enablement:

• Fragmented decision rights and unclear design authority between Naval Architecture, Systems Engineering, Production Engineering, and Waterfront Operations. Engineering Change Notices (ECNs) aged in the queue without a decisive Configuration Control Board (CCB) cadence, creating decision latency and impacting drawing release On-Time Delivery (OTD). KPI underperformance: Drawing release OTD trended below plan, and change cycle time exceeded program governance thresholds.
• Functional silos drove misalignment between Work Breakdown Structure (WBS) and Organizational Breakdown Structure (OBS), resulting in weak Control Account ownership and inconsistent EVM techniques across Control Account Managers (CAMs). KPIs underperformed: Schedule Performance Index (SPI) and Cost Performance Index (CPI) lagged baseline; variance at completion (VAC) lacked credible ownership.
• Spans and layers were inconsistent with heavy manufacturing benchmarks. Supervisory coverage varied widely by trade, with excessive layers in engineering and insufficient front-line supervision in hull, pipe, and electrical shops. KPIs underperformed: Supervisor-to-craft ratios spiked above target, labor productivity trended below baseline hours, and overtime percentage rose without corresponding throughput.
• Integrated Master Schedule logic was not consistently respected in shop dispatching and material kitting. Production control lacked a robust interface with MES, and material availability did not align with zone outfitting plans. KPIs underperformed: Schedule adherence by stage (block, grand block, unit, and final assembly) fell short; material availability at release-to-work gates showed frequent stock-outs and expedite rates increased.
• Program management routines and PMO governance were not anchored in a standardized cadence. CAM reviews, risk registers, and baseline change control occurred irregularly, reducing transparency and increasing replan frequency. KPIs underperformed: Action closure SLA slipped; the frequency of out-of-sequence work and rework hours increased; nonconformance reports (NCR) remained open beyond quality management targets.
• Role ambiguity blurred the lines between Design Authority and Production Engineering. Model-based definition (MBD) policies were not enforced consistently in PLM, leading to late-stage engineering clarifications and drawing revisions during fabrication. KPIs underperformed: First Article Inspection (FAI) acceptance lagged, and the number of engineering queries from the shop floor exceeded norms for mature programs.
• Supplier and long-lead management lacked a clear RASCI and escalation path within the program-centric structure. Engineering-to-procurement handoffs were inconsistent, resulting in incomplete or non-standard technical data packages (TDPs). KPIs underperformed: On-time supplier readiness at need date fell; late change incorporation rate rose; cost of poor quality attributed to suppliers impacted margins.
• Quality, safety, and compliance governance were functionally sound but disconnected from program cadence. ABS/NAVSEA hold points, ISO 9001 processes, and CMMC/DFARS cybersecurity requirements were handled centrally, creating bottlenecks in program execution. KPIs underperformed: Audit finding closeout cycle times extended; repeat findings emerged; test and trials defect backlogs grew as commissioning approached.
• Digital thread gaps across PLM, PDM, ERP/MRP, and MES reduced data fidelity for IPTs. Configuration items in PLM were not consistently synchronized with ERP item masters and MES routings, hindering status-at-a-glance dashboards. KPIs underperformed: Data reconciliation efforts increased; dashboard refresh latency was high; CAMs lacked real-time earned value visibility at the control account level.
• Change saturation in the workforce, combined with union constraints and skill shortages in key trades, made it difficult to adjust staffing and leadership spans. Training on new processes and CAM responsibilities was ad hoc. KPIs underperformed: Training completion rates were uneven; onboarding time for new supervisors lengthened; near-miss and TRIR trends showed variability amid operational stress.

2) Project Objective

Primary objective: We designed and implemented a program-centric matrix operating model for the shipyard, anchored by integrated product teams and a formal design authority, with optimized spans and layers and role charters that clarified decision rights and accelerated accountability across engineering, production, and program management.

Secondary objectives:

• Performance: Align WBS, OBS, and IMS to enable credible EVM performance at the control account level and strengthen schedule realism through integrated planning, risk management, and configuration control.
• Economics: Streamline supervisory layers and rebalance spans to reduce overhead drag, improve labor productivity, and improve shop throughput without prematurely expanding headcount.
• Compliance: Embed NAVSEA/ABS hold points, ISO 9001 quality processes, DFARS/CMMC cybersecurity, and EVMS requirements into the program governance model, CCB cadence, and PMO routines.
• Customer impact: Improve drawing release OTD, supplier readiness, and waterfront execution to protect contractual milestones, trials readiness, and acceptance events.
• Digital/data enablement: Define the digital thread for IPTs by role, integrating PLM, MES, ERP/MRP, and project controls to provide single-source-of-truth dashboards and configuration status accounting.
• Capability-building: Develop role charters, RASCI, training curricula, CAM standards, and leadership routines that institutionalized the program-centric model and sustained decision velocity.
• Risk reduction: Establish a disciplined CCB, baseline change control, and programmatic risk management that reduced unplanned churn, rework, and out-of-sequence work.

3) Methodology and Approach

We executed an Organization capability project centered on “Shipyard Operating Model And Organization Design,” segmented into coordinated workstreams to diagnose current-state challenges, design the future-state matrix, and enable adoption with governance and digital integration. Each workstream tied explicitly to decision speed, KPI integrity, risk reduction, and time-to-value acceleration.

Workstream 1: Operating Model Blueprint and Decision Architecture

• Activities conducted:
  • Mapped end-to-end value streams from concept design through construction, commissioning, and trials, identifying decision choke points, handoffs, and queues affecting drawing release and waterfront execution.
  • Defined the future-state program-centric matrix spanning IPTs organized by product (hull, outfitting, electrical, HVAC), zone, and system, aligned to the Contract WBS and product breakdown structure.
  • Codified decision rights using a decision architecture (e.g., RAPID-style taxonomy) differentiating Recommend, Approve, Perform, Input, and Decide roles, with a focus on Design Authority, CCB, and PMO baselines.
  • Designed the Program Management Office governance model, including cadence for Program Reviews, CAM Reviews, Risk Review Boards, and CCB meetings aligned to IMS milestones and Stage Gates (SRR, PDR, CDR, TRR).
• Tools/frameworks used:
  • RACI/RAPID decision matrices, value stream mapping, responsibility modeling, operating model canvas, and governance charters for CCB and PMO.
  • Integration with EVMS constructs to tie decision rights to cost/schedule change control and baseline integrity.
• Stakeholders involved: CEO/yard GM, COO, Program Directors, Chief Engineer, PMO lead, Head of Quality, Supply Chain Director, CHRO, and IT/OT leadership.
• Link to outcomes: Clarified authority and codified governance were designed to reduce decision latency, strengthen configuration control, and improve CPI/SPI credibility through timely, accountable decisions.

Workstream 2: Spans & Layers Assessment and Organization Sizing

• Activities conducted:
  • Built a detailed current-state organization model across functions (Engineering, Production, Supply Chain, Quality, PMO, Finance, IT) and programs, including role inventories, job families, and leadership levels.
  • Quantified spans and layers by area (shops, waterfront, engineering), benchmarked against heavy industrial and defense manufacturing norms, and ran scenarios to reduce unnecessary management layers.
  • Analyzed supervisor-to-craft ratios by trade and shift, including foreman coverage in steel, pipe, and electrical, to rebalance front-line leadership and improve shop floor control.
  • Developed an organization sizing model by phase gate and vessel lifecycle, flexing IPT staffing by workload (IMS logic, earned value burn rates, and design release curves).
• Tools/frameworks used:
  • Org modeling and spans-and-layers analytics, activity-based time allocation for leaders, and scenario planning for supervisory ratios and functional consolidation.
  • WBS-to-OBS mapping to ensure each Control Account had a clear owner in the new matrix.
• Stakeholders involved: CHRO, Production leadership, Chief Engineer, PMO, Finance/EVMS analysts, and Union/Works Council representatives as applicable.
• Link to outcomes: Right-sizing and layer rationalization were designed to reduce overhead friction, strengthen front-line supervision, and improve throughput without compromising compliance.

Workstream 3: Integrated Product Teams (IPTs) and Role Charters

• Activities conducted:
  • Defined IPT topology by product/zone/system with embedded disciplines: Program Management, Systems Engineering, Production Engineering, Quality, Supply Chain, and Waterfront Operations.
  • Authored role charters for IPT Leads, CAMs, Design Authority Delegates, Production Supervisors, Material Controllers, and Supplier Quality Engineers, including decision rights and key interfaces.
  • Established Control Accounts and work packages aligned to IMS logic and EVMS guidelines, including objective earned value techniques and percent-complete rules by task type.
  • Drafted IPT ceremonies and routines: week-ahead planning, constraint removal stand-ups, cross-functional design reviews, and CCB pre-briefs to synchronize engineering, procurement, and fabrication.
• Tools/frameworks used:
  • Role charter templates, RASCI matrices, standard work for IPT routines, and CAM playbooks covering variance analysis, estimate-at-complete (EAC) practices, and baseline change control.
  • WBS dictionary enhancement to align technical scope with financial control.
• Stakeholders involved: IPT Leads, CAMs, Engineering discipline leads, Production Superintendents, Supplier Quality, and PMO.
• Link to outcomes: Clear charters and standard IPT routines were designed to increase decision velocity, reduce rework, and promote schedule integrity through synchronized engineering and production.

Workstream 4: Design Authority and Configuration Management

• Activities conducted:
  • Clarified Design Authority ownership from concept through as-built, formalizing technical baselines and change thresholds requiring CCB approval versus delegated authority.
  • Integrated model-based systems engineering (MBSE) and model-based definition (MBD) practices into PLM workflows, including configuration item structures, revision control, and digital sign-offs.
  • Defined CCB membership, agenda, inputs, and outputs, linked to IMS milestones and EVMS baseline impacts, ensuring change provenance and traceability.
  • Aligned classification society and customer requirements (e.g., ABS/NAVSEA) with configuration audits and technical data package (TDP) readiness criteria.
• Tools/frameworks used:
  • Configuration status accounting templates, change impact assessment protocols (cost/schedule/risk), and digital traceability within PLM/PDM.
  • Design freeze calendars synchronized with procurement lead times and build sequence.
• Stakeholders involved: Chief Engineer/Design Authority, Systems Engineering, Configuration Management, PMO/Program Controls, Quality, and Supply Chain Engineering.
• Link to outcomes: Formalized design authority and disciplined CCB were designed to curtail late changes, protect the build sequence, and improve drawing release OTD and FAI readiness.

Workstream 5: PMO, EVMS, and IMS Integration

• Activities conducted:
  • Redesigned PMO processes to standardize CAM reviews, variance analysis, risk and opportunity management, and baseline change control, integrated with weekly IPT routines.
  • Rebased selected schedules to remove unrealistic float and align logic with shop constraints, crane availability, dry dock windows, and material readiness.
  • Established a tiered governance model: Program Reviews (monthly), IPT Reviews (weekly), and daily execution control boards, each with specific metrics and escalation paths.
  • Enhanced EVMS data quality through control account mapping, coding discipline, and earned value technique standards appropriate to engineering, fabrication, and test tasks.
• Tools/frameworks used:
  • IMS health diagnostics, schedule risk analysis inputs, EV techniques catalogs, variance analysis standards, and risk registers integrated with EAC processes.
  • Dashboard specifications for CPI, SPI, critical path adherence, change burn-down, and cumulative flow across engineering and production work centers.
• Stakeholders involved: PMO, Program Managers, CAMs, Finance/EV Analysts, Production Planning & Control, and IT data teams.
• Link to outcomes: Integrated PMO routines and consistent EVMS practices were designed to increase plan credibility, sharpen risk visibility, and stabilize baseline performance.

Workstream 6: Production Operations Interface and Material Flow

• Activities conducted:
  • Mapped MES/ERP/PLM interfaces to ensure routings, work instructions, and configuration status were synchronized with engineering releases and procurement milestones.
  • Established week-ahead and day-of execution controls linking dispatching with constraint management (labor, cranes, bays, material, test equipment) and designed escalation protocols.
  • Clarified handoffs between Production Engineering and shop supervision, including weld procedures, fit-up tolerances, and system test prerequisites.
  • Aligned SIOP with program needs, validating long-lead materials planning, supplier readiness reviews, and kitting triggers tied to drawing maturity gates.
• Tools/frameworks used:
  • Constraint-based scheduling, kitting readiness scorecards, digital work instruction templates, and Andon-style escalation mechanisms.
  • Waterfront visual management standards and takt-aligned milestones for critical zones.
• Stakeholders involved: Production leadership, Production Engineering, Materials Management, Supplier Quality, and IT/OT.
• Link to outcomes: A synchronized production interface was designed to reduce out-of-sequence work, stabilize material availability, and protect IMS critical path activities.

Workstream 7: People, Change Management, and Capability Build

• Activities conducted:
  • Built a comprehensive change plan addressing leadership alignment, communications, training, and union/works council engagement, sequenced with decision gates and milestone reviews.
  • Developed competency models and training curricula for IPT leads, CAMs, supervisors, and engineering managers, including decision-making, EVMS, and configuration management.
  • Established leadership routines (tiered meetings), performance dialogues, and coaching mechanisms to reinforce new behaviors and decision rights.
  • Migrated job architecture and titles to align with role charters; defined selection criteria for IPT lead roles and clarified succession plans.
• Tools/frameworks used:
  • Stakeholder heat maps, readiness assessments, communications plans, and training effectiveness measures.
  • Behavioral anchors for leadership standards and performance management alignment.
• Stakeholders involved: CHRO, Learning & Development, Program Leadership, Union representatives, and Communications.
• Link to outcomes: Capability building and reinforcement routines were designed to embed the operating model, reduce change fatigue, and sustain decision velocity.

Workstream 8: Digital Enablement and Data Architecture for IPTs

• Activities conducted:
  • Defined role-based data access across PLM, MES, and ERP to reflect new decision rights and ensure configuration integrity, including CCB workflows and sign-offs.
  • Specified integration requirements for dashboards that combined EVMS data, IMS milestones, engineering release status, and material readiness at the control account level.
  • Identified data quality remediation steps: coding discipline for WBS/OBS, reconciliation of item masters and BOMs, and timestamp alignment for lead/lag analysis.
  • Developed minimum viable analytics for IPT stand-ups and Program Reviews, including change burndown, aging of ECNs, and supplier readiness indices.
• Tools/frameworks used:
  • Data dictionaries, role-based access control (RBAC) matrices, KPI trees, and dashboard specifications.
  • PLM-PDM-ERP-MES integration maps to support digital thread and configuration status accounting.
• Stakeholders involved: IT enterprise architects, Data governance leads, PMO analysts, Engineering systems admins, and Production control.
• Link to outcomes: Digital enablement was designed to provide single-source-of-truth for IPTs, reduce manual reconciliations, and improve timeliness of decision-making data.

4) Data Request

To execute this Organization project in Shipbuilding & marine systems, we assembled a comprehensive data request to ensure traceability from the operating model through program performance and compliance. We specified time horizons, granularity, and typical data quality pitfalls to preempt delays.

• Commercial and program data:
  • Contract scope, CDRLs, WBS dictionary, Contract WBS/OBS mapping, and key milestones (SRR, PDR, CDR, TRR, trials, delivery).
  • IMS with full logic and resources for the last 24–36 months and current forward plan, weekly or bi-weekly status granularity.
  • EVMS datasets for the past 18–24 months: BCWS, BCWP, ACWP, CPI, SPI, variance narratives, EACs, baseline change logs.
  • Program risk registers, opportunity registers, and mitigation plans with dates and owners.
• Operational data:
  • Production schedules by area/zone, shop dispatch lists, rework logs, out-of-sequence work records, and constraint logs (crane, bay, manpower).
  • Material readiness reports: kitting status, shortages, expedites, supplier OTIF, and long-lead tracking for 18–24 months.
  • Engineering release plans: drawing registers, 3D model maturity, ECN logs, change aging, and release OTD for the last 12–18 months, weekly granularity.
• Financial data:
  • Program P&L, overhead allocations, labor rates, burden rates, and capitalization policies.
  • Functional budgets for Engineering, Production, Supply Chain, Quality, and PMO, with headcount and overtime trends for 12–24 months.
• Technical/engineering data:
  • PLM/PDM structure for configuration items, BOMs (EBOM/MBOM), revision histories, sign-off workflows, and approval matrices.
  • Systems engineering artifacts: requirements traceability, interface control documents, verification plans.
• Regulatory/ESG data:
  • ABS/NAVSEA audit findings, ISO 9001/14001 certification records, corrective action logs, and close-out status.
  • DFARS/CMMC and NIST 800-171 compliance evidence, cybersecurity policies, and previous assessment outcomes.
  • Safety metrics: TRIR, near-miss reports, safety observation trends for the last 24 months.
• People and governance data:
  • Current org charts, job descriptions, job family architectures, salary bands, and leadership levels.
  • Spans and layers data by function and program; supervisor-to-craft ratios by trade and shift.
  • Training records for CAMs, IPT leads, supervisors; union contracts and works council agreements; grievance logs and change consultation processes.
• Systems data:
  • Application landscape: ERP/MRP (e.g., SAP, IFS), MES, PLM/PDM (e.g., Teamcenter, ShipConstructor/AVEVA), scheduling tools, and data lake/BI stack.
  • Data dictionaries, integration maps, RBAC/permission matrices, and data quality rules.
• Granularity and horizons:
  • Weekly or bi-weekly for IMS/EVM/production control; monthly for financials and HR; per-event for ECNs/CCB decisions and quality audits.
  • Historical coverage of at least 12–24 months for trend analysis, seasonality, and change effects; forward view through next major milestones.
• Common data quality pitfalls:
  • WBS/OBS code mismatches, version control issues across PLM and ERP item masters, and inconsistent earned value techniques.
  • Time booking delays, phantom float in IMS, missing logic ties, and non-standard calendars across programs.
  • Duplicate job titles, ambiguous role descriptions, and outdated org charts misaligned with actual reporting lines.
  • Manual spreadsheets acting as systems of record, leading to reconciliation gaps and delayed dashboards.

5) Questions for Client

• What level of authority should reside with the Design Authority versus the CCB for cost/schedule-impacting changes, and where is leadership comfortable delegating decisions to IPTs?
• Which contractual milestones and trials windows constitute non-negotiable anchors for the operating model redesign, and how should decision gates align to those dates?
• How much baseline re-planning risk is acceptable during transition, and what thresholds should trigger executive intervention?
• What is the targeted span-and-layer profile by function and area, and what supervisory ratios by trade are acceptable within union constraints?
• Which programs or vessels will serve as the initial proving ground for IPT deployment, and what criteria define a successful pilot from an executive perspective?
• What EVMS compliance posture must be maintained during transition, and what support is needed to satisfy DCMA surveillance and customer audits?
• What capital and operating budget is available for enabling systems changes (PLM/MES/ERP integration, dashboards), and what cybersecurity requirements constrain solution choices?
• What are the known bottlenecks in engineering release, procurement of long-leads, and material kitting that the operating model must explicitly address?
• How should supplier management and source selection decision rights be structured between Program, Engineering, and Supply Chain to balance technical rigor and schedule needs?
• What level of workforce disruption is tolerable (role reassignments, leadership changes), and what engagement protocols with unions/works councils are required?
• Which KPIs will be used by the executive team to gauge operating model effectiveness in the first two quarters post-implementation, and what targets will indicate progress?
• What training and certification standards should be mandatory for IPT leads and CAMs, and who will own ongoing capability development?
• Where do current governance forums (Program Reviews, Risk Boards, CCB) fall short, and what cadence and participation changes are leadership willing to commit to?
• What is the appetite for consolidating functions (e.g., Production Engineering with Planning), and what are the non-negotiable separations of duty?
• Which customer and classification society interfaces require program-level ownership, and how will we coordinate inspections and hold points within the new matrix?

6) Interview Guide for Subject Matter Experts

SME Role: Program Director / Program Manager

• How do you currently structure Control Accounts, and where does WBS-to-OBS alignment break down in practice?
• What are the recurring drivers of variance in CPI/SPI, and how do CAMs escalate systemic issues?
• Which governance routines (CAM reviews, risk boards) add value versus consume time without decisions?
• Where are the biggest gaps between IMS logic and actual execution in shops and waterfront operations?
• How do you evaluate change requests for schedule impact and integrate decisions into the baseline?
• What information do you need in weekly IPT stand-ups to make decisions without reverting to executive forums?

SME Role: Chief Engineer / Design Authority

• What defines engineering maturity for drawing release, and what causes late-stage rework or clarifications?
• How are ECNs triaged and approved, and what percentage could be delegated to IPT-level authority safely?
• Where do PLM workflows hinder or support configuration control, and what approval bottlenecks are persistent?
• How do Systems Engineering and Production Engineering coordinate model-based definition and manufacturability?
• What are the known failure modes during FAI and trials, and how should technical baselines mitigate them earlier?
• What product areas or systems require dedicated Design Authority delegates embedded in IPTs?

SME Role: Director of Production / Waterfront Operations

• Where does supervisory coverage fall short by trade or shift, and how does that impact rework and out-of-sequence work?
• How do you prioritize work when material readiness and engineering release do not align with the IMS?
• What constraints (cranes, bays, test equipment) drive daily replanning, and how do you escalate blockers?
• Which handoffs from Production Engineering require redefinition, and what technical content is most often incomplete?
• What are the critical routines for day-of control, and what data is missing at the point of use?
• How should IPTs interact with shop supervision to avoid decision bottlenecks while preserving safety and quality?

SME Role: Head of Supply Chain / Materials Management

• How do you align long-lead procurement and kitting with drawing maturity and design freeze points?
• Where do TDPs lack completeness or standardization, and how does that affect supplier quality and readiness?
• What supplier readiness gates are enforced prior to need date, and who owns those decisions?
• How often do you expedite due to planning misalignment, and what would reduce expedite frequency?
• What data exchanges between PLM, ERP, and MES cause errors in BOM, routings, or item masters?
• Which procurements should sit under program-level decision rights versus enterprise sourcing strategies?

SME Role: PMO / EVMS Lead

• Which earned value techniques are applied by work package type, and where is guidance insufficient?
• What baseline control issues recur during re-plans, and how is variance narrative quality assessed?
• How do you assure schedule logic integrity, resource leveling, and calendars across programs?
• What is the maturity of the risk register, and how do risks translate into schedule and EAC adjustments?
• Which dashboards and KPIs are reliable, and where do manual reconciliations introduce latency?
• How should the PMO enforce accountability without creating administrative burden for IPTs and CAMs?

SME Role: Quality and Compliance Leader

• Where do ISO 9001 processes, ABS/NAVSEA hold points, and customer audits intersect with program cadence?
• What are the most common NCRs, and where do systemic corrective actions stall?
• How do you capture and act on FAI and trials defects, and who owns cross-functional remediation?
• Which compliance requirements (DFARS/CMMC) must be embedded in role charters and system permissions?
• What quality gates should be controlled by IPTs versus central quality to balance speed and rigor?
• How do you monitor and close repeat findings, and what governance ensures lesson capture?

SME Role: CHRO / HR Business Partner

• What is the current job architecture, and where does role ambiguity exist between functions and programs?
• Where are spans and layers out of tolerance, and what constraints (union, market) limit changes?
• How are leaders selected and developed for IPT roles, CAM responsibilities, and front-line supervision?
• What performance management and incentive mechanisms reinforce program-centric accountability?
• What training infrastructure is in place, and how is competency validated for critical roles?
• What change management practices have worked or failed during prior reorganizations?

7) Timeline

We executed a 12-week plan sequenced to minimize disruption to ongoing programs, integrate governance and systems, and prepare leadership to operate the new model. Decision gates tied to design authority and IPT activation were set to align with IMS milestones.

• Weeks 1–2: Mobilization and Discovery
  • Confirmed scope, objectives, and decision principles with executive sponsors.
  • Conducted stakeholder interviews and workshops across Engineering, Production, PMO, Supply Chain, Quality, and HR.
  • Collected and profiled data sets (IMS, EVMS, org structures, PLM/ERP/MES maps) and validated sources of truth.
  • Decision gate: Agree on problem statement, baseline KPIs, and design criteria for the operating model.
• Weeks 3–4: Diagnostics and Current-State Assessment
  • Completed spans-and-layers analysis; quantified supervisory coverage by trade; identified bottlenecks in decision rights and CCB cadence.
  • Assessed IMS logic health, EVMS technique consistency, and WBS/OBS misalignments.
  • Mapped value streams and critical handoffs between engineering release, procurement, and fabrication.
  • Decision gate: Align on key gaps and prioritized opportunities; confirm target IPT topology options.
• Weeks 5–6: Operating Model Design and Governance Charters
  • Developed program-centric matrix options and evaluated trade-offs versus functional structures.
  • Authored governance charters for CCB, PMO, and Program Reviews; defined RAPID/RASCI for top 20 decision types.
  • Drafted Design Authority charter, technical baseline ownership, and design freeze calendar.
  • Decision gate: Executive selection of preferred operating model; confirm decision rights and governance cadence.
• Weeks 7–8: Organization Sizing, Role Charters, and IPT Setup
  • Finalized spans-and-layers targets; mapped roles to job architecture; identified leaders for IPTs and CAM assignments.
  • Authored role charters for IPT leads, CAMs, engineering managers, production supervisors, and supplier-facing roles.
  • Configured initial IPT routines and meeting cadences; developed CAM playbooks and standard work.
  • Decision gate: Approve org charts, staffing plan, and IPT launch schedule; confirm union/works council engagement steps.
• Weeks 9–10: Systems and Data Enablement
  • Defined RBAC updates in PLM/MES/ERP; mapped CCB workflows; specified dashboard requirements and data sources.
  • Remediated critical data quality issues (code discipline, BOM alignment, schedule calendars) to enable pilot IPT dashboards.
  • Aligned PMO reporting cadence with IPT reviews; integrated risk registers and change logs with EAC processes.
  • Decision gate: Validate dashboards, access controls, and CCB workflows; authorize pilot activation.
• Weeks 11–12: Pilot Activation, Capability Build, and Handoff
  • Launched pilot IPTs on a defined scope (selected zones/systems or a specific hull), with leadership coaching and day-by-day support.
  • Delivered training for IPT leads, CAMs, supervisors, and engineering managers; finalized communications and reinforcement plans.
  • Established metrics review and feedback loops; documented lessons and prioritized enhancements for broader rollout.
  • Decision gate: Confirm readiness for scaled deployment; agree on governance for continuous improvement and sustainment.

8) Deliverables

• Operating Model Blueprint
  • Documentation of the program-centric matrix design, value streams, IPT topology, decision architecture, and governance forums. Used by executives to institutionalize decision rights and cadence.
• Spans & Layers Assessment and Org Charts
  • Quantitative analysis of current versus target spans and layers; future-state org charts by function and program. Used by HR and leaders to implement structure changes and rebalance supervision.
• Design Authority and CCB Charter
  • Formal definition of technical baseline ownership, approval thresholds, CCB membership, inputs/outputs, and workflows. Used by engineering and program leadership to enforce configuration control.
• IPT Role Charters and RASCI
  • Detailed charters for IPT leads, CAMs, engineering managers, production supervisors, supplier quality, and materials roles, with RASCI for top decisions. Used to clarify accountability and accelerate decisions.
• CAM Playbook and EVMS Standards
  • Guidance on earned value techniques by task type, variance analysis standards, risk-to-EAC integration, and baseline change control. Used by PMO and CAMs to standardize performance management.
• Governance Calendar and Leadership Routines
  • Cadence for Program Reviews, CAM Reviews, Risk Boards, and CCB; standard agendas, inputs, and outputs. Used by leadership to maintain rhythm and focus on critical decisions.
• Systems and Data Enablement Plan
  • RBAC matrices, integration maps across PLM/ERP/MES, dashboard specifications, and data dictionary updates. Used by IT and PMO to implement digital support for IPTs.
• KPI Tree and Dashboard Prototypes
  • Linked metrics for schedule adherence, CPI/SPI, drawing release OTD, ECN aging, material readiness, and quality gates. Used in IPT stand-ups and Program Reviews for status-at-a-glance.
• Change Management and Communications Plan
  • Stakeholder mapping, readiness assessments, messaging frameworks, and training plans. Used by HR and Communications to guide adoption and mitigate change fatigue.
• Training Curriculum and Certification Pathways
  • Learning paths for IPT leads, CAMs, supervisors, and engineering managers; assessments and certification criteria. Used to build durable capabilities and role readiness.
• Implementation Roadmap and Risk Register
  • Phased deployment plan with decision gates, resource plan, and risk mitigations. Used by sponsors to manage rollout and dependencies with ongoing programs.
• Union/Works Council Engagement Package
  • Briefing materials, impact summaries, and consultation schedule aligned to structural changes. Used by HR and leadership to engage labor stakeholders appropriately.

9) Industry Insights

Shipbuilding & marine systems programs operate at the intersection of complex systems integration, heavy industrial execution, and regulated defense contracting. Operating model effectiveness directly influences schedule realism, risk posture, and contractual performance. The following insights informed the design choices and trade-offs in this project.

• Market dynamics:
  • Naval recapitalization, offshore wind installation vessels, and specialized support ships increased demand for complex builds with high systems content. Lead-yard/follow-yard models and teaming arrangements required clarity on design authority and configuration control across partners.
  • Supply chain fragility, long-lead components (propulsion, switchboards, HVAC plants), and inflationary pressures increased the premium on early design freeze and disciplined change management.
• Technology shifts:
  • Model-based systems engineering and model-based definition accelerated design throughput but required robust PLM governance and delegated design authority embedded in IPTs to avoid late clarifications.
  • Digital thread integration across PLM, ERP/MRP, and MES enabled real-time configuration status but depended on strict coding discipline, RBAC, and synchronized workflows between engineering, procurement, and production.
• Ecosystem and partnering patterns:
  • Primes, design houses, and shipyards increasingly collaborated, necessitating clear decision rights on technical baselines, supplier selection, and change incorporation to prevent rework and contractual disputes.
  • Vendor quality and supplier readiness became shared responsibilities; IPTs needed integrated Supplier Quality roles and escalation routines to preserve schedule integrity.
• Regulations and standards:
  • Compliance with NAVSEA standards, ABS rules, ISO 9001, and EVMS guidelines required disciplined governance. CMMC/DFARS cybersecurity obligations influenced systems design and access control for IPTs.
  • Test and trials regimes, FAI, and classification hold points demanded program-level ownership to align inspections with build sequence and minimize retests.
• Buyer behavior:
  • Defense and government buyers emphasized baseline discipline, credible EACs, and risk transparency. Operating models that embed PMO rigor and design authority at the program level increased confidence during reviews.
  • Commercial buyers prioritized delivery windows and lifecycle support; program-centric IPTs improved coordination between design, procurement, and production to protect delivery commitments.
• What “good” looks like:
  • Program-centric matrix with IPTs aligned to product/zone/system, each with a Control Account Manager accountable for cost/schedule, a Design Authority delegate accountable for technical integrity, and an embedded production engineering liaison.
  • Decision cadence with weekly IPT stand-ups, bi-weekly CCB pre-briefs, monthly Program Reviews, and disciplined change control linked to IMS gates and EVMS baselines.
  • Spans and layers tuned to heavy manufacturing benchmarks: fewer layers in engineering with empowered team leads; robust front-line supervisory coverage in shops; clear separation of duties for quality and compliance.
  • Digital thread with synchronized PLM/ERP/MES, role-based dashboards providing visibility into drawing maturity, material readiness, and control account performance.
• Near-term disruptions to watch:
  • Acceleration of digital shipyard initiatives (augmented reality instructions, automated welding, robotics) requiring new role charters and decision rights in IPTs.
  • Tightening cybersecurity and data sovereignty rules affecting supplier integration and remote collaboration tools.
  • Labor market constraints in specialized trades and engineering disciplines necessitating redesigned supervisory models, training pipelines, and cross-skilling strategies.
  • Growing emphasis on sustainability and alternative fuels systems, increasing technical complexity and the need for stronger configuration control and multidisciplinary IPTs.
• Implications:
  • Operating models that concentrate decision rights at the IPT level, within a strong Design Authority and PMO framework, created the conditions for faster, better decisions without eroding compliance or baseline discipline.
  • Spans-and-layers optimization and role clarity reduced organizational drag, freeing leadership capacity to manage risk and protect critical path activities.
  • Digital enablement, when tied to role-based workflows and governance, provided actionable information at the right cadence, reducing reliance on ad hoc reconciliations.