PWS.pdf

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

TRAINING AIRCRAFT DIVISION

TINKER AIR FORCE BASE, OK 73145

FA8106-15-R-0001

APPENDIX A

PERFORMANCE WORK STATEMENT

FOR

T-1A ENGINEERING SERVICES SUPPORT

PREPARATION DATE: 19 February 2015

PREPARING ORGANIZATION: AFLCMC/WLZW, TINKER AFB OK 73145-3020

Table of Contents (Ctrl+click to advance to paragraph)

Section Paragraph/Title Page Number

1 SECTION I – DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.1 Contractor Responsibility

1.2 Definitions

1.3 Platform Description

1.4 Program Requirements

1.4.1 Mission Essential Services

1.5 Program Management

1.5.1 Program Management

1.5.2 Obsolescence

1.5.3 COMBS Support

1.5.4 Meeting Support

1.5.4.1 Weekly Status Report

1.5.4.2 Program Management Review, System Safety Group & System Supportability Review

1.5.4.3 Configuration Control Board

1.5.5 Cost and Schedule Reporting Requirements

1.5.6 PCO Letters & ROM Preparation

1.5.7 Technical Order Library

1.5.8 Service Information and FAA Directive Review

1.5.8.1 Evaluation Content

1.5.8.2 Urgent FAA Airworthiness Directives (AD)

1.5.9 Operational Safety, Suitability & Effectiveness

1.5.9.1 Systems Engineering Approach

1.5.9.2 FAA Certification

1.5.9.2.1 FAA Records

1.5.10 Commercial Manuals

1.5.11 Engineering Data

1.5.12 Data Rights

1.5.13 Security

1.5.14 Contractor Requirements for DoD Common Access Card

1.5.15 Contractor Authorization to be Passenger on T-1A

1.6 Recurring Engineering

1.6.1 Recurring Engineering Sustainment

1.6.2 Configuration Management

1.6.2.1 Configuration Identification

1.6.2.2 Configuration Change Control

1.6.3 In-Flight Emergency (IFE) Support and Crisis Management Team (CMT) Support

1.6.4 Mishap Investigation and Recovery Support

1.6.5 Maintenance Program Support

1.6.6 Data Accession List

1.6.7 Environmental Support

1.6.8 Safety

1.6.8.1 Safety Inquiries

1.6.9 Reliability and Maintainability Support

1.6.10 Technical Order Support

1.6.10.1 Commercial Manuals (not used by Air Force personnel to perform maintenance)

1.6.10.2 AFTO Form 22 and AF Form 847 Evaluations

1.6.10.3 Changes Resulting from Service Documents or Deficiency Reports

1.6.11 Systems Engineering Management Plan

1.7 Recurring Engineering Maintenance/Technical Assistance Requests (-107 Requests)

1.8 Recurring Engineering – Deficiency Reporting

1.9 Non-Recurring Engineering

1.9.1 Reporting Requirements

1.9.2 EA Contractor Acceptance and Contractual Changes

1.9.3 EA Performance

1.9.4 EA Reporting

1.9.5 Notification of EA Expenditures

1.9.6 Data Rights for EA Assignments

1.9.7 EA Completion/Closure

1.9.8 Scope of EA Activities

1.9.9 Engineering Studies

1.9.10 Data Accession List Data Base

1.9.11 Safety and Environmental Management

1.9.12 System Augmentation

1.9.12.1 Aircraft Prototype Modifications

1.9.12.2 Support for Aircraft Modifications

1.9.12.3 Technical Data Review

1.9.12.4 Engineering Support Required for System Integration

1.9.12.5 Test Support of Modifications

1.9.12.6 Configuration Management

1.9.12.7 Service Instructions

1.10 Over and Above

1.10.1 ‘Over and Above’ Shall include but not be limited to AIRCRAFT REPAIR

1.10.1.1 Repair Efforts

1.10.1.2 Contractor Field Team Efforts

1.10.1.3 Unscheduled Depot Maintenance

1.11 Other Meetings

1.12 Quality Assurance Provisions

1.13 Special Projects

2 SECTION II – SERVICE SUMMARY

2.1 Service Summary (SS) Requirements

2.2 Performance Objectives and Thresholds

2.2.1 Surveillance Methods

2.3 Contractor Performance Evaluation

3 SECTION III – Government Furnished Property (GFP) ATTACHMENT 1 Acronyms ATTACHMENT 2 Definitions ATTACHMENT 3 Applicable Documents ATTACHMENT 4 CDRL List ATTACHMENT 5 Instructions for Processing Aircraft at Contractor Facility

1 SECTION I – DESCRIPTION OF SERVICES/GENERAL INFORMATION

This Performance Work Statement (PWS) describes the Engineering Support Services (ESS) to be provided by the Aircraft Original Equipment Manufacturer (OEM) to the Air Force T-1A (Beechcraft 400) program.

The requirements of this PWS are applicable to the T-1A aircraft systems, as specified in each paragraph below. Engineering support required is divided into recurring and non-recurring activities. Engineering support includes but is not limited to: study and analysis of aircraft deficiencies; design, development, testing, and supplemental Federal Aviation Administration (FAA) or military certification of engineering changes necessary to correct such component deficiencies/obsolescence or to introduce product enhancements; and incorporation of resulting engineering changes into the aircraft via retrofit; configuration and data management, and source data to support technical manual updates. This PWS also includes Contractor field team activities and aircraft crash damage repair.

1.1 Contractor Responsibility

The Contractor is responsible for the content and work direction as stated in this PWS.

NOTE: Procuring Contracting Officer’s (PCO) Authority. The PCO is the only person authorized to approve changes to any of the requirements under this PWS and any provisions contained elsewhere in this contract. In the event the Contractor implements any such change at the direction of any person other than the PCO, the change will be considered to have been made without authority. All references to “day(s)” refer to working day(s).

1.2 Definitions

The Contractor shall find definitions in Attachment 2 to this PWS.

1.3 Platform Description

This PWS defines services required for Engineering Services (ES) support of the Air Education and Training Command (AETC) fleet of 178 T-1A trainer aircraft. ES support requirements include Program Management, Sustaining Engineering, Non-Recurring Sustaining Engineering, Configuration Management and Technical Publications.

The T-1A Jayhawk is a commercial derivative of the Beechcraft 400 aircraft manufactured by the Contractor with a FAA Type Certificate. The aircraft is a medium-range, twin-engine jet used to train student pilots to fly airlift and tanker aircraft. The instructors at the schoolhouse at NAS Pensacola provide Intermediate Navigator and Naval Flight Officer training, and airmanship orientation to navigators selected for airlift or tanker aircraft and Pilot Instructor Training.

The T-1A Main Operating Bases are:

a) Randolph AFB, TX

b) Laughlin AFB, TX

c) Vance AFB, OK

d) Columbus AFB, MS

e) NAS Pensacola, FL

1.4 Program Requirements

The Contractor shall accomplish both "Recurring" and "Non-Recurring" services in support of the task requirements. The "Recurring" service will involve continuous Contractor action and will not require additional contractual authorization or tasks for accomplishment, except as required in Section 1.9. The "Non-Recurring" services will be accomplished only upon specific requests of the contracting officer and issued as Engineering Assignments (EAs) against the contract.

1.4.1 Mission Essential Services

Not applicable to this requirement.

1.5 Program Management

1.5.1 Program Management

The Contractor shall provide centralized Program Management, which shall include Program and Financial capabilities responsible for management of resources, performance, monitoring program status, and ensuring compliance with contract deliverables. The Contractor shall manage performance, risks, subcontracts, suppliers, and data required and shall use existing management systems to the maximum extent possible.

The Contractor shall establish efficient working relations with other T-1A contractors for information exchange, resolution of system problems, and implementation of system changes and shall establish appropriate Associate Contractor Agreements as necessary. The Contractor shall continuously perform process improvement activities, as appropriate, in conjunction with all T-1A training system participants.

The Contractor shall establish and maintain data management policies, procedures, and controls to ensure quality preparation, timely delivery, and tracking of the data requirements. The Contractor shall establish a focal point by Full Scale Performance (FSP) for integrating the data management efforts. All interfaces shall be established through this focal point.

The Contractor shall establish a focal point by FSP to provide communication, information, and dissemination of technical and related data in support of the T-1A Contractor Operated and Maintained Base Supplier (COMBS) field service representatives (FSRs), main operating base (MOB) Maintenance Contractors, and the using agencies’ representatives as necessary to provide field and student undergraduate pilot training operational support. The Contractor shall not initiate any communication with the operational and maintenance organizations. The Contractor shall inform the USAF Program Management Office (PMO) of all communication with the operational and maintenance organizations. The PMO is the focal point for any and all communication downward with the operational and maintenance organizations.

1.5.2 Obsolescence

The Contractor shall coordinate with their Commercial Engineering Support Services department to identify and notify the Government of any potential part obsolescence.

1.5.3 COMBS Support

The Contractor shall, upon direction of the Government, monitor T-1A spares backorders and assist the COMBS contractor in delivery of parts to the COMBS contractor.

1.5.4 Meeting Support

The Contractor shall support required meetings and teleconferences to discuss program status, review requirements compliance and resolve open issues.

The Contractor shall provide engineering support for meetings directed by the Government. The Contractor shall charge engineering hours for meeting support directed by the Government to recurring engineering efforts. The Contractor shall charge engineering hours for all other meetings that are task specific to that specific task/ work order (i.e. EI, ET, EP or EA).

1.5.4.1 Weekly Status Report

The Contractor shall support telecoms every two weeks and provide a weekly status report of all sustaining engineering efforts. The status report shall be in Contractor format, to include for each task the information noted below:

a) Title of task

b) Date task was assigned

c) Estimated completion date

d) Applicable project tracking numbers

e) Actions completed during last week (cumulative)

f) Project issues or concerns and status

g) Project elements on hold for input to the Contractor

In order to close out task assignments, the Contractor shall submit final closure requests to the Program Engineer. The request shall be sent electronically or during status update meeting(s) and include justification for closure.

Deliverable: A002, Weekly Status Report, DI-MISC-80508B/T

1.5.4.2 Program Management Review, System Safety Group &

System Supportability Review

The Contractor shall support an annual PMR, an annual System Safety Group (SSG) and a System Supportability Review (SSR), where the Contractor shall act as a technical advisor to each meeting. The Government and Contractor shall mutually agree upon agenda items prior to the PMR. The Contractor shall prepare and provide a proposed PMR agenda and presentation materials as requested by the Government prior to the meeting. The Contractor shall provide meeting minutes, including action items, related to the Contractor’s presentation. The meeting minutes shall be coordinated with Program Manager (PM) and Program Engineer within 10 working days after the specific meeting prior to final delivery.

Deliverable: A003, Conference Minutes, DI-ADMN-81250A/T

1.5.4.3 Configuration Control Board

The Contractor shall support all T-1A configuration control boards (CCB), as required by the Government. The Contractor shall act as a technical advisor at the CCB.

1.5.5 Cost and Schedule Reporting Requirements

The Contractor shall provide a monthly Cost Status Report. The Contractor shall provide a monthly update to the Integrated Master Schedule.

Deliverable: A004, Performance and Cost Report, DI-FNCL-80912/T Deliverable: A005, Integrated Master Schedule, DI-MGMT-81861/T

1.5.6 PCO Letters & ROM Preparation

The Contractor shall prepare and submit responses to PCO Letters (PCOL) and develop & submit Rough Order of Magnitude (ROM) estimates when required by the Government. Response shall be within the negotiated timeframe agreed to by the PCO/PMO and the Contractor. The Contractor shall also provide estimates in support of decision making and the planning, prioritization, identification and capture of funding for future efforts.

1.5.7 Technical Order Library

The Contractor shall maintain a current library of T-1A Technical Orders (TOs) for internal use in performing requirements of the PWS. This library may be electronic.

TOs are available format via Enhanced Technical Information Management System (ETIMS). The Contractor shall request and obtain an account with the PMO.

1.5.8 Service Information and FAA Directive Review

The Contractor shall review and provide publications pertaining to FAA compliance, Operational Safety, Suitability and Effectiveness (OSS&E) and system/component OEM information or suggested actions, within 30 days of receipt. The Contractor review shall include the following:

a) Airframe and Engine Service Bulletins (SBs).

b) Airframe and Engine Service Letter (SLs).

c) Structural Item Interim Advisories.

d) FAA Notices of Proposed Rule Making (NPRM) - New and Revised.

e) Airworthiness Directives (ADs).

f) Any other new or revised FAA final rules.

g) SBs and SLs from vendors of onboard components/black boxes specifically identified by the Government. The Contractor shall review such literature as though it were an OEM SL or SB.

Deliverable: A010, Airworthiness Directives / Service Bulletins / Advisory Data, DI-

MISC-81241/T

1.5.8.1 Evaluation Content

The Contractor shall review service literature and notify the PMO if applicable to the T- 1A or Hawker 400T. For each service document which the Contractor recommends Government action be taken, the Contractor shall provide the following information within 30 days:

a) A summary of the activity discussed within the service publication and a brief description of the changes made by any revision. Include Contractor's recommendation and specific justification for benefits gained by incorporation considering the uniqueness of the Air Force mission, maintenance concepts and unique configurations.

b) ADs/SBs associated with the subject service publication.

c) Service publication effectivity by tail number/core engine, referencing group number effectivity based on configuration. Also identify if spares are affected.

d) Status of incorporation of previous revisions on each aircraft, engine or related spares (status will be determined and tracked from the best available data as provided by the Government).

e) If earlier version of the service publication has been completed, identify any additional work requirements necessary.

f) Identification of service publications subject to aircraft uniqueness issues.

g) All affected TOs, Time Compliance Technical Orders (TCTOs), Manuals, Minimum Equipment List, or Minimum Essential Systems List.

h) Identification of the applicable Aircraft Structural Integrity Program (ASIP) control point in support of the Individual Aircraft Tracking Program (IATP).

The Contractor shall notify the Government in the event that a lack of data precludes publication evaluation and recommend an appropriate method (i.e. inspection, documentation review, etc.) for determining resolution.

1.5.8.2 Urgent FAA Airworthiness Directives (AD)

The Contractor shall provide copies and brief comments of any applicable Model 400 AD or any new or revised FAA Final Rules that require operator compliance within 12 months to the Program Engineer within 48 hours of receipt.

The Contractor shall monitor the issuance of ADs, including emergency ADs and immediately adopted rule ADs. If, upon review, the AD appears to affect and require action on the T-1A within 7 calendar days, the Contractor shall immediately notify the Program Engineer. If the Program Engineer cannot be contacted, the Contractor shall attempt to contact the applicable Program Manager, Engineering Section Chief, Branch Chief, or Chief Engineer in that order until contact is made.

1.5.9 Operational Safety, Suitability & Effectiveness

The Contractor shall, support the Government in the development, maintenance and execution of the OSS&E program in all Contractor activities supporting recurring and non-recurring engineering work provided as part of this PWS, and as requested by Program Engineer via an EI.

The Contractor shall provide a single engineering focal point by FSP for resolution of Government inquiries or concerns about technical aspects of T-1A programs.

1.5.9.1 Systems Engineering Approach

The Contractor shall include a disciplined engineering approach that ensures full spectrum integration and systems engineering principles are applied when performing all non-recurring and recurring tasks in this PWS.

1.5.9.2 FAA Certification

The Contractor shall provide ongoing support for maintaining the certification basis and records of the aircraft and engines to include certification review of new changes and in-service incidents, support of the continuing airworthiness of the existing configurations, maintenance and retrieval of certification records, development of certification processes and continued coordination with FAA certification authorities. Contractor shall provide personnel and infrastructure as is required to fulfill these requirements.

1.5.9.2.1 FAA Records

The Contractor shall track and maintain FAA certification data and records by tail number or individual aircraft from the best available data as previously generated under contract or provided by the Government.

1.5.10 Commercial Manuals

The Contractor shall provide updates upon receipt to the following Commercial Manuals:

1) 2 copies of Beechcraft Corporation Interactive Maintenance Library Beechjet Model 400/400A, Model 400XP, and Model 400A/400

2) 2 copies of Beechcraft Commercial Flight Manual P/N 128-590001-167 Deliverable: A014, Commercial Manuals/Contractor Format

1.5.11 Engineering Data

The Contractor shall use its own standard practices to ensure that new drawings prepared under this contract are of production quality, unless otherwise specified by the Program Engineer.

1.5.12 Data Rights

The Contractor shall afford unlimited rights to the Government for new drawings or documents prepared under this contract. The Contractor shall notify the PCO upon identification of a yet-to-be developed drawing or document that will contain proprietary data if such a drawing or document is derived from an existing drawing/document which is proprietary to the preparing activity. This notification is in accordance with DFARS 252.227-7013(e)(3). Validation of technical data markings shall be in accordance with DFARS 252.227-7037, Validation of Restrictive Markings on Technical Data. The Contractor shall seek further direction and approval from the PCO to proceed on the engineering assignment when granting unlimited rights is not feasible.

1.5.13 Security

The Contractor shall comply with the security requirements listed in DoD Series Regulations and the appropriate Security Classification Guide(s).

1.5.14 Contractor Requirements for DoD Common Access Card

If contractor employees must obtain/hold a Common Access Card (CAC) to in performance of contract requirements, the following are required:

1) The contractor must perform background checks on employees requiring a CAC, using local law enforcement. This will become part of the application for a CAC.

2) Employees requiring a CAC will be screened by 72 SFS before they are issued Tinker AFB access badges.

3) Contractor personnel will be escorted by USAF personnel while on Tinker AFB except where specific work areas have been identified to the Contractor by the PCO.

4) Contractor will maintain and provide roster for both personnel and vehicles. Names of personnel and vehicles (description, vehicle number, tag/license number) must be verified by the company and should receive a background screening check. Define process for replacement of workers. Substitute personnel and vehicles must receive the same vetting process before obtaining access to the installation.

5) 72 SFS Anti-terrorism Officer will provide Anti-Terrorism Level 1 training if requested by the contactor ; and 72 SFS personnel will provide procedures for contractor personnel to report suspicious activity and stolen equipment.

Note - if CAC is obtained from a USAF Base other than Tinker AFB, contact that base Security Forces Squadron to determine the details of their CAC approval process. It will likely be very similar.

1.5.15 Contractor Authorization to be Passenger on T-1A

Contractor representatives are authorized to be a passenger on the aircraft when the local Commander determines the need for on-board capability. This provision applies primarily to missions involving travel to remote areas away from the home base, or the demonstration of in-flight malfunctions that cannot be demonstrated on the ground.

Unusual circumstances may dictate that the local Commander approve that the Contractor Technical representatives be a passenger on the aircraft for other reasons.

When applicable regulations or directives require that orders (or other formal documentation) be issued to implement this clause of the contract. The local commander is responsible to provide the required orders or other documentation.

1.6 Recurring Engineering

The Contractor shall respond to Engineering Inquiry (EI), Engineering Task (ET) and Engineering Project (EP) direction.

Engineering Inquiry (EI) An EI is defined as a Government initiated request by the Program Engineer regarding daily technical aspects of the program. These inquiries are expected not to exceed 16 hours and do not require an approved authorization form. Upon the recognition that a specific request will exceed the 16 hour EI limit, the Contractor shall submit appropriate form and receive Government authorization prior to performing work beyond the 16 hour threshold.

Engineering Task (ET):

ETs are intended to be limited efforts not exceeding 40 hours. ETs are generated and approved by Program Engineer and are initiated directly with the Contractor Engineering. The Contractor shall include total cost estimate to include labor, material, and travel requirement estimates as well as a work description, ET deliverable description, and estimated completion date on the ET authorization form. The Program Engineer will provide authorized ET form to the Contractor Program Manager, the Contractor Project Engineer and the Contractor Contract Manager. Any effort for coordination and/or development of the ET authorization form shall be coordinated with the Contractor Project Engineer. The Contractor shall track individual ET labor hours and costs and shall notify Program Engineer if the ET is expected to exceed 40 hours or approved cost estimates. The Contractor shall obtain PCO approval prior to performing work beyond the 40 hour threshold or exceeding approved cost estimates.

Engineering Project (EP):

EPs are intended to be limited efforts not exceeding 160 hours. EPs are initiated by a Program Engineer but are approved by the PCO. The Program Engineer will submit a written request for the engineering requirement to the Contractor. Upon receipt of the requirement, the Contractor shall submit an EP authorization form for PCO authorization for engineering actions expected to require between 40 and 160 hours. The Contractor shall include total cost estimate to include labor, material, and travel requirement estimates as well as a work description, EP deliverable description, and estimated completion date on the EP authorization form.

The Contractor shall track each individual EP by estimated or actual completion and report actual labor hours and actual cost in accordance with CDRL A004.

Deliverable: A004, Performance and Cost Report, DI-FNCL-80912/T

1.6.1 Recurring Engineering Sustainment

The Contractor shall provide support of the T-1A Type Certificated aircraft through responses to EI, ET, or EP concerns regarding, but not limited to, aircraft design, performance, FAA certification, maintenance workload, cost reduction, reliability and safety. The Contractor shall, when authorized by the PCO, dispatch engineering and other support personnel to field locations if required. The Contractor shall provide an engineering focal point by FSP for all concerns in regards to technical aspects of the Program. All interfaces shall be established through this focal point.

Deliverable: A006, Contract Change Proposals (CCPs), DI-ADMN-81401B/T

The Contractor is authorized to provide estimates in response to requests received from the PCO and/or persons designated by the PCO. The Contractor shall prepare and provide the Program Engineer and PCO, a work statement that describes the activity to be performed, the period of performance, labor, travel, material cost estimate and if applicable an assessment of the adequacy of funding to perform the work specified based on the estimated cost.

1.6.2 Configuration Management

The Contractor shall maintain configuration management of the T-1A Type Certificated design and associated engineering technical data utilizing FAA procedures and MIL- HDBK-61A scope of intent.

a) The Contractor shall exercise their role as identified in Table 1-1as well as management control over the manufacturing and quality of all the Contractor installed items on the T-1A aircraft. The engineering release records of Government approved Contractor items shall reflect the Contractor's FAA approved internal system of control to ensure that all approved Class I and II changes have been incorporated and that supporting documentation is updated and maintained current.

Applies to Development of New Systems and to Modifications of Existing Systems GOVERNMENT The Contractor PERFORMING ACTIVITIES

Solicits concept (System Engineering) studies.

Specifies desired performance attributes for a system.

Selects Contractor or approves engineering change proposal or modification request.

Approves performance configuration specifications.

Monitors Contractor CM process via:

IPT participation Metrics Performance reviews

Baselines selected product performance configuration documentation after verifying that performance requirements have been achieved.

May become CDCA for other documentation as contractually established.

Baselines product (design) configuration documentation after verifying that the design documentation matches the delivered configuration

Configuration control authority for the USAF T-1A aircraft

Performs system engineering studies.

Determines alternative system approaches.

Proposes Items or Design Solutions.

Prepares and submits performance specifications for approval. Participates with Government on IPTs.

Initiates development. Incrementally baselines design solution and acts as Current Document Control Authority (CDCA) for released (meaning upon approval of the Government) configuration documentation, e.g. performance and detail specifications, engineering drawings, engineering models, etc. for which another Government activity or commercial organization is not already the CDCA.

Baselines product (design) configuration documentation after verifying performance attributes and consistency between item and configuration documentation.

The Contractor continues as CDCA for the T-1A type certificated baseline.

Table 1-1

b) The Contractor shall demonstrate supporting documentation verifying that all software/firmware related to their engineering services tasking subject to FAA requirements of the certification process has received approval from the FAA for the intended application of the T-1A program.

1.6.2.1 Configuration Identification

The Contractor shall manage the T-1A aircraft system baselines in accordance with FAA and USAF requirements listed below by maintaining current configuration identification documentation.

a) The Engineering Specification for Model 400A, BS 24354 Rev C dated 10 December 1998, combined with the Addendum Specification (Part 1 and Part II), BS 24525 Rev 15 dated 21 Oct 2011, define the production T-1A Jayhawk (400T). The Contractor shall maintain the Part I and Part II Addendum Specification in accordance with the Contractor's engineering release system.

The specification shall be subject to Government approval if updates are required.

b) The Contractor shall maintain the Air Vehicle Prime Item Development Specification (PIDS) PS 3962, Rev F dated 1 October 1998 in accordance with The Contractor's engineering release system. The specification shall be subject to Government approval if updates are required.

Deliverable: A007, System/Subsystem Specification (SSS), DI-IPSC- 81431A/T

1.6.2.2 Configuration Change Control

a) The Contractor shall electronically generate Class 1 Engineering Change

Proposals (ECPs) for the T-1A Training System, as required, using MIL-HDBK- 61A as a guide. All Class I changes shall be submitted to USAF for approval.

The Contractor shall act as integrator for the T-1A Training System on ECPs generated by the Contractor and ensuring ECPs that are generated by the Contractor are properly implemented.

Deliverable: A008, Engineering Change Proposal (ECP) / Notice of Revision

(NOR), DI-CMAN-80639C & DI-CMAN-80642C

b) The Contractor shall electronically generate Contract Change Proposals (CCPs) as required.

Deliverable: A006, Contract Change Proposals (CCPs), DI-ADMIN-81401B/T

c) The Contractor shall provide early notification of Class 2 changes that affect TOs or spares. The Government will review these Class 2 changes for concurrence in classification.

d) The Contractor shall submit changes to affected T-1A technical documents resulting from an approved ECP.

(NOR), DI-CMAN-80639C & DI-CMAN-80642C

1.6.3 In-Flight Emergency (IFE) Support and Crisis Management Team (CMT) Support

The Contractor shall provide a focal point by FSP to the PCO to coordinate requests for in-flight emergency assistance from 8 am to 5 pm CST on working days. The United States Government (USG) and the Contractor recognize that focal points will not have access to technical data and computers after normal business hours. Focal points shall include T-1A Product Support Engineering. The Contractor shall ensure the instructions for obtaining support for in-flight emergencies are current at all times and disseminated to the appropriate Government organization as directed. For IFE support provided during normal business hours, the Contractor shall immediately provide email notification and summary of IFE to the Program Engineer. For IFE support provided outside of normal business hours, the Contractor shall provide notification and summary of IFE to the Program Engineer NLT 8:30AM Central Time the next business day.

The Contractor shall participate in Crisis Management Team (CMT) telecoms or meetings. The Contractor shall ensure CMT reference documents are kept current.

The Contractor shall regard participation in CMT as its highest systems engineering support priority. In the event of conflict, other systems engineering support requests shall be worked in order of priority provided by the Government.

1.6.4 Mishap Investigation and Recovery Support

The Contractor shall provide on-site mishap investigation and recovery support as directed by the PCO. The process of providing this support will be jointly coordinated if time permits. The Contractor shall provide upon request the most knowledgeable Engineering representative possible based on the situation. The Contractor shall provide immediate access to any supporting documentation required. The Contractor shall provide support for T-1A mishap investigations using AFI 91-204 as a guide.

The Contractor shall notify the procuring Safety Office or a designated Government Representative (GR) within one (1) hour of all mishaps or incidents. A written report of the mishap/incident shall be sent within three calendar days to the GR, who will forward it to the Procuring Safety Office. For information not available at the time of initial written report, the Contractor shall provide the remaining information via interim reports every 3 business days until the investigation report is complete, unless extended by the Government Safety Office.

Deliverable: A009, Mishap Investigation Report, DI-MISC-80508B/T

1.6.5 Maintenance Program Support

As directed by the PCO, the Contractor shall develop and propose changes to the Scheduled Inspection and Maintenance Requirements Manual (-6 TO), as applicable based on ADs, SBs, SLs, and agreed-to changes resulting from engineering analysis or study. The Contractor shall propose maintenance program changes based on updates to the operational profile, safety-related issues or mission critical failures experienced by Government and specific Government requests as information is provided by the Government. The Contractor shall review available maintenance data, support maintenance review meetings and provide recommendations for changes to aircraft maintenance programs.

1.6.6 Data Accession List

The Contractor shall provide an annual update to the data accession list (DAL).

Information shall be made available to the Government through a secure electronic database (using Commercial-Off-the-Shelf industry standard Microsoft Windows compatible software) containing DAL items and making online access available to designated Government personnel. Government personnel shall be granted access to secure electronic database (e.g. SharePoint) by the Contractor. It is understood the Contractor's method of granting access requires verification of US Citizenship. The recommended method for obtaining this verification is for the USAF to submit a visit request to the Contractor using the Joint Personnel Adjudication System (JPAS).

Deliverable: A011, Data Accession List (DAL), DI-MGMT-81453A/T

1.6.7 Environmental Support

The Contractor shall coordinate and monitor responses to Government inquiries about environmental management.

The Contractor shall support the Government on environmental issues/concerns and provide recommendations as required per EI, ET, EP, or EA. The Contractor shall be familiar with federal (Environmental Protection Agency (EPA), Occupational Safety and Health Administration (OSHA), Department of Defense (DoD), etc), state and local existing environmental laws and regulations that may impact the aircraft systems.

The Contractor shall review recurring engineering efforts and identify environmental issues/concerns to the Program Engineer and provide recommendations. The Contractor shall support pro-active planning to ensure environmental issues/concerns are addressed.

1.6.8 Safety

The Contractor shall coordinate and monitor responses to Government inquiries about system safety management.

The Contractor shall maintain report 400E220.

The Contractor’s System Safety/Environmental Management Program Plan will be available to the Program Office upon request.

The Contractor shall review recurring efforts for safety issues. The Contractor shall develop a mishap risk assessment for all SSG open items IAW MIL-STD-882E and the applicable System Safety/Environmental Management Program Plan. The Contractor shall attend designated System Safety Working Group (SSWG) and/or SSG meetings at the request of the Government. The Contractor shall support pro-active planning to ensure safety issues are addressed.

1.6.8.1 Safety Inquiries

The Contractor shall investigate, analyze, and report to the Government on any situation that may affect ground and flight safety of the aircraft and/or associated aircraft personnel, when requested by the Program Engineer via an EI or ET. The Contractor shall provide, within 24 hours of a safety inquiry, an initial response, including a Preliminary Hazard Analysis and an initial Hazard Risk Index (HRI) per MIL-STD 882E, to the Program Engineer. The Contractor shall provide with the initial response a schedule and estimated effort for completing analysis of the situation, including completion of the hazard analysis, determination of a final HRI, and development of a technical/risk management recommendation. Upon initial notification of the evaluation by the Contractor, the Government will determine if additional action is required and will notify the Contractor for further action. If, at any time during evaluation of the Safety Inquiry, the Contractor determines a safety of flight issue exists, the Contractor shall notify the Government immediately by the most expeditious method.

1.6.9 Reliability and Maintainability Support

The Contractor shall coordinate and monitor responses to Government inquiries or concerns about reliability and maintainability. The Contractor shall provide technical expertise to support USAF reliability and maintainability investigations.

1.6.10 Technical Order Support

1.6.10.1 Commercial Manuals (not used by Air Force personnel to perform maintenance) The Contractor shall monitor the Contractor approved system commercial data and provide a listing (annually) to the Government of those changes made to the commercial maintenance manuals that the Contractor has determined to be applicable to the T-1A technical orders.

Deliverable: A017, Technical Report – Study Services, DI-MISC-80508B/T

1.6.10.2 AFTO Form 22 and AF Form 847 Evaluations

The Contractor shall, at the direction of the PCO, analyze and evaluate Technical Manual (TM) Change Recommendation and Reply (AFTO 22s) and Recommendation for Change of Publication (AF Form 847s) and provide recommendations at the of the Program Office. The Contractor shall provide periodic status of the reviews in-progress at an interval specified by the Program Office.

1.6.10.3 Changes Resulting from Service Documents or

Deficiency Reports

As directed by the PCO, the Contractor shall develop and deliver data that can be utilized to update TOs to be in compliance with type certificate, design, modification and procedural changes as required by the terms of the service document, or to implement corrective action when appropriate for resolution of a deficiency report.

1.6.11 Systems Engineering Management Plan

As directed by the PCO, the Contractor shall develop, maintain and update the Contractor’s Systems Engineering Management Plan (SEMP) and provide a copy to the Program Engineer. The Contractor shall provide for technical planning, integrate Government and Contractor practices and processes and conduct continuous process improvement consistent with corporate improvements and program needs. The SEMP shall include a description of the key technical and technical management processes.

The Contractor shall establish, in the SEMP, a set of metrics and measurements (the baseline) that will be used to monitor Contractor performance, including guidelines/standards for applicability. At a minimum, the SEMP shall address the metrics defined in the Program Office Systems Engineering Plan (SEP). The SEMP shall include a matrix that correlates the Program Office SEP with the Contractor’s SEMP. In addition, the Contractor SEMP shall encompass:

a) Affordability and cost effectiveness.

b) Requirements analysis and management.

c) Functional analysis and allocation.

d) Integrated planning and scheduling.

e) Risk management / Risk mitigation (Use DAU Risk Management Guide as a guide) (upon direction of the PCO, provide a copy to the Program Engineer) Deliverable: A012, Contractor's Risk Management Plan, DI-MGMT-81808/T

f) Technical Performance Measures (TPM).

g) Interface control.

h) Baseline management.

i) Configuration Management.

j) Technology insertion.

k) System validation and verification.

Deliverable: A013, System Engineering Management Plan (SEMP), DI-MGMT- 81024/T

1.7 Recurring Engineering Maintenance/Technical Assistance

Requests (-107 Requests)

The Contractor shall provide engineering support to resolve -107 requests as directed by the Program Engineer, using TO 00-25-107 as a guide. For -107 requests that cannot be resolved within five business days after receipt, the Contractor shall provide a plan to resolve -107s within two additional business days after receipt.

NOTE: The PCO and/or the Program Engineer will grant adjustments to the estimated completion date if it is shown Government inaction specific to an -107 request caused an unreasonable delay in the Contractor’s performance of that task. The adjustment will be limited to total time of Government caused delay as determined by the PCO and/or Program Engineer.

1.8 Recurring Engineering – Deficiency Reporting

The Contractor shall conduct Deficiency Reporting (DR) investigations and materiel teardown analyses in accordance with TO 00-35D-54. Category I DR investigations shall take priority over all other DR investigations. All other DR investigations shall be worked in order of priority provided by the Government. Initial reports for DR investigations in support of safety investigations (to be designated “Mishap and High Accident Potential (MHAP)”) shall include teardown information and repair cost data.

Teardown reports shall include, but are not limited to, visual anomalies, non-destructive inspection results, uncharacteristic component performance, benchmark tests, and possible root cause(s), as appropriate. The Contractor shall coordinate DR investigations with applicable organizations, including the Government, vendors, subcontractors, and the COMBS Contractor. Extension of CDRL reporting timelines may be granted by the Government on a case-by-case basis upon written request by the Contractor. The final reply shall address the cause of the reported condition, and corrective action necessary, which may be accomplished by the Contractor, including preventive action to preclude recurrence.

Deliverable: A015, Deficiency Report, DI-MGMT-80258A/T

1.9 Non-Recurring Engineering

The Contractor shall perform non-recurring engineering in support of the T-1A Type- Certificated aircraft as authorized by the PCO via an EA. EAs will be authorized by separate bilateral contract modification with a PWS to include a definition of task completion, due date and total ceiling price. In all cases, any effort expected to exceed 160 labor hours, shall be accomplished as an EA, which must be approved by the PCO via a modification to the contract. Furthermore, the Program Office will insure that each EA PWS contains a delivery date, the estimated man-hours for the task, and a list of deliverables as applicable, along with the date of delivery for those deliverables. An EA must contain that information before the requirement will be processed. The Contractor shall include a disciplined engineering approach that ensures full spectrum integration and systems engineering principles are applied when performing all non-recurring and recurring tasks in this PWS. The Contractor shall provide for technical planning, integrate Government and Contractor practices and processes and conduct continuous process improvement consistent with corporate improvements and program needs.

1.9.1 Reporting Requirements

For each task authorized by contract modification, the Contractor shall provide a monthly status report until the effort is completed. At the conclusion of each task authorized by contract modification, the Contractor shall provide a technical report describing the analysis, results, and recommendations as required by the effort.

Deliverable: A016, Contractor's Progress, Status, and Management Report, DI-

MGMT-80227/T

Deliverable: A017, Technical Report - Study Services, DI-MISC-80508B/T

1.9.2 EA Contractor Acceptance and Contractual Changes

The Contractor shall start work on an EA upon receipt of the contract modification authorizing the EA. The Contractor shall immediately notify the PCO, if upon receipt of an EA or at any time thereafter, the Contractor concludes the EA cannot be completed within the total ceiling price or by the authorized due date.

The Contractor may recommend changes to an EA with cost/schedule impacts (if any) identified. The Contractor shall coordinate any such proposed changes through the PCO and also identify the changes to the PM and Program Engineer. If the Program Engineer concurs with the proposed technical changes, the Program Engineer will forward the changes to the PCO recommending incorporation. However, the Contractor shall not perform to the proposed revised EA until the changes have been authorized by the PCO by a contract modification.

1.9.3 EA Performance

EAs shall be governed by the same requirements as stated within this PWS, any exceptions or deviations shall be stated within the EA. The Contractor shall submit deliverables as specified in each EA.

1.9.4 EA Reporting

The Contractor shall report the status of each active EA in the Weekly Status report.

1.9.5 Notification of EA Expenditures

For other than Firm Fixed Price (FFP) EAs, the Contractor shall provide written notice to the PCO (copy to the Program Engineer and Engineering Services Support (ESS) PM), if expenditures are expected to exceed 85% of the total ceiling price on the EA within the next thirty (30) days. The Contractor shall notify the PCO when it is determined that the actual expenditures on an EA will be substantially less than the ceiling price. An estimate of final expenditures shall be provided within 120 days after PCO concurrence of closure.

1.9.6 Data Rights for EA Assignments

The Contractor shall afford unlimited rights to the Government for new drawings or documents prepared under this contract. The Contractor shall notify the PCO upon identification of a yet-to-be developed drawing or document that will contain proprietary data if such a drawing or document is derived from an existing drawing/document which is proprietary to the preparing activity. In accordance with DFARS 252.227-7013(e) (3), the Contractor shall identify data that will be provided with restrictions to use, release or disclosure. Validation of technical data markings shall be in accordance with DFARS 252.227-7037, Validation of Restrictive Markings on Technical Data. The Contractor shall seek further direction and approval from the PCO to proceed on the engineering assignment when granting unlimited rights is not feasible.

1.9.7 EA Completion/Closure

The Contractor shall provide written notification to the PCO when an EA has been completed and the effort is closed. The notification should include/reference documentation evidencing completion. The PCO will provide written concurrence that all activities have been satisfactorily completed or specific identification of areas of nonconformance. The Contractor shall not continue to perform past the EA due date or expend any amount in excess of the EA ceiling price without PCO approval. Formal closure will be evidenced by DD250 acceptance.

Note: DD250s will be completed via WAWF IAW DFARS 252.232-7003.

1.9.8 Scope of EA Activities

The Contractor shall be prepared to perform non-recurring engineering/data services similar to, but not limited by, the tasks listed below (from 1.9.9 to 1.9.12) when authorized by the PCO through an EA.

1.9.9 Engineering Studies

The Contractor shall conduct engineering studies to determine system definition and modification requirements for enhancements to airframe or mission systems as directed by the PCO. The Contractor shall coordinate with the Program Engineer and the

Government Aircraft operator/maintainer to develop enhancements that satisfy Government requirements and capabilities, or resolve performance issues as directed by the PCO.

1.9.10 Data Accession List Data Base

The Contractor shall maintain a secure electronic database (using Commercial-Off-the- Shelf industry standard Microsoft Windows compatible software) containing DAL items and making online access available to designated Government personnel. Government personnel shall be granted access to secure electronic database with no more than a PCO letter (PCO will verify Common Access Card (CAC) and state issued identification of individual provided with access). The Contractor shall update the file index as required. The Contractor shall provide the updated file index semi-annually in the DAL.

The DAL shall include, but not be limited to, final versions of: released engineering drawings; modification specifications; test procedures; test reports; vendor manuals;

engine records; historical maintenance records; DAL file index; and FAA records. The Contractor shall flow this requirement down to major subcontractors and include Subcontractor data on the Data Accession List. The Contractor shall establish back-up and recovery processes that assure the DAL database will not experience catastrophic loss.

Deliverable: A011, Data Accession List (DAL), DI-MGMT-81453A/T

1.9.11 Safety and Environmental Management

The Contractor shall update report 400E220 (T-1A), which shall be documented in a System Safety/Environmental Management Program Plan with responsibility for oversight and review of engineering development activities. The Contractor’s system safety engineering risk analysis results shall be reported IAW MIL-STD 882E.

The Contractor shall be familiar with federal (EPA, OSHA, DoD, etc.) state and local environmental laws and regulations that may impact the aircraft systems.

The Contractor shall respond to Program Engineer environmental inquiries and review applicable Government data provided from other Contractors and identify environmental issues/concerns to the Program Engineer. The Contractor shall review each non-recurring engineering effort and identify environmental issues/concerns to the Program Engineer.

The Contractor shall support designated Environmental Working Group (EWG) meetings, conferences and workshops upon specific request of the Program Engineer.

The Contractor shall support proactive planning to ensure environmental issues/concerns are addressed.

1.9.12 System Augmentation

1.9.12.1 Aircraft Prototype Modifications

The Contractor shall perform any and all phases (i.e. site surveys, engineering design, technical data development, source data preparation, fabrication, kit procurement, installation, test, certification, and delivery) necessary to complete the prototype modifications…