For: Facility operators tracking cardio fleets, and dealer service managers reporting performance under service agreements.
The decision: Which availability measure to track per unit, and what should send a unit for diagnosis, replacement review or a service-provider conversation.
60-second answer: Console uptime from connected cardio equipment tells you whether the console was powered and connected. It does not tell you whether a member could complete a normal session. Track usable availability separately: opening hours minus hours the unit was out of use, per unit. Use console data for fault patterns and running hours, check the manufacturer’s definition of every metric it reports, and set review triggers as your own operating choices.
A powered console is not an available machine
A treadmill can show a responsive console all day while its belt slips under load, its safety key is missing or it carries an out-of-order sign. By console uptime it is healthy; by any measure a member would recognize, it is out of service. The reverse also happens: a network outage can take every console offline while the machines, if their consoles support offline use, run perfectly well in manual mode.
So keep two measures and never let one stand in for the other.
- Usable availability: the share of opening hours a unit could complete a normal session with its safety features working. Calculate it as (opening hours − hours out of use) ÷ opening hours, per unit.
- Console or network connectivity: the share of time the console was powered, responsive and reporting. It explains data gaps and connected features; it does not prove the machine was usable.
Count “out of use” from the moment the unit is tagged out until a recorded return-to-service check, using the same times as the call log described in breakdown response. Measure against opening hours, not the 24-hour clock, or every number looks better than members experienced it.
Records to pull
- Opening hours for the period.
- Tag-out and return-to-service times for each unit, from the call log or floor checks.
- The console or facility-software export: fault events, running hours and any “uptime” figure, with the vendor’s written definition of each.
- Service visit reports for the same units.
- Staff floor-check notes on units signed out of use without a service call, which are hours a call log alone can miss.
What each metric can and cannot tell you
| Metric | Source | What it can show | What it cannot show | Decision it supports |
|---|---|---|---|---|
| Usable availability | Call log and floor checks | Hours a member could actually use the unit | Why it was unavailable, without the delay code | Service performance; replacement review |
| Console connectivity | Console or facility software | Data gaps; connected-feature outages | Mechanical or safety faults | Network and firmware follow-up |
| Fault events per unit | Console fault log, deduplicated | A unit producing far more faults than its neighbors | Faults the console does not detect | Diagnostic visit before another reset |
| Repeat faults | Fault log plus visit reports | The same fault returning after a repair | Whether the first repair was correct, without the report | Repair-or-replace comparison |
| Running hours | Console | Accumulated use against the manufacturer’s maintenance schedule | Condition; heavy-use hours wear differently | Scheduling the maintenance the manual specifies |
| Early session ends | Console session data | Units members leave quickly | The reason, which may be position, comfort or a fault | A staff test on the unit |
| Use spread across same-model units | Session data at peak | Units members avoid while they work | Whether avoidance is mechanical or positional | Floor check; future layout or mix |
When counting fault events, group entries logged within a short window so one fault producing a cascade of codes counts once. Check how the manufacturer defines a fault event and an uptime figure before comparing units or brands. Two systems may count very different things under the same label.
An illustrative reading
Take a single-site club open 100 hours a week, about 430 opening hours in a month. One treadmill’s console reports 99% uptime for the month. The call log shows the unit was tagged out for belt slip for 42 opening hours while a part was on order. Its usable availability was (430 − 42) ÷ 430, about 90%. The console figure was accurate about the console and silent about the machine. These numbers are illustrative, not a benchmark.
If a service agreement or vendor report promises “uptime,” ask in writing how it is defined, which hours it counts and whether units tagged out with a working console are included.
Set review triggers as operating choices
FEX does not publish green, amber and red bands for these metrics; no universal threshold applies across brands, duty levels and sites. Decide in advance what sends a unit for review, write it down, and apply it consistently. Variables to set your triggers from:
- how much the site depends on that unit type, and whether alternatives exist at peak;
- what the service agreement commits to, and how it defines availability;
- the unit’s own baseline compared with identical units on the same floor;
- the maintenance schedule in the manufacturer’s manual for that model;
- any safety-related fault, which means removal from use, not a review trigger.
Review monthly for fault patterns and availability; small floors produce noisy monthly numbers, so look for units that stay out of line across several months rather than reacting to one reading.
Using availability in service agreements
For dealers, reporting usable availability alongside console data is a stronger renewal argument than console uptime alone, because it matches what the customer experienced. For operators, it is the figure to bring to the service provider review. Pair it with the delay code so the conversation separates parts waits from technician capacity.
What to do this week
- Ask your console or facility-software vendor for written definitions of every metric it reports, especially “uptime.”
- Add tag-out and return-to-service times to the call log if they are missing.
- Calculate usable availability per cardio unit for last month and compare it with the console figure.
- Write your review triggers down and file them with the service agreement.
Continue with FEX
- Connected equipment data: assign access and retention
- Console firmware: control versions and support lifecycle
- Calculate documented downtime cost
FEX editorial guidance: the availability definition, metric table and illustrative reading are FEX analysis. They are not manufacturer specifications, contractual entitlements or industry benchmarks.
Editorial update, October 8, 2026: Removed green, amber and red bands for belt hours, fault frequency, console uptime, session abandonment, utilization spread, downtime and repeat faults, which were not supported by a source. Removed a statement applying fixed service-interval percentages across equipment types. Added a usable-availability measure distinct from console uptime and guidance on confirming vendor metric definitions. Qualified the statement that machines run normally in manual mode during a network outage, which depends on the console, and removed an unsupported claim about which out-of-use hours are most often missed.
