ETO Project Management in PLM

ETO in practice: From CAD and documents to delivery – with a single source of truth

In many Norwegian industrial companies, the project itself is the product. They deliver individual machines, customised systems or small batches – often based on modular solutions, but almost always with a clear element of Engineer‑to‑Order. The customer influences the solution, either directly or indirectly, and each project takes on a life of its own.

This places very different demands on project management than series production does. Yet projects are often managed using the same tools: CAD files in PDM, documents in folders, progress in Excel – and status updates in meetings, email and Teams. It works. Until it doesn't.

When project management becomes a manual discipline

In ETO projects, you need to keep track of more than just the design at all times. It is about knowing which version currently applies, which decisions have been made along the way, and what actually remains to be done before delivery. When this information is scattered, project management effectively becomes manual work.

Typical symptoms are easy to recognise:

• project managers spend time “finding out the status”
• the engineering team becomes a bottleneck for clarifications
• errors are discovered late, often only during production or close to final delivery

This is rarely due to a lack of expertise. The challenge is structural. When product data, decisions and progress live in different systems – and partly in people's heads – there is no actual single source of truth.

Most SMEs today have good core tools in place: CAD, PDM and ERP. What is often missing is the layer in between. The place where the project should actually live – where the product, decisions and progress are connected.

Link progress to the deliverable, not the spreadsheet

In ETO, reversing the approach provides better control. Rather than managing the project alongside the product, the project should be managed through the product.

In practice, this means:

• progress is linked to actual milestones and deliverables
• tasks follow product changes, not email threads
• status is updated when work is performed – not after meetings

This is the core concept of modern, cloud-based PLM. In Autodesk Fusion Manage, for example, the project can be structured around the deliverable, with milestones and tasks that are either manual or directly linked to design and change processes. Product structure, documentation and history accompany the project in the same context.

The point is not the Gantt chart itself. The point is that project progress reflects the actual status of the product and decisions. For SMEs, this is rarely about doing “everything” at once. Often, the greatest impact comes from starting with one specific delivery workflow: one typical product, a few clear milestones, and clearly assigned responsibilities. Once the structure is established, it can be reused and built upon – without making the solution cumbersome. When the project effectively is the product, project management should live where the product lives. Not in separate files, folders and meetings, but in one coherent structure that actually reflects reality.

If you often use meetings to find out the status, it is a sign that status tracking is not systematic.

Feel free to get in touch for a no-obligation conversation about how one specific delivery in your business could be structured more effectively.