, ,

A Yacht Builder Picked Its ERP So Design Changes Stop Getting Rekeyed

N23D
A Yacht Builder Picked Its ERP So Design Changes Stop Getting Rekeyed

A yacht builder with more than 60 years behind it just picked an ERP for one reason above the rest: so a design change stops getting rekeyed. On October 8, Syspro announced that British luxury motor yacht maker Fairline Yachts selected Syspro cloud ERP and its Syspro Torque industrial AI platform to run operations from design and engineering through to aftersales.

The press release spells out the pain plainly. Engineering change control, bills of materials, material requirements planning, shop floor and quality management are being put on the same data, so that “a design change flows through to purchasing and scheduling without being rekeyed or chased.” Anyone who has watched a buyer order parts off last month’s BOM knows what that sentence is worth.

Fairline testing facility in Ipswich with four yachts moored alongside

Fairline is not alone this week. Infor’s CloudSuite Industrial October 2026 release leans on supplier variability planning and an Enterprise Quality Hub, and process-manufacturing ERP vendor Wherefour added an MCP connector that gives AI tools read-only access to inventory, production and traceability data. The common thread: vendors are selling AI on top of ERP, but the hard part is still getting engineering, purchasing and quality to agree on one record.

That is the gap that matters for anyone building boats, machines or aircraft. AI that “logs every decision under operator control” is only as good as the BOM revision it reads. If the engineering change lives in one system and the purchase order in another, the AI just finds the wrong answer faster.

Fairline Squadron 68 flybridge motor yacht exterior

In N23D, ERP does not import the BOM from PLM; it reads the same released part identity. When an engineering change is released, open purchase requisitions, MRP demand and MES work orders that pointed at the old revision are flagged before anyone orders or builds against it. It is one native Rust binary, local-first, with a permanent license, so the change thread does not depend on an integration project.

Fairline’s choice is a good signal: manufacturers are buying ERP for the digital thread, not the general ledger. The question to ask any vendor, including us, is simple. When engineering releases Rev C at 3pm, what does purchasing see at 3:01?

Sources / References