| Live Search | ||||||
|---|---|---|---|---|---|---|
|
...
For the best results, it is recommended the Asset Utilities steps are run in the following order:
Accessing Asset Well Utility | Access under menu option User Processes → Asset Utilities → Wells |
Run Extract Public Data | Well data is downloaded from the industry source (IHS or gDC) and is compared to existing wells. New wells are also found. This step can take a while depending on your company size. Note: This step can be skipped if the review of the wells has not been completed from the last time the extract was run. Do not run this step if you have accepted wells but have not done the Update step as the wells will be moved back to the pending New Well folder if the public data is run again. Note: Validate step is run along with the Extract step. |
Run Error Summary | The Error Summary will list all (New and Updated Wells) distinct errors. All code table issues and errors should be fixed in either the Translate table or the Validation tables. |
Run Validate Step | This step will verify the data to the Translate and CS Land validation code tables. If Errors on the Error Summary were fixed, run the Validate Step again to confirm all issues have been addressed. Run the Error Summary report and Validate steps as many times as necessary to ensure there are no code table issues or errors. Once there are no errors, proceed to the Update step. Running the Validate step moves any accepted new wells and accepted update wells into the accepted folders. If Code table or errors on new wells will appear in the error summary when the new wells are in the accepted folder |
Review Wells | Open up Well Lists to accept, ignore the well updates. |
Run Validate Step | Running the Validate step will move any accepted new wells and accepted update wells into the accepted folders. If Code table or errors exist on new wells they will appear in the error summary when the new wells are in the accepted folder. The Validate step should be re-run after the Review step. This will capture any errors on any new wells or updated fields that were previously set to Pending. Re-Run Error Summary:
|
Run Update | The Update will update the CS Land Well module for Wells with no errors. Normally, this step would not be run until after you have reviewed your Updates and/or New Wells in the Review process. The Update step will:
|
Run Reports | At a minimum, it is recommend to run these two reports at the end of the process. Additional reports are available and listed below.
Save report as a PDF or XPS and save to an Excel file for future (audits) reference. Hint: Add a date stamp to the file name “ddmmmyyy” to easily identify the specific run in the future if required. |
Reports
There are additional optional reports that can be run:
...
The grid below shows the functionality of the different columns.
Column | Values | Description | Comment |
|---|---|---|---|
Table | N/A | This will either be the CS W_DETAIL1 or W_DETAIL2 table | |
Column/Well Source Column | N/A | This is the column name in the W_DETAIL1 or W_DETAIL2 table. | Anything that is bold on the screen is a mandatory field. See chart below where mandatory are highlighted in green. All fields in the W_DETAIL tables are included even though some cannot be updated by the utility. |
Include | Yes, No | If Yes is selected then the field will be updated by the Asset Utility | If the chart below says Optional then the field is not mandatory and you can either select Yes or No. If the chart below says Mandatory then Yes must be selected. If the chart below says No, then No should be selected. The field cannot be updated by the utility, highlighted in yellow. Note: If Include = No and Preference = 'Use CS*', updates are still excluded. |
Translate | Yes, No | If Yes is selected, Translate table or CS code tables are used as a cross-reference to populate the correct code | Used to indicate whether or not to translate data in this column before putting the value into CS Land. Only columns flagged by Yes will be translated regardless of the entries in the translate table (N will ignore any entries in the translate table) Use the chart below to determine if Yes should be used. If there is a Yes* in the chart below then the Load Rules tab will determine if a translation of codes is done. Many of the industry source fields are dates, numbers, or text so a translation is not required. |
Update Preference | Use Source, Use CS or Manual Review | If include is Yes then this will indicate how the column will be updated. Mandatory non Industry fields would use CS as the source and default values are required | This flag is to indicate the user preference on any updates. If Use Source, it will always update CS Land with the source data or set to the Default. Note: non operated wells default to Use Source. If Use CS, it never updates and always uses the input from CS Land or set to the Default If Manual review is selected, it will show the proposed update and allow the user to Accept or bypass (default is bypass) |
Audit | Yes or No | Fields can be audited by selecting Yes | This flag is to indicate if an audit record is to be kept for this column. Reports can be used to show the old and new values for any audited fields |
Default Value | Null or has a value | See the grid below for Mandatory fields | Default values are used on new wells only and are used mainly for Mandatory fields if there is no data in the industry source. I.e. Admin Company, Area, Division, etc. But can be used on any column. There are fields that are mandatory that cannot be sourced from industry data so default values are required. This will show Use CS* as the Update preference in the chart below. Table defaults are setup by P2 but can be changed to meet client business requirements. |
Table | Column | Include | Translate | Update Preference | Default Value |
|---|---|---|---|---|---|
w_detail1 | abandoned_date | Optional | No | Use Source | |
w_detail2 | accounting_project | No | No | Use Source | |
w_detail1 | admin_company | Mandatory | No | Use CS* | Default Required |
w_detail1 | area | Mandatory | No | Use CS* | Default Required. Suggest WELLUTIL |
w_detail2 | bounds | Mandatory | No | Use Source | Suggest 0 |
w_detail2 | bounds_direction | Mandatory | No | Use Source | Suggest E |
w_detail1 | completion_date | Optional | No | Use Source | |
w_detail1 | confident_flag | Mandatory | No | Use Source | Suggest N |
w_detail2 | contract_operator | No | No | Use Source | |
w_detail1 | direction_drilled | Mandatory | No | Use Source | Suggest N |
w_detail1 | district | No | No | Use Source | |
w_detail1 | division | Mandatory | No | Use CS* | Default Required. Suggest WELLUTIL |
w_detail2 | dsu | Mandatory | No | Use CS* | Suggest 0 |
w_detail2 | dsu_uom | Mandatory | No | Use CS* | Suggest H |
w_detail2 | expiry_date | No | No | Use Source | |
w_detail2 | facility | No | No | Use Source | |
w_detail2 | field | Optional | Yes* | Use Source | |
w_detail1 | file_status | Mandatory | No | Use CS* | Suggest WELLUTIL |
w_detail1 | govern_agmt_oper | No | No | Use Source | |
w_detail1 | government_status | Optional | Yes | Use Source | |
w_detail2 | govt_unit_code | Optional | Yes | Use Source | |
w_detail2 | ground_elevation | Mandatory | No | Use Source | Suggest 0 |
w_detail1 | injection_date | Optional | No | Use Source | |
w_detail2 | kelly_bushing_elev | Mandatory | No | Use Source | Suggest 0 |
w_detail2 | lahee_class | Optional | No | Use Source | |
w_detail1 | last_prod_date | Optional | No | Use Source | |
w_detail1 | lessor_type | No | No | Use CS* | |
w_detail2 | licence_date | Optional | No | Use Source | |
w_detail2 | licence_number | Optional | No | Use Source | |
w_detail2 | metes | Mandatory | No | Use source | Suggest 0 |
w_detail2 | metes_direction | Mandatory | No | Use Source | Suggest N |
w_detail1 | on_production_date | Optional | No | Use Source | |
w_detail1 | payout_date | No | No | Use Source | |
w_detail1 | Penalty | Mandatory | No | Use CS* | Suggest N |
w_detail2 | plug_back_depth | Mandatory | No | Use Source | Suggest 0 |
w_detail2 | Pool | Optional | Yes* | Use Source | |
w_detail2 | producing_zone | Mandatory | Yes | Manual Review | Suggest UNDEFINED |
w_detail2 | projected_depth | Mandatory | No | Use Source | Suggest 0 |
w_detail2 | Reserve | No | No | Use Source | |
w_detail1 | rig_release_date | Optional | No | Use Source | |
w_detail1 | shutin_date | No | No | Use Source | |
w_detail1 | shutin_reason | No | No | Use Source | |
w_detail1 | spud_date | Optional | No | Use Source | |
w_detail1 | status_date | Mandatory | No | Use CS* | Suggest sysdate |
w_detail2 | surface_location | Optional | No | Use Source | |
w_detail2 | target_zone | Optional | Yes | Use Source | |
w_detail2 | total_depth | Mandatory | No | Use Source | Suggest 0 |
w_detail2 | total_depth_zone | Optional | Yes | Use Source | |
w_detail2 | true_vert_depth | Mandatory | No | Use Source | Suggest 0 |
w_detail2 | unit_of_measure | Mandatory | No | Use CS* | Suggest M |
w_detail1 | well_licensee | Mandatory | Yes | Manual Review | Suggest WELLUTIL |
w_detail1 | well_name | Mandatory | No | Manual Review | Suggest UNKNOWN |
w_detail1 | well_status | Mandatory | Yes | Manual Review | Default required. Suggest WELLUTIL |
w_detail1 | well_status_date | Mandatory | No | Manual Review | Suggest sysdate |
w_detail1 | well_type | Mandatory | Yes | Manual Review | Default required. Suggest WELLUTIL |
Exclude Units Tab
Enter unit codes into this table for new unit wells that are not to be populated in the Well module. This will exclude any new wells with the government unit code. When the code has been entered, the Well Asset Utility will no longer display the new unit wells for this unit in the New Wells folder.
An example of when the exclude unit functionality would be used is when a unit has been sold and you no longer want new unit wells added. Note: Unit code must exist in the CS Land Unit code table even if to be ignored. This will be a company by company business decision.
...
Ignore Wells Tab
Wells entered into this table will not come into the Utility process unless they are de-selected. Users can manually maintain this table to ignore wells from source for various reasons.
Note: The Ignore Wells functionality only ignores new wells from being added. You cannot use the ignore wells for UpdateWells.
Also, Wells set to Ignore in the Review process will automatically be added to this table after the Update step is run.
...
UWI = Identifies the well to ignore
Reason = Add the reason the well is being ignored
Review Date = Enter the date to review this well. Maybe in a delay mode and may not have spudded, drilled, producing, etc.
...