POM Planning
Production planning board
Planning in the core: assign orders and operations to employees on the planning board – with capacity, schedule risk and staff suggestions.
Included in the core (POM Core)
Online demo first, then a 30-day trial
- 01
The problem
A plan is current until the first change. Then rescheduling starts from scratch, and nobody sees whether the delivery date still holds.
- 02
How POM solves it
On the planning board you drag orders and operations onto employees. The server calculates the end and the following operations, and conflicts show up as notices. Capacity comes from working time, shift plan, absences and public holidays; if data is missing, POM says “capacity cannot be determined yet” instead of silently assuming 40 hours. Staff suggestions propose who fits – by qualification, performance, workload and experience.
- 03
The result
Bottlenecks show up before the delivery date makes them visible. POM never changes the customer’s date by itself.
Functions
What is inside.
-
Planning board with order, employee and equipment views
-
Capacity and workload per week – from working time, shift plan, absence and public holidays
-
Schedule risk with traffic lights and staged check tasks; warning “end after delivery date”, the schedule watch reports delays
-
Staff suggestions with five switches; qualification check when scheduling as off, notice or block
-
“Next orders” for the operator, without a Gantt chart
-
Print the order overview and export it to Excel
-
Part of POM Core – included in every licence
- Roadmap
From December 2026: machine per operation with set-up as a block of its own, backward scheduling from the delivery date with proposal and confirmation, a feasible delivery date already in the quote
- Roadmap
From December 2026: planning board by machine and a weekly plan per machine to print and post – today you assign the machine to the whole order
- Roadmap
No date yet: plan-versus-actual Gantt, bottleneck analysis and scenarios in planning
How it fits together
Every module feeds the next.
Receives
- POM Warenwirtschaft (ERP) The order confirmation creates a production order per line and hands “schedule” to work preparation; purchase dates show the material risk
- POM Shop Floor Data Times and good quantities move the order’s progress on; completion books the receipt
- POM Machines & Maintenance Maintenance and over-allocation as a notice in planning
- POM Warehouse Logistics Staging for production per shift from the same stock ledger
- POM Quality An open quality block stops the completion
- POM Time Recording Approved absence immediately affects capacity, planning board and staff suggestions; clocking in and out tells the automatic cover who is present
- POM HR On the effective date POM switches badge, cover and planning; after an approved leaving date nothing is planned beyond the last working day from December 2026
- POM Integration Writes orders, customers, articles and employees from other systems; feedback goes back
- POM AI Interface (MCP) External AI programs read, draft and propose, never with more rights than the person; a person approves
- POM Multi-Site Stock and ledgers per site; one order can run across two plants
Passes on
- POM Warenwirtschaft (ERP) Demand from production orders becomes a purchase proposal
- POM Warenwirtschaft (ERP) The inbox recognises an order e-mail and assigns it to customer and quote; after checking and approval it becomes the order confirmation from December 2026
- POM Shop Floor Data Production orders to log on and off at the terminal, “next orders” for the operator
- POM Time Recording One employee record: time recording, absence, skills, piecework pay, shop floor data and planning read the same person
- POM Piecework Pay The same employee record, no second staff list for piecework
- POM HR The same employee record, HR does not create a second personnel register from December 2026
- POM Analytics Orders, dates and lead times
Price
Concurrent users count, not accounts.
Included in the core (POM Core) 10 % saving with annual billing
| POM Core | with 1user | with 5users | with 10users | with 20users | with 50users | more than 100users |
|---|---|---|---|---|---|---|
| net / month | 15 € | 69 € | 129 € | 234 € | 504 € | On request |
| net / month, annual billing | 13.50 € | 62.10 € | 116.10 € | 210.60 € | 453.60 € |
Example amounts with the same number of users, net plus statutory VAT. Per module you book as many concurrent users as you need, at most as many as in the core. User accounts are unlimited.
More than 100 concurrent users: individual quotation, price on request. Request a quote
Quick answers
Questions about POM Planning
What can planning in the core do today?
On the planning board you drag orders and operations onto employees; the server calculates the end and following operations, and conflicts appear as notices. Capacity and workload per week come from working time, shift plan, absence and public holidays. Schedule risk is shown with traffic lights, and staff suggestions propose who fits.
Does POM plan machines too?
Today you assign a machine to the whole order. From December 2026 machine and order planning per operation arrives: set-up as a block of its own, backward scheduling from the delivery date with proposal and confirmation, a feasible delivery date already in the quote and a weekly plan per machine to print.
How does planning know qualifications and absences?
From data POM already keeps: the skills matrix with levels from 1 to 5 belongs to the employee master in the core. Absences and public holidays go into capacity; with POM Time Recording, approved leave shows on the planning board at once. If data is missing, POM says “capacity cannot be determined yet” instead of silently assuming 40 hours.
Do I have to book planning separately?
No. POM Planning is part of the core and included in every licence.
See POM for your business.
First we show you POM in an online demo with a sample company. After that you can test it for 30 days with a trial licence of your own.