At 07:00 on Monday the planner opens the weekly report and it shows 412 approved work orders against crew capacity of roughly 300 (both figures illustrative). The scheduling meeting then spends forty minutes deciding which 300 to release, and cannot, because 180 of the 412 are sitting at WMATL waiting on material and WMATL is a synonym of APPR. Nothing in the report is wrong. The estate’s Maximo work order status design put three operating states behind one internal value, and the report grouped on that value.
Work order statuses in IBM Maximo Manage are held in the WOSTATUS synonym domain. Internal values (WAPPR, APPR, INPRG, COMP, CLOSE, CAN, HISTEDIT) carry the business logic. Synonyms carry the operating language, and three of them ship with the product: WSCH for waiting to be scheduled, WMATL for waiting on material, WPCOND for waiting on plant conditions. All three are synonyms of APPR. The structure is long established and behaves the same way on Maximo 7.6.1 estates and on MAS Manage.
What the WOSTATUS domain actually controls
The internal value decides behaviour. IBM documents the allowable transitions for each one: from INPRG a work order can go to WMATL, COMP, WAPPR or CLOSE, and from COMP the only route is CLOSE. Synonyms inherit the transitions of the internal value they sit under. The Edit Rules under Work Order Options in the Organizations application also key off the internal value, so a field that is read-only after approval is read-only at WSCH, WMATL and WPCOND alike.
Three consequences follow, and they set the boundaries of every status design decision.
- Internal values cannot be added to a synonym domain. A new operating state is a new synonym of an existing internal value, not a new behaviour.
- Every status change writes a row to the WOSTATUS table with the user and the timestamp. That table is the evidence for how long work sits in each state.
- The Domains application carries a View/Modify Conditions action against each synonym value, which controls whether that value appears in the Change Status list for the record in hand.
Failure mode 1: one internal value carries three operating meanings
The report behind Monday’s meeting is usually a Start Center result set or a KPI filtered on approved work. Written against the internal value, it returns authorised work, costed work and work blocked on a part as one population, and the planner has no way to subtract the blocked records without opening them. Written against the synonym string instead, the same query silently drops WMATL and WPCOND, and the backlog looks smaller than it is.
The control. Name one synonym per genuine wait, and give each one a role that owns it. Waiting on a permit, waiting on a shutdown window, waiting on a third-party contractor and waiting on a part are four different people’s problems and four different synonyms of APPR. Operational reporting then groups on the synonym; finance and compliance reporting groups on the internal value, where APPR means authorised to incur cost. Both views are true at once, which is the point of the domain.
Failure mode 2: a wait state without an exit condition becomes the backlog
WMATL is the usual example. A work order enters it when a part is unavailable and leaves it when somebody notices the part has arrived. With no measure of dwell time, records accumulate there and drop out of the weekly review, because the report reads them as approved work and the storeroom receipt that unblocked them changed no status.
The control. Every synonym in the catalogue gets an entry trigger, an exit condition and a target dwell time. Dwell time is measurable directly from the WOSTATUS history table: the days between the row that set the status and the row that cleared it. Then put an escalation against the wait states with a condition on status and status date, notifying the named owner at the target and the supervisor at twice the target. Escalations that run cleanly at scale are the mechanism that makes a wait state self-clearing rather than self-perpetuating.
Failure mode 3: the release decision has no named holder
Where every planner and supervisor holds the Change Status option in Work Order Tracking, the transition from a wait state to INPRG happens wherever the pressure is highest that morning. Programmes in this position usually discover it during an audit, when the WOSTATUS history shows work released by six different user IDs with no consistent rule.
The control. Two configuration surfaces do this without a line of code. Conditional signature options in Security Groups grant or revoke a privilege based on a conditional expression, so releasing high-criticality work can be held to the supervisor group while routine work is released by the planner. Conditions attached to synonym values through View/Modify Conditions in the Domains application keep a status out of the list until its precondition is met, which puts the rule in the configuration rather than in a training note. Where the release is a genuine approval with a paper trail, the transition belongs in a workflow process rather than in the Change Status dialog, and the workflow assignment then names the decision holder on the record.
Failure mode 4: completion closes the record before the data arrives
Completing the last assignment on a work order also changes the work order status, to COMP or CLOSE depending on the WOSTATUSONASNTCOMP setting held in MAXVARS. Where that setting says CLOSE, the record becomes history the moment the last technician finishes their assignment. HISTEDIT is the only status change IBM allows from CLOSE, so any actual labour hours, materials or failure codes still outstanding have to be added through it. Reliability data rarely survives that, because a supervisor chasing this week’s work does not reopen last week’s history record.
The control. Set WOSTATUSONASNTCOMP to COMP, so completion stops field work and the record stays editable. Then close COMP work orders with an escalation carrying a change-status action after a defined number of days, and put the data the reliability team depends on into the escalation condition: actuals present, failure codes recorded on the work types where they are mandatory. Closure becomes a data-quality gate on a cadence rather than a side effect of a mobile device.
Failure mode 5: the status catalogue exists only in the configuration
The WOSTATUS domain record defines the values and the Change Status dialog presents them. Where intent lives nowhere else, the meaning of each synonym is carried by whoever has been in post longest, and a new planner learns it by getting it wrong in front of a supervisor.
The control. One page, seven columns: internal value, synonym, what it means operationally, the role that owns it, the entry trigger, the exit condition, the target dwell time. Reviewed quarterly with the planners and supervisors who use it, and versioned alongside the rest of the Maximo configuration baseline. A status catalogue that fits on one page is a status design somebody can hold in mind at 07:00 on Monday.
What stays hard
Four limits stay in place after the design is right. The transitions available from each internal value are fixed by product logic, so a chain of custom wait states cannot be forced into a strict order by configuration; conditions on domain values are the available lever and they evaluate one record at a time. Renaming a synonym in the Domains application does not update the work orders already carrying the old string, and Maximo says so at the point of saving, so a rename splits the history across two values and the reports have to map both. Dwell time analysis only reaches back to the date a synonym was introduced. And statuses set by mobile completion, assignment completion or an inbound integration message do not pass through the Change Status dialog at all, so any control that lives only in that dialog is partial by design.
The position
The number the planner argues with on Monday morning is set in the WOSTATUS domain long before the report runs. Estates that name one synonym per real wait, give each one an owner, an exit condition and a dwell target, hold the release privilege behind a conditional signature option, and close work orders on a data gate rather than on assignment completion, produce a backlog figure the planner can schedule against. Estates that run everything through APPR and its three shipped synonyms will keep arguing about which 300 to release, with a report that cannot settle it. The domain gives an operator two languages over one behaviour model: the internal value for anything financial or auditable, the synonym for anything a planner schedules against. The catalogue is what makes the second one legible.