BluePrint: Sahana First Response

Current Status

​Fit-Gap analysis spreadsheet

Available features:

Missing features:

1. Common Operating Picture with Crisis Mapping (who, what, when, and where)
2. manage event type specific work flows pre-populated message templates and messages (field-observation, casualty-illness, situation-information, response-resource, resource-messaging and management-summary reports)
3. input and output ​HXL #Event, ​SITREP and ​RM feeds [2] to serve as an aggregator and a publisher-subscriber
4. Desktop and Mobile applications to integrate and to server as a publisher and a subscriber
5. Approve or Reject asset management, incident reports, situational-reporting, and resource messaging
6. Support multiple language message delivery options: HTTP, RSS/Atom, SMS, Email, FTP
7. digitally sign the messages
8. ​Pictographs for reporting incidents (field and casualty-illness reports)
9. Incident specific SOP check list

Introduction

<What problem is this solution solving?> <How will this solution add value to Sahana?> <Name any similar existing solutions>

Briefly

Sahana First Response (SaFiRe) is designed to support a Simple Emergency Operation Center (EOC). An EOC could be as simple as a single terminal with a single user (e.g. a Dispatch Station) recording incident reports and dispatching an emergency service. The emergency service might be the maintenance engineers of a telecommunications service provider deployed to fix a backup power generator. A Police EOC would utilize for managing field-observation (burglary, accident, dispute) and casualty-illness reports (accident, murder). The Police response and resources allocated to an incident varies upon the scenario. The other extreme is managing a crisis such as an earthquake with many casualties, damages, and losses. All these, whether big or small, require managing a series of activities and sharing information across multiple Incident Command and Control System (ICCS) platforms.

Problem

Under a well-developed disaster management system, the Disaster Management Organization(s) of a Country should be aware of and should map every significant emergency incident or risk in the country. Disseminating such information among multiple agencies with disparate systems can be complicated. ​Multi-Agency Situational-Awareness (MASA) platforms facilitate the integration of silo-ed Organizations and dilutes inter-agency rivalry at every level of a National warning and incident management system. Such a platform that incorporates the ​Common Alerting Protocol (CAP) standard is far more likely to interoperate with National and International warning systems. Moreover, the CAP content standard lays out emergency policies and procedures for streamlined information sharing among multiple agencies.The ​World Meteorological Organization, ​International Telecommunication Union, and ​OASIS (Organization for the Advancement of Structured Information Standards) are advocates of CAP and continue to promote the adoption of the warning standard. Sahana Alerting and Messaging Broker (SAMBRO) is essentially a Sahana Eden template designed for Multi-Agency Situational-Awareness. Moreover, it adopts the CAP standard for Sahana to interoperate with other warning systems.

Stakeholders

<Who will be the users of the solution?> <Who else will be affected by this solution? eg. Developers, Users of Existing Functionality that may be changed?> <How will stakeholders be affected?> Tip: Engage these stakeholders in the development of your BluePrint.

User Stories

<​http://en.wikipedia.org/wiki/User_story> <A good User Story should answer the following questions:> <* Who the user is> <* What they want the solution to do for them?> <* Why they want it to do that? (goal)> <eg. A <type of user> wants the solution to <do something for them> so that <can achieve a goal>.>

Requirements

<Group requirements in subsections, e.g. _{etc.> <​http://en.wikipedia.org/wiki/Requirements_analysis requirements> <Identify different types of requirements:>}

Functional

• Crisis Mapping for receiving and visualizing incident reports

Non-functional

​http://en.wikipedia.org/wiki/Non-functional_requirements

Interoperability

Standards

System Constraints

Design

<Where relevant include alternative design options>

Data Model

(e.g. EER or class diagrams)

Workflows

<Diagrams or Pseudocode>

Site Map

<for User Interface solutions>

Wireframes

<for User Interface solutions>

Technologies

Current Implementation

<Leave open for a list of existing implementation of this solution in Sahana Eden:> <*a brief description of the implementation (date/time, name, design options chosen)> <*a link to the code> <*list of deployments of the implementation> <*links to case studies> <*short analysis of achievements/problems>

Planned Implementation

<List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on>

Future Extensions

<List of features which could be included, but are outside of the scope of this extension>

Outstanding Questions

<Questions about the features or design that haven't been (and need to be) answered>

References

<Links to external resources>