QR and identifiers¶
Where: QR & Identifiers in the Operations group, /app/qr. Shown when asset operations are turned on for your organization.
What it answers: can every device be found quickly on the plant floor, by label, tag or the plant's own ID?
What a label is¶
A BreachSpider QR label holds only a random code: no device name, no address, no inventory details. Scanning it opens the device for people signed in to your organization; anyone else sees nothing. It is not a password, and revoking it makes the code open nothing.
The screen¶
Counts at the top: devices, with an active label, without a label, labels not yet printed, revoked labels, devices without an asset tag, plant and legacy identifiers.
Filter by site, area, label state and search (name, tag, model or identifier). Select devices, or every device in the scope, and act:
| Action | What happens |
|---|---|
| Create QR labels (N without one) | Every device in the chosen site and area without a label gets one (no code yet, or a code never printed). Existing labels keep their code |
| Reprint all labels | Labels for every device in the scope; existing codes are reprinted, never changed |
| Create labels for selected | Labels for the devices you ticked |
| Print labels | Three formats: 2.5 x 1.5 in sheet labels, 30 per sheet (2.625 x 1 in), thermal 2 x 1 in. Optionally show site and area, vendor and model, and an extra line. After printing you confirm whether they printed correctly; only confirmed prints are recorded. Reprints keep the code |
| Replace label | Revokes the old code and issues a new one, with a reason |
| Revoke | The code opens nothing from now on, with a reason; the device and its records are unchanged. Undo is available |
| Scan QR | Uses the camera, or a photo of a label. If a code is on several devices, you choose; nothing opens automatically |
| Enter a code | Type or use a barcode scanner: a BreachSpider label, an asset tag, a plant ID or a legacy code |
| Import identifiers | One row per code: device (asset tag or exact name), type (plant_id, customer_label or legacy_qr), value. Rows are checked first and shown with a result; rows with a problem are left out. Undo is available |
An unknown code can be assigned to a device as an identifier, so the same code finds the device next time.
How it works on the plant floor¶
- Create labels for a site. Choose the site (and area), then Create QR labels: every device without a label gets one. For a single device, open it and use QR label in its panel (Create label, Print label).
- Print and stick. Sheet or thermal labels, sorted by asset tag so you can walk the floor in order. Confirm what printed correctly; only confirmed prints are recorded.
- Scan. A technician uses Scan QR (phone or tablet camera, or a photo of the label) or Enter a code (typed, or a USB or Bluetooth barcode scanner). The device opens with its findings, fix, maintenance and backups. Someone outside your organization who scans the label sees nothing.
- Keep the labels you already have. If devices already carry plant equipment IDs, customer labels or older QR or barcode labels, Import identifiers links those codes to the devices. Scanning an existing label then finds the device too, so nothing has to be relabelled.
You can use BreachSpider's own identifiers (the QR label and the asset tag), your own codes, or both: any of them finds the device.
Identifiers and asset tags¶
- Asset tag:
SITECODE-0001, from the site code set on Sites. - Identifiers: plant equipment IDs, customer labels and existing QR or barcode labels, so a device can be found by any of them. Not serial numbers or network addresses: BreachSpider does not store those, and an identifier that looks like a network address is refused.
- Record status: Operational or Follow-up required, your own workflow label. It never changes findings.
Every label, tag and identifier event is kept in the audit history on Backups & integrity.
API¶
This module is part of the web app. It has no public API, SDK or MCP tool.