Portable Natural Gas Odorizer Project Requirements and Deployment Planning
- Jul 9
- 5 min read
Updated: Aug 2
A portable natural gas odorizer should be selected and configured from the actual operating requirements, not from one maximum-flow or pressure number.
A useful deployment review considers the purpose of temporary odorization, minimum and maximum flow, pressure, injection basis, connection points, odorant supply, controls, monitoring, downstream verification and field logistics.
The project team should resolve these inputs before mobilization whenever possible. Missing information can lead to equipment changes, delayed installation or a verification plan that does not represent the operating system.
Burgess Pipeline Services provides operational support and documentation, not legal advice.
Define Why Temporary Odorization Is Needed
Begin with the operating objective:
Permanent odorizer outage
Planned maintenance or bypass work
Pipeline commissioning
Pipeline pickling or conditioning
Odor-fade remediation
Temporary CNG or other fuel-gas supply
RNG or biogas interconnection
Source or gate change
Temporary industrial or campus service
Permanent-system startup and transition support
The objective affects the required deployment period, connection arrangement, operating records, verification locations and exit criteria.
A maintenance bypass may require rapid transfer of responsibility between permanent and temporary systems. A conditioning project may instead require repeated downstream observations across several operating cycles.
Confirm the Complete Gas-Flow Range
The project data should identify:
Minimum expected flow
Normal operating flow
Maximum expected flow
Zero-flow periods
Intermittent or cyclic demand
Startup and shutdown transitions
Flow units and standard conditions
Flow-data source
Expected signal update rate
Known uncertainty or unavailable data
Manual or fallback operating basis
Maximum flow alone is not enough.
Low flow, zero flow and rapid transitions can affect the suitable injection method and control strategy. The project team should also distinguish recorded gas volume from instantaneous flow and ensure all units use a consistent basis.
Document Pressure and Connection Conditions
Provide:
Minimum operating pressure
Normal operating pressure
Maximum operating pressure
Applicable design or allowable pressure
Expected pressure transitions
Injection-point pressure
Available pressure differential
Sample-point pressures
Connection sizes and types
Valve and isolation arrangement
Tubing or hose requirements
Distance from equipment to injection point
Distance from equipment to sample points
Pressure ratings should be checked for every component in the proposed connection path. A pressure rating for the main odorizer does not establish the suitability of every hose, fitting, regulator or sample connection.
Physical installation and isolation must follow the operator's approved procedures and site requirements.
Establish the Odorant Basis
Document:
Operator-approved odorant or blend
Current safety data sheet
Approved injection basis
Available starting quantity
Storage arrangement
Expected consumption
Refill method
Transfer responsibilities
Final residual-odorant responsibility
Material-compatibility review
Required containment and odor-control measures
Do not assign one odorant, density or injection rate to every project.
Where 49 CFR §192.625 applies, the regulation addresses detectability, suitable odorant characteristics, introduction without wide variations and periodic sampling. It does not prescribe one portable equipment configuration.
Define the Flow Signal and Control Basis
If proportional-to-flow control is required, identify:
Flowmeter or source system
Signal type
Minimum and maximum signal values
Engineering-unit scaling
Update frequency
Signal ownership
Communication protocol when applicable
Behavior during signal loss
Zero-flow behavior
Manual fallback method
Authority to change the injection setting
The commissioning review should confirm that the displayed flow, totalized flow and controller units agree with the operator-approved basis.
A controller command does not independently prove that odorant moved through the injection path or reached downstream locations.
Review Power, Communications and Area Requirements
Project planning should establish:
Available electrical supply
Battery or backup expectations
Solar suitability when considered
Communications coverage
Remote-access requirements
Alarm-notification recipients
Required local controls
Hazardous-location determination
Environmental enclosure requirements
Temperature and weather conditions
Flooding, drainage or vehicle exposure
Grounding and bonding requirements
Physical and cybersecurity access controls
Hazardous-location suitability must follow the documented site classification. It should not be assumed solely because equipment is portable.
Remote monitoring should also use a controlled connection appropriate for operational technology. A public HMI or PLC login is not a complete remote-access design.
Define Alarms and Response Responsibility
A temporary deployment plan should identify which conditions are monitored and who responds.
Potential conditions include:
Flow-signal loss
Low or unavailable odorant supply
Injection-path issue
Controller or communication fault
Power loss
Unexpected operating mode
High or low downstream result
Inventory discrepancy
Unauthorized configuration change
For each applicable condition, document:
Detection method
Alarm threshold or trigger
Local or remote notification
Responsible person
Required response
Authority to adjust operation
Escalation path
Required record
Thresholds and responses should come from the operator-approved plan, not a generic online matrix.
Plan Odorant Runtime and Refill Logistics
Runtime planning should use compatible project inputs:
Recorded or forecast gas volume
Approved injection basis
Odorant density when required
Usable starting inventory
Expected operating period
Refill quantity and delivery lead time
Minimum reserve
Tank measurement method
Uncertainty in flow and inventory
Standby and contingency requirements
Do not treat a calculated runtime as a guarantee. Flow, operating duration, injection settings, transfers and measurement uncertainty can change actual use.
A refill plan should identify who monitors inventory, who authorizes delivery and what occurs if the available quantity approaches the operator-approved action point.
Select Representative Verification Locations
Verification should not be limited to the injection point.
The plan may need to address:
Downstream extremities
Low-flow branches
Alternate gates or sources
Looped-system configurations
Recently installed or conditioned segments
Large or variable loads
Locations affected by flow-direction changes
The handoff point to a permanent odorizer
Operator-designated customer or facility locations
Odorant-concentration measurements and gas-in-air odor-intensity tests answer different questions. The project record should identify the method used, sample conditions, location and operating configuration.
Neither method replaces combustible-gas detection or an approved leak-investigation procedure.
Plan Mobilization and Site Access
Before scheduling the deployment, confirm:
Site address and responsible contact
Required mobilization date
Site-access hours
Operator orientation and permitting
Equipment placement area
Vehicle, lifting or unloading access
Available working clearance
Injection and sample-point readiness
Required hoses, tubing and adapters
Odorant-delivery access
Containment and drainage conditions
Weather protection
Communications coverage
Site security
Staffing and monitoring expectations
Photographs, drawings and connection details can identify conflicts before equipment reaches the site.
Define Backup and Contingency Requirements
A contingency review may consider:
Required standby equipment
Spare power or communications
Alternate flow signal
Manual operating basis
Additional odorant inventory
Replacement hoses or connection components
Response-time expectations
Permanent-system fallback
Conditions requiring temporary operation to pause
Remobilization requirements
Backup planning should reflect the consequence and duration of an interruption. Not every project requires the same level of redundancy.
Build the Deployment and Turnover Record
A useful record may include:
Approved project scope
System boundary and operating objective
Confirmed flow and pressure range
Odorant and injection basis
Connection drawings or photographs
Flow-signal and controller configuration
Equipment and instrument identification
Calibration and functional-check records
Starting inventory
Alarm and response matrix
Verification locations and methods
Operating and event logs
Refill and transfer records
Deviations and corrective actions
Transition or exit criteria
Responsible-party and operator acceptance records
The record should identify limitations and unresolved information rather than implying that every possible operating condition was demonstrated.
Portable Odorization Support From BPS
Burgess Pipeline Services can evaluate qualifying temporary odorization projects using the confirmed operating data, site requirements and requested verification scope.
BPS's currently approved public operating specification is 0-70 MMSCF/H at 0.5 lb/MMSCF. Actual deployment eligibility also depends on pressure, minimum and intermittent flow, connections, odorant, controls, site classification, utilities and documentation requirements.
Send the project location, purpose, schedule, flow and pressure range, odorant basis, connection information, power and communications availability, proposed verification locations and required operating support, or call (323) 609-5009.
BPS provides operational support and documentation, not legal advice.
Frequently Asked Questions
Is Maximum Gas Flow Enough to Select a Portable Odorizer?
No. Minimum, zero and intermittent flow, pressure, injection basis, signal availability, connections and verification requirements also matter.
What Information Should Be Provided for an Odorizer Rental Request?
Provide the operating objective, location, schedule, flow and pressure range, odorant basis, connection details, utilities, monitoring expectations and proposed downstream verification points.
Does a Normal Controller Screen Prove Odorant Delivery?
No. Controller activity should be compared with available delivery evidence, inventory movement and downstream results.
Should Exit Criteria Be Defined Before Mobilization?
Yes. Defining the permanent-system readiness, verification and handoff requirements early helps prevent an arbitrary rental-period end date from becoming the only demobilization criterion.
