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. Contractual maintenance hours

    Contractual agreements may define a fixed number of hours of scheduled maintenance as Available. It seems this is not supported by Greenbyte yet. Please add.

    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

    0 comments  ·  Availability contracts  ·  Flag idea as inappropriate…  ·  Admin →
  2. Proper calculation of time-base availability when data is missing

    As off today, if 10-minutes data are missing for some reason (scada issue for example), then this period is just not taken into account for contractual availability calculation and for system availability calculation. This is an issue because in many case, when accessing the turbines, the maintenance technicians will shut down the communication to prevent remote restart of the turbine, and this loss of communication will also trigger wrong availability calculation.
    We expect time-based availability to be based on the period duration, not the 10-min data being there or not, and during data losses, the turbine should be considered available.…

    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  ·  0 comments  ·  Availability contracts  ·  Flag idea as inappropriate…  ·  Admin →
  3. Select Availability Category Within Task

    When creating a task there is an option that may be selected that is labeled "Affects Downtime". If this option is enabled, the availability contract categories should appear and one should be assigned to the task.

    This would be useful for sites that are utilizing tasks to coordinate site work.

    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  ·  Availability contracts  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add additional equations for calculating Energetic Availability based on specific OEM contracts

    It would be extremely useful to be able to create custom availability contracts that use different methods for calculating lost production and energetic availability.

    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  ·  1 comment  ·  Availability contracts  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base