AMC 21.A.15(b)(5) Breakdown of the certification programme into compliance demonstration items (CDIs)

• ED Decision 2019/018/R found in: Initial Airworthiness and Environmental Protection (No 748/2012) Part-21 Part-21L (Jul 2024)

AMC 21.A.15(b)(5) Breakdown of the certification programme into compliance demonstration items (CDIs) ED Decision 2019/018/R 1.       What is a CDI? A CDI is a meaningful group of compliance demonstration activities and data identified in the certification programme which can be considered in isolation for the purpose of performing the risk assessment that allows EASA to determine its level of involvement (LoI) using a risk-based approach. The possibility to create this grouping of compliance demonstration activities and data is intended to facilitate the risk assessment. However, there may be cases in which the risk assessment may also be performed at the level of the compliance demonstration activity or data, or at the level of the whole certification project. The chosen breakdown into CDIs may affect the resulting risk classes (please refer to [AMC 21.B.100(a) and 21.A.15(b)(6)](#_DxCrossRefBm1649096977)), but should not have any effect on the compliance demonstration itself or on EASA’s LoI. 2.       The grouping of compliance demonstration activities and data The compliance demonstration activities and data grouped in a CDI may demonstrate compliance with a requirement, a group of requirements, or even a part of a requirement. In this context, ‘requirement’ means any element of the type-certification basis or operational suitability data (OSD) certification basis as specified in [21.B.80](#_DxCrossRefBm1649096853) and [21.B.82](#_DxCrossRefBm1649096972), or the environmental protection requirements as specified in [21.B.85](#_DxCrossRefBm1649096971). A CDI may comprise any of the means of compliance listed in [Appendix A to AMC 21.A.15(b)](#_DxCrossRefBm1649096976). CDIs may be tailored to the scope and size of the project. On simple projects, a CDI may address all the compliance demonstration activities within a given technical area (e.g. avionics, flight, structures, hydromechanical systems, OSD-cabin crew data (CCD), etc.) or of the whole project. A CDI should not be too large, by combining completely unrelated compliance demonstration activities or data, so that it becomes meaningless, but neither should it be so small that it might not be considered in isolation from some other related compliance demonstration activities or data. A way of meaningfully grouping compliance demonstration activities and data, for example, is to select some activities and data and group them into a single CDI, as the certification programme must already contain the applicable requirements, the proposed means of compliance for each requirement, as well as the associated compliance documents for each means of compliance. Another way to meaningfully group the data is to do it at the level of the technically related compliance demonstration activities and data. This may facilitate the assessment of those activities and data against the novelty, complexity, and criticality criteria (see [AMC 21.B.100(a) and 21.A.15(b)(6)](#_DxCrossRefBm1649096977)). The resultant CDI may encompass various means of compliance. 3.       Description of CDIs Each CDI should be sufficiently described in the certification programme, and should detail the following: — the scope of the CDI; and — the information on the novelty, complexity, and criticality of the item being certified. However, in cases where the rationale of the assessment is obvious, it is considered to be sufficient to indicate whether or not a CDI is novel or complex, and whether or not the impact is critical. Note: Obvious cases are cases for which the classification is straightforward and does not require additional clarifications. In general, applicant explanations/notes regarding the proposed classification should be provided, since this will also facilitate the acceptance of the LOI proposal. Nevertheless, to avoid unnecessary additional effort, these explanations can be omitted if they are obvious. Additionally, it is recommended to identify the EASA panel(s)/discipline(s) affected by each CDI, as this will support the determination of the novelty, complexity, and criticality, and finally identify the performance of the design organisation approval (DOA) holder.