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
17 results found
-
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.
-
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.
-
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.
-
Setting a default "Main status within the group" for specific status groups
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".
9 votesThanks for your feedback, this is a great request. It's open for voting from other users.
-
exclude specific status from grouping
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.
20 votesThanks for your feedback, this is a great request. It's open for voting from other users.
-
Display availability in status log
It would be great if, in the status log (the one in data studio), one would be able to see how much one stop/status affects the availability for that turbine during the given month or period.
This would significantly facilitate the process of comparing the data in Greenbyte to that of the service provider.
4 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Provide the ability to manually make a stop active
Sometimes it's necessary to set a previously closed stop code back to active in Greenbyte, or the user may have to create an active stop manually. It is not possible to create the active stop today.
Making a stop active can be done by contacting Greenbyte support, however, this takes time and can be tedious for large sites with multiple stop codes to re-open.
It would improve the usability of the system and improve the overall status log functionality if it was possible to manually set a stop code as active, and not have to go through GB support each…
10 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Add button "Uncollapse all / Collapse all"
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".
6 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Having the ability to lock certain statuses belonging to long standing issues
Having the ability to lock certain statuses belonging to long standing issues for example: Turbines stopped for Gearbox replacement- if the PLC sends a new error status to Scada and Breeze task will vanish along with comment. Having a lock status option would prevent such issues
15 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
status log: add column with losses for stops
When you want to knwo the losses of a specific stop, yu have to press the 3 points, analyze. That takes a lot of time. Please add a column with the losses for every stop.
7 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Rule-based status categorization
For some OEMs, the order in which status codes come in can indicate if an event is contractually available or not.
For example, if code A comes in followed by code B and then code C, it's a maintenance event (OEM liable). But if code A is followed by code D and then Code C, it's an owner-liable event.
Being able to automate the categorization of status events based on rules would help with the categorization of these kinds of downtime events.
7 votes -
Display totals in Status logs
In Status Categorization,
1- why don't you display the losses together with the downtimes for each line?
2- then could you display the total of losses and downtimes for what is on display (and thus filtered)?
It could be very useful so to know the total of losses and downtimes for a specific downtime code by example, or any other filtered downtimes8 votes -
Make it possible to sort columns in Status Categorization
I want to be able to arrange the downtimes by duration, WTG, start time, end time, category, code, comment, etc.
37 votes -
Status Log: Display Days - Hours and Minutes
I would like Breeze to display durations on status logs / stops in days - hours and minutes. At the moment it rounds it up or down to days which is not a true reflection of the length of the stop and is a misrepresentation.
4 votesBringing this back on based on requests to see if we get more votes on it.
-
Status Categorization: Assign task from drop down (same as category)
Task asignment is somehow impractical. It would be very useful to be able to asign a Task from the Status Categorization window - same as for Contract Category.
10 votes -
Status Categorization miscelaneous filtering option
Detailed description
A few suggestions related to Status Categorization:1 - Be able to filter out Status Codes from being displayed. I may not want to see irrelevant status (untwisting) or too frequent status (curtailment) Same as filtering out status with time < xx 1 Add a Task combo to easily apply a Task to a Status Code (same as with Contract Category)
2 - Bulk Assingment. Add a checkbox next to Status Code so you can select several Status and apply the same configuration at once (Contract Category - Comment)
3 - When Expanding Status Codes - add a…
5 votes -
Status categorization / Status log: improve grouping / splitting meachnism
(1) Ignore warnings in the grouping/splitting meachnism. The most issues we have right now with grouping/splitting are related to warnings - as a stop can not be split if there is a warning in the period.
(2) Auto-split status groups when there is a change in the availablity category (as this is the normal use case for splitting - e.g. if the turbine has an error (unavailable) after a planned grid shut down or maintenance (available).
(3) Auto-split in certain special cases. E.g. Nordex 920 (icing status) change to 921 (MET Ice detection alarm finished) - WT remains stopped and…
16 votes
- Don't see your idea?