Skip to content
Danaos

Ship Repair ERP: Why Expedient Works, Dry Docking, and Riding Crew Need Project-Grade Cost Control

Ship repair operations demand project-grade ERP that handles rapid re-estimation, scope changes during dry docking, expedient works cost tracking, riding crew management, and real-time cost-to-completion visibility.

 

Generic ERPs and asset management systems fail because ship repair is project work, not maintenance scheduling. ProjectVIEW ERP by DANAOS Projects delivers this with BoQ-native cost control.

 

Why Ship Repair Is Project Work, Not Asset Maintenance

 

Ship repair yards operate in a fundamentally different business model than operational asset management. Every repair job is unique. Scope changes constantly—damage assessments reveal hidden structural problems, hidden corrosion, or machinery defects that were not initially visible. Time pressure is extreme: a vessel sitting in dry dock accumulates off-hire costs of USD 20,000–100,000 per day, depending on ship type and market rates. Change orders are the norm, not the exception.

 

Classification society requirements add regulatory complexity. The vessel cannot re-enter service until hull surveys, machinery certifications, and statutory inspections are complete and documented. This is project management, not maintenance scheduling. Each repair is a time-bounded, budget-constrained, scope-variable delivery of compliance and seaworthiness.

 

Generic asset management systems (eMaintenance, CMMS) are designed for routine preventive maintenance, spare parts inventory, and predictive monitoring. They cannot handle rapid re-estimation, multi-disciplinary subcontractor coordination, emergency procurement, or billing complexity. They also lack project cost control—the ability to track estimated costs, actuals, and committed costs side-by-side, and alert managers to overruns in real-time.

 

The Three Modes of Ship Repair

 

Planned Dry Docking

 

Scheduled maintenance, hull treatment, machinery overhaul, regulatory surveys. Repair specifications are defined in advance—a Bill of Quantities (BoQ) is drafted, subcontractors are tendered, budgets are agreed, and work is scheduled to meet class and statutory deadlines.

 

Planned dry docks typically run 4–12 weeks. Costs are front-loaded into budgets and are relatively predictable, but scope changes still occur as paint surveys reveal additional corrosion, or machinery teardown exposes hidden wear.

 

Expedient Works

 

Unplanned emergency repairs. A vessel suffers casualty—hull damage, engine failure, or structural distress during a voyage. The vessel must reach the nearest repair yard. Damage assessment is rapid, repair specifications are drafted on-the-fly, subcontractors are mobilized immediately, and procurement is expedited at premium cost. Speed and cost visibility are critical.

 

The shipowner and insurance surveyor need real-time clarity on cost-to-completion so they can authorize or restrict scope. Expedient works can run 2–8 weeks and carry significant cost volatility.

 

Riding Crew / Voyage Repairs

 

Repairs at sea or in port during the vessel’s operational voyage. Crew and external technicians (via helicopter or supply boat) conduct emergency patch repairs, replace failed components, or perform temporary fixes to keep the vessel operational until it reaches a full repair yard.

 

These repairs are short-duration, remote-coordinated, and must be tracked and billed back to the vessel project or voyage. Materials and labor are sourced locally or by emergency supply chain. Documentation and cost tracking are fragmented because work happens across distributed locations.

 

What Ship Repair Yards Need from ERP

 

BoQ-Based Estimation

 

Repair specifications must be defined as a structured Bill of Quantities—item-by-item breakdown of hull work, machinery work, outfit work, certification, with quantities, units, rates, and total cost per item. This BoQ becomes the control baseline for all downstream activities: procurement, subcontractor contracts, cost tracking, and variation management.

 

Real-Time Cost Control During Execution

 

Actual costs (labor, materials, subcontractor invoices) must be recorded and compared against the BoQ estimates in real-time. The system must flag cost overruns, committed costs (purchase orders, subcontractor change orders), and cost-to-completion forecasts. Managers need this visibility to decide whether to authorize scope increases or curtail work.

 

Change Order Management

 

Scope changes during dry dock (additional corrosion repair, machinery defects, regulatory surprises) must be captured as formal change orders—new BoQ line items, cost and schedule impact, approval chain, billing to shipowner. The ERP must track original scope, authorized changes, and actual execution.

 

Subcontractor Management

 

Ship repair is a multi-trade discipline: steel workers, welders, painters, electricians, machinery technicians, divers (for underwater hull work), rope access specialists. Each trade is typically a separate subcontractor. The ERP must allocate BoQ line items to subcontractors, track interim certifications and sign-offs, monitor progress against schedule, and manage invoicing and variations.

 

Materials Procurement Tied to Repair Specifications

 

Steel plate, paint systems, fasteners, pipe, valves, seals, and consumables must be procured to match repair specifications. In expedient works, procurement is urgent and at premium cost. The ERP must link procurement to BoQ, track purchase orders, receipt, and invoicing, and flag delivery delays that could impact schedule.

 

Machinery Spare Parts Management

 

Engines, pumps, compressors, boilers, and auxiliary machinery require specific spare parts. The ERP must maintain a spare parts library linked to machinery models, track inventory, and flag obsolescence or long-lead-time items. Integration with machinery cost control ensures that spare part costs are captured against the correct repair scope.

 

Multi-Currency Billing

 

Shipowners are international. A vessel registered in Panama, managed in Singapore, insured in London, and repaired in Dubai must have invoicing that reconciles costs in multiple currencies—USD (labor and international subcontractors), EUR (some trades), AED (local services), and others. The ERP must handle multi-currency cost capture and billing.

 

Classification Society Integration

 

The ERP must track certification milestones, survey dates, and approval sign-offs from the vessel’s classification society (Lloyd’s, ABS, DNV, ClassNK, etc.). Non-compliance with survey schedules can delay vessel re-entry to service and trigger off-hire penalties.

 

ERP & Software Comparison for Ship Repair

 

Article content

 

ProjectVIEW ERP for Ship Repair Operations

 

ProjectVIEW ERP is built on a BoQ-native framework—the Bill of Quantities is the core data structure, not an afterthought. Every module in ProjectVIEW connects back to BoQ.

 

Budget Estimation & Bidding

 

ProjectVIEW allows rapid BoQ creation from repair specifications. Estimators define line items (steel repairs, painting, machinery overhaul), quantities, and rates. The system calculates total estimated cost and material schedules. For expedient works, a fast-track BoQ can be drafted and shared with the shipowner within hours.

 

Cost Control

 

As work executes, actual costs are recorded against BoQ line items. Purchase orders, labor timesheets, and subcontractor invoices are matched to line items. ProjectVIEW calculates: Estimated Cost (budget), Committed Cost (POs + subcontractor contracts), Actual Cost (invoices + labor), and Forecast Cost-to-Completion. Variance alerts trigger when actuals exceed estimates by a threshold. This is the fastest way to surface cost overruns and authorize corrective action.

 

Change Order Management

 

When scope changes occur (additional steel repair, machinery defect discovered, regulatory requirement), a formal Change Order is created. It defines new BoQ line items, cost and schedule impact, and approval chain. ProjectVIEW tracks: Original Scope (baseline BoQ), Authorized Changes (approved COs), and Current Scope (original + approved changes). The system prevents unapproved scope creep.

 

Subcontractor Management

 

BoQ line items are allocated to subcontractors by trade. Steel workers get hull repair items. Machinery technicians get engine/pump items. Painters get surface treatment. ProjectVIEW tracks each subcontractor’s scope, interim progress, interim certifications (sign-off by classification society inspector), and invoicing. Interim certifications are tied to BoQ completion milestones, so the system can enforce certification before final payment.

 

Procurement & Materials Management

 

Materials and spare parts are procured against BoQ requirements. For expedient works, ProjectVIEW can flag long-lead-time items and trigger emergency sourcing. All purchase orders are linked to the BoQ, so cost tracking is unified: estimate → committed (PO) → actual (receipt & invoice).

 

Machinery Management

 

Machinery cost tracking is integrated with repair specifications. Engine overhaul, boiler retubing, or compressor replacement is defined as BoQ items. Spare parts, labor, and subcontractor costs for each machinery item are tracked in the Machinery module and reconciled to the BoQ cost baseline. This ensures that machinery work does not slip into uncontrolled territory.

 

What ERP do ship repair yards currently use?

 

Most yards use legacy systems or fragmented tools: BIM for design, MS Project for scheduling, spreadsheets for cost tracking, and separate accounting packages. Few have integrated BoQ-native cost control. This creates visibility gaps and delays in change order authorization.

 

Can a generic ERP handle ship repair?

 

Partially. Generic ERPs (SAP, Oracle) can manage finance, procurement, and HR. But they lack BoQ-native cost control, rapid re-estimation, and multi-discipline subcontractor workflows. Implementation is 12–18 months and requires heavy customization. Ship repair is not the design center for these platforms.

 

What is the difference between dry docking cost control and expedient works cost control?

 

Dry docking is planned, budgeted in advance, and has time to manage vendor contracts and procurement cycles. Expedient works is unplanned, requires real-time re-estimation and approval, and operates at premium cost due to speed. The ERP must support both modes: planned (budget lock-down) and expedient (rapid variance visibility).

 

How does ProjectVIEW handle riding crew repairs at sea?

 

Riding crew repairs can be captured as a sub-project or separate cost code within the vessel project. Labor, materials, and third-party technician costs are recorded in real-time (via mobile or remote data entry) and aggregated to the vessel’s cost baseline. This keeps voyage repairs integrated with the ship’s full repair life cycle.

 

How long does it take to implement ProjectVIEW ERP in a ship repair yard?

 

Typical go-live is 5–6 months: discovery (4 weeks), design & configuration (8 weeks), testing & training (4 weeks), cutover (2 weeks). A yard can often run a pilot project (one repair) in parallel during implementation to validate workflows and identify gaps early.

 

Conclusion

 

Ship repair is not asset maintenance. It is project work—unique, time-constrained, scope-volatile, and subject to real-time cost pressure. Planned dry docking, expedient works, and riding crew repairs all require the same core capability: rapid BoQ-based estimation, real-time cost control, change order management, and subcontractor orchestration.

 

Generic ERPs and asset management systems fall short. They lack BoQ-native cost control and cannot respond at the speed that ship repair demands. ProjectVIEW ERP is purpose-built for capital-intensive project industries. Its trilateral BoQ ↔ WBS ↔ Cost Codes framework delivers project-grade cost control for repair yards, shipbuilders, and marine operators.

 

If your ship repair yard is struggling with cost overruns, delayed change orders, or fragmented visibility across subcontractors and materials, ProjectVIEW offers a faster, simpler path to control.

Calendar