Skip to content
Influence

Greenbyte Ideas

← Power Factors Influence

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.



How can we improve?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

14 results found

  1. Breeze does not have feature which logs out the user when production loss of the wind farm is more that 100 MW compared to potential power.

    The maximum power of wind farm is more that 100 MW in which case it is classified as a major production unit. If this wind farm suddenly loses production over 100 MW we must publish so called UMM (Urgent Marketing Message).
    Our external wind farm operator is monitoring this wind farm and if production loss over 100 MW occurs the operator must inform us. At the same time they need to prevent that inside information of the event does not be available or visible.
    Is it possible to have feature in Breeze so that alarm is given when production loss…

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →

  2. Defining alerts based on events that last less than 10 minutes

    It is currently not possible to set up an alert with an "evaluation period" of less than 10 minutes.
    Consequently, it is not possible to generate curtailment status for events that last less than 10 minutes.
    My suggestion would be to make the definition of an "evaluation period" optional.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →

  3. Boolean operator for alerts

    Currently, alerts cannot handle "OR" conditions or any other boolean operator apart from (N)AND. If for instance I want to know if one of two statusses is active together with another status, I need to create two alerts.
    Current alert setup is "Device1(StatusX AND StatusY) AND Device2(StatusZ)".
    It is not possible to have "Device1(StatusX OR StatusY) AND Device2(StatusZ)" in one alert.
    If would be nice to be able to freely play with boolean operators to get to trigger an alert.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →

  4. Repeating errors via Alerts: ignore sub statuses

    We appreciate the new functionality to add generic repeating errors via alerts with the "stop" and "occurs at least x times" conditions. However, such alerts are currently looking at all stop statuses, i.e. also sub statuses under a certain status group. This leads to the problem that we currently get a lot of alerts if e.g. a turbine is spamming a lot of statuses while being manually stopped during maintenance. Therefore, the alert should only focus on main statuses.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →

  5. Add a "Severity"/"Category" field for alerts

    It would be really helpful to be able to categorize alerts ( "HSE" , "Main Components", "Performance", etc...) or at least be able to label them with a "Severity" level : Critical / Major / Minor etc.

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    Archived  ·  Eliane responded

    We have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.

  6. Alerts: tag, created by, filter options

    we see how the number of alerts we are creating is growing, and we need the interface to provide a better organization and being able to track the status. The following points will help:

    • Add field "alert created by".
    • Add a field "category": ideally with a list of several categories to be defined by the user: curtailment, bat protection, underperformance, noise, etc.
    • Add field "date of creation" and "last modified"
    • Enable filter alerts by: enabled/not enabled, created by, category, curtailment/alert, date of creation/modification, etc.
    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    Archived  ·  Eliane responded

    We have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.

  7. Larm vid ofrivillig reducerad effekt

    Hej
    Vi har missat ett antal gånger att vindkraftverk har börjat att producera med reducerad effekt vid till exempel uppdateringar av styrsystemet och då har det inte blåst när uppdateringen blir gjord utan det börjar blåsa upp lite senare.
    Förslag är att aktuell effekt på verket jämförs med powercurve och när det skiljer för mycket (Som man kan ställa in procentuellt) under en viss tid (Som man också kan ställa in) och beroende på yttertemperatur (Inställbar) då det ju kan vara is som är en naturlig förklaring så får vi larm
    Exempel har vi om ni frågar då t,ex ett…

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →

  8. Alert: enable a paramater for the % of past data that meets the rules before triggering

    Target: to reduce the number of fake alerts.
    Reason: we often have the use case of monitoring several variables that have to be within a certain threshold when during specific status circumstances, but the reaction time is not immediate. It would be extremely helpful to define a kind of condition fulfilment ratio in order to trigger the alert only when the parameters are met for more than 5%/10%/20%/90% of the evaluation period.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    Archived  ·  Eliane responded

    We have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.

  9. Alerts: prolong evaluation period by excluded time

    In the Alerts, there is a possibility to exclude time with certain data from the alert evaluation period. The idea is to add an option to prolong the evaluation period accordingly with the excluded time period. Because now for example, if an alert's evaluation period is set to 7 days, but excluded stop data lasts for 6,9 days of those 7 days, then the alert is in practice calculated on an actual evaluation period of only 0,1 days, and this leads to unnecessary alerts.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    Archived  ·  Eliane responded

    We have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.

  10. Add shadow calendar to specific turbines

    To be able to create alerts when a shadow stop is not corresponding with the shadow calendar

    8 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    Archived  ·  Eliane responded

    Thanks for your feedback, Casper. 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.

  11. Alerts: exclude from evaluation period such time periods when the wind speed is lower than a certain value

    Add an option in the alert settings to define the alert's evaluation period so that it excludes from calculation such time periods when a certain parameter is lower/higher than a certain limit value (for example exclude such time periods when the wind is lower than a certain value).

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    Archived  ·  Eliane responded

    We have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.

  12. Timed alerts

    Please can you set up the timed alerts to be able to specify different times on different days. For example :

    Monday to Thursday I would like alerts being sent between 21:00 – 07:00 overnight.
    Friday 19:00 – 07:00
    Saturday / Sunday 16:00 – 08:00

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    Archived  ·  Erika Brandes responded

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

  13. Group Devices between sites for Alerts

    Allow Devices/Inverters/Turbines to be grouped together within and between Sites.

    This is will simplify how setting up multiple Alerts to individual devices between sites for large portfolio.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    Archived  ·  Eliane responded

    We have great new features lined up that we can’t wait to share with you. Unfortunately this request is not part of the roadmap.

  14. Collaborative Library of alarms to be set up

    It would be very useful to have a collaborative library of alarms set up by Breeze users - so we can "copy" the alarms other users are using.

    7 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Alerts  ·  Admin →
  • Don't see your idea?

Greenbyte Ideas

Categories

Feedback and Knowledge Base

(thinking…)