FoT_SOW_9FEB2012.pdf

STATEMENT OF WORK (SOW)

For The

SPECIAL OPERATIONS FORCES DEPLOYABLE

NODE (SDN)

FAMILY OF TERMINALS

(FoT)

9 February 2012

United States Special Operations Command (USSOCOM)

Program Executive Officer for Command, Control, Communications and Computers (PEO-C4)

7701 Tampa Point Boulevard

MacDill AFB, FL 33621-5316

Table of Contents

1. SCOPE

1.1 INTRODUCTION

1.2 SYSTEM DESCRIPTION

1.3 CONCEPT OF OPERATIONS

1.4 PRODUCTION QUALIFICATION

2 APPLICABLE DOCUMENTS

2.2 APPLICABLE DOCUMENTS

3. SECURITY

4. COMMON REQUIREMENTS

4.1 KEY PERFORMANCE PARAMETERS

4.2 REQUIREMENTS

4.2.1 Operating and Storage Temperature Range

4.2.2 Modem Function

4.2.3 Terminal Control, Monitor and Alarm

4.2.4 External Modem and GPS Interfaces

4.2.5 Uninterruptable Power Supply (UPS)

4.2.6 System Set-Up and Tear-Down Time

4.2.7 Transport Configuration

5. TEST AND CERTIFICATION REQUIREMENTS

5.1 IN-PLANT BURN-IN TEST

5.2 PRODUCT QUALIFICATION TEST (PQT)

5.3 PRODUCTION ACCEPTANCE TEST (PAT)

5.4 SATCOM SERVICE PROVIDER COMPLIANCE/CERTIFICATION

5.4.1 Military X-band and Ka-band Compliance/Certifications (KPP)

5.4.2 C and Ku-band SATCOM Service Provider Compliance (KPP)

5.5 INTEGRATED LOGISTICS SUPPORT

5.5.1 System Operations and Maintenance Manuals

5.5.2 Instructor and Key Personnel Training & Training Materials

5.5.3 Computer Based Training (CBT) Application

5.5.4 Maintenance Concept

5.5.5 Warranty and Warranty Repairs

5.5.6 Contractor Depot Logistics Support (Non-Warranty Repairs)

5.5.7 Reliability Program

5.5.8 Maintainability Program

5.5.9 Test Support Package

5.5.10 Packaging, Handling, Storage and Transportation

5.6 MANAGEMENT SYSTEMS REQUIREMENTS

5.6.1 Integrated Product Teams (IPT)

5.6.2 Monthly Program Status Reports

5.6.3 Program Reviews

5.6.4 Safety and Safety Assessment Report (SAR)

5.6.5 Configuration Management Program

5.6.6 As-Built Configuration

5.6.7 Quality Program

5.7 REFURBISHMENT AND PRODUCTION PLANNING

APPENDIX A: 1.2 METER TERMINAL

A.1 APERTURE SIZE

A.2 OPERATING FREQUENCY BANDS (KPP)

A.3 RADIO FREQUENCY PERFORMANCE

A.4 WIND PERFORMANCE

A.5 ANTENNA RANGE OF MOTION

A.6 ANTENNA POLARIZATION (KPP)

A.7 SATELLITE ACQUISITION

A.8 SYSTEM SET-UP/TEAR-DOWN TIME (KPP)

A.9 FREQUENCY BAND RECONFIGURATION TIME

A.10 SYSTEM WEIGHT (KPP)

A.11 VOLUME (KPP)

A.12 PRIME POWER

APPENDIX B: 2.0 METER TERMINAL

B.1 APERTURE SIZE

B.2 OPERATING FREQUENCY BANDS (KPP)

B.3 RADIO FREQUENCY PERFORMANCE

B.4 WIND PERFORMANCE

B.5 ANTENNA RANGE OF MOTION

B.6 ANTENNA POLARIZATION (KPP)

B.7 SATELLITE ACQUISITION AND TRACKING (KPP)

B.8 SYSTEM SET-UP/TEAR-DOWN TIME (KPP)

B.9 FREQUENCY BAND RECONFIGURATION TIME

B.10 SYSTEM WEIGHT (KPP)

B.11 VOLUME (KPP)

B.12 PRIME POWER

1. SCOPE

1.1 Introduction

This Statement of Work (SOW) defines the requirements to integrate, configure, test, verify performance, certify, deliver, support and sustain the Special Operations Forces Deployable

Node (SDN) Family of Terminals (FoT). The SOF FoT shall consist of the items identified in the following paragraphs and in the attached Appendices. Common requirements applicable across all terminal variants are defined below in the main body of this SOW. Additional, variant-specific requirements are defined in each Appendix. Delivery will include personnel, facilities, materials, equipment, software and services necessary to accomplish the tasks defined in this

SOW for FoT units. All services and data are to be provided in accordance with the Contract

Data Requirements List (CDRL).

1.2 System Description

The FoT shall consist of several portable satellite communications (SATCOM) terminal variants as defined below and in the attached Appendices. These terminals shall provide secure and non-secure voice, video and data communications at multiple classification levels to deployed SOF worldwide. The FoT will provide multi-user, multi-classification satellite transmission and reception capabilities. The terminals included in the FoT will provide tactically deployed SOF users with worldwide connectivity to the SOF Information Enterprise (SIE). Each terminal variant will provide the capability for multiple users/laptops to access SIE services and will be capable of simultaneous operations over multiple classifications (SCI, Secret, and Unclassified enclaves).

The SDN FoT is an evolutionary, follow-on lifecycle replacement for the legacy SOF

Deployable Node-Medium (SDN-M) variants and the larger SOF Deployable Node-Heavy

(SDN-H) terminals. The FoT will be comprised of several terminal variants, initially including but not limited to: a 1.2 meter aperture terminal operating in the X, Ku and Ka bands and a 2.0 meter aperture terminal operating in the C, X, Ku, and Ka bands. Other terminal configurations may be added from time to time through an engineering change proposal process and after approval by the SDN configuration control board (CCB).

The primary goal of the FoT is to provide at least the existing capabilities provided by the legacy

SDN-M and SDN-H systems. Requirements common to all FoT variants are defined in Section 4 below. Additional requirements applicable to specific terminal variants are defined in the attached Appendices.

1.3 Concept of Operations

SOF mission success depends on coordinated operations on or around the target and the ability to receive, process and report information. The SDN FoT will support the mission-critical capability for tactical elements to receive, process and transmit information to and from the SIE.

The SIE is the United States Special Operations Command (USSOCOM) infrastructure systems/networks that is a subset of the Global Information Grid (GIG) and used to disseminate information between Headquarters (HQ) USSOCOM, components, operational detachments, Theater Special Operations Commands (TSOCs), and selected government agencies and activities.

SOF historically operates in environments with limited or no Command, Control, Communications, Computers, Intelligence (C4I) infrastructure. This necessitated reliance on portable equipment that is carried forward for initial Command and Control (C2). The legacy

SDN terminals, SDN-M and SDN-H provided the reachback capability for deployed SOF. The

SDN-M connected deployed SOF elements to their respective headquarters and provided an interface for the SOF War-fighter to the GIG at throughputs between 512 Kbps to 6 Mbps. The

SDN-M provides essential communications that meet the need of 10-15 users by providing “first in” communications connectivity and reach-back. The SDN-H is designed to support requirements of larger elements such as a Joint Special Operations Task Force (JSOTF) or

Combined Joint Special Operations Task Force (CJSOTF) and up to 300-500 users.

Both the SDN-M and SDN-H provide essential C4I for command and control, situational awareness, mission planning, analysis and reporting, collaboration, and real-time mission coordination between tactical teams, aircraft, and C2 elements. Both systems use Commercial-off-the-Shelf (COTS) and Government-off-the-Shelf (GOTS) hardware and software and are compliant with mandatory industry, regulatory and DOD standards and directives. Both systems are also deployable, relatively lightweight, commercial air transportable, secure satellite communications package used to access services to/from SCAMPI/GIG network segments, through government owned and leased commercial earth terminals.

The capabilities and multiple variants of the FoT will allow maximum flexibility for deployed

SOF at all levels to: a.) mission-tailor equipment suites and b.) exploit worldwide, locally available satellite spectrum allowing connectivity to SIE services via USSOCOM Mediaports and SOF Strategic Entry Points (SSEPs), or DoD Teleports and STEP sites.

Terminals operating in the military X and Ka bands shall have current DISA/ARSTRAT certifications authorizing access to the Defense Satellite Communications System (DSCS) and

Wideband Global SATCOM (WGS) space segments. Additionally, terminals operating in the commercial C and Ku frequency bands shall be compliant with applicable requirements imposed by Intelsat, Eutelsat, and SES WorldSkies for operation over those constellations. The entire family of terminals shall utilize a common graphical user interface (GUI). The USSOCOM satellite communications (SATCOM) network employs iDirect modem technology. FoT terminals shall have integral iDirect modems interoperable with current USSOCOM iDirect modem implementations.

1.4 Production Qualification

The first phase of production will be the fabrication, integration, and testing of the Production

Qualification Systems (five of each of the variants defined in the Appendices). Prior to the full rate production decision, the contractor shall deliver the Production Qualification Systems to the

Government for conduct of User Acceptance Testing (UAT). The Production Qualification

Systems delivered to the Government shall be fully integrated terminals as defined in this SOW and its Appendices. The Production Qualification Systems unit airtime costs that are incurred for testing during the PQT are the responsibility of the contractor. Total pricing for the

Production Qualification Systems shall include the tasks and deliverables associated with all of the Management Systems, Test and Certification, User Acceptance, Production, Quality, Provisioning, and Integrated Logistics Support (ILS) requirements for Government acceptance of the Production Qualification Systems, including refurbishment after User Acceptance Testing.

ILS proposed pricing of the Production Qualification Systems shall also include development and delivery of documentation for training, logistics, operations and maintenance, and an initial spares list. In addition, the cost for a test support package during UAT shall be included in the price for these units. Development of course materials/plan of instruction and conduct of the initial Instructor and Key Personnel Training (IKPT) course in support of the User Acceptance

Testing shall be included in the cost of the Production Qualification Systems. The Computer

Based Training Application shall be included in the cost of the Production Qualification

Systems.

In accordance with the schedule milestones and required documentation identified in this SOW, the Contractor shall produce the Production Qualification Systems and perform all activities relevant to personnel, facilities, materials, equipment, software, training, and other services.

Fabrication of the Production Qualification Systems shall follow accepted commercial fabrication practices and shall meet all of the FoT requirements identified in this SOW and attached Appendices. Following completion of all functional and technical testing and final system acceptance, the Production Qualification Systems shall become the approved production

FoT baseline configuration. Upon retrofit and acceptance testing, the Production Qualification

Systems shall be delivered as production FoT systems.

2 APPLICABLE DOCUMENTS

2.1 Order of Precedence Statement

The documents referenced herein, to the revision shown, form a part of this SOW to the extent specified.

In the event of inconsistency among documents, the following descending order of precedence shall apply:

a. The contract

b. This SOW

c. Contract Data Requirements List (CDRL)

2.2 Applicable Documents

Publication Number Title Date

MIL-STD-810G

Environmental Engineering Considerations

And Laboratory Tests

31 OCT 2008

MIL-STD-1472F / and

Change Notice 1

Human Engineering 23 AUG 1999 /

5 DEC 2003

MIL-STD-188-164A /

with CN3

Interoperability Of SHF Satellite

Communications Terminals

25 August

MIL-STD-188-165A

Interoperability Of SHF Satellite

Communications PSK Modems (FDMA

Operation)

15 APR 2002

MIL-STD-882D Standard Practice For System Safety 10 FEB 2000

Wideband Global SATCOM (WGS) X and

Ka-Band Terminal Certification

Requirements, version 1.03

27 FEB 2009

Defense Satellite Communications System

(DSCS) Satellite Communications

(SATCOM) Terminal Performance

Certification

AUG 2009

Defense Satellite Communications System

(DSCS) Earth Station Terminal Certification

Process

Coordination

Draft, dated 1

July 1996 or later

Defense Satellite Communications System

(DSCS) Earth Station Terminal Certification

Procedures

Coordination

Draft, dated

April 1997 or later

WGS Ka-Band Terminal Certification Test

Procedures, Version 2.1

14 MAR 2006

Wideband Gapfiller Satellite (WGS) Concept of Operations (CONOPS), (v.5.6)

13 MAR 2006

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

Minimum Technical and Operational

Requirements

OCT 2008

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.

1 October 2010

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 05-62 IB Docket Number 00-248

Sixth Report And Order And

Third Further Notice Of Proposed

Rulemaking for streamlining licensing of non-compliant terminals.

15 March 2005

FCC 05-63 IB Docket No. 00-248

Fifth Report and Order in IB Docket No. 00-

15 March 2005

CFR-47, Parts 25.2098 and 25.209134

Co-Satellite Interference, Off Axis Power

Density Antenna Performance Standards, Licensing Provisions of Very Small Aperture

Terminal (VSAT) Networks

FCC 05-62 IB Docket Number 00-248

Sixth Report And Order And

Third Further Notice Of Proposed

Rulemaking

15 March 2005

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 March 2005

3. SECURITY

Security will be in accordance with the DoD Contract Security Classification Specification, DD

Form 254, provided in the RFP. The Contractor’s personnel supporting this Contract shall receive a COMSEC briefing when working any unclassified task involving the INFOSEC boundary (e.g., production assembly, test, and repair), or will be cleared at the SECRET level when working any task that’s been classified. Contractor personnel will be authorized to courier classified information up to the SECRET level in performance of official duties upon approval of, and designation by, the COR.

The contractor shall ensure requirements for safeguarding classified information and classified material are fulfilled to include: obtaining and verifying personnel security clearances, verifying security clearances and indoctrination of visitors, controlling access to restricted areas, protecting government property, and securing automated and non-automated management information systems and data. The contractor's management system shall prevent unauthorized disclosure of classified and sensitive unclassified information. The Government shall be immediately notified of any security incident or any indication of a potential unauthorized disclosure, or compromise, of classified, or sensitive unclassified, information.

The contractor shall provide security management support. Typical efforts include, but are not limited to: performing classified document control functions, inventorying classified materials, processing program access requests, preparing and monitoring personnel indoctrination and debriefing agreements, and maintaining and using security-related databases.

4. COMMON REQUIREMENTS

The following requirements apply to all terminal variants. In addition to these requirements, variant-specific requirements are defined in the individual Appendices to this document. The technical objectives for the FoT are to satisfy the Key Performance Parameters (KPPs), and all other requirements defined in subsequent sections of this SOW and its Appendices. Additional requirements applying to specific variant types are found in the Appendices.

4.1 Key Performance Parameters

The KPPs for each of the initial FoT variants defined in Appendices A and B are defined in the paragraphs and sections below and in the applicable Appendix for each variant.

4.2 Requirements

4.2.1 Operating and Storage Temperature Range

The operating temperature range for all variants shall be, as a minimum, -32 C to +50 C (KPP).

The storage temperature range for all variants shall be, as a minimum, -40 C to +60 C.

4.2.2 Modem Function

The FoT variants shall be provisioned with an embedded iDirect modem function (iConnex

Evolution). The modem function shall support iDirect Multi-Frequency Time Division Multiple

Access (MF-TDMA), Digital Video Broadcast-Satellite Return Channel (Generation 2) (DVB-

S2), and spread spectrum modes of operation. The modes of operation shall be selectable by the terminal operator and not require the operator to externally load additional software.

4.2.3 Terminal Control, Monitor and Alarm

Terminal control shall be implemented via pushbuttons activating the pre-loaded iDirect options file and automatically sequencing the terminal into an active state to acquire and join the defined network in the options file. Indicators shall be provided on the terminal case housing for the terminal operator to assist in antenna pointing and satellite acquisition and to indicate operating status of the terminal. As a minimum; Power, Status, Network, Transmit, Receive, Crypto, and

Temperature indicators as provided by the iDirect modem card shall be provisioned. Indicators shall have the ability to be extinguished by the terminal operator. These indications shall also be displayed to the operator on the terminal control GUI described next.

A terminal control, monitor and alarm function (CMAF) shall be provided via a Graphical User

Interface (GUI). The GUI appearance shall be as common as possible across all FoT variants, diverging only for frequency band selection and configuration, and tracking functions in the larger aperture terminals. The GUI shall be hosted on a terminal control processor. The terminal control processor shall be a handheld or laptop computer. The SATCOM terminal and terminal control processor shall communicate via IEEE 802.3 Ethernet. The terminal shall be provisioned with a minimum of three IEEE 802.3 Ethernet ports (weatherproof RJ-45) for terminal control processor and Local Area Network (LAN) connections supporting user data streams. The terminal shall also be provisioned with at least one digital subscriber line (DSL) port to support separation of the antenna and terminal control processor by at least 1 kilometer. The terminal control processor shall be hosted in the same transit case as the SATCOM terminal during transport. The GUI shall provide functions for terminal equipment configuration, terminal control, status monitoring and reporting, alarm indications, and event logging. Specifically, the

GUI shall have a main screen showing summary information that contains: receive Eb/No or receive signal strength, transmit EIRP (from an output monitor at the high power amplifier), Alarm Indications, Equipment Status (i.e., a block diagram containing all VSAT equipment and indicating color coded normal, alarmed, or failed terminal function/subsystem status). The GUI shall provide the ability to click on a terminal subsystem or function in the GUI and then be immediately redirected to the configuration screen for that device/function. The GUI shall indicate status and progress to the operator during set-up/teardown to include acquisition of the correct satellite (to include carrier frequencies) and entering the iDirect network. The

Government shall have unlimited reproduction rights to the terminal control/GUI software.

As an alternative to the terminal CMAF being hosted on an external computer, the vendor may, at its option, host this function on a processor internally mounted inside the terminal. In the event this alternative is pursued all of the above requirements for functions and indicators shall still be satisfied by providing a Web browser interface to the CMAF and GUI via a Contractor provided handheld or laptop computer.

The terminal shall be provisioned with a Receive Monitor port (BNC-type female connector) to monitor the downconverted receive signal at L-band.

4.2.4 External Modem and GPS Interfaces

Each terminal variant that operates in the military X and Ka frequency bands shall be provisioned with interfaces, on TNC (female) connectors, to support use of an external satellite communications modem (user provided). The external IF interfaces are in addition to the internal interfaces supporting the integral iDirect modem.

All terminal variants shall provide an external port supporting an external Global Positioning

System (GPS) receiver to provide receive signal to the terminal to aid in satellite pointing and acquisition. The port shall interface with the AN/PSN-13A Defense Advanced GPS Receiver

(DAGR) and shall be capable of accepting GPS information from the DAGR. A DAGR-to-terminal cable shall be provided by the contractor for each terminal procured by the Government.

4.2.5 Uninterruptable Power Supply (UPS)

The Contractor shall provide a UPS capability of sufficient capacity to power all FoT variants for a minimum of 15 minutes. The UPS shall provide continuous operation of the terminal variants and uninterrupted network services during disruptions or loss of prime power. This capability shall be housed in its own separate transit case and shall not exceed 88 pounds in weight.

Volume of the UPS shall not exceed 80 linear inches (L+W+H). Weight and volume of the UPS does not count against the terminal weight and volume. Each terminal ordered shall be delivered with a UPS. The contractor shall certify that batteries selected for inclusion in the UPS allow for the transport of the UPS on commercial air carriers in accordance with the restrictions identified at http://safetravel.dot.gov/index.html.

4.2.6 System Set-Up and Tear-Down Time

Set-up and tear-down times are unique to each FoT variant, variant-specific requirements are defined in the Appendices. Set-up and tear down times shall include set-up and tear down of the entire SATCOM terminal. Set-up time shall begin with the FoT packed in its transit configuration in the transit cases, and shall be completed when the iDirect modem has obtained network lock on the Hub transmit signal. Tear down time shall be the reverse sequence and conclude when the system is fully packed in the hard transit cases. No tools shall be required for set-up or tear-down.

4.2.7 Transport Configuration

The FoT will be transported in ruggedized transit cases to the area of operations via military or commercial air, and within the Theater of Operations by truck or helicopter. The transit cases shall be provided by the Contractor for primary transport and provide sufficient padding to protect the system while being transported. Transit cases shall be lockable and have extendable handles for carrying. Any case identified as a 4-person lift (IAW MIL-STD-1472F) case shall have, as a minimum, two handles per case side and one handle per case end when viewing the case from above. Where possible, end handles should be of a wide enough opening to allow gripping with both hands. Variant-specific transit case quantity, weight and volume requirements are defined in the Appendices.

4.2.8 Commonality Of Parts

To the maximum extent possible the FoT variants shall be constructed of common and interchangeable parts and software to simplify troubleshooting and facilitate training and logistical support. The contractor shall identify which parts are being used across multiple terminal variants.

5. TEST AND CERTIFICATION REQUIREMENTS

5.1 In-Plant Burn-In Test

Prior to Production Qualification Testing (PQT) and/or Production Acceptance Testing (PAT)

(in accordance with sections 5.2 and 5.3) the Contractor shall perform a 48-hour continuous In-

Plant Burn-In test, at ambient temperature (23 o C), for the Production Qualification Systems and at least 20% of all additional production terminals. The system shall be power-cycled, one half hour off for every 3 hours on. If a failure occurs, the unit under test shall be repaired and the burn-in shall continue from that point on with the exception that the burn-in shall continue until the last 12 hours are failure-free. Daily tests consisting of simulated traffic shall be conducted to verify system performance. The Contractor shall provide a burn-in test report (CDRL A001).

The Government reserves the right to observe this test.

5.2 Product Qualification Test (PQT)

The Government shall witness qualification testing on the FoT at the contractor's facility and shall be notified by the contractor at least ten days in advance of testing. The in-plant qualification tests shall verify system compliance with the technical and environmental requirements, safety of operation, radiation hazard protection, and shall be conducted in accordance with contractor proposed and Government approved test procedures (CDRL A002).

PQT procedures and testing shall include individual testing of the SATCOM terminals. The contractor shall perform all testing necessary for obtaining SATCOM certifications for operation over civilian and government space segments. All the Production Qualification Systems shall undergo full PQT. At least 20% of all additional production terminals shall undergo PQT. The production unit airtime costs during testing are the responsibility of the contractor. The PQT shall include operational testing over the full operational temperature range defined above using test methods 501.5 and 502.5, Procedure II in accordance with MIL-STD-810G.

The FoT terminal and UPS, while in the configurations identified below, shall be subjected to the following contractor conducted environmental tests in accordance with the stated procedure in

MIL-STD-810G:

Vibration IAW MIL-STD-810G, method 514.6, Procedure 2. The specific test procedures, levels and duration for Transportation Life Phase mode categories 5, and 7 through 11 referenced in Table 514.6-I, Vibration Environment Categories, shall be implemented. Truck/trailer/tracked environment shall use the loose cargo test procedures

(packed for transit).

Humidity IAW MIL-STD-810G, method 507.5 (packed for transit and deployed configuration)

Salt Fog IAW MIL-STD-810G, method 509.5(packed for transit and deployed configuration)

Sand and Dust IAW MIL-STD-810G, method 510.5 Procedures I and II(packed for transit and deployed configuration)

Shock IAW MIL-STD-810G, method 516.6 procedures II and IV (packed for transit).

(NOTE: This requirement is not applicable to the UPS)

Rain IAW MIL-STD-810G, method 506.5, Procedure 1(packed for transit and deployed configuration)

High Temperature IAW MIL-STD-810G, method 501.5, Procedure I (transit configuration)

Low Temperature IAW MIL-STD-810G, method 502.5, Procedure I (transit configuration)

The contractor shall provide all the necessary equipment for testing purposes with the exception of any identified GFE. The contractor shall provide a PQT test report to the Government at least

7 days prior to the shipment of any terminal (CDRL A003). The test report generated as a result of the MIL-STD-810 testing above shall be included as part of the first PQT test report. The

Government reserves the right to observe any performed testing pertaining to production of the systems and shall be notified by the contractor at least ten days in advance of testing.

5.3 Production Acceptance Test (PAT)

The PAT shall be a subset of the PQT and shall be conducted on the remaining production terminals that do not undergo PQT. The Contractor shall provide the Government its proposed

PAT procedures for FoT for Government review and approval (CDRL A018). The Contractor shall maintain the test equipment design, hardware, procedures and software in accordance with its internal procedures, including software and hardware configuration control, and calibration and maintenance. The PAT reports shall be provided concurrent with the delivery of each terminal and provide verification of FoT performance as specified in this SOW (CDRL A019).

The Government reserves the right to observe this test.

5.4 SATCOM Service Provider Compliance/Certification

5.4.1 Military X-band and Ka-band Compliance/Certifications (KPP)

At Production Qualification Systems delivery the contractor shall provide current DSCS/WGS certification letters (CDRL A005) issued by ARSTRAT and DISA authorizing operation over the WGS and DSCS X and Ka military bands for FoT variants with X and Ka-band capabilities.

Terminals operating in X-band shall be compliant with all requirements for operations over the

XTAR space segment.

5.4.2 C and Ku-band SATCOM Service Provider Compliance (KPP)

At Production Qualification Systems delivery the Contractor shall provide a Ku-band terminal compliant with all Federal Communications Commission (FCC) and International

Telecommunications Union (ITU) requirements (to include off-axis emissions) identified in the documents listed in paragraph 2.2 above and Intelsat, SES New Skies and Eutelsat requirements applicable for terminals of the same size operating in their respective space segment (per

Appendices below). The Contractor shall conduct all testing required to verify SATCOM terminal performance is compliant with the appropriate service standard when the terminal is integrated into the SIE architecture. The Government reserves the right to observe any performed testing pertaining to production of the systems and shall be notified by the contractor at least ten days in advance of testing.

The Contractor shall provide antenna patterns and any other required data to verify FCC and ITU compliance and a Eutelsat certification of authorization to operate earth stations, in accordance with Eutelsat Note 2001/008, Issue 2 dated 16/07/01. (CDRL A004)

5.5 Integrated Logistics Support

5.5.1 System Operations and Maintenance Manuals

The Contractor shall deliver a System O&M Manual for each FoT variant comprised of existing manuals for each subsystem and additional system-level information providing a road map through the subsystem manuals. The System O&M Manual shall reflect the FoT configuration delivered under this contract. The manual shall include; equipment technical data, equipment setup and installation procedures, detailed menu field definitions, warnings, alarms and precautions, all authorized operator level tasks/procedures, principles of operation; security guidance, all authorized field-level testing, fault isolation and troubleshooting, support/test equipment, removal/replacement procedures, warranty handling instructions, disposal instructions, and a Repair Parts and Special Tools List (Note: Special Tools are those required for repair only, system set-up and tear down shall require no tools as defined in paragraph 4.2.6 above). Actual photos showing step-by-step assembly is desired in this manual. Initial delivery, to the Government, of the Systems O&M Manual shall be 45 days prior to User Acceptance

(CDRL A008). The Government shall have 15 days to review and comment on the manual. If the manual is deemed inadequate, the Contractor shall incorporate Government comments as specified within 15 days of receipt of the Government's comments. Upon completion of User

Acceptance, the Government may provide additional comments for incorporation into the manual. The manual shall be structured so it can be easily updated as required by follow-on FoT

Engineering Change Proposal (ECP) technology upgrades or technology insertions. Final delivery of the System O&M Manual shall be one hard-copy (8 ½ by 11 page-size) and one digital copy in PDF format, on CD-ROM or DVD. One hard-copy and CD-ROM/DVD copy of the manual shall be delivered with each FoT system. The CD-ROM/DVD shall contain separate files selectable by a user for O&M manuals for each FoT variant. The CD-ROM/DVD shall be labeled as “SDN Family of Terminals (FoT) Operations and Maintenance Manuals”. The

Contractor shall provide any required updates to the Government, within 15 calendar days of approved changes, in the same format as the final delivery of the System O&M Manual each time it is required. The System O&M Manual is necessary for operation, maintenance, installation and training as set forth in DFARS 252.227-7015(b)(1)(iv).

5.5.2 Instructor and Key Personnel Training & Training Materials

Instructor and Key Personnel Training (IKPT) is intended to “train the trainer.” The Contractor shall develop the IKPT training course materials and deliver them to the Government for review and approval (CDRL A009). The Contractor shall provide an initial IKPT training class to the

LCSM instructors and other personnel approximately 2-4 weeks prior to Government-conducted

User Assessment Test and Evaluation (UATE) (CDRL A010). The IKPT class shall provide training for up to 8 students and shall be at least 24 hours in duration per FoT variant. The

LCSM instructor's initial class shall provide training to User Acceptance personnel with the

Contractor’s instructors monitoring. Additional Contractor conducted classes for IKPT training are a requirement and shall be ordered at the discretion of the Government and held at the LCSM location. The optional IKPT classes shall be at least 24 hours in duration per FoT variant and presented to a maximum of 8 students per class. A minimum of 30 days notification shall be given by the Government prior to the required course date. The Government, in coordination with the Contractor, shall be responsible for providing the facilities and FoT systems (two terminals, minimum, for every eight students) to conduct the training. The Contractor shall provide each student a full set (hard copy) of training materials during each IKPT course to include an FoT systems O&M manual plus an additional soft copy on CD ROM/DVD. The materials shall be developed in Contractor format and approved by the Government. Materials shall be delivered to the Government with full reproduction rights, and consist of hard-copy paper documents and an electronic version on CD-ROM. Format of the electronic deliverable shall be in a mutually agreeable version of PDF format. The IKPT materials are necessary for operation, maintenance, installation and training as set forth in DFARS 252.227-7015(b)(1)(iv).

Updates to any and all documentation due to the Government shall be provided in the same conditions that the originals, to include version control, are provided.

5.5.3 Computer Based Training (CBT) Application

The Contractor shall provide a CBT application based on training documents and training support packages to meet the requirements for CBT using COTS development software (CDRL

A011). An open-systems architecture shall be used to support code reuse as well as a database-centric design to facilitate content changes as required. The CBT application shall be delivered to the Government with full reproduction rights. The CBT shall be structured so that students open a high level directory to select the appropriate training module(s) for a specific terminal variant. Format of the electronic deliverable shall be in a mutually agreeable version of a CD-

ROM or DVD. A single consolidated CD-ROM/DVD shall host all CBT materials for all FoT variants. The CBT application is necessary for operation, maintenance, installation and training as set forth in DFARS 252.227-7015(b)(1)(iv). Updates to any and all documentation due to the

Government shall be provided in the same conditions that the originals are provided.

5.5.4 Maintenance Concept

The Government anticipates a two-level maintenance concept for the FoT: Field and

Sustainment. Field level maintenance includes preventive maintenance tasks, fault isolation and troubleshooting and the removal and replacement of line replaceable units (LRUs) identified in the FoT O&M manual. The LRUs shall be defined as those components which can be removed and replaced within 15 minutes by operators without special electronics skills and training, or peculiar support equipment or unique tooling. The Contractor shall propose a list for

Government review and approval of LRUs decomposed into shop replaceable units (SRUs) that can be supported under this concept. As part of Field level maintenance, the Government’s Life

Cycle Sustainment Manager (LCSM) is responsible for shipping replacement parts to the user’s unit, verifying failures of returned parts en-route to the Contractor, and maintaining a “float” supply of parts to support the user community. The Government LCSM is also responsible for shipping and receiving parts between the user organization and Contractor. All parts, those being returned to the Contractor for repair, or from the Contractor to the users, shall be processed through the Government LCSM activity. All maintenance above the Field level shall be considered Sustainment level and shall be returned to the designated Government LCSM for repair and return. Upon notification from the user, the Government LCSM shall provide the necessary replacement parts/materiel to the user organization and contact the Contractor Depot for return and repair of failed parts/materiel. The FoT systems shall be designed for minimal operator maintenance that does not require special electronics skills, tools, and training. All warranty, depot level sustainment and technical assistance support for the Government provided laptops will be provided by the Government LCSM.

5.5.5 Warranty and Warranty Repairs

The Contractor shall provide a system warranty of 24 months for the FoT terminals. The

Contractor shall address innovative ways to reduce turn-around-time of repaired components and dispute adjudication and handling of Could Not Duplicate (CND) failures. Any non-GFE assembly or component that fails shall be repaired or replaced subject to the terms of the manufacturer warranty. Turn-around time for repair or replacement of warranted items shall not exceed 30 calendar days. Turn-around time is defined as starting when the contractor receives the item at its shipping/receiving dock and terminating when the item leaves the contractor’s shipping/receiving dock. Warranty activities shall be documented in the Monthly Program Status

Report as defined in paragraph 5.6.2 below.

5.5.6 Contractor Depot Logistics Support (Non-Warranty Repairs)

The Contractor shall propose a plan to support non-warranty repairs of the FoT. Any repair action determined to require 65% or more of that item’s replacement cost (as verified by Defense

Contract Management Agency) shall be considered beyond economical repair and shall result in replacement of the affected part or replaceable unit. The government LCSM shall receive notification of such within two days from determination of need for replacement. The

Contractor shall address innovative ways to reduce turn-around-time of repaired components and dispute adjudication and handling of CND failures. Turn-around time for repair or replacement of all items shall not exceed 30 days. Turn-around time is defined as starting when the contractor receives the item at its shipping/receiving dock and terminating when the item leaves the contractor’s shipping/receiving dock.

The Contractor shall establish and provide Contractor Depot Logistics Support for all hardware, firmware, and software procured under this contract on a firm fixed price. This maintenance activity may employ the same structure that is used to provide warranty support. The Contractor shall furnish all qualified labor, supervision, materials, equipment, tools, appliances, and services to repair FoT LRUs. Repairs shall be performed at the contractor's facility and can be supported through field upgrades as necessary and must be reviewed and approved by the Government prior to execution. The Contractor shall repair or replace, and return to the Government, any

LRU within 15 work days after receipt of a failed LRU. The Contractor shall maintain the capability to provide all “out of warranty” repair support for all FoT hardware, firmware and software – excluding any GFE. Non-warranty repair activities shall be documented in the

Monthly Program Status Report as defined in paragraph 5.6.2 below.

5.5.7 Reliability Program

The reliability program shall ensure that all hardware/software items comply with the item/components product specifications. The FoT system availability shall be a minimum of

98% . The Contractor shall maintain a Reliability Program throughout the period of performance of this contract and shall report the status of the reliability program at Program Management

Reviews (PMR) and in the Monthly Program Status Report as defined in paragraph 5.6.2 below.

5.5.8 Maintainability Program

The Contractor shall ensure maintenance concerns are addressed during system design and integration to achieve a mean time between operational mission failure (MTBOMF) of 10000 hours.

5.5.8.1 Provisioning

The Contractor provided provisioning parts list (PPL) shall be updated on an annual basis

(CDRL A006). At a minimum, the PPL shall include part number, Commercial and

Government Entity (CAGE) Code, and National Stock Number (NSN) (if applicable). The

Contractor shall also recommend the initial Government LCSM pipeline spares parts list based on historical failure rates and analysis of FoT components (CDRL A007). This spares list shall be updated on an annual basis. Determination of sparing strategies and actual spares quantities to be procured shall be made by the Government and shall be based on sparing analysis for actual procurement densities of the FoT.

5.5.8.2 Item Unique Identification (IUID).

In accordance with DFARS 252.211-7003, the FoT shall be identified, through the use of item unique item identifier (UID) marking. Information regarding implementation of UID methods can be found at the Office of the Under Secretary of Defense for Acquisition Technology and

Logistics website (http://www.acq.osd.mil/dpap/UID/) and the Special Operations Forces

Tactical Assured Connectivity System (SOFTACS)_UID Plan, dated 21 December 2006.

5.5.9 Test Support Package

The Contractor shall provide test support services for the FoT systems during Government

UATE. Test support services shall include all necessary spare parts, test equipment, publications, sustainment maintenance and services required for UATE. The test support services shall be available throughout the UATE. The UATE shall be conducted at a CONUS location and last approximately ten days. The Contractor shall be notified of the dates and locations for conducting UATE, once determined.

5.5.10 Packaging, Handling, Storage and Transportation

The packing of the equipment, material and spare parts shall be such as to provide protection against damage, deterioration and wear during transportation, handling and storage (best commercial practices). Once the systems are complete and packed for transport, the Contractor shall ship the systems to the Government LCSM for fielding to the gaining commands. As the systems are received by the LCSM, they will be inspected and tested at the LCSM’s facility to ensure they are operationally suitable for fielding. If the systems or any components of the system are deemed faulty, the Contractor shall support the LCSM with troubleshooting, replacement or repair of the component(s) at the expense of the Contractor. Once the LCSM has certified the systems are fully operational, the LCSM will provide the Contractor with a formal notification of acceptance at which point the LCSM and equipment warranties support the cost of any future failures.

5.6 Management Systems Requirements

5.6.1 Integrated Product Teams (IPT)

The Contractor shall participate in USSOCOM IPTs that include major sub-contractors and

USSOCOM representatives. IPT activities shall include oversight of the integration effort for the

FoT system to ensure that a quality product is delivered on schedule that meets the performance specifications. The Contractor shall employ sound concurrent engineering and logistics principles by using all relevant disciplines in cross-functional teams.

http://www.acq.osd.mil/dpap/UID/

5.6.2 Monthly Program Status Reports

The Contractor shall monitor sub-contractors’ product quality and performance against delivery schedules. The contractor shall report “issue and corrective action status” in a monthly Program

Status Report and at Program Management Reviews. The Contractor shall prepare and submit a

Program Status Report monthly (CDRL A012). The report shall include a program schedule reflecting the progress against the significant milestones that are required to manufacture, test, deliver and support the FoT system. In addition, the Monthly Program Status Report shall contain sections detailing Warranty, non-Warranty and Maintenance Status of all failures and repair actions, including but not limited to point of origin, part description, part number, serial number, date of receipt, reason for return, corrective action taken, date item(s) returned to the

LCSM, contractor cost of repair, and estimated hours of operation along with reliability calculations, shall be provided to the Government to maintain symptom and failure resolution for inspection. Quarterly submissions of this reporting requirement shall start no later than 90 days after contract award. The Contractor shall plan and execute the FoT program utilizing its own internal tracking and reporting system. The Contractor shall implement an integrated master plan and contract master schedule (CMS) that clearly defines all the tasks necessary to satisfy the requirements in this SOW.

5.6.3 Program Reviews

The Contractor shall conduct Program Management Reviews (PMRs) with USSOCOM at the

Contractor’s facility, no more frequent than quarterly, through the five year lifecycle of the contract (CDRL A013). During these reviews, the Contractor shall report on progress of tasks covered by this SOW, problems encountered and/or anticipated, and corrective action planned.

The Contractor shall host a combined Post Award Conference (PAC) and Preliminary Design

Review (PDR) within 15 days after contract award and shall host a Critical Design Review

(CDR) within 30 days of the PDR. In addition, Technical Interchange Meetings (TIMs), as required for training, provisioning, technical manuals approval, etc. shall be conducted as determined by the Government. A program review shall be held in conjunction with delivery of the first terminals. The Contractor shall provide meeting/conference agendas, briefings, and minutes for the reviews (CDRL A014).

5.6.4 Safety and Safety Assessment Report (SAR)

The contractor shall be responsible for all safety aspects of engineering changes and shall evaluate all real and potential hazards associated with personnel operation, test and maintenance procedures, and component attributes. The contractor shall perform a Safety Assessment and submit a Safety Assessment Report using MIL STD-882D as a guide and in accordance with

(CDRL A015). The SAR shall:

Document the safety risk being assumed prior to test or operation of the system.

Identify all safety features of the system hardware and software design, specific controls or precautions to be followed in the use of the system

Provide verification of compliance to safety requirements identified in the system specification

Identify toxic and environmentally unacceptable materials used in the system, any possible alternative materials, and recommended actions to eliminate or reduce the use of hazardous materials

Address any exposure concerns to personnel during operational or maintenance proce-dures to include fabrication, transportation, setup and tear down, or resulting from damage to the equipment

The contractor shall attach to the SAR a completed System Safety Design Verification Checklist and Material Safety Data Sheets for all hazardous materials and identify any material used in the system design that requires disposal as a hazardous waste.

5.6.5 Configuration Management Program

The Contractor shall develop and maintain a Configuration Management Program in accordance with the Contractor’s internal procedures for all item hardware and software; all test equipment hardware and software, and other test or simulation hardware and software. From time to time and as necessary the Contractor shall propose (CDRL A016), and the Government shall review and approve, engineering change proposals (ECPs) offering enhancements and improvements in terminal hardware and/or software performance.

5.6.6 As-Built Configuration

The Contractor shall maintain an as-built configuration database that allows traceability of all hardware and software provided beginning with the delivery of the Production Qualification

Systems, and ending with the final warranty period (CDRL A017). At conclusion of the warranty period, the complete database shall be provided to the Government. Access to data shall be granted to the Government within 14 days notice. This includes:

a. As-built configuration data.

b. Tracking all Class I/II ECPs, deviations/waivers.

c. Evolution of the Technical Design Package (TDP) for both hardware and software.

d. Identification of all serial numbers, UIDs, and/or lot codes.

The Contractor shall maintain an as-built configuration listing for each deliverable item to the

Government. If an item is returned to the Contractor for repair or update, the Contractor shall update the configuration listing.

5.6.7 Quality Program

The Contractor shall maintain a documented Quality Assurance (QA) program for the FoT in compliance with or certified by ISO 9001 and ISO 9004. The Contractor shall use their existing processes and procedures. QA personnel shall participate in IPTs, formal reviews, configuration audits, configuration control boards (CCB), and material review boards (MRB). QA shall develop material inspection plans (MIP) for incoming material. QA shall monitor the performance of the FoT system through the manufacturing cycle, maintain test data and perform statistical analysis.