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
-
Create a specific degradation factor for the first year
The solar panels manufacturers commonly warranty a different degradation factor for the first year than for the following ones (see example attached: a 3% degradation is expected for the first year, then a 0.706% factor for year 2 to 25).
Could you create a separate degradation factor for the first year of operations?2 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
add/copy downtime to multiple days
At the moment you can add several turbines/assets to a specific downtime but it would be great to also be able to copy or apply a specific planned downtime on multiple days when you have several downtimes with the same time but at different dates. e.g add a planned downtime for 8 hours on monday 08:00 to 16:00 and then be able to copy this and apply also on tuesday or several days.
3 votes -
Order by device number not Power
Have the option to when hovering over a data table the data displayed is in the device number order, not highest value (power, current)
e.g. when looking power produced by each Inverter module for inverter 1 be ordered 1.1, 1.2, 1.3, 1.4 etc not in the order in which they are producing the most power
2 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Make Analyse URL links include the filtering
Make the Analyse links include the filtering. For example if I select the time period to be 2021 I'd like the link shared to also be filtered for 2021
2 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Make the URL links human readable
Make the URL links human readable, so that I can alter them to adjust the outputs, e.g. for example if I wanted to create a link outside of Greenbyte to refer to show something within Greenbyte
2 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Tracker availability from statuses
Today, the tracker availability is only calculated via the deviation of angles. We would need to also have it calculated following (stop) statuses.
1 voteThanks for your feedback, this is a great request. It’s open for voting from other users.
-
PR at meter level based on IEC
In solar, calculate the performance ratio at meter level based on the IEC standard definition.
1 voteThanks for your feedback, this is a great request. It’s open for voting from other users.
-
See Service Contract on Status events in Task
It would bee really great to be able to see what Service Contract different Status events have in a task. Could it be added as a column under Status events?
And also the possibility to change the category if needed directly in the task.2 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 -
Hide "Devices (opt)" during site access at sites with selected WTSR rules
For sites with selected WTSR rules, the option to choose a device during site access should be hidden. Selecting a device should only be possible at the next step by choosing qualified personell.
5 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Improve possibilities for signal data in status export
Recently, the possibility to add a singal data to the status export was released.
A possible way to improve this could the following: not only having the averaged value for the whole status period, but also the possibility to have the measurement of the desired variable at the beginning and end of a stop. This can be quite useful too at some cases:
-like ambient temperature for start-stop of icing stops,
-wind speed and ambient temperature for bat protections stop or even
-light intensity when shadow flicker starts/stop.1 voteThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Clickable header in monitor/analyze to allow moving up and down the device hierarchy
When showing a dashboard in Analyze for a site, I can click on a device on the site and get to the dashboard for that device. For that dashboard I would like to see the "path" I moved, i.e. Portfolio/Site/Device as the header, and I would like to be able to click on e.g. "Site" to get back to the site dashboard.
2 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Qualifications under Personell
Hello, Is it possible to add more qualifications under personell?
If i would like to see following:
GWO
Medical
Hotwork permitAlso if possible to add a date for:
Issued date:
Expire date:Thanks
5 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
"Service this year" signal to count contractual year an not calendar year
The signal "service this year", coming from the "maintenance" toggle on availability contracts, currently considers a calendar year. To make it coherent with the availability contract, it should consider the "contractual year" instead.
3 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Make it possible to upload the Default Power Reduction Mode Allocation List from Vestas to manage curtailments
Vestas turbines with PPC uses Power Derete Internal codes that in Greenbyte is called Curtailment mode signals. These signal indicate a curtailment event that could have direct impact on the contracual availibility depending on how they are categorized. What the signals indicate and how they should be catecorized are listed in the Default Power Reduction Mode Allocation List.
The only way to get the Greenbyte system to take this signals into account in the contractual availibity right now is to create an alert and link that alert to one of your curtailment satuses. It not very optimal (with a growing…
5 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.
-
Make it possible to set heatmap upper and lower limits in Data Studio
When creating a Heatmap widget on an Analyze Dashboard, the user can easily fix the scale of the axis, by specifying the upper and/or lower limit.
However, this functionality doesn't existing when creating a heatmap in the Data Studio. This makes it very difficult to compare different temperature signals, since you cannot fix them to the same scale.
This would be a very useful addition to the Data Studio.
1 voteThanks for your feedback, this is a great request. It’s open for voting from other users.
-
o Service hours/allowed scheduled maintenance cannot be count into the contractual availability.
Each contract is different and a common detail in a service contract like a maximum allowed number of maintenance hours (not taken into account for the unavailability) is not possible in Greenbyte.
Therefore the numbers in the greenbyte report must be recalculated by the number of scheduled maintenance in order to calculate the contractual availability.2 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.
%20during%20site%20access.png){kind=link}
- Don't see your idea?