In order to get a Type ID in ERATV you need to:
1. Submit to the authorising entity (NSA or Agency) a request for the creation of a draft type in ERATV before applying for the authorisation. When the Agency is the authorising entity, please use this template (TEM_VEA_092).
2. When granted access to the draft type provide the technical details directly in ERATV. The draft type contains the TYPE ID to use in the authorisation application. More information about ERATV can be found here.
3. When your draft type is ready in ERATV print it into a PDF file (or export it to Excel), fill-in this template (TEM_VEA_060) and upload both files into the documentation of your application in the OSS.
When submitting an application through the OSS, the applicant must provide the concerned EC certificates and EC declarations through the OSS, taking into account the scope of the application (e.g. in case of new authorisation, only the EC certificates and EC declarations of Interoperability Constituents impacted by the change need to be submitted). Before submitting the application, the applicant must ensure that all the EC certificates and EC declarations are uploaded in ERADIS.
During the assessment of an application for authorisation, the authorising entity shall perform several checks on the EC certificates and EC declarations, such as consistency between the application and ERADIS/ERATV, consistency between the EC certificates mentioned in the EC declarations and the actual EC certificates submitted in the application etc.
In order to reduce streamline the assessment process, applicants are kindly requested to fill-in this template (TEM_VEA_061) and include it in the application for authorisation before submitting it.
Templates and checklists can be used to support the work of the actors during the assessment. These templates and checklists are documents to fill in with usual office suite tools and to upload in the OSS as attachments to the various reports (mainly completeness check, detailed assessment, conclusion, decision and authorisation). The templates and checklists are made available to the users through the templates folder in the library.
Applicant are free to organize their documentation according to their needs. The folder structure proposed for the documentation is a guidance. However respecting it renders the elaboration of the mapping tables easier and it is therefore encouraged. If the structure is not followed it is highly probable that it will take more time to create the mapping table. In some cases the applicant may want to provide sub-folders; in such case a zip file (of the sub-folders) should be uploaded in the documentation and the reference(s) in the mapping table(s) shall contain the location and the filename in the zip file.
Various documents are required for the authorisation. Such documents shall be provided in the documentation supporting the application. In case of positive decision related to the application the issuing authority has the obligation to check that the concerned documents are present in ERADIS. In case they are not, the decision will be positive but the authorisation will not be delivered to the applicant (pending the documents are uploaded).
The list of documents to upload in ERADIS are listed in the ERADIS homepage.
It is not necessary to use the issues log for all the questions occurring during the assessment of an application.
The purpose of the issues log is:
In practice all communications do not have to go through the issues log and other communication channels can still be used (e.g. phone or email). However, a user is expected to create an issue in the issues log in the following cases:
Note that nothing prevents the user to create an issue later on if this appears to be relevant.
Another aspect relates to the formulation of the issue. An issue may contain several questions but in that case, all questions need to be of the same type, have the same due date, etc. and the issue can only be closed when all questions are answered. It is left at the discretion of the user (and ultimately the project manager) to organise this in the most appropriate manner depending on the needs of the project.
Issues shall be created by users as soon as they evaluate that one of the purpose is met.