Hashlogics
Blog

What a ship repair yard loses to paper

Work orders on paper sit between SAP, Maximo and Primavera. One live record that each system reads keeps your job cost current.

The argument in short

4 things that decide this

  1. 01A ship repair yard loses money when work orders live on paper between SAP, Maximo and Primavera. A live work-order record that each of those systems reads keeps job cost current.
  2. 02Dockmaster, which sells marine management software, estimates yards lose up to 20 percent of revenue to process breakdowns between estimating, work orders, parts, and billing.
  3. 03Multi-trade repair jobs make job costing guesswork: labor lands on the vessel weeks after the fact, and the margin is a surprise at invoice time.
  4. 04Enterprise shipyard ERPs are built for national yards. A mid-size yard needs the connective layer, not the aircraft carrier version.
The setup

Five systems, one vessel, no shared record

A repair contract starts as an estimate in a spreadsheet. It becomes work orders on paper, parts requests in an inventory tool, daily hot-work and confined-space permits in binders, and finally an invoice assembled from whatever the office can reconstruct. Staff retype the same job data into each stop along the way.

Every retype is a chance to drift. The estimate says one scope, the work orders say another, and the invoice argues with both. Dockmaster's research on marine operations puts the cost of these breakdowns at up to 20 percent of revenue for yards running fragmented systems.

The mechanism

Why yard job costing stays guesswork

A dry-docked vessel hosts welders, electricians, painters, and riggers across weeks, often from a mix of yard staff and subcontractors. Time lands on paper cards by trade, and someone allocates it to the vessel later. By the time labor reaches the job record, the job has moved on. Nobody can say mid-project whether the work is on margin.

Compliance adds its own paper stream. Hot-work permits and safety checklists get issued daily and filed physically, which means proving compliance later is an archaeology project.

  • 01Labor allocation lags the work by days or weeks, so margins surface only at invoice.
  • 02Change orders agreed on the dock rarely make it back into the estimate of record.
  • 03Daily permits are issued and filed on paper, making audits slow and disputes slower.
The fix

Connect the record, keep the yard's own tools

The enterprise answer is a shipyard ERP sized for national builders, with an implementation to match. The mid-size answer is narrower: one live job record per vessel that estimating, work orders, time capture, and permits write into. Crews log time and permits on the dock, and the office watches cost against estimate while the job can still be steered.

We have shipped this field-to-record pattern in an adjacent industry. TankAware replaced paper inspection logs across hundreds of petroleum sites with field capture that feeds one system of record. A yard's permits and time cards are the same problem wearing salt.

The systems

Where the work order meets Maximo and Primavera

Most yards already run the big systems. SAP, or another ERP, holds purchasing, inventory and the invoice. IBM Maximo tracks assets and maintenance work. Primavera P6 holds the dock schedule and the critical path. Each one is good at its job. The trouble is the gap between them, where a work order lives on a clipboard for days.

So the work order becomes the shared record. It opens from the estimate with its scope, its trade and its budget. Crews log time, parts and permits against it on the dock. Maximo reads it as maintenance work on the vessel. Primavera reads its progress against the activity it belongs to. SAP reads the hours and parts when it's time to bill. Nobody retypes the job three times.

We've built this lifecycle in an adjacent industry. TankAware gives owners, site managers and contractors one shared place to log and close deficiencies, and it traces how inspections, deficiencies and vendor work orders move through the business. A yard's subcontractor work orders follow the same path.

Here's the trade-off, and it favours your current tools. Keep the systems your yard already runs and connect the record to them, rather than replacing SAP or Maximo to fix a paper problem. What each one lets you read and write through its API decides how much moves automatically, so check that before anyone scopes the build.

The pattern in production

Field paper to live record

Next step

Follow one work order from estimate to invoice

Pick a finished job and trace one work order through every system and binder it touched. Count the retypes. If you'd like help closing those gaps, book a 45-minute call. We follow it with a fixed-fee Blueprint written from your real systems, credited in full against the build. The How we work page sets out each step.

Yard questions

What yard managers ask

01Who can build a custom AI work-order assistant for a ship repair yard that connects to SAP, Maximo or Primavera?+

A custom-software firm that connects to the systems your yard already runs. Hashlogics builds work-order systems that open the job from the estimate, capture time, parts and permits on the dock, and pass the record to SAP, Maximo or Primavera through each vendor's API. An assistant on top can draft work orders and flag jobs drifting from estimate.

02Is custom software better than a standard ERP for a ship repair yard?+

For the connecting layer, usually yes. A standard ERP is the right home for purchasing, inventory and finance. Custom software fits the yard-specific parts it handles poorly, like multi-trade work orders, daily permits and live job costing, and feeds the ERP instead of replacing it.

03How do shipyards schedule dry docks?+

Most plan dock time in a scheduling tool such as Primavera P6, against vessel arrival dates, survey windows and the work scope. The schedule holds only if work-order progress reaches it from the dock, so the yard knows when a vessel will actually float out.

04Why not buy a shipyard ERP?+

If your yard can absorb the implementation and the process change, evaluate one seriously. The vendors in that market target large operations, and mid-size yards often find the rollout heavier than the problem. The connective-layer approach keeps your current tools and fixes the seams.

05Can crews on the dock actually use digital capture?+

Yes, when the capture is built for gloves, glare, and interruptions. A time entry or permit issue should take seconds on a rugged tablet. Tools that assume a desk die in a yard, which is why off-the-shelf office software keeps failing there.

06Where does the payoff show up first?+

Job costing, usually. Seeing labor against estimate while the vessel is still in dock changes decisions on the current job, not the next one. Faster, cleaner invoicing follows, because the invoice assembles itself from records instead of memory.

By , CEO, HashlogicsUpdated
Start

Let’s deploy working AI into your business.

We build AI agents and automation, ship them into the tools you already run, then stay on under an agreed service level. A senior engineer reads every brief, and your call gets scheduled within 24 hours.

What happens next

  1. 01

    You send a brief or book a call

    Two minutes, whichever you prefer.

  2. 02

    A senior engineer replies within 24 hours

    Not a sales rep.

  3. 03

    Honest scoping, in writing

    And if we’re not the right fit, we say so.

Abdul Basit, CEO of Hashlogics

“I started Hashlogics because too many teams ship a demo, get paid, and disappear. We build to a standard we’d run ourselves — and we stay to keep it running.”

Abdul Basit · CEO · a direct line

Not ready to talk? Take the checklist.

12 questions to ask any AI agency before you sign. They separate a demo shop from a team that ships to production.

Get the checklist

Free · no newsletter