DE EN
Try it free

POM in your industry

ERP & planning for automotive suppliers

Delivery performance, call-offs and evidence – for customers who audit their suppliers.

30 days, every module, no contract

The challenges

What it really hinges on here.

  1. 01

    Call-off quantities shift weekly and ripple through the plan

  2. 02

    On-time delivery is measured – and discussed at the annual review

  3. 03

    Complaints demand structured answers: 8D, actions, effectiveness

Suppliers under audit

Evidence before the customer asks.

An automotive supplier is assessed by its customers all the time: delivery dates, complaints, evidence. The customer keeps those figures in its own system. If you want to answer at the annual review with figures of your own, you need them from live operations – not from a spreadsheet someone put together the night before. That is where POM starts: with the data that is created anyway when orders are planned, produced, inspected and delivered.

POM Analytics shows delivery performance straight from live operations, with a trend line over calendar weeks. The delivery date analysis shows early, on time and late separately; you decide from when an order counts as early. The customer analysis sorts by delayed orders, and filters narrow it down to one customer, one article or one period. If a call-off shifts, drag the order in planning and see at once what it means for capacity and due dates.

After a drawing change, the first part needs proof. POM Quality releases a first article only with a stored proof document, and series production stays blocked until then; one proof covers every part of a split order. POM Inspection defines per article and work step which characteristics to check with which tolerance, and rates the measured value for dimensional characteristics. A quality block stops the order at completion, and with POM Shipping at dispatch too.

When a complaint comes in, POM Complaints turns it into a record with order reference, urgency and status – with 8D report, corrective actions and root cause analysis. Rework is planned like any other order, and the new delivery date is visible to planning and dispatch. If the cause lies in a supplier batch, POM Traceability shows forwards and backwards which orders it went into and which customers received it. The affected-orders list narrows down which deliveries are involved.

From order to key figure

How a series part runs through POM.

  1. 01

    Order and planning

    The order is created with article, quantity and due date. If the customer shifts quantities or dates, drag the order on the Gantt board and see the effect on capacity and due date immediately.

    POM CorePOM Planning

  2. 02

    Goods receipt with batch

    Material subject to batch tracking is recorded at goods receipt with supplier and manufacturer batch. From then on, POM records in which order, at which workstation and by whom the batch is processed.

    POM WarenwirtschaftPOM Traceability

  3. 03

    First article and release

    The first part is inspected and the proof is attached to the order. POM releases the first article only with a stored document – until then, series production stays blocked.

    POM Quality

  4. 04

    Series with inspection plan

    Start, stop and quantity are booked at the terminal. The versioned inspection plan asks for the characteristics per work step; records keep inspector, gauge and quantities for good, rework and scrap.

    POM BDEPOM Inspection

  5. 05

    Delivery and key figures

    Delivery note and invoice are created from the order. POM Analytics classifies the order as early, on time or late; a complaint becomes a record with an 8D report.

    POM WarenwirtschaftPOM AnalyticsPOM Complaints

What POM brings to your industry

Delivery performance per customer at a glance, first articles released only with proof, inspection plans with measured values, batches traceable forwards and backwards – and complaints with 8D structure.

Quick answers

Questions from practice.

Can POM receive call-offs via EDI?

Call-offs via EDI are not part of POM. If your customer or your existing system provides orders as a CSV or Excel file or via REST, POM Integration imports them with field mapping and a preview; a second run creates no duplicates and only applies changes. If a date shifts, drag the order in planning and see the effect on capacity and due date immediately.

Can series production start while the first article is not released?

No. Without a stored proof document POM Quality does not release a first article, and series production stays blocked until the release. As proof you store the document your customer requires, such as the inspection report; it is kept on the order on your server and included in backups. If an order is split, the proof covers every part of it.

Can I pass the 8D report on to my customer?

The 8D report with steps D1 to D8 is attached directly to the complaint in POM Complaints and can be printed. Cause and actions sit alongside; rework is planned like any other order, and the new delivery date is visible for planning and dispatch.

A customer rejects a delivery – which others are affected?

Starting from the order of the rejected delivery, the material record in POM Traceability shows which batches went into it. From each of these batches POM searches forwards to find the other orders and shipments it went into; the affected-orders list names them. The prerequisite is batch tracking on the article – with POM BDE, the server then does not accept a booking without a batch number.

How do I show a customer my own delivery performance?

POM Analytics calculates on-time delivery from the orders in the system and shows it with a trend line over calendar weeks, filtered to one customer if you wish. You define in the settings how many days of deviation still count as on time and from when an order counts as early. Drilldown takes you to the individual orders, and CSV or Excel export provides the figures for the supplier review.

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.