Boresight_System_SOW_15_Aug_2025_ATT2.docx

15 August 2025

Statement of Work (SOW) for

F-16 Boresight System

Prepared by

AFLCMC/ROZ SUPPORT EQUIPMENT & VEHICLES

235 BYRON STREET

BLDG 300 WEST WING, BAY D, SUITE 27A

ROBINS AFB GA 31098-1813

THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

1. SCOPE 6

2. APPLICABLE DOCUMENTS 6

3. DEFINITIONS

4. REQUIREMENTS 8

1. SCOPE

This document defines the tasks associated with the procurement of the F-16 Boresight System as described by PD24WRWNZEC004 and is to be used in conjunction with PD24WRWNZEC004.

2. APPLICABLE DOCUMENTS

The following documents are applicable to the SOW to the extent specified herein.

2.1 Government documents.

2.1.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks of the exact revision listed below form a part of this SOW to the extent specified herein.

FEDERAL STANDARDS

FED‑STD‑313F Material Safety Data, Transportation Data, and Disposal Data for Hazardous Materials Furnished to Government Activities

DEPARTMENT OF DEFENSE STANDARDS

MIL‑STD‑882E(1) System Safety

2.1.2 Other Government documents, drawings, and publications.

DATA ITEM DESCRIPTIONS (DIDs)

(Copies of these documents are available online at http://quicksearch.dla.mil/.)

DEPARTMENT OF DEFENSE MANUALS

TM-86-01R Air Force Technical Manual Contract Requirements

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY (NIST)

(Copies of this document are available online at https://nvlpubs.nist.gov/.)

PURCHASE DESCRIPTIONS

PD24WRWNZEC004 F-16 Boresight System

2.2 Non-Government publications. The following documents of the exact revision listed below form a part of this document to the extent specified herein.

SAE International

(Application for copies should be addressed to SAE International, Inc., 400 Commonwealth Drive, Warrendale PA 15096, http://www.sae.org/.)

2.3 Order of precedence. In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. DEFINITIONS

3.1 Beyond Economical Repair (BER). BER is defined as an estimated cost to repair in excess of 75% of the replacement cost.

3.2 Beyond Physical Repair (BPR). BPR is defined as an asset that is physically impossible to repair or when the damage is so extensive that restoration to a functional state is not possible with current technology or resources.

3.3 Controlled Unclassified Information (CUI). CUI is defined as unclassified information that laws, regulations, or Government-wide policies allow for, or require, safeguarding.

3.4 Repair. Repair is defined as the restoration or replacement of parts or components of the item as necessitated by wear and tear, damage, or failure of parts, in order to return the item to serviceable condition and to maintain it in efficient operating condition.

4. REQUIREMENTS

4.1 Program management.

4.1.1 Common Access Card (CAC). The contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to Department of Defense (DoD) computer networks/systems, for DoD facility entry control, and/or for physical access to facilities and buildings to perform tasks under the contract/order. The contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the Procuring Contracting Officer (PCO). The Government will provide the contractor instructions on how to complete a Contractor Verification System (CVS) application and notify the contractor of approval/disapproval of contractor/subcontractor personnel application.

Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility (usually the Military Personnel Flight (MPF)).

The contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within seven calendar days. The contractor shall immediately (within the same day) report a lost or stolen CAC to the PCO. The contractor shall return any issued CAC to the PCO within seven calendar days once contractor personnel no longer require computer network/system access. The contractor shall return any and all CACs to the PCO within seven calendar days after completion/termination of the contract.

4.1.2 Access to Government systems. The procuring activity will provide and/or arrange contractor personnel access to system(s) necessary to perform tasks under the contract/order. The contractor shall ensure contractor personnel who require access to an unclassified Government computer network/system have the appropriate background check or security investigation conducted. The procuring activity will provide and/or arrange system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract/order or transfer/termination of contractor personnel, the contractor shall ensure the system account(s) are closed.

4.1.3 Controlled Unclassified Information (CUI). CUI is defined as unclassified information that laws, regulations, or Government-wide policies allow for, or require, safeguarding. Knowledge and/or generation of CUI is required for performance of the contract/order. This SOW governs work that contains the development and transfer of CUI between contractors and the United States (U.S.) Government. All CUI shall be controlled until authorized for public release. The contractor shall ensure personnel, information, system, property, and facility security requirements are met. The contractor shall comply with Government security regulations including, but not limited to, Department of Defense (DoD) 5200.2-R, Personnel Security Program; DoD 5220.22-M; DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; and DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual to protect Government interests. Determine if Cybersecurity Maturity Model Certification (CMMC) is required and what level. The contractor shall ensure the security of any Information Technology (IT) environment at the contractor's facility that hosts CUI. The contractor shall maintain a cyber-secure environment for all components of a non-federal IT system that processes, stores, and/or transmits CUI as defined in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171 to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of CUI. Contractors shall ensure their employees have been trained in the proper marking of CUI; authorized and approved training material will be provided to the contractor prior to contract award. The contractor shall ensure that all personnel handling CUI associated with this contract have been properly trained, have been approved to handle CUI, have a valid need to handle CUI, and shall safeguard any CUI in their possession at all times. The contractor shall maintain a cyber-secure IT environment that reduces and manages risk by meeting the intent of Cybersecurity Maturity Model Certification (CMMC) Level I. The contractor shall also take necessary precautions and actions to ensure that the IT environment for any software development is secure and free of malware and malicious code. The contractor shall report any cyber incidents to the Government in accordance with DFARS Clause 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting) as applicable.

4.1.4 Data delivery and transfer. To promote effective schedule management, email shall be utilized to the maximum extent possible for tasks identified in this SOW. Department of Defense (DoD) Secure Access File Exchange (SAFE) shall be the secondary (backup) electronic data exchange, located at https://safe.apps.mil/, and utilized when temporary circumstances do not permit use of AF365 Teams.

4.1.5 Program manager. The contractor shall identify to the Government and maintain a single point of contact (program manager) for all matters under this contract. The contractor shall also ensure that all program management personnel assigned to the program shall be available, as required, to meet program objectives.

4.1.6 Plant access. The contractor shall arrange for full access to applicable contractor facilities and offices by Government representatives conducting any business, making observations, or performing inspections required by public law or by this contract.

4.1.7 Monthly status report. The contractor shall submit a monthly status report that shall cover actions to date as well as a projection of planned work for the remaining effort. Reports shall document tasks, issues, actions, and deliverables. Problem areas shall be identified with proposed solutions and outcomes. (DI-MGMT-81928, Contractor's Progress and Status Report)

4.2 Conferences and program reviews. Throughout the Period of Performance (POP) of the contract, conferences, meetings, and technical or programmatic reviews may be supplemented with a virtual environment as directed by the Procuring Contracting Officer (PCO) if travel restrictions, safety measures, or other program specifics prevent or limit the number of in-person attendees. Virtual meetings can utilize, but shall not be limited to, AF365 Teams. The contractor shall adhere to any Federal, State, or local health and well-being regulations and guidelines for contractor-hosted in-person gatherings with Government personnel.

4.2.1 Postaward conference. If the Government determines that a postaward conference is necessary, the Government will convene a postaward conference with the contractor at the contractor's facility, Robins AFB, or AF365 Teams within 60 calendar days after contract award. The PCO will coordinate the actual date, time, and location of the conference with the contractor.

4.2.2 System Engineering Technical Reviews (SETRs).

4.2.2.1 Test Readiness Review (TRR). The contractor shall conduct a TRR 14 calendar days prior to the start of the test. The TRR shall assess test objectives, test methods and procedures, scope of tests, and determine if required test resources have been properly identified and coordinated to support planned tests. The TRR shall be held at at the contractor's facility. The PCO will coordinate the actual date and time of the TRR with the contractor.

4.2.2.2 SETR documentation. The contractor shall prepare all necessary detailed status reports for the SETR meetings, Meeting Agendas, and Meeting Minutes. The contractor shall prepare formal documentation of the TRR. (DI-ADMN-81249, Meeting Agenda; DI-ADMN-81250, Meeting Minutes; DI-MISC-80508, Technical Report - Study/Services)

4.2.3 Program Management Reviews (PMRs). The contractor shall participate in and support all reviews, audits, and meetings as requested by the PCO or the contractor. PMRs shall be conducted quarterly or as required at a mutually agreeable location or via AF365 Teams. (DI-ADMN-81249, Meeting Agenda; DI-ADMN-81250, Meeting Minutes)

4.2.4 Production Readiness Review (PRR). A PRR shall be conducted to ensure the contractor is ready to begin production. The PRR shall include an evaluation of the contractor's manufacturing readiness processes, quality management system, production planning (that is, facilities, tooling and test equipment capacity, personnel development and certification, process documentation, inventory management, supplier management, etc.). Unless otherwise specified or directed by the PCO, the PRR shall be conducted at the contractor's facility within 30 days following procuring activity approval of the test report.

4.2.5 Conference room. The contractor shall provide a conference room suitable for meetings of up to 15 Government representatives, plus contractor personnel, in support of scheduled meetings at the contractor's facility. The conference room shall support AF365 Teams access for virtual attendees.

4.2.6 Meeting agendas. The contractor shall publish an agenda for all meetings and conferences specified in 4.2.2 - 4.2.4. The contractor shall request from the Government any items or issues to be discussed or presented at the meetings and shall include such items in the agenda. Agendas shall be submitted not less than seven calendar days prior to any meeting. (DI-ADMN-81249, Meeting Agenda)

4.2.7 Meeting minutes. The contractor shall provide a written record of the discussions, decisions, and action items identified at each meeting. Minutes shall include presentation material. (DI-ADMN-81250, Meeting Minutes)

4.3 Systems engineering.

4.3.1 Environment, Safety, and Occupational Health (ESOH).

4.3.1.1 System safety. The contractor shall establish, conduct, document, and maintain a system safety program in accordance with MIL-STD-882. The contractor shall document their approach for analyzing, eliminating, or minimizing ESOH hazards during all phases of the program. The contractor shall initiate changes in the system design based on safety analysis results such that the associated risk is reduced to a level acceptable to the Government. An initial system safety hazard analysis shall be provided 14 calendar days prior to the TRR; an updated version of the analysis shall be provided with the test report. (DI-SAFT-81626, System Safety Program Plan; DI-SAFT-80101, System Safety Hazard Analysis Report (SSHAR))

4.3.1.2 Hazardous materials. The contractor shall manage hazardous materials, including those embedded in the system or used during operation or maintenance, as an element of the Systems Engineering process. The system shall not generate or use Class I or Class II Ozone Depleting Substances (ODS) during operation, maintenance, or disposal. The use of hexavalent chromium is also prohibited. The contractor shall list any hazardous materials to be delivered under this contract, including locations, quantities, and special handling and disposal procedures. This information shall be documented in the monthly status report (see 4.1.7) and reviewed at the PMRs; it shall be in accordance with FED-STD-313.

4.3.2 Counterfeit Prevention Plan (CPP). Contractors that supply electronic parts or systems that contain electronic parts shall establish policies and procedures to avoid, detect, mitigate and disposition counterfeit electronic parts to prevent such parts from entering the United States Air Force (USAF)/DoD supply chain. These policies and procedures shall be documented in a CPP for submission and approval in accordance with DI-MISC-81832 and accomplished for all specified contract items. DI-MISC-81832 is applicable to Parts, Material, and Processes Selection (PMPS) associated with delivery of systems and assemblies to the USAF and DoD. The requirements established by DI-MISC-81832 also apply to electronics components procured in sustainment of such systems and assemblies. The requirements of the DoD-adopted SAE AS5553, Aerospace Standard, Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and Disposition shall also apply. The initial CPP shall be provided 30 calendar days after contract award. (DI-MISC-81832, Counterfeit Protection Plan)

4.3.2.1 Applicability. The contractor shall identify all business locations and programs to which the CPP applies. The CPP shall address materials, hardware, electronic parts, and procured assemblies.

4.3.2.2 Definitions. The contractor shall utilize definitions in accordance with AS5553 to ensure consistency. Any contractor-derived definitions shall be included in an appropriate CPP appendix or annex. (Ref. 3, 3.1, 3.2, 3.3, and Appendix H of AS5553)

4.3.2.3 Parts availability and use of parts brokers. The contractor shall not procure materials, systems, assemblies, subassemblies, or parts from parts brokers when available from Original Manufacturers (OM) or their authorized distributors. In cases where materials, systems, assemblies, subassemblies, or parts are no longer available from the OM or their authorized distributors, procurement from brokers may be authorized as defined by the contractor's policy and their CPP. (Ref. 4.1.1, 4.1.2.e., and Appendix A of AS5553)

4.3.2.4 Procurement policies. The contractor shall provide and implement policy directing development and implementation of business practices, procedures, and processes to prevent procurement of counterfeit materials and parts. The contractor shall identify the appropriate office(s), business units, functional organizations, and programs, who shall have responsibility for development, maintenance, and implementation of the CPP. The CPP shall identify the specific roles and responsibility for each. (Ref. 4.1.2, 4.1.3, and Appendices B, C, and D of AS5553)

4.3.2.4.1 Risk assessment. The contractor shall address the risk of using unknown sources and/or unauthorized suppliers in the CPP. Application or technical risk assessments shall establish the effect that counterfeit parts may have on in accordance with performance. Vendor or source of supply risk assessments shall establish the potential for obtaining counterfeit parts. Using any risk analysis tool acceptable to the Government, the contractor shall conduct a risk assessment based upon item characteristics and how likely it is that a counterfeit part will be received. The contractor shall identify and describe in the CPP how parts are selected for assessment and what risk is acceptable based upon the parts design, construction, material, and functional requirements. As a minimum, analysis shall be completed for flagging high risk items, such as items that are obsolete, discontinued, rare, etc. The contractor shall require completion of a trade study, documented within the CPP that shall facilitate determining whether 100% testing of parts procured from after-market sources is more cost effective than qualification or requalification of a manufacturer. (Ref. 4.1.2, 4.1.3 and appendices B, C, and D of AS5553)

4.3.2.5 Detection and avoidance responsibilities. The contractor shall establish processes for the review and approval of contractor and applicable subcontractor systems for the detection and avoidance of counterfeit electronic parts and suspect counterfeit electronic parts, which processes shall be comparable to the processes established for contractor business systems under section 893 of the Ike Skelton National Defense Authorization Act for Fiscal Year 2011 (Public Law 111–383; 124 Stat. 4311; 10 U.S.C. 2302 note). The contractor shall flow down such requirements and processes to their subcontractors in accordance with ODASD Memo titled "Overarching DoD Counterfeit Prevention Guidance", dated 16 March 2012. (Ref. AS5553, 4.1.4, 4.1.5, appendix E)

4.3.2.6 Testing and verification. The contractor shall establish and accomplish testing and verification processes for items not received from an original equipment manufacturer, original component manufacturer, or authorized distributor that are identified as having high risk for counterfeit potential. These processes apply to prime contracts and to subcontracts or suppliers below the prime contracts. The contractor shall provide a list of acceptable test facilities if the subcontractor or supplier does not have the capability to in accordance with form required testing. Submittal of Certificates of Compliance indicating the parts are not counterfeit shall be acceptable for verification of testing. (Ref. 4.1.4 and Appendix E of AS5553)

4.3.2.7 Configuration identification and traceability. The contractor shall identify and control the configurations of all systems, assemblies, subassemblies, and parts, and enable mechanisms to provide traceability of parts. The contractor shall report to the Government when control of the configurations of all systems, assemblies, subassemblies, and parts, and mechanisms to provide traceability of parts are not possible. The contractor shall identify the specific systems, assemblies, subassemblies, and parts beyond the contractors' control. The contractor shall be responsible for detecting and avoiding the use or inclusion of counterfeit materials and parts, to include procured assemblies and subassemblies, in such products and shall be responsible for the rework or corrective action that may be required to resolve the use or inclusion of counterfeit materials and parts. The cost of counterfeit electronic parts and suspect counterfeit electronic parts and the cost of rework or corrective action that may be required to remedy the use or inclusion of such parts are not allowable costs under Department contracts, unless:

1. the contractor has established a counterfeit avoidance/detection system approved by the DoD,

2. the counterfeit parts were procured from a DoD-accredited trusted supplier or provided as Government property, and

3. the contractor has provided timely notification to the Government. (Ref. 4.1.6 and Appendix F of AS5553).

4.3.2.8 Counterfeit notification and reporting. The contractor shall report in writing to the Procuring Activity within 30 calendar days of determining any end item, component, part, or material contained in supplies purchased by the Department of Defense, or purchased by a contractor or subcontractor for delivery to, or on behalf of, the Department, contains counterfeit electronic parts or suspect counterfeit electronic parts for the purpose of investigation and notification of the Air Force Office of Special Investigations (AFOSI). The PCO will coordinate reporting to the appropriate Program Management/Item Management, System Engineering Management, the Air Force Materiel Command (AFMC) Discrepant Materiel Reporting Program (DMRP) Office in 406 SCMS/GULAB, and the AFOSI. Additionally, the contractor shall within the same 30 calendar day period ensure all suspected or confirmed counterfeit items are entered into the Government-Industry Data Exchange Program (GIDEP) system, which will serve as the DoD central reporting repository. (Ref. 4.1.7 and Appendix G of AS5553)

4.3.2.9 Counterfeit protection training. The contractor shall provide appropriate training and shall require all personnel working procurement within their company, to include at a minimum their supply chain management specialists, receiving inspectors, and engineers, to complete said training. The contractor shall determine the appropriate training required. Training may be developed in-house or may be other Industry accepted training. The CPP shall describe and list the training provided by the contractor to their personnel.

4.4 Logistics.

4.4.1 Technical Order (TO) requirements. The contractor shall develop and deliver technical manuals in accordance with TM-86-01. No production F-16 Boresight System will be accepted prior to Government approval of the technical manuals. (TM-86-01, Air Force Technical Manual Contract Requirements)

4.4.2 Provisioning. The contractor shall identify and recommend logical spare/repair parts sufficient to meet system/equipment operation and supportability in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). GEIA-HB-0007B (Logistics Product Data Handbook) should be used as a guide. The format shall be consistent with existing Government Provisioning data system (D220). The following DIDs apply:

a. DI-SESS-81758, Logistics Product Data. Specific Logistics Product Data to be submitted:

i. Provisioning Parts List (PPL) Top-down sequence

ii. Design Change Notices (DCNs)

iii. Statement of Prior Submission (SPS)

iv. Long Lead Items List (LLIL)

b. DI-SESS-81874, Engineering Data For Provisioning (EDFP).

(DI-SESS-81758, Logistics Product Data; DI-SESS-81874, Engineering Data For Provisioning (EDFP))

4.4.2.1 Provisioning Guidance Conference (PGC). A Provisioning Guidance Conference (PGC) shall be scheduled by the Prime Provisioning Activity (PPA) and should be held within 45 days after receipt of contract in conjunction with the postaward conference. The PGC is normally held at AFGLSC PPA for approximately two days to ensure both the contractor and the Government understand the provisioning requirements on contract. If a PGC is not desired, the contractor shall submit a written request for waiver of the PGC to the PPA. In the event a waiver is approved, a mutual understanding of the Provisioning requirements shall be communicated in some forum in which the AFMC Form 718 (Provisioning Performance Schedule (PPS)) shall be documented/completed, signed by both the Government and contractor, and a contract modification issued, if required. (DI-ADMN-81249, Meeting Agenda; DI-ADMN-81250, Meeting Minutes)

4.4.3 Training and familiarization. Training shall be provided so that users and maintainers can operate and maintain the F-16 Boresight System properly. Video training shall be provided with each unit on a CD/DVD-ROM. Video training in the CD/DVD-ROM shall have multiple videos labeled according to the specific tasks for easy search. A hard copy of the training manual shall be supplied with each unit; an electronic copy of the training manual shall also be provided on the video training CD/DVD-ROM. The training manual shall contain written descriptions and procedures with images that explain step by step how to operate and maintain the unit. A copy of all training materials shall be provided to and approved by the procuring activity prior to providing with each unit. (DI-ILSS-80872, Training Materials)

4.5 Testing and evaluation.

4.5.1 Design analysis. A design analysis of the system and each subsystem shall be performed to verify compliance with this SOW and each applicable requirement of the PD. The analysis shall include, but is not limited to, environmental and hazardous material management (see 4.3.1.2); a calibration cycle analysis (see 4.6.4 of the PD); and a transportability analysis (see 4.6.9 of the PD). A Material Safety Sheet (MSDS) shall be provided for each hazardous material identified for use in the program (see 4.3.1.2). (Note that the system safety hazard analysis is addressed in 4.3.1.1.) An initial design analysis shall be provided 14 calendar days prior to the TRR and an updated version with the test report. (DI-MISC-80508, Technical Report - Study/Services)

4.5.2 Test support. The contractor shall ensure common repair parts are available during all phases of testing specified herein so that failures do not delay the test beyond the repair time required to return the equipment to serviceable condition. In the event that one or more replacement parts are required to repair a failure, the contractor shall ship the part(s) to the test location via “same day” or “overnight” service at the direction of the procuring activity. Copies of the latest draft TOs shall be available for Government use during compatibility testing and operational test and evaluation.

4.5.3 First article test.

4.5.3.1 First article test procedures. The contractor shall develop detailed test procedures, which shall address all requirements identified in the PD and this SOW, except for the compatibility testing (see 4.5.3.4). The test procedures shall include data record sheets, charts, graphs, identification of test instruments by manufacturer, model number, and serial number. The test procedures shall address modeling and simulation (M&S); if M&S is not applicable, the test procedures shall be so noted. (DI-NDTI-80603, Test Procedure)

4.5.3.2 First article testing. After Government approval of the first article test procedures, the contractor shall schedule the testing to be conducted. If shipping is required to move the item(s) to and from a test site away from the contractor’s facility, the contractor shall be responsible for all costs associated with the shipment. The contractor shall notify the Government of the date, time, and location of first article testing 30 calendar days prior to the start of testing. The test will be witnessed by one or more Government representatives.

4.5.3.2.1 Calibration.

4.5.3.2.1.1 Calibration and Measurement Requirement Summary (CMRS). The contractor shall provide a CMRS that details the measurement requirements of the system, subsystem, or equipment; the Test, Measurement, and Diagnostic Equipment (TMDE); and the calibration standards and equipment required to assure traceability of all measurements through the individual military department metrology and calibration programs to approved national standards. The summary identifies and validates the adequacy of TMDE and the need for calibration standards and equipment. (DI-QCIC-80278, Calibration and Measurement Requirements Summary (CMRS))

4.5.3.2.1.2 Calibration procedures. Calibration procedures and equipment requirements shall be provided, along with adjustment processes, maintenance manuals, and mechanical drawings for the boresight system. Precision Measurement Equipment Laboratory (PMEL) training shall be included in order to be able to calibrate the system at regional PMELs.

4.5.3.2.1.3 Calibration certificate. Each boresight system shall be supplied with an initial certificate of calibration. Calibration shall be traceable to the International System of Units through National Institute of Standards and Technology (NIST) or other internationally recognized testing laboratory. (DI-QCIC-80798, Calibration Certificate)

4.5.3.3 First article test daily situation reports (SITREPs). Throughout the first article test, the contractor shall submit a daily situation report (SITREP) that shall cover all monitored daily test activities. Examples are:

a. Test logs.

b. Observed data to include: Observations, comments, anomalous conditions, or other items completed for each first article unit.

c. Recorded data as applicable to the type of equipment.

d. Records of preventive maintenance activities performed.

(DI-MGMT-81928, Contractor's Progress and Status Report)

4.5.3.4 Compatibility testing. During the first article test, a test item shall be shipped to Morris ANGB, Tucson AZ for compatibility testing in accordance with 4.6.3 of the PD. Air Force personnel will perform the test and any required maintenance; contractor personnel shall witness the test and maintenance and advise the Air Force personnel. At the conclusion of the compatibility test, the test item shall be shipped to the contractor's facility. The contractor shall be responsible for all costs associated with shipping the item to the compatibility test location and returning it to the contractor's facility.

4.5.3.5 First article test report. The contractor shall submit a first article test report upon completion of the first article test. The test report shall document all testing performed, including results of any unsuccessful test attempts. Failure reports generated as a result of the FRACAS process (see 4.5.4 of the PD) shall be included with results of unsuccessful test attempts. (DI-NDTI-80809, Test/Inspection Report)

4.5.4 Operational Test and Evaluation (OT&E). After completion of first article testing and approval by the Government of the first article test report, all first article F-16 Boresight Systems shall be shipped to Morris ANGB, Tucson AZ for OT&E. The contractor shall be responsible for all costs associated with shipping. Air Force operators and maintainers will conduct all OT&E. The contractor shall provide a spare parts kit with each first article F-16 Boresight System shipped for the OT&E containing all items required to conduct scheduled maintenance during the test as well as common repair parts predicted to be needed during the OT&E. Contractor's support shall be available (within 48 hours of notification exclusive of weekends and official Federal Government holidays) all times during the OT&E. All OT&E shall be completed within 45 calendar days.

4.5.5 Restoration. After completion of first article and OT&E acceptance, the first article F-16 Boresight Systems shall be shipped, within 30 calendar days, to the contractor's facility for restoration. The contractor shall be responsible for any repairs that may be necessary to restore the first article F-16 Boresight Systems to a serviceable, "like new" condition while retaining configuration integrity. The contractor shall be responsible for all costs associated with shipping of the first article F-16 Boresight Systems to the contractor's facility for restoration.

4.5.6 Disposition. The approved unit shall be retained at the contractor's facility, to serve as a manufacturing standard, until the last shipment.

4.5.7 Conformance test. The contractor shall test each production item in accordance with Leave 4.4 of the PD utilizing a subset of the first article test procedures.

4.6 Configuration management.

4.6.1 Configuration requirements.

4.6.1.1 Baselines.

4.6.1.1.1 Functional baseline. The functional baseline is the PD.

4.6.1.1.2 Allocated baseline. All of the documents used to produce and define the configuration at the conclusion of the TRR shall constitute the allocated baseline.

4.6.1.1.3 Product baseline. All of the documents used to produce and define the accepted units shall be identified in a Product Baseline Index (PBLI). The list shall identify the applicable version number as required. (DI-SESS-82019, Product Baseline Index (PBLI))

4.6.1.2 Production release. Production release is acknowledgment by the procuring activity that the contractor has satisfied all requirements to proceed with delivery of hardware to be furnished under the contract. The contractor assumes all risks in initiating production before the test report and TOs have been delivered and approved by the procuring activity.

4.6.2 Engineering Change Proposals (ECPs). Notwithstanding any other provision in the contract, no contractor or subcontractor's change in design, fabrication, assembly, part, material, process, or source of supply shall be made to the allocated or product baseline unless such change is submitted in writing by ECP and approved by the procuring activity. Any request for change shall be accompanied by complete documentation supporting the need for the change. A system safety impact statement shall be provided as part of the submittal; it shall quantify and qualify the system safety risk identified and how it impacts the system safety risk already identified for the system. A Notice of Revision (NOR) shall be submitted with each ECP. Should the Government approve an ECP, the contractor shall be responsible for submitting updated TOs and the system safety hazard analysis report (see 4.3.1.1) to reflect the changes made in the ECP. (DI-SESS-80639, Engineering Change Proposal (ECP); DI-SESS-80642, Notice of Revision (NOR)).

4.6.3 Request for Variance (RFV). The contractor shall prepare an RFV whenever a departure from the contractually-specified base line is proposed for a specific number of units or for a specific time. (DI-SESS-80640, Request for Variance (RFV))

4.7 Interface Control Document (ICD). The contractor shall develop, implement, and maintain an ICD that defines and documents all system external interfaces . The ICD shall include interface definitions, communication protocols, data formats, and physical connections required for the proper integration and operation of the system. The ICD shall also provide the necessary information to manage and control interfaces throughout the system lifecycle, ensuring compatibility and interoperability with interfacing systems. All interfaces shall be described in sufficient detail to allow independent verification of compliance with system requirements. (DI-SESS-81248, Interface Control Document (ICD))

4.8 Cybersecurity. The contractor shall implement cybersecurity in accordance with Department of Defense Instruction (DoDI) 8500.01, DoDI 8510.01, and AFI 17-101. The contractor shall provide cybersecurity support to include, but not limited to, engineering and technical analysis and assessment of system cybersecurity, development and delivery of Risk Management Framework (RMF) artifacts, and design, integration, testing, and documentation of implemented cybersecurity controls. The contractor shall include cybersecurity activities and events on the IMS. The contractor shall address technical details of cybersecurity requirements as part of applicable SETRs.

4.8.1 Cybersecurity analysis. The contractor shall perform an engineering analysis and risk and technical assessment of system cybersecurity for each end item. The engineering analysis shall include, but not be limited to, system hardware and software architecture, I/O data flow, supply chain integrity, and operational conditions as it relates to system cybersecurity. The contractor shall perform a comprehensive risk assessment based on the system cyber vulnerabilities and threats. The contractor shall also conduct analysis for any commercial-off-the-shelf and/or non-developmental items to ensure that they are appropriately configured, software, hardware and firmware is controlled, and any unique risks they pose are mitigated. (DI-MISC-80508, Technical Report - Study/Services, Cybersecurity Analysis)

4.8.2 Risk management framework (RMF). The contractor shall develop and deliver the required artifacts for the Platform Information Technology (PIT) Assessment and Authorization (A&A) package to meet the intent and requirements of DODI 8510.01 and AFI 17-101 for RMF implementation. The contractor shall utilize NIST SP 800-37, NIST SP 800-53, and applicable overlays in addressing the security controls associated with the various artifacts. The contractor shall include cybersecurity RMF activities and events on the IMS. (DI-MGMT-82001, DoD RMF Package Deliverables)

4.8.3 Cybersecurity security controls design, integration, and testing. The contractor shall provide design, integration, and testing support for system modification(s) of hardware and/or software solutions to mitigate or resolve cybersecurity risks for given vulnerabilities and threats. The contractor shall conduct all specified SETRs to adequately convey the approach to requirements analysis, design, integration, and testing. The contractor shall define and develop test programs, plans, and procedures, witness and support or conduct testing, evaluate and/or document the results of testing and evaluation for cybersecurity of components, subsystems and/or systems, and associated software. (DI-MGMT-82140, Cybersecurity Test Plan; DI-MGMT-82142, Naval Aviation Cybersecurity Test Report)

4.8.4 Software. The contractor shall develop and deliver a Software Assurance Evaluation Report (SAER) to demonstrate that all delivered software functions as intended and is pending free of vulnerabilities (that is, defects, bugs, malware, etc.) either intentionally or unintentionally inserted as part of the software throughout the development lifecycle. (DI-IPSC-82249, Software Assurance Evaluation Report (SAER))

4.8.5 Computer program identification number (CPIN). The contractor shall submit a request for CPIN assignment of all custom and/or commercial software and/or firmware to be delivered to the Government. CPIN assignment requests shall be accomplished by direct on-line data entry into Enhanced Technical Information Management System (ETIMS) in accordance with TO 00-5-16 guidelines. The contractor shall deliver the final Computer Software Configuration Items (CSCIs) on CD/DVD-ROM and shall contain all files, drivers, and other data necessary for installation and operation of the software/firmware. The CPIN media label information shall match the information in ETIMS. (DI-MISC-81454, Computer Program Identification Number Catalog Information; DI-AVCS-80700, Computer Software Product End Items)

4.8.6 Supply Chain Risk Management (SCRM). An SCRM plan or strategy shall be developed to address risks such as obsolescence of hardware components or software, as well as the integrity of the supply chain, to include hardware sources and software development and distribution. (DI-MGMT-82256, Supply Chain Risk Management (SCRM) Plan)

4.9 Repairs. Repair is defined as the restoration or replacement of parts or components of the item as necessitated by wear and tear, damage, or failure of parts, in order to return the item to serviceable condition and to maintain it in efficient operating condition.

4.9.1 Repair authorization. The procuring activity will authorize repairs by using the information listed on the Repair Request Form submitted by the user. After the delivery order is published, the procuring activity will communicate to the owners of the equipment that they can send it into the contractor’s facility for repair based on priority. The user will only contact the procuring activity for approval of the repair(s).

4.9.2 Test, Teardown, and Evaluation (TT&E). After receipt of the item, TT&E shall be performed by the contractor to determine the cause of failure prior to conducting actual repair of the item.

4.9.2.1 No Fault Found (NFF)/Re-Test Okay (RTOK). When the contractor cannot duplicate the fault, known as a NFF/RTOK, the contractor shall notify the PCO and obtain approval to place NFF/RTOK asset against NFF CLIN. The contractor shall not charge the full repair price, but only the firm-fixed-price associated with NFF/RTOK actions determined during the negotiation of the contract.

4.9.2.2 Beyond Economical Repair (BER) and Beyond Physical Repair (BPR). BER is defined as an estimated cost to repair in excess of 75% of the replacement cost. BPR is defined as an asset that is physically impossible to repair or when the damage is so extensive that restoration to a functional state is not possible with current technology or resources. The contractor shall notify the Government of BERs and BPRs in writing through the Administrative Contracting Officer (ACO) to the PCO within five (5) workdays of identifying the BER or BPR requirement. The Government shall review the BER and BPR requests. The Government will determine whether to fund the BER or BPR or will request the contractor to condemn the asset. If the Government determines to proceed with repair of the BER or BPR asset, a request for a cost proposal, required work breakout, and full repair process of the asset will be provided to the Government. If the Government approves condemnation of the asset, the contractor shall not charge the full repair cost, but only the firm fixed price associated with the firm-fixed price BER/BPR CLIN. The PCO retains the right to request enlarged color photographs (electronic media preferred) of any proposed condemned end item.

These photographs shall clearly portray the extent of damage to the end item and/or effects of overheating. One photograph shall be of the entire end item showing the part number and serial number designation. The results of any electrical testing performed and the end item shall also be submitted for review. The contractor may be required to submit the proposed condemned end item to the Government technical representative for evaluation, confirmation, and/or disposition instructions.

4.9.2.2.1 Condemned items. The procuring activity may request to have items condemned under the provisions of the contract kept at the contractor’s facility for future cannibalization.

4.9.2.2.2 Authorization to scrap an item. Upon receipt of authorization from the Government to scrap an item, the contractor shall complete all actions/directions (including authorized cannibalization) and submit a scrap certificate and DD250, if required, within 30 days.

4.9.2.2.3 Cannibalization. The contractor may request permission to cannibalize reparable US Government sub-component assemblies for use in repair of specific serial numbered Government-owned assets on this contract. The procuring activity will provide the final determination and disposition instructions to the PCO who will provide cannibalization determinations to the contractor via the ACO.

4.9.3 Repair turn-around. Equipment received for repair shall be repaired and shipped back to the user within 30 calendar days of the repair authorization by the procuring activity. There shall be no more than two late deliveries per quarter. The contractor shall notify the procuring activity if the delivery of any asset will not meet the scheduled delivery date and negotiate a revised delivery date. The late asset shall be delivered by the revised delivery date acceptable to the procuring activity.

4.9.3.1 Repair delays. If for any reason the contractor is unable to initiate repair of equipment within 15 calendar days of receiving equipment at the contractor’s facility, the contractor shall immediately notify the PCO and provide the reason why repair cannot be initiated, and an estimated date of when repair of identified items will…