How do you separate instructed curtailment from a real fault?

Loss bucketing is configured with your performance team before anything is ranked, so L1 to L5 above are decided at source rather than argued after the fact. That classification is what makes an availability figure defensible with an offtaker and useful to a maintenance planner.

Does this work across a mixed OEM portfolio?

Yes, and that is the reason to run it beside the OEM portals rather than inside them. We have onboarded portfolios carrying several wind makes, several inverter makes and battery systems from another vendor into one Maximo Renewables instance. Each portal remains accurate about its own kit; the fleet view is what none of them can produce.

Where does it fit if we already run Maximo Manage for the network?

On top of Manage. Manage stays the system of record for assets, work and inventory across both halves of the estate, so renewables work inherits the same competency rules, permit discipline and change control as substation work. Renewables adds the onboarding and analytics layer for the renewables portion, on the same platform we run for Manage under MaxIron-managed hosting.

Who decides which fault gets the crew first?

A performance engineer on your side. Analytics rank candidates by lost generation and confidence; the engineer weighs the access window, crew competency, spares and the forecast, and sets the order with a recorded reason. We build no path where a ranking dispatches a crew to a high voltage site on its own.

Utilities, Renewables

One operating view across the portfolio, on the week the weather decides everything

A utility running wind, solar and storage beside a regulated network carries two operating models in one business. This page runs a storm week through IBM Maximo Renewables from the performance desk and from the crew. Capability on Renewables; sector on utilities.

Book a portfolio onboarding review Back to utilities

One storm week

The same six days from the performance desk and from the crew

The test is the week output collapses for four reasons at once and nobody reaches a turbine until Thursday. Sites and timings are composed from mixed portfolios we have onboarded.

Performance desk

Crew and site

Sun 16:00

Named storm forecast for three days. Monday and Tuesday turbine work stood down in Manage.

Two crews retasked to ground work at Solar Site B; Thursday access window diaryed.

Mon 04:10

Two wind sites cut out as designed. Curtailment covers 40 MW for six hours. Three OEM portals alarm; none sees the others.

Nobody travels. Instructed and cut-out stops need no attendance once both are classified.

Tue 09:30

L1 and L2 hours separated. Two faults remain: pitch fault on WTG-14, string under-performance at Solar Site B. Analytics rank the turbine first; the engineer puts solar first because wind stays above access until Thursday, and records that reason.

Two Manage work orders, parts reserved, permit and competency attached.

Wed 07:00

Wind holds above access all day. Both jobs sit planned, visible to network-side planners.

Authorised person and solar permit confirmed for the minute the wind drops.

Thu 12:40

Wind falls below access. Dispatch follows Tuesday’s order.

Both jobs executed under the same permit discipline as substation work, closed against the asset.

Fri 15:00

Availability read with instructed, weather, grid and fault hours separated.

Offtaker Monday starts from one agreed record.

Classification before ranking

Five stop classes, and where each hour is charged

Until an hour has a class, a curtailment instruction and a gearbox fault look identical in the availability figure the maintenance plan is built from.

Ref	Stop class	What raises it	Where the hour is charged
L1	Instructed curtailment	A dispatch or balancing instruction from the National Energy System Operator, or from EirGrid in Ireland.	Against the instruction, with its reference. The availability figure is untouched.
L2	Weather stop	Cut-out wind speed, icing or lightning risk, recorded against the site for the hours it applied.	Against environment. The turbine did what it was designed to do.
L3	Grid event	A voltage or frequency excursion on the connection, timestamped from the SCADA record.	Against the network, with the event window kept for the connection agreement conversation.
L4	Asset fault	A stop code or an under-performance that the OEM portal and the SCADA record agree on.	Against the asset in Manage, as a work order carrying a failure class.
L5	Unclassified	A stop with no code, no instruction and no weather record behind it.	Held open. An unclassified hour is a data defect and is worked as one before the figure is signed.

Codes L1 to L5 are stable across performance reports and offtaker reviews.

Boundaries

Three limits worth agreeing before an onboarding is scoped

Each changes what a first onboarding should cover.

Weather and your safety rules set the access window

Wind speed, lightning risk, sea state and your own authorisation rules decide when a crew can climb. Renewables decides which job the crew goes to when the window opens.

Metering and settlement stay with their own systems

Availability and loss attribution here are operational. Commercial settlement, metering and subsidy reporting stay with the systems and people who own them, and receive an operational record that agrees with the work record.

One fleet view rests on one data model

Different tag conventions, structures and levels of API maturity per OEM make onboarding real engineering. Where a site has thin data we scope the first phase narrower and name the sites it covers. The wider sector approach is on Maximo for utilities.

Onboarding

What a mixed portfolio has to carry, technology by technology

The fleet view is only as good as the structure underneath it.

Wind: turbine, tower, gearbox, pitch system, converter

Each carries its own record, so a fault lands somewhere specific. SCADA over OPC UA or Modbus, stop codes mapped per OEM, and the IEC 61400-25 signal set where the make supports it. Two wind makes means two mappings onto one taxonomy, and that mapping is the work.

Solar: inverter, combiner, string, module

String level output is retained, because a fortnight of quiet under-performance is invisible at site level and obvious at string level. Dataloggers arrive over SFTP at 5 or 15 minute resolution where a site has no API.

Battery storage: rack, module, power conversion system

Cycle counts, state of charge windows and temperature per rack. Degradation is read against the warranty terms, so each BESS record carries its warranty reference and its commissioning capacity test.

Sites with no usable interface

Where an OEM portal exposes no API and the site has no datalogger, that site is named as outside the first phase rather than left as a hole in a fleet view. The general capability sits on our Renewables page.

Where this sits

IBM Maximo Renewables for utilities, questions we are asked first

How do you separate instructed curtailment from a real fault?: Loss bucketing is configured with your performance team before anything is ranked, so L1 to L5 above are decided at source rather than argued after the fact. That classification is what makes an availability figure defensible with an offtaker and useful to a maintenance planner.
Does this work across a mixed OEM portfolio?: Yes, and that is the reason to run it beside the OEM portals rather than inside them. We have onboarded portfolios carrying several wind makes, several inverter makes and battery systems from another vendor into one Maximo Renewables instance. Each portal remains accurate about its own kit; the fleet view is what none of them can produce.
Where does it fit if we already run Maximo Manage for the network?: On top of Manage. Manage stays the system of record for assets, work and inventory across both halves of the estate, so renewables work inherits the same competency rules, permit discipline and change control as substation work. Renewables adds the onboarding and analytics layer for the renewables portion, on the same platform we run for Manage under MaxIron-managed hosting.
Who decides which fault gets the crew first?: A performance engineer on your side. Analytics rank candidates by lost generation and confidence; the engineer weighs the access window, crew competency, spares and the forecast, and sets the order with a recorded reason. We build no path where a ranking dispatches a crew to a high voltage site on its own.

Bring us your worst week.

A week where output collapsed, the portals disagreed and the availability figure took days to settle. We walk it back hour by hour against L1 to L5 and say what an onboarding would have to cover.

Bring this to the first call

Your site list by technology and OEM, including sites with no usable portal API
The last availability figure you had to argue about, and who with
How renewables work reaches your Manage instance today
Your access rules: wind speed, lightning and sea state limits

Book a portfolio onboarding review How we deliver Renewables generally