Changes between Version 4 and Version 5 of BluePrint/SAFIRE
- Timestamp:
- 03/27/16 12:41:17 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/SAFIRE
v4 v5 9 9 10 10 ==== Missing features: ==== 11 1. built on the Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) version 1.2 '''[1]''' 12 1. manage templates, manage messages [[BR]] 13 1. manage CAP Profiles (multiple languages, identifier format, etc) in ../cap/000_config file 14 1. receive CAP feeds '''[2]''' to serve as an aggregator and a pubhub 15 1. approve or reject a CAP message prior to dissemination 11 1. Common Operating Picture with a Crisis Map 12 1. manage event type specific templates and messages 13 1. receive SITREP and RM feeds '''[2]''' to serve as an aggregator and a pubhub 14 1. approve or reject dispatch, incident reports, situational-reports, request-resources 16 15 1. delivery options: HTTP, RSS/Atom, SMS, Email, FTP (dynamic labels) 17 1. visualize CAP feeds on a map ("common operating picture") 18 1. Use GIS-based risk assessment techniques to develop predefined (hazard, event, and severity specific) CAP alert area templates\1. delivery options: HTTP, RSS/Atom, SMS, Email, Voice-text (audio) 16 1. built on the Emergency Data Exchange Language (EDXL) SITREP and RM standards 19 17 1. subscription management (who, what, when, and where) serve as a subhub 20 1. Feed in to Google Alerthub '''[3]''' and [http://preparecenter.org/activities/universal-app-program IFRC Universal Hazard App]21 1. support multiple language CAPmessage publication18 1. Exchange data with other EDXL compliant systems 19 1. support multiple language SITREP/RM message publication 22 20 1. digitally sign the messages 23 21 1. Mobile application to server as a publisher and a subscriber 24 1. Pictographs for Alerting25 1. Event specific SOP check list22 1. Pictographs for reporting incidents and situational=reports 23 1. Incident specific SOP check list 26 24 27 25 == Introduction ==