Attachment_2_PWS_170002_A1.pdf

Attachment 2

HSCG44-17-R-170002

Amendment 0001

Performance Work Statement

Attachment 2 - PWS 1 HSCG44-17-R-170002/Amendment 0001

PERFORMANCE WORK STATEMENT (PWS)

FOR UNITED STATES COAST GUARD RESCUE 21 COASTAL AND VESSEL

TRAFFIC SERVICE (VTS) RADIO CONTROL SYSTEM (RCS)

1.0 BACKGROUND

This Performance Work Statement (PWS) provides for the procurement, integration with government-furnished base stations, delivery, configuration, installation, and operational testing of a Radio Control System for the Rescue 21 Coastal and Vessel Traffic Service systems.

Rescue 21 (R21) Coastal provides Very High Frequency (VHF) and Ultra High Frequency (UHF) communications, Digital Selective Calling (DSC), and Direction Finding (DF) capabilities for the United States Coast Guard (USCG) in the continental United States, Hawaii, Guam, Saipan, Rota, Puerto Rico, and the US Virgin Islands. The system is installed at 32 Coast Guard sectors and 168 stations, with sensors and related equipment at 258 remote fixed facilities (RFFs) (a mix of commercial leased and Coast Guard-owned remote sensor sites). Operating on a 24/7 schedule, the system has been designed to provide an availability of 99.5% for approximately 1,200 operators.

The Vessel Traffic Service (VTS) system provides active monitoring and navigational advice for vessels in ten particularly confined and busy waterways. Its sensors include voice communications (VHF FM, 25 kHz wide band), radar, AIS, and cameras installed at 49 remote sites. The VTS Radio Subsystem, deployed at eight of ten VTS sites, provides overlapping coverage and capabilities with Rescue 21 at many of its ports; consolidation of the two systems will reduce sustainment and Information Assurance costs.

Designed and continually improved over more than ten years of operation, R21 Coastal is tailored to meet Coast Guard requirements and enable security and search and rescue missions.

Customization and a lengthy design period, however, have produced a highly integrated system that is unique to the Coast Guard, making a desired move toward competitive sustainment problematic.

To address this problem, the Coast Guard has developed a transition-to-competition strategy, which takes advantage of required adaptive maintenance activities. The strategy divides R21 Coastal into two parts: a Radio Subsystem, with requirements that can be met by many commercial systems, and a DF/DSC Subsystem that meets unique Coast Guard requirements.

Both subsystems may be further broken down into control systems and radios. Of the three radio types shown in Figure 1, only base stations are directly controlled by the Radio Control System (RCS). However, the RCS must be able to communicate with existing portable and mobile radios and provide Over-The-Air Rekeying capabilities for them. A high level overview of system elements is provided in the following diagram:

Attachment 2 - PWS 2

Figure 1: R21 Coastal System Elements

2.0 SCOPE

The Radio Control System for both R21 Coastal and VTS shall consist of Operator Consoles, a Radio/Console Control and Audio Route/Record/Replay System, status monitoring, and remote maintenance, diagnostic, and correction capabilities. The Radio Control System shall provide record/replay capabilities that will be accessed by the R21 Coastal DF/DSC Subsystem to correlate direction finding lines of bearing with received audio.

The Radio Control System (RCS) shall be capable of integrating wideband analog VHF base stations (R21 and VTS), mixed mode (analog wideband and digital narrowband) VHF base stations (R21 only), and narrowband UHF digital base stations (R21 only). All R21 Coastal base stations will conform to the TIA-102.BAHA standard and the BAHA-A draft extension supporting OTAR capabilities. An Interface Control Document will be provided to support integration of the RCS with R21 Coastal ICOM Eclipse 2 base stations. VTS Quantar T5365A base stations and AstroTac receivers are currently interfaced via 4-wire audio with tone-control.

The Contractor shall provide an adapter for VTS base stations converting analog voice and control to a BAHA-compliant interface, enabling integration with the Radio/Console Control and Audio Route/Record/Replay System.

The U.S. Coast Guard is moving away from the Sector-centric Radio/Console Control and Audio Route/Record/Replay Systems installed at each of the 32 Sectors for R21 Coastal. Rather than having individual “back room” setups, the Coast Guard is moving to a “Regional” paradigm, which will include two or more Sectors, and their associated RFFs, within a given region. Each region will include fully redundant, geographically separate back room systems. This will mitigate the risk of down time due to network or infrastructure failures and allow Sectors within a given region the ability to shift RFF radio watch/control amongst each other. The U.S. Coast Guard is also migrating to virtualized rather than dedicated servers and thin rather than thick client operator consoles running browser-based applications. Thin client consoles and virtualized

Attachment 2 - PWS 3 servers, which simplify support and Information Assurance, are objectives for the Radio Control System.

Radio Control Systems and base stations shall be deployed using a strategy that minimizes effects on critical operations, since a loss of capabilities can result in loss of life or vessel collisions on crowded waterways. Roll out of RCS will be managed over multiple years, with the goal of a soft cutover at each sector or VTS.

To achieve soft cutover, ICOM Eclipse 2 base stations are being integrated with the existing R21 Coastal system. All RFFs are planned to be fully transitioned to ICOM Eclipse 2 base stations that have been configured, tested, and certified as fully operational prior to deployment of RCS.

Installation of RCS at the sector will involve cutover of remote sites to the new RCS while minimizing disruptions to operations. If problems arise, remote sites will be quickly returned to the existing system (a soft cutover). A similar strategy will be used for deployment of VTS workstations (already in place at all sites) and base station adapters.

The Contractor shall conduct a Factory Acceptance Test verifying all required functionality. The Contractor shall install a RCS and perform a System Operation Verification Test (SOVT) at General Dynamics Mission Systems in Scottsdale, AZ (location of the current support baselines) and at C3CEN in Portsmouth, VA (future Radio Subsystem baseline). The Contractor shall assist General Dynamics in Scottsdale with integration of the DF/DSC Subsystem with RCS’s record/replay capabilities. Upon completion of all system integration and testing, the Contractor, working with General Dynamics, shall install the divided system at three sectors as part of initial deployment efforts. Upon successful Initial Deployment, the Contractor, working with General Dynamics, shall complete deployment to all Coastal sectors. VTS installations shall be coordinated with VTS support personnel and C3CEN’s Command Center product line.

3.0 APPLICABLE DOCUMENTS

TIA TSB 88.1, Rev D Wireless Communication Systems – Performance in Noise and Interference-Limited Situations – Recommended Methods for Technology-Independent Modeling, Simulation and Verification

12-Apr

TIA/EIA 568 Commercial Building Telecommunications Cabling Standard 15-Dec TIA-102.BAHA or BAHA-A draft Project 25 Fixed Station Interface Messages and Procedures 2006

TIA-102.AACA-A Project 25 Digital Radio Over-the-Air Rekeying (OTAR) Protocol 2014

TIA-102.BAAA-A Common Air Interface 2013 DHS 4300 5.4.5 SENSITIVE SYSTEMS HANDBOOK v11.0 Jan-15 TIA-102.CAAA-D Transceiver Measurements and Methods 2013 TIA-102.CAAB-D Transceiver Performance Recommendations 2013

TIA-603-E Land Mobile FM or PM Communications Equipment Measurement and Performance Standards Mar-16

TIA-102.AACD Project 25 Digital Land Mobile Radio- Key Fill Device Interface Protocol 2014

Attachment 2 - PWS 4

1692-2011 IEEE Guide for the Protection of Communication Installations from Lightning Effects 2011

Motorola R56 Standards and Guidelines for Communication Sites 2005

NFPA 70 National Electric Code 2015

3.1 Performance Work Statement (PWS) Addendums

PWS Addendum A: Sector, Station, RFF, VTS, VTS Remote Site Locations and Equipment PWS Addendum B: Rescue 21 Coastal Regions PWS Addendum C: C3CEN Security (CL-CS) Industrial Security Addendum for Secret Classified-Related Work

4.0 PERFORMANCE REQUIREMENTS

4.1 The Contractor shall provide all supplies, services, resources, and management necessary to complete all tasks listed in this PWS.

4.2 Contract Work Breakdown Structure

The Contractor shall provide a Contract Work Breakdown Structure in accordance with CDRL A001.

Deliverable A001: Contract Work Breakdown Structure, CDRL A001, DID DI-MGMT- 81334D

4.3 Integrated Project Schedule (IPS)

The Contractor shall develop and maintain an event-based Integrated Project Schedule (IPS), which includes each CLIN awarded, exercised, and/or not exercised to be used as a primary tracking tool for technical and schedule status. The IPS shall be in accordance with CDRL A002 and contain all events and accomplishments for performance of this contract/order by the Contractor and major subcontractors, plus delivery milestones. The Contractor’s IPS shall show the critical path for all applicable deployment tasks by Sector, region and VTS and be updated quarterly.

Deliverable A002: Integrated Project Schedule, CDRL A002, DID DI-MGMT-81650

4.4 Information Assurance Compliance Report / Radio Control System Prohibited Protocol Certification The Contractor shall document, in accordance with CDRL A003, that the Radio Control System contains no prohibited protocols in accordance with reference DHS 4300A Sensitive Systems Policy (https://www.dhs.gov/publication/4300a-sensitive-systems-policy), specifically paragraph 5.4.5, and DISA Ports, Protocols, and Services PPS Category Assignments List (CAL).

Examples of prohibited protocols include TELNET, FTP, etc. The Contractor shall provide a list of all protocols that are resident on the RCS for Government validation against the policies and guidance mentioned above.

https://www.dhs.gov/publication/4300a-sensitive-systems-policy

Attachment 2 - PWS 5

Deliverable A003: Information Assurance Compliance Report, Radio Control System Prohibited Protocol Certification, CDRL A003, DID DI-MISC-80508B

4.5 Integration

4.5.1 Radio Control System (RCS) Integration with Base Stations The Government will provide ICOM Eclipse 2 and Quantar base stations to the Radio Control System Contractor for integration with the RCS within 30 days after award. The Government will provide all base station documents needed for the integration task. See PWS Section 8.0 Government Furnished Resources, Equipment, and Information for additional details.

4.5.2 Factory Acceptance Test Procedure

A Factory Acceptance Test Procedure (in accordance with CDRL A004) shall be provided to the Government for approval prior to the Factory Acceptance Test.

Deliverable A004: Factory Acceptance Test Procedure, CDRL A004, DID DI-NDTI-81942

4.5.3 Factory Acceptance Test of the Radio Control System

Post-integration, the Contractor shall conduct a Factory Acceptance Test of the Radio Control System with the integrated base stations (R21 and VTS). The Factory Acceptance Test shall include a live demonstration of OTAR capabilities. The Contractor shall propose a location for the live demonstration. The Government will provide portable and mobile radios to be used for the demonstration.

4.5.4 Factory Acceptance Test Report

A Factory Acceptance Test Report (in accordance with CDRL A005) shall be provided to the Government after successful completion of the test. The complete Radio Subsystem shall meet all requirements.

Deliverable A005: Factory Acceptance Test Report, CDRL A005, DID DI-NDTI-80809B

4.6 Deployment of RCS to General Dynamics

The Contractor shall deploy a Radio Control System (RCS) to General Dynamics to support division of the existing R21 Coastal system.

4.6.1 Site Survey-General Dynamics

The Contractor shall perform a site survey for installation of RCS at General Dynamics in Scottsdale, AZ. A site survey report shall be provided to the Government in accordance with

CDRL A006.

Deliverable A006-01: General Dynamics Site Survey Report, CDRL A006, DID DI-MISC- 81381

Attachment 2 - PWS 6

4.6.2 Installation Plan-General Dynamics

The Contractor shall develop an installation plan for General Dynamics in accordance with CDRL A007. ICOM Eclipse 2 base stations will be on site, installed, and ready to support installation, configuration, and testing.

Deliverable A007-01: General Dynamics Installation Plan, CDRL A007, DID DI-MGMT- 80033A

4.6.3 Bill of Materials--General Dynamics

The Contractor shall provide a Bill of Materials (BOM) for the General Dynamics installation in accordance with CDRL A008.

Deliverable A008-01: Radio Control System BOM, CDRL A008, DID DI-SESS-81359B

4.6.4 SOVT--General Dynamics

The Contractor shall provide, install, configure, and perform a System Operational Verification Test (SOVT) of the Radio Control System at General Dynamics Mission Systems, Inc., 8201 E.

McDowell Road, Scottsdale, AZ 85257, after written notification from the Contracting Officer, and with completion on or before 90 calendar days after award. A SOVT Plan (in accordance with CDRL A009) shall be provided to the Government for approval prior to the test. A SOVT Report (in accordance with CDRL A010) shall be provided to the Government after successful completion of the test. The complete Radio Subsystem shall meet all requirements.

Deliverable A009-01: SOVT Plan, CDRL A009, DID DI-QCIC-80154A

Deliverable A010-01: SOVT Report, CDRL A010, DID DI-NDTI-80809B

4.6.5 Radio Control System Support Documentation- General Dynamics Mission Systems The Contractor shall provide all Radio Control System installation manuals, configuration manuals, system administration manuals, repair manuals, and repair parts lists (in accordance with CDRL A011) necessary for support of RCS to General Dynamics.

All Radio Control System installation manuals, configuration manuals, system administration manuals, repair manuals, and repair parts lists will be posted on a USCG Intranet portal for Government use.

Deliverable A011-01: Radio Control System Support Documentation, CDRL A011, DID

DI-TMSS-80527C

4.6.6 RCS Operator and Maintenance Training

The Contractor shall provide operator and maintenance training on the Radio Control System installed at General Dynamics Mission Systems. Training shall include two sessions for a maximum of 10 persons per session. The Contractor shall provide electronic and hard copies of the course material for each student prior to training. Training will be attended by both Government and contractor personnel.

Attachment 2 - PWS 7

Deliverable A012-01: Radio Control System Training Manuals, CDRL A012, DID DI-

SESS-81518C

4.6.7 Radio Control System (RCS) Interface Control Document

The Contractor shall provide an Interface Control Document (in accordance with CDRL A014) which includes all information necessary to support integration of the Radio Control System and the DF/DSC Subsystem. The Government assumes that documentation on accessing recorded audio from the digital voice logger will be sufficient to support this effort. The Contractor shall provide remote assistance via phone and email to answer questions or clarify information.

Deliverable A014: Radio Control System Interface Control Document, CDRL A014, DID

DI-IPSC-81436A

4.7 Deployment of RCS to USCG C3CEN

The Contractor shall deploy the Radio Control System to C3CEN.

4.7.1 Site Survey-C3CEN

The Contractor shall perform a site survey for installation of the RCS at C3CEN. A site survey report shall be provided to the Government in accordance with CDRL A006.

Deliverable A006-02: C3CEN Site Survey Report, CDRL A006, DID DI-MISC-81381

4.7.2 Installation Plan-C3CEN

The Contractor shall develop an installation plan for C3CEN in accordance with CDRL A007.

Deliverable A007-02: C3CEN Installation Plan, CDRL A007, DID DI-MGMT-80033A

4.7.3 RCS Bill of Materials-C3CEN

The Contractor shall provide a Bill of Materials (BOM) for the C3CEN installation in

Deliverable A008-02: Radio Control System BOM, CDRL A008, DID DI-SESS-81359B

4.7.4 SOVT-C3CEN

The Contractor shall provide, install, configure, and perform a System Operational Verification Test (SOVT) of the Radio Control System at the Coast Guard’s Command, Control, and Communications Engineering Center (C3CEN), 4000 Coast Guard Blvd., Portsmouth, VA 23703, after written notification from the Contracting Officer and with completion on or before 90 calendar days after award. The ICOM Eclipse 2 base stations will be on site, installed, and ready to support installation, configuration, and testing. A SOVT Plan (in accordance with CDRL A009) shall be provided to the Government for approval prior to the test. A SOVT Report (in accordance with CDRL A010) shall be provided to the Government after successful completion of the test. The complete Radio Subsystem shall meet all requirements.

Deliverable A009-02: SOVT Plan, CDRL A009, DID DI-QCIC-80154A

Attachment 2 - PWS 8

Deliverable A010-02: C3CEN SOVT Report, CDRL A010, DID DI-NDTI-80809B

4.7.5 Radio Control System Support Documentation-C3CEN

The Contractor shall provide all Radio Control System installation manuals, configuration manuals, system administration manuals, repair manuals, and repair parts lists (in accordance with CDRL A011) necessary for support of RCS.

All Radio Control System installation manuals, configuration manuals, system administration manuals, repair manuals, and repair parts lists will be posted on a USCG Intranet portal for Government use.

Deliverable A011-02: Radio Control System Support Documentation, CDRL A011, DID

DI-TMSS-80527C

4.7.6 RCS Operator and Maintenance Training

The Contractor shall provide operator and maintenance training on the Radio Control System installed at the Coast Guard’s Command, Control, and Communications Engineering Center (C3CEN), 4000 Coast Guard Blvd., Portsmouth, VA 23703, after written notification from the Contracting Officer. Training shall include two sessions for a maximum of 10 persons per session. The Contractor shall provide electronic and hard copies of the course material for each student prior to training. Training will be attended by both Government and contractor personnel.

Deliverable A012-02: Radio Control System Training Manual, CDRL A012, DID DI-

4.8 Customer Communications Package

The Contractor shall develop a Customer Communications Package (in accordance with CDRL A013) for each CLIN by sector and deliver to the R21 Asset Line at C3CEN. Once reviewed and approved by C3CEN, the Contracting Officer will provide a notice to proceed to the Contractor.

The Customer Communications Package shall include information for CG operators describing the impact of the changes associated with the installation of a new Radio Control System.

Deliverables A013-01 – A013-32: Customer Communications Package, CDRL A013, DID DI-MISC-80508B, Sample format in Exhibit B (32 times)

4.9 Adjustment of Installation Schedules

The Contractor shall be responsible for adjusting installation schedules as necessary to accommodate sector or VTS operations. When an operation requires the use of R21 Coastal or the VTS, the Contractor shall adjust the work schedule to accommodate that need.

4.10 Initial Deployment of RCS - Sectors San Juan, Honolulu, and Guam Working with General Dynamics, the Contractor shall deploy the Radio Control System to Sector San Juan, Sector Honolulu, and Sector Guam. Deployment includes the Radio/Console Control and Audio Route/Record/Replay System at the sectors, operator consoles installed at sectors and stations, and remote site monitoring equipment installed at RFFs.

Attachment 2 - PWS 9

4.10.1 Site Survey-Sector San Juan

The Contractor shall perform a site survey for installations of RCS at Sector San Juan. A site survey shall include the sector, stations, and RFFs. A site survey report shall be provided to the Government in accordance with CDRL A006.

Deliverable A006-03: Sector San Juan Site Survey Report, CDRL A006, DID DI-MISC- 81381

4.10.2 Installation Plan-Sector San Juan

The Contractor shall develop an installation plan for Sector San Juan in accordance with CDRL A007.

Deliverable A007-03: Sector San Juan Installation Plan, CDRL A007, DID DI-MGMT-

4.10.3 RCS Bill of Materials-Sector San Juan

The Contractor shall provide a Bill of Materials (BOM) for the Sector San Juan installation in

Deliverable A008-03: Radio Control System BOM, CDRL A008, DID DI-SESS-81359B

4.10.4 SOVT-Sector San Juan

The Contractor shall install the Radio Control System at Sector San Juan and, working with General Dynamics, perform a SOVT of the complete system (Radio Subsystem and DF/DSC Subsystem) in accordance with CDRLs A009 and A010.

Deliverable A009-03: SOVT Plan, CDRL A009, DID DI-QCIC-80154A

Deliverable A010-03: San Juan SOVT Report, CDRL A010, DID DI-NDTI-80809B

4.10.5 RCS Operator Training-Sector San Juan

The Contractor shall provide operator training on the Radio Control System installed at Sector San Juan after written notification from the Contracting Officer. Training shall include two sessions for a maximum of 10 persons per session. The Contractor shall provide electronic and hard copies of the course material for each student prior to training. Training will be attended by both Government and contractor personnel.

Deliverable A012-03: Radio Control System Training Manual, CDRL A012, DID DI-

4.10.6 Site Surveys- Sectors Honolulu and Guam

The Contractor shall perform site surveys for installations of the RCS at Sectors Honolulu and Guam. Site survey reports shall be provided to the Government in accordance with CDRL A006.

Deliverables A006-04 – A006-05: Sectors Honolulu and Guam Site Survey Reports, CDRL

A006, DID DI-MISC-81381

Attachment 2 - PWS 10

4.10.7 Installation Plans

The Contractor shall develop installation plans for Sectors Honolulu and Guam in accordance with CDRL A007.

Deliverables A007-04 – A007-05: Sectors Honolulu and Guam Installation Plans, CDRL

A007, DID DI-MGMT-80033A

4.10.8 Bill of Materials (BOMs)

The Contractor shall provide Bill of Materials (BOMs) for Sectors Honolulu and Guam installations.

Deliverables A008-04 – A008-05: Radio Control System BOM, CDRL A008, DID DI-

SESS-81359B

4.10.9 SOVTs- Sectors Honolulu and Guam

Contractor shall install the Radio Control System at Sectors Honolulu and Guam and, working with General Dynamics, perform SOVTs of the complete system (Radio Subsystem and DF/DSC Subsystem) in accordance with CDRLs A009 and A010.

Deliverable A009-04: SOVT Plan, CDRL A009, DID DI-QCIC-80154A

Deliverables A010-04 – A010-05: Radio Subsystem SOVT Reports, CDRL A010, DID DI-

NDTI-80809B

4.10.10 RCS Operator Training - Sectors Honolulu and Guam

The Contractor shall provide operator training on the Radio Control System installed at Sectors Honolulu and Guam after written notification from the Contracting Officer. Training shall include two sessions for a maximum of 10 persons per session. The Contractor shall provide electronic and hard copies of the course material for each student prior to training. Training will be attended by both Government and contractor personnel.

Deliverables A012-04 – A012-05: Radio Control System Training Manual, CDRL A012, DID DI-SESS-81518C

4.11 Full Rate Deployment to R21-C Regions

Following completion of the Low Rate Initial Deployments, the Radio Control System shall be deployed on a regional basis to the 48 contiguous United States (see Addendum B). For R21 Coastal and embedded VTS sites, regional deployment shall include a primary Radio/Console Control and Audio Route/Record/Replay System installed at one sector within the region, a secondary hot standby Radio/Console Control and Audio Route/Record/Replay System installed at a different sector in the region, operator consoles installed at sectors, VTSs, and stations, and remote site monitoring and adapter equipment installed at RFFs and VTS remote sites.

Attachment 2 - PWS 11

4.11.1 Site Surveys-R21 Regions

The Contractor shall perform region site surveys for installations in all Government regions. Site survey reports shall be provided to the Government. Site survey reports (in accordance with CDRL A006) shall include recommendations on locations for the Radio/Console Control and Audio Route/Record/Replay System.

Deliverables A006-06 – A006-10: Region Site Survey Reports, CDRL A006, DID DI-

MISC-81381

4.11.2 Installation Plans- R21 Regions

The Contractor shall develop installation plans for R21 regions in accordance with CDRL A007.

Deliverable A007-06 – A007-10: Region Installation Plans, CDRL A007, DID DI-MGMT-

4.11.3 Bill of Materials-R21 Regions

The Contractor shall provide Bill of Materials (BOMs) for region installations in accordance with CDRL A008.

Deliverable A008-06 – A008-10: Radio Control System BOM, CDRL A008, DID DI-SESS- 81359B

4.11.4 SOVTs-R21 Regions

The Contractor shall install the Radio Control System at Coast Guard regions and, working with General Dynamics and VTS support personnel, perform SOVTs of the complete system (Radio Subsystem and DF/DSC Subsystem) in accordance with CDRLs A009 and A010.

Deliverable A009-05 - A009-09: SOVT Plan, CDRL A009, DID DI-QCIC-80154A

Deliverable A010-06 – A010-10: Radio Subsystem SOVT Reports, CDRL A010, DID DI-

NDTI-80809B

4.11.5 RCS Operator Training- R21 Regions

The Contractor shall provide operator training on the Radio Control System installed at all sectors within a Coast Guard region after written notification from the Contracting Officer.

Training shall include two sessions for a maximum of 10 persons per session. The Contractor shall provide electronic and hard copies of the course material for each student prior to training.

Training will be attended by both Government and contractor personnel.

Deliverable A012-06 – A012-10: Radio Control System Training Manual, CDRL A012, DID DI-SESS-81518C

4.12 Non-Disclosure Agreements

If needed, the Contractor shall agree to enter into a non-disclosure agreement with the integration contractor (General Dynamics Mission Systems) and/or the Base Station contractor (ACG Systems, Inc.) to support this effort.

Attachment 2 - PWS 12

5.0 DELIVERABLES

See applicable CDRL for deliverable due date.

Deliverable Numbers CDRL DID Description PWS ref.

A001 A001 DI-MGMT-81334D Contract Work Breakdown Structure 4.2

A002 A002 DI-MGMT-81650 Integrated Project Schedule 4.3

A003 A003 DI-MISC-80508B

Information Assurance Compliance Report, Radio Control System Prohibited Protocol Certification

4.4

A004 A004 DI-NDTI-81942 Factory Acceptance Test Procedure 4.5.1

A005 A005 DI-NDTI-80809B Factory Acceptance Test Report 4.5.1

A006-01 - A006-10 A006 DI-MISC-81381 Site Survey Report

4.6.1 4.7.1 4.10.1 4.10.6 4.11.1

A007-01 - A007-10 A007 DI-MGMT-80033A Installation Plan

4.6.2 4.7.2 4.10.2 4.10.7 4.11.2

A008-01 – A008-10 A008 DI-SESS-81359B Radio Control System BOM

4.6.3 4.7.3 4.10.3 4.10.8 4.11.3

A009 -01 - A009-09 A009 DI-QCIC-80154A System/Site Operational Verification Test (SOVT) Plan

4.6.4 4.7.4 4.10.4 4.10.9 4.11.4

A010-01 - A010-10 A010 DI-NDTI-80809B System/Site Operational Verification Test (SOVT) Report

4.6.4 4.7.4 4.10.4 4.10.9 4.11.4

A011-01 – A011-02 A011 DI-TMSS-80527C Radio Control System Support Documentation

4.6.5 4.7.5

A012-01 - A012-10 A012 DI-SESS-81518C Radio Control System Training Manual

4.6.6 4.7.6 4.10.5 4.10.10 4.11.5

A013-01 - A013-32 A013 DI-MISC-80508B Customer Communications Package 4.8

A014 A014 DI-IPSC-81436A Radio Control System Interface Control Document 4.6.7

Attachment 2 - PWS 13

6.0 TECHNICAL SPECIFICATIONS

The technical specification below contains requirements identified as “Objectives”. An “Objective” is a preferred/desired capability/requirement and will be evaluated based on the degree of benefit provided to the Government. All others are required minimum capabilities/requirements.

6.1 User Authentication & Microsoft Active Directory Integration The Radio Control System (RCS) shall be capable of being integrated with the USCG’s enterprise information system management environment (USCG Microsoft Active Directory) and shall require users and administrators to authenticate at log-in using USCG-issued Common Access Cards (CAC).

6.1.1 Operator Console Locking. The system shall prevent the Operator Console from locking during periods of inactivity or removal of a user’s CAC.

6.1.2 User Log-in Agreement Banner. The system shall be able to display the USCG user agreement banner at log-in.

6.1.3 Operation during Log-out/Log-in. The Operator Console shall be able to continue to receive audio, provide audio through speakers, and record audio during user log-out/log-in at the beginning and end of each watch stander’s duty period.

6.1.4 User Account Lockout. User account shall be able to be locked after 45 days of inactivity.

6.2 Information System Security

The system shall be characterized as Moderate-Moderate-Moderate for Confidentiality, Integrity, and Availability in accordance with National Security Systems (CNSS) Instruction No. 1253, Security Categorization and Control Selection for National Security Systems, NIST SP 800-60, Guide for Mapping Types of Information and Information Systems to Security Categories and the Federal Information Processing Standards [FIPS] 199, Standards for Security Categorization of Federal Information and Information Systems). The system shall be capable of meeting required technical security requirements set forth in the applicable NIST 800-53 security controls as determined by the relevant CNSSI no. 1253 Security Control Baseline for this security categorization level.

6.2.1 STIG Hardening. RCS related workstation and server operating systems as well as any associated applications and devices shall be capable of being configured according to applicable DoD Security Technical Implementation Guides (STIGS). The Contractor shall complete the STIG Applicability Guide and Collection Tool hosted at http://iase.disa.mil/stigs/agct/Pages/index.aspx.

• All applicable STIGs found after completing the checklist shall be implemented on the system.

• Windows 10 Version 1, Release 2 (01 FEB 2016), or latest version, posted at:

http://iase.disa.mil/stigs/os/windows/Pages/index.aspx

Attachment 2 - PWS 14

• Windows Server Version 2, Release 3 (23 OCT 2015), or latest version, posted at:

• DoD STIG Master list is available at: http://iase.disa.mil/stigs/Pages/a-z.aspx

• Completed STIG checklists shall be made available for Government review upon request.

6.2.2 Enterprise Services. System operator consoles and servers shall be compatible with Coast Guard enterprise SCCM 2012 patch management and the DoD McAfee Host-Based Security System (HBSS) (see http://www.disa.mil/hbss) applications.

6.2.3 System Protocols. The Contractor shall ensure that the Radio Control System contains no prohibited protocols in accordance with reference DHS 4300A Sensitive Systems Policy (www.dhs.gov/publication/4300a-sensitive-systems-policy), specifically paragraph 5.4.5, and the DISA Ports, Protocols, and Services PPS Category Assignments List (CAL). Examples of prohibited protocols include TELNET. FTP, etc. System PPS lists shall be made available for Government review upon request.

6.3 Radio Control System Capacities

6.3.1 Operator Consoles. The RCS shall support a minimum of 75 non-collocated (network-connected) Operator Consoles (sector, VTS, or station, see sections 4 and 5 below) with a single Radio/Console Control and Audio Route/Record/Replay System.

6.3.2 Radios. The RCS shall integrate and support a minimum of 300 (quantity) ICOM Eclipse 2 and Quantar VHF (R21 and VTS) base stations and ICOM Eclipse 2 UHF base stations (R21 only) with a single Radio/Console Control and Audio Route/Record/Replay System.

6.3.3 Network Capacity. Operator consoles, base stations, and the Radio/Console Control and Audio Route/Record/Replay System will be primarily non-collocated. Information on network throughput requirements for the total number of radios and operator consoles is required.

6.4 Radio/Console Control and Audio Route/Record/Replay System

6.4.1 Redundancy. The RCS shall include non-collocated, hot standby redundancy for the Radio/Console Control and Audio Route/Record/Replay System, supporting continued operation of consoles and Remote Fixed Facility (RFF) radios when the primary Radio/Console Control and Audio Route/Record/Replay System is inoperative or network connections fail.

6.4.1.1 Capability Description. Hot standby capabilities, switching time, and switching method shall be described sufficiently to understand the impact on capabilities and operations. Objective for console switch over: <= 10 minutes; Threshold: <= 60 minutes.

6.4.1.2 Effect on RFFs or VTS Remote Sites. If modifications are required at RFFs or VTS remote sites to support redundancy, describe those modifications, their installation http://iase.disa.mil/stigs/os/windows/Pages/index.aspx http://iase.disa.mil/stigs/Pages/a-z.aspx http://www.disa.mil/hbss http://www.dhs.gov/publication/4300a-sensitive-systems-policy

Attachment 2 - PWS 15 procedures, and any impact on operations during installation.

6.4.1.3 Effects on Interfaces. If modifications are required at RFFs or VTS remote sites to support redundancy, describe the effect of those modifications on the TIA-102.BAHA-A and OTAR interface between the Radio/Console Control and Audio Route/Record/Replay System and RFFs.

6.4.2 Architecture. Virtualization of Radio/Console Control and Audio Route/Record/Replay System servers is an objective requirement. Individual physical servers are a threshold requirement.

6.4.3 System Flexibility. Radio/Console Control and Audio Route/Record/Replay Systems are to be installed over large regions sufficient to provide continued operation during natural or man-made disasters in any one area. However, disasters may occur that degrade parts of two regions. Therefore, the ability to add new or move existing consoles from one region to another, or RFFs from one region to another, is an objective requirement. If the Coast Guard reconfigures its network to support data exchange, adding RFFs or consoles should require one hour or less of one person effort. This capability should exist at a System Administrator level. Vendor or manufacturer intervention should not be required.

6.5 Record/Replay

6.5.1 General. The system shall record and provide a means to playback all transmitted and received communications for the previous 30 days at each operator console.

6.5.2 Unencrypted Recordings. The system shall record all voice transmissions in an unencrypted audio format.

6.5.3 Instant Playback. The system shall provide a means to replay the last received call or any call during a user selectable time interval within the last 30 minutes.

6.5.3.1 Instant Playback Response. The system shall initiate the replay of a selected transmission within one (1) second of selecting the call.

6.5.4 Playback Sorting. The system shall allow the operator to sort recorded calls by date/time, RFF, and channel.

6.5.4.1 Playback Sorting Response. The system shall re-sort the recorded calls list within one (1) second of operator command.

6.5.5 Archiving. The system shall allow the operator to select one or more recorded calls for archiving to non-flash portable media, such as compact disk (CD) or digital video disk

(DVD).

6.5.6 Timestamp. The system shall timestamp all recordings. Timestamp precision shall be one second or better. Objective: 0.1 second.

6.5.7 Digital Voice Logger Integration. The Coast Guard has a requirement to provide an interface control document to a third party for integration of digital voice logging capabilities (ability to independently search for and retrieve recorded audio). Contractor must provide a

Attachment 2 - PWS 16

Digital Voice Logger interface control document to General Dynamics to support DF/DSC integration.

6.6 Operator Consoles

6.6.1 Sector Operator Consoles. The RCS shall include multiple operator consoles (i.e. 3-4) at each of thirty-two (32) Sector Command Centers (SCCs) for R21 and 2-7 operator consoles at eight (8) Vessel Traffic Centers.

6.6.1.1 Sector Operator Console RFF Capacity. Each Sector Operator Console shall have the capacity to transmit/receive and change channels on all radios at a minimum of twenty (20) RFFs (5 radios per RFF).

Objective: 30 RFFs, 5 radios per RFF

6.6.1.2 Speakers. Each Sector Operator Console shall provide a minimum of six (6) speakers. At least one speaker in the Sector Operator Console shall be capable of monitoring all base stations assigned to the Operator Console. RCS shall support assignment of one or more base stations to the other speakers.

6.6.1.3 Foot Pedal. Each Sector Operator Console shall provide a dual action foot pedal to key the microphone and mute all speakers.

6.6.1.4 Headsets. Each Sector Operator Console shall be provisioned with a wired headset with push to talk button, microphone, and headphones. Wireless headsets cannot be used in sectors.

6.6.1.5 Sector Console Architecture. An operator console running thin client, browser-based applications is an objective requirement. Consoles running thick client applications are the threshold requirement.

6.6.2 Station Operator Consoles. The system shall include one (1) Station Operator Console at each Coast Guard station.

6.6.2.1 Station Operator Console RFF Capacity. Each Station Operator Console shall have the capacity to transmit/receive and change channels on all radios at a minimum of ten (10) RFFs (5 radios per RFF).

Objective: 20 RFFs, 5 radios per RFF

6.6.2.2 Speakers. Each Station Operator Console shall provide a minimum of four (4) speakers. At least one speaker in the Station Operator Console shall be capable of monitoring all base stations assigned to the Operator Console. RCS shall support assignment of one or more base stations to the other speakers.

6.6.2.3 Foot Pedal. Each Sector Operator Console shall provide a dual action foot pedal to key the microphone and mute all speakers.

6.6.2.4 Headsets. Each Sector Operator Console shall be provisioned with a wired headset with push to talk button, microphone, and headphones. Wireless headsets cannot be used in sectors.

Attachment 2 - PWS 17

6.6.2.5 Station Console Architecture. An operator console running thin client, browser-based applications is an objective requirement. Consoles running thick client applications are the threshold requirement.

6.6.3 Operator Console Intercom. The system shall provide separate intercom capabilities between SCCs, between the SCC and its subordinate stations, and between SCCs and VTCs.

6.6.4 Visual Indication. Operator Consoles shall provide a visual indication of which RFF is transmitting or receiving a signal.

6.6.5 Manual Muting. Operator Consoles shall be capable of manually muting all speakers upon command by the operator. Manual mute shall automatically un-mute after 30 seconds.

6.6.6 Cross-muting. The RCS shall provide a cross-muting capability to support muting of adjacent base stations when transmitting on a common frequency.

6.6.7 Time-out. Operator consoles shall be capable of “timing-out” to prevent unnecessary or unwanted transmissions (e.g., stuck key).

6.6.8 Operator Console Configuration. Configuration of an Operator Console shall be restricted to a system administrator user role.

6.6.8.1 Administrative Control of RFFs. Selection of which RFFs or VTS remote sites are monitored by an operator console shall be restricted to a system administrator user role.

6.6.8.2 Administrative Control of Frequency Selection. Configuration of frequencies available for selection by an operator during channel changes shall be restricted to a system administrator user role. The USCG will use this capability to ensure that one radio always remains on channel 16.

6.6.8.3 Speaker Configuration. Assignment of RFFs or VTS remote sites to operator console speakers shall be restricted to a system administrator user role.

6.7 Encryption

The RCS, when integrated with ICOM Eclipse 2 base stations, shall provide FIPS Pub 140-2 compliant encryption capabilities including FIPS-197 compliant Advanced Encryption Standard (AES) and Digital Encryption Standard (DES) encryption of “Over the Air” communications on P25 Phase 1 digital channels in the Federal Land Mobile Radio band. Note: The requirement is for “Over the Air” encryption of sensitive data, not end-to-end encryption over-the-wire.

6.7.1 Multi-Key Encryption. The system shall store a minimum of twenty-seven (27) unique encryption keys for separate missions.

6.7.2 User Selectable. The system shall allow the operator to select the encryption mode (clear/protected) and encryption key.

6.7.3 Encryption Mode Indicator. The system shall provide a visual indicator to the operator identifying whether transmitted or received calls are encrypted or in the clear

6.8 Key Management Facility (KMF).

The R21 RCS is currently configured to receive P25-compliant encryption key material over the network from a Motorola Key Management Facility (Motorola KMF Server, KMF Client version 7.14.0033) installed and operated at the US Customs and Border Protection (CBP) National Law

Attachment 2 - PWS 18

Enforcement Communications Center (NLECC). If the proposed Radio Control System is not compatible with current Motorola KMF equipment, the system shall be compliant with other vendor commercial KMF equipment (provide details on the commercial KMF system that affords compatibility).

6.8.1 Over The Air Re-Keying. The system shall be capable of receiving Key Management Messages (KMMs) generated by the CBP NLECC and distributing the KMMs to mobile subscriber units. If not compatible with the Motorola equipment, the system shall be compliant with other vendor commercial KMF equipment (provide details on commercial KMF compatibility).

6.8.2 Encrypted Communications Compatibility with USCG Standard Mobile Radios.

The system shall be compatible with Project 25 (P25) mobile and portable radios which support both Digital Encryption Standard (DES) and Advanced Encryption Standard (AES) encryption. All radios conform to the TIA–102.AACA-A Project 25 Digital Radio Over-the-Air Rekeying (OTAR) Protocol.

6.9 RFF and VTS Remote Site Monitoring.

The RCS shall monitor sensors at the RFFs and VTS remote sites and display status at the SCC R21 and VTS Operator Consoles. The system shall provide a visual and audible alarm if the statuses of RFF sensors change as well as a means of acknowledging and resetting the alarm.

The system shall record sensor values for a minimum of 30 days to support trend analysis. The system shall also provide remote access by maintenance personnel external to the Operator Console to support fault location and identification.

6.9.1 Intrusion Detection. For RFFs and VTS remote sites where the Coast Guard is the sole occupant of a shelter, the Remote Site Monitoring System shall alarm when the shelter door is opened. For RFFs or VTS sites where the equipment is in a shared space, the Remote Site Monitoring System shall alarm when the equipment cabinet access door is opened.

6.9.2 High/Low Temperature. The Remote Site Monitoring System shall alarm when the RFF or VTS remote site is above or below its normal temperature range.

6.9.3 Fire/Smoke Alarm. The Remote Site Monitoring System shall alarm when smoke is detected in the RFF or VTS remote site.

6.9.4 Utility Power. The Remote Site Monitoring System shall indicate whether the site is operating on normal utility power or an emergency back-up power supply.

6.9.5 Radio Fault Monitoring. The system shall indicate the operational status of the RFF and VTS radios including any built-in self-diagnostic fault monitoring capability of the radios.

6.9.6 Generator Status. The system shall indicate the status of the RFF generator.

6.9.7 Generator Fuel Status. The system shall provide information on the level of propane or diesel and generate an alarm when tank is ¼ full.

6.9.8 Consumable Near Real-Time System Status Information. The RCS shall provide near real-time system operating status information, and RFF and VTS remote site monitoring sensor status, in one of the consumable formats listed below:

Attachment 2 - PWS 19

• Coast Guard Enterprise Service Bus (ActiveMQ-based)

• Kml

• Shapefile

6.10 Telephone Interface (sector only)

The RCS shall provide a minimum of one telephone line interface at each sector Operator Console. The telephone interface shall allow the operator to dial and receive telephone calls on the Public Switched Telephone Network (PSTN) via Government-provided analog POTS lines collocated with the Radio/Console Control and an Audio Route/Record/Replay System (primary and back up).

6.10.1 Call History. The telephone interface shall provide a list of a minimum of the last ten dialed and received telephone calls.

6.10.2 Contact List. The telephone interface shall include a contact list to store a minimum of one hundred frequently used telephone numbers.

6.10.3 Caller ID. The system shall display the telephone number and identification of incoming calls as available from the call (Caller ID) and from numbers stored in the contact list.

6.11 Circuit Management

6.11.1 Coverage Overlap Muting. The system shall be configurable to mute received audio from RFFs or VTS remote sites whose receive coverage area overlaps with the transmit coverage area of a transmitting RFF. Muting shall be static (pre-defined in a table accessible to the system administrator).

6.11.2 Network Latency Compensation. Contractor shall provide information on how the proposed system can be configured to compensate for fixed network latency (latency increases when RFFs lose landline connections and switch to back up VSAT network connections) between the RFFs and the operator consoles in order to minimize echoes when calls are received or transmitted by two or more RFFs.

6.11.3 Transmit Groups. The system shall allow the operator to configure transmit groups in order to transmit from multiple RFFs at once, up to all RFFs assigned to the operator console.

6.11.4 Patches. The system shall allow the operator to configure patched circuits between two or more radios at geographically separated RFFs, between two or more radios on different frequencies, and between one or more radios and a telephone line.

6.11.5 Volume Control. The system shall allow the operator to set the volume on each speaker, telephone, and intercom circuit.

6.12 Automatic Broadcast Notice to Mariners

The system shall provide the ability for an operator to pre-record broadcast information and select the RFFs, radio frequency, times, and periodicity to automatically transmit the message.

Attachment 2 - PWS 20

6.12.1 Text to Audio. The system shall provide the ability to enter an automated broadcast message as text and convert the text to audio for broadcasting.

6.12.2 Automated Message Preview. The system shall provide the ability to play back an automated broadcast notice prior to finalizing the automated transmission.

6.12.3 Automated Transmission. The system shall transmit the automated broadcast notice to mariners without impacting on-going distress communications.

6.13 Mean Time Between Failure (MTBF)

Major Assemblies of the Radio Control System shall meet the following MTBF requirements to ensure high system availability. An explanation of the origin of MTBF hours provided by Contractors (based on existing systems or calculated) shall be provided in the proposal. Numbers based on existing systems will be rated higher than calculated values. Note that the Radio Subsystem network, power, and climate control will be provided by the Coast Guard.

6.13.1 Sector Operator Consoles. Sector Operator Consoles shall provide an MTBF of >= 40,000 hours.

6.13.2 Station Operator Consoles. Station Operator Consoles shall provide an MTBF of >= 40,000 hours.

6.13.3 Radio/Console Control and Audio Route/Record/Replay System. The Radio/Console Control and Audio Route/Record/Replay System shall provide an MTBF of >= 25,000 hours.

6.13.4 Remote Monitoring System. Remote Monitoring System assemblies at VTS and R21 remote sites shall provide an MTBF of >=25,000 hours. Remote Monitoring System assemblies at Sectors shall provide an MTBF of >=40,000 hours. Note: Remote monitoring at sectors shall be considered available if displayed on at least one operator console assembly.

7.0 CONTRACTOR PERSONNEL

7.1 QUALIFIED PERSONNEL

The Contractor shall provide qualified personnel to perform all requirements specified in this

PWS.

7.2 KEY PERSONNEL

7.2.1 The Contractor shall designate a Project Manager and a System Engineer as key personnel.

The requirements of HSAR Clause 3052.215-70 shall be met before removing or replacing any key personnel.

7.2.2 Project Manager - The Project Manager shall be a single point of contact for the Contracting Officer and the Contracting Officer’s Representative (COR) and shall monitor the progress of the tasks and make adjustments as necessary to ensure the successful completion of

Attachment 2 - PWS 21 the project. The contractor shall designate an alternate to function as the Project Manager when the Project Manager is unavailable. Minimum experience requirements for both are as follows:

• At least 6 years of experience on radio communications projects.

• Meeting facilitation skills.

• Technical writing skills.

• Microsoft Office skills.

7.2.3 System Engineer - The System Engineer shall be responsible for all technical aspects of the project. Minimum experience/education requirements are as follows:

• A Bachelor’s degree in Engineering (ABET-accredited academic institution).

• At least 5 years of experience on radio communications projects.

• Meeting facilitation skills.

• Technical writing skills.

• Microsoft Office skills.

8.0 GOVERNMENT FURNISHED RESOURCES, EQUIPMENT, AND INFORMATION

8.1 Two (2) ICOM Eclipse 2 VHF base stations (156-174 MHz) with Ethernet interface, transmitter, power amplifier, receiver, preselector, documentation, and programming software, plus ancillary hardware for a 19-inch rack installation will…