Häufig gestellte Fragen
Which functions must an ERP for metal processing include?
An ERP for metal processing should map both discrete manufacturing via bills of materials and routings and process-oriented material handling for coils, sheets and bars including remnant quantities. Central features are contract manufacturing with and without customer-supplied material, a variant configurator for sheet metal, profiles and welded assemblies, and batch and heat traceability via material certificates. Added to this are shop-floor and machine data collection (BDE/MDE) and MES connectivity to sawing, punching, laser and welding machines, as well as post-costing that compares planned against actual machine and material costs. An integrated CAD/PLM interface to systems such as SolidWorks, Inventor or Creo prevents duplicate entry of geometry and master data.
How does an ERP support material certificate and batch management according to EN 10204?
The EN 10204 standard (adopted in Germany as DIN EN 10204) defines the types of inspection documents for metallic products, including the 3.1 inspection certificate, which is confirmed by the manufacturer through a body independent of the production department, and the 3.2 certificate, which is additionally countersigned by an independent third party. An ERP should store these certificates digitally against the material, batch or heat and automatically pass them on to the resulting parts when coils, sheets or bars are cut. This preserves seamless traceability from delivery to the end product, which is decisive for safety and compliance in mechanical engineering, the energy sector and pressure equipment. When needed, the right certificate can then be enclosed with the respective delivery without a manual search.
Does an ERP help with offcut and nesting optimisation?
ERP and MES systems frequently integrate nesting modules for sheets and profiles that arrange multiple parts on a sheet or coil in such a way that offcut is minimised and material utilisation is maximised. The optimisation algorithms take into account not only pure material consumption but often also manufacturing costs and lead times, so that utilisation and effort can be weighed against each other. Results are handed over to CAM and machine control systems via formats such as DXF or CSV, while the ERP books remnant quantities back as usable stock. How large the material savings actually are depends heavily on part geometry, lot sizes and formats and should be assessed per project.
What does CBAM mean for metal processing companies and their ERP?
The EU carbon border adjustment mechanism CBAM covers, among other goods, iron, steel and aluminium and entered its definitive phase on 1 January 2026, in which importers must record and declare the embedded emissions of their imports; the purchase of CBAM certificates, however, has been postponed to 1 February 2027, so the certificates for 2026 imports will only be acquired in 2027. The decisive figure is a quantity threshold of 50 tonnes net mass per year and importer; imports below this are largely exempt, which according to the European Commission relieves around 90 percent of the companies originally affected, while about 99 percent of emissions remain covered. Anyone importing above the threshold must record import quantities and the associated greenhouse gas emissions and declare them annually in verified form. An ERP can support this by keeping quantities, origin and emissions data structured per material and supplier and making them evaluable for CBAM reporting.
How are machines connected to the ERP via BDE/MDE and OPC UA?
Machine connectivity increasingly relies on the open standard OPC UA, which enables vendor-independent data exchange between machines and higher-level systems such as MES and ERP. Specifically for machine tools, the VDW association has established umati (universal machine technology interface), an OPC UA-based companion specification that allows uniform integration of different machines. This makes it possible to automatically capture operating and machine data (BDE/MDE) such as run times, faults and piece counts and feed them back into order management and post-costing. The integration effort varies with the machine park, controller generation and interface depth and should be assessed per machine type before the project starts.
What does a metal processing ERP cost?
Realistic implementation costs for a metal processing ERP in the mid-market range roughly between several hundred thousand and over one million euros over the first three to five years, depending on user count and depth of customisation. The MES/BDE integration with welding, punching and laser cutting machines is a major cost driver, since each OPC UA connection has to be set up separately per machine type. On top of this, on-premise models incur annual maintenance and update fees in the usual range of around 18 to 22 percent of the licence sum, or alternatively a cloud subscription billed per user per month. A reliable estimate only emerges from the specific requirements specification; more in our guide ERP costs.
Cloud or on-premise – what suits metal processing?
Both operating models are widespread in the industry, and the choice depends on the depth of customisation, the existing IT and the machine connectivity. Cloud solutions are gaining ground for smaller and mid-sized deployments because they outsource operations and updates and are ready to run faster. On-premise remains the first choice where highly individual processes, deep MES coupling on the shop floor or particular data sovereignty requirements are paramount. More on this trade-off at Cloud vs on-premise.
How long does implementing an ERP take in metal processing?
In the metal processing sector, mid-market ERP implementations typically take around 10 to 20 months, while larger multi-site projects can well require 30 to 48 months. Worker acceptance of BDE terminals on the shop floor requires intensive training and usually a two- to three-month pilot area before the full roll-out. A substantial part of the project duration goes to concept work, customising and data migration, with the rest spent on testing, training and go-live. You will find an implementation checklist at ERP implementation checklist.