A CMMS that schedules off real usage and real risk, not just a calendar.
SMMS (Smart Maintenance Management System) gives planners and schedulers meter-based PM triggers with a re-fire guard, FMEA-linked risk scores to sequence the backlog, real-time parts availability checks, and governed AI-assisted plan drafting that always waits for human review.
What does a planner/scheduler need that a basic work-order queue doesn’t give them?
A planner isn't just moving tickets through a queue — they're deciding which job happens this week, whether the crew has the parts to actually do it, and whether the next PM interval should tighten based on what the equipment is telling them. That needs PM triggers that respond to real usage, not just a date on a calendar; a documented risk score to sequence competing priorities; a way to check parts availability before committing a crew; and AI drafting help for the repetitive plan updates that doesn't require re-checking every field by hand.
Four capabilities, one connected data model
Meter-based PM triggers with a re-fire guard
PM plans can trigger on meter readings (runtime hours, cycles, mileage) as well as calendar intervals, with a unique-constraint guard against duplicate re-fires — a planner isn’t manually tracking which meter-based jobs already fired this cycle.
PM strategy for reliability engineersFMEA-linked risk scores feed scheduling priority
FMEA worksheets carry a computed, database-CHECK-constrained RPN and configurable risk bands — a planner sequencing next week’s work has a documented risk score to point to instead of relying on whoever asks loudest.
FMEA software in SMMSParts availability checked before a job is scheduled
Spare-parts availability is a real, queryable inventory lookup (also exposed to Elisa as a governed AI tool) — a planner can confirm parts are on hand before committing a crew to a job, rather than discovering a stockout mid-repair.
How AI-assisted lookups are governedAI-drafted maintenance plans, always human-reviewed
Elisa can draft or propose updates to maintenance plans through the same catalog-driven, audited action policy every other mutating action goes through — a planner reviews and accepts a draft; nothing publishes itself.
How RCFA findings feed PM changesBuilding next week’s schedule
A planner at Meridian Fabrication Works (a synthetic demo tenant) is building next week's PM schedule. A meter-based trigger for the Cooling System's circulation pump has fired ahead of the calendar interval — runtime hours crossed the threshold early, a sign of a harder duty cycle than the schedule assumed. Before committing the crew, the planner checks parts availability for the bearing kit the job needs; it's in stock at the site storeroom. The job's FMEA-linked RPN sits in the "high" band after a recent RCFA finding raised its Occurrence score, so it gets slotted ahead of a lower-risk job competing for the same crew. Elisa had already drafted an updated PM interval overnight based on the same RCFA finding; the planner reviews it, adjusts the interval slightly, and accepts it.
Limitations
SMMS is pre-revenue with no deployed customer sites — every capability claim on this page is about what the product does today, not about scheduling-efficiency numbers that don't exist yet to cite honestly.
- SMMS does not auto-schedule or auto-assign crews based on risk score alone — RPN and meter triggers inform the decision; a planner still makes the call.
- There is no dedicated crew-capacity optimization/routing engine — scheduling is planner-driven, supported by the data above, not an automated dispatch algorithm.
Frequently asked questions
Can PM schedules trigger off actual equipment usage instead of just a calendar date?
Yes — PM triggers can be meter-based (runtime hours, cycles, mileage) in addition to calendar intervals, with a unique-constraint guard that prevents the same trigger from firing twice for the same meter threshold.
How do I decide what gets scheduled first when the backlog is long?
FMEA gives you a computed RPN (Severity × Occurrence × Detection) and tenant-configurable risk-band thresholds (low/medium/high), enforced by database CHECK constraints so the ordering between your own thresholds can’t drift. It’s a documented number to sequence against, not a replacement for judgment on edge cases.
Can I check parts availability before I schedule a job?
Yes — spare-parts inventory is queryable directly, and the same lookup is available to Elisa as a governed AI tool if you want to ask conversationally instead of running a report.
Does AI schedule work automatically, or do I stay in control?
AI-drafted maintenance-plan changes and work-order proposals go through the same catalog-driven policy and permission checks a human-initiated action would — a planner reviews and accepts a draft before it takes effect. Nothing is published or scheduled without that review.
See risk-based scheduling on your own PM calendar.
Request a demo and we'll walk through meter-based triggers and FMEA-linked prioritization on a tenant shaped like your fleet — or take the free RMI QuickScan first to see where your program stands today.