Wellbore Casing

the wellbore casing table describes the casing strings installed in a wellbore — the steel pipe sections lining the hole each record is one casing section with its depth interval and diameters prodx uses casing geometry for bottomhole pressure and flow modeling, particularly for annular and casing flow paths the unique constraint on casing entries is sourcewellboreid + sourceid variable data type unit of measure is nullable? default value description sourceid string no source id for the casing section from wellview wvcas table, idrec column from openwells cd assembly table, assembly id column sourcewellid string no source id for the well from wellview wvcas table, idwell column from openwells cd assembly table, well id column sourcewellboreid string no source id for the wellbore from wellview wvcas table, idrecwellbore column from openwells cd assembly table, wellbore id column topmd double ft yes 0 0 top measured depth of the casing section bottommd double ft no bottom measured depth of the casing section id double in no inner diameter of the casing from wellview wvcas table, szidnommincalc column od double in no outer diameter of the casing from wellview wvcas table, szodnommincalc column roughness double in yes 0 0006 absolute roughness coefficient of the casing material rundate datetime offset yes date the casing was run datetime offset (with timezone) in iso 8601 format example 2022 09 27t16 28 37 +0000 wellbore casing notes every well requires casing data wells with no casing data will fail a data integrity check, and the system will not compute values for them top measured depth notes if topmd is null, the system assumes 0 ft roughness notes if roughness is null, the compute engine applies 0 0006 in its place data integrity checks condition response any non nullable field is null or empty record rejected (sourcewellid, sourcewellboreid) does not match an existing wellbore row skipped partial success on bulk ingest rows referencing an unknown wellbore are skipped while the remaining rows are written the error response names each skipped row an error response therefore does not mean nothing was written common error messages api scenario error response add / upsert casing unknown wellbore casing with sourceid 'xxx' was skipped wellbore with sourcewellid 'xxx' and sourcewellboreid 'xxx' was not found