SOW Updated.docx

CONTROLLED UNCLASSIFIED INFORMATION (CUI)

STATEMENT OF WORK (SOW)

FOR

309TH SOFTWARE ENGINEERING GROUP (309 SWEG)

INTERCONTINENTAL BALLISTIC MISSILE (ICBM) TELEMETRY INTEGRATED PROCESSING SYSTEM (ITIPS) TELEMETRY RECORDER/FRONT-END PROCESSOR REPLACEMENT

Hill Air Force Base, Utah

22 June 2023/1.0

1.0 INTRODUCTION

1.1 Purpose

The 309 SWEG 520th Squadron at Hill Air Force Base (HAFB) is to replace and upgrade the ITIPS. ITIPS is made up of a series of front-end processors that monitor and analyze over 2,500 parameters for ICBM sample tests. The ITIPS program supports the Western Range (WR) for the sole purpose to determine the health of the ICBM Minute Man (MM) III fleet and to abide by international treaties.

1.2 Scope

The ITIPS Program requires six (6) identical front-end processors that meet the requirements specified in Section 2 of the SOW.

1.3 Background

The ITIPS Program is located at Vandenberg Space Force Base (VSFB) and HAFB. To conduct the ICBM tests, the ITIPS requirement is to have two front-end processors in operation at the time of the launch and a spare front-end processor on the shelf in case one processor goes down. HAFB is the test bed for the actual ITIPS program at VSFB, so an exact match is needed at HAFB. Thus, the requirement is for six telemetry systems (front-end processors).

The current ITIPS system has been in place for over 10 years. The ITIPS Program is down to four front-end processors, three at VSFB and one at HAFB. One of the processors at VSFB fails regularly. When this happens, the processor at HAFB must be shipped to VSFB to be put on the shelf as the backup, otherwise the launch couldn’t take place. The technical team is doing all they can to keep the processors up and running by piecing the systems together from non-functional units.

2.0 REQUIREMENT

2.1 Front-End Processor Requirements

2.1.1 Be capable of processing 32 channels of Telemetry data plus 1 channel of time that supports both IRIG-B and IRIG-G sine wave amplitude-modulated formats.

2.1.2 Be capable of processing 32 channels of PCM data. The connectors shall be BNC with TTL logic. The supported PCM encodings shall be at least NRZ-S, NRZ-L, and RNRZ-L+15.

2.1.3 Be capable of ingesting and processing 32 channels of TMoIP data in the form of IRIG 106-13 Ch10-UDP and/or RCC218-20 or newer.

2.1.4 Be capable of processing 4.8kbps-30Mbps on each telemetry channel.

2.1.5 Have auto polarity detection for normal or inverted data on a channel-by-channel basis.

2.1.6 Be capable of frame synchronization with editable frame synchronization options of “Bits in Minor Frame”, “Frame Sync Pattern”, “Frame Sync Mask”, and “Frame Sync Size”.

2.1.7 Be capable of best source selection for the telemetry channels. The best source selector shall be able to:

· Align incoming data channels to prevent data repeat or loss.

· Exclude data channels that are out of lock.

· Function in different modes including in-lock-weighted, last-in-lock, data merging, etc.

· Handle up to 16 channels per selection.

· Allow 4 or more best source selector groupings of channels.

· Have a best data merge function that allows bit-level error checking/comparing.

· Be capable of processing PCM and TMoIP data streams or any combination of the two.

· Be capable of merging PCM channels with TMoIP channels.

2.1.8 Have a GUI capable of changing/editing all user options including but not limited to data stream source, type, bitrate, channels included in each best source selector, frame sync parameters, and recording options.

2.1.9 Have a GUI capable of editing each channel name/source and display the name/source.

2.1.10 Be capable of recording both incoming channels and the output of the best source selector in the same IRIG 106-13 compatible chapter 10 file.

2.1.11 Be capable of fitting in a 4U rack space with additional breakout boards if necessary.

2.1.12 Have at least 2 1000BASE-T network interfaces. The box must be able to support 2 fiber connections either through a SFP module or and additional/upgraded NIC.

2.1.13 Have an output TMoIP stream that is configurable for IRIG 106-13 Ch10-UDP and optionally RCC218-20 or newer.

2.2 Technical Training

The contractor shall conduct operations training after delivery of the front-end processors. The training shall be five (5) business days. The training shall be scheduled upon processors being shipped and take place at HAFB after delivery of the processors.

2.3 Technical Documentation

The contractor shall provide system operation and maintenance manuals sufficient for operation in both hard and soft copy. The Government shall be granted unlimited reproduction rights on the operation and maintenance manuals. (CDRL A001 Operation and Maintenance Manual)

2.4 Technical Support

The contractor shall provide twelve (12) months of technical support starting from the date of processor delivery.

2.5 Warranty

The contractor shall provide a warranty of 60 months from when the processors have been received and accepted.

3.0 General Information

3.1 Contract Management

Overall responsibility and approval reside with the Procuring Contracting Office. No conversation, recommendation, or direction, whether given directly or implied by Government personnel or representatives, will affect the scope, schedule, or price of the program covered by this SOW nor shall be acted upon by the contractor unless specifically directed in writing by the Contracting Officer (CO).

3.2 Delivery

The contractor shall deliver six identical front-end processors In Accordance With (IAW) the requirements of section 2. Deliveries shall be made 120 days after receipt of (ARO) award. All products shall be shipped to; 7278 4th St. Bldg. 100, Bay O, Hill AFB, UT, 84056-5203, ATTN: Gary Scott Larsson.

Reference

image1.png