Chapter 3.2 - Information generation - Data modules
Aerospace and Defence Industries Association of Europe
2016-12-31



GENERAL


This chapter explains the general structure of a data module. There are
a number of data module types, which are appropriate for use in the
production of all technical information required in operation and
maintenance of the Product.



BASIC STRUCTURE


All data modules have a basic structure, which is comprised of two
sections:

-   identification and status section, which is defined in Chapter
    3.9.5.1 - Data modules - Identification and status section.

-   content section, which is defined in Chapter 3.9.5.2 - Data
    modules - Content section.


Identification and status section

The identification and status section is the first part of a data
module.

It contains identification data (eg, data module code, title, issue
number, issue date, language) and status data (eg, security
classification, responsible partner company and originator,
applicability, technical standard, QA status, skill, reason for update).
Specific details are given in Chapter 3.9.5.1 - Data modules -
Identification and status section.

The identification and status section provides data that can be used
for:

-   management of the data module within the CSDB

-   management of the use of applicability

-   management of the quality control process

-   management and control of retrieval functions

-   automatic compilation of sets or subsets of information

-   general information for users accessing the CSDB

Applicability

The overall applicability for an entire data module is captured in the
identification and status section and is explained in Chapter 3.9.5.3 -
Data modules - Applicability.

Security classification

The general rules for security classifications are explained in Chapter
3.6 - Information generation - Security and data restrictions. The
detailed application of security classifications for an entire data
module is captured in the identification and status section and is
explained in Chapter 3.9.5.1 - Data modules - Identification and status
section.

Quality assurance

The process for QA is explained in Chapter 3.7 - Information generation
- Quality assurance.

Reason for upde

The reason for update can be used to record the reason for developing
the initial issue of a data module or the reason for any changes made to
the data module. Refer to Chapter 3.9.5.2.1.1 - Common constructs -
Change marking.


Content section

The content section is the second part of a data module. It contains the
text and illustrations that is presented to the user. The different
types of the content section and their use are described in Chapter
3.9.5.2 - Data modules - Content section.

Applicability

Content applicability can be allocated to elements within the content
section. Refer to Chapter 3.9.5.3 - Data modules - Applicability.

Security classification

A security classification can be allocated to elements within the
content section. Refer to Chapter 3.9.5.2.1 - Content section - Common
constructs.

Reason for change

Within the content section, changes can be identified and this can
include the reason for change. Details of how to apply change is
explained in Chapter 3.9.5.2.1.1 - Common constructs - Change marking.