The Bluvision Condition Monitoring using the Bluzone ecosystem is done by mounting beacons onto physical assets such as motors or gearboxes. After an initial configuration the installed beacons will continuously collect and advertise telemetry data (temperature, vibration). This data can be received and forwarded to the Bluzone Cloud by BluFi devices installed nearby.
On the Cloud side, this data is then be evaluated against a specific set of rules defined by a Policy. If the data received from any of the installed beacons starts violating this policy, Bluzone will create an alert and (optionally) notify end-users that there is an issue.
Setting up a Condition Monitoring installation does therefore require the 3 essential steps described below.
Note:
The information below assumes basic knowledge about the Bluzone ecosystem - including familiarity with device provisioning, beacon configuration and policies. If you require additional information about these topics, please take a look at our How-To Guides first.
Policy Configuration
In order to enable Condition Monitoring for beacons in your Bluzone project you need to create one or more appropriate policies. The policy type that needs to be used for this type of evaluation is called "Motion Condition". Please refer to the below page for more details about the creation and configuration of a Motion Condition Policy.
The policies for Condition Monitoring can be created at any point before or after the preparation of your devices. We do however recommend that you only start adding beacons to existing policies after you have properly mounted, provisioned and configured them.
Provisioning / Installation
This step refers to the physical placement of a beacon on the target asset. The quality of an asset's health evaluation in Bluzone depends largely on the quality of the data that the attached beacon produces. There are 3 important factors to keep in mind when mounting a beacon for Condition Monitoring:
- The beacon should be mounted as close as possible to the source of the evaluated vibrations.
- The beacon should be mounted and fixated as firmly as possible to avoid resonance.
- The beacon must be mounted in range of a nearby Blufi.
Beacon Configuration
Before Bluzone can evaluate a beacon's data for Condition Monitoring, you need to make sure that a beacon does actually produce the correct type of data for the policy that you are using. There are generally 3 options for properly configuring a beacon for Condition Monitoring:
...
While beacon configuration in general offers a wide selection of settings, only a few of them are relevant for use with Condition Monitoring. Please visit the page linked below for detailed information about the configuration of a beacon's Condition Monitoring features.
...
solution is an end-to-end vibration and temperature monitoring system, which includes monitoring hardware, data transmission hardware, cloud storage, analytics, alerting, and user interface/ visualization. The condition monitoring solutions leverages Bluvision bluetooth low-energy (BLE) beacon technology to provide continuous visibility and long battery life. The BEEKs CM v2 beacon (specifications sheet) has a high-bandwidth accelerometer that takes vibration readings once every two minutes and transmits data to Bluzone cloud (through BluFi gateways, may be AC or DC) where it is stored and analyzed.
The following sections walk through basic setup and installation, policy configuration, Bluzone UI navigation, vibration background and theory, deployment troubleshooting, and advanced configuration.
1. General Setup and Installation
To get started, use the HID-Bluvision Condition Monitoring Installation Guide and walk through the steps from start to finish. This will take you through everything from account creation to hardware provisioning to physical installation. After the installation is complete, for more detailed information on policy setup, navigating Bluzone, and advanced configuration, see the following sections.
2. Policy Creation and Configuration
Bluzone's Policy feature allows you to create custom alerting for the beacons. The following policies in Bluzone are useful with the BEEKs CM v2 beacon:
- Motion Condition: machine learning model that learns a beacon's baseline vibration level, then generates an alert when the vibration deviates from this significantly for a sustained period of time
- Vibration Threshold: generates an alert when a beacon's vibration level goes above a defined threshold
- Temperature Threshold: generates an alert when a beacon's temperature goes above or below defined thresholds
- Battery Voltage: generates an alert when a beacon's voltage is low
3. Navigating Bluzone
The following tutorials show some of the features of Bluzone that are helpful for condition monitoring with the BEEKs CM v2 beacon:
- Change Units
- Firmware Updates