Bentley OpenGround Alternatives for Geotechnical Data Management

Why geotechnical teams start shopping for a Bentley OpenGround alternative

The trigger is usually a licence renewal landing next to a project margin review. A firm looks at what it spends on geotechnical data software, counts how many people genuinely need it against how many need to look something up occasionally, and concludes that the ratio is wrong. Nothing has failed. The logs are produced, the data is stored, the projects ship. The question is whether the value is proportionate, and once that question is asked out loud it does not go away.

The second trigger is the gap between having data and using it. A firm accumulates hundreds of investigations across a region and cannot easily answer a question that should be trivial: what do we already know about ground conditions within two kilometres of this site. Individual projects are well managed and the corporate memory is not. Add client specific log formats that need a template change for every framework, laboratory schedules that keep growing new test types, and the increasing expectation that ground data feeds a digital twin or a design model rather than only a PDF, and the software that was scoped as a log production tool starts feeling narrow.

What OpenGround genuinely does well

Be fair before you replace anything. Geotechnical data has a genuinely awkward structure. A borehole is a hierarchy of samples, strata, in situ tests, installations and laboratory results, each with its own attributes, depths and units, and each with a paper trail. Getting that schema right is not a weekend of work, and OpenGround inherits a long lineage of doing it properly, including support for the AGS data transfer format that the industry runs on.

Log and report production is the second real strength. Producing a borehole log that is legible, consistent, correctly scaled and acceptable to a picky client reviewer is a typesetting problem as much as a data problem, and it is the sort of thing engineers wildly underestimate until they try to reproduce it. There is also value in sitting inside a wider infrastructure stack, so ground data can travel toward design and modelling tools rather than dying as an attachment on a report. Finally, having a vendor maintain the schema and the AGS handling as standards evolve is worth something on its own, because that maintenance never stops.

Where it actually strains

Per user economics is the pressure most firms feel first. Geotechnical data is consumed far more widely than it is created. Designers, project managers, environmental specialists and bid teams all want to look at it, but licensing them is hard to justify, so they get PDFs, and the PDF becomes the working copy. Once that happens, the database stops being the place people go.

Configuration ceilings come second. Every consultancy has its own laboratory schedule quirks, its own logging conventions, its own client specific field requirements, and packaged systems accommodate that to a point and then push you into workarounds. Reporting rigidity is closely related. Standard logs and standard summaries are handled well, but the cross project question, the one about regional trends or about how many sites in a framework hit a particular condition, usually means an export and a spreadsheet.

Integration burden is the fourth pressure. Field data collection apps, laboratory information systems, survey and coordinate data, design software and document management all need to exchange data, and each connection must survive both sides changing. Finally there is portability, and here the industry is better placed than most: AGS export means your data is not truly locked in. That is worth remembering, because it makes a custom option far less risky in this category than in others.

Your real options

There are four honest paths and staying is a real one. If your investigations are well run, your logs pass client review and your only complaint is licence count, negotiating access tiers or moving casual users to read only distribution is cheaper and safer than changing platforms.

Switching is the second path. Firms with heavy gINT investment sometimes stay on that lineage and extend it with specialist add ins such as those from Datgel, particularly where complex laboratory schedules are the difficulty. Organisations whose work is environmental as much as geotechnical often shortlist EarthSoft EQuIS, because contaminated land and monitoring data is where it concentrates. GeoDin from Fugro is a long standing option in ground investigation data management. Smaller teams producing modest volumes of logs sometimes use RockWare LogPlot or Golden Software Strater and keep the data itself in a database they control. None of these removes the underlying schema problem, they relocate it.

The third path is unbundling, and it fits this category unusually well because AGS gives you a clean boundary. Keep the packaged tool where it is strongest, log production and standards compliant storage on live projects, and build a corporate data layer that ingests AGS from every project, whoever produced it, including data supplied by contractors and other consultants. That layer becomes your regional knowledge base, your bid support tool and your reporting engine. The fourth path is full replacement with custom software, which suits contractors, owners and asset operators whose needs are narrower and more repetitive than a consultancy's.

When a custom build pays back

The build case is strongest for the corporate layer rather than the project layer. If a firm holds ten years of investigations and cannot query them together, the value locked up is significant and the technical problem is tractable, because AGS is a documented format and the schema is known. Building a searchable, mapped, cross project ground database that ingests AGS regardless of which software produced it is well understood work with a clear payback in bid quality and reduced repeat investigation.

It also pays back for asset owners and infrastructure operators. A rail authority, a water utility or a port does not need a consultancy's full toolset. It needs a permanent, queryable record of ground conditions across its estate, linked to structures and assets, that outlives any individual consultant appointment. Packaged geotechnical software is priced and shaped for producers of data, not custodians of it, and the mismatch is expensive.

It does not pay back if your data discipline is inconsistent, because a central database over unreliable inputs simply centralises the unreliability. It does not pay back if you are trying to avoid learning AGS, since standards compliance is the thing that makes any of this portable. And it does not pay back if nobody will own the schema, because a geotechnical database without an owner drifts within a year.

Migration reality

This is the rare category where migration is genuinely more manageable than average, and you should use that to your advantage. AGS export gives you a documented, industry standard representation of the substantive data, which means the core of your information is portable by design rather than by vendor goodwill.

What does not travel is everything around it. Log templates and layout definitions, custom fields your firm added over the years, laboratory schedule configurations, project metadata, coordinate systems and datum handling, and attached documents such as field records, photographs and laboratory certificates. Budget for reproducing templates rather than migrating them, and expect that to be a meaningful slice of the work.

Practically, run the two side by side on a live project of average complexity, produce the same logs from both, and have the engineer who signs the logs compare them line by line. That is the only test that matters, because a log that a client reviewer rejects costs more than any licence saving. Migrate historical data in batches, starting with a single completed framework so you can validate the process before committing years of records to it.

Cost bands and the honest recommendation

OpenGround is sold as a subscription within Bentley's licensing model, and the practical cost driver is how many people you licence rather than how much data you hold, so confirm current terms directly rather than working from a number quoted a few years ago.

On the custom side, from what Digital Heroes delivers: a focused build, an AGS native project or corporate database with search, mapping and automated log and summary output, runs roughly $45k to $110k over 10 to 16 weeks. A full ground data platform covering field capture, laboratory result handling, corporate search, asset linkage and reporting runs roughly $150k to $320k. Those are one time build costs plus hosting rather than recurring per user licences, which is exactly why the maths changes for organisations with many occasional viewers.

Stay if you are a consultancy producing logs at volume and your complaint is licence count rather than capability. Switch if your work is predominantly environmental, or if a specialist add in solves the laboratory complexity that is actually hurting you. Build the corporate layer, not the log producer, if your problem is that ten years of investigations are unqueryable. Replace outright if you are an asset owner who needs a permanent ground record rather than a production tool.