Professional Documents
Culture Documents
Brian Taylor
Snr Subsea Systems Engineer, J P Kenny
What is a System?
Definition An (assembly or) combination of interrelated elements (or parts) working together toward a common objective. Ergo, System Engineering is
The (design and) implementation of (production) systems that require the integration of diverse and complex tasks.
Project Drivers
System Engineering Process Project Development Team Development Phasing
Design Basis
The System
System Definition
System Drivers
Design Intent
Design Basis
Design Philosophies
Detailed Design
Installation Spread
System Drivers System Building Blocks Construction Flow Assurance Commissioning Operations Materials Control IMR & Installation
Infield Gathering
Import/Export Risers
Well Testing
Diver/ROV/ROT Flange Remote Tie-Ins None Topsides Dehydration Topsides Compression Subsea Dehydration Subsea Compression
Vertical Horizontal
Satellite Wells (Vertical or Deviated) Cluster Manifold Wells (Usually Deviated) Template Manifold Wells (Deviated) Distributed Tie-In Daisy-Chain
System Design
Equipment Engineering
Concept
FEED
Detail Design
Time
TERRA NOVA
QUICK C O NNEC T /DISCONNE C T T URRE T SOF E C MOORINGS SOF E C PIL E D ANC HORS
INSTAL L ATION AC T IVIT IES CSO R ISE R CSO 'HOST ' T E MPL ATE /MANIFOL D KOS
XMAS T REE S F MC
FLEXIBLE FLOWLINES
CSO OPEN 'GL ORY HOL E ' CSO
PC C SO SBR HE S PC L F MC DC
PE T R O-C A NADA C OF L E X I P ST E NA OF F SH OR E SH AWMONT BR OWN & R OOT H AL L I B UR T ON E NE R G Y SE R V I C E S PC L C ONST R UC T OR S F MC (SOF E C , K OS) DOR I S C ONPR O
Questions......
Workshop
Its discussion time........ We will spend the next 30 mins or so split into 2 groups
Group 1 Suggested key words: Responsibilities Ownership Deliverables (e.g. P&ID, Philosophies, Design Basis etc) Input & Influence [on project processes] Gate / Peer Reviews
Group 2 Suggested key words: Integrated Team System Manager Current project s [examples of use] Opportunity [to adopt as industry approach] Scaled [down for a small project]
Conclusions
We will record any outcomes from today's workshop and present them to the SUT for their use
Group 1
Frame how the systems engineers responsibilities progress through the project lifecycle. PHASE 1: Definition of project design basis. Engineering concept definition / functionality. Take reservoir characteristics and provide to FA engineer FA design basis. System manager frames the opportunity. Develop a high level concept to prove commerciality of project. Feed into overall value of project (NPV, R01, etc).
14
Group 1
PHASE 2: Generate alternative layouts for subsea architecture. Enhance project design basis, philosophies, P&IDs and strategies. Develop Subsea design and Pipeline design. Constraints on project contracting strategy, scheduling drivers and government issues etc. Technical qualification program. Screen options, both internally and externally. Select preferred option and provide recommendation. Conduct Pre-FEED surveys. Define technical specifications that need to be developed in Phase 3 (FEED ITT package). System engineer ensures integrity of design.
15
Group 1
PHASE 3: FEED Driver to attain scope definition. Develop a schedule. Integration of all disciplines: Functional engineer. Operations. Flow assurance. Precommission / IMR. Project Execution Plan Role &Responsibilities. Prequals verification and assurance program. ITT procurement packages. Subsea Equipment Vendors, Umbilical Vendors, etc. Long Lead Items based on schedule constraints. Class III established. Final Investment Decision [FID].
16
Group 1
PHASE 4: Execution. Award and manage packages. Interface management. Ensure project support is in place and processes are clearly defined. System verification activities: Design reviews. Monitoring and assessing Fit for Purpose SIT Constructability and installability.
17
Group 2
Current Projects and how the system is managed: Pluto Systems manager Process and FA Materials / integrity Operations Commissioning I/F management Gorgon Engineering management Standard guidelines WEL SSF Integrity Team (TIAs) Centralise TIAs by project at the project base Integrated team.
18
Group 3
Does the TIG work? There appear to be lots of chiefs is this extra responsibility over there normal discipline role? There has to be a facilitator for the TIG. But with what level of responsibility? The process needs to be well defined before project kick-off Lessons learnt from various projects (see group 2) should be compiled to see if it transferrable to your project Pros of TIG type & of Traditional type Cons of TIG type & of Traditional type Communication is key to the TIG Project management systems must be coordinated across the different disciplines/contracts Interfaces have to be filtered, meaningful and given prioritised accordingly Empowerment people in the TIG must be given the authority to make a decision and follow it through Scaling does not appear to be an issue and the TIG would seem lend itself particularly well to projects with smaller client team
19