Second SDO Emergency Services Coordination Workshop April 12-14, 2007

Primary Requirements Activities Common Requirements/Common Solutions: conferences Telematics: January conference Integrated Patient Tracking Initiative Core Services Agency location Rights management

New Emergency Response Data Market: Use Cases All are citizens to a variety of agencies, including 9-1-1 Telematics: consumer and trucking. Trains Medical devices: personal heart monitor; diabetes phone Sensors: building monitors, air and water monitors Weather systems (e.g. Weatherbug) Critical Infrastructure; Volunteers

Emergency Response Issues No clear line between emergency agencies and the public Millions of employees of agencies 220 million+ citizens are part of emergency response virtual enterprise Responders carry commercial phones Very high percentage of responders are volunteers

Clear Requirement from Agencies: Spread Information Old days: stove piped contact; call only One “right” agency: 9-1-1 for public calls LOST is example Multiple agencies for Citizen to Authority; not a single, right destination Subscriber control, subject to override

Primary Technical Activities Messaging: DM SWG, EIC, OASIS EM TC OASIS EDXL Distribution Element, CAP, HAVE, Resource Messaging Building core service instantiations EPAD Identity Rights Management Demonstration of integrated patient/victim information Systems

Key Initiatives (1) With NCOIC: Net-Enabled Emergency Response (NEER) With Red Cross, NENA and others: Informed Interoperable Emergency Response Messaging Radio over Internet Protocol Core Services

Key Initiatives (2) With HIMSS and others: Patient Tracking Phase II With telematics, NENA, others: VEDS 2.0, Extrication Portal

MECI Information Framework Core Services Agency Locator (EPAD) Identity Management Digital Rights Management Intelligent Message Brokers Shared Services Radio IP Bridges IP Backbone Networks IP-based Standards e.g. EDXL, CAP, NIEM, SIP Network Discovery Layer EMT(s) Access Point I/O Backbone Fire Departments Access Point I/O Backbone Red Cross & NGO(s) Access Point I/O Backbone Data Bases Layer of Interoperability Communications Layer

NEER Focus: What Needs to Happen Core services Policies that populate them NEER will: Validate requirements and proposals Review technology Suggest best practices for them

Shared and Core Services Definition Business case Many or all domains Core Types Identity rights mgmt/access control Agency locator Data rights mgmt Other security Design Rights: COTS Policies & Protocols Transport Standards Enterprise Services Agency Applications

Core Services What are they? Why do we need them? Shared utilities provisioned collectively by the emergency services community Compelling business case for all to share Allows stakeholders to leverage common functions Why do we need them? Enables information sharing and discovery across multiple domains Extends reach to NGOs, private sector, media companies quickly and easily

Concept of Enterprise Services EMS Run Report Agency Applications 9-1-1 CAD EOC, CIMS Traffic NLETS, NCIC EPA’s EIEN LOB Services PHIN RHIOs Shared Services Message Broker Information Discovery Radio over IP GIS Core Services Agency Locator Identity Mgmt Digital Rights Other Security

Policies & Protocols Near term needs Radio interoperability Warning; messaging Intelligence sharing Medium term needs NRP, NIMS, ICS, TCL Moving from single use to multi-use Decision bodies exist; flexible tools do not Policies & Protocols Transport Data Standards Core Services Agency Applications

Core Services: Agency Locator Registration Who am I? What am I ?(Identity) Organization type; role What incidents do I want to hear about? Jurisdiction, help, just interest For what geographic areas and what times for each? Where do I want calls and data sent? What are my radio frequencies, gateway, codecs?

Core Services – Identity Management and Access Control Who is the entity? - Organization identity How is organization represented? (Identifiers) Username, Log-in (Password, PINs, Smartcards, Biometrics, etc.) How can org. prove who it is? (Authentication) Validation of identifiers What can it do when it has proved who it is? (Authorization) What functions can be performed What data can be accessed Role-based – tied to identifiers – user and organization How can we know it’s working? (Auditing) Auditing and reporting

ARC, COMCARE, NENA et al Non-profit consortium Select technology partners Deploy alphas of two core services Trials and production Standardized web services for querying core services