View end user daily metered volume¶
The End User Daily Metered Volume screen is used to view, analyze, and validate daily metered volume data for end users across a selected date range. This screen provides a day-level breakdown of usage, deliveries, imbalances, adjustments, and related attributes, enabling accurate operational review and billing validation.
It is commonly used for daily volume analysis, imbalance review, rate validation, and audit purposes.
Prerequisites¶
Before working with the End User Daily Metered Volume screen, ensure the following prerequisites are met:
- The user has add or modify permissions for the End User Daily Metered Volume screen.
- The LDC is configured and active.
- End users and related accounts are configured.
- Daily volume data exists for the selected date range.
- Rate, rider, and weather zone configurations are available.
Procedure to view end user daily metered volumes¶
Step 1: Navigate to the End User Daily Metered Volume screen¶
- Log in to the nGenue application.
- Use the Search icon and enter End User Daily Metered Volume in the search bar.
-
Double-click End User Daily Metered Volume to open the End User Daily Metered Volume (Volume Management) screen.

-
The screen is divided into two main sections:
Step 2: Define end user volume query criteria¶
-
Use the End User Volume Query section to control how daily volume data is retrieved.
Fields Description One End User for Many Days Retrieves daily volume records for a selected end user across a date range. All End Users for One Day Retrieves daily volume records for all end users for a specific gas day. LDC Select the Local Distribution Company from the dropdown. Pool Filter volumes by pool, if applicable. Rate / Rider Filter volumes based on rate or rider configuration. Pipeline Filter volumes by pipeline. Marketer Filter volumes by marketer. End Users (Active Only) Select the end user whose daily volumes are displayed. Date Range Defines the start and end dates for which daily volume data is retrieved. -
Click Load Volumes to retrieve the matching records.
Step 3: Review end user volume records¶
-
The End User Volume Records section displays daily volume data in a grid format. Each row represents a single gas day for an end user.
Fields Description Date Gas day for which volume data is displayed. Account Account number associated with the end user. Net Usage Net usage calculated for the gas day. End User Name of the end user. OV Code Override code applied to the volume, if any. Pool Realloc Pool reallocation volume applied to the day. Grp Balanced Delivery Group-balanced delivery volume. Used Bal Svc Indicates usage of balancing services. Cash Outs Cashout volumes applied for the day. Total Misc Delivery Miscellaneous delivery adjustments. Fuel Loss Fuel loss volume applied. End User Trades Trade volumes associated with the end user. LDC Supplied Volume supplied by the LDC. Net Delivery Net delivered volume for the day. Final Imbalance Final imbalance after all adjustments. Day Fac Day factor used in calculations. Rate Rider Rate or rider applied for the gas day. End User Status Status of the end user on the gas day. Weather Zone Weather zone applied to the end user for the day. -
The grid supports sorting, filtering, and aggregation to assist with volume validation and analysis.

Icons available on this screen¶
Toolbar icons¶
Left-side action icons¶
Key points¶
- This screen provides day-level visibility into end user volume data.
- Daily volumes directly impact billing, cashouts, and imbalance calculations.
- Query modes allow flexible retrieval across days or end users.
- Weather zones and rate riders influence volume calculations.
- Export and grid tools support audit, validation, and reporting needs.
Summary¶
The End User Daily Metered Volume screen delivers a comprehensive and auditable view of daily end user volume activity. By combining flexible query options, detailed daily metrics, and powerful grid tools, this screen supports accurate usage analysis, billing validation, imbalance review, and operational decision-making within nGenue.


