Greenbyte Ideas
Our approach to product feedback
The benefits of giving us your product feedback
What happens to your product feedback
How we choose what to implement
- Customer feedback - there are many ways we listen for your feedback:formal customer interviews and other research activitiesevents like conferences and trade showscomments 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.
Custom applications
216 results found
-
Display active status/alerts in the Remote Operations Portfolio Overview
It would be very useful if you could see the turbine status when hovering over the alert symbols on the Remote Operations > Portfolio Overview page. E.g lack of wind, turbine fault status, site accesses etc
6 votes -
Be able to select past contractual years
"Contractual year" exists, this is great. I would also like to selected "past" contractual years.
4 votes -
30 minute resolution data, this would match how revenue meter data is supplied
I want to see 30 minute resolution data, this would match how revenue meter data is supplied and could be compared directly against SCADA for anomalies
4 votesIn the meantime, you can plot SCADA data on 15-min resolution and compare to 30-min meter data. Alternatively, you can aggregate meter data to 1-hour and compare to 1-hr aggregations of SCADA data.
-
Make it possible to use the Manufacturer Potential Power signal in the potential power cascade
In some cases (e.g. grid curtailment where the site has an export constraint) the existing potential power methods in Greenbyte provided significantly over-estimated figures for Lost Production.
The manufacturer potential power signal often provides accurate potential power readings during periods of curtailment. If it were possible to make this part of the potential power cascade, users would be able to get more accurate lost production to curtailment figures.
5 votes -
Make it easier to keep the status event start end end e-mails apart
E-mail notifications are in plain text at the start and the end of a status event.
The header is the same in both cases, which is not comfortable.The first word of the header of the second email, when the status is resolved, should be "RESOLVED" or something similar.
In that way one would easily differentiate between an initial status event an the end of this event.3 votes -
Show more than 20 site access logs on screen
Less than half the screen is used on the site access page, so it would make sense to utilise the wasted space and reduce the number of pages people have to click through. The side bar is useful, however viewing a site access via this changes the filters on the main page which negates any actual benefit.
9 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
status categorization direct form the task> view page
It would be nice if the status could be categorized from the task > view page.
For now you create a task, add some status codes and than you have to go back to the status categorization, search for the status and than categorize it.
that seems to me a unnecessary long way to do it.4 votes -
Monitoring performance of a wind farm with a time span that currently do not exist
I wish to create a dashboard which will contain visuals showing the data of the following time span:
"Last civil month / year" (different from last 30 days / last 365 days) : if today is August 20th, "last civil month" is from July 1st to July 31st
"Contractual year to date" : year to date data starting from the first day of the contractual year (e.g February 1st for a contractual year going from February 1st Y to January 31st Y+1)
3 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
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.
7 votes -
Make it possible to view Alerts in Data Studio
Users will often have to go into data studio to investigate the underlying signals behind an alert. However, it is not possible to see Alerts on the status overview the same way you can see stops, warnings, communications outages, or curtailment. This would make it much easier to analyze the Alert.
11 votes -
Alert schemes to include Days of the Week scheduling
Alert Schemes to include Days of the Week.
Noise Curtailment schedule need to also respect working hours. I.e the Turbines need to be curtailed Monday-Friday evening, Saturday Afternoon and Sunday full day.
This is Especially important for UK wind farms that have to protect "Amenity". (a special kind of noise curtailment for sensitive sites near neighborhoods in rural areas) Where infringement of "Amenity" must be reported on and followed up.12 votes -
Use metadata for alert conditions
I would like to use a metadata field (site and device) as an alert condition. In this case the capacity meta data field.
Anyone who has more user cases where a similar scenario applies - please add your comments!
At present, alerts can only be configured based on absolute values (e.g. MW) and not relative values (%). This means for every new site added certain alerts (e.g. grid curtailment) need to be duplicated and adjusted for the site specific absolute values. It would be easier if alert rules could be defined based on relative values and made applicable to all…
5 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Make 'hours per category' (component) table available in Taxonomy
For availability contracts Greenbyte provides a widget called 'hours per category' in table format. This makes it very easy to copy the data into excel.
Taxonomy does not have this functionality though! We can only look at downtime per component as a pie chart.
Being able to show it in a table format and quickly copy/paste this data over to excel for further analysis and reporting (e.g. GADS reporting).
4 votes -
Add 'Year to date' and 'all' time selector
I feel like existing Data Studio pre-default time selectors are not enough to cover all most typical situations. I end up selecting a 'year to date' custom period very often, so it would be very good to have that in place.
Also, for verification purposes it would be nice to have an 'all time' time selector, which will take all data available since TimestampStart of the device to date.8 votes -
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.…8 votes -
Revenue budget
Such as we have Revenue figures in the system, they would be more meaningful if we also had the Revenue budget (such as the energy budget), which would be simply applying the same fix price per MWh to the energy budget already available in the platform
3 votes -
Power Curve Analyzyer- pls change colours
Power Curves
Please use colours that are more distinguished in difference. As it is now it is very hard to see difference between learned PC in light blue and Best Fit in slightly darker blue.
Neither curves nor scatter plot gets clear enough to actually see any difference! See attached picture.
Thanks & regards :-)7 votes -
In specific cases warning triggers losses calculation and impact availability. We need an option to turn OFF this logic.
Currently if there is a warning status code and the turbine shows no production during wind high enough to be operational, the turbine is automaticaly seen as faulty and availability is set to 0 for that period. The warnings status code will get losses calculated and attached.
We'd like an option to turn OFF this feature. We consider that, by definition, a warning status code should never trigger any losses calculation and never have any impact on availability figures.
6 votes -
Audit trail of comments in the comments section in portfolio page
Currently, we can only see one comment against the stop and it is often the latest update on the stop. To see a history of work undertaken to bring the turbine back online, it would be useful to have an audit trail of comments that can be saved somewhere in the back end. That basically means that when we use APIs to export the comments in status logs it only pulls the latest comment- like it does now but there should still be a provision to view the history of comments including user, date and time elsewhere in GEC.
5 votes -
Make custom section titles visible on the report outline page
When creating a report that contains several custom sections, it's difficult to know which section is which since the section titles don't update.
If I want to see what my custom section is, I need to reload the report and find it again. This is time consuming, especially for reports which take a long time to load.
If the main report outline page updated with section titles, just like the table of contents does, this would make reporting much more efficient.
10 votes
- Don't see your idea?