Document code:  PRO-0027.06  Security level:  Internal  Effective date:  15/01/2019  ICT Governance  o redefining priorities.  • escalates to the Programme Board as necessary, especially when it becomes  evident that the Project plan commitments cannot be kept regarding planned  scope, schedule, or resourcing, • in general, takes decisions on issues escalated to it, and  • manages any other issues brought to the attention or decision making of the  Project Board.  • has a clear scope that it works on, for example one Product or a single Service,  • ensures readiness of the change proposals brought to it, checking o for normal changes, the existence and maturity of ▪ the Request for Change (RFC),  ▪ the Change Impact Assessment (CIA), especially that impact to  interrelated / interconnected areas, for example to other Products  has been taken into account, and  ▪ the communication Plan.  o for pre-approval of a new standard change, the existence and maturity of  the Standard Change Pre-Approval (SCP).  • decides on change proposals brought to it,  o for Product changes, whether the change is suitable to be implemented as  maintenance work or if it should be implemented as part of a Project, and  o whether the change has been analysed sufficiently to proceed or if the  change should be further analysed before the CAB can make a decision.  • manages Product maintenance release and patching work, o deciding on composition of a maintenance release or a patch, bundling a  number of changes together, TEM-0129.01  Uncontrolled copy once printed. Ensure that the right version is in use.  Page  59  of  92 The following applies to CABs with product and / or service scope. For Product scope, the  CAB manages maintenance work, configuration changes and other similar changes to the  Product. For Service scope, the CAB manages the same related to all Products used to  implement the Service and other service specific changes as necessary. The Change Advisory Board  The Change Advisory Board manages changes within its scope. The CAB for ECHA IT  changes is called the iCAB, and is covered later in the document. This section does not  apply to it.  For Lightweight Projects, any discussion / meeting between the Project Manager and the  Project Executive can be documented as a Project Board meeting and meeting minutes  provided in an email.  The Project Board is chaired by the Project Executive.  3.9.4. Change Advisory Board (CAB)