CN112561262B - Experience feedback data pushing method applied to barrier analysis and computer terminal - Google Patents
Experience feedback data pushing method applied to barrier analysis and computer terminal Download PDFInfo
- Publication number
- CN112561262B CN112561262B CN202011395998.1A CN202011395998A CN112561262B CN 112561262 B CN112561262 B CN 112561262B CN 202011395998 A CN202011395998 A CN 202011395998A CN 112561262 B CN112561262 B CN 112561262B
- Authority
- CN
- China
- Prior art keywords
- failure
- barrier
- data
- information
- analysis
- 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
- 230000004888 barrier function Effects 0.000 title claims abstract description 284
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000009471 action Effects 0.000 claims abstract description 51
- 238000012937 correction Methods 0.000 claims abstract description 50
- 238000012545 processing Methods 0.000 claims abstract description 18
- 238000007726 management method Methods 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 9
- 238000007689 inspection Methods 0.000 claims description 3
- 230000008520 organization Effects 0.000 claims description 3
- 238000003908 quality control method Methods 0.000 claims description 3
- 238000012954 risk control Methods 0.000 claims description 3
- 230000010354 integration Effects 0.000 claims description 2
- 238000009472 formulation Methods 0.000 abstract description 3
- 239000000203 mixture Substances 0.000 abstract description 3
- 239000002699 waste material Substances 0.000 abstract description 2
- 230000002708 enhancing effect Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012549 training Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/06—Energy or water supply
-
- 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
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S10/00—Systems supporting electrical power generation, transmission or distribution
- Y04S10/50—Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Economics (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Health & Medical Sciences (AREA)
- Marketing (AREA)
- Theoretical Computer Science (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (AREA)
- Educational Administration (AREA)
- Public Health (AREA)
- Water Supply & Treatment (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to an experience feedback data pushing method and a computer terminal applied to barrier analysis, wherein the method comprises the following steps: acquiring historical data; processing the historical data to obtain barrier analysis information; the barrier analysis information includes: failure barrier information, failure cause information, and corrective action information; classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations; integrating failure reasons, corrective measures and failure barrier association relations to form an experience feedback database; barrier analysis was performed based on an empirical feedback database. According to the invention, the intelligent pushing is realized by forming the experience feedback database and utilizing the experience feedback database, so that the accuracy and efficiency of failure barrier identification and correction measure formulation are effectively improved, the manpower resources are greatly saved, and the waste cost caused by operation and technical errors is reduced.
Description
Technical Field
The invention relates to the technical field of barrier analysis of nuclear power plants, in particular to an empirical feedback data pushing method and a computer terminal applied to barrier analysis.
Background
With the development of big data technology and intelligent analysis technology, the technology of integrating experience feedback data flow and specific service flow has gradually matured, so that the requirements of function research and development and intelligent promotion in specific service scenes are more prominent and obvious. Therefore, the intelligentization, the refinement and the high efficiency of the application of the experience feedback data in each business process of the nuclear power plant are required to be improved, and the information is pushed timely and accurately.
However, the current nuclear power plant field still fails to provide a better intelligent pushing scheme for experience feedback data based on the requirement.
Disclosure of Invention
The technical problem to be solved by the invention is to provide an experience feedback data pushing method and a computer terminal applied to barrier analysis aiming at the defects in the prior art.
The technical scheme adopted for solving the technical problems is as follows: a method for pushing empirical feedback data applied to barrier analysis is constructed, comprising:
acquiring historical data;
processing the historical data to obtain barrier analysis information; the barrier analysis information includes: failure barrier information, failure cause information, and corrective action information;
classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations;
integrating the failure reasons, the corrective measures and the failure barrier association relations to form an experience feedback database;
and performing barrier analysis according to the experience feedback database.
Wherein the history data includes: a history report of nuclear power plant event analysis;
the processing the historical data to obtain barrier analysis information comprises the following steps:
and processing report information in the history report of the nuclear power plant event analysis, and extracting failure barrier information, failure reason information and corrective action information in the report information.
The classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations comprises the following steps:
based on the failure barrier information, the failure reason information and the correction measure information in the report information, summarizing the failure barrier data and the correction measure data corresponding to each failure reason;
respectively carrying out coding treatment on the failure barrier data and the correction measure data to obtain coding of the failure barrier data and coding of the correction measure data;
acquiring the code of each failure reason;
binding the codes of each failure reason with the codes of the corresponding failure barrier data and the codes of the correction measure data to obtain the association relation between each failure reason and the corresponding correction measure and the corresponding failure barrier;
and the association relations of all the failure reasons, the corresponding corrective measures and the failure barriers are the association relations of the failure reasons, the corrective measures and the failure barriers.
Wherein, the integrating the failure reason, the correction measure and the failure barrier association relation to form an experience feedback database includes:
and storing the failure reasons, the corrective measures and the failure barrier association relations in a database to form the experience feedback database.
Wherein said performing a barrier analysis from said empirical feedback database comprises:
determining the current failure reason;
and obtaining a failure barrier and corrective measures corresponding to the current failure reason according to the current failure reason and combining the experience feedback database.
Wherein the determining the current failure cause includes:
and determining the current failure reason according to the failure reason classification.
Wherein, according to the current failure reason and in combination with the experience feedback database, obtaining the failure barrier and the corrective measure corresponding to the current failure reason comprises:
acquiring the codes of the current failure reasons according to the current failure reasons;
and according to the codes of the current failure reasons, combining the experience feedback database to obtain failure barriers and corrective measures corresponding to the current failure reasons.
Wherein the method further comprises:
and classifying the failure barrier data by adopting a preset method.
Wherein, the classifying the failure barrier data by adopting a preset method includes:
and classifying the invalid barrier data according to the specific content of the invalid barrier data to obtain the small-class invalid barrier data.
Wherein, the classifying the failure barrier data by adopting a preset method further comprises:
and classifying the failure barrier data according to the historical working experience value to obtain large-class failure barrier data.
Wherein the large class of failure barrier data includes at least one of the small classes of failure barrier data.
Wherein the large class of failure barrier data comprises: administrative, work organization, project management, program standard, field management, risk control, quality control, equipment management, personnel, inspection, engineering, and physical barriers.
The invention also provides an experience feedback data pushing system applied to barrier analysis, which comprises:
an acquisition unit configured to acquire history data;
the processing unit is used for processing the historical data to obtain barrier analysis information; the barrier analysis information includes: failure barrier information, failure cause information, and corrective action information;
the association relation determining unit is used for classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations;
the integration unit is used for integrating the failure reasons, the corrective measures and the failure barrier association relations to form an experience feedback database;
and the barrier analysis unit is used for carrying out barrier analysis according to the experience feedback database.
The invention also provides a computer terminal comprising a processor and a memory for storing a computer program, the processor being adapted to execute the computer program stored by the memory to implement the empirical feedback data pushing method applied to barrier analysis as described above.
The present invention also provides a storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the empirical feedback data pushing method as described above applied to barrier analysis.
The method for pushing the experience feedback data applied to the barrier analysis and the computer terminal have the following beneficial effects: comprising the following steps: acquiring historical data; processing the historical data to obtain barrier analysis information; the barrier analysis information includes: failure barrier information, failure cause information, and corrective action information; classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations; integrating failure reasons, corrective measures and failure barrier association relations to form an experience feedback database; barrier analysis was performed based on an empirical feedback database. According to the invention, the intelligent pushing is realized by forming the experience feedback database and utilizing the experience feedback database, so that the accuracy and efficiency of failure barrier identification and correction measure formulation are effectively improved, the manpower resources are greatly saved, and the waste cost caused by operation and technical errors is reduced.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
fig. 1 is a flow chart of an empirical feedback data pushing method applied to barrier analysis according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an empirical feedback data pushing system applied to barrier analysis according to an embodiment of the present invention.
Detailed Description
For a clearer understanding of technical features, objects and effects of the present invention, a detailed description of embodiments of the present invention will be made with reference to the accompanying drawings.
In order to solve the defects of screening of failure barriers and corresponding correction action formulation in the event analysis process of the current nuclear power plant, the invention provides an experience feedback data pushing method applied to barrier analysis.
Specifically, referring to fig. 1, fig. 1 is a flow chart of an empirical feedback data pushing method applied to barrier analysis according to the present invention.
As shown in fig. 1, the empirical feedback data pushing method applied to barrier analysis includes:
step S101, historical data is acquired.
Optionally, the history data includes: historical reporting of nuclear power plant event analysis. Specifically, the historical report of the nuclear power plant event analysis includes: internal operational event reports and license operational event reports. The historical data of the embodiment of the invention comprises the following steps: historical multiple internal running event reports and multiple license running event reports.
Step S102, processing the historical data to obtain barrier analysis information; the barrier analysis information includes: failure barrier information, failure cause information, and corrective action information.
In some embodiments, processing the historical data to obtain barrier analysis information includes: and processing report information in the history report of the nuclear power plant event analysis, and extracting failure barrier information, failure reason information and corrective action information in the report information.
Specifically, for the obtained multiple historical internal operation event reports and multiple historical license operation event reports, each report records a failure barrier corresponding to each failure reason and corresponding corrective measures, for example, assume that the failure reason in report a includes: the failure reasons a1, a2 and a3, wherein the failure barriers corresponding to the failure reasons a1 are as follows: failure barrier b11, failure barrier b12, failure barrier b13; the failure barriers corresponding to the failure reason a2 are as follows: a failure barrier b21, a failure barrier b22; the failure barriers corresponding to the failure reason a3 are as follows: failure barrier c31, failure barrier c32, failure barrier c33, failure barrier c34; the corrective measures corresponding to the failure reason a1 are as follows: corrective action x11, corrective action x12, corrective action x 13; the corrective measures corresponding to the failure reason a2 are as follows: corrective measure x21, corrective measure x 22; the corrective measures corresponding to the failure reason a3 are as follows: corrective action x31, corrective action x32, corrective action x33, corrective action x 34. When the failure barrier information extraction is performed, the relevant information of the failure reason a1, the failure reason a2 and the failure reason a3 is extracted, and the failure barriers and the correction measures corresponding to the failure reason a1, the failure reason a2 and the failure reason a3 are also extracted, and meanwhile, the respective corresponding relations, namely the failure barriers and the correction measures (b 11, b12, b13 and x11, x12 and x 13) corresponding to the failure reason a1, the failure barriers and the correction measures (b 21, b22 and x21 and x 22) corresponding to the failure reason a2 and the failure barriers and the correction measures (c 31, c32, c33, c34 and x31, x32, x33 and x 34) corresponding to the failure reason a3 are also reserved.
Therefore, the report information in the embodiment of the invention includes the failure cause information, the failure barrier information, the correction measure information and the corresponding relation among all the internal operation event reports, and the failure cause information, the failure barrier information, the correction measure information and the corresponding relation among all the license operation event reports.
And step S103, classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations.
In some embodiments, classifying, summarizing and encoding the barrier analysis information to obtain failure causes, corrective actions and failure barrier association relationships includes:
and step S1031, summarizing failure barrier data and correction measure data corresponding to each failure reason based on the failure barrier information, the failure reason information and the correction measure information in the report information.
Specifically, the failure barrier data corresponding to each failure cause includes: the number and content of failure barriers corresponding to each failure cause. The corrective action data corresponding to each failure cause includes: the number and content of corrective actions corresponding to each failure cause.
For example, as previously described, in report a: the failure barrier corresponding to the failure cause a1 includes: failure barrier b11, failure barrier b12, and failure barrier b13. As described above, the corrective measures corresponding to the failure cause a1 are: corrective action x11, corrective action x12, and corrective action x 13.
In report B: the failure barrier corresponding to the failure cause a1 includes: failure barrier b11, failure barrier b12, failure barrier b13, and failure barrier b14; the corrective measures corresponding to the failure reason a1 include: corrective action x11, corrective action x12, corrective action x13, corrective action x14, and corrective action x15.
The summary can be obtained: the failure barrier data corresponding to the failure cause a1 includes: the four invalidation barriers correspond to the following contents: failure barrier b11, failure barrier b12, failure barrier b13, and failure barrier b14. The corrective action data corresponding to the failure cause a1 includes: the contents of the five correction measures are respectively as follows: corrective action x11, corrective action x12, corrective action x13, corrective action x14, and corrective action x15.
Further, after summarizing the failure barrier data corresponding to each failure reason in all reports, classifying the failure barrier data by adopting a preset method. Specifically, the failure barrier data can be classified according to the historical working experience value, and the large-class failure barrier data can be obtained. And classifying the failure barrier data according to the specific content of the failure barrier data to obtain the failure barrier data of the small category. Wherein the large class of failure barrier data includes at least one small class of failure barrier data.
In some embodiments, assuming that the historical data is a report of 2909, extracting the failure barrier data corresponding to each failure cause in the report of 2909 may obtain 4638 failure barriers and corresponding contents thereof, and categorizing and summarizing the 4638 failure barriers, where the categorizing and summarizing may include: administrative, work organization, special management, program, site management, risk control, quality control, equipment management, personnel, inspection, engineering installation, engineering, and entity etc. 17 broad classes of failure barriers, and then 165 subclasses of failure barriers can be grouped together according to the specific content of each failure barrier.
Further, after 17 major classes of failure barriers and 165 minor classes of failure barriers are classified and summarized, the extracted correction measure data are summarized aiming at the failure barriers of different classes, so that the correction measure corresponding to the failure barrier of each class is summarized.
And S1032, respectively encoding the failure barrier data and the correction measure data to obtain the encoding of the failure barrier data and the encoding of the correction measure data.
In some embodiments, after 17 major classes of failure barriers and 165 minor classes of failure barriers are summarized in the step S1301, corresponding coding settings are performed on the summarized 17 major classes of failure barriers to achieve the purpose of identifying the 17 major classes of failure barriers through the set codes, and similarly, corresponding coding settings are also performed on the summarized 165 minor classes of failure barriers, so that the purpose of identifying the 165 minor classes of failure barriers can be achieved through the set codes.
Further, corresponding codes are also carried out for the correction measures corresponding to the summarized failure barriers of each category, so that the corresponding relation between the codes of one category of failure barriers and the codes of the correction measures corresponding to the codes can be obtained.
Step S1033, obtaining codes of each failure reason.
Step S1034, binding the codes of each failure reason and the corresponding codes of the failure barrier data and the corresponding codes of the correction measure data, and obtaining the association relation between each failure reason and the corresponding correction measure and the corresponding failure barrier. And the association relations between all failure reasons and corresponding correction measures and failure barriers are failure reasons, correction measures and failure barrier association relations.
In some embodiments, as previously described, the summary results in:
the failure barrier data corresponding to the failure cause a1 includes: the four invalidation barriers correspond to the following contents: failure barrier b11, failure barrier b12, failure barrier b13, and failure barrier b14.
The corrective action data corresponding to the failure cause a1 includes: the contents of the five correction measures are respectively as follows: corrective action x11, corrective action x12, corrective action x13, corrective action x14, and corrective action x15.
Assume that the code of failure cause a1 is 01. The failure barriers b11 and b12 belong to the administrative category, which is coded 001, the failure barrier b13 belongs to the program standard, which is coded 002, and the failure barrier b14 belongs to the anti-human, which is coded 003.
Corrective action x11 and corrective action x12 correspond to failure barrier b11, which is coded 100, corrective action x13 corresponds to failure barrier b12, which is coded 101, corrective action x14 corresponds to failure barrier b13, which is coded 110, and corrective action x15 corresponds to failure barrier b14, which is coded 111.
Binding the code of the failure reason a1 and the code of the failure barrier data and the code of the correction measure data corresponding to the code of the failure reason a1 to be: binding 01 with 001, 002, 003 and 100, 101, 110 and 111 to obtain the corresponding corrective action and failure barrier association relation of the failure reason a 1.
And step S104, integrating the failure reasons, the corrective measures and the failure barrier association relations to form an experience feedback database.
In some embodiments, integrating the failure cause, corrective action, and failure barrier associations, forming the empirical feedback database includes: and storing the failure reasons, the corrective measures and the failure barrier association relations in a database to form an experience feedback database.
And step 105, performing barrier analysis according to the experience feedback database.
In some embodiments, performing the barrier analysis based on the empirical feedback database includes: determining the current failure reason; and according to the current failure cause, combining an experience feedback database to obtain a failure barrier and corrective measures corresponding to the current failure cause.
In some embodiments, determining the current failure cause includes: and determining the current failure reason according to the failure reason classification.
Specifically, the failure cause classification includes: equipment failure cause, human cause, and management cause. Based on this, in the event analysis process, it is possible to determine which of the device failure cause, the human cause, and the management cause the failure cause is based on the device failure cause, the human cause, and the management cause.
Further, in some embodiments, based on the current failure cause, in combination with the empirical feedback database, obtaining a failure barrier and corrective action corresponding to the current failure cause includes: acquiring the codes of the current failure reasons according to the current failure reasons; and according to the codes of the current failure reasons, combining an experience feedback database to obtain failure barriers and corrective measures corresponding to the current failure reasons.
For example, when the event analysis is performed, the content of determining the failure cause is as follows according to the classification of the failure cause (i.e. the equipment failure cause, the human cause and the management cause): when the office is switched, insufficient communication is caused, and the category of the current failure reason can be determined according to the content of the failure reason as follows: for human reasons, therefore, the coding of the current failure cause can be obtained: 0101.
after the code 0101 of the current failure cause is obtained, the code is input into an experience feedback database, the experience feedback database obtains the corresponding failure barrier code according to the association relation between the code (0101) and the corresponding correction measure and the failure barrier, and the corresponding failure barrier is obtained according to the obtained failure barrier code. Let the failure barrier corresponding to 0101 be the failure of the information exchange or imperfect program file. Thus, the empirical feedback database pushes to the user both types of failure barriers to failure in the exchange of information or incomplete program files. After receiving the information exchange failure or the incomplete two types of failure barriers of the program file, the user further analyzes and compares the information exchange failure or the incomplete two types of failure barriers, and finally confirms that the information exchange failure is the information exchange failure, namely confirms that the failure barrier is the information exchange failure.
Further, after determining that the failure barrier is an information exchange failure, the experience feedback database can directly obtain corresponding correction measures in the experience feedback data based on the association relation of the correction measures corresponding to the failure barrier that is the information exchange failure, and the setting of the correction measures corresponding to the information exchange failure includes: and (3) enhancing measures such as enhancing training, adding a confirmation item in a work order, enhancing the use of a human factor tool card and the like, pushing the obtained measures such as enhancing training, adding the confirmation item in the work order, enhancing the use of the human factor tool card and the like to a user by using an experience feedback database, analyzing and comparing the user, and finally confirming that the corrective measure is the human factor tool card. And (5) completing barrier analysis work.
According to the embodiment of the invention, the historical data are summarized into the failure barrier categories to form the experience feedback database, and the binding relation between the failure barrier and the failure reasons and the correction measures is stored in the experience feedback database, so that different failure barrier categories can be matched by combining the reason classification when the event analysis is carried out, the identified failure barrier can be intelligently pushed to the event analysis personnel for judgment and application by the event analysis personnel, and the accuracy and efficiency of the identification of the failure barrier and the establishment of the correction measures in the event analysis process are effectively improved through the different correction measures corresponding to the failure barrier on the basis.
Referring to fig. 2, fig. 2 is a schematic structural diagram of an empirical feedback data pushing system applied to barrier analysis according to an embodiment of the present invention. The system for pushing the experience feedback data applied to the barrier analysis can be used for realizing the method for pushing the experience feedback data applied to the barrier analysis disclosed by the embodiment of the invention.
Specifically, as shown in fig. 2, the empirical feedback data pushing system applied to barrier analysis includes:
an acquisition unit 201 for acquiring history data.
And the processing unit 202 is configured to process the historical data to obtain barrier analysis information. Wherein the barrier analysis information includes: failure barrier information, failure cause information, and corrective action information.
And the association relation determining unit 203 is configured to classify, summarize and encode the barrier analysis information, and obtain failure reasons, corrective measures and failure barrier association relations.
And the integrating unit 204 is configured to integrate the failure cause, the corrective measure and the failure barrier association relationship to form an experience feedback database.
And a barrier analysis unit 205 for performing a barrier analysis according to the empirical feedback database.
Further, the invention also provides a computer terminal, which comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for executing the computer program stored in the memory to realize the empirical feedback data pushing method applied to barrier analysis disclosed by the embodiment of the invention.
Further, the present invention also provides a storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the empirical feedback data pushing method for barrier analysis disclosed in the embodiments of the present invention.
In the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, and identical and similar parts between the embodiments are all enough to refer to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above embodiments are provided to illustrate the technical concept and features of the present invention and are intended to enable those skilled in the art to understand the content of the present invention and implement the same according to the content of the present invention, and not to limit the scope of the present invention. All equivalent changes and modifications made with the scope of the claims should be covered by the claims.
Claims (13)
1. An empirical feedback data pushing method applied to barrier analysis, comprising:
acquiring historical data;
processing the historical data to obtain barrier analysis information; the barrier analysis information includes: failure barrier information, failure cause information, and corrective action information;
classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations;
integrating the failure reasons, the corrective measures and the failure barrier association relations to form an experience feedback database;
performing a barrier analysis according to the empirical feedback database;
the history data includes: a history report of nuclear power plant event analysis;
the processing the historical data to obtain barrier analysis information comprises the following steps:
processing report information in a history report of the nuclear power plant event analysis, and extracting failure barrier information, failure reason information and corrective measure information in the report information;
the classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations comprises the following steps:
based on the failure barrier information, the failure reason information and the correction measure information in the report information, summarizing the failure barrier data and the correction measure data corresponding to each failure reason;
respectively carrying out coding treatment on the failure barrier data and the correction measure data to obtain coding of the failure barrier data and coding of the correction measure data;
acquiring the code of each failure reason;
binding the codes of each failure reason with the codes of the corresponding failure barrier data and the codes of the correction measure data to obtain the association relation between each failure reason and the corresponding correction measure and the corresponding failure barrier;
and the association relations of all the failure reasons, the corresponding corrective measures and the failure barriers are the association relations of the failure reasons, the corrective measures and the failure barriers.
2. The method for pushing experience feedback data applied to barrier analysis according to claim 1, wherein integrating the failure cause, the corrective action, and the failure barrier association relation to form an experience feedback database comprises:
and storing the failure reasons, the corrective measures and the failure barrier association relations in a database to form the experience feedback database.
3. The method for pushing empirical feedback data for use in barrier analysis according to claim 1, wherein the performing barrier analysis according to the empirical feedback database comprises:
determining the current failure reason;
and obtaining a failure barrier and corrective measures corresponding to the current failure reason according to the current failure reason and combining the experience feedback database.
4. The empirical feedback data pushing method for use in barrier analysis of claim 3, wherein the determining the current failure cause comprises:
and determining the current failure reason according to the failure reason classification.
5. The method for pushing empirical feedback data for barrier analysis according to claim 3, wherein the obtaining, according to the current failure cause and in combination with the empirical feedback database, the failure barrier and corrective action corresponding to the current failure cause comprises:
acquiring the codes of the current failure reasons according to the current failure reasons;
and according to the codes of the current failure reasons, combining the experience feedback database to obtain failure barriers and corrective measures corresponding to the current failure reasons.
6. The empirical feedback data pushing method for use in barrier analysis of claim 1, further comprising:
and classifying the failure barrier data by adopting a preset method.
7. The method for pushing empirical feedback data for use in barrier analysis according to claim 6, wherein classifying the failed barrier data using a predetermined method comprises:
and classifying the invalid barrier data according to the specific content of the invalid barrier data to obtain the small-class invalid barrier data.
8. The method for pushing empirical feedback data for use in barrier analysis according to claim 7, wherein classifying the failed barrier data using a predetermined method further comprises:
and classifying the failure barrier data according to the historical working experience value to obtain large-class failure barrier data.
9. The empirical feedback data pushing method for use in barrier analysis of claim 8, wherein the large class of failed barrier data includes at least one of the small classes of failed barrier data.
10. The empirical feedback data pushing method for use in barrier analysis of claim 9, wherein the large class of failed barrier data comprises: administrative, work organization, project management, program standard, field management, risk control, quality control, equipment management, personnel, inspection, engineering, and physical barriers.
11. An empirical feedback data pushing system for barrier analysis, comprising:
an acquisition unit configured to acquire history data;
the processing unit is used for processing the historical data to obtain barrier analysis information; the barrier analysis information includes: failure barrier information, failure cause information, and corrective action information;
the association relation determining unit is used for classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations;
the integration unit is used for integrating the failure reasons, the corrective measures and the failure barrier association relations to form an experience feedback database;
a barrier analysis unit for performing a barrier analysis based on the empirical feedback database;
the history data includes: a history report of nuclear power plant event analysis;
the processing the historical data to obtain barrier analysis information comprises the following steps:
processing report information in a history report of the nuclear power plant event analysis, and extracting failure barrier information, failure reason information and corrective measure information in the report information;
the classifying, summarizing and encoding the barrier analysis information to obtain failure reasons, corrective measures and failure barrier association relations comprises the following steps:
based on the failure barrier information, the failure reason information and the correction measure information in the report information, summarizing the failure barrier data and the correction measure data corresponding to each failure reason;
respectively carrying out coding treatment on the failure barrier data and the correction measure data to obtain coding of the failure barrier data and coding of the correction measure data;
acquiring the code of each failure reason;
binding the codes of each failure reason with the codes of the corresponding failure barrier data and the codes of the correction measure data to obtain the association relation between each failure reason and the corresponding correction measure and the corresponding failure barrier;
and the association relations of all the failure reasons, the corresponding corrective measures and the failure barriers are the association relations of the failure reasons, the corrective measures and the failure barriers.
12. A computer terminal comprising a processor and a memory, the memory for storing a computer program, the processor for executing the computer program stored in the memory to implement the empirical feedback data pushing method of any of claims 1-10 for use in barrier analysis.
13. A storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the empirical feedback data pushing method for barrier analysis according to any of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011395998.1A CN112561262B (en) | 2020-12-03 | 2020-12-03 | Experience feedback data pushing method applied to barrier analysis and computer terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011395998.1A CN112561262B (en) | 2020-12-03 | 2020-12-03 | Experience feedback data pushing method applied to barrier analysis and computer terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112561262A CN112561262A (en) | 2021-03-26 |
| CN112561262B true CN112561262B (en) | 2023-07-18 |
Family
ID=75047556
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011395998.1A Active CN112561262B (en) | 2020-12-03 | 2020-12-03 | Experience feedback data pushing method applied to barrier analysis and computer terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112561262B (en) |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106779402A (en) * | 2016-12-13 | 2017-05-31 | 深圳中广核工程设计有限公司 | Nuclear power plant's emergency rating judges expert system and method |
| CN110533308B (en) * | 2019-08-16 | 2022-05-17 | 中国核电工程有限公司 | Establishment method and availability evaluation method of process system availability database |
-
2020
- 2020-12-03 CN CN202011395998.1A patent/CN112561262B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112561262A (en) | 2021-03-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113407517B (en) | Data quality health degree analysis method and system based on multidimensional analysis technology | |
| CN111176953B (en) | Abnormality detection and model training method, computer equipment and storage medium | |
| CN114048870A (en) | Power system abnormity monitoring method based on log characteristic intelligent mining | |
| CN109614433A (en) | The recognition methods of data blood relationship, device, equipment and storage medium between operation system | |
| CN114449018B (en) | Automatic log file uploading method and system for power acquisition terminal | |
| CN111506635A (en) | System and method for analyzing residential electricity consumption behavior based on autoregressive naive Bayes algorithm | |
| CN112733147A (en) | Equipment safety management method and system | |
| CN113806343B (en) | Evaluation method and system for Internet of vehicles data quality | |
| CN114356900A (en) | Power data anomaly detection method, device, equipment and medium | |
| CN112561262B (en) | Experience feedback data pushing method applied to barrier analysis and computer terminal | |
| CN111581110B (en) | Service data accuracy detection method, device, system and storage medium | |
| CN116074215B (en) | Network quality detection method, device, equipment and storage medium | |
| CN112182065A (en) | Asset management system and method based on automatic acquisition and multi-source import | |
| CN117390015A (en) | Method and device for storing battery passport and storage medium | |
| CN115658620B (en) | Data authorization sharing method and system based on big data | |
| CN110795308A (en) | Server inspection method, device, equipment and storage medium | |
| CN111143622B (en) | Fault data set construction method based on big data platform | |
| CN110851486A (en) | Data storage method and device | |
| CN114218383A (en) | Method, device and application for judging repeated events | |
| CN103728330B (en) | Carbon-13 nmr spectra data are utilized to determine method and the system of organic compound structure | |
| CN111626586B (en) | Data quality detection method, device, computer equipment and storage medium | |
| CN116757334B (en) | Financial data processing method, system, readable storage medium and computer | |
| CN110119406B (en) | Method and device for checking real-time task records | |
| Chen et al. | Pre-processing and audit of power consumption data based on composite mathematical statistics model | |
| CN114462196A (en) | Electric energy meter state evaluation and replacement method, device and terminal |
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 |