Importing Data into WellSpring - CSV file

Home > Other Topics > Importing Data into WellSpring - CSV file

Comma or tab delimited text data can be imported into WellSpring via a three step process. To bring up the import screen select "Tools - Import from CSV" from the main menu in your project. You can also access the import screen from the project tab:

Step 1

Specify a delimiter (tab, comma, or auto detect). Auto detect is recommended. Then Browse to your text file and click “Preview from file”. You can also copy the data to your clipboard (right click copy from a spreadsheet) then click “Preview from clipboard” to import the copied data.

Step 2

Setup import parameters; the configuration used in your last import will be presented as default.

First specify high-level settings:

Setting	Description
Skip first rows/columns	The number of rows at the top and/or columns on the left to ignore during import. The rows/cols that will be ignored are shown in the preview table with a gray background.
Scenario	The scenario to import into. If the imported well does not exist in this scenario, then it will be copied there during import.
Create missing facilities	If checked, any required Target Flow Facilities (see below) that do not exist will be automatically created as gas plants.
Date format	The format for all dates to be imported. All formats support dates of the format MMM-YYYY and QQ-YYYY.
User Data units	If user data is being imported in the header section, this setting indicates the unit system (metric/imperial) and scale (medium/large as defined by WellSpring).
Completion/Drilling capital type	The capital types to use for completion/drilling capital imported from the header section.

Next, using the drop-down selection boxes in the preview table (see below), identify the header rows and mark the start of production data. If you need additional row marker drop-down boxes, click the “Add new header row dropdown” link. The definitions for these are in the Row Marker Definitions table below.

Here is the import spreadsheet used in the above example: It can be downloaded here

Mandatory settings are shown in red bold. Exact valid values are shown italic.

Row Marker Definitions

Setting	Description
Skip	Ignore this row.
Asset Name	The name of the well in this column. This must be the first importable row in the file. If this cell is blank, the previous name, if any, will be used.
Asset Sub Type	The sub type of the well. Valid values are: OilWell, GasWell, Injector.
Asset Start Date	The start date of the well being imported. If not specified, the start date of the project will be used.
Target Flow Facility	The facility the imported well flows to. If the well already exists and flows to a different facility, this setting will be ignored.
Product	This field is only required if production, capital, or opcost data is being imported. This line must occur in the file before the Units line. The valid values for this setting are: The product type: Oil, Gas, Water, Ethane, Propane, Butane, Sulfur, InjectedWater, Cond. Date. A “Date” column lists the dates of production data in columns to the right for the same well and production set. Cumulative volume; valid values are: CumOil, CumGas, CumWater. Production in the columns to the right are treated as rate-cum production values based on this column’s cum volumes. capital:<capitalname> where <capitalname> is replaced with the name of capital type defined in the current model. opcost:<opcostname> where <opcostname> is replaced with the name of an opcost type defined in the current model.
Units	This setting is only required if a Product line has been identified. It specifies the unit string of the production data in this column. Examples are: e3m3, bbl, mstb, e6m3/d, m3/e6m3, %. Mixed unit systems and scales are supported.
Completion Days	Drilling Tab: number of days for well completion
Completion Cost	Drilling Tab: cost for well completion
Drilling Days	Drilling Tab: number of days for well drilling
Drilling Cost	Drilling Tab: cost for drilling well
Move Days Before	Drilling Tab: Number of days to move before drilling
Move Days After	Drilling Tab: Number of days to move after drilling
Production Set Name	The name of the production set to import production data into. If not specified, the Default set will be used.
Production Delay Days	Drilling Tab: Number of days to delay production after drilling
Production Data Start	This setting is only required if a Product line has been identified. This marks the first row of production data. The data in the column will be imported either to its end or until the first blank cell is encountered. Exception: capital and opcost data is expected to be sparse, so an opcost or capital column is imported until its end or until an entire blank row in the import file is encountered.
UserData:<userdataname>	This marks this single row as containing a value to be imported into a scalar user-defined data variable, where <userdataname> is to be replaced with name of user data variable.

Notes on importing production

The columns of the import file are processed from left to right. It is expected that all columns for each production set of a well will be grouped together. If a Product column of type Date or Cum (“CumOil”, “CumGas”, or “CumWater”) is encountered, that Date/Cum column will be applied to all following columns until either: i) a different asset name or production set name is encountered, ii) another Date column is encountered, or iii) a Cum column is encountered. Only one Cum column is supported for each well/production set combination. The existence of a Date or Cum column changes how the following production columns are interpreted:

If a production column is ordered before a Date or Cum column, then the data is treated as monthly data starting from the start date of the well. The production data is imported as either a daily rate or a monthly volume, where the distinction is made based on the specified units. If the “production” is either capital or opcost, the data is imported on the 1st of the month.

If a Date column precedes a production column for a well, then the production data is again either a rate or a volume, but the dates of the values are taken from the preceding date column. The dates must be in increasing order, but need not be monthly or evenly spaced:

If the production is supplied as rates (date1,rate1; date2,rate2; date3,rate3; …), then a daily rate of rate1 is imported for the time period from date1 through date2. If the dates are mid-month, then the production rates will be imported into WellSpring as a daily-weighted average of specified for each month.
If the production is supplied as monthly volumes, then the volumes are converted to daily rates and monthly volumes are calculated and imported.
If the “production” is either capital or opcost, then the data is imported on the 1st of the month of the corresponding date.

If a Cum column precedes a production column, then the production data is expected to be cum-rate, cum-ratio, or cum-cut data and is imported unmodified into WellSpring. If a Cum column precedes a capital or opcost column, then the capital/opcost data is imported as if there was no Date or Cum column, as in option 1 above.

Once the import is configured, click “Validate”.

If errors were encountered in the validation step, the Step 2 interface will be displayed with error messages shown in red at the top. Either correct the import settings, or click the “Back to step 1” link to load a different import file.

Step 3

Once the import file has been successfully validated, the Step 3 interface will be displayed. Summary information like number of lines found in import file and number of wells to be created will be presented along with any warning messages.

To complete the import process, click “Import”. Otherwise click “Back to step 2” to adjust the import configuration or “Back to step 1” link to load a different import file.

The sample import file shown in the examples can be downloaded here

A sample csv file with imported capital and opex can be downloaded here