Contents

1. What this window is for How it relates to the daily capacity plan 2. The concepts you need Scenario and official schedule Dispatching rule — which order goes first Forward and backward scheduling Horizon and frozen horizon Manual pinning (📌)Setup time — sequence-dependent Alternate machine (⇄)Virtual rows: Subcontract and No machine defined How an operation's duration is calculated The machine calendar — where capacity comes from Work centers and secondary resources 3. The Schedule tab — the Gantt chart Reading the Gantt chart The details panel 4. Pinning by drag and drop 5. The Scenarios tab — comparison and approval Action buttons The "Source changed" badge and the version conflict 6. New scenario — fields and assumptions Assumptions 7. The Bottleneck tab — the heat map "Add 1 shift" — before / after 8. Delivery promise (CTP) — which date can I give the customer How it is calculated Reading the result 9. Rescheduling — after a disruption The difference report Compare two scenarios 10. The Definitions tab Setup matrix Alternate machines Machine shifts Recipe op setup time 11. The plan line on a production order 12. On the phone (Garden + Steps)13. Permissions 14. Warnings, errors and what to do

Help › Production › Production Schedule (APS)

Production Schedule (APS) — A Guide from Scratch

The hardest planning question is "which machine will run this job, and exactly when will it finish?" The daily capacity plan tells you which job can be done on which day; Production Schedule (APS — advanced planning and scheduling) goes one step further: it places every operation on a machine at minute resolution and takes shifts, breaks, planned maintenance, downtime and the setup time lost at every changeover into account. You try different assumptions as scenarios, compare their results side by side and approve one as the official schedule; the delivery date you promise to a customer comes out of the same calculation.

1. What this window is for

The window has six tabs: Schedule (Gantt), Scenarios, Bottleneck, Delivery promise, Rescheduling and Definitions. It answers four questions:

Which job runs on which machine, and when? — a Gantt chart of machine rows and operation bars (section 3).
Which plan should we run? — scenarios, a side-by-side KPI comparison and the approval of the official schedule (sections 5 and 6).
Where is the bottleneck, and what if we add a shift? — a day × machine utilisation heat map and a one-click "before / after" trial (section 7).
Which date can we promise the customer? — the earliest delivery for a new order line, based on capacity and material (section 8).

How it relates to the daily capacity plan

The daily capacity plan (KUR_PLAN) in the Corporate Backbone works at day resolution; it is also what calculates material allocation and confirmed supply dates. Production Schedule does not replace or change that plan and has no MRP of its own: it reads each order's material-ready date from the active capacity plan (including the confirmed supply due date) and does not start the order's first operation before that date. If there is no active capacity plan, the Scenarios tab says "No capacity plan (KUR_PLAN): material constraints are unknown, only capacity is scheduled." — the schedule is then built on machine capacity alone and material delays are not taken into account.

Once an official schedule is approved, the due-date radar of Stuck Work Tracking takes the order's planned finish from here (the end of its last operation); without an official schedule it uses the capacity plan.

Where to open it. In the Production group of the dock, Production Schedule (APS) (next to Stuck Work). The Show in schedule link in a production order's details opens the window with that order highlighted (section 11). There is only one window: opening it again brings the open one to the front. The strip at the top shows the official schedule's name, who approved it and when, the number of late orders and the last finish.

2. The concepts you need

Scenario and official schedule

A scenario is a scheduling trial: a name, a dispatching rule, a direction, a horizon and optional assumptions (extra shift, closed machine, extra machine). When a scenario is calculated, each operation's machine, start and finish are saved together with the key indicators (KPIs). When you approve one of the calculated scenarios, it becomes the official schedule. There is only one official schedule at a time; when a new one is approved the previous one goes to the archive. Approval writes the planned machine, planned start and planned finish onto the order operations — that is the plan you see in the production order's details. Calculating a scenario does not touch the orders.

Scenario status	What it means
Draft	Saved but not yet calculated; it has no indicators.
Calculated	Its schedule and indicators are ready; it can be compared and approved.
Official schedule (★)	The plan in force. It cannot be recalculated, dragged or deleted; only its name and note can change.
Archive	A former official schedule. It can be viewed and copied; it is not recalculated or edited.

Dispatching rule — which order goes first

Orders are placed on the machines one at a time; the scenario's rule decides which order is placed first. The order placed first gets the best gaps.

Rule	Scheduled first
Earliest due date (EDD)	The order with the nearest due date. The default for a new scenario; the simplest way to protect deliveries.
Shortest processing time (SPT)	The order with the shortest total remaining processing time. It finishes many jobs quickly; long jobs may be left behind.
Critical ratio (CR)	The order with the smallest ratio of time left until the due date to remaining processing time: the one with the most work left relative to its due date comes first.
First in, first out (FIFO)	The order with the oldest order date.
Order priority	The order with the highest priority; on a tie, the one with the nearer due date (priority: Production › work order priority).

In every rule a tie is broken by order number (the lower number first), so two calculations on the same data give the same result. Sub-orders are scheduled before their parent order, and the parent's first operation does not start before the sub-orders finish.

Forward and backward scheduling

Forward (earliest): operations are placed in the earliest free time. For each operation the program looks at the gaps in the candidate machines' calendars (including the gap between two jobs) and chooses the place where the operation finishes earliest. This is the default direction.
Backward (just-in-time): operations are placed towards the due date, last to first, with the latest start; the job does not finish too early and wait as work in progress. If placing it that way would violate the order's earliest start (material-ready date, previous operation), that order is scheduled forward and a warning is written.

Horizon and frozen horizon

Horizon (1–365 days): the period over which the indicators — utilisation, bottleneck, heat map — are measured. Operations that spill beyond the horizon are still placed (the calendar is limited to two years); an order that finds no place at all counts as could not be planned.
Frozen horizon (days between 0 and the horizon): open operations in the official schedule whose start falls within this many days from now stay in place on the same machine with the same start in a recalculation (❄). It stops near-term jobs already released to the shop floor from moving at every calculation. If the machine no longer exists or is closed, the frozen operation is released and a warning is written.

Manual pinning (📌)

When you drag and drop a bar in the Gantt chart, that operation is pinned to the machine and start you chose (section 4). Pinned and frozen operations are placed first in the calculation; the other orders are scheduled around them according to the rule. When a scenario is copied, its pins are copied too.

Setup time — sequence-dependent

Moving a machine from one product family to another needs an adjustment, a die change or a tool change. The program finds the setup time in this order:

If the operation has already started, setup is 0; if the same product code follows itself on the same machine, it is also 0.
The setup matrix: the most specific row for the previous job's family → this job's family on that machine (section 10).
If the matrix has no match, the recipe operation's setup time (Definitions › Recipe op setup time).
If that is missing too, the recipe's setup time, for the order's first operation only.

Because setup depends on the sequence, placing a job between two others also changes the next job's setup; the program recalculates it and does not use that gap if the next job no longer fits. In the Gantt chart, setup is the hatched leading part of a bar.

Alternate machine (⇄)

When the machine in the routing is busy or closed, the operation can move to a defined alternate machine; its processing time is multiplied by the alternative's speed factor. Among the candidate machines (the main machine, its alternatives and the scenario's extra machine copies) the one where the operation finishes earliest is chosen; on a tie, the one with less setup wins, then the lower preference order, then the machine code. A bar running on an alternative carries the ⇄ mark.

Virtual rows: Subcontract and No machine defined

Subcontract operations are shown in the Subcontract (external) row, and operations whose routing machine is empty or undefined in the No machine defined (—) row. These rows sit at the bottom of the Gantt chart in a separate shade: they count as infinite capacity, run on the default calendar and are not counted in utilisation. The dates there are therefore not firm due dates: confirm the subcontract due date with the supplier separately, and assign a machine in the recipe to operations without one.

How an operation's duration is calculated

Run time = SURE_DK × ⌈remaining ÷ CAVITY⌉ × speed factor (on an alternate machine only) · bar = setup + run. If CAVITY is 0 or empty, SURE_DK × remaining. Remaining = order quantity − the sum of non-cancelled confirmations. A completed operation is not scheduled.

Example. Unit time 2 min, CAVITY 4, 1,000 pieces remaining → ⌈1,000 ÷ 4⌉ = 250 cycles × 2 min = 500 min of processing. On an alternate machine with a speed factor of 1.25, 625 min. With 30 min of setup the bar takes 655 working minutes. Durations are working minutes: breaks, off-shift time, planned maintenance and downtime are skipped, which is why a bar may look longer on the calendar than its duration.

The machine calendar — where capacity comes from

Working days are Monday–Friday. If "Saturdays too" / "Sundays too" is ticked on an extra shift in the scenario, those days become working days as well.
Shifts: if Human Resources shifts are chosen for the machine, those shifts' hours (a night shift runs into the next day), minus breaks. If none is chosen, the machine's daily working minutes (480 if empty), starting at the first active shift's start — or at 08:00 if there is none.
A day-based shift plan (the operations flow's machine × date plan), if present, overrides that day: 0 = the machine is closed that day, above zero = that many minutes.
Planned maintenance: every maintenance-period days from the last maintenance date, the first 240 working minutes of that day are removed (this can be changed in the scenario).
Downtime records are removed from capacity from their start for their duration. A machine whose status is not active has no capacity at all; its jobs go to an alternate machine.

Work centers and secondary resources

A routing step can be linked to a work center instead of a single machine: the schedule places the step on the center's machine that becomes free first and divides the run time by the center's efficiency; a center without machines is scheduled with virtual parallel machines (CENTER/1 …). If operator, mould, fixture, tool or area requirements are written on the step, the operation goes into the first interval in which the machine and all those resources are free at the same time; on the Schedule tab "Show resource lanes" draws operator and mould lanes, and the indicators show operator/mould utilisation and the bottleneck resource. Definitions and rules: Work Centers guide (together with the schedule).

3. The Schedule tab — the Gantt chart

The control strip at the top chooses what part of the schedule you see:

Control	What it does
Scenario	The empty choice is Official schedule. In the list the official schedule is marked with ★ and archived ones with "(Archive)". If there is no official schedule, the window opens the first calculated scenario.
Range	1 week, 2 weeks (default), 30 days — starting yesterday — or Entire schedule.
Machine	All machines or a single machine.
Hourly · Daily · Weekly	The zoom scale. The Gantt chart scrolls horizontally and vertically; the time axis stays at the top and the machine names stay on the left.
Order filter	Type Order no, stock code or description in the box: bars that do not match fade, and the order you are looking for stands out. When you highlight an order from the details panel, a "Remove highlight from order … ×" button appears next to the box.
Refresh	Reads the schedule from the server again. It does not recalculate — calculation is on the Scenarios tab.

Below the strip is a summary of the selected scenario: its name, status badge, rule, the Calculated: … time, the indicator boxes and any server warnings (a collapsible list titled "… warnings"; their meanings are in section 14).

Reading the Gantt chart

Each row is a machine; the start of the row shows the machine's name and its utilisation in the selected range. Virtual rows (Subcontract, No machine defined) sit at the bottom with an Infinite capacity note. The bars are operations; they show the order number and, if there is room, the operation name. The legend at the bottom of the window summarises the marks:

Appearance	Meaning
Hatched leading part of a bar	Setup (hatched) — the adjustment/die-change time.
Solid coloured part	Run (colour = order) — the colour comes from the order number; all operations of the same order share a colour.
Red border	Overdue orders — the order finishes after its due day.
📌 · ❄ · ⇄	Manually pinned · In frozen horizon · Alternate machine.
Grey shading	Off shift — the hours when the machine does not work. Drawn only for a range of up to 62 days.
Amber shading	Planned maintenance.
Red shading	Downtime — a recorded breakdown or stoppage.
Dashed red vertical line	Today — now.

Hovering the mouse over a bar opens a details balloon: order number, stock code, description, the Late badge, Operation, Machine, Setup time, Run time, Start, End, Due date, Quantity and Customer.

The details panel

Clicking a bar opens the details panel on the right (in a scenario where dragging is on, a click also selects the bar). The panel contains:

Order number, stock code, the Late badge and the description; Due date · finish, the Delay if any, and Material ready: … or Material-ready date unknown.
Highlight this order / Remove highlight — brings all the order's operations forward in the Gantt chart; Open production order — opens the order in the Production window.
A table of all the order's operations (Operation, Machine, Start; with the 📌 and ❄ marks). Clicking a row selects that operation.
The selected operation's box: Setup … + run …, the time span, the quantity; if pinned, 📌 Unpin; if frozen, "This operation is in the frozen horizon. Its position is kept on recalculation."

Orders that could not be placed are listed under the Gantt chart in a collapsible list titled Unplanned orders: n; clicking an order opens the production order. If the selected scenario has not been calculated it says "This scenario has not been calculated yet. Calculate it on the Scenarios tab.", and if there is no official schedule at all, "There is no official schedule yet. Calculate a scenario on the Scenarios tab and approve it as the official schedule."

4. Pinning by drag and drop

The way to correct the schedule with the planner's knowledge is to drag a bar. There are three conditions: the desktop window, write permission (section 13), and a selected scenario that is not the official schedule or archived. When they hold, the scenario summary says "Drag a bar to another machine or time to pin it." and the cursor turns into a hand over the bar.

Grab the bar and drag it to another machine row or time. A dashed ghost bar shows the target machine and the new start.
Drop it. The new start is the bar's left edge (setup included), rounded to the minute.
The server pins the operation to that machine and start and recalculates the scenario. A green box says "The operation was pinned to machine … starting at …. The scenario was recalculated." with the new late-order count and last finish; the Gantt chart refreshes.

You cannot drop onto a virtual row (Subcontract, No machine defined): the ghost turns red and says "Cannot drop on a virtual row".
If you dropped it at a non-working time, the first working moment is used; if it clashes with another pinned job on the same machine, the operation is moved after it; if you dropped it on a machine that is not in the routing, the duration is calculated at the main machine's speed. In each case a warning is written (section 14).
To remove a pin, click the bar and press 📌 Unpin in the details panel: "Unpinned. The scenario was recalculated."

The official schedule cannot be dragged. On the official schedule it says "The official schedule cannot be changed by dragging. Work on a copy." and a Copy and edit button sits next to it. The button creates a scenario named "… (copy)" (its pins are copied too) and opens it in the Gantt chart: drag the bars, then approve it on the Scenarios tab. There is no dragging on the phone.

5. The Scenarios tab — comparison and approval

The scenario list is also a comparison table: each scenario is a row, each indicator a column. The first column shows the scenario's name and, below it, its rule, direction, horizon and frozen horizon, its assumptions in blue (extra shift, closed machine, extra machine, maintenance) and the calculation/approval time. In the numeric columns green is the best value among the scenarios compared (archive excluded); a row with late orders is written in red.

Column	What it measures
Late orders	The number of orders that finish after their due date. An order finishing by 23:59 on its due day counts as on time. Fewer is better.
Total delay (days)	The sum of the late orders' delays, in calendar days (one decimal). Five orders one day late and one order five days late give the same total; read the two columns together.
Utilisation	On real machines, the ratio of (setup + processing) minutes within the horizon to available working minutes, averaged over machines. Virtual rows are not counted. It is neither good nor bad on its own and is not highlighted in green.
Setup time	The total setup time of all operations. It drops in a scenario that lines up jobs of the same family one after another. Less is better.
Bottleneck	The machine with the highest utilisation, and its percentage.
Unplanned orders	Orders that could not be placed at all (no routing, machine closed with no alternative, no room within two years). Fewer is better.
Last end	The finish of the latest operation — when all the open work will be done. Earlier is better.

The top strip holds + New scenario (section 6), the Show archived too (n) box if there are archived scenarios, and the capacity plan note: "Material-ready dates are read from the capacity plan (…)." or, in orange, the no-KUR_PLAN warning (section 1).

Action buttons

Button	When it shows · what it does
Schedule	When the scenario has indicators. Opens the scenario on the Schedule tab.
Calculate	On draft and calculated scenarios. Rebuilds the schedule from the current order, routing, machine, downtime and calendar data: "… calculated: … operations, … ms." Any warnings are listed below. Pins are kept.
Confirm	Only in the Calculated status; disabled if the source has changed. A confirmation asks: "Make this scenario the official schedule? The previous official schedule is archived and the planned dates of the order operations are rewritten." Result: "… is now the official schedule. Planned dates were written for … operations."
Copy	On every scenario (archived and official included). Asks for the copy's name (suggested "… (copy)"); the rule, assumptions and pins carry over.
Edit	Except on archived ones. Opens the form (section 6); on the official schedule only the name and note change. Saving does not recalculate.
Delete	Except on the official schedule. After the confirmation "Delete the scenario and its calculated schedule?": "Scenario deleted."

The "Source changed" badge and the version conflict

Every calculation keeps a signature of the data it used (orders, routings, machines, downtimes, calendar). If that data changes after the calculation, a Source changed badge appears next to the scenario (on hover: "Order, routing, machine or downtime records changed after this calculation. Recalculate.") and Confirm is disabled ("Source changed. Recalculate first."). If the change happened just as you approved, the server rejects the approval with SURUM_CAKISMASI: "Order, routing, machine or calendar data changed after the calculation. Recalculate the scenario." Press Recalculate in the red box, look at the result and then approve — a schedule built on old data cannot become official.

If the badge appears on the official schedule, a Source changed — reschedule button appears in the window's top strip; it takes you to the Rescheduling tab (section 9).

The official schedule is protected. It cannot be deleted ("The official schedule cannot be deleted. Approve another scenario first.") or recalculated ("The official schedule cannot be recalculated. Copy it and calculate the copy."). To update it: copy → calculate → compare → approve. The Rescheduling tab does the same in one step.

6. New scenario — fields and assumptions

Pressing + New scenario opens the form. A new scenario starts with EDD, forward, a 30-day horizon and a 2-day frozen horizon.

Field	Description
Scenario name	Required, at most 80 characters. If empty: "The scenario name cannot be empty." Pick a name that says what you are trying: "Saturday CNC-1", "Press-2 closed".
Dispatching rule	One of the five rules (section 2); a one-sentence explanation of the chosen rule is shown below.
Scheduling direction	Forward (earliest) or Backward (just-in-time) (section 2).
Horizon (days) · Frozen horizon (days)	Horizon 1–365; frozen horizon between 0 and the horizon. The server rejects out-of-range values.
Note	At most 1,000 characters; write why the scenario was set up.

Assumptions

Assumptions affect only this scenario's calculation; they do not touch the machine cards, the shift definitions or other scenarios. This is where "what if?" gets its answer.

Extra shift — a machine (or All machines) + minutes / day (0–1,440, default 480). The minutes are added after the last shift of every working day; if Saturdays too / Sundays too is ticked, those days become working days as well. If a machine has both its own row and an All machines row, the machine's own row applies. Add a row with + Add extra shift, remove it with ×.
Closed machine — the machine is not used at all in this scenario; its operations go to an alternate machine, and if there is none the order cannot be planned. Pick it from the + Add closed machine list.
Extra machine (copy with the same specs) — source machine × quantity (1–20). The copy works the same shifts and carries no planned maintenance or downtime; in the Gantt chart it is a separate row such as CODE#2 and is a candidate for the main machine's jobs. It tests "what if we bought one more machine?" without spending anything.
Minutes deducted on a planned maintenance day — the working minutes removed from capacity on maintenance days. Empty = 240 minutes.

Create scenario (Save when editing) saves the scenario but does not calculate it: "Scenario saved: …. Calculate it to see the result." On the official schedule's form the rule, direction, horizon and assumptions are locked: "Only the name and note of the official schedule can be changed. Copy the scenario to change rules and assumptions."

Example: will Saturday overtime save the due dates? On Scenarios, press Copy on the official schedule's row → name it "Saturday CNC-1" → Edit → Extra shift: CNC-1, 480 minutes, Saturdays too → Save → Calculate. Read the two rows side by side: if late orders and total delay went down and setup time did not change, the overtime works. If you like it, Confirm.

7. The Bottleneck tab — the heat map

Choose a scenario (empty = official schedule) and a range (1 week, 2 weeks, 30 days, 60 days — starting today). At the top it says "Bottleneck machine: …" with its percentage. Each row of the table is a machine, sorted from the highest utilisation down; the bottleneck row has a red background and a Bottleneck badge. Each day cell is that day's load ÷ capacity percentage; hovering shows "day: load … / capacity … (…%)".

Cell colour	Utilisation
Light green	Under 50%
Green	50–85%
Amber	85–100% — full, no slack left
Red	100–120% (overloaded)
Dark red	Over 120%
—	No capacity (holiday, closed machine). An empty cell = no load that day.

A day above 100% does not mean more work was squeezed onto the machine than it can take that day — the schedule does not exceed capacity; the percentage can rise because of jobs spilling across the day boundary and infinite-capacity cases. What to look at are the three columns at the end of the row:

Utilisation — the machine's rate for the whole period; 100% and above is shown in red.
Load — the total setup + processing time on the machine.
Queue — the average wait between the moment a job could start (previous operation finished, material ready) and the moment it actually starts on the machine. A long queue is the real sign of a bottleneck.

"Add 1 shift" — before / after

If you have write permission, each machine row ends with an Add 1 shift button; the size of the shift to try is set by Extra shift to try (240 / 480 / 720 min) and the Saturdays too box in the strip. The button creates a copy of the selected scenario named "‹scenario› + ‹machine› ‹minutes› min", adds the extra-shift assumption for that machine and calculates it. The result box shows:

An Indicator · Before · After · Difference table — an improvement in green, a deterioration in red; the utilisation difference in "points".
A difference report showing which orders moved and by how much (section 9).
"The result was written to a separate scenario: …. The official schedule did not change." and Show the new scenario in the schedule. If you like the result, approve the new scenario on the Scenarios tab.

If the selected scenario has not been calculated yet, the button returns the error "Calculate this scenario first."

8. Delivery promise (CTP) — which date can I give the customer

The delivery promise (capable-to-promise) answers "how soon can we deliver?" for a line that is not an order yet. Enter the Product (stock code), Quantity and Requested delivery date (default: 14 days from now) and press Calculate earliest delivery.

How it is calculated

Capacity: the routing of the product's active recipe (latest version) is placed like a new order into the free capacity of the official schedule. The operations of the official schedule stay where they are; the new line goes into the gaps and at the end. Open orders that are not in the official schedule are not taken into account (a warning is written).
If there is no official schedule, all open orders are rescheduled with the EDD rule and the new line is placed after them; the Calculation basis box says "No official schedule, so all open orders were rescheduled".
Material: the recipe's direct (first-level) components including the scrap allowance; requirement = line quantity × requested quantity ÷ recipe output quantity. Free stock = on hand in normal, active warehouses − the quantity of this component allocated in the active capacity plan.

Reading the result

Box	Meaning
Earliest delivery	The headline. Green: "The requested date (…) can be met."; red: "… cannot be met."; grey: "No firm promise can be given for …". A delivery finishing by the end of the requested day counts as met.
By capacity	The moment the machines can finish the job (assuming material is sufficient).
Material	Material sufficient · Material short · Material status unknown (the recipe has no components). If short, a Missing materials table appears: Stock code, Description, Required quantity, Free stock, Shortage.
Recipe · Calculation basis	The recipe used (or No active recipe) and whether the calculation rests on the official schedule's free capacity or on a rescheduling.
Operation placement	Each operation of the new line: machine, start, finish, setup and processing time.

If material is short, the earliest delivery stays empty. The capacity date is still shown, but the warning "… components are short in free stock. The earliest delivery date depends on material confirmation." appears: before giving a date, confirm the supply due date of the missing components with purchasing.

A delivery promise creates no record; the official schedule does not change and no write permission is needed. The promise becomes firm with the next schedule once the order is taken and a work order opened. If the product has no active recipe it says "… has no active recipe, so no delivery promise can be calculated.", and if the recipe has no routing, "The … recipe has no operation routing, so no capacity date can be calculated."

9. Rescheduling — after a disruption

A machine broke down and a downtime record was opened, a machine was set to passive, or an urgent order came in: the official schedule no longer shows reality. Choose the Source scenario (empty = official schedule) and press Reschedule (write permission required). The server calculates a copy of the source named "Reschedule ‹time›" with the current data; the rule, assumptions and pins stay as they were. The result is a new scenario: the official schedule does not change until you approve it.

The result box holds the Show in schedule and Approve in Scenarios buttons, the indicator boxes and a Reasons for changes list. The program looks for three reasons:

"Machine … was set to inactive. Its jobs moved to another machine or further down the queue."
"Machine … has a … downtime record starting …: ‹reason›"
"… new orders entered the schedule: #…, #…"

If there is none, it says "No new downtime, inactive machine or new order was found. The difference comes from current data (confirmations, duration changes)."

The difference report

It starts with a one-sentence summary: "… orders slipped: average … days, at most … days." (or "No order's end date changed."), and, in red if any order misses its due date, "… orders miss their due date." Below it, the table of moved orders (Order, Stock code, Old end, New end, Difference) is sorted from the largest shift down: plus and red means later, minus and green means brought forward; clicking an order number opens the production order. The collapsible Operations with a changed machine: … list shows the old and new machine.

Compare two scenarios

In the lower box of the same tab you can compare any two calculated scenarios: choose the Scenario and the Reference (empty = official schedule) and press Compare. The result is the same difference report; it answers "compared with the official schedule, which orders move in this scenario?". Comparing needs no write permission.

10. The Definitions tab

There are four sub-sections. Changes to the definitions are saved immediately but do not change the result of existing scenarios by themselves: "Setup time saved. Recalculate the scenario to see its effect." A user without write permission can only view the definitions.

Setup matrix

Each row: Machine (All machines = every machine), Previous product family, Next product family (Any family = every family) and Setup (min) (0–1,440). Saving the same triple again updates the row; Edit loads the row back into the form. A product family = the stock card's sub-groups (main group definitions excluded) + the card type (raw material, semi-finished, finished…); a product can belong to more than one family. If the family list is empty it says "No product family found: families come from the stock card subgroups and item type."

The most specific row wins: a machine-specific row beats All machines, a concrete previous family beats Any family, a concrete next family beats Any family (in that order of weight). At equal specificity the larger time is chosen. Example:

Matrix rows	Changeover → time used
`CNC-1 · boru → profil · 45` `CNC-1 · * → * · 20` `* · * → profil · 30`	On CNC-1, boru → profil: 45 · on CNC-1, levha → profil: 20 (the machine-specific row first) · on LAZER-2, levha → profil: 30 · on LAZER-2, profil → boru: no match → the recipe operation's setup time.

An All machines · Any family → Any family row matches every changeover. If you add one, the setup times on the recipe operations are never used. If you want a general default, fill in the recipe operation's setup time; use the matrix for changeovers that truly depend on the family.

Alternate machines

Each row links an alternative to a main machine: Primary machine, Alternate machine, Speed factor (multiplies the processing time: 1 same speed, 1.25 is 25 percent slower, 0.8 faster), Preference order (1–99, the lower is tried first), Recipe no (0 = all recipes) and Operation no (0 = all operations). Narrowing the scope is for cases where the alternative can do only a certain step of a certain product. Add, and when editing Save / Cancel.

Machine shifts

The table shows each machine's Status (Active / Inactive / Under maintenance / Broken down — anything not active is shown in red and has no capacity), its Daily minutes and its Shifts. Shifts come from the Human Resources shift definitions; choose them by clicking the buttons (code + hours) and press the Save that appears on the row. Breaks are removed from capacity. If none is chosen it says Default (daily minutes): the machine's daily minutes are used from the first shift's start (08:00 if there is none). If there are no shift definitions at all it says "No shift definitions. Add them under Human Resources › Shifts." (see Human Resources).

Recipe op setup time

Choose the Product (stock code) and press Load operations: the product's active recipes and each one's operations (Operation, Machine, Run time (min), Setup (min)) are listed. Change the setup box and press Save on the row. This is the fixed time used when the setup matrix has no match. The Recipe setup time in the heading is the older recipe-wide field and is used only for the first operation, and only when that is empty.

11. The plan line on a production order

When an official schedule is approved, each operation's plan is written onto the order. Open a work order's details in the Production window: in the Operations (routing) list a blue label appears next to each operation — Plan: machine · DD.MM HH:MM – DD.MM HH:MM. Hovering over the label shows "Official schedule: …". The Show in schedule link in the list heading opens Production Schedule on the Schedule tab with this order highlighted.

The plan changes only on approval; calculating or dragging a scenario does not touch the orders.
If there is no official schedule, the operation was not planned, or the Production Schedule module is off for you, the label does not appear at all — this is not an error.
The planned start date on the Program tab and in the work order list are separate fields; APS approval does not change them (see Production › the Program tab).

12. On the phone (Garden + Steps)

On a screen smaller than 7 inches the window opens in a three-step layout: Summary · Schedule · Delivery promise.

Summary — one card per non-archived scenario: name (official ★), status, rule, horizon, calculation time and two-column indicator boxes; Show schedule. If there is no capacity plan, the warning sits at the top.
Schedule — a scenario picker and a List / Gantt view, from yesterday to 14 days ahead. List: operation cards per machine (Order, Time, Duration; late ones in red, with 📌 ❄ marks), a machine filter and utilisation. Gantt: read-only — "Read-only. Tap a bar for details, drag to scroll."; the scale can be chosen.
Delivery promise — four steps: 1 Product (search by stock code or description and pick from the list) → 2 Quantity → 3 Requested date (shortcuts "In 1 week", "In 2 weeks", "In 1 month") → 4 Result (the same cards as on the desktop). Buttons: Continue, Back, Calculate earliest delivery, New query, Recalculate.

There is no writing on the phone. Creating, calculating, approving and dragging scenarios and the definitions are desktop work; if there are no scenarios the phone says "No scenarios yet. Scenarios are created and calculated in the desktop window." The delivery promise works fully on the phone too — to give a date while you are with the customer. Choosing the interface: Mobile guide.

13. Permissions

Task	Required
Viewing: Schedule, Scenarios, Bottleneck, Definitions; Delivery promise; comparing two scenarios	System administrator or the production module permission. Otherwise: "The production schedule requires production module permission."
Writing: add/edit/copy/delete a scenario, Calculate, Confirm, drag and drop and remove a pin, Add 1 shift, Reschedule, save definitions	In addition, the write gate must be open on the server and the user must not be read-only. Otherwise the top right of the window says "Read-only: you are not allowed to change the schedule." and the write buttons are hidden.

14. Warnings, errors and what to do

Warnings do not stop the calculation; the schedule is built, but they tell you that an estimate or a release happened somewhere. Errors stop the action. The "…" in the sentences is replaced by the real order, operation and machine.

Message	What to do
"No official schedule. Calculate and approve a scenario first."	Scenarios › + New scenario → Calculate → Confirm.
"No active capacity plan (KUR_PLAN): material constraints are unknown, only capacity was scheduled."	Run and activate the daily capacity plan in the Corporate Backbone (Corporate Backbone); then recalculate the scenario.
"The material-ready date of … orders is not confirmed in the capacity plan (…). These orders were scheduled by capacity only."	These orders' dates are optimistic. Have the supply due dates of the missing components confirmed.
"Order, routing, machine or calendar data changed after the calculation. Recalculate the scenario."	Recalculate in the red box → check the result → Confirm (section 5).
"Only a calculated scenario can be approved." · "Calculate this scenario first."	Calculate the scenario first.
"The official schedule cannot be deleted. Approve another scenario first." · "The official schedule cannot be recalculated. Copy it and calculate the copy." · "The official schedule cannot be changed. Copy it and change the copy."	Copy or Copy and edit; work on the copy and approve it.
"Order … op …: machine … is closed/inactive and has no alternate, so the order could not be planned."	Make the machine active, define an alternate machine under Definitions, or remove it from the scenario's Closed machine list.
"Order … (…): no operation routing, so it could not be scheduled." · "Order … op …: no slot was found within the two-year calendar horizon."	Enter an operation routing on the recipe; for the second, check the machine's shifts and daily minutes (its capacity may be zero).
"… operations have no machine defined. They are shown in the infinite-capacity "—" row and are not firm dates." · "… subcontracted operations are shown in a separate row. Confirm subcontract due dates with the supplier separately."	Assign a machine to the recipe operation; confirm the subcontract due date with the subcontractor (section 2).
"Order …: backward scheduling from the due date would violate the earliest start, so it was forward scheduled."	Information: this order's due date is tight. Check the indicators for the delay risk.
"Manually pinned / Frozen operation (order …, op …) was rescheduled because machine … is unavailable." · "… was moved to … because it clashed with another pinned job on the same machine." · "… was placed in non-working time. The first working time, …, was used."	The program moved the pin to the nearest valid place. If the result is fine, do nothing; otherwise drag the bar again or remove the pin.
"Order … op … was manually pinned to machine …, which is not in its routing. The duration was calculated at the primary machine's speed."	If that machine really can do the job, define it under Definitions › Alternate machines with a speed factor.
"Order … op …: a pinned/frozen operation starts before the previous operation ends (sequence violation)."	Remove the pin or drag the bar to after the previous operation's finish.
"… components are short in free stock. The earliest delivery date depends on material confirmation." · "… open orders are not in the official schedule and were not considered in the delivery promise."	For the first, confirm the supply due date with purchasing (section 8). For the second, the official schedule is out of date: bring the new orders in with the Rescheduling tab and approve, then repeat the delivery promise.
"The horizon must be between 1 and 365 days." · "The frozen horizon must be between 0 and the horizon."	Bring the value in the form within the limits.
"A read-only user cannot write schedule records." · "The write gate is closed (HNR_WRITE)"	Permissions are with the system administrator (section 13).
"The APS schedule tables (APS_*) have not been set up for this company yet. They are created when the Java server opens the company — restart the Java service."	The system administrator must restart the Java service.

Related guides: Production · Stuck Work Tracking · Corporate Backbone · Human Resources · Mobile.