Choosing a CMMS Work-Order Discipline Under Staffing Pressure
A property management firm operates six office buildings totaling 720,000 sq ft with a maintenance staff of nine technicians and one supervisor. The firm has used a CMMS for two years, but adoption is poor: roughly 40 percent of work is logged, most reactive calls are handled by phone or radio and never entered, and preventive maintenance completion runs about 55 percent. Technicians say the system takes too long and that the mobile app crashes in the parking garages. The supervisor closes work orders in batches at month-end, often without notes. Ownership wants key performance indicators - mean time to repair, PM compliance, and backlog - reported quarterly. A tenant satisfaction survey shows complaints about slow response on HVAC calls. The firm can fund either a CMMS mobile upgrade and training program or two additional technicians, not both.
1. What is the root-cause diagnosis of the poor CMMS adoption, and how should the manager distinguish a tool problem from a process and culture problem?
Read the worked answer
The symptoms point to a combination, and the manager should separate them before spending:
- Tool problem: the mobile app crashing in parking garages is a connectivity or application defect. That is real and fixable, and it directly explains why technicians avoid logging work in the field. Verify by testing the app in the affected locations and reviewing crash logs with the vendor.
- Process problem: work handled by phone or radio and never entered means there is no defined intake path. If the path of least resistance bypasses the CMMS, adoption will stay low regardless of the tool. The fix is a single intake rule: every request enters the system, even if entered by a dispatcher on the technician's behalf.
- Culture and accountability problem: the supervisor closing work orders in batches at month-end without notes signals that the system is treated as a reporting formality, not an operating record. Technicians follow the supervisor's behavior. Batch closing also destroys the data needed for mean time to repair and backlog.
Distinguishing test: if the app were fixed tomorrow, would logging rise? If the answer is uncertain because the intake path and supervisory habits are unchanged, the dominant cause is process and culture, not the tool. The 55 percent PM completion rate supports this: PM tasks are scheduled in the system, so low completion reflects execution and follow-up, not app crashes.
Diagnosis: all three causes are present, but the binding constraint is process discipline and supervisory behavior, with the app defect as an aggravating factor.
2. Given the either/or funding choice, what should the manager recommend, and what implementation steps and metrics would make the recommendation credible?
Read the worked answer
Recommendation: fund the CMMS mobile upgrade and training program, with conditions, and defer the two technicians. The reasoning:
- Adding two technicians to a system where 60 percent of work is invisible will not improve the metrics ownership wants. It will add capacity to an unmeasured process and may reduce urgency to fix the system.
- The data needed for mean time to repair, PM compliance, and backlog cannot be produced at 40 percent logging. Ownership's reporting requirement is unachievable without adoption, so adoption is the gating item.
Conditions and implementation steps:
- Fix the app defect first and verify in the garages; do not pay for training on a broken tool.
- Establish a single intake rule and assign dispatch responsibility so no request bypasses the system.
- Require same-day closing with notes; prohibit batch closing. Audit a sample weekly.
- Train by role, with short field sessions, and designate a technician champion per building.
- Set a 90-day adoption target (for example, 85 percent logging and 80 percent PM completion) and review weekly with the supervisor.
- Revisit the technician staffing question after 90 days using real backlog and response data.
Metrics to report quarterly: mean time to repair by priority, PM completion against schedule, open backlog by age, and first-response time for HVAC calls tied to the tenant survey. Define each metric and its data source in writing so the numbers are defensible.
The manager should also address the supervisor's batch-closing practice directly as a performance expectation, since the reporting requirement depends on it.