Oil & Gas Integrated Operations using aspenONE Nick Barnett

Agenda Drivers for Integrated Operations Solution Overview Architecture Functionality and Screenshots More than just real-time process data Model integration and simulation

Drivers for Integrated Operations

Drivers for Integrated Operations

Importance of Asset Monitoring Upstream Business is Complex, with numerous sources of Data, Documents, Procedures, Alarms, and disparate Systems containing information critical to successful and reliable Asset Operation. Poor Access can impact Safety, Reliability of Production, Ability to Prove use of Best Practices, etc. Workflow is Critical to Success! Access to Information at the right time is critical to Operations performing best utilization of knowledge in running assets. Ease of Access and Use of Operational Knowledge and Systems should translate to improved use of Best Practices and Decision Making Processes that prevent Safety, Lost Production, and Operator Error Incidents.

Total Exploration To access easily to all the tools To create a common identity A FO portal for the future ? Best Practices Staff management Documentation KPI’s Dashboards PDMS Action Plan POB data base SAP Planning PJC/EXP Seminar – “Cap Coopération” Nantes – December 15th to 17th, 2004

aspenONE Asset Monitoring for Oil & Gas Production: IP21 Enterprise Historian with Operations Manager for monitoring and visualization of various data sources. Drilling: Time-based Drilling data monitoring and visualization based on WITSML (client & server) and Vertical Trending

aspenONE Asset Monitoring for Oil & Gas The Digital Oil Field aspenONE Asset Monitoring for Oil & Gas Remote onshore experts Onshore experts Offshore control room Onshore Maint. Ops Onshore Ops Center O&G Inc.

Typical Production Architecture Onshore Ops Center OM-II Publish/Subscribe Bus

Integration Evolution Database Message Bus Point-to-Point App App App App App App App App Data Centric Open Message-Based InfoBus App App App App App App App Scalability Unknowns High cost of Support & Maintenance Monolithic Data Store Creates Redundant Data Central Point of Failure Distributed and Scaleable Functionally Rich Event-Driven

Integration Infrastructure versus OPC OPC is a very popular standard for integrating within a plant or on an oil platform When you want to connect multiple platforms to a Corporate Office it is not so suitable, especially if you want to manage security and firewalls and achieve very high bandwidth and this is where OM-II comes into its own – it is even more of a requirement where network connectivity is poor OM-II provides centralized licensing, security, audits

Event Driven, Message-based Integration Publish/Subscribe, Request/Reply Interactions – combats availability issues Asynchronous messaging – combats bandwidth issues Multiple qualities of service for message delivery – combats bandwidth issues Business process workflows – improves information flow to where needed Distributed run-time components – improves uptime and access to data Scaleable – as field develops and expands APPL B APPL E APPL A APPL C APPL D Point to Point Vibration Analysis Wellhead Testing MMS Apps Historian ERP The picture on the top left depicts legacy integration architectures where all applications make point-to-point connections with each other. The following are the problems with such an architecture: Such systems can be difficult to develop, maintain and port. Components must agree on network connections, low-level format for data transfer, and other details. Architecture does not scale, Difficult to add new functionality without impacting the existing applications. TIB/Rendezvous software allows the components of a distributed system to be more loosely coupled. Loose coupling decreases costs for development, operation and maintenance, and increases system longevity. The analogy is that of a hardware bus where you plug in applications on the backplane and they all communicate with each other seamlessly. Condition Monitoring Bus 9

Typical Dashboard

Example Well Overview

Event Management - Diagnosis

Role Based Visualization Create Once – Use Many Times We can define Objects: Pumps Compressors Wells etc With Standard tags Standard process events Standard calculations Standard economic information Standard graphics And Use Multiple Times RDB Data Tags Calculations Events

Flexible Data Structures Support Your Applications Create Objects that model your assets

More than just real-time process data Access to key documents – in context Production & Injection Plans Condition monitoring of rotating machines Well Testing Production Allocation and Reporting Creating maintenance work orders Model integration and simulation

HYSYS Model Integration using OSE™ Teams using an integrated approach to the business, leveraging discipline-specific expertise, and rigorous simulation Integrated Business Approach Reservoir Engineer Economic Analyst HYSYS model (s) HYSYS Reservoir model (s) Pipeline model (s) Economic model (s) Process Engineer Production Engineer

Integrated Asset Modelling: Aspen OSE™ provides a ‘Single Integrated Asset Model’ framework that integrates with Aspentech and third-party vendor simulation, optimization and planning tools which allows engineers to: Manage and connect models of wells, gathering systems, and facilities Simulate the entire asset in Aspen OSE™ using HYSYS™ (Upstream) and 3rd party tools Analyze individual variables from multiple models, and develop large scale optimization and planning solutions

Aspen OSE™ Aspen Open Simulation Environment OSE Extends the value of models across the enterprise through: Model Interoperability Model Execution Model-based analysis Model management Model deployment

Questions…

Thank you! Nick Barnett nick.barnett@aspentech.com