Low-Flow Natural Gas Odorization: Operating Envelope, Zero Flow and Restart Verification
Updated: 2 days ago
Low-flow odorization is not simply a high-flow setpoint turned down. At a municipal gate, master-meter system, private campus, RNG interconnection or temporary gas supply, demand may cycle below an odorizer's stable control range, fall to zero and restart abruptly. Those transitions affect gas-flow measurement, the timing of odorant delivery, mixing, sample timing and the meaning of downstream results.
A controller command can show what the system intended to deliver. It does not, by itself, prove that odorant moved through the injection path or arrived at a representative downstream location. A defensible plan connects the operating state, gas-flow input, calculated command, physical-delivery evidence, odorant inventory and downstream verification.
The operator remains responsible for defining applicable requirements and accepting the method. Burgess Pipeline Services provides operational support and documentation, not legal advice.
Start with operating states, not one minimum-flow number
"Minimum flow" is often treated as a single value. Real sites behave in several distinct states:
steady flow within the normal operating range;
minimum sustained flow;
intermittent demand with repeated starts and stops;
zero flow or no verified consumption;
restart and ramp-up after a no-flow period;
rapid changes between sources, gates or load blocks; and
loss, freezing or invalidation of the flow signal.
Each state should have an approved control response and a verification method. A unit that performs well at a low steady rate may behave differently when the same daily volume arrives in short cycles. The project plan therefore needs both the magnitude of flow and its time pattern.
Build a verified operating envelope
Before selecting or mobilizing an odorization method, document the expected operating envelope:
minimum, normal and maximum standardized gas flow;
pressure and temperature ranges at the injection point;
expected duration and frequency of zero-flow periods;
startup, shutdown and ramp behavior;
gas source, composition and operator-approved odorant blend;
required injection basis and the standard conditions used for gas volume;
flowmeter type, signal, update rate, totalization and signal-loss behavior;
injection point, mixing path and representative verification locations;
available power, communications and area classification;
odorant storage, refill access and containment;
alarm routing, response ownership and backup plan; and
required logs, reports and turnover records.
The equipment review should then address minimum controllable delivery, maximum injection pressure, repeatable cycle or batch size, response time, check-valve and injection-point behavior, logging, alarms and the evidence available to confirm physical delivery. Do not infer the usable project range from a nameplate maximum or a controller display alone.
Separate gas-flow measurement, command and actual delivery
A low-flow verification chain has several layers:
The gas meter measures or estimates standardized volume.
The controller converts that input and the approved injection basis into a command.
The actuator, pump or valve responds.
Odorant physically moves through the injection path.
Tank mass or level changes over a suitable reconciliation period.
Representative downstream results show what reached the operating system.
These layers should use synchronized timestamps and consistent units. Confirm the gas-flow standard conditions and time basis before comparing a gas totalizer with odorant inventory. When demand is intermittent, a short spot check can be misleading if it does not cover a complete operating cycle.
Reconcile commanded injection with independent delivery evidence and inventory over a meaningful window. Investigate unexplained differences instead of assuming that one signal validates the entire chain. For a deeper reconciliation workflow, see BPS's guide to odorant injection verification.
Define zero-flow behavior before startup
Zero flow is an operating state, not a performance claim. Depending on the system and piping arrangement, continued actuation without verified gas movement can accumulate odorant in tubing or at the injection point and affect the next restart. The approved response may be to inhibit delivery, hold a pending dose, use controlled batch logic, alarm for operator action or follow another equipment-specific procedure.
Define the following before mobilization:
what constitutes zero or invalid flow;
whether the command is inhibited, accumulated or discarded;
the maximum permitted held or deferred dose;
how a false flow signal is detected;
what happens after power or communications loss;
who authorizes a manual intervention; and
what evidence is required before normal automatic operation resumes.
Avoid a universal restart delay. Travel time, mixing, pipeline volume, flow path and demand determine when a downstream sample represents the restarted condition.
Verify restart and ramp-up as a transition
A restart check should capture the transition, not just a later steady-state reading. Record:
the time gas flow returned and when the signal became valid;
gas flow, pressure and the selected source or path;
controller command and control mode;
physical-delivery evidence;
tank level or mass before and after the review window;
alarms, overrides and manual actions; and
downstream results after sufficient travel and mixing time.
If flow ramps through multiple ranges, confirm the system crosses between control modes without an unexplained delivery gap or concentrated release. Any acceptance limits and corrective actions should come from the operator-approved plan and applicable equipment documentation.
Use controlled batching only within an approved plan
When the required average dose is below a system's repeatable continuous-delivery range, controlled batching may be considered. The plan should specify the accumulation basis, minimum repeatable batch, maximum deferral time or quantity, trigger conditions, no-flow behavior, interlocks and restart limits.
Batching changes the timing of delivery. It does not remove the need to evaluate mixing, travel time and representative downstream results. A sample collected too early may reflect gas that entered the system before the batch, while a poorly selected location may miss the active flow path.
Match verification locations and timing to the operating path
Low-flow systems can have long residence times and changing flow paths. Record which source, gate, regulator run or load block was active when each sample was taken. For looped, multi-source or master-meter systems, select locations that represent extremities, vulnerable paths and actual demand patterns rather than relying only on the odorizer outlet.
Document the sample point, date and time, gas flow, pressure, active path, instrument identification and status, test method and any conditions that affect interpretation. Keep odorant concentration measurements distinct from perceived odor-intensity or gas-in-air tests. They answer related but different questions.
For U.S. systems where 49 CFR 192.625 applies, the regulation addresses readily detectable gas, introduction without wide variations and periodic sampling. The operator should determine applicability, procedures and acceptance criteria for the specific system.
Build an alarm-response matrix
A usable alarm plan says more than "alarm present." Assign an owner, immediate response, confirmation step and required record for conditions such as:
no, stale or implausible gas-flow signal;
an injection command without corroborating delivery evidence;
unexpected tank or inventory movement;
high or low delivery indication;
loss of power or communications;
abnormal injection pressure or differential;
a downstream result outside the approved range; and
an odor complaint or possible overodorization event.
Setpoints and delays should be project- and equipment-specific. The response matrix should identify when automatic operation may continue, when manual verification is required and when escalation or shutdown is required under the operator's procedures.
Temporary and mobile low-flow project data
For temporary odorization, responsibility boundaries matter as much as equipment selection. The data sheet should identify who provides and validates the flow signal, who supplies odorant, who changes settings, who responds to alarms, who performs downstream checks, who reconciles inventory and who approves demobilization.
BPS can support equipment-only rental, hybrid support or turnkey field service. A low-flow request should include the operating states, flow and pressure ranges, zero-flow pattern, duration, injection basis, power and communications, area classification, connection details, sample locations, staffing expectations, refill access, backup requirements and turnover deliverables.
Define acceptance and turnover before demobilization
Do not use an arbitrary number of operating days as the only exit criterion. A turnover package should show which operating states were observed, whether gas and odorant totals were reconciled, which representative downstream paths were verified, how alarms and restart behavior were checked, what settings and exceptions remain, and who accepted the results.
A temporary system should be removed only after the operator-approved exit criteria are met and the permanent arrangement and downstream condition have been verified for the relevant operating paths.
Low-flow odorization support from BPS
Burgess Pipeline Services helps operators plan low-flow and intermittent-flow odorization, define control and alarm responsibilities, operate temporary systems, reconcile delivery evidence and document downstream verification.
For project review, provide the expected operating states, standardized flow and pressure ranges, schedule, odorant basis, flow signal, injection and sample locations, utilities, communications, area classification, staffing model and required turnover records. Call (323) 609-5009 to discuss equipment-only, hybrid or turnkey support.
Frequently asked questions
Does zero gas flow mean an odorizer should keep dosing?
There is no universal answer. The approved response depends on the system, injection arrangement and operating plan. Blind continued dosing without verified gas movement can create accumulation or restart problems, so zero-flow logic, held-dose limits and restart verification should be defined in advance.
Does a controller setpoint prove odorant was delivered?
No. A setpoint or command records intent. Delivery should be corroborated with suitable physical evidence, inventory reconciliation and representative downstream verification.
Is odorant concentration the same as perceived odor intensity?
No. Instrument concentration and human odor-intensity or gas-in-air testing provide different evidence. The operator should select methods that match the requirement and document how results are interpreted.
When can a temporary low-flow odorizer be removed?
After the operator-approved exit criteria are met. Those criteria should address the permanent arrangement, relevant operating states, representative downstream verification, documentation and any unresolved exceptions rather than relying only on elapsed time.
