Greenbyte Ideas
9 results found
-
Administrate Alerts - Show severity
It would be good to have a severity column when you administrating alerts, sometimes you want to add the severity, but you don't know which alert already has one, so you need to go one by one.
4 votes -
Icing detection
There is an existing idea posted in influence regarding the calculation of icing loss by the IEA Task 19 method, but there is no option to comment on it so I created this new topic.
In order to achieve the calculation of icing loss, there should actually be an option to set up an alert that would generate "curtailment" statuses by the IEA Task 19 method.4 votes -
Defining alerts based on status or warnings that have no duration
In some cases, status or warning have no duration, but inform about the beginning or the end of curtailment, for instance.
It would be useful if alerts could be set up by a status/warning code indicating the beginning of some event, and another status/warning code indicating it ended.4 votes -
Plain text notifications for Alerts
For Stops Greenbyte can email notifications in plain text format that are easily processible for other systems (unlike the HTML type messages with nice layout). I would like this to be extended to Alerts, shouldn't be a large job I guess??
4 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Connecting alerts to tasks (acknowledging and commenting)
For monitoring purposes it would be of great benefit to be able to ackonowledge and connect alerts with corresponding tasks. Alerts can come and disappear with a different scheme than statuses if the conditions are met. This would make it possible to have task comments appear at the status codes and the corresponding alerts at the same time. This would increase the overview about situations we want to be aware of.
18 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
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.
12 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.
-
Alerts: Allow users to manually end and/or delete alerts
We often have the case that alerts are not closed properly or are just generated for testing so manual editing is needed which only GB support can do at the moment. As alerts are user generated (by certain rules), it should be possible to edit and delete them.
12 votes
