Insights · Utility and industry IT hiring · 6 minute read

How to Staff a Maintenance Management System Migration

Keep necessary maintenance work visible and correctly scheduled while changing the system that organizes it. Staff the migration around equipment knowledge, repeatable conversion and evidence the maintenance team can verify.

By Vitaver Staffing ·

Keep the next maintenance job attached to the right equipment

Imagine a utility replacing the computerized maintenance management system, or CMMS, used at several facilities. The first Monday after the move, a planner must see which equipment is due for service, a technician must find the correct instructions, and a supervisor must distinguish completed work from work still waiting for parts. Getting the asset count right is one checkpoint. Preserving those decisions is the mission.

Before opening a search, the maintenance manager should choose a small group of representative equipment and trace a complete job from scheduling through completion. Include a time-based inspection, a task triggered by equipment usage, a job waiting for a part and an asset that has moved between locations. Use those cases to define the people and evidence the assignment needs. The Department of Energy’s CMMS guide identifies work orders, equipment history, maintenance schedules and supporting documents among typical capabilities. DOE, Operations and Maintenance Best Practices Guide, chapter 4.

Give data decisions to people who understand the equipment

Assign a maintenance planner or reliability specialist to own the meaning of each record. A data engineer can build and repeat the conversion, but someone who knows the equipment must decide whether two similarly named pumps are duplicates, whether a retired component belongs in active schedules and which service history must follow a replacement. Put disputed mappings on a list with the source evidence, decision owner and date needed. Keep the original identifiers available so reviewers can trace the conversion.

Separate equipment identity from the location where it operates. IBM’s Maximo documentation describes asset records with identifiers, location and hierarchy, while location systems can preserve information about equipment moves and performance at particular sites. That distinction gives the team a useful test: can a planner find the current equipment at a station and still follow the history of the equipment that previously operated there? Confirm the model for the exact product and release in the assignment. IBM, Assets overview and Locations.

Build the team around scheduling, conversion and acceptance

The application specialist owns configuration and the relationship between job plans, work orders and scheduling. The data engineer owns extraction, mapping, repeatable loading and reconciliation. A maintenance representative tests whether the resulting work makes sense on the ground. Give an integration engineer responsibility for any inventory, purchasing or equipment-reading interface that can create or change maintenance work. A small engagement can combine technical roles when one person has the necessary skills and review capacity is available.

Make one person responsible for validating scheduling after the move. IBM describes time-based and meter-based maintenance, and its meter documentation distinguishes cumulative usage from measurements such as pressure or temperature. For a runtime-triggered task, check the unit, reading history, reset handling and next due point. For a time-triggered task, check the date and the rule used to calculate it. Treat any unexplained change in which job is due as an exception to resolve before acceptance. IBM, Meters.

In candidate assessment, give everyone applying for the same role the same fictional asset list and work-order sample. Ask the data candidate how they would identify unresolved duplicates and reconcile the load. Ask the application candidate how they would verify the next due work after a meter reset. Score the relevant decisions and evidence, including when the person seeks a maintenance owner’s judgment. State the actual site visits, approved access and maintenance windows in the first conversation.

Accept a usable maintenance queue and a repeatable handoff

Before cutover, the maintenance manager should approve a reconciliation of open, completed, deferred and cancelled work. Count records by meaningful categories and investigate differences. In a controlled test, have a planner generate the expected work, let a technician retrieve the instructions and record completion, and verify the resulting next due task. Test a part reservation and return status if those interfaces are in scope. Keep test work isolated from real dispatch and purchasing.

Agree who records work during any freeze and who reconciles it afterward. Name the person authorized to delay activation if a required job disappears or equipment identity remains ambiguous. Give each unresolved item an operating response, owner and review date. Have the receiving administrator repeat a small conversion or reconciliation without the contractor directing every step.

This applies the Vitaver Playbook’s Mission First principle to maintenance staffing. The engagement is ready to close when the maintenance team can explain its queue, verify the next jobs and maintain the records through the approved process. That evidence gives the buyer a sound basis for accepting the technical work.

← All Insights