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. In practice, that means 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 therefore 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. For one thing, every repair job is unique. Scope also changes constantly, because damage assessments reveal hidden structural problems, hidden corrosion, or machinery defects that no one could see at first. In addition, 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. As a result, change orders are the norm, not the exception.

 

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

 

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

 

The Three Modes of Ship Repair

 

Planned Dry Docking

 

This mode covers scheduled maintenance, hull treatment, machinery overhaul, and regulatory surveys. Here, the yard defines repair specifications in advance. First, it drafts a Bill of Quantities (BoQ). Then it tenders subcontractors, agrees budgets, and schedules work to meet class and statutory deadlines.

 

Planned dry docks typically run 4–12 weeks. Budgets carry most costs up front, so costs are relatively predictable. Still, scope changes occur as paint surveys reveal additional corrosion, or machinery teardown exposes hidden wear. That is why dry docking cost control matters even in planned work.

 

Expedient Works

 

Expedient works are unplanned emergency repairs. For example, a vessel suffers casualty—hull damage, engine failure, or structural distress during a voyage. The vessel must then reach the nearest repair yard. Damage assessment is rapid, and the yard drafts repair specifications on the fly. Meanwhile, it mobilizes subcontractors immediately and expedites procurement at premium cost. So speed and cost visibility are critical.

 

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

 

Riding Crew / Voyage Repairs

 

These are repairs at sea or in port during the vessel’s operational voyage. For instance, 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 and remote-coordinated. Still, the yard must track them and bill them back to the vessel project or voyage. Teams source materials and labor locally or through an emergency supply chain. As a result, documentation and cost tracking are fragmented, because work happens across distributed locations.

 

What Ship Repair Yards Need from ERP

 

BoQ-Based Estimation

 

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

 

Real-Time Cost Control During Execution

 

Next, the system must record actual costs (labor, materials, subcontractor invoices) and compare them against the BoQ estimates in real-time. It must also flag cost overruns, committed costs (purchase orders, subcontractor change orders), and cost-to-completion forecasts. After all, managers need this visibility to decide whether to authorize scope increases or curtail work.

 

Change Order Management

 

In addition, the ERP must capture scope changes during dry dock (additional corrosion repair, machinery defects, regulatory surprises) as formal change orders. Each one covers new BoQ line items, cost and schedule impact, approval chain, and billing to the shipowner. The ERP must also 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. Typically, each trade is a separate subcontractor. Therefore, 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

 

Similarly, the yard must procure steel plate, paint systems, fasteners, pipe, valves, seals, and consumables to match repair specifications. In expedient works, procurement is urgent and at premium cost. So 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. Thus, 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 also ensures that spare part costs land against the correct repair scope.

 

Multi-Currency Billing

 

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

 

Classification Society Integration

 

Finally, 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

 

DANAOS Projects built ProjectVIEW ERP on a BoQ-native framework. In other words, 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 then calculates total estimated cost and material schedules. For expedient works, the team can draft a fast-track BoQ and share it with the shipowner within hours.

 

Cost Control

 

As work executes, the system records actual costs against BoQ line items. It also matches purchase orders, labor timesheets, and subcontractor invoices to line items. ProjectVIEW then 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), the team creates a formal Change Order. 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). As a result, the system prevents unapproved scope creep.

 

Subcontractor Management

 

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

 

Procurement & Materials Management

 

Teams procure materials and spare parts against BoQ requirements. For expedient works, ProjectVIEW can flag long-lead-time items and trigger emergency sourcing. Because every purchase order links to the BoQ, cost tracking is unified: estimate → committed (PO) → actual (receipt & invoice).

 

Machinery Management

 

Machinery cost tracking connects directly to repair specifications. For instance, the BoQ defines engine overhaul, boiler retubing, or compressor replacement as line items. The Machinery module then tracks spare parts, labor, and subcontractor costs for each machinery item and reconciles them 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 to 7 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

 

In summary, ship repair is not asset maintenance. Instead, 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, however, 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.

George Tsolakis

About the author

George Tsolakis

Chief ERP Architect, DANAOS Projects

George (Georgios) Tsolakis is Chief ERP Architect at DANAOS Projects and a subject-matter expert in construction ERP architecture, engineering economics, cost accounting and construction cost control. With more than 30 years of experience building construction-specific enterprise technology, he conceived ProjectVIEW ERP and remains its principal architect and lead developer, directing business analysis, product architecture, advisory, implementation and support for project-based…