Glossary
Key terms used throughout the Blecon documentation.
Components
The named parts of Blecon. See Components for the full map.
Access Point Integrations: Juniper Mist access points used as tag scanners. See Integrations.
Alert Workflow: The lifecycle every alert follows: pending, active, acknowledged, resolved. See Alert Workflow.
Asset Registry: Every registered tag as a named asset with type, keywords, custom fields and history. See Asset Registry.
Blecon Hub: Fixed hotspot hardware mounted in a facility. See Blecon Hub.
Blecon Track AI: The AI features in Blecon Track: rule suggestions, rule drafting from a sentence, and verdicts on alerts. See Blecon Track AI rule builder.
Deployment Planning: Setting up a site with its floors, rooms, hubs and anchors, and planning where hubs go. See Set up a site.
Device Tracking: The policies and work schedules that decide when a device running the Blecon Agent has its own location recorded. See Device Tracking.
Event Delivery: The channels that carry alerts and notifications to people and systems. See Event Delivery.
History Store: The position and sensor record for every asset, kept for 3 months. See History Store.
Insights: Statistics and PDF reports across the fleet. See Statistics and Reports.
Map: The map of every asset's current position, with trips and raw positions. See Map.
MCP Server: The Model Context Protocol server that gives AI assistants access to Blecon Track. See MCP Server.
Positioning Engine: The part of the cloud that turns hotspot sightings into positions. See Positioning Engine.
Registration Tools: The ways to add tags: scanning, workflows and bulk import. See Registration Tools.
Rules Engine: Evaluates every asset against every enabled rule and raises alerts or notifications. See Rules Engine.
Security Model: Security between the tag and the cloud. Hotspots relay data but hold no keys. See What is Blecon?.
Tag Range: The tags that work with Blecon. See Tag Range.
Tracker API: The API that the Blecon Track dashboard is built on. See Tracker API.
Trip Timeline: An asset's position history segmented into stops and trips. See Trip Timeline.
Workspace Administration: Workspace settings, members and roles, and account management. See Workspace settings.
Zone System: The zones you draw on the map, and the entry and exit history they record. See Zone System.
A
Alert: An active alert created when a rule's condition is met. Alerts persist until the condition resolves. See Alerts.
Asset: A tracked tag displayed on the Blecon Track map. See Assets.
Asset association: A parent-child relationship between two assets, representing a physical connection (e.g., a sensor attached to a vehicle). See Asset associations.
B
Blecon Agent: The software (an app) for mobile devices, laptops and vehicles. It makes the device a hotspot (it scans for nearby tags and relays their data to the cloud), and it scans tags to register them. See Blecon Agent (mobile hotspots) for download links and setup.
Blecon Track: The Blecon tracking application. Provides the map, rules, alerts, and notifications. See Blecon Track overview.
C
CloudEvents: An open standard for describing event data. Blecon uses CloudEvents format for all events delivered via data routing.
Coordinate zone: An earlier name for a zone. See Zone.
D
Data routing: The system for delivering tag events from Blecon to your external systems.
Device: A mobile device, tablet or laptop running the Blecon Agent. The dashboard lists devices under Devices, where you can see where each one is. A device also provides tracking coverage: where it relays tag signals, it is a hotspot. A device is not a tag. The things you attach to assets are tags, shown as assets.
Device linking: Lets the person using a device run a workspace's workflows from the Blecon Agent's Workflows menu, with no account. A device links to one workspace at a time. Linking is separate from device tracking: a device can be linked and not tracked, or tracked and not linked. See Devices running the Blecon Agent.
Device tracking: Records where a device running the Blecon Agent is, within the workspace's Device Tracking policies. A tracked device is listed under Devices. Linking a device usually turns on tracking too, unless the person chooses Link without tracking. Unlinking does not stop tracking. Stop tracking on the device's page stops it and keeps the device's history. Starting again needs the person's consent, except for company devices.
H
Heartbeat: A periodic position update sent even when a tag hasn't moved. Ensures you always have recent position data.
Hotspot: The general word for anything that detects Bluetooth tag signals and forwards them to the Blecon cloud: a hub, a device running the Blecon Agent, or a third-party access point. Hotspots don't pair with tags or decrypt data. Security is tag-to-cloud. See Hotspots.
Hub: A dedicated hardware hotspot, mounted at a permanent location. A hub is one kind of hotspot, so use "hub" when you mean the fixed hardware and "hotspot" when you mean any of them. Hubs are registered and placed under Network → Hubs in the dashboard. See Hubs.
L
Linked device: A device running the Blecon Agent that is linked to one workspace. See Device linking.
P
Positioning: The process of calculating a tag's location from Bluetooth signal measurements and hotspot locations. See How positioning works.
Positioning profile: A named preset (Fast, Balanced, or Accurate) that sets all positioning tuning values, trading reaction speed against position stability. Profiles are maintained by Blecon and improved centrally; overriding an individual value through the API puts a workspace on Custom. See Positioning settings.
R
Anchor: A Blecon tag installed at a fixed place and placed on the map. A hotspot that detects a placed anchor gets a location fix at the anchor's position, if that fix is better than the location the hotspot already has. An anchor without a position has no effect. Previously called a reference beacon; older API integrations may still use the reference_* field names, which continue to work. See Anchors.
RSSI: Received Signal Strength Indicator. A measurement of Bluetooth signal strength in dBm (typically -100 to 0). Stronger signals (closer to 0) indicate the tag is nearer to the hotspot.
Rule: A condition that the system evaluates against tag positions and behaviour. Rules can generate alerts, auto-associate tags, or record trips. See Rules.
S
Stop: A period when an asset was still, at one place. A stop is a zone if the asset stopped inside one, and a coordinate otherwise. See Trips and stops.
T
Tag: A small BLE tracker, smart label, or sensor attached to an asset. Tags broadcast Bluetooth signals that hotspots detect, and the system calculates their position. See Hardware overview.
Trail: The movement path of an asset shown on the Blecon Track map, connecting position updates over time.
Trip: One movement between two stops. A stationary period too short to be a stop stays on the trip as a pause, so a lunch break does not split one run in two. See Trips and stops.
Z
Zone: A named area that you draw on the map (polygon or bounding box). An asset is in the zone when its position is inside the boundary and, for a zone with a floor, on that floor. See Zones.
Zones indoors: Zones used inside buildings. Placed anchors and placed hubs give hotspots their location, so the assets they detect get positions that zones can contain. See Zones indoors.
Zone tag: A label applied to zones for grouping and bulk rule management. See Use zone tags to manage rules at scale.