Upload
austen-barrett
View
263
Download
0
Tags:
Embed Size (px)
Citation preview
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 Framework6
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
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
FDD
DRWGS
SDD
SPECS
An integrated management program that enables accuracy and consistency
Physical Configuration
Facility Documentation
Controlled Processes Maintain RelationshipsControlled 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.:
o Skid Equipment
o Safe Shutdown
o Isolation Groups (what is tagged out simultaneously for PM Plan)
o 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/COLACodes & StandardsITAAC
15
Data/Document/Relationship Development Lifecycle
Engineered Item(TAG Number)
SSC & AttributesLocation & AttributesEngineering ProgramSpecificationsEng Drawings
Requirements(Source Number)
Contract Design Basis Functions and Values and other Commitments in DCD/COLACodes & StandardsITAAC
16
Data/Document/Relationship Development Lifecycle
Engineered Item(TAG Number)
Procured Item(Mgf/Model)
Vendor ManualVendor DrawingsBOMSpecifications
SSC & AttributesLocation & AttributesEngineering ProgramSpecificationsEng Drawings
Requirements(Source Number)
Contract Design Basis Functions and Values and other Commitments in DCD/COLACodes & StandardsITAAC
17
Data/Document/Relationship Development Lifecycle
Engineered Item(TAG Number)
Procured Item(Mgf/Model)
Installed Item(Mgf/Model/Serial)
Vendor ManualVendor DrawingsBOMSpecifications
Inspection ReportWork OrdersPM RecordTest ResultsITAAC Pkg
SSC & AttributesLocation & AttributesEngineering ProgramSpecificationsEng Drawings
Requirements(Source Number)
Contract Design Basis Functions and Values and other Commitments in DCD/COLACodes & StandardsITAAC
18
Data/Document/Relationship Development Lifecycle
Engineered Item(TAG Number)
Procured Item(Mgf/Model)
Installed Item(Mgf/Model/Serial)
Vendor ManualVendor DrawingsBOMSpecifications
Inspection ReportWork OrdersPM RecordTest ResultsITAAC Pkg
Associate Serial Number Object with Tag No.
SSC & AttributesLocation & AttributesEngineering ProgramSpecificationsEng Drawings
Requirements(Source Number)
Contract Design Basis Functions and Values and other Commitments in DCD/COLACodes & StandardsITAAC
19
Goal is to Extract the Data That Generated Documents to be Consumed by all End Users
20
CMIS
Efficient Decision Making
Standardized Attributes Single Source
of “Truth”
20
Use Cases forEPRI PIM Model
CMIS Use CasesWhat 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
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 the2.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 the2.Design and Operating information that fulfills the requirement to the3.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 50.59 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 Model3
D M
od
el
2D
Mo
de
l
Re
qu
ire
me
nts
Ma
na
ge
me
nt
MS
Off
ice
Ca
lcu
lati
on
sS
pe
cif
ica
tio
ns
Stu
die
s
Do
cu
me
nt
Ma
na
ge
me
nt
Sy
ste
m
Su
pp
lie
rIn
form
ati
on
Co
ns
tru
cti
on
/T
es
tIn
form
ati
on
33
Conceptual Configuration Information Management System Model3
D M
od
el
2D
Mo
de
l
Re
qu
ire
me
nts
Ma
na
ge
me
nt
MS
Off
ice
Ca
lcu
lati
on
sS
pe
cif
ica
tio
ns
Stu
die
s
Do
cu
me
nt
Ma
na
ge
me
nt
Sy
ste
m
Su
pp
lie
rIn
form
ati
on
Co
ns
tru
cti
on
/T
es
tIn
form
ati
on
Equipment DATA
Publish DOCUMENTS to Document Management System Publish DOCUMENTS
34
Conceptual Configuration Information Management System Model3
D M
od
el
2D
Mo
de
l
Re
qu
ire
me
nts
Ma
na
ge
me
nt
MS
Off
ice
Ca
lcu
lati
on
sS
pe
cif
ica
tio
ns
Stu
die
s
Do
cu
me
nt
Ma
na
ge
me
nt
Sy
ste
m
Su
pp
lie
rIn
form
ati
on
Co
ns
tru
cti
on
/T
es
tIn
form
ati
on
Equipment DATA
Publish DOCUMENTS to Document Management System Publish DOCUMENTS
Manufacture/Model DATAInstalled (serial #) DATA
Equipment DATAGeographic DATA
Doc to SSC &SSC to Location
Relationship DATA
Requirements DATA
Configuration Management Information System
Document Meta DATA
35
Conceptual Configuration Information Management System Model3
D M
od
el
2D
Mo
de
l
Re
qu
ire
me
nts
Ma
na
ge
me
nt
MS
Off
ice
Ca
lcu
lati
on
sS
pe
cif
ica
tio
ns
Stu
die
s
Do
cu
me
nt
Ma
na
ge
me
nt
Sy
ste
m
Su
pp
lie
rIn
form
ati
on
Co
ns
tru
cti
on
/T
es
tIn
form
ati
on
Equipment DATA
Establish Doc to DocDoc to SSC/Mgf/Model/Serial #
Doc to Requirements Relationships
Publish DOCUMENTS to Document Management System Publish DOCUMENTS
Document Numbers
Relationship DATA
Rqm't ID
Manufacture/Model DATAInstalled (serial #) DATA
Equipment DATAGeographic DATA
Doc to SSC &SSC to Location
Relationship DATA
Requirements DATA
Configuration Management Information System
Document Meta DATA
SSC DATA
36
En
gin
eeri
ng
Pro
gra
ms
Configuration Management Information System
Publish ChangesBack to CMIS
ITA
AC
Publish ChangesBack to CMIS
Mar
gin
Man
agem
en
t Publish ChangesBack to CMIS
37
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 DataDiscuss Kickoff of Industry EPRI PIM Working
Group TeamsDiscuss Industry AdoptionDiscuss Software Solution Vendor Adoption
45