When an turbine implies degraded operation instead of complete shutdown (not full power when it can) the degraded operation factor shall be classified as degraded downtime for the relevant degraded Wind turbine and in accordance with the availability formula.

Example: Turbine A is operating with cooling issues, therefore the turbine can operate but not on full power, meaning it is curtailed out of safety. In normal operation the turbine is able to produce 4Mw, due to the temperature issue it can now only produce 2Mw. This means that for the time of degraded operation, the turbine availability is 50% instead of 100%.

This contractual formula for Degraded operation cannot be implemented in Breeze to the Time-Based contractual availability right now.
I would really like to see this implemented in Breeze so it can calculate the availability conform contract.

Vestas turbines with PPC uses Power Derete Internal codes that in Greenbyte is called Curtailment mode signals. These signal indicate a curtailment event that could have direct impact on the contracual availibility depending on how they are categorized. What the signals indicate and how they should be catecorized are listed in the Default Power Reduction Mode Allocation List.

The only way to get the Greenbyte system to take this signals into account in the contractual availibity right now is to create an alert and link that alert to one of your curtailment satuses. It not very optimal (with a growing list of 58 signals) and usefull information about what signal ocurs where and when can not be found in the status logs or satus categorization list.

As off today, if 10-minutes data are missing for some reason (scada issue for example), then this period is just not taken into account for contractual availability calculation and for system availability calculation. This is an issue because in many case, when accessing the turbines, the maintenance technicians will shut down the communication to prevent remote restart of the turbine, and this loss of communication will also trigger wrong availability calculation.
We expect time-based availability to be based on the period duration, not the 10-min data being there or not, and during data losses, the turbine should be considered available. It is then the supervisor to add a stop status manually if required.

As off today, to have correct system availabilities, we need to stop status to Excel and re-calculate manually. A bit low tech. It shouldn't be the way.