Readers, antennas, inlays
Choose passive UHF (RAIN) RFID when you need item-level visibility at scale, low per-unit cost (cents per inlay), and you can engineer the read environment. The differentiator across this category is rarely the silicon — it is antenna design, inlay tuning for the substrate, and the reader's ability to handle dense-reader mode and high-velocity item flows. TRACIO routinely specifies and benchmarks across these vendors in retail back-of-house, pharma serialisation, automotive build-genealogy, and aerospace tool-control programmes. We have no reseller margin on any of the brands listed.
Impinj · Zebra Technologies · Honeywell · Alien · NXP · Smartrac · Avery Dennison · HID Global · Mojix · Confidex · Beontag.
Precision positioning
Choose UWB when you need sub-30 cm accuracy, deterministic latency, and high tag density — typical use cases are aerospace tool tracking, automotive build cells, hospital workflow at room/bay granularity, and motorsport telemetry. The vendor differentiators sit in anchor coverage density, ranging schemes (TDoA vs TWR), tag battery life, and how cleanly the platform exposes raw location events to your own analytics layer. FiRa Consortium profiles (IEEE 802.15.4z) increasingly make multi-vendor interoperability practical, but each platform still has its own integration and calibration tax. TRACIO has commissioned UWB deployments from a few hundred to several thousand anchors and benchmarks vendors against published, witnessed test plans.
Ubisense · Sewio · Pozyx · Eliko · Inpixon / CXApp · NXP / Qorvo (Decawave) UWB chipsets · FiRa Consortium ecosystem.
AoA & beaconing
Choose BLE 5.x when 1–3 m room/zone accuracy is good enough and you need a high tag count at low cost per asset — the typical sweet spot is healthcare workflow, retail and warehouse asset finding, and large-estate occupancy analytics. Angle-of-Arrival (AoA) implementations lift accuracy meaningfully but require careful antenna-array placement and RF planning; pure RSSI deployments are cheaper but more sensitive to environment. Some platforms (Cisco Spaces, Aruba HPE) ride existing enterprise Wi-Fi infrastructure, which can collapse capex but constrains the analytics layer. TRACIO has delivered hospital-scale Quuppa networks, Kontakt.io retail rollouts, and Cisco-Spaces overlay programmes — we'll model the trade-off against UWB and RAIN for your specific use case.
Quuppa · Kontakt.io · Estimote · AiRISTA Flow · Cisco Spaces · Aruba HPE · Nordic Semiconductor · Silicon Labs · Texas Instruments.
Clinical workflow
Choose a healthcare-specialised RTLS when you need pre-built integrations to Epic, Cerner / Oracle Health, Meditech, or a regional EMR, plus clinical workflows (hand-hygiene, contact tracing, patient flow, infant security, asset par-level) already validated by reference customers. The differentiators here are clinical-evidence depth, HIPAA / GDPR posture, mixed-modality RF + ultrasound for room-level certainty, and the willingness of the vendor to integrate with rather than replace your existing biomed and EMR stack. Hybrid stacks — e.g. a CenTrak second-generation infrastructure alongside an AiRISTA or Kontakt.io analytics layer — are increasingly the right answer. TRACIO has advised on RTLS programmes across hospital groups in EMEA, NALA, and MENA, including standardisation across 20+ sites.
CenTrak · Stanley Healthcare (Aeroscout) · Sonitor · AiRISTA Flow · Kontakt.io Care · Midmark · Versus / Midmark RTLS.
Active & sensor tags
Choose active and sensor tags when read range, harsh environments, or integrated sensing (temperature, shock, tilt, GNSS, satellite backhaul) matter more than per-tag cost. Typical territories are heavy-asset yards, container fleets, oil & gas, mining, and lone-worker safety in environments where passive UHF and BLE both struggle. Differentiators include ATEX / IECEx zone ratings, expected battery life (3–10 years), built-in GNSS or satellite (Iridium, Astrocast, Swarm), and the maturity of the device-management platform. TRACIO has specified active-RTLS programmes across container terminals, deep-mining operations, and remote field assets — including hybrid LPWAN-plus-satellite architectures for sites with no terrestrial coverage.
Identec Solutions · Sigfox / UnaBiz · Mojix · WiseTrack · Iridium · Astrocast · Swarm Technologies.
Long-range, low-power
Choose LPWAN when you need kilometre-range, multi-year battery, and small payloads — typical fits are utility metering, agriculture, smart-building sub-metering, supply-chain sensors, and city-scale asset trackers. LoRaWAN gives you private-network control and a deep open ecosystem; NB-IoT and LTE-M give you carrier-managed coverage without owning gateways; Sigfox / UnaBiz sits at the simplest, lowest-data-rate end. Differentiators include network-server maturity (The Things Industries vs Senet vs Helium), eSIM and global-roaming options for cellular IoT (1NCE, EMnify, Soracom), and the platform's handling of geolocation by network triangulation versus on-device GNSS. TRACIO has designed private LoRaWAN networks for utilities and industrial sites and runs comparative TCO models across LoRaWAN, NB-IoT, and LTE-M as a standard part of vendor selection.
Semtech LoRa · The Things Industries · MachineQ (Comcast) · Senet · Helium · UnaBiz / Sigfox · Soracom · Hologram · EMnify · 1NCE.
Infrastructure-free positioning
Choose SLAM and vision-based positioning when fixed-anchor infrastructure is impractical, environments change frequently, or the asset to be tracked is itself a robot or vehicle that needs to localise as well as be located. The category splits roughly into onboard SLAM stacks for AMRs (Slamcore, Sevensense), survey-grade indoor mobile mapping for digital-twin creation (NavVis, Faro, Trimble), and edge-AI hardware that hosts vision models close to the camera (Hailo, NVIDIA Jetson, Google Coral, Edge Impulse). Differentiators are loop-closure robustness in feature-poor environments, sensor fusion with IMU and wheel odometry, and the integration story into ROS 2 or the host platform. TRACIO advises on hybrid stacks — e.g. fixed UWB or BLE anchors for ground-truth correction over SLAM — rather than betting an entire programme on a single positioning modality.
Slamcore · Sevensense (ABB) · Slambox-class platforms · NavVis · Faro · Trimble Indoor Mobile Mapping · Hailo · NVIDIA Jetson · Google Coral · Edge Impulse.
Robotics fleets
Choose AGV or AMR vendors based on payload class, navigation style (fixed-path AGV vs. SLAM-based AMR), and the operational shape of the work — tugging, lifting, goods-to-person picking, or autonomous case handling. The category split that matters operationally is whether you need a single vendor's stack at depth, or a mixed fleet orchestrated through VDA 5050 (now the de-facto standard for cross-vendor AGV/AMR interoperability) and a master control system on top. Differentiators include safety certification (ISO 3691-4), throughput at peak vs. published peak, charging strategy, and how well the WMS / WES / WCS integration is documented. TRACIO works with both robot vendors and end-clients to specify, procure, and run mixed-vendor fleets under a single orchestration layer — see our Fleet page for the full method.
MiR (Teradyne) · Otto Motors (Rockwell) · Locus Robotics · Geek+ · Seegrid · Fetch Robotics (Zebra) · 6 River Systems · Boston Dynamics. VDA 5050 orchestration.
Cloud & edge
Choose the IoT platform that matches your existing cloud commitment, your data-residency posture, and the team that has to run it — not the platform with the most slideware. Hyperscaler stacks (Azure IoT, AWS IoT, Google Cloud) win on developer ecosystem and integration with adjacent data services; industrial platforms (Siemens MindSphere / Insights Hub, PTC ThingWorx) win on shop-floor connectivity and OT semantics; open-source options (Eclipse ThingsBoard, Hono, Balena) win on portability and unit economics at large device counts. Differentiators that matter in real deployments are device-twin throughput, OTA update reliability across heterogenous fleets, and total cost at five-year scale rather than published list price. TRACIO has selected, architected, and recovered IoT platform deployments on all of the named stacks, and has no economic stake in the outcome.
Microsoft Azure IoT · AWS IoT Core + Greengrass · Google Cloud IoT · Siemens MindSphere · PTC ThingWorx · Software AG Cumulocity · Eclipse ThingsBoard / Hono · Balena.
Stream & lake
Choose the streaming and analytics stack based on event volume, query patterns, and how tightly the location data needs to land in the same warehouse as your finance, sales, and operational data. Streaming backbones (Kafka, Kinesis, Flink) handle the millions-of-events-per-day reality of a real RTLS programme; time-series stores (InfluxDB, TimescaleDB, QuestDB, ClickHouse) keep raw location and sensor history queryable; lakehouse formats (Delta Lake, Iceberg) plus Databricks or Snowflake on top give analysts and data scientists the same single source. Differentiators in practice are write-throughput at sustained load, retention-tier economics, and how cleanly the platform supports late-arriving events and corrections — the bread-and-butter problems of location data. TRACIO designs canonical event schemas and reference architectures that are deliberately portable across these stacks.
Kafka · Flink · Kinesis · InfluxDB · TimescaleDB · QuestDB · ClickHouse · Delta Lake · Iceberg · Databricks · Snowflake.
Simulation
Choose digital-twin tooling based on what the twin is actually for — visual situational awareness, discrete-event simulation for layout and throughput, real-time operational mirroring, or design-stage validation. Visual-realism platforms (NVIDIA Omniverse, Unity Industrial Collection, Unreal Engine) shine when stakeholder buy-in and 3D fidelity matter; discrete-event simulators (AnyLogic, FlexSim, Siemens Plant Simulation under Xcelerator) earn their fee when the question is throughput, queueing, or layout change ROI; graph-based twins (Azure Digital Twins) sit between live RTLS data and operational analytics. Most enterprise programmes need two of these, not one. TRACIO designs the data spine that feeds the twin from real-world RTLS, RFID, and IIoT sources, and we resist projects where the twin is a screensaver rather than a decision tool.
NVIDIA Omniverse · Siemens Xcelerator · Azure Digital Twins · AnyLogic · Unity Industrial Collection · Unreal Engine.
ERP · MES · EMR · WMS
The integration target almost always defines the architecture, not the RTLS or RFID layer itself — an aerospace tool-control programme lives or dies on its SAP, MES, and quality-system integration; a clinical-workflow programme lives or dies on Epic or Cerner integration. The category includes ERP (SAP S/4HANA + EWM, Oracle Fusion, Infor), service / asset management (ServiceNow IRM and HAM, IBM Maximo), clinical (Epic, Cerner / Oracle Health, Meditech, InterSystems), MES (Rockwell FactoryTalk, Siemens Opcenter, GE Proficy), and logistics-execution (Manhattan Active, Blue Yonder, Körber). Differentiators are the depth of pre-built connectors, ownership of the canonical product / patient / asset master, and the realism of the vendor's roadmap on event-driven integration. TRACIO acts as the independent integration architect, defining the contract between the location layer and the system of record so neither side dictates terms.
SAP S/4HANA + EWM · Oracle Fusion · ServiceNow IRM/HAM · Epic · Cerner Oracle Health · Meditech · Rockwell FactoryTalk · Siemens Opcenter · Manhattan · Blue Yonder · Körber.
Not exhaustive. New vendors enter the market continuously and we keep our knowledge current. Names belong to their respective trademark holders.