01 Nov 2017
This information aims to bring you up to date with the latest changes that are now available to users in Sentinel and Sentinel On Demand
The perceived value of Sentinel and Sentinel – On Demand is enhanced in several ways:
- New RTC & Alert handling
- New noise event alert
- Traffic Light indicators – Hardware or Windows Phone.
- Alerts based on two locations
- Battery Level Excel output
- VMT Support
- Location Sharing of NMT
- Stakeholder App updated for vibration
- New Site Setup and Overview
- Stakeholder web Configuration
New Real Time Control (RTC) Application in Sentinel
Between Sep 2016 and Jan 2017 all the other UI components were updated, with a new look and feel. Along with this, the RTC (Real Time Control) client has now been renewed to follow the look and feel of the stakeholder web and keep a more consistent branding.
Along with this change in look and feel, it was necessary to introduce a transparent change as Microsoft are no longer supporting the older mapping API used in the Legacy RTC client. This change has also introduced pan and zoom capabilities on the map.
Figure 1: New RTC
It is also now possible for the user to setup and use a bitmap image instead of BING maps. Previously this was a services only feature.
Initially the New RTC will be enabled in parallel to the legacy RTC so that users can slowly move towards the new implementation.
New Alert handling
With the legacy RTC client, the alert handling required the user to type in the reason for the alert, or select from a drop-down the comment to be applied. This proved to be time consuming for the users, and when two users are categorizing a noise event, chances are that they will use a different word or phrase to describe the same event.
The New RTC client, changes this work flow, by allowing the use of buttons with a standard set (which can be defined per tenant/site/location) of alert categories. Each time a standard category is chosen, the chosen category also allows the event to be included or disregarded based on what the noise is. For example, if a user chooses “People Speaking”, then the category Community Noise could be set up to automatically disregard the noise, with no further action for the Users.
Figure 2: Category Manager
These changes which have been introduced are expected to speed up the process of alert handling, by making a much more efficient workflow.
Figure 3: Alert handling interface
This change will also be complimentary to Machine Learning which is currently in development, allowing consistent approach to categorising the Noise events.
A final Change to the RTC client is a new more efficient method to listen to the audio.
Previously, to listen to the audio, a new browser window was opened up to listen to the audio. This is no longer the case. Now, the audio is visible in the browser with the alert.
Figure 4: Audio handling with alerts
It is also now a standard feature that any audio clip can be disabled from the stakeholder web, as required.
New Alert rules
This rule allows the user to set a trigger from the noise event to capture audio with a buffer of a defined number of seconds from before the noise event. The Audio can be set to be created on exceedance or on warning, and at the level or above the defined level of exceedance/warning. When these requirements are met, then the audio file is generated from the defined number of seconds before the event.
Figure 5: Audio Start definition
This is set-up from the new Noise Event Alert:
Figure 6: Noise Event Alert Rule
A physical traffic light indicator in the vehicles that highlights when alerts from Sentinel were going to impact the site, or when an exceedance was detected.
Figure 7: Traffic light Hardware
The solution was implemented with a few different options”. The traffic lights can be configured to:
- Follow the green, yellow and Red levels on the Stakeholder Web, or
- Follow one or more configured alert rules, including the new “Correlated” alert rule.
The Hardware options that are available can be seen in the figure, and also can been seen is an option to use a Windows Smart Phone, instead of other hardware.
Alerts on noise from two correlated locations
This new alert rule was developed to use two locations rather than one to generate an alert. Using a noise monitor that is close to the source of the mine/construction site, and a second noise monitor that is located closer to a community area, the alert uses levels defined on both monitors which both need to exceed for the alert to generate.
In the diagram below, If the exceedance level at location 1 is set to 80dB, and the exceedance level at location 2 is set to 60dB, then both these need to be met, and the exceedance needs to be found at location 1 first, and using the distance between to the two locations, the second exceedance at location 2 should have a delay based on the time it takes for the noise to reach location 2. If this is not met (e.g. location 2 detects noise first) then, the noise event is not attributed to the mine, and an alert is not generated.
During the setup, the user defines the primary (location 1) monitor and the secondary monitor (location 2) used in the alert as well as the distance between them. Alerts can be set to be ignored with high windspeed (configurable) or rain. Alerts can also be defined based on the time of day.
Battery Level in Excel Output
It is now possible to select the addition of the hourly battery levels in the Data export for excel. During the output wizard, the user now has the option to select to show the battery level in the output:
2 1 d
Figure 9: Show Battery Level
Once this is selected in the wizard, the user will have the battery levels in the report listed for each hour of the LEQ and in the summary information:
Figure 10: Battery Levels
Figure 11: Battery Levels
With the release of the New VMT Type 3680, Sentinel has been updated to display the 1-min real time vibration update, along with the Vibration data in the history graph (both VMT and Minimate).
Figure 12: Vibration display on Overview
If it also now possible to export the VMT data graph to Excel output.
Figure 13: Vibration Levels Excel output
This enhancement allows one customer to share a specific location, which will make it visible on another customers overview. This service is setup by Brüel & Kjær on request from the customer. There is currently no impact on either the RTC or the Stakeholder Web, but soon it will also be possible to view these shared monitors on the New RTC.
There is no impact on reporting.
Stakeholder App update
The Stakeholder app has also been updated to add support for vibration information, and to only show selected data types.
Figure 14: Stakeholder App with Vibration
New Site Setup and overview
New customisations are now available in the site setup. The user can now display:
- VMT data in the real-time and history view
- History Ln values
- Hide Audio from a single location, and
Stakeholder Web Configuration
This update allows the user to configure the levels of the traffic light indicators for the stakeholder web. Now if a user wants the traffic light indicators to always remain in the green state, they can simply set both the exceedance and warnings levels to 200 and it will remain green. This is a site-wide change.
Figure 15: Location settings for traffic lights
At the same time, the user can hide the real-time view from the stakeholder be selecting the “Hide Realtime Noise data on Stakeholder” in the figure above.
Services will provide customer training on request.
In case you have any questions, please contact our EMS Operation Centre