APPENDIX_A_SOW.pdf

PDF 203 KB Posted

Attached to
KC-135 Aero-I SATCOM Replacement Federal contract opportunity
Solicitation number
KC-135_Aero-I
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Tinker Air Force Base

About this file

This document provides a statement of work for the KC-135 Aero-I Satellite Communications replacement program. The statement of work details requirements for replacing the aging INMARSAT Aero-I SATCOM system currently used on C/KC-135 aircraft with a new Iridium SATCOM system. Key requirements include integrating and testing the new SATCOM system in a software integration laboratory, producing group A and B kits for installation, conducting developmental and operational testing on two aircraft, and providing contractor field teams to install the new system on approximately 359 USAF aircraft and up to 10 foreign military sales aircraft between 2023 and 2025. The contractor must also produce technical orders and data to support installation of the new system through programmed depot maintenance.

Statement of Work

View the file

Other files for this federal contract opportunity

Other files attached to KC-135 Aero-I SATCOM Replacement, newest first.
File Type Posted
UPDATED_5-_Vendor_Questions_and_Government_Responses_04_Nov_19.pdf PDF
UPDATED_4-_Vendor_Questions_and_Government_Responses_29_Oct_19.pdf PDF
UPDATED_3-_Vendor_Questions_and_Government_Responses_10_Oct_19.pdf PDF
UPDATED_2-_Vendor_Questions_and_Government_Response_30_SEP_19.pdf PDF
UPDATED-Vendor_Questions_and_Government_Responses_26_SEP_19.pdf PDF
ATTACHMENT_2_Section_M_EVALUATION_FACTORS_REV_A.pdf PDF
APPENDIX_A_SOW_REV_A.pdf PDF
ATTACHMENT_3_PRICING_MATRIX_REV_A.xlsx XLSX spreadsheet
FA810519R0005_______0001.pdf PDF
Vendor_Questions_and_Government_Responses_10_SEP_19.pdf PDF
APPENDIX_C_CSDR_Plan.pdf PDF
APPENDIX_B_SRD.pdf PDF
EXHIBIT_A_CDRLs.pdf PDF
APPENDIX_C_CSDR__DD2794_Attachment.xlsx XLSX spreadsheet
EXHIBIT_A_CDRLs.zip ZIP file
ATTACHMENT_3_PRICING_MATRIX.xlsx XLSX spreadsheet
ATTACHMENT_2_Section_M_EVALUATION_FACTORS.pdf PDF
FA810519R0005.pdf PDF
ATTACHMENT_1_Section_L_Instructions_to_Offerors.pdf PDF
EXHIBIT_A_DIDs.pdf PDF
AERO-I_Additional_Questions_and_Responses.pdf PDF
Synopsis_-_Aero-I.pdf PDF
Aero-I_Pre-Solicitation_Attendee_List-_16_May_2019.pdf PDF
Pre-Solicitation_Q&A's_(Round_2).pdf PDF
ppi_tool.accdb MDB file
Pre-Solicitation_Questions_-_Post_to_FBO_(Updated).pdf PDF
Pre_Solicitation_Conf_-_Aero-I_DRAFT_-_FINAL.pdf PDF
SRD.pdf PDF
Section_L_Pricing.xlsx XLSX spreadsheet
FA810519R0005V19.pdf PDF
Section_M.pdf PDF
SOW.pdf PDF
CDRLs.pdf PDF
KC135_AERO_I_Contract_CSDR_Plan.xls XLS spreadsheet
Registration_Form.docx DOCX document
Section_L.pdf PDF
AERO-I_Industry_Day_Slides.pdf PDF
AERO-I_Replacment_Industry_Day_Registration_Form.pdf PDF
Show all 38

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

APPENDIX A

Statement of Work - AERO-I SATCOM Replacement

Statement of Work for

C/KC-135 Aero-I Satellite Communications (SATCOM) Replacement Program

Permanent Modification for the

C/KC-135

Preparation Date: 08 August 2019

Purchase Request No.: FD2030-20-30019

PREPARING ORGANIZATION: AFLCMC/WKDM TINKER AFB OK 73145

Table of Contents 1 Scope

Background

2 Applicable Documents Department of Defense (DoD) Specifications

Department of Defense Standards

Industry Publications

3 Requirements Group A and B Kits

Open Skies Aircraft

Foreign Military Sales (FMS) Participation

Aircraft Integration and Installation Strategy

Software Integration

Contract Data Requirements List (CDRL)

Cost and Software Data Reporting (CSDR)

Program Management

Conferences and Reviews

3.9.1 Post Award Conference (PAC)

3.9.2 Technical Order (TO) Guidance Conference

3.9.3 Program Management Reviews (PMR)

Technical Requirements/Reviews

3.10.1 Systems Requirement Review (SRR)

3.10.2 Integrated Test Team (ITT)

3.10.3 Cybersecurity Technical Interchange Meeting (TIM)

Integration

3.11.1 Preliminary Design Review (PDR)

3.11.2 Critical Design Review (CDR)

3.11.3 TO In-Process Reviews (IPR)

3.11.4 Environmental Test Reports

Configuration Management (CM)

3.12.1 Engineering Change Proposals (ECP)

Over and Above – Labor

Over and Above – Material

4 Test

Software Integration Laboratory (SIL) Testing

Test Readiness Review (TRR)

Developmental Test (DT) and Operational Test (OT)

4.3.1 Test Plan

TO Verification/Certification

Test Close Out

Combined Functional Configuration Audit, (FCA), System Verification Review (SVR), and Product Readiness Review (PRR)

5 Production Identification Marking Requirements

Item Unique Identification (IUID) Requirements

Estimated Production and Delivery

Physical Configuration Audit (PCA)

Packaging and Handling – PDM Installation

Warranty

6 Installation CFT Installation

6.1.1 Disposition Instructions

6.1.2 Verification of Installation

6.1.3 Travel

PDM Installation – US Aircraft Only

Government Furnished Information

7 Contract Closeout

1 Scope This Statement of Work (SOW) defines the work to be performed by the contractor to identify, develop, integrate, and test a Commercial Off-the-Shelf (COTS) Iridium Satellite Communication (SATCOM) system to replace the current C/KC-135 International Marine/Maritime Satellite (INMARSAT) satellite system on an estimated 359 USAF aircraft and up to 10 Foreign Military Sales (FMS) aircraft. The SATCOM replacement must be compatible with both Block 40 and Block 45 aircraft. Work will include integration of the COTS SATCOM system in Collins Aerospace’s Software Integration Facility (SIL) in Cedar Rapids, Iowa, support of aircraft testing, production of Group A and Group B kits, as well as Contractor Field Team (CFT) installation of the SATCOM replacement on aircraft. The contractor shall also produce a comprehensive engineering package to support Programmed Depot Maintenance (PDM) installation of the satellite system.

Background The C/KC-135 currently utilizes the INMARSAT organization’s Aeronautical Intermediate (Aero-I) service as part of its Global Air Traffic Management (GATM) system. Aero-I provides oceanic Controller/Pilot Data Link Communications (CPDLC) to Air Traffic Control (ATC) and Aircraft Communications Addressing/Reporting System (ACARS) Beyond Line-Of-Sight (BLOS) messages to 618 Tanker Airlift Control Center (TACC) Global Decision Support System. The SRT-2000 SATCOM Transceiver Part Number (P/N) 822-1346-001 and IGA-2000 SATCOM Antenna P/N: 822-1369-001 are installed on the aircraft and provide the required communications path. Both of these items are becoming increasingly unsupportable, causing increased maintenance and Mission Impaired Capability Awaiting Parts (MICAP) hours.

2 Applicable Documents The following documents are applicable to this SOW.

Department of Defense (DoD) Specifications Unless otherwise indicated, copies of specifications, standards and handbooks listed below are available from the Standardization Document Order Desk, 700 Robbins Ave, Bldg 4D, Philadelphia PA 19111-5094.

Department of Defense Standards

AFI 63-137 Communications, Navigation, Surveillance/Air Traffic Management

(CNS/ATM)

DoD 5000.04-M-1 Cost and Software Data Report (CSDR) Manual

MIL-HDBK-61A Configuration Management Guidance MIL-HDBK-516C Airworthiness Certification Criteria MIL-STD-129P Military Marking for Shipping and Storage MIL-STD-130N DOD Standard Practice Identification

Marking of U.S. Military Property MIL-STD-881D Standard Practice for Work Breakdown

Structures for Defense Material Items MIL-STD-882E System Safety MIL-STD-2073-1D Standard Practice for Military Packaging

Industry Publications

ARP4761 Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment

ASTM-D-3951 Commercial Packaging RTCA DO 160G Environmental Conditions and Test

Procedures for Airborne Equipment SAE AS50881 Wiring Aerospace Vehicle SAE AS-9132 Data Matrix Quality Requirements for

Parts Marking SAE E1A649-1 Configuration Management Requirements for Defense Contracts

NIST Special Publication 800-171r1 Protecting Controlled Unclassified Information in Nonfederal systems and Organizations

3 Requirements The contractor shall accomplish the integration, test, procurement and installation of an Iridium SATCOM replacement system for Block 40 and Block 45 C/KC-135s. The contractor shall meet all of the requirements detailed in the C/KC-135 Aero-I SATCOM Replacement Program System Requirements Document (SRD). The contractor shall provide two permanently modified aircraft as a first article delivery for one (1) Block 40 and one (1) Block 45 configuration. The contractor shall include small business participation of at least 8% of the total proposal price.

Group A and B Kits

The government defines a Group A kit as consisting of cables, wiring harness, antenna mount, and associated hardware. The government defines a Group B kit as consisting of a transceiver and antenna. The contractor shall ensure both Group A and Group B kits are free of Diminishing Manufacturing Sources and Material Shortages (DMSMS). The contractor shall deliver DMSMS reports as required. The USAF requirement is based on a 10 percent sparing for the Group B kit and no sparing for the Group A kit. The FMS requirement is based on one (1) spare Group B kit for each country and no sparing for the Group A kit. The contractor shall provide required kitting as directed by delivery orders.

(A044)

Open Skies Aircraft The contractor shall integrate the proposed solution on the two (2) Open Skies OC-135 aircraft. The Open Skies aircraft are included as part of the estimated 359 USAF aircraft requirement. There is no requirement for specific OC-135 testing in the SIL. However, integration with the OC-135 shall be incorporated as part of the Block 40 engineering package. OC-135 installation will be accomplished in PDM, however the government reserves the right to change the installation method to CFT.

Foreign Military Sales (FMS) Participation The contractor shall plan to integrate the proposed solution on up to 10 aircraft in support of the following FMS customers:

Country # of Aircraft Configuration Software Version

Turkey 7 Block 40 40.6.3

France 3 Block 40 40.6.3

Note that Turkey will begin transition to software version 45.1.1 in calendar year 2021.

FMS participation in the program has not yet been determined.

Aircraft Integration and Installation Strategy The contractor shall provide the aircraft transceiver and antenna integration strategy at the Preliminary Design Review (PDR).

The contractor shall consider utilization of Contractor Field Teams (CFT) and Programmed Depot Maintenance (PDM). The government will schedule and conduct PDM installations. The contractor shall produce and deliver Group A kits and Group B kits as ordered according to the established delivery schedule. The government intent is to utilize the maximum number of PDM for organic installation during years 3-5 of the contract, which equates to 75 aircraft per year for a total of 225 aircraft. The government intent is the remaining 134 installations shall occur via CFT.

The contractor’s strategy shall include the following analyses:

a. Structural

b. Electrical load

c. Antenna fluid dynamics

d. Spectrum analysis of the Electromagnetic Interference/Electromagnetic

Compatibility (EMI/EMC) characteristics of the replacement antenna

The contractor’s strategy shall incorporate a Polyurethane Conductive Antenna Gasket between the antenna and the aircraft mounting plates.

The integration, Group A kit and Group B kit production, and installation of FMS aircraft are in addition to this strategy and are as directed by delivery order.

Software Integration As the sole source avionics integrator for the C/KC-135, the contractor shall coordinate with Collins Aerospace for software integration and SIL testing. The contractor shall;

a) Provide four (4) SATCOM transceivers and four (4) antennas to the Collins Aerospace Software Integration Laboratory at Cedar Rapids no later than PDR

b) Design and deliver the SIL specific hardware needed to install transceivers and antenna in the SIL

c) Modify four (4) test lines at Collins Aerospace’s SIL (two (2) Block 40 and two

(2) Block 45) to enable over-the-air transmission testing to the Communication, Navigation, and Surveillance/ Air Traffic Management (CNS/ATM) and TACC.

The contractor shall modify one (1) Block 40 and one (1) Block 45 test line for integration testing at a time which conforms to the Integrated Program Management Plan (IPMP). The remaining two (2) test lines shall be modified by the end of the contract delivery schedule, as the SIL testing schedule allows.

d) Tailor CNS/ATM matrices for Iridium satellite communications, and ensure KC- 135 CNS/ATM recertification. The government will acquire the CNS/ATM certification in accordance with AFI 63-137 using the contractor-provided matrices. (A020)

e) The contractor shall integrate Iridium SATCOM capabilities into the Block 40 and Block 45 C/KC-135 aircraft and produce a black label Operational Flight Program (OFP) software release for each aircraft block. The Block 40 configuration shall be baselined on OFP 40.6.3 and included in OFP 40.7. The Block 45 configuration shall be baselined on OFP 45.1.1 and included in OFP 45.3.

Once installed, all delivered hardware shall remain in the SIL as government property.

Software integration efforts for FMS aircraft are as required and in addition to the above effort as directed by delivery order.

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.

Contract Data Requirements List (CDRL) A list of data requirements contained in this SOW can be found in Table 1 and each SOW paragraph references specific data requirements at the end of each applicable paragraph.

The contractor shall upload all CDRL deliverables into Lifecycle Management Program (LCMP). The government will provide access to LCMP not later than ten (10) business days after contract award. All CDRLs shall be delivered in accordance with the DD Form 1423s. CDRL deliverables referenced as “Draft” will be considered a 100% draft meaning that all applicable information the contractor has at the time the data requirement is to be delivered is included in the document. The contractor shall deliver a Data Accession List (DAL) monthly. (A038)

Table 1. Contract Data Requirements List

A001 Conference Agenda A002 Presentation Materials A003 Conference Minutes A004 Integrated Program Management Plan A005 Technical Manual Contractor Requirements A006 Commercial Drawings/Models and Associated Lists A007 System Security Management Plan A008 Level 1 System Specification A009 Level 2 Subsystem Specifications A010 Level 3 Subsystem Specifications A011 Systems Engineering Management Plan A012 Aircraft Test Cards A013 Integrated Test Management Plan A014 Interface Control Document A015 System Requirements Verification Matrix A016 Modified Airworthiness Certification Criteria A017 Human Engineering Design Approach Document - Operator A018 Contractor’s Risk Management Plan A019 A-Kit Engineering Drawings A020 CNS/ATM Certification Matrices

A021 Safety Assessment Report A022 System Safety Hazard Analysis Report A023 Aircraft Test Plan A024 Contract Summary Report A025 Software Test Report A026 Management Plan A027 Architectural Analysis Report A028 Cybersecurity Assessment Test Plan A029 Cybersecurity Assessment Test Report A030 Configuration Audit Plan A031 Item Unique Identification Marking Plan A032 Item Unique Identification Marking Activity, Validation & Verification A033 Engineering Change Proposal A034 Software Version Description A035 Installation Completion Notification A036 Configuration Audit Summary Report and Certification A037 Engineering Change Proposal System Safety Report A038 Data Accession List A039 Cost Data Summary Report A040 Functional Cost-Hour Report A041 Progress Curve Report A042 Contractor Business Data Report A043 Contract Work Breakdown Structure

A044 Diminishing Manufacturing Sources and Material Shortages (DMSMS) Health Analysis Report

Cost and Software Data Reporting (CSDR)

The contractor shall systematically collect and report actual contract costs to provide DoD cost analysts with data necessary to estimate the costs of ongoing and future government programs. CSDRs shall be prepared in accordance with the instructions contained in the most recently approved versions of the data item descriptions (DIDs), DI-FNCL-81565C, DI-FNCL-81566C, DI-FNCL-81567C, DI-FNCL-81765B, and DI- MGMT-81334D, as applicable. (A039, A040, A041, A042, A043)

In the performance of this contract, the contractor shall use:

a. A documented standard CSDR process that satisfies the guidelines contained in the DoD 5000.04–M–1 (CSDR Manual), and the DIDs;

b. Management procedures that provide for generation of timely and reliable information for the contractor cost data reports (CCDRs) and software resources data reports (SRDRs) required by the CCDR and SRDR data items of this contract;

c. The most recently Government-approved CSDR plan for this contract, DD Form 2794, and the most recently approved CSDR DIDs; and

d. The contractor shall require and flow down the requirement for CSDR reporting from subcontractors at any tier with a subcontract that exceeds $50 million or any subcontracts valued between $20 million and $49 million that are designated by the government as being high risk, high value, or high technical interest. If, for subcontracts that exceed $20 million, the contractor changes subcontractors or makes new subcontract awards, the contractor shall notify the government.

Program Management The contractor shall designate a Single Point of Contact (SPOC) for all tasks required for the program. The contractor SPOC shall have responsibility and authority for the control and coordination of all contractor work performed under this SOW. The contractor shall also submit a management plan describing the contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs. (A026)

Conferences and Reviews The contractor shall provide necessary support for Program Management Reviews (PMR), Technical Interchange Meetings (TIM), Technical Reviews, and Conferences.

The contractor shall provide agendas, presentation material, and minutes of these meetings. The contractor shall host government reviews as described below. The contractor shall host reviews at the contractor or sub-contractor facilities. The contractor shall ensure agenda items include, but are not limited to, contract status and updates as it relates to cost, schedule, and performance. (A001, A002, A003)

3.9.1 Post Award Conference (PAC)

The contractor shall conduct a PAC not later than 45 calendar days after contract award.

The PAC shall include a discussion of the contractor and applicable subcontractors’ standard cost and software data reporting (CSDR) processes that satisfy the guidelines contained in the DoD 5000.04-M-1 (CSDR Manual), and the requirements in the government-approved CSDR plan for the contract, DD Form 2794, and related Resource Distribution Table (RDT). At this conference, the contractor shall provide a baseline program schedule. The contractor agenda shall address and provide details to their understanding of the contract requirements and interpretation of the CDRLs at Table 1.

(A001, A002, A003, A004, A026)

3.9.2 Technical Order (TO) Guidance Conference

The contractor shall, along with the C/KC-135 Technical Order Management Agency (TOMA), co-host a TO guidance conference for this effort to be held in conjunction with the PAC. The contractor shall provide a briefing on their interpretation of the Technical Manual Contract Requirement (TMCR), basic contract, Military Specifications (MIL-

SPEC), Military Standards (MIL-STD), and the planned preparation and delivery of the TOs and related data. (A001, A002, A003, A005)

3.9.3 Program Management Reviews (PMR)

The contractor shall provide PMRs by teleconference or in combination with another scheduled meeting/review to capture program status. The PMRs shall occur quarterly until the last CFT installation has been evaluated and accepted. (A001, A002, A003)

Technical Requirements/Reviews

3.10.1 Systems Requirement Review (SRR)

The contractor shall conduct an SRR. All documents need to be provided not later than the date specified in the CDRL. (A001, A002, A003) Entry Criteria:

a. System Security Management Plan (SSMP) (Draft) (A007) Contains the data content, format, and intended use of the Contractor's system security plan (or extracts thereof), to include any associated plans of action, addressing the Contractor’s internal unclassified information system(s).

b. Level 1 Systems Specification (SS) (Draft) (A008) The SS specifies the requirements for a system or subsystem and the methods to be used to ensure that each requirement has been met.

c. Systems Engineering Management Plan (SEMP) (Final) (A011)

d. Provide Risk Management Plan (Final) (A018)

The contractor's Risk Management Plan will be used to monitor management and schedule of the contract efforts relative to a system and equipment. This information shall provide the government with risk data for all risks associated with the system/equipment.

3.10.2 Integrated Test Team (ITT)

The contractor shall support at least three (3) ITT meetings by teleconference to coordinate actions as necessary to complete Iridium SATCOM system test activities in accordance with contract schedule. Meeting frequency as determined at PAC. (A001, A002, A003)

3.10.3 Cybersecurity Technical Interchange Meeting (TIM)

The contractor shall support development of cybersecurity draft information covering the SATCOM replacement system to assist in updating platform security documents. The contractor shall provide quarterly government-led cybersecurity TIMs support to the KC- 135 Information System Security Manager (ISSM). The contractor shall provide status updates of all cybersecurity deliverables. (A001, A002, A003)

Integration

3.11.1 Preliminary Design Review (PDR)

The contractor shall conduct a PDR. This System Engineering milestone review shall have entry and exit criteria, based on the C/KC-135 Legacy Tanker System Engineering Plan (SEP)/SEMP as defined during the PAC requirements review. Successful completion of PDR will be defined by government concurrence with the proposed technical solution, as well as government approval of all supplied CDRLs. The contractor shall provide all documents not later than the date specified in the CDRL. (A001, A002, A003) Entry Criteria:

a. Certification and Verification (Cert/Ver) approach for TCTO and all TOs (A005)

b. Technical Manual Schedule and Status (TMSS) (Draft) (A005)

c. Provide Commercial Drawings/Models and Associated Lists. (Final) (A006)

Commercial Drawings/Models and Associated Lists define commercial items acquired by the Department of Defense.

d. SSMP (Final) (A007)

e. Level 1 SS (Final) (A008)

f. One (1) Level 2 Subsystem Specifications for each modified hardware or software subsystem (Draft) (A009) The Subsystem Specifications specifies the requirements for a system or subsystem and the methods to be used to ensure that each requirement has been met.

g. Integrated Test Management Plan (ITMP) (Draft) (A013) The ITMP presents a general outline for a total test for a system for the testing and evaluation conducted during development, and coordinates the engineer and service tests.

h. Interface Control Document (ICD) (Draft) (A014) The Interface Control Document (ICD) provides a record of all interface information (such as drawings, diagrams, tables, and textual information) generated for the project

i. System Requirements Verification Matrix (SRVM) (Draft) (A015) The Specification Requirement Verification Matrix provides traceability between the Test Requirements Document (TRD) or procedure (similarity analysis or inspection test methods) and the Prime Item Development Specification (PIDS) requirements.

j. Military Airworthiness Certification Criteria (MACC), Certification Basis (Draft) (A016) The contractor shall develop a Modification Airworthiness Certification Criteria (MACC) as defined in MIL-HDBK-516C for the C/KC-135 Iridium SATCOM system and identify the C/KC-135 Airworthiness Certification Criteria for applicability to this effort. The contractor shall evaluate airworthiness risks for the applicable criteria and determine if the refreshed SATCOM system is reportable or non-reportable. The government will attain airworthiness certification using the

MACC.

k. Human Engineering Design Approach Document – Operator (HEDAD-O) (Draft) (A017) The Human Engineering Design Approach Document–Operator (HEDAD-O) describes equipment that interfaces with operators. This document provides a source of data to evaluate the extent to which equipment having an interface with operators meets human performance requirements and human engineering criteria, and provides the human engineering rationale for the design.

l. Risk Management Updates (A018)

m. CNS/ATM Matrices (Draft) (A020)

n. System Safety Hazard Analysis (SSHA) (Final) (A022)

The contractor shall perform activities in accordance with MIL-STD-882E or ARP 4761 and shall generate a System Safety Hazard Analysis (SSHA) to identify any hazards associated with the project.

o. Cybersecurity Assessment Test Plan (Final) (A028)

p. Cybersecurity Assessment Test Report (Final) (A029)

3.11.2 Critical Design Review (CDR)

The contractor shall conduct a Critical Design Review (CDR). This System Engineering milestone reviews shall have entry and exit criteria based on the SEP/SEMP as defined during the PAC requirements review. The contractor shall provide all documents not later than the date specified in the CDRL. (A001, A002, A003) Entry Criteria:

a. Field/Depot Installation/Removal plan shall include strategy for the removal of the legacy systems (TCTO) (Draft) (A005)

b. Temporary Modification (T2) Plan (Draft) (A005)

c. Cert/Ver approach for TCTO and all TOs (Update) (A005)

d. One (1) Level 2 Subsystem Specifications for each modified hardware or software subsystem (Final) (A009)

e. One (1) Level 3 Subsystem Specifications for each modified hardware or software subsystem (Draft) (A010)

f. Integrated Test Management Plan (Final) (A013)

g. Interface Control Document (Final) (A014)

h. SRVM (Draft) (A015)

i. MACC, Certification Basis and Experimental Flight Release Basis (Draft) (A016)

j. Human Engineering Design Approach Document – Operator (HEDAD-O) (Draft)

(A017)

k. Risk Management Updates (A018)

l. CNS/ATM Matrices (Draft) (A020)

m. Safety Assessment Report (SAR) (Draft) (A021)

The Safety Assessment Report (SAR) is a comprehensive evaluation of the safety risks being assumed prior to test or operation of the system or at contract completion. The SAR shall identify all safety features of the system, design, and procedural hazards that may be present in the system being acquired, and specific procedural controls and precautions that should be followed.

n. Aircraft Test Plan (ATP) (Draft) (A023)

o. Architectural Analysis Report (Draft) (A027)

3.11.3 TO In-Process Reviews (IPR)

The contractor shall host 75%, 90%, and 100% TO in-process reviews as defined in the Technical Manual Contractor Requirements (TMCR). (A005)

3.11.4 Environmental Test Reports

The contractor shall provide the government with the SATCOM manufacturer’s DO- 160G test report as tailored in the SRD for the transceiver and antenna. (A006)

Configuration Management (CM) The contractor shall implement CM processes to control all aspects of the SATCOM replacement effort, to include but not be limited to all Hardware Configuration Items (HWCI), Computer Software Configuration Items (CSCI), Firmware Configuration Items (FWCI), and Line Replaceable Units (LRU) documentation and processes, IAW ANSI/EIA 649B and the MIL-HDBK-61A. The CM process shall include specific processes for identification of changes which may instigate engineering change proposals or deviations from designs and architectures presented to or reviewed by the government. The contractor shall integrate and execute a multiple configuration baseline management approach in the software development process and system engineering approach to support parallel Block 40 and 45 efforts.

3.12.1 Engineering Change Proposals (ECP)

Any change which affects the form, fit function, cost or schedule requirements of the system (Class 1 or major change), shall be prepared as an ECP, and the contractor shall submit ECPs to the government for approval. The contractor shall follow guidance per ANSI/EIA 649B and MIL-HDBK-61A for any necessary ECPs. Class II or Minor changes prepared as ECPs do not require government approval but shall be presented to the government for concurrence of change class designation, i.e. Class I or Class II change. The contractor shall submit ECP System Safety Report (ECPSSR) as required.

(A033, A037)

Over and Above – Labor The contractor shall submit over and above work requests and proposals to the Contracting Officer (CO). The contractor shall not begin work until authorized by the CO in writing.

Over and Above – Material The contractor shall submit over and above work requests and proposals to the CO. The contractor shall not begin work until authorized by the CO in writing.

4 Test

Software Integration Laboratory (SIL) Testing The contractor shall:

a. Use OFP 40.6.3 and OFP 45.1.1 as the baseline for software integration with the goal of delivering a black label software release, along with an applicable Software Version Description (SVD) document, to the government. (Final) (A034)

b. Perform testing of the integrated software changes in the SIL

c. Coordinate with the government on deficiencies encountered during testing, correct deficiencies and perform any required regression testing.

d. Verify Iridium SATCOM system performance and CNS/ATM compliance via

Over the Air testing in the SIL

e. Provide a SIL system test report to the government. (Final) (A025)

Testing at the Collins Aerospace SIL for FMS countries will be as directed in the delivery orders. For planning purposes, SIL testing will not be required for Turkey since their software configuration is compatible with the US Block 40 configuration. For planning purposes, testing at the Collins Aerospace SIL will be required for France due to inconsistencies with the US Block 40 configuration.

Test Readiness Review (TRR) The contractor shall conduct a Test Readiness Review (TRR) to demonstrate system maturity, results of SIL testing, and provide first article aircraft readiness. This includes an Aircraft Modification Readiness Review (AMRR). The following shall be delivered not later than 30 calendar days prior to the TRR unless otherwise noted. (A001, A002, A003)

a. T2 Installation/Removal Instructions (Draft) (A005)

b. Installation/Removal Instructions (TCTO) (Draft) (A005)

c. Post Installation/Removal Checkout Instructions (Final) (A005)

d. One (1) Level 3 Subsystem Specifications for each modified hardware or software subsystem (Final) (A010)

e. Aircraft Test Cards (Final) (A012)

f. SRVM (Final) (A015)

g. MACC First Flight Compliance Report (Draft) (A016)

h. A-kit Engineering Drawings (Draft) (A019)

The Technical Data Package contains a technical description of an item suitable for use as the basis for future competitive acquisition, production, installation, modification, engineering support, maintenance and logistics support of military material developed by or for the Department of Defense.

i. SAR (Final) (A021)

j. Aircraft Test Plan (ATP) (Final) (A023)

k. Architectural Analysis Report (Final) (A027)

Developmental Test (DT) and Operational Test (OT)

The contractor shall:

a. Install one Group A and Group B kit onto a Block 45 KC-135 aircraft, and one

Group A and Group B kit onto a Block 40 KC-135 aircraft

b. Support final verification of Test Cards with Lead Developmental Test

Organization (LDTO) prior to DT&OT

c. Perform DT on USAF supplied Block 40 and Block 45 aircraft at a designated

USAF site

d. Analyze test deficiencies, present analysis to government for coordination and correct coordinated deficiencies

e. Provide engineering support to OT via phone

f. If determined at PDR, remove all installed Group B kits, from the aircraft, after the completion of DT&OT

DT&OT is planned to occur at Scott Air Force Base, Illinois, but subject to change to another location within the Continental United States. The government will provide the test dates to the contractor after the Test Readiness Review.

4.3.1 Test Plan

The contractor shall deliver draft and final Developmental Test & Evaluation (DT&E) Aircraft Test Plan and Test Cards for both C/KC-135 Block 40 and Block 45 aircraft configurations. (A012, A013, A023)

TO Verification/Certification The contractor shall support the Air Force verification of all Group A kit drawings, Group A and Group B kit installation drawings, Group A and Group B kits, TO Source Data, and TCTOs at the completion of aircraft test. The contractor shall assist with verification by identifying assets required to accomplish the efforts and provide a technical writer and engineering support for each verification. The contractor shall incorporate approved verification comments. (A005)

Test Close Out The contractor shall provide aircraft test results and final copies of all technical data (engineering drawings, installation drawings, wire routing drawings, technical orders and the TCTO) before the beginning of PDM and CFT installs.

a. MACC Compliance Report (Final) (A016)

b. HEDAD-O (Final) (A017)

c. A-kit Engineering Drawings (Final) (A019)

d. CNS/ATM Matrices (Final) (A020)

e. STR (Final) (A025)

Combined Functional Configuration Audit, (FCA), System Verification

Review (SVR), and Product Readiness Review (PRR) The C/KC-135 Program Office (PO) will conduct and the contractor shall support an FCA/SVR/PRR at contractor’s/subcontractor’s site after Test Close Out to verify the system’s performance and compliance with the requirements and the government CDR specification. The PO will notify the contractor of scheduled PRR no later than thirty

(30) calendar days prior to allow adequate time to prepare travel plans. The government will provide an agenda no later than ten (10) business days prior to the PRR. At the conclusion of the PRR, the contractor shall provide a Configuration Audit Summary Report and the government will approve procurement of production assets. (A036)

5 Production

Identification Marking Requirements The contractor shall mark all items IAW MIL-STD-130N.

Item Unique Identification (IUID) Requirements The contractor shall provide an IUID Marking Plan and an IUID Verification Report.

(A031, A032)

Estimated Production and Delivery The contractor shall provide Group A kits and Group B kits to the government in accordance with the contract schedule and delivery orders. The contractor shall provide details of how they will meet the installation schedule via an Integrated Master Schedule.

(A004)

The purchase quantity per contract year for the US and FMS is subject to change based on funding authorizations. The FMS funding is dependent upon the timing of when FMS countries sign and return an International Program Directive (IPD) to the KC-135 FMS International Acquisition Program Office to allow case execution. The FMS funding dates are not currently defined.

Physical Configuration Audit (PCA) The government will conduct, with contractor participation, a 100% configuration audit of the two (2) Group A kits to be installed as part of the first article delivery to verify the actual configuration meets the provided drawing and technical data package specifications. The contractor shall provide a Configuration Audit Plan when ready for PCA. The contractor shall host the PCA at the contractor’s facility and will be operated IAW MIL-HDBK-61A. The contractor shall ensure that the PCA audits result in wiring, cables, and cable bundles pass continuity checks IAW SAE AS50881. (A030)

Packaging and Handling – PDM Installation

The contractor shall package the Group A kits and Group B kits marked for Programmed Deport Maintenance (PDM) installations in accordance with ASTM-D-3951, Commercial Packaging or MIL-STD-2073-1D, the Standard Practice for Military Packaging. The contractor shall mark the packages for shipping and storage in accordance with MIL-STD-129P, Military Marking for Shipment and Storage, and ship them as cited on the individual order.

The contractor shall provide via email commercial shipping documentation or provide shipping information on a DD Form 1149, Requisition and Invoice/Shipping Document for each production kit shipment as identified on each individual order. The USAF and the FMS Point of Contact (POC) will be identified and provided to the vendor on each delivery order. All shipments will be CONUS.

Warranty The contractor shall provide a minimum one-year (12 Month) warranty IAW FAR Part 52.246-17 Warranty of Supplies of a Noncomplex Nature.

6 Installation Table 2 shows the estimated number of aircraft to be installed during each contract year.

Table 2. Government Schedule

Contract Year 1

Contract Year 2

Contract Year 3

Contract Year 4

Contract Year 5

Integration & Testing 2 Installation – US Aircraft

(CFT) 27 36 36 35

Installation – US Aircraft

(PDM) 75 75 75

Installation – France 1 1 1 Installation – Turkey 3 2 2

CFT Installation

The government will provide an installation schedule that details the location and number of aircraft to be installed. The preliminary schedule will be established at the PAC and finalized after first article delivery and acceptance of both the Block 40 and Block 45 aircraft. The CFT installation is anticipated to be scheduled at a rate of three (3) aircraft per month in contract years 2-5, which provides flexibility for less or more installations at the government’s discretion. For planning purposes, each CFT installation shall occur on separate days and separate visits. The government will attempt to schedule multiple aircraft for installation at the same location, mission availability permitting. The CFT installation shall not exceed 30 consecutive hours after receipt of each aircraft, to include sealant cure time. The government will provide a POC at every installation location. The government will provide an in-brief upon arrival at each location consisting of local procedures and policies. The contractor shall be responsible for:

a. The removal and disposition of the existing transceiver, antenna, and associated wiring and hardware.

b. The installation of the replacement transceiver, antenna, and associated wiring and hardware.

c. The installation of the updated OFP.

d. The operational check and installation verification of the system.

CFT installation for FMS aircraft is anticipated to be scheduled in contract years 3-5.

6.1.1 Disposition Instructions

The contractor shall be responsible for the packaging and shipment of the removed antenna (NSN 5985-01-484-1767BY) and transceiver (NSN 5895-01-507-3889CX). All assets must be returned in their own individual shipping container (1 ea. per container) with the NSN clearly marked on the outside of the shipping container. The antenna (NSN 5985-01-484-1767BY) must be shipped in a container measuring at least 30 inches long by 14 inches wide and 5 inches high with a foam insert that is cut to fit the antenna securely to avoid damage to the asset during shipment. The transceiver (NSN 5895-01- 507-3889CX) must be shipped in a container measuring at least 17 inches long by 12 inches wide and 9 inches high with a foam insert that is cut to fit the transceiver securely to avoid damage to the asset during shipment. Return all reclaimed assets to the following address in “F” condition code:

SW3119

DLA Distribution Warner Robbins 455 Byron Street Bldg 376 Robins AFB, GA 31098-1887

Disposition instructions for FMS aircraft may vary and shall be followed in accordance with the delivery order.

6.1.2 Verification of Installation

The government considers an installation to be acceptable once all procedures from the TCTO have been accomplished and validated by a government representative via DD Form 250. The contractor shall provide monthly updates regarding the status of installations completed. (A035)

6.1.3 Travel

CFT shall be ready to travel with qualified personnel and equipment as directed not later than 90 days after receipt of first installation delivery order or as directed by the government. The contractor shall not travel without coordination with the PO. The contractor shall submit a travel request to the contracting officer not later than 14 days prior to travel. The contractor shall be responsible for making travel arrangements to and from each location to include airfare, rental cars, and lodging as required. Government lodging is not guaranteed. When planning travel, the contractor shall follow the Joint Travel Regulations (JTR).

PDM Installation – US Aircraft Only

PDM installations are organic to the government. The contractor shall provide engineering support as required.

Government Furnished Information The government will provide access to current configuration drawings and technical orders (TOs) required to integrate and install the Group A kits and Group B kits.

7 Contract Closeout The contractor shall provide a contract summary report. (A024)

1.
1 Scope
1.1 Background
2 Applicable Documents
2.1 Department of Defense (DoD) Specifications
2.2 Department of Defense Standards
2.3 Industry Publications
3 Requirements
3.1 Group A and B Kits
3.2 Open Skies Aircraft
3.3 Foreign Military Sales (FMS) Participation
3.4 Aircraft Integration and Installation Strategy
3.5 Software Integration
3.6 Contract Data Requirements List (CDRL)
3.7 Cost and Software Data Reporting (CSDR)
3.8 Program Management
3.9 Conferences and Reviews
3.9.1 Post Award Conference (PAC)
3.9.2 Technical Order (TO) Guidance Conference
3.9.3 Program Management Reviews (PMR)
3.10 Technical Requirements/Reviews
3.10.1 Systems Requirement Review (SRR)
3.10.2 Integrated Test Team (ITT)
3.10.3 Cybersecurity Technical Interchange Meeting (TIM)
3.11 Integration
3.11.1 Preliminary Design Review (PDR)
3.11.2 Critical Design Review (CDR)
3.11.3 TO In-Process Reviews (IPR)
The contractor shall host 75%, 90%, and 100% TO in-process reviews as defined in the Technical Manual Contractor Requirements (TMCR). (A005)

3.11.4 Environmental Test Reports

3.12 Configuration Management (CM)
3.12.1 Engineering Change Proposals (ECP)
3.13 Over and Above – Labor
3.14 Over and Above – Material
4 Test
4.1 Software Integration Laboratory (SIL) Testing
4.2 Test Readiness Review (TRR)
4.3 Developmental Test (DT) and Operational Test (OT)
4.3.1 Test Plan
4.4 TO Verification/Certification
4.5 Test Close Out
4.6 Combined Functional Configuration Audit, (FCA), System Verification Review (SVR), and Product Readiness Review (PRR)
5 Production
5.1 Identification Marking Requirements
5.2 Item Unique Identification (IUID) Requirements
5.3 Estimated Production and Delivery
5.4 Physical Configuration Audit (PCA)
5.5 Packaging and Handling – PDM Installation
5.6 Warranty
6 Installation
6.1 CFT Installation
6.1.1 Disposition Instructions
6.1.2 Verification of Installation
6.1.3 Travel
6.2 PDM Installation – US Aircraft Only
6.3 Government Furnished Information

7 Contract Closeout

File details come from the government source that posted it. Updated .