Statement of Work.pdf

F15E Engineering Obsolescence Assessment 2400149 SOW

Statement of Work

Project: F15E Flight Control Computer (FCC) Engineering Obsolescence Assessment

Program Manager: Brooke Stroud

Period of Performance: 15 May 2024 – 15 May 2025

1. Background The Flight Control Computer (FCC) is an integral part of the AN/ASW51 Automa c Flight Control Set (AFCS), which along with sensors, servoactuators, and pilot controllers, provides aircra control along pitch, roll, and yaw axes. BAE Systems is the Original Equipment Manufacturer (OEM), developer, and producer of the FCC, which was developed specifically for the F15E’s mission and opera onal requirements. The FCC is expected to remain on the F15E fleet for its remaining lifecycle currently scheduled for 2045.

2. Objec ve/Purpose This Statement of Work (SOW) is for the Engineering Assessment for Obsolescence of Na onal Stock Number (NSN) 6615013527003, Flight Control Computer, which is applicable to the F 15E aircra . The purpose of this effort is for the contractor to do an indepth Engineering Assessment on the F15E FCC and provide the Government a way to con nue suppor ng the F 15E FCC with a Form, Fit, Func on, and Interface (F3I) obsolescence refresh. The contractor shall deliver an Engineering Assessment in the form of an Engineering Evalua on Report (EER) that will iden fy the level of effort for an obsolescence refresh of the FCC and a Rough Order of Magnitude (ROM) detailing associated costs and melines.

3. Tasks The contractor shall deliver an Engineering Assessment in the form of an Engineering Evalua on Report (EER) that will iden fy the level of effort for an obsolescence refresh that results in a F3I asset of the F15E FCC, NSN 6615013527003. The Engineering Assessment shall address piece part moderniza on and part availability that is fully compa ble to the specifica ons of the current NSN. The EER shall discuss the Engineering Assessment, detail how the contractor shall address the obsolete components’ issues/risks, the steps they’ll take to mi gate these issues/risks in the future F3I refresh effort, provide a ROM es mate for budgetary purposes, and upon receipt of an RFP provide a technical supplement to an official quote to follow. The ROM for the F3I F15E FCC Refresh shall include a breakdown of cost elements that includes but is not limited to: Engineering Support, Prototype Fabrica on, Technical Data, Tes ng, Develop & Design Prototype, & Travel along with the expected Period of Performance.

a. Obsolescence Correc on The Contractor shall review the exis ng cer fied equipment to iden fy obsolescence problems. The BAE EER may iden fy an upgrade path that provides an F3I compliant approach at the LRU level. The BAE solu on may iden fy an obsolescence mi ga on path that includes op mized CCAs.

b. Engineering Data All deliverable documenta on as specified herein (ref Sec on 4) created using Government funding as a result of this contract shall be delivered to the Government with unlimited rights.

c. Technical Interchange Mee ngs The Contractor shall support and cochair two (2) Technical Interchange Mee ngs with SCMS/GUEA. The first mee ng shall take place within 14 days of contract award. The mee ngs shall be convened virtually on an agreed upon date by the Government 409th

SCMS/GUEA and Contractor. The Government will prepare the mee ng.

The Contractor PM, or designee, will par cipate in all mee ngs, telecoms, and reviews held with the Government, as required. The Government shall no fy the Contractor of the me and loca on NLT 3 workdays prior to the event.

d. Rela onship of Subcontractor with Subcontractors/Vendors The Contractor shall levy on the subSubcontractors and subvendors the same requirements as are levied on them by this SOW. This requirement shall apply at all ers of Subcontractor/vendor levels associated with the program.

e. Security Requirements The actual knowledge and/or genera on of classified informa on and/or Controlled Unclassified Informa on (CUI) are not expected to be necessary for performance of the contract/order. Contractor personnel are required to comply with security requirements to preclude poten al security incidents or viola ons. If a change in the security classifica on of the contract/order becomes necessary a er contract/award, the Contractor shall make a reasonable effort to con nue performance of tasks under the contract/order in compliance with the change in security classifica on in accordance with FAR 52.2042, Security Requirements.

i. Security Regula ons The Contractor shall ensure personnel, informa on, system, property, facility and, if applicable, interna onal security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with the following security regula ons: Department of Defense (DoD) 5200.2R, Personnel Security Program; DoD 5220.22M, Na onal Industrial Security Program Opera ng Manual (NISPOM); DoD Direc ve (DoDD) 5205.02E, DoD Opera ons Security (OPSEC) Program; DoD Manual 5205.02M, DoD Opera ons Security (OPSEC) Program Manual; and Robins Air Force Base Integrated Defense Plan (RAFB IDP) 31101.

ii. Opera ons Security (OPSEC) The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collec on and exploita on of cri cal informa on. The Contractor shall comply with DoDD 5205.02E and DoD Manual 5205.02M to protect United States (U.S.) Government interests. The contractor shall ensure contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

iii. The Communica ons Security (COMSEC) The Contractor shall use only DoD SAFE to transmit or otherwise transfer Controlled Unclassified Informa on (CUI).

f. Cybersecurity The Contractor shall consider the impact to NSN design to implement cybersecurity features to ensure availability, integrity, authen ca on, confiden ality, and nonrepudia on [thereof]. The Contractor shall iden fy cybersecurity risks to the proposed system and document them in the whitepaper.

g. Access to Government Systems(s) Access to Government system(s) will not be required to perform tasks under the contract/order.

h. Access to Government Facility or Military Installa on Access to Government facility or military installa on will not be required to perform tasks under the contract/order.

4. Contract Data Requirements List(s) (CDRL) The following table provides a descrip on for each deliverable and the required No Later Than (NLT) delivery date.

Contract Line Item No.

Data Item Number

Deliverable Title Due Date SOW Para Reference

0002 A001 Engineering Evalua on Report

(EER)

305 days ARO a

0002 A002 Monthly Status Report 30 days ARO, and NLT the

5th day of the month therea er b

0002 A003 Official Quote (ROM) 305 days ARO c

0002 A004 Contractor Program Management Plan

30 days ARO d

a. Engineering Evalua on The Contractor shall evaluate all analysis data including obsolete components to determine the improvements that may be needed while maintaining F3I integrity at the SRU level. The evalua on may include but is not limited to parts obsolescence iden fica on and Reliability and Maintainability (R&M) analysis. The Contractor shall address the obsolete components’ issues/risks and the steps they shall take to mi gate these risks in the future obsolescence mi ga on solu on. The analyses and tests which are conducted shall be documented in an Engineering Evalua on Report (EER) for the specific type of equipment being reviewed. [CDRL A001]

b. Monthly Status Report Monthly Status Reports (MSR) shall include technical progress made, schedule status, travel conducted, mee ngs a ended, issues, and recommenda ons. The MSR is intended to report on schedule and performance against SOW requirements, providing informa on at the SOW task level. As such, it shall iden fy progress made and schedule status per deliverable, deliverables completed within the previous monthly repor ng period, and will indicate what deliverables are scheduled to be delivered during the upcoming monthly repor ng period. [CDRL A002]

c. Rough Order of Magnitude (ROM) The Rough Order of Magnitude (ROM) for the Replacement of NSN 6615013527003 shall include a breakdown of cost elements that includes but is not limited to Engineering Support, Prototype Design, Prototype Fabrica on, Technical Data, Tes ng, Develop & Design Prototype, & Travel along with the expected Period of Performance.

[CDRL A003]

d. Contractor Program Management Plan Within 30 business days of contract award, the Contractor shall provide a Program Management Plan (PMP) that es mates the sub task accomplishment and delivery date of each task assigned over the life of the contract. Although the PMP is an es mate, the Contractor shall make every effort reasonable to adhere to the plan. Changes to the PMP require wri en no fica on for approval of the change. [CDRL A004]

e. Quality of CDRL Deliverable The Government will reject a deliverable if three or more technical errors or five or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL or contract. A minor error is exemplified by a typographical error, a gramma cal error, etc. The rejected deliverable shall be corrected and resubmi ed within five business days of no fica on of Government rejec on.

f. Receipt of CDRL Deliverable CDRL deliverables shall be submi ed via DoD Safe and the customer approval email a achment submi ed directly to the iden fied personnel on the CDRL via Wide Area Work Flow (WAWF). There shall be no more than two late submission(s) of deliverables per contract period of performance. The Contractor shall no fy the Government if the delivery of any data/document will not meet the scheduled delivery date and nego ate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

g. Final Government Inspec on and Acceptance The Final acceptance of the CDRLs will occur via Work Area Work Flow (WAWF). The Government will have the right to reject or require correc on of any deficiencies. In the event of rejec on of the deliverable, the iden fied personnel on the CDRL will no fy the Contractor in wri ng of the specific reasons why the deliverable was rejected.

All documents shall be reviewed by the iden fied personnel on the CDRL. The Government will no fy the Contractor of any discrepancies within five workdays of receipt. The Contractor shall correct the discrepancies and resubmit within five workdays.