Exhibit B - Scenario.docx

FA702221R0001

Exhibit B

SCENARIO

The mission system supporting atmosphere and space operations at Air Force Technical Applications Center (AFTAC) Headquarters receives data from United States Nuclear Detonation Detection System (USNDS) Integrated Correlation and Display System (ICADS) mission system in the form of small, individual files known as End Products (EPROs), as defined by the ICADS Offline Interface Control Document (ICD). EPROs provide sensor detection data (“mission triggers”) as well as many different forms of sensor State of Health, commanding, and satellite ephemeris data. EPROs are individual files which contain raw satellite telemetry (binary) data and ICADS preamble and post-amble data (metadata) taken from ICADS’ operational database. The functions of the AFTAC mission system (the “offline” mission system from the ICADS perspective) begins with the receipt of EPROs, which usually come in the form of Unix “tarball” (tape archive files, comparable to zip files) containing dozens of individual EPROs, at a rate of several tar balls per minute, 24/7/365, from two separate ICADS systems. As a result, operators may be presented with hundreds to thousands of EPROs at one time. To lessen the burden upon the operators concerning interpretation; the AFTAC mission system has multiple layers of automation to identify and to elevate priority information to the operators’ attention.

Given/Constraints:

1. A new spacecraft constellation with multiple sensors on each spacecraft is anticipated to enter service in 48 months. The sensor suite on each spacecraft will include optical, radio frequency, x-ray, neutron, and gamma sensors. Each sensor may or may not be an incremental improvement over previous or existing sensors but must be seamlessly integrated.

2. The draft ICD and sample data (in the form of EPROs described above) will be available approximately 36 months before spacecraft enter operational service. The first spacecraft will have a 6 month on-orbit checkout period when all sensors will be powered on and producing mission data in a test configuration. Sample algorithms for mission processing will also be provided by sensor designers approximately 36 months before spacecraft enter operational service. Algorithms may come in a variety of languages with various data storage configurations. Data and algorithms will address the needs of the USNDS mission and its operators but may not fully address the needs of AFTAC’s mission and its operators.

3. The current mission system is being migrated to an enterprise, system-of-systems network in accordance with the AFTAC Flight Plan, the AFTAC Digital Mobilization Policy (15 Jun 2020), and the AFTAC Software Development Strategy Document (Ver 1.0 dated 28 May 2020). See the technical library for additional documents.

4. AFTAC staff and leadership desire to migrate away from legacy software without a strong developer base; such software includes Fortran, C, and Motif.

5. Documentation of both the AFTAC mission system and ICDs ("ICADS Offline ICD") for previous satellite systems are available. See the RFP technical library.

6. On-site (AFTAC HQ, Patrick AFB) seating for the contract team is limited to 13 workstations.

7. The ability of the mission system to operate continuously, 24/7/365, is the squadron’s top priority.

8. The software will be deployed on a NetApps/Cisco Flexpod virtualized solution with a Red Hat Enterprise Linux operating system and Oracle databases.

Tasks:

1. Describe preparatory actions prior to implementing system changes. Include interactions with other contractors (to include DOE National Labs) and internal AFTAC partners. Describe handling of data ranging from binary satellite telemetry files through complex Oracle databases; describe handling of existing algorithms coded in a variety of languages.

2. Plan the work to integrate this new family of sensors into an existing mission system, given the constraints above for optical and neutron sensor data processing. Provide an Integrated Master Schedule (IMS) and manpower loading to fully implement optical and neutron sensor data processing, assuming sensor designers’ algorithms will need to be modified to support the AFTAC mission. The IMS and manpower loading should go no lower than three tiers.

3. Describe technical aspects associated with this work. Specifically, discuss technical tasks needed to go from documentation provided by sensor designers (to include sample data) to the ability of the mission system to fully analyze new sensor data, in synchronization with existing data, in a stable operational environment. Describe expected interactions with government team members and partners identified in the PWS needed to execute the tasks.

4. Constrain your answers to 20 pages, excluding all graphics and attachments.