Datgel Alternatives for Geotechnical Data Management and Logging

Why geotechnical teams start looking for a Datgel alternative

The usual trigger is a platform question rather than a product one. Datgel tooling sits on top of gINT, so a firm reviewing its geotechnical software is really deciding how long to stay on a desktop centred workflow while the wider industry moves toward cloud data management, field capture on tablets and ground data feeding design models rather than only paper logs. That is a strategy decision about where the firm wants to be in five years, and the add ins get pulled into it even when they are working perfectly well.

The second trigger is scale of the wrong kind. A consultancy accumulates hundreds of investigations, each impeccably logged, and still cannot answer what it collectively knows about a region. Individual project data is excellent and corporate memory is nil. Add a client framework that demands a bespoke log format, a laboratory adding test types nobody configured for, and a bid team that wants a map of prior work rather than a folder of PDFs, and the shape of the requirement has moved beyond what a logging toolset was ever meant to cover.

What Datgel genuinely does well

Be fair before you change anything. The specialism is real. Geotechnical laboratory data is one of the messier data structures in engineering: dozens of test types, each with different result sets, staging, units, corrections and reporting conventions, and clients who each want them presented slightly differently. Handling that properly requires people who understand both the engineering and the data model, and that combination is rare. Firms that use the Datgel tooling generally do so because it handles complexity that generic software flattens.

The second strength is the consultancy nature of the relationship. Custom log templates, AGS transfers, database structures and data transformations delivered by people who know geotechnics is a different experience from filing a ticket with a large vendor. For a mid sized firm with no internal data specialist, that is genuinely valuable and it is the reason clients stay for years. There is also value in staying on a mature, well understood desktop platform: it is predictable, it works offline, and the engineers who use it already know exactly how it behaves.

Where it actually strains

Platform dependency is the first pressure and the most strategic. The tooling extends gINT, so your roadmap is tied to decisions made about that platform by someone else. That is not a criticism of anyone's product, it is simply a structural fact you should factor into a five year plan, especially as cloud and field capture expectations rise on projects.

Vendor concentration is the second. A specialist supplier gives you depth you cannot get elsewhere, and it also means your templates, your schema knowledge and often your data transformations sit with a small team. Ask directly what happens if that relationship ends, and get the answer in a form you can act on rather than a reassurance.

Layered licence economics is the third: you are paying for the base platform and the add ins, per user, in an organisation where far more people want to read ground data than to produce it. The practical result is PDFs circulating as the working copy. Customisation through consulting is the fourth pressure, and it cuts both ways: expert work delivered properly, but every change is an engagement rather than something a competent internal user can do on a Tuesday. Finally, desktop and project centred structures make cross project reporting awkward, which is exactly the question firms increasingly want to answer.

Your real options

There are four honest paths and staying is a genuine one. If your laboratory complexity is the hard part of your work and the tooling handles it, replacing that with something more generic is a downgrade dressed as modernisation. Log quality and lab fidelity are what your clients actually see.

Switching is the second path. Bentley OpenGround is the obvious cloud direction for firms who want managed geotechnical data with vendor maintained schema and standards handling. EarthSoft EQuIS suits organisations whose work is as much environmental and monitoring as geotechnical. GeoDin from Fugro is another established option in ground investigation data management. Smaller teams with modest log volumes sometimes drop to RockWare LogPlot or Golden Software Strater and hold the data in a database they control. Each of these relocates the schema problem rather than removing it, so compare on the parts that actually hurt you.

The third path is unbundling, and this category supports it unusually well because AGS gives a clean, documented boundary. Keep the specialist tooling for what it is best at, live project logging, laboratory complexity and template fidelity, and build a corporate layer that ingests AGS from every completed job regardless of who produced it. The fourth path is full replacement with custom software, which fits owners, operators and contractors whose needs are narrower and more repetitive than a consultancy's, and who mainly need a durable record rather than a production tool.

When a custom build pays back

The build case is strongest above the project, not inside it. A firm sitting on a decade of investigations with no way to query them together is holding real commercial value it cannot reach. Building a searchable, mapped ground database that ingests AGS and links investigations to sites, clients and frameworks is a well bounded problem with a documented data format, and the payback shows up in bid quality, in avoided repeat investigation and in the speed of answering a client question during a pitch.

It also pays back when a specific workflow is eating senior hours. Automated client specific reporting packs, laboratory result validation against acceptance criteria, or a review and approval workflow for logs before issue are all repetitive, rule driven tasks with a measurable hourly cost. Those are the tasks software removes permanently rather than merely relocating.

It does not pay back when the underlying discipline is inconsistent, because a central database over uneven inputs produces confident wrong answers. It does not pay back as a way of avoiding standards work, since AGS compliance is precisely what makes any of this portable. And it does not pay back if the firm will not name an owner for the schema, because geotechnical data models drift within a year of losing their custodian.

Migration reality

The good news is that the substantive data is portable by design. AGS exists so that investigation data can move between organisations and systems, so boreholes, samples, strata, in situ tests and laboratory results can travel in a documented, vendor neutral form. That single fact makes this category far less risky to leave than most enterprise software.

What does not travel is the accumulated craft. Log and report templates, custom fields the firm added over years, laboratory schedule configuration, project metadata, coordinate and datum handling, and attached documents such as field records, photographs and laboratory certificates. Assume templates get rebuilt rather than moved, and put a realistic number against that instead of discovering it halfway through.

Practically, run both approaches on one live project of average complexity, produce the same log set from each, and have the engineer who signs logs compare them line by line. That comparison is the acceptance test, because a log a client reviewer rejects costs more than any licence saving. Then migrate historical data one framework or one client at a time so you can validate the process before committing ten years of records to it.

Cost bands and the honest recommendation

Datgel is sold as add in licensing on top of the base platform, alongside consulting for templates and data work, so your total is a licence line plus a services line and both should be in the comparison. Confirm current terms with the vendor rather than working from an old quote, because licensing models in this category change.

On the custom side, from what Digital Heroes delivers: a focused build, an AGS native corporate ground database with search, mapping and automated reporting, runs roughly $40k to $100k over 8 to 14 weeks. A full ground data platform covering field capture, laboratory result handling, validation workflow, corporate search and asset linkage runs roughly $140k to $300k. Those are one time build costs plus hosting rather than recurring per user licences, which is the whole reason the maths changes for firms with many occasional viewers.

Stay if laboratory complexity and template fidelity are the hard part of your work and the tooling handles them. Switch if you want a managed cloud platform with vendor maintained schema, or if your work has drifted toward environmental monitoring. Build the corporate layer, not the logger, if your problem is that years of investigations are unqueryable. Replace outright only if you are an owner or contractor who needs a durable ground record rather than a production toolset.