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

• Takeover 2: from the incumbent FWC ECHA/2017/09 Contractor for the related products; 

• Takeover 3: from the incumbent FWC ECHA/2017/10 Contractor for the related products; 

Annex 2a –  Products in scope gives a detailed overview of the platforms and its products to be taken over by FWC666 contractors. 

The FWC666 contractors are expected to take over existing documentation and to produce their own based on that where relevant. Evolutions of these are foreseen throughout the duration of FWC666. This approach will enable continuity of services and ensure that changes to the procedures proposed can be a priori validated by stakeholders in ECHA’s IT ecosystem. 

The FWC666 contractors ’ teams must be sufficiently sized for the takeover and at the required professional standards to be able to absorb the complexity of ECHA IT landscape and structure. The takeover teams must be able to start their duties as of the date required and perform all related tasks under the SC that will include the takeover duties. Any delay in composing/staffing the team will jeopardise the complete takeover phase. 

The FWC666 contractor ’s team must be allocated to the activity and remain as such as of the signature of the Specific Contract linked to the takeover. Personnel corresponding with core profiles (see Resources ) – when being replaced – will hand over the acquired knowledge according to the knowledge management strategy outlined in the takeover Plan. 

ECHA, via the incumbent and other contractors, will provide knowledge transfer on the products and the global architecture linked to the scope of the FWC666. The FWC666 future contactors shall ensure that a maximum number of staff (preferably all, but in any case, all staff linked to core profiles without exception) will be available to attend knowledge transfer activities. ECHA will provide takeover knowledge transfer only once and it is then up to each contractor to keep the knowledge internally. 

In all cases, the contractors ’ teams will cooperate with ECHA, the incumbent contractors and any other third parties nominated by ECHA. The following is a non-exhaustive list of activities and deliverables expected: 

## 4.3.2. Activities 

• Understand the role of the product or set of products for ECHA 

• State of play: backlog of Run and Grow activities, technical and business projects/evolutions planned or to be planned in short and mid-term, product quality (maintainability, code) 

• Be aware of the knowledge base and undertake it 

• Define, if needed, an action plan to bring the product to an agreed baseline and to be executed and finished before the end of the phase in-phase 

• Review with ECHA project/service manager the handover/takeover plan 

• Organise and perform the takeover with ECHA and the handing over Contractor 

• Set up, if needed, an action plan for team skills upgrade 

• Set up the whole working environment, tooling etc. in due time 

• Set up all application management activities. 

• Take over the responsibility of the service(s) from the incumbent Contractor 

