Attach 1 ESS Follow-On PWS Draft.docx

AIR FORCE AIR DOMINANCE SYSTEMS CENTER (AFADSC)

PRESIDENTIAL AND EXECUTIVE AIRPOWER DIRECTORATE

EXECUTIVE AIRCRAFT DIVISION (EAD)

TINKER AFB, OK 73145

PERFORMANCE WORK STATEMENT

(PWS)

For

ENGINEERING SUPPORT SERVICES

PREPARATION DATE: 1 July 2025

PWS CONTROL NUMBER: PWS-27-ESS-01

CONTRACT NUMBER: FA8134-27-D-BXXX

PREPARING ORGANIZATION: AFLCMC/WVV TINKER AFB OK 73145-3020

1.0 SECTION I – OVERVIEW

This Performance Work Statement (PWS) outlines the engineering support services, both recurring and non-recurring, required to sustain and modernize specific aircraft as designated by the Government. The scope of work encompasses the following weapon systems, with the understanding that aircraft platforms, sites, and locations may be modified throughout the contract period:

1) Air Force: E-4B/747; VC-25A/747; AFMC NT-43/737; C-32A/757; C-40B/C/737; VC-25B/747 NOTE: The Government reserves the right to add, modify, or remove supported aircraft platforms and operational locations throughout the duration of this effort to accommodate evolving mission requirements.

1.1 Contractor Responsibility

The Contractor shall:

1) Execute all work requirements as specified with this PWS

2) Manage and deliver Contract Data Requirements Lists (CDRL) items in accordance with the following criteria

a. Submit all deliverables on or before specified due dates

b. Ensure accuracy and completeness of all submitted documentation

c. Comply with format and content requirements as defined in the CDRL

d. Maintain quality control standards throughout the submission process

e. Revise disapproved CDRLs within two (2) weeks of notification of unacceptance

1.2 Procuring Contracting Officer’s (PCO) Authority

The PCO is the sole authority authorized to modify or approve changes to:

1) Any requirements specified in this PWS

2) Any provisions contained within the contract

3) Any contractual terms and conditions Any modifications implemented without explicit PCO approval are:

1) Considered unauthorized

2) Made at the Contractor’s own risk

3) Subject to rejection and/or removal

4) Not eligible for compensation

5) Potentially subject to contractual remedies NOTE: Implementation of changes directed by any person other than the PCO, regardless of their position or authority level, will be considered unauthorized and outside the scope of this contract.

1.3 Calendar Days and Time Measurement

All references to “day(s)” within this PWS shall be interpreted as “calendar day(s)”—excluding federal holidays, unless otherwise stated. All timeframes are based on the official time zone of the Executive Aircraft Division, Tinker AFB.

NOTE: When the last day of a specified period falls on a weekend or Federal holiday, the period shall extend to the next business day, unless otherwise specified in writing.

NOTE: Federal holidays are as follows: New Year’s Day, Martin Luther King's Birthday, Washington’s Birthday, Memorial Day, Juneteenth National Independence Daty, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, and Christmas Day. If the holiday falls on Sunday, it is observed on Monday. If the holiday falls on Saturday, it is observed on Friday.

1.4 PLATFORM DESCRIPTIONS

1.4.1 E-4B National Airborne Operations Center

The E-4B is the National Airborne Operations Center (NAOC) for the National Command Authority (NCA) which includes the President of the United States, the Secretary of Defense and the Chairman of the Joint Chiefs of Staff (CJCS). In case of national emergency or destruction of ground command control centers, the E-4B provides a modern, highly survivable, command, control and communications center to direct U.S. forces, execute emergency war orders and coordinate actions by civil authorities. There are four E-4B aircraft in the Air Force inventory, with one constantly on alert.

The E-4B aircraft, a militarized version of the Boeing 747-200, is a four-engine, swept-wing, long-range, high-altitude airplane capable of being refueled in flight. It is equipped with the electronics, communications, and personnel and equipment required for the NAOC missions. The E-4B serves as a worldwide, survivable enduring node of the National Military Command System (NMCS) for the purpose of exercising national security responsibilities throughout the full spectrum of conflict. The E-4B has electromagnetic pulse protection, nuclear and thermal effects shielding, an electrical system designed to support advance electronics and a wide variety of communications equipment. An advanced satellite communications system allows worldwide communications among strategic and tactical satellite systems and the airborne operations center.

1.4.2 VC-25A Air Force One

The mission of the VC-25A, more commonly known as "Air Force One," is to provide senior leader air transportation for the President of the United States. The fleet consists of two specially configured Boeing 747-200 aircraft. These aircraft have been managed by Air Force Life Cycle Management Center (AFLCMC) since they were deployed in the early 90s. These aircraft provide safe, comfortable, reliable, worldwide air transport with a communications capability that provides an “office in the sky” environment. The basic airframes, engines and avionics systems are commercial-off-the-shelf (COTS) with unique mission support systems and equipment installed to support mission requirements. The basic aircraft and unique systems are maintained to Federal Aviation Administration (FAA) standards.

The contractor shall not use the VC-25A, in terminology or visually, in connection with advertisement of any system/component installed on the aircraft. The Contractor shall ensure sub-contractors also do not use the VC-25A, in terminology or visually, in connection with advertisement of any system/component installed on the aircraft.

1.4.3 NT-43A

The AFMC NT-43A aircraft is a Government owned, contractor operated Boeing 737-200 commercial derivative aircraft modified for special mission support. This aircraft was previously an AF T-43A Navigation Trainer.

1.4.4 C-32A

The mission of the C-32A is to provide senior leader transportation for the Vice President, First Lady and cabinet members. The fleet consists of four specially configured Boeing 757-200 aircraft stationed at Joint Base Andrews, MD. The C-32A provides safe, comfortable and reliable transportation for our nation’s leaders to locations around the world. Serves as an office in the sky and provides critical senior leadership mission capabilities. The basic airframes, engines and avionics systems are commercial-off-the-shelf (COTS) with unique mission support systems and equipment installed to support mission requirements.

1.4.5 C-40B

The mission of the C-40B is to provide airlift and an office in the sky for combatant commanders. The fleet is made up of four Boeing 737-700IGW commercial derivative aircraft stationed at Joint Base Andrews, MD. The basic airframes, engines and avionics systems are COTS with unique mission support systems and equipment installed to support mission requirements.

1.4.6 C-40C

The C-40C is a multi-mission aircraft providing rapid response to worldwide team travel and special air mission tasking. The primary customers are Congress and Senate members and senior military members. The fleet consists of seven Boeing 737-700IGW commercial derivative aircraft modified for senior leaders. The basic airframes, engines and avionics systems are COTS with unique mission support systems and equipment installed to support mission requirements. Three aircraft are stationed at Joint Base Andrews, MD operated by Air National Guard (ANG) and four are stationed at Scott AFB, IL and are operated by Air Force Reserve Corps (AFRC.)

1.4.7 VC-25B The Next Air Force One

The mission of the VC-25B, more commonly known as "The Next Air Force One," will provide air transportation to the President of the United States (POTUS) ensuring he/she is able to execute the duties of Head of State, Chief Executive, and Commander in Chief. The Boeing 747-8i commercial aircraft was uniquely modified to provide POTUS, staff, and guests with safe comfortable, and reliable air transport with a communications capability that provides a “flying White House” environment. The modification of these aircraft is managed by Air Force Life Cycle Management Center / WVB (AFLCMC/WVB). The modifications to the 747-8 aircraft include the following major enhancements:

a. Avionics and flight deck – military communication, navigation, and surveillance capabilities are added to the 747-8 flight deck.

b. Mission Communication Subsystem (MCS) – a new MCS is added to provide global secure/non-secure voice, data, and video communications.

c. Interior – a customized Layout of Passenger Accommodation (LOPA) is required to provide presidential accommodations, a Medical Compartment, Senior Staff Compartment, Staff Area, Guest Area, Press Area, Forward and Aft Lower Lobe stowage, and accommodations for aircrew.

d. Airframe and systems – airframe and system enhancements include electrical power upgrades, autonomous enplaning/deplaning, autonomous baggage loading, and Electromagnetic Environmental (E3) hardening.

The contractor shall not use the VC-25B, in terminology or visually, in connection with advertisement of any system/component installed on the aircraft. The Contractor shall ensure sub-contractors also do not use the VC-25B, in terminology or visually, in connection with advertisement of any system/component installed on the aircraft.

2.0 SECTION II – RECURRING ENGINEERING

The Recurring Engineering services (Section 2.1 through Section 2.4) and Technical Publications (Section 2.9) will involve continuous Contractor action and will not require additional contractual authorization or tasks for accomplishment. Government requests for services and tasks outside the funded scope of Recurring Engineering and Technical Publications are as provided for in Nonrecurring Engineering (Section 3.0).

2.1 SYSTEMS ENGINEERING

2.1.1 Systems Engineering Management Plan (SEMP)

The Contractor shall provide a Systems Engineering Management Plan (SEMP) that details the engineering processes, systems, organization and resources required to support the platforms listed in Section 1.0 of this PWS. The SEMP shall address the following:

a. Requirements analysis and management

b. Functional analysis and allocation

c. Integrated planning and scheduling

d. Technical Performance Measures (TPM)

e. Interface control

f. Baseline management

g. Technology insertion

h. Analysis, integration and test (to include system validation and verification)

i. System architecture development

(CDRL XX01)

2.1.2 Safety Management Plan

The Contractor’s safety program shall be maintained in accordance with the latest published version of MIL-STD 882. The Contractor shall develop and deliver a contractor’s safety management plan.

(CDRL XX18)

2.1.3 Safety Analysis and Reporting

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

(CDRL XX02)

2.1.4 Engineering Baseline Control and Maintenance

(Applies to: VC-25A, E-4B, C-32A, C-40B/C, and VC-25B) The Contractor shall control and maintain the engineering data baseline for the disciplines specified in Appendices D-F and M. The Contractor shall maintain the data by obtaining supplemental analyses and incorporating the data into the baseline document. The Contractor shall document the existing configuration and performance of the aircraft/system/function.

The Contractor shall update the baselines established through modifications and changes. The Contractor shall incorporate data from third party changes and modifications using data provided by the Program Office. The Contractor shall review the baselines annually or when directed. The Contractor shall analyze and make recommendations to the Program Office using the baseline data.

(CDRL XX03)

2.1.5 Reliability Maintainability and Availability (RM&A) / System Failure Analysis (Applies to: E-4B) The Contractor shall monitor RM&A, analyze and evaluate system performance, logistical health and supportability issues affecting systems, as well as operations and maintenance performance. The Contractor shall use all available data to analyze in-service systems on operational and depot possessed aircraft to determine parts usage trends and generate recommended solutions to improve RM&A and support and/or reduce costs by utilizing tools specifically developed to assist in performing those requirements (for example: System Performance Dashboard Metric, CANN Projections, Time Change Items (TCI) Reports, Windchill Risk and Reliability). The Contractor shall utilize these tools to maintain current databases and update tools as necessary to perform analysis on in-service systems. The Contractor shall respond to Program Office and field inquiries on crew and ground-reported discrepancies.

The Contractor shall have access to Maintenance Information Systems (MIS) to provide a monthly RM&A report that includes Basing & Logistics Analysis Data Environment (BLADE) and/or Logistics, Installations and Mission Support – Enterprise View (LIMS-EV) mission capable and non-mission capable rates, aircraft availability, non-mission capable drivers, system non-mission capable drivers, completed monthly activities, and current open activities as part of the monthly status report.

The Contractor shall have and maintain access to Government MIS to assist in analyzing in-service systems on operational and depot possessed aircraft (for example: BLADE, Reliability and Maintainability Information System (REMIS); Logistics, Installations and Mission Support – Enterprise View (LIMS-EV); Integrated Maintenance Data Systems (IMDS); Comprehensive Engine Management Systems (CEMS); Global Combat Support Systems – Air Force (GCSS-AF); Enhanced Technical Information Management Systems (ETIMS)) and maintaining current databases and update tools as necessary to perform analysis on in-service systems.

The Contractor shall provide R&M data and analysis support for evaluation of service literature items that are applicable to the fleet, field and depot maintenance requirements/intervals. The Contractor shall work with the Boeing DMS Process Action Team on Diminishing Manufacturing Sources and Material Shortages (DMSMS) issues on request. The Contractor shall incorporate DMSMS data from the DMS Process Action Teams if applicable into R&M analyses and corrective action recommendations. The Contractor shall attend and support program meetings intended to enhance system R&M and/or improve aircraft availability, maintenance, and mission effectiveness. The Contractor shall attend industry, DoD, and Large Data Analytics meetings/conferences to maintain awareness of R&M/DMSMS/Data Mining issues.

(CDRL XX06)

2.1.6 Reliability and Maintainability (R&M) Planning and Execution (Applies to: C-32A and C-40B/C) The Contractor shall develop and execute a platform R&M Plan that improves system reliability performance and/or reduces costs. The plan shall employ and implement new tools as needed to provide improved R&M capabilities to enhance platform support. The plan shall provide for:

· Data collection from the Government-provided and Boeing-provided sources.

· Continuing review and analysis of collected data to identify reliability, maintainability, and availability issues.

· Generation of recommendations for resolution of selected reliability, maintainability, and availability issues.

· Response to Program Office and field inquiries on crew and ground-reported discrepancies. Examples of events that may also prompt inquiries are Deficiency Reports, ETOPS and RVSM event reports, and Service Difficulty Reports.

· R&M data and analysis support for evaluation of service literature items that are applicable to the fleet on request.

· R&M data and analysis support for evaluation of maintenance requirements and intervals.

· R&M data and analysis support for Diminishing Manufacturing Sources and Material Shortages (DMSMS) issues in cooperation with the Program Office, the Contractor DMS team, and the CLS contractor.

· Incorporation of DMSMS data into R&M analyses and corrective action recommendations.

· Attendance and support of program meetings intended to enhance system R&M and/or improve maintenance effectiveness.

· Attendance of industry and DoD meetings in order to remain aware of R&M issues in the commercial fleet including Boeing Fleet Team and Working Together Meetings.

(CDRL XX06, XX12)

2.1.7 Technology Roadmap (C-32A, C-40B/C, and VC-25B)

The Contractor shall develop a Technology Roadmap for each platform. The roadmap shall include solutions to address worldwide aviation regulation changes, obsolescence, emergent issues, and existing and/or new technologies that could impact mission performance. Items on the roadmap shall be reviewed regularly and prioritized with Government Program Office input. Each item on the roadmap shall identify the notional implementation schedule along with the pertinent cost estimate data resulting from related nonrecurring engineering activities.

2.1.8 Field and Depot Level Maintenance Historical Data

(Applies to: VC-25A, E-4B, C-32A, C-40B/C, and VC-25B) The Contractor shall maintain access to the Reliability and Maintainability Information System (REMIS), Integrated Maintenance Data Systems (IMDS) or Global Combat Support Systems – Air Force (GCSS-AF) Data Services. The Contractor shall use REMIS, IMDS, GCSS-AF, or Contractor provided databases as necessary to obtain historical field and depot level discrepancy data (e.g. AFTO 349 or equivalent data) in support of maintenance activities and general inquiries.

2.2 SERVICE INFORMATION AND FAA AIRWORTHINESS DIRECTIVES

2.2.1 Service Information and FAA Airworthiness Directives Review The Contractor shall review publications pertaining to FAA compliance, Operational Safety, Suitability and Effectiveness (OSS&E) and system/component Original Equipment Manufacturer (OEM) information or suggested actions. The Contractor review shall include the following:

a. Service Bulletins (SB)

b. Service Letters (SL)

c. Structural Item Interim Advisories

d. Telegraphic Messages issued by the manufacturer of the aircraft

e. FAA Notices of Proposed Rule Making (NPRM)

f. Airworthiness Directives (AD)

g. Alternative Means of Compliance (AMOC)

h. Special Airworthiness Information Bulletins (SAIB)

i. FAA final rules

j. FAA Information for Operators (InFO)

k. FAA Safety Alert for Operators (SAFO)

l. Maintenance Tips

m. Operational Literature (Ops SB, Ops Ltr, etc)

n. Service Bulletins and Service Letters from vendors of components/black boxes specifically identified by the Government The Contractor shall attend industry and DoD meetings as needed to remain aware of in-service issues in the commercial fleet including Boeing Fleet Team and Working Together Meetings. Travel is separately authorized by the PCO.

NOTE: Service Information and FAA Directive reviews for NT-43A shall identify items potentially applicable to those aircraft, based on the original factory configuration baseline T-43A configuration (AFMC T-43). Such items shall be delivered as a group, monthly.

(CDRL XX04)

2.2.2 Service Literature Evaluation

(Applies to: VC-25A (except a.22, a.25, a.34, e), E-4B (except a.25, a.34, e), C-32A (except a.21, a.22), and C-40B/C (except a.21, a.22), and VC-25B (except a.25)) Except those determined to be informational only or non-applicable, the Contractor shall provide an evaluation for all reviewed publications to the Government IAW following:

a. For service publications that include OEM recommended actions, the evaluation letter shall include the following:

1. A summary of the activity discussed within the service publication and a brief description of the changes made by any revision

2. A summary of benefits gained and/or consequences avoided by incorporation considering the uniqueness of the aircraft mission, maintenance concepts and unique configurations

3. A recommendation of Approve (to adopt, accomplish, or comply with all or portion of publication which represents an aircraft inspection, modification, or regulatory compliance action), Disapprove (to not adopt, accomplish, or comply with all or portion of publication), Defer, and/or No Further Action (where the publication corresponds to or is superseded by another publication which has been or will be reviewed and any corresponding actions are addressed by or where the publication has been previously complied with), including Contractor’s rationale.

4. Level of recommended incorporation: Field, Depot, Engine Shop Visit (ESV), and/or Component Shop Visit (CSV)

5. Contractor Recommended Incorporation Time including threshold for inspection/modifications and repetitive intervals for inspections (both commercial and Air Force equivalent)

6. Publication Author (e.g. FAA, Rockwell, Honeywell, etc)

7. Publication Type: AD, SB, SL, SAIB, AMOC, Alert SB, and Special Attention SB

8. Publication Number

9. Publication Title

10. Publication Release Date

11. Contractor Evaluation Submission Date

12. ATA (2 digit level minimum, 4 digit level if available in bulletin)

13. CAT Level (as stated by the publication and applicable for Engine SBs only)

14. Service publication effectivity by tail number/core engine, referencing group number effectivity based on configuration.

15. ADs, SBs, and TCTOs/Airframe Change (AFC) associated with the subject service publication

16. Identify (Y/N) if the service publication is software related, where publication relates to new and revised software or software baseline for any level (aircraft, system, component, carry-on, etc.)

17. Status of incorporation of previous revisions on each aircraft, engine, landing gear, etc. (status will be determined and tracked from the best available data)

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

19. Identification of aircraft uniqueness or non-standard BCA modification issues and concerns based upon available, published platform Tech Manuals (IPC, AMM, etc.)

20. Identify affected Tech Orders and Tech Manuals, as identified in the publication

21. Identify (Y/N) if there is a potential for impact on nuclear hardness of the aircraft

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

23. Identify (Y/N) if there is a potential for impact to electromagnetic interference (EMI), electromagnetic compatibility (EMC), radio frequency (RF) effects, electrical load analysis (ELA), or Emission Security (EMSEC)

24. Provide affected discrepancy and replacement data (as needed).

NOTE: Government will provide supply data if unavailable to ESS Contractor

25. When Boeing warranty coverage is applicable, provide a synopsis of service publication warranty coverage to include aircraft T/N(s) and expiration

26. Publication compliance time (as applicable) to include stated threshold for inspection/modifications and repetitive intervals for inspections/modifications

27. Identification of existing or upcoming scheduled maintenance requirement(s), such as work/task card number, TCTO number, shop visit work requirement, Time Change Item (TCI), etc., when applicable to the service publication work requirement and/or access

28. AD Effective Date (applicable for AD only)

29. Identify (Y/N) actions that affect spares if applicable

30. Labor hours required to accomplish inspection/modification as listed within the service information publication

31. Specific material requirements including nomenclature, part number (P/N), quantity, cost and re-order lead time as listed within the service information publication

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

33. Identify corresponding or superseding service publication(s)

34. Identify (Y/N) if the service publication affects the applicable programs Extended Operations (ETOPS) configuration or compliance (including ETOPS In-Flight Start Program), Reduced Vertical Separation Minimum (RVSM) configuration or compliance, a Principal Structural Element (PSE) (as identified in publication), Maintenance Significant Item (MSI), Critical Safety Item (CSI), and carry-on item NOTE: MSIs and CSIs will be identified by the Government

b. For service publications that do not include OEM recommended actions and require explanation beyond what information is included in the service publication, an evaluation letter shall include the following:

1. A summary of the activity discussed within the service publication and a brief description of the changes made by any revision

2. ADs, SBs, and TCTOs/Airframe Change (AFC) associated with the subject service publication

3. Identification of aircraft uniqueness or non-standard BCA modification issues and concerns based upon available, published Tech Manuals (IPC, AMM, etc.)

4. A recommendation (as needed), including Contractor’s rationale

5. Identify affected Tech Orders and Tech Manuals, as identified in the publication

6. Publication Author (e.g. FAA, Rockwell, Honeywell, etc)

7. Publication Type: AD, SB, SL, SAIB, AMOC, Alert SB, and Special Attention SB

8. Publication Number

9. Publication Title

10. Publication Release Date

11. Contractor Evaluation Submission Date

c. For service publications which were reviewed by the Contractor per 2.2.2 and determined to be Informational only, an evaluation letter for each is not required. Instead, the Contractor shall summarize these items in a monthly letter that includes the following:

1. Publication Author (e.g. FAA, BCA, CFM, Honeywell, etc.)

2. Publication Type: AD, SB, SL, SAIB, AMOC, Alert SB, Special Attention SB, etc.

3. Publication Number

4. Publication Title

d. For non-applicable service publications which were reviewed by the Contractor per 2.2.2, an evaluation shall not be provided to the Government. However, the Contractor shall document/record the following in a database or as otherwise prescribed by each program:

1. Publication Author (e.g. FAA, BCA, CFM, Honeywell, etc.)

2. Publication Type: AD, SB, SL, SAIB, AMOC, Alert SB, Special Attention SB, etc.

3. Publication Number

4. Publication Title

5. Contractor’s rationale why publication was not applicable NOTE: The Contractor shall not provide copies of service literature that is deemed not applicable.

e. For service publications reviewed by the Contractor per 2.2.2, and are not being recommended to leave the parts-partner relationship to incorporate, shall be summarized in a monthly letter that includes the following:

1. Publication Author (e.g. FAA, BCA, CFM, Honeywell, etc.)

2. Publication Type: AD, SB, SL, SAIB, AMOC, Alert SB, Special Attention SB, etc.

3. Publication Number

4. Publication Title

5. Brief summary of the activity discussed within the service publication

6. Illustrated Parts Catalog (IPC) incorporation status as needed NOTE: The Contractor shall notify the Government if a lack of data precludes publication evaluation and recommend an appropriate method (i.e. inspection, documentation review, etc.) for determining resolution.

(CDRL XX04)

2.2.3 Service Action Review Board (SARB)/Concurrence Disposition Meeting (Applies to: VC-25A, E-4B, C-32A, C-40B/C, and VC-25B) The Contractor shall conduct and host SARB/Concurrence meetings as required by each platform. The purpose of the meeting is to document and record Government decisions concerning Service Literature for each platform. The Contractor shall also furnish the necessary facility.

The SARB review shall be documented on a standard concurrence checklist specifically developed for each weapon system. The Contractor shall provide this SARB concurrence checklist to document the Government decisions made during the SARB review. At a minimum, the following shall be addressed on the SARB concurrence checklist:

a. Approval/Disapproval/Deferred/No Action Required

b. Effectivity

c. De-Configure Risk

d. TCTO Required – Verification

e. Recurring/One Time Inspection

f. Completion Document/Job Sign-off Verification

g. Field/Depot Determination

h. Kit Recommendations

i. Spares Affected

j. Drawing Changes

k. Technical Manuals Affected – if possible, the recommended changes

l. Impact to the Program Protection Plan to include Anti-Tamper, Critical Component/Critical Program Information

m. Impact to Cybersecurity (i.e. Cybersecurity Strategy, Platform IT (PIT) documentation, Mission Systems)

n. Impact to Supply Chain (i.e. Counterfeit parts, alternative vendor)

o. Impact to Software Assurance (i.e. trusted vendor source, change to software delivery process)

p. Impact to PESHE

(CDRL XX07, XX08)

2.2.4 Government Industry Data Exchange Program (GIDEP) Review (Applies to: VC-25A, E-4B, C-32A, C-40B/C, and VC-25B) The Contractor shall participate in the GIDEP to receive information from the Failure Experience Data Bank (FEDB) and the Product Information Data Bank (PIDB). The Contractor shall screen information received from the FEDB and PIDB for applicability and provide a summary of applicable items. The Contractor shall provide a summary that determines if parts are installed/utilized on the applicable aircraft and provide recommendations.

(CDRL XX13)

2.2.5 Configuration Data Management Database

(Applies to: VC-25A, E-4B, C-32A, C-40B/C, and VC-25B) The Contractor shall maintain a database to provide status accounting and management of the aircraft configuration pertaining to service literature, FAA ADs, TCTOs, Supplemental Type Certificates (STCs), and Military Type Certificate (MTC) (VC-25B) as a minimum. This database shall have the capability to support related activities outlined in this PWS, such as service literature evaluations, SARB, AD audits; and generate reports, which would include but not limited to: SICD, and AD Compliance Status Report. This database will be accessible available 24/7 via the internet, and contain the following information and capabilities, as a minimum:

a. Current status for each item and record in the database (e.g. service literature and publications, AD’s, TCTO, STC, and MTC (VC-25B)).

b. Contain service literature and evaluation information per Sections 2.2.2.

c. Program Office recommendation and SARB disposition information included in concurrence sheets SARB minutes and per Section 1.8.1.

d. All documents delivered under Section 2.2.2 shall have view, download/save and print capabilities.

2.2.6 Emergency, Urgent and Short Compliance FAA Airworthiness Directives (ADs) The Contractor shall monitor the issuance of ADs, including emergency ADs and immediately adopted rule ADs, at least once per calendar day including weekends and holidays. If upon review of any newly released or revised ADs or FAA Final Rules which appear to affect and require action on any aircraft in this PWS, within 48 hours of receipt the Contractor shall provide copies and brief comments of any ADs or FAA Final Rules that require operator compliance within 12 months. If, upon review, the AD appears to affect and require action on any aircraft in this PWS within 7 calendar days, the Contractor shall immediately notify the Government and ensure contact is made. When not available on-line from applicable FAA websites, the Contractor shall obtain and provide copies to the Government.

2.2.7 Dispatch Deviation Guide and FAA Minimum Equipment List The Contractor shall provide updates to the 737, 737 BBJ, 757 and 747 Dispatch Deviation Guide and FAA Minimum Equipment List as developed by the airplane manufacturer and the FAA respectively.

(CDRL XX03)

2.2.8 Airworthiness Management Planning Information

(Applies to: VC-25A, E-4B, C-32A (except a), C-40B/C (except a), and VC-25B) The Contractor shall provide airworthiness management planning information as a section of the required monthly status report described in the following:

a. Weapon System Activity Planning

b. FAA Airworthiness Activity Requirements.

(CDRL XX06)

2.2.9 FAA Airworthiness Activity Requirements

(VC-25A, E-4B, C-32A, C-40B/C, and VC-25B) The Contractor shall provide a listing of released FAA Airworthiness Requirements that have pending Government or Contractor activity requirements as part of the monthly status report. The listings, to include suspense dates, shall cover each aircraft individually and shall extend into the future as far as necessary to cover pending activity. The outstanding requirements shall be divided into two areas based on the following categories:

a. Airworthiness requirements pending activity from a Government or Contractor organization as the next step in the accomplishment process; within the listing, identify the next step in the process and what the Government and/or Contractor organization is responsible for performing

b. Airworthiness requirements that the Government has dispositioned as an alternate means of compliance (AMOC) or disapproved, whereby the AMOC consists solely of a later accomplishment date than the FAA stated date shall not be included on the subject list.

(CDRL XX06)

2.2.10 Engine Records

(Applies to: VC-25A, C-32A, C-40B/C, and VC-25B) Contractor shall maintain a current file of all engine inspection and shop visit records. The Contractor shall furnish the data upon Government request. The Contractor shall evaluate engine records received for adequacy and notify the Program Office(s) of any deficiencies.

NOTE: The Government will provide engine inspection and shop visit records as they are generated.

2.2.11 Engine Management Plan

(Applies to: VC-25A, C-32A, C-40B/C, and VC-25B) The Contractor shall develop, maintain, and provide an engine management plan that will allow proactive and predictive engine maintenance. This plan shall include scheduling, configuration management, maintenance control, analysis of engine performance data and engine shop visit monitoring. The Contractor shall derive predictions based on average engine utilization and OEM published requirements.

C-32A and C-40B/C Only: The Contractor shall review Engine Condition Monitoring (ECM) data provided by the Government for potential engine problems or failures that impact the Engine Management Plan.

This summary shall have the following data elements for each engine:

a. Engine Rotation Schedule to predict planned engine removals by Aircraft tail number and engine position

b. On-Wing Maintenance: Develop scheduled requirements using OEM literature and Commercial Publications

c. Engine Shop Visit (ESV): High level maintenance and Life Limited Parts (LLPs) requirements based on Engine Rotation Schedule.

d. Historical Documentation (as provided by the Government): Accomplished on-wing maintenance and utilization C-40B/C Only: The Contractor shall use the CFM Engine Workscope Planning Document as a resource to plan and recommend work requirements for ESV.

(CDRL XX03)

NOTE: The Government will notify the Contractor in writing, monthly, of the aircraft/engine utilization data to include total flying hours, full stop, touch-and-go landings, engine hours, and engine cycles for the month being reported.

NOTE: The Contractor shall notify the Government of any record inadequacy or deficiency issues.

NOTE: The Government will notify the Contractor of any change removal/installation, date of removal/installation, and utilization at removal/installation

2.2.12 Auxiliary Power Unit (APU) Management Plan

(Applies to: C-32A and C-40B/C) The Contractor shall develop, maintain, and provide an APU/LG management plan that will allow proactive and predictive APU/LG maintenance. This plan shall include scheduling, configuration management, maintenance control, analysis of available APU/LG performance data and APU/LG shop visit monitoring. The Contractor shall maintain a current file of all APU/LG inspections and shop visit records and derive predictions based on average APU/ LG utilization and OEM published requirements.

The Contractor shall review APU/LG condition monitoring data provided by the Government for potential problems or failures that impact the APU/LG Management Plan.

The APU and LG management plan shall have the following content:

a) APU/LG Rotation Schedule to predict planned APU removals by Aircraft tail number

b) On-Wing Maintenance: Develop scheduled requirements using OEM literature and Commercial Publications

c) APU/LG Shop Visit: High level maintenance and Life Limited Parts (LLPs) requirements based on APU Rotation Schedule.

d) Historical Documentation (as provided by the Government): Accomplished on-wing maintenance and utilization

(CDRL XX03)

NOTE: The Government will notify the Contractor in writing on a monthly basis of the aircraft utilization which shall include total flying hours, full stops, touch-and-go landings, APU hours and APU/LG cycles for the month being reported. Additionally, the Government will notify the Contractor of any unscheduled APU/LG maintenance.

NOTE: The Government will notify the Contractor of any APU/LG removal/Installation, date of removal/installation, and utilization at removal/installation.

2.2.13 Auxiliary Power Unit (APU) Management Plan

(Applies to: E-4B and VC-25B) The Contractor shall provide APU management support and engineering services in support of the task requirements.

The Contractor shall compile and present data to the E-4B SPO for monitoring and reporting APU maintenance progress, report asset locations, and conditions of GTCP660-4 APU assets, track APU time change requirements, and track TCTO / SB compliance.

The Contractor shall develop and maintain an APU airworthiness management program to maintain E-4B APU fleet configuration, forecast APU management recommendations based on known airframe/APU requirements, and assess operational characteristics (e.g., full-stop landings, flight hours, elapsed calendar time, and significant events) which may impact APU lifecycle cost and performance. The Contractor shall provide all data artifacts and recommendations to the E-4B SPO for the E-4B APU airworthiness, modifications, AD and SB incorporation, and maintenance planning and accomplishments throughout the contract period. Recommendations shall be provided to the Government at periodic meetings and documented in minutes of those meetings.

The Contractor shall review and process current/historical maintenance data, provide engineering and program management decision quality data for support of maintenance review meetings, and provide recommendations for changes to APU maintenance programs. The Contractor shall identify and propose changes to the field maintenance plan, T.O. 1E-4B-6, and the E-4B APU Maintenance Plan, D226-46441-1. The Contractor shall review available maintenance data and support maintenance review meetings.

(CDRL XX03)

2.2.14 APU Records

(Applies to: C-32A, C-40B/C, and VC-25B) The Contractor shall maintain a current file of all APU inspections and APU shop visit records. The Contractor shall furnish the data upon Government request.

NOTE: The Government will provide APU inspections and APU shop visit records as they are generated.

(CDRL XX03)

2.2.15 APU Records Review

(Applies to: C-32A, C-40B/C, and VC-25B) The Contractor shall evaluate APU records received for adequacy and notify the Program Office of any deficiencies.

2.2.16 Maintenance Program Support

(Applies to: (VC-25A, E-4B, C-32A C-40B/C, and VC-25B) The Contractor shall develop and propose changes to the Scheduled Inspection and Maintenance Requirements Manual, Programmed Depot Maintenance (PDM) / Heavy Maintenance (HM) Plan (as applicable based on AD's, SB's, Service Letters, and the Corrosion Prevention and Control Program (CPCP) document) as required. The Contractor shall also propose revisions based on changes to the operational profile, safety or mission critical failures, as well as specific Government requests. The Contractor shall evaluate and propose revisions based upon modifications or upgrades to the aircraft systems.

2.2.17 FAA Certification and Airworthiness

(Applies to: VC-25A, E-4B, C-32A, C-40B/C, and VC-25B) The Contractor shall track and maintain FAA certification data and records by platform and tail number. The Contractor shall provide airworthiness support to include assessment of worldwide aviation regulation changes, in-service incidents, modifications, existing configurations, maintenance, new technologies and emergent issues. The Contractor shall also provide retrieval of certification records, development of certification processes and continued coordination with FAA and USAF certification authorities.

2.2.18 Service Information Configuration Document (SICD)

(Applies to: VC-25A, E-4B, C-32A, C-40B/C, and VC-25B) The Contractor shall maintain and provide a historical report of all applicable SBs and ADs, with the current incorporation status on each engine and aircraft, at a minimum. The Contractor shall evaluate and track data supporting incorporation from the best available data as provided by the Government.

NOTE: The Government will provide official released copies of TCTOs to the Contractor.

(CDRL XX03)

2.2.19 Maintenance Planning Document Revisions

(Applies to: C-32A, C-40B/C, and VC-25B) The Contractor shall obtain and review the applicable OEM Maintenance Planning Document (MPD) / task card revisions. The Contractor shall provide synopsis and applicability of all changes to the applicable maintenance program. The Contractor shall review changes based on the Government’s approved configuration (which includes military approved modifications), military maintenance requirements, operational use/profile, maintenance and reliability data, and program specific sustainment and operational requirements. The Contractor shall provide recommended changes that deviate from the OEM requirements. The Contractor shall incorporate recommended deviations as approved by the Government.

(CDRL XX05)

2.2.20 Scheduled Maintenance Checks

(Applies to: C-32A, C-40B/C, and VC-25B) The Contractor shall maintain a maintenance planning database with approved scheduled task requirements and task schedule. The Contractor shall provide A Check and C Check work packages to support the scheduled maintenance master schedule.

NOTE: The Government will provide completed A Check information to the Contractor for tracking and scheduling purposes.

(CDRL XX03)

2.2.21 Maintenance Inspection Requirements Document

(Applies to: C-32A, C-40B/C, and VC-25B) The Contractor shall develop and maintain a Maintenance Inspection Requirements Document that will include the following information:

a. Defines the current A and C Check maintenance program

b. TCI list that contains the mandatory replacement interval for time change items and life limited parts.

c. Conditional inspection requirements

d. Special inspection requirements where the required intervals fall outside of the A and C Check Maintenance Program

(CDRL XX05)

2.2.22 Training Manuals and Materials

(Applies to: VC-25A d-f only, C-32A a & g only, C-40B/C a-c & g only, and VC-25B d-f only) The Contractor shall provide training material designed for the following subjects as requested by the Government:

1. ETOPS and RVSM Training

1. Self Defense System (SDS) Training (C-40 only)

1. General Familiarization Training (C-40 only)

1. Avionics Systems Line and Base Maintenance (ATA level 3)

1. Systems Rigging (ATA level 4)

1. Combined Mechanical/Electrical…