integrated remote control system
Post on 12-Sep-2021
10 Views
Preview:
TRANSCRIPT
© 2010 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of Invensys or its subsidiaries. All third party trademarks and service marks are the proprietary marks of their respective owners.
© Invensys 00/00/00 Invensys proprietary & confidential Slide 1
Total EP NL Integrated Remote Control System Stavanger 1st March 2012 Hans van Gool Delivery Director Invensys Operations Management
Introduction Me, Hans van Gool, Delivery Director. Ref. to Mr. Denneman Total EP NL (it’s his presentation)
‘The Automation and Control team lead with strong vision’
Subject:
Enable remote operations from a Central Control Room for 21 offshore platforms offshore Northsea, technical concepts as well as the human factor translated into operational and alarm philosophy to cope with increased span of control.
Situation now versus new situation with full integrated operations from CCR
Slide 2
Slide 3
• Total E&P Netherland is a subsidiary of Total SA in Paris and produces gas from the Dutch continental shelf in the North Sea.
• 19 million sm3/d gas production to Client Gas Terra
• 23 Offshore platforms 4 Main treating treating centres (Day shift) 19 Satellite platforms (Unmanned) Central Onshore Control Room (24/7)
Slide 4
Terminology Infrastructure and systems
• DCS versus Scada
• DCS, integrated control and visualisation system (Single Vendor)
• Scada, Visualization and PLC based control (Multi vendor)
• OPC versus proprietary protocol for data exchange
• OPC for tag data exchange between different systems (Vendors)
• OPC standard does not cover for connectivity fail recovery
• OPC+ is vendor developped OPC solution with tested and proven
recovery.
• Wonderware Scada System Platform for interconnecting multiple
locations based on proven proprietary protocol
Slide 5
Current Situation today
Slide 6
Slide 7
Aw AW AW
Radio tower
CP OPC interfaces
CP
Aw AW AW
Radio tower
CP OPC interfaces
CP
Aw AW AW
Radio tower
CP OPC interfaces
CP
Aw AW AW
Radio tower
CP OPC interfaces
CP
Aw AW AW
Radio tower
CP OPC interfaces
CP
L7P (TC)
K6P(TC)
K5P(TC)
F15(TC)
CCR
Current system Treating Centres to CCR
CCR – TC’s 8 Mb KPN Tough
network
TC’s – Satellites 2 - 8 Mb KPN Tough
network
All Comm. Based on OPC
Slide 8
Current system Satellites to TC’s to CCR
Treating Centre
K6CC Treating Centre
K5CC Treating Centre
F15 Treating Centre
L7CC
CCR Central Control Room (Onshore)
Satellite
K6D
Satellite
K6DN
Satellite
K6GT
Satellite
K4A
Satellite
K4BE
Satellite
K5B
Satellite
K5D
Satellite
K5EN/C
Satellite
L4PN
Satellite
L7N
Satellite
L7H
Satellite
L7B
Satellite
L4A
Satellite
L4PN
Satellite No Sys
L7A K1A K5F
Satellite
K5CU Satellite
L4B Satellite
K6N
History
• 1990 - 1996, Start with TC’s automation using Emerson Provox DCS and Triconex safety systems
• 1998, Comsat project, Sattelite platforms Scada to Fix32 and interconnect all platforms with OPC basis is Millenium compliancy.
• 2001, K6CC First Foxboro Plug-in Migration to migrate obsolete Provox with minimal downtime introducing OPC+ for recovering network outages.
• 2002 – 2010, F15A, L7CC, K5CC, remaining treating centers and critical satellites, migrate to Foxboro DCS
• 2003, CCR first CCR move, 2007 second CCR move both on OPC base with reduced dataset.
• 2009, alarm rationalization project to unify alarming across all platforms and implement Ureason alarm management over all platforms
• 2011, ObsoleteFix to Wonderware migration for 12 Satellite platforms, Changeover in 3 days.
• Now, move from remote operations to Integrated operations from Onshore with 1 to 1 operations onshore - offshore.
Operational tasks and responsibilities
Offshore Satellites
• Unmanned, designed for remote operations, remote start / shutdown
Offshore Treating centres
• Maintain the availability of the asset and related satellites
• During day shift strong support to CCR operator in operations of the
Treating Centre and related Satellites
• Backup operations for CCR during night.
Onshore CCR
• Monitoring and control of the offshore assets.
• Dispatching, Nomination planning to Gas Terra, per platform based on
3 pipelines, WGT, NGT and Nogat . Slide 10
Slide 11
Overview Gas Nominations
Satellite Platform Wonderware HMI
Main control (2 consoles each with 2 monitors)
CCR • Strong ergonomic design (Office env.) • Overview nominations and total assets
production • 2 identical operations positions/consoles • At night all nomination is controlled from
CCR, during day TC’s support control the assets
• TC and Sat based on reduced dataset Operations Real time, OPC
• Alarm management using reduced dataset alarm generations
• Satellite operations realtime based on Wonderware system platform from all locations
• Remote desktops and terminal sessions as backup for details for TC’s
CCR operations
Technical concepts High level availability of systems with focus on data integrity
• Treating Centre platforms and critical Satellite platforms to have DCS.
• Less critical satellites equipped with PLC / Scada solution
• All platforms have Triconex TMR safety system for ESD / Fire & Gas.
• Redundant OPC solution for all communications between the platforms
and on-shore
• OPC+ high available OPC link with high recovering from instable
communication infrastructure.
• Implement uniform solutions/versions across the platforms
• Reduced tags configuration for remote real time operations.
• Remote desktops and terminal sessions as backup and detailed info
Slide 12
Key benefits available from the current system Not to lose this functionality moving to the integrated system
• Scada (Wonderware) and DCS (Foxboro) have one unified operating philosophy
for operations
• 1 unified library for Human Interface, Process Control and Safety Control
• Alarm annunciation allowing direct alarm access
• Lean data exchange between Offshore and Onshore as a result from good
operational knowledge of Total EP for optimal minimal use of infrastructure
• All locations (TC’s and Satellites) are autonomous
• Fallback/Detailed info available from remote sessions for all offshore platforms.
• 2 operators operating all platforms during the night from the onshore CCR.
• Two 12 hours shifts onshore for two operators aligned with the offshore shifts
Slide 13
Requirements by Total EP
Enable Full (1 to 1) operations from CCR
‘higher span of control’ ‘Less dependent on offshore operations’
Operations, Maintenance
Slide 14
Operational requirements (Total EP) Full operation of assets from CCR
• Functional Identical workstations Offhore and in Onshore CCR for
• Graphic displays
• Alarm annunciation
• Integrated alarm sounding, acknowledgement and logging
• Connectivity to main historical database for operational information provision
to non production related personnell on Office network
• CCR alarm display must visualize ALL offshore loacations alarms on one
screen
• Defined real-time response times, overdue results in alarm
• Introduce onshore CCR tighter alarm settings to allow for longer reaction to
resolve some critical situations
• No single point of failure
• Have a fall back possibility and Disaster recovery plan.
Operational requirements (Total EP), ‘other tasks’ Ergonomic integration of other operator tools and systems
• Overview screens for dispatching / Nomination planning
• Production calculation tools. Link the demanded nomination to the selection
of the in total approx. 100 wells, to achieve the nomination, ~19 million m3/d.
• Ureason alarm management overview Preventive Versus Reactive
• Nomination messaging system (Edigas), Prod. reporting to Client. (Gas Terra)
• AIS, Automatic Identification of ships system monitoring
• Email communications
• Risk analysis for exception handling to nominations demand deviations and
reporting off nominations demand deviations
Slide 16
Maintenance requirements (Total EP)
• One set of graphics for CCR and Offshore
• One engineering database
• Single location for information storage, use of typical solutions
resulting in reduction in maintenance and engineering efforts
• Achieve where possible identical look and feel for all locations
• Standardization of functions
• No single point of failure, allow for repair on next business day
Slide 17
Constraints (Total EP)
Reliability and timing of the offshore communication infrastructure
• TEPNL makes use of a KPN (provider) maintained microwave system, which
is rented by a consortium of all operators in the North Sea (TOUGH)
• Related to bandwidth, a dedicated minimum bandwidth will be made available
(8 Mb) for this use to each offshore location
• Average ping response time is below 20 ms. In case of switching, due to poor
reception of the radio signals, the transmitter will switch to the alternative
route, which will take 200-400 ms and will occur average once-a-day
(depending on weather- and sea conditions)
• OPC Standard not to cover for connectivity definition
Infrastructure is considered most critical to achieve real time behaviour for the
CCR onshore (50msec. Is considered limit).
Slide 18
Slide 19
Future System Architecture
Handle Constraints
Integrate the systems
Slide 20
Operations execution: Total EP and Invensys What is the secret?
• Basis for the final integration of systems is there. DCS + Scada = ECS
• One vendor for all systems, one support contract, one vendor for first level
24/7 support for all systems.
• Relation is based on different disciplines involved in the use of the systems to
all achieve their goals, Maintenance, Operations and Engineering.
• Project execution, delivering projects on time within the budgets for 11 years
now. ‘Do what we upfront define we will do’, Good definition is key.
• Allow for both formal (contractual) and open and informal communications
and recognize the importance of both.
• Solutions thinking on all levels.
• Availability of Global Agreement and local transparent frame agreement for
executing projects.
Slide 21
Contact us:
Slide 22
Questions?
Slide 23
top related