BTMAPS for Moscow SYSTEM OUTPUTS PART II

Team Number: 7 Subteam University UCD: Mark Hopkins, Pat Kavanagh, Philip LEstrange Subteam University Penn State: Dzul Fadli Aizat, Kevin Voller, Eric Werkheiser Subteam University of So Paulo: Bruno Azenha, Emanuel Valente, Rafael Mariano, Robson Aleixo. Output Screen Summaries: Output Screen Name 1. Country Embassy (Web Page) 2. Routes Status 3. Utility Status 4. Media (Web Page) Description Shows through a web page the citizens information (with nationality from that country) involved by attack, either infected or dead. Shows what roads are blocked for some reason, traffic intensity, subway and highways. Stakeholders Foreign Countries & Embassies Moscow Public Transportation, Moscow/Russian Road Authority

Shows what utility service (water, energy, commu- Utility Providers nication) is working or is in trouble. Shows information (through a web page) about the utility services and it has the option to download the feed (rss) file from each of utility. So the Media will be able to disseminate information of use to Moscow citizens. The GUI provided the NGOs with: Live Feed: News, Messages and Locations of Established Camps Media

5. MBRS NonGovernment Organizations

Non-Government Organization

Inventories: List of Supplies Available, Out of Stocks and On Delivery Trucks. List of NGOs: Messaging System Between NGOs to Coordinate Next Moves 6. MBRS: GovThe main map provides a resizable map, provided Government Incident ernment Incident by Google Maps API, which can be zoomed into Team Team and moved around. The overlaid elements shown are traffic (red lines represent heavy traffic, green represent light traffic) and incident reports that have associated locations. The color of the dot corresponds to the incident report shown at the bottom. More details on any of these reports can be summoned by double clicking on the dot, either on the map or next to the report on the bottom of the screen. The tabs above the map correspond to overlays that can be chosen to be shown on the map. Any combination of overlays can be chosen. Shown is only the health overlay (and traffic; the system can recognize when such simple additions as traffic patterns will interrupt view and will make these invisible, unless specified by the user). The health overlay shown uses varying degrees of color cloud to track the spread of contaminant. Buttons on the lower right of the screen open new windows in which messages sent directly to the Government Incident Team can be viewed. In the upper right is also a tab to view the map fullscreen. 7. MBRS: Hospi- Shows the most important data for the hospital to Hospitals tal output screen function. Shows real time data and incoming messages to help better respond to changing events. The tabs allow the user to focus in on specific patients, doctors or their total amount of supplies on hand. 9. Register of Calls received and location 8, 9 GIS Map 8, 9. Location Map Detailed information on call times, locations and Fire Service, Ambulance description of the nature of the calls. These could Service, be tagged and categorised to allow aggregation Command Centre and show trends. Using different symbols to highlight impacted areas for selected stakeholders Showing antidote centres etc. Emergency Services, Command Centre Public, Emergency Services,

Command Centre 8. Hospital Capacity 9. Utility & Comms Infrastructure Status 9. Summary Screen 9. Twitter Trend Feed Analysis Shows status of hospital capacity - could be a graphical report Emergency Services

Traffic Light Report showing status of various utility Army, Emergency Serand infrastructural services vices, Local Government Shows overall status of the system, scoresheet on Incident decision centre, scale of 1-5 of threat status Command Centre Analysis of public reaction generated from Twitter Incident decision centre, feeds, breaking news trends related to the inciCommand Centre dents.

GUI Mockups: (See numbered row in table above for name, description, and stakeholder list) 1