Sequential control ticket text importing method and system based on regular expression

Abstract

The invention relates to the technical field of power system automation, in particular to a sequential control ticket text importing method and system based on a regular expression, and the method comprises the steps: obtaining sequential control ticket text content, analyzing the sequential control ticket text content based on the regular expression, and obtaining an analysis result; if the analysis is successful, matching the analysis result with data in a monitoring database; and importing the instantiated electronic ticket obtained by successful matching into a monitoring database of a monitoring system. According to the method, the full-process automation from text analysis to data library writing is realized, and the problems of efficiency bottleneck and semantic ambiguity existing in a traditional manual importing mode are effectively solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of power system automation, in particular to a regular expression-based sequence control ticket text import method and system. BACKGROUND

[0002] In the daily operation and maintenance management of substations, the import of sequence control tickets (full name: sequence control operation tickets) is a key link to ensure safe and efficient operation of equipment. Traditional sequence control ticket import mainly relies on manual operation mode. However, based on long-term practical operation experience of substations and in-depth analysis of a large number of actual cases, combined with careful observation and systematic summary of the sequence control ticket import operation process, it is found that the manual import method has many problems and deficiencies that need to be solved, which seriously hinders the modernization process of substation operation and maintenance management.

[0003] Efficiency bottleneck: Substation sequence control tickets cover a large number of operation steps and involve a large number of complex parameter settings. When manually importing, the operator needs to input each item of information word by word and sentence by sentence, and repeatedly checks to ensure accuracy. In the face of a large amount of information, the operator's processing speed is extremely slow, which not only directly leads to low efficiency of substation operation and maintenance, but also ties up a large number of human resources in tedious data entry work, affecting the overall improvement of substation operation efficiency.

[0004] High error risk: The process of manually importing sequence control tickets is essentially a collection of a large number of repetitive and tedious operations. The operator is prone to fatigue in a long and intense working state, and it is difficult to maintain high concentration at all times. At the same time, when manually entering data, it is inevitable that errors will occur. Incorrect sequence control ticket data may cause equipment malfunction, trigger safety accidents, cause equipment damage, and even paralyze the power grid, posing a huge threat to the stable operation of the power system.

[0005] Serious lack of real-time performance: Traditional manual import of sequence control tickets usually follows a fixed time schedule, such as daily at a specific time or regularly for centralized processing. This mode cannot adapt to the dynamic changes in the substation operating environment. In actual operation, substations may face unexpected situations at any time and need to adjust the sequence control ticket content in a timely manner to respond to changes. However, the fixed time schedule of manual import makes it impossible to update and process sequence control tickets in real time, causing substation operation and maintenance personnel to be unable to obtain the latest operation instructions in a timely manner, delaying the handling of emergency situations and increasing the risk of accident expansion, seriously affecting the rapid response capability of substations to deal with unexpected events.

[0006] High skill dependency: The order control ticket import work requires operators to have solid power system knowledge, rich equipment operation experience and accurate data processing ability. The operator not only needs to be familiar with the performance parameters and operation specifications of various devices in the substation, but also needs to accurately understand the meaning and logical relationship of each instruction in the order control ticket. However, in actual work, the skill level of operators is uneven, and operators with insufficient skills or experience may have deviations in understanding the order control ticket, and may misinterpret or make mistakes during import. This high dependence on operator skills makes it difficult to effectively guarantee the quality and stability of order control ticket import work, increasing the uncertainty of substation operation and management. SUMMARY

[0007] The purpose of the present application is to provide a regular expression-based order control ticket text import method and system to solve at least one of the above technical problems, to realize efficient, accurate and real-time import of order control tickets, and to provide strong support for the safe and stable operation of substations.

[0008] The present application achieves the above-mentioned purposes through the following technical solutions:

[0009] A regular expression-based order control ticket text import method, comprising:

[0010] Obtain the order control ticket text content, parse the order control ticket text content based on regular expressions, and obtain the parsing result;

[0011] If the parsing is successful, match the parsing result with the data in the monitoring database;

[0012] Import the instantiated electronic ticket obtained by successful matching into the monitoring database of the monitoring system.

[0013] Further, the order control ticket includes primary operation tickets and secondary operation tickets; each type of operation ticket includes an order control ticket name and an order control ticket step.

[0014] The parsing result includes a parsing conclusion and data obtained by parsing;

[0015] The parsing conclusion includes parsing success and parsing failure.

[0016] Further, the parsing of the order control ticket text content includes:

[0017] According to the first format template, the order control ticket name is parsed to obtain the interval name, interval source state and interval target state; if the order control ticket name cannot be parsed by the first format template, the parsing conclusion is output as parsing failure; wherein the first format template is a preset syntax for parsing the order control ticket name.

[0018] If the sequence control ticket name is successfully parsed, the sequence control ticket step name is parsed according to a second format template; if the sequence control ticket step name cannot be parsed by the second format template, the parsing result is output as a parsing failure; wherein the second format template is a preset syntax for parsing the sequence control ticket step name.

[0019] Further, the first format template of the primary operation ticket includes: (1) "XXX is converted from YYY to ZZZ"; (2) "XXX is reversed from YYY to ZZZ"; (3) "XXX is converted from YYY to ZZZ"; wherein XXX represents an interval name, YYY represents an interval source state, and ZZZ represents an interval target state.

[0020] The first format template of the secondary operation ticket includes: "put into XXX protection", "exit XXX protection", "put into XXX reclosing", and "exit XXX reclosing".

[0021] Further, the second format template includes:

[0022] (1) For the sequence control ticket step name with the syntax "pull XXX", "disconnect XXX", and "close XXX", the operation item type is "primary remote control", and the XXX primary device name and the "five-protection remote signal" name are matched;

[0023] (2) For the sequence control ticket step name with the syntax "put into XXX" and "exit XXX", the operation item type is "pressure plate remote control", and the XXX secondary soft pressure plate name and the IED protection LD or the SPG soft pressure plate object name under the public LD are matched;

[0024] (3) For the sequence control ticket step name with the syntax containing ".* background.*", ".* check.*", ".* on-site.*", ".* measurement.*", ".* manual.*", ".* reset.*", ".* check $", and ".* remote control and pressure plate $", the operation item type is "prompt item";

[0025] The sequence control ticket step name that does not satisfy the above three points is output as a parsing failure.

[0026] Further, the parsing result is matched with the data in the monitoring database, including:

[0027] The data obtained by parsing the sequence control ticket name is matched with the data in the monitoring database according to a first matching rule;

[0028] The data obtained by parsing the sequence control ticket step name is matched with the data in the monitoring database to obtain a sequence control ticket step matching result.

[0029] Further, the first matching rule comprises: matching the interval name with the "alias" of the PMS interval object, and matching the interval source state and the interval target state with the state of the national grid interval, respectively.

[0030] Further, the data obtained by parsing the sequence control ticket step name is matched with the data in the monitoring database, comprising:

[0031] Comparing whether the number of operation steps is consistent; if not, obtaining the sequence control ticket step matching result as "step inconsistency", and ending the comparison; if consistent, continuing to perform the comparison;

[0032] According to the second matching rule, the step details are compared, and the sequence control ticket step matching result is obtained.

[0033] The sequence control ticket step matching result further comprises: "step description inconsistency", "step type inconsistency", "step associated remote control point", and "platen point inconsistency".

[0034] Further, the second matching rule comprises: primary equipment name matching and protection soft platen name matching.

[0035] The primary equipment name matching comprises: (1) extracting the primary equipment dispatch number in the text and matching the primary equipment dispatch number with the "five-prevention remote signal" name; (2) if the matching fails, the primary equipment dispatch number is not extracted, and the full operation step is matched with the "five-prevention remote signal" name again.

[0036] The protection soft platen name matching comprises: querying the IED protection LD or the SPG soft platen object under the public LD of the "protection device" added in the "protection device table" of the PMS interval object, obtaining the actual SPG soft platen name in the protection device; and matching the protection soft platen name with the actual SPG soft platen name in the protection device.

[0037] A sequence control ticket text import system based on a regular expression comprises:

[0038] A parsing module is configured to obtain sequence control ticket text content, parse the sequence control ticket text content based on a regular expression, and obtain a parsing result.

[0039] A matching module is configured to match the parsing result with data in a monitoring database if the parsing is successful.

[0040] A ticket writing module is configured to import the instantiated electronic ticket obtained by the matching into a monitoring database of a monitoring system.

[0041] The present application has the following beneficial effects:

[0042] The application optimizes the substation sequential control ticket import process: through regular expression driven automated analysis and double-layer verification mechanism, the efficiency of traditional manual import is improved, the error rate is reduced, and millisecond-level real-time interaction between operation ticket and monitoring system is realized.

[0043] The application is compatible with the differentiated naming specification of primary / secondary operation tickets, and through the fault-tolerant design combining device number priority matching and full-text bottom-up verification, the success rate of analysis of non-standard expressions is improved, and relying on IED device level soft pressure plate matching technology, manual configuration errors are effectively avoided.

[0044] The application provides high-reliability operation support for substation control systems through standardized and intelligent data integration mode, and significantly reduces the operation risk caused by human factors. BRIEF DESCRIPTION OF DRAWINGS

[0045] Figure 1 The figure is a regular expression-based substation sequential control ticket text import method flowchart of one embodiment of the application;

[0046] Figure 2 The figure is a regular expression-based substation sequential control ticket text import method flowchart of another embodiment of the application;

[0047] Figure 3 The figure is a regular expression-based substation sequential control ticket text import method principle diagram of one embodiment of the application;

[0048] Figure 4 The figure is a substation sequential control ticket text content schematic diagram of one embodiment of the application;

[0049] Figure 5 The figure is a substation sequential control ticket text content schematic diagram of another embodiment of the application;

[0050] Figure 6 The figure is a regular expression-based substation sequential control ticket text import system schematic diagram of one embodiment of the application. DETAILED DESCRIPTION

[0051] The content of the application will now be discussed with reference to exemplary embodiments. It should be understood that the discussed embodiments are only to enable those of ordinary skill in the art to better understand and thus implement the content of the application, and are not intended to imply any limitation on the scope of the application.

[0052] As used herein, the term "comprising" and variations thereof are to be construed as meaning "including but not limited to". The term "based on" is to be construed as "based at least in part on". The terms "one embodiment" and "an embodiment" are to be construed as "at least one embodiment".

[0053] Embodiment one

[0054] Figure 1 A flow chart of a regular expression-based order control ticket text import method is an embodiment of the present application. Figure 1 As shown in the figure, according to an embodiment of the present application, a regular expression-based order control ticket text import method comprises the following steps:

[0055] In step S102, the order control ticket text content is obtained, the order control ticket text content is parsed based on a regular expression, and a parsing result is obtained.

[0056] In step S104, if the parsing is successful, the parsing result is matched with data in a monitoring database.

[0057] In step S106, the instantiated electronic ticket obtained by successful matching is imported into the monitoring database of the monitoring system.

[0058] The order control ticket comprises a primary operation ticket and a secondary operation ticket; each type of operation ticket comprises an order control ticket name and an order control ticket step.

[0059] The parsing result comprises a parsing conclusion and data obtained by parsing.

[0060] The parsing conclusion comprises parsing success and parsing failure.

[0061] In the embodiment, a regular expression-based order control ticket text automatic import method is provided, and the structured text is intelligently parsed and matched by using a pre-defined regular expression template library. Specifically, in the parsing stage, the regular engine is used to identify the operation ticket type (primary / secondary), and the standardized ticket header syntax and operation step syntax are matched respectively, and key elements such as interval name, device number and operation type are extracted. For non-standard expressions, the operation type is identified based on the regular expression. In the matching stage, a double-checking mechanism is used: first, the interval alias mapping and the State Grid comparison are used to ensure that the macro operation object is correct, and then the device number is used to match the combination of the priority matching and the full-text fuzzy matching, so as to be compatible with the field differentiated naming specification, and finally the instantiated electronic ticket meeting the format requirements of the monitoring database is generated.

[0062] The present application realizes the full-process automation from text parsing to data writing, and effectively solves the efficiency bottleneck and semantic ambiguity problems existing in the traditional manual import method.

[0063] According to an embodiment of the present application, in step S102, the order control ticket text content is parsed, comprising:

[0064] In step S1022, the sequence control ticket name is parsed according to the first format template to obtain the interval name, interval source state and interval target state. If the sequence control ticket name cannot be parsed by the first format template, the parsing result is that the parsing fails. The first format template is a preset syntax for parsing the sequence control ticket name.

[0065] In step S1024, if the sequence control ticket name is parsed successfully, the sequence control ticket step name is parsed according to the second format template. If the sequence control ticket step name cannot be parsed by the second format template, the parsing result is that the parsing fails. The second format template is a preset syntax for parsing the sequence control ticket step name.

[0066] Preferably, the first format template of the primary type operation ticket includes: (1) “transfer XXX from YYY to ZZZ”; (2) “transfer XXX from YYY to ZZZ”; (3) “transfer XXX from YYY to ZZZ”; wherein XXX represents the interval name, YYY represents the interval source state, and ZZZ represents the interval target state.

[0067] The first format template of the secondary type operation ticket includes: “put into XXX protection”, “exit XXX protection”, “put into XXX reclosing”, and “exit XXX reclosing”.

[0068] Preferably, the second format template includes:

[0069] (1) For the sequence control ticket step name with the syntax “pull XXX”, “disconnect XXX” and “close XXX”, the operation item type is “primary remote control”, and the XXX primary device name and the “five-protection remote signal” name are matched;

[0070] (2) For the sequence control ticket step name with the syntax “put into XXX” and “exit XXX”, the operation item type is “pressure plate remote control”, and the XXX secondary soft pressure plate name and the IED protection LD or the SPG soft pressure plate object name under the public LD are matched;

[0071] (3) For the sequence control ticket step name with the syntax containing “.*background.*”, “.*check.*”, “.*on-site.*”, “.*measurement.*”, “.*manual.*”, “.*reset.*”, “.*check$”, “.*remote control closing pressure plate$”, the operation item type is “prompt item”;

[0072] The sequence control ticket step name that does not satisfy the above three points is output as a parsing failure.

[0073] In this embodiment, the text content of the sequential control ticket is analyzed by using a double-layer analysis mechanism: first, the name of the sequential control ticket is analyzed based on a first format template to extract macro operation objects such as interval name, interval source state and interval target state; and only when the name of the sequential control ticket is successfully analyzed, a second format template is started to analyze each step of the sequential control ticket. This hierarchical verification design effectively avoids redundant processing of invalid steps, and significantly improves the utilization rate of system resources.

[0074] At the name analysis level of the sequential control ticket, differentiated regular templates are constructed for primary operation tickets and secondary operation tickets. The primary operation ticket uses a dynamic syntax template such as “change XXX from YYY to ZZZ”, and extracts three elements XXX (interval name), YYY (interval source state) and ZZZ (interval target state) by using named entity recognition technology. The secondary operation ticket defines standardized operation sentence patterns such as “put in / exit XXX protection / reclosing” according to the characteristics of protection devices. In particular, the secondary ticket analysis module is compatible with composite expressions such as “1 / 2+bus+state name of national grid equipment”, and realizes automatic separation of equipment number and state description by using the grouping capture mechanism of regular expressions.

[0075] For the analysis of the step name (operation step) of the sequential control ticket, three regular matching rules are designed: for primary device operations such as “open / disconnect / close XXX”, the number in XXX (such as 5022) is extracted and accurately matched with the five-prevention remote signal table; for “put in / exit XXX” and other platen operations, the IED protection LD or SPG soft platen object name under the public LD is directly associated; for inspection-type auxiliary operations, a keyword matching strategy containing “check”, “remote control platen” and other patterns is used. When the operation step does not conform to the device remote control syntax and does not contain the pre-defined prompt keyword, the parsing failure is automatically marked and the process is terminated. This fault-tolerant mechanism effectively guarantees the rigor of data analysis.

[0076] The present application realizes efficient structured processing of the text of the sequential control ticket by using a double-layer analysis mechanism driven by regular expressions. The first layer of analysis uses differentiated templates to accurately extract the interval name, source state and target state in the name of the sequential control ticket. The second layer of analysis processes primary device operations, platen operations and inspection-type auxiliary operations by using three regular matching rules, and uses verification methods such as equipment number extraction and matching with five-prevention remote signals and IED protection device association to ensure accurate analysis of the operation steps. The present application significantly improves the import efficiency of the sequential control ticket, reduces the error rate of manual intervention, guarantees the rigor of data analysis through the fault-tolerant mechanism, and effectively solves the problems of low efficiency, high error rate and lack of real-time performance in the traditional manual import method.

[0077] According to an embodiment of the present application, step S104 comprises:

[0078] Step S1042, match the data obtained by parsing the sequence control order name with the data in the monitoring database according to the first matching rule;

[0079] Step S1044, match the data obtained by parsing the sequence control order step name with the data in the monitoring database, and obtain the sequence control order step matching result.

[0080] Preferably, the first matching rule comprises: matching the interval name with the "alias" of the PMS interval object, and matching the interval source state and the interval target state with the state of the national grid interval, respectively.

[0081] Preferably, step S1044 comprises:

[0082] Comparing whether the number of operation steps is consistent; if not, obtaining the sequence control order step matching result as "step inconsistency", and ending the comparison; if yes, continuing to perform the comparison;

[0083] According to the second matching rule, comparing the step details, and obtaining the sequence control order step matching result;

[0084] The sequence control order step matching result further comprises: "step description inconsistency", "step type inconsistency", "step associated remote control point", and "pad point inconsistency".

[0085] Preferably, the second matching rule comprises: primary equipment name matching and protection soft pad name matching.

[0086] The primary equipment name matching comprises: (1) extracting the primary equipment dispatch number in the text and matching the primary equipment dispatch number with the "five-prevention remote signal" name; (2) if the matching fails, not extracting the primary equipment dispatch number, and matching the whole operation step with the "five-prevention remote signal" name again.

[0087] The protection soft pad name matching comprises: querying the IED protection LD or the SPG soft pad object under the public LD of the "protection device" added in the "protection device table" of the PMS interval object, obtaining the actual SPG soft pad name in the protection device, and matching the protection soft pad name with the actual SPG soft pad name in the protection device.

[0088] In the embodiment, in step S104, the data successfully parsed by step S102 is matched with the monitoring database to ensure the consistency of the sequence control order content and the actual equipment state. This process includes two core stages: first, macro data matching based on the sequence control order name, and then in-depth verification of the details of the operation step, forming a verification system from the whole to the part.

[0089] The first matching rule focuses on the verification of the sequence control ticket name analysis result. By associating and matching the interval name obtained through analysis with the "alias" of the PMS interval object, the mapping relationship between the operation object and the database entity is established. At the same time, the interval source state and the interval target state are compared with the national grid standard interval state to ensure that the operation instruction conforms to the power grid operation specification. This double-factor verification mechanism effectively guarantees the macro rationality of the operation instruction.

[0090] In the step detail content matching stage, a progressive comparison strategy is adopted. First, the consistency of the number of operation steps is checked, and if the number of steps does not match, the process is directly terminated and marked as "step inconsistency" error. When the number of steps is consistent, according to the second matching rule, a deep comparison is carried out: for a device operation, the device dispatching number (such as 2631) is extracted and matched with the five-prevention remote signal table, and if it fails, it is returned to the full-text fuzzy matching; for the press plate operation, the IED protection LD or the SPG soft press plate object name under the public LD is directly associated to ensure that the remote control object is consistent with the actual configuration of the protection device.

[0091] The matching mechanism adopts a multi-level fault-tolerant design. For example, in the device name matching, the precise matching of the digital number is preferred to improve the efficiency, and when the field naming is not standardized, it can automatically switch to the full-text matching mode. For the protection soft press plate, the actual SPG soft press plate name is obtained by querying the PMS protection device table, avoiding manual configuration errors. This hybrid matching strategy takes into account the verification rigor and field adaptability, significantly improving the success rate of sequence control ticket import.

[0092] The present application realizes the efficient and accurate connection of sequence control ticket data and monitoring system by constructing a regular-driven double-check matching mechanism. At the macro level, through interval name-PMS alias mapping and interval state-national grid standard state comparison, the semantic association between operation instruction and power grid model is established; at the micro level, a progressive step verification strategy is adopted, combining device number priority matching and full-text backup verification hybrid mode, which significantly improves the compatibility of non-standard expressions. In particular, the IED device level matching design for protection soft press plate effectively solves the naming ambiguity and configuration error problems existing in traditional manual import method, improves the success rate of sequence control ticket import, and shortens the single ticket processing time through automated process, providing a high-reliability data integration solution for power grid control system.

[0093] Embodiment two

[0094] Figure 2 The flow chart of the sequence control ticket text import method based on regular expression according to another embodiment of the present application; Figure 3 The principle diagram of the sequence control ticket text import method based on regular expression according to an embodiment of the present application. As shown in Figures 2-3As shown, according to one embodiment of the present invention, a method for importing control ticket text based on regular expressions includes the following steps:

[0095] Step S202: parse the text content of the control ticket to obtain the parsing result; the parsing result includes: parsing conclusion and parsed data;

[0096] Parsing conclusions include: parsing success or parsing failure;

[0097] Sequential control tickets are divided into primary and secondary operation tickets. Each type of operation ticket includes two parts: the name of the sequential control ticket and the steps of the sequential control ticket. During the parsing process, the primary and secondary operation tickets are parsed separately.

[0098] Step S202 specifically includes:

[0099] Step S2021: Parse the sequence control ticket name according to the first format template to obtain the interval name, interval source state, and interval target state;

[0100] The first format template is the preset syntax for parsing the name of the sequential control ticket;

[0101] The first format template of a one-time operation ticket includes: (1) "Convert XXX from YYY to ZZZ"; (2) "Convert XXX from YYY to ZZZ"; (3) "Convert XXX from YYY to ZZZ";

[0102] Where XXX represents the interval name, YYY represents the interval source state, and ZZZ represents the interval target state;

[0103] The first format template of the secondary operation ticket includes: "Start XXX protection", "Exit XXX protection", "Start XXX reclosing", "Exit XXX reclosing" ("XXX protection" is marked in red);

[0104] The first format template for parsing secondary operation tickets not only supports the 12 state descriptions specified by the State Grid, but also supports parsing "1 / 2+bus+State Grid equipment state name" into "main bus / auxiliary bus+State Grid equipment state";

[0105] For the name of the sequential control ticket that cannot be parsed using the first format template, the parsing conclusion is output as parsing failure.

[0106] Step S2022: If the parsing of the sequential control ticket name is successful, the sequential control ticket step name is parsed according to the second format template;

[0107] The second format template is a preset syntax for parsing the sequence ticket step name;

[0108] The second format template includes:

[0109] (1) For the sequence control ticket step name with the syntax of "open XXX", "disconnect XXX" and "close XXX", the operation item type is "one-time remote control", and the XXX one-time device name and the "five-protection remote signal" name are matched;

[0110] (2) For the sequence control ticket step name with the syntax of "put in XXX" and "exit XXX", the operation item type is "soft plate remote control", and the XXX secondary soft plate name and the SPG soft plate object name under the IED protection LD or public LD are matched (only the actual plate name is matched);

[0111] (3) For the sequence control ticket step name containing "(.*background.*)|(.*check.*)|(.*on-site.*)|(.*measurement.*)|(.*manual.*)|(.*reset.*)|(.*check$)|(.*remote control and plate closing$)", the operation item type is "prompt item (including hard plate)"; that is, the sequence control ticket step name containing "(.*background.*)|(.*check.*)|(.*on-site.*)|(.*measurement.*)|(.*manual.*)|(.*reset.*)|(.*check$)|(.*remote control and plate closing$)" is judged as a prompt item;

[0112] The sequence control ticket step name that does not meet the above three descriptions is output as a parsing failure.

[0113] Step S204, if the parsing conclusion is parsing success, the data obtained by parsing is matched with the data in the monitoring database; specifically including:

[0114] Step S2041, the data obtained by parsing the sequence control ticket name is matched with the data in the monitoring database according to the first matching rule;

[0115] The first matching rule includes: matching the interval name with the "alias" of the PMS interval object, and matching the interval source state and the interval target state with the state of the State Grid interval, respectively.

[0116] Step S2042, the data obtained by parsing the sequence control ticket step name is matched with the data in the monitoring database to obtain the sequence control ticket step matching result; including:

[0117] Step one, compare whether the number of operation steps is consistent; if not, return the "step inconsistency" sequence control ticket step matching result and end the comparison; if consistent, execute step two;

[0118] Step two, compare the step details according to the second matching rule, and return the sequence control ticket step matching result;

[0119] The sequence control ticket step matching result further includes: "step description inconsistency", "step type inconsistency", "step associated remote control point", and "platen point inconsistency", etc.

[0120] The second matching rule includes: primary equipment name matching and protection soft platen name matching; specifically,

[0121] The primary equipment name matching: (1) extracting the primary equipment dispatch number (a digital string, such as 2631) in the text and matching it with the "five-protection remote signal" name; (2) if the matching fails, the primary equipment dispatch number is not extracted, and the full operation step is matched with the "five-protection remote signal" name again (compatible with the similar "knife gate" naming in the field).

[0122] The protection soft platen name matching: querying the IED protection LD or the SPG soft platen object under the public LD of the "protection equipment" added in the "protection equipment table" of the PMS interval object, obtaining the actual SPG soft platen name in the protection device; and matching the protection soft platen name with the actual SPG soft platen name in the protection device.

[0123] In step S206, the instantiated electronic ticket obtained by the successful matching in step S204 is imported into the monitoring database of the monitoring system.

[0124] In the embodiment, the Excel format sequence control ticket is parsed; if the parsing is successful, the data, including the SCADA primary equipment, secondary equipment, remote control, platen, etc., is obtained from the monitoring database, the parsed data is matched with the interval and equipment of the monitoring database, that is, the parsed data is matched with the PMS interval object and the monitoring database equipment; if the matching is successful, the instantiated electronic ticket (in memory) is generated based on the matching result, and the instantiated electronic ticket is imported into the monitoring system to perform the write ticket operation on the monitoring database.

[0125] The application realizes the automatic parsing and standardized conversion of the sequence control ticket text through the regular expression driven structured parsing engine, wherein the dual-mode matching mechanism (primary / secondary operation ticket classification processing) combines the national grid specification expansion template, effectively covering the text parsing requirements in complex scenarios; the application significantly improves the matching accuracy of the sequence control ticket and the monitoring database; finally, through the error type positioning and the electronic ticket instantiation generation, the efficiency bottleneck of the traditional manual import method is solved, the intelligent parsing-verification-warehousing full-process automation of the dispatch operation ticket is realized, and a high-reliability data integration scheme is provided for the power grid control system.

[0126] Embodiment three

[0127] According to an embodiment of the application, a sequence control ticket text import method based on regular expressions comprises the following steps:

[0128] In step S302, the sequence control order text content is parsed; including parsing the sequence control order name, parsing the sequence control order step name;

[0129] Figure 4 The sequence control order text content of one embodiment of the present application is shown in the figure. Figure 4 For example, the parsing process is described as follows:

[0130] After obtaining the sequence control order text content, first, the sequence control order name in the "one-time part" of the "operation order description" is parsed. Taking the sequence control order name "change the long-lasting first line from operation to hot standby" as an example, the sequence control order name is parsed according to the first format template "change XXX from YYY to ZZZ", and the parsed result is obtained as follows:

[0131] The interval name is "long-lasting first line",

[0132] The interval source state is "operation",

[0133] The interval target state is "hot standby".

[0134] Then, the sequence control order step name under the sequence control order name is parsed.

[0135] Taking the sequence control order step name "pull open the long-lasting first line 5022 switch" as an example, according to the second format template "pull open XXX", the operation item type is "one-time remote control", and the one-time device name is matched with the "five-protection remote signal" name; after parsing the sequence control order step name, the following result is obtained:

[0136] The one-time device "long-lasting first line 5022 switch" is remotely controlled, and the action is "pull open".

[0137] Similarly, the content of the sequence control order step name "exit the long-lasting first line 5021 switch intelligent control cabinet 5021 remote control pressure plate" is parsed, according to the second format template "exit XXX", the operation item type is "pressure plate remote control", and the secondary soft pressure plate name is matched with the SPG soft pressure plate object name under the IED protection LD or public LD (only the actual pressure plate name is matched); after parsing the sequence control order step name, the following result is obtained:

[0138] The secondary device "long-lasting first line 5021 switch intelligent control cabinet 5021 remote control pressure plate" is remotely controlled, and the action is "exit".

[0139] Figure 5 The sequence control order text content of another embodiment of the present application is shown in the figure. Figure 5 For example, the parsing process is further described as follows:

[0140] The text content of the sequential control ticket is obtained. First, the sequential control ticket name is parsed. Taking the sequential control ticket name "change No. 2 main transformer from operation to hot standby" as an example, according to the first format template "change XXX from YYY to ZZZ", the parsed result is obtained as follows:

[0141] Interval name: "No. 2 main transformer",

[0142] Interval source state: "operation",

[0143] Interval target state: "hot standby".

[0144] Then, the sequential control ticket step name under the sequential control ticket name is parsed; and the sequential control ticket step name is obtained.

[0145] For the sequential control ticket step name "pull open No. 2 main transformer 302 switch", according to the format "pull open XXX", the operation item type is "one-time remote control", and the one-time device name and "five-protection remote signal" name are matched; the parsed result is obtained as follows:

[0146] The one-time device "No. 2 main transformer 302 switch" is remotely controlled, and the action is "pull open".

[0147] Similarly, the sequential control ticket step names "pull open No. 2 main transformer 202 switch" and "pull open No. 2 main transformer 5031 switch" are parsed respectively, and the parsed results are obtained as follows:

[0148] The one-time devices "No. 2 main transformer 302 switch" and "No. 2 main transformer 5031 switch" are remotely controlled, and the action is "pull open".

[0149] In step S304, the parsed sequential control ticket name is compared according to the first matching rule.

[0150] The first matching rule includes: finding "PMS interval" in the monitoring database, finding the corresponding sequential control interval object in the PMS interval according to the interval name obtained in step S302, then comparing the interval name with the alias of the sequential control interval object respectively to determine whether they match; if they match, the sequential control ticket name obtained by matching in the monitoring database is taken as the target sequential control ticket name; then the interval source state and the interval target state obtained in step S302 are compared with the State Grid interval state name in the monitoring database.

[0151] In step S306, the sequential control ticket steps are compared with the target sequential control ticket steps to obtain the sequential control ticket step matching result; wherein the target sequential control ticket steps are the sequential control ticket steps under the target sequential control ticket name.

[0152] Step S306 specifically includes:

[0153] The operation steps (i.e., the sequential control ticket steps) in the sequential control ticket text are compared with the corresponding operation steps (i.e., the target sequential control ticket steps) under the operation ticket.

[0154] Prior to comparing the number of operation steps;

[0155] If the number of steps is inconsistent, return the step control ticket step matching result of "step inconsistency" and end the comparison;

[0156] If the number of steps is consistent, compare the step details according to the second matching rule, and return the step control ticket step matching result;

[0157] The step control ticket step matching result includes error types, including: "step description inconsistency", "step type inconsistency", "step associated remote control point", and "pad point inconsistency", etc.

[0158] The second matching rule includes:

[0159] For primary equipment: (1) Extract the primary equipment dispatch number (a number string such as 2631) in the text and compare it with the "five-prevention remote signal" name to determine whether it matches; (2) If it does not match, do not extract the digital dispatch number, and use the full operation step and "five-prevention remote signal" name to match again (compatible with similar "knife gate" naming on site);

[0160] For the pad: match the protection soft pad name, the matching range is the "protection equipment" added in the "protection equipment table" of the PMS interval object, and only the soft pad name in the protection LD or public LD under the SPG soft pad object in the IED is matched. Actual soft pad name in the protection device.

[0161] Step S308, generate an instantiated electronic ticket according to the result obtained by the final matching success, and write the electronic ticket into the monitoring database of the monitoring system.

[0162] The application significantly improves the intelligent level of the sequence control ticket processing by constructing an automatic analysis and double-layer matching mechanism. In the analysis layer, the three elements of interval name, source state and target state in the sequence control ticket name are accurately extracted by using a formatted template, and the step name is automatically classified as a primary equipment remote control operation or a secondary pressure plate remote control operation through a device type identification mechanism, and a mapping relationship with the five-prevention remote signal name and the SPG soft pressure plate object is established to realize the structured analysis of the operation intention. In the matching layer, through the double comparison mechanism (name comparison + state comparison) between the interval name and the PMS interval object, combined with the multi-dimensional verification of the step level, including the step number consistency verification, the double matching of the equipment number and the five-prevention remote signal, and the SPG object matching of the protection soft pressure plate name, the matching result containing the error type positioning is finally output. The application effectively solves the problems of low efficiency, high error rate and lack of real-time in manual import of sequence control tickets, ensures the matching accuracy and abnormal diagnosis capability of the sequence control ticket and the monitoring database, realizes the automatic generation and real-time integration of the sequence control ticket, and provides reliable technical support for power grid dispatching operation.

[0163] Embodiment four

[0164] Figure 6 The figure is a schematic diagram of a sequence control ticket text import system based on regular expressions according to an embodiment of the application. As shown in the figure, according to an embodiment of the application, a sequence control ticket text import system based on regular expressions comprises: Figure 6

[0165] An analysis module 10 is configured to obtain sequence control ticket text content, analyze the sequence control ticket text content based on regular expressions, and obtain an analysis result.

[0166] A matching module 20 is configured to match the analysis result with data in a monitoring database if the analysis is successful.

[0167] A ticket writing module 30 is configured to import the instantiated electronic ticket obtained by successful matching into a monitoring database of a monitoring system.

[0168] ​In this embodiment, a regular expression-based sequence control ticket text import system is proposed, and the core architecture of the system is composed of an analysis module 10, a matching module 20 and a ticket writing module 30. The analysis module 10 performs structured analysis on the sequence control ticket text through a predefined regular expression template library, supports differentiated syntax matching of primary / secondary operation tickets, and extracts key elements such as interval name, device number and operation type; the matching module 20 adopts a double-factor verification mechanism, first verifies the rationality of the operation object through interval alias mapping and comparison with the State Grid, and then verifies the details of the steps through the combination of device number priority matching and full-text fuzzy matching; finally, the ticket writing module 30 automatically writes the verified instantiation electronic ticket into the monitoring database. Through the cooperative work of the regular engine and the database query, the system realizes the full-process automation from text analysis to data writing.

[0169] The present application significantly improves the efficiency and accuracy of sequence control ticket import, replaces traditional manual operation with regular expression-driven automated analysis, shortens the processing time of single ticket, improves the import success rate, and effectively reduces the operation risk caused by semantic ambiguity through the mixed matching strategy compatible with the field differentiated naming specification.

[0170] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

[0171] The above description is only the preferred embodiment of the present application and the explanation of the applied technical principles. Those skilled in the art should understand that the scope of the application involved in the present application is not limited to the technical solutions formed by the specific combination of the above technical features, and also covers other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept. For example, the above features are replaced with the technical features disclosed in the present application (but not limited to) having similar functions to form technical solutions.

[0172] It should be understood that the size of the serial number of the steps in the summary and the embodiments of the present application does not absolutely mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Claims

1. A method for importing control ticket text based on regular expressions, characterized in that: include: Obtain the text content of the order control ticket, parse the text content of the order control ticket based on a regular expression, and obtain the parsing result; If the analysis is successful, the analysis result is matched with the data in the monitoring database; The instantiated electronic ticket obtained by successful matching is imported into the monitoring database of the monitoring system.

2. The method for importing control ticket text based on regular expressions according to claim 1 is characterized in that: Sequential control tickets include primary operation tickets and secondary operation tickets; Each type of operation ticket includes the name of the control ticket and the steps of the control ticket; The analysis results include: analysis conclusions and data obtained from analysis; The analysis conclusions include: analysis success and analysis failure.

3. The method for importing control ticket text based on regular expressions according to claim 2 is characterized in that: Parsing the text content of the control ticket includes: Parse the sequence control ticket name according to the first format template to obtain the interval name, interval source state, and interval target state; if the sequence control ticket name cannot be parsed by the first format template, output the parsing conclusion as parsing failure; wherein the first format template is a preset grammar for parsing the sequence control ticket name; If the parsing of the sequence control ticket name is successful, the sequence control ticket step name is parsed according to the second format template; if the sequence control ticket step name cannot be parsed through the second format template, the parsing conclusion is output as parsing failure; wherein, the second format template is a preset syntax for parsing the sequence control ticket step name.

4. The method for importing control ticket text based on regular expressions according to claim 3 is characterized in that: The first format template of a one-time operation ticket includes: (1) "Convert XXX from YYY to ZZZ"; (2) "Convert XXX from YYY to ZZZ"; (3) "Convert XXX from YYY to ZZZ"; where XXX represents the interval name, YYY represents the interval source state, and ZZZ represents the interval target state; The first format template of the secondary operation ticket includes: "Enable XXX protection", "Exit XXX protection", "Enable XXX reclosing", and "Exit XXX reclosing".

5. The method for importing control ticket text based on regular expressions according to claim 3 is characterized in that: The second format template includes: (1) For the step names of the control ticket with the syntax of "open XXX", "disconnect XXX" and "close XXX", the operation item type is "primary remote control", and the name of the XXX primary device is matched with the name of the "five-defense remote signal"; (2) For the sequential control ticket step names with the syntax of "enter XXX" and "exit XXX", the operation item type is "press plate remote control", and the XXX secondary soft press plate name is matched with the SPG soft press plate object name under the IED protection LD or public LD; (3) For the step names of the control ticket that contain the syntax ".*Background.*", ".*Check.*", ".*On-site.*", ".*Measurement.*", ".*Manual.*", ".*Reset.*", ".*Check$", and ".*Remote Control Clamping Plate$", the operation item type is "Prompt Item"; For the ticket control step names that do not meet the above three descriptions, the parsing conclusion will be output as parsing failure.

6. The method for importing control ticket text based on regular expressions according to claim 1 is characterized in that: Matching the parsing result with the data in the monitoring database includes: Matching the data obtained by parsing the control ticket name with the data in the monitoring database according to the first matching rule; The data obtained by parsing the sequence control ticket step name is matched with the data in the monitoring database to obtain the sequence control ticket step matching result.

7. The method for importing control ticket text based on regular expressions according to claim 6 is characterized in that: The first matching rule includes: matching the interval name with the "alias" of the PMS interval object, and matching the interval source state and interval target state with the State Grid interval state respectively.

8. The method for importing control ticket text based on regular expressions according to claim 6 is characterized in that: Matching the data obtained by parsing the name of the control ticket step with the data in the monitoring database includes: Compare the number of operation steps to see if they are consistent. If not, obtain the step matching result of the control ticket as "Inconsistent Steps" and end the comparison. If they are consistent, continue the comparison. Compare the details of the step according to the second matching rule to obtain the matching result of the sequential control ticket step; Among them, the matching results of the sequential control ticket steps also include: "inconsistent step description", "inconsistent step type", "step associated remote control point" and "inconsistent pressure plate point".

9. The method for importing control ticket text based on regular expressions according to claim 8 is characterized in that: The second matching rule includes: a device name match and a protection soft pressure plate name match; The primary device name matching includes: (1) extracting the primary device dispatch number in the text and matching the primary device dispatch number with the name of "five-defense remote signaling"; (2) if the matching fails, not extracting the primary device dispatch number, and matching the entire operation steps with the name of "five-defense remote signaling" again; The protection soft pressure plate name matching includes: querying the SPG soft pressure plate object under the IED protection LD or public LD of the "protection device" added in the "protection device table" of the PMS interval object to obtain the actual SPG soft pressure plate name in the protection device; matching the protection soft pressure plate name with the actual SPG soft pressure plate name in the protection device.

10. A regular expression-based control ticket text import system, characterized in that: include: A parsing module is used to obtain the text content of the order control ticket, parse the text content of the order control ticket based on a regular expression, and obtain a parsing result; A matching module, for matching the analysis result with the data in the monitoring database if the analysis is successful; The ticket writing module is used to import the instantiated electronic ticket obtained by successful matching into the monitoring database of the monitoring system.

Images