Greenbyte Ideas
Our approach to product feedback
The benefits of giving us your product feedback
What happens to your product feedback
How we choose what to implement
- Customer feedback - there are many ways we listen for your feedback:formal customer interviews and other research activitiesevents like conferences and trade showscomments and votes on issues here in Greenbyte & BluePoint Influence
- CSM team insights - our CSM team knows which issues are the most challenging and most common for customers.
- Product analytics - we track how users move through the system, which helps us understand how existing features are being used.
- Product strategy - our long-term strategic vision for the products.
Custom applications
273 results found
-
Site maintenance schedule
Have a maintenance schedule for sites with an alert system for overdue works.
- Security Alarm inspections
- CCTV inspections
- Fire Alarm inspections
5 votes -
Have a maintenance schedule tracker for turbines
Have a maintenance schedule for the turbines with an alert system for overdue works.
- Annual maintenance
- Semi-annual maintenance
- Blade inspection
- HV inspections
10 votes -
Automatic updates of technicians GWO records
Create an API link between the personnel page and WINDA to automatically update technicians GWO records/qualifications using their WINDA ID.
12 votes -
stop button data studio
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 variables
7 votes -
Curtailing park output to max MW
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 -
Auto Comment option for errorcode's.
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.
11 votes -
Data exports - change default setting for file type
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 -
description api key
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 -
Display several power curves relating to different periods
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.
14 votes -
active status event widget should have editable comments
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.
8 votes -
Icing detection
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 for potential powers
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 -
Add turbine reference anemometer for Lost Production Calculation during communication issue
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 -
Find statuses with a comment, to identify major status events
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.
3 votesThanks for your feedback, this is a great request. It's open for voting from other users.
-
add column to active status event
Add 'lost production' to active status event.
4 votes -
Option to upload mass allocation edits to status log
Editing the status log (even mass edit) in the Monitor/Status Categorization page can be a bit cumbersome for large sites. A feature that allows the user to download the status data, update the allocations in Excel and then upload the edited data into Greenbyte would be helpful.
6 votes -
Categorization : mass edit -> make main event of their groups the corresponding status
Each month I have to manually extend all repeating error code 23, and change the underlying substations to "main event of the group".
Would be amazing, and smart, to have the "mass edit" function to promote all selected statuses of each group to "main event" of their corresponding group.
Just like in the following example in the attachment.
9 votesThanks for your feedback, this is a great request. It's open for voting from other users.
-
Adding dynamic tools to report
We would like to have the option to add dynamic tools to the generated report. Moving away from a simple PDF view and being able to show more information, regarding low performance, detailed charts etc. Most of those widgets would be generated via PowerBI and added to the report as custom sections.
4 votes -
Automatic general status for: Does not generate despite the existence of a resource.
There are times when the WTG does not show a failure but despite the existence of a resource it does not generate. For this reason, it would be ideal if there was an automatic event where it shows that there is a resource and the WTG does not generate.
This would be useful to capture moments in which the wind turbine does not generate despite having a resource, due to some failure not expressed in the states.
3 votes -
Comparison of actual production data of different years with each other
Hi all,
I wonder if it would be possible to compare actual production data of different calendar years with each other within one widget or dashboard?
I would like to show to the investors a relative comparison of the production years. This is possible in the Report section, but I would like to have it available in the Analyse section.5 votesThanks for your feedback, this is a great request. It's open for voting from other users.
- Don't see your idea?