Method for checking reasonability of operation logic of hydropower station

Abstract

The invention provides a hydropower station operation logic rationality checking method, which comprises the following steps of: 1, carding all standard operation tickets, and establishing label characteristics of the operation tickets; equipment names, operation types and equipment numbers in the operation ticket names are used as feature tags of the operation tickets, and a feature library of the operation tickets is established for all the operation tickets; 2, extracting the content of the operation order, and establishing event features of operation steps; 3, combining the tag features and the event features, and establishing a feature set of the operation order; step 4, cleaning the operation instructions of the hydropower station, extracting constraint features of equipment operation, and establishing a constraint set which includes operation order constraints and operation event constraints; and 5, performing logic rationality evaluation on the issued operation ticket by using the feature library and the constraint library of the operation ticket. Whether the operation logic of the operation order is reasonable or not can be automatically checked.

Description

Technical Field

[0001] The invention relates to the field of automatic operation of a hydropower station, and in particular to a method for checking the rationality of operation logic of a hydropower station. Background Art

[0002] The operation ticket is not only the basis for ensuring the safe operation of the power station, but also the key link to improve operation efficiency, standardize operation behavior, prevent accidents and fulfill legal responsibilities. The core of the operation ticket is the operation sequence of the equipment. The rationality test of the operation logic of the operation ticket can ensure the accuracy and completeness of the operation and avoid misoperation caused by errors in the operation ticket. The operation logic is mainly reflected in two aspects: operation sequence and operation conditions. The operation sequence refers to the operation steps between the equipment, that is, each operation task includes multiple operation equipment. When performing the operation task, the prescribed operation steps must be strictly followed, otherwise it will cause an accident. Operation conditions refer to each step of the operation can only be performed if the limited conditions are met, otherwise it cannot be performed or an accident will occur. Due to the large number of equipment in hydropower stations and the great differences in operation tickets, the current inspection of operation logic is mainly based on manual judgment based on experience, and there is a lack of automated inspection methods. Manual inspection requires high professional and technical capabilities and on-site operation experience of employees, and is prone to misjudgment. Summary of the invention

[0003] The present invention starts from two aspects, operation logic and operation conditions, and proposes an automated operation logic rationality checking method by analyzing and refining the common characteristics of operation logic and operation conditions, which can automatically check whether the operation logic of the operation ticket is reasonable.

[0004] The present invention provides a method for checking the rationality of the operation logic of a hydropower station, which can automatically check the operation logic from two aspects: operation conditions and operation sequence. Specifically, it comprises the following steps:

[0005] Step 1: Sort out all standard operation tickets and establish label features for the operation tickets.

[0006] The equipment name, operation type, and equipment number in the operation ticket name are used as feature tags of the operation ticket, and a feature library of operation tickets is established for all operation tickets.

[0007] S1.1. The equipment name is the task object of the operation ticket, and is also the equipment mentioned in the operation ticket name (operation ticket equipment), including: circuit breaker, disconnector, main transformer, busbar, line, technical water supply pump, etc.;

[0008] S1.2, Equipment number is the number of the task object;

[0009] S1.3. Operation type refers to the operation status in the operation ticket, including: maintenance, hot standby, cold standby, etc.

[0010] Step 2: Extract the operation ticket content and establish the event characteristics of the operation steps.

[0011] S2.1. Treat each step of the operation ticket as an independent operation event, use the operation type, equipment name, equipment number, and operation method as feature tags, and establish a feature library of operation events for all operation tickets.

[0012] S2.2, Operation type refers to the mode of operation, including: closing, disconnecting, starting, stopping, etc.;

[0013] The equipment name is the equipment mentioned in the operation steps (operation event equipment), including: circuit breaker, disconnector, ground knife, pressure plate, button, etc.;

[0014] S2.3. Equipment number refers to the number of the task operation event equipment.

[0015] Step 3: Merge label features and event features to create a feature set for the operation ticket.

[0016] S3.1. Express the operation ticket model as a set of label features, event features and constraint features. Merge the two types of features. The operation ticket model can be expressed as: model = (device feature set, number feature set, operation feature set), equipment feature set = (operation ticket device name, operation event device 1 name, ..., operation event device n name), number feature set = (operation ticket device number, operation event device 1 number, ..., operation event device n number), operation feature set = (operation ticket operation type, operation event 1 operation type, ..., operation event n operation type).

[0017] S3.2. Clean up the standard operation tickets of the hydropower station, assign values ​​to the model according to the contents of the operation tickets, establish feature sets for standard tickets, collect all feature sets, and form a feature library for operation tickets.

[0018] Step 4: Clean up the operating procedures of the hydropower station, extract the constraint features of equipment operation, and establish a constraint set. The constraint set includes operation ticket constraints and operation event constraints, which can be described as:

[0019] S4.1. Constraint set = (status constraint set (operation ticket status constraint, operation event status constraint), logic constraint set of operation event (name of logical device, type of logical device), locking constraint set of operation event (name of locking device, type of locking device)).

[0020] S4.2, the state constraint set is the working state that the operation ticket equipment and the operation event equipment must have to complete the corresponding operation. The operation ticket state constraint corresponds to the operation type in step 1. The operation ticket can only be executed when the working state of the equipment is different from the operation type of the operation ticket in step 1, otherwise it cannot be executed. The operation event can only be implemented when the operation event state constraint matches the operation type of the operation event in step 2, otherwise it cannot be implemented.

[0021] S4.3. The logical constraint set of the operation event is the logical device of the operation event. This operation event can only be executed when the logical device is put into operation, including the device name and device type.

[0022] S4.4. The locking constraint of the operation event is the locking device of the operation event. This time can only be executed when the locking device status is not in the state of investment, including the device name and device type.

[0023] S4.5. Establish the constraint set of standard tickets and clean up the constraint sets of all standard tickets to form a constraint library.

[0024] Step 5: Use the feature library and constraint library of the operation ticket to evaluate the logical rationality of the issued operation ticket.

[0025] S5.1. Extract the feature set of the opened operation ticket according to steps 1, 2 and 3.

[0026] S5.2. Obtain the corresponding standard ticket in the feature library according to the label features, and extract the feature set and constraint set of the standard ticket.

[0027] S5.3, then compare the equipment features, number features and operation features respectively. When the three sets of feature text descriptions and sequences are exactly the same, the features of the issued operation ticket meet the requirements and go to step S5.4, otherwise go to step S5.3.1.

[0028] S5.3.1. Compare the feature description of the operation ticket with the feature description of the standard ticket. If there is only one feature description that is different or the order is different, the operation logic is unreasonable.

[0029] S5.3.2. The number of operation ticket features is greater than the number of standard ticket features, and the operation logic is unreasonable.

[0030] S5.3.3. The number of operation ticket features is less than the number of standard ticket features, and the operation logic is unreasonable.

[0031] S5.4. Check the constraint sets of the operation events one by one in the order of the operation steps, and compare the state constraint set, logic constraint set and locking constraint set respectively. If the constraint sets of all events are the same as the constraint sets of the standard events, the operation logic is reasonable; otherwise, the operation logic is unreasonable. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 The figure is a flow chart of rationality evaluation of the present invention. DETAILED DESCRIPTION

[0033] Take a circuit breaker maintenance operation ticket as an example to explain how to perform operation logic rationality detection. If the circuit breaker is operated to the maintenance state, 5 steps are required.

[0034] Step 1: Sort out all standard operation tickets and establish label features for the operation tickets.

[0035] The equipment name, operation type, and equipment number in the operation ticket name are used as feature tags of the operation ticket, and a feature library of operation tickets is established for all operation tickets.

[0036] S1.1. The equipment name is the task object of the operation ticket, and is also the equipment mentioned in the operation ticket name (operation ticket equipment), including: circuit breaker, disconnector, main transformer, busbar, line, technical water supply pump, etc.;

[0037] S1.2, Equipment number is the number of the task object;

[0038] S1.3. Operation type refers to the operation status in the operation ticket, including: maintenance, hot standby, cold standby, etc.

[0039] The operation type in this case is: maintenance; the operation device is: circuit breaker; the device number is the circuit breaker number.

[0040] Step 2: Extract the operation ticket content and establish the event characteristics of the operation steps.

[0041] S2.1. Treat each step of the operation ticket as an independent operation event, use the operation type, equipment name, equipment number, and operation method as feature tags, and establish a feature library of operation events for all operation tickets.

[0042] S2.2, Operation type refers to the mode of operation, including: closing, disconnecting, starting, stopping, etc.;

[0043] The equipment name is the equipment mentioned in the operation steps (operation event equipment), including: circuit breaker, disconnector, ground knife, pressure plate, button, etc.;

[0044] S2.3. Equipment number refers to the number of the task operation event equipment.

[0045] In this case, the circuit breaker maintenance includes 5 events: ① disconnect the circuit breaker, ② disconnect the line disconnector, ③ disconnect the busbar side disconnector, ④ close the upper grounding switch of the circuit breaker, and ⑤ close the lower grounding switch of the circuit breaker.

[0046] Step 3: Merge label features and event features to create a feature set for the operation ticket.

[0047] S3.1. Express the operation ticket model as a set of label features, event features and constraint features. Merge the two types of features. The operation ticket model can be expressed as: model = (device feature set, number feature set, operation feature set), equipment feature set = (operation ticket device name, operation event device 1 name, ..., operation event device n name), number feature set = (operation ticket device number, operation event device 1 number, ..., operation event device n number), operation feature set = (operation ticket operation type, operation event 1 operation type, ..., operation event n operation type).

[0048] The characteristic set of the circuit breaker in this example can be written as

[0049] Equipment feature set = (circuit breaker, circuit breaker, disconnector, disconnector, earthing switch, earthing switch)

[0050] Number feature set = (circuit breaker number, circuit breaker number, outgoing disconnect switch number, power disconnect switch number, upper grounding switch number, lower grounding switch number)

[0051] Operational characteristics = (inspection, disconnect, disconnect, disconnect, close, close).

[0052] S3.2. Clean up the standard operation tickets of the hydropower station, assign values ​​to the model according to the contents of the operation tickets, establish feature sets for standard tickets, collect all feature sets, and form a feature library for operation tickets.

[0053] Step 4: Clean up the operating procedures of the hydropower station, extract the constraint features of equipment operation, and establish a constraint set. The constraint set includes operation ticket constraints and operation event constraints, which can be described as:

[0054] S4.1 constraint set = (status constraint set (operation ticket status constraint, operation event status constraint), logic constraint set of operation event (name of logical device, type of logical device), locking constraint set of operation event (name of locking device, type of locking device)).

[0055] S4.2, the state constraint set is the working state that the operation ticket equipment and the operation event equipment must have to complete the corresponding operation. The operation ticket state constraint corresponds to the operation type in step 1. The operation ticket can only be executed when the working state of the equipment is different from the operation type of the operation ticket in step 1, otherwise it cannot be executed. The operation event can only be implemented when the operation event state constraint matches the operation type of the operation event in step 2, otherwise it cannot be implemented.

[0056] ① The state constraint set of this case includes the state constraint of the circuit breaker and the state constraints of the five operation steps in the operation ticket, as follows:

[0057] Operation ticket: non-maintenance,

[0058] Operation event 1: Close,

[0059] Operation event 2: Close,

[0060] Operation event three: disconnect,

[0061] Operation event 4: disconnect,

[0062] S4.3. The logical constraint set of the operation event is the logical device of the operation event. This operation event can only be executed when the logical device is put into operation, including the device name and device type.

[0063] ②Logical constraint set of operation events:

[0064] Operation event 1: Control power switch of the circuit breaker, switch number.

[0065] Operation event 2: Control power switch of the outgoing line isolating switch, switch number.

[0066] Operation event three: Control power switch of busbar disconnector, switch number.

[0067] Operation event four: Control power switch of upper grounding switch, switch number.

[0068] Operation event None: Control power switch of lower side grounding switch, switch number.

[0069] S4.4. The locking constraint of the operation event is the locking device of the operation event. This time can only be executed when the locking device status is not in the state of investment, including the device name and device type.

[0070] ③ Locking constraint set of operation events:

[0071] Operation event 1: Outgoing line disconnector, switch number; busbar disconnector, switch number.

[0072] Operation event 2: circuit breaker, circuit breaker number.

[0073] Operation event three: circuit breaker, circuit breaker number; outgoing line disconnector, switch number.

[0074] Operation event four: circuit breaker, circuit breaker number; outgoing line disconnector, switch number; busbar disconnector, switch number.

[0075] Operation event five: circuit breaker, circuit breaker number; outgoing line disconnector, switch number; busbar disconnector, switch number.

[0076] S4.5. Establish the constraint set of standard tickets and clean up the constraint sets of all standard tickets to form a constraint library.

[0077] Step 5: Use the feature library and constraint library of the operation ticket to evaluate the logical rationality of the issued operation ticket.

[0078] S5.1. Extract the feature set of the opened operation ticket according to steps 1, 2 and 3.

[0079] S5.2. Obtain the corresponding standard ticket in the feature library according to the label features, and extract the feature set and constraint set of the standard ticket.

[0080] S5.3, then compare the equipment features, number features and operation features respectively. When the three sets of feature text descriptions and sequences are exactly the same, the features of the issued operation ticket meet the requirements and go to step S5.4, otherwise go to step S5.3.1.

[0081] S5.3.1. Compare the feature description of the operation ticket with the feature description of the standard ticket. If there is only one feature description that is different or the order is different, the operation logic is unreasonable.

[0082] S5.3.2. The number of operation ticket features is greater than the number of standard ticket features, and the operation logic is unreasonable.

[0083] S5.3.3. If the number of operation ticket features is less than the number of standard ticket features, but the feature description of the operation ticket is consistent with that on the standard ticket, proceed to S5.4.

[0084] S5.4. Check the constraint sets of the operation events one by one in the order of the operation steps, and compare the state constraint set, logic constraint set and locking constraint set respectively. If the constraint sets of all events are the same as the constraint sets of the standard events, the operation logic is reasonable; otherwise, the operation logic is unreasonable.

[0085] If the issued operation ticket has the same characteristic values ​​and constraint values ​​as the standard ticket, S5.4 can determine that the ticket is issued correctly.

[0086] If the issued operation ticket has the same number of features as the standard ticket, but the feature descriptions are different, S5.3.1 can be used to determine that the logic is incorrect.

[0087] If the number of characteristic operation tickets issued is greater than the number of standard tickets, S5.3.2 can be used to determine that the logic is incorrect.

[0088] If the number of characteristics of the issued operation ticket is less than the number of standard tickets, S5.3.3 can be used to determine that the logic is incorrect.

[0089] If the issued operation ticket has the same number of features and the same feature description as the standard ticket, if one of the state constraints, logic constraints, and blocking constraints has a different value, the logic is incorrect.

Claims

1. A method for checking the rationality of the operation logic of a hydropower station, characterized in that: The following steps are involved: Step 1: Sort out all standard operation tickets and establish label features for the operation tickets; The equipment name, operation type, and equipment number in the operation ticket name are used as feature tags of the operation ticket, and a feature library of operation tickets is established for all operation tickets; Step 2: Extract the operation ticket content and establish the event features of the operation steps; Step 3: Merge label features and event features to create a feature set for the operation ticket; Step 4: Clean up the operating procedures of the hydropower station, extract the constraint features of equipment operation, and establish a constraint set, which includes operation ticket constraints and operation event constraints; Step 5: Use the feature library and constraint library of the operation ticket to evaluate the logical rationality of the issued operation ticket.

2. A method for checking the rationality of operation logic of a hydropower station according to claim 1, characterized in that: In step 1, the equipment name is the task object of the operation ticket and the equipment mentioned in the operation ticket name, including: circuit breaker, disconnector, main transformer, busbar, line, technical water supply pump; The device number is the number of the task object; The operation type is the operation status in the operation ticket, including: maintenance, hot standby, and cold standby.

3. A method for checking the rationality of operation logic of a hydropower station according to claim 1, characterized in that: In step 2, each step of the operation ticket is regarded as an independent operation event, and the operation type, equipment name, equipment number, and operation mode are used as feature tags to establish a feature library of operation events for all operation tickets; Operation type refers to the mode of operation, including: close, disconnect, start, stop; The equipment names are the equipment mentioned in the operation steps, including: circuit breaker, disconnector, ground knife, pressure plate, button; The device number refers to the number of the task operation event device.

4. A method for checking the rationality of operation logic of a hydropower station according to claim 1, characterized in that: Step 3 specifically includes the following sub-steps: S3.

1. The operation ticket model is expressed as a collection of label features, event features, and constraint features. The two types of features are merged and the operation ticket model is expressed as: Model = (equipment feature set, number feature set, operation feature set); Equipment feature set = (operation ticket equipment name, operation event equipment 1 name, ..., operation event equipment n name); Number feature set = (operation ticket device number, operation event device 1 number, ..., operation event device n number); Operation feature set = (operation ticket operation type, operation event 1 operation type, ..., operation event n operation type); S3.

2. Clean up the standard operation tickets of the hydropower station, assign values ​​to the model according to the contents of the operation tickets, establish feature sets for standard tickets, collect all feature sets, and form a feature library for operation tickets.

5. A method for checking the rationality of operation logic of a hydropower station according to claim 1, characterized in that: In step 4: Constraint set = (state constraint set (operation ticket state constraint, operation event state constraint), logic constraint set of operation event (name of logical device, type of logical device), locking constraint set of operation event (name of locking device, type of locking device)); The state constraint set is the working state that the operation ticket equipment and operation event equipment must have to complete the corresponding operation. The operation ticket state constraint corresponds to the operation type in step 1. The operation ticket can only be executed when the working state of the equipment is different from the operation type of the operation ticket in step 1, otherwise it cannot be executed; the operation event can only be implemented when the operation event state constraint matches the operation type of the operation event in step 2, otherwise it cannot be implemented; The logical constraint set of an operation event is the logical device of the operation event. This operation event can only be executed when the logical device is put into operation, including the device name and device type. The blocking constraint of an operation event is the blocking device of the operation event. This time can only be executed when the blocking device is not in the state of being thrown, including the device name and device type; Establish the constraint set of standard tickets, and clean up the constraint sets of all standard tickets to form a constraint library.

6. A method for checking the rationality of operation logic of a hydropower station according to claim 1, characterized in that: Step 5 specifically includes the following sub-steps: S5.

1. Extract the feature set of the opened operation ticket according to step 1, step 2 and step 3; S5.

2. Obtain the corresponding standard ticket in the feature library according to the label feature, and extract the feature set and constraint set of the standard ticket; S5.3, then compare the equipment features, number features and operation features respectively. If the three sets of feature text descriptions and sequences are exactly the same, the features of the issued operation ticket meet the requirements and go to step S5.4, otherwise go to step S5.3.1; S5.3.

1. If the feature description of the operation ticket is different from that of the standard ticket, or the order is different, the operation logic is unreasonable; S5.3.

2. The number of operation ticket features is greater than the number of standard ticket features, and the operation logic is unreasonable; S5.3.3, the number of operation ticket features is less than the number of standard ticket features, and the operation logic is unreasonable; S5.

4. Check the constraint sets of the operation events one by one in the order of the operation steps, and compare the state constraint set, logic constraint set and locking constraint set respectively. If the constraint sets of all events are the same as the constraint sets of the standard events, the operation logic is reasonable; otherwise, the operation logic is unreasonable.

Images