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

## 1. Objectives of the Framework Contract 

The key objectives under this FWC are: 

1. To successfully support the achievement of ECHA’s Target Enterprise Architecture 2020-2023 and its future evolutions during the timespan of the FWC. 

2. To build a successful partnership among all the parties (ECHA and contractors) participating in the implementation of the FWC, based on effective: 

• FWC governance 

• Standardisation of practices and toolchains used throughout the Software Development Lifecycle (SDLC) and during the Build and Deploy process, particularly for knowledge management and collaboration between the parties, in order to facilitate sharing of and access to knowledge by all parties involved in servicing the portfolio in scope 

• Collaboration in a multi-party, multi-vendor environment. 

3. To provide excellent services to ECHA’s internal and external customers, having quality and smooth delivery of services, continuous improvement, innovation and increasing efficiency over time. 

ECHA's IT architecture landscape is a multi-party multi-vendor environment based on the integration of many different technical “ components ” , most of which are custom-built and some are provided by third parties (details in Annex 3 –  2018-2020 Target IT Enterprise Architecture). Several contractors service such architecture at the same time in their specific scope, performing development, maintenance, application delivery and release management tasks and service desk. Thus, end-to-end delivery of services and solutions require separate, yet integrated, contributions of the contractors. 

Occasionally, ECHA will require the contractor to take the overall lead in coordinating the end-to-end delivery. On such occasions the contractor shall act as ECHA's single point of contact and take care independently of the communications and collaborations with the other teams. 

With respect to the ongoing framework contracts that FWC666 will replace, ECHA aims at stepping up harmonisation and alignment of practices and toolchains used in the software processes to gain efficiency through standardisation and to ensure transparency and accessibility of knowledge to all parties involved in servicing the portfolio. To this effect, ECHA is investing on adopting a common SDLC and Build & Deploy environment, owned by ECHA and used by all contractors in a harmonised fashion. Details are provided in section 8.1 ECHA standard tooling. 

ECHA will contribute to the success of FWC666 by providing business domain expertise, running the specific contracts in a transparent and smooth way, supervising good collaboration amongst parties and assisting the contractor in applying the FWC governance in areas where the contractor shall align with existing ECHA frameworks such as Enterprise Architecture, Security, and Automation (see chapter 10. Table of ContentsAnnexes for details). 

During the execution of FWC666, the contractor is welcome to proactively provide feedback on how ECHA can be a better partner and make a better contribution towards the success of FWC666. 

