APPARATUS AND METHOD FOR USING DISTRIBUTED SYSTEM ARCHITECTURE (DSA) IN INTERNET OF THINGS (IOT) EDGE APPLIANCES

IoT edge appliances with DSA integrate cloud and industrial networks, addressing the scalability and security issues of SCADA and DCS systems by enabling secure, uniform data exchange and analysis across distributed industrial environments.

JP7584386B2Active Publication Date: 2024-11-15HONEYWELL INTERNATIONAL INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2021162750
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2015-12-08
Filing Date
2021-10-01
Publication Date
2024-11-15
Estimated Expiration
2036-11-14

AI Technical Summary

Technical Problem

Existing SCADA and DCS systems face challenges in scaling out and distributing over long distances while maintaining secure communication with cloud networks in industrial process control and automation systems.

Method used

Implementing IoT edge appliances with distributed systems architecture (DSA) that integrate with cloud networks and industrial process control systems, enabling secure communication and data exchange using Global Data Access (GDA) methods, and supporting both SCADA and DCS systems with local human-machine interfaces and mobility services.

Benefits of technology

Enables scalable and secure communication between cloud networks and industrial systems, facilitating uniform data analysis and control across distributed environments without additional hardware, ensuring data coherence and security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007584386000001
    Figure 0007584386000001
  • Figure 0007584386000002
    Figure 0007584386000002
  • Figure 0007584386000003
    Figure 0007584386000003
Patent Text Reader

Abstract

A method for safely operating a supervisory control and data acquisition (SCADA) system and a distributed control system (DCS) by scaling out and distributing the SCADA system and DCS, an IoT edge appliance, and a non-transitory computer-readable medium are provided. [Solution] The method includes receiving a configuration signal to configure an IoT edge appliance (160) to communicate with at least one of a first device (164) on a cloud network (162) or a second device (102a) on an industrial process control and automation system network (104), configuring a communication link with the cloud network (162) and the industrial process control and automation system network (104), and communicating data with at least one of the first device (164) on the cloud network (162) or the second device (102a) on the industrial process control and automation system network (104).
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001]

[0001] The present disclosure is directed generally to distributed system architectures (DSA) and, more particularly, to implementing Internet of Things (IoT) edge appliances in DSAs in industrial process control and automation systems. [Background technology]

[0002] DSA is a technology that is used to scale out supervisory control and data acquisition (SCADA) systems and distributed control systems (DCS) and to support distributed systems over long distances. The DSA system can be configured to run these SCADA and DCS systems securely through the cloud. Summary of the Invention

[0003]

[0003] The present disclosure relates to apparatus and methods for using Internet of Things (IoT) edge appliances in industrial process control and automation systems.

[0004] In a first embodiment, a method is provided. The method includes discovering, by an Internet of Things (IoT) edge appliance, a communication link with a cloud network and an industrial process control and automation system network. The method includes receiving, by the IoT edge appliance, a configuration signal that configures the IoT edge appliance to communicate with at least one of a first device on the cloud network or a second device on the industrial process control and automation system network. The method includes configuring, by the Internet of Things (IoT) edge appliance, a communication link with a cloud network and an industrial process control and automation system network. Further, the method includes communicating, by the IoT edge appliance, data with at least one of the first device on the cloud network or the second device on the industrial process control and automation system network.

[0004]

[0005] In a second embodiment, an IoT edge appliance is provided that includes a processing circuit. The processing circuit is configured to receive a configuration signal that configures the IoT edge appliance to communicate with at least one of a first device on a cloud network or a second device on an industrial process control and automation system network. The processing circuit is also configured to configure a communication link with the cloud network and the industrial process control and automation system network. The processing circuit is further configured to communicate data with at least one of the first device on the cloud network or the second device on the industrial process control and automation system network.

[0005]

[0006] In a third embodiment, a non-transitory computer readable medium is provided that stores one or more executable instructions. The one or more executable instructions, when executed by one or more processors, cause the one or more processors to discover a communication link with a cloud network and an industrial process control and automation system network. The one or more executable instructions, when executed by the one or more processors, cause the one or more processors to receive a configuration signal that configures the IoT edge appliance to communicate with at least one of a first device on the cloud network or a second device on the ... The executable instructions, when executed by the one or more processors, cause the one or more processors to configure a communications link with a cloud network and an industrial process control and automation system network. Further, the one or more executable instructions, when executed by the one or more processors, cause the one or more processors to communicate data with at least one of a first device on the cloud network or a second device on the industrial process control and automation system network.

[0006]

[0007] Other technical features will be readily apparent to those skilled in the art from the following figures, descriptions, and claims. [Brief description of the drawings]

[0007]

[0008] For a more complete understanding of the present disclosure, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which: [Figure 1] FIG. 1 illustrates an example of an industrial process control and automation system according to the present disclosure. [Diagram 2] FIG. 2 illustrates details of an example IoT edge appliance according to the present disclosure. [Diagram 3] FIG. 3 illustrates an example method according to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008]

[0012] The figures discussed below, and the various embodiments used to illustrate the principles of the invention in this patent document, are merely exemplary and should in no way be construed as limiting the scope of the invention, as those skilled in the art will understand that the principles of the invention may be implemented in any type of appropriately configured device or system.

[0009]

[0013] Distributed System Architecture (DSA) allows SCADA systems and DCS to be both scaled out and distributed over long distances. By incorporating DSA capabilities into Internet of Things (IoT) edge appliances, the IoT edge appliances can, for example, integrate applications, big data storage, and communication between the IoT cloud network and on-premise devices that use DSA capabilities (such as sensors, actuators, controllers, human-machine interfaces (HMIs), and on-site applications). This makes it possible.

[0010]

[0014] FIG. 1 illustrates an example of an industrial process control and automation system 100 according to the present disclosure. As shown in FIG. 1, the system 100 includes at least one product or The system 100 may include various components that facilitate the production or processing of products or other materials. For example, the system 100 is used herein to facilitate control over components in one or more plants 101a-101n. Each plant 101a-101n represents one or more processing facilities (or one or more portions thereof), such as one or more manufacturing facilities for producing at least one product or other material. In general, each plant 101a-101n may implement one or more processes and may be individually or collectively referred to as a process system. A process system generally refers to any system or portion thereof configured to process one or more products or other materials in some manner.

[0011]

[0015] In FIG. 1, the Purdue model of process control is used to implement the system 100. In the Purdue model, "Level 0" can include one or more sensors 102a and one or more actuators 102b. The sensors 102a and actuators 102b represent components in a process system that can perform any of a wide variety of functions. For example, the sensor 102a can measure temperature, pressure, or A wide variety of characteristics in the process system can be measured, such as flow rate. Also, the actuators 102a can change a wide variety of characteristics in the process system. The sensors 102a and actuators 102b can represent any other or additional components in any suitable process system. Each of the sensors 102a includes any suitable structure for measuring one or more characteristics in the process system. Each of the actuators 102b includes any structure that operates on or affects one or more conditions in the process system.

[0012]

[0016] At least one network 104 is coupled to the sensors 102a and the actuators 102b. The network 104 facilitates interaction with the sensors 102a and the actuators 102b. For example, the network 104 transports measurement data from the sensors 102a and provides control signals to the actuators 102b. Network 104 may represent any suitable network or combination of networks. As specific examples, network 104 may represent an Ethernet network, an electrical signal network (such as a HART or FOUNDATION FIELDBUS network), an air control signal network, or any other or additional type(s) of network(s).

[0013]

[0017] In the Purdue model, "Level 1" may include one or more controllers 106 coupled to the network 104. Among other things, each controller 106 may use measurements from one or more sensors 102a to control the operation of one or more actuators 102b. For example, the controller 106 may receive measurement data from one or more sensors 102a and use the measurement data to generate control signals for one or more actuators 102b. Each controller 106 may include any structure suitable for interfacing with one or more sensors 102a and controlling one or more actuators 102b. Each controller 106 may represent, for example, a proportional-integral-derivative (PID) controller or a multivariable controller, such as a robust multivariable predictive control technique (RMPCT) controller, or other types of controllers implementing model predictive control (MPC) or other advanced predictive control (APC). As a particular example, each controller 106 may represent a computing device running a real-time operating system.

[0014]

[0018] Two networks 108 are coupled to the controller 106. The networks 108 facilitate interaction with the controller 106 by transporting data to and from the controller 106. The networks 108 may represent any suitable network or combination of networks. As a particular example, the networks 108 may represent a redundant pair of Ethernet networks, such as a FAULT TOLERANT ETHERNET (FTE) network from HONEYWELL INTERNATIONAL INC.

[0015]

[0019] At least one switch / firewall 110 couples network 108 to two networks 112. Switch / firewall 110 can transport traffic from one network to the other. Switch / firewall 110 can also block traffic on one network from reaching the other network. Switch / firewall 110 includes any structure suitable for communicating between networks, such as a HONEYWELL CONTROL FIREWALL (CF9) device. Network 112 can represent any suitable network, such as an FTE network.

[0016]

[0020] In the Purdue model, "Level 2" may include one or more machine-level controllers 114 coupled to the network 112. The machine-level controllers 114 perform various functions to support the operation and control of the controllers 106, sensors 102a, and actuators 102b, and may be associated with a particular piece of industrial equipment (such as a boiler or other machinery). For example, the machine-level controllers 114 may log information collected or generated by the controllers 106, such as measurement data from the sensors 102a or control signals for the actuators 102b. The machine-level controllers 114 may also monitor the operation of the controllers 106. The machine level controllers 114 may also execute applications that control the actuators 102b, thereby controlling the operation of the actuators 102b. Additionally, the machine level controllers 114 may provide edge access to the controllers 106. Each of the machine level controllers 114 includes any structure suitable for providing access to, controlling, and performing operations related to a machine or other individual equipment. Each of the machine level controllers 114 may represent, for example, a server computing device running a MICROSOFT WINDOWS operating system. Although not shown, different machine level controllers 114 may be used to control different equipment in a process system (each equipment associated with one or more controllers 106, sensors 102a, and actuators 102b).

[0017]

[0021] One or more operator terminals 116 are coupled to the network 112. The operator terminals 116 represent computing or communication devices that grant user access to the machine level controllers 114. The machine level controllers 114 can then grant user access to the controllers 106 (and potentially to the sensors 102a and actuators 102b). As a particular example, the operator terminals 116 can allow a user to review the operation history of the sensors 102a and actuators 102b using information collected by the controllers 106 and / or the machine level controllers 114. The operator terminals 116 can also allow a user to adjust the operation of the sensors 102a, actuators 102b, controllers 106, or machine level controllers 114. Additionally, the operator terminals 116 can receive and display warnings, alerts, or other messages or indications generated by the controllers 106 or the machine level controllers 114. Each of the operator terminals 116 includes any structure suitable for supporting user access and control of one or more components in the system 100. Each of the operator terminals 116 may represent, for example, a computing device running the MICROSOFT WINDOWS operating system.

[0018]

[0022] At least one router / firewall 118 couples the network 112 to two networks 120. The router / firewall 118 may be a secure router or a combination router / firewall. Network 120 may represent any suitable network, such as an FTE network, and includes any structure suitable for communicating between networks.

[0019]

[0023] In the Purdue model, "Level 3" includes one or more unit-level controllers 122 coupled to a network 120. Each unit-level controller 122 is typically associated with one unit in the process system and represents a collection of different machines that work together to accomplish at least a portion of the process. The unit-level controllers 122 perform various functions to support the operation and control of the components at the lower levels. For example, a unit-level controller 122 may The unit-level controllers 122 may record information collected or generated by components at one level, execute applications that control components at lower levels, and provide secure access to components at lower levels. Each of the unit-level controllers 122 may include any structure suitable for providing access to, controlling, and performing operations related to one or more machines or other equipment in a process unit. Each of the unit-level controllers 122 may represent, for example, a server computing device running a MICROSOFT WINDOWS operating system. Although not shown, different unit-level controllers 122 may be used to control different units in a process system (each unit being associated with one or more machine-level controllers 114, controllers 106, sensors 102a, and actuators 102b).

[0020]

[0024] Access to the unit-level controller 122 may be granted by one or more operator terminals 124. Each of the operator terminals 124 includes any structure suitable for supporting user access and control of one or more components in the system 100. Each of the operator terminals 124 may represent, for example, a computing device running the MICROSOFT WINDOWS operating system.

[0021]

[0025] At least one router / firewall 126 couples network 120 to two networks 128. Router / firewall 126 may include any structure suitable for communicating between networks, such as a secure router or a combined router / firewall. Network 128 may represent any suitable network, such as a FET network.

[0022]

[0026] In the Purdue model, "Level 4" may include one or more plant-level controllers 130 coupled to the network 128. Each plant-level controller 130 is typically associated with one of the plants 101a-101n, and each plant may include one or more process units implementing the same, similar, or different processes. The plant-level controllers 130 perform various functions to support the operation and control of the components at the levels below them. As a specific example, the plant-level controllers 130 may execute one or more manufacturing execution system (MES) applications, scheduling applications, or other or additional plant or process control applications. Each of the plant-level controllers 130 may include any structure suitable for providing access to, controlling, and operating in connection with one or more process units in a process plant. Each of the plant-level controllers 130 may represent, for example, a server computing device running the MICROSOFT WINDOWS operating system.

[0023]

[0027] Access to the plant-level controller 130 may be granted by one or more operator terminals 132. Each of the operator terminals 132 includes any structure suitable for supporting user access and control of one or more components in the system 100. Each of the operator terminals 132 may represent, for example, a computing device running the MICROSOFT WINDOWS operating system.

[0024]

[0028] At least one router / firewall 134 couples the network 128 to one or more networks 136. The router / firewall 134 may be a secure router or a combined router / firewall that provides communication between the networks. Network 136 may represent any suitable network, such as an enterprise-wide Ethernet or other network, or all or a portion of a larger network (such as the Internet).

[0025]

[0029] In the Purdue model, "Level 5" may include one or more enterprise-level controllers 138 coupled to the network 136. Each enterprise-level controller 138 may typically perform planning tasks for multiple plants 101a-101n and control various aspects of the plants 101a-101n. Additionally, the enterprise-level controllers 138 may perform various functions to support the operation and control of components in the plants 101a-101n. As specific examples, the enterprise-level controllers 138 may execute one or more command processing applications, enterprise resource planning (ERP) applications, advanced planning and scheduling (APS) applications, or any other or additional enterprise control applications. Each of the enterprise-level controllers 138 may include any structure suitable for providing access to, controlling, and performing operations related to the control of one or more plants. Each of the enterprise-level controllers 138 may represent, for example, a server computing device running the MICROSOFT WINDOWS operating system. In this document, the term "enterprise" refers to an organization having one or more plants or other processing facilities to be managed. Note that if a single plant 101a is to be managed, the functionality of the enterprise-level controller 138 may be incorporated into the plant-level controller 130.

[0026]

[0030] Access to the enterprise-level controller 138 may be granted by one or more operator terminals 140. Each of the operator terminals 140 includes any structure suitable for supporting user access and control of one or more components in the system 100. Each of the operator terminals 140 may represent, for example, a computing device running the MICROSOFT WINDOWS operating system.

[0027]

[0031] The various levels of the Purdue model may also include other components, such as one or more databases. The database or databases associated with each level may store any suitable information related to that level or one or more other levels of the system 100. For example, a historian 141 may The historian 141 may be coupled to the network 136. The historian 141 may represent a component that stores various information about the system 100. The historian 141 may store information used during production scheduling and optimization, for example. The historian 141 stores information and facilitates retrieval of the information. Although shown as one centralized component coupled to network 136, historian 141 may be located anywhere in system 100, or multiple historians may be distributed at different locations in system 100.

[0028]

[0032] 1 may represent computing devices. For example, each of the controllers 106, 114, 122, 130, 138 may include one or more processing devices 142 and one or more memories 144 for storing instructions and data used, generated, or collected by the processing device(s) 142. Each of the controllers 106, 114, 122, 130, 138 may also include one or more Ethernet interfaces or Each of the operator terminals 116, 124, 132, 140 may also include at least one network interface 146, such as one or more Ethernet interfaces or wireless transceivers. Each of the operator terminals 116, 124, 132, 140 may also include one or more processing devices 148 and one or more memories 150 for storing instructions and data used, generated, or collected by the processing device(s) 148. Each of the operator terminals 116, 124, 132, 140 may also include at least one network interface 152, such as one or more Ethernet interfaces or wireless transceivers.

[0029]

[0033] According to the present disclosure, the system 100 also includes an IoT edge appliance 160. The IoT edge appliance 160 integrates the plants 101a-101n and the network 136 with a cloud network 162 and one or more operator terminals 164. The IoT edge appliance 160 includes a distributed system architecture (DSA). The distributed system architecture (DSA) includes, for example, applications, big data storage, and analytics with on-premise devices (such as sensors, actuators, controllers, HMIs, and field applications). Communication between the IoT cloud network, including the IoT edge appliance 160, allows both the SCADA system and the DCS to be scaled out and distributed over long distances. The IoT edge appliance 160 is configured with both process automation and SCADA systems in mind.

[0030]

[0034] The IoT Edge Appliance 160 includes a DSA that is platform independent and includes a Global Data Access (GDA) data method that is configured to allow for periodic and asynchronous data access as well as alarms and events. The GDA data method is also configured to maintain data coherency and provide fast access to local data. An IoT Edge Appliance 160 that includes a DSA can be locally configured with an interface on the IoT Edge Appliance 160, or once implemented in the system 100, it can be cloud-based to recognize partner appliances and further recognize aggregate elements (such as tag names and asset classes). The partner appliances and element names may be configured through the edge network 162. In an embodiment, the IoT edge appliance 160 simply configures the IoT edge appliance 160 with the partner appliance and element names that are to be collected when the IoT edge appliance 160 receives the partner appliance or element name. The IoT Edge appliance 160 may also include security features, in which case the IoT Edge appliances 160 can only be configured by specific operators via a secure username and password. A username and password may be received and authenticated by IoT Edge appliance 160 to enable configuration signals that configure IoT Edge appliance 160. In an embodiment, the secured username and password may further grant access only to designated devices communicating with IoT Edge appliance 160.

[0031]

[0035] The IoT Edge Appliance 160 is configured for process automation. In process automation, the IoT Edge Appliance 160 enables scale-out of DCS without the need for extra computers and servers, enables wide-area plant interconnectivity, and enables uniform display of data about aggregated systems to a cloud network for consistent data analysis. The IoT Edge Appliance 160 also supports SCADA systems. In SCADA systems, the IoT Edge Appliance 160 provides local man-machine interfaces (HMIs) and mobility services, as well as cloud network services. The IoT Edge appliances 160 communicatively link various distributed solutions (such as pipelines, tank farms, wellheads in an oil field, etc.) for both uniform connectivity of the collection to the network 162.

[0032]

[0036] The IoT Edge Secure Gateway 160 is a platform based on a suitable embedded real-time operating system (OS) (such as a scaled-down form of LINUX). On top of the real-time OS, common protocol machines are layered to deliver "downstream" connectivity services to the on premise physical devices and systems using open protocols. These protocols can include Ethernet / IP, OPC UA, ProfiNet, IEC-61850, Modbus / TCP, HART / IP, etc. Non-Ethernet based protocols can also be communicated over serial communication ports ( Data collected from these downstream protocols is mapped to a unified abstraction layer that provides a consistent namespace and a set of data services for information exposure to the cloud layer.

[0033]

[0037] The communications stack for the cloud network 162 includes OPC UA and its core services for synchronous and asynchronous data publishing, alarm and event publishing, historical data transfer, blind record or "BLOB" transfer, etc. Other cloud protocols may be supported instead of or in addition to OPC UA. Other cloud protocols may have similar services, including event streaming to an event hub in the cloud and data access services. The IoT edge appliances 160 may be located at various layers in the control system and may include security services, including encryption and certificate based authentication. The IoT Edge Appliance 160 can provide a security feature. These services are available for both cloud-based connections and on-premise system and device connections. The IoT Edge Appliance 160 provides a secure guard traffic flow in both directions to protect both the cloud and on-premise systems and devices (such as devices in the plant 101, as well as the enterprise-level controller 138 and operator terminals 140).

[0034]

[0038] The IoT edge appliance 160 can be connected to different devices in the system 100. For example, while FIG. 1 shows the IoT edge appliance 160 located between the cloud network 162 and the network 136, the IoT edge appliance 160 can also be located between the network 136 and the router / firewall 134, between the network 128 and the router / firewall 126, between the network 120 and the router / firewall 118, between the network 112 and the switch / firewall 110, between the network 108 and the controller 106, between the network 104 and the sensor 102a, or between the network 104 and the actuator 102b. The IoT edge appliance 160 can also be located between the plant level controller 130 and the network 128, between the operator terminal 132 and the network 128, between the unit controller 122 and the network 120, between the operation station 124 and the network 120, between the machine controller 102b, ... An IoT Edge appliance 160 may be located between the operator terminal 114 and the network 112, or between the operator terminal 116 and the network 112. An IoT Edge appliance 160 may also be located between the network 136 and the plant 101b, or between the network 136 and the plant 101n. As described herein, multiple IoT Edge appliances 160 may be located at different locations within the system 100.

[0035]

[0039] In an embodiment, network 136 may represent a cloud network configured to facilitate communication between IoT edge appliance 160 and at least one of enterprise-level controller 138, operator terminal 140, historian 141, or one or more plants 101b-101n via wireless communications.

[0036]

[0040] Although FIG. 1 illustrates an example of an industrial process control and automation system 100, various modifications can be made to FIG. 1. For example, a control and automation system can include any number of sensors, actuators, controllers, servers, operator terminals, networks, risk managers, and other components. Additionally, the configuration and arrangement of system 100 in FIG. 1 is merely exemplary. Components can be added, omitted, combined, or placed in any other suitable configuration according to particular needs. Additionally, certain functions may be modified to suit the particular needs of system 100. This is merely an example. In general, control and automation systems are highly configurable and can be implemented by individual components. It may be configured in any suitable manner according to need.

[0037]

[0041] FIG. 2 illustrates an example configuration of an IoT edge appliance 160 according to the present disclosure. As shown in Figure 2, the IoT Edge Secure Gateway 160 is a The bus system 205 supports communication between at least one processing device 210, at least one storage device 215, at least one communication unit 220, and at least one input / output (I / O) unit 225.

[0038]

[0042] The processing device 210 executes instructions. The instructions are loaded into the memory 230. Processing device 210 may include any suitable number or types of processors or other devices in any suitable configuration. Examples of types of processing device 210 include microprocessors, microcontrollers, digital signal processors, field programmable gate arrays, application specific integrated circuits, and discrete circuits.

[0039]

[0043] Memory 230 and persistent storage 235 are examples of storage device 215 and represent any structure or structures capable of storing and facilitating retrieval of information (such as data, program code, and / or other suitable temporary or persistent information). Memory 230 may represent random access memory or any other suitable volatile or non-volatile storage device or devices. Persistent storage 235 may include one or more components or devices that support long-term storage of data, such as read-only memory, a hard drive, a flash memory, or an optical disk.

[0040]

[0044] The communications unit 220 supports communication with other systems or devices. For example, the communications unit 220 may include a network interface card or a wireless transceiver that facilitates communication over the network 136. The communications unit 220 may support communication over any suitable physical or wireless communications link(s).

[0041]

[0045] The I / O unit 225 allows for the input and output of data. For example, the I / O unit 225 may provide a connection for user input via a keyboard, mouse, keypad, touch screen, or other suitable input device. The I / O unit 225 may also send output to a display, printer, or other suitable output device.

[0042]

[0046] FIG. 2 illustrates an example of an IoT edge appliance 160, although various modifications may be made to FIG. 2. For example, the IoT edge appliance 160 may come in a variety of configurations. The IoT edge appliance 160 illustrated in FIG. is intended to illustrate one example type of IoT edge appliance and is not intended to limit the disclosure to any particular type of IoT edge appliance.

[0043]

[0047] FIG. 3 illustrates an example method 300 according to the present disclosure. The method 300 may be implemented in any suitable system using any suitable device. For example, As discussed below, the method 300 may be implemented in an IoT edge appliance 160 discussed herein. For ease of explanation, the method will be described with respect to the system 100 of FIG. Explain 300.

[0044]

[0048] As shown in FIG. 3 , in step 305, the IoT edge appliance 160 receives a configuration signal that configures the IoT edge appliance 160 to communicate with at least one device in the cloud network 162 or at least one device in the industrial process control and automation system network 136. In an embodiment, the configuration signal configures the IoT edge appliance 160 to extend the industrial process control system with additional controllers or terminals, for example. Alternatively, the IoT edge appliance 160 may discover new controllers or terminals and add them to the industrial process control system. The edge appliance 160 also enables wide area plant interconnectivity to enable uniform visibility and control from any operator terminal.

[0045]

[0049] In an embodiment, IoT Edge Appliance 160 is part of a SCADA system that controls a collection of distributed solutions (such as pipelines, tank farms, well heads in an oil field, etc.) The IoT Edge Appliance 160 provides local HMI and mobile services, as well as a consistent namespace and set of data services for exposing information to the cloud layer.

[0046]

[0050] In step 310, the IoT edge appliance 160 is configured to communicatively link with the cloud network 162 and the industrial process control and automation system network 136. The cloud network 162 utilizes a first communication protocol, and the industrial process control and automation system network 136 utilizes a second communication protocol. The IoT edge appliance 160 includes a DSA. The DSA is platform independent and includes a Global Data Access (GDA) data method. The Global Data Access (GDA) is configured for periodic and asynchronous data access, as well as alarms and events. The GDA data method is also configured to maintain data coherency and quickly access local data.

[0047]

[0051] In step 315, the IoT edge appliance 160 communicates with at least one of the devices on the network 136 or the cloud network 162. For example, the IoT edge appliance 160 may receive signals from or send signals to devices on the network 136 or the cloud network 162.

[0048]

[0052] Although Figure 3 illustrates one example of a method 300, various modifications may be made to Figure 3. For example, although illustrated as a series of steps, various steps illustrated in Figure 3 may overlap, be performed in parallel, be performed in a different order, or be performed multiple times. Furthermore, some steps may be combined or removed, and additional steps may be added according to individual needs.

[0049]

[0053] In one embodiment, various functions described in this patent document are realized or supported by a computer program formed of computer readable program code and embedded in a computer readable medium. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium accessible by a computer, such as read only memory (ROM), random access memory (RAM), hard disk drive, compact disk (CD), digital video disk (DVD), or any other type of memory. "Non-transitory" computer readable medium excludes wired, wireless, optical, or other communication links that carry transitory electrical or other signals. Non-transitory computer readable medium includes media that can store data permanently and media that can store data and subsequently be overwritten, such as rewritable optical disks or erasable memory devices.

[0050]

[0054] It may be beneficial to provide definitions of certain words and phrases used throughout this patent document. The terms "application" and "program" refer to one or more computer programs adapted for implementation in suitable computer code (including source code, object code, or executable code). "communicate" and its derivatives include both direct and indirect communication. The words "include" and "comprise" and their derivatives mean inclusion without limitation. "or" means any part of a program, software component, set of instructions, procedure, function, object, class, instance, associated data, or any portion thereof. The term "associated with" and its derivatives can mean including, contained within, interconnected, incorporating, housed within, connected to or with, coupled to or with, communicable with, cooperate with, interleave, juxtaposed, adjacent to, bounded by, having, having a property, having a relationship to or with, and the like. The phrase "at least one" when used with a list of items means that different combinations of one or more of the listed items can be used, and only one item in the list need be required. For example, "at least one of A, B, and C" includes any of the combinations A, B, C, A and B, A and C, B and C, and A and B and C.

[0051]

[0055] Nothing in this application should be read as implying that any particular element, step, or function is a required or essential element required for inclusion in the scope of the claims. The scope of patented subject matter is defined only by the allowed claims. Furthermore, the use of "means for" or "means for" in certain claims may be used without departing from the spirit or scope of the invention. Any claim in any accompanying document is not necessarily a "step for" claim unless the words "step for" are explicitly used and followed by a participle phrase that identifies the function. No invocation of 35 U.S.C. §112(f) is intended with respect to any of the claims or claim elements contained herein. When terms such as, but not limited to, "mechanism," "module," "device," "unit," "component," "element," "member," "apparatus," "machine," "system," "processor," or "controller" are used in the claims, it is understood and intended to refer to structures well known to those of ordinary skill in the relevant art and which may be further modified or improved by the features of the claims themselves, and no invocation of 35 U.S.C. §112(f) is intended with respect to any of the claims or claim elements contained herein. It is not intended to invoke

[0052]

[0056] While this disclosure has described specific embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Thus, the above description of example embodiments does not define or constrain this disclosure. Moreover, other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure, as defined by the following claims.

Claims

1. receiving (305), by an Internet of Things (IoT) edge appliance (160), a configuration signal for configuring said IoT edge appliance (160) to communicate with at least one of a first device (164) on a cloud network (162) or a second device (102a) on an industrial process control and automation system network (104); configuring (310) a communications link between the cloud network (162) and the industrial process control and automation system network (104) by the IoT edge appliance (160), the IoT edge appliance (160) including a distributed systems architecture (DSA), the DSA including a global data access (GDA) data method configured to enable periodic and asynchronous data access; receiving, by the IoT edge appliance (160), a username and password that enables the IoT edge appliance (160) to enable the configuration signal for configuring the IoT edge appliance (160) to communicate with at least one of the first device (164) on the cloud network (162) or the second device (102 a) on the industrial process control and automation system network (104); communicating (315) data with the at least one of the first device (164) on the cloud network (162) or the second device (102a) on the industrial process control and automation system network (104) by the IoT edge appliance (160); the configuration signals configure the IoT edge appliance (160) to enable scale-out of a distributed control system (DCS) via communication with the cloud network (162) and devices including sensors, actuators, controllers, HMIs, and applications in the industrial process control and automation system network (104). method.

2. 2. The method of claim 1, wherein the configuration signal configures the IoT edge appliance (160) to facilitate interconnection between plants (101a, 101b).

3. The method of claim 1 , wherein a namespace and data format of data presented to the first device on the cloud network is uniform.

4. 4. The method of claim 3, further comprising configuring the data upon receiving the data from the first device through the cloud network to be suitable for presentation in a namespace and data format of the second device.

5. 2. The method of claim 1, wherein the configuration signal configures the IoT edge appliance (160) to allow communication between the second device (102a) on the industrial process control and automation system network (104) and at least a fourth device (106) on the industrial process control and automation system network (104).

6. An Internet of Things (IoT) edge appliance (160) in an industrial process control and automation system, comprising: A processing circuit (210), The processing circuitry includes: receiving a configuration signal to configure the IoT edge appliance (160) to communicate with at least one of a first device (164) on a cloud network (162) or a second device (102a) on an industrial process control and automation system network (104); configuring a communications link between said cloud network (162) and said industrial process control and automation system network (104), said IoT edge appliance (160) including a distributed system architecture (DSA), said DSA including a global data access (GDA) data method configured to enable periodic and asynchronous data access; receiving a username and password that enables the IoT edge appliance (160) to enable the configuration signal to configure the IoT edge appliance (160) to communicate with at least one of the first device (164) on the cloud network (162) or the second device (102 a) on the industrial process control and automation system network (104); communicating data with the at least one of the first device (164) on the cloud network (162) or the second device (102a) on the industrial process control and automation system network (104); It is configured as follows: the configuration signals configure the IoT edge appliance (160) to enable scale-out of a distributed control system (DCS) through communication with the cloud network (162) and devices including sensors, actuators, controllers, HMIs, and applications in the industrial process control and automation system network (104); IoT Edge Appliances (160).

7. 7. The IoT edge appliance of claim 6, wherein the configuration signal configures the IoT edge appliance to facilitate interconnection between plants.

8. 7. The IoT edge appliance of claim 6, wherein the configuration signal configures the IoT edge appliance to present uniform data having a namespace and data format of the first device on the cloud network.

9. 10. The IoT edge appliance of claim 8, wherein the processing circuitry (210) is further configured to, upon receiving data from the first device (164) through the cloud network (162), configure the data to be suitable for presentation in a namespace and data format of the second device (102 a).

10. A non-transitory computer-readable medium storing one or more executable instructions that, when executed by one or more processors, cause the one or more processors to: receiving (305) a configuration signal for configuring an Internet of Things (IoT) edge appliance (160) to communicate with at least one of a first device (164) on a cloud network (162) or a second device (102a) on an industrial process control and automation system network (104); Configuring (310) a communications link between the cloud network (162) and the industrial process control and automation system network (104), the IoT edge appliance (160) including a distributed systems architecture (DSA) including a global data access (GDA) data method configured to enable periodic and asynchronous data access; receiving a username and password that enables the IoT edge appliance (160) to enable the configuration signal to configure the IoT edge appliance (160) to communicate with at least one of the first device (164) on the cloud network (162) or the second device (102 a) on the industrial process control and automation system network (104); communicating (315) data with the at least one of the first device (164) on the cloud network (162) or the second device (102a) on the industrial process control and automation system network (104); Run the command, the configuration signals configure the IoT edge appliance (160) to enable scale-out of a distributed control system (DCS) through communication with the cloud network (162) and devices including sensors, actuators, controllers, HMIs, and applications in the industrial process control and automation system network (104); Non-transitory computer-readable medium.

Citation Information

Patent Citations

  • Program delivery system and program delivery method

    JP2008152475A

  • Smart device for industrial automation

    US20130211546A1

  • Management system

    WO2010137066A1

  • Wireless communication network power optimization for control of industrial equipment in harsh environments

    WO2014028661A2