content_image/506796.jpg
<img src='content_image/506796.jpg'>

disaster recovery 

• Interactions in activities related to Enterprise Architecture (EA); 

• Interactions in the context of business / stakeholder management activities. 

The above is not meant to be exhaustive and can be subject to changes during the contract. In case of changes to ECHA organisation or to the Contractors of ECHA, the Contractor will be informed of the new counterparts replacing the current ones and the interaction model will have to be updated accordingly, including the related parts of the FQP. Details on ECHA organisation are provided in Annex 7 –  ECHA organisation. 

## 4.1.1.2. Interaction between contractors and third parties 

The Contracting Authority expects the establishment of direct working technical relationships between the Contractors in order to improve the overall efficiency of the service delivery. Cooperation and proactive attitude, irrespective of the ascertained responsibilities are critical success factors for successful interaction; thus, to ensure the correct functioning of ECHA’s operations. 

With regards to the interaction between the Contractors of the FWC666 –  mainly when the work requires the involvement of both lots – , ECHA will indicate: 

• The high-level activities to be covered by each lot 

• The high-level functional dependencies (whenever possible) 

• The time and cost constraints 

The Contractors will use this information and work together on the preparation of a common plan to deliver the work, including the detailed dependencies and risks. ECHA retains control over and may require full traceability of the information exchanged between the Contractors. Whereas ECHA requires direct collaboration among all contractors across the two lots, ECHA shall intervene in case of conflict arising. Failure to comply with the requirements on collaboration/ interaction shall result in the application of the corresponding compensatory measures as per Service Level Agreement (Section 7.3). 

The activities below are few examples of the joint work to be performed by the Contractors of the two lots: 

• Development of a Transform  project (Lot 1) using some of the existing components (Lot 2). 

• The Application Management services (Lot 2) required by a Transform  project (Lot 1) 

• Takeover and handover activities between lots 

Details of the activities of each lot are provided in the rest of the Work Packages of this document. 

In addition to the expected cooperation between the different Contractors of this FWC666, projects and services quite often involve additional parties, requiring contribution from Contractors outside this FWC666 or consisting of different components and different level of responsibilities. On such occasions it is essential that the contractor is willing to act as ECHA's single point of contact and take care of the communications and collaboration with the other teams, 'behind the scenes', without reliance on ECHA only. 

ECHA will contribute to the success of this FWC666 by supporting the contractor, providing business domain expertise, running the contracts in a transparent and smooth way, ensuring that other parties are collaborating, and assisting the contractor to understand and apply the governance and guidance in areas where the contractor is obliged to align with existing ECHA frameworks such as Enterprise Architecture, Security, and Automation. 

