<< Click to Display Table of Contents >> Navigation:  Functions by Department > Maintenance Control & Continuing Airworthiness > Technical Documentation

Note: For managing receipt, dispatch and revision control of your internal and external publications on all your sites, refer to Documents & Manuals

 

Each time a MR (M.Requirements) is printed or exported as a pdf file, the publications associated with this MR (Document Manager) are printed as well so that all information and procedures relevant to the MR embodiment are provided to the engineer.

 

When the associated publications and forms are produced internally or when a procedure is implemented to update the MR whenever the associated publications are updated, the pdf file of the associated publication is recorded as an attachment of the MR (using the Document Manager).

 

When the associated publication is an external document which is subject to revision (AMM / IPC / WDM for example), a link to the current version of this document is recorded in AMS. This ensures that whenever the MR is printed, the publications associated with it are current.

 

There are 3 methods to link the OEM manuals with the Maintenance Requirements (MR) in AMS:

 

Method 1:

 

Each task from the AMM is in the form of an individual pdf file (for example, the AMM task 21-31-00-710-802 is stored in a pdf file named AMM21-31-00-710-802.pdf)

 

Note: if the AMM is provided as a single pdf file, or one pdf file per ATA chapter, this file can easily be split by bookmark using Acrobat X or higher (Choose View > Tools > Pages; then select "Split Document" and "Split document by top-level bookmark and click on OK)

 

In AMS, record the file link (a link to your local network where the pdf files have been copied to) every time the AMM procedure is called out (MR > Document Manager with autoprint activated). Using a file link instead of recording the actual file ensures that the latest version of the file is used every time the MR is called out. This link is recorded one time only (the link does not need to be updated when a new revision of the AMM is received) unless the MR itself and the procedure need to be changed.

 

When a new revision of the manual is received, the new pdf files are copied to the network location. All task cards will reflect the latest revision.

 

Method 2:

 

The OEM of the manual is providing a function / procedure / interface to be called by an external software to obtain the pdf file of the desired task. The task reference is is provided as a parameter and the pdf file is returned as result. This method is tailored to each OEM as the function / procedure / interface is specific to the OEM and to the concerned manual.  Specific development is required to activate this method.

 

When a new revision of the manual is received, the new manuals are automatically available without further action, provided the path to the external function / procedure / interface remains unchanged.

 

Method 3:

 

The OEM provides the documentation in SGML format (usually called XML documentation). This form of documentation is proprietary as it uses customized SGML tag definition (DTD file - Document Type Definition). Integration  of SGML documentation into AMS is specific to each OEM and Customer. This method is similar to method n°2 to the exception that AMS needs to build the pdf document based on the data sources provided by the OEM (SGML files). A modification of the file definition by the OEM will require a modification of the file reading procedures in AMS.