Omniterra Atlas · Application 04

Tie the payment quantity to the site state that supports it.

Calculate controlled surfaces, cut/fill, and quantities for progress valuation, payment review, and production reconciliation.

Starts with
Photos, video, drone capture, plans, control, and prior site states.
You receive
A dated metric workflow for one work package, comparison surface, control model, and measurement method.
Product output / application view
Atlas metric reconstruction for earthworks quantity review.
Inspect metric, visual, semantic, and temporal layers together, with direct links back to the capture and prior site states.
01 / Operational outcome
What improves

Review payment quantities against the reproducible site state that produced them.

The workflow is organized around one operating question: What quantity is supported by the accepted site state, and where do design, contractor, and observed surfaces differ?
Benefit 01

Connects calculated quantities to a reproducible spatial record

Output used

Capture, control, CRS, and reconstruction QA

Benefit 02

Speeds review of disputed or high-value work packages

Output used

Accepted existing-ground and current surfaces

Benefit 03

Preserves the exact world state behind each valuation

Output used

Project summary, technical methods, open rasters, geometry, and source records

02 / Operational context
Who uses it and when

Start with the operating team, trigger, and decision.

The technical scope starts from the operating moment, available observations, site geometry, time window, and the result the team needs to use.
Teams
Civil contractors, owners, quantity surveyors, project controls, lenders, and earthworks specialists.
Primary users
Commercial director, project controls lead, quantity surveyor, owner’s engineer, or lender monitor.
When it applies
A payment application, disputed quantity, month-end progress cut, production reconciliation, or design revision.
Decision to support
What quantity is supported by the accepted site state, and where do design, contractor, and observed surfaces differ?
03 / Evidence and deliverables
Configured workflow

A dated metric workflow for one work package, comparison surface, control model, and measurement method.

The workflow connects named inputs, spatial processing, technical review, and reusable outputs for a defined site state or review period.
Atlas stores the capture, spatial products, findings, and comparison state as one versioned site record.
Output set

What the team receives to support the decision.

01

Capture, control, CRS, and reconstruction QA

Generated from the registered capture and stored in the current Atlas site version.

02

Accepted existing-ground and current surfaces

Linked to source imagery, geometry, control, and review state.

03

Cut/fill, volume, area, and exception calculations

Structured for browser inspection, comparison, and repeat processing.

04

Project summary, technical methods, open rasters, geometry, and source records

Exported in open spatial formats for GIS, engineering, and operations systems.

04 / Related use cases

Bring the decision and the site evidence.
Define the record that can support it.

A dated metric workflow for one work package, comparison surface, control model, and measurement method.

Send the decision date, site or capture, review period, and the assets or work package under review. We will reply with the required inputs, processing scope, output formats, and next step.

Email Us

Performance cookies.