If the codes are noise, everything built on them inherits the noise — every FMECA, every RCM review, every condition-monitoring business case. The evidence exists. It's trapped in free text.
A fixed-fee audit first, so you know exactly what your data can and cannot support before committing to remediation. The sequence is deliberate — each stage pays for the decision to take the next.
Your history scored against your own asset and reliability structures — or ISO 14224, where the standard is the target: code integrity, field completeness, downtime attribution. Quantifies the decision cost of what's missing and maps the remediation. The report is yours — whoever you hire to act on it.
AI-assisted classification of free text into equipment class, subunit and maintainable item, with failure mode, mechanism, cause and detection method. Every machine suggestion carries a confidence score; low-confidence records are human-verified. Delivered as clean tables your EAM and BI consume directly — coded to your catalogue, or to the standard where you choose it.
Monthly ingestion, exception queues for new records, code-catalogue governance and drift reporting — so the standard holds after the project ends, not just at handover.
Remediation fixes the history you have. Capture fixes the history you're about to write. A Regulus capture agent — a phone line or chat the artisan reaches during the breakdown — takes the story in their own words, asks the follow-ups a reliability engineer would, and writes the record fully coded into your EAM. Ninety seconds at the machine instead of a Monday batch entry.
Regulus works only on equipment data — downtime, work orders and notifications. Operator and technician fields are excluded at ingestion, so there's no personal information in our pipeline to begin with. What remains is still production data — original values preserved, every transformation logged, and nothing that leaves your boundary.
We ingest only equipment, downtime, work-order and notification fields. Operator, technician and HR-linked delay reasons are excluded before processing — they never enter our pipeline.
A GPU appliance in your server room running our stack. Records never leave your network. An in-region private-cloud option exists for sites that prefer it.
No third-country APIs in the pipeline. Data-residency rules never come into question, because nothing crosses a border to begin with.
Models fine-tuned on your data belong to you. Contractually. They don't train anyone else's product.
For a listed company, downtime data is production data — price-sensitive by definition. It should never transit a public API, so in our pipeline it doesn't.
Every plant writes its own shorthand. Generic models guess at it; a model fine-tuned on your code catalogue, asset structure and years of long text doesn't have to.
Built by engineers who sign off maintenance strategies and write the capital motivations that bad data blocks — fifteen-plus years in heavy-industry asset management and reliability engineering, now paired with private AI infrastructure. Not a consultancy that read the standard. People who live with its absence.
Founding-client pricing for the first three sites, in exchange for a written case study.