Glossary

The terms of this application in the meaning they carry here. Where a term means something different in another application, it says so.

Term	Meaning
Anchor	A BLE antenna array that receives the signals of the tags and measures the angle they arrive from. An anchor is connected to an Anchor+ and does not talk to the cloud itself. The device list still shows the older spelling xAnchor.
Anchor+	The device at the installation, with up to three anchors connected to it. It evaluates their reception and reports the measurements to an Edge or directly to the cloud. The device list still shows the older spelling xAnchor+.
Artifact	A file stored with a space — a floor plan, a firmware image or a configuration. Managed under Files.
Device	A piece of equipment installed in a space: an anchor, an Anchor+, an Edge or a gateway. Every device belongs to exactly one tenant; within that tenant it may be bound to one space or be shared across all of them, see Shared space. Elsewhere: in Tag Provisioning & Management a device is the cellular tag itself or a BLE device it observes.
Device type	Determines what a device is and what it can do — which features it offers, which devices may sit below it, and how it authenticates. Chosen when the device is created and not changed afterwards.
Edge	Aggregates several Anchor+ devices of one site: it computes the positions from their measurements, detects entering and leaving of locations and passes the results to the cloud. It runs on site, not in the cloud. The device list still shows the older spelling xEdge.
Feature	A capability that can be switched on and configured individually. A location type has features such as the GPS Map, the floor plan or scenarios; a device has features such as positioning or presence detection.
Gateway	An IoT gateway through which devices reach the cloud. Gateways belong to the tenant, not to a single space, and are managed in the tenant administration. Elsewhere: in Tag Provisioning & Management "gateway" is a property of a beacon, not a device of its own.
Georeferencing	Placing a floor plan onto the world map so that a position in the plan corresponds to a geographic coordinate. Done by setting reference points whose real coordinates are known.
Infrastructure space	The space an application space obtains its locations, devices, tags and position events from — read-only. One infrastructure can serve several use cases that stay separate from one another: each has its own business data, all see the same location tree and the same devices. The reference is set when the application space is created and cannot be changed afterwards.
Localization	Determining whether an asset is inside a defined location. It uses the position as its input — positioning produces the coordinate, localization decides which location it falls into.
Location	A node in the location tree of a space — a site, a hall, a floor or a zone, for example. Which levels exist and what may sit below them follows from the location type.
Location type	Determines what a location is and how it behaves: which types may sit below it and which features it offers. The types are configurable per tenant, so the levels differ from installation to installation.
Measurement	A single measured value that a position is computed from — the angle a signal arrives from, or its received strength.
Onboarding	Connecting a device to the cloud so that it reports and can be configured. Elsewhere: in Users & Permissions onboarding means inviting a person and setting up their account.
Permission	What a role is allowed to do with a resource. Permissions are not granted per person but per role, and they are inherited along the location tree: whoever may act on a location may also act on everything below it.
Position	Where an object is. Either a coordinate in a coordinate system or an identifier such as a location or an address.
Positioning	Deriving the position of an object from a series of measurements — for example from the angles or signal strengths that several anchors have measured.
Role	A bundle of permissions that is assigned to a user or a group, for example Space Admin or Tracking Viewer. Roles are the only place where permissions are defined.
RTLS	Real-Time Locating System. A system that determines and reports the position of tagged objects continuously.
Scenario	Binds a locating method to a location: which technology is used there, with which devices and which settings. Without a scenario there is no positioning at a location.
Scenario type	The template a scenario is created from. It brings the locating method along and defines which settings the scenario has and which devices it requires.
Shared space	A device or a tag does not have to belong to a single space. Assigned to the shared space of the tenant instead, it is available in all of that tenant’s spaces — useful for equipment that several spaces use.
Space	A self-contained working area within a tenant. What it holds follows from its space type: the locating infrastructure — a location tree with the devices and scenarios installed there — the business data of an application, or both. A tenant may have several spaces, one per site for example.
Space type	Determines the role of a space: Infrastructure holds locations, devices and scenarios, Application holds the business data of one use case and references an infrastructure space, General holds both and is the default. Chosen when the space is created and not changeable afterwards. Each application offers only the types it can work with, which is why the selected space may change when you switch application.
Tag	A physical tag attached to an object so that it can be located. A tag belongs to a tenant and is assigned to a space, or to the shared space of the tenant. Elsewhere: in Tag Provisioning & Management a tag is a cellular device that appears on its own and has no space.
Tag profile	The configuration a tag receives — how often it reports, how it behaves, which firmware it runs. Several tags share a profile, so a change reaches all of them.
Tenant	An isolated organizational unit. Users, groups, spaces, devices, assets and tags always belong to exactly one tenant, and no data is visible across tenants.
User	A single person with an account. Which applications and which spaces they see follows from their roles.

Term

Meaning

Anchor

A BLE antenna array that receives the signals of the tags and measures the angle they arrive from. An anchor is connected to an Anchor+ and does not talk to the cloud itself. The device list still shows the older spelling xAnchor.

Anchor+

The device at the installation, with up to three anchors connected to it. It evaluates their reception and reports the measurements to an Edge or directly to the cloud. The device list still shows the older spelling xAnchor+.

Artifact

A file stored with a space — a floor plan, a firmware image or a configuration. Managed under Files.

Device

A piece of equipment installed in a space: an anchor, an Anchor+, an Edge or a gateway. Every device belongs to exactly one tenant; within that tenant it may be bound to one space or be shared across all of them, see Shared space. Elsewhere: in Tag Provisioning & Management a device is the cellular tag itself or a BLE device it observes.

Device type

Determines what a device is and what it can do — which features it offers, which devices may sit below it, and how it authenticates. Chosen when the device is created and not changed afterwards.

Edge

Aggregates several Anchor+ devices of one site: it computes the positions from their measurements, detects entering and leaving of locations and passes the results to the cloud. It runs on site, not in the cloud. The device list still shows the older spelling xEdge.

Feature

A capability that can be switched on and configured individually. A location type has features such as the GPS Map, the floor plan or scenarios; a device has features such as positioning or presence detection.

Gateway

An IoT gateway through which devices reach the cloud. Gateways belong to the tenant, not to a single space, and are managed in the tenant administration. Elsewhere: in Tag Provisioning & Management "gateway" is a property of a beacon, not a device of its own.

Georeferencing

Placing a floor plan onto the world map so that a position in the plan corresponds to a geographic coordinate. Done by setting reference points whose real coordinates are known.

Infrastructure space

The space an application space obtains its locations, devices, tags and position events from — read-only. One infrastructure can serve several use cases that stay separate from one another: each has its own business data, all see the same location tree and the same devices. The reference is set when the application space is created and cannot be changed afterwards.

Localization

Determining whether an asset is inside a defined location. It uses the position as its input — positioning produces the coordinate, localization decides which location it falls into.

Location

A node in the location tree of a space — a site, a hall, a floor or a zone, for example. Which levels exist and what may sit below them follows from the location type.

Location type

Determines what a location is and how it behaves: which types may sit below it and which features it offers. The types are configurable per tenant, so the levels differ from installation to installation.

Measurement

A single measured value that a position is computed from — the angle a signal arrives from, or its received strength.

Onboarding

Connecting a device to the cloud so that it reports and can be configured. Elsewhere: in Users & Permissions onboarding means inviting a person and setting up their account.

Permission

What a role is allowed to do with a resource. Permissions are not granted per person but per role, and they are inherited along the location tree: whoever may act on a location may also act on everything below it.

Position

Where an object is. Either a coordinate in a coordinate system or an identifier such as a location or an address.

Positioning

Deriving the position of an object from a series of measurements — for example from the angles or signal strengths that several anchors have measured.

Role

A bundle of permissions that is assigned to a user or a group, for example Space Admin or Tracking Viewer. Roles are the only place where permissions are defined.

RTLS

Real-Time Locating System. A system that determines and reports the position of tagged objects continuously.

Scenario

Binds a locating method to a location: which technology is used there, with which devices and which settings. Without a scenario there is no positioning at a location.

Scenario type

The template a scenario is created from. It brings the locating method along and defines which settings the scenario has and which devices it requires.

Shared space

A device or a tag does not have to belong to a single space. Assigned to the shared space of the tenant instead, it is available in all of that tenant’s spaces — useful for equipment that several spaces use.

Space

A self-contained working area within a tenant. What it holds follows from its space type: the locating infrastructure — a location tree with the devices and scenarios installed there — the business data of an application, or both. A tenant may have several spaces, one per site for example.

Space type

Determines the role of a space: Infrastructure holds locations, devices and scenarios, Application holds the business data of one use case and references an infrastructure space, General holds both and is the default. Chosen when the space is created and not changeable afterwards. Each application offers only the types it can work with, which is why the selected space may change when you switch application.

Tag

A physical tag attached to an object so that it can be located. A tag belongs to a tenant and is assigned to a space, or to the shared space of the tenant. Elsewhere: in Tag Provisioning & Management a tag is a cellular device that appears on its own and has no space.

Tag profile

The configuration a tag receives — how often it reports, how it behaves, which firmware it runs. Several tags share a profile, so a change reaches all of them.

Tenant

An isolated organizational unit. Users, groups, spaces, devices, assets and tags always belong to exactly one tenant, and no data is visible across tenants.

User

A single person with an account. Which applications and which spaces they see follows from their roles.