Bright Alliance Tech Limited · Shenzhen factory liaison, direct prince@brightalliance.net WhatsApp +86 158 8972 3515
Asset Tracking & Public Services — application environment
Deployment

Asset Tracking & Public Services

Everything the balance sheet owns and nobody can find at 4 pm on a Friday.

Asset tracking is the least glamorous RFID business and the one that pays back fastest, because the baseline is almost always a spreadsheet that nobody trusts. The project is not a reader purchase; it is a count that has to reconcile. That means the tag has to survive the asset, the read point has to match how people actually walk, and the software has to accept a batch upload from a device that was out of coverage for two hours. We quote the handheld and the antenna, and we are explicit about which assets a handheld can find and which ones need a fixed portal.

Who actually makes the purchase

Facilities and estate teams, hospitals and labs, utilities and municipal works, telecom tower operators, and the RFID integrators who deliver the inventory count.

Where these projects stall

Typical software in this stack
SAP FI-AA / EAMMaximoInfor EAMFreshservice / Jira SMGS1 EPC Tag Data Standard
Devices quoted here: 5
Send this requirement
01

The asset register is wrong before the project starts

Most sites begin with 15-30 percent of records that cannot be matched to a physical object. The first pass is always a discovery walk, not a go-live, and the device has to be fast enough that a two-day count does not become two weeks.

02

The tag fails before the reader does

Metal shelves, liquid containers, autoclaves and outdoor poles each break a different tag. On-metal UHF labels, ceramic tags, or a simple printed 2D label with a photo in the record beats an RFID tag that reads at 20 cm.

03

Nobody owns the sync

Basements, plant rooms, tunnels and lift shafts have no signal. Batch mode with a timestamped queue and a duplicate-safe upload is the requirement; real-time sync is a nice-to-have that becomes the reason a count is rejected.

Data flow

How the information actually moves

This is the part that decides the device. Each step below has a different requirement for screen size, scan engine and connectivity.

01Tag and registerEvery asset gets an identity: an on-metal UHF label where it survives, a printed 2D label where it does not, both carrying the same asset number so the record works either way.
02Discovery countA handheld with a 4 dBi circular antenna sweeps a floor in a pass, logging location zone and timestamp. The gap list - records with no read - is the deliverable, not the read count.
03Fixed points where it mattersServer rooms, pharmacy stores and tool cribs get a portal or a shelf antenna so movement is captured without anyone scanning. This is where a handheld stops being enough.
04Move, repair, retireThe same device records transfers, sends an item to repair and retires it, with a photo attached. The audit trail is the product; the hardware just has to not lose it.
05Reconcile and reportCounts export to the fixed-asset register and to the finance period. Anything that cannot be reconciled is flagged rather than quietly written off, which is what auditors actually ask for.
Questions we get

Before you ask

The questions that come up on almost every project in this sector, answered before the first call.

All questions
01UHF RFID or just barcodes?
Barcodes if the assets are few, close together and read one at a time. UHF when the job is finding things: a shelf of 300 tagged items reads in seconds and tells you what is missing, which a barcode never will because you have to see each label.
02What read range is realistic indoors?
A handheld at 2 W with a 4 dBi antenna gives 3-6 m on a well-placed on-metal tag, less through shelving and much less around corners. Vendors quoting 20 m are quoting an open-field number with a fixed reader. Plan the count by zone, not by radius.
03Can this run on the devices we already own?
If they have a UHF module or a 2D imager and a keyboard-wedge or SDK path into your EAM, yes. We will tell you which of your existing units can carry the workload and which will need an external Bluetooth reader instead of a new fleet.
04Can you supply five units for a pilot?
Yes. A pilot is the normal entry point. We quote single units at sample pricing and support the pilot with spare parts on the same order — a spare battery and a cradle, not a pallet.
05Do the Android units ship with GMS?
Most Android models ship with GMS. For builds where Google services must be absent, we supply a GMS-free firmware on the same hardware — say so at the quotation stage, because it is a firmware decision, not a setting.
06What warranty do you give?
One year as standard, covering the unit and the battery against manufacturing faults. Extended cover and advance-replacement terms are available for fleets — ask for them with the quotation, not after the first failure.

Running a asset tracking project?

Send the workflow and the software stack. You will get two models and the caveats, not a catalogue.

Chat with Prince · WhatsApp