Why machine-building projects demand different steering
A machine-building project starts with a price that was promised before design work began. From then on, execution decides how much of the margin survives.
Design release, ordering the long-lead items, start of assembly, FAT, delivery, commissioning, acceptance: each of these milestones hangs on the previous one, and delay at the end often triggers a contractual penalty. In parallel, five, ten, or twenty other orders run at the same time, competing for the same design engineers, fitters, and commissioning engineers. And in the middle of design, change requests arrive from the customer, implemented immediately on the technical side and claimed commercially far too rarely.
Task lists do not capture that. What has to be steered is the order: its schedule, its hours, its money.
Five steering problems that cost margin in mechanical engineering
1. Status lives in slides. Every week, project managers collect numbers, consolidate them in PowerPoint, and present a picture that is already outdated in the meeting. Preparation costs hours per project per week. Decisions run on yesterday’s data.
2. Escalations become visible when they are expensive. The delay on a long-lead item surfaces when assembly is at a standstill. The design problem reaches management when the FAT date starts to wobble. Days to weeks pass between occurrence and visibility, exactly the window in which countermeasures would still have been cheap.
3. Resource conflicts are settled in the hallway. Design is overbooked, the commissioning engineer is planned for two machines at once, and whoever asks loudest gets the people. A reliable utilization view across all orders and departments is missing.
4. The quote costing and the final costing never meet. The order was sold with a margin. Whether it still exists only becomes clear after project end, in the final costing. In between, hours and purchase orders accumulate without a running project P&L. By the time the number is finally on the table, countersteering is no longer possible.
5. Changes without a claim. The customer asks, engineering delivers, and the claim is never filed. Without systematic change management with commercial assessment, a machine builder gives away money it is contractually entitled to.
What project management software for mechanical engineering has to deliver
Solving these five problems takes more than boards and task lists. The requirements list for mechanical and plant engineering:
- Scheduling across all orders with the critical path, milestones through FAT and acceptance, and dependencies between the trades
- Resource planning in FTE across departments, with conflicts visible before they materialize
- A running project costing and project P&L per order: plan, actuals, forecast, and a variance walk that shows which position is eating the margin
- Change and claim management with schedule and financial impact in one record
- Suppliers and long-lead items in the same schedule picture as the project
- A fixed steering rhythm: meetings with an agenda, actions with owners and due dates, escalations with timestamps
- Answers from the project data instead of searching through folders: ask about project status in natural language and get answers with citations
- EU data residency and traceable permissions
How Evoltir covers these requirements
Evoltir is the steering platform for industrial projects. All orders, schedules, resources, costs, and changes live in one data foundation. A number has one source.
Schedule and critical path. All orders in one schedule view, with milestones, dependencies, and the critical path per project. Delay becomes visible where it originates, and the effect on FAT and acceptance is immediately readable.
Resources in FTE. Utilization per department and person across all projects. Conflicts appear in the plan and get resolved there, before two machines need the same commissioning engineer.
Costing and project P&L. Quote costing, a running P&L, and a forecast per order. The variance walk leads from the total deviation down to the position causing it. Margin is steered during the project, not established after project end.
Change requests with financial impact. Every change request is assessed technically and commercially and moves through a clear status from draft to implementation. The claim is created in the system, not from memory.
Suppliers in the schedule picture. Purchase orders and delivery dates of critical components are attached to the project plan. The long-lead item that can endanger the project sits next to the milestone it endangers.
Steering rhythm. Meetings with a fixed agenda, action tracking with owners and due dates, escalations with timestamps. Status is generated from the data that is maintained anyway. Slide-building disappears.
AI on your own project data. Questions like “Where does order X stand, and what threatens the FAT date?” are answered from your company’s real project data. Across all projects, the platform spots developments before they become escalations. The data stays in the EU.
Implementation without an IT project
Evoltir is operational in 3 days. The first steering cycle runs in week 2. After 90 days, the evidence is on the table, against measurement points defined up front instead of gut feeling. That is what the 90-day pilot with a fixed scope is for. The packages and their scope are shown on the packages page.
Generic tools, heavyweight PPM platforms, and the gap between them
Task tools are quick to roll out and stop where the order begins: no project P&L, no claims, no FTE planning across departments. Heavyweight PPM platforms cover a lot, but demand months-long implementation projects, configuration partners, and dedicated administrators. For a machine builder with twenty parallel orders, both are the wrong size. Evoltir occupies the gap: deep enough for P&L, claims, and resources, light enough to start in days.
Frequently asked questions
How is Evoltir packaged?
Evoltir is available in three packages. Scope and terms are aligned to your organization. The packages are shown on the packages page.
How long does implementation take?
3 days to operational readiness. The first steering cycle runs in week 2, the evidence after 90 days.
Where is our data stored?
In the EU. Database in Frankfurt, GDPR-oriented architecture. Details on the security page.
Does Evoltir replace our ERP?
No. The ERP remains the system of record for order management and accounting. Evoltir steers the projects: schedules, resources, project P&L, changes, meetings.
Who is Evoltir built for?
For machine and plant builders with several parallel customer projects, from special-purpose machinery to plant engineering with long durations.
Is there a pilot?
Yes. 90 days, a fixed scope, measurement points defined up front, and a substantiated decision at the end.
Related pages: Automotive suppliers · Aerospace · Energy · Industrial Mittelstand