Effective Change Management in the ET Project
Managing changes in the ET Project involves navigating the R&D phase, establishing a baseline design, and preparing for a lifecycle supported by proper documentation. This presentation outlines the key concepts, processes, and steps for effective change management to ensure quality and traceability throughout the project lifecycle.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Document ID ET-0221A-24 Document type Slides Document status RELEASED Author L. Latronico Verified by L. Orsini, L. Lucchesi, C. Olivetto Approved by A. Variola Request For Changes How to manage changes in the ET Project ET Symposium, Maastricht, May 7th2024 1 05/07/2024
Outline Context Definitions Flowchart Discussion 05/07/2024 2
Context We now operate in the ET Preparatory Phase R&D is ongoing Baseline design not yet established Many changes are expected PO prepares to support the entire ET lifecycle with delivery of project documents (TDR, PMP, QAP ) to the BGR for approving ET Configuration Management during engineering, construction and integration Changes must be managed to ensure quality, i.e. distribution of information and traceability 05/07/2024 3
Basic definitions Change Owner Root system Request For Change RFC Change Control Board CCB Deviation from released info or configuration (docs, specs, requirements, tech drawings) Initiator and responsible of the management process Physical or data system where the change originates Process for instantiating a request of a change and seeking approval Board of technical experts and relevant system managers to analyze and dispose (applies to major changes only) 4 05/07/2024
Main Change management steps Identification and description Specifies nature, reason, owner and root system Impact analysis and classification Defines which systems are affected Class is major if impact extends root system, else minor Approval Evaluation of the impact Recommendation (approve/ reject/ re-analyze) Validation Independent re-analysis of the approval process Notification distribution of change-related information Implementation Separate process not covered here 5 05/07/2024
RFC Flowchart Identification Description Classification Start of approval 05/07/2024 6
RFC Flowchart Impact analysis 05/07/2024 7
RFC Flowchart Validation Notification Implementation 8 05/07/2024
Discussion points Documents support change process RFC Change evaluation report Many changes are expected Change Register Change notification Key actors Change owner Root system manager Technical coordinator Definition of boards (CCB, Validation) on a case-by-case basis shall ensure technical competence, independent and redundant evaluations As far as the validation processes are concerned, the relevant board and processes should be defined a priori, associated to the relevant roles. 05/07/2024 9
