Incident Commander for Android Project

From Random Hacks of Kindness
Jump to: navigation, search

Contents

[edit] Incident Commander for Android Project

[edit] Summary

Problem Definition: Incident Commander

Initial event: RHoK 2.0 - New York

Incident Commanders, whether managing an international humanitarian crisis or a local volunteer response to a fire or medical emergency, need to understand where critical resources and points-of-interest are located e.g. Responders, Equipment, Locations, Security, Supplies, etc... The application will track Responders in real-time; give them route information to their target destinations; enable them to request urgent assistance should they be threatened; alert them to danger areas through virtual "fencing"; enable basic data collection via voice, web or SMS communications.

During the RHoK weekend the Incident Commander team developed a functional prototype android application, utilizing SMS messaging to send and receive incident alerts, location and real-time status updates through a user-friendly interface.

Capabilities built during RHoK include:

  • Track readiness prior to a call by gathering GPS coordinates for Responders (Complete)
  • Allow Responders to communicate whether they are responding via mobile application (Complete)
  • Tracking Responder progress to the Incident via regular location updates (in progress)
  • Provide Responder with Google Maps directions and text-to-speech updates en route (in progress)
  • Track Responders throughout Incident as they enter/exit hazardous areas defined by Command (future development)

[edit] Resources

Web-based Prototype: note: the web-based application (prototype) is a superset of the system's functionality. Android app specs are a targeted subset and should be achievable during the RHoK weekend. Narrow format for smartphones and tablets.

Open Source website:

Screen Mock-Ups

[edit] Members

  • John Reilly (Problem Definition Owner)
  • Shayne Adamski
  • Kane Albarron
  • Aidan Feldman
  • PJ Herring
  • Trishan de Lanerolle
  • Jason Lindesmith
  • Ralph Morelli

[edit] Status Updates

[edit] Day 1; 7PM EST

  • All team members versed on problem definition.
  • Design approach validated e.g. Use of SMS for data transfer between Android client and Google App Engine server.
  • User Interface wireframes in development; 80% complete for limited functionality.
  • Trinity College open source Android project identified as "donor" app for the following:
    • Background processing
    • SMS Send
  • Components to be built:
    • SMS Listener
    • App Initialization (using callerId via SMS to determine local Google Voice phone numbers.)
  • Open Source website updated with temporary repository for working Android code (team members added as contributors.)

[edit] Day 2; 12PM EST

  • User Interface Completed
  • Listener built
  • Finalizing server adapters
  • Competition entry page updated

[edit] ASKS

  • Android code or patterns for an SMS Listener (maybe "notifications manager"?)
  • Android code or patterns for "intents"...
  • Folks who have developed for Android in Java who could knock-down be "on call" to knock down some obstacles in our way tomorrow.

[edit] Group Doodles

Personal tools