Release Notes for Qbyte Metrix Version 1.15
- 1 Release Overview
- 2 Release Contents
- 2.1 Conversions
- 2.1.1 MB Petrinex Inclusion
- 2.2 Enhancements
- 2.2.1 Methane Emissions
- 2.2.2 MB Petrinex Inclusion
- 2.2.3 Better Together
- 2.2.4 Petrinex
- 2.2.5 General
- 2.3 Issues Resolved
- 2.3.1 General
- 2.3.2 Ideal Product Shrinkage
- 2.3.3
- 2.3.4 Functional Implementation Types
- 2.4 Download the Qbyte Metrix 1.15 Release Inventory Spreadsheet
- 2.1 Conversions
- 3 Database
- 4 Known Issues
Release Overview
Release Date
November 13, 2019
Release Type
Minor
Product Interoperability Matrix
Recommended System Requirements
Summary of Changes
There are two main Regulatory enhancements that are the focus of this release: the Methane Emissions project, and the MB Petrinex Inclusion project. In addition to these two projects, there are various other enhancements as well as several outstanding issues that have been resolved.
Methane Emissions
The various provincial governments are introducing new definitions for FUEL, FLARE, and VENT, which will impact how you enter consumption volumes at facilities. There are several features to enhance Qbyte Metrix to provide an easy, flexible way for you to enter and report consumption per the various new directives.
These basic changes allow you to dispose of and receive a generic volume of gas to be used for consumption. With the new definitions for FUEL, FLARE, and VENT, it is not reasonable to expect the sending facility to know what the gas they send needs to be reported as (other than to know it is being sent for consumption). Similarly, it is not reasonable to ask the receiving facility to enter multiple consumption receipts for each type of consumption. It is much easier to simply bring in a single consumption receipt and identify the type of consumption through the facility-level usage or well-level consumption factors (for consumption used at the well from receipts).
For dispositions/receipts that automatically update explicit Lease Fuel, Flare or Acid Gas volumes we cannot modify the behavior. It would be very difficult to try to convert that data into the new more generic consumption approach, therefore we will leave the existing Fuel Receipt, Lease Fuel, Flared, and Acid Gas receipt types as is, and add two new receipt types: Consumption and Consumption Receipt, that can be used for any type of consumption, including at the well-level (from receipt). We will also leave the battery disposition/receipt of Transfer for Fuel as is and introduce a new Transfer for Consumption that can be used for any type of consumption, including being used at the well-level (from receipt).
MB Petrinex Inclusion
As most of you are probably aware by now, Manitoba will be adopting the use of Petrinex starting with April 2020 Production with a scheduled Go-Live date of May 4, 2020 .
There will be no modifications to their Royalty Calculations and Invoicing at this time. Clients will still be expected to calculate and submit Crown as is done currently.
For those of you familiar with existing Petrinex functionality, the adoption of Petrinex by Manitoba should be relatively smooth, as they are adopting most of the same rules as Saskatchewan. The differences are outlined below.
Manitoba batteries will not report Heat Content on wellhead GAS PROD entries on the Volumetric submission.
For more information see Manitoba Petrinex Inclusion Project Overview .
Release Contents
Conversions
MB Petrinex Inclusion
DESCRIPTION | SUMMARY |
---|---|
Petrinex Master Data | We have defaulted the various Petrinex fields on Manitoba Batteries, Gathering Systems, Plants, Injection Facilities and Delivery Systems to help ease the transition for our clients. With these default values being pre-populated, this will reduce the number of facility master updates that users must make when Petrinex functionality is enabled. Batteries:
Gathering Systems:
Plants:
Injection Facilities:
Delivery Systems:
|
Enhancements
Methane Emissions
FEATURE NAME | AREA IMPACTED | SUMMARY |
---|---|---|
Gas Receipts at batteries for use at the well-level expanded to allow Flare and Vent | Well Maintenance - Production Battery Balance - Gas | Qbyte Metrix now provides the ability to use gas receipt volumes at the well-level for Flare or Vent, in addition to the existing Lease Fuel functionality. Currently, batteries can enter a Fuel Receipt for Wells receipt to show gas volumes coming into the battery for use at the well-level. The wells using the receipt gas will have a consumption factor set up with the Adjust Production option set to Receipt (Do Not Adjust Production) and a Usage Type of Lease Fuel.
|
New Consumption receipt that can be used for any valid consumption type | Battery Balance, GGS Balance, Plant Balance Consumption Allocation (Battery, GGS or Plant) | Qbyte Metrix now provides a new receipt type (Consumption) to allow a facility (Battery, Gathering System or Plant) to receive gas that it can use for any valid consumption appropriate for that facility. Currently, batteries and gathering systems only have access to Fuel Receipt and plants have Lease Fuel, Flared, or Acid Gas receipts. For each of these receipt types, the received volumes are automatically designated for the use specified and cannot be used for anything else. To make it easier for the facility receiving gas to determine how it will be used, Qbyte Metrix introduced two new receipt types:
Neither of these new receipt types limits the use of the received volumes, other than they must be used for consumption. How the received volumes are used is determined by the data entry at the consumption Usage ID level. Any volumes not accounted for by the Usages will be assumed to be used as Lease Fuel at the receiving facility. Note: When the receiving facility is a battery, the received volumes can also be used at the well-level for those wells with consumption factors indicating that the volumes are coming from receipts. |
Battery-to-Battery transfers for consumption (not just Fuel or Market) | Battery Balance - Gas | Qbyte Metrix now provides a new battery-to-battery disposition type (Transfer for Consumption) to allow for the transfer of gas from one battery to another for consumption at either the battery or well-level. Currently, Qbyte Metrix provides two types of battery-to-battery transfers: Transfer for Market and Transfer for Fuel. The first is used to transfer gas volume to then be sent for processing. The second is used to transfer gas volume to be used for Lease Fuel at the receiving battery. The Transfer for Fuel disposition automatically creates a Fuel Receipt at the receiving battery. To make it easier to transfer gas from one battery to another and leave it up to the receiving battery to determine how to use the gas, Qbyte Metrix introduced a new disposition type:
|
Rename gas disposition types to reflect that they can be used for any valid consumption type | Battery Balance, GGS Balance, Gas Flow Balance, and Plant Balance | Qbyte Metrix renamed a couple of disposition types to reflect the fact the volume can now be used for any valid consumption type.
Note: Since dispositions of these types do not auto-generate receipts, you must manually enter the receipt at the destination facility - there is no functional change to this disposition type, however, the receiving facility can now use either a Fuel Receipt (as they do currently) or the new Consumption/Consumption Receipt receipt type, depending upon the receiving facility and their requirements. |
Import Data By Template option for Facility Usage IDs | Import Data By Template | Qbyte Metrix now provides a new (FACILITYCONSUSAGEGENERAL) for Import Data By Template to allow for the creation and/or updating of Facility Usage IDs. With the new definitions surrounding consumption, you may want/need to use Usage IDs more frequently, and this new template makes mass creation and/or updating easier.
|
Adjust Theoretical option on Facility Consumption Usages | Consumption Allocation (Battery, GGS or Plant) Step Processing: STEP01 - Allocation | Qbyte Metrix now allows the user to control whether an individual Facility Usage ID is to be netted off the theoretical and/or gathered volumes of those entities it is allocated to. Currently, when the facility is set up to use Usages and they are being allocated down to entities, all usages are netted off the theoretical volume (or gathered as appropriate), there is no way to indicate only certain usages should impact the theoretical (gathered) volume. Each Facility Usage ID has a new Adjust Theoretical option, which defaults to Yes to ensure existing functionality remains the same, but can be set to No. When Adjust Theoretical = No the usage is still allocated down to the entities (or in the case of an IPS Order Id, the order is still allocated down to the entities), but the allocated volume is not subtracted from those entities' theoretical (gathered) volumes. This option may be useful when receiving gas to be used as consumption. Since the gas being consumed is not from the facility's production, instead of reducing the theoretical (gathered) volume of the entities consuming the gas, it may be more accurate to ignore the consumption volume that came from receipts. Note: When a facility is using a mixture of its own production and receipt volume for consumption, it may be necessary to split the consumption into multiple Usage IDs in order to better control which volumes impact theoretical (gathered) volumes and which do not. |
MB Petrinex Inclusion
FEATURE NAME | AREA IMPACTED | SUMMARY |
---|---|---|
MB Petrinex Directories | System Configuration - Directories | Qbyte Metrix has added the ability to set up Directories to be used for MB Petrinex Exports (i.e. Volumetric Submissions , etc.) and MB Petrinex Imports (i.e. Oil Pipeline Split Imports ). These new Directory Types can be maintained in the System Configuration screen, Directories tab under the Administration menu. |
Enable Petrinex Operators in Manitoba | Region Maintenance - Petrinex Operators | Qbyte Metrix will now allow for the maintenance of Manitoba Petrinex Operators by Region when the production date is greater than or equal to MB Petrinex Implementation date. |
Enable Petrinex fields on Entity Masters | Battery Maintenance - Master GGS Maintenance - Master Plant Maintenance - Master Injection Facility Maintenance - Master | Qbyte Metrix will now display Petrinex-specific fields on the various Entity Maintenance screens for Manitoba entities when the production date is greater than or equal to MB Petrinex Implementation date. |
Battery Maintenance - Enable Battery Subtypes for MB Batteries | Battery Maintenance - Master | Qbyte Metrix now includes the new Manitoba Battery Subtypes on the Battery Maintenance > Master tab. Measurement Edits have also been loaded that match the edits for equivalent Saskatchewan B attery Subtypes, where possible. As EPAP has not yet been implemented for Manitoba, all Measurement Edits will have an initial maximum severity of Warning. Note: When EPAP is implemented, the Measurement Edits will be re-evaluated. Reminder: Use System Configuration (Measurement Edits) to enable Measurement Edits for Manitoba, and to determine if Battery Subtypes are to be mandatory for Manitoba batteries. |
Enable Report As Product functionality for By-Products | Battery Maintenance - Gas Flow GGS Maintenance - Gas Flow Plant Maintenance | Qbyte Metrix will now enable the Report As Product field on the Plant Maintenance, GGS Maintenance > Gas Flow and Battery Maintenance > Gas Flow screens for Manitoba facilities after the MB Petrinex Implementation date. Clients can use this option to override how the product is reported to Petrinex. |
Royalty Tax Payers | Well Maintenance - Royalties - Crown Unit Maintenance - Crown | Qbyte Metrix has added the ability for the user to explicitly set the Royalty Tax Payer (RTP) for each owner in the DOI at a non-unit well level or at a unit level, for Manitoba entities. Manitoba only uses Royalty Tax Payer on the Oil Valuation RTP, so only OIL Royalty Tax Payers will be allowed on Manitoba wells and/or units. Non-unit wells:
Units:
Note:
|
Petrinex Well Groups | Petrinex Well Group Maintenance | Qbyte Metrix will now allow for Petrinex Well Groups to be maintained for Manitoba facilities when the production date is greater than or equal to the MB Petrinex Implementation date. |
Enable Fire, Theft, Spill and Blending Shrinkage for Battery Oil Dispositions | Battery Balance - Oil Facility Volumetric Entry Definitions Step Processing: STEP07 - Financial Interface | Qbyte Metrix will now allow Oil disposition types of Blending Shrinkage, Fire, Theft and Spill Manitoba batteries when the production date is greater than or equal to the MB Petrinex Implementation date.
In addition, the volumes associated with these dispositions can be included in a Financial Voucher with their own Entry Definition(s). General Type is LOSS and Specific Type will depend upon the type of loss (i.e. FIRE, THEFT, SPILL, SHR) and/or the volumes used (i.e. RLO, ROYT). |
Enable Purchased option on Oil Injection Receipts and Dispositions | Battery Balance - Oil Facility Volumetric Oil Pipeline Split Oil Valuation RTP | Qbyte Metrix will now display and enable the Purchased flag on Battery Oil Receipts and Dispositions of type Injection when the production date is greater than or equal to the MB Petrinex Implementation date. In Manitoba, like in Saskatchewan, oil purchased for load injection purposes must be reported as a Purchased Receipt/Disposition (PURREC/PURDISP) and is reported on the Oil Pipeline Split and Oil Valuation RTP. |
Enable Spill for Battery Water Dispositions | Battery Balance - Water Facility Volumetric | Qbyte Metrix will now allow Water dispositions of type Spill for Manitoba batteries when the production date is greater than or equal to the MB Petrinex Implementation date. |
Gas Pipeline Split | Pipeline Split | Qbyte Metrix has added the ability to generate/submit Petrinex Gas Pipeline Splits for Manitoba properties. Note: Gas Pipeline Splits are not mandatory in Manitoba. |
Oil Pipeline Split | Pipeline Split | Qbyte Metrix has added the ability to generate/submit Petrinex Oil Pipeline Splits for Manitoba properties. Note: Oil Pipeline Splits are mandatory in Manitoba and must be Full split (including all owners). The Oil Pipeline Split for Manitoba follows most of the same rules as Saskatchewan. |
Oil Valuation RTP | Generate Oil Valuation Data Oil Valuation RTP Oil Valuation RTP by Control Group | Qbyte Metrix has added the ability to generate/submit Petrinex Oil Valuation RTP for Manitoba properties. The Oil Valuation RTP for Manitoba follows most of the same rules as Saskatchewan. |
Facility Volumetric | Generate Volumetric Injection Volumetric Files | Qbyte Metrix has added the ability to generate/submit Petrinex Volumetric data for Manitoba properties. |
SAF/OAF | Generate SAF/OAF File for Prior Period Injection SAF/OAF Files Generate SAF/OAF | Qbyte Metrix has added the ability to generate/submit Petrinex SAF/OAF (Oil and Gas) for Manitoba properties. Note: SAF/OAF is optional in Manitoba. |
Subtype Load/Verification | Subtype Load/Verification | The Subtype Load/Verification Upload process has been enhanced to allow Manitoba batteries. This will only apply to Manitoba batteries when the production date is greater than or equal to the MB Petrinex Implementation date . |
Enable Petrinex Override fields for Consumption Usages | Consumption Allocation | Qbyte Metrix has enabled the Petrinex Province, Petrinex Entity Type, and Petrinex Government Code fields for Consumption Usages in the Consumption Allocation screen for Manitoba facilities on or after the MB Petrinex Implementation date. Note: The Petrinex Activity field will also be displayed for Manitoba plants when the production date is on or after the MB Petrinex Implementation date. |
Remove pre-Petrinex MB Government Reporting after MB Petrinex Implementation Date | MB Government Reporting | Qbyte Metrix now displays an error message on the MB Government Reporting screen when a production date after the MB Petrinex Implementation date is selected. |
Better Together
FEATURE NAME | AREA IMPACTED | SUMMARY |
---|---|---|
Qbyte FM Report ID from Qbyte FM OneStep | Qbyte FM OneStep | The Qbyte FM OneStep process now returns the Report ID of the Qbyte Metrix Interface process (REVU066). Currently, the Qbyte FM Report ID sent back to Qbyte Metrix from the Qbyte FM OneStep is the ID of the Validate Interfaced Vouchers process (ACTU116) in Qbyte FM. Since the ID of the Qbyte Metrix Interface process, sometimes called Batch ID, Interface ID, or Interface Control ID in Qbyte FM and Qbyte Optix for Qbyte FM, can be used as a means of selection in various Qbyte FM screens and Qbyte Optix for Qbyte FM reports, it was deemed more useful for that ID to be passed back to Qbyte Metrix as the Qbyte FM Report ID. It will continue to be displayed on the Financial Identifier Status screen and in the Message Centre. |
Voucher Status Integration between Qbyte Metrix and Qbyte FM | Financial Identifier Status | Qbyte Metrix now accepts status updates on Vouchers from Qbyte FM for vouchers that were created in Qbyte Metrix and displays the updated status on the Financial Identifier Status screen. Note: To use this functionality, it must be enabled in both Qbyte Metrix and Qbyte FM.
|
Petrinex
FEATURE NAME | AREA IMPACTED | SUMMARY |
---|---|---|
Acid Gas FLARE Reporting | Consumption Allocation on Plant Balance Plant Volumetric | Qbyte Metrix now provides the option to indicate whether plant-level Acid Gas is to be considered FLARE, along with the ability to specify a From/To Facility for the FLARE volume. Currently, all Acid Gas volumes entered at a plant are reported with the activity SHR with no From/To Facility. Note:
Note: Although, this is not mandatory until January 2020 Production, as of May 2019 Production Petrinex will accept FLARE as a valid activity for the product ACIDGAS on Facility Volumetric submissions for plants.
|
Override Shipper for Oil Pipeline Split | Market Master Oil Pipeline Split | Qbyte Metrix now provides the ability to override the Shipper that appears on the Oil Pipeline Split by entering an Override Shipper on the Market Master. Currently, Qbyte Metrix uses the purchaser as the Shipper on the Oil Pipeline Split. |
General
FEATURE NAME | AREA IMPACTED | SUMMARY |
---|---|---|
Calculated Battery Gas Oil Ratio | Battery Maintenance (Production) Well Maintenance (Production) Battery Balance (Summary, Well Input, and Gas Balance) Battery Step Processing: STEP01 - Allocation Import Data By Template | Qbyte Metrix now provides the ability to indicate that a battery is using a system-calculated Battery Gas Oil Ratio. For these batteries, Qbyte Metrix will calculate the Battery Gas Oil Ratio and apply that to all eligible wells attached to the battery to determine the wellhead gas production. Currently, clients with batteries that are using a Battery Gas Oil Ratio are using various workarounds within Qbyte Metrix to get the allocation of wellhead gas and the Petrinex reporting correct. This functionality will also:
Note: Qbyte Metrix will not limit the use of this functionality to a specific province or a specific type of battery. It is up to you to understand the requirements for your batteries, including Provincial regulations, and to ensure that you are using a calculation method that is acceptable for each battery and the jurisdiction it is in.
|
Royalty Volume Calculation for Oil Royalty Obligations | Control Group Step Processing: STEP06 - Freehold and Override Royalty Calculation Summary and Detail reports Royalty Owner Summary report | Qbyte Metrix now provides an option to modify the calculation to determine Royalty Volume on non-Taken-In-Kind Oil Royalty Obligations when there are no Oil Sales for the well/tract associated with the Royalty Obligation. Taken-In-Kind royalties have no Royalty Value, just a Royalty Volume, and are therefore not impacted by this new functionality. Currently, if there are no Oil Sales Volume or Value for the well/tract, the Royalty Volume will be zero as there is no way to determine the effective rate for the Royalty Obligation. The effective rate typically reflects Royalty Value divided by Sales Value, the effective rate is then applied to the Sales Volume to calculate the Royalty Volume associated with the Royalty Value. When there is no Sales Volume or Sales Value, the effective rate is zero and therefore the Royalty Volume is zero. Depending upon your internal requirements, having a zero Royalty Volume and a non-zero Royalty Value may have been an issue with Royalty reconciliation and financial booking.
Note: By default, this functionality will not be activated. You must explicitly activate this functionality (if required). A Start Date was implemented for this option to ensure that prior period results are not impacted unless you wish to implement the functionality retroactively by using an earlier Start Date. |
Water Meter Factor | Well Maintenance (Production) Battery Balance (Well Input) Import Data By Template | Qbyte Metrix now provides the ability to enter a Water Meter Factor at a well. This factor is applied to all water production (test and measured) entered for the well, and is basically an adjustment factor. Currently, Qbyte Metrix has both an Oil Meter Factor and a Gas Meter Factor, but is missing a corresponding Water Meter Factor. There is currently no way for you to apply a correction factor to the entered water production volumes.
|
Update Facility Charge Primary Retrieval Usage Details | Facility Charge Global Formula Facility Charge Maintenance - Facility Charges Facility Charge Maintenance - Formulas | The Usage Details information has been updated for the following Primary Retrieval Types to provide more detailed information:
Note: This update only updated the Usage Details text and will not affect Facility Charge processing.
|
Issues Resolved
General
SUMMARY | AREA IMPACTED | NOTES |
---|---|---|
Too many warning messages on the Consumption Allocation screen | Consumption Allocation (Battery Balance Gas, GGS Balance, and Plant Balance) | Issue: On the Consumption Allocation screen accessed from the various Balance screens, there were warning messages displayed when the sum of the entered entity-level volumes was less than the entered usage-level volume. These warning messages were frustrating for users that were not entering specific volume per entity, but were simply using the entity linkage to indicate which entities Qbyte Metrix should allocate the entered usage-level volume to. Resolution: To reduce the number of warning messages displayed, the warning message indicating the sum of the entered entity-level volumes is less than the entered usage-level volume will only be displayed when the sum of the entity-level volumes is not zero. This means the message will only be displayed when you have entered volumes for at least one entity attached to the usage, but have not accounted for the entire usage-level volume. |
Balance Checks does not launch from Consumption Allocation | Consumption Allocation (Battery Balance Gas, GGS Balance, and Plant Balance) | Issue: The Balance Checks link on the Consumption Allocation screen, displayed when the facility does not balance, did not launch the pop-up with the balance details when clicked. Resolution: The Balance Check Details pop-up is now displayed when the Balance Checks link is selected on the Consumption Allocation screen for an un-balanced facility. |
Battery and Gathering System Fuel Receipts cannot have a Sending Battery | Battery Balance - Gas Gathering System Balance | Issue: When adding a Fuel Receipt from a Battery on the Battery Balance or Gathering System Balance, any Battery ID entered generated an error indicating it is not a valid Battery Facility. Resolution: Fuel Receipts on the Battery Balance and Gathering System Balance now correctly validate an entered Sending Battery ID. |
Extra Gas Receipts on Gas Flow Balance for Battery using Fuel Receipt for Wells | Battery Balance - Gas Gas Flow Balance | Issue: For Gas Flow batteries with one or more Fuel Receipt for Wells gas receipts, when generating Gas Flow dispositions/receipts either automatically when data was saved on the Battery Balance or by clicking the Upload Gas Flow Dispositions and Save button on the Gas Flow Balance, an extra Fractionation receipt was created for each Fuel Receipt for Wells receipt. Resolution: Fuel Receipt for Wells (now called Consumption Receipt for Wells) are ignored when creating Gas Flow disposition/receipts. |
Selecting a facility charge in the grid when on the Owners tab does not work in View mode | Facility Charges | Issue: On a Facility with multiple pages of Facility Charges, users were unable to switch to a Facility Charge on another page while in the Owner Exceptions tab in View Mode. Resolution: In View Mode, users can switch between Facility Charges while in the Owner Exceptions tab. |
When a Tract has inventory but is not attached to the Unit, Step 2 issues an incorrect error message | Step Processing: STEP02 - Sales and Transfers | Issue: A facility selling from a tract's inventory would display the following incorrect warning message during Step1-2 processing if that tract was no longer connected to a unit, or if the unit master was missing: I null associated not associated with a unit, or the unit does not have a current master. Resolution: Step1-2 processing has been changed to display a correct warning message with enough information for the user to correct the issue. For example, Tract AKEABUGAST01 is not associated with a unit, or the unit does not have a current master. |
Unable to delete jobs from the File Repository grid with Full Access to the FileRepository security component | File Repository | Issue: The Canceljobs security component incorrectly disabled the ability to delete a selected job from the File Repository screen. Resolution: The functionality of the File Repository grid has been modified so that the ability to delete a job from the File Repository grid is only controlled by the security component FileRepository.
|
In some instances, BYP Royalties are not calculated for Partner Operated Wells | Partner Operated Battery Balance (Sales) Step Processing: STEP06 - Royalties | Issue: When individual by-product (i.e. Propane, Butane, etc.) production transactions were missing for Partner Operated Wells, Royalty Obligations set up with BYP as the product did not calculate a royalty on all the by-product volumes. Note: In order to determine the by-products to be included in a BYP royalty, Qbyte Metrix relies on the products that the well is producing. If there are no production transactions for a given by-product, then it will not be included in the royalty obligation calculation. The production transactions may have been missing because manually created sales transactions (Partner Operated Battery Balance > Transactions) did not automatically create matching production transactions for the products. It was up to the user to create both the sales and the production transactions. Resolution: To help reduce the effort and to eliminate the need for the user to create both sales and production transactions, when sales transactions are saved for Partner Operated Wells, matching production transactions are now created (if they do not already exist). |
Negative production allocated on Gas Flow properties when allocated consumption exceeded theoretical volumes | Step Processing: STEP01 - Allocation | Issue: When allocated consumption exceeded theoretical, a negative production was being calculated. This only impacted properties that were Gas Flow and that were using either a Gathered or Component allocation method. Resolution: When allocated consumption exceeds theoretical, the adjusted theoretical is now set to 0 and a corresponding message is generated in the Message Centre. Production is then allocated down to the adjusted theoretical without generating any negative production. |
Calculated inlet volumes into non-Gas Flow BC plants for reporting on the SAF/OAF did not consider all consumption | Step Processing: STEP01 - Allocation | Issue: When calculating the inlet volumes into a non-Gas Flow BC Plant, only the first consumption usage found at each facility for a given entity was being considered. The overall inlet volume into the plant was correct, but the allocation of that volume down to the producing entities may not have considered the correct adjusted gathered. Resolution: All consumption allocated to each entity is being accumulated and used to calculate the inlet volumes. Note: This may cause the results of existing properties to change. |
Obsolete Oil receipt type of Heavy Truck Load still available | Battery Balance - Oil | Issue: An obsolete receipt type Heavy Truck Load was still appearing as a valid option when creating a Battery Oil Receipt for batteries attached to a Control Group with Allow Special Heavy Oil Processing = Yes. Resolution: When creating a Battery Oil Receipt, Heavy Truck Load is no longer a valid receipt type for any battery. |
Gas Flow Facility Volume Sent report missing volumes in some rare situations | Step Processing: STEP02 - Sales and Transfers | Issue: In rare circumstances, a delivery from one Gas Flow facility to another was corrupt, was not being allocated, and no messages were being generated in the Message Centre. This resulted in no volumes in the Gas Flow Facility Volume Sent report, and therefore no theoretical at the receiving facility. Resolution: Step Processing has been modified to correctly handle the possibility of corrupt dispositions. |
Facility Charges may be over-calculated when Owner Exception list had multiple owners | Step Processing: STEP04 - Facility Charges | Issue: The following Primary Retrieval Types had a common issue when looking at the Owner Exceptions on the charge. They calculated the charge on the full amount for each owner in the list (only INCLUDE lists are used). The charges were only calculated when at least one of the owners in the Owner Exception list (if entered) was in the entity being charged, however, if the Owner Exception list contained more than one owner in the entity, then that entity may have been over-charged (charged the total amount for each Owner in the list that is in the DOI).
Note: Some of the above did not have this issue for unitized entities depending upon how the Unit/Tract Criteria option was set. Resolution: The Facility Charge process has been modified to ensure that charges using one of the above Primary Retrieval Types to only calculate the charge once per entity regardless of how many owners in the Owner Exception list are associated with the entity. The charge continues to be calculated only for those entities that have at least one Owner in the Owner Exceptions list, if entered. The Primary Retrieval Types that over-calculated have been addressed without impacting the scenarios that may have been working depending upon the Unit/Tract Criteria. |
Ideal Product Shrinkage
SUMMARY | AREA IMPACTED | NOTES |
---|---|---|
Step 1 Processing crashes for a facility using the Ideal Product Shrinkage method when analysis data is entered incorrectly | Step Processing: STEP01 - Allocation | Issue: For facilities using Ideal Product Shrinkage when sales analyses were entered incorrectly such that the actual volume for one or more components was significantly larger than their theoretical volume, the ratio of actual to theoretical exceeded 999.999999 and the Step Processing job would crash. Resolution: The Step Process for Ideal Product Shrinkage facilities has been modified to check the ratio of actual to theoretical volume and will now generate an appropriate message in the Message Centre. |
Some Gas Flow specific fields were displayed within the IPS Order screens for non-Gas Flow Facilities | Maintain IPS Order Table - Order Details grid Maintain IPS Order Table -Participant Details grid | Issue: Some Gas Flow-specific fields were displayed within the IPS Order Table screens for non-Gas Flow Facilities. Resolution: The following changes have been made to display only the relevant data for non-Gas Flow facilities:
|
The user was unable to return to the Maintain IPS Order Table - Participant Groups tab when the View Group Membership button was selected | Maintain IPS Order Table - Order Participant Details Maintenance (Participant Groups tab) Participant Group Maintenance | Issue: The user was unable to return to the Participant Groups tab of Maintain IPS Order Table after launching the Participant Group Maintenance screen via the View Group Membership button. Resolution: A Cancel button has been added to the Participant Group Maintenance screen when the screen is accessed using the View Group Membership button on the I PS Facility Balance > IPS Order Table > Edit Participant Details > Participant Groups tab. Clicking this Cancel button will take the user back to the Order Participants Details Maintenance > Participants Groups tab. |
The Flow ID column was incorrectly named as Flow Group within the Maintain IPS Order Table - Participant Details screen | Maintain IPS Order Table - Order Participant Details Maintenance (Flow Groups tab) | Issue: The Flow ID column was incorrectly named Flow Group within the Participant Details screen. Resolution: The column has been renamed to Flow ID. |
The Production Date may not have been populated correctly on the Flow ID Maintenance screen when launched from the Maintain IPS Order Table | Maintain IPS Order Table - Order Participant Details Maintenance (Flow Groups tab) Flow ID Maintenance | Issue: When the Create New Flow ID button was clicked from the Flow IDs tab of the Maintain IPS Order Table, the Production Date on the Flow ID Maintenance screen was being defaulted to Current System Production Date instead of to the Production Date from the Maintain IPS Order table. Resolution: The Flow ID Maintenance screen will now default the Production Date from the Maintain IPS Order table when the Create New Flow ID button is clicked from the Flow IDs tab. |
Order Details grid did not automatically re-sort to reflect modified Order Sequences. | Maintain IPS Order Table - Order Details | Issue: When a user changed the Sequences on the Order Details grid a nd clicked the Save button, the grid remained in its original order. Resolution: When the Save button is clicked on the Order Details screen, the grid is now re-sorted based on the Sequence. |
Save button may have required multiple clicks to correctly resolve duplicate Order Sequence errors. | Maintain IPS Order Table - Order Details | Issue: When errors occurred due to duplicate Order Sequences, resolving the issue may have required the user to click the Save button multiple times. This situation occurred when after having received the error messages about duplicate orders, the user corrected one of the duplicate orders to make the Order Sequences unique and then without tabbing off the Sequence column clicked the Save button immediately. In this case, the first click of the Save button would not save the data, there would still be an Order Sequence highlighted as an error, but no error messages would be displayed. Clicking the Save button a second time would successfully save the data. Resolution: Clicking the Save button after modifying an Order Sequence with or without tabbing off the Sequence field will now correctly re-validate all Order Sequences and Save the data successfully, if there are no other errors. |
The Participant Details grid was not being refreshed correctly when a new Order was selected. | Maintain IPS Order Table - Order Details | Issue : After a user viewed participants for the selected Order by clicking the View Participant Details button, selecting or deselecting an Order in the grid did not update the Participant Details section. The Participant Details from the previously selected Order remained displayed. Resolution: When the user selects or deselects an Order (using the checkbox) after having viewed Participant Details, the Participant Details section is now cleared and hidden until the View Participant Details button is clicked again. |
Functional Implementation Types
SUMMARY | NOTES |
---|---|
Added Functional Implementation Types | The following Functional Implementation Types have been added to Qbyte Metrix:
|
Download the Qbyte Metrix 1.15 Release Inventory Spreadsheet
Database
FEATURE NAME | AREA IMPACTED | NOTES |
---|---|---|
New fields added to database tables used in Battery GOR calculations | Battery GOR Calculations | A new field, CALCULATE_BATTERY_GOR, has been added to the following tables:
A new field, BATTERY_GOR_EXEMPT, has been added to the following tables:
A new field, GOR_ESTIMATED, has been added to the WELL_PRODUCTION_SUMMARIES table. The following fields have been added t o the BATTERY_PRODUCTION_SUMMARIES table:
|
New fields added to database tables used in Facility Consumption calculations | Consumption Calculations | The following fields have been added to the BATTERY_PRODUCTION_SUMMARIES table:
The following fields have been renamed in the BATTERY_PRODUCTION_SUMMARIES table:
A new field, GENERIC_VOLUME , has been added to the following tables:
A new field, ADJUST_THEORETICAL, has been added to the following tables:
|
New field added to database tables used in Battery Water calculations | Battery Water Calculations | A new field, WATER_METER_FACTOR, has been added to the following tables:
|
New field added to database tables used in Oil Pipeline Split reporting | Oil Pipeline Split Reporting | A new field, OVERRIDE_SHIPPER , has been added to the following tables:
|
Known Issues
SUMMARY | NOTES |
---|---|
Microsoft Edge Print pop-up makes Qbyte Metrix Close button unresponsive | Issue: On Qbyte Metrix screens such as the Well Theoretical Summary or Oil Disposition Validations, clicking Print causes the Close or Cancel buttons to become unresponsive. Workaround: The screen must be exited by closing the web browser window. |
STEP01 - Allocations may have an Error message but the Step still completes successfully | Issue: For facilities using Ideal Product Shrinkage it is possible that some Error messages may be generated during the STEP01 - Allocations process, but the overall Step process still show as completing successfully. |
Voucher Status Integration between Qbyte Metrix and Qbyte FM | Issue: The Voucher Status Integration between Qbyte Metrix and Qbyte FM in addition to being enabled in both applications requires the Voucher Type assigned to REVU066 must be METRIX. Workaround: Create a new Voucher Type in Qbyte FM and assign it to REVU066.
|
Copyright© 2024 IFS AB. Copying prohibited. All rights reserved.