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. 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 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 →
  2. 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.

    0 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 →
  3. PR at meter level based on IEC

    In solar, calculate the performance ratio at meter level based on the IEC standard definition.

    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 →
  4. See Service Contract on Status events in Task

    It would bee really great to be able to see what Service Contract different Status events have in a task. Could it be added as a column under Status events?
    And also the possibility to change the category if needed directly in the task.

    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  ·  Plan  ·  Flag idea as inappropriate…  ·  Admin →
  5. Production losses are calculated towards to Warning events

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

    2. 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
    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 →
  6. 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)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  7. Hide "Devices (opt)" during site access at sites with selected WTSR rules

    For sites with selected WTSR rules, the option to choose a device during site access should be hidden. Selecting a device should only be possible at the next step by choosing qualified personell.

    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

    0 comments  ·  Plan  ·  Flag idea as inappropriate…  ·  Admin →
  8. Single Sign On and external authentication

    We utilise Microsoft SSO for our IDAM across all our SaaS platforms and Breeze should allow sign on with OAUTH.

    This is now a security requirement for all our platforms, and considering Breeze taps into to Operational systems, its a key target for these requirements.

    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  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  9. Improve possibilities for signal data in status export

    Recently, the possibility to add a singal data to the status export was released.
    A possible way to improve this could the following: not only having the averaged value for the whole status period, but also the possibility to have the measurement of the desired variable at the beginning and end of a stop. This can be quite useful too at some cases:
    -like ambient temperature for start-stop of icing stops,
    -wind speed and ambient temperature for bat protections stop or even
    -light intensity when shadow flicker starts/stop.

    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  ·  Data export  ·  Flag idea as inappropriate…  ·  Admin →
  10. Export status file by stops only

    We would like to export the status file by only a certain type of status such as stops. Currently we can export the status file only but it includes all status types.

    5 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  ·  Data export  ·  Flag idea as inappropriate…  ·  Admin →
  11. Clickable header in monitor/analyze to allow moving up and down the device hierarchy

    When showing a dashboard in Analyze for a site, I can click on a device on the site and get to the dashboard for that device. For that dashboard I would like to see the "path" I moved, i.e. Portfolio/Site/Device as the header, and I would like to be able to click on e.g. "Site" to get back to the site dashboard.

    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  ·  Dashboards and widgets  ·  Flag idea as inappropriate…  ·  Admin →
  12. Scheduled Turbine Control / Shutdown Feature

    For bird regulations it´s more and more necessary to shutdown turbines for certain days and periods over a week. Especially for issues with cranes or red kites we would like to have a "scheduled control feature" or "scheduled shutdown calendar" in which you can set times and turbines for being ramped down & up in advance (e.g. monday morning for the whole week).The actual "turbine shutdown feature" only allow instantaneous ramp down & up of a wind turbine but no advanced scheduled programming. An instantaneous shutdown feature doesn´t give us the efficiency and flexibility to handle a big portfolio with…

    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  ·  Remote Operations  ·  Flag idea as inappropriate…  ·  Admin →
  13. Qualifications under Personell

    Hello, Is it possible to add more qualifications under personell?
    If i would like to see following:
    GWO
    Medical
    Hotwork permit

    Also if possible to add a date for:

    Issued date:
    Expire date:

    Thanks

    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  14. "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.

    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. Make it possible to upload the Default Power Reduction Mode Allocation List from Vestas to manage curtailments

    Vestas turbines with PPC uses Power Derete Internal codes that in Greenbyte is called Curtailment mode signals. These signal indicate a curtailment event that could have direct impact on the contracual availibility depending on how they are categorized. What the signals indicate and how they should be catecorized are listed in the Default Power Reduction Mode Allocation List.

    The only way to get the Greenbyte system to take this signals into account in the contractual availibity right now is to create an alert and link that alert to one of your curtailment satuses. It not very optimal (with a growing…

    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  ·  Availability contracts  ·  Flag idea as inappropriate…  ·  Admin →
  16. Make it possible to generate a report of Predict alerts for one or multiple turbines

    In order to act upon a Predict alert, it is often necessary for the user to share the finding with an external stakeholder (e.g. the OEM). However, it is difficult to get Predict alerts out of the system - most users need to resort to taking screenshots of individual graphs and re-assembling them in an email or word document.

    Having the ability to generate a .pdf report of Predict alerts for one or multiple turbines would make it much easier to share Predict findings; a critical step in getting issues resolved.

    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

    0 comments  ·  Predict  ·  Flag idea as inappropriate…  ·  Admin →
  17. Display availability in status log

    It would be great if, in the status log (the one in data studio), one would be able to see how much one stop/status affects the availability for that turbine during the given month or period.

    This would significantly facilitate the process of comparing the data in Greenbyte to that of the service provider.

    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  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  18. Predict - Be able to create statistics of Predict alerts

    Currently, Predict provides a list of alerts to be managed. However, there is a lack of functionality to create statistics around Predict. E.g. repetitions per turbine/component, timelines, summaries (Dirty Dozen). Having the ability to create statistics would be great.

    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  ·  Predict  ·  Flag idea as inappropriate…  ·  Admin →
  19. Coustum Delay for Notifications

    I need the option to coustmise the delay in the notefication scheme.
    (1-24h)
    Wait for [1,2,...,8,...,24] before sending a notification

    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  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  20. Make it possible to manually edit the end time of a status event

    There are instances when the end time of a status event in Greenbyte is not correct.

    For example, if a turbine is stopped and loses communication with Greenbyte. The end timestamp of the stop event will often appear in Greenbyte as the same timestamp that the communication outage was fixed. In reality, the stop event code may have occurred earlier than that (Greenbyte just didn't know, since communications weren't active).

    The only fix today is for the user to contact Greenbyte support and request the change be made by them. This is inefficient and can be particularly cumbersome when working…

    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  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 10 11
  • Don't see your idea?

Feedback and Knowledge Base