Att 01 - PWS - F-15 TDAS.pdf

FA8621-12-R-6259

Attachment 1

1 March 2012

PERFORMANCE WORK STATEMENT

For

F-15 Training Device Acquisition and Support

Prepared by:

Department of the Air Force

ASC/WNSK

Aeronautical Systems Center (AFMC)

Wright-Patterson Air Force Base, Ohio

Table of Contents

1.0 SCOPE

1.1. F-15 ATD Description

1.1.1. F-15E IAT:

1.2. F-15 MTD Description

1.2.1. F-15C Automatic Flight Control System Trainer (TFE-2):

1.2.2. F-15C Main Landing Gear and Arresting Gear Trainer (TFE-6):

1.2.3. F-15C Seat and Canopy System Trainer (TFE-7):

1.2.4. F-15C Armament System Trainer (AST) (TFE-20):

1.2.5. F-15E Aircraft Maintenance Trainer (AMT) (TFE-21):

1.2.6. F-15E Armament Load Trainer (ALT) (TFE-24):

1.2.7. F-15E Seat and Canopy Trainer (TFE-25):

2.0 APPLICABLE DOCUMENTS

2.1. Department of Defense Standards

2.2. Other Documents

3.0 TSSC OPERATIONS

3.1. Program Management

3.1.1. Program Meetings

3.1.2. Schedule Management

3.1.3. Risk Management

3.1.4. Data Management

3.1.5. Quality Assurance

3.1.6. Problem Reporting System

3.1.7. Safety

3.1.8. Small Business Utilization

3.1.9. Associate Contractor Agreement (ACA)

3.1.10. Import/Export Licenses and Agreements

3.2. Systems Engineering

3.2.1. Technical Reviews and Meetings

3.2.2. Requirements Traceability Matrix

3.2.3. Software Engineering

3.3. Program Security

3.3.1. Industrial Security

3.3.2. Physical Security

3.3.3. Personnel Security

3.4. Identification

3.5. Voluntary Protection Program

3.6. Logistics Data Library (LDL)

3.6.1. LDL Contents Databases

3.6.2. Technical Data Format

3.6.3. Visual, Sensor and Mission Databases

3.6.4. Software Baselines

3.6.5. Data Gathering and Verification

3.6.6. Commercial Software Maintenance

3.6.7. Coding and Documentation Standards

3.6.8. Status Accounting Database

3.7. Recompetition Support Package (RSP)

3.7.1. RSP Status Report

3.7.2. Audits

3.7.3. RSP Adjustments

4.0 TSSC ENGINEERING

4.1. Workload Management

4.2. Engineering Services Tasking Response

4.2.1. Engineering Capability

4.2.2. Major Development Tasking

4.3. Concurrency

4.4. Engineering Studies and Analyses

4.5. Configuration Management

4.5.1. Configuration Management Systems

4.5.2. Data Rights

4.5.3. Baseline Management

4.5.4. System Verification Review (SVR)/Physical Configuration Audit (PCA)

5.0 MAINTENANCE

5.1. Contractor Logistics Support (CLS) General

5.1.1. Compliance with Technical Data

5.1.2. Depot Repair Capability

5.1.3. Maintenance Concepts

5.1.4. Maintenance Actions

5.1.5. Hazardous Material Disposal

5.2. ATD Maintenance and CLS

5.2.1. On-Site Support

5.2.2. Payment Reduction

5.2.3. Technician Assistance

5.2.4. Support of Additional Activities

5.3. MTD Maintenance and CLS

5.3.1. On-Call Support

5.3.2. Notification

5.3.3. Response Times and Levels

5.3.4. Maintenance Response Actions

5.3.5. Customer Forms

5.3.6. Impacts to Repair Time

5.3.7. Payment Reduction

5.3.8. Major Mishap

6.0 CONCURRENCY UPGRADES, MODIFICATIONS AND CONVERSIONS

6.1. Training System Change Request

6.2. Initial Major Modifications

6.2.1. Trainer Field Equipment Functional Check

6.2.2. Trainer Field Equipment Conversions

6.2.3. Trainer Field Equipment Test Sets

6.2.4. APG-82 Malfunctions

6.2.5. Advanced Display Core Processor (ADCP) II

6.2.6. Suite 8 Operational Flight Program

6.3. Other Major Modifications/Engineering Change Proposals

6.4. Trainer Modification Installation

6.4.1. Documentation Updates

6.4.2. Data Required to Accomplish Modifications

6.4.3. Performance Specifications and Drawings

6.4.4. Hardware Prototyping, Kits, and Installation

6.4.5. Software Installation

6.4.6. Version Description Document

6.4.7. Time Compliance Technical Manual

6.4.8. Site Training

6.4.9. Government-Furnished Equipment (GFE)

6.4.10. Testing

6.4.11. Visual/Sensor Databases/Mission Data

7.0 ADDITIONAL TRAINER PROCUREMENT

8.0 TRAVEL

9.0 SPARES

9.1. Spares Purchases

9.1.1. Provisional Items and Spares

10.0 TRANSITION

10.1. Transition at Beginning of Contract

10.1.1. Facility and Material Transition

10.2. Transition at End of Contract

10.2.1. Facility and Material Transition

10.2.2. Inventories and Audits

10.2.3. Transition Plan

10.2.4. Transition Team

10.2.5. Repair Cycle Items

10.2.6. Transition Support Proposal

10.3. Continuation of Essential Services During Crises

11.0 MISCELLANEOUS

11.1. Personnel Assignments

11.1.1. Pass and Identification

11.1.2. Personnel Travel and Relocation Requirements

11.2. Government Facilities and Equipment

11.2.1. Provided Government Facility Equipment, Utilities and Repair

11.2.2. Non-Provided Government Facility Equipment, Utilities and Repair

11.2.3. Provided Equipment and Services

11.3. Device Relocations

11.4. Disposal and Disposition

11.5. Trainer Storage

11.6. Accident/Incident Reporting & Investigation

11.7. Contractor Identification of Company Association

12.0 DISPUTES

13.0 SERVICE SUMMARY

14.0 ACRONYMS

1.0 SCOPE

This Performance Work Statement (PWS) defines the tasks associated with Contractor

Logistics Support (CLS), change management, training system conversion, production of new training devices and contract transition for the F-15 Training Device Acquisition and

Support (TDAS) program. Supportive efforts include possible relocation of any training device and operations of a Training System Support Center (TSSC). The F-15 TDAS program includes F-15E Aircrew Training Devices (ATD) and F-15C and E Maintenance

Training Devices (MTDs).

1.1. F-15 ATD Description

The F-15E ATDs provide the capability for development of proper aircrew coordination in comprehensive flight, mission, and tactics environments. The ATDs provided under this contract are the F-15E Integrated Aircrew Trainers (IATs) as described below.

1.1.1. F-15E IAT:

The F-15E IAT is a PC-Based, Hands On Throttle And Stick (HOTAS)

ATD. The device consists of a Pilot Station, Weapons Officer Station, an

Instructor Operator System (IOS) and a Mission Support Computer.

Initial HOTAS schoolhouse training provides aircrews with the knowledge and skills required for warfare tasks. Instructor led familiarization training is used to teach basic cockpit procedures, as well as training in navigation, targeting, weapons delivery tactics, instrument, and data interpretation, radar and electronic warfare operation.

Formal Training Unit (FTU) courses that utilize the IAT include Initial

Qualification Training, Continuation Training, Transition/Requalification

Training and the Senior Officer Course. The IATs are currently at a Suite

7E capability level with Suite 8 to be tentatively scheduled to be delivered in 2015. Six IATs are currently in use at 4TS, Seymour Johnson AFB, NC. The IATs can also be used independently by students after training hours.

1.2. F-15 MTD Description

The F-15 MTDs are used to support familiarization training, procedural training, troubleshooting/fault isolation, component R&R/rigging/operational checks, and engine run training. The MTDs also support classroom training for checkout of the F-15C/E training system using flight line support equipment. All training on the MTD devices are derived from the platform technical orders (TOs). Descriptions of these devices are below.

1.2.1. F-15C Automatic Flight Control System Trainer (TFE-2):

This trainer is configured with three separate panels representative of comparative aircraft sections. The TFE-2 facilitates instruction in location and identification of integrated avionics, hydraulics and electrical systems components and their operational checkout, fault isolation, and repair.

1.2.2. F-15C Main Landing Gear and Arresting Gear Trainer (TFE-6):

The TFE-6 is used for operation and identification of component inspections, alignment, and operational checkout. Troubleshooting procedures for hydraulics, electrical, and mechanical portions of the landing gear system are also taught.

1.2.3. F-15C Seat and Canopy System Trainer (TFE-7):

The device is used to train ejection seat and canopy system operation, component identification and location training as well as operational checkout procedures, inspection, alignment, troubleshooting, and repair of the system. The trainer contains inert ejection system components along with related subsystems, trainer-peculiar components, and electrical wiring necessary for an operational trainer system.

1.2.4. F-15C Armament System Trainer (AST) (TFE-20):

The TFE-20 supports classroom training for checkout of the F-15C

Armament system. The device includes a panel containing aircraft components and control console housing aircraft cockpit controls/indicators and instructor controls, malfunction switches and loading/display panel to simulate weapons loading/firing sequences. The

TFE-20 is used to train armament technicians in operational checkout procedures, inspections, alignment, troubleshooting, and repair of the armament system.

1.2.5. F-15E Aircraft Maintenance Trainer (AMT) (TFE-21):

The TFE-21 consists of high fidelity cockpits connected to a computational system that provides a high fidelity aircraft component operational simulation supporting normal operation as well as malfunction simulations. Instructors can train students in Avionics Systems, Electrical

Power/Lighting System, Power Plant Systems, and Engine Run Training requirements with simulated performance both with and without F-15E system malfunctions. This enables student training in all aspects of equipment maintenance, operational checkout, alignment, and troubleshooting procedures, and repairs. The trainer implements job guides and its Cathode Ray Tube (CRT) display provides training feedback and reinforcement.

1.2.6. F-15E Armament Load Trainer (ALT) (TFE-24):

The TFE-24 consists of a simulated, full size, highly realistic F-15E aircraft built from salvaged parts. The trainer has a forward cockpit attached to a computational system that provides high fidelity aircraft component simulations. The trainer supports armament technician training.

1.2.7. F-15E Seat and Canopy Trainer (TFE-25):

The TFE-25 consists of an actual F-15B forward fuselage that provides egress training, maintenance inspection, seat and canopy removal and installation and cockpit familiarization. The trainer contains inert ejection system components along with related subsystems, trainer-peculiar components, and electrical wiring necessary for an operational trainer system.

2.0 APPLICABLE DOCUMENTS

The following documents are applicable to this PWS to the extent specified herein.

2.1. Department of Defense Standards

AFI 31-401, Information Security Program Management, 1Nov05 (Change 1, 19Aug09)

AFI 31-501, Personnel Security Program Management, 27Jan05 (Change 1, 10Jan12)

AFI 31-601, Industrial Security Program Management, 29Jun05 (Change 1, 31Mar10)

AFI 32-7042, Solid and Hazardous Waste Compliance, 15Apr09 (Change 1, 20Jun07)

AFI 33-200, Information Assurance (IA) Management, 23Dec08 (Change 2, 15Oct10)

AFI 33-201,Vol 1(FOUO) Communications Security (COMSEC), 1May03

(Change2,15Oct10)

AFI 33-201, Vol 2 Communications Security (Comsec) User Requirements, 26Apr05

(Change 1, 3Jun09)

AFI 33-210, Air Force Certification and Accreditation (C&A) Program (AFCAP), 23Dec08

DFARS Clause 252.211-7003, Item Identification and Valuation, Aug08

DFARS Clause 252.211-7007, Reporting of Government Furnished Equipment in the

Compartmented Information, 9Oct08 (Change 1, 13June11)

DoD 5200.1-R, Information Security Program, Jan 97

DoD 5200.2-R, Personnel Security Program, Jan 87

DoD 5220.22-M, National Industrial Security Program Operating Manual, 28Feb06

DoDI 8500.2, Information Assurance (IA) Implementation, 6Feb03

DoDI 8510.01, DoD Information Assurance Certification and Accreditation Process

(DIACAP), 28Nov07

MIL-STD-130N, DoD Standard Practice Identification Marking of U.S. Military

Property, 17Dec07

Technical Order 00-35D-54, USAF Deficiency Reporting, Investigation, and Resolution, 1Oct09

2.2. Other Documents

Occupational Safety Health Act (Public Law 91-596)

Training System Product Group (TSPG) Common Dataset Standard, Version 1.0, 01Dec06

3.0 TSSC OPERATIONS

The contractor shall provide integrated management of the F-15 TDAS operations to meet contract requirements. Operations include activities at each training site and the TSSC. The contractor shall establish, provide, and operate a facility for the government owned F-15

TSSC.

3.1. Program Management

The contractor shall develop a Management Plan that documents its program management process for the overall planning, programming, directing and controlling of the F-15 TDAS. The contractor shall manage the TDAS program in accordance with

(IAW) this plan. (A041)

3.1.1. Program Meetings

The contractor shall provide for and support Semi-Annual Program

Management Reviews (PMRs), semiannual Training Systems

Configuration Working Group (TSCWG) meetings, various Integrated

Product Team (IPT) meetings and other TSSC task reviews at the discretion of the government. Meetings shall be held at government facilities or hosted by the contractor at the government’s discretion. The contractor shall prepare the agenda and minutes for these meetings. (A001

A002)

3.1.2. Schedule Management

The contractor shall execute the program IAW the contract IMP. The contractor shall establish and maintain an Integrated Master Schedule

(IMS) that includes a detailed schedule for each device that is traceable to the IMP, to schedule the allocation of program resources and manpower to achieve program requirements. The IMS shall identify critical path relationships between activities to allow effective reallocation of resources

IAW DID-MGMT-81650 paragraph 2.4.1.15. The contractor shall update the IMS as program activities are accomplished and to adjust for resource fluctuations and materiel delivery changes. (A014)

3.1.3. Risk Management

The contractor shall implement a risk management program to identify, track, and assess cost, schedule and performance risks; implement necessary risk mitigation procedures and report on mitigation progress at the PMRs.

3.1.4. Data Management

The contractor shall generate and distribute contractual data IAW the

CDRLs. The contractor shall maintain the status of all data deliverables.

The contractor shall identify on the Data Accession List (DAL) all internal documents, computer programs, and data artifacts generated by the contractor or its subcontractors as a result of this contract. (A008)

3.1.4.1. Unclassified Website Access to Program Data

The contractor shall deliver CDRL items in electronic media format compatible with government systems. Note that electronic media format is NOT merely the digital imaging of paper documents unless the content of the source material is primarily image-based (i.e. alphanumeric-based documents should be accessible/searchable using a word-processor or spreadsheet application as appropriate). This delivery shall also include those non-deliverables identified on the DAL that are in electronic format. Those that are not in electronic format will be provided in the format in which they were created. The contractor shall establish a website for access to electronic program data. Government personnel will have read-only access. Access to the website shall be password controlled.

Notification of new postings to the website shall be provided by e-mail to Air Force Program Office designated government team members.

3.1.4.2. Monthly Activity Reports

The contractor shall submit monthly activity reports not later than (NLT) seven business days after the first of the month that shall address the following items.

3.1.4.2.1 A billing summary that includes a listing of the date, the contract and line item numbers, and amount of the invoices submitted for payment.

3.1.4.2.2 Engineering activity providing a summary of the project(s), accomplishments for the past month, upcoming tasks, and associated risks/issues.

3.1.4.2.3 Log of On-Call telephone assistance, including the date and time of call, customer name, telephone number, the contractor representative answering the call, device identification, problem description, and the resulting recommendations/actions.

3.1.4.2.4 Status of spares repaired or replaced during the month including the following:

3.1.4.2.5 Repairable: repair/condemnation data for each item, including site, trainer type or Trainer Flight Equipment (TFE) number, serial number, part number, noun, National Stock Number

(NSN) if applicable, quantity, condition status, source of supply, cage code, and lead time.

3.1.4.2.6 Recompetition Support Package (RSP) change

recommendations based on current spares consumption/status.

3.1.4.2.7 Summary of on-call MTD activities listing the site, device type or TFE number and serial number, hours spent, status on completion, description of the discrepancy, corrective action, and assets used, required Response and Fix Time (RAFT), the actual RAFT, and explanation of variance (over required), if any. The summary shall also include a cumulative performance rating defined as the percent of service calls completed within the required RAFT.

3.1.4.2.8 Summary of the Seymour Johnson on-site IAT support

activities, including device type or IAT serial number, a description of the discrepancy, a description of the corrective action, and IAT down time. Furthermore, the report shall include an activity summary for each IAT, including completed training hours, alternate training session hours, scheduled training hours, Nonchargeable hours, and IAT Availability

Rate (AR) as defined in Para 5.2.1.2. (A012 A013 A018)

3.1.4.3. IAT Field Service Report

The contractor shall prepare a monthly Field Service Report

(FSR). A copy of the current month’s FSRs shall be provided as part of the monthly activity reports. The contractor shall provide the program metrics listed below in the monthly FSR. These metrics shall also be reported at the PMRs. (A011)

3.1.4.3.1. IAT Field Service Report Content

The IAT FSR shall also include:

AFTO Form 781 series entries

IAT Availability Rates

IAT Monthly Utilization Rates

Device identification

Point of contact

Contract number

Notification date of failure

Completion date

Hours spent

Nonchargeable delays

Status on completion

Description of the discrepancy, corrective action, and assets used

Other maintenance activities performed

3.1.4.4. MTD Field Service Report

When MTD on-call support is accomplished, the contractor shall prepare a FSR. The current month’s FSRs shall be provided as part of the monthly activity reports. The contractor shall provide the program metrics listed below in the monthly FSR. These metrics shall also be reported at the PMRs. (A011)

3.1.4.4.1. MTD Field Service Report Content

Following completion of each MTD maintenance action the contractor shall complete and submit a FSR to the Project

Officer/Contracting Officer’s Representative (PO/COR) within five (5) business days. The FSR shall include:

Site where service was performed

Device identification

Government Site POC

Type of maintenance

Date work began

Description of discrepancy

Corrective action performed

Breakdown of daily labor hours

Parts added/removed

Training down time (hours)

3.1.4.5. Maintain Field Service Records

3.1.4.5.1. IAT Field Service Records

The contractor shall maintain field service records for each

IAT documenting serial number, scheduled hours, contracted hours, total utilized hours, availability, total lost hours, reason(s) for lost hours and spares consumption.

Each IAT FSR shall be certified by the contractor CLS lead and then provided to the PO/COR for validation and signature prior to sending through distribution. (A011)

3.1.4.5.2. MTD Field Service Records

The contractor shall maintain field service records documentation for each MTD. The contractor shall report the condition of each MTD in the FSR. (A011)

3.1.5. Quality Assurance

The contractor shall establish and maintain a quality control plan (QCP) to ensure the requirements of the contract are provided as specified. The

QCP is subject to non-acceptance by the Procuring Contracting Officer

(PCO) and revision required by the contractor at no additional cost to the government to ensure quality service. Contractor compliance with the

QCP will be monitored by the government. The QCP shall address (as a minimum), the following:

3.1.5.1. Inspection System

The QCP shall describe the contractor’s inspection system covering the services in this PWS. The plan must specify the areas to be inspected, how often inspections will be accomplished, and the titles of the individuals who will perform the inspections.

3.1.5.2. Discrepancy Prevention

The QCP must address the contractor’s method for identifying and preventing discrepancies and their causes in the quality of service performed before the level of performance becomes unacceptable.

3.1.5.3. Inspection Files

The QCP shall establish requirements for maintenance of on-site records of all inspections conducted by the contractor and the necessary corrective action(s) taken. This documentation shall be accessible by the government throughout the term of this contract. (A029)

3.1.6. Problem Reporting System

The contractor shall establish, execute, and maintain a computerized

Problem Reporting System to document and track problems from identification through implementation of the corrective action. A problem does not automatically indicate a contract non-compliance issue; it may also indicate an absent requirement. The Problem Reporting System shall include records documenting:

3.1.6.1 Discrepancies [e.g., Test Discrepancies (TD)] – contract non-compliance issues indicated by results of verification activities

(failed tests, inspections, analyses, or demonstrations), and latent defects discovered during system operation.

3.1.6.2 System performance needs or shortcomings identified by any government or contractor IPT member (i.e. Deficiencies).

3.1.6.3 The contractor’s Problem Reporting System database shall also contain the data and tracking information required for the Joint

Deficiency and Reporting System (JDRS), compliant with

Technical Order (TO) 00-35D-54 to include functioning as the

Originator, Originating Point, and Support Point as outlined in the referenced JDRS TO. The contractor shall enter all problems determined to be Deficiencies into the JDRS for the F-15 TDAS program during the Period of Performance of this contract.

3.1.6.4 The contractor shall provide the government with electronic access to the records maintained in the contractor’s Problem

Reporting System under provisions of the Data Accession List and Data Management requirements. All problem report records shall include (as a minimum): a report tracking number, date submitted, classification, a brief description, originator, status, priority, responsible person, corrective action, estimated date for correction, and overall summary. Problem reports may be initiated by the contractor, government personnel, or government-authorized contracted on-site staff as a result of test activities and any other observed system anomalies or inadequacies. (A007)

3.1.7. Safety

The contractor shall identify, analyze, report, and mitigate all safety hazards (environment, safety, and occupational health (ESOH) risks) to minimum (acceptable) levels IAW MIL-STD-882 criteria. This includes informing the PO/COR and PCO immediately upon any major accident/injury incident. The contractor shall also summarize all safety

(ESOH) risks assumed during test and operation, identify safety features of the system, and specify procedural controls specific to the devices. Any new designs or modifications will include the identification and mitigation of safety (ESOH) hazards IAW the guidelines (direction) of MIL-STD-

882. (A019)

3.1.7.1. Electrostatic Discharge (ESD) Control

The contractor shall implement and maintain a process to control

ESD IAW ANSI/ESD S20.20-2007.

3.1.8. Small Business Utilization

The offeror shall implement a contractual Small Business Subcontracting

Plan and Small Business Participation Plan and report actual achievement of meeting the requirements set forth in the plans and set forth in contract

Clause H109 within 30 days after completion of each calendar year. Note:

this Small Business Subcontract Report is different than the semi-annual eSRS reporting requirement. (A015)

3.1.9. Associate Contractor Agreement (ACA)

As necessary for specific tasks, the contractor shall enter into ACAs for exchanging data; accessing and using third party software and equipment;

receiving technical support; working interface issues; and/or agreeing on equipment use and time.

3.1.10. Import/Export Licenses and Agreements

The contractor shall obtain required import/export licenses and agreements as needed.

3.2. Systems Engineering

The contractor shall develop and maintain a requirements-driven, iterative-design systems engineering management process outlining the overall planning, programming, directing and controlling as applicable to the F-15 TS. The contractor shall document the systems engineering process in a System Engineering Management Plan (SEMP) as approved by the government. (A030)

3.2.1. Technical Reviews and Meetings

The contractor shall support technical reviews to provide status information on current projects. These may be held in conjunction with

PMRs or other IPT meetings. The type and number of formal reviews shall be documented in the tasking for each specific project.

The contractor shall attend any additional program reviews upon request of the Air Force Program Office.

3.2.2. Requirements Traceability Matrix

The contractor shall maintain an electronic Requirements Traceability

Matrix (RTM) that identifies all performance requirements (including modifications) and provides traceability to the implemented design and verification documentation (test procedures, audits, etc) that confirms the correct and complete implementation of each requirement. The contractor shall review and update the RTM upon any modification of the F-15

TDAS requirements. (A032)

3.2.3. Software Engineering

The contractor shall manage and resolve software defects and issues related to the training devices. The contractor shall maintain software media in an operable condition and in the current and government-approved baseline configuration. The contractor shall maintain a TS software support capability to design, validate and deliver training device software releases. (A038 A040)

3.2.3.1. Software Releases

The contractor shall manage and deliver software releases in order to maintain concurrency with the fielded aircraft configurations.

3.2.3.2. Software Documentation

When a Computer Software Configuration Item (CSCI) is modified to a new version, the contractor shall update all applicable software documentation not less than 10 working days prior to release of the new version unless otherwise authorized by the government.

3.3. Program Security

The contractor shall comply with the following security requirements, by January of

2015, as specified in Joint Air Force Army and Navy 6/0 – Special Access Program

Security Manual:

JAFAN 6/3, Protecting Special Access Program Information within Information

Systems

JAFAN 6/4, Special Access Program Tier Review Process

JAFAN 6/9, Physical Security Standards for Special Access Program Facilities

The contractor shall have a facility that is capable of meeting requirements and of attaining a higher classification for personnel by January 2015 at no capital investment cost to the government. The contractor shall not need to meet a Top Secret requirement.

The contractor shall comply with local base standards for safety and security and the contractor shall maintain security for all government facilities they occupy/manage IAW host base security requirements. The contractor shall be responsible for providing escorts for personnel requiring access to include but not limited to scheduled visitors, facility maintenance personnel and government personnel. The contractor shall maintain and manage all contractor owned facilities in a manner IAW industry standards and equivalent to base facilities. The contractor shall create and maintain operating procedures IAW the DoD and AF security disciplines listed below. The contractor shall protect For Official Use Only (FOUO) and classified material from unauthorized access.

The contractor shall report all security violations and/or anomalies to the government

PO/COR and Air Force Program Office no later than the morning of the next business day.

DODI 8510.01

DODI 8500.2

DOD 5200.1-R

DOD 5200.2-R

DoD 5220.22-M

AFI 31-401

AFI 31-501

AFI 31-601

AFI 33-200

AFI 33-201 Volume 1

AFI 33-203 Volume 1

AFI 33-203 Volume 3

AFI 33-210

Security activities shall include routine duties as prescribed by the System Security

Profile (SSP) which may include:

Audits of system/user activity

Items under security seal

System maintenance log

Personnel/user access maintenance

Antivirus updates

3.3.1. Industrial Security

The contractor shall enter into a Visitor Group Security Agreement

(VGSA) for services performed on-base. The contractor will need to coordinate with each base and abide by their policies and procedures.

The contractor shall comply with the requirements of DoD 5200.22-M and

AFI 31-601 in management of the contract.

The contractor shall be responsible for managing classified data IAW

Section J, Attachment 11, “DD Form 254 Contract Security

Specification”.

The contractor shall oversee system-wide industrial security operations

IAW applicable DoD and AF instructions listed in Para 3.3, Program

Security and this paragraph.

3.3.2. Physical Security

The contractor shall be responsible for ensuring that all mandated physical security requirements are met. The contractor shall enforce local, AF and

DoD instructions on controlled and prohibited items inside the secure area.

The contractor shall provide security in the event of a security system malfunction at a secure IAT training facility.

The contractor shall perform visitor control using Joint Personnel

Adjudication System (JPAS). The contractor shall have the capability for sending/receiving classified visit requests.

When required by real world Force Protection Condition (FPCON) levels, the contractor shall secure the IAT training facility IAW base directives and control entry into the facility IAW base plans unless relieved by US military personnel.

At the end of each workday, the contractor shall secure government IAT 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 issued to the contractor by the government are not lost, misplaced, used by unauthorized persons or duplicated.

3.3.3. Personnel Security

The contractor shall ensure the requirements for granting access to classified information, as defined in 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 personnel. For personnel that travel overseas, the contractor shall provide the passport number and visa with expiration date to the Air Force Program Office.

3.4. Identification

The contractor shall follow the applicable Item Unique Identification (IUID) requirements in Section I, Defense Federal Acquisition Regulation Supplements

(DFARS) Clauses 252.211-7003 and 252.211-7007 and MIL-STD-130N.

The contractor shall determine which Government Furnished Property (GFP) items fall under the requirements of DFARS Clause 252.211-7007. For items that require a virtual

Unique Item Identifier (UII), the contractor shall mark them with a UII. The contractor shall have until six months after receipt of order to comply with this requirement.

In the attachment specified in DFARS Clause 252.211-7003, paragraph (c)(1)(iii), the contractor shall list, for delivered items, only those embedded items that have a UII due to the item's delivered spare having a UII.

The contractor shall use Automated Identification Technology (AIT) for unique identification of items.

3.5. Voluntary Protection Program

The contractor shall establish a Safety and Health Plan and corresponding site safety checklist resulting in the prompt investigation, correction and tracking of safety and health violations and/or uncontrolled hazards in contractor work areas. Installation-specific references and policies may be included (or attached) to the plan.

The contractor shall comply with the specific health and safety requirements identified in this PWS, as well as the Occupational Safety Health Act (Public Law 91-596).

The contractor shall comply with the health and safety rules of the government installation that not directly addressed in this PWS.

The contractor shall take reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and government personnel performing or in any way coming in contact with the performance of this requirement.

The contractor shall take additional immediate precautions identified by the PO/COR for health and safety purposes.

3.6. Logistics Data Library (LDL)

The contractor shall establish and maintain a LDL at the TSSC containing all training device baseline technical data (operator and technical manuals, drawings, software manuals, acceptance test procedures, and Commercial Item manuals), engineering reference data, and source and object software with media. Copies of aircraft Technical

Orders (TOs), compatible with the most current trainer baseline, shall be provided, maintained, updated, and distributed to each site as applicable (typically for maintenance trainers).

3.6.1. LDL Contents Databases

The contractor shall provide and maintain a database to track the inventory of the LDL. The contractor shall ensure that the database identifies all applicable technical documentation and software for each trainer baseline.

The contractor shall also ensure that the database software is compatible with the most current government software. An electronic copy of the

LDL database files shall be made available to the Air Force Program

Office upon request.

3.6.2. Technical Data Format

The contractor shall maintain all technical data, drawings, and manuals in the same style and format as existing data and per the Technical Manual

CDRL Requirement. The contractor shall convert to electronic media when changes are made, unless directed otherwise by the Air Force

Program Office. (A022 A025)

3.6.3. Visual, Sensor and Mission Databases

The contractor shall maintain a library of visual, sensor and mission databases. The contractor shall copy and distribute this data as tasked by the Air Force Program Office. (A037)

3.6.4. Software Baselines

The contractor shall maintain a master and backup copy of all current baselines supported by the TSSC. The contractor shall archive at least one previous revisions of every baseline.

3.6.5. Data Gathering and Verification

At the beginning of the contract, the contractor shall collect, verify, and inventory data pertaining to the support of training devices covered in this contract and maintain it in the LDL.

3.6.6. Commercial Software Maintenance

The contractor shall track upgrades in commercial software used to support this contract and determine the need for updates or modifications.

The contractor shall forward recommendations to the Air Force Program

Office.

3.6.7. Coding and Documentation Standards

The contractor shall implement effective software coding and documentation standards using IEEE/EIA 12207 as a guide. New code generated under this effort shall conform to these standards. These standards shall meet or exceed those currently used with the trainer(s) software and documentation and shall be approved by the Air Force

Program Office at contract start.

3.6.8. Status Accounting Database

The contractor shall develop, update (on a monthly basis), and maintain a status accounting database. The status accounting database software shall be compatible with the most current government software requirements and shall include the following data:

Trainer inventory (type, serial number, location, status)

Discrepancy status

Proposed modifications and enhancements

3.7. Recompetition Support Package (RSP)

The RSP for use by the contractor in support of the F-15 TDAS requirements shall consist of government approved and owned reparable spares, support equipment and technical data (e.g. list of IATs and MTDs and locations, Government Furnished

Aircraft Equipment (GFAE) parts, IAT and MTD spares, TSSC software, support equipment, and F-15 trainer related technical publications). The RSP shall be maintained in serviceable condition and reflect the latest device configuration. At contract termination, the RSP shall be returned to the government in serviceable condition and in the latest configurations. The contractor shall provide an update to the

RSP semi-annually. This update shall include item cost, location, and quantities of reparable spares and support equipment. The contractor shall replenish spares taken from spares inventory to support the IAT availability requirement and MTD repair times. All recommendations and associated justifications concerning changes

(additions/deletions) to the RSP shall be submitted through the PCO for approval. The contractor shall identify to the government any items deemed excess to the program requirements and shall request disposition instructions within 30 days of the recognized excess. The contractor shall disposition excess equipment IAW FAR 45.5. The contractor shall be responsible for execution of the proper government turn in documents, providing a copy to the PO/COR. The PO/COR will be responsible for coordinating any required base support equipment or services.

3.7.1. RSP Status Report

The contractor shall prepare a semiannual report that includes the following:

Current baseline definitions for each trainer type, including: indentured drawing list and status, List Of Applicable Publications (LOAPS), List Of

Applicable Software (LOAS), system specifications, test procedures, and any other applicable documentation

3.7.1.1. Spares inventory and status

3.7.1.2. Consumption/usage and obsolete parts (and recommended replacements)

3.7.2. Audits

The contractor shall support annual RSP audits and System Verification

Review (SVR)/Physical Configuration Audit (PCA) of the product baselines as directed by the Air Force Program Office. The contractor shall correct any deficiencies discovered in such audits.

3.7.3. RSP Adjustments

The contractor shall recommend adjustments in the RSP to increase training device readiness or to reduce maintenance costs. The contractor shall only implement adjustments after receiving authorization from the

PCO.

4.0 TSSC ENGINEERING

4.1. Workload Management

The contractor shall staff the F-15 TDAS TSSC to provide engineering services supporting the training systems covered under this contract. These services include, but are not limited to, studies and analyses, design, development, modifications, Safety

Investigation Board (SIB), configuration control, resolving Diminishing Manufacturing

Sources (DMS) and obsolescence issues, and technical data management.

The contractor shall iteratively evaluate supportability, reliability, maintainability and parts obsolescence issues. The contractor shall provide engineering services as assigned via PCO tasking letters. The contractor shall provide logistics support, including maintenance actions, parts repair, maintenance and management of the RSP, training device/equipment relocation, and disposal/disposition of training devices. The contractor shall be responsible for effectively managing and executing the combined engineering and maintenance tasks, including risk management. The contractor shall follow standard design practices and update documentation per Configuration

Management, Para 4.5.

4.2. Engineering Services Tasking Response

When tasked to carry out an engineering project or provide a service under this contract, the contractor shall provide a written response that provides the information in the following subsections. Required response time shall be provided at time of tasking and

Air Force Program Office will review and approve tasking responses before work begins.

4.2.1. Engineering Capability

The contractor shall perform routine and/or urgent engineering service taskings on a firm-fixed price basis in monthly increments (up to one year on an individual CLIN). One month of engineering capability equates to 666.6 estimated engineering hours, or a total of 8,000 estimated engineering hours in a given year. Note this is not a FFP Level of Effort CLIN. As needed, the government will fund the applicable Engineering Materials CLIN (cost, no profit/fee).

4.2.1.1. Carry Over

The government anticipates ordering this capability in annual allotments but reserves the right to order in monthly increments. Should the government order less than a full year of capability, and later on, order additional capability on the same CLIN in consecutive months, that capability can be carried over/moved as necessary between months within the period of performance issued on that CLIN. If, later on, the government orders additional capability on the same CLIN but not in consecutive months, then the capability cannot be carried over to the new set of months.

4.2.1.2. Process for Assigning Service Taskings

The government will identify service taskings on a periodic basis and will request that the contractor propose a specific number of hours and materials (if applicable) required per task. Once the government approves the task the contractor will be authorized to begin performance of that task. When directed by Air Force Program Office to perform routine and urgent engineering taskings, the contractor shall respond providing the following:

Technical approach description

Test/verification approach description

Start and completion date

Proposed estimated number of engineering hours

Estimate of material, if required

4.2.1.3. Engineering Hours

The total “estimated” engineering hours proposed and approved per task will be used in determining how much of the total capability has been used. Should a task take more time to actually complete than was originally proposed, the government will not be penalized by the expending of additional hours than were originally proposed and approved for that task. Likewise, should a task take less time to actually complete than was originally proposed, the contractor will not be penalized by levying additional tasks.

4.2.1.4. Carry Over Example

In December 2014 the government only has funding for 6 months of capability and issues a task order incorporating/funding CLIN 3002AA from 1 January to 30

June 2015. During the 6 months the government only provides the contractor with 3,500 estimated hours worth of taskings. In June 2015 the government obtains additional funding and issues a new task order incorporating/funding

CLIN 3002AA from 1 July to 31 December 2015. The government can provide the contractor with an additional

4,500 estimated hours worth of taskings to be performed, for a total of 8,000 estimated engineering hours worth of taskings to be performed anytime between 1 January 2015 and 31 December 2015. In that same example, if the government had not issued the new task order in June 2015 prior to the end of June 2015, but issues a new task order in

July 2015 for 5 months worth of capability from August to

December 2015, then the government could not carry over the “left-over” 500 hours from the first 6 months to the last

5 months. The contractor would still be authorized to invoice for all 6 months of capability on the first task order because of the firm-fixed price nature of the CLIN.

If an urgent need arises, routine engineering taskings may be reprioritized to include the urgent need as directed by the

PCO.

4.2.2. Major Development Tasking

The contractor shall perform major development taskings in addition to the engineering capability requirements in paragraph 4.2.1 and the initial major modifications in paragraph 6.2. The contractor shall provide the response in the form of an Engineering Change Proposal (ECP).

4.3. Concurrency

The contractor shall maintain device equipment, databases, and environments used to provide training concurrent with the changing configuration of the fielded F-

15C/E aircraft. The contractor shall maintain concurrency with aircraft modifications at individual IAT/MTD sites as directed by the Air Force Program

Office. These will be considered as separately priced changes. Concurrency of the

IAT, TFE-21 and TFE-24 shall be accomplished by using the F-15E OFP source code. The contractor shall be provided access to OFP flight software and RPS software and shall develop each concurrency update from the F-15E RPS software and hardware version corresponding to the concurrency update. Concurrency updates shall be made available at all sites no later than 30 days prior to implementation on the first aircraft.

4.4. Engineering Studies and Analyses

The contractor shall perform engineering studies on deficiencies, enhancements, and modernization to the training systems as tasked by the Air Force Program

Office. The contractor shall develop cost and schedule estimates. Studies may include investigation of new technologies and an evaluation of the benefits of their insertion to improve capabilities and services. The contractor shall be solely responsible for acquisition of all source design criteria and data necessary to accomplish such tasks. Results of studies and analysis shall be documented in a report submitted to the PCO. All data and analysis generated under these taskings shall become government property. (A024)

4.5. Configuration Management

The contractor shall define, implement and maintain a configuration management process as documented in a Configuration Management Plan (CMP). The contractor shall establish and maintain a current and traceable TS hardware and software baseline configuration IAW the contractor's configuration management process. The contractor shall manage the configuration of the training device software, firmware, hardware, and the Technical Data Package (TDP), hereafter referred to as the Product Baseline, as tasked by the Air Force Program Office. The contractor shall with their configuration management system manage, track and control TS change activities, release formal baseline changes, provide traceability to training and design requirements, track configuration of all fielded assets and produce status accounting reports. The contractor shall update and maintain applicable program specifications, through the use of Engineering/Contract Change

Proposal (ECP/CCP), Training System Change Requests (TSCRs) and Notice of

Revision (NOR).(A003 A004 A005 A006 A009 A010)

4.5.1. Configuration Management Systems

The contractor shall use the current computer-based configuration management systems unless the contractor justifies and the government approves a different system. The contractor shall ensure these systems and data are transferable to other contractors; therefore, any new configuration management systems shall not contain proprietary or non-commercially available components. The system shall be used to manage the software documentation, hardware specifications, technical publications, test procedures, engineering drawings and all other documentation

4.5.2. Data Rights

The contractor shall ensure these processes and data are transferable to other contractors; therefore, any new configuration management systems shall not contain proprietary or non-commercially available components.

4.5.3. Baseline Management

The contractor shall establish and maintain a hardware and software functional and physical configuration baseline for the IATs and MTDs. The contractor shall identify any deviations from the approved configuration baseline.

4.5.4. System Verification Review (SVR)/Physical Configuration Audit (PCA)

The contractor shall host and support government auditors during government/contractor SVR/PCA of hardware and software. SVR shall take place prior to PCA.

5.0 MAINTENANCE

5.1. Contractor Logistics Support (CLS) General

The contractor shall provide logistics support to manage, maintain and support the

F-15 Training System. The support shall be provided with either on-call maintenance or on-site technician support as designated by site. CLS on-site activities shall center on ATDs. CLS On-call activities shall center on the MTDs.

CLS activities shall include but not be limited to the following: site inventory management; inventory storage and control; distribution and management of supportability assets; logistics analysis and supportability assessment updates;

identification and management of supportability issues; acquisition of all replenishment or replacement assets and asset repairs; disposition and disposal of obsolete and condemned support assets; execution of supportability quality audits;

development and management of logistics data as a result of engineering sustainment or part obsolescence replacement; acquisition, validation and management of technical publications; management of TS libraries; and management, maintenance and testing of IATs and MTDs. The contractor shall coordinate all issues that may arise or require coordination with the PO/COR.

5.1.1. Compliance with Technical Data

The contractor shall establish a TODO account. All maintenance performed by the contractor shall be accomplished IAW applicable technical orders and technical manuals, commercial manuals, and engineering drawings. The contractor shall schedule and perform both scheduled and unscheduled maintenance actions in such a manner as to minimize impact on unit scheduled utilization of devices.

5.1.2. Depot Repair Capability

The contractor shall establish a depot repair capability in support of all training devices. All failed repairable assets returned from field sites shall be repaired or refurbished and returned to the RSP or customer, as applicable.

The contractor shall be responsible for any costs incurred by the government to bring the spares, support equipment, and the TDP to a serviceable condition due to non-performance or negligence of the contractor. The contractor shall make recommendations for condemnation of unserviceable or obsolete items and, if approved by the Air Force Program Office, dispose of them IAW Disposal and Disposition, Para 11.4.

5.1.3. Maintenance Concepts

The users and the types of…