Changes between Version 45 and Version 46 of BluePrint/SAFIRE

Timestamp:

03/30/16 02:26:34 (9 years ago)

Author:

Nuwan Waidyanatha

Comment:

--

BluePrint/SAFIRE

@@ -70 +70 @@
 <Identify different types of requirements:>
 === Functional ===
+
+Features in these kind of terms - NOTE WE HAVE ALL of these features already - they 'just' need bringing together into a coherent template which has been tested and documented.
+
 * [wiki:BluePrint/CrisisMap Crisis Mapping] for receiving and visualizing incident reports
-
-I would phrase the features in these kind of terms (note we have *all*
-of these features already - they 'just' need bringing together into a
-coherent template which has been tested and documented)
-
-* Staff/Volunteer Management
-- Credentials can be tracked (Skills, Training & Experience) to remind
-people when they need to attend refresher trainings and see where
-there are gaps in cover that need addressing
-
-* Asset Management
-- Assets can be tracked through purchase, deployment, loans and repairs.
-
-* Fleet Management
-- Vehicles can have their fuel usage monitored and use GPS Tracking to
-report their current positions
-
-* Incident Reporting
-- Incidents can be logged by call centre staff or can be reported from
-the field by both trusted agents & the general public (including
-through Twitter/SMS/Email)
-
-* Dispatch
-- Teams of people & their equipment (vehicles/radios/etc) can be
-assigned to an incident according to their Skills & Availability
-(Rostering)
-
+* Staff/Volunteer Management - Credentials of personnel can be tracked (Skills, Training & Experience) to:
+     * remind people when they need to attend refresher training and see where there are gaps in cover that need addressing
+     * categorization allows for automatic matching to a resource requirementt
+* Asset Management - Assets can be tracked through purchase, deployment, loans and repairs.
+* Fleet Management - Vehicles can have their:
+    * fuel usage monitored and 
+    * use GPS Tracking to report their current positions
+* Incident Reporting - Incidents can be:
+     * logged by call centre staff
+     * reported from the field by both trusted agents
+     * reported by the general public (including through Twitter/SMS/Email)
+* Dispatch - Teams of people & their equipment (vehicles/radios/etc) can be assigned to an incident according to their Skills & Availability
+(Roster)
 * Incident Management
-- SOP checklists can be worked through based on scenario templates
-- The Incident Manager can file status updates & request additional
-resources to be dispatched
-
+     * SOP checklists can be worked through based on scenario templates
+     * The Incident Manager can file status updates & request additional resources to be dispatched
+     * Crisis map is updated with eachh response action to provide a near real-time common operating picture
 * Share Information amongst heterogeneous systems
-- FYI &/or Action requests can be shared with all authorised
-stakeholders, whether or not they use Sahana (as long as they support
-open standards such as EDXL or we develop a custom adapter)
+     * Action requests can be shared with all authorized
+     * stakeholders, whether or not they use Sahana (as long as they support open standards such as EDXL)
+     * or we would develop a custom adapter
 
 === Non-functional ===