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 action details \[1] you have mulitple options for installing litmus edge depending on your specific requirements the most common scenarios are installing on a physical hardware device such as an ipc (industrial pc) as a vm (virtual machine) you can install as a vm using oracle virtualbox, vmware esxi, vmware workstation player, qemu emulator kvm, and windows hyper v on docker on kubernetes see installation and deployments docid\ jffvzu 4clizx75qr5r3 to learn more \[2] after installing litmus edge, you can customize the setup of the instance to your specific requirements \[2a] 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 interfaces docid iedsujv4gn1cvlgrdome to learn more \[2b] 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 servers docid\ pgzwsr3dtjm4dgl2x93ab to learn more \[2c] 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 servers docid\ pgzwsr3dtjm4dgl2x93ab to learn more \[3] once litmus edge is installed and configured properly, you can start adding devices and tags in devicehub \[3a] see connect a device docid\ pal6abpzbrimdu9lvgj30 to learn how to connect devices to devicehub review the industrial systems connection guide docid\ er7j0mogtlktbxyupdcd to see the list of available drivers and compatible plcs/devices \[3b] add tags docid\ xgwokqbtpevii7or82ll0 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 \[4] you have several options to process, visualize, and analyze the polled and normalized data create and manage data flows 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 manager docid\ jghnqyhxbik8x2nhh5vte to learn more create and manage analytics flows & models analytics docid 8aloe 5 c9ubqjsw0ppcx 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 visualize and analyze data with marketplace applications 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 applications docid\ iipan4olp8rqznjc q8br and applications guides docid 1plxngagcprclgz6enlpo to learn more integrate connector to third party systems 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 integration docid\ smmzyvhcv ehvv8rguyb7 and integration guides docid\ wj0qnhw9mgsjhho1eevjj to learn more add an opc ua hierarchy 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 server docid\ howgx4pvvvi0kd9emj5 p to learn more customize systems customize settings such as security, network, user, and other settings to protect the integrity of your edge instance see the options in the system docid\ ng1bptexkjoaxu8q4f ph section of litmus edge to learn more