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. 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 →
  2. 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 →
  3. Provide the ability to manually make a stop active

    Sometimes it's necessary to set a previously closed stop code back to active in Greenbyte, or the user may have to create an active stop manually. It is not possible to create the active stop today.

    Making a stop active can be done by contacting Greenbyte support, however, this takes time and can be tedious for large sites with multiple stop codes to re-open.

    It would improve the usability of the system and improve the overall status log functionality if it was possible to manually set a stop code as active, and not have to go through GB support each…

    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  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  4. Create a search option for the comments in the status log or status categorization.

    There is a possibility to add a comment to a status event.

    e.g. Status event for unscheduled maintenance might have a comment: "Changing the main gear".

    Over a longer period it would be nice to see how ofter a main gear was exchanged. Filtering on text "Main gear" would give all comments with "main gear".

    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  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  5. Rule-based status categorization

    For some OEMs, the order in which status codes come in can indicate if an event is contractually available or not.

    For example, if code A comes in followed by code B and then code C, it's a maintenance event (OEM liable). But if code A is followed by code D and then Code C, it's an owner-liable event.

    Being able to automate the categorization of status events based on rules would help with the categorization of these kinds of downtime events.

    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

    Accepting Votes  ·  0 comments  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  6. More direct access to editing comments in the Logbook (status categorization)

    In Status categorization, it would save us a lot of time if we could click directly on the Comment field to enter a Comment, instead of going through : click on the 3 dots, click on Edit, click on the Comment section, write comment, save.
    It is also easier to grasp everything at once, when several related events come one after the other.

    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  ·  1 comment  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  7. Display totals in Status logs

    In Status Categorization,
    1- why don't you display the losses together with the downtimes for each line?
    2- then could you display the total of losses and downtimes for what is on display (and thus filtered)?
    It could be very useful so to know the total of losses and downtimes for a specific downtime code by example, or any other filtered downtimes

    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

    Accepting Votes  ·  0 comments  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  8. Make it possible to sort columns in Status Categorization

    I want to be able to arrange the downtimes by duration, WTG, start time, end time, category, code, comment, etc.

    30 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  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  9. Options for Mass Edit in Status Log and Status Categorisation

    The Mass Edit function on the Status Log and Status Categorisation page is quite limited. I would like to see the below mass edit functions to be built as well. Otherwise you must go one by one to do any of these tasks.

    Below is a list of all requests for Mass Edit options:

    Delete
    Link Task
    Set end time
    Compensate
    Split Statuses

    19 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  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  10. Status Categorization: Assign task from drop down (same as category)

    Task asignment is somehow impractical. It would be very useful to be able to asign a Task from the Status Categorization window - same as for Contract Category.

    10 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  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  11. Status Categorization miscelaneous filtering option

    Detailed description
    A few suggestions related to Status Categorization:

    1 - Be able to filter out Status Codes from being displayed. I may not want to see irrelevant status (untwisting) or too frequent status (curtailment) Same as filtering out status with time < xx 1 Add a Task combo to easily apply a Task to a Status Code (same as with Contract Category)

    2 - Bulk Assingment. Add a checkbox next to Status Code so you can select several Status and apply the same configuration at once (Contract Category - Comment)

    3 - When Expanding Status Codes - add a…

    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  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  12. Status categorization / Status log: improve grouping / splitting meachnism

    (1) Ignore warnings in the grouping/splitting meachnism. The most issues we have right now with grouping/splitting are related to warnings - as a stop can not be split if there is a warning in the period.

    (2) Auto-split status groups when there is a change in the availablity category (as this is the normal use case for splitting - e.g. if the turbine has an error (unavailable) after a planned grid shut down or maintenance (available).

    (3) Auto-split in certain special cases. E.g. Nordex 920 (icing status) change to 921 (MET Ice detection alarm finished) - WT remains stopped and…

    11 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  ·  Statuses  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base