Sibilla Kairos In development

Intervene at the right moment. Not too early, not too late.

In Greek, kairós is the right moment. Kairos is the maintenance planner of Sibilla: it reads what the predictive models say, what your maintenance history says and what the SAP PM plan allows, and proposes when to intervene and what to group in the same stop. The decision stays with the planner.

Talk to us about Kairos How it works Back to Sibilla

In development: Kairos is announced here, it is not yet available. When it is, this page will say so.

The problem

Fixed calendars on one side, isolated alarms on the other.

A calendar-based plan replaces components on dates, whether they need it or not. Predictive monitoring says that an asset is degrading and how urgently, one alarm at a time. Between the two sits the planner, who has to decide, often in a spreadsheet, when to stop a unit, what else to do while it is stopped, and whether the crew and the parts will be there.

Predictive maintenance does not always pay off, and a prediction without a plan does not pay off at all. Kairos is the step from "this bearing is degrading" to "we stop this unit in the low-wind week, and we also do the two inspections due that month".

How it works

Three sources, one proposal, your decision.

1

Three sources

Kairos plans on operating hours and on the calendar, combining:
- Sibilla's predictive results: KDI and events, that is which assets have entered the P-F interval and with what urgency.
- The maintenance history: failures, interventions, durations and causes, in the ISO 14224 structure.
- The maintenance plan in SAP PM: scheduled orders, stop windows, resources.
2

A proposal

AI models propose when to intervene and what to group: which interventions to bring into the same stop window, weighing the risk from the fault-tree base and the impact on production. Every proposal shows its reasons: the signal, the failure mode, the history, the constraints of the plan.
3

The planner decides

Accept, move or split a proposal. Nothing is scheduled without a person. Writing the result back into SAP PM is a project-based integration, like every notification towards your CMMS.

Why a separate module

Predictive says that an asset is degrading. Kairos says when it is worth acting.

The predictive core answers "is this asset degrading, and how urgent is it?". Kairos answers a different question: "when is it worth intervening, and together with which other work?". Whoever needs a tool to plan maintenance by operating hours finds here the dedicated tool, which uses the predictive results but not only.

What you need

Sibilla running, a history, a plan.

Available Sibilla on your assets, with models and a KDI history: Kairos reads the predictive core, it does not replace it.
Available A maintenance history: failures, interventions, durations and causes. The closer to the ISO 14224 structure, the better; we help you get there.
Project-based Access to the maintenance plan in SAP PM: read first; write back when you decide so.

SAP is a trademark of its owner; it is cited only to describe compatibility.

Standards

The standards we refer to.

References for method and vocabulary, not labels on the product.

Standard	Subject	With Kairos
EN 13306	Maintenance terminology	The same words for preventive, predictive and condition-based maintenance in the plan and in the proposals.
IEC 60300-3-11	Reliability-centred maintenance	The P-F interval is the window Kairos plans within.
ISO 14224	Reliability and maintenance data	The structure of the history Kairos learns from.
ISO 55000	Asset management	Planning decisions documented with their reasons.

All the standards we refer to · Is predictive maintenance worth it on your asset? · Connectors

Talk to us about Kairos.

If you plan maintenance by operating hours today, tell us how you do it: it helps us build Kairos on real plans, not on ours.

Talk to us about Kairos