SNC/SCANA – New Build Configuration Management

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

INPO Update CMBG Meeting June 2013
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Plant Information Model (PIM) Breakout N1 – (1:00pm – 2:30pm), Monday, June 16, 2014 Russell Adams – EPRI Consultant Laurent Perkins, Bentley Kent Freeland,
Cadle & Yeates Ch 5 Revised by Ivor Perry Sept Detailed Planning - 1.
Software Configuration Management
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Configuration Management
National Finance Center’s 2008 Customer Forum EmpowHR 9.0 Billy Dantagnan Teracore.
Release & Deployment ITIL Version 3
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
SE-02 CONFIGURATION MANAGEMENT Today we talk about Software Configuration Management (SCM for short): - What? - Why? - How?
Web Development Process Description
Project Management Process Overview
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Software Configuration Management
Configuration Management (managing change). Starter Questions... Which is more important?  stability  progress Why is change potentially dangerous?
Identify steps for understanding and solving the
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Georgia Institute of Technology CS 4320 Fall 2003.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
Westinghouse/Southern/SCANA – New Build Configuration Management
Scott Butson District Technology Manager. Provide professional to all district staff Professional development has been provided on a regular basis to.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Federal Aviation Administration By: Giles Strickler, UCS Program Manager Procurement Policy (AJA-A11) Date:September 22, 2010 Unified Contracting System.
Project Management Process Transition & Closure Project Management Process Project Description Team Mission/ Assignment Major Milestones Boundaries Team.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Josh Olson Southern Nuclear - Vogtle 3&4
University of Minnesota Internal\External Sales “The Internal Sales Review Process” An Overview of What Happens During the Review.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 29 Slide 1 Configuration management.
Regulatory Streamlining Task Force Update Discussion Item December 6, 2011 Board of County Commissioners.
Software Configuration Management n Art of coordinating SW development to minimize confusion n Software quality assurance (umbrella) activity n Set of.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
State of Georgia Release Management Training
Vogtle 3 & 4 Commercial Facility Turnover and Information Handover Lessons Learned Elizabeth J. Johnson SNC CM Project Lead.
Project Management Processes for a Project
Report Performance Monitor & Control Risk Administer Procurement MONITORING & CONTROLLING PROCESS.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
Certifying Data in Controlled Databases for Direct Use ERIC PACE CM GROUP SUPERVISOR 1.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Software Configuration Management
Software Project Configuration Management
BUSINESS DRIVEN TECHNOLOGY
Testing the System.
Chapter 11: Software Configuration Management
Software Configuration Management
SNC/SCANA – New Build Configuration Management
Software Planning Guidelines
TechStambha PMP Certification Training
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Configuration Management (managing change)
Description of Revision
NRC Cyber Security Regulatory Overview
Plant Vogtle Units 3 and 4 Alex Thirkell.
ITIL: Why Your IT Organization Should Care Service Support
Kickoff Presentation Date of Presentation Presenter Name
ITIL: Why Your IT Organization Should Care Service Support
Vogtle 3&4 Configuration Management
Experience with an IT Asset Management System
Your Facility Your Information
Standard Design Process (SDP) Software Tom Czerniewski Entergy Nuclear
Enterprise Program Management Office
Chapter 11: Software Configuration Management
HART Technologies Process Overview
X-DIS/XBRL Phase 2 Kick-Off
ITIL: Why Your IT Organization Should Care Service Support
Final Design Authorization
Configuration Management
Managing Project Work, Scope, Schedules, and Cost
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

SNC/SCANA – New Build Configuration Management Eric Pace - V.C. Summer - CM Supervisor V.C. Summer 2&3 – Configuration Management Team Alex Thirkell - Vogtle - CIMS Lead Vogtle 3&4 – Configuration Management Team BOTH Introduce ourselves and our roles within our Organizations Don’t spend a lot of time here.

Objectives Provide an update on construction progress for Summer 2&3 and Vogtle 3&4. Provide summary of ongoing efforts with contractor on Configuration Management. Provide an update on Configuration Management system development at both sites. ALEX

ERIC - Use slide to show site layout

ERIC Use slide to talk about recent construction activities, issues, and progress

ALEX Progress as of January 2015. Use to compare against newer pictures.

ALEX Progress as of January 2016. Useful to show the descriptions.

ALEX Current Status. Cooling Tower (U4) – Almost complete Deaerator installed on Turbing Island (U3) Containment rings continued to be installed

Information Turnover Joint Pilot Concluded December 2014 Results of Information Turnover Pilot Information transfer infrastructure Insight into information review and acceptance Insight into Consortium information inventories Contacts within Consortium for Information Turnover Additional actions to be taken BOTH Information Turnover Includes: | For All: Records | - Systems Engineering Documents | - Areas Native Files | - Components Master Equipment List | - Programs Program Data 3D Model ________________________________________________________ Joint Pilot Participants are SCE&G, Southern Company, Westinghouse, and CB&I. The Objectives of the pilot were to identify all consortium information sources, Identify infrastructure and processes required for turnover Record activities and milestones required to support the information turnover and to transfer selected systems, areas and programs from the consortium to each customer Perform an inventory of available consortium information (documents and data) Identify the required utility program information (documents and data) Determine the transfer processes required for turnover of the information from the consortium to the customer The Focus Areas, systems, areas and program evaluated, as part of the pilot scope are: Standard Plant System, Spent Fuel Pool Cooling System (SFS) Standard Plant System, Non Class IE DC and UPS System (EDS) Site Specific System, Yard Fire Water System (YFS)/Vogtle Only Area, Main Control Room (MCR) Program, MOV Program

Ongoing CM Activities Common Turnover Processes Early Transfer of Records Phased Approach to Information Turnover Information Turnover Pilots Design Authority Transfer BOTH All of this equates to a common Information Turnover Plan/Process

Ongoing CM Activities Releasable, Disclosable, and Deliverable Native Files Calculations As-Built vs As-Designed Master Equipment List & Other Databases Station Equipment Labeling BOTH All of this equates to a common Information Turnover Plan/Process

CMIS Development SmartPlant® Foundation Provides Change Control User Securities Relationship Synchronization Traceability Data Consolidation Over All Engineering Documents, Plant Assets, and Regulatory Requirements ERIC

CMIS Development Milestones Information Turnover Ready – 2nd Quarter 2017 Procedure Development: Sept 2015 (Production) Station Master Equipment List: July 2016 Engineering Documents: July 2016 Information Turnover: December 2016 Design Authority Ready – 4th Quarter 2017 Engineering Change Process: July 2017 Requirements Mgmt & Tracking: September 2017 ERIC

CMIS Development Various Organizational Data Needs… Single Source of Truth ERIC

CMIS Development ERIC

CMIS Development SmartPlant® Foundation The CMIS System Will Improve: CM Principles Process Efficiencies Modification Overhead Engineering Programs Access to Information 3D Model Relationships Data Centralization Document-Tag Cross Referencing Critical Document Electronic Conversion, Centralization, Access Document Centric ERIC Time to Find and Verify Data

Configuration Information Management System CIMS – Vogtle 3&4 Configuration Information Management System ALEX Screenshot of software.

CM Strategy ALEX Establish the Process Implement Look ahead to Design Transfer

Handover/Turnover ALEX Solution Architecture for Handover/Turnover for both Documents and Tags

Object Classification Documents Equipment Requirements Drawings Pumps Design Basis Procedures Valves Safety Rqmts Calculations Switches CFRs ALEX All the objects types that are possible. Correspondence Test Equipment Contracts Invoices Tooling Test Plans

Contextual Mapping ALEX Change Events People Organizations Equipment Documents ALEX Each of these object types can be related to other objects. Distribution Order Projects Requirements

Design Change Process Looks for other affected objects Gathers objects using eB relationships Refine by analyzing candidates ALEX These relationships are ultimately utilized for determining impacts of the design change process.

Change and Configuration Management in eB Requirements What must be there What is there What we say is there ALEX All of this is done to ensure proper Configuration Management. Closed-loop Change Process Data and Documents Items

Efforts to Date Handover Process Master Equipment List (MEL) Process now well Established Requested – 100,000+ documents Received – 90,000+ documents Future: Full Synchronizing with Site Data Center Master Equipment List (MEL) 60,000+ tags loaded to date WEC, CB&I, and SNC MEL Development Team (MDT) Subcomponent Review Board (SRB) ALEX

Questions ERIC Eric Pace – eric.pace@scana.com Alex Thirkell – atthirke@southernco.com