--- title: System Architecture slug: litmusedge-v1/overview/system-architecture description: Learn more about the system architecture of Litmus Edge. docTags: createdAt: 2022-03-30T21:21:47.000Z --- Review the following information to learn more about the system architecture and network architecture of Litmus Edge. # System Architecture The diagram below shows the system architecture of Litmus Edge and the different paths that data can travel through Litmus Edge. ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/t5F6FhjgM77Tp4JK5Jg2Q_image.png "System Architecture") **\[1] **You have the option of accessing Litmus Edge through the Web UI, the Terminal User Interface (TUI), or REST API. See the following to learn more: - [Access the Litmus Edge Web UI](docId\:tGtrj9DEH1W_ro24kmbmQ) - [Access the Terminal User Interface](docId\:R1Lz44wFFv3H9Jg33NWlP) - [Litmus API Portal Overview](docId\:kNxgkk_CsgYpYpHe1DE7l) **\[2] **To get data into Litmus Edge, you will need to configure a connection between PLCs and DeviceHub drivers. Review the list of available drivers and the parameters that need to be configured in the [Industrial Systems Connection Guide](docId\:x7F6RogWGUb9AiJkZ8aFr). Once the data flows into DeviceHub, it is sent to the message broker for further processing. **\[3]** Once the data reaches the message broker, there are different paths the data can flow. - You can store the data in a database. Learn more about database options for Litmus Edge in [DataHub](docId\:z0j1tmAAzK3kPvGFNmvHL). - There are different options for the data to flow northbound for further processing. \[4] You can send the data northbound to the following: - You can send the data through an application in Litmus Edge. Learn more about [Applications](docId\:j4jhjBWbwQY1BS9A3G6Zk) and [Applications Guides](docId:-DKHmS9kYfUcfLPohUyk2). - Create flows in the [Flows Manager](docId\:qCWlxV4BmMR13WWIsoI89). - Process the data in [Analytics](docId\:FGJKbOQwGVGgd2nuQgRo5). - Integrate Litmus Edge with other applications for Cloud and DB Connectivity. Learn more about [Integration](docId\:Wpqo1fE02tmx3AsKewQU6) and [Integration Guides](docId\:ZJCZ7NP6pGLZGihEVl8Ed). - Configure an [OPC UA Server](docId\:Wu741skertOa8mwl1IpBY). # Network Architecture The diagram below shows the typical network architecture for Litmus Edge. Refer to the callouts in the diagram and descriptions below to learn more. ![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/bdP8pWgkZbLddmMBe7hf5_network-architecture.png "Litmus Edge Typical Network Architecture") ## Options for Setting Up Litmus Edge You have the following options for setting up Litmus Edge on your site. Learn more about [Installation and Deployments](docId\:kfV1aRRRlYrgPLszg75gl). ### Option 1 Refer to callout **\[1]** in the diagram. - Litmus Edge in a DMZ is connected to PLCs through a Level 2 switch. - Only the "Head" PLC has a network connection in a designated VLAN. - The Litmus Edge in the DMZ must have access to the same VLAN as the "Head" PLC. - The Litmus Edge in the DMZ can read from registers of the "Head" PLC. - Other PLCs attached to the "Head" PLC must transfer their data to the "Head" PLC to be read. ### Option 2 Refer to callout **\[2]** in the diagram. - Litmus Edge in a DMZ is connected to PLCs through a Level 2 switch. - All PLCs have a network connection in a designated VLAN. - The Litmus Edge in the DMZ must have access to the same VLAN as the PLCs. - The Litmus Edge in the DMZ will be able to connect to all PLCs to read data. ### Option 3 Refer to callout **\[3]** in the diagram. - Litmus Edge in a DMZ is connected to other data sources through a Level 2 switch. - All data sources have a network connection in a designated VLAN. - The Litmus Edge in the DMZ must have access to the same VLAN as the data sources. - The Litmus Edge in the DMZ will be able to connect to all data sources to read data. ### Option 4 Refer to callout **\[4]** in the diagram. - Litmus Edge in a DMZ is connected to a PLC through a panel switch. - The panel switch is connected to a Level 2 switch. - The PLC is connected to the panel switch. - The Litmus Edge in the DMZ must have access to the same VLAN as the PLC. - The Litmus Edge in the DMZ will read data from any PLC connected to the panel switch. ### Option 5 Refer to callout **\[5]** in the diagram. - An RS232 to Ethernet converter connects to a PLC through an RS232/484 physical connection. - Litmus Edge can read from the registers on the connected PLC. - The Litmus Edge in the DMZ will read the data from the PLC through the Ethernet converter. ### Option 6 Refer to callout **\[6]** in the diagram. - Litmus Edge in a DMZ connects to a Remote I/O Module/Sensor Gateway. - The Remote I/O Module/Sensor Gateway is connected to the PLC (or in some cases to the Level 2 switch). - Sensors are connected to the gateway through wireless or proprietary technology. - The Litmus Edge reads sensor data through the PLC or through the gateway if it's connected to the Level 2 switch. ## Cloud and Litmus Edge Manager Setup Refer to the following options for setting up cloud storage and Litmus Edge Manager. ### Litmus Edge Manager Refer to callout **\[7]** in the diagram. Data collected from Litmus Edge is sent to [Litmus Edge Manager](https://docs.litmus.io/edgemanager) for consolidation. ### Cloud Storage Refer to callout **\[8]** in the diagram. Litmus Edge Manager sends data to cloud systems or other enterprise systems. Learn more about [Applications](docId\:j4jhjBWbwQY1BS9A3G6Zk) and [Applications Guides](docId:-DKHmS9kYfUcfLPohUyk2). ### Integrations Refer to callout **\[9]** in the diagram. Litmus Edge can also send data directly to cloud systems/other enterprise systems through integrations. Learn more about [Integration](docId\:Wpqo1fE02tmx3AsKewQU6) and [Integration Guides](docId\:ZJCZ7NP6pGLZGihEVl8Ed).