CN112763936B - Intelligent fault processing method and system - Google Patents
Intelligent fault processing method and system Download PDFInfo
- Publication number
- CN112763936B CN112763936B CN202011201781.2A CN202011201781A CN112763936B CN 112763936 B CN112763936 B CN 112763936B CN 202011201781 A CN202011201781 A CN 202011201781A CN 112763936 B CN112763936 B CN 112763936B
- Authority
- CN
- China
- Prior art keywords
- alarm
- fault
- condition
- conversion
- pushing
- 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
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/50—Testing of electric apparatus, lines, cables or components for short-circuits, continuity, leakage current or incorrect line connections
- G01R31/52—Testing for short-circuits, leakage current or ground faults
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R1/00—Details of instruments or arrangements of the types included in groups G01R5/00 - G01R13/00 and G01R31/00
- G01R1/02—General constructional details
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Alarm Systems (AREA)
Abstract
The invention discloses a fault intelligent processing method and a system, wherein the method comprises the following steps: when the alarm occurs, recording the alarm; setting an alarm-to-fault condition, wherein the alarm-to-fault condition comprises a fault conversion condition and a fault duplicate removal condition, and the fault duplicate removal condition corresponds to the fault conversion condition; converting the first alarm into a first fault when the alarm includes only the first alarm satisfying the fault conversion condition; and setting an automatic pushing condition, and automatically pushing the first fault when the first fault meets the automatic pushing condition. The invention can realize the automation and the process of the early warning and the processing of the faults in the urban road lighting management.
Description
Technical Field
The invention relates to the technical field of urban intelligent lighting management, in particular to a fault intelligent processing method and system.
Background
The urban road lighting system is directly related to night travel safety and life convenience of urban residents, and along with rapid increase of urban population scale, the density and the number of lighting devices in the urban road lighting system are continuously developed. The traditional management mode of reporting the fault by only depending on equipment, manually analyzing the fault reason and processing cannot maintain the normal and continuous operation of the system.
Disclosure of Invention
The invention aims to provide a fault intelligent processing method and system, and aims to realize the automation and the process of early warning and processing of faults in urban road lighting management aiming at the defects in the prior art.
Therefore, the invention adopts the following technical scheme:
an intelligent fault processing method comprises the following steps: when an alarm occurs, recording the alarm; setting an alarm-to-fault condition, wherein the alarm-to-fault condition comprises a fault conversion condition and a fault duplicate removal condition, and the fault duplicate removal condition corresponds to the fault conversion condition; converting the first alarm to a first fault when the alarm includes only a first alarm that satisfies the fault conversion condition; when the alarm further comprises a second alarm meeting the fault conversion condition, the second alarm occurs no earlier than the first alarm, and the fault names of the first alarm and the second alarm are the same, converting the first alarm into the first fault, and excluding the second alarm; or when the alarm further comprises a third alarm meeting the fault conversion condition, the third alarm occurs no earlier than the first alarm, and the third alarm meets the fault rearrangement condition, converting the first alarm into the first fault, and excluding the third alarm; and setting an automatic pushing condition, and automatically pushing the first fault when the first fault meets the automatic pushing condition.
Preferably, the alarm types include system alarms and device alarms.
Preferably, the equipment alarms of the same type are classified and converted into the same fault name.
Preferably, a device alarm log table is provided for categorizing the device alarms.
Preferably, the first fault is updated according to the alarm value of the second alarm.
Preferably, the fault conversion condition includes an application device grouping and a conversion alarm value.
Preferably, the fault and duplicate removal condition comprises a duplicate removal fault, a duplicate removal source, a duplicate removal state, a duplicate removal time and a duplicate removal alarm value.
Preferably, the next automatic pushing is carried out in a delayed manner.
Preferably, the automatic pushing comprises immediate pushing or custom time pushing.
Based on the same inventive concept, the invention also provides a fault intelligent processing system, which comprises: the recording module is used for recording the generated alarm; the fault verification module is used for verifying whether the alarm meets a fault conversion condition; the fault repetition eliminating module is used for eliminating the second alarm when the alarms comprise a first alarm and a second alarm which pass the verification of the fault judging module respectively, the occurrence time of the second alarm is not earlier than that of the first alarm, and the fault names converted by the first alarm and the second alarm are the same; or when the alarm comprises a first alarm and a third alarm, the first alarm and the third alarm are respectively verified by the fault judgment module, the third alarm occurs no earlier than the first alarm, and the third alarm meets a fault resetting condition, the fault resetting module resets the third alarm; the fault duplicate removal condition corresponds to the fault conversion condition; the fault conversion module is used for converting the first alarm into a first fault when the alarm only comprises the first alarm and the first alarm passes the verification of the fault judgment module; and the automatic pushing module is used for automatically pushing the first fault meeting the automatic pushing condition.
The technical scheme has the advantages that:
1. through various parameter judgment and duplicate removal judgment, the fault repetition rate and the inefficiency are reduced, the management level is improved, and the manual analysis workload is reduced;
2. the fault names of the same type of alarm conversion of equipment of each manufacturer are unified, and the learning cost of a user is reduced;
3. through automatic pushing judgment, the accuracy of fault pushing and the timeliness of processing are enhanced, the integrity of a fault processing flow is ensured, and the waste of resources is reduced.
Drawings
FIG. 1 is a flow chart of a fault intelligence processing method;
FIG. 2 is a settings page for an alarm-to-fault condition for a fault intelligence processing system;
FIG. 3 is an overall logic flow diagram of an alarm-to-fault;
FIG. 4 is a setup page for automatic push conditions for the fault intelligence processing system;
fig. 5 is an overall logic flow diagram of automatic push.
Detailed Description
In order that the objects, features and advantages of the invention will be more clearly understood, a more particular description of the invention will be rendered by reference to the appended drawings, which are illustrated in detail in order to provide a thorough understanding of the invention, but which may be carried out in other ways than those described. Accordingly, the invention is not limited by the specific implementations disclosed below.
Example one
As shown in fig. 1, the present embodiment provides an intelligent fault handling method, which is applied to an urban road lighting system, and includes the following steps:
s1, when an alarm occurs, recording the alarm.
And the fault intelligent processing system records the generated alarm. The alarm types include system alarms, i.e., alarms judged by the system, and device alarms, i.e., alarms actively reported by the device. The system records the system alarm and the equipment alarm respectively to form alarm records. The alarm records comprise attributes such as alarm names, alarm phases, application equipment groups and alarm values, and are used for judging subsequent fault conversion conditions and fault repetition elimination conditions and facilitating tracing of alarms of the system by system managers in the future.
Since the equipment of the system is from different manufacturers, and the protocols and standards of each manufacturer are different, for the same type of alarm, the equipment of different manufacturers has different alarm judgment logics and reported alarm names, so that the alarm records in the traditional system are rough and complicated, the manual analysis by a user is required, and the learning cost of the user is increased.
In this embodiment, the system can be compatible with the alarm names of the devices of each manufacturer, and the alarms of the same type are classified and subsequently converted into the same fault name.
The classification function will be described with reference to an electrical leakage fault as an example. The electric leakage early warning is that the equipment actively reports the electric leakage early warning, namely the equipment alarm.
The positive force equipment reports through analog quantity records, fifty equipment reports through leakage alarm and protection tripping, and the intelligent communication equipment reports through leakage alarm. The system firstly records the received equipment alarms, then classifies the equipment alarms, judges the types of the alarms, and converts the alarms into fault names corresponding to the types, namely leakage faults.
The system is provided with an equipment alarm record table, the table records alarm names correspondingly reported by equipment of different manufacturers, and the system carries out screening through the table.
Correspondingly, the user can also adopt different classification modes, so that the classification function of the system can also meet the personalized requirements of the user.
And S2, setting an alarm-to-fault condition, wherein the alarm-to-fault condition comprises a fault conversion condition and a fault duplicate removal condition, and the fault duplicate removal condition corresponds to the fault conversion condition.
The fault includes attributes such as a fault name.
Firstly, fault conversion setting is carried out on a system, and comprises a fault name (corresponding to the function of converting alarms of the same type of each manufacturer into the same fault name), fault description (describing the fault), conversion types (pull-down options comprising system alarms and equipment alarms and being associated with options for converting the alarms), conversion alarms (pull-down options comprising alarm names contained in the selected conversion types and supporting multiple options, namely selecting the alarm names converted into the fault names, namely selecting the alarm names corresponding to the fault names and classified into the same type), conversion phases (pull-down options comprising all phases and A/B/C phases, selecting all options and respectively converting the faults according to 3 phases, selecting the A/B/C phase options and converting the faults according to the selected phases), and equipment grouping (pull-down options, acquiring the equipment grouping established in the system as options, the alarm value of the fault is only updated when the alarm selected in the conversion alarm reported by the equipment is converted and the alarm value of the fault is not cancelled (a switch option is used, when the alarm is converted into the fault and the alarm is not cancelled), the alarm value of the fault is only updated, a new fault record is not generated, and the alarm value of the fault is the alarm value of the corresponding alarm). The failover setup page of the system is shown in detail in the upper half of fig. 2.
As noted above, the fault conversion condition includes application device grouping and conversion alarm value. And filling or selecting the fault name, the fault description, the conversion type, the conversion alarm and the conversion phase according to the alarm record, and selecting the alarm value according to the system requirement when updating.
Then, fault resetting is carried out in the system, the fault resetting corresponds to the fault conversion setting, and includes a reset fault (it is to be specifically pointed out that the reset fault is a name of a cleared fault, that is, when the fault set in the fault conversion setting is a rotated fault and is in a non-alarm condition, a name of a fault to be cleared, and the reset faults in the rest are reserved faults, that is, when the fault exists and is in a non-alarm condition, the fault set in the fault resetting corresponding to the fault is cleared), a reset source (a pull-down option, which includes a loop, a phase and a device, and reset according to the set source after selection), a reset state (a pull-down option, which includes all, alarm and non-alarm conditions, and reset according to the set state after selection), and a reset time (an input box, unit is minutes, and the reset time is the reset time of the fault conversion alarm reporting time-the reset fault conversion time, and after setting, judging to remove the weight according to the set time length), and removing the weight alarm value (a range input box which removes the weight according to the set range after setting). The failing bank reset page of the system is shown in detail in the lower half of fig. 2.
From the above, the fault and duplicate removal condition includes a duplicate removal fault, a duplicate removal source, a duplicate removal state, a duplicate removal time and a duplicate removal alarm value. The user may select one or a combination of several of the above as a condition for determining whether to remove a fault.
In the setting page of the alarm-to-fault condition shown in fig. 2, the names of the faults of the same type of alarm conversion of each manufacturer are unified as leakage faults; the alarm with the alarm value not less than 4 is limited to be capable of switching to the fault, and the serious alarm is screened out to be switched to the fault so as to be convenient for subsequent automatic pushing and timely processing; the alarm value updating is started, repeated alarms are eliminated, and meanwhile the latest alarm value data are obtained, so that the information synchronization is ensured; the method eliminates the frequently occurring concurrent fire zero imbalance fault, namely invalid alarm, and is accurate to the circuit weight removal; the weight-removing state ensures that at least one fault exists and can be processed in time; the deduplication time is typically set to a reasonable concurrency period, excluding only concurrent failures within the concurrency period.
And S3, when the alarm only comprises a first alarm meeting the fault conversion condition, converting the first alarm into a first fault.
And when the alarm further comprises a second alarm meeting the fault conversion condition, the second alarm occurs no earlier than the first alarm, and the fault names of the first alarm and the second alarm are the same, converting the first alarm into the fault, and eliminating the second alarm.
Or when the alarm further comprises a third alarm meeting the fault conversion condition, the conversion time of the third alarm is not earlier than that of the first alarm, and the third alarm meets the fault rearrangement condition, the first alarm is converted into the fault, and the third fault is eliminated.
When an alarm reported by one device (corresponding to a second alarm described in the claims) can be correspondingly converted into a fault a, if another fault B which has the same name as the fault and is not capable of being extinguished exists in the system (i.e., corresponding to a first alarm conversion), the fault a which occurs after the system is eliminated (if two alarms occur simultaneously, one of the two alarms is retained and is switched to a fault, and the other alarm is eliminated, i.e., the fault is failed to be switched, i.e., the system does not convert the alarm into a fault, the retained alarm corresponds to the first alarm, and the eliminated alarm corresponds to the second alarm).
When the alarm value update option is enabled in the fault conversion setting, the alarm value of the existing fault B is replaced with the alarm value of the second alarm occurring later. If the option is not enabled, the alarm value of the existing fault B is not updated.
When the above alarm (which corresponds to the third alarm described in the claims) reports, if there is another fault C (i.e., corresponds to the first alarm transition) in the system that is the same as the equipment and has not been cleared, and the alarm satisfies the fault rearrangement setting corresponding to the fault transformation setting of the fault C, the fault C is the rearrangement fault of the fault a, and the system eliminates the alarm (if two alarms occur simultaneously, it means that the first alarm is set as the primary alarm for retention, and the third alarm is set as the secondary alarm for elimination).
When any one of the faults B or C does not exist in the system, the system converts the alarm into the fault A, namely the alarm is converted into the fault success, and the system records the fault A in a fault list. The fault is recorded in a fault list according to the set fault name and the translation phase. The number of faults is determined by inverting the phase, if all the phases are selected, 3A/B/C phases are inverted respectively, and if a specific phase is selected, only 1 phase is inverted.
When the fire-zero imbalance alarm occurs independently, the fire-zero imbalance alarm is converted into a fire-zero imbalance fault, and subsequent automatic pushing judgment is carried out.
The overall logic flow diagram for alarm vs. fault is shown in fig. 3.
The system generates an alarm record in real time, and firstly judges whether the alarm can be converted into a fault according to the fault conversion setting. The judgment logic mainly comprises three points: first, whether the alarm name is in the failure transformation setting or not, and only when the alarm set in the failure transformation setting occurs, the failure transformation is judged, second, whether the device reporting the alarm is in the device group or not, and third, whether the alarm value of the alarm is in the transformation alarm value range or not.
If one of the alarm records does not satisfy the fault conversion condition set by the fault conversion, the alarm record fails to convert the fault. If the alarm is satisfied, the system performs fault resetting on the alarm according to the fault resetting condition set by the fault resetting.
When the fault is removed, whether the fault which has the same fault name as the equipment and is not alarmed still exists in the system or the heavy removal fault corresponding to the alarm is judged, and if the fault does not exist, the alarm is converted into the fault successfully. If yes, whether the source of the duplicate removal fault is met or not is continuously judged (the duplicate removal source of the duplicate removal fault is consistent with the generation source of the alarm, the duplicate removal can be successful), and if yes, the alarm is failed to be switched to the fault. If not, continuously judging whether the state of the duplicate removal fault is met, and if so, failing to alarm the duplicate removal fault. If not, continuously judging whether the interval between the time of the duplicate removal fault conversion and the time of the alarm is within the set time length, and if so, failing to convert the alarm into the fault. If not, continuously judging whether the alarm value of the alarm meets the re-alarm value, and if so, failing to convert the alarm into a fault. If not, the alarm goes to failure success.
If the alarm goes wrong successfully, the system converts the alarm into a fault of a correspondingly set fault name.
The judgment sequence of the overall logic of the alarm-to-fault can be reasonably adjusted, and the increase of judgment conditions is supported.
And S4, setting an automatic pushing condition, and automatically pushing the first fault when the first fault meets the automatic pushing condition.
The automatic push setting is carried out in the system, and the automatic push setting comprises a fault name (pull-down option, selecting a fault needing automatic push), an alarm value (a range input box, pushing according to a set range after setting), recovery delay (the input box, the unit is divided, a fault push alarm observation period is set, an alarm is cancelled in the observation period after setting, the alarm is not pushed, the deadline of the observation period is fault conversion time + set time length), push time (the check box is added with the input box, the prompt push can be checked, or the self-defined time push is input), push and weight removal faults (pull-down option, if the selected weight removal faults are pushed by the same equipment, the current faults are not pushed), and weight removal time (the input box, the effective time length of the push and weight removal faults is set, and the weight removal time is current fault conversion time-weight removal fault push time). The automatic push setup page of the system is shown in detail in fig. 4.
The overall logic flow diagram of automatic push is shown in fig. 5. When the fault is newly converted, whether the fault name is in automatic pushing setting or not needs to be judged, automatic pushing is judged only when the fault set in automatic pushing occurs, automatic pushing is not needed if the fault is not set, if the fault is set, the alarm value of the current fault is continuously judged to be within the range of the alarm value to be pushed, and if the fault is not met, automatic pushing is not carried out. If yes, continuously judging whether the set weight removal fault is pushed by the same equipment, if yes, judging the weight removal time, and if the interval between the current fault conversion time and the weight removal fault pushing time exceeds the set time length, otherwise, not pushing. If the heavy discharge fault is not pushed or the heavy discharge time is longer than the set time, continuing to judge whether the recovery delay exists, and if the alarm disappears in the set time after the fault conversion, not automatically pushing, and if the alarm disappears, automatically pushing to a production system according to the set pushing time, and informing maintenance personnel to go to a fault point for processing.
In the setting page of automatic pushing shown in fig. 4, an electric leakage fault is selected as a fault that needs to be actively pushed, so that the timeliness of pushing the fault is ensured; limiting the range of alarm values to be pushed, and screening out serious faults to be pushed; the recovery delay time is set, the condition that the equipment failure occurs frequently and is reported and eliminated is avoided (after the system pushes a failure work order, a maintenance team arranges personnel to go to maintenance, but the failure is actively eliminated), and the resource waste is avoided; immediate pushing is set, and timeliness of fault pushing is guaranteed (individual serious faults with low urgency can be pushed in a user-defined time, for example, a fault occurring in the middle of the night can be pushed in a working period, and maintenance personnel can conveniently process the faults in the first time after working); the fire-zero imbalance fault is eliminated, and as described above, the fire-zero imbalance and the electric leakage are two faults with high concurrency, the maintenance modes are consistent, and repeated pushing is avoided; the principle of setting the weight removal time is the same as that in the failure removal time, and the weight removal time is generally set to a reasonable concurrent period, and only concurrent failures within the concurrent period are removed.
The judgment sequence of the overall logic of automatic pushing can be reasonably adjusted, and the increase of judgment conditions is supported.
The failure also supports manual push. The system management personnel can manually analyze the faults which are not automatically pushed and then manually push the faults which need to be processed in time to the production system.
The method of the embodiment unifies the fault names of the same type of alarm conversion of equipment of various manufacturers, reduces the learning cost of users, and meets the personalized requirements of the users; through various parameter judgment and rearrangement judgment, the failure repetition rate and the inefficiency are reduced, the automation and the intellectualization of urban road lighting management are improved, and the manual analysis workload is reduced; through automatic pushing judgment, the accuracy of fault pushing and the timeliness of processing are enhanced, the integrity of a fault processing flow is ensured, and the waste of resources is reduced.
The method described in this embodiment is not limited to the application of the control and management of the urban intelligent lighting system, but also can be applied to other technical fields of urban intelligent control and management, and technical fields of production, operation and maintenance, and the like.
Example two
The embodiment provides an intelligent fault handling system which comprises the following structures.
And the recording module is used for recording the generated alarm. The recording module records a system alarm and a device alarm, respectively. The recording module is provided with an equipment alarm recording table and is used for classifying equipment alarms so as to convert equipment alarms of the same type of each manufacturer into the same fault name in the following process.
And the fault verification module is used for verifying whether the alarm meets the fault conversion condition.
Before the system is used, a user firstly carries out fault conversion setting and corresponding fault re-elimination setting in the system. I.e. the fault deduplication condition corresponds to the fault conversion condition.
When an alarm is reported on one device, the fault verification module verifies whether the alarm meets a fault conversion condition. The alarm qualifies for a transition fault when the alarm satisfies a fault transition condition.
And the fault duplicate removal module is used for removing the second alarm when the alarms comprise a first alarm and a second alarm, the first alarm and the second alarm are verified by the fault judgment module respectively, the second alarm occurs no earlier than the first alarm, and the fault names converted by the first alarm and the second alarm are the same.
Or when the alarm comprises a first alarm and a third alarm, the first alarm and the third alarm respectively pass the verification of the fault judgment module, the third alarm occurs no earlier than the first alarm, and the third alarm meets the fault elimination condition, the fault elimination module eliminates the third alarm.
And when one alarm passes the verification of the fault verification module, the fault repetition elimination module carries out repetition elimination judgment on the alarm.
When an alarm is reported, the fault verification module preliminarily judges that the alarm can be converted into a fault with a certain fault name, and if another fault which has the same fault name as the equipment and does not alarm exists in the system, the fault resetting module eliminates the alarm, namely the alarm fails to be converted into the fault, namely the system does not convert the alarm into the fault.
When an alarm is reported, the fault verification module preliminarily judges that the alarm can be converted into a certain fault, and at the moment, if another fault which is the same as the equipment and is not eliminated exists in the system and the latter fault is a re-elimination fault of the former fault, the fault re-elimination module eliminates the alarm.
And the fault conversion module converts the first alarm into the first fault when the alarm only comprises the first alarm and the first alarm passes the verification of the fault judgment module.
When an alarm passes the verification of the fault verification module and the fault duplicate removal module respectively, the fault conversion module converts the alarm into a fault and records the fault in a fault list.
And the automatic pushing module is used for automatically pushing the first fault meeting the automatic pushing condition.
Before the system is used, the user also carries out automatic pushing setting in the system. And after the new fault is converted, automatic pushing is judged, and the automatic pushing module automatically pushes the fault meeting the judgment condition to a production system and informs maintenance personnel to go to a fault point for processing.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.
Claims (8)
1. An intelligent fault processing method is characterized by comprising the following steps:
when an alarm occurs, recording the alarm;
setting an alarm-to-fault condition, wherein the alarm-to-fault condition comprises a fault conversion condition and a fault duplicate removal condition, and the fault duplicate removal condition corresponds to the fault conversion condition;
the alarm types comprise system alarms and equipment alarms, and the equipment alarms of the same type are classified and converted into the same fault name;
converting the first alarm to a first fault when the alarm includes only a first alarm that satisfies the fault conversion condition;
when the alarm further comprises a second alarm meeting the fault conversion condition, the second alarm occurs no earlier than the first alarm, and the fault names of the first alarm and the second alarm are the same, converting the first alarm into the first fault, and excluding the second alarm;
or when the alarm further comprises a third alarm meeting the fault conversion condition, the third alarm occurs no earlier than the first alarm, and the third alarm meets the fault rearrangement condition, converting the first alarm into the first fault, and excluding the third alarm;
and setting an automatic pushing condition, and automatically pushing the first fault when the first fault meets the automatic pushing condition.
2. The intelligent fault handling method according to claim 1, wherein an equipment alarm log is provided for categorizing the equipment alarms.
3. The intelligent fault handling method of claim 1, wherein the first fault is updated according to the alarm value of the second alarm.
4. The intelligent fault handling method of claim 1, wherein the fault conversion conditions include conversion phase, application device grouping, and conversion alarm value.
5. The intelligent fault handling method of claim 1, wherein the fault deduplication condition comprises a deduplication fault, a deduplication source, a deduplication state, a deduplication time, and a deduplication alarm value.
6. The intelligent fault handling method according to claim 1, wherein the next automatic push is delayed.
7. The intelligent fault handling method of claim 1, wherein the automatic pushing comprises immediate pushing or custom time pushing.
8. An intelligent fault handling system, comprising:
the recording module is used for recording the generated alarm;
the fault verification module is used for verifying whether the alarm meets a fault conversion condition;
the fault repetition eliminating module is used for eliminating the second alarm when the alarms comprise a first alarm and a second alarm which pass the verification of the fault judging module respectively, the occurrence time of the second alarm is not earlier than that of the first alarm, and the fault names converted by the first alarm and the second alarm are the same;
or when the alarm comprises a first alarm and a third alarm, the first alarm and the third alarm are respectively verified by the fault judgment module, the third alarm occurs no earlier than the first alarm, and the third alarm meets a fault resetting condition, the fault resetting module resets the third alarm;
the fault duplicate removal condition corresponds to the fault conversion condition;
the fault conversion module is used for converting the first alarm into a first fault when the alarm only comprises the first alarm and the first alarm passes the verification of the fault judgment module;
and the automatic pushing module is used for automatically pushing the first fault meeting the automatic pushing condition.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011201781.2A CN112763936B (en) | 2021-02-04 | 2021-02-04 | Intelligent fault processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011201781.2A CN112763936B (en) | 2021-02-04 | 2021-02-04 | Intelligent fault processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112763936A CN112763936A (en) | 2021-05-07 |
| CN112763936B true CN112763936B (en) | 2021-11-26 |
Family
ID=75693270
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011201781.2A Active CN112763936B (en) | 2021-02-04 | 2021-02-04 | Intelligent fault processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112763936B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1860451A (en) * | 2003-10-16 | 2006-11-08 | 思科技术公司 | Policy-based network security management |
| CN107203843A (en) * | 2017-05-19 | 2017-09-26 | 国家电网公司 | Intelligent decision system is sent in long-range examination based on monitoring information |
| CN111106959A (en) * | 2019-12-20 | 2020-05-05 | 贵州黔岸科技有限公司 | Abnormity monitoring and alarming system and method for transportation management system |
| CN112055451A (en) * | 2020-07-14 | 2020-12-08 | 厦门市智联信通物联网科技有限公司 | Street lamp monitoring system with intelligent fault discrimination and intelligent fault analysis |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020124214A1 (en) * | 2001-03-01 | 2002-09-05 | International Business Machines Corporation | Method and system for eliminating duplicate reported errors in a logically partitioned multiprocessing system |
-
2021
- 2021-02-04 CN CN202011201781.2A patent/CN112763936B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1860451A (en) * | 2003-10-16 | 2006-11-08 | 思科技术公司 | Policy-based network security management |
| CN107203843A (en) * | 2017-05-19 | 2017-09-26 | 国家电网公司 | Intelligent decision system is sent in long-range examination based on monitoring information |
| CN111106959A (en) * | 2019-12-20 | 2020-05-05 | 贵州黔岸科技有限公司 | Abnormity monitoring and alarming system and method for transportation management system |
| CN112055451A (en) * | 2020-07-14 | 2020-12-08 | 厦门市智联信通物联网科技有限公司 | Street lamp monitoring system with intelligent fault discrimination and intelligent fault analysis |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112763936A (en) | 2021-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101009586B (en) | Processing method for alarm filtering condition in the alarming system | |
| CN103679554B (en) | Power grid accident separating brake aided analysis method | |
| CN103001824B (en) | A kind of supervisory control system and method for supervising monitoring multiple servers | |
| CN113191635B (en) | Intelligent management system for electric energy of construction engineering site | |
| CN110942235B (en) | Emergent evaluation system of electric power | |
| CN110348690B (en) | Tree search based result query menu grid accident auxiliary decision making system and method | |
| CN111127250B (en) | Power data monitoring event analysis system and method | |
| CN109741653B (en) | Intelligent power failure emergency treatment training simulation method based on reasoning | |
| CN110768845A (en) | Intelligent substation process level virtual connection fault positioning system | |
| CN103376348A (en) | Method of controlling fault current in system for monitoring and controlling power system | |
| JPH07212325A (en) | Fault display system in centralized monitoring system | |
| CN108768995B (en) | Substation self-adaptive master station access method | |
| CN112763936B (en) | Intelligent fault processing method and system | |
| CN113987724A (en) | Power grid risk identification method and system based on topology analysis | |
| CN111969709B (en) | Intelligent alarm method and system based on power system spare power automatic switching analysis | |
| CN110609761B (en) | Method and device for determining fault source, storage medium and electronic equipment | |
| CN105388882A (en) | Preliminary plan determining method and apparatus of power grid accident | |
| CN113359584B (en) | Method and device for diagnosing state of intelligent pole equipment in offline mode | |
| CN113328898B (en) | Fault diagnosis method and system with autonomous learning capability | |
| CN103268353A (en) | Power grid alarming automatic response system and power grid alarming automatic response method | |
| CN117559447B (en) | Power failure studying and judging data analysis method and system based on power grid model | |
| CN109992625B (en) | Remote integrated power grid data storage system and method | |
| CN114336500B (en) | Fault diagnosis and power restoration method, device and equipment for regional power grid | |
| US20240039780A1 (en) | System for determining mass outage and method of using | |
| CN116582485A (en) | Dual-network redundancy transmission method and device based on link selection |
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 | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A fault intelligent processing method and system Effective date of registration: 20220328 Granted publication date: 20211126 Pledgee: Xiamen Jinyuan Financing Guarantee Co.,Ltd. Pledgor: XIAMEN IOTCOMM TECHNOLOGY CO.,LTD. Registration number: Y2022980003369 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right |