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
272 results found
-
Edit Status event from Status overview inside Data studio
Normally, We use Status categorization for monitoring/editing/add comment in each of event occured in our wind farm.
but sometime it's easier and quicker if we monitoring the status event by using Status overview which is sub-function inside Data studio.
It would be really great if I also can edit/modify the status right from the bar graph of Status overview.
Hope you understand what i mean.
4 votes -
Change status categorisation to chronological order
Hi,
It would be helpful if the status categorisation window can be changed to allow for a chronological view of the stops as well. In the current configuration, latest stops are prioritised and listed first. It would be helpful to allow for a re-ordering, to start with (oldest last), when specifying a specific month to view all stops.
Hope this helps!
2 votes -
Status Categorization - New main status quick select
Adding a quick option to set a new status as main status for the event would save alot of time in handling contract codes and general cleanup
11 votes -
OPC UA keeps holding data with communicatoin loss
Dear,
We noticed that due to the switch from OPC DA to OPC UA for Vestas turbines, the latest data is been visualized when there is no communication.
This is most likely because of the OPC UA interface that doesn't change its data.
Because of this we can't see if there is a communication loss with a turbine.
To tackle this there should be a timeout implemented when there is no change in the data on the OPC UA interface of that turbine for more than 30 minutes the turbine should be indicated as offline.kr,
Hans1 vote -
Status codes Export grouped/ungrouped
We would like to have the option (via a checkbox) to include the sub statuses of a group while doing an export. The default option would be as it is at the moment, and then there would be a check box, to get all sub statuses if needed.
8 votes -
Custum Delay for Notifications
This is basically a repeated idea, it was requested 4 times before, but always rejected. Does it fit in the roadmap now to have the same options in the dropdown list for the delay in the notification scheme as there is for an alert?
The current notification delay is quite limited, jumping from 1 hour to 4 hours to 24 hours and ending there, whereas an alert can be set to hourly intervals, up to 30 days.5 votes -
Add "Last year" and "Last moth" in the time span of the widgets
We use an average over time graph, and every time we generate a month report (for previous months and years), we have to use the custom interval to adjust the required period. It would be very helpful to add the option "Last month" and "last year" in the time-span
7 votes -
frozen data (turbines seems producing)
We have had the issue that data in greenbyte is frozen and therefore it looks good as there is production. it turned out that there was no connection anymore and it was showing the latest output. When the wind was dropping it was obvous that these turbines could not produce that much, some of them turned out to be even stopped.
idea: Let Greenbyte check every 10min if the wind/KW output changes, it is highly unlikely that these two factors are stable. if stable it means there is a data issue, a notification for that would indicate this tpe of…
3 votes -
Implement dark mode for Greenbyte dashboards
Dark mode setting for greenbyte dashboards would be helpful for those that spend particularly long time periods using greenbyte systems.
Tried using extension however this corrupts certain features so is not a relevant solution.
Dark mode will also reduce eyestrain and related vision issues from prolonged computer use.
8 votes -
Clarity to input signals for calculated values.
In Data Studio, can you show the exact background signal that is used to feed into the calculated value as you hover over the calculated values such as Production Based Availability.
2 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 -
Automate component categorization of statuses
Feature for automatically categorizing status codes to components.
This functionality is currently available for automating categorization towards contract categories (as in screenshot). Improvement would be to add a column with the default component to map the status code to.
3 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 -
Customization of Plan / Personnel Qualifications
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 support
8 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 -
Automatic closing of stop events when the turbine starts generating
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.
5 votes -
Administrate Alerts - Show severity
It would be good to have a severity column when you administrating alerts, sometimes you want to add the severity, but you don't know which alert already has one, so you need to go one by one.
4 votes -
Enable mass deletion of incorrectly created curtailments
Sometimes a lot of curtailment statuses are incorrectly created out of Greenbyte alerts. To delete them one by one is very tedious.
Please add a delete button, under the mass edit menu in status log and status categorization.6 votesThanks for your feedback, this is a great request. It's open for voting from other users.
-
Change the density adjusted wind speed in Power curve analyzer in Data studio as a setting instead of Default
The new feature with density adjusted wind speed in the power curve widget is great. However, the graph in the data studio gets a bit clogged with both options turned on at the same time. It would be good to have this as a setting instead of including both wind speeds by default, in the same way as scatter is a setting to include in the graph
5 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
- Don't see your idea?