/
What Can I do to Prepare for BC Petrinex Implementation?

What Can I do to Prepare for BC Petrinex Implementation?

Search the Qbyte Metrix Wiki
 

Back to BC Petrinex Inclusion Project Overview           Back to FAQ and How To's 



Clients with properties in British Columbia should take the time to review the following British Columbia Checklist items prior to installing Qbyte Metrix 1.10. Clients with properties in Alberta that send to British Columbia or receive from British Columbia should also take the time to review the following Alberta Checklist items prior to installing Qbyte Metrix 1.10. Some of the potential setup changes identified during this review process may be able to be addressed within your current version of Qbyte Metrix, while others may require that you wait until you have Qbyte Metrix 1.10 installed and have the BC Petrinex functionality enabled. If the setup changes require a specific version of Qbyte Metrix, that will be noted.

British Columbia Checklist

Review the field schematics of your British Columbia properties to determine battery and gathering system boundaries, and to ensure that Petrinex is made aware of the potential new facilities that you will require.  
  • Remember that Enbridge Receipt Points will become Gathering Systems, by default, however, there is room for negotiation and some of the Receipt Points may simply be batteries. 

  • With the Qbyte Metrix 1.9 Release: Batteries can be connected directly to a plant, with no need for a gathering system in between.

Review your Owners in Qbyte Metrix and their Government Code for British Columbia. Since the current BC Government Reporting required very little partner reporting, you may not have entered the BC Government Code on all the necessary Owners.
  • Remember the SAF/OAF will report Working Interest Owners, so they will need Government Codes. Also, for British Columbia, GAS DISP activities will require a Shipper, so your Purchasers will also need Government Codes.

  • Current BC Government Reporting uses a 4-character Owner Government Code. With the implementation of Petrinex, the Owner Government Code will be increased to 5 characters. 

  • With the Qbyte Metrix 1.10 Release: You can adjust your Government Codes to 5 characters, even for production dates prior to BC Petrinex implementation. The current BC Government Reporting within Qbyte Metrix has been modified (in Qbyte Metrix 1.10) to automatically convert any 5-character Owner Government Code to a 4-character code, if possible. If the leading character of a 5-character code is not a zero, an error will be generated during Step Processing and processing will not be able to continue.

Review your British Columbia Facilities and Delivery Systems in Qbyte Metrix.
  • Facilities, and more likely Delivery Systems, may not have the correct Government Code assigned to them, since the current BC Government Reporting did not require them to be reported.

Check your Delivery Systems and ensure that you understand the underlying facility that the Delivery System is representing, and that it has the correct Petrinex ID.
Check to ensure the Petrinex fields (I.e. Petrinex Facility, Produce Pipeline Split, etc.) that are associated with the Delivery System are set correctly. Remember: Pay special attention to the Petrinex Facility and Oil Pipeline Split fields, as they can significantly impact the Petrinex reporting.
Review the Operators of your Facilities and Delivery Systems and ensure that they are correct, so that cascades can be reported correctly on the SAF/OAF.
Review your British Columbia wells and units.
The British Columbia government assumes that all Gas wells produce Condensate, so ensure that all your Gas wells are set up as producing Condensate.
The British Columbia government only allows unitization of Oil wells, so ensure that you have no Gas wells attached to a unit.
Review the Qbyte Metrix implementation of your properties in British Columbia. These properties must be reviewed with an eye towards how basic Petrinex reporting works. 
For example, how the Volumetric follows the flow of product through each facility from production to sales, how the Oil Pipeline Split and Oil Valuation RTP tracks Oil Sales back to the producing battery/unit, how the SAF/OAF must cascade to facilities with different operators, and how products are reported.
Since Petrinex reporting follows the flow of product, you will not be able to simply use a Delivery System to represent product moving between facilities, unless the destination is a sales point (Pipeline, Meter Station, Terminal, etc.). You may require an actual facility set up and added to your Control Group Schematic to report correctly to Petrinex.
  • This would also include any scenarios where you have cross-control group dispositions but without using true cross-control group transfers. In these cases, you may want to reconsider the use of true cross-control group transfers, or you may have to set up duplicate facilities in each control group so that you can generate the correct SAF/OAF reporting.

  • Remember: Even to respond correctly to a cascaded volume on an SAF/OAF, you need the actual facility set up and in your control group schematic.

Review the products being produced at plants and Gas Flow batteries and/or gathering systems. Product reporting on the current BC Government reports was done at a very high-level, whereas the product reporting within Petrinex is much more detailed (I.e. Spec versus Mix, Iso versus Normal, etc.).
  • Check the LPG Fractionation flag at plants, and make sure it reflects the correct setting.

    • Optionally, you can modify the products being produced to reflect the actual product. With the Qbyte Metrix 1.8 Release, Mix, Spec, Iso and Normal variants of the products are available at each plant (or Gas Flow battery and gathering system).

  • Check the use of the LPG/NGL product. This is not a valid product for Petrinex, so its use will have to be addressed.

    • You can modify the set-up to use the actual product the LPG/NGL was meant to represent. 
      With the Qbyte Metrix 1.8 Release: Mix, Spec, Iso and Normal variants of the products are available at each plant (or Gas Flow battery and gathering system).

    • If you wish to leave the facility using the LPG/NGL product: When Qbyte Metrix 1.10 is installed (and you have enabled BC Petrinex functionality) you can set the Report As field for the LPG/NGL product to reflect the actual product.

Check if any of your properties are sending Gas to the Younger plant (Government Code 0000932). This plant has special status in that for the most part royalties are paid on the Gas coming into Younger and not on the Gas and products leaving Younger.
  • With the Qbyte Metrix 1.10 Release: Once the BC Petrinex functionality is enabled, any plants set up in Qbyte Metrix to represent the Younger plant will have to have the Royalty Paid at Inlet field set to Yes.

Review the Oil Transportation Cost/Rate entry being used on the BC09. You may want to reconsider how this is set up in Qbyte Metrix to take advantage of the functionality associated with the Oil Valuation RTP submission.
  • Once Qbyte Metrix 1.10 is installed and BC Petrinex functionality is enabled: Transportation rates can be entered on the Oil Valuation RTP screen (or uploaded using an Import by Template spreadsheet upload), like in Saskatchewan.

Review the NGL/Sulphur Transportation Cost/Rate entry being used on the BC08. You may want to reconsider how this is set up in Qbyte Metrix to take advantage of the functionality associated with the NGL/Sulphur Valuation RTP submission.
  • Once Qbyte Metrix 1.10 is installed and BC Petrinex functionality is enabled: Transportation rates can be entered on the NGL Valuation RTP screen.

Review any cross-border transactions with facilities in Alberta.
  • If a British Columbia property is sending to an Alberta Delivery System representing a sales point (i.e. Pipeline, Terminal, Meter Station, etc.) then it can be treated like any other Delivery System mentioned above. 

    • Ensure that the Petrinex fields on the Alberta Delivery System are correct.

  • If a British Columbia property is sending product to an Alberta facility for further processing or delivery to sales point, then once BC Petrinex is implemented, the Alberta facility must be in the flow of the product.  It cannot be represented as a simple Delivery System or the cascade, and its responses will not be reported correctly.

Review Partner Operated properties.
Review the products being entered at your Partner Operated batteries, and determine how they may have to be adjusted once Petrinex is implemented for British Columbia.
  • Basic Qbyte Metrix products (C3, C4, etc.) are automatically reported as the Spec variant (C3-SP, C4-SP, etc.) on Petrinex reports. 
    Within the Qbyte Metrix 1.10 Release: Partner Operated batteries can enter transactions at the Spec, Mix, Iso, Normal product variants.

You may have properties that you do not operate but that are not set up in Qbyte Metrix as Partner Operated due to other considerations (i.e. wells swing to more than one plant). 
  • With the Qbyte Metrix 1.10 Release: You may be able to set them up as true Partner Operated properties. As of Qbyte Metrix 1.10, Partner Operated batteries will have the ability to specify a Plant ID on Production and Sales transactions (gas & by-products only). This is in addition to the Plant ID that can be associated with the Partner Operated battery on the Battery Maintenance. This will allow a single Partner Operated battery to show wells as producing and/or selling from more than one Plant. 

 

Alberta Checklist

Alberta properties are, for the most part, not directly impacted by the BC Petrinex Inclusion project. However, Alberta properties that have any cross-border transactions with properties in British Columbia may be impacted. Unlike between Alberta and Saskatchewan, there will be cascaded entries required on the SAF/OAF between Alberta and British Columbia facilities. In addition, once British Columbia implements Petrinex reporting, the auto-creation of DISP entries from REC will begin even for cross-border activities.

Review Alberta properties sending product to British Columbia
If an Alberta property is sending product to a British Columbia Delivery System representing a sales point (i.e. pipeline, terminal, meter station), ensure that the Petrinex fields on the British Columbia Delivery System are full and correct.
  • Prior to BC Petrinex being implemented these Delivery Systems would be set up as Petrinex Facility = No, and would be reported to the province only (Petrinex ID = BC).  Once BC Petrinex is implemented, the Delivery System will more than likely be set up as Petrinex Facility = Yes, and will require a full Petrinex ID including province, type and code.

If an Alberta property is sending product to a British Columbia facility for further processing or delivery to a sales point, then once BC Petrinex is implemented, the British Columbia facility must be in the flow of the product. It cannot be represented as a simple Delivery System or the cascade, and its responses will not be reported correctly.
Review Alberta properties that receive product from British Columbia.
If an Alberta battery is receiving oil belonging to wells/units in British Columbia, then the Alberta battery will be required to include those volumes on the Oil Pipeline Split.
  • With the Qbyte Metrix 1.10 Release and once the BC Petrinex functionality is enabled: Alberta batteries will automatically create Oil Pipeline Split entries for any British Columbia wells/units, regardless of the Pipeline Split fields on the Battery and/or Delivery System. This is like the automatically created APMC entries.

If an Alberta plant is receiving gas on behalf of wells in British Columbia, then all facilities sending gas to the plant must also report GAS DISP volumes on the SAF/OAF to satisfy the Inlet trigger in British Columbia.
  • With the Qbyte Metrix 1.10 Release and once the BC Petrinex functionality is enabled: These plants will have to have the Processing BC Wells field set to Yes.


Copyright© 2024 IFS AB. Copying prohibited. All rights reserved.