1. V. C. Summer Nuclear Stations Transition to a Data Centric Paradigm CMBG Atlanta June 2013

2. OBJECTIVE Address aspects of implementing an interconnected data centric CMIS, encompassing the entire CM Life Cycle, that supports timely validation & verification of plant safety, design, operations, and maintenance 2

3. GOALS 1.Define CMIS 2.Address the vision and planning process for implementation of a data centric CMIS 3.State challenges of CMIS implementation post EPC 4.Discuss benefits of CMIS in a post EPC realm 5.List Benefits of inclusion into an EPC 6.Identify Overall Lessons Learned 3

4. What is CMIS? CMIS is an Information Repository that stores Plant Configuration Information in a “Single Source of Truth” that can be drawn upon by multiple Applications for controlling Plant Activities that depend on accurate, reliable, and easily retrievable information. 4

5. WHY CMIS Necessary to effectively maintain information configuration control in an increasingly expanding data driven society Document only approach will be unduly challenged to manage configuration control Continuous Improvement in work quality and processes Economics 5

6. 6

7. ILLUSTRATIVE EXAMPLE Needed changes in attitude and behavior Compare similar transition issues from: Document Centric to Data Centric information control AND Analog to Digital Controls 7

8. CMIS CM TRIANGLE 8 Requirements FDDFDD DRWGSDRWGS SDDSDD SPECSSPECS An integrated management program that enables accuracy and consistency Physical Configuration Facility Documentation Controlled Processes Maintain Relationships

9. VCS CMIS Project Background  2007 AP1000 Builders Group development of utility data requirements  2008 began Configuration Management Software discussion with Software Vendors  2008 EPRI new build CM and handover initiatives  2008-2011 Information Gather Trips  2011 Developed Business Case  2012 Senior Staff approval  2012 Software Vendor Selected & Contract Signed  2013 - 2014 Development in Five Phases 9

10. Business Problem Multiple Organizations exchange information. Transactions are primarily paper based Many disconnected data systems The same information exist within multiple applications Different names and meanings for same information Data Turnover format not compatible with Owner use 10

11. DEVELOPING CMIS I.CMIS Vendor software products are tools II.Ensure Department Input on Functionality and Content III.Design CMIS as Single Source of CM Controlled Data IV. Bound Data Scope to control Data Management Cost V.Structure CMIS to Facilitate Data Turnover from Vendor VI.Develop CMIS in Phases VII.Ensure CMIS is easily Expandable VIII.CMIS implements Plant CM from Const - Plant Ops life 11

12. Bounding Data Managed in CMIS Managing CM at a Data Level requires additional “overhead” Considerations to determine what is controlled in CMIS: –Importance to Protection of Health and Safety of Public –Defines the Design & Licensing Basis –Operations Critical - Commercial risk value –Multiple application use –Frequency of use –Contains Data that has no formal controlled database –Used in required programs MR, DRAP, EQ, M&TE, ISI, etc Goal is to start with a Compact, high use data set that can be expanded as value is realized 12

13. Building Relationships  Many Document to Tag Relationships are built in the EPC Plant model.  Documents to Tag Relationships created in other tools have to be Manually Created.  Document to Document Relationships have to be Manually Created.  Take Advantage of the EPRI PIM Model Efforts 13

14. HOW IS SCANA DEVELOPING CMIS I.Created a dedicated CMIS team composed of Stakeholder and IT personnel II.Designated a Core Team of Stakeholders that is Empowered to provide input for each Department III.Working with Intergraph for a Five Phased fast track implementation. 14

15. Core Team Member Responsibilities I.Define Department Data Needs to be Configuration Controlled in CMIS II.Provide input on Data Structure III.Define Functionality Desired from CMIS IV.Define Document/Data Relationship Structure V.Participate in Testing Software 15

16. FIVE PHASE IMPLEMENTATION 16

17. POST EPC CHALLENGES Identification of required information Define information format for receipt Building Staff while developing and implementing CMIS Final Detailed Design Not Complete Working with Vendors post EPC EPC’s needs vs Owner/Operator 17

18. End Results One source of critical to function controlled data with multiple attributes that are consumed by multiple applications and changed from one application. Data quality that can be confidently used by all levels of applications by specified milestones. Data and Document Relationships that will build a design basis taxonomy to support configuration control of changes and operability determinations of the plant. Ability to manage as-designed, as-specified, as-built, and as-tested configurations of the plant. Access to data and documents via the 2D and 3D Models Electronic Delivery of Compliant, “as-built” Information for Smarter Operation and Maintenance Satisfied Happy Customers – User Friendly & Responsive 18

19. BENEFITS OF INCLUSION INTO EPC Same as END Results for Post EPC Benefits Clearly defined information turnover expectations (what & format) Limited if any keying of information Improved & Faster validation of information No bow wave of information to address Capture of Tribal knowledge from Beginning Improved Customer /Vendor Alignment 19

20. SUCCESS KEYS LESSONS LEARNED Get IT involvement and input from the start Start Now – Planning takes years Stakeholder input received up front and built into the process Perform Business case early Obtain Senior staff approval and budget Leverage industry expertise (EPRI,INPO,NEI, CMBG, NIRMA) Identify required Information and format Incorporate into the initial EPC contract Establish a DATA Steward Team Make IT your best Friend 20

21. ILLUMINATING EXAMPLE Changed Attitudes and Behaviors Analog Film Camera to Digital Cameras (including Smart Phones) How many of us now regularly use film today vs 10 years ago. Now ask where information technology will be 10 years from now? This will also necessitate a continuous improvement in CM to stay abreast of the current and future challenges. 21

22. Questions LET’S BUILD EFFECTIVE, RELIABLE, EFFICIENT CM 22