A temporary gas delivery can arrive at the gate on schedule and still leave a project without usable fuel. The trailer may lack the correct pressure-reducing station, the site may not be ready for hookup, or the crew may still be waiting for commissioning checks before gas can flow. For construction managers, utility operators, and industrial teams, delivery performance metrics only matter when they show whether the deployment protected the schedule, maintained service, and avoided downtime.
Temporary CNG and LNG service needs a stricter definition of success than a truck arriving within a promised window. The useful measurement point is operational, not purely logistical: the right gas, equipment, pressure, quantity, documentation, and trained handoff must be available when the site needs them.
Why Standard Delivery Metrics Fail Temporary Gas Projects
A pipeline contractor in West Texas can report a 98% on-time delivery rate from its temporary CNG provider and still have a serious reliability problem. In one realistic operating scenario, the provider's trailer arrived within the agreed window, but it lacked the correct pressure-reducing station. The crew stood idle for 14 hours, waiting for the equipment required to connect and use the gas. The delivery counted as on time. The project experience was a failure.
Arrival isn't the same as readiness
Standard freight dashboards usually answer a narrow question: did the shipment reach the destination by the promised date? On-time delivery, or OTD, measures the percentage of orders delivered within the promised window, calculated as orders delivered on time divided by total orders, multiplied by 100. That definition makes OTD useful for schedule reliability and supplier scorecards, as explained in this overview of on-time delivery metrics.
Temporary gas deployments have more failure points after the vehicle reaches the site. A trailer can arrive without the specified regulator, hose assembly, fittings, monitoring equipment, or documentation. The pad may not be accessible, the electrical connection may be incomplete, or the site contact may not be available to authorize the handoff. None of those failures necessarily change the arrival timestamp.
The service outcome matters more than the vehicle timestamp
A site supervisor doesn't care that a trailer crossed the geofence if the crew can't establish a safe, tested gas supply. For temporary CNG and LNG, delivery should be considered complete only when the required equipment is present, the connection is verified, gas is flowing at the agreed specification, and the responsible site personnel understand the operating procedure.
That broader definition changes the dashboard. It adds site-readiness exceptions, equipment mismatches, commissioning delays, partial fills, and resolution time to the performance conversation. It also shifts accountability toward the people who can prevent failure, including dispatchers, drivers, project managers, site contacts, and commissioning technicians.
Practical rule: Count a deployment as successful when it protects the workfront, not when the trailer merely reaches the address.
The rest of the measurement system should follow that rule. Project managers need indicators tied to usable supply, avoided idle time, and service continuity. A high arrival percentage can remain useful as one diagnostic signal, but it shouldn't be the headline KPI when the project depends on a functioning temporary gas installation.
Core Delivery Performance Metrics for CNG and LNG Services
Start with a small set of measures that dispatchers and site supervisors can act on during the shift. OTIF, first-fill success, commissioning lead time, hookup duration, trailer utilization, and safety performance cover the main reliability questions without turning the dashboard into an inventory of disconnected numbers.
OTIF is the anchor metric. It extends punctuality by asking whether the order arrived on time and in full. The technical definition is the count of orders delivered on time and in full divided by total orders, multiplied by 100, as described in this logistics performance framework. For temporary gas, “in full” must include the contracted gas quantity and the equipment package needed to use it.
| Metric | Formula | What It Reveals |
|---|---|---|
| OTIF delivery rate | Orders delivered on time and complete ÷ total orders × 100 | Whether the supplier met the schedule, quantity, and equipment commitment |
| First-fill success rate | First fills completed without a preventable exception ÷ total first fills × 100 | Whether new deployments become usable without rework |
| Order-to-commissioning lead time | Commissioning timestamp minus order-confirmation timestamp | How quickly demand becomes an operating gas supply |
| Deployment and hookup time | Gas-flow-at-spec timestamp minus trailer-arrival timestamp | Whether site setup, connection, testing, and handoff are efficient |
| Trailer utilization rate | Productive deployment time or delivered capacity ÷ available fleet capacity | Whether fleet size, routing, and swap planning match demand |
| Safety incident frequency | Recordable delivery or site incidents ÷ relevant deliveries or operating exposure | Whether speed and utilization are being achieved without unacceptable risk |
Read the first fill differently by fuel type
For an LNG tanker, first-fill success depends heavily on the delivered liquid quantity, transfer procedure, tank condition, vapor-management steps, and readiness of the receiving installation. For a CNG tube trailer, the usable result depends more directly on pressure, temperature, regulator configuration, connection integrity, and the pressure profile available to the customer.
A shipment can be physically full and still fail operationally if the receiving system can't accept it safely or the pressure-reduction equipment isn't correct. That's why first-fill success should record the reason for every failed or delayed startup, rather than treating all first fills as equivalent.
Use utilization to expose fleet waste
Utilization isn't a vanity measure for the fleet team. Low productive use can indicate excessive spare capacity, poor swap timing, long site waits, inefficient routing, or a mismatch between trailer configuration and customer demand. High utilization can also signal risk if the fleet has no recovery capacity for an outage or equipment failure.
Teams building an objective measurement program can use solving delivery measurement with The OKR Hub to connect operational indicators with accountable objectives. The important design choice is to pair each speed metric with a quality or outcome measure, so faster dispatch doesn't conceal incomplete delivery or unsafe commissioning.
How to Measure and Calculate Each Metric Accurately
Accurate delivery performance metrics begin in the field, not in the reporting layer. If dispatchers, drivers, and site supervisors record different event times or use inconsistent exception codes, the final dashboard will produce precise-looking results from unreliable inputs.
Build the event trail first
The core event sequence should run from request through operating supply:
- Order confirmation: Dispatch records when the provider accepts the request, the requested fuel type, quantity, pressure requirements, equipment package, and promised window.
- Dispatch release: The fleet system records when the assigned trailer and driver leave the depot.
- Arrival: GPS telematics or a geofence records the vehicle's arrival at the approved site.
- Handoff: The driver and site representative complete a digital checklist covering access, equipment condition, connections, and documentation.
- Commissioning: The responsible technician records testing, pressure verification, valve status, and authorization to place the system in service.
- Gas flowing at specification: This timestamp closes deployment and hookup time.
- Electronic proof of delivery: The customer confirms receipt, quantity, equipment, and any exception before the record enters the reporting system.
Match each calculation to the right source
OTIF needs the promised window from dispatch, the actual arrival from telematics, and completeness confirmation from the electronic proof of delivery and handoff checklist. Lead time uses the order-confirmation event and the commissioning sign-off, not the dispatch-release time alone.
Deployment time requires two trustworthy timestamps, arrival and gas flowing at specification. A manual note saying “connected” isn't enough if the site still needs pressure testing or a corrective equipment swap. Digital commissioning forms should require the person completing the check to select the operating status and document any exception before closing the task.
Fill-rate data differs by fuel. LNG quantity should be tied to weighbridge tickets or the approved transfer record. CNG performance should incorporate pressure and temperature readings from the tube trailer and the receiving system, because nominal trailer capacity doesn't necessarily equal usable delivery at the customer's required conditions.
Close the common data gaps
Missing site-readiness confirmations create false supplier failures and false customer failures. Manual timestamp entry creates another problem, especially when a driver records arrival after completing the connection. Geofence-triggered arrival logs, mobile checklists, electronic signatures, and automatic exception codes reduce those gaps.
Fleet management systems should feed trailer assignment, movement, dwell, swap, and availability records into a centralized reporting layer. Safety data must combine driver logs with site inspection reports, because road events and connection-site hazards appear in different operational systems. A daily data-quality check should flag missing commissioning records, impossible event sequences, duplicate deliveries, and open exceptions without an owner.
Industry Benchmarks and SLA Targets for Temporary Gas Delivery
Temporary gas SLAs should reflect the consequence of failure, not copy a parcel carrier's delivery promise. A construction customer may need a planned deployment aligned with a tie-in milestone. A utility responding to an outage may need rapid mobilization and continuous replenishment. An industrial facility managing peak demand may value predictable swaps, accurate quantities, and stable operating pressure more than the fastest initial arrival.
There are no universal benchmark ranges that can be responsibly applied to every CNG or LNG deployment. The right target depends on site access, permitting, equipment configuration, fuel type, route conditions, commissioning requirements, and the customer's cost of downtime. Use the table below as a structure for negotiating measurable service levels, then set the actual thresholds from the project schedule and operating risk.
| Metric | Construction Benchmark | Utility Outage SLA | Industrial Peak Shaving |
|---|---|---|---|
| On-time delivery | Tie arrival to approved workfront and milestone windows | Tie mobilization and replenishment to outage command requirements | Tie scheduled swaps to demand forecasts and tank or pressure limits |
| OTIF | Include gas, regulators, hoses, fittings, paperwork, and trained handoff | Include the complete operating package required for service restoration | Include quantity accuracy, compatible equipment, and usable transfer |
| Deployment time | Measure arrival through gas flowing at specification | Measure mobilization through safe operating supply | Measure trailer or tanker exchange through stable supply |
| Lead-time adherence | Confirm order acceptance, site readiness, and milestone date | Define an emergency response clock and escalation path | Use planned demand signals and replenishment commitments |
| Exception management | Require named owners and recovery plans for each workfront risk | Require immediate escalation for supply, access, or equipment failures | Track recurring swap, quantity, and utilization variance |
Set different promises for different operating modes
Scheduled construction deployments should use milestone-based guarantees, not a single drop target. The contract can identify the required readiness date, commissioning completion, equipment list, and recovery responsibility if the site isn't usable.
Emergency utility work needs a response commitment that covers dispatch, mobilization, arrival, setup, and replenishment. A short arrival promise means little if the supplier hasn't reserved the correct equipment or can't provide an escalation contact when the first connection fails.
Industrial peak shaving needs a replenishment SLA built around the facility's consumption profile and reserve policy. It should define what happens when demand changes, a trailer swap is delayed, or the delivered quantity doesn't match the expected operating requirement.
For broader KPI design, track logistics efficiency with KPIs offers useful context on comparing efficiency measures without relying on one isolated score. Contract terms should also address weather, road closures, unsafe access, customer-caused readiness failures, and force majeure. Those carve-outs should pause supplier penalties only when the event is documented, communicated, and separated from preventable execution errors.
The Hidden Costs That Simple On-Time Averages Conceal
A monthly on-time average can look healthy while the project absorbs expensive failures. The problem isn't that OTD is useless. The problem is that an average gives every miss roughly the same weight, even though a short timing variance and a failed first fill can have completely different operational consequences.
A late CNG delivery can leave a crew waiting beside an unfinished workfront. A missed LNG replenishment can force a utility or industrial operator to consume backup fuel faster than planned. If the deployment supports a critical construction milestone, one unresolved exception can push labor, equipment, inspections, and subcontractor activity into a later window.
Track severity and recovery, not just frequency
A useful exception scorecard starts with three questions:
- How often did something go wrong? Track exception rate by cause, site, route, trailer, fuel type, and supplier.
- How long did recovery take? Measure mean time to resolution from exception creation to restored operating supply.
- What did the failure consume? Record crew standby, equipment rental extensions, rescheduling effort, fuel substitution, and contractual exposure.
The delivery KPI guidance from nShift highlights exception rate, exception-resolution time, WISMO contact rate, and cost per successful delivery as important complements to simple averages. For temporary gas, WISMO-style contacts can appear as repeated calls from a site asking where the trailer is, whether the equipment is correct, or when commissioning will finish.
Calculate the consequence of each exception
A practical failed-delivery cost model adds the direct and indirect consequences:
Exception cost = crew standby cost + equipment rental extension + rescheduling cost + substitute-fuel cost + assessed contractual exposure
The inputs should come from the project controls team and contract records, not from a guessed industry average. A dashboard can then assign greater weight to failures that stop work or threaten service continuity, while recording minor timing variances separately.
Averages answer how often the network misses. Severity-weighted reporting answers which misses can stop the job.
This approach can make performance appear worse after implementation because hidden failures become visible. That isn't measurement failure. It means the team has stopped smoothing away depot variance, failed handoffs, and unresolved exceptions that were already costing the project money.
Building Dashboards and Reporting Cadences That Drive Action
A dashboard should tell someone what happened, what is at risk, and who must act next. A monthly supplier scorecard can't protect a workfront that needs a commissioning decision this morning, so active deployments require a shorter operational loop.
Put the right signals in each view
The real-time dispatch screen should show active order status, assigned trailer, current location, promised window, site-readiness confirmation, equipment package, exception owner, and commissioning state. The dispatcher needs operational facts, not a polished percentage that hides an open connection problem.
Construction project managers benefit from a daily deployment tracker during critical-path work. It should identify tomorrow's demand, access restrictions, required equipment, responsible site contact, and the exact event that closes the deployment. Utility operations teams need an incident-oriented view with open exceptions, replenishment risk, escalation status, and time since the last usable supply. Industrial operators need demand forecasts, trailer availability, projected swap timing, quantity variance, and operating reserve status.
Match reviews to the project phase
- Daily: Review active deliveries, on-time status, site-readiness flags, exceptions, commissioning delays, and next-day demand.
- Weekly: Review lead-time trends, recurring causes, route and depot variance, utilization, cost variance, and supplier recovery performance.
- Monthly: Review OTIF scorecards, vendor comparisons, safety trends, contract exceptions, and systemic corrective actions.
- Post-project: Compare planned versus actual deployment performance, document preventable failures, and carry the findings into future procurement and mobilization plans.
Design alerts around decisions
An alert should identify the condition, the owner, the required action, and the escalation deadline. “Delivery at risk” is weak. “Site access confirmation missing, project manager to confirm before dispatch release” is actionable.
The reporting system should integrate dispatch records, GPS telematics, electronic proof of delivery, fleet availability, site handoff confirmations, and commissioning forms. Blue Gas Express is one mobile natural gas option for temporary CNG and LNG supply, with deployments designed for customers managing construction, maintenance outages, generator commissioning, and similar short-term requirements. Whatever supplier you use, require the same event-level data so vendor comparisons reflect operating outcomes rather than inconsistent reporting methods.
Real-World Applications for Construction and Utility Customers
The strongest use cases treat delivery performance metrics as early-warning systems, not historical reports. A construction team that monitors deployment time and site-readiness exceptions can intervene before a pipeline tie-in window closes. A utility team that tracks exception resolution can direct escalation toward the failure most likely to interrupt service. An industrial operator can compare fill accuracy with trailer utilization and identify whether extra swaps are caused by demand, routing, or poor fleet configuration.
In one construction scenario, a general contractor used deployment-time tracking and site-readiness exception codes to identify a recurring handoff problem before it affected a pipeline tie-in milestone. The intervention avoided a two-week delay and $180,000 in idle crew costs. Those figures are part of the scenario, not a universal benchmark, and the lesson is the measurement design: arrival time alone would not have exposed the risk.
A utility outage example shows why recovery deserves its own measure. During a 72-hour main replacement affecting 4,000 customers, an exception-based scorecard and resolution-time tracking supported 99.2% service continuity. The relevant control wasn't whether deliveries arrived. Operators monitored supply risk, escalated exceptions, and measured how quickly each issue returned the site to stable service.
For industrial peak shaving, fill-rate and utilization records can reveal inefficient trailer swaps during a boiler conversion. In a scenario involving temporary LNG, correcting those swap inefficiencies reduced temporary LNG spend by 15% over six months. That result depends on the facility's demand pattern, fleet plan, contract terms, and operating discipline, so it shouldn't be treated as a standard outcome.
Customers should ask temporary gas providers for granular records covering arrival, equipment completeness, commissioning, quantity, exceptions, resolution, and safety. That data helps project teams prevent disruption before a missed delivery becomes idle labor, an outage escalation, or an avoidable supply cost.
Blue Gas Express provides mobile CNG and LNG solutions for construction projects, utility outages, generator commissioning, and industrial operations that need temporary natural gas while permanent infrastructure is delayed or unavailable. Review your required delivery events, site-readiness checks, and escalation points, then visit Blue Gas Express to discuss a temporary gas deployment aligned with your operating schedule.