Common use of Phase II - Technical Familiarization Clause in Contracts

Phase II - Technical Familiarization. 8.3.1 The objective of this phase is technical familiarization with the project by the VA and the establishment of the initial VA Certification Basis and the initial VI. 8.3.2 This phase begins with the scheduling of a familiarization meeting, unless the product is a derivative and the changes from previously validated designs do not warrant the briefing. 8.3.3 The VA should receive a thorough familiarization briefing on a new certification program in order to fully understand the product design and any unique or novel design features. Detailed discussions will also be presented when: • The product has novel design features, or its use is unconventional, • The product contains design features where experience has shown an unsafe condition might occur, • New rule interpretations or MOC for the existing rules are proposed, and • The product design features items identified on the VA’s Potential VI(I) list. This information will be used to establish the VA Certification Basis for the project. It will also serve the purpose of educating the VA so it may appropriately deal with continued operational safety issues within its country. 8.3.4 The briefing should be conducted jointly by the CA and the applicant. 8.3.5 For sequential certification/validation projects, the CA should identify its certification basis and present an overview of any significant compliance findings established during its certification program. For concurrent certification/validation projects, the CA will identify its proposed certification basis. 8.3.6 Of prime importance is the opportunity for the VA to understand the MOC used or to be used. The CA and the Applicant will provide general information on the methods of compliance that have been used (sequential certification/validation) to the VA during the technical familiarization phase. This general information should be sufficiently detailed to allow the VA team to understand the general principle of the MOC used or to be used. In depth discussion of MOC (including those for SRD's as necessary) should be conducted in phase III. Further discussion of MOC that have been used and accepted by both the CA and VA for harmonised rules and for non-SRD should not be required. 8.3.7 The CA and the applicant will present detailed information on the MOC that are used, or are to be used, to establish compliance with regulations related to subjects referred to under 8.3.3, such as basic loads, or fatigue, that are judged to be significant by the CA. 8.3.8 For sequential certification/validation projects, the CA will thoroughly brief the VA on all exemptions and special conditions issued by the CA to ensure they are fully understood by the VA. For concurrent certification/validation projects, the CA will thoroughly brief the VA on all proposed exemptions and special conditions. 8.3.9 The objective of the briefing is to convey information to the VA. In- depth discussion or debate of the material is to be done, if needed, during Phase III of the project. The VA should ask clarifying questions and have dialogue as necessary to properly understand the material presented. 8.3.10 It is expected that all VA functional areas would be represented at the briefing so that the familiarization briefing takes place only once. It is recognized that once information is received, the size of the actual VA team involved in the type validation may be reduced. For instance, if there are no significant systems issues, the VA team may not have a full-time systems member. 8.3.11 This phase includes the familiarization flights by the VA. 8.3.12 This phase ends with the establishment of the initial VA Certification Basis and initial validation items.

Phase II - Technical Familiarization. 8.3.1 The objective of this phase is technical familiarization with the project by the VA and the establishment of the initial VA Certification Basis and the initial VI. 8.3.2 This phase begins with the scheduling of a familiarization meeting, unless the product is a derivative and the changes from previously validated designs do not warrant the briefing. 8.3.3 The VA should receive a thorough familiarization briefing on a new certification program in order to fully understand the product design and any unique or novel design features. Detailed discussions will also be presented when: • The product has novel design features, or its use is unconventional, • The product contains design features where experience has shown an unsafe condition might occur, • New rule interpretations or MOC for the existing rules are proposed, and • The product design features items identified on the VA’s Potential VI(I) list. This information will be used to establish the VA Certification Basis for the project. It will also serve the purpose of educating the VA so it may appropriately deal with continued operational safety issues within its country. 8.3.4 The briefing should be conducted jointly by the CA and the applicant. 8.3.5 For sequential certification/validation projects, the CA should identify its certification basis and present an overview of any significant compliance findings established during its certification program. For concurrent certification/validation projects, the CA will identify its proposed certification basis. 8.3.6 Of prime importance is the opportunity for the VA to understand the MOC used or to be used. The CA and the Applicant will provide general information on the methods of compliance that have been used (sequential certification/validation) to the VA during the technical familiarization phase. This general information should be sufficiently detailed to allow the VA team to understand the general principle of the MOC used or to be used. In depth discussion of MOC (including those for SRD's as necessary) should be conducted in phase III. Further discussion of MOC that have been used and accepted by both the CA and VA for harmonised harmonized rules and for non-SRD should not be required. 8.3.7 The CA and the applicant will present detailed information on the MOC that are used, or are to be used, to establish compliance with regulations related to subjects referred to under 8.3.3, such as basic loads, or fatigue, that are judged to be significant by the CA. 8.3.8 For sequential certification/validation projects, the CA will thoroughly brief the VA on all exemptions and special conditions issued by the CA to ensure they are fully understood by the VA. For concurrent certification/validation projects, the CA will thoroughly brief the VA on all proposed exemptions and special conditions. 8.3.9 The objective of the briefing is to convey information to the VA. In- depth discussion or debate of the material is to be done, if needed, during Phase III of the project. The VA should ask clarifying questions and have dialogue as necessary to properly understand the material presented. 8.3.10 It is expected that all VA functional areas would be represented at the briefing so that the familiarization briefing takes place only once. It is recognized that once information is received, the size of the actual VA team involved in the type validation may be reduced. For instance, if there are no significant systems issues, the VA team may not have a full-time systems member. 8.3.11 This phase includes the familiarization flights by the VA. 8.3.12 This phase ends with the establishment of the initial VA Certification Basis and initial validation items.

Phase II - Technical Familiarization. 8.3.1 The objective of this phase is technical familiarization with the project by the VA and the establishment of the initial VA Certification Basis and the initial VI. 8.3.2 This phase begins with the scheduling of a familiarization meeting, unless the product is a derivative and the changes from previously validated designs do not warrant the briefing. 8.3.3 The VA should receive a thorough familiarization briefing on a new certification program in order to fully understand the product design and any unique or novel design features. Detailed discussions will also be presented when: • The product has novel design features, or its use is unconventional, • The product contains design features where experience has shown an unsafe condition might occur, • New rule interpretations or MOC for the existing rules are proposed, and • The product design features items identified on the VA’s Potential VI(I) list. This information will be used to establish the VA Certification Basis for the project. It will also serve the purpose of educating the VA so it may appropriately deal with continued operational safety issues within its country. 8.3.4 The briefing should be conducted jointly by the CA and the applicant. 8.3.5 For sequential certification/validation projects, the CA should identify its certification basis and present an overview of any significant compliance findings established during its certification program. For concurrent certification/validation projects, the CA will identify its proposed certification basis. 8.3.6 Of prime importance is the opportunity for the VA to understand the MOC used or to be used. The CA and the Applicant will provide general information on the methods of compliance that have been used (sequential certification/validation) to the VA during the technical familiarization phase. This general information should be sufficiently detailed to allow the VA team to understand the general principle of the MOC used or to be used. In depth discussion of MOC (including those for SRD's as necessary) should be conducted in phase III. Further discussion of MOC that have been used and accepted by both the CA and VA for harmonised rules and for non-SRD should not be required. 8.3.7 The CA and the applicant will present detailed information on the MOC that are used, or are to be used, to establish compliance with regulations related to subjects referred to under 8.3.3, such as basic loads, or fatigue, that are judged to be significant by the CA. 8.3.8 For sequential certification/validation projects, the CA will thoroughly brief the VA on all exemptions and special conditions issued by the CA to ensure they are fully understood by the VA. For concurrent certification/validation projects, the CA will thoroughly brief the VA on all proposed exemptions and special conditions. 8.3.9 The objective of the briefing is to convey information to the VA. In- depth discussion or debate of the material is to be done, if needed, during Phase III of the project. The VA should ask clarifying questions and have dialogue as necessary to properly understand the material presented. 8.3.10 It is expected that all VA functional areas would be represented at the briefing so that the familiarization briefing takes place only once. It is recognized that once information is received, the size of the actual VA team involved in the type validation may be reduced. For instance, if there are no significant systems issues, the VA team may not have a full-time systems member. 8.3.11 This phase includes the familiarization flights by the VA. 8.3.12 This phase ends with the establishment of the initial VA Certification Basis and initial validation items.