ComboCurve: Import ARIES Database

ComboCurve: Import ARIES Database

Import ARIES Database

For a video tutorial on import/exporting and QC tieouts of econ see the following article - ComboCurve: ARIES Conversions
Also to see items unsupported see the following article - ComboCurve: ARIES Import/Export Conversions – Currently Unsupported Items

Supported Databases

The database must be a .accdb or .mdb and must be unzipped. If you need assistance with the database please check out the following article - ComboCurve: ARIES - Preparing and Transferring Access databases (.accdb or .mdb).

How to Import an ARIES Database

To import a database click on the hamburger icon at the top left in the platform and select Data Import.


Next click +Create Data Import and New ARIES Import (.accdb or .mdb)




When you import a database it will always import as a new project. You can give the import a reference name but note that this is not the name of the project, only a name that can be easily referred to if it is ever needed to refer back to for mappings, etc at a later date.  Leaving the default-date-time-stamp is fine at this step. Click Create. 




Then the import screen will appear and it is a 3-step process: Upload, Mapping and Import.  These are described below and you can move from one to the other as you satisfy each one.

1. Upload

Then upload the database (.accdb or .mdb) by dragging and dropping or click select from computer. 

Note that just because a file is Access, it might not be a valid ARIES project so review in ARIES or send to CC for review via a ticket submission if an error is given. 

This is optional but on the box on the right, you can also (at the time of upload) attach a valid ARIES "OUTSIDEFILE" (usually with a ".A" extension) that is referred to via a FILE keyword in ARIES economics lines and contain things like prices, differentials, production taxes that can be edited outside of ARIES and/or Access.  These must be zipped together even if it is only a single file.

When ready, denoted by the uploaded file name appearing in the box above, click on the blue upload button. A progress bar will appear to show transfer progress in the box and then a green bar at the top to show extraction progress.  This may take some time.



2. Mapping


Once finished, the progress selection will move to Mapping which itself is broken up into 3 sections: Headers, Production Data (Monthly) and Production Data (Daily).  All three must be satisfied to move on.  



The items on the left are ARIES Headers and CC Headers are on the right.  You can drag and drop either direction to map headers for the contained database fields for all included wells. 

Notes
ARIES PROPNUM auto-populate to CHOSEN ID and also ARIES ID so no need to map those. 

Also optional is whether you want/need to map any other header.  Only items highlighted in purple MUST be satisfied such as Surface Longitude when Surface Latitude is mapped (ie, you must have a Long to match the Lat).  The funnel icons at top of each section allow selecting/deselecting only those fields that have already been mapped or conversely that have yet to be mapped.  This makes it easier to see what you have already done or pare down to what you need to still do.  You can also type in search fields to view ONLY desired fields to map to make it easier to find desired matches.


There are controls at the top for mapping:
  1. MAP SUGGESTED - This is a great place to start!  Click this and all exact matches on header names will be auto-mapped (special characters such underscores and periods are treated as spaces) and many other obvious selections are made automatically
  2. MAP DATA SNAPS - this can be used to find macros used in the database AC_Economic table from the AC_Property table and can help create models upon import with Data Snaps (see below for more information)
  3. RESET - start over mapping from scratch
  4. SAVE - Save the mappings you have made currently to be reused on subsequent db imports (name appropriately for later recall)
  5. LOAD  - Pull a saved mapping to be reused here on this db import
  6. EXPORT - Export the mappings to a .xls file to disseminate or keep a permanent record

Notes
Map Data Snaps
This feature will find macros in the AC_Economic Table that reference headers in the AC_Property table which can create models as Data Snaps on import. To use this feature you must FIRST use Map Suggest and THEN Map Data Snaps. 


Once you are happy with your header mappings, you can move on to the Monthly or Daily Production sections.  These also auto-map PROPNUM to Chosen ID but unlike headers, at least one selection must be made for Oil, Gas or Water.  Caveat: some ARIES dbs use different names for modeled production such as GAS, SOLD_GAS, PRODUCED_GAS, etc so take care in mapping the streams that represent the forecasted projects used for economics into the CC defaults.


If you would like to change, update, or add headers you can after the import by doing a Regular Import through Data Import into the existing project created. To obtain these headers from PHDWin to do this you will need to export the tables as csv files from the Access Database.


Once Finished on all three sections, click Next at the bottom, right of the screen to move on to the next section.

3. Import

This is the area to make selections for the project as to what will be imported. 



Enter the ComboCurve Project Name in the field. This will be the official project name

By default, ALL wells housed in the Access db will be imported.  On the CC Forecast set and/or Scenario(s), wells may or may not show up there depending on whether they have valid data in those areas.  If you want to add a well that has no ARIES forecast to the forecast set, that may be done by editing the forecast set after import for instance.

  1. Select Scenarios - You can select one (recommended) or more scenarios to be brought into the project.  The number allowed is up to 10 but is based on the size of the project that is being imported.  Very large projects may limit down to a minimum of 2 but subsequent uploads may be combined with "CC Merge Project", etc.  As can also subsequent imports of forecasts via scenario or ARIES Econ Data (.txt) uploads. 
  2. Select Setups - You are only ever allowed a single setup for any db import.  These house things such as Aggregation Dates (ARIES Effective Dates), etc that can change project economics but are easily re-created in most instances by CC General Options selections in the scenario.  In some cases, ARIES has common or default lines housed in Settings that can make large changes to the db.  This may be re-modeled via other techniques in CC.
  3. Only Import forecast - If you are only interested in bringing in the forecasts (along with any historical production), this will speed up import.  This button is for import via MS Access imports whereas .txt imports can be done as described above also.
  4. Create ELTS on Import - This function is feature-flagged for limited release as is is in beta testing at the moment.  It makes CC ELTs (Embedded Lookup Tables) from ARIES SIDEFILES and LOOKUPS rather than flattening those values to more simple economics lines.  This can be troublesome due to the disparate nature of the two programs but CC will continue to develop techniques to make this more robust.

Finally, click Import in right bottom corner.  Progress can be viewed in the bell icon at the top-right of the screen.  Very large and complex dbs may take some time to complete and occasionally are too large to process in the most extreme cases.  If that happens, submit a ticket and we can review and help facilitate import.

Once completed, metrics on the import will appear on what was imported. Note that "Failed" production is nothing to worry about since it just denotes production PROPNUMs with NULL records (no valid production or zero placeholders). If any errors were encountered during the process which the handler could report on, you will see DOWNLOAD ERROR REPORT no longer grayed out.  This can be downloaded and analyzed in Excel.  However, economic comparison between the two programs is a much better way to analyze and QC so see the Knowledge Base for files needed to facilitate this as well as training videos on how-to. Finally, once imported, CC "lands" on the newly imported project so you can navigate to any of the modeled items to review, run econ, edit models, etc.  


    • Related Articles

    • ComboCurve: ARIES Import/Export Conversions – Currently Unsupported Items

      The current version of the front-end ARIES import interface handles the majority of ARIES database imports and exports. Some of the more complex and less commonly used syntax, especially certain overlay definitions, might not be currently handled, ...

    • ComboCurve: ARIES - Importing and Exporting Forecasts via .txt in the Forecast Module

      Importing and Exporting Forecasts to ComboCurve from ARIES Importing Forecast to ComboCurve From ARIES Here's a video showing the workflow: https://www.loom.com/share/ff233c5af4c34e7fa33db9711dd5a8e5 ComboCurve has a method to ingest forecasts (only, ...

    • ComboCurve: ARIES - Preparing and Transferring Access databases (.accdb or .mdb)

      Preparing and Transferring ARIES Access databases (.accdb or .mdb) General Size Limits ComboCurve has full support for ARIES (MS Access databases) and PHDWin imports. Feel free to submit a ticket and a Customer Success Representative can help in the ...

    • ComboCurve: Export Scenario to ARIES

      Export Scenario to ARIES When exporting there are two types of exports Exports entire contents of economics into an MS Access database for use in ARIES, or A CSV file that can be copied into the AC_ECONOMIC table and a TXT file that can be imported ...

    • ComboCurve: PHDWin Scenario Import

      PHDWin Scenario Import Note: For a video tutorial on importing/exporting and QC tieouts of econ, see the following article - ComboCurve: PHDWin Conversions PHD to PHZ To import a PHDWin project into CC the file must be a PHZ file. A PHZ is the PHDWin ...