T25_SOW-Revision_(Final).pdf

STATEMENT OF WORK

FOR

T25 Simulator for Electronic combat Training (SECT) for adding an Electro-

Optical / Infrared (EO/IR) Sensor simulation model

FOR

76 SMXG / 555 SMXS

OC-ALC/OBCA

26 January 2017

Scope:

The Contractor shall provide all engineering labor, follow-on support, training, equip-ment/material requirements, and implementation schedule necessary to perform adding an Electro-Optical / Infrared (EO/IR) Sensor simulation model to the AN/FSQ-T25 Simulator for Electronic Combat Training (SECT) located at Naval Air Station Pensacola (NASP).

The Contractor shall be responsible for insuring all services, parts and Original Equipment Manufacturer (OEM) components provided under this contract conform to the manufactur-er’s equipment specifications.

Item Description:

Contractor shall provide updates to the T25 Simulator for Electronic Combat Training (SECT) to add an Electro-Optical / Infrared (EO/IR) Sensor simulation used for training Combat Systems Officers (CSO) in its fundamental usage and mission employment.

This effort will include at least two (2) software deliveries, hardware installation, follow-on support (i.e., on-site, electronic communication, and telephone), and training sessions at Na-val Air Station Pensacola (NASP).

As part of this acquisition, the contractor shall identify, assess, select, acquire, and integrate an EO/IR sensor suite simulation model into the T25 SECT baseline software to train Under-graduate Combat Systems Officer Training (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, course-ware, visual and sensor database changes, and SECT man-uals.

The EO/IR Sensor simulation requires the MetaVR visual system Version 5.9. Currently, the T25 includes the MetaVR visual system Version 5.9, which is used for an Out-The-Window (OTW) visual scene, providing additional situational awareness to the student. Since the abil-ity to simultaneously provide both the OTW visual scene and the EO/IR sensor in a scenario is not required, no additional MetaVR licenses will be required.

The EO/IR Sensor simulation model requires a Hand Control Unit (HCU). The existing T25 HCU is sufficient and will not be required to be replaced. The initial mapping of HCU con-trols to the EO/IR Sensor simulation will be determined during Software Readiness Review (SRR) and tested during the first delivery.

First Delivery:

The following requirements will be included in the first delivery within 3 months of contract award:

• IR (White Hot, Black Hot) Sensor Mode

• Low Light Television (LLTV) Sensor Mode

• EO (Color, Black and White (BW)) Sensor Mode

• Daylight Spotter Camera Target Detection, Recognition, and Identification

• Azimuth and Elevation Steering via the HCU

• Zoom In / Zoom Out via the HCU

• Laser Range Finding

• Point Mode / Rate Mode

• All Aircraft Data Displayed

• Azimuth FOV Indicator and Readout Displayed

• Elevation FOV Indicator and Readout Displayed

• Cross Hair Displayed

• Current Sensor Mode Displayed

• 20” Simulated Panel including pull-down menus

• Power Loss Malfunction

• Loss of Azimuth turret movement Malfunction

• Loss of Elevation turret movement Malfunction

• Loss of EO Camera Malfunction

***To maintain T25 SECT continuity and after first delivery installation, the contrac-tor shall demonstrate functionality and operability to the Government Subject Matter Expert (SME).***

Second delivery:

The following requirements will be included in the second delivery within 6 months of con-tract award:

Updates to EO/IR Sensor Simulation

• Implement EO/IR Post Processing Effects

• Enhance EO/ IR Laser operation

• Enhance Laser Data Display

• Enhance Target Data Display

• Add Interface to Moving Map and Instructor Station

• Add EO/IR GPS and INS

• Add INS Alignment Error, Loss of GPS Signal, and Drift Rate Error Malfunctions

• Add ability for the script to evaluate:

o Which entity is being designated with the laser o Has the designated target has been destroyed o Is an entity is in the Field of View (FOV) of the EO/IR Sensor

• Update the Instructors Manual o Add EO/IR Sensor o Add EO/IR Sensor usage of HCU

• Update the Mission Generation Manual o Add EO/IR Sensor usage of HCU

• Update the Software Users Manual

• Develop one ATP that will verify all SOO Requirements, including functionality in other areas (i.e. Moving Map, Instructor Station, and Environment)

• Add the EO/IR Sensor to one existing scenario for use with the ATP

Updates to Moving Map

• Display EO/IR Line of Bearing (LOB) / Pointing Angle on Map

• Implement Military Grid Reference System (MGRS) to the extent that Falcon-view supports it

• Update the Instructors Manual for Moving Map

Updates to Environment

• Implement Laser Target Designation Capability

• Update the Software Users Manual

Updates to Instructor Station / Mission Builder

• Display EO/IR Line of Bearing (LOB) / Pointing Angle on Map

• Display EO/IR Designated Target on Map

• Display EO/IR Sensor State Data in Student Monitor Dialog

• Update IR Signal Properties to support Laser Signals

• Update the Instructors Manual o Map updates o Student Monitor Dialog updates o IR Signal Properties updates

• Update the Mission Generation Manual o IR Signal Properties updates Update the Software Users Manual

***At the second delivery and prior to Final Government Acceptance Testing, Re-gression Testing will be performed to ensure the T25 SECT maintains the GOLD Load (Base Line Operating Standard) to prevent training degradation and system failure. The contractor shall provide necessary scripting to demonstrate functionali-ty and operability to the Government Subject Matter Expert (SME). ***

Deficiency correction will be completed within 6 months of contract award.

Hardware:

Since the EO/IR Sensor simulation will be displayed on a monitor connected to the Simula-tion PC (instead of the large top monitor connected to the Visual PC), an additional capture card and cable will be needed to connect the Visual PC to the Simulation PC. The only slot that is available in the Simulation PCs is a PCI Express slot (see figure below). As a result, a different capture card than the one currently in use by the T25 must be used for this ECP. The following shall be provided by the contractor:

• 25 x Datapath VISIONRGB-E2S Capture Cards

• 25 x DVI-IS-6-MM Cable Assembly

• All Capture Cards necessary to fulfill the requirement shall be installed on-site by the contractor

• Spare Capture Cards will be left to 76 SMXG / 555SMXS personnel

• All necessary cables and other hardware to complete the requirement shall be provided by the contractor.

Follow-On Support and Training:

At the conclusion of deficiency correction, additional follow-on support (i.e., on-site, elec-tronic communication and telephone) for 76 SMXG / 555 SMXS personnel will be provided and limited to 100 hours in addition to the required three (3) 8-hour hands-on training days.

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

During this upgade the Contractor shall provide three (3) full 8-hour days of T25 SECT hands-on training for six (6) 76 SMXG / 555 SMXS personnel at the NASP facility. The dates of the training will be mutually agreed upon by the Contractor and the on-site personnel.

Travel days will be on a Monday and Friday, with training to be conducted during that Tues-day – Thursday calendar week. The training will be completed prior to the T25 EO/IR Simu-lation model’s final Government Acceptance Testing (GAT). In order to facilitate government integration of the EO/IR deliverables into the T25 SECT environment, objectives for the training shall include but not limited to the following:

• 8 hrs – Overview of Overall T25 SECT Architecture The Contractor will provide training on T25 SECT software architecture down to subsystem level (i.e., instructor computer, student computer, MetaVR computer, radar computer), to in-clude folder structure for executables and configuration files for each subsystem and place-ment of the EO/IR Suite within the architecture.

• 8 hrs – Integration Methodologies for T25 SECT The Contractor will provide 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 modi-fication on the Trainer System Support Center (TSSC) network, and pushing final code to T25 SECT subsystem computers.

• 8 hrs – Troubleshooting Techniques and Question/Answer Block The Contractor will provide training on known errors in the EO/IR Suite software (e.g., error log types and remedies). Training will include troubleshooting approaches for interface issues between EO/IR Suite software and other T25 SECT software, approaches for debugging inter-face issues between the EO/IR Suite software and capture card hardware, and free play ques-tions and answers.

Software Rights:

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).

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 on-ly.

Cybersecurity:

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 ap-plicable overlays, authentication, and non-repudiation.

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

The Contractor shall identify and document the applicability of the security controls as re-quired 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 implementa-tion of controls compliance, and technical measures recommended to meet or mitigate non-compliant controls.

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 Cyber-security Management, Air Force Assessment and Authorization Program (AFAAP), Authority to Operate.

The contractor shall support an assessment of Cybersecurity impacts and provide Cybersecuri-ty technical support and documentation.

Emergency Procedures:

The Contractor personnel shall follow the direction of the Government personnel with regard to emergency procedures, such as fire, tornado, active shooter, bomb threats, or other emer-gency. It is the responsibility of the Contractor to provide guidance and to establish proce-dures for its employees to respond to an emergency. It is the Contractor’s responsibility to account for their employees following an emergency evacuation. The Contractor personnel shall participate with the Government personnel in all fire and tornado drills at no additional cost to the Government.

Health & Safety on Government Installations:

While performing work under this contract the Contractor shall comply with all applicable federal, state and local regulations regarding occupational safety and health. During the exe-cution of the contract, the Contractor shall notify the Contracting Officer (CO), Contracting Officer Representative (COR), and Government Contract Administrator (CA) within one (1) business day of any damage to Government property in which the dollar value exceeds $500,000.00 and within two (2) work days, for any damage to Government property less than $500,000.00.

Mishap notifications shall contain, as a minimum, the following information:

• Contract, Contract Number, Name and Title of Person(s) Reporting

• Date, Time and exact location of accident/incident

• Brief Narrative of accident/incident (Events leading to accident/incident)

• Cause of accident/incident, if known

• Estimated cost of accident/incident (material and labor to repair/replace)

• Nomenclature of equipment and personnel involved in accident/incident

• Corrective actions (taken or proposed)

• Other pertinent information

If requested by the designated CO, the Contractor shall immediately secure the mishap sce-ne/damaged property and impound pertinent maintenance and training records, until released by the Procuring Safety Office. Contractors will not dispose of contract data related to a mishap until notified to do so by the CO.

Clearance Requirements:

The National Industrial Security Program Operating Manual (NISPOM), February 2006 ap-plies. Contractor must obtain SECRET safeguarding capability prior to being provided SE- CRET information. Contractor will require access to intelligence information and must com-ply with AFI 14-303/AFMC Supplement 1. The Program Manager has determined that dis-closure does not create an unfair competitive advantage for the contractor or a conflict of in-terest with the contractor's obligation to protect the information and will submit the AFMC Form 210 to the AETC SIO (OSS/USM) for approval prior to granting access. For Official Use Only (FOUO) applies. Any classified information generated in the performance of this contract shall require the contractor to apply derivative classification and markings consistent with the source material. This contractor is required to provide adequate and approved stor-age for classified hardware or material to the level of SECRET which because of size or quantity cannot be safeguarded in an approved storage container. The Notification of Gov-ernment Security and Visitor Group Security Agreement Clause applies. OPSEC require-ments apply.

Personnel Security

The contractor shall ensure the requirements for granting access to classified information, as defined in the NISPOM, DoD 5220.22-M, DoD 5200.1-R, DoD 5200.2-R, AFI 31-401 and AFI 31-501, are met. The contractor shall maintain proper security clearances for its person-nel. The level of security clearance for the unique workloads and facility will be addressed within each task order.

Operational Security (OPSEC)

OPSEC requirements are required in an effort to reduce program vulnerability from success-ful adversary collection and exploitation of critical information. OPSEC will be applied throughout the lifecycle of the contract. Critical Information list will be provided by the Government. OPSEC surveys to measure the effectiveness of the OPSEC program will be conducted by the Government.

Physical Security The contractor shall be responsible for ensuring that all mandated physical security require-ments are met. The contractor shall enforce local, AF, and DoD instructions on controlled and prohibited items inside the secure area. The contractor shall perform visitor control us-ing Joint Personnel Adjudication System (JPAS).

At the end of each workday, the contractor shall secure all assigned Government facilities, equipment, and materials. The contractor shall safeguard all Government property provided for contractor use. The contractor shall establish and implement procedures to ensure that keys and cards issued to the contractor by the Government are not lost, misplaced, used by unauthorized persons or duplicated.

Industrial Security

The contractor shall enter into a Visitor Group Security Agreement (VGSA) for service per-formed on a military installation. The contractor shall comply with the requirements of the National Industrial Security Program Operating Manual (NISPOM), DoD 5200.22-M and AFI 31-601 in management of the contract. The contractor shall appoint an Industrial Secu-rity Manager/Specialist who shall oversee security operations IAW applicable DoD and AF instructions listed above.

Access to Facilities and Property

Access to Government facilities is limited. Therefore, the Contractor shall coordinate re-quired access/usage times and dates through Government Technical Program Manager (TPM) or designated facility, at least 15 calendar days prior to the need date per task order.

Control of the facilities shall remain with the Government.