Do we need to replace our existing systems to use Sandhed?

No. Sandhed connects to your existing equipment and systems. Your PLCs, RTLS anchors, sensors, and warehouse system stay in place. Sandhed reads from them through standard protocols. You do not need to change your existing infrastructure.

How does Sandhed handle data from different RTLS vendors?

Each RTLS vendor has a dedicated bridge service that translates vendor-specific messages into a unified position format. A coordinate mapping wizard aligns each vendor's coordinate system with your floor plan. You can run multiple RTLS vendors in the same facility and see all positions on one floor plan.

What happens when a data source goes offline?

Sandhed shows the last known state for any asset whose data source stops sending. MQTT-based bridges use persistent sessions so messages queue at the broker during outages. Failed messages are saved to a dead letter queue for retry. When the source comes back, data flows resume without manual intervention.

Can we connect systems that are not on the supported list?

Yes. The REST API accepts metric and position data from any source that can make an HTTP POST request. You define the asset mapping and data format, then push data on whatever schedule your system supports. This covers custom PLCs, edge devices, barcode scanners, and third-party platforms.

Universal Integration

Your Equipment Already Talks.Nobody Is Listening in One Place

Your PLCs, sensors, RTLS tags, and warehouse systems all generate data. Sandhed connects to all of them through a unified pipeline and brings everything onto one floor plan.

Request a Demo Take the Assessment

The Problem

Where Things Break Down

Your factory runs on a patchwork of systems. PLCs speak OPC UA. Position tags use MQTT. Environmental sensors have their own gateway. Your warehouse system has a REST API. Each vendor has its own dashboard, its own coordinate system, its own data format. Getting a single picture of your facility means opening five tabs, mentally overlaying the information, and hoping the timestamps line up. When you add a new sensor type or swap an RTLS vendor, the integration work starts from scratch.

Every data source has its own screen

Your PLC data is in SCADA. Your RTLS positions are in the vendor portal. Your environmental sensors have a web dashboard. Your warehouse data lives in the WMS. Nobody sees everything in one place because no system connects to all the others.

5+ separate systems to check during a single walkthrough

New integrations take months

When you add a new sensor vendor or swap your RTLS system, the integration project starts from scratch. Custom middleware, coordinate mapping, data format conversion, and testing can stretch to months before the data is usable.

3-6 months per new vendor integration

Data formats and coordinates do not match

Your UWB system reports positions in its own coordinate grid. Your RFID readers report zone IDs. Your PLCs push metric values in vendor-specific formats. Combining them requires custom transformation code for every pair of systems.

Manual coordinate mapping and data normalization for each source

Our Approach

What Sandhed Does Differently

Sandhed runs dedicated bridge services for each data source. MQTT-based systems like industrial telemetry, UWB positioning, BLE tracking, RFID readers, and environmental sensors connect through topic subscriptions. HTTP-based systems like heavy equipment telematics and warehouse management connect through polling at configurable intervals. Any custom source can push data through the REST API. Every bridge validates incoming data, maps vendor tag IDs to your assets, transforms coordinates to your floor plan, and pushes updates to the browser in real time. Failed messages go to a dead letter queue for retry instead of getting dropped. The result is one floor plan with every data source visible in one view.

MQTT and HTTP Bridge Services

Each data source connects through a dedicated bridge that handles the vendor protocol. MQTT bridges subscribe to vendor topics for real-time data. HTTP bridges poll external APIs at configurable intervals. Every bridge validates data with schemas and handles failures with retry queues.

Automatic Coordinate Transformation

RTLS vendors report positions in their own coordinate systems. A visual calibration wizard lets you place control points on your floor plan, compute the affine transformation, and verify accuracy with a grid overlay. Positions from any vendor display correctly on your floor plan.

Unified Tag-to-Asset Mapping

Every vendor uses different identifiers: tag IDs, serial numbers, EPC codes. Sandhed maps all of them to your internal assets through a single mapping table. When you swap tags or change vendors, you update the mapping and the data flows to the right asset.

REST API for Custom Sources

Any system that can make an HTTP POST can push metric and position data directly into Sandhed. No MQTT broker required. This covers custom edge devices, barcode scanners, manual check-ins, and any PLC that supports HTTP calls.

Quick Assessment

How Exposed Is Your Facility?

Integration Readiness Assessment

Answer 5 questions to get a personalized score and recommendations.

How many separate vendor dashboards or systems does your team check daily?

How long does it take to integrate a new sensor or data source into your operations view?

Can you see equipment positions and sensor data on the same screen?

Industry Applications

Built for Your Industry

Universal Integration for Manufacturing

Connect your PLCs, CNC machines, RTLS tags, and quality sensors into one view on your 3D floor plan. See machine telemetry and asset positions together without switching between vendor dashboards.

Manufacturing

Universal Integration for Warehousing

Connect RTLS tracking, environmental sensors, WMS data, and forklift telematics onto your 3D warehouse floor plan. See everything in one view.

Warehousing & Logistics

Universal Integration for Food & Beverage

Connect temperature sensors, production line PLCs, RTLS tracking, and environmental monitors to your 3D floor plan. See food safety data alongside production status.

Food & Beverage

Universal Integration for Pharmaceutical

Connect cleanroom sensors, production equipment, BMS data, and RTLS tracking to your 3D floor plan. Unified environmental and equipment monitoring for GMP compliance.

Pharmaceutical

Universal Integration for Automotive

Connect assembly line PLCs, quality gate sensors, RTLS tracking, and supplier logistics onto your 3D floor plan. See the full assembly operation in one view.

Automotive

Expected Outcomes

Results You Can Measure

Supported connection types

Industrial, RTLS, IoT, warehouse, and custom sources

Unified view

All data sources on one 3D floor plan

0 sec

Data latency

From sensor to screen via WebSocket

0 hrs

Setup time

From floor plan to live data integration

Based on platform capabilities and industry benchmarks. Results vary by facility.

FAQ

Common Questions

Sandhed connects to OPC UA, MQTT, Modbus TCP, and EtherNet/IP for industrial telemetry. RTLS systems connect via MQTT or REST depending on the vendor. Environmental IoT devices connect through MQTT. Warehouse and telematics systems connect through HTTP polling. Any other source can use the REST API to push data directly.

Related Resources

Answer

How to Get Real-Time Machine Data Without a 6-Month Integration Project

Traditional machine data integration projects take 4-6 months because they try to connect every system to every other system. The faster approach is read-only data collection through edge gateways that translate machine protocols into a common format without modifying the machine controllers. You can go from zero to first data point in days, not months.

Read answer

See All Your Data Sources on One Floor Plan

Bring your floor plan and a list of your data sources. We will show you how Sandhed connects to them and what the unified view looks like for your facility.