Phase II: Communications Asset Database CAD

1
Phase II Communications Asset Database (CAD) Lt
Col H. Calvin Bowditch NCS Critical
Infrastructure Protection Division
(NC3) Calvin.bowditch_at_ncs.gov [phone]
Dec 5, 2006
2
Communications Asset Database (CAD) Purpose

• The National Communications System (NCS) of the
  Department of Homeland Security solicited
  information addressing rapidly deployable voice
  and data communications systems to support
  emergency responders during natural disasters or
  other situations where the communications
  infrastructure is congested, damaged, or
  otherwise made inoperable (e.g., loss of power)

2
3
Purpose of Request for Information (RFI)

• Obtained information from service providers,
  equipment integrators, government agencies, and
  private organizations that can provide turn-key
  rapidly deployable emergency telecommunications
  systems and services in specific technology areas
  

3
4
Structure of RFI

• Provide any materials, suggestions, and
  discussion you deem appropriate. Include, as
  appropriate, the following information
• Description of products/technologies/research/stan
  dards, including performance information
• High-level system architecture views showing
  connectivity between proposed devices, network
  elements, etc.
• Bandwidth and spectrum requirements for proposed
  products and/or services
• Plans for commercial use of these technologies
• Currently deployed equipment/services in
  applications similar to the NCS mission
  requirements
• Other deployed systems as appropriate
• Cost, schedule, and delivery estimates
• Deployment and operational considerations
  (required staff to operate, etc.)
• Existing Government contracts
• Corporate expertise, background, staffing
  capabilities (including security clearances, if
  applicable)

4
5
Technology Categories (Definitions)

• Mobile Satellite Systems providing two-way
  voice/data communications. Both single channel
  and multi-channel equipment to be installed in a
  mobile communications vehicle or other
  transportable container (e.g. fly away kit)
• Land Mobile Radio (LMR) providing two-way voice
  communications
• Cellular providing two-way voice and data
  communications
• System Integrators/Interoperability solutions
  providing voice connectivity interoperable
  solutions between disparate voice networks (e.g.
  LMR, cellular, military, PSTN, etc.). Provide
  details of the interoperable equipment as well as
  the engineering services to be used in
  identifying, deploying, and operating engineered
  solutions in an incident area
• Internet/Data Communications solutions providing
  two-way data communications to support operations
  staff personnel

5
6
Processing Requests for Communications Assistance

• Requests for federal communications support for
  State and local authorities come via the FCO to
  ESF 2
• ESF 2 will check on availability of potential
  solutions among commercial options. Commercial
  solutions will normally be processed through FEMA
  TIMACS. This step involves a check by FEMA IT to
  ensure they do not have needed items in stock
• If a commercial option is not available then
  federal options will be considered (FEMA, DHS,
  NIFC, DoD). DoD options are considered to be a
  last resort
• ESF 2/NORTHCOM LNO will work with the DCO to
  determine if a DoD solution is appropriate. If
  the best solution is a DoD solution then ESF 2
  will process the MA and the ESF 2 NC LNO will
  coordinate the request through the DCO to
  NORTHCOM
• If a government asset is deployed then ESF 2
  will take as a priority action finding a
  commercial solution to replace it
• The actual deployment of any asset will be
  reported and tracked by ESF 2

6
7
Support Elements
Industry
ESF 2 Support Agencies
Request Deployment
Acquisition
ESF 2 FECC (NCC Supporting)
Deploy Assets / Services
Deploy Communication Assets
SCO/FCO
Track Deployment
Request assistance
Track Deployment
State Local Request
Incident area
7
8
Phase II Improvements

• Transitioned CAD to a platform environment that
  provided operational simplicity and can
  accommodate future enhancements
• Implemented multi-user, web-based system
• Solves scalability issue
• Solves synchronization issue
• Solves some data refresh/updates issues
• Solves configuration control issue
• Included authenticated access
• Solves some security issues
• Developed new and improved system capabilities
  defined by users

8
9
Phase II Notional System View
9
10
Phase II Issues

• To realize benefits in 06, the following issues
  are being addressed
• End user training
• Exercises (if needed)
• Operational environment issues (SQL Server
  acquisition, etc.)

10