What gets integrated?

This article explains what BriqSafe can integrate through IoT devices, where sensor data is stored, and how readings can complete scheduled jobs.

Note

IoT monitoring must be enabled for your organisation. Device links also require the integrations entitlement at the relevant Location.

What you can integrate

BriqSafe can register sensor devices from an integration and connect them to the item they measure. Depending on the device and setup, you can connect a device to:

• an Asset
• an Area
• a System

A device can be linked to one target only. Its readings are then available on the device record and can be used by scheduled jobs when the device sensors are mapped to compliance parameters.

Supported device setup options

Vendor-provisioned devices

When a vendor has provisioned a device for your organisation, enter its DevEUI in IoT Devices using Add a device by DevEUI. BriqSafe shows A vendor provisioned this device for you. Select the installation Location, optionally enter a Device name, and select Claim device.

Claiming registers the device but does not connect it to what it measures. Select Connect this device, then use Link Device to connect it to an Asset, Area or System.

Devices that are not recognised

If the DevEUI is not recognised, you can register the device by providing its Integration, Device name and Device Type. You can optionally assign it to a Location and Asset.

For the guided setup, select Registering a FactoryLab sensor?, then Use the guided setup. The Select Device Model field offers CLiPR and CLiPR Flex. The selected model fixes the Device Type.

Devices that report before registration

An integration can hold unknown devices for review. Open IoT Devices, select Pending, and open Pending Approvals. Each pending row includes the device EUI, integration, detected type, message count, and first and last seen times.

Use Approve device to enter a Device Name, choose a required Device Type, and select Approve. You can also select Reject device to ignore the device.

What data BriqSafe receives

A device can provide sensor readings and device health information. The device page can show:

• sensor readings plotted as Minimum, Maximum and Average
• connectivity, battery and signal information
• the last time the device was seen
• device identity and integration details, including EUI, Delivered via, Registered, Manufacturer, Model and Firmware

Use 24 Hours, 7 Days, 30 Days or Custom to select the chart period. Readings that do not fill a job remain available on the device chart.

How readings connect to BriqSafe work

1. Open the device and select Link Device on the unlinked row.
2. Choose whether to link the device to an Asset, Room or System.
3. Select the target at its Location, then select Link Device.
4. For an asset link, open Sensor Mappings, select Map, and choose Add Sensor Mapping.
5. Select a sensor and a compliance parameter, then select Add Mapping.

BriqSafe automatically maps sensors when a device is linked. Asset links show the mappings so they can be reviewed. Area and System links also use automatic mappings, but those mappings are not shown for review on the device page.

Only mapped sensors can fill scheduled jobs. A reading is used when the job is due and the reading is newer than the mapping's staleness threshold, which is 24 hours by default. When all required job parameters have values, the job becomes Done. If only some values are available, it becomes In Progress.

What does not happen automatically

• A registered or claimed device is not connected to an Asset, Area or System until it is linked.
• An unmapped sensor reading is shown on the device chart but does not fill a job.
• A reading that arrives when no due job needs that parameter creates no job update, recommendation or notification.
• An out-of-range reading does not create a sensor alert. It can fill a scheduled job, and a matching risk rule can draft a Technical Recommendation.
• Sensor-generated jobs are recorded in the Organisation Logbook as Task auto-completed, with Unknown shown instead of a person's name.

Device status and problems

A device that has not transmitted shows Pending and Waiting for First Data. The troubleshooting panel refers to the gateway, device activation and integration settings. The status clears when the first reading arrives.

Connectivity and battery issues appear on Actions as Sensor offline or Low battery. These items clear when the device reports again or its battery is replaced. There is no alert object for an individual measured value.

If IoT Devices shows Coming Soon, the organisation-level IoT Devices feature is switched off. No user can enable this feature from the product. Without the integrations entitlement, device links from a Location's Asset, Area and System requests are refused, even for an Owner.