Use this hub to move from output level + architecture constraints to an RFQ that can be delivered.
Request an RFQ
Send project constraints + output level. Get a BOM-oriented quote path.
OEM/ODM & Customization
Private label / selected firmware or mechanical changes (scope-dependent).
Procurement Terms
MOQ, lead time, warranty/RMA and delivery boundaries for integrators.
Scope & Delivery Boundaries
What we source & deliver (and what we don’t)
GridRTLS provides the device & data layer for industrial UWB RTLS deployments, serving system integrators and engineering teams who require reliable, integration-ready hardware and clear technical boundaries.
What we provide
- Industrial UWB RTLS hardware: anchors/base stations, tags & wearables, wiring-free beacons, gateways and backhaul accessories.
- Architecture-aware device selection based on target output level (presence / 1D / 2D / multi-floor) and site constraints.
- BOM-oriented quotations aligned with deployment geometry, anchor visibility and communication topology.
- Integration-ready data outputs for customer platforms or third-party RTLS software.
- Documentation packages to support system integration, commissioning and acceptance.
What we do not provide
- No on-site installation, cabling or civil construction.
- No turnkey RTLS platform development or long-term platform operation.
- No end-customer project management or EPC-style delivery.
- No price-comparison or “lowest-cost” factory bidding.
Our role is to help integrators reduce rework, avoid mis-specification, and move from technical requirements to a deliverable RFQ.
Overview
Procurement context, architecture options, and how to proceed
This Procurement Hub is built for system integrators and engineering teams who need the “device & data layer” of an Industrial UWB RTLS deployment — anchors/beacons, tags/wearables, gateways/backhaul options, and integration-ready data outputs. It is not a price-compare factory page: the purpose is to help you specify the right architecture, reduce rework, and get an RFQ that can actually be delivered.
Why this matters: UWB positioning is geometry-driven. For true 2D positioning, the tag must be able to “see” multiple reference points (anchors/base stations) at the same time. In practical terms, the site layout and anchor visibility dominate performance more than a spec sheet headline. Our procurement flow is designed to start from output level and architecture, then map to hardware choices.
What you can source through GridRTLS
- UWB Anchors / Base Stations (wired PoE/DC options) for indoor positioning infrastructure.
- Wireless / Wiring-free UWB Beacons for sites where cable work is costly or restricted.
- Tags & Wearables for personnel, visitors, materials, and mobile assets (badge/card, wristband, helmet terminal, material tag, vehicle terminals).
- Backhaul choices: classic wired Ethernet, 4G/5G uplink scenarios, and gateway-based communication when public network access is not allowed.
- Indoor–outdoor fusion workflows combining UWB (indoors) with BeiDou/GNSS (outdoors) for continuous tracking in mixed areas.
Architectures we commonly quote (choose based on site constraints)
- Wired (PoE/Ethernet) architecture: anchors/base stations connect through network switches/cabling to a server/cloud platform.
- 4G/5G transmission architecture: base stations (or terminals) upload data via cellular where cabling is impractical.
- Wiring-free beacon + cellular: beacons are deployed by site conditions; terminals upload via 4G/5G; suitable for rapid deployment.
- Gateway communication architecture: for environments where data cannot access the public network; gateway relays data to local/cloud server.
How to use this hub: If you already have a floor plan and a target output level (presence / 1D corridor / 2D area / multi-floor), go straight to Request an RFQ. If you need OEM/ODM, customization, private label, or firmware/label adjustments, use OEM/ODM & Customization. For MOQ/lead time/warranty/compliance pack expectations, use Procurement Terms.
TL;DR
Quick procurement decision points
- Start from the output level you need (presence / 1D / 2D / multi-floor) — it directly drives anchor count and cost
- For 2D UWB positioning, the tag must have simultaneous visibility to multiple anchors; anchor geometry beats “marketing accuracy claims”.
- Use presence detection (single anchor) or 1D corridor tracking (two anchors) to reduce infrastructure cost when full 2D is not required.
- Choose your backhaul first: wired PoE/Ethernet, cellular (4G/5G), or gateway relay when public network access is restricted.
- Typical device blocks: anchors/base stations + tags/wearables + server/cloud platform (and optional gateways).
- Tag form factor matters as much as RF: wristband/badge/helmet/material/vehicle terminals change charging, mounting, and safety workflows.
- If your project includes indoor + outdoor areas, consider UWB + BeiDou/GNSS fusion devices that switch modes across boundaries.
- For harsh environments, shortlist industrial-grade enclosures and (when needed) intrinsically-safe / explosion-proof variants (model-dependent).
- For procurement, ask for a deliverable set: recommended BOM, deployment notes, and acceptance checklist — not just a quote.
- If you need OEM/ODM/private label/customization, align requirements before RFQ to avoid re-quoting later.
Process
A spec-first flow designed for real deployment
1 Define Output Level & Acceptance Criteria
Decide whether you need presence detection, 1D corridor positioning, or 2D area positioning (and whether multi-floor is required). This choice determines minimum anchor visibility requirements and infrastructure cost.
2 Select Architecture by Site Constraints
Choose wired PoE/Ethernet, cellular (4G/5G), wiring-free beacons + cellular, or gateway communication architecture when the public network is not allowed. Lock this first, then choose devices that match the architecture.
3 Plan Anchor/Beacon Layout (Geometry First)
For 2D areas, plan anchor placement so tags can “see” at least three anchors simultaneously. For corridors/aisles, 1D layouts can reduce anchor count. Provide floor plans and ceiling height to size the BOM.
4 Pick Tag/Wearable Types by Workflow
Choose personnel wearables (badge/wristband/helmet), material tags, and vehicle terminals based on charging strategy, mounting method, safety PPE rules, and whether you need SOS/alerts or hybrid indoor–outdoor tracking.
5 Confirm Environment & Compliance Constraints
Confirm IP rating needs, temperature range, hazardous-area requirements, and whether intrinsically safe / explosion-proof options are required (model-dependent).
6 RFQ → Sample/Pilot → Integration Validation
Submit RFQ with site constraints and output level. Validate with a pilot: measure coverage, NLOS behavior, update rate, and integration data flow before scaling to production.
7 Scale BOM + Deployment Checklist
Once pilot metrics match acceptance criteria, finalize the BOM (anchors/beacons/tags/gateways) and lock deployment + commissioning checklist for repeatable rollouts.
Checklists
Use these to avoid missing RFQ inputs and re-quoting
RFQ Inputs (Send These to Get an Accurate Quote)
- Floor plan / layout (CAD/PDF) + number of floors
- Ceiling height + mounting constraints (wall/ceiling/pole)
- Target output level: presence / 1D / 2D / multi-floor
- Estimated coverage area (m²) and key zones (hazard zones / restricted zones)
- Network constraint: wired Ethernet available? If not, cellular? Or no public network allowed?
- Tag types & quantities: personnel / visitor / material / vehicle
- Update rate requirement (e.g., slow people tracking vs fast vehicle safety)
- Expected accuracy in the real environment (LOS/NLOS, metal, machinery, tunnels)
- Alarm needs: SOS / geofence / overtime detention / speed/route deviation (if applicable)
- Integration target: do you need raw positions, events, or API/webhook output?
- Power availability at anchor points (PoE vs DC)
- Any hazardous-area compliance requirements (intrinsically safe / explosion-proof)
Architecture Decision Checklist (Wired vs 4G vs Wiring-free vs Gateway)
- Can you run Ethernet/PoE to anchor points economically? (If yes → wired architecture is usually simplest)
- If cabling is restricted, can you rely on 4G/5G coverage inside the site?
- If public network is not allowed, do you need a gateway relay to local/cloud server?
- Do you need rapid deployment with minimal construction? (Wiring-free beacon approach)
- Will tags cross indoor/outdoor boundaries? (Consider UWB + BeiDou/GNSS fusion)
- Server placement: on-prem server vs cloud server (IT/security requirement)
- Maintenance model: battery replacement plan for wiring-free beacons/tags vs fixed powered anchors
Infrastructure Sizing (Anchor/Beacon Count by Output Level)
- Presence detection: 1 anchor can detect whether a tag is inside a space (cost-saving mode)
- 1D positioning (corridor/tunnel/aisle): 2 anchors can be sufficient when width position is not needed
- 2D positioning (open area): plan for at least 3 anchors visible to the tag simultaneously
- For 2D: avoid anchor “shadow zones” caused by metal, machinery, and NLOS conditions
- Confirm whether you need 3D/multi-floor visualization and map alignment (coordinate system mapping)
- Decide whether base stations need time synchronization features for your deployment style (model-dependent)
Tag/Wearable Selection (Match Device to Workflow)
- Personnel tracking: wristband vs badge/card (charging, wearing policy, swap management)
- Helmet-required zones: helmet terminals avoid “no wristband / no lanyard” constraints
- Material/asset tracking: magnetic material tags simplify mounting on metal assets
- Vehicles/forklifts: vehicle terminals + (optional) collision avoidance/alerts where required
- If you need indoor–outdoor continuity: fusion terminals that switch between UWB and BeiDou/GNSS
- Determine battery strategy: centralized charging vs long-life battery devices (maintenance plan)
- Decide SOS / buzzer / vibration / motion detection needs per user role
FAQ
Answers procurement teams ask before RFQ
Are you a supplier, manufacturer, or vendor?
We operate as a procurement and integration-focused supplier for Industrial UWB RTLS device & data layers. We help SI/engineering teams choose the right architecture (wired / cellular / gateway) and source matching hardware blocks (anchors, tags, beacons, gateways) with integration-ready deliverables.
What is the minimum anchor requirement for UWB 2D positioning?
For true 2D positioning, the tag needs simultaneous visibility to at least three anchors/base stations. Anchor geometry and line-of-sight conditions are critical and should be planned from the floor plan stage.
Can I reduce cost if I don’t need full 2D accuracy?
Yes. Output-level design can reduce infrastructure: presence detection can be achieved with a single anchor for “in/out of zone,” and 1D corridor positioning can work with two anchors when width position is not required.
What architectures do you support for backhaul and data transmission?
Common architectures include wired PoE/Ethernet to a server/cloud platform, cellular (4G/5G) transmission where cabling is not feasible, wiring-free beacon + cellular solutions for rapid deployment, and gateway relay architectures when public network access is restricted.
My site can’t access the public network. Can I still run RTLS?
Yes. A gateway communication architecture can relay data to a local server/cloud server while keeping devices off the public network. This is commonly used when IT/security policies restrict direct cellular/public network access.
Do you support indoor–outdoor continuous tracking?
In mixed indoor/outdoor workflows, fusion approaches can use UWB indoors and switch to BeiDou/GNSS outdoors, with data transmitted via cellular or gateway depending on constraints.
What device blocks are included in a typical RTLS system BOM?
A typical system includes a server/cloud platform, data transmission layer (switches/cabling or cellular/gateway), positioning anchors/base stations, and tags/wearables attached to people, materials, and vehicles.
What kinds of tags/wearables are available?
Common industrial tag types include wristbands, work cards/badges, helmet terminals, material/asset tags, and vehicle terminals. The correct choice depends on PPE rules, charging strategy, mounting method, and whether you need SOS/alerts or hybrid tracking.
Does UWB RTLS require a map or coordinate system?
Yes. In practical deployments, anchor locations are mapped into a coordinate system aligned to the site layout, then time-of-flight/ranging data is used to solve positions. This is why floor plans and mounting coordinates are RFQ-critical inputs.
Do you offer platform software features like maps, tracks, geofences, and SOS?
Positioning platform software typically supports real-time map display, historical track playback, electronic fences, and SOS/alarm workflows. We focus on device + data layer procurement and integration readiness; the business layer can be built by the SI or integrated via outputs/APIs.
Can you support OEM/ODM, customization, or private label?
For selected device types, OEM/ODM and customization (labeling, form factor adjustments, selected firmware behaviors) may be possible. Use the OEM/ODM page to align requirements before submitting RFQ to avoid re-quoting.
Where should I start if I’m not sure what to buy?
Start with output level + site constraints: (1) presence / 1D / 2D / multi-floor, (2) wired vs cellular vs gateway constraints, (3) tag types and quantities. Then submit an RFQ with a floor plan so the anchor/beacon layout can be designed around geometry and visibility.