content_image/504924.jpg content_image/504923.jpg
<img src='content_image/504924.jpg'>

Authority and/or a third party nominated by the Contracting Authority. The number (in principle no more than one per year) and timing of these audits are determined by the Contracting Authority. The Contracting Authority might not always notify the contractor in advance of the timing of the audit. 

The contractor must cooperate and support the audit team during its entire mission. After the audit report is released, the Contractor will issue his position regarding the points raised in the audit report. These will be discussed between the Contracting Authority and the contractor. Follow-up of the decisions, agreed between both parties, will be implemented via the QPRs, or if necessary, by conducting another verification audit on the contractor' premises. 

Please also refer to “article II. 24 ” of the draft Framework Contract (“Annex XX –  Draft FWC”) for details on the use of the contradictory procedure. 

Please refer to Annex 16 –  Service Level Agreement for applicable service levels. 

Note that audit reports shall be kept confidential by the Contracting Authority. 

## 4.2. IT Enterprise Architecture, Strategy and Security (WP 2) 

The following table describes the work packages covered under this work package. The Contractor shall have an adequate organisation, expected staffing, methodology, inputs and outputs to successfully engaging in the tasks and services provided. 

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

## 4.2.1. IT Enterprise Architecture and Strategy (WP 2.1) 

The products, services and technologies in scope of FWC66 6 form part of ECHA’s integrated IT landscape in the areas called “Industry channel” and “data platform”. ECHA’s target Enterprise Architecture document governs the evolution of such architecture (see Annex 4 –  2020-2023 Target IT Enterprise Architecture) as agreed at corporate level and overseen by ECHA’s Enterprise Architecture team. 

IT EA is always represented in the ECHA IT programmes on-going projects (and services if need be) via the internal network of Architecture Focal Points (AFP network), extending the EA team in the day-to-day activities. 

The IT EA also defines high-level objectives, principles and good practices that should be respected in all new developments, especially those proposing to introduce new capabilities, new technologies or related to management of data in domains of enterprise- level interest. The Contractor shall familiarise themselves with the existing EA landscape (see Annex 3 – 2018-2020 Target IT Enterprise Architecture) and its targets, as prerequisite to collaborate with ECHA’s Enterprise Architecture team and the AFP network and ensure that the delivered solutions contribute to the real isation of ECHA’s target Enterprise Architecture goals. 

ECHA aims at partnering with its IT contractors in all domains of Enterprise Architecture (business, data, application, and technology). Thus, ECHA requires the active engagement of contractors in the establishment and follow up of good practices and knowledge sharing in this area. 

