258 results found
Add an "Export" option under the "Planned/HSE" tab. Have the option to choose which HSE items to export by state- either resolved or unresolved, as well as by site. Have an option to select the date range.1 vote
The "Greenbyte Forum" event was a really good place to hear about the latest developments, learn from other users, and better understand the Greenbyte product. I'd recommend hosting one in 2024, particularly given the development of Unity, wider coverage of products under PowerFactors, and that it has been a while since the last one.1 vote
For some assets then events have a start date, but do not have an end time due to communication/data issues. In these cases when the turbine start generating, the stop event should end.
Equally, we have the reverse where an event might not have a start date, but the turbine is not generating. It would be good to create a synthetic event for these periods too.2 votes
Please add a delete button, under the mass edit menu is status log and status categorization . thanks2 votes
Hi Greenbyte team,
Is that possible to make customizable the Plan/Personnel Qualifications?
Actually there's much more than AT, CT qualification needed to specify the technicians' qualification for WTSR.
Thank you very much for your support8 votes
Have a maintenance schedule for sites with an alert system for overdue works.
- Security Alarm inspections
- CCTV inspections
- Fire Alarm inspections
Have a maintenance schedule for the turbines with an alert system for overdue works.
- Annual maintenance
- Semi-annual maintenance
- Blade inspection
- HV inspections
Create an API link between the personnel page and WINDA to automatically update technicians GWO records/qualifications using their WINDA ID.11 votes
Sometimes, you perform an data request in the data studio but it takes a long time to load. you sometimes want to make a change to the data request but you have to wait till the data is loaded.
It would be nice to have a stop button so you can fill in the new variables7 votes
Due to various reasons there is a need to curtail the park output to a max MW for a given period of time. E.g. when TSO imposes grid constraints (grid maintenance or grid capacity issues).
The park level max should also be modelled top-down. I.e. not scale on turbine level.2 votes
Some errors are to general (or not telling exactly the status of the turbine), like for example Vestas errors: "RCS 13" or errorcode "user defined alarm 20" Therefore a auto comment would make sence that described the code so all of the teammembers know what is happening on a specific windfarm when those kind of errors occur.4 votes
Can we have the default setting changed from "one file per aggregate" to "one file for all aggregates"? In 99% of the cases, we need one file including all turbines, so we have to change the setting for each export (and often forget to do so...).5 votes
It would be good to be able to add descriptions to API keys so you can document the purpose of the API key.4 votes
Currently, in all widgets and on the data studio, we can only select one time period. To carry out an in-depth analysis of the power curves of a turbine, it would be very interesting to be able to select several periods (one for each PC displayed simultaneously) to detect underperformance more effectively. In addition, it would allow to identify the date of occurrence of an underperformance, as well as to compare wind resources of the two periods on the distribution of the scatter plot.13 votes
In the active status event widget on monitor -> portfolio or monitor -> windfarm, you can easily acknowledge an event by pressing the button. But you cannot double click on a comment section to fill in a comment.
This feature is available in the statuslog, but would be very handy to have in the Active status event widget also.4 votes
There is an existing idea posted in influence regarding the calculation of icing loss by the IEA Task 19 method, but there is no option to comment on it so I created this new topic.
In order to achieve the calculation of icing loss, there should actually be an option to set up an alert that would generate "curtailment" statuses by the IEA Task 19 method.4 votes
Methods currently implemented for the calculation of potential powers are not state-of-the-art.
It would be great if more methods were implemented, like the power-to-power method that Greenbyte wrote a white paper about a couple of years ago, methods involving Machine Learning, methods using learnt power curves computed based on wind speeds from a meteorological model, learnt power curves by wind direction sector with biased nacelle wind speeds measured during stops being rebuilt from data of reference turbines, etc.2 votes
On windfarms of only two turbines, it is impossible to calculate Lost Production to Downtime in some cases.
For example, during a communication issue on one turbine, the other turbine works as reference turbine but the calculation is not performed in presence of any curtailment of the reference turbine.
Add a reference anemometer would allow the possibility to use either Learned or Default PC on the turbine which have no communication, using wind speed signal of the reference turbine.8 votes
In order to quickly see major status events, we would in Status Log or Status Categorization like to filter out all events that have a comment.
In Aug 22, a new feature was released to search within the comments. This is similar but not the same as finding all statuses with comments.2 votes
Thanks for your feedback, this is a great request. It's open for voting from other users.
Add 'lost production' to active status event.4 votes
- Don't see your idea?