Häufig gestellte Fragen
Which ERP is suitable for small machine builders with fewer than 50 employees?
For smaller machine builders, the main candidates are SAP Business One, Microsoft Dynamics 365 Business Central and mid-market-focused solutions such as godesys or axavia, which can be implemented with manageable effort. The decisive factor is less the headcount than the share of variant-rich one-off and make-to-order manufacturing, because a high engineer-to-order share requires a powerful configurator even in small companies. In practice, the right setup varies considerably depending on production type, size class and the customising depth of the specific ERP setup. A well-founded answer therefore always requires a look at the company's individual business processes and strategic IT roadmap.
What does an ERP for machine building cost?
Realistically, licence and implementation costs are in the range of roughly 4,000 to 12,000 euros per user depending on vendor and depth of adaptation; with 50 users, the total budget for the initial implementation typically falls between around 250,000 and 700,000 euros. Licence or subscription fees typically account for only around 25 to 35 percent of project costs, with the larger remainder going to implementation, customising, training and data migration. The migration of complex bill-of-materials and variant structures in particular is a frequently underestimated cost driver in machine building. Viewed over the entire period of use, companies should calculate the total cost of ownership over five to seven years rather than just the purchase price; our TCO calculator guide provides a sound logic for this.
Cloud or on-premises for a machine building ERP?
Both operating models are widespread in the industry; there is no universally correct answer. Larger and internationally active machine builders are increasingly relying on cloud-native or hybrid architectures, while smaller companies with deep customisations frequently still run on-premises. In the mid-market, a growing share of new projects now starts cloud-first, but cloud migration in machine building tends to proceed more slowly than in wholesale, for example, because productive on-premise systems often remain in parallel use for five to ten years. Important trade-off criteria are data sovereignty, integration needs with CAD/PLM, and the vendor's long-term update and maintenance strategy.
Why does machine building need an industry-specific ERP instead of a standard solution?
Classic inventory management or standard ERP systems quickly reach their limits in machine building as soon as products are designed project-specifically, carry multi-level bills of materials and are manufactured over weeks or months. An industry-specific ERP for machine building frequently comes with functions such as a variant configurator, concurrent costing, project controlling and service and spare parts management largely preconfigured, thereby reducing adaptation effort and implementation risk. Standard solutions can in principle also be upgraded, but this often requires extensive and expensive customising that complicates later updates. Which path makes sense depends on the production type and the share of one-off and make-to-order manufacturing.
How long does implementing a machine building ERP take?
Timelines vary greatly with company size, process complexity and depth of adaptation: lean, largely standard-based mid-market projects can go live in around 6 to 12 months, while variant-rich engineer-to-order ventures with deep CAD/PLM integration tend to take 12 to 24 months, and larger multi-site or group projects run even longer. An ERP implementation is not a pure IT project but a reorganisation effort encompassing process analysis, conception, realisation, testing, training and a stabilisation phase. The bottleneck in machine building is frequently the migration of complex bill-of-materials and variant structures, which alone can take several months. Promises of just a few weeks are generally unrealistic for demanding engineer-to-order manufacturers; neutral selection support helps to assess timelines and vendors realistically.
Which functions and interfaces must a machine building ERP necessarily offer?
Central are a deep mapping of engineer-to-order and make-to-order, a powerful variant configurator with rule-based bills of materials, and concurrent costing at project and order level. Equally important are clean interfaces to CAD and PLM systems such as SolidWorks, Inventor or Creo, ideally with bidirectional BOM synchronisation, as well as a connection to an MES for shop floor manufacturing. Added to this are service and spare parts management across the entire machine lifecycle and internationalisation functions such as languages, currencies, Intrastat and customs, since German machine building has an export ratio of around 80 percent. Which of these functions take priority should be weighted in the requirements document based on your own processes.