| 4 | | |
| 5 | | == Current Status == |
| 6 | | |
| 7 | | [# Fit-Gap analysis spreadsheet] |
| 8 | | ==== Available features: ==== |
| 9 | | 1. Manage and allocate skilled resources (SAR, Engineering, Defense), assets (radios, vehicles, equipment), and track their current location |
| 10 | | 1. Common Operating Picture with [wiki:BluePrint/CrisisMap Crisis Mapping] (who needs and doing what, when, and where) |
| 11 | | 1. Approve or Reject asset management, incident reports, situational-reporting, and resource messaging |
| 12 | | 1. Desktop and Mobile applications to integrate and to server as a publisher and a subscriber |
| 13 | | 1. Support multiple language message delivery options: REST API, EDXL, RSS/Atom, SMS, Email, FTP |
| 14 | | 1. Incident specific SOP check list |
| 15 | | ==== Missing features: ==== |
| 16 | | 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) |
| 17 | | 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 |
| 18 | | 1. digitally sign the messages |
| 19 | | 1. [https://sahana.io/2014/04/17/symbols-to-fia/ Pictographs for reporting incidents] (field and casualty-illness reports) |
| | 135 | |
| | 136 | == Current Status == |
| | 137 | |
| | 138 | [# Fit-Gap analysis spreadsheet] |
| | 139 | ==== Available features: ==== |
| | 140 | 1. Manage and allocate skilled resources (SAR, Engineering, Defense), assets (radios, vehicles, equipment), and track their current location |
| | 141 | 1. Common Operating Picture with [wiki:BluePrint/CrisisMap Crisis Mapping] (who needs and doing what, when, and where) |
| | 142 | 1. Approve or Reject asset management, incident reports, situational-reporting, and resource messaging |
| | 143 | 1. Desktop and Mobile applications to integrate and to server as a publisher and a subscriber |
| | 144 | 1. Support multiple language message delivery options: REST API, EDXL, RSS/Atom, SMS, Email, FTP |
| | 145 | 1. Incident specific SOP check list |
| | 146 | ==== Missing features: ==== |
| | 147 | 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) |
| | 148 | 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 |
| | 149 | 1. digitally sign the messages |
| | 150 | 1. [https://sahana.io/2014/04/17/symbols-to-fia/ Pictographs for reporting incidents] (field and casualty-illness reports) |
