Pipelines Asset Utility

1 Accessing the CS Pipelines Asset Utility
2 Admin
- 2.1 Control Table
- 2.2 Ignore Pipelines Table
- 2.3 Translate Table
- 2.4 Source Operator Table
3 Process steps
- 3.1 Run Extract Public Data
- 3.2 Review Pipelines (Ignore/Accept Pipelines)
- 3.3 Run Validate
- 3.4 Run Error Summary report
- 3.5 Run Update
4 Reports

Accessing the CS Pipelines Asset Utility

Activate CS Pipeline Utility: User Processes > Asset Utilities > Pipelines

Admin

Opening Admin window is not mandatory; you can just open the Admin window if you want to maintain the information. Admin window includes the following tabs:

Control Table

This table will list out all tables and columns that exist within CS Land.

Note: when using IHS data, Saskatchewan pipelines will get the licence number from the "regulatory code" field if populated otherwise it will use the "approval number".

Ignore Pipelines Table

Users can manually maintain this table to ignore Pipelines from source for various reasons. Pipelines set to ignore in review process will automatically be added to this table.

Translate Table

This is the basic translation table for all columns. Note: Translate flag in control table must be set to Yes, before any translation to done on the source values.

Source Operator Table

This table contains the “Licensed” vendor codes of the client. Codes in this table will be considered operated Pipelines. All other licensed codes will be considered non-operated. Codes in the table are from the third party source.

Process steps

Run Extract Public Data

If you run Extract Public data, all Pipelines will be downloaded from the source excluding Pipelines to be ignored.

This process executes various steps in a prescribed order.

Determine new Pipelines based on Source Operator
Determined potential Pipelines updates base on source / CS last update
Set sort on Pipeline Licence No./Line No. on all selected Pipelines to this point.
Run translate process.
Run Compare Process – This will compare all potential updates with CS to determine which columns are to be updated based on rules in the control table. (All Pipelines that were selected for updates may not actually cause an update to occur within CS)
Run Validation Step: It is validate columns that have been selected for update.

Review Pipelines (Ignore/Accept Pipelines)

Use Pipelines Asset Utility Review window to Accept or Ignore or defer decisions on the New and Update Pipelines.

New Pipelines are categorized by:

Operator Match: Matches based on the Source Operator table

Update Pipelines are categorized by:

Operated: Current Pipelines operated by the client
Non-Operated: non operated Pipelines existing in the Pipelines module. On initial review all non-operated Pipelines will be accepted.
Licensee Changing: Shows Pipelines where the current Licensee in the Pipelines module is being changed

Each module is identified by:

Accepted: Pipelines that have been accepted during a previous run
Pending: Pipelines that have not been accepted or ignored.
Ignore: Pipelines that have been ignored

Control Buttons:
There are 2 check boxes and 2 Control buttons and available to Accept or Ignore New Pipelines.

Add: Add to the Pipelines Module. A new file number will be automatically generated.
Append to File Number: Enter the file number you wish to append the Pipeline to.
Accept: Click this to add Pipeline to the Pipelines module
Ignore: Click this to ignore the Pipeline. The Pipelines will be placed into the Ignore Pipelines table. User will be prompted to enter reason and a review date.

Note: If neither Accept nor Ignore is checked off, Pipeline will be in Pending mode. When first reviewing new Pipelines, all the Pipelines will be defaulted to Pending and will require a manual review of each and every new Pipeline, upon selecting an individual Pipeline, the right panel of the window will display basic information about this new Pipeline.

Run Validate

At this step Pipelines to be validated include new Pipelines that have been accepted and columns that have been selected for update.

The first step is to set any default values for new Pipelines as defined in the control table. Current Pipelines validations include:

Lengths of data do not exceed limits in CS
Dates are of valid format
Values that exists in code tables are valid
New Pipelines contain all mandatory columns

Run Error Summary report

This report creates a summary report of each distinct error, so it gives you a chance to fix all existing errors by updating Validation tables or Admin tables. If you don’t fix those errors, Pipelines and Columns with errors won’t be included in Update.

Note: Once you fixed all errors you should run Validation step and run this report again to make sure there are no outstanding errors on selected Pipelines and columns.

Run Update

Once you made sure there is no outstanding error with selected Pipelines, run this step, Updates run 3 steps:

1. Verify: this step is run immediately before any updates, regardless if Validation has been run by user.

2. Updates: Updates all Pipelines / columns that have been selected for updates that have no errors are processed.

3. New: Adds all new Pipelines that have been accepted and have no errors are processed.

Reports

Error Summary Report (RP-0258)
Pipeline Errors Report (RP-0259)
New Pipeline Added Report (RP-0264)
Pipeline Updates Report (RP-0262)
Run Statistics Report (RP-0261)
Pipeline Audit Report (RP-0269)