Every bag, tracked from check-in to carousel.
A major international airline was losing time and goodwill to mishandled and delayed baggage, with limited visibility across the transfer journey.
The programme and figures on this page come from an earlier work by our advisers. The client name is withheld under NDA. Figures are as reported at the time. Named references are available under NDA when you engage.
Results in this engagement
End-to-end baggage read visibility.
Fewer mishandled bags.
Loading and unloading turn times.
Earlier work by our advisers. Client name withheld under NDA. Client name withheld under NDA; figures as reported at the time. Named references available under NDA. We model your own numbers when you engage.
The challenge
Mishandled and delayed bags drive compensation costs and erode passenger trust, and conventional barcode scanning leaves blind spots across transfers.
Our approach
- Passive RFID tagging of bags with read points across check-in, sortation, loading and arrivals.
- End-to-end read reconciliation aligned to IATA Resolution 753.
- Exception alerting for bags that miss a scan point.
- Passenger-facing visibility into bag status.
- Integration with baggage handling and departure-control systems.
Technology & integration
Stack deployed: Passive UHF (RAIN) RFID tags and fixed read portals across the baggage journey.
Integration: Baggage handling system (BHS), departure control, and passenger app / notification services.
Outcome: “Improved passenger trust while reducing baggage-handling inefficiencies.”
Related: Logistics RTLS · Passive RFID vs RTLS · Compare technologies · Aviation & airports
Baseline, method, period and what we excluded.
This page describes an engagement our advisers led in earlier roles. The client name is withheld under NDA. Figures are as reported at the time, with published industry sources where noted.
- Baseline: Barcode hand-offs; mishandled bag rate known only from claims.
- Method: IATA-aligned RAIN bag tags; read points check-in→sort→load→arrival; mishandle and read-rate by node.
- Period: Selected flight clusters / piers before network expansion.
- Excluded: Lab portal rates without pier metal and bag density reality.
Programme context
Baggage RFID follows IATA-style bag tag programmes with pier and carousel readers. Metal and bag density dominate RF design.
Airline/handler process ownership beats hardware brand.
Outcomes in this engagement and how they were earned
Outcomes: lower mishandling, better transfer performance, cleaner passenger messaging inputs.
Lessons from this engagement
Lessons: pier metal reality; handheld fallback; multi-handler governance.
Deeper problem framing
Mishandling clusters at transfers and dense piers. Handler multi-party governance is political.
Approach
IATA-aligned tags; pier RF reality tests; handheld fallback; multi-handler SOPs.
Outcomes and measurement
Mishandling rate, transfer success, exception ageing.
Governance, risk and what we refuse to claim
Figures from this engagement only. Your payback depends on adoption, integration quality and exception labour, not tag unit cost. Named references under NDA on engagement.
We challenge any supplier who asks you to accept demo-day averages as production truth.
Implementation sequence and change management
Pier metal trials; handler governance MoU; handheld fallback; IATA encoding quality; transfer KPI alignment.
KPIs: mishandling, transfer success, exception ageing.
Buyer checklist, supplier challenges and engagement shape
For baggage RFID, run pier metal trials and multi-handler governance before airport-wide claims.
Buyer checklist before you sign: (1) written system of record for events; (2) acceptance tests with 95th-percentile performance under real interference; (3) integration owner named in IT/OT; (4) privacy or labour consultation path if people are tagged; (5) cybersecurity zoning sketch; (6) five-year TCO including batteries, spares, recalibration and SLA escalations; (7) exit/export terms so you are not hostage to a cloud tenant; (8) a pilot that can fail without political punishment.
Supplier claims to challenge in this pattern: brochure accuracy without production load; 'compliance included' without artefacts; ROI that assumes perfect adoption in 30 days; references that cannot be called under NDA; install partners who have never worked your vertical's overlays; shared support accounts; and any design that dumps locating onto a flat plant or clinical VLAN.
How TRACIO typically engages: stage-1 architecture and measurement design; independent shortlist and RFP language; pilot acceptance criteria; then optional implementation oversight or programme rescue if a prior pilot stalled. We don't sell hardware, so our advice stays independent. Pages like this one exist so you can prepare the workshop. Your numbers replace every planning band when we model payback.
Risk register themes that recur: mute fatigue on alerts; shadow spreadsheets reappearing beside the platform; battery logistics understaffed; master data too weak to support identity; works-council or IG review starting too late; and success declared on demo day before night-shift reality.
Document baseline windows explicitly: what you measured, for how long, which shifts, and what you excluded. Investment committees and auditors both punish fuzzy before/after stories. If your baseline is weak, spend two to four weeks fixing measurement before ordering anchors or portals. That discipline is cheaper than a stranded deployment and is the difference between a locating programme and a technology souvenir.
Training and communications plan: who explains purpose to operators, how often refreshers run, how contractors are inducted, and how successes are fed back without turning safety systems into league tables. Budget a champion network on each shift. Platforms do not adopt themselves. Where unions or works councils exist, share the purpose statement and retention rules early. Surprise monitoring is how programmes die. Finally, schedule a formal gate review against the written criteria; celebrate a no-go if evidence is weak. Expanding failure is not delivery.
Last updated:
Hangar & MRO reality
Independent advisory means the radio is chosen last. After the job, the constraints and the system of record are clear.
Tool control that survives a turnaround
Map FOD risk, calibrated-tool custody and hangar flow before a radio is chosen.
Independent, aviation-grade
Shortlists respect on-metal tags, hangar RF and the MRO system already running, not a partner programme.
Integrate to the maintenance record
Events land in the system engineers already trust so accountability outlives the pilot.
Measurement
Baseline: mishandled-bag rate and dock-to-carousel scan gaps for the target lanes. Pilot: one pier or transfer bank with bag-tag RFID reconciled to the BHS / DCS events. Steady-state: tag read rate at choke points, time-to-locate a mishandled bag, and transfer success. Figures are as reported in this engagement. The airline stays unnamed under NDA.