Attachment I PWS.pdf

70Z079-22-R-ISD30485

IDIQ PERFORMANCE WORK STATEMENT

FOR

U.S. Coast Guard Small Cutter Connectivity Ku-Band

1.0 GENERAL

1.1 SCOPE

The purpose of this Indefinite Delivery, Indefinite Quantity (IDIQ) contract is to obtain Small Cutter Connectivity (SCC) Ku-Band service, warranty, hardware, and support for USCG Small Cutters, Deployable Contingency Communication System (DCCS) kits, Rescue 21 Remote Fixed Facility (RFF) connectivity backups, and lab mockups utilizing KVH V7-HTS Ku-Band systems. This will provide standard Ku-Band equipment suites and service for the platforms described. The Coast Guard intends to use this Ku-Band service for remote connectivity to the Coast Guard’s data network, CGOne, for mission essential applications.

1.2 APPLICABLE DOCUMENTS

1.3.1 Compliance Documents

The following documents, or the most current revision if updated, provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this contract:

DHS MD 11042.1, Safeguarding Sensitive but Unclassified (For Official Use Only) Information

DHS Direct ive 140-01, Revision 02, Information Technology Security Program

DHS 4300A, Sensitive Systems Policy, Version 13.1

DHS 4300A, Sensitive Systems Policy Handbook, Version 12.0

DHS 4300B, National Security Systems Policy, Version 10.0

DHS Form 11000-6, Non-disclosure agreement.

DHS Directive 139-05 Office of Accessible Systems and Technology

FIPS 140-2 Security Requirements for Cryptographic Modules FIPS 197 Advanced Encryption Standard (AES) 256-bit encryption compliant.

Internet Protocol v6 (IPv6)

Homeland Security (HLS) Enterprise Architecture (EA). NOTE: THIS PUBLICATION

WILL NOT BE PROVIDED TO OFFERORS. IT WILL BE PROVIDED TO THE

WINNING CONTRACTOR POST AWARD.

HLS EA Technical Reference Model (TRM) Standards and Products Profile Safeguarding of Sensitive Information (MAR 2015) Information Technology Security Awareness and Privacy Training (MAR 2015) 3052.204-71, Contractor Employee Access (SEP 2012) COMDTINST 5500.13F USCG Cybersecurity Manual (31 JAN 2020)

NOTE: The Contractor can obtain these documents by contacting the servicing Acquisitions Office and can be provided the updated versions as they are released.

2.0 SPECIFIC REQUIREMENTS/TASKS

2.1 TASK ONE. HARDWARE PURCHASE & REPLACEMENT REQUIREMENTS:

2.1.1 Hardware Requirements.

The Contractor shall provide the following SCC V7-HTS components:

2.1.1.1 KVH V7-HTS system:

All applicable cabling, mounts, KVH TracPhone V7-HTS satellite antennas (P/N: 02-1925-CG or 02-1925-01NL), InnoMedia Multimedia Terminal Adaptor (MTA) XT 6328-2Re (P/N 19-0504), Integrated CommBox Modems (P/N: 02-2204-02), and additional proprietary system components necessary for dual and single antenna SCC KVH V7-HTS system installations.

Additionally, for any hardware and/or systems that are not covered under warranty (see Section 2.5), the Contractor shall provide an option for purchase such additional hardware and /or systems, in order to fulfill USCG needs for additional installs or replacement systems that may arise.

2.1.2 Manuals.

Each V7-HTS Ku-Band system purchased shall include one copy of the installation and operation manuals in hard copy format and a separate copy in electronic (CD/DVD) format.

2.1.3 Equipment Delivery

The Contractor shall ship a fully functioning system to each location specified by the Government in delivery orders placed under this IDIQ. Shipments shall be anywhere within the U.S., including Alaska and Hawaii, as well as the territories of Guam and Puerto Rico.

Additional systems may be required to be delivered to FPO/APO addresses as operational needs dictate.

The Contractor shall be capable of shipping equipment within 24-hours of receipt of an order and shall ship equipment via overnight delivery when so specified in the delivery order.

The Coast Guard will store each system in a climate-controlled facility if it will not be installed immediately.

2.2 TASK TWO. NETWORK BACKHAUL REQUIREMENTS:

2.2.1 End-to-End Network Specifications and Performance Requirements.

The Contractor shall provide an end-to-end solution that meets the minimum specifications outlined in subtasks 2.2.2 – 2.2.7, including terrestrial network segment capabilities, Contractor Furnished Equipment (CFE) to be installed at the designated USCG Points of Presence (POP), availability, and network backhaul.

2.2.2 Network Backhaul Requirement.

The contractor shall deliver terrestrial segment capabilities compatible with the space segments and commercial teleports. The Contractor shall provide all equipment and services at the commercial teleports for up and down linking the USCG end-user terminals, connecting to the Contractor-furnished terrestrial infrastructure, and transmitting and receiving each circuit to the appropriate USCG POPs referenced in PWS section 2.2.4, within 90 days of contract award. The Contractor shall provide all equipment and services to implement an end-to-end solution, with the exception of GFE end-user terminals.

2.2.3 CGONE Network Access.

The Contractor shall establish access to the USCG enterprise Internet Protocol (IP) network CGONE at the USCG POPs. The Contractor shall ensure airtime plans provided/or activated are compatible with the USCG service requirements. The Contractor shall deliver MPLS backhaul to Ethernet handoff at each USCG POP. The Contractor shall provide a list of all CFE to be installed at USCG POPs and identify how much rack space (rack units (RUs)) shall be required to house the CFE. The CFE shall be limited to a total of two rack units (2 RU) at each of the POPs. The CFE power shall be limited to a total of 4 Amps at 110 VAC at each of the POPs. All CFE shall be managed by the Contractor. Management shall include periodic vulnerability scanning, patching, and maintenance/configuration updates as required by COMDTINST 5500.13F USCG Cybersecurity Manual. The USCG will be responsible for physical security at USCG POPs.

The Contractor shall deliver the terrestrial network backhaul segment to the three USCG POPs outlined in this subtask. Contractor-provided circuits and CFE installed at the POPs shall be capable of handling the full aggregate network load (data throughput, M&C traffic, and data management overhead) for a minimum of 133 simultaneous end user circuits. The backhaul infrastructure must provide cryptographic mechanisms to prevent unauthorized disclosure of information and detect changes to information during transmission.

2.2.3.1 The three USCG POPs are:

USCG Command, Control, Communications, Computers, Cyber, and Intelligence Service Center (C5ISC) located at Building 17A at 7323 Telegraph Road, Alexandria, Virginia, 20598.

USCG C5ISC Kearneysville located at the Main Building at 408 Coast Guard Drive, Kearneysville, WV, 25430.

USCG Base Alameda located at Building 5 at Coast Guard Island, Alameda, CA, 94501.

2.2.4 Network Design

The USCG will provide the IP Scheme for all cutter LANs and USCG POP meet-me-points during the combined IDIQ and TO Post-Award Conference. The Contractor shall provide the IP Scheme for the CFE segment. The Contractor shall maintain a single static IP for each USCG end-user terminal regardless of routing within the Contractor’s network.

2.2.5 Terrestrial Network Availability

The Contractor shall meet the minimum link availability of 99.99% for network links (i.e.

terrestrial backhaul segments). The terrestrial network includes the connections from the CFE network equipment at each commercial teleport to the USCG (any two of the three USCG POPs). The availability shall be calculated daily and averaged over a 30-day period for each terrestrial teleport. The vendor shall calculate and provide an availability figure in the monthly report for each commercial teleport, for the previous 30 calendar days. The contractor shall calculate the terrestrial network availability figure using the formula: End-to-

End Ao = Uptime for connectivity between the teleport and at least two of the USCG POPs/uptime + downtime. This figure shall be provided for each teleport and the 99.99% requirement applies to each teleport individually. Failure to maintain 99.99% availability from a single teleport will be considered failure to meet this performance objective.

2.2.6 End-to-End Operational Availability

The end-to-end operational availability (Ao) for each circuit shall be greater than or equal to 98.5%. The end-to-end performance of all circuits shall be calculated daily and averaged over a 30-day period to determine the overall satellite network availability. The vendor shall calculate and provide an availability figure in the monthly report for the previous 30 calendar days. The Contractor shall calculate operational availability using the formula: End-to-End Ao = Uptime/(Uptime+Downtime).

2.3 TASK THREE. NETWORK OPERATIONS SECURITY CENTER (NOSC)

REQUIREMENTS:

2.3.1 The Contractor shall provide NOSC staffing for each of these services, 24 hours a day, 7 days a week, 365 days per year.

2.3.2 The Contractor shall maintain a log of personnel with access to DHS/USCG sensitive information and servicing NOSC personnel. The NOSC shall be limited to need to know personnel only.

2.3.3 The Contractor shall mask Coast Guard cutter position information from being viewable at the NOSC. Contractor shall seek permission to unmask the cutter position only for troubleshooting efforts.

2.3.4 The Contractor shall actively monitor Coast Guard Ku-Band connections and correct problems expeditiously and have the ability to support, diagnose and troubleshoot each terminal to support troubleshooting efforts and have access to terminal manufacturers for advanced hardware support which can provide immediate information regarding outages and failures.

2.3.5 The Contractor shall reply to e-mail requests for assistance from the Coast Guard technicians within 24 to 48 hours.

2.3.6 The Contractor shall maintain a database of Ku-Band equipment installed on Coast Guard cutters and provide access to the authorized Coast Guard representatives upon request.

2.3.7 The Contractor shall replace equipment identified by their technicians as faulty within 24-hours if it is within the warranty requirements as specified in Section 2.5 of this PWS.

2.3.8 The Contractor NOSC is responsible for all terminal communications.

2.3.9 The Contractor NOSC must adhere to the security requirements as outlined in Section 4.1 of this PWS.

2.3.10 The Contractor shall also provide an e-mail address/distribution list to which USCG personnel can e-mail questions or requests for assistance. The telephone line and e-mail address shall be for USCG calls/messages only.

2.3.11 Telephone calls for Contractor support will come from a peer USCG Tier-1 troubleshooter who may initiate a conference call with a Cutter and mobile asset technician to initiate troubleshooting efforts.

2.3.12 The NOSC telephone operator response shall be immediate upon receipt of a telephone call from the USCG. The NOSC shall provide the USCG with email acknowledgement of the telephone call within 15 minutes of receipt of call.

2.3.13 The NOSC shall provide the Government with pro-active monitoring to ensure the reliable cutter communications and lead troubleshooting of all SCC Ku-Band connections for the USCG.

2.3.14 The Contractor NOSC shall answer the direct line telephone and any email as described in this section.

2.3.15 The Contractor NOSC shall have the ability to view, monitor, record, and have access to network management services which can provide immediate information regarding outages and failures in order to troubleshoot the entire RF/IP path from the cutter terminal to the USCG POP.

2.3.16 The Contractor shall provide 48 hours of advance notice to the Government prior to performing maintenance operations of any kind affecting USCG connectivity. Maintenance periods shall not exceed one hour and will count against availability.

2.3.17 The Contractor NOSC must be available within 150 days of contract award. Date of availability shall be specified within the Project Plan.

2.4 TASK FOUR. ONLINE PORTAL REQUIREMENTS:

The Contractor shall provide a portal accessible to the Contracting Officer’s Representative (COR) and USCG Technical Team via Hyper Text Transfer Protocol with Secure Sockets Layer (HTTPS) that must be accessible through a Virtual Private Network using two factor authentication with Contractor provided user access management based on user hierarchy provided by the USCG. The portal must provide at a minimum: monthly reports, near real time usage reports by individual asset with the ability to run reports over a specified period of time, and near real time reports of system errors, faults, and outages. Account management and monitoring for assets that is searchable and able to provide near real time information to include: bandwidth plan assignment (uplink/downlink speed), online/offline status, restrictions, faults/errors, and IP assignment. This task shall be achieved and made available within 150 days of award, and date of availability shall be specified within the Project Plan.

2.5 TASK FIVE. WARRANTY SERVICE REQUIREMENTS:

2.5.1 The Contractor shall warrant all Ku-Band equipment purchased under this contract for a period of two years after acceptance by the Government. The Contractor shall provide a warranty plan suitable for distribution with each asset purchased which details the required steps to obtain warranty services. Task Five (5) shall be achieved and made available within 150 days of award, and date of availability shall be specified within the Project Plan.

2.5.2 Cost of shipping assets under warranty to/from the Contractor shall be borne by the Contractor.

2.5.3 Under this warranty the Contractor shall replace any defective V7-HTS Ku-Band equipment component at no cost to the Government. The Contractor shall ship replacement equipment within 24 hours of a warranty claim via overnight delivery.

2.5.4 The warranty period shall start upon acceptance by the Government at the installation site (i.e. cutter). Systems shall be considered accepted by the Government upon satisfactory installation and registration with the supporting hub or 30 days from government receipt of the equipment, whichever is sooner.

2.5.5 In the event of obvious shipping damage, the USCG may refuse delivery. The Contractor shall provide a replacement system within 24 hours and provide instructions on shipping the damaged system back to the Contractor’s facility. The warranty period shall not start until the replacement system is received and accepted.

2.5.6 In the event the Ku-Band equipment fails at installation (i.e. out of the box failures) the Contractor shall provide a replacement system/component to the cutter within 24 hours of being notified of the failure by the Government.

2.5.7 The Contractor shall offer extended warranty coverage for V7-HTS Ku-band equipment currently installed and in use by the Government. Extended warranty coverage shall be for a complete shipboard equipment suite (all above and below-deck equipment).

The Government shall have the option of purchasing extended warranty coverage for a partial year at the rate of 1/365th of the annual cost for each day of warranty service. The partial year option is only available to cutters to bring them in line with the annual renewal period.

2.6 TASK SIX. SATELLITE AIRTIME REQUIREMENTS:

2.6.1 Data Connectivity.

The V7-HTS Ku-Band systems shall enable cutters, DCCS kits, Rescue 21 RFFs, and mock-ups to transmit and receive information to/from shore-based Internet Protocol (IP) networks remotely via airtime plans outlined in Section 2.6.2. The Contractor shall ensure transition of all cutters, DCCS kits, Rescue 21 RFFs, and mock-ups within 120 days of contract award and date of completion shall be specified within the Project Plan.

2.6.1.1 All cutters, RFFs, mock-ups (excluding those in Bahrain) shall be transitioned, tested, and validated. Cutters and mock-ups in Bahrain shall be scheduled separately as they have unique operational missions and require coordination during the workday in Bahrain. There are six operational cutters and one lab system mock-up in Bahrain.

2.6.1.2 DCCS Kits shall be transitioned, tested, and validated. Note- DCCS kits are not continuously connected to the satellite network. The Contractor shall coordinate with the USCG at least 5 business days in advance to schedule a date/time for these system to be connected to the satellite service (for downloading files and/or testing purposes).

2.6.2 Satellite Airtime Plans:

2.6.2.1 The Contractor shall provide V7-HTS tiered broadband system pre-paid unlimited airtime plans with no Fair Access Policy (FAP) capable of the following download / upload rates at a minimum that are compatible with the USCG’s existing KVH TracPhone V7-HTS satellite antennas (P/N: 02-1925-CG), Integrated CommBox Modems (P/N: 02-2204-02):

Committed Information Rates (CIR):

256 Kbps/128 Kbps

512Kbps/256Kbps

1Mbps/512Kbps

2Mbps/512Kbps

4Mbps/1Mbps

8Mbps/2Mbps

10Mbps/3Mbps

Note: See Vendor’s “IDIQ Established Rates” for pricing information on these rates. The rates above are the minimum required download/upload rates required to be available on the V7-HTS system. The USCG may order service at some or all of these rates throughout the life of the contract.

2.6.2.2 Airtime shall be priced for a minimum period of one year (365 days) for each configuration specified in section 2.1.1. The Contractor shall also allow partial-year airtime purchases. These shall be priced as a pro-rated amount at the rate of 1/365th of the annual cost for each day of airtime service. The partial year option is only available to ships to bring them in line with the annual renewal period or to purchase airtime for DCCS kits in accordance with paragraph 2.6.2.5.

2.6.2.3 The Contractor shall provide a Metered Rate airtime that allows a Deployable Contingency Communication System (DCCS) to transfer up to 50MB/month at up to 2Mbps X 1 Mbps (download/upload) and use the TracPhone Enhanced Voice Service with two unique VOIP telephone lines/numbers for each kit. The USCG intends to purchase this plan annually for each DCCS system.

2.6.2.4 The USCG COR shall be able to direct the contractor to transfer individual DCCS systems from the Metered Rate plan to the fixed rate plan, and vice versa. The contractor shall make such a transition effective within 24-hours of receiving that direction. The Contractor may impose a nominal service-change fee for each transition. If such a fee is imposed, the USCG intends to pre-pay a nominal quantity of service change fees in advance, at the beginning of each fiscal year. The USCG also intends to pre-purchase a nominal quantity (days) of Fixed Rate airtime at the beginning of each fiscal year. The Coast Guard intends to leave the DCCS Systems on the Metered Rate plan so they can be tested monthly to ensure the hardware is operating properly. The Coast Guard intends to temporarily change one or more DCCS systems to a Fixed Rate plan when a system or systems are deployed for contingency use, for example in response to a natural disaster.

2.6.2.5 The COR shall have the authority to direct the Contractor to transition one or more DCCSs from the Metered Rate to the Fixed Rate at any time throughout the year. There shall be no limit to the number of times or systems that can be transitioned and no minimum or maximum number of days that a system can remain on the Fixed Rate plan. The COR will notify the Contractor by phone, followed by electronic mail confirmation, when requesting a DCCS be transitioned from the Metered Rate plan to a Fixed Rate plan (or vice versa). The notification will include the specific DCCS to be transitioned, the specific Fixed Rate plan to be used, and the date Fixed Rate service is to begin or end. The Contractor shall be capable of transitioning between plans within 24 hours of COR notification.

2.6.3 Satellite Coverage:

2.6.3.1 The Coast Guard requires 24x7x365 V7-HTS Ku-Band satellite coverage in the areas in Attachment III V7-HTS Coverage Area, provided by the Vendor upon award. Areas in Attachment III are as follows: Red areas are the required coverage areas, Yellow/Green are the desired areas. The only inland coverage areas required are continental US, Alaska, Hawaii, Guam, Puerto Rico, the Caribbean Islands, throughout all of the Great Lakes, and the Saint Lawrence Seaway and Bahrain; no other inland areas shall be considered as part of the required coverage areas. Any changes in coverage, price, or availability will require prior notification to the Government (at a minimum, 30 days).

2.6.3.2 Any loss of coverage and/or availability will result in a credit to the Government for all affected pre-paid airtime plans operating, or scheduled to operate, in the affected area(s) equivalent to the cost that would be incurred for the duration of the affect

2.6.3.3 Frequency Clearances (FC) and Approvals.

The Contractor shall support Host Nation Agreement (HNA) efforts in obtaining international approvals for radio spectrum operations under this IDIQ in foreign nations. The Contractor will provide international services under each task order as scheduled with the full approval of each affected host nation. Typical services may include, but are not limited to host nation approvals, landing rights, operating agreements, site licenses, and frequency clearances. If host nation support becomes necessary during the life of each task order, then the Government will add the appropriate Contract Line Item Numbers (CLINs) to the order at the necessary time and services will invoice at the pass-through rate. No profit or fee shall be authorized for HNAs. The Contractor may be required to provide HNAs for any nation covered within the limits defined in the coverage area, as needed by the user. If the permanent license requires time for processing, then the Contractor shall provide a temporary FC license to meet service start date requirements. FC requests are for the maximum time period allowable by the host nation, up to the life of the contract. The Contractor shall provide the Government with copies of regulatory licenses and approvals obtained to operate and use the spectrum for countries within the required service region.

2.6.3.4 Electro Magnetic Interference (EMI)/Radio Frequency Interference (RFI) Identification, Characterization, and Geo-location.

The Contractor shall provide legible EMI/RFI identification, characterization, and geo-location. Such services include the ability to identify and characterize sub-carrier EMI/RFI being transmitted underneath an authorized carrier, and the ability to geo-locate the source of any and all EMI/RFI. The Contractor shall also immediately report the existence of EMI/RFI to the COR and USCG Operations Staff (TIS-SG- WAN_Cutter_Connectivity@uscg.mil , CGCYBER-NOSC-EOC-Networks@uscg.mil , CGCYBER-SMB-NOSC-EOC-WatchSupervisor@uscg.mil ). Additionally, the Contractor mailto:TIS-SG-WAN_Cutter_Connectivity@uscg.mil mailto:TIS-SG-WAN_Cutter_Connectivity@uscg.mil mailto:CGCYBER-NOSC-EOC-Networks@uscg.mil mailto:CGCYBER-SMB-NOSC-EOC-WatchSupervisor@uscg.mil shall make best efforts to geo-locate the source of the interference and report findings. The Contractor shall support Government exercises focused on the resolution of EMI/RFI interference scenarios as directed, no more frequently than quarterly. The Contractor (and/or subcontractors) shall provide initial acknowledgement of EMI/RFI to the COR by telephone within 10 minutes. Best effort geo-location of the interfering signal source, spectrum analyzer screenshots, and characterization shall be provided within 30 minutes of Contractor EMI/RFI detection or Government request if events are detected by the Government. The Contractor shall provide updates of such information to the Government upon change, upon request, or every two hours from initial report, until incident resolution. If secure email and/or voice communications are not available, the Contractor (and subcontractors) shall use a mutually agreed upon media and voice communications capability capable of protecting sensitive but unclassified data. Upon incident resolution, the Contractor shall provide a Summary of Action Report, summarizing the incident, corrective actions taken, and incident resolution, to the COR.

2.7 TASK SEVEN. VOICE-OVER-INTERNET-PROTOCOL (VOIP) REQUIREMENTS:

2.7.1 The SCC and DCCS systems shall provide the ability to place voice calls from any VOIP enabled phone that is connected to the MTA, to any phone on the Public-Switched Telephone Network (PSTN), or ship-to-ship calls to other V7-HTS equipped Coast Guard assets, while underway.

2.7.2 VOIP calls to CONUS, Puerto Rico, and Hawaii shall incur no additional charge beyond the standard airtime charges.

2.7.3 Any additional VOIP call charges (e.g. OCONUS calls) shall be charged separately from the VOIP service charge.

2.7.4 VOIP calls from cutters to locations other than CONUS, Puerto Rico and Hawaii shall be billed at the rate(s) established at the award of this contract. This service shall be billed monthly. Invoices shall include an itemized list of calls showing the following information for each call billed:

The originating cutter’s name and/or phone number

The phone number called

The date & time the call originated

The duration of the call

The per-minute rate

The total cost of the call

2.7.5 The USCG will pre-pay a not-to-exceed amount for long-distance charges & funds will be released to the Contractor upon invoice approval. The Contractor shall alert the COR and contracting officer when funding in this pre-paid CLIN falls below the amount projected to be billed for the following three months.

2.7.6 The SCC and DCCS systems shall be able to process up to two (2) VOIP calls simultaneously with data activity; these calls shall not reduce the bandwidth available for data communications.

2.7.7 Task Seven (7) shall be achieved and made available within 150 days of award, and date of availability shall be specified within the Project Plan.

3.0 CONTRACTOR PERSONNEL

3.1 Qualified Personnel

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

3.2 Employee Identification.

Contractor employees visiting USCG facilities shall wear an identification badge that, at minimum, displays the Contractor name, the employee’s photo, name, clearance-level and badge expiration date. Visiting Contractor employees shall comply with all USCG security requirements. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent, and display all identification and visitor badges in plain view above the waist at all times.

3.2.1 Contractor employees visiting Government facilities shall wear an identification badge that, at a minimum, displays the Contractor name, the employee’s photo, name, clearance-level and badge expiration date. Visiting Contractor employees shall comply with all Government escort rules and requirements. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent and display all identification and visitor badges in plain view above the waist at all times.

3.2.2 Contractor employees working on-site at Government facilities shall wear a Government issued identification badge. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent (in meetings, when answering Government telephones, in e-mail messages, etc.) and display the Government issued badge in plain view above the waist at all times.

3.3 Employee Conduct.

The Contractor’s employees shall comply with all applicable USCG regulations, policies and procedures (e.g., fire, safety, sanitation, environmental protection, security, “off limits” areas, wearing of parts of military uniforms, and possession of weapons) when visiting or working at USCG facilities. The Contractor shall ensure Contractor employees present a professional appearance at all times and that their conduct shall not reflect discredit on the United States, the Department of Homeland Security, or the USCG.

3.4 Removing Employees for Misconduct or Security Reasons.

The Government may, at its sole discretion (via the Contracting Officer), direct the Contractor to remove any Contractor employee from DHS facilities for misconduct or security reasons. Removal does not relieve the Contractor of the responsibility to continue providing the services required under the contract. The Contracting Officer will provide the Contractor with a written explanation to support any request to remove an employee.

3.5 Continuity of Support.

The Contractor shall ensure that the contractually required level of support for this requirement is maintained at all times. The Contractor shall ensure that all contract support personnel are present for all hours of the workday. If for any reason the Contractor staffing levels are not maintained due to vacation, leave, appointments, etc., and replacement personnel will not be provided, the Contractor shall provide e-mail notification to the Contracting Officer’s Representative (COR) prior to employee absence. Otherwise, the

Contractor shall provide a fully qualified replacement.

4.0 OTHER APPLICABLE CONDITIONS

4.1 SECURITY

4.1.1 Department of Homeland (DHS) Security Directives. All hardware, software, and services provided under this contract shall be compliant with the following DHS directives:

DHS Directive 140-01, Revision 02, Information Technology Security Program

DHS 4300A, Sensitive Systems Policy Handbook, Version 13.1

DHS Management Directive 11042.1, Safeguarding Sensitive But Unclassified (For Official Use Only) Information

Information Technology Security Awareness and Privacy Training (MAR 2015)

3052.204-71, Contractor Employee Access (SEP 2012)

4.1.2 Federal Information Processing Standards (FIPS) Publications. All hardware and software interfaces provided under this contract shall compliant with the following requirement:

Further all equipment provided under this contract shall be Internet Protocol v6 (IPv6) capable.

4.1.3 IT Security Plan. The Contractor shall provide, implement, and maintain an IT Security Plan. This plan shall describe the processes and procedures the Contractor shall follow to ensure appropriate security of IT resources developed, processed, or used under this contract. The plan shall also document the approach for CFE management, including the resources and remote access requirements. The plan shall also describe contingency operations/considerations for delivery of these services.

4.1.3.1 Within 30 days after contract award, the Contractor shall submit for approval their IT Security Plan. The IT Security Plan, as approved by the Contracting Officer, shall be incorporated into the contract as a compliance document.

4.1.3.2 The Contractor’s IT Security Plan shall meet or exceed Federal laws, regulations, or instruction including, but are not limited to, references in the above Sections 1.31 & 4.1.1.

4.1.3.3 The security plan shall specifically include instructions regarding handling and protecting law enforcement sensitive information at the Contractor’s proposed sites (including any information stored, processed, or transmitted using the Contractor’s computer systems), and the secure management, operation, maintenance, programming, and system administration of computer systems, networks, and telecommunications systems.

4.1.4 Facility Security Plan. Within 30 days of contract award the Contractor shall provide a Facility Security Plan for each of the MPLS Teleport(s) and/or Meet-Me point(s) proposed by the Contractor, which shall be consistent with and further detail the approach contained in the offeror's proposal. This plan shall meet or exceed the “Relevant Controls” in the most recent version of “DHS Sensitive Systems Handbooks 4300A, section 4.2.1”.

4.1.5 Protection of Unclassified Department of Defense (DoD) Data. The Contractor shall protect unclassified DoD data from unauthorized access or disclosure in accordance with DoDI 8582.01, “Security of Unclassified Information on Non-DoD Information Systems,” (http://www.dtic.mil/whs/directives/corres/pdf/858201p.pdf) and the program’s Security Classification Guide.

4.1.6 Security Review. The USCG may elect to conduct periodic reviews to ensure that the security requirements contained in this contract are being implemented and enforced.

The Contractor shall afford DHS, including the organization of the DHS Office of the Chief Information Officer, the Office of the Inspector General, authorized COR, and other USCG oversight organizations, access to the Contractor’s facilities, installations, operations, documentation, databases, and personnel used in the performance of this contract. The Contractor will contact the DHS Chief Information Security Officer to coordinate and participate in the review and inspection activity of USCG oversight organizations external to the DHS. Access shall be provided to the extent necessary for the USCG to carry out a program of inspection, investigation, and audit to safeguard against threats and hazards to the integrity, availability, and confidentiality of DHS data or the function of computer systems operated on behalf of DHS and to preserve evidence of computer crime.

4.2 PLACE OF PERFORMANCE.

The primary place(s) of performance will be the Contractor’s facilities and USCG facilities located at the following:

USCG Command, Control, Communications, Computers, Cyber, and Intelligence Service Center (C5ISC) located at Building 17A at 7323 Telegraph Road, Alexandria, Virginia, 20598.

USCG C5ISC Kearneysville located at the Main Building at 408 Coast Guard Drive, Kearneysville, WV, 25430.

USCG Base Alameda located at Building 5 at Coast Guard Island, Alameda, CA, 94501.

4.3 HOURS OF OPERATION

Contractor employees shall generally perform all work between the hours of 0800 and 1600 EST, Monday through Friday (except Federal holidays). However, there may be occasions when Contractor employees shall be required to work other than normal business hours, including weekends and holidays, to fulfill requirements under this PWS.

4.4 TRAVEL.

Contractor travel shall not be required for this requirement.

4.5 POST-AWARD CONFERENCE

The Contractor shall attend a virtual Post-Award Conference with the Contracting Officer and the COR not later than 10 business days after the date of contract award. The purpose of the Post-Award Conference, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this task order. The Post-Award Conference will be held via teleconference.

4.6 PROJECT PLAN

The Contractor shall provide a final draft Project Plan at the Post-Award Conference for the http://www.dtic.mil/whs/directives/corres/pdf/858201p.pdf

Government. The plan, at a minimum, shall include: (a) list of work to be performed; (b) project schedule; (c) description of intended results; (d) role of key personnel, if applicable and (f) how quality of service (project) will be maintained throughout life of contract. The Government will provide comments on that Project Plan within 15 Days of receipt. The contractor shall provide a final Project Plan within 15 days of receipt of the Government’s comments.

4.6.1 Transition Timeline. Within the project schedule of the Project Plan, the Contractor shall include a detailed timeline of the transition of all services. This timeline shall address the below milestones at a minimum, with start and end date(s) for each. . If the Contractor adds milestones, the timeline shall provide a brief description of each additional milestone included along with the start and finish dates as applicable. g. The minimum required milestones are as follows:

Backhaul service available (one milestone for each link proposed)

Backhaul service connected & Offeror’s equipment installed in USCG POPs (one milestone for each link proposed)

Backhaul service tested end-to-end from Offeror’s location to USCG POPs (one milestone for each link proposed)

Transition of USCG C5ISC Alexandria Lab system (mock-up) to the new service, complete & tested.

Start of cutter & other operational USCG system transitions.

o Transition and testing/validation of in-port cutters (start & finish dates) o Transition and testing/validation of underway cutters excluding cutters in Bahrain (start & finish dates) o Transition and testing/validate of cutters and lab system (mock-up) in

Bahrain (start & finish dates).

o Transition and testing/validation of Guam Backup services (start & finish dates) Transition and testing/validation of DCCS Kits (start & finish dates).

4.7 BUSINESS CONTINUITY PLAN

The Contractor shall prepare and submit a Business Continuity Plan (BCP) to the Government. The BCP Plan shall be due 15 business days after the date of award and will be updated on an annual basis. The BCP shall document Contractor plans and procedures to maintain support during an emergency, including natural disasters and acts of terrorism.

The BCP, at a minimum, shall include the following:

A description of the Contractor’s emergency management procedures and policy

A description of how the Contractor will account for their employees during an emergency

How the Contractor will communicate with the Government during emergencies

A list of primary and alternate Contractor points of contact, each with primary and alternate:

o Telephone numbers o E-mail addresses

4.7.1 The BCP shall be activated immediately after determining that an emergency has occurred, shall be operational within 24 hours of activation or as directed by the

Government, and shall be sustainable until the emergency situation is resolved and normal conditions are restored or the contract is terminated, whichever comes first. In case of a life threatening emergency, the COR shall immediately make contact with the Contractor Project Manager to ascertain the status of any Contractor personnel who were located in Government controlled space affected by the emergency. When any disruption of normal, daily operations occur, the Contractor Project Manager and the COR shall promptly open an effective means of communication and verify:

Key points of contact (Government and Contractor)

Temporary work locations (alternate office spaces, telework, virtual offices, etc.)

Means of communication available under the circumstances (e.g. email, webmail, telephone, FAX, courier, etc.)

Essential Contractor work products expected to be continued, by priority

4.7.2 The Government and Contractor Project Manager shall make use of the resources and tools available to continue contracted functions to the maximum extent possible under emergency circumstances. Contractors shall obtain approval from the Contracting Officer prior to incurring costs over and above those allowed for under the terms of this contract.

Regardless of contract type, and of work location, Contractors performing work in support of authorized tasks within the scope of their contract shall charge those hours accurately in accordance with the terms of this contract.

4.8 MONTHLY REPORTS

The Project Manager shall provide a monthly report to the Contracting Officer and COR via electronic mail. This report shall include a summary of all Contractor work performed, an assessment of technical progress, schedule status, and any Contractor concerns or recommendations for the previous reporting period. The monthly report shall be delivered via electronic mail to the COR and any other Government representatives designated by the COR and shall include the following as a minimum:

A list of any maintenance activities planned for the next 90 days that could impact service, including the planned date and time, the expected duration, the expected impact and any action planned/required to mitigate the impact to service.

A list of any maintenance activities completed during the prior month and a description of the results and the impact to service.

A list of any network outages that occurred during the prior month, including the date(s) duration and cause (e.g. weather, planned maintenance, unplanned maintenance, etc.).

A calculation of the availability for each satellite, (network availability = (Total time) – (down time)/ (total time).

A list of any requests for support from USCG customers that were opened over the prior month, with a description of the issue and the resolution.

A list of any issues to be discussed during the upcoming monthly meeting (these may be raised by the Government or the Contractor).

A list of any outstanding invoices that have been submitted but not paid, including the invoice number and date submitted.

Terrestrial Network Availability for each teleport the previous month, calculated in accordance with PWS paragraph 2.2.5.

End-to-end Operational Availability for the previous month, calculated in accordance with PWS paragraph 2.2.6.

A table showing the dates/times of warranty claims received and hardware failures diagnosed with the corresponding shipping date for the replacement part(s). The contractor shall also make individual shipping documents available to the government upon request of the COR or contracting officer to substantiate the dates in the reports.

4.9 QUARTERLY STATUS MEETINGS

The Contractor shall coordinate and conduct a quarterly status meeting, starting one month following the Post-Award Conference. This meeting shall be held via teleconference. The agenda for this quarterly meeting is to review the monthly reports and to discuss upcoming or ongoing maintenance, changes and any/all contract related pending issues. The USCG may ask the Contractor address specific concerns or questions regarding Advanced Services Airtime during these meetings.

4.10 GENERAL REPORT REQUIREMENTS

The Contractor shall provide all document deliverables required by this contract electronically, in one of the following formats:

Microsoft Word

Microsoft Excel

Microsoft Power Point

Adobe Acrobat

4.11 COMMUNICATION

The Contractor shall be responsible for keeping the Contracting Officer and COR informed about issues pertaining to contract performance, including the status of deliverables, throughout the period of performance of this contract, and ensuring Contractor activities are aligned with the requirements stated in this PWS.

4.11.1 Fault Reporting.

For all services under this contract, the Contractor shall report fault information to the USCG Operations Staff (TIS-SG-WAN_Cutter_Connectivity@uscg.mil , CGCYBER-NOSC- EOC-Networks@uscg.mil , CGCYBER-SMB-NOSC-EOC-WatchSupervisor@uscg.mil ).

Fault information includes but is not limited to detection, identification, and isolation of faults; and initiation, tracking, and completion of corrective actions. The Contractor shall electronically report fault information with the associated signal parameters for out-of-tolerance alarms and carrier-related alarms via trouble tickets to the above addresses as well as provide a summary of fault trends and detailed statistics in its Monthly Status Report. The Contractor shall update trouble tickets a minimum of every two-calendar days for non-serious issues regardless of change in status, and daily for serious issues. Serious issues are those that affect service and cause interruptions or outages. Non-serious issues are those that cause no service interruption or outage, but hinder the ability to establish new service

4.12 INVOICING

The Contractor shall invoice monthly for all airtime related charges with the exception of warranty services, VOIP Overage NTE Value, DCCS Pre-Purchased Airtime, and DCCS Pre-Purchased Rate Change Fees which shall be invoiced annually. The Contractor shall send the USCG COR copies of the invoices for review prior to submission to the USCG mailto:TIS-SG-WAN_Cutter_Connectivity@uscg.mil mailto:CGCYBER-NOSC-EOC-Networks@uscg.mil mailto:CGCYBER-NOSC-EOC-Networks@uscg.mil mailto:CGCYBER-SMB-NOSC-EOC-WatchSupervisor@uscg.mil

FINCEN.

4.13 DATA RIGHTS.

All documentation, electronic data, processes and procedures and/or other forms of information generated by the Contractor in support of this work statement shall be considered Government property in accordance with FAR Clause 52.227-14 and shall be provided to the Government at the end of the performance period in a format accessible and usable by the Government.

4.14 PROTECTION OF INFORMATION.

Contractor access to sensitive information may be required under this contract. This may include sensitive information regarding Government networks (e.g. IP addresses, traffic routing, vulnerabilities), USCG vessel locations, access to systems that transmit Government information, or other information that, if disclosed, could have an adverse impact on the welfare or conduct of Government programs or operations essential to the national interest . Contractor employees shall safeguard USCG information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive but Unclassified (For Official Use Only) Information. Sensitive but Unclassified (SBU) includes information categorized by DHS or other USCG agencies as:

For Official Use Only (FOUO); Official Use Only (OUO); Sensitive Homeland Security Information (SHSI); Limited Official Use (LOU); Law Enforcement Sensitive (LES);

Safeguarding Information (SGI); Unclassified Controlled Nuclear Information (UCNI); and any other identifier used by other USCG agencies to categorize information as sensitive but unclassified. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a non-disclosure agreement (DHS Form 11000-6). The Contractor shall ensure employees safeguard this information when the new Controlled Unclassified Information (CUI) framework replaces the sensitive but unclassified (SBU) categorization. Contractor access to information protected under the Privacy Act is required under this PWS. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the law and Government policy and regulation.

4.15 SECTION 508 COMPLIANCE

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) (codified at 29 U.S.C. § 794d) requires that when Federal agencies develop, procure, maintain, or use information and communications technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public with disabilities must be afforded access to and use of information and data comparable to that of Federal employees and members of the public without disabilities.

All products, platforms and services delivered as part of this work statement that, by definition, are deemed ICT shall conform to the revised regulatory implementation of Section 508 Standards, which are located at 36 C.F.R. § 1194.1 & Appendix A, C & D, and available at https://www.gpo.gov/fdsys/pkg/CFR-2017-title36-vol3/pdf/CFR-2017-title36-vol3-part1194.pdf. In the revised regulation, ICT replaced the term electronic and information technology (EIT) used in the original 508 standards. ICT includes IT and other equipment.

Exceptions for this work statement have been determined by DHS and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the https://www.gpo.gov/fdsys/pkg/CFR-2017-title36-vol3/pdf/CFR-2017-title36-vol3-part1194.pdf https://www.gpo.gov/fdsys/pkg/CFR-2017-title36-vol3/pdf/CFR-2017-title36-vol3-part1194.pdf

Contracting Officer and a determination will be made according to DHS Directive 139-05, Office of Accessible Systems and Technology, dated November 12, 2018 and DHS Instruction 139-05-001, Managing the Accessible Systems and Technology Program, dated November 20, 2018, or any successor publication.

4.15.1 Section 508 Requirements for Technology Products

Section 508 Requirements for Technology Products: Reports

Applicable Exception: N/A Authorization #: N/A

Applicable Functional Performance Criteria: Does not apply

Applicable 508 requirements for electronic content features and components (including but not limited to Internet or Intranet website; Electronic documents; Electronic reports;

Electronic training materials): All requirements in E205 apply, including all WCAG 2.0 Level A and AA Success Criteria apply as specified in E205

Applicable 508 requirements for software features and components: Does not apply

Applicable 508 requirements for hardware features and components: Does not apply

Applicable 508 requirements for support services and documentation: All requirements in Chapter 6 apply

4.15.2 Section 508 Requirements for Technology Products: Satellite Terminals

Applicable Exception: ICT Functions Located in Maintenance and Monitoring Spaces Authorization #: EXC0001290

Applicable Functional Performance Criteria: Does not apply

Applicable 508 requirements for electronic content features and components: Does not apply

Applicable 508 requirements for software features and components: Does not apply

Applicable 508 requirements for hardware features and components: Does not apply

Applicable 508 requirements for support services and documentation requirements: Does not apply

4.15.3 Section 508 Deliverables

Section 508 Accessibility Conformance Reports: For each ICT item offered through this contract (including commercially available products, and solutions consisting of ICT that are developed or modified pursuant to this contract), the Offeror shall provide an Accessibility Conformance Report (ACR) to document conformance claims against the applicable Section 508 standards. The ACR shall be based on the Voluntary Product Accessibility Template Version 2.0 508 (or successor versions). The template can be found at https://www.itic.org/policy/accessibility/vpat. Each ACR shall be completed by following all of the instructions provided in the template, including an explanation of the validation method used as a basis for the conformance claims in the report.

4.16 TECHNOLOGY INSERTION

4.16.1…