Trigger preventive maintenance schedules based on equipment run hours
This solution shifts manufacturers from reactive repairs to usage-based maintenance by automatically triggering work orders based on actual machine run time. It gives MSPs a highly repeatable, easy-to-deploy service that directly prevents catastrophic equipment failures and costly production halts for their clients.
The problem today
$50K
lost per major unplanned machine breakdown
18%
of maintenance budgets wasted on reactive repairs and guesswork
Dave Kowalski is the maintenance supervisor at a 35-person precision machining shop in Rockford, Illinois, responsible for keeping 30-plus CNC machines and compressors running across two shifts. His biggest frustration is walking into work on a Monday after a weekend breakdown — staring at a $30,000 emergency repair bill for a machine his calendar said wasn't due for service for another six weeks.
01The Problem
A machine running double shifts gets the same service interval as one that sat idle — and the bearings pay for it.
A single unexpected breakdown wipes out the production run, triggers emergency labor rates, and forces a parts scramble.
Manual run-hour logs collapse the moment the one person who maintains them is on vacation or pulled to the floor.
Over-maintained idle machines burn labor and parts budget while under-maintained high-run assets approach failure undetected.
No single supervisor can accurately track real utilization across a full floor — so they estimate, and eventually a compressor proves them wrong.
One unplanned breakdown during peak production erases an entire month's maintenance budget, making cost planning nearly impossible.
02The Solution
Solution Brief
Fictional portrayal · illustrative
- Dave runs 30-plus CNCs and compressors across two shifts
- PM schedule built in Excel five years ago — date-based, not hour-based
- High-utilization machines accumulate untracked wear between fixed calendar dates
- Idle machines serviced on schedule; busy ones silently approach failure
- $10K–$50K breakdown cost lands without warning during peak production
- 48-hour emergency can erase an entire month's maintenance budget
- Gap between calendar date and actual run hours is where breakdowns originate
- Non-invasive sensors track actual operating hours per asset, per shift
- At 500 hours, work order fires automatically into CMMS with asset ID, task, and parts list
- Dave's clipboard disappears — floor coverage no longer depends on one person's log
- One prevented breakdown funds the full system deployment on the math alone
- Sensors, gateway, and CMMS integration package into recurring managed services revenue replicable across every Rockford-area manufacturer
“I had a compressor go down last February because I was two weeks late catching that it had blown past its service hours. Cost us three days of production. Now the work order shows up in the system before I even think to check. I didn't realize how much mental energy I was burning just trying to keep track of all of it.”
— Dave Kowalski is the maintenance supervisor at a 35-person precision machining shop in Rockford, Illinois, responsible for keeping 30-plus CNC machines and compressors running across two shifts
03What the AI Actually Does
Run-Hour Accumulator
Non-invasive CT sensors on each machine silently track actual operating hours in real time, feeding live utilization data through an IoT gateway — no manual logging, no guessing, no clipboard required.
Threshold-Based Work Order Trigger
When any asset crosses its predefined run-hour limit, the system automatically creates a fully populated work order in the CMMS — right asset, right task, right parts list — without anyone having to remember to check.
PM Schedule Optimizer
Instead of treating every machine on the same calendar cycle, the system maintains a live maintenance queue based on actual utilization — so heavily-run equipment gets serviced on time and idle equipment isn't wasting labor hours on unnecessary PMs.
04Technology Stack
Fiix CMMS (Professional Plan)
$75/user/month. Typical deployment: 1 admin + 3 technicians = $300/month. MSP resells at 15-20% markup or bills separately for managed CMMS administration.
Cloud-based Computerized Maintenance Management System that serves as the central hub for all maintenance operations. Professional plan includes meter…
Mosquitto MQTT Broker
Free. No licensing cost. Runs on gateway or edge server.
Lightweight MQTT message broker that receives sensor data from IoT gateways and makes it available to Node-RED for processing. Handles pub/sub messagi…
Node-RED
Free. No licensing cost. Runs on gateway or edge server.
Flow-based visual programming tool that serves as the logic engine for the system. Accumulates run hours per asset based on sensor current readings, c…
InfluxDB OSS
Free for self-hosted OSS edition. Runs on edge server.
Time-series database optimized for IoT sensor data. Stores raw current readings, calculated run-hour totals, and historical trends per asset. Enables …
Grafana OSS
Free for self-hosted OSS edition. Runs on edge server.
Visualization dashboard that displays real-time and historical run-hour data per asset, sensor health status, and maintenance KPIs. Provides the plant…
Zapier (Starter Plan)
$29.99/month for 750 tasks/month. Typically sufficient for 20-machine deployments.
Connects Fiix CMMS to the client's existing business systems for notifications and workflow automation. Example Zaps: work order created → Slack notif…
05Alternative Approaches
UpKeep CMMS + UpKeep Edge Sensors (All-in-One Vendor)
UpKeep Essential at $20/user/month per seat; sensor hardware bundled at higher margin
Instead of the Fiix + NCD + Node-RED stack, use UpKeep's integrated solution. UpKeep offers its own branded wireless IoT sensors (UpKeep Edge) that connect directly to the UpKeep CMMS platform without needing a separate MQTT broker, Node-RED, or custom integration logic. Sensors communicate via cellular or Wi-Fi gateways to UpKeep's cloud, and the platform handles run-hour calculation and work order triggering natively.
Strengths
- Dramatically simpler deployment — no middleware, no custom Node-RED flows, no MQTT broker
- Single vendor for hardware + software support
- Faster time-to-value (days instead of weeks)
Tradeoffs
- Higher recurring cost (UpKeep Essential at $20/user/month is cheaper per seat, but sensor hardware is bundled and likely higher margin for UpKeep)
- Less flexibility — locked into UpKeep's sensor ecosystem and can't easily add third-party sensors
- Limited customization of logic (e.g., hysteresis, multi-threshold PMs)
- The MSP has less value-add since there's less to configure and manage — which means less recurring revenue
Best for: Client wants fastest possible deployment, has limited technical appetite, and prefers a single-vendor support relationship. Not ideal for MSPs looking to build sticky managed services revenue.
PLC-Direct Integration via OPC UA (No New Sensors)
Kepware KEPServerEX license $1,500–$5,000+; $0 per machine for sensor hardware
If the client's equipment already has PLCs (Siemens S7, Allen-Bradley ControlLogix/CompactLogix, Mitsubishi, Fanuc), extract run-hour data directly from the PLC's internal counters via OPC UA. Use Kepware KEPServerEX or an open-source OPC UA client to read PLC tags, bridge to MQTT, and feed into the same Node-RED → Fiix pipeline. No CT sensors needed.
Strengths
- No additional sensor hardware costs ($0 per machine)
- More accurate — PLCs track actual cycle time, spindle-on time, etc., not just electrical current
- Can extract additional data (cycle counts, fault codes, program numbers) for richer PM triggers
Tradeoffs
- Requires PLC programming expertise (Allen-Bradley RSLogix, Siemens TIA Portal) to expose the right tags — a specialized skill the MSP may not have
- Kepware license is $1,500–$5,000+
- Only works for machines WITH PLCs — older manual machines, compressors, and conveyors typically don't have PLCs
- Integration is more brittle — PLC firmware updates can break tag mappings
Best for: Client has modern CNC machines or injection molders with accessible PLCs and the MSP has automation engineering capability. Can be combined with CT sensors for equipment without PLCs.
MaintainX + Manual Meter Entry (Lowest Cost)
MaintainX Essentials at $16/user/month; no hardware costs
Deploy MaintainX CMMS (Essentials at $16/user/month) with meter-based PM triggers, but have operators manually enter run-hour readings from existing analog hour meters or machine displays rather than deploying automated sensors. Operators record readings at the start and end of each shift via the MaintainX mobile app.
Strengths
- Extremely low cost — no sensor hardware, no gateways, no edge server, no custom integration
- Can be implemented in 1-2 weeks
- Good starting point to build the PM habit before investing in automation
Tradeoffs
- Relies on human discipline — operators forget to log readings, enter incorrect values, or skip the process entirely
- Data is only as frequent as manual entry (typically 1-2x per shift vs. continuous)
- No real-time monitoring or sensor health alerts
- The MSP has minimal recurring revenue since there's no infrastructure to manage
Best for: Client has a very tight budget (<$5,000), wants to pilot a PM program before committing to hardware, or has equipment where CT sensors are impractical (pneumatic-only machines, manual presses).
Samsara Full-Stack IoT Platform
$30–$50/device/month; approximately $600–$1,000/month for 20 machines, plus CMMS costs
Use Samsara's industrial IoT platform, which provides gateways, sensors, cloud platform, and dashboarding in a single integrated solution. Samsara gateways connect to equipment via CT sensors, vibration sensors, or direct PLC connections, and the Samsara cloud handles data collection, visualization, and integrates with CMMS platforms via API.
Strengths
- Enterprise-grade platform with excellent dashboarding, mobile app, and alerting out of the box
- Samsara handles all the middleware (no Node-RED, no MQTT broker setup)
- Strong API for CMMS integration
- Good choice for clients who also have fleet vehicles (Samsara's core business)
Tradeoffs
- Significantly higher recurring cost — typically $30–$50/device/month, which for 20 machines would be $600–$1,000/month just for the IoT platform, on top of CMMS costs
- Less MSP control over the technology stack
- Vendor lock-in to Samsara's ecosystem
- Overkill for simple run-hour tracking
Best for: Client is a larger manufacturer (100+ assets), has fleet vehicles they also want to monitor, values a polished enterprise platform, and has the budget. Also good when the MSP wants to minimize custom integration work.
Vibration-Based Condition Monitoring (Predictive Enhancement)
$349–$499 per vibration sensor for the 5-10 most critical assets
Extend beyond run-hour-based PM to include vibration analysis on critical rotating equipment (motors, pumps, spindles, fans). Deploy NCD or ifm vibration sensors on the 5-10 most critical assets. Use vibration trending in Grafana to detect bearing wear, imbalance, and misalignment BEFORE failure, enabling true condition-based maintenance that supplements the hour-based schedule.
Strengths
- Catches failures that time-based PM cannot (a bearing can fail at 200 hours if misaligned, or last 5,000 hours if properly installed)
- Significantly reduces catastrophic failures
- Impressive to the client — provides tangible early-warning capability
- Higher MSP revenue from additional sensors ($349–$499 each) and a more sophisticated monitoring service
Tradeoffs
- Vibration analysis requires more expertise to interpret — baseline must be established per machine, and alert thresholds need tuning over 2-3 months
- Higher sensor cost
- More complex Node-RED flows
- Not a replacement for run-hour-based PM but an addition
Best for: After the basic run-hour system is stable and the client sees value, propose this as a Phase 2 enhancement for their highest-value equipment. Positions the MSP as a strategic partner moving the client up the maintenance maturity curve.
Ready to build this?