Inactive

Please direct all questions and responses regarding this Synopsis directly to the PCO, Ian Morris. This announcement constitutes a Synopsis for Common Weapons Engagement Zone (CWEZ) for the F-16 aircr... Please direct all questions and responses regarding this Synopsis directly to the PCO, Ian Morris. This announcement constitutes a Synopsis for Common Weapons Engagement Zone (CWEZ) for the F-16 aircraft. AFLCMC/WAM F-16 System Program Office intends to award an IDIQ contract for 5 years to provide the the F-16 Aircraft Weapons System Division updating of CWEZ software on the F-16 Weapon System to include Software Capabilities Upgrade (SCU), Multi-Mission Computer (MMC M-Series), EPAF MLU F-16 Blk 15 Weapon System Operational Flight Program (OFP). The contractor-delivered CWEZ software will be integrated into the above listed OFP programs on their respective F-16 platforms by the US Air Force. This action is being conducted to identify potential sources capable of meeting the requirements for the following examples, but not limited to the following draft statement of work: 1.0 DESCRIPTION OF SUPPLIES This Statement of Work (SOW) defines the effort for this IDIQ of the F-16 Aircraft Weapons System Division updating of Common Weapon Engagement Zone (CWEZ) software on the F-16 Weapon System to include, Software Capabilities Upgrade (SCU), Multi Mission Computer (MMC M-Series), EPAF MLU F-16 Block 15 Weapon System Operational Flight Program (OFP). The contractor shall deliver CWEZ software to the US Air Force. The contractor delivered CWEZ software will be integrated into the above listed OFP programs on their respective F-16 platforms by the US Air Force. 2.0 SCOPE The F-16 Weapon System CWEZ Integration program includes re-host of the Zone Acquisition Process (ZAP) software into the Applicable F-16 weapons system defined under each Delivery Order (DO) per this IDIQ. The contractor developed CWEZ software will be integrated by 309th SMXG personnel at Hill AFB. 3.0 CONTRACTOR REQUIREMENTS 3.1 Software Language Conversion For each missile model in the current CWEZ version of ZAP, the contractor shall deliver to the US Air Force re-hosted C++ language software for integration into the aircraft OFP. All of the software test drivers delivered shall also be converted to C++ as necessary. 3.2 Software efforts 3.2.1 The ZAP software will include the most current missile models that are resident in the current CWEZ version of ZAP software. These include the AIM-9M, AIM-9XBLK-I/II, AIM-120B, AIM-120C, AIM-120C5/C7, AIM-120D. 3.2.2 The models will be converted from existing models and no new missile functionality will be required. 3.2.3 The missile models will reflect the truth simulations provided by Raytheon. 3.2.4 The following Example of capabilities but not limited to, below will be delivered or required under each D/O of this IDIQ: 1. AIM-9X Block I Air to Ground WEZ 2. AIM-9X Block I Zone 1-4 simulation adapted to maneuver zone (RMAX, RTR, RTC, RMIN) 3. AIM-9X Block II Zone 1- 4 simulation adapted to maneuver zone (RMAX, RTR, RTC, RMIN) 4. AIM 9X Block II Air to Ground WEZ 5. AMRAAM all variants simulation adapted to maneuver zone (RMAX, RTR, RTC, RMIN) 6. Provide Decoupled Weapon Engagement Zone (DWEZ) software and any new updates for AIM-9M, AIM- 9X BLK-I/II, and all AMRAAM variants as they become available. 3.3 Software Rights and Licensing 3.3.1 The contactor shall identify the computer software subparts that it, its subcontractors or suppliers, assert should be furnished with restrictions on use, release or disclosure. For each software piece identified, the supplier shall provide a reason for the restriction along with the party claiming the restriction. 3.4 Integration Support The contractor shall provide integration support to the US Air Force for the delivered re-hosted C++ software. This support shall consist of Common WEZ analysis of potential software integration and test deficiencies/issues with F-16 Weapons System(s) OFP software. 3.5 Interface Memorandum System The contractor shall establish an Interface Memorandum (IFM) system to provide a formal correspondence system with WWMPA. An IFM shall be used as a form of communication between the contractor, WWMPA, and the 309th. 3.6 Program Management The contractor per this IDIQ shall monitor, assess, manage, and mitigate risks to cost, schedule and technical performance throughout the period of performance of each D/O to include but not limited to the following examples: Shall conduct or attend the following but not limited to program meetings: 1. Technical Interchange Meetings (TIMs) 2. Kickoff Meeting 3. Design Review 4. FCA/PCA 3.7 CDRL List Shall submit the following basic contract data items as called out per D/O: 1. Status Report 2. Software Requirements Specification 3. Software Version Description 4. Software Test Description 5. Software Test Plan 6. Interface Control Document (ICD) 7. Software Product Specification 8. Software Design Description 9. ZAP executable code and Map tool/supporting documentation 10. Software Test Report 4.0 DELIVERY SCHEDULE AND PERIOD OF PERFORMANCE The delivery schedule and period of performance for this effort shall be defined per D/O for each F-16 Weapons System integration effort. 5.0 TRAVEL The Contractor may be required to travel to various Department of Defense and commercial facilities. Notification of travel will be sent to the Project Officer for base clearance. The contractor will be responsible for making his own travel and lodging arrangements necessary to support the task requirement. The Travel for the contractor will be called out and or defined under each D/O per this IDIQ. 6.0 SECURITY 1. The Contractor shall establish and maintain a security program to satisfy the requirements of the Government-provided Contract Security Classification Specification, DD Form 254. 2. The Contractor shall support Government in fulfilling IA requirements needed to support fielding the OFP/Software/Firmware or Hardware product. This includes but is not limited to: Certificate of Volatility (COV), Supporting IA Risk Assessment, Assistance in Conducting Criticality Analysis (CA) and Demonstration of visibility into supply chain and Software Assurance (SWA) for critical components. Deep dive analysis on site of the COV once final COV is bought off by the government, typically 2-4 days to complete on site deep dive. 7.0 GOVERNMENT PROVIDED EQUIPMENT/INFORMATION (GFE/GFI) The Government will provide no GFE/GFI to the contractor in order to satisfy the work scope delineated in this SOW.

Inactive

Please direct all questions and responses regarding this Sources Sought directly to the PCO, Ian Morris. This announcement constitutes a Sources Sought for Common Weapons Engagement Zone (CWEZ) for th... Please direct all questions and responses regarding this Sources Sought directly to the PCO, Ian Morris. This announcement constitutes a Sources Sought for Common Weapons Engagement Zone (CWEZ) for the F-16 aircraft. This is not a Request for Proposal (RFP) or an Invitation for Bid (IFB), nor is it to be construed as a commitment by the US Government. The following information is to identify potential contractors who have the skills, experience, and knowledge required to successfully provide the described capability. AFLCMC/WAM F-16 System Program Office intends to award an IDIQ contract for 5 years to provide the the F-16 Aircraft Weapons System Division updating of CWEZ software on the F-16 Weapon System to include Software Capabilities Upgrade (SCU), Multi-Mission Computer (MMC M-Series), EPAF MLU F-16 Blk 15 Weapon System Operational Flight Program (OFP). The contractor-delivered CWEZ software will be integrated into the above listed OFP programs on their respective F-16 platforms by the US Air Force. This action is being conducted to identify potential sources capable of meeting the requirements for the following examples, but not limited to the following draft statement of work: 1.0 DESCRIPTION OF SUPPLIES This Statement of Work (SOW) defines the effort for this IDIQ of the F-16 Aircraft Weapons System Division updating of Common Weapon Engagement Zone (CWEZ) software on the F-16 Weapon System to include, Software Capabilities Upgrade (SCU), Multi Mission Computer (MMC M-Series), EPAF MLU F-16 Block 15 Weapon System Operational Flight Program (OFP). The contractor shall deliver CWEZ software to the US Air Force. The contractor delivered CWEZ software will be integrated into the above listed OFP programs on their respective F-16 platforms by the US Air Force. 2.0 SCOPE The F-16 Weapon System CWEZ Integration program includes re-host of the Zone Acquisition Process (ZAP) software into the Applicable F-16 weapons system defined under each Delivery Order (DO) per this IDIQ. The contractor developed CWEZ software will be integrated by 309th SMXG personnel at Hill AFB. 3.0 CONTRACTOR REQUIREMENTS 3.1 Software Language Conversion For each missile model in the current CWEZ version of ZAP, the contractor shall deliver to the US Air Force re-hosted C++ language software for integration into the aircraft OFP. All of the software test drivers delivered shall also be converted to C++ as necessary. 3.2 Software efforts 3.2.1 The ZAP software will include the most current missile models that are resident in the current CWEZ version of ZAP software. These include the AIM-9M, AIM-9XBLK-I/II, AIM-120B, AIM-120C, AIM-120C5/C7, AIM-120D. 3.2.2 The models will be converted from existing models and no new missile functionality will be required. 3.2.3 The missile models will reflect the truth simulations provided by Raytheon. 3.2.4 The following Example of capabilities but not limited to, below will be delivered or required under each D/O of this IDIQ: 1. AIM-9X Block I Air to Ground WEZ 2. AIM-9X Block I Zone 1-4 simulation adapted to maneuver zone (RMAX, RTR, RTC, RMIN) 3. AIM-9X Block II Zone 1- 4 simulation adapted to maneuver zone (RMAX, RTR, RTC, RMIN) 4. AIM 9X Block II Air to Ground WEZ 5. AMRAAM all variants simulation adapted to maneuver zone (RMAX, RTR, RTC, RMIN) 6. Provide Decoupled Weapon Engagement Zone (DWEZ) software and any new updates for AIM-9M, AIM- 9X BLK-I/II, and all AMRAAM variants as they become available. 3.3 Software Rights and Licensing 3.3.1 The contactor shall identify the computer software subparts that it, its subcontractors or suppliers, assert should be furnished with restrictions on use, release or disclosure. For each software piece identified, the supplier shall provide a reason for the restriction along with the party claiming the restriction. 3.4 Integration Support The contractor shall provide integration support to the US Air Force for the delivered re-hosted C++ software. This support shall consist of Common WEZ analysis of potential software integration and test deficiencies/issues with F-16 Weapons System(s) OFP software. 3.5 Interface Memorandum System The contractor shall establish an Interface Memorandum (IFM) system to provide a formal correspondence system with WWMPA. An IFM shall be used as a form of communication between the contractor, WWMPA, and the 309th. 3.6 Program Management The contractor per this IDIQ shall monitor, assess, manage, and mitigate risks to cost, schedule and technical performance throughout the period of performance of each D/O to include but not limited to the following examples: Shall conduct or attend the following but not limited to program meetings: 1. Technical Interchange Meetings (TIMs) 2. Kickoff Meeting 3. Design Review 4. FCA/PCA 3.7 CDRL List Shall submit the following basic contract data items as called out per D/O: 1. Status Report 2. Software Requirements Specification 3. Software Version Description 4. Software Test Description 5. Software Test Plan 6. Interface Control Document (ICD) 7. Software Product Specification 8. Software Design Description 9. ZAP executable code and Map tool/supporting documentation 10. Software Test Report 4.0 DELIVERY SCHEDULE AND PERIOD OF PERFORMANCE The delivery schedule and period of performance for this effort shall be defined per D/O for each F-16 Weapons System integration effort. 5.0 TRAVEL The Contractor may be required to travel to various Department of Defense and commercial facilities. Notification of travel will be sent to the Project Officer for base clearance. The contractor will be responsible for making his own travel and lodging arrangements necessary to support the task requirement. The Travel for the contractor will be called out and or defined under each D/O per this IDIQ. 6.0 SECURITY 1. The Contractor shall establish and maintain a security program to satisfy the requirements of the Government-provided Contract Security Classification Specification, DD Form 254. 2. The Contractor shall support Government in fulfilling IA requirements needed to support fielding the OFP/Software/Firmware or Hardware product. This includes but is not limited to: Certificate of Volatility (COV), Supporting IA Risk Assessment, Assistance in Conducting Criticality Analysis (CA) and Demonstration of visibility into supply chain and Software Assurance (SWA) for critical components. Deep dive analysis on site of the COV once final COV is bought off by the government, typically 2-4 days to complete on site deep dive. 7.0 GOVERNMENT PROVIDED EQUIPMENT/INFORMATION (GFE/GFI) The Government will provide no GFE/GFI to the contractor in order to satisfy the work scope delineated in this SOW.