A cloud platform and method for industrial equipment operation and maintenance

Abstract

This invention discloses a cloud platform and method for industrial equipment operation and maintenance. The platform includes: a field device system, including a PLC controller, for acquiring operational data of the industrial equipment; a field sensing system, with Kepware industrial configuration software installed on terminal devices; the terminal devices are connected to the PLC controller to acquire and process the operational data; a data transmission system for uploading the processed operational data to a cloud database; a cloud platform backend system, on which virtual devices corresponding to the industrial equipment are deployed, storing the received operational data and adjusting the state of the virtual devices based on the operational data; and a cloud platform frontend system for visually displaying the state of the virtual devices. This invention, by installing Kepware industrial configuration software on the terminal devices, can significantly reduce equipment costs and is easy to implement. This invention can be widely applied in the field of Internet of Things (IoT) technology.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) technology, and in particular to a cloud platform and method for the operation and maintenance of industrial equipment. Background Technology

[0002] With the widespread application of high-end equipment, represented by industrial robots, these robots are integrated into the manufacturing, welding, and assembly processes of automotive parts production. Currently, the monitoring, debugging, and maintenance of equipment in factories mainly rely on factory technicians collecting and recording data on-site, or sometimes abandoning recording altogether due to the sheer volume of data. This results in factories expending significant manpower and resources on data collection. To resolve the conflict between the maintenance and debugging of robots and other equipment and the availability of technical maintenance personnel, as well as the conflict between reducing maintenance costs and the availability of spare parts for high-end equipment, connecting local factory equipment to the cloud allows factory managers and technicians to monitor the robot system's operational status from anywhere, anytime, via network resources and specific domain names. This data can be stored long-term in the cloud, enabling accurate retrieval and analysis when needed. Connecting equipment data to the cloud, through data analysis and processing, also provides early warning functions. When equipment malfunctions, an alarm can be triggered, and abnormal equipment data can be promptly notified to factory management. This can significantly reduce economic losses caused by malfunctions, achieving intelligent maintenance and reducing the need for maintenance technicians.

[0003] Existing cloud platforms have the following drawbacks: 1) High deployment difficulty: Dedicated gateways are required for data collection, followed by uploading to the cloud. This process demands engineers learn new technologies (commonly OPCUA), new programming languages ​​(commonly C#), and write data transmission and reception modules, storage modules, etc., from the ground up. The development cycle is long, and the learning cost is high. 2) Poor scalability and portability: The modules are often designed for specific PLCs. Different PLCs have different memory partitions and variable reading rules. If a PLC from a different manufacturer is encountered, the transmission and reception modules, storage modules, etc., need to be rewritten. Summary of the Invention

[0004] In order to at least partially solve one of the technical problems existing in the prior art, the purpose of this invention is to provide a cloud platform and method for the operation and maintenance of industrial equipment.

[0005] The technical solution adopted in this invention is:

[0006] An industrial equipment operation and maintenance cloud platform, comprising:

[0007] Field device systems, including PLC controllers, are used to acquire operating data from industrial equipment;

[0008] The field sensing system includes at least one terminal device, on which Kepware industrial configuration software is installed; the terminal device is connected to the PLC controller and is used to acquire and process the operating data of the industrial equipment.

[0009] A data transmission system, connected to the terminal device, is used to upload the processed operational data to a cloud database;

[0010] The cloud platform backend system deploys virtual devices corresponding to industrial equipment, stores received operational data, and adjusts the state of the virtual devices based on the operational data. In practical applications, the cloud platform backend system refers to a server or a terminal PC deployed on a public network / local area network.

[0011] The cloud platform front-end system is used to visually display the status of virtual devices.

[0012] Furthermore, based on Kepware industrial configuration software, the terminal device is equipped with a PLC acquisition module plugin and a Data Logger plugin;

[0013] The PLC acquisition module plugin, as a plugin in the Kepware industrial configuration software, is used to be compatible with PLC controllers and to read data from the PLC controllers.

[0014] The DataLogge plugin, as a plugin in the Kepware industrial configuration software, is used to upload data from the Kepware industrial configuration software to a preset cloud database.

[0015] Furthermore, the Kepware industrial configuration software acquires operational data in the following ways:

[0016] Obtain operational data using either a trigger-based or fixed-period method;

[0017] Configure a unique ID for each piece of acquired runtime data; based on this ID, the cloud platform backend system will match the runtime data to the corresponding virtual device.

[0018] Furthermore, the Kepware industrial configuration software sets the format of the runtime data in the following manner:

[0019] Configure attributes for the running data, including the data name, write time, and value; the attributes correspond one-to-one with the fields in the database table.

[0020] Furthermore, the cloud platform backend system processes the received operational data as follows:

[0021] After receiving the runtime data, the corresponding virtual device is matched based on the ID information using a table lookup method, and the runtime data is stored in the corresponding storage space.

[0022] Equipment faults are detected based on operational data, and the status of virtual devices is adjusted based on the detection results.

[0023] Furthermore, the cloud platform backend system is developed based on the Spring Boot framework, which includes Mybatis plugin, Redis plugin, and Nginx plugin.

[0024] Furthermore, the terminal device is a PC terminal or an industrial control computer terminal.

[0025] Furthermore, the industrial equipment is equipped with a workstation sensor, which includes at least one of a position sensor, an angle sensor, a temperature sensor, a battery valve sensor, or a voltage and current sensor.

[0026] Furthermore, the workstation sensor is either a sensor built into the industrial equipment or an additional sensor.

[0027] Another technical solution adopted in this invention is:

[0028] The method for building a cloud platform for the operation and maintenance of industrial equipment, as described above, includes the following steps:

[0029] Workstation sensors are installed on industrial equipment, and the operating data collected by the workstation sensors is read by a PLC controller;

[0030] Deploy terminal devices at the equipment site, install Kepware industrial configuration software on the terminal devices, and connect the terminal devices to the PLC controller;

[0031] Each piece of operational data is configured with a unique ID using Kepware industrial configuration software, and the operational data is then sent to the cloud platform backend system.

[0032] After receiving the operational data, the cloud platform backend system stores the operational data according to the ID information and adjusts the status of the virtual devices; the virtual devices correspond one-to-one with the industrial equipment.

[0033] The beneficial effects of this invention are: by installing Kepware industrial configuration software on terminal devices as a field sensing system, this invention can significantly reduce equipment costs and is easy to implement. Furthermore, Kepware industrial configuration software is compatible with various PLC controllers and can be widely adapted to different industrial equipment. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following description is provided with accompanying drawings of the relevant technical solutions in the embodiments of the present invention or the prior art. It should be understood that the accompanying drawings described below are only for the purpose of clearly illustrating some embodiments of the technical solutions of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0035] Figure 1 This is a structural block diagram of the field equipment system in an embodiment of the present invention;

[0036] Figure 2 This is a structural block diagram of the field sensing system in an embodiment of the present invention;

[0037] Figure 3 This is a structural block diagram of the cloud platform backend system in an embodiment of the present invention;

[0038] Figure 4 This is a structural block diagram of the cloud platform front-end system in an embodiment of the present invention. Detailed Implementation

[0039] The embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention. The step numbers in the following embodiments are set only for ease of explanation, and there is no limitation on the order between the steps. The execution order of each step in the embodiments can be adaptively adjusted according to the understanding of those skilled in the art.

[0040] In the description of this invention, it should be understood that the orientation descriptions, such as up, down, front, back, left, right, etc., are based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limiting this invention.

[0041] In the description of this invention, "several" means one or more, "more than" means two or more, "greater than," "less than," and "exceeding" are understood to exclude the stated number, while "above," "below," and "within" are understood to include the stated number. The use of "first" and "second" in the description is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly indicating the number of indicated technical features, or implicitly indicating the order of the indicated technical features.

[0042] In the description of this invention, unless otherwise explicitly defined, terms such as "set up," "install," and "connect" should be interpreted broadly, and those skilled in the art can reasonably determine the specific meaning of the above terms in this invention in conjunction with the specific content of the technical solution.

[0043] Terminology Explanation:

[0044] MyBatis: MyBatis is an excellent persistence layer framework that supports customized SQL, stored procedures, and advanced mapping. MyBatis avoids almost all JDBC code and the need for manually setting parameters and retrieving result sets. MyBatis can use simple XML or annotations to configure and map native information, mapping interfaces and Java POJOs (Plain Ordinary Java Objects) to records in the database.

[0045] Redis: Redis is a key-value storage system. Similar to Memcached, it supports a wider range of value types, including string, list, set, sorted set (zset), and hash. These data types support push / pop, add / remove, intersection, union, difference, and more complex operations, all of which are atomic. Furthermore, Redis supports various sorting methods. Like Memcached, data is cached in memory for efficiency. The difference is that Redis periodically writes updated data to disk or appends modification operations to a log file, and it also implements master-slave synchronization.

[0046] Nginx: Nginx (engine x) is a high-performance HTTP and reverse proxy web server that also provides IMAP / POP3 / SMTP services. Developed by Igor Sysoev for Rambler.ru (Russian: Рамблер), Russia's second most visited website, Nginx's public version 1.19.6 was released on December 15, 2020. Its source code is released under a BSD-like license and is known for its stability, rich feature set, simple configuration files, and low system resource consumption. On January 25, 2022, nginx 1.21.6 was released. Nginx is a lightweight web server / reverse proxy server and email (IMAP / POP3) proxy server, released under a BSD-like license. Its characteristics include low memory consumption and high concurrency; in fact, nginx's concurrency performance is better than other web servers of its type.

[0047] Spring Boot: Spring Boot is a new framework provided by the Pivotal team, designed to simplify the initial setup and development process of new Spring applications. This framework uses specific configuration methods, eliminating the need for developers to define boilerplate configurations. The Spring framework features Inversion of Control (IoC), which aims to facilitate project maintenance and testing. It provides a unified method for configuring and managing Java objects through Java reflection. The Spring framework utilizes a container to manage the lifecycle of objects. The container can configure objects by scanning XML files or specific Java annotations on classes, and developers can obtain objects through dependency lookup or dependency injection. The Spring framework includes an Aspect-Oriented Programming (AOP) framework. The Spring AOP framework is based on the proxy pattern and is configurable at runtime; the AOP framework primarily modularizes cross-concerns between modules.

[0048] HTML: HTML stands for Hypertext Markup Language, a markup language. It consists of a series of tags. These tags unify the format of documents on the web, connecting scattered Internet resources into a logical whole. HTML text is descriptive text composed of HTML commands, which can specify text, graphics, animations, sounds, tables, links, etc.

[0049] CSS (Cascading Style Sheets) is a computer language used to style HTML (an application of Standard Generalized Markup Language) or XML (a subset of Standard Generalized Markup Language) documents. CSS can not only statically format web pages, but also dynamically format elements on a webpage in conjunction with various scripting languages. CSS allows for pixel-level precise control over the layout and positioning of elements on a webpage, supports almost all font sizes and styles, and has the ability to edit the styles of webpage objects and models.

[0050] JavaScript: JavaScript (abbreviated as "JS") is a lightweight, interpreted or just-in-time (JIT) programming language with a function-first approach. Although it is best known as a scripting language for developing web pages, it is also used in many non-browser environments. JavaScript is a prototype-based, multi-paradigm dynamic scripting language that supports object-oriented, imperative, declarative, and functional programming paradigms.

[0051] Vue: Vue is an open-source JavaScript framework for creating user interfaces and a web application framework for creating single-page applications. Vue focuses on the view layer in the MVC pattern. At the same time, it can easily obtain data updates and realize the interaction between the view and the model through specific methods inside the components.

[0052] This embodiment provides a remote operation and maintenance platform for the automotive industry based on the Internet of Things (IoT) and industrial cloud. The platform, built upon welding workstations and internet resources, enables cloud-based visualization of automotive welding equipment factories, data traceability, and equipment fault alarms. The technical solution involves reading data from each workstation via a local area network (LAN) and PLCs on-site. Data is collected from the PLCs and then transferred to the industrial configuration software via PCs deployed on-site. The collected data is transmitted via Ethernet to a designated server on the public network. This server is configured with a relational database for storing the on-site data. A Java backend project developed using Spring Boot also runs on this server. This backend project adds, deletes, modifies, and queries data from the database, categorizes, processes, and stores the data, and returns the query results to the user interface. Users can access factory and equipment-related data by logging into a designated domain name after running the frontend project on their terminal devices.

[0053] Specifically, the remote operation and maintenance platform includes: field equipment system, field sensing system, data transmission system, cloud platform backend system, and cloud platform frontend system.

[0054] Among them, see Figure 1 The field equipment system includes field welding workstation equipment, workstation actuators, workstation sensors, and PLC controllers.

[0055] See Figure 2 The field sensing system includes a PLC acquisition module plug-in, a Data Logger plug-in, an ODBC token, Kepware industrial configuration software, and a personal PC terminal or industrial control computer terminal.

[0056] The data transmission system includes communication methods that can access Ethernet, such as Ethernet network, WIFI, or 4G / 5G network, to transmit on-site data to the cloud server.

[0057] See Figure 3 The cloud platform's backend system includes relational databases, Mybatis, Redis, Nginx, and Spring Boot.

[0058] See Figure 4 The cloud platform's front-end system includes HTML, CSS, JavaScript, and Vue. HTML, CSS, and JavaScript form the technology stack for user interaction, used to create the system's web-based interface and display data. Vue is the system framework for the front-end system, integrating and developing the aforementioned HTML, CSS, and JavaScript.

[0059] As an alternative implementation, the field welding workstation equipment includes a rotary robotic arm, a turntable, and a fixture for an industrial robot.

[0060] As an alternative implementation, field workstation sensors include position sensors, angle sensors, temperature sensors, solenoid valve sensors, voltage and current sensors, etc., for industrial robot spindles, turntables, and grippers.

[0061] As an alternative implementation, the field workstation actuator includes an electric and pneumatic drive on the rotary arm, turntable, and gripper of an industrial robot.

[0062] As an optional implementation method, the PLC acquisition module plug-in is a plug-in in the Kepware configuration software. It is developed based on the OPCUA protocol and can perform data transmission functions with other plug-ins in the configuration software. It is also compatible with most mainstream PLC devices on the market and can read data from these PLC devices through simple configuration.

[0063] As an optional implementation, the Data Logger acquisition module plugin is a plugin in the Kepware configuration software, developed based on the Opcua protocol, which can upload data from the configuration software to a specified cloud database.

[0064] As an optional implementation, the ODBC token is a unique identifier for the cloud database on the public network, and it is configured with the public IP address of the cloud database and the port number on which the software runs.

[0065] The aforementioned Kepware industrial configuration software is compatible with other plug-ins that use OPCUA as the communication method. These plug-ins can exchange and transmit data via a communication protocol. This Kepware industrial configuration software needs to run on the personal PC or industrial control computer terminal.

[0066] As an optional implementation, the relational database contains instance data that uniquely corresponds to the field data, and receives field equipment data.

[0067] As an optional implementation, Mybatis, Redis, and Nginx are used as plugins for the backend system to improve backend development efficiency and offer high compatibility and convenience. Spring Boot is the system framework for the backend system, integrating Mybatis, Redis, and Nginx for development.

[0068] This embodiment also provides a method for implementing a remote operation and maintenance platform for welding machinery, including the following steps:

[0069] The first step is to set up the field equipment system. This involves installing field workstation sensors on the field welding workstation equipment, including position sensors, angle sensors, temperature sensors, solenoid valve sensors, voltage and current sensors, etc. These sensors can be integrated into the equipment or added separately. Next, install field workstation actuators, including electric and pneumatic drive units. The PLC controller reads the workstation sensor data and sends commands to the field workstation actuators.

[0070] The second step is to build a field sensing system. This involves deploying the Kepware industrial configuration software runtime environment on personal PCs or industrial control computers in the field. The PLC acquisition module plug-in connects to the field PLC device via Ethernet, reads data from the PLC controller, and transmits the data to the Kepware configuration software via the OPCUA communication protocol. The Data Logger plug-in retrieves data from the configuration software and obtains the specified server and software port information from the ODBC token. This data is then written to the cloud database via network transmission methods such as Ethernet / WIFI / 4G / 5G network.

[0071] During the activation of the Data Logge plugin, the following configurations are required: 1) Configure the method by which the Kepware industrial configuration software obtains data from the PLC controller; 2) Configure the format of the data sent by the Kepware industrial configuration software.

[0072] Regarding part 1): Kepware industrial configuration software can acquire data by triggering acquisition when data changes or by triggering acquisition at fixed periods. Additionally, Kepware industrial configuration software requires configuring the data range; data can be imported in groups or selected as individual data points. A unique ID is configured for each data point; the rules for setting this ID can be pre-defined, and when data is written to the database, it can be allocated to the storage space of the specified device using this ID.

[0073] Regarding part 2): When sending data to the cloud database, attribute configuration is required. Attributes mainly include data name, write time, and value. These attributes are matched one-to-one with fields in the database table, which needs to be pre-defined. Later, during data parsing, the corresponding data is written to the corresponding fields based on the attributes. In addition to the above-mentioned attributes, an additional data ID attribute, as described above, needs to be added. Based on the configured attributes, when a new data packet is received, the data in the database is automatically updated according to the data packet content, which includes the data name, write time, value, and named ID.

[0074] The third step involves the cloud platform's backend system retrieving the original data written from the database. Each data entry includes a data name, write time, current status, and a specific flag (i.e., the ID mentioned above). Within the cloud platform's backend system, production lines and virtual devices are pre-established, each corresponding one-to-one with offline industrial equipment, and the ID is bound to the virtual device.

[0075] In a Java backend project, multiple data monitors detect the written data and, based on the ID information, write the data to the virtual device that matches that ID. Specifically, the mapping between IDs and virtual devices is recorded in a pre-defined table, which specifies the device and production line inclusion relationship for each piece of data. By looking up the table, the production line and virtual device matching the data are retrieved.

[0076] The backend system uses a technology stack including Mybatis, Redis, and Nginx to perform secondary processing on the raw data. The data is first divided into real-time and historical data. Real-time data is then distributed across different production lines and devices for user viewing. Historical data is stored according to write time, device, etc. Furthermore, historical data can also be used to predict and determine the source of faults, providing data analysis for early warning and alarm modules.

[0077] The fourth step involves the welding equipment management personnel accessing a specific webpage through the deployed cloud platform front-end system. On this webpage, they create virtual equipment and virtual production lines with the same parameters as the physical equipment, and establish the inclusion relationship between these virtual equipment and production lines through a visual interface. Based on this, data is allocated to different devices using unique data address information for each piece of data, establishing the inclusion relationship between individual data and devices. When there are changes or modifications to the data, equipment, or production lines, these data can be added, deleted, or modified through the front-end visual interface.

[0078] The fifth step is to map the physical production lines onto the virtual data. Company personnel can log into a designated webpage to view the real-time operation of different production lines and equipment. System data can be divided into real-time and historical data. When users need to view real-time data, they select the corresponding production line and equipment. Based on the visual interface, the data can be displayed numerically or as a line graph.

[0079] The sixth step is that enterprise personnel can see the system's prompts for real-time abnormal data in the cloud platform front-end system, as well as a summary report of the abnormal messages. The summary report includes information such as data name, device, line, write time, error value, correct value, and cause of the abnormality.

[0080] In the seventh step, enterprise personnel can view and trace the historical information of devices in the cloud platform's front-end system. By selecting the device and time period, they can query the device's data operation status during that time period. For a more intuitive presentation, the data also supports display through visual icons, and data can be added or deleted at will, facilitating horizontal comparison.

[0081] In summary, this embodiment has the following advantages and beneficial effects compared to the corresponding technology:

[0082] (1) Functionally, it can remotely monitor and control equipment in real time via network resources, and quickly obtain the operating status of local equipment in the factory. It can browse, statistically analyze, and perform analysis of real-time data and historical parameter information related to production within the platform, and has an early warning function. It has a high degree of intelligence and can effectively improve production efficiency and product qualification rate.

[0083] (2) In terms of deployment and use, this platform only requires the addition of a PC device that can be connected to the Internet. No additional gateways, routers, collectors or other peripheral components are required. No additional data cable connection is required. Only the network cable needs to be connected to the PLC main unit, which can greatly reduce the difficulty and cost of deployment.

[0084] (3) In terms of extended use, this embodiment uses Kepware industrial configuration software to collect data from all PLC devices on site. Kepware industrial configuration software comes with multiple PLC acquisition protocols, enabling seamless data collection from various brands and protocols of PLCs on site. No matter how many different brands of equipment are added, the data can be collected seamlessly into Kepware industrial configuration software. At the same time, the data is uniquely identified by the datalogger plugin, which standardizes differentiated data according to the same dimension, making it convenient for classification and storage after entering the database.

[0085] In some alternative embodiments, the functions / operations mentioned in the block diagrams may not occur in the order shown in the operation diagrams. For example, depending on the functions / operations involved, two consecutively shown blocks may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order. Furthermore, the embodiments presented and described in the flowcharts of this invention are provided by way of example to provide a more comprehensive understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is altered and sub-operations described as part of a larger operation are executed independently.

[0086] Furthermore, although the invention has been described in the context of functional modules, it should be understood that, unless otherwise stated, one or more of the described functions and / or features may be integrated into a single physical device and / or software module, or one or more functions and / or features may be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding the invention. Rather, given the properties, functions, and internal relationships of the various functional modules in the apparatus disclosed herein, the actual implementation of the module will be understood within the scope of conventional skill of an engineer. Therefore, those skilled in the art can implement the invention as set forth in the claims using ordinary techniques without excessive experimentation. It is also understood that the specific concepts disclosed are merely illustrative and not intended to limit the scope of the invention, which is determined by the full scope of the appended claims and their equivalents.

[0087] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0088] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0089] More specific examples of computer-readable media (a non-exhaustive list) include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0090] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0091] In the foregoing description of this specification, references to terms such as "one embodiment," "another embodiment," or "some embodiments" indicate that a specific feature, structure, material, or characteristic described in connection with an embodiment or example is included in at least one embodiment or example of the present invention. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0092] Although embodiments of the invention have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.

[0093] The above is a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. An industrial equipment operation and maintenance cloud platform, characterized in that, The application relates to a system for monitoring industrial equipment, which comprises the following: a field device system comprising a PLC controller for acquiring operation data of industrial equipment; a field perception system comprising at least one terminal device, wherein a kepware industrial configuration software is installed on the terminal device; the terminal device is connected with the PLC controller, and is used for acquiring operation data of industrial equipment and processing the operation data; a PLC acquisition module plug-in and a Data Logge plug-in are arranged on the terminal device; the PLC acquisition module plug-in is used as a plug-in in the kepware industrial configuration software, is used for being compatible with the PLC controller, and is used for reading data of the PLC controller; the Data Logge plug-in is used as a plug-in in the kepware industrial configuration software, and is used for uploading data in the kepware industrial configuration software to a preset cloud database; the kepware industrial configuration software acquires operation data in a triggering mode or a fixed cycle mode; unique ID information is configured for each obtained operation data; based on the ID information, a cloud platform back-end system matches the operation data to corresponding virtual equipment; the kepware industrial configuration software sets the format of operation data by configuring attributes of the operation data, and the attributes comprise a data name, a writing time and a value; the attributes correspond to fields in a database table one by one; a data transmission system for uploading the processed operation data to the cloud database; a cloud platform back-end system, wherein virtual equipment corresponding to the industrial equipment is deployed on the cloud platform back-end system; after receiving the operation data, the cloud platform back-end system matches corresponding virtual equipment according to ID information in a table lookup mode, and stores the operation data in a corresponding storage space; equipment fault detection is carried out according to the operation data, and the state of the virtual equipment is adjusted according to a detection result; a cloud platform front-end system for visually displaying the state of the virtual equipment.

2. The industrial equipment operation and maintenance cloud platform of claim 1, wherein, The cloud platform back-end system is developed based on a Spring Boot framework, and the Spring Boot framework comprises a Mybatis plug-in, a Redis plug-in and an Nginx plug-in.

3. The industrial equipment operation and maintenance cloud platform of claim 1, wherein, The terminal device is a PC terminal or an industrial computer terminal.

4. The industrial equipment operation and maintenance cloud platform of claim 1, wherein, The industrial equipment is provided with a workstation sensor, and the workstation sensor comprises at least one of a position sensor, an angle sensor, a temperature sensor, a battery valve sensor or a voltage and current sensor.

5. The industrial equipment operation and maintenance cloud platform of claim 4, wherein, The workstation sensor is a sensor that is self-provided by the industrial equipment or is additionally arranged.

6. The method for building an industrial equipment operation and maintenance cloud platform according to any one of claims 1-5, characterized in that, The system comprises the following steps: installing a workstation sensor on industrial equipment, and reading operation data collected by the workstation sensor through a PLC controller; deploying a terminal device on a device site, installing a kepware industrial configuration software on the terminal device, connecting the terminal device with the PLC controller, and arranging a PLC acquisition module plug-in and a Data Logge plug-in on the terminal device; configuring unique ID information for each operation data through the kepware industrial configuration software, and sending the operation data to a cloud platform back-end system. After the cloud platform backend system receives the running data, the corresponding virtual device is matched according to the ID information, and the running data is stored; the device fault is detected according to the running data, and the state of the virtual device is adjusted according to the detection result; the virtual device corresponds to the industrial device one by one.

Images