A Maximo job plan is the template a planner reaches for when a work order needs to exist. It carries the tasks, the labour estimate, the materials, the tools, the safety content and, on a well run estate, the procedural detail a technician actually uses on the tools. Get the library right and the work order is mostly written before the planner opens it. Get it wrong and every PM cycle becomes a fresh argument about what the job actually is.
This piece covers the patterns that make Maximo job plans hold up over years of use in IBM Maximo Manage, including under MAS, and the discipline that keeps the library usable long after the implementation team has moved on.
What a Job Plan Is Actually Carrying
A job plan, in Maximo Manage, is a reusable template for a unit of work. It holds tasks, planned labour, planned materials and services, tools, and links to safety content. When the job plan is applied to a work order, those rows are copied onto the work order and become the basis of the plan for that specific job.
Two practical points get missed. The first is that the job plan is the parent for the planning data on the work order, but the work order is not chained back to it. Once applied, the work order can be edited, and changes to the job plan after the fact do not flow into work orders already in flight. That is by design, and it is the reason why a “small tweak” to a live job plan does not behave the way people expect.
The second is that a job plan with no tasks is still a job plan. It will still copy planned labour, materials and tools onto a work order. Many estates run a mix of single-task and multi-task plans, and confusion about which to use is a common source of bloat.
Structure That Survives Contact With the Field
The structure of the library matters more than the structure of any single plan. A library that started clean usually ends up bloated because nobody decided up front what would be one job plan and what would be many.
The pattern that holds up:
- One job plan per genuinely repeatable unit of work. If two PMs differ only in frequency, that is one plan referenced by two PM records, not two plans.
- Tasks are used when the technician needs to record progress, time or measurements at the task level. If every task is going to be ticked at once at the end of the job, the tasks are decoration. Either give them a reason to exist or fold them into the work plan as procedure.
- The job plan number is meaningful at a glance. A prefix that ties to asset class or trade, a short purpose token, and a sequence is enough. The bare auto-generated number reads as noise inside a year.
- Materials sit on the plan where they are genuinely planned. Consumables that the technician picks up from a van stock or storeroom by feel do not belong on every plan; they belong in the storeroom issue process.
The test for a library is whether a planner who has not seen a particular asset before can find the right plan in under a minute. If the search has to be guided by tribal knowledge, the library has drifted.
Revision Control Is Not Optional
IBM Maximo supports job plan revision control at the organisation level. With revision control on, an active job plan cannot be edited in place. Changes are made on a new revision, that revision is activated, and the old revision is retained for the audit trail. PMs and work orders pick up the active revision when the plan is applied next.
Estates that turn revision control off because it “slows people down” usually find out within a year why it exists. The job plan that the technician ran against last quarter is no longer the job plan in the system. The reliability engineer cannot tell, from the work order history, which version of the procedure was followed. Any compliance argument that depends on the job plan being a controlled document quietly collapses.
The right default for any regulated or safety-critical estate is revision control on, with a clear approval path for activating a new revision. Treat the job plan like a controlled document because, in a meaningful sense, it is one.
Safety Content Belongs on the Plan, Not in the Toolbox Talk
Maximo Manage links job plans to safety plans, which in turn carry hazards, precautions, tag-outs and lock-outs at the asset and work asset level. When this is configured properly, the safety content lands on the work order automatically whenever the plan is applied.
A few rules of thumb keep this honest:
- Hazards and precautions belong on the asset and the work plan, not on a separate document the supervisor remembers to attach.
- Lock-out and tag-out steps that depend on plant state are part of the procedure, not optional reading.
- If a permit is required, the relationship between the permit and the job plan or work order should be explicit, not a sticker on a clipboard.
The safety content the operator has agreed should accompany this work should travel with the work order every time, without depending on anyone remembering to attach it.
Job Plans and PMs: Sequences That Earn Their Keep
For preventive maintenance, the link between the PM record and the job plan is where most of the value of the library compounds. IBM has long documented job plan sequences on PMs for situations where the work varies by cycle: a short routine inspection each month, with a deeper overhaul every twelfth cycle, for example. Configured as a sequence on a single PM, this avoids three or four PMs against the same asset, with arithmetic in someone’s head about which one is due next.
The sequence approach also keeps the asset history clean. The PM record is one thing, the work orders generated from it are an honest stream, and the variation in scope is visible without needing to reconcile across records.
The same logic applies for route-based work, where one PM and one job plan can cover an inspection round across many locations, and for meter-based PMs, where the job plan describes the work and the meter drives the frequency. Keep the PM library small, let the job plans carry the scope.
Where the Library Comes From
A surprising number of job plan libraries are seeded once at the end of implementation and then never curated. After three or four years the library carries plans that are no longer used, plans that have been superseded, and plans that should have been merged. The more recent plans often contradict the older ones.
A modest discipline keeps this under control:
- An annual review by trade, looking at usage and ownership.
- A clear rule for retiring plans that have not been applied for a defined period.
- A standing owner for each plan, the same way a start centre template has a named owner.
- A path for the front line to propose changes, with a small queue and a real approver. The technician who notices the wrong torque value should not have to escalate to make it right.
Programmes that pair this with a clear maintenance strategy at the asset level tend to end up with a smaller, more useful library and a more honest PM schedule.
Closing Position
The job plan is the most visible artefact in the Maximo work management chain. It is the document the technician reads, the basis of the planner’s plan, and the structure the auditor follows when reading the history of a regulated asset. Treated as a controlled document with a small library, clear revisions, real safety content and PM sequences that match how the work actually varies, it earns its keep on every work order. Treated as a quick template, it quietly costs the operation a great deal more than it saves.