Piping Specification
25194-3PS-PL-031
Procedure for Creating and Distributing
Smartplant Review Data
25194-3PS-PL-031
Page 1 of 11
reserved.
0321/098/
06
CHW
SJH
DH
PKS
03/02/06
TD
SJH
DH
PKS
Rev
Date
Revision
By
Chkd
Appr
Client
25194-3PS-PL-031
Page 2 of 11
Contents
1. Purpose...............................................................................................................................................
2. Scope..................................................................................................................................................
3. Definitions...........................................................................................................................................
4. General................................................................................................................................................
5. Set-up..................................................................................................................................................
6. SmartPlant Review Usage...................................................................................................................
7. Archiving and Backup.........................................................................................................................
8. Plotting................................................................................................................................................
1.
Purpose......................................................................................................................................33
2.
Scope..........................................................................................................................................33
3.
Definitions...................................................................................................................................33
4.
General........................................................................................................................................44
5.
Set-up..........................................................................................................................................55
6.
7.
8.
Plotting................................................................................................................................101011
25194-3PS-PL-031
Page 3 of 11
1.
Purpose
1.1.
2.
3.
Scope
2.1.
The scope of this document covers the hardware requirements, set-up, and
working methodology to be used while working with the Intergraph SmartPlant
Review program on the Jamnagar Refinery Expansion Project. It does not
provide an explanation of the commands used in the Smart Plant Review
software.
2.2.
Users requiring assistance with SmartPlant Review commands are directed to use
the project document Elementary Level Reference Guide for Intergraphs Design
Review, or the help files that accompany the software.
2.3.
Definitions
3D CAD Model
Back up
SmartPlant Review(SPR)
SmartPlant Review
Integrator
SmartPlant Review
Session
Microstation
25194-3PS-PL-031
Page 4 of 11
4.
PDS
Server
Workstation
General
4.1.
Key design personnel will use the software to review the quality of the design in
the 3D PDS CAD model with representatives of Reliance Petroleum Limited.
This type of review is known as a Formal Review.
4.2.
Design personnel will use the software to review the quality of the design in the
3D PDS CAD model. This type of review is known as Informal Review. Both
Formal and Informal SmartPlant Review sessions are to be run from the
SmartPlant Review workstations. The Formal reviews will be copied to the
project data server for archiving by the CAD Coordinator by EDS.
4.3.
Due to the poor measurement facilities provided in SmartPlant Review it will not
be used for isometric checking.
4.4.
The display of the 3D CAD Model using SmartPlant Review is a copy of the
PDS 3D CAD Model. The Microstation design files and data files containing the
intelligence from the PDS Model Database are copied to the SmartPlant Review
workstation. This copying process is performed using the SmartPlant Design
Review Integrator. This application is accessed through the PDS Shell menu.
4.5.
The standard PDS 3D CAD Workstations will be used to create the SmartPlant
Review session using the SmartPlant Design Review Integrator. The node
for the session files should be set to the appropriate SmartPlant Review
workstation. Contact the Complex CAD co-ordinator to obtain the correct node
number. Ensure that the correct PATH is entered for the session files.
4.6.
4.7.
All of the SmartPlant Review specific workstations will be connected via a high
performance 100Mbps network. This will enable each SmartPlant Review
25194-3PS-PL-031
Page 5 of 11
5.
Set-up
5.1.
Hardware/Software
5.1.1. All computers will use the Microsoft Windows XP operating system, workstation
or server as appropriate.
5.1.2. The PDS Batch Server will have the Intergraph PDS 3D software including the
Integrator software, loaded onto it. The PDS Data server will hold the project
specific PDS data files stored within the appropriate project specific directory
structure.
5.1.3. The SmartPlant Review specific workstation is to be a Bechtel Build
BECXP_LON_VI_R1 Intel(R) Xeon(TM) CPU 3.6GHz 2 GB of RAM
Micosoft Windows XP professional Version 2002 Service Pack 1 or better.
5.1.4. The SmartPlant Review specific workstation shall have the latest certified
version of the SmartPlant Review software
25194-3PS-PL-031
Page 6 of 11
6.
Figure 6-1
6.1.1. It is necessary to initially run the SPR Integrator to establish that the project data
is working with SmartPlant Review . To make use of the processing power of the
PDS servers the first batch run of each unit SPR session will be run on a server
serverdesignated by PAG..
6.1.2. The complex piping CAD co-ordinator will be responsible for creating a SPR
session for each uniteach unit within the complex. Each session should process
files from all of the disciplines.
25194-3PS-PL-031
Page 7 of 11
Figure 6-2
6.1.5. Then select the PDS models to be included in the SPR session.
6.1.6. The SPR session should be batch run. To avoid the server backups it is
suggested that a start time for the batch run be set tobefore 22:00
6.1.7. The first session should be run such that the queue PDlabel_builder is a pipe
queue to the remote server as advised by the PAG group. The files should be
shipped to the appropriate complex SPR workstation.
25194-3PS-PL-031
Page 8 of 11
Figure 6-3
6.2.1. The *.SPR files created for each of the PDS models during the first run of the
SPR sessions contains a snapshot of the data contained in the PDS Oracle data
base. To ensure that all the files used with SmartPlant Review are kept up to
date it is necessary to update the information by running SPR sessions daily.
25194-3PS-PL-031
Page 9 of 11
6.2.2. The complex piping CAD co-ordinator will be responsible for creating schedule
the abovea SPR session that will be run at the end of each working day. To avoid
the server backups it is suggested that a start time for the batch run be set
beforeto 22:00
6.2.3. The daily SPR sessions will be run from a local Pdlabel_builder queue on a
SmartPlant Review workstationReview workstation situated on the project floor.
6.2.4. The complex piping CAD co-ordinator will be responsible for creating SPR
sessions for the checking areas. A checking area may consist of one or more
PDS models. The purpose of the checking areas is break up the entire Unit
into smaller practical working areas. This will reduce the amount of data
required to be processed by the computer hardware and the network. These
sessions will be run as and when required.
6.2.5. Once the SPR sessions have been run the complex piping CAD co-ordinator is
responsible for copying the all of the *.dri, *.dgn, *.SPR, *.prp, *.tag files to the
location as defined in appendix b allow access to the SPR data by CAD
workstations.
6.3.
6.3.1. A new SPR session will be created for each Formal review held. The unique
naming convention will ensure that the data from multiple Formal SPR sessions
can be easily recalled after archiving.
6.3.2. Formal reviews will require the overall SPR session created at section 6.1 is to be
used. Due to the large quantity of data involved sufficient time for the session to
run should be considered prior to holding the formal review
6.3.3. After a formal review all files including the *.dgn, *.prp, *.dri, *.SPR, and *.tag
files are to be copied from the SmartPlant Review workstation to CD backup
sub-directory on the project server.
6.4.
6.4.1. Typically informal reviews will be conducted with *.DRI files created for each of
the checking areas created at paragraph 6.2.4. Whilst it is possible to create
and use any *.DRI files which cover the required model bases, using the
checking area *.DRI files will yield data that is consistent across the project.
6.4.2. The user will create a sub-directory for the informal checking area review using
the convention defined in appendix b. The name of this sub-directory will be
the users BUN (Bechtel Unique Name).copy the data over to the local
workstation and review data. Cad-Coordinators will need to setup a seamless
system such that the users get the latest data from the server over to their local
workstation.
6.4.3. Using the Windows File Manager copy the <checking area> .DRI, <checking
area>.TAG, <checking area>.SET files from the SPR data storage sub-directory
to the sub-directory created in paragraph 6.4.2. For additional information see
appendix b.
25194-3PS-PL-031
Page 10 of 11
6.4.4. Rename all of the files from <checking area>.* to < BUN>.* . Start the
SmartPlant Review application and use the <BUN>.DRI file. All comments
made using the PLACE TAG command will be stored in the <BUN>.TAG
separate from all other project SmartPlant Review data.
6.4.5. Using a text editor such as notepad or PFE add the following new line to the DRI
file above the first line in the DRI file starting with dgn{ name:
dgn_search_path {<drive>:<path>}
Where g:\pds\SPR\261 is the path to the project SPR data located on the
remote server.
6.4.6. It is not usually necessary to back up informal review data. Should a situation
occur where data from an informal review is required to be archived, copy the
necessary files to an archive sub-directory on the project server. These files will
then be backed up in the usual manner with the rest of the project data.
6.5.
6.5.1. A booking schedule will be maintained by the Complex SPR Co-ordinator so that
the SPR terminals may be reserved for specific times and dates where required.
At other times the terminals should be used on a first- come first-served basis.
Inter discipline Co-operation will be needed during these free-for-all times.
6.5.2. Where this practice results in a discipline being unable to use the SPR terminals
to their satisfaction the Complex SPR Co-ordinator may allocate specific time
slots for each discipline during the week to resolve the problem. The Project SPR
Co-ordinator should be made aware of the problem so that extra hardware may
be acquired, or if possible loan a SmartPlant Review workstation from another
complex.
6.5.3. Users who are unable to gain access to a SmartPlant Review workstation to run
a SmartPlant Review session pertaining to a single PDS design area or less can
use SmartPlant Review loaded onto theira PDS workstation (TD300 spec or
greater).
6.5.4. Under NO circumstances are comments to be made using SmartPlant Review
when the DRI file has a filename the same as a formal SPR session.
6.5.5. Do not write SPR tags to a remote *.TAG file. All DRI files must be located on
the local workstation. This will ensure that the tag file is local also. It is possible
for two users to write to the same SPR tag file (*.TAG). When two or more
users write comments to the same SPR tag file typically some of the comments
are lost and the tag file becomes corrupt.
6.6.
SPR Construction
6.6.1. Construction has a requirement to view the SPR datamodels. A team at site will
create SPR sessions based on their requirements. All PDS projects will be
workshared with Site and they can run SPR sessions locally.
25194-3PS-PL-031
Page 11 of 11
25194-3PS-PL-031
Page 12 of 11
7.
7.1.
7.1.1. Project design personnel will not be responsible for backing up project data to a
removable media such as DAT tape or Compact Disks. This is the responsibility
of EDS.
7.1.2. Data stored on the remote servers in the project directories will be backed up by
EDS as defined in the service level agreement between the Bechtel Corporation
and EDS. Requests for the retrieval of backed up data should be made through
the complex CAD co-ordinator.
7.1.3. Notify EDS of the requirement for them to copy the files located in the CD
backup sub-directory to a standard CD using their CD writer. Additionally,
provide EDS with the name of the complex piping CAD co-ordinator that
should be contacted upon completion of the assigned task. EDS are to advise the
appropriate complex CAD co-ordinator once the CD containing the files is
available for collection.
7.1.4. EDS are responsible for storing the archived CDs. EDS will provide the
appropriate complex CAD co-ordinator with a reference ID for each CD, and a
list of the files stored against that ID.
7.1.5. To retrieve an archived CD the complex CAD co-ordinator will provide the
reference ID of the CD to the EDS representative for retrieval.
7.1.6. The archived CDs are to be returned to EDS for storage after use.CAD
Coordinator needs to ensure that once the formal review is finished, he copies
over the data along with tags to the PDS server so that it is archived along with
rest of the files.
7.1.7.
8.
Plotting
8.1.
25194-3PS-PL-031
Page 13 of 11
Appendix A
SPR DesignReview Integrator - Label Builder Interface
25194-3PS-PL-031
Appendix A Page 1 of 2
The Label Builder Interface window must be completed as below :Field Name
Description
SmartPlant Review
Number
After an entry is made to the Control File Path field (above), the
system echoes the file path to the Tag File Path field. The tag file
path represents the location of the tag file.
NOTE: When entering the path of files located on the server. While the project data may be located
on the GR: drive, this identifier only related to the your workstation. The same project data may be
on the F: drive relating to the server.
25194-3PS-PL-031
Appendix A Page 2 of 2
Appendix B
File and Directory Naming Convention
B-1A Project SmartPlant Review data storage sub-directory on a remote file server
All SmartPlant Review related files for informal reviews will reside in a sub directory on
the remote server. The sub-directories will be as follows:
COMPLEX
SHARE
DESIGN REVIEW
DATA SUB-DIRECTORY
zarom
\\lonsbr10<Server>\2519
4\zarom
\drv\<unit name>
zcppp
\\lonsbr10<Server>\2519
4\zcppp
\drv\<unit name>
zcrud
\\lonsbr10<Server>\2519
4\zcrud
\drv\<unit name>
zfccc
\\lonsbr10<Server>\2519
4\zfccc
\drv\<unit name>
zfuel
\\lonsbr10<Server>\2519
4\zfuel
\drv\<unit name>
zmero
\\lonsbr10<Server>\2519
4\zmero
\drv\<unit name>
zoffs
\\lonsbr10<Server>\2519
4\zoffs
\drv\<unit name>
Zpru3
\\lonsbr10<Server>\2519
4\zpru3
\drv\<unit name>
zreft
\\lonsbr10<Server>\2519
4\zreft
\drv\<unit name>
zsulf
\\lonsbr10<Server>\2519
4\zsulp
\drv\<unit name>
zutil
\\lonsbr10<Server>\2519
4\zutil
\drv\<unit name>
25194-3PS-PL-031
Appendix B Page 1 of 3
25194-3PS-PL-031
Appendix B Page 2 of 3
SHARE
SMARTPLANT REVIEW
FORMAL SUBDIRECTORY
zarom
\\lonsbr10<Server>\251
94\zarom
\drv\<unit name>\formal
zcppp
\\lonsbr10<Server>\251
94\zcppp
zcrud
\\lonsbr10<Server>\251
94\zcrud
\drv\<unit name>\formal
zfccc
\\lonsbr10<Server>\251
94\zfccc
\drv\<unit name>\formal
zfuel
\\lonsbr10<Server>\251
94\zfuel
\drv\<unit name>\formal
zmero
\\lonsbr10<Server>\251
94\zmero
\drv\<unit name>\formal
zoffs
\\lonsbr10<Server>\251
94\zoffs
\drv\<unit name>\formal
Zpru3
\\lonsbr10<Server>\251
94\zpru3
\drv\<unit name>\formal
zreft
\\lonsbr10<Server>\251
94\zreft
\drv\<unit name>\formal
zsulf
\\lonsbr10<Server>\251
94\zsulp
\drv\<unit name>\formal
zutil
\\lonsbr10<Server>\251
94\zutil
\drv\<unit name>\formal
\drv\<unit name>\formal
As the Servers are backed up daily the formal (30%, 60% and 90%) data will also be
archived along with rest of the files.
25194-3PS-PL-031
Appendix B Page 3 of 3
SHARE
SMARTPLANT REVIEW
ARCHIVE SUB-DIRECTORY
zarom
\\lonsbr10\25194\zarom
\drv\<unit name>\archive
zcppp
\\lonsbr10\25194\zcppp
\drv\<unit name>\archive
zcrud
\\lonsbr10\25194\zcrud
\drv\<unit name>\archive
zfccc
\\lonsbr10\25194\zfccc
\drv\<unit name>\archive
zfuel
\\lonsbr10\25194\zfuel
\drv\<unit name>\archive
zmero
\\lonsbr10\25194\zmero
\drv\<unit name>\archive
zoffs
\\lonsbr10\25194\zoffs
\drv\<unit name>\archive
Zpru3
\\lonsbr10\25194\zpru3
\drv\<unit name>\archive
zreft
\\lonsbr10\25194\zreft
\drv\<unit name>\archive
zsulf
\\lonsbr10\25194\zsulp
\drv\<unit name>\archive
zutil
\\lonsbr10\25194\zutil
\drv\<unit name>\archive
25194-3PS-PL-031
Appendix B Page 4 of 3
25194-3PS-PL-031
Appendix B Page 5 of 3
Appendix C
Complex SPR Co-ordinator Responsibility
C-1
The Project SPR Co-ordinator will be responsible for but not limited to the following: Provide EDS with files for archive to CD after a Formal reviewEnsure to copy the data
over the PDS server after formal review has been completed.
Point of contact for CD retrieval.
Training of new users of Design/Review.
Ensuring all disciplines have access to SPR terminals as required.
Report problem with the SmartPlant Review hardware and network to PAG
Creation of Formal SmartPlant Review sessions.
Creation and maintenance of Informal SmartPlant Review sessions.
File management and directory maintenance
Assist with Formal review
25194-3PS-PL-031
Appendix C Page 1 of 1