That's the idea. Check out this list of problem definitions: http://www.rhok.org/problem-definitions/full-list/ - these aren't pie-in-the-sky ideas that we came up with, these are real needs as described by real crisis responders.

Ideas are cheap, it's execution that matters: http://www.paulgraham.com/ideas.html

I can assure that these organizations are rife with ideas, bringing the ideas "to market" is the problem.

(I helped plan this event)

The code you write is your own. We encourage people to license their code under an OSI approved license.

Finally those academics are working with a real game. That ORTS thing was not at all representative of real RTSs.

The project treats game design as a math/science discovery problem where hypotheses must be created and tested via concrete games.

A related but more general question: When people talk of bits of infrastructure being connected or disconnected from the Internet, are they talking about the presence of direct, layer 3 connectivity (can I ping the airport's tracking systems?), any layer (if I hack the contracting company's intranet can I view aircraft positions through a series of proxies and application layers?) or actual electronic disconnection from the Internet (can you get only get in via getting your man on the inside the tweet the secrets from his cell)? Distributed infrastructural systems communicate Somehow...

Funny you mention that, I've already blurred all the maps. Enjoy: http://www.adamsmith.as/blurry_maps/

s/has/has not already/