Natural Gas Odorant Tank Sizing and Runtime Planning: Capacity, Refill Triggers and Reserve
Updated: 20 hours ago
Tank sizing is not an annual-use calculation with a universal percentage added at the end. A useful plan has to answer several connected questions: how much odorant the system is expected to use during each operating period, how much of the vessel inventory is actually available for service, how long replenishment takes, what reserve the operator requires, and how forecast use will be checked against actual inventory.
Those questions matter for permanent odorization stations, temporary odorizers, commissioning work, bypass service and intermittent-load applications. The result should be a documented operating basis—not a promise that a tank will last a fixed number of days under every condition.
This guide explains the inputs, equations, evidence limits and handoffs that belong in a tank-capacity and refill plan. It does not establish a universal injection rate, tank size, fill limit, reserve percentage or legal-compliance method. BPS provides operational support and documentation; the operator retains responsibility for its requirements, approvals and decisions.
Start with the operating period, not one annual-flow number
A single average flow can hide the periods that control capacity and refill timing. Before selecting a vessel or predicting runtime, divide the project into time buckets that reflect how the system will actually operate. Depending on the application, those buckets may be hourly, daily, shift-based or tied to operating events.
For each period, document:
expected gas volume or flow and duration;
the operator-approved odorant injection basis;
startup, shutdown, zero-flow and restart states;
expected load or source changes;
the anticipated project start and end dates;
delivery lead time, site access and receiving windows;
planned outages, holidays or other replenishment constraints; and
the uncertainty assigned to the forecast.
Use the same standard-volume basis throughout the calculation. If flow, billing and controller records use different base conditions or units, reconcile them before calculating odorant demand. A polished spreadsheet cannot correct inconsistent inputs.
Define nominal, fillable, usable, reserve and unavailable inventory
“Tank capacity” can refer to different quantities. A sound plan labels each quantity instead of treating the nameplate volume as fully available inventory.
Nominal capacity is the manufacturer’s stated vessel size. Maximum permitted fill is the limit established by the applicable equipment documentation, product requirements and approved operating procedure. Measured inventory is the amount indicated by the accepted level or weighing method at a stated time. Usable inventory is the quantity the operator allows to be consumed before replenishment or shutdown action. Reserve inventory is a defined quantity held for an operator-approved contingency. Unavailable or uncertain inventory includes any amount that cannot be credited because of pickup limits, measurement uncertainty, retained product, isolation boundaries or unresolved discrepancies.
These quantities are equipment- and procedure-specific. They should be recorded with their source, units and approval date. Neither the vessel nameplate nor a generic web calculator establishes usable capacity.
Estimate odorant demand with consistent units
When gas volume is stated in standard cubic feet and the approved injection basis is stated in pounds per million standard cubic feet, the planning relationship is:
Expected odorant mass (lb) = gas volume (scf) × injection basis (lb/MMSCF) ÷ 1,000,000
When gas flow is stated directly in MMSCF per hour for a defined interval:
Expected odorant mass (lb) = flow (MMSCF/h) × interval (h) × injection basis (lb/MMSCF)
These equations estimate mass demand from stated inputs. They do not select the injection basis, prove actual delivery or establish downstream odor intensity.
Convert mass to liquid volume only when the current product density and its stated reference conditions are documented:
Expected liquid volume = expected odorant mass ÷ documented density
Do not apply one odorant density to every blend. Use the current supplier documentation for the product in service and keep the units explicit. If density is temperature-dependent or the source states a reference temperature, preserve that condition in the worksheet.
Forecast variable and intermittent gas demand in time buckets
For steady demand, the calculation may be repeated for each day or shift. For variable demand, calculate each time bucket separately and sum the results. This makes peaks, shutdowns and schedule changes visible.
Zero flow deserves its own state. A zero-flow interval may stop calculated gas demand, but it does not automatically resolve odorizer behavior, trapped liquid, controller state, restart logic or downstream verification. Those issues belong in the operating plan and should be coordinated with the low-flow, zero-flow and restart procedure.
For temporary work, the forecast should include mobilization, commissioning, active operation, standby periods and the operator’s demobilization criteria. If the end date is uncertain, show more than one duration scenario instead of presenting a single date as certain.
A useful forecast displays at least a base case and an operator-approved stress case. The stress case should reflect identified uncertainties—such as a longer duration, higher gas use or delayed delivery—rather than an automatic percentage copied from another project.
Convert demand into a refill trigger
A refill trigger should provide enough usable inventory to cover expected consumption while replenishment is being arranged, plus the reserve and allowances approved for that service.
A general planning relationship is:
Refill-trigger quantity = forecast use during delivery lead time + operator-approved reserve + documented allowance for known uncertainty
The relationship is simple; the inputs are not. Delivery lead time may depend on product availability, carrier requirements, site receiving hours, transfer readiness, weather, access and authorization. Reserve may be expressed as mass, liquid volume, operating hours or another controlled quantity. The uncertainty allowance should be tied to named risks rather than a universal percentage.
Translate the trigger into the same observable quantity used in the field, such as an approved level, mass or volume reading. Document who monitors the trigger, who can place the order, who confirms delivery readiness and what escalation applies if the trigger is crossed before replenishment is available.
A fixed 20 percent margin is not a universal standard. It may be too small for one project and unnecessarily large for another. The operator should approve the reserve logic and document why it fits the specific service.
Reconcile forecast, commanded delivery and actual inventory
Runtime planning improves when expected use is checked against independent evidence. One practical inventory relationship is:
Expected ending inventory = measured starting inventory + documented receipts − supported delivered quantity − documented removals or returns
Compare that result with the measured ending inventory for the same boundary and time period. Record the difference and investigate material variance using the operator’s acceptance criteria.
This comparison is not a substitute for downstream sampling or odor-intensity testing. It is an inventory-control check. Controller commands and calculated injection totals, along with pump-stroke records, may show what the system intended to deliver, but they do not by themselves prove that the expected quantity entered the gas stream. A tank-level change also has limits: it may be affected by reading resolution, temperature, vessel geometry, unrecorded transfers or the measurement method.
The reconciliation record should identify the data sources, time stamps, units, corrections, responsible person and any unresolved exception. Where a result is outside the approved tolerance, the plan should define who evaluates it and what other evidence is required.
Treat every level method as evidence with limits
Odorization systems may use sight indications, level gauges, load cells, differential measurements, controller inputs, manual measurements or other methods. Each has a range, resolution, installation basis and maintenance requirement. Manufacturer documentation and the operator’s approved procedure should control how the reading is taken and interpreted.
Thermal imaging can sometimes help screen for a liquid boundary under suitable conditions, but it should not be presented as a universally accurate inventory measurement. A screening image does not automatically establish mass, usable capacity or actual injection.
Record the measurement method beside every inventory value. If a conversion table, vessel geometry or calibration record is required, identify the current controlled source. Do not convert an approximate reading into a more precise result than the method supports.
Size temporary systems around mobilization and demobilization
Temporary odorization projects add logistics that a permanent-station calculation may not capture. The planning package should address:
the usable starting inventory at site acceptance;
refill or cylinder-exchange method and access;
anticipated consumption by operating phase;
delivery lead time and after-hours constraints;
backup or contingency arrangements approved by the operator;
the minimum inventory required to start a planned operating period;
records needed before a refill, exchange or return; and
the operator’s evidence-based demobilization criteria.
The largest available vessel is not automatically the best choice. Capacity interacts with mobilization limits, site space, containment, pressure and connection interfaces, inspection, product handling, transportation and the duration of service. A smaller replenishable system may suit one project; a larger inventory interval may suit another. The decision should be tied to documented project conditions.
Check interfaces beyond liquid capacity
A vessel-volume calculation is only one part of system selection. Before approval, confirm the interfaces that could constrain operation:
odorant product and current safety data;
pressure boundaries and approved transfer method;
containment and vapor-control requirements;
fill connection and delivery access;
area classification, power and communications;
level indication, alarms and data retention;
low-flow, zero-flow and restart behavior;
downstream sampling and verification locations; and
inspection, maintenance and turnover responsibilities.
Manufacturer manuals can show real equipment options and limits, but a tank size or feature offered on one model should not be generalized to every odorizer.
Build the operating and turnover record
A capacity and runtime package should be usable after the initial calculation. Keep the approved basis and the operating evidence together.
Recommended records include:
equipment and vessel identification;
product and current supplier documentation;
nominal, permitted-fill, usable and reserve quantities;
calculation units, standard-volume basis and density source;
time-bucketed gas-demand forecast;
approved injection basis;
refill trigger and lead-time assumptions;
starting inventory and receiving records;
supported delivered quantity;
ending inventory and variance;
alarms, overrides and out-of-range events;
downstream verification references;
open exceptions and corrective actions; and
approval, revision and handoff history.
If the forecast changes, revise the basis rather than silently editing the result. The revision record should show what changed, why it changed and who accepted the new operating plan.
Project data for a BPS review
To review tank capacity, runtime and refill logistics, BPS typically needs the operating period, min/max/zero-flow profile, pressure information, approved odorant blend and injection basis, current vessel and level-method details, usable starting inventory, refill method, delivery lead time, site access, connection information, alarms, documentation expectations and responsibility boundaries.
BPS can help organize these inputs, support temporary odorization planning, reconcile operating records and prepare turnover documentation. Final criteria, reserve, procedures and compliance determinations remain with the operator and its qualified advisers.
Odorization planning support from BPS
For a project-specific capacity and runtime review, call Burgess Pipeline Services at (323) 609-5009. Bring the flow schedule, approved injection basis, product information, usable-inventory definition, refill constraints and desired operating window. BPS will help identify missing inputs and build a documented plan around the actual service conditions.
Frequently asked questions
Is a 20 percent tank-sizing margin an industry standard?
No universal percentage applies to every odorization project. Reserve and uncertainty should reflect the operator’s approved criteria, delivery lead time, demand variability, measurement limits and the consequences of delayed replenishment.
Can one density be used for every natural gas odorant?
No. Density depends on the product or blend and the stated reference conditions. Use current supplier documentation for the odorant in service and keep mass and volume units explicit.
Does a controller total show how much odorant remains in the tank?
Not by itself. A controller total may support commanded- or calculated-delivery records, while tank inventory depends on an accepted measurement method and documented receipts, removals and returns. Compare independent evidence within the same time boundary.
Is tank sizing the same as runtime forecasting?
They are related but different. Tank sizing defines an appropriate capacity and usable inventory for stated conditions. Runtime forecasting estimates how long the current usable inventory may support a changing demand profile before an action point is reached.
When should the refill trigger be set?
Set it early enough to cover forecast use through the expected delivery and transfer window, plus the operator-approved reserve and named uncertainties. Document the observable trigger, responsible roles and escalation path.
