Asset register and hierarchy
Sites, systems and components in one tree, on a taxonomy of 192 component types in the ISO 14224 style. Viewer, Editor and Superuser roles per organisation, inherited along the tree.
Reference: ISO 14224
Available
Asset management
ISO 55000 describes asset management as the coordinated work of an organisation to get value from its assets. In maintenance, that value is decided failure by failure: which ones matter, how they announce themselves, what to do about them. Sibilla carries the chain from the asset register to the decision, on your data.
Maintenance strategy
Reliability-centred maintenance asks every failure mode the same question: does it announce itself early enough to act? If the warning is measurable and leaves time to plan, condition-based maintenance pays off. If not, a preventive task or a planned run-to-failure is the honest answer.
Sibilla works where the answer is yes. It reads the signals you already collect, notices the degradation at point P and leaves your team the time between P and F to order the part and schedule the stop.
From register to decision
Sites, systems and components in one tree, on a taxonomy of 192 component types in the ISO 14224 style. Viewer, Editor and Superuser roles per organisation, inherited along the tree.
Reference: ISO 14224
Available
A Blueprint describes how a failure mode shows on a type of asset: the signals it needs, the expected degradation pattern, the effects. Your FMEA is where new Blueprints start.
Reference: IEC 60812
Available
Fault trees with 271 failure nodes in the catalogue; risk matrices weighing safety, environment and continuity of service; minimal cut sets.
Reference: IEC 61025
Available
Data quality on every measurement point, then analysis models tested before field use, then KDIs with confidence bands and a log of every run.
Reference: ISO 17359, ISO 13374
Available
Every KDI linked to its failure mode and to its place in the fault tree. Asset Health shows the worst state of each asset in one sentence. The expert decides.
Reference: ISO 13379-1
Available
Inspections suggested from the fault tree; notifications opened in SAP PM, Maximo or the CMMS you already use, following your processes.
Reference: ISO 13374 (advisory generation)
Project-based
The full Sibilla suite
Sibilla's predictive core reads the plant and tells you where to look. Around it, the suite covers the rest of asset management: inspections in the field, work orders, reliability, spare parts, people and contractors. Start with the core and add one module at a time, or take the full suite.
Asset register, guided field inspections and investment planning.
Available
Takes predictive maintenance into the field and up to investment decisions. Inspections run on digital checklists in a mobile app; every report is stored, versioned and approved; what the crew finds feeds a health score that ranks the fleet for replacement and refurbishment. It supports the processes an ISO 55001 asset management system asks for; the system itself remains your organisation's.
Digital checklists on a phone or, for harsh environments, on an optional ruggedised tablet. The technician follows the steps, records measurements, conditions and photos on the asset they belong to, and sends the report for approval.
When Sibilla flags a degradation, the crew does not get a generic task: it gets a card written for that finding. Why this inspection and where to look, with the data behind it; safety first; the tests to run, in order, with the standard each one refers to; what to measure and what readings to expect; the conditions to record; what to report; and a decision guide that says what to do with each result. The card supports the crew; it never replaces the site's work procedures and permits.
Inspection reports are stored, versioned and go through an approval workflow, with an audit trail on the asset register. Coverage, overdue inspections and closure of findings are tracked as KPIs.
Findings and predictive indicators feed a health score per asset. The fleet is ranked on it, and a replacement and refurbishment plan weighs CAPEX against OPEX.
Example (illustrative). On a solar inverter, Sibilla sees the DC insulation resistance fall and stay low. The card tells the crew to measure the combiner feeders one at a time before opening any box, to check the surge arresters first, to run dry and wet insulation tests as described in IEC 62446-1, and to compare the inverter's own reading with a handheld tester: if they disagree, the problem is the sensor, not the insulation.
Works on
What you get
From an alert to a work order closed and recorded.
Available
A lightweight CMMS inside Sibilla, as an alternative or a complement to SAP: plan, schedule, assign, execute and record the work, with permit-to-work and lockout/tagout, time and materials. Every intervention goes back to the models: what actually fixed the problem becomes history the plant owns.
Works on
What you get
The reliability engineer's cockpit: MTBF, MTTR, bad actors, RCM and FMEA.
Available
Turns failure history into reliability decisions. It computes MTBF, MTTR and availability, finds the bad actors with a Pareto analysis and structures the maintenance strategy with RCM and FMEA worksheets, as a natural extension of Sibilla's fault trees.
Works on
What you get
Strategic spare parts across site, regional and supplier warehouses.
Available
Decides which strategic spares to stock, where, and when to reorder, across a network of warehouses: on site, in regional depots and at suppliers or on consignment. It combines failure risk and remaining life from the models with lead times, criticality and target service levels, to keep less capital in the warehouse without exposing the plant to the most expensive downtime.
Works on
What you get
Notifications and maintenance plans in SAP PM, driven by condition.
Project-based
Closes the loop between what Sibilla detects and what the ERP executes: from a predictive alert it creates the notification or work request in SAP PM, keeps the status in sync both ways and adapts maintenance plans and intervals to the condition of each asset. It is built on your SAP system and your processes, by a team that has designed maintenance processes in SAP for twenty years.
Works on
What you get
The plant's memory: failure modes, repairs and root causes, asset by asset.
Available
Captures the maintenance knowledge that today leaves with an external contractor or a retiring technician: failure modes, repairs, root causes, field notes and photos, for each asset. It becomes a searchable library, and it gives the AI agents your real history instead of generic knowledge.
Works on
What you get
Plain-language explanations inside the Sibilla screens.
Available
Brings the agents into the Sibilla screens: next to a report, a data-quality check or the fleet status, it explains in plain words why an asset is in alarm, summarises reports and suggests what to check next. Detection stays deterministic; every statement links back to the evidence, and the decision stays with the expert.
Works on
What you get
Skills and capacity: is the crew qualified for the work, and when.
Available
Manages the people who do the maintenance: a skills matrix, licences and qualifications with their expiry dates, qualification per type of task, capacity planning and dispatch. It answers the question every organisation that brings maintenance in-house has to answer: can our crew do this work, and from when.
Works on
What you get
Make or buy: what to bring in-house, and when.
Available
Supports the decision to bring maintenance in-house with numbers: it compares in-house and contractor cost per activity and asset, follows contractors' service levels, cost and quality during the transition, and builds the baseline that justifies, or postpones, each step.
Works on
What you get
A service: the whole history of the plant, read once, to photograph the starting condition.
Available
Before the models run every day, our engineers read the plant's full history with Sibilla: which signals degraded, when, how often data quality was poor, which failure modes were visible in advance. The result is a report per asset and a shared starting point: what is healthy, what needs an eye, and where monitoring is not worth it.
Works on
What you get
Available: in the current release and optional, switched on in your Sibilla installation if you choose it. Project-based: built on your systems and processes. SAP and the other names cited are trademarks of their respective owners; they are cited only to describe compatibility.
Standards
They are the shared vocabulary of reliability and maintenance teams, so we cite them by name. They are references for method, not labels on the product.
| Standard | Subject | With Sibilla |
|---|---|---|
| ISO 55000 · ISO 55001 | Asset management: overview, principles and vocabulary; requirements for the management system | Evidence on condition and risk for asset decisions.ISO 55001 concerns your organisation, not a software product. |
| ISO 14224 | Collection and exchange of reliability and maintenance data for equipment | Taxonomy of 192 component types in the ISO 14224 style, with failure modes per component. |
| EN 13306 | Maintenance terminology | The same words for failure, fault, condition-based and predictive maintenance. |
| IEC 60812 | Failure modes and effects analysis (FMEA and FMECA) | Each Blueprint watches a failure mode; your FMEA is the starting point for new ones. |
| IEC 61025 | Fault tree analysis | Fault trees, risk matrices and minimal cut sets for each asset type. |
| SAE JA1011 · JA1012 · IEC 60300-3-11 | Reliability-centred maintenance | The P-F interval and the choice between condition-based, preventive and run-to-failure.Defining the strategy with your team: Project-based |
| ISO 17359 | Condition monitoring and diagnostics of machines: general guidelines | From failure modes to the parameters to measure, and how often. |
| ISO 13374 | Condition monitoring data processing, communication and presentation | The same chain: acquisition, data quality, models, KDI, failure mode and risk, decision. |
| ISO 13379-1 | Data interpretation and diagnostics techniques | KDIs linked to failure modes, with a similarity score to the expected degradation pattern. |
| ISO 13381-1 | Prognostics | Sibilla shows how degradation evolves.We do not quote a remaining useful life without a documented case. |
Titles are summarised; the full titles are in the ISO, IEC, CEN and SAE catalogues. Standards for a single asset type, such as ISO 20816 for vibration, are on each asset sheet.
Processes and EAM
An amber KDI is useful only when it becomes an inspection, a notification, a decision someone owns. Our team brings twenty years of maintenance processes in SAP: we design that path with you, on the EAM or CMMS you already use.
Connectors, level by level · How a pilot works
No. Your EAM or CMMS remains the system of record for assets, work orders and costs. Sibilla adds what it does not have: the condition of each asset, read from the signals, linked to failure modes and risk.
No software can: ISO 55001 concerns your organisation's asset management system and is assessed by an audit of it. Sibilla provides evidence on condition and risk for the decisions that system has to take.
Yes, as a project with your team: criticality of the assets, failure modes, and the choice between condition-based, preventive and run-to-failure for each one.
SAP, Maximo and the other names cited are trademarks of their respective owners; they are cited only to describe compatibility.
Tell us the asset, the failure you fear most and the systems you run: we'll show you where Sibilla would notice it.
Request a demo on your asset