Distinguish the delivery configurations
List the road vehicles and the work each driver performs. If the operation includes both cylinder routes and bulk deliveries, keep them separate in the equipment review and sample-day worksheet. The same business name does not make two vehicle connections equivalent.
Product pressure, gas identity, cylinder custody and customer inventory are outside the driver-log scope. Confirm those systems and any proposed integration independently.
Industrial gas delivery evaluation worksheet
| Configuration field | Evidence to bring |
|---|---|
| Cylinder-route vehicle | Engine, connector, mobile device and repeated-stop duties |
| Bulk-delivery vehicle | Road-truck details and driver responsibilities during delivery |
| Spare vehicle | Separate compatibility and parked handoff check |
| Office review | Which staff need access to each driver’s records |
Bring the actual truck configuration
Ask for the vehicle selection and log review described in the Factor PT30 manual on the exact proposed version. Record which configurations were demonstrated and which still need a real-vehicle test.
Have the carrier’s responsible reviewer assess cargo and operational requirements separately. Do not infer hazardous-material classification, pressure monitoring or cylinder tracking from an ELD connection.
For the broader fleet discussion, see tanker. Use the ELD rollout checklist to assign training and review responsibilities, and check ELD applicability for the actual operation.
Industrial gas delivery questions
Can one successful bulk-truck test cover the cylinder-delivery fleet?
Only if the relevant configurations have been shown to be equivalent; otherwise test them separately.
Does the ELD track individual cylinders automatically?
No such capability is included in the driver-log scope described here.