Orders and dates
Products
Section titled “Products”A product is a process with its properties already filled in: “12 m frame” is the “Frame” process with its length, its number of modules and its material. It is reused in every order that includes it.
Orders and lines
Section titled “Orders and lines”| Entity | Fields |
|---|---|
| Order | Customer, reference, priority or weight |
| Order line | Product, quantity, due date |
Each unit in a line becomes a job to plan, with its tasks. Each unit keeps its identity across replans, so a new plan can be compared with the previous one unit by unit.
Due dates
Section titled “Due dates”The due date is a soft rule: the plan tries to meet it and, if it cannot, penalises the deviation.
| Penalty | What it measures |
|---|---|
| Lateness | Each time unit the order finishes after its date |
| Earliness | Each time unit it finishes before (producing early also has a cost: stock, space) |
| Order duration | Time between the first and the last task (the more compact, the less work in progress) |
Each penalty has a weight, and each order or customer can have its own: one customer can penalise lateness more than another. See the On-time delivery objective.
Withdrawing an order
Section titled “Withdrawing an order”An order can be withdrawn from a plan: its capacity is freed and the rest is recomputed without touching what is already running.