Predictive maintenance software and connected monitoring systems
Building maintenance intelligence from measured equipment behaviour: condition monitoring first, accumulated failure history second, and prediction once the data supports it.
Predictive maintenance uses equipment measurements and failure history to estimate when an asset may need attention. It differs from simply scheduling a service or detecting a condition change: a useful prediction needs evidence that supports the forecast.
| Approach | Trigger | Evidence needed |
|---|---|---|
| Preventive maintenance | A calendar or usage interval. | Service schedules and operating history; a failure forecast is not required. |
| Condition monitoring | A measured change from a threshold or baseline. | A trustworthy measurement chain and context for interpreting deviations. |
| Predictive maintenance | An estimated failure likelihood or remaining life within a defined horizon. | Relevant labelled history and evaluation showing the estimate is useful for that asset and decision. |
What is usually being asked for
The request is normally some version of “tell us before it breaks”. It is a reasonable thing to want. Unplanned downtime is expensive, and scheduled maintenance replaces parts that still had life in them.
The difficulty is that genuine prediction of a specific failure, with enough warning to act, generally requires recorded examples of that failure developing. Most operations do not have them, because failures are rare and nobody was recording the relevant signals when they happened. A programme that promises prediction from data that does not exist will disappoint, and will make the next proposal harder to get approved.
The sequence that works
- Measure. Instrument representative equipment properly and collect continuously. See legacy machine retrofit.
- Establish normal. Build a baseline for each machine under its own operating conditions. Machines of the same model in the same plant often differ enough that a shared threshold is useless.
- Detect departures. Alert when behaviour moves away from that baseline. This can support maintenance decisions before enough failure history exists for a validated prediction.
- Record outcomes. When something is investigated or repaired, capture what was found against the signals that preceded it. This is the step most programmes skip, and it is the one that makes everything later possible.
- Predict, once earned. With accumulated labelled history, estimating remaining life or failure probability becomes a question that can be answered with evidence rather than optimism.
What gets measured
Vibration for bearing condition, imbalance, misalignment and looseness. Motor current and power for load, developing mechanical resistance and cycle timing. Temperature and its trend relative to load. Acoustic signature, including ultrasonic ranges for leaks and early wear. Cycle and utilisation data for how the machine is actually being used, which often explains more than any single sensor.
Alerts people will act on
A programme lives or dies on whether maintenance staff trust it. Too many false alarms and alerts get ignored within weeks, at which point the investment is dead regardless of how good the underlying analysis is.
That argues for conservative alerting at the start, thresholds tuned per machine using real collected data rather than defaults, alerts that reach people in the tools they already use, and a feedback route so an investigated alert improves the system rather than vanishing.
How we help
- Scoping. Which assets justify instrumentation, based on what their failures actually cost you.
- Sensing and installation design. What to measure and how to mount it, so the data means something. See sensor selection and signal conditioning.
- Collection infrastructure. Devices, gateways, connectivity, storage and retention sized for the data rate you are committing to.
- Baselining and alerting. Per-machine normals and departure detection, tuned against your own data.
- Integration. Into your maintenance system, so alerts become work orders rather than emails.
- Analysis as history accumulates. Revisiting the prediction question when the dataset can support it. See AI for industrial machinery.
What the predictive-maintenance software would do
- SensorRecord condition signals and operating context.
- GatewayTimestamp, validate and buffer readings.
- StorageKeep asset identities, units and data-quality flags.
- AnalysisCompare with a baseline or evaluate a validated model.
- AlertPresent a reviewable event with supporting evidence.
- Work orderSend an approved action to the agreed maintenance interface.
- Outcome feedbackRecord findings and link them back to the original event.
Sensor choice sets the limits of the analysis. Start with selecting sensors for condition monitoring, then scope maintenance dashboards and alert integration. For installed equipment, review legacy-machine retrofit.
- Asset
- Example pump
- Signal
- Vibration trend
- Review status
- Engineer review requested
- Maintenance action
- Work order awaiting approval
- Outcome
- Record inspection findings after review
A real implementation also needs timestamps, units, data-quality context, permissions and an audit trail.
A pilot acceptance-criteria template
| Criterion | Agree before the pilot | Review evidence |
|---|---|---|
| Data completeness | Usable-sample target, acceptable gaps and asset/time coverage. | Missing-data report and timestamp checks per asset. |
| Alert review | Who reviews events, within what time and with what context. | A record of reviewed events and resulting decisions. |
| False alarms | Define what counts as a false alarm and the observation window. | Reviewed labels, including unresolved events; report the denominator. |
| Maintenance outcomes | How findings, actions and later failures are linked to alerts. | Work-order references and completed investigation records. |
| Data ownership | Ownership, access roles, retention and export responsibilities. | Agreed data dictionary, access test and export example. |
Possible integration outputs include timestamped condition events, asset status through an API, dashboard views and work-order requests. The actual interfaces, permissions, failure handling and deliverables are agreed with the systems your operation uses.
Specify predictive maintenance software around the maintenance team
A useful software brief describes what happens after an abnormal signal arrives. Who reviews it, which evidence they need, how an action is assigned and where the outcome is recorded all affect whether the system supports maintenance. We scope custom sensing, firmware and software together, or integrate with existing data collection where it is suitable.
Requirements to settle before development
- Asset identity: map every sensor channel to the correct machine, location and operating context; record changes when equipment is replaced.
- Missing data: show when readings are stale, incomplete or outside a valid range. A disconnected sensor must not appear as a healthy machine.
- Alert ownership: define who acknowledges, investigates and closes an event, with escalation for unresolved events.
- Maintenance integration: agree the receiving system’s API, mandatory fields and permissions. Use event identifiers to prevent a retried request from creating duplicate work orders.
- Deployment: decide where processing and storage run, who operates them, and how sites work during connectivity loss.
- Review: preserve the readings and maintenance findings behind each decision, so thresholds and models can be evaluated later.
Extend your current tools or build a dedicated application?
If the maintenance team already works in a CMMS, adding a separate queue can create extra administration. An integration may be more useful than another dashboard. A dedicated application may be justified when asset-specific analysis, offline operation or custom review steps cannot be represented in the existing system. We assess this during discovery rather than assume a new platform is required.
Start with a representative asset group and the pilot criteria above. The deliverable should include the agreed workflow, data definitions, access roles and test evidence. Share your asset list, sample data and current maintenance software through the enquiry form below; our dashboard and backend development work can then be scoped around the interfaces your team actually uses.
What we will not claim
We will not quote a percentage reduction in downtime before seeing your equipment and your data. Figures of that kind, quoted in advance, are marketing rather than engineering. What we will do is agree measurable criteria for the pilot, and report honestly against them, including where the data did not support the original hope.
Related
AI for industrial machinery, industrial IoT and equipment monitoring, cloud and dashboards.
Which failures hurt most?
Tell us what the equipment is, what unplanned downtime costs, and whether you already record anything about machine condition or repair history.
What clients ask before starting
Can you guarantee a reduction in downtime?
No, and we would treat any figure quoted before seeing your equipment as marketing rather than engineering. What we do is agree measurable criteria for a pilot and report honestly against them, including where the data did not support the original hope.
How long before the system is useful?
Condition monitoring and departure alerting usually deliver value within months, because they need a baseline rather than failure history. Genuine prediction depends on accumulating recorded failures, which takes longer and cannot be rushed.
We have no maintenance history. Can we still start?
Yes. Start by measuring and by recording what is found whenever equipment is investigated or repaired. That second habit is the one most programmes skip, and it is what makes prediction possible later.
