FINALPWS091707.doc

SOLICITATION: HC1013-07-R-2025

CONTRACT:

US Army Intelligence and Security Command

Project TROJAN Commercial Communications Services Performance Work Statement

SOLICITATION NUMBER HC1013-07-R-2025

17 September, 2007

Table of Contents

1.0 Scope

1.1 Scope

1.2 Objectives

2.0 Applicable Documents

2.1 Technical Publications

2.2 Other Documents

3.0 Requirements

3.1 General Description of Service Requirements

3.2 Types of Services Required

3.3 Technical Interface Requirements

3.4 Performance Requirements

3.5 Maintenance

3.6 reserved

3.7 National Emergency

3.8 Timing and Synchronization

3.9 Management Requirements

3.10 Host Nation Connection and Approval

3.11 Telecommunications System Installation Plan

3.12 Management Meetings/Conferences and Reports

3.13 Conference Agenda

3.14 Meeting Reports

3.15 Exception reporting

3.16 General Requirements

3.17 Commercial Communications Interface (CCI) Room

3.18 FCC Regulatory Matters

3.19 Memorandum of Agreement, Arifjan Kuwait

3.20 Future Expansion Requirements

4.0 Quality Control Procedures

4.1 Acceptance Test Plan

4.2 Acceptance Testing

4.3 Periodic Testing

4.4 Outage Testing

4.5 Service Delivery Summary (SDS)

5.0 Security

5.1 Facility Security

5.2 Personnel Security

6.0 Site Surveys

6.1 Contractor Site Surveys

6.2 Radio Frequency Interference (RFI)

7.0 Conditions

7.1 Schedule Changes

7.2 Camp Arifjan, Kuwait

7.3 TNCC Circuit Assignments 34

7.4 Transition

7.5 GFE/GFI

Definitions

Appendix A- List of Acronyms

Appendix B- Typical Site Conditions for Remote Fixed Sites

Appendix C- TROJAN Transportable Terminal Characteristics

Appendix D- Circuit Listing

NOTE: Appendix C&D are excel spreadsheets and attached separately

Performance Work Statement (PWS)

For

US Army Intelligence and Security Command

Project TROJAN Commercial Communications Services

1.0.

SCOPE

1.1. This Performance Work Statement (PWS) describes Government requirements for commercially contracted, end-to-end, communications services in support of the TROJAN and/or Intelligence Electronic Warfare (IEW) Systems. The TROJAN/IEW Systems, will provide the U.S. Government an operational intelligence capability and a means to enhance the combat readiness of tactical Military Intelligence (MI) personnel. The TROJAN System will consist of a series of CONUS and OCONUS based fixed/transportable/mobile systems with varying configurations interconnected by long-haul terrestrial and satellite communications to TROJAN Network Control Centers (TNCCs), located at Ft. Bragg, NC and Ft. Belvoir, VA. The communications services shall provide for transmission and reception of synchronous, full-duplex or simplex, asymmetrical or symmetrical, digital circuits carrying encrypted data across both domestic and international boundaries. Network architectures will utilize a combination of Single Channel per Carrier (SCPC), Time Division Multiple Access (TDMA), and spread spectrum technologies.

1.2.

Objectives. The objective is to obtain the following types of services:

1.2.1.

Fixed Site Communications Service. This service shall provide end-to-end connectivity, DEMARC-to-DEMARC, for fixed sites listed in Appendix D, with options for additional service, to the TNCCs. Services may be provided by satellite, terrestrial or a combination of both.

1.2.2.

Satellite Communications Connectivity for Government- Owned Transportable C, and Ku Band Satellite Terminals. This service shall provide satellite connectivity, including satellite bandwidth and Contractor-provided hub equipment, between the TNCCs and remotely deployed Government-owned and operated transportable satellite terminals. Services will include telephonic support to Government-owned terminals in the activation and troubleshooting of deployed terminals operated by government personnel with varying degrees of terminal expertise.

1.2.3.

Reserved

1.2.4.

Trojan Bandwidth Assigned Upon Demand (T-BAUD). This service will require the Contractor to provide uplink/downlink services (satellite modems, RF equipment, etc) at the TNCCs for a defined number of Government-owned TROJAN transportable terminal circuits utilizing satellite space segment capacity leased in bulk under this PWS. Configuration of the T-BAUD circuits will be managed by the Government.

1.2.5.

Bandwidth Capacity. The Contractor shall provide bulk transponder services to the Government. The transponder bandwidth/power allocations will be managed by the Government, utilizing Contractor-provided, task specific software, to support T-BAUD operations as well as provide bandwidth for Contractor-provided transportable satellite terminals located anywhere in the 50 states, Puerto Rico and the Virgin Islands.

1.2.6.

Host Nation Approval, Landing Rights, FCC Licenses. The contractor shall coordinate regulatory documentation and approval required to operate Contractor-owned, as well as Government-owned, satellite terminals at CONUS and OCONUS locations.

1.2.7.

Satellite Transponder First Right of Refusal (FRR). When directed by the Government, the Contractor shall obtain FRR for satellite transponders and bandwidth to support future requirements.

2.0.

APPLICABLE DOCUMENTS. The following documents form a part of this PWS to the extent specified herein. In case of a conflict between the document and this PWS, the PWS takes precedence.

2.1.

Technical Publications:

a.

National Telecommunications and Information Administration (NTIA) "Red Book" (rev 9/95). Specifically Chapter 5 "Spectrum Standards" and Chapter 10 "Procedures for the Review of Telecommunications System for Frequency Availability and Electromagnetic Compatibility" pertain. The reference is available on the World Wide Web at http:\\www.ntia.doc.gov/osmhome/redbook/redbook.html.

b.

IEEE C95.1-1991 (Safety Levels with Respect to Human

Exposure to Radio Frequency Electromagnetic Fields, 3 KHz to

300 GHz.). Reference is available on the World Wide Web at http://standards.ieee.org/reading/ieee/std_public/description/emc/C95.1-1991_desc.html

2.2.

Other Documents:

a.

DoD 5220.22-M National Industrial Security Program

Operating Manual(NISPOM), dated 28 February, 2006. The reference is available on the World Wide Web at http://www.dtic.mil/whs/directives/corres/html/522022m.htm.

b.

TROJAN Security Class Guide, Project TROJAN dated 10 July 1996. Available from USAINSCOM G6.

c.

TROJAN SPIRIT Classification Guide dated 12 July 1996. Available from USAINSCOM G6.

d.

T-BAUD Operating Procedures dated 5 May 2006. Available from USAINSCOM G6.

3.0.

REQUIREMENTS. The Contractor shall provide the labor, materials, and facilities required to design, engineer, procure, install, test, transition, document, operate, maintain, and administer network control and operational support for all services and facilities provided by the Contractor necessary to fulfill Government requirements. The leased services provided under this requirement will use Contractor-provided and owned equipment. Other sites, services or subnetworks may be requested at a later date.

3.1. General Description of Service Requirements. Based upon operational considerations and cost effectiveness to the Government, the Contractor shall:

3.1.1.

Design and implement a single transmission medium or any combination of transmission media (e.g. fiber optics, wire, microwave radio or satellite) and equipment that satisfies the requirements shown in Appendix D.

3.1.2.

Exercise a turn-key, end-to-end, demarc-to-demarc transition of the current TROJAN System operational services. See Appendix D for a list of existing circuits and Contractor- provided terminal locations.

3.1.3.

Acquire, install, test, operate and maintain Contractor-furnished communications service.

3.2.

Types of Service Required.

3.2.1.

Fixed Site Communications Service. The service shall provide end-to-end connectivity, DEMARC-to-DEMARC, for fixed sites shown in Appendix D, with options for additional service from widely dispersed worldwide locations to the TNCCs.

3.2.1.1.

The physical location of the Ft. Belvoir DEMARC is in the Contractor’s room in building 2310 (Constitution Hall, Ft. Belvoir, VA). The Ft. Bragg DEMARC is in the communications interface room, building 5353, Ft. Bragg, NC. The Contractor shall choose the type of communications medium that fulfills the Government requirement based upon operational considerations and cost effectiveness. The Government reserves the right to approve or disapprove the recommendations of the Contractor. The fixed site service information identified in Appendix D is the current data rate requirements. Paragraph 3.2.1.2 and 3.2.1.3 below identify maximum data rates that these sites may be required to operate at. If the Contractor chooses to propose satellite connectivity for the sites listed below, the equipment shall be able to support the data rates listed.

3.2.1.2.

The following CONUS/HI fixed site locations are currently being supported by Contractor-provided equipment installations. This paragraph defines the capacity for which the contractor equipment must be designed for. Appendix D defines the current circuit/carrier requirement. Bandwidth for these terminals will be supported via capacity defined in paragraph 3.2.5.

a. Schofield Barracks, HI Single carrier up to 1544Kbps

b. Charlottesville, VA

Single carrier up to 1544Kbps

c. Wahiawa, HI Gateway

Two carriers up to 1024Kbps

d. Ft. Lewis, WA

Two carriers up to 1544Kbps

e. Draper, UT

Single carrier up to 768Kbps

f. Camp Pendleton, CA

Single carrier up to 1544Kbps

g. Ft. Huachuca, AZ

Two carriers up to 1544Kbps

h. Camp Lejeune, NC Single terrestrial circuit

1.544Kbps 3.2.1.3.

The following OCONUS fixed site locations are currently being supported by Contractor-provided equipment installations:

a. Weisbaden, Germany

Single carrier up to 768Kbps

b. Darmstadt, Germany

Single carrier up to 2048Kbps

c. Camp Arifjan, Kuwait

Two carriers up to 2048Kbps 3.2.2.

Satellite Communications Connectivity for Government- Owned Transportable C and Ku Band Satellite Terminals. This service shall provide satellite connectivity, including DEMARC-to-DEMARC satellite bandwidth, between the Contractor-provided up/down link equipment at the TNCCs and remotely deployed Government-owned and operated transportable satellite terminals. These locations shall be in support of CONUS or OCONUS operations. CONUS operations will utilize satellite bandwidth procured under paragraph 3.2.6 unless specified otherwise.

3.2.2.1.

The DEMARC point for Government-owned and operated terminals shall be at the surface of the antenna reflector. Types of Government satellite terminals for this service will include, but are not limited to, TROJAN SPIRIT II, TROJAN LITE, TROJAN TLITE, Unified Command Suite (UCS), PROJECT TRITON/PROPHET, and TROJAN Mobile Remote Receiver System (TMRRS). Appendix D identifies the terminals which will be assigned to individual circuits. Appendix C provides baseline antenna terminal performance information for deployed Government satellite terminals.

3.2.2.2.

Other Government satellite terminals which cannot be specified at this time will conform to commercial satellite interoperability standards.

3.2.2.3. Except when geographic location of the deployed Government-owned satellite terminal limits access to satellites which have single hop coverage of the TNCCs, all transportable service will up/downlink directly into antenna terminals located at the TNCCs.

3.2.2.4.

Proposed satellite architectures supporting Government-owned, deployed terminals, shall not provide an antenna elevation angle less than 9 degrees from the Full Coverage deployed locations (identified in Appendix D) to the satellite. This does not include services supporting Multiple Frequency-Time Division Multiple Access (MF-TDMA) SATCOM on the Move (SOTM) service, defined in paragraph 3.2.8, which requires a minimum 25 degree antenna elevation angle from the deployed terminal location.

3.2.2.5. For satellite services supporting Government-owned satellite terminals deployed to geographic locations which do not access satellites with single hop coverage of the TNCCs, remote up/downlink (gateway) sites with terrestrial or double satellite connectivity. Paragraph 3.4.2.6 defines maximum tolerable end-to-end transmission delay.

3.2.2.6.

Satellite architectures utilizing cross-strapped transponder configurations are acceptable except for services supporting Government-owned MF-TDMA SOTM terminals. In this case, the deployed terminals must be on the same transponder as the hub terminal, whether the hub is located at the TNCC (Ft Bragg/CONUS) or an overseas gateway (OCONUS) location.

3.2.3.

Reserved

3.2.4.

Reserved

3.2.5.

T-BAUD. The T-BAUD concept is based on leasing 50 state Ku Band satellite bandwidth and associated transponder power along with Contractor-provided satellite earth station (hub) termination services and satellite modems. These leases will satisfy satellite connectivity requirements between the TNCCs and TROJAN SPIRIT II or other Government-owned terminals operating at any location within the 50 states, Puerto Rico and the Virgin Islands. The use of the contiguous satellite bandwidth and power (fractional or full transponders) will be managed by the Government and link variables will be tailored to optimize the network for user’s requirements and specific operational conditions. The Government will develop transmission plans for T-BAUD bandwidth and will assign users access to the satellite links within this bandwidth. The Government will change the transmission plan in terms of number of satellite links, link data rates, coding rates and power for specific operating locations as frequently as needed to respond to changing user’s requirements. The Government will not exceed the T-BAUD satellite bandwidth or transponder power under lease and the number of satellite links for any given transmission plan will not exceed the number of modems under lease for T-BAUD service. Transponder plans will be coordinated with the Contractor prior to implementation.

3.2.5.1.

The Contractor shall provide T-BAUD services consisting of the following:

a) One (1) Ku band satellite transponder, and associated transponder power, covering the 50 states, Puerto Rico and Virgin Islands. The required mix of circuits, currently supported on SES satellite AMC04, is defined in Appendix D. In addition to supporting transportable terminals, the selected satellite/transponder configuration will also provide connectivity to Contractor-provided terminals in the 50 states. These circuits and locations are also defined in Appendix D.

b) Two (2) Ku band transponders, and associated transponder power, covering a minimum of the 48 contiguous states, Puerto Rico and Virgin Islands. The required mix of circuits is defined in Appendix D, currently supported on SES satellite AMC09.

c) Satellite hub services (earth station) at the TNCCs. Additionally, the Contractor shall provide antenna terminal services at the Wahiawa, HI DSCS gateway, which will utilize T-BAUD bandwidth services to link the Korea-based TROJAN DSCS circuits to the TNCCs.

d) Contractor-owned satellite modems and RF/antenna equipment adequate to support the number of T-BAUD circuits defined by the Government in Appendix D.

e) All operation and maintenance associated with this requirement.

3.2.5.2.

Connectivity - The T-BAUD service shall provide connectivity between the TNCC’s DEMARCs defined in paragraph 3.3.2.1 and the remote Government-owned terminal DEMARCs, as defined in paragraph 3.3.2.4.

3.2.5.3.

T-BAUD Management Software - The Contractor shall provide task specific software to the Government to conduct link analysis (link budgets) and prepare satellite transponder plans for using and sharing the bandwidth/power among Government-owned terminals. The software will be satellite/transponder specific, providing all carrier parameters required to prepare the transponder frequency plan. The Contractor shall allow the Government to manage user access to the satellite links and change the transmission plan at any time in order to respond to changing user’s requirements. The Contractor shall provide training for up to eight personnel identified by the Government on the operation of the software and the process for coordinating the transponder plans with the satellite vendor. The Contractor shall review and concur with Government-prepared transmission plans, or provide corrections/alternatives, within 48 hours of submission.

3.2.5.4.

Baseline Link Budgets - The Contractor shall provide contiguous Ku Band satellite bandwidth and transponder power sufficient to satisfy the baseline T-BAUD configuration shown in Appendix D and meet the circuit performance requirements in paragraph 3.4.3. The bandwidth and power must satisfy the number of links, data rates (symmetrical), and specific operating locations shown in Appendix D based on all remote Government terminals being TROJAN SPIRIT II, 2.4 meter Ku Band systems defined in Appendix C, Item A. The Contractor shall include detailed link budgets developed in accordance with paragraph 3.4.3., fully justifying the total proposed amount of satellite bandwidth and power needed to satisfy the baseline T-BAUD configuration, as well as the power and bandwidth required for the Contractor-provided terminals on the same transponder.

3.2.5.5. TNCC Modems - For T-BAUD service, the Contractor shall provide 70 each satellite modems, plus appropriate spares, to allow up to a maximum of 70 each active SCPC satellite links within the T-BAUD bandwidth at any given time. These modems shall be capable of operation at a maximum of 8.448 Mbps and compatible with the Comtech EF Data SLM 3650 and SLM 5650 satellite modems installed in the Government-owned terminals. The Contractor-provided modems will also be capable of TURBO FEC coding.

3.2.6.

Bandwidth Capacity. The Contractor shall offer both full and partial transponder services as specified below.

3.2.6.1.

Full and Partial Transponder Service:

a.

Full Transponder Service. The Government has the authority to specify the transponder gain setting from the full range of those available and to allocate the entire transponder bandwidth and power exclusively to Government TROJAN users.

b.

Partial Transponder Service. The Government’s use of bandwidth within a transponder where the satellite operator sets the transponder operating point, and exercises sole control over the allocation of the transponder’s bandwidth and power.

3.2.6.2.

The Contractor shall offer satellite transponder bandwidth on a non-preemptible basis. Bandwidth shall not be preempted for any reason and shall be replaced in the event of failure.

3.2.6.3.

Unless otherwise specified, the Contractor shall offer transponder bandwidth on geosynchronous satellites, station-kept to within ±0.1 degree in both orbital longitude and inclination.

3.2.6.4. Initially, the contractor will provide three full transponders to be populated with carriers supporting T-BAUD (paragraph 3.2.5) and fixed, Contractor-provided, satellite terminals serving fixed TROJAN facilities in CONUS, Hawaii, Alaska, Puerto Rico and Virgin Islands (paragraph 3.2.1). The transponders will disperse across no more than two different satellites with the following coverage:

a) One (1) satellite transponder/satellite combination covering Full Coverage CONUS, Hawaii, Puerto Rico, Virgin Islands and best coverage Alaska (Fairbanks and south at a minimum).

b) Two (2) transponders (on a separate satellite from the 50 state coverage satellite) covering at a minimum Full Coverage CONUS, Puerto Rico and Virgin Islands.

3.2.6.5.

As defined in 3.2.5.3, the contractor shall provide task specific software to perform link analysis and prepare transponder plans for coordination with the satellite provider.

3.2.6.6.

The contractor shall provide transponders of adequate bandwidth (currently 36 MHz each) and power to support all of the carriers defined in Appendix D currently supported by AMC-04 and AMC-09.

3.2.7. TDMA - The Contractor shall design, procure, install, operate and maintain TDMA hub services at the TNCCs in support of deployed UCS terminals in the 50 states configured with iDirect NETMODEM 7350 equipment. Terminal performance specifications are defined in Appendix C. Satellite bandwidth will be provided under the Bandwidth Capacity requirement in paragraph 3.2.6. The Contractor shall make available data ports and equipment capabilities which will allow monitoring of TDMA services from the TROJAN Network Operations Center (TNOC).

3.2.8.

MF-TDMA SOTM - The Contractor shall provide MF-TDMA SOTM hub services supporting two different deployment concepts.

3.2.8.1.

CONUS - The Contractor shall design, procure, install, operate and maintain hub services at the Ft. Bragg TNCC to support CONUS deployed, transportable, SOTM satellite terminals configured with L3 Communications, LINKABIT MPM-1000 Internet Protocol (IP), Spread Spectrum, MF-TDMA satellite modems. Satellite bandwidth will be provided under the Bandwidth Capacity requirement in paragraph 3.2.6. The initial MF-TDMA network will consist of four (4) 1.8 meter antennas and eight (8) 18 inch antennas communicating and being controlled by Contractor-provided hub services at the Ft. Bragg TNCC. Transportable terminal performance specifications are defined in items “E” and “H” in Appendix C.

a) Coverage - Full Coverage CONUS, Puerto Rico and Virgin Islands.

b) DEMARC - The Government/Contractor DEMARC will be the serial input connector to the Government’s router equipment in the Ft. Bragg TNCC.

C) Constraints - Satellite service selected by the Contractor shall provide a better than 25 degree antenna take off angle from Full Coverage CONUS, Puerto Rico and Virgin Islands. Connectivity between the transportable terminal up/downlink location to the Ft. Bragg TNCC shall induce less than 0.500 seconds one way delay.

d) Initial bandwidth requirements: 12 MHz contiguous space segment, provided by the Contractor (paragraph 3.2.5).

e) Cross-strapped transponder configurations are not allowed for the MF-TDMA network.

3.2.8.2.

OCONUS - The Contractor shall design, procure, install, operate and maintain hub services at a location identified by the Contractor to support OCONUS deployed transportable, SOTM satellite terminals configured with L3 Communications, LINKABIT MPM-1000 Internet Protocol (IP), Spread Spectrum, MF-TDMA satellite modems. The MF-TDMA network will consist of four (4) 1.8 meter antennas and eight (8) 18 inch antennas communicating and being controlled by Contractor provided hub services at an up/downlink location proposed by the Contractor.

a) Coverage - Full Coverage Iraq initially. Expansion to Full Coverage Iraq/Afghanistan.

b) DEMARC - The Government/Contractor DEMARC(s) will be the serial input connector to the Government’s router equipment at the TNCCs. Connectivity will be the Belvoir or Bragg TNCC (not both at the same time) and switched at the discretion of the Government.

c) Constraints - Satellite service selected by the Contractor shall provide a better than 25 degree antenna take off angle from Iraq initially and finally Iraq/Afghanistan. Connectivity from the up/downlink location to the TNCC shall induce less than 0.500 seconds delay.

d) Initial bandwidth requirements: 12 MHz contiguous space segment, provided by the Contractor.

e) Cross-strapped transponder configurations are not allowed for the MF-TDMA network.

3.2.9.

C-Band Satellite Test Circuit. The Contractor shall provide a full period, full duplex 64/64Kbps C-Band satellite circuit for Government testing of C-Band RF packages installed on the TROJAN SPIRIT II and other terminals prior to deploying these terminals to a geographic region supported by C Band satellites. For this circuit, the Contractor shall provide sufficient C Band satellite bandwidth/power, based on a TROJAN SPIRIT II, 2.4 meter C band antenna performance specifications defined in Appendix C, Item A, with coverage of the 50 states. The Contractor shall adhere to the satellite link performance specifications of paragraph 3.4. in developing the link budget for this C-Band test circuit. The Government/Contractor DEMARC will be at the Ft. Belvoir TNCC Commercial Communications Interface (CCI) only, as defined in paragraph 3.2.2.

3.3.

Technical Interface Requirements. The Contractor shall meet the following technical interface requirements:

3.3.1.

Data Rates. SCPC TROJAN circuits are synchronous, full duplex or simplex, and both symmetrical and asymmetrical. Circuits may be unframed and unformatted. Other specified services will utilize TDMA and spread spectrum technologies. Site specific data rates (in Kbps) are shown in Appendix D.

3.3.2.

Interface. There are six different physical interfaces utilized in the TROJAN/IEW Network.

3.3.2.1.

TNCC for SCPC Services-

a) The interface at the TNCCs will be at the DCE (line) connector on the ADC patch panel in the CCI room in Constitution Hall, Building 2310, Ft. Belvoir, VA and the CCI room, Building 5353, Ft. Bragg, NC.

b) The Contractor is responsible for providing cabling from their equipment to the line side of the CCI patch panel in the CCI room. Pin out for the connector will be EIA-530 DCE.

c) The Contractor shall install their equipment in Government- provided equipment racks and utilize Government-provided AC power. For services which do not down link directly into vendor-provided antennas at the TNCCs, the Government will provide access to Government-provided, on-base, fiber optic or copper cabling to span the distance between the base Dial Central Office (DCO) and vendor's DEMARC point in the CCI room of the TNCC. The vendor retains responsibility for end-to-end (DEMARC-to-DEMARC) connectivity of all services it provides.

d) The Contractor shall provide all required timing and synchronization signals at an accuracy level adequate to provide service performance levels defined in paragraph 3.4. The Contractor shall develop and distribute reference timing to their satellite modems and configure the base band side of the modems to provide the Government an RS-530 interface IAW Table 3-1.

PURPOSE

DIRECTION

SIGNAL

DTE DCE

8,10

RECEIVER READY

(BALANCED)

2,14

SEND DATA

3,16

RECEIVE DATA

15,12

SEND TIMING

24,11

TERMINAL TIMING -------->

17,9

RECEIVE TIMING

SHIELD

SIGNAL GROUND

Table 3-1, Ft. Belvoir/Bragg DEMARC RS-530

3.3.2.2.

U.S. Government/Contractor DEMARC Point for Contractor-Furnished Fixed and Transportable Sites. For Contractor-furnished, remote, fixed TROJAN/IEW sites, the Contractor shall interface to a male, 37-pin connector which represents the Data Termination Equipment (DTE). Pin assignments for the DCE interfaces have been defined in Table 3-2. The 37-pin connector shall be the Government/Contractor DEMARC point.

a) Commercial Communications Equipment Installation at Remote Sites. The Contractor shall install its indoor equipment into a single Government Furnished Property (GFP) cabinet shared with U.S. Government equipment at Fixed Sites. Figure 1 illustrates the rack face of a typical GFP cabinet and identifies the available space reserved for Contractor use.

b) Electrical power for Contractor-installed equipment at Government sites will be provided by the Government. The power sources may be 110 VAC/60 Hz, or 220 VAC/50 Hz, depending on the location.

PURPOSE

13,31

RECEIVER READY

4,22

6,24

5,23

17,35

TERMINAL TIMING -------->

8,26

Table 3-2, Distant Stations DEMARC RS-449

3.3.2.3.

Relay Sites. A relay site is a Government location where the circuit(s) does not terminate into TROJAN/IEW user equipment, but continue to a distant location using other communications. The only relay site currently in operation is at the Naval Communications Activity, Wahiawa, HI. This site interfaces to Pacific based TROJAN fixed site locations serviced by the Defense Satellite Communications Services (DSCS) station. The Contractor shall interface to a male, 37-pin connector which represents the DTE. Pin assignments for the DCE interfaces are defined in Table 3-3. The 37 pin connector shall be the Government/Contractor DEMARC point. The Contractor shall provide a DCE interface in accordance with EIA Standard RS-449 balanced as specified in Table 3-3. The interfaces shall be balanced, synchronous, and capable of handling the data rates listed in Appendix D.

a) Commercial Communications Equipment Installation at Relay Sites. The Contractor shall install its indoor equipment into Government Furnished Property (GFP) cabinet shared with U.S. Government equipment at Relay Sites.

b) Electrical power for Contractor installed equipment at Government relay sites will be provided by the Government.

PURPOSE

4,22

6,24

5,23

17,35

STATION CLOCK

8,26

Table 3-3, Relay Sites RS-449

3.3.2.4.

Government/Contractor DEMARC Point for Government- Furnished Transportable Satellite Terminal Sites. For transportable sites, the Contractor shall provide the required transponder power and bandwidth. The DEMARC is the face of the antenna reflector.

3.3.2.5.

TDMA. The Government/Contractor DEMARC will be the RG45, 10/100 BASE T ports of the Government-provided router switching equipment located at the TNCCs. The DEMARC point for the Government-owned terminals will be at the face of the antenna reflector.

3.3.2.6.

MF-TDMA SOTM. The Government/Contractor DEMARC will be the RG45, 10/100 BASE T ports of the Government-provided router switching equipment located at the TNCCs (OCONUS/CONUS configuration). The DEMARC point for the Government-owned terminals will be at the face of the antenna reflector.

Figure 3-1 — Typical CCI Rack

3.4.

Performance Requirements.

3.4.1.

General. The Contractor shall provide leased communications services, CONUS and OCONUS, that are operational on a "full-time", 24-hour/day basis. Unattended operation of Contractor-owned equipment is permitted at remote fixed and relay sites, provided that the Government's requirements for availability, reliability, maintainability and digital performance are met. The performance requirements are divided into two cases:

3.4.1.1. Case 1: If the Contractor provides fixed or transportable communications terminals at both ends of the link and the DEMARC points at each end of the service are the connectors as described at Tables 3-1, 3-2 and 3-3, the Contractor is responsible for meeting the requirements of paragraph 3.4.2.

3.4.1.2.

Case 2: If the Government provides the satellite communications terminal(s) at one or both ends of the link, and the DEMARC point for the Government-provided terminal is at the surface of the antenna reflector, the Contractor is responsible for meeting the requirements of paragraph 3.4.3.

3.4.2.

Contractor-Provided Terminal Circuit Performance for SCPC services. The Contractor shall ensure that each end-to-end circuit meets the performance requirements listed below, regardless of data rate.

3.4.2.1. Percent Error Free Seconds (% EFS): Fewer than 3.5 percent of 1 second intervals shall have any errors averaged over 24 hours (equivalent to 96.5 percent error free seconds).

3.4.2.2.

Degraded Minutes: Fewer than 10 percent of the 1 minute intervals shall have a Bit Error Rate (BER) of 1 X 10-6 or worse.

3.4.2.3.

Severely Errored Seconds: Fewer than 0.2 percent of one second intervals shall have a BER of 1 X 10-3 or worse.

3.4.2.4.

Jitter. The amount of jitter induced by the leased communications network on an end-to-end basis shall be less than 5 percent of the data unit interval.

3.4.2.5.

Mean-Time-to-Loss of Bit Count Integrity (MTTLBCI). The MTTLBCI for any end-to-end circuit shall be one (1) or less loss of BCI in 24 hours.

3.4.2.6.

Delay. The end-to-end transmission delay on any Contractor-provided circuit shall not exceed 0.550 seconds, regardless of the transmission medium used.

3.4.2.7.

Availability. The DEMARC-to-DEMARC link availability shall be equal to or greater than 99.5 percent for 24 hours/day averaged over a period of 30 days. A period of unavailability begins when the BER in each second is 1X10-4 or worse for a period of 10 consecutive seconds. These seconds are counted as unavailable time. The period of unavailable time ends when the BER for each second is better than 1X10-4 for a period of 10 consecutive seconds. These 10 seconds are counted as available time.

3.4.2.8.

BER shall be better than 1X10-7, averaged over 24 hours.

3.4.2.9.

Link Budgets. The Contractor shall provide link budget analysis in his own format which will assure that all specifications of paragraph 3.4.2. are met. The link budget analysis shall clearly define and list:

1)Satellite characteristics, including G/T, required saturated flux density, transponder back off, gain step setting, downlink EIRP 2)Link margins, including rain model used and predicted attenuation, and other assumed margins 3)Link parameters, including coding rate, required Eb/No, data overhead, modulation type, allocated bandwidth, interference components (such as transponder, adjacent satellite, cross polarization, etc.) and resulting link availability 4)Ground Terminal characteristics including G/T, required uplink EIRP, and pointing losses.

The analysis shall define the required satellite power and bandwidth for each link in terms of power in Watts and bandwidth in MHz and the percent of transponder power and bandwidth required.

3.4.3.

Government-Provided Satellite Terminal(s) At One Or Both Ends Of The Link Operating In SCPC mode.

3.4.3.1.

Link Budgets. The Contractor shall provide link budget analyses in his own format for the links using terminal performance specifications in Appendix C for known Government Transportable Satellite Terminals. Appendix D identifies the terminals which can be expected to be assigned to various circuits in this PWS. If a Government Transportable Satellite Terminal is used other than those listed in Appendix C, the Government will furnish the terminal's specifications to the Contractor. The link budgets will allow the link to operate at the same performance levels as identified in paragraph 3.4.2.

3.4.3.2.

The Contractor shall provide satellite access, troubleshooting and restoral support to deployed TROJAN transportable satellite terminals being serviced by Contractor- provided equipment at the TNCCs. In the event testing with the deployed Government terminal reveals problems in meeting performance standards defined in paragraph 3.4.2., the Contractor shall isolate the problem to Contractor-owned or Government-owned equipment. In the event the problem is traced to Contractor owned equipment, the Contractor shall immediately perform corrective measures to bring performance of the service in line with that defined in paragraph 3.4.2. If the problem is traced to Government-owned equipment, the Contractor shall assist the Government terminal operators in the troubleshooting of their equipment.

3.4.4.

Government-Provided Satellite Terminals At One Or Both Ends Of The Link Operating in TDMA, MF-TDMA SOTM Mode.

3.4.4.1.

The Contractor shall offer terms, conditions and performance standards for TDMA and MF-TDMA SOTM services defined in paragraph 3.2.7. and paragraph 3.2.8.

3.4.4.2.

Link Budgets. The Contractor shall provide link budget analyses as well as unique TDMA operational parameters (i.e. time slots, spectrum spreading factors, etc) in his own format for the links using terminal performance specifications in Appendix C, items E, G and H. Appendix D identifies the terminals which can be expected to be assigned to various TDMA/MF TDMA networks.

3.5.

Maintenance.

3.5.1. The Contractor shall provide labor, supervision, materials, tools, test equipment, calibration, and services as necessary to provide complete operations and maintenance support for all Contractor-furnished equipment. The maintenance of all Contractor equipment and space segments are the sole responsibility of the Contractor. The Contractor shall operate and maintain all Contractor-provided hardware and space segments consistent with the availability and other performance standards identified in this PWS. In the event a disruption of service is in progress or predicted, the Contractor shall so advise the Government by notifying the INSCOM TNOC at (703)706-1063. The Contractor shall establish a means, acceptable to the Government, by which the Government can advise the Contractor that a maintenance or operational emergency exists.

3.5.1.1.

Scheduled Maintenance. The Contractor shall provide written notification to the INSCOM Contracting Officer's Representative (COR) and the designated Government TROJAN/IEW representative(s) responsible for a site before initiating any maintenance or maintenance related activities at that site impacting on existing services. Unless otherwise authorized by the Government, the Contractor shall provide a 45 day written advance notice to the COR of any planned outage(s), including space segment outage(s), that will or could cause an interruption to, or degradation of, system operation. The Contractor shall also notify the COR of any action to be taken at that site that will or could affect the operation of any other TROJAN/IEW site(s).

3.5.1.2.

Unscheduled Maintenance. The Government will notify the Contractor when maintenance of an emergency nature exists. The Contractor shall initiate corrective action in accordance with the response times detailed below. The Contractor shall maintain sufficient technical personnel with current passports and visas available to meet this response criterion.

3.5.2.

Response Time. The Contractor shall operate and maintain all Contractor-provided hardware and space segments consistent with the availability and other performance standards identified in paragraph 3.4.2. As a minimum, the Contractor shall be responsible for initiating corrective action as follows:

3.5.2.1. TNCCs - The Contractor shall provide sufficient staffing for 24 hour/day, seven day/week, 365 day/year on-site monitoring, restoration and circuit activation services.

3.5.2.2.

Unmanned OCONUS/CONUS Gateway Locations (Wahiawa, HI)- On-site within 2 hours.

3.5.2.3.

Remote CONUS Sites- In route within 2 hours.

3.5.2.4.

Remote OCONUS Sites - In route within 4 hrs. At OCONUS locations that require visas that cannot be obtained in advance of Government approval to enter the area, the Contractor shall be in route as soon as possible but not later than 72 hours after notification.

3.5.3.

The Government may require enhanced response times to increase availability rates at specific sites in the future.

3.5.4.

Satellite Channel or Equipment Failure. The Contractor shall take action(s) to restore any Contractor- provided failed channel or equipment associated with the TROJAN/IEW System in accordance with paragraph 3.4.

3.6.

Reserved 3.7.

National Emergency

3.7.1. The Contractor shall continue to provide on-site support to all sites during all periods of hostile fire/imminent danger circumstances.

3.8.

Timing and Synchronization. The TROJAN leased communications circuits are both domestic and international and will traverse through many different timing regions utilizing different types of transmission equipment. The Contractor shall take the necessary actions to ensure that circuit synchronization is achieved such that MTTLBCI is kept within the specified limits as defined in paragraph 3.4.2.

3.8.1.

U.S. Government Sites. At all U.S. Government sites, except the TNCCs and the relay sites, the Contractor shall provide an external timing or clock signal (Send Timing) from DCE DEMARC for the timing and synchronization of the Government equipment at those sites.

3.8.2.

Earth Terminal Complex, Ft. Belvoir, VA/Ft. Bragg, NC. Timing and synchronization of Contractor-furnished equipment at Ft. Belvoir/Ft. Bragg will be achieved by a Contractor-furnished station clock, which is traceable to the UTC via the U.S. Naval Observatory, and requires the Contractor to provide Send Timing at the DEMARC point. The station clock will have accuracy and stability on the order of +/- 7 X 10-12 and +/- 3 X 10-12. The Contractor shall provide any and all timing and synchronization equipment (i.e., buffers, etc.) to interface with the Government equipment. All leased communication lines provided by the Contractor shall be synchronized prior to interfacing with Government equipment. Figure 3-2 illustrates the timing and synchronization configuration at Ft. Belvoir. It also applies to Contractor services at the Ft. Bragg TNCC.

Figure 3-2 Ft Belvoir Timing and Synchronization

3.8.3.

Relay Sites. For each circuit, the Government will provide a station clock at the same rate as the received data rate of the circuit. Station clock at relay sites will appear at the DEMARC as defined in Table 3-3.

3.9.

Management Requirements.

3.9.1.

Government Management. The Government has the right to monitor the system design, implementation, control, and operation of the leased system during the life of the contract. This will be accomplished through Quarterly In Process Reviews (QIPR) that are scheduled by the Government. Implementation of Government-approved changes resulting from such reviews shall be the responsibility of the Contractor. The Contractor shall participate in such reviews, furnish all data necessary for conducting the review and submit hard copies of all briefing materials to the Government. The Contractor shall provide unrestricted access to all documentation and associated materials reflecting the design, configuration, and performance of the leased system.

3.9.2.

Management Plan. The Contractor shall provide a Management Plan that governs all actions required to transition the existing TROJAN leased communications service requirements to the new TROJAN/IEW leased communications services. The Management Plan will detail all actions required to operate and maintain the TROJAN/IEW system consistent with the performance criteria contained in this PWS. Further, the Management Plan shall describe in detail, at a minimum, the Contractor's proposed structure and methodology for planning, engineering, executing, testing, transitioning, operating and maintaining, and controlling, all requirements of this PWS throughout the life of this contract.

3.9.2.1.

The Management Plan is intended to serve as the Government/Contractor coordinated instrument that describes the specifics of the Contractor's plan and schedule to implement all elements of this contract. The Management Plan will to be used for several purposes, to include:

a) Transition - The Management Plan will detail proposed transition process, schedule and test/acceptance procedures for all services being transitioned to the new contract. It will be used for monitoring the Contractor's progress in performing transition tasks. To minimize disruption to the customer community, INSCOM G6/TROJAN Management Office (TMO) will approve cutover schedules and coordinate individual circuit downtime with the users. In this regard, the maximum downtime for any given site during transition shall not exceed 24 hours unless otherwise approved by the Government.

b) Document the Contractor's plan to operate and maintain the transitioned services.

c) A baseline document to be modified as necessary to reflect TROJAN/IEW program evolution.

d) The basis for reporting during QIPR and/or other interaction between the Government and the Contractor.

3.10.

Host Nation/Connection Approval (HNA). Host nation approval and/or connection approval may be required in any or all of the countries listed in Appendix D. It is the responsibility of the Contractor to acquire appropriate Landing Rights/HNA/Terminal Licensing for any Contractor-provided equipment/services. When requested, the Contractor shall coordinate and acquire Landing Rights/HNA/Terminal licensing for Government-owned and operated terminals being supported by the TROJAN network using Contractor-provided space segment services. Failure to obtain appropriate approvals in sufficient time shall not be a cause for not obtaining full operational capability by the end of the transition period. Two OCONUS locations are currently being supported with HNA/Licensing coordination for Government-owned terminals.

a) Okinawa- One Government-owned transportable terminal.

b. Korea - Six Government owned transportable terminals.

3.11.

Telecommunication System Installation Plan (TSIP)(CDRL A0001). The Contractor shall provide a TSIP in accordance with the CDRL for each TROJAN/IEW location where Contractor-owned facilities and equipment are proposed. In the case of sites where a foreign vendor will provide the service, any information received from the foreign vendor shall be provided to the Government. Each TSIP (CDRL A0001) shall be delivered, per the CDRL, to the Government 30 days prior to scheduled installation start. At sites where new facilities are proposed, the Contractor shall perform a joint Government/Contractor site survey, satisfying, at a minimum, requirements identified in paragraph 6.0.

3.12.

Management Meetings/Conferences and Reports. The Contractor shall plan for, conduct, and report on all meetings/conferences between the Contractor and the U.S. Government as well as host nation officials. All Contractor costs associated with meeting and conference attendance shall be incidental to the contract and not separately billed. A Conference Agenda and Meeting Report shall be prepared by the Contractor and submitted for each meeting/conference held between the Contractor and the Government. The following meetings/conferences and Agenda/Meeting reports represent the minimum requirements. Additional meetings/conferences may be scheduled as determined by the Government.

3.12.1.

Design Review. Within 15 calendar days after award of contract there shall be a Design Review at the Contractor's facility. At that time, the Contractor shall distribute to the Government a revised Management Plan.

3.12.2.

QIPR. In-process reviews (IPRs) shall be conducted at least quarterly throughout the transition period at locations to be determined by the Government. During the post transition period, periodic IPRs will be held at the discretion of the Government. IPRs shall enable the Government to observe the work accomplished and to review the content and format of the existing data for conformance to the PWS. The Government will provide guidance and direction to the Contractor relative to the contractual effort during these reviews. When requested by the Government, the Contractor shall provide an updated Management Plan. During QIPRs, the Contractor shall provide an updated report on activities related to the contract. At a minimum, the Contractor's report will include:

a) Key dates/schedules relevant to installation, testing, or other critical events.

b) A narrative of outstanding problem areas and their resolution status.

c) A discussion of new problem areas being encountered or anticipated, their effect on the project, and steps being taking to resolve the situation.

d) A summary of future plans along with recommendations or proposals the Government should consider.

3.12.3.

Weekly Conference Calls. The Contractor shall initiate a weekly telephonic conference. This telephonic conference is chaired by the Contracting Officer (KO) and will include participation from Government engineering, operations, and user organizations as well as the Contractor. Technical resources (i.e. telephone bridge services) will be provided by the Contractor.

3.13.

Conference Agenda. The Contractor shall provide the Government with an agenda to be used for all meetings between the Government and the Contractor. The agenda shall be in the Contractor's own format but shall address, as a minimum: The objective of the meeting, a topical outline, which organization is responsible for addressing specific issues, descriptions of the results of previous meetings, descriptions of milestones or problem resolution status, and identification of future milestones or problem areas.

3.14.

Meeting Reports. The Contractor shall provide the Government with a set of minutes, in the Contractor's format, documenting all meetings between the Government and the Contractor, within 14 days of completion of the meeting. This report shall be made available to the Government in the current version of MICROSOFT WORD.

3.15.

Exception Reporting. In the event a serious disruption of services/schedules occurs or is projected to take place, the Contractor shall submit a Project Status Report. These reports shall be submitted to the Contracting Officer’s Technical Representative (COTR) within 2 days of the precipitating event and independent of the periodic IPRs. Reports of this nature shall be preceded by an alerting telephone call to the Contracting Officer’s Representative (COR) and the TNOC. The follow-up written report shall be in the Contractor's format but address as a minimum:

a) Nature and impact of the problem.

b) Level of effort to resolve problem.

c) Projected schedule for resolution.

d) Point of contact and phone number for status.

e) Other relevant information deemed appropriate.

3.16.

General Requirements.

3.16.1.

Communications in Host Countries. In certain host countries, the Contractor may be required to acquire in-country segments from the local Public Telephone and Telegraph (PTT) authority for TROJAN/IEW services to/from/within their country. The Contractor shall be responsible for establishing and maintaining sound working relationships with the local national authorities responsible for providing leased communications services. In addition, the Contractor shall ensure that all regulatory matters required by either the host country or an international agency for implementation of leased communications services are quickly resolved. This includes, but is not limited to such actions as:

a) Obtaining Host Nation Approval, Landing Rights, equipment licenses.

b) Ordering the circuit(s) following Allied Long Lines Agency (ALLA)/NATO Long Lines Agency (NALLA) procedures (if required).

c) Obtaining frequency assignments/approvals.

d) If the Contractor is unable to obtain Host Nation Connection Approval that meets the Governments service date, a Status Report that states the problem, addresses mitigating actions taken by the Contractor, and outlines what is required to complete the action, will be issued to the Government.

3.16.2.

Site Preparation. The Contractor shall be responsible for all site preparation…