Get real time alerts for every machine
Thresholds you set per asset, sent as they are crossed rather than found at the next inspection. The alert goes to whoever needs it, not to a report nobody opens.
By job role
Know a machine is going before it goes.
Most maintenance systems record what already broke. Output IQ watches the readings that change first, so the work moves out of the breakdown column and into the plan.
- No implementation fee
- Rolling monthly
- Thirty days to change your mind
- UK hosted
Asset healthLive
PRESS-04 vibration
30 day trend
6.3
Alert level6.0 mm/s↑ 5.0% 30 days ago5.2 mm/s↑ 21.2%
Unplanned work
Share of hours
22
Prev month31%↓ 29.0% Target15%↑ 46.7%
Assets watched
Continuously
24
With thresholds18↑ 33.3% Due for service3↑ 700%
The problem
Maintenance runs on dates, and machines do not.
A service interval is a guess dressed up as a schedule. Some machines get serviced long before they need it and some fail three weeks after a clean bill of health, and both cost money.
01
A breakdown arrives with no history
The machine stops, someone rings, and the first job is working out what changed. The readings that would have answered that were never recorded.
02
Servicing is scheduled on the calendar
Two identical machines running very different hours get the same service date. One is over maintained and the other is running on borrowed time.
03
The first alert is a person
Somebody hears it, smells it or notices the part is worse. By then the failure has usually started, and the window to plan the work has closed.
What you get
Catch it before it becomes a breakdown.
Watch critical readings live while you work
Vibration, temperature, current and run hours on screen while you are diagnosing. You can watch a machine react to what you just changed.
Let readings drive TPM, not a calendar
Condition based work rather than date based. The machines that need attention put their hands up, and the ones that are fine stop consuming planned hours.
Service on real usage, not on fixed dates
Run hours are counted by the machine. Service intervals fall due on what an asset has actually done, which is the only number that has anything to do with wear.
Root cause a breakdown from the readings
After a failure the thirty days before it are still there. Vibration climbing, temperature creeping and the load pattern changing tell you what to look at.
Where the numbers come from
Four sources, one figure.
None of this is typed in by anybody. The number you look at is assembled from the parts of the business that already produce it.
The ERP
Orders, stock, purchasing and finance. What was sold, what it was quoted at and what was bought to make it.
Mobile job tracking
Jobs booked on and off from a phone or a tablet on the floor. Labour lands against the job as it happens, not on a timesheet at the end of the week.
Connected sensors
Power, vibration, heat, pressure and run hours, straight off the machine. Nothing to key in and nothing to remember.
Failures that announce themselves
Continuous readings against thresholds you set, with the history kept. The work moves from the breakdown column into next week's plan.
Unplanned share of hours 22 Down from 31% last month
In practice
Measured, anonymised results will be published here as our first deployments report them. Nothing invented goes on this page in the meantime.
The rest of the business
The same feed, read a different way.
Questions
The ones maintenance managers ask.
What can you actually monitor?
Current draw, vibration, temperature, pressure, humidity, run hours and more, depending on the sensor. The range grows, and if something matters to you and is not listed we will tell you honestly whether we can do it.
Do the sensors need wiring in?
Most clip on. Some are fitted. Nothing needs the machine rewired or the control system opened up.
Does it replace our CMMS?
It can feed one or replace one depending on what you run. What it adds either way is the condition data that a work order system does not collect.
How far back does the history go?
Readings are retained so that a failure can be investigated against the weeks before it, and backups are kept with a thirty day history.
Can I set different limits per machine?
Yes. Every asset has its own thresholds, because a limit that suits a press is meaningless on a compressor.
Get started
Your business, one platform. Complete control. Real time intelligence.
Explore how Output IQ can empower your business, from automated ERP and MRP to live data analysis and sensors. Service before Software.