Table C - Receiving Organisation Enterprise The Receiving Organisation/Enterprise will provide financial support to the trainee for the traineeship: Yes ☐ No ☐ If yes, amount (EUR/month): ……….. The Receiving Organisation/Enterprise will provide a contribution in kind to the trainee for the traineeship: Yes ☐ No ☐ If yes, please specify: …. The Receiving Organisation/Enterprise will provide an accident insurance to the trainee (if not provided by the Sending Institution): Yes ☐ No ☐ The accident insurance covers: - accidents during travels made for work purposes: Yes ☐ No ☐ - accidents on the way to work and back from work: Yes ☐ No ☐ The Receiving Organisation/Enterprise will provide a liability insurance to the trainee (if not provided by the Sending Institution): Yes ☐ No ☐ The Receiving Organisation/Enterprise will provide appropriate support and equipment to the trainee. Upon completion of the traineeship, the Organisation/Enterprise undertakes to issue a Traineeship Certificate within 5 weeks after the end of the traineeship. By signing this document, the trainee, the Sending Institution and the Receiving Organisation/Enterprise confirm that they approve the Learning Agreement and that they will comply with all the arrangements agreed by all parties. The trainee and Receiving Organisation/Enterprise will communicate to the Sending Institution any problem or changes regarding the traineeship period. The Sending Institution and the trainee should also commit to what is set out in the Erasmus+ grant agreement. The institution undertakes to respect all the principles of the Erasmus Charter for Higher Education relating to traineeships. Commitment Name Email Position Date Signature Trainee Trainee Responsible person12 at the Sending Institution Supervisor13 at the Receiving Organisation During the Mobility Table A2 - Exceptional Changes to the Traineeship Programme at the Receiving Organisation/Enterprise (to be approved by e-mail or signature by the student, the responsible person in the Sending Institution and the responsible person in the Receiving Organisation/Enterprise) Planned period of the mobility: from [month/year] ……………. till [month/year] ……………. Traineeship title: … Number of working hours per week: … Detailed programme of the traineeship period: Knowledge, skills and competences to be acquired by the end of the traineeship (expected Learning Outcomes): Monitoring plan: Evaluation plan: After the Mobility Table D - Traineeship Certificate by the Receiving Organisation/Enterprise Name of the trainee: Name of the Receiving Organisation/Enterprise: Sector of the Receiving Organisation/Enterprise: Address of the Receiving Organisation/Enterprise [street, city, country, phone, e-mail address], website: Start date and end date of traineeship: from [day/month/year] …………………. to [day/month/year] ……………….. Traineeship title: Detailed programme of the traineeship period including tasks carried out by the trainee: Knowledge, skills (intellectual and practical) and competences acquired (achieved Learning Outcomes): Evaluation of the trainee: Date: Name and signature of the Supervisor at the Receiving Organisation/Enterprise:
Preparation and Organisation of Meetings The Chairperson shall convene ordinary meetings of the Project Committee at least once every 6 (six) months and shall also convene extraordinary meetings at any time upon written request of any Member.
Intergovernmental Organizations As instructed from time to time by ICANN, Registry Operator will implement the protections mechanism determined by the ICANN Board of Directors relating to the protection of identifiers for Intergovernmental Organizations. A list of reserved names for this Section 6 is available at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved. Additional names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Any such protected identifiers for Intergovernmental Organizations may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such protected identifiers shall be transferred as specified by ICANN. Registry Operator may self-‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. SPECIFICATION 6 REGISTRY INTEROPERABILITY AND CONTINUITY SPECIFICATIONS
