ID05180024_AMDT_0001_020819.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

The purpose of this amendment 0001 is to delete in its entirety the cover page, Section C - Description/Specifications/ Statement of Work (SOW), Section J Attachment 7, and Section M - Evaluation Factors for Award included in the RFP issued on December 31, 2018, and replace them with the revised documents included in this amendment 0001.

General Services Administration FAS Contracting Division 230 S. Dearborn Street, Suite 3800 Chicago, IL 60604

See block 6

ID05180024

ID05180024

02/08/2019

12/31/2018

DEPARTMENT OF DEFENSE (DOD) INTELLIGENCE, SURVEILLANCE, AND

RECONNAISSANCE (ISR) SENSOR DATA BACKHAUL

A procurement by the

U.S. General Services Administration On behalf of

United States Special Operation Command (USSOCOM) Solicitation Number/GSA ITSS# ID05180024

This requirement is being solicited as a total small business set-aside NAICS 334290 - Other Communications Equipment Manufacturing

Product Service Code (PSC) – 5895 Miscellaneous Communication Equipment

Table of Contents

1. Part I – The Schedule

A. Section A – Solicitation/Contract Form B. Section B – Schedule of Services & Prices/Costs C. Section C – Description/Specifications/Statement of Work D. Section D – Packaging & Marking E. Section E – Inspection & Acceptance F. Section F – Delivery and Performance G. Section G – Contract Administration Data H. Section H – Special Contract Requirements

2. Part II – Contract Clauses

A. Section I – Contract Clauses

3. Part III – Documents, Exhibits & Other Attachments

A. Section J – List of Attachments

4. Part IV – Representations & Instructions

5. Section K – Representations, Certifications and Other Statements of Offerors

6. Section L – Instructions, Conditions, and Notice to Offerors

7. Section M – Evaluation factors for Award

a. Attachment 1 - Past Performance Questionnaire

SECTION C

Description/Specifications/Statement of Work (SOW)

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

SOLICITATION ID05180024

Statement of Work (SOW) for Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Tactical, Deployable Sensor Data Backhaul

7 February 2019

1. SCOPE: This Statement of Work (SOW) outlines Contractor tasks required to support global

Geographical Combatant Command (GCC) tactical, deployable sensor data backhaul. This level of effort includes development and delivery of fully integrated, small form factor tactical, deployable suites with the ability to support Wideband Global SATCOM (WGS) backhaul of sensor data (specifically full motion video) through DISA Gateways for follow on distribution through the Defense Enterprise Computing Centers (DECCs) supporting the Unified Video Dissemination System (UVDS) and Global Broadcast System (GBS). When required this may include Command & Control (C2) Services through the appropriate C2 Service provider. In addition, the Contractor shall provide necessary user, maintenance, training, and operator manuals; identify/recommend/deliver government approved bench stock, spares and consumable kits; facilitate/provide pre-deployment training; provide depot level functions; and secure/offer knowledgeable worldwide deployable Field Service Representatives (FSRs).

2. PERIOD OF PERFORMANCE: The period of performance (POP) will be a five-year base Indefinite-Delivery Indefinite-Quantity (IDIQ) contract with performance requirements and respective POPs under each Task Order issued against the base IDIQ.

3. TASKS: The Contractor shall develop and deliver a tactical, deployable sensor data backhaul suite using Commercial Off The Shelf (COTS) components and/or Government Furnished Equipment (GFE). These systems shall be comprised of an integrated, small form-factor deployable suite capable of backhauling ISR sensor data for locations employing airborne ISR assets and without organic sensor data backhaul capabilities as well as allow receipt of other mission relevant full motion video from the GBS forward broadcast. The capability shall be designed to support various DoD customers including, but not limited to, United States Special Operations Command (USSOCOM), United States Africa Command (USAFRICOM), United Stated Pacific Command (USPACOM), United States Central Command (USCENTCOM), and the other Geographic Combatant Commanders (GCCs), as required, with the likelihood of supporting additional non-DoD customers.

NOTE: This Section 3 identifies minimum requirements for this effort, given the potential 5-year award associated, there are several areas identified herein where performance enhancements are sought.

This effort shall include the following as a minimum:

3.1. Delivery of fully tested and deployment-ready tactical, deployable backhaul suites with User, Maintenance, Technical, and Operator Manuals. Although a single variant satisfying the below requirements may satisfy the provisions of this SOW the government is seeking the ability (based upon user requirement) to upgrade/select/robust/down-select individual components and capabilities in order to best support their specific requirement.

3.2. At a minimum, the basic system shall include the following components:

3.2.1. Sensor Data Red Router/Switch

3.2.2. Transport (Black) Router/Switch

3.2.3. Sensor Data Encoder(s)/Transcoder(s)

3.2.4. FDMA Modem

3.2.5. GBS Receiver(s)

3.2.6. Very Small Aperture Terminal (VSAT)

3.2.6.1. Although a single VSAT may satisfy the provisions of this SOW the government is seeking the ability (based upon user requirement) to select/down-select from a variety of options in order to best support their specific requirement.

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

3.2.7. High Assurance Internet Protocol Encryption (HAIPE)

3.2.8. Power Supply and Uninterruptable Power Supply (UPS)

3.2.8.1. Basic system power consumption must be 20 Amps or less and operate on common AC systems (e.g., 110-120VAC, 220-240VAC, 50Hz, 60Hz)

3.2.8.2. Uninterruptable Power Supply (UPS) must be capable of sustaining basic system operations

3.2.9. With appropriate training, the basic system setup shall be capable of completion (and demonstrate the ability to pass data) in no longer than four (4) hours; two (2) hours or less for a skilled contractor technician. The government’s goal given the tactical, deployable requirement, soonest possible setup for the basic system itself is the optimal goal

3.2.9.1. Deployable containers shall be sufficiently marked, effectively configured, and allow efficient utilization

3.2.9.2. Operator, User, and Maintenance Manuals should be easily accessible and intuitive

3.2.9.3. The basic system shall maximize logistical efficiency and operational effectiveness through consolidation of components, racks, patch panels, power management, red/black components/separation, etc.

3.2.9.4. The basic system shall maximize logistical efficiency and operational effectiveness through consolidation of cables and connections, etc.

3.3. At a minimum, this solution shall:

3.3.1. Provide the ability to encode/transcode at least two (2) video sources for output in the

Standard Definition (SD) & High Definition (HD) and encode/transcode at least two (2) video sources for output in the following formats: H.264, AVC, H.265, and HEVC

3.3.2. Provide the capability to correctly ingest and decode/transcode analog and digital Full Motion Video formats, along with associated metadata

3.3.3. Provide the ability to encode/transcode video data and associated metadata to desired output formats/resolutions/rates

3.3.4. Be modular and scalable to support ingest, encode/transcode, and transport (satellite or terrestrial) of a minimum of 4 concurrent HD full motion video feeds (e.g., 30fps HD H.264) Provide the organic capability to directly downlink at least two (2) DVB-S2 (GBS) carriers irrespective of the ISR data polarity and distribute the data/feeds with collocated and/or distributed users/operators/analysts as required

3.3.5. Be capable of scalable backhaul (satellite or terrestrial) from a minimum of 5 Mbps to 20 Mbps with additional terminal offerings for throughput rates as high as 25 Mbps Provide decoding/encoding/transcoding of High-Efficiency Video Compression (HEVC)

3.3.6. This solution shall provide the ability to support high definition (HD) and Standard Definition (SD) full motion video backhaul with H.264/AVC/HD H.265/High Efficiency Video Coding (HEVC) capable of encoding at least 2 input video sources into multiple output HD/SD streams (i.e. 2 stream destinations/input).

3.3.7. Provide the capability to correctly ingest and decode/encode/transcode analog and digital video formats, along with associated Metadata.

3.3.8. Provide the ability to decode/encode/transcode video data supporting H.264/AVC/HD H.265/HEVC with the capability of transcoding at least 2 video streams into multiple output HD/SD streams (i.e. 2 stream destinations/input) and associated metadata at the following rates:

3.3.8.1. TRANSCODING INPUTS:

3.3.8.1.1. Input H.265/HEVC:

• Main Profile Up to Level 4 (1080p30)

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

• Transport Stream, or RTSP Up to 10 Mbps

• CBR, VBR

3.3.8.1.2. Input H.264/AVC:

• Baseline, Main, High Profile

• Up to Level 4.2 (1080p60)

• Transport Stream, or RTSP

• Up to 20 Mps

• CBR, VBR

• Input MPEG-2:

• MainProfile@MainLevel (SD)

• MainProfile@HighLevel (HD)

3.3.8.1.3. Input MPEG-2:

• MainProfile@MainLevel (SD)

• MainProfile@HighLevel (HD)

• Transport Stream

• Up to 20 Mbps

• CBR, VBR

3.3.8.1.4. ENCODING INPUTS

• Input Video:

• Composite NTSC/PAL/PAL-M

• SD-SDI SMPTE 259M

• HD-SDI SMPTE 292M, 274M, 296M

3.3.8.1.5. ENCODING/TRANSCODING OUTPUTS

• Output H.265/HEVC:

• Main Profile

• Up to Level 4 (1080p30)

• Transport Stream

• Up to 6 Mbps

• Transport Stream Shaping, VBR

3.3.8.1.6. Output H.264/AVC:

• Main Profile

• Up to Level 4.2 (1080p60)

• Transport Stream

• Up to 10 Mbps

• Transport Stream Shaping, VBR

3.3.8.1.7. Output MPEG-2 Video:

• Simple and Main Profile@MainLevel

• Up to 10 Mbps

• Transport Stream Shaping, VBR

• Video Resolutions:

• 1920x1080p 60/59.94/50/30/29.97/25/24/23.98 Hz

• 1920x1080i 60/59.94/50 Hz

• 1280x720p 60/59.94/50/30/29.97/25 Hz

• 720x480/576i 60/59.94/50 Hz

3.3.8.1.8. METADATA HANDLING

• KLV with support of both Asynchronous and Synchronous KLV

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

• MISB ST0601.10 - UAS Datalink Set

• MISB ST0604.2 - Time Stamping

• STANAG 4609

• SMPTE 336M-2007 Data Encoding Protocol

• CoT to KLV Conversion

• Closed Captioning (EIA-608 & EIA-708)

3.3.8.1.9. Input Metadata:

• KLV or CoT over serial RS-232

• KLV or CoT over IP

• KLV over HD-SDI

3.3.8.1.10. Metadata (Processing):

• CoT Relay

• Insertion and KLV edits

• KLV pass-through

3.3.8.1.11. VIDEO PROCESSING

• De-interlacing

• Down Scaling

• Aspect Ratio Preserved

• Configurable Frame Rate

3.3.8.1.12. NETWORKING

• Single Program Transport Stream (SPTS)

• Unicast/Multicast (IGMPv3)

• TS over UDP

• RTSP (input only)

• Session Announcement (SAP)

3.3.9. Although manual configuration capabilities satisfy the provisions of this SOW the government is seeking an accredited mechanism to automate the configuration and control in order to increase ease of use and decrease set-up time.

3.3.10. The Government is seeking options for a local video server capability as an enhancement to the system (Optional)

3.3.10.1. The government is seeking options for a a local video server with a web interface for management and analysis as an enhancement to the system (Optional)

3.3.11. The system must support Frequency Division Multiple Access (FDMA). Although FDMA support is mandated by this SOW the government is seeking an option for easily moving to Time Division Multiple Access (TDMA) if required/desired.

3.3.12. The system shall provide the capability to transition, with minimal system changes, to emerging satellite modem technologies

3.3.13. Provide primarily Ka (Commercial and Military) satellite band usage with options for X (Commercial and Military) and Ku bands

3.3.14. Provide High Assurance Internet Protocol Encryption (HAIPE; NSA Type-1) for a maximum supported sensor data rate of 25Mbps

3.3.15. Provide the ability to host a video web portal on the associated sensor data local area network (LAN)

3.3.16. Provide optional Command and Control (C2) Services enclaves at the unclassified and collateral levels (NIPRNET and SIPRNET) with a port density capacity for a minimum of five (5) user devices using added enclaves at multiple security classification levels

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

3.3.17. Possess a total basic system weight not to exceed 500 pounds

3.3.18. Incorporate a GUI software solution for configuration and monitoring of equipment and connectivity, to include modem, routers, switches, IP routes, and decoders. The configuration capability should simplify the configuration actions required by the technician related to entering Satellite Access Authorization and Gateway Access Authorization information.

3.3.19. Support C2 services (NIPR/SIPR) to include hosting multiple enclaves with security boundaries

3.3.20. Although the system is tactical and deployable in application the government seeks the ability to leverage enterprise Network Operations (NetOps) capabilities to monitor and manage local system status and operation

3.4. Based on government specified needs, and in accordance with the agreed upon solution implemented (reference paragraph 3.1), the Contractor shall identify any additional equipment needed to support the tactical, deployable sensor data backhaul capability.

3.4.1. The contractor shall provide a solution-specific proposal to include an equipment list, pricing, timeline for delivery, and any associated impacts (e.g., resourcing, spares, software/hardware, etc.) as soon as the additional items required for the customer-specified buildout are identified.

3.4.1.1. Spares: The Contractor shall propose a sustainment plan including a recommended spares and parts list (RSPL). The cost proposal shall include purchase, storage, and shipping of applicable spares.

3.4.1.2. Bench Stock: The Contractor shall provide life cycle analysis for the equipment and propose fact-of-life upgrades for all equipment items delivered. The contractor shall provide monthly inventories of consumables and notify the government when quantities are below 60% of proposed/agreed to RSPL quantities.

3.4.1.3. Configuration Management: The Contractor shall demonstrate a viable configuration management process to ensure tracking and accountability for system warranties, software licensing, and in order to support government mandated configuration management processes/systems (e.g., REMEDY, Engineering Review Boards {ERBs}, Configuration Control Boards {CCBs}, Risk Management Framework {RMF} Artifact production/delivery, etc.).

3.5. Facilitate/provide just in-time, pre-deployment, and/or re-occurring training, to include Training

Manuals.

3.5.1. The Contractor shall provide training classes in conjunction with the software/hardware install, at a government specified CONUS location prior to deployment, and/or on a reoccurring basis as required.

3.5.1.1. At a minimum, the training shall cover information on the fundamental topics required to manage the system including: system management, transrate/transcode components/operations, network interface components/operations, network router components/operations and configuration management, initial break-fix repair (box swapping), basic troubleshooting techniques, and procedures for reporting failures and requesting factory support.

3.5.1.1.1. Initial setup to include all systems/components (radio frequency (RF), networking equipment, and, if applicable, C2 Services)

3.5.1.1.2. Operations/configuration of the RF and network components

3.5.1.1.3. Teardown, packing, and shipping process(es)

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

3.5.1.1.4. Troubleshooting of RF and network equipment with the minimum ability to rectify outages and/or degradation at the Tier 2 level

3.5.1.2. The Contractor will conduct the training in accordance with the applicable GCC (e.g. USCENTCOM, USAFRICOM, and USPACOM, etc.) and Contractor coordinated timeline, at the contractor’s facility or other government-specified location (to be determined).

3.5.2. Training Manuals: The Contractor shall provide training in accordance with the applicable GCC (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.) specified format(s). Training shall include providing all students with training manuals, reference materials, and COTS user guides to include a soft copy for the applicable government program office(s)

3.5.2.1. Training Manuals shall cover at a minimum: fundamental information required to manage the systems, including: transrate/transcode component set-up/operations, network interface component set-up/operations, network router components set-up/operations and configuration management, initial break-fix repair (box swapping), basic troubleshooting techniques, and procedures for reporting failures and requesting factory/help desk support

3.6. Secure/offer tactical, deployable sensor data backhaul system knowledgeable, globally deployable Field Service Representatives (FSRs).

3.6.1. The Contractor shall support the systems and deploy, configure, redeploy, and support these systems to and in forward operating locations (e.g., USCENTCOM, USAFRICOM, and/or other COCOM (Combatant Command) areas of operation) with the applicable location being disclosed on a need to know basis to ensure successful setup, installations, and operations. The Contractor shall also support a minimum of 12 hour a day, 7 day a week operations for the duration of the deployment or pre-deployments, and/or impart the necessary training/familiarity to ensure successful 24/7 operations by assigned government/military personnel and change out personnel when not on duty as directed per each Task Order SOW.

3.6.1.1. In addition to setup, basic configuration, operational testing, and basic troubleshooting, the Contract FSR shall provide on-site training that includes the following at a minimum:

3.6.1.1.1. Initial setup to include all systems/components (RF and networking equipment)

3.6.1.1.2. Operations/configuration of the RF and network components

3.6.1.1.3. Teardown and packing & shipping process(es)

3.6.1.1.4. Troubleshooting of RF and network equipment with the minimum ability to rectify outages and/or degradation at the Tier 2 level

3.6.1.2. The Contractor shall purchase the network components (and associated items) and license/maintenance renewals, and account for in, the equipment management system.

3.6.1.3. The FSR will, during periods of continual deployment when not on duty, be telephonically available 24/7 and within 15 minutes of attempted contact. FSRs must also be available for response and physical onsite support no more the 45 minutes of initial contact when deployed.

3.6.1.4. In those instances when the FSRs are not continually deployed to the classified forward operating location (e.g., USCENTCOM, USAFRICOM, and/or other COCOM areas of operation with the applicable location being disclosed on a need to know basis), FSR may be required to provide reach back support from another location (e.g. Ramstein AB, Germany). FSRs shall ensure telephonic contact is possible within

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

30 minutes and if necessary, respond to their appointed place of duty in no less than 1 hour to provide necessary higher level troubleshooting support and/or to facilitate classified communications.

3.6.1.5. The Contractor shall provide access to 24x7 Tier 3 level troubleshooting support.

3.6.1.6. In the conduct of initial setup and operations and in a direct operational support role at the forward operating location, the FSRs will serve as the site level subject matter expert for the Stingray suite and operations. The FSRs shall accomplish their duties in accordance with documented procedures, however, also rely upon a high level of technical experience to assess any system and/or ground satellite terminal issues, outages, and/or performance degradation. The FSRs will also manage government/military customer queries, initiate trouble tickets, report outages and provide timely updates for interested parties, provide telephonic assistance to government/military operators while off duty and report for duty as necessary to conduct physical troubleshooting/outage isolation as required, escalate outages requiring a higher Tier (OEM engineer) level of response. The FSRs will also accomplish and/or assist with directed/required upgrades and Information Assurance (IA) hardening within requisite skillset.

3.6.1.7. Prior to deployment and in the initial stages of deployment installation and operations, the FSRs will serve as a field level subject matter expert providing training for government/military personnel operating the Stingray suite outside of his physical presence on-site (e.g. 12 hour tour of duty) or while supporting operations from a reach back location (e.g. Ramstein AB, Germany). The training provided will consist of Tier 0/1 “touch labor” and Tier 2 operational level expertise, as required.

3.6.1.8. Training at the Tier 0/1 “touch labor” level shall ensure the ability to conduct rudimentary monitoring with attention focused on status, alarms, faults, and as the first contact entity when outages are experienced and affect operations. Reaction is 100% procedural in nature utilizing preexisting checklists, operating instructions, and/or a Tier 2 or higher level technician in telephonic contact. Tier 0/1 “touch labor” training most often applies when the FSR is consistently deployed forward and assigned government/military personnel are only assigned to situational awareness functions in support of Stingray operations.

3.6.1.9. Training at the Tier 2 level is necessary when the FSRs are not consistently deployed forward and the government/military personnel are primarily assigned for Stingray operations. Similar to the FSRs, the government/military personnel will be trained in accordance with documented procedures, however, will also require the technical experience to assess most Stingray and/or ground satellite terminal issues, outages, and/or performance degradation. This will include the training necessary to initiate trouble tickets, report outages and provide timely updates for interested parties, and escalate outages requiring a higher Tier (OEM engineer) level of response. At the Tier 2 level, they may also be required to accomplish directed/required upgrades and Information Assurance (IA) hardening within requisite skillset and with telephonic direction/support from a reach back Tier 2 FSR and/or Tier 3 OEM senior engineer.

3.6.1.10. When providing reach back support, the FSRs must possess significant skill and knowledge at the Tier 2 level and demonstrate some aptitude at the Tier 3 level. In this scenario, the FSR must rely upon their experience/background in order to assess any terminal issue, outage, operational degradation remotely, and telephonically guide government/military completion of terminal maintenance (scheduled and unscheduled). This level shall conduct in depth log analysis and root cause isolation.

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

Based upon operational and technical experience, this tier is the field level subject matter expert and bear responsibility for provisioning and commissioning new terminals. Finally, in their tier 3 technician capacity, the FSRs shall conduct and facilitate advanced troubleshooting activities and establish and document procedures for lower tiers as required and, in most instances, remotely/telephonically.

3.6.1.11. As required, the contractor shall support pre-deployment training and testing at designated locations, using a government-provided (GFE) system. In addition, the contractor will assist in the maintenance and reconstitution of forward deployed systems returning from the applicable AOR.

3.6.1.12. The contractor shall assist in deployment preparation, providing support to the Geographical Combatant Commander’s (GCC) forward operating locations. This includes pre-deployment and deployment planning support as required. At a minimum, the contractor shall provide support for the installation and training at three OCONUS locations (e.g. home station for the deploying unit and/or Ramstein AB, Germany or another staging area, and the forward operating location(s)—to be disclosed on a need to know basis). In addition to setup, basic configuration, operational testing, and basic troubleshooting, the FSR shall provide on-site training that includes the following at a minimum:

3.6.1.12.1. Initial Setup to include all Systems/Components (RF and Networking Equipment)

3.6.1.12.2. Operations/Configuration of the RF and Network Components

3.6.1.12.3. Teardown and Packing & Shipment Processing

3.6.1.12.4. Troubleshooting of RF and Network Equipment

3.7. Based on government specified needs, and in accordance with the agreed upon solution implemented (reference paragraph 3.1), the Contractor shall identify any additional equipment needed to support the tactical, deployable sensor data backhaul capability.

3.7.1. The contractor shall provide a solution-specific proposal to include an equipment list, pricing, timeline for delivery, and any associated impacts (e.g., resourcing, spares, software/hardware, etc.) as soon as the additional items required for the customer-specified buildout are identified.

3.8. SATCOM Terminal Evaluation: The system shall incorporate a suite of MILSATCOM certified (ARSTRAT requirements for WGS certification), or with an approved waiver, tactical Ka terminals with a minimum throughput of no less than 2 Mbps and a maximum of 20 Mbps.

3.9. Site Surveys: The Contractor shall conduct site surveys (telephonic and/or on-site if required) to identify any upgrades required for current DISA Gateway locations.

3.9.1. The contractor shall propose travel to support surveys at three (3) CONUS and two (2)

OCONUS locations upon Government request.

3.10. INFORMATION ASSURANCE SUPPORT

3.10.1. The suite shall include meet all information assurance requirements as directed by the applicable GCC, Combat Support Agency, or non-DoD customer’s Certification and Accreditation (C&A) authority and to obtain an Authorization to Operate (ATO) prior to the new equipment installation.

3.10.2. As a minimum, the Contractor will perform the work effort in accordance with RMF processes for identifying security requirements, providing security solutions, and managing information security activities.

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

3.10.3. The Contractor shall verify the system meets the security requirements defined in the DoD 8510 application manual and that the design includes items on the Approved Products List (APL) for general use by the DoD.

3.11. PROGRAM MANAGEMENT SUPPORT

3.11.1. The Contractor shall provide GCC (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.) specified program management support for the installations. Support shall include but is not limited to:

• Program and/or project execution

• Scheduling/Timelines

• Program/project status, periodic updates, and continuing information flow

• Personnel with current and relevant levels and breadth of acquisition program management experience, technical expertise, and programmatic/project management skillsets

3.12. INSTALLATION SUPPORT

3.12.1. Installation of the provided hardware. Upon completion of the installation the system(s) will:

• Meet all OEM requirements of installed items

• All software will remain at the currently approved operational baseline

• All hardware will be operational and, as required, transferred to the unit(s) for sustainment support

4. GENERAL INFORMATION

4.1. The Contractor shall meet all requirements and responsibilities in support of the appropriate GCC (e.g. at a minimum USCENTCOM, USAFRICOM, USPACOM, etc.) as outlined in this SOW. All staff shall be fully trained, professional, and customer oriented and will consistently provide responsive, flexible, and cost effective service. Quality work performance in accordance with applicable standards and guidelines shall be ensured. The Contractor shall perform the standards of this SOW in an environmentally acceptable manner consistent with Federal, State and local laws as well as applicable Instructions. The Contractor shall provide all personnel, tools, material, supervision, and other items or services necessary to perform installation, and in the instance of FSRs, operation of the equipment. The Contractor shall also perform all pre-installation, intermediate installation, and post installation testing and certifications as required.

4.2. The Contractor shall furnish everything required to perform all services required by this SOW with the exception of those items or services specifically stated to be provided by the GCC (e.g.

USCENTCOM, USAFRICOM, USPACOM, etc.).

4.3. The contractor shall comply with all regulations listed in the below table.

Publication Number Title Date

MIL-STD-810G/with Change 1

Environmental Engineering Considerations And Laboratory Tests

15 APR 2014

MIL-STD-1472G Human Engineering 11 JAN 2012

MIL-STD-188-164B

Change Notice 1

Interoperability Of SHF Satellite Communications Terminals

20 JUL 2016

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

MIL-STD-188-165A,

W/Change 1

Interoperability Of SHF Satellite Communications PSK Modems (FDMA Operation)

1 NOV 2005

MIL-STD-882E Standard Practice For System Safety 11 MAY

MIL-STD-130N,

Change 1

Department of Defense Standard Practice: Identification of Marking of U.S. Military Property

16 NOV 2012

MIL-STD-196F Joint Electronics Type Designation System (JETDAS) 11 SEP 2013

MIL-HDBK-61A Military Handbook: Configuration Management Guidance 7 FEB 2001

Wideband X and Ka-Band Terminal Performance Certification Test Procedures, Version 2.0

2 APR 2015

Wideband Terminal Performance Certification Requirements, Version 2.00

18 JUL 2013

ITU-R S.728-1 Maximum Permissible Level of Off-Axis e.i.r.p. Density from Very Small Aperture Terminals (VSATs)

1 JAN 1995

ITU-R S.580-6 Radiation diagrams for use as design objectives for antennas of earth stations operating with geostationary satellites.

1 JAN 2003

Eutelsat Earth Station Standard (EESS) 502, Issue 11, revision 1

Minimum Technical and Operational Requirements JAN 2017

ITU Appendix 30B Web Site http://www.itu.int/en/ITU- R/space/plans/Pages/AP30B.aspx

N/A

Federal Communications Commission (FCC) 47 CFR, Part 25.209

Antenna performance standards including antenna gain patterns in the geostationary satellite orbit plane, off-axis gain patterns, and cross-polarization gain patterns.

18 AUG 2016

FCC 47 CFR Part 25.134

Licensing provisions of VSAT networks with respect to maximum allowable antenna feed input power density.

FCC 47 CFR Part 25.132

Verification of earth station antenna performance standards

FCC 25.218 Off-axis EIRP density envelopes for FSS earth stations transmitting in certain frequency bands

18 AUG 2016

FCC 05-63 IB Docket No. 00-248

Fifth Report and Order in IB Docket No. 00248

15 MAR

FCC 05-63 FIFTH REPORT AND ORDER IN IB

DOCKET NO. 00-248,

AND THIRD REPORT AND ORDER IN CC

DOCKET NO. 86-496

15 MAR

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

NMEA 0183

Ver. 4.10

National Marine Electronics Association 0183 Interface Standard

NMEA 2000

Ver 2.00

National Marine Electronics Association Standard for Serial-Data Networking of Marine Electronic Devices

5. FIELD SERVICE SUPPORT AND TRAVEL

5.1. The contractor may be required to travel in support of the IDIQ Task Orders. The Government may recommend Contractor travel to seminars, conferences, workshops, meetings, events or training that is government unique or is necessary to maintain the requirements of the Task Order SOW. The Contractor shall obtain written approval from the Contracting Officer or TPOC prior to Contractor personnel incurring any travel expense. The Contractor shall identify personnel who will be traveling and provide travel estimates to the Government 10 business days prior to departure but a minimum of 2 business days prior to departure when there are extenuating circumstances to the projected travel date. Contractor costs for travel will be reimbursed in accordance with FAR 31.205-46, in arrears. The travel costs shall be reasonable and allowable as defined in FAR 31.201 and in accordance with the limitations of the JTR/FTR/DSSR.

Reimbursement shall only be authorized in support of government-directed travel. Travel to other Government or civilian facilities outside the local area may be required. The contractor shall invoice monthly on the basis of cost incurred. The contractor must provide documentation in support of all travel expenses. The contactor will not be reimbursed for local travel (within a 50-mile radius of the Government/contractor’s facility) or commuter travel (commute from home to work site). Commuter travel (recurring travel from an offeror’s location to the customer’s site) is not reimbursable. The Contractor shall follow all appropriate travel directives regarding cost and safety. Invoice submissions including travel costs shall include completed travel expense sheets (i.e., travel voucher) for each trip and each employee who traveled. The travel expense report, receipts of $75 or more (with exceptions being lodging and transportation), and supporting documentation (e.g., approval email for exceeding per diem rates, cost comparisons, etc.) shall be submitted with the invoice. Expense report(s) must include the traveler’s name, dates of travel, destination, purpose of travel, Approval Authority documentation (e.g., copy of the e-mail authorizing travel by Government official), and cost for each trip. All travel costs shall be compiled into the Government provided travel expense sheet (PWS Addendum I) or similar document that has been determined to be acceptable by the Government. The entire submission shall be complete and organized to enable the Government to complete an efficient review.

Submissions that are not complete and organized are subject to rejection.

5.1.1. Joint Travel Regulation: The Contractor will use the JTR and FTR for all applicable cost reimbursable travel actions.

5.1.2. Travel Advisories: The Contractor will review State Department and other travel advisories prior to travel abroad.

5.1.3. Recruitment and retention incentives in accordance with the Department of State

Standardized Regulations (DSSR) may be authorized for contractors providing required support when in travel status. Danger Pay and Post (Hardship) Differential allowances for such travel will be authorized in accordance with the DSSR. The allowances for such costs shall be identified separately. The allowance for a specific

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul location, as determined by the Department of State Office of Allowances, will be considered effective when the contractor lands on the ground of such location (i.e.

“wheels down”).

5.1.4. DBA Travel Insurance is required for all OCONUS travel.

5.1.5. Access to the Synchronized Pre-deployment and Operational Tracker (SPOT) is required to support overseas travel.

5.2. QUALITY ASSURANCE

5.2.1. The GCC (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.) program manager will evaluate the Contractor’s performance under this SOW using the method of surveillance specified in the contract terms and conditions and based upon reports provided by program/project managers and/or technical representatives (TRs).

5.3. SECURITY REQUIREMENTS

5.3.1. Facility/Personnel Clearances: The Contractor must have a Secret cleared facility and the ability to manage personnel security clearances including compartmented and Alternate Compensatory Control Measures (ACCM).

5.4. Disclosure of Information. Performance under individual Task Orders will require the personnel to have (at least an) active SECRET security clearances. The Program and Project Managers, and at least one available FSR will require Top Secret SI access. The Contractor will have access to information sensitive to applicable GCCs (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.), or other government agencies. The Contractor will not divulge or release information developed or obtained in the course of project performance, except to authorized GCC (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.) personnel or upon written approval of the applicable GCC (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.)

program/project manager. Any question on the release or use of information, or doubt of a person’s authority to request information, will be addressed to the applicable GCC (e.g.

USCENTCOM, USAFRICOM, USPACOM, etc.) program/project manager. The Contractor providing this support may be required to execute an SF-312, Non-Disclosure Agreement.

5.5. Inquiries, Comments, and Complaints. The Contractor shall direct all inquiries, comments, or complaints arising from matters observed, experienced, or learned as a result of, or in connection with performance, the resolution of which may require dissemination of official information, to the applicable GCC (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.) program/project manager.

5.6. Release of Information. Contractor shall not release any information (including photographs, files, public announcements, statements, denials or confirmations) on any part/phase of the project hereunder without the prior written approval of the GCC (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.) program/project manager. The Contractor shall not release information regarding individuals associated with the project hereunder without the prior written approval of the applicable GCC (e.g. USCENTCOM, USAFRICOM, USPACOM, etc.)

program/project manager.

6. IDIQ Management. The Contractor shall ensure that the base IDIQ and each Task Order will have a designated Contractor Point of Contact (POC). The IDIQ/Task Order POC shall be responsible for serving as the coordinating single point of contact between the Contractor and Government. The POC shall be fully authorized to manage the activities of Contractor and third-party contractors needed to meet the Task Order requirements, providing a corporate escalation path for issues that may develop on individual Task Orders.

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul

7. Monthly Invoice. The Contractor shall provide a monthly invoice for each TO to be submitted simultaneously with the monthly status report. The monthly invoice shall be submitted by the 15th of each month. If any information is missing or incorrect the invoice shall be rejected. The invoice shall include but not be limited to:

• Task Order number.

• The Contractor shall provide an itemized invoice for all items included in the submittal.

• Travel costs (if needed).

• Supporting documentation for travel costs (if needed). Invoices including travel costs shall include supporting documentation as required by the Federal Travel Regulation (FTR) and Joint Travel Regulation (JTR). Invoice submissions including travel costs shall include completed travel expense sheets for each trip for each employee.

• The Contractor shall comply with line item billing requests.

• The Contractor shall include number of hours expended per labor category, the labor category, and the rate for the month being invoiced.

• The Contractor shall include a total amount of labor hours and total dollars expended.

8. Contractor Submission. Deliverables are to be transmitted with a cover letter, on the prime contractor’s letterhead, describing the contents, electronically through the General Services Administration’s (GSA) web-based procurement system, Information Technology Solutions Shop (ITSS), government TPOC, and to any other destination(s) as required per the Government’s request.

The Contractor shall provide hard copy deliverables as required upon the Government’s request. All deliverables shall be produced using recommended software tools/versions as approved by the Government. Reports shall be accomplished utilizing the MS Office Software Suite (to include MS Project as required) or Adobe .pdf. All raw and summarized data, test results, drawings, pictures, modeling, analytics, process orders, methodologies and coding shall be unrestricted and submitted electronically with final test reports, provided to the Government in Microsoft Word, Excel, and PowerPoint presentation formats. All final reports shall be presented to the Government through in-person briefings summarizing all results and recommendations as well as final documented reports.

9. Administration. Work is to be accomplished through the General Services Administration, Federal Acquisition Service (FAS), Great Lakes Region, through its contract with the selected Contractor.

Certification by the Government of satisfactory services provided is contingent upon the Contractor performing in accordance with the terms and conditions of the referenced contract, this document, the approved technical and price quote, and all amendments. Government TPOC, GSA's representatives, and the Contractor's representative(s) shall meet when deemed necessary by the Government TPOC.

The Government TPOC, the GSA representatives, and the Contractor’s representative may meet at the place determined by the Government.

10. Kickoff Meeting. The Contractor in conjunction with the GSA Contracting Officer (CO) shall meet with key Government representatives within 30 business days after award to ensure a common understanding of the requirements, expectations, and ultimate end products. The Contractor shall discuss the overall understanding of the project and review the background information and materials provided by the Government representatives. Discussions will also include the scope of work, deliverables to be produced, how the efforts will be organized, projects completed, assumptions made/expected and results. A concerted effort shall be made to gain a thorough understanding of the Government expectations. However, nothing discussed in this or in any subsequent meetings or discussions between the Government and the Contractor shall be construed as adding, deleting, or modifying any Task Order requirements, including deliverable specifications and due dates.

11. Post Award Conference/Periodic Progress Meetings. The Contractor agrees to attend any post award conferences convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The Contracting Officer, TPOC, GSA COR, and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the Contracting Officer will apprise the Contractor of

Department of Defense (DOD) Intelligence, Surveillance, and Reconnaissance (ISR) Sensor Data Backhaul how the government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government. A Monthly Status report that will list completed work for the period, outstanding issues, problems, resolutions and plans for the next month’s activities shall be submitted to the TPOC and with the monthly invoice.

12. Identification of Contractor Employees. All contract personnel attending meetings, answering

Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.

13. Contractor Performance. The Contractor shall establish and provide a qualified workforce capable of performing the required tasks. All staff shall be fully trained, professional, and customer oriented and will consistently provide responsive, flexible, and cost effective service. The Government shall approve all key personnel resumes. The Contractor shall monitor work performance, measure results, ensure delivery of contracted product deliverables and services, support management and decision making, and facilitate communication. The Contractor shall bring problems or potential problems affecting performance to the attention of the TPOC and GSA PM as soon as possible. The Contractor shall provide in writing the results of all meetings with the TPOC that affect and/or change conditions, or result in additional agreements or requirements to the GSA PM. The Contractor shall not perform any work outside the scope or requirements of this SOO and resultant order without express written approval of the GSA Contracting Officer. Verbal reports shall be followed up with written reports within 48 hours of submission of the verbal report. The Contractor shall establish and maintain a documented set of disciplined, mature, and continuously improving processes for administering all contract and Task Order efforts with an emphasis on cost efficiency, schedule, performance, responsiveness, and consistently high-quality delivery. Quality work performance in accordance with applicable standards and guidelines shall be ensured. The Contractor shall perform the standards of this SOO in an environmentally acceptable manner consistent with all Federal, State and local laws.

14. Quality Assurance. Inspections will be conducted in accordance with the contract terms and conditions with unacceptable or unsatisfactory work being addressed as outlined therein. Services will be monitored for contract compliance on an ongoing basis as designated in the Quality Assurance Surveillance Plan (QASP).

15. Non-Personal Services. The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services.