1. Pipeline and Meter Station Reporting Changes Meeting February 4, 2004
The Petroleum Registry of Alberta Energizing the flow of information
Pipeline and Meter Station Reporting Changes Meeting February 4, 2004

2. Agenda Introductions Purpose of the Meeting Reporting Changes
Background
Design Changes
Implementation
Other

3. Purpose of the Meeting
Inform the Operators of the changes to the pipeline and meter station reporting
Discuss the Implementation Process and Timing of the changes
Capture any other input from the Pipeline Operators

4. Background of Reporting Changes
TCPL is required to report many “paper” pipelines in order for the Registry to accommodate the large number of meter stations and “auto” population of activities.
ATCO also has large files with many meter stations and “auto” population of activities --- requires processing after Registry hours.
Volumetric Changes to a single meter station require the entire PL to be resubmitted – results in large amount of processing in order to change one number.

5. Background of Reporting Changes Cont’d
Some pipeline to pipeline activities are not able to be reported under the current setup and rules.
Liquids Pipelines and Terminals are unable to report DISP’s to Alberta facilities when they control the measurement of the product.
Changes required to reflect the true business process for pipelines
Funding
Shared equally between Industry, DOE and EUB
Total cost = $126 K

6. Design Changes Reporting done at the MS level versus the PL
Transactions will begin at the meter station (MS) and the Registry will autopopulate the Pipeline activity.
CSO’s are restricted at the MS to the specific activities (i.e. at a 631 type MS, the CSO can only report receipts).
ISC’s will be required at the meter station but the Registry will not autopopulate them where they are not needed (no ISC’s at the PL).

7. Design Changes - con’t Key Terms
Field relates to a meter station that receive gas from facilities that are inside the Royalty network i.e. GS, GP, IF
Interconnect relates to meter stations where the gas is leaving (flowing out of) a pipeline to another facility these other facilities includes other pipelines, BT, GS, GP, IF, PL
Interconnect Receipt and Interconnect Disposition meter stations are the same type of meter stations except an interconnect receipt meter station will be reported by the receiving facility operator (receipts will populate dispositions) and the interconnect disposition meter station will be reported by the disposing facility operator (dispositions will populate receipts).

8. Design Changes - con’t Key Terms
Autopopulate Flag is an infrastructure item that indicates the volume, energy and ISCs (where applicable) transactions will be created to flow through (in and out of) the meter station to the facilities connected on both ends of the meter station. It can only be used when there is a one to one relationship between the meter station and a single facility connected on each end of the meter station i.e. the meter station receives from a single facility and delivers to a single facility.

9. Design Changes - con’t Meter Station Sub type Definitions
631 Field Receipt Meter Station
This subtype of meter station handles field Receipts from producing facilities. Gas DISP to this type of MS is a Royalty Trigger and requires an SAF/OAF to be submitted.
632 Interconnect Receipt Meter Station
This subtype of meter station handles gas leaving the pipeline it is linked to. The PL operator will report the MS REC from the PL. The CSO can only report the MS DISP to facilities other than the linked PL if the auto populate flag set is set to No. If the auto populate flag is set to Yes the PL operator will report the MS REC from the PL and the Registry will auto populate the DISP to the other facility.

10. Design Changes - con’t Meter Station Sub type Definitions
633 Interconnect Disposition Meter Station
This subtype of meter station handles gas leaving the pipeline it is linked to. The PL operator may report the MS REC from the PL. The CSO may report the MS DISP to facilities other than the linked PL if the auto populate flag is set to No. However if the auto populate flag is set to Yes the CSO may report the DISP to the single facility linked downstream from the MS and the Registry will auto populate the REC from the linked PL.
634 Interconnect Non Reconciled Meter Station
This subtype of meter station is used to identify when gas is leaving or entering the PL the MS is linked to via a non-reporting entity. For example Gas from or gas to Saskatchewan. It should always be 100% out of balance. Only the linked PL should be reported in the from/to field at this type of MS.

11. Design Changes - con’t Meter Station Sub type Definitions
635 Registry Summary Non Reporting Meter Station
This subtype of meter station is not used for volumetric reporting in the Registry.
636 Non Reporting Meter Station
637 NEB Regulated Field Receipt Meter Station
This subtype of meter station handles field Receipts from producing facilities. Gas DISP to this type of MS is a Royalty Trigger and requires an SAF/OAF to be submitted.

12. Design Changes – con’t Meter Station Sub type Definitions
638 NEB Regulated Interconnect Receipt Meter Station
This subtype of meter station handles gas leaving the pipeline it is linked to. If the MS is reporting in the Registry. The PL operator will report the MS REC from the PL. The CSO can only report the MS DISP to facilities other than the linked PL if the auto populate flag set is set to No. If the auto populate flag is set to Yes the PL operator will report the MS REC from the PL and the Registry will auto populate the DISP to the other facility.

13. Design Changes - con’t Meter Station Sub type Definitions
639 NEB Regulated Interconnect Disposition Meter Station
This subtype of meter station handles gas leaving the pipeline it is linked to. If the MS is reporting in the Registry. The PL operator may report the MS REC from the PL. The CSO may report the MS DISP to facilities other than the linked PL if the auto populate flag is set to No. However if the auto populate flag is set to Yes the CSO may report the DISP to the single facility linked downstream from the MS and the Registry will auto populate the REC from the linked PL.

14. Design Changes - con’t MS Subtype 631 & 637 with No Auto populateGP
DISP to MS w/ISC Auto
MS Subtype 631 & 637
PL/MS Oper reports DISP to PL w/ISC
CSO reports REC w/ISC from multiple facilities
Linked Pipeline – REC from MS No ISC Auto IF
DISP to MS w/ISC Auto

15. Design Changes - con’t MS Subtype 631 & 637 with Auto Populate
PL/MS Oper reports DISP to PL w/ISC
MS REC from GP w/ISC Auto GP
DISP to MS w/ISC Auto
Linked Pipeline
REC from MS No ISC Auto

16. Design Changes - con’t MS Subtype 632 & 638 with No Auto Populate
GP*
REC From MS No ISC Auto
MS Subtype 632 & 638
PL/MS Oper reports REC from PL w/ISC
CSO reports DISP w/ISC to multiple facilities
Linked Pipeline – DISP to MS No ISC Auto
IF*
REC from MS w/ISC Auto
PL*
REC From MS No ISC Auto
* IF’s only will have ISCs populated

17. Design Changes - con’t MS Subtype 632 & 638 With Auto Populate
PL/MS Oper reports REC from PL w/ISC
MS DISP to GP w/ISC Auto
GP*
REC from MS No ISC Auto
Linked Pipeline – DISP to MS No ISC Auto
* IF’s only will have ISCs populated

18. Design Changes - con’t MS Subtype 633 & 639 with No Auto Populate
GP*
REC from MS No ISC Auto
MS Subtype 633 & 639
PL/MS Oper reports REC from PL w/ISC
CSO reports DISP to multiple Facilities w/ISC
Linked Pipeline – DISP to MS No ISC Auto
GS*
REC from MS No ISC Auto
IF*
REC from MS w/ISC Auto
* IF’s only will have ISCs populated

19. Design Changes - con’t MS Subtype 633 & 639 With Auto Populate
MS REC from PL w/ISC
Auto
CSO reports DISP to Single Facility w/ISC
Linked Pipeline – DISP to MS No ISC Auto
IF*
REC from MS w/ ISC Auto
* IF’s only will have ISCs populated

20. Design Changes - con’t MS Subtype 634 Gas Leaving the Pipeline (PL)
PL/MS Operator reports REC from PL No ISC
No DISP created MS 100% out of balance
No CSO
Linked Pipeline – DISP to MS No ISC Auto

21. Design Changes - con’t MS Subtype 634 Gas Entering the Pipeline (PL)
PL/MS Operator reports DISP to PL No ISC
No REC created MS 100% out of balance
No CSO
Linked Pipeline –REC from MS No ISC Auto

22. Implementation
Steering Committee approval was received January 21, 2004
Development has commenced and is to be completed and system tested by March 31st
Acceptance Testing will occur in April
Conversion, by the Registry, to the new process is estimated at 5 days and will take place right after the EUB deadline – approx. May 20th

23. Implementation - con’t
Prior to implementation of the changes, cleanup and validation is needed on existing data
Pipeline operators need to validate existing Meter station subtypes ( any required changes to
Any “pending” records need to be accepted (operator must Submit)
Pipeline operators need to clean up outstanding EUB non-compliance issues, where possible

24. Implementation Schedule
Task
Date Required
Complete Validation of MS Subtypes (MS operators)
February 28th
Facility operators accept “pending” records and balance MS and PL’s
March 31st
Registry Development Complete
Registry Acceptance Testing
April 1 – 30th
Pipeline Companies test batch file submission
April 15 – May 15th
Registry Conversion
May 20 – 25th
Go Live with new process
May 26th

25. Other Items Confirm the Change Leader Pipeline Splits New Issues?
with the name, phone number, and of contact person
Pipeline Splits
Electronic uploads to the pipeline companies
Availability mid-year for industry to use
New Issues?