4  RFID Tag Type Selection

4.1 Start With the Story

A tag choice is really a promise about power, distance, surface, memory, cost, and lifetime. A passive label on a carton, a battery-assisted tag on an asset, and an active beacon on equipment all create different evidence and different maintenance obligations.

Use this chapter to choose the tag from the job backward. Name the object, read zone, material, handling, memory, and replacement path first, then decide which tag type can prove the claim without hiding an operational cost.

4.2 In 60 Seconds

RFID tag type is a workflow decision. Passive tags fit controlled read zones where the reader energizes the tag. Battery-assisted passive tags add onboard power for sensing or logging while still using reader-driven communication. Active tags use their own transmitter or beacon behavior when the asset must report from an area rather than only at a checkpoint. The best choice is the one that can be piloted with the real object, material, mounting method, reader layout, battery plan, privacy boundary, and exception process.

Phoebe’s Field Notes: What The BAP Cold-Chain Tote’s Coin Cell Actually Budgets

Phoebe’s Why

“Battery-limited” in this chapter’s service-life row is a real number, not a label. A coin cell’s printed mAh is a charge budget; multiplying by its terminal voltage turns it into the energy the tag’s electronics can actually spend, and that voltage is not fixed – it sags under load by the current times the cell’s own internal resistance, and it drifts down slowly on the shelf from self-discharge even between reads. Both effects get worse together on a refrigerated cold-chain tote: cold measurably raises a coin cell’s internal resistance, so the exact same sensing or backscatter current pulse that would sag safely at room temperature can sag much harder inside the very cold room the tag is supposed to be monitoring.

The Derivation

Charge to energy conversion at nominal voltage \(V\):

\[E_{Wh} = Q_{Ah}\times V\]

Terminal voltage under load, from open-circuit voltage \(V_{oc}\) and internal resistance \(R_{int}\):

\[V_{term} = V_{oc} - I\,R_{int}\]

Self-discharge over time \(t\) at a fractional monthly (or yearly) rate \(r\), compounding:

\[Q_{remaining}(t) = Q_0\,(1-r)^{t}\]

A defensible usable-capacity budget stacks self-discharge with a safety headroom to a minimum operating cutoff voltage:

\[Q_{usable} = Q_0 \times (1-r)^t \times f_{cutoff}\]

Worked Numbers: A CR2032-Class BAP Sensor Tag Against This Chapter’s Own 24-Month Interval

• Nameplate: catalog-typical CR2032, \(Q_0=225\) mAh, \(V_{oc}=3.0\) V \(\Rightarrow E = 0.225\times3.0=0.675\) Wh.
• Derating to this chapter’s own 24-month service interval: catalog-typical self-discharge \(\approx1\%\)/year gives \((1-0.01)^2=0.980\) remaining; with a \(0.85\) cutoff-headroom factor, usable \(=225\times0.980\times0.85=187\) mAh.
• Average-current budget that fits inside 24 months (17,520 hours): \(187\text{ mAh}/17{,}520\text{ h}=10.7\,\mu\)A – this is the physical reason a BAP sensor tag must spend almost all of that interval asleep, only waking briefly at reader handoffs, matching the chapter’s own “battery powers local electronics” framing rather than a beacon duty cycle.
• Sag during a catalog-typical 15 mA sensing/backscatter pulse: at a fresh room-temperature \(R_{int}\approx20\,\Omega\), sag \(=15\text{ mA}\times20\,\Omega=0.300\) V, terminal \(2.70\) V – safe. At a catalog-typical cold-chain \(R_{int}\approx60\,\Omega\) (roughly 3x higher in a refrigerated 36-hour trip like this chapter’s own tote example), sag \(=15\text{ mA}\times60\,\Omega=0.900\) V, terminal \(2.10\) V – close enough to a typical 2.0 V logic cutoff that a fresh-cell bench test at room temperature would not catch the field failure.
• Tie to the chapter’s own lifecycle arithmetic: the same 250 reusable tags over a 24-month interval that the chapter budgets at \(250/24=10.4\) replacements per month is exactly the population size where a systematic cold-sag failure – invisible on the bench – would show up as scattered field read failures, not as a single bad batch.

4.3 Learning Objectives

By the end of this chapter, you will be able to:

• Distinguish passive, battery-assisted passive, and active RFID tags by power source and communication behavior.
• Explain why tag form factor, attachment, and surrounding material can matter as much as the tag family.
• Select a tag type from workflow evidence instead of generic performance claims.
• Review tag memory and sensor choices without overloading the tag with application state.
• Build a tag lifecycle record that covers encoding, commissioning, monitoring, replacement, and decommissioning.

4.4 Quick Check: RFID Tag Fit

4.5 Tag Types By Power And Behavior

RFID tags are easier to choose when you separate three questions:

• How does the tag get power?
• How does it communicate?
• When does the workflow need evidence?

Figure 4.1: RFID Tag Types Compared

4.5.1 Passive Tags

Passive tags have no normal operating battery. The reader field energizes the tag for a read, and the tag responds through the relevant LF, HF, NFC, or UHF behavior. Passive tags fit workflows where the read zone can be engineered and the object only needs to be identified when it passes that zone.

Use passive tags when:

• The object passes a known tap, shelf, gate, doorway, cabinet, conveyor, or handheld audit zone.
• Battery maintenance would be unacceptable.
• The business event is checkpoint based, such as received, returned, presented, counted, or verified.
• The team can test real materials, attachment methods, tag orientation, and reader settings.

Watch for:

• Metal, liquids, body proximity, stacking, folding, and packaging changes.
• Tags that work before attachment but fail after being mounted.
• Business requests that actually require area presence rather than checkpoint evidence.

4.5.2 Battery-Assisted Passive Tags

Battery-assisted passive tags, often called BAP or semi-passive tags, use onboard power for electronics such as sensing, logging, or stronger internal operation. Their communication still depends on reader interaction and the specific product family. The battery does not automatically turn the tag into an active beacon.

Use battery-assisted passive tags when:

• The object needs local sensing or logging and can be read at planned points.
• The tag must preserve sensor state between reads.
• Operations can manage battery age, storage conditions, and replacement rules.

Watch for:

• Confusing “battery in the tag” with autonomous area tracking.
• Storing too much changing application state on the tag.
• Forgetting what happens when the battery is weak, expired, or unavailable.

4.5.3 Active Tags

Active tags use onboard power for radio transmission or beacon behavior. They fit workflows that need area presence, periodic status, or location evidence between checkpoints. They also add receiver coverage, battery lifecycle, configuration, privacy, and decommissioning work.

Use active tags when:

• The asset must be discoverable without passing a fixed checkpoint.
• Area presence or movement history matters to the process.
• The organization can support battery replacement, receiver maintenance, and location evidence review.

Watch for:

• Using active tags when a well-designed checkpoint would be enough.
• Treating beacon sightings as exact location proof without validation.
• Leaving active identifiers running after the asset is retired or leaves the controlled environment.

4.6 Workflow Evidence Drives Tag Family

Every RFID tag decision comes down to two linked questions: where does the tag get its energy, and how does it send data back? Those two answers define the three families: passive, battery-assisted passive (BAP), and active. Range, size, cost, battery life, and support work follow from that power-and-transmit choice.

A passive tag harvests all its energy from the reader’s field and answers by backscatter, reflecting the reader’s carrier. An active tag carries a battery and its own transmitter, so it can beacon without waiting for a reader field. BAP sits between them: it has a battery for sensing, memory, or stronger internal operation, but still replies by backscatter. Getting this framing right stops the common mistake of assuming “has a battery” means “long range.”

Turn that framing into a workflow test before looking at a catalog. If 120 tagged cases move through a dock portal and the business event is “received at this doorway,” passive UHF can be a sensible first candidate because the cases pass a controlled reader zone. The pilot record might say: 120 expected cases, 118 accepted reads, 2 manual exceptions, and 0 neighboring cases accepted. That is a tag-and-zone acceptance record, not just a tag selection.

If the same organization wants to know whether a refrigerated tote exceeded a threshold during a 36-hour trip, the tag needs onboard sensing or logging between handoff reads. A BAP sensor tag can fit because its battery powers the sensing side while the reader still collects data at planned checkpoints. If a yard trailer must report presence without passing any gate, active tags or another location system are the right family to evaluate because the asset has to announce itself into an area.

A useful selection sentence is specific: “Use passive UHF labels for carton receiving at dock 3 after the portal pilot proves reads and exceptions; use BAP sensor tags for cold-chain totes when the handoff reader collects identity plus excursion status; evaluate active tags only for assets that must be found away from checkpoints.” One sentence separates three families, three evidence needs, and three support models.

4.7 Selection Path

Start with the business event, not with a tag catalog.

Figure 4.2: RFID tag selection path from business event through object environment, read pattern, tag family, form factor, pilot evidence, and lifecycle record

Use this sequence:

1. State the event the tag must support: identify, count, receive, release, locate, monitor, or audit.
2. Document the object and environment: material, shape, mounting, liquids, metal, people, cleaning, heat, motion, and privacy exposure.
3. Choose the read pattern: deliberate tap, shelf read, doorway pass, handheld audit, cabinet read, conveyor read, or area presence.
4. Choose the tag family: passive, battery-assisted passive, active RFID, or another technology if RFID is not the right fit.
5. Choose the form factor and memory behavior.
6. Pilot representative items and record settings, misses, duplicates, exceptions, and retest triggers.

This order prevents the common mistake of selecting a tag type from a generic promise and then discovering that the real object, reader layout, or support process does not match.

4.8 Family Comparison And Support Burden

The family comparison should include radio behavior and operational burden.

Property	Passive	BAP or semi-passive	Active
Power source	Reader RF field only	Battery powers local electronics	Battery powers electronics and transmitter
How it replies	Backscatter	Backscatter	Own transmitter or beacon
Typical UHF behavior	Controlled read zones and item tagging at scale	Better sensitivity or sensing at planned reads	Area presence, RTLS, vehicles, and high-value assets
Service life	No tag battery service	Battery-limited	Battery-limited
Cost and size	Lowest and smallest	Middle	Highest and largest

Passive range is short because the link is limited at both ends: the reader must deliver enough power to turn the tag on, and then recover a very weak reflected signal. A BAP tag removes much of the forward-link limit by powering its own chip, so it can wake and answer at lower field strength without becoming a transmitter.

Practitioners should add lifecycle arithmetic to the table. Passive labels can be practical for high-volume disposable packaging because there is no battery service queue. Battery-powered tags need an owner. If a pilot approves 250 reusable sensor tags with a 24-month service interval, operations should plan for about 250 / 24 = 10.4 tags per month to be inspected, rotated, or replaced, plus spares for damage and loss. If no one owns that queue, the tag family is not approved even when the radio pilot looks good.

Form factor needs the same discipline. A label that reads well on dry cardboard may fail on a foil-lined pouch or a metal tool. The review should include a small matrix: object material, tag package, mounting method, read pattern, accepted reads, missed reads, duplicate reads, and failure owner. For example, a tool-room pilot might test 30 tools with on-metal hard tags, require 30 / 30 reads inside the cabinet zone, and require 0 reads when the tool is on the staging cart outside the zone. That evidence is stronger than a generic “on-metal tag selected” line.

Memory choices also belong here. A tag with user memory is not automatically better than a simple EPC label. If the workflow only needs a stable asset identifier, keep mutable state in the backend where corrections are auditable. Use tag-resident data when the object must carry status through disconnected handoffs, and write the rewrite, privacy, and conflict rules before deployment. The practical result is a tag record that names family, package, encoding, memory use, reader settings, exception path, lifecycle owner, and retest trigger.

4.9 Form Factor And Attachment

Tag family is only part of the choice. The same tag chip can behave very differently in different packages and mounting positions.

Figure 4.3: RFID tag form-factor review connecting object material, attachment method, tag package, and pilot evidence

Review the physical fit:

• Label or inlay: Useful for flat packaging when handling, bending, and material effects are acceptable.
• Hard tag: Useful when the tag needs mechanical protection, screws, ties, adhesive, or reusable mounting.
• On-metal tag: Designed for objects where ordinary tags are detuned by metal.
• Embedded tag: Built into a product, tool, badge, garment, or container during manufacturing or preparation.
• Harsh-process tag: Selected for cleaning, heat, moisture, chemicals, impact, or repeated handling.
• Implant-style tag: Used only in controlled domains where close read behavior, safety, and identity process are well defined.

Good pilots include bad cases. Test the worst likely attachment, orientation, stacking, handling, and environmental conditions, not only the neat demonstration sample.

4.10 Memory, Identity, And Sensors

Tag memory should support identification and the workflow, not replace the business system.

Design rules:

• Keep the primary identifier stable and compatible with the readers and partners that must read it.
• Use TID or chip identity as supporting evidence when clone resistance or chip verification matters.
• Use user memory only when data must travel with the object and the privacy and rewrite rules are acceptable.
• Keep mutable process state in auditable backend systems unless there is a strong reason to store it on the tag.
• Treat sensors as evidence sources that need calibration, timestamping, ownership, and exception handling.

Old tag class shorthand appears in some legacy material, but design reviews should name the actual standard, tag product behavior, memory behavior, and support plan being used. For UHF passive deployments, EPC Gen2 / ISO 18000-63 language is usually more useful than old class labels.

4.11 Lifecycle Evidence

Tag selection is incomplete until the lifecycle is owned.

Figure 4.4: RFID tag lifecycle evidence loop from encoding through decommissioning

Lifecycle records should cover:

• Encoding: Who issues identifiers, what format is used, and how duplicates are prevented.
• Attachment: How the tag is mounted, protected, and verified on the real object.
• Commissioning: Which reader settings, antennas, firmware, and test evidence were accepted.
• Monitoring: How missed reads, duplicate reads, weak batteries, and unknown identifiers are detected.
• Replacement: How failed, damaged, expired, or transferred tags are handled.
• Decommissioning: How identifiers are disabled, retired, removed, or privacy-protected when the asset leaves the process.

For battery-powered tags, the lifecycle record must also include storage time, activation rules, expected service window, replacement owner, and disposal path.

4.12 Example: Cold-Chain Case Tag

A reusable cold-chain case needs identity at receiving doors and a temperature-excursion flag from transport. The best initial candidate is not automatically an active tag. If the case is only read at planned handoff points, a battery-assisted passive sensor tag may fit better: the onboard power supports sensing and logging, while the doorway reader collects the identity and status during the handoff.

Review evidence should include:

• Representative case material, contents, condensation, and tag mounting.
• Whether the handoff reader can reliably collect both identity and sensor status.
• What the tag records when it is not in a reader field.
• Battery age and activation process.
• What happens when temperature evidence is missing, late, or inconsistent.
• Whether privacy or custody rules limit who can read the tag.

If the case must be located continuously across a facility, or if no planned read points exist, the design may need active RFID, UWB, BLE beacons, or another location system. The tag choice follows the evidence requirement.

4.13 Backscatter, Transmitters, And Battery Evidence

BAP and active tags both have batteries, so people often treat them as the same class with different range. They are not. The difference is physical and regulatory. A backscatter tag, whether passive or BAP, only reflects the reader’s carrier. It does not generate its own radio emission, so it works inside the reader’s field and its range is bounded by how weak a reflection the reader can detect. An active tag runs a transmitter, so it must comply with transmit rules, drains its battery faster, and can reach across a room or yard because it is not relying on a faint reflection.

That is why a cold-chain sensor tag that must last a shipment is usually BAP: battery for the temperature sensor and memory, backscatter for lower-cost planned reads. An asset-tracking beacon that must be found anywhere in a warehouse is active because the asset has to announce itself without being in a reader field.

The acceptance evidence changes with the radio behavior. A passive or BAP tag needs a reader field at the moment of communication, so the test asks whether the intended reader zone can energize, query, and decode the tag population. An active tag needs receiver coverage and a beacon policy, so the test asks whether receivers hear enough beacons, whether the area estimate is good enough, and whether battery and privacy controls are owned. A beacon every 5 seconds produces 60 / 5 = 12 transmissions per minute. A beacon every 60 seconds produces one transmission per minute. The right interval is an operations decision, not a tag-family slogan.

For BAP sensing, the arithmetic is different. If a cold-chain tag logs every 10 minutes for a 48-hour trip, it creates 48 * 60 / 10 = 288 samples before the receiving reader collects the record. The pilot should prove that the tag stores the needed samples, the handoff read retrieves identity plus excursion status, and missing sensor evidence enters an exception queue. A passive label cannot create those between-read samples. An active tag could report periodically, but then the design must justify receiver coverage, transmit settings, battery service, and identifier exposure.

4.14 Common Mistakes

• Choosing from a generic read-distance promise: Real performance depends on the object, material, attachment, antenna layout, reader settings, and workflow.
• Confusing battery-assisted with active: A battery-assisted passive tag can log or power electronics, but it does not necessarily beacon by itself.
• Ignoring form factor: A tag selected in a spreadsheet can fail after bending, washing, mounting, stacking, or exposure.
• Overusing user memory: Tag-resident data can create privacy, synchronization, and rewrite problems.
• Forgetting decommissioning: Tags and identifiers need a retirement process, especially when assets leave controlled custody.
• Skipping exception design: Unknown tags, duplicate identifiers, failed batteries, and missed reads need an owner.

4.15 Review Checklist

Before approving a tag type, confirm that the team can show:

• The business event and read pattern.
• The object, material, attachment method, and environmental stress.
• The selected tag family and form factor.
• Identifier, memory, sensor, and privacy decisions.
• Pilot evidence with representative good and bad cases.
• Reader settings and middleware assumptions connected to the tag choice.
• Lifecycle ownership for encoding, commissioning, monitoring, replacement, and retirement.

4.16 Knowledge Check

4.17 Quick Check: BAP Versus Active

4.18 Match Tag Types To Roles

4.19 Order The Tag Selection Review

4.20 Summary

RFID tag choice is not a simple passive-versus-active preference. Passive tags fit engineered read zones. Battery-assisted passive tags add onboard power for sensing or logging while still depending on planned reads. Active tags fit area reporting and autonomous beacon behavior. Every choice needs evidence from the real object, attachment method, environment, reader layout, memory behavior, privacy boundary, and lifecycle plan.

4.21 Key Takeaway

RFID tag type selection should match power source, memory, form factor, environment, read range, lifecycle, cost, and standards requirements.

4.22 Concept Relationships

• Tag family affects reader choice, antenna layout, battery ownership, privacy exposure, and support work.
• Form factor connects the tag chip to the real object and environment.
• Memory behavior connects identity design to backend records and partner interoperability.
• Sensor behavior adds calibration, timestamp, exception, and battery responsibilities.
• Lifecycle evidence keeps tag performance reviewable after deployment conditions change.

4.23 References

This chapter was checked against official RFID and NFC standards context from GS1 EPC/RFID materials, the ISO/IEC 18000-63 standards page, and NFC Forum specifications. Always verify procurement language against the exact tag product, regional rules, reader firmware, and operational environment.

4.24 What’s Next

• RFID Frequency Bands: connect LF, HF, NFC, UHF, and active behavior to read-zone choices.
• RFID System Components: review readers, antennas, middleware, memory, and business-event handoff.
• RFID Design and Deployment: turn tag choices into a pilot and rollout plan.
• RFID Troubleshooting: diagnose missed reads, duplicate reads, material problems, and lifecycle failures.