EE535 Chap.9 Maintenance Scheduling, CBM and Field Service
Maintenance Scheduling, CBM and Field Service
Scheduling works on several horizons
Long-range planning shows expected jobs, workload, materials, competence, access and budget over future years. Medium-range planning converts commitments into ready work packages and resolves procurement, interfaces and major access. Short-range scheduling sequences named orders against actual people, parts, permits and windows.
Each horizon answers a different question, and information should move between them so weekly actuals can change future capacity assumptions.
A due date does not make a job executable
Scheduled work competes with corrective demand, engineering changes and condition alerts. Planners need to check labour, skills, materials, tools, access, dependencies, opportunities and safety controls.
Compatible jobs can share an access opportunity, while incompatible work may compete for the same area or specialist. A feasible schedule preserves critical work and records the evidence and new decision date for anything deferred.
Time and usage remain separate triggers
A task may be due by calendar time, kilometres, cycles or another exposure measure.
Conversion requires an operating-rate assumption, and rates can change. Keep the authoritative counter and calendar trigger distinct, using forecast rates for planning rather than silently replacing measured usage.
Completion must reset the correct state against the correct asset, especially when equipment is moved or replaced.
Condition evidence creates a controlled route
Condition-based maintenance adds measurement, interpretation and a response state. Trend and threshold rules need data quality, asset identity and a link to the relevant failure mode.
An alert then needs validation, a work order, resources, dispatch and verification. Condition monitoring that ends at an alarm can create more messages without improving reliability.
The response route is part of the design.
Field service closes the information gap
Mobile tools can deliver current asset information, task steps, dynamic forms and safety controls while returning findings, actuals and restoration information directly. Dispatch can use status, skill and location, and integration can connect detected faults with orders and service estimates.
The benefit depends on controlled versions, offline and synchronisation rules, asset selection and validation. A device accelerates the information chain; it does not correct a weak one.
What this chapter covers
- 01
Long, medium and short scheduling horizons
- 02
Labour, materials, access and dependency constraints
- 03
Opportunity maintenance and competing work
- 04
Calendar, usage and combined triggers
- 05
Condition measurements, trends and action states
- 06
Field service, mobile forms and dispatch
- 07
Actuals, deferral and feedback to future plans
Worked example · free
Resolve a labour-capacity conflict
- 3Calculate adjusted hours for each job.
- 2Compare total demand with capacity.
- 4Explain the controlled response.
Key terms
- Scheduling Horizon
- The time range over which work, resources and constraints are planned at a chosen level of detail.
- Opportunity Maintenance
- Work combined with an available access or outage opportunity to reduce repeated disruption or setup.
- Usage Trigger
- A maintenance initiation point based on measured exposure such as kilometres or cycles.
- Condition Alert
- A controlled notification that condition evidence has reached a review or action state.
- Dispatch
- Assignment and release of executable work to suitable field resources.
- Deferral
- A controlled decision to move work, including rationale, risk, evidence and a new review or due point.
Maintenance Scheduling, CBM and Field Service FAQ
Why separate long-range planning from weekly scheduling?
The long view exposes future workload, budget, competence and material needs, while weekly control resolves actual orders, people, parts and access. One without the other creates either strategy without execution or a busy schedule that conceals future capacity failure. Actuals should update long-range assumptions.
Can kilometres be converted directly into calendar days?
Only with an explicit operating-rate assumption, and the measured usage counter should remain authoritative. Average rates help forecast when a trigger may arrive but can change with service. Keep both axes visible and avoid false precision, especially when equipment use varies or fitment changes.
What makes a condition alert actionable?
It needs trustworthy measurement, the correct asset identity, interpretation tied to a failure mode, a response state, a work route, competent resources, access and verification. Without those elements the alert is information, not maintenance control, and can add backlog without reducing consequence.
Exam move
Build a three-horizon schedule for one maintenance regime. Put budget, workload and competence in the long horizon; work-package preparation and access coordination in the medium horizon; and named orders, people, parts and permits in the short horizon. Add one calendar trigger, one usage trigger and one condition alert without converting them prematurely.
Create a capacity conflict and resolve it using consequence, condition and permitted windows. Record any deferral and feed actual labour and findings back into the long-range assumptions.
Working through Maintenance Scheduling, CBM and Field Service in EE535? Sia is AskSia’s AI Electrical Engineering tutor — ask any EE535 Maintenance Scheduling, CBM and Field Service question and get a clear, step-by-step explanation grounded in how EE535 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.