This document discusses how simple software agents can help manage smart cities. It proposes using agents to represent individual urban elements like buildings, infrastructure and citizen activities. Agents could help cities transition from just collecting urban data to actively "farming" and reusing municipal information. The document provides examples of how agents could help with tasks like managing public art/monuments, coordinating streetlight repairs based on citizen reports, and resolving data issues between city departments. Developing agent-based applications is presented as a way to apply complexity theory and make cities more participatory, adaptive and knowledge-driven.
Powerful Google developer tools for immediate impact! (2023-24 C)
UCL - Future Cities
1. Simple Agents for Smart Cities
from Agent-based Modeling to Agent-oriented Programming
Future Cities and Digital Technologies September 27, 2013
UCL-CASA
Guerin & Carrera
6. goal of City knowledge
To promote the transformation of Municipalities from
Hunter-gatherers of urban data to Farmers of
municipal information
7. Dissertation (MIT) - 2004
City Knowledge: An Emergent Information
Infrastructure for Sustainable Urban Maintenance,
Management and Planning
http://hdl.handle.net/1721.1/28790
(google: ”City Knowledge MIT”)
8. philosophy of city knowledge
treated as any other City Infrastructure
farmed not hunted
atomized by urban element
re-combined and re-used
Urban Information should be:
9. Premises of city knowledge
Cities are “finite”
City = Structures & Activities
Municipal gov. controls urban change
Past can be reconstructed (once)
Future can be intercepted (daily)
112. Simple Agents for Smart Cities
Conclusions and Future Research
• Deploy Agents for Structures and Activities
• Define the Agents API
• Refine CK Console and Chrome Extension
• Develop more Real-world Applications with Agents
• Explore the Implications for City Government
• Apply Complexity Theory to Urban Gradients
Work closely with CASA!
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5:
All categories of public art in the catalog
Runs on a single machine or cluster Single domain Data limited to specific application “ Toy Models” Slide 3: City 3D (ca. 1980-90) – representing structures Slide 4: Evacuation (late 90’s) – Structures and activities Slide 5: