ExoSense® Overview¶
ExoSense® is an end-to-end solution for remote monitoring applications that need to gather data from sensors, machines, PLCs, legacy controls, etc. It enables OEMs, Distributors, and System Integrators to provide customers with a branded and configurable application to go with connected devices and sensors.
Users are able to view machine and sensor data and insights, build dashboards, receive notifications on state condition changes, manage user access, generate reports, and manage their account.
OEMs and System Integrators are able to build and configure the application to look and feel like their own product, create integrations, and manage organization group hierarchy.
What is ExoSense?¶
ExoSense is a condition monitoring application that runs on top of IoT Platform services. It is highly configurable and supports a wide range of assets and application types - from factory equipment to remote monitoring of machines to mobile vehicles.
ExoSense is deployed as whitelabel instances, meaning users manage it as their own product offering, creating a hierarchy of customers and partners that control permission levels.
Digital Assets are collections of signals sourced from connected equipment, rules on those signals, digital content about the Asset, and dashboard visualizations.
Digital Assets¶
ExoSense® focuses around the concept of users interacting with digitalized Assets in the application.
These assets represent real-world systems, machines, and equipment. Data signals, historical data, conditional rules, notifications, and permissions revolve around the concept of an asset. Assets are a collection of signals and those signals can come from various devices. The Digital Asset Objects do not need to be the same as the physical IoT Devices, which provides flexibility when setting up the system.
Data Flow¶
Terminology¶
| Term | Definition |
|---|---|
| Asset | Digital Twin virtual representation of a physical system or machine. Signals are associated to an Asset. Signals under and Asset can include data from one or many connected devices. |
| Channel | Stream of data from an IoT connected device (e.g., sensor data, status codes, event data), that will be consumed by Assets (Digital Twins). |
| Dashboard | A visualization associated to an asset, group, or private use that displays 'panels' which represent assets and asset signals in various visualizations. |
| Device Also: Connected 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. |
| ExoEdge | Exosite's gateway and device software to help integrate edge devices to Murano and ExoSense. |
| ExoSense | Exosite's remote condition monitoring solution that runs on top of Murano. |
| Gateway | Typically a one to one relationship with the term Device, but there are some use cases where a Gateway is truly a pass-thru for identifiable connected IoT devices. 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. |
| Insights | Real-time and continuous stream analytics that work as an asset transformation. Custom Insights are supported. |
| Murano | Exosite's IoT Platform. See https://exosite.com/iot-platform/ |
| 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. |
| 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. |
| Signal Transform | 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. |
| 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. |
Requirements¶
Browser Support¶
ExoSense runs as a web application in a web browser on top of an IoT and application platform. The following tables list typical browsers and whether they are supported by ExoSense.
Computers / PCs¶
| Browser | ExoSense Support | Notes / Recommendations |
|---|---|---|
| Google Chrome | Supported | Recommended browser |
| Mozilla Firefox | Not Supported | Can be used but is not validated or tested. |
| Apple Safari | Not Supported | Can be used but is not validated or tested. |
| Microsoft Edge (Chromium Version) | Supported | Tested and validated. |
| Microsoft IE version 11 | Not Supported (As of Oct, 2019) | Recommend Microsoft Edge or Microsoft Edge built on Chromium |
Mobile / Tablets¶
The ExoSense web application supports small touchscreen based devices, i.e. smart mobile phones and tablets. These devices have many browsers that can be installed and run on them, ExoSense has been built to run on small touchscreens and has been validated on specific devices/browsers such as iPhone iOS (Safari, Chrome), iPad iPadOS (Safari), and Android OS (Chrome). The functionality for small screens has been limited for user experience reasons, these details can be found below.
| Device Screen Size | ExoSense Support | Notes / Recommendations |
|---|---|---|
| Touchscreen Tablet Size | Supported (BETA) v2.29.0 | Touchscreen sizes: 600 pixels < width < 960 pixels Dashboard Viewing: All panels are full width Disabled Functionality:
|
| Touchscreen Mobile Phone Size | Supported (BETA) v2.29.0 | Touchscreen sizes: 360 pixels < width < 600 pixels Dashboard Viewing: All panels are full width Disabled Functionality:
|
Native mobile apps¶
ExoSense currently does not have any native mobile OS applications. Please contact support or sales for needs in this area to discuss future roadmap.