National Capital Region (NCR) Closed Circuit Television (CCTV) Integration Framework Project Phase I Final Report Summary and Phase II Update June, 2011.

Slides:



Advertisements
Similar presentations
Supporting New Business Imperatives Creating a Framework for Interoperable Media Services (FIMS)
Advertisements

Overview What is the National ITS Architecture? User Services
Douglas Bass, Director Office of Emergency Management Fairfax County, VA.
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Maryland State Highway Administration Maryland Transportation Operations Summit 2008 This Session is about Focus on how agencies are effectively using.
XProtect® Expert 2013 Product presentation
Agency Administrators August 17, 2004 Wethersfield Police Department CAPTAIN A Service Management Update Capitol Region Council of Governments.
TPB Human Service Transportation Coordination Program 1 Key Elements of the Update to the Coordinated Human Service Transportation Plan Human Service Transportation.
Nevada Communication Interoperability Plan Overview Developed by Nevada Communications Steering Committee Version 2.0 – Adopted April 6, 2006.
MetroCIO GIS Committee Meeting Tuesday, November 20, – 3 PM.
Presented to: MPAR Symposium II By: James Williams – Director, Systems Engineering and Safety Date: 17 November 2009 Federal Aviation Administration Multifunction.
Chapter 10 Information Systems Management. Agenda Information Systems Department Plan the Use of IT Manage Computing Infrastructure Manage Enterprise.
Session 151 National Incident Management Systems Session 15 Slide Deck.
Considering an Enterprise Architecture for the NSDI
November 2009 Network Disaster Recovery October 2014.
1 IT Governance 2006 Strategy/Business Case Presentation Department of Human Services.
Confidential Crisis Management Innovations, LLC. CMI CrisisPad TM Product Overview Copyright © 2011, Crisis Management Innovations, LLC. All Rights Reserved.
Trichord/VDOT Public Private Partnerships Experiences and Lessons Learned May 19, 2003 Trichord, Inc James Monroe Highway Leesburg, VA (703)
Update on MOITS Strategic Plan Development Andrew J. Meese, AICP COG/TPB Staff MOITS Technical Subcommittee September 9, 2008 Item # 5.
Wisconsin Digital Summit Monona Terrace November 15, 2004 Justice and Public Safety Interoperability: Wisconsin’s Justice Information Sharing (WIJIS) Initiative.
What is Enterprise Architecture?
11 SECURITY TEMPLATES AND PLANNING Chapter 7. Chapter 7: SECURITY TEMPLATES AND PLANNING2 OVERVIEW  Understand the uses of security templates  Explain.
1 NYC D.C Metro PA JUSTIS & The SHIELD Pilot December 12, 2003 Office of Justice Programs Senior Staff Presentation.
National Capital Region Climate Change Report OVERVIEW Joan Rohlfs, Chief, Air Quality Planning Metropolitan Washington Council of Governments October.
Coordination and Net Working on DRR Rapid Emergency Assessment and Coordination Team (REACT) Bishkek November, 2009.
Disaster Management eGov Initiative (DM) Program Overview December 2004.
Dixie Regional ITS Architecture Project Summary July 31, 2006.
RESF-1 Transportation Kick-Off Workshop Chair: Natalie Jones-Best (DDOT) April 19 th, am to 12 noon.
Metropolitan Washington Council of Governments (MWCOG) Geographic Information System Committee Proposal for 2007 National Spatial Data Infrastructure Cooperative.
Enterprise GIS Planning and Framework Jennifer Reek GIS Coordinator City of Brookfield, WI.
Introduction to the Data Exchange Hub (DEH) Project July 15, 2005.
Information Sharing Challenges, Trends and Opportunities
Nevada Communication Interoperability Plan Overview Developed by Nevada Communications Steering Committee Version 2.0 – Adopted April 6, 2006.
Briefing on the Washington Metropolitan Area Transportation Operations Coordination (MATOC) Program Presentation to the Transportation Planning Board Michael.
2010 W EST V IRGINIA GIS C ONFERENCE Wednesday, June 9, 2010.
Homeland Security Grant Program 2015 Process Michelle Hanneken Illinois Emergency Management Agency.
PSIC Grants GIS Needs. Background NCR Region - UASI grants NCR Interoperability Program (NCRIP) –Data Exchange Hub –NCRNet This year DHS grants.
Talking Technology & Transportation (T3) Webinar July 25, 2007.
U.S. Department of Agriculture eGovernment Program July 15, 2003 eAuthentication Initiative Pre-Implementation Status eGovernment Program.
1 Briefing on Draft Safety Element for the 2007 CLRP Michael J. Farrell Andrew J. Meese, AICP COG/TPB Staff TPB Technical Committee November 2, 2007 Item.
Update to MW-COG GIS Committee December 5, Updates Data acquisition status –Physical Transfer: Montgomery County Prince Georges County Prince William.
ITS Standards Program Strategic Plan Summary June 16, 2009 Blake Christie Principal Engineer, Noblis for Steve Sill Project Manager, ITS Standards Program.
United States Department of Justice Global Security Working Group Update Global Advisory Committee November 2, 2006 Washington, D.C.
Capital Beltway Operational Test August Capital Beltway Operational Test 2 Op Test Overview I-95 portion of the Capital Beltway Multi-jurisdiction.
September 25, 2013 Greg Davis FHWA Office of Safety Research, Development and Test Overview of V2I Safety Applications.
EDUCAUSE 2005 Annual Conference October 19, 2005.
1 Course of Action For Strengthening Transportation Communications and Coordination In the National Capital Region Presented by John M. Contestabile Maryland.
City of Minneapolis 35W Bridge Emergency Response October 25, 2007.
National Information Exchange Model (NIEM) Executive Introduction November 29, 2006 Thomas O’Reilly NIEM Program Management Office.
Regional Seminar on Promotion and Utilization of Census Results and on the Revision on the United Nations Principles and Recommendations for Population.
ARCHITECTURE ENGINEERING COMMUNICATIONS TECHNOLOGY AVIATION | CIVIL | CONSTRUCTION SERVICES | DATA SYSTEMS | ENVIRONMENTAL FACILITIES ENGINEERING | GEOSPATIAL.
Camden County Travel Management Coordination Center Project Update Camden County WIB Board Meeting – March 26, 2008.
UASI 2008 Concept Paper Establishing a Coordinated Regional Geospatial Infrastructure for the National Capital Region Tom Conry Fairfax County, VA Virginia.
Your Life Safety Mission Is Our Passion Public Safety Communication Consultants Committed to Earning Your TRUST NCR Study for Regional NG9-1-1 Design July.
RESF-1 Transportation May 2006 Meeting Chair: Natalie Jones Best (DDOT) May 23 rd, pm to 3pm.
1 Item #10 Progress Report on Actions to Improve Regional Transportation Communication and Coordination During Incidents John M. Contestabile Director,
University of Wyoming Financial Reporting Initiative Update April 2016.
Melissa Lance Operations Systems Manager July 16, 2015 Connected Vehicle Update National and Virginia Perspective.
Philippine Network for Injury Data Management System National Center for Disease Prevention and Control National Epidemiology Center Information Management.
P hilippine N etwork for I njury D ata M anagement S ystem PROPOSED SYSTEM DESIGN Information Management Service.
The Do’s and Don’ts of Modernization Maine Bureau of Motor Vehicles Deputy Secretary of State Thomas Arnold.
Building a Transportation Database WMATA Rail Station Mapping Project 3/18/2014.
L’Oreal USA RSA Access Manager and Federated Identity Manager Kick-Off Meeting March 21 st, 2011.
Update from the Faster Payments Task Force
Strategy for Complex Networking, IT, & Telecommunication Decisions
Project Overview – Phase 1
National Emergency Communications Plan Goal 2
Scanning the environment: The global perspective on the integration of non-traditional data sources, administrative data and geospatial information Sub-regional.
PLANNING A SECURE BASELINE INSTALLATION
Interoperable Communications Technical Assistance Program
Presentation transcript:

National Capital Region (NCR) Closed Circuit Television (CCTV) Integration Framework Project Phase I Final Report Summary and Phase II Update June, 2011 John Contestabile Asst. Program Mgr. Homeland Protection

Agenda Nature of the video sharing problem Project Overview / Team / Statement of Work / Study Participants Study Accomplishments Conceptual Interoperability Model / NCR Application Video Sharing Ground rules Recommended “To Be” Architecture Recommended “To Be” Security Concept Future / Follow on Recommendations Next Steps 2

Nature of the Video sharing Problem No policy or CONOPS for sharing Video ownership and permissions to access issues Permission to control Pan/tilt/zoom of the camera No common network to access the video Varying video formats that cannot be viewed by others Varying bandwidth and file size issues Limits on number of users that can access a particular camera feed without “crashing” the system Most systems designed to “aggregate” video within an agency, not share it outside the agency 3

Video Project Overview Goals: Interoperability – able to share video images Develop a Concept of Operations (CONOPS) with the practitioners Provide strategic direction for future video system investments Critical Success Factors: Operating procedures to define and facilitate video sharing Technical Framework to enable video sharing Strategy and resources to implement and maintain a video sharing system. Phase I study to investigate the problem and recommend a way forward (completed March, 2011) Phase II to implement the proposed architecture between the regional Departments of Transportation (to be completed this summer) 4

Project Sponsor, Manager and Partners Project Sponsor NCR Critical Infrastructure Protection Working Group Project Manager DC Homeland Security and Emergency Management Agency Project Partners Johns Hopkins University Applied Physics Laboratory SkyLine Network Engineering, LLC & Earth Security Electronics, LLC 5

Review Statement of Work Five Tasks: Task 1: Finalize Conceptual Project Plan - Hold stakeholder meetings to identify a subset of CCTV systems that represent the region geographically, technologically, jurisdictionally and by discipline. Completed in April 2010 Task 2: Conduct Video Systems Inventory - Develop data collection strategy, identify camera locations with GPS coordinates and retain in a database, and develop GIS presentation of the data. Completed in July 2010 Task 3: Conduct Data Analysis - Identify camera coverage gaps, document “As Is” architecture, develop “To Be” video sharing alternatives, and provide illustrative ROM cost estimates to migrate. Completed October 2010 Task 4: Develop Concept of Operations (CONOPS) – Review policies, standard operating procedures, and any existing CONOPS. Work with participant stakeholders to develop a draft video sharing CONOPS. Completed by November Phase I final draft report completed December, 2010 Task 5: Additional Systems Integration (optional) - Include additional cameras or systems into the framework as requested. Tasked to build a prototype system between the regional transportation agencies. Initiated December 2010 through August

Study Participants Arlington County DC Homeland Security and Emergency Management Agency (HSEMA) Fairfax County (Department of Police) Maryland Department of Transportation (MDOT) Maryland State Police Maryland State Highway Administration (SHA) Maryland Transportation Authority (MdTA) Metropolitan Washington Airports Authority (MWAA), National and Dulles Airports Montgomery County Department of Police Montgomery County Department of Transportation Prince Georges County United States Park Police Virginia Department of Transportation (VDOT) Washington Metropolitan Area Transit Authority (WMATA) Washington Suburban Sanitary Commission Capital Wireless Information Net (CapWIN) * Fairfax County Data Exchange Hub (DEH) * FEMA Office of National Capital Region Coordination * Maryland Coordination and Analysis Center (MCAC) * * indicates video consumer only 7

Study Accomplishments Developed camera inventory of participating agencies Produced a Concept of Operations for video sharing Developed a map based display of cameras Developed “As Is” and proposed “To Be” video sharing architecture Developed a security framework for sharing video images Develop order of magnitude cost estimates for implementation of the “To Be” architecture 8

Conceptual Interoperability Model 9

NCR Adaptation of the Conceptual Interoperability Model 10By: Twyla Garrett circa 2005

Video Sharing Ground Rules Overall Ground Rules Video sharing must be both horizontal and vertical The new system should support any sharing currently in place The new system should initially support real-time video sharing to various centers, who may then provide it to first responder/field units (i.e. Emergency Management Agencies, Fusion, and Operations Centers) 11

Video Sharing Ground Rules Source Agency Decides what to share Video Remains under their control Exclusive Property, right to record, retention policy Determines Security Level for each Video Determines Permissions to see video Retains Pan/Tilt/Zoom (PTZ) camera control Ability to disable video feed or feeds to Receiving Agencies, based on Security level or user group Should not require major modifications to the current video systems Receiving Agencies (Viewing Agencies) May request stored images from Source Agency May retain or share only with Permission from Source Agency MOU needed for recording video of source agency when they do not May request Agency to record images May request PTZ movement 12

Existing “AS IS” Video Sharing Capability The current “As Is” architecture of the participating agencies has traditionally been limited to a combination of video sharing at the Data and Presentation Layers. These methods have been successful for the short term and on a small scale, but have been very expensive and difficult to implement. As we look towards a regional architecture for video sharing these current methods will need to be replaced with a more efficient and network friendly approach. 13

Potential Types of Video Sharing Presentation Layer video sharing requires expensive infrastructure investment, distributes control, creates network security issues, and typically requires each connection to be a custom design. The user will typically have separate workstations for each application. Data Layer video sharing allows for direct access to the video source, but increases the need for expensive, high bandwidth networks. Sharing at this level may also necessitate camera licenses for every camera connection, require extensive firewall rules, lead to major scalability issues, and require the source data to be a particular type of feed leading to the expense of new equipment. Physical Security Information Management (PSIM) video sharing is a combination of the Presentation Layer and Data Layer models. This technique, while applicable to a limited number of EOCs, multiplies the issues of connectivity costs, network security, source control, and network bandwidth needs if applied regionally. 15

Recommended “TO BE” Video Sharing Concept Utilize a Layered Approach Interoperability is achieved in the Integration Layer Normalize the data Distribute the data utilizing a Secure Architecture Allow Data to be viewed in each Agency’s current Presentation Layer Application 20

21

22

Recommended “TO BE” Video Sharing Concept Pros: Provides Agency with source control and the ability to create multiple security domains Camera and Intranet are only accessed once Firewall Friendly Eliminates Vendor Dependence Allows Agencies freedom to choose VMS and Presentation Applications that meets their needs Highly scalable Low Bandwidth impact Ability to share with Mobile devices Ability to create instant access to video No Client needed to see the video Ability to Adjust Stream Bandwidth Ability to Change Stream Output Comparable Cost is low Cons: Additional Configuration needed to extend PTZ control Limited Access to Video Archives 23

Recommended “TO BE” Video Sharing Security Concept Four Video Security Levels, set by the owning agency. Level 1 – Open access to partners - public/no MOU needed Ex. Highway Traffic video, public parking areas Level 2 – Open access to partners/regional MOU needed Ex. Rail platform video, lobbies, plazas Level 3 – Restricted access to partners/agency specific MOU needed Ex. Views of non-public areas, internal building video Level 4 – LEO only/restricted access/agency specific MOU needed Ex. Surveillance video, screening areas, possibly encrypted 24

Recommended “TO BE” Video Sharing Security Concept Four User Security Levels, set by the owning/receiving agencies. Level 1 - Unlimited Access at the owning agency Unlimited Access at the receiving agency Level 2 - Unlimited Access at the owning agency Unlimited Access at the receiving agency Level 3 - Unlimited Access at the owning agency Access controlled by user ID/password or authentication at the receiving agency Level 4 - Access controlled by the owing agency Generally no access except by MOU, controlled by user ID/password or authentication at the receiving agency 25

Phase II Next Steps Under “Optional Task 5”, Implement the “To Be” video sharing architecture between the regional transportation agencies (i.e. VDOT, DC DOT, MDOT/SHA) Sub Task 1 – Review Architecture with the transportation agencies in light of existing and proposed systems Sub Task 2 – Develop proposed systems design(s) and cost estimate(s) Sub Task 3 – Implement the selected proposed system design Additional ‘08 UASI Funding - $200,000 Period of performance – December 2010 to August

Phase II Next Steps Demonstration 27

Phase III - FY 2011 UASI Follow on Project - $740K Expand the DOT pilot architecture to other partners (particularly MWAA and WMATA)…to include hardware Integrate map based display of cameras with regional GIS systems (i.e. VIPER/EMMA/iSAVE/vUSA ) and other data sets Develop systems documentation (i.e. DEH/NCRnet) as well as a long term governance and sustainment plan in association with the CIO Committee Refine security framework based on implementation of the “To Be” architecture Develop a plan for Private Sector participation in regional video sharing 28

Questions? Many thanks to All who participated in this study! John Contestabile Johns Hopkins University/Applied Physics Lab 29

Additional Slides 30

NCR CCTV Project Inventory 31