Skip to main content
Maintenance planning projects upcoming workload and costs. The planner module allows detailed planning.

​
Tabs

​
Outcome

Planner Outcome tab

Utfall — projected activities per week, stacked by vehicle

Projected workload and costs over time.
1

Collect the work

Every vehicle gets its vehicle type’s tasks, and every currently mounted component gets its component type’s tasks — attached to the vehicle carrying it, so all work for a train appears together.
2

Find the first due point

For a distance interval, remaining kilometres are converted to days using the planning’s daily rate. For a day interval, the count runs from the last completed record; with no history the first cycle starts now. Anything already past due is clamped to today and flagged overdue.
3

Repeat forward

Occurrences step forward until the window ends. Seasonal tasks shift to the next season start. One-time tasks produce a single occurrence, and only if never completed.
Where a task has both a primary and a secondary interval, the earlier of the two sets the first occurrence while the shorter interval drives the repeat rhythm, since both clocks reset when the work is done.

​
Planner

Planner scheduler tab

Planerare — the scheduler timeline, one row per vehicle, with daily totals on top

Maintenance scheduler with drag and drop function. Dragging an occurrence changes its planned date, and that change is saved. Nothing else about an occurrence can be edited — the projected dates are computed values. The timeline totals manhours and cost per day from the estimates on each task. Those estimates are maintained here and on Maintenance Plan, and are never touched by the plan import — with one exception: if a task disappears from a delivered plan revision the task row is deleted and its estimates go with it.

​
Projected tolerance interval and planned date

An occurrence is within tolerance when its planned date falls between earliest and latest. The scheduler highlights that window as guidance, but scheduling outside it is allowed — the only hard rule is that the planned date must stay inside the planning’s own window.

​
Tables

Field reference

planner_maintenanceplanning and planner_plannedoccurrence.

​
Roles