Introduction to EPRI Plant Information Model (PIM) Russell Adams EPRI Bob Renuart UniStar

AGENDA What is the EPRI PIM Model Business Need Use Cases Value Proposition Workshop Objectives

EPRI Initiative that is Leading the Industry to Data Centric Processes 3 Report

EPRI Initiative that is Leading the Industry to a Standard for Handover 4 Report

What is the EPRI PIM Model

EPRI PIM Model History 1987: EPRI Technical Report - Guidelines for Specifying Integrated Computer-Aided Engineering Applications for Electric Power Plants Background: Many CAE Systems/Application Already Developed  Stand-alone and Unable to Share Plant Data  Resulting in Costly Redundancies in Capturing, Handling, and Maintaining data Objective: Develop Data Model Integrating All Plant Data for Use in Developing CAE Applications Results: Findings Demonstrated Need for a Plant Data Model 2010: Developed Plant Information Network (PIN) Study Model 2011: Updated PIN Study Model to Modern Plant Information Model (PIM) Developed a Standard Handover Framework for Data and Documents Developed a Standard Configuration Management Taxonomy and Reference Model Framework 6

EPRI PIM Model Today and Thinking Forward An Evolving Open Source Standard for Handover of Power Plant Data Incorporating  Standard Handover Framework  CM Taxonomy and Relationship Framework Leverage to support Implementation of a World Class CMIS throughout the NNPP Lifecycle Eighty (80) Percent usable by US NNPP Projects and adoptable by Non-US NNPP Projects

Business Need for EPRI PIM Model

Operating Fleet Business Problem Multiple Organizations exchange information and documents during EPC Transactions are primarily paper based with little relationships established The creation and management of information and documents has led to many disconnected data systems, applications, and environments The same piece of information can and does exist within many applications under different technical names with different meanings Minimal attention to delivery of information in a data format for commissioning, operations, and maintenance 9

PIM Model Objective: Leverage Automation to Maintain Configuration at a Data/Document Level 10 Requirements FDDFDD DRWGSDRWGS SDDSDD SPECSSPECS An integrated management program that enables accuracy and consistency Physical Configuration Facility Documentation Controlled Processes Maintain Relationships

Old Way of Managing Configuration Information Document List is Managed in a Document Management System that captures: Who What When Master Equipment List in a Separate Data Base: Each Equipment Tag Number is related to:  Safety Classification  Equipment Properties (flow, pressure, temp, etc.)  Some Drawings  Vendor Information  Membership to an Engineering Program 11

Old Way of Managing Configuration Information (cont) Separate System for Managing Requirements Design Basis Documents Owner Requirements Disconnected Database Multiple Databases for other Uses “copy” data from the MEL or worse Recreates it – Equipment Reliability MOV Program Inservice Test Program 12

Challenges for Configuration Control of Data The same Data often managed in separate, disconnected systems that complicates change control. Much Data is tied to the tag number that would benefit from a different relationship structure, e.g., Vendor data Limited use of a defined Hierarchy of SSCs and Documents that facilitates “Inherency” of data: A room ID should inherit the elevation, wall/slab IDs, Building Number and Island Designation it is associated and all of their attributes without having to key it in. An Equipment ID should inherit the system, system grouping, and component subtype, component type, component grouping it is associated and all of their attributes without having to key it in. 13 Limitations of the Old Way

Limitations of the Old Way (con’t) Limited use of Relationships – It is not only Important to Make Relationships, but just as Important to define the type of Relationship Document to Document Relationships. Examples:  Doc A “is a Design Input to” Doc B  Doc C “is a Requirement fulfilled by” Doc D  Doc D “is a Reference for” Doc A Document to Tag and Tag to Tag Relationships  Room ID – Elevation – Walls - Building – Island  Master Tag that Groups related tags, e.g.: oSkid Equipment oSafe Shutdown oIsolation Groups (what is tagged out simultaneously for PM Plan) oPower Dependency  Engineering Program (ISI, IST, ER, EQ, AOV, MOV) 14

Data/Document/Relationship Development Lifecycle Requirements (Source Number) Contract Design Basis Functions and Values and other Commitments in DCD/COLA Codes & Standards ITAAC 15

Data/Document/Relationship Development Lifecycle Engineered Item (TAG Number) SSC & Attributes Location & Attributes Engineering Program Specifications Eng Drawings Requirements (Source Number) Contract Design Basis Functions and Values and other Commitments in DCD/COLA Codes & Standards ITAAC 16

Data/Document/Relationship Development Lifecycle Engineered Item (TAG Number) Procured Item (Mgf/Model) Vendor Manual Vendor Drawings BOM Specifications SSC & Attributes Location & Attributes Engineering Program Specifications Eng Drawings Requirements (Source Number) Contract Design Basis Functions and Values and other Commitments in DCD/COLA Codes & Standards ITAAC 17

Data/Document/Relationship Development Lifecycle Engineered Item (TAG Number) Procured Item (Mgf/Model) Installed Item (Mgf/Model/Serial) Vendor Manual Vendor Drawings BOM Specifications Inspection Report Work Orders PM Record Test Results ITAAC Pkg SSC & Attributes Location & Attributes Engineering Program Specifications Eng Drawings Requirements (Source Number) Contract Design Basis Functions and Values and other Commitments in DCD/COLA Codes & Standards ITAAC 18

Data/Document/Relationship Development Lifecycle Engineered Item (TAG Number) Procured Item (Mgf/Model) Installed Item (Mgf/Model/Serial) Vendor Manual Vendor Drawings BOM Specifications Inspection Report Work Orders PM Record Test Results ITAAC Pkg Associate Serial Number Object with Tag No. SSC & Attributes Location & Attributes Engineering Program Specifications Eng Drawings Requirements (Source Number) Contract Design Basis Functions and Values and other Commitments in DCD/COLA Codes & Standards ITAAC 19

Goal is to Extract the Data That Generated Documents to be Consumed by all End Users FSAR Design Basis Calculation Output Vendor Specification IST Test Result -Design Change Information Design basis Design Margin Performance Knowledge Operability Equip Reliability Fulfillment of Require- ments Decision 20 Assumptions Inputs Methodology Calcs RAW RISC Reliability class PRA Attributes Wind load Temperature Flooding Environmental CMIS Efficient Decision Making Standardized Attributes Flows Temperature Pressure Specs Regulatory Design Operational Margin AOV MOV FCV Manual Component Type Single Source of “Truth” 20

CMIS will be the “Information Hub” of the Operating Plant Lifecycle Management System 21

Use Cases for EPRI PIM Model CMIS Use Cases What are the Benefits of a CM Structured to the EPRI Guideline?

Use Cases for a Data Repository with the PIM Architecture At this point, the Use Cases have been Qualitative – The use cases presented mostly relate to areas we have all had to deal with in a document centric world. The EPRI ANT Integration Committee has requested Quantitative Use Cases with Lifecycle Costs and Benefits – This is planned for 2013 EPRI will benchmark multiple global, high-risk, high- consequence industries that have been through the transition of a document centric to a data centric Plant Lifecycle Management System to determine the real value and payback realized, as well as lessons learned. 23

Use Cases for EPRI PIM during EPC Develop and Control Margins 24

EPRI PIM Model Ancestor View 25

SSC Fails to perform Intended Safety Function (Design Basis Value in DCD/COLA) Use Case of EPRI PIM to Develop a Margin Management Model Design Margin Full Qualification Analytical Margin ITAAC Result Ongoing IST Trend Actual Capability 26

Use Cases for EPRI PIM during EPC Develop and Control Margins Manage Requirements and Conduct more thorough Design Impact Reviews when the: Licensing Basis Changes (RAIs), Detailed Design Changes (Owner Request, RAIs), Construction Changes (Field Change) 27

Manage Requirements and Conduct more thorough Design Impact Reviews 28 CMIS will have a built in CM “Taxonomy” with Relationships that connect: 1.Requirements (from the DCD, COLA, other Licensing Info)

Manage Requirements and Conduct more thorough Design Impact Reviews 29 CMIS will have a built in CM “Taxonomy” with Relationships that connect: 1.Requirements (from the DCD, COLA, other Licensing Info) to the 2.Design and Operating information that fulfills the requirement

Manage Requirements and Conduct more thorough Design Impact Reviews 30 CMIS will have a built in CM “Taxonomy” with Relationships that connect: 1.Requirements (from the DCD, COLA, other Licensing Info) to the 2.Design and Operating information that fulfills the requirement to the 3.Installed information that validated the installed asset meets the Requirements through tests and inspections (ITAAC)

Use Cases for EPRI PIM during EPC Develop and Control Margins Manage Requirements and Conduct more thorough Design Impact Reviews. Manage Design Inputs that change often during EPC Manage Unverified Assumptions –Chaining Impact of a Design Document with a UVA on Issue for Construction Manage the impact on a Response to a Request for Information if the Response Basis Document Changes Single Source of Configuration Controlled Data for Engineering Programs, ITAAC, Construction, etc. Satisfied Owner/Operator during Handover and Turnover to Utility 31

Use Cases for EPRI PIM after Operational Modern Plant Lifecycle Management (PLM) Systems are Data Driven Access to Licensing Basis and Requirements to Support Operability Determinations and Functionality Assessments Tool to conduct Design Impact Reviews to support Plant Modifications and Evaluations Configuration Controlled Source of Data for Maintenance, Calibrations, Post Maintenance Testing Criteria, Inservice Testing, Inservice Inspection, Equipment Reliability, Maintenance Rule

Conceptual Configuration Information Management System Model 33

Conceptual Configuration Information Management System Model 34

Conceptual Configuration Information Management System Model 35

Conceptual Configuration Information Management System Model 36

37

38

CMIS will be the “Information Hub” of the Operating Plant Lifecycle Management System 39

Value Proposition for EPRI PIM Model

EPRI PIM Value Proposition Lack of a Standard for Handover is Leading to Difficulty in Expressing and Ambiguity in Interpreting Handover Content and Functional Requirements Resulting in Increased Cost and Time with the Net Effect of Lots of One-off Solutions and Re-Inventing the Wheel Business Problem SolutionBenefits Anticipated Long- Term Benefits 41

EPRI PIM Value Proposition Lack of a Standard for Handover is Leading to Difficulty in Expressing and Ambiguity in Interpreting Handover Content and Functional Requirements Resulting in Increased Cost and Time with the Net Effect of Lots of One-off Solutions and Re-Inventing the Wheel Business Problem EPRI PIM’s Standard Handover Framework and Configuration Management Taxonomy Reference Model can be leveraged by the Industry to Support Implementation of a World Class CM Program Throughout the Plant Lifecycle Solution Benefits Anticipated Long- Term Benefits 42

EPRI PIM Value Proposition Lack of a Standard for Handover is Leading to Difficulty in Expressing and Ambiguity in Interpreting Handover Content and Functional Requirements Resulting in Increased Cost and Time with the Net Effect of Lots of One-off Solutions and Re-Inventing the Wheel Business Problem EPRI PIM’s Standard Handover Framework and Configuration Management Taxonomy Reference Model can be leveraged by the Industry to Support Implementation of a World Class CM Program Throughout the Plant Lifecycle Solution Adopting EPRI PIM will Lead to More Standardized Hanover Specifications, Solutions and Software Applications/Systems Resulting in Cost and Time Savings by Reducing the Difficulty in Expressing and the Ambiguity in Interpreting Handover Content Benefits Anticipated Long- Term Benefits 43

EPRI PIM Value Proposition Lack of a Standard for Handover is Leading to Difficulty in Expressing and Ambiguity in Interpreting Handover Content and Functional Requirements Resulting in Increased Cost and Time with the Net Effect of Lots of One-off Solutions and Re-Inventing the Wheel Business Problem EPRI PIM’s Standard Handover Framework and Configuration Management Taxonomy Reference Model can be leveraged by the Industry to Support Implementation of a World Class CM Program Throughout the Plant Lifecycle Solution Adopting EPRI PIM will Lead to More Standardized Hanover Specifications, Solutions and Software Applications/Systems Resulting in Cost and Time Savings by Reducing the Difficulty in Expressing and the Ambiguity in Interpreting Handover Content Benefits Handover of Quality Information will occurs Timely and Seamlessly as Content that is Interrelated with Logical, Traceable, Reproducible and Manageable Relationship Connections between Requirements and SSCs Anticipated Long- Term Benefits 44

EPRI PIM Model Workshop Objectives Discuss how the EPRI PIM can be implemented in a value added way even if the Utility or EPC has an “Imperfect Start,” i.e., little data structure. Live Demonstration of PIM - The Power of Data Discuss Kickoff of Industry EPRI PIM Working Group Teams Discuss Industry Adoption Discuss Software Solution Vendor Adoption 45

EPRI PIM Model – Join Us Thank you 46