Recommendation: Review the causes per turbine and prioritise the interventions with the greatest impact on farm availability.
Platform
The second operational layer
Orian sits above the systems you already have: it collects what they produce, interprets it with expert judgement and turns it into traceable decisions.
How it works
From scattered information to a recorded decision
Four steps that repeat every day on every asset in the portfolio.
Step 01
Input
Operational, technical, contractual and manual information enters the system through importers, email and external sources.
Step 02
Evaluation
The evaluator engine checks operations against the defined method and detects deviations, breaches and risks.
Step 03
Interpretation
Each finding becomes an alert with severity, scope and a recommendation, or a report section with its associated calculation.
Step 04
Record
Everything is recorded: what was detected, what was published, what was answered and when it was closed. That record is the basis of certification.
Data model
The structure of the asset, made explicit
Orian models the reality of the asset in five levels. Every data point, every alert and every report is anchored to one of them, which allows aggregation and drill-down without losing the origin.
This hierarchy is what allows the same alert to be read at portfolio level and investigated at component level.
Inputs
Where the information comes from
Orian works with the information that already exists in your organisation, in the format in which it is already produced.
Spreadsheets and operational files
Direct import of the formats already used day to day: production, availability, outages, preventive work and open items. They are configured by data type and by farm.
A dedicated mailbox is read to bring in the information that currently arrives by email.
Weather sources
Integration with open weather services for daily and weekly forecasting.
Manual entry
Point entry of information with no digital origin: minutes, agreements and field observations.
Contractual documentation
O&M contract data, availability commitments and commercial terms.
Asset history
Configuration of every machine and every component, with its intervention history.
Outputs
What the system gives back
All incoming information becomes concrete outputs, each with its own judgement and its own trace.
Recommendation: Analyse recurrence by component and consider a single comprehensive intervention instead of successive corrective jobs.
Recommendation: Update the open-items register and renegotiate the committed dates with the O&M provider.
Recommendation: Quantify the energy not produced and document it for contractual treatment.
Recommendation: Assess the scope of the retrofit and its return before the next outage campaign.
Compliance by farm
Indicator detail
| Code | Requirement | Frequency | Compliance |
|---|---|---|---|
| AC-01 | Daily forecast published | Daily | 100 % |
| AC-03 | Estimated production for the day | Daily | 96 % |
| AC-08 | Monthly availability | Monthly | 92 % |
| AC-13 | Preventive work progress | Monthly | 78 % |
| AC-14 | Open-items register | Weekly | 64 % |
Next step
Let us look at it with your data
We analyse your portfolio, identify what information you already have and show you what you would get from Orian on day one.