Ideas

Our approach to product feedback

Here at Greenbyte, we take product feedback extremely seriously. We believe that listening to our customers, team members, and prospects - by taking their ideas on board - is a sure-fire way to build a better product.
We use your feedback to identify the most important features, ideas, pain points, and opportunities so that you can get more value from our product as efficiently as possible.


The benefits of giving us your product feedback

If you take the time to submit your product feedback to us, it means that you have a direct say in how our product develops over time. It means that your ideas are valued and listened to, rather than filed away and ignored.
Ultimately, it allows us to work with you to build the best product we possibly can.

What happens to your product feedback

Our product teams meet regularly to go through new requests. Once we have verified that a request isn’t already available in the system, we change the status to Accepting votes so that more people can vote, prioritize, and give us information. This allows us to gauge demand, gather use cases, and establish impact & value.

If we decide to build a request the status will change to Planned or Started. When it’s done, the status will change to Released. Anyone who has submitted or voted on a specific request will be notified when the status of the request is updated. We will always provide an explanation as to the nature of the status update.

Unfortunately, not all requests are in line with our vision and strategy, so sometimes we reject them. When this happens, the status will be changed to Archived and we’ll add a note to let you know that it won’t be delivered.


How we choose what to implement

When we plan a release, we use many factors to help decide which suggestions to implement, including:

  • Customer feedback - there are many ways we listen for your feedback:
    formal customer interviews and other research activities
    events like Greenbyte Forum conferences and trade shows
    comments and votes on issues in Greenbyte 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 product.
If you reach out directly to our support or customer success teams, they'll be able to look up the ideas for you, but they won't have any additional information or provide an estimate for when your item will be reviewed.


Custom applications

Sometimes you need functionality that is specific to your needs and not necessarily useful for other customers or in line with Greenbyte’s strategic goals. These special requests are addressed through custom applications, which can be developed by you, using the Greenbyte API, by third-party partners, or by Greenbyte for an additional fee. If you are interested in having a custom application built, contact your CSM.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Calculate power curves including air density correction

    We would like to see a calculation of power curves including air density correction - based on measured air temperature for example.

    38 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  2 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  3. Performance Index to exclude curtailment events

    Performance Index is calculated during periods where the System Availability is 100%.
    This period of time include curtailment or when Maximum Export Capacity (refereed in Breeze as "Utility set point") is below the total wind farm power output potential.
    Therefore, a "Custom Key Performance Index" feature to create a Performance Index to considering these externalizes would solve this oversight.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  1 comment  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  1 comment  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  1 comment  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  13. Make it possible to use MERRA-2 wind data in Greenbyte

    It could be used to perform resource-adjusted budget calculations.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Accepting Votes  ·  1 comment  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  15. "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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Calculations and metrics  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base