Predictive Maintenance Software

Predictive maintenance software for faults your team can detect and act on.

A model is useful only when a measurable condition changes before failure and maintenance can respond in time. RaftLabs develops predictive maintenance software around one equipment class and failure mode, joining condition data with work history, validating warning performance, and sending evidence into the CMMS for technician review.

See our work

Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

Are critical assets still failing between scheduled services while healthy parts are replaced early?

02

Do condition alerts reach a dashboard without enough evidence or lead time for a technician to act?

Plain answer

Predictive maintenance software uses condition and work history to spot equipment faults before failure. RaftLabs develops one warning model, validates warning time and false alarms, and sends evidence to the CMMS for review. A focused first release starts at $30K and takes 12 to 18 weeks.

The alert arrived three minutes before the machine stopped.

The monitoring system was technically right. The temperature crossed its threshold, the alarm fired, and the fault appeared on a dashboard. Maintenance still had no time to inspect the asset or move production.

Predictive maintenance has to change the work plan before the failure. That means finding a reliable precursor, proving the useful warning window, and putting enough evidence into the technician's existing queue.

First scope

01
1 asset class
kept inside the first model boundary
Comparable equipment and operating states
02
1 failure mode
linked to a specific inspection response
An anomaly alone is not a diagnosis
03
$30K
starting development price
Fixed after the signal and workflow audit

RaftLabs does not currently publish a named predictive-maintenance outcome case study. The first engagement therefore tests whether the available condition data supports a useful warning against the buyer's own maintenance history before broader development is recommended.

Prediction is worth developing only when warning time changes the maintenance plan.

Calendar maintenance or simple thresholds are better when they already control the risk at lower cost.

A fit

The asset is critical enough that avoidable downtime or early replacement carries material cost.

Condition and maintenance records can be aligned by stable asset identity and time.

A technician can inspect within the warning window and record what was found.

Not a fit

The asset is cheap, redundant, or easier to replace after failure.

The relevant condition is not measured and cannot be instrumented safely.

Maintenance outcomes are not recorded against stable assets or components.

Scope

What the first predictive-maintenance release needs

  • 01

    Asset and failure-mode boundary

    One equipment class and one costly failure mode define the first test. The team agrees what counts as a useful warning, which inspection follows it, and who may change the alert policy.
  • 02

    Condition and maintenance data model

    Sensor streams are joined with operating state, component history, service records, inspections, and failures. Stable identifiers and time alignment prevent a healthy replacement component from inheriting the failed part's history.
  • 03

    Warning model and evidence

    A threshold, anomaly detector, classifier, or remaining-life model is selected from the data and response need. Each alert carries the condition change and context a technician needs to judge it.
  • 04

    CMMS workflow and feedback

    Qualified warnings enter the existing work process with the asset, urgency, evidence, and recommended inspection. Technician findings close the loop and show whether alerts remain useful as equipment and operating conditions change.

Mixed OEM fleets: mining equipment monitoring

Mining fleets are mixed by nature: one portal shows an engine condition, another system holds the asset identifier, and the CMMS records a repair against a different code. The shift report combines them by hand. Fleet visibility begins with identity and accountable maintenance, not a larger dashboard.

  1. 01

    Asset and telemetry contract

    Reconcile equipment, component, sensor, location, and CMMS identifiers, and map vendor units, codes, sampling cadence, timestamps, quality flags, operating modes, and access limits into a common model. Preserve raw evidence where needed; the common model gives users a stable operational view.

  2. 02

    Condition and alert decisions

    Start with approved thresholds, trends, or combinations for one condition, each carrying evidence, confidence, severity, recommended next step, and suppression state. Communication loss and bad sensors are separated from equipment conditions so noisy data does not become a maintenance instruction.

  3. 03

    Alert-to-action loop closes in the CMMS

    Qualified warnings propose or create work with explicit mapping, duplicate prevention, acknowledgement, escalation, retry, and failure handling. Technician findings return to the monitoring record so rules and models can be judged against what actually happened.

  4. 04

    Fleet operations and stewardship

    Show current condition, stale feeds, open alerts, acknowledged work, and exceptions by site or equipment class, with rule configuration, audit history, data-quality queues, and runbooks that do not hide vendor limitations.

Duty context changes everything. Two haul trucks with the same engine hours degrade very differently; a model that ignores payload, road, and ore learns hard work as failure. Equipment family drives the signal design: haul trucks need CAN and telematics, temperatures, pressures, payload, speed, grade, fault codes, and oil analysis; shovels need hydraulic pressure, temperature, vibration, and duty cycles. If the organisation cannot distinguish a failed component from a planned exchange, improve component-event history before promising a remaining-life model. Mines also operate far from reliable connectivity, so edge processing preserves inference locally, and offline behaviour, model updates, and time sync need explicit design. New pits, roads, haul distances, and ore blends change duty, so monitor feature distributions and retrain. Judge ROI in production terms: tonnes moved, plant throughput, equipment availability, not model accuracy.

Trade-off

Do not replace an OEM portal merely to reproduce its dashboard. Integrate the fleet when a maintenance decision crosses vendor boundaries and approved feeds with representative history are available for a bounded pilot.

Should you use preventive or predictive maintenance?

Preventive vs predictive maintenance

Preventive maintenancePredictive maintenance
TriggerCalendar time, usage, or manufacturer intervalA measured change associated with a developing fault
Best fitKnown wear intervals and inexpensive scheduled workCritical assets where condition gives useful warning
DataAsset register and service scheduleCondition, operating state, maintenance, and failure history
Main riskHealthy parts replaced early or faults missed between visitsFalse alarms or warning too late for maintenance to respond
DecisionService when the interval arrivesInspect when evidence crosses the approved warning rule

Many fleets need both. Prediction belongs only on asset and failure combinations where the extra signal changes cost, risk, or uptime.

How it works

From asset selection to monitored work orders

Prove one warning and response path before covering more equipment.

  1. Phase 1
    01

    Choose the asset and response

    Define the equipment class, failure mode, consequence, warning window, inspection step, and maintenance owner.

  2. Phase 2
    02

    Align condition and work history

    Join sensor, operating-state, maintenance, component, inspection, and failure records by asset and time. Inspect missing periods and changed sensors.

  3. Phase 3
    03

    Validate warning performance

    Backtest alerts by lead time, missed faults, false alarms, operating regime, and the team's capacity to inspect them.

  4. Phase 4
    04

    Connect the CMMS and learn

    Deliver evidence into work orders, record technician findings, monitor drift, and expand only when the first warning remains useful in operation.

What proof should a pilot produce?

A credible pilot should show which historical events would have triggered an alert and how much warning they provided. It should also show missed faults, false alarms entering the maintenance queue, and whether a technician could have changed the outcome. The result should expose assets or operating regimes where the data is insufficient.

That evidence is more useful than a generic claim about reducing downtime. RaftLabs does not publish a predictive-maintenance percentage because performance depends on the equipment, failure mode, sensors, maintenance records, and response window.

An anomaly is called a fault
A change from normal may reflect load, environment, maintenance, or a replaced sensor. Technician review and operating context decide whether it matters.
Different assets share one baseline
Equipment age, configuration, load, and sensor placement can change the healthy range. Compare like with like before training one fleet-wide model.
The warning has no response owner
A prediction that sits on a separate dashboard changes nothing. Route it into the CMMS with an inspection step and accountable person.
Retraining erases the policy
A new model can move alert behaviour. Compare it with the current version and require approval before promotion.

Scope and price

A focused predictive-maintenance release starts at $30K.

Begin with one equipment class, one actionable failure mode, historical validation, and one CMMS path.

We test whether the signal supports useful warning before committing to more asset classes or automatic work orders.

Starting investment

Starts at $30K

A focused first release usually takes 12 to 18 weeks. Instrumentation, safety controls, and sparse history move the estimate most.

Signal audit first

We inspect representative condition and maintenance history before fixing the production scope. If the precursor or response window is not credible, we say so.

Fixed-price phase

Once the asset, failure mode, acceptance measures, CMMS boundary, and handover are agreed, the phase price is locked in writing.

Work with us

Show us the asset that fails between service dates.

Bring its condition history, maintenance records, failure mode, and response window. We will test whether prediction is justified.

  • Scope and cost agreed before work starts. No surprises. No obligation.
  • Working prototype within 3 weeks of kickoff.
  • Pay by milestone. You see progress before each invoice.
  • 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
  • All conversations are NDA-protected.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

The useful data depends on the failure mode. A first audit links condition signals such as vibration, temperature, pressure, current, alarms, or operating state with stable asset IDs, component changes, maintenance work, inspections, and confirmed failures. Data volume alone does not prove the required precursor exists.

Sometimes. Anomaly detection can learn a healthy operating baseline without many failure labels, but an anomaly is not automatically a fault. A technician still needs to assess whether the change is useful. Failure classification or remaining-life estimates need stronger outcome history and enough comparable events.

The integration should send the asset, suspected failure mode, supporting condition evidence, urgency, and recommended inspection into the maintenance workflow. Duplicate suppression prevents repeated orders while one inspection remains open. Technician findings then become feedback for the warning policy and model.

Measure whether the warning arrives early enough to change the maintenance plan, how many real faults it identifies, how many false alarms consume technician time, and whether the team records inspection outcomes. Compare the result with the current preventive or reactive baseline.

A focused first release for one equipment class and failure mode starts around $30K and usually takes 12 to 18 weeks. New sensors, several operating regimes, sparse maintenance history, safety controls, multiple asset classes, and deeper CMMS workflows increase the scope. A complete quote names the equipment class and failure mode in scope, the data work needed before modelling, who does what and who can see and change what, what 'done' looks like for the first release, the system connections the warnings must reach, and anything left out. Changes are priced and approved in writing before the work changes.

Yes, when each vendor or site exposes an approved API, export, gateway, or other supported interface. We map equipment identifiers, units, sampling cadence, fault codes, operating states, timestamps, and data-quality flags into a common contract. Integration feasibility and licence limits are confirmed during discovery, not assumed from a brand name.

Two haul trucks with the same engine hours degrade very differently; models that ignore duty variables learn hard work as failure. Equipment family drives the signal design: haul trucks need CAN and telematics, temperatures, pressures, payload, speed, grade, fault codes, and oil analysis; shovels need hydraulic pressure, temperature, vibration, and duty cycles. If the organisation cannot distinguish a failed component from a planned exchange, start by improving component-event history before promising an exact remaining-life model.

With a canonical asset model and an explicit data-access plan; the platform must handle mixed OEMs without requiring identical parameter sets. Mines operate far from reliable connectivity, so edge processing preserves inference locally, and offline behaviour, model updates, and time sync need explicit design. New pits, roads, haul distances, and ore blends change duty, so monitor feature distributions and retrain.

They can create or propose work when the CMMS interface and operational controls allow it. The design defines equipment mapping, priority, job plan, evidence, duplicate prevention, acknowledgement, status updates, closure, cancellation, and retry behaviour. High-consequence actions should retain the client-approved human review and safety process.

Buy a product when it already covers your equipment class and failure mode, connects to your CMMS in the way your team works, and its way of warning matches how your technicians can respond. Build custom software when your fleet mixes OEM feeds a product does not combine, when the warning has to carry your own duty context and evidence into your own work-order process, or when the failure mode that costs you money is specific to your operation. Either way, the test is the same: the warning has to arrive early enough to change the maintenance plan, and a technician has to be able to act on it.

A focused first release usually takes 12 to 18 weeks. The calendar holds four phases: choosing the asset and response, aligning condition and work history, validating warning performance, and connecting the CMMS so the team learns from what technicians find. The dates also move with things on your side: access to the condition and maintenance records the audit needs, time from the maintenance owner who signs off the warning window, and any safety review the work must pass. The scope document is where the dates for your release are given in writing.

You do, from day one. The code, the accounts, your data, and the project notes are yours from the first day of the work, not handed over at the end, and the notes stay current as the work goes, so another capable team could continue from them.

You already hold everything the work runs on: the code, the accounts in your name, your data, and project notes that stay current. There is nothing to extract from us, so moving to another team, or bringing the work in-house, does not start with recovering your own system. We do not offer source-code escrow, because nothing is held back for escrow to release.

Penetration testing is taken care of. No production data is used in development, always. Backups are tested, always. When someone leaves the team, offboarding steps remove their access. The third-party services the system depends on, including any that process your data, are named in the scope document before signing. We claim practices we can show you, not certifications.

The legal and safety obligations attach to your operation and your equipment, and they stay yours. Scoping names the rules that apply to a system like this one and which controls belong in the build, so you can see what the system covers and what your own operations and agreements must still do. Compliance is shared in that sense; no software delivery on its own makes an operation compliant.

After the first release, continued monitoring, model retraining, threshold changes, and new asset classes are arranged and priced in writing, as ongoing support or as a further fixed phase, or your own team runs them from the operating notes. Standing costs exist whoever looks after the system: hosting and scoring infrastructure, sensor and data-source costs, CMMS and connected service licences, and any OEM feed licences. Those costs are named in the scope, not discovered after launch.

We work on five principles. Switch to async: most updates are written, so nothing waits on a meeting. Be prepared: calls have an agenda and the material read beforehand. Write: decisions, warning thresholds, and changes are written down where both sides can see them, not left in call memory. Ask/tell: questions and bad news travel as soon as they are known, not at the next scheduled update. Own: a named person on our side owns each piece of work, and you can talk to the people doing the work directly.

Yes. We sign your NDA before anything sensitive is shared, and the information you share for scoping stays confidential.

No. The team that scopes your equipment and data is the team that builds the system. Our teams are in India and Ireland, and the people on your calls are the people on your project.

All our AI-assisted work runs through RaftKit, our own AI workflow process, described at raftkit.com. Work moves through five phases, from blueprint to build to review, with quality gates between them. Finished work goes through a two-stage review, with up to 23 specialised AI reviewers checking each task, and the most serious problems block the work from shipping until they are fixed. A named person on our team stays accountable for what reaches you.