Nuclear power overhaul key project planning method

Abstract

The invention relates to the technical field of nuclear power overhaul, and aims to solve the problems that data cannot be updated in real time, whether an overhaul key project is matched with an overhaul period cannot be quickly judged, the efficiency is low, errors are easy to occur, and a user cannot conveniently inquire when the overhaul key project plan is edited and displayed through an EXCEL table in the prior art. The invention provides a nuclear power overhaul key project planning method, which comprises the following steps: reading a preventive database key project list, and uploading non-preventive database projects; determining the work type of the project; a key project planning first draft is compiled; comparing the project overhaul type with the work type, and reminding an unmatched project; analyzing unmatched projects, and modifying and planning to be matched with the overhaul type; and a key project planning final draft is formed after modification, and is published and displayed to the user after being checked to be correct. According to the method, the work content, the overhaul number and the period of the overhaul key project are automatically read from the preventive database, and the first draft of the whole-life overhaul key project planning is automatically formed.

Description

Technical Field

[0001] The invention relates to the technical field of nuclear power overhaul, and in particular to a method for planning key nuclear power overhaul projects. Background Art

[0002] There are many nuclear power plant overhaul projects, some of which have a significant impact on the safety, quality, progress and cost of the unit overhaul. If such projects are not identified and arranged properly, they will directly affect the power generation and operating performance of the power plant.

[0003] At present, we mainly rely on personal experience and ability to identify key overhaul projects, analyze the windows and duration of projects, adjust project plans, and judge whether the project duration matches the overhaul duration. There is a lack of unified standards and methods. In addition, we use Excel format to compile and display plans, and rely on manual comparison of database data to compile and upgrade planning tables. Data cannot be updated in real time, is prone to errors, is inefficient, versions are easily confused, and are inconvenient to query. Summary of the invention

[0004] The main purpose of the present invention is to provide a nuclear power overhaul key project planning method to solve the problems that the data of the original overhaul key project planning edited and displayed through EXCEL tables cannot be updated in real time, cannot quickly determine whether the overhaul key projects and the overhaul period match, is inefficient, prone to errors, and is inconvenient for users to query.

[0005] Another object of the present invention is to provide a method for planning key nuclear power overhaul projects to solve the problem that the original key overhaul projects are difficult to identify.

[0006] In order to achieve the above object, the present invention provides the following technical solutions:

[0007] A method for planning key nuclear power overhaul projects, comprising:

[0008] Step 1: Read the list of key items in the preventive database and upload the items in the non-preventive database;

[0009] Step 2: Determine the type of work for the project;

[0010] Step 3: Prepare the first draft of key project planning;

[0011] Step 4: Compare the project overhaul type and work type, and remind the mismatched projects;

[0012] Step 5: Analyze the unmatched items and modify the plan to match the overhaul type;

[0013] Step 6: After modification, the final draft of the key project plan is formed, and after verification, it is released and displayed to users.

[0014] In some embodiments, for PM projects that have been marked in the overhaul key project field in the preventive database, the PMID-PMRQ, equipment code, work content, start value, cycle, and last execution time field information of the marked project are read into the corresponding fields of the overhaul key project planning table.

[0015] In some embodiments, relevant information of two types of non-preventive database projects, major technical transformation and major defect projects, are uploaded to the overhaul key project planning table.

[0016] In some embodiments, a list of key projects is selected before step 1, and the list of key projects includes:

[0017] (a) Three major tests for a ten-year overhaul;

[0018] (b) Major equipment items and tests for the primary circuit such as pressure vessels and evaporators;

[0019] (c) Power supply projects;

[0020] (d) Projects involving network lines;

[0021] (e) Projects with heavy loads under high voltage switchboards;

[0022] (f) Items of generator and steam turbine bodies.

[0023] In some embodiments, step 2 specifically includes:

[0024] Step 2.1: Determine the implementation period of the project;

[0025] Step 2.2: Determine the implementation window;

[0026] Step 2.3: Compare the project's windows and durations with those of the standard milestones;

[0027] Step 2.4: Determine the type of project work.

[0028] In some embodiments, if the implementation window of the project is M and the implementation period is T, the milestone window M of this type of unit is T when the standard period of the A-type overhaul is T. A , the standard duration of a Class B overhaul is T B , the standard duration of a C-type overhaul is T C , determine the project work type according to the following method:

[0029] If T≤T C , and T≤T B , T≤T A , then the work type of the project is ABC;

[0030] If T>T C, and T≤T B , T≤T A , then the work type of the project is AB;

[0031] If T>T C , and T>T A , T≤T B , then the work type of the project is B;

[0032] If T>T C , and T>T B , T≤T A , then the work type of the project is A;

[0033] If T>T A , and T≤T C , T≤T B , then the work type of the project is BC;

[0034] If T>T A , and T>T B , T≤T C , then the work type of the project is C;

[0035] If T>T B , and T≤T C , T≤T A , then the work type of the project is AC.

[0036] In some embodiments, if the implementation windows of the two projects are consistent and have a logical relationship of precedence, the implementation durations of the two projects are merged and then compared with the durations in the standard milestones.

[0037] In some embodiments, step 3 specifically includes:

[0038] Step 3.1: Automatically generate the pre-maintenance key project plan (i.e., automatically marked plan) according to the overhaul number and cycle in the database, and manually mark the plan with reference to the automatically marked plan to form a first draft (for key project plans that are not compiled for the first time, the manually marked first version is the plan mark released in the previous version);

[0039] Step 3.2: Compare the automatic marking plan and the manual marking plan to see if they are consistent, and automatically prompt where the plans are inconsistent;

[0040] Step 3.3: Plan major technical improvements and major defect projects.

[0041] In some embodiments, step 3.1 specifically includes:

[0042] Step 3.1.1: Calculate the predicted overhaul number for each item in the key project planning table, and automatically mark and plan each overhaul item to be performed;

[0043] Step 3.1.2: Refer to the mark in step 3.1.1, and combine it with the actual planning situation to manually mark it in another location. For key project plans that are not compiled for the first time, the manual marking of the first version is the planning mark released in the previous version. Automatic marking and manual marking are usually consistent. They will be inconsistent only when the project start value or period has changed or the manual marking has been manually adjusted.

[0044] In some embodiments, the work type and overhaul type of the project are compared, and if there is a mismatch, the work type of the project is marked.

[0045] Compared with the prior art, the nuclear power overhaul key project planning method provided by the present invention has the following beneficial effects:

[0046] The present invention automatically reads the work content, overhaul number and cycle of the overhaul key project in the preventive database, and automatically forms a preliminary draft of the whole life cycle overhaul key project planning.

[0047] The method of the present invention has extremely high timeliness and refreshes data in real time according to items in the database.

[0048] Furthermore, the present invention proposes an objective method for determining the implementation period of a key project that does not rely on human subjective judgment.

[0049] Furthermore, the present invention realizes an automatic reminder function for database item changes.

[0050] Furthermore, the present invention proposes an innovative concept of project "work type", and classifies key projects (work type) according to the overhaul type, which is used to determine whether the key projects match the overhaul period. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solution of the present invention, the following briefly introduces the drawings required for the technical description.

[0052] Figure 1 A flow chart of a method for planning key nuclear power overhaul projects provided by the present invention;

[0053] Figure 2 A flowchart for selecting a list of key projects provided by the present invention;

[0054] Figure 3 This is a rendering of the planning and display method for the overhaul key project provided by the present invention. DETAILED DESCRIPTION

[0055] The following is further explained in detail through specific implementation methods.

[0056] like Figure 1As shown, the present invention provides a method for planning key nuclear power overhaul projects, comprising the following steps:

[0057] Step 1: Read the list of key items in the preventive database and upload the items in the non-preventive database. It has extremely high timeliness and refreshes data in real time according to the items in the database.

[0058] For PM items that have been marked in the overhaul key project field in the preventive database, the overhaul management system will read the PMID-PMRQ, equipment code, work content, start value (overhaul number corresponding to the database), cycle, last execution time and other field information into the corresponding fields of the overhaul key project planning table.

[0059] Since major technical transformation and major defect projects are not preventive database projects but non-preventive database projects, relevant information needs to be manually uploaded to the overhaul key project planning table.

[0060] As an implementable approach, Figure 2 As shown, a list of key projects needs to be selected, and the key projects are selected from the periodic projects in the preventive maintenance database, the technical transformation projects in the technical transformation project list, and the projects in the unit defect list. Key projects need to meet the following conditions:

[0061] (1) Seriously affecting the reliability of unit equipment, that is, selecting from the equipment classification;

[0062] (2) Influence on the overhaul construction period, select from the implementation period;

[0063] (3) Due to resource or technical constraints such as venue, materials, external collaboration, etc., advance arrangements are required to facilitate the work.

[0064] Based on the above conditions, key projects can be summarized into the following projects, which are convenient and quick to select from tens of thousands of projects:

[0065] (a) Three major tests for a ten-year overhaul;

[0066] (b) Major equipment items and tests for the primary circuit such as pressure vessels and evaporators;

[0067] (c) Power supply (main transformer, auxiliary transformer, diesel engine, switchboard) projects;

[0068] (d) Projects involving network lines;

[0069] (e) Projects with heavy loads (pumps, motors) under high-voltage switchboards;

[0070] (f) Items of generator and steam turbine bodies.

[0071] Step 2: Determine the work type of the project. The work type is an innovative concept that classifies key projects according to the overhaul type (work type) in order to quickly determine whether the project can match the overhaul period. Step 2 specifically includes:

[0072] Step 2.1: Determine the implementation period of the project as follows:

[0073] For implemented projects, take the shortest duration of all previous work orders, the minimum value Min (implementation duration of historical work orders);

[0074] The implementation period of the work order = actual end time - actual start time;

[0075] If it has not been implemented, but has been implemented in units of the same reactor type, the shortest construction period of the reference unit shall be taken;

[0076] If it has not been implemented before and has not been implemented in other units, an estimated construction period will be given based on expert analysis.

[0077] Enter the implementation period into the implementation period field of the planning table (such as Figure 3 "Implementation period" column).

[0078] Step 2.2: Determine the implementation window. The implementation window of the project is marked according to two milestone nodes. First, determine between which two milestone stages each project can be arranged. The implementation window input data is displayed in the implementation window field (such as Figure 3 “Implementation Window” column).

[0079] Step 2.3: Compare the project's windows and durations with those of the standard milestones.

[0080] It should be noted that overhaul types are divided into Class A overhaul, Class B overhaul, and Class C overhaul. Different reactor types and overhaul types have their own standard target duration. Each type of overhaul has a standard milestone, and each standard milestone window has a corresponding standard duration. These standard information has been entered into the overhaul planning standard library in advance.

[0081] The work type of the project is related to the overhaul type. The work type is defined as follows:

[0082] Work type A: only suitable for A-type overhaul, B and C-type overhaul will affect the standard construction period;

[0083] Work type B: only suitable for B-type overhaul, and will affect the standard construction period if it is not used for A or C-type overhaul;

[0084] Work type C: only suitable for C-type overhaul, and will affect the standard construction period if it is not used for A or B-type overhaul;

[0085] Work type AB: only suitable for A and B type overhauls. It will affect the standard construction period if it is put on C type overhaul.

[0086] Work type BC: only suitable for B and C type overhauls. It will affect the standard construction period if it is not used for A type overhauls.

[0087] Work type AC: only suitable for A and C type overhauls. It will affect the standard construction period if it is put on B type overhaul.

[0088] Work type ABC: Suitable for A, B, and C type overhauls, and will not affect the standard construction period.

[0089] Step 2.4: Determine the project work type as follows:

[0090] (1) Within the same implementation window, there is no logical relationship between the execution of a project and other projects.

[0091] If the implementation window of the project is M and the implementation period is T, the milestone window M of this type of unit is T in the standard period of Class A overhaul. A , the standard duration of a Class B overhaul is T B , the standard duration of a C-type overhaul is T C , determine the project work type according to the following method:

[0092] If T≤T C , and T≤T B , T≤T A , then the work type of the project is ABC;

[0093] If T>T C , and T≤T B , T≤T A , then the work type of the project is AB;

[0094] If T>T C , and T>T A , T≤T B , then the work type of the project is B;

[0095] If T>T C , and T>T B , T≤T A , then the work type of the project is A;

[0096] If T>T A , and T≤T C , T≤T B , then the work type of the project is BC;

[0097] If T>T A , and T>T B , T≤TC , then the work type of the project is C;

[0098] If T>T B , and T≤T C , T≤T A , then the work type of the project is AC.

[0099] (2) If the implementation windows of the two projects are consistent and have a logical relationship, the implementation periods of the two projects are combined and then compared with the period in the standard milestone. Because such projects will not arrange two long-term projects in the same overhaul, it is only necessary to combine and compare the implementation periods of the long-term project with the project that is executed in every overhaul, and then determine the work type of the long-term project.

[0100] (3) For some special projects, which can only be carried out in Category A or Category B overhaul according to regulations, the work type is directly determined to be A or B without considering the above-mentioned construction period comparison step.

[0101] For example, the standard milestone of the M310 unit C-type overhaul (25-day duration) is as follows:

[0102]

[0103]

[0104] Example 1: The window for comprehensive inspection of low-pressure injection pump 3RIS001PO is M30-M80, and the implementation period is 10 days, which is 13.42 days less than the "M30-M80" in the C-type standard milestone. Therefore, it can be judged that this project will not affect the C-type overhaul period. Using the same method, it is compared with the standard milestones of A and B-type overhauls, and it is judged that it does not affect the A and B-type overhaul periods. Then the work type of this project is ABC.

[0105] Example 2: The window of a work is M30-M80, and the implementation period is 15 days. This means that it exceeds the "M30-M80" in the Class C standard milestone by 13.42 days, is less than the "M30-M80" in the Class B standard milestone by 24.42 days, and is less than the "M30-M80" in the Class A standard milestone by 31.33 days. The work type of the project is AB.

[0106] If the implementation windows of the projects are consistent and have a logical relationship, the implementation durations of the two projects will be combined and then compared with the duration in the standard milestone. Such projects will not schedule two long-term projects in the same overhaul, so only the implementation duration of the long-term project and the project that is executed in each overhaul will be combined and compared.

[0107] Example 3: Diesel engine LHP ten-year overhaul, window M30-M80, implementation period 412 days. Diesel engine LHQ annual overhaul, window M30-M80, implementation period 2 days.

[0108] The two projects need to be carried out successively, with a combined duration of 14 days, which is longer than the 13.42 days of "M30-M80" in the C-type standard milestone, and shorter than the days of "M30-M80" in the B-type standard milestone and "M30-M80" in the A-type standard milestone. Therefore, the work type of the diesel engine LHP ten-year maintenance project is AB.

[0109] Example 4: For some special projects, regulations stipulate that they can only be carried out in Category A overhaul or Category B overhaul. In this case, the work type is directly determined to be A or B without considering the above-mentioned construction period comparison step.

[0110] Step 3: Prepare the first draft of key project planning.

[0111] Step 3 specifically includes:

[0112] Step 3.1: Automatically generate the pre-maintenance key project plan (i.e., automatic marking plan) according to the overhaul number and cycle in the database, and manually mark the plan with reference to the automatic marking plan to form a preliminary draft, including:

[0113] Step 3.1.1: Calculate the predicted overhaul number for each item in the key project planning table, and automatically mark and plan each overhaul item to be performed.

[0114] The algorithm for calculating the predicted overhaul number for each project is as follows:

[0115] According to the starting value A1 and cycle C of each item, the predicted overhaul number sequence {An} of each item is calculated.

[0116] Where: An=A1+(n-1)C;

[0117] {An}=(A1,A2,A3,……An), An<=the last overhaul number in the service life.

[0118] The mark (i.e. automatic mark) on the corresponding overhaul column of each project is generated completely according to the project start value and cycle according to the predicted overhaul number. Automatic marking can quickly generate planning marks, and the more important purpose is to update data in real time and adjust the plan in time according to the changes in the start value and cycle of the project in the database.

[0119] Step 3.1.2: Refer to the marking in step 3.1.1 and combine it with the actual planning situation to manually mark another location (see Figure 3, mark Y column for automatic marking, P column for manual marking). For key project plans that are not compiled for the first time, manually mark the first version as the plan mark released in the previous version.

[0120] For most projects, automatic marking and manual marking are consistent; when the project start value or cycle is changed, or the manual marking is manually adjusted, there will be inconsistencies. Among them, the inconsistency after manual adjustment is allowed, because the planning of key projects is not completely carried out according to the cycle. The final plan is published with manual marking.

[0121] Step 3.2: Compare the database read plan (automatic marking) and the manually marked plan to see if they are consistent, and automatically prompt where the arrangements are inconsistent.

[0122] The judgment method is: Figure 3 As shown, the automatic marking and manual marking of items are two adjacent rows. Check whether there is an automatic mark above the marked column in the manual marking row. If not, the blank column will be automatically marked as a reminder.

[0123] When the period and start value in the database change, the automatic mark will change accordingly, but the manual mark will not change, thus triggering the reminder mark, which can promptly prompt the data to change and prompt whether to modify the project plan.

[0124] When a reminder mark appears, confirm that the manual mark does not need to be modified, acknowledge the inconsistency (because key project planning is not carried out completely according to the cycle, other factors need to be considered), fill in the remarks at the reminder mark, and eliminate the reminder. This can prevent checking after each reminder appears and improve efficiency.

[0125] Step 3.3: Plan major technical improvements and major defect projects.

[0126] Since major technical transformation and major defect projects are non-preventive database projects and cannot be read automatically, they need to be manually added to the overhaul key project planning table and do not need to be automatically marked. They need to be manually marked according to the major technical transformation project plan and major defect project implementation plan.

[0127] The present invention automatically reads the work content, overhaul number and cycle of the overhaul key project in the preventive database, and automatically forms a preliminary draft of the whole life cycle overhaul key project planning.

[0128] Step 4: Automatically compare the project overhaul type and work type, and automatically remind of mismatched projects.

[0129] Each overhaul has an overhaul type A\B\C. Compare the work type and overhaul type of the project. If there is a mismatch, mark the work type of the project with a different color background. For example, the full pressure drop test of the spraying, work type A, is scheduled for a 314C overhaul, so an automatic reminder is given.

[0130] Step 5: Analyze the unmatched items and modify the plan to match the overhaul type, for example, by manual analysis.

[0131] Step 6: After checking the first draft, publish it and form a publishing page to show it to users. The published version only shows manually marked lines. The latest published version is displayed, and the archived historical published versions can be viewed at any time. The published version is not allowed to be modified. If you need to modify it, copy the published version to generate a new version for editing.

[0132] The present invention adopts a display method for the planning of key projects of the whole life cycle overhaul; adopts a project work type classification and marking method, and classifies the projects according to the principle that the type of overhaul in which the project is placed will not affect the overhaul period or has the least impact on the overhaul period. After classification, the projects that do not match the work type and overhaul type can be automatically found; when the start value and cycle of the key project in the database change, a reminder is given in the planning table. The present invention realizes the determination of the implementation period of the key project and the rapid determination of the last execution time of the key project.

[0133] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for planning key nuclear power overhaul projects, characterized in that: include: Step 1: Read the list of key items in the preventive database and upload the items in the non-preventive database; Step 2: Determine the type of work for the project; Step 3: Prepare the first draft of key project planning; Step 4: Compare the project overhaul type and work type, and remind the mismatched projects; Step 5: Analyze the unmatched items and modify the plan to match the overhaul type; Step 6: After modification, the final draft of the key project plan is formed, and after verification, it is released and displayed to users.

2. The method for planning key nuclear power overhaul projects according to claim 1, characterized in that: In step 1, for the PM items that have been marked in the overhaul key item field in the preventive database, the PMID-PMRQ, equipment code, work content, start value, cycle, and last execution time field information are read into the corresponding fields of the overhaul key item planning table.

3. The method for planning key nuclear power overhaul projects according to claim 1, characterized in that: In step 1, upload relevant information of two types of non-preventive database projects, major technical transformation and major defect projects, into the overhaul key project planning table.

4. The method for planning key nuclear power overhaul projects according to claim 1, characterized in that: Prior to step 1, a list of key projects is selected, which includes: (a) Three major tests for a ten-year overhaul; (b) Major equipment items and tests for the primary circuit such as pressure vessels and evaporators; (c) Power supply projects; (d) Projects involving network lines; (e) Projects with heavy loads under high voltage switchboards; (f) Items of generator and steam turbine bodies.

5. The method for planning key nuclear power overhaul projects according to claim 1, characterized in that: Step 2 specifically includes: Step 2.1: Determine the implementation period of the project; Step 2.2: Determine the implementation window; Step 2.3: Compare the project's windows and durations with those of the standard milestones; Step 2.4: Determine the type of project work.

6. The method for planning key nuclear power overhaul projects according to claim 5, characterized in that: In step 2.4, if the implementation window of the project is M and the implementation period is T, the standard period for the type of unit milestone window M in the A-type overhaul is T A , the standard duration of a Class B overhaul is T B , the standard duration of a C-type overhaul is T C , determine the project work type according to the following method: If T≤T C , and T≤T B , T≤T A , then the work type of the project is ABC; If T>T C , and T≤T B , T≤T A , then the work type of the project is AB; If T>T C , and T>T A , T≤T B , then the work type of the project is B; If T>T C , and T>T B , T≤T A , then the work type of the project is A; If T>T A , and T≤T C , T≤T B , then the work type of the project is BC; If T>T A , and T>T B , T≤T C , then the work type of the project is C; If T>T B , and T≤T C , T≤T A , then the work type of the project is AC.

7. The method for planning key nuclear power overhaul projects according to claim 5, characterized in that: In step 2.4, if the implementation windows of the two projects are consistent and have a logical relationship of sequence, the implementation durations of the two projects are merged and then compared with the duration in the standard milestone.

8. The method for planning key nuclear power overhaul projects according to claim 1, characterized in that: Step 3 specifically includes: Step 3.1: Automatically generate the pre-maintenance key project plan according to the overhaul number and cycle in the database, and refer to the automatic marking plan to manually mark the plan to form a preliminary draft; Step 3.2: Compare the automatic marking plan and the manual marking plan to see if they are consistent, and automatically prompt where the plans are inconsistent; Step 3.3: Plan major technical improvements and major defect projects.

9. The method for planning key nuclear power overhaul projects according to claim 8, characterized in that: Step 3.1 specifically includes: Step 3.1.1: Calculate the predicted overhaul number for each item in the key project planning table, and automatically mark and plan each overhaul item to be performed; Step 3.1.2: Refer to the marking in step 3.1.1 and combine it with the actual planning situation to manually mark another location.

10. The method for planning key nuclear power overhaul projects according to claim 1, characterized in that: In step 4, the work type and overhaul type of the project are compared, and if there is a mismatch, it is marked at the work type of the project.

Images