TEM-0129.01  Uncontrolled copy once printed. Ensure that the right version is in use.  Page  19  of  92 • Product Roadmap  has been described in  PRO-0058 IT Product Management .  • Release Plan  consolidates the upcoming releases and other similar changes. This  includes Maintenance releases, Project releases etc. The Release Manager  maintains the Release Plan, which is common for all Products and Services.  • The Service Definition Package,  consisting of the Service Card, Technical  Service Description and Requirements & Verification document describe the  essence of the Service: what is offered, what kind of requests can be made, who  can request the Service, how requests are processed and what is the Service  availability. Approved by the Service Owner, after consultation from Service  Steering Committee as required. The SPD is created and updated as necessary for  Service establishment / improvement work. • Project Initiation Document (PID)  describes the planning for the project,  including scope, key objectives, budget, time, resourcing, organisation and way of  working. Approved by the Programme Board. PIDs are created as required to  launch project work. • IT Investment Vision  is an investment proposal. It provides the business case  and cost benefit analysis (ex-ante evaluation) justifying the proposed IT  investment. The Vision document may cover a multi-annual perspective and  includes a road map of the investment’s intended evolution over time. Approved by  the IT DPB. IT Investment Visions are not created and updated as required. • High-Level Maintenance Plan  describes the scope and budget of planned  maintenance work, composed of work suitable for implementation as maintenance  work (as defined under change management) over a period of time, and may  provide a road map of the maintenance releases. The High-Level Maintenance Plan  may be created as during the rolling planning work and approved as part of the  Programme Plan by IT DPB or it can be created later, in which case it is approved  by the Programme Board. Note that emergency changes do not require pre- planning nor formal board approval • Programme Plan documents the Programme’s planned work for the next one to  three years and the required resourcing to implement it. The Plan covers in  detailed manner the first year and in more road map like fashion the next two  years. Integral part of the planning are the plans to further developing the Services  and Products under the Programme’s responsibilities. Approved by the IT DPB. The  Programme Plans are the core content of the IT Master Plan. IT Programme Plans  are created as part of the rolling planning work. • Single Programming Document (SPD), IT Master Plan  and  Target IT  Enterprise Architecture  form the guiding strategic documents for the IT work,  with the first two covering the whole Agency and the latter two being specific to IT.  Directors approve these documents in the key governing bodies (Directors  Coordination Meeting and IT Directors Programme Board). SPD and IT Master Plan  are adopted by the Management Board and approved by the Budgetary Authorities;  therefore, they also provide the legal basis for the IT expenditure. The SPD and IT  Master plan are created as part of the rolling planning work. The external bodies are not part of ECHA ICT Governance and are shown purely to clarify  the overall landscape of the ICT Governance. Please see later in the document for more detailed descriptions of the Governance bodies.  Summary of the key governance documents:  3.2.5. Overview of the Key Governance Documents  Document code:  PRO-0027.06  Security level:  Internal  Effective date:  15/01/2019  ICT Governance 