Attachment 01 - KC-135 CCR SOW-Revised SOW 18 Sept 2023.pdf

CUI

STATEMENT OF WORK

FOR

KC-135 Center Console Refresh

Preparation Date: 18 Sept 2023

Purchase Request No.: F3YCAL3209A001

DISTRIBUTION D: DISTRIBUTION AUTHORIZED TO THE DEPARTMENT OF DEFENSE AND U.S. DOD

CONTRACTORS ONLY FOR ADMINISTRATIVE OR OPERATIONAL USE, 12 APRIL 2021.

OTHER REQUESTS SHALL BE REFERRED TO: AFLCMC/WLT

For more information look up:

DOD INSTRUCTI ON 5200.48 CONTROLLED UNCLASSIFIED INFORMATION (CUI)

CUI

CONTROLLED BY: AFLCMC/WLT

CUI CATEGORY: CONTROLLED TECHNICAL INFORMATION

CONTROLS: DISTRIBUTION D

POC: jacqueline.burns.5@us.af.mil mailto:jacqueline.burns.5@us.af.mil

Page i

CHANGE HISTORY

Mod. No. Description of Changes Requested By Approved By Date

None Initial version

Page ii

TABLE OF CONTENTS

1.0. Scope

1.1. Trade Space Adaptability

1.2. Component Function and Obsolescence Descriptions

1.2.1. Fuel System Components

1.2.2. Flight Display System Components

2.0. Applicable Documents

2.1. DoD Specifications, Standards and Other Documentation

3.0. Definitions

3.1. Modular Open Systems Architecture

3.2. Commercial Off-the-Shelf

3.3. Authoritative Source of Truth

3.4. Engineering Change Proposal

4.0. General Requirements

4.1. Program Management Requirements

4.1.1. Program Planning

4.1.2. Earned Value Management

4.1.3. Meeting Support

4.1.4. Integrated Digital Environment

4.1.5. Management

4.1.6. Contractor Cost and Software Data Reporting

4.2. Engineering

4.2.1. Software Engineering

4.2.2. Hardware Engineering

4.2.3. Systems Engineering

4.2.4. Digital Enterprise/Engineering

4.2.5. Certification Management

4.2.6. Safety Management

4.2.7. Human Factors Engineering

4.2.8. CCR Working Group

4.2.9. Prototype

4.2.10. Display Development Station

4.3. Test and Evaluation

4.3.1. Test DevOps

Page iii

4.3.2. Systems Integration Laboratories

4.3.3. Incremental Testing

4.3.4. Electromagnetic Interference/Compatibility Testing

4.3.5. Ground and Flight Testing

4.3.6. Cybersecurity Testing

4.3.7. Logistics T&E

4.3.8. Post Test

4.3.9. Operational Test

4.4. Data

4.4.1. Technical Manuals

4.4.2. Technical Data Package

4.5. Configuration Management

4.5.1. Configuration Control

4.6. Production Requirements

4.7. Installation

4.7.1. Aircraft Induction

4.7.2. Group A & B Installation

4.7.3. Verification of Installation

4.7.4. Aircraft Delivery

4.7.5. Acceptance Flight Check Flights

4.7.6. Disposition Instructions

4.7.7. Demilitarization and Disposal Instructions

4.8. Product Support

4.8.1. Quality Management

4.8.2. Supply Chain Risk Management

4.8.3. Logistics Management Reviews

4.8.4. Reliability and Maintainability

4.8.5. Training

4.8.6. Provisioning

4.8.7. Initial Spares

4.8.8. Sparing Recommendation

4.8.9. Diminishing Manufacturing Sources and Material Shortages

4.8.10. Item Unique Identification (IUID) Requirements

4.8.11. Package and Handling Requirements

Page iv

4.8.12. Maintenance Planning

4.8.13. Depot Repair Partnering

4.8.14. Warranty

4.8.15. Non-Warranty Repairs

4.8.16. Repair Maintenance History

4.8.17. Government Furnished Property

4.8.18. Discrepancies Incident to Shipment

4.8.19. Simulators

4.9. Over and Above

4.10. Travel

4.11. Security Requirements

4.11.1. Security Management

4.11.2. Operations Security (OPSEC)

4.11.3. Controlled Unclassified Information (CUI)

4.11.4. Covered Defense Information

4.11.5. Program Protection Plan (PPP)

4.11.6. Critical Program Information (CPI) Identification/Protection

4.11.7. Security Classification Guide (SCG)

4.11.8. Personnel Security (PERSEC)

4.11.9. Security Incidents and Violations

4.11.10. Common Access Card (CAC)

Appendix A: CDRLs

Appendix B: Abbreviations, Acronyms, and Brevity Codes

Page v

LIST OF FIGURES

Figure 1: Flight Deck Objective Scope

LIST OF TABLES

Table 1: Cited Document Location Table 2: Accessible Documentation Table 3: Government (Program Office) Provided Documentation Table 4: A and B Kit Ordering Schedule Table 5: Installation Schedule Table 6: CDRLs

1.0. Scope

The KC-135’s primary mission is to provide worldwide, day/night, adverse weather Aerial Refueling (AR) to receiver-capable United States (U.S.) and coalition military aircraft. KC-135 aircraft are designed to provide robust, sustained AR capability to support joint, allied, and coalition air forces, and specialized national defense missions. The KC-135 executes secondary missions such as cargo and/or passenger travel and aero-medical evacuations without impacting the primary AR mission.

The KC-135 Fuel System (FS) is core to the purpose of the KC-135 weapon system. Other aircraft weapons systems develop and execute their missions based upon the advertised capabilities of the KC-135 to refuel these airborne aircraft effectively and efficiently. The sustainability, availability, and operability of the KC-135 is largely contingent on a successful refresh of the fuel management system via the Center Console Refresh (CCR) program. The CCR program name is derived from the location of the components within program scope.

The current KC-135 FS and Flight Display System (FDS) Line Replaceable Units (LRUs) are obsolete due to Diminishing Manufacturing Sources and Material Shortages (DMSMS), which has resulted in difficulty procuring and maintaining the FS and FDS LRUs ultimately causing a reduction in mission capability rates for the KC-135 fleet. The Program Office (PO) has a requirement to resolve the KC-135 obsolescence issues for the KC-135 FS and FDS LRUs.

The scope of the CCR Program includes development of a fuel management system and display system and the modification of KC-135 aircraft with the developed systems. To support the development and modification effort, the program also includes the development and delivery of prototypes, A-Kits, B-Kits, a roll on/roll off test pallet (Display Development Station (DDS)), simulator kits, System Integration Laboratory (SIL) kits, and the modification of SILs and the potential to include Foreign Military Sales.

The replacement or “refresh” of obsolete components may also provide opportunities to achieve a more optimal solution. Since CCR is a large avionics upgrade, the proposed solutions might include adjacent systems not part of the obsolescence scope just described. The Government understands Commercial Off-The-Shelf (COTS) solutions integrate many avionics functions into one component and limiting the solutions to only obsolescence components would in turn limit the number of available solutions.

1.1. Trade Space Adaptability

The Government is interested in future growth and adaptability functions, features, and components In Accordance With (IAW) the Systems Requirements Document (SRD) identified as “should” statements detailed in the Creative Adaptability Components section of the SRD.

Solutions may change the form and fit of individual components, to include components outside scope of CCR, and enhance their function, as long as systems and the aircraft maintain existing functionality.

Figure 1: Flight Deck Objective Scope

The CCR core upgrades are depicted in green in Figure 1 above. The trade space adaptability components are depicted in blue. Additional components may be modified provided they do not negatively impact the functionality of the system or the aircraft.

1.2. Component Function and Obsolescence Descriptions

1.2.1. Fuel System Components

1.2.1.1. Integrated Fuel Management Panel

The Integrated Fuel Management Panel (IFMP) provides the flight crew with the switches, indicators, displays, and annunciators used to monitor and control fuel quantity and distribution. The individual tank quantity, total fuel, Center of Gravity (CG), and boom flow rate data are input into the IFMP in Binary Coded Decimal (BCD) format over the RS-422 data bus. The IFMP converts this BCD data into seven segment information and illuminates the appropriate displays on the front panel. The IFMP provides 10 individual tank displays, total fuel quantity, CG % mean aerodynamic chord line, fuel transfer rate, and fuel transferred quantity.

1.2.1.2. Fuel Management Advisory Computer

The Fuel Management Advisory Computer (FMAC) computes fuel quantity, CG, and weight and balance information and is comprised of individual excitation and indicating electronics for each tank. Each individual tank indicating circuit is individually powered from its own circuit breaker protected power supply. Tank indicating circuitry commonality begins in the FMAC at the measurement and computation unit where individual tank and total fuel quantities are computed by common processor electronics. The fuel indicating function is performed by the active channel microprocessor. Also, an identical standby channel provides back-up redundancy to the common areas of the tank indicating circuitry. In case of failure in the active system, execution of the CG total fuel, AR functions, and the fuel indicating functions are picked up by the standby channel. Each of these processors is individually powered by its own switching supply. The FMAC uses measured capacitance aircraft data from the fuel probes and compensators to compute and display continuous fuel quantity, CG, air refueling fuel transfer, and in-flight advisories to maximize fuel efficiency.

1.2.1.3. Tank Interface Unit

The tank interface unit is an electrically passive device containing 20 externally adjustable trim capacitors that are adjusted as part of the initial unit installation. Two trim capacitors provided for each tank make it possible to calibrate the individual tank indicating circuits. The capacitors are adjusted to calibrate the dry (empty) value of the tank unit to 400.00 (±0.25) pF and the dry value of the compensators tank unit to 197.50 (±0.25) pF. All 10 tank indicating circuits are functionally equivalent. The tank interface unit contains 20 externally adjustable trim capacitors that are adjusted at the time of initial installation of the unit. Two trim capacitors are provided for each compensator tank unit, making it possible to calibrate individual tank indicating circuits in conjunction with 31 fuel probes.

1.2.2. Flight Display System Components

1.2.2.1. Multi-Functional Display/Primary Flight Display

Multi-Functional Display/Primary Flight Display (MFD/PFD) provides information through a combination of display modes and overlays in conjunction with annunciations, current mode of operation, and condition of the systems providing displayed information. This information comes from the Electronic Attitude Director Indicator (EADI), Electronic Horizontal Situation Indicator (EHSI), Enhanced Traffic Alert and Collision Avoidance System (ETCAS), Enhanced Ground Proximity Warning System (EGPWS), Terrain mapping (TERR), and Weather Radar (WXR).

The MFD provides this information in a combination of display modes and overlays in conjunction with annunciations, current mode of operation, and condition of the systems.

1.2.2.2. Control Display Unit

The Control Display Unit (CDU) is the primary pilot input device for Built in Tests (BIT), Inertial Navigation Unit (INU) alignment, radio interface, and alpha-numeric keypad entries. The CDU communicates with the FMAC and Flight Performance Application (FPA) to display pilot CG computations data. They also provide data entry through a keypad for access to communications, Identification Friend or Foe (IFF) transponders and ETCAS, navigation flight plan pages, and both pilot and copilot steering pages.

1.2.2.3. MFD Control Panel

The MFD control panel controls the MFD’s navigation and situational awareness informational formats for the flight crew throughout all mission phases.

2.0. Applicable Documents

2.1. DoD Specifications, Standards and Other Documentation

The contractor shall use the latest document revisions available at the time of contract award.

Table 1 identifies access points for cited documentation listed in Table 2 and Table 3.

Table 1: Cited Document Location

Access Location Identifier for Tables 2.2 and 2.3

Description/Explanation

A DoD ASSIST Quick Search for all Distribution A publications: ASSIST- QuickSearch Basic Search (dla.mil)

This includes Military Specifications, Military Standards, Military Handbooks, and Data Item Descriptions (DID)

B DoD Issuances for all Distribution A publications: DoD Issuances Home (whs.mil)

This includes DoD Directives, DoD Instructions, DoD Manuals, and DoD (or DD) Forms

Additional Details:

DoD Directives: DoD Directives (whs.mil) DoD Instructions: DoD Issuances (whs.mil) DoD Manuals: DoD Manuals (whs.mil) DoD (or DD) Forms: Use the “DD Forms” drop down menu

C Air Force Issuances for all Distribution A publications: Department of the Air Force E-Publishing > Publications + Forms (af.mil)

This includes Air Force Instructions and Air Force Forms; use the “Search Products” field for all Air Force Issuances

D Copyrighted Industry Standard that must be acquired from the appropriate industry organization such as ANSI, ASME, EIA, IEEE, RTCA, SAE, or others.

E To be provided directly by the Legacy Tanker Program Office

F “Other” – see specific entry in Table 2 and Table 3 https://quicksearch.dla.mil/qsSearch.aspx https://quicksearch.dla.mil/qsSearch.aspx https://www.esd.whs.mil/DD/DoD-Issuances/ https://www.esd.whs.mil/DD/DoD-Issuances/ https://www.esd.whs.mil/Directives/issuances/dodd/ https://www.esd.whs.mil/Directives/issuances/dodi/ https://www.esd.whs.mil/Directives/issuances/dodm/ https://www.e-publishing.af.mil/Product-Index/ https://www.e-publishing.af.mil/Product-Index/

Table 2: Accessible Documentation

Document Number

(if applicable)

Document Title Release/Revision Date

Access Location (see Table 1)

AFI 91-204 Safety Investigations and Reports 10 Mar 21 C

AFMC Form 158 Packaging, Handling, Storage, and Transportation Acquisition and Sustainment Product Support Instruction

14 Oct 22 C

AFMC Form 718 Provisioning Performance Schedule 7 Dec 18 C

AFMCI 21-126 Temporary 2 (T-2) Modification of Aerospace Vehicles

19 July 2005;

Incorporating Change 1, 28

June 2016

C

AFTO Form 781 ARMS Aircrew/Mission Flight Data Document 3 Jul 17 C

ANSI/ESD

S20.20-2021

Protection Of Electrical and Electronic Parts, Assemblies and Equipment

14 Dec 21 D

ANSI Publication

AS9100D Quality Management Systems - Requirements for Aviation, Space and Defense Organizations

Sep 16 D

SAE

International Publication

AS9132B Data Matrix Quality Requirements for Parts Marking

May 15 D

SAE

International Publication

ASTM D3951 Standard Practice for Commercial Packaging May 18 D

ASTM

42 U.S.C. ch. 14 Atomic Energy Act of 1954 30 Aug 54 F

Executive Order 13526

Classified National Security Information 29 Dec 09 F

DAFMAN 16-

1404 Vol 1-3

Air Force Information Security Program 12 Apr 22 C

Document Number

(if applicable)

Document Title Release/Revision Date

Access Location (see Table 1)

DCMA 8210-1D Contractor's Flight and Ground Operations Feb 23 F

Aircraft Operations

Resource Page (dcma.mil)

DD Form 1149 Requisition and Invoice/Shipping Document Jan 16 B

DD Form 1348- 1A

Issue Release/Receipt Document Jul 91 B

DD Form 1653 Transportation Data for Solicitations Apr 99 B

DD Form 250 Material Inspection and Receiving Report Aug 00 B

DO 160G Environmental Conditions and Test Procedures for Airborne Equipment

8 Dec 10 D

RTCA

DO 178C Software Considerations in Airborne Systems and Equipment Certifications

13 Dec 11 D

DO 254 Design Assurance Guidance for Airborne Electronic Hardware

19 Apr 00 D

DoDD 5205.02E DoD Operations Security (OPSEC) 20 Jun 12 B

DoDI 2040.02 International Transfer of Technology, Articles, and Services

27 Mar 14 B

DoDI 3200.14 Principles and Operational Parameters of the DoD Scientific and Technical Information Program

14 Mar 14 B

DoDI 5000.02 Operation of the Adaptive Acquisition Framework

23 Jan 22 B

DoDI 5000.73 Cost Analysis Guidance and Procedures 13 Mar 22 B

DoDI

5000.83_DAFI63-

Technology and Program Protection to Maintain Technological Advantage

21 May 21 B https://www.dcma.mil/Customers/Aircraft-Operations-Resource-Page/ https://www.dcma.mil/Customers/Aircraft-Operations-Resource-Page/ https://www.dcma.mil/Customers/Aircraft-Operations-Resource-Page/ https://www.dcma.mil/Customers/Aircraft-Operations-Resource-Page/

Document Number

(if applicable)

Document Title Release/Revision Date

Access Location (see Table 1)

DoDI 5200.39 Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E)

28 May 15 B

DoDI

5200.48_DAFI16-

Controlled Unclassified Information 6 Mar 20 B

DoDI 5230.24 Distribution Statements on Technical Documents

10 Jan 23 B

DoDD 5230.25 Withholding of Unclassified Technical Data From Public Disclosure

15 Oct 18 B

DoDI

8000.89_DAFI

99-103

Capabilities Based Test and Evaluation 9 Dec 21 C (Not B)

Search “99-103”

DoDI 8582.01 Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information

9 Dec 19 B

DoDM 5000.04 Cost and Software Data Reporting 7 May 21 B

DoDM 5200.01, Vol

1_AFMAN16-

1404, Vol 1

Information Security Program 6 Apr 22 C

DoDM

5400.07_AFMAN

33-302

Freedom of Information Act (FOIA) Program 27 Apr 18 C

EIA 649-1A Configuration Management Requirements for Defense Contracts

Aug 20 D

EIA Publication

EIA 748D Earned Value Management Systems 8 Jan 19 D

EIA Publication

IEEE 15288.2 Technical Reviews and Audits on Defense Programs

10 Dec 14 D

IEEE Publication

Document Number

(if applicable)

Document Title Release/Revision Date

Access Location (see Table 1)

MIL-HDBK-516C Airworthiness Certification Criteria 12 Dec 14 A

MIL-HDBK-61B Department of Defense (DoD) Handbook - Configuration Management Guidance

7 Apr 20 A

MIL-HDBK-896A Manufacturing Management Program Guide 25 Aug 16 A

MIL-PRF-63033 Technical Manuals, Technical:

Demilitarization of Surplus Military Items, Preparation of

3 Dec 21 A

MIL-STD-129R

w/ Change 2

Military Marking for Shipment and Storage 25 Feb 23 A

MIL-STD-130N

w/ Change 1

DoD Standard Practice: Identification Marking of the U.S. Military Property, 16 November

16 Nov 12 A

MIL-STD-1472H DoD Design Criteria Standard - Human Engineering

15 Sep 20 A

MIL-STD-2073-

1E w/ Change 4

Standard Practice for Military Packaging, 07 January 2011

22 Apr 19 A

MIL-STD-3022

w/ Change 1

Documentation of VV&A for Models and Simulations, 28 January 2008

5 Apr 12 A

MIL-STD-31000B Technical Data Packages 31 Oct 18 A

MIL-STD-461G Requirements for the Control of Electromagnetic Interference

11 Dec 15 A

MIL-STD-464D Electromagnetic Environmental Effects Requirements for Systems

24 Dec 20 A

MIL-STD-882E System Safety 11 May 12 A

NIST Special Publication 800-

Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations

Feb 20 F

SP 800-171 Rev.

2, Protecting Controlled

Unclassified Information in

Nonfederal Systems and

Organizations | CSRC (nist.gov) https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final

Document Number

(if applicable)

Document Title Release/Revision Date

Access Location (see Table 1)

N/A DoD Digital Engineering Strategy Jun 18 F

2018-Digital- Engineering-

Strategy_Approv ed_PrintVersion.

pdf (cto.mil)

N/A Integrated Product Support Element Guidebook

Mar 21 F

Integrated Product Support (IPS) Element

Guidebook (dau.edu)

N/A Joint Travel Regulation UNKNOWN F

Joint Travel Regulations |

Defense Travel Management

Office (dod.mil)

NAS-3306 Rev 4 Facility Requirements for Aircraft Operations 29 May 20 D

AIA/NAS

NIST SP 800-60

vol 2 Rev 1

Appendices to Guide for Mapping Types of Information and Information Systems to Security Categories

Aug 08 F

SP 800-60 Vol. 2 Rev. 1, Mapping Information/Syst em Types to Security

Categories | CSRC (nist.gov)

SD-22 DoD

DMSMS

Guidebook

Diminishing Manufacturing Sources and Material Shortages: A Guidebook of Best Practices for Implementing a Robust DMSMS Management Program

22 May A

SF364 Report of Discrepancy Feb 80 F

Forms | GSA https://ac.cto.mil/wp-content/uploads/2019/06/2018-Digital-Engineering-Strategy_Approved_PrintVersion.pdf https://ac.cto.mil/wp-content/uploads/2019/06/2018-Digital-Engineering-Strategy_Approved_PrintVersion.pdf https://ac.cto.mil/wp-content/uploads/2019/06/2018-Digital-Engineering-Strategy_Approved_PrintVersion.pdf https://ac.cto.mil/wp-content/uploads/2019/06/2018-Digital-Engineering-Strategy_Approved_PrintVersion.pdf https://ac.cto.mil/wp-content/uploads/2019/06/2018-Digital-Engineering-Strategy_Approved_PrintVersion.pdf https://www.dau.edu/tools/t/Integrated-Product-Support-(IPS)-Element-Guidebook-https://www.dau.edu/tools/t/Integrated-Product-Support-(IPS)-Element-Guidebook-https://www.dau.edu/tools/t/Integrated-Product-Support-(IPS)-Element-Guidebook-https://www.dau.edu/tools/t/Integrated-Product-Support-(IPS)-Element-Guidebook-https://www.dau.edu/tools/t/Integrated-Product-Support-(IPS)-Element-Guidebook-https://www.travel.dod.mil/Policy-Regulations/Joint-Travel-Regulations/ https://www.travel.dod.mil/Policy-Regulations/Joint-Travel-Regulations/ https://www.travel.dod.mil/Policy-Regulations/Joint-Travel-Regulations/ https://www.travel.dod.mil/Policy-Regulations/Joint-Travel-Regulations/ https://www.travel.dod.mil/Policy-Regulations/Joint-Travel-Regulations/ https://csrc.nist.gov/publications/detail/sp/800-60/vol-2-rev-1/final https://csrc.nist.gov/publications/detail/sp/800-60/vol-2-rev-1/final https://csrc.nist.gov/publications/detail/sp/800-60/vol-2-rev-1/final https://csrc.nist.gov/publications/detail/sp/800-60/vol-2-rev-1/final https://csrc.nist.gov/publications/detail/sp/800-60/vol-2-rev-1/final https://csrc.nist.gov/publications/detail/sp/800-60/vol-2-rev-1/final https://csrc.nist.gov/publications/detail/sp/800-60/vol-2-rev-1/final https://www.gsa.gov/reference/forms

Table 3: Government (Program Office) Provided Documentation

Document Number

(if applicable)

Document Title Release/Revision Date

Access Location (see Table 1)

AWB-130 Airworthiness Bulletin: Certification Basis 2 Jun 21 E

AWB-140 Airworthiness Bulletin: Compliance Report 2 Jun 21 E

AWB-150 Airworthiness Bulletin: Airworthiness Risk Assessment and Acceptance

30 Sep 20 E

N/A CCR SRD 26 Jul 23 E

N/A Initial Provisioning Performance Specification (IPPS) w/ Attachments

10 Aug 17 E

N/A KC-135 ITT Charter May 21 E

N/A KC-135 Legacy Tanker Configuration Management Plan

6 Apr 21 E

N/A KC-135 Program Protection Plan Feb 23 E

N/A Legacy Tanker System Engineering Plan (SEP), CCR Annex

28 Jul 2023 E

N/A Legacy Tanker Systems Engineering Plan

(SEP)

13 Aug 21 E

N/A Legacy Tanker Test Evaluation Master Plan

(TEMP)

May 21 E

N/A AFRL-STO MBSE Style Guide v1-2 N/A E

N/A OMG SysML Ver 1.6 Nov 19 E

OMS-STD-001

Rev J

Open Mission Systems Standard 16 Dec 22 E

TM-86-01R Air Force Technical Manual Contract Requirements (TMCR)

17 Jun 20 E

TO 00-35D-54 USAF Deficiency Reporting, Investigation, and Resolution

Most Current Version in

ETIMS

E

3.0. Definitions

3.1. Modular Open Systems Architecture

The definition of Modular Open Systems Architecture (MOSA) can be found in TITLE 10§ 4401, Requirement for modular open system approach in major defense acquisition programs.

3.2. Commercial Off-the-Shelf

The definition of COTS can be found in 48 CFR § 2.101 – Definitions.

3.3. Authoritative Source of Truth

The definition of Authoritative Source of Truth (ASoT) can be found in the DoD, Digital Engineering Strategy, June 2018.

3.4. Engineering Change Proposal

The definition of Engineering Change Proposal (ECP) can be found in the Legacy Tanker Systems Engineering Plan (SEP), 13 August 2021

4.0. General Requirements

The contractor shall design a solution for a FS and FDS by satisfying the requirements addressed in the CCR SRD. The CCR SRD describes the requirements through detailed descriptions. In the event there is a discrepancy between this Statement of Work (SOW) and the SRD, the SRD shall have precedence.

The contractor shall deliver the Contract Data Requirements List (CDRL) items via government approved CDRL Delivery tool.

The contractor shall support the option for virtual attendees for all CCR Program meetings.

The Contractor shall maintain NAS-3306 compliant facilities.

The contractor shall not divulge any information regarding files, data, processing activities/functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standards of conduct. Contractors requiring access to Government Automated Information Systems (AIS) shall have background investigations and security awareness training completed, after task order award but prior to AIS access. When the period of performance is complete and/or contractor personnel leave work on this project, they will have five calendar days to terminate all their network user accounts and return all access cards and base identification badges.

All records generated by the contractor shall be marked with appropriate distribution statement in accordance with the DD1423 Contract Data Requirement List (CDRL) and delivered to the government.

Deliverables (i.e., drawings, briefing charts, analysis, software, reports), accomplished under this contract shall be marked with appropriate legends with the unlimited rights in accordance with the FARS/DFARS contract language.

The contractor shall provide the A-kit/Installation drawings, and B-kit engineering drawings with unlimited rights, as negotiated. The A-kit/B-kit Installation drawing package will ensure the USAF the ability to supply or compete A-kits/B-kits, complete depot maintenance/ installation, as well as perform organic maintenance of the system.

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

The contractor shall ensure contractor employees required to communicate with government personnel can read, write, and speak English to effectively communicate with the government. The Contractor shall obtain contractor’s badges to allow unescorted entry onto Tinker AFB or Common Access Cards (CAC) to allow access to government databases as required to complete the requirements of this SOW or a specific non-recurring Task Assignment. The contractor shall work with appropriate government sponsors to obtain these identification badges. Issuance of CACs will require completion of National Agency Checks (NAC) with written inquiries in accordance with AFI 31-501 and AFI 31-501_AFGM2016-01. Legacy Tanker Program Office in-house Contractor personnel shall hold a Secret or higher security clearance.

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. This requirement has been determined to be essential and does require continued support during a crisis as defined in DFARS 252.237-7023.

4.1. Program Management Requirements

The contractor shall provide a single Point of Contact (POC), not to exceed two alternates, who shall represent the contractor for management and authority of all contractual and operational requirements of the contract. The contractor shall maintain the name and contact information of all POCs in the key contact list.

The contractor shall develop, maintain, and provide an organizational chart identifying key personnel names and job titles with a line of responsibility between the organizational elements.

4.1.1. Program Planning

The contractor shall conduct program planning for all events from contract award through the completion of all contract activity. The contractor shall plan for the necessary events, significant accomplishments, and accomplishment criteria needed to successfully complete the program, including mandatory events, accomplishments, and entry and exit criteria.

This planning shall encompass all Integrated Product Teams (IPT) structures, contractor Work Breakdown Structure elements, and functional disciplines. (A001)

The contractor shall develop and maintain a Work Breakdown Structure (WBS). The WBS shall be extended to the lowest level required to provide adequate internal management, surveillance, and performance measurement and shall be the basis for tracking, controlling, measuring, and reporting cost and schedule performance. The WBS shall be consistent with the Integrated Master Schedule (IMS).

4.1.2. Earned Value Management

The contractor shall implement an earned value management system IAW the guidelines in the American National Standards Institute/Electronic Industries Alliance Standard 748, Earned Value Management Systems (ANSI/EIA-748) and the clauses for this contract.

(A002)

4.1.2.1. Integrated Master Schedule

The contractor shall manage the execution of CCR work using an (IMS) as a day-to-day execution tool and to periodically assess progress in meeting program requirements.

The contractor shall report on program progress IAW the IMS at each Program Management Review, at selected technical reviews, and in response to the Government’s request. The contractor shall maintain and update the IMS, when necessary, to reflect Government approved changes, or changes in the contractor’s detailed execution activities or schedule. The contractor shall include the activities of the prime contractor and their major subcontractors in the IMS. All contractors shall derive all schedule information delivered to the Government or presented at program reviews from the IMS. The contractor shall perform appropriate analyses of the IMS tasks and report potential or existing problem areas and recommend corrective actions to eliminate or reduce schedule impact (A002, A003).

4.1.2.2. Integrated Baseline Review

The contractor shall engage with the Government Program Manager (PM) during Integrated Baseline Reviews (IBR) to evaluate the risks inherent to the contract’s planned performance measurement baseline. The contractor shall host a Government-conducted IBR at the contractor facility occurring no later than ninety

(90) calendar days after contract award and subsequently following any events that would cause a re-baseline. The IBR shall verify the contractor is using a reliable performance measurement baseline, which includes the entire scope of the contract, entire scope of work, consistency with contract schedule requirements, and adequate resource assignments.

4.1.3. Meeting Support

The contractor shall support required meetings, reviews, and conferences for both in-person meetings and virtual meetings with Microsoft Teams or other Government approved applications (video, web, or audio).

4.1.3.1. Post Award Conference

The contractor shall coordinate a CCR Post Award Conference (PAC) for the Government. The contractor shall conduct the PAC within thirty (30) calendar days of contract award at the contractor’s facility. The contractor shall address and provide details to their understanding of the contract requirements. The contractor shall outline how the requirements of the contract shall be achieved.

(A004, A005, A006)

4.1.3.2. Technical Order Guidance Conference

Working through the Technical Order Management Agency (TOMA), the contractor shall co-host and participate in a guidance conference for this effort. The Technical Order Guidance Conference (TOGC) will be held within twenty (20) business days after contract award. The Technical Manual Schedule and Status (TMSS) will be formalized at this conference. The contractor shall present a briefing of their interpretation of the basic contract, Statement of Work, CDRL, DIDs, MIL-SPECs, MIL-DTLs, MIL-STDs, SIRs, and the planned preparation and delivery of the Technical Orders (TO) and related data. The TOMA will dictate whether the TOGC will be held in-person or virtually.

(A004, A005, A006, A007)

4.1.3.3. Program Management Review

The contractor shall host and conduct PMRs every six months at a facility within twenty (20) miles of Tinker Air Force Base (AFB), OK, unless an alternate location is authorized by the Procuring Contracting Officer (PCO). The approved facility shall accommodate in-person attendees to be coordinated prior to facility approval.

(A004, A005, A006)

4.1.3.4. Status Review

The contractor shall host and conduct status reviews virtually once every two weeks through Engineering & Manufacturing Development (EMD) and monthly thereafter.

The contractor shall host the first status review within fourteen (14) calendar days following the PAC.

• At a minimum, the contractor shall present the following at the status reviews:

• Accomplished events since the previous weekly status review

• Management of new and existing risks

• Project successes and improvements

• Identification of new action items

• Review of existing action items

• Status of deliverables

• Changes to the projected schedule

• Risks: new or updated

(A008)

4.1.4. Integrated Digital Environment

An Integrated Digital Environment (IDE) will support the ASoT portion of Digital

Engineering (DE) by providing a means to control, manage, organize, and preserve data and data models. This will result in a complete, transparent, and reliable source of program information across the remaining program lifecycle so cross functional organizations can make decisions from the same information.

The contractor shall develop and maintain a contractor-hosted IDE that enables DE processes and the required DE features such as, but not limited to, document reviews, establishing baselines, and viewing traceability models. The contractor shall perform systems architect functions and systems engineering of its IDE to ensure required data transitions are accessible and/or delivered to the Government. The contractor shall provide the Government with support materials such as, but not limited to, IDE access instructions, technical support POC, IDE navigation guides, a description of privileges granted, and/or training materials.

The contractor shall ensure the IDE is at least Impact Level 4 (IL4).

The contractor shall provide updated training, system change notifications, and other similar materials to the Government on the same schedule as company internal updates are provided.

The contractor shall establish an IDE, provide the Government access, and provide the Government support materials prior to the PAC. The CCR contractor IDE database shall remain supported and be accessible by the Government with all Government privileges in place up to achieving black label. The contractor shall ensure all contractor content uploaded into the IDE and/or database(s) remains in place until black label is achieved.

(A009)

The government defines blue label software as ready for Formal Qualification Test (FQT).

The government defines red label software as ready for Developmental Test. Black label software is representative of the final product configuration for the program.

4.1.5. Management

4.1.5.1. Risk Management Plan

The contractor shall establish and maintain a Risk Management Plan. The contractor shall document their risk management process in a contractor Risk Management Plan.

The contractor shall document any tailoring to industry or other standard (e.g., corporate) processes. The contractor shall plan for, identify, and mitigate technical, cost, test, and schedule risks for all phases of the CCR program. The contractor shall incorporate risk mitigation plans into all program planning and technical activities. The contractor shall present the full risk portfolio at a minimum every six (6) months at PMR. Additionally, the contractor shall present new or updated risk at the biweekly status meeting. (A010, A011)

4.1.6. Contractor Cost and Software Data Reporting

The contractor shall systematically collect and report to Cost Assessment Data Enterprise

(CADE) and the United States Government (USG) the actual contract costs and technical information. (A012, A013, A014, A015)

4.2. Engineering

4.2.1. Software Engineering

4.2.1.1. Software Program Management

The contractor shall develop software compliant with the Design Assurance Level (DAL) specified by the contractor’s safety assessment report. (A016) The contractor shall develop and maintain a Software Development Plan (SDP) compliant with DO-178C. The SDP shall be delivered IAW the IMS. (A017) IAW DO-178C, the contractor shall develop a Software Configuration Index, a Software life cycle Environment Configuration Index and a Software Accomplishment Summary. The Software Configuration Index, Software life cycle Environment and Software Accomplishment Summary fulfill the requirement for a Software Product Specification and shall be delivered IAW the IMS. (A018).

4.2.1.2. Software Requirements Definition

The contractor shall define software requirements compliant with DO-178C. (A019)

4.2.1.3. Software Design

The contractor shall develop and maintain software design standards for software applications with a DAL of “C” or higher compliant with DO-178C.

The contractors shall deliver Software Design Description (SDD) compliant with

DO-178C. (A020).

4.2.1.4. Software Development

The contractor shall develop and maintain software code standards for software application with a DAL of “C” or higher compliant with DO-178C.

4.2.1.5. Incremental Design Review

The Government’s desire is to have frequent and less formal reviews of the contractor’s progress. For the purposes of this SOW, these reviews will be referred to as an Incremental Design Review (IDR). These IDRs will primarily focus on the development of CCR’s functional performance and architecture. (A006) The IDRs shall contain, at a minimum, the following:

• Previous action item status and results

• Amount of progress completed per the contractor’s plan

• Deviations and/or adjustments to the plan

• New action items The contractor shall schedule IDRs every forty (40) business days between SRR and PDR closeout with Government approval of IDR scheduling.

The contractor shall schedule IDRs every twenty (20) business days between PDR closeout and CDR closeout with Government approval of IDR scheduling.

The contractor shall schedule IDRs every sixty (60) business days between CDR closeout and 90 business days before DT begins, with Government approval of IDR scheduling.

4.2.2. Hardware Engineering

The contractor shall use unmodified COTS to the maximum extent possible, unless alternatives have been approved by the Government. If any development is required and approved, the contractor shall develop new and modified hardware compliant with

DO-254.

4.2.2.1. Open Systems Management Plan

The contractor shall include in the Open Systems Management Plan (OSMP) how MOSA Tier 1 will be achieved and how MOSA Tiers 2 and 3 might be achieved IAW OMSC-STD-001 RevJ OMS Standard. The OSMP will be reviewed for approval during Preliminary Design Review (PDR). (A021)

4.2.2.2. Interface Control Document

The contractor shall submit the Interface Control Document (ICD) IAW the IMS.

(A022, A023, A024).

For hardware and software interfaces impacted by the CCR modification, the contractor shall ensure electrical and data compatibility between KC-135 modified aircraft and legacy systems.

4.2.3. Systems Engineering

The contractor shall implement and execute a systems engineering program. The contractor shall deliver a Systems Engineering Management Plan (SEMP). (A025).

The contractor shall create a requirements model demonstrating 100% traceability of all requirements and use Model-Based Systems Engineering (MBSE) tenants in the creation of the models.

The contractor shall adhere to AFRL-STO MBSE Style Guide v1-2 and OMG SysML Ver

1.6 for all MBSE deliverables. Both the AFRL-STO MBSE Style Guide v1-2 and OMG SysML Ver 1.6 were created to complement each other as one complete style guide. The OMG SysML Ver 1.6 is an embedded file within the AFRL-STO MBSE Style Guide v1- 2 Cameo file. This embedded OMG SysML Ver 1.6 will be provided by the government as a PDF. The contractor will need access to No Magic Cameo Systems Modeler Enterprise Edition 2021x or suitable MBSE conversion software to view AFRL-STO MBSE Style

Guide v1-2.

The contractor shall complete all efforts associated with this contract at Continental United States (CONUS) locations.

4.2.3.1. Verification Provisions

Program requirements stated within the SRD must be verified to show they have been met.

4.2.3.2. CCR Modification Induction Minimum Equipment List

The contractor, in conjunction with the Government, shall identify the minimum equipment which must be operational prior to beginning the CCR modification on an aircraft. Reference may be made to the operational headquarters Air Mobility Command KC-135 Minimum Equipment List (MEL), but differences from the operational MEL shall be mutually agreed to by the contactor and the Government, and specifically identified as exceptions to the operational MEL in the CCR Modification Induction MEL. (A026)

4.2.3.3. Technical Reviews and Audits

The Government intends to take an iterative approach to CCR program development and acquisition. Additional technical reviews and/or audits deemed necessary by the contractor may be supported by the Government.

The Government mandated technical reviews and audits are listed in this section followed by the intent of each. The entry and exit criteria for these technical reviews and audits are described in the CCR SEP Annex.

The contractor shall use available models to generate appropriate information to fulfill the review and audit criteria and incorporate these into the SRR, System Functional Review (SFR), PDR, Critical Design Review (CDR), MRRA, Functional Configuration Audit (FCA), and PCA.

The contractor shall present during live technical reviews material that uses any level of MBSE features by using the contractor’s choice of MBSE software. The contractor shall use any media of choice to present non-MBSE information such as, but not limited to, organizational charts, presentation agenda/schedule, and/or photos. The contractor shall deliver to the Government the MBSE file used in the meeting in its entirety and the non-MBSE meeting materials no later than seven (7) calendar days after the end of the review event.

The contractor shall identify any additional technical reviews and audits, if needed. The contractor shall tailor both the mandated and additional (if identified) technical and review audits based on guidance provided in IEEE 15288.2.

4.2.3.3.1. System Requirements Review/System Functional Review

The contractor shall conduct an SRR and SFR as defined in the SEP. These reviews may be held concurrently or separately as needed. The contractor shall host these reviews at the contractor’s facility. (A004, A005, A006)

4.2.3.3.2. Preliminary Design Review

The contractor shall host a PDR at the contractor’s facility. The contractor shall follow the entry and exit criteria as specified in the SEP/Systems Engineering Management Plan (Cert). The contractor shall use the current OFP version defined by the government as the baseline for software integration. (A004, A005, A006, A027, A028, A029, A030, A031, A032)

4.2.3.3.3. Critical Design Review

The contractor shall host and conduct a CDR at the contractor’s facility. Results of this review shall become the initial product baseline for CCR. The contractor shall follow the entry and exit criteria as specified in the SEP/SEMP. (A004, A005, A006, A031, A091)

4.2.3.3.4. Modification Risk and Readiness Assessment

The contractor shall host and conduct a Modification Risk and Readiness Assessment (MRRA) prior to modification of the first prototype. The contractor shall receive Government approval prior to beginning modification. The contractor shall, at a minimum, brief the following:

• Brief status of kit procurement:

• Drawings status

• Outstanding action items or issues

• Identified risks and risk mitigation plans

• Certifications required

• Aircraft delivery date

The contractor shall provide a Modification Readiness Risk Assessment Report as reference for Government decision authority to approve commencing aircraft modification. The report shall detail the mitigation of identified modification risks and the contractor’s readiness to begin prototype aircraft modifications. (A004, A005, A006, A033, A034)

4.2.3.3.5. Functional Configuration Audit

The contractor shall support FCA at its facility for the Government to verify the CCR system and subsystems are being developed to meet the capabilities detailed in the CCR Initial Capabilities Document. (A035)

4.2.3.3.6. Physical Configuration Audit

The contractor shall support two PCAs at its facility for the Government to verify that the CCR system production kits which successfully pass developmental test and operational testing are accurately and sufficiently detailed in the technical drawings intended to define the product baseline. The contractor shall support the initial PCA within ten (10) business days after developmental test closeout and a second PCA within ten (10) business days after operational test closeout. The audit shall be performed in compliance with MIL-HDBK-61B (Configuration Management Guidance) and must be completed prior to the Full Rate Production Decision Review. (A035)

4.2.4. Digital Enterprise/Engineering

The contractor shall implement an ASoT methodology within a digital ecosystem to the extent required by the modeling objectives included in the contract.

The contractor shall allow the Government access to the contractor’s requirements database software starting prior to the PAC and ending at black label.

The contractor shall provide the Government access to view all CCR MBSE and/or System Modeling Language (SysML) data products in their respective native software platforms.

The contractor shall make available for viewing all data products being developed, modified, managed, and/or stored. The contractor shall allow Government access during contractor working days and working hours.

4.2.5. Certification Management

4.2.5.1. Airworthiness Certification

The contractor shall support airworthiness certification for CCR and DDS separately.

The contractor shall provide subject matter support for Government Airworthiness (AW) activities to conduct an AW assessment and receive an AW approval prior to conducting any flight operations.

The contractor shall provide the necessary data to support the Government’s effort of obtaining the AW approval prior to conducting any flight operations.

4.2.5.1.1. Systems Engineering Air Worthiness Considerations

The contractor shall integrate AW into their Systems Engineering processes to support integration and efficiency of program requirements, development, verification and certification processes, and tools. The contractor shall provide subject matter support for AW activities required by the Government to conduct an AW assessment. These AW activities include development of a Certification Basis, executing compliance verification activities to obtain airworthiness data, and develop a Compliance Report with supporting documentation, and assessment of residual risk(s). The contractor shall develop and deliver the updated Certification Basis associated with the program. The Contractor shall develop and deliver the Certification Basis associated with the program. The Contractor shall comply with AWB-130; the Certification Basis shall contain the system description, applicable criteria, standards, and methods of compliance from MIL-HDBK-516, as designated by the Government for this effort, and rationale for non-applicability.

This document shall become part of the functional baseline for this program. The contractor shall include rationale for the criteria that have been updated. (A036)

4.2.5.1.2. Compliance Report

The contractor shall develop and deliver the Compliance Report. The Contractor shall comply with AWB-140; the Compliance Report shall provide a mapping of substantiating data to each applicable criterion in the Certification Basis from MIL- HDBK-516(C). The contractor shall deliver documentation used to substantiate the AW of the design to allow the Government to review and analyze information in preparation to show AW compliance even if the substantiating documentation is not otherwise specific as a contract deliverable. The contractor shall assist the Government in updating the Compliance Report ahead of each phase (e.g., flight test, operations). The contractor shall include rationale for the criteria that have been updated. (A037)

4.2.5.1.3. Risk Assessment and Acceptance

The contractor shall identify hazards due to non-compliances, recommend near term restrictions, and identify work remaining to strengthen compliance. The contractor shall capture this information in the compliance Report, the associated Safety Assessment report, and the AW Risk Assessment Package. The contractor shall support the government’s risk acceptance efforts IAW AWB-150. (A038)

4.2.5.1.4. As-Built Configuration Description

The contractor shall support the AW process by providing documentation on the air system configuration for each aircraft.

4.2.5.2. Air Force Flight Standards Agency Certification

The contractor shall support the Government in obtaining Air Force Flight Standards Agency certification of the CCR PFD.

4.2.5.3. AIMS Certification

The contractor shall support the DoD Air Traffic Control Radar Beacon System, Identification Friend or Foe, Mark XII/Mark XIIA, Systems (AIMS) recertification.

4.2.5.4. CNS-ATM Matrices

The contractor shall provide analysis and information in support of CCR Compliance with Communication, Navigation, and Surveillance/Air Traffic Management (CNS/ATM) matrices.

4.2.5.5. ARCA Certification

The contractor shall support Air Refueling Certification Agency (ARCA) certification for the CCR Program.

4.2.5.6. Cybersecurity Requirements

The contractor shall provide to the Government required source data to support the CCR, DDS, and Systems…