ExoSense Terminology¶
| Term | Definition |
|---|---|
| Asset | A digital representation of a physical system or machine, i.e. a Digital Twin. Assets have streaming data (Signals) to store sensor and status information from the physical world. Assets also have content files, meta information, and links. devices. Information about Rules |
| Signal | Individual piece of data for an Asset (Digital Twin) that has a real time and historical (time series) component associated it in addition to data unit, data type, and other properties. Typically sourced from IoT connected device channels. Information about Signals |
| Device | Also: IoT Device, Connected Device, Edge Device. Electronic hardware with ability to send data, an IoT connected device. The connected thing that is measuring a sensor or asking for data (e.g. fieldbus) for a physical data. It is typically connected via IP (internet protocol) unless an advanced use case that includes a gateway that talks on behalf of the devices. |
| Channel | Stream of data from an IoT connected Device (e.g., sensor data, status codes, event data), that will be consumed by Asset Signals. |
| Gateway | A gateway typically is an IoT edge device that handles protocol conversion (fieldbus to cloud, sensor interface to cloud). There are some use cases where a Gateway is truly a pass-thru for identifiable connected IoT devices. A gateway can also be a piece of software in the cloud that handles protocol conversion. Please contact Exosite for more information about custom Gateway talk-on-behalf-of applications where the devices do not have ability to connect using IP. |
| Dashboard | A visualization associated to an asset, group, or private use that displays 'panels' which represent assets and asset signals in various visualizations. ExoSense Dashboards Information |
| Insights | Real-time and continuous stream functions that are inserted into the Asset Signal data pipeline, of type transform (analytics), rule, or action. Custom Insights are supported. Information about Insights |
| Rule | Signal pipeline workflow logic that has the ability to detect states of a signal. Output is a state event, which affects the state of a signal and the asset. Rule events (state changes) are written to the asset log. Information about Rules |
| Transform | Also Transformation Signal pipeline workflow logic that has the ability to perform operations or other functions on Asset signal data. Output of a transformation is a secondary signal that has it's own properties. Information about Transforms |
| Content | Files and content associated to an Asset. Can be uploaded by a device or a user. Asset Content Information |
| Asset Template | A template of the digital Asset that can be used to create and update many assets to use the same signals, transforms, rules, dashboards, and other functionality of the Asset. Asset Templates |
| Asset Type | A collection of Assets that contain similar key metrics, when viewed as a fleet or group of assets. Typically representing similar type of equipment or machines, a product model, etc. Asset Templates |
| User | Any user that can log into ExoSense using email/password for authentication. All users have a User Role and are assigned to a group node in the group hierarchy. User Roles and Permissions |
| Group | A node in a permission hierarchy that contains assets, users, devices, subgroups, and group dashboards. Can represent any combination of regions, customers, sites, locations, or other organizational structures. Group / Hierarchy Management |
| Role | A role is given to a user that defines what functionality they have access to in ExoSense. A role is a list of permissions. User Roles and Permissions |
| Permission | A specific function that a User Role can perform within the application. User Roles and Permissions |