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
Screenshots
EPRI PIM Model
PIM Features – Object Screen
Selected Object
Lifecycle
Views
Parents,Children,Siblings
Relationships
CM Taxonomy
Object Attributes
Attribute Related
Items
Industry
References
4
PIM View – Dynamic Reports
Selected
Object….
5
PIM View – Dynamic Radial Diagram
Selected Object….
6
PIM Example – CM Taxonomy Relationships
View
Selected Object
Parent, Children,
Sibling
Relationships
CM Taxonomy
7
PIM View – Dynamic CM Taxonomy View
Selected Object….
8
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 Structure
 Functionality Desired from CMIS
 Document/Data Relationship Structure
 Participate 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 Steps
EPRI 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
Attribute Group
Document UID
Document UID
Document UID
Document UID
Document UID
Document UID
Document UID
Document UID
Name
Document Date
Document Number
Document Title
Document Type
Document Purpose
Document Revision
Document Development Status
Document Use Status
Datatype
datetime
string
string
string
string
integer
string
string
Def.Value Choices
(none)
(none)
(none)
(none)
Document UID
Design Control
Design Control
Design Control
Records Management
Records Management
Document Version
Design Authority Control Required
Safety Related Document
Contains Unverified Assumptions
Quality Assurance Record
Record Retention Classification
string
boolean
boolean
boolean
boolean
string
(none)
Yes
(none)
(none)
Yes
Lifetime
Record
Lifetime
Records Management Record Retention Period
string
(none)
(none)
(none)
Draft; Final; Preliminary; Preliminary with Unverified Assumptions
Information Only; Issued for Comments; Issued for Review; Issued for
Bid; Issued for Construction; Issued for Design; As-built; As-design
Yes; No
Yes, No
Yes; No
Yes; No
Lifetime Record; Production Nonpermanent Record; Programmatic
Nonpermanent Record
Lifetime;10 Years;3 Years
26
PIM Feature – Inherited Object Attributes
Attribute Group
Handover
Requirements
Handover
Requirements
Name
File Type
Handover
Requirements
Handover
Requirements
Handover
Requirements
Handover
Requirements
Handover
Requirements
Handover
Requirements
Access and Control Classification
string
Retention Business Value
string
Access Frequency
string
Signed Document Requirement
boolean
Handover
Requirements
Handover
Requirements
Handover
Requirements
Handover
Requirements
Required Revision Category
Datatype Def.Value Choices
string
(none)
3D Model; Database; PDF; MS Word- doc; MS Excel- xls; Proprietary
Format; Structured Data; Text - txt
string
Living
Living Revision Controlled; Revision Frozen at Handover - Can be
Revision Superseded; Revision Frozen at Handover Archive Only
Controlled
Everyone Everyone; Intellectual Property; Limited Access; Proprietary;
Safeguards
Essential Essential; Legally Mandatory; Interest; Phase Specific; Transitory
Design
Audit Purposes; Design Changes; Licensing Changes; Maintenance;
Changes Normal Operations
Yes
Yes; No
Verification of Authenticity Required boolean
Yes
Yes; No
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
Hard Copy Required
boolean
No
Yes; No
Native File Required
boolean
Yes
Yes; No
PDF File Format Compliance
Requirement
Required PDF File Format
boolean
Yes
Yes; No
string
(none)
PDF, Formatted Text and Graphics; PDF, Image Only; PDF,
Searchable Image (Exact)
27
Under Construction
 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
Next Steps Industry Adoption
Industry Adoption –
Why?
 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
Next Steps Software Solution
Vendor
?
Intergraph’s
Adoption & Endorsement
of PIM
Keith Denton Intergraph
Intergraph SP CMIS
with EPRI PIM Model
Live 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
Requirements
Engineered Item
Procured Item
Installed Item
42
Ambiguity?
RATED DIFFERENTIAL HEAD
ISO 15926
Total Developed Head
DIFF. HEAD
INPO Centrifugal Pump Model
American Petroleum Institute
API Data Sheet
PMP DESIGN HEAD
Differential Head Rated
AP1000 BG SUDS
Differential Head, Rated
HI EDE Standard
Process Industry Practice
(PIP Data Sheet)
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
44
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
45
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
46
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
47
Publish Changes
Back to CMIS
Margin
Management
Publish Changes
Back to CMIS
ITAAC
Engineering
Programs
Configuration Management Information System
Publish Changes
Back to CMIS
48
Configuration Management Information System
Information
Turnover to Client
49
CMIS will be the “Information Hub” of the
Operating Plant Lifecycle Management System
50