Skip to content

Greenbyte Ideas

Our approach to product feedback

Here at Power Factors, 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 better products.
We use your feedback to identify the most important features, ideas, pain points, and opportunities so that you can get more value from our products 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 products develop 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 products we possibly can.

What happens to your product feedback

Our product teams meet regularly with the CSMs, to go through new ideas. Once we have verified that an idea isn’t already available in the system, and seems like a good idea, we change the status to Accepting Votes. Then 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 implement an idea, the status will change to Planned or In Development. When it’s done, the status will change to Delivered. 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 conferences and trade shows
    comments 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.
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 Power Factors 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 Power Factors 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

22 results found

  1. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base