KC10_KDC10_ESS_PWS_Rev8_pdf.pdf

PERFORMANCE WORK STATEMENT

FOR

KC-10A AND KDC-10 ENGINEERING

SUSTAINMENT SUPPORT (ESS)

1 October 2016 – 30 June 2020

7 December 2015

Prepared by

AFLCMC/WKDBB

3001 Staff Dr. Suite 2AC489D

TINKER AFB, OK 73145

i

Table of Contents

SECTION 1 – DESCRIPTION OF SERVICES

1.0 INTRODUCTION

1.1 Scope

1.2 Applicability

1.3 Period of Performance

2.0 ENGINEERING SUSTAINMENT SUPPORT REQUIREMENTS

2.1 Program Requirements

2.1.1 Program Location

2.1.2 Days

2.1.3 Program Engineers and Lead Equipment Specialist

2.1.4 Program Documentation

2.2 Engineering Assignments

2.2.1 Definition

2.2.2 EA Funding Types

2.2.3 EA Proposal Submittals

3.0 Recurring Engineering/Data Services

3.1 Firm Fixed Price (FFP) Tasks

3.1.1 Single Point of Contact

3.1.2 In-Flight Emergency Support

3.1.3 Systems Engineering

3.1.3.1 Specialty Engineering Disciplines

3.1.3.2 Systems Engineering Management Plan (SEMP

3.1.4 Service Information and FAA Directive Review (KC-10A)

3.1.4.1 Evaluation Content (KC-10A)

3.1.4.2 Applicable Inspection/Modification Accomplishment

3.1.5 Dispatch Deviation Guide and FAA Minimum Equipment List

3.1.6 Aircraft Airworthiness Management (KC-10A)

3.1.6.1 FAA Airworthiness Activity Requirements

3.1.6.2 Service Information Configuration Document (SICD)

3.1.7 Contractor Manpower Reporting

ii

3.1.8 Government Industry Data Exchange Program (GIDEP) Review (KC-10A)

3.1.9 Electronic Data and Correspondence Exchange

3.1.9.1 Electronic Media

3.1.9.2 Hardware/Software Support

3.1.9.3 MyBoeingFleet.com Data

3.1.9.3.1 Administration of Access

3.1.9.4 Data Accession List (DAL)

3.1.10 Status Reports

3.1.11 Contractor Supplied Publications

3.2 Cost Plus Fixed Fee (CPFF) Tasks

3.2.1 Emergency, Urgent and Short Compliance FAA Airworthiness Directives

3.2.2 Response to Technical Inquiries (RTIs)

3.2.2.1 RTI Authorization

3.2.2.2 RTI Reporting

3.2.2.3 Substitute Parts

3.2.3 Maintenance Program Support (KC-10A)

3.2.3.1 Heavy Maintenance/Programmed Depot Maintenance Plan Document Support

3.2.3.2 Field and Depot Level Maintenance Historical Data

3.2.4 AFTO 22/AF Form 847/AF Form 1000 Evaluation

3.2.5 Master Data Files

3.2.5.1 Data Requests

3.2.5.2 MDF File Index

3.2.5.3 KDC-10 Drawing Revision Service (KDC-10)

3.2.6 Support for Aircraft Modifications

3.2.7 Cost Estimates

3.2.8 Environmental/Bioenvironmental Support

3.2.9 Safety

3.2.9.1 Safety Inquiries

3.2.10 Meetings and Conference Attendance/Support

3.2.10.1 Program Management Review (PMR)

3.2.10.2 Conference Attendance/Support

iii

3.2.10.3 Flight Manual Review Conferences

3.2.11 Tech Data Review/Update

3.2.12 Engineering Disposition Automated Routing System (eDARS) Technical and Software Support (KC-10A)

3.2.12.1 Technical Support

3.2.12.2 eDARS Software Support

3.2.13 Weapon System Integrity Program (WSIP) Support (KC-10A)

3.2.13.1 ASIP

3.2.13.2 Mechanical Systems Integrity Program (MECSIP) and Avionics Integrity Program

(AVIP)

3.2.13.3 Corrosion Prevention and Control Program (CPCP)

3.2.14 Pre-Proposal Review of Engineering Assignments

3.2.15 Diminishing Manufacturing Sources and Material Shortages (DMSMS) (KC-10A)

4.0 Nonrecurring Engineering (NRE)

4.1 NRE Description

4.2 Prototype and Kit-Proof Modifications

4.3 Authorization

4.4 Acceptance and Contractual Change

4.5 Performance

4.6 Notification of Expenditure

4.7 Notification of Completion/Closure

4.8 Engineering Studies

4.9 Engineering Support

4.10 Aircraft Mission Support

4.11 Deficiency Reporting

5.0 Deliverables

6.0 Quality Assurance Provisions

7.0 Government POC

SECTION II – SERVICE SUMMARY

1.0 Introduction

1.1 Performance Objectives and Thresholds

iv

1.2 Surveillance Methods

2.0 Contractor Performance Evaluation

Table 2-1: Service Summary

SECTION III – GOVERNMENT FURNISHED PROPERTY/SERVICES

1.0 Government Furnished Property (GFP)

1.1 Data

1.2 Specific GFP

SECTION 1 – DESCRIPTION OF SERVICES

1.0 INTRODUCTION

This Performance Work Statement (PWS) describes the recurring and nonrecurring engineering support services required to sustain and modernize the aircraft identified herein, as determined by the Government. The following Weapon Systems are supported by this PWS:

1. United States Air Force – KC-10A

2. Royal Netherlands Air Force (RNLAF) – KDC-10

1.1 Scope

This PWS describes requirements necessary to provide Sustaining Engineering Services for the KC-10A and KDC-10. Technical and program direction for this PWS are provided under the direction of the Legacy Tanker Division, AFLCMC/WKD.

1.2 Applicability

All paragraphs are applicable to both KC-10A and KDC-10, unless noted otherwise.

1.3 Period of Performance

This PWS supports a 15-month basic period of performance and two 1-year options with a 6-month option to extend. The contract will expire on 30 June 2020 if all options are exercised by the Government.

2.0 ENGINEERING SUSTAINMENT SUPPORT REQUIREMENTS

2.1 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 provided in section 3.0 Recurring Engineering/Data Services. The “Non-Recurring” service will be accomplished only upon specific requests of the Procurement Contracting Officer (PCO) and issued as Engineering Assignments (EAs) against the contract.

The Contractor shall provide personnel who are capable of effectively communicating with the government.

The Contractor shall provide the resources to accomplish the requirements of this contract.

Resources will include, as a minimum, Contractor developed proprietary design data, modification data, production data and personnel with special skills such as aerodynamics, structural and electrical design, stress analysis, corrosion, engines, maintenance planning, non-destructive inspection, technical writing and FAA-Designated Engineering Representatives (DERs) and FAA-Authorized Representatives (ARs).

2.1.1 Program Location

The Contractor’s main business location for the recurring effort shall be in the local vicinity of Tinker AFB. The location for non-recurring efforts will be dependent on the skills and resources required for each EA; however, local vicinity personnel shall have the project engineering responsibility for each EA.

2.1.2 Days

All deliverables are expressed in calendar days.

2.1.3 Program Engineers and Lead Equipment Specialist

Program Engineer in the PWS is defined as a Government KC-10A assigned engineer. The Lead Equipment Specialist (ES) is the Government KC-10A Lead ES.

2.1.4 Program Documentation

All records, files, documents, and work papers generated by the contractor during execution of this contract will be marked and delivered with appropriate data rights to the PCO as outlined in the contract.

2.2 Engineering Assignments

2.2.1 Definition

Engineering Assignments (EAs) will be used to authorize engineering support services under the PWS. EA tasks require greater than 250 manhours to accomplish.

2.2.2 EA Funding Types

EAs generated under this PWS will be funded as Cost Plus Fixed Fee (CPFF), Firm Fixed Price (FFP), or Time and Materials (T&M). EAs will be funded with CPFF when the extent of work is unknown or cannot be reasonably estimated with any degree of confidence. FFP will be used for well-defined efforts with very few unknowns. T&M will be used only in emergency situations such as providing engineering/technical support to safety investigating boards, resolving safety of flight issues, or returning grounded aircraft to flight status.

2.2.3 EA Proposal Submittals

For EAs funded as FFP and CPFF efforts, the Contractor shall submit formal cost/schedule proposals to the CO in a format agreed upon by the CO and the Contractor. For EAs funded as T&M efforts, the Contractor shall submit informal estimates of EA cost and schedule to the CO accompanied by a table that delineates the cost by EA paragraph. The cost table shall be provided in contractor format. The proposals shall be submitted to the Government IAW the time frames outlined Table 1-1 below. Fully funded positions (i.e., single points of contact, etc.)

shall not separately charge for any efforts in support of proposal preparation.

Table 1-1: EA Proposal Submittal Time Frames

3.0 Recurring Engineering/Data Services

The Contractor shall perform the following engineering/data services as prioritized and directed by the PCO.

3.1 Firm Fixed Price (FFP) Tasks

3.1.1 Single Point of Contact

The Contractor shall provide a single Point of Contact, (POC) for management of projects and any alternate(s) who shall act for the Contractor. The name(s) shall be provided to the PCO in writing within two working days after contract award. These POCs shall ensure proper planning, scheduling, visibility, control and performance of the KC-10A and KDC-10 Sustaining Engineering Services contract. The POCs shall also channel requests to proper organizations

Contract Funding Type EA Funding Threshold Proposal Submittal Schedule

FFP/CPFF

≤ Truth In Negotiations Act (TINA) Threshold Within 30 calendar days

> TINA Threshold Within 45 calendar days

T&M N/A Within 5 calendar days

Note: Proposal submittal schedule may be extended at the discretion of the PCO if warranted by special situations.

within the Contractor’s facility and plan/program all tasks to ensure timely actions and responses to Air Force requirements.

3.1.2 In-Flight Emergency Support

The Contractor shall provide a 24-hour per day focal point within 2 days of contract award to the PCO to coordinate requests for in-flight emergency assistance with in-plant design and technical personnel to assure quick response to using activities experiencing in-flight emergencies. The Contractor shall ensure the instructions for obtaining the support for in-flight emergencies are current at all times and disseminated to the appropriate government organization. CDRL A001.

3.1.3 Systems Engineering

3.1.3.1 Specialty Engineering Disciplines

The Contractor shall provide the Engineering disciplines listed below:

a) Systems Integration

b) Electrical Loads Analysis (ELA)

c) Weight and Balance

d) Environmental Control System (ECS)

e) Electromagnetic and Environmental Effects Engineering

f) Antenna/Radio Frequency Effects

g) Stress and Structures

h) Aerodynamics/Air Vehicle Performance

i) Product Engineering

j) Configuration Management

k) Test and Evaluation

l) Reliability and Maintainability (R&M)

m) FAA Type Certification

n) Software/Firmware

o) System Safety

3.1.3.2 Systems Engineering Management Plan (SEMP)

The Contractor shall prepare and deliver a SEMP. Execution of recurring and nonrecurring tasks shall follow the approved SEMP. The SEMP shall address the following, as a minimum. CDRL A002

a) Operational Safety, Suitability and Effectiveness (OSS&E) per AFI 63-101/20-101

b) Airworthiness – FAA requirements, AFPD 62-6 and AFI 62-601

c) Affordability, Cost Effectiveness and Earned Value Management

d) Requirements analysis and management

e) Functional analysis and allocation

f) Risk Management

g) Technical Reviews

h) System Safety

i) Design Synthesis

j) Validation/Verification

k) Information Assurance/Cyber Security

l) R&M

m) Human Systems Integration

n) Configuration/Baseline/Data Management

o) Technology Insertion

p) Interface Control

q) System Architecture Development

r) Quality

s) Integrated Planning and Scheduling

t) Technical Performance Measures (TPM)

3.1.4 Service Information and FAA Directive Review (KC-10A)

The Contractor shall review publications pertaining to Federal Aviation Administration (FAA) compliance, OSS&E and system/component Original Equipment Manufacturer (OEM) information or suggested actions. The Contractor review shall include the following:

a) Airframe Service Bulletins (SBs)

b) Airframe Service Letters (SLs)

c) Structural Item Interim Advisories

d) Telegraphic Messages issued by the manufacturer of the aircraft

e) FAA Notices of Proposed Rule Making (NPRM) – new and revised

f) Airworthiness Directives (ADs)

g) Any other new or revised FAA final rules

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

3.1.4.1 Evaluation Content (KC-10A)

The Contractor shall review publications and for each publication upon which the Contractor recommends government action be taken (excluding Monthly Attrition letter items), provide the following information, as applicable, within 30 days of receipt. CDRL A003

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 United States Air Force (USAF) mission, maintenance concepts and unique configurations

b) ADs/SBs associated with the subject service publication

c) Service publication effectivity by tail number, referencing group number effectivity based on configuration; also identify if spares are affected

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

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

f) Identification of service publications subject to aircraft uniqueness issues

g) Impact to all affected Technical Orders (TOs), available Time Compliance Technical

Orders (TCTOs) or Manuals

3.1.4.2 Applicable Inspection/Modification Accomplishment

The Contract shall provide the following for each applicable inspection/modification accomplishment as part of the above evaluation.

a) Brief description of the accomplishment instruction

b) Level of incorporation: Field or Depot

c) Threshold for inspection/modifications and repetitive intervals for inspections (both commercial and Air Force equivalent)

d) Manhours required to accomplish inspection/modification as listed within the service information publications

e) Contractor recommendation for each inspection/modification accomplishment instruction. Specify if accomplishment is a terminating action for the subject service publication

f) Priority of incorporation

g) Specific kit requirements including kit part number(s), quantity, kit cost and re-order lead time as listed within the service information publication

h) Special tooling requirements including tool part number(s), quantity and tool cost as listed within the service information publication

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.

3.1.5 Dispatch Deviation Guide and FAA Minimum Equipment List

The Contractor shall provide updates to the DC-10 Dispatch Deviation Guide and FAA Minimum Equipment List as developed by the OEM and the FAA respectively. CDRL A004

3.1.6 Aircraft Airworthiness Management (KC-10A)

The Contractor shall develop and maintain an aircraft airworthiness management system as follows:

3.1.6.1 FAA Airworthiness Activity Requirements

The Contractor shall provide a listing of released FAA Airworthiness Requirements that have pending Government or Contractor activity requirements. The listings, to include suspense dates, shall cover each aircraft individually and shall extend into the future as far as necessary to cover pending activity. The outstanding requirements shall be divided into two areas based on the following categories. CDRL A005

a) Airworthiness requirements pending activity from a Government or Contractor organization as the next step in the accomplishment process. Within the listing identify the next step in the process and what Government or Contractor organization is responsible for performing the action.

b) Airworthiness requirements that the Government has dispositioned as accomplishing via an Alternate Means of Compliance (AMOC) or disapproved for accomplishment. If the AMOC consists solely of a later accomplishment date than the FAA stated date, the requirement shall not be included on the subject list.

3.1.6.2 Service Information Configuration Document (SICD)

The Contractor shall maintain and provide a historical report of all applicable SBs and ADs, with the current incorporation status on each aircraft. The Contractor shall update the report within 45 days after each semiannual period (31 March and 30 September). The Contractor shall evaluate and track data supporting incorporation from the best available data as provided by the Government. CDRL A003

3.1.7 Contractor Manpower Reporting

3.1.7.1 The Contractor shall report ALL contractor labor hours (including any subcontractor labor hours for services that exceed the simplified acquisition threshold) required for performance of services provided under this contract for the USAF required to meet the requirements of FY11 NDAA Section 8108 of Public Law 112-10, of the Department of Defense and Full-Year Continuing Appropriations Act, 2011. This data shall be provided through a secure data collection site located at http://www.ecmra.mil. The Contractor shall fill in all data fields required by the web collection site.

3.1.7.2 Reporting inputs will be for the labor executed during the period of performance for each Government Fiscal Year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of the each calendar year. The Contractor may direct questions to the Contract Manpower Reporting Application (CMRA) help desk.

3.1.7.3 Information from the secure website is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

3.1.7.4 Data for USAF service requirements must be input at the USAF CMRA link. User manuals for government personnel and contractors are available at the United States Army CMRA link at http://www.ecmra.mil.

3.1.8 Government Industry Data Exchange Program (GIDEP) Review (KC-10A)

The Contractor shall participate in the GIDEP to receive information from the Failure Experience Data Base (FEDB) and Product Information Data Base (PIDB). The Contractor shall screen information received from the DEDB and PIDB for applicability and provide a monthly summary of applicable items to the Program Engineer and Lead ES. CDRL A006

3.1.9 Electronic Data and Correspondence Exchange

The Contractor shall implement capabilities as needed to provide electronic data transfer capabilities IAW Government-approved industry standard techniques. Electronic data transfer capability will be required in two (2) areas:

a) Data/information on electronic media.

b) Implementation/maintenance of electronic data transfer.

3.1.9.1 Electronic Media

The Contractor shall deliver data in electronic or paper format that is accurate, secure and timely, as agreed to by the Program Engineer.

3.1.9.2 Hardware/Software Support

The Contractor shall provide hardware/software support to maintain the Government-to- Contractor data interchange as agreed to by the Program Engineer and the weapon system hardware/software support organizations. The support shall be in conjunction with other hardware/software support supplied by the Contractor.

3.1.9.3 MyBoeingFleet.com Data

The Contractor shall provide electronic access to MyBoeingFleet.com (MBF) services and use of the data per the MBF agreement (Contract Attachment X, Special Terms and Conditions) as follows:

3.1.9.3.1 Administration of Access

The Contractor shall provide a service that manages identification (ID) and initial password assignment to authorized MBF electronic access users. The Government ESS Program Manager (PM), as the Designated Government Liaison, or the PCO will approve all requests for MBF access prior to the Contractor granting access.

3.1.9.4 Data Accession List (DAL)

The Contractor shall develop and maintain an electronic database (using Commercial-Off-the- Shelf (COTS) industry standard Microsoft Windows compatible software) containing DAL items and making online access available to designated Government personnel. The Contractor shall notify the Government when the DAL is operational, no later than three (3) months following contract award. The Contractor shall establish backup and recovery processes that assure the DAL database will not experience catastrophic loss and can be transferred completely to the Program Engineers at the end of the contract. CDRL A004

3.1.10 Status Reports

The Contractor shall provide monthly status reports which address both the Recurring and Nonrecurring efforts. The report shall contain detailed schedules and status of RTIs and EAs in process and a list of RTIs and EAs accomplished. The report shall also detail, for each effort in progress, spend plan charts for time and material (T&M) efforts; and a table of authorized manhours, total manhours expended, total authorized funds and total funds expended. The

Contractor shall include residual Engineering Projects (EPs) and EAs initiated under contract

FA8106-07-C-001. CDRL A007

The Contractor shall provide a monthly cost status report that contains authorized funding, manhours expended, amounts billed, Estimate at Completion (EAC) and a percent of total EA funding expended by EA Accounting Classification Reference Number (ACRN). CDRL A007

The Contractor shall support KDC-10 Engineering Financial Reporting and provide a monthly status that is releasable to the RNLAF incorporating the items above. CDRL A008

3.1.11 Contractor Supplied Publications

The Contractor shall provide the following from the Boeing Data and Services Catalog whenever the document is updated in SGML format, if applicable:

a) DC-10 Standard Wiring Practices Manual (SWPM)

b) KC-10 Aircraft Maintenance Manual (AMM) (SGML format)

c) DC-10 Douglas Material Specification (DMS)

d) DC-10 Douglas Process Material (DPM) Index

e) DC-10 Douglas Process Standards (DPS)

f) DC-10 Illustrated Tool and Equipment List (ITEL)

3.2 Cost Plus Fixed Fee (CPFF) Tasks

3.2.1 Emergency, Urgent and Short Compliance FAA Airworthiness Directives

The Contractor shall monitor the issuance of ADs, including emergency ADs and immediately adopted rule ADs, at least once per calendar day including weekends and holidays. Within 48 hours of receipt, the Contractor shall provide copies and brief comments of any AD or any new or revised FAA Final Rule that require that requires operator compliance within 12 months. If, upon review, the AD appears to affect and require action on any aircraft in the PWS within seven

(7) calendar days, the Contractor shall immediately notify the Government and ensure contact is made. When not available on-line from applicable FAA websites, the Contractor shall obtain and provide copies to the Government.

3.2.2 Response to Technical Inquiries (RTIs)

The Contractor shall support requests for engineering, substitute parts and general inquiries in support of aircraft logistics efforts and Government objectives. The Contractor shall maintain cognizance over requests, directions and requirements to ensure that planning, programming, accomplishment of events and delivery meet Government objectives.

3.2.2.1 RTI Authorization

The Contractor shall provide timely response to issues from AFLCMC/WKDB Program Engineers and the Lead Equipment Specialist (ES). The Contractor shall respond to RTIs that can be completed in less than 40 manhours per occurrence without prior authorization from the PCO or a Contracting Officer’s Representative (COR); however, authorization from PCO or COR must be obtained before proceeding on any RTI that requires more than 40 but less than 250 manhours to complete. RTIs that require more than 250 manhours to complete will be accomplished as non-recurring EAs.

The Contractor shall obtain written/verbal approval from a Program Engineer prior to responding to a request originating outside of Program Engineering or the Lead ES.

3.2.2.2 RTI Reporting

The Contractor shall provide a monthly report that includes the monthly efforts supported, planned execution schedule, actual schedule, and the number of manhours expended each month per RTI. CDRL A005

3.2.2.3 Substitute Parts

The Contractor shall provide engineering support to resolve substitute part requests. The Contractor shall document engineering decisions and provide a recommendation to the Program Engineer and, if required, update the engineering drawings. The Contractor shall request approval for greater than 40 manhours, including an EA if necessary, for substitutes requiring considerable effort to obtain engineering or FAA approval. The Contractor shall notify the Program Engineer in writing with appropriate rationale, if an approved part is not available and a redesign or non-standard component is required.

3.2.3 Maintenance Program Support (KC-10A)

The Contractor shall develop and propose to the Program Engineer changes to the Scheduled Inspection and Maintenance Requirements Manual (-6 TO), Programmed Depot Maintenance Plan and Heavy Maintenance Plan as applicable based on ADs, SBs and SLs. The Contractor shall propose changes based on changes to the operational profile, safety or mission critical failures experienced by the 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.

3.2.3.1 Heavy Maintenance/Programmed Depot Maintenance Plan Document Support

The Contractor shall maintain the existing Heavy Maintenance (HM)/Programmed Depot Maintenance (PDM) document. The Contractor shall identify and validate changes needed to maintain the document. The Contractor shall recommend changes to the plan no less than once per year to the Program Engineer for approval. The Contractor shall provide a revised document incorporating approved changes. CDRL A009

3.2.3.2 Field and Depot Level Maintenance Historical Data

The Contractor shall maintain access to the Reliability and Maintainability Information System (REMIS) or Air Force Knowledge System (AFKS). The Contractor shall use REMIS or AFKS as necessary to obtain historical field and depot level discrepancy data (e.g. AFTO 349 or equivalent data) in support of maintenance activity, general inquiries, and execution of RCM and integrity program type analysis.

3.2.4 AFTO 22/AF Form 847/AF Form 1000 Evaluation

The Contractor shall analyze and evaluate Technical Manual (TM) Change Recommendation and Reply (AFTO 22s), Recommendation for Change of Publication (AF Form 847s) and IDEA application (AF Form 1000s) and provide recommendations at the request of the Lead ES. The Contractor shall provide periodic status of the reviews in-progress at an interval specified by the Lead ES.

As required, the Contractor shall perform evaluations of AF Form 1000s in accordance with Air Force Instruction (AFI) 38-401, The Air Force Innovative Development through Employee Awareness (IDEA) Program, and provide a recommendation with the following support data:

a) Supporting information for recommendation.

b) Cost evaluation.

3.2.5 Master Data Files

The Contractor shall organize, maintain and manage the Master Data File (MDF). The MDF shall consist of data provided to the Contractor by the Government and data developed by the Contractor for the Government and includes technical data that defines the technical baseline for platforms covered by this contract. The MDF may include data in both physical and electronic form. The Contractor may store technical data developed under this contract in the electronic or physical form in which it was released or is being maintained. The MDF shall include, but not be limited to, final versions of: released engineering drawings; modification specifications; test procedures; test reports; vendor manuals; historical maintenance records; MDF file index; and FAA records.

The Contractor shall develop and provide a Program Data Management Plan within 90 days after contract award that defines the management of the MDF and other data developed under this contract. The plan shall be approved by the Government. Data prepared for the Government under this contract shall be included in the MDF as defined in the Program Data Management Plan. The Plan shall also include a MDF disaster recovery plan. CDRL A004

The MDF shall be stored and managed by the Contractor. Data provided by the Government shall be treated as Government Furnished Information (GFI) subject to DFARS 252.227-7025.

“Technical data” and “computer software” shall have the meaning ascribed to those terms in DFARS 252.227-7013 and 252.277-7014, respectively. Ownership and rights to the data in the MDF remain unchanged. The Contractor shall have no additional rights in the data based on its custodial role. The Government shall retain all existing rights and responsibilities with respect to Government provided data.

The MDF shall be maintained and made accessible to the Government by the Contractor. The Contractor shall provide a POC with 14 days of contract award for Government requests for data.

If the follow-on Contractor is not the incumbent Contractor, or the Government terminates the contract at any time, the incumbent Contractor shall participate in and complete, a phase-out joint inventory no later than ten (10) calendar days prior to the end of the last performance period.

3.2.5.1 Data Requests

The Contractor shall provide data to the Program Engineer including furnishing of one copy reproduced from the best available master of nonproprietary and releasable proprietary data.

Requests for such data will be limited to that required for support of the aircraft identified in this contract.

3.2.5.2 MDF File Index

The Contractor shall create and maintain an electronic file index which references all data contained in the MDF. The Contractor shall update the file index as required. The Contractor shall provide the updated file index quarterly. CDRL A004

3.2.5.3 KDC-10 Drawing Revision Service (KDC-10)

The Contractor shall provide revised data to the Program Engineer and RNLAF for previously delivered aerial refueling system KDC-10 drawings. The Contractor shall deliver data whenever revisions are received, but no less than annually. CDRL A004

3.2.6 Support for Aircraft Modifications

The Contractor shall support aircraft modifications using processes defined in the SEMP. The Contractor shall accomplish engineering reviews related to definition of, planning for or accomplishment of modifications of weapon systems identified in this contract. The Contractor shall assist in identifying and resolving technical problems that arise in the design and integration of new systems. The Contractor shall support by participating in management, design and technical meetings and performing detailed technical review of design and installation, engineering and technical publications as requested by the Program Engineer. The Contractor technical reviews shall include, but is not limited to, safety, structural, installation/integration, software, testing, certification, supportability, and reliability/maintainability concerns. The objective of these reviews will be to enhance aircraft safety of flight and compatibility of mission equipment. The Program Engineer will define the extent of the effort and provide access to the requisite data needed for this support. The Contractor shall provide recommendations, including supporting technical data, as requested.

3.2.7 Cost Estimates

The Contractor shall, as requested, develop and provide cost estimates to support the pricing of EAs and other contracting efforts. The Contractor shall also provide estimates in support of decision making and the planning, prioritization, identification and capture of funding for future efforts. The Contractor can receive requests for estimates from the PCO or from the Program Engineer. Cost estimates shall include 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.

3.2.8 Environmental/Bioenvironmental Support

The Contractor shall support the Program Engineer on environmental/bioenvironmental issues/concerns and provide recommendations, as requested. The Contractor shall be familiar with federal (EPA, OSHA, DoD, etc.), state and local existing and proposed environmental laws and regulations that may impact the weapon systems.

The Contractor shall respond to Program Engineer inquiries and review applicable government data provided from other Contractors and identify issues/concerns to the Program Engineer. The Contractor shall review recurring and non-recurring engineering efforts and identify issues/concerns to the Program Engineer. The Contractor shall support designated working group meetings, conferences and workshops upon specific request by the Program Engineer.

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

3.2.9 Safety

The Contractor shall develop and maintain a safety program with responsibility for oversight and review of engineering development activities within 90 days of contract award. The Contractor’s safety engineering program shall meet the requirements of 14 CFR Part 25 and the latest edition of MIL-STD-882. CDRL A004

The Contractor shall review recurring and non-recurring efforts for safety issues. The Contractor shall attend designated technical meetings, reviews or safety working group meetings at the request of the Government. The Contractor shall support proactive planning to ensure safety issues are addressed.

3.2.9.1 Safety Inquiries

The Contractor shall immediately report any situation that may affect ground or flight safety of aircraft and/or personnel to the Government. The Contractor shall provide an initial response, including a Preliminary Hazard Analysis (PHA) and an initial Risk Assessment Code (RAC) per MIL-STD-882 within 24 hours of a safety inquiry or discovery of a safety situation. The initial response shall include a schedule and estimate of effort completing the analysis through the development of a risk management recommendation. CDRL A009

3.2.10 Meetings and Conference Attendance/Support

3.2.10.1 Program Management Review (PMR)

The Contractor shall host and conduct a PMR to discuss engineering support status every three months or as requested by the Chief Engineer. The Government and Contractor shall mutually agree upon agenda items; however, all open EAs shall be included. The Contractor shall prepare and provide a proposed agenda and presentation materials as requested by the Government prior to the meeting. The reviews must include detailed information (such as individual EA spend plan, current cost and schedule status, potential problem areas, etc.) to allow a thorough understanding of the “health” of each EA. The Contractor shall also furnish the necessary facility. The Contractor shall prepare and provide coordinated minutes to the Program Engineer and appropriate attendees within 14 days after the meeting. The Contractor shall provide the Government at least seven (7) days to review the minutes prior to delivery of the coordinated minutes. CDRL A010 (agenda) CDRL A011 (minutes)

3.2.10.2 Conference Attendance/Support

The Contractor shall attend and provide technical support to certain annual meetings/conferences to include, but not limited to, the Aging Aircraft Conference, Aerial Refueling Systems Advisory Group (ARSAG), KC-10A Maintenance Steering Group, KC-10A Contractor Logistics Support (CLS) PMR, and the DC-10, MD-10 and MD11 Fleet Team Meeting. Support shall include a trip report detailing discussions related and impacting the KC-10A and KDC-10 due within 14 days after completion of the meeting. CDRL A009

3.2.10.3 Flight Manual Review Conferences

The Contractor shall attend and provide technical support to annual Flight Manual Review Conferences (FMRCs). Each FMRC will last up to five (5) days including travel time and will be conducted at a CONUS location outside of the local Oklahoma City area.

3.2.11 Tech Data Review/Update

The Contractor may be required, as a result of work conducted in support of non-recurring or recurring tasks, to review and update existing technical data. The Contractor may be required to provide a list of impacted technical data.

The Contractor may be required to develop technical source data in response to new operational, maintenance or logistic procedures/requirements.

The Contractor will use engineering source data and USAF requirements when developing updates for existing technical data or when developing technical source data.

3.2.12 Engineering Disposition Automated Routing System (eDARS) Technical and Software Support (KC-10A)

3.2.12.1 Technical Support

The Contractor shall be prepared, at onset of contract award, support all Aircraft on Ground (AOG) requests and any others submitted through eDARS. Support shall be available 24 hours per day, seven (7) days per week. Support shall also include on-site visits, as required.

3.2.12.2 eDARS Software Support

The Contractor shall host and provide support as requested to upgrade, revise and maintain the eDARS program and database, as well as provide access as needed.

3.2.13 Weapon System Integrity Program (WSIP) Support (KC-10A)

The Contractor shall prepare and submit a WSIP plan within 90 days of contract award. The plan shall be updated annually to include changes in methodology and policies. The plan shall ensure sound engineering tools, processes, and practices are integrated at the system level to allow sustainment of the OSS&E of the KC-10A aircraft, all IAW FAA process and procedures.

In particular, the plan shall include, but not be limited to, the following:

a) Oversight of ongoing integrity programs

b) Document WSIP activities

c) Prepare an annual WSIP report.

The WSIP program shall include Aircraft Structural Integrity Program (ASIP), Mechanical System Integrity Program (MECSIP), Avionics Integrity Program (AVIP) and the Corrosion Prevention and Control Program (CPCP).

3.2.13.1 ASIP

The Contractor shall conduct and maintain an ASIP IAW AFI 63-101, Integrated Life Cycle Management, and MIL-STD-1530, Aircraft Structural Integrity Program. The Contractor shall:

a) Update and maintain the currency of the KC-10A Individual Aircraft Tracking Program (IATP) with AFTO Form 18 data available through OC-ALC/EN, findings from applicable inspections and information concerning major structural repairs and/or replacements

b) Participate in ASIP reviews/briefings

c) Prepare and submit the annual ASIP report; to include updating the Equivalent Flight

Hour (EFH) Calculator spreadsheet from the latest IATP data

d) Prepare and deliver an updated version of the ASIP Master Plan IAW MIL-STD-1530, Paragraph 5.1.1.3 60 days prior to contract closure which details programmatic tasks required to ensure KC-10A structural integrity.

e) Review SBs, ADs and aircraft modifications/repairs for ASIP impact

The Contractor may also be required to develop depot and field level Non-Destructive Inspection (NDI) procedures to support ASIP inspections. CDRL A009

3.2.13.2 Mechanical Systems Integrity Program (MECSIP) and Avionics Integrity Program

(AVIP)

The Contractor shall provide engineering/technical support to assist the KC-10A Program Engineers in maintaining a proactive and effective MECSIP and AVIP for all mechanical and avionics systems, subsystems, equipment and components of the KC-10A aircraft (NOTE: with the exception of CNS/ATM installed/modified equipment).

The Contractor shall develop, if necessary, maintain and update annually the KC-10A MECSIP and AVIP plans IAW AFI 63-101, Integrated Life Cycle Management, MIL-STD-1798, Mechanical Equipment and Subsystem Integrity Program, and MIL-STD-1796, Avionics Integrity Program. CDRL A009

3.2.13.2.1 The Contractor shall maintain accurate and current prioritized Critical Components Lists (CCLs) for safety-critical, mission-critical and durability-critical mechanical and avionics systems components utilizing an approved prioritization methodology for safety, reliability, availability, Total Non-Mission Capable for Maintenance (TNMCM), aborts, inherent failures and cannibalization actions. Usage data shall be provided via the Government as supplied by the Contractor Logistics Support (CLS) contractor. The CCLs shall be accessible via the DAL.

CDRL A009

3.2.13.2.2 The Contractor shall monitor all mechanical and avionics systems and subsystems using established CCL methodology. For components whose Mean Time Between Failure Type 1 (MTBF-1) fall below 80% of the established Mean Acceptable Performance (MAP) value, issue CCL performance degradation alerts for those components with a validated degradation correlation that include recommendations for continued monitoring or further assessment.

CDRL A009

3.2.13.2.3 The Contractor shall develop a plan and support completion of tasks included in MIL- STD-1798C Table 1 MECSIP tasks. Specific tasks that will be accomplished shall be determined by mutual consent of the Contractor and the Government. Examples include reviewing the 1C-10(K)A-6WC decks for accuracy, ensuring technical data is available and current, developing safety- and mission-critical component inspection and/or replacement intervals, developing a “Bad Actor” program, and monitoring component repairs and overhauls.

CDRL A009

3.2.13.2.4 The Contractor shall maintain a prioritized list of all candidate initiatives that will improve safety or R&M of current mechanical/avionics systems, subsystems, equipment or components. CDRL A009

3.2.13.2.5 The Contractor shall publish an end-of-year MECSIP/AVIP systems health assessment report that summarizes the top MECSIP/AVIP drivers for the year including TNMCM, inherent failures, cannibalizations, aborts and change in performance/MTBF alerts.

Other topics that will be included in this report shall be determined by mutual consent of the Contractor and the Government. CDRL A009

3.2.13.2.6 The Contractor shall accomplish analyses on mechanical/avionics systems anomalies and/or deficiencies identified through monitoring and assessment, aircraft mishaps, Maintenance Steering Group (MSG) recommendations, Engineering Investigation Deficiency Reports/Product Quality Deficiency Reports (EIDRs/PQDRs), etc. as requested by the Government. Specific efforts that may be accomplished under this effort include Reliability Assessments, Risk Assessments, Service Life Assessments and Life Cycle Assessments. CDRL A009

3.2.13.2.7 The Contractor shall determine potential solutions for any safety issues or R&M opportunities that are either identified as part of the MECSIP/AVIP process or through other activities as requested by the Government. The solutions must be validated by detailed, comprehensive root cause analyses to ensure the proper solutions to the problems are identified and justified by quantitative data. There are no limitations or restrictions to the potential solutions that may be proposed to resolve problems; i.e., they may include parts upgrades, procedural changes, system modifications, etc. Generate Budgetary Planning Estimates (BPEs) or Follow-on Planning Estimates (FPEs) for each solution as requested by the Government.

Rules and definitions guiding these solutions shall be as follows:

a) Potential solutions must include the FAA certification process and associated costs

b) A BPE will be comprised of cost and schedule estimate for NRE, prototype development and installation, and implementation on the affected aircraft

c) An FPE will be comprised of manhour and schedule estimates for NRE, prototype development and installation, and implementation on the affected aircraft

Provide the proposed solutions, root cause analyses and BPEs/FPEs upon their completion n interim letters to the Government. CDRL A009

3.2.13.2.8 The Contractor shall develop complete technical data packages for the solutions identified in Paragraph 2.2.22.7 above that are requested by Government for further development. Completion of these technical data packages may require the development of manufacturing and installation drawings, generation of TO source data, fabrication and installation of prototype parts, completion of laboratory and/or flight tests and generation of FAA required supporting data for certification. CDRL A009

3.2.13.2.9 The Contractor shall support and attend meetings for MECSIP, work card reviews, AVIP, Cockpit Working Group (CWG) and System Safety Group as requested by the Government. Additionally, conduct TIMs as required to review the status and acceptability of efforts being accomplished under this task.

3.2.13.2.10 The Contractor shall identify to the Government data required from other KC-10A contractors to support these activities.

3.2.13.3 Corrosion Prevention and Control Program (CPCP)

The Contractor shall maintain visibility of KC-10A corrosion and coating issues. The Contractor shall submit an annual report of corrosion repairs; to include those requiring OEM dispensation as well as standard depot repairs, with possible preventive recommendations in order to identify possible trends. The Contractor shall evaluate and propose projects as requested to address coating issues such as chromium VI workplace issues, leading edge erosion, removal of chromium VI from the coating system, etc. CDRL A009

3.2.14 Pre-Proposal Review of Engineering Assignments

Review of EAs by the Contractor prior to the Government requesting a formal proposal is required to ensure completeness, accuracy and clarity of requirements.

3.2.15 Diminishing Manufacturing Sources and Material Shortages (DMSMS) (KC-10A)

3.2.15.1 The Contractor shall provide a supply chain supportability and obsolescence web-based program to identify pending DMSMS issues. Contractor shall obtain the license, provide interface to Government and Contractor personnel, and provide training as required.

3.2.15.2 The Contractor shall identify aircraft parts from Bills of Material (BOMs) from KC-10A Line Replaceable Unit (LRU) Component Maintenance Manuals (CMMs) and upload those to the subject program to query various on-line parts availability services (Q Star, Haystack, etc.).

Also, the Government may identify additional parts and supply the required information to be input into the program.

3.2.15.3 The Contractor shall provide a quarterly report detailing possible DMSMS issues.

CDRL A009

4.0 Nonrecurring Engineering (NRE)

4.1 NRE Description

The Contractor shall perform NRE/data services as prioritized and directed by the PCO. The non-recurring services will be accomplished only upon specific requests of the PCO and issued as EAs against the contract.

4.2 Prototype and Kit-Proof Modifications

The Contractor may be requested to perform any and all phases (i.e., site surveys, engineering design, technical data development, TCTO preparation, fabrication, kit procurement, installation, test, FAA and military certification, and delivery) necessary to complete prototype and kit-proof modifications. Prototype modifications shall be defined as the first modification performed for a specified weapon system configuration. Kit-proof modifications shall be defined as the second modification performed to validate systems for production TCTO readiness. Multiple configurations for a single weapon system may result in multiple prototype modifications for that weapon system. Prototype modifications may include, but not be limited to, modifications to airframe, aircraft systems, aircraft avionics/Command, Control, Communication and Information (C3I) and mission equipment. Prototype modifications may be required to support correction of deficient or obsolete systems as well as the development of new and enhanced systems. As requested, the Contractor may be required to provide spares provisions as necessary to support installation and testing.

4.3 Authorization

The Contractor shall accomplish work on EAs only after authorization from the PCO.

Government contract orders will include formal work authorizations for each EA and will identify or define the EA problem, task description or PWS, due date and total estimated cost.

4.4 Acceptance and Contractual Change

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 estimated cost or by the authorized due date. The Contractor shall notify the PCO within 30 days of any recommended changes to the EA that would resolve the potential funding/completion data shortfall(s).

The Contractor may recommend changes to an EA that do not impact the total estimated cost.

The Contractor shall coordinate any such proposed changes through the Program Engineer. If the Program Engineer concurs with the proposed 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.

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

4.6 Notification of Expenditure

The Contractor shall provide written notification to the PCO (copy to the Program Engineer and ESS PM) a minimum 30 days prior if expenditures are expected to exceed 85% of the total estimated cost on the EA.

The Contractor shall notify the PCO when it is determined that the actual expenditures on an EA will be substantially less than the total estimated cost.

4.7 Notification of Completion/Closure

The Contractor shall provide written notification to the PCO when…