Home/Solutions/Government
AQ.SOL.03

The whole program, in one place.

Program pages for council, the public and each department, built from GIS, the ERP and the systems departments already run. Contractors' RFIs, submittals, schedules and pay applications worked in one place, with outside firms signing in free. Start with one program page and keep every system you have.

Cadastral parcel and zoning map for municipal records
RECORDS / 10.26 PARCELS AND ZONING

The problem

A city or county runs on systems that do not talk to each other. Public Works has GIS and work orders. Finance has the ERP. Capital projects live in project management tools, and permitting, revenue and records each have a system of their own. Every department keeps its own data, and a complete picture means pulling from everywhere and reconciling by hand.

Contractors send as-builts, pay applications and schedules as attachments. A report for council or the public is built by hand. When a project is finished, the infrastructure it built is still not in the systems that maintain it.

The whole program, in one place

Aquifer puts program pages, maps, contractor coordination, schedules and accounting on one platform for the agencies that own capital programs and operate what they build. It stays in sync with ArcGIS, the ERP, Primavera and the 70+ systems departments already run, with one model of the program underneath, where every asset, activity, document, person and company carries its source and date. Take one part and keep everything else.

Canvas

A program page for council, the public and each department, read on a laptop or a phone. Spend against budget, open items and a map colored by status, from the systems you already run. Share it by a link that always shows the latest approved version, and take the link back when you need to.

Studio

Where the pages and maps are built, from GIS and the systems each department runs. Aquifer AI drafts the map or the dashboard from a sentence, and a person approves each version before anyone outside sees it.

Coordination

RFIs, submittals and open items with every contractor on every project, each with who it is waiting on and for how long. Outside firms sign in free and see only what they owe.

Handover into the record

Closeout submittals, as-builts, O&M manuals and warranties build the handover record as the project closes, checked against your template, so the asset is in the record when the project is accepted.

Accounting

AP for contractor pay applications, coded to project, fund and program, in sync with the ERP you run today. Aquifer AI reads the PDF, codes it and routes it through your approval chain by amount and dimension, and the audit log records every step. The ERP keeps its ledger; move it when you choose.

Scheduling

Every contractor’s schedule in one place. Import each XER or P6 XML, read milestones and variance across the program, and share it with the contractors and the departments without a license for each of them.

Integrations

A product on its own, with no app required. 70+ pre-built connectors keep ArcGIS, the ERP, work management, revenue and permitting systems in sync, so the assessor’s record, the parcel boundary and the tax roll agree, field updates from ArcGIS Field Maps reach the system of record, and lineage shows where every value came from. A copy in Snowflake or your warehouse feeds the dashboards you build and the open-data platform you already run.

Exchange

A product on its own, with no app required. Pay applications, as-builts, schedules, RFIs and submittals move between your systems and your contractors’ without portals or re-keying. Share with other jurisdictions and regional agencies the same way. Each side decides what it shares, keeps its own systems, and guests join free.

Aquifer AI

Aquifer AI reads the pay application, drafts the program page, checks the schedule and answers questions across the program. Bring your own AI through an MCP server or a ChatGPT Action.

The platform, as government uses it.

In the product, for government.

A program dashboard drafted by Aquifer AI from the program's data

Where the day‑to‑day changes.

Patterns we see across this industry, and what changes on the platform.

UC.01 Reporting to council
Before

Pull data from each contractor, combine it with the ERP and GIS, build the deck for council by hand. It is out of date by the meeting.

→
After

A Canvas program page with a map colored by status, spend against budget and open items, shared with council and the public by a link that always shows the latest approved version.

UC.02 Contractor pay applications
Before

Pay applications arrive by email. Finance keys them in, codes each one to project, fund and program, and chases the approval chain.

→
After

Aquifer AI reads the pay application, codes it to project, fund and program and routes it through your approval chain in Accounting, with an audit log, in sync with your ERP.

UC.03 Contractor as-built delivery
Before

The contractor emails shapefiles. The GIS team reviews, reformats and imports them by hand. New infrastructure sits in limbo.

→
After

As-builts arrive through Exchange in your format, or as closeout submittals in Coordination, and land in ArcGIS. The infrastructure is in the record when the project is accepted.

UC.04 Property and parcel data
Before

The assessor updates property records. GIS updates parcel boundaries. Revenue bills from another source. Discrepancies surface in audits.

→
After

Integrations keeps the assessor, GIS and revenue systems in sync. One update flows everywhere, with the source and date on every value.

The systems government runs, connected.

17 systems across 4 categories.

GIS & Mapping

5 connectors
ArcGISArcGIS Field MapsArcGIS Survey123GeoJSONShapefile

ERPs & Financials

4 connectors
Oracle Cloud ApplicationsSAPMicrosoft Dynamics 365Tyler Technologies

Project Management

3 connectors
Oracle PrimaveraAutodesk Construction CloudProcore

Data & Analytics

5 connectors
SnowflakeAzure SynapsePower BITableauSocrata

Something useful before any sales call.

Describe the page you need and name one system it should read from. Aquifer AI drafts it from live data; you leave with a live page and a share link.

A page in a day

Describe the page you need. Leave the session with a live one and a share link.

  • A live page on your own data, authored from your description
  • A share link for the people who need to read it, on a laptop or a phone
  • The next two pages you would build, written down

The whole program, in one place.