It would help a lot if Greenbyte can add "Yesterday" as an option so that creating a daily report for us doesn't need to select dates everytime.

With reference to the implemented mass edit options as requested in "Options for Mass Edit in Status Log and Status Categorisation", one is missing: the "Delete" option.

Voting open for a delete button!

Often, Operational Restrictions (ORs) are in place for sites and/ or turbines. Tehy have different severities. Sometimes, there is a complete "no access" due to safety risks in place. Unfortunately, currently such an "hard OR" cannot be visually distinguished from the other, "lighter" HSE or OR information during the log on procedure.

Suggestion: Own (severe) category and calour (red) for ORs, which deny complete access to a site or turbine due to high safety risk. In addition,such ORs should always be on top of the HSE list during log on!

Currently the ring chart with the real time power is not clearly visible because it is superimposed on the map.

Alerts are really useful, but there is currently no way to display them in reports. It would be great to put an alert log widget in the reports (like the status log). This would make our reports more complete, and allow us to track alerts that would be recurring on certain devices.

We would like to export the status file by only a certain type of status (Stops, warnings ) such as blade bending warning or manual stop event.
same as you can sort events in the statuslog.

It would be nice to know if the event was added manually on Greenbyte, it's possible to see it just in the UI not through the API.

Could you change the overdue icon colour to Yellow or Orange and make it flash if possible.
Currently overdues are show in red and this can be mistaken as a stop fault when carrying out our duties.
If this could be changed to a different colour and made to flash then it would make it easier to notice and less likely to be missed.
Ive attached a screenshot of what an overdue red icon for reference.

For some redundant groups of statuses like Bat Curtailment for instance, it would be a great gain of time to be able to set by default one of the status inside the group as the main status for every status group of the same kind.

This would avoid the repetitive and manual act of setting the status that we want as "The main status event within the group".

I think a feature that notifies us either audibly or via pop up box to site accesses that have gone overdue would be very useful so as to keep visitors as safe as possible while visiting our sites. it means we can then react quicker to over due situations and start the escalation process to reaching them to check on there welfare much quicker . Taking into account that a lot of the sites are in remote locations and so response times to possible accidents or injuries needs to be as quick as possible.

When using export data, it is possible to get other datasignals during the time of a status, for example the exact windspeed, nacelle direction etc. at the moment of a status.

This is not yet possible with API using the Status endpoint. Could this be made possible?

The ability to exclude specific status messages from grouping. We have a specific status that stops the turbine, but is not the main reason if the turbine after that does not automatically start. It should be the next status as the main status. Therefore we would like the option that for a specific status, you can select to not group this status.

We suggest to open up the possibility to create reports in site time. Financial reporting is typically done in site time and therefore the current setup in Greenbyte generates a sync issue if the wind farm is located in another timezone than company time.

Currently, tasks and HSE events in Greenbyte can only be designated as "Unresolved" or "Resolved". Being able to indicate that a task is in progress would make it possible to monitor how quickly action is being taken and ultimately closed out.

We need the possibility to list only HSE cases of a certain status (resolved - unresolved) in the report HSE table widget. Currently it is not possible to have a table in the reports listing only the open = "unresolved" HSE cases.

When metering systems are connected to the Scada one standardized tech. KPI is to understand the middle voltage losses between WTGs and official energy metering.
Ideally such should be calculated on kWh/MWh basis as simple delta between Sum of Energy Export (WTGs) and official Metering. Additionally the % deviation should be calculated, too.

Further benefits:
As Greenbyte introduced the Loss Waterfall also this calculation would benefit from the above as additional losses (depending the size of the wind farm typically 0.5 - 2.x %) could be highlighted. Additional precision for the Loss Waterfall Diagram!

Is it possible to add a "Trainee" section under personnel qualifications? There are many technicians who do not have any qualifications yet and it would be advantageous for OCC etc... to be confident on the status of the technician and know to not allow them to take control of a turbine and that only site access is allowed.

For conditional power curves it would be nice to have the following options:
1. copy the default values to conditonal power curve for editing, that saves time entering the values manually.
2. it would be nice to add a condition: to be able to give a start date + time and end date + time. Currently if curtailment starts at 10:00 at day 1 and ends at 16:00 at day 5 it requires you to manually enter the conditional power curve 3 times!

Is it possible to add ‘Competent Person (CP)’ in the dropdown box on Breeze when adding in a qualification after completion of a site induction.

A CP has more limitations on the tasks they can carry out on the HV/LV system than AP and SAP. A CP id not the same as a CT.