Page History

...

3.2.1.1 Modify the Primary Coordinator Contact (PCoCo)

...

For Framework Contracts:

If an External Partner or Consortium Leader (Economic Operator) would like to modify the PCoCo for their Organisation, they must address their request by e-mail to the functional mailbox (FMB) of the respective Framework Contract Owner, who will then forward the request (if the request is validated) to the dedicated EC Funding and Tender Service Helpdesk service to apply the changes in the system.

...

• The LEAR must provide the full name, e-mail address and EU Login username of the new PCoCo in their request.
• The PCoCo must be from the same entity to be entitled as correspondent of the project (recognised by the same entity domain in the e-mail address).
• The EC Funding and Tender Service Helpdesk will automatically inform both concerned parties (Economic Operator and Framework Contract Owner) by e-mail on the outcome of the request.

3.2.1.2 Manage Project Roles (CoCo, CLSIGN)

Remember: As a general rule, a CoCo is automatically assigned as PCoCo for the procedure or project if they are the submission initiator of the tender.

For Contribution Agreements:

For Contribution Agreements, the PCoCo is communicated to the Contracting Authority by the representative of the organisation during the negotiation stage (i.e.

...

therefore before contract preparation). The PCoCo is then assigned to the contract by the EC Operational Manager during the contract preparation.

For a specific invitation, submission, or contract, LSIGNs, CoCos and PCoCos can manage the project-level roles of users that are within their own organisation (unique PIC ID), and any user within the organisation can have multiple roles.

For example: Organisation LSIGNs are able to sign contracts and amendements for the organisation, but if the orgaisation would need to restrict the signatory role for contracts and amendments, the LSIGN can nominate a CLSIGN to the contract (project-level). The LEAR or Account Administrator of the organisation would first need to appoint the LSIGN role to a user beforehand (organisation-level).

If any modification is needed for the PCoCo role of a Contribution Agreement, the Organisation will need to contact the Contracting Authority to request the required modification.

3.2.1.2 Manage Project Roles (CoCo, CLSIGN)

For a specific invitation, submission, or contract, Procurement LSIGNs, CoCos and PCoCos can manage the project-level roles of users that are within their own organisation (unique PIC ID), and any user within the organisation can have multiple roles.

For example (Procurement LSIGN and CLSIGN):

Legal Signatories (LSIGN or Procurement LSIGN) have the right to sign contracts and amendments managed through the Funding and Tenders Portal on behalf of the organisation, so their role is relevent at organisation and project-level.

An organisation can have an unlimited number of Legal Signatories.

For Procurement Contracts, Specific Contracts under Framework Contracts, or Contribution Agreements:

• If the orgaisation would need to restrict the signatory role for contracts and amendments, the Procurement LSIGN can nominate a CLSIGN to the contract (project-level). The LEAR or Account Administrator of the organisation would therefore first need to appoint the Procurement LSIGN role to a user of the organisation beforehand (organisation-level).
• If CLSIGN(s) are nominated for a contract, Procurement LSIGN(s) will no longer be able to sign the contract (and amendements – if relevant).
• If no CLSIGN(s) are nominated for a contract, then all Procurement LSIGNs for the organisation will receive notifications for the contract (and amendements – if relevant).
• Only and any Procurement LSIGN of an organisation can nominate or revoke the CLSIGN user role.

How to manage Project Roles - Procedure or Contract (CoCo/CLSIGN)

...