C4S LE for MEL-LEDGR-BMS.docx

Call for Solutions for Launcher Approach - Launched Effects (LE) Technical Presentations to Inform Army Aviation’s Launch Approach for Launched Effects (LE) from Ground and Air

Point of Contacts for Submission:

Procurement Contracting Officer:

Angela L. Andrews, ACC-RSA CCAM-AVE-D Angela.L.Andrews5.civ@army.mil Contract Specialist Melissa Gaddis ACC-RSA CCAM-AVE-D melissa.d.gaddis.civ@army.mil

USARMY Redstone Arsenal ACC Mailbox ACC-RSA-UAS-Marketplace usarmy.redstone.acc.mbx.acc-rsa-uas-marketplace@army.mil

UAS Marketplace uasmarketplace@army.mil

Distribution Statement D: Distribution authorized to the Department of War and U.S. DoW contractors only; Administrative or Operational Use, 21/09/2022. Other requests shall be referred to the CPE Aviation, Unmanned Aircraft Systems Project Management Office (UAS PMO), SFAE-AVN-U, Redstone Arsenal, AL 35898-5000.

Please advise the cognizant Procurement Contracting Officer and Contract Specialist as soon as possible via the email above if your organization intends to submit a response to this Call for Solutions.

Additionally, if you have already initiated and submitted your Initial Acceptance Packet (IAP) with the UAS Marketplace team, please contact the Contracting Officer and Contract Specialist to notify them that your package is already submitted.

*Note on Continuous Submission: This is an open and continuous Call for Solutions. Submissions received by the Initial Evaluation Cut-Off Date will be prioritized for the first evaluation cycle. All submissions received thereafter will be evaluated on a continuous, rolling basis as they are received to ensure a steady pipeline of innovative solutions to the UAS Marketplace.

1. BACKGROUND

The U.S. Army Contracting Command – Redstone Arsenal (ACC-RSA) is issuing this Call for Solutions (abbreviated “Call” hereafter) against Commercial Solutions Opening (CSO) W58RGZ-26-S-C001 under the authority of 10 U.S.C. § 3458. This Call will seek solutions for integration and development to inform the U.S. Army’s Launcher Approach.

The Launcher Approach for Air Launched Effects by PM UAS currently considers the use of Modular Effects Launcher (MEL), the Launched Effects Dispenser for Ground and Rotorcraft (LEDGR), and the Navy’s Battle Management System (BMS). This Call does not seek to buy Launched Effects (LE) but rather to inform the United States Government’s (USG) path forward for its launcher development.

The primary goal of this Call is to inform the USG’s Launcher Approach by identifying solutions that are compatible with the LEDGR, Navy’s BMS, and/or the MEL systems, as well as inform the appropriate interfaces necessary to enable an open-systems launcher. Additionally, the USG seeks information on available industry solutions for common carry and launch tubes. The Call process is designed to evaluate systems that inform the USG on:

· Launched Effects Dispenser for Ground & Rotor (LEDGR) Interoperability

· Industry Common Launcher approaches

· Modular Effects Launcher (MEL) Interoperability

· Vendor Software Interoperability

The first data call review from industry must be submitted within 45 days of this announcement to the ACC-RSA point of contact at usarmy.redstone.acc.mbx.acc-rsa-uas-marketplace@army.mil. Following the initial review of submissions received, the United States Government may issue a new call for solutions in the future. The Government reserves the right to alter or cancel this call at any time.

The onboarding process and establishment of a Basic Ordering Agreement (BOA) or Other Transaction (OT) authorities, as described below, do not constitute a production contract or guarantee any future orders. All procurement initiated by the USG will be based on specific mission requirements and the availability of funds.

2. PROBLEM STATEMENT

The character and pace of modern warfare are being redefined by the rapid proliferation and innovation of UAS/LE. With many industry partners providing potential LE solutions, the USG requires a versatile launcher solution that is adaptable to various industry partner designs. The USG designed/owned MEL and LEDGR are to fill the capability gaps for current multiple LE solutions. The responses provided will help guide USG in developing the launcher architecture ensuring future needs of the Army are met. This Call does not seek to procure LE but to inform the USG on development of a launcher approach supporting LE. In general, the Government is seeking information to innovative solutions compatible with USG owned MEL, LEDGR, or BMS efforts and to identify potential commercial approaches available for common carry and launch tubes.

To address this urgent need, the Army must rapidly identify and assess innovative commercially available approaches that inform development of Army Aviation’s launchers and be integrated into the open-system launcher construct.

3. TECHNICAL ATTRIBUTES

A detailed description of the required and desired technical attributes for the launch solutions is provided in the SOO, included as Attachment 1 to this Call. Offerors must refer to the SOO for a comprehensive understanding of the Government's technical objectives detailing the following: Information/Approaches that can interface and launch from the USG owned LEDGR, Information/approaches on products that can provide common carry and launch multiple LE variants from a MEL, Information/approaches of products that can interface and launch directly from the MEL (ex: LE all up rounds), Information/Approaches on Vendor Software integration into USG software (Modular Open Systems Approach (MOSA) Strategy, API Drivers, etc.).

4. AWARD INFORMATION

4.1 Authority and Instrument Award

This Call is issued under the authority of CSO procedures detailed within the UAS Marketplace CSO W58RGZ-26-S-C001, found at:

https://sam.gov/workspace/contract/opp/f71bdf94c86846379f21abc2d73a7b54/view In accordance with 10 US Code 3458, use of a CSO is considered a competitive procedure.

The Government intends to establish one or more Firm-Fixed-Price BOAs as a result of this Call. A BOA is not a contract and does not obligate any funds or guarantee any future orders. It is a written instrument of understanding that establishes the terms and conditions for potential future orders. All orders placed against the BOA are subject to the availability of funds. Although the Basic Ordering Agreement (BOA) serves as the primary acquisition vehicle, procurements under this Call may utilize alternate methods. These options include existing interagency contracts, Other Transaction (OT) authorities, or newly negotiated FAR-based contracts.

4.2 Offeror Eligibility Requirements

To be eligible for the UAS Marketplace, offerors must meet all of the following requirements:

· All proposed solutions must be fully compliant with Section 848 of the National Defense Authorization Act (NDAA) for Fiscal Year 2020, which prohibits the procurement and use of UAS, and their critical flight components manufactured in covered foreign countries, including the People's Republic of China. Offerors must be prepared to provide a complete Bill of Materials (BOM) and support supply chain verification activities to prove compliance. Be considered a responsible contractor in accordance with FAR Part 9.1.

· Possess a Unique Entity ID (UEI) and have an active and approved registration in the System for Award Management (SAM.gov).

· Have an approved Commercial and Government Entity (CAGE) code.

· Have a current NIST SP 800-171 DoW assessment completed and posted in the Supplier Performance Risk System (SPRS) in accordance with DFARS 252.204-7019.

· Meet all cybersecurity requirements stipulated in this solicitation, which may include a specific Cybersecurity Maturity Model Certification (CMMC) level and compliance specified in the resulting BOA or orders in accordance with DFARS Clause 252.204-7012 for the protection of Controlled Unclassified Information.

· Disclose any actual or potential Organizational Conflicts of Interest (OCIs) to the Contracting Officer.

· Be registered in the prescribed government invoicing system (e.g., Wide Area Workflow).

4.3 Government Rights and Disclaimers

· Marketplace Onboarding Decision: The Government reserves the right to make multiple awards, a single award, or no award as a result of this Call.

· Binding Authority: Only a warranted Contracting or Agreements Officer has the authority to enter, modify, or execute a binding instrument on behalf of the United States Government.

· Cancellation: The Government reserves the right to cancel this Call, either before or after the closing date. If the Call is canceled, the Government has no obligation to reimburse an offeror for any proposal preparation costs.

· Standard Terms: The terms and conditions of any resulting BOA will be based on FAR Part 12. Offerors are encouraged to review FAR 52.212-4 and 52.212-5. The offeror will be required to review and accept additional UAS Marketplace specific terms and conditions.

4.4 Submission Updates and Revisions. Offerors are responsible for maintaining a current, complete, and accurate submission package. Throughout the open period of this CSO, offerors may submit revised documentation to update their submission to correct inadvertent errors or address feedback from the Government. The formal acceptance of any updates into the official evaluation package, however, remains at the sole discretion of the Government. All evaluations will be based on the latest submission officially accepted by the Government at the time of review.

5. CALL FOR SOLUTION NOTES

In addition to the general guidelines included in the UAS Marketplace CSO, the following guidelines apply to this Call:

· The Offeror shall demonstrate an innovative, existing, verifiable commercial solution, and Offerors are responsible for monitoring SAM.gov for any amendments to this solicitation that may have updated information.

· The Solution Brief must identify any intellectual property involved and associated restrictions on the Government’s use of that intellectual property.

· The Government reserves the right to tailor the evaluation phases based on an offeror's prior engagement with DoW entities.

Important Notice for All Offerors:

This Call encompasses solutions that inform the Army’s LE Launcher Approach. While the overall submission and evaluation process follows the same framework for all systems, offerors must be aware that specific requirements and procedures may vary between these categories.

It is the offeror's responsibility to read all sections carefully and ensure their submission fully complies with the specific requirements applicable to their proposed solution.

6. SOLUTION SUBMISSION REQUIREMENTS

6.1 Overview of Submission Steps: Submission of White Paper and Request for Demonstration The Government will utilize a three step process to evaluate submissions. Offerors who successfully show their technical path via white paper will be eligible for Step 2/3, Invitation to Demonstrate in Lab and Test Range.

Crucially, the establishment of a BOA does not constitute a purchase or a guarantee of future orders. The BOA serves only as the contractual framework that makes the UAS available for purchase. If a Government user determines that a specific UAS meets their unique operational needs, they may initiate an order against the established BOA via the UAS Marketplace. The Government makes no commitment to the volume or frequency of orders.

6.2 Step 1 - Technical White Paper

As the foundational step, interested Offerors must submit a Technical White Paper (TWP). The TWP is no longer than a five page paper to include a title page with Company Name, CAGE Code, DUNS number, Company Address, Place of Performance Address; Point of Contact with name, title, phone, and email address, or a ten slide PowerPoint file including a title slide as described above. Technical Papers shall address one, some, or all of the topics below:

· Describe the unique technical aspects of your solution/concept and how it adapts to and integrates on the USG’s LEDGR and/or path to adapting. Interface Control Documents for LEDGR are available from the USG via Email:UASLaunchAndControl@army.mil

· Describe the unique technical aspects of your industry solution/concept for a common carry and launch tube/system that can accommodate multiple LE vendors.

· Describe the unique technical aspects of your solution/concept and how it adapts to and integrates onto the USG’s MEL and/or path to adapting. Interface Control Documents for MEL are available from the USG via Email: UASLaunchAndControl@army.mil

· Describe how the solution/concept utilizes a MOSA for software architecture and Arm/Fire integration pathway with a USG fire control application.

6.3 Step 2 & 3 – Invitation to Demonstrate in Lab and Test Range Upon completion of assessments, the USG may invite vendors to demonstrate. Vendors would first provide a demonstration of their solution on a USG provided LEDGR or MEL in a Government provided lab. Step 3 would entail a LE Rodeo, to be coordinated by the Aviation & Missile Center (AvMC) LEDGR Team in FY27.

7. EVALUATION CRITERIA

7.1 Step 1 – Technical White Paper (TWP)

7.1.1 Technical White Paper Evaluation

· Evaluation Focus: The Government will evaluate the Offerors’ TWP to assess the proposed solution's alignment with the Government's needs, technical feasibility, and innovation, based on its described Technical Merit.

· Evaluation Ratings: Technical submissions show a path to MEL/LEDGR/BMS integration, or Offers insightful information regarding a MOSA for software architecture and Arm/Fire integration pathway with a USG fire control application

· Outcome: Offerors may be invited to demonstrate in a USG lab (see Steps 2 & 3). Debriefs are not available due to this Call being for information purposes only.

7.1.2 Step 2 & 3 Lab / Flight Demonstration Evaluation

· Evaluation Focus: The demonstration will be evaluated on a pass/fail basis against the key performance parameters and mission scenarios defined by the Government. The purpose is to verify the technical capabilities claimed. This will be a USG-owned lab/range, contractor-operated event. To facilitate this, the Government will provide a Demonstration Coordination Packet to Offerors, if selected. This packet will provide comprehensive guidance for the event and will include the following components:

· Test Range and Airspace Information: Details on the designated test range location, logistical and site access instructions, and the process for coordinating airspace. This will also include range-specific safety protocols and any operational constraints.

· Flight Cards: A detailed plan, developed by the vendor, outlining the specific maneuvers, payload demonstrations, C2 link checks, and safety procedures required to verify the system's capabilities during the live flight event.

· Vendor Attendance: To ensure a safe and efficient demonstration, attendance will be limited to essential personnel. The Government will coordinate with the offeror to finalize the number of attendees prior to the event.

· Flight Demonstration Readiness Review: One week prior to the scheduled demonstration, the Government will conduct a readiness review with the Offeror using a standardized template. This mandatory review will serve as a final check to ensure all logistical, technical, and safety requirements have been met before the vendor and government teams deploy for the event.

· Evaluation Ratings:

· Successful: The system successfully demonstrated the required technical capabilities and performance.

· Unsuccessful: The system failed to demonstrate the required technical capabilities and performance.

8. GENERAL INFORMATION AND QUESTIONS

Questions are to be sent only to the Procurement Contracting Officer and Contract Specialist. The following shall be utilized in the email subject line: Call for Solution – W58RGZ-26-S-C001-0005 (reference the section area). Material questions and answers will be published on www.sam.gov.

9. CONTACT INFORMATION

Procurement Contracting Officer:

Angela L. Andrews Angela.L.Andrews5.civ@army.mil usarmy.redstone.acc.mbx.acc-rsa-uas-marketplace@army.mil

Contract Specialist:

Melissa Gaddis melissa.d.gaddis.civ@army.mil usarmy.redstone.acc.mbx.acc-rsa-uas-marketplace@army.mil

ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

The Offeror shall perform an OCI analysis and submit the results of that analysis in addition to the IAP submission. Specifically, the Offeror shall analyze the details of the Call and the implementation of their proposed Solution for actual or potential OCI situations associated with the performance of the Offeror, or any of the Offeror’s proposed teammates or subcontractors, under any contract or agreement the Offeror or the Offeror’s teammates or subcontractors have been or may be awarded by any federal agency or other entity. The Offeror shall describe in detail the methodology used to identify actual or potential OCI issues. The level of detail for OCI analysis may not be the same for all vendors. FAR 9.5 may be used as guidance for OCI analysis. If no conflicts are identified, a risk mitigation plan is not required; however, a description of the analysis methodology, and an affirming statement that no conflicts are identified shall be included.

If the Offeror identifies any actual or potential OCIs with respect to the performance of the Offeror or the Offeror’s subcontractors or teammates, the contractor shall provide an OCI Mitigation Plan to be incorporated as an attachment to any resulting contract or agreement. Any proposed avoidance or mitigation techniques shall be consistent with FAR 9.5 and the most recent decisions of the Government Accountability Office (GAO) and the U.S. Court of Federal Claims.

10. NON-GOVERNMENT ADVISORS

Offerors are advised that non-Government personnel may be used to assist in the evaluations for this Call. Non-Government advisors will be bound by appropriate non-disclosure agreements (NDAs) with the Government to protect proprietary and competition-sensitive information. By submitting a response to this CSO, the offeror acknowledges this process and waives any and all claims against the Government for any disclosures of proprietary information by non-Government personnel. If an offeror executes a direct NDA with the non-Government advisors, a copy of the signed agreement must be included with their submission.

11. ATTACHMENTS

Attachment 1. Statement of Objectives (SOO) image1.jpeg image2.png