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
-
Show windpark/wind turbine/device name in website title
In our operations we often have multiple Greenbyte tabs open in Chrome. It would be very beneficial if the name of page would contain the name of the item you have opened so you can go to the page you want directly instead of checking them one by one.
For example;
Greenbyte - Wind Farms >>> Greenbyte - WindparkName
Greenbyte - Devices >>> Greenbyte - DeviceName
etc. etc.2 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Make it easier to keep the status event start end end e-mails apart
E-mail notifications are in plain text at the start and the end of a status event.
The header is the same in both cases, which is not comfortable.The first word of the header of the second email, when the status is resolved, should be "RESOLVED" or something similar.
In that way one would easily differentiate between an initial status event an the end of this event.3 votes -
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 -
status categorization direct form the task> view page
It would be nice if the status could be categorized from the task > view page.
For now you create a task, add some status codes and than you have to go back to the status categorization, search for the status and than categorize it.
that seems to me a unnecessary long way to do it.4 votes -
Add 'Year to date' and 'all' time selector
I feel like existing Data Studio pre-default time selectors are not enough to cover all most typical situations. I end up selecting a 'year to date' custom period very often, so it would be very good to have that in place.
Also, for verification purposes it would be nice to have an 'all time' time selector, which will take all data available since TimestampStart of the device to date.8 votes -
Proper calculation of time-base availability when data is missing
As off today, if 10-minutes data are missing for some reason (scada issue for example), then this period is just not taken into account for contractual availability calculation and for system availability calculation. This is an issue because in many case, when accessing the turbines, the maintenance technicians will shut down the communication to prevent remote restart of the turbine, and this loss of communication will also trigger wrong availability calculation.
We expect time-based availability to be based on the period duration, not the 10-min data being there or not, and during data losses, the turbine should be considered available.…9 votes -
Monitoring performance of a wind farm with a time span that currently do not exist
I wish to create a dashboard which will contain visuals showing the data of the following time span:
"Last civil month / year" (different from last 30 days / last 365 days) : if today is August 20th, "last civil month" is from July 1st to July 31st
"Contractual year to date" : year to date data starting from the first day of the contractual year (e.g February 1st for a contractual year going from February 1st Y to January 31st Y+1)
3 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Use metadata for alert conditions
I would like to use a metadata field (site and device) as an alert condition. In this case the capacity meta data field.
Anyone who has more user cases where a similar scenario applies - please add your comments!
At present, alerts can only be configured based on absolute values (e.g. MW) and not relative values (%). This means for every new site added certain alerts (e.g. grid curtailment) need to be duplicated and adjusted for the site specific absolute values. It would be easier if alert rules could be defined based on relative values and made applicable to all…
5 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Export Data - Export energy budgets other than the "default" one
In Export Data, I can select the Default Budget signal. However, other budgets that I have created in the platform are not available in that section. It would be good to have them like any other signal.
1 voteThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Make custom section titles visible on the report outline page
When creating a report that contains several custom sections, it's difficult to know which section is which since the section titles don't update.
If I want to see what my custom section is, I need to reload the report and find it again. This is time consuming, especially for reports which take a long time to load.
If the main report outline page updated with section titles, just like the table of contents does, this would make reporting much more efficient.
10 votes -
Power Curve Analyzyer- pls change colours
Power Curves
Please use colours that are more distinguished in difference. As it is now it is very hard to see difference between learned PC in light blue and Best Fit in slightly darker blue.
Neither curves nor scatter plot gets clear enough to actually see any difference! See attached picture.
Thanks & regards :-)7 votes -
Make all data readable through the API
I'd like to be able to access all data visible in GEC through the API.
For example the "potential power order" and "reference devices" from the Admin Turbine view, and data signal mappings from the Comms view.
14 votes -
Alerts: Allow users to manually end and/or delete alerts
We often have the case that alerts are not closed properly or are just generated for testing so manual editing is needed which only GB support can do at the moment. As alerts are user generated (by certain rules), it should be possible to edit and delete them.
12 votes -
In specific cases warning triggers losses calculation and impact availability. We need an option to turn OFF this logic.
Currently if there is a warning status code and the turbine shows no production during wind high enough to be operational, the turbine is automaticaly seen as faulty and availability is set to 0 for that period. The warnings status code will get losses calculated and attached.
We'd like an option to turn OFF this feature. We consider that, by definition, a warning status code should never trigger any losses calculation and never have any impact on availability figures.
6 votes -
Make 'hours per category' (component) table available in Taxonomy
For availability contracts Greenbyte provides a widget called 'hours per category' in table format. This makes it very easy to copy the data into excel.
Taxonomy does not have this functionality though! We can only look at downtime per component as a pie chart.
Being able to show it in a table format and quickly copy/paste this data over to excel for further analysis and reporting (e.g. GADS reporting).
4 votes -
Add site/device access icon from sidebar in widgets
For monitoring turbines, it would we very helpful to have the site/device access icon or similar pictogramm able to be shown within the monitor / portfolio / stops after having connected a device / site access to a stop code. See attached file.
20 votes -
Audit trail of comments in the comments section in portfolio page
Currently, we can only see one comment against the stop and it is often the latest update on the stop. To see a history of work undertaken to bring the turbine back online, it would be useful to have an audit trail of comments that can be saved somewhere in the back end. That basically means that when we use APIs to export the comments in status logs it only pulls the latest comment- like it does now but there should still be a provision to view the history of comments including user, date and time elsewhere in GEC.
5 votes -
Make it possible to use MERRA-2 wind data in Greenbyte
It could be used to perform resource-adjusted budget calculations.
4 votes -
Revenue budget
Such as we have Revenue figures in the system, they would be more meaningful if we also had the Revenue budget (such as the energy budget), which would be simply applying the same fix price per MWh to the energy budget already available in the platform
3 votes -
Delete specific user from site access
When editing an open site access log, make it possible to delete a specific user log from the site access - At the moment when adding people to an open site access log, if you select the wrong person by mistake it is not possible to amend that log. Instead we currently have to set the log off time to the same as the log on time - It would be a lot more useful to be able to delete the incorrect persons details so that they do not show at all.
8 votes
- Don't see your idea?