Deliverables and tasks

The purpose of this ASD-STAN Technical Report is to define generic requirements and methods for the acceptance of supplier’s design capabilities and management of Design Organization authorizations to suppliers performing design activities and/or tasks on behalf of DOAH.

This document covers all suppliers as soon as they produce deliverables related to the design of parts or appliances (e.g. design data, compliance documents for certification activities, etc.) and/or perform the associated tasks (e.g. classification of changes to TC, execution of laboratory tests for development or compliance demonstration and associated test data results collection and documentation).

Any designing of parts or appliances or any execution of associated tasks performed by persons not directly employed by the DOAH should be considered as work being subcontracted, and therefore could be eligible to the cascade of authorization as defined in this document (refer to Table 1 in 1.2).

Examples of tasks which can be subcontracted are:

— laboratory testing, test set-up and/or inspection;

— design data and drawings;

— stress analysis;

— qualification of software/equipment;

— Instructions for Continued Airworthiness (ICA).

Examples of tasks which can be delegated are:

— technical endorsement of laboratory testing, test set-up and/or inspection;

— technical endorsement of design data and drawings;

— technical endorsement of stress analysis;

— technical endorsement of qualification of software/equipment;

— classification of changes and approval of minor changes at product level;

— classification of repairs and approval of minor repairs at product level;

— technical endorsement of Instructions for Continued Airworthiness (ICA).

This ASD-STAN Technical Report is applicable for:

— initial design during product development (type certificate/STC/RTC process): subcontractor’s contribution to the preparation of compliance documents to be used by TC/STC applicant in the frame of the certification activities;

— changes to the type certificate/STC/RTC;

— repairs;

— engineering decision over unintentional manufacturing deviations.

Signature rules

General

Deliverables to be produced by a supplier might require up to three levels of signatures.

Level 1 signature

This is a signature for technical endorsement of the deliverable (e.g. design data might require only a Level 1 signature, when not used as compliance documents as intended in Part 21), see subclause 4.1 for more details.

Level 2 signature

This is the signature by a compliance verification engineer, as defined in Part 21.A.239(d)2 (e.g. a compliance document requires at least a Level 1 and a Level 2 signatures), see subclause 4.2 for more details.

NOTE Per AMC 21.A.239(d)(2) The independent verification function of the demonstration of compliance should consist of the verification by a person that did not create the compliance data. Such a person may work in conjunction with the individuals that prepare compliance data.

Level 3 signature

This is a signature by an authorized signatory of a DOAH for the exercise of its Part 21.A.263 privileges (e.g. classification of changes to TC, approval of minor changes to TC), see subclause 4.3 for more details.

Three levels of signature authorizations can be granted by the DOA holder to its suppliers. The granting of signatory authorizations to suppliers does not relieve the DOAH of its DOA obligations as per Part 21 requirements.

The Table 1 below provides a synthesis of the scope covered by this document with the associated deliverable/signatory level.

A Level 1 signature authorization is an authorization to a supplier to sign a deliverable requiring at least a Level 1 signature, Level 2 and Level 3 signature authorizations are for the signature of a deliverable requiring Level 2 and/or Level 3 signatures.

Level 2 authorization implies a Level 1 authorization has been already granted.

NOTE External CVE acting on behalf of the DOAH and not pertaining to DOAH or suppliers organization is allowed but not covered by the general rules of the current version of the standard.

A Level 3 authorization implies that:

— a Level 2 authorization has been already granted, except when authorized scope covers only deliverables without additional work to demonstrate compliance;

— a Level 1 authorization has been already granted.

The minimum requirements being:

— one signature for each applicable level;

— independence is needed between the individual holding a Level 1 signature used to demonstrate the compliance and the individual holding the Level 2 signature performing the verification of the demonstration of compliance.