Technical familiarisation (Phase Sample Clauses

Technical familiarisation (Phase. 2) a) The objective of this phase is to provide detailed technical information about the project to the VA’s team to enable the definition of, and decision on, the VA’s initial type certification basis. The objective can only be fully satisfied when the applicant has provided a sufficiently detailed description of the design to the VA and when the CA certification basis has been sufficiently presented to the VA. This is done, in particular, during one or several technical familiarisation meeting(s). b) The applicant, in coordination with the Project Certification Manager (PCM) of the VA and in consultation with the CA, will draw up an agenda for this/ these meeting(s), and coordinate the necessary arrangements, including the details related to the preparation of suitable descriptive material and other documentation necessary for the good conduct of the meeting(s). c) The technical familiarisation meeting(s) may be organised using modern communication means (e.g. teleconference, videoconference), especially in a case where the resources to assemble a technical audience could be economically disproportionate to the scale and complexity of the design being validated. d) The PCMs of the CA and VA will ensure that the technical familiarisation meeting is scheduled at a date suitable to all parties involved and that sufficiently knowledgeable representatives from all parties are participating. The CA is expected to attend the familiarisation meeting, given that it has a thorough knowledge of the certification of the design. e) The applicant, with support from the CA as applicable, will present to the VA: (1) An overview of the proposed design, intended operational use and, if applicable, relation to previously approved products, (2) The CA certification basis and proposed VA certification basis, including analysis of their differences. (3) Any novel design features, novel applications of existing technology, or unconventional uses of the product, (4) Any design features where experience has shown that an unsafe condition might occur, (5) All exemptions/ deviations, special conditions, and equivalent level of safety findings/ equivalent safety findings issued by the CA, and (6) Any newly proposed interpretations or MoCs for existing standards. f) For concurrent validation projects, in addition to the above elements, the CA may identify the domains, if any, where delegation may be given to the VA for the findings of compliance to both CA and VA requirements. For e...