GroundOS / platform
Connect sensors, camera context and project information so teams can understand what is happening, act on it and keep the record.
From the field to the decision
RTLS brings tagged people, machinery and assets into a shared site map. UWB uses local anchors; RTK uses satellite positioning with corrections in suitable outdoor conditions. Assignments connect tag IDs to equipment, teams and roles.
Last-seen times and missing data remain visible. Site layout, obstructions and coverage determine the installation and positioning performance.
A frame helps reviewers understand access, equipment placement and conditions around an event. Link it to location history and the relevant project records.
Identities and roles come from tag assignments. They are not inferred through facial recognition. Periodic image analysis provides observations for review.
Local proximity warnings run separately from periodic video analysis and cloud reporting. Compatible devices, warning zones and the site configuration define their operation.
Warnings alert people. They do not brake, stop or control machinery. See when a device was last connected and when its records were last updated.
Relate observations to programmes, work fronts, quantities, materials and responsibilities. Mobile reporting adds the context that sensors cannot supply.
Recommendations retain source references, assumptions and revisions. The responsible person reviews consequential actions before approval.
Two sources, one view. The camera supplies the scene. RTLS supplies tag positions; equipment IDs, badges and roles come from assignments. Roles are not inferred from appearance or facial recognition.
Alignment matters. Overlay alignment requires camera calibration, a common coordinate system and timestamp alignment. RTLS positions must match the frame time; newer positions must not be presented as if captured in an older image.
Steel lies beside the road; the crane’s outriggers are deployed nearby. The image alone does not establish the remaining clear width.
Source: camera 04 · frameThe delivery plan reserves crane access from 13:00–16:00. That schedule comes from the document, not from the photograph.
Source: delivery plan v3 · 17 SepAsk the site manager to verify access width and the unloading area. The procurement lead can then review the delivery window.
Status: awaiting human reviewScale, clearance, current site conditions and supplier availability. A single frame cannot prove waiting time, equipment utilisation or movement.
Existing construction systems
Bring reports, planning files, material registers and asset records together around your work fronts. Keep the source and latest revision clear as information moves between teams.
Connect site information with your project and planning systems. We’ll define the right integration around your workflow, whether your team uses Procore, Autodesk Construction Cloud, Primavera or another system.
Share the records your team needs, in formats they can use. Build from useful reports to connected workflows that reduce repeated entry and keep changes visible.
A chosen workflow, a responsible team and access to the relevant records. Location use cases also need suitable tags, site coverage and agreed installation. Document-based reporting can start from existing project information.
Agree company, project and role permissions, retention and the purpose of each data source before deployment. Team activity provides context for work review; it is not individual productivity scoring.
Local warning operation is independent of cloud and video. Confirm device power, local coverage, buffering and synchronisation behaviour in the selected installation. Cloud-dependent views and reporting need a connection to update.
GroundOS