Device management method, device, device and storage medium

Abstract

The present invention proposes an equipment management method, apparatus, device and storage medium, the method comprising obtaining a query keyword input by a user, querying an equipment model from a model library, and creating a new model if the equipment model is not found in the model library; selecting the equipment model from the model library and constructing an equipment instance; obtaining a configuration instruction input by a user, configuring an equipment model component of the equipment instance, and defining an equipment collection point corresponding to the equipment instance in the equipment model component; obtaining a real-time parameter value of the equipment collection point, and displaying the real-time parameter value through a data chart of the equipment instance; judging whether the equipment instance triggers an alarm event, and if so, executing an alarm action associated with the alarm event; the present invention flexibly defines equipment models, has high compatibility, can greatly reduce the cost of secondary development of the system, and effectively solves the problems of poor flexibility, high development cost and low development efficiency of existing factory equipment management systems.

Description

Technical Field

[0001] The present invention relates to the technical field of equipment management, and in particular to an equipment management method, apparatus, device and storage medium. Background Art

[0002] With the continuous development of the Internet of Things in the textile printing and dyeing industry, intelligent equipment has begun to penetrate into various printing and dyeing factories. Printing and dyeing equipment generally transmits equipment operating parameters to a control management system through various sensors. Managers manage the printing and dyeing equipment in a unified manner through the equipment management system. However, there are many types of printing and dyeing equipment purchased by the factory, including setting machines, dyeing machines, water meters, etc. The parameter management systems of different types of equipment have different compatibility. The same type of equipment may not all come from the same brand or manufacturer, and their operating parameters may also have compatibility conflicts. Therefore, it is difficult for the existing equipment management system to be managed uniformly in the same system, and the factory needs to carry out secondary development of the management system. Moreover, the equipment used in each factory will be different, so it is necessary to carry out targeted secondary development of the management system of each factory, which greatly increases the cost. When the factory adds equipment, the system still needs to be developed and used again, which has poor flexibility, cumbersome operation, low efficiency, and increased costs. Summary of the invention

[0003] In view of the above-mentioned defects, the purpose of the present invention is to propose an equipment management method, device, equipment and storage medium to solve the problems of poor flexibility, high development cost and low development efficiency of existing factory equipment management systems.

[0004] To achieve this object, the present invention adopts the following technical solutions:

[0005] A device management method comprises the following steps:

[0006] Obtaining the query keyword input by the user, querying the device model from the model library, and creating a new model if the device model is not found in the model library;

[0007] Select the device model from the model library to build a device instance;

[0008] Acquire a configuration instruction input by a user, configure a device model component of the device instance, and define a device collection point corresponding to the device instance in the device model component;

[0009] Acquire the real-time parameter value of the device collection point, and display the real-time parameter value through a data chart of the device instance;

[0010] Determine whether the device instance triggers an alarm event, and if so, execute the alarm action associated with the alarm event.

[0011] Preferably, the method for creating a new model comprises the following steps:

[0012] Get a new model instruction, and create a new model in the database.

[0013] Receive the parameter information input by the user, and create and configure the following basic parameter definitions for the new model:

[0014] Creating and configuring static attributes to modify fixed attribute information defining the device model;

[0015] Create and configure acquisition parameters, modify and define the parameter information that can be obtained by the device model;

[0016] Create and configure event definitions, modify alarm rules that define trigger thresholds for the alarm events, and define the alarm actions;

[0017] Creating and configuring state value definitions, modifying the states of the device model and the parameter value attributes corresponding to the states;

[0018] Create and configure alarm code definitions, modify the alarm code, alarm description, alarm type and other information and their mapping relationships of the device model;

[0019] Create and configure custom parameters; modify model metrics that define user-defined algorithms.

[0020] Preferably, before selecting the device model from the model library and constructing the device instance, the method further includes receiving a copy instruction, selecting and copying the device model from the model library, and forming a new model by configuring the device model.

[0021] Preferably, in configuring the device model component of the device instance, the method further includes independently editing, adding or deleting the parameter definition of the device model in the device model component of the device instance:

[0022] Independently edit and modify the original parameter definition of the device model in the device instance;

[0023] or, independently adding parameter definitions of the device model in the device instance;

[0024] Or, independently delete the parameter definition of the device model in the device instance.

[0025] Preferably, the method further comprises independently editing, adding or deleting parameter definitions of the device model in the model library:

[0026] Independently edit and modify the original parameter definition of the device model in the model library;

[0027] or, independently adding parameter definitions of the device model in the model library;

[0028] Or, independently delete the parameter definition of the device model in the model library.

[0029] Preferably, in configuring the device collection point corresponding to the device model, the method further includes the step of generating an alarm for missing the device collection point:

[0030] Determine whether each acquisition parameter in the device model corresponds to the device acquisition point. Otherwise, a prompt will pop up indicating that the acquisition parameter is missing the device acquisition point.

[0031] Preferably, the method further comprises a device query step:

[0032] Configure the device name, device type, device status, alarm type and parameter information corresponding to the device model in the device card;

[0033] Get the query keywords;

[0034] The device models related to the keywords are retrieved from the device cards, and the retrieved device models are listed.

[0035] The present application also proposes a device management apparatus, comprising:

[0036] Model library, used to store device models and parameter definitions of device models;

[0037] The model query module is used to obtain the query keywords input by the user and query the device model from the model library;

[0038] Model creation module, used to create new models;

[0039] A device instance construction module, used for selecting the device model from the model library to construct a device instance;

[0040] A parameter configuration module, used to obtain a configuration instruction input by a user, configure a device model component of the device instance, and define a device collection point corresponding to the device instance in the device model component;

[0041] A parameter acquisition module, used to obtain the real-time parameter values ​​of the equipment collection points;

[0042] A display module, used for displaying the real-time parameter value obtained by the parameter obtaining module through a data chart of the device instance;

[0043] A determination module, used to determine whether the device instance triggers an alarm event;

[0044] The execution module is used to execute the alarm action associated with the alarm event.

[0045] The present application further proposes a device management device, comprising a memory storing executable program code; a processor coupled to the memory; the processor calls the executable program code stored in the memory to execute the device management method.

[0046] The present application further proposes a computer storage medium, wherein the computer storage medium stores computer instructions, and the computer instructions are used to execute the device management method when called.

[0047] One of the above technical solutions has the following advantages or beneficial effects:

[0048] Create device instances based on the established device model to achieve fast and flexible batch creation of device instances; obtain real-time parameter data from production equipment in actual production, display the real-time parameter values ​​through the device model, and monitor the production equipment by determining whether to trigger an alarm event, thereby achieving unified management of the entire production instance and solving the problem that devices from different manufacturers are not compatible in the same system, resulting in the inability to manage them uniformly. In addition, this application has high compatibility by flexibly defining device models, which can greatly reduce the cost of secondary development of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 It is a flowchart of an embodiment of the device management method proposed by the present invention;

[0050] Figure 2 is a flow chart of another embodiment of the device management method proposed by the present invention;

[0051] Figure 3 It is a schematic diagram of module connections in an embodiment of the equipment management device proposed by the present invention. DETAILED DESCRIPTION

[0052] The embodiments of the present invention are described in detail below. Examples of the embodiments are shown in the drawings. The embodiments described below with reference to the drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0053] In the description of the embodiments of the present invention, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present invention, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0054] like Figure 1-2 As shown, a device management method includes the following steps: obtaining a query keyword input by a user, querying a device model from a model library, and creating a new model if the device model is not found in the model library;

[0055] Select the device model from the model library to build a device instance;

[0056] Acquire a configuration instruction input by a user, configure a device model component of the device instance, and define a device collection point corresponding to the device instance in the device model component;

[0057] Acquire the real-time parameter value of the device collection point, and display the real-time parameter value through a data chart of the device instance;

[0058] Determine whether the device instance triggers an alarm event, and if so, execute the alarm action associated with the alarm event.

[0059] Specifically, the method allows the user to flexibly create the device instance, and complete the management model of the device instance by copying the device model in the model library to the device instance. When the required device model is not available in the database, the device model can be newly created to define new parameter definitions; the device instance is created according to the established device model, and after selecting the model, all parameter configurations, status configurations, alarm event configurations, etc. of the device model are copied to the device instance, so as to achieve fast and flexible batch creation of the device instance; data parameters are obtained from production equipment in actual production, and the real-time parameter values ​​of the device collection points are associated with the corresponding device model in the model of the device instance, and the real-time parameter values ​​are displayed through the device model, and the production equipment is monitored by judging whether an alarm event is triggered, so as to achieve unified management of the entire production instance, solve the problem that devices from different manufacturers are not compatible in the same system, and thus cannot be managed uniformly, and the application has high compatibility by flexibly defining the device model, which can greatly reduce the cost of secondary development of the system;

[0060] An embodiment of applying the present application to printing and dyeing production is proposed. First, a new instance is created and named as the printing and dyeing instance. The equipment that needs to be managed in the printing and dyeing workshop, including bleaching machines, rolling dyeing machines, printing machines, baking machines, washing machines, etc., is searched and queried from the model library, and the searched equipment model is copied to the printing and dyeing instance. If the printing machine is not found in the model library, a new blank model is created in the model library, and relevant parameter definitions are configured on the printing machine model. The data provided by the printing machine data interface is completely configured on the printing machine model, thereby completing the construction of the printing machine model. The printing machine model is then copied from the model library to the printing and dyeing instance, and all the equipment that needs to be managed in the printing and dyeing production workshop are matched one by one. After the model is built in the printing and dyeing instance, the equipment model in the printing and dyeing instance is matched with the production equipment corresponding to the printing and dyeing production workshop. The production equipment corresponding to the printing and dyeing production workshop is matched with the parameters. Equipment is generally provided with data collection point output. After the operating parameter data of the production equipment is obtained through the collection point, the parameters are sent to the equipment model corresponding to the printing and dyeing instance. For example, the temperature, operating speed, operating time and other information of the roller dyeing machine in the production workshop are obtained. The roller dyeing machine model in the printing and dyeing instance will display the obtained information. The staff can directly obtain the parameter data of the roller dyeing machine in actual production from the roller dyeing machine model. Similarly, the data of other equipment in the production workshop will also be synchronized to the corresponding equipment model for display. The staff can uniformly manage and monitor all equipment in the workshop through the equipment model simulated in the printing and dyeing instance; alarm events are set in the bleaching machine model, roller dyeing machine model, printing machine model, baking machine model, and washing machine model. If the equipment model triggers an alarm event, a message will be sent to inform the staff, thereby realizing safety monitoring of the workshop.

[0061] Furthermore, creating a new model includes the following steps:

[0062] Get a new model instruction, and create a new model in the database.

[0063] Receive the parameter information input by the user, and create and configure the following basic parameter definitions for the new model:

[0064] Creating and configuring static attributes to modify fixed attribute information defining the device model;

[0065] Create and configure acquisition parameters, modify and define the parameter information that can be obtained by the device model;

[0066] Create and configure event definitions, modify alarm rules that define trigger thresholds for the alarm events, and define the alarm actions;

[0067] Creating and configuring state value definitions, modifying the states of the device model and the parameter value attributes corresponding to the states;

[0068] Create and configure alarm code definitions, modify the alarm code, alarm description, alarm type and other information and their mapping relationships of the device model;

[0069] Create and configure custom parameters; modify model metrics that define user-defined algorithms.

[0070] The device instances constructed in this application are highly compatible. New devices can be defined by creating new models and defining various parameters of the new devices according to the needs of the devices.

[0071] Static attributes describe the fixed attribute information of the model and are not mandatory, such as device brand, model, and specifications.

[0072] Collection parameters define the parameter information that the model can obtain from the edge / sensor. The identifier in the collection parameters needs to obtain data from the data processing platform interface. After selecting the production equipment in the corresponding data collection module, the collection path of all parameters is the ID by default, and the parameters can modify the collection path separately. When selecting a production equipment, you cannot select a production equipment that has been associated with an instance.

[0073] Event definition, define and edit alarm rules, define the threshold of identifiers to trigger alarms and other actions, support the creation and editing of multiple rules, and support the push of trigger action event notifications when conditions are met, such as: when the water volume is greater than 50L, push message rule logic definition, and support setting message push configuration code in event definition;

[0074] Status value definition, defines the escape of parameter enumeration of machine model device status. Some status values ​​are device status attributes composed of multiple parameters, such as: device status = combination of MachineStateInt and OnLine parameters, which respectively display running, stopped, offline, and online. The values ​​obtained by custom status values ​​are stored in time series (used to generate the fluctuation history of each parameter of device operation within the statistical time period) and are tentatively stored for 5 years.

[0075] Alarm code definition, defines the mapping relationship between the alarm code, alarm description, alarm type and other information of the model, such as: Alarm, alarm code 101 = cabinet temperature is too high; the alarm code definition supports setting the message push configuration code; each rule in the event in the alarm code definition (that is, each alarm code) will be triggered separately, and each rule has a level, including severe alarm, important alarm, and general alarm;

[0076] Custom parameters, custom algorithms create indicators of models, such as: daily startup rate = startup time / 24 hours; when creating custom parameters, it is necessary to determine whether the formula is valid, test whether the result can be calculated, and verify whether the result is consistent with the data type selected by the current custom parameter;

[0077] It should be noted that after the device model is successfully created, if there are custom parameters and status value definitions in the device model, it is necessary to call the data acquisition module interface and save the custom acquisition parameters or status values ​​under the corresponding device production device (because the value of the custom parameter is the result of other parameters calculated through formula calculation, there will be no custom parameters in the collection point table on the original data acquisition module), which is used to store the historical values ​​of the custom parameter in the data acquisition module in sequence later.

[0078] Each parameter group supports custom sorting, and the model supports adding multiple components of the same type. The same component name cannot exist in the same model. The frequency of storing acquisition parameters, custom parameters, and custom status values ​​is 1 minute / one record. When the user clicks to leave the current page or switch to other parameter components, it is necessary to check whether the editing information of the current parameter component has been saved. If not, a pop-up window will be displayed.

[0079] In a further embodiment, before selecting the device model from the model library and constructing the device instance, it also includes receiving a copy instruction, selecting and copying the device model from the model library, and forming a new model by configuring the device model.

[0080] Furthermore, configuring the device model component of the device instance further includes independently editing, adding or deleting parameter definitions of the device model in the device model component of the device instance:

[0081] Independently edit and modify the original parameter definition of the device model in the device instance;

[0082] or, independently adding parameter definitions of the device model in the device instance;

[0083] Or, independently delete the parameter definition of the device model in the device instance.

[0084] Specifically, in this embodiment, when the device model in the database is inconsistent with the parameters required by the device instance, the parameter definition of the device model can be flexibly configured according to the actual needs of the device instance, and the static properties, acquisition parameters, event definitions, status value definitions, alarm code definitions, and configuration custom parameters of the device model can be modified and edited, or parameters can be added / deleted. After the device model in the model library of this application is copied to the device instance, the device model in the device instance and the device model in the model library will be disconnected. The modification operation of the device model in the device instance will only independently modify the parameter definition of the device model in the device instance, and will not affect the device model in the database. The independent modification will only act on the device model of the current device instance, thereby realizing flexible configuration of the device model. Before deleting the parameter definition of the device model in the instance, secondary confirmation is required before deleting the information, and batch deletion is supported.

[0085] Furthermore, the method further includes independently editing, adding or deleting parameter definitions of the device model in the model library:

[0086] Independently edit and modify the original parameter definition of the device model in the model library;

[0087] or, independently adding parameter definitions of the device model in the model library;

[0088] Or, independently delete the parameter definition of the device model in the model library.

[0089] Specifically, in this embodiment, when the device model in the database needs to be modified according to needs, the device model in the model library can be modified independently, the parameter definition of the device model can be flexibly configured, the static properties, acquisition parameters, event definitions, status value definitions, alarm code definitions, and configuration custom parameters of the device model can be modified and edited, or parameters can be added / deleted. After the device model in the model library of this application is copied to the device instance, the device model in the device instance and the device model in the model library will be disconnected. The modification operation of the parameter definition of the device model in the model library will only independently modify the device model in the model library, and will not affect the device model in the device instance that has been constructed. The independent modification will only act on the device model in the model library. When the model is copied later, it will be copied according to the modified device model, thereby realizing flexible configuration of each device model. Before deleting the parameter definition of the device model in the model library, a second confirmation is required before deleting the information, and batch deletion is supported.

[0090] Furthermore, configuring the device collection point corresponding to the device model also includes the step of generating an alarm for missing the device collection point:

[0091] It is determined whether each acquisition parameter in the device model corresponds to the device acquisition point, otherwise a prompt is popped up to indicate that the acquisition parameter lacks a device acquisition point.

[0092] Specifically, in this embodiment, after the device model selects the production equipment in the corresponding data acquisition module, the default collection path of all parameters is the ID. If the production equipment is modified, it will trigger the automatic modification of all parameter paths. At the same time, this embodiment can also modify the collection path of individual collection parameters separately. The collection parameters are configured on the device model. When there is a collection parameter without a corresponding collection path, a prompt will pop up that the collection parameter is missing the equipment collection point. The staff can re-modify the definition of the collection point after receiving the prompt to ensure that the monitored parameter data is not missed.

[0093] Furthermore, the method further comprises a device query step:

[0094] Configure the device name, device type, device status, alarm type and parameter information corresponding to the device model in the device card;

[0095] Get the query keywords;

[0096] The device models related to the keywords are retrieved from the device cards, and the retrieved device models are listed.

[0097] Specifically, in this embodiment, in order to facilitate the query of the device model, a device card is configured for the device model. The device card is configured with the device name, device status, alarm type and parameter information corresponding to the device model, wherein the device status includes running, stopping, online and offline, the alarm type includes serious alarm, important alarm and general alarm, and the parameter information is the parameter information collected by the device model from the production equipment. The device model required by the user can be quickly searched through keyword query, thereby obtaining the relevant information of the device model; the query result, when the device status is offline, displays the last online time, and can click to view the historical data before disconnection. The query result only displays the device whose device type attribute is non-meter, and only displays the device whose monitorable attribute is turned on. When there is an alarm, it supports the display of alarm labels. If there are multiple alarms in a device that have not ended at the same time, the alarm sign with the highest event level is displayed. The query results are sorted by default by device status priority (1 in operation, 2 stopped, 3 waiting for production, 4 offline), then by device type (first letter of the pinyin), and finally by alarm level (1 urgent, 2 serious, 3 important, 4 normal).

[0098] In addition, Figure 3 As shown, the present application proposes a device management apparatus, comprising:

[0099] Model library, used to store device models and parameter definitions of device models;

[0100] The model query module is used to obtain the query keywords input by the user and query the device model from the model library;

[0101] Model creation module, used to create new models;

[0102] A device instance construction module, used for selecting the device model from the model library to construct a device instance;

[0103] A parameter configuration module, used to obtain a configuration instruction input by a user, configure a device model component of the device instance, and define a device collection point corresponding to the device instance in the device model component;

[0104] A parameter acquisition module, used to obtain the real-time parameter values ​​of the equipment collection points;

[0105] A display module, used for displaying the real-time parameter value obtained by the parameter obtaining module through a data chart of the device instance;

[0106] A determination module, used to determine whether the device instance triggers an alarm event;

[0107] The execution module is used to execute the alarm action associated with the alarm event.

[0108] Specifically, the model query module queries the device model. If the corresponding device model is not found in the model library, a new model is created through the model creation module; the device model is copied from the model library through the device instance construction module to build a device instance; the parameter definition of each device model in the device instance is configured through the parameter configuration module, and the device collection point corresponding to each device model is configured; the real-time parameter value of each device collection point is obtained by the parameter acquisition module, and the real-time parameter value is displayed in each device model in the device instance through the display module; the judgment module is used to judge whether each device model triggers an alarm event. If so, the execution module is used to execute the alarm action associated with the current alarm event.

[0109] In this embodiment, the device embodiment described above is only illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art may understand and implement it without paying creative labor.

[0110] In addition, the present application proposes a device management device, comprising a memory storing executable program code; a processor coupled to the memory; and the processor calls the executable program code stored in the memory to execute the device management method.

[0111] In addition, the present application proposes a computer storage medium, wherein the computer storage medium stores computer instructions, and the computer instructions are used to execute the device management method when called.

[0112] For the purposes of this specification, a "computer readable medium" may be any device that can contain, store, communicate, propagate or transmit a program for use with or in conjunction with an instruction execution system, device or apparatus. More specific examples of computer readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (control method), a portable computer disk case (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and editable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, a computer readable medium may even be paper or other suitable medium on which the program may be printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering or, if necessary, processing in another suitable manner, and then stored in a computer memory.

[0113] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0114] In addition, each functional unit in each embodiment of the present invention may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0115] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0116] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0117] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention belong.

[0118] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, apparatus or device (such as a computer-based system, a system including a processing module, or other system that can fetch instructions from an instruction execution system, apparatus or device and execute instructions), or used in combination with these instruction execution systems, apparatuses or devices.

[0119] It should be understood that the various parts of the embodiments of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0120] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A device management method, characterized in that: The following steps are involved: Obtaining the query keyword input by the user, querying the device model from the model library, and creating a new model if the device model is not found in the model library; Select the device model from the model library to build a device instance; Acquire a configuration instruction input by a user, configure a device model component of the device instance, and define a device collection point corresponding to the device instance in the device model component; Acquire the real-time parameter value of the device collection point, and display the real-time parameter value through a data chart of the device instance; Determine whether the device instance triggers an alarm event, and if so, execute the alarm action associated with the alarm event; The step of creating a new model includes the following steps: Obtain a new model creation instruction, and create a new model in the model library; Receive the parameter information input by the user, and create and configure the following basic parameter definitions for the new model: Creating and configuring static attributes to modify fixed attribute information defining the device model; Create and configure acquisition parameters, modify and define the parameter information that can be obtained by the device model; Create and configure event definitions, modify alarm rules that define trigger thresholds for the alarm events, and define the alarm actions; Creating and configuring state value definitions, modifying the states of the device model and the parameter value attributes corresponding to the states; Create and configure alarm code definitions, modify the alarm code, alarm description, alarm type and other information and their mapping relationships of the device model; Create and configure custom parameters; modify model indicators that define user-defined algorithms; Configuring the device model component of the device instance also includes independently editing, adding or deleting parameter definitions of the device model in the device model component of the device instance: Independently edit and modify the original parameter definition of the device model in the device instance; or, independently adding parameter definitions of the device model in the device instance; or, independently deleting the parameter definition of the device model in the device instance; Also included is independent editing, adding or deleting parameter definitions of the device models in the model library: Independently edit and modify the original parameter definition of the device model in the model library; or, independently adding parameter definitions of the device model in the model library; Or, independently delete the parameter definition of the device model in the model library.

2. A device management method according to claim 1, characterized in that: Before selecting the device model from the model library and constructing the device instance, the method further includes receiving a copy instruction, selecting and copying the device model from the model library, and forming a new model by configuring the device model.

3. A device management method according to claim 1, characterized in that: Configuring the device collection point corresponding to the device model also includes the step of generating an alarm for missing the device collection point: It is determined whether each acquisition parameter in the device model has a corresponding device acquisition point. If not, a prompt is popped up indicating that the acquisition parameter lacks a device acquisition point.

4. A device management method according to claim 1, characterized in that: It also includes the device query step: Configure the device name, device type, device status, alarm type and parameter information corresponding to the device model in the device card; Get the query keywords; The device models related to the keywords are retrieved from the device cards, and the retrieved device models are listed.

5. A device management device, characterized in that: The device management method according to any one of claims 1 to 4 is applied, including: Model library, used to store device models and parameter definitions of device models; The model query module is used to obtain the query keywords input by the user and query the device model from the model library; Model creation module, used to create new models; A device instance construction module, used for selecting the device model from the model library to construct a device instance; A parameter configuration module, used to obtain a configuration instruction input by a user, configure a device model component of the device instance, and define a device collection point corresponding to the device instance in the device model component; A parameter acquisition module, used to obtain the real-time parameter values ​​of the equipment collection points; A display module, used for displaying the real-time parameter value obtained by the parameter obtaining module through a data chart of the device instance; A determination module, used to determine whether the device instance triggers an alarm event; The execution module is used to execute the alarm action associated with the alarm event.

6. A device management device, characterized in that: A memory storing executable program code; a processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the device management method according to any one of claims 1 to 4.

7. A computer storage medium, characterized in that: The computer storage medium stores computer instructions, and when the computer instructions are called, they are used to execute the device management method according to any one of claims 1 to 4.

Images