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
276 results found
-
Reporting Terminology
It would be useful if you had the option to manually change the reporting terminology. For example our clients do not recognise the the terminology "Time-based Availability (Global).
1 voteWe have great new features lined up that we can't wait to share with you. Unfortunately this request is not part of the roadmap.
-
Make it possible to manually edit the end time of a status event
There are instances when the end time of a status event in Greenbyte is not correct.
For example, if a turbine is stopped and loses communication with Greenbyte. The end timestamp of the stop event will often appear in Greenbyte as the same timestamp that the communication outage was fixed. In reality, the stop event code may have occurred earlier than that (Greenbyte just didn't know, since communications weren't active).
The only fix today is for the user to contact Greenbyte support and request the change be made by them. This is inefficient and can be particularly cumbersome when working…
3 votesWe have great new features lined up that we can't wait to share with you. Unfortunately this request is not part of the roadmap.
-
Performance index should exclude periods below cut-in wind speed
Currently, if wind speeds are low (e.g. below cut-in), Greenbyte still calculates performance index. The values in this range are typically ~100%, which skews the PI metric, since PI isn't really defined in this range.
This results in PI values that can be inflated if wind speeds have been low over the time period in question.
1 voteThe PI calculation already accounts for this.
-
Aggregation of Inverters into Inverter stations
Hello,
Would it be possible to aggregate Inverters in particular String inverter on a dashboard so they show as inverter stations?
I.e
Inverters 1.1, 1.2, 1.3, 1.4 display data as Inverter station 1 (IS1)
and so on for all inverter stations based on the metadata.
This would be particularly useful as it is very difficult to look at graphs of string inverters that cover a site of 50+ string inverters.
Regards,
Calum
1 voteWe can already do this in Greenbyte. Please take contact with your CSM to get more information about how to do it.
-
Normalised string current in table
Be able to produce a table for the last 24 hours (or last full day) of normalised string current for either all strings at a site or an individual CB
1 voteWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Priority of statuses
When several statuses happens at the same time, the system often chooses the wrong status as the main status. If it is possible to priority statuses over eachother, it would reduce the time chaning status (and categorisation)
Example, Repair and Maintenance should go before Idling at turbine2 votesWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Contractual maintenance hours
Contractual agreements may define a fixed number of hours of scheduled maintenance as Available. It seems this is not supported by Greenbyte yet. Please add.
9 votesWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Repeating errors via Alerts: ignore sub statuses
We appreciate the new functionality to add generic repeating errors via alerts with the "stop" and "occurs at least x times" conditions. However, such alerts are currently looking at all stop statuses, i.e. also sub statuses under a certain status group. This leads to the problem that we currently get a lot of alerts if e.g. a turbine is spamming a lot of statuses while being manually stopped during maintenance. Therefore, the alert should only focus on main statuses.
1 voteWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap, but we have just delivered other great functionality in this area.
-
Scheduled Turbine Control / Shutdown Feature
For bird regulations it´s more and more necessary to shutdown turbines for certain days and periods over a week. Especially for issues with cranes or red kites we would like to have a "scheduled control feature" or "scheduled shutdown calendar" in which you can set times and turbines for being ramped down & up in advance (e.g. monday morning for the whole week).The actual "turbine shutdown feature" only allow instantaneous ramp down & up of a wind turbine but no advanced scheduled programming. An instantaneous shutdown feature doesn´t give us the efficiency and flexibility to handle a big portfolio with…
1 voteThis is a great request, but we cannot commit on any future development in this area, at least not right now. But stay tuned!
-
We would like to have an easy way to download data that can be manipulated in a different sowtware (e.g. Excel).
At this time the data export option is not much flexible, and the data exported have a format that can't be easily manipulated, probably due to the configuration of decimal point (GB uses dot (.) but in some countries is used the comma (,) This could sounds trivial, but there is a big problem at the time of manage data from different sources. Could be possible to implement a tool that allows the direct download of the data from a widget for example?
1 voteWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Coustum Delay for Notifications
I need the option to coustmise the delay in the notefication scheme.
(1-24h)
Wait for [1,2,...,8,...,24] before sending a notification1 voteWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Searching in the status category on certain text is not possible
We noticed for instance many pitch related errors for a wind farm.
We needed an overview of all those related errors. It seems that many different related errors had all the word “pitch” in the error description. But in Greenbyte I cannot filter on a description “pitch” and report all losses to those specific errors.1 voteWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Can't see which turbine in "Turbine status" widget that's affected
It's very hard in the turbine status widget to see which turbine is affected by a warning or error since our naming convention starts with the project name, for example "Häjsberget" and then the turbine number.
So, I'm wondering. Instead of seeing just "Häjsb..." for all turbines in this windfarm in the park. Could we either get the turbine number included or a possibility to remove the "ID" column in the widget and get some more space or perhaps display a turbine "nick name" or alias that we set ourselv instead?
I'd like it to show either "Häj...14" or if…
3 votesRemoving the ID column should be already supported by this workflow:
1. Click the three lines in the top-right corner of the widget and select Edit.
2. In the Columns field, deselect the ID column.
3. Click Save. -
Make "Multi-year Average" widget suitable for Energy signals
This widget currently presents averages of data. This is not suitable for Energy signals, and this would probably be one of the most useful use cases (comparing the energy from this year against other years).
3 votesWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Page breaks in report notes sections
The notes sections in reports have limited functionality which could be improved greatly if there was an option to insert page breaks rather than having to estimate where these will appear once the report is generated
1 voteWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Scatter Plot for Bright Platform Widgets and Data Studio
The addition of Scatter Plots (similar to what is currently available in Breeze) for the Bright platform to allow data analytics for metrics such as Performance Index v Irradiance, or Current vs Voltage on sub-dc monitoring channels
2 votesSince there is a workaround for this specific use case, we won’t add this request to our roadmap.
-
Finding the wf in monitor view fast an easy
To be able to color code the buttons
1 voteWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Add table widgets/reports with columns containing different time intervals
Please add tables with columns containing different time intervals, for example to quickly have a view on the availability for all months (separately) during the past year and a final column with sum/average.
Columns would then contain different turbines/wind farms.
It would also be interesting to see the individual turbine availability in rows after the corresponding farm availability.1 voteSomething similar is available with rows and columns reversed. We hope this fulfils your use case.
-
Add a "Severity"/"Category" field for alerts
It would be really helpful to be able to categorize alerts ( "HSE" , "Main Components", "Performance", etc...) or at least be able to label them with a "Severity" level : Critical / Major / Minor etc.
5 votesWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
The formatting of the power graphs in the app and on the website are differtent
In the mobile version the dashed line is the potential power while in the desktop version the dashed line is the actual power. Pretty confusing, could you make the formatting identical?
Cheers,
Yannick1 voteWe have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
- Don't see your idea?