Embedded Files
Because you are not permanently in front of your computer at your office, when something happens on your machines you want to be alerted and notified by e-mail on your smartphone. At this moment, you can use a simple web browser connected to your company network, connect to Vision and consult details of latest alerts.
What is an alert?
2 categories of alerts are detected and tracked by Vision:
machine alarm status changes to notify you when some aggravating alarms status changes occured - ex: machine was OK and then presents temporarily an DANGER alarm status before to come back in OK alarm status
instrument status changes to notify you when some troubles occured - ex: network connection loss, sensor defects, ... - and
For both alert categories, Vision tracks all status changes in order to tell you how long machine stayed in each alarm status (OK, preALARM, ALARM or DANGER) and/or how long MVX stayed in each state (Ready, Started, Unreachable, Sensor defects)
Notification workflow
According to your user settings - see advanced settings - you can be notified by email when alarms occured on your machine and then consult Vision when needed to have more details about these alerts
e-mail content:
Server name: name of NESTi4 server
Database name database where is declared machine
Asset parents: machine location name
Asset name: machine name
Asset Guid: machine universal identifier
Alarm status: new alarm status (previous alarm status)
Measurement date: date of measurement with this alarm
Operating condition: operating condition of the machine when alarm occured
Vision alerts console
When connected to Vision, then open the alerts console to see all machines with at least one new alert:
Alerts list presents the following information for each machine with at least one new alert:
Parent name of the first parent ; click on this name to navigate directly to this location
Name name of the machine ; click on this name to navigate directly to the correponding asset home page
Last acknowledgment date and time of the previous acknowledgment of this machine
%Vibration alarm status breakdown (in duration and % of time) of the change in alarm status since the last acknowledgment (or beginning of monitoring)
%Instrument status breakdown (in duration and % of time) of the change in instrument status since the last acknowledgment (or beginning of monitoring)
Begin date and time when the first status change since the last acknowledgment (or beginning of monitoring)
End date and time when the status comes back to a normal situation without specific maintenance - ex: false alarm due to high vibration levels temporarily induced by an external event (works, handling, etc.)
Because this list presents machines with new alerts, you can select one or more machines and decide to do one of the following operations:
acknowledge alerts for the selected machine
create a work order for the selected machine - see Work orders
How acknowledge alerts?
The alert console should contain only machines with new alerts and requiring intervention in order to help you to focus your attention on important informations. Consequently, as soon as an alert has been processed then it must be acknowledged so that the machine concerned disappears from the alerts console. From this moment, if a new alert appears on this machine, then you will be notified again and the machine will again be put in the list of alerts.
Acknowledgement can be done directly from the alerts console or from the asset home page
IMPORTANT:
Acknowledgement considers all categories of alerts ; it is not possible to acknowledge only machine alarms or only instrument defects
Acknowledgement comment text is mandatory for acknowledgment traceability (machine history) - see Asset Home Page
Page updated
Report abuse