1. Westinghouse/Southern/SCANA – New Build Configuration Management
Eric Pace – V.C. Summer – CM Supervisor
V.C. Summer 2&3 – Configuration Management Team
Prentice Gilbert – Vogtle- CM Supervisor
Vogtle 3&4 – Configuration Management Team
BOTH
Introduce ourselves and our roles within our Organizations
Don’t spend a lot of time here.

2. Objectives
Provide an update on construction progress for Summer 2&3 and Vogtle 3&4.
Provide a summary of the Joint Pilot on Information Turnover.
Provide summary of ongoing efforts with consortium on Configuration Management.
Provide an update on Configuration Management system development at both sites.
PRENTICE

3. ERIC
- Use slide to show site layout

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

5. PRENTICE
Slide showing Layout from Josh’s presentation last year. Feel free to replace with a better slide.

6. PRENTICE
Use this slide to include a more recent photo of Vogtle construction to use in discussing project progress. You can opt to not include a more recent picture and just discuss from previous slide.

7. Information Turnover Joint Pilot
Scope of Information Turnover Pilot
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

8. Lessons Learned Turnover Pilot Simulator & 301 Turnover
Underestimated Quantity of Documents
Handling of SUNSI information varied
File Size Transfer Issues
Shortfalls in Data Validation and Releasable Reviews
Simulator & 301 Turnover
Single point accountability (STS System & 301 Turnover Engineers)
Thorough walk downs (identified 161 punch list items for STS, 92 for 301)
Strong partnership with Construction Oversight
Clearly define expectations early for scope of turnover
Physical Boundaries
Documentation Expectations
Identifying/Transferring Manufacture Warranties
PRENTICE

9. Ongoing CM Activities Information Handover Processes
Information Turnover Contract Details
Master Equipment List Improvement
Program Data Acquisition
Station Equipment Labeling
BOTH

10. CMIS Development SmartPlant® Foundation Provides
Change Control
User Securities
Relationship Synchronization
Traceability
Over All Engineering Documents, Assets, and Requirements
ERIC

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

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

13. CMIS Development Phased Development Approach
Configuration Management Information System
Procedure Development: July 2015
Station Master Equipment List: December 2015
Engineering Documents: April 2016
Information Turnover: July 2016
Engineering Change Process: July 2016
Engineering Program Data: Late 2016
Procurement and Warehouse: Late 2016/Early 2017
ERIC

14. CIMS Development
PRENTICE

15. CIMS Configuration Information Management System
Equipment Database, MEL
Relates drawings, rooms, components, FSAR, MEL etc.
Interfaces with Maximo and Documentum
Automate Design processes: DCP’s ABN’s
Production Rollout: March 2015
PRENTICE

16. What is Enterprise Bridge (eB)?
eB is Asset Lifecycle Information Management
Assets
Plant & Equipment
Requirements
Documents
People & Organizations
Projects
Lifecycle
Design, Construction, Operation, & Maintenance
Information Management
Timely access to trusted information
PRENTICE

17. Solution Architecture
PRENTICE

18. Object Classification
Documents
Equipment
Requirements
Drawings
Pumps
Design Basis
Procedures
Valves
Safety Rqmts
Calculations
Switches
CFRs
PRENTICE
Correspondence
Test Equipment
Contracts
Invoices
Tooling
Test Plans

19. Contextual Mapping PRENTICE Change Events People Organizations
Equipment
Documents
PRENTICE
Distribution Order
Projects
Requirements

20. Change and Configuration Management in eB
Requirements
What must be there
What is there
What we say is there
PRENTICE
Closed-loop Change Process
Data and Documents
Items

21. Design Change Process Looks for other affected objects
Gathers objects using eB relationships
Refine by analyzing candidates
PRENTICE

22. Work Flows Document Upload Edit Document Review Document
Reject
Approve Document
PRENTICE
Post to
Documentum
Approve

23. Efforts to Date Handover Process Master Equipment List (MEL)
Process now well Established
Docs Requested – 25,282; Docs Received – 20,473
Synchronizing with Site Data Center
Master Equipment List (MEL)
50,000+ tags loaded to date
WEC, CB&I, and SNC MEL Development Team (MDT)
Subcomponent Review Board (SRB)
PRENTICE

24. Questions
ERIC