Work orders that close as reliability records
Plan, execute and close every job through eight states, so what you finish is data you can trust
One work order, one maintenance record
A work order in Magnus Reactor is the job and the record at once. It carries the tag and installed unit, the maintenance category and activity, scheduled and actual dates, active hours and downtime, the crew who did the work and the parts they used. One work order is one maintenance record, laid out the way ISO 14224 Table 8 expects, so nothing is re-keyed later for reliability analysis.
The lifecycle does the enforcing. A job moves from requested to closed through eight states, and the step from work done to completed checks that the times, hours and codes a reliability engineer needs are actually there. The front of the process asks for little so that the back of it can be strict.
Explore asset managementBenefits
Raise work without waiting for codes
Report a failure with the tag, what happened in plain words, how bad it is and when. Mechanism, cause and detection method are filled in later by whoever knows, never by the person holding the radio.
Move every job through the same eight states
Requested, approved, planned, scheduled, in progress, work done, completed, closed. Each transition stamps who moved it and when, so a job's history is a sequence of facts rather than a memory.
Close only jobs that are fully recorded
Completion checks actual start and finish, active hours and downtime, the activity and item for corrective work, and the failure event link. A work order that passes is a maintenance record you can compute from.
Keep the preventive program on schedule
Define PM tasks by calendar, operating hours or demands, fixed or floating, with grace days and route-based targets. Work orders are raised ahead of due dates and anything past due lands in the backlog.
Plan, gate and classify every job
Take a job from request to closure
A work order starts as a request and ends as a closed record. Review it into approved, with technical-authority approval when the job is safety critical and overdue. Identify activities, resources and parts to make it planned; assign dates and crew to make it scheduled. Stamping the actual start puts it in progress, the craft confirms work done, validated times and resources make it completed, and technical completion closes it. Cancel from any of the first four states. Every move lands in the status history with who, when and a note.
Follow the lifecycle step by stepComplete only what the record can support
The step from work done to completed is where the data is checked. Actual start and finish must be stamped. Active maintenance hours and downtime hours must be present, with the work-while-running check answered. Corrective work must name the maintenance activity and the subunit or maintainable item worked on. When downtime far exceeds active time, a delay reason is required: logistics, weather, scaffolding, spare parts, crew or permits. Corrective work orders and failure events must reference each other, enforced in the database. Warnings never block; only missing facts do.
- Actual start and finish stamped
- Active hours and downtime recorded
- Activity and item named on corrective work
- Delay reason when downtime far exceeds active time
- Corrective work order and failure event linked both ways
Schedule preventive work by calendar, hours or demands
Define a PM task once: its subcategory, the maintenance activity, an interval in calendar time, operating hours or demands, and whether the schedule is fixed or floats from the last completion. Add grace days, estimated hours, priority and whether the job requires a shutdown. One task can cover many tags, so a route through every fire-water valve is a single task with many targets, each carrying its own next-due date. Work orders are raised automatically inside a lead window, never duplicated, and anything past due appears in the backlog.
Report a failure now, code it later
Reporting a failure needs the tag, what happened in plain words, how bad, and when. Failure mode, mechanism, cause, detection method, consequence classes and the failed item are added afterwards by whoever knows, from lists filtered to the equipment class. The event runs reported, investigating, corrective planned, corrected and closed; it turns corrected when the linked corrective work order completes, and closing requires a different person from the one who reported it. When a PM finds a fault, one action raises the event and the corrective work order together.
Classify work so the KPIs stay honest
Every work order is corrective, preventive or modification. Preventive splits into condition-based work, testing and inspection or condition monitoring, and predetermined work: periodic test, scheduled replacement, scheduled service. Corrective is immediate or deferred. Modification is a deliberate third category: rebuilding a skid or upgrading a control loop is real work with real hours, but it is not maintenance, so it is excluded from every maintenance KPI. Priority, plant impact and spare-part location are recorded alongside, so the record explains the response as well as the work.
Account for hours, resources, delays and parts
Record labor by discipline, mechanical, electrical, instrument or other, with man-hours and headcount. Log vessels and rigs in days, ROV and divers in hours. Note each delay with its reason and duration. List the subunits and maintainable items worked on and the parts consumed against them, with unit cost. Estimated and actual hours and cost sit side by side, and rework is linked to the job it repeats. The result is a record that answers what the job cost, why it took as long as it did, and which item keeps consuming parts.
Explore InventoryFollow a job through the lifecycle
Eight states from request to closure. A job can be canceled from any of the first four; once work starts, it can only move forward, and each step forward has something to satisfy.
Requested
A job is raised against a tag: a failure reported from the field, a PM task falling due, or a modification request. Cancel here if it is a duplicate.
Tag and plain-words description
Approved
Review the request. Safety-critical work that is already overdue needs technical-authority approval before it goes any further.
Technical authority when safety critical and overdue
Planned
Identify the maintenance activity, the subunit or item, the labor disciplines, resources and parts the job needs, and estimate hours and cost.
Activities, resources and parts identified
Scheduled
Set scheduled start and finish within the latest allowable finish, and assign the crew. This is the last state from which a job can be canceled.
Dates and crew assigned
In progress
Stamping the actual start moves the job. From here the work order can only go forward.
Actual start stamped
Work done
The craft confirms the work is physically finished and the time is stamped. Hours, delays and parts can still be recorded.
Craft confirmation
Completed
Times, hours, downtime, activity, item, delay reason and the failure-event link are validated. A corrective job completing here moves its failure event to corrected.
All completion gates pass
Closed
Technical completion. The closure time is stamped and the work order becomes a maintenance record that reliability KPIs read from.
Closure time stamped
Part of one record
A work order is one row in the same record the rest of the product reads, so the job connects to the tag, the parts and the test that raised it without re-keying.
Asset Management
Resolve every job to a tag and unit
A work order cites the functional location and the installed unit at that tag on the day, joined through the installation history in Asset Management, so the job follows the tag while the serial keeps its own change-out record.
Inventory
Consume parts against the item position
Every part consumed on a job is recorded with its part master number, quantity, unit cost and the level-9 position it went into, feeding the where-used and worst-actor views in Inventory.
IoT & Metering
Raise corrective work from a failed test
When a test record in IoT & Metering fails, the failure event it opens already carries its detection method, and the corrective work order holds that event as its mandatory link.
Questions we are asked
No. Moving from work done to completed requires actual start and finish, active maintenance hours and downtime hours, and an answer to whether the work was done while the equipment was running. If downtime far exceeds active time, a delay reason is required too. The job stays at work done until those facts are entered.
No. The field entry is the tag, plain words, how bad and when; the codes come afterwards, from lists filtered to the equipment class. A mode outside the class matrix is recorded with a warning, not rejected.
One action on the PM work order reports the failure: a failure event is created with the detection method derived from the PM subcategory, and a linked corrective work order is raised at the same time. An organization setting decides whether minor faults fixed in place during the PM must raise a record or can be noted on the PM itself.
Only after its corrective work order completes. Completing the linked work order moves the event to corrected on its own; closing it is a separate step that verifies the coding and must be done by a second person, never the reporter. The rule is enforced per record, whatever role the reporter holds.
Because it is not maintenance. Rebuilding, upgrading or re-engineering equipment consumes hours and parts and deserves a work order, but counting it as corrective or preventive would distort failure rates, PM/CM ratios and man-hour KPIs. Modification work orders keep every field of the record and are excluded from every maintenance KPI.
Yes. Corrective work is classified immediate or deferred, with priority high, medium or low, and plant impact zero, partial or total. An immediate job can be raised, approved and started in minutes and still carries the same completion gates, so an emergency repair ends up as complete a record as a scheduled one.