DOC ID © Chevron 2005 Chevron PRODML Pilot Activities Vendor Participants: Invensys Weatherford...

DOC ID© Chevron 2005

Chevron PRODML Pilot Activities

Vendor Participants:

Invensys

Weatherford

Tibco

Halliburton

Matrikon

Euriware

Energy Components


Background

Chevron’s pilots have a few common characteristics:

• Using a large brownfield waterflood field as a basis

• Concentrating on water handling

• Providing a number of vendor opportunities

• Developing in-house capability

• Expanding in scope over time


Background (cont…)

2006: Compared Field vs Facility forecasts and notified operator. Stress tested the standard with multiple 700 well data calls in a single process model

2007: Combined multiple elements – forecasting, real time capacity management, field network optimization and cross-functional visualization

2008:

A: Continue to refine pilot to plug and play pieces (8) that are “fit for purpose”

B: Testing new WG07 functionality (SAM-Shared Asset Model, extensibility)

C: Working with other PRODML members on NOJV reporting

D: Preparing to test the use of WITSML data for well modeling


Characteristics of a Workflow

A workflow …

• should systematically organize components;

• should define roles, for operator personnel, for vendors and for automated systems;

• must have endpoints that effectively define the purpose of the process;

• needs defined information exchanges (such as those defined as part of the PRODML Standards);

• needs visibility of information flow;

… and looking ahead to results, a workflow:

• leads to achievable results;

• has a process that can be documented and learned;

• enables measurement of results.


End to end workflows are complicated

End PointsR

ese

rvo

ir

Production ManagementWater Management

Figure 3

Reservoir Field Facility

FacilityFieldReservoir


We chose water management so we could prepare definable process blocks

End PointsR

ese

rvo

irProduction ManagementWater Management

Figure 4

FacilityFieldReservoir

ProductionHistoryProduction

Forecast

Capacity ForecastWell

Production Changes

PumpSettings

Injection Targets


Typical setup – Note how we can separate IT and Tech activities

Calculator 2

Systematic organization of resources

Orchestration

Calculator 1

Visualization

DataCube

Data Integration

RulesTrigger

DataSources

DataLayer

Figure 2


Data Integrator

Chevron Pilot - 2006

InvensysFacility SCADA History

WeatherfordWell TestHistory

Local System (SS)Field Oil Sales / Inventory

History

Local SystemField Gas Sales History

WeatherfordStatusHistory

Energy ComponentsDaily Allocation / Status / Well Listing

WeatherfordLOWIS

Well StatusForecast

HalliburtonDSS

Well ProductionForecast

InvensysInFusion

TankForecast

InvensysNotification

2b

4a

14 Future: Check well test before shut in order

15 Same as 9a/b

2a

101

5a

6a

7a

8

9a

11

12a

13 Future; Add to tank forecast

1 Trigger: Clock set for once a day

2 GetFromStore: Get tank data (7 days)

3 Model: 7 day tank forecast

3

4 AddToStore: Pass tank forecast

4b

5 AddtoStore: Alarm to notification

5b

6 GetFromStore: Well forecasts

6b

7 GetFromStore: Well allocated production (x days)

7b

8 Model: 7 day production forecast

9 GetFromStore: well status forecast

9b

10 Model: Maintenance forecast

11 Model: Well vs Facility Qw in

12 AddToStore: Consolidate data

12b

13

14 15


Chevron Pilot - 2007

Orchestration

Predict Produced Water Change

2 5b4 3

Notify

Data Integration 7 Day forecastBased on past 7 days

And including maintenance

7

7 da

ys o

f Pro

d

Blk

Val

ve S

tatu

s C

han

ge

5 1

1

WellHistory

GiveData(drop file)

14 d

ays

of

Inj

Wel

l Tes

ts

4b3b2b 6

Trend Model

Figure 5

Orchestration

React to Tank Level Change

1

5

4 3

Notify

Data IntegrationTank Model

78

6

Tan

k Le

vel &

Qo

ut

Act

ive

Wel

l Lis

t

Sta

tus

On/

off

Wel

l tes

t

2

WellHistory

SCADA

Based on Recommendation Filter active well list by StatusAnd Block Valve Status

Based on RecommendationSort by BOPD (open) or WOR (SI)Solve for >= Recommendation(maximize oil producing)

Rec

omm

enda

tion

Level Trend

0

5

10

15

20

25

30

9/5/0723:52

9/6/070:00

9/6/070:07

9/6/070:14

9/6/070:21

9/6/070:28

9/6/070:36

Time

Ft

0

5

10

15

20

25

30

Open8500Recommended Volume

Change

List of wells toopen or close

Figure 6

Ta

rge

ts,

Co

nst

rain

ts

Orchestration

Optimize Injection to Target[Change of Water Source At Headers]

1

9

64

Recommend

Data Integration

System Optimizer

8

Network Model

3

7

WellHistory

Blk

Val

ve S

tatu

s C

han

ge

SCADA

Q,P

Pu

mp

s &

WIW

s

NetworkSoR

X-referenceSCADA tags

1b 4b 6b 7b2

Act

ive

Wel

l Lis

t

Cur

rent

.cf

gfil

e

5

He

ade

r Li

stin

g

Figure 7

Orchestration

Visualization Orchestration

2 54

VisualizationResponse

76

VisualizationRequest 1

3

Data Integration

NetworkSoR

SCADA

X-referenceSCADA tags

Provide roll-upWell/hdr/section

Figure 8


2008 – Meet Workflow CriteriaPlug & Play / Intersecting Workflows

BForecast

APre-

Processor

CRT Tank

Level Mngt

DWell

Changes

ESource

Wtr Needs

FNetwork

Opt.

GExcept.Report

HX-F(x)Visual

E’InjectionTargets

G’Well

Model

B’Alternate

Model

B”Alternate

Model

Fit for purpose – forecast accuracy meets need of next step

Test WITSML Data acquisition – Automate well model building

Touch point – Reservoir management sets targets

Test Shared Asset Model – Network changes


2008 – NOJV Reporting

BAOpportunityAssessment

C D E

• Organize interested parties• Prepare project plan• Given: use North Sea example as guide• Get internal input vs guide

DOC ID © Chevron 2005 Chevron PRODML Pilot Activities Vendor Participants: Invensys Weatherford...

Documents

Transcript of DOC ID © Chevron 2005 Chevron PRODML Pilot Activities Vendor Participants: Invensys Weatherford...