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
28 results found
-
Use calculated variables in Data Studio
Define calculated variables for analysis in the Data Studio - such as:
"wind park average value" -
"average of selected turbines". Note that the "wind park average" option is already available in the "alarms" section.17 votes -
Add turbine reference anemometer for Lost Production Calculation during communication issue
On windfarms of only two turbines, it is impossible to calculate Lost Production to Downtime in some cases.
For example, during a communication issue on one turbine, the other turbine works as reference turbine but the calculation is not performed in presence of any curtailment of the reference turbine.
Add a reference anemometer would allow the possibility to use either Learned or Default PC on the turbine which have no communication, using wind speed signal of the reference turbine.8 votes -
Electrical Losses/ Electrical Performance Index
Can you please add a calculated Index to the Data Studio to calculate the percentage of loss energy from the internal cable network on the site. It needs to be (Meter Export Energy divided by Virtual Production) – 1 and presented as a percentage? It would fit in the PERFORMANCE group with Performance Index.
8 votes -
calculate icing loss
Calculation of the realised production loss (MWh) due to icing, per turbine. Calculation with the IEA standard methodology: https://community.ieawind.org/task19/t19icelossmethod
7 votes -
Allow Taxonomy to do analytics with the data
Taxonomy is an add-on that give you data from the WTG to the RDS-PP category. There would be a lot of value allowing the user to do the navigation the other way around as well. This is from the RDSPP category down to the turbine.
6 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Make it possible to use the Manufacturer Potential Power signal in the potential power cascade
In some cases (e.g. grid curtailment where the site has an export constraint) the existing potential power methods in Greenbyte provided significantly over-estimated figures for Lost Production.
The manufacturer potential power signal often provides accurate potential power readings during periods of curtailment. If it were possible to make this part of the potential power cascade, users would be able to get more accurate lost production to curtailment figures.
6 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 -
Data availability for devices
The Data Availability KPI is only available for power generating units. It should be available as a variable in Data Studio / Dashboards / Reports and also available in the alarm rules.
6 votes -
Lost production : manual recording possibility
In case of grid loss -for example- - the lost production of a status log can be calculated with the Estimated Potential Power. But this considers only a short period of time (mean between one hour before and one hour after the shutdown). When the shutdown is for a long time period (several hours or days) - it would be useful that the users could add a lost production manually.
6 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 -
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 -
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 -
Middle voltage loss calculation (Energy Export vs. Energy Meter) in MWh or %
When metering systems are connected to the Scada one standardized tech. KPI is to understand the middle voltage losses between WTGs and official energy metering.
Ideally such should be calculated on kWh/MWh basis as simple delta between Sum of Energy Export (WTGs) and official Metering. Additionally the % deviation should be calculated, too.Further benefits:
As Greenbyte introduced the Loss Waterfall also this calculation would benefit from the above as additional losses (depending the size of the wind farm typically 0.5 - 2.x %) could be highlighted. Additional precision for the Loss Waterfall Diagram!3 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.
-
Power bars and maximum installed effect or maximum effect according to power curve
It would be nice if the app and the web page could use the maximum power curve value instead of installed capacity in the power bars.
This would improve our visual knowledge if the machine is running accordingly to the current PC.
3 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Clarity to input signals for calculated values.
In Data Studio, can you show the exact background signal that is used to feed into the calculated value as you hover over the calculated values such as Production Based Availability.
2 votes -
Methods for potential powers
Methods currently implemented for the calculation of potential powers are not state-of-the-art.
It would be great if more methods were implemented, like the power-to-power method that Greenbyte wrote a white paper about a couple of years ago, methods involving Machine Learning, methods using learnt power curves computed based on wind speeds from a meteorological model, learnt power curves by wind direction sector with biased nacelle wind speeds measured during stops being rebuilt from data of reference turbines, etc.2 votes -
I would like to see the Max.Power ever produced (wind turbine, park, portfolio level)
Hi all,
in order to reflect the maximum power ever produced a new KPI is required. I tried to use the Max.Power signal in GB, but this is not the correct tag to display the max. power output (for a wind turbine, park or portfolio).
THX2 votes -
Compare curtailment loss % for different periods
I would like to ask you to make a feature to calculate and make visual tools to know "time-based curtailment loss".
As the background of this request, currently, we are getting many grid curtailments and want to compare the degree of them in different sites.
We can see the amount of production-based loss on Greenbyte, however, we can't see the time-based losses so it's difficult to do a comparison between different sites.So we request you to set up features like the below:
- calculate time-based curtailment loss(%), day by day, week to week, month to month, year to year.…2 votes
- Don't see your idea?