IoT CygNet Link EIE Data Flow

Data flows to and from the IoT CygNet Link EIE in the following configuration, and the whole system may span multiple enterprise products, multiple computers, and multiple operating systems.

IoT CygNet Link EIE – Data Flow

From left to right:

• The Target system is a CygNet Enterprise instance configured with an IoT CygNet Link EIE device, with standard data groups to Get (DG_F_DEV) and Send (DG_T_DEV) UIS commands with the appropriate parameters to the MQTT server and then to Weatherford Link. The IoT CygNet Link EIE uses the MQTT Comm EIE to communicate with the MQTT server.
• The CygNet Enterprise issues a data group-driven UIS command to publish and subscribe to a payload sent to and retrieved from the MQTT Server. The MQTT server then forwards the payload to Weatherford Link.
• Weatherford Link sends the payload (the UIS command) to CygNet on the Edge device with the provided parameters. In a production environment, the Weatherford Link instance would normally be running in the same location as the source CygNet UIS, although that is not required. CygNet on the Edge has no knowledge of Weatherford Link.
• The Source system is running a CygNet on Edge instance configured with an appropriate device protocol to communicate with the Remote Device (e.g., an eProdRPC EIE or other EIE). The CygNet on Edge DDS and UIS will have the same data groups and commands as the CygNet Enterprise DDS and UIS and will get and send UIS commands to one or more remote devices (e.g., WellPilot RPOC or other RTU type) to poll DynaCards and other configuration or information data groups.
• CygNet running on the Edge polls the Remote Device, issues a command to the RTU, creates new DynaCard or other transactions, and updates statistics points. Weatherford Link then publishes any new transactions from CygNet on the Edge to the MQTT server. The MQTT server sends the DATA payload back to the CygNet Enterprise, which then processes the payload and saves the DynaCard transactions and other polled data completing the data flow round trip.

Each device in the source Edge UIS should have one or more facility links set for one or more configuration data groups. This may reflect the way devices are setup in the Edge device where the Well facility is not the same as the Device facility. All facilities in the Edge UIS should have a SYFACINFO point and other common statistics points (e.g., SYCSSTN - Total succ polls, etc.) configured.