File server, SharePoint or Google Drive, with the permissions already in place. Nothing moves.
Lomara extracts projects, borings, locations, clients and years, even from scanned PDFs. We check locations with you.
Every past project and boring on one map, over hazard, geology and terrain layers.
Questions answered from your own files, with every source linked. Teams next.
Type an address, pick a radius, and see every past project and boring nearby, over hazard, geology and terrain layers.
An agent in Slack (Teams next) that answers from your own proposals, reports, logs and lab data, and links every source it used.
The name comes from loam, a soil engineers log every day. Every proposal, boring log and report your firm has written is a layer in its own ground. Lomara samples it, so the layer you need comes up with its source attached.
Decades of work settle into project folders, old proposals and a few senior engineers' memories.
Lomara connects to your files where they live and logs the projects, borings, locations and answers inside.
The layer you need surfaces with its source: a pin on the map in Ground, a cited answer in Ask.
Relevant-experience tables in minutes, not a day of digging through old SOQs.
"Similar jobs in the East Bay, last 10 years"Scope a new site with everything the firm already learned nearby.
"What did we find within half a mile?"Plan borings around the gaps, with past logs one tap away.
"Where's our coverage thin on this alignment?"Go/no-go on a bid with the site's hazards and the firm's history in view.
"Is this parcel in a liquefaction zone?"One archive, two ways in, with the permissions you already have.
No answer, snippet or filename from a file you can't already open. Users and groups come from Microsoft or Google.
Files are indexed for retrieval only.
Admins see what was asked and what came back.
Projects, borings, clients and years pulled from old files.
It can't change your archive.
Hazard zones, fault traces, geology and terrain.
No recommendations or design parameters. The PE computes and signs.
File server, SharePoint or Google Drive. Nothing to migrate.
In 1983, Robert Wong, Ph.D., PE, GE, founded AGS, Inc. in the San Francisco Bay Area. His wife built the firm alongside him, running the business, accounting, finance and office. Their daughter, Alice, grew up seeing both sides of a firm: the engineering judgement that wins the work, and the operations that keep the doors open.
When Alice joined AGS in 2023, she found four decades of knowledge about the ground sitting in folders and in a few senior engineers' heads. So she built the tools to put it to work, designed hand in hand with AGS's engineers, who tested every version on live bids: first at AGS, now for firms like it.
Start with a free fit check. Most firms then run a 90-day pilot on one team before going firm-wide.
See whether your archive is ready, before anyone shares a file.
Your archive mapped and answering in Slack, with a go/no-go at week four.
Lomara across the firm, after a pilot proves it on your own work.
[Pilot fee] and firm-wide pricing to confirm before launch.
Yes. Ground runs in the browser; Ask runs in Slack today, with Teams next. Users and groups come from Microsoft or Google.
That's the point. Scanned PDFs, old proposals and field notes are what Archive Setup is for, and we check locations with you before the map goes live.
No. Lomara uses the permissions in your source systems. No answer, snippet or filename comes from a file the asker can't already open.
No. Your files are indexed for retrieval only.
Every answer cites its source so it can be checked, and if nothing was found it says so rather than guessing. Reply to it in Slack to flag a wrong result; that feedback is how it improves.
No. It finds and cites. Your engineers compute, recommend and sign.
In 20 minutes we'll show its hazards, geology and terrain on the map, and what your archive could add to it.
No files needed for the first call.Or a project number. Ground centres on the site and draws your search radius.
Past projects and borings appear, each linked to its reports and logs.
Hazard zones, fault traces, geology and terrain, with a summary of what applies.
A relevant-experience table, sourced row by row, ready for the SOQ.
Every project the firm has worked, with number, client, year, discipline and documents, on one map.
Points with depth, date and groundwater, linked to the log and the report it came from.
Public seismic, fault, flood and geologic maps under your own archive, with a site summary of which zones apply.
Every similar project in a city or radius, with client and year, exported for the proposal in minutes.
Archive Setup pulls locations and borings from old reports and proposals, scanned ones too.
Start with a free fit check. Most firms then run a 90-day pilot on one team before going firm-wide.
See whether your archive is ready, before anyone shares a file.
Your archive mapped and answering in Slack, with a go/no-go at week four.
Lomara across the firm, after a pilot proves it on your own work.
[Pilot fee] and firm-wide pricing to confirm before launch.
From your own project sheets, proposals and reports. Archive Setup pulls addresses, coordinates and site descriptions, including from scanned PDFs, and we check every estimated pin with you before the map goes live.
Exact pins come from coordinates or addresses in a report. Estimated pins are inferred from a site description, and Ground shows them differently so nobody mistakes one for the other.
Hazard zones, fault traces, surficial geology and terrain. We launch with California public layers; other states on request.
No. Ground runs in the browser. Type an address or project number and pick a radius.
Yes. The relevant-experience table exports for the SOQ, with the source linked on every row.
The same people who can open the files today. Ground uses the permissions in your source systems.
Bring an address you're bidding on. We'll show its hazards, geology and terrain, and what your archive could add to it.
No files needed for the first call.Mention @lomara with a place, a scope and the fields you need.
Your proposals, reports, logs and lab data, with your permissions.
Every fact links to the report, log or proposal it came from.
No source, no answer. It lists what it searched instead.
Projects most like a new bid, ranked by scope and distance, each linked to its report or proposal.
Boring ID, depth, groundwater and source report, one row per boring.
When the files you can open don't hold the answer, Ask says so and shows what it searched.
Ask posts a digest to #bd-leads: each new opportunity with the firm's closest past projects and nearest borings.
A place, a scope and the fields you need. Tell it which folder to search and it narrows the results.
Only files the asker can already open.
No source, no answer.
No recommendations, conclusions or design parameters.
You review it; the PE computes and signs.
It can't change your archive.
Indexed for search only.
What was asked, what came back.
A private app in your workspace.
Start with a free fit check. Most firms then run a 90-day pilot on one team before going firm-wide.
See whether your archive is ready, before anyone shares a file.
Your archive mapped and answering in Slack, with a go/no-go at week four.
Lomara across the firm, after a pilot proves it on your own work.
[Pilot fee] and firm-wide pricing to confirm before launch.
In Slack today, installed as a private app in your workspace. Teams is next. It runs on the same archive as Ground.
Your file server, SharePoint or Google Drive: proposals, reports, boring logs and lab data. Only files the person asking can already open.
It says so, and lists what it searched. No source, no answer.
No. It finds and cites, and gives you sourced material. Your engineers recommend and sign; marketing writes the final copy.
No. Files are indexed for search only, and every question is logged for admins.
Every team gets a one-page prompting guide at rollout. Tell it which folder to search (Projects, Proposals or Library) and it narrows the results.
In 20 minutes we'll show what Ask finds in a sample archive, and what it could find in yours.
No files needed for the first call.