Greenbyte Ideas
26 results found
-
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 -
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 -
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 -
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 -
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 -
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.
-
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.
-
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 -
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.
21 votesThanks for your feedback, this is a great request. It's open for voting from other users.
-
Filter component in Status Categorization
In status categorization it would be very handy to be able to filter on the component level. For instance to filter on "Manual pauze" in order to easily extract them from a large list and allocate the correct component.
6 votes -
Automatically connecting a status change in case a site access is active on the turbine
Currently if a team is working on a turbine and the status is changing due to their work the new alert is not connected to the site access.
This creates a lot of extra work and does not flag any real issues and needs to be connected manually to the site access.
This would make it way more efficient to work with a dashboard which flags only new issues.9 votes -
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
16 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
