A full-process control method for civil aircraft continuous airworthiness events

Abstract

The present application provides a method for the whole process control of civil aircraft continuous airworthiness events, which includes: automatically driving the event determination process based on the event determination plan, and monitoring the determination of the event determination process; automatically driving the event screening process based on the event screening plan, and determining the target event screening level based on the target event determined by the event determination process and the preset event screening level standard; automatically driving the event evaluation process based on the event evaluation plan, and monitoring the event evaluation of target events corresponding to different target event screening levels; automatically driving the event investigation process based on the event investigation plan, and monitoring the situation of conducting event investigations or rejecting event investigations in the event investigation process; automatically driving the measure formulation and release process based on the measure formulation and release plan, and monitoring the formulation and release of measures based on the results of conducting event investigations in the measure formulation and release process. According to the above method, the problem of incompatibility of multiple businesses in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the technical field of airworthiness review, and more specifically, to a method for full-process control of continuous airworthiness events of civil aircraft. Background Art

[0002] At present, when managing the failures, failures and defects of a certain type of aircraft during the design, manufacturing, use and maintenance process through online information collection, event analysis, risk assessment, engineering investigation, corrective measures and other application functions, the process often uses a serial approach to achieve the process of upstream business completion driving downstream business development, which basically meets the requirements of continuous airworthiness business process management and standardized processing of event tracking and locating. Clearly responsible persons can formulate corresponding measures based on the evaluation results to improve the design, manufacturing, use and maintenance processes of the aircraft, thereby improving the safety and reliability of a certain type of aircraft.

[0003] However, in the above technology, risk assessment adopts a fully structured report format, which has poor maintainability and is not compatible with system changes. In addition, there are many scenarios in the continuous airworthiness process, such as cross-stage business adjustments, parallel business development, event duplication, event closure, file version change, event information supplement, etc., which are not compatible with the above technology. Summary of the invention

[0004] In view of this, the purpose of this application is to provide a full-process management and control method for civil aircraft continuous airworthiness events. The handling process is divided into seven processes: information collection, event determination, event screening, risk assessment, event investigation, measure formulation and release, and event closure. Each process has a corresponding output file. The severity level of the event is derived based on the event probability and impact level, and the classified process control is carried out for the graded events to drive event screening, evaluation, investigation, measure improvement to closure, which solves the problem of incompatibility of multiple businesses in the existing technology.

[0005] In a first aspect, an embodiment of the present application provides a method for full-process control of civil aircraft continuous airworthiness events, the method comprising:

[0006] Generate an information report based on various information collected on civil aircraft safety incidents during the design, manufacture, use and maintenance of civil aircraft; wherein the civil aircraft safety incidents may include various types of failures, accidents, defects, exceeding technical limitations or deviations that have occurred or been discovered;

[0007] For the information report sheet, automatically drive the event determination process based on a preset event determination plan, and monitor the determination status of the event determination process;

[0008] After the event determination process is completed, the event screening process is automatically driven based on a preset event screening plan, and the target event screening level is determined based on the target event determined by the event determination process and the preset event screening level standard;

[0009] Automatically drive the event assessment process based on the preset event assessment plan, and monitor the event assessment status of target events corresponding to different target event screening levels;

[0010] Automatically drive the incident investigation process based on the preset incident investigation plan, and monitor the implementation or rejection of incident investigations in the incident investigation process;

[0011] Automatically drive the measures formulation and release process based on the preset measures formulation and release plan, and monitor the formulation and release of measures based on the results of the incident investigation in the measures formulation and release process;

[0012] After the incident assessment process and the measures formulation and release process are completed, monitor the incident closure and summary status of the incident closure and summary process.

[0013] Furthermore, the method further comprises:

[0014] In the case of repeated reporting of the same event and the event not being closed, monitor the merging of the same event reported repeatedly in the event merging process, and determine the execution status of the main event as the final basis after the merger;

[0015] In the event that an ongoing event needs to be cancelled due to abnormal or objective factors, monitor the event closure process and directly close it and sign the resolution.

[0016] Further, the preset event determination plan includes the event determination plan name, event determination plan completion time, event determination plan completion status, event determination plan responsible person node and event determination plan deliverables; wherein, the event determination plan name is the completed event report form, the event determination plan completion status is the event report form signed and completed, the event determination plan responsible person node is the event collector node, and the event determination plan deliverable is the signed and completed event report form;

[0017] The method of automatically driving the event determination process based on a preset event determination plan for the information report sheet and monitoring the determination status of the event determination process includes:

[0018] Sending the information report form to the event collector node, obtaining the preliminary event determination result from the event collector node, and monitoring the signing of the event report form under the first preset time constraint;

[0019] After the event report form is signed, the signed event report form is sent to the event supervisor node, and the event administrator node designated by the event supervisor node is determined;

[0020] Monitor the subsequent event determination result of the event administrator node under the second preset time constraint, and use the subsequent event determination result to correct the preliminary event determination result to obtain the target event determined by the event determination process; wherein, if the target event is determined to be a CCAR21.5 event, send the event report form to the reviewer node within the preset time.

[0021] Furthermore, the method further comprises:

[0022] When the target event determined by the event determination process needs to be updated, information is supplemented for multiple rounds of target events, automatically associated with the event report form to form a complete event, and the event information supplementation status of the event supplement process is monitored.

[0023] Furthermore, the preset event screening plan includes the event screening plan name, event screening plan completion time, event screening plan completion status, event screening plan responsible person node and event screening plan deliverables; wherein, the event screening plan name is the completed event screening form, the event screening plan completion status is the event screening form signing completion, the event screening plan responsible person node is the operation supervisor node, and the event screening plan deliverable is the signed event screening form;

[0024] After the event determination process is completed, the event screening process is automatically driven based on a preset event screening plan, and the target event screening level is determined based on the target event determined by the event determination process and the preset event screening level standard, including:

[0025] After the event determination process is completed, based on the target event determined by the event determination process and the preset event screening level standard, the target event screening level in the event screening list is determined;

[0026] The signing process of the event screening sheet is monitored, and the signed event screening sheet is sent to the operation supervisor node.

[0027] Furthermore, the method further comprises:

[0028] If the operation supervisor node recommends initiating an ad hoc meeting, the signed event screening form will be associated with the minutes of the ad hoc meeting, and the conclusion of the event screening plan will be automatically formed based on the meeting resolution of the ad hoc meeting.

[0029] Further, the preset event assessment plan includes the event assessment plan name, event assessment plan completion time, event assessment plan completion status, event assessment plan responsible person node and event assessment plan deliverables; wherein, the event assessment plan name is the completed event risk assessment report, the event assessment plan completion status is the event risk assessment report is signed and completed, the event assessment plan responsible person node is the event administrator node, and the event assessment plan deliverable is the signed event risk assessment report;

[0030] The event evaluation process is automatically driven based on the preset event evaluation plan, and the event evaluation status of target events corresponding to different target event screening levels is monitored, including:

[0031] For target events corresponding to different target event screening levels, monitor the event assessment status of the target events described in the event risk assessment report and generate an event risk assessment report;

[0032] Monitor the signing process of the event risk assessment report, send the internally signed event risk assessment report to the reviewer node for review, and determine the review result; wherein, the review result can close the event or wait for the event investigation phase to be completed to trigger the implementation of the measures formulation and release plan.

[0033] In a second aspect, the embodiment of the present application further provides a device for controlling the entire process of continuous airworthiness events of a civil aircraft, the device comprising:

[0034] An information collection module is used to generate an information report sheet based on various information collected on civil aircraft safety incidents during the design, manufacture, use and maintenance of civil aircraft; wherein the civil aircraft safety incidents may include various types of failures, accidents, defects, technical limitations or deviations that have occurred or been discovered;

[0035] An event determination module, for automatically driving an event determination process based on a preset event determination plan for the information report sheet, and monitoring the determination status of the event determination process;

[0036] An event screening module, used to automatically drive the event screening process based on a preset event screening plan after the event determination process is completed, and determine the target event screening level based on the target event determined by the event determination process and the preset event screening level standard;

[0037] An event evaluation module is used to automatically drive the event evaluation process based on a preset event evaluation plan and monitor the event evaluation status of target events corresponding to different target event screening levels;

[0038] An event investigation module, used to automatically drive the event investigation process based on a preset event investigation plan, and monitor the situation of conducting or rejecting the event investigation in the event investigation process;

[0039] A measures formulation and release module, which is used to automatically drive the measures formulation and release process based on a preset measures formulation and release plan, and monitor the formulation and release of measures based on the results of the incident investigation in the measures formulation and release process;

[0040] The event closing and summarizing module is used to monitor the event closing and summarizing status of the event closing and summarizing process after the event evaluation process and the measure formulation and release process are completed.

[0041] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the steps of the above method are performed.

[0042] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method as described above are executed.

[0043] The embodiment of the present application provides a full-process control method for continuous airworthiness events of civil aircraft. Continuous airworthiness control mainly completes the management of application functions such as information collection, event determination, event screening, event evaluation, event investigation, corrective improvement measures, and event summary for all types of failures, faults, defects, and situations that exceed technical limitations or deviations that occur or are discovered during the design, manufacture, use, and maintenance of aircraft. According to the classification of airworthiness authority information, design information, manufacturing information, customer engineering information, test aircraft information, and in-service aircraft information, the handling process is divided into seven major processes: information collection, event determination, event screening, risk assessment, event investigation, measure formulation and release, and event closure. Each process has a corresponding output file, and the signing and review process is carried out. The severity level of the event is obtained by the probability and impact of the event, and the level events are classified and controlled to drive event screening, evaluation, investigation, and measure improvement to closure.

[0044] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0046] Figure 1 A flow chart of a method for full-process control of civil aircraft continuous airworthiness events provided in an embodiment of the present application;

[0047] Figure 2 A flowchart of an event determination method provided in an embodiment of the present application;

[0048] Figure 3 A schematic diagram of the structure of a full-process control device for continuous airworthiness events of civil aircraft provided in an embodiment of the present application;

[0049] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work belongs to the scope of protection of the present application.

[0051] Research has found that, at present, when managing the failures, failures and defects of a certain type of aircraft during the design, manufacturing, use and maintenance process through online information collection, event analysis, risk assessment, engineering investigation, corrective measures and other application functions, the process often uses a serial approach to achieve the upstream business completion and drive the downstream business process, which basically meets the requirements of continuous airworthiness business process management and standardized processing of event tracking and locating. Clearly responsible persons can formulate corresponding measures based on the evaluation results to improve the aircraft design, manufacturing, use and maintenance processes, thereby improving the safety and reliability of a certain type of aircraft.

[0052] However, in the above technology, risk assessment adopts a fully structured report format, which has poor maintainability and is not compatible with system changes. In addition, there are many scenarios in the continuous airworthiness process, such as cross-stage business adjustments, parallel business development, event duplication, event closure, file version change, event information supplement, etc., which are not compatible with the above technology.

[0053] Based on this, an embodiment of the present application provides a method for full-process control of civil aircraft continuous airworthiness events. The handling process is divided into seven processes: information collection, event determination, event screening, risk assessment, event investigation, measure formulation and release, and event closure. Each process has a corresponding output file. The severity level of the event is derived based on the event probability and impact level, and the level events are classified and process controlled to drive event screening, evaluation, investigation, and measure improvement to closure, which solves the problem of incompatibility of multiple businesses in the prior art.

[0054] See also Figure 1 , Figure 1 This is a flow chart of a method for controlling the entire process of a civil aircraft continuous airworthiness event provided in an embodiment of the present application. Figure 1 As shown in , the full-process control method for civil aircraft continuous airworthiness events provided by the embodiment of the present application includes:

[0055] S101, generating an information report based on various information collected on civil aircraft safety incidents during the design, manufacture, use and maintenance of civil aircraft; wherein, the civil aircraft safety incidents may include various types of failures, accidents, defects, exceeding technical limitations or deviations that have occurred or been discovered.

[0056] It should be noted that civil aircraft safety incidents refer to failures that affect or may affect aircraft safety during the design, manufacturing, flight test, customer service and in-service process of aircraft products and processes. According to the embodiments provided in this application, civil aircraft safety incidents may include various types of failures, accidents, defects, exceeding technical limitations or deviations that occur or are discovered. Various information related to civil aircraft safety incidents may include airworthiness authority information, design information, manufacturing information, customer engineering information, test aircraft information and in-service flight information when various types of failures, accidents, defects, exceeding technical limitations or deviations occur or are discovered. An information report form refers to a report form filled out based on the above-mentioned various information.

[0057] With respect to the above step S101, in the specific implementation, the relevant business departments shall collect various information of all kinds of failures, accidents, defects, exceeding technical limitations or deviations that occur or are discovered during the design, manufacturing, use and maintenance of civil aircraft, and compile information reports based on the collected information. According to the embodiment provided by the present application, the information reporter generates the information report and submits the information report to the event collector. When the information reporter pushes the information to the event collector, he can manually select the corresponding event collector through the list.

[0058] S102, for the information report form, automatically drive the event determination process based on a preset event determination plan, and monitor the determination status of the event determination process.

[0059] It should be noted that the event determination plan refers to a plan for performing event determination on the various information in the information report. The event determination process refers to the process of performing event determination on the various information in the information report. The determination situation refers to the determination result obtained after performing event determination on the information report, where the determination result may be the type of event.

[0060] With respect to the above step S102, in the specific implementation, after the information report form is generated, the event determination process is automatically driven based on the preset event determination plan, and the determination of the event determination process is monitored. According to the embodiment provided by the present application, after the event collector collects the information report form, he needs to make an event determination on the information in the information report form as soon as possible, complete the signing of the event report form, and needs to select the head of the Continuing Airworthiness Committee Office and report it.

[0061] According to the embodiment provided by the present application, the preset event determination plan includes the event determination plan name, the event determination plan completion time, the event determination plan completion status, the event determination plan responsible person node and the event determination plan deliverables; wherein, the event determination plan name is the completed event report form, the event determination plan completion status is the event report form signing completion, the event determination plan responsible person node is the event collector node, and the event determination plan deliverable is the signed event report form.

[0062] See also Figure 2 , Figure 2 This is a flow chart of an event determination method provided in an embodiment of the present application. Figure 2 As shown in , for the information report form, the event determination process is automatically driven based on a preset event determination plan, and the determination status of the event determination process is monitored, including:

[0063] S201, sending the information report form to the event collector node, obtaining the preliminary event determination result from the event collector node, and monitoring the signing status of the event report form under the first preset time constraint.

[0064] It should be noted that the preliminary determination result of the event refers to the initial determination result determined based on the information report form. The first preset time refers to the signing time limit set in advance, and different preliminary determination results of the event will correspond to different first preset events. The event report form refers to the event report form generated after determining the information in the information report form. The signing status refers to the signing status of the event report form by the event collector.

[0065] For the above step S201, in the specific implementation, after the information report form is generated, it is sent to the event collector node, and the event collector judges the information report form, determines the preliminary judgment result of the event, and monitors whether the signing of the event report form is completed under the first preset event constraint. Specifically, if the information in the preliminary judgment information report form is a CCAR21.5 event, the preliminary judgment result of the event is a CCAR21.5 event, and the signing of the event report form needs to be completed within 24 hours (including non-working days); if the information in the preliminary judgment information report form is not a CCAR21.5 event, the preliminary judgment result of the event is not a CCAR21.5 event, and the determination of the preliminary judgment result of the event needs to be completed within 5 working days, and if it is an event, the signing of the event report form needs to be completed. Here, the CCAR21.5 event refers to the event determined in accordance with the "Civil Aviation Products and Components Qualification Review Regulations".

[0066] S202, after the event report form is signed, the signed event report form is sent to an event supervisor node, and an event administrator node designated by the event supervisor node is determined.

[0067] Regarding the above step S202, in the specific implementation, the event collector needs to select an event supervisor when compiling the event report form, and the event administrator can select A, the supervisor of the Continuing Airworthiness Committee Office. The signed event report form is sent to the event supervisor node, and the event supervisor at the event supervisor node determines the event administrator node. Specifically, a supervisor A of the Continuing Airworthiness Committee Office is responsible for the subsequent designation of event management members, and a supervisor B of the Continuing Airworthiness Committee Office is responsible for the subsequent designation of initial risk assessment members (the initial risk assessor is determined during plan management). This supervisor is the default supervisor of the Continuing Airworthiness Committee Office (the initial risk assessor is determined according to the results set by B when the event management member makes the plan.

[0068] S203, monitoring the subsequent event determination result of the event manager node under the second preset time constraint, and using the subsequent event determination result to correct the preliminary event determination result, to obtain the target event determined by the event determination process.

[0069] It should be noted that the second preset event refers to the subsequent determination time limit set in advance, and different preliminary determination results of the event will correspond to different second preset events. The subsequent determination result of the event refers to the determination result determined by the event administrator based on the event report form. The target event refers to the event corresponding to the final determined event report form.

[0070] For the above step S203, in the specific implementation, after the event report form, the event supervisor node and the event administrator node are determined, the event administrator of the event administrator node determines the subsequent event determination result under the second preset event constraint. If the subsequent event determination result is different from the preliminary event determination result, the preliminary event determination result is corrected using the subsequent event determination result to obtain the target event determined by the event determination process. Among them, if the determined target event is a CCAR21.5 event, the event report form needs to be sent to the reviewer node within a preset time. According to the example provided in this application, the event report form requires three levels of review and approval: preparation, review, countersignature (optional), and approval. After receiving the event report form, the head of the Continuing Airworthiness Committee Office, A, designates an event management member. After receiving the event report form, the event management member determines whether the event on the event report form is a CCAR21.5 event. After the head of the Continuing Airworthiness Committee Office A receives the event report, the system starts timing. If the event received is initially judged as a CCAR21.5 event by the event collector, the event management member must complete the subsequent work of the process within 24 hours (including non-working days); if the event received is initially judged as a non-CCAR21.5 event by the event collector, the event management member must complete the subsequent work of the process within 48 hours (including non-working days). If the event is a CCAR21.5 event, the event management member needs to send the fault, failure and defect report and the event report to the reviewer node at the same time.

[0071] As an optional implementation, the method further includes:

[0072] When the target event determined by the event determination process needs to be updated, information is supplemented for multiple rounds of target events, automatically associated with the event report form to form a complete event, and the event information supplementation status of the event supplement process is monitored.

[0073] Regarding the above steps, when implementing them, if the event collector finds that there is updated information on the reported event, he / she should complete the event information supplement work as soon as possible, fill out the event information supplement form, and submit it to A, the director of the Continuing Airworthiness Committee Office. Anyone involved in the event handling can fill out the event information supplement form at any time to request the event collector to provide additional information on the event. The original event collector will reply to the event information supplement form and submit it to the person who made the request. After A, the director of the Continuing Airworthiness Committee Office, receives the event information supplement form submitted by the event collector, he / she needs to send the event information supplement form to the relevant participants of the event, and automatically associate the event information supplement form with the event report form to form a complete event. For CCAR21.5 events, the event information supplement form needs to be sent to the reviewer node, which will not affect the main process. For other events, it will be pushed together with the event screening form. If the event screening form process has ended, the event information supplement form will be pushed in real time.

[0074] S103, after the event determination process is completed, the event screening process is automatically driven based on a preset event screening plan, and the target event screening level is determined based on the target event determined by the event determination process and a preset event screening level standard.

[0075] It should be noted that the event screening plan refers to the plan for screening the events determined by the event determination process. The event screening process refers to the process of screening events. The event screening level standard refers to the pre-set level assessment standard for event level screening. The target event screening level refers to the level corresponding to the final determined event. Here, the target event screening level is mainly graded according to the severity of the event, which can be divided into four levels: red, orange, yellow, and green. The red level represents the highest risk of the event; the orange level represents the greater risk of the event; the yellow level represents the lesser risk of the event; and the green level represents the event has no safety impact.

[0076] Regarding the above step S103, in specific implementation, after the event determination process is completed, the event screening process is automatically driven based on the preset event screening plan, and the target event screening level is determined based on the target event determined by the event determination process and the preset event screening level standard.

[0077] The preset event screening plan includes the event screening plan name, event screening plan completion time, event screening plan completion status, event screening plan responsible person node and event screening plan deliverables; wherein, the event screening plan name is the completed event screening form, the event screening plan completion status is the event screening form signing completion, the event screening plan responsible person node is the operation supervisor node, and the event screening plan deliverable is the signed event screening form;

[0078] With respect to the above step S103, after the event determination process is completed, the event screening process is automatically driven based on a preset event screening plan, and the target event screening level is determined based on the target event determined by the event determination process and the preset event screening level standard, including:

[0079] Step 1031, after the event determination process is completed, based on the target event determined by the event determination process and the preset event screening level standard, determine the target event screening level in the event screening list.

[0080] Step 1032, monitoring the signing process of the event screening form, and sending the signed event screening form to the operation supervisor node.

[0081] For the above steps 1031-1032, in the specific implementation, after the event determination process is completed, the target event screening level in the event screening form is determined based on the target event determined by the event determination process and the preset event screening level standard. And monitor the signing process for the event screening form, and send the signed event screening form to the operation supervisor node. According to the example provided in this application, the event screening process is a fully structured form, and a four-level review and approval process is carried out: preparation-review-countersign-approval, which is prepared by the event supervisor and the review, countersign, and approval personnel are selected; the event screening form in the event handling procedure system file requires that an expert must countersign, and the countersignature is also a mandatory link. Each link rejection will be returned to the preparation and rewriting. The event screening form is linked to the meeting minutes and action items of the event screening group of the Office of Continuing Airworthiness Committee by the operation supervisor through the meeting management module. The event screening level requirements are set as follows: If it is a CCAR21.5 event, within 48 hours of receiving the task (including non-working days); Events with a red event screening level: within 72 hours of receiving the task (including non-working days); Events with an orange event screening level: within 2 weeks of receiving the task (including non-working days); Events with a yellow or green event screening level: within 1 month of receiving the task (including non-working days); Leader-focused and customer-focused events: from the moment the event type change is received, they are handled in accordance with the time limit requirements for events with an initial risk of red; Events that meet multiple of the above conditions: the shortest processing time limit shall prevail. The red, orange, yellow or green event level needs to be determined after review by the Technical Committee. The completion time of the Continuing Airworthiness Technical Committee is the approval time plus 20 natural days; the completion time of the review meeting is the approval time plus 40 natural days.

[0082] In the above step S103, multiple plan settings can also be supported to re-drive the upgrade event filter list. The event filter list can be upgraded and managed in the order of A, B, C,..., and the latest version is valid; for the upgrade file, the time constraint requirements shall be based on the upgrade time requirements set in the plan management use case.

[0083] As an optional implementation, the method further includes:

[0084] If the operation supervisor node recommends initiating an ad hoc meeting, the signed event screening form will be associated with the minutes of the ad hoc meeting, and the conclusion of the event screening plan will be automatically formed based on the meeting resolution of the ad hoc meeting.

[0085] For the above steps, during the specific implementation, if the operation supervisor node recommends starting an interim meeting, the signed event screening form will be associated with the minutes of the interim meeting, and the meeting resolution results will automatically form the conclusion of the event screening. The meeting needs to proceed according to the preset plan, with timeout warnings. The completion results support automatic merging of events or closing events or triggering the event assessment plan to take effect, and the event investigation plan to take effect. According to the example provided in this application, after the event screening form is approved, all events trigger a to-do list to the operation supervisor, who determines whether to report it to the reviewer node. If the event type is a mergeable event, the to-do list is also triggered to the event supervisor, who selects the event to be merged. If the event type is a closed event, the current process remains unchanged; after the event screening form is approved, if the suggestion to start an interim meeting of the Continuing Airworthiness Technical Committee is selected as "Yes", the to-do list is triggered to the operation supervisor to associate the meeting minutes, which does not affect the main process; the event screening form is associated with the meeting minutes and action items of the event screening group of the Continuing Airworthiness Committee Office by the operation supervisor through the meeting management module.

[0086] S104, automatically driving the event evaluation process based on a preset event evaluation plan, and monitoring the event evaluation status of target events corresponding to different target event screening levels.

[0087] It should be noted that the event evaluation plan refers to the plan for conducting event evaluation on the target event, the event evaluation process refers to the process of conducting event evaluation on the target event, and the event evaluation situation refers to the evaluation result determined by the evaluation of the target event.

[0088] For the above step S104, the event assessment process is automatically driven based on the preset event assessment plan, and the event assessment status of the target events corresponding to different target event screening levels is monitored, which can support multiple plan settings to re-drive the upgraded event risk assessment report.

[0089] The preset event assessment plan includes the event assessment plan name, event assessment plan completion time, event assessment plan completion status, event assessment plan responsible person node and event assessment plan deliverables; wherein, the event assessment plan name is the completed event risk assessment report, the event assessment plan completion status is the signing of the event risk assessment report, the event assessment plan responsible person node is the event administrator node, and the event assessment plan deliverable is the signed event risk assessment report.

[0090] With respect to the above step S104, the event evaluation process is automatically driven based on the preset event evaluation plan, and the event evaluation status of the target events corresponding to different target event screening levels is monitored, including:

[0091] Step 1041 , for target events corresponding to different target event screening levels, monitor the event assessment status of the target events described in the event risk assessment report, and generate an event risk assessment report.

[0092] It should be noted that the incident risk assessment report refers to the report generated based on the incident assessment situation during the accident assessment process.

[0093] Step 1042, monitor the signing process for the event risk assessment report, send the internally signed event risk assessment report to the reviewer node for review, and determine the review result.

[0094] It should be noted that the signing process refers to the signing of the event risk assessment report, and the review result refers to the result obtained by the reviewer after reviewing the event risk assessment report.

[0095] For the above steps 1041-1042, during the specific implementation, for the target events corresponding to different target event screening levels, monitor the event assessment of the target events described in the event risk assessment report, and generate an event risk assessment report. The event level is further clarified, the event risk level and event impact are fully structured, and the warning of events of different risk levels is automatically set, which is associated with the minutes of the temporary meeting, and the meeting resolution results are automatically formed into the conclusion of the event assessment. The meeting needs to proceed according to the preset plan, and the timeout warning is issued. Monitor the signing process of the event risk assessment report, send the internally signed event risk assessment report to the review node for review, and determine the review results. Among them, the review result can close the event or wait for the event investigation stage to be completed to trigger the formulation and release plan of the measures to take effect. According to the example provided in this application, the event assessment is in the form of a document report, with five levels of review: preparation, proofreading, review, counter-signing (mandatory), verification, and approval. The event management member drives the event risk assessment through a plan. At the start, the event management member sets a detailed risk assessment plan for the event in the plan management use case. When the result of the review by the Continuing Airworthiness Technical Committee is passed, the report must continue to complete the review process until approval. The report after internal approval must be submitted to the reviewer node for review. The review results are pass or reject. If passed, the report is archived. After being rejected by the Continuing Airworthiness Technical Committee or the Continuing Airworthiness Review Meeting, the event management member creates a new event assessment plan in the plan management use case. The event risk assessment level requirements are set as follows: Yellow event: within three months from the completion of the initial risk assessment (including non-working days); Red and orange events: within four weeks from the completion of the initial risk assessment (including non-working days); Leadership-focused and customer-focused events: starting from the moment the event type change is received, they shall be handled in accordance with the time limit requirements for events with an initial risk of red; Events that meet multiple of the above conditions: the shortest processing time limit shall prevail; For upgraded documents, there are no time constraints; The completion time of the Continuing Airworthiness Technical Committee is the approval time plus 20 natural days; The completion time of the review meeting is the approval time plus 40 natural days.

[0096] S105, automatically driving the event investigation process based on a preset event investigation plan, and monitoring the situation of conducting the event investigation or rejecting the event investigation in the event investigation process.

[0097] It should be noted that the event investigation plan refers to the plan for investigating the target event, and the event investigation process refers to the process of investigating the target event.

[0098] For the above step S105, in the specific implementation, the event investigation process is automatically driven based on the preset event investigation plan, and the situation of conducting event investigation or rejecting event investigation in the event investigation process is monitored. According to the example provided by this application, some special attribute structured splicing file report forms initiate event investigation suggestion sheets, which are currently three-level review and approval, initiate event investigation instructions, promote feedback event investigation feedback sheets, and draw conclusions on event investigation reports. In case of duplication of event investigation suggestions, evaluate whether it is necessary to conduct event investigation work: if it is necessary to conduct, then conduct subsequent event investigation processes; if the problem is relatively clear and does not need to be conducted, then reject the suggestion sheet; since the relevant event investigation has been conducted, there is no need to conduct this investigation, then feedback is given on the suggestion sheet for the relevant event investigation. For the event investigation after the event merger, for the event merger situation, if the event report sheet 1 has completed the event investigation work, after the event report sheet 2 is merged, the original event investigation is not sufficient to fully support the event report sheet 2, then a new event investigation suggestion sheet is initiated with the event report sheet 2. The event management member drives the event investigation by means of a plan. When the event investigation is initiated, the event management member sets the event investigation plan in the plan management use case. After the event investigation report is rejected by the Continuing Airworthiness Technical Committee or the Continuing Airworthiness Review Meeting, the event management member creates a new event investigation plan in the plan management use case. In step S105, multiple plan settings can be supported to re-drive the event investigation.

[0099] S106, automatically driving the measure formulation and release process based on the preset measure formulation and release plan, and monitoring the formulation and release of measures based on the results of the incident investigation in the measure formulation and release process.

[0100] Regarding the above step S106, during the specific implementation, the measure formulation and release process is automatically driven based on the preset measure formulation and release plan, and the formulation and release of measures based on the results of the event investigation in the measure formulation and release process is monitored.

[0101] According to the examples provided in this application, when each stage (incident reporting, screening, risk assessment, incident investigation, formulation and release of measures) is first started, the plan is automatically triggered by the system, and the relevant stage tasks are directly generated. The event management member determines whether the work plan for this stage is executed, and no plan approval is required. The planned end point of "completing the event screening form" and "completing the event risk assessment report" is when the report review process flows to the end of approval, at which time it is submitted to the Technical Committee for review. When the result of the review is passed, the report must continue to complete the review process until approval. When the result of the review is rejected, if the subsequent review and reviewer review are rejected and the "incident screening work" and "incident risk assessment work" need to be restarted, a new plan needs to be set. After plan approval, the plan drives a new round of "completion of screening work" and "completion of risk assessment work". The approved report needs to be submitted to the reviewer node for review. The review results are pass or reject. If it is passed, the report is archived. If it is rejected, if the subsequent review and reviewer review are rejected, it is necessary to restart the "event screening work" and "event risk assessment work". In this case, a new plan needs to be set up. After the plan is approved, the plan will drive a new round of "completion of screening work" and "completion of risk assessment work".

[0102] The planned end point of the incident investigation is when the review is completed. If the "incident screening work" and "incident risk assessment work" need to be restarted when the subsequent review and the reviewer's review are rejected, a new plan needs to be set. After the plan is approved, the plan will drive a new round of "completion of screening work" and "completion of risk assessment work". The end of the screening / risk assessment stage is marked by the archiving of the incident screening form / incident risk assessment report. The "measure formulation and release" plan triggers the minutes of the associated continuous technical airworthiness committee meeting. The incident management supervisor can trigger the plan again to apply for the relevant document version change after the corresponding task is released until the incident is closed. Support event merging, the same type of events can be merged and handled after review, and the merged events can be closed synchronously when the event is closed. In step S106, multiple plan settings can be supported to re-drive the formulation of measures and release service announcements.

[0103] S107, after the event evaluation process and the measure formulation and release process are completed, monitor the event closure and summary status of the event closure and summary process.

[0104] For the above step S107, in the specific implementation, after the event assessment process and the measures formulation and release process are completed, the event closure and summary of the event closure and summary process are monitored. Event closure is mainly closed manually by the event management member, who selects the reviewer and the approver, and notes the closing basis, and can upload attachments. The closing criteria need to provide event closure prompts: the event screening form is approved by the review meeting, and the event is closed in the event screening stage; the event with a green risk assessment result, the event screening form is approved by the review meeting, and the event is closed after screening; the event with a yellow risk assessment result meets any of the following conditions; the event risk assessment report is approved by the review meeting, and the event is closed in the risk assessment; the event with an orange and red risk assessment result is closed in the correction / improvement measure action project; after the event with a yellow, orange, or red risk assessment result is closed, experience summary work needs to be carried out; after the event is closed, the processing flow of the event ends. If the event needs to be reprocessed, it can be associated with the closed event by adding a new task. The event summary work, some special attribute structured splicing file report forms, are divided into event process summary and event final summary. Summary of the event process: During the event handling process, the event management members need to summarize the historical handling of the event, so as to trace the historical handling of the event in the event decision-making process. Final summary of the event: After the event is closed, the event management members need to summarize the entire process of event handling and complete the final summary report of the event, so as to trace the entire process of event handling when a new event occurs or re-attention is paid. The event summary report requires three levels of review and approval: preparation, review, counter-signature (optional), and approval. The experience summary is in the form of a structured splicing file report with some special attributes. After each yellow, orange or red event is approved for closure by the Continuing Airworthiness Technical Committee, an experience summary needs to be carried out, and the event management members shall designate the corresponding supervisor of the Airworthiness Engineering Center to complete it. The review process of the experience summary report is preparation, review, counter-signature (optional), certification (optional), and approval. The experience summary report must be reviewed and approved by the Continuing Airworthiness Technical Committee meeting and approved by the Deputy Director of the Continuing Airworthiness Technical Committee (Deputy Chief Engineer of Airworthiness).

[0105] As an optional implementation, the method further includes:

[0106] A: For the case where the same event is reported repeatedly and has not been closed, monitor the situation of merging the same event reported repeatedly in the event merging process, and determine the execution status of the main event as the final basis after the merger.

[0107] For the above steps, during the specific implementation, when there is repeated reporting of the same event and the event has not been closed, the situation of merging the repeated reports of the same event in the monitoring event merging process is monitored. Regardless of the stage of the event, the execution status of the main event is automatically used as the final basis after the merger. Event merging means that when an event is reported repeatedly, including repeated reporting of the same event by multiple centers, repeated reporting of the same event by multiple flights, etc., the event management member can apply for event merging for the repeated events, and the premise of event merging is that the event has not been closed. According to the examples provided in this application, whether in the event determination process stage, the event screening process stage, the event assessment process stage, the event investigation process stage or the measure formulation and release process stage, it supports automatic triggering of merging events and closing events. As long as there is repeated reporting of the same event and the event has not been closed, the same events can be merged, and the execution status of the main event can be determined as the final basis after the merger.

[0108] B: In the event that an ongoing event needs to be cancelled due to abnormal or objective factors, monitor the event closure process and directly close and sign the resolution.

[0109] For the above steps, when implementing them, if an ongoing event needs to be cancelled due to abnormalities or objective factors, monitor the closing and approval of the resolution in the event closing process. According to the examples provided by itself, whether in the event determination process stage, event screening process stage, event assessment process stage, event investigation process stage or measure formulation and release process stage, it supports automatic triggering of merging events and closing events. As long as an ongoing event needs to be cancelled due to abnormalities or objective factors, the event needs to be closed, and the direct closing and approval of the resolution in the event closing process is monitored.

[0110] The full-process control method of civil aircraft continuous airworthiness events provided in this application example mainly completes the management of application functions such as information collection, event determination, event screening, event evaluation, event investigation, correction and improvement measures, and event summary for all kinds of failures, faults, defects, and situations beyond technical limitations or deviations that occur or are discovered during the design, manufacture, use, and maintenance of aircraft. According to the classification of airworthiness authority information, design information, manufacturing information, customer engineering information, test aircraft information, and in-service aircraft information, the handling process is divided into seven major processes: information collection, event determination, event screening, risk assessment, event investigation, measure formulation and release, and event closure. Each process has a corresponding output file, and the signing and review process (three-level signing and review or five-level signing and review) is carried out. The severity level of the event (divided into four levels: red, orange, yellow, and green) is obtained through the probability and impact of the event, and the level event is classified and controlled to drive event screening, evaluation, investigation, and measure improvement to closure. Introduce the planned first system self-driving and event management member planned self-driving methods, drive changes and versions through the planned process in the sequential execution process, coordinate management and process control, and automatically monitor the execution of the Continuing Airworthiness Technical Committee and the review meeting in the process, so as to achieve a full-process management and control method from information to event closure. According to the full-process management and control method of civil aircraft continuous airworthiness events provided in this application, the event object can also be virtualized, and the event is used as the main object for full life cycle management. Relevant event process reports (event report form, event screening form, event risk assessment report, event investigation report, etc.) are all attached to the top-level event, and the report version upgrade is not constrained. A comprehensive verification is performed when the event is merged and closed, and the final version of the report is published as the final report.

[0111] See also Figure 3 , Figure 3 This is a schematic diagram of the structure of a full-process control device for continuous airworthiness events of civil aircraft provided in an embodiment of the present application. Figure 3 As shown in , the whole process control device 300 of the civil aircraft continuous airworthiness event includes:

[0112] The information collection module 301 is used to generate an information report form based on various information collected on civil aircraft safety incidents during the design, manufacture, use and maintenance of civil aircraft; wherein the civil aircraft safety incidents may include various types of failures, accidents, defects, technical limitations or deviations that have occurred or been discovered;

[0113] An event determination module 302 is used to automatically drive an event determination process based on a preset event determination plan for the information report sheet, and monitor the determination status of the event determination process;

[0114] An event screening module 303 is used to automatically drive the event screening process based on a preset event screening plan after the event determination process is completed, and determine the target event screening level based on the target event determined by the event determination process and a preset event screening level standard;

[0115] An event evaluation module 304 is used to automatically drive the event evaluation process based on a preset event evaluation plan, and monitor the event evaluation status of target events corresponding to different target event screening levels;

[0116] An event investigation module 305 is used to automatically drive the event investigation process based on a preset event investigation plan, and monitor the situation of conducting event investigation or rejecting event investigation in the event investigation process;

[0117] The measure formulation and release module 306 is used to automatically drive the measure formulation and release process based on a preset measure formulation and release plan, and monitor the formulation and release of measures based on the results of the incident investigation in the measure formulation and release process;

[0118] The event closing and summarizing module 307 is used to monitor the event closing and summarizing status of the event closing and summarizing process after the event evaluation process and the measure formulation and release process are completed.

[0119] Furthermore, the civil aircraft continuous airworthiness event full process control device 300 also includes an event merging module 308, and the event merging module 308 is used to:

[0120] In the case of repeated reporting of the same event and the event not being closed, monitor the merging of the same event reported repeatedly in the event merging process, and determine the execution status of the main event as the final basis after the merger;

[0121] In the event that an ongoing event needs to be cancelled due to abnormal or objective factors, monitor the event closure process and directly close it and sign the resolution.

[0122] Further, the preset event determination plan includes the event determination plan name, event determination plan completion time, event determination plan completion status, event determination plan responsible person node and event determination plan deliverables; wherein, the event determination plan name is the completed event report form, the event determination plan completion status is the event report form signed and completed, the event determination plan responsible person node is the event collector node, and the event determination plan deliverable is the signed and completed event report form;

[0123] When the event determination module 302 automatically drives the event determination process based on the preset event determination plan for the information report form and monitors the determination status of the event determination process, the event determination module 302 is further used to:

[0124] Sending the information report form to the event collector node, obtaining the preliminary event determination result from the event collector node, and monitoring the signing of the event report form under the first preset time constraint;

[0125] After the event report form is signed, the signed event report form is sent to the event supervisor node, and the event administrator node designated by the event supervisor node is determined;

[0126] Monitor the subsequent event determination result of the event administrator node under the second preset time constraint, and use the subsequent event determination result to correct the preliminary event determination result to obtain the target event determined by the event determination process; wherein, if the target event is determined to be a CCAR21.5 event, send the event report form to the reviewer node within the preset time.

[0127] Furthermore, the event determination module 302 is also used for:

[0128] When the target event determined by the event determination process needs to be updated, information is supplemented for multiple rounds of target events, automatically associated with the event report form to form a complete event, and the event information supplementation status of the event supplement process is monitored.

[0129] Furthermore, the preset event screening plan includes the event screening plan name, event screening plan completion time, event screening plan completion status, event screening plan responsible person node and event screening plan deliverables; wherein, the event screening plan name is the completed event screening form, the event screening plan completion status is the event screening form signing completion, the event screening plan responsible person node is the operation supervisor node, and the event screening plan deliverable is the signed event screening form;

[0130] After the event determination process is completed, the event screening module 303 automatically drives the event screening process based on a preset event screening plan. When determining the target event screening level based on the target event determined by the event determination process and the preset event screening level standard, the event screening module 303 is further used to:

[0131] After the event determination process is completed, based on the target event determined by the event determination process and the preset event screening level standard, the target event screening level in the event screening list is determined;

[0132] The signing process of the event screening sheet is monitored, and the signed event screening sheet is sent to the operation supervisor node.

[0133] Furthermore, the event screening module 303 is also used for:

[0134] If the operation supervisor node recommends initiating an ad hoc meeting, the signed event screening form will be associated with the minutes of the ad hoc meeting, and the conclusion of the event screening plan will be automatically formed based on the meeting resolution of the ad hoc meeting.

[0135] Further, the preset event assessment plan includes the event assessment plan name, event assessment plan completion time, event assessment plan completion status, event assessment plan responsible person node and event assessment plan deliverables; wherein, the event assessment plan name is the completed event risk assessment report, the event assessment plan completion status is the event risk assessment report is signed and completed, the event assessment plan responsible person node is the event administrator node, and the event assessment plan deliverable is the signed event risk assessment report;

[0136] When the event evaluation module 304 automatically drives the event evaluation process based on the preset event evaluation plan and monitors the event evaluation conditions of target events corresponding to different target event screening levels, the event evaluation module 304 is further used to:

[0137] For target events corresponding to different target event screening levels, monitor the event assessment status of the target events described in the event risk assessment report and generate an event risk assessment report;

[0138] Monitor the signing process of the event risk assessment report, send the internally signed event risk assessment report to the reviewer node for review, and determine the review result; wherein, the review result can close the event or wait for the event investigation phase to be completed to trigger the implementation of the measures formulation and release plan.

[0139] See also Figure 4 , Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 4 As shown in , the electronic device 400 includes a processor 410 , a memory 420 and a bus 430 .

[0140] The memory 420 stores machine-readable instructions executable by the processor 410. When the electronic device 400 is running, the processor 410 communicates with the memory 420 via the bus 430. When the machine-readable instructions are executed by the processor 410, the above-mentioned Figure 1 as well as Figure 2 The steps of the full-process control method for civil aircraft continuous airworthiness events in the method embodiment shown solve the problem of incompatibility of multiple businesses in the prior art. The specific implementation method can be found in the method embodiment and will not be repeated here.

[0141] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 as well as Figure 2 The steps of the full-process control method for civil aircraft continuous airworthiness events in the method embodiment shown solve the problem of incompatibility of multiple businesses in the prior art. The specific implementation method can be found in the method embodiment and will not be repeated here.

[0142] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0143] In the several examples provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device examples described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0144] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0145] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0146] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0147] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are only used to distinguish the description and are not to be understood as indicating or implying relative importance.

[0148] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the present application examples, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A method for the whole process control of civil aircraft continuous airworthiness events, characterized in that: The method comprises: Generate an information report based on various information collected on civil aircraft safety incidents during the design, manufacture, use and maintenance of civil aircraft; wherein the civil aircraft safety incidents may include various types of failures, accidents, defects, exceeding technical limitations or deviations that have occurred or been discovered; For the information report sheet, automatically drive the event determination process based on a preset event determination plan, and monitor the determination status of the event determination process; After the event determination process is completed, the event screening process is automatically driven based on a preset event screening plan, and the target event screening level is determined based on the target event determined by the event determination process and the preset event screening level standard; Automatically drive the event assessment process based on the preset event assessment plan, and monitor the event assessment status of target events corresponding to different target event screening levels; Automatically drive the incident investigation process based on the preset incident investigation plan, and monitor the implementation or rejection of incident investigations in the incident investigation process; Automatically drive the measures formulation and release process based on the preset measures formulation and release plan, and monitor the formulation and release of measures based on the results of the incident investigation in the measures formulation and release process; After the incident assessment process and the measures formulation and release process are completed, monitor the incident closure and summary of the incident closure and summary process; The preset event determination plan includes the event determination plan name, event determination plan completion time, event determination plan completion status, event determination plan responsible person node and event determination plan deliverables; wherein, the event determination plan name is the completed event report form, the event determination plan completion status is the event report form signed and completed, the event determination plan responsible person node is the event collector node, and the event determination plan deliverable is the signed and completed event report form; The method of automatically driving the event determination process based on a preset event determination plan for the information report sheet and monitoring the determination status of the event determination process includes: Sending the information report form to the event collector node, obtaining the preliminary event determination result from the event collector node, and monitoring the signing of the event report form under the first preset time constraint; After the event report form is signed, the signed event report form is sent to the event supervisor node, and the event administrator node designated by the event supervisor node is determined; Monitor the subsequent event determination result of the event administrator node under the second preset time constraint, and use the subsequent event determination result to correct the preliminary event determination result to obtain the target event determined by the event determination process; wherein, if the target event is determined to be a CCAR21.5 event, send the event report form to the reviewer node within the preset time; The preset event screening plan includes the event screening plan name, event screening plan completion time, event screening plan completion status, event screening plan responsible person node and event screening plan deliverables; wherein, the event screening plan name is the completed event screening form, the event screening plan completion status is the event screening form signing completion, the event screening plan responsible person node is the operation supervisor node, and the event screening plan deliverable is the signed event screening form; After the event determination process is completed, the event screening process is automatically driven based on a preset event screening plan, and the target event screening level is determined based on the target event determined by the event determination process and the preset event screening level standard, including: After the event determination process is completed, based on the target event determined by the event determination process and the preset event screening level standard, the target event screening level in the event screening list is determined; Monitor the signing process of the event screening form, and send the signed event screening form to the operation supervisor node; The preset event assessment plan includes the event assessment plan name, event assessment plan completion time, event assessment plan completion status, event assessment plan responsible person node and event assessment plan deliverables; wherein, the event assessment plan name is the completed event risk assessment report, the event assessment plan completion status is the event risk assessment report is signed and completed, the event assessment plan responsible person node is the event administrator node, and the event assessment plan deliverable is the signed event risk assessment report; The event evaluation process is automatically driven based on the preset event evaluation plan, and the event evaluation status of target events corresponding to different target event screening levels is monitored, including: For target events corresponding to different target event screening levels, monitor the event assessment status of the target events described in the event risk assessment report and generate an event risk assessment report; Monitor the signing process of the event risk assessment report, send the internally signed event risk assessment report to the reviewer node for review, and determine the review result; wherein, the review result can close the event or wait for the event investigation phase to be completed to trigger the implementation of the measures formulation and release plan.

2. The method according to claim 1, characterized in that The method further comprises: In the case of repeated reporting of the same event and the event not being closed, monitor the merging of the same event reported repeatedly in the event merging process, and determine the execution status of the main event as the final basis after the merger; In the event that an ongoing event needs to be cancelled due to abnormal or objective factors, monitor the event closure process and directly close it and sign the resolution.

3. The method according to claim 1, characterized in that The method further comprises: When the target event determined by the event determination process needs to be updated, information is supplemented for multiple rounds of target events, automatically associated with the event report form to form a complete event, and the event information supplementation status of the event supplement process is monitored.

4. The method according to claim 1, characterized in that The method further comprises: If the operation supervisor node recommends initiating an ad hoc meeting, the signed event screening form will be associated with the minutes of the ad hoc meeting, and the conclusion of the event screening plan will be automatically formed based on the meeting resolution of the ad hoc meeting.

5. A full-process control device for continuous airworthiness events of civil aircraft, characterized in that: The device comprises: An information collection module is used to generate an information report sheet based on various information collected on civil aircraft safety incidents during the design, manufacture, use and maintenance of civil aircraft; wherein the civil aircraft safety incidents may include various types of failures, accidents, defects, technical limitations or deviations that have occurred or been discovered; An event determination module, for automatically driving an event determination process based on a preset event determination plan for the information report sheet, and monitoring the determination status of the event determination process; An event screening module, used to automatically drive the event screening process based on a preset event screening plan after the event determination process is completed, and determine the target event screening level based on the target event determined by the event determination process and the preset event screening level standard; An event evaluation module is used to automatically drive the event evaluation process based on a preset event evaluation plan and monitor the event evaluation status of target events corresponding to different target event screening levels; An event investigation module, used to automatically drive the event investigation process based on a preset event investigation plan, and monitor the situation of conducting or rejecting the event investigation in the event investigation process; A measures formulation and release module, used to automatically drive the measures formulation and release process based on a preset measures formulation and release plan, and monitor the formulation and release of measures based on the results of the incident investigation in the measures formulation and release process; An event closing and summarizing module is used to monitor the event closing and summarizing status of the event closing and summarizing process after the event evaluation process and the measure formulation and release process are completed; The preset event determination plan includes the event determination plan name, event determination plan completion time, event determination plan completion status, event determination plan responsible person node and event determination plan deliverables; wherein, the event determination plan name is the completed event report form, the event determination plan completion status is the event report form signed and completed, the event determination plan responsible person node is the event collector node, and the event determination plan deliverable is the signed and completed event report form; When the event determination module automatically drives the event determination process based on the preset event determination plan for the information report form and monitors the determination status of the event determination process, the event determination module is further used to: Sending the information report form to the event collector node, obtaining the preliminary event determination result from the event collector node, and monitoring the signing of the event report form under the first preset time constraint; After the event report form is signed, the signed event report form is sent to the event supervisor node, and the event administrator node designated by the event supervisor node is determined; Monitor the subsequent event determination result of the event administrator node under the second preset time constraint, and use the subsequent event determination result to correct the preliminary event determination result to obtain the target event determined by the event determination process; wherein, if the target event is determined to be a CCAR21.5 event, send the event report form to the reviewer node within the preset time; The preset event screening plan includes the event screening plan name, event screening plan completion time, event screening plan completion status, event screening plan responsible person node and event screening plan deliverables; wherein, the event screening plan name is the completed event screening form, the event screening plan completion status is the event screening form signing completion, the event screening plan responsible person node is the operation supervisor node, and the event screening plan deliverable is the signed event screening form; After the event determination process is completed, the event screening module automatically drives the event screening process based on a preset event screening plan. When determining the target event screening level based on the target event determined by the event determination process and the preset event screening level standard, the event screening module 303 is further used to: After the event determination process is completed, based on the target event determined by the event determination process and the preset event screening level standard, the target event screening level in the event screening list is determined; Monitor the signing process of the event screening form, and send the signed event screening form to the operation supervisor node; The preset event assessment plan includes the event assessment plan name, event assessment plan completion time, event assessment plan completion status, event assessment plan responsible person node and event assessment plan deliverables; wherein, the event assessment plan name is the completed event risk assessment report, the event assessment plan completion status is the event risk assessment report is signed and completed, the event assessment plan responsible person node is the event administrator node, and the event assessment plan deliverable is the signed event risk assessment report; When the event evaluation module automatically drives the event evaluation process based on the preset event evaluation plan and monitors the event evaluation conditions of target events corresponding to different target event screening levels, the event evaluation module is also used to: For target events corresponding to different target event screening levels, monitor the event assessment status of the target events described in the event risk assessment report and generate an event risk assessment report; Monitor the signing process of the event risk assessment report, send the internally signed event risk assessment report to the reviewer node for review, and determine the review result; wherein, the review result can close the event or wait for the event investigation phase to be completed to trigger the formulation and release plan of measures to take effect.

6. An electronic device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the storage medium communicate via the bus, and the processor executes the machine-readable instructions to perform the steps of any method as claimed in claims 1 to 4.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are executed.

Images