Professional Documents
Culture Documents
RU-V BALIKPAPAN
Doc. No. : 26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 1 / 67
AUTOMATION PLAN
004 27-Nov-20 Re-approved for Design Chen Weichen Huang Chaowei R.Goentoro
003 13-Jul-20 Re-approved for Design Chen Weichen Huang Chaowei Li Guohui
002 01-Jun-20 Re-approved for Design Chen Weichen Huang Chaowei Li Guohui
001 08-Feb-20 Re-approved for Design Chen Weichen Huang Chaowei Li Guohui
000 08-Jan-20 Approved for Design Chen Weichen Huang Chaowei Li Guohui
00A 10-Dec-19 Issued for Review Chen Weichen Huang Chaowei Li Guohui
Rev. Date Description Prepared By Reviewed By Approved By
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 2 / 67
REVISION LOG
001 08-Feb-10 21-78 AFES and Plaxis are not listed in the contract
TABLE OF CONTENT
1. PURPOSE ...................................................................................................................... 9
2. DEFINITION .................................................................................................................. 9
3. REFERENCES ............................................................................................................... 10
4. SOFTWAREVERSIONS ................................................................................................. 10
5. SMARTPLANT P&ID .................................................................................................... 13
5.1 Software versionand seed files ............................................................................. 13
5.2 Details of services used for the project ................................................................ 13
5.3 Oracledatabase setup ........................................................................................... 14
5.4 SPPID Setup .......................................................................................................... 14
5.5 Site restoration ..................................................................................................... 14
5.6 Plant restoration ................................................................................................... 14
5.7 Smart plant PID application association ............................................................... 15
5.8 Plant hierarchy structure (PBS)............................................................................. 15
5.9 SPPID execution plan ............................................................................................ 16
5.10 Naming conventions (ITEM TAGS) ........................................................................ 17
5.11 Reference data implementation plan ................................................................... 19
5.12 Creation of SPPID drawing ................................................................................... 24
5.13 Reference data management ............................................................................... 24
5.14 Backup .................................................................................................................. 25
5.15 Disaster recovery procedure ................................................................................ 25
5.16 Data maintenance procedure ............................................................................... 25
5.17 Final SPPID deliverables ........................................................................................ 26
6. SMARTPLANT 3D ........................................................................................................ 26
6.1 Software version and seed files ............................................................................ 26
6.2 Details of services used for the project ................................................................ 27
6.3 SQL Server database setup ................................................................................... 28
6.4 S3D setup .............................................................................................................. 28
6.5 Site database restoration ..................................................................................... 28
6.6 Catalog database restoration ............................................................................... 28
6.7 Model (PLANT) &report database restoration ..................................................... 29
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 6 / 69
6.8 Plant hierarchy and system setup for each task ................................................... 30
6.9 Working units ....................................................................................................... 31
6.10 Permission group .................................................................................................. 32
6.11 S3D modeling scope ............................................................................................. 33
6.12 Interface checking ................................................................................................ 34
6.13 Reference data management ............................................................................... 36
6.14 Process of managing construction phase changes ............................................... 36
6.15 Project database maintenance ............................................................................. 37
6.16 Project database integrity .................................................................................... 38
6.17 S3D backup ........................................................................................................... 40
7. SMARTPLANT INSTRUMENTATION ............................................................................. 40
7.1 Software version ................................................................................................... 40
7.2 Details of services used for the project ................................................................ 40
7.3 Oracle database setup .......................................................................................... 40
7.4 Roles and responsibilities ..................................................................................... 40
7.5 Info maker............................................................................................................. 42
7.6 SPI enhanced smartplant report generator.......................................................... 42
7.7 Import utility ......................................................................................................... 42
7.8 Overview of SPI database ..................................................................................... 42
7.9 Project deliverables .............................................................................................. 44
7.10 Plant hierarchy structure (PBS)............................................................................. 44
7.11 Naming conventions (ITEM TAGS) ........................................................................ 45
7.12 Instrument types and profiles .............................................................................. 47
7.13 Final documentation and deliverables ................................................................. 48
7.14 Backup and disaster recovery procedure ............................................................. 49
8. SMARTPLANT HANDOVER REQUIREMENT .................................................................. 49
8.1 Contractor information handover to owner ........................................................ 49
8.2 File& Sent to owner during EPC execution ........................................................... 50
8.3 Closeout handover................................................................................................ 50
8.4 Smartplant schematics handover requirement .................................................... 50
8.5 SmarttplantP&ID (SPPID) handover requirement ................................................ 50
8.6 Smartplant instrumentation (INTOOLS/SPI) handover requirement ................... 52
8.7 Smartplant3D (S3D) modeling handover requirement ........................................ 53
8.8 VUE files ................................................................................................................ 55
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 7 / 67
LIST OF FIGURES
Figure 5.12-1.Create Drawing ..................................................................................................... 24
LIST OF TABLES
Table 2-1.AbbreviationsandDefinitions ....................................................................................... 9
1 PURPOSE
The overall objective of the Automation Plan document is to ensure that the CONTRACTOR provides
OWNER with information in the form of data required to effectively manage its assets and business
together with the files and data required for oversight and virtualization of the design development
during the EPC phase of the project by CONTRACTOR. the description and use of the calculation and
analysis software used in the detailed design process are listed. These are requirements over and above
the deliverable’s requirements prescribed elsewhere OWNER has adopted the smartplant suite of
software for Process and plant design from HEXAGON© which currently include engineering authoring
tools: SPPID, S3D, SPRD, SPI. Also, SPR will be used as the 3D model review tool for the 3D model.
To better Communicate design intent, interface with other contractor and COMPANY, engineering
design work shall be developed using Smartplant suite of model and database software to maximum
extent.
2 DEFINITION
The following terms, acronyms, abbreviations, etc., shall have as used here shall have the meaning as
shown in Table 2-1 below:
Table2-1: Abbreviations and Definitions
3 REFERENCES
Table3-1: References
4 SOFTWARE VERSIONS
Engineering software to be used in this project is as follows:
Table 4-1: Software versions
1 Offshore
2 Process
3 Piping
5 Mechanical
6 Instrument
7 Electrical
10 Office Software
12 HVAC
13 Database Software
14 Model Review
15 Operating System
17. CivilandStructure
5 SMARTPLANT P&ID
5.1 Software version and seed files
Application Tool: SPPID Version 2014R1
Application Tool: SPEM Version 2014R2
Database Tool: Oracle 11g R2
Receive owner's seed files for project restoration
SPPID seed files as follows
⚫ P&ID Reference Data
⚫ Plant Structure Backup
⚫ Border Template
⚫ ItemTagFormat.xml
⚫ Itemtag.dll
⚫ Report Files
⚫ Plant.ddt Files
⚫ SPPID.ddt Files
SERVER/
S. No Operating System Database SPPID Version
LOCATION
Database
Windows Server
1 Server Oracle 11g R2
2008 R2 64-bit
(Indonesia)
SPLM Server
2
(Indonesia)
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 14 / 67
SPPID
Application Version 2014R1
Windows Server
3 Server Oracle 11g R2
2008 R2 64-bit SPEM Version
(Indonesia)
2014R2
ELECTRICAL DISTRIBUTION
LWLWR01LF001 430
FACILITIES
TELECOMMUNICATIONS, CCTV,
LWLWR01LF001 436
SYSTEM
TEMPORARY CONSTRUCTION
LWLWR01LF001 471
FACILITIES LAWE LAWE
⚫ Software Versions
⚫ Roles & Responsibilities of Key SPPID Personnel (Administrators, Lead designers, users)
⚫ Setup information
⚫ Details of all servers used for the project
⚫ Plant Hierarchy (PBS) structure
⚫ Reference Data implementation plan
⚫ Instructions for Designers for use of correct Symbols, Labels to be used
⚫ Instructions for resolving Inconsistencies in SPPID drawings
⚫ Setup for Reports outputs
⚫ Backup & Disaster recovery procedure
⚫ Data maintenance procedure (such as Database constraint checks, database maintenance,
Duplicate Items check)
5.10 Naming conventions (ITEM TAGS)
Equipment
Whereas:
⚫ AAA Indicates the WBS Facilities Code.
⚫ BBB Indicates the Equipment Code.
⚫ CC Indicates the Sequence Number. The SequenceNumber shall start at 01 and
end at 99. All the Major Equipment falling under same Equipment Designation shall have a unique
serial number so that there is no ambiguity.
⚫ A-Z Indicates the Suffix for standby / Redundant Equipment.
For example: 431-P-001A
Pipe Run
SEQUENCE NUMBER
WBS FACILITIES CODE
FLUID ABBREVIATION
Whereas:
⚫ AAA Indicates the fluid abbreviation.
⚫ BBB Indicates the WBS facilities code.
⚫ CCC Indicates the Sequence number. The sequence number shall start at 001
and end at 999.
For example: P-420-001
Valve
P Process Fluid
420 WBS Facilities Code (Tankage Unit)
001 Sequence Number
AAA BBB CCC
SEQUENCE NUMBER
VALVE CODE
Whereas:
Instrument
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 19 / 67
Whereas:
⚫ AAA Indicates the WBS facilities code.
⚫ BBBB Indicates the Instrument Code.
⚫ CCC Indicates the Sequence Number. The Sequence number shall start at 001 and end at
999. All the major Equipment falling under same Equipment Designation shall have a unique serial
number so that there is no ambiguity.
⚫ A-Z Indicates the Suffix for standby / redundant Equipment.
For Example: 420-PG-001A
Equipment Code
Equipment Name
LAWE-LAWE Terminal
AH Analyzer House
AS Anchor Support
D Pressure Vessels
DA Deaerator
E Exchanger, Reboilers
EA Air Fin Coolers
F Fired Heater, Furnace, Air Preheater
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 20 / 67
CAUSTIC B
CATALYST CAT
CHLORINE CL
CHEMICALS CH K
CHEMICAL SEWER CS
PROCESS
AMMONIA NH
HYDROGEN H
AMINE (OR DEA) MEA
CRUDE OIL P
PROCESS FLUID P P1
SULFURIC ACID SA
AUXILIARY COOLING WATER
ACWR
RETURN
AUXILIARY COOUNG WATER
ACWS
WATER
SUPPLY
BLOWDOWN WATER BDW
BOILER FEED WATER BFW
BALLAST WATER BLW
BOILER WATER BW
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 22 / 67
PLANT AIR PA
DRY AIR DA
PURGE NITROGEN PN
DRIED PLANT AIR DPA
FUEL GAS FG
FUELS
OILY SLOP OS
SEAL OIL SO
HIGH PRESSURE STEAM HS
HIGH HIGH PRESSURE STEAM HHS
LOW PRESSURE STEAM LS
STEAM
STEAM S
CHEMICAL DRAIN CD
CAUSTIC DRAIN CSD
HEAVY AND LIGHTHYDROCARBON
D
DRAIN (CLOSED DRAIN)
Rule Manager
At the start of the project default Intergraph rule set will be deployed. Further for any customization if
required, shall be done with prior approval from the company.
Catalog Manager
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 24 / 67
The folder structure has been kept as delivered from client or Intergraph. The symbols provided by the
company have been placed according to the instructions received.
Option Manager
The Option Manager controls the appearance of a SPPID drawing by selecting the Colours, line styles,
gapping styles and heat tracing styles. This also defines the location of symbols, rules, Template files.
Filter Manager
Filters have been kept as delivered from Intergraph.
Format Manager
Formats have been kept as delivered from Intergraph.
5.12 Creation of SPPID drawing
Creation of SPPID Drawings in Drawing Manager of Intergraph SmartPlant P&ID is as per following:
Figure 5.12-1.CreateDrawings
c) OWNER Application Specialist shall review the request and provide approval or alternative feedback.
OWNER engineering specialists (e.g. process, piping, instrumentation or electrical engineers) will be
consulted for approval where required. Consultation shall be recorded and updated in change request
log file.
d) CONTRACTOR SPPID Administrator (as directed by the OWNER Application Specialist) shall update
SPPID application reference data to reflect approved change requests only.
e) All the additional reference data customization shall be created with a prefix as “LAWE_” after the
prior approval from OWNER.
5.14 Backup
A daily backup of the plant will be scheduled. Drawing versioning will be scheduled by SPPID
administrator in order to fix a bugged drawing. Backup operations are performed during idle time, not
during designer operations
5.15 Disaster recovery procedure
Full plant backup tapes will be maintained at least weekly. Apart from that we have the procedure to
enable trace logs for oracle database with help of this we will be able to do point in time recovery.
5.16 Data maintenance procedure
The following activities must be performed by SPPID administrator on weekly basis:
⚫ Ensure that all drawings are up to date
⚫ Recreate drawings
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 26 / 67
⚫ OPC Reports
⚫ Resolving all inconsistencies
⚫ Run duplicate Item Tag report and report it to designers
⚫ Clean all database constraints
⚫ Delete orphan model items (using DelOrpModItems.dll)
⚫ Verify symbol for every new symbol created
5.17 Final SPPID deliverables
CONTRACTOR shall ensure that SPPID data does not have any data inconsistencies before final delivery.
CONTRACTOR shall adhere to the following guidelines for final SPPID deliverables:
1) SPPID data shall be as-built.
2) All drawings and reports within or extracted, using SPPID, shall be updated with as-built information.
3) CONTRACTOR shall use the Smart Plant P&ID “Re-Create P&ID from Database” functionality for each
drawing before final handover to OWNER.
4) CONTRACTOR shall ensure that all deliverables, submitted to OWNER can be extracted from the
restored backups.
5) CONTRACTOR shall upgrade SPPID data to OWNER approved version.
6) CONTRACTOR shall be responsible to eliminate any inconsistencies in the upgrade process to the
SPPID version approved by the OWNER.
7) CONTRACTOR shall submit a database consistency and health check report before and after the
upgrade.
8) CONTRACTOR shall take responsibility, to validate the data, after upgrade, to the SPPID version
approved by the OWNER. Any inconsistency noticed during the upgrade, shall be documented and
provided to OWNER.
9) CONTRACTOR shall facilitate the OWNER in uploading the data set at OWNER’s site. CONTRACTOR
shall resolve any issues, which may arise when OWNER is evaluating the data, until the ‘Provisional Final
Acceptance Certification’ is obtained.
10) CONTRACTOR shall provide all documents concerned with SPPID, in hardcopies, PDF and native
editable electronic formats (MS-Word, MS Excel, etc.).
11) CONTRACTOR shall provide a report on all software architecture changes, if any in SPPID version
change.
6 SMARTPLANT 3D
6.1 Software version and seed files
Following software’s and their modules shall be used for the built-up of 3D Model.
Application Tool: S3D Version 2016
Database Tool: Microsoft SQL Server 2014
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 27 / 67
SPLM Server
2
(Indonesia)
Interference
Windows Server Microsoft SQL S3D
3 Checking Server
2012 R2 64-bit Server 2014 Version 2016
(Indonesia)
Figure 6.9-1.WorkingUnits
6.10 Permission group
Following permission groups will be created and access rights can be given to these permission groups.
Based on access rights, S3D user can edit or modify or create an item in S3D environment. Every
professional designer has the write permission for that specialty, and can create, modify, and delete
models. Administrators have full control of each permission group.
The Permission assignment is given as per the following table:
Engineering Permission-Group
S3D System Name Access Rights
Discipline Name
⚫ It is required that the contractor ensures that the delivered data are not corrupted and/or contain
inconsistencies before delivery. As a minimum, the following checks and cleanup shall be
performed:
⚫ General:
⚫ Temporary files and directories shall be removed prior to delivery,
⚫ SmartPlant 3D Database Consistency Check report should be run without
⚫ reporting
⚫ Inconsistencies.
⚫ The SmartPlant 3D To-Do-List Shall be empty
6.12 Interface checking
Interference management of clashes will be the responsibility of the EPC Contractor to ensure that all
interference checks are planned and executed to meet project quality targets. The setup and execution
of interference checks for each discipline will be carried out by out of box Intergraph delivered
interference check rules.
The responsibility of interference will be assigned to the respective disciplines and discipline lead
engineer will be responsible to resolve the interference.
In S3D we are having below mentioned options for clash checking the detail description of the types are
listed below.
Figure 6.12-1.InterferenceCheckingSettings1
Severe: Between 2 simple physical or required objects like structural member and pipe
Optional: Between 2 simple physical or required objects like structural member and structural part
Clearance: Distance between 2 simple physical or required objects
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 35 / 67
With respect to the 3D display aspect of the modeled objects we can select the required objects for
interference checking and apply the rules accordingly as per OWNER requirement.
Figure 6.12-2.InterferenceCheckingSettings2
EPC Contractor S3D Administrator will configure and start the interference server which is also known
as database detects with Intergraph delivered “No Clearance Rule”. After starting database detects S3D
Administrator will be able to have the real time status of the interference checking process by following
display window. After finishing the process EPC Contractor S3D Administrator will extract the detailed
report for Interference/clashes from S3D.
EPC Contractor will submit clash check reports to OWNER prior to all formal model reviews.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 36 / 67
Figure 6.12-3.InterferenceCheckingSettings3
At the end of the project EPC Contractor will deliver clash free model when the S3D project will send to
OWNER ownership.
6.13 Reference data management
S3D Reference data includes reference data used for all disciplines. These include piping specifications
& catalog, equipment catalog, cable tray specifications, structural sections, VB symbols etc. All
customizations required for various rules.
Drawings & reports also come under Reference data. These include view styles, drawing templates, rules
for dimensions, rules for labels etc.
EPC Contractor will customize S3D catalog to include all sizes for all piping components such that it
matches the requirement for the project phase for piping material specifications.
EPC Contractor will retain and backup all bulkload excel files, source codes for symbols, rules, support
assemblies etc. for handover to OWNER.
All changes/customization (additions, modifications and deletions) of S3D shall be recorded in an excel
workbook with separate worksheet/tab for each type, for submission to OWNER.
6.14 Process of managing construction phase changes
As per red mark-up drawing during construction, 3D model will be updated. Same changes will be
reflected in As built mark-up drawing.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 37 / 67
Figure 6.15-1.DatabaseMaintenance1
No optimization - Indicates that you do not want to optimize any database tables. This option is selected
by default and the grid control is blank. Selecting one of the other grid controls will populate the grid
with fragmentation information.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 38 / 67
Figure 6.15-2.DatabaseMaintenance2
Rebuild selected indexes - Indicates that you want to rebuild the indexes on the database tables for the
selected tables in the grid. The software automatically determines a fill factor for the database tables.
This fill factor is dependent on the activity in the database. When a model is very dynamic, the fill factor
will be low, but when few modifications occur in the model (for example, in a reference or "as-build"
model), the fill factor will be high. Similarly, during catalog creation (for example, during heavy bulkload
periods), the fill factor will be low, but when the catalog becomes stabilized and used in production, the
fill factor will be high.
If this option is selected but no tables are checked in the associated grid, nothing happens.
Reorganize selected indexes - Indicates that you want to reorganize the indexes on the database tables
for the selected tables in the grid.
If this option is selected but no tables are checked in the associated grid, nothing happens.
6.16 Project database integrity
The Database > Integrity command is available in the Project Management environment. For more
information on database integrity, see the Database Integrity Guide.
1. Select a Plant, catalog, or site in the Project Management tree view. Your selection determines the
databases available for checking database integrity: select a Plant if you want to check all of the
databases associated with that Plant; select a catalog if you want to check the Catalog database only;
select a site to check the Site database only.
2. Database > Integrity. The Database Integrity dialog box appears.
3. Check the database you want to command the process. You can check more than one database.
4. Select Basic check or Full check.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 39 / 67
Figure 6.16-1.CheckDataConsistency
5. Click Run to start the command. Processing displays in the Checking window.
6. When the command is done and processing the selected databases, click Exit to dismiss the dialog
box.
7. Go to the Once Database Integrity has finished, next action is to clean the database for issues that
were found. The Clean Database command is not yet integrated in the GUI environment; you will need
to use a special custom command with progID S3DCleanDatabaseCmd.CCheckObj to perform clean
procedure. This command needs to be executed from an S3D session as there may be objects that need
to be modified in the graphical environment.
Common task to use the Tools > Run Reports command and generate reports of the records generated
by the Database > Integrity command.
7 SMARTPLANT INSTRUMENTATION
7.1 Software version
Application Tool: SPI Version 2016 SP1
Database Tool: Oracle 11g or 12 c
7.2 Details of services used for the project
SERVER/
S.No Operating System Database SPI Version
LOCATION
Database
Windows Server Oracle 11g or
1 Server
2012 R2 64-bit 12 c
(Indonesia)
SPLM Server
2
(Indonesia)
Application SPI
Windows Server Oracle 11g or
3 Server Version 2016
2012 R2 64-bit 12 c
(Indonesia) SP1
The project SPI Administrator shall co-ordinate & executes all SPI related administrative tasks and
communicates issues and updates to SPI users on the project across locations.
2) System Administrator
SPI System Administrator is responsible for handling the following administrative tasks:
⚫ Identify database setup parameters and liaise with IT for its setup. These parameters must be
uniform across all project offices to allow OWNER applications and other interfaces to connect
seamlessly.
⚫ Project Initialization
⚫ Database Maintenance
⚫ Creation of Users And departments
⚫ Assign Domain Administrator
⚫ Manage the SPLM License server
⚫ Schedule backup & archival
⚫ Database Tuning and its maintenance
⚫ Coordination with IT for software update and service pack implementation
3) Domain Administrator
Domain Administrator is responsible for handling the following administrative task:
⚫ Review and implementation of OWNER SPI requirements for the software and database for the
application version, SPE interface etc.
⚫ Develop project execution plan, and associated SPI procedures
⚫ Identify Project Deliverables and setup typical for project approval
⚫ PAU definition as per project requirement and in line with other SmartPlant tools
⚫ Define Naming Conventions
⚫ Access Right Managements
⚫ Customize UDFs/UDTs
⚫ Customize/Maintain SPI Default Tables like Instruments types, IO Types etc.
⚫ Locking/unlocking of the database activities and entities.
⚫ database Maintenance
⚫ Preference management
⚫ Report Management
⚫ Configuration of SPI modules like Index, Specification, Process Data, Hook-up, wiring etc. to suit
user &OWNER requirements
⚫ Customize Reports and Datasheets using Infomaker
⚫ Import of external databases using import module
⚫ Title block customization using Infomaker and Enhanced report utility.
⚫ Project specific customization based on OWNER or associated requirements
⚫ Communicate updates that are to be executed on SPI master seed database
⚫ Manage technical queries, change requests and associated documentation with OWNER.
4) Super User
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 42 / 67
Domain Administrator shall identify a Super user at all work locations. Super user shall havemaximum
working level privileges including import utility; however, he will not perform any
Administrative task. Super user shall handle day to day user queries and interface with Domain
administrators.
5) Users
The users shall be categorized based on function and shall work with SPI Index, Specification, Browser,
Wiring, Hook-Up & Loop drawing Modules to generate SPI deliverable as per project requirements.
7.5 Info maker
Info maker Version 12.5 Build (2511) shall be used to generate and/or modify SPI instrument
specification forms, reports, templates, etc.
7.6 SPI enhanced smartplant report generator
The Enhanced Report Utility shall be used to generate graphical reports for items such as loops, cables
and terminal strips. The Enhanced Report Utility is compatible with other commercial software packages
and the generated enhanced reports can be saved in formats that are compatible with Smart Sketch,
AutoCAD or MicroStation. This utility shall have the same version as that of SPI application.
7.7 Import utility
This utility provides the necessary means to import data from other file formats such as dBase files,
Microsoft excel files.
7.8 Overview of SPI database
SPI, Version 2016is a Windows based integrated Instrumentation Engineering and Design Application
which uses an Oracle Database. It covers most of the aspects of Instrumentation Engineering design.
The application is broken down into various modules that reflect different stages of instrumentation
work. These modules include administration, Import Utility, instrumentation Index, Process Data,
Instrument Specification, Wiring, Hook-up (Installation Details) and Loop Diagram, etc.
1) Administration Module
The Administration Module used by the System and Project Administrator to set the Project conventions
(e.g. Plant/Area/Unit hierarchy, Loop and Tag number structure) and to grant access (read only, write,
etc.) to users (e.g. Engineers and Designers) for accessing the various SPI modules. SPI is supplied with
numerous instrument pre-defined fields. User Defined Fields (UDF) and User Defined Tables (UDT) can
be defined where additional field are required to enter specific data / functional requirements, which
are not normally covered by the SPI Database default fields. UDFs and UDTs are custom fields and tables
used to store user-defined information for an instrument tag.
2) Instrument Index Module
The Instrument Index Module allows for the creation, modification and maintenance of a
comprehensive database that contains all instrumentation components required for a project. The
module offers tools for adding, editing, duplicating and deleting individual instrument tags or loops.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 43 / 67
Instrument types and their profile provide the facility for quick, accurate, and standardized data entry.
Data such as Manufacturer & Model, P&ID drawing numbers, line numbers, locations, I/O types and
equipment numbers are organized in supporting tables. Other functions provided by the Instrument
Index Module include item - oriented (Tag, Loop, etc.) filtered, sorted, and customizable database
viewing options, report generation in various formats, attaching remarks to items, creating specific
summaries, and viewing and managing history. Software alarms shall be provided on analogue signals,
using values entered in the various fields.
3) Data Change
During the course of the project, data will get update/modified as design develops, these
updates/modifications shall be communicated to OWNER as per defined project procedures for OWNER
review/approval. In general data can change in six ways, addition, deletion, expansion, reduction,
alteration & rename. It is probable that proprietary instrument database changes system will have
operating procedure to monitor and record database changes.
4) Process Data Module
This module is used for the entry of process data, initially for the line and later consequently for the
individual instrument tags. It is also possible to enter process data into process fields through
Instruments Modules.
5) Specification Module
Instrument Specification (Data) Sheets are generated by using SPI Instrument Specification Forms. These
forms originate as PSR files.
6) Calculation Module
This module can be used for preliminary sizing of control valves, Pressure safety valves, and Orifice plates,
which uses data from the Process data and Instrumentation index modules. This module employs
calculation method based on international standards such as ISA, ANSI, API, ISO and IEC. The final
calculation shall be performed using the Vendor sizing programs or other project approved methods.
7) Browser Module
The Browser module provides a wide-angle view of instrument index data and allows browsing through
and modifying it from a single location in SPI. The core of the Browser module, Browser manager which
contains a number of predefined Browser categorized by data type. Each browser is associated with a
particular SPI module but in some cases, it is possible to present data from several different modules in
a single browser view. User/Administrator can define a number of different Browser views for each
Browser to organize data according to different requirements. Each browser view will have its own style
settings, sorting sequence, and filter to present instrument index data in the most efficient and
informative manner. The Browser view style setting determine which columns and entities will be
displayed. The sorting sequence organizes the selected fields in particular order and the filter lets you
display the data filtered according to the condition. However, it is advisable to create personal views
and default view shall not be altered.
8) Wiring Module
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 44 / 67
This module is used for the creation of instrument cable, Junction Box and Marshalling Cabinet
termination details and perform the wiring activities. Reference database for cables, junction boxes and
termination details are created within SPI database. Reference database is used to generate the cable
lists and the cable connection details. The module is used to generate cable schedule using pre-
customized PSR format. The Junction Box and Marshalling rack/cabinet Interconnection diagram shall
be generated from SPI with Default Delivered Panel - Strip with adjacent connection report with project
approved title block.
9) Loop Module
Instrument Loop Drawing are generated using ESL by fetching data from Index Modules (IO list related
information & ICSS Database) and wiring module (Instrument wiring details). The required customization.
Loop templates, borders, symbols, layouts, etc., shall be submitted to OWNER for approval before
implementation.
10) Hook-Ups-Module
SPI Hook-up- Module shall be used to create the Hook-up/installation details for mounting and
connecting the instruments. Below is the listing of different Hook-up/installation types.
⚫ Pneumatic Hook-up type (instrument air distribution, valve air supply, etc.)
⚫ Process Hook-up Type (impulse tubing line, etc.)
⚫ Installation Hook-up type (Instrumentation Fabrication Drawings)
This module takes care of important managerial tasks quickly and easily such as assigning instrument
types to hook-up type & instrument to hook-up.
The hook-up library will be generated to cover the item number, description and material details and
will be made as default for the project. The different hook-up typical shall be developed and assigned
against the respective tag to generate the detailed hook-up and installation MTO.
7.9 Project deliverables
The following deliverables, but are not limited to, shall be generated using SmartPlant Instrumentation.
⚫ Instrument index
⚫ Input/output lists
⚫ Instrument data sheets
⚫ Instrument sizing calculations
⚫ Loop diagrams
⚫ Hook-ups & Installationdrawings
7.10 Plant hierarchy structure (PBS)
Project uses the Plant-Area-Unit (P-A-U) hierarchy system. A Plant Breakdown Structure (PBS) is a
classified hierarchy with superiors (or roots) and subordinates (or dependents). For example, a PBS for
organizing plant data might be plant/area/unit. The CONTRACTOR will follow the Plant break down (P-
A-U) structure as defined by OWNER.
Plant Name – ***
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 45 / 67
ELECTRICAL DISTRIBUTION
LWLWR01LF001 430
FACILITIES
TELECOMMUNICATIONS, CCTV,
LWLWR01LF001 436
SYSTEM
TEMPORARY CONSTRUCTION
LWLWR01LF001 471
FACILITIES LAWE LAWE
SEQUENCE NUMBER+SUFFIX
INSTRUMENT TYPE
Whereas:
⚫ AAA Indicates the WBS Facilities Code.
⚫ BBBBB Indicates the Instrument Type.
⚫ CCCCC Indicates the Sequence Number and the Suffix for standby / Redundant
Equipment. The SequenceNumber shall start at 001 and end at 999. All the instrumentsnot in the
same loop shall have a unique serial number so that there is no ambiguity.
For example: 431-PT-001A
SEQUENCE NUMBER+SUFFIX
LOOP MEASURED VARIABLE
Whereas:
⚫ AAA Indicates the WBS Facilities Code.
⚫ BBB Indicates the Loop Measured Variable.
⚫ CCCCC Indicates the Sequence number and the Suffix for standby / Redundant
Equipment. The sequence number shall start at 001 and end at 999.
For example: 420-P-001A
may arise when OWNER is evaluating the data, until the Provisional/Final Acceptance Certification' is
obtained.
7.14 Backup and disaster recovery procedure
a) Backup
Generally, CONTRACTOR take daily backup in application machine and weekly on database server from
database server, CONTRACTOR will take copy of this backup to centralized database server and as well
as use to keep weekly backup file on hard disk drive.
b) Disaster Recovery Procedure
In any disaster condition CONTRACTOR shall avail the latest backup from the secured centralized
database server. As these backups are stored on daily basis, the envisaged loss of data will be limited to
one working day. The restored backup will be updated and will be available the SPI / Project users
The Contractor shall validate the information prior to handover to OWNER. Handover shall be on a
regular basis during Project execution. The handover information shall be subjected to OWNER / third
party validation. The Contractor shall resolve any anomalies resulting from the validation exercise,
All Documents, Drawings and Engineering Data shall be delivered by the Contractor in the specified
electronic formats to facilitate import to and population of the OWNER systems.
The information will be required at various stages through the Project, to be agreed by OWNER and
Contractor, to test the transfer and validation processes prior to final handover.
The Contractor shall develop an Information Handover Procedure for review and agreement by the
OWNER that will include but is not limited to, drawing / document and metadata handover, engineering
and procurement information, databases, configuration files, analytical/calculation models, Operations
and Maintenance information, etc. that will facilitate the Operation, Maintenance and Modification of
the facility into the future.
8.2 File& Sent to owner during EPC execution
⚫ Regular handover of SmartPlant Review mode review .Vue files to OWNER of CONTRACTOR scope
including, if applicable, vendor and 3rd party models that make up the full CONTRACTOR scope
⚫ SmartPlant model and databases handover to OWNER (S3D, SPPID, SPI)
⚫ Data handovers to OWNER via MS EXCEL spreadsheet of tag and other registers for data
warehousing purposes.
8.3 Closeout handover
CONTRACTOR will issue a well-defined project automation closeout procedure in accordance with the
project schedule. The purpose of this procedure is to support the safe and smooth archival and turnover
of all project related data.
8.4 Smartplant schematics handover requirement
Intelligent Systems shall be: used for the creation & management of P&ID, Electrical,Communications
and Instrument design. Intelligent Systems differ from other Engineering Systems in that the information
is developed, verified, approved and maintained entirely within a database, generally without any wet
copy approval. These systems provide an opportunity to significantly reduce the volume and necessity
for hardcopy output
8.5 SmarttplantP&ID (SPPID) handover requirement
SmartPlant P&ID is an intelligent P&ID schematic generation application; it is interfaced to other
SmartPlant applications and can facilitate the data integration, alignment and clash/data error detection
of mismatches between the 3D model, the Instrumentation and the P&ID.
⚫ Deliverables
The contractor is required to remove all temporary drawings, test drawings, test symbols and assemblies,
temporary filters, reports, etc. from the SmartPlant P&ID data before delivery.
The contractor is required to use the SmartPlant P&ID; Re-Create P&ID from Database” functionality
before final Q&C and delivery.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 51 / 67
The contractor is required to ensure that the delivered SmartPlant P&ID data is free of any database
exceptions and orphan entries. The contractor is required to run all appropriate utilities as delivered
with the software for identifying and resolving database issues.
The contractor is required to provide any modified source code for alt dlls that were created for the
SmartPlant P&ID project and must highlight the modifications vis-a-vis delivered code. This code is to be
sufficiently documented such that OWNERS can understand what the function is required to do. It
should be understood from the start of the project that the OWNER owns all code created for the project.
It is a strict requirement that all code be issued to the OWNER to enable the recompilation of the binary
dlls at a future date when the SmartPlant P&ID software is upgraded.
include
a. Symbol libraries
b. Report Templates
c. Itemtag.dll
1 Application backup
d. ltemtagformat.xml
programs
g. Plant backup
It is required that the contractor remove all test data, test CAD blocks, temporary browser views,
temporary reports, etc., from the SmartPIant Instrumentation database and system directories before
delivery.
⚫ The contractor is required to deliver the SmartPlant Instrumentation database in a backup format.
The contractor is required to run the appropriate utilities as delivered with SmartPlant
Instrumentation for identifying and resolving database issues such as "CheckDB, the contractor is
to provide the log file from this utility showing that there are no errors. It is thecontractor's
responsibility to fix such errors.
⚫ The following will be provided:
⚫ CAD Blocks, symbols, border templates, title block PSRs
⚫ Customized PSR files for reports and datasheet templates
⚫ Document specifying approved deviations from standard specification the: above electronic
deliverables will be made available on the DVD media and includes an index to all that is contained
on the DVD.
⚫ EPC Contractor will as-built the SPI Database, drawings & reports and upgrade data to OWNER
approved SPI version before final handover.
No Deliverable from Contractor Remarks
a. CAD blocks
b. PSR files
If a new set of catalogs and specifications are to be developed for handover the Contractor must validate
those against the 3D model. The integrity of the 3D model must be assured.
⚫ 3D Data Files
the Contractor shall provide, at handover, the final project deliverables from the SmartPlant 3D (S3D)
application:
⚫ Complete SmartPlant 3D (S3D) Project Backup preformed from the SmartPlant 3D (S3D) project
management environment
Complete backup of project “Symbols’ share including complete backupof the directory structures for
drawings and reports created from SmartPIant 3D (S3D)
This includes but is not limited to:
⚫ Customized / added symbol definitions
⚫ Symbol executables (dll files)
⚫ Symbol source codes
⚫ Solid edge files
⚫ SAT files
⚫ Symbol 2D files
⚫ Drawing border Files
⚫ Drawing View Style definitions
⚫ Drawing Label definitions
⚫ Final extracted Isometric Drawings
⚫ Final Orthographic Drawings
⚫ All Reports (in MS Excel format)
Secondary Archive:
⚫ Zip file ORACLE server database backup files for site, Site Schema, Plant Model, Catalog, and
Catalog Schema
⚫ All MS Excel Catalog Bulkload file for all disciples. It is mandatory that these files reflect 100
percent of the Catalog database (e.g. such the entire Catalog contents can be recreated by bulk
loading these files),
The following reportsare required to be submitted:
⚫ Final IFG (Interference Check Report) Report
⚫ Final Database Consistency Check Report
⚫ Complete Catalog Verification Report
⚫ Final Project To-Do-List Report
⚫ Line List Report
Data Checks and Cleanup
It is required that the contractor ensures that the delivered data are not corrupted and/or contain
inconsistencies before delivery. As a minimum, the following checks and cleanup shall be performed:
⚫ General:
⚫ Temporary files and directories shall be removed prior to delivery,
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 55 / 67
e. SAT files
f. Symbol 2D files
9 INFORMATION EXCHANGE
9.1 Process
A data handover process is required to provide a mechanism for meaningful information change history
Delivery will be a combination of native SmartPlant application databases, individual files, engineering
list and other formats that may be applicable to the project. These deliverables may also establish the
relationship of deliverables with the metadata (tag, system model, manufacturer, etc.) where applicable.
9.2 Frequency
Timetable and frequency of the transfers
Discipline Deliverable Software Duration/ Frequency
Application/For Start/Finish
Engineering
SPM Buoy Body Stress Calculations Ansys or other
One time
Design Report similar FE Tools
Completion
Completion
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 57 / 67
Engineering
Structural Design and Sacs or other similar
PLEM Design One time
Stress analysis FE Tools
11 3D MODEL CONTENT
The following list itemizes piping commodities and other features that are to be depicted in the
completed 3D model for model review and interfacing purposes and will include:
⚫ Plant Equipment-vessels, tanks, pumps, exchangers etc.
⚫ All valve& larger piping
⚫ Vendor supplied piping where vendor has utilized a 3D model of S3D compatible format
⚫ All in-line piping items including piping specialty items and instruments
⚫ Insulation (all remaining)
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 59 / 67
13 STAAD.PRO
STAAD.Pro is one of the most widely used structural analysis and design software products worldwide.
It supports over 90 international steel, concrete, timber & aluminum design codes.
STAAD.Pro can make use of various forms of analysis from the traditional static analysis to more recent
analysis methods like p-delta analysis, geometric non-linear analysis, Pushover analysis (Static-Non-
Linear Analysis) or a buckling analysis. It can also make use of various forms of dynamic analysis methods
from time history analysis to response spectrum analysis. The response spectrum analysis feature is
supported for both users defined spectra as well as a number of international standard specified spectra.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 60 / 67
MAJOR FEATURES
1) Configure Requirement
The current version of staad pro software required the minimum following system configuration.
Windows system Win 10 64-bit Enterprise
CPU 2.6GHz, DDR 2G.
Analysis model files can be created on the customer computer as per the steps of given guide. The
Database Character set can be defined by engineer, SI unit and International standard can be set as
default.
2) Structural analysis
Engineer used Staad Pro for various type of structural analysis, including concrete structure and steel
structure. For the current project, pump shelter, pipe rack, substation building will be performed
analysis to check the serviceability.
3) Code Check
Staad Pro contained different countries’ design code and can assistant engineer to finish the structural
design. AISC 360-10 are used for steel structural design, ACI 318-14 are used for concrete structural
design, ASCE 7-10 are used for load and load combination determined, the seismic can be considered
into design as well based on the code.
4) Worldwide usage
Staad Pro can be used for worldwide range as per the rule of Bentley Company. It is an online authorized
permission, the engineers of CPP can use staad pro at both China and Indonesia in same time, and the
staad model can be checked by different engineer easily for its small size.
5) Version History
Staad Pro to retain the version history of the edits made to the document, various version of the
same model file can be storage consecutive by system and compared anytime; previous versions can be
restored if an incorrect edit has been made to the item.
14 AFES
AFES is software which use commond practice for foundation design analysis, and also in this software
can spare more time during detail desain because the result is until the reinforcement requirement
analysis.
15 PLAXIS
Regarding the big foundation design especially tank foundation, contractor will use PLAXIS for
makesure the actual respons the soil due to load from above of foundation.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 61 / 67
16 OFFSHORE SOFTWARE
16.1 AUTOPIPE
AUTOPIPE is a stand-alone computer aided engineering (CAE) program for calculation of piping stresses,
flange analysis, pipe support design, and equipment nozzle loading analysis under static and dynamic
loading conditions.
Due to the pipeline installation and operation process, there will be a variety of stress on the pipeline.
The impulse pressure at the pump equipment port, the internal stress during the strong installation of
the pipeline, the pressure caused by the change of the medium temperature, the force exerted by the
valve bracket on the valve, etc., all kinds of forces will produce corresponding deformation displacement
in the pipeline. In order to find displacement and deformation in time, AUTOPIPE is used for stress
analysis of pipeline expansion spool in this project.
Expansion spool analysis
Firstly, according to the drawing of expansion spool, the 3D model is established. Then the attributes
are given. Taking unloading line as an example, the diameter and wall thickness of the pipeline need to
be modified. The load is then applied which will be provide by the expansion calculation. Finally, the
software will analyze the stress of the expansion spool and output the calculation results in the form of
text or chart. Moreover, the expansion spool cannot produce large deformation and displacement.
16.2 ORCAFLEX
OrcaFlex is a marine dynamics program developed by Orcina for static and dynamic analysis ofa wide
range of offshore systems, including all types of marine risers (rigid and flexible), global analysis,
moorings, installation and towed systems.OrcaFlex provides fast and accurate analysis of catenary
systems such as flexible risers and umbilical cables under wave and current loads and externally imposed
motions.
Orcaflex provides flexible finite element models, mainly including pipeline model, A& R winch model,
pipe laying ship model, seabed model, etc. In this project, orcaflex is mainly used for dynamic installation
analysis during pipe laying.
Main Work Finished
1. Environmental data setting
The environmental loads modeled in ORCAFLEX include SEA, SEABED, WIND, WAVES, CURRENT. All this
data should be correctly input according to the investigation report. In this way, the ocean situation can
be accurately simulated.
2. Modeling
According to the specification of pipe laying barge, the ship model is established. Then add other
parameters, including tension, lay radius, lay water depth, outer diameter of pipe, etc. These parameters
will directly affect the quality and safety of pipe laying.
3. Result
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 62 / 67
Orcaflex automatically performs static and dynamic analysis, and outputs the results in the form of
graphs and tables. You can directly see the operation of pipe laying in the form of diagram.Orcaflex
automatically performs static and dynamic analysis, and outputs the results in the form of graphs and
tables. You can directly see the operation of pipe laying in the form of diagram. Through the form of
tables, the stress and displacement values of each component, as well as the maximum stress ratio of
the over bending section and the sag bending section are obtained
16.3 OFFPIPE
OFFPIPE is a sophisticated, finite element method-based computer program. It has been developed
specifically for the modeling and structural analysis of nonlinear problems encountered in the
installation and operation of offshore pipelines.
In this project, the program is used for static &dynamic installation analysis of pipe laying. It will use a
detailed finite element model for normal pipe laying, abandonment and recycling analysis.
Pipelay Analysis
S-laying method is the most commonly used method of submarine pipeline laying at present. The stinger
and tensioner are the key equipment of S-type pipeline laying. First of all, according to the information
provided, including the clear height of each pipe support and tensioner, the draft of the ship and so on,
the model of pipe laying ship and stinger is established. Then set the total outside diameter of the
pipeline, the tension of the tensioner, the laying radius and the laying water depth. Then set the
environmental parameters, including current speed, wave speed and so on. Finally, the OFFPIPE will
automatically calculate the maximum stress ratio of the over bending section and the sag bending
section of the pipeline. By repeatedly adjusting the parameters, mainly tension and laying radius, the
maximum stress ratio of the pipeline shall not exceed the allowable value to ensure that the pipeline
will not yield or break due to excessive bending. Through many adjustments, find the appropriate
number of tensioners, tension and laying radius.
16.4 ANSYS
The ANSYS program itself has a strong 3D modeling capability, and the ANSYS GUl (graphical interface)
can create complex geometric models.
ANSYS is usually used for the stress characteristics of local structures. The Morison equation and other
wave theories can be used to generate the load spectrum and the stress and deformation analysis can
be directly carried out in ANSYS mechanical. In the project, the program is used for the strength and
fatigue life calculation of the offshore pole beam support structure.
Analysis Workflow
First, the model of supporting structure needs to be built. Because the supporting structure is mostly
simple geometry, it can be directly combined with the geometry defined by ANSYS. For example, using
multiple boxes to glue together by glue command can form a geometric symmetry.
After the model is built, attributes need to be given, including element attributes and material attributes.
Support structure generally uses solid element. Material properties can be input according to the
properties of steel, including Poisson's ratio, modulus of elasticity, etc. Then you need to draw the grid.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 63 / 67
The size of the mesh needs to be defined before it can be meshed for each individual. Then add
constraints and loads. The movement in X, Y, Z direction is limited to the fixed place. The load is added
according to the actual situation. Generally, the offshore supporting structure will be subject to waves,
currents, etc. These loads need to be converted into forces and moments by calculation before they can
be added to the model. At last, ANSYS will analyze the whole model statically. There are many analysis
results, including stress, displacement, and moment and so on. Generally, it only depends on the stress
and displacement.
16.5 MATHCAD
Mathcad is engineering calculation software. It is oriented around a worksheet, in which equations and
expressions are created and manipulated in the same graphical format in which they are presented
(WYSIWYG). In the project, it is used to calculate the wall thickness of pipeline, pipeline expansion, free
span, etc.
Different from other ocean engineering calculation software, Mathcad can't simply input parameters to
get the corresponding output results. Engineers need to find the specifications, find the corresponding
formula, and then use Mathcad to compile.
Taking the wall thickness calculation of unloading line as an example, engineers need to find out the
corresponding wall thickness calculation formula according to the specifications specified by the owner
(mainly API RP1111 and ASME B31.4), and then use Mathcad to compile the formula. First set the initial
value. It is necessary to give values to the parameters (such as water depth, outside diameter, design
pressure and other parameters) needed for wall thickness calculation. Then, the corresponding
equations are listed according to the formula, and the unknown number will be finally solved by
Mathcad through iterative layers. It also can plot the serial result in the 2D or 3D picture.
16.6 MOSES
MOSES software is a software tool that integrates modeling, simulation and analysis of ocean
engineering. In the long course of development, MOSES software has gradually matured, with its
functions covering offshore installation, hydrodynamic calculation, stability check, structural calculation
and many other aspects. In this project, it is used for pipeline floating stability analysis.
Modeling
Morrison's equations are used to combine plates, tubes and hull to simulate structures, as well as semi-
submersible or floating platforms. Then, hydrostatics, hydrodynamics and plate element grids will be
auto generated. The program can refine the mesh and compute the intersection, junction, and
difference values of defined polygons and apply these values to the mesh generated.
Hydrostatics Analysis
Automatic Ballasting calculates the load necessary to maintain the balance and gives the ship's draft
(draft depth, trim, heeling) and load. It can also interactively ballast the ballast tanks and automatically
correct the system weight and inertia.Add environmental loads, including wave loads, current loads, etc.
Result
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 64 / 67
The amplitude operator of the motion response at any point of the structure and the response
amplitude operator of the inertial force of the whole structure can be calculated.
Using the response amplitude operator and ISSC spectrum, JONSWAP spectrum, or user-defined
spectrum, you can calculate the resulting statistics.
A series of curves and tables can be generated for a range of draft and trim angles, including
displacement, waterline area, center of buoyancy and center of buoyancy position, transverse
metacenter and longitudinal metacenter height (KM) from baseline, load changing draft depth, and
moment changing trim.
16.7 SACS
SACS is an integrated finite element structural analysis package of applications that uniquely provides
for the design of offshore structures, including oil and gas platforms, wind farms, and topsides of FPSOs
and floating platforms.
In marine engineering, SACS is mainly used to analyze the stress, deformation and displacement changes
of marine structures under different working conditions. SACS have many types of analysis, but usually
only static analysis is used.
In this project, SACS may be used to analyze the stress, deformation and displacement of the stinger and
PLEM structure.
For stinger analysis, the stinger is located at the tail of the ship and is in a suspended state, which may
cause deformation under the action of gravity and may also be affected by other loads. Therefore, it is
necessary to analyze the overall structural stress of the stinger through SACS. Firstly, the model of stinger
is established. Because sacs can't build too precise model, it can only build a general outline with
members according to the specification and size of the stinger. Then modify the member properties.
Properties mainly include section, yield strength, etc. Generally, the roller is simulated by a round pipe,
and the other supporting structures are simulated by section steel. The base load is then added. The
stinger is mainly subject to its own gravity, pipe gravity, wind load, etc. Then the loads are combined
and multiplied by the safety factor (usually 2 at sea). Finally, the static analysis is carried out. SACS will
express the results in the form of text and graph, so that the stress and deformation of each member
can be observed intuitively, soas to judge whether the strength of the stinger meets the requirements.
For PLEM analysis, PLEM modeling is completed, and then different cases are added to check the
stresses and deformation of each member.
16.8 SAGE PROFILE
SAGE Profile is market leader software for subseapipeline analysis. It assists pipeline engineers in
designing and installing subsea pipelines.
Then, the software wasrapidly and broadly accepted in the industry, was immediately seenas afast and
efficient tool to performon-bottom roughness analyses,rock-dump optimization or even plough pick-up
analyses. This software allows modelinga broader range ofpipeline complexities,such as lateral or
upheaval buckling, thanks to its explicit finite element engine.
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 65 / 67
Analysis Workflow
The process of analyzing Bottom roughness with SAGE Profile is as follows:
⚫ Creating a project
⚫ Creating a new pipeline
⚫ Defining the seabed
Importing full 3D Digital Terrain Model seabed. Then, the DTM Seabed page offers some statistical
information (bin size, minimum and maximum Easting, Northing and Elevation) about the selected
DTM.
⚫ Creating a new route
At this stage, the type of the route be created by Easting Northing Elevation data. Then, the pipeline
route is automatically superimposed on the plan view of the Digital Terrain Model. The
corresponding pipeline profile is shown as well in the Graphics pane.
⚫ Assigning soil properties
In the Surface Soil Description page, we describe the properties of the (surface) soil over the entire
KP range. In the Graphics pane, expanding the ‘Soil description’ expander to show the assignment
of the surface soil versus KP. The Rectification page allows modifying the seabed, e.g. to fill gaps or
the smoothen sharp slopes.
⚫ Assigning pipe joint properties
In the Pipe Joint Assignment page, the entire pipe be described as an assembly of subsections built
out of uniform pipe joints. Modeling a single wall pipeline. For deriving some statistics on the
seabed roughness of the proposed pipeline route, we will perform a route stability assessment by
the “Route Stability and Seabed Roughness” page.
⚫ Simulating
These pipe-soil interaction zones and models are automatically identified based on the pipe joint
definition and the surface soil definition. The corresponding curves are shown in the Graphics Pane
under ‘Pipe Soil Interaction’.
⚫ Processing the results
Creating the plots for showing the span length and the stress of the pipe by the “OUTPUT” tab. In
the simulation, we define local logging to monitor the evolution of displacement or bending stresses
at this location, and this result also be shown as plots.
ANALYSISWORKFLOW CHART
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 66 / 67
RoughnessAssessment
Simulatin no Processing seabed
g
yes
finis
h
Figure 14.8-1. Analysis Workflow Chart
16.9 AGA
The AGA/PRCI OBS is considered the world standard for the design and analysis of sub-sea pipelines.
AGA/PRCI OBS features calculation of kinematics from 3-D irregular waves, several hydrodynamic force
models, models for partial burial, non-linear, time dependent interaction between pipeline and soil
(sand and clay) and non-linear pipeline material properties (for boundary elements). This allows for
detailed analysis of specific pipeline sections subjected to specified environmental conditions. The new
release consists of three (3) levels with Level 1 being used for quick simplified analysis, Level 2 for
comprehensive detailed design and modeling (most used) and Level 3 for advanced and very complex
sub-sea pipeline design modeling. In this project, it is used for pipeline on-bottom stability analysis.
In the Level 2 analyses, factor-of safety against lateral movement is defined as the net hydrodynamic in-
line force divided by the available soil resistance at the instant of least stability during passage of wave.
A minimum factor of safety of 1.0 has been used to indicate that the pipeline is stable.
The fundamental acceptance criteria for stability are as follows:
At the end of a 4-hour storm build up, the pipeline should be stable in the U1/100 condition.
At the end of a 3-hour storm period, the pipeline should be stable in the U1/1000 condition.
However, the following comments are made when interpreting the AGA results:
1) Instability for the U 1/1000 condition, but stability for the U 1/100 condition indicates that less than
4 waves in the design storm can cause pipe movement.
2) Instability for the U 1/100 condition during storm buildup, but stability for the 1/1000 condition during
design storm indicates the pipeline more likely to be stable during the storm.
3)Stability of the pipeline shall be checked for the maximum wave induced velocity corresponding to
wave break limit of 0.78 times the water depth where the significant wave height is stable and the
EPC OF LAWE-LAWE FACILITIES RDMP
RU-V BALIKPAPAN
Doc. No. :26076-110-G05-GAN-L0002 Rev No. : 004
AUTOMATION PLAN
Job No. : 26076 Page No. : 67 / 67
corresponding maximum wave height calculated as 1.86 times the significant wave height is not stable
for the given water depth.
4)For dense sands, where embedment is limited, thus soil resistance is not time dependent, this limited
movement will not impact soil resistance, therefore the pipeline will remain stable after the movement
has occurred.
5) For loose sands, soft clay conditions, where soil resistance is time dependent, pipe movement will
result in a significant reduction in soil resistance, hence large movements may occur since re-
embedment may not occur.
17 ATTACHMENTS
Attachment 1 Mandatory Custom Attributes
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks:
Remarks: