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

13 results found

  1. Automatic updates of technicians GWO records

    Create an API link between the personnel page and WINDA to automatically update technicians GWO records/qualifications using their WINDA ID.

    12 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  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  2. description api key

    It would be good to be able to add descriptions to API keys so you can document the purpose of the API key.

    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  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  3. Lost production of statuses in the API should follow the selected period

    For the Status endpoint, statuses overlapping over start date and/or end date should only take that part of the Lost production value that corresponds to the selected time interval.

    Otherwise the Lost production does not match what you can see in the platform, e g in Data Studio, for the same time interval.

    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  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  4. Ability to export only overdue site access via the API

    We can export the site access via the API but it would be great if we could filter the overdue site access in the export.

    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  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  5. Include other data signals with the Status API

    When using export data, it is possible to get other datasignals during the time of a status, for example the exact windspeed, nacelle direction etc. at the moment of a status.

    This is not yet possible with API using the Status endpoint. Could this be made possible?

    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

    1 comment  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  6. Status changes trazability via API

    when it comes to refreshing a status database via API, it is quite challenging to update manual changes in the status (i.e, category changes, group structure change, manually added stops that change the group structure,,,)

    Would be great to have in the API some way to trace those changes. For example, "last modified" point in the API would already help. It would also be nice to know if the event was added manually, see image.

    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

    1 comment  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  7. Allow API permissions that limit the period of data that can be accessed

    I would like to share data, but just for a set time period, for example from Jan-2020 to Dec-2020. As such I propose having a start-date, end-date and "all time" period option when creating (or editing) the API keys

    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  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  8. Export high resolution data at wind farm level

    We would like to be able to export high resolution data at wind farm level instead of at wind turbine level.

    6 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  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Accepting Votes  ·  Giorgio responded

    Thanks for your feedback, this is a great request. It’s open for voting from other users.

  9. API Endpoint - 'Try it out' gives 401

    The Greenbyte Developer Portal shows the endpoints, with a TRY IT OUT button on the right hand side. Could you show some (fake) data there?

    Whenever I click this button, I always get an empty body with 401 status.

    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

    Accepting Votes  ·  1 comment  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  10. Make all device power curves available from the API

    Currently only the default power curves for each device are available via the API. It would be good to be able to extract all of the power curves assigned to a device

    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  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Accepting Votes  ·  Eliane responded

    Thanks for your feedback, this is a great request. It’s open for voting from other users.

  11. Add turbine "title" in the data.json

    In order to obtain "turbine title" in addition to "turbine Id" directly from same json please add the "turbine title" in the data.json.
    For instance I am gathering data with data request and always need to make a second request to have the "turbine title" which is not present in data.json and more useful than turbine ID for final utilisation.

    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

    Accepting Votes  ·  0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  12. Make all data readable through the API

    I'd like to be able to access all data visible in GEC through the API.

    For example the "potential power order" and "reference devices" from the Admin Turbine view, and data signal mappings from the Comms view.

    14 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

    Accepting Votes  ·  1 comment  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

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

  13. API write endpoints for Metadata fields

    We would like to be able to use the API for writing values to metadata fields.

    21 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

    Accepting Votes  ·  1 comment  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?

Greenbyte Ideas

Categories

Feedback and Knowledge Base

(thinking…)