Cost from the ERP, progress from Procore, dates from the schedule, the drawings, the building model and the site itself, related into one model of the project. Every Aquifer app reads from it, so the numbers agree, and every value keeps its source and its date.
Schedules, costs, labor, RFIs, submittals, change orders, inspections and work orders, from the systems that run them.
Building models, drawings, specifications, engineering calculations, equipment schedules and material specs.
As-built conditions, photos, 3D scans, survey points, sensor readings and inspection results, each tied to the element it observes.
Documents describe elements. Activities install them. Observations record what was seen, and people and companies are assigned to the work. Every link carries where it came from and the dates it held, so two sources that disagree are shown side by side rather than merged.
A project with its status, dates and location, and one or more sites with their boundaries. A campus, a road corridor or distributed solar is one project with many sites.
Buildings, floors, rooms, walls, beams, pipes, ducts and panels, in a hierarchy, with their classification, their geometry and their properties. Road segments, bridges and valves for infrastructure. Arrays, inverters and transformers for energy.
Every activity with its planned and actual dates, who is assigned, which elements it touches, what it depends on, and its cost planned, committed, actual and forecast.
Each document with its version, what elements it describes and what activities it relates to. Drawings, specifications, submittals, RFIs, photos, scans, reports, permits, contracts, change orders and invoices.
Progress from a field report or a photo, a condition from an inspection or a scan, a measurement from a survey, an issue, a question and its answer. Each carries where it was observed, what it observed and how reliable it is.
People, companies, trades and roles, connected to the activities they do, the documents they author and review, the observations they report and the elements they are responsible for.
This drawing shows this wall. This task installs this pipe. This photo shows this beam. This RFI references this spec section. This revision supersedes that one. Each link carries its source, its confidence and the dates it held.
Spend against budget by project, open items by contractor, milestones against the baseline, on one page, with each number traceable to the system it came from.
A late activity with the elements it installs, the submittals and RFIs that gate it, the trade assigned, and the cost it carries, instead of a login per system and a spreadsheet.
Work in place by element and cost code, from field reports and photos, against what was planned and what has been billed.
The current revision for any element, the revisions it superseded, the RFIs that touched it, and the photo or scan that shows what is there now.
Procore, the ERP, the schedule, the drawings and the model, read through Integrations and kept current. Source data stays in your own datastore. The model holds what was understood and the references back.
Records are matched across systems by their source references, their location and their names. Aquifer AI reads the drawings, specifications and photos and proposes the rest, so a commitment, its invoices, the submittals under it, the drawings that show the work and the place it happens become elements, activities, documents and observations. Each link carries its source and its confidence.
Two sources that disagree are shown side by side, with their dates. Nothing is silently resolved. The model keeps history, so you can see the state of the project on any date.
Canvas pages, Studio dashboards and maps, Scheduling, Accounting, Coordination and Aquifer AI read from one model of the project. The numbers agree because they come from the same place.
Project and portfolio pages for everyone on the job.
Read about Canvas →Dashboards, maps and 3D views built from the model.
Read about Studio →Activities, dependencies and the critical path.
Read about Scheduling →Commitments, costs and billing by job, phase and cost code.
Read about Accounting →RFIs, submittals and open items, tied to the elements and documents they touch.
Read about Coordination →Answers questions about the project with the model behind them.
Read about Aquifer AI →What happens when two systems disagree?
Both values are kept with their sources and dates, and the disagreement is flagged where people read it. Nothing is resolved silently.
Can we start with one system?
Yes. The model starts with whatever you connect first, often Procore or the ERP, and grows as you connect more. Every app that reads the model works with what is there.
Where does AI fit?
Records are matched across systems by their source references, location and names. Aquifer AI reads drawings, specifications and photos and proposes the links the records alone cannot make, each with its source and confidence. People review what matters.
Does it work for horizontal construction as well as vertical?
Yes. The same model that holds a building's floors, rooms, walls and systems for vertical construction holds road segments, bridges, water mains and valves for horizontal construction, and arrays, inverters and transformers for energy. The solar model adds what solar projects need on top.
We use a small number of first-party cookies to understand which pages visitors find useful. No advertising, no third parties. Privacy notice
