Greenbyte Ideas
28 results found
-
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 -
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 -
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 -
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.
-
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.
-
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.
-
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 -
"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.
-
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.
-
Overlapping curtailment schemes: lost production calculations
Calculate lost productions per category (commercial, grid, owner, etc) taking into account simultaneous curtailment signals and setpoints. A dynamic calculation would provide more accurate results.
2 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
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?
1 voteThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Sun Elevation and Azimuth Data Channels based on Site Location Metadata
Add data channels in Bright for sun elevation and sun azimuth based on site coordinates that are set in metadata, and allow these channels to be queried through the API.
These data channels could be used to correlate the actual irradiance to the sun's position, or performance metrics against the sun's position to help identify if areas of underperformance are due to a specific location of the sun.
1 voteThanks 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.
-
Loss of Production Site Grid Export Limit
Some wind farms have grid export limits that are less than the installed capacity of the wind farm. When the farm output is at its export capacity, for any turbines that are stopped I would like the loss of production to be zero as the wind farm is not actually losing this potential production.
2 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
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 voteThanks 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
