CN116795064B - DCS-based alarm management method, electronic equipment and storage medium - Google Patents
DCS-based alarm management method, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116795064B CN116795064B CN202310919904.3A CN202310919904A CN116795064B CN 116795064 B CN116795064 B CN 116795064B CN 202310919904 A CN202310919904 A CN 202310919904A CN 116795064 B CN116795064 B CN 116795064B
- Authority
- CN
- China
- Prior art keywords
- alarm
- alarm limit
- limit value
- approval
- record
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 59
- 238000003860 storage Methods 0.000 title claims abstract description 13
- 230000008859 change Effects 0.000 claims abstract description 171
- 230000005856 abnormality Effects 0.000 claims abstract description 12
- 238000000034 method Methods 0.000 claims description 54
- 230000008569 process Effects 0.000 claims description 28
- 238000012508 change request Methods 0.000 claims description 19
- 238000012937 correction Methods 0.000 claims description 15
- 230000006399 behavior Effects 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 4
- 230000000694 effects Effects 0.000 abstract description 14
- 230000002159 abnormal effect Effects 0.000 abstract description 9
- 230000004048 modification Effects 0.000 description 8
- 238000012986 modification Methods 0.000 description 8
- 238000012790 confirmation Methods 0.000 description 7
- 230000009471 action Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000006872 improvement Effects 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 230000001276 controlling effect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012550 audit Methods 0.000 description 1
- 238000012824 chemical production Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Alarm Systems (AREA)
Abstract
The application relates to the technical field of automatic control, and provides an alarm management method based on DCS, electronic equipment and a storage medium. The alarm management method based on the DCS comprises the following steps: acquiring an alarm bit number and an actual alarm limit value of an alarm bit of the DCS; under the condition that the actual alarm limit value is determined to be changed, generating an alarm limit value change record corresponding to the alarm bit number; and outputting alarm limit value abnormality prompt information corresponding to the alarm bit number under the condition that the approval passing record corresponding to the alarm limit value change record does not exist. By adopting the technical scheme, the control effect on the alarm flooding can be improved, and the alarm abnormal prompt information corresponding to the alarm bit number is output under the condition that the actual alarm limit value is changed and the corresponding approval record does not exist, so that the on-line supervision on the alarm limit value of each alarm bit can be realized, the operation behavior of the alarm limit value can be standardized, and the control effect on the alarm flooding can be further realized.
Description
Technical Field
The application relates to the technical field of automatic control, in particular to an alarm management method based on DCS, electronic equipment and a storage medium.
Background
DCS (Distributed Control System ) is applied to the industries of chemical industry, electric power, nuclear energy and the like. At present, DCS has an automatic alarm function, but is prone to problems of alarm flooding, which results in a great deal of time consumed in the alarm processing process.
The alarm flooding is usually caused by unreasonable setting of the alarm limit value, so in order to treat the alarm flooding, in the related art, an operator can adjust the alarm limit value of an alarm position according to actual conditions in the actual working process, thereby controlling the alarm quantity of the DCS.
However, the alarm limit value of the alarm bit is maintained offline by an operator, and an administrator cannot effectively monitor the alarm limit value, which leads to the problem that the alarm management of the DCS is not standard and further leads to poor treatment effect on alarm flooding.
Disclosure of Invention
In order to help to improve the treatment effect on alarm flooding, the application provides a DCS-based alarm management method, electronic equipment and a storage medium.
In a first aspect, a DCS-based alarm management method is provided, for use in an alarm management platform, and the following technical scheme is adopted:
An alarm management method based on DCS, for use in an alarm management platform, the method comprising:
Acquiring alarm account information of an alarm bit of a DCS, wherein the alarm account information comprises the alarm bit number and an actual alarm limit value corresponding to the alarm bit number;
determining whether the actual alarm limit value is changed;
Generating an alarm limit value change record corresponding to the alarm bit number under the condition that the actual alarm limit value is determined to be changed;
determining whether an approval passing record corresponding to the alarm limit value change record exists or not;
And outputting alarm limit value abnormality prompt information corresponding to the alarm bit number under the condition that the approval passing record corresponding to the alarm limit value change record does not exist.
By adopting the technical scheme, the control effect on the alarm flooding can be improved. According to the technical scheme, the actual alarm limit value is determined through the alarm account information, under the condition that the actual alarm limit value is determined to be changed, whether the corresponding approval record exists or not is determined, and under the condition that the corresponding approval record does not exist, the alarm abnormal prompt information corresponding to the alarm bit number is output, so that the on-line supervision of the alarm limit value of each alarm bit can be realized, the operation behavior of the alarm limit value can be standardized, and the treatment effect of alarm flooding can be further achieved.
Optionally, the determining whether the actual alarm limit value is changed includes:
Acquiring an expected alarm limit value corresponding to the alarm bit number, wherein the expected alarm limit value is maintained by the alarm management platform;
determining whether the actual alarm limit value matches the expected alarm limit value;
And under the condition that the actual alarm limit value is not matched with the expected alarm limit value, determining that the actual alarm limit value is changed, and executing the step of generating an alarm limit value change record corresponding to the alarm bit.
According to the technical scheme, the expected alarm limit value corresponding to the alarm bit number is recorded in the alarm management platform, so that whether the actual alarm limit value corresponding to the alarm bit number is changed or not can be determined based on the matching relation between the actual alarm limit value corresponding to the alarm bit number and the expected alarm limit value, the change condition of the actual alarm limit value can be accurately determined, and the monitoring and management of the alarm limit values of all alarm bits can be facilitated.
Optionally, after determining whether the approval passing record corresponding to the alarm limit value change record exists, the method further includes:
And under the condition that the approval passing record corresponding to the alarm limit value change record exists, updating the expected alarm limit value based on the actual alarm limit value.
In the above technical solution, under the condition that the approval passing record corresponding to the alarm limit change record exists, the change of the actual alarm limit is legal, and at this time, the actual alarm limit is determined to be the expected alarm limit, so that the update of the expected alarm limit can be realized, whether the actual alarm limit is changed or not can be accurately determined, and meanwhile, the alarm limit of each alarm bit can be conveniently monitored based on the alarm management platform, so that the improvement of the treatment effect on the alarm flooding can be facilitated.
Optionally, when it is determined that the approval passing record corresponding to the alarm limit value change record does not exist, the method further includes:
determining whether an approval ticket corresponding to the alarm limit change record exists;
and under the condition that the approval list corresponding to the alarm limit change record exists, sending first prompt information to an administrator terminal so as to prompt the administrator to approve the approval list.
By adopting the technical scheme, under the condition that the approval list corresponding to the alarm limit value change record exists, the first prompt message is sent to the administrator terminal to prompt the administrator to approve the corresponding approval list, so that the validity of the alarm limit value change can be determined, and the abnormal change of the alarm limit value can be further processed.
Optionally, when it is determined that the approval passing record corresponding to the alarm limit value change record does not exist, the method further includes:
Determining whether an approval reject record corresponding to the alarm limit value change record exists or not;
And sending second prompt information to an administrator terminal under the condition that the approval reject records corresponding to the alarm limit value change records exist, so as to prompt the administrator to process the illegal behaviors of the operator.
By adopting the technical scheme, the second prompt information can be sent to the manager side under the condition that the approval reject records corresponding to the alarm limit change records exist, so that the manager is prompted to process the illegal behaviors of the operator, the illegal behaviors of the operator can be corrected in time, the behavior of the private alarm limit is controlled, and the supervision of the alarm limit can be facilitated.
Optionally, after determining whether the approval rejection record corresponding to the alarm limit value change record exists, the method further includes:
Under the condition that the approval reject records corresponding to the alarm limit change records are not present, determining whether the associated approval passing records of the alarm limit change records exist or not, wherein the alarm bit numbers corresponding to the associated approval passing records are identical to the alarm bit numbers corresponding to the alarm limit change records;
Determining a target alarm limit value in the associated approval passing record under the condition that the associated approval passing record of the alarm limit value change record exists;
And sending correction prompt information containing the target alarm limit value to an administrator terminal and/or an operator terminal so as to prompt correction of the alarm limit value of the alarm bit.
By adopting the technical scheme, whether the associated approval passing record of the alarm limit change record exists or not can be further determined under the condition that the approval passing record corresponding to the alarm limit change record does not exist, and correction prompt information is sent to an administrator and/or an operator under the condition that the associated approval passing record exists so as to prompt correction of the alarm limit of the alarm bit, so that the correct target alarm limit can be timely determined under the condition that the operator has an operation error, and prompt correction is carried out on the alarm limit, thereby realizing effective supervision of the alarm limit, and further being beneficial to improving the treatment effect of alarm inundation.
Optionally, before determining whether the approval passing record corresponding to the alarm limit value change record exists, the method further includes:
Determining whether the alarm limit change record needs approval or not;
And executing the step of determining whether an approval passing record corresponding to the alarm limit change record exists or not under the condition that the alarm limit change record needs approval.
By adopting the technical scheme, whether the alarm limit change record needs to be approved or not can be determined before whether the approval passing record corresponding to the alarm limit change record exists or not is determined, and whether the alarm limit change record exists or not is determined under the condition that the alarm limit change record does not need to be approved or not is determined, so that alarm change which needs to be approved can be regulated, and the regulation efficiency of the alarm limit can be improved.
Optionally, the method further comprises:
Responding to an alarm limit value change request, and generating an approval sheet based on the alarm limit value change request, wherein the approval sheet comprises an alarm bit number of an alarm bit corresponding to the alarm limit value change request and a target alarm limit value corresponding to the alarm bit number;
Transmitting the approval ticket to the administrator terminal based on the approval process corresponding to the approval ticket;
and responding to the approval passing instruction corresponding to the approval sheet returned by the administrator, and generating an approval passing record corresponding to the approval sheet.
By adopting the technical scheme, under the condition that the alarm limit value change request is received, the approval list can be generated based on the alarm limit value change request, the approval list is sent to the manager side based on the approval process corresponding to the approval list, and the approval passing record corresponding to the approval list is generated under the condition that the approval passing instruction returned by the manager side is received, so that the on-line approval of the approval list can be realized through the alarm management platform, the on-line supervision of the alarm limit value can be facilitated, and further the alarm inundation can be managed.
In a second aspect, an electronic device is provided, which adopts the following technical scheme:
An electronic device, the electronic device comprising:
at least one processor;
A memory;
At least one application program, wherein the at least one application program is stored in the memory and configured to be executed by the at least one processor, the at least one application program configured to: any one of the DCS-based alarm management methods provided in the first aspect is performed.
In a third aspect, a computer readable storage medium is provided, and the following technical solutions are adopted:
a computer readable storage medium having stored thereon a computer program which, when executed in a computer, causes the computer to perform any of the DCS-based alarm management methods provided in the first aspect.
In summary, the present application includes at least one of the following beneficial technical effects:
1. The method can help to promote the treatment effect of the alarm flooding, and can realize the on-line supervision of the alarm limit value of each alarm bit because the method determines whether the corresponding approval record exists or not under the condition that the actual alarm limit value is changed and outputs the alarm abnormal prompt information corresponding to the alarm bit number under the condition that the corresponding approval record does not exist, thereby being beneficial to standardizing the operation of the alarm limit value by operators and further being capable of treating the alarm flooding.
2. Under the condition that the approval reject records corresponding to the alarm limit change records exist, second prompt information is sent to the administrator side to prompt the administrator to process the illegal behaviors of the operator, so that the illegal behaviors of the operator can be corrected in time, the behaviors of privacy modification of the alarm limit are controlled, and supervision of the alarm limit can be facilitated.
Drawings
FIG. 1 is a flow chart of a first implementation of a DCS-based alarm management method provided by an embodiment of the present application;
FIG. 2 is a flow chart of a second implementation of a DCS-based alarm management method provided by an embodiment of the present application;
FIG. 3 is a flow chart of a third implementation of a DCS-based alarm management method provided by an embodiment of the present application;
FIG. 4 is a flow chart of a fourth implementation of a DCS-based alarm management method provided by an embodiment of the present application;
FIG. 5 is a flowchart of a fifth implementation of a DCS-based alarm management method provided by an embodiment of the present application;
FIG. 6 is a flowchart of an alarm limit change record generation method according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings 1 to 7 and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
The embodiment of the application provides an alarm management method based on a DCS, which is used in an alarm management platform, wherein the alarm management platform can be integrated in a management system of the DCS or can be independently arranged, and the implementation mode of the alarm management platform is not limited.
In this embodiment, an example in which the alarm management platform operates on an electronic device is described, where the electronic device may be a server or a terminal device, and the terminal device may be an industrial control computer, a personal computer, or the like.
Referring to fig. 1, the DCS-based alarm management method includes the steps of:
Step 101, acquiring alarm account information of an alarm bit of the DCS.
The alarm account information is used for recording the alarm condition of the alarm bit of the DCS. In one example, the alarm ledger information is generated by individual alarm bits of the DCS according to preset rules. In one example, the preset rule is constituted by at least one alarm limit.
In one example, where DCS is applied to chemical production, the alarm bit may be set based on process points in DCS, such as: flow, pressure, potential, current, etc., the present embodiment does not limit the setting mode of the alarm bit.
In actual implementation, the alarm ledger information may be manually recorded by an operator, and the generation mode of the alarm ledger information is not limited in this embodiment.
Optionally, acquiring alarm ledger information of an alarm bit of the DCS includes: and acquiring alarm account information based on an information interaction port with the DCS.
In this embodiment, the alarm ledger information includes an alarm bit number and an actual alarm limit value corresponding to the alarm bit number. Specifically, the alarm bit number is used for uniquely identifying an alarm bit in the DCS, and the actual alarm limit value is the alarm limit value currently used by the alarm bit indicated by the alarm account information. In actual implementation, the alarm bit may correspond to more than two alarm limits, where the alarm ledger information includes at least one alarm limit.
Optionally, the actual alarm limit value may be directly recorded in the alarm ledger information, or may also be obtained by analyzing the alarm ledger information, where the mode of determining the alarm limit value included in the alarm ledger information in this embodiment is defined.
In one example, the alarm management platform can automatically obtain alarm account information corresponding to all or a designated part of alarm bits in the DCS at regular intervals, and comb and analyze the alarm account information respectively, so that the automatic inspection of the alarm bits can be facilitated, the actual condition of the alarm bits can be monitored, and further the problem of alarm flooding can be avoided.
In one example, the alarm management platform acquires alarm account information corresponding to all or appointed part of alarm bits in the DCS one by one, and processes the acquired alarm account information in sequence, so that the calculation resources occupied by the alarm management method can be reduced, the problem of excessive resources occupied when the alarm account information of each alarm bit is uniformly acquired and the alarm account information is uniformly carded and analyzed can be avoided, and the requirement of the alarm management method on the performance of the electronic equipment can be further reduced.
In actual implementation, the alarm ledger information may also include other content, such as: alarm limit change information, alarm limit description information, and/or units of alarm limit, etc., the present embodiment does not limit what the alarm ledger information actually includes.
Step 102, determining whether the actual alarm limit is changed.
Optionally, determining whether the actual alarm limit is changed includes: acquiring an expected alarm limit value corresponding to the alarm bit number; determining whether the actual alarm limit value is matched with the expected alarm limit value; and under the condition that the actual alarm limit value is not matched with the expected alarm limit value, determining that the actual alarm limit value is changed.
And the expected alarm limit value corresponding to the alarm bit number is maintained by the alarm management platform. Specifically, the expected alarm limit value may be a preset alarm limit value, or may be determined based on an actual alarm limit value corresponding to the alarm bit number acquired by history (for example, last time), or may be determined based on other manners, which is not limited in the determining manner of the expected alarm limit value in this embodiment.
According to the technical scheme, the expected alarm limit value corresponding to the alarm bit number is recorded in the alarm management platform, so that whether the actual alarm limit value corresponding to the alarm bit number is changed or not can be determined based on the matching relation between the actual alarm limit value corresponding to the alarm bit number and the expected alarm limit value, the change condition of the actual alarm limit value can be accurately determined, and the monitoring and management of the alarm limit values of all alarm bits can be facilitated.
In one example, the alarm bit corresponds to more than two alarm limits, different alarm limits correspond to different types, and at this time, determining whether the actual alarm limit matches the expected alarm limit includes: determining a target expected alarm limit value which is the same as the actual alarm limit value in the expected alarm limit value; it is determined whether the actual alarm limit matches the target expected alarm limit.
In one example, the alarm limit includes: upper limit, lower limit and lower limit.
In one example, the type of actual alarm limit may be determined based on alarm ledger information. Such as: the content of the alarm ledger information includes "lower limit of data", and the type of the actual alarm limit value at this time includes "lower limit". In actual implementation, the type of the actual alarm limit value may be determined based on other manners, and the embodiment does not limit the manner of determining the type of the actual alarm limit value.
Further, the actual alarm limit value includes two or more, and determining whether the actual alarm limit value matches the expected alarm limit value includes: for each actual alarm limit, it is determined whether the actual alarm limit matches the expected alarm limit, respectively. Therefore, a plurality of alarm limit values of the alarm position can be monitored simultaneously, and further the efficiency of monitoring the alarm limit values can be improved.
In actual implementation, it may also be determined whether the actual alarm limit has changed based on other means, such as: when the content of the alarm ledger information includes alarm limit value change information, the actual alarm limit value can be directly determined to be changed, and the mode of determining whether the actual alarm limit value is changed is not limited in this embodiment.
And 103, under the condition that the actual alarm limit value is determined to be changed, generating an alarm limit value change record corresponding to the alarm bit number.
The alarm limit value change record is used for indicating the actual change condition of the alarm limit value corresponding to the alarm bit number.
In one example, the alarm limit change record includes an alarm bit number and a target alarm limit corresponding to the alarm bit number.
The target alarm limit value is used for indicating the changed alarm limit value.
Optionally, generating the alarm limit change record includes: and determining the actual alarm limit value corresponding to the alarm bit number as the target alarm limit value corresponding to the alarm bit number, and obtaining an alarm limit value change record.
Further, the alarm limit value change record further includes an initial alarm limit value, and at this time, the alarm limit value change record is generated, and further includes: and determining the expected alarm limit value as an initial alarm limit value corresponding to the alarm bit number, and obtaining an alarm limit value change record.
Wherein the initial alarm limit is used for indicating the alarm limit before the change.
In actual implementation, the alarm limit change record may also be generated based on other means, such as: the alarm limit change record is directly generated based on the alarm limit change information in the alarm ledger information, and the embodiment does not limit the way of generating the alarm limit change record.
Step 104, determining whether an approval passing record corresponding to the alarm limit value change record exists.
And the approval is used for indicating the change condition of the alarm limit value compliance corresponding to the alarm bit number. In one example, the approval passing record is generated when an administrator approves the approval of the approval document and the approval passes.
The approval sheet at least comprises an alarm bit number and a target alarm limit value corresponding to the alarm bit number. In actual implementation, the approval sheet may also include other information, such as: the operator number, the initial alarm limit value corresponding to the alarm bit number, etc., and the embodiment does not limit the information actually included in the audit list.
In one example, the approval ticket is generated based on an alarm limit change request sent by the operator. In actual implementation, the approval may also be obtained directly based on other means, such as: the present embodiment does not limit the manner in which the review batch is obtained, as it is sent directly by the operator.
In actual implementation, the approval passing record may also be directly input into the alarm management platform by the administrator, and the embodiment does not limit the acquisition mode of the approval passing record.
Generally, an operator needs to go through approval before changing the alarm limit value of the alarm bit, so whether the alarm limit value changing operation is compliant can be determined based on the corresponding situation of the alarm limit value changing record and the approval passing record.
In one example, the approval passing record includes an alarm bit number and a target alarm limit corresponding to the alarm bit number. The target alarm limit value is used for indicating the changed alarm limit value passing the approval.
Correspondingly, determining whether the approval passing record corresponding to the alarm limit value change record exists or not includes: determining whether each approval passing record has an approval passing record which is the same as the alarm bit number and the target alarm limit value in the alarm limit value change record; if yes, determining that an approval passing record corresponding to the alarm limit value change record exists; if the approval passing record does not exist, determining that the approval passing record corresponding to the alarm limit value change record does not exist.
In other examples, the approval passing record may also include other information, such as: the initial alarm limit value corresponding to the administrator number, the operator number, and/or the alarm bit number, etc., and the present embodiment does not limit what is actually included in the trial pass record.
In actual implementation, whether or not there is an approval passing record corresponding to the alarm limit change record may be determined based on other methods, which is not limited in this embodiment.
And 105, outputting alarm limit abnormity prompt information corresponding to the alarm bit number under the condition that the approval passing record corresponding to the alarm limit change record does not exist.
Optionally, when it is determined that an approval passing record corresponding to the alarm limit change record exists, that is, the alarm limit change compliance is indicated, at this time, an actual alarm limit may be recorded, or other operations may be performed, which is not limited in this embodiment, and the step performed when it is determined that the approval passing record corresponding to the alarm limit change record exists.
In one example, the alarm management platform has an expected alarm limit recorded therein, at which time the expected alarm limit is updated based on the actual alarm limit in the presence of an approval passing record corresponding to the alarm limit change record.
In one example, updating the expected alarm limit based on the actual alarm limit includes: the actual alarm limit is determined as the expected alarm limit.
In the above technical solution, under the condition that the approval passing record corresponding to the alarm limit change record exists, the change of the actual alarm limit is legal, and at this time, the actual alarm limit is determined to be the expected alarm limit, so that the update of the expected alarm limit can be realized, whether the actual alarm limit is changed or not can be accurately determined, and meanwhile, the alarm limit of each alarm bit can be conveniently monitored based on the alarm management platform, so that the improvement of the treatment effect on the alarm flooding can be facilitated.
In one example, outputting alarm limit value abnormality prompt information corresponding to an alarm bit number includes: and sending alarm limit value abnormality prompt information containing an alarm bit number to an administrator side and/or an operator side.
The administrator refers to a device used by an administrator, for example: and a computer, a mobile phone and other devices used by an administrator. In one example, the administrator terminal logs in with an administrator account, so that the alarm management platform can send information to the administrator terminal based on the administrator account.
The operator side refers to equipment used by an operator, such as: and equipment such as a computer, a mobile phone and the like used by operators. In one example, the operator terminal logs in with an operator account, so that the alarm management platform can send information to the operator terminal based on the operator account.
In another example, outputting alarm limit value abnormality prompt information corresponding to the alarm bit number includes: and controlling alarm devices corresponding to the alarm positions corresponding to the alarm position numbers to output abnormal prompt information, wherein the alarm devices corresponding to different alarm positions are identical or different. The alarm device may be disposed in the control room or may be disposed near the alarm position, and the setting position of the alarm device is not limited in this embodiment.
In actual implementation, the alarm abnormality prompting information can be output in other modes, and the output mode of the alarm abnormality prompting information is not limited in this embodiment.
Optionally, the alarm management system generates data during the alarm management process, such as: the data such as the expected alarm limit value, the alarm limit value change record, the alarm limit value abnormal prompt information and the like support inquiry and export. Furthermore, the alarm management system provides an information display interface, so that data generated in an alarm process can be displayed through the information display interface, and the alarm limit value of each alarm position in the DCS can be further conveniently monitored.
The implementation principle of the alarm management method based on the DCS provided by the embodiment is as follows: acquiring alarm account information of an alarm position of the DCS, wherein the alarm account information comprises an alarm position number and an actual alarm limit value corresponding to the alarm position number; determining whether the actual alarm limit value is changed; under the condition that the actual alarm limit value is determined to be changed, generating an alarm limit value change record corresponding to the alarm bit number; determining whether an approval passing record corresponding to the alarm limit value change record exists or not; and outputting alarm limit value abnormality prompt information corresponding to the alarm bit number under the condition that the approval passing record corresponding to the alarm limit value change record does not exist. By adopting the technical scheme, the improvement of the treatment effect on the alarm flood can be facilitated, the actual alarm limit value is determined through the alarm account information in the technical scheme, whether the corresponding approval record exists or not is determined under the condition that the actual alarm limit value is changed, and the alarm abnormal prompt information corresponding to the alarm bit number is output under the condition that the corresponding approval record does not exist is determined, so that the on-line supervision of the alarm limit value of each alarm bit can be realized, the operation behavior of the alarm limit value can be standardized, and the treatment effect on the alarm flood can be further realized.
In some embodiments, optionally, referring to fig. 2, in step 105, in a case where it is determined that there is no approval passing record corresponding to the alarm limit change record, the method further includes the following steps:
Step 201, determining whether an approval ticket corresponding to the alarm limit change record exists.
The approval ticket is used for indicating an alarm limit value change request to be approved. Typically, the approval ticket is generated based on the alarm limit change request sent by the operator for approval by the administrator.
In one example, the approval ticket includes at least an alarm bit number and a target alarm limit corresponding to the alarm bit number. The target alarm limit value is used for indicating the changed alarm limit value.
Correspondingly, determining whether the approval ticket corresponding to the alarm limit change record exists or not includes: determining whether each approval ticket has the approval ticket which is the same as the alarm position number and the target alarm limit value in the alarm limit value change record; if so, determining that the approval ticket corresponding to the alarm limit change record exists, and if not, determining that the approval ticket corresponding to the alarm limit change record does not exist.
In actual implementation, the approval sheet may also include other information, such as: the operator number, the initial alarm limit value corresponding to the alarm bit number, etc., at this time, whether the approval ticket corresponding to the alarm limit value change record exists or not may also be determined in other manners, and the embodiment does not limit the information actually included in the approval ticket.
Step 202, sending first prompt information to an administrator terminal to prompt the administrator to approve the approval ticket corresponding to the alarm limit change record under the condition that the approval ticket corresponding to the alarm limit change record exists.
Under the condition that the approval list corresponding to the alarm limit change record exists, namely that an operator submits the alarm limit change to approval but modifies the alarm limit under the condition that the administrator does not do the approval, at the moment, a first prompt message is sent to the administrator to prompt the administrator to approve the corresponding approval list, so that the validity of the alarm value change can be determined, the modification and the approval are synchronous, and meanwhile, the abnormal change of the alarm limit can be further processed.
Optionally, the first prompt information may include a number of the approval ticket corresponding to the alarm limit change record, or may also include an approval link of the approval ticket corresponding to the alarm limit change record, which in this embodiment does not limit the content of the first prompt information.
In actual implementation, the first prompt information and the alarm limit value abnormality prompt information can be combined and sent to an administrator side, and at the moment, the administrator can be helped to process the abnormality.
In the above embodiment, when the approval passing record corresponding to the alarm limit change record does not exist, whether the approval ticket corresponding to the alarm limit change record exists is further determined, and when the approval ticket corresponding to the alarm limit change record exists, the first prompting information is sent to the administrator terminal to prompt the administrator to approve the corresponding approval ticket, so that the validity of the alarm limit change can be determined, and the further processing of the abnormal change of the alarm limit can be facilitated.
In some embodiments, optionally, referring to fig. 3, in step 105, in a case where it is determined that there is no approval passing record corresponding to the alarm limit change record, the method further includes the following steps:
Step 301, determining whether an approval reject record corresponding to the alarm limit change record exists.
And the approval rejection record is used for indicating the non-compliance change condition of the alarm limit value corresponding to the alarm bit number. Specifically, the approval rejection record is generated when an administrator approves the approval batch and approves the approval rejection.
In one example, the approval rejection record includes an alarm bit number and a target alarm limit corresponding to the alarm bit number. The target alarm limit value is used for indicating the alarm limit value after the change of the approval rejection.
Optionally, the manner of determining whether the approval reject record corresponding to the alarm limit change record exists is the same as the manner of determining whether the approval pass record corresponding to the alarm limit exists in step 104, and this implementation is not described herein.
Step 302, sending second prompt information to the administrator terminal to prompt the administrator to process the illegal actions of the operator when the condition that the approval reject record corresponding to the alarm limit value change record exists is determined.
Under the condition that the approval reject records corresponding to the alarm limit change records exist, namely, the fact that an operator still modifies the alarm limit under the condition that the alarm limit change approval is rejected is indicated, at the moment, second prompt information is sent to an administrator terminal to prompt the administrator terminal to process the illegal behaviors of the operator, so that the illegal behaviors of the operator can be corrected in time, the behaviors of privacy modification of the alarm limit are controlled, and supervision of the alarm limit can be facilitated.
Optionally, the second prompt information may include a number of the approval rejection record, or may also include specific content of the approval rejection record, which is not limited in this embodiment.
In an example, when it is determined that the approval record corresponding to the alarm limit value change record exists, the second prompting information may be synchronously sent to other operators corresponding to the operation position, so as to prompt the other operators to correct the alarm limit value in time.
The other operators may include operators other than the operator submitting the approval report corresponding to the approval ticket, or may include operators other than the operator actually executing the alarm limit value change operation, and the determination method of the other operators is not limited in this embodiment.
In the technical scheme, the second prompt information can be sent to other operators, so that the prompt of the other operators to correct the alarm limit value in time can be facilitated, and the management of the alarm limit value can be facilitated.
In the above embodiment, under the condition that the approval passing record corresponding to the alarm limit value change record does not exist, whether the approval reject record corresponding to the alarm limit value change record exists is further determined, and under the condition that the approval reject record corresponding to the alarm limit value change record exists, second prompt information is sent to the administrator terminal to prompt the administrator terminal to process the illegal action of the operator, so that the method can help to correct the illegal action of the operator in time, control the action of privacy modification of the alarm limit value, and further help to monitor the alarm limit value.
Based on the above technical solution, referring to fig. 4, further, step 301, after determining whether there is an approval reject record corresponding to the alarm limit change record, further includes:
Step 401, determining whether the associated approval passing record of the alarm limit change record exists or not when determining that the approval reject record corresponding to the alarm limit change record does not exist.
And the alarm bit number corresponding to the associated approval passing record is the same as the alarm bit number corresponding to the alarm limit value change record.
In one example, the approval passing records include an executed approval passing record and an unexecuted approval passing record, where the associated approval passing record is the unexecuted approval passing record.
Correspondingly, the approval passing record corresponding to the alarm limit value change record determined in the step 104 is determined as the executed approval passing record.
Further, the initial alarm limit value corresponding to the associated approval record is the same as the initial alarm limit value corresponding to the alarm limit value change record. Wherein the initial alarm limit is used for indicating the alarm limit before the change. Thus, the accuracy of the determined associated approval records can be further improved.
In step 402, in the case where there is an associated approval passing record of the alarm limit change record, a target alarm limit in the approval passing record is determined.
The target alarm limit value is used for indicating the changed alarm limit value passing the approval.
Under the condition that the associated approval records exist, the fact that the operator possibly has misoperation is indicated, and the alarm limit value is changed incorrectly is caused, so that the correct alarm limit value needs to be determined in time and the operator is guided to correct in time.
Step 403, sending correction prompt information including the target alarm limit value in the associated approval passing record to the administrator end and/or the operator end, so as to prompt correction of the alarm limit value of the alarm bit.
In one example, the correction hint information may also include other information such as: other contents of the management approval passing record are not limited to the specific contents of the correction prompt information in this embodiment.
The manner of sending the correction prompt message to the administrator terminal and/or the operator terminal is the same as the manner of outputting the alarm limit value abnormality prompt message corresponding to the alarm bit number in step 105, and this embodiment is not described herein again.
In the above embodiment, under the condition that the approval reject record corresponding to the alarm limit change record does not exist, whether the associated approval pass record of the alarm limit change record exists is further determined, and under the condition that the associated approval pass record exists, correction prompt information is sent to an administrator and/or an operator to prompt correction of the alarm limit of the alarm bit, so that the correct target alarm limit can be timely determined under the condition that an operator has an operation error, and prompt based on correction of the alarm limit is provided, thereby realizing effective supervision of the alarm limit, and further being beneficial to improving the treatment effect of alarm flooding.
In some embodiments, optionally, referring to fig. 5, before determining whether there is an approval passing record corresponding to the alarm limit change record in step 104, the method further includes the steps of:
Step 501, determining whether the alarm limit change record needs approval.
In one example, the alarm limit change record includes an alarm bit number, and determining whether the alarm limit change record requires approval includes: and determining whether the alarm limit change record needs approval or not based on the alarm bit number.
The alarm position number to be checked and/or the alarm position number not to be checked are preset.
In another example, the alarm limit change record includes a type of alarm limit, and determining whether the alarm limit change record requires approval includes: and determining whether the alarm limit change record needs approval or not based on the type of the alarm limit.
The type of the alarm limit value to be checked and/or the type of the alarm limit value not to be checked are preset.
In other examples, it may also be determined whether the alarm limit change log requires approval based on both of the above. Such as: under the condition that the alarm bit number and the alarm limit value are obtained without approval, determining that the alarm limit value change record is not approved, otherwise, determining that the alarm limit value change record is approved; and, for example: and setting the type of alarm limit value to be approved in the alarm bit number independently according to different alarm bit numbers.
In actual implementation, it may also be determined whether the alarm limit change record needs approval based on other manners, such as: determining whether the alarm limit change record needs approval or not based on the relation between the change amplitude of the alarm limit and the preset maximum change amplitude, for example: whether the alarm limit change record needs to be approved or not is determined based on whether the target alarm limit exceeds a preset no-approval range, and the mode of determining whether the alarm limit change record needs to be approved or not is not limited in the embodiment.
Step 502, executing the step of determining whether an approval passing record corresponding to the alarm limit change record exists or not, namely executing step 104, under the condition that the alarm limit change record needs approval.
Optionally, when it is determined that the alarm limit change record does not need to be approved, that is, the alarm limit change compliance is indicated, at this time, an actual alarm value may be recorded, or a determining operation may also be performed.
In the above embodiment, before determining whether the approval passing record corresponding to the alarm limit change record exists, whether the alarm limit change record needs to be approved is determined, and whether the alarm limit change record exists is determined under the condition that the alarm limit change record does not need to be approved, so that the alarm change which needs to be approved can be supervised, and the supervision efficiency of the alarm limit can be improved.
In some embodiments, optionally, referring to fig. 6, the DCS-based alarm management method provided in this embodiment further includes the steps of:
in step 601, in response to the alarm limit change request, an approval ticket is generated based on the alarm limit change request.
The approval ticket comprises an alarm bit number of an alarm bit corresponding to the alarm limit value change request and a target alarm limit value corresponding to the alarm bit number.
Alternatively, the alarm limit change request may be sent by the operator, or may be acquired in another manner, and the embodiment is not limited to the manner in which the alarm limit change request is acquired.
In other examples, the approval ticket may also include other information, such as: the expected alarm limit value corresponding to the alarm bit number, etc., and the embodiment does not limit the content actually included in the examination batch.
In actual implementation, the approval ticket can also be sent to the alarm management platform directly by an employee side or other equipment, so that the calculation amount of the alarm management platform can be reduced.
Step 602, sending the approval ticket to the administrator terminal based on the approval process corresponding to the approval ticket.
Optionally, the approval process corresponding to the approval sheet may be determined based on the alarm number and/or the target alarm limit value in the approval sheet, and the embodiment does not limit the determination manner of the approval process corresponding to the approval sheet.
In one example, the alarm bits are classified, and approval processes corresponding to the alarm bits of different classes are the same or different, and at this time, the approval processes may be determined based on the alarm bit numbers.
In another example, the approval process is determined based on the range of limits to which the target alarm limit belongs. The limit value ranges are obtained by dividing the alarm limit value range in advance according to the area range of the alarm limit value, the approval processes corresponding to the limit value ranges are preset, and the approval processes corresponding to different limit value ranges are identical or different.
Step 603, generating an approval passing record corresponding to the approval ticket in response to an approval passing instruction corresponding to the approval ticket returned by the administrator.
In one example, the approval passing instruction includes approval modification content, such as: the alarm bit number and the target alarm limit value corresponding to the alarm bit number generate an approval passing record based on the approval passing instruction. Because the administrator may modify and/or supplement the content in the approval document during the approval process, generating the approval passing record based on the approval passing instruction may help to improve the accuracy of the content in the approval passing record.
Furthermore, the contents which are not contained in the approval passing instruction can be supplemented based on the approval ticket or the information recorded in the alarm management platform, so that the enrichment of the contents of the approval passing record can be facilitated.
In another example, no modification of the content in the approval process is allowed, at which point an approval pass record may be generated directly based on the approval.
In actual implementation, the approval passing record may be generated in other manners, and the embodiment does not limit the manner of generating the approval passing record.
Optionally, the response to the approval passing instruction corresponding to the approval ticket returned by the administrator side further includes: and generating change confirmation information, and sending the change confirmation information to an operator terminal to prompt the operator to modify the alarm limit value of the alarm bit into a target alarm limit value.
Optionally, the generating manner of the change confirmation information is the same as the generating manner of the approval passing record, and this embodiment is not described herein.
In one example, the manner of sending the change confirmation information to the operator terminal may include sending the change confirmation information to the operator terminal sending the alarm limit value change request, or may also include sending the change confirmation information to the operator terminal of the operator corresponding to the alarm bit like the alarm bit number, and the embodiment is not limited to the manner of sending the change confirmation information to the operator terminal.
In the above embodiment, when the alarm limit change request is received, the approval ticket is generated based on the alarm limit change request, the approval ticket is sent to the administrator terminal based on the approval process corresponding to the approval ticket, and the approval passing record corresponding to the approval ticket is generated when the approval passing instruction returned by the administrator terminal is received, so that the on-line approval of the approval ticket can be realized through the alarm management platform, the on-line supervision of the alarm limit can be facilitated, and further the treatment of the alarm flood can be facilitated.
The embodiment of the application also provides electronic equipment. As shown in fig. 7, the electronic device 700 shown in fig. 7 includes: a processor 701 and a memory 703. The processor 701 is coupled to a memory 703, such as via a bus 702. Optionally, the electronic device 700 may also include a transceiver 704. It should be noted that, in practical applications, the transceiver 704 is not limited to one, and the structure of the electronic device 700 is not limited to the embodiment of the present application.
The Processor 701 may be a CPU (Central Processing Unit ), general purpose Processor, DSP (DIGITAL SIGNAL Processor, data signal Processor), ASIC (Application SpecificIntegrated Circuit ) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules and circuits described in connection with this disclosure. The processor 701 may also be a combination that performs computing functions, such as including one or more microprocessors, a combination of a DSP and a microprocessor, or the like.
Bus 702 may include a path to transfer information between the components. Bus 702 may be a PCI (PERIPHERAL COMPONENT INTERCONNECT, peripheral component interconnect standard) bus, or an EISA (ExtendedIndustry Standard Architecture ) bus, or the like. Bus 702 may be divided into an address bus, a data bus, and the like. For ease of illustration, only one thick line is shown in fig. 7, but not only one bus or one type of bus.
The Memory 703 may be, but is not limited to, ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, RAM (Random Access Memory ) or other type of dynamic storage device that can store information and instructions, EEPROM (ELECTRICALLY ERASABLEPROGRAMMABLE READ ONLY MEMORY ), magnetic disk storage or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
The memory 703 is used for storing application program codes for executing the present application and is controlled by the processor 701 for execution. The processor 701 is configured to execute application code stored in the memory 703 to implement what is shown in the foregoing method embodiments.
Among them, electronic devices include, but are not limited to: mobile terminals such as mobile phones, notebook computers, PDAs (personal digital assistants), PADs (tablet computers), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. And may also be a server, etc. The electronic device shown in fig. 7 is only an example and should not be construed as limiting the functionality and scope of use of the embodiments of the application.
The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, which when executed in a computer, causes the computer to execute the DCS-based alarm management method provided by the above embodiment.
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein.
The foregoing is only a partial embodiment of the present application, and it should be noted that it will be apparent to those skilled in the art that modifications and adaptations can be made without departing from the principles of the present application, and such modifications and adaptations should and are intended to be comprehended within the scope of the present application.
Claims (9)
1. A DCS-based alarm management method for use in an alarm management platform, the method comprising:
Acquiring alarm account information of an alarm bit of a DCS, wherein the alarm account information comprises the alarm bit number and an actual alarm limit value corresponding to the alarm bit number;
determining whether the actual alarm limit value is changed;
Generating an alarm limit value change record corresponding to the alarm bit number under the condition that the actual alarm limit value is determined to be changed;
determining whether an approval passing record corresponding to the alarm limit value change record exists or not;
Outputting alarm limit value abnormality prompt information corresponding to the alarm bit number under the condition that the approval passing record corresponding to the alarm limit value change record does not exist;
The method further comprises the following steps when the condition that the approval passing record corresponding to the alarm limit change record does not exist is determined:
Determining whether an approval reject record corresponding to the alarm limit value change record exists or not;
Under the condition that the approval reject records corresponding to the alarm limit change records are not present, determining whether the associated approval passing records of the alarm limit change records exist or not, wherein the alarm bit numbers corresponding to the associated approval passing records are identical to the alarm bit numbers corresponding to the alarm limit change records;
Determining a target alarm limit value in the associated approval passing record under the condition that the associated approval passing record of the alarm limit value change record exists;
And sending correction prompt information containing the target alarm limit value to an administrator terminal and/or an operator terminal so as to prompt correction of the alarm limit value of the alarm bit.
2. The method of claim 1, wherein the determining whether the actual alarm limit has changed comprises:
Acquiring an expected alarm limit value corresponding to the alarm bit number, wherein the expected alarm limit value is maintained by the alarm management platform;
determining whether the actual alarm limit value matches the expected alarm limit value;
And under the condition that the actual alarm limit value is not matched with the expected alarm limit value, determining that the actual alarm limit value is changed, and executing the step of generating an alarm limit value change record corresponding to the alarm bit.
3. The method of claim 2, wherein after determining whether there is an approval passing record corresponding to the alarm limit change record, further comprising:
And under the condition that the approval passing record corresponding to the alarm limit value change record exists, updating the expected alarm limit value based on the actual alarm limit value.
4. The method according to claim 1, wherein in the case where it is determined that there is no approval passing record corresponding to the alarm limit change record, further comprising:
determining whether an approval ticket corresponding to the alarm limit change record exists;
and under the condition that the approval list corresponding to the alarm limit change record exists, sending first prompt information to an administrator terminal so as to prompt the administrator to approve the approval list.
5. The method of claim 1, wherein the determining whether the approval reject record corresponding to the alarm limit change record exists further comprises:
And sending second prompt information to an administrator terminal under the condition that the approval reject records corresponding to the alarm limit value change records exist, so as to prompt the administrator to process the illegal behaviors of the operator.
6. The method of claim 1, wherein the determining whether there is an approval passing record corresponding to the alarm limit change record further comprises:
Determining whether the alarm limit change record needs approval or not;
And executing the step of determining whether an approval passing record corresponding to the alarm limit change record exists or not under the condition that the alarm limit change record needs approval.
7. The method according to claim 1, wherein the method further comprises:
Responding to an alarm limit value change request, and generating an approval sheet based on the alarm limit value change request, wherein the approval sheet comprises an alarm bit number of an alarm bit corresponding to the alarm limit value change request and a target alarm limit value corresponding to the alarm bit number;
Transmitting the approval ticket to the administrator terminal based on the approval process corresponding to the approval ticket;
and responding to the approval passing instruction corresponding to the approval sheet returned by the administrator, and generating an approval passing record corresponding to the approval sheet.
8. An electronic device, the electronic device comprising:
at least one processor;
A memory;
At least one application program, wherein the at least one application program is stored in the memory and configured to be executed by the at least one processor, the at least one application program configured to: performing the DCS-based alarm management method of any of claims 1 to 7.
9. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when executed in a computer, causes the computer to perform the DCS-based alarm management method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310919904.3A CN116795064B (en) | 2023-07-25 | 2023-07-25 | DCS-based alarm management method, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310919904.3A CN116795064B (en) | 2023-07-25 | 2023-07-25 | DCS-based alarm management method, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116795064A CN116795064A (en) | 2023-09-22 |
| CN116795064B true CN116795064B (en) | 2024-07-19 |
Family
ID=88040383
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310919904.3A Active CN116795064B (en) | 2023-07-25 | 2023-07-25 | DCS-based alarm management method, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116795064B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109686066A (en) * | 2018-12-27 | 2019-04-26 | 石化盈科信息技术有限责任公司 | Alarm management system and method |
| CN111915268A (en) * | 2020-07-21 | 2020-11-10 | 北京厚德邦安科技有限责任公司 | Standardized management method based on chemical industry DCS alarm change |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104914822B (en) * | 2015-04-20 | 2018-03-27 | 中国石油化工股份有限公司青岛安全工程研究院 | Method for pimelinketone device alarming and managing |
| CN109658042B (en) * | 2018-10-08 | 2023-08-25 | 平安科技（深圳）有限公司 | Review method, device, equipment and storage medium based on artificial intelligence |
| WO2020132799A1 (en) * | 2018-12-24 | 2020-07-02 | 深圳迈瑞生物医疗电子股份有限公司 | Method and apparatus for setting alarm limit value for monitoring device |
| CN110752942B (en) * | 2019-09-06 | 2021-09-17 | 平安科技（深圳）有限公司 | Alarm information decision method and device, computer equipment and storage medium |
| CN114201090B (en) * | 2021-12-22 | 2023-08-04 | 苏州浪潮智能科技有限公司 | Product production abnormality early warning system, method, computer device and storage medium |
-
2023
- 2023-07-25 CN CN202310919904.3A patent/CN116795064B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109686066A (en) * | 2018-12-27 | 2019-04-26 | 石化盈科信息技术有限责任公司 | Alarm management system and method |
| CN111915268A (en) * | 2020-07-21 | 2020-11-10 | 北京厚德邦安科技有限责任公司 | Standardized management method based on chemical industry DCS alarm change |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116795064A (en) | 2023-09-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112052111B (en) | Processing method, device and equipment for server abnormity early warning and storage medium | |
| CN110987493A (en) | Equipment abnormality detection method and device, storage medium and electronic equipment | |
| CN115841255B (en) | On-site early warning method and system for building engineering based on-line analysis | |
| CN112115026A (en) | Server cluster monitoring method and device, electronic equipment and readable storage medium | |
| CN112817935A (en) | Data processing method, device and equipment based on field type and storage medium | |
| CN116340934A (en) | Terminal abnormal behavior detection method, device, equipment and storage medium | |
| CN112631924A (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN115858311A (en) | Operation and maintenance monitoring method and device, electronic equipment and readable storage medium | |
| CN116795064B (en) | DCS-based alarm management method, electronic equipment and storage medium | |
| CN117290803A (en) | Energy storage inverter remote fault diagnosis method, system and medium | |
| CN114024867B (en) | Network anomaly detection method and device | |
| CN116302669A (en) | Substation protection fixed value monitoring method, system, device and medium | |
| CN114722025A (en) | Data prediction method, device and equipment based on prediction model and storage medium | |
| CN110348984B (en) | Automatic credit card data input method and related equipment under different transaction channels | |
| CN109829681B (en) | Software development monitoring method, device, computer equipment and storage medium | |
| CN112261072A (en) | Service calling method, device, equipment and storage medium | |
| CN114281812A (en) | Data storage method, device, equipment and medium | |
| CN115903677A (en) | Industrial system interaction method and device and industrial system | |
| CN116340097A (en) | Method, device, equipment and storage medium for processing abnormal information | |
| CN115495358A (en) | Log automatic test method, device, system and medium | |
| CN114185864A (en) | Operation log management method and device, electronic equipment and storage medium | |
| CN116610559A (en) | Test method, test device, electronic equipment and computer readable storage medium | |
| CN116880398A (en) | Fault analysis method and system of instrument control equipment, electronic equipment and storage medium | |
| CN117081939A (en) | Traffic data processing method, device, equipment and storage medium | |
| CN116975200A (en) | Method, device, equipment and medium for controlling working state of server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |