52.The General Assembly may decide to establish co-operation with entities (Institutes, Universities, other Consortia, N(H)MSs) outside the ALADIN Consortium, under conditions to be determined.
53.A co-operation agreement shall specify, as a minimum, the objectives and areas of co-operation and the rights and obligations of the ALADIN Consortium and of the co-operating entity, in particular in terms of their compatibility with the provisions of Articles 8, 9 and 10.
54.Because there exists at the time of signing of this MoU an agreement between Météo-France and ECMWF concerning the use of the IFS code in the ALADIN System and because the signing of this MoU happens jointly with the one of an ALADIN-HIRLAM agreement, the implications of the agreement with ECMWF are addressed in Annex II and the cooperation with the HIRLAM consortium in Annex III.
55.A representative of the co-operating entity might be invited as an observer for the discussion of relevant points at the General Assembly meetings.
56.The resources available for the implementation of this MoU are:
The manpower committed on an annual basis by the Members and the acceding Members for their contributions to the agreed plans covering all activities referred to in Article 1, paragraph 3 above;
The ALADIN Annual Budget made available by the Members and acceding Members, defined as the envelope of resources required to support consortium-level overhead activities that cannot be covered by the manpower contributions of the Members and acceding Members.
57.The purpose of the ALADIN Annual Budget is to facilitate and enhance cooperation and interactions between the Members and acceding Members, with a view to increasing the collective value of their individual manpower contributions to the Cooperation, and the overall efficiency and usability of the ALADIN System.
58.The ALADIN Annual Budget should mainly cover some expenditure related to administrative or cooperation overheads and mobility that are necessary at Consortium level for efficient scientific and technical coordination and code maintenance.
59.The ALADIN Annual Budget comprises three parts:
a minimum flat rate financial contribution applicable to all Members, unless otherwise agreed by the General Assembly in exceptional circumstances, aimed at covering the absolute minimum necessary volume of the tasks listed in paragraph 59 above;
additional voluntary financial contributions of Members or grouping of Members (e.g. LACE);
‘in-kind’ contributions corresponding in general to consortium-level tasks other than those listed in paragraph 59 above.
60.The minimum flat rate financial contribution applicable to all Members shall not exceed a ceiling determined by the General Assembly for the duration of this MoU. (See last GA recommendation)
61.The financial part of the ALADIN Annual Budget is also fed by the entry fees of new Members and can also include royalties if agreed by the General Assembly.
62.The way of collecting and administrating the relevant financial contributions shall be agreed by the General Assembly, taking into account practical capacity of the Members being then in charge of the implied redistribution steps;
63.The financial contributions of Members that are also members of the RC-LACE, including their individual minimum flat rate contributions, may be contributed and administrated through LACE, provided these contributions are dedicated to the purposes outlined in paragraphs 58 and 59, and managed by the Programme Manager in accordance with the provisions of Article 4, paragraph 42 iv. (Too complex)
64.After approval, the ALADIN Annual Budget (three parts) is executed under the authority and control of the Programme Manager with designated ALADIN administrative support, and, when practical, with direct administrative support from Members.
65.Resource requirements (manpower and budget) are established and reviewed on an annual basis by the General Assembly. Commitments and allocation of resources are approved and recorded by the General Assembly. (In practice transversal monitoring of second and third part are impossible; this should be reflected in the MoU in one way or the other. If we separate the manpower and budget issues like suggested just below, the monitoring of the first part of the budget should reappear more prominently here)
66.The realisation of the manpower and budget commitments are monitored by and reported to the General Assembly. The record of cumulative manpower contributions of Members and acceding Members is maintained by the Programme Manager and made available to Members and acceding Members. The record at the time of signature of this MoU is attached as Annex I.
Information exchange within the Members, acceding Members and towards users
67.An ALADIN Newsletter, based on the scientific and technical contributions of the Members and acceding Members, is published regularly.
68.An official web-site is maintained, where all the relevant information about the project is published. A password-protected part of the web-site is available to the Members and acceding Members for confidential information exchange purposes.
69.The ALADIN Consortium makes its best efforts to present the ALADIN achievements at major scientific events (including its own Workshops) and publish the findings in suitable peer-reviewed journals.
70.The ALADIN Common Codes, along with all related intellectual property rights, shall be owned by the Parties and acceding Members in proportion to their respective contributions, as recorded by the General Assembly, without prejudice to the intellectual property rights for those parts for which a single originator can be identified.
71.The related rights will be protected by the Parties under the guidance of the General Assembly with the understanding that executive functions can be delegated as agreed to the Programme Manager.
72.Lists of ALADIN Co-owned Codes shall be included in relevant agreements with their co-owners, along with the definition of the respective rights and obligations of the co-owners.
73.Any Member contributing code or software to the ALADIN System, under this MoU without being the formal owner or right-owner of that code or software shall guarantee that the rights to use such code and software for the implementation of this MoU are granted to the Parties, and inform the General Assembly in advance of any restriction affecting the possible use of that code or software by the Parties.