Module

Alerts

Early detection. Immediate control.

Operational control

What it does

A system that watches what nobody has time to watch

Orian runs 97 automatic evaluators over operational information. Each evaluator checks a specific condition — an availability deviation, an overdue preventive job, an accumulation of corrective work, a grid limitation — and, when it is met, issues an alert.

Every alert arrives with a severity, a scope, the data that triggered it and a recommended action. It is not an alarm: it is a prepared decision.

Active alerts 97 evaluators · 12 families

E-12-I-05 The number of turbines with low availability has increased considerably Critical

Recommendation: Review the causes per turbine and prioritise the interventions with the greatest impact on farm availability.

E-03-I-19 Accumulation of corrective work on the same wind turbine Serious

Recommendation: Analyse recurrence by component and consider a single comprehensive intervention instead of successive corrective jobs.

E-08-I-10 Open items whose resolution date has already passed Serious

Recommendation: Update the open-items register and renegotiate the committed dates with the O&M provider.

E-13-I-05 Increase in losses due to grid limitations in the current month Important

Recommendation: Quantify the energy not produced and document it for contractual treatment.

E-09-S-06 Possible retrofit applicable to the same platform Moderate

Recommendation: Assess the scope of the retrofit and its return before the next outage campaign.

Capabilities

How the alert engine works

12 thematic families

Evaluators are grouped by area: commissioning and initial contracts, monthly values, outage control, daily weather forecast, weekly work forecast, O&M meeting minutes, preventive work progress, turbine open items, major corrective work and retrofits, ad-hoc data entry, low availability and grid limitations.

Five severity levels

Critical, serious, important, moderate and minor, so that priority does not depend on the reader's interpretation.

Defined scope

Every alert states whether it applies to the portfolio, the farm, the wind turbine or the component.

Associated recommendation

The alert does not only describe the problem: it states the expected action.

Output channels

Alerts are published as operational notices, incorporated into the daily news or fed into the spoken summary.

History and status

Every alert keeps its trace: when it was issued, what triggered it and when it stopped being active.

The real product

A capture of the running system

An image taken from the system in production, with real data from the demonstration portfolio.

Orian critical alert about the duration of preventive interventions at a solar plant — **Real capture** Critical alert with the detail of the finding, the affected objects, the recommendations and last month's registry by type of intervention.

Orian alert about the excessive duration of the last preventive at a wind farm — **Real capture** Follow-up alert: actual versus estimated duration of the last preventive, with the forecast against execution comparison.

What you get

Systematic detection of deviations that go unnoticed today.
Objective prioritisation based on severity and scope.
A recommended action on every alert.
A historical record of everything detected and how it was resolved.
An objective basis for claims and for the contractual relationship with the O&M provider.