pim model workshop russell adams epri bob renuart unistar
TRANSCRIPT
PIM Model Workshop
Russell Adams EPRI
Bob Renuart UniStar
EPRI PIM WORKSHOP AGENDA
Screenshots EPRI PIM Model Live Demo How will a Utility develop CMIS with an “Imperfect
Start”? Next Steps
ScreenshotsEPRI PIM Model
PIM Features – Object Screen
4
Selected Object
Lifecycle
Parents,Children,Siblings
Views
Object Attributes
Attribute Related Items
Relationships
Industry References
CM Taxonomy
PIM View – Dynamic Reports
5
Selected Object….
PIM View – Dynamic Radial Diagram
6
Selected Object….
PIM Example – CM Taxonomy Relationships
7
Selected Object
Parent, Children, Sibling Relationships
CM Taxonomy
View
PIM View – Dynamic CM Taxonomy View
8
Selected Object….
PIM View – Dynamic Tree
9
Live Demo
How will a Utility develop CMIS with an “Imperfect Start”?
How will a Utility develop CMIS with an “Imperfect Start”?
Designate a Core Team that is Empowered to provide input for each Department
Make Decisions on:• Level of Requirements to track at a data level that will be related to
design data.• Data to be managed in CMIS – CM at the Data Level has an
overhead. • What data should be “published” into CMIS after the plant goes
operational.• Establishing Relationships, types of Relationships• Certifying Data that is not delivered by the EPC as Configuration
Controlled.• Functionality within CMIS
Compile the above Information and Develop a Functional Requirements Spec that will be issued for Bid
12
Obtain Stakeholder Input to better Define:
Department Data Needs that should be Configuration Controlled in CMIS
Data StructureFunctionality Desired from CMISDocument/Data Relationship StructureParticipate in Testing Software
13
Requirements Tracking in CMIS
Defining and Bounding the Scope of Requirements is the Labor Intensive Part. This has to be done first.
One Approach used by a New Build: Identify Requirements to the numerical paragraph level in the DCD, COLA, Other Licenses and Permits etc., that contain Quantitative Licensing Basis Values and establish Relationships to the SSC Tag Object.
14
Example of a Quantitative Requirement for CCW in the DCD
15
Another Example
16
Requirements Tracking in CMIS
Leveraging CMIS can:• Provide traceability to where the Requirement is
implemented in the EPC Lifecycle• Identify if a Requirement may be affected by a Design
Change by establishing Relationships to affected Documents/Data
• Identify what Design may be impacted if a Requirement is changed.
17
Bounding Data Managed in CMIS
Managing CM at a Data Level requires additional “overhead” A typical Pump Data sheet has 100-150 attributes. In reality only
about 25 need to be in CMIS at the DATA level (the Pump Data Sheet will still be available as a configuration controlled Document linked to the Tag Number and retrievable within CMIS).
How Decide? New Build practice is to predefine Attributes for each Object Class that:• Defines the Design Basis of the Objects• Supports Equipment Reliability • Is used in Maintenance Rule, PRA, DRAP• Is Operations Critical • Contains Data used in more than one application (i.e., is in the “hub” of the
Flower Diagram showed earlier) EXAMPLE. Work Control and the ISI Program require access to Weld Numbers, and Weld Attributes for SR Systems
• Contains Data that has no formal controlled database to manage CM CMIS will be Extensible so that more content can be easily added.
Goal is to start with a Compact, high use data set and add later as value is realized
18
Building Relationships
Many Document to Tag and Tag to Tag Relationships are built in the EPC 2D and 3D model. These relationships can be Inherited into CMIS
Many Document to Tag Relationships can be Inherited from the Document Number, i.e., System Number, Building Number, etc.
Consider Electronic Extraction of Tag and Document Numbers in the content of a document.
Document to Document Relationships for the most part have to be Manually Created.
Experience shows it takes an average of 10 minutes per document to open, review, identify, and record relationships. This could likely be cut in half with Electronic Extraction.
19
Establishing Quality Control Standards for Data Managed in CMIS
Data imported from the EPC Master Equipment List (MEL) should have high integrity.
Data imported from other sources should have a “recent,” approved PDF version that validates integrity.
Data that doesn’t fall into the above, may require revalidation before use in an Appendix B Application.
Caution: Don’t assume all the data in the 2D/3D models is Configuration Controlled
Use a Graded Approach for Data Change Control, e.g.,• Data that represents the Design Basis, full Appx B• Data that is important to Plant Operations, but not part of the
Design Basis, a lower level of control • Data that is purely Administrative. Admin Control
Tags, like documents, should carry Revision Level that changes whenever the attributes of the tag change.
20
Revalidating Data that has not been Configuration Controlled
Data Objects will be assigned Status Codes and Revision Levels in CMIS.
The Status Code will Caution the End-User re Integrity.
Once the End User validates, the Status Code will change. This can be an ongoing process.
21
Next StepsEPRI PIM Model
Next Steps -Industry Working Group Teams
Industry Working Subgroup Teams
Team 1• Finalize Relationship Choices• Finalize CM Taxonomy Model• Identify CM Taxonomy Model Standard Relationships
Team 2• Handover DocType Groups and Lifecycle Stages• Standard Set of Document Types and their related Doctype Group• Attributes for Configuration Information Management
Team 3• Identify and Leverage Results From Current NNPP Projects
Document Relationships Initiatives• Develop CM Taxonomy for Regulatory & Industry Codes that all US
NNP Must Comply With
24
PIM Handover Standard – Record & Document Types
25
PIM Feature – Inherited Object Attributes
26
Attribute Group Name Datatype Def.Value ChoicesDocument UID Document Date datetime (none) Document UID Document Number string (none) Document UID Document Title string (none) Document UID Document Type string (none) Document UID
Document Purpose
string
Document UID Document Revision integer (none) Document UID Document Development Status string (none) Draft; Final; Preliminary; Preliminary with Unverified AssumptionsDocument UID Document Use Status string (none) Information Only; Issued for Comments; Issued for Review; Issued for
Bid; Issued for Construction; Issued for Design; As-built; As-designDocument UID Document Version string (none) Design Control Design Authority Control Required boolean Yes Yes; NoDesign Control Safety Related Document boolean (none) Yes, NoDesign Control Contains Unverified Assumptions boolean (none) Yes; NoRecords Management Quality Assurance Record boolean Yes Yes; NoRecords Management Record Retention Classification string Lifetime
RecordLifetime Record; Production Nonpermanent Record; Programmatic Nonpermanent Record
Records Management Record Retention Period string Lifetime Lifetime;10 Years;3 Years
PIM Feature – Inherited Object Attributes
27
Attribute Group Name Datatype Def.Value ChoicesHandover Requirements
File Type string (none) 3D Model; Database; PDF; MS Word- doc; MS Excel- xls; Proprietary Format; Structured Data; Text - txt
Handover Requirements
Required Revision Category string Living Revision Controlled
Living Revision Controlled; Revision Frozen at Handover - Can be Superseded; Revision Frozen at Handover Archive Only
Handover Requirements
Access and Control Classification string Everyone Everyone; Intellectual Property; Limited Access; Proprietary; Safeguards
Handover Requirements
Retention Business Value string Essential Essential; Legally Mandatory; Interest; Phase Specific; Transitory
Handover Requirements
Access Frequency string Design Changes
Audit Purposes; Design Changes; Licensing Changes; Maintenance; Normal Operations
Handover Requirements
Signed Document Requirement boolean Yes Yes; No
Handover Requirements
Verification of Authenticity Requiredboolean Yes Yes; No
Handover Requirements
Verification of Authenticity Method string (none) Electronic Authorization (Signatures); Digital Stamp (PE); Printed Stamp (PE); Embossed Stamp (PE); Professional Engineer (PE) (Wet Signature); Wet Signatures
Handover Requirements
Hard Copy Required boolean No Yes; No
Handover Requirements
Native File Required boolean Yes Yes; No
Handover Requirements
PDF File Format Compliance Requirement
boolean Yes Yes; No
Handover Requirements
Required PDF File Format string (none) PDF, Formatted Text and Graphics; PDF, Image Only; PDF, Searchable Image (Exact)
Discuss Kickoff of Industry EPRI PIM Working Group Teams to• Populate Standard Handover Framework for Documents and Data
(Content)• Populate Standard Configuration Management Taxonomy
Reference Model (CM)
28
Under Construction
Next Steps -Industry Adoption
Industry Adoption –
Industry Team Participation Incorporate the EPRI PIM Standard for Handover and
Configuration Information Management into ISO 15926
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
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
30
Why?
Next Steps -Software Solution Vendor
?
Intergraph’sAdoption & Endorsement of PIM
Keith Denton Intergraph
Intergraph SP CMIS with EPRI PIM ModelLive Demo
Kevin Gribbin Intergraph
IBM’s Rational Modeling of EPRI PIM
Darrell Schrag IBM
EPRI PIM Model – Join Us
Thank you
35
CMIS SSC Taxonomy for EPC
36
CMIS SSC Taxonomy for EPC
Requirements Engineered Item
37
CMIS SSC Taxonomy for EPC
Requirements Engineered Item
38
CMIS SSC Taxonomy for EPC
Requirements Engineered Item
39
CMIS SSC Taxonomy for EPC
Requirements Engineered Item
40
Data/Document/Relationship Development Lifecycle
Requirements Engineered Item Procured Item
41
42
Requirements Engineered Item Procured Item Installed Item
Ambiguity?
HI EDE Standard
Differential Head, Rated
PMP DESIGN HEAD
RATED DIFFERENTIAL HEAD
Total Developed Head
AP1000 BG SUDS
ISO 15926
INPO Centrifugal Pump Model
Process Industry Practice (PIP Data Sheet)
American Petroleum InstituteAPI Data Sheet
Differential Head Rated
DIFF. HEAD
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
44
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
45
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
46
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
47
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
48
Configuration Management Information System
InformationTurnover to Client
49
CMIS will be the “Information Hub” of the Operating Plant Lifecycle Management System
50