Facility Management and Service Planning · Lesson 4
Performance Baseline and Decision Dashboard
3 min read
Lesson objectives
Build a performance measure with a denominator and impact category suited to shift decisions.
Reading tools
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A dashboard says 90% of maintenance work finished on time. What exactly entered its numerator and denominator? Fast cosmetic tasks could dominate the count and hide delayed reports that disrupt occupants. Start a useful dashboard with a decision question, such as whether the late shift needs more high-impact response coverage. Collect consistently defined fields: opened time, category as assigned at opening, required deadline, response time, restoration time, affected asset and a reason for any exclusion. Only then calculate the percentage. Do not mistake several calls about one event for several failures if the decision concerns failure frequency. Keep the number of callers separately if it helps explain user impact.
Suppose three months record 20 high-impact reports with 15 timely responses, then 18 with 12, then 22 with 17. Monthly rates are 75%, about 66.7% and about 77.3%. When denominators differ, the combined rate is not the simple average of the three percentages. Add successes, 15+12+17=44, and eligible reports, 20+18+22=60: the combined rate is about 73.3%. The simple percentage average is about 73.0%, close by coincidence but incorrectly weighted. Do not decide from the number alone. Examine report mix and arrival times, and whether service hours, logging method or occupancy changed. One weak month could show inadequate shift cover, or it could reflect a new channel recording reports that previously went unseen.
Test data quality before ranking suppliers. Look for repeated work-order IDs, closure timestamps earlier than opening, categories changed after a breach and tickets closed without a test result. Return doubtful records to their source; deleting a bad-looking row simply to raise the rate is not cleaning. Show how many records were excluded and why, along with the period and system of record. If one month counts every order and another counts faults only, mark a definition break instead of drawing a false trend. Then frame a reversible decision: 'Trial late-hour coverage for four weeks; retain it if high-impact compliance improves without cost per report exceeding the demand organization's approved limit.' That limit is a documented management choice, not a universal value supplied by this lesson.
Lesson summary
Separate total workload from consequential faults and check comparability before interpreting a changed rate.