Worked examples
Worked examples
Illustrative workflows built on sample data. These are not client references.
Scope
one area submission, field to AGS 4.1 package
01 / Sample workflow
One area submission, field to AGS 4.1 package.
Illustrative workflows built on sample data. These are not client references.
02 / Data handling
One controlled environment for field, laboratory, and quality control.
Captured once, at source
Drilling records, strata descriptions, sampling and groundwater readings entered against location and depth interval and held in the central database.
One governed schema
Records resolve to project, area, location, sample and test.
Laboratory lifecycle
Entered → Calculated → Checked → Approved → Reported → Submitted.
Derived values
SPT N is taken from the full drive. Refusal is preserved verbatim, never summed and never treated as a measured N.
Review
Every result is approved by the responsible engineer before it reaches a deliverable. Independent four-eyes review can be enabled per project.
03 / AGS 4.1 generation
Mapped, conformance-checked, corrected, reviewed — then generated.
- 01
Mapping
Records map to AGS 4.1 groups and headings.
- 02
Conformance checks
Integrity, engineering logic, AGS reference checks and plausibility run on entry.
- 03
Correction
Findings are resolved on the source record.
- 04
Approved
Every result is approved by the responsible engineer before it reaches a deliverable. Independent four-eyes review can be enabled per project.
- 05
Generation
The package is generated from approved records after checks pass.
AGS 4.1 · BS 5930 · BS 1377 · BS EN ISO 14688 / 14689 · ASTM D1586
04 / AGS 4.1 generation walkthrough
Step through the line, from captured record to submitted package.
An illustrative workflow from sample records to an AGS 4.1 package.
Step 1 of 7 · Data management
14% of the line covered
Do this: Enter each measurement once, where it is made — never re-type it at the office.
Hover a step for a one-line summary · arrow keys move between steps
Capture
Drilling records, strata descriptions, sampling, SPT increments, groundwater readings, and laboratory determinations entered once against a location and depth interval.
What goes in
- Daily drilling record
- Strata description by interval
- Sample register
- SPT / in-situ increments
- Groundwater readings
AGS 4.1 groups touched
What is checked or computed
- Location IDs unique and resolvable to the project register
- Depth intervals continuous, non-overlapping, within hole depth
- Descriptions written from the BS 5930 / ISO 14688 dictionary, not free text
What leaves this step
Raw records held in the central database, attributable to the person and time of capture.
05 / AGS 4.1 FAQ
The questions engineers and clients ask before the first package.
Inputs, conformance checks and responsible engineer review.
Inputs & data management
What data has to be in place before an AGS 4.1 file can be generated?
A complete location register, strata descriptions by depth interval, the sample register, in-situ test increments, groundwater observations, and the laboratory determinations for each specimen. Every one of those records must resolve to a parent record — a project, an area, a location, a stratum, or a sample — before generation is possible.
Can legacy, Excel, or older AGS data be brought in?
Yes. Legacy records enter through the same import, mapping, and four-layer conformance checking as current works. Digitised is not the same as verified, so a historical record earns its place in the corpus exactly as a new one does.
Do engineers ever type computed values?
No. Raw measurements, engine-derived values, and approved results each enter through one controlled path. Classification, N-values, recovery indices, gradation parameters, and index properties are produced by the standards engine and held read-only.
Which AGS groups are shown in the sample workflow?
PROJ, TRAN, ABBR, UNIT, LOCA, GEOL, SAMP, ISPT, CORE and WSTG for field and in-situ data, plus the relevant laboratory groups — GRAG, LLPL, SHBG, CONG and RUCS among them — with the FILE group carrying the accompanying deliverables.
Validation
When does conformance checking run?
Continuously, against the live record set on every change — not at export time. That is why a package can be cut on the submission date without discovering findings on the submission date.
What do the four layers actually check?
L1 integrity covers IDs, depths, dates, units and precision. L2 engineering logic covers strata coherence, sample position within its interval, and groundwater readings against the drilling record. L3 covers AGS 4.1 reference checks for group presence, headings, parent–child references and dictionary terms. L4 plausibility raises values that are structurally valid but factually improbable for the ground being described.
An AGS file can pass a checker and still be wrong. How is that handled?
That is precisely what layer four exists for. A file can satisfy every dictionary and reference rule while describing ground that does not exist. Plausibility screening against regional expectations raises those records for engineering review before review.
How are findings corrected?
Every finding enters an issue log with an owner and a resolution record, and the correction is made on the source record — never on an exported file. Re-checking runs automatically on save, so the log sheet, the report table, and the AGS file move together.
Reviews & governance
Who reviews data before a deliverable?
Every result is approved by the responsible engineer before it reaches a deliverable. Independent four-eyes review can be enabled per project.
What is stored with a review?
The reviewing engineer, the timestamp, and the version of the governing standard in force. The status ladder — Entered → Calculated → Checked → Approved → Reported → Submitted — is forward-only, with audit logging in progress ahead of customer pilots.
How is the sample workflow reviewed?
Findings are shown per area before the package is issued.
Is the audit trail sufficient for a tender or a claim?
Audit log of imports, checks, reviews and exports · in progress.
Common customer questions
How long does a submission package take to produce?
Once records are approved, the AGS 4.1 file, borehole logs, factual report tables, Excel exports and the conformance report are generated together in one operation, per area. The elapsed time sits in validation and review, not in export.
Does G& replace our design and modelling tools?
No. Open formats mean G& coexists with your existing design and modelling tools. It governs the data and controls the submission; your data remains portable.
What happens when a client has its own submission format?
Client-specific submission rules are applied per package, on top of AGS 4.1 reference checks, so a package is assessed against the rules of the party actually receiving it.
Can we see the output before committing?
Yes — an anonymised AGS 4.1 file generated from approved records is downloadable in the walkthrough above, and fully redacted example deliverables are published on the outputs page.
AGS 4.1 · BS 5930 · BS 1377 · BS EN ISO 14688 / 14689 · ASTM D1586 · ASTM D4546
When findings are raised
On entry
Package leaves the building
After checks pass
Source of every exported value
Traceable