ERP for Tool Making (Werkzeugbau) — software for moulds, dies and one-off precision tooling
Werkzeugbau — tool making — produces moulds, stamping dies, jigs and fixtures, typically one-off, almost always engineered to a customer's product, and almost always under tight intellectual-property restrictions. A tool can carry thousands of unique parts, machining hours measured in the hundreds and a project schedule that runs from design via try-out to series qualification at the customer. An ERP for tool making has to live with project-based engineering, complex one-off BOMs, machining-time estimation as a first-class costing input, milestone billing across design, manufacturing and acceptance phases, and customer-IP handling that is genuinely audit-grade.
Requirements
Every tool is a project. The ERP has to manage projects with WBS, milestones, deliverables and earned-value tracking, not just orders. BOMs are essentially one-off: an injection mould may have 1,500 unique items, almost none of which will ever be used in another tool, which means classic part-reuse master-data strategies fail. Engineering integration with CAD/CAM — Siemens NX, PTC Creo, Catia, hyperMILL, TopSolid, Cimatron — brings parametric data and machining strategies into the ERP. Machining-time estimation is the heart of costing: a five-axis cavity cut takes hours per surface, and a wrong estimate destroys the margin. Milestone billing across design, ordering, manufacturing, try-out and customer acceptance is standard, with payment terms tied to acceptance criteria. Customer IP — the product geometry the tool produces — must be ring-fenced inside the ERP and PLM: access rights, NDA scope and IP-tagged documents are not optional in automotive, medical or consumer-electronics tool-making.
Mandatory functions
Mandatory features start with project management: WBS, scheduling, resource loading, earned-value reporting and tight links from project to engineering, production and finance. The BOM module must handle one-off items at scale — thousands of unique parts per project — without forcing engineering to invent permanent part numbers for every screw. Machining-time estimation either runs in the ERP via parametric rules (per cubic centimetre removed, per surface area cut, per setup) or against an external tool with bidirectional data flow. Milestone billing supports partial invoicing tied to project events, with revenue recognition respecting IFRS 15 and HGB § 253 rules for long-term contracts. Production scheduling manages shared bottleneck capacity (five-axis machining centre, EDM, heat-treatment slot) across parallel projects. CAD/CAM integration brings geometry, machining strategies and tool-path data into the production order with feedback from the shop floor.
Vendor landscape
The DACH tool-making vertical has a small but mature specialist field. ams.erp is the dominant project-and-variant Mechanical Engineering ERP with strong Werkzeugbau credentials. AppliCon (out of the Hamburg area), Stappert and GUS-OS with the Tooling vertical cover the mid-market. Sage b7 and oxaion appear in Mid-Market tool shops with a strong machining background. SAP S/4HANA with Project System (PS) and ETO add-ons is the option of choice for very large tool-making divisions inside automotive or industrial-equipment groups. Microsoft Dynamics 365 Business Central with a tool-making add-on appears in smaller shops aligned to the Microsoft stack. PLM is essential: Siemens Teamcenter, PTC Windchill or 3DEXPERIENCE sit alongside the ERP in almost every serious selection. Selection often pivots on the customer base: an automotive Tier-1 supplier base demands automotive-specific quality and IP processes that not every generalist ERP supports out of the box.
Trends and outlook
Three trends affect new selections. First, additive manufacturing for mould inserts and conformal cooling channels brings new costing and routing models into Werkzeugbau, with hybrid additive-plus-subtractive workflows that the ERP must support. Second, digital twin and instrumented tools: pressure, temperature and cycle-count sensors in the production tool feed back to the toolmaker for refurbishment and warranty work, which raises the bar on IoT-back-to-ERP data flows. Third, customer IP and cyber-security under NIS-2 and ISO 27001 demand auditable access control over both engineering data and ERP transactions, especially for tool makers serving German automotive OEMs and Tier-1 suppliers.
Related Topics
Frequently Asked Questions
Why does a tool maker need project-based ERP rather than discrete-manufacturing ERP?
Because the unit of work is the project, not the production order. Each tool has its own schedule, its own milestone-billing plan and its own profitability case. A discrete-manufacturing ERP optimised for repeated production runs misses the project structure entirely and forces parallel project tracking in Excel, which is exactly where most Werkzeugbau financial pain originates.
How is machining-time estimation handled in practice?
Either inside the ERP via parametric estimation (cost per cubic centimetre removed, per surface area finished, per setup, per heat-treatment step) or against an external estimation tool integrated with the CAM system. Either way, the estimate feeds the quotation and the production plan, and feedback from actual machining times calibrates the rule base over time.
What does milestone billing look like for a tool?
Typical milestones are contract award (down payment), design release, ordering of major plate stock, manufacturing complete, try-out (Erstmusterprüfung), customer acceptance and warranty release. Each milestone triggers a partial invoice, with payment terms negotiated against the project schedule. The ERP must support partial invoicing tied to milestone evidence rather than to ad-hoc dates.
How important is customer-IP handling in Werkzeugbau?
Critical, especially for automotive, medical and consumer-electronics customers. Product geometry, performance parameters and even tool design choices can be commercially sensitive. The ERP, PLM and CAD systems must enforce access rights, document NDA scope and produce an audit trail of who saw what, when — both for compliance and for the rare but expensive IP-leakage dispute.