Local map versus network map
A single-site deployment of the spatially fused twin keeps the live 3D view inside one facility. Operators open the map, see RTLS positions of forklifts and people, overlay IoT readings, and pull in MES or WMS data that belongs only to that plant. Shift supervisors and logistics teams work from the same local picture. Replay, spaghetti diagrams and zone heat maps stay limited to one floor plan and one set of anchors.
When the same customer runs the architecture across several facilities the picture widens. One login can move between sites. The presentation describes the ability to start at a site-wide view and drill toward machine-level detail when PLC data is present. Central teams get a consistent spatial layer without forcing every plant onto identical RTLS hardware or the same 3D model quality.
Data points and licensing across the network
Pricing runs by data points ordered, with volume tiers and no charge per number of users. A single plant often sits in a lower tier. Each additional facility multiplies the points because every RTLS tag, sensor feed and integrated stream counts. Higher total volume moves the unit price down the tier table, so the cost structure of multi-site deployments improves with scale.
Licences remain valid for one year and renew automatically. Enterprise onboarding can cover the whole network while the Platform tier stays available for plants that prefer self-management. The same public REST API and .NET SDK work for every site; nothing in the licence model requires a separate product SKU per location.
Day-to-day routines that shift
Single-site teams own their own anchor calibration, their own 3D model updates and their own shift analytics. Multi-site introduces shared reference points. Route analysis or dwell-time patterns from one plant can be examined against another, but only when the spatial context travels with the data. Central logistics managers compare forklift utilisation or material movement across plants without travelling to each location.
The logistics management module itself does not change. Work orders still arrive by button, scan, touchscreen or direct MES connection. Drivers accept, routes are recorded, and the full chain—who needed what, who took it, which path, how long—stays available for later review. The difference is that the dataset now spans multiple sites, so engineers can examine material flows plant by plant from one place.
What the architecture keeps the same
Under the hood the twin still does the same job. It ingests RTLS positions (BLE, UWB, RFID or SLAM), IoT sensor streams and system data into one spatial layer. Deployment options remain public cloud, private cloud, fully on-premises or hybrid. On-premises continues to run Ubuntu 24.04 LTS plus Docker and still omits push notifications and automatic 3D processing.
Security measures stay TLS, role-based access, OT/IT segmentation and audit logging. Personal tracking remains opt-in. The platform still does not replace ERP, MES or WMS and still does not calculate OEE or run discrete-event simulation. It supplies visualisation, spatial context and decision support around data that other systems already produce.
Practical checks before expanding
Before moving from one plant to several, confirm that each new site can supply a usable 3D model within the 100 MB practical limit and that RTLS accuracy matches the local process needs—UWB for sub-metre work, BLE for the 1–3 metre range. Test whether central users can actually reach the drill-down views they need without waiting on local IT. Check that the extra data-point volume lands in a tier that keeps unit cost acceptable. Those three checks usually reveal whether the multi-site version of the same architecture will stay operationally useful or simply multiply complexity.