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
21 results found
-
We can't show the amount of revenue originating from compensated lost production due to curtailments
Create an extra revenue signal which shows only the revenue coming from compensated lost production.
4 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.
-
Cascading potential power - Capacity Factor
Add another potential power method based on historical Capacity Factor. With the aim to estimate producibility in case of downtimes, it could be useful to include the historical avrg of WTG capacity factor to be multiplied by WTG nomical power.
1 voteGreat idea! It is not one of our priorities right now, but we think we have a way where you would get the same results as you expect, so please stay in touch with your CSM.
-
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.
-
Show Equivalent Full Load Hours in "hours"
Equivalent Full Load Hours is sometimes shown in "hours" in the platform, but sometimes is shown in "seconds" (like Share->Export Data, or Reports->Time series table (widget)).
This indicator is useful in hours, can this be resolved?
0 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.
-
Calculate Energy Theoretical from different sources of Potential Power
Today, Energy Theoretical is only calculated from the first source of Potential Power in the assigned Potential Power Order. It would be good to have, such as we have different Potential Power signals, to get the Energy Theoretical from all of these sources.
1 voteThis is a duplicate request.
-
New variable: active status during 10-min bin
We would need a calculated variable for all devices with the main status code active for each 10-min data bin (if any).
This would be very helpful for deeper checks and analyses being able to treat specific 10-min data points depending on the status that was active (i.e bat shutdown related status, shadow flicker, power curtailment, etc etc)
A specific example: we want to check if the turbine was stopping too much in reason "bat protection". For this, we need to filter out any other stops that are not related to bat protection.
Another specific sample: we need to prove…
2 votesThis is currently not possible to achieve, but if I read your request correctly, I believe a good way around to achieve this would be to create 2 widgets on the Analyze section:
1. Dirty Dozen, filtering by Curtailment statuses only.
2. Status Overview, filtering by Curtailment statuses only.Please contact your CSM in case of doubts.
-
Add the counter data for particle count as it already exists for Energy export
The currently particle counts provided in the energy cloud are 10 min values. By using the option cumulate values, it is possible to obtain the cumulative sum. However, if a sensor is reset the comulative values will show a negative values. As the comulative can be optained from the turbine system, I would like to add this counter data in the energy cloud as an additional signal to be used in dashboards and widgets
2 votesIf the particle count is available as a counter it should be possible for our installations team to install the counter data. Please reach out to your CSM to check how the installation has been done.
-
Generation Forecast
For power plants where weather forecast data is currently integrated (e.g. windspeeds forecast), it would be good if Breeze can show a calculation of generation forecast that already considers any WTGs down in the forecasted period, be it planned downtime like maintenance, or even unplanned downtimes due to mechanical/technical issues.
Example, a windfarm has 20 WTGs operating today but there will be planned downtimes tomorrow affecting 4 WTGs due to maintenance.
Then, the plant's day-ahead generation forecast (using a 3rd party's weather forecast data in m/s) should be adjusted accordingly based on the expected number of WTG's operating (in this…
1 votePlease reach out to your customer success manager. What you want to achieve might be possible with our add-ons and parnerships.
-
Waste Management
I suggest the inclusion of a widget for the tracking of each year's waste production per category for wind farms. The annual quantities could be plotted on a graph
2 votesThanks for your feedback, Nikos. This is an interesting idea, but since it’s not in line with our current strategy, I’m going to archive it for consideration if our long-term plans change.
-
Performance Ratio and Solar Conversion Ratio
We would like to have in Breeze other ratios than the PR that is already available:
Performance Ratio PR (alternative calculation):
PRsolarsite = Total Power AC / (Irradiation * Area * Yield)PR_Inverter = Total Inverter Power AC / (Irradiation * Area * Yield)
Where the yields depends on the type of modules that is installed.
Solar Conversion Ratio SCR:
SCRsolarsite = Total Power AC / (Irradiation * Area)SCR_Inverter = Total Inverter Power AC / (Irradiation * Area)
1 voteWe have great new features lined up for this year that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Bright : Define an irradiation cut-in PV module daily temperature calculation.
For now the daily average of module temperature is calculated upon the 24h of the day - which is not relevant because modules are not producing at night and night temperatures are lower. Therefore - the daily temperature calculated by Bright is too low. As we are using modules temperature to correct our estimated PR - we would like to apply the same calculation conditions (Irradiation cut-in - availability threshold etc.) under which Bright calculates the daily PR.
1 voteWe have great new features lined up for this year that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Weight the plant availability by the capacity of each inverter
If inverters with different capacities are used on a plant - the time-based availability should be weighted by the capacity of the inverter that is not running.
1 voteWe have great new features lined up for this year that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Bright - Peak Hour Device Production
It would be extremely useful for both reporting and alarm setting - if a user were able to calculate peak hourly production during a period of interest.
0 votesWe have great new features lined up for this year that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Electrical losses between inverters and grid meter
We would like to be able in reports to display a table that summarizes active power losses that comes from interconnection cables - per sites and per month.
1 voteWe have great new features lined up for this year that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Inverters production normalized (in kWh/kWp)
Inverters production normalized (in kWh/kWp)
0 votesWe have great new features lined up for this year that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Lost Production to Other/Wind Speed
Deviation from budget is explained by Wind Speed - Performance - Downtime - Data Availability and Unexplained. Breeze currently calculates Performance and Downtime - it would be very helpful for it to be able to show the remaining deviation (which can be labelled as Lost Production to Wind Speed and/or Lost Production to Other). Deviation due to Wind Speed can be calculated in a number of ways - some of which are very simple e.g. difference between budget and theoretical. On a monthly and yearly level as a minimum.
3 votesInstead of this solution, we are building the capability to break down losses into various categories like shading, soiling, electrical losses, tracker issues, combiner box issues, turbine component failures, etc.
We believe that this information is more relevant and actionable, so we have moved away from focusing on breaking down losses in relation to forecasted figures.
However, we are in the process of building a feature which provides the deviation from the forecasted figures; for example deviation between actual and forecasted irradiation.
-
Manual anemometer wind speed correction function per wind turbine
Allow to manually adjust a linear (y=ax+b) anemometer correction function per wind turbine (would be nice to have also per 30o direction sector) . So the wind speed you see in all the data is the adjusted one.
1 voteWe have great new features lined up for this year that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Custom Calculations
Can you add a tool to allow users to do a custom calculation using data already available in Breeze and be able to save them for future use or display in a dashboard widget?
17 votesWe have great new features lined up for this year that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
-
Set up a "liability distribution" graph
Show on the same graph - for each kind of failure - the failure rate and the related total downtime (some failures happen very often - but in the end - do not generate much downtime)
2 votesWe have great new features lined up for this year that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.
I would suggest using the Dirty Dozen widget to try and achieve this.
-
Lost production per status code
We would like to see the breakdown of lost production per alarm code.
7 votesIt sounds like this would be possible using the Dirty Dozen widget available in Data Studio or on Analyze dashboards. If this would not solve your need could you please clarify the request.
- Don't see your idea?