Source data processing system and method for aircraft technical manual development

Abstract

The invention relates to the field of aircraft source data processing, in particular to a source data processing system and method for aircraft technical manual development. The method comprises the following steps of: performing data exchange by using an XML (Extensible Markup Language), realizing unified management of texts, 3D (Three-Dimensional) digital-analog, videos and audios by virtue of an artificial intelligence technology, mapping a technical manual data module Schema and a source data document structure, and further decomposing the technical content of source data into an atomic data set; correlation is established between source data atomic data and data module XML elements according to the mapping relation, the specific data range needed by technical manual development is accurately positioned in a large number of design, engineering and guarantee documents, accurate tracking of the source data change condition is supported, the influence range of source data change on the technical manual is recognized, and the technical manual development efficiency is improved. The interactive electronic technical manual development system is pushed through the task system to implement related changes, and the accuracy and effectiveness of technical contents in the technical manual are powerfully guaranteed.

Description

Technical Field

[0001] The present invention relates to the field of aircraft source data processing, and in particular to a source data processing system and method for developing aircraft technical manuals. Background Art

[0002] The development of aircraft technical publications usually adopts the ATA 100, ATA2200 or S1000D standards, or industry standards that are basically equivalent to the above standards. When the ATA 100 standard is adopted, technical publications are managed with page blocks as the smallest data unit, which is a linear technical publication. Its typical development process is to use word processing software to edit a large number of documents stored in the computer. The ATA2200 standard is an extension of the ATA 100 standard, which supports the use of the SGML language to develop interactive electronic manuals in a digital development system. Its typical development process is to read structured documents compiled in the SGML language in the digital development system for editing, select a style sheet, and generate interactive documents that support interactive browsing and operation through the publishing engine. The S1000D standard is currently the most advanced and popular technical publication standard in the world. It uses the XML language commonly used in the computer field and manages data in a public source database with data modules as the smallest data unit. Its typical development process is to read data modules compiled in the XML language from the public source database in the digital development system for editing, flexibly select the required data modules to customize and publish technical publications, and even interactively browse and operate the elements at all levels in the data module. It has good data reusability and can achieve more powerful interactive functions.

[0003] At present, the aircraft technical publication development software that supports the above standards mainly focuses on entering the technical content into the software system in the form pre-specified by each standard. It does not pay enough attention to how to convert source data into technical content and how to effectively track the implementation of source data changes in technical content. It usually relies on developers to manually collect, analyze and convert source data. The correctness, completeness and applicability of technical content usually depend on personal experience, ability and attitude. The composition and structure of modern aircraft systems are usually more complex, and the frequency of technical status changes is also increasing. In particular, some areas are affected by specific mission requirements, and improvements and modifications are frequent. The timeliness of the implementation of technical status is quite high. Simply relying on manual processing often leads to untimely changes, omissions and content errors in technical publications.

[0004] In order to fully tap the potential of aircraft technical publication development software, effectively process source data and track its changes, it is necessary to establish a software system to manage the various source data required for technical publication development in an organic manner, decompose the source data in an intelligent way, extract effective information and dynamically associate it with the technical publication structure. Summary of the invention

[0005] Purpose of the Invention

[0006] The present invention provides a source data processing system for the development of aircraft technical manuals, which solves the problem of lack of effective processing means for the required source data in the process of technical manual development and the reliance on manual processing of technical content by developers. It implements digital management of the source data required for the development of technical manuals, establishes a dynamic association between the source data and the content of the technical manuals, breaks the information gap between source data processing and technical manual development, and effectively supports the development of civil aircraft technical manuals.

[0007] To achieve the above-mentioned purpose, the present invention adopts a source data processing system for the development of civil aircraft technical manuals, uses XML language for data exchange, and uses artificial intelligence technology to achieve unified management of text, 3D digital models, videos, and audios. The technical manual data module Schema is mapped to the source data document structure, and then the source data technical content is decomposed into an atomic data set. An association is established between the source data atomic data and the data module XML elements according to the mapping relationship. The specific data range required for the development of the technical manual is accurately located in a large number of design, engineering, and support documents, and the accurate tracking of source data changes is supported. The scope of influence of source data changes on the technical manual is identified, and the interactive electronic technical manual development system is promoted to implement relevant changes through the task system, which effectively guarantees the accuracy and effectiveness of the technical content in the technical manual.

[0008] Technical Solution

[0009] A source data processing system for aircraft technical manual development includes 7 sub-modules: project management subsystem, content template subsystem, data association subsystem, data management subsystem, implementation management subsystem, document structure subsystem and data exchange subsystem.

[0010] The project management subsystem is used to centrally manage the source data required for the development of aircraft technical manuals, and supports the implementation of data creation and update functions through automatic data exchange or manual methods through manual operation. It supports the establishment of projects by aircraft model, and each project corresponds to an aircraft model, including technical manual structure information. Through the content template subsystem and data association subsystem, the association relationship between technical manuals and source data is managed.

[0011] The content template subsystem is used to manage the content templates corresponding to each type of data module in the technical manual. It supports the implementation of template creation and template update functions through automatic data exchange and manual human operation, and supports the association of content templates with data modules.

[0012] The data association subsystem is used to establish a mapping relationship between the technical manual structure information and the source data. It supports reading the technical manual structure information from the project management subsystem, and uses artificial intelligence tools based on large language models to obtain the relevant source files and atomic data sets required for each data module from the document structure subsystem through keywords, and establish the corresponding relationship between each element of the data module content template structure and each atomic data of the source file.

[0013] The data management subsystem is the data layer for source data management. It is used to store, process and manage the data created by each subsystem. It provides a data reuse mechanism, which can reuse duplicate data between batches of the same type of aircraft to free up storage space and reduce processing difficulty. It supports data self-inspection and data mining.

[0014] The implementation management subsystem is used to track the implementation of source data in the technical manual and supports the information push mechanism. The implementation management subsystem manages the tasks of the source files throughout their life cycle, starting with the creation of source data by the document structure subsystem, and using the information push mechanism to track the implementation of source data and its subsequent changes in the interactive electronic technical manual development system.

[0015] The document structure subsystem is used to parse the source data document structure and form a structured atomic data set that can be used for dynamic association. The source file is obtained through the data management subsystem, combined with the source file template, and the source file document structure is established by using artificial intelligence tools based on a large language model to perform data recognition, decompose the source file into individual atomic data level by level, and form a structured atomic data set.

[0016] The data exchange subsystem uses the technical manual source data management system as a bridge to exchange data between the interactive electronic technical manual development system and other design or manufacturing information systems that generate source data. The data exchange subsystem obtains source data from other design or manufacturing information systems and stores it in the data management subsystem in the technical manual source data management system for other subsystems to process to form data, relationships, tasks and other information, and pushes it to the relevant functional modules in the technical interactive electronic technical manual development system to assist and track the development of technical manuals.

[0017] A source data processing method for aircraft technical manual development includes a source data acquisition and processing method, and a source data implementation application and feedback method.

[0018] The source data acquisition and processing method includes the following steps:

[0019] Step 1: The project management subsystem synchronously reads the structured technical manual information in the interactive electronic manual development system through the data interaction subsystem, and synchronously creates a technical manual development source data processing project according to the aircraft model, builds structured information, and displays the project content from a dual perspective of source data perspective and technical manual structure perspective.

[0020] Step 2: Obtain the XMLSchema structured information of various data modules in the interactive electronic manual development system through the content template subsystem, or manually establish the structured content templates of various data modules required for this project.

[0021] 3) The content template subsystem reads the XML Schema architecture of various types of data modules in the interactive electronic manual development system through the data exchange subsystem, converts it into a readable content template through the template creation function, and updates the template in real time through the template update function.

[0022] 4) Manually customize and trim the XML Schema architecture of each type of data module one by one through the template creation function, convert it into a readable content template, and update the template in real time through the template update function.

[0023] Step 3: The data management subsystem obtains the aircraft design or manufacturing source data files through the data exchange subsystem and stores them in the data management subsystem.

[0024] 5) Data management subsystem, which obtains data from the project design or manufacturing information system through the data exchange subsystem, including project management information, technical manual structure information, technical manual content template, technical manual source data, and the relationship between the two.

[0025] 6) The data management subsystem tracks the differences between the technical status of each batch of aircraft, and directly realizes the automatic reuse of related data for the parts with the same technical status.

[0026] 7) The data management subsystem mines the source data, extracts and splices the atomic data sets of the source data files, and creates a modified source data file without redundant data according to the content template, which can be directly used to assist the development of technical manuals.

[0027] 8) The data management subsystem conducts self-inspection of data and implements historical version management for all data. Through the historical version review of data, it checks whether the source data and content templates are missing, and whether the association relationships are confusing.

[0028] And provide highlighted reminders.

[0029] The method for implementing application and feedback of source data includes the following steps:

[0030] Step 4: The implementation management subsystem obtains the creation information of the source data file from the data management subsystem, and simultaneously creates the technical manual development or update task information.

[0031] Step 5: The document structure subsystem identifies the source data stored in the data management subsystem and creates a structured document. It also parses the document structure to form a structured atomic data set that can be dynamically associated with the content template elements of the technical manual.

[0032] 5) The document structure subsystem obtains the source data file from the data management subsystem, performs intelligent analysis on the source data file according to the source data file template of the project design or manufacturing information system, and establishes the source file document structure.

[0033] 6) The technical staff adjusts the granularity of the source file document structure through the correction function of the document structure subsystem, and adds keywords to each atomic data as needed to facilitate association with the content template elements.

[0034] 7) Through the comparison function of the document structure subsystem, the historical data of the source file document structure is compared with the document structure of the same type of source file, and the omissions, contradictions, inconsistent granularity and other problems in the comparison results are exchanged with the project design or manufacturing information system, used as a technical document pre-receiver, and early warning of the integrity of technical documents that have been compiled but not yet issued in the project design or manufacturing information system.

[0035] 8) The document structure subsystem parses the source file document structure and decomposes the source data obtained from the data management subsystem into individual atomic data level by level to form a structured atomic data set. The atomic data set is described in XML language, supports independent storage of any atomic data, supports reference to atomic data through the source file document structure, and displays the hierarchical relationship between elements.

[0036] Step 6: The data association subsystem establishes the association relationship between the structural information of the technical manual of this project and the structured atomic data set through keywords.

[0037] 5) Through the mapping function in the data association subsystem, establish the association information between the data module and the source data file.

[0038] 6) Through the mapping function in the data association subsystem, the association information between the content template elements and the atomic data of the source data is established.

[0039] 7) Through the correction function in the data association subsystem, the technical staff manually checks the correctness of the association relationship, and cancels or adds the association relationship as needed, and manually corrects the association relationship between the data module and the source data file, and the association relationship between the content template element and the atomic data.

[0040] 8) Through the difference prompt function of the data association subsystem, the differences between the existing project data and the historical versions are tracked and highlighted to form difference reminder information, which is pushed to the actual management subsystem, and the interactive electronic technical manual development system is notified through the data exchange subsystem to update the technical manual.

[0041] Step 7: The implementation management subsystem obtains source data file creation information from the data management subsystem and creates a technical manual development or update task.

[0042] 3) Push the technical manual tasks, associated relationships and atomic data sets to the interactive electronic manual development system through the data exchange subsystem for use in the development or update of the interactive electronic manual.

[0043] 4) The associated difference information pushed by the data association subsystem is pushed to the interactive electronic manual development system through the data exchange subsystem for use in the development or update of the interactive electronic manual.

[0044] Step 8: The interactive electronic manual development system feedback is read through the data exchange subsystem and other information systems (such as aircraft design system or manufacturing information system) are notified as needed to improve the source data file.

[0045] The beneficial effects of this application are:

[0046] The present invention relates to a source data processing system and method for the development of aircraft technical manuals. Compared with the prior art solutions, the source data required for the development of the technical manuals is stored in a dedicated database for unified management. By classifying, decomposing and integrating the source data, the information required therein is combined with the technical manual to establish a mapping relationship, which can support developers to quickly develop the content of the technical manual. At the same time, it can track the changes in the source data, identify the impact of the changes in the source data on the technical content of the technical manual and issue a change reminder, and manage the development of the technical manual and the required source data in a linked manner. At the same time, artificial intelligence tools are introduced to significantly improve data processing efficiency. The entire work flow has a high degree of intelligence and automation, and can effectively ensure the timeliness of the implementation of technical status changes in the technical manual in a relatively low-cost manner, and properly reduce the probability of problems such as the technical manual not being consistent with the actual content and the slow implementation of the technical status from the source. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 A schematic diagram of the structure of a source data processing system for developing a civil aircraft technical manual provided by the present invention;

[0048] Figure 2 A schematic diagram of the workflow of the project management subsystem provided by the present invention;

[0049] Figure 3 A schematic diagram of the workflow of the content template subsystem provided by the present invention;

[0050] Figure 4 A schematic diagram of the workflow of the data association subsystem provided by the present invention;

[0051] Figure 5 A schematic diagram of the workflow of the implementation management subsystem provided by the present invention;

[0052] Figure 6 A schematic diagram of the workflow of the document structure subsystem provided by the present invention;

[0053] Figure 7 The present invention provides a flow chart of an exemplary method of a source data processing system and method for developing a civil aircraft technical manual. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical scheme and advantages of the implementation of the present invention clearer, the technical scheme in the embodiment of the present invention will be described in more detail in combination with the embodiment of the present invention. In the example, the same or similar reference numerals throughout represent the same or similar originals or elements with the same or similar functions. The described embodiments are part of the embodiments of the present invention, not all of them. The embodiments described below by reference are exemplary and intended to be used to explain the present invention, and should not be construed as limitations on the present invention. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in the field without making creative work belong to the scope of protection of the present invention. The following is a detailed description in combination with the embodiments of the present invention.

[0055] according to Figure 1 As shown, this embodiment provides a technical manual source data processing system, which is composed of a project management subsystem 100, a content template subsystem 200, a data association subsystem 300, a data management subsystem 400, an implementation management subsystem 500, a document structure subsystem 600 and a data exchange subsystem 700.

[0056] The project management subsystem 100 is used to uniformly manage the source data required for the development of aircraft technical manuals, and supports the establishment of projects by aircraft model, with each project corresponding to an aircraft model. The project management subsystem 100 provides data creation, data update, and data display functions. The data creation function is used to create technical manual structure information in each project. The data update function is used to maintain the technical manual structure information, such as performing deletion, replacement, and upgrade. The project management subsystem 100 supports the automatic mode of data exchange and the manual mode of implementing data creation and data update functions through manual operation.

[0057] according to Figure 2As shown, the project management subsystem includes a data creator 110, a data updater 120 and a data presenter 130. The project subsystem 100 can read structured technical manual information from the interactive electronic manual development system 800 through the data exchange subsystem 700, create technical manual structure information 160 through the data creator 110, and update it in real time through the data updater 120, or manually create technical manual structure information 160 one by one through the data creator 110 and update it regularly through the data updater 120.

[0058] The specific form of the technical manual structure information 160 in the project management subsystem 100 depends on the standard on which the technical manual is based. In this embodiment, the technical manual is based on the S1000D standard. The technical manual is organized in the form of data modules, and each data module has a unique data module code. Therefore, the project management subsystem 100 adopts the standard numbering system coding rules provided by the S1000D standard to construct the product structure decomposition for comprehensive logistics support purposes. The product structure decomposition includes four levels: system, subsystem, sub-subsystem, and component. The four levels are sequentially expanded in a tree form. The data module code of each data module 180 in the technical manual is associated with the product structure decomposition. According to the granularity of the data module 180 in the technical manual, the data module code may be associated with the above four levels respectively, thereby forming a data module requirement list 170 as the main component of the technical manual structure information 160.

[0059] The data displayer 130 calls the association displayer 330 through the data association subsystem 300 to display the association relationship 361 between the data module 180 and the source data file 660 and the association relationship 362 between the content template element 261 and the atomic data 664 in the technical manual structure information 160, which is divided into the technical manual structure perspective 131 and the source data file perspective 132.

[0060] When the data displayer 130 displays from the technical manual structure perspective 131, the technical manual structure information 160, that is, the data module requirement list 170 associated with the product structure decomposition is first displayed, and then the source data file 660 associated with each data module 180 in the list is displayed through the association relationship 361 between the data module 180 and the source data file 660, and then the association relationship 362 between the content template element 261 and the atomic data 664 is displayed. When the data displayer 130 displays from the source data file perspective 132, the source data file list 670 is first displayed, and then the data module 180 associated with each source data file 660 in the list is displayed through the association relationship 361 between the data module 180 and the source data file 660, and then the association relationship 362 between the content template element 261 and the atomic data 664 is displayed. The data displayer 130 supports the screening and display of different batches of aircraft of the same model according to the difference in technical status in each project, and supports the folding, expansion, query and screening of the data module requirement list 170 and the source data file list 670.

[0061] The content template subsystem 200 is used to manage the content templates 260 corresponding to different types of data modules 180 of the technical manual. The S1000D standard provides common XML Schema for different types of data modules 180. The XML Schema specifies the structured document content composition of the data module 180, including the configuration of elements and attributes at each level. When developing the technical manual of each model, it is necessary to customize the XML Schema according to the actual situation to form a structured content template 260, which contains the required content template elements 261. The content template subsystem 200 supports the implementation of template creation and template update functions in an automatic way through data exchange and in a manual way through manual operation.

[0062] according to Figure 3 As shown, the content template subsystem 200 provides a template creator 210, a template updater 220 and a template presenter 230. The content template subsystem 200 can also read the XML Schema architecture 810 of each type of data module in the interactive electronic manual development system 800 through the data exchange subsystem 700, convert it into a readable content template 260 through the template creator 210 and update it in real time through the template updater 220, or manually customize and trim the XML Schema architecture 810 of each type of data module one by one through the template creator 210, convert it into a readable content template 260 and update it in real time through the template updater 220.

[0063] The template displayer 230 provides a display page for content templates 260, obtains technical manual structure information 160 through the project management subsystem 100, and associates the content template 260 with the data module 180 in the data module requirement list 170 for display. The template displayer 230 supports batch setting of content templates 260 for data modules 180, and can be the same content template 260 for multiple data modules 180 with the same information code. It also supports arbitrarily selecting data modules 170 in the product structure decomposition to associate content templates 260. The content template subsystem 200 displays the data module requirement list 170 established by the project management subsystem 100 through the content template display page 231. Clicking any data module 180 in the list will display the corresponding content template 260. Any content template element 261 in the content template 260 has a unique number, which is reflected on the left side of the content template 260. Each number points to the numbered content template element 261, and a rectangular box contains the numbered content template element 261. The content template element 261 and the number are linked by a straight line.

[0064] The data association subsystem 300 is used to establish a mapping relationship between the technical manual structure information 160 and the related source data files 660. Figure 4 As shown, the data association subsystem 300 includes a mapping associator 310 , an association corrector 320 , an association displayer 330 , and a difference prompter 340 .

[0065] The mapping associator 310 has a built-in artificial intelligence tool based on a large language model, which reads the technical manual structure information 160 from the project management subsystem 100, obtains the SNS, information code, location code and other contents from the data module code of each data module 180 in the data module requirement list 170, and analyzes and determines the required technical information, uses the technical information as a keyword 311 to obtain the relevant source data file 660 in the document structure subsystem 600 through intelligent search and matching, and establishes an association relationship 361 between the data module 180 and the source data file 660. The mapping associator 310 obtains the manual template 260 corresponding to each data module 180 from the project management subsystem 100 through the content template subsystem 200, and based on the corresponding relationship between the data module 180 and the source data file 660, uses the content template element 261 of the manual template 260 to obtain the atomic data 664 of the relevant source data file 660 through intelligent search and matching, and establishes an association relationship 362 between the content template element 261 and the atomic data 664.

[0066] The association corrector 320 introduces a manual correction link and provides an interactive operation window, allowing technicians to check the correctness of the association relationship and cancel or add the association relationship as needed. The association corrector 320 first corrects the association relationship 361 between the data module 180 and the source data file 660, and then corrects the association relationship 362 between the content template element 261 and the atomic data 664.

[0067] The association displayer 330 supports display from the data module 180 to the source data file 660, and display from the source data file 660 to the data module 180. It supports multiple display formats, including lists, text boxes, and knowledge graph formats, and supports association display at various levels according to the structure of the content template 260 and the source data file 660.

[0068] The difference prompter 340 can read the association relationship 361 between the data module 180 and the source data file 660 and the association relationship 362 between the content template element 261 and the atomic data 664, and track the historical version difference of the atomic data 664 and highlight it, and form the atomic data difference reminder information 341 based on the historical version difference, push it to the implementation management subsystem 500, and notify the interactive electronic technical manual development system 800 to update the technical manual through the data exchange subsystem 700. The difference prompter 340 can also track the historical version difference of the content template element 261 and highlight it, and form the content template difference reminder information 342 based on the historical version difference, push it to the implementation management subsystem 500, and notify the document structure subsystem 600 to redefine the document structure granularity.

[0069] The data management subsystem 400 is the data layer of the technical manual source data processing system, which is used to store, process and manage the data created by each subsystem, including project management information, technical manual structure information, technical manual content templates, technical manual source data, and the relationship between the two. The data management subsystem 400 provides a data reuse mechanism, which can accurately track the differences between the technical status of each batch of aircraft, and directly realize the automatic reuse of related data for the same technical status. The data management subsystem 400 provides a data mining mechanism to extract and splice the atomic data sets of the source data files, and create a modified source data file without redundant data according to the content template 260, which can be directly used to assist the development of technical manuals. The data management subsystem 400 provides a data self-checking mechanism to implement historical version management for all data. Through the historical version review of the data, it checks whether the source data and content templates are missing, whether the relationship is chaotic, and provides a reminder function.

[0070] The implementation management subsystem 500 is used to track the implementation of the source data file 660 in the technical manual and supports the information push mechanism. Figure 5As shown, the task subsystem 500 includes a task creator 510 , an information pusher 520 , and a feedback processor 530 .

[0071] The implementation management subsystem 500 obtains the source data file creation information 460 of the source data file 660 from the data management subsystem 400, and creates a technical manual update task 560 through the task creator 510. The technical manual update task 560 is divided into a structure analysis 561, a data association 562, and a change implementation 563. The information pusher 520 pushes the structure analysis 561 and the data association 562 to the document structure subsystem 600 and the data association subsystem 300 in sequence. After the data association 562 is completed, the information pusher 520 pushes the push change implementation 563 to the interactive electronic manual development system 800 through the data exchange subsystem 700, and provides the association relationship 361 between the data module 180 and the source data file 660, the association relationship 362 between the content template element 261 and the atomic data 664, and the atomic data 664.

[0072] The feedback processor 530 reads the technical manual development progress 860 and feedback 870 in the interactive electronic manual development system 800 through the data exchange subsystem 700, and pushes the feedback 870 to the information pusher 520. The information pusher 520 notifies the design or manufacturing information system 900 that generates the source data to update the data as needed through the data exchange subsystem 700.

[0073] The document structure subsystem 600 is used to parse the source data of the technical manual. The source data of the technical manual comes from various technical documents of the aircraft. The technical documents are usually created in the information system using a specified template and have recognizable document identifiers and good formats. The document structure subsystem 600 has a built-in artificial intelligence tool based on a large language model, which can perform data recognition on the source data to establish a structured document structure, and parse the document structure to form a structured atomic data set that can be used to dynamically associate with the content template elements of the technical manual. Figure 6 As shown, the document structure subsystem 600 includes a document structure identifier 610 , a document structure corrector 620 , a document structure storage 630 and a document structure parser 640 .

[0074] The document structure identifier 610 obtains the source data file 660 from the data management subsystem 400, obtains the source data file template 910 from the design or manufacturing information system 900 according to the document identifier 661 of the source data file 660, and performs intelligent analysis on the source data file 660 in combination with the source data file template 910 to establish a source file document structure 662. The source file document structure 662 is structured data of the relationship information between the smallest data units formed by decomposing the source data file 660 level by level into the smallest data units based on the source data file template 910.

[0075] The document structure corrector 620 receives the source file document structure 662 from the document structure identifier 610. The document structure corrector 620 provides the source file document structure 662 in a tree-like exploded diagram display mode, so that the technician can adjust the granularity of the source file document structure 662 and add keywords of each atomic data as needed to facilitate association with the content template element 261.

[0076] The document structure storage 630 stores the source file document structure 662 optimized by the document structure corrector 620, provides a source file document structure 662 historical data comparison function and a source file document structure 662 comparison function of the same type, can identify omissions, contradictions, inconsistent granularity and other problems in the source file document structure 662, and can also exchange data with the design or manufacturing information system 900, and be used as a technical document pre-receiver to issue early warnings on the integrity of technical documents that have been compiled but not yet issued in the design or manufacturing information system 900.

[0077] The document structure parser 640 uses the source file document structure 662 provided by the document structure storage 630 to decompose the source data file 660 obtained from the data management subsystem 400 into each atomic data 664 level by level, forming a structured atomic data set 663, each atomic data identifier 664 is used for each indivisible independent self-contained data unit. The atomic data set 663 is described using the XML language, supports independent storage of any atomic data 664, supports reference to atomic data through the source file document structure 662, and displays the hierarchical relationship between each element.

[0078] The data exchange subsystem 700 is used to exchange data between the technical manual source data processing system and the interactive electronic technical manual development system, and between the technical manual source data processing system and other information systems that generate source data. The data exchange subsystem 700 directly establishes a connection with multiple subsystems in the interactive electronic technical manual development system 800 to achieve information acquisition and push. When the data exchange subsystem 700 exchanges data between the design or manufacturing information system 900, it adopts different processing methods according to the file types such as text, graphics, digital model, video, audio, etc., and stores it in the data management subsystem 400 by reading the historical data change version or adding a new node. For packaged data that does not support intelligent recognition, it provides a manual creation of description documents. The description document adopts a unified template to realize the clear relationship between the packaged data and the technical manual structure information through intelligent recognition of the description document.

[0079] like Figure 1 and Figure 7 As shown, a method for implementing a source data processing system for developing a civil aircraft technical manual includes the following steps:

[0080] Step 1: Create a technical manual development project based on the aircraft model and build the technical manual structure information;

[0081] Step 2: Create content templates for the data modules included in the technical manual structure information;

[0082] Step 3: Receive source data files from other information systems and store them in the data management subsystem;

[0083] Step 4: Obtain source data files through the data management subsystem and establish technical manual development or update tasks;

[0084] Step 5: Parse the source data file to form a source data file document structure and a source data file atomic data set;

[0085] Step 6: Establish the association relationship between the content template and the document structure of the source data file;

[0086] Step 7: Pushing the association relationship and atomic data set to the interactive electronic manual development system;

[0087] Step 8: Read the feedback from the interactive electronic manual development system and notify other information systems to improve the source data files as needed.

[0088] It is understood by those skilled in the art that, unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as the general understanding of ordinary technicians in the field to which the present invention belongs. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and unless defined as here, will not be interpreted with idealized or overly formal meanings. The specific implementation methods described above further describe the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the present invention. Within the spirit and principle of the present invention, any technician familiar with the profession may use the above disclosed technical content to change or modify it into an equivalent embodiment of equivalent changes for application in other fields, but any simple modification, equivalent change and modification made to the above embodiments according to the technical essence of the present invention without departing from the technical solution content of the present invention, any modification, equivalent replacement, improvement, etc., made according to the technical essence of the present invention, should be included in the protection scope of the present invention.

Claims

1. A source data processing system for aircraft technical manual development, characterized in that: It includes 7 sub-modules: project management subsystem, content template subsystem, data association subsystem, data management subsystem, implementation management subsystem, document structure subsystem and data exchange subsystem; The project management subsystem is used to uniformly manage the source data required for the development of aircraft technical manuals, and supports the implementation of data creation and update functions through automatic data exchange or manual methods through manual operation; it supports the establishment of projects according to aircraft models, each project corresponds to an aircraft model, contains technical manual structure information, and manages the association relationship between technical manuals and source data through the content template subsystem and data association subsystem; The content template subsystem is used to manage the content templates corresponding to each type of data module in the technical manual; it supports the implementation of template creation and template update functions in an automatic way through data exchange and in a manual way through manual operation, and supports the association of content templates with data modules; The data association subsystem is used to establish a mapping relationship between the technical manual structure information and the source data; Supports reading technical manual structure information from the project management subsystem. Through keywords, it uses artificial intelligence tools based on large language models to obtain relevant source files and atomic data sets required for each data module from the document structure subsystem, and establishes the corresponding relationship between each element of the data module content template structure and each atomic data of the source file. The data management subsystem is the data layer for source data management. It is used to store, process and manage the data created by each subsystem. It provides a data reuse mechanism, which can reuse duplicate data between batches of the same type of aircraft to free up storage space and reduce processing difficulty. It also supports data self-checking and data mining. The implementation management subsystem is used to track the implementation of source data in the technical manual and supports the information push mechanism. The implementation management subsystem manages the tasks of the source files throughout their life cycle, starting with the creation of source data by the document structure subsystem, and using the information push mechanism to track the implementation of source data and its subsequent changes in the interactive electronic technical manual development system. The document structure subsystem is used to parse the source data document structure and form a structured atomic data set that can be used for dynamic association. The source file is obtained through the data management subsystem, and combined with the source file template, an artificial intelligence tool based on a large language model is used to perform data recognition to establish the source file document structure, and the source file is decomposed into each atomic data level by level to form a structured atomic data set. The data exchange subsystem uses the technical manual source data management system as a bridge to exchange data between the interactive electronic technical manual development system and other design or manufacturing information systems that generate source data; The data exchange subsystem obtains source data from other design or manufacturing information systems and stores it in the data management subsystem of the technical manual source data management system for other subsystems to process to form data, relationships, and task information, which is then pushed to the relevant functional modules in the technical interactive electronic technical manual development system to assist and track the development of the technical manual.

2. The source data processing method for aircraft technical manual development according to the processing system of claim 1, characterized in that: Includes source data acquisition and processing, source data implementation, application and feedback.

3. The source data processing method according to claim 2, characterized in that: The source data acquisition and processing includes the following steps: Step 1: The project management subsystem synchronously reads the structured technical manual information in the interactive electronic manual development system through the data interaction subsystem, and synchronously creates a technical manual development source data processing project according to the aircraft model, builds structured information, and displays the project content from a dual perspective of source data perspective and technical manual structure perspective.

4. The source data processing method according to claim 3, characterized in that: Step 2: Obtain the XML Schema structured information of various data modules in the interactive electronic manual development system through the content template subsystem, or manually establish the structured content templates of various data modules required for this project through manual operation; 1) The content template subsystem reads the XML Schema architecture of various types of data modules in the interactive electronic manual development system through the data exchange subsystem, converts it into a readable content template through the template creation function, and updates the template in real time through the template update function; 2) The XML Schema architecture of each type of data module is manually customized and trimmed one by one through the template creation function, converted into a readable content template, and the template is updated in real time through the template update function.

5. The source data processing method according to claim 4, characterized in that: Step 3: The data management subsystem obtains the aircraft design or manufacturing source data file through the data exchange subsystem and stores it in the data management subsystem; 1) Data management subsystem, which obtains data from the project design or manufacturing information system through the data exchange subsystem, Including project management information, technical manual structure information, technical manual content template, technical manual source data, and the correlation data between the two; 2) The data management subsystem tracks the differences in technical status between batches of aircraft and, for parts with the same technical status, Directly realize automatic reuse of related data; 3) The data management subsystem mines the source data, extracts and splices the atomic data sets of the source data files, and creates a transformed source data file without redundant data according to the content template, which can be directly used to assist in the development of technical manuals; 4) The data management subsystem performs self-inspection on the data and implements historical version management on all data. Through the review of historical versions of the data, it checks whether the source data and content templates are missing, whether the association relationships are confusing, and provides highlighted reminders.

6. The source data processing method according to claim 5, characterized in that: The implementation, application and feedback of source data include the following steps: Step 4: The implementation management subsystem obtains the creation information of the source data file from the data management subsystem, and simultaneously creates the technical manual development or update task information.

7. The source data processing method according to claim 6, characterized in that: Step 5: The document structure subsystem identifies the source data stored in the data management subsystem and creates a structured document; and parses the document structure to form a structured atomic data set that can be dynamically associated with the content template elements of the technical manual; 1) The document structure subsystem obtains the source data file from the data management subsystem, performs intelligent analysis on the source data file according to the source data file template of the project design or manufacturing information system, and establishes the source file document structure; 2) The technician adjusts the granularity of the source file document structure through the correction function of the document structure subsystem. Add keywords to each atomic data as needed to make it easier to associate with content template elements; 3) Through the comparison function of the document structure subsystem, the historical data of the source file document structure is compared with the document structure of the same type of source files, and the omissions, contradictions, and inconsistent granularity problems in the comparison results are exchanged with the project design or manufacturing information system, used as a technical document pre-receiver, and early warning of the integrity of technical documents that have been compiled but not yet issued in the project design or manufacturing information system; 4) The document structure subsystem parses the source file document structure, and decomposes the source data obtained from the data management subsystem into individual atomic data level by level to form a structured atomic data set; the atomic data set is described using XML language, supports independent storage of any atomic data, supports referencing atomic data through the source file document structure, and displays the hierarchical relationship between elements.

8. The source data processing method according to claim 7, characterized in that: Step 6: The data association subsystem establishes the association relationship between the structural information of the technical manual of this project and the structured atomic data set through keywords; 1) Establish the association information between the data module and the source data file through the mapping function in the data association subsystem; 2) Establishing the association information between the content template elements and the atomic data of the source data through the mapping function in the data association subsystem; 3) Through the correction function in the data association subsystem, the technicians manually check the correctness of the association relationship, cancel or add the association relationship as needed, and manually correct the association relationship between the data module and the source data file, and the association relationship between the content template element and the atomic data; 4) Through the difference prompt function of the data association subsystem, the differences between the existing project data and the historical versions are tracked and highlighted to form difference reminder information, which is pushed to the actual management subsystem, and the interactive electronic technical manual development system is notified through the data exchange subsystem to update the technical manual.

9. The source data processing method according to claim 8, characterized in that: Step 7: The implementation management subsystem obtains the source data file creation information from the data management subsystem and creates a technical manual development or update task; 1) Push the technical manual tasks, associations and atomic data sets to the interactive electronic manual development system through the data exchange subsystem for use in the development or update of the interactive electronic manual; 2) The associated difference information pushed by the data association subsystem is pushed to the interactive electronic manual development system through the data exchange subsystem for use in the development or update of the interactive electronic manual.

10. The source data processing method according to claim 9, characterized in that: Step 8: Read the interactive electronic manual development system feedback through the data exchange subsystem and notify other information systems to improve the source data file as needed.

Images