Measured by survey.
Volumes and distances need a survey crew, so they are checked rarely.
Introducing Resolve, our fast decision-making model. Meet Resolve →
How far.
How big.
How much is left.
Cameras and drones capture a site every day, but a picture can't tell you how much is in a pile, how close a person is to a moving machine, or whether a load fits under a beam.
Volumes and distances need a survey crew, so they are checked rarely.
Between surveys, people estimate from experience and truck counts.
Clearance and separation rules are written down, but rarely measured while the work happens.
The model does one hard job: working out how far away each part of the image is. Everything after that is geometry and rules, which is cheap, fast and checkable.
Drone surveys and the fixed cameras you already have.
Every pixel given a distance.
Ground markers and known sizes fix the scale.
Volumes, distances and clearances computed.
Against book stock, limits and design.
Survey SV-0714 · stockpile SP-3. Measured, not assumed. Every volume keeps the surface it came from.
Captured. 1,860 photos from the morning flight at 4 cm ground resolution.
Built. Depth and surface model; scale fixed by six ground markers.
Measured. 12,480 m³, from contours at 0.5 m intervals.
Compared. Book stock is 13,900 m³: a variance of −10.2%.
Illustrative example. Site, survey and figures are fictional.
Measurement is only useful if it happens often and can be checked.
Works from the drone surveys and fixed cameras you already run.
Site MeasurementEvery figure comes with the surface it was measured from and the calculation.
How Check worksProcessing can run on a site server, with results sent when there's a connection.
Deployment optionsThe AI goes to where the work is, from hosted to air-gapped.
Start with a hosted service when speed of adoption and managed operations are priorities. Agree data handling, access and service requirements as part of the engagement.
Discuss hostedDeploy dedicated instances in your AWS, Azure, Google or Oracle account. Align the architecture with your cloud standards, operational responsibilities and integration requirements.
Discuss public cloudRun it inside your own private cloud or VPC, with network access, storage and controls set around your boundary.
Discuss private cloudRun software, storage and local inference on your own servers. Plan capacity, integration, maintenance and support around the environment your team operates.
Discuss on-premisePlace intelligence near industrial sites and operational equipment, where latency and connectivity shape the design. Match the workload to the local compute available.
Discuss edgeOperate local workflows without a continuous internet connection. Define how data is transferred, how updates are applied, and what must remain available offline.
Discuss offlinePlan for an installation with no external network connection. Local models, dependencies, data transfer and maintenance all become part of the deployment design.
Discuss air-gappedEach one is tested on your own work before you rely on it.
It sees, hears and reads the work as it happens.
Explore Sense →From piles of paper to records you can use.
Explore Understand →Every line compared. Only the gaps reach you.
Explore Check →Follow the evidence across systems. Find out what happened, and why.
Explore Investigate →Know what comes next, and plan for it.
Explore Anticipate →The next step, taken. The reason, recorded.
Explore Operate →Start with the operational problem. We’ll work out the data, models and agents it needs, and where it should run.
Talk to us →