Transcript Introduction to EPRI Plant Information Model

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
www.epri.com
Report
1022684
3
EPRI Initiative that is Leading the Industry to a
Standard for Handover
www.epri.com
Report
1019221
4
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
F
D
D
S
D
D
D
R
W
G
S
S
P
E
C
S
Requirements
Physical
Configuration
An integrated management
program that enables
accuracy and consistency
Facility
Documentation
Controlled Processes
Maintain Relationships
10
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
Limitations of the Old Way
 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 (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.:
o
o
o
o
Skid Equipment
Safe Shutdown
Isolation Groups (what is tagged out simultaneously for PM Plan)
Power 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
Requirements
(Source Number)
Engineered Item
(TAG Number)
Contract
Design Basis
Functions and
Values and other
Commitments in
DCD/COLA
Codes & Standards
ITAAC
SSC & Attributes
Location &
Attributes
Engineering
Program
Specifications
Eng Drawings
16
Data/Document/Relationship Development Lifecycle
Requirements
(Source Number)
Engineered Item
(TAG Number)
Contract
Design Basis
Functions and
Values and other
Commitments in
DCD/COLA
Codes & Standards
ITAAC
SSC & Attributes
Location &
Attributes
Engineering
Program
Specifications
Eng Drawings
Procured Item
(Mgf/Model)
Vendor Manual
Vendor
Drawings
BOM
Specifications
17
Data/Document/Relationship Development Lifecycle
Requirements
(Source Number)
Engineered Item
(TAG Number)
Contract
Design Basis
Functions and
Values and other
Commitments in
DCD/COLA
Codes & Standards
ITAAC
SSC & Attributes
Location &
Attributes
Engineering
Program
Specifications
Eng Drawings
Procured Item
(Mgf/Model)
Vendor Manual
Vendor
Drawings
BOM
Specifications
Installed Item
(Mgf/Model/Serial)
Inspection
Report
Work Orders
PM Record
Test Results
ITAAC Pkg
18
Data/Document/Relationship Development Lifecycle
Requirements
(Source Number)
Engineered Item
(TAG Number)
Procured Item
(Mgf/Model)
Installed Item
(Mgf/Model/Serial)
Associate Serial Number Object
with Tag No.
Contract
Design Basis
Functions and
Values and other
Commitments in
DCD/COLA
Codes & Standards
ITAAC
SSC & Attributes
Location &
Attributes
Engineering
Program
Specifications
Eng Drawings
Vendor Manual
Vendor
Drawings
BOM
Specifications
Inspection
Report
Work Orders
PM Record
Test Results
ITAAC Pkg
19
Goal is to Extract the Data That Generated
Documents to be Consumed by all End Users
Standardized Attributes
Specs
• Flows
• Temperature
• Pressure
Margin
• Regulatory
• Design
• Operational
Component
Type
Calcs
PRA
Attributes
Environmental
•
•
•
•
Single Source
of “Truth”
•FSAR Design
Basis
•Calculation
Output
•Vendor
Specification
•IST Test
Result
•-Design
Change
AOV
MOV
FCV
Manual
• Assumptions
• Inputs
• Methodology
Knowledge
• Design basis
• Design
Margin
• Performance
• Operability
• 50.59
• Equip
Reliability
• Fulfillment of
Requirements
Decision
• RAW
• RISC
• Reliability class
• Wind load
• Temperature
• Flooding
Efficient Decision Making
Information
CMIS
20
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, highconsequence 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
Use Case of EPRI PIM to
Develop a Margin Management Model
ITAAC Result
Ongoing IST Trend
Actual Capability
Design Margin
Full Qualification
Analytical Margin
(Design Basis Value in
DCD/COLA)
SSC Fails to perform Intended Safety Function
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
CMIS will have a built in
CM “Taxonomy” with
Relationships that
connect:
1. Requirements (from
the DCD, COLA,
other Licensing Info)
28
Manage Requirements and Conduct more
thorough Design Impact Reviews
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
29
Manage Requirements and Conduct more
thorough Design Impact Reviews
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)
30
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 50.59 Evaluations
 Configuration Controlled Source of Data for
Maintenance, Calibrations, Post Maintenance
Testing Criteria, Inservice Testing, Inservice
Inspection, Equipment Reliability, Maintenance
Rule
Construction /
Test
Information
Supplier
Information
Document
Management
System
Requirements
Management
MS Office
Calculations
Specifications
Studies
2D Model
3D Model
Conceptual Configuration Information Management System Model
33
Construction /
Test
Information
Publish DOCUMENTS to Document Management System
Supplier
Information
Document
Management
System
Requirements
Management
MS Office
Calculations
Specifications
Studies
2D Model
3D Model
Conceptual Configuration Information Management System Model
Publish DOCUMENTS
Equipment DATA
34
Conceptual Configuration Information Management System Model
Publish DOCUMENTS to Document Management System
Publish DOCUMENTS
Construction /
Test
Information
Supplier
Information
Document
Management
System
Requirements
Management
MS Office
Calculations
Specifications
Studies
2D Model
3D Model
Equipment DATA
Requirements DATA
Equipment DATA
Geographic DATA
Doc to SSC &
SSC to Location
Relationship DATA
Document Meta DATA
Manufacture/Model DATA
Configuration Management Information System
Installed (serial #) DATA
35
Conceptual Configuration Information Management System Model
Publish DOCUMENTS to Document Management System
Publish DOCUMENTS
Requirements DATA
Equipment DATA
Geographic DATA
Doc to SSC &
SSC to Location
Relationship DATA
Rqm't ID
Construction /
Test
Information
Document Numbers
Establish Doc to Doc
Doc to SSC/Mgf/Model/Serial #
Doc to Requirements
Relationships
SSC DATA
Supplier
Information
Document
Management
System
Requirements
Management
MS Office
Calculations
Specifications
Studies
2D Model
3D Model
Equipment DATA
Document Meta DATA
Manufacture/Model DATA
Installed (serial #) DATA
Relationship DATA
Configuration Management Information System
36
Publish Changes
Back to CMIS
Margin
Management
Publish Changes
Back to CMIS
ITAAC
Engineering
Programs
Configuration Management Information System
Publish Changes
Back to CMIS
37
Configuration Management Information System
Information
Turnover to Client
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
Business
Problem
• 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
Solution
Benefits
Anticipated LongTerm Benefits
41
EPRI PIM Value Proposition
Business
Problem
Solution
Benefits
• 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
• 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
•
Anticipated LongTerm Benefits
42
EPRI PIM Value Proposition
Business
Problem
Solution
Benefits
• 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
• 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
• 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
Anticipated LongTerm Benefits
43
EPRI PIM Value Proposition
Business
Problem
Solution
• 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
• 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
Benefits
• 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
Anticipated LongTerm 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
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