210 likes | 293 Views
NCOIC Technology Day. Restoring Communications Infrastructure after a Complex Humanitarian Disaster . Nelson Santini (DataPath) and Mobile Emergency Communications Interoperability (MECI) Team January 22, 2007. Approved for Public Release Jan 07-103.
E N D
NCOIC Technology Day Restoring Communications Infrastructureafter a Complex Humanitarian Disaster Nelson Santini (DataPath) and Mobile Emergency Communications Interoperability (MECI) Team January 22, 2007 Approved for Public Release Jan 07-103
Restoring communications infrastructure within the first 72 hours after a Complex Humanitarian Disaster (CHD) is vital to health and safety of the population. Implementation of NCO principles for Mobile Emergency Communication Interoperability (MECI) can solve this problem. Problem Statement
Complex Humanitarian Disaster (CHD) Challenges • Impact of CHDs on the global population is ever increasing • Responders have limited exposure to critical communication technology • Agencies use disparate technology, policies and databases. • Infrastructure is fragmented and unique to a region and its agencies
CHD Landmark Events • December 26, 2004 Indian Ocean Earthquake and Banda Aceh Tsunami • August 23, 2005 Gulf of Mexico Hurricane Katrina • October 8, 2005 Kashmir Earthquake
Global Impact Banda Aceh Tsunami • Damage $ Undetermined USD • Fatalities 230,000+ total • Affected Areas Eastern Africa, Southern Asia, Indian Ocean Hurricane Katrina • Damage $84 B USD • Fatalities 1,836 total • Affected Areas Bahamas, Cuba, United States Kashmir Earthquake • Damage $ Undetermined USD • Fatalities 74,500+ total (100,000+ Injured) • Affected Areas Pakistan, India, Afghanistan
Common Challenges • Outdated communications systems • Disparate systems and protocols • Poor network logistics and support • Civil and military resource coordination • Unrehearsed responses • Inaccessible public and private data sources • Cultural differences
Current Needs • Emergency response operational plan and analysis • Inter-organizational information sharing and assurance (IA) of data communications • Pre-existing collaboration core services based on SOAs • Pre-existing communication services beyond hand-held radios • Standard protocol network - EoIP
Critical MECI Gaps • No pre-defined Mobile Emergency Communications framework • Few data standards, much less semantic interoperability • Few interfaces to the standards that exist • Few shared, and no core services • identity management, agency locator, data rights management • Civilian/Civilian/Military collaboration (CIMIC) • Policies: from transport to apps to operations
NCOIC’s Goals Enable responders around the world to: • Leverage communication networks effectively and manage any security threat • Restore communication assets and capabilities needed to manage a CHD; any time and anywhere • MECI IPT Report “Findings and Recommendations for Mobile Emergency Communications Interoperability (MECI)”
MECI IPT: Enabling Interoperability LMR &SATCOM Customer Requirements SCOPE NIF Building Blocks NCAT Prepackaged Mobile Emergency Interoperable Comms Infrastructure Components 911, E911 MSS/PSAP WiMax WiFi Hastily- Formed Networks Incident Command System DMIS CAP Connectionless & Connection- Oriented Transport 2.0G & 2.5G Cellular Software Defined Radios MANET/ DSR Protocol NCOIC is specifyingBuilding Codes (PFCs with standards, patterns and methods)for the arrows so NCO stakeholders can build interoperable solutions
Agency Locator(EPAD) Identity Management Digital Rights Management Core Services Disaster Management Info Service Radio IP Bridges Geographic InformationServices Access Point Shared Services EMT(s) I/O Backbone I/O Backbone I/O Backbone Access Point Red Cross & NGO(s) Access Point Communication Layer Fire Departments Standards e.g. EDXL, CAP, NIEM Network Discovery Layer Data Base Services Information Framework
Transport Network discovery Agency applications Shared services Data standards Core services Policies in systems Services Information Framework • Yes • Yes • Yes, few interfaces • Few • Few • Partial prototype • Sparse
The Way Forward Technology itself isn’t a solution to CHD management Success requires a: • Defined architectural framework • Comprehensive response strategy • Methodology to coordinate a dynamic response Hastily Formed Networks (HFNs)
The Way Forward- Technology - • Open standard pre-defined architectural framework • EoIP • Information based and web-enabled service environment • SOA • Autonomously configurable networks and linkage to existing networks • Network Centric Operations Standards
The way forward- Policy - • Coordinated leadership • Improved operational planning • All hazards, all organizations • Assume de-centralized ownership of legacy assets • Assume centralized ownership of HFNs assets • Pre-defined (ideally based on day to day): • Organizational coordination: core services enabling policy implementation • Role-based rights management: identity, data, security, SLAs • Drills, training, accountability
NCOIC Discussion