Equivalent Full Load Hours is sometimes shown in "hours" in the platform, but sometimes is shown in "seconds" (like Share->Export Data, or Reports->Time series table (widget)).

This indicator is useful in hours, can this be resolved?

Equivalent Full Load Hours is sometimes shown in "hours" in the platform, but sometimes is shown in "seconds" (like Share->Export Data, or Reports->Time series table (widget)).

This indicator is useful in hours, can this be resolved?

In the mobile version the dashed line is the potential power while in the desktop version the dashed line is the actual power. Pretty confusing, could you make the formatting identical?
Cheers,
Yannick

Would it be possible to add a category "Miscellaneous" to the list of task categories. Right now there is one called unknown which sort of does the job. However, when displaying the tasks in our monthly reports to our customers, that particular category name might imply that we lack information regarding the subject. It would be preferable if something more neutral like "Miscellaneous" would exist.

Question related to production forecast. For signal power forecast the time span (one day period) is missing. The only option is to choose custome time interval, but it result in a constant reedition widget with the new day. Whether such an implementation is possible?

We use the HSE feature mainly to notify the on-site technicians about HSE warnings by the OEMs. These are valid for all turbines of the same type (e.g. Vestas V-112, Enercon E-82 etc), so it would be very helpful to bulk-create and bulk-resolve such warnings for all affected turbine types (side note: as HSE warnings might be country specific, the option of selecting the assets/countries should still exist).

We have different availability targets for our O&M contracts (e.g. time-based with exclusions) compared to for internal reporting and monitoring (e.g. production-based system availability). It would be good to be able to set different targets for different availability KPIs.

You can see how confusing this is with only one availability target number in the Key Metrics attached. In the example the difference is negative for Production-based Availability, but positive for the other availabilities, while this is really down to the calculation methodology for each and not a fair comparison to budget/target availability.

Hello, I would like to filter the data based on the timestamp.
In France, we have 2 different noises curtailment - 1 during night period (10PM to 7AM) and the other during day period (7AM to 10PM).
When I display the PC during 1 year, it includes all timestamps, but in my case, I may only require the night/day period during this whole year.

I'm missing the option to filter on WT-types in Data Studio. We have a great variety of WT-bands and WT-types. Therefore it would be great to be able to filter in order to ease the evaluation within certain WT-types.

Objective 1: Get task comments and Device Accesses for more than one taskId or SiteAccessId at a time in a similar way to the site access/ tasks API.

Objective 2: Get device access comments.

It's a fixed period. It's possible to select Categories and State, but not the period.

It would be beneficial to be able to export the data used in a specific visualization through the three bar menu, or from data studio with an option instead of trying to replicate the data needed in the data export tool.

Add data channels in Bright for sun elevation and sun azimuth based on site coordinates that are set in metadata, and allow these channels to be queried through the API.

These data channels could be used to correlate the actual irradiance to the sun's position, or performance metrics against the sun's position to help identify if areas of underperformance are due to a specific location of the sun.

The addition of Scatter Plots (similar to what is currently available in Breeze) for the Bright platform to allow data analytics for metrics such as Performance Index v Irradiance, or Current vs Voltage on sub-dc monitoring channels

Contractual agreements may define a fixed number of hours of scheduled maintenance as Available. It seems this is not supported by Greenbyte yet. Please add.

While checking the correct grouping of Status events, we need to uncollapse them one by one.

This is not very RSI friendly.

We would like a button in one of the top rows "Uncollapse all".

We have a target availability on the Wind Farm and on the Wind Turbine level. It would have been better to have both as the target is not accurate when using only wind turbine level in our case.

It would be nice if the app and the web page could use the maximum power curve value instead of installed capacity in the power bars.

This would improve our visual knowledge if the machine is running accordingly to the current PC.

Some wind farms have grid export limits that are less than the installed capacity of the wind farm. When the farm output is at its export capacity, for any turbines that are stopped I would like the loss of production to be zero as the wind farm is not actually losing this potential production.