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
268 results found
-
Defining alerts based on status or warnings that have no duration
In some cases, status or warning have no duration, but inform about the beginning or the end of curtailment, for instance.
It would be useful if alerts could be set up by a status/warning code indicating the beginning of some event, and another status/warning code indicating it ended.4 votes -
conditional powercurve
For conditional power curves it would be nice to have the following options:
1. copy the default values to conditonal power curve for editing, that saves time entering the values manually.
2. it would be nice to add a condition: to be able to give a start date + time and end date + time. Currently if curtailment starts at 10:00 at day 1 and ends at 16:00 at day 5 it requires you to manually enter the conditional power curve 3 times!4 votesThanks for your feedback, this is a great request. It's open for voting from other users. -
Site time should match SCADA time during summer months (not just in winter!)
In summer when Australia/Melbourne shifts to Australian Eastern Daylight Time (AEDT = UTC+11) 'Site time' does not match the Vestas wind turbines which always follow Australian Eastern Standard Time (AEST = UTC+10). It would be preferable for the Site time to always match the SCADA data. Thanks!
4 votes -
Production losses are calculated towards to Warning events
Would be possible chance configuration so that losses are not calculated toward to warning event? It looks little bit strange in monthly report if losses are calculated toward to warning (this is not root cause for losses). This is not good function in some old wind farms where are all time active warnings. This feature would be individually changed in every wind farm if somebody want that losses are calculated toward to warning.
I would like suggest next: In Breeze, there is general information code (blue) some is generated automatically by Breeze when next conditions are filled.
- Now active stop-code
- …
4 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.
-
Status changes trazability via API
when it comes to refreshing a status database via API, it is quite challenging to update manual changes in the status (i.e, category changes, group structure change, manually added stops that change the group structure,,,)
Would be great to have in the API some way to trace those changes. For example, "last modified" point in the API would already help. It would also be nice to know if the event was added manually, see image.
4 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Plain text notifications for Alerts
For Stops Greenbyte can email notifications in plain text format that are easily processible for other systems (unlike the HTML type messages with nice layout). I would like this to be extended to Alerts, shouldn't be a large job I guess??
4 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Target availability on Wind Farm level
We have a target availability on the Wind Farm and on the Wind Turbine level. It would have been better to have both as the target is not accurate when using only wind turbine level in our case.
4 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Be able to select past contractual years
"Contractual year" exists, this is great. I would also like to selected "past" contractual years.
4 votes -
30 minute resolution data, this would match how revenue meter data is supplied
I want to see 30 minute resolution data, this would match how revenue meter data is supplied and could be compared directly against SCADA for anomalies
4 votesIn the meantime, you can plot SCADA data on 15-min resolution and compare to 30-min meter data. Alternatively, you can aggregate meter data to 1-hour and compare to 1-hr aggregations of SCADA data.
-
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 -
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 -
Make it possible to use MERRA-2 wind data in Greenbyte
It could be used to perform resource-adjusted budget calculations.
4 votes -
Add new modifiable Production-based System Availability signal
Add a new, additional availability signal called “Corrected Production-based System Availability Estimate”, that we could modify so that we could fully exclude from the availability calculation certain days for certain turbines (related to e.g. insurance cases, grid outages etc). Otherwise the availability should be an identical copy of the standard Production-based System Availability. We would need to have the possibility to later adjust the lengths of those excluded historical time periods several times, as our estimates get more accurate in time, and the availability calculation should be instantly updated accordingly. We would like to have the possibility to use the…
4 votes -
Reports/ Power curves - allow to change/fix the scale of the x- and y-axis
x-axis: right now it is scaled automatically accoring to the wind speed data points - i. e. we sometimes have differently scaled power curves in the same report. Instead the x-axis should be fixed (e.g. according to the reference power curve)
y-axis: we would like to show negative power values in order to show stops for some turbine types (e.g. Vestas) - where the power becomes negative if the turbine is stopped.
4 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.
-
Analyze Dashboard: custom interval+zoomable graphs
Make it possible to set and a custom interval in Analyse Dashboards - in order to review what happened during a specific interval. In addition to the above it would be very usefull if the same zoom functionalities could be used as in Datastudio to zoom into a certain period. This way the user does not have to open each graph seperately in datastudio to do the zoom actions but it can be done directly from the analyses dashboard.
4 votes -
Show names of personnel on site access overview page
Show names of personnel on site access overview page - so you don't have to hover over them to see the names.
4 votes -
Add new performance index calculation method - avoiding false low performance alarms
With the current definition of the performance index (PI = P act/P pot) and the way it is used in the low performance alarm ("average the PI in the period x if the average wind speed is above y") - we often see false alarms due to too high performance index volatility and especially PIs dropping at low wind speeds. This could be solved with a PI definition that focuses on the difference between P act and P pot rather that the ratio P act/P pot - the modified formular being PI mod = (P rated – (P pot -…
4 votes -
Attach Active Custom Alarms to Tasks
It would be useful to be able to attach active custom alarms to tasks. Some of the alarms that we have created - we would like to associate with a task to signify to the operator that the alarm has been analyzed and categorized. This would be similar to how statuses can be associated with a task.
4 votes
- Don't see your idea?