BAE PWS_(20-Nov-25).docx

DOCX document 102 KB Posted

Attached to
AIS Engineering Services for ATE
Solicitation number
Not on record
Issued by

About this file

This Performance Work Statement (PWS) details engineering services for the F-16 Avionics Intermediate Shop (AIS) Automatic Test Equipment (ATE) Commodities Sustainment Program for the Air Force Sustainment Center. The contract requires BAE Systems to provide comprehensive sustainment support for AIS test stations used across seven USAF Major Commands, Hill Air Force Base Depot locations, and approximately 22 European Participating Air Force/Foreign Military Sales countries.

Key responsibilities include commodities sustaining engineering, software integration and maintenance, technical order maintenance, and maintenance of Government Furnished Equipment at facilities in San Diego, CA and Fort Worth, TX. The contractor must maintain test stations at a 95% Fully Mission Capable rate, provide quarterly obsolescence reports, develop supply chain risk management plans, and support cybersecurity requirements. The effort encompasses hardware/software engineering tasks, technical studies, engineering analysis, spares support, field assistance, non-recurring engineering activities, and repair/modification of equipment to support AIS system requirements. The contract will involve maintaining various test station configurations including AdC AIS, IAIS, VXI-IAIS, and R-IAIS, with specific focus on sustaining operational capabilities for F-16 weapon systems.

View the file

Other files

On GovTribe

Work with this file

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

Text version

PERFORMANCE WORK STATEMENT

(PWS) FOR

F-16 AVIONICS INTERMEDIATE SHOP (AIS)

AUTOMATIC TEST EQUIPMENT (ATE) COMMODITIES SUSTAINMENT PROGRAM

CONTRACT: TBD

DATE: 20 NOVEMBER 2025

PREPARED BY: 416 SCMS/GUMAA

6070 GUM LANE

BLDG 1213

HILL AFB, UT 84056-5825

Disclosure Notice – This information is furnished on the condition that it will not be released to another nation without specific authority of the Department of the Air Force of the United States, that it will be used for military purposed only, that individual or corporate rights originating in the information, whether patented or not, will be respected, that the recipient will report promptly to the United States any known or suspected compromise, and that the information will be provided substantially the same degree of security afforded it by the Department of Defense of the United States. Also, regardless of any other markings on the document, it will not be downgraded or declassified without written approval of the originating U.S. agency.

SECTION I

DESCRIPTION OF SERVICES

0. SCOPE

1.1.1 The Avionics Intermediate Shop (AIS) Systems Sustainment Program, located in the 416 Supply Chain Management Squadron (SCMS), is responsible for ensuring the operational capability of AIS Systems worldwide through the sustainment of Automatic Test Equipment (ATE) components contained within the Advanced Avionics Intermediate Shop (AdC AIS), Improved Avionics Intermediate Shop (IAIS), Versamodule Extensions for Instrumentation Improved Avionics Intermediate Shop (VXI-IAIS), and Rackmount Improved Avionics Intermediate Shop (R-IAIS) test stations. These test station components are vital to the overall health of AIS ATE located throughout seven (7) United States Air Force (USAF) Major Commands (MAJCOMs), Hill Air Force Base Depot locations (to include Support Center Pacific), and approximately 22 European Participating Air Force (EPAF) / Foreign Military Sales (FMS) countries worldwide. AIS components are sustained by obtaining vital services required to maintain ATE Full Mission Capability in support of F-16 weapon system requirements.

1.1.2 This Performance Work Statement (PWS) identifies and subsequently defines the services required to sustain components contained within the AIS series of test stations. The identified services/activities are to be provided by BAE Systems, Information and Electronic Systems Integration Inc., San Diego, CA; hereafter referred to as “BAE”, “BAE Systems”, or “the contractor”. Services provided identify the sustainment activities to be provided to the 748th Supply Chain Management Group (SCMG), 416 SCMS. The customer will be referred to hereafter as “416 SCMS”, “the 416th”, or simply “the Government”. References to 416 SCMS in this PWS may involve AFSC, AFLCMC, or local OO-ALC organizations, such as the 309 Maintenance Group, AFLCMC/WAM (F-16 Division), or the 581 Software Engineering Squadron (SWES).

1.1.3 Services to be provided include ATE Commodity Sustaining Engineering, Component Software Integration and Maintenance, ATE Maintenance of Government Furnished Equipment/Property located at contractor facilities, and Technical Order Maintenance Support. These services are essential to the task of ensuring integrity, mission readiness, sustainability, reliability, and maintainability of components contained within the AIS series of test stations, to include AdC AIS, IAIS, VXI-IAIS, and R-IAIS. Additionally, when required, the contractor shall perform Non-Recurring Engineering (NRE) activities in order to develop resolutions to obsolescence issues over and above Form-Fit-Function interface component replacement, and/or to develop new test capabilities in support of weapon system requirements.

0. TERMS EXPLAINED

“ACO”: Administrative Contracting Officer “AdC AIS”: Advanced Computer Avionics Intermediate Shop “ACSN”: Advanced Change Study Notice “AFLCMC”: Air Force Life Cycle Management Center “AFSC”: Air Force Sustainment Center “AIS”: All existing AIS and IAIS configurations of Test Stations “ATE”: Automatic Test Equipment “ATP”: Acceptance Test Procedures “Calibration”: A comparison between two instruments, one of which is a standard of higher accuracy, to detect and correlate or adjust any variation in the accuracy of the instrument or equipment item being compared or tested. Calibration shall be accomplished using Government-approved contractor technical data “CAVAF”: Commercial Asset Visibility, Air Force – web-based application that allows the user to report transactions on a daily basis for End Item repair, overhaul, and modification of repairable items from receipt by the contractor to induction for work, production, and shipment back to the Air Force “C&S”: Control and Support “CDRL”: Contract Data Requirements List “CMRS”: Calibration and Measurements Requirements Summary “CO”: Contracting Officer “Component”: An assembly or any combination of parts, subassemblies, and assemblies mounted together in manufacture, assembly, maintenance, or rebuild “COOP”: Contingency of Operations Plan “COR”: Contracting Officer Representative “CPIN”: Computer Program Identification Number “Diagnose”: To ascertain, using the contractor’s technical data and/or Government-approved contractor technical data what is causing the end-item to be unserviceable “DID”: Data Item Description “DMSMS”: Diminishing Manufacturing Sources and Material Shortages “DR”: Deficiency Report “DRILS”: Defense Repair Information Logistics System – a web-based serialized maintenance data collection and retrieval system “ECO”: Engineering Change Order “ECP”: Engineering Change Proposal “ETIMS”: Enhanced Technical Information Management System “EPAF”: European Participating Air Force “ESD”: Electrostatic Discharge “FMC”: Fully Mission Capable “FMS”: Foreign Military Sales “FSB”: Field Service Bulletin “FSD”: Full Scale Development “GFE”: Government Furnished Equipment “GFP/M”: Government Furnished Property/Material “IAW”: In Accordance With “IAIS”: Improved Avionics Intermediate Shop “IPPS”: Initial Provisioning Performance Specification “ISO”: International Organization for Standardization “ITA”: Interface Test Adapter “ITAR”: International Traffic in Arms Regulations “LOA”: Letter of Offer and Acceptance “LRU”: Line Replaceable Unit “Maintenance”: Preventative and/or correctional activities to ensure that facilities and equipment are functionally capable of expected operation. As a result of these activities, equipment should be in good operating condition (clean, free from unrecognized hazards, etc.) within specified limitations such as those imposed by age and prior use “MILSTRIP”: Military Standard Requisitioning and Issue Procedures “MIP”: Material Improvement Project “Modification (Mod)”: A change in the physical or functional characteristics of a system, equipment, or end-item that affects form, fit, or function “N/A”: Not Applicable “NRE”: Non-Recurring Engineering “NSN”: National Stock Number “OEM”: Original Equipment Manufacturer “OFP”: Operational Flight Plan “OPSEC”: Operational Security “ORSK”: Operational Readiness Support Kit “PIDS”: Prime Item Development Specification “PLISN”: Provisioning List Item Sequence Number “PME”: Prime Mission Equipment “PMP”: Program Management Plan “PPS”: Provisioning Performance Schedule “PWS”: Performance Work Statement “R&M”: Reliability and Maintainability “R-IAIS”: Rackmount Improved Avionics Intermediate Shop “ROM”: Rough Order of Magnitude “SCRM”: Supply Chain Risk Management “SCMG”: Supply Chain Management Group “SCMS”: Supply Chain Management Squadron “SE”: Support Equipment “SERD”: Support Equipment Recommendation Data “SGML”: Standardized General Markup Language “SMR”: Source Maintenance and Recoverability “STS”: System Test Specification “SVD”: Software Version Document “TCTO”: Time Compliance Technical Order “TIM”: Technical Interchange Meeting(s) “TPS”: Test Program Set “USAF”: United States Air Force “VXI-IAIS”: Versamodule Extensions for Instrumentation Improved Avionics Intermediate Shop “XML”: Extensible Markup Language

Section II

SERVICES DESCRIPTION SUMMARY:

0. PERFORMANCE OBJECTIVES

The contractor shall be responsible for the accomplishment of all ATE Commodities Sustainment Task Orders necessary to support operational requirements for existing F-16 operational users as well as potential new F-16 users.

The following Table provides a summary of primary responsibilities and duties.

Performance Objective

PWS Reference
Performance Threshold
Provide Quarterly Obsolescence Reports
4.2.3.3.6
Submit quarterly report 100% complete by the end of the designated month to meet objective. Submit quarterly report 100% complete one week prior to the end of designated month to exceed objective
Prepare and submit logistics documentation
4.1.1, 4.2.3.2, 4.2.3.2.1, 4.2.3.2.2, 4.2.3.2.3, 4.2.3.2.4, 4.2.3.3.9
Data to be submitted 90% accurate as required to capture ECO and/or logistics data changes to meet objective. Data to be submitted 100% accurate as required to capture ECO and/or logistics data changes to exceed objective
Provide Commodities Sustaining Engineering Support
4.2.2, 4.2.2.1, 4.2.2.2, 4.2.2.3, 4.2.3.1, 4.2.3.2
Support tasks to be captured in report delivered by the end of the designated month to meet objective. Support tasks to be captured in report delivered one week prior to the end of designated month to exceed objective
Provide technical support to field sites
4.2.1.5, 4.2.2, 4.2.2.2.1, 4.2.2.3, 4.2.3, 4.2.3.1, 4.2.3.1.1, 4.2.3.1.2

Respond to field requests with a plan within 72 hours to meet objective. Respond to field requests with a plan within 48 hours to exceed objective

Provide On-site technical support to the 416 SCMS
4.2, 4.2.2
Respond to requests from the 416 SCMS with a plan for completion/resolution within one week to meet objective. Complete/resolve requests from the 416 SCMS within one week to exceed objective
Provide Status Reports to the Government
4.2.1.3, 4.2.2.1, 4.2.2.2.1, 4.2.2.2.2, 4.2.2.2.3, 4.2.2.3.2, 4.2.3.2.2, 4.2.3.3.7, 4.2.4.11, 4.2.5.4, 4.2.6.7
Submit status reports monthly 100% on time by the 20th of each month to meet objective. Submit status reports monthly prior to the 20th of each month to exceed objective
Incorporate changes resulting from Hardware Integration investigations into ATE software
4.2.4, 4.2.4.5
Incorporate changes resulting from Hardware Integration investigations 90% accurately to meet objective. Incorporate changes resulting from Hardware Integration investigations 100% accurately to exceed objective
Incorporate changes resulting from TPS regression testing into ATE software
4.2.4.5
Incorporate changes resulting from TPS regression testing 90% accurately to meet objective. Incorporate changes resulting from TPS regression testing 100% accurately to exceed objective
Provide Technical Order Change Pages
4.2.5, 4.2.5.1, 4.2.5.4
Provide Technical Order Change Pages that are 90% accurate to meet objective. Provide Technical Order Change Pages that are 100% accurate to exceed objective
Perform all maintenance tasks required to maintain GFE in a serviceable condition
4.2.6.1, 4.2.6.2, 4.2.6.3, 4.2.6.4
Perform maintenance tasks to support 92% FMC rate to meet objective. Perform maintenance tasks to support 95% FMC rate to exceed objective
Perform repairs required to maintain GFE in a serviceable condition
4.2.6.3, 4.2.6.4
Perform repairs to maintain GFE at a 92% FMC rate to meet objective. Perform repairs to maintain GFE at a 95% FMC rate to exceed objective
Incorporate changes resulting from software problem reports into ATE software
4.2.2.3, 4.2.2.3.1
Incorporate changes resulting from government approved software problem reports 90% accurately to meet objective. Incorporate changes resulting from government approved software problem reports 100% accurately to exceed objective

SECTION III

GOVERNMENT FURNISHED EQUIPMENT (GFE) AND SERVICES

0. GFE/GFP

To support weapon system requirements, the Government will make available, on a rent-free non-interference basis, to BAE Systems, F-16 Full Scale Development (FSD) AdC AIS, IAIS, VXI-IAIS, and R-IAIS test stations for the duration of this effort. GFE is currently located in Fort Worth, Texas, and San Diego, California, respectively. GFE shall not be moved without authorization from the Government Contracting Officer (CO). AdC AIS GFE will be maintained until the identified “Sunset” date for AdC test stations, 30 June 2026.

0.0.1 GFE/GFP in support of this effort will be identified utilizing the appropriate forms and/or systems. Upon request, the Government may approve additional functional GFP, material, or equipment if required to support GFE maintenance activities.

0.0.2 The contractor shall perform an annual physical inventory of all GFE/GFP assets in their possession. A report shall be generated and provided to the Government on an annual basis. Reporting period is one year from contract award (IAW CDRL A013, DI-MGMT-80441D, Annual Government Property Physical Inventory Report).

0.0.3 The Government may make Government-archived technical data available to the contractor (as appropriate) in support of this effort.

0.0.4 When technical work is performed on-site at Government facilities, the Government will provide workspace, office supplies, access to computer data bases, and other resources, as defined at the Task Order level, at no cost to the contractor.

1.2 Services: The contractor shall furnish all material, SE, tools, general purpose test equipment, and services required by this PWS unless specified elsewhere herein.

1.3 Foreign Disclosure: Foreign Disclosure restrictions do apply.

SECTION IV

GENERAL INFORMATION

4.1 General Work Requirement:

The contractor shall be responsible for the accomplishment of all ATE Commodities Sustainment tasks necessary to support USAF and EPAF/FMS intermediate and depot-level operational requirements, as defined by the Government at the Task Order level.

The contractor shall be responsible for the accomplishment of all Sustaining Engineering tasks necessary to support operational requirements for all established configurations of F-16 AIS test stations, as defined by the Government at the Task Order level.

The contractor shall be responsible for the accomplishment of Software Integration tasks, to include the procurement of all materials necessary for the integration and subsequent maintenance of applicable operating software for the VXI-IAIS, R-IAIS, and IAIS test stations, as defined by the Government at the Task Order level.

The contractor shall be responsible for the accomplishment of all maintenance and maintenance-related engineering and technical activities necessary to keep all configurations of GFE AIS test stations in a state of operational readiness in support of mission requirements, as defined by the Government at the Task Order level. The GFE is utilized to accomplish hardware/software engineering tasks; perform technical studies and engineering analysis; provide spares support and field assistance; perform non-recurring engineering activities; and perform repair, modification, and/or equipment manufacturing to support AIS system requirements.

The contractor shall perform all maintenance functions to maintain GFE in a mission capable state to meet program requirements contained in this PWS. Maintenance functions shall include, but are not limited to, operational testing, daily self-test, diagnostic testing, calibration; and preventative maintenance and repair of station equipment and/or associated components as contained within this PWS.

The contractor shall be responsible for the accomplishment of all tasks and material necessary to revise and maintain F-16 AIS Series of Test Stations Technical Orders in a current and accurate state In Accordance With (IAW) this PWS. Technical Orders to be maintained shall be identified at the Task Order level.

0. Data

4.1.1.1 Contract Data Requirement List (CDRLs): The contractor shall prepare and submit the following documents and media in support of this work effort IAW the CDRL Exhibits cited below.

FORM/REPORT SHORT TITLE
FORM/REPORT TITLE
APPLICABLE CDRL EXHIBIT/DIRECTIVE
Monthly Status Report
Contractor’s Progress & Status Report
A001, DI-MGMT-81928/T
Technical Report
Technical Report-Study/Services
A002, DI-MISC-80508B
Technical Manual Contract Requirements
Technical Manual Contract Requirements (TMCR)
A003, TM-86-01R
Engineering Data for Provisioning
Engineering Data for Provisioning (EDFP)
A004, DI-SESS-81874A/T
Logistics Product Data
Logistics Product Data
A005, DI-SESS-81758A/T
Engineering Design Data
Acquisition and Sustainment Data Package (ASDP) Engineering Design Data and Associated Lists (EDDAL)
A006, DI-SESS-82351A/T
Material Improvement Project Plan
Acquisition and Sustainment Data Package (ASDP) Material Improvement Project Plan
A007, DI-MGMT-80258C
Operating Software Information
Computer Program End Item Documentation
A008, DI-IPSC-80590B
Operating Software Information
Computer Program Manual (CPM)
A009, DI-IPSC-81447A
Software Manual
Software User Manual
A010, DI-IPSC-81443A
Configuration Status Accounting Information
Configuration Status Accounting (CSA) Information
A011, DI-SESS-81253E
Safety Hazard Report
System Safety Hazard Analysis Report (SSHAR)
A012, DI-SAFT-80101D
Government Inventory Report
Government Property (GP) Inventory Report
A013, DI-MGMT-80441D
Program Management Plan
Management Plan
A014, DI-MGMT-80004A
Supply Chain Risk Management Plan
Supply Chain Risk Management (SCRM) Plan
A015, DI-MGMT-82256A
DMSMS Implementation Plan
Diminishing Manufacturing Sources and Material Shortages (DMSMS) Implementation Plan
A016, DI-MGMT-81949
DMSMS Management Plan
Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan
A017, DI-MGMT-81948
Counterfeit Prevention Plan
Counterfeit Prevention Plan
A018, DI-MISC-81832

4.1.1.2 Technical Data: The contractor shall modify technical data IAW the contractor’s engineering directives, internal drawings and procedures; Acceptance Test Procedures, and other procedures as mutually agreed upon by the contractor and the Government in compliance with the applicable Data Item Description (DID). Station software installation and operation instructions shall be provided in the Software Version Document (SVD) complying with the applicable DID). Technical data requirements will be identified and defined at the Task Order level.

0. Security The contractor shall comply with all requirements of DD Form 254, Department of Defense Contract Security Classification Specification, attached to the contract.

4.1.2.1 This effort has a valid Facility Clearance with SECRET safeguarding capabilities. The contractor shall require access to Controlled Unclassified Information (CUI), Program and Security Classification Guides, and classified TPS software. The contractor shall adhere to all Operations Security (OPSEC) requirements. Contractor personnel shall receive and generate classified information, fabricate, modify, and/or store classified hardware, require access to classified information outside the U.S., Puerto Rico, U.S. possessions and trust territories. The contractor shall ensure that all technical, analyst, and managerial personnel have the appropriate security clearances for the work being performed. Tasks may include work up to the Secret level. Strictly administrative duties performed by contractor personnel shall not require a security clearance; however, personnel assigned these duties may require an investigation for sensitive duties.

4.1.2.2 The contractor shall establish a COMSEC account for classified material used in performance of this contract. Associated classified material stored at contractor facilities, shall be handled and stored according to COMSEC safeguarding requirements IAW 32 CFR Part 117/NIPSOM, Section 117.21.

4.1.2.3 All EPAF/FMS applicable tasks shall be performed IAW International Traffic in Arms Regulations (ITAR) and Export Administrative Regulations (EAR). The contractor and Directorate of Defense Trade Controls (DDTC) registered subcontractors utilizing the FMS exemption (126.6(c)) for defense services, technical exchanges, and delivery of hardware, must ensure the respective Letter of Offer and Acceptance (LOA) is valid at the time exports are performed. If the LOA expires and is unable to be renewed/extended prior to the delivery of hardware, technical data, and defense services, the applicable EPAF/FMS customer(s) will be responsible for ultimate delivery.

4.1.3 Supply Chain Risk Management

The contractor shall identify, assess, plan for, and mitigate actual or potential threats, vulnerabilities, and disruptions to the USAF’s supply chain throughout its lifecycle to ensure mission effectiveness. The contractor shall detail specific supply chain risks and provide a management and mitigation plan identifying how the contractor will ensure Supply Chain Risk management is effective over the life of the contract (IAW CDRL A015, DI-MGMT-82256A, Supply Chain Risk Management (SCRM) Plan).

4.1.3.1 The Supply Chain Risk Management (SCRM) Plan shall address the broad spectrum of supply chain risks that have the potential to jeopardize the integrity of products, services, people, and technologies, compromise intellectual property, disrupt the flow of product, materiel, information, and finances needed for continued USAF operations, and drive materiel cost increases to the program. The contractor shall inform and include the Government in any mitigations or alterations to the program via updates to the SCRM plan (IAW CDRL A015, DI-MGMT-82256A, Supply Chain Risk Management (SCRM) Plan).

4.1.3.2 The contractor shall develop and execute processes for identifying supply chain risks as early as possible, to include: the persistent and comprehensive tracking, monitoring, and re-evaluation of supply chain risks and their corresponding mitigation actions, and communicating supply chain risks to affected stakeholders and the Government. The contractor shall notify the Government in writing of identified actual and potential supply chain risks and include them as subsequent updates to the SCRM plan (IAW CDRL A015, DI-MGMT-82256A, Supply Chain Risk Management (SCRM) Plan).

4.1.3.3 The contractor’s SCRM program and processes shall apply to the prime and their suppliers, subcontractors, associated integrators, and vendors, spanning the entirety of the supply chain, from the lowest level possible (i.e. raw material or Class II vendors) to delivery of a finished product and/or service.

4.1.3.4 As part of the overall SCRM approach, the contractor shall establish, document, and maintain documentation about subcontractors/vendors for all parts that will be used for Government contracts. The contractor shall continuously monitor their sources of supply for unknown, unauthorized, non-certified, or unqualified sources providing parts or services from any sub-tier supplier within the contractor’s supply chain. The contractor shall investigate and submit findings, as needed, to update the SCRM plan. Findings may include root causes, impacts, and corrective action (IAW CDRL A015, DI-MGMT-82256A, Supply Chain Risk Management (SCRM) Plan).

4.1.3.5 The SCRM plan shall detail the contractor’s supply chain risk management approach, providing specific emphasis on the risks associated with the following: Continuity of Operations, Foreign Influence, and Cybersecurity. Each element shall be included in the overarching SCRM plan provided to the Government (IAW CDRL A015, DI-MGMT-82256A, Supply Chain Risk Management (SCRM) Plan).

1.1.4 Contingency of Operations

The contractor shall develop and/or update a Continuity of Operations Plan (COOP), also known as a Business Operations Plan, which outlines the processes and actions to prepare for, and respond to, unplanned natural and man-made disruptions to mission essential operations and provide it to the Government as part of the SCRM plan (IAW CDRL A015, DI-MGMT-82256A, Supply Chain Risk Management (SCRM) Plan). The COOP shall address disruptions caused by the following:

1. Natural causes possible in the local vicinity (winter weather, earthquakes, hurricanes, fires, flooding, wind, pandemics, etc.)

2. Man-made causes (cyber-attacks, electrical outages, strikes affecting workforce, civil unrest, modes of transportation, and receiving/shipping goods, etc.)

4.1.4.1 In the event of disruption, the COOP will explain the following contingencies:

1. How work will continue in the same or alternate facility(ies)

2. Ability to use and/or augment the current workforce

3. Ability to repair/restore key infrastructure (machinery, computers, logistics, etc.)

4. How to maintain communication with the Government and others in the supply chain

4.1.4.2 The contractor shall provide essential records management for personnel working on USAF contracts. Records will be accessible to key members of the organization. The contractor shall ensure continuous records management support (training, etc.) despite any change in personnel.

4.1.4.3 If required, the contractor shall prepare for the continuation of essential DoD services during a crisis IAW DFARS 252.237-7023, DFARS 252.237-7024, and other applicable references as necessary. In a state of emergency, if the Government deems necessary, the contractor shall provide all services necessary to ensure mission accomplishment. On occasion, services may be required to support activation, or exercise of contingency plans outside normal duty hours.

1.1.5 Foreign Influence

The contractor shall disclose any Foreign Ownership, Control, or Influence for the purpose of initial or continued facility clearance eligibility. A Standard Form 328, Certificate Pertaining to Foreign Interest, shall be submitted to the cognizant Government security office specified in each DD254.

4.1.5.1 The contractor shall provide information regarding Foreign Ownership, Control, or Influence. The contractor shall provide an update on its financial health and potential Foreign Ownership, Control, or Influence when a merger or acquisition occurs via an update to the SCRM plan (IAW CDRL A015, DI-MGMT-82256A, Supply Chain Risk management (SCRM) Plan).

4.1.5.2 Foreign contractor participation is excluded at the prime and subcontractor level, unless authorized through a current approved National Interest Determination (NID). It is solely the responsibility of the contractor to obtain necessary certification from the U.S. Department of State and comply with the federal laws and regulations. Questions must be directed to the U.S. Department of State’s Directive of Defense Trade Controls.

1.1.6 Cybersecurity

The contractor shall develop and implement a cybersecurity protection of supply chain information plan and provide a copy to the Government as part of the overall SCRM plan (IAW CDRL A015, DI-MGMT-82256A, Supply Chain Risk Management (SCRM) Plan). The contractor shall conduct early and continuous monitoring throughout the contract to prevent or reduce impacts of cyber vulnerabilities where adversaries are able to exploit, steal, alter, manipulate, interrupt, or destroy system functionality, information, or technology. The contractor’s plan shall address the following:

4.1.6.1 Make specific reference to these aspects of the National Institute of Standards and Technology Special Publication (NIST SP) 800-161, Supply Chain Risk Management Practices for Federal Information Systems and Organizations, that represent the contractor’s implemented processes and practices.

4.1.6.1.1 Include a description of how the contractor shall protect the supply chain from exploitation due to the insertion of counterfeits/malware, unauthorized production, tampering, theft, insertion of malicious software and hardware, functionality alteration, and any other elements that would allow adversaries to gain unauthorized access to data, alter data, interrupt communications, or otherwise disrupt operations.

4.1.6.1.2 Inform the Government of any instances of unauthorized access and/or compromises to the contractor’s digital information, parts, and/or components.

4.1.6.1.3 Make specific reference to those aspects of NIST SP 800-53 that represent the processes and practices the contractor will implement. The plan and processes shall apply to the prime and their suppliers, subcontractors, associated integrators, and vendors, spanning the entirety of the supply chain from the raw material stage to delivery of a finished product.

4.1.6.1.4 When required, the contractor and any subcontractors shall provide to the Government a system security plan and any associated plans of action developed to satisfy the adequate security requirements of DFARS252.204-7012, and IAW NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, in effect at the time the solicitation is issued or as authorized by the Contracting Officer, to describe the contractor’s unclassified information system(s)/network(s) where covered defense information associated with the execution and performance of this contract is processed, is stored, or transmits. This information shall be submitted as part of the overall SCRM plan (IAW CDRL A015, DI-MGMT-82256A, Supply Chain Risk Management (SCRM) Plan).

4.1.6.2 The contractor shall ensure all hardware, with special emphasis on lowest Critical Components (CC) and components containing Critical Program Information (CPI), are from trusted sources and are manufactured by approved personnel as documented in the contractor’s Security Plan. To mitigate supply chain risk, the contractor’s SCRM plan shall document their Security Plan, IAW The Committee on National Security System Directive (CNSSD) No. 505 and NIST SP 800-61.

4.1.6.3 The contractor shall ensure that no critical components procured are on the Section 806 (National Defense Authorization Act of Fiscal Year 2011 (Public Law 111-383)) and Section 2339a (Title 10, United States Code) Lists in the Supplier Performance Risk System (SPRS). The contractor shall develop and implement a Counterfeit Parts Prevention Program in compliance with Defense Federal Regulation (DFAR) 252.246-7007 Contractor Counterfeit Electronic Part Detection and Avoidance System, using SAE AS5553, SAE AS6171, SAE AS6081, and Independent Distributors of Electronics Association (IDES) Standard {IDEA-STD-1010B}) or similar practices to prevent the inclusion of counterfeit parts or parts with malicious logic. The contractor shall perform acceptance testing on lowest CCs and components containing CPI IAW Counterfeit Parts Prevention Program (IAW CDRL A018, DI-MISC-81832, Counterfeit Prevention Plan).

4.1.6.4 The contractor shall implement DoD Trusted Systems and Networks (TSN) strategies that integrate robust engineering, SCRM, security, counterintelligence, intelligence, cybersecurity, hardware and software assurance; and information systems security engineering disciplines to manage risk to system integrity and trust IAW DODI 5200.44, Protection of Mission Critical Functions to Achieve TSN.

4.1.6.5 All tasks shall be performed in compliance with Technical Order 33-1-38, Cybersecurity for Automatic Test Systems and Automatic Test Equipment in FSC. Cybersecurity requirements shall be identified and defined at the Task Order level.

1.1.7 Quality

4.1.7.1 The contractor shall establish, document, and maintain a quality system, such as International Organization for Standardization (ISO) 9001:2015, as a means of ensuring that the requisite quality assurance oversight is exercised in fulfilling the requirements of this effort. The contractor shall ensure that this requirement is levied on any subcontractors used in satisfying the requirements of this effort. The contractor shall maintain Capability Maturity Model Integration (CMMI) Level 3 Certification (appraised and maintained at Level 3) throughout the duration of this effort. The contractor shall manage, document, and implement all software changes under the BAE Systems Software Engineering Institute (SEI) validated process.

1.1.8 Safety Mishap and Reporting:

4.1.8.1 The contractor shall comply with safety and mishap reporting requirements. Report shall be provided to the Government as required (IAW CDRL A012, DI-SAFT-80101D, Safety Hazard Report).

1.2 SPECIFIC WORK REQUIREMENTS

1.2.1 Contractor Program Management Organization

4.2.1.1 The contractor shall provide the necessary administrative, financial, quality assurance, analyst, specialist, technical, and/or managerial personnel and resources necessary to fulfill Government requirements. These personnel shall also provide a program management organization to manage internal requirements, serve as the focused point of contact, and ensure all aspects of this program are adequately controlled and monitored.

4.2.1.2 The contractor shall be responsible for any subcontract management necessary to meet Government requirements and shall be responsible and accountable for subcontractor performance. The contractor will manage work distribution to ensure there are no Organizational Conflict of Interest considerations. The contractor may add subcontractors to their team only after notification to the Contracting Officer and Contracting Officer Representative.

4.2.1.3 The contractor shall develop and provide a Program Management Plan (PMP) (IAW CDRL A014, DI-MGMT-80004A, Management Plan). The PMP shall provide information on the contractor’s organization, practices, and techniques to be utilized in managing both the program and working relationships with subcontractors, vendors, and Government customers to provide complete and comprehensive sustainment of AIS ATE Commodities. The PMP shall include, but is not limited to, the plan purpose, scope, schedule, budget, performance plan, quality plan, risk plan, and any additional support plans required to complete the requirements of this effort. At minimum, the PMP shall address the following areas:

1. Identification of key personnel positions.

2. Approach to ensure technical experts have appropriate training and certification.

3. Approach for accountability of GFP/GFE.

4. Acquisition of contractor Common Access Cards (as required).

5. Acquisition of other facility access card(s) (as applicable).

6. Issuance of appropriate Security clearances (as applicable).

7. Timelines for submitting contract data requirements.

8. Approach to ensure open communication with the Government, to include periodic (daily, weekly, etc.) reviews documenting progress.

9. The contractor shall process changes to the established plan following their documented quality procedures. Any subsequent changes and/or amendments to the established PMP throughout the Period of Performance shall be IAW (CDRL A014, DI-MGMT-80004A Management Plan, and shall be documented in the corresponding Monthly Status Report(s), CDRL A001, DI-MGMT-81928/T, Monthly Status Report).

4.2.1.4 The contractor shall be required to participate in a Government-scheduled Kick-Off Meeting after contract award. The purpose of the Kick-Off Meeting is to:

4.2.1.4.1 Aid both the Government and the contractor in achieving a clear and mutual understanding of all requirements.

4.2.1.4.2 Identify and resolve potential problems. The contractor shall be prepared to discuss any contract requirements calling for clarification. The Government, with mutual input from the contractor, will schedule the Kick-Off meeting to be conducted within 30 days of contract award. The contractor shall prepare a tentative agenda for the Kick-Off meeting and submit it to the Contracting Officer Representative (COR) within two (2) weeks of Kick-Off meeting. The contractor shall incorporate any COR comments into the agenda no later than one (1) week prior to the Kick-Off Meeting. Within 10 business days after Kick-Off meeting conclusion, the contractor shall provide meeting minutes.

4.2.1.5 The contractor shall provide system-level support for problem resolution and sustainment activities to ensure operational capability of existing ATE and ATE commodities. This support includes component design and specialty engineering, data management, and Configuration Management compliance activities. This support shall also include analysis of deficiencies not previously identified during operational use of fielded equipment. Support and sustainment activities shall be provided at Air Force Sustainment Center (AFSC) facilities, Air Force Life Cycle Management Center (AFLCMC) facilities, contractor facilities, or at field sites when required by the Government.

4.2.1.6 The contractor shall provide Rough Order of Magnitude (ROM) estimates as requested by the 416 SCMS to support anticipated sustaining engineering tasks not previously identified, at no cost to the Government.

4.2.1.7 The contractor shall ensure that discrete vendor system sub-elements are fully compatible by integrating the fabricated systems and sub-systems with each other to ensure that no operational deficiencies are identified.

4.2.1.8 The contractor shall evaluate the possible solutions sets for system and sub-system integration deficiencies, select the most cost-effective solution set, and direct the appropriate vendor to remedy the deficiencies.

4.2.1.9 The contractor shall model and analyze different hardware/software technical solution sets to optimize solutions.

4.2.1.10 The contractor shall analyze different logistics support approaches for candidate systems and, if necessary, conduct Non-Recurring Engineering (NRE) activities to develop sustainment alternatives for ATE commodities.

4.2.1.11 The contractor shall travel as required to attend Program Management Reviews (PMRs), Working Group meetings, Technical Interchange Meetings (TIMs), quality oversight activities, and design reviews. Reference 4.3 for travel guidelines.

1.2.2 HILL AIR FORCE BASE ON-SITE TECHNICAL SUPPORT

In order to ensure the sustainment and operational capability of fielded AIS ATE and ATE components, the contractor shall provide the Government with on-site Commodity Sustaining Engineering and Component Software Integration and Maintenance technical support. Operational capability shall be achieved through troubleshooting, and subsequently resolving, technical issues being experienced in the field by USAF, EPAF, and FMS customers. Primary technical support shall be provided on-site at Hill AFB. However, this effort may include providing technical support on-site and off-site at Government and contractor locations, as well as at F-16 field locations worldwide in support of 416 SCMS requirements. Technical support shall be provided by one (1) Full-time Equivalent (FTE) personnel. Technical support may include but not be limited to the elements identified below:

4.2.2.1 Liaison Support: Act as a liaison for AIS Systems with contractors, Hill AFB Avionics Integration Support Facility (AISF) software engineers, and Hill Air Force Base (AFB) Depot maintenance personnel. Liaison services shall include attendance at meetings, reviews, and the preparation of technical information needed to support AFSC and/or AFLCMC requirements. Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (IAW CDRL A001, DI-MGMT-81928/T, Monthly Status Report).

4.2.2.2 Commodity Sustaining Engineering Support: The contractor shall monitor the operational status of fielded AdC AIS, IAIS, VXI-IAIS, and R-IAIS stations. This includes coordinating field site requests for assistance in resolving issues relating to test station operations, requesting failure data for analysis of reported problems, identifying failure trends; and recommending appropriate hardware, software, and/or Technical Order changes to resolve technical issues. In order to provide the identified technical support, access to Government databases and facilities shall be required.

4.2.2.2.1 The contractor shall provide technical assistance to the Government to create Field Service Bulletin (FSB) and Time Compliance Technical Order (TCTO) instructions for hardware modifications, enhancements, and operating software releases. The contractor shall prepare kit build-up documentation; schedule, coordinate, and support field kit-proofs; coordinate release of TCTOs; and monitor and report TCTO accomplishments (IAW A003, TM-86-01R, Technical Manual Contract Requirements). Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (IAW CDRL A001, DI-MGMT-81928/T, Monthly Status Report).

4.2.2.2.2 The contractor shall develop and maintain hardware and software acquisition and sustainment plans. The contractor shall draft, process, and disseminate the information on AF Forms 1243, CPIN/AFCRI Data and Control Record Part 1, and AFTO Forms 873, Time Compliance Technical Order Requirements, in support of hardware and software requirements; generate Computer Program Identification Number (CPIN) labels; and manage ATE and software Material Improvement Project (MIP) bucket changes affecting AFLCMC and/or AFSC-managed equipment (IAW CDRL A008, DI-IPSC-80590B, Computer Program End Item Documentation; CDRL A009, DI-IPSC-81447A, Computer Program Manual (CPM); CDRL A010, DI-IPSC-81443A, Software User Manual; CDRL A007, DI-MGMT-80258C, Acquisition and Sustainment Data Package (ASDP) Material Improvement Project Plan). Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (CDRL A001, DI-MGMT-81928/T, Monthly Status Report).

4.2.2.2.3 The contractor shall provide logistics operation support, as required, when assigned by the AIS Systems Sustainment Program and/or Government Logistics Managers. The contractor shall be required to travel in support of assigned tasks. Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (IAW CDRL A001, DI-MGMT-81928/T, Monthly Status Report).

4.2.2.3 F-16 AIS Component Software Integration and Maintenance Support: The contractor shall coordinate software problem reports from IAIS/VXI-IAIS/R-IAIS field sites, Hill AFB AISF, Hill AFB Depot, and contractor engineering/testing facilities. Reports may include problems related to test station operations, diagnostics calibration, C&S/Self-Test software, and/or Line Replaceable Unit (LRU) Test Program Sets (TPSs). The Government shall approve, schedule, and prioritize required tasks addressing software deficiencies and/or other tasks resulting from reports.

4.2.2.3.1 The contractor shall generate deficiency and problem reports based on pact and severity to the reported test station. The contractor shall review and categorize reports for work by the responsible engineering facility for engineering investigation/analysis. The contractor shall edit, test, and review operating software loading instructions for inclusion in the appropriate Technical Order.

4.2.2.3.2 The contractor shall organize, schedule, and participate in Software Compatibility Tests and software Validation and Verification (V&V) activities; provide technical inputs, as well as develop and maintain software program schedules, plans, checklists, documentation, and procedures. When directed by the Government, the contractor shall schedule, organize, and conduct Technical Order risk reduction activities; coordinate software kit-proofs; and sustain software programs with respect to corrective maintenance, performance improvement, and adaptive maintenance tasks performed within the bounds of existing system test specifications. Finally, the contractor shall provide data for ATE Technical Orders impacted by software and hardware updates (IAW A003, TM-86-01R, Technical Manual Contract Requirements). Support provided by the contractor shall be captured in the corresponding Monthly Status Report(s) (IAW CDRL A001, DI-MGMT-81928/T, Monthly Status Report).

1.2.3 ATE COMMODITIES SUSTAINING ENGINEERING:

The contractor shall provide ATE Commodity Sustaining Engineering support for hardware/software delivered to F-16 customers as part of the overarching AIS Systems Sustainment Program managed by the 416 SCMS. Support tasks are defined, in general, as tasks required to provide continued support to the Government for comprehensive management of AdC AIS/IAIS/VXI-IAIS/R-IAIS ATE commodities. This includes providing technical support to investigate and develop proposed solutions for ATE component hardware problems identified by USAF, EPAF, and FMS customers. Additionally, the contractor shall be responsible for identifying revisions to IAIS/VXI-IAIS/R-IAIS ATE component hardware necessary to accommodate the implementation of changes to LRU testing requirements. These additional requirements may be identified during field usage and evaluation, or whenever a determination is made that additional capability is required. Consequently, revisions to testing requirements may also drive changes to System Test Specifications (STS) and/or component hardware managed by the 416 SCMS.

4.2.3.1 Sustaining Engineering Technical Support

The contractor shall provide technical support for problem resolution and sustainment activities, as required, to ensure operational capability of existing F-16 AIS Systems and derivative ATE components. These activities shall support deficiencies not previously identified during operational use of AIS equipment. Support and sustainment activities shall be provided at Hill AFB, contractor facilities, and/or at field sites when required by the Government.

4.2.3.1.1 The contractor shall provide engineering and/or technical assistance for F-16 AIS test stations, derivative ATE components, and/or associated equipment for which the USAF does not have organic engineering capability or expertise to accomplish the needed assistance in a timely manner. As the Government identifies issues, assistance shall be requested via email or telephone. Technical assistance may be at 416 SCMS/GUMAA (Hill AFB), field user locations (USAF/EPAF/FMS), or at contractor facilities. Assistance requests shall be fully defined for the respective requirements being supported.

4.2.3.1.2 Travel for this effort may be required to provide engineering/technical assistance for F-16 AIS test stations, ATE components, and/or associated Support Equipment at CONUS and/or OCONUS USAF/EPAF/FMS field site locations in support of weapon system requirements. Efforts requiring extensive engineering/technical troubleshooting and/or maintenance may be executed on separate Task Orders in order to ensure successful resolution of complex technical issues (i.e. intermittent failures). The contractor shall work with the Government when these issues arise to determine if separate contract efforts (Task Orders) are warranted.

4.2.3.1.3 The contractor shall perform failure analysis to address Electrostatic Discharge (ESD) related failure modes, their resulting consequences, and recommendations for corrective action; particularly when contained in contractor proposed Advanced Change Study Notices (ACSNs) and Engineering Change Proposals (ECPs) for electronic parts, assemblies, and equipment (IAW CDRL A002, DI-MISC-80508B, Technical Report-Study/Services).

4.2.3.1.4 The contractor shall review and analyze FSBs and DRs, with their associated exhibits, for cause(s) of failure(s). Analysis may entail complete teardown and testing of subject AIS system hardware. The contractor shall provide resulting data to the Government according to the appropriate CDRL(s) (IAW CDRL A002, DI-MISC-80508B, Technical Report-Study/Services; CDRL A007, DI-MGMT-80258C, Acquisition and Sustainment Data Package (ASDP) Material Improvement Project Plan).

4.2.3.1.5 When required by the Government, the contractor shall perform and provide engineering studies, problem investigations and analyses; operational evaluations, Teardown Deficiency Reports, sustainment recommendations, and system and sub-systems evaluations (IAW CDRL A002, DI-MISC-80508B, Technical Report-Study/Services).

4.2.3.1.6 The contractor shall perform Reliability and Maintainability (R&M) studies, to include reliability, analyses, maintainability analyses, field data evaluations, environmental stress screenings, and/or other R&M related tasks in support of Government requirements (IAW CDRL A002, DI-MISC-80508B, Technical Report-Study/Services).

4.2.3.1.7 The contractor shall utilize best commercial practices whenever submitting analyses, drawings, reports, evaluations, studies, etc. (IAW CDRL A002, DI-MISC-80508B, Technical Report-Study/Services).

4.2.3.1.8 The contractor shall submit prepared engineering drawings and associated lists in the designated appropriate forms to support technical problem resolution(s). When required, the contractor shall also provide complete set(s) of engineering drawings suitable for investigations, analyses, feasibility studies, engineering prototype development and testing; and/or hardware/software deficiency corrections (IAW CDRL A006, DI-SESS-82351A/T, Acquisition and Sustainment Data Package (ASDP) Engineering Design Data and Associated Lists (EDDAL)).

4.2.3.2 Logistics Sustaining Engineering Support

The contractor shall maintain software tools to provide the Government with the required provisioning data and supporting logistics documentation for ATE commodities. The contractor shall be responsible for obtaining the appropriate software-operating license(s). The software tools, at a minimum, shall contain the necessary elements required to submit accurate logistics and provisioning data to the Government.

4.2.3.2.1 The contractor shall provide data for and participate in provisioning processes IAW the appropriate CDRLs (CDRL A004, DI-SESS-81874A/T, Engineering Data for Provisioning (EDFP); CDRL A005, DI-SESS-81758A/T, Logistics Product Data) and the Initial Provisioning Performance Specification (IPPS). Order precedence for Engineering Data for Provisioning shall be IAW the IPPS.

4.2.3.2.2 The contractor shall provide logistics support documentation formatted similar to SAE-GEIA-STD-0007. Each part must have a unique identification number called a Provisioning List Item Sequence Number (PLISN), level of indenture, National Stock Number (NSN), manufacturer…

This is the start of the file's text. The full file is on GovTribe.

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