content_image/467611.jpg content_image/467612.jpg
<img src='content_image/467611.jpg'>

Document code: Security level: Effective date: ICT Governance 

PRO-0027.06 Internal 15/01/2019 

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

## 3.5.4. Maintenance Work 

The Change Manager is responsible for the planning of the scope of a Change Release. 

The Change Manager prepares a High-Level Maintenance Plans describing the Maintenance work to be performed. The High-Level Maintenance Plan focuses on the key areas to work on, any major changes to be implemented and related impact, and the benefit to Business of the work. Therefore, it is not a simple extract from the issue-tracking tool. 

The Programme Board approves the High-Level Maintenance Plan. Often it is approved as part of the Programme Plan. 

The (Product / Service) CAB is the governance body for Maintenance work. The work can be performed in multiple parts, for example over multiple Maintenance Releases. Please see sections 3.9 and 3.10 for further information on related governance boards and roles and section 3.5.2 on change management and the workings of CABs. 

## 3.5.5. Direct Service Changes 

Direct Service Changes are the ones that are not implemented via Project or Maintenance of any of the Products, for example changes in availability hours or support hours or in service level. These changes are either implemented as part of a Project or in Change Management. 

## 3.5.6. Release Management 

Release Management is in charge of maintaining the Release Plan, which consolidates the release planning of the Programmes. 

Two release windows have been identified, one in the spring (indicatively February to June) and one in the autumn (indicatively September to November). This approach has been selected to secure efficient management of the integration and the maximum availability of the necessary resources and facilities. Exceptions are possible if absolutely necessary, but discouraged. When Project and Maintenance work is planned, the Release Manager can be consulted for preliminary timing. 

The Release Management (RM activities focus on readiness for releasing, releasing interdependencies and releasing synchronisation aspects. 

