AB Crown Shippers Balance Project Change Leader Meeting #2 May 4, 2015

Transcription

1 AB Crown Shippers Balance Project Change Leader Meeting #2 May 4, 2015 By acceptance of the attached material, all parties acknowledge that all material released by Petrinex is to be used for the sole purpose as agreed to by Petrinex. This material shall not be used for any other purpose or disclosed to any other party without prior approval by Petrinex.

2 Agenda Introductions Project Overview Stakeholder Definitions Requirements Change Leader Role & Expectations Communications Data submission methods CSV XML Online Clarification of use of RECCON and RECTRK Examples of how to report RECCON and RECTRK Testing Plan Training Plan Alberta Energy and Petrinex Contacts Other Sources of Information 2

3 Introductions Alberta Energy: Resource Revenue and Operations Laurie Schneider, Director, Oil Royalty Operations Ann Blackmore, Director, Royalty-In-Kind Operations Petrinex: JC Vanderwalt, System Analyst, Fujitsu Ross Weaver, Industry Manager Ann Hagedorn, Industry Coordinator Sharon Rudyk, Industry Coordinator 3

4 Project Overview Stakeholder Definitions In this presentation the following key definitions and abbreviations apply: Delivering Facility Operators (DFOs): Operators of facilities (e.g. batteries) delivering Crown oil volumes to pipelines, terminals and custom treating plants. Pipeline Operators (POs): Operators of pipelines, terminals and custom treating plants receiving Crown volumes from DFOs or from other facilities operated by POs. 4

5 Project Overview Requirements As of June 2015 delivery month POs will be required to: Submit monthly Crown (APMC) shippers balance information through Petrinex. These submissions can be made online or via batch processes using.xml or.csv formats. Resolve any imbalances in APMC volumes reported as transfers between pipelines, terminals and custom treating plants. New Petrinex reports will be available so Pipeline Operators PO s can proactively identify and resolve these any imbalances. As of June 2015 delivery month DFOs will be required to: Monitor and reconcile any imbalances between Crown/APMC splits reported by the DFO and corresponding receipts reported by the PO. Reconciliation of imbalances is a current responsibility of DFOs, but is currently triggered by a phone call from the DOE requesting that the imbalance be addressed. The new process will continue to require the Delivering Facility Operator to address these imbalances. New Petrinex reports will be available so Delivering Facility Operators DFO s can proactively identify and resolve these imbalances 5

6 Project Overview Requirements Delivering Facility Operator Reports under Report Queries 6

7 Project Overview - Change Leader Role and Expectations Role of the Change Leader 1. Primary Point of Contact for the BA with Alberta Energy and Petrinex with respect to this project. 2. Disseminate information to those in the BA that need the information in order for your company to prepare for these changes 3. Ensure your company is ready to report correct information on a timely basis through Petrinex at go-live. Note: In discussions with some stakeholders we understand that the required changes to their systems associated with this project cannot be implemented until later in the fall. To address this concern Alberta Energy is asking companies that will be unable to meet the July reporting commencement date to contact Cindy MacLaren (Cindy.MacLaren@gov.ab.ca) to discuss alternate submission arrangements. 7

8 Project Overview - Change Leader Role and Expectations Expectations of the Change Leader Thoroughly understand Alberta Energy/APMC requirements and Petrinex Processes Communicate effectively with Alberta Energy and Petrinex: If you need more information, assistance, additional clarity let us know. Communicate effectively with Internal and affected External Stakeholders: Marketing staff, marketing administration and accounting, IT staff, testers, users, management, other External software vendors, other Plan ahead, plan well 8

9 Project Overview Communications Information is available on the Petrinex website Initiatives Alberta Crown Shippers Balance Project 9

10 Project Overview Communications 10

11 Project Overview Communications 11

12 Project Overview Communications 12

13 Data submission Methods: Batch Submissions - CSV 13

14 Data submission Methods: Batch Submissions - CSV Data element Example Content Format Comments Verb ADD ADD is the only valid verb Noun SHIPPERSBALANCE SHIPPERSBALANCE is the only valid noun Format Version 001 (prefix with 0 s) Current is 001 Submitting Facility AB 2 chars Must be AB,BC or SK Province Submitting Facility Type PL 2 chars PL, CT and TM are the only valid facility types Submitting Facility digits (prefix Must be 7 digits Identifier with 0's) Stream Type CRD Max 3 chars Must be one of the following valid types: CRW,HSO,LSB,MSO,MSW,SHE, SLE,SO,CRD,C5+,LLB,WCB,F,BR, MBL,CAL,ACR,SW,LSO,WCS, LLK Production Year-Month YYYY-MM Shipper BA 0PMC Max 5 chars The Shipping BA or Agent (prefix with 0 s) Reference Code 1234 max 16 digits Optional reference to internal system 14

15 Data submission Methods: Batch Submissions - CSV Data element Example Format Comments Content Activity RECCON max 12 chars INVCL - Closing Inventory, OVRSHRT Overage/Shortage LOSS Loss Allowance RECCON Connected receipts RECTRK Trucked receipts TRFIF Transfer In from a Facility, TRFIS- Transfer in from another Shipper, TRFOF Transfer out to another Facility TRFOS Transfer out to another Shipper Connected From/To AB 2 chars Facility Province Connected From/To BT 2 chars Must be valid facility type Facility Type Connected From/To Facility Identifier digits (prefix with 0's) Must be 7 digits From/To Facility Province AB 2 chars From/To Facility Type BT 2 chars Must be valid facility type From/To Facility Identifier digits (prefix with 0's) Must be 7 digits From/To BA SK 2 chars Only required for TRFOS, TRFIS activities Province/State From/To BA ID 0123 Max 5 chars (prefix with Must be valid BA 0 s) Volume Maximum 5 digits (1 decimal) Volume in m 3 15

16 Data submission Methods: Batch Submissions - XML Level TAG Occurrences Min/Max 0 SHIPPERSBALANCE 1 * DataType Length Description Special Notes 5 submittingfacility 1 1 Unique ID identifying the submitting facility 10 provincestate 1 1 string 2 Province code 10 type 1 1 string 2 Facility type code 10 identifier 1 1 string 16 Number that uniquely identifies the facility. 5 productionmonth 1 1 yearmonth 7 5 streamtype 1 1 string 12 The stream type The year and month for this submission (yyyy-mm format). 5 shipperbaprovincestate 1 1 string 2 The jurisdiction of the shipper BA ID Consists of province abbreviation, facility type, and a 7 digit sequence number. One of the following stream type ID values: CRW,HSO,LSB,MSO,MSW,SHE, SLE,SO,CRD,C5+,LLB,WCB,F,BR, MBL,CAL,ACR,SW,LSO,WCS, LLK This helps applications validate the shipper BA ID information. 5 shipperbaid 1 1 string 20 The shipper BA Id. This can only be 0PMC. 5 amendmentnumber 0 1 Integer 10 Sequence number of amendment. Zerobased, every submission increments this number, regardless of pre- or postextraction. 5 referencecode 0 1 string 16 Reference code for the submission. Petrinex to DOE Petrinex to Industry Not required for input Petrinex Schema 16

17 Data submission Methods: Batch Submissions - XML Level TAG Occurrences Min/Max 5 balancerow 1 * DataType Length Description Special Notes 10 activity 1 1 string 12 Activity being submitted. This distinguishes the different sections in the Shippers balance submission and is used to determine how the row should be validated and submitted to DOE. 10 connectedfromtofa cility 0 1 Unique ID identifying the from/to facility. The following activityies will require a connectedfromtofacility value: RECCON Connected receipts RECTRK Trucked receipts TRFIF Transfer In from a Facility, TRFOF Transfer out to another Facility. 15 provincestate 1 1 string 2 Province code 15 type 1 1 string 2 Facility type code 15 identifier 1 1 string 16 Number that uniquely identifies the facility. 10 fromtofacility 0 1 Unique ID identifying the from/to facility. 15 provincestate 1 1 string 2 Province code 15 type 1 1 string 2 Facility type code 15 identifier 1 1 string 16 Number that uniquely identifies the facility. 10 fromtobaprovincestate 0 1 string 2 The jurisdiction of the shipper BA ID 10 fromtobaid 0 1 string 20 The From/To Shipper BAID 10 volume 1 1 decimal 8,1 The volume in m 3. Only required for TRFOS, TRFIS Activities. This helps applications validate the shipper BA ID information. Only required for TRFOS, TRFIS Activities. 17

18 Data submission Methods: Batch Submissions - XML Example XML 18

19 Data submission Methods: Online Submissions Users can manually input the shipper balance data using the Edit Shippers Balance screen. 19

20 Clarification of the use of RECCON and RECTRK There are two (2) receipt activities specific to Shippers Balance Reporting: RECCON - receipt from connected facilities RECTRK - receipt from trucked facilities The reason to have 2 receipt activities is to allow companies that operate multiple facilities to report a pipeline and its associated facilities on one Shippers Balance submission for that pipeline. Note that operators submitting APMC Shippers Balance reports using the xml Common Schema (generated by their marketing system) need not supply activity codes as Petrinex will create a submission with these activity codes automatically. 20

21 Clarification of the use of RECCON and RECTRK The following are the rules and definitions for the use of RECCON and RECTRK: 1. There must always be a facility identified as the Connected From/To Facility. 2. The Connected From/To Facility can be the same as the reporting facility. 3. The other From/To Facility id is only required when RECTRK is reported. RECCON: Is used to report volumes when the Connected From/To Facility is a non-operated facility, or when the operator of multiple reporting facilities wants to report each operated facility individually. RECCON only requires the Connected From/To Facility to be identified. If the Connected From/To Facility is a TM or CT another shippers balance submission is expected from those reporting facility operators. RECTRK: Is used to report volumes when the Connected From/To Facility is the reporting facility or another operated facility. RECTRK requires both the Connected From/To Facility and From/To Facility to be identified. 21

22 Examples of how to Report RECCON and RECTRK: Scenario 1 PL operator operates TM 4 connected (linked) to PL 1 where non-operated BTs and TMs also connected to the PL. Reporting on one Shippers Balance PL 1 Activity RECCON RECCON RECCON RECCON Connected From/To BT 1 (non-op) BT 2 (non-op) TM 2 (non-op) TM 3 (non-op) RECTRK TM 4 (op) BT 3 RECTRK TM 4 (op) BT 4 RECTRK TM 4 (op) TRFOF PL 2 From/To [trucked from] No Bty Entered ERROR RECCON previously Form 141 RECTRK previously Form 142 enter bty or submit separate Shippers Balance 22

23 Examples of how to Report RECCON and RECTRK: Scenario 2 TM 2 operator has volumes trucked to it from non-operated BTs, operates CT 1 that is connected to it and transfers to non-operated PL Reporting on one Shippers Balance TM 2 Activity Connected From/To From/To [trucked from] RECTRK TM 2 (op) BT 6 RECTRK TM 2 (op) BT 7 RECTRK TM 2 (op) BT 8 RECTRK CT 1 (op) BT 4 RECTRK CT 1 (op) BT 5 TRFOF PL 1 RECCON previously Form 141 RECTRK previously Form

24 Examples of how to Report RECCON and RECTRK: Scenario 3 TM 3 operator has volumes trucked to it from non-operated BTs, operates CT 2 that is connected to it and transfers to non-operated PL Reporting on separate Shippers Balances TM 3 Activity Connected From/To From/To [trucked from] RECTRK TM 3 (op) BT 1 RECTRK TM 3 (op) BT 2 RECCON TRFOF CT 2 (op) PL 1 (non-op) CT 2 Activity Connected From/To From/To [trucked from] RECTRK CT 2 (op) BT 3 RECTRK CT 2 (op) BT 4 TRFOF TM 3 (op) RECCON previously Form 141 RECTRK previously Form

25 Testing & Training Plans Testing Plan Petrinex staff will be available to run your batch files in a test environment during the months of June through October Sample batch files created by a software system or from spreadsheets can be ed to Petrinex which will be loaded and the processing results will be ed back to the requestor. Instructions for this testing will be available at the beginning of May 2015 on the Petrinex Website under Initiatives DOE Crown Shippers Balance Reporting Project Tips and Job Aids Job Aid Instructions for Industry Interoperability Testing 25

26 Testing & Training Plans Training Plan As part of this project, training will be available to assist users in being ready to use the new reporting process and functionality. This training is provided through internet-based online training modules, Tips and Job Aids which are accessible on the Petrinex website under the Resource Centre Training Modules - Login. Crown Shippers Balance training modules will be released in late June. If you currently do not have access to the Petrinex training system, click on the link Access the Online Training System at the bottom on the Resource Center tab on the Petrinex website. 26

27 Alberta Energy and Petrinex Contacts Alberta Energy Laurie Schneider, Director Oil Royalty Operations Ann Blackmore, Director Royalty-In-Kind Operations Petrinex Ross Weaver, Industry Manager (403) Sharon Rudyk, Industry Coordinator (403) Ann Hagedorn, Industry Coordinator (403) Petrinex Service Desk: (Calgary); (other locations) 27

28 Other Sources of Information Questions Related to Policy and Rules: Alberta Energy Contacts (Laurie Schneider and Ann Blackmore) Petrinex Website: Initiatives Tab, click Alberta Crown Shippers Balance Reporting Project Will include documents/communications relevant to the project Petrinex Questions: Pre-go-live: Industry Team (Ross Weaver, Sharon Rudyk or Ann Hagedorn) Post-go-live: Petrinex Service Desk 28