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. Digital Twin Assets are collections of information, namely signals sourced from connected equipment, rules on those signals, digital content about the Asset, and dashboard visualizations.

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¶

ExoSense® is based around the concept of users interacting with digitalized Assets in the application, i.e. Digital Twins. These assets represent real-world systems, machines, and equipment and can include data timeseries signals, metadata, conditional rules, uploaded content files, and visualization dashboards.

Assets Overview

IoT Devices & Sources¶

ExoSense also has a concept of Devices to represent sources of data, namely IoT edge devices but also data sources may also be integrated from other device data clouds and services. ExoSense allows viewing and managing devices for installation, assigning ownership, and allowing data to be mapped to Assets.

Device sources may be mapped to to assets in 1 to 1, many to 1, and 1 to many scenarios. The application is flexible for different types of IoT sources.

Managing Devices Connecting Devices

Data Flow¶

Assets are a collection of signals, streams of data being acquired through a IoT edge or other sources. A root signal is sourced from a IoT identity channel, which are typically from IoT edge devices (sensors, etc) but may also be from other data from third-party integrations. Assets may source data from 1 or more edge IoT devices and/or data integrations.

Streaming Data: Signals

These signals, which are defined as a data type and unit in some cases, may then be used through the ExoSense application. Signals are a part of the data pipeline. This pipeline allows Transform, Rule, and Action functions to be added to handle additional streaming data processing and event creation.

Signals Overview

File Upload: Content

Content files can be uploaded from IoT edge devices also, this is mapped to Assets and stored as content under the asset. These files are available for download and visualizations on dashboards.

Content Overview

Requirements¶

Deploying / Running¶

ExoSense is both a web browser based application (front end) and a backend solution that handles all of the data flow, data storage, rules, and API functionality. ExoSense is hosted and runs as an application from the Exosite Murano IIoT Platform (Exosite Cloud, Dedicated Cloud, or On Prem) and uses Murano's services such as IoT Connectors, databases, script engine, web-service, websocket, web asset hosting, and other micro-services.

Individual ExoSense solutions are deployed as their own instances from with-in a user's Exosite business account in Murano. Each instance has it's own URL, branding, users, assets, hierarchy and data storage.

IoT Connectors¶

ExoSense supports data from IoT edge devices or from federated device clouds via a Murano IoT Connector's device events, using a common schema for mapping channels to Asset Signals. For devices connected to other clouds or device platforms, or that sends data in a different format, a Murano IoT Connector may be created to handle the translation into the proper data events and schema.

Connecting a Device - Guide IoT Connectors

Channels - Represent a stream of data for a unique parameter like a temperature sensor or a status read from a register or a true/false boolean value from another part of the machine. Channels are unique streams of data. Note: Channels may be used for bidirectional communication, such as a control request.

Content Files - Devices may upload content files which may be a log for helping troubleshoot the IoT device itself or for high resolution data captures of sensor data.

Configuration¶

Branding¶

ExoSense allows administrators to brand the application with their logo, name, and color schemes. Additional configuration and feature controls are available.

Administration Theme Configuration

Users and Access Controls¶

ExoSense supports a group hierarchy for building out access controls to groups of assets. Users are assigned a role and a group for their access to the solution.

Group Hierarchy Overview User Management Overview

Browser Support¶

ExoSense's user interface 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.

Mobile / Tablets¶

The ExoSense web application uses the concepts of Response Web Design to render the application interface on all screen-sizes and resolutions. This includes using with browsers on medium to small touchscreen based devices like smart mobile phones and tablets. ExoSense will work on device browsers such as iPhone iOS (Safari, Chrome), iPad iPadOS (Safari), and Android OS (Chrome).

Touchscreen Mobile Phone

Touchscreen Tablet