Skip to main content
A maintenance dispatch records work against a . Dispatches are created reactively for failures or generated from preventive schedules. Operators execute them in MES; configuration and reporting are under Resources in the ERP.

​
Dispatches

A maintenance dispatch records the problem, work center, assignee, time, and parts. It uses this lifecycle:
Every dispatch carries a priority (Low, Medium, High, Critical) and a source that says where it came from: Reactive (a breakdown, the default), Scheduled (generated from a preventive schedule), or Non-Conformance (raised from a ). It also carries a severity that says who handles it: Preventive, Operator Performed, Support Required, or OEM Required. Time is tracked as events against the dispatch, and parts as dispatch items.

​
What it’s against

A dispatch is attached to a work center and a required location — the machine being maintained. The Takes work center offline option also moves the work center’s downtime window in the schedule.

​
Preventive schedules

A maintenance schedule (Resources → Maintenance → Schedules) defines a work center, location, frequency (Daily, Weekly, Monthly, Quarterly, or Annual), priority, estimated duration, required parts, an optional procedure, and a Next Due Date. A background job runs daily at 06:00 UTC and creates an Open dispatch for each active schedule whose next due date has arrived. The dispatch has source Scheduled, severity Preventive, and a copy of the scheduled parts. Daily schedules can select weekdays and Skip Holidays. A schedule with Takes Work Center Offline needs an estimated duration; that window is taken out of the work center’s capacity in scheduling.

​
Blocking and OEE impact

Each dispatch declares its OEE impact: Down, Planned, Impact, or No Impact. This is an availability gate, not a metric.

​
Material and cost

Parts used in maintenance are issued from inventory, drawing stock down through the as a Maintenance Consumption movement.