PWS_BoeingESSContract_CY16_Final_3Mar15.docx

AFLCMC/WKDAC-PWS-14-015

3 Mar 15

PERFORMANCE WORK STATEMENT

FOR

C/KC-135 ENGINEERING

SUSTAINMENT SUPPORT (ESS)

CY16

AFLCMC/WKDAC-PWS-14-015

3 Mar 15

Prepared by

AFLCMC/WKDAC

3001 Staff Dr. Ste 2AC489

TINKER AFB OK 73145

Table of Contents

SECTION I – DESCRIPTION OF SERVICES

1.0 INTRODUCTION

1.1 Background

As the System Program Management office for the C/KC-135 Weapon System, the Legacy Tanker Division (AFLCMC/WKD) has the responsibility to maintain/sustain the day-to-day operations and safety of the United States Air Force (USAF) C/KC-135 fleet and its Foreign Military Sales (FMS) variants and to ensure their long term viability and effectiveness. This requires accomplishing widely diverse engineering/technical activities including responding to field/depot problems, resolving in-flight emergencies, supporting safety investigations, completing engineering studies, accomplishing aircraft damage assessments, developing repair/rework procedures, ensuring the accuracy and adequacy of C/KC-135 technical orders as well as a multitude of other tasks. For the most part, organic/government engineers within AFLCMC/WKD accomplish these activities; however, many tasks require the knowledge, expertise, experience, and specialized engineering capabilities of a qualified contractor who has access to historical military/commercial-related aircraft design data, C/KC-135 proprietary/limited rights drawings and C/KC-135 engineering/technical data to effectively and efficiently complete. In short, the support/assistance of a qualified contractor through this Engineering Sustainment Support PWS is essential in maintaining the Operational Safety, Suitability and Effectiveness (OSS&E) of the USAF C/KC-135 fleet and its FMS variants from now through their retirement.

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 the C/KC-135 fleet. This shall include systems engineering support, detailed design engineering, design change analyses, system and subsystem integration, technical analyses, liaison engineering support, stress analyses, 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 must have expertise in all aspects of C/KC-135 design, structures, engineering, configuration, sustainment, aerodynamics, propulsion, electronics, hardware, support equipment and system integration. The contractor must obtain access to C/KC-135 design, engineering, qualification, test, reliability, and configuration data. The contractor must also possess suitable facilities, tools, equipment, and personnel to provide all C/KC-135 sustaining engineering services.

1.3 Scope

This Performance Work Statement (PWS) describes all the requirements necessary to provide Sustaining Engineering Services for the sustainment of the C/KC-135 Weapon System including its airframe and airframe components and mechanical/electrical systems, subsystems and their components. The PWS requirements are associated with maintaining the C/KC-135 aircraft as a viable platform for the USAF and its FMS customers 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) for C/KC-135 series aircraft, associated training devices, and support systems. The -135 series aircraft encompassed by this PWS include all variants of the C/KC-135 including KC-135R/T, OC-135B, RC-135S/U/V, and FMS aircraft. Technical and program direction for this PWS are provided under the direction of the Legacy Tanker Division Program Manager, AFLCMC/WKD.

2.0 APPLICABLE DOCUMENTS

2.1 Access

The Contractor shall have access to or possession of all C/KC-135 aircraft design, engineering, qualification, test and reliability and configuration data (including all proprietary and limited rights drawings and technical data) for the C/KC-135 aircraft and its variants. The contractor shall also have access to or possession of a complete set of Technical Orders for the C/KC-135 aircraft including maintenance manuals (-2s), Structural Repair manual (-3s), Illustrated Parts Breakdown manuals (-4s), 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.

Table 2.0-1: Applicable Document Table

3.0 ENGINEERING SUSTAINMENT SUPPORT REQUIREMENTS

3.1 General Requirements

3.1.1 Engineering Assignments

3.1.1.1 Definition

Engineering Assignments (EAs) will be used to authorize engineering support services under this PWS. An EA is an AFLCMC/WKD 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 Materials (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. Typical characteristics of Routine and Urgent EAs are shown in Table 3.1-1 below.

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

Table 3.1-1: EA Categories

3.1.1.5 EA Proposal Submittals

For EAs funded as FFP and CPFF efforts, the contractor shall submit formal cost/schedule proposals to the PCO in a format agreed upon by the PCO and contractor. 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. The cost table shall be provided in contractor format. The proposals shall be submitted to the Government in accordance with the time frames outlined in Table 3.1-2 below. Fully funded positions (i.e., program managers, contracts personnel, single points of contact, etc.) shall not separately charge for any efforts expended in support of proposal preparation.

Table 3.1-2: EA Proposal Submittal Time Frames

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

3.1.1.6 EA Revisions

3.1.1.6.1 Unexpected, unplanned or unforeseen events can result in the need to obtain additionally 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 Engineering Sustainment Support 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 and/or the C/KC-135 Weapon Systems Sustainment MECSIP and FSIP Master Plan), 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 visitor badges to allow unescorted entry onto Tinker AFB or Common Access Cards (CACs) 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 airframe design, aircraft systems, aerodynamics, software, structures, 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. It is desirable, but not required, that flight crews/boom operators be current to accomplish the tasks outlined in this PWS unless specifically required by an EA.

3.2.1.3 When attending meetings with Government personnel, the contractor employees shall identify themselves as contractor personnel by introducing themselves or begin 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 entry to the place of duty and access/use of a desk, telephone, copy machine, fax machine, computer and Tinker internet 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 recurring and/or nonrecurring tasks initiated under this PWS. Accordingly, the contractor shall initiate actions to gain access to the appropriate systems as required by individual tasks. 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 CACs (reference Paragraph 3.2.1.1) (Note: For the purposes of this PWS, JEDMICS shall be considered as the only drawing data base that reflects the current configurations of KC-135 systems/components. Other drawing data bases, such as Boeing’s REDAR system, may not contain the latest drawing changes incorporated on the KC-135 weapon system by USAF engineers).

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 135 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 135 fleet, 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 will be marked and delivered with appropriate data rights to the PCO at EA as outlined in the DFARs.

3.2.7 Technical Review Meetings

3.2.7.1 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 jointly by the contractor and Government EA focal point. The contractor shall prepare agendas, minutes, and presentation materials for these TIMs as required. (DI-ADMN-81249A, CDRL 002 and DI-ADMN-81250A, CDRL 003)

3.2.7.2 The contractor shall conduct informal Working Group Meetings (WGMs) as specified in each individual EA initiated under this PWS. Purpose of these WGMs is to review the status/acceptability of efforts accomplished under each particular task and to resolve any issues/problem areas with the EAs at the working level before presentation of the EA results to management. Time and location of the WGMs will be determined jointly by the contractor and Government EA focal point.

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 (ODSs)

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/WKDAC.

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 with unlimited rights, the contactor shall stop work immediately and notify the Contracting Officer Representative (COR) in AFLCMC/WKDMA 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 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 Single Point of Contact

The contractor shall provide a single Point of Contact (POC) for management of projects and any alternate(s) who shall act for the contractor when the POC is absent to the contracting officer in writing within two working days after contract award. These POCs shall ensure proper planning, scheduling, visibility, control, and performance of the C/KC-135 Sustaining Engineering Services contract. The POCs shall also channel requests to proper organizations within the contractor’s facility and plan/program all EAs to ensure timely actions and responses to Air Force requirements.

3.3.1.2 Systems Engineering Management Plan (SEMP)

The Contractor shall prepare and deliver an updated version of the Systems Engineering Management Plan (SEMP) generated during the basic year of this contract (FY11) as required for use in the performance requirements of all EAs initiated under this PWS. The Contractor shall ensure that OSS&E is addressed in accordance with (IAW) AFI 63-101/20-101 in the updated SEMP. The requirements of this updated SEMP shall be complied with during integration assessments, studies, and reviews impacting systems or components on the C/KC-135 aircraft. (DI-MGMT-81024 CDRL 001).

3.3.1.3 On-Site Liaison Engineering Support for OC-ALC A/C Maintenance Line

The contractor shall provide up to 8 man-years of structures and/or systems liaison engineering/technical support on-site at OC-ALC, Tinker AFB OK to analyze and disposition structural/systems-related AFMC Form 202s, Nonconforming Technical Assistance Requests and Replies, generated during completion of Programmed Depot Maintenance (PDM) or Unprogrammed Depot Level Maintenance (UDLM) on C/KC-135 aircraft. The desired goal (although not mandatory) is to provide first and second engineering signatures on 75% of the 202s within 1 working day of submission and 85% of the 202s within 2 working days of submission with the number of 202s being worked (Work in Progress (WIP)) not exceeding 20. The AFMC Forms 202 shall be evaluated, dispositioned, and coded in accordance with AFLCMC/WKD Operating Instruction 21-109 and AFMCMAN 21-1. The engineers shall also attend status meetings, production meetings, etc to discuss the status or disposition of any AFMC Form 202 as required. Finally, the engineers 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-MISC-80508B/T CDRL 006)

3.3.1.4 On-Site Liaison Engineering Support for OC-ALC Backshops

The contractor shall provide up to 1.25 man-years of liaison engineering/technical support on-site at OC-ALC, Tinker AFB OK to analyze and disposition AFMC Form 202s, Nonconforming Technical Assistance Requests and Replies, generated during repair or overhaul of structural components and Management of Items Subject to Repair (MISTR) items in the AFMC backshops. For the purposes of this PWS, backshops shall include the flight controls shop, the boom shop, the 2-level engine shop or any other maintenance shop where KC-135 parts/assemblies are overhauled and/or repaired. The desired goal (although not mandatory) is to provide first and second engineering signatures on 75% of the 202s within 1 working 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 AFLCMC/WKD Operating Instruction 21-109 and AFMCMAN 21-1. Additionally, the engineer shall support AFSC process improvements initiatives such as lean events, rapid improvement events, benchmarking, best practices, technical studies, etc. The engineer shall also interface with backshop personnel to determine the adequacy of existing overhaul Statements of Work (SOWs) and recommend/generate SOW changes required to improve the quality/durability of overhauled items. Finally, the engineer shall generate repair/overhaul SOWs to support unprogrammed overhaul actions. (DI-MISC-80508B/T CDRL 006)

3.3.1.5 Conversion of Duplicate AFMC Form 202 Dispositions into Permanent Technical Order Repair Procedures

The contractor shall convert the repair dispositions from duplicate 202s into Level III T.O. source data suitable for inclusion in the appropriate C/KC-135 Technical Orders. These 202s will be provided to Boeing at the rate of approximately 5 each month from a list of potential candidate duplicate 202s maintained by AFLCMC/WKDN. If the repair procedures dictate a need for formal drawing changes/updates, the contractor shall also generate and release appropriate Advanced Drawing Change Notices (ADCNs). Additionally, appropriate stress/structural analyses shall be accomplished on each repair to ensure its damage tolerance and durability. Each of the repair procedures shall: (a) Include damage limitations that encompass reasonable and expected damage for any component or structural element addressed in the AFMC Form 202; (b) Include repair procedures that are permanent or at least acceptable without additional inspection/evaluation from PDM to PDM; (c) Be thorough, complete and easily understood by journeyman aircraft and/or sheetmetal mechanics; (d) Include all material, fastener, and miscellaneous hardware requirements; and (e) To the maximum extent possible, use only stocklisted and available parts. The contractor shall provide the new procedures to the Government for tabletop validation/verification and/or prototyping on an aircraft undergoing PDM; any changes or lessons learned during the validation/verification or prototyping efforts will be incorporated in the T.O source data prior to delivery to the Government. (DI-MISC-80508B/T CDRL 006)

3.3.1.6 Evaluation of Commercial 7X7 Airworthiness/Service Publications for C/KC-135 Applicability

3.3.1.6.1 The contractor shall review and evaluate new/revised 707, 727, 737-100/200/300/400/500 and 747-100/200 Service Bulletins (SBs), Airworthiness Directives (ADs), Service Letters (SLs), Structural Item Interim Advisories (SIIAs) and Special Airworthiness Information Bulletins (SAIBs) that are non-operator specific (and therefore proprietary to that operator) for applicability to the –135 aircraft and provide recommended actions to the –135 fleet to accomplish the intent of these commercial aircraft documents. This review/evaluation shall be accomplished in two phases as follows:

(a) Phase 1: For every commercial service publication, the contractor shall determine whether the publication is Applicable - Recommended, Applicable - Not-Recommend or Non-Applicable – Not-Recommended for implementation on the C/KC-135. Definitions of these publication categories shall be as follows: (1) Applicable – Recommended: Intent of service publication has direct relevance to the C/KC-135 aircraft, regardless of originating aircraft type, and should be incorporated into the C/KC-135 aircraft; (2) Applicable – Not Recommended: Intent of service publication has direct relevance to C/KC-135, regardless of originating aircraft type, but the C/KC-135 aircraft has specific configurations/current procedures that negate the need to incorporate it; and (3) Non-Applicable – Not Recommended: Intent of service publication has no direct relevance to C/KC-135, regardless of originating aircraft type. Additionally, for each service publications reviewed/evaluated, the contractor shall provide (1) a summary of the subject addressed within the service publication and/or a brief description of the changes made by any revision, (2) a justification to support the contractor’s determination of service publication applicability to the C/KC-135 aircraft (the “how” and “why’), and (3) a qualitative Mishap Risk Assessment (MRA) for Applicable – Recommended items. The contractor shall notify the Government by e-mail within 4 hours of receiving an AD and shall provide the initial evaluation within 3 working days; the contractor shall notify the Government by e-mail within 3 working days of receiving any other service publication listed above and shall provide the initial evaluation within 10 working days. Notification to the Government and posting of all correspondence concerning the airworthiness/service publications can be accomplished through the contractor’s MATRIX system in lieu of e-mail if desired. (DI-MISC-80508B/T CDRL 006)

(b) Phase 2: For up to six commercial service publications identified by the Government for further evaluation, the contractor shall provide the following additional information: (1) List of all affected Technical Orders or Manuals; (2) Brief description of the accomplishment instructions; (3) Threshold for inspection/modifications and repetitive intervals for inspections (both commercial and Air Force equivalent); (4) Man-hours required to accomplish the inspection and/or modification as listed within the service information publication; and (5) Quantitative Mishap Risk Assessment (MRA) in accordance with Mil-Std-882E identifying the risk of operating the C/KC-135 fleet until implementation of the mitigating actions outlined in the service publication. The contractor shall provide this additional information within 10 working days of being requested to develop it. The contractor’s MATRIX system may be used to notify the Government when Phase 2 evaluations are completed if desired. (DI-MISC-80508B/T CDRL 006)

3.3.1.6.2 The contractor shall develop one complete technical data packages for mitigating actions for any commercial service publication as requested by the Government and approved by a COR. Completion of this technical data package 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, generation of engineering supporting data such as System Safety Analyses, TACC/MACC analyses, structural analyses, and electrical load analyses, or development of a draft TCTO as required by the specific situation. (DI-MISC-80508B/T CDRL 006)

3.3.1.6.3 The contractor shall provide a focal point to support AFLCMC/WKDAC in coordinating the identification of commercial 7X7 airworthiness/maintenance requirements documents for C/KC-135 applicability and tracking the development and implementation of any engineering and maintenance actions required to mitigate them. The focal point shall also maintain and update at least quarterly a master schedule of all documents reviewed by the contractor and their current status. (DI-MISC-80508B/T CDRL 006)

3.3.1.7 Maintenance of C/KC-135 Inspection Requirements Documents

The contractor shall provide inputs concerning T.O. 1C-135-6 corrections, additions and clarification which are submitted from C/KC-135 field units on AFTO Forms 22 and coordinate recommended approvals/disapprovals answers for them with the approval/disapproval authority within AFLCMC/WKDAC. Specifically, the contractor shall:

3.3.1.7.1 Review AFTO Forms 22 for proposed changes, updates and revisions to the C/KC-135 inspection technical orders (T.O. 1C-135-6 and all associated workcards), Work Unit Code manual (1C-135-06), and Equipment Inventory List technical order (1C-135-21), conduct preliminary evaluations of them and route proposed changes, updates and revisions to the appropriate approving authority. The AFTO Forms 22 will be provided to the contractor by the AFLCMC/WKDAC T.O. 1C-135-6 point of contact. Evaluation of these changes shall be completed within 48 clock hours from receipt of AFTO Forms 22 for emergency requests, 10 calendar days for urgent requests and 45 calendar days for routine requests. (DI-MISC-80508B/T CDRL 006)

3.3.1.7.2 Prepare AFMC Form 252, T.O. Publication Change Request, for each specific technical order change and any T.O. source data or supporting documentation required to be submitted with them. Forward copies of the AFMC Form 252 and supporting documentation to the Technical Content Manager (TCM) for incorporation into the T.O. The 252 forms shall be completed within 60 calendar days of identifying that a change to a publication is required. (DI-MISC-80508B/T CDRL 006)

3.3.1.7.3 Update/maintain the currency of the C/KC-135 Inspection Requirements Document (IRD) with new/revised maintenance inspection requirements. Data sources used for updating the IRD will include, as a minimum, Airworthiness/Service Publication reviews, ASIP details, FSIP findings, ACI details, PDM SOW and T.O. 1C-135-6. Only routine changes to these documents will be incorporated into the IRD; updates to the IRD resulting from substantial/extensive changes to these documents (i.e., complete re-write of Dash 6 manual, re-organization of depot maintenance cycle into a 4-yr/8-yr PDM program, etc.) will be accomplished as a stand-alone efforts on follow-on EAs. (DI-MISC-80508B/T CDRL 006)

3.3.1.8 Interface Control Working Group Support

The contractor shall provide 1 man-year of technical and management support to assist the AFLCMC/WKDM ICWG focal point in executing/maintaining an Interface Control Working Group (ICWG) to ensure an orderly and compatible integration of on-going and future programs for the C/KC-135 weapon system. The ICWG shall comply with the requirements of AFLCMC/WKD OI 20-004, Interface Control Working Group, and AFLCMC/WKD OI 21-001, Configuration Management, Configuration Control Board (CCB), including but not limited to, maintaining/updating baseline system integration requirements documentation and baseline space layout drawings of the aircraft, determining compatibly of all on-going and future modifications, identifying any incompatibilities between modifications, and providing recommended solutions to resolve the incompatibilities. The contractor shall also accomplish other tasks within the scope of AFLCMC/WKD OI 20-004 and AFLCMC/WKD OI 21-001 as requested by the AFLCMC/WKDM ICWG focal point. (DI-MISC-80508B/T CDRL 006)

3.3.1.9 Maintenance/Sustainment of Historical Files and Electronic Databases

3.3.1.9.1 The contractor shall maintain a historical file of fleet support records such as interim letters, closing actions, status reports, funds reports, etc. The contractor shall also maintain paper and electronic records on safety issues in order to retrieve information on past incidents.

3.3.1.9.2 The contactor shall sustain/maintain the Multiple Application for Technical Resources and Information Xchange (MATRIX) electronic database, including its hardware components and software, to allow storage and retrieval of EA documentation (Statements of Work, interim letters, closing letters, deliverables, etc.) and Team Spirit information and accomplish programmatic functions needed to execute the requirements of this PWS. Improvements and/or upgrades MATRIX shall be accomplished as required to maintain its currency, and functionality.

3.3.1.9.3 The contractor shall maintain C/KC-135 engineering/technical data files at the contractor’s facility as specified in a specific EA. This file shall consist of both Boeing developed data and data provided by the Air Force.

3.3.1.10 Program Management Meetings

3.3.1.10.1 The contractor shall conduct monthly Continuous Quality Improvement (CQI) meetings to review the status of all EAs with scope, cost, or schedule problems, all immediate or urgent EAs, and any other special subjects deemed appropriate by the government or contractor. Time and place of the meeting and format for any briefing charts provided during the reviews shall be at the discretion of the contractor. Most meeting attendees will participate in this meeting in a face-to-face conference room setting; however, it is permissible for some attendees to participant in the meetings through WebEx, by telecom, or through other electronic means to eliminate TDY/travel costs.

3.3.1.10.2 The contractor shall conduct Program Management Reviews (PMRs) to review the status of all opened EAs under the contract. The reviews must 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 will be conducted up to four times annually at the contractor’s Oklahoma City, OK, facility. Formats for the briefing charts provided at the reviews shall be determined by government and contractor representatives before the meetings. The contractor shall provide meeting minutes within 10 working days of the review. (DI-ADMN-81249A, CDRL 002 and DI-ADMN-81250A, CDRL 003)

3.3.1.11 Telephone Logs, Status Reports and Closing Letters

3.3.1.11.1 The contractor shall maintain a log of all 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 will be provided on a quarterly basis. (DI-MGMT-80227/T, CDRL 004).

3.3.1.11.2 For CPFF and T&M EAs only, the contractor shall provide a monthly financial status report (first report due 40 calendar days after contract award with subsequent reports due every 30 calendar days thereafter, due by the 10th of the month) throughout the duration of this contract. (DI-MGMT-80227/T, CDRL 004)

3.3.1.11.3 The contractor shall provide a Technical Order Status and Schedule (TOSS) report, in contractor format, on a monthly basis. (DI-MGMT-80227/T CDRL 004)

3.3.1.11.4 The contractor shall provide closing letters for all non-recurring EAs accomplished under this PWS. The closing letters must be delivered to 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, etc requested in the EA. In addition, all closing letters and their attachments shall be posted to MATRIX within 30 working days of their release. (DI-ADMN-80447A/T CDRL 005, DI-MISC-80508B/T CDRL 006, DI-SESS-81000C CDRL 007)

3.3.1.12 Contractor Manpower Reporting

3.3.1.12.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..1.12.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.1.12.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.1.12.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.3.1.13 Engineering Drawing/Data Management

3.3.1.13.1 When requested by the Government, the contractor shall incorporate AFLCMC/WKD generated AF IMT 3925s (Engineering Order), AF IMT 3926s (Engineering Order - Continuation Sheet) and/or AF IMT 3927s (Engineering Order – Parts List Changes) into the C/KC-135 master drawings maintained by Boeing. In order for Boeing to be added to the Air Force’s distribution list for these AF Forms 2600 and AF Forms 1662, Boeing shall provide the name and e-mail address of the POC to receive these documents within 10 working days of contract award. When this information is incorporated into engineering drawings through advancement of the drawing revision letter, copies of the revised drawing(s) shall be furnished in accordance with the CDRL. (DI-SESS-81000C CDRL 007)

3.3.1.13.2 When requested by the Government, the contractor shall provide reference service to AFLCMC/WKD including furnishing (1) legible copy of any data under paragraph 3.3.1.14.1. Requests for such data will be limited to that required by AFLCMC/WKD for engineering review and in-house engineering projects. Data furnished to the Air Force under this requirement shall be furnished as copies on paper and, in addition to any legends appearing on the data, marked with an appropriate legend indicating that the data is being furnished for the purpose of engineering consulting or problem analysis and is to be destroyed upon completion of the engineering assignment under which the data was furnished. (DI-MISC-80508B/T CDRL 006)

3.3.1.13.3 The contractor shall submit digital copies of updated/revised C/KC-135 drawings not already being delivered under other taskings or EAs to the Joint Engineering Data Management and Control System (JEDMICS) office at Tinker AFB OK. The updated drawings shall be delivered on a monthly basis. (DI-SESS-81000C CDRL 007)

3.3.1.14 Voluntary Protection Program (VPP)

3.3.1.14.1 TAFB, OK, is in the process of pursuing VPP recognition or has already been recognized under the Occupational Safety and Health Act (OSHA) Voluntary Protection Plan (VPP). VPP impacts all "applicable contractors" operating on AF Installations. (applicable contractors are contractors that have completed 1000 hours or more at TAFB, OK, within three (3) months on the same contract.) It is the contractor's responsibility to ensure its employees and managers have a comprehensive understanding of VPP and are in full compliance with OSHA requirements (Public law 91-596). The contractor shall follow the safety and health rules of the installation and OSHA. Detailed information on VPP is available on the OSHA website at http://www.osha.gov/dcsp/vpp/index.html.

3.3.1.14.2 Definitions:

a. Applicable Contractors: Contractors whose employees work more than 1000 hours per quarter on a Government installation.

b. Days Away, Restricted, and/or Transfer Case Incident Rate (DART): Number of recordable injuries and illness cases per 100 full-time employees resulting in days away from work, restricted work activity, and/or job transfer that a site has experienced in a given time frame.

c. Total Case Incident Rate (TCIR): Total number of recordable injuries and illness cases per 100 full-time employees that a site has experienced in a given time frame.

3.3.1.14.3 The contractor shall submit a Safety and Health Plan (SHP) and corresponding site safety checklist to the Program Office PCO, PM, and COR ten (10) business days after contract award. The contractor's SHP shall include appropriate measures to ensure the contractor reacts promptly to investigate, correct and track alleged safety and health violations and uncontrolled hazards in the contractor’s work areas. The contractor shall comply with the contractor’s SHP. The SHP shall

a. Identify processes and procedures used to track compliance with the SHP, and the process and procedures that shall be used to correct violations;

b. Demonstrate a management commitment to employee safety and health and shall identify the application of the SHP to subcontractors, if applicable;

c. Identify the roles and responsibilities of the following individuals; management, supervisors, employees and safety coordinator;

d. Identify applicable safety rules and regulations and shall include a worksite hazard analysis to include base-line hazard identification and required control measures;

e. Include a job site analysis to include hazard of tasks required to control…