A gas day is not the same as a calendar day, and that single fact trips up more measurement and reporting work than almost anything else in gas accounting. It is a fixed 24-hour window, usually starting at 9:00 a.m. rather than midnight, over which pipelines nominate, schedule, and settle gas volumes. This guide explains what a gas day is, why the boundary sits where it does, and how flow computers and SCADA systems must be aligned to it to avoid volumes landing in the wrong day.
Gas Day in one line: A gas day is a standardized 24-hour period used for scheduling and accounting gas flow, most commonly beginning at 9:00 a.m. in one time zone and running to 9:00 a.m. the next morning. Flow computers accumulate volume, energy, and quality data into this window and produce a daily record aligned to it, so that nominations, deliveries, and imbalances are all measured against the same clock rather than against the calendar midnight boundary.
The gas day exists because pipeline gas has to be scheduled ahead of time, and scheduling needs a common boundary that everyone on the pipe agrees on. Rather than roll the books at midnight, when control-room staffing and business processes are thin, the industry settled on a morning start so that nominations can be submitted, confirmed, and adjusted during business hours before the flow period begins. The 9:00 a.m. start is the most widely used convention on North American interstate pipelines.
The exact clock time is less important than the fact that it is fixed and shared. What matters is that a delivery credited to a given gas day is bounded by the same start and end instant everywhere along the transaction - producer, gatherer, transporter, and buyer. If one party's meter rolls at midnight and another's rolls at 9:00 a.m., their daily totals will never reconcile even when the physical gas is identical.
A gas day is also usually labeled by the calendar date on which it begins. So the gas day dated the fifteenth actually spans from 9:00 a.m. on the fifteenth to 9:00 a.m. on the sixteenth. That labeling convention is a frequent source of off-by-one confusion when someone compares a gas-accounting report to a calendar-day report and the totals do not match.
In the field, the gas day is enforced by the flow computer at each meter run. The device continuously integrates flow rate into volume, but it snapshots and closes out a daily record precisely at the configured contract-hour boundary. At that instant it freezes the day's accumulated volume, energy, average pressure, temperature, and heating value, then starts a fresh accumulation for the next gas day. This daily record is what feeds gas accounting and custody-transfer settlement.
Two settings on the flow computer control this: the contract hour, which sets when the day rolls, and the time zone, which anchors that hour to real time. If either is wrong, the closed record covers the wrong 24 hours. A meter set to roll at midnight local time will attribute the nine hours before 9:00 a.m. to the wrong gas day, silently shifting volume between two days' books even though the total over a long period still ties out.
Daylight-saving transitions add a further wrinkle. On the spring-forward and fall-back days, one gas day is effectively 23 or 25 clock hours long depending on how the flow computer is configured to handle the shift. Well-designed devices keep the contract hour anchored consistently so the accounting is not distorted, but a misconfigured clock can produce a short or long day that shows up as an apparent imbalance.
When flow-computer data is pulled into a SCADA or cloud monitoring platform, the daily rollup must respect the gas day, not the server's midnight. This is a common place for reporting errors to creep in: the flow computer correctly closes its record at 9:00 a.m., but a naively built dashboard sums the hourly or interval data from midnight to midnight and reports a number that disagrees with the official meter record. Both are internally consistent, yet they describe different 24-hour windows.
A cloud SCADA such as Merobix avoids this by reading the flow computer's own daily record where possible and, where it rebuilds daily totals from interval data, by applying the same contract hour and time zone the meter uses. The goal is that the volume a field operator sees on a daily production screen matches the volume that appears on the gas accountant's statement to the penny, because both are bounded by the identical gas day.
For operators, the practical discipline is to make sure every meter, RTU, and reporting layer shares one definition of the gas day. When a well or facility shows a puzzling day-over-day swing, one of the first things to check is whether a device was recently swapped or reconfigured and its contract hour reset to a default. A single mis-set boundary can make a perfectly healthy well look like it lost a chunk of production one day and gained it back the next.
Pipeline gas is scheduled in advance, and the industry adopted a morning boundary so nominations can be submitted and confirmed during business hours before the flow period begins. The 9:00 a.m. start is the most common North American convention, though what matters most is that everyone in a transaction uses the same fixed boundary.
A calendar day runs midnight to midnight, while a gas day is a fixed 24-hour accounting window that usually runs 9:00 a.m. to 9:00 a.m. and is labeled by the date it starts. Because the boundaries differ, a gas-accounting daily total and a plain midnight-to-midnight total for the same date will not match.
The daily record will cover the wrong 24-hour window, shifting volume between two adjacent gas days and creating apparent imbalances even though the long-run total still ties out. The two settings to verify are the contract hour, which sets when the day rolls, and the time zone that anchors it, along with correct handling of daylight-saving transitions.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.