Project Homeland

1
Project Homeland

• Activities and Lessons Learned
• BARGC Pilot

Steve Grisé Project Homeland Data Architect ESRI
2
BAR-HSDS Project Goals
Implement Operational Data Sharing Systems to
Support Regional Emergency Management Needs

• Network of servers with replication for data
  sharing
• Secure login access for first responders
• Data Management
• Access to the models (CATS, HAZUS) on the server
  or data download
• Update Base data for the models
• Web display of the results
• Regional exercise
• Documentation with lessons learned
• Long term maintenance and implementation plan

3
Common Operating Picture
4
Project Participants
5
BAR-GC Participants

• USGS
• NGA
• USACE
• Bay Area Regional GIS Council (BAR-GC)
• BAR-GC membership includes
• Association of Bay Area Governments
• Bay Area Automated Mapping Association
• City of Oakland
• City/County of San Francisco
• City of San Jose
• County of Alameda
• County of Contra Costa
• CA Office of Emergency Services, Coastal Region
• CA Regional Water Quality Control Bd, SF Bay
• City of Berkeley
• City of Concord
• City of Santa Rosa
• County of Marin
• County of Napa

• ESRI - Prime Contractor
• VESTRA Resources (HW/SW Install, Data Loading)
• Art Botterell (System security)
• Scott Parsons (MOU Facilitation)

6
Local to HS Data Model

• Local diverse data models to HS Best Practice
  data model
• Managed by Regional/State Hubs
• BAR-GC Data mapping example shown below

7
BARGC Data Model
HLS/HLD View
BARGC View
HLS Operations from FGDC HSWG Symbology Standard
HLS Critical Infrastructure from HSIP MEDS and
Federal Lists
Detailed Local Content From Local Government
Best Practices
Quick Demonstration
State/Local
Federal
8
(No Transcript)
9
Colorado Concept
Homeland GIS Systems (States/Locals/etc.)
HLS Operations
Emergency Management/Homeland Systems

• Emergency Management Systems
• National Incident Management System
• Intel Data Sharing and Fusion

HLS Critical Infrastructure
National GIS
National Data Content
Detailed Local Content
Buildings
Transport
Utilities
Admin Areas
Basemap
Environ- mental
10
National Data Flows
National Compilation
State/Regional Systems
Internet
Open
Users National Communities HLS/HLD Community
DHS, DoD, NGA, Law Enforcement, States, Locals
Secure Networks
Access Controlled
Local Data
11
Colorado Data Flows
HLS/HLD Community
Colorado State System
National GIS
COP
1 National Layers
National Layers
National Layers
EOC
Mirror
1 National CIP
Mirror
ETL
ETL
50-100 Partners
Foundation
Foundation
Mirror
Mirror
ETL
12
Systems Architecture Implications
13
Data Summary

• Need more analysis of information product
  requirements to improve design (i.e. DHS
  Universal Task List)
• Ongoing role for Best Practices (bottom up and
  top down)
• Recommendation for a series of implementation
  projects to start building infrastructure,
  establishing workflows, and advancing design
  specifications

14
ETL Activities
Our original concept
15
BAR-GC Pilot ProjectHigh-Level ETL Production
Workflow

• Data Acquisition
• Data Inventory Assessment
• Data Preparation
• ETL Processing
• Geodatabase Delivery (SQL Server)

16
BAR-GC project metrics

• Approx 2.2 Million features mapped and loaded to
  the BARGC-HSDS
• Could load 25,000 features a minute
• Advanced tools improved loading times and
  minimized geometry errors

17
ETL Environment
Quick Demonstration
18
Data Interoperability Tools
19
ETL Summary

• Basic ETL processes can be improved
• Implementation cost is largely due to lack of
  standards at a local level (ETL mapping effort)
• Missing data, missing attributes, lack of
  standards drives cost and results
• Bulk update procedures (for now)
• Basic data security model needs work
• Unique Identifiers for features essential (local
  level)
• Other design patterns also important

20
Pilot System Components
21
Security Levels

• User
• Viewer Access
• Data Provider
• Data Integrators
• Administrator
• Web Server
• Web Services
• AES 128 bit encryption for files (FIPS std for
  SBU data)
• Data
• Features
• Layers
• Organizational
• Procedural

22
Data Security

• Data Model security not implemented by Viewer yet
• Data Issues (even images) stored on multiple
  client devices
• Compilation of regional data increases
• Usefulness
• Uniqueness
• of information and leads to higher security
  concerns as described in the Rand Report, Mapping
  the Risks

23
BARGC Data Security Matrix
24
Systems Summary

• Security was more complex than anticipated
• https password protection certificates
  appears to work well
• ftp encrypted files over https
• Rights tables distributed via VPN tunneling
• Good start towards a repeatable process for
  solution implementation
• Rights management needs more work
• Documentation in progress

25
Project Template

• Some materials available now
• Project Tasks/plan
• Example MOUs and data sensitivity approach
• Data Model
• ETL mapping files and process
• Viewer software/capabilities
• EOC integration approach/experience
• Documentation coming soon

26
California Activities

• BARGC now a legal entity under ABAG
• Current ODP grant request to fund integrated
  geospatial operations
• State
• Regional (ie BARGC)
• Local levels (ie Tri-Valley Fire Depts)
• CA moving towards State Regions model
• Momentum started at the local level and led to
  State participation

27
Whats Next?

• Work with CO State and USGS on Colorado pilot
  just starting
• Significant USGS role
• Project Homeland moving toward HLS/HLD Community
  support
• USGS taking lead on further data pilots
• Opportunity for States to collaborate with USGS
  to move this national effort forward

28
(No Transcript)