equipment
RFID for Cylinder Tracking: What Propane Operators Need to Validate Before Scaling
The first steps propane distributors should take when conducting RFID tracking pilot
By Michael Gillmann
A cylinder that reads reliably on its own can still be difficult to identify when loaded on a truck with dozens of others. For a propane distributor considering a radio-frequency identification (RFID) pilot, that difference will determine whether a project removes scanning work or leaves employees searching for cylinders.
Passive ultra-high-frequency RFID allows a reader to scan cylinder identifiers without lining up each barcode. The tag needs no battery, but its performance still depends on where it is mounted and how the cylinder passes the reader.
At a liquefied petroleum gas filling plant in North America, employees were scanning cylinders individually at arrival, departure and checkpoints. The distributor evaluated tags to reduce that manual work, but dense metal cylinders and variable tag positions were making reliable reading difficult in earlier trials.
The breakthrough came from adapting the tracking system as well as loading arrangements and tag placement to reduce interference from other cylinders and enable hands-free reading as cylinders pass through fixed portals.
Begin With 1 Checkpoint
For a distributor, the first question is which job RFID should improve: counting returned cylinders at receiving, confirming a dispatch load or reconciling stock in a yard. Time spent scanning, checking discrepancies and correcting records will provide a baseline for judging the result.
A fixed reader may suit a repeated movement through a controlled lane. But a handheld reader is more practical for an inventory check or resolving an exception.
The choice depends on how employees already handle the cylinders. If they must unload or rearrange a stack solely to obtain a read, that extra work belongs as a consideration when comparing reader methods.
Validate Tag Attachment
When bonded to loose paint, a tag may come off with the paint even if the bond itself holds. Surface preparation, coating condition and the specified installation procedure therefore belong in the trial. Record the time needed to prepare and tag a cylinder as well as the result.
Cylinder curvature limits the area available for mounting an RFID tag. A bendable tag can follow a curved surface, while a rigid, rugged tag needs a suitable mounting area and protection from handling. A useful comparison is how each construction fits the cylinder designs and loading arrangements in the fleet.
Placement also affects exposure to impacts and contact with other cylinders. A protected position will improve survival but can make the tag harder to read on a loaded truck. Test candidate positions with the operators who handle the cylinders. Keep markings and access to valves unobstructed and have the cylinder owner approve the attachment approach if needed.
The next test involves cleaning and refurbishment. Will the tags remain in place, be protected or be replaced during those processes? Exposure to a particular wash or refinishing process should be checked separately from ordinary outdoor use. A short pilot can reveal early attachment failures, but it cannot establish years of service life.
Read the Intended Cylinders
A portal needs to identify the cylinders moving through, in bulk and at speed. But extending read distances can capture nearby inventory. Testing with tagged cylinders beside the lane, as well as those passing through it, will help fine-tune the tracking system.
Antenna position, power settings and the boundaries of the read area give the reader provider ways to address that trade-off. Tests need to include different cylinder orientations, load arrangements and normal travel speeds. One cylinder may respond repeatedly while another is unread, so the total number of tag responses only tells part of the story.
Comparing the distinct cylinder identities recorded against the known contents of each test load will create a baseline, with missed cylinders and unwanted reads logged separately.
How can the team tell a placement problem from an isolated damaged tag? Have the team note where the missed cylinders sat in the load. How should the team select readers and mobile devices? Take into account the operating location and any hazardous-area requirements. It will save your equipment layout and even your pilot budget.
Connect Each Cylinder to the Right Record
When a cylinder appears overdue, operators need to check its last recorded dispatch and look for a missed return transaction before treating it as a lost asset. Comparing time away from the plant can also help identify slow return loops. Both tasks will depend on connecting each movement to the correct cylinder record.
Which identifier should connect the tag to the cylinder record? A tag’s electronic product code memory is most commonly used. It can be programmed with a unique number defined by the distributor or a standardized asset identifier. Your own internal identification scheme may suit a fleet managed within one system. But a standardized format becomes the norm when identification needs to be shared with partners in the value chain or understood by different software systems.
Another option is a serialized tag identifier (TID), the chip’s factory-assigned identity. This avoids allocating the identifier yourself, but each still needs to be associated with the cylinder record. Verify that the selected chip provides a unique serialized TID and that the readers and software capture it reliably at the intended checkpoint.
Whichever approach is selected, verify the link to the cylinder record during installation, along with any printed identification (on the tag or separate). For operator-assigned numbers, agree who allocates them and how repeat tag orders avoid duplicates. Two cylinders sharing one identifier can end up with their movements recorded in the same history, even when the readers work correctly.
The software also needs to register what happened. At receiving, the reader location, direction of travel and expected return transaction can help distinguish arriving cylinders from nearby stock.
As for recording a return, that record does not establish that a cylinder is filled, inspected or ready for dispatch. Those statuses require their own process records.
Repeated reads and incomplete loads need agreed handling and exception rules in the software. Employees need a clear way to resolve an unread cylinder or a discrepancy before closing the transaction.
What happens when a tag is damaged or removed? Its replacement should reconnect to the existing cylinder record. The old identifier should no longer create conflicting transactions. Testing this handover protects the usefulness of maintenance history and return records beyond the life of the first tag.
All these decisions depend on reliable handoff records, while RFID does not provide continuous tracking between checkpoints and sites.
Define Scaling Criteria Before the Pilot
A good pilot will use a representative mix of cylinder sizes, surface conditions and load arrangements. It will ensure the selected movements are repeated through ordinary handling cycles as well as busy operating periods. And it will check both the physical tag and the resulting records.
What if a load needs several stops and retries before every cylinder is recorded? Those interventions should be counted as part of the result: how often employees stepped in and how long each intervention took.
The completed transaction is then reconciled against the cylinders that actually moved. The key here is setting acceptable limits before the pilot begins, regarding missed identities, unwanted reads, attachment failures and manual corrections.
What should be included in the cost comparison? I recommend taking into account installation labor, readers, software integration training and replacement tags. The pilot’s measured operating effort can then be compared with the earlier baseline, making savings dependent on how much scanning and reconciliation work actually disappears.
More importantly: When exactly should you scale? Expansion should take place once the pilot produces dependable records with an acceptable handling burden. The next site can then receive a documented setup and a clear exception process, with any differences in racks or loading methods checked before deployment.
The goal is for your team to finish an ordinary working shift with records they can trust and fewer discrepancies to resolve.
Gibster - stock.adobe.com
