PWS_KC_135_ASES_CY16_R4_(2).docx

AFLCMC/WKDA-PWS-14-018

15 Sep 14

PERFORMANCE WORK STATEMENT

FOR

C/KC-135 Avionics Sustaining Engineering Services (ASES)

CY16

AFLCMC/WKDA-PWS-14-018

15 September 2014 Revision 4 – 28 Jan 15

Prepared by

AFLCMC/WKDA

3001 Staff Dr. Ste 2AC489

TINKER AFB OK 73145

Table of Contents

SECTION I – DESCRIPTION OF SERVICES

1.0 INTRODUCTION

1.1 Background

Over the last 15 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 was begun 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. It will culminate with the addition of Block 45 to the KC-135s which will include new autopilot, flight director, radar altimeter and electronic engine instruments displays and is scheduled to occur from 2014 to 2023. 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. Based on this, the organic/government engineers within 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 codes 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 from a qualified contractor to accomplish recurring and nonrecurring engineering services to support maintenance and sustainment of C/KC-135 aircraft avionics systems. This 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 codes 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.

1.3 Scope

This Performance Work Statement (PWS) describes all 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 (maintenance engineering). The -135 series aircraft encompassed by this PWS include all variants of C/KC-135 aircraft including the KC-135R/T, OC-135B, RC-135S/U/V and FMS versions of the aircraft. Technical and program direction for this PWS are provided under the direction of the Legacy Tanker System 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 and 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. The contractor shall also have access to or possession of a complete set of Technical Orders 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 below 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 PCO within ten (10) working days after receipt of an updated publication. The contractor shall not implement any publication changes until approved by the PCO.

INACTIVE for new designs

3.0 AVIONICS SUSTAINING ENGINEERING SERVICES REQUIREMENTS

3.1 General Requirements

3.1.1 Engineering Assignments

3.1.1.1 EA Definition

Engineering Assignments (EAs) will be used to authorize non-recurring engineering support services under this PWS. An EA is a Legacy Tanker Division developed form that identifies the problem, defines the work to be accomplished, specifies due dates and 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). The recurring services will involve well defined, short term, repetitive efforts that require continuing and continuous contractor action; non-recurring services will involve less well defined, longer term, peculiar efforts.

3.1.1.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 Material (T&M) efforts. 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.

3.1.1.3 EA Execution

The contractor shall fulfill the requirements of specific task assignments as designated in individual Engineering Assignments (EAs). The contractor shall provide the resources to accomplish all requirements of this PWS within the specified cost and schedules. The contractor shall ensure that all work accomplished under this PWS is compliant with their in-house quality management program.

3.1.1.4 EA Priorities

EAs will be used to authorize work under this PWS irrespective of funding type; i.e., CPFF, FFP, or T&M. All EAs will be assigned a priority of either Routine or Urgent based on the nature of the issue. Characteristics of Routine and Urgent EAs are as follows:

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

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 EA Proposal Submittals

3.1.1.5.1 For EAs funded as FFP and CPFF efforts, the contractor shall submit formal cost/schedule proposals to the PCO in accordance with the table below. For EAs funded as T&M efforts, the contractor shall submit informal estimates of EA cost and schedule to the PCO accompanied by a table that delineates the cost by EA paragraph in accordance with the table below. The formal/informal proposals (including cost table) shall be submitted in a format agreed upon by the PCO and contractor.

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

3.1.1.5.2 During review and or proposal preparation for all EAs, the contractor shall determine whether or not the engineering/technical data (drawings, briefing charts, analyzes, reports, T.O. source data, etc.) that will be delivered as part of the EA will be marked with proprietary data/limited rights legends in accordance with the applicable FARs/DFARs. This determination will be reflected in a ground rule on every EA prior to its authorization. If, during execution of an individual EA, it is determined that deliverables that were originally agreed to be marked as unlimited data are to be marked with proprietary data/limited rights legends, the contractor shall stop work immediately on the EA and notify the government of this data legend marking change. The Government will then determine whether or not to proceed with the EA.

3.1.1.6 EA 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 EAs. To request changes to current EAs, the contractor shall submit formal change proposals for additional funding for CPFF EAs and/or schedule extensions for FFP and CPFF EAs to the PCO in a format agreed upon by the PCO and contractor. For T&M EAs, the contractor shall coordinate the additional funding and/or schedule extensions with the AFLCMC/WKDMA Sustaining Engineering Program Manager and Procurement Contracting Officer (PCO) for concurrence and approval. All approved changes to existing EAs will be authorized and placed on contract via a modification authorized by the PCO.

3.1.1.6.2 The PCO is the only person authorized to direct work or change contractual requirements. The PCO is the only individual who can obligate the Government. 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.

3.2 Performance Requirements

The contractor shall accomplish each engineering assignment using accepted engineering practices and principles. The contractor shall consider and 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, and System Engineering as defined and directed by each specific engineering 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 IAW this PWS. The contractor shall ensure contractor employees required to communicate with Government personnel can read, write, and speak English. 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 EA. 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 dated 28 Apr 13.

3.2.1.2 The contractor shall provide qualified engineering/technical personnel in performing the activities outlined in this PWS. A full range of engineering skills in avionics systems design and integration, software development, test, liaison engineering, and safety engineering are required to accomplish the requirements of this PWS. In addition, 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 Subcontractors

In performing the requirements of this PWS, the contractor may be required to obtain unique services and/or hardware from approved system, subsystem, and equipment manufacturers.

3.2.3 Remote Duty Assignments

3.2.3.1 In conjunction with performing services away from the contractor’s plant, the Government will provide access/use of a desk, telephone, copy machine, fax machine, and computer as required.

3.2.3.2 Contractor 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, or holidays allocated by the contractor to their employees. Additionally, the contractor shall determine the work schedule/work location for their employees affected by base closure days.

3.2.3.3 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.2.4 Access to Government Data Systems

Access to Government data systems (REMIS, GO-81, Long Term Health Monitoring System (LtHMS), DO-43, JEDMICS, AFSAS, etc.) may be required to execute the requirements of EAs initiated under this PWS. Accordingly, the contractor shall initiate actions to gain access to the appropriate systems as required by individual EAs. Access to REMIS, GO81, LtHMS, DO43 and JEDMICS will require a favorable NACI investigation; access to AFSAS 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 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 and the specific EAs. 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 EAs, or (2) fabricate or purchase items of hardware or software for use on the fleets, other than those required for accomplishment of EAs.

3.2.6 Program Documentation

All records, files, documents, and work papers generated by the contractor during execution of an EA shall be marked and delivered with appropriate data rights to the PCO at the closure of the EA as outlined in the DFARs.

3.2.7 Software/System Integration Laboratory

The contractor shall develop, possess or have access to a Software/System Integration Laboratory (SIL) for the purposes of development and sustainment of Block 40, Block 45 and other modifications and upgrades to software for use on C/KC-135 aircraft.

3.2.8 Insourcing Requirements

During execution of this PWS, the government may determine that it is in their best interest to insource some of the work historically accomplished by the contractor under this PWS. In that case, contractor may be requested 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 O-Zone 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 that are required to comply with the requirements of an EA 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 approval by AFLCMC/WKDA.

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 AFLCMC/WKDA for further direction.

3.2.11.2 All documentation developed under this PWS, whether produced in hard-copy or in digital format, shall be marked IAW AFI 61-204. In particular, the contractor shall ensure that 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.

3.3 Recurring Engineering Services Requirements

Recurring Services are activities performed on a continuing basis to ensure continued mission effectiveness and operation and are aided by daily and effective contractor response and execution. 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 (Firm Fixed Price Tasks)

3.3.1.1 Contractor Engineering Support

The contractor shall provide, at a minimum, a full time liaison engineer for support located in Cedar Rapids, IA, to be the focal point for all C/KC-135 technical efforts. The liaison engineer shall:

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

(b) Provide support and be in attendance at Government/Contractor Program Reviews. Attend one PMR quarterly in Oklahoma City, Oklahoma, and support other PMRs by telecom.

(c) Travel to assist in technical support to any location directed by the Government.

(d) Provide technical on-site Depot assistance in Oklahoma City, Oklahoma for one week per quarter to address system inquiries, troubleshooting assistance, and overall engineering support. The dates for each quarterly visit will be provided to and agreed upon by the Government by the 3rd calendar day of each quarter (Jan 3, April 3, Jul 3, Oct 3).

3.3.1.2 Systems Engineering Management Plan (SEMP)

The contractor shall update the contractor’s Systems Engineering Management Plan (SEMP) generated during the ASES Bridge contract as required for use in the performance of requirements for all EAs initiated under this PWS. The contractor shall ensure OSS&E in accordance with (IAW) Air Force Policy Directive (AFPD) 63-12, AFI 63-101/20-101, Air Force Materiel Command Instruction (AFMCI) 63-1201, and the guidance provided in MIL-HDBK-514 are addressed in the updated SEMP. The requirements of this updated SEMP, in conjunction with the Government’s System Engineering Plan, shall be complied with during integration assessments, studies, and reviews impacting systems or components on the C/KC-135 aircraft. (DI-MGMT-81024 CDRL 009).

3.3.1.3 On-Site Sustainment Engineering Support

The contractor shall provide one full-time avionics technician to provide technical engineering assistance on-site at AFLCMC/WKD, 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 desired goal (although not mandatory) is to provide signature approval on 75% of the 202s within 1 day of submission and 85% of the 202s within 2 days of submission. The AFMC Forms 202 shall be evaluated, dispositioned, and coded in accordance with AFLCMC/WKD Operating Instruction 21-109 and AFMCMAN 21-1. 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 desired goal (although not mandatory) is to provide first engineering disposition on 75% of the 202s within 1 day of submission and 85% of the 202s within 2 days of submission.

(c) Assist AFLCMC/WKDA 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 time frame 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) Finally, the technician 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 AFLCMC/WKDN. (DI-ADMN-80447A/T CDRL 004)

3.3.1.4 Interface Control Working Group Support

The contractor shall provide technical and management support for the Interface Control Working Group (ICWG) to ensure an orderly and compatible integration of on-going and future programs. As part of this effort, the contactor shall maintain and update baseline system integration requirements documentation and baseline space layout drawings and antenna layouts of the aircraft. The contractor shall also determine compatibly of all on-going and future modifications, identify any incompatibilities between modifications and provide recommended solutions to resolve the incompatibilities. (DI-MISC-80508B/T CDRL 005)

3.3.1.5 Technical Order Sustainment

3.3.1.5.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. The delivered T.O. source data shall be accurate and free from typographical and grammatical errors. The contractor shall:

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

b. Initial and final incorporate verified, modification related, source data packages as requested by the PCO or a COR (Category B). 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 CGM, IGES, or Raster format and text will be in Microsoft Word or SGML format;

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

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

3.3.1.5.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.5.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.2 Recurring Technical Support (Cost Plus Fixed Fee Tasks)

3.3.2.1 Avionics Integrity Program Support

The contractor shall provide engineering/technical support to assist the Legacy Tanker Division in maintaining a proactive and effective 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 (AIMP). Components being replaced by the C/KC-135 Block 45 will be subjected to analyses/evaluations that have safety implications, 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 AFLCMC/WKDA 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 requests to proper organizations within the contractor’s facility and planning/programming of EAs to ensure timely actions and responses to Air Force requirements.

3.3.2.1.2 Assist in developing a plan and support completion of tasks included in MIL-STD-1796 Table 1 Summary of AVIP Requirements. Specific tasks that will 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. (DI-MISC-80508B/T CDRL 005)

3.3.2.1.3 The contractor shall provide engineering/technical support to assist the C/KC-135 System Program Manager in maintaining a proactive and effective Weapon Systems Integrity Program (WSIP) and Avionics Integrity Program (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 WSIP processes and procedures and C/KC-135 Weapon Systems Sustainment WSIP and AVIP Master Plans.

Notes: WSIP integrates avionics, mechanical, structural and propulsion integrity programs to ensure sound engineering tools, processes and practices are integrated at the system level to sustain the weapon system’s operational safety, suitably and effectiveness (OSS&E).

3.3.2.1.4 Assist WSIP/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 FSIP 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 FSIP focal point at least once annually. (DI-MISC-80508B/T CDRL 005)

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 that will improve safety or 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. (DI-MISC-80508B/T CDRL 005)

3.3.2.1.7 Accomplish AVIP analyses on specific 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), etc. 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. (DI-MISC-80508B/T CDRL 005)

3.3.2.1.8 Develop complete technical data packages for the solutions identified above that are 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 Technical Order (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, TACC/MACC analyses, structural analyses, and electrical load analyses, development of draft TCTOs, providing source data for completion of AFMC Forms 252, etc. 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. For any prototype effort, the Government will provide all maintenance personnel, aircraft access, standard test equipment, bench stock items, etc.; the contractor will provide onsite support and part kits. 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. (DI-MISC-80508B/T CDRL 005, DI-SESS-81000C CDRL 006, TM-86-01N, CDRL 007)

3.3.2.1.9 Support and attend meetings for AAIP, Product Improvement Working Group (PIWG), Dash 06 and 6 Reviews, Avionics/Electrical Working Group (AEWG), Cockpit Working Group (CWG), Aircraft Information Program (AIP), Aircraft Maintenance Requirements Document (AMRD), and System Safety Group (SSG) as requested by the Government AVIP focal point. Additionally, conduct TIMs/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. The report shall be due the 10th of the month following the last month in the quarter. In addition, provide the Government AVIP focal point with a quarterly briefing package for senior leaders by the 24th of the month following the last month in the quarter. (DI-MISC-80508B/T CDRL 005)

3.3.2.1.11 Develop and maintain an AVIP library with all pertinent documentation generated during the performance task. The AVIP library shall be searchable and include historic files, track recommendations, and be accessible by the Government AVIP members.

3.3.2.2. Post Production Aircraft Support

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

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/WKD for routine engineering questions relative to in-flight emergencies and flight safety issues. (DI-ADMN-80447A/T CDRL 004)

3.3.2.2.2 The contractor shall Respond to Technical Inquiries (RTIs) concerning avionics system issues from AFLCMC/WKD program managers, engineers and technical specialists, depot and/or field maintenance activities, operational units, or flight test/safety centers, etc. The contractor shall also provide engineering assistance for short term projects that can be completed in 250 hours or less 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-250 hour projects include tasks that fall under the general categories of Paragraphs 3.4.1 through 3.4.13. Specific tasks the contractor shall accomplish under this PWS paragraph are as follows:

(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 -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. (DI-MISC-80508B/T CDRL 005)

3.3.2.3 Cockpit Working Group

The contractor shall participate in all Cockpit Working Group (CWG) meetings to review all 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 CWG are consistent and compatible with existing/planned aircraft avionics/electrical system architectures. The contractor shall also attend other technical/engineering meetings, conferences, seminars, etc. as requested and maintain liaison with subsystem contractors and AFLCMC/WKD engineers and equipment specialists to monitor current or planned cockpit hardware/software changes that may impact future sustainment efforts. The contractor shall maintain a database of the CWG action items to include status and resolution. The database will be briefed by the contractor to the Government on a quarterly basis. The database (in spreadsheet form) will be provided to the Government quarterly. For planning purposes, the contractor shall assume that two (2) yearly CWG meetings will be conducted during the PWS period of performance. (One official meeting and one by telecom). For planning purposes, the meetings will be held in the Tinker AFB vicinity. (DI-MISC-80508B/T CDRL 005)

3.3.2.4 Sustainment of Avionics System Components Intentionally Left Blank

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 meetings during the PWS period of performance to review the status of all opened EAs under the contract. The reviews shall include detailed information (such as individual EA spend plans, current cost and schedule status, potential problem areas, etc.) to allow a thorough understanding of the “health” of each EA. These PMRs shall be conducted at the contractor’s Midwest City, OK, facility. The frequency 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. (DI-ADMN-81249A CDRL 001 and DI-ADMN-81250A CDRL 002)

3.3.2.5.2 The contractor shall conduct formal Technical Interchange Meetings (TIMs) as specified in each individual EA 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 by the contractor. The contractor shall prepare agendas, minutes, and presentation materials for these TIMs as required. (DI-ADMN-81249A CDRL 001 and DI-ADMN-81250A CDRL 002)

3.3.2.6 Telephone Logs, Status Reports and Closing Letters

3.3.2.6.1 The contractor 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. This log shall be initially provided by the 10th calendar day after the first full month following contract award with subsequent submittals due by the 10th calendar day of each month thereafter. (DI-MGMT-80227/T CDRL 003).

3.3.2.6.2 For CPFF and T&M EAs only, the contractor shall provide monthly financial status reports throughout the duration of this contract. The first report shall be provided by the 17th calendar day after the first full month following contract award with subsequent reports due by the 17th calendar day of each month thereafter. (DI-MGMT-80227/T CDRL 003)

3.3.2.6.3 The contractor shall provide closing letters for all non-recurring EAs accomplished under this PWS. The closing letters shall be received by the government within 15 working days of the closing date on the EA. The closing letter will be delivered in contractor format and will include as attachments all required, technical reports, laboratory reports, trip reports, damage assessments, technical order source data, drawings, software version descriptions, etc. requested in the EA. (DI-ADMN-80447A/T CDRL 004, DI-MISC-80508B/T CDRL 005, DI-SESS-81000C CDRL 006, TM-86-01N CDRL 007, and/or DI-IPSC-81442A CDRL 008)

3.3.2.7 Contractor Manpower Reporting

3.3.2.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 United States Air Force 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.3.2.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 each calendar year (30 Oct 14 for FY14 labor data). Contractors may direct questions to the Contract Manpower Reporting Application (CMRA) help desk.

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

3.3.2.7.4 Data for Air Force service requirements must be input at the Air Force CMRA link. User manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

3.4 Non-Recurring Engineering Services Requirements

The contractor shall perform the activities as requested in individual EAs to sustain the Operational Safety, Suitability and Effectiveness of the legacy tanker fleet and its FMS counterparts. These activities require the developmental, production and maintenance efforts outlined in Section 1 and are directly related in ensuring that the legacy tanker fleet accomplishes its mission requirements. The contractor shall utilize a systems engineering approach for all design and integration efforts in meeting the technical requirements of the EAs initiated under this PWS. Additionally, the contractor shall ensure that Engineering Assignments (EAs) are completed within originally authorized cost and schedule estimates. The contractor shall perform the following activities as required in the individual EAs:

3.4.1 Aircraft Mishap and Incident Investigations

The contractor shall participate in investigations of mishaps/incidents and provide engineering support, coordinate analyses and evaluation of causes, and formulate recommendations for the elimination of conditions responsible for such occurrences as defined by an EA. This shall include dispatching appropriately trained engineering personnel for on-site support to Safety Investigation Boards (SIBs) and providing in-plant support when requested by either the Air Force investigators or the Contractor’s representatives at the mishap site. To support this requirement, the contractor shall ensure that potential advisors to SIBs are technically trained and medically prepared to support worldwide mishap investigations. (DI-MISC-80508B/T CDRL 005)

3.4.2 Engineering and Technical Assistance

The contractor shall provide technical assistance to installation sites and United States Air Force units to investigate, troubleshoot and resolve problems which affect safety-of-flight, maintenance, installation and/or operation of legacy tanker avionics systems and/or avionics-related Peculiar Ground Support Equipment as directed through individual EAs. The contractor shall document all technical information/assistance required to resolve the issues. (DI-MISC-80508B/T CDRL 005)

3.4.3 On-Site Liaison Engineers - Intentionally Left Blank

3.4.4 Hardware and Software Development/Sustainment

The contractor shall perform hardware and software development/sustainment as directed through individual EAs. Design drawings shall be in accordance with ASME Y14.100-2004, MIL-T-31000, and the CDRL to the level as specified in the EA. When the type drawings (Level) are not specified in the EA, the contractor shall request that the cognizant AFLCMC/WKD technical representative provide specific direction. The contractor shall provide all software modifications (maintenance support and Operational Flight Programs (OFP)), unless specifically required by the individual EA, IAW the method of development and level of documentation used for prior software development. The contractor shall provide new software IAW best commercial practices unless defined otherwise in the individual EA. The new or upgraded ground and/or flight software must execute as required in accordance with the individual EA requirements. The contractor shall provide the updated database and software programs for the aircraft as directed by individual EAs. (DI-MISC-80508B/T CDRL 005, DI-SESS-81000C CDRL 006 and/or DI-IPSC-81442A CDRL 008)

3.4.5 Prototyping of Hardware/Software Changes

When required by the EA, the contractor shall develop/fabricate/produce/provide hardware and software for the purpose of design confirmation, ground/flight test, and/or validation and verification as directed through individual EAs. The contractor shall prepare and verify a TCTO to document the design. (TM-86-01N CDRL 007)

3.4.6 Test Procedures

The…