Runtime and Cycle Analytics From Current Signals
Turn current sensor readings into runtime proof, cycle counts, exception alerts, and maintenance triggers.
Runtime totals
After-hours use
Site comparison
Asset trend
Know when assets actually run
Runtime analytics help teams move from assumption to evidence. F2 Core can show when equipment ran, how long it ran, and whether the pattern looks normal.
Runtime totals
Hourly, daily, weekly, and monthly totals.
After-hours use
Highlight runtime outside operating windows.
Site comparison
Compare similar assets across sites.
Asset trend
Trend by asset over weeks and months.
Cycles matter
Some assets fail because of cycles, starts, and usage patterns. EO3 data supports cycle-based maintenance planning where appropriate.
Cycle count
Cycles by asset over time.
Short cycling
Detect short-cycle patterns that indicate trouble.
Unusual starts
Spot unusual start patterns relative to schedule.
PM trigger
Cycle thresholds trigger PM when crossed.
From data to action
Analytics do not stop at charts. F2 Core routes exceptions into tickets, vendor workflows, and reports.
Runtime / cycle exceptions
Anomalous patterns
After-hours activity
Alert
Ticket creation
Vendor route
Service completion
Cost history
Monthly report inclusion
Energy savings note
Energy Management features help identify runtime patterns, exceptions, and opportunities for action. Actual savings depend on site conditions, equipment, usage, tariffs, and implementation.
Ready to turn runtime data into action?
Walk through EO3 runtime analytics with real exceptions and routed work.