Sensors overview

This article explains how sensors work in BriqSafe and guides engineers and viewers through registering, placing, linking, and managing sensors for continuous monitoring of assets.

Note

Required role: Engineer for device registration, placement, and linking; Viewer for monitoring and reviewing sensor data

Adding and Registering a Sensor Device

To bring new sensor hardware into BriqSafe, you first need to register the device in the system.

1. Open IoT Devices and select Add Device.
2. On Select Device Source, choose FactoryLab and click Next.
3. On Select Device Model, pick either ClipR or ClipR Flex.
4. Complete the Add FactoryLab Device form to register the device.

Note that only FactoryLab devices can be registered today. The Other Provider option is marked "Coming Soon" and is not selectable.

Registering a device does not link it to an asset yet; you must link it before it can start feeding data into jobs.

Placing a Sensor and Linking to an Asset

After registration, place the sensor physically and attach it to the asset it will monitor.

1. Open IoT Devices and click Place Device.
2. In Device Identifier, paste the sensor’s QR code data or type its 16-character DevEUI.
3. Click Next.
4. On Select Location, choose the site, then the asset, and for temperature devices, select the water type (Cold, Hot, Mixed, or Return pipe).
5. Click Confirm Placement then Place Device.

A message "Device placed successfully!" confirms the sensor is registered and linked.

The web wizard requires pasting or typing the DevEUI since it does not have a camera; camera scanning exists only in the mobile app.

If the device is already placed on another asset, placing it again relocates it and removes the old link. The button will read Relocate Device in this case.

Linking a Device to an Asset and Mapping Sensor Data

You must link the registered device to an asset and map its sensor entities to the relevant compliance parameters.

1. Open the device from the IoT Devices list.
2. In the Linked To card, click Link Device and select the target asset.
3. Once linked, the Sensor Mappings section appears.
4. Click Map to connect each device sensor entity to the BriqSafe parameter it measures.
5. Each mapping includes a staleness threshold (default 24 hours), which determines how old a reading can be before it is ignored.
6. Save your changes.

Each device can link to only one target at a time (asset, area, or system).

Only mapped entities provide data to scheduled jobs; unmapped sensor data is visible in charts but does not auto-fill jobs.

Monitoring Sensor Devices

Monitor sensors deployed at locations or across the organisation to check their status and readings.

Viewing Devices at a Single Location

1. Open the desired Location.
2. Go to the IoT Devices tab.
3. View the list displaying each device’s Name, Type, Status, Battery, Signal, Last Seen, and linked asset.
4. Use the Search box and filters for Status and Type to narrow results.
5. Click Refresh to update device metadata live from the sensor platform.

If no devices are deployed, the message "There are no IoT devices deployed at this location." appears.

Viewing All Devices Across the Organisation

1. Open IoT Devices from the organisation menu.
2. Browse the cross-site list with the same columns as the location view.
3. Search and filter devices by name, EUI, asset, status, and type.
4. Open any device row to see full details.

Understanding Device Status

Device status reflects connectivity, not compliance:

• Pending: Device registered but not yet sent data.
• Online: Device actively reporting data.
• Offline: Device not currently reporting.
• Unknown: Status cannot be determined.

Battery and signal indicators show device health; low battery or poor signal warnings appear alongside status badges.

Note that device status does not indicate asset compliance. An online device may still have non-compliant readings, and offline devices do not trigger alerts.

Reading Device Details and Telemetry

1. Open a device from the IoT Devices list.
2. The info card displays DevEUI (read-only), Type, Source, manufacturer, model, battery, and signal data where available.
3. The Linked To card shows the asset, area, or system the device is linked to.
4. Select a sensor entity from the left-hand list to view its readings chart showing min, max, and average over a selected time range.
5. Click Refresh to reload device details and chart data.

Devices that have never transmitted data show a Pending status and a troubleshooting panel instead of the chart. This state clears once the first reading arrives.

How Sensor Readings Interact with Scheduled Jobs

Sensors automatically fill scheduled compliance jobs with measurement data, streamlining fieldwork.

1. When a job for an asset is Pending or In Progress and includes parameters linked to sensor entities, fresh readings fill those parameters automatically if within the staleness threshold.
2. If all required parameters are filled, the job status changes to Completed. If only some are filled, it remains In Progress; if none are filled, it remains Pending.
3. Each filled parameter records the reading’s value, unit, and timestamp as data provenance.

Readings older than the staleness threshold are skipped. Offline devices cause jobs to remain pending, needing manual completion.

The job status reflects progress, not pass or fail: compliance rules evaluate readings separately.

Reviewing Sensor-Completed Jobs and Risk Recommendations

You can audit jobs filled by sensors just as you would manual entries.

1. Open the completed job from the Location tab Jobs.
2. Parameter values display sensor readings along with their value, unit, and timestamp.
3. The data provenance shows the source as the sensor pipeline.

If a sensor-filled job breaches a risk rule, the system creates a draft Technical Recommendation in the Recommendations tab of the location.

1. Open the draft recommendation to review.
2. With edit access, approve or dismiss it.

The sensor path does not generate cases or automatic escalations; draft recommendations follow the standard review workflow.

Managing and Editing Sensor Devices

You can update device details, unlink it from an asset, or move it to another asset as needed.

1. Open the device from the IoT Devices list.
2. Click Edit to rename the device or change its type; then click Save.
3. To detach a device from its asset, use Unlink in the Linked To card.
4. To move a device, run Place Device again to relocate it.

Unlinking preserves sensor mappings, allowing easy relinking without remapping entities.

Device deletion requires a Manager or higher role and is not available for lower roles.

Troubleshooting Sensor Issues

Device Stuck in Pending

A device that is Pending has not yet transmitted its first reading. This is a normal lifecycle stage rather than a fault.

If the device remains Pending for long, verify the physical sensor and its network conditions; there is no manual retry in the app.

DevEUI Registration Conflicts

If a DevEUI you enter is already registered in your organisation, the system reuses that device without creating a duplicate.

If the DevEUI belongs to another organisation, registration stops with the message: "This device is registered to another organisation. Please contact support."

Interpreting No Alerts from Sensors

Sensors do not generate in-app alerts, alert queues, or per-reading dismissal or escalation actions.

When a reading is concerning, it fills a scheduled job that, if breaching, triggers a draft Technical Recommendation automatically.

To act on an issue outside this workflow, schedule a manual follow-up job.

No push notifications or alerts are sent for offline or bad readings; monitoring device lists is necessary to notice offline devices.

Device Activity Timeline

The Device Timeline card on a device’s detail page currently shows a "Coming Soon" placeholder and holds no data.

Do not rely on it for auditing device history.

Prerequisites for Using the IoT Devices Area

The IoT Devices functionality requires your organisation to have the integrations entitlement (gold plan or above) and the IoT Devices feature toggle enabled.

If the toggle is off, all IoT routes show a "Coming Soon" screen. Without entitlement, device requests are refused even for organisation owners.

These are organisation-level settings; individual users cannot enable them.