Article

ERP for heavy equipment manufacturers: what to get right

Heavy equipment manufacturers need an ERP that handles deep, changing bills of materials, long-lead purchasing, serial records and aftermarket service, not just orders and invoices. Get those right and the rest has something reliable to build on.

The short answer

Heavy equipment is built in low volumes from many parts, often to specification, then supported in the field for years. The ERP must get five things right:

  1. Multi-level bills of materials that change without breaking orders in progress.
  2. Planning and purchasing around long-lead components.
  3. Serial records: what was built, for whom, from which parts.
  4. Job costing showing each machine's margin during the build.
  5. Aftermarket service: parts, warranty, maintenance.

Get these right and the rest can be simple; get them wrong and spreadsheets take over.

Why heavy equipment is different

Most ERP demos show one product made repeatedly from a stable recipe. Heavy equipment is different:

Configure or engineer to order

Options, attachments, custom engineering: each order can have its own BOM.

Deep product structures

Frame, hydraulics, drivetrain, cab, electrical; ERPNext supports multi-level BOMs per sub-assembly.

Long build cycles

Weeks per unit: large work in progress, so costing must be timely.

Long-lead components

Engines, axles and hydraulics ordered months ahead, sometimes before the order is final.

Years of support

Parts, warranty claims and scheduled maintenance can be a significant part of the business.

Get the bill of materials right first

The BOM drives planning, purchasing, costing and service. Decide early:

DecisionWhat to settle
Levels in the ERPWhich stay in engineering tools; detailed structures are often simplified into manufacturing BOMs
OptionsBase plus option BOMs (easier to maintain) or a BOM per configuration (simpler to understand)
Engineering changesWhich orders a replaced part affects; is old stock used up first?
OwnershipEngineering, production or a named administrator; without one, BOMs drift from what is built

Plan purchasing around lead times

In ERPNext, a work order signals the manufacture of a quantity of an item and generates material requirements from its BOM. For heavy equipment, add:

  • Accurate lead times, reviewed regularly with suppliers.
  • Forecast or reservation buying of major components before the order is final.
  • Supplier performance tracking: one late axle delays a whole machine.
  • Landed cost: duties, freight and brokerage on parts cleared through the CBSA's CARM system.

Track every machine by serial number

Serial tracking connects production to service; an ERPNext serial number record holds each unit's location, warranty and maintenance contract expiry. Serialize every machine and major component (engines, transmissions), keep an as-built record linking them, and put customer, delivery date and warranty terms on the machine. When a supplier recalls a component batch, this finds the affected machines.

Cost each job while it is being built

Standard costing rarely works for configured, low-volume products; most manufacturers need job or project costing:

  • Material at actual or moving average cost
  • Labour and machine time per job
  • Overhead applied consistently
  • Quoted vs actual cost per machine

Many systems fall short here: test with real data before you commit.

Support the installed base

Aftermarket parts and service often carry better margins than new equipment.

Parts sales

Cross-references for supersessions and alternate part numbers.

Warranty claims

Linked to the machine serial and, where relevant, recovered from suppliers.

Scheduled maintenance

ERPNext maintenance schedules plan regular service visits for customer equipment.

Dealers and field service

Visibility for dealers who sell and service your equipment.

Canadian considerations

AreaWhat to set up
CurrenciesBuying in USD, selling in CAD and USD: multi-currency pricing, purchasing and revaluation from day one
Sales taxGST/HST and PST vary by province and customer; record exemptions properly
French documentsQuotes, invoices, manuals and warranty terms for Quebec customers
Data locationCheck supported Canadian cloud regions; they help with residency but do not answer every requirement

General information only: confirm tax treatment with your accountant.

Hypothetical first phase
Demonstration, not a client project

Hypothetical example. A manufacturer builds forestry attachments in three base models with about twenty options. Today, sales quotes in a spreadsheet, engineering keeps BOMs in CAD files, and production builds from printed drawings. Costs are only known at year-end.

A sensible first phase would be: a manufacturing BOM per base model plus option BOMs; work orders created from sales orders; serial numbers on every finished unit and on engines; and a simple job cost report comparing quoted and actual cost. Service, dealer access and detailed shop-floor time tracking would follow in a second phase, once the core data is trusted.

Requirements checklist

Products and engineering

  • How deep are our BOMs, and which levels must the ERP manage?
  • How are options and custom engineering represented?
  • Who approves engineering changes, and how will they reach open orders?

Planning and purchasing

  • Which components have lead times longer than our build cycle?
  • Do we buy major components early, and how is that risk tracked?
  • Are duties, freight and brokerage included in component cost?

Traceability and service

  • Which items need serial numbers, and do we need as-built records?
  • How are warranty claims recorded and recovered from suppliers?
  • Do dealers or field technicians need access?

Costing

  • Can we see quoted versus actual cost for each machine?
  • How are labour and overhead applied?

Limitations

No ERP removes the need for disciplined data: with inaccurate BOMs or uncontrolled engineering changes, it plans and costs the wrong thing faster. Some engineer-to-order businesses also need configuration or engineering tools alongside the ERP.

Next step

Our ERP implementation service maps these processes before any configuration. See also Prometheus ERP and our work with manufacturers.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

  1. Bill Of Materials, ERPNext documentation (Frappe)
  2. Work Order, ERPNext documentation (Frappe)
  3. Serial Number, ERPNext documentation (Frappe)
  4. Maintenance Schedule, ERPNext documentation (Frappe)
  5. CARM: Assess and pay duties and taxes on imported commercial goods, Canada Border Services Agency

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.

Talk to Promatics

Get a straight answer for your situation

General advice only goes so far. Tell us about your environment and we will tell you what we would do, what it would cost and what to watch out for.

  • A named specialist who owns the outcome, not a chat window
  • Advice checked against your actual systems, contracts and risks
  • Written scope and costs in CAD before any work starts