F-15 TDAS PWS_DRAFT

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

XX December 2011

Table of Contents

1.0 SCOPE

1.1. F-15 Aircrew Training Devices (ATDs)

1.1.1. F-15E Integrated Avionics Trainer (IAT)

1.2. F-15 Maintenance Training Devices (MTDs)

1.2.1. TFE-2, F-15C Automatic Flight Control System Trainer

1.2.2. TFE-6, F-15C Main Landing Gear and Arresting Gear Trainer

1.2.3. TFE-7, F-15C Seat and Canopy System Trainer

1.2.4. TFE-20, F-15C Armament System Trainers (AST)

1.2.5. TFE-21, F-15E Aircraft Maintenance Trainers (AMT)

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

1.2.7. TFE-25, F-15E Seat and Canopy Trainers

2.0 APPLICABLE DOCUMENTS

2.1. Department of Defense Standards

2.2. Other Documents

2.3. Order of Precedence

2.4. Acronyms List

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.4.1. Data Rights

3.1.4.2. Website Access to Program Data

3.1.4.3. Monthly Activity Report (MAR)

3.1.4.4. Field Service Report (FSR)

3.1.4.4.1. Field Service Report - IAT

3.1.4.4.2. Field Service Report - MTD

3.1.5. Quality Assurance

3.1.6. Deficiency Reporting

3.1.7. Safety

3.1.7.1. Electrostatic Discharge (ESD) Control

3.1.8. Small Business

3.1.9. Associate Contractor Agreement (ACA)

3.1.10. Import/Export Licenses and Agreements

3.1.11. Key Personnel

3.2. Systems Engineering

3.2.1. Technical Reviews and Meetings

3.2.2. Requirements Traceability Matrix

3.2.3. Software Engineering

3.2.3.1. Software Releases

3.2.3.2. Software Documentation

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. 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. Recompetition Support Package (RSP) Status Report

3.7.2. Audits

3.7.3. RSP Adjustments

4.0 TRAINING SYSTEM SUPPORT CENTER (TSSC) ENGINEERING

4.1. Workload Management

4.2. Engineering Services Tasking Response

4.2.1. Routine Tasking

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.4.1. – 4.1.4.6

5.1.5. Hazardous Material Disposal

5.2. ATD MAINTENANCE AND CLS

5.2.1. On-Site Support

5.2.1.1. Availability Rate

5.2.1.2. Aircrew Training Device Schedules

5.2.1.3. Contractor-Provided Tools/Support Equipment and Consumables

5.2.1.4. Customer Forms

5.2.2. Technical Assistance

5.2.2.1. Set-Up

5.2.2.2. Operations

5.2.2.3. Mission Generation

5.2.3. Support of Additional Activities

5.2.4. Surge Operation

5.3. MTD MAINTENANCE AND CLS

5.3.1. On-Call Support

5.3.2. Response Times and Levels

5.3.3. Maintenance Response Actions

5.3.4. Customer Forms

5.3.5. Impacts to Repair Time

5.4. Major Mishap

6.0 CONCURRENCY UPGRADES, MODIFICATIONS AND CONVERSIONS

6.1. Training System Change Request

6.2. TFE Conversion

6.3. Trainer Modification Installation

6.3.1. Documentation Updates

6.3.2. Data Required to Accomplish Modifications

6.3.3. Major Modifications

6.3.4. Hardware Prototyping, Kits, and Installation

6.3.5. Software Installation

6.3.6. Version Description Document

6.3.7. Time Compliance Technical Manual

6.3.8. Site Training

6.3.9. Government-Furnished Equipment (GFE)

6.3.10. Testing

6.3.11. Sensor Databases/Mission Data

7.0 TRAINING SYSTEM DEVICE PROCUREMENT

8.0 TRAVEL

9.0 SPARES

9.1. Spares Purchases

9.1.1 Provisional Items and Spares

10.0 TRANSITION

10.1. Initial Transition

10.2. Facility and Material Transition

10.3. Follow-on Transition

10.3.1. Facility and Material Transition

10.3.2. Inventories and Audits

10.3.3. Transition Plan

10.3.4. Transition Plan IPT

10.3.5. Repair Cycle Times

10.3.6. Transition Support Proposal

10.4. 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. Facilities and Equipment

11.2.1. Provided Facility Equipment, Utilities and Repair

11.2.2. Maintenance of Government-Provided Facilities

11.2.3. Government-Provided Equipment and Services

11.3. Trainer 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 thru E Maintenance

Training Devices (MTD).

1.1 F-15 ATD Description

The F-15 ATDs provide initial aircrew training and development of proper aircrew coordination in comprehensive flight, mission, and tactics environments. Description of this device is below.

1.1.1 F-15E IAT:

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

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.

The IATs can be used independently by students after training hours. All Formal

Training Unit (FTU) courses include Initial Qualification Training, Transition/Requalification Training and the Senior Officer Course. These devices are currently at a Suite 7E capability level with Suite 8 to be tentatively scheduled to be delivered in 2015. Six devices are currently in use at 4TS, Seymour Johnson

AFB, NC.

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. Descriptions of these devices are below.

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

Consists of three separate panels representative of comparative aircraft sections.

Facilities 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):

Used for operation and identification of components inspections, alignment, and operational checkout. Troubleshooting procedures for hydraulics, electrical, and mechanical portions of the landing gear system are taught.

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

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 are taught. 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):

Supports classroom training for checkout of the F-15C Armament system using

Flight Line Support Equipment. 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. Used to teach armament technicians in the operational checkout procedures, inspections, alignment, troubleshooting, and repair of the armament system.

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

Consists of high fidelity cockpits connected to a computational system that provides high fidelity aircraft component operational simulations that support normal operation as well as malfunction simulations. Instructors can train students in

Avionics Systems, Electrical Power/Lighting System and Power Plant Systems with simulated performance both with and without malfunctions of F-15E systems. This enables student training in all aspects of equipment maintenance, operational checkout, alignment, and troubleshooting procedures, and repairs. Trainer implements job guides and CRT display provides training feedback and reinforcement.

1.2.6 F-15E Armament Load Trainer (ALT) (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):

Consists of actual F-15B forward fuselages that provide 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

AFI 31-601, Industrial Security Program Management, 29Jun05

AFI 32-7042, Civil Engineering Waste Management, 15Apr09 (Change 1, 31Mar10)

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-202, Network and Computer Security, 18May07

AFI 33-203, Emission Security Vol 1, 31Oct05, Supplement 1, 7Feb06

AFI 33-203, Emission Security Vol 3, 2Nov05

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

AFI 36-2248, Operation and Management of Aircrew Training Devices, 1May98

AFI 36-2251, Management of Air Force Training Systems (for information only), 5Jun09

AFI 63-101, Acquisition and Sustainment Life Cycle Management, 3Aug11

AFI 63-124, Performance-Based Services Acquisition (PBSA), 1Aug05

AFI 63-1201, Life Cycles Systems Engineering, 23Jul07

AFI 91-301, Air Force Occupational and Environmental Safety, Fire Protection, and

Health (AFOSH) Program, 1Jun96

AFPD 33-2, Information Protection, 19Apr07

AFSOCI 33-201, Controlled Access Area, 8Oct08

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

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

DoD Item-Unique Identification (IUID) Registry, Nov08

DoDD 5000.01, The Defense Acquisition System, 20Nov07

DoDD 5200.01, DoD Information Security Program and Protection of Sensitive

Compartmented Information, 9Oct08

DoDD 5230.24, Distribution Statements on Technical Documents, 18Mar87

DoDD 5230.25, Withholding of Unclassified Technical Data from Public Disclosure, 18Aug95

DoDD 8500.01E, Information Assurance, 23Apr07

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

DoD Instruction (DoDI) 2040.02, International Transfer of Technology, Articles, and

Services, 10Jul08

DoDI 3020.37, Continuation of Essential DoD Contractor Services During Crises, 6Nov90 (Change 1, 26Jan96)

DoDI 5000.02, Operation of the Defense Acquisition System, 8Dec08

DoDI 5200.39, Critical Program Information (CPI) Protection within the DoD, 16Jul08

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

DoDI 8510.01, DoD Information Assurance Certification and Accreditation Process

(DIACAP), 28Nov07

DoD Manual 5200.1, The Acquisition Systems Protection Program, 16Mar94

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

Property, 17Dec07

MIL-STD-882D, DoD Standard Practice for System Safety, 10Feb02

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

2.2 Other Documents

ANSI/ESD S20.20-2007 Protection of Electrical and Electronic Parts, Assemblies and

Equipment (Excluding Electrically Initiated Explosive Devices)

IEEE/EIA 12207.0, Standard for Information Technology – Software Life Cycle

Processes, May98

Occupational Safety Health Act (Public Law 91-596)

USAF TSPG Common Dataset Standard, 1Dec06

2.3 Order of Precedence

In the case of a conflict between the cited references, the contents herein and the PWS, the order of precedence is the PWS, the contents herein, then the cited references.

3.0 TSSC OPERATIONS

The contractor shall provide integrated management of the F-15 TDAS operations which meets the contract requirements. Operations include activities at each training site and the

TSSC. The contractor shall establish, and operate a government owned F-15 TSSC.

3.1 Program Management

The contractor shall develop a program management process outlining the overall planning, programming, directing and controlling of the F-15 TDAS. The contractor shall document the program management process in a Management Plan (MP). The contractor shall manage the TDAS program in accordance with the Government approved contractor's MP. The contractor’s proposed MP shall be incorporated into the contract as an attachment to the PWS.

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), various Integrated Product Team (IPT) meetings and other TSSC task reviews at the discretion of the government. The contractor shall prepare the agenda and minutes for these meetings.

Deliverable(s): CDRL(AXXX)

3.1.2 Schedule Management

The contractor shall execute the program IAW the contract Integrated Master Plan

(IMP). Consistent with contract delivery requirements, the contractor shall establish and maintain an Integrated Master Schedule (IMS) that is consistent with 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 when appropriate. The

Contractor shall update the IMS, IAW the CDRL as program activities are accomplished, and to adjust for resource fluctuations and materiel delivery changes.

3.1.3 Risk Management

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

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 all internal documents and computer programs generated as a result of this contract on the Data Accession List (DAL).

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 program office designated Government team members.

3.1.4.2 Monthly Activity Report (MAR)

The contractor shall submit a monthly activity report NLT seven business days after the first of the month, that shall address the following items.

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

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

Log of telephone assistance calls, 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.

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

o 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 o Consumable: consumption data for each item, including site, trainer type or TFE number, part number, noun, NSN if applicable, and quantity o Recompete Support Package (RSP) change recommendations based on current spares consumption/status.

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.

Summary of the on-site ATD support activities, including site, device type or TFE number, 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 device, including completed training hours, alternate mission hours, scheduled training hours, exception hours, and device Availability Rate (AR) as defined in

Para 5.2.1.1.

3.1.4.3 ATD Field Service Reports (FSR)

When ATD on-site is accomplished, the contractor shall prepare a FSR. A copy of the current month’s FSRs shall be provided as part of the MAR.

The contractor shall provide the following program metrics and those listed below in the monthly FSR: (1) ATD availability rates and (2) MTD on-call statistics. These metrics should also be reported at the PMRs.

3.1.4.3.1 Field Service Report - ATD

The IAT FSR shall also include:

Site where service was performed

Device identification

Point of contact

Contract number

Notification date

Completion date

Hours spent

Nonchargeable delays

Status on completion

Description of the discrepancy, corrective action, and assets used

Explanation of any response time that exceeds the required time

Other maintenance activities performed

3.1.4.4 MTD Field Service Reports (FSR)

When MTD on-call support is accomplished, the contractor shall prepare a

FSR. A copy of the current month’s FSRs shall be provided as part of the

MAR. The contractor shall provide the following program metrics and those listed below in the monthly FSR: (1) ATD availability rates and (2)

MTD on-call statistics. These metrics should also be reported at the PMRs.

3.1.4.4.1 Field Service Report – MTD

Following any maintenance action on each MTD, contractor shall complete FSR within five (5) business days of completed action. The

FSR shall include:

a) Site where service was performed

b) Device identification

c) Site POC

d) Type of maintenance

e) Date work began

f) Description of discrepancy

g) Corrective action performed

h) Breakdown of daily labor hours

i) Parts added/removed

j) Training Hours Lost

3.1.5 Quality Assurance

The contractor shall develop and maintain an ISO 9001:2008 or equivalent compliant quality management process outlining the overall planning, programming, directing and controlling quality of the F-15 TDAS. The contractor shall establish and maintain a Quality Control Plan (QCP) to ensure the requirements of the contract are provided as specified. The contractor shall develop and implement procedures to identify, prevent, and ensure non-performance or continual repeat of defective service does not occur. Contractor compliance with the QCP will be monitored by the Government. The contractor shall incorporate the QCP in the MP.

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:

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

b) System performance needs or shortcomings identified by any Government or

Contractor IPT member (i.e. Deficiencies).

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

Technical Order. 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. The Government shall be provided 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.

3.1.7 Safety

The Contractor shall have the responsibility of identifying, analyzing, reporting, and mitigating all safety hazards (environment, safety, and occupational health (ESOH) risks) to minimum (acceptable) levels in accordance with MIL-STD-882 criteria.

This includes informing the PO/COR and Program Office immediately upon any major accident/injury occurred. 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 in accordance with the guidelines (direction) of MIL-STD-882. The Hazard

Analysis Reports (Safety Assessment Reports) will be delivered to the government program office for review.

3.1.7.1 Electrostatic Discharge (ESD) Control

The contractor shall implement and maintain a process to control ESD in accordance with ANSI/ESD S20.20-2007. The contractor shall control

ESD in accordance with the contractor's ESD process.

3.1.8 Small Business Participation

The offeror shall implement a contractual Small Business Participation Plan and report on an annual basis actual achievement of meeting the goals set forth in the plan.

3.1.9 Associate Contractor Agreement

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.

The contractor shall plan for and conduct the verification activities in accordance with the F-15 TS specifications using government-approved Acceptance Test Procedures

(ATPs). The ATPs shall be submitted for government approval two (2) weeks prior to contractor verification testing. The contractor shall manage, track and correct discrepancies identified during testing. The contractor shall support the Government during Governmental tests and evaluations. The contractor shall document all test results for both government and contractor testing, to include test discrepancies, and consolidate into a report prior to Material Inspection and Receiving Report (DD Form

250) acceptance. The contractor shall resolve all deficiencies according to the process and timeline laid out in JRDS (ref. para 3.1.6). The contractor shall verify all modifications before the start of government testing.

The contractor shall conduct engineering verification testing in accordance with contractor-developed and government-approved specifications, ATPs and Approval Test

Guides (ATGs). Test results shall be submitted within 30 days of scheduled testing.

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

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.

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.

3.2.3.1 Software Releases

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

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 Jan 2015 at no capital investment cost to the government.

The contractor shall comply with local base standards for safety and security and the contractor shall maintain security for all facilities they occupy/manage in accordance with host base security requirements. Contractor shall be responsible for providing escorts for personnel requiring access to include but not limited to scheduled visitors, maintenance personnel and Government personnel. Contractor shall maintain and manage all contractor owned facilities in a manner in accordance with industry standards and equivalent to base facilities. The contractor shall create and maintain operating procedures in accordance with 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 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

3.3.1 Industrial Security

The contractor shall enter into a long-term Visitor Group Security Agreement

(VGSA) for services performed on-base.

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 in accordance with

Section J, Attachment 5 “DD Form 254 Contract Security Specification”.

The contractor shall oversee system-wide industrial security operations in accordance with 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 training facility.

The contractor shall perform visitor control using Joint Personnel Adjudication

System (JPAS) and XX.

When required by real world Force Protection Condition (FPCON) levels, the contractor shall secure the aircrew training facilities in accordance with base directives and control entry into those facilities in accordance with base plans unless relieved by US military personnel.

At the end of each workday, the contractor shall secure 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 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 overseas personnel, the contractor shall provide the passport number and visa with expiration date to the Government 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 contracting officer for health and safety purposes.

3.6 Logistics Data Library (LDL)

The contractor shall establish a LDL at the TSSC which shall be used to maintain 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. Aircraft

Technical Orders (TO), shall be compatible with the most current trainer baseline, shall be maintained where applicable (typically for maintenance trainers). The contractor shall maintain, update, and distribute baseline technical orders (TOs) for the maintenance trainer.

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 is capable of identifying 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 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 Contract

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

Office.

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

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 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 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. technical manuals, commercial manuals, software, engineering drawings, etc.). The RSP shall be maintained in serviceable condition and reflect the latest ATS configuration. At contract termination, the RSP shall be returned to the

Government in serviceable condition and in the latest configuration. The contractor shall provide an update to the RSP 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 ATD availability requirement and

MTD repair times. All recommendations and associated justifications concerning changes (additions/deletions) to the listing shall be submitted through the Procurement

Contracting Officer (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 Recompetition Support Package (RSP) Status Report

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

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

b) Spares inventory and status

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

3.7.2 Audits

The contractor shall support annual RSP audits and Physical and Functional

Configuration Audits (PCA/FCA) of the Product Baseline 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 government.

4.0 TSSC ENGINEERING (CLIN XXXX FP LOE)

4.1 Workload Management

The contractor shall staff the F-15 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 obsolescence issues, and technical data management. The contractor shall evaluate supportability, reliability, maintainability and parts obsolescence issues. The contractor shall provide engineering services as assigned via tasking letters from the Air Force Program Office or COR Maintenance.

The contractor shall provide logistics support, including maintenance actions, parts repair (including maintenance of the RSP and management, 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 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 Routine Tasking

Contractor shall perform routine engineering service taskings (typically under 500 hours). When directed by Air Force Program Office to perform routine engineering taskings, contractor shall respond providing the following:

Technical approach description

Test/verification approach description

Start and completion date

Estimate of not to exceed tasking effort (hours)

Upon receipt of government approval the contractor shall begin work.

4.2.2 Major Development Tasking

Contractor shall perform major development taskings (typically over 500 hours) such as engineering changes. The contractor shall provide the response in the form of an Engineering Change Proposal (ECP) and include the information for routine taskings above, plus selected items from the following list, as specified in the tasking, within 30 days of the government request:

A Work Breakdown Structure (WBS) for the planned work

A schedule

A staffing plan for the duration of the work

A risk analysis and mitigation plan

Any impacts to training devices and/or associated support equipment and software, including recommended changes to the RSP, and identification of any

Mean Time Between Failure (MTBF) changes

The subcontractor requirements

Cost element breakdown

A Work Breakdown Structure (WBS) for the planned work

A Integrated Master Schedule (IMS)

A staffing plan for the duration of the work

A risk analysis and mitigation plan

The subcontractor requirements

A procurement plan for any required acquisitions

A disposition plan for any waste or removed parts

Cost element breakdown

Technical approach description

A software development plan

Test/verification approach description

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 ATD/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 Rapid Prototype System (RPS) software in conjunction with the actual 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 modifications 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.

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 in accordance with 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).

4.5.1 Configuration Management Systems

The contractor shall use the current computer-based configuration management systems unless the contractor justifies 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 include 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 ATDs 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 System Verification Review (SVR)/Physical Configuration

Audit (PCA) of hardware and software. SVR shall take place prior to PCA.

5.0 MAINTENANCE (CLINS XXXX, YYYY FFP)

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 in the form of either on-call or on-site. CLS on-site activities shall center on ATD’s currently residing at Seymour Johnson AFB, NC.

CLS On-call activities shall center on the MTD’s.

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 ATDs 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 in accordance with 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 operations.

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 in accordance with Para 11.4.

5.1.3 Maintenance Concepts

The users and the types of trainers included in this contract require several different approaches for maintenance and logistics support. Detailed in the following paragraphs are various maintenance concepts the contractor shall use to maintain F-

15 training devices. The contractor may adjust concepts as training devices are added/deleted/re-allocated with the approval of the PO/COR or Program Office.

The contractor’s maintenance concepts shall meet operational needs and at the same time keep costs to a minimum. Requirements that shall be met for response times and availability rates are found in Section J, Attachments A: Contracts

Requirements; J: On-call CLS; and K: On-site CLS.

5.1.4 Maintenance Actions

CLS involves all levels of maintenance, supply support and material management of the training devices.

5.1.4.1 The contractor shall provide a schedule of recommended preventive maintenance actions to the COR in the monthly maintenance plan. The scheduled maintenance will be incorporated in the aircrew monthly schedule on a noninterference basis. The scheduled maintenance plan is implemented upon Government approval.

5.1.4.2 The contractor may have access to training devices to perform maintenance or modification when the training device is not required for training.