DE EN
Try it free

POM in your industry

ERP & planning for special vehicles

Project manufacturing with long build times and documentation the customer keeps for decades.

30 days, every module, no contract

The challenges

What it really hinges on here.

  1. 01

    One vehicle, hundreds of operations across months

  2. 02

    Changes during the build are normal, not the exception

  3. 03

    Hand-over needs documents, not memories

Build times measured in months

One vehicle, one file.

A special vehicle is a project lasting months: body, electrics, hydraulics, paint, acceptance – often hundreds of operations across several trades. In POM the vehicle is an order with a process chain, and the order overview shows how far along it is. On the Gantt board you plan the operations across weeks and employees; approved leave reduces capacity before it surprises assembly. With POM BDE, hours are booked against the order at the terminal, not estimated at month end.

Changes during the build are normal: an extra storage compartment, different lighting, a postponed acceptance date. With POM Collaboration every internal question hangs on the order as a message, and follow-up work becomes a task with an owner and a due date. For recurring cases such as a customer change request, you define a form that captures the details in a structured way. Six months later, the order still shows who decided what.

At hand-over the customer wants to see records, not recollections. In the material record, POM Traceability shows which batches went into a vehicle order – for material subject to batch tracking, from goods receipt onwards. POM Inspection records tests per work step, such as final acceptance, with inspector, gauge and result. The bookings show who worked on which operation; the skills matrix in POM Quality shows which qualification that person holds for it.

With a special vehicle, the original estimate is rarely the final bill. POM Costing calculates according to your scheme; if the scope changes, a new version is created instead of overwriting the released one. Post-calculation sets the planned times against the hours actually booked. On the next similar build you see where the time went – and calculate with reality instead of the estimate from back then.

From planning to hand-over

How a build runs through POM.

  1. 01

    Order with process chain

    The order gets a workflow with the stages of the build, such as frame, electrics, hydraulics and acceptance. The order overview shows this process chain with its progress.

    POM Core

  2. 02

    Planning over months

    On the Gantt board, the operations are spread across weeks and employees. Unplanned orders wait in the pool, overdue work is flagged, and approved leave reduces the capacity of those affected.

    POM PlanningPOM Absence

  3. 03

    Hours at the terminal

    Fitters scan order and personnel number and book against the operation with start and stop. The evaluation shows per order and employee how many hours the build has taken so far.

    POM BDE

  4. 04

    Changes on the order

    Questions and change requests stay on the order as messages, follow-up work as tasks with a due date. If the scope changes, the costing gets a new version.

    POM CollaborationPOM Costing

  5. 05

    Acceptance and hand-over

    Final acceptance follows an inspection plan for this work step; the record names inspector, gauge and result. At hand-over, the material record shows the installed batches, and post-calculation shows plan against actual.

    POM InspectionPOM TraceabilityPOM Costing

What POM brings to your industry

Communication, documents and decisions stay on the project, installed batches remain traceable – and the calculation follows reality instead of the original guess.

Quick answers

Questions from practice.

How do I record customer changes during the build?

With POM Collaboration, on the order itself. Internal questions, for example to work preparation or purchasing, are messages linked to the order; implementing the change becomes a task with an owner and a due date. Recurring details, such as those of a customer change request, are captured with a form of your own. Six months later it is still clear who decided what.

What can I prove from POM at hand-over?

Which batches are in the vehicle is shown by the material record in POM Traceability, provided the material is subject to batch tracking. Tests are recorded in POM Inspection with inspector, gauge and result, and cannot be changed. The bookings from POM BDE show who worked on which operation. POM does not keep serial numbers of individual parts; traceability works with batches.

How does costing stay current on orders that run for months?

By booking instead of estimating. With POM BDE the hours land on the operation, and post-calculation in POM Costing sets them against the planned times. If the customer changes the scope, you correct through a new version; the released one stays frozen. The evaluation per order, employee, workstation and shift shows where the time goes.

Can we start with a few modules and extend later?

Yes. The base price includes POM Core and POM Planning; modules such as POM Collaboration, POM BDE or POM Traceability are added when you need them. You then receive a new licence file, activate it on your server, and every workstation picks it up without reinstalling. A deselected module removes functions, never data – and during the 30-day trial every module is unlocked.

How do I keep track of several vehicles in build at once?

The order overview shows every vehicle with its process chain and progress, and overdue work is clearly flagged. The Today dashboard assembles what is due today in configurable tiles – with POM Collaboration, unread messages and due tasks too. On the Gantt board, bottlenecks become visible when several vehicles share the same employees.

Built in manufacturing. Built for manufacturing.

Every module, no contract. We set up the server together with you – and you talk to the people who write the software.