9003-0003.doc

HQ AFSPC

CONTRACT INFORMATION

Provide study and modeling support, technical support, software enhancement (including modification, maintenance, configuration control, and data file teneration of runs) for the Space Surveillance Network Analysis Model (SSNAM)

8283 Greensboro Drive

McLean, VA 22102-3838

(Base + 1 Opt Yrs)

STATEMENT OF WORK

FOR

SPACE SURVEILLANCE NETWORK ANALYSIS MODEL

(SSNAM)

FOR

Headquarters Air Force Space Command/ XOCS - XPY - DRX

Revised 7 February 2006 9003-0003

1.0 DESCRIPTION OF SERVICES:

Provide study and modeling support, technical support, software enhancement (including modification, maintenance, configuration control, and data file teneraion and execution of runs) for the Space Surveillance Network Analysis Model (SSNAM). SSNAM is a large-scale simulation model developed under the sponsorship of HQ AFSPC/XOC. It is a “force structure analysis” model, which through simulation assesses the impact of closing existing sensor sites or adding new sites to the Space Surveillance Sensor Network (SSN). It models ground based radar and optical sensors as well as space based optical or IR sensors.

SSNAM also has an Event Analysis mode that can do coverage analysis for new launch and maneuver scenarios to determine such statistics as time to Element Set (Elset) #1.

SSNAM is a large, multi-language software system with over half a million lines of code. It runs under Windows 2000 on a load-shared network of 16 PC’s. The following table shows the details on lines of code:

A typical SSNAM catalog run takes ~10 hours on a cluster of 16 PC’s. The run is usually a simulation of a 40-day period of SSN operations for a full (~10,000 satellite) catalog. Each simulation day the Cheyenne Mountain Operations Center (CMOC) Tasker in SSNAM is run to assign the sensor tasking for the day (i.e. which sensors should obtain data for each satellite using actual sensor capacity data). For the selected sensors observations are simulated using detailed sensor models (SSNAM uses “probability of detection” models based upon satellite radar cross section (RCS) or visual magnitude and geometry of the sensor pass to determine whether an individual SSN sensor will have visibility for a particular pass. Realistic noise is applied to the simulated tracking data). Least Square batch orbit determination using the standard SGP4 ephemeris propagation model is then done on all satellites receiving data in that 24-hour period to obtain an updated elset, and then the cycle is repeated for the next day.

Statistics are collected during the 40-day simulation to reflect sensor loading/response to tasking, number of lost satellites, elset error growth rates, and average age of elsets. Statistics are grouped into near-earth, deep space, manned, and geostationary categories. Excel plots are generated to display results.

1.1 ORGANIZATION BEING SUPPORTED:

HQ AFSPC/XOCS

SMC/SY

HQ AFSPC/XPY

HQ AFSPC/ DRX

150 Vandenberg St. Suite 1105

Peterson AFB, CO 80914

1.1.1 MISSION: Model and simulate AFSPC Space Surveillance Network to support force structure decisions to improve Space Situational Awareness.

1.2 SPECIFIC REQUIREMENTS

The objective requirements include conducting SSN configuration studies and enhancing model functionality.

1.2.1 REQUIREMENT 1: SSNAM TECHNICAL SUPPORT TO OPERATIONAL STUDIES:

Contractor shall execute runs and prepared data for XPY. This task includes time necessary to meet with requesting users to determine their needs and design runs accordingly. Additionally, the contractor shall support bi-annual Integrated Product Team (IPT) meetings to discuss study requirements and results with government sponsors. The results of all runs and analysis will be provided electronically to and coordinated with HQ AFSPC/XOCS and HQ AFSPC/XPY prior to distribution to any user. All runs will be approved by HQ AFSPC/XOCS prior to initiation of work. Expected runs during the period of performance include:

1.2.1.1 Government estimate approximately two major studies, or four medium studies or 5 low studies or a combination of the three different studies. Each different study will be approved in the IPT process prior to execution.

1.2.1.2 Up to two new catalog mode sensor addition studies (GP) to support IPP analysis

1.2.1.3 Technical (e.g. database modification, parameter adjustment) support to XPY for XPY run event and catalog studies

1.2.1.4 DELIVERABLES:

Meeting minutes. (CDRL 0005)

1.2.2 REQUIREMENT 2: SSNAM SOFTWARE TOOL ENHANCEMENTS AND TECHNICAL SUPPORT

This task includes the following subtasks:

1.2.6.1 Enhance pass break logic to define viewing opportunities for Space Based Space Surveillance (SBSS) to be used in conjunction with the SP tasker.

1.2.6.2 Special Perturbation (SP) processing implementation analysis and prototype development design (i.e. sensor noise analysis, SP vector accuracy analysis, data distribution via server, run-time performance analysis)

1.2.6.3 Phase 1 of SP processing implementation (i.e. modified atmosphere model, high fidelity sensor noise, integrate SP tasker, update to F95 DC, update to LAMOD, load share tasker look angle calculation)

1.2.6.4 XPY SSNAM lab support for those tasks related to SP in this requirement (e.g. software installation, new hardware integration, SSNAM network configuration)

1.2.2.1 DELIVERABLES:

The contractor shall deliver the source code and documentation of software developed in support of this task. (CDRL0024)

1.2.3 REQUIREMENT 3: Space Situational Awareness Integration Office (SSAIO) Study and Modeling Support

This task includes incorporating aspects of the SP catalog to support SSAIO National SSA architecture analysis and development studies. The results of all runs and analysis will be provided electronically to and coordinated with HQ AFSPC/XOCS and HQ AFSPC/XPYC prior to distribution to the user. Expected tasks during the period of performance include (not in priority order)

1.2.3.1 Add additional sensors (new or modified models) to the SSN to support studies (e.g. “generic” S-Band Fence sensors) The Government estimates approximately no new and only one slightly modified model.

1.2.3.2 Increase the capacity of SSNAM to process a catalog of approximately 50,000 - 100,000 objects to include small debris.

1.2.3.3 Run catalog maintenance and selected event runs to inspect the added functionality of new sensors and expanded catalog capacity. The Government estimates approximately two catalog maintenance and zero event runs………

1.2.4 ADDITIONAL DELIVERABLES:

The contractor shall deliver a Monthly Status Report (MSR) by the 20th of each month covering activities of the preceding month. The report shall contain a list of personnel on each task, description of the work accomplished during the previous month, list of meetings attended, deliverables provided, travel accomplished, and funds expended during the period of performance by labor hour/category, with cumulative expenditures and associated funding remaining. (CDRL 0011)

1.3 TRAVEL.

No future travel expected

2.0 SERVICE DELIVERY SUMMARY

Para Performance Threshold

1.2.2.1.

1.2.3

No more than two (2) late documents per year and no more than five (5) days late. Nor more than one (1) set of corrections or edits and all corrections must be accomplished within five (5) working days.

through

1.2.3.

Contractor receives no more than two (2) formal customer complaints/contract discrepancy reports per year. The contractor successfully resolve customer complaints within 10 calendar days of receipt, 100% of the time.

3.0. Government Furnished Property and services

3.1. HARDWARE: See Appendix A

3.2. SOFTWARE: Microsoft Office environment. SSNAM software.

4.0 GENERAL INFORMATION

4.1 SECURITY. Contractor shall provide personnel with clearances commensurate with the DD 254, Department of Defense Contract Security Classification Specification.

APPENDIX A