> ## Documentation Index > Fetch the complete documentation index at: https://docs.harbinge.rs/llms.txt > Use this file to discover all available pages before exploring further. # Glossary > Key terms used throughout Forager and this documentation ## Asset A physical device tracked in Forager — typically a piece of IT equipment with a barcode label. Each asset has an **asset tag** (the barcode value) and a **recorded location** (where the CMDB says it should be). ## Asset Tag The unique identifier printed on an asset's barcode label. Forager uses this value to match a scanned barcode to a record in the system and to write back to the CMDB. ## Attestation A record created each time a tech scans an asset. Every attestation captures: the asset tag, the tech's current location (determined by RF fingerprint), the tech's identity, a timestamp, and the result type (match, mismatch, or new asset). Attestations are the audit artifact — they are immutable records of when each device was physically observed and where. ## Biometric Lock A security feature that encrypts the Forager session on device and requires fingerprint or face authentication each time the app is opened. Enrollment happens automatically on first login. Managed via Profile → Security. If no biometrics are enrolled on the device, the feature is inactive and the app opens normally. ## Confirmation A successful attestation where the asset's recorded location matches the tech's current location. Also called a **match**. Confirmations update the asset's *Last Confirmed* date and count toward compliance coverage. ## Coverage A measure of how well a location has been surveyed. Rooms with more RF captures from varied positions have higher coverage and produce more accurate location classification. Coverage is visible in the app's Coverage screen. ## Fingerprint The RF signal pattern captured at a specific location during a survey. A fingerprint is built from Wi-Fi access point signal strengths and BLE beacon readings. The app matches a tech's current signal environment against stored fingerprints to determine which room they are in. ## Gateway A LilyGO T-SIM7080G-S3 hardware concentrator that listens for ESP-NOW broadcasts from Raven beacons and forwards check-ins to Forager over LTE-M cellular. Gateways require a Hologram SIM, an LTE antenna, and continuous USB-C power. One Gateway per floor is typically sufficient. ## Location Node A named point in the physical location hierarchy — a building, floor, wing, room, or any other level. Location nodes form a tree: a building contains floors, floors contain rooms. Assets and survey fingerprints are both associated with location nodes. ## Match See **Confirmation**. ## Mismatch An attestation where the tech's current location (by RF fingerprint) does not match the asset's recorded location. Forager alerts the tech and asks whether to update the asset's location. The result is recorded as either *mismatch\_confirmed* (location updated) or *mismatch\_dismissed* (tech chose not to update). A mismatch indicates that either the asset has been moved, or the asset's CMDB record is out of date. ## Never Confirmed An asset status indicating that the asset exists in Forager's registry but has never received a successful match attestation. The asset may have been imported from a CMDB or added during an initial new-asset scan, but no tech has yet performed a clean confirmation for it. Never-confirmed assets are not necessarily lost — they may simply not have been encountered during normal field work yet. A high count of never-confirmed assets in an area typically means that area hasn't been swept. ## PMI (Preventive Maintenance Inspection) A scheduled inspection of a physical asset to verify it is functioning correctly, safely, and in compliance with regulatory standards. Common in healthcare (Joint Commission, DNV), facilities management, and industrial environments. In Forager, PMI schedules are stored as `next_pmi_date` and `pmi_interval_days` on each asset record. ## PMI Status A computed value indicating where an asset stands relative to its scheduled inspection date: | Status | Meaning | | ------------ | ------------------------------------------- | | **Overdue** | `next_pmi_date` is in the past | | **Due Soon** | `next_pmi_date` is within the next 30 days | | **OK** | `next_pmi_date` is more than 30 days away | | **None** | No PMI schedule has been set for this asset | PMI Status appears in the [PMI Compliance](/dashboard/reports#pmi-compliance-tab) report and is included in the asset roster export. ## Photo Attestation An optional feature that captures a tight JPEG crop of the physical asset tag at the moment of each camera barcode scan. The photo is stored alongside the attestation record and is viewable as a thumbnail in the web Attestation Log. Provides auditors with timestamped visual evidence that a tech directly witnessed a device. Photo Attestation is opt-in per company and has no effect on hardware scanner attestations (no camera frame is available in that path). ## Presence Confirmation (Manual) See **Presence Confirmation**. ## Presence Confirmation (Passive) Automated asset presence confirmation performed by Raven beacons without any tech involvement. Ravens broadcast their identity periodically; a Gateway forwards the broadcast to Forager, which records a check-in for the assigned asset. Passive confirmation does not replace manual scanning for compliance attestation but confirms an asset is still in the facility between manual sweeps. ## Raven A battery-powered ESP32 beacon attached to an asset. Ravens wake on a configurable interval, scan nearby Wi-Fi access points and BLE devices, sign the payload with a per-device HMAC secret, and broadcast via ESP-NOW to any nearby Gateway. Ravens are provisioned via the Forager Android app; each Raven has a paired NTAG215 NFC sticker for field identification. ## Raven Check-in A recorded event when a Gateway successfully receives and verifies a broadcast from a Raven. Each check-in updates the Raven's `last_seen` timestamp and battery level. Check-ins with a valid HMAC are recorded as `hmac_valid: true`. The core Forager workflow. As field techs move through a facility doing normal IT work, they scan device barcodes. The app compares each scanned device's recorded location to where the tech currently is. Matches are silently recorded; mismatches trigger an alert. Compliance attestation accumulates continuously without dedicated audit walks. ## Recorded Location The location currently on file for an asset — what the system believes to be the asset's home. This is the value written to the CMDB and displayed in reports. It updates when a mismatch is confirmed. ## Site A building (or equivalent top-level location node) used as the unit of access control in Forager. Techs are assigned to sites; a site assignment grants access to all assets on every floor and in every room inside that building. Which level of the location tree counts as a "site" is configured per company. The default is the building level — direct children of the root node. ## Site Membership A tech's assignment to a specific site. Each membership grants the tech read and write access to all assets located under that site node. A tech can have memberships at multiple sites and can switch between them using the site picker on the home screen. Admins are not subject to site memberships — they see all assets across the entire company. ## Survey The process of teaching Forager what each room's RF environment looks like. A tech walks each room once, either tapping their position on a floor plan or naming the location, and the app captures several RF scans. The resulting fingerprint is used to classify the tech's location during future presence confirmation sessions. ## Webhook An HTTP callback that Forager sends to an external system (such as ServiceNow) when an attestation is recorded. Webhooks enable real-time CMDB updates without manual data entry. Configured under Dashboard → Settings.