Modules
Each module writes into the same central geotechnical database under the same four-layer validation. Nothing runs on a private copy of your data.
M01 · Field
BS 5930 · AGS 4.1
Capture once, at source
Drilling records, strata descriptions, sampling, and groundwater readings entered on the rig against location and depth interval — offline-tolerant, synced into the central database on connection.
M02 · Field
ASTM D1586 · Eurocode 7
Every increment, bound to depth
SPT, CPT, permeability, and pressuremeter records held against their location and depth interval, with method, instrument, and standard version attached to every value.
M03 · Database
AGS 4.1 · BS EN ISO 14688 / 14689
One governed estate
Projects, areas, locations, strata, samples, in-situ tests, lab results, and groundwater observations in a strict parent–child schema, with referential integrity enforced at the database itself.
M04 · Database
AGS 4.1
Digitised is not verified
Legacy AGS and Excel records enter through the same mapping and four-layer validation as live works — a historical record earns its place in the corpus the way a new one does.
M05 · Laboratory
BS 1377 · ASTM
Request to result, one record
Request, schedule, test, calculate, check, approve, report — the full lifecycle on the sample record, with results autofilled back into logs and report tables.
M06 · Laboratory
Contract rate schedules
Billed from approved records
Interim payment statements built directly from approved records — quantities your client can trace to the borehole, the sample, and the test. No re-entry, no reconciliation.
M07 · Output
BS 5930 · BS 1377
Publication-grade, reviewed from the record
Borehole logs, factual report tables, and factual report drafts drawn directly from approved records — not re-plotted in a spreadsheet. A beta review workflow can comment on scientific consistency, data accuracy, missing evidence, and standards alignment before submission.
M08 · Output
BS 1377 · ASTM D4546
Ground truth, plotted
Failure envelopes, consolidation curves, gradations, SPT profiles, and groundwater hydrographs alongside project KPIs, productivity, and submission readiness per area.
M09 · Governance
AGS 4.1 · Client submission specs
Nothing leaves unvalidated
Four-layer validation, client-specific submission rules, an issue log with corrections, and a go / no-go readiness view per area before anything leaves the building.
M10 · Governance
ISO 9001-aligned workflows
Tender-grade accountability
Role-based access across project engineer, data coordinator, QA reviewer, project manager, and admin — with every import, validation, approval, and export audit-logged.
Validation, in place
A flag raised in the laboratory module is the same flag the QA reviewer clears and the project manager sees on the readiness view.
Book a DemoGulf Coastal Ph. 2 / All areas / Open issues
| Ref | Layer | Record | Raised by | Severity |
|---|---|---|---|---|
| IS-241 | L2 Engineering logic | BH-115/S11 | Engine | Blocker |
| IS-238 | L1 Data integrity | BH-107 depths | Engine | Error |
| IS-231 | L3 AGS compliance | LBST parent ref | Engine | Error |
| IS-226 | L4 Plausibility | GW vs. drilling | QA reviewer | Warning |