In specific cases warning triggers losses calculation and impact availability. We need an option to turn OFF this logic.
Currently if there is a warning status code and the turbine shows no production during wind high enough to be operational, the turbine is automaticaly seen as faulty and availability is set to 0 for that period. The warnings status code will get losses calculated and attached.
We'd like an option to turn OFF this feature. We consider that, by definition, a warning status code should never trigger any losses calculation and never have any impact on availability figures.
Matthieu Utz
shared this idea
-
Roberta Takeuchi
commented
I had this problem with the service availability, the service category of this warning code was considered as unavailable, so I had to leave without category or chosing/creating a category that is considered as available. In case of system availability, this should not occur (at least I believe it shouldn't)