Power failure maintenance system, method, equipment and medium

Abstract

The invention relates to the technical field of power system power failure maintenance, and discloses a power failure maintenance system, method and device and a medium, the system comprises an information acquisition module used for acquiring maintenance cycle information and defect state information of substation equipment, and further comprises a first determination module and a second determination module, the multi-source power-cut planning system comprises a first planning module and a second planning module which are respectively used for judging whether equipment is in a maintenance needing state or a defect state, the first planning module and the second planning module are used for generating plan prompt information when the corresponding state is triggered, and the plan generation module is used for automatically generating a structured first-edition power-cut plan by combining the equipment type, the defect level and the multi-source planning information. In addition, the system can support the function of automatically comparing and fusing different data sources such as project management, other plans and the like, and equipment with serious defects can be highlighted and displayed through a visual interface. And the intelligent level of power failure maintenance plan compilation is improved.

Description

Technical Field

[0001] This invention relates to the field of power system outage maintenance technology, and in particular to an outage maintenance system, method, equipment and medium. Background Technology

[0002] Currently, in the operation and maintenance of power systems, the execution of outage maintenance plans requires professional formulation. Only professionally formulated operation and maintenance plans can ensure the safe and stable operation of the power grid and improve the health level of equipment in the power system. Traditional outage maintenance plans are generally formulated based on information such as manually collected equipment ledgers, defect records, or project arrangements. Ultimately, this information is summarized and coordinated through tables or offline meetings.

[0003] However, this traditional method has many drawbacks. For example, in terms of information sources, this traditional method has a very low ability and efficiency in integrating data from different sources, and it is easy to make mistakes or omissions. Moreover, this manual power outage maintenance plan requires knowing in advance or within a precise time period whether the equipment maintenance cycle is due. This deficiency will cause the existing maintenance plan to be lagging behind or difficult to match with actual needs.

[0004] Moreover, traditional technology-designed plans lack standardized rules for data collection and prioritization, making it difficult to ensure that critical equipment is processed in a timely manner and also unable to be visualized.

[0005] Therefore, there is an urgent need for a system and method that can automatically aggregate multi-source maintenance needs and intelligently identify equipment status, while generating a structured initial version of the power outage plan. Summary of the Invention

[0006] Purpose of the invention: In view of the above-mentioned existing problems, the present invention discloses a power outage maintenance system, method, equipment and medium, which can solve the problems of low information integration capability and efficiency, easy error and omission in the formulation of power outage maintenance plans by traditional manual maintenance methods, as well as the problems of maintenance plans being lagging behind or not matching actual needs, lacking standard collection and priority ranking rules and unable to be visualized.

[0007] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0008] In a first aspect, the present invention provides a power outage maintenance system, the system comprising:

[0009] The information acquisition module is used to acquire first equipment information and second equipment information of the first substation; the first equipment information is used to characterize the maintenance cycle status of the equipment to be inspected in the first substation; the second equipment information is used to characterize the defect status of the target equipment in the first substation.

[0010] The first determining module is used to determine the first state of the equipment to be repaired based on the first equipment information.

[0011] The first state includes any one of the following: maintenance required state and maintenance not required state;

[0012] The first planning module is used to generate first planning information based on the maintenance-required state when the first state is in the maintenance-required state; the first planning information is used to prompt staff to include the equipment to be maintained in the initial power outage plan.

[0013] The second determining module is used to determine the second state of the target device based on the second device information;

[0014] The second state includes any one of the following: normal state and defective state;

[0015] The second planning module is used to generate second planning information based on the defective state when the second state is in the defective state; the second planning information is used to prompt staff to include the target equipment in the initial power outage plan;

[0016] The plan generation module is used to obtain the equipment type information of the target equipment, determine the defect level of the target equipment based on the equipment type information and the defect status, and generate the initial power outage plan based on the defect level, the first plan information and the second plan information to meet the maintenance needs of the equipment in the first substation.

[0017] As a preferred embodiment of the power outage maintenance system described in this invention, the first determining module is specifically used for:

[0018] Parse the first device information and extract the next maintenance date of the device to be repaired;

[0019] Determine whether the next maintenance date falls within the current calendar month;

[0020] If so, then set the first state to the state requiring maintenance;

[0021] If not, then set the first state to the maintenance-free state.

[0022] As a preferred embodiment of the power outage maintenance system described in this invention, the second determining module is specifically used for:

[0023] Parse the second device information to obtain the defect record and corresponding plan status identifier of the target device;

[0024] When the defect record exists and the plan status identifier is active, the second status is determined to be the defect status;

[0025] When the defect record does not exist or the plan status is inactive, the second status is determined to be the normal status.

[0026] As a preferred embodiment of the power outage maintenance system of the present invention, the plan generation module, when determining the defect level of the target equipment based on the equipment type information and the defect status, is specifically used for:

[0027] Based on a preset defect level mapping rule, the defect state is converted into an initial defect level;

[0028] Based on the equipment type information, query the equipment importance weight table to obtain the corresponding weight value;

[0029] The initial defect level is weighted and calculated with the weight value to obtain the final defect level; wherein, if the equipment type is a critical power transmission and transformation equipment, the final defect level is forcibly upgraded to the severe level.

[0030] As a preferred embodiment of the power outage maintenance system described in this invention, the plan generation module, when generating the initial power outage plan, is specifically used for:

[0031] All equipment in the first state that needs maintenance and all target equipment in the second state that is defective are grouped together according to their substation, voltage level and bay name.

[0032] The collected equipment list is prioritized and sorted according to the final defect level; the higher the defect level, the higher the ranking.

[0033] The sorted list of devices is output as the initial power outage plan.

[0034] As a preferred embodiment of the power outage maintenance system described in this invention, the information acquisition module is further configured to:

[0035] In response to scheduled task instructions, automatically query the project management database to obtain the equipment list associated with projects that intersect with the current month's time window;

[0036] The plan generation module is also used to merge the equipment in the equipment list into the initial power outage plan and mark its source as project management.

[0037] As a preferred embodiment of the power outage maintenance system of the present invention, the system further includes a data comparison module and a visualization display module;

[0038] The data comparison module is used to compare the imported external planning data with the data in the maintenance cycle database, defect management database, and project management database by field matching.

[0039] The device records that simultaneously meet multiple library conditions in the comparison results are filtered out and pushed to the plan generation module as supplementary input for generating the initial power outage plan;

[0040] The visualization module is used to display the initial power outage plan in tabular form on the user interface;

[0041] Equipment items with a severe defect level are highlighted in red.

[0042] An export button is provided to export the initial power outage plan as an Excel file in response to user actions.

[0043] Secondly, the present invention provides a power outage maintenance method, comprising:

[0044] The information acquisition module obtains information about the first and second equipment of the first substation.

[0045] The first determination module and the second determination module respectively determine the first state of the equipment to be inspected and the second state of the target equipment.

[0046] When the first state is a maintenance-required state, the first planning module generates the first planning information; when the second state is a defective state, the second planning module generates the second planning information.

[0047] The initial power outage plan is generated by combining equipment type information, defect level, first plan information, and second plan information through the plan generation module.

[0048] Thirdly, the present invention provides an electronic device including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described above.

[0049] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described above.

[0050] Compared with existing technologies, the beneficial effects of this invention are that it proposes a power outage maintenance system. The system includes an information acquisition module for acquiring maintenance cycle information and defect status information of substation equipment; a first determination module and a second determination module for determining whether equipment is in a maintenance-required or defective state, respectively; a first planning module and a second planning module for generating planning prompts when the corresponding state is triggered; and a planning generation module for automatically generating a structured initial power outage plan by combining equipment type, defect level, and multi-source planning information. The system also supports automatic comparison and fusion with different data sources such as project management and other plans, and can highlight equipment with serious defects through a visual interface. This invention achieves automatic identification, intelligent aggregation, and priority ranking of power outage maintenance needs, thereby significantly improving the intelligence level of power outage maintenance plan preparation. Attached Figure Description

[0051] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0052] Figure 1 This is a schematic diagram of the system structure of a power outage maintenance system provided in one embodiment of the present invention.

[0053] Figure 2 This is an internal structural diagram of an electronic device in a power outage maintenance system according to an embodiment of the present invention. Detailed Implementation

[0054] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of the present invention.

[0055] Example 1, referring to Figure 1 This is the first embodiment of the present invention, which provides a power outage maintenance system, including:

[0056] Figure 1 A schematic diagram of a power outage maintenance system is shown. The system includes:

[0057] The information acquisition module is used to acquire first equipment information and second equipment information of the first substation; the first equipment information is used to characterize the maintenance cycle status of the equipment to be inspected in the first substation; the second equipment information is used to characterize the defect status of the target equipment in the first substation.

[0058] The first determining module is used to determine the first state of the equipment to be repaired based on the first equipment information.

[0059] The first state includes any of the following: maintenance required state and maintenance not required state;

[0060] The first plan module is used to generate first plan information based on the maintenance requirement when the first state is in the maintenance requirement state; the first plan information is used to prompt staff to include the equipment to be maintained in the initial power outage plan.

[0061] The second determining module is used to determine the second state of the target device based on the second device information;

[0062] The second state includes any of the following: normal state and defective state;

[0063] The second planning module is used to generate second planning information based on the defect status when the second state is in a defect state; the second planning information is used to prompt staff to include the target equipment in the initial power outage plan.

[0064] The plan generation module is used to obtain the equipment type information of the target equipment, determine the defect level of the target equipment based on the equipment type information and defect status, and generate an initial power outage plan based on the defect level, the first plan information and the second plan information to meet the maintenance needs of the equipment in the first substation.

[0065] In some embodiments, the first determining module is specifically used for:

[0066] S101, parse the information of the first equipment and extract the next maintenance date of the equipment to be inspected;

[0067] The prerequisite for formulating a power outage maintenance plan is accurately determining whether equipment is nearing its maintenance cycle. Only by clearly identifying which equipment's maintenance time falls within the current planning window can we ensure that maintenance tasks are not missed or delayed. Therefore, it is essential to accurately extract the next maintenance date for each piece of equipment to be maintained from the primary equipment information as a key basis for determining whether it should be included in the initial power outage plan.

[0068] Specifically, a structured parsing engine can be used to identify and extract fields from the primary equipment information. This information typically originates from an equipment ledger database or maintenance cycle management database and is stored in a structured data format, including fields such as equipment number, equipment name, last maintenance time, maintenance cycle days, and next maintenance date. The parsing process first verifies data integrity, confirming the existence and compliant format of the next maintenance date field. If the field is missing, the next maintenance date is dynamically calculated based on the last maintenance time and maintenance cycle days. Subsequently, this date is compared with the current calendar month for subsequent status determination.

[0069] Specifically, the system first reads all records of equipment awaiting maintenance from the equipment ledger of the first substation, such as phase A of the 110 kV main transformer, bay B of the 35 kV circuit breaker, and unit C of the 10 kV capacitor bank. Then, for each record, it locates the value of its "next maintenance date" field. For example, the next maintenance date for phase A of the main transformer is February 15, 2**5. Next, it determines whether the date falls within the current calendar month. The current time is February 2**5, so February 15, 2**5 belongs to the current calendar month. Finally, it extracts and caches all equipment that meets the conditions and their next maintenance dates for use by the first determination module.

[0070] The next maintenance date refers to the planned date set according to the preventive testing procedures for power equipment or the manufacturer's maintenance recommendations, which is the next time a power outage maintenance operation must be performed. This date is automatically calculated and generated by the system after the equipment is put into operation or after the last maintenance is completed, and is stored in the maintenance cycle management database.

[0071] In some embodiments, the steps for establishing a structured parsing engine can be as follows:

[0072] Step 1.1: Receive the raw data stream of the first device information, perform format verification and caching on the raw data stream, and initialize the structured parsing engine;

[0073] Step 1.2: Determine whether the original data stream conforms to the preset data structure template. If it does, proceed to step 1.3; otherwise, proceed to step 1.7.

[0074] Step 1.3: Identify and extract the equipment number field, and verify whether the equipment number exists in the main index of the equipment ledger of the first substation. If it exists, proceed to step 1.4; otherwise, proceed to step 1.7.

[0075] Step 1.4: Locate the position of the next maintenance date field in the data record, and determine whether the field is not empty and conforms to the date format specification. If it does, proceed to step 1.5; otherwise, proceed to step 1.6.

[0076] Step 1.5: Directly read the value of the next maintenance date field, combine the equipment number and the next maintenance date into a structured key-value pair, store it in the pending queue, and proceed to step 1.7;

[0077] Step 1.6: Query the last maintenance time field and the maintenance cycle day field based on the equipment number. If both fields are valid, calculate the next maintenance date based on these two fields. Combine the equipment number and the calculated next maintenance date into a structured key-value pair and store it in the pending queue. Proceed to step 1.7.

[0078] Step 1.7: Release the memory resources used in this parsing, shut down the structured parsing engine, and end the current parsing process.

[0079] Therefore, the structured parsing engine built through the above steps can ensure that the next maintenance date of each piece of equipment to be inspected is extracted stably and accurately from the first equipment information from multiple heterogeneous sources, avoiding information omissions due to missing fields or abnormal formats, and providing complete and reliable data support for subsequent status determination.

[0080] S102, Determine whether the next maintenance date falls within the current calendar month;

[0081] If so, set the first state to the maintenance required state;

[0082] If not, then set the first state to "no maintenance required".

[0083] During the preparation of power outage maintenance plans, it is essential to ensure that only equipment whose maintenance cycle falls within the current planning window is included in the initial power outage plan. This avoids prematurely scheduling equipment that is not yet due or omitting equipment that is about to be due. Therefore, it is necessary to determine the time allocation of the next maintenance date for each piece of equipment to be maintained, confirming whether it falls within the current calendar month. This is a crucial logical step in determining whether equipment enters a maintenance-required state.

[0084] Specifically, a precise comparison method based on calendar time intervals can be used to match the extracted next maintenance date with the natural month boundary corresponding to the current system time. This method first obtains the current system time and determines the first and last days of the current natural month as time windows; then, it performs an inclusion check on the next maintenance date of each device against this time window.

[0085] Specifically, first, the current time is obtained from the system clock as February 1, 2**5 years later. Therefore, the current calendar month is determined to be February, 2**5 years later, with the time window starting on February 1, 2**5 years later and ending on February 31, 2**5 years later. Then, for each device record in the queue to be processed, for example, the next maintenance date for phase A of the 110 kV main transformer is February 15, 2**5 years later; the next maintenance date for bay B of the 35 kV circuit breaker is January 5, 2**6 years later; and the next maintenance date for unit C of the 10 kV capacitor bank is... January 28, 2025; then, these dates are judged one by one. February 15, 2025 falls between February 1, 2025 and February 31, 2025, and is determined to belong to the current calendar month. January 5, 2026 and January 28, 2025 are not in this range and are determined not to belong to the current calendar month. Finally, all judgment results are marked as Boolean values ​​to drive the assignment logic of the first state. For example, the A phase of the main transformer is marked as the state that needs maintenance, and the other two devices are marked as the state that does not need maintenance.

[0086] The current calendar month refers to the complete calendar month from 00:00 on the first day of the month to 24:00 on the last day of the month, based on the Gregorian calendar month and year of the current system date; the time window refers to the start and end date interval used to define the effective time range for planning, and in this invention, it specifically refers to the first and last dates of the current calendar month.

[0087] In some embodiments, the second determining module is specifically used for:

[0088] S201, parse the information of the second device to obtain the defect record of the target device and the corresponding plan status identifier;

[0089] During the development of power outage maintenance plans, it is essential to accurately identify equipment with operational defects that requires scheduled power outages to ensure the safe and stable operation of the power grid. To this end, it is necessary to completely extract the defect records and corresponding planned status identifiers for each target device from the secondary equipment information database. This serves as the core basis for determining whether the equipment is in a defective state. Only when both the defect record exists and the planned status identifier is active can the equipment be confirmed for inclusion in the initial power outage plan.

[0090] Specifically, a structured defect information parsing process can be used to extract fields and verify the status of the second device information. This second device information comes from a defect management database and is typically stored in a structured form, containing fields such as device number, defect description, discovery time, defect level, and planned status identifier. The parsing process first verifies data integrity, then extracts the defect record content and planned status identifier value, and performs a logical consistency check.

[0091] Specifically, the system first reads all defect entries for target equipment from the defect management database of the first substation. For example, it checks the "planned status identifier" field for each defect entry. For instance, it checks the "planned status identifier" field for each defect entry. For example, the "planned status identifier" for phase A of the 110 kV main transformer is active, the "planned status identifier" for phase B of the circuit breaker is inactive, and the "planned status identifier" for phase C of the capacitor bank is not active because there are no defect records. Next, it checks whether the defect record exists and whether the planned status identifier is active. Phase A of the main transformer meets both conditions. Although there is a defect record in phase B of the circuit breaker, the planned status identifier is inactive. Phase C of the capacitor bank has no defect record. Finally, it combines the equipment that meets the conditions with its defect record and the active status identifier and outputs the results for use by the second determination module. For example, only phase A of the main transformer is confirmed to have valid defect information.

[0092] Among them, defect records refer to abnormal phenomena or fault information discovered and entered into the system during equipment operation or inspection, including defect type, location, severity and discovery time; plan status identifier refers to the status flag used to mark whether the defect has been formally included in the maintenance plan process, with values ​​of active or inactive. Active status indicates that the defect needs to be handled by power outage, while inactive status indicates that the defect has been repaired, temporarily suspended or does not require power outage.

[0093] S202, When a defect record exists and the plan status identifier is active, the second status is determined to be a defect status;

[0094] S203, when the defect record does not exist or the plan status is marked as inactive, the second status is determined to be normal.

[0095] In the process of developing power system outage maintenance plans, it is essential to accurately classify equipment operating status to distinguish which equipment requires outage maintenance due to unresolved defects and which is in a healthy operating state and requires no intervention. Misclassifying equipment without defects or already deferred as defective will lead to wasted resources; overlooking truly defective equipment may trigger operational risks. Therefore, it is crucial to rigorously determine the secondary status of target equipment based on the existence of defect records and the activation status of planned status indicators.

[0096] Specifically, a dual-condition logic judgment mechanism can be used to classify the status of each target device. This mechanism first confirms whether the defect record exists, and then verifies whether the corresponding plan status identifier is active. Both conditions must be met simultaneously to determine the defect status; otherwise, it is classified as normal.

[0097] Specifically, the process begins by retrieving the target equipment list and its corresponding defect records and planned status identifiers from the parsed second equipment information. For example, the 110 kV main transformer phase A has a defect record of abnormal winding temperature rise and its planned status identifier is active; the 35 kV circuit breaker bay B has a defect record of operating mechanism jamming but its planned status identifier is inactive; and the 10 kV capacitor bank C unit has no defect records. Then, logical judgments are performed on each piece of equipment sequentially. The main transformer phase A satisfies both the existence of a defect record and the active planned status identifier, thus its second status is determined to be defective. Although the circuit breaker bay B has a defect record, its planned status identifier is inactive, failing to meet both conditions, therefore its second status is determined to be normal. Since the capacitor bank C unit has no defect record, regardless of the planned status identifier value, its second status is directly determined to be normal. Finally, the second status results of all equipment are output in a structured manner, for example, the main transformer phase A is marked as defective, and the other two equipment are marked as normal, serving as the input basis for the second planning module.

[0098] Among them, the defect status refers to the operational defects that the target equipment currently has but has not yet been repaired and have been formally included in the power outage maintenance process, which need to be handled by arranging power outage operations; the normal status refers to the target equipment having no operational defects, or although there were defects in the past, they have been repaired, temporarily suspended, or clearly do not require power outage intervention, and are in a state of safe operation.

[0099] Building upon the above embodiments, there are also situations where the defect information status of the target equipment is complex. For example, although a piece of equipment may have historical defect records, its current planned status identifier may have been manually set to an inactive state by maintenance personnel, indicating that the defect has already been addressed through live handling or delayed handling. Another example is that some newly commissioned equipment has not yet generated any defect records. In such cases, judging the equipment status based on only a single condition can easily lead to misjudgment. Therefore, a dual-condition logical judgment mechanism must be introduced to ensure that only equipment that simultaneously satisfies the existence of a defect record and has its planned status identifier in an active state is classified as having a defect status.

[0100] Meanwhile, in order to accurately determine the second state of the target device, this solution implements a dual-condition logic judgment mechanism through the following steps.

[0101] Step 2.1: Read the defect record field and plan status identifier field of the target equipment one by one from the second equipment information;

[0102] Step 2.2: Determine if the defect record field is empty. If it is not empty, proceed to step 2.3; otherwise, proceed directly to step 2.5.

[0103] Step 2.3: Determine if the plan status identifier field is equal to the activation status. If yes, proceed to step 2.4; otherwise, proceed to step 2.5.

[0104] Step 2.4: Mark the second state of the current target device as a defective state, record the device number and defect details, and proceed to step 2.6;

[0105] Step 2.5: Mark the second state of the current target device as normal state. Regardless of whether its defect record exists or what the planned state identifier is, as long as the two activation conditions are not met at the same time, it is classified as normal state, and proceed to step 2.6.

[0106] Step 2.6: After determining the status of the current device, continue processing the next target device until all target devices have been traversed.

[0107] Therefore, this invention effectively avoids misjudgment of status due to isolated reliance on defect records or plan status identifiers through a dual-condition logic judgment mechanism, ensuring that the initial power outage plan only includes defective equipment that truly needs power outage processing, thereby improving the accuracy of plan preparation and execution efficiency.

[0108] In some embodiments, when determining the defect level of a target device based on device type information and defect status, the plan generation module is specifically used for:

[0109] S301, Based on the preset defect level mapping rules, the defect status is converted into the initial defect level;

[0110] During the generation of power outage maintenance plans, the impact of different types of equipment defects on power grid safety varies significantly. A uniform approach would fail to reflect risk priority. Therefore, it is essential to transform identified defective equipment into quantifiable initial defect levels based on the specific manifestations of their defects using standardized rules. This provides the foundational input for subsequent weighted calculations and priority ranking.

[0111] Specifically, a mapping table-driven conversion mechanism based on defect type and severity can be adopted. This mechanism predefines the correspondence between defect status and initial defect level according to power industry standards and operation and maintenance experience, ensuring that the conversion process is objective, consistent and traceable.

[0112] Specifically, the process begins by extracting defect type fields and defect description keywords from defect records. For example, the defect type for phase A of the 110 kV main transformer is "abnormal winding temperature rise," the defect type for bay B of the 35 kV circuit breaker is "operating mechanism jamming," and the defect type for unit C of the 10 kV capacitor bank is "slight oil leakage from the casing." Next, a matching process is performed based on preset defect level mapping rules. These rules explicitly state that "abnormal winding temperature rise" corresponds to a critical initial defect level, "operating mechanism jamming" corresponds to a moderate initial defect level, and "slight oil leakage from the casing" corresponds to a minor initial defect level. Then, the defect status of each device is converted to its corresponding initial defect level according to the rules. For example, phase A of the main transformer is converted to a critical level, bay B of the circuit breaker is converted to a moderate level, and unit C of the capacitor bank is converted to a minor level. Finally, a structured mapping list of all target devices and their initial defect levels is created for use by the subsequent weighted calculation module.

[0113] Among them, the preset defect level mapping rule refers to the rule table formulated by the power operation and maintenance management department and solidified in the system. The rule table divides various equipment defects into four initial defect levels: minor, general, major, and urgent, according to the degree of impact on the system operation safety. The initial defect level refers to the basic risk level determined only based on the nature of the defect itself before considering the importance weight of the equipment. It is used to generate the final defect level by combining it with the equipment type weight.

[0114] In some embodiments, a mapping table-driven conversion mechanism based on defect type and severity is used, and its execution flow is as follows:

[0115] Step 3.1: Receive the target device that has been determined to be in a defective state and its complete defect record, and cache it in the defect level conversion buffer;

[0116] Step 3.2: Extract the defect type field and defect description text from the defect record. If both fields are valid, proceed to step 3.3; otherwise, proceed to step 3.6.

[0117] Step 3.3: Query the preset defect level mapping table and match the current defect type with the entries in the mapping table. If an exact match is found, proceed to step 3.4; otherwise, proceed to step 3.5.

[0118] Step 3.4: Read the initial defect level value corresponding to the matching item, bind the target device number with the initial defect level, store it in the conversion result set, and proceed to step 3.6;

[0119] Step 3.5: Perform keyword scanning on the defect description text to identify whether it contains key feature words defined in the mapping table. If at least one valid keyword is identified, determine the initial defect level according to the default level associated with the keyword, bind the device number, store it in the conversion result set, and proceed to step 3.6. If no keyword is identified, mark the device defect information as incomplete and proceed to step 3.6.

[0120] Step 3.6: Release the temporary data of the current device in the buffer and continue processing the next target device until all defective devices have been traversed.

[0121] Therefore, by using the above mapping table-driven conversion mechanism, unstructured or semi-structured defect status information can be uniformly converted into standardized initial defect levels, ensuring that defect data from different sources and with different representations have consistency and comparability in subsequent weighted calculations, and providing a reliable basis for generating scientific and reasonable power outage plans.

[0122] S302, Query the equipment importance weight table based on the equipment type information to obtain the corresponding weight value;

[0123] In formulating power outage maintenance plans, the impact of different equipment on power grid operation safety varies significantly. For example, a main transformer failure may lead to a large-scale power outage, while a defect in auxiliary equipment has a limited impact. If the maintenance sequence is arranged solely based on the defect level, the priority protection needs of critical equipment may be overlooked. Therefore, it is necessary to quantitatively assess the importance of equipment based on its type, obtaining the corresponding weight values ​​by consulting an equipment importance weight table, and providing a basis for subsequent weighted calculation of the final defect level.

[0124] Specifically, a weight lookup table mechanism based on equipment classification codes can be adopted. This mechanism relies on the power system's standard equipment classification system to match each type of equipment with a preset importance weight, ensuring that the weight assignment is standardized and consistent.

[0125] Specifically, the process begins by extracting equipment type information from the basic ledger of the target equipment. For example, the equipment type for phase A of the 110 kV main transformer is "main transformer type," the equipment type for bay B of the 35 kV circuit breaker is "switch type," and the equipment type for unit C of the 10 kV capacitor bank is "reactive power compensation type." Next, based on the equipment type name or code, a precise matching query is performed in the equipment importance weight table. This weight table is pre-set by the operation and maintenance management department based on factors such as the equipment's location in the power grid topology, its power supply range, and the impact of historical faults. Then, the weight value corresponding to the matching item is read; for example, the weight value for "main transformer type" is 1.5, for "switch type" it is 1.2, and for "reactive power compensation type" it is 0.8. Finally, each target device is bound to its obtained weight value, forming an equipment-weight mapping relationship for subsequent weighted calculation modules to use.

[0126] The equipment importance weight table is a structured configuration table stored in the system database. This table uses the equipment type as the index field and associates it with a numerical weight value greater than zero to reflect the criticality of this type of equipment in the operation of the power grid. The weight value is a quantitative coefficient that measures the importance of the equipment. The higher the value, the greater the impact of the equipment on the safe and stable operation of the system, and the higher its proportion in the final defect level calculation.

[0127] S303, the initial defect level and weight value are weighted to obtain the final defect level; if the equipment type is a critical power transmission and transformation equipment, the final defect level is forcibly upgraded to the severe level.

[0128] In the preparation of power outage maintenance plans, decisions based solely on the severity of defects or the importance of equipment cannot fully reflect the actual risk level of the equipment. Both factors must be integrated, and the urgency of maintenance for each piece of equipment must be comprehensively assessed through quantitative methods. Therefore, a weighted calculation of the initial defect level and the equipment importance weight value is necessary to generate a final defect level that truly reflects the overall risk of the equipment, providing a scientific basis for subsequent prioritization.

[0129] Specifically, a linear weighted mapping algorithm can be used to first convert discrete initial defect levels into numerical scores, then multiply them by continuous weight values, and finally map them back to the standard defect level system. This algorithm ensures that, under the same defect performance, critical equipment receives a higher risk rating, thus prioritizing its maintenance.

[0130] Specifically, the initial defect level is first converted into a numerical score according to preset rules, for example, 1 point for minor, 2 points for moderate, 3 points for major, and 4 points for emergency. Then, the weight value corresponding to the equipment is obtained. For example, the initial defect level of phase A of the 110 kV main transformer is major, corresponding to 3 points, with a weight value of 1.5; the initial defect level of bay B of the 35 kV circuit breaker is moderate, corresponding to 2 points, with a weight value of 1.2; and the initial defect level of unit C of the 10 kV capacitor bank is minor, corresponding to 1 point, with a weight value of 0.8. Finally, the weighted score is calculated, with the score for phase A of the main transformer being 3 multiplied by 1.5. The score is 4.5. The score of circuit breaker B bay is 2 multiplied by 1.2, which equals 2.4. The score of capacitor bank C unit is 1 multiplied by 0.8, which equals 0.8. Then, the weighted scores are classified according to the preset final defect level threshold range. For example, a score greater than or equal to 4.0 is judged as severe, 2.0 to 3.9 is judged as major, 1.0 to 1.9 is judged as moderate, and less than 1.0 is judged as minor. Finally, the main transformer A phase is determined to be severe, the circuit breaker B bay is major, and the capacitor bank C unit is minor, and these are recorded as the final defect levels of each device.

[0131] The final defect level refers to the risk level derived by comprehensively considering the severity of the equipment's own defects and the equipment's importance in the power grid. It is divided into four levels: minor, moderate, major, and severe, and is used to guide the priority ranking in power outage plans. The weighted calculation refers to the process of multiplying the numerical score of the initial defect level by the weight value of the equipment's importance to form a continuous score that reflects the comprehensive risk, and then mapping it back to the discrete level through a threshold.

[0132] In some embodiments, a linear weighted mapping algorithm is used to first convert discrete initial defect levels into numerical scores, then multiply them by continuous weight values, and finally map them back to the standard defect level system. The specific steps are as follows:

[0133] Step B1: Obtain the initial defect level and corresponding equipment importance weight value of the target equipment;

[0134] Step B2: Convert the initial defect level into the corresponding numerical score according to the preset level-score mapping rule;

[0135] Step B3: Multiply the numerical score by the equipment importance weight value to obtain the weighted composite score;

[0136] Step B4: Determine the final defect level based on the threshold range of the weighted composite score.

[0137] Furthermore, step B2 includes four cases: B21, B22, B23, and B24.

[0138] B21: When the initial defect level is determined to be minor, the numerical score is set as the first baseline score;

[0139] B22: When the initial defect level is determined to be moderate, the numerical score is set as the second baseline score;

[0140] B23: When the initial defect level is determined to be critical, the numerical score is set as the third baseline score;

[0141] B24: When the initial defect level is determined to be urgent, the numerical score is set to the fourth baseline score.

[0142] Furthermore, step B4 includes four cases: B41, B42, B43, and B44.

[0143] B41: When the weighted composite score is greater than or equal to the upper limit of the first threshold, the final defect level is determined to be severe.

[0144] B42: When the weighted composite score is less than the upper limit of the first threshold but greater than or equal to the upper limit of the second threshold, the final defect level will be determined as a critical level;

[0145] B43: When the weighted composite score is less than the upper limit of the second threshold but greater than or equal to the upper limit of the third threshold, the final defect level is determined to be the general level;

[0146] B44: When the weighted composite score is less than the upper limit of the third threshold, the final defect level will be determined as minor.

[0147] Therefore, through the multi-level judgment and mapping mechanism of the above-mentioned linear weighted mapping algorithm, the qualitative defect description and equipment importance can be integrated into a unified quantitative risk level, ensuring that critical equipment can still receive higher maintenance priority than ordinary equipment when there are moderate defects, thereby improving the scientific nature and safety of power outage plans.

[0148] In some embodiments, when generating an initial power outage plan, the plan generation module is specifically used for:

[0149] S401, group all equipment under maintenance in the first state that needs maintenance and all target equipment in the second state that is defective according to their substation, voltage level and bay name.

[0150] Before generating the initial power outage plan, equipment from both maintenance expiration dates and defect-triggered sources must be uniformly integrated to avoid duplication or omission. Failure to group equipment according to the power grid topology will result in a lack of organization in subsequent power outage arrangements, making it difficult to coordinate coordinated power outages of multiple devices within the same substation or electrical bay. Therefore, it is necessary to structure and group the two types of equipment based on their physical affiliation within the power system—namely, their substation affiliation, voltage level, and bay name—to form a logically clear and easily dispatchable equipment set.

[0151] Specifically, a multi-level grouping and aggregation strategy can be adopted. First, the two types of equipment lists are merged, and then nested groups are formed according to the three-level attributes of substation, voltage level, and bay name to ensure centralized management of equipment within the same electrical unit.

[0152] Specifically, the process begins by retrieving a list of all equipment requiring maintenance from the first planning module, such as the 110kV main transformer phase A (next maintenance date falls in the current calendar month) and the 35kV busbar PT (maintenance period expired). Then, the second planning module retrieves a list of all target equipment in a defective state, such as the 110kV main transformer phase A (abnormal winding temperature rise and planned status marked as active) and the 10kV capacitor bank unit C (oil leakage defect and planned status marked as active). The two lists are then merged and deduplicated to form a unified pool of equipment to be collected. Finally, the process is performed according to the substation to which the equipment belongs. The equipment is grouped into three levels, such as dividing all equipment into the first substation equipment group; then, within this substation group, it is further divided into two levels according to voltage level, forming the 110 kV group, the 35 kV group, and the 10 kV group; finally, within each voltage level group, it is divided into three levels according to bay name, such as the 110 kV main transformer bay, the 35 kV bus PT bay, and the 10 kV capacitor C bay; finally, each three-level group forms a collection unit, which contains all equipment under that bay that needs maintenance or has defects. For example, the collection unit of the 110 kV main transformer bay contains the A phase of the main transformer (which simultaneously meets the requirements of needing maintenance and defect status), which serves as the basic unit for subsequent priority ranking.

[0153] Among them, aggregation refers to the process of structurally grouping equipment from different judgment paths that need to be uniformly scheduled for power outage according to their hierarchical position in the physical structure of the power grid; the bay name refers to the identifier of the smallest electrical operation unit in the substation divided according to the function of primary equipment, such as "main transformer bay", "line bay", "capacitor bay", etc., which is used to define the operation and maintenance boundaries of the equipment.

[0154] S402, prioritize the collected equipment list according to the final defect level. The higher the defect level, the higher the ranking.

[0155] If all equipment is assigned maintenance order without differentiation during the initial power outage plan generation process, high-risk equipment may not be addressed in a timely manner, potentially leading to escalation of equipment failures or even grid accidents. Therefore, the final defect level must be used as the core prioritization criterion to ensure that equipment with serious and major defects receives priority access to power outage resources, achieving the maintenance goal of controllable risk and efficient resource allocation.

[0156] Specifically, a stable sorting algorithm based on the lexicographical order of defect levels can be used to arrange the aggregated equipment list from high to low according to the final defect level. Equipment of the same level will maintain the original aggregation order to avoid introducing additional uncertainty due to sorting disturbances.

[0157] Specifically, the final defect level of each device is first read from the collected equipment list. For example, the 110 kV main transformer phase A is classified as severe, the 35 kV circuit breaker bay B as major, the 10 kV capacitor bank unit C as minor, and the 35 kV busbar PT as general. Then, a sorting key-value mapping is established according to the preset defect level priority sequence—severe, major, general, minor. Next, the entire equipment list is sorted in descending order, with severe devices at the top, followed by major, general, and minor devices. For example, the sorted order is: main transformer phase A (severe), circuit breaker bay B (major), busbar PT (general), and capacitor bank unit C (minor). Finally, the sorted equipment list is output as the core content of the initial power outage plan for subsequent display and export.

[0158] The final defect level refers to the comprehensive risk level determined by weighting the initial defect level and the importance of the equipment, and is divided into four fixed levels: severe, major, general, and minor. Priority ranking refers to the process of linearly arranging equipment according to the final defect level. The higher the level, the greater the threat to power grid security the equipment poses, and the higher the priority should be given to power outage maintenance.

[0159] In some embodiments, the specific steps of the stable sorting algorithm based on defect level lexicographical order are as follows:

[0160] Step C1: Receive the completed list of devices, initialize the sorting buffer, and load the final defect level field for each device;

[0161] Step C2: Determine if the device list is empty. If it is empty, proceed to step C7; otherwise, proceed to step C3.

[0162] Step C3: Construct a defect level priority mapping table, mapping severe, major, minor, and slight to integer priority values ​​in sequence, with smaller priority values ​​indicating higher levels;

[0163] Step C4: Iterate through each device in the device list, query the mapping table according to its final defect level, obtain the corresponding integer priority value, and append it to the end of the device record as a sorting key;

[0164] Step C5: Call the stable sorting function to sort the device list in ascending order using integer priority values ​​as the primary key. If two devices have the same priority value, their original relative order during the aggregation phase is maintained.

[0165] Step C6: Write the sorted device list into the initial power outage plan output queue, clear the sorting buffer, and proceed to step C7.

[0166] Step C7: Release all temporary data structures and end the sorting process.

[0167] Therefore, by using the stable sorting algorithm based on the defect level dictionary order, it is possible to ensure that high-risk equipment is prioritized while maintaining the original logical order of equipment within the same risk level. This avoids confusion in the maintenance order of equipment within the same interval or voltage level due to sorting disturbances, thereby improving the feasibility of power outage plans and the efficiency of scheduling coordination.

[0168] S403 outputs the sorted list of devices as the initial power outage plan.

[0169] After completing the equipment aggregation and prioritization, the structured and ordered results must be solidified into a deliverable and operable initial power outage plan for review and subsequent adjustments by dispatching, operation and maintenance, and management personnel. Retaining only temporary data in memory without standardized output will prevent plan flow, hinder collaboration, and even lead to missed maintenance tasks. Therefore, the sorted equipment list must be packaged into an initial power outage plan according to a unified format, ensuring it includes all necessary attribute fields to support subsequent visualization and export functions.

[0170] Specifically, a structured plan generator can be used to convert the sorted equipment list into plan entries containing complete business attributes, and inject metadata to identify the source type, forming a standard initial version of the power outage plan dataset.

[0171] Specifically, the system first receives a sorted list of equipment from the priority sorting module, such as 110kV main transformer phase A (critical level), 35kV circuit breaker bay B (major level), 35kV busbar PT (general level), and 10kV capacitor bank unit C (minor level). Then, it adds fields for each piece of equipment, including its substation, voltage level, bay name, equipment type, defect description, and plan source identifier, where the plan source identifier is marked as "cycle expired," "defect triggered," or "project management." Next, these are assembled sequentially into a structured record set, with each record representing a piece of equipment for which a power outage is scheduled. This set is then encapsulated into a preliminary power outage plan object, with a generation timestamp and version identifier added. Finally, this object is written to the output interface of the plan generation module for use by the visualization module or for subscription by external systems.

[0172] The initial power outage plan refers to a structured data set automatically generated by the system, containing all equipment that needs to be scheduled for power outage maintenance and their priority order. This plan has not yet been manually coordinated or verified by resource constraints, but it has integrated multi-source demands and completed risk priority ranking. The plan source identifier is used to distinguish the reasons for including equipment in the plan, including three categories: maintenance cycle expiration, activation defects, or related project management tasks, which facilitates subsequent traceability and statistical analysis.

[0173] In some embodiments, the information acquisition module is further configured to:

[0174] S501 responds to scheduled task instructions, automatically queries the project management database, and obtains the equipment list associated with projects that intersect with the current month's time window;

[0175] In the process of compiling power system maintenance plans, in addition to periodic maintenance and defect handling, there are numerous power outage demands driven by projects such as infrastructure renovation, technical upgrades, major overhauls, or special projects. Failure to include equipment associated with these projects in the initial power outage plan will hinder project implementation or lead to duplicate power outages, impacting overall operation and maintenance efficiency. Therefore, it is essential to proactively connect to the project management database through a scheduled task mechanism to accurately identify projects that overlap with the current month and extract their associated equipment lists, serving as a crucial supplementary source for the initial power outage plan.

[0176] Specifically, an automatic query mechanism based on time window intersection detection can be adopted. At the beginning of each month, the system scheduler triggers a scheduled task to connect to the project management database and execute a structured query to filter out project records whose planned implementation time overlaps with the current calendar month.

[0177] Specifically, the system scheduling module first triggers a scheduled task instruction at midnight on the first day of each month; then, it determines the time window based on the current calendar month. For example, if the current month is February 2**5, the time window is from February 1st to February 31st, 2**5. Next, it sends an SQL query to the project management database with the condition that "the planned start date of the project is less than or equal to the end date of the time window and the planned end date of the project is greater than or equal to the start date of the time window". Then, it extracts the unique identifier of each matching project and its associated equipment list from the returned results. For example, if the planned time for a 110 kV main transformer capacity expansion project is from January 20th to February 10th, 2**5, which intersects with the current time window, its associated equipment includes the A phase of the 110 kV main transformer and its matching disconnect switch. Then, it merges and removes duplicates from the equipment lists of all matching projects to form a complete set of project-driven equipment. Finally, it pushes this set along with the source identifier "Project Management" to the plan generation module for subsequent merging into the initial version of the power outage plan.

[0178] Among them, the current month time window refers to the complete calendar month interval defined by the Gregorian calendar year and month of the current system date, which is used to define the scope of projects that need to be considered in this month; the project management database refers to the structured database that stores information on various power grid engineering projects, including fields such as project number, name, planned start and end time, and list of associated equipment; time window intersection means that the planned implementation period of the project overlaps with the current month time window by at least one day, regardless of whether the project is a cross-month continuation or only partially falls within the current month.

[0179] S502, the plan generation module is also used to merge the equipment in the equipment list into the initial power outage plan and mark its source as project management.

[0180] If the initial power outage plan is developed solely based on periodic maintenance and defect-triggered needs, necessary power outages driven by engineering projects will be overlooked, potentially preventing timely implementation of technical upgrades, infrastructure projects, or major repairs. Therefore, it is essential to seamlessly integrate the equipment list obtained from the project management database into the already sorted initial power outage plan, clearly identifying its source and attributes. This ensures that dispatchers can differentiate between different demand types and coordinate resources appropriately.

[0181] Specifically, an incremental merging strategy with source identifiers can be adopted. While retaining the original priority structure, project-related equipment can be inserted as supplementary entries at the end of the plan and uniformly injected with the "Project Management" source label to avoid confusion with periodic or defective equipment.

[0182] Specifically, the process first receives the project-driven equipment list output by step S501, such as the 110kV main transformer phase A and its matching disconnector associated with a 110kV main transformer capacity expansion project, and the 35kV circuit breaker D bay associated with a 35kV line renovation project. Then, it checks whether these devices already exist in the current initial power outage plan. If they do, duplicates are skipped, and only missing devices are added. Next, basic attributes such as the substation, voltage level, bay name, and equipment type are filled in for each newly added device, and the source field is forcibly set to "Project Management". Then, these devices are appended to the end of the initial power outage plan as an additional list, without participating in the priority sorting based on defect level, as the necessity of the power outage is determined by the project progress rather than the risk level. Finally, the version identifier and total equipment count of the initial power outage plan are updated to complete the merge operation.

[0183] Among them, the project management source refers to the type of demand for equipment that is included in the power outage plan due to its participation in power grid infrastructure, technical transformation or special projects. This source is independent of the expiration of the maintenance cycle or the triggering of defect status. The incremental merging strategy refers to the processing method of integrating new source equipment into the existing plan in an additional manner without destroying the existing plan structure, so as to ensure that multi-source demand is traceable, distinguishable and coordinated.

[0184] In some embodiments, the system further includes a data comparison module and a visualization module;

[0185] S601, the data comparison module is used to compare the imported external plan data with the data in the maintenance cycle database, defect management database and project management database by field matching.

[0186] In actual operation and maintenance work, dispatching departments or collaborating units often provide draft external power outage plans, such as regional coordination plans, cross-unit joint inspection schemes, or temporary power supply arrangements. Directly adopting this external data without cross-validation may introduce duplicate, conflicting, or invalid equipment entries, compromising the completeness and accuracy of the initial power outage plan. Therefore, it is essential to use a data comparison module to perform multi-source field-level matching between external plans and the system's three core databases—the maintenance cycle database, the defect management database, and the project management database—to identify high-reliability equipment records that simultaneously meet multiple business conditions, serving as supplementary input to the initial power outage plan.

[0187] Specifically, a three-way parallel matching mechanism can be adopted to simultaneously query three internal databases for each device in the external plan, and make precise comparisons based on key fields such as device number, substation name, voltage level and bay name, and record the source of the matching results.

[0188] Specifically, the system first receives external planning data uploaded by users, such as an Excel spreadsheet containing information on 110kV main transformer phase A, 35kV circuit breaker bay E, and 10kV switchgear unit F. Then, it extracts the unique equipment identifier and related topology attributes for each record. Next, it initiates a three-way comparison process: the first path compares the equipment information with the maintenance cycle database to confirm whether it is in a maintenance-required state; the second path compares it with the defect management database to confirm whether there are any active defect records; and the third path compares it with the project management database to confirm whether it is associated with any engineering projects implemented in the current month. Then, it summarizes the results of the three comparisons. For example, if main transformer phase A matches in both the defect management and project management databases but not in the maintenance cycle database, it determines whether at least two databases match. If so, the equipment is marked as a "multi-source consistent equipment." Finally, all multi-source consistent equipment is filtered out and pushed to the plan generation module as enhanced input for generating the initial power outage plan.

[0189] Among them, other external planning data refers to draft power outage plans or equipment lists provided by external entities that are not automatically generated by this invention. These typically originate from superior dispatch instructions, reports from collaborating units, or reuse of historical plans. Field matching and comparison refers to the process of comparing precise values ​​between different databases based on structured fields such as equipment number, substation, voltage level, and bay name. Multi-source consistent equipment refers to equipment that appears in external plans and has corresponding records in at least two of the maintenance cycle database, defect management database, and project management database. This indicates that its power outage requirements have multiple business bases and are highly reliable.

[0190] S602, filter out the device records that meet multiple library conditions in the comparison results and push them to the plan generation module as supplementary input for generating the initial version of the power outage plan;

[0191] When integrating external planning data, indiscriminate import of all data may introduce isolated, outdated, or unverified equipment entries, interfering with the system's automatically generated maintenance logic. Only equipment with confirmed genuine power outage needs across multiple business dimensions deserves high priority for inclusion in the initial power outage plan. Therefore, it is essential to accurately select equipment records that match at least two of the maintenance cycle database, defect management database, and project management database from the comparison results. This ensures that the necessity of their power outages is supported by multiple business considerations, thereby enhancing the comprehensiveness and authority of the initial power outage plan.

[0192] Specifically, a multi-database intersection judgment rule can be adopted to logically combine and judge the three comparison results of each external device. Only when the number of matching databases is greater than or equal to two is it considered a valid supplementary device.

[0193] Specifically, the matching status of each external device output from step S601 in the three internal databases is first obtained. For example, the 110 kV main transformer phase A is successfully matched in the defect management database and the project management database, but not in the maintenance cycle database; the 35 kV circuit breaker E bay is only successfully matched in the maintenance cycle database, with no record in the other two databases; the 10 kV switchgear unit F is successfully matched in both the defect management database and the maintenance cycle database. Then, the number of databases in which each device is successfully matched is counted: the main transformer A is matched in 2 databases, the circuit breaker E bay is matched in 1 database, and the switchgear unit F is matched in 2 databases. Next, based on the filtering condition of "number of matching databases ≥ 2", the main transformer phase A and the switchgear unit F are retained, while the circuit breaker E bay is removed. Then, the source identifier "multi-source verification" is added to the retained devices, and the substation, voltage level, bay name, and original external plan number are completed. Finally, the filtered device records are packaged into a structured data package and pushed to the plan generation module through the internal message channel as a supplementary input for the initial power outage plan to participate in subsequent collection and sorting.

[0194] Among them, multiple database conditions refer to the existence of consistent and valid records for equipment in at least two databases: the maintenance cycle database, the defect management database, and the project management database; multi-source verification refers to the system recognizing equipment as a high-confidence power outage object because it simultaneously meets two or more business scenarios (such as requiring both periodic maintenance and being associated with engineering projects, or having both activated defects and being in the maintenance window); supplementary input refers to an additional set of cross-validated equipment injected in addition to the periodic and defect-driven equipment automatically generated by the system, used to enhance the coverage completeness of the initial power outage plan.

[0195] S603, the visualization module is used to display the initial power outage plan in tabular form on the user interface;

[0196] S604, Equipment items with a severe defect level are highlighted in red;

[0197] The S605 provides an export button, which, in response to user actions, exports the initial power outage plan as an Excel file.

[0198] In some embodiments, a new unit including assessment and conflict detection functions can be designed. This unit can be used to perform maintenance resource conflict detection and collaborative feasibility assessment on the equipment in the initial power outage plan. The specific steps can be as follows:

[0199] Specifically, the steps for conducting maintenance resource conflict detection and collaborative feasibility assessment on the equipment in the initial power outage plan include steps D1 to D5:

[0200] Step D1: Obtain the substation, voltage level, and bay name of all equipment in the initial power outage plan;

[0201] Step D2: Determine the power outage operation unit corresponding to each device based on the interval name, and query the existing dispatch and maintenance windows for that operation unit in the current month;

[0202] Step D3: Determine whether there are multiple devices within the same operating unit that have overlapping maintenance needs scheduled from different planning sources;

[0203] Step D4: If there is a time overlap, initiate the collaborative merging strategy to generate a unified joint power outage recommendation;

[0204] Step D5: Integrate conflict-free devices with merged joint outage units into an optimized initial outage plan output.

[0205] Furthermore, step D3 includes three cases: D31, D32, and D33.

[0206] D31: When it is determined that only one device is included in the initial power outage plan within the same interval, mark the device as an independent executable unit, which does not require collaborative processing;

[0207] D32: When multiple devices within the same interval are determined to originate from the same plan type (e.g., all are defect-triggered), they are automatically merged into a single power outage task to reduce the number of operations.

[0208] D33: When multiple devices are located within the same interval and originate from different plan types (e.g., one from periodic maintenance and one from project management), check whether their planned time windows overlap. If they overlap, they are forcibly merged into a joint power outage unit and marked with the "multi-source collaboration" label. If they do not overlap, a resource conflict warning is issued and the original entry is retained for manual review.

[0209] Therefore, by introducing a maintenance resource conflict detection and collaborative feasibility assessment mechanism, it is possible to identify and resolve repeated power outages or time conflicts within the same electrical bay in advance during the automatic generation of the initial power outage plan, significantly reducing the subsequent manual coordination workload, while improving the decoupling efficiency of power grid outages and the safety of operation and maintenance.

[0210] Among them, the operating unit refers to the collection of electrical equipment in a substation that can be independently shut down and isolated, with the interval as the smallest unit; the joint power outage suggestion refers to the combined execution plan proposed for multiple equipment that need to be shut down within the same operating unit, aiming to complete all maintenance tasks in one power outage operation; the multi-source collaborative identifier is used to mark power outage tasks driven by different business sources but automatically merged by the system due to overlapping physical locations, which facilitates subsequent traceability and statistical analysis.

[0211] Example 2, refer to Figure 2 This embodiment also provides a power outage maintenance method, including:

[0212] The information acquisition module obtains information about the first and second equipment of the first substation.

[0213] The first determination module and the second determination module respectively determine the first state of the equipment to be inspected and the second state of the target equipment.

[0214] When the first state is a maintenance-required state, the first planning module generates the first planning information; when the second state is a defective state, the second planning module generates the second planning information.

[0215] The initial power outage plan is generated by combining equipment type information, defect level, first plan information, and second plan information through the plan generation module.

[0216] The above-mentioned unit modules can be embedded in the processor of the electronic device in hardware form or independent of it, or they can be stored in the memory of the electronic device in software form, so that the processor can call and execute the corresponding operations of the above modules.

[0217] This embodiment also provides an electronic device, which can be a terminal, and its internal structure diagram can be as follows. Figure 2As shown, the electronic device includes a processor, memory, communication interface, display screen, and input device connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a power outage maintenance method. The display screen can be an LCD screen or an e-ink screen. The input device can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the device's casing, or an external keyboard, touchpad, or mouse.

[0218] This embodiment also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, it performs the following steps:

[0219] The information acquisition module obtains information about the first and second equipment of the first substation.

[0220] The first determination module and the second determination module respectively determine the first state of the equipment to be inspected and the second state of the target equipment.

[0221] When the first state is a maintenance-required state, the first planning module generates the first planning information; when the second state is a defective state, the second planning module generates the second planning information.

[0222] The initial power outage plan is generated by combining equipment type information, defect level, first plan information, and second plan information through the plan generation module.

[0223] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A power outage maintenance system, characterized in that, include: The information acquisition module is used to acquire information about the first and second equipment in the first substation. The first equipment information is used to characterize the maintenance cycle status of the equipment to be inspected in the first substation. The second equipment information is used to characterize the defect status of the target equipment within the first substation; The first determining module is used to determine the first state of the equipment to be repaired based on the first equipment information. The first state includes any one of the following: maintenance required state and maintenance not required state; The first planning module is used to generate first planning information based on the maintenance-required state when the first state is in the maintenance-required state. The first plan information is used to prompt staff to include the equipment to be repaired in the initial power outage plan; The second determining module is used to determine the second state of the target device based on the second device information; The second state includes any one of the following: normal state and defective state; The second planning module is used to generate second planning information based on the defective state when the second state is in the defective state; the second planning information is used to prompt staff to include the target equipment in the initial power outage plan; The plan generation module is used to obtain the equipment type information of the target equipment, determine the defect level of the target equipment based on the equipment type information and the defect status, and generate the initial power outage plan based on the defect level, the first plan information and the second plan information to meet the maintenance needs of the equipment in the first substation.

2. The power outage maintenance system as described in claim 1, characterized in that, The first determining module is specifically used for: A structured parsing engine is used to identify and extract fields from the first equipment information. The first equipment information is parsed to extract the next maintenance date of the equipment to be repaired. The parsing process first verifies the data integrity and confirms that the next maintenance date field exists and is in a compliant format. If a field is missing, the next maintenance date is dynamically calculated based on the last maintenance time and the number of days in the maintenance cycle; then the date is compared with the current calendar month for subsequent status determination. A precise comparison method based on calendar time intervals is adopted to match the extracted next maintenance date with the natural month boundary corresponding to the current system time to determine whether the next maintenance date belongs to the current natural month; If so, then set the first state to the state requiring maintenance; If not, then set the first state to the maintenance-free state.

3. The power outage maintenance system as described in claim 1, characterized in that, The second determining module is specifically used for: A structured parsing process for defect information is adopted to extract fields and verify status of the second equipment information. The second equipment information is parsed to obtain the defect record and corresponding planned status identifier of the target equipment. First, all defect entries of the target equipment are read from the defect management database of the first substation. Then, for each defect entry, its "planned status identifier" field is checked. Next, it is determined whether the defect record exists and whether the planned status identifier is active. Finally, the equipment that meets the conditions and its defect record and active status identifier are combined and output. A dual-condition logic judgment mechanism is used to classify the status of each target device. When the defect record exists and the plan status is active, the second status is determined to be the defect status. When the defect record does not exist or the plan status is inactive, the second status is determined to be the normal status.

4. The power outage maintenance system as described in claim 1, characterized in that, When determining the defect level of the target device based on the device type information and the defect status, the plan generation module is specifically used for: A mapping table-driven conversion mechanism based on defect type and severity is adopted to convert the defect status into an initial defect level based on preset defect level mapping rules; Based on the equipment type information, query the equipment importance weight table to obtain the corresponding weight value; first, extract the equipment type information from the basic ledger of the target equipment, then perform a precise matching query in the equipment importance weight table according to the equipment type name or code, then read the weight value corresponding to the matching item, and finally, bind each target equipment with its obtained weight value to form an equipment-weight mapping relationship. The initial defect level is weighted and calculated with the weight value to obtain the final defect level; wherein, if the equipment type is a critical power transmission and transformation equipment, the final defect level is forcibly upgraded to the severe level. When performing weighted calculations, a linear weighted mapping algorithm is used to first convert the discrete initial defect levels into numerical scores, then multiply them by continuous weight values, and finally map them back to the standard defect level system.

5. A power outage maintenance system as described in claim 1, characterized in that, When generating the initial power outage plan, the plan generation module is specifically used for: All equipment in the first state that needs maintenance and all target equipment in the second state that is defective are grouped according to their substation, voltage level and bay name. Specifically, a multi-level grouping and aggregation strategy is adopted. First, the two types of equipment lists are merged, and then nested grouping is carried out according to the three-level attributes of substation, voltage level and bay name to ensure centralized management of equipment within the same electrical unit. Based on the final defect level, a stable sorting algorithm based on the lexicographical order of the defect level is used to prioritize and sort the collected device list. The higher the defect level, the higher the ranking. Devices of the same level maintain their original collection order. The sorted list of devices is output as the initial power outage plan.

6. The power outage maintenance system as described in claim 1, characterized in that, The information acquisition module is also used for: In response to scheduled task instructions, an automatic query mechanism based on time window intersection detection is adopted to automatically query the project management database and obtain the equipment list associated with projects that intersect with the current month's time window; The plan generation module is also used to merge the equipment in the equipment list into the initial power outage plan using an incremental merging strategy with source identification, and mark its source as project management; the incremental merging strategy with source identification, while retaining the original priority structure, inserts project-related equipment as supplementary entries at the end of the plan, and uniformly injects the "project management" source label.

7. A power outage maintenance system as described in claim 1, characterized in that, The system also includes a data comparison module and a visualization display module; The data comparison module is used to compare the imported external planning data with the data in the maintenance cycle database, defect management database, and project management database by field matching. The device records that simultaneously meet multiple library conditions in the comparison results are filtered out and pushed to the plan generation module as supplementary input for generating the initial power outage plan; The visualization module is used to display the initial power outage plan in tabular form on the user interface; Equipment items with a severe defect level are highlighted in red. An export button is provided to export the initial power outage plan as an Excel file in response to user actions.

8. A power outage maintenance method, using the power outage maintenance system as described in any one of claims 1 to 7, characterized in that, include: The information acquisition module obtains information about the first and second equipment of the first substation. The first determination module and the second determination module respectively determine the first state of the equipment to be inspected and the second state of the target equipment. When the first state is a maintenance-required state, the first planning module generates the first planning information; when the second state is a defective state, the second planning module generates the second planning information. The initial power outage plan is generated by combining equipment type information, defect level, first plan information, and second plan information through the plan generation module.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the power outage maintenance method according to claim 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the power outage maintenance method as described in claim 8.

Images