AS WITNESS. The Parties have caused this Consortium Agreement to be duly signed by the undersigned authorised representatives in separate signature pages the day and year first above written.
AS WITNESS. For: ESKOM HOLDINGS SOC LTD [No lower than an E-Band Manager to sign] (Name of witness in print) Duly authorised SIGNED at on
AS WITNESS. The Parties have caused this Consortium Agreement to be duly signed by the undersigned authorised representatives in separate signature pages the day and year first above written. It is too impractical for all Parties to sign the same document at the same time. The procedure proposed for the signatures is widely used: Each Party signs a separate signature page as many times as there are Parties (it is also possible to sign only 1 or 2 originals as only one fully signed copy is necessary according to Belgian Law). The Coordinator gathers all originals and then delivers the whole package consisting of the text and all signatures (original or copies) to all Parties. [INSERT NAME OF PARTY] Signature(s) Name(s) Title(s) Date [INSERT NAME OF PARTY] Signature(s) Name(s) Title(s) Date [INSERT NAME OF PARTY] Signature(s) Name(s) Title(s) Date [Attachment 1: Background included] According to the Grant Agreement (Article 24) Background is defined as “data, know-how or information (…) that is needed to implement the action or exploit the results”. Because of this need, Access Rights have to be granted in principle, but parties must identify and agree amongst them on the Background for the project. This is the purpose of this attachment. !! Beware – Attachment 1 is a vital document – check what your project partners are listing and (more importantly) not listing!! Earlier framework programmes required the parties to define Background and to make any exclusions "specific". This was translated into the Consortium Agreements by having Background exclusion lists, mostly in addition to the list of Background Included. The new MGA for H2020 obliges the parties to “identify and agree” upon the Background for the Project. Therefore, DESCA2020 proposes to work with actively listed Background. It is the responsibility of the parties to make this ‘agreement on Background’. It seems reasonable to expect that if parties know of a specific need for access rights to specific Background, they will be able to identify this up front (potentially with limitations). In any case, such a duty to inform is explicitly mentioned in Article 25.2 and 25.3 of the MGA) and this information needs to be shared before accession to the GA. The counterpart of working with a positive list is that the parties fully accept that anything not listed simply IS no Background, and that therefore, there is no reason to “exclude” it. That is the reason why there is no need any more to explicitly exclude backgrou...
AS WITNESS. THE EMPLOYEE
AS WITNESS the hands of the duly authorised representatives of the parties hereto the day and year first before written.
AS WITNESS. THE MUNICIPAL MANAGER 2. ..…………………………….
AS WITNESS. THE SELLER
AS WITNESS. The Parties have caused this Consortium Agreement to be duly signed by the undersigned authorised representatives in separate signature pages the day and year first above written. Signature(s) Name(s) Prof Zerbetto Francesco Title(s) Head of Department Date
AS WITNESS. For: [NAME OF OTHER PARTY]
