Carrier rocket testing and launching process refined information management and control system based on handheld terminal

Abstract

The invention discloses a carrier rocket test-launch process refined information management and control system based on a handheld terminal. The system comprises a decision-making area, a design management and control area and a test-launch execution area. From the perspective of converting files into data information transmission, a new process management and control design method and concept are adopted, carrier rocket launching site process information management and control design is carried out, a hierarchical management and control framework of different professional systems is established through a modularization method according to a launching site process operation mode, an information transmission management mode in refined management and control is constructed, and the management and control efficiency is improved. Unified management and template process scheme design in process management and control are realized, and the design scheme is implemented in a handheld terminal. Flow design work and result and state check and confirmation are completed among the stages through a handheld terminal, refined management and control of work flow information of a carrier rocket in a launching site are achieved, the test launch execution efficiency and reliability of a carrier rocket launching task are improved, and high-quality launch task completion is achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of launch vehicle process information control, and in particular to a launch vehicle test and launch process refined information control system based on a handheld terminal. Background Art

[0002] There are many work items for launch vehicles at the launch site, and the workspaces are closely connected, including the transport and unloading of launch vehicles into the launch site, rocket status recovery and handover, rocket technical area installation and testing, rocket transfer and vertical assembly, subsystem testing, launch general inspection, full system gas inspection, propellant filling, launch and other process links. Depending on the model and mission, the work items of launch vehicles at the launch site involve 200-500 people, 20-50 working days, and about 20 major process links. The information system control and implementation of process design, work requirements, operation content, completion effect, quality status and other links at the launch site is extremely difficult. When there are errors in work arrangements or the operation quality does not meet the requirements, it may lead to the postponement or cancellation of the launch mission, and in serious cases, it may lead to the catastrophic impact of the failure of the flight mission.

[0003] The work process of the launch vehicle at the launch site is designed by the general designer, and the commanders of each system are responsible for the design and formulation of the work content. The operators or equipment in the relevant positions perform installation operations and tests, and the operators or equipment in the positions confirm the operation results after the operation. Currently, the launch process arrangement, implementation and confirmation of the execution effect of the launch vehicle at the launch site are completed through the transmission of paper documents or CDs, which has problems such as low transmission efficiency, easy deviation in the transmission process, poor control effect, poor execution effect constraint, poor precision of result confirmation and delayed timeliness. Summary of the invention

[0004] The present invention provides a carrier rocket test and launch process refined information control system based on a handheld terminal. From the perspective of converting files into data information transmission, a new process control design method and concept are adopted to carry out the carrier rocket launch site process information control design. Through a modular method, a hierarchical control architecture of different professional systems is established according to the launch site process operation mode, and an information transmission management mode in refined control is constructed to achieve unified management and templated process scheme design in process control, and the above design scheme is implemented in a handheld terminal. The process design work and result and status check confirmation are completed between each level through a handheld terminal, so as to achieve refined control of the carrier rocket's work process information at the launch site, improve the test and launch execution efficiency and reliability of the carrier rocket launch mission, and achieve high-quality completion of the launch mission.

[0005] First, a launch vehicle test and launch process refined information control system based on a handheld terminal is provided, including a decision-making area, a design control area, and a test and launch execution area;

[0006] The decision area is used to input the launch mission requirements based on the mission input terminal and send the launch mission requirements to the design control area. It is also used to execute the launch decision based on the launch execution terminal according to the launch execution plan fed back by the design control area.

[0007] The design control area has a multi-level design process; the multi-level design process subdivides the launch mission layer by layer, and finally subdivides it into multiple basic work units of operation and test; the design control area sends the execution requirements of the test and launch operation to the test and launch execution area through the operation and test basic work units based on handheld terminals; in addition, the design control area confirms and counts the test and launch feedback information reported by the test and launch execution area based on handheld terminals; the design control area summarizes, reports, and confirms the test and launch process information level by level, and forms a final launch execution plan to feed back to the decision-making area;

[0008] The test and development execution area obtains the test and development operation content provided by the design control area through handheld terminals to perform tests and operations, and collects records as required, enters the collected results through the handheld terminal, and then outputs them to the design control area; the connection between the design control area and the test and development execution area is the job instruction, which is the design output of the design control area and guides the work of the test and development execution area.

[0009] In combination with the first aspect, in certain implementations of the first aspect, the design and control area is provided with model-level processes, system-level processes and subsystem-level processes, and the subsystem-level processes are further subdivided into basic work units of operation and testing; wherein, a launch vehicle launch mission requirement corresponds to a model-level process, a model-level process corresponds to multiple system-level processes, a system-level process corresponds to multiple subsystem-level processes, and a subsystem-level process corresponds to multiple basic work units of operation and testing.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the system satisfies at least one of the following:

[0011] The model-level process is divided into work phases, with important time points, key technical nodes, and test and launch cycles clearly defined. As the process of the entire launch site cycle, it guides the entire operation, testing, and command process, and the authority is open to model command.

[0012] The system-level process is a refinement of the first-level workflow. It refines the phased work of the first-level workflow and guides the work of multiple working days. The authority is open to system commanders.

[0013] Subsystem-level processes guide the implementation of daily operations, testing, and data interpretation processes; authority is open to subsystem commanders;

[0014] The basic work unit is the lowest-level smallest unit in the launch site test and launch workflow design; the basic work unit connects with the process upward to assemble the process; it is integrated with the job positions and job operation requirements downward, and the authority is open to the participating job personnel.

[0015] In combination with the first aspect, in some implementations of the first aspect, the test execution area is provided with a test execution terminal, an operation execution terminal, a multimedia acquisition terminal, and a data acquisition terminal;

[0016] The test execution terminal is used to execute the test according to the job instructions;

[0017] The operation execution terminal is used to perform operations according to the job instructions;

[0018] The multimedia acquisition terminal is used to carry out multimedia acquisition and input multimedia acquisition results according to the job operation instructions. The multimedia acquisition results correspond to the operation results of the operation execution terminal;

[0019] The data collection terminal is used to complete data collection and enter data collection results according to the job operation instructions. The data collection results correspond to the test results of the test execution terminal.

[0020] In combination with the first aspect, in certain implementations of the first aspect, the design control area is connected to the test and development execution area through the final subdivided operation test basic work unit; the test and development operation content of each operation test basic work unit is determined by the job instruction; the job instruction includes a variety of work templates, and the test and development operation content of the basic work unit is determined by the corresponding work template; the work template in the job instruction serves as an information transmission channel for the test and development execution area to complete the collection work and feedback to the design control area; the same work template is used in different basic work units.

[0021] In a second aspect, a method for using the launch vehicle test and launch process refined information management and control system as described in any one of the implementations of the first aspect is provided, comprising:

[0022] In the decision-making area, the launch mission requirements are determined based on the mission entry terminal, the key parameters of the launch mission are entered, and the launch mission requirements are sent to the design control area;

[0023] The information is transmitted to the design control area. The process design terminal completes the design step by step based on the multi-level design process, and finally subdivides it into multiple basic work units of operation and test. The connection between each basic work unit of operation and test and the test and development execution area is achieved through the job instructions.

[0024] The information is transmitted to the test and development execution area. Each execution terminal performs operations according to the job operation instructions, collects data through the collection terminal, and transmits the information to the design control area in the form designed in the job operation instructions;

[0025] The information is transmitted to the design control area, and the execution confirmation terminal summarizes and confirms the results step by step according to the multi-level design process, and forms the final launch execution plan and feeds it back to the decision-making area;

[0026] In the decision-making area, the final launch decision is made based on the launch execution plan fed back by the launch execution terminal to the design control area.

[0027] In conjunction with the second aspect, in certain implementations of the second aspect, the following conditions are met in the design control area:

[0028] In the process design phase, a launch vehicle launch mission requirement corresponds to a model-level process; a model-level process is subdivided into multiple system-level processes for design, a system-level process is subdivided into multiple subsystem-level processes for design, and a subsystem-level process is subdivided into multiple basic work units for operation and testing;

[0029] In the execution confirmation link, the collection results from the test and launch execution area are transmitted to the operation test result confirmation terminal corresponding to the basic working unit for confirmation, and the operation test result confirmation terminal outputs an operation test result; multiple operation test results are transmitted to a corresponding result confirmation terminal in the subsystem for confirmation, and the result confirmation terminal outputs an analysis result; multiple analysis results are transmitted to a corresponding rocket status review terminal in the system level for confirmation, and the rocket status review terminal outputs a rocket status review result; multiple rocket status review results are transmitted to a corresponding test and launch process confirmation terminal in the model level for confirmation, and the test and launch process confirmation terminal outputs a test and launch process confirmation result, which is the launch execution plan of the carrier rocket launch mission; a carrier rocket launch mission has only one test and launch process confirmation result.

[0030] In conjunction with the second aspect, in certain implementations of the second aspect, the following conditions are met in the design control area:

[0031] Sequentially number multiple basic work units of operation tests under the same subsystem process;

[0032] The currently numbered operation test basic work unit sends the operation test task to the test and development execution area;

[0033] The operation test task is completed and reported to the operation test result execution confirmation terminal corresponding to the current number;

[0034] After the operation test result execution confirmation terminal confirms, a confirmation message is sent to the next numbered operation test basic working unit and / or the operation test result execution confirmation terminal corresponding to the next numbered operation test basic working unit.

[0035] In conjunction with the second aspect, in certain implementations of the second aspect, in the execution confirmation link of the design control area, when a certain level of execution confirmation terminal determines that the result confirmation requirements are not met, the unsatisfied state is transmitted to the corresponding process design terminal at the same level, and the process design terminal re-sends the process information to the process design terminal at the next level to re-execute the process design; wherein,

[0036] After the subsystem-level execution confirmation terminal counts the data reported by multiple operation test result execution confirmation terminals, it determines that there are results that do not meet the confirmation requirements, and passes the result identification that does not meet the requirements to the corresponding subsystem-level process design terminal. The subsystem-level process design terminal determines the corresponding operation test basic work unit based on the result identification, so that the operation test basic work unit determines whether it is necessary to re-execute the process design and re-execute the operation test work.

[0037] In conjunction with the second aspect, in certain implementations of the second aspect, in the execution confirmation link of the design control area, when a certain level of execution confirmation terminal determines that the result confirmation requirements are not met, the unsatisfied state is transmitted to the corresponding process design terminal at the same level, and the process design terminal re-sends the process information to the process design terminal at the next level to re-execute the process design; wherein,

[0038] When the operation test result execution confirmation terminal counts the collected results from the test and development execution area and determines that there are results that do not meet the confirmation requirements, the result identification that does not meet the requirements is passed to the corresponding operation test basic work unit; the operation test basic work unit determines the corresponding execution terminal in the test and development execution area based on the result identification and the job instruction manual, so that the execution terminal re-executes the operation test work; or the operation test basic work unit modifies the content in the job instruction manual work template based on the result identification and forms a new work template, so that the execution terminal re-executes the operation test work according to the new work template.

[0039] In conjunction with the second aspect, in certain implementations of the second aspect, when a new target work template is formed in a job instruction book, it is mutually confirmed between multiple operation test result confirmation terminals, and / or confirmed by a corresponding subsystem-level execution confirmation terminal; wherein,

[0040] The basic work unit of the operation test enters the test and development operation content on a blank template. The test and development operation content is generated by referring to the paper material or CD material circulation process. After the test and development execution area feeds back the operation content and operation results to the design control area, the confirmed operation content forms a new target work template in the job instruction.

[0041] In conjunction with the second aspect, in certain implementations of the second aspect, when a new target work template is formed in a job instruction book, it is mutually confirmed between multiple operation test result confirmation terminals, and / or confirmed by a corresponding subsystem-level execution confirmation terminal; wherein,

[0042] Before the operational test results are confirmed, a unified paper material or CD-ROM material circulation process is used for execution; after the corresponding operational test is completed and the results are obtained, the data is digitized through the collection terminal in the test and development execution area, and fed back to the execution confirmation terminal in the design and control area for result confirmation; after the results are confirmed, a new target work template is formed in the job instruction book with reference to the paper material or CD-ROM material circulation process.

[0043] Compared with the prior art, the solution provided by the present invention includes at least the following beneficial technical effects:

[0044] (1) Realize refined information control over the launch vehicle test and launch workflow at the launch site, improve the execution efficiency and reliability of the launch vehicle launch mission, and achieve high-quality and successful completion of the launch vehicle launch mission.

[0045] (2) Through the refined information control of the launch site test and launch process, a templated design scheme can be established to automatically execute process design, test operation execution, collection and record execution, result analysis and status review, and realize the construction of automatic test and launch process based on the refined information control system. In addition, by combing the process and combining it with the refined information control system, the workload, error-prone links, and high-risk points of the launch site test and launch can be analyzed, process design optimization can be carried out, and resource allocation in the launch site test and launch process can be reasonably allocated.

[0046] (3) Based on the refined information control system of the launch vehicle launch site test and launch process, job operation instructions for various tasks in the launch site test and launch can be established, and online information control of the work within the launch site can be carried out. The operation test execution requirements can be updated in a timely manner according to changes in the design technical status, ensuring the correctness, reliability and effectiveness of the execution of the launch vehicle launch site test and launch work. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 This is a schematic diagram of the refined information management and control system for the launch site test and launch process of a carrier rocket based on a handheld terminal. DETAILED DESCRIPTION

[0048] The present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0049] The present invention provides a launch vehicle test and launch process refined information control system based on a handheld terminal and its use process. The launch vehicle test and launch process refined information control system is mounted on a handheld terminal, and the launch vehicle test and launch process control is realized by operating on the handheld terminal. Figure 1 As shown, the process refined information control system can include a decision-making area, a design control area, and a testing and execution area.

[0050] The decision-making area conducts top-level design and launch judgment, and is the input and output part of the launch vehicle test and launch process refined information control system. In the decision-making area, the launch mission requirements can be entered based on a handheld terminal (such as a mission entry terminal) and sent to the design control area. In addition, for the launch execution plan fed back by the design control area, the decision-making area can perform launch judgment based on a handheld terminal (such as a launch execution terminal).

[0051] The design control area is a system design and analysis scenario. In the process design stage, the input situation is decomposed and designed in detail, and the test operation execution requirements and result collection requirements are formulated; and in the execution confirmation stage, the collection situation is analyzed and the status is checked to provide a basis for judgment for the final output. The design control area can have a multi-level design process. The multi-level design process can subdivide the launch task layer by layer, and finally subdivide it into multiple basic work units of operation and test. The design control area can send the execution requirements of the test and launch operation to the test and launch execution area through the basic work unit of operation and test. In addition, for the test and launch feedback information reported by the test and launch execution area, the design control area can confirm and count the test and launch feedback information based on the handheld terminal and the result collection requirements. The subdivided multiple basic work units of operation and test can summarize, report, and confirm the test and launch process information level by level, and form the final launch execution plan to feedback to the decision-making area.

[0052] exist Figure 1 In the illustrated embodiment, the design control area is provided with model-level processes, system-level processes and subsystem-level processes, and the subsystem-level processes are further subdivided into basic work units of operation and testing. Among them, a launch vehicle launch mission requires a model-level process, a model-level process corresponds to multiple system-level processes, a system-level process corresponds to multiple subsystem-level processes, and a subsystem-level process corresponds to multiple basic work units of operation and testing. The above three basic work processes are also used as basic design modules, and common basic-level modules of processes can be constructed between different launch vehicle missions.

[0053] The test and development execution area is the execution scenario for the specific implementation of the test and development process. The test and development operation content (including test operation execution requirements and result collection requirements) provided by the design control area is obtained through a handheld terminal to perform tests and operations, and the collection and recording are carried out according to the input requirements. The collection results are entered through the handheld terminal and then output to the design control area. The connection between the design control area and the test and development execution area is the job instruction, which is the design output of the design control area and guides the work of the test and development execution area.

[0054] The job instructions indicate the clear execution status of the test and operation work, and formulate the test data collection and multimedia recording status. When the design control area transmits the test and development operation content to the test and development execution area, the test and development execution area performs the test and development work based on at least one terminal. Figure 1 In the illustrated embodiment, the test and development execution area may be provided with a test execution terminal, an operation execution terminal, a multimedia acquisition terminal, and a data acquisition terminal. The test execution terminal is used to execute tests in accordance with the job instructions. The operation execution terminal is used to perform operations in accordance with the job instructions. The multimedia acquisition terminal is used to carry out multimedia acquisition in accordance with the job instructions and enter the multimedia acquisition results (for example, the operation results of the corresponding operation execution terminal). The data acquisition terminal is used to complete data acquisition in accordance with the job instructions and enter the data acquisition results (for example, the test results of the corresponding test execution terminal). The test and development execution area counts the multimedia acquisition results and the data acquisition results, and transmits the information to the design control area according to the template designed in the job instructions.

[0055] The launch vehicle test and launch process refined information system is based on handheld terminals for information transmission and execution. The entire information system is established in a dedicated network environment. Each handheld terminal is connected and interconnected with the integrated server through a network switch. The integrated server receives, processes and stores status, and provides data, status and other support for the handheld terminal.

[0056] The following describes the use process of the refined information management and control system for the testing and development process.

[0057] Step 1: In the decision-making area, determine the launch mission requirements based on the mission entry terminal, enter the key parameters of the launch mission, and send the launch mission requirements to the design control area.

[0058] Step 2: Information is transmitted to the design control area. The process design terminal completes the design step by step based on the multi-level design process, and is finally subdivided into multiple basic work units of operation and testing. Each basic work unit of operation and testing is connected to the test and development execution area through job instructions.

[0059] In the design control area, a refined information control architecture can be constructed according to the three-level process model, through the model level, system level, subsystem level and operation test level. After clarifying the launch mission status of the carrier rocket, the refined information control system plan for the launch process of the carrier rocket based on the handheld terminal will be implemented.

[0060] The model-level process, i.e. the main work process, is divided into major work phases, with important time points, key technical nodes, and test and launch cycles clearly defined. As the process of the entire launch site cycle, it guides the development of the entire operation, test, and command process. The model commander is responsible for the formulation, confirmation, and approval of the process.

[0061] The system-level process is a refinement of the first-level workflow. It refines the phased work of the first-level workflow and guides the work of 1-2 working days. It is mainly used by system commanders. The first-level process plays a connecting role.

[0062] The subsystem-level process mainly guides the daily operation, testing, and data interpretation process within the system. It is mainly used by subsystem commanders to guide the operation and testing work content of the executive personnel.

[0063] The basic work unit is the lowest unit of the modular launch site test and launch workflow design. The basic work unit module is the junction of the two dimensions of process and position. The basic work unit module is the main object of design and the main carrier for clear job responsibilities. The basic work unit connects with the process upwards to assemble the process; it integrates with the position and job requirements downwards to guide the specific work of the test position personnel.

[0064] In the process design phase, a launch vehicle launch mission requires a model-level process. A model-level process is subdivided into multiple system-level processes for design, a system-level process is subdivided into multiple subsystem-level processes for design, and a subsystem-level process is subdivided into multiple basic work units for operation and testing.

[0065] Step 3: The information is transmitted to the test and development execution area. Each execution terminal performs operations according to the job instructions, collects data through the collection terminal, and transmits the information to the design control area in the form designed in the job instructions.

[0066] The job operation instruction condenses and integrates the general and special requirements for the job into one, becoming a "one-stop" job operation manual, which is used to guide the use when carrying out a specific basic work, and to formulate execution procedures and collection steps.

[0067] Combined with the above, the design control area is connected with the test and development execution area through the final subdivided operation test basic work unit. The test and development operation content of each operation test basic work unit is determined by the job instruction. The job instruction can include a variety of work templates, and the test and development operation content of the basic work unit can be determined by the corresponding work template. The work template in the job instruction can be used as an information transmission channel for the test and development execution area to complete the collection work and feedback to the design control area. The same work template can be used in different basic work units, thereby constructing a general job book module to form a design template.

[0068] In some embodiments, multiple operation test basic work units under the same subsystem process are numbered sequentially. The currently numbered operation test basic work unit sends the operation test task to the test execution area. After the operation test task is completed and reported to the operation test result execution confirmation terminal corresponding to the current number, and confirmed by the operation test result execution confirmation terminal, a confirmation message is sent to the next numbered operation test basic work unit and / or the operation test result execution confirmation terminal corresponding to the next numbered operation test basic work unit; thereby realizing the interaction between the same-level operation test basic work units and the same-level operation test result execution confirmation terminals, and ensuring the sequential execution of tasks.

[0069] Step 4: The information is transmitted to the test and development execution area. Each execution terminal performs operations according to the job instructions, collects data through the collection terminal, and transmits the information to the design control area in the form designed in the job instructions.

[0070] In the execution confirmation link, the collection results from the test and launch execution area are transmitted to the operation test result confirmation terminal corresponding to the basic work unit for confirmation, and the operation test result confirmation terminal outputs an operation test result; multiple operation test results are transmitted to a corresponding result confirmation terminal in the subsystem for confirmation, and the result confirmation terminal outputs an analysis result; multiple analysis results are transmitted to a corresponding rocket status review terminal at the system level for confirmation, and the rocket status review terminal outputs a rocket status review result; multiple rocket status review results are transmitted to a corresponding test and launch process confirmation terminal at the model level for confirmation, and the test and launch process confirmation terminal outputs a test and launch process confirmation result, which is the launch execution plan of the launch vehicle launch mission. A launch vehicle launch mission can have only one test and launch process confirmation result.

[0071] In one possible scenario, in the execution confirmation link of the design control area, when a certain level of execution confirmation terminal determines that the result confirmation requirements are not met, the unsatisfied status can be transmitted to the corresponding process design terminal at the same level, and the process design terminal re-sends the process information to the next level of process design terminal to re-execute the process design.

[0072] In one embodiment, after the subsystem-level execution confirmation terminal counts the data reported by multiple operation test result execution confirmation terminals and determines that there are results that do not meet the confirmation requirements, the result identifier that does not meet the requirements is passed to the corresponding subsystem-level process design terminal. The subsystem-level process design terminal determines the corresponding operation test basic work unit based on the result identifier, so that the operation test basic work unit determines whether it is necessary to re-execute the process design and re-execute the operation test work.

[0073] In another embodiment, when the operation test result execution confirmation terminal counts the collected results from the test and development execution area and determines that there are results that do not meet the confirmation requirements, the result identification that does not meet the requirements is passed to the corresponding operation test basic work unit. The operation test basic work unit can determine the corresponding execution terminal in the test and development execution area based on the result identification and the job instruction manual, so that the execution terminal re-executes the operation test work; or the operation test basic work unit can modify the content in the job instruction manual work template based on the result identification and form a new work template, so that the execution terminal re-executes the operation test work according to the new work template.

[0074] Step 5: The information is transmitted to the decision-making area. The launch execution terminal compares the key parameters of the launch and the test and launch process to confirm the status, and checks and checks the launch mission requirements to confirm that they are met, and determines the launch conditions of the carrier rocket.

[0075] In one possible situation, when the last-level design process forms a new target basic work unit and there is no corresponding work template in the job instruction, a new target work template needs to be formed in the job instruction.

[0076] In one embodiment, the operation test basic work unit can enter the test and development operation content on a blank template. The test and development operation content can be generated, for example, with reference to the specific circumstances of the existing paper material or CD material circulation process. The test and development operation content is used to subsequently form a new target work template in the job instruction book, and the new target work template corresponds to the new target basic work unit. After the test and development execution area feeds back the operation content and operation results to the design control area, the confirmed operation content forms a new target work template.

[0077] In another embodiment, the existing paper material or optical disc material circulation process is uniformly used before the operation test results are confirmed. After the corresponding operation test is completed and the results are obtained, the data is digitized through the acquisition terminal in the test execution area and fed back to the execution confirmation terminal in the design control area for result confirmation. After the results are confirmed, a new target work template is formed in the job operation instruction book with reference to the specific situation of the existing paper material or optical disc material circulation process.

[0078] Furthermore, the formation of a new target work template can be mutually confirmed between multiple operation test result confirmation terminals, and can also be confirmed through a corresponding subsystem level execution confirmation terminal.

[0079] Example 1

[0080] Combination Figure 1 After the launch mission requirement A1 in the decision-making area, the model-level process B1, system-level process B2 (possibly multiple B21, B22, ..., B2X), subsystem-level process B3 (possibly multiple B31, B32, ..., B3X), operation test basic work unit B4 (possibly multiple B41, B42, ..., B4X), and job instruction C1 (possibly multiple C11, C12, ..., C1X) in the design control area are sequentially connected. The job instruction C1 is respectively connected with the operation test basic work unit B4, test C2, operation C3, multimedia record C4, test data C5 and operation test result D4. After the operation test result D4 (possibly multiple D41, D42, ..., D4X), it is sequentially connected with the analysis result confirmation D3 (possibly multiple D31, D32, ..., D3X), rocket status review D2 (possibly multiple D21, D22, ..., D2X), test and launch process confirmation D1, and execution launch judgment E1.

[0081] For the launch vehicle test and launch process at the launch site, a design template for process, data analysis, and test execution is developed. After receiving the launch mission of the launch vehicle, the information system can be refined according to the launch vehicle test and launch process, automatically completing process compilation, information transmission path design, test operation instructions and collection instructions execution, and automatically analyzing execution results, status review, and process confirmation capabilities, so as to automatically determine whether the launch vehicle meets the launch requirements.

[0082] The process-refined information control system uses handheld terminals to control the work processes of assembly, testing, filling and launching of launch vehicles at the launch site through a refined information system, realize the automatic formulation and execution of test and launch work and processes, guide the implementation of operation and testing work, and confirm and control the results of the test work, the completion effect and the status of the rocket. The control system uses the original status transmission and process design documents, operation test guidance documents and quality confirmation documents to establish a digital information transmission method and a standardized process design plan, which improves the efficiency and refinement of process information control, and improves the completion quality of the launch site test and launch work. The handheld terminal is the main carrier for the implementation of control and implementation of the process-refined information system in the launch process. This launch site test and launch workflow refinement information control system solution has no precedent in the field of launch vehicles in my country.

[0083] Although the present invention is disclosed as above in the form of a preferred embodiment, it is not intended to limit the present invention. Any person skilled in the art may make possible changes and modifications without departing from the spirit and scope of the present invention. Therefore, the scope of protection of the present invention shall be based on the scope defined by the claims of the present invention.

Claims

1. A launch vehicle test and launch process refined information management and control system based on a handheld terminal, characterized in that: Includes decision-making area, design control area and test and development execution area; The decision area is used to input the launch mission requirements based on the mission input terminal and send the launch mission requirements to the design control area. It is also used to execute the launch decision based on the launch execution terminal according to the launch execution plan fed back by the design control area. The design control area has a multi-level design process; the multi-level design process subdivides the launch mission layer by layer, and finally subdivides it into multiple basic work units of operation and testing; The design control area uses handheld terminals to send the execution requirements of the test and development operations to the test and development execution area by operating the basic test work unit. In addition, the design control area uses handheld terminals to confirm and count the test and development feedback information reported by the test and development execution area. The design and control area will summarize, report and confirm the test and launch process information step by step, and form the final launch execution plan and feed it back to the decision-making area; The test and development execution area obtains the test and development operation content provided by the design control area through the handheld terminal to perform tests and operations, collects and records as required, enters the collected results through the handheld terminal, and then outputs them to the design control area; The connection between the design control area and the test and development execution area is the job instruction, which is the design output of the design control area and guides the work of the test and development execution area.

2. The system according to claim 1, characterized in that The design control area is equipped with model-level processes, system-level processes and subsystem-level processes. The subsystem-level processes are further subdivided into basic work units of operation and testing; among them, one launch vehicle launch mission requirement corresponds to one model-level process, one model-level process corresponds to multiple system-level processes, one system-level process corresponds to multiple subsystem-level processes, and one subsystem-level process corresponds to multiple basic work units of operation and testing.

3. The method of use according to claim 2, characterized in that: The system satisfies at least one of the following: The model-level process is divided into work phases, with important time points, key technical nodes, and test and launch cycles clearly defined. As the process of the entire launch site cycle, it guides the entire operation, testing, and command process, and the authority is open to model command. The system-level process is a refinement of the first-level workflow. It refines the phased work of the first-level workflow and guides the work of multiple working days. The authority is open to system commanders. Subsystem-level processes guide the daily operation, testing, and data interpretation processes; The authority is open to subsystem commanders; The basic work unit is the lowest-level smallest unit in the launch site test and launch workflow design; the basic work unit connects with the process upward to assemble the process; it is integrated with the job positions and job operation requirements downward, and the authority is open to the participating job personnel.

4. The system according to claim 1, characterized in that The test execution area is equipped with test execution terminals, operation execution terminals, multimedia acquisition terminals, and data acquisition terminals; The test execution terminal is used to execute the test according to the job instructions; The operation execution terminal is used to perform operations according to the job instructions; The multimedia acquisition terminal is used to carry out multimedia acquisition and input multimedia acquisition results according to the job operation instructions. The multimedia acquisition results correspond to the operation results of the operation execution terminal; The data collection terminal is used to complete data collection and enter data collection results according to the job instructions. The data collection results correspond to the test results of the test execution terminal.

5. The system according to claim 1, characterized in that The design control area is connected with the test and development execution area through the final subdivided operation test basic work unit; the test and development operation content of each operation test basic work unit is determined by the job instruction; the job instruction includes a variety of work templates, and the test and development operation content of the basic work unit is determined by the corresponding work template; the work template in the job instruction serves as an information transmission channel for the test and development execution area to complete the collection work and feedback to the design control area; the same work template is used in different basic work units.

6. A method for using the launch vehicle test and launch process refined information management and control system according to any one of claims 1 to 5, characterized in that: include: In the decision-making area, the launch mission requirements are determined based on the mission entry terminal, the key parameters of the launch mission are entered, and the launch mission requirements are sent to the design control area; The information is transmitted to the design control area. The process design terminal completes the design step by step based on the multi-level design process, and finally subdivides it into multiple basic work units of operation and test. The connection between each basic work unit of operation and test and the test and development execution area is achieved through the job instructions. The information is transmitted to the test and development execution area. Each execution terminal performs operations according to the job operation instructions, collects data through the collection terminal, and transmits the information to the design control area in the form designed in the job operation instructions; The information is transmitted to the design control area, and the execution confirmation terminal summarizes and confirms the results step by step according to the multi-level design process, and forms the final launch execution plan and feeds it back to the decision-making area; In the decision-making area, the final launch decision is made based on the launch execution plan fed back by the launch execution terminal to the design control area.

7. The method of use according to claim 6, characterized in that: In the design control area, the following requirements must be met: In the process design phase, a launch vehicle launch mission requires a model-level process; A model-level process is subdivided into multiple system-level processes for design, a system-level process is subdivided into multiple subsystem-level processes for design, and a subsystem-level process is subdivided into multiple basic work units for operation and testing; In the execution confirmation phase, the collection results from the test execution area are transmitted to the operation test result confirmation terminal corresponding to the basic work unit for confirmation, and the operation test result confirmation terminal outputs an operation test result; The multiple operation test results are transmitted to a corresponding result confirmation terminal in the subsystem for confirmation, and the result confirmation terminal outputs an analysis result; The multiple analysis results are transmitted to a corresponding rocket status review terminal in the system level for confirmation, and the rocket status review terminal outputs a rocket status review result; Multiple rocket status review results are transmitted to a corresponding test and launch process confirmation terminal in the model level for confirmation, and the test and launch process confirmation terminal outputs a test and launch process confirmation result, which is the launch execution plan of the carrier rocket launch mission; a carrier rocket launch mission has only one test and launch process confirmation result.

8. The method of use according to claim 6, characterized in that: In the design control area, the following requirements must be met: Sequentially number multiple basic work units of operation tests under the same subsystem process; The currently numbered operation test basic work unit sends the operation test task to the test and development execution area; The operation test task is completed and reported to the operation test result execution confirmation terminal corresponding to the current number; After the operation test result execution confirmation terminal confirms, a confirmation message is sent to the next numbered operation test basic working unit and / or the operation test result execution confirmation terminal corresponding to the next numbered operation test basic working unit.

9. The method of use according to claim 6, characterized in that: In the execution confirmation phase of the design control area, when a certain level of execution confirmation terminal determines that the result confirmation requirements are not met, the unsatisfied status is transmitted to the corresponding process design terminal at the same level, and the process design terminal re-sends the process information to the next level of process design terminal to re-execute the process design; After the subsystem-level execution confirmation terminal has counted the data reported by multiple operation test result execution confirmation terminals, it is determined that there are results that do not meet the confirmation requirements, and the result identifier that does not meet the requirements is transmitted to the corresponding subsystem-level process design terminal. The subsystem-level process design terminal determines the corresponding operation test basic work unit according to the result identifier, so that the operation test basic work unit determines whether it is necessary to re-execute the process design and re-execute the operation test work; and / or, When the operation test result execution confirmation terminal counts the collected results from the test and development execution area and determines that there are results that do not meet the confirmation requirements, the result identification that does not meet the requirements is passed to the corresponding operation test basic work unit; the operation test basic work unit determines the corresponding execution terminal in the test and development execution area based on the result identification and the job instruction manual, so that the execution terminal re-executes the operation test work; or the operation test basic work unit modifies the content in the job instruction manual work template based on the result identification and forms a new work template, so that the execution terminal re-executes the operation test work according to the new work template.

10. The method of use according to claim 6, characterized in that: When a new target work template is formed in the job instruction book, it is mutually confirmed between multiple operation test result confirmation terminals, and / or confirmed through the corresponding subsystem level execution confirmation terminal; wherein, The basic work unit of the operation test enters the test and launch operation content on the blank template, and the test and launch operation content is generated with reference to the paper material or CD material circulation process; after the test and launch execution area feeds back the operation content and operation results to the design control area, the confirmed operation content forms a new target work template in the job instruction book; or, Before the operational test results are confirmed, a unified paper material or CD-ROM material circulation process is used for execution; after the corresponding operational test is completed and the results are obtained, the data is digitized through the collection terminal in the test and development execution area, and fed back to the execution confirmation terminal in the design and control area for result confirmation; after the results are confirmed, a new target work template is formed in the job instruction book with reference to the paper material or CD-ROM material circulation process.

Images