Program pages and site maps from GIS, the ERP and asset management. Every contractor's schedule, RFIs, submittals and pay applications in one place, and the as-builts in the record when the work is done. A model built for solar, with every deadline that carries money.
Utilities and asset owners run capital programs and operations on systems that do not share a record. GIS holds the asset locations, the ERP holds the money, Primavera holds each contractor’s schedule and work management holds the maintenance. Contractors send as-builts, pay applications and progress as email attachments, and someone reconciles it all by hand.
A capital project finishes, and the assets it built are still not in the systems that operate them. Solar developers and EPCs carry the same problem with a clock on it. Interconnection, site control, permits and tax-credit dates each have money attached, and they are tracked in spreadsheets.
Aquifer puts program pages, maps, schedules, contractor coordination and accounting on one platform, kept in sync with ArcGIS, Oracle, SAP, Primavera and the 70+ systems you already run. One model of the program sits underneath, with assets, activities, documents, observations, people and companies, every value carrying its source and date, read by every app. For solar there is a model of its own. Take one part and keep everything else.
A page for the program, a map for each site and an asset view for operations, read by leadership, engineering and the contractors on a laptop or a phone. Studio builds them from ArcGIS, the ERP and the EAM, drafted by Aquifer AI and approved by a person, with GIS and asset views down to the element.
Start at a map of the program colored by status, go down to a site and the equipment on it, and see its schedule, open items and cost together.
RFIs, submittals and open items with every contractor on the program, each with who it is waiting on and for how long. Contractors sign in free and see only what they owe.
Closeout submittals, as-builts, O&M manuals and warranties build the handover record as they come in, checked against your template, so the asset record is ready when the work is done.
Every contractor’s schedule in one place. Import each XER or P6 XML, read milestones and variance across the program, and share the schedule with contractors without a license for each of them. For solar, the critical path runs through interconnection as well as construction.
AP for contractor pay applications, coded to project and funding source, in sync with the ERP you run today. Aquifer AI reads the PDF, codes it and routes it through your approval chain with an audit log. EPCs run certified payroll and prevailing wage from the same platform. The ERP keeps its ledger; move it when you choose.
A product on its own, with no app required. 70+ pre-built connectors keep ArcGIS, your ERP, your EAM and Primavera in sync, with asset records, work orders and cost flowing in both directions, field updates from ArcGIS Field Maps reaching the system of record, lineage on every value, and a copy in Snowflake or your warehouse for Power BI and Tableau.
A product on its own, with no app required. As-builts, pay applications and work orders move between your systems and your contractors’ without portals or re-keying. Each contractor sees only what you share with them, guests join free, and the data arrives in your format.
Public reference data about land, grid and rules, built once and kept current, with each company’s projects on top. Score sites, track the dates that carry money with the buffer left on each, keep a tax-credit evidence binder as the work happens (evidence, not tax advice), roll installed quantities into the pay application, keep one record per interconnection request, and assemble the handover package and the data room.
Aquifer AI reads pay applications, study PDFs and leases into the model with a citation on each value, 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.
A program page with every site on a map colored by status, read by leadership and the contractors on a laptop or a phone.
Read about Canvas →Site maps and asset views built from ArcGIS, the ERP and the EAM, drafted by Aquifer AI and approved before anyone outside sees them.
Read about Studio →RFIs, submittals and closeout with every contractor, with as-builts, O&M manuals and warranties building the handover record.
Read about Coordination →Every contractor's schedule imported from P6 and read in one place, with milestones and variance across the program.
Read about Scheduling →Contractor pay applications read by Aquifer AI, coded to project and funding source and routed for approval, in sync with SAP or Oracle.
Read about Accounting →ArcGIS, the ERP, the EAM and Primavera in sync, with asset records and work orders flowing both ways and a copy in Snowflake.
Read about Integrations →As-builts, pay applications and work orders between your systems and each contractor's, in your format, with guests joining free.
Read about Exchange →Public land, grid and rules data with your projects on top, every deadline that carries money, and the evidence binder beside it.
Read about the solar model →Patterns we see across this industry, and what changes on the platform.
GIS updates asset locations. The ERP updates asset records. Someone reconciles them when the audit comes.
A change in either system flows to the other through Integrations, with lineage on every value. The asset record agrees everywhere it is read.
The contractor emails shapefiles. The GIS team reviews, reformats and imports them by hand. New assets sit in limbo.
As-builts arrive through Exchange in your format, or as closeout submittals in Coordination, and land in ArcGIS and your EAM. The assets are in the record when the work is done.
Pull from each contractor's system, combine it with internal data, build the report in Excel.
Every contractor's schedule, pay applications and open items on one Canvas page, with the program map beside them. Leadership opens the page instead of waiting for the report.
Pay applications arrive as PDFs. Someone keys each one into the ERP, codes it to the project and the funding source and chases the approval.
Aquifer AI reads the pay application, codes it to project and funding source and routes it for approval in Accounting, in sync with the ERP you run.
17 systems across 4 categories.
We use analytics cookies to see which pages are useful, and LinkedIn and Google tags to measure our ads and show them to past visitors on LinkedIn. Privacy notice