emc boston momentum user group 2011- delivering a global project through the documentum...
Post on 08-Sep-2014
741 Views
Preview:
DESCRIPTION
TRANSCRIPT
TRINITY TECHNOLOGIES 1 © 2011 Trinity Technologies Corporation
Documentum User Group Boston
Trinity Technologies Corporation:
Building a Global Project Infrastructure
October 11, 2011
Presenter: Rick Ekstrand
Co-President and CTO
TRINITY TECHNOLOGIES 2 © 2011 Trinity Technologies Corporation
Agenda
Trinity Technologies Introduction
Global Project Challenges
Design/Construction Example
Plant Operations Example
TRINITY TECHNOLOGIES 3 © 2011 Trinity Technologies Corporation
Trinity Technologies Corporation
Consultants on IT Solutions for the
Energy Industries
Extensive Client List in the Energy Industries
Industry Thought Leadership for Technology,
Business Processes, Organizational Change
About Trinity Technologies
TRINITY TECHNOLOGIES 5 © 2011 Trinity Technologies Corporation
Fundamental Driver for Energy Companies
Creating Value from the Information Asset™
Physical Asset Information Asset
TRINITY TECHNOLOGIES 6 © 2011 Trinity Technologies Corporation
Global Project Challenges
TRINITY TECHNOLOGIES 7 © 2011 Trinity Technologies Corporation
Global Project Collaboration
Today’s energy capital projects are being designed,
procured, and constructed by multiple global organizations,
often times part of a consortium
You could have the NSSS vendor delivering a design from
Japan, with engineering being done in the US and
construction handled in the Middle East
TRINITY TECHNOLOGIES 8 © 2011 Trinity Technologies Corporation
Global Project Collaboration
How are different organizations dispersed around the
globe contributing to the EPC on a project?
How do you exchange documents, drawings, data?
Especially with use of different systems and at different locals
How do you backup systems when they are being used around the
clock?
How do you notify all parties of updates?
How do you ensure that everyone - from design and procurement
to construction - are using current documents?
How do you manage RFI and design changes?
TRINITY TECHNOLOGIES 9 © 2011 Trinity Technologies Corporation
Global Project Structure
Design Construction Example
TRINITY TECHNOLOGIES 10 © 2011 Trinity Technologies Corporation
Total Creation and Management of the Information
Management System (IMS) for Project
Selection of applications in IMS system
Change management approach
Naming/taxonomy for project
Workflows between: Systems
Organizations
Design of data center
Security
Records management and turnover
TRINITY TECHNOLOGIES 11 © 2011 Trinity Technologies Corporation
High-Level Architecture
DC
DCTM
DC eRoom JPMO
DCTM
Site
DCTM
Site
DCTM
NSSSREF PLANT
DCTM
EPC
DCTM
On-Shore
Engineering
1&2
CONSTRUCTORTURBINE
VENDOR
NSSS Vendor
1
2
Automated Import to DC (Publish)
Transfer of transmittal to NSSS
FW
FW
Automated Import to EPC from DC export
3
3
Documentum
Documentum will:
Documentum
Inter-Systems Information Flow
SP P&ID SP Elec PDS
Documentum
Design Basis
Documents
SP Foundation
Data Drawings,
Correspondence
Marian
Pipe
Support
Isogen
TRINITY TECHNOLOGIES 15 © 2011 Trinity Technologies Corporation
Information Flow
P&ID SPI SPEL PDS
SAP
SPF - NSSS
Admin Db / Tech Db
Documentum EDMS
Workflow Engine
PWDb
Numbering System Validation
Workflow Engine
Primavera
Isom
etric
Model
SmartPlant Review
NSSS IMS
Architecture Overview
SPF
in Datacenter
replicated from NSSS
Update
Process
P&ID SPEL
MARIAN
SmartPlant ReviewDocumentum EDMS
replicated from NSSS
SPI
Project
StatusCEIDS Primavera
Vendors
Centra
E-MeetingWinPCS
Citrix
Update
Process
Co
nso
rtiu
mN
SS
S IM
S
TRINITY TECHNOLOGIES 16 © 2011 Trinity Technologies Corporation
Interface Diagram
Documentum POs with
associated
Equip Tags
Equip Tags
and
Descriptions
Drawings
and
associated
Equip Tags
Document
Status
Updates
TRINITY TECHNOLOGIES 17 © 2011 Trinity Technologies Corporation
Publishing from NSSS to Data Center
NSSS posts data into an exchange area in within the
Data Center file system NAS
FTP
From there it is picked up, processed, and loaded into the
Data Center Data is validated and transformed
Documents with metadata are loaded into the repository
Intelligent version logic
Transmittal is automatically generated and distributed
TRINITY TECHNOLOGIES 18 © 2011 Trinity Technologies Corporation
High-Level Architecture
NSSS to EPC to Owner
NSSS Vendor
EPC Vendor
OWNER
TRINITY TECHNOLOGIES 19 © 2011 Trinity Technologies Corporation
NSSS to Data Center Data Mapping
A Data Map has been created:
TRINITY TECHNOLOGIES 20 © 2011 Trinity Technologies Corporation
EPC Office- 09:30 AM EST
Paul authors new specification, and uploads it to the content repository, initiating review workflow.
Predictive caching job, based on a workflow, automatically pushes new spec to BOCS cache in ShangHai for review step.
Site Office 9:00 AM
Helena logs on to her computer when she arrives at work in the morning. She sees she has a spec for review in her inbox and is able to quickly download it from the BOCS cache to review.
TRINITY TECHNOLOGIES 21 © 2011 Trinity Technologies Corporation
Design Center
Project Responsible Engineer approves new Design Change for Construction. Lifecycle state is changed to “approved”.
Predictive caching job, based on a lifecycle state, automatically pushes new Design Change to all BOCS caches
Remote Plants
Plant Managers can quickly download latest DesignChange from nearby content cache.
TRINITY TECHNOLOGIES 22 © 2011 Trinity Technologies Corporation
Trinity “System Metrics”
TRINITY TECHNOLOGIES 23 © 2011 Trinity Technologies Corporation
Monitor Remote Servers
Monitor remote server performance data, Docbase server, Webtop
server, Database server
Monitor performance data capture is synchronized chronologically with
tests
TRINITY TECHNOLOGIES 24 © 2011 Trinity Technologies Corporation
IMS Change Management
Capturing best practices
Design basis information repository
What information can be changed?
Design change process Review
Approval
Notification
TRINITY TECHNOLOGIES 25 © 2011 Trinity Technologies Corporation
Plant Numbering System Structure
Locator
Code
Project
Type Code
Sequence
Number
Plant
Code
• This is the structure for both component numbering and
document numbering.
• Some of the same codes can be used for numbering both
documents and components.
• Caution: Always be clear if the entity in question is a
component tag number or an AP1000 document.
TRINITY TECHNOLOGIES 26 © 2011 Trinity Technologies Corporation
Project and Engineering Documents
Data Center
EPC
DI
NSSS
ProcurementJPMO
Site
Site
Collaborate
eRoom
Documentum
View All
Retrieve Project and Engineering documents
View All
DCRs,
NCRs
Collaborate
eRoom
Publish/
Link
to D
ocs
Engineering Documents
Assumptions
· Assumption – Each Entity will manage its
deliverables production using common project
procedures.
· The Project will manage a common set of
project procedures in the Data center
· Each Entity will publish its deliverables to the
DC. The DC is the official document
repository
· All document management reports will be run
based on the documents in the DC
· DCRs & NCRs – Initiated in the DC (Number
assigned), then published to the DC when
initiated (Issue approved) and when
dispositioned ((Solution approved).
Publish/
Link to Docs
DCRs, NCRs
TRINITY TECHNOLOGIES 27 © 2011 Trinity Technologies Corporation
Vendor Documents
Data Center
EPC
DI
NSSS
ProcurementJPMO
SITE
SITE
Equipment Spec Deviation
Review & Approval
DC
Rs
– In
itiate
d &
Ap
pro
ve
d
DocumentumPublish all Dispositioned
Vendor Document Submittals, PO
Amndmnts,
DCRs – Initiated & Approved
Publish all Dispositioned
VendorDocument Submittals,
PO Amendments
View All
Publish all Dispositioned
Vendor Document Subm
ittals, PO Amndm
nts,
DCRs – Initiated & Approved
· Position - The Chinese Procurement
Entity (Via JPMO) needs to publish all
Vendor Document submittals to the
DC to support progress updates.
Vendors
Review & Approval
Vendors
Review
&
Approval
Eq
uip
me
nt
Sp
ec
De
via
tio
n R
eq
ue
sts
Equip
Spec
Devia
tion
Revie
w &
Appro
val
Equipment Spec
Deviation Requests
RMI Vendor
Revie
w &
Ap
pro
val
Eq
uip
Sp
ec D
evia
tio
n
Revie
w &
Ap
pro
val
TRINITY TECHNOLOGIES 28 © 2011 Trinity Technologies Corporation
Equipment Specifications and Purchase Orders
Data Center
EPC
DI
NSSS
ProcurementJPMO
SITE
SITE
Equip
Specs
Collaborate
eRoom
Pu
blis
h
Documentum
Publish Deliv
erables
Retrieve Equipment Specs&
Publish PO’s, Amendments
View Procurement
Documents
DR
Equipment Spec
Deviation Requests
Collaborate
eRoom
Publis
h/
Lin
k to
PO
NSSS
Procurement
Publish Equipment Specs, Deviations
&
PO’s, Amendm
ents
Assumptions and Positions
· Assumption - The Data Center (DC) is the
Repository for Released Documents. Project
participants control their documents prior to
release.
· Assumption - EPC will maintain Document
Control for EPC products; DI may publish some
deliverables to DC
· Position – Review & Approval of Specs, Pos,
Deviations, Amendments, etc. are controlled
outside the DC (#, initiation & disposition) and
published to DC when released. Deviation
requests are published to DC upon initiation as
well as upon disposition.
· Assumption – The Procurement and JPMO
activities/publishing to the DC is per a separate
contract.
TRINITY TECHNOLOGIES 29 © 2011 Trinity Technologies Corporation
Correspondence
Data Center
EPC
DI
NSSS
ProcurementJPMO
SITE
SITE
SSW Correspondence
To/FromDI
Vie
w A
ll
Documentum
WEC/SSW
Numbered
Correspondence
View All
Numbered Correspondence
to/from
Named Parties
Positions
· NSSS and EPC will use a common index,
which is maintained in the Data Center.
Participants will also maintain
correspondence number indices in the DC
· Assumption – The Procurement and JPMO
activities/publishing to the DC is per a
separate contract.
SS
W C
orr
esp
on
den
ce
To
/Fro
m
WE
C
Vendors
Commercial Correspondence
Vendors
Com
mercial
Correspondence
TRINITY TECHNOLOGIES 30 © 2011 Trinity Technologies Corporation
Publication of Deliverables
NSSS
JPMO
· Action Item – EPC will need to
access DI DCTM or get reports of in
process work documents
eRoom
EPC
eRoom
Documentum
Deliverables Publishing
Data Center
· Correspondence
· Internal Documents
· (Copies of Deliverables)
· Deliverables and Indexes
Published by EPC
Design Institute
DI Document Mgt Sys
Publish Deliverables
· Project Deliverables
· Project Correspondence
· Document Indices
Documentum
· Internal correspondence
· Deliverables and Indexes
Published for Shaw by DI
Collaboration
Retrieve Deliverables &
Indices
TRINITY TECHNOLOGIES 32 © 2011 Trinity Technologies Corporation
Menubar
TRINITY TECHNOLOGIES 33 © 2011 Trinity Technologies Corporation
Menubar
TRINITY TECHNOLOGIES 34 © 2011 Trinity Technologies Corporation
Properties
TRINITY TECHNOLOGIES 35 © 2011 Trinity Technologies Corporation
Transmittal Menu Items
TRINITY TECHNOLOGIES 36 © 2011 Trinity Technologies Corporation
Best Practices Security
Overview
Password Policy and Procedure
Account Lockout Policy and Procedure
Local Policy and Procedure Audit Policy
User Rights Assignment
Security Options
Event Log
Server, Workstations, Laptops
User Naming Standards
Group Naming Standards
TRINITY TECHNOLOGIES 37 © 2011 Trinity Technologies Corporation
Persistent Protection of Content
You secure your content at rest…
You ensure only certain people
can access the content…
But once an authorized user opens the content,
they are free to do whatever they want with it!
This is where
Information Rights
Management (IRM)
is needed
TRINITY TECHNOLOGIES 38 © 2011 Trinity Technologies Corporation
Operations Example
TRINITY TECHNOLOGIES 39 © 2011 Trinity Technologies Corporation
Operations Documentum Repository
Nuclear Documents
Documentum Content Management in use since May 2002 for Nuclear
documents.
All documents and records available to entire fleet (10 sites) via Intranet (5,800+
licensed users) through single repository.
24/7 operation with real time changes available immediately.
Accounts Payable
Invoice scanning with character recognition.
Security In Processing
Contractor plant access documentation using form capture techniques, fax
interface, etc.
2,000 contractors each outage, 8-10 outages a year.
TRINITY TECHNOLOGIES 40 © 2011 Trinity Technologies Corporation
Data Points
Object Types and Volume Records: 8.0+ million, 1.2 million pages scanned per month.
Drawings: 500,000+ , 8,000 revisions per year via Workflow
Procedures: 100,000+, 24,000 revisions per year
Correspondence: 40,000+
UFSAR
Tech Specs
Design Documents: 50,000+
Training Lesson Plans
Invoice scanning with recognition for Accounts Payable
Personnel Screening Documentation (Background Check,
Entrance Tests, Fingerprints, Work History, Medical, etc)
TRINITY TECHNOLOGIES 41 © 2011 Trinity Technologies Corporation
Nuclear PassPort Interface
PassPort Control Documents Registry in PassPort enables real time
Configuration Management with Engineering, Maintenance, Operations.
One way interface push from PassPort to Documentum
Automated Creation of object in Documentum on creation of first document revision
in PassPort (create_cd)
Automated version creation in Documentum on creation of any additional revisions
(revise_cd)
Attribute and Status values passed to Documentum on field changes (attrib_chg)
Triggers Version to become Current in Documentum on Issue action in PassPort.
Synchronized within 20 seconds or PassPort action.
Viewing capability from PassPort image icons (no license)
Combines strengths of both programs
Eliminates need to have every document in Documentum.
TRINITY TECHNOLOGIES 42 © 2011 Trinity Technologies Corporation
Nuclear Drawings
Drawings Source files stored in Documentum with TIF Rendition used as
viewable document. AutoCAD software utilized.
Hybrid files stored using Virtual Documents.
Rendition process extracts data from AutoCAD title block to
populate key fields and Aperture Card hollerith data.
Workflows used for all drawing record revisions with electronic
signatures.
Aperture card hollerith text file and TIF output automated as step
in Workflow.
TRINITY TECHNOLOGIES 43 © 2011 Trinity Technologies Corporation
Nuclear Procedures
Procedures
Source files stored on line and exposed to users.
PDF rendition displayed for users as default.
Rendition services used to create PDF renditions.
Real time interface with Control Document Registry (PassPort / PIMS)
ensures correct revision available at all times.
25,000 revisions per year processed.
Workflows enables complex process in workflow.
Extractor Routine
Home grown application
Export renditions or source files for any folder grouping
Allows extraction of 1000+ renditions in minutes.
TRINITY TECHNOLOGIES 44 © 2011 Trinity Technologies Corporation
Records Application
ERMS – Electronic Records Management System
Built on Content Manager Doc Type
Front end web application built to efficiently enter and process records
at Department level.
Automated index from PassPort for Work Orders, Engineering
Changes, Document revisions, Action Items. Eliminates data entry for
several thousand records per month.
Goal is to move records out of department each day. No lingering.
Huge success in the high volume departments.
Significant improvements in Records program realized.
Records scanned using Kofax Ascent software (No OCR).
Final Records capture on either
Microform (> 10 year retention)
CD (3 – 10 yr)
Electronic storage (< 3 yr)
TRINITY TECHNOLOGIES 45 © 2011 Trinity Technologies Corporation
Conclusions: Trinity Project Infrastructure
1. World class scalable technology platform to support
the plant project effort
2. Unparalleled experience in the definition and delivery
of systems for power plants
3. A complete solutions delivery team
4. Major financial strength, assuring support for the full
life of the nuclear units
top related