Manufacturing Execution System Deployment

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 large naval and commercial shipbuilder operated multiple yards with panel lines, hull block assembly, pre-outfitting, painting, and final integration. Production management sought to deploy a Manufacturing Execution System (MES) to orchestrate block and zone work orders, standardize labor capture, digitize quality records, enable end-to-end genealogy, and connect IIoT assets to increase visibility, throughput, and first-pass yield. The production environment was complex: engineering output flowed from PLM to ERP, planning lived in Primavera P6, and operations relied on paper travelers and disparate spreadsheets. Configuration control requirements were stringent given NAVSEA, ABS/DNV class, and Level I/Subsafe traceability mandates.

The client faced a set of intertwined pain points that constrained schedule adherence, drove rework, and obscured true performance:

• Fragmented work order management: Block- and zone-based work packages were planned in P6 and ERP but executed on paper travelers, leading to mis-sequencing, missed hold points, and late discovery of constraint violations at block erection.
• Low-quality labor capture: Time was recorded at the end of shift in batch form, often at the job family level rather than specific operation, obscuring productivity variances by block and zone. Overtime and indirect labor were difficult to allocate accurately.
• Limited first-pass yield visibility: Weld, fit-up, coating, and NDT outcomes were logged in standalone quality systems or scanned PDFs, making it hard to differentiate between shop-induced defects versus material issues or procedure non-compliance.
• Genealogy gaps: Material heat numbers, welder IDs, joint IDs, and component serials were inconsistently linked to as-built structure and systems, complicating Level I/Subsafe material traceability, class surveyor reviews, and configuration audits.
• IIoT disconnects: Panel line PLCs, CNC cutting tables, welding machines, and blasting/painting booths were not integrated to MES. OEE, downtime codes, and environmental conditions (temperature/humidity) were manually sampled and not synchronized with work order execution.
• Change propagation issues: Engineering changes (ECNs/DCNs) were not reliably pushed into open work orders. In-flight rework was triggered late, causing scrap and schedule churn at zone integration and commissioning.
• Inventory and kitting delays: Kitting status for pipe spools, cableways, HVAC, and equipment modules was tracked in WMS but not visible at the station. Crews started work without all materials staged, driving stop-start and out-of-sequence work.
• Compliance friction: AS9100/ISO9001 processes, NAVSEA S9074 welding requirements, ABS/DNV hold points, and CMMC/NIST 800-171 cybersecurity controls imposed heavy documentation needs that paper-based workflows struggled to meet.
• Inconsistent KPI baselines: Key performance indicators such as schedule adherence, earned value metrics (CPI, SPI), rework rate, NDT reject rate, labor utilization, and first-pass yield were compiled weekly with 3–10 day latency, hampering production control and daily tier meetings.

Representative performance indicators underperformed or lacked fidelity to support decisive action:

• First-pass yield for hull fabrication and outfitting was variably estimated; quality teams reported double-digit NDT re-inspection rates in certain blocks without reliable root-cause correlation to welders, procedures, or material lots.
• Schedule adherence at the zone level was masked by aggregate P6 progress curves; SPI trended below 1.0 on critical paths without operation-level visibility to recoveries.
• Labor productivity in hours per ton and hours per outfitting package fluctuated widely; inaccurate labor charging hindered continuous improvement and incentive plan fairness.
• WIP aged beyond planned takt in pre-outfitting and paint booths due to missing materials and delayed quality clearances; average WIP days exceeded planning norms with no digital Andon to escalate blockers.
• OEE on panel lines and CNC cutting was tracked manually; equipment downtime codes lacked standardized taxonomy, limiting asset reliability analytics.

Leadership aligned on the need for an MES deployment tightly integrated with PLM, ERP, WMS, and IIoT to enable block and zone work order execution, reliable labor capture at the operation level, digital quality records with automated hold points, end-to-end genealogy, and real-time production control dashboards suitable for both operations and program management.

2) Project Objective

Primary objective: We deployed a shipbuilding-specific MES to orchestrate block and zone work orders, digitize labor capture, embed quality records and hold points, provide material and process genealogy, and integrate IIoT signals, thereby raising production visibility and enabling higher throughput and first-pass yield across hull fabrication and outfitting.

Secondary objectives:

• Performance: Established real-time execution control and short-interval management with operation-level status, enabling proactive constraint removal on critical paths.
• Economics: Built a cost-accurate labor and material charging model at the work order operation level, improving reliability of EVMS (CPI/SPI) and program financials.
• Compliance: Implemented digital travelers, e-signatures, and automated hold-point workflows aligned to NAVSEA, ABS/DNV, and Level I/Subsafe traceability requirements.
• Customer impact: Enabled transparent milestone reporting for owner reps and class surveyors through auditable quality records and configuration-aligned as-built genealogy.
• Digital/data enablement: Designed a standards-based integration architecture (ISA-95) to synchronize PLM/ERP/WMS/MES and IIoT with a governed production data model.
• Capability-building: Trained supervisors, planners, quality inspectors, and craft leads on MES usage, digital tier boards, and root-cause problem-solving using MES analytics.
• Cybersecurity: Deployed an architecture aligned to CMMC 2.0 and NIST 800-171 with segmented OT networks (ISA/IEC 62443), MFA, and auditing controls for MES.

3) Methodology and Approach

We executed an integrated program composed of eight workstreams, sequenced to reduce risk, compress time-to-value, and anchor the MES deployment to the shipyard’s digital thread. Each workstream targeted specific pain points and linked directly to the KPIs that leadership prioritized.

Workstream 1: Current-State Mapping and Value Stream Diagnostics

Activities conducted:

• Mapped end-to-end production flows from steel receipt through panel line, block assembly, pre-outfitting, blast/paint, erection, and commissioning, aligning to block and zone structures used in planning and configuration management.
• Conducted Gemba walks and time studies on representative stations (panel line, CNC cutting, pipe shop, cableways, HVAC module assembly) to quantify cycle times, wait times, handoffs, and rework triggers.
• Inventoried all execution artifacts: paper travelers, weld maps, WPS/PQR binders, NDT reports, torque logs, coating logs, calibration certificates, and material test certificates (MTCs).
• Built a SIPOC and swimlane analysis across Production, Planning, Quality, Engineering, Supply Chain, and IT/OT to identify systemic bottlenecks and data breaks.

Tools and frameworks used:

• Value stream mapping (VSM) with takt-time assessment adapted to shipbuilding’s batch/queue reality.
• ISA-95 levels mapping to locate systems of record and define handoffs between Level 3 (MES) and Level 4 (ERP/PLM).
• Root-cause frameworks (5-Why, Ishikawa) to categorize FPY loss drivers.

Stakeholders engaged: Production directors, area supervisors, planners, quality leads, engineering change control, supply chain, IT/OT architects. This groundwork prioritized the initial MES scope and identified the data foundation required to enable block/zone execution and genealogy.

Workstream 2: Architecture and Integration Design (ISA-95 Aligned)

Activities conducted:

• Defined the target architecture for Information Technology in the yard: MES as Level 3 orchestrator, integrated upstream to PLM (eBOM, MBOM, routings, 3D model), ERP (work orders, costs, inventory), and P6 (schedule), and downstream to IIoT/SCADA and quality instrumentation.
• Specified integration patterns: message exchange via APIs and message bus (REST/JSON, MQ), OPC UA for OT connectivity, MQTT for telemetry, and file-based fallbacks where necessary.
• Designed data models for block/zone structures, operation definitions, resource calendars, and quality plans, ensuring round-trip configuration control with PLM and change management processes.
• Determined on-prem vs. hybrid topology to meet ITAR, CMMC 2.0, and NIST 800-171, with a DMZ, jump hosts, and segmented OT networks (ISA/IEC 62443 zones and conduits).

Tools and frameworks used:

• Architecture diagrams and sequence diagrams to validate end-to-end data flow and event orchestration.
• Master data governance framework for parts, operations, stations, and quality characteristics.
• Security controls catalog aligned to CMMC practices (access control, audit/logging, incident response, configuration management).

Stakeholders engaged: Enterprise architects, cybersecurity, PLM admins, ERP functional leads, OT engineers, and vendors. The design was oriented to reduce integration risk, accelerate pilot deployment, and maintain compliance posture.

Workstream 3: Master Data, Digital Thread, and Configuration Control

Activities conducted:

• Reconciled EBOM from PLM to MBOM and shop-floor routings for hull structure, piping, electrical, and HVAC systems, normalizing block and zone references and ensuring a consistent “ship breakdown structure” (SBS) across disciplines.
• Standardized part numbers, weld joint IDs, WPS/PQR references, and inspection/test attributes to enforce consistent labeling on digital travelers.
• Established a genealogy schema linking material heats, welder IDs, weld joints, NDT results, torque values, coating batch lots, and serial-controlled items to the as-built configuration under configuration management control.
• Configured automated change propagation so that ECNs/DCNs updated open work orders with controlled disposition (use-as-is, rework, scrap) and traceable e-signature approvals.

Tools and frameworks used:

• Data profiling and cleansing tools to resolve duplicates and naming inconsistencies (zones, blocks, systems).
• PLM-MES integration adapters to synchronize MBOM and work instructions, including 3D model snapshots and weld maps.
• Configuration management practices aligned to NAVSEA and class requirements for controlled updates and audit trails.

Stakeholders engaged: PLM/configuration management, welding engineering, quality/NDT, production planning, and IT data governance. The focus was to create a reliable digital thread that supported both execution and auditability.

Workstream 4: MES Solution Configuration and Extensions

Activities conducted:

• Configured MES modules for work order orchestration, operation-level dispatching, labor time capture (badges, barcodes, kiosks, mobile), electronic travelers, and quality plans with automated hold points.
• Developed extensions for shipyard-specific needs: block/zone work order hierarchy, zone-centric dashboards, weld map integration, and as-built system tagging.
• Set up labor capture with operation-level coding, reason codes for delays and rework, and supervisor overrides with audit trails to support EVMS accuracy.
• Built digital forms for NDT (RT, UT, MT, PT), coating logs, torque and pressure tests, and calibration verifications with embedded e-signatures.

Tools and frameworks used:

• MES vendor toolset (workflow engine, form designer, rules engine) to model visual travelers, hold points, and escalation logic.
• Role-based access control mapped to union roles, QA signatories, and class surveyor view-only access.
• API connectors to ERP (work order creation/close, cost posting), WMS (kit status, pick confirmations), and PLM (work instructions, 3D views).

Stakeholders engaged: Operations supervisors, planners, quality engineers, IT developers, and vendor solution architects. Configuration choices aimed to reduce manual handoffs, cut data latency, and improve compliance confidence.

Workstream 5: IIoT Connectivity and Production Telemetry

Activities conducted:

• Inventoried OT assets: panel line PLCs, CNC cutting machines, welding machines with digital power sources, blast/paint booths, compressors, and material handling assets.
• Implemented an edge gateway layer (OPC UA servers, MQTT brokers) with secure connectivity to MES and a time-series historian for OEE, downtime, and environmental monitoring.
• Mapped machine states and downtime taxonomies to MES operation status, enabling digital Andon and exception management at the station and zone levels.
• Integrated environmental sensors (temperature, humidity) to quality plans where process conditions impacted weld and coating quality.

Tools and frameworks used:

• Edge computing gateways with protocol translation (Kepware/ignition) and secure certificates management.
• Data historian and analytics layer for time-series, enabling correlation between equipment states and quality outcomes.
• Time synchronization (NTP/PTP) to ensure consistent time stamping across MES, historian, and PLCs.

Stakeholders engaged: OT engineers, maintenance, quality, IT security, and MES integration leads. The design fostered higher signal fidelity for production control and enabled root-cause analysis of FPY losses.

Workstream 6: Quality, Genealogy, and Compliance Enablement

Activities conducted:

• Digitized quality plans with automated gate checks for mandatory inspections and class surveyor hold points, including NAVSEA Level I/Subsafe material controls.
• Embedded weld procedures (WPS) and qualifications (PQR, welder qualifications) into operation workflows with e-signatures and real-time validation.
• Configured genealogy capture for materials (heat/lot), welds (joint ID, welder ID, parameters), NDT results, coatings (batch), and torque/pressure tests, linking all to as-built configuration by block, zone, and system.
• Built audit-ready reports and e-DHR equivalents for shipbuilding, supporting ABS/DNV reviews and customer acceptance milestones.

Tools and frameworks used:

• Electronic forms with conditional logic and image attachments (NDT images, weld photos, coating thickness readings).
• Device integration for gauges and NDT equipment where digital interfaces were available, reducing manual transcription risk.
• Compliance mapping to AS9100/ISO9001 clauses and CMMC controls for audit trails and access restrictions.

Stakeholders engaged: Quality/NDT leadership, welding engineering, class liaison, compliance officers, and customer representatives. This workstream was central to reducing rework drivers and ensuring audit-readiness.

Workstream 7: Change Management, Training, and Operating Model

Activities conducted:

• Defined a future-state operating model for production control: daily tier meetings, escalation paths, and MES-driven performance management cadence at shift, zone, and program levels.
• Developed role-based training for craft, supervisors, planners, quality inspectors, and maintenance on MES usage, scanners/mobile devices, and digital Andon response.
• Created SOPs for job start, operation handoff, quality e-signature, rework initiation, and deviation management, with union and HR alignment.
• Implemented change agent networks and feedback loops to capture adoption barriers and iterate workflows.

Tools and frameworks used:

• ADKAR and stakeholder heat maps to tailor engagement intensity by role and yard.
• Digital adoption toolkits and quick-reference guides at stations, integrated with MES help content.
• Governance forums and KPIs to monitor adoption (scan compliance, timely labor capture, e-signature rates).

Stakeholders engaged: Production and HR leadership, union representatives, training leads, safety, and IT support. The emphasis was on sustained behavior change and consistent usage patterns.

Workstream 8: Pilot, Scale-Up, and Governance

Activities conducted:

• Delivered an initial pilot in a selected block family and associated zones (e.g., mid-body hull blocks and adjacent outfitting zones), covering work order execution, labor capture, quality, and IIoT integration.
• Ran hypercare with cross-functional war room, instrumented with dashboards showing latency, error rates, and user adoption metrics.
• Codified scale-up playbooks, data migration sequences, and cutover plans for additional blocks/zones and eventually other yards.
• Established a permanent MES governance board to oversee backlog, release cadence, cybersecurity posture, and vendor performance.

Tools and frameworks used:

• Pilot entry/exit criteria tied to data quality thresholds, process adherence, and system performance SLAs.
• Release management and DevSecOps practices with environment segregation (DEV/TEST/PROD) and automated regression testing for critical workflows.
• Risk management log and decision gates aligned to program milestones (keel laying, launch, sea trials).

Stakeholders engaged: Yard operations, program management, IT/OT, finance/EVMS, and vendor PMO. The approach balanced speed with control, while building the governance muscle to sustain the solution.

4) Data Request

To execute the project effectively, we requested a comprehensive dataset spanning commercial, operational, financial, technical, regulatory, people, and systems domains. We defined time horizons, granularity, and known data quality pitfalls upfront.

• Commercial/program:
  • Contract structure, CDRLs, EVMS reporting requirements, and milestone schedules for active programs (last 24–36 months).
  • Owner/class interactions and survey requirements by vessel type.
• Operational:
  • Detailed routing and operation lists for hull fabrication, piping, electrical, HVAC, and painting by block and zone; operation standard times and resource requirements.
  • Work order history with start/finish, partial completes, rework records, deviations, and scrap (operation-level granularity).
  • Kitting/picking logs from WMS, shortage reports, and staging times by station.
  • Equipment availability and maintenance logs for panel lines, CNC cutters, welding machines, and paint booths (shift-level granularity).
• Financial/EVMS:
  • Labor charging codes and timekeeping data at the operation or job level; indirect allocation rules; overtime policies (shift/day granularity).
  • EVMS baselines, actual cost of work performed (ACWP), budgeted cost of work scheduled (BCWS), and cost/schedule variance reports aligned to WBS/SBS.
• Technical/engineering:
  • PLM artifacts: EBOM, MBOM, routings, work instructions, weld maps, and 3D visualizations by block and zone.
  • Engineering changes (ECNs/DCNs) history with effectivity, disposition, and affected work orders.
  • Material properties, WPS/PQR library, welder qualifications, and qualified parameter ranges.
• Quality/regulatory:
  • NDT records (RT, UT, MT, PT), coating inspection logs, torque and pressure test results, calibration certificates, and material test certificates with heat numbers.
  • Class and NAVSEA hold-point matrices; Level I/Subsafe material control procedures.
• People/governance:
  • Organization structure, union agreements impacting time capture and job rotation.
  • Training matrices for welding, NDT, coatings, and MES user roles; e-signature authority lists.
• Systems and infrastructure:
  • ERP (e.g., SAP S/4HANA), PLM (e.g., Teamcenter), P6, WMS, QMS, T&A, and current shop-floor applications (versions, integration points, customizations).
  • OT asset inventory: PLCs, HMIs, machine controllers; protocol support (OPC UA/DA, Modbus, proprietary); network topology and security zones.
  • Historian/SCADA data sources; NTP/PTP configuration; certificate authority and identity providers for MES.

Typical time horizons and granularity:

• Historical operational and quality data: 24–36 months, at operation-level granularity; weld/joint-level for critical structures; shift-level equipment telemetry.
• Financial and EVMS data: 18–24 months at WBS level mapped to operations where available; alignment to block/zone structures.
• Engineering changes: full lifecycle records for the last 24 months with effectivity windows and impact scope.

Common data quality pitfalls we addressed:

• Mismatched block/zone naming conventions across PLM, ERP, and spreadsheets, resulting in mapping errors.
• Work orders without operation-level detail or with generic resource codes that hid true capacity constraints.
• Scanned PDFs for quality records lacking structured fields; manual transcription errors for NDT and coating logs.
• Duplicate or recycled part numbers and missing heat numbers for Level I materials.
• Timekeeping entries posted in batch at shift end, obscuring actual start/stop times and rework effort.
• OT asset clocks not synchronized, leading to time-stamp drift between MES and machines.

5) Questions for Client

• What scope of vessels, yards, and programs should the initial MES deployment cover, and where is the highest urgency (block family, zones, or specific shops)?
• How tightly do you want MES to drive the schedule (dispatch and hold points) versus reflecting execution while P6 remains the master driver?
• What is the acceptable risk profile for on-prem versus hybrid architectures given ITAR and CMMC requirements?
• Which KPIs will govern success (e.g., FPY, schedule adherence, WIP days, EVMS reliability), and what decision cadences need real-time views?
• What is your position on standardization of block/zone work package structures across programs versus program-specific tailoring?
• How should we handle labor capture granularity given union rules, crew structures, and incentive compensation implications?
• What change control authorities must approve ECN/DCN propagation into in-flight work, and what disposition rules are acceptable?
• What degree of integration is required with class surveyor processes and owner representative access to digital quality records?
• What constraints exist in OT networks and equipment vendors for IIoT connectivity (OPC UA availability, proprietary drivers, security zones)?
• What capital and operating budget envelope is reserved for licenses, integration, devices (scanners/tablets), and OT gateways?
• Which cybersecurity controls are mandatory at go-live (MFA, logging, vulnerability scans), and what audit schedule must we prepare for?
• What training bandwidth is available for craft and supervisors, and how will we backfill during training and pilot hypercare?
• Are there anchor milestones (keel, launch, sea trials) that create hard decision gates for pilot exit and scale-up?
• What legacy systems or custom tools must be retained or decommissioned, and what data retention policies apply?
• Which vendor relationships (MES, PLM, ERP) should be leveraged or avoided, and what contractual constraints exist?

6) Interview Guide for Subject Matter Experts

Production Director (Hull and Outfitting)

• How do you currently prioritize work across blocks and zones when constraints emerge, and what information is missing at daily tier meetings?
• Where do you see the largest schedule risk: panel line, block assembly, pre-outfitting, paint, or integration? What signals would allow earlier intervention?
• How do you measure crew-level productivity and rework today, and where does time booking fail to reflect reality?
• What escalation paths exist for material shortages, quality holds, and equipment downtime, and how often are these triggers late?
• What are the top three process deviations that recur and cause production turbulence?
• What governance cadence do you expect for production control dashboards and decision-making?

Welding Engineering and NDT Lead

• Which WPS/PQR relationships and parameter ranges must be validated at operation start, and how is welder qualification verified?
• Where do weld rejects cluster (by joint type, position, material, or environmental conditions), and how do you trace root cause today?
• What information from machines (current, voltage, travel speed) is available digitally, and how should it be correlated to weld records?
• How are NDT requests scheduled, executed, and logged, and which steps are prone to transcription errors?
• What Level I/Subsafe controls require special handling in genealogy and e-signature workflows?
• How should class surveyors and customer QA access records, and what redactions are required?

Planning and Scheduling (Primavera P6)

• How are block- and zone-level activities structured in P6, and how are work packages derived and released?
• What is the current fidelity of status updates from the shop floor to P6, and how do you handle partial completions?
• How often do ECNs/DCNs drive replanning, and how do you communicate resequencing to production?
• What buffers or float do you build into critical paths, and where are the typical sources of variance?
• Which integration touchpoints between MES and P6 are necessary for practical control without overconstraining operations?

Supply Chain and Warehouse/Kitting

• How do you plan and execute kitting by block and zone, and what percent of kits are staged complete on time?
• Where do shortages originate (supplier slip, quality hold, mispick), and how is that communicated to production?
• What identifiers (barcodes/RFID) are used for parts and kits, and how consistently are they scanned at station?
• What integration is required between WMS and MES for pick confirmations, staging status, and substitution approvals?
• What material attributes (heat numbers, batch/lot) must travel with the kit for genealogy?

IT/OT Architecture and Cybersecurity

• What is the current network segmentation between enterprise and OT, and how are remote connections and protocol gateways managed?
• Which identity providers and MFA solutions are in place, and how should MES authenticate users and devices?
• What logging, SIEM, and vulnerability management tools are mandated, and what is the patching window in OT?
• Which OT assets support OPC UA or require proprietary drivers, and where is protocol conversion feasible?
• What disaster recovery and high-availability requirements exist for MES and integrations?
• What CMMC controls are audited regularly, and what evidence must MES produce?

Quality and Compliance (Class, NAVSEA)

• Which hold points require enforced e-signatures and “no-go” gates, and what is the approval chain?
• How do you presently assemble evidence packs for class surveys and customer milestones, and what gaps cause delays?
• What calibration and instrument control processes must integrate with MES quality records?
• What document retention periods apply to weld/NDT/coating records and Level I materials?
• How often are audit nonconformities driven by documentation defects versus process defects?

Finance/EVMS and Program Management

• How do you reconcile labor booking with EVMS at the control account level, and where are the biggest accuracy gaps?
• What level of cost visibility at operation or zone would change decision-making for program managers?
• What cycle time and latency expectations do you have for cost reporting and SPI/CPI updates?
• How are change orders and customer-directed changes reflected in EVMS baselines, and how should MES support traceability?
• What is the threshold for approving investment in devices and IIoT gateways based on expected reporting benefits?

7) Timeline

We followed a 12-week plan designed to balance rapid deployment with robust controls, with clear decision gates tied to MES scope for block and zone execution, labor capture, quality, genealogy, and IIoT connectivity.

Weeks 1–2: Discovery and Alignment

• Conducted stakeholder interviews, Gemba walks, and data inventory across production, quality, planning, engineering, supply chain, and IT/OT.
• Mapped current-state value streams and identified high-impact pilot scope (target block family and associated zones).
• Confirmed architectural principles (ISA-95 alignment, on-prem/hybrid posture) and compliance envelope (CMMC, ITAR, class).
• Decision gate: Approve pilot scope, KPI focus, and architectural direction.

Weeks 3–4: Diagnostics and Data Foundation

• Executed data profiling and master data cleansing for block/zone structures, operations, part numbers, and quality attributes.
• Drafted MBOM-to-routing mapping; defined genealogy schema; configured initial integration stubs to PLM/ERP/WMS.
• Developed initial quality plan templates and hold-point matrices for pilot scope.
• Decision gate: Sign-off on data model, genealogy schema, and integration interface specifications.

Weeks 5–6: Solution Configuration and Integration Build

• Configured MES workflows for work order dispatch, labor capture, digital travelers, and quality e-signatures for pilot operations.
• Implemented API integration to ERP (work order lifecycle, costs), PLM (work instructions, 3D imagery), and WMS (kitting status).
• Established identity and access management, logging, and role-based permissions aligned to cybersecurity standards.
• Decision gate: Complete system integration test (SIT) and approve move to OT connectivity setup.

Weeks 7–8: IIoT Connectivity and Station Readiness

• Deployed edge gateways, configured OPC UA/MQTT connections, and set up historian streams for target machines and sensors.
• Mapped machine states/downtime to MES operations; configured digital Andon and exception alerts.
• Provisioned devices (scanners, tablets, kiosks) and validated station ergonomics and network reliability.
• Decision gate: Factory acceptance of IIoT integrations and station readiness; approve pilot cutover.

Weeks 9–10: Pilot Execution and Hypercare

• Launched pilot in selected block/zone scope; monitored adoption metrics (scan compliance, e-sign rates, labor capture timeliness) and system performance.
• Ran daily war room, captured and prioritized defects and change requests, and iterated workflow configurations.
• Collected evidence for compliance checks with internal QA and class liaison participation.
• Decision gate: Assess pilot exit criteria and define scale-up increments.

Weeks 11–12: Validation, Governance, and Scale-Up Plan

• Validated data synchronization across PLM/ERP/WMS/MES; confirmed genealogy completeness and quality record integrity.
• Codified operating model, training plan, and governance for continued releases; prepared vendor and internal support roles.
• Built a phased rollout roadmap for remaining blocks/zones and additional yards with investment case and risk mitigations.
• Decision gate: Executive approval for scale-up and funding allocation.

Critical path items included master data cleansing, PLM-to-MES mapping, cybersecurity control validation, and IIoT driver availability for OT assets. Decision gates ensured scope control and compliance readiness.

8) Deliverables

• Current-State Diagnostics Pack:
  • Value stream maps, pain-point inventory, and KPI baseline visibility; used to align leadership on pilot scope and priorities.
• MES Requirements and Traceability Matrix:
  • Functional and non-functional requirements mapped to block/zone execution, labor capture, quality, genealogy, IIoT, security, and compliance; enabled vendor configuration and testing coverage.
• Target Architecture Blueprint (ISA-95 Aligned):
  • Logical and physical architecture, integration patterns, security zones, data flows, and environment topology; used by IT/OT and vendors to implement integrations.
• Master Data and Digital Thread Playbook:
  • Standards for block/zone nomenclature, MBOM routing, operation codes, quality attributes, and genealogy schema; included cleansing scripts and governance roles.
• Quality and Compliance Blueprint:
  • Digital quality plans, hold-point matrix, e-signature workflows, and evidence templates aligned to NAVSEA, ABS/DNV, and Level I/Subsafe; used by QA and class liaison.
• IIoT Connectivity and Telemetry Design:
  • Asset inventory, tag mappings, downtime taxonomy, edge gateway configuration, historian schema, and Andon alerting; used by OT and maintenance.
• Integration Specifications Package:
  • API contracts for ERP/PLM/WMS/P6, event sequencing, error handling, and reconciliation procedures; used by integration developers.
• Cybersecurity and Compliance Plan:
  • CMMC control mapping, identity/access design, logging/SIEM integration, backup/DR, and OT segmentation controls; used by security, audit, and operations.
• Pilot Execution Plan and Hypercare Runbook:
  • Cutover checklist, training schedule, support model, defect triage process, and exit criteria; used by operations and IT during pilot.
• Training Curriculum and SOPs:
  • Role-based training materials, quick reference guides, e-learning modules, and SOPs for job start, labor capture, quality e-signature, and rework; used by supervisors and craft.
• KPI Dashboard Mockups and Data Dictionary:
  • Designs for real-time production control dashboards (zone/operation/quality), with metric definitions and data lineage; used by managers and analysts.
• Implementation Roadmap and Investment Case:
  • Phased rollout plan, resource model, device and infrastructure bill of materials, license plan, and financial analysis (TCO/NPV); used by executives for funding decisions.
• Governance Charter and Operating Model:
  • MES steering committee, change control board, release management cadence, and RACI; used to sustain and evolve the solution.

9) Industry Insights

Shipbuilding and marine systems in Aerospace & Defense have entered a phase where modular construction, digital thread integration, and secure, connected operations are essential to delivering complex vessels on schedule and to specification. Several market and technology trends informed our approach to MES deployment.

• Market dynamics:
  • Naval recapitalization programs and commercial decarbonization agendas increased demand for complex hulls with advanced systems. Backlogs intensified schedule pressure and pushed yards to industrialize processes while addressing skilled labor shortages.
  • Program oversight tightened. EVMS expectations and milestone scrutiny increased, necessitating operation-level data to substantiate progress and recoveries.
• Technology shifts:
  • Convergence of PLM, MES, and IIoT matured. Vendors strengthened shipbuilding templates (block/zone models, weld maps), enabling tighter integration of 3D models, work instructions, and execution data.
  • Edge and historian technologies simplified secure OT connectivity (OPC UA, MQTT) while providing the foundation for OEE and condition monitoring.
  • Model-Based Definition (MBD) and digital work instructions reduced ambiguity at the station, especially for complex outfitting and cable installation.
• Ecosystem and partnering:
  • Strategic alignment with PLM and ERP vendors was critical. Joint roadmaps avoided brittle customizations and leveraged standard adapters for BOM, routing, and visualization.
  • System integrators with shipyard experience accelerated deployment by applying block/zone best practices and prebuilt quality forms for weld and coating processes.
• Regulations and standards:
  • CMMC 2.0 and NIST 800-171 drove architectural choices, favoring on-prem or hybrid deployments with strong identity, logging, and segmentation controls.
  • NAVSEA requirements, Level I/Subsafe controls, and ABS/DNV class rules mandated rigorous genealogy and auditable quality records, reinforcing the case for digital travelers and e-signatures.
  • ISA-95 and ISA/IEC 62443 provided a blueprint for system layering and secure OT integration.
• Buyer behavior:
  • Executives prioritized solutions that improved schedule predictability and audit readiness. Proofs of value in limited zones/blocks that translated into credible scale-up plans were favored over monolithic, multi-year programs.
  • Change management and user adoption were recognized as pivotal; buyers expected strong training and operating model deliverables alongside technology.
• What “good” looks like (illustrative targets):
  • Near real-time (sub-5-minute) visibility of operation status by zone and block, with reliable roll-up to P6 and EVMS.
  • First-pass yield uplift evidenced by reduced NDT re-inspections and fewer quality deviations at block integration, supported by robust genealogy and in-process checks.
  • Scan and e-signature compliance consistently above 98% for digital travelers; high-fidelity labor capture at operation level enabling more accurate CPI/SPI.
  • OEE baselined and monitored on panel lines and critical machines, with standardized downtime codes enabling targeted reliability improvements.
  • Complete digital evidence packs ready for class and customer reviews without manual collation.
• Near-term disruptions and implications:
  • Increasing adoption of robotics (weld, painting) and autonomous material handling will heighten the need for MES-OT orchestration. Architectures must be adaptable to integrate these assets.
  • Green fuels and new materials (e.g., high-strength steels, composites) will require updated WPS/PQR libraries and quality plans; MES must support rapid qualification and change control.
  • Cyber threats targeting OT will intensify; zero-trust principles, continuous monitoring, and rigorous patch management will become table stakes for MES environments.

In this context, deploying an MES tailored to block and zone work orders, labor capture, digital quality, genealogy, and IIoT connectivity represented a practical, value-oriented step toward a secure digital shipyard. The approach emphasized a robust data foundation, standards-based integration, disciplined change control, and an operating model that sustained adoption and continuous improvement across yards and programs.