Proper calculation of time-base availability when data is missing
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.
Erwann Euzenat
shared this idea
