ASESFollow-OnFINALPWS14Jul22.pdf

PERFORMANCE WORK STATEMENT

FOR

C/KC-135 Avionics Sustaining

Engineering Services (ASES)

14 July 2022

Prepared by

AFLCMC/WLTMC

3001 Staff Dr. Ste 2AF1 91A

TINKER AFB OK 73145

Table of Contents

SECTION I – DESCRIPTION OF SERVICES

1.0 INTRODUCTION

1.1 Background

1.2 Problem Statement

1.3 Scope

2.0 APPLICABLE DOCUMENTS

2.1 Access

2.2 Documents

3.0 AVIONICS SUSTAINING ENGINEERING SERVICES REQUIREMENTS

3.1 General Requirements

3.1.1 Task Assignments

3.2 Performance Requirements

3.2.1 Personnel Requirements

3.2.2 Subcontractors

3.2.3 Remote Duty Assignments

3.2.4 Access to Government Systems

3.2.5 Materials, Supplies, and Services

3.2.6 Program Documentation

3.2.7 Software/System Integration Laboratory

3.2.8 In-sourcing Requirements

3.2.9 Use of Ozone Depleting Substances (ODCs)

3.2.10 Mission Essential Services

3.2.11 Markings and Legends

3.3 Recurring Engineering Services Requirements

3.3.1 Recurring Mission Support

3.3.2 Recurring Technical Support

3.4 Non-Recurring Engineering Services Requirements

3.4.1 Aircraft Mishap and Incident Investigations

3.4.2 Engineering and Technical Assistance

3.4.3 Reserved

3.4.4 Hardware and Software Development/Sustainment

3.4.5 Prototyping of Hardware/Software Changes

3.4.6 Test Procedures

3.4.7 Avionics System Integrity Program (AVIP) Evaluations

3.4.8 Airworthiness/Service Publications

3.4.9 Government Vendor Support

3.4.10 Product Improvement and Avionics Planning

3.4.11 Logistics Support

3.4.12 Source Data/Change Packages

3.4.13 Support for Technical Conferences/Seminars

4.0 DATA DELIVERABLES

5.0 QUALITY ASSURANCE PROVISIONS

6.0 SPECIAL REQUIREMENTS

6.1 Security

6.2 Travel

6.3 Information Assurance/Information Technology Protection

6.4 Voluntary Protection Plan (VPP)

7.0 PERIOD OF PERFORMANCE

8.0 POINT OF CONTACT

SECTION II – SERVICE SUMMARY

1.0 INTRODUCTION

1.1 Performance Objectives and Thresholds

1.2 Surveillance Methods

2.0 CONTRACTOR PERFORMANCE EVALUATION

SECTION III – GOVERNMENT FURNISHED PROPERTY/SERVICES

1.0 GOVERNMENT FURNISHED EQUIPMENT/PROPERTY

1.1 Physical Inventory Report

2.0 GOVERNMENT FURNISHED SERVICES

SECTION I – DESCRIPTION OF SERVICES

1.0 INTRODUCTION

1.1 Background

Over the last 22 years, the avionics systems in the C/KC-135 aircraft have been updated from

1950’s era stand-alone analog systems to modern, fully integrated, software-controlled digital systems. This modernization began with installation of Pacer CRAG from 1999 through 2003, which added a new radar, compass, Global Positioning System (GPS), Traffic Alert and

Collision Avoidance System (TCAS), Enhanced Ground Proximity Warning System (EGPWS) and cockpit Multi-functional Displays (MFDs) to the aircraft. It continued with the addition of

Global Air Traffic Management (GATM) to the aircraft from 2003 through 2011, which included

Communications, Navigation, and Surveillance /Air Traffic Management (CNS/ATM) systems and APX-119/Mode V. Today, KC-135s are receiving the Block 45 upgrade which will include new autopilot, flight director, radar altimeter and electronic engine instruments displays and is projected to occur from 2014 to 2027. Some of the Line Replaceable Units (LRUs)/components used in these systems are military-unique equipment; however, most of the LRUs/components and their embedded software are Commercial Off-the-Shelf (COTS) equipment with proprietary data rights held by the Original Equipment Manufacturers. The Legacy Tanker Division require the knowledge, expertise, experience, and specialized engineering capabilities of a qualified contractor who has access to commercial design data, proprietary software code and limited rights engineering/technical data to maintain/sustain the day-to-day safety and operations of these avionics systems. This contractor support is also critical in maintaining the Operational

Safety, Suitability and Effectiveness (OSS&E) of these avionics systems in the C/KC-135 aircraft.

1.2 Problem Statement

Engineering support is required to accomplish recurring and nonrecurring engineering services to support maintenance and sustainment of C/KC-135 aircraft avionics systems. This support shall include avionics systems engineering support, detailed design engineering, design change analyses, avionics system and subsystem integration, technical analyses, liaison engineering support, drawing and technical order development, safety analyses, reliability and maintainability analyses, ground and flight test support, program analyses, design study preparation, mishap investigation, engineering feasibility studies, material deficiency report analyses, field problem investigation, failure analyses, and in-flight emergency response. The contractor shall also develop and sustain ground and/or flight software for Block 30, Block 40, Block 45 and other modifications/upgrades used on C/KC-135 aircraft. The contractor must have expertise in the design, integration, and sustainment of avionics systems, subsystems, their related components and associated ground/flight software code and system components and must have access to design, engineering, qualification, test, reliability, and configuration data for all avionics systems currently installed in the C/KC-135 aircraft. The contractor must also possess suitable facilities, tools, equipment, and personnel to provide all C/KC-135 aircraft avionics engineering support services.

http://www.acronymfinder.com/Communications%2c-Navigation%2c-and-Surveillance-_-Air-Traffic-Management-(CNS_ATM).html

1.3 Scope

This Performance Work Statement (PWS) describes the requirements necessary to provide

Avionics Sustaining Engineering Services for the sustainment of the avionics, communications and electrical systems, subsystems, related avionics systems components and associated ground/flight software used on the C/KC-135 aircraft weapon systems. The PWS requirements are associated with maintaining the operational safety, suitability and effectiveness of C/KC-135 aircraft avionics systems and, as such, shall include those engineering efforts required to:

(1) Achieve or substantially improve product performance beyond present operating levels

(development engineering);

(2) Plan, design, and develop tooling, obtain materials, perform quality assurance, and develop manufacturing procedures necessary to achieve a cost effective and producible production article (production engineering); and/or

(3) Review, assess, define, and resolve technical or supportability deficiencies revealed in fielded systems, products, and materials (sustaining engineering).

The -135 series aircraft encompassed by this PWS include all variants of C/KC-135 aircraft including the KC-135R/T, RC-135S/U/V and Foreign Military Sales (FMS) versions of the aircraft. Technical and program direction for this PWS are provided under the direction of the

Legacy Tanker Program Manager, Legacy Tanker Division.

2.0 APPLICABLE DOCUMENTS

2.1 Access

The contractor shall have access to or possession of all design, engineering, qualification, test, reliability, and configuration data (including all proprietary and limited rights drawings and technical data) for the avionics systems, subsystems, their related components and ground/flight software code used in the avionics systems currently installed in C/KC-135 aircraft if available.

The contractor shall also have access to or possession of a complete set of Technical Orders

(TOs) relating to the avionics systems in C/KC-135 aircraft including maintenance manuals (-2s) and Inspection Requirements Manuals (-6s).

2.2 Documents

The documents listed in Table 2.1 are provided for reference only and should be used by the contractor as guidelines during the execution of this PWS unless specifically addressed in a task paragraph. Additionally, this list will not be updated during the period of performance of this

PWS unless update of a document is necessary to ensure compliance with a specific paragraph of this PWS. In that case, the contractor shall identify any cost/schedule impacts or conflicts that will impact the contractor’s ability to accomplish the requirements of this PWS to the

Procurement Contracting Officer (PCO) within ten (10) working days after receipt of an updated publication. The contractor shall only implement PCO approved publication changes

Table 2.1 – Reference Documents

DOCUMENT DATE TITLE

AFI 17-101 6 Feb 2020 Risk Management Framework (RMF) for Air Force

Information Technology (IT)

AFI 31-501 27 Jan 2005 Personnel Security Program Management

AFI 16-201

30 Nov 2020

Disseminating Scientific and Technical Information

AFI 61-201 30 Nov 2020 Management of Scientific and Technical Information

(STINFO)

AFI 62-601 11 Jun 2010 USAF Airworthiness

AFI 63-101/20-101 30 Jun 2020 Acquisition/Logistics Integrated Life Cycle Management

AFLCMC/WKD OI 21-

8 Aug 2014

Engineering Completion of AFMC Form 202, Nonconforming Technical Assistance Request and Reply

AFMCI 63-1201 21 Jul 2021

Implementing Operational Safety, Suitability, and

Effectiveness (OSS&E) and Life Cycle Systems

Engineering

AFMCI 21-301 13 Jan 2017 Air Force Materiel Command Technical Order System

Implementing Policies

AS9100 2015

Aerospace – Model for Quality Assurance in Design, Development, Production, Installation, and Servicing

ASME Y14.100-2004 6 Sep 2005 Engineering Drawing Practices

CJCSI 6510.01F 9 Feb 2011 Information Assurance (IA) and Support to Computer

Network Defense (CND)

DoD 5220.22-M 28 Feb 2006 National Industrial Security Program Operating Manual

(NISPOM)

DoDI 8500.01 14 Mar 2014 Cybersecurity

AFI 17-130 13 Feb 2020 Cybersecurity Program Management

DoDI 4140.67 26 April

DoD Counterfeit Prevention Policy

DoDI 5200.44 04 Nov 2012 Protection of Mission Critical Functions to Achieve

Trusted Systems and Networks (TSN)

MIL-HDBK-516C 12 Dec 2014 Airworthiness Certification Criteria

MIL-STD-1796A 13 Oct 2011 Avionics Integrity Program (AVIP)

MIL-STD-1840C 22 Apr 2010 Automated Exchange of Technical Information

INACTIVE for new designs

MIL-STD-31000B 31 Oct 2018 Standard Practice Technical Data Packages

MIL-STD-38784A 04 Sep 2018 Standard Practice for Manuals, Technical: General Style and Format Requirements

MIL-STD-882E 11 May 2012 Standard Practice for System Safety

SAE Aerospace

Standard 9100D 20 Sep 2016

Quality Management Systems – Requirements for

Aviation, Space and Defense Organizations

DOCUMENT DATE TITLE

MECSIP AVIP Master

Plan 10 Dec 2019

Mechanical Equipment and Subsystems Integrity Program

(MECSIP) and Avionics Integrity Program (AVIP) Master

Plan

C/KC-135 PPP

AFLCMC/WKD-16-001

Version 4.0

15 Sep 20 C/KC-135 Weapon System Program Protection Plan (PPP)

IA PIT Guidebook 19 Dec 2013

Ver. 1.5

Information Assurance Platform Information Technology

Guidebook

3.0 AVIONICS SUSTAINING ENGINEERING SERVICES REQUIREMENTS

3.1 General Requirements

3.1.1 Task Assignments

3.1.1.1 Task Assignment Definition

Task Assignments will be used to authorize non-recurring engineering support services under this PWS. A Task Assignment is a Legacy Tanker Division developed form that identifies the problem, defines the work to be accomplished, specifies due dates, priorities, and provides the funding information for the support being acquired. The contractor shall accomplish both

Recurring and Nonrecurring Engineering Services in response to the requirements defined herein, and shall prepare and deliver data as listed on the Contract Data Requirements List

(CDRL).

3.1.1.2 Task Assignment Contract Types

Task Assignments generated under this PWS will be contracted as Cost Plus Fixed Fee (CPFF), Cost Plus Incentive Fee (CPIF), Firm Fixed Price (FFP), Fixed Price Incentive Firm (FPIF), Firm

Fixed Price Level of Effort (FFP LOE) or Time and Material (T&M) efforts.

3.1.1.3 Task Assignment Execution

The contractor shall fulfill the requirements of specific task assignments as designated in individual Task Assignments. The contractor shall provide the resources to accomplish requirements of this PWS within the specified cost and schedules. The contractor shall ensure work accomplished under this PWS is compliant with the quality standards as stated in the basic contract or applicable order.

3.1.1.4 Task Assignment Priorities

Task Assignments shall be prioritized in accordance with table 3.1.

Table 3.1 – Task Assignment Categories

3.1.1.5 Task Assignment Proposal Submittals

3.1.1.5.1 For Task Assignments contracted as FFP, FPIF, CPFF, CPIF, and/or FFP LOE efforts, the contractor shall submit formal cost and schedule proposals to the PCO in accordance with the table below. For Task Assignments contracted as T&M efforts, the contractor shall submit estimates of Task Assignment cost and schedule to the PCO accompanied by a table that delineates the cost by Task Assignment paragraph in accordance with the table 3.2. The formal/informal proposals (including cost table) shall be submitted in a format agreed upon by the PCO and contractor.

Table 3.2 – Task Assignment Proposal Thresholds/Schedules

Contract Type Task Assignment Funding

Threshold Proposal Submittal Schedule

FFP, FPIF, CPFF

CPIF and/or

FFP LOE

≤ Truth In Negotiations Act

(TINA) Threshold Within 30 working days

> TINA Threshold Within 45 working days

T&M N/A Within 7 working days

Note: Proposal submittal schedule may be accelerated or extended at the discretion of the PCO. The contractor may earn incentives or disincentives according to the incentive plan document attached to task assignments.

Task

Assignment

Category

Typical Task Assignment Characteristics

Urgent

a. Support to Class A, B and C Safety Investigation Boards and resolution of mishap board recommendations;

b. Evaluation/Correction of immediate safety-of-flight or work stoppage issues;

c. Resolution of issues that could affect the reliability, maintainability or availability of the fleet within the next 6 - 12 months;

d. Completion of any program/project designated by the customer as crucial to the upgrade and/or sustainment of the weapon system

Routine

a. Resolution of issues that could affect the reliability, maintainability or availability of the fleet in the out-years

b. Development of processes or procedures that improve the long term maintenance/supportability of the weapons system;

c. Completion of routine, day-to-day, projects that maintain the operational readiness, supportability, and sustainment of the fleet

3.1.1.5.2 The contractor shall mark all contract deliverables in accordance with the Contract Data

Requirement (DD1423) as attached to the specific Task Assignment. All data markings shall be in accordance with the applicable Federal Acquisition Regulation/Defense Federal Acquisition

Regulation Supplement (FARs/DFARs).

3.1.1.6 Task Assignment Revisions

3.1.1.6.1 Unexpected, unplanned or unforeseen events can result in the need to obtain additional funding and/or schedule extensions for active Task Assignments. The contractor shall comply with the applicable clauses to request additional funding for cost reimbursable or T&M Task

Assignments. The contractor shall submit request for schedule extensions to the PM, COR, and

PCO. Only the PCO can obligate the government, direct work, change contractual requirements, or approve additional funding or schedule changes. In the event the Contractor implements a change at the direction of an individual other than the PCO, the change will be considered to have been made without official authority. Approved changes to existing Task Assignments will be authorized and placed on contract via a modification authorized by the PCO.

3.2 Performance Requirements

The contractor shall accomplish each task assignment using accepted engineering practices and principles. The contractor shall apply the accepted principles/rules of Reliability &

Maintainability; Reliability Centered Maintenance, System Safety (per MIL-STD-882E), Hazardous Materials and Ozone Depleting Chemicals; Human Engineering, Cybersecurity, and

System Engineering as defined and directed by each specific Task Assignment.

3.2.1 Personnel Requirements

3.2.1.1 The contractor shall be responsible for the selection, staffing, hiring, training, expertise, assignment of duties, reassignment of duties, transfer, supervision, management, control, and termination of Contractor employees to perform all work In Accordance With (IAW) this PWS.

The contractor shall ensure contractor employees required to communicate with government personnel can read, write, and speak English to effectively communicate with the government.

The Contractor shall obtain contractor’s badges to allow unescorted entry onto Tinker AFB or

Common Access Cards (CAC) to allow access to government databases as required to complete the requirements of this PWS or a specific non-recurring Task Assignment. The contractor shall work with appropriate government sponsors to obtain these identification badges. Issuance of

CACs will require completion of National Agency Checks (NAC) with written inquiries in accordance with AFI 31-501 and AFI 31-501_AFGM2016-01. Legacy Tanker Program Office in-house Contractor personnel shall hold a Secret or higher security clearance.

3.2.1.2 Personnel, material and equipment may be required to support laboratory testing, in-plant quality control, electronic data processing, and logistics as specified in this PWS.

3.2.1.3 When attending meetings with government personnel, the contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification.

Additionally, during telephone conversations and in formal or informal written correspondence, the contractor personnel shall appropriately identify themselves as contractor employees.

3.2.2 Reserved

3.2.3 Reserved

3.2.4 Access to Government Systems

Access to government data systems such as Reliability and Maintainability Information Systems

(REMIS), GO81, Joint Reliability Availability Management System (JRAMS) or its replacement

AFFIRM, DO-43, Joint Engineering Data Management Information and Control Systems

(JEDMICS), Air Force Safety Automated System (AFSAS), Defense Automatic Addressing

System Center (DAASC) Automated Message Exchange System (DAMES), Secure Internet

Protocol Router (SIPR), etc.) may be required to execute the requirements of task assignments initiated under this PWS. Accordingly, the contractor shall initiate actions to gain access to the appropriate systems as required by individual Task Assignments. Access to REMIS, GO81, JRAMS DO43, and Joint Engineering Data Management Information and Control Systems

(JEDMICS) will require a favorable NACI investigation; access to AFSAS and SIPR will require a SECRET security clearance. The appropriate government sponsor will assist the contractor in gaining access to these systems, including obtaining a CAC (reference Paragraph 3.2.1.1), as required. (Note: For the purposes of this PWS, JEDMICS shall be considered as the only drawing data base that reflects the current configurations of the C/KC-135 systems/components.)

3.2.5 Materials, Supplies, and Services

The contractor shall be responsible for procurement of materials, supplies, services, etc. required for accomplishment of projects subject to the terms of this PWS. The contractor shall not be required to: (1) furnish labor for the modification, maintenance, or repair of aircraft, components, accessories, equipment, or software other than those required for accomplishment of this PWS, and Task Assignments or (2) fabricate or purchase items of hardware or software for use on the fleets, other than those required for accomplishment of this PWS and Task Assignments.

3.2.6 Program Documentation

All records, files, documents, and work papers generated by the contractor during execution of a

Task Assignment shall be marked and delivered with appropriate data rights markings in accordance with the CDRL or applicable DFARS at the closure of the Task Assignment.

3.2.7 Software/System Integration Laboratory

The contractor shall maintain, possess, and have access to Software/System Integration

Laboratory(s) (SIL) for the purposes of development and sustainment of Block 40, Block 45 and other modifications for use on C/KC-135 aircraft.

3.2.8 In-sourcing Requirements

During execution of this PWS, the government may determine it is in their best interest to in-source some of the work historically accomplished by the contractor under this PWS. The contractor may be requested as a separate Contract Line Item Number (CLIN) to assist in determining/recommending the type and quantity of workload that could be transitioned back to the government based on manpower, skill levels, expertise, access to proprietary data, availability of automated computer tools, etc. required to effectively and efficiently execute it.

3.2.9 Use of Ozone Depleting Substances (ODCs)

The contractor shall not use Class I ODCs during the fabrication, manufacture, and/or procurement of any prototype parts, components, items, subassemblies or assemblies required to comply with the requirements of a task assignment authorized under this PWS. If this is not feasible, submit a request to waive this requirement on a case-by-case basis for review and coordination by Legacy Tanker Division

3.2.10 Mission Essential Services

No services provided under this PWS are considered essential during crisis situations in accordance with DFARS 252.237-7023.

3.2.11 Markings and Legends

3.2.11.1 All deliverables (i.e., drawings, briefing charts, analyzes, reports, T.O. source data, T.O.

changes, etc.) to recurring and nonrecurring tasks accomplished under this PWS shall be marked with appropriate legends in accordance with the applicable FARs/DFARS; however, if any data that is to be provided to the government under this PWS cannot be delivered in accordance with the CDRL, the contactor shall stop work immediately and notify the Contracting Officer's

Representative (COR) in Legacy Tanker Division for further direction. (CDRL A005, E001)

3.2.11.2 Documentation developed under this PWS, whether produced in hard-copy or in digital format, shall be marked IAW AFI 16-201. In particular, the contractor shall ensure all engineering and technical information (i.e. information relating to research, development, engineering, testing, evaluation, production, operation, use, and maintenance for military products, services, and equipment for military systems) is marked with Distribution Statement A, B, C, D, E or F as appropriate. (CDRL A001, B004)

3.3 Recurring Engineering Services Requirements

Recurring services are activities performed on a continuing basis to ensure continued mission effectiveness and operation. The contractor shall ensure the recurring services are accomplished effectively and timely in accordance with the requirements of the PWS. The contractor shall perform the following recurring engineering services:

3.3.1 Recurring Mission Support

3.3.1.1 Contractor Engineering Support

The contractor shall provide, at a minimum, two full time liaison engineers (one Software

Systems Engineer and one Systems Engineer) to support Tinker AFB and be the focal point for all C/KC-135 technical efforts. The liaison engineers shall:

a. Assist the C/KC-135 Avionics Sustaining Engineering Services Program Manager in providing timely responses and assistance. This includes technical and non-technical responses, and support from all contractor engineering disciplines.

b. Support the government in responding to questions and tasks related to discrepancies, corrections, enhancements, deficiencies, and modifications of C/KC-135 Software and

Avionics Systems.

c. Support the preparation/update of C/KC-135 sustainment Modification Airworthiness

Certification Criteria (MACC) analyses per AFI 62-601 and MIL-HDBK-516C by supporting project teams as Subject Matter Experts (SMEs) to identify C/KC-135 Airworthiness

Certification impacts and compliance requirements. (CDRL A007)

d. Support maintenance of the change request database for all fielded configurations of C/KC-

135 software and provide AFLCMC/WLT with copies of the change request database content as required to support data gathering.

e. Provide government with recommendations for implementing software change requests into planned Operational Flight Program (OFP) releases.

f. Coordinate with project teams to ensure Automated Computer Program Identification

Number System (ACPINS) is updated for all developmental/fielded software configurations.

Note: This requires obtaining and maintaining an active Automated Computer Program

Identification Number System (ACPINS) account.

g. Provide support for government Program Reviews and other government required meetings, either in person or via telecom as coordinated with Program Office.

h. Travel to assist in technical support to any location directed by the government shall be

IAW Cost Reimbursable CLIN.

i. Provide technical assistance to the on-site sustaining engineering avionics technician for

Depot support at Tinker AFB, OK to address system inquiries, troubleshooting assistance, and overall engineering support.

j. If, in order to perform liaison services in this PWS away from contractor facilities, the government will provide access/use of a desk, telephone, copy machine, fax machine, and computer as required. When required to work at a government installation other than Tinker

AFB, the contractor shall notify the COR if work space or equipment is required.

k. Liaison personnel located on-site at a government facility shall observe a normal work week of 40 hours, eight (8) hours a day during normal duty hours Monday through Friday except for vacations, sick days, base closures, or Federal Holidays. For government planning purposes, the contactor shall provide a notice at least 48 hours prior to the start of the holiday.

Additionally, the contractor shall determine the work schedule/work location for their employees affected by base closure days. Teleworking may be authorized at the discretion of the COR or Contracting Officer. When approved, the contractor shall maintain the same level of professional conduct and communications as if working in person and shall also ensure all work is fully supported as if working in person.

l. When on-site at a government facility, the contractor employees shall follow the direction of government employees in regards to emergency procedures, i.e., fire, tornado, active shooter and bomb threats. It is the responsibility of the contractor to provide guidance and establish procedures for responding to an emergency for their employees and to account for their employees following an emergency evacuation. Contractor personnel shall participate with government personnel in all fire and tornado drills at no additional cost to the government.

3.3.1.2 On-Site Sustainment Engineering Support

The contractor shall provide one full-time avionics technician to provide technical engineering assistance on-site at AFLCMC/WLT, Tinker AFB OK to support sustainment of the C/KC-135 avionics systems and their related subsystems and components. In particular, this technician shall:

a. Analyze and disposition avionics-related AFMC Form 202s, Nonconforming Technical

Assistance Requests and Replies, generated during completion of Programmed Depot

Maintenance (PDM) on C/KC-135 aircraft. The objective is to provide signature approval on

75% of the 202s within 1 day of submission and 85% of the 202s within 2 working days of submission. The AFMC Forms 202 shall be evaluated, dispositioned, and coded in accordance with Legacy Tanker Division Operating Instruction 21-109 and AFMCI 21-301.

The cognizant technician shall also attend status meetings, production meetings, etc. to discuss the status or disposition of any AFMC Form 202 as required.

b. Complete Engineering Technical Assistance Requests (ETARs) submitted by C/KC-135 field units for resolution of avionics related issues. The objective for the contractor is to provide first engineering disposition on 75% of the 107s within 1 working day of submission and 85% of the 107s within 2 working days of submission. The cognizant technician shall also attend meetings to discuss the status or disposition of any 107 as required.

c. Assist Legacy Tanker Division engineers in responding to e-mails, telephone calls, faxes, etc. dealing with avionics-related maintenance issues from C/KC-135 depot and/or field locations. Responses shall be provided in a period consistent with the needs of the requestors.

d. Support evaluation of mission planning system changes and mission flight data changes, and assist in coordination with contractor on impacts to avionics hardware/software.

e. Support evaluation of avionics hardware/software changes and assist in coordination with contractors on impacts to mission planning system and mission flight data.

f. The contractor shall provide repair information for all repeat 202s (dispositions with the same repair used to repair two or more identical or similar defects in a 1 year period) in contractor format to Legacy Tanker Division. (CDRL A001)

g. Travel to assist in technical support to any location directed by the government shall be

IAW Cost Reimbursable CLIN.

h. Attend engineering meetings, section work flow and WLT group ventures. Work with cognizant Item Manager, Equipment Specialist, Program Manager, Logistician, and Engineer as an IPT team member for project and questions from the field/PDM/PO.

3.3.1.3 Fuel Management Performance System/Flight Performance Algorithm

The contractor shall provide support for the C/KC-135 Avionics System Fuel Management

Performance System (FMPS), Flight Performance Algorithm (FPA) and associated iPad and PC calculators. Periodic software updates are required to adapt to changes and sustain integration with the overall KC-135 Flight Management System (FMS). Work will be detailed in a monthly technical report. (CDRL A001)

3.3.1.3.1 The contractor shall prototype FMPS and FPA changes, with PO concurrence for prototype FMPS/Operation Flight Program (OFP) updates.

3.3.1.3.2 The contractor shall prototype IOS-based calculator changes, with PO concurrence for prototype iPad Operating System (IOS) updates.

3.3.1.3.3 The contractor shall prototype PC-based FMPS and FPA calculator changes, with PO concurrence for prototype PC-Based calculator updates.

3.3.1.3.4 The contractor shall maintain a roadmap of current and future FMPS and FMPS calculator software/hardware configurations.

3.3.1.3.5 The contractor shall review all deficiency reports, problem reports, and incident reports pertaining to the FMPS and FPA and provide recommendations to the PO.

3.3.1.3.6 The contractor shall review Flight Manual Review Conference (FMRC) actions and

Crew Station Working Group (CSWG) actions pertaining to the FMPS, FPA and calculators and provide recommendations to the PO.

1368987901C Sticky Note Marked set by 1368987901C

3.3.1.3.7 The contractor shall perform detailed analysis and provide a report for specific problems, when requested by the Contracting Officer's Representative (COR), for detailed analysis updates.

3.3.1.3.8 The contractor shall develop and build prototype designs to verify corrective actions for problems/deficiencies, when requested by the COR, for prototype designs.

3.3.1.3.9 The contractor shall resolve day-to-day issues identified by C/KC-135 field users and/or PO engineers to maintain the current operational capability of the current C/KC-135 fuel management system and associated calculators.

3.3.1.3.10 The contractor shall conduct a technical interchange meeting quarterly (TIM). (CDRL

B002, B003).

3.3.1.4 Technical Order Sustainment

3.3.1.4.1 The contractor shall provide Technical Order (T.O.) sustainment services required to maintain the currency and accuracy of the legacy tanker avionics maintenance manuals as requested by the PCO or a COR, according to Table 3.3. Per 00-5-3 Technical Order (TO), the term TO is equivalent to the DoD term Technical Manual. The delivered T.O. source data shall be accurate and free from typographical and grammatical errors. (CDRL E001)

Table 3.3 – Tech Order Sustainment Services

T.O

Category

Definition

Category A Prepare change packages associated with routine, non-modification related, T.O. changes

Category B Initial and or final incorporate verified, modification related, source data packages as requested by the PCO or a COR. Note The government will provide digital copies of each Category B source data package delivered to the contractor for T.O. incorporation. Illustrations will be in Computer Graphics

Metafile (CGM), Initial Graphics Exchange Specification (IGES), or Raster format and text will be in Microsoft Word or SGML format

Category D Prepare unique T.O. services as requested by the PCO or a COR

Additional

Services

Provide Technical Order conference support, both in-plant and out-plant, as requested by the COR and approved by the PCO. (CDRL E001 TM-86-01R)

3.3.1.4.2 The contractor shall prepare change packages IAW MIL-STD-38784A. The contractor shall deliver text and graphics IAW MIL-STD-1840C in SGML format. The contractor shall deliver direct image copies as requested by the PCO or a COR.

3.3.1.4.3 The contractor shall maintain the master files (reproduction media) for the avionics series maintenance manuals as requested by the PCO or a COR. The master digital files of text and illustrations shall be held and stored at the contractor’s facility until such time the government requests delivery.

3.3.1.4.4 When required, the contractor shall develop and deliver Technical Manual (TM) source data to the level of technical manual requirements. The levels of TM Source Data are defined as follows:

a. Level I: Formal Technical Order changes, developed by the Technical Publications organization by Contractor and reviewed/approved by the government prior to delivery;

b. Level II: Technical Order formatted source data developed by the Technical Publications organization by Contractor from engineering data;

c. Level III: Data from a non-Publications organization or changes to existing art pages generated by the Technical Publications organization by Contractor. Source data may not meet current Technical Order format requirements and may be provided in multiple formats;

d. Level IV: Redlined markups to existing Technical Order pages, simple typed text/tables, internal reports or unformatted data. If not specified on the Task Assignment the contractor will provide data in Level III format. Delivered Technical Manual Source data to the level of technical manual requirements which are accurate and free from any typographical/grammatical errors.

3.3.2 Recurring Technical Support

3.3.2.1 Avionics Integrity Program Support

The contractor shall provide engineering/technical support to assist the Legacy Tanker Division in maintaining the Avionics Integrity Program (AVIP) for all Electrical, Communications and

Avionics systems, subsystems, equipment and components of the aircraft. To accomplish the intent/objectives of these programs, the contractor shall comply with the developed AVIP processes and procedures and the Avionics Integrity Program Master Plan. Components being replaced by the C/KC-135 Block 45 will be subjected to safety analyses and evaluations. , i.e., these components will be exempt from reliability, service life, and life cycle assessments as well as Analytical Condition Inspections (ACIs) and solution development activities. Specifically, the contractor shall:

3.3.2.1.1 Identify/appoint a single Point of Contact (POC) for support of the AVIP and any alternate(s) who shall act for the contractor when the POC is absent to Legacy Tanker Division in writing within two working days after contract award. These POCs shall support proper planning, scheduling, visibility, control, and performance of the C/KC-135 AVIP. The POCs shall also provide requests to proper organizations within the contractor’s facility and assist in planning/programming Task Assignments to ensure timely actions and responses to Air Force requirements.

3.3.2.1.2 Specific tasks to be accomplished shall be determined by mutual consent of the contractor and the government AVIP focal point. Examples include reviewing applicable avionics, communication, and electrical Work Unit Codes (WUC) in the -06 manual 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. Additionally, the contractor shall continue to work and monitor the status of open actions tracked by the AVIP. (CDRL A002)

3.3.2.1.3 The contractor shall provide engineering/technical support to assist the C/KC-135

Program Manager in maintaining the AVIP for all avionics, communications and electrical systems, subsystems, equipment and components of the C/KC-135 aircraft. To accomplish the intent/objectives of these programs, the contractor shall comply with the previously-developed

AVIP processes and procedures and the C/KC-135 Mechanical Equipment and Subsystems

Integrity Program (MECSIP) and Avionics Integrity Program (AVIP) Master Plan.

3.3.2.1.4 Assist AVIP in the maintenance of an accurate and current prioritized Critical

Components Lists (CCLs) for safety-critical, mission-critical and durability-critical avionics system components using the established AVIP prioritization methodology for safety, reliability, availability, Total Non-Mission Capable for Maintenance (TNMCM), aborts, inherent failures and cannibalization actions. Provide the updated avionics components for the CCL to the government AVIP in conjunction 3.3.2.1.10.

3.3.2.1.5 For avionics components where Mean Time Between Failure Type I (MTBF-1) falls below 80% of the established Mean Acceptable Performance (MAP) value, assist in the issuance and evaluation of CCL performance degradation alerts for those components with a validated degradation correlation that include recommendations for continued monitoring or further assessment.

3.3.2.1.6 Maintain a prioritized list of all avionics candidate initiatives improving safety or reliability, maintainability, and availability (RM&A) of current avionics systems, subsystems, equipment or components. The list shall include a recommendation whether or not serially tracking system components is appropriate based on the particular situation (include with quarterly report IAW 3.3.2.1.10).

3.3.2.1.7 Accomplish AVIP analyses on specific C/KC-135 avionics systems anomalies and/or deficiencies identified through AVIP monitoring and assessment, aircraft mishaps, Material

Safety Task Group (MSTG) recommendations, Product Improvement Working Group (PIWG) action items, Avionics/Electrical Working Group (AEWG), Engineering Investigation

Deficiency Reports/Product Quality Deficiency Reports (EIDR/PQDRs), as requested by the government AVIP focal point. Specific efforts that may be accomplished under this effort include Reliability Assessments, Risk Assessments, Service Life Assessments, and Life Cycle

Assessments as defined in previous AVIP meetings. (CDRL A002)

3.3.2.1.8 Develop complete technical data packages for the solutions identified above requested by the government AVIP focal point for further development. Completion of these technical data packages may require the development of Product Drawings and Associated Lists, generation of T.O. source data for affected manuals, fabrication and installation of prototype parts, completion of laboratory and/or flight tests, generation of engineering supporting data such as System Safety Analyses, Certification Basis and Compliance Reports, structural analyses, and electrical load analyses, development of draft Time Compliant Tech Orders (TCTOs), providing source data for completion of Recommended Change, as required by the specific situation. The level of T.O. source data to be delivered to the government (i.e., Level I, Level II. Level III, or

Level IV) will be appropriate to the solution being implemented as determined by the AVIP focal point. All prototype efforts will be addressed in individual task assignments. Provide the technical data packages with all supporting documentation upon their completion in interim letters. Additionally, provide a digital copy of all drawings changes generated as a result of this effort. (CDRL A002, A003, A005, A007, E001)

3.3.2.1.9 Support and attend meetings for Product Improvement Working Group (PIWG), Dash

06 and 6 Reviews, Avionics/Electrical Working Group (AEWG), Crew Station Working Group

(CSWG), Aircraft Information Program (AIP), Aircraft Maintenance Requirements Document

(AMRD), Software Working Group (SWWG), System Safety Working Group (SSWG) and

System Safety Group (SSG) as requested by the government AVIP focal point. Additionally, conduct Technical Interchange Meetings (TIMs)/Working Group Meetings (WGMs) as required to review the status and acceptability of efforts being accomplished under this task and to obtain

Air Force concurrence to close efforts that have been completed under this task.

3.3.2.1.10 Provide a Quarterly Summary detailing the efforts accomplished for the preceding three months (this requirement is not met by the monthly Systems Engineering reports, this is a summary of all tasks covered in tasks defined in 3.3.2.1.1 - 3.3.2.1.19 (CDRL A003)

3.3.2.1.11 Develop and maintain an AVIP library with all pertinent documentation generated during the performance task. (CDRL A003)

3.3.2.2 Aircraft Support

The contractor shall provide engineering/technical assistance to support depot/field maintainers on a daily basis for routine/urgent response tasks. Responses and closing actions for post-production aircraft support issues shall be technically sound, complete and accurate and provided in timeframes meeting customer requirements. Support shall be provided in the following two areas: Aircraft Support responses/closing actions are technically sound, complete and accurate and are provided in a timeframe that meets customer requirements.

3.3.2.2.1 The contractor shall provide a 24-hour a day, 7 days a week focal point for in-flight emergency assistance via telephone to crews and technical personnel assuring responsive actions.

The contractor shall provide the name and telephone number for 24 hour Point of Contact (POC) to the PCO within five (5) working days of contract award. The contractor shall provide technical assistance to AF operating unit’s safety offices and to AFLCMC/WLT for routine engineering questions relative to in-flight emergencies and flight safety issues. (CDRL A001)

3.3.2.2.2 The contractor shall address Respond to Technical Inquiries (RTIs) submittals concerning avionics system issues from AFLCMC/WLT program managers, engineers and technical specialists, depot and/or field maintenance activities, operational units, or flight test/safety centers, etc. The RTIs will be directed by a PCO or a COR for submittal and tracking.

The contractor shall also provide engineering assistance for short term projects that can be completed at or below the Simplified Acquisition Threshold (SAT) as authorized by the PCO or a COR to maintain or potentially improve the day-to-day maintenance and operational effectiveness of the C/KC-135 aircraft fleet. These less-than-SAT projects include tasks that fall under the general categories of Paragraphs 3.4.1 through 3.4.13 and (a) and (b) below:

(a) Review and evaluate Service Bulletins (SBs), Airworthiness Directives (ADs), Service

Letters (SLs), Structural Item Interim Advisories (SIIAs) and Special Airworthiness Information

Bulletins (SAIBs) for applicability to the C/KC-135 aircraft and provide recommended actions for fleet implementation if required to accomplish the intent of these commercial aircraft documents. Update the AVIP library to document actions accomplished for any airworthiness/service publication review.

(b) Review and evaluate government-Industry Data Exchange Program (GIDEP) alerts and establish contractual vehicles as required to secure access to vendor/supplier proprietary engineering specification, drawings, blueprints and/or other data required to complete the requirements of this PWS. (CDRL A001)

3.3.2.3 Crew Station Working Group

The contractor shall host and participate in all Crew Station Working Group (CSWG) meetings to review corrective actions, corrections to equipment defects, maintenance upgrades, etc. for compliance with all environmental, operational, ergonomic and human factor requirements. This is required to ensure all solutions/decisions recommended by the CSWG are consistent and compatible with existing/planned aircraft avionics/electrical system architectures.

The contractor shall host, in coordination with the government CSWG chairman and focal liaison, two (2) CSWG meetings to be conducted each year during the period of performance

(PoP). The contractor shall maintain a database of the CSWG action items to include status and resolution. The database will be briefed by the contractor to the government on a semi-annual basis. The updated database and list of attendees (in spreadsheet form) will be provided to the government, within 45 working days after each CSWG. All meetings will be hybrid (virtual and in-person), pending the approval by the COR. In-person meetings shall be one in the Oklahoma

City area and one in the vicinity of the contractor’s facility. (CDRL A004, A009, B001, B002, B003)

3.3.2.4 Reserved

3.3.2.5 Program Management Reviews and Technical Interchange Meetings

3.3.2.5.1 The contractor shall conduct two (2) Program Management Review (PMR) meetings during the PWS period of performance to review the status of all open Task Assignments under the contract. The reviews shall include detailed information to allow a thorough understanding of the “health” of each Task Assignment. For each Task Assignment, the detailed information shall include a list of the tasks completed with date completed, list of uncompleted task with estimated completion date, past and projected spend plan, and any identified cost, schedule, and performance risk to complete Task Assignment. These PMRs shall be conducted at the contractor’s facility. The schedule of these PMRs and the formats for the briefing charts provided at the reviews shall be determined by government and contractor representatives. The contractor shall provide meeting minutes within 10 working days of the review. (CDRL B001, B002, B003)

3.3.2.5.2 The contractor shall submit monthly status reports during the PWS period of performance. The contractor shall also conduct status meetings during the PWS period of performance to review open Task Assignments under the contract. The reviews shall include information (such as individual Task Assignment cost, schedule, and performance) to allow an understanding of the “health” of each Task Assignment. These meetings may be conducted via telecom, primarily, but attendance at the contractor’s facility may occur, as coordinated between the contractor and government. The format of the briefing charts provided shall be determined by government and contractor representatives. The contractor shall track action items assigned during these meetings. (CDRL B002, B003, B004)

3.3.2.5.3 The contractor shall conduct formal TIMs as specified in each individual Task

Assignment initiated under this PWS. Purpose of these TIMs is to review the status/acceptability of efforts accomplished under each particular task and to obtain Air Force approval to close efforts under that task. Time and location of the TIMs will be determined in in each task assignment. The contractor shall prepare agendas, minutes, and presentation materials for these

TIMs as required. (CDRL B001, B002, B003)

3.3.2.6 Telephone Logs, Status Reports and Closing Letters

3.3.2.6.1 The contractor (or sub-contractor(s), as appropriate) shall provide a log of all recurring tasks/efforts associated with responses to telephone inquiries from depot/field activities and contractor engineers to include title, engineer assigned, requesting organization, and action taken. (CDRL B004).

3.3.2.6.2 For CPFF, FPIF, and T&M Task Assignments only, the contractor shall provide monthly financial status reports throughout the duration of this contract. (CDRL B004)

3.3.2.6.3 The contractor shall provide closing letters (Contract Summary Report) for all non-recurring Task Assignments accomplished under this PWS. (CDRL A001, A005, A006, B007, E001)

3.3.2.7 Contractor Manpower Reporting

3.3.2.7.1 Contractor shall report contract services in accordance with Defense Federal

Acquisition Regulation Supplement 252.204-7023, Alternate 1. The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields in the Service Contract Report (SCR) at www.SAM.gov

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 each http://www.sam.gov/ calendar year Contractors may direct questions to the SAM.gov service desk

(https://www.fsd.gov/fsd-gov/home.do)."

*Reporting Period: Contractors are required to input data by 31 October of each year.

Uses and Safeguarding of Information: Information from the secure web site 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.

User Guide: Data for Air Force service requirements must be input at www.sam.gov. A quick start user guide is available at on the SAM.gov website at https://sam.gov/SAM/transcript/SCR_QSG.pdf. In addition, a full user guides for contractors and government personnel are available at https://www.sam.gov/SAM/pages/public/help/samUserGuides.jsf.

3.3.2.8 Systems Engineering Management Plan (SEMP)

The contractor shall maintain a Systems Engineering Management Plan…