Multi-level agile multiplexing-oriented digital maintenance manual information model construction method

Abstract

The invention provides a multi-level agile multiplexing-oriented digital maintenance manual information model construction method. The method comprises the steps of determining maintenance manual planning contents; basic information related to maintenance is collected; performing multi-level multiplexing on the maintenance themes, the maintenance information units and the information elements, and transmitting the reusable maintenance themes, the maintenance information units and the information elements to a manual making step; making a maintenance manual on the basis of collecting basic information related to maintenance and reusable maintenance themes, maintenance information units and information elements; and maintaining and updating the maintenance manual according to the technical state change and the user use feedback information. According to the method, the situation that the information structure and the content architecture are inconsistent and nonstandard in the compilation process of the maintenance manual can be reduced; and meanwhile, the problems that the requirement analysis is not perfect enough and the technical content verification is not sufficient enough when the maintenance manual is compiled are solved, the manual analysis and cleaning work is reduced, and the usability of the maintenance manual is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of electronic equipment maintenance, and in particular to a method for constructing a digital maintenance manual information model oriented to multi-level agile reuse. Background Art

[0002] Maintenance manuals are an important part of the use information of electronic equipment. They are the basic basis for guiding users to use and maintain equipment, and are also important supporting materials for correctly performing maintenance operations when a fault occurs. With the continuous advancement of modern technology, the hardware composition and functional performance of electronic equipment are becoming more and more complex and intelligent. Users have higher and higher requirements for the completeness and granularity of maintenance manuals. Traditional paper maintenance manuals have problems such as incomplete information, weak operation guidance, and difficult iterative updates. Digital maintenance manuals have gradually become the mainstream of technical information.

[0003] However, currently, digital maintenance manuals lack standardized information model guidance, and the information structure and content architecture are inconsistent and non-standard. At the same time, when compiling maintenance manuals, the demand analysis is often not perfect, the technical content verification is not sufficient, and the maintenance manuals are limited by the technical capabilities and maintenance experience of the writers, and cannot provide a good guide for the technical operations of maintenance personnel. In fact, there are similarities between the system composition, functional performance and hardware structure of similar electronic equipment in the same field, and the maintenance solutions are also referenceable. However, the reuse of maintenance manuals currently requires a lot of manual analysis and cleanup work, and there is an urgent need for an intelligent tool and method to guide the rapid reuse and construction of maintenance manuals. Summary of the invention

[0004] The present invention aims to provide a method for constructing a digital maintenance manual information model for multi-level agile reuse, so as to solve the problem that digital maintenance manuals for electronic equipment are difficult to construct and reuse.

[0005] The present invention provides a method for constructing a digital maintenance manual information model for multi-level agile reuse, comprising the following steps:

[0006] S1, Manual planning: determine the planning content of the maintenance manual;

[0007] S2, information preparation: collect basic information related to maintenance;

[0008] S3, manual reuse: perform multi-level reuse of maintenance topics, maintenance information units and information elements, and pass the reusable maintenance topics, maintenance information units and information elements to the manual production step;

[0009] S4, manual production: based on the collection of basic information related to maintenance and reusable maintenance topics, maintenance information units and information elements, the maintenance manual is produced;

[0010] S5, Manual Update: Maintain and update the maintenance manual according to the changes in the technical status and the user feedback information.

[0011] Further, step S1 includes:

[0012] Determine the expected usage locations and scenarios of the maintenance manual, and classify and grade the target users of the maintenance manual according to their specialties, skills, experience, etc.

[0013] Confirm the content of the maintenance manual according to the target users and usage scenarios of the maintenance manual, and determine the display form and interaction functions of the maintenance manual according to the content of the maintenance manual and the display device of the maintenance manual.

[0014] Estimate the production cost and cycle of the maintenance manual on the basis of maximizing information reuse.

[0015] Further, in step S2, the basic information of the maintenance manual includes maintenance object information, maintenance plan, maintenance resource information, maintenance safety information, and other information.

[0016] Further, step S3 includes:

[0017] Based on the planned content of the maintenance manual, perform multi-level reuse of maintenance topics, maintenance information units, and information elements, and give priority to directly reusing similar maintenance topics; when no completely reusable maintenance topic can be found, consider partial reuse, that is, reuse at the maintenance information unit level; when there is no reusable maintenance information unit, reuse some information elements; among them, an association with a single source information should be established during reuse.

[0018] Further, let the set of maintenance topics included in the current maintenance manual be R, and select the set of maintenance manuals {R1, R2,.., R n} of similar products in similar fields, then the reusable maintenance manual domain is R n =R1 UR2,...,UR n ;

[0019] For the maintenance topic r i in the maintenance manual planned by the manual, the maintenance manual requirements are For its maintenance manual requirements are m < n, there exists

[0020]

[0021] Among them, is the similarity calculation method, η t is the contribution rate parameter, which is related to the classification of the maintenance manual requirements; if is greater than the topic similarity threshold tsd, then r j Maybe r i Similar maintenance topics, r j All the maintenance topics that have been prepared are sent to experts for review. If the experts pass the review, i You can directly reuse the maintenance theme j All the contents in;

[0022] If not present satisfy This means that there is no fully reusable maintenance topic, but there may be a type of maintenance information unit in the maintenance topic that can be reused, satisfying:

[0023]

[0024] in, Indicates the contribution parameter related to the security information unit, tsd Js is the security information unit similarity threshold; r j The specific content of the information unit in the information unit is passed to the expert for review. If the expert passes the review, r i Reusable j Maintenance information unit content;

[0025] Repeat the above method to calculate R n Are there reusable maintenance preparation, basic inspection, and maintenance operation information units in the system? If there are similar information units, they will be passed to experts for review. After the experts pass the review, they will be reused through multiple information units of different maintenance topics to complete the r i All the contents in;

[0026] If there is no maintenance information unit that has been prepared for reuse, you can compare it with the unprepared information element library and reuse the maintenance resource information, maintenance object, maintenance plan and maintenance safety information elements; Calculate r i Information element set IF i and r j Information element set IF j The reusability of Represents r j Information element set IF j Reusable, pass it to experts for review, and reorganize it according to the maintenance manual production process after patent review. i basic information content; if there is no reusable situation, the experience of collecting information elements in other maintenance manuals can only be passed on as a reference for information preparation.

[0027] Furthermore, in step S4, the manual production step includes information element processing, maintenance information unit production, maintenance theme production and information release;

[0028] Manual production relies on information model editing, which includes information elements, maintenance information units and maintenance topics. Information elements, maintenance information units and maintenance topics are coded and managed according to single source information.

[0029] Information elements are derived from the basic information collected during the information preparation phase and are standardized according to unified rules for content and format;

[0030] A plurality of various information elements are combined and processed to form a maintenance information unit, a plurality of maintenance information units are combined to form a maintenance theme, and one or more maintenance themes are published to form a maintenance manual.

[0031] Furthermore, the maintenance theme preparation includes:

[0032] Based on the information elements of maintenance object library, maintenance plan library, maintenance resource library, maintenance operation library, and operation safety library, information combination and standardized compilation are carried out according to the characteristics and content of the maintenance work to form maintenance information units; maintenance is classified into multiple levels based on maintenance products, the maintenance theme name is confirmed, and the maintenance theme is itemized and coded layer by layer according to the set rules, and stored in the library for management. Each maintenance code calls a different maintenance information unit according to the set organizational order, which constitutes a complete maintenance theme.

[0033] Furthermore, the digital expression of the maintenance theme is as follows:

[0034] Create maintenance topics based on maintenance codes, and let the maintenance code library be R = {r1, r2, r3, ..., r n}, where r i Represents a maintenance code in the maintenance code library, which is related to the maintenance object. j , maintenance resources Rs i , Maintenance and Inspection Rt i , Maintenance Operation Rd i and Job Safety Js i Together they form the maintenance theme; among them, the maintenance object ro j ∈RO, RO is the maintenance object library, which contains multiple structure tree nodes of products from system to parts to components to components. A single maintenance object corresponds to one or more maintenance topics; maintenance resources Rs i ={rs1,rs2,...,rs m}, Rs i ∈RS, RS is the maintenance resource pool;

[0035] Maintenance topics are modularized in the order of maintenance preparation, basic inspection, maintenance operation, and post-maintenance inspection;

[0036] Maintenance preparation: Select maintenance code i Required maintenance resource setrs i ={rs1,rs2,...,rs m},ro j ∈RO, and call the information unit Js i , link relevant operating manuals or usage conditions, combine and compile maintenance preparation precautions and safe working conditions, and publicize the safe working conditions throughout the maintenance process;

[0037] Basic inspection: Select the maintenance code i Related maintenance inspection steps Rt i ={rt1,rt2,...rt q}, Rt i ∈RT, RT is the maintenance inspection library, maintenance inspection Rt i Organize by inspection steps;

[0038] Maintenance operation: Order maintenance code r i The maintenance operation is Rd i ={rd1,rd2,...rd p}, Rd i ∈RD, RD is the maintenance operation library, maintenance operation Rd i Organize by operation steps, operation steps θ Before execution (θ≤q), the role and expected results of the operation should be explained, and the safety information of the current step should be prompted as needed. θ and required maintenance resources Rt θ , rd θ After execution, for steps where error messages may occur, a recovery procedure should be provided, linking the recovery procedure to a maintenance step and providing a jump;

[0039] Post-repair inspection: Select the repair code i Related Post-Maintenance Inspection Rat i ={rt1,rt2,...rt s}, Rat i ∈RT, RT is the maintenance inspection library, similar to the basic inspection before maintenance, and the post-maintenance inspection Rat i Also organized by inspection steps.

[0040] Further, the maintenance topics are divided into breakdown maintenance, preventive maintenance and maintenance by item type.

[0041] Further, step S5 includes:

[0042] Update the information elements, maintenance information units and maintenance information topics of the maintenance manual according to changes in the product's technical status and user feedback on the use of the maintenance manual. At the same time, based on the association of the single source information established during reuse, when the information source manual is updated, the corresponding content of the maintenance manual of the reused information source is synchronously updated. When the content changes but does not affect user use, internal version control is performed, otherwise the version should be changed, and the corresponding users are prompted to update the manual version according to the actual technical status of the product.

[0043] In summary, due to the adoption of the above technical solution, the beneficial effects of the present invention are:

[0044] The present invention reduces the inconsistency and non-standardization of information structure and content architecture in the process of compiling a maintenance manual by planning a standardized maintenance information model; at the same time, through a multi-level maintenance information model reuse method, it solves the problems of incomplete demand analysis and insufficient technical content verification when compiling a maintenance manual, reduces manual analysis and cleanup work, and improves the usability of the maintenance manual. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention 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 creative work.

[0046] Figure 1 It is a basic flow chart of the method for constructing a digital maintenance manual information model for multi-level agile reuse in an embodiment of the present invention.

[0047] Figure 2 A schematic diagram of an information model for making a maintenance manual according to an embodiment of the present invention. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0049] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0050] Example

[0051] like Figure 1 As shown, this embodiment proposes a method for constructing a digital maintenance manual information model for multi-level agile reuse, including the following steps:

[0052] S1, Manual planning: Determine the planning content of the maintenance manual; specifically:

[0053] Determine the intended use locations and scenarios of the maintenance manual, and classify the target users of the maintenance manual according to their profession, skills, experience, etc.;

[0054] The content of the maintenance manual is confirmed according to the target users and usage scenarios of the maintenance manual, and the display format and interactive functions of the maintenance manual are determined according to the content of the maintenance manual and the display device of the maintenance manual.

[0055] On the basis of ensuring maximum information reuse, estimate the cost and cycle of maintenance manual production.

[0056] S2, information preparation: collecting basic information related to maintenance; in this embodiment, the basic information of the maintenance manual includes:

[0057] Maintenance object information, including component structure, drawings, prototypes, etc.;

[0058] Maintenance plan, including maintenance level, maintenance activities and estimated maintenance hours involved;

[0059] Maintenance resource information, including personnel, tools, materials, etc. involved in maintenance activities;

[0060] Maintenance safety information, including general safety information and information on personnel safety, equipment safety, and environmental safety during maintenance operations;

[0061] Other information, such as maintenance solutions and maintenance cases for similar products.

[0062] S3, manual reuse: multi-level reuse of maintenance topics, maintenance information units and information elements, and transfer of reusable maintenance topics, maintenance information units and information elements to the manual production step, including:

[0063] Based on the content planned in the maintenance manual, multi-level reuse of maintenance topics, maintenance information units, and information elements is carried out. Priority is given to directly reusing similar maintenance topics; when no completely reusable maintenance topic can be found, partial reuse is considered, that is, reuse at the maintenance information unit level; when there is no reusable maintenance information unit, some information elements are reused; among them, an association with a single source of information should be established during reuse to facilitate synchronous update of the information source. The specific reuse method is as follows:

[0064] Let the set of maintenance topics included in the current maintenance manual be R, and select the set of maintenance manuals {R1, R2,.., R n} of similar products in similar fields, then the reusable maintenance manual domain is R n = R1 UR2,..., UR n .

[0065] For the maintenance topic r i in the maintenance manual requirements planned in the manual is For its maintenance manual requirement is m < n, there exists

[0066]

[0067] Among them, is the similarity calculation method, generally, methods such as edit distance, vector cosine, and Jaccard coefficient can be used, and η t is the contribution rate parameter, which is related to the classification of maintenance manual requirements. Generally speaking, in the order of maintenance manual requirement category from maintenance topic name -> maintenance object name -> maintenance environment -> maintenance information unit name -> maintenance safety requirements, η t decreases.

[0068] If is greater than the topic similarity threshold tsd, then r j may be a similar maintenance topic to r i . Transfer all the already made maintenance topics of r j to the expert for review. If the expert review passes, r i can directly reuse all the content in the maintenance topic r j .

[0069] If there is no satisfying then it means that there is no completely reusable maintenance topic. But there may be a reusable situation for a certain type of maintenance information unit in the maintenance topic. For example: for its maintenance information unit name is Js i, it is calculated that there is no maintenance topic that can be fully reused, but there is satisfy:

[0070]

[0071] in, Indicates the contribution parameters related to the safety information unit. Generally speaking, the contribution parameter of the name of the information unit itself is the highest, followed by the name of the maintenance object and the name of the maintenance object. Js is the security information unit similarity threshold.

[0072] Therefore, r j The specific content of the maintenance information unit in the maintenance information unit is passed to the expert for review. If the expert passes the review, r i Reusable j Maintenance information unit content.

[0073] Repeat the above method to calculate R n Are there reusable maintenance information units such as maintenance preparation, basic inspection, and maintenance operation in the system? If there are similar maintenance information units, they will be sent to experts for review. After the experts pass the review, the maintenance information units of multiple different maintenance topics will be reused to complete the r i All the contents in.

[0074] If there is no maintenance information unit that has been prepared and can be reused, you can compare it with the unprepared information element library and reuse the maintenance resource information, maintenance object, maintenance plan and maintenance safety information elements. Calculate r i Information element set IF i and r j Information element set IF j The reusability of Represents r j Information element set IF j Reusable, pass it to experts for review, and reorganize it according to the maintenance manual production process after patent review. i basic information content; if there is no reusable situation, the experience of collecting information elements in other maintenance manuals can only be passed on as a reference for information preparation.

[0075] S4, manual production: Produce a maintenance manual based on the collection of basic maintenance-related information and reusable maintenance topics, maintenance information units and information elements.

[0076] like Figure 2As shown in the figure, manual production mainly includes several steps, including information element processing, maintenance information unit production, maintenance theme production and information release. Manual production relies on information model editing. The information model includes information elements, maintenance information units and maintenance themes. Information elements, maintenance information units and maintenance themes are coded and managed according to single source information to ensure data uniqueness, consistency, compliance and integrity.

[0077] Information elements are derived from the basic information collected during the information preparation phase, including maintenance object information, maintenance plan information, maintenance resource information, maintenance safety information and other maintenance information, and are standardized according to unified rules for content and format, and stored in media such as pictures, 3D models and rich media;

[0078] A plurality of various information elements are combined and processed to form a maintenance information unit, a plurality of maintenance information units are combined to form a maintenance theme, and one or more maintenance themes are published to form a maintenance manual.

[0079] Specifically, the maintenance theme preparation described in S4 includes:

[0080] Based on the information elements such as the maintenance object library, maintenance plan library, maintenance resource library, maintenance operation library, and operation safety library, information is combined and standardized according to the characteristics and content of the maintenance work to form maintenance information units. Generally speaking, maintenance information units include maintenance preparation, basic inspection, maintenance operation, post-maintenance inspection, and operation safety. Based on the maintenance product, maintenance is classified into multiple levels, the maintenance theme name is confirmed, and the maintenance theme is coded level by level according to the set rules and stored in the library. Each maintenance code calls different maintenance information units according to the set organizational order, which can constitute a complete maintenance theme. Maintenance themes can be divided into fault repair, preventive maintenance, and maintenance according to project type. The digital expression of the production method of maintenance themes is as follows:

[0081] Create maintenance topics based on maintenance codes, and let the maintenance code library be R = {r1, r2, r3, ..., r n}, where r i Represents a maintenance code in the maintenance code library, which is related to the maintenance object. j , maintenance resources Rs i , Maintenance and Inspection Rt i , Maintenance Operation Rd i and Job Safety Js i Multiple maintenance information units together constitute the maintenance subject. j ∈RO, RO is the maintenance object library, which contains multiple structure tree nodes of products from system to parts to components to components. A single maintenance object may correspond to multiple maintenance topics; maintenance resources Rs i={rs1,rs2,...,rs m}, Rs i ∈RS, RS is the maintenance resource library, including tools and spare parts required for maintenance;

[0082] Maintenance topics should be modularized in the order of maintenance preparation, basic inspection, maintenance operation, and post-maintenance inspection;

[0083] Maintenance preparation: Select maintenance code i Required maintenance resource setrs i ={rs1,rs2,...,rs m},ro j ∈RO, and call job security Js i , link relevant operating manuals or usage conditions, combine and compile maintenance preparation precautions and safe working conditions, and publicize the safe working conditions throughout the maintenance process;

[0084] Basic inspection: Select the maintenance code i Related maintenance inspection Rt i ={rt1,rt2,...rt q}, Rt i ∈RT, RT is the maintenance inspection library, maintenance inspection Rt i Organize according to the inspection steps, generally follow the inspection order of easy first then difficult, outside first then inside.

[0085] Maintenance operation: Order maintenance code r i The maintenance operation is Rd i ={rd1,rd2,...rd p}, Rd i ∈RD, RD is the maintenance operation library, maintenance operation Rd i Organize by operation steps, operation steps θ Before execution (θ≤q), the role and expected results of the operation should be explained, and the safety information of the current step should be prompted as needed. θ and required maintenance resources Rt θ , rd θ After execution, for steps that may cause error messages, a recovery procedure should be provided, linking the recovery procedure to a maintenance step and providing a jump. θ After execution, if there is no exception, jump to r θ+1 Or end the maintenance operation (θ = q, i.e. the object returns to normal after the maintenance operation is completed), if there is an error message er1, execute the recovery procedure rp1, and re-execute the maintenance step rt after execution λ (λ<θ).

[0086] Post-repair inspection: Select the repair code i Related Post-Maintenance Inspection Rat i ={rt1,rt2,...rt s}, Rat i ∈RT, RT is the maintenance inspection library, similar to the basic inspection before maintenance, and the post-maintenance inspection Rat i It is also organized according to the inspection steps, following the inspection order of easy first then difficult, outside first then inside. The basic inspection before maintenance and the inspection after maintenance have different purposes and requirements, so there are overlaps but they are not completely equivalent.

[0087] S5, Manual Update: Maintain and update the maintenance manual according to changes in technical status and user feedback.

[0088] Establish a maintenance manual version control mechanism: Update the maintenance manual's information elements, maintenance information units, maintenance topics, and other contents based on changes in product technical status, user feedback on maintenance manuals, etc.; at the same time, based on the association of single-source information established during reuse, when the information source manual is updated, the corresponding contents of the maintenance manual of the reused information source are updated synchronously. When the content changes but does not affect user use, internal version control is performed, otherwise a version change should be performed; ensure that the scope of the impact of the manual version change is controllable, and provide manual version update prompts to the corresponding users based on the actual technical status of the product.

[0089] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for constructing a digital maintenance manual information model for multi-level agile reuse, characterized in that: The following steps are involved: S1, Manual planning: determine the planning content of the maintenance manual; S2, information preparation: collect basic information related to maintenance; S3, manual reuse: perform multi-level reuse of maintenance topics, maintenance information units and information elements, and pass the reusable maintenance topics, maintenance information units and information elements to the manual production step; S4, manual production: based on the collection of basic information related to maintenance and reusable maintenance topics, maintenance information units and information elements, the maintenance manual is produced; S5, Manual Update: Maintain and update the maintenance manual according to changes in technical status and user feedback.

2. The method for constructing a digital maintenance manual information model for multi-level agile reuse according to claim 1 is characterized in that: Step S1 includes: Determine the intended use locations and scenarios of the maintenance manual, and classify the target users of the maintenance manual according to their profession, skills, experience, etc.; Confirm the content of the maintenance manual according to the target users and usage scenarios of the maintenance manual, and determine the display format and interactive functions of the maintenance manual according to the content of the maintenance manual and the display device of the maintenance manual; On the basis of ensuring maximum information reuse, estimate the cost and cycle of maintenance manual production.

3. The method for constructing a digital maintenance manual information model for multi-level agile reuse according to claim 1 is characterized in that: In step S2, the basic information of the maintenance manual includes maintenance object information, maintenance plan, maintenance resource information, maintenance safety information and other information.

4. The method for constructing a digital maintenance manual information model for multi-level agile reuse according to claim 1, characterized in that: Step S3 includes: Based on the maintenance manual planning content, maintenance topics, maintenance information units and information elements are reused at multiple levels, with priority given to direct reuse of similar maintenance topics. When no fully reusable maintenance topics can be found, partial reuse is considered, that is, reuse from the maintenance information unit level. When there are no reusable maintenance information units, some information elements are reused. Among them, an association with a single source information should be established during reuse.

5. The method for constructing a digital maintenance manual information model for multi-level agile reuse according to claim 4 is characterized in that: Let the maintenance topic set contained in the current maintenance manual be R, and select the maintenance manual set of similar products in similar fields {R1, R2, .., R n }, the maintenance manual domain can be reused as R n =R1 UR2,...,UR n ; For the maintenance topic r i The maintenance manual requirements planned in the manual are For Its maintenance manual requirements are m < n, there exists Calculate r i And r j The similarity of. If the calculated similarity is greater than the maintenance topic similarity threshold tsd, then r j May be a similar maintenance topic of r i Transfer all the made maintenance topics to the expert for review. If the expert review is passed, r j Can directly reuse all the content in the maintenance topic r i ; j ; If not present If the similarity is greater than the maintenance topic similarity threshold, it means that there is no fully reusable maintenance topic, but there may be a type of maintenance information unit in the maintenance topic that can be reused. If the security information unit similarity is greater than or equal to the security information unit similarity threshold, then r j The specific content of the information unit in the information unit is passed to the expert for review. If the expert passes the review, r i Reusable j Maintenance information unit content; Repeat the above method to calculate R n Are there reusable maintenance preparation, basic inspection, and maintenance operation information units in the system? If there are similar information units, they will be passed to experts for review. After the experts pass the review, they will be reused through multiple information units of different maintenance topics to complete the r i All the contents in; If there is no maintenance information unit that has been prepared and can be reused, compare the unprepared information element library and reuse the maintenance resource information, maintenance object, maintenance plan and maintenance safety information elements; Calculate r i Information element set IF i and r j Information element set IF j Reusability, if the information element set IF i and information element set IF j The similarity of is greater than or equal to the information element similarity threshold, indicating that r j Information element set IF j Reusable, pass it to experts for review, and reorganize it according to the maintenance manual production process after patent review. i basic information content; if there is no reusable situation, the experience of collecting information elements in other maintenance manuals can only be passed on as a reference for information preparation.

6. The method for constructing a digital maintenance manual information model for multi-level agile reuse according to claim 1, characterized in that: In step S4, the manual production steps include information element processing, maintenance information unit production, maintenance theme production and information release; Manual production relies on information model editing, which includes information elements, maintenance information units and maintenance topics. Information elements, maintenance information units and maintenance topics are coded and managed according to single source information. Information elements are derived from the basic information collected during the information preparation phase and are standardized according to unified rules for content and format; A plurality of various information elements are combined and processed to form a maintenance information unit, a plurality of maintenance information units are combined to form a maintenance theme, and one or more maintenance themes are published to form a maintenance manual.

7. The method for constructing a digital maintenance manual information model for multi-level agile reuse according to claim 6, characterized in that: The maintenance theme production includes: Based on the information elements of maintenance object library, maintenance plan library, maintenance resource library, maintenance operation library, and operation safety library, information combination and standardized compilation are carried out according to the characteristics and content of the maintenance work to form maintenance information units; maintenance is classified into multiple levels based on maintenance products, the maintenance theme name is confirmed, and the maintenance theme is itemized and coded layer by layer according to the set rules, and stored in the library for management. Each maintenance code calls a different maintenance information unit according to the set organizational order, which constitutes a complete maintenance theme.

8. The method for constructing a digital maintenance manual information model for multi-level agile reuse according to claim 7, characterized in that: The digital representation of the maintenance theme is as follows: Create maintenance topics based on maintenance codes, and let the maintenance code library be R = {r1, r2, r3, ..., r n }, where r i Represents a maintenance code in the maintenance code library, which is related to the maintenance object. j , maintenance resources Rs i , Maintenance and Inspection Rt i , Maintenance Operation Rd i and Job Safety Js i Together they form the maintenance theme; among them, the maintenance object ro j ∈RO, RO is the maintenance object library, which contains multiple structure tree nodes of products from system to parts to components to components. A single maintenance object corresponds to one or more maintenance topics; maintenance resources Rs i ={rs1,rs2,...,rs m }, Rs i ∈RS, RS is the maintenance resource pool; Maintenance topics are modularized in the order of maintenance preparation, basic inspection, maintenance operation, and post-maintenance inspection; Maintenance preparation: Select maintenance code i Required maintenance resource setrs i ={rs1,rs2,...,rs m },ro j ∈RO, and call the information unit Js i , link relevant operating manuals or usage conditions, combine and compile maintenance preparation precautions and safe working conditions, and publicize the safe working conditions throughout the maintenance process; Basic inspection: Select the maintenance code i Related maintenance inspection steps Rt i ={rt1,rt2,...rt q }, Rt i ∈RT, RT is the maintenance inspection library, maintenance inspection Rt i Organize by inspection steps; Maintenance operation: Order maintenance code r i The maintenance operation is Rd i ={rd1,rd2,...rd p }, Rd i ∈RD, RD is the maintenance operation library, maintenance operation Rd i Organize by operation steps, operation steps θ Before execution (θ≤q), the role and expected results of the operation should be explained, and the safety information of the current step should be prompted as needed. θ and required maintenance resources Rt θ , rd θ After execution, for steps where error messages may occur, a recovery procedure should be provided, linking the recovery procedure to a maintenance step and providing a jump; Post-repair inspection: Select the repair code i Related Post-Maintenance Inspection Rat i ={rt1,rt2,...rt s }, Rat i ∈RT, RT is the maintenance inspection library, similar to the basic inspection before maintenance, and the post-maintenance inspection Rat i Also organized by inspection steps.

9. The method for constructing a digital maintenance manual information model for multi-level agile reuse according to claim 8, characterized in that: Maintenance topics are divided into breakdown maintenance, preventive maintenance and maintenance by project type.

10. The method for constructing a digital maintenance manual information model for multi-level agile reuse according to claim 1, characterized in that: Step S5 includes: Update the information elements, maintenance information units and maintenance information topics of the maintenance manual according to changes in the product's technical status and user feedback on the use of the maintenance manual. At the same time, based on the association of the single source information established during reuse, when the information source manual is updated, the corresponding content of the maintenance manual of the reused information source is synchronously updated. When the content changes but does not affect user use, internal version control is performed, otherwise the version should be changed, and the corresponding users are prompted to update the manual version according to the actual technical status of the product.

Images