Attch_1_Performance_Work_Statement.pdf

FA8621-15-R-6315

Attachment 1 - Performance Work Statement (PWS)

23 Mar 15

Performance Work Statement (PWS)

For The Contractor Logistics Support (CLS)

Of The T-1A Ground Based Training System (GBTS)

Contract No.: FA8621-15-R-6315

Prepared by:

Air Force Life Cycle Management Center, Simulators Division

AFLCMC/WNS

2300 D Street, Bldg. 32

Wright-Patterson AFB, OH 45433-7249

Date: 23 Mar 15

PWS Change Matrix

Revision Date Description Paragraphs Contract Modification

Table of Contents

1.0 Background

1.1 Acquisition Strategy Objective

2.0 APPLICABLE DOCUMENTS

3.0 REQUIREMENTS

3.1 Program Management (PM)

3.1.1 Business Management

3.1.2 Program Meetings

3.1.3 Monthly Status Reports (MSRs)

3.1.4 Financial Management Tracking and Reporting

3.1.5 50/50 Requirement Report

3.1.6 Associate Contractor Agreements (ACAs)

3.1.7 Base Support

3.1.8 Security

3.1.9 Quality Program

3.1.10 Safety and Health

3.1.11 Voluntary Protection Program

3.1.12 Data Management

3.1.13 Configuration Management (CM)

3.1.14 Integrated Program Management Report (IPMR)

3.1.15 Deficiency Reporting (DR)

3.2 Contractor Logistics Support (CLS)

3.2.1 Operational Schedule

3.2.2 Surge

3.2.3 Mission Capability

3.2.4 GBTS Availability

3.2.5 Trainer Access and Support

3.2.6 Trainer and Maintenance Area Housekeeping

3.2.7 Trainer and Personnel Movement

3.2.8 Relocation of Personnel

3.2.9 Disposal

3.2.10 Emergency Weather Alert Plan

3.2.11 Maintenance

3.3 Training System Support Center (TSSC)

3.3.1 TSSC Operation

3.3.2 TSSC Tasks

3.3.3 Visual Database Maintenance and Updates

3.3.4 TSSC Equipment

3.3.5 TSSC Software, Data Rights, and Licensing

3.3.6 System Integration

3.3.7 Maintaining and Distributing Data Files

3.3.8 Concurrency

3.3.9 Change Management

3.3.10 Technical/COTS/Vendor Manuals

3.3.11 COTS Software Maintenance

3.3.12 Item Unique Identification (IUID)

3.3.13 Recompetition Support Package (RSP)

3.3.14 Support Equipment (SE)

3.3.15 Obsolescence

3.3.16 Revision of Engineering Drawings

3.3.17 Revision of Software Specifications and Documentation

3.4 Systems Engineering

3.4.1 System Testing

3.4.2 Technology Insertion

3.5 Transition

3.5.1 Transition Planning

3.5.2 Transition Integrated Product Team

3.5.3 Joint Inventories and Audits

3.6 Manpower Reporting

4.0 SERVICES SUMMARY

4.1 Services Summary Requirement

4.1.1 Surveillance Methods

4.2 Quality Assurance

5.0 ACQUISITION SYSTEMS PROTECTION

5.1 System Security

5.1.1 Supply Chain Risk Management (SCRM)

6.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

6.1 Government Furnished Property (GFP)

6.2 Damage to Government Property

6.3 Repair of Government Property

6.4 Replacement of GFP

6.5 Physical Inventory

7.0 GENERAL INFORMATION

7.1 Acronyms

7.2 T-1A GBTS Trainer Listing

PROGRAM SCOPE/OVERVIEW

1.0 Background

The T-1A Ground Based Training Systems (GBTS) program is now in sustainment after delivery of 16 Operational Flight Trainers (OFTs) and 14 Avionics Parts Task Trainers (APTTs). The T- 1A GBTS provides direct, transferable pilot training for the T-1A aircraft. The student gains knowledge and experience with all controls and instruments during takeoff, landing, Visual Flight Rules (VFR) and Instrument Flight Rules (IFR), flight, navigation and emergency conditions. The OFTs are supported by two Training System Support Centers (TSSCs). The TSSC at Randolph Air Force Base (AFB) is responsible for providing maintenance, modifications, engineering support, and configuration/data management support for the undergraduate pilot training baseline configuration. The TSSC at Naval Air Station (NAS) Pensacola is responsible for the Combat Systems Officer (CSO) baseline configuration. The Technical Data Package (TDP) consists of: software documentation, source code, hardware specifications, technical publications, Acceptance Test Procedures (ATP), engineering drawings, visual databases, maintenance and operation manuals/documentation, licenses, vendor documentation, and other related documentation required to maintain or enhance the training system.

1.1 Acquisition Strategy Objective

The contractor shall provide Contractor Logistics Support (CLS) in accordance with (IAW) contract requirements at the following locations:

Randolph AFB Two (2) OFTs and two (2) APTTs.

Columbus AFB Four (4) OFTs and three (3) APTTs Vance AFB Four (4) OFTs and four (4) APTTs Laughlin AFB Four (4) OFTs and four (4) APTTs NAS Pensacola Two (2) OFTs and one (1) APTT

The contract period of performance may be up to 5 years, 5 months (5-month base and 5 one-year pre-priced options). The contract shall also include a pre-priced option to extend services;

this shall not exceed 6 months. This shall be a Firm-Fixed-Price (FFP) contract with a Cost Reimbursable No Fee (CRNF) Contract Line Item Numbers (CLINs).

The contractor shall provide CLS to maintain a 95% availability rate. The contractor shall provide modification capability for Visual Database, NAVAIDs, Trainer Initial Conditions files, and Approach Plates at the TSSC at Randolph AFB. The Government will provide initial spare part package (Recompetition Support Package, RSP) as defined in this PWS and the contract.

The contractor shall support the government in maximizing competition on subsequent T-1A GBTS contracts by providing the government the ability to modify and maintain the software utilized on this contract throughout the life of the T-1A GBTS. Diminishing Manufacturing

Sources and Material Shortages (DMSMS) issues affecting availability requirements are monitored and reported to the government for consideration for necessary improvements and possible Engineering Change Proposals (ECPs). The contractor shall perform local configuration management (CM) tracking and repository functions of hardware, software, firmware, supporting engineering and technical documentation (via electronic means to the maximum extent possible) for all system baselines for which the contractor is responsible. Both TSSCs at Randolph AFB and NAS Pensacola shall be responsible for maintaining the product baselines common across all sites. Only the CSO baseline shall be maintained at the TSSC facility at NAS Pensacola.

2.0 APPLICABLE DOCUMENTS

The following documents form a part of this PWS to the extent specified herein. The Contractor shall maintain current and complete regulations, manuals and other directives deemed necessary to perform contract requirements. The Contractor shall comply with all regulations, manuals and other directives as referenced in the contract. Any reference to a publication includes the basic and all its supplements and amendments. Supplements or amendments may be issued during the life of the contract. In the event of conflict between the documents (other than those implementing Public Law) referenced herein and the contents of this PWS, then contents of this PWS shall be considered as superseding requirements.

Number

Document Name Date

2.1 Military Standards

MIL-STD-882E Standard Practice for System Safety 11 May 2012 MIL-STD-130N Identification Marking of United States Military

Property 16 Nov 2012

2.2 Department of Defense

JTR Joint Travel Regulations Current Issue

DoD 5000.04-M-1 Cost and Software Data Reporting (CSDR) Manual 4 Nov 2011 DoD 5220.22-M National Industrial Security Program Operating

Manual (NISPOM) 28 Mar 2013

DoDD 5000.01 The Defense Acquisition System 20 Nov 2007 DoDI 5230.24 Distribution Statements on Technical Documents 23 Aug 2012 DoDD 5230.25 Withholding of Unclassified Technical Data From

Public Disclosure 18 Aug 1995

DoDI 5000.02 Operation of the Defense Acquisition System 25 Nov 2013 DoDI 5000.64 Accountability and Management of DoD Equipment and Other Accountable Property 19 May 2011

DoDI 5010.12-M DoD Technical Data Management Program 14 May 1993 DoDI 5200.39 Critical Program Information (CPI) Protection within the Department of Defense (DoD) 28 Dec 2010

DoDM 5200.01, DoD Information Security Program: Controlled 24 Feb 2012

Vol 1-4 Unclassified Information (CUI)

2.3 Air Force Manuals, Regulations, and Instructions

AFI 21-113 Air Force Metrology And Calibration (AFMETCAL)

Management 23 Mar 2011

AFI 32-1065 Grounding Systems 1 Oct 1998 AFI 36-2251 Management of Air Force Training Systems 5 Jun 2009

AFI 63-101/20-

Integrated Life Cycle Management 7 Mar 2013

2.4 Air Force Occupational Safety and Health Regulations

AFI 91-203 Air Force Consolidated Occupational Safety

Instruction 19 Aug 2014

2.5 Occupational Safety and Health Administration Regulations 29 CFR 1910 General Industry Standards & Interpretations (OSHA

1910) Vol I http://www.osha.gov/pls/oshaweb/owadisp.show_document?p_ta ble=STANDARDS&p_id=9696

Various

Public Law 91-596 Occupational Safety and Health Act (OSHA) as amended by Public Law 101-552, §3101, November 5,

2.6 ANSI/ASQC Q90-Series - American National Standard Institute/American Society for Quality Control ASQ Q9001 Quality Management Systems - Requirements

Jan 2008

2.7 Other Documents

TO 00-20-2 Technical Manual: Maintenance Data Documentation 15 Nov 2009 TO 00-20-14 AF Metrology and Calibration Program 30 Sep 2011 TO 00-25-234 General Shop Practice Requirements For The Repair, Maintenance, and Test of Electrical Equipment 23 Mar 2014

TO 00-35D-54 USAF Deficiency Reporting, Investigation and Resolutions

1 Nov 2011

SAE EIA-649B Configuration Management Standard 1 Apr 2011 FIPS Publication

Standards for Security Categorization of Federal Information and Information Systems

Feb 2004

MIL-HDBK-61A Configuration Management Guidance Feb 2001

AIA/NAS

NAS411

Hazardous Material Management Program 30 Sep 2013

NIST Special Publication 800-53

Recommended Security Controls for Federal Information Systems and Organizations

Apr 2013

OPNAV INST

5100.23 Series

Navy Safety and Occupational Health 12 Jul 2011

SAE AS5553 Fraudulent/Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition

21 Jan 2013

3.0 REQUIREMENTS

3.1 Program Management (PM)

The contractor shall develop and maintain a program management process outlining the overall planning, programming, directing and controlling of the T-1A GBTS program. The contractor shall document the program management process in a Management Plan (MP). The contractor shall manage the T-1A GBTS program IAW the contractor’s MP. (CDRL A004, Management Plan, DI-MGMT-80004A)

The contractor shall not effect contract changes without the authorization of the Procurement Contracting Officer (PCO) or the Administrative Contracting Officer (ACO). Site operations personnel shall interface with the Government designated Contracting Officer Representative (COR) at each site for day-to-day liaison, oversight, and contract authority. The COR and HQ AETC/A3FP T-1A GBTS PM at Randolph AFB shall be the Government points of contact for all TSSC activities at Randolph AFB and NAS Pensacola.

The contractor shall provide the CORs with access to the contractor’s performance data for the purpose of assisting the Program Management Office (PMO) in measuring the contractor’s performance. Site operations personnel shall also allow COR daily access to site areas for the purpose of evaluating contractor performance factors such as maintenance/logistics documentation, housekeeping, safety, conservation, efficient management of Air Force materials, and security of Air Force assets.

3.1.1 Business Management

The contractor shall manage the T-1A GBTS CLS program in a manner that supports the requirements of AFI 36-2251. The contractor shall perform all program and technical management functions required to efficiently and effectively control program cost, schedule, and performance. The contractor shall be responsible for program management, subcontractor and vendor management, and financial management, including the planning, establishment, and operation of the GBTS CLS support activities under this contract. Management activities shall include oversight of hardware and software engineering and engineering support.

3.1.1.1 Personnel Staffing

Assignment of contractor personnel shall be the responsibility of the contractor. The contractor shall notify the PMO and update the organization chart if personnel changes occur.

3.1.1.2 Personnel Qualifications

Contractor personnel shall be qualified in the operation/instruction, maintenance and logistic support of the T-1A GBTS and TSSC.

3.1.1.3 Personnel Training

The contractor is responsible for all training requirements and costs associated to perform the requirements of this contract.

3.1.1.4 Pass and Identification

All assigned contractor personnel shall obtain the passes and long-term identification as required by the Government at each site. The contractor shall establish procedures to return all passes and identification when personnel depart a site or separate from this contract. The contractor shall comply with Government security procedures and Facility Security Plans at each site.

3.1.1.5 Subcontractor Management

In accordance with FAR 52.219-14 - Limitations on Subcontracting (Nov 2011), for a service contract, at least 50% of the contract cost incurred for personnel shall be expended for employees of the prime Small Business contractor. The contractor shall present how this requirement is being met at all Program Management Reviews (PMR).

3.1.2 Program Meetings

3.1.2.1 Program Management Review

The contractor shall support two PMRs per fiscal year at the Government’s discretion and a location chosen by the Government. It may be conducted in person or telephonically. The PMR shall provide details of program schedule, technical and financial status, action items, risk management, and other topics as needed. The Government reserves the right to change the scheduling of these meetings, as required. Contractor participation shall include presentation of tasking status, generation of recommendations, proposed agendas, and generation and distribution of approved meeting minutes. The contractor shall prepare and distribute draft meeting minutes to be approved by the PMO no later than 10 days after meeting completion.

(CDRL A005, Conference Agenda, DI-ADMN-81249A; CDRL A006, Conference Minutes, DI-ADMN-81250A)

3.1.2.2 Post Award Conference

A Post Award Conference shall be held within ninety (90) calendar days after contract award, at the discretion of the PCO. The contractor shall host a post award conference at their facilities.

The conference shall introduce the key participants and identify points of contact. The ACO will lead the discussion so both parties understand the scope of the work.

(CDRL A006, Conference Minutes, DI-ADMN-81250A)

3.1.2.3 Technical Interchange Meetings (TIMs)

The contractor shall support up to two (2) TIMs per year, as required at Randolph AFB. The TIMs will be used to discuss program issues, between PMRs, based on any Engineering Change Proposals (ECPs) design or test reviews. (CDRL A006, Conference Minutes, DI-ADMN- 81250A)

3.1.3 Monthly Status Reports (MSRs)

The contractor shall submit MSRs, containing the following elements:

• Operational Schedule

• Surge Activity

• Availability Summary per GBTS System to include:

- Hours Available

- Hours Scheduled

- Hours Utilized

- Missions Scheduled

- Missions Completed

- Availability Rate

- Operational Losses

• Maintenance

- Maintenance Actions (The Contractor shall utilize the AFTO Form 781 series, IAW

AFTO 00-20-2, Paragraph 7.9 as a guide on-equipment repairs), (Off-equipment repairs shall be documented using TO 00-20-2, Paragraph 7.11 as a guide.)

- Spares consumption

• Identify any trends or recommendations for corrective actions

• Engineering Accomplishments

• Report and track obsolescence issues (CDRL A001, Contractor’s Progress, Status and Management Report, DI-MGMT- 80227/T)

3.1.4 Financial Management Tracking and Reporting

The contractor shall develop, operate and maintain a financial management tracking system. The contractor shall provide access to supporting reports and documentation that augment the joint government/contractor system management capability. The contractor shall support the Government’s budgeting process by providing data and insight into T-1A GBTS expenditures and termination liability. The contractor shall also support the Government’s process of developing and maintaining Life Cycle Cost (LCC) estimates for the T-1A GBTS by providing data and insight into the costs of maintaining and modifying the T-1A GBTS. The contractor shall comply with DFARS 252.234-7003 Notice of Cost and Software Reporting System (NOV 2010) and DFARS 252.234-7004 Cost and Software Data Reporting System (NOV 2010) and shall accomplish cost and software resources reporting IAW DoD 5000.04-M-1.

The contractor shall prepare a Contract Funds Status Report on a quarterly basis. (CDRL A007, Contract Funds Status Report, DI-MGMT-81468/T).

The contractor shall prepare a Contractor Sustainment Report on a quarterly basis. (CDRL A008, Contractor Sustainment Report, DI-FNCL-81831).

3.1.5 50/50 Requirement Report

The contractor shall provide depot data IAW Title 10 United States Code Section 244 known as the “50/50” law, as amended by the National Defense Authorization Acts of FY98. (CDRL A009, The 50/50 Requirement Report, DI-MGMT-81749A/T)

3.1.6 Associate Contractor Agreements (ACAs)

(a) The Contractor, Contractor's subcontractors and or Contractor's subcontractors lower tier subcontractors shall enter into associate contractor agreements (ACAs) for any portion of the contract requiring joint participation in the accomplishment of the Government's requirement.

The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the T-1A GBTS which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. Associate Contractors are listed in (h) below.

(b) ACAs shall include the following general information:

(1) Identify the associate contractors and their relationships.

(2) Identify the program involved and the relevant Government contracts of the associate contractors.

(3) Describe the associate contractor interfaces by general subject matter.

(4) Specify the categories of information to be exchanged or support to be provided.

(5) Include the expiration date (or event) of the ACA.

(6) Identify potential conflicts between relevant Government contracts and the ACA;

include agreements on protection of proprietary data and restrictions on employees.

(c) A copy of such agreement shall be provided to the Contracting Officer for review before execution of the document by the cooperating contractors.

(d) Nothing in the foregoing shall affect compliance with the requirements of the clause at AFFARS 5352.209-9000, Organizational Conflict of Interest.

(e) The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

(f) Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

(g) All costs associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended as required by the Government during the performance of this contract.

(h) The following contractors are associate contractors with whom agreements are required:

CONTRACTOR ADDRESS PROGRAM/CONTRACT

L-3 Link Simulation & Training 2200 Arlington Downs Road F33657-01-D-2077 QP02 Arlington, TX 76011-6320

RSI Visual Systems Inc. 955 Freeport Parkway, Suite 100 F33657-01-D-2077 QP02 Coppell, TX 75019

UFA, Inc. 12 South Summit Avenue, F33657-01-D-2077 QP02

Suite 220 Gaithersburg, MD 20877

3.1.7 Base Support

Base support will be provided by the Government to the Contractor. Base support includes Government-controlled working space, material, equipment, services (including automatic data processing), or other support which the Government determines can be made available at, or through, any Air Force installation where this contract shall be performed. All Government property in the possession of the Contractor, provided through the base support requirement, shall be used and managed in accordance with the Government Furnished Property requirements.

3.1.8 Security

Operational Security (OPSEC) practices are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of Critical Information (CI). OPSEC practices are required throughout the lifecycle of this contract.

The Contractor shall:

a) Maintain physical security of the simulator system area.

b) Open building one hour prior to start of the operational window and secure the simulator bays and maintenance area at the close of operational window.

c) Be the point of contact for access to the trainer area during non-duty hours.

i. The Government’s COR at each site shall provide access to the trainer site for emergency personnel if Contractor’s personnel are not available.

d) Escort contracted janitorial services.

e) Maintain compliance with the base security plan.

f) Safeguard all Government property provided for use.

g) Be responsible for all keys or cipher combinations received or issued by the

Government, and shall assure the keys are not lost or misplaced and that combinations are not compromised or used by unauthorized persons. Keys issued to the Contractor, by the Government, shall not be duplicated by the Contractor.

h) Identify themselves as Contractors or subcontractors during meetings, telephone conversations, in electronic messages, or correspondence related to this contract.

i) Clearly identify contractor-occupied facilities such as offices, separate rooms, or cubicles with Contractor supplied signs, name plates or other identification, showing that these are work areas for Contractor or subcontractor personnel

3.1.8.1 Safeguarding Government Property

The contractor shall ensure adequate facility security processes and procedures are in place to safeguard Government property and information. The contractor is responsible for all Government property provided to them to perform the requirements of this contract. The contractor shall comply with all Air Force security procedures, directives and local policies for safeguarding Government property.

3.1.8.2 Damage Report

The contractor shall immediately report damage of Government property to the COR or onsite Government representative and ACO.

3.1.8.3 Damage Investigations

The contractor shall not condemn or dispose of Government property until released to do so by the ACO via the COR. The contractor shall immediately secure the area and damaged item(s) until released by the ACO. The COR will immediately secure the damaged equipment until released by the investigating authority. The COR through the ACO, will accomplish such releases. If the Government elects to conduct an investigation of the incident, the contractor shall cooperate fully and assist Government personnel until completion of the investigation. The contractor shall incur the costs, direct or indirect, when the damage to Government property is due to contractor neglect or misuse. The contractor shall include a clause in any of its subcontracts to require the subcontractor’s cooperation and assistance in mishap reporting and investigation, as well as fiscal responsibility as required.

3.1.9 Quality Program

The Contractor shall implement and maintain a quality assurance program for support of T-1A GBTS and TSSC operations. The Contractor shall allow access to all program data, documentation, and records of inspection throughout the contract performance period, so that performance can be evaluated by the Government. The Contractor shall correct noted deficiencies and provide a mitigation strategy to correct deficiencies within an agreed-to timeframe coordinated with the Government program office. The Contractor shall develop a Quality Assurance Program Plan to be delivered 30 days after transition completion. (CDRL A010, Quality Assurance Program Plan (QAPP), DI-QCIC-81794)

At a minimum, the plan shall address compliance and implementation of the following items:

a) A process to ensure the required trainer availability rate is maintained on all training devices.

b) An inspection and audit process to ensure serviceable spare level quantities are maintained in the Recompetition Support Package (RSP).

c) A periodic audit process to ensure service delivery objectives as indicated in Table 4.1 are met.

3.1.10 Safety and Health

The Contractor shall develop and support a system safety program in compliance with industry best practices, Occupational Safety Health Act (OSHA), Air Force Occupational Safety and Health (AFOSH), and the Naval Occupational Safety and Health Program (NAVOSH). The contractor shall comply with all applicable federal, state, county, local, and territorial statutory and regulatory environmental requirements applicable to T-1A GBTS operations. Contractor shall comply with the requirements of MIL-STD-882E.

3.1.10.1 Hazardous Waste

The contractor shall be responsible for the proper handling and disposal of all hazardous waste resulting from the performance of this contract. Government facilities, services, and equipment shall be used where available. Ozone Depleting Substances (ODS) shall be managed IAW National Aerospace Standard (NAS) 411. The requirements of Air Force Federal Acquisition Regulations Supplement (AFFARS) 5323.804 shall be passed down to vendors and subcontractors. The contractor shall comply with applicable laws and regulations, including USAF and Base operating procedures, for hazardous waste management and disposal.

3.1.11 Voluntary Protection Program

The Contractor shall comply with the specific health and safety requirements identified in this PWS, as well as the OSHA (Public Law 91-596) requirements and NAVOSH requirements in accordance with OPNAV INST 5100.23 Series. 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.1.12 Data Management

The contractor shall develop and implement a data management process and document it in the Contractor’s Configuration Management Plan (CMP) for all phases of the training system life cycle. The contractor shall plan for, generate, collect, prepare, publish and distribute contractually required data with content, format, and in quantities specified by the Contract Data Requirements List (CDRL). The contractor shall be responsible for the management of changes, additions, and deletions of data items. The contractor shall recommend items to be added, revised, or deleted, as appropriate, and shall maintain the status of all data deliverables. The contractor shall generate and maintain Contract Data Status information to monitor all data activity (i.e., delivery, documentation, approvals due but not delivered, status of delinquent data).

This data shall be available via a web-based integrated data environment. (CDRL A011, Contractor’s Configuration Management Plan, DI-CMAN-80858B).

3.1.12.1 Data Accession List (DAL)

The contractor shall prepare a DAL. The DAL shall list all data the contractor and subcontractors generate during the course of this contract to which the Government is able to access. This data is in addition to data required by the DD Form 1423s. This data shall be available to the Government upon PCO request and is not a substitute for data requirements ordered elsewhere in the PWS, CDRLs, and contract. (CDRL A024, Data Accession List (DAL), DI-MGMT- 81453A/T).

3.1.12.2 Web-based Integrated Data Environment

The Contractor shall establish and maintain a Web-based Integrated Data Environment. The Contractor, its sub-contractors and the Government shall have access to this web-based Integrated Data Environment. Access to the website shall be controlled. The Web-based Integrated Data Environment shall allow electronic access to CDRLs.

3.1.13 Configuration Management (CM)

The contractor shall define, implement and maintain a configuration management process using MIL-HDBK-61A and ANSI/EIA-649 as a guide to all CM procedures. Management and control of the configuration of the T-1A GBTS shall be the responsibility of the contractor and shall accomplish this through the TSSC. The contractor shall submit a CMP, which addresses the management of baseline, obsolescence, technology refresh management, and process improvements. (CDRL A011, Contractor’s Configuration Management Plan, DI-CMAN- 80858B).

3.1.13.1 Configuration Audits

The Contractor shall co-chair with the Government all System Verification Review/Physical Configuration Audits (SVR/PCA). A configuration audit will be conducted when there is a change to the Government approved baselines. (CDRL A006, Conference Minutes, DI-

ADMN-81250A)

3.1.14 Integrated Program Management Report (IPMR)

The contractor shall prepare an IPMR for system transition, and any system modifications.

(CDRL A003, Integrated Program Management Report, DI-MGMT-81861/T)

3.1.15 Deficiency Reporting (DR)

The Contractor shall participate in the Government’s deficiency reporting, investigation and resolution system using TO 00-35D-54. A deficiency report is a quality defect, defective GFE part, software failure due to a latent defect or a part that has to be redesigned/retrofitted (latent design flaw) and can be written against any asset. The Contractor shall use the deficiency report to ensure complete information is input to the Joint Deficiency Reporting System (JDRS) system. After the Government deficiency reporting and tracking system is established, the Contractor shall act as the originator, originating point, and support point as defined in TO 00- 35D-54. Deficiency reports may be initiated by the contractor, Government personnel, or Government-authorized contracted on-site staff. The contractor shall analyze T-1A GBTS training system deficiencies, determine action, resolve and manage the support process throughout the contract period of performance. The contractor shall evaluate this data continuously to detect and report maintenance and sustainment trends. The formal closure of the DRs will be through the Government's Material Improvement Product Review Board. (CDRL A012, Material Improvement Project Report, DI-MGMT-80258A/T)

3.2 Contractor Logistics Support (CLS)

The contractor shall manage, maintain, update, and support the T-1A GBTS at five (5) USAF sites as identified in Paragraph 7.2, T-1A GBTS Trainer Listing.

The contractor shall:

1. Provide the complete range of logistics support services to the T-1A GBTS Program.

2. Systematically identify, assess, and provide logistics support that will ensure the maximum level of operational performance and availability of T-1A GBTS systems in the field.

3. Maintain a system availability rate of 95% for all GBTS devices IAW paragraph 3.2.4

4. Provide on-site scheduled and unscheduled maintenance support for the T-1A GBTS.

5. Ensure that scheduled maintenance does not conflict with scheduled training operations.

6. Install only Government approved software updates provided by the TSSCs.

7. Ensure that scheduled GBTS maintenance does not conflict with scheduled training operations.

8. Provide all hardware and software maintenance support required to maintain the system in a mission capable condition.

9. Record, track, and report system repair and maintenance activity to include all noted deficiencies and malfunctions. Contractor shall retain this data throughout life of contract.

10. Evaluate this data continuously to detect maintenance trends.

11. Analyze and resolve system deficiencies and manage the support process throughout the contract period of performance.

12. Keep Government informed of obsolescence risks and issues.

3.2.1 Operational Schedule

The contractor shall support the Operational Support Window requirement. The Operational Support Window shall be defined as the scheduled hours of system availability for use. The contractor shall be capable, with a 30-day notification, of supporting 12, 14 or 16 hours per day Monday through Friday training schedule, excluding Federally-observed national holidays. OFT missions shall be scheduled for a length of 3 hours. A successfully completed mission shall be annotated as a successfully completed scheduled mission on Air Force Technical Order (AFTO) Form 781.

3.2.2 Surge

Surge shall be defined as that time when the contractor is tasked to work outside or exceeding the daily Operational Support Window. This shall include weekends, holidays and extended hours. The contractor shall support surge required to support training, access for other contractors during non-work hours, or to support Government operations and exercises. The contractor shall notify the PCO/ACO that a surge requirement exists and, upon receipt of PCO/ACO authorization, proceed with surge support.

3.2.3 Mission Capability

The contractor shall maintain the system in a mission capable condition as defined:

a. Fully Mission Capable (FMC) GBTS device: GBTS device can perform all operational training requirements required by the mission.

b. Not Mission Capable (NMC) GBTS device: GBTS device not able to perform some or all command assigned training requirements.

3.2.4 GBTS Availability

The contractor shall maintain a 95% availability rate for all training devices. See Contract Clause H-001 Ground Based Training System (GBTS) Availability.

3.2.4.1 Disagreements

Disagreements between the contractor and an instructor regarding performance of, or credit for, a mission shall go to the COR for resolution. If the disagreement persists, complete details of the disagreement shall be sent to the ACO with a copy to the PMO. The ACO will make the final determination.

3.2.4.2 Measuring Performance

Availability provides a measurement of contractor performance. Equipment shall be maintained in a satisfactory condition with all repairs made in an acceptable and timely manner.

Housekeeping, safety, conservation, efficient management of Air Force materials, security of Air Force assets and meeting documentation requirements shall also be considered performance factors. The COR will evaluate all these factors on a daily basis.

3.2.5 Trainer Access and Support

The contractor shall provide access and support to the trainer as specified in the following paragraphs.

3.2.5.1 Government Use Time

The contractor shall make GBTS equipment available to the Government for, but not limited to, accident investigation, unit-specific non-syllabus training and other activities with contractor maintenance support and operational support (i.e., system operation). The contractor shall ensure operations or maintenance personnel are available to support Government use of training GBTS, as required. Government use shall have priority; however, conflicts between Government Use Time and normal training may relieve the contractor in having to meet the device availability requirements, but only for that incident. The contractor shall inform the Government of these conflicts as soon as possible so that the proper resolution can be formulated. A minimum number of hours shall be set aside each month as Government Use Time. The amount of time per OFT set aside each month shall be mutually agreed on by the contractor and Government after the Post-Award Conference. This allotted time shall not go beyond the contracted hours established for each training site.

3.2.5.2 Other Contracted Personnel

The contractor shall provide access to other contractors as approved by the COR, PCO, and the using command on a non-interference/no-cost basis. This shall, where required, involve GBTS/TSSC access for installation and testing. This access may include, but not limited to, review of spares, support equipment, drawings, technical data, source code, software documentation, and visual analysis of the operating functions of the training systems. The contractor shall maintain visitor logs using AF Form 1109. The contractor shall escort uncleared visitors in secured areas. This support shall fall within normal operational schedule, unless otherwise directed by the COR.

3.2.5.3 Simulator Certification (SIMCERT)

The contractor shall support the using command by assisting in Simulator Certifications (SIMCERT), Inspector General (IG) inspections, and Air Force audits as required.

3.2.6 Trainer and Maintenance Area Housekeeping

The contractor shall perform routine clean-up, remove residual materials from OFTs, TSSC, and shop work areas. Data library, offices and RSP storage areas shall be kept clean and free of clutter.

3.2.7 Trainer and Personnel Movement

Upon direction and funding by the PCO, the contractor shall provide for the relocation of the OFTs, TSSC equipment, and subsystems. The contractor shall develop, implement and maintain preservation, packaging, packing and marking of all materials/items to protect against physical damage, mechanical damage and other forms of degradation during storage, handling and shipments to the destination specified by the Government. The contractor shall ensure that materials/items can be transported by the desired modes of transportation via commercial means.

The contractor shall reassemble and test the OFTs and TSSC equipment at the new location.

3.2.8 Relocation of Personnel

In the event that OFTs or the TSSC are relocated for operational purposes, and upon direction and funding by the PCO, the contractor shall relocate OFT and or TSSC personnel to continue to fulfill the requirements of this contract.

3.2.9 Disposal

The Contractor shall be responsible for reporting excess personal property IAW FAR 52.245-1, “Government Property” and DFARS clause 252.245-7004, Reporting, Reutilization, and Disposal”.

In the event that OFTs, TSSC or subsystems are no longer required by the using command and upon coordination with the Plant Clearance Officer (PLCO) and direction and funding by the PCO, the contractor shall dismantle, package and ship the equipment to the destination specified by the Government.

3.2.10 Emergency Weather Alert Plan

The contractor shall develop an emergency weather alert plan, delineating actions to be accomplished upon notification of severe weather. The contractor shall coordinate these procedures with the site COR to assure the plan is consistent with local operating procedures for the safety of personnel and equipment. The plan shall be available for Government review if requested.

3.2.11 Maintenance

The contractor shall provide total maintenance to include:

• All inspections

• Preventive and unscheduled maintenance

• Cleaning, lubrication, service and replacement of parts

• Troubleshooting, repair, bench check, re-assembly and testing

• Calibration and conducting of operational checks to verify the correction of malfunctions, adequate and proper serviceable condition of components, subsystems or systems

Frequency and requirements for inspections, servicing and preventive maintenance will be obtained from technical manuals, vendor manuals, Air Force instructions or industry standards.

The contractor will inspect, maintain, and repair the in-house electronic equipment grounding system and ensure that it continues to comply with AFI 32-1065. Resistance measurements and any repairs required to grounding systems shall be reported to the Base Civil Engineer (CE) through the COR. The contractor shall monitor and advise the COR of suspected problems to Real Property interfaces, such as power, ground, environmental systems, to assure compatibility and integrity of training systems and subsystems. The contractor shall provide any additional resources not provided by the Government necessary to accomplish these tasks at contractor expense. A summary of maintenance actions shall be provided in accordance with paragraph 3.1.3, MSR. (CDRL A001, Contractor’s Progress, Status and Management Report, DI-

MGMT-80227/T)

3.2.11.1 Basic Hand Tools

The contractor shall provide for all basic hand tools required to perform maintenance requirements of this contract.

3.2.11.2 Initial Startup

Contractor maintenance personnel shall be available for each scheduled training mission.

Maintenance personnel will prepare the GBTS for scheduled mission start.

3.2.11.3 Repair

The contractor shall provide CLS for total logistics support for all levels of maintenance to the GBTS, TSSC and support equipment. The contractor shall, where appropriate, suggest different CLS approaches to meet operational needs. The contractor shall conduct repair, maintenance and test of electrical components using TO 00-25-234 as a guide.

3.2.11.4 Uninterrupted Power Supplies (UPS) & Power Line Monitors (PLM)

The contractor shall provide field maintenance to the UPSs and PLMs to the level at which technical data and spares are available.

If repair is beyond the contractor capability or resources, then the contractor shall arrange for repair or replacement of UPS/PLMs by Original Equipment Manufacturer (OEM) or certified repair source (vendor) . The contractor shall obtain onsite COR approval to place the UPS/PLM in “bypass”. In the absence of the COR, the contractor may elect to operate in the bypass mode if deemed in the Government’s best interest. The contractor shall, within 24 hours, determine UPS/PLM failure cause, and repair or initiate vendor repair action. Vendor support shall be on site within 72 hours of initiation of request for support. If UPS/PLM failure impacts trainer availability rate, payment reduction will be based on the COR assessment of the situation leading to unconditioned power problem and the contractor responsiveness to the problem.

3.3 Training System Support Center (TSSC)

The TSSC shall be the focal point for accomplishing and managing hardware and software modifications, technical and engineering data tasks, RSP tasks, configuration control, data collection and reporting. The contractor shall design, develop and test changes to all software and hardware baselines. All tasks in this section shall be considered part of the TSSC core Level of Effort (LOE).

3.3.1 TSSC Operation

The contractor shall operate and maintain the TSSCs at Randolph AFB and NAS Pensacola. The contractor shall provide the necessary trained personnel and resources to operate the TSSC.

While operational maintenance is the responsibility of each site, the TSSC shall be responsible for maintaining the product baselines common across all sites. Only the CSO baseline shall be maintained at the NAS Pensacola TSSC facility. Maintaining the product baseline includes providing modification support for the GBTS, configuration and data management. The TSSC processes and organization shall be based on the Systems Engineering practices referenced in the Systems Engineering Management Plan (SEMP) (Section 3.6.1).

The contractor shall not make any unauthorized modifications to the T-1A GBTS or any item under CM. Any proposed TSSC changes to the system shall first be screened, reviewed, and approved by the Government.

The contractor shall be responsible for and shall develop, test and distribute changes, modifications and/or updates for:

• Visual database maintenance and updates

• T-1A GBTS NAVAIDS databases

• Trainer Initial Condition (TIC) files

• Approach Plates

• Concurrency

• TSSC hardware

• Technical manuals, engineering drawings and other engineering data, and vendor manuals.

• Software and hardware modification development, test, distribution and installation

• Hardware and software configuration management of the following items:

• OFT and APTT

• RSP management

• Maintenance data collection

3.3.2 TSSC Tasks

The contractor’s TSSC personnel shall determine the best method for accomplishing all work required and/or assigned by the Government. The contractor shall respond to the TSSC PO’s and HQ AETC/A3FP T-1A GBTS PM's authority for tasking and prioritizing TSSC work within the constraints of the contract. The contractor shall be responsive to possible changes to the priority scheme that may occur during the option year depending on the training needs. TSSC equipment shall only be used to accomplish tasks of the TSSC. TSSC equipment shall not be used for any other purpose without prior TSSC COR approval. Contractor personnel at the TSSC shall support the following activities:

• TSSC management

• Product baseline management

• Baseline distribution to sites

• Baseline software development/modification/merge

• Database administration

• Configuration management, status accounting

• Data and documentation review/management/updates

• Testing

3.3.3 Visual Database Maintenance and Updates

The contractor shall maintain, update, and test changes to the visual database models to include terrain, texture, and 3-D models for the existing T-1A GBTS.

3.3.4 TSSC Equipment

The contractor shall evaluate the existing TSSC equipment and identify additional equipment requirements for the TSSC to the Government for approval. Additional equipment shall be procured as Contractor Acquired Property (CAP). Any additional TSSC equipment procured shall be added to RSP, maintained, and managed as support equipment.

3.3.5 TSSC Software, Data Rights, and Licensing

The contractor shall obtain any additional software development tools required to satisfy the TSSC requirements. The contractor shall evaluate TSSC Software, Data Rights, and Licensing.

The contractor shall take the required actions to assure sufficient data rights and licensing agreements have been secured from the incumbent to begin TSSC Operations. Any agreements obtained shall be documented via ACA and reported IAW paragraph 3.1.6.

The Government requires Unlimited or Government Purpose Rights for all newly developed items, components, processes, computer software, and technical data developed in the execution of this contract.

3.3.6 System Integration

The contractor shall act as system change integrator, regardless of the source of the change, modification or update. The contractor shall consider the GBTS system as a whole. System analysis shall be performed to integrate software changes to achieve the desired system functionality. This involves understanding of the subsystem interfaces between the GBTS maintained software subsystems and the other subsystems (hardware and or software). (CDRL A003, Integrated Program Management Report, DI-81861/T)

3.3.7 Maintaining and Distributing Data Files

The Contractor shall maintain technical documentation supporting TSSC modifications and submit updates as they become available. These documents shall include:

• Operator's manuals

• Users guides

• Handbooks

• System administration guides

• System Operation and Maintenance Manuals

The TSSC shall have capability to keep on record one full database and models for backup and debugging purposes. The TSSC shall have the capability to perform full restore of these files, if needed. Each operating site shall have a full database backup for system restore capability. The TSSC shall distribute changes to the sites to maintain a current backup capability.

3.3.8 Concurrency

The contractor shall ensure that the GBTS are concurrent with the aircraft functional baselines.

Concurrency modifications can originate from the AETC, the aircraft platform office, or by change proposals originating from the contractor or other Government personnel; however, all concurrency modification efforts shall require direction from the PCO.

3.3.9 Change Management

The contractor shall perform change management and maintain technical baselines to include change management documentation for software, hardware, support equipment, engineering data, drawings, technical orders/manuals, and databases. The contractor is subject to Government oversight and audits and shall provide change management documentation as required. The contractor shall be responsible for maintaining, updating, and distributing all technical publications, specifications and engineering data needed for operation and maintenance of the devices. The contractor shall provide the required labor and materials to develop, test and distribute modification kits to all GBTS sites in support of minor hardware/software modifications (Class II Changes). The contractor shall make all Class II change documentation available to the Government for review. The effort to accomplish these minor modifications shall be included as part of the contractor’s proposed labor and material for the TSSCs. Class 1 changes shall be approved by the Government through the Engineering Change Proposal (ECP) process. The PCO shall be the final authority in the determination of what constitutes a Class II change. (CDRL A018, Revision To Existing Government Documents DI-ADMN-80925)

3.3.9.1 Engineering Change Proposal (ECP)

The contractor shall prepare and submit an ECP as requested by the PCO, whenever a change to baseline documentation is identified or requested. (CDRL A013, Engineering Change Proposals, DI-CMAN-80639C/T)

3.3.9.2 Contract Change Proposal (CCP)

The contractor shall prepare and submit a CCP when proposing a change to the contract not impacting the requirements specifications. (CDRL A014, Contract Change Proposal, DI-

ADMN-81401B)

3.3.9.3 Requests for Deviation

The contractor shall prepare and submit a Request for Deviation if it seeks a deviation from the requirements specifications or their appendices. (CDRL A015, Request for Deviation, DI-

CMAN-80640C)

3.3.9.4 Status Accounting

The contractor shall generate internal Configuration Status Accounting (CSA) records tracking the configuration change history for all devices and the TSSC. The contractor shall:

a. Identify the current approved configuration documentation

b. Record and report implementation status of authorized changes.

c. Provide the traceability of all changes from the original baseline configuration documentation

d. Report the effectivity and installation status of configuration changes

The contractor shall maintain:

e. A current list of current support manuals and documentation

f. Listing of current engineering drawings and associated lists

g. Listings of current software versions

h. Listings of current…