like Twitter for sensors

Yodit Stanton

Smart Cities: Reality vs Marketing

Government Digital Service Design Principles

Design for Smarter Cities?
1.

Start with (user) needs*

2.

Do less (provide resources (like APIs) that will help other people build things)

3.

Design with data (learn from real world behaviour)

4.

Do the hard work to make it simple (Release Minimum Viable Products early, test them with real users)

5.

Iterate. Then iterate again.

6.

Build for inclusion

7.

Understand context

8.

Build digital services, not websites

9.

Be consistent, not uniform

10. Make things open: it makes things better

https://www.gov.uk/design-principles

Chain of data custody between a Local

Authority and Devices
Sensor device > Data Provider > people >
DB > people > ETL > people> CSV > public
entity> people > ETL> IT Vendor> DW >
people > CSV > Sharepoint > Dropbox >
and us !!!

We want to create a commons around sensor data

Let us design solutions to

problems of today rather than
some unknowable future.

Things we havent figured out

-
-
-
-

Who maintains all these sensors?

Who pays for the infrastructure?
How can we make Smart Cities iteratable?
Filling the bridge between multiple domains
e.g. Architects vs Computer Scientists

Thank You
@yoditstanton