Glossary

This section describes the terms that make up the Live Systems Data services platform.

General terms

Asset

A representation of a real-world object containing a visual model and associated data. Assets can also be aggregations of other assets. For example:

• A sensor
• A device containing many sensors
• An equipment composed of many devices and sensors
• A facility hosting many pieces of equipment

Data association

A mechanism for establishing relationships between entities in the platform. For example:

• The connection between an entity's 3D model and its data points
• The connection between two sensors that are part of the same equipment

Data connector

A platform component that enables the link between Live Systems Data services and an external data source. Connectors translate data formats used by external sources and provide normalized sets to be used by other platform components.

Data point

An individual source for the data provided to the Live Systems Data services platform. It can be a single source or part of a larger set for a given data source.

Data source

A system that provides the data ingested by the Live Systems Data services platform.

Data sources can expose one or more data points at once. They can also provide data that's close to a real-world object, like an IoT device, or a higher-level data aggregator, like an IoT hub, a database, or a cloud service.

Device

A mechanical or electronic contrivance which reports telemetry from one or more sensors.

Entity

A concept used to model individual elements handled by the platform, like assets and data points.

External system

Any data source that isn't a component of the Live Systems Data services platform. External systems are integrated into the platform through data connectors.

Facility

A digital twin of a real-world building or location, like a factory or airport. Facilities contain many assets and are themselves considered an asset, being the primary subject of the Operational Twin scenario.

Facility data simulator

A data source that simulates a facility and its data points to generate synthetic data sets used for the development and testing of solutions built with the Live Systems Data services platform.

Knowledge graph

A graph-based data structure that represents a network of entities and their relationships to one another.

Operational Twin

A digital twin scenario that captures and visualizes the operational state and behavior of real-world assets. It is the main focus for Live Systems Data services. It covers the remote monitoring of facilities and the visualization of their 3D models and associated data.

Ontology

A semantic data model represented as a knowledge graph that describes specific entities and relationships that exist within a given knowledge domain.

Relationship

An element of the knowledge graph that defines how entities are tied together.

Sensor

A data point that provides real-world information about assets. It's typically the source of telemetry like temperature, speed, and other information referred to as IoT data.

Telemetry

An unending source of real-time information reported by a sensor, such as temperature, speed, and other information referred to as IoT data.

Alert rule terms

Action

The details from the alert message. Includes the title and description.

Created at

A timestamp of when the alert rule was created.

Evaluation interval value

How often the alert rule is evaluated by default.

Evaluation interval unit

Unit of measurement for the Evaluation Interval. Can be in milliseconds, seconds, minutes, hours, days, weeks, or years.

Expression

The property and values of the evaluational expression that monitors and triggers the alert. Must be in JSON format.

ID

The Globally Unique Identifier (GUID) of the alert rule represented in the same row.

Is disabled

A boolean that represents whether or not an alert is disabled. Disabled alerts aren't monitored or triggered.

Name

The name of the alert rule. Unlike the GUID, this value doesn't have to be unique.

Severity

An identifier that represents the priority of the alert. Severity values must be defined within the user application.

Trigger delay value

The time between the conditions of the alert being met and the alert being sent.

Facility simulator terms

Data Source

The content of the telemetry data that was sent.

Device (facility simulator)

The representation of the behavior of a device in the simulated scenario. Made up of the device IDs, a schedule of how frequently telemetry data is sent, a data source with telemetry data content, and the configuration used by the TelemetrySink.

Facility (facility simulator)

A virtual representation of a physical facility.

Scenario

A collection of devices operating in the same facility. Scenarios can be executed to generate simulated IoT telemetry data for the facility. You can only execute one scenario for a specific facility at a time.

Schedule

List of time intervals that determine when the device sends telemetry data. Can be configured to stop after sending a limited amount of events or to continue sending events indefinitely.

Telemetry Sink

Consumer of the telemetry generated by a simulated device. The TelemetrySink is often an IoT service in one of the cloud providers.

Workspace

A collection of facilities owned by the same organization.

Data association terms

3D object

A particular 3D object within a model and/or scene.

Association

The creation of a 1:1 relationship between a source device and a 3D object. Association can be accomplished by executing a specific rule or by executing all automated rules.

Building Information Modeling objects

A scene and/or 3D object with CAD software is comprised of many Building Information Modeling (BIM) objects. These BIM objects contain both geometric (3D and 2D) and non-geometrical data and allow you to define custom properties for each 3D model. You can export this information from the CAD software for use in third-party applications, such as the Live Systems Data services platform.

For example, in a scene that contains wind turbines, each turbine can have its manufacturer, model, and serial number defined in the BIM objects.

Custom properties

Key-value pairs defined by the user on a 3D object. They are used by a rule to establish a relationship between a source device and a corresponding 3D Object and/or game object within the application.

Disassociation

The removal of the relationship between a source device and a 3D object. Disassociation can be accomplished by executing a specific rule or by executing all automated rules.

Rule

A user-defined way of creating a relationship between source devices and a 3D object within the application. You can define rules to be run manually or configure them to run automatically. Currently, only direct mapping and regular expression rules are supported.

Rule interpreter

A system that understands how to execute rules of a particular type against a set of source devices and a 3D object. Currently, only direct mapping and regular expression rules are supported.

Source device

A physical device which reports telemetry from one or more sensors.