76_SMXG_T25_SECT_EO_IR_SOO-1_Redacted.pdf

STATEMENT OF OBJECTIVES (SOO)

F O R T H E

E L E C T R O - O P T I C A L / I N F R A R E D ( E O / I R ) S E N S O R S I M U L A T I O N

O N T H E T 2 5 S E C T P R O G R A M

O C T O B E R 1 1 , 2 0 1 6

1 PURPOSE

This Statement of Objective (SOO) defines the Government’s requirements for the following:

1) Addition of an EO/IR sensor simulation model into the T25 SECT;

2) Follow-Up Support;

3) Training

The current Undergraduate Combat Systems Officer Training (UCT) curriculum has a fundamental sensors training skillset gap. The Government has identified that the integration of sensors training into the UCT advanced syllabuses will close this gap and allow for any student to flow through EO/IR sensor training at varying levels of fundamental mission employment, i.e., part-task to whole-task operation, knowledge, skill, engagement tactics, etc.

As part of this effort, the contractor shall identify, assess, select, acquire, and integrate an EO/IR sensor suite simulation model into the T25 SECT baseline software to train UCT students. The contractor shall install and test the EO/IR model on the T25 SECT. The contractor shall provide updated documentation for all hardware, software, courseware, visual and sensor database changes, and SECT manuals.

The implementation objective for the T25 EO/IR Sensor Simulation enhancement is to utilize an existing, already developed EO/IR simulation model, and to maximize use of the existing T25 SECT hardware and software, including the existing visual system and databases. The only hardware and software development should be integration and tailoring, with the selection of an appropriate sensor display. An operational limitation that offers the operator the choice of either out-the-window display or EO/IR sensor display, but not both simultaneously is acceptable. Other than the optional limitation of simultaneous display of out-the-window and EO/IR sensor, there shall be no degradation of functional and performance capabilities of the T25 SECT as a result of this change.

The schedule for technical review, development, integration, and test for the of the EO/IR sensor capability modification shall adhere to the following:

a) System Requirements Review (SRR), Preliminary Design Review (PDR), and Critical Design Review (CDR) (via any means, e.g., TELCON), shall be conducted, culminating with EO/IR sensor prototype integration and checkout for operator review and comment at NASP within 3 months after contract award (ACA). Reviews may be combined/concurrent. Technical Interchange Meetings (TIMs) with SMEs and program management may supplement technical reviews as needed to promote rapid information and data flow and build-up between developers and operations users. Government representatives may schedule periodic status updates with the contractor team to assure integrated team alignment.

b) Final government acceptance testing (GAT) shall be conducted at NASP on any appropriate number of SECT student stations, and discrepancies resolved within 6 months of ACA.

c) At least one training lesson shall be tested in accordance with the sensor training concept.

2 BACKGROUND

The T25 SECT does not have an EO/IR sensor model in its simulator avionics/systems models. EO/IR sensors are ubiquitous on USAF aircraft. EO/IR sensor operation and use is now a fundamental CSO skill.

AETC approved changes to the UCT program, allow training tracks to be tailored for different major weapon systems, including sensors management and employment. AETC’s long-term permanent solution is based on the integration of various sensors into the T25 SECT baseline for part-task and whole-task sensor competency to provide varying appropriate levels of difficulty in the UCT program.

2.1 TASK DESCRIPTION

a) Integrate an existing EO/IR simulation model into the baseline SECT system software. The selected sensor model may require tailoring and tuning to meet UCT specific requirements, and for integration into the baseline software. It is expected that the contractor development team will work collaboratively with the Program Office and Air Force Subject Matter Experts (SME) to ensure that the all the UCT specific requirements are understood. At a minimum, the EO/IR sensor shall include the following capabilities:

1. Sensor Modes:

• IR (White hot, Black hot) – this can be a physics-based model with real time material classification, or a simple notational model where physics-based fidelity is not required, both options include dynamic hot spots that are driven by simulation events (e.g. heating engine compartment, hot wheels/tracks, hot gun barrel, persistent tracks on the ground).

• Low Light Television (LL TV) able to see ambient light and IR lasers.

• EO (Color, Black and White (BW) – simulates a visual-spectrum camera, natural color or grey scale, with wide and narrow.

• Sensor modes are subject to post-processing effects which include noise, focus, depth-of-field, level, gain, AC coupling, motion blur, and digital zoom.

2. Operational Capabilities include:

• Daylight Spotter Camera Target Detection, Recognition and Identification

• Azimuth and Elevation Steering via the Hand Control Unit (HCU)

• Zoom In/Zoom Out via HCU

• Laser Range Finding, IR Laser (Sparkle) and Target Illumination

• Point Mode / Rate Mode (i.e. Target Track / Stabilization) – defined in paragraph b) below

• Stow

3. Displayed Aircraft Data (to the extent that the data is already available on the system):

• Airspeed (KTS)

• Altitude (FT)

• Roll (DEG)

• Pitch (DEG)

• Vertical Velocity (FT/MIN)

• Heading (DEG)

• Time

4. Displayed Sensor Data:

• Azimuth FOV Indicator and Readout

• Elevation FOV Indicator and Readout

• Cross Hair

• Current Sensor Mode

• LASER Data (Military Grid Reference System (MGRS) ,ALT) (LASER and Track

Modes Only)

• Target Data (MGRS,ALT) The Target data is a function of where the sensor is looking and should be displayed on the sensor at all times

b) The EO/IR sensor simulation shall also include the following characteristics:

1. The simulation shall include a 20” simulated panel that mimics a computer monitor that displays the output of the EO/IR sensors and includes a pull-down menu that allows the operator to initialize and align the EO/IR sensor.

2. The simulated EO/IR sensor shall have the capability to illuminate a target using a laser so that another entity can deploy a weapon at that target.

3. The simulated EO/IR sensor shall include an interface to the existing Moving Map to display the EO/IR pointing angle and to input EO/IR target location in MGRS.

4. The simulated EO/IR sensor shall include its own INS and GPS.

5. Simulated EO/IR sensor shall include a “Point” mode and a “Rate” mode. The “Point” mode shall stay fixed on a given point regardless of how the ownship is maneuvering.

The “Rate” mode shall automatically update the EO/IR Azimuth and Elevation pointing angles so as to track a moving object (i.e. another entity).

c) Simulated EO/IR sensor shall include the following malfunctions:

1. INS alignment error (Student clears by initiating INS alignment through a menu selection on the 20” display)

2. Loss of GPS signal

3. Drift Rate Error

4. Power Loss

5. Loss of Azimuth turret movement

6. Loss of Elevation turret movement

7. Loss of EO camera

d) Additional Required Tasks:

1. Provide necessary spares for modified systems. These spares will be located such that the training throughput requirements will not be affected.

2. Provide TSSC and on-site operational and maintenance training as required. Revise and provide all necessary documentation.

3. Provide hardware and software updates to the TSSC.

4. Update all drawings and lists as affected by this modification.

5. Update course lessons and related courseware as affected by this modification.

2.2 COMMONALITY

a) The T25 SECT instructional features and simulated malfunction capability shall be updated to allow full instructor control over normal, abnormal, and emergency functioning.

b) The Contractor shall clearly delineate all risks in the proposal, their probability and consequence of occurring, mitigation plans, and recovery plans in case the risk(s) are realized.

c) The Contractor shall clearly, with the proposal, delineate all training limitations due to interconnection complexities.

2.3 SCHEDULE REQUIREMENTS

The proposal shall include a detailed Microsoft Project schedule. The schedule submitted with the proposal may be a separate project file from the basic contract Integrated Master Schedule (IMS) schedule, or it may be the IMS with this effort integrated. After contract award, this effort shall be tracked using the IMS IAW this SOO. Ensure total project duration is delineated starting with 0 day.

The schedule shall include time to integrate into the baseline SECT software load, at least one lesson/training scenario reflecting ready-for-training and ready-to-train.

2.4 TRAINING THROUGHPUT REQUIREMENTS

a) The Contractor shall coordinate the modification with the 76 SMXG scheduling function so that training throughput is not affected. The Contractor shall, in a timely fashion, work with 76 SMXG to identify any potential training impacts and workaround solutions.

b) 76 SMXG shall ensure that other tasks on the program do not affect this modification.

2.5 TSSC SUPPORT

No TSSC Level of Effort (LOE) hours shall be utilized for this ECP; however, the TSSC may support the Configuration/Data Management (C/DM), as well as any required site distribution tasks (i.e.

software updates, manuals, support technical reviews, TIMs, GAT, etc.). All TSSC support shall be clearly delineated in the proposal.

2.6 TECHNICAL REQUIREMENTS

2.6.1 FUNCTIONAL AND PERFORMANCE REQUIREMENTS

The EO_IR ECP shall adhere to the 76 SMXG T25 SECT EO_IR SOO.

2.6.2 QUALITY ASSURANCE REQUIREMENTS

a) Quality assurance shall be IAW the requirements of the contractor’s quality assurance processes.

b) The Contractor shall propose a logical mix of technical/program reviews for this effort.

c) Test planning shall be coordinated with AETC/A3FC, 76 SMXG, and the 479 Operations Support

Squadron (OSS).

d) Testing shall be done using an approved Acceptance Test Procedure (ATP).

e) The Contractor shall assume that the modification shall be tested by performing a performance/functional test (i.e., using the ATP(s)) and a Force Development Evaluation (FDE).

Government Acceptance Testing will be done by the Government Program Office (AFLCMC/WNS) and supported by the SME from the 76 SMXG and 479th Flying Training Group.

f) All damages to the T25 SECT are the responsibility of the Contractor.

2.6.3 WORKMANSHIP

Workmanship shall be IAW the requirements of this SOO. Software quality reviews shall be shown to the government upon request.

2.6.4 CONFIGURATION /DATA MANAGEMENT

a) C/DM shall be done IAW this SOO.

b) Data submittals shall be IAW the requirements of the SOO.

c) All T25 SECT related documentation, drawings, lists, etc. shall be updated to reflect any product baseline changes as a result of this effort.

d) In the proposal, the Contractor shall include a list of all CDRLS to be updated as part of this effort.

2.6.5 SUBCONTRACTOR MANAGEMENT

The Contractor shall ensure that their subcontractor(s) and vendors meet the subcontractor/vendor requirements of the SOO.

2.6.6 CYBERSECURITY

a) The Contractor shall design into the system the best practices of Cybersecurity which include confidentiality, integrity and availability to the level of categorization approved with the applicable overlays, authentication, and non-repudiation.

b) The Contractor shall protect the system against compromising security requirements IAW Assessment and Authorization (AA), INFOSEC, EMSEC, COMSEC, OPSEC, COMPUSEC, Physical Security, and Procedural Security.

c) The Contractor shall identify and document the applicability of the security controls as required by DoDI 8500.01, Cybersecurity; DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT); and NIST SP 800-53 Security and Privacy Controls for Federal Information Systems and Organizations for the system; the implementation of controls compliance, and technical measures recommended to meet or mitigate non-compliant controls.

d) For this project, plan for and coordinate with AETC/A3FC, 76 SMXG, and AFLCMC/WNSS compliance with Department of Defense (DOD) RMF, through AFI 33-200, Air Force Cybersecurity Management, Air Force Assessment and Authorization Program (AFAAP), Authority to Operate.

e) The contractor shall support an assessment of Cybersecurity impacts and provide Cybersecurity technical support and documentation.

2.6.7 SOFTWARE RIGHTS

a) T25 source code modified as a result of integrating an existing EO/IR Sensor suite simulation model will adhere to DFAR 252.227-7017 Identification and Assertion of Use, Release, or Disclosure Restrictions (JAN 2011).

b) The EO/IR Sensor suite simulation model, if privately developed or uses Internal Research and Development (IR&D) funding may be delivered as a Dynamic Link Library (DLL) (i.e. no source code) to be licensed for use on the T25 for the express intent of student training only.

2.7 FOLLOW-UP SUPPORT

At the conclusion of deficiency correction, additional phone and email support for 76 SMXG personnel will be provided and will be limited to 100 hours of effort. Any additional support required after the 100 hours of effort can be executed via additional contract agreements between 76 SMXG and contractor.

2.8 TRAINING

Contractor will provide three (3) full 8-hour days T25 SECT hands-on training for two or three (2-3) 76 SMXG personnel at the NASP facility. The number of personnel will not exceed 3 individuals; the dates of the training will be mutually agreed upon. Travel days will be on a Monday and Friday, with training to be conducted during that Tuesday – Thursday calendar week. The training will be completed prior to the T25 EO/IR ECP final GAT; this training will be included in the contractor’s IMS. To facilitate government integration of the EO/IR deliverables into the T25 SECT environment, objectives for the training shall include the following:

• 8 hrs. – Overview of Overall T25 SECT Architectures o Training on T25 SECT software architecture down to subsystem level (i.e., instructor computer, student computer, MetaVR computer, radar computer), to include folder structure for executables and configuration files for each subsystem and placement of the EO/IR Suite within the architecture

• 8 hrs. – Integration Methodologies for T25 SECT o Training on re-compiling code modifications made to T25 SECT software to call new EO/IR

Suite software, using code analyzer (e.g., Beyond Compare) to generate code difference listing for T25 SECT software, loading and testing the EO/IR modification on the TSSC network, and pushing final code to T25 SECT subsystem computers.

• 8 hrs. – Troubleshooting Techniques and Question/Answer Block o Training on known errors in the EO/IR Suite software (e.g., error log types and remedies), troubleshooting approaches for interface issues between EO/IR Suite software and other T25 SECT software and between the EO/IR Suite software and capture card hardware, and freeplay questions and answers.

3 ACRONYMS

A3FC – Combat Systems Officer Programs Branch (AETC) AA – Assessment and Authorization ACA – After Contract Award AETC – Air Education and Training Command AFAAP – Air Force Assessment and Authorization Program AFI – Air Force Instruction ALT - Altitude AFB – Air Force Base AFLCMC – Air Force Life Cycle Management Center ATP – Acceptance Test Procedure

BW – Black and White C/DM – Configuration/Data Management CDR – Critical Design Review CDRL – Contract Data Requirements List COMPUSEC – Computer Security COMSEC – Communications Security DEG – Degree DLL – Dynamic Link Library DOD – Department of Defense DoDI – Department of Defense Instruction ECP – Engineering Change Proposal EMSEC – Emission Security EO– Electro-Optical FDE – Force Development Evaluation FOV – Field of View FT – Feet GAT – Government Acceptance Test(ing) GPS – Global Positioning System HCU – Hand Control Unit HQ – Headquarters IAW – In Accordance With IMS – Integrated Master Schedule INFOSEC – Information Security INS – Internal Navigation System IR – Infrared IR&D – Internal research and Development IT – Information Technology KTS – Knots LOE – Level of Effort LL – Low Light MGRS – Military Grid Reference System MIN - Minute NASP – Naval Air Station, Pensacola NIST – National Institute of Standards and Technology OH – Ohio OPSEC – Operations Security OSS – Operations Support Squadron Ownship – In training and simulation technology, ownship is the vehicle or platform being simulated (Aircraft). In visual systems the “ownship” sometimes means the principal eye-point for which an image is created.

PDR – Preliminary Design Review PWS – Performance Work Statement RMF – Risk Management Framework SECT – Simulator for Electronic Combat Training SME – Subject Matter Expert SOO – Statement of Objectives SRR – System Requirements Review TIM – Technical Interchange Meeting TSSC – Training System Support Center TX – Texas

UCT – Undergraduate Combat Systems Officer Training WNSE/WNSEB – Simulator Division, Engineering WNSS – Simulator Division, Program Management

3 ACRONYMS