Method and system for automatically importing and distributing project rule numbers for planar graph verification

Abstract

The invention discloses a method and a system for automatically importing and distributing project rule numbers for planar graph verification. The method comprises the following steps: generating a rule distribution table according to system configuration rules of a system configuration rule file; and creating a verification report template, importing the platform rule number in the platform document into the verification report template, and generating an intermediate record form. Importing project rule numbers in the rule distribution table into corresponding positions in the middle record form; and screening and marking the project rule number distributed to the'plane graph 'in the middle record form to obtain a final record form. Creating a sub-table group; and importing the project rule number distributed to the plane graph into a corresponding sub-table according to whether the project rule number distributed to the plane graph in the final recording form records a function of a corresponding platform rule number in a platform document, so as to obtain different function forms of the plane graph verification project. The method and the system have the characteristics of short time consumption, high efficiency and high accuracy.

Description

Technical Field

[0001] This invention relates to the field of rail transit technology, and more specifically to a method and system for automatically importing and assigning project rule numbers for plan verification. Background Technology

[0002] In the signaling system of urban rail projects, it is necessary to verify the plan according to the system configuration rules (i.e., project rule number) and fill the verification results of each rule into the verification report template to finally form a verification report.

[0003] The traditional method involves manually copying and pasting system configuration rules one by one into the verification report template. Since this involves thousands of rules and a large amount of data, manual work is inefficient, and errors and omissions are common during the copy-paste process, making it difficult to guarantee completeness and accuracy. Summary of the Invention

[0004] The purpose of this invention is to improve a method and system for automatically importing and assigning project rule numbers for floor plan verification. This method is characterized by short processing time and high efficiency, and overcomes the problem of easily finding or missing rules when searching manually, thus achieving high accuracy.

[0005] To achieve the above objectives, the present invention provides a method for automatically importing and assigning project rule numbers for floor plan verification, comprising: The rule allocation table generation module extracts system configuration rules from the "system configuration rule file" that records system configuration rules to generate a "rule allocation table"; wherein, the system configuration rules include: platform rule number, project rule number, the allocation object and type of project rule number, and the correspondence between platform rule number and project rule number; The template creation module creates a "Verification Report Template" and imports all platform rule numbers from the "Platform Documentation" into the "Verification Report Template" to generate an intermediate record form; the "Platform Documentation" is used to record platform rule numbers and platform rule number functions; The import rules module imports the project rule numbers from the "Rule Allocation Table" into the corresponding positions in the intermediate record form based on the type of project rule number, the correspondence between platform rule number and project rule number. The import rules module filters and marks the project rule numbers assigned to the "Floor Plan" in the intermediate record form based on the allocation objects of the project rule numbers in the "Rule Allocation Table" to obtain the final record form; The sub-table generation module creates a sub-table group; the sub-table group includes a remarks sub-table and multiple record sub-tables; the multiple record sub-tables correspond to the functions of the platform rule numbers in the "Platform Documentation", and the remarks sub-table corresponds to the functions of platform rule numbers not recorded in the "Platform Documentation"; and according to whether the project rule number assigned to the "Floor Plan" in the final record form is recorded in the "Platform Documentation", the project rule number assigned to the "Floor Plan" is imported into the corresponding sub-table to obtain different function forms for the floor plan verification project.

[0006] Optionally, the project rule number includes: a specific project rule number and a general project rule number; wherein, the specific project rule number cannot be found in the "Rule Allocation Table" and the function of the corresponding platform rule number is not recorded in the "Platform Documentation"; the general project rule number can be found in the "Rule Allocation Table" and the function of the corresponding platform rule number is recorded in the "Platform Documentation". The methods for creating a "Verification Report Template" using the template creation module include: Create a worksheet form, which includes: platform rule number, project rule number, floor plan verification item with "floor plan" as the assigned object, and content items, and complete the creation of the "verification report template"; Based on the function of the platform rule number in the "Platform Documentation", the "Content Entries" column is divided into multiple record sub-columns and one remarks sub-column; Among them, the remarks sub-column corresponds to the functions of platform rule numbers not recorded in the "platform documentation"; The multiple record sub-columns are divided according to the function of the platform rule number in the "Platform Documentation", with each record sub-column corresponding to the function of a platform rule number in the "Platform Documentation".

[0007] Alternatively, the method of creating a "verification report template" through the template creation module also includes: The template creation module divides the "Verification Report Template" into multiple general rule sections and one specific rule section based on the function of the system-assigned rules in the "Platform Documentation" and the type of the project rule number; Based on the functions of the system allocation rules in the "Platform Documentation", the "Verification Report Template" is divided into multiple general rule parts, with each general rule part corresponding to the function of a system allocation rule. The specific rule section is used to mark the rule number of a specific project.

[0008] Optionally, the method for generating intermediate record forms by importing platform rule numbers from the "Platform Documentation" into the "Verification Report Template" through a template creation module includes: Based on the function of the platform rule number in the "Platform Documentation", fill in each platform rule number in the "Platform Documentation" into the corresponding general rule section to obtain the intermediate record form.

[0009] Optionally, the method for importing the project rule number from the "Rule Allocation Table" file into the corresponding position in the intermediate record form based on the correspondence between the platform rule number and the project rule number in the "Rule Allocation Table" includes: The import rule module iterates through the types of project rule numbers recorded in the rule allocation table to determine whether the project rule number is a specific project rule number. When it is a specific project rule number, fill in the project rule number in the position where there is no corresponding platform rule number in the intermediate record form; When it is not a specific project rule number, the import rule module compares the platform rule number corresponding to the project rule number in the rule allocation table with the platform rule number in the intermediate record form. If the platform rule number in the rule allocation table matches the one in the intermediate record form, then fill in the rule number of that project in the intermediate record form at the position corresponding to the platform rule number. If the platform rule number in the rule allocation table is inconsistent with that in the intermediate record form, no operation will be performed.

[0010] Optionally, methods for filtering and marking the project rule numbers assigned to the "Floor Plan" in the intermediate record form to obtain the final record form include: The import rule module iterates through the allocation objects of the project rule number and determines whether the allocation object of the project rule number in the "rule allocation table" is "floor plan" in order to obtain the final record form. When the project rule number in the rule assignment table is assigned to the "floor plan" object, then mark the project rule number in the intermediate record form; If the project rule number in the rule assignment table is not assigned to a "floor plan" object, no operation will be performed.

[0011] Optionally, before importing the project rule number from the "Rule Assignment Table" into the intermediate record form, the template creation module marks the function of each platform rule number in the "Platform Document" in the "Content Entries" of the intermediate record form according to the function of each platform rule number in the "Platform Document"; and marks the positions in the remarks sub-column of the "Content Entries" that do not correspond to the platform rule number, so as to mark the sub-column in the "Content Entries" corresponding to the specific project rule number; During the process of importing the project rule number assigned to "Floor Plan" into the corresponding sub-table in the sub-table generation module, the project rule number is filled into the sub-table corresponding to "Content Item" according to the mark in the sub-column of "Content Item" to obtain different functional forms for floor plan verification projects.

[0012] In addition, the present invention also provides a system for automatically importing and assigning project rule numbers for floor plan verification, comprising: The rule allocation table generation module receives the "system configuration rule file", extracts system configuration rules from the "system configuration rule file", and then imports the system configuration rules into the "rule allocation table". The template creation module receives the "Platform Document" and creates a "Verification Report Template" that includes the project rule number, platform rule number, project rule number allocation object, and content items. The template creation module imports all platform rule numbers recorded in the "Platform Document" into the "Verification Report Template" to obtain an intermediate record form. The import rules module receives the intermediate record form generated by the template creation module; the import rules module receives the "rule allocation table" file from the rule allocation table generation module; the import rules module imports the project rule numbers in the "rule allocation table" into the intermediate record form according to the type of project rule number, the correspondence between platform rule number and project rule number in the "rule allocation table"; the import rules module filters out the project rule numbers assigned to the "floor plan" according to the "allocation object" in the "rule allocation table" file, and marks the platform rule number in the intermediate record form to obtain the final record form; The sub-table generation module receives the final record form generated by the import rule module; the sub-table generation module establishes a sub-table group including a remarks sub-table and multiple record sub-tables; and the multiple record sub-tables correspond to the functions of the platform rule numbers in the "Platform Document", while the remarks sub-table corresponds to the functions of platform rule numbers not recorded in the "Platform Document"; the sub-table generation module imports the project rule numbers assigned to the "Floor Plan" into the corresponding sub-tables according to whether the project rule numbers in the final record form are recorded in the "Platform Document", thereby obtaining different function forms for the floor plan verification project.

[0013] Optionally, during the process of importing the project rule number assigned to the "Floor Plan" into the corresponding sub-table, the template creation module divides the "Content Item" into multiple record sub-columns and one remarks sub-column according to the function of the platform rule number in the "Platform Document"; the remarks sub-column corresponds to the function of the platform rule number not recorded in the "Platform Document"; the multiple record sub-columns respectively correspond to the function of the platform rule number in the "Platform Document"; Furthermore, the template creation module marks the function of each platform rule number in the "Platform Document" in the "Content Items" of the intermediate form according to the function of each platform rule number in the "Platform Document"; and marks the positions in the "Content Items" notes that do not correspond to platform rule numbers, so as to mark the sub-column in the "Content Items" corresponding to specific project rule numbers; The sub-table generation module fills in the project rule number into the sub-table corresponding to the "Content Item" sub-column according to the mark of the project rule number in the corresponding sub-column of "Content Item" to obtain different functional forms for the floor plan verification project.

[0014] Optionally, after dividing the content items into multiple sub-columns, the template creation module divides the "Verification Report Template" into a specific rule section and multiple general rule sections according to the function of the platform rule number and the type of the project rule number in the "Platform Documentation". The specific rule section is used to store the rule number of a specific project; the multiple general rule sections each correspond to the function of a platform rule number in the "platform document" to store the platform rule number and project rule number corresponding to the function of that platform rule number.

[0015] Compared with the prior art, the technical solution of the present invention has at least the following beneficial effects: The method described in this invention overcomes the problem of easily finding or missing rules during manual searching by automatically traversing the rule allocation table, thus achieving high accuracy. By automatically filling the item rule numbers from the rule allocation table into the "Applicable Rules" template and marking the item rule numbers assigned to the floor plan, and simultaneously automatically filling these marked item rule numbers into each sub-table according to the functional module (i.e., the sub-column names of the "Items" column), the method of this invention is characterized by its short processing time and high efficiency.

[0016] The method described in this invention is applicable to the initial plan design verification and subsequent regression verification, and has strong usability; at the same time, it provides a reference for the automation of the design verification of subway signaling systems. Attached Figure Description

[0017] Figure 1 This is a flowchart of the method for automatically importing and assigning project rule numbers for floor plan verification according to the present invention.

[0018] Figure 2 This is a schematic diagram of the rule allocation table.

[0019] Figure 3 A diagram illustrating the configuration rules file for the system.

[0020] Figure 4This is a schematic diagram of the "verification report template" for the method of automatically importing and assigning project rule numbers for floor plan verification according to the present invention.

[0021] Figure 5 This is a schematic diagram of a sub-table for the method of automatically importing and assigning project rule numbers for floor plan verification according to the present invention. Detailed Implementation

[0022] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0023] In the description of this invention, it should be noted that the terms "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0024] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal communication between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0025] This invention provides a system for automatically importing and assigning project rule numbers for floor plan verification. The system imports the "system configuration rule file" into the "rule assignment table", and then imports the project rule numbers for different floor plan verification projects into the "verification report template (APPLICABLE RULES)" according to the "platform document" and the "rule assignment table", and then assigns them to different functional forms of the floor plan verification project.

[0026] Among them, such as Figure 2As shown, the "System Configuration Rules File" records system configuration rules, which include: platform rule number, project rule number, the allocation object of the project rule number, the type of project rule number, and the correspondence between platform rule number and project rule number. The type of project rule number includes: specific project rule number and general project rule number. Specifically, the specific project rule number cannot be found in the "Rule Allocation Table" and its function is not recorded in the "Platform Documentation." The general project rule number can be found in the "Rule Allocation Table" and its function is recorded in the "Platform Documentation."

[0027] like Figure 3 As shown, the "rule allocation table" is obtained through the system configuration rules in the "system configuration rule file" and serves as a tabular representation of the "system configuration rule file".

[0028] The "Platform Documentation" includes platform rule numbers and their corresponding functions. The sections of the "Platform Documentation" categorize platform rule numbers according to their functions, recording the usage rules for each rule number.

[0029] Specifically, the system described in this invention includes: a rule allocation table generation module, a template creation module, a rule import module, and a sub-table generation module.

[0030] The rule assignment table generation module can input a "system configuration rule file" in Word format (e.g., ...). Figure 3 As shown), and extract system configuration rules from the "System Configuration Rules File", and then import the system configuration rules into the "Rule Assignment Table" in EXCEL format (e.g. Figure 2 (as shown in the image)

[0031] The template creation module allows input of a "Platform Document" containing platform rule numbers and their associated functions, and creates "Validation Report Templates (APPLICABLE RULES)". These "Validation Report Templates (APPLICABLE RULES)" must include: project rule number, platform rule number, the assigned object of the project rule number, and content entries for recording the functions of the platform rule number. The template creation module divides these "content entries" into multiple record sub-columns and one notes sub-column (Other). The record sub-columns are divided according to the functions of the platform rule numbers recorded in the "Platform Document" (i.e., the chapter names of the "Platform Document"), marking the functions of each project rule number as recorded in the "Platform Document". Each record sub-column is named after or an abbreviation of the chapter name of the "Platform Document". The notes sub-column (Other) corresponds to functions of platform rule numbers not recorded in the "Platform Document", used to mark project rule numbers for functions not recorded in the "Platform Document", i.e., marking specific project rule numbers. This division of content entries facilitates the generation of different function forms for the floor plan validation project, enabling different tests for project rule numbers corresponding to functions of different platform rule numbers. The template creation module can import all platform rule numbers recorded in the "Platform Documents" into the "Platform Rule Number" column of the "Verification Report Template (APPLICABLERULES)" to obtain an intermediate record form.

[0032] In a preferred embodiment, to enhance the readability of the "Applicable Rules" templates, the template creation module, after dividing the content items into multiple sub-columns, can horizontally divide the "Applicable Rules" templates into a specific rule section and multiple general rule sections based on the function of the platform rule number (i.e., the chapter name of the "Platform Document") and the type of the project rule number (see...). Figure 4 The specific rule section stores specific project rule numbers; multiple general rule sections correspond to the functions of platform rule numbers in the "Platform Documentation" (i.e., the chapter names of the "Platform Documentation"), storing the platform rule number and project rule number corresponding to the function of that platform rule number; and the general rule sections use the chapter names of the "Platform Documentation" to name the corresponding parts. Then, the template creation module can import all platform rule numbers recorded in the "Platform Documentation" according to their corresponding platform rule number functions into the corresponding general rule section of the "Platform Rule Number" column in the "Applicable Rules" of the "Verification Report Template," obtaining an intermediate record form. At this time, platform rule numbers with the same function are arranged together, making it convenient for operators to find the platform rule number with the corresponding function in the "Applicable Rules" of the "Verification Report Template" by the name of each section.

[0033] Furthermore, the template creation module can mark the function of each platform rule number in the "Platform Document" in the intermediate record form according to the function of each platform rule number in the "Platform Document," that is, mark it in the corresponding sub-column of the "Content Item" in the intermediate record form. Furthermore, it marks the positions in the remarks sub-column where there is no corresponding platform rule number (i.e., the "Platform Rule Number" column is blank), to mark the sub-column (i.e., the remarks sub-column) of the "Content Item" corresponding to a specific project rule number.

[0034] The import rules module can receive the intermediate record form generated by the template creation module. The import rules module can also receive the "rule allocation table" file generated by the rule allocation table generation module. Based on the type of project rule number, the correspondence between platform rule number and project rule number in the "rule allocation table" file, the import rules module imports the project rule numbers from the "rule allocation table" file into the intermediate record form. Specifically, for general project rule numbers, the corresponding platform rule number can be found in the "rule allocation table." When the platform rule number in the "rule allocation table" file and the intermediate record form match, the project rule number corresponding to that platform rule number in the "rule allocation table" is imported into the corresponding position in the intermediate record form; otherwise, the project rule number is not imported. For specific project rule numbers, if a corresponding platform rule number cannot be found in the "rule allocation table," the project rule number is imported into the position in the intermediate record form where the corresponding platform rule number is not recorded. The import rule module filters out the project rule numbers assigned to the "Floor Plan" based on the allocation objects of the project rule numbers in the "Rule Allocation Table" file, and marks the project rule numbers in the intermediate record form, indicating that the project rule numbers need to be verified by the floor plan. After the project rule numbers assigned to the "Floor Plan" in the intermediate record form are entered, the import rule module generates the final record form.

[0035] The sub-table generation module can receive the final record form sent by the import rule module. The sub-table generation module can create sub-table groups, each including multiple record sub-tables and one remarks sub-table. The multiple record sub-tables correspond to the functions of platform rule numbers in the "Platform Documentation," and each record sub-table is named after a function of a platform rule number. The remarks sub-table corresponds to the functions of platform rule numbers not recorded in the "Platform Documentation," and is used to store the project rule numbers (typically used to store specific project rule numbers) corresponding to the functions of platform rule numbers not recorded in the "Platform Documentation." The sub-table generation module can fill in the project rule number assigned to the "Floor Plane" in the final record form with the corresponding function of the platform rule number in the "Platform Documentation" (i.e., the marker of the project rule number in the corresponding sub-column of the "Content Item") into the sub-table corresponding to the function of the platform rule number (e.g., the project rule number's marker in the corresponding sub-column of the "Content Item"). Figure 5 As shown, this allows for the functional categorization of project rule numbers assigned to the "Floor Plan" to obtain different functional forms for the floor plan verification project.

[0036] When using the system described in this invention, the system configuration rules are extracted from the "System Configuration Rule File" by the rule allocation table generation module; then, the system configuration rules are imported into an EXCEL format "Rule Allocation Table" file. Simultaneously, the template creation module creates "Verification Report Templates (APPLICABLE RULES)" and, based on the functions of the platform rule numbers recorded in the "Platform Documentation," divides the content items in the "Verification Report Templates (APPLICABLE RULES)" into multiple record sub-columns and remarks sub-columns; then, all platform rule numbers from the "Platform Documentation" are imported into the corresponding parts of the "Verification Report Templates (APPLICABLE RULES)" to generate an intermediate record form. Further, the template creation module can mark the corresponding functions of each project rule number in the "Platform Documentation" in the intermediate record form according to the functions of the platform rule numbers in the "Platform Documentation," that is, mark them in the corresponding sub-column of the "Content Items" in the intermediate record form; and mark the positions in the remarks sub-column that do not correspond to platform rule numbers, thus marking the sub-column of the "Content Items" corresponding to specific project rule numbers. The import rule module receives the "rule allocation table" file sent by the rule allocation table generation module and the intermediate record form sent by the template creation module. Based on the consistency between the project rule number in the "rule allocation table" file and the platform rule number in the intermediate record form, it imports the general project rule number from the "rule allocation table" file into the corresponding position in the intermediate record form. It also imports the specific project rule number from the "rule allocation table" into the position of the intermediate record form where no platform rule number is recorded. Then, based on the allocation object of each project rule number in the "rule allocation table," the import rule module filters and marks the project rule numbers assigned to the "floor plan" in the intermediate record form, generating the final record form. The sub-table generation module receives the final record form sent by the import rule module and creates a sub-table group. Simultaneously, based on the function of the platform rule number corresponding to the project rule number assigned to the "floor plan" in the final record form (i.e., marking the platform rule number function in the sub-column of the "content item" corresponding to each project rule number in the intermediate record form), the sub-table generation module fills in the project rule number into the sub-table corresponding to the sub-column name of the "content item" (e.g., ...). Figure 5 As shown), different functional forms are obtained to verify the floor plan project.

[0037] like Figure 1 As shown, this invention provides a method for automatically importing and assigning project rule numbers for floor plan verification, applied to the aforementioned system. It includes: The rule allocation table generation module extracts system configuration rules from the "system configuration rule file" that records system configuration rules to generate a "rule allocation table"; wherein, the system configuration rules include: platform rule number, project rule number, the allocation object and type of project rule number, and the correspondence between platform rule number and project rule number.

[0038] The template creation module creates a "Verification Report Template" and imports all platform rule numbers from the "Platform Documentation" into the "Verification Report Template" to generate an intermediate record form; the "Platform Documentation" is used to record platform rule numbers and platform rule number functions; The import rules module imports the project rule numbers from the "Rule Allocation Table" into the corresponding positions in the intermediate record form based on the type of project rule number, the correspondence between platform rule number and project rule number.

[0039] The import rules module filters and marks the project rule numbers assigned to the "Floor Plan" in the intermediate record form based on the project rule numbers in the "Rule Assignment Table" to obtain the final record form.

[0040] The sub-table generation module creates a sub-table group; the sub-table group includes a remarks sub-table and multiple record sub-tables; the multiple record sub-tables correspond to the functions of the platform rule numbers in the "Platform Documentation", and the remarks sub-table corresponds to the functions of platform rule numbers not recorded in the "Platform Documentation"; and according to whether the project rule number assigned to the "Floor Plan" in the final record form is recorded in the "Platform Documentation", the project rule number assigned to the "Floor Plan" is imported into the corresponding sub-table to obtain different function forms for the floor plan verification project.

[0041] Furthermore, the method of the present invention specifically includes: Step 1: Extract system configuration rules from the "System Configuration Rules File" to obtain the "Rule Assignment Table".

[0042] The rule assignment table generation module generates rules from a Word-formatted "System Configuration Rules File" (e.g., ...). Figure 3 Extract system configuration rules (as shown) and populate them into an Excel-formatted "Rule Assignment Table" (e.g., ...). Figure 2 (as shown in the file). Among them, such as... Figure 2 As shown, the format of the rules in the rule allocation table (i.e., the column names of the rule allocation table) includes: System Configuration Rule Number (i.e., Project Rule Number) (SYCR), Rule Content (Text), Design, Safety Attribute (Safety), Allocation Object (Allocation), Input Source (Source), and Specific Rule (Specific rule).

[0043] Specifically, the "Input Source" column is used to record platform rule numbers. The "Specific rule" column indicates the type of project rule number. Each cell in this column is marked "Yes" or "No". When a cell in this column is marked "Yes", it means that the cell corresponds to a specific project rule number, that is, the "Input Source" column for that project rule number does not record the platform rule number (i.e., the rule is not recorded in the "System Configuration Rule File"). When a cell in this column is marked "No", it means that the cell corresponds to a general project rule number, that is, the "Input Source" column for that project rule number will record the corresponding platform rule number (i.e., the platform rule number is recorded in the system configuration rule file), such as... Figure 3 As shown, the "Allocation" column records the objects to which the project rule number is assigned. These objects include: Scheme Plan, Train Operation System (TMS), and Addressing Plan. When the "Allocation" column records "Scheme Plan," it means that the project rule number needs to be verified on the Scheme Plan.

[0044] Step 2: Create “Applicable Rules”; and import the platform rule number into the “Applicable Rules” according to the “Platform Documentation” to obtain the intermediate record form.

[0045] The template module creates a worksheet form and sets its format. For example... Figure 4 As shown, the names of the first to tenth columns in the form are: Platform Rule Number, Project Rule Number, Not considered (from SyCR) (rules not required for system configuration), Not considered (synthesis) (report statistics page not required), N / A (from GFPD) (not applicable in platform rules), To check inpriority (to check in TMS), To check in SP (to check in SP) (indicating the assigned object is "plan view"), Other verification (other document verification), and Items (content items), thus completing the creation of the "Verification Report Template (APPLICABLE RULES)".

[0046] Furthermore, based on the function of the platform rule number and the type of the project rule number in the "Platform Documentation," the "Content Items" column is divided into multiple record sub-columns and one remarks sub-column. The remarks sub-column corresponds to the function of a platform rule number not recorded in the "Platform Documentation," and is used to mark the project rule number corresponding to the function of that platform rule number (i.e., to mark a specific project rule number). The multiple record sub-columns are divided according to the function of the platform rule numbers in the "Platform Documentation," and each record sub-column corresponds to the function of a platform rule number in the "Platform Documentation" (i.e., the chapter name or abbreviation of the name in the "Platform Documentation"). The name of each record sub-column is the content corresponding to the chapter number in the "Platform Documentation" or its abbreviation, and the record sub-column is used to mark the function of the platform rule number corresponding to the platform rule number.

[0047] Furthermore, the names of the recorded sub-columns include: line, track container, track chaining, ZC area, SIG area, platforms & stations, train charac, stop point (SSP), secondary detection zone (SDD), change of end area, turnout and turnout point (Sw & Pt), signal light type (Si_Lamp_Type), signals, permanent speed limit (PSR), automatic turnaround route (Cycles), routes, sidings, stabling, workshop, washing zone, KP gap, tech room, dwell time and running time, emergency platform closure (ESP), platform screen doors (PSD), personnel safety switch (SPKS), automatic turnaround without personnel (ATB), conventional direction, and discrimination area. areas, flanking, gap, intertrack, and movements.

[0048] Then, the template creation module imports all the platform rule numbers in the "Platform Documents" into the "Verification Report Template (APPLICABLE RULES)" to obtain the intermediate record form.

[0049] In a preferred embodiment, to facilitate operators in quickly obtaining platform rule numbers or the corresponding project rule numbers through "Applicable Rules," after completing the above-mentioned operation of creating "Applicable Rules," the template creation module can horizontally divide the "Applicable Rules" into multiple general rule sections and one specific rule section based on the function of the system-assigned rules in the "Platform Documentation" and the type of the project rule number. (See [link to relevant documentation]). Figure 4 .

[0050] Specifically, in this embodiment, based on the function of the system allocation rules in the "Platform Documentation", the "Applicable Rules" are horizontally divided into multiple general rule parts, each of which corresponds to the function of a system allocation rule; that is, rows a to b in the form of the "Applicable Rules" are the jth general rule part.

[0051] Meanwhile, since the platform documentation only records the platform rule number and its corresponding function, while the "Rule Assignment Table" contains both general project rule numbers and specific project rule numbers, and the specific project rule number does not have a corresponding platform rule number in the "Rule Assignment Table", in order to enable the "Applicable Rules" to record all project rule numbers in the "Rule Assignment Table", the specific project rule number is marked in the specific rules section of the "Applicable Rules"; that is, rows c to d in the form of the "Applicable Rules" are the specific rules section.

[0052] In this embodiment, a template module is created to define rows c to d of the "Validation Report Template (APPLICABLE RULES)" form as a specific rule section, used to record content for which the project rule number is a specific rule. Based on the number n of chapters in the "Platform Documentation," n general rule sections, equal to the number of chapters in the "Platform Documentation," are set after the specific rule section in the "Validation Report Template."

[0053] In this embodiment, when importing platform rule numbers from the "Platform Documentation" into the "Verification Report Template," the platform rule numbers from each chapter of the "Platform Documentation" are filled into the corresponding general rules section according to their functions. After importing all platform rule numbers from the "Platform Documentation" into the "Verification Report Template (APPLICABLE RULES)," an intermediate record form containing the platform rule numbers is obtained.

[0054] In one specific embodiment, the "Platform Documentation" includes n chapters, and the "Verification Report Templates (APPLICABLE RULES)" will be divided into n+1 parts. The specific rule parts and the general rule parts are separated by a row of cells with a gray background; each general rule part is also separated by a row of cells with a gray background, and the first cell of each general rule part indicates the function of its corresponding platform rule number (i.e., the chapter name in the "Platform Documentation"). See [link to relevant documentation]. Figure 4 .

[0055] Step 3: For the intermediate record form in Step 2, determine whether each platform rule number can be searched for in the "Platform Documentation" to find the corresponding function of the platform rule number, and record the function of the corresponding platform rule number in the intermediate record form.

[0056] If a platform rule number can be found in the "Platform Documentation" to search for the corresponding function of the platform rule number, then search for the functions of the platform rule number in the "Platform Documentation" in turn, and mark the function of the platform rule number corresponding to the item rule number as "x" in the corresponding record sub-column of the "Content Items" column.

[0057] Furthermore, for positions in the intermediate record form where the platform rule number is not recorded (i.e., the "Platform Rule Number" column is blank), a mark is made in the corresponding remarks sub-column to mark the sub-column (i.e., the remarks sub-column) in the "Content Item" corresponding to the specific item rule number.

[0058] Step 4: Import the rules module. Based on the type of project rule number, the correspondence between platform rule number and project rule number in the "Rule Assignment Table", complete the filling of project rule number in the intermediate record form, and filter out the project rule number assigned to the "Floor Plan" to obtain the final record form.

[0059] Step 4.1: Determine whether the project rule number recorded in the rule allocation table is a specific project rule number, and complete the filling in of the first and second columns of the intermediate record form.

[0060] Specifically, following the row order in the rule allocation table, select a cell from the "Specificrule" column of the rule allocation table; determine whether the content recorded in the cell is "YES" (i.e., determine whether the type of the project rule number is a specific project rule number), and fill the project rule number into the corresponding position.

[0061] When there is a cell marked "yes" in the "Specific rule" column of the rule allocation table, that is, the project rule number corresponding to that cell in the rule allocation table is a specific project rule number, fill in the project rule number into the cell in the second column ("Project Rule Number" column) of the intermediate record form where there is no corresponding platform rule number, that is, there is no corresponding platform rule number at that cell position.

[0062] In a preferred embodiment, since the intermediate record form is divided into a specific rule section and multiple general rule sections, when a cell in the "Specific rule" column of the rule allocation table is recorded as "yes", the item rule number corresponding to that cell will be filled into the specific rule section of the second column (i.e., the "item rule number" column) of the intermediate record form (see [link]). Figure 4 Furthermore, in the intermediate record form, fill in "NA" in the "Platform Rule Number" column corresponding to the rule number of this project.

[0063] When a cell marked "No" exists in the "Specific rule" column of the rule allocation table, it means that the project rule number corresponding to that cell in the rule allocation table is a general project rule number. In this case, the import rule module compares the platform rule number corresponding to that cell in the rule allocation table with the platform rule number in the first column ("Platform Rule Number") of the intermediate record form. If the platform rule numbers in the two tables match, the project rule number corresponding to that platform rule number in the rule allocation table is entered into the second column ("Project Rule Number") of the intermediate record form. Figure 4 As shown, this is to complete the filling of the general project rule number in the intermediate record form (that is, to fill in the "project rule number" column in the intermediate record form according to the correspondence between the platform rule number and the project rule number in the "rule allocation table").

[0064] If a platform rule number cannot be found in the second column of the intermediate record form in the rule allocation table, no operation will be performed, that is, the entry of the project rule number corresponding to the platform rule number will be abandoned.

[0065] Step 4.2: After completing Step 4.1, based on the contents of the "Allocation" column in the rule allocation table, filter out the rule numbers of the projects assigned to the "Floor Plan" and complete the eighth column ("Floor Plan Verification" column (To check in SP)) in the intermediate record form to obtain the final record form.

[0066] The import rules module searches for the content recorded in the "Allocation" column of the rule allocation table and determines whether the content recorded in the "Allocation" column of the rule allocation table is "Scheme Plan" (i.e. whether the project rule number determined in step 4.1 is assigned to the Scheme Plan).

[0067] When the "Allocation" column of a cell in the rule allocation table records "Scheme Plan", the project rule number corresponding to that cell is recorded. Then, the project rule number is retrieved in the first column of the intermediate record form ("Project Rule Number" column (SYCR)). In the intermediate record form, the cell corresponding to the project rule number in the "To check in SP" column is filled with "x" to mark that the project rule number is allocated to the Scheme Plan.

[0068] If the content recorded in the "Allocation" column corresponding to the cell selected in step 4.1 of the rule allocation table is not "Scheme Plan", then no operation is performed on the intermediate record form (i.e., jump to step 4.3 to perform step 4.1 on the next cell in the "Specific rule" column of the rule allocation table).

[0069] Step 4.3: Iterate through the cells in the "Allocation" column of the rule allocation table, repeating steps 4.1 to 4.2, to filter out all project rule numbers assigned to the "Floor Plan" and obtain the final record form.

[0070] Step 5: Create sub-table groups, and fill the corresponding sub-tables with the project rule numbers assigned to the floor plan according to the function and type of the platform rule number corresponding to each project rule number in the final record form.

[0071] Specifically, the sub-table generation module creates a sub-table group based on the function of the platform rule number in the "Platform Document" (i.e., each sub-column of the "Content Entry" column) and the type of the project rule number. The sub-table group includes multiple record sub-tables and one notes sub-table. Each of the multiple record sub-tables corresponds to the function of a platform rule number in the "Platform Document," and its name is the chapter name or an abbreviation of the chapter name in the "Platform Document," corresponding to the names of the multiple record sub-columns of the "Content Entry." The notes sub-table is used to indicate the function of a specific project rule number that is not recorded in the "Platform Document," i.e., it stores specific project rule numbers. At this point, each sub-table corresponds to each sub-column of the "Content Entry" column (see...). Figure 4 , Figure 5 (As shown).

[0072] Subsequently, the sub-table generation module imports the functional categories of the project rule numbers assigned to the "Floor Plan" into the corresponding sub-tables based on the function of the platform rule numbers in the "Platform Document" (i.e., the markers in the sub-columns of the "Content Entries"). See also Figure 4 When the project rule number assigned to the "Floor Plan" does not have a corresponding platform rule number and the function of the corresponding platform rule number cannot be found in the "Platform Documentation," that is, when the project rule number is marked in the remarks sub-column of the "Content Item" in the final form (usually a specific project rule number is marked), then the project rule number is imported into the remarks sub-table. When the platform rule number corresponding to the project rule number assigned to the "Floor Plan" in the final record form can be found in the "Platform Documentation," that is, when the project rule number is marked in the record sub-column of the corresponding "Content Item" in the final record form, then the project rule number is filled into the sub-table corresponding to the "Content Item" sub-column to obtain different function forms for the floor plan verification project.

[0073] Specifically, the sub-table generation module can search for cells marked "x" in each sub-column of the "Content Items" column, and fill in the corresponding project rule number into the first column of the corresponding sub-table, thus forming different functional forms for the floor plan verification project, such as... Figure 5 As shown.

[0074] In summary, the method for automatically importing and assigning project rule numbers for floor plan verification described in this invention overcomes the problem of easily finding or missing rules by automatically filling the project rule numbers in the rule assignment table into the "verification report template" and marking the project rule numbers assigned to the "floor plan". Based on the function of the platform rule numbers in the "platform documentation", the sub-columns of the "content item" column corresponding to the marked project rule numbers are automatically filled, and the sub-columns of the "content item" column (Items) are filled into the corresponding sub-tables according to the sub-columns of the "content item" column (Items) to quickly and efficiently obtain different functional forms for floor plan verification projects.

[0075] Although the present invention has been described in detail through the preferred embodiments above, it should be understood that the above description should not be considered as a limitation of the present invention. Various modifications and substitutions to the present invention will be apparent to those skilled in the art after reading the above description. Therefore, the scope of protection of the present invention should be defined by the appended claims.

Claims

1. A method for automatically importing and assigning project rule numbers for floor plan verification, characterized in that, include: The rule allocation table generation module extracts system configuration rules from the "system configuration rule file" that records system configuration rules to generate a "rule allocation table"; wherein, the system configuration rules include: platform rule number, project rule number, the allocation object and type of project rule number, and the correspondence between platform rule number and project rule number; The template creation module creates a "Verification Report Template" and imports all platform rule numbers from the "Platform Documentation" into the "Verification Report Template" to generate an intermediate record form; the "Platform Documentation" is used to record platform rule numbers and the functions of platform rule numbers; The import rules module imports the project rule numbers from the "Rule Allocation Table" into the corresponding positions in the intermediate record form based on the type of project rule number, the correspondence between platform rule number and project rule number. The import rules module filters and marks the project rule numbers assigned to the "Floor Plan" in the intermediate record form based on the allocation objects of the project rule numbers in the "Rule Allocation Table" to obtain the final record form; The sub-table generation module creates a sub-table group; the sub-table group includes a remarks sub-table and multiple record sub-tables; the multiple record sub-tables correspond to the functions of the platform rule numbers in the "Platform Documentation", and the remarks sub-table corresponds to the functions of platform rule numbers not recorded in the "Platform Documentation"; and according to whether the project rule number assigned to the "Floor Plan" in the final record form is recorded in the "Platform Documentation", the project rule number assigned to the "Floor Plan" is imported into the corresponding sub-table to obtain different function forms for the floor plan verification project.

2. The method for automatically importing and assigning project rule numbers for floor plan verification according to claim 1, characterized in that, The types of project rule numbers include: specific project rule numbers and general project rule numbers; wherein, the specific project rule number cannot be found in the "Rule Allocation Table" and the function of the corresponding platform rule number is not recorded in the "Platform Documentation"; the general project rule number can be found in the "Rule Allocation Table" and the function of the corresponding platform rule number is recorded in the "Platform Documentation". The methods for creating a "verification report template" using the template creation module include: Create a worksheet form, which includes: platform rule number, project rule number, floor plan verification item with "floor plan" as the assigned object, and content items, and complete the creation of the "verification report template"; Based on the function of the platform rule number in the "Platform Documentation", the "Content Entries" column is divided into multiple record sub-columns and one remarks sub-column; Among them, the remarks sub-column corresponds to the functions of platform rule numbers not recorded in the "platform documentation"; The multiple record sub-columns are divided according to the function of the platform rule number in the "Platform Documentation", with each record sub-column corresponding to the function of a platform rule number in the "Platform Documentation".

3. The method for automatically importing and assigning project rule numbers for floor plan verification according to claim 2, characterized in that, The methods for creating a "verification report template" using the template creation module also include: The template creation module divides the "Verification Report Template" into multiple general rule sections and one specific rule section based on the function of the system-assigned rules in the "Platform Documentation" and the type of the project rule number; Based on the system allocation rules of the "Platform Documentation", the "Verification Report Template" is divided into multiple general rule parts, and each general rule part corresponds to the function of a system allocation rule. The specific rule section is used to mark the rule number of a specific project.

4. The method for automatically importing and assigning project rule numbers for floor plan verification according to claim 3, characterized in that, The methods for generating intermediate record forms by importing platform rule numbers from the "Platform Documentation" into the "Verification Report Template" through the creation of a template module include: Based on the function of the platform rule number in the "Platform Documentation", fill in each platform rule number in the "Platform Documentation" into the corresponding general rule section to obtain the intermediate record form.

5. The method for automatically importing and assigning project rule numbers for floor plan verification according to claim 2, characterized in that, Based on the correspondence between platform rule numbers and project rule numbers in the "Rule Allocation Table," the methods for importing project rule numbers from the "Rule Allocation Table" file into the corresponding positions in the intermediate record form include: The import rule module iterates through the types of project rule numbers recorded in the rule allocation table to determine whether the project rule number is a specific project rule number. When it is a specific project rule number, fill in the project rule number in the position where there is no corresponding platform rule number in the intermediate record form; When it is not a specific project rule number, the import rule module compares the platform rule number corresponding to the project rule number in the rule allocation table with the platform rule number in the intermediate record form. If the platform rule number in the rule allocation table matches the one in the intermediate record form, then fill in the rule number of that project in the intermediate record form at the position corresponding to the platform rule number. If the platform rule number in the rule allocation table is inconsistent with that in the intermediate record form, no operation will be performed.

6. The method for automatically importing and assigning project rule numbers for floor plan verification according to claim 1, characterized in that, Methods for filtering and marking the project rule numbers assigned to "Floor Plan" in the intermediate record form to obtain the final record form include: The import rule module iterates through the allocation objects of the project rule number and determines whether the allocation object of the project rule number in the "rule allocation table" is "floor plan" in order to obtain the final record form. When the project rule number in the rule assignment table is assigned to "floor plan", then the project rule number is marked in the intermediate record form; If the project rule number in the rule assignment table is not assigned to a "floor plan" object, no operation will be performed.

7. The method for automatically importing and assigning project rule numbers for floor plan verification according to claim 2, characterized in that, Before importing the project rule number from the "Rule Assignment Table" into the intermediate record form, the template creation module marks the function of each platform rule number in the "Platform Document" in the "Content Items" of the intermediate record form according to the function of each platform rule number in the "Platform Document"; and marks the positions in the "Content Items" notes that do not correspond to the platform rule number, so as to mark the sub-column in the "Content Items" corresponding to the specific project rule number. During the process of importing the project rule number assigned to "Floor Plan" into the corresponding sub-table in the sub-table generation module, the project rule number is filled into the sub-table corresponding to the "Content Item" according to the mark in the sub-column of "Content Item" to obtain different functional forms for the floor plan verification project.

8. A system for automatically importing and assigning project rule numbers for plan verification according to any one of claims 1-7, characterized in that, include: The rule allocation table generation module receives the "system configuration rule file", extracts system configuration rules from the "system configuration rule file", and then imports the system configuration rules into the "rule allocation table". The template creation module receives the "Platform Document" and creates a "Verification Report Template" that includes the project rule number, platform rule number, project rule number allocation object, and content items. The template creation module imports all platform rule numbers recorded in the "Platform Document" into the "Verification Report Template" to obtain an intermediate record form. The import rules module receives the intermediate record form generated by the template creation module; the import rules module receives the "rule allocation table" file from the rule allocation table generation module; the import rules module imports the project rule numbers in the "rule allocation table" into the intermediate record form according to the type of project rule number, the correspondence between platform rule number and project rule number in the "rule allocation table"; The import rule module filters out the project rule number assigned to the "Floor Plan" based on the "Assignment Object" in the "Rule Assignment Table" file, and marks the platform rule number in the intermediate record form to obtain the final record form; The sub-table generation module receives the final record form generated by the import rule module; the sub-table generation module establishes a sub-table group including a remarks sub-table and multiple record sub-tables; and the multiple record sub-tables correspond to the functions of the platform rule numbers in the "Platform Document", while the remarks sub-table corresponds to the functions of platform rule numbers not recorded in the "Platform Document"; the sub-table generation module imports the project rule numbers assigned to the "Floor Plan" into the corresponding sub-tables according to whether the project rule numbers in the final record form are recorded in the "Platform Document", thereby obtaining different function forms for the floor plan verification project.

9. The system for automatically importing and assigning project rule numbers for floor plan verification according to claim 8, characterized in that, During the process of importing the project rule number assigned to the "Floor Plan" into the corresponding sub-table, the template creation module divides the "Content Item" into multiple record sub-columns and one remarks sub-column according to the function of the platform rule number in the "Platform Document"; the remarks sub-column corresponds to the function of the platform rule number not recorded in the "Platform Document"; the multiple record sub-columns respectively correspond to the function of the platform rule number in the "Platform Document"; Furthermore, the template creation module marks the function of each platform rule number in the "Platform Document" in the "Content Items" of the intermediate form according to the function of each platform rule number in the "Platform Document"; and marks the positions in the "Content Items" notes that do not correspond to the platform rule number, so as to mark the sub-column in the "Content Items" corresponding to the specific project rule number. The sub-table generation module fills in the project rule number into the sub-table corresponding to the "Content Item" sub-column according to the mark of the project rule number in the corresponding sub-column of "Content Item" to obtain different functional forms for the floor plan verification project.

10. The system for automatically importing and assigning project rule numbers for plan verification according to claim 8, characterized in that, After dividing the content items into multiple sub-columns, the template creation module further divides the "Verification Report Template" into a specific rule section and multiple general rule sections based on the function of the platform rule number and the type of the project rule number in the "Platform Documentation". The specific rule section is used to store the rule number of a specific project; the multiple general rule sections each correspond to the function of a platform rule number in the "platform document" to store the platform rule number and project rule number corresponding to the function of that platform rule number.

Images