AI Assistant

A subsurface analyst that can read your project and the public Texas data, answer in context, and drive the map.

Opening the Assistant

Assistant icon, upper toolbar.

The assistant opens as a panel on the right-hand side of the application. The map stays live behind it, which is deliberate — answers frequently refer to what is on screen, and the assistant can change what is on screen. Type your question in the box at the bottom and press Enter or click Send.

What It Can Do

The assistant reads from two sources and will tell you which one a number came from:

• Public data — Texas RRC records for every well in the state: operator, lease, field, total depth, completion and plug dates, permits, wellbore records, FracFocus completion disclosures, allocated production and the directional surveys the RRC publishes.
• Your project — the directional surveys, well logs, formation tops, headers, landing zone interpretations, production and saved forecasts you have imported.

Typical work it handles well:

• Offset and analog analysis — nearest wells measured lateral-to-lateral, with the distance to each one quoted.
• Production questions — history, peak rates, cumulative volumes, decline behaviour, EUR estimates and ranking across a set of wells.
• Completion intensity from FracFocus — proppant and fluid loading, normalized per foot, compared against neighbours.
• Well and lease lookups — operator, status, permit history, spud dates, elevation and datum.
• Spacing and development questions across a section or a lease.
• Structural questions against your grids, and landing zone calculations.
• Log and petrophysical work where your project has the curves for it.
• Driving the application — it can move the map, select wells, and annotate the map with what it is describing.

How to Ask

Treat it like a colleague who has the data in front of them. Naming a well, lease, operator or API anchors the answer; so does having the well selected on the map before you ask. Follow-up questions keep the context of the conversation, so "now show me the gas" or "what about the one to the south" works.

The assistant is instructed to compute before it answers, to quote distances, and to compare like with like — modern horizontals against modern horizontals, not against a 1985 vertical on the same lease. If the data for an answer is not there, it will say so rather than estimate. Every number it gives comes from a query, not from recall.

Token Allowance

Assistant usage is metered in tokens and resets at midnight Central time:

Tier	Daily allowance
Free	1,000,000 tokens per day
Premium	5,000,000 tokens per day
Enterprise	Unlimited

The allowance is checked before a question is accepted, not during the answer — a question that starts inside your allowance always finishes, even if it runs past it. Once you are over, the assistant will tell you what you have used and when it resets. Nothing else in the application is affected: the allowance applies only to the assistant.

Your usage for the session, today, this week, this month and all time is shown on your account page.

If the Assistant Cannot Answer

• Check that the right project is selected — project questions are answered against the selected project only.
• Check that the data it needs is actually imported. It will tell you when a project has no logs, no production or no grids rather than guessing.
• If you have hit the daily allowance, the message will say so explicitly.
• If an answer looks wrong, ask it where the number came from. It will name the source and the well.

Public Data

Every permitted well in Texas, hosted by us, available to every account without importing anything.

What It Is

OG Welly hosts the public Texas Railroad Commission well data. It covers the whole state and includes well headers, completions, drilling permits, the RRC well bore database, FracFocus completion disclosures, allocated production, and the directional surveys the RRC publishes for the subset of wells that have them on file.

Public data is available to every signed-in account on every tier, it does not belong to a project, and it does not count against your storage allowance.

Turning It On

Wellbore Dropdown, map editor toolbar.

Select OG WELLY from the Wellbore Dropdown, the same dropdown you use to pick one of your own imported directional survey files. It appears at the top of the list and is selectable even before a project has been chosen, because it does not use projects.

The wellbores are served to the map as tiles, so only the wells inside your current viewport are fetched and drawn. Zooming out over a large area will show fewer wells than zooming in — that is the tiling working, not missing data.

Clicking a Well

Clicking any public wellbore on the map opens the wellbore legend card, which shows the API, the operator, the lease and well number, and an inferred status pill. Hover the status pill for the evidence behind it — the label is an inference, and the tooltip tells you what it was inferred from.

The card carries four actions:

• Plot Well — adds the well to the trajectory / gun barrel plot.
• Well Header — opens the full well header window described below.
• StrataView — sends the well to the StrataView module.
• Production — opens the Production module with this well selected.

The Well Header Window

The Well Header window is organised into four sections, selected by the chips across the top. Every well opens on General.

General

The RRC well header and completion record: API10 and API14, lease name, well number, operator, field, county, district, total depth, completion date, plug date, permit number, the oil/gas code, and surface and bottomhole coordinates.

If the well is also in one of your own imported header files, your header row is shown here instead — your naming and your columns take precedence over the public record.

Completion

FracFocus disclosures for the well, one chip per disclosure job when more than one is on file. This is where completion design lives: fluid volume, proppant mass, and the derived intensity figures.

Permit

The drilling permit currently in force: permit number and sequence, purpose, profile (vertical, directional, horizontal, sidetrack), operator number, permitted depth, the received / issued / amended / expiry dates, spud date, surface casing date, status, legal location, surface acres, nearest city, Rule 37 and Rule 38 references, and the permitted surface and bottomhole coordinates.

A well collects several permits over its life, and each permit collects amendments. This section shows the most recently issued permit at its current sequence, and the note underneath tells you how many permits are on file and how many times the one shown has been amended.

A blank spud date means not reported, not "not drilled". If nothing appears at all, the note will tell you the date range the permit table currently covers. The RRC publishes one file per month.

Wellbore

The RRC well bore database record: elevation together with its reference datum, completion and drilling-completed dates, the W-2 / G-1 received date, formation name and depth, plug-back depth, whether a directional survey was filed, survey and abstract, block and section, WGS84 coordinates, the number of filings on record and the date of the latest one.

The elevation datum is the reason this section exists. Every depth in a log is measured from somewhere, and ground level to kelly bushing is typically 10–30 ft — exactly the size of error that makes two wells appear to disagree about a marker. Where the RRC gives an elevation but no reference, this section says so explicitly rather than leaving a blank that looks like ground level. About half of the wells in the database predate the requirement and have no elevation at all.

Public Production

With OG WELLY as the selected wellbore layer, the Production module plots RRC production for the clicked well. Oil combines oil and condensate; gas combines gas well gas and casinghead gas.

Coverage and Limitations

• Coverage is Texas today. Additional states will be added over time.
• Directional surveys exist for the digitized subset of wells. A well with no survey on file plots from its surface and bottomhole locations.
• The permit, wellbore and disclosure tables are loaded from the RRC and FracFocus on their publication schedule. A recently permitted or recently completed well may not appear immediately.
• The data is republished as the agencies publish it. Where a record is blank, missing, or internally inconsistent, we surface that rather than filling it in.

Shapefiles

Importing, projecting, symbolising and troubleshooting vector layers.

Importing Shapefiles

Shapefiles are uploaded through Large Imports → Shapefiles, in compressed ZIP format. If you have trouble importing or viewing a shapefile:

• Ensure all required files (.shp, .shx, .dbf, .prj, and any other sidecar files) are inside the ZIP.
• Check for invalid geometries before upload.
• Navigate to Manage Data → Shapefiles to confirm the layer reached your project.

A single upload is limited to 1 GB, and the ZIP's contents may not expand beyond 500 MB uncompressed.

How Shapefiles Are Drawn

An imported shapefile is converted at upload time into a vector tile layer and drawn on the map as a tilelayer, the same way the public wellbores are. Two consequences are worth knowing:

• The browser only fetches the tiles under your current viewport, so a layer with hundreds of thousands of features is practical to work with. Panning fetches more; it is not reloading the layer.
• Colours are not baked into the tiles — they are applied in the browser from the feature attributes. Changing a symbology is therefore instant and does not re-download anything.

Tiles are built once, when the layer is imported. A very large layer may take a moment to finish processing after the upload itself completes.

Projection

Shapefiles are projected to EPSG:4326 (WGS84). If a layer lands in the wrong place, check the .prj in your ZIP — a missing or incorrect projection definition is the usual cause.

Attribute Tables

Shapefile attribute tables can be viewed in the Shp Data window. Previously imported shapefiles can only be viewed once the data has been fetched into the current session with the shapefile Fetch button.

Clicking a feature on the map opens a legend card naming which layer the feature belongs to, along with its attributes — useful when several shapefiles overlap.

Symbologies

Shapefile layers default to white polylines (white fill if the geometries are closed polygons). Symbology is edited in the shapefile Symbology window by selecting the layer you want to change. There are two methods:

1. Basic style
2. From shapefile attributes

Note: to apply a symbology to the selected layer you must click Apply Symbology at the bottom of the window.

Basic Symbology

Basic style applies the same colours to every feature in the layer. Fill opacity, line width and fill behaviour are all adjustable, and features can be labelled using an attribute value.

Attribute Symbology

Attribute symbology colours individual features from a selected attribute. A numeric field is binned into equal-range groups according to your bin count; a qualitative field is binned into unique values. If the bin count is smaller than the number of unique values, an "other" bin is created and the remaining features share one colour.

Map Latency

If the map is slow, the usual cause is too many layers drawn at once rather than any single layer. Turn off what you are not using, and prefer simplified geometry for layers you keep on permanently.

Deleting Shapefiles

Navigate to Manage Data → Shapefiles, select the layers you want to remove, and click Delete. The layer, its attributes and its tiles are removed from the database and the storage is returned to your allowance.

Trajectories

Directional surveys, the wellbore plot, the gun barrel view, and wellbore symbology.

Importing Directional Surveys

Directional surveys are uploaded through Large Imports → Trajectories. OG Welly expects a .csv containing the following fields:

• API Number
• Latitude
• Longitude
• True Vertical Depth
• Measured Depth

At import you will be prompted to map your CSV's columns onto those fields, and to select the join well header containing the wells in the survey file.

Please import the corresponding well header .csv before importing the trajectory file.

Viewing Wellbores

To put a group of wellbores on the map, select one of your imported directional survey files from the Wellbore Dropdown. If you make a selection and still cannot see your wells:

• Pan or zoom to the approximate location of the wells.
• Adjust the symbology of the wellbore group.
• Confirm the survey imported correctly and that a join header was defined, by selecting the file in the Well Data window.

Wellbores default to a single colour when first loaded. See Symbologies below to change it.

Trajectory / Gun Barrel Plot

To plot wells, you must select at least one well. There are three ways:

• In the secondary toolbar, click Select Wells by Polygon, click New, and draw a polygon intersecting at least one well. A selection may not exceed 50 unique APIs or it will be rejected.
• Click a wellbore on the map and click Plot Well in the wellbore legend card.
• Select a well name from the Well Name Dropdown, below the Wellbore Dropdown.

The wellbore plot is hidden until at least one well is selected. It opens in Trajectory view and can be switched to Gun Barrel view with View Mode → GB in the secondary toolbar.

The wells currently on the plot are shown as chips along the top of the plot. Clicking the × on a chip removes that well from the selection without redrawing the whole thing.

Trajectory View

The full selected wellbore(s) are plotted using TVD for the y values and the xy offset between each survey station and the surface hole for the x values. Click and drag on the plot area to zoom in; scroll on either axis to zoom out; change the selection from the Wellbores section of the toolbar.

Gun Barrel View

Gun Barrel view plots a cross-sectional view of the selected wellbores. When you first switch to it, the gun barrel line is generated North–South through the mid-point of the selected wells, which may not intersect all of them. Wells that do not intersect the line, or that are not in the selection, are not plotted.

The line's position and orientation are adjusted with the sliders in the Gun Barrel section of the toolbar: 0–360° of rotation, and up to 10,000 ft of pan perpendicular to strike in either direction.

The intersection points are drawn on the map, along with A (the start of the line) and A′ (the end). X = 0 on the gun barrel plot is A.

Gridded Tops on the Plot

Interpolated top surfaces can be drawn over both views. Click Add Tops to Plot in the secondary toolbar and select either Welly's provided grids or your own user grids.

In Gun Barrel mode, each selected grid is sampled at the start of the gun barrel line, at the end, and at every intersection point, producing an interpolated top surface across the section.

In Trajectory mode, each selected grid is sampled at every survey station of one of the selected wells by default. To show tops for more than one well, select additional API numbers in the Filter Tops by API window. Tops in trajectory mode are most meaningful when the selected wells are landed perpendicular to formation strike.

Free accounts see Welly's Midland Basin grids; grids in other basins appear in the list but are marked and cannot be selected.

Symbologies

Wellbores default to green on the map and in the plots. Colours are edited in the wellbore Symbology window. There are two methods:

1. Basic style
2. From well headers

Basic Symbology

Applies one colour to every wellbore in the layer. Click Set Symbologies at the bottom of the window to apply.

Well Header Symbology

Colours individual wellbores from a selected well header field. A numeric field is binned into equal-range groups according to your bin count; a qualitative field is binned into unique values. If the bin count is smaller than the number of unique values, an "other" bin is created and the remaining wellbores share one colour.

Map Latency

If the map is slow, too many wells may be drawn at once. Reduce the number of active layers and make sure you are on a current browser.

Deleting Surveys

Navigate to Manage Data → Trajectories, select the survey files you want removed, and click Delete.

Formation Tops & Grids

Importing tops, correlating new ones, and rendering structural surfaces on the map.

Welly Grids vs. User Grids

The Source toggle in the grid section of the toolbar switches between Welly grids — structural surfaces we build and maintain — and User grids, which are the formation top sets you have imported or correlated yourself.

Welly grids are published for the Anadarko, Midland, Delaware, Williston and Gulf Coast basins. Free accounts have access to the Midland Basin grids; the other basins are listed but marked and cannot be selected. Current coverage is shown on the Grid Coverage page.

Importing Formation Tops

Formation tops are uploaded through Large Imports → Formation Tops. OG Welly expects a .csv containing:

• Latitude
• Longitude
• Top

You will be prompted to map your CSV's columns onto those fields. Top should be the true vertical depth of the top of the formation at that latitude and longitude. Do not use sub-sea TVD unless your directional surveys are also in SSTVD.

One file is one surface. Naming the .csv after the horizon it represents (for example "Wolfcamp XY.csv") is good practice, though you will be prompted for the surface name at import.

Creating Formation Tops

A new formation top group can be created in the Grid Data window: click Create, enter the name, and click Save. The new group then exists in your project.

Correlating Tops

New tops can be added to an existing group by picking them in the Cross Section module. With a cross section drawn, select your formation top group, click Correlate, and pick the top by clicking the appropriate position on each well log. Click Stop Correlating to save the new tops to your project.

Viewing a Grid Surface on the Map

Any formation top group with at least three top entries can be gridded and drawn on the map. Select the grid in the Grids section of the toolbar and the structure map renders. Contour Interval and Color Scheme adjust the display, and the Labels, Lines and Mesh toggles control contour labels, contour lines and the control point mesh.

Grid Mesh

Setting Mesh to On draws the xy control of the surface — the interconnection of the control points the contours were interpolated from. It is the quickest way to see whether an odd-looking contour is real structure or an artefact of sparse control.

Troubleshooting

If a selected grid does not appear on the map:

• Confirm the file imported: Manage Data → Fm. Tops.
• Open Grid Data in the middle pane (fetch your grids from the database first) and select the grid. You should see values in the Depth, Latitude and Longitude fields. If those are empty, delete the grid and re-import the .csv with the required fields mapped.
• A surface needs at least three usable control points. Rows with a missing coordinate or a missing top are dropped before interpolation.

Deleting Formation Tops

Navigate to Manage Data → Fm. Tops, select the files you want removed, and click Delete.

Well Logs

Importing LAS files, joining them to headers, cross sections, and StrataView.

Importing Digital Well Logs

Well logs are uploaded through Large Imports → Well Logs. OG Welly expects conventionally formatted .las files, with a UWI, a log header, mnemonics and curve values. If you have trouble importing:

• Confirm the correct Join Header was selected at import.
• Open Well Log Data to inspect what reached the database.
• Check the .las header before importing — a UWI / API number is required.

A batch may contain up to 1,000 .las files, and you may have two log import jobs running at once. The files are uploaded straight to storage from your browser, so a large batch does not have to pass through the application.

A corresponding well header .csv (the Join Header) is required to give each log a location. The header must contain:

• Latitude
• Longitude
• API Number

The API / UWI in each log header is matched against the API numbers in your well header, and the match is what gives the log its coordinates. You can confirm it worked by opening Well Log Data in the middle pane — the Latitude and Longitude fields should be populated.

Joining Log Locations

Locations are seeded automatically at import. If they are missing afterwards, open the Well Log Data window in the lower toolbar and click Refresh. OG Welly re-reads the join header defined at import and attempts to tie latitudes and longitudes to the logs.

Viewing Well Logs on the Map

Logs are placed on the map by filtering on mnemonic. Select one or more mnemonics from the Well Log Checklist in the map editor toolbar; any log containing all of the selected mnemonics appears as a red circle on the map.

Cross Section Module

Cross sections are drawn on the map between well logs. First make sure the logs you want are visible on the map. Then click Cross Section in the secondary toolbar and click New XS. Click your logs on the map one by one — a grey box populates with the API numbers as you go. Click Finish when done, then View to open the module. A light-blue line on the map shows the section line. Clear removes it.

Curve Symbology

Click Curve Symbology in the Cross Section toolbar. To shade a curve above or below a cutoff, enter a Shading Value, choose > or <, and pick a Fill Color. Top Depth and Base Depth set the displayed interval.

The curve scale is set with Log Scale: From and Log Scale: To, and can be made logarithmic with the logscale radio buttons.

Cross sections default to gamma ray ("GR"). Choose a different curve from the mnemonic dropdown.

Symbology definitions can be saved: click Save, name the style, and save. Saved styles are then available from the Curve Symbology dropdown.

Formation Tops on a Cross Section

Your formation tops can be drawn over the curves by selecting them under Tops in the Cross Section toolbar. OG Welly matches tops to logs on latitude / longitude and draws matches as dashed lines. Hover a dashed line to see which top it is.

StrataView Module

StrataView interpolates well log values along the trajectory of a horizontal wellbore. Three data types are required:

• A grid (formation tops)
• A directional survey
• A well log (.las) to act as the type log

Select a directional survey, a grid and a type log to run it. Your type log and your selected wellbore must both fall within the area of the gridded surface — a wellbore entirely outside the grid's control points cannot be hung on it, and StrataView will say so rather than draw a flat surface.

Where only part of the wellbore falls outside the control points, the nearest known top is carried out to those stations and the section stays continuous. This is normal for a well near the edge of a grid.

Log Downsample reduces the number of log samples plotted: a value of 2 uses every other value, 5 every fifth, and so on. Downsampling lowers latency at the cost of precision.

The measured depth slider along the bottom of the module selects the measured depth at which the stratigraphic position of the wellbore is interpolated onto the left-hand plot. The wellbore position at that depth is drawn as a white horizontal line on the well log plot.

StrataView can also colour the survey points by an MWD curve — see the MWD Logs section.

Deleting Well Logs

Navigate to Manage Data → Well Logs, select the logs you want removed, and click Delete.

MWD Logs

Measurement-while-drilling curves, used to colour the wellbore in StrataView.

What MWD Is Used For

MWD logs are used in one place: the StrataView module. They are not drawn on the map as their own layer, they are not used in the Cross Section module, and they are not used by the Production or Type Curve modules.

Their purpose is to give you the drilling-time measurement along the lateral, so the stratigraphic interpretation StrataView produces can be checked against what the bit actually read. The survey stations of the wellbore are coloured by the MWD curve value, which turns the trajectory into a log trace in its own right — where the curve changes character, you are seeing the bit enter or leave the target.

Importing MWD Logs

MWD logs are uploaded through Large Imports → MWD Logs, as .las files. Each file must carry an API / UWI in its header and must contain a depth curve — DEPTH, DEPT or DEP — alongside the measured curves.

Uploads are limited to 200 files at a time, and 50 MB per file. Re-importing a file for a well already in your project merges the new curves into that well rather than replacing it.

Using MWD in StrataView

1. Open StrataView and select your directional survey, grid and type log as usual.
2. Choose a curve from the MWD GR Curve dropdown. The dropdown lists the mnemonics available for the selected well, so it is empty if no MWD file matched.
3. Run the module. The survey points are coloured by the MWD curve value, sampled at the nearest MWD depth to each station.

The colour scheme is the same one selected for the rest of the module, including any user-defined colour rules, so the MWD-coloured trajectory reads on the same scale as the type log beside it.

Null values (-999.25) and non-finite values are dropped before colouring rather than being painted as real readings.

Manual Offset

Manual Offset shifts the plotted wellbore depth by a fixed amount, in the same units as your survey. It exists because MWD depth and wireline depth are referenced and measured differently, and a consistent tens-of-feet shift between the two is routine. Use it to tie the MWD trace to the type log when you can see that the character matches but the depth does not.

Finding Which Wells Have MWD

With a wellbore layer selected on the map, click highlight mwd in the Logs section of the map editor toolbar. Every well in that layer with a matching MWD file in your project is highlighted on the map. Clearing the wellbore selection clears the highlights.

Troubleshooting

• The MWD curve dropdown is empty. No MWD file in this project matched the selected well's API. Confirm the file imported under Manage Data, and check the UWI in the .las header.
• The curve is selected but nothing is coloured. The file needs a depth curve (DEPTH, DEPT or DEP) as well as the curve you selected. A curve with no depth to hang it on cannot be sampled.
• The colouring looks shifted against the type log. That is what Manual Offset is for.
• Everything is one colour. Check that the curve you picked is the one you meant — a constant or mostly-null curve will read as flat.

Production & Type Curves

Monthly volumes, Arps decline fitting, economics, and aggregate type curves built from saved forecasts.

Where Production Data Comes From

Production is used in two places: the Production and Type Curve modules, and the AI assistant, which uses it to answer questions about rates, cumulative volumes, decline behaviour and well ranking.

There are two sources, and which one you get depends on the selected wellbore layer:

• Your imported production, when one of your own wellbore layers is selected.
• Public RRC production, when OG WELLY is the selected wellbore layer. Oil combines oil and condensate; gas combines gas well gas and casinghead gas. These are allocated well-level volumes derived from lease-level filings — see the Public Data section.

Importing Production

Production is uploaded through Large Imports → Production as a .csv. You will be prompted to map four columns:

• API — matched on digits only, so formatting does not matter
• Producing Month — any recognisable date format
• Oil
• Gas

You are also asked to name the dataset. Re-importing under the same name replaces that dataset rather than duplicating it, which makes a monthly refresh straightforward.

Production Module

Production icon in the upper toolbar, or Production on the wellbore legend card.

Clicking Production on a well's legend card opens the module with that well already selected. You can also pick a well from the Wellbore dropdown inside the module, and choose Oil or Gas from the Type dropdown.

Actual monthly volumes are plotted as points. The dashed line over them is the Arps forecast.

The Timeline Slider and the Fit Window

The slider along the bottom of the plot sets the fit window — the range of months the decline is fitted to. This matters more than any other control: a well with a workover, a shut-in period or a ramp-up should not be fitted from first production. Move the left handle to where you want the decline to start and the curve is refitted from there.

The fit is a least-squares Arps fit over the whole window, and it re-runs whenever you move the slider or change the well or the commodity.

Arps Variables

Click Arps to open the fitted parameters — qi, di, b and dt. They are populated by the fit and are fully editable: typing a value overrides the fit and redraws the forecast, so you can accept the automatic fit or impose your own. dt is the terminal decline the hyperbolic switches to.

Economic Limit

The forecast is drawn out to whichever economic limit comes first: a rate limit (ecl_barrels for oil, ecl_mcf for gas) or a life limit in months (ecl_months).

Economics and NPV

With the forecast in place, the economics inputs drive the NPV card:

• price_barrels / price_mcf — commodity pricing
• NRI — net revenue interest
• LOE — lease operating expense
• prod_tax and av_tax — production and severance / ad valorem tax
• Interest Type — Royalty or WI, with its own NRI decimal

The card updates as you type. All of it is screening economics on a single-well decline forecast — flat pricing, no differentials, no capital.

Production Groups

A production group is a named set of saved forecasts, and it is the bridge between the Production module and the Type Curve module.

1. In the Production module, click group to open the group window.
2. Select an existing group, or click New Group…, name it, and click Create.
3. With a well fitted and a group selected, click Add to Group. The Arps parameters, the economic limits, the pricing, the tax and LOE assumptions and the interest type are all saved with the well.

Every field above is required at save time. If something is missing, the message names the field and nothing is written.

A saved group can also be exported: Export Production Report, select the group, click Export.

Type Curve Module

Type Curves icon in the upper toolbar.

The Type Curve module builds an aggregate curve from a saved production group. Select the Production Group and the commodity, and every well's forecast in the group is plotted together with the group's aggregate Arps fit. Hovering a well highlights it against the rest.

Normalization

The Normalize dropdown lists the numeric fields available on the well header joined to the group's wells — lateral length being the usual one. Selecting a field normalizes every well in the group to it, so wells with different completed lengths can be compared on the same basis.

The dropdown is populated from the header file linked to the group's wells, so it is empty if the group's wells have no joined header.

Aggregate Arps and Economics

The group's qi, di, b and dt are fitted across the group and, as in the Production module, can be overridden by typing. Commodity pricing feeds an NPV card for the type curve itself, which is the number you would carry into a development case.

Troubleshooting

• "No production data for this well." With one of your own layers selected, the well's API was not found in the production you imported into this project — check that the API column mapped correctly at import. With OG WELLY selected, the RRC has no allocated production on file for that API.
• The fit looks wrong. Move the left slider handle past the ramp-up, the workover or the shut-in. Almost every bad fit is a fit window problem.
• The forecast stops early. Check the economic limit rate and the months limit — the forecast is drawn to the first of the two.
• The Normalize dropdown is empty. The group's wells are not joined to a well header, or the header has no numeric fields.
• The type curve is empty. The selected group has no saved forecasts for the selected commodity — a group saved from oil fits has nothing to show under gas.