# Operators and reference lists

Source: https://developers.novilabs.com/data/tables/reference/

> Operators, operator contacts, the basin list, and data lineage.

Views live in `NOVI_DATA_ACCESS.NOVI_WELLS`. Column descriptions are from the Wells data dictionary, release 26.4.3. Type is the data model's logical type, and unit appears where the model declares one. For Snowflake column types, query `NOVI_DATA_ACCESS.INFORMATION_SCHEMA.COLUMNS`.

## OPERATOR

A company that operates wells. One row per company. Its registrations, and the contact details filed with them, are operator\_contact rows keyed by operator\_id.

| Column | Type | Unit | Description |
| --- | --- | --- | --- |
| `OPERATOR_ID` | integer |  | Surrogate key for the company, derived from name. |
| `WEBSITE` | string |  | Operator website URL. |
| `TICKER` | string |  | Stock ticker symbol. NULL when the company is not publicly traded or the ticker is unknown. |
| `IS_PUBLIC` | boolean |  | Whether the organization is a publicly traded company. |
| `NAME` | string |  | The company's name, verbatim as the source gave it. May contain trailing whitespace. Unique, and the value operator\_id is derived from. |
| `SOURCE_ID` |  |  | Foreign key to source.source\_id for data lineage. |
| `CREATED_AT` | timestamp |  | Timestamp the operator record was created. |
| `UPDATED_AT` | timestamp |  | Timestamp of the most recent update. |

## OPERATOR_CONTACT

How to reach an operator about a particular jurisdiction, and the registration that jurisdiction issued. A row is either a registration a regulator issued, or an operator's presence in a jurisdiction with no registration behind it; is\_registered says which, and external\_operator\_id is empty on the second kind. Because the unregistered case is a row rather than an absence, a lookup from an operator to a jurisdiction distinguishes 'no registration exists' from 'not present here'.

| Column | Description |
| --- | --- |
| `OPERATOR_CONTACT_ID` | Surrogate key for this registration or presence. |
| `OPERATOR_ID` | Foreign key to operator.operator\_id: the company this row belongs to. Part of the natural key. |
| `EXTERNAL_OPERATOR_ID` | The registration identifier the regulator issued. Absent where no registration exists; required where is\_registered is true. Part of the natural key. |
| `COUNTRY` | ISO 3166-1 alpha-2 country of the jurisdiction in jurisdiction\_reported. Not the mailing country, which is not modelled. Part of the natural key. |
| `JURISDICTION_REPORTED` | The state or province that issued the registration, or in which the operator is evidenced. Part of the natural key. |
| `IS_REGISTERED` | TRUE where a regulator issued this registration, FALSE where only activity in the jurisdiction attests to the operator's presence. The two row kinds are different claims, 'this regulator issued this registration' versus 'this operator is evidenced here and no registration exists', and this column is what tells them apart; external\_operator\_id is empty on the second kind. |
| `OPERATOR_REPORTED` | The operator's name as this registration recorded it, or as the activity source reported it. Filed spellings differ between a company's registrations, so this is the name on THIS row rather than the company's canonical name, which is operator.name. |
| `ADDRESS` | Mailing address, first line. |
| `ADDRESS2` | Mailing address, second line, suite, floor or unit. |
| `CITY` | Mailing address city. |
| `ADDRESS_STATE` | Mailing state or province. Where post is sent, which may differ from jurisdiction\_reported, the jurisdiction that licensed the operator. |
| `POSTAL_CODE` | Mailing postal code, a US ZIP or ZIP+4, or a Canadian postal code. The mailing country is not modelled, so both forms are accepted and neither is tied to country, which is the licensing jurisdiction's country rather than the address's. |
| `PHONE` | Contact telephone number as reported. |
| `EMERGENCY_PHONE` | Emergency contact telephone number as reported. |
| `SOURCE_ID` | Foreign key to source.source\_id for data lineage. |
| `CREATED_AT` | Timestamp the record was created. |
| `UPDATED_AT` | Timestamp of the most recent update. |

## BASIN

Reference list of basins and subbasins.

| Column | Type | Unit | Description |
| --- | --- | --- | --- |
| `BASIN` | string |  | Name of the basin, e.g. "Permian" |
| `SUBBASIN` | string |  | Name of the subbasin, e.g. "Midland" |
| `SOURCE_ID` |  |  | Foreign key to source.source\_id for data lineage. |

## SOURCE

Data lineage dimension. One row per (system, collection, source\_file, source\_path) lineage tuple, where source\_file carries the upstream dataset name (e.g. 'US\_Horizontals', 'US\_Onshore', 'Canada'). Every base fact and dimension row carries a source\_id resolving to exactly one row here, and rows from different datasets of the same upstream table receive distinct source\_ids. ingested\_at carries the date and time of the bulk export that last loaded this lineage tuple, so it moves with each export.

| Column | Description |
| --- | --- |
| `SYSTEM` | Originating system name (e.g., 'regulator', 'internal\_ops'). |
| `INGESTED_AT` | When the data was ingested into the platform. |
| `COLLECTION` | Source collection or dataset name within the originating system. |
| `SOURCE_FILE` | Upstream dataset name carrying the bulk-export provenance for this row (e.g. 'US\_Horizontals', 'US\_Onshore', 'Canada'). Names the dataset rather than a single file, because this schema's lineage is tracked per dataset. |
| `SOURCE_PATH` | Path or URI to the source data file or object. |
| `SOURCE_ID` | Deterministic integer hash of the canonical lineage payload. Serves as both primary key and dedup key. |
| `CREATED_AT` | Timestamp the source record was created in this system. |
| `UPDATED_AT` | Timestamp of the most recent update to this source record. |
