CN114493065A - Preventive maintenance work order batch triggering method based on grouping mode - Google Patents
Preventive maintenance work order batch triggering method based on grouping mode Download PDFInfo
- Publication number
- CN114493065A CN114493065A CN202011253359.1A CN202011253359A CN114493065A CN 114493065 A CN114493065 A CN 114493065A CN 202011253359 A CN202011253359 A CN 202011253359A CN 114493065 A CN114493065 A CN 114493065A
- Authority
- CN
- China
- Prior art keywords
- pmaq
- event
- plan
- work order
- work
- 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.)
- Pending
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 26
- 238000000034 method Methods 0.000 title claims abstract description 23
- 230000003449 preventive effect Effects 0.000 title claims abstract description 21
- 238000012545 processing Methods 0.000 claims abstract description 56
- 238000006467 substitution reaction Methods 0.000 claims abstract description 42
- 238000004364 calculation method Methods 0.000 claims description 9
- 238000004064 recycling Methods 0.000 claims description 5
- 238000012163 sequencing technique Methods 0.000 claims description 3
- 238000010200 validation analysis Methods 0.000 claims 1
- 230000001960 triggered effect Effects 0.000 description 7
- 238000007726 management method Methods 0.000 description 6
- 238000010923 batch production Methods 0.000 description 3
- 230000000737 periodic effect Effects 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 2
- 208000028952 Chronic enteropathy associated with SLCO2A1 gene Diseases 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000000525 cavity enhanced absorption spectroscopy Methods 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000003825 pressing 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
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06316—Sequencing of tasks or work
-
- 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/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- 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/20—Administration of product repair or maintenance
-
- 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
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- General Health & Medical Sciences (AREA)
- Water Supply & Treatment (AREA)
- Data Mining & Analysis (AREA)
- Public Health (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the technical field of nuclear power plant equipment management, and particularly discloses a preventive maintenance work order batch triggering method based on a grouping mode. The method comprises the following steps: searching all PMAQ meeting the effective state of the condition according to the input parameters; judging whether any PMAQ in the PMAQ data table has a substitution relation, and locking the PMAQ and the associated work order; generating a PM work plan for the locked PMAQ; carrying out state identification on PM events in the PM work plan; comparing the PM working plan with an expected page event; generating a state identifier according to the PM working plan to process an event; and releasing the locked PMAQ and the associated work order pair, setting the locked PMAQ and the associated work order pair to be in a processed state, and processing the next PMAQ or the next group of PMAQs in the PMAQ data table. The method can realize batch triggering of PM projects, reduce the influence on the whole system, improve the batch processing efficiency and avoid batch processing execution failure caused by the problem of one PM project.
Description
Technical Field
The invention belongs to the technical field of nuclear power plant equipment management, and particularly relates to a preventive maintenance work order batch triggering method based on a grouping mode.
Background
Preventive Maintenance (PM for short): the method is used for preventing and relieving performance degradation or faults aiming at SSCs (systems, equipment, parts and structures), or monitoring, checking and tracking the performance and the state of the equipment so as to maintain or prolong the service life of the equipment. Preventive maintenance is subdivided into periodic maintenance, predictive maintenance and strategic maintenance. Periodic Maintenance (Periodic Maintenance): are preventive maintenance performed at predetermined calendar time intervals, or predetermined equipment run times, or overhaul period intervals of the power station. The preventive maintenance database management module of the power plant production management system has the functions of completing management of preventive maintenance projects and triggering of preventive maintenance work orders (PM work orders for short).
The PM work order triggering is a core function of a preventive database management module, the triggering logic is complex, and the internal correlation is tight. At present, several production management systems used by domestic nuclear power plants, such as an N1-EAM system and an IFS system (CEAS, CMS and TEAM), have some problems on the PM triggering function and are not comprehensive enough. For example, after the IFS system triggers the work order, the start value of the PM item cannot be reflected in the work order that has not been triggered to execute. The N1-EAM is that when the current overhaul work order of the PM project is not closed, future overhaul work orders cannot be triggered by normal means, the requirement that a plurality of overhaul work orders need to be triggered in advance by a domestic nuclear power plant cannot be met, a plurality of unconventional means often need to be adopted, and the follow-up modification of the PM project is influenced.
Existing system PM work orders trigger batch processes to use pessimistic locks, which lock all PM items when the batch process begins execution, and do not unlock until the batch process ends. If the number of items triggered in one batch is large, for example, a work order of one overhaul is triggered, the system is locked for a long time, and the generation of other work orders is influenced.
Disclosure of Invention
The invention aims to provide a grouping mode-based preventive maintenance work order batch triggering method, which solves the problem of influence on the whole system when PM projects are triggered in batches, improves the batch processing efficiency and avoids batch processing execution failure caused by the problem of one PM project.
The technical scheme of the invention is as follows: a preventive maintenance work order batch triggering method based on a grouping mode comprises the following steps:
s1, searching all PMAQs in the effective state meeting the conditions according to the input parameters, and forming a PMAQ data table;
s2, judging whether any PMAQ in the PMAQ data table has a substitution relation, and locking the PMAQ and the associated work order;
s3, generating a PM working plan for the locked PMAQ;
s4, carrying out state identification on the PM event in the PM work plan;
for PMAQ without substitution relation, directly marking the generation state of each PM event of the PM work plan as S, and indicating that PMWO needs to be created on an expected page;
sequencing the PMAQ substitution logic processing for a group of PMAQs with substitution relation, recycling each substitution logic of the processing related item, and identifying the generation state of the PM event;
s5, comparing the PM working plan with an expected page event;
s6, generating a state identifier according to the PM working plan to perform event processing;
and S7, unlocking the locked PMAQ and the associated work order pair, setting the locked PMAQ and the associated work order pair to be in a processed state, and processing the next PMAQ or the next group of PMAQs in the PMAQ data table.
The PM working plan generated by the locked PMAQ specifically comprises the following steps: processing the locked daily PMAQ project data to form a corresponding PM working plan; the frequency of daily items is year, month, week and day, according to the frequency Freq, the grace period, the deadline DD of PMAQ and the work order generation time range of PMAQ, and in the range of (the current time, the current time + the work order generation time range), a PM work plan is generated from the deadline DD of PMAQ, and each PM event of the PM work plan has an deadline DD, an earliest completion date EF and a latest completion date LF.
When the locked daily PMAQ project data is processed, when the PMAQ does not have a generated future event work order, a PM work plan is generated on the basis of the cutoff date DD and the frequency Freq of the PMAQ;
when the PMAQ has a generated future event work order, generating a PM work plan according to the calculation type of the PMAQ;
for PMAQ with the calculation type C, generating a work plan based on the expiration date DD of PMAQ, the expiration date DD1 of the future event work order and the frequency Freq; for PMAQ with calculation type D, the work plan is generated based on only the cutoff date DD and the frequency Freq of PMAQ, without considering the cutoff date of the PMAQ future event work order.
Generating the PM work plan for the locked PMAQ in S3 further includes processing the locked overhaul PMAQ project data to form a corresponding PM work plan;
processing the locked overhaul PMAQ project data under an automatic trigger mode to form a corresponding PM working plan;
according to the frequency Freq of the PMAQ, the overhaul number of the PMAQ and the work order generation time range, when the frequency Freq is within the range of (the current time, the current time + the work order generation time range), a PM work plan is generated from the deadline of the PMAQ;
in a manual trigger mode, calculating from the locked PMAQ overhaul number until the overhaul number of the PM event in the PM working plan is equal to the input overhaul number to form a corresponding PM working plan;
in S4, for a group of PMAQ having an alternative relationship, sorting the processing of the PMAQ alternative logics, and recycling each alternative logic of the associated item, the identifying the generation state of the PM event specifically includes:
s4.1, aiming at a group of PMAQs with substitution relation, sorting the PMAQ substitution logic processing;
when the PMAQ substitution logic is sorted, sorting the PMAQ substitution logic from high to low according to substitution levels, and sorting the PMAQ substitution logic from low to high according to the PMAQ frequency when the levels are the same;
s4.2, circularly processing each alternative logic for substituting the associated item, and identifying the generation state of the event;
the step of circularly processing each alternative logic for replacing the associated item in the step S4.2, and identifying the generation state of the event specifically includes performing alternative logic processing and identification on the multi-layer alternative relationship of the daily PMAQ item:
according to each event sequenced by the PMAQ replacement logic, searching events of EF-LF (delay/delay) containing the planned event deadline (DD) of the replacement PMAQ project in the replaced PMAQ project, if the generation status flags of the two found associated events are not equal to R, executing S4.2.1.2 and S4.2.1.3 steps, otherwise skipping the two steps to continue processing the next event of the replacement PMAQ project until the replacement logic of each event of the replacement project and the replaced project is processed completely;
setting the generation status identification of the replaced event to R;
compressing EF \ LF of the substitution event;
compressing EF \ LF of the replacing event according to a principle of approaching the DD of the replacing event, wherein EF takes the larger value of the replacing event and the EF of the replaced event, and LF takes the smaller value of the replacing event and the LF of the replaced event;
the generation status of all events whose generation status is identified as empty is set to S.
The step 4.2 of circularly processing each alternative logic for replacing the associated item, and identifying the generation state of the event specifically includes performing alternative logic processing and identification on the multi-layer alternative relation of the overhaul PMAQ item:
finding an event with a revision number equal to the revision number of the substitute PMAQ item in the substitute PMAQ item according to each event sequenced by the PMAQ substitute logic, if the generation state flag of the found associated event is not equal to R, continuing to operate in step S4.2.2.2, otherwise skipping step S4.2.2.2 to continue processing the next event of the substitute PMAQ until the substitute logic of each event of the substitute item and the substituted item is processed completely;
setting the generation status identification of the replaced event to R;
the generation status of all events whose generation status is identified as empty is set to S.
In the S5, the comparing the PM work plan with the expected page event includes:
s5.1, comparing the PM work plan of the daily project with an expected page event;
circulating each PM event in the PM working plan, and finding out an event containing the PM event DD in EF-LF in an expected page;
s5.1.1, if the generation state of the PM event in the PM working plan is equal to S or R, modifying EF \ LF of the PM event;
s5.1.1.1, if the lock date field value of the expected page event is equal to N, then EF of the PM work plan takes the larger value corresponding to the two events, LF takes the smaller value corresponding to the two events;
s5.1.1.2, if the locking date field value of the expected page event is equal to Y, the EF \ LF of the PM work plan is equal to the EF \ LF of the corresponding event in the expected page;
s5.1.2, if the generation state of the PM event in the PM work plan is equal to S and the expected page event has a work order, modifying the generation state identification from S to E;
s5.1.3, if the generation state of the PM event in the PM work plan is equal to S and the expected page event has no work order, the generation state identifier remains unchanged and is still S;
s5.1.4, there is an event in the PM work plan, but there is no corresponding event in the expected page, the mark is still S;
s5.2, comparing the PM work plan of the overhaul project with an expected page event;
circulating each PM event in the PM working plan, and finding an event with a overhaul number equal to the overhaul number of the PM event in an expected page;
s5.2.1, modifying the generation state identifier from S to E when the generation state of the PM event in the PM working plan is equal to S and the expected page event has a work order;
s5.2.2, if the generation state of the PM work plan event is equal to S and the expected page event has no work order, the generation state identification is still S;
s5.2.3, there is an event in the PM work plan, but there is no corresponding event in the expected page, the identification is still S.
In S6, generating a state identifier according to the PM work plan to perform event processing, which specifically includes:
s6.1, when the PM work plan state identification bit is S, generating a new work order
S6.1.1, sorting PM work plan events according to DD positive sequence;
s6.1.2, copying and generating a new work order from the template work order associated with PMAQ for all events with the generation state identification of S of the PM work plan, and updating the work order number to the event corresponding to the PM work plan
S6.1.3, copying the EF \ DD \ LF \ overhaul number of the PM work plan event to the corresponding field of the new work order of the event;
s6.1.4, identifying all the generation states of the PM work plan as rows of S, and inserting the events containing the worksheet number and the EF \ DD \ LF \ overhaul number into an expected page according to the DD positive sequence mode;
s6.2, writing EF/DD/LF of the PM work plan event to a corresponding field of the corresponding generated work order when the PM work plan state identification bit is E;
and S6.3, when the PM work plan state identification bit is R, no processing is performed.
In S1, according to the input parameters, all the PMAQ in the valid state that meets the condition are searched, and a PMAQ data table is formed, which specifically includes:
s1.1, inputting parameters, automatically and periodically searching all PMAQ items which meet the conditions and are in an effective state in a preventive maintenance database through automatic triggering, and obtaining a PMAQ data table;
inputting parameters, and automatically and periodically searching all PMAQ items in the preventive maintenance database which meet the effective state of the conditions for automatic triggering, wherein the searching conditions are as follows: the deadline (DD) of the PMAQ is less than or equal to the current date plus the work order generation time range; summarizing the searched PMAQ items to form a PMAQ data table;
s1.2, searching all PMAQ items in an effective state meeting the conditions by inputting parameters required by triggering to obtain a PMAQ data table;
and manually triggering in batches by inputting parameters required by triggering, searching all PMAQ items in an effective state meeting the conditions, and summarizing the searched PMAQ items to form a PMAQ data table.
The invention has the following remarkable effects: the method for triggering the batch of the preventative maintenance work orders based on the grouping mode can realize the batch triggering of PM projects, simultaneously reduce the influence on the whole system, improve the batch processing efficiency and avoid the failure of batch processing execution caused by the problem of one PM project; the problem of the overdue of the replaced project caused by unreasonable planning arrangement is avoided. The function that one unit can trigger a plurality of overhaul (different overhaul) projects is realized, and the requirement that the overhaul project needs to be triggered by several rounds in advance for purchasing overhaul spare parts of a power plant is met.
Detailed Description
The terms referred to in the present invention include: the terms PMAQ, PMWP, PM event, grace period, PMWO, substitution relationship (PMAQ a instead of PMAQ B), and work order generation timeframe, etc., are specifically explained as follows:
(1) PMAQ: a PM item;
(2) PMWP: a PM work plan;
(3) PM event: entries in the PMWP with an outline expiration date (DD), an earliest completion date (EF), and a latest completion date (LF) on the PM event;
(4) a grace period, which is the period of completing EF and LF of a PM event; usually 25% of the frequency of PM, and 25% of the frequency of PM before and after PM;
(5) PMWO: a PM work order, one PM event may be associated with 0 or 1 PMWO, and one PMWO may be associated with only one PM event.
(6) Alternative relationship (PMAQ a instead of PMAQ B):
after PMAQ a produced a work order, some work order B of the substituted PMAQ B was pressed and thus not produced. The relation between the work order b which is not generated by pressing and the substitute work order a is as follows: EF to LF of b include DD of a. Also known as generating replacement logic.
(7) The work order generation time range is as follows: the time range used when the PMAQ project automatically triggers the work order is day, and the work order generation time range corresponding to each PMAQ may be different and generally relates to the frequency.
(8) The generation status flag bit in the PM work plan (PMWP) includes S, R, E, which has the following specific meaning: s, creating a PMWO on an expected page; r is replaced, and PMWO does not need to be generated; e is that PMWO already exists in the expected page and the expiration date (DD) of the work order is consistent with the calculated expiration date (DD) of the PMWP;
a preventive maintenance work order batch triggering method based on a grouping mode specifically comprises the following steps:
s1, searching all PMAQs in the effective state meeting the conditions according to the input parameters, and forming a PMAQ data table;
s1.1, inputting parameters, automatically and periodically searching all PMAQ items which meet the conditions and are in an effective state in a preventive maintenance database through automatic triggering, and obtaining a PMAQ data table;
inputting parameters, and automatically and periodically searching all PMAQ items in the preventive maintenance database which meet the effective state of the conditions for automatic triggering, wherein the searching conditions are as follows: the deadline (DD) of the PMAQ is less than or equal to the current date plus the work order generation time range; summarizing the searched PMAQ items to form a PMAQ data table, wherein the PMAQ meeting the conditions can be a daily item or an overhaul item;
s1.2, searching all PMAQ items in an effective state meeting the conditions by inputting parameters required by triggering to obtain a PMAQ data table;
manual batch triggering is realized by inputting parameters required by triggering, all PMAQ items in an effective state meeting the conditions are searched, and the searched PMAQ items are summarized to form a PMAQ data table;
s2, judging whether any PMAQ in the PMAQ data table has a substitution relation, and locking the PMAQ and the associated work order;
s2.1, selecting any PMAQ in a PMAQ data table, and judging whether the PMAQ has a substitution relation;
judging whether the selected PMAQ items have an alternative relation, if so, finding out all PMAQ items having direct and indirect alternative relations with the PMAQ in a PMAQ data table, and taking the PMAQ items as a group of PMAQ items;
s2.2, locking a group of PMAQs with an alternative relation or locking the PMAQs without the alternative relation, and simultaneously locking the group of PMAQs or triggering the PMAQs to a work order PMWO;
s3, generating a PM working plan for the locked PMAQ;
s3.1, processing the locked daily PMAQ project data to form a corresponding PM working plan;
the frequency of daily items is year, month, week and day, and according to the frequency (Freq) of PMAQ, grace period, deadline (DD) of PMAQ and work order generation time range, in the range of (current time, current time + work order generation time range), a PM work plan is generated from the deadline (DD) of PMAQ, and each PM event of the PM work plan has a deadline (DD), an earliest completion date (EF) and a latest completion date (LF);
generating a PM work plan based on an expiration date (DD) and frequency (Freq) of the PMAQ when the PMAQ has no generated future event work order; the deadline of each PM event in the PM working plan is respectively as follows: DD, DD + Freq, DD +2 Freq, DD +3 Freq, … …, DD + n Freq; wherein (DD + n + Freq) is less than or equal to (current time + work order generation time range)
When the PMAQ has a generated future event work order, generating a PM work plan according to the calculation type of the PMAQ;
for PMAQ with the calculation type C, generating a work plan based on the deadline (DD) of PMAQ, the deadline (DD1) and the frequency (Freq) of a future event work order; the deadline of each PM event in the generated PM work plan is respectively as follows: DD, DD1, DD1+ Freq, DD1+2 + Freq, … …, DD1+ n + Freq; wherein (DD1+ n Freq) is less than or equal to (current time + work order generation time range);
for PMAQ with the calculation type D, the work plan is generated only on the basis of the expiration date (DD) and the frequency (Freq) of the PMAQ without considering the expiration date of the PMAQ future event work order; the deadline of each PM event in the generated PM work plan is respectively as follows: DD, DD + Freq, DD +2 Freq, DD +3 Freq, … …, DD + n Freq; wherein (DD + n Freq) is less than or equal to (current time + work order generation time range);
s3.2, processing the locked overhaul PMAQ project data to form a corresponding PM working plan;
s3.2.1, processing the locked overhaul PMAQ project data under the automatic trigger mode to form a corresponding PM working plan;
according to the frequency (Freq) of the PMAQ, the overhaul number of the PMAQ and the work order generation time range, when the frequency (Freq) of the PMAQ is within the range of (the current time, the current time + the work order generation time range), a PM work plan is generated from the deadline date of the PMAQ, and the deadline date of each PM event in the generated PM work plan is respectively as follows: DD, DD1, DD2, … …, DDn; wherein DD is the deadline of PMAQ, DD1 is the starting time corresponding to the next overhaul calculated according to the overhaul number and the frequency, DD2 is the starting time corresponding to the next overhaul number, and so on, the starting time corresponding to the last event overhaul number is less than or equal to (the current time + the work order generation time range);
s3.2.2, under the manual trigger mode, starting to calculate from the locked PMAQ overhaul number until the overhaul number of the PM event in the PM work plan is equal to the input overhaul number, and forming a corresponding PM work plan;
s4, carrying out state identification on the PM event in the PM work plan;
for PMAQ without substitution relation, directly marking the generation state of each PM event of the PM work plan as S, and indicating that PMWO needs to be created on an expected page;
sequencing the PMAQ substitution logic processing for a group of PMAQs with substitution relation, recycling each substitution logic of the processing related item, and identifying the generation state of the PM event;
s4.1, aiming at a group of PMAQs with substitution relation, sorting the PMAQ substitution logic processing;
when the PMAQ substitution logic is sorted, sorting the PMAQ substitution logic from high to low according to substitution levels, and sorting the PMAQ substitution logic from low to high according to the PMAQ frequency when the levels are the same;
s4.2, circularly processing each alternative logic of the alternative association items, and identifying the generation state of the event;
s4.2.1, carrying out substitution logic processing and identification on the multilayer substitution relation of the daily PMAQ project;
s4.2.1.1, according to each event sequenced by the PMAQ replacement logic, searching events of EF-LF containing the planned event deadline (DD) of the replacement PMAQ project in the replaced PMAQ project, if the generation status flags of the two found associated events are not equal to R, executing S4.2.1.2 and S4.2.1.3 steps, otherwise skipping the two steps to continue processing the next event of the replacement PMAQ project until the replacement logic of each event of the replacement project and the replaced project is processed completely;
s4.2.1.2, setting the generation status identification of the replaced event to R;
s4.2.1.3, compressing EF \ LF of the substitute event;
compressing EF \ LF of the replacing event according to a principle of approaching the DD of the replacing event, wherein EF takes the larger value of the replacing event and the EF of the replaced event, and LF takes the smaller value of the replacing event and the LF of the replaced event;
s4.2.1.4, setting the generation state of the event of which all generation states are marked as empty as S;
s4.2.2, carrying out substitution logic processing and identification on the multi-layer substitution relation of the overhaul PMAQ project;
s4.2.2.1, finding out the event with the overhaul number equal to the overhaul number of the substitute PMAQ item in the substitute PMAQ item according to each event sequenced by the PMAQ substitute logic, if the generation state flag of the found associated event is not equal to R, continuing to operate in step S4.2.2.2, otherwise skipping step S4.2.2.2 to continue processing the next event of the substitute PMAQ until the substitute logic of each event of the substitute item and the substituted item is processed completely;
s4.2.2.2, setting the generation status identification of the replaced event to R;
s4.2.2.3, setting the generation state of the event with all the generation states marked as empty as S;
s5, comparing the PM working plan with an expected page event;
s5.1, comparing the PM work plan of the daily project with an expected page event;
circulating each PM event in the PM working plan, and finding out an event containing the PM event DD in EF-LF in an expected page;
s5.1.1, if the generation state of the PM event in the PM working plan is equal to S or R, modifying EF \ LF of the PM event;
s5.1.1.1, if the lock date field value of the expected page event is equal to N, then EF of the PM work plan takes the larger value corresponding to the two events, LF takes the smaller value corresponding to the two events;
s5.1.1.2, if the locking date field value of the expected page event is equal to Y, the EF \ LF of the PM work plan is equal to the EF \ LF of the corresponding event in the expected page;
s5.1.2, if the generation state of the PM event in the PM work plan is equal to S and the expected page event has a work order, modifying the generation state identification from S to E;
s5.1.3, if the generation state of the PM event in the PM work plan is equal to S and the expected page event has no work order, the generation state identifier remains unchanged and is still S;
s5.1.4, there is an event in the PM work plan, but there is no corresponding event in the expected page, the mark is still S;
s5.2, comparing the PM work plan of the overhaul project with an expected page event;
circulating each PM event in the PM working plan, and finding an event with a overhaul number equal to the overhaul number of the PM event in an expected page;
s5.2.1, modifying the generation state identifier from S to E when the generation state of the PM event in the PM working plan is equal to S and the expected page event has a work order;
s5.2.2, if the generation state of the PM work plan event is equal to S and the expected page event has no work order, the generation state mark is still S;
s5.2.3, there is an event in the PM work plan, but there is no corresponding event in the expected page, the mark is still S;
s6, generating state identification according to PM working plan and processing event
S6.1, when the PM work plan state identification bit is S, generating a new work order
S6.1.1, sorting PM work plan events according to DD positive sequence;
s6.1.2, copying and generating a new work order from the template work order associated with PMAQ for all events with the generation state identification of S of the PM work plan, and updating the work order number to the event corresponding to the PM work plan
S6.1.3, copying the EF \ DD \ LF \ overhaul number of the PM work plan event to the corresponding field of the new work order of the event;
s6.1.4, identifying all the generation states of the PM work plan as rows of S, and inserting the events containing the worksheet number and the EF \ DD \ LF \ overhaul number into an expected page according to the DD positive sequence mode;
s6.2, writing EF/DD/LF of the PM work plan event to a corresponding field of the corresponding generated work order when the PM work plan state identification bit is E;
s6.3, when the PM work plan state identification bit is R, no processing is performed;
and S7, releasing the locking of the locked PMAQ and the related work order, setting the locked PMAQ and the related work order to be in a processed state, and processing the next PMAQ or the next group of PMAQs in the PMAQ data table.
Claims (10)
1. A preventive maintenance work order batch triggering method based on a grouping mode is characterized by comprising the following steps:
s1, searching all PMAQs in the effective state meeting the conditions according to the input parameters, and forming a PMAQ data table;
s2, judging whether any PMAQ in the PMAQ data table has a substitution relation, and locking the PMAQ and the associated work order;
s3, generating a PM working plan for the locked PMAQ;
s4, carrying out state identification on the PM event in the PM work plan;
for PMAQ without substitution relation, directly marking the generation state of each PM event of the PM work plan as S, and indicating that PMWO needs to be created on an expected page;
sequencing the PMAQ substitution logic processing for a group of PMAQs with substitution relation, recycling each substitution logic of the processing related item, and identifying the generation state of the PM event;
s5, comparing the PM working plan with an expected page event;
s6, generating a state identifier according to the PM working plan to process an event;
and S7, releasing the locking of the locked PMAQ and the related work order, setting the locked PMAQ and the related work order to be in a processed state, and processing the next PMAQ or the next group of PMAQs in the PMAQ data table.
2. The method of claim 1, wherein the step of generating the PM work plan for the locked PMAQ specifically comprises: processing the locked daily PMAQ project data to form a corresponding PM working plan; the frequency of daily items is year, month, week and day, according to the frequency Freq, the grace period, the deadline DD of PMAQ and the work order generation time range of PMAQ, and in the range of (the current time, the current time + the work order generation time range), a PM work plan is generated from the deadline DD of PMAQ, and each PM event of the PM work plan has an deadline DD, an earliest completion date EF and a latest completion date LF.
3. The method as claimed in claim 2, wherein the PM work plan is generated based on the cutoff date DD and frequency Freq of the PMAQ when the PMAQ has no generated future event work order while the locked daily PMAQ project data is processed;
when the PMAQ has a generated future event work order, generating a PM work plan according to the calculation type of the PMAQ;
for PMAQ with the calculation type C, generating a work plan based on the expiration date DD of PMAQ, the expiration date DD1 of the future event work order and the frequency Freq; for a PMAQ of calculation type D, the work plan is generated based only on the cutoff date DD and the frequency Freq of the PMAQ, regardless of the cutoff date of the PMAQ future event work order.
4. The method of claim 1, wherein the step of generating the PM work plan for the locked PMAQ at S3 further comprises processing the locked overhaul PMAQ project data to form a corresponding PM work plan;
under an automatic trigger mode, processing the locked overhaul PMAQ project data to form a corresponding PM working plan;
according to the frequency Freq of the PMAQ, the overhaul number of the PMAQ and the work order generation time range, when the frequency Freq is within the range of (the current time, the current time + the work order generation time range), a PM work plan is generated from the deadline of the PMAQ;
and under the manual trigger mode, starting to calculate from the locked PMAQ overhaul number until the overhaul number of the PM event in the PM work plan is equal to the input overhaul number, and forming a corresponding PM work plan.
5. The method as claimed in claim 1, wherein the step of S4, for a group of PMAQ having an alternative relationship, sorting the PMAQ alternative logic processing, and recycling each alternative logic of the associated item to identify the generation status of the PM event, specifically comprises:
s4.1, aiming at a group of PMAQs with substitution relation, sorting the PMAQ substitution logic processing;
when the PMAQ substitution logic is sorted, sorting the PMAQ substitution logic from high to low according to substitution levels, and sorting the PMAQ substitution logic from low to high according to the PMAQ frequency when the levels are the same;
and S4.2, circularly processing each replacing logic for replacing the related item, and identifying the generation state of the event.
6. The method according to claim 5, wherein the step S4.2 of cyclically processing each alternative logic of the alternative associated item and identifying the generation status of the event specifically includes processing and identifying the alternative logic of the multi-layer alternative relationship of the daily PMAQ item:
according to each event sequenced by the PMAQ replacement logic, searching events of EF-LF (delay/delay) containing the planned event deadline (DD) of the replacement PMAQ project in the replaced PMAQ project, if the generation status flags of the two found associated events are not equal to R, executing S4.2.1.2 and S4.2.1.3 steps, otherwise skipping the two steps to continue processing the next event of the replacement PMAQ project until the replacement logic of each event of the replacement project and the replaced project is processed completely;
setting the generation status identification of the replaced event to R;
compressing EF \ LF of the substitution event;
compressing EF \ LF of the replacing event according to a principle of approaching the DD of the replacing event, wherein EF takes the larger value of the replacing event and the EF of the replaced event, and LF takes the smaller value of the replacing event and the LF of the replaced event;
the generation status of all events for which the generation status is identified as empty is set to S.
7. The method according to claim 5, wherein the step S4.2 of cyclically processing each alternative logic of the alternative associated item and identifying the generation state of the event specifically includes the steps of processing and identifying the alternative logic of the multi-layer alternative relation of the overhaul PMAQ item:
finding an event with a revision number equal to the revision number of the substitute PMAQ item in the substitute PMAQ item according to each event sequenced by the PMAQ substitute logic, if the generation state flag of the found associated event is not equal to R, continuing to operate in step S4.2.2.2, otherwise skipping step S4.2.2.2 to continue processing the next event of the substitute PMAQ until the substitute logic of each event of the substitute item and the substituted item is processed completely;
setting the generation status identification of the replaced event to R;
the generation status of all events whose generation status is identified as empty is set to S.
8. The method according to claim 1, wherein the comparing of the PM work plan with the expected page event in S5 includes:
s5.1, comparing the PM work plan of the daily project with an expected page event;
circulating each PM event in the PM working plan, and finding out an event containing the PM event DD in EF-LF in an expected page;
s5.1.1, if the generation state of the PM event in the PM working plan is equal to S or R, modifying EF \ LF of the PM event;
s5.1.1.1, if the lock date field value of the expected page event is equal to N, then EF of the PM work plan takes the larger value corresponding to the two events, LF takes the smaller value corresponding to the two events;
s5.1.1.2, if the locking date field value of the expected page event is equal to Y, the EF \ LF of the PM work plan is equal to the EF \ LF of the corresponding event in the expected page;
s5.1.2, if the generation state of the PM event in the PM work plan is equal to S and the expected page event has a work order, modifying the generation state identification from S to E;
s5.1.3, if the generation state of the PM event in the PM work plan is equal to S and the expected page event has no work order, the generation state identifier remains unchanged and is still S;
s5.1.4, there is an event in the PM work plan, but there is no corresponding event in the expected page, the mark is still S;
s5.2, comparing the PM work plan of the overhaul project with an expected page event;
circulating each PM event in the PM working plan, and finding an event with a overhaul number equal to the overhaul number of the PM event in an expected page;
s5.2.1, modifying the generation state identifier from S to E when the generation state of the PM event in the PM working plan is equal to S and the expected page event has a work order;
s5.2.2, if the generation state of the PM work plan event is equal to S and the expected page event has no work order, the generation state identification is still S;
s5.2.3, there is an event in the PM work plan, but there is no corresponding event in the expected page, the identification is still S.
9. The method according to claim 1, wherein the step S6 of generating the status flag according to the PM work plan for event processing specifically includes:
s6.1, when the PM work plan state identification bit is S, generating a new work order
S6.1.1, sorting PM work plan events according to DD positive sequence;
s6.1.2, copying and generating a new work order from the template work order associated with PMAQ for all events with the generation state identification of S of the PM work plan, and updating the work order number to the event corresponding to the PM work plan
S6.1.3, copying the EF \ DD \ LF \ overhaul number of the PM work plan event to the corresponding field of the new work order of the event;
s6.1.4, identifying all the generation states of the PM work plan as rows of S, and inserting the events containing the worksheet number and the EF \ DD \ LF \ overhaul number into an expected page according to the DD positive sequence mode;
s6.2, writing EF/DD/LF of the PM work plan event to a corresponding field of the corresponding generated work order when the PM work plan state identification bit is E;
and S6.3, when the PM work plan state identification bit is R, no processing is performed.
10. The method as claimed in claim 1, wherein in S1, the PMAQ of all qualified validation states is searched according to the input parameters, and a PMAQ data table is formed, specifically including:
s1.1, inputting parameters, automatically and periodically searching all PMAQ items which meet the conditions and are in an effective state in a preventive maintenance database through automatic triggering, and obtaining a PMAQ data table;
inputting parameters, and automatically and periodically searching all PMAQ items in the preventive maintenance database which meet the effective state of the conditions for automatic triggering, wherein the searching conditions are as follows: the deadline (DD) of the PMAQ is less than or equal to the current date plus the work order generation time range; summarizing the searched PMAQ items to form a PMAQ data table;
s1.2, searching all PMAQ items in an effective state meeting the conditions by inputting parameters required by triggering to obtain a PMAQ data table;
and manually triggering in batches by inputting parameters required by triggering, searching all PMAQ items in an effective state meeting the conditions, and summarizing the searched PMAQ items to form a PMAQ data table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011253359.1A CN114493065A (en) | 2020-11-11 | 2020-11-11 | Preventive maintenance work order batch triggering method based on grouping mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011253359.1A CN114493065A (en) | 2020-11-11 | 2020-11-11 | Preventive maintenance work order batch triggering method based on grouping mode |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114493065A true CN114493065A (en) | 2022-05-13 |
Family
ID=81489706
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011253359.1A Pending CN114493065A (en) | 2020-11-11 | 2020-11-11 | Preventive maintenance work order batch triggering method based on grouping mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114493065A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102024181A (en) * | 2009-09-10 | 2011-04-20 | 上海宝信软件股份有限公司 | Artificial intelligence maintenance system and method |
| US20120197661A1 (en) * | 2011-01-31 | 2012-08-02 | Yuekang HealthCare Management Consultants, Inc. | Managing system for health care plan and managing method for the same |
| US20130197958A1 (en) * | 2011-08-01 | 2013-08-01 | Telcordia Technologies, Inc. | Critical date management |
| CN108171346A (en) * | 2018-01-25 | 2018-06-15 | 中广核核电运营有限公司 | Processing method, device and the computer equipment of nuclear power plant's instrument control mantenance data |
| CN108491939A (en) * | 2018-03-28 | 2018-09-04 | 青岛河澄知识产权有限公司 | A kind of Transit Equipment Intelligent Maintenance management method |
| CN109064140A (en) * | 2018-08-17 | 2018-12-21 | 北京天安智慧信息技术有限公司 | Internet of things equipment operation management system |
| CN109858746A (en) * | 2018-12-26 | 2019-06-07 | 阳光电源股份有限公司 | A kind of fault ticket distributing method and fault ticket management system |
-
2020
- 2020-11-11 CN CN202011253359.1A patent/CN114493065A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102024181A (en) * | 2009-09-10 | 2011-04-20 | 上海宝信软件股份有限公司 | Artificial intelligence maintenance system and method |
| US20120197661A1 (en) * | 2011-01-31 | 2012-08-02 | Yuekang HealthCare Management Consultants, Inc. | Managing system for health care plan and managing method for the same |
| US20130197958A1 (en) * | 2011-08-01 | 2013-08-01 | Telcordia Technologies, Inc. | Critical date management |
| CN108171346A (en) * | 2018-01-25 | 2018-06-15 | 中广核核电运营有限公司 | Processing method, device and the computer equipment of nuclear power plant's instrument control mantenance data |
| CN108491939A (en) * | 2018-03-28 | 2018-09-04 | 青岛河澄知识产权有限公司 | A kind of Transit Equipment Intelligent Maintenance management method |
| CN109064140A (en) * | 2018-08-17 | 2018-12-21 | 北京天安智慧信息技术有限公司 | Internet of things equipment operation management system |
| CN109858746A (en) * | 2018-12-26 | 2019-06-07 | 阳光电源股份有限公司 | A kind of fault ticket distributing method and fault ticket management system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102654907A (en) | Method and system for tracking quality of products in flow industry | |
| CN107918799B (en) | Ship comprehensive guarantee management system based on BS framework | |
| Kou et al. | Optimal inspection policy for a three-stage system considering the production wait time | |
| CN113867299A (en) | IPPS problem solving method under uncertain disturbance based on digital twin | |
| CN103198364A (en) | Nuclear power station main transformer service life management strategy optimization method based on genetic algorithm | |
| US20140163926A1 (en) | Automated root cause analysis | |
| Samhouri | An intelligent opportunistic maintenance (OM) system: a genetic algorithm approach | |
| EP2697753A1 (en) | Adjustment of an industrial installation | |
| CN105404940B (en) | Maintenance resource prediction method for ship use stage | |
| CN114493065A (en) | Preventive maintenance work order batch triggering method based on grouping mode | |
| CN117217672A (en) | Account checking method and system and production management system | |
| Alsyouf et al. | A multi-objective optimization of maintenance policies using weighted comprehensive criterion method (WCCM) | |
| Yu et al. | A new two-stage stochastic model for reverse logistics network design under government subsidy and low-carbon emission requirement | |
| CN102509187B (en) | Data mining based method for obtaining MRO (maintenance, repair and overhaul/operation) knowledge of large equipment | |
| CN111580462A (en) | Cutter consumption management system and method | |
| CN114662812B (en) | Automatic scheduling method for daily pre-maintenance project of nuclear power plant | |
| CN115293734A (en) | Real-time cost accounting method and system based on manufacturing process | |
| Nabhan | Effective implementation of reliability centered maintenance | |
| Li et al. | Considering machine health condition in jointly optimizing predictive maintenance policy and X-bar control chart | |
| CN118260555B (en) | Charging pile fault detection method and system | |
| Pan et al. | Optimization Method of Equipment Spare Parts Based on Monte Carlo Simulation | |
| Kim et al. | Designing a lifecycle integrated data network for remanufacturing using RFID technology | |
| Liao et al. | Mission reliability driven Risk-based maintenance approach of multi-state intelligent manufacturing system | |
| Jia et al. | Research of new equipment maintenance information management based on data mining | |
| CN113362197A (en) | New energy network access full-flow through identification and alarm method and device thereof |
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 |