= !BluePrint: Sahana First Response =
[[TOC]]


== Current Status == 

[https://docs.google.com/spreadsheets/d/1N9xUqZQhignq7QM_7CtrV4zv86sq4lMdJj81IQuch3Y/edit?usp=sharing Fit-Gap analysis spreadsheet]
==== Available features: ====

==== Missing features: ==== 
1. Common Operating Picture with [wiki:BluePrint/CrisisMap Crisis Mapping] (who, what, when, and where)
1. manage [wiki:BluePrint/Event 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)
1. input and output [http://hxlstandard.org/standard/1_0final/dictionary/#crises HXL #Event], [https://www.oasis-open.org/news/announcements/emergency-data-exchange-language-situation-reporting-edxl-sitrep-v1-0-committee-s SITREP] and [http://docs.oasis-open.org/emergency/edxl-rm/v1.0/errata/EDXL-RM-v1.0-OS-errata-os.html RM] feeds '''[2]''' to serve as an aggregator and a publisher-subscriber
1. Desktop and Mobile applications to integrate and to server as a publisher and a subscriber
1. Approve or Reject asset management, incident reports, situational-reporting, and resource messaging
1. Support multiple language message delivery options: HTTP, RSS/Atom, SMS, Email, FTP
1. digitally sign the messages
1. [https://sahana.io/2014/04/17/symbols-to-fia/ Pictographs for reporting incidents] (field and casualty-illness reports)
1. 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 ===
[[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/Deployments/SAMBRO/broker.JPG, align="left")]] 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 engineering crew 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 Agencies with their Incident Command and Control Systems (ICCSs). The problem that SAIFRE is solving is providing a simple crisis and emergency response management system.

=== Problem ===
Under a well-developed emergency management system, the Emergency Management Services of a Country should be aware of and should map every significant emergency incident and its response. Sharing such information among multiple agencies with disparate systems can be complicated. Solutions such as WebEOC are hard for small developing nations to finance. [http://lirneasia.net/2012/05/masas-iscram-2012/ Silo-ed Organizations and inter-agency rivalry] at various levels of a national emergency management system becomes a difficult challenge to integrate. 
=== Solution ===
SAFIRE is essentially a Sahana Eden template combining various modules to support the work flows of a simple EOC from incident report inception through a cycle until the situation is contained. Important SAFIRE features:
1. Crisis mapping contributes to the common operating picture and categorical representation of the reports with situation visualization and decision management
1. Able to input and output reports in various formats (JSON, XML, PDF, XSL, SQL) and emergency data exchange standards (EDXL, HXL)
1. Use a combination of voice and data input and output streams for collecting and disseminating situational reports and resource messaging
1. Adaptable to handheld and desktop devices for collecting, processing, and sharing information
1. Generic but flexible to customize to any user's liking; i.e. disaster management, police, civil society, private companies, and NGOs
== 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>.>

=== explosion ===
A large hazardous material factory explosion is reported to the Call Center. Police, Fire, and Ambulatory Services are dispatched to the scene. The EOC issues a Chemical Biological Radiological Nuclear (CBRN) SMS/Cell Broadcast alert targeting the population in and around the location to evacuate the area.  EOC coordinates with CBRN Specialists and First-Responders to contain the incident and continues to update the situation-information.

=== landslide ===
A small landslide completely covering the road is reported by a driver to the Call Center. The Call Center dispatches the local Road Maintenance Authority and Community Emergency Response Team Members to the scene. EOC issues an Alert for situational-awareness. Now the Transportation Authority knows to temporarily halt the bus service along that route. Health department know not to dispatch any Ambulance along that road in an emergency, instead use alternate routes.

=== flood rescue ===
A person stranded on the roof with several other people, escaping from a flash flood, calls the Dispatch Services. The EOC deploys a Search & Rescue team with a boat to rescue the people to safety. The EOC dispatches a second team with warm clothing, food, and a vehicle to transport the victims to a temporary shelter.

=== food poisoning ===
A processed food item had been contaminated with a deadly substance. The Health department issues food safety a Public Warning requesting that anyone with the mentioned symptoms should visit the local hospital. The Health department issues a Restricted Alert to all Health Workers and Health Facilities with instructions on the specific procedures for responding to the crisis. Food Safety Authorities issue issue a Public Warning targetting Shop ownerst o remove the product from their shelves. Hotels and Restaurants are aware of the situation and will refrain from serving the product.

=== Tropical Cylcone ===
The First-Responders are dispatched to sweep the area to find any victims as well as assess the damage. The EOC collects the incident reports and begins compiling situation-information reports to plan the required response resource to restore immediate utilities and services. EOC coordinates the critical infrastructure restoration.

=== Train derailment ===
A high speed train derailed in a mountainous area. An observer calls in reporting mass number of casualties and several survivors stuck in unsafe carriages. The EOC dispatches local authorities to the scene to assess the situation and provide immediate assistance. After receiving field-observation reports the EOC dispatches other relevant First-Responders to stabilize the train and to rescue the survivors. 


== Requirements ==
<Group requirements in subsections, e.g.,, etc.>
<http://en.wikipedia.org/wiki/Requirements_analysis requirements>
<Identify different types of requirements:>
=== Functional ===
* [wiki:BluePrint/CrisisMap 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>