For: Operators running connected cardio consoles, and the dealers who sell, install or renew them.
The decision: Whether a console or equipment management system is costing or saving staff time, and what to require from the supplier before buying, renewing or changing it.
60-second answer: FEX found no published industry figure for console minutes per shift, so measure yours. Log every console task for a period you set: pairing and member questions, resets, fault handling, software updates, reporting and new-hire training, with the walk included. Match the log to support tickets and the system’s fault history. Then check how updates are delivered. Life Fitness says Facility Connect can push updates in bulk or on a schedule, that an update “can take up to 45 minutes to install” with the equipment unavailable, and that a USB drive inserted at each console is the fallback. Credit a saving only after it has been demonstrated and timed on your floor.
Where console time goes
A quote for fitness equipment technology lists hardware, licenses and installation. The staff time the system will consume, and the time it may save, are not on it. Both are measurable, task by task:
- Onboarding and pairing: account lookups, pairing a phone or wearable, explaining the interface, and the follow-up questions that recur.
- Resets and logouts: frozen screens, sessions left open, programs that will not clear. Log the walk separately from the fix, because in a large room the walk can be the larger part.
- Fault handling: noticing, verifying, logging, taping off, telling the desk and opening a ticket. This is the labor before a technician is involved.
- Software updates: scheduling, checking completion, and any visit to a console with a USB drive.
- Reporting: exports, cleanup and reconciliation between systems, set against the decisions the report changed.
- Training: the time for a new hire to work each interface independently, multiplied by your own hiring rate.
- Credits: tasks the system removed, such as inspection walks replaced by remote status, or manual logging replaced by automatic records.
Build the log from records you already have
Records to pull:
- A staff time log for a period you set, covering quiet and busy days: date, time, role, task line, console serial number, minutes including walk, outcome and ticket number.
- Supplier support tickets for the same period and the prior year, by category and unit.
- The management system’s fault and status history, and its update history.
- IT or network tickets that involve the consoles; network setup is covered in connected cardio security checks.
- Member complaints that name a console.
Floor staff should keep the log, because they know which tasks recur and they will record the walk an office-based observer forgets. Keep minutes as the primary record, and convert them to labor cost at your own wage rates only when you build the business case.
Updates and remote management: what manufacturers document
How updates reach the fleet is a line the operator and supplier can control. Life Fitness’s Facility Connect support article (updated August 30, 2024) says updates can be pushed immediately or scheduled for later, applied to several units at once, or set to install automatically through Remote Auto Update. It says updates “can take up to 45 minutes to install,” during which “the equipment will not be available for use,” recommends not updating during peak traffic hours, and says an update will never interrupt a workout in progress. Only users with Admin, Office Staff or Maintenance roles can update software. A separate Life Fitness article describes the manual fallback for times when updates cannot be pushed from Facility Connect: copy the build to a blank USB drive and insert it into the console’s front port, console by console.
Precor’s connected fitness page lists “real-time equipment monitoring, remote software updates” among its asset management features, available on all Precor Connected Fitness products. Treat both as descriptions of what the systems offer, and confirm which consoles on your fleet support them and which software versions they run.
Ask every supplier the same questions in writing: which consoles can be updated remotely, who schedules updates, how failed updates are reported, and how long the manufacturer will supply updates for the model. NIST’s IR 8259 Revision 1 (April 2026) recommends that IoT product manufacturers build in security functionality and give customers the cybersecurity information they need, which FEX treats as a reasonable basis for asking about support periods. Version control and rollback are covered in gym equipment firmware updates.
| Ledger line | Record that measures it | Leans toward keep or renew | Leans toward fix, renegotiate or replace |
|---|---|---|---|
| Resets and logouts | Time log; reset count by serial number | Few, spread across units | Repeated on the same units or software version |
| Onboarding and pairing | Time log; member questions | Falls after the first weeks | Stays flat; staff do every pairing |
| Fault handling | Time log; support tickets; fault history | Remote status identifies the unit and code | Every fault needs a walk to verify |
| Software updates | Update history; time log | Remote and scheduled outside peak hours | Manual visits to each console |
| Reporting | Time log; decisions the report changed | Used, and reconciled automatically | Hours of cleanup, no decision changed |
| Training | Time to independent use; hiring records | Short induction on few interfaces | Several interfaces to learn per hire |
| Credited savings | Supplier demonstration timed on your floor | Timed and repeatable | Described but not shown |
Net the ledger and set triggers
Total the minutes on cost lines and on timed credits for the same period. A system that nets negative is not automatically wrong; it may carry a programming or member benefit you can describe. The trade should be deliberate, and someone should decide which task loses those minutes. Feed the labor line into the cash-flow case described in gym equipment ROI.
Triggers you set: a level of weekly console minutes, or a ticket count on one model or software version, that prompts a supplier review; and a repeat of the log after any update, system change or layout change.
Red flags:
- Saving claims that arrive as slides rather than a timed demonstration.
- No update history, or updates applied console by console across a large fleet.
- Repeated resets on one software version with no ticket raised.
- Monthly reports nobody uses.
- Subscription renewals approved without the time log; fees and lapse terms are covered in equipment software fees.
What to do this week
- Give floor staff a log sheet with the task lines above and run it for a period you set.
- Pull support tickets, fault history and update history for the same period.
- Ask each supplier to state update method, scheduling, failure reporting and support period by console model, in writing.
- Ask for a live, timed demonstration of any claimed saving before crediting it.
- Net the ledger, set the review triggers and diarize a repeat after the next update.
Continue with FEX
- Measuring usable cardio hours
- Assigning connected equipment data responsibilities
- Calculating documented downtime costs
FEX editorial guidance: the task lines, ledger reading and triggers are FEX analysis. Manufacturer statements describe the named systems as published and may differ by console model and software version; manufacturer instructions control updates and service. This is not IT security advice; confirm network and security requirements with your IT provider and the manufacturer.
Source notes
- Life Fitness Support: Facility Connect – How To Update Your Equipment’s Software Version (updated August 30, 2024) — Bulk, scheduled and automatic updates; duration and availability; peak-hours advice; user roles.
- Life Fitness Support: How To Manually Update Equipment Software Using A USB Drive (updated August 15, 2024) — Manual USB fallback at the console.
- Precor: Connected Fitness Solutions (accessed October 8, 2026) — Real-time monitoring and remote software updates.
- NIST: IR 8259 Rev. 1, Foundational Cybersecurity Activities for IoT Product Manufacturers (April 20, 2026) — Manufacturer security functionality and customer information.
Editorial update, October 9, 2026: Removed the composite club ledger, its invented minute counts and the “minutes per shift” claims, and reframed the piece as a method using the operator’s own time logs and support tickets. Added Life Fitness and Precor documentation on remote updates and NIST’s April 2026 guidance for IoT manufacturers, and removed a shared stock photo.
