# Geotechnical Data & AGS 4.1 Submission Control | G&

> G& carries every borehole, sample, and lab result from the rig to a certified AGS 4.1 submission — four-layer validation, full traceability, signed by your engineers.

## The load path

### 01 — Raw (Door 1 — capture)

Field and lab measurements, captured once at source.

The only stage where a human types a value. Everything downstream is computed or approved, never re-entered.

- **Entry** — Field logging, lab bench entry, instrument import, legacy AGS / Excel migration
- **Mutability** — Editable by the recording engineer until the record is calculated
- **Authority** — Recording engineer · Data coordinator

- Measurement bound to its location, depth interval, and sample ID on write
- Units, method, and instrument recorded alongside the value
- Capture timestamp and author attached — no anonymous rows
- Legacy imports enter through the same mapping, not a side channel

- **Data integrity** — IDs resolve, depths ordered, dates valid, units declared
- **AGS compliance** — Group and heading exist in the AGS 4.1 dictionary
- **Engineering logic** — Sample sits inside a logged stratum; groundwater reconciled against drilling

Exit: A raw record cannot leave this stage until integrity and dictionary checks pass.

### 02 — Engineered (Door 2 — standards engine)

Computed by the standards engine. Read-only, always.

No computed value is ever typed on an entry screen. The engine holds sole calculation authority, against a versioned standard.

- **Entry** — Standards engine, triggered by the raw records it depends on
- **Mutability** — Read-only. Correct the input, and the derived value recomputes
- **Authority** — Standards engine — ASTM · BS 1377 · BS EN ISO 14688 / 14689

- Classification, indices, and correlations derived from raw inputs only
- Governing standard and clause version stamped onto each derived value
- Full dependency graph retained — every value resolves to its inputs
- Recalculation on input change, with the previous result kept in history

- **Engineering logic** — Derived values coherent across strata, tests, and depth
- **Plausibility** — Structurally valid but factually wrong results flagged for review
- **AGS compliance** — Parent–child references intact after recalculation

Exit: A derived value carries no signature. It is evidence, not a deliverable.

### 03 — Certified (Door 3 — signing engineer)

Approved by a signing engineer. The only door to a deliverable.

Approval is a named human act. Nothing enters an AGS file, a report table, or a payment certificate without it.

- **Entry** — QA review, then explicit approval by a named signing engineer
- **Mutability** — Locked. A correction is a new forward transition, never an overwrite
- **Authority** — Signing engineer · QA reviewer · Project manager

- Record locked with user, timestamp, and standard version
- Released to AGS 4.1 export, borehole logs, report tables, and IPC quantities
- Extends the validated corpus — queryable by later investigations
- Any later change raises a new issue and a forward-only transition

- **Client submission rules** — Client-specific headings, naming, and formats checked
- **Submission readiness** — Go / no-go per area, with blockers, errors, and warnings resolved
- **Audit** — Approval, export, and every access logged for tender-grade review

Exit: Approved is the only state a deliverable can be built from.

## Modules

- **M01 Field logging** (Field) — Drilling, logging, sampling, and groundwater readings captured once at source — descriptions to BS 5930, offline-tolerant, synced into the central database.
- **M02 In-situ testing** (In-situ) — SPT, CPT, permeability, and pressuremeter records held against their location and depth interval, with method and standard version attached to every value.
- **M03 Laboratory** (Lab) — Request, schedule, test, calculate, check, approve, report, bill — the full lifecycle on one record, with results autofilled back into logs.
- **M04 Borehole logs & report tables** (Logs) — Publication-grade logs and factual report tables drawn directly from approved records, not re-plotted in a spreadsheet.
- **M05 Maps & data explorer** (GIS) — Locations, strata, and test coverage on regional coordinate systems, queryable by formation, test type, or depth interval.
- **M06 Submission control** (Submission) — Four-layer validation, client-specific rules, issue log, and a go / no-go readiness view per area before anything leaves the building.

## Interoperability

- AGS 4.1 in / out
- Excel round-trip
- CSV
- GIS exports
- Open data formats
- PDF deliverables

## Common questions

### Can we migrate legacy records without rebuilding templates?

Yes. Legacy AGS and Excel records import through the same mapping and four-layer validation as live works, so migrated data arrives verified rather than merely digitised.

### Does G& replace our design and modelling tools?

No. Open formats mean G& works alongside your existing design stack — it holds the governed record and controls the submission.

### Who can approve a value?

Only a named signing engineer. Derived values are computed by the standards engine and are read-only; approval is the single door to any deliverable.

### Where is the data hosted?

Regional and sovereign hosting options are available, with role-based access and every import, validation, and export audit-logged.