ams.erp — engineer-to-order specialist for capital-equipment manufacturing
ams.erp is the engineer-to-order ERP from ams.Solution AG, headquartered in Krefeld in Germany. The vendor's positioning is unusually focused: rather than a general manufacturing ERP, ams.erp targets engineer-to-order, capital-equipment and project-based manufacturing specifically, with workflows built around the operational reality of building one-of-a-kind or low-volume engineered products. Target customers are mechanical engineering, plant construction, capital-equipment manufacturers, mould and tool makers, and similar single-piece or small-batch project manufacturers in the German Mid-Market. The functional depth in project-based manufacturing is among the strongest in the mid-market segment, which is the recurring selection driver for ams.erp customers.
Overview
ams.Solution AG sits in a deliberate manufacturing-vertical niche: ETO (engineer-to-order) and project-based manufacturing for the German Mid-Market. Where competing mid-market ERPs treat project-based manufacturing as a module bolted onto general discrete-manufacturing functionality, ams.erp is built around the project-manufacturing pattern from the data model up. That architectural decision pays back for customers whose operational reality is building configured machines, complete plants, custom moulds or one-off engineered products — the kind of work where each customer order is essentially a small engineering project. Ownership is private and the management team is long-tenured. Customer count is in the hundreds of focused mid-market ETO implementations, with strong presence in mechanical engineering, plant construction, mould and tool making and electrical-engineering project businesses in the German Mid-Market.
Functional sweet spot
Engineer-to-order project management is the strongest pillar. Project structures with multi-level work breakdown, integrated quotation and project costing, project cash-flow forecasting, multi-stage approval workflows and tight cross-module project visibility — cost rollups across project work, purchasing, production and external service — cover the operational core of ETO businesses. CAD integration through dedicated connectors (SolidWorks, Autodesk, Siemens NX, PTC Creo and others) keeps engineering bills of material aligned with production. Variant configuration handles configurable products at the level ETO businesses need. Production planning supports project-based capacity and material requirements planning with the kind of finite-scheduling logic ETO operations require. Field service supports installed-equipment after-sales workflows. Financial accounting is GoBD-compliant with native DATEV integration, ZUGFeRD and XRechnung outbound invoicing. CRM and document management round out the suite at mid-market depth.
DACH positioning
ams.erp has substantial DACH presence in mechanical engineering, plant construction, capital-equipment manufacturing, mould and tool making and electrical-engineering project businesses. Customer size typically ranges from 50 to 800 employees, with concentrated geographic strength in North Rhine-Westphalia (the vendor's home region) and southern Germany. GoBD compliance is delivered out of the box, with audit trail, journal export and GDPdU support. DATEV connectivity is mature and native. ZUGFeRD and XRechnung outbound invoicing are supported. The partner ecosystem is concentrated, with ams.Solution AG's own consulting team handling most implementations directly — the vendor-delivered model is operationally significant for ETO customers, who benefit from consultants who have actually worked on similar project-manufacturing patterns rather than generalist ERP implementers. Localisation for Austria and Switzerland is mature. International rollouts among German-headquartered ETO manufacturers are increasingly common.
Pricing and implementation
ams.erp is priced as a perpetual licence with annual maintenance or as a subscription, with bundles depending on user count and functional scope. Public list pricing is not standardised; mid-market ETO deals typically negotiate based on user count, module footprint and implementation scope. Total cost of ownership is competitive with general mid-market manufacturing-specialist alternatives (canias, oxaion, abas, proAlpha) and substantially below SAP S/4HANA or Infor LN for comparable ETO functional scope. Implementation timelines run six to eighteen months for typical scope, longer for multi-site rollouts. The vendor's implementation methodology emphasises ETO-specific project-manufacturing templates that compress the design phase if the customer accepts close-to-standard ETO process. Customisation through supported extension paths is the recommended approach; the depth of ETO functional fit out of the box typically reduces the customisation burden compared to competing mid-market ERPs that handle ETO through bolt-ons.
Selection considerations
Choose ams.erp if you are a German Mid-Market engineer-to-order manufacturer (50 to 800 employees) in mechanical engineering, plant construction, capital equipment, mould and tool making or similar project-based manufacturing — and you value the depth of native ETO functionality. Choose it especially if you would otherwise have to customise a generalist ERP heavily to handle project-manufacturing workflows. Choose it for businesses where CAD integration with SolidWorks, Autodesk, NX or Creo is operationally important and ams.erp's specific connectors fit your engineering stack. Skip ams.erp for non-ETO manufacturing — high-volume discrete production, distribution-led businesses and process manufacturing should evaluate different products. Skip it for very large enterprise scenarios above 1,500 employees, where SAP or Infor LN scale better. Against oxaion and canias, both also competitive for ETO; ams.erp's specific advantage is the deeper out-of-the-box ETO functional fit.
Related Topics
Vendor homepage of ams.erp
Current view of the website https://www.ams-erp.com/
Direct comparisons with ams.erp
See ams.erp im strukturierten Direktvergleich gegen andere ERP-Systeme — mit feature scope, target audiences, strengths and weaknesses.
Reviews for ams.erp
No published reviews yet for ams.erp on erp-software.org yet.
Write your own review for ams.erp schreiben
Write Sie uns Ihre experience with ams.erp. We publish reviews after a brief editorial check in 1–3 business days. Fields marked with * are required.
Frequently Asked Questions
What does engineer-to-order actually mean in the ams.erp context?
Engineer-to-order (ETO) means each customer order requires engineering work specific to that order — building a custom machine, designing a unique plant configuration, manufacturing a specific tool or mould. Each order is essentially a small engineering project, with its own design, parts list, production routing, supplier sourcing and on-site commissioning. The data model and workflows in ams.erp are built around this pattern: project structures with multi-level WBS, integrated quotation-and-design phases, project cash-flow forecasting, and tight cross-module project visibility. Configure-to-order (CTO), where customer orders are configured from pre-engineered variants, is also supported but ETO is the architectural starting point.
How does ams.erp integrate with CAD systems?
Dedicated connectors for SolidWorks, Autodesk (AutoCAD, Inventor), Siemens NX, PTC Creo and other major CAD systems keep engineering bills of material aligned with the production bills of material in ams.erp. Engineering changes flow into the ERP through structured connector workflows rather than manual re-entry. This integration is one of the recurring selection drivers for ETO customers, particularly those whose engineering teams work in a specific CAD environment that ams.erp supports natively. Custom CAD integrations are possible through the vendor's services where the standard connectors do not cover the engineering stack.
Can ams.erp also handle high-volume production for businesses with mixed ETO and serial production?
Yes, but with care. The product is optimised for ETO and project-based manufacturing; serial production is supported but is not where the architectural strengths lie. Businesses with substantial high-volume serial production alongside ETO often evaluate canias, abas, proAlpha or SAP alongside ams.erp to weigh the trade-offs. For businesses where ETO is the dominant manufacturing mode and serial production is the secondary activity, ams.erp is usually a better fit than the reverse pattern.