Factory management and control system, redundancy control method, storage medium, and computer device

Abstract

The embodiment of the invention discloses a factory management and control system, a redundancy control method, a storage medium and computer equipment, and relates to the field of intelligent manufacturing. According to the technical scheme of the invention, by introducing a double-ring network architecture, redundancy design of a virtualization server and platform data acquisition software, backup and emergency response of a local SCADA system and other measures, high availability, reliability and non-interruption effects of the whole system are realized. The technical measures jointly form a powerful industrial control system, and a powerful guarantee is provided for continuous and stable operation of the industrial process.

Description

Technical Field

[0001] The present application relates to the field of intelligent manufacturing, and in particular to a factory management and control system, a redundant control method, a storage medium and a computer device. Background Art

[0002] In the field of modern industrial automation, Facility Management and Control System (FMCS) plays a vital role. The system is responsible for managing and monitoring various facilities and equipment in the factory to ensure that production efficiency, safety and maintenance efficiency are optimized. FMCS integrates multiple technologies, such as sensor technology, communication technology, and data processing technology, to achieve comprehensive monitoring and intelligent scheduling of factory environment, production equipment, energy management, etc.

[0003] In the current FMCS design, in order to enhance the reliability and stability of the system, redundant design is widely used. Among them, the redundant design of the Programmable Logic Controller (PLC) is one of the core. By setting up the main PLC and the backup PLC, when the main PLC fails, the backup PLC can quickly take over the control task to ensure the continuity and stability of the production process. This design effectively avoids the impact of a single PLC failure on the entire system and improves the fault tolerance of the system.

[0004] In addition to the redundant design of PLC, the redundant design of SCADA (Supervisory Control And Data Acquisition) virtual platform is also an important part of FMCS. As the core software platform of FMCS, SCADA system is responsible for data collection, processing, display and alarm functions. Setting up multiple virtual servers with the same functions in the virtual platform can achieve data backup and load balancing, further improving the reliability and response speed of the system. When a virtual server fails, other virtual servers can take over its tasks to ensure the normal operation of the SCADA system.

[0005] However, although the existing FMCS has adopted redundant design measures in terms of PLC and SCADA virtual platforms, it still has certain limitations when facing network-level problems such as line failure or switch failure. When a line or switch in the FMCS fails, the data of the field equipment cannot be transmitted normally to the central control system, resulting in the system being unable to collect and process field data in real time. In this case, even if the PLC and SCADA virtual platforms themselves are in normal condition, the entire FMCS cannot work properly, thus affecting the production efficiency and safety of the factory. Summary of the invention

[0006] The embodiments of the present application provide a factory management and control system, a redundant control method, a storage medium and a computer device, which can solve the problem of low operational reliability of factory management and control systems in the prior art. The technical solution is as follows:

[0007] In a first aspect, an embodiment of the present application provides a factory management and control system, including:

[0008] At least one operator station, at least one engineer station, a main management core switch, a standby management core switch, a monitoring and control data acquisition virtual platform, a main ring network core switch, a standby ring network core switch, a ring network access switch 11 to a ring network access switch 1n, a ring network access switch 21 to a ring network access switch 2n, a PLC main controller 11 to a PLC main controller 1n, a PLC standby controller 21 to a PLC standby controller 2n, a local monitoring and control data acquisition device 1 to a local monitoring and control data acquisition device n; n is an integer greater than 1;

[0009] Wherein, the main management core switch is connected to the standby management core switch;

[0010] Each operator station is connected to the main management core switch, and each operator station is connected to the standby management core switch;

[0011] Each engineer station is connected to the primary management core switch, and each engineer station is connected to the backup management core switch;

[0012] The main management core switch and the standby management core switch are respectively connected to the monitoring control data acquisition virtual platform;

[0013] The main ring network core switch and the standby ring network core switch are respectively connected to the monitoring control data acquisition virtual platform;

[0014] The main ring network core switch is connected to the standby ring network core switch;

[0015] The main ring network core switch is connected to the ring network access switch 11, the ring network access switch 11 is connected to the ring network access switch 12, ..., the ring network access switch 1n is connected to the standby ring network core switch; the main ring network core switch, the ring network access switch 11 to the ring network access switch 1n, and the standby ring network core switch form a first ring network;

[0016] The main ring network core switch is connected to the ring network switch 21, the ring network access switch 21 is connected to the ring network access switch 22, ..., the ring network access switch 2n is connected to the standby ring network core switch; the main ring network core switch, the ring network access switch 21 to the ring network access switch 2n, and the standby ring network core switch form a second ring network;

[0017] The PCL main controller 11 is connected to the ring network access switch 11, the PCL main controller 12 is connected to the ring network access switch 12, ..., the PCL main controller 1n is connected to the ring network access switch 1n;

[0018] The PLC standby controller 21 is connected to the ring network access switch 21, the PLC standby controller 22 is connected to the ring network access switch 22, ..., the PLC standby controller 2n is connected to the ring network access switch 2n;

[0019] The local monitoring and control data acquisition device 1 is connected to the ring network access switch 11 and the ring network access switch 21 respectively, the local monitoring and control data acquisition device 2 is connected to the ring network access switch 12 and the ring network access switch 22 respectively, ..., the local monitoring and control data acquisition device n is connected to the ring network access switch 1n and the ring network access switch 2n respectively.

[0020] In a second aspect, an embodiment of the present application provides a redundant control method for a plant management and control system applied to the present application, including:

[0021] When it is detected that the first ring network and the second ring network have line disconnection faults at the same time, the OI / DA / IO Server in the monitoring and control data acquisition virtual platform is switched to a hot standby state, and the local monitoring and control data acquisition devices 1 to n are activated to a running state; each local monitoring and control data acquisition device sends a data request to the corresponding PLC controller in the running state, and stores the equipment field data reported by the PLC controller;

[0022] When it is detected that the line fault of any one of the first ring network and the second ring network is normal, the device field data locally stored in each local monitoring and control data acquisition device is reported to the OI / DA / IO Server in the monitoring and control data acquisition virtual platform, and then the OI / DA / IO Server in the monitoring and control data acquisition virtual platform is activated to the running state, and the local monitoring and control data acquisition devices 1 to local monitoring and control data acquisition devices n are switched to the hot standby state.

[0023] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0024] In a fourth aspect, an embodiment of the present application provides a computer device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0025] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:

[0026] The present application introduces a dual-ring network architecture based on a redundant controller, namely a first ring network and a second ring network. This design significantly enhances the reliability and fault tolerance of the network. When a ring access switch in a ring network fails, the system can quickly switch to the reverse route of the same ring network or the route of another ring network to ensure continuous data transmission. The dual-ring network architecture not only avoids system interruptions caused by single point failures, but also provides an effective data transmission path in the case of multi-path failures, thereby ensuring the continuous and stable operation of the entire system.

[0027] By using virtualized servers and platform-based data collection software, this technical solution splits the data collection and storage functions into independent redundant servers. When a functional server fails, the system can automatically switch to a backup server or an idle resource server to replace the work of the original functional server. This redundant design ensures the continuity and reliability of data collection and storage functions, and can ensure the normal operation of the system and data loss even in the event of multiple functional failures.

[0028] This application also establishes a local SCADA (Supervisory Control and Data Acquisition) system as a backup for the SCADA virtual platform. When the SCADA virtual platform fails, the system can quickly switch to the local SCADA system to continue data collection and preservation. The introduction of the local SCADA system not only improves the emergency response capability of the system, but also ensures that when the virtual platform fails, the system can seamlessly switch to the local mode to maintain the continuity and integrity of the data.

[0029] Combining the above technical measures, this application achieves the uninterrupted effect of the overall system. Whether at the network level, server level or data collection and storage level, the system has strong fault tolerance and redundant design. This design ensures that the system can quickly switch to backup or redundant resources when facing various failures and challenges, ensuring continuous data transmission and stable operation of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0031] Figure 1 is a schematic diagram of the structure of the FMCS provided in the embodiment of the present application;

[0032] Figure 2 It is a flowchart of a redundant control method provided in an embodiment of the present application;

[0033] Figure 3 is another flow chart of a redundant control method provided by the present application;

[0034] Figure 4 It is a structural schematic diagram of a computer device provided by this application. DETAILED DESCRIPTION

[0035] In order to make the objectives, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0036] Figure 1 An exemplary architectural diagram of a plant management and control system that can be applied to the present application is shown.

[0037] like Figure 1 As shown, the factory management and control system may include: at least one operator station View, at least one engineering station Engineering Station, a main management core switch 1, a standby management core switch 2, a supervisory control data acquisition SCADA virtual platform 3, a main ring network core switch 4, a standby ring network core switch 5, a ring network access switch 11 to a ring network access switch 1n, a ring network access switch 21 to a ring network access switch 2n, a PLC main controller 11 to a PLC main controller 1n, a PLC standby controller 21 to a PLC standby controller 2n, and a local SCADA device 1 to a local SCADA device n; n is an integer greater than 1.

[0038] Figure 1 Taking n=3 as an example, the number of operator stations is two, and the number of engineer stations is one. In the specific embodiment, the number of n, the number of operator stations, and the number of engineer stations are not limited thereto, and can be flexibly set according to actual needs.

[0039] Among them, the ring network access switch 21~ring network access switch 2n, the main ring network core switch 4 and the backup ring network core switch 5 together constitute a first ring network connected end to end, and the ring network access switch 21~ring network access switch 2n, the main ring network core switch 4 and the backup ring network core switch 5 together constitute a second second ring network connected end to end.

[0040] The connection relationship of the above-mentioned devices is explained below: the main management core switch and the standby management core switch are connected; each operator station is connected to the main management core switch, and each operator station is connected to the standby management core switch; each engineer station is connected to the main management core switch, and each engineer station is connected to the standby management core switch; the main management core switch and the standby management core switch are respectively connected to the monitoring and control data acquisition virtual platform; the main ring network core switch and the standby ring network core switch are respectively connected to the monitoring and control data acquisition virtual platform; the main ring network core switch is connected to the standby ring network core switch; the main ring network core switch is connected to the ring network access switch 11, the ring network access switch 11 is connected to the ring network access switch 12, ..., the ring network access switch 1n is connected to the standby ring network core switch; the main ring network core switch, the ring network access switches 11 to the ring network access switches 1n, and the standby ring network core switch form a first ring network; the main ring network core switch is connected to the ring network switch 21, and the ring network access switch 12 is connected to the ring network access switch 1n. The switch 21 is connected to the ring network access switch 22, ..., the ring network access switch 2n is connected to the standby ring network core switch; the main ring network core switch, the ring network access switch 21~ring network access switch 2n, and the standby ring network core switch form a second ring network; the PCL main controller 11 is connected to the ring network access switch 11, the PCL main controller 12 is connected to the ring network access switch 12, ..., the PCL main controller 1n is connected to the ring network access switch 1n; the PLC standby controller 21 is connected to the ring network access switch 21, the PLC standby controller 22 is connected to the ring network access switch 22, ..., the PLC standby controller 2n is connected to the ring network access switch 2n; the local monitoring and control data acquisition device 1 is respectively connected to the ring network access switch 11 and the ring network access switch 21, the local monitoring and control data acquisition device 2 is respectively connected to the ring network access switch 12 and the ring network access switch 22, ..., the local monitoring and control data acquisition device n is respectively connected to the ring network access switch 1n and the ring network access switch 2n.

[0041] The operator station is used to provide the operator with a human-machine interface (HMI) to monitor the factory's production status, equipment operation, alarm information, etc., and supports the operator to remotely control and operate the factory equipment. Each operator station is connected to the main management core switch and the backup management core switch through redundant connections to ensure high reliability and data integrity.

[0042] The Engineering Station is used for system configuration, program writing, downloading, debugging and system maintenance, and is the development and management center of the factory automation system. It is connected to the main management core switch and the backup management core switch through redundant connections to ensure that engineers can continuously access the system to perform necessary work.

[0043] The main management core switch and the backup management core switch are the core of the factory network, responsible for data transmission and communication between the operator station, engineer station and SCADA virtual platform, and provide network redundancy and fault switching functions. The two are connected through high-speed links to form a redundant architecture, and are connected to the operator station, engineer station and SCADA virtual platform at the same time.

[0044] The SCADA virtual platform is used to collect the operation data of various equipment in the factory in real time, process, store and analyze the data, provide a data visualization interface, and support alarm and event management. It is connected to the main management core switch, backup management core switch, main ring network core switch and backup ring network core switch to achieve efficient data transmission and sharing.

[0045] The main ring network core switch and the backup ring network core switch are the core devices of the ring network, responsible for the transmission and forwarding of data within the ring network, and provide network redundancy and fault recovery capabilities. The two are connected through redundant links and are connected to the SCADA virtual platform, ring network access switch and PLC master / standby controller.

[0046] The ring network access switch serves as the access point of the ring network, connecting the PLC controller and local SCADA equipment to the ring network. They are connected according to the ring topology to form two independent ring networks, and each ring network access switch is connected to the corresponding PLC controller and local SCADA equipment.

[0047] The PLC master controller and the PLC standby controller are responsible for the automation control of factory equipment. The PLC master controller is responsible for normal operation, and the PLC standby controller takes over the control task when the master controller fails. The PLC master controller is connected to the ring network access switch of the first ring network, and the PLC standby controller is connected to the ring network access switch of the second ring network to achieve redundant control.

[0048] Local SCADA equipment: used to collect and monitor real-time data of factory field equipment, supporting local control and alarm functions. Each local SCADA device is connected to two ring network access switches through redundant connections to ensure data reliability and integrity.

[0049] according to Figure 1In the network architecture, the factory management and control system (FMCS) of this application ensures the high reliability, high availability and data integrity of the system through redundant architecture and ring network design, meeting the needs of factory automation and intelligent management.

[0050] In some embodiments of the present application, the primary management core switch 1 and the backup management core switch 2 are configured as stacked switches. The specific configuration process includes:

[0051] Install stacking cards: Stacking cards are the core components of stacking switch technology and are responsible for physical connection and communication. Install stacking cards on the primary management core switch 1 and the backup management core switch 2, and ensure that the stacking cards are correctly inserted into the designated slots of the switches. The stacking cards should support the required stacking bandwidth and number of ports to meet network requirements.

[0052] Configure the stack ID: The stack ID is used to identify each switch in the stack. Configure the stack ID on the switch to ensure that each switch has a unique identifier in the stack. The stack ID is usually automatically assigned when the switch boots up, but it can also be manually configured to meet specific needs.

[0053] Configuring stack priority: The stack priority determines which switch in the stack will operate as the master switch. When configuring the stack priority, ensure that the master switch has a higher priority than the slave switch. The stack priority can be manually configured on the switch or automatically determined based on the switch's hardware and software versions.

[0054] Save the configuration: After configuring the stack ID and stack priority, make sure to save the configuration to the switch's non-volatile memory (NVRAM). This ensures that the configuration is not lost if the switch is rebooted or fails.

[0055] Connect stacking cables: Use stacking cables to connect the physical stacking ports of the active management core switch 1 and the standby management core switch 2. The stacking cables should support the required stacking bandwidth and length to meet network requirements. When connecting stacking cables, ensure that the cables are properly inserted into the stacking ports and follow the manufacturer's guidelines for connection.

[0056] Dual-link port aggregation: To improve the reliability and performance of stacked switches, you can configure dual-link port aggregation. Dual-link port aggregation allows you to establish multiple physical connections between stacked switches and aggregate them into one logical connection. This ensures that when a single physical connection fails, traffic can be automatically redirected to other available physical connections. When configuring dual-link port aggregation, you should ensure that the switches support the required aggregation protocols (such as LACP, PAgP, etc.) and configure the aggregation group, ports, and priorities correctly.

[0057] After configuration is complete, the stacked switches will be operated and managed as a single logical device. The configuration and management functions of the entire stack can be accessed through the management interface of any stacked switch. In addition, stacked switches also support various advanced functions such as link aggregation, VLAN division, routing protocols, etc. to meet complex network requirements.

[0058] In summary, configuring the active management core switch 1 and the standby management core switch 2 as stack switches can improve network reliability, performance, and simplify management. During the configuration process, the manufacturer's guidelines and best practices should be carefully followed to ensure the correct configuration and operation of the stack switches.

[0059] Furthermore, in some embodiments of the present application, VMware software and AVEVA System Platform software are installed in the monitoring and control data acquisition virtual platform, and the VMware software creates multiple virtual machines based on hardware resources, and the AVEVA System Platform software is used to deploy multiple OI / DA / IO Servers, multiple AOSs and multiple Historian Servers in the created virtual machines.

[0060] Among them, VMware software is responsible for abstracting physical hardware resources (such as CPU, memory, storage, etc.) into virtual resources, so that multiple virtual machines can run on the same physical hardware. vCenter Server (Control Center Service): vCenter Server is the core management component of VMware. It provides a centralized management platform for monitoring, configuring and managing ESXi hosts and virtual machines in a virtual environment. vSphere HA (ESXi host, virtual machine): vSphere HA is a high availability feature provided by VMware. It can automatically restart virtual machines to other available hosts when a host or virtual machine fails, thereby ensuring business continuity.

[0061] AVEVA System Platform software provides a component-based architecture that allows industrial acquisition software to run as a platform application. OI / DA / IO Server (data acquisition driver): This is the data acquisition component of AVEVA SystemPlatform software. It is responsible for collecting data from various industrial devices (such as sensors, instruments, etc.) and converting it into information that the system can understand and process. AOS (Application Server): AOS is one of the core components of AVEVA System Platform software. It provides an operating environment for applications, including data processing, event processing, alarm management, etc. Historian Server: Historian Server is responsible for storing and managing historical data, which can be used for trend analysis, report generation, etc. It is usually tightly integrated with OI / DA / IO Server and AOS to ensure data accuracy and consistency.

[0062] Specifically, OI / DA / IO Server is used to collect real-time data from industrial equipment, including analog quantities, digital quantities, status information, etc. The collected raw data is converted into an information format that the system can understand and process. It supports multiple communication protocols and device types to ensure compatibility with various industrial equipment.

[0063] AOS is used to: process and analyze the collected data, including data filtering, data compression, data conversion, etc. Monitor and process events in the system, such as equipment failures, alarms, etc., and trigger corresponding response measures. Provide alarm configuration, alarm notification, alarm recording and other functions to ensure that the system can detect and handle abnormal situations in a timely manner.

[0064] Historian Server is used to: store the collected historical data in the database for subsequent analysis and query. Provide trend analysis tools to allow users to view the changes in data over time and identify potential problems and trends. Generate various reports based on user needs, including real-time data reports, historical data reports, etc., to help users better understand the operating status of the system.

[0065] In summary, the SCADA virtual platform built on VMware software and AVEVA System Platform software provides strong technical support for data acquisition and monitoring systems. Through the virtualization of hardware resources, the platform operation of industrial acquisition software, and the tight integration of various components, the system can achieve efficient and reliable data acquisition, processing and storage, providing strong support for industrial production and operations.

[0066] In some embodiments of the present application, when constructing a virtual platform for monitoring and controlling data acquisition, in order to ensure that the platform can cope with possible future load growth while ensuring the stability and reliability of the system, it is necessary to reasonably configure hardware resources. According to experience, hardware resources are usually configured to 150% of the historical maximum load to provide sufficient buffering and redundancy.

[0067] Specifically, the hardware resource configuration steps include:

[0068] Historical load data analysis: Collect the load data of the platform over the past period of time, including key indicators such as CPU usage, memory usage, disk I / O, etc. Analyze the historical load data to determine the historical maximum load value. This is usually the highest load value observed in a specific time period (such as a day, week, or month).

[0069] Calculate the required hardware resources: Calculate the required hardware resources based on the historical maximum load value. This includes the number of CPU cores, memory capacity, disk storage capacity, and I / O bandwidth. Multiply the required hardware resources by 150% to get the final hardware configuration requirements.

[0070] Select hardware components: Select appropriate hardware components based on the calculated hardware configuration requirements. This includes servers, storage devices, network devices, etc. Ensure that the performance and reliability of the selected hardware components meet the requirements of platform operation.

[0071] Build a virtual platform: Use virtualization technology (such as VMware) to build a virtual platform. Allocate corresponding resources to each virtual machine on the virtual platform according to the hardware configuration requirements. Ensure that the resource allocation of the virtual machine meets the performance and reliability requirements of the platform.

[0072] Performance testing and optimization: Run performance tests on the virtual platform to simulate actual load conditions. Based on the test results, optimize the performance of the virtual platform, such as adjusting virtual machine resource allocation, optimizing system configuration, etc. Ensure that the virtual platform can run stably under simulated load and that performance meets expected requirements.

[0073] Monitoring and management: Deploy monitoring tools to monitor the hardware resource usage of the virtual platform in real time. Set alarms and thresholds. When resource usage approaches or exceeds the threshold, issue an alarm and take appropriate measures. Regularly maintain and manage the virtual platform to ensure system stability and reliability.

[0074] See also Figure 2 , which is a flowchart of a redundant control method provided in an embodiment of the present application. The redundant control method of the present application is applied to Figure 1 Factory management and control systems. Figure 2 As shown, the method of the embodiment of the present application may include the following steps:

[0075] S201. When the core switch of the main ring network detects that a line disconnection fault occurs in the first ring network, the PLC main controller 11~PLC main controller 1n is switched from the running state to the hot standby state, and the PLC standby controller 21~PLC standby controller 2n is activated from the hot standby state to the running state; the core switch of the standby ring network collects the equipment field data from the PLC standby controller 21~PLC standby controller 2n from the second ring network, and the core switch of the standby ring network reports the collected equipment field data to the OI / DA / IO Server in the data acquisition virtual platform.

[0076] Among them, the main ring network core switch monitors the connection status of the first ring network in real time through its built-in link layer protocol (such as spanning tree protocols such as STP / RSTP / MSTP) or physical layer detection mechanism. When a line disconnection fault is detected, the fault handling process is triggered immediately. Once the fault is confirmed, the main ring network core switch sends a state switching instruction to the PLC main controller 11 to the PLC main controller 1n through a specific communication protocol (such as SNMP, Modbus TCP, etc.) or an internal communication mechanism to switch it from the running state to the hot standby state. At the same time, an activation instruction is sent to the PLC standby controller 21 to the PLC standby controller 2n to activate it from the hot standby state to the running state.

[0077] After the PLC standby controllers 21 to 2n are activated to the running state, they start to execute the control logic normally and collect the equipment field data. The standby ring network core switch collects the equipment field data of these PLC standby controllers from the second ring network through its configured network interface. The standby ring network core switch reports the collected equipment field data to the OI / DA / IO Server in the data acquisition virtual platform through an internal communication channel (such as private protocol, OPC UA, etc.) or a standard communication protocol (such as MQTT, HTTP, etc.). The OI / DA / IO Server is responsible for receiving, parsing and storing this data for subsequent analysis and processing.

[0078] S202. When the core switch of the standby ring network detects that the line of the second ring network is disconnected, the PLC standby controllers 21 to 2n are switched from the running state to the hot standby state, and the PLC main controllers 11 to 1n are activated from the hot standby state to the running state; the core switch of the main ring network collects the equipment field data from the PLC main controllers 11 to 1n from the first ring network, and the core switch of the main ring network reports the collected equipment field data to the OI / DA / IO Server in the data acquisition virtual platform.

[0079] Among them, similar to S201, the core switch of the standby ring network monitors the connection status of the second ring network in real time through its built-in link layer protocol or physical layer detection mechanism. When a line disconnection fault is detected, the fault handling process is immediately triggered. Once the fault is confirmed, the core switch of the standby ring network sends a state switching instruction to the PLC standby controller 21 to the PLC standby controller 2n through the same communication protocol or internal communication mechanism to switch it from the running state to the hot standby state. At the same time, an activation instruction is sent to the PLC main controller 11 to the PLC main controller 1n to activate it from the hot standby state to the running state.

[0080] After the PLC master controllers 11 to 1n are activated to the running state, they start to execute the control logic normally and collect the equipment field data. The main ring network core switch collects the equipment field data of these PLC master controllers from the first ring network through its configured network interface. The main ring network core switch reports the collected equipment field data to the OI / DA / IO Server in the data acquisition virtual platform through the same communication channel or protocol. The OI / DA / IO Server continues to be responsible for receiving, parsing and storing this data.

[0081] For example, ring network A (first ring network) includes ring network access switches 11, 12, 13 and a main ring network core switch.

[0082] Ring network B (second ring network): includes ring network access switches 21, 22, 23 and a backup ring network core switch.

[0083] PLC controller: PLC main controller 11~13 and PLC standby controller 21~23.

[0084] OI / DA / IO Server: Deployed in the data acquisition virtual platform, responsible for receiving data from the PLC controller.

[0085] A line disconnection fault occurs in the ring network A, specifically, the line between the ring network access switch 11 and the ring network access switch 12 is disconnected, and the line between the ring network access switch 11 and the main ring network core switch is disconnected.

[0086] The redundancy process includes:

[0087] The main ring network core switch detects the line disconnection fault of ring network A through the ring network protocol (such as STP / RSTP, etc.). The main ring network core switch attempts to receive data from ring network access switches 11 to 13 in the original clockwise direction, but fails to receive data successfully due to the line disconnection.

[0088] The main ring network core switch sends a counterclockwise data transmission request to the ring network access switches 11, 12, and 13 as an attempt to recover from the fault. The ring network access switches 12 and 13 can respond to this request and try to return data to the main ring network core switch. However, since the line between the ring network access switch 11 and the main ring network core switch is still disconnected, the main ring network core switch cannot receive data from the ring network access switch 11.

[0089] The main ring network core switch notifies the backup ring network core switch of the fault. The backup ring network core switch sends a clockwise data transmission request to the ring network access switches 21, 22, and 23 through the ring network B (the second ring network). The ring network access switches 21, 22, and 23 are able to respond to this request and successfully return data to the backup ring network core switch. The backup ring network core switch successfully receives the data from the ring network access switches 21, 22, and 23, confirming that the clockwise routing configuration of the second ring network B is valid.

[0090] Due to the failure of ring network A, PLC master controllers 11-13 can no longer request data from the OI / DA / IO Server. The backup ring network core switch notifies the PLC controller to switch states: PLC backup controllers 21-23 are activated to the running state, while PLC master controllers 11-13 are switched to the hot standby state. PLC backup controllers 21-23 start running and send data requests to the OI / DA / IO Server deployed in the monitoring and control data acquisition virtual platform.

[0091] After receiving the data request from the PLC standby controllers 21 to 23, the OI / DA / IO Server processes the data request. The OI / DA / IO Server returns a data response to the PLC standby controllers 21 to 23 to ensure the continuity of data communication. In this process, the OI / DA / IO Server successfully collects data from the PLC standby controllers 21 to 23 through the clockwise routing of the second ring network B, achieving uninterrupted data collection.

[0092] Through the above steps, when ring network A fails, the system can automatically switch to ring network B and activate PLC standby controllers 21-23 to ensure the continuity of data collection. OI / DA / IO Server can continue to receive data from PLC controllers, ensuring the normal operation of the monitoring and control data acquisition virtual platform.

[0093] For further information, see Figure 3 As shown, another flowchart of the redundant control method specifically includes:

[0094] S301. When it is detected that line disconnection failures occur simultaneously in the first ring network and the second ring network, the OI / DA / IO Server in the monitoring and control data acquisition virtual platform is switched to hot standby state, and the local monitoring and control data acquisition devices 1 to local monitoring and control data acquisition devices n are activated to running state; each local monitoring and control data acquisition device sends a data request to the corresponding PLC controller in running state, and stores the equipment field data reported by the PLC controller.

[0095] Among them, the system simultaneously monitors the connection status of the first ring network and the second ring network through a built-in fault detection mechanism (such as a network monitoring tool, SNMP protocol, etc.). When it is detected that the line disconnection fault occurs simultaneously in the two ring networks, the system triggers an emergency fault handling process. After receiving the fault notification, the OI / DA / IO Server in the monitoring and control data acquisition virtual platform automatically switches from the running state to the hot standby state, and stops receiving and processing data from the PLC controller. At the same time, the system activates local monitoring and control data acquisition devices 1 to local monitoring and control data acquisition devices n, and these devices switch from the hot standby state or standby state to the running state. Each local monitoring and control data acquisition device establishes a connection with the corresponding PLC controller in the running state through a preset communication protocol (such as Modbus TCP, OPC UA, etc.). Each local monitoring and control data acquisition device sends a data request to the corresponding PLC controller to request to obtain the device field data. The PLC controller responds to the data request and sends the device field data to the corresponding local monitoring and control data acquisition device. After receiving the data, the local monitoring and control data acquisition device performs necessary verification and processing, and then stores the data in a local storage device (such as a hard disk, SSD, etc.) to ensure the integrity and availability of the data

[0096] S302. When it is detected that the line fault of any one of the first ring network and the second ring network is normal, the device field data stored locally in each local monitoring and control data acquisition device is reported to the OI / DA / IO Server in the monitoring and control data acquisition virtual platform, and then the OI / DA / IO Server in the monitoring and control data acquisition virtual platform is activated to the running state, and the local monitoring and control data acquisition devices 1 to the local monitoring and control data acquisition device n are switched to the hot standby state.

[0097] The system continues to monitor the connection status of the first ring network and the second ring network.

[0098] When it is detected that the line fault of any ring network has returned to normal, the system triggers the fault recovery process. Each local monitoring and control data acquisition device reads the previously stored device field data from the storage device. Through the restored network connection, the locally stored device field data is reported to the OI / DA / IO Server in the monitoring and control data acquisition virtual platform. After receiving the data from the local monitoring and control data acquisition device, the OI / DA / IO Server performs data verification and integration. After confirming that the data is complete and correct, the OI / DA / IO Server switches from the hot standby state to the running state, and resumes receiving and processing data from the PLC controller. At the same time, the system switches the local monitoring and control data acquisition device 1 to the local monitoring and control data acquisition device n from the running state to the hot standby state, waiting for the next possible fault processing task.

[0099] For example, assume that: Ring network A (first ring network) includes ring network access switches 11, 12, etc., and connected primary ring network core switches. Ring network B (second ring network) includes ring network access switches 21, 22, etc., and connected backup ring network core switches. PLC master controller 11 communicates with OI / DA / IO Server via ring network A, and PLC backup controller 21 communicates with OI / DA / IO Server via ring network B. Local SCADA1 is a monitoring and control data acquisition device deployed on site, used to provide data backup and control functions when the ring network fails.

[0100] Fault situation: In ring network A, the line between ring network access switch 11 and the primary ring network core switch is disconnected, and the line between ring network access switch 11 and ring network access switch 12 is also disconnected. In ring network B, the line between ring network access switch 21 and the backup ring network core switch is disconnected, and the line between ring network access switch 21 and ring network access switch 22 is also disconnected.

[0101] The redundant control process includes:

[0102] Fault detection: The system detects that both ring network A and ring network B have line faults, triggering the dual ring network fault handling process. OI / DA / IO Server state switching: The OI / DA / IO Server detects that the connection with the PLC master controller 11 and the PLC standby controller 21 is interrupted and cannot receive data. The OI / DA / IO Server automatically switches from the running state to the hot standby state, stopping data processing and reporting.

[0103] Local SCADA1 activation: Local SCADA1 detects the loss of connection with the OI / DA / IO Server and automatically switches from hot standby to running state. Local SCADA1 sends a data request to the PLC controller in running state (which may be a redundant device of the PLC master controller 11 or other online PLC controller) through a preset communication protocol.

[0104] Data request and collection: After receiving the data request, the PLC controller processes and returns the equipment field data. After receiving the data, the local SCADA1 stores and preliminarily processes it to ensure that the data is not lost and the control is not out of control.

[0105] Route switching and data retention: Due to a ring network failure, the local SCADA1 collects data from the PLC controller through the corresponding ring network access switch (if there is still an available route) or directly through the local network. If the ring network is completely interrupted, the local SCADA1 may communicate with the PLC controller through other communication methods (such as wireless, wired backup network).

[0106] Fault recovery: The system continuously monitors the connection status of ring network A and ring network B. When it detects that the line fault of any ring network has been restored to normal, the system triggers the fault recovery process.

[0107] Data re-collection: OI / DA / IO Server status recovery: OI / DA / IO Server detects that the connection with the ring network is restored and automatically switches from hot standby status to running status. OI / DA / IO Server starts to receive and process data from the PLC controller.

[0108] Local SCADA1 data reporting: Local SCADA1 reports the field data of the equipment stored during the fault to the OI / DA / IO Server. During the data reporting process, the integrity and consistency of the data are ensured.

[0109] Data integration and processing: After receiving the data reported by the local SCADA1, the OI / DA / IO Server integrates and processes the data to ensure the continuity and consistency of the data in the system.

[0110] Local SCADA1 status switching: After data collection and integration are completed, local SCADA1 automatically switches from the running state to the hot standby state, waiting for the next possible fault handling task.

[0111] Furthermore, in some embodiments of the present application, when the monitoring and control data acquisition virtual platform detects that any one of the AOS, OI / DA / IO Server and Historian Server fails, it uses idle hardware resources to create a virtual machine, and then the created virtual machine takes over the failed service.

[0112] The monitoring and control data acquisition virtual platform has a built-in comprehensive monitoring mechanism, which monitors the operating status of key components such as AOS, OI / DA / IO Server and Historian Server in real time through heartbeat detection, service status query, etc. Once a component is detected to have a failure or performance abnormality, the system will immediately trigger an alarm mechanism to notify the administrator or automatically start the fault handling process.

[0113] After receiving a fault alarm, the system first evaluates the currently idle hardware resources, including CPU, memory, storage, etc., to determine whether there are enough resources to create a new virtual machine. If the resources are sufficient, the system will automatically create a new virtual machine based on the preset virtual machine template (including the operating system, necessary software and service configuration, etc.). This virtual machine will be used to take over the failed service.

[0114] After the newly created virtual machine is started, the system will migrate the relevant data and configuration of the failed service (such as AOS, OI / DA / IO Server or Historian Server) to the new virtual machine. After the migration is complete, the services on the new virtual machine will automatically start and take over the services originally provided by the failed server. This includes functions such as data processing, data storage, and data communication. To ensure that the service takeover is successful, the system will verify and test the services on the new virtual machine. This includes checking the running status of the service, data integrity, and communication capabilities.

[0115] While the virtual machine is taking over the service, the administrator repairs the failed server. This includes hardware replacement, software repair, or system reinstallation. If the failed server is successfully repaired and verified to be able to provide services again, the administrator can migrate the service from the virtual machine back to the original server. This usually needs to be done during off-peak hours to reduce the impact on the system. If the service has been successfully migrated back or it is decided not to use the newly created virtual machine, the administrator should release the hardware resources occupied by the virtual machine.

[0116] The following takes the complete failure of the Historian Server in the SCADA virtual platform as an example to illustrate.

[0117] In the SCADA virtual platform, the vSphere HA (high availability) system is responsible for monitoring the operating status of all key components, including the AOS server, OI / DA / IO server, and Historian Server. When all Historian Servers fail, vSphere HA will not be able to receive data responses from the Historian Servers.

[0118] Heartbeat detection failure: vSphere HA detects the online status of the Historian Server by sending heartbeat signals periodically. If no heartbeat response is received for multiple consecutive times, vSphere HA will consider that the Historian Server has failed.

[0119] Service status query exception: vSphere HA will also try to query the service status of the Historian Server. If the query result shows that the service is not running or cannot be accessed, it will further confirm the occurrence of the fault.

[0120] After confirming the failure of the Historian Server, vSphere HA will automatically evaluate resources and prepare to create a new virtual machine to take over the service.

[0121] vSphere HA checks the idle hardware resources in the cluster, including CPU, memory, storage, and network. Ensure that there are enough resources to support the creation and operation of new virtual machines. Based on the preset virtual machine template (including the operating system, software, and service configuration required by the Historian Server), vSphere HA selects a suitable template to create a virtual machine. vSphere HA creates a new virtual machine on an idle ESXi host in the cluster. This virtual machine will be used to take over the failed Historian Server service.

[0122] After the newly created virtual machine is started, vSphere HA starts the service takeover process.

[0123] vSphere HA migrates the data (such as historical data, configuration files, etc.) on the failed Historian Server to the newly created virtual machine. This is usually achieved through shared storage or data replication technology. On the new virtual machine, vSphere HA automatically starts the Historian Server service. This service will take over all the functions originally provided by the failed server. vSphere HA verifies and tests the Historian Server service on the new virtual machine. Ensure that the service is running normally and can receive and process data.

[0124] After the virtual machine successfully takes over the Historian Server service, the administrator repairs the failed server. The administrator checks the failed Historian Server, determines the cause of the failure, and repairs it. This may include hardware replacement, software repair, or system reinstallation. If the repaired Historian Server can provide services again and meets performance and reliability requirements, the administrator can migrate the service back from the virtual machine to the original server. This usually needs to be done during off-peak hours to reduce the impact on the system. If the service has been successfully migrated back or it is decided not to use the newly created virtual machine, the administrator should release the hardware resources occupied by the virtual machine.

[0125] Through the detailed description of the above steps and the key interactions in the example, you can clearly understand how vSphere HA ensures system continuity and availability by creating virtual machines and taking over services when the Historian Server fails in the SCADA virtual platform.

[0126] Furthermore, in some embodiments of the present application, when the monitoring and control data acquisition virtual platform detects that all faults have occurred in the AOS, OI / DA / IO Server and Historian Server, the OI / DA / IO Server in the monitoring and control data acquisition virtual platform is switched to a hot standby state, and the local monitoring and control data acquisition device 1 to the local monitoring and control data acquisition device n are activated to an operating state; each local monitoring and control data acquisition device sends a data request to the corresponding PLC controller in the operating state, and stores the equipment field data reported by the PLC controller.

[0127] The monitoring and control data acquisition virtual platform will continuously monitor the key components in the system, including AOS (application server), OI / DA / IO Server (data acquisition and interface server) and Historian Server (historical data server). When the platform detects that all or key parts of these components fail, the corresponding fault handling mechanism will be triggered.

[0128] Once a fault is detected, the platform will immediately switch the OI / DA / IO Server to hot standby status. Hot standby status means that the server is ready to immediately take over the work of the failed server without additional startup or initialization time. At the same time, the platform will activate local monitoring and control data acquisition device 1 to local monitoring and control data acquisition device n to run. These devices may be data acquisition terminals distributed in different locations, used to collect field data in real time.

[0129] Each activated local monitoring and control data acquisition device will send a data request to the corresponding PLC (Programmable Logic Controller) controller in operation. The data request may contain information such as the type of data to be collected, the collection frequency, and the data format.

[0130] After receiving the data request, the PLC controller will collect the corresponding data from the field equipment according to the content of the request. The collected data may include sensor readings, equipment status, operating parameters, etc.

[0131] The PLC controller reports the collected equipment field data to the corresponding local monitoring and control data acquisition device. After receiving the data, the local monitoring and control data acquisition device will store it in the local storage device for subsequent analysis and processing. At the same time, these data may also be transmitted in real time to the monitoring and control data acquisition virtual platform or other related systems for further analysis and decision-making.

[0132] The following example illustrates the process of SCADA virtual platform fault switching.

[0133] The monitoring system in the SCADA virtual platform detected that the AOS server, OI / DA / IO server, and HistorianServer all failed. These failures may manifest as service interruption, no response, or data loss. The vSphere HA (high availability) system began to evaluate the free virtual machine resources in the cluster. This includes resources such as CPU, memory, storage, and network. After evaluation, vSphere HA found that the current free virtual machine resources cannot accommodate all virtual machines that need to be migrated or restarted due to failures.

[0134] Based on the resource evaluation results, vSphere HA decides to send a hot standby switch request to the OI / DA / IO Server. This request is to ensure that in the event of a failure, the OI / DA / IO Server can quickly switch to the hot standby state to take over the work of the failed server.

[0135] After receiving the hot standby switch request, the OI / DA / IO Server starts to process the request. The processing may include releasing currently occupied resources, preparing the hot standby environment, configuring network connections, etc. During the processing, the OI / DA / IO Server will interrupt the connection with the local SCADA to ensure that no data conflict or loss occurs during the switch. Once the OI / DA / IOServer completes the hot standby preparation, it returns a response to vSphere HA that the hot standby switch request has been completed. This means that the OI / DA / IOServer is ready to take over the work of the failed server.

[0136] After the local SCADA1~3 detects that the connection with the OI / DA / IO Server is lost, it switches from the hot standby state to the running state according to the preset fault switching logic. This means that they will begin to take over the data acquisition and control tasks originally handled by the OI / DA / IO Server. The local SCADA1~3 that switches to the running state begins to send data requests to the PLC controller in the running state. These requests may include real-time data reading, equipment status query, etc. After receiving the data request, the PLC controller processes it according to the content of the request. This may include reading sensor data, executing control logic, etc. After processing, the PLC controller returns the requested data to the local SCADA1~3.

[0137] Local SCADA 1-3 collects data from PLC controllers through corresponding ring network access switches. These data may include equipment status, operating parameters, etc. The collected data is used by local SCADA 1-3 to monitor and control industrial processes in real time, realizing localized operation of data collection and control.

[0138] In the above process, the fault detection and resource evaluation functions of vSphere HA ensure the stability and reliability of the system. When a critical server failure is detected, vSphere HA can respond quickly by sending hot standby requests and processing mechanisms to ensure that the OI / DA / IO Server can switch to hot standby status and take over the work of the failed server. At the same time, the local SCADA1~3 fault switching and data acquisition functions ensure that the real-time monitoring and control of the industrial process are not affected, and realize the local operation of data acquisition and control.

[0139] Furthermore, in some embodiments of the present application, it also includes:

[0140] When the main ring network core switch detects that an access switch failure occurs in the first ring network, the PLC main controller 11~PLC main controller 1n is switched from the running state to the hot standby state, and the PLC standby controller 21~PLC standby controller 2n is activated from the hot standby state to the running state; the standby ring network core switch collects the equipment field data from the PLC standby controller 21~PLC standby controller 2n from the second ring network, and the standby ring network core switch reports the collected equipment field data to the OI / DA / IO Server in the data acquisition virtual platform.

[0141] The core switch of the main ring network monitors the operation status of the access switch in the first ring network in real time through its built-in monitoring and diagnosis functions. When a fault is detected in the access switch, the core switch of the main ring network will trigger the fault handling process.

[0142] The core switch of the main ring network switches the PLC main controller 11 to the PLC main controller 1n from the running state to the hot standby state. This switching process is to ensure that in the event of a failure of the access switch, the PLC main controller will not continue to send data or execute control instructions to the failed network, thereby avoiding potential data loss or control errors. At the same time, the core switch of the main ring network activates the PLC standby controller 21 to the PLC standby controller 2n from the hot standby state to the running state. These standby controllers are in the hot standby state before the failure switching, that is, the necessary programs and configurations have been loaded and are ready to take over the tasks of the main controller at any time. Once the main controller is switched to the hot standby state, the standby controller will immediately start to execute the control task to ensure the continuity and stability of the industrial process.

[0143] After the PLC standby controllers 21 to 2n are activated to the running state, they will start to collect the equipment field data. These data may include sensor readings, equipment status, operating parameters, etc. The standby ring network core switch receives these equipment field data from the PLC standby controllers through the second ring network. In order to ensure the accuracy and integrity of the data, the standby ring network core switch will verify and organize these data.

[0144] The core switch of the backup ring network reports the collected equipment field data to the OI / DA / IO Server in the data acquisition virtual platform. This reporting process is usually implemented through network protocols (such as TCP / IP) to ensure the real-time and reliability of the data. During the reporting process, the core switch of the backup ring network may need to perform identity authentication and permission checks with the OI / DA / IO Server to ensure the security and integrity of the data. Once the data is successfully reported to the OI / DA / IO Server, the data will be used for real-time monitoring, data analysis, fault diagnosis and other tasks, providing important support for the optimization and management of industrial processes.

[0145] The following description is made by taking the failure of the ring network access switch 11 in the ring network A as an example.

[0146] The main ring network core switch monitors the connection status of each access switch in the ring network A in real time through the ring network protocol (such as spanning tree protocols such as STP / RSTP / MSTP or specific ring network protocols). When the ring network access switch 11 fails, the main ring network core switch detects that it cannot receive data from the ring network access switches 11, 12, and 13 in the originally set clockwise direction.

[0147] In order to try to bypass the fault point, the main ring network core switch sends a request for counterclockwise data transmission to the ring network access switches 11, 12, and 13. This usually means that the transmission direction of the data packet will be changed from the original clockwise to counterclockwise. After receiving the request for counterclockwise data transmission, the ring network access switches 12 and 13 begin to adjust their forwarding rules to support counterclockwise data transmission.

[0148] After processing the request for counterclockwise data transmission, the ring network access switches 12 and 13 start to return data to the main ring network core switch. However, due to the failure of the ring network access switch 11, the main ring network core switch cannot receive the data return from the ring network access switch 11, thereby confirming that the ring network access switch 11 has indeed failed.

[0149] After confirming that a fault has occurred in ring network A, the backup ring network core switch sends a request for clockwise data transmission to ring network access switches 21, 22, and 23 through ring network B routing. After receiving the request for clockwise data transmission, ring network access switches 21, 22, and 23 begin to adjust their forwarding rules to support clockwise data transmission. After processing the request for clockwise data transmission, ring network access switches 21, 22, and 23 begin to return data to the backup ring network core switch. The backup ring network core switch successfully receives the data return from ring network access switches 21, 22, and 23, thereby confirming the feasibility of ring network B routing.

[0150] The core switch of the backup ring network retains the clockwise routing configuration of ring network B to ensure stable transmission of subsequent data.

[0151] PLC controller state switching:

[0152] At the same time, due to the fault in ring network A, PLC master controllers 11-13 cannot request data from OI / DA / IO Server, and PLC standby controllers 21-23 are activated to run state. PLC master controllers 11-13 are switched to hot standby state, ready to take over the work of PLC standby controllers when needed.

[0153] After being activated to the running state, the PLC standby controllers 21-23 start to send data requests to the OI / DA / IO Server. These data requests may include real-time data reading, device status query, etc.

[0154] After receiving the data requests from the standby PLC controllers 21 to 23, the OI / DA / IO Server starts to process the requests. After the processing is completed, the OI / DA / IO Server returns a data response to the standby PLC controllers 21 to 23.

[0155] The core switch of the standby ring network successfully collects data from the standby PLC controllers 21 to 23 through the ring network B route. These data are reported to the OI / DA / IO Server in real time by the core switch of the standby ring network.

[0156] Through the above steps, although the ring network access switch 11 in the ring network A fails, the entire system successfully realizes uninterrupted data collection and transmission through the cooperation of the backup ring network core switch and the PLC backup controller.

[0157] This ensures the continuity and stability of industrial processes and avoids data loss or control interruption due to network failure.

[0158] In summary, the above execution process involves multiple links such as fault detection, data transmission request, PLC controller state switching, data request and processing, and data acquisition. Through reasonable network design and fault switching strategy, the system can quickly restore data transmission and acquisition functions when a fault occurs, ensuring the normal operation of the industrial process.

[0159] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 2-3 The method steps of the embodiment shown in the figure can be found in the specific implementation process. Figure 2 The specific description of the illustrated embodiment will not be repeated here.

[0160] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the fault detection and device switching method described in the above embodiments.

[0161] See also Figure 4 , which provides a schematic diagram of the structure of a computer device according to an embodiment of the present application. The computer device may be Figure 1 The ring network core switch, ring network access switch, SCADA virtual platform, local SCADA equipment or PLC controller. Figure 4 As shown, the computer device 400 may include: at least one processor 40 , at least one network interface 404 , a user interface 403 , a memory 405 , and at least one communication bus 402 .

[0162] The communication bus 402 is used to realize the connection and communication between these components.

[0163] The user interface 403 may include a display screen (Display) and a camera (Camera), and the optional user interface 403 may also include a standard wired interface and a wireless interface.

[0164] The network interface 404 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0165] Among them, the processor 40 may include one or more processing cores. The processor 40 uses various interfaces and lines to connect the various parts of the entire computer device 400, and executes various functions and processes data of the computer device 400 by running or executing instructions, programs, code sets or instruction sets stored in the memory 405, and calling data stored in the memory 405. Optionally, the processor 40 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 40 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 40, and it can be implemented separately through a chip.

[0166] Among them, the memory 405 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 405 includes a non-transitory computer-readable storage medium. The memory 405 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 405 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 405 may also be optionally at least one storage device located away from the aforementioned processor 40. As Figure 4 As shown, the memory 405 as a computer storage medium may include an operating system, a network communication module, a user interface module and an application program.

[0167] exist Figure 4 In the computer device 400 shown in FIG. 1 , the user interface 403 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 40 can be used to call the application program stored in the memory 405 and specifically execute the following steps: Figure 2 The specific process can be referred to Figure 2-3 As shown, no further description is given here.

[0168] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0169] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A factory management and control system, characterized in that: include: At least one operator station, at least one engineer station, a main management core switch, a standby management core switch, a monitoring and control data acquisition virtual platform, a main ring network core switch, a standby ring network core switch, a ring network access switch 11 to a ring network access switch 1n, a ring network access switch 21 to a ring network access switch 2n, a PLC main controller 11 to a PLC main controller 1n, a PLC standby controller 21 to a PLC standby controller 2n, a local monitoring and control data acquisition device 1 to a local monitoring and control data acquisition device n; n is an integer greater than 1; Wherein, the main management core switch is connected to the standby management core switch; Each operator station is connected to the primary management core switch, and each operator station is connected to the backup management core switch; Each engineer station is connected to the primary management core switch, and each engineer station is connected to the backup management core switch; The main management core switch and the standby management core switch are respectively connected to the monitoring control data acquisition virtual platform; The main ring network core switch and the standby ring network core switch are respectively connected to the monitoring control data acquisition virtual platform; The main ring network core switch is connected to the standby ring network core switch; The main ring network core switch is connected to the ring network access switch 11, the ring network access switch 11 is connected to the ring network access switch 12, ..., the ring network access switch 1n is connected to the standby ring network core switch; the main ring network core switch, the ring network access switch 11 to the ring network access switch 1n, and the standby ring network core switch form a first ring network; The main ring network core switch is connected to the ring network switch 21, the ring network access switch 21 is connected to the ring network access switch 22, ..., the ring network access switch 2n is connected to the standby ring network core switch; the main ring network core switch, the ring network access switch 21 to the ring network access switch 2n, and the standby ring network core switch form a second ring network; The PCL main controller 11 is connected to the ring network access switch 11, the PCL main controller 12 is connected to the ring network access switch 12, ..., the PCL main controller 1n is connected to the ring network access switch 1n; The PLC standby controller 21 is connected to the ring network access switch 21, the PLC standby controller 22 is connected to the ring network access switch 22, ..., the PLC standby controller 2n is connected to the ring network access switch 2n; The local monitoring and control data acquisition device 1 is connected to the ring network access switch 11 and the ring network access switch 21 respectively, the local monitoring and control data acquisition device 2 is connected to the ring network access switch 12 and the ring network access switch 22 respectively, ..., the local monitoring and control data acquisition device n is connected to the ring network access switch 1n and the ring network access switch 2n respectively.

2. The system according to claim 1, characterized in that The main management core switch and the standby management core switch are configured as stack switches.

3. The system according to claim 1 or 2, characterized in that: The monitoring and control data acquisition virtual platform is installed with VMware software and AVEVA System Platform software. The VMware software creates multiple virtual machines based on hardware resources, and the AVEVA System Platform software is used to deploy multiple OI / DA / IO Servers, multiple AOSs and multiple Historian Servers in the created virtual machines.

4. The system according to claim 3, characterized in that The hardware resources of the monitoring and control data acquisition virtual platform are equal to the hardware resources required by the historical maximum load*150%.

5. A redundant control method, characterized in that: Applied to the engineering management and control system according to any one of claims 1 to 4, the redundant control method comprises: When the main ring network core switch detects that a line disconnection fault occurs in the first ring network, the PLC main controller 11 to the PLC main controller 1n are switched from the running state to the hot standby state, and the PLC standby controller 21 to the PLC standby controller 2n are activated from the hot standby state to the running state; the standby ring network core switch collects the equipment field data from the PLC standby controller 21 to the PLC standby controller 2n from the second ring network, and the standby ring network core switch reports the collected equipment field data to the OI / DA / IO Server in the data acquisition virtual platform; When the backup ring network core switch detects that the line of the second ring network is disconnected, the PLC backup controller 21~PLC backup controller 2n is switched from the running state to the hot standby state, and the PLC main controller 11~PLC main controller 1n is activated from the hot standby state to the running state; the main ring network core switch collects the equipment field data from the PLC main controller 11~PLC main controller 1n from the first ring network, and the main ring network core switch reports the collected equipment field data to the OI / DA / IO Server in the data acquisition virtual platform.

6. The method according to claim 5, characterized in that Also includes: When it is detected that the first ring network and the second ring network have line disconnection faults at the same time, the OI / DA / IO Server in the monitoring and control data acquisition virtual platform is switched to a hot standby state, and the local monitoring and control data acquisition devices 1 to n are activated to a running state; each local monitoring and control data acquisition device sends a data request to the corresponding PLC controller in the running state, and stores the equipment field data reported by the PLC controller; When it is detected that the line fault of any one of the first ring network and the second ring network is normal, the device field data stored locally in each local monitoring and control data acquisition device is reported to the OI / DA / IO Server in the monitoring and control data acquisition virtual platform, and then the OI / DA / IOServer in the monitoring and control data acquisition virtual platform is activated to the running state, and the local monitoring and control data acquisition devices 1 to local monitoring and control data acquisition devices n are switched to the hot standby state.

7. The method according to claim 5 or 6, characterized in that: Also includes: When the monitoring and control data acquisition virtual platform detects that any one of the AOS, OI / DA / IO Server and Historian Server fails, it uses idle hardware resources to create a virtual machine, and then the created virtual machine takes over the failed service.

8. The method according to claim 7, characterized in that Also includes: When the monitoring and control data acquisition virtual platform detects that all faults occur in AOS, OI / DA / IO Server and Historian Server, the OI / DA / IO Server in the monitoring and control data acquisition virtual platform is switched to hot standby state, and local monitoring and control data acquisition devices 1 to local monitoring and control data acquisition devices n are activated to running state; each local monitoring and control data acquisition device sends a data request to the corresponding PLC controller in running state, and stores the equipment field data reported by the PLC controller.

9. The method according to claim 8, characterized in that Also includes: When the main ring network core switch detects that an access switch failure occurs in the first ring network, the PLC main controller 11~PLC main controller 1n is switched from the running state to the hot standby state, and the PLC standby controller 21~PLC standby controller 2n is activated from the hot standby state to the running state; the standby ring network core switch collects the equipment field data from the PLC standby controller 21~PLC standby controller 2n from the second ring network, and the standby ring network core switch reports the collected equipment field data to the OI / DA / IO Server in the data acquisition virtual platform.

10. A computer storage medium, characterized in that: The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 5 to 9.

11. A computer device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 5 to 9.

Images