The short answer
Heavy equipment is built in low volumes, from many parts, often to a customer's specification, and then supported in the field for years. An ERP for this kind of manufacturer has to get five things right:
- Multi-level bills of materials that can change without breaking orders already in progress.
- Purchasing and planning that account for long lead times on major components.
- Serial-level records of what was built, for whom, from which parts.
- Job or project costing that shows margin on each machine while it is being built.
- Aftermarket service: parts, warranty and maintenance for the installed base.
A system that handles these well can be simple elsewhere. A system that handles them poorly will be worked around with spreadsheets, however good its other features are.
Why heavy equipment is different
Most ERP demonstrations show a manufacturer making the same product repeatedly from a stable recipe. Heavy equipment rarely works like that:
- Configure-to-order or engineer-to-order. Customers choose options, attachments and sometimes custom engineering. Each order can have its own bill of materials.
- Deep product structures. A machine is made of sub-assemblies (frame, hydraulics, drivetrain, cab, electrical), each with its own components. ERPNext, for example, supports multi-level BOMs in which each sub-assembly can have its own BOM (ERPNext documentation).
- Long build cycles. A single unit can be in production for weeks, so work in progress is large and costing needs to be timely.
- Expensive, long-lead components. Engines, axles and hydraulic systems may need to be ordered months ahead, sometimes before the customer order is final.
- Years of support after delivery. Replacement 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:
- Which BOM levels you will manage in the ERP and which stay in engineering tools. Very detailed engineering structures are often simplified into manufacturing BOMs.
- How options are modeled. A base BOM plus option BOMs, or a separate BOM per configuration. The first is easier to maintain; the second is simpler to understand.
- How engineering changes flow in. When a part is replaced, the ERP needs to know which orders it affects and whether stock of the old part should be used up first.
- Who owns the BOM. Engineering, production or a named BOM administrator. Without a clear owner, BOMs drift away from what is actually built.
Plan purchasing around lead times
Production planning in an ERP turns demand into work orders and material requirements. In ERPNext, a work order signals the manufacture of a quantity of an item and generates material requirements from its BOM (ERPNext documentation). For heavy equipment, add:
- Accurate lead times on long-lead items, reviewed regularly with suppliers.
- Forecast or reservation buying for major components, so that the purchase happens before the sales order is final.
- Supplier performance tracking, because one late axle delays a whole machine.
- Landed cost for imported components. Duties, freight and customs brokerage on goods entered through U.S. Customs and Border Protection (CBP) belong in the cost of the part (CBP).
Track every machine by serial number
Serial tracking connects production to service. In ERPNext, a serial number record tracks each unit's location, warranty and maintenance contract expiry dates (ERPNext documentation). For heavy equipment, you usually want:
- a serial number for each finished machine and for major serialized components (engines, transmissions);
- an as-built record linking the machine to the component serials fitted;
- the customer, delivery date and warranty terms on the machine record.
When a supplier issues a recall on a batch of components, this is how you find the affected machines.
Cost each job while it is being built
Standard costing alone rarely works for configured, low-volume products. Most heavy equipment manufacturers need job or project costing:
- material issued to the work order at actual or moving average cost;
- labor and machine time recorded against the job;
- overhead applied consistently;
- a comparison of quoted cost against actual cost, per machine.
This is where many systems fall short. Test it with real data before you commit.
Support the installed base
Aftermarket parts and service often carry better margins than new equipment. The ERP should support:
- parts sales with cross-references (supersessions, alternate part numbers);
- warranty claims linked to the machine serial and, where relevant, recovered from suppliers;
- scheduled maintenance, such as ERPNext's maintenance schedules, which plan regular service visits for customer equipment (ERPNext documentation);
- dealer or field service visibility, if dealers sell and service your equipment.
US considerations
- Currencies. Many US equipment makers import components priced in other currencies and sell in USD, and some also sell abroad in other currencies. Configure multi-currency pricing, purchasing and revaluation from the start.
- Sales and use tax. There is no federal sales tax. State and local sales and use tax rules vary by state and by customer, and exemptions for some buyers (resale, manufacturing or government, for example) need to be recorded properly with their certificates.
- Customs and trade documents. For imported and exported components and machines, keep tariff classification, country of origin and any USMCA claims on the item and the purchase or sales record so that duties are costed correctly.
- Data location. If you prefer US hosting, check which cloud regions the ERP supports. Region choice helps with data residency but does not answer every requirement on its own.
This is general information. Confirm tax treatment with your accountant.
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 design-software 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 many levels 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 before the order is final? 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 labor and overhead applied?
Limitations
No ERP removes the need for disciplined data. If BOMs are inaccurate or engineering changes are not controlled, the ERP will plan and cost the wrong thing more quickly. Some engineer-to-order businesses also need product configuration or engineering tools that sit alongside the ERP rather than inside it.
Next step
If you are choosing or reconfiguring an ERP for equipment manufacturing, our ERP implementation service starts by mapping 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.
- Bill Of Materials, ERPNext documentation (Frappe)
- Work Order, ERPNext documentation (Frappe)
- Serial Number, ERPNext documentation (Frappe)
- Maintenance Schedule, ERPNext documentation (Frappe)
- U.S. Customs and Border Protection, U.S. Customs and Border Protection (CBP)
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.