What project management software does in plant engineering, and where the status is still missing.

Anyone searching for project management software for plant engineering usually has a specific problem. Dates slip, costs run away, or nobody knows exactly where the project stands. The good news is that there are mature tools for the first two problems. The third is harder.

This article sets out what the common solutions do, what to look for when choosing one and where the project status is missing even with the best software.

What does project management software do in plant engineering?

In machine building and plant engineering with one-off and special-purpose manufacturing, you will mainly come across three kinds of tool. Each has its strength.

Scheduling, for example with MS Project. Tasks, dependencies, milestones and the critical path can be modelled cleanly. If delivery of the control cabinet slips, you can see what slips behind it, right through to the FAT and commissioning at the customer's site. A baseline lets you compare plan against actual.

Project modules in the ERP. They hold the project structure, budgets, purchase orders, hours and material requirements. For post-calculation and controlling they are usually the only reliable source, because purchasing and production book in the ERP anyway.

Dedicated project and multi-project tools. They plan resources across many projects, reveal bottlenecks in engineering or assembly and offer portfolio views for management. Some come with task boards for the team's day-to-day work.

What all three have in common is that they manage structured data. Dates, hours, amounts, responsibilities. They are good at that, and that is what you should use them for.

What should you look for when choosing one?

A few questions help before you compare offers.

• Where do costs and materials live today? If everything is booked in the ERP, a separate cost module in a second system rarely makes sense. Keeping data twice costs more than it brings.
• How detailed is your planning really? A schedule with many hundreds of tasks that nobody maintains is worse than a rough one that is right.
• Do you need multi-project resource planning? If engineering and commissioning are regularly the bottleneck across several projects, yes. If each project has its own fixed team, probably not.
• How do you handle customer changes? A change process with approval, cost impact and schedule impact often matters more in plant engineering than any Gantt view.
• Who maintains the system? This is the most important question. Any software is only as current as the person feeding it.

Why is the project status still missing despite project management software?

That last question leads to the heart of the matter. Project management software manages what someone enters. The real project status, however, is created elsewhere.

A typical case. The customer emails to say the safety guarding on the operator side needs an additional door. Engineering replies, and sales promises delivery without moving the date. At the next site meeting the team decides to change the bill of materials. That goes into OneNote.

None of this appears in the schedule. Nor in the ERP, until the first purchase order for the extra part goes out. The information exists, but only in the documents, minutes and mailboxes. It only reaches the software when someone copies it across.

Three gaps follow from that.

The maintenance gap. Copying takes time, and time is scarce in project business. So things are collected and entered later, often just before the next status meeting.

The delay. Days pass between the decision in the email and the entry in the system. In the meantime assembly is planning with the old status.

The translation. What lands in the software is a shortened version. A customer change with conditions becomes a line saying "add door". Why, under which commitment and who approved it stays in the email.

What this scattered gathering looks like in everyday work, and what it costs, is described in detail in the article on project status in Excel, OneNote and email.

Where is the real project status created in plant engineering?

If you want to understand the status of a running project, you rarely look at the Gantt chart first. You look at

• the specification and its revisions, because that is where the commitments are,
• the minutes from kick-off, site meetings, FAT and SAT, because that is where open points and acceptance conditions are,
• the emails with customer and suppliers, because that is where decisions and dates are made,
• the notes in OneNote, because that is where phone agreements are recorded.

These documents are usually already organised on SharePoint, the network drive or in OneNote. They do not need to move to become useful. How an AI can be connected to that storage without a migration is shown in the article on SharePoint and network drives as project storage.

How does an AI project assistant close the gap without replacing the software?

The obvious answer would be even more comprehensive project management software. That only moves the problem, because someone would have to feed that too. It makes more sense to use a tool that reads where the status is created.

That is the approach behind Project Memory in KoAssist, the AI project assistant for machine building and plant engineering. It is currently in pilot operation and runs alongside MS Project and the ERP, not in their place.

You connect the project folder or upload the specification. From it, KoAssist fills in a project profile with requirements by chapter, and every item shows its source. Anything missing appears as an open item, and "Who knows?" suggests whom you could ask.

Emails from your mailbox are filed in the project after you approve them. From emails and minutes, KoAssist suggests changes to open points, dates and decisions. Only what someone on the team accepts becomes valid. The overview shows status, next step, open points, decisions and risks, and the timeline shows milestones, deadlines and commitments.

What Project Memory deliberately does not do matters just as much. It does not plan resources, draw Gantt charts, do costing, record time or write anything into the ERP. That is what your project management software is for. Access rights come from your file storage, so anyone who may not open a folder in the source system will not see it in KoAssist either.

Does this fit your existing system landscape?

If your dates are in good hands in MS Project and your costs in the ERP, but you are missing the substance of the status, that is exactly the gap Project Memory was built for. The product page shows how it works with the file storage you already have. If you would like to see it on one of your own projects, you can book a demo.