--- title: User Journey slug: litmusedge/overview/user-journey description: Review a typical user journey of installing, deploying, and configuring Litmus Edge. docTags: createdAt: 2022-03-30T21:22:08.000Z --- *** 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. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/899b-XC6ZI8Eoz8BPadLA_le-user-journey.png" size="80" width="11488" height="9895" darkWidth="11488" darkHeight="9895" position="flex-start" showCaption="false"} ## 1. Installation You have multiple 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. Instance Setup After installing Litmus Edge, you can customize the setup of the instance to your specific requirements. ### 2a. Network Interfaces 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. Fallback DNS Resolvers 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. NTP Servers 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. DeviceHub Setup Once Litmus Edge is installed and configured properly, you can start adding devices and tags in DeviceHub. ### 3a. Connect a Device 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 [Add a Tag](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. Process and Visualize Data 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 and 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 Connectors 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 System Settings 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.