Page 1 Energy | Environment | National Security | Health | Critical Infrastructure © 2009 Science Applications International Corporation. All rights reserved.

Slides:



Advertisements
Similar presentations
1 Emergency Response Management Systems (ERMS)versus(ERSM) Emergency Response Systems Management: Identifying the Critical Path to Improved Decision Support.
Advertisements

Homeland Security Information Network-Emergency Management (HSIN-EM) Fire Service Community Overview Technologies for Critical Incident Preparedness Conference.
Federated Digital Rights Management Mairéad Martin The University of Tennessee TERENA General Assembly Meeting Prague, CZ October 24, 2002.
September 30, 2011 OASIS Open Smart Grid Reference Model: Standards Landscape Analysis.
Delivering Mission Agility Through Agile SOA Governance 13 th SOA e-Government Conference 4/12/2012 Presented by Wolf Tombe Chief Technology Officer (CTO)
EInfrastructures (Internet and Grids) US Resource Centers Perspective: implementation and execution challenges Alan Blatecky Executive Director SDSC.
1 NGA Regional Bio-Terrorism Conference Boston, Massachusetts January 12-13, 2004.
IS 700.a NIMS An Introduction. The NIMS Mandate HSPD-5 requires all Federal departments and agencies to: Adopt and use NIMS in incident management programs.
1 Executive Office of Public Safety. 2 National Incident Management System.
DHS, National Cyber Security Division Overview
National Space-Based Positioning, Navigation, and Timing (PNT) Federal Advisory Board DHS Challenges & Opportunities Captain Curtis Dubay, P.E. Department.
Session 121 National Incident Management Systems Session 12 Slide Deck.
Considering an Enterprise Architecture for the NSDI
Understanding Multiagency Coordination IS-701.A – February 2010 Visual 2.1 Unit 2: Understanding Multiagency Coordination.
The National Incident Management System. Homeland Security Presidential Directive 5 To prevent, prepare for, respond to, and recover from terrorist attacks,
A Robust Health Data Infrastructure P. Jon White, MD Director, Health IT Agency for Healthcare Research and Quality
The National Incident Management System
Development Principles PHIN advances the use of standard vocabularies by working with Standards Development Organizations to ensure that public health.
Resiliency Rules: 7 Steps for Critical Infrastructure Protection.
National Incident Management System. Homeland Security Presidential Directive – 5 Directed the development of the National Incident Management System.
National Response Framework
Information Sharing Puzzle: Next Steps Chris Rogers California Department of Justice April 28, 2005.
US NITRD LSN-MAGIC Coordinating Team – Organization and Goals Richard Carlson NGNS Program Manager, Research Division, Office of Advanced Scientific Computing.
Strengthening the Strategic Cooperation between the EU and Western Balkan Region in the field of ICT Research Regional ICT R&D priorities, Jelena Pantelic,
EbXML Overview Dick Raman CEO - TIE Holding NV Chairman CEN/ISSS eBES Vice Chair EEMA and HoD in UN/CEFACT Former ebXML Steering Group.
GEO Work Plan Symposium 2012 ID-05 Resource Mobilization for Capacity Building (individual, institutional & infrastructure)
1 © 2003 Cisco Systems, Inc. All rights reserved. CIAG-HLS Security For Infrastructure Protection: Public-Private Partnerships KEN WATSON 15 OCT.
Disaster Management eGov Initiative (DM) Program Overview December 2004.
Division of Emergency Management & Homeland Security Department of Emergency Services & Public Protection June 25, 2013 Connecticut All-Hazards Response.
Copyright © 2004 by The Web Services Interoperability Organization (WS-I). All Rights Reserved 1 Interoperability: Ensuring the Success of Web Services.
NIEM Domain Awareness June 2011 Establishing a Domain within NIEM.
Critical Infrastructure Protection: Program Overview
Information Sharing Challenges, Trends and Opportunities
Disaster Management e-Gov Initiative Program A Deceptively Simple Approach to an Emergency Data Exchange Language Distribution Element (EDXL-DE) Based.
SEARCH Membership Group Systems & Technology PAC Global Justice XML Data Model (GJXDM) Update January 29, 2005.
Communications Government Services, Incorporated Software Defined Radio for Public Safety Presentation to the National Conference on Emergency Communication.
1 Emergency Management Standards EM- XML Consortium & EM Technical Committee Presentation to Steve Cooper March 18,2003.
The State of the Information Sharing Union The State of the Information Sharing Union Paul Wormeli Executive Director IJIS Institute
S/L/T Version 1 National Response Framework Overview for Local, Tribal and State Audiences January 22, 2008.
PS Version 1 National Response Framework Overview for Private Sector Audiences January 22, 2008.
11/10/ :04 AM National Information Exchange Model James Feagans & Michael Daconta NIEM Project Manager GLOBAL ADVISORY COMMITTEE BRIEFING October.
Session 81 National Incident Management Systems Session 8 Slide Deck.
Enabling pK12 Data Identification, Movement and Usage Larry Fruth, Ph.D. Executive Director Schools Interoperability Framework Association April 23, 2007.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
National Information Exchange Model (NIEM) Executive Introduction November 29, 2006 Thomas O’Reilly NIEM Program Management Office.
Dr. Shane Renwick, DVM, MSc, A/Director, Animal Health Science Division, Canadian Food Inspection Agency CAHLN, UCVM June 8, 2010 Foresight for Canadian.
Timothy Putprush Baltimore, MD September 30, 2009 Federal Emergency Management Agency (FEMA) Integrated Public Alert and Warning System Presentation to.
SEARCH SEARCH, The National Consortium for Justice Information and Statistics
C4ISR for the Military: Development and Implementation Presentation to the Security Network’s C4ISR, Robot Platforms, and Sensor Conference Greg Collins,
1 Dr. David Boyd Director Office for Interoperability and Compatibility Command, Control and Interoperability Division Science and Technology Directorate.
Secure Communications—No Compromise Real Time Communications in Emergency Response Planning and Operations Tim Vittetoe VIACK Corporation.
National Incident Management System (NIMS)
NATIONAL INCIDENT MANAGEMENT SYSTEM (NIMS)
Session 161 National Incident Management Systems Session 16 Slide Deck.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
1 Presented by Jim Nixon, Breakout Session Moderator December 15, 2005 Report from Breakout Session #2 Individuals/Organizations to Government.
Technology Services – National Institute of Standards and Technology Implementing the National Technology Transfer and Advancement Act in the Federal Government.
SEARCH, The National Consortium for Justice Information and Statistics Melissa Nee Government Affairs Specialist SEARCH Overview Briefing.
2015 USACE Exercise – December 1, 2015 New Madrid Seismic Zone – Earthquake FEMA Mission, Legal Authorities and Regional Capability Overview Gus Wulfkuhle.
NATIONAL INCIDENT MANAGEMENT SYSTEM Department of Homeland Security Executive Office of Public Safety.
NIMS AND THE NRF – MADE SIMPLE. 2  NIMS is a comprehensive, national approach to incident management  NIMS provides the template for incident management,
National Emergency Communications Plan Update National Association of Regulatory Utility Commissioners Winter Committee Meeting February 16, 2015 Ron Hewitt.
James D. Goltz Branch Chief, Earthquake, Tsunami and Volcanic Hazards Program California Emergency Management Agency and Anne Rosinski Senior Engineering.
Open GIS Consortium Charles Heazel March 19, 2003.
Integrated Public Alert and Warning System
TeleManagement Forum The voice of the OSS/BSS industry.
Emergency Management: Incident, Resource, and Supply Chain Management
The National Incident Management System
Emergency Management: Incident, Resource, and Supply Chain Management
Presentation transcript:

Page 1 Energy | Environment | National Security | Health | Critical Infrastructure © 2009 Science Applications International Corporation. All rights reserved. SAIC and the SAIC logo are registered trademarks of Science Applications International Corporation in the U.S. and/or other countries. Introduction UICDS is the “middleware foundation” that enables National Response Framework (NRF) and National Information Management System (NIMS), including Incident Command Structure (ICS), information sharing and decision support among commercial and government incident management technologies used across the country to prevent, protect, respond, and recover from natural, technological, and terrorist events The UICDS Architecture Specification that describes standards and data model for technology providers to adapt their products and share information A pilot reference implementation that is a real-world, operational test environment and development kit for technology providers to use to adapt their products A national outreach program to expand awareness of the role of technology in homeland security Chip Mahoney, P. E. Project Manager, Unified Incident Command and Decision Support (UICDS) Science Applications International Corporation (SAIC) UICDS Sponsor: Larry Skelly Department of Homeland Security Science & Technology Directorate, Infrastructure & Geophysical Division

Page 2 Energy | Environment | National Security | Health | Critical Infrastructure © 2009 Science Applications International Corporation. All rights reserved. SAIC and the SAIC logo are registered trademarks of Science Applications International Corporation in the U.S. and/or other countries. What Is the Process That You and/or Your Company Use to Ensure That Your Product Meets the Needs of the End-user? Derived from from nationally recognized policy-level documents –National Information Management System (NIMS) –National Response Framework (NRF) Open, non-proprietary, standards-based design and interfaces Identification of end-user needs and technology provider capabilities via a national outreach program –End user subject matter experts (internal and external) –Government (early focus on federal, transition to states and locals) –Technology providers (commercial off-the-shelf, government off-the-shelf, universities) Evolutionary development with continual feedback into the system design and implementation –Software engineering process that results in: Architecture -> demonstration -> pilot -> deployment –Early demonstration of system feasibility –Multiple opportunities for the end-user assessment –Multiple builds build on previous operational concept

Page 3 Energy | Environment | National Security | Health | Critical Infrastructure © 2009 Science Applications International Corporation. All rights reserved. SAIC and the SAIC logo are registered trademarks of Science Applications International Corporation in the U.S. and/or other countries. What Are Some of the Challenges Associated With This Process? Technical challenges –Large number of integrations (jurisdictions, sites, applications) –No single solution for information sharing – multiple networks and interfaces –Peer-to-peer coordination versus centralized command and control –Evolving technologies and standards and applications Operational challenges –Information-sharing desires vary –Local capabilities, needs and constraints vary –Local investments in technology vary Programmatic challenges –Local acceptance of a federally funded capability –Competing end-user feedback

Page 4 Energy | Environment | National Security | Health | Critical Infrastructure © 2009 Science Applications International Corporation. All rights reserved. SAIC and the SAIC logo are registered trademarks of Science Applications International Corporation in the U.S. and/or other countries. And Does This Process Vary Depending on Whether the Customer/Client Is a Government Agency Versus a Commercial Company? UICDS outreach focuses on both government organizations and technology providers –UICDS Technology Providers (commercial off-the-shelf and government off-the-shelf vendors, universities) via regular communications Biweekly telecons (20 – 40 participants) with specific technical topics and coordination of upcoming events and opportunities Regular s (approximately 900 on the mailing list, approximately 240 active, approximately 90 DevKit users, 30 demo participants) –Government organizations (federal, state, tribal, local, non-government organizations) via meetings, briefings, demos and UICDS pilot participation Federal (including Departments of Homeland Security, Justice, and Defense,and FEMA and Health and Human Services) State/local (including UICDS pilot in Virginia, All Hazards Consortium) NGOs (including power companies, universities, aid matrix) –Conferences and workshops provide a confluence of government and UICDS Technology Providers Recent examples include UCore Users Group, NIEM/OASIS Conference, International Association of Emergency Managers (IAEM) Conference, Public Safety Innovation Center (PSIC), EMWS09 – provides an interactive platform for UICDS collaboration Introductory materials Document library Demos Discussions Acronyms are defined on page 8.

Page 5 Energy | Environment | National Security | Health | Critical Infrastructure © 2009 Science Applications International Corporation. All rights reserved. SAIC and the SAIC logo are registered trademarks of Science Applications International Corporation in the U.S. and/or other countries. How Do You Validate or Assess the Efficacy of Your Technology? UICDS efficacy is validated by: –Improvements in end-user information sharing and decision support capabilities in a standard fashion (one-to-many integration) Within a jurisdiction/organization Across jurisdictions/organizations –Number of participating technology providers and jurisdictions/organizations and how they interact –Specific quantitative metrics that describe interactions and help validate scalability Incident frequency and duration Information sharing numbers, update frequency, file size

Page 6 Energy | Environment | National Security | Health | Critical Infrastructure © 2009 Science Applications International Corporation. All rights reserved. SAIC and the SAIC logo are registered trademarks of Science Applications International Corporation in the U.S. and/or other countries. Are There Industry Standards That Help Define How Well a Technology Must Perform in Order to Be Effective? If There Are No Standards, Should There Be? Industry standards help facilitate interoperability. Examples include: –Policy level: NIMS/NRF –Information exchanges: NIEM, UCore –Domain-specific standards bodies: OASIS, OGC, LEITSC, IEEE, APCO, ASTM Complexity of systems leads to the use of multiple standards –Overlap and gaps How standards are implemented is a challenge –Buy/build: When to use existing standards and when to create a new standard? –System compliance to a standard - complete versus partial – what is enough? –Flexibility for ease of implementation versus “creative differences” –System-specific overhead information UICDS integrates across multiple standards (and across domains) Acronyms are defined on page 8.

Page 7 Energy | Environment | National Security | Health | Critical Infrastructure © 2009 Science Applications International Corporation. All rights reserved. SAIC and the SAIC logo are registered trademarks of Science Applications International Corporation in the U.S. and/or other countries. Visit Us at UICDS Project Community Outreach Director James W. Morentz, Ph.D. (703) DHS S&T Program Manager: Lawrence E. Skelly DHS S&T Program Support: Tomi` Finkle UICDS Project Project Manager Chip Mahoney (917) DHS S&T Technical Lead: Nabil R. Adam, Ph.D.

Page 8 Energy | Environment | National Security | Health | Critical Infrastructure © 2009 Science Applications International Corporation. All rights reserved. SAIC and the SAIC logo are registered trademarks of Science Applications International Corporation in the U.S. and/or other countries. Acronyms APCO = Association of Public Safety Communications Officials ASTM = American Society of Testing and Materials CAP = Common Alerting Protocol COTS = Commercial Off The Shelf DHS = Department of Homeland Security DOJ = Department of Justice EDXL = Emergency Data Exchange Language EDXL-DE = EDXL Distribution Element EDXL-RM = EDXL Resource Messaging EMWS09 = Workshop on Emergency Management: Incident, Resource, and Supply Chain Management FEMA = Federal Emergency Management Agency GOTS = Government Off The Shelf GeoRSS = an emerging Web feed standard for encoding location HHS = Health and Human Services ICS = Incident Command System/Structure IEEE = Institute of Electrical and Electronics Engineers LEITSC = Law Enforcement Information Technology Standards Council MACS = Multi-Agency Coordination System NIEM = National Information Exchange Model NIMS = National Information Management System NGO = Non-Government Organization NRF = National Response Framework OASIS = Organization for the Advancement or Structured Information Standards OGC = Open Geospatial Consortium PSIC = Public Safety Innovation Center SAFECOM = a DHS communications program SIOC = Strategic information and operations center SME = Subject Matter Expert SOAP = Simple Object Access Protocol ST = Science and Technology UICDS = Unified Incident Command and Decision Support UCore = Universal ULEX = Universal Lexical Exchange VA = Virginia