Bringing in your data
| Source | Supported |
|---|---|
| LAS | 2.0 and 3.0, wrapped and unwrapped data, header items (well name, UWI, company, service company...) |
| WITSML | 1.3.1.1, 1.4.1.1 and 2.0 trajectories; 1.x formation markers and depth logs; live (growing) logs through your WITSML store |
| CSV | a complete built-in mapping (wells, strings, components, intervals, tops, survey, hole sections...) |
| PPDM and other databases | through mapping profiles (a PPDM 3.9 starter profile is included - verify column names against your schema) |
Units are read from the data (for example WITSML angles in radians or degrees, depths in m, ft or US survey feet) and converted exactly. Problems never stop an import silently: every skipped or unmapped item is listed as a warning.
Change history
Changes to a well are recorded with who made them, when and why: edits made in the schematic, and the differences between two versions of a well (for example before and after a workover). The history is saved with the well, can be exported as a spreadsheet (CSV), and the comparison of two well states shows the author and date of each change.
Very large log files
LAS files are read as they stream in, so file size is not limited by memory. For an overview of a very long or finely sampled log you can ask for a bounded number of samples: the log is reduced by keeping, for each small depth interval, the lowest and highest value of every curve - peaks such as gas shows or washouts stay visible. For interpretation use the full-resolution log. You can also read only some curves or a depth interval.
Exporting your data
Wells can be written back out as CSV (in your own database layout, through its mapping profile), LAS 2.0 or 3.0, and WITSML 1.4.1.1 (surveys, formation tops, logs). Exported files read back without loss. WITSML 1.4.1.1 has no field for fluid contact types, so contacts are exported as named markers.
Your codes
Data models use their own codes ("PKR", "PROD CSG", "OIL WATER CONTACT"). A vocabulary file maps them to the standard codes the views understand. A code that is not mapped is reported, never guessed.
{
"name": "PPDM-style source codes (sample - replace with your data model's code lists)",
"domains": {
"componentType": {
"PKR": "PACKER_PERMANENT", "PKR-PERM": "PACKER_PERMANENT", "PKR-RET": "PACKER_RETRIEVABLE", "PKR-HYD": "PACKER_HYDRAULIC",
"SSSV": "SSSV_TUBING_RETRIEVABLE", "TRSV": "SSSV_TUBING_RETRIEVABLE", "WRSV": "SSSV_WIRELINE_RETRIEVABLE",
"NIP": "NIPPLE_LANDING", "NIP-NOGO": "NIPPLE_NOGO", "GLM": "GAS_LIFT_MANDREL", "SSD": "SLIDING_SLEEVE", "WEG": "WIRELINE_ENTRY_GUIDE",
"LNR-HGR": "LINER_HANGER", "LTP": "LINER_TOP_PACKER", "FS": "FLOAT_SHOE", "FC": "FLOAT_COLLAR", "BP": "BRIDGE_PLUG", "CR": "CEMENT_RETAINER",
"THS": "WELLHEAD_TUBING_HEAD", "CHH": "WELLHEAD_CASING_HEAD", "TREE": "XMAS_TREE", "HGR": "TUBING_HANGER"
},
"stringKind": { "COND": "Conductor", "SURF CSG": "Surface", "INT CSG": "Intermediate", "PROD CSG": "Production", "LNR": "Liner", "TBG": "Tubing", "CT": "CoiledTubing" },
"itemStatus": { "ACTIVE": "Installed", "IN HOLE": "Installed", "PULLED": "Removed", "P&A": "Abandoned", "PROPOSED": "Planned" },
"intervalType": { "PERF": "PERFORATION", "OPEN HOLE": "OPEN_HOLE" },
"contactType": { "OIL WATER CONTACT": "OWC", "GAS OIL CONTACT": "GOC", "GAS WATER CONTACT": "GWC", "FREE WATER LEVEL": "FWL" },
"lithology": { "SH": "shale", "SS": "sandstone", "LS": "limestone", "DOL": "dolomite", "ANHY": "anhydrite", "CLST": "claystone" },
"curveMnemonic": { "GAM": "GR", "GRC": "GR", "GR_EDTC": "GR", "RDEP": "RT", "RMED": "RES", "DEN": "RHOB", "NEU": "NPHI", "DTC": "DT" }
}
}
Your layer names
Companies and countries name the same formation differently ("Top Draupne", "DRAUPNE FM", "Draupneformasjonen"). A lexicon maps all of them to one unit. The views then show the name in your language, keep the original name for traceability, and correlate wells by unit - so wells from different operators line up.
{
"name": "Kuwait formations (sample - verify names and Arabic spellings with your geoscience standards)",
"stripPrefixes": [ "Top ", "Base ", "TOP ", "BASE " ],
"units": [
{ "id": "DAMMAM", "name": "Dammam Formation", "aliases": [ "DAMMAM FM" ], "localNames": { "ar": "تكوين الدمام" }, "lithology": "limestone" },
{ "id": "RUS", "name": "Rus Formation", "aliases": [ "RUS FM" ], "localNames": { "ar": "تكوين الرص" }, "lithology": "anhydrite" },
{ "id": "UMM_ER_RADHUMA", "name": "Umm Er Radhuma Formation", "aliases": [ "UER", "UMM ER RADHUMA FM" ], "localNames": { "ar": "تكوين أم الرضمة" }, "lithology": "dolomite" },
{ "id": "MISHRIF", "name": "Mishrif Formation", "aliases": [ "MISHRIF FM" ], "localNames": { "ar": "تكوين مشرف" }, "lithology": "limestone" },
{ "id": "AHMADI", "name": "Ahmadi Formation", "aliases": [ "AHMADI FM" ], "localNames": { "ar": "تكوين الأحمدي" }, "lithology": "shale" },
{ "id": "WARA", "name": "Wara Formation", "aliases": [ "WARA FM" ], "localNames": { "ar": "تكوين وارة" }, "lithology": "sandstone" },
{ "id": "MAUDDUD", "name": "Mauddud Formation", "aliases": [ "MAUDDUD FM" ], "localNames": { "ar": "تكوين مودود" }, "lithology": "limestone" },
{ "id": "BURGAN", "name": "Burgan Formation", "aliases": [ "BURGAN FM", "Burgan Fm." ], "localNames": { "ar": "تكوين برقان" }, "lithology": "sandstone", "color": "#c8a000" },
{ "id": "SHUAIBA", "name": "Shuaiba Formation", "aliases": [ "SHUAIBA FM" ], "localNames": { "ar": "تكوين الشعيبة" }, "lithology": "limestone" },
{ "id": "ZUBAIR", "name": "Zubair Formation", "aliases": [ "ZUBAIR FM" ], "localNames": { "ar": "تكوين الزبير" }, "lithology": "sandstone" },
{ "id": "RATAWI", "name": "Ratawi Formation", "aliases": [ "RATAWI FM" ], "localNames": { "ar": "تكوين الرطاوي" }, "lithology": "limestone" },
{ "id": "MINAGISH", "name": "Minagish Formation", "aliases": [ "MINAGISH FM" ], "localNames": { "ar": "تكوين المناقيش" }, "lithology": "limestone" },
{ "id": "NAJMAH", "name": "Najmah Formation", "aliases": [ "NAJMAH FM" ], "localNames": { "ar": "تكوين النجمة" }, "lithology": "shale" },
{ "id": "MARRAT", "name": "Marrat Formation", "aliases": [ "MARRAT FM" ], "localNames": { "ar": "تكوين مرات" }, "lithology": "limestone" }
]
}
The sample lexicons and code lists are illustrative. Have your geoscience and data teams verify names, spellings and codes before use.
Your database layout
A mapping profile tells the software which tables and columns hold wells, strings, equipment, tops and surveys, and in which units. Your administrator can place company-specific profiles in the environment's profile folder; they are used before the built-in ones.