Designing the AI-Ready City
Connecting GIS, digital twins and engineering data across the capital-project lifecycle.
Event Summary
Capital projects create some of local government's most valuable — and most fragmented — information. Planning studies, engineering drawings, BIM models, permits, utility records, inspection reports, schedules, contracts and as-built documentation are often stored in different systems and formats.
This event examines how GIS, BIM, digital twins and AI can create a connected project environment extending from early planning and public engagement through design, construction, inspection and long-term maintenance.
Speakers discuss scenario modeling, project prioritization, design coordination, construction monitoring, automated document analysis, schedule and risk detection, and the handover of accurate project information into operational asset systems.
Key Takeaways
Attendees will learn:
- 01
How to connect GIS, BIM, engineering and construction information.
- 02
Why AI readiness should be included in project data requirements.
- 03
How digital twins can support planning, construction and operations.
- 04
How to reduce information loss between project delivery and asset maintenance.
- 05
How AI can assist with document review, risk identification and progress monitoring.
- 06
How to identify conflicts between projects occurring in the same location.
- 07
How to create a location-based capital investment portfolio for leadership and the public.
Resource Guide
AI-Ready Capital Project Guide
Connect GIS, BIM and engineering data across the project lifecycle so information survives the handover into operations.
Data you should have on hand
- Capital project portfolio with location and phase
- Design and BIM models plus as-built documentation
- Permits, utility records and easements
- Construction schedules, contracts and change orders
- Inspection reports and progress imagery
Readiness checklist
- AI and data requirements are written into scopes and contracts
- Deliverable standards specify formats, attributes and coordinate systems
- As-builts flow into asset systems as a required closeout step
- Project locations are visible in one portfolio map
- Conflicts between co-located projects are detected before bid
Questions to ask internally
- How much project information do we lose at handover?
- Who owns the as-built to asset-record conversion?
- Which document reviews could AI triage first?
- Can leadership see capital investment by neighborhood?
Next 90 days
- Add data deliverable language to the next three project scopes
- Publish a capital portfolio map for leadership and the public
- Pilot automated document review on one closed project
Metrics to track
- % of projects delivering compliant as-built data
- Days from closeout to asset record update
- Number of conflicts caught pre-construction
Attend this event