A hospital UPS drops out for four minutes and nobody notices — the transfer switch bridges the gap before an alarm even fires. A single rooftop chiller drifts down to 68% availability over six months and nobody notices either, until the July heat wave and three floors of tenant complaints land on the same afternoon. Both are availability failures. Only one gets treated like one, because most facility teams track every asset against the same uptime number instead of the target its class actually demands. OxMaint tracks availability against the right benchmark for each asset class, not one flat number for the whole building.
Asset Availability Software — OxMaint CMMS
Set The Right Uptime Target For Every Asset Class — Then Prove You Hit It
Availability tracked per asset class, not per building. Downtime causes tagged automatically. PM compliance tied to uptime outcome. Capital planning triggered by data, not by failure.
99.98%
Uptime target for data-center-grade critical power — roughly 1.6 hours of downtime tolerated across an entire year
65-68%
Typical OEE-based availability on HVAC and chiller assets running under reactive-only maintenance
80-85%
Achievable availability on the same chiller plant once structured PM and condition monitoring are in place
3-6x
Motor starting load multiple that undersized backup power sizing forgets — the top cause of a failed transfer test
Not Every Asset Deserves The Same Uptime Target
A five-nines target on a lobby escalator is wasted budget. A five-nines target treated as optional on an operating-room UPS is a life-safety failure waiting to happen. The first step in any real availability program is classifying every asset into the tier it actually belongs to, then holding it to that tier's number — not the one written on last year's maintenance contract by default.
01
Mission-Critical
Target: 99.98%+ · under 2 hrs downtime/year
UPS systems, medium-voltage switchgear, server-room CRAC units, N+1 or 2N power paths. Any unplanned event here stops operations or endangers life immediately.
02
Life-Safety
Target: Regulated · transfer under 10-30 seconds
Standby generators, fire pumps, emergency lighting, smoke control. Governed by NFPA 110/99 and local AHJ rather than internal SLA — failure here is a compliance event first.
03
Business-Critical
Target: 90-95% · structured PM dependent
Chillers, air handlers, elevators, boilers. Downtime does not stop the building but it does stop comfort, throughput, or revenue within hours.
04
Standard-Occupancy
Target: 85-90% · scheduled repair acceptable
Lighting circuits, low-priority pumps, secondary doors. A short outage is an inconvenience, not an incident — repair can wait for the next scheduled visit.
Reactive Tracking vs An OxMaint-Managed Availability Program
Most facilities already collect downtime data somewhere — a work order system, a BAS trend log, a technician's notebook. What is usually missing is the connective layer that turns raw downtime minutes into an availability number per asset class, tied to a target, with a root cause attached. That layer is the actual difference below.
| Dimension |
Reactive Tracking |
OxMaint-Managed Program |
| Availability calculation |
Estimated at year-end from memory and invoices |
Calculated per asset in real time from logged downtime events |
| Target by asset class |
One informal number for the whole site |
Separate target set and tracked per criticality tier |
| Downtime root cause |
Rarely categorized beyond "it broke" |
Every event tagged — mechanical, electrical, procedural, vendor delay |
| Repeat-failure visibility |
Same asset fails again before the pattern is seen |
Rolling trend flags recurring failure categories per asset |
| PM-to-outcome link |
PM completion tracked separately from actual uptime |
PM compliance and availability shown side by side per asset |
| Capital planning |
Replacement decided after a failure event |
Assets trending below target flagged for CapEx 1-2 years ahead |
Stop Guessing At Your Availability Number
Every asset gets its own target, its own downtime log, and its own trend line — so the number you report to leadership is the number the equipment actually delivered.
Six Signs Your Availability Program Is Still Reactive
Availability problems rarely announce themselves as a single dramatic outage. They show up first as small, easy-to-ignore signals. These are the six that consistently show up in facilities before a major unplanned-downtime event.
1
No Single Number Exists
Ask what the availability of the main chiller was last quarter and the answer takes days to assemble, or does not exist at all.
2
Downtime Logged As Text, Not Data
Outages are noted in a notebook or ticket description instead of a structured field that can be trended over time.
3
Same Fault, Different Month
A pump trips, gets reset, and trips again in eight weeks — with no record connecting the two events to the same root cause.
4
Backup Systems Untested Under Real Load
Generators and UPS units pass a no-load test but have never been proven against the actual starting load of connected motors.
5
PM Completion Tracked, Outcome Is Not
The team can prove every PM was completed, but nobody can show whether availability actually improved as a result.
6
Replacement Decided Mid-Failure
The first time replacement is seriously discussed is during an emergency call-out, not during a planning meeting.
What Facility Teams See After One Full Cycle
100%
Of critical assets carrying a defined, class-appropriate availability target
5 min
To pull an audit-ready availability report for any asset, building, or portfolio
30%+
Typical reduction in repeat failures once root cause tagging is in place
1-2 yrs
Earlier warning on replacement decisions versus deciding after a failure
Q
We used to report uptime as one number for the whole plant and everyone knew it was a guess. Now every chiller, every UPS module, and every air handler has its own target and its own trend line. When the board asks why we are replacing a unit, we show them the availability curve instead of explaining a breakdown after the fact.
Director of Plant Operations · Regional Healthcare Campus
Frequently Asked Questions
Asset Availability Software — OxMaint CMMS
Know Your Real Uptime Number Before Leadership Asks For It
Class-based availability targets, automatic downtime tagging, and CapEx signals that arrive years before the failure does.
