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

## 3.5.8. Records and Documents 

• CAB related files (ECHA DMS, under the Service’s activity code based DMS folder structure, please see earlier sections). 

• Maintenance work fil es (ECHA DMS, under the Service’s activity code based DMS folder structure, please see earlier sections). 

• Programme Related documents, including Programme Board documents (ECHA DMS, under the Programmes activity code) 

• Project files and records (ECHA DMS, under the Project activity code), at minimum 

o link to the related, approved version of the Final Investment Vision document (only when the Project is part of an ongoing Investment) 

o Project Initiation Document 

o Communication Plan 

o minutes of Project Board meetings 

o Project Closure Report 

• Release Management files (ECHA DMS, under the Release Management activity code) 

• iCAB Change Requests 

• iCAB files 

• PLA-0015 IT BCP - IT Continuity Technical Preparedness Plan 

## 3.6. Operative IT work including ITIL Service Operations 

Operative IT work implements the ITIL Service Operation lifecycle phase , and concentrates on providing the implemented Services for consumption in a stable, reliable, and cost efficient way, while at the same time remaining flexible and receptive to controlled changes and continual improvement. 

Operative IT work includes for example application management, user support, application and infrastructure monitoring, maintenance break planning, software patching, incident management, and the operative implementation of a number of horizontal aspects. 

Service Operations is also responsible for the management of service levels and service level agreements with outsourcing Contractors. In fact, the operative IT work is largely outsourced. Managing outsourced operative work is a core responsibility of the Service Team . Therefore, the outsourcers are responsible for the largest share of the operative processes, which are not within the scope of the ECHA ICT Governance. 

