Sensors overview

This article explains how sensors are registered, linked, monitored, and used to fill scheduled jobs in BriqSafe.

Before You Get Started

The IoT Devices feature must be enabled for your organisation. If it is disabled, IoT Devices and its pages show Coming Soon. Device links also require the integrations entitlement at the relevant Location.

Register a sensor

Register a sensor with its 16-character DevEUI (device identifier).

1. Open IoT Devices and select Add a device by DevEUI.
2. Type, paste, or scan the DevEUI. It can include dashes or colons, or contain QR data.
3. Follow the result shown for the identifier:

• A vendor provisioned this device for you: select the installation Location and choose Claim device.
• This device is already registered: select View device.
• This device is registered somewhere else: contact support or the vendor named in the message.
• An unrecognised identifier: continue with the registration fields or select Use the guided setup for a FactoryLab sensor.

A malformed identifier is rejected with Invalid DevEUI format. Must be 16 hex characters. If the check fails, select Try again. A failed check does not mean that the identifier is available.

Use the guided setup for a FactoryLab sensor

1. On the unrecognised-identifier screen, select Use the guided setup.
2. Under Select Device Model, choose CLiPR or CLiPR Flex.
3. Select Add FactoryLab Device.
4. Enter the identifier in DevEUI and review Device Name. The name must contain 3 to 100 characters.
5. Optionally select Link to Entity.
6. Select Add Device or Add & Create Another.

The selected model fixes Device Type. To change it, go back and select another model. Registering a device does not link it to an Asset, Area, or System unless the link succeeds.

Connect a sensor to what it measures

A claimed or registered device must be linked before its readings can fill a job.

1. Open the device and select Link Device on the unlinked row.
2. In What do you want to link this device to?, choose Asset, Room, or System.
3. Select the target at its Location and select Link Device.

A device links to one target only. Linking automatically maps its sensors. If a sensor could match more than one parameter, review Sensor Mapping Results and select Confirm Mappings.

Review sensor mappings for an Asset

1. Open the linked device.
2. In Linked To, select Map.
3. Select Add Sensor Mapping.
4. Choose a sensor in Select sensor.
5. Choose a parameter in Select parameter.
6. Select Add Mapping.

Only mapped sensors fill jobs. Unmapped readings remain available in the device chart. One sensor can map to one parameter. A mapping uses a 24-hour staleness threshold by default; readings older than that are skipped.

Understand automatic job completion

When automatic filling is enabled, BriqSafe checks due jobs and uses the latest valid reading from each mapped sensor.

• Only a To do or In Progress job due today or earlier is checked.
• A reading must be newer than the mapping's staleness threshold, which is 24 hours by default.
• If all parameters have values, the job becomes Done.
• If only some parameters have values, the job becomes In Progress.
• If no values are filled, the job keeps its current status.

The job stores the reading's value, unit, and time. A job that is not due yet is not filled. A parameter that no sensor measures still needs to be completed manually. The Automatic Job Execution setting on a Structure can turn automatic filling off for all jobs under that Structure.

View sensor status and readings

View devices at a Location

1. Open the Location and select the IoT Devices tab.
2. Review each device's Name, Type, Status, Battery, Signal, Last Seen, and Linked To values.
3. Use search to find a device by name or EUI, or select Refresh to request current data.

The organisation-wide IoT Devices list also supports the Status, Type, Source, Link Status, and Site filters. Pending means that the device is registered but has not transmitted yet.

Read a device's telemetry

1. Open the device.
2. Select a sensor from the Sensors list.
3. Choose 24 Hours, 7 Days, 30 Days, or Custom.

The chart shows Minimum, Maximum, and Average readings. Select Refresh to re-fetch data. A device that has never transmitted shows Waiting for First Data. Its troubleshooting checks cover the gateway, device activation, and integration settings.

Understand alerts and compliance results

Sensor status describes connectivity, not compliance. A device can be Online while an Asset is not compliant, and an Offline device does not create a compliance issue by itself.

• A device that stops reporting creates a Sensor offline item in Actions.
• A low battery creates a Low battery item in Actions.
• These items are counted in the Sensors offline and Sensors with low battery tiles.
• An out-of-range reading does not create a sensor alert. If it fills a scheduled job, the job can complete and a matching risk rule can create a draft Technical Recommendation.

Sensor offline and low battery items clear when the device reports again or its battery is replaced. They do not have an acknowledgement or push notification.

Review automatically completed jobs

1. Open Organisation Logbook from the main menu.
2. Find the entry named Task auto-completed.
3. Select the entry to open its details.

The entry has no named person as the actor and shows Unknown in the byline. The Location's Timeline also lists the job, but only the logbook event identifies it as sensor-completed.

Maintain a device

1. Open the device.
2. Select Edit to change the device name or expose Type, then select Save.
3. Select Unlink in the Linked To card to detach the device.
4. Use Move, Replace, or Remove from site when the device changes Location, is exchanged, or is returned to the vendor.

Unlinking removes the sensor mappings. Linking the device again runs automatic matching again rather than restoring the previous mappings. Remove from site is reversible and does not delete the device.

Investigate a device that is not reporting

• Check whether the device is Pending and shows Waiting for First Data.
• Review the gateway, device activation, and integration settings listed under Troubleshooting Tips.
• Check the device's Device Timeline for registration, placement, offline periods, recovery, and battery events.
• Contact support with the device identifier when the device has changed organisations, requires platform history, or you need raw platform data.

The device timeline records lifecycle and connectivity events, not individual readings. Readings are available in the device chart.