User Journey

The diagram below displays the most common user journey of the Litmus Edge experience. This journey can include multiple paths and you are welcome to combine these as you see fit.

You have multiple options for installing Litmus Edge depending on your specific requirements. The most common scenarios are installing:

See Installation and DeploymentsInstallation and Deployments to learn more.

After installing Litmus Edge, you can customize the setup of the instance to your specific requirements.

The Litmus Edge software package installation includes a default configuration for the selected device's interface. You must configure the default entries with your own network information. See Configure Network InterfacesConfigure Network Interfaces to learn more.

The Litmus Edge software package installation includes a default configuration for the Fallback DNS Resolvers that is only suitable for the open Internet. You must delete and replace the default entries with your own network information. See Configure DNS/NTP ServersFallback DNS Resolvers to learn more.

The Litmus Edge software package installation includes a default configuration for the NTP server ports that is only suitable for the open Internet. You must delete and replace the default entries with your own network information. See Configure DNS/NTP ServersNTP Servers to learn more.

Once Litmus Edge is installed and configured properly, you can start adding devices and tags in DeviceHub.

See Connect a DeviceConnect a Device to learn how to connect devices to DeviceHub. Review the Industrial Systems Connection GuideIndustrial Systems Connection Guide to see the list of available drivers and compatible PLCs/devices.

Add a TagAdd Tags to the connected device to subscribe to that device's data by register. For example, you may tag the PLC registers that contain the current temperature and vibration values. The data is collected with the frequency you define, automatically normalized, and published to the internal Message Broker. This data becomes available to both internal and external entities.

You have several options to process, visualize, and analyze the polled and normalized data.

Flows allow you to view device data and configure the output so you can better visualize how the device is operating. For example, subscribe to a tag that provides temperature values, average the temperature values per hour, and then publish the average values to the Message Broker. Then add a function that monitors the published average temperatures and raises an alarm if the value exceeds a predefined threshold. See Flows ManagerFlows Manager to learn more.

AnalyticsAnalytics are used to create flows. You can add input, function, and output instances, and then connect them. The flows can use KPIs or Machine Learning models. For example, apply out-of-the-box Compliance and Loss or Production Cycle KPIs to the data obtained from the Message Broker. Then publish the results to another tag at the Message Broker. Alternatively, submit the data to a pre-trained TensorFlow machine learning model and use the resulting predictions for decision making.

You have access to a default set of applications in a Public Marketplace. You can add your own Docker container-based applications in a Private Repository. See ApplicationsApplications and Applications GuidesApplications Guides to learn more.

You can configure connectors to connect to cloud services. This allows you to publish data from an edge device directly to a cloud service provider or database. See IntegrationIntegration and Integration GuidesIntegration Guides to learn more.

The OPC UA protocol provides a publish-subscribe client server technology for reliable data transmission. You can add your edge devices and tags in a hierarchy. See OPC UA ServerOPC UA Server to learn more.

Customize settings such as security, network, user, and other settings to protect the integrity of your edge instance. See the options in the SystemSystem section of Litmus Edge to learn more.