Skip to content

Completion component (Well, Zone)

Yue Zhang edited this page Jun 23, 2021 · 12 revisions

Introduction and history:

This component was first designed to be a Reservoir engineering tool for investigating which zones in which wells were perforated at which time. User story: As a reservoir engineer, I like to get an overview of which zones in which wells are producing when. In addition, I also like to display kH per zone per well in order to get an indication of the productivity index (Productivity index is proportional to kH, k = permeability, h = net thickness)

For an ensemble of models, the perforation per well per zone is a calculation of the percentage of realizations/runs where that well/zone is perforated in the user-selected time interval. For kH the value will be an average of kH for the realizations/runs for that well/zone.

In BigLoop or FMU the perforation information is taken from the input files (COMPDAT) to simulator alternatively from geological modeling software. The ECL2DF library can be used to extract data from the input files (COMPDAT) to the simulator (https://github.com/equinor/ecl2df, documentation https://equinor.github.io/ecl2df/)

There may be many other use cases for the Completion component as both geophysics and geology have several use cases for displaying well zone information for both one model and an ensemble of models.

MS1

  • Thickness of line for the given well zone indicate the percentage of perforation status
  • well selector
  • Well sorting
  • Time interval selector and choosing at state start/at end/average/maximum
  • Zone filter/selector
  • Tooltip for mouseover on a given well/zone

MS2

  • Export zone/layer info, and well attribute/collections from RMS
  • Display kH values
  • Filter by well categorical attribute
  • Change color for completion (Color for open, color for closed, color for not perforated)

MS3

  • Decide options for using with, colour, sparkline/logline

Demo of each child component is available by running "npm run storybook"

Each component also has corresponding tests (XXXX.test.tsx) which cover snapshot tests and user event tests.

Clone this wiki locally