J3_VaNG_COP_Pre_bid_Briefing_30AUG16_v2.pptx

Virginia National Guard

Common Operating Picture (COP) Plan FY 2016-2020

Pre-Bid Meeting

30AUG2016

Agenda VaNG Common Operating Picture (COP) Concept and Assumptions

VaNG COP Desired End State. Layers, and Examples

Development Timeline and Phases

ARDEC KEYSTONE Middleware

Questions/Comments

VaNG Common Operating Picture (COP) Design Concept Intent is to provide an interactive COP using middleware which translates information to and from interagency partners to attain timely holistic situational awareness for decision makers.

Creates interoperability leveraging existing technology unlike a “solution of one” Similar to the SCNG SCOPe capabilities VaNG COP pulls information from other ESFs through VDEM per interagency MOAs Uses real time data input by interagency partners increasing accuracy and saving time currently lost to recreating data display attained through shared access to partner systems

VaNG Common Operating Picture (COP) Assumptions U.S. Army Armament Research, Development and Engineering Center (ARDEC) can assist VaNG CNGB will decide NGCC COP DEC16 based on NGB-J6 FSA VaNG will be selected as the NGB pilot State in FEMA Region 3 VaNG COP COA meets the needs for a Commonwealth of Virginia COP coordinated by VDEM Another state will allow use of one of their core until a core is established in Virginia or another FEMA Region 3 State.

State or grant funds will be available to contract ESF and other connections through a core and to purchase a core

VaNG COP End State Defined

What the VaNG COP is:

Interactive user defined Common Operating Picture.

Available on any NIPR network.

–Utilizes 4 primary systems: Google Earth, WebEOC, ESRI FLEX Viewer, and DSCA Dashboard tied together via middleware.

–Provides event specific layers that aid in Staff Course of Action (COA) development.

–Provides real time Unit Status info, Mission Assignment tracking, and State SIGACT tracking.

–Accuracy of the system depends on timely updates at the user / unit level.

What the VaNG COP is not:

–Not designed to replace current asset tracking platforms or STAMIS systems. Can provide passive asset visibility and a “snap shot” in time for personnel and equipment availability for DSCA response.

–Not meant to be a singular solution to total situational awareness and must be augmented with other systems to provide the CDR and Staff with information needed to maintain SA during a dynamic DSCA event.

VaNG COP Core installed at G6/DOIM Ft. Pickett, within FEMA Region 3, or in another State

VaNG COP is/becomes the ESF16 portion embedded within the VDEM COP VaNG COP configuration connects disparate programs using middleware (UICDS, KEYSTONE, etc.)

Proposed VaNG COP System Architecture

Categories of VaNG COP Layers

VaNG COP Steady State Layers

VA Critical Infrastructure VaNG Unit Status

VDEM

Potential WebEOC Unit Status Report VaNG Unit

VaNG COP Contingency Layers

Virginia Route Status

VaNG COP Analytical Layers

Lake Windsor Forest Acres Lake Katherine Spring Lake

Example of a Desired VaNG COP Layer

Civil Air Patrol to cover West of I-26 to Georgia

Covering major corridors of travel and High risk dams in there areas.

Looking for swift water, extensive flooding in rural areas and dam breaches in those areas.

8/30/2016

MISSION ASSIGNMENTS

Pre-Bid Meeting with Prospective Vendors

NLT 26SEP16

V2 30AUG16

FY 2021 Joint Interagency COP of the Commonwealth of Virginia

7-11MAY18

VaNG J3 Coordination meeting with ARDEC VaNG and VDEM Site Visit to SCNG JOC VaNG TAG Requests to be the NGB J6 FEMA Region 3 Test Pilot State

6APR16

29-30OCT15

CRITICAL ISSUES:

State Agency / ESF Interface DoD Interface (ATO) Continued funding Core server and alternate VaNG COP Advertised for Bid

30AUG16

NLT 6SEP16

Questions Submitted by Vendors

20JAN17

JAN18

Virginia Governor Inaugural

TBD OCT16

58th Presidential Inaugural

13SEP16

Vendor Proposal Review and Selection by Govt VaNG Common Operating Picture (COP) / Shared Situational Awareness (SSA) Developement Project Start Date Vigilant Guard 2018

27APR16

VaNG J3 COP Contract Review with USPFO

Planned In Progress Completed

- Critical

23MAR16

LEGEND

22SEP15

VaNG VTC with SCNG COP Demonstration

NGB J6 Keystone Demonstration @ NGB NGCC

23AUG16

2AUG16

VaNG J3 Concept Briefing to Dr. Stern, VDEM

PHASE 2

PHASE 3

NGB Functional Solution Analysis of SSA Complete

DEC16

PHASE 4

PHASE 5

PHASE !

FY 2017

FY 2018

FY 2019

FY 2016

FY 2020

ENDSTATE:

1-Efficient use of information sharing solutions 2-Leverage existing systems 3-Enhanced interoperability and information exchange between State and Federal interagency partners

NOV16

Initiate MOA with State Interagency Partners

18AUG16

State Interagency Partner Pre-Bid Planning Meeting

VaNG Common Operating Picture (COP) Phase 1 A. Initial capabilities outlay to include Virtualization of server.

B. Migration of current GEE capabilities/data layers into the new COP/SSA, coding for automation of data pulled from Guard owned system on a set schedule monthly/bi monthly C. SSA/COP should be able to incorporate WebEOC incidents with the ability to filter based on report type and/or event. This must be linked to Virginia Department of Emergency Management.

D. VDOT systems will be a layer with all information systems to include coding that will refresh each camera link that is in view mode on a set time table without requiring human interaction in order to limit downtime.

E. Coding of adaptors required by Keystone to gain SAA.

F. COP/SSA should tie into VDEM Region’s 2, 3, 7 and National Capital Region (NCR) for Presidential Inauguration support.

G. VSP allowed systems will be a layer to refresh shared information that is in view mode on a set VSP time table that requires no human interaction in order to limit downtime.

H. System is complete and usable with the above defined processes.

I. Implement lessons learned.

VaNG Common Operating Picture (COP) Phase 2 A. COP/SSA shall have the ability to build internal/custom reports, which can be shared through the system, or exported into various formats (e.g. .pdf, .doc, .jpg, .tiff, etc.) and emailed with the default email system on the user’s computer.

B. COP/SSA should be able to provide dynamic windows with customized real-time data just by hovering mouse pointer over a symbol, link, or other icon located within the map window.

C. Ability to view and update COP/SSA across a smartphone/mobile app is preferred. This includes the ability for users with proper permissions the ability to upload pictures via the web or mobile interface and the administrator to have smartphone access management to allow him/her to see user requests and approve, deny, send out invitations etc.

D. COP/SSA must be able to integrate internal VANG GIS data from the Maneuver Training Center and the Facilities Management Office.

E. COP/SSA should have some form of built-in chat function. Chat capability should allow for near unlimited public and private chats. All chats must have an export capability. An automatic recording and back up capability of all chats with no user intervention is preferred.

F. Tie fully into VDEM and Capital Police for Governor’s Inauguration.

G. Implement lessons learned.

VaNG Common Operating Picture (COP) Phase 3 A. Major commo transmission lines and transfer stations/substations

B. Major power transmission lines and transfer stations/substations

C. Airport runway capabilities (ICAO airport codes, length, width, capable of C-130 or C-17 landings, etc.)

D. Hospital status (address, phone number, total bed counts, trauma level, available beds, specialties like burn units or decontamination capabilities (Ebola certified)

E. Paid and volunteer fire and EMS stations including addresses and phone numbers (possibly coverage areas)

F. Police/sheriff stations including addresses and phone numbers (possibly coverage areas

G. Large sporting/event venues including addresses and phone numbers (fairgrounds, race tracks, stadiums)

H. Public school buildings including addresses and phone numbers

I. Military installations including addresses and phone numbers

J. Cell tower locations, by provider if available

K. Standard map layers (e.g. road names, city/state names & boundaries, zip code boundaries, place names, etc.)

L. Water treatment plants, waste treatment plants

M. Continue functionality upgrades, coding of adaptors and automation of live streams.

N. COP/SSA should have an operational level customizable dashboard that can be used to track metrics, connections with partners, etc. Current dashboard is made of multiple pods, including a situational awareness map, a file share, multiple chat windows, mission status window, and multiple notepads. Dashboard must allow for collaboration within each pod window without affecting other windows.

O. Tie into MDNG for Vigilant Guard exercise.

P. Implement lessons learned.

VaNG Common Operating Picture (COP) Phase 4 A. Continue functionality upgrades

B. Implement lessons learned from Vigilant Guard exercise.

VaNG Common Operating Picture (COP) Phase 5 A. Sustainment and functionality upgrades as required

B. Implement lessons learned

KEYSTONE

What is Keystone?

A middleware that translates between disparate EM/FP/SA systems Government Off The Shelf (GOTS), license free, DIACAP Accredited system Facilitates information sharing both vertically and horizontally among disparate systems Cost-effective information sharing approach Agnostic to EM/FP/SA systems deployed within DoD and organizations “outside the fence”.

What are the objectives of Keystone?

Enhance information sharing for all hazard/imminent threat situational awareness Cross-sharing of emergency management and force protection domains Enhance mission assurance by passing near real-time information Enhance relationships with Federal, State, and local government entities

OASD - Office of the Assistant Secretary of Defense for Nuclear, Chemical, and Radiological Matters

Uniformed Service personnel and facilities are at risk because neither automated force protection processes or procedures, nor emergency management SA tools exist to share automated all-hazard, near real-time event information among commands, components, and installations. Improving situational awareness (SA) and decision support in current and future Common Operational Pictures (COPs) requires a robust and adaptable middleware that facilitates information sharing for mission assurance (MA), force protection (FP), and emergency management (EM), both vertically and horizontally among disparate SA tools.

Every Geographic COCOM identifies the need for information sharing in various ways. When comparing these requirements, the lack of automated timely and relevant information sharing is a key limiting factor for FP/EM reporting and operations. The problem of untimely and insufficient information sharing was directly identified in the DoD Fort Hood shooting investigation findings and recommendations, as well as in the after action review and report for the Complex Catastrophes’ National Level Exercise 2011.

8/30/2016

KEYSTONE Technical Overview How does Keystone work?

Keystone consists of a “core” and “adapters” Core provides the common/standard language, the routing logic, and the business rules The adapters provide the translation from each disparate system to/from the core What are business rules?

A set of sharing agreements based on the MOU/MOA of connected systems Define what information is shared and to which system Examples: Incident type, Proximity, Severity Rules can be within a single core (intra-core), or with multiple external cores (inter-core) Allows Keystone to expand rapidly to new and existing deployments

OASD - Office of the Assistant Secretary of Defense for Nuclear, Chemical, and Radiological Matters

Uniformed Service personnel and facilities are at risk because neither automated force protection processes or procedures, nor emergency management SA tools exist to share automated all-hazard, near real-time event information among commands, components, and installations. Improving situational awareness (SA) and decision support in current and future Common Operational Pictures (COPs) requires a robust and adaptable middleware that facilitates information sharing for mission assurance (MA), force protection (FP), and emergency management (EM), both vertically and horizontally among disparate SA tools.

Every Geographic COCOM identifies the need for information sharing in various ways. When comparing these requirements, the lack of automated timely and relevant information sharing is a key limiting factor for FP/EM reporting and operations. The problem of untimely and insufficient information sharing was directly identified in the DoD Fort Hood shooting investigation findings and recommendations, as well as in the after action review and report for the Complex Catastrophes’ National Level Exercise 2011.

8/30/2016

VaNG COP Proposed COA

VDEM

VaNG

ESF 1

ESF 2

ESF 4

ESF 3

ESF 6

ESF 5

ESF 13

ESF 7

ESF 11

ESF 12

ESF 8

ESF 14

ESF 15

ESF 16

ESF 17

CORE

ESF 9

ESF 10

JOC

COP

VEOC

COP

COP

COP

VDOT

VSP

COP

COP

COP

COP

COP

COP

SPS

Governor

COP

COP

NGB

DHS

Questions/Comments image1.png image2.png image3.png image4.png image5.png image6.png image7.png image8.png image9.png image10.png image11.png image12.tiff image13.tiff image14.jpg image15.tiff image16.jpg image17.png image18.png image19.png image20.png