Pick a layer to read it, or jump to its section.
Client-side applications, the Logidot Cloud, the physical hardware and the WMS / ERP
Our Technology
Our Technology
To empower the digital transformation of your operations, you need to know the precise location and status of the relevant assets on the shop floor. In addition, you need to connect these in real-time and enhance them with computational power, so that they interact in the fastest and smartest way possible. Logidot helps you achieve this through three core technologies: RTLS, IOT platform and simulator.
RTLS
Technology powering our RTLS
Logidot combines a handful of technologies to reliably track assets with industry-leading accuracy.
UWB
Ultra-wideband (UWB) is a short-range wireless communication protocol - like Wi-Fi or Bluetooth - which uses radio waves of short pulses over a spectrum of frequencies ranging from 3.1 to 10.5 GHz. Its unique combination of signal characteristics - a fine time resolution and resistance to interference and reflections - makes it a secure, reliable and accurate choice for asset tracking.
Find out more.GPS
Using the latest GPS chips, we can reliably track assets outdoors with submeter accuracy and in some cases also indoors by combining signals from multiple satellites.
IMU
IMUs can measure forces, angular rates and orientation using a combination of accelerometers and gyroscopes. It allows for accurate location tracking over short trajectories in case of occlusions or GPS or UWB signal is lost.
QR and Barcodes
A barcode, consisting of bars and spaces, is a machine-readable representation of numerals and characters. Today, stripes as shown below on packages of products sold at supermarkets, convenience stores and other stores are ubiquitous.
RFID
Uses electromagnetic fields to automatically identify and track tags attached to objects. An RFID system consists of a tiny radio transponder, a radio receiver and transmitter. When triggered by an electromagnetic interrogation pulse from a nearby RFID reader device, the tag transmits digital data, usually an identifying inventory number, back to the reader.
Sensor Fusion
By combining the data from multiple physical sensors via fusion algorithms, an accurate and robust tracking performance can be achieved.
- 3D accuracy [R95] (cm)
- < 30
- Max range (m)
- 65
- Sensor fusion
- 6-axis IMU (accelerometer + gyroscope), GPS
- GNSS (optional)
- Multiband GNSS
UWB, GPS, IMU, RFID, QR and sensor fusion on one floor; TWR and TDoA
The floor itself
State-of-the art sensors for all use cases
-
Anchor
Fixed sensor-set that provide location to moving targets, include UWB sensor. Can use the embeeded battery for months of life-cycle or be connected to your power maze.
- Dimension (mm)
- < 100 x 60
- Integrated Sensors
- UWB
- Weight (g)
- 100 Anchor + 600 Default battery
-
Vehicle Tag
Interfaces with our gateway, integrates UWB, a 6-axis IMU (accelerometer and gyroscope) and GPS. Battery life of one week with the option to be attached directly to the vehicle power source.
- Dimension (mm)
- 130 x 100 x 35
- Indicators
- 1 Actuator + 1 Sensor by default, extendable
- Integrated Sensors
- UWB, 6-axis IMU (accelerometer + gyroscope), GPS
- Weight (g)
- 150 Device + 1200 Battery (optional)
-
Wearable Tag
Interfaces with our gateway, integrates UWB and a 3-axis accelerometer. Battery life of one day.
- Dimension (mm)
- 67 x 44 x 15
- Integrated Sensors
- UWB, 3-axis accelerometer
The layer the other two stand on: tags on the vehicles and the people, anchors on the racking, a gateway off the floor. What they measure leaves the building once and arrives in the cloud as position, identity and status.
- Tags
- Anchors
- Gateway
- 3D accuracy [R95] (cm)
- < 30
- Max range (m)
- 65
- Operating frequency
- 6.5 to 8.5 GHz
- Protection level
- IP67 (outdoors) and IP54 (indoors)
Data Sheet
01 General Considerations
- 3D accuracy [R95] (cm)
- < 30
- Antenna type
- 360 deg omnidirectional
- Data Interface
- Flexible communication for gateway via 3G/4G/5G, WiFi 2.4GHz (802.11g) and Ethernet and tags via 6.5-8.5 GHz RF and Bluetooth 5.1
- Sensor fusion
- 6-axis IMU (accelerometer + gyroscope), GPS
- GNSS (optional)
- Multiband GNSS
- Operating frequency
- 6.5 to 8.5 GHz
- Protection level
- IP67 (outdoors) and IP54 (indoors)
- Max range (m)
- 65
02 Gateway
- Energy consumption (W)
- 20
- Power Supply
- Flexible power interface PoE, 9-36V DC, 110-220V AC
- Weight (g)
- 2000
03 Availability & Security
- Installation
- Flexible mounting screws, magnets or straps
- Latency
- 5 min. to analytics
3s for live view - Safety
- Daily backups
- Security
- Standard enterprise grade encryption with end-to-end web security based on SSL
04 Support
- Web (browser)
- Chrome, Edge, Firefox, Safari, Opera
- Database
- Google Cloud Platform
- Integration
- Available REST APIs for integration with your own systems
WMS/ERP/MES plugins for the most common providers or integration on demand - Apps (mobile)
- IOS & Android
Anchor, vehicle tag, wearable tag, and the four data sheets
IOT Platform
Our real-time IOT platform gives location, ID, and status data for various assets and translates into measurable processes. The platform, therefore, makes it possible to monitor, optimize, and automate processes in production and logistics. The open and highly elastic architecture enables easy integration and a rapid ROI.
- Anchor Fixed on the racking
- Gateway The link off the floor
- Wearable Tag Worn by the people
- Vehicle Tag Fitted to the fleet
- Dashboard Read in the office
- 3rd Party Sensors What is already on site
Anchor
Anchors are the building’s reference points. Screwed, magneted or strapped to racking, columns and walls, each one ranges every tag in view over UWB — months on the internal battery, or wired into site power.
- UWB
- Up to 65 m range
- Battery or wired
Gateway
The gateway is the one box between the floor and the platform: it collects what the anchors hear and forwards it over whatever the site already has — Ethernet, Wi-Fi or a mobile connection.
- 3G/4G/5G, Wi-Fi, Ethernet
- PoE, DC or AC
- Encrypted end to end
Wearable Tag
A wearable tag puts the people on the floor on the same live map as the vehicles — UWB for position and a 3-axis accelerometer for what they are doing. A day on a charge, and nothing to operate.
- UWB
- 3-axis accelerometer
- A day per charge
Vehicle Tag
Forklifts, pallet trucks and tugs carry a vehicle tag. UWB indoors, a 6-axis IMU for motion and GPS when the work goes outside — a week on battery, or taken straight off the vehicle’s own power.
- UWB · IMU · GPS
- 3D to 10 cm
- A week, or vehicle power
Dashboard
Every position lands against your own floor plan, so the dashboard shows zones, dwell and routes rather than dots — live within seconds, analysed within minutes, and available through the API to the WMS, ERP or MES you already run.
- Live view in 3s
- Analytics in 5 min
- Open API
3rd Party Sensors
The architecture is open at the edge too. Sensors you already have — presence, environment, gates, scanners — stream in beside Logidot’s own, so one platform carries the whole picture.
- Existing hardware
- One stream
- Rapid ROI
Where the work is done
Cloud
Hosted for you, so there is nothing to install or keep running on site. Analytic services turn tracks into measures, the intelligence layer reads those measures against how the operation is meant to run, the reporting tools assemble what comes out, the dashboard support services serve the live view, and storage keeps the history — backed up daily and encrypted end to end.
- 1 Analytic services
- 2 Intelligence
- 3 Reporting tools
- 4 Dashboard services
- 5 Storage
- Database
- Google Cloud Platform
- Latency
- 5 min. to analytics
3s for live view - Security
- Standard enterprise grade encryption with end-to-end web security based on SSL
- Safety
- Daily backups
Logidot Cloud, taken apart
WMS (3rd party)
The system of record you already run
The warehouse management system stays where it is. Logidot exchanges data with it in both directions — plugins for the most common providers, or an integration built for yours — so real-time position can retire the manual, error-prone steps around it instead of adding another screen.
- WMS / ERP / MES
- Both directions
- Plugins or on demand
Simulator service
The operation, run forward
The same data drives a model of your floor you can run forward: layouts, resource allocation, picking strategies and stock placement tried against a shift before anything moves in the building.
- Layouts
- Picking strategies
- Resource allocation
Analytics layer
Positions become measures
Where tracks turn into the numbers an operation is run on: time by zone, travelled time against order fulfilment, spaghetti maps, utilisation and productivity. Analysed within five minutes of the movement itself.
- Zone analytics
- Spaghetti maps
- Analysed in 5 min
Intelligence layer
Measures become judgements
What the analytics measure is read against how the operation is meant to run, so that a busy hour can be told from an unusual one and a pattern worth acting on from noise. It is what turns the numbers below it into the judgements the automation layer acts on — the three together are one pipeline, from position to insight to action.
- Patterns
- Anomalies
- What matters now
Automation layer
Supervision, automated
Rules you set watch the live picture for you and flag the anomalies — a vehicle in a restricted zone, an asset that has not moved, a check that was skipped — while the reporting tool sends the regular numbers out without anyone assembling them.
- Custom rules
- Alerts
- Automated reporting
RTLS Platform
What everything above stands on
The real-time location layer. UWB ranging from the anchors, motion from the tags and GPS where the work goes outdoors, fused into one position per asset against your own floor plan — 3D to 10 cm, up to 16 Hz, on screen within three seconds. Vehicles, goods, maintenance and people all arrive here first.
- 3D to 10 cm
- Up to 16 Hz
- Live in 3s
REST API(s)
For the systems
Everything the platform knows is available over REST, so the systems that run the work can read it directly rather than through a person copying numbers between screens.
- REST
- Live and historical
- SSL end to end
Web dashboard
For the office
The live view and the reports in a browser: wherever you are, sign in and the floor is on screen as it is now, with the history behind it.
- Live view
- Reports
- Any browser
Mobile apps
For the floor
The same platform in a hand on the floor — checks before a vehicle is used, a log of who used what and when, and the picture where the work is happening rather than back at a desk.
- iOS & Android
- Access control
- Usage log
The RTLS platform, the four services on it, the WMS across the top and the three surfaces
Where the operation is read
Client-side applications
What your people actually open: the web dashboard with the live map and the charts behind it, the mobile apps on the floor, and the integrations that put the same picture inside the tools they already use.
REST API(s)
For the systems
Everything the platform knows is available over REST, so the systems that run the work can read it directly rather than through a person copying numbers between screens.
- REST
- Live and historical
- SSL end to end
Web dashboard
For the office
The live view and the reports in a browser: wherever you are, sign in and the floor is on screen as it is now, with the history behind it.
- Live view
- Reports
- Any browser
Mobile apps
For the floor
The same platform in a hand on the floor — checks before a vehicle is used, a log of who used what and when, and the picture where the work is happening rather than back at a desk.
- iOS & Android
- Access control
- Usage log
- Web (browser)
- Chrome, Edge, Firefox, Safari, Opera
- Apps (mobile)
- IOS & Android
Web dashboard, mobile apps and the REST API
Your data, coming the other way
WMS / ERP
Orders, stock and master data come the other way, from the systems of record into the platform, so a position on the map is a pallet with an order behind it rather than an anonymous dot.
- 1 Orders, stock and master data From the WMS / ERP into the platform
- 2 Position, identity and status Back to the WMS / ERP over the REST API
WMS (3rd party)
The system of record you already run
The warehouse management system stays where it is. Logidot exchanges data with it in both directions — plugins for the most common providers, or an integration built for yours — so real-time position can retire the manual, error-prone steps around it instead of adding another screen.
- WMS / ERP / MES
- Both directions
- Plugins or on demand
REST API(s)
For the systems
Everything the platform knows is available over REST, so the systems that run the work can read it directly rather than through a person copying numbers between screens.
- REST
- Live and historical
- SSL end to end
- Integration
- Available REST APIs for integration with your own systems
WMS/ERP/MES plugins for the most common providers or integration on demand
Customer data in, located goods out
Sandbox
Simulator
Model an operation before a single sensor is installed. The simulator drives your own floorplan with realistic vehicle and picker movement, and the platform treats it exactly like a live site — the same map, the same alerts, the same reports you would see on day one.
- 1 Validate a deployment on paper Lay out aisles, zones and traffic on the real floorplan and watch how assets move through it. Coverage gaps and congestion show up before anchors are mounted, not after.
- 2 Test rules before they alert anyone Zone events, speed limits, fencing and collision rules run against simulated traffic exactly as they run against live data — so thresholds are tuned before the first shift depends on them.
- 3 Train and demonstrate without hardware Because simulated runs are indistinguishable to the platform, the live map, analytics, reports and alerts all work. Teams can be trained, and the system reviewed, ahead of installation.
- What you see
- The live map, alerts and reports exactly as they run on a live site
- How long it takes
- Watch a full shift play out in minutes, or follow it in real time
- What we need from you
- Your floorplan, the zones that matter and the vehicles you run
- What you get back
- Where coverage falls short, where traffic backs up and how your rules behave — before anything is mounted
Sandbox
Run a warehouse in your browser
The real one runs on your floorplan, inside the platform. This one has the same work cycle and the same dials on a sample floor — 64 by 36 metres, 280 pick faces, four zones and a fleet you control.
The floor needs JavaScript to run. The controls below describe what it does.
- Forklift
- Pallet truck
- Picker
- Waiting line
- Carrying a load
Click a rack bay to order that line now. Click a vehicle to follow it.
- Throughput
- /h
- Open orders
- orders
- Cycle time
- min
- Fleet in use
- %
- Distance driven
- km
- Time giving way
- %
Fleet
- Forklift 2.4 m/s
- Pallet truck 1.8 m/s
- Picker 1.2 m/s
Demand and handling
| Vehicle | Doing | Orders | km | Battery |
|---|---|---|---|---|
| No vehicles on the floor. Add one and the orders start moving. | ||||
Just happened
What this one leaves out
One floor, one shift, nearest-vehicle dispatch and simplified physics — arithmetic light enough to run at sixty frames a second in a browser tab. The production simulator plans across your own floorplan, runs shifts and rosters, and replays months of your order history.
A simulated floor: 64 by 36 metres, four zones, a fleet you control
The platform, asked in plain language
AI agent
The same measures, asked for in words rather than built into a report: which aisles cost the most walking this week, why an alert fired at 04:12, what would change if the fast movers moved bay. The assistant reads what the platform already knows — live position, zone analytics, the rule events, the history — answers with the numbers it used, and hands anything it proposes to the simulator, so a change is tried against a shift before it is made on the floor. It runs beside the platform on servers we host, signed in with the same account as the dashboard.
- Ask in plain language
- The data you already have
- Proposes, you approve
- Reads
- Live position, zone analytics, rule events and history
- Hands over to
- The simulator, so a suggestion is run before it is done
- Runs
- Beside the platform, on our own servers
- Access
- The same sign-in as the dashboard
A question, the data it was answered from, and the change tried before it is made
How We Compare
| Technology | Accuracy | Reach | Location | Application | Duration Anchor | Duration Tag | Infrastructure Cost | Ease of Deployment/Use |
|---|---|---|---|---|---|---|---|---|
| Wi-Fi |
<20 m
|
<150 m
|
2D
|
Medium
|
Medium
|
Low
|
|
|
| Bluetooth (BLE) |
<6 m
|
<50 m
|
2D
|
Medium
|
Medium
|
High
|
|
|
| RFID/NFC |
<10 cm
|
<1cm
|
Spot
|
Low
|
Passive
|
Low
|
|
|
| Existing UWB |
<20 cm
|
<100 m
|
2D/3D
|
Low
|
High with TDoA
|
Low
|
|
|
| Logidot |
<20 cm
|
<100m
|
2D/3D
|
High
|
High with TDoA
|
High
|
|
|
Benefits
High-performance
up to 10cm accurate in 3D and low latency
Adjustable update rate
up to 16Hz
Long range
up to 50m intersensor distance
Robust
against reflections, noise, vibrations and shocks
Scalable
simply add more beacons
Self-calibrating
can be deployed in a matter of minutes