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

for the Contractor to fulfil its duties under this FWC666. ECHA retains the right to on-board additional and/or other tools where deemed appropriate to fulfil its duties during the life- time of the FWC666. 

Furthermore, all pertinent information related to execution of this FWC666 will be stored in these tools and that any such information is the intellectual property of ECHA. 

ECHA may quality check and audit the usage of the tools, data quality, process compliance, etc. These activities may be tasked to a third party, if ECHA so decides (see also section 4.1.8 Cooperation with the Contracting Authority during audits (WP 1.8)). 

## 8.2. Middleware/platforms 

With regard to the SDLC, ECHA requires the Contractors to use specific versions of specific middleware and platforms for products . These are managed by ECHA’s as part of the adopted technology roadmap (see Annex 6), which the Contractors shall respect when developing and managing products for ECHA. 

## 8.3. Licensing 

ECHA will provide licenses for the SDLC standard tooling when technically and financially feasible. In cases where technical constraints arise, the issue will be handled through the governance and agreements made via specific contracts or FWC666 amendment. 

For middleware, platforms and any other components required for the Contractors to fulfil its duties under the FWC666 that are running on ECHA infrastructure (whether on-premise, off-premise, private cloud, public cloud etc.), ECHA will cover the costs for licenses. The cost for any other licenses will be covered by the Contractors. 

Licensing for monitoring of application management required by the Contractors to fulfil its duties will initially be with the Contractors (ref. section 8.4 Possible future prospects). 

## 8.4. Possible future prospects 

In line with the SDLC harmonization efforts, ECHA is committed to realizing continuous efficiency gains with the progressive consolidation of the tooling used for development and IT service delivery. 

To this end, further improvements could be achieved by consolidating other processes to the same ecosystem. Please see Annex 18 –  ECHA standard tooling for further details. 

## 9. General requirements 

## 9.1. Starting date and duration of the Framework Contract 

The Framework Contract enters into force as of the date when the last contracting party signs, indicatively expected to be in January 2021. 

The execution of tasks may not start before the Framework Contract enters into force. Signature of the Framework Contract imposes no obligation on the Agency to purchase. Only the signature of specific contracts will be binding on the Agency. The execution of the tasks for a specific contract may not start before the corresponding specific contract(s) under the Framework Contract has been signed. 

For LOT 1, the Framework Contract shall be signed for 24 [twenty-four] months and can be renewed automatically under the same conditions up to two times, the first time for a period of 24 [twenty-four] months, and the second time for a period of 24 [twenty-four] 

