Is custom software better than a standard ERP for a ship repair yard?
Big shipyard ERPs suit national yards with IT departments. Your repair yard most likely needs three workflows built well, connected to the books you keep.
The short answer
For a ship repair yard, a standard shipyard ERP is enough while your work fits its standard workflow; custom software is better for the steps it leaves to spreadsheets, phone calls and re-keying, and the lower-risk route is to build that layer around the ERP or accounting system you already run rather than replace it.
You'll see enterprise systems such as IFS Cloud on any shortlist, and older shipbuilding suites like Logimatic's MARS, which AVEVA bought in 2010. Floorganise's Floor2Plan handles production planning, and SSI ShipConstructor handles 3D design and engineering.
Pick a shipyard ERP if your yard can staff a long rollout and needs estimating, procurement, production and finance in one system. If you run a mid-size repair yard, a scoped build fixes the three things that bleed money now. Those are live job costing per vessel, digital work permits, and dock scheduling that survives change orders. An ERP is a program; your build is a project.
In most yards, estimates, work orders, parts, schedules and billing live in separate systems, with your staff re-typing between them. Enterprise vendors solve this with breadth, and they earn their place in new-build and naval work. For a hundred-person repair yard, that breadth is the problem: a long rollout assumes IT staff, process discipline and budget you rarely carry.
A custom build is narrower on purpose. You pick the two or three workflows where money leaks and build them around how your yard already works. Then you connect them to the accounting system you're keeping. Multi-trade job costing usually comes first, because guessing margins on a two-month vessel stay is how yards lose quietly.
Side by side
A program against a project.
| Dimension | Shipyard ERP | Scoped custom build |
|---|---|---|
| Built for | Large yards: new-build, naval, hundreds of trades | Mid-size repair and service yards |
| Scope | Everything: estimating to finance | The workflows that bleed: costing, permits, scheduling |
| Implementation | A long program with process change across the yard | Scoped per workflow, shaped to current practice |
| IT burden | Assumes dedicated staff and admin roles | Runs maintained, with a named engineer instead of a department |
| Compliance records | Modules configured to class and HSE needs | Hot-work and confined-space permits digital from day one |
| Cost shape | Enterprise licence plus implementation services | Engineering per workflow, then hosting and maintenance |
Shipyard ERP
Where it wins
- One vendor covers the yard end to end, estimating through finance.
- Proven in naval and new-build programs where auditors expect it.
- Class-society and regulatory reporting arrives as configuration, not code.
- Reference customers exist at the largest yards in the world.
Where it hurts
- Implementation length and cost assume an enterprise, not a hundred-person yard.
- Process change runs yard-wide before the first benefit lands.
- Modules you will never use are part of the licence anyway.
- Small-yard requests sit low on an enterprise vendor's roadmap.
Scoped custom build
Where it wins
- Live job costing per vessel and trade, without waiting for month-end.
- Digital permits with the sign-offs and time limits your HSE process requires.
- Dry-dock and berth scheduling that absorbs change orders instead of breaking.
- Connects to existing accounting rather than replacing it.
Where it hurts
- Narrow by design: it will not run procurement or finance for you.
- The yard must commit real people to scoping, or the build encodes guesses.
- Maintenance is a standing arrangement, not a one-time purchase.
- A yard heading into naval prime-contract work will eventually need ERP-grade records anyway.
How to choose
Ask what you couldn't answer last month. If your question was which vessel made money and which trades overran, you need a costing build, not an ERP.
- 01Choose an ERP if the yard runs new-build or naval programs where end-to-end enterprise records are contractual.
- 02Choose a custom build if job costing, permits or dock scheduling still run on paper and spreadsheets.
- 03Sequence them where growth is real: build the costing and permit layer now, and let it feed an ERP later if the yard scales into one.
- 04Choose neither before mapping one vessel's job end to end. The map shows which workflows actually leak.
Paper field records replaced at industrial scale
Questions yard managers ask
01Is custom software better than a standard ERP for a ship repair yard?+
Custom software is better for the workflows a standard ERP leaves to spreadsheets: live job costing per vessel, digital permits and dock scheduling. If you run new-build or naval programs that need enterprise records end to end, an ERP such as IFS Cloud is the stronger choice. Most repair yards build the narrow layer and connect it to the accounting they keep.
02Can I use a standard shipyard ERP and custom software together?+
Yes. Your ERP keeps procurement and finance, while a custom layer handles costing, permits and scheduling. It writes results back through whatever API or export your ERP version offers, and IFS Cloud publishes OpenAPI specs for its REST APIs.
03What software does a mid-size ship repair yard actually need?+
Three systems cover most of your pain. First, job costing that tracks labour and material per vessel and trade in real time. Next come digital work permits for hot work and confined spaces, and a scheduling view of docks and berths that survives change orders. Everything else can stay where it is until those three run cleanly for you.
04How long does a shipyard ERP take to implement?+
Enterprise shipyard systems are sold with implementation programs measured in seasons, because they change estimating, procurement, production and finance at once. A scoped custom workflow is a project, accepted against written criteria. You're comparing a program against a project.
05Can custom software handle class and HSE compliance records?+
Yes, where the records are defined. Your permits, inspections and sign-offs are structured documents with rules, which is exactly what software captures well. We have replaced paper inspection logs across hundreds of fuel sites with signed digital records, and the same record-keeping shape applies dockside.
06How much does custom software cost for a ship repair yard?+
You won't get an honest number before an engineer maps your yard. Enterprise ERP pricing is licence plus a services program, quoted per yard. A custom build starts with a free scoping call, then a fixed-fee Blueprint credited in full against the build. If the plan isn't one you'd act on, you don't pay for it.
07Will I lose my data if I move off a standard shipyard ERP?+
Not if you plan it. Before the switch, export your vessels, jobs, cost history and open purchase orders, and keep finance in one system through the cutover. You may never need the move, because your custom layer sits beside the ERP.
Related
- Industrial: AI, automation and custom software →Our industrial hub: AI, automation and custom software.
- Shipyard software development →Software we build for ship repair and service yards.
- What does ship repair job costing need? →Labour, material and change orders per vessel, answered.
- Custom software development →How scoped builds are priced and run.
- Oil and gas software development →Field inspection and compliance work in adjacent heavy industry.
- Build vs buy software →How you decide between building and buying, in general.
- How we work →Our free scoping call, the fixed-fee Blueprint and milestone pricing.

