TCS-PSS CSO_10192026_final.pdf

CUI

Pa ge

Call for Solutions for Tactical Communication Systems Procurement, Services & Sustainment Enterprise Acquisition

Solution for Next Generation Command and Control Transport Layer Soldier-Borne and Special Purpose and Ground Maneuver Communication Capabilities

Reference Number CSO-ARMY-TCS-PSS-2027

19 October 2026

PREPARED BY:

Capability Program Executive Command and Control Information Network Project Manager Command and Control Transport

Product Manager Tactical Communication Systems

This document contains proprietary or source selection information related to the conduct of a Federal Agency procurement. The disclosure and receipt of this information is restricted by the Office of Federal Procurement Policy (41 U.S.C. Div. B of subtitle I). The unauthorized disclosure of this information may subject both the discloser and the recipient to the contractual, civil, and/or criminal penalties as provided by law.

Controlled by Project Manager Command and Control Transport CUI Categories: BUDG, CTI, EXPT, SSEL, PROCURE, PROPIN Limited Dissemination Control: FEDCON POC: Katie Smith, (520) 691-3434, kathleen.m.smith230.civ@army.mil

Pa ge

CALL FOR SOLUTIONS

Tactical Communication Systems Procurement, Services & Sustainment Enterprise Acquisition Solution for Next Generation Command and Control Transport Layer Soldier-Borne and Special Purpose and Ground Maneuver Communication Capabilities

Project Number TCS Enterprise CSO-ARMY-TCS-PSS-2027 Army Open Solicitation (AOS) Number W9128Z-25-S-A002 Call for Solution Title Tactical Communication Systems Procurement, Services &

Sustainment (TCS-PSS) Issued By Army Contracting Command – Aberdeen Proving Ground

(ACC-APG)

Solution Submission Requirements To respond to this Call for Solutions, please refer to Section 6

*White Papers Due Date/Time (Suspense)

19 November 2026 at 1700 Eastern Standard Time (EST)

Point of Contracts (POCs) for White Paper Submission

Contracting/Agreements Officer: Jennifer Anderson, jennifer.d.anderson57.civ@army.mil, Specialist: Aaliyah Coles, aaliyah.m.coles.civ@army.mil

NOTE: Please advise the cognizant Contracting/Agreements Officer and Specialist as soon as possible via the emails above if your organization intends to submit a White Paper in response to this Call for Solution.

*Any submissions that are received by the Contracting/Agreements Officer after the suspense date/time listed above will be deemed late and not evaluated. It is the sole responsibility of the company to ensure that its submission is received in the email inboxes listed above before the deadline specified.

This Call for Solution may result in the Government awarding Federal Acquisition Regulation (FAR) contracts or non-FAR agreements In Accordance With (IAW) Defense Federal Acquisition Regulation Supplement (DFARS) 212.70 – Defense Commercial Solutions Opening. Other Transaction (OT) that may be awarded from this Call for Solution are not subject to the FAR or its supplements, as applicable. Use of a CSO in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) subpart

212.70 is considered to be a competitive procedure for the purposes of 10 U.S.C.

chapter 221 and FAR subpart 6.102.

mailto:jennifer.d.anderson57.civ@army.mil mailto:aaliyah.m.coles.civ@army.mil

Pa ge

1. BACKGROUND.

The Department of the Army, on behalf of the Capability Program Executive Command and Control Information Network (CPE C2IN), Project Manager Command & Control Transport (PM C2T), and Product Manager Tactical Communication Systems (TCS), is issuing this Call for Solutions (CFS) under the authority of DFARS 212.70 to acquire innovative commercial items and services that enhance Army tactical communication capabilities.

This CFS supports the Army’s objective to rapidly identify, evaluate, and competitively select industry partners capable of delivering a TCS Enterprise supply and services solution that enables expedited procurement and delivery of transport hardware and related communication capabilities. These capabilities directly support Next Generation Command and Control (NGC2), including testing, fielding, operational integration and sustainment. The enterprise solution may also support legacy hardware and software sustainment, logistics services, and the procurement, management, and integration of commercial software licenses required for Army tactical communication systems.

This CFS expands the Army’s engagement with innovative commercial vendors including traditional and non‑traditional defense contractors by enabling streamlined acquisition pathways aligned with Army modernization priorities. The commercial solutions approach provides an enterprise framework for continued production, engineering, and sustainment of current single and multi‑channel radios, while allowing for competitive onboarding of new and emerging technologies through recurring updates to the Army CSO.

The notional TCS enterprise solution is envisioned as a set of multiple single-award Indefinite Delivery Indefinite Quantity (SA IDIQ) contracts, flexible enough to be awarded under FAR Parts 12, 13, 15, and 16.

The ordering period is expected to be ten years. Additionally, the Army may also elect to award multiple single-award Other Transactions. This structure provides flexibility to procure solutions based on operational mission needs while offering competition and innovation across the vendor base. This CFS is issued under the AOS Number W9128Z‑25‑S‑A002.

2. PROBLEM STATEMENT.

Current mission requirements demand secure, interoperable, and resilient transport hardware solutions that can support National Security Agency (NSA) High Assurance certification requirements or Sensitive But Unclassified–Encrypted (SBU-E) communications across the Army’s tactical formations. The NGC2 architecture must field these transport capabilities to ensure connectivity, data protection, and mission command resilience in contested and coalition environments.

The Army seeks innovative commercial solutions to modernize, field, sustain, and evolve tactical communication systems that support secure, resilient, and interoperable mission command across all echelons. The Army requires the ability to procure hardware, software, services, training, licenses, sustainment, and lifecycle support to ensure continuous operational readiness and rapid technology refresh in contested environments.

Army formations require modern tactical communication systems capable of secure voice, data, and networking functions across joint, coalition, and interagency partners. These systems must remain

Pa ge interoperable, cyber‑secure, exportable when authorized, and adaptable to evolving mission requirements.

The Scope of capabilities include but are not limited to the following:

1. Procurement of end-item hardware, ancillaries and parts down to the card level.

2. Software upgradeable systems to extend their useful life without the need for hardware upgrades.

3. Software applications and waveforms with licensing models that allow the Army to purchase, manage, and load software onto government‑owned equipment.

4. High‑assurance product coordination with NSA for cryptographic, cybersecurity, and secure communications compliance.

5. Delivery of Risk Management Framework (RMF) documentation/artifacts to support Interim

Authority to Test (IATT) and Authority to Operate (ATO) efforts.

6. Hardware and software sustainment including field‑level, depot‑level, and post‑production software support.

7. Warranty management and repair of warrantied items.

8. Configuration management and obsolescence planning to ensure long‑term viability.

9. Technology refresh, substitution, and modification to maintain relevance against emerging threats.

10. Waveform porting to Army specified platforms.

11. Testing support including lab, field, interoperability, cybersecurity, and certification testing.

12. Engineering, logistics, management, and test data delivered as CDRLs to support lifecycle management.

13. Integration of software licenses onto Army owned systems, including GFE workflows.

14. Onsite and off‑site training for operators, maintainers, and system administrators, to include train the trainer.

15. Field Service Representative (FSR) support for deployment, troubleshooting, and operational readiness.

16. Depot transition planning for hardware and software sustainment.

17. Post‑production software support and long‑term sustainment activities.

18. Lifecycle sustainment documentation to enable organic depot capability.

19. Development and maintenance of Technical Manuals to support system operation and sustainment.

20. Provisioning Data management to support supply chain and logistics operations.

21. Supply chain risk management framework implementation to mitigate risks in the supply chain and ensure system integrity.

22. Flexible delivery schedules to meet fielding needs. The ability to surge production when required.

23. Bailed assets as required to support the evaluation of new technologies.

24. Commercial manuals and computer software documentation (as defined in DFARS 252.227-

7989(a) (DEVIATION 2026-O0036) shall be provided in accordance with DFARS 252.227- 7990(c)(1) (DEVIATION 2026-O0036). DFARS 252.227-7990 (DEVIATION 2026-O0036) shall be included in all subcontracts.

3. PRODUCT CHARACTERISTICS AND DESIRED SOLUTION ATTRIBUTES.

Note to Offerors: The following characteristics and attributes reflect the comprehensive enterprise target architecture. Offerors are not required to provide a single solution that satisfies all listed attributes. Offerors

Pa ge are explicitly encouraged to propose component, modular, subsystem, or niche solutions addressing a subset of these attributes where their commercial products or services provide capability.

Product Characteristics and Desired Attributes Include the Following:

1. Security & Encryption: NSA-certified or certifiable SBU-E encryption capability ensuring protection of unclassified but sensitive mission data.

2. Rapid zeroization function capable of purging all data, cryptographic keys, and sensitive configurations.

3. Hardware-rooted secure boot process.

4. Dismounted, mounted, and “fly-away” configurations capable of operation in any combat environments.

5. Single or multi-band capability built on commercially available Software Defined Radio architecture allowing rapid waveform integration.

6. Open architecture design that enables rapid scaling across echelons and seamless integration into the Army’s networks and frameworks.

7. IPv4.

8. Support mass scalability.

9. maintain reliable connectivity in contested environments using point-to-point, point-to-multi point, or self-forming mesh networking.

10. Natively interfaces with an approved government End User Device.

11. Support extended mission endurance to minimize power draw without impacting performance

(decrease power consumption and reduce heat).

12. The ability to prioritize voice or data traffic.

13. Small form factor or radio card for integration into unmanned systems.

14. Integration into existing mounts on ground and aviation platforms with vehicle mount installation kits (i.e. HMS or SINCGARS).

15. Application Programming Interfaces (API), including detailed interface control documents and standards, to interface with your proposed solution.

16. IPv6.

17. Tool (software and hardware) for planning the network and loading cryptographic keys.

18. Cryptographically sound TRANSEC measures, logically independent of COMSEC encryption, to secure transmission sequences and protect all transmission metadata (including but not limited to user IDs, GPS locations, and routing information) from adversarial collection.

19. Tactical Identity, Credential, and Access Management (ICAM), support Multi-Factor Authentication for privileged admin functions, and support cryptographic attestation of hardware/software integrity prior to network access.

20. Active Electronic Protection and automated interference mitigation to withstand Electronic Attack at Government-defined jammer-to-signal ratios.

21. Modes for Low Probability Intercept/Low Probability of Detection techniques, including variable power control, spectral masking, and Radio Frequency silence (Emissions Control).

Pa ge

22. Protect sensitive information implementing logically separate, FIPS-validated cryptographic mechanisms for Data-at-Rest software and Data-in-Transit (Communications Security).

23. Receive and validate cryptographically signed software packages prior to installation and deny software packages that fail validation or are unsigned.

24. Support secure, cryptographically signed, Over-the-Air updates for all software and firmware.

25. Generate automated locally stored audit logs, cryptographically hashed or digitally signed ensuring unauthorized alteration is immediately detectable, in an exportable industry-standard format (e.g.

test, CSV, JSON) via a physical, wired maintenance port.

26. Deliver 3ea initial production-representative devices for Government-conducted Radiated Emissions characterization and support of the Government risk assessment by remediating any critical anomalies found to establish an electromagnetic and compromising emissions baseline.

27. Integration with Army’s Small Tactical Universal Battery (STUB).

28. Operate within standard tactical vehicular and dismounted power budgets without requiring proprietary power sources.

29. Connect wirelessly to an End User Device and/or Headset on the soldier.

30. Access to a local wireless network (5G).

31. Critical high risk failure components are externally accessible.

32. Critical high risk failure components are replaceable without disassembly of the system.

33. Leverage additive manufacturing techniques for replacement of non-electric components.

34. Cryptographically authenticated, rapid zeroization function capable of purging all data, cryptographic keys, and sensitive configurations.

35. Hardware-rooted secure boot process that cryptographically validates the integrity and authenticity of all firmware before execution.

36. Natively interfaces with Radio over Internet Protocol.

37. Not single-point reliant on GPS for timing or synchronization to maintain secure operations in a

GPS-denied environment without degrading performance.

38. The system shall allow field‑level replacement of major components (LRUs) without specialized training, tools, or Test, Measurement, and Diagnostic Equipment (TMDE).

39. Commercial software license agreements shall not conflict with federal procurement law, fail to satisfy user needs or include unacceptable attributes such as indemnification or other types of provisions that include unauthorized or unbudgeted funding obligations, attorney's fees, state or foreign choice of law/jurisdiction provisions, binding arbitration provisions, and injunctive relief provisions.

4. AWARDING INSTRUMENT

The Call will be awarded in accordance with the AOS procedures detailed within Solicitation W9128Z-25-S- A002, found here: https://sam.gov/workspace/contract/opp/c30e51cdfa344f73ba7fd297d6e9acae/view This Call provides instructions to companies and how the Government will evaluate submissions.

https://sam.gov/workspace/contract/opp/c30e51cdfa344f73ba7fd297d6e9acae/view

Pa ge

5. CALL INSTRUCTIONS AND NOTES

Interested parties are invited to submit White Papers in response to this CSO. White Papers should be no more than 15 pages and must include the following:

1. Company Information: Company name, address, CAGE code, and point of contact information.

Identification as a traditional or non-traditional defense contractor.

2. Technical Concept: Description of the proposed solution and how it addresses the problem statement, required attributes and desired attributes. Maturity level of the technology (TRL/MRL).

Integration approach with the Army’s NGC2 architecture.

3. Commercial Viability: Description of current commercial applications and availability. Intellectual property ownership or licensing considerations.

4. Rough Order of Magnitude (ROM) Cost and Schedule: Estimated development, production, and sustainment costs. Proposed schedule for testing, certification, and production delivery.

5. The requirements identified in Section 3 are intended to describe the Government’s anticipated needs and may not be applicable to all potential solution providers. Respondents should address only those requirements that align with their capabilities, products, services, and business model.

Responses should clearly identify the specific requirements the company is capable of satisfying and describe the respondent’s relevant portfolio, offerings, technologies, and associated capabilities. The Government recognizes that vendors may provide solutions that address all or only a subset of the identified requirements and encourages respondents to highlight unique approaches or capabilities that may contribute to mission success.

6. All responses submitted under this Call for Solutions must be Unclassified. Proprietary/CUI:

Unclassified proprietary data and CUI are permitted but must be explicitly and properly marked per DoD regulations.

7. DFARS 252.227-7992 (DEVIATION 2026-O0036), Identification and Assertion of Use, Release, or Disclosure Restrictions. Government rights in commercial and non-commercial technical data and software deliverables shall be governed by DFARS 252.227-707989 (DEVIATION 2026-O0036), and DFARS 252.227-7990 (DEVIATION 2026-O0036) respectively. Pursuant to the requirements set forth in DFARS 252.227-7992(d) (DEVIATION 2026-O0036), Offerors are required to specifically identify Data/Software Rights Assertions related to technical data and software deliverables utilizing the format prescribed. As indicated in DFARS 252.227-7992(e) (DEVIATION 2026-O0036), an Offeror's failure to submit, complete, or sign the notification and identification required by paragraph (d) with its offer may render the offer ineligible for award.

5.1 Overview of Submission Phases

The response process for this Call will generally consist of the following phases:

Phase 1: Request for White Papers Offerors will submit a high-level summary of their proposed solution, addressing the government’s objectives and requirements.

Pa ge

Phase 2: Pitch (unless bypassed) Selected offerors may be invited to present and discuss their solution in a live or virtual setting.

Phase 3: Solution Proposal Offerors advancing to this phase will be invited to submit a detailed proposal for final evaluation and potential award.

Detailed submission requirements for Phase 1 are provided in Section 6. Evaluation criteria for Phase 1 are outlined in Section 7. Phase 2 and/or Phase 3 submission requirements and evaluation criteria will be provided via subsequent invitation letters.

5.2 General Notes

Offerors are reminded that all awards are subject to the availability of funds and the Government reserves the right to make multiple awards, a single award, or no award as a result of this Call.

Only a Contracting or Agreements Officer has the authority to enter into, modify, or execute a binding instrument on behalf of the United States Government. All payment obligations are subject to Congressional appropriations.

In order to be eligible for award, offerors must:

o Possess a Unique Entity ID (UEI) and be registered in the System for Award Management (SAM) prior to award, and maintain active registration throughout the period of performance.

o Register in the prescribed government invoicing system (e.g., Wide Area Work Flow).

o Accurately represent their small business size and status as required.

o Be determined responsible by the Contracting/Agreements Officer and not be suspended, debarred, or otherwise prohibited from receiving an award.

o Disclose any actual or potential Organizational Conflicts of Interest (OCIs) to the

Contracting/Agreements Officer prior to award.

Offerors are responsible for monitoring SAM.gov for any amendments or updates to this Call.

Notice to Offeror(s): The Government reserves the right to cancel this open Call, either before or after the closing date. If the Government cancels this open Call, the Government has no obligation to reimburse an offeror for any costs.

6. SOLUTION SUBMISSION REQUIREMENTS

White Papers shall be submitted electronically in PDF format to the Army Contracting Point of Contact listed in this announcement. White Paper submissions are due on 19 November 2026 at 1700 EST.

Interested parties are requested to submit all clarifying questions and feedback no later than 26 October 2026 at 16:00 EST utilizing the official TCS-PSS Question & Comment Microsoft Form, which can be accessed at https://forms.osi.apps.mil/r/4wAYi7G7tv. Please be advised that the Government will review submissions and provide responses on an intermittent basis as they are completed. This link also includes an Intent to Submit response. This registration is entirely optional and does not obligate your company to submit a final response; it is solely used to assist the Government in estimating evaluation timelines.

6.1 Phase 1 – Request for White Papers

https://forms.osi.apps.mil/r/4wAYi7G7tv

Pa ge

6.1.1 Phase 1 – White Paper Content

White Papers shall not exceed 15 written pages using 12-point Times New Roman font or, alternatively, may take the form of briefing slides not exceeding 15 slides. The Government will not consider inserted textboxes/pop-ups or internet links to additional information as part of the White Paper and will not consider such information in its evaluation. White Papers are intended to be clear and concise.

White Papers shall include the following at a minimum:

A. Title Page (does not count against page limit)

1. Company Name, Title, Date, Point of Contact Name, E-Mail Address, Phone, Address, and Call reference number. If registered in SAM.gov, include the Commercial and Government Entity (CAGE) code and Unique Entity Identification (UEI) code.

2. Specifically identify the Call for which the White Paper is submitted.

B. Executive Summary (one page)

1. Provide an executive summary of the technology.

C. High-Level Technology Solution/Concept

1. Offerors shall provide a comprehensive Portfolio Alignment Narrative describing how their company’s products, technologies, and services align with the product characteristics and desired attributes, identified in this Call for Solutions. The narrative must clearly demonstrate the breadth, maturity, and applicability of the Offeror’s portfolio to Army tactical communication system needs.

2. Provide a description of the Offeror’s full product portfolio relevant to tactical communication systems, including hardware, software, licenses, services, and sustainment capabilities.

3. Identification of products currently fielded, commercially available, in production, or under development.. For purposes of this CSO the Army currently utilizes the following definitions for TCS kits, however, respondents are encouraged to identify the most efficient definition based their unique commercial solution:

• A Mounted Kit is comprised of radio, power cable, all antenna assemblies for mounted operations of all waveforms installed on the radio, loudspeaker-microphone, cable for connection to vehicle intercom system, vehicle mountable GPS antenna, RF filters, triplexers, and other adapters to support the waveforms installed on the radio

• A Dismounted Kit is comprised of radio, GPS antenna, GPS cable, case, rechargeable battery, loudspeaker-microphone, earphone, and antennas for dismounted operations for all waveforms installed on the radio

4. For each product characteristics and desired solution attribute listed in the Call for Solutions, Offerors shall:

a) Identify the specific product(s) or service(s) that meet the requirement.

Pa

b) Describe how the product satisfies the technical, operational, or sustainment requirement.

c) Provide evidence of performance, certification, or compliance where applicable (e.g., NSA coordination for high‑assurance products).

d) Identify portfolio elements that meet or exceed desired attributes.

e) Explain how these capabilities enhance Army mission effectiveness, reduce lifecycle cost, or improve interoperability.

f) Describe any additional features, innovations, or differentiators not explicitly required but beneficial to Army tactical communications.

g) Describe capabilities such as waveform porting, technology refresh, obsolescence mitigation, software maintenance support, depot transition support, or advanced sustainment models.

5. Address applicable capabilities individually and describe how your solution achieves the relevant scope of requirements addressed by your offering.

6. Explain how the proposed technical approach is feasible, achievable, and supported by a technical team with the expertise and experience to accomplish the proposed solution/concept.

7. Provide the following: (All compliance documents and certifications listed below may be submitted as attachments and will not be applied toward the page limitation).

a) List the waveforms with which your solution is capable of cross-banding, if any.

b) Confirm compliance with MIL-STD-810H Change Notice 1 (May 2022) to include

Environmental and Physical Stress Testing.

c) Confirm compliance with MIL-STD-1472H dated 15 September 2020 criteria for prolonged handling and momentary contact.

d) Provide Key and Certificate Management Plan.

e) Provide Plan for achieving Post-quantum compliance with Commercial National Security

Algorithm Suite 2.0 by 1 January 2027.

f) Provide an overview of your supply chain risk management plan.

g) Provide battery hours to power proposed solution without conformal wearable battery.

h) For High Assurance solutions, describe your plan and timeline to achieve NSA certification for Security Evaluation Requirement Document (SERD) v2.0 compliance.

i) Describe your plan to support products once they have been procured (software updates, firmware updates, assess new vulnerabilities etc.).

8. Provide the most optimal production schedule and minimum quantity requirements to maintain

“hot” production line(s). Identify proposed project schedule and total estimated out-the-door price to include “cold-start” production unit pricing. In order to aid in the development of ROMs for production unit pricing respondents may assume notional annual delivery requirement of 5,000 radios. This is not a commitment or minimum guarantee under this CSO process. It is only to be considered for purposes of estimating and establishing production lead times.

D. Company Viability

1. Provide a brief overview of the company. Include a summary of current fundraising to date or a summary of top line (gross sales/revenues).

2. Provide a summary of product/solution commercialization and go-to-market strategy.

Pa

E. Intellectual Property Statement/Commercial Software License Agreements/Disclosures IAW DFARS 252.227-7992 (does not count against page limit)

1. As needed, include a separate disclosure for each company that would be a participant in the solution/concept.

2. The Government may be unable to evaluate the White Paper if a Company fails to provide the information requested above.

7. EVALUATION CRITERIA

7.1 Phase 1 – White Paper Basis of Evaluation

White Papers correctly submitted in response to the Call will be evaluated against the below criteria. The Government reserves the right to use external market research in the evaluation of a Company's viability.

The Government reserves the right to not respond to white papers incorrectly submitted under this call. The Government reserves the right to select all, some, or none of the white paper submissions submitted in response to this call.

The Government intends to evaluate the White Paper to determine which proposed solutions have the potential to best meet the Governments needs utilizing the evaluation criteria below.

White Papers submitted in response to this open solicitation will be evaluated using the following factors in descending order of importance are: (a) Technical Merit, (b) Schedule/ROM, and (c) Viability.

a. Technical Merit. The Government will evaluate the Company’s White Paper submission in accordance with Paragraph 6.1.1, Section C, 1 through 8. The Government will evaluate the Company’s Offeror’s proposed solution/concept relevance to the respective Call; innovation or a potential capability; solves a problem or provides potential innovative technological advancements;

capabilities and scalability of the solution; benefits of the solution/concept, and technical approach, as well as maturity path. Commercial software licenses must comply with federal procurement law and satisfy the Government’s needs. As indicated in DFARS 252.227-7992(e) (DEVIATION 2026- O0036), an Offeror's failure to submit, complete, or sign the notification and identification required by paragraph (d) with its offer may render the offer ineligible for award.

b. Schedule/ROM. The Government will review the Offeror White Paper submission in accordance with Section 6.1.1, C, 8. The Government will evaluate the Company proposed solution/concept project schedule and estimated out-the-door total cost.

c. Viability. The Government will evaluate the Company White Paper in accordance with Section 6.1.1, D, 1 and 2. The Government will evaluate the submitted company overview, and if applicable, summary of product/solution commercialization and market strategy.

7.2 Phase 1 - White Paper Selection Process.

Pa

Based on the evaluation, the White Paper will be categorized as Selected for Further Consideration or Not Selected for Further Consideration. The selection of one (1) or more submissions into the next Phase will be based on the criteria listed above and funding availability. White Papers considered not to have (1) sufficient merit or relevance to the topic, (2) a Government need, or (3) funds are not expected to be available, the submission may be declined without further review.

Step 1: Selection Decision

Based on the evaluation of the criteria outlined in Section 7.1, the Government will categorize each White Paper into one of the following two initial selection gates:

Selected for Further Consideration: The submitted White Paper has been determined to be of technical merit, represents an achievable schedule and viable maturity pathway. As such, the Government intends to invite the Company to participate in next phase should funding be available.

Not Selected for Further Consideration: The submitted White Paper does not represent either the necessary degree of technical merit, technical innovation, or relevance to agency priorities to warrant further proposal effort or consideration.

The Army anticipates Topics may routinely receive more White Papers than resources to award. All submissions will be fairly evaluated, however, only select White Papers will be invited to Phase 2 and/or Phase 3. The government reserves the right to limit the number of Companies invited to Phase 2 and/or Phase 3. As such, a Company’s solution may be evaluated to be of merit but not invited to Phase 2 and/or Phase 3. White Papers that are chosen for Phase 2 and/or Phase 3 will be notified in writing as soon as practicable. The Government reserves the right to bypass Phase 2 into Phase 3 to request a formal proposal should funding be available.

For all White Papers categorized as Selected for Further Consideration, the Government will assign the submission to one of the following three active disposition pathways based on program priorities, technical maturity, and funding availability. The categories for disposition will include Acceptable but not tested;

Acceptable for testing; and, Acceptable, funded.

• Acceptable but not tested products may be placed on the TCS Verified Products List (VPL) for future consideration and may be offered the opportunity to implement BOAs or SA IDIQs with the Army.

• Accepted for testing solutions will undergo laboratory and/or field based operational evaluation(s) and, based on shared testing requirements utilizing offerors bailed assets, funding decisions will be made.

• The most promising tested solutions will be placed on the VPL and may be selected for instant funding based on the proposal amount and availability of funding.

• Other promising tested solutions not selected for immediate funding may be offered an opportunity to implement a BOA or SA IDIQ with the Army.

7.3 Period of Validity

Pa

Two-Year Solution Validity Period All White Papers evaluated as acceptable under this Call for Solutions shall remain valid and active for a period of twenty-four (24) months from the date of the Government's initial selection notification. During this 2-year period, the Government may initiate a FAR contract award, non-FAR agreement, or Other Transaction (OT) based on these submissions without requiring a new Phase 1 White Paper submission.

8. NON-GOVERNMENT ADVISORS

In accordance with AOS, Section I the Government will use non-Government advisors from the following contractors with the contact information provided:

NOTICE: Prospective respondents are hereby notified that the Government will utilize Systems Engineering and Technical Assistance (SETA) support contractor services during the review of CSO responses. Non- Disclosure Agreements for SETA contractors have been established. In the event that CSO responses include proprietary information, respondents are also required to sign and provide a proprietary protection agreement in accordance with FAR 9.505-4(b) with the CSO response to allow support contractor access to the proprietary information.

The contractor company and points of contact for establishing the proprietary protection agreement are:

Defense Acquisition Support Services, LLC., 210 Research Blvd, Suite 210, Aberdeen, MD 21001, Daniel Sullivan, (757) 630-9561, daniel.sullivan4@dasservicesllc.com

SigmaTech, Inc., 631 Discovery Drive, Huntsville, AL 35806, Peter Eck, (256) 319-9238, peter.eck@sigmatech.com

As a reminder, by submitting information to the Government, the Company further understands that it had an opportunity to enter into an NDA directly with the Non-Government Advisor and therefore waives any and all claims against the Government for any disclosures of proprietary information by the non- Government personnel. Such NDAs are the responsibility of the Company, and the Government shall not be a party to them. Companies shall provide a copy of the signed NDAs to the Government with submissions.

9. ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

The Offeror shall perform an OCI analysis and submit the results of that analysis in addition to the White Paper 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;

mailto:daniel.sullivan4@dasservicesllc.com mailto:peter.eck@sigmatech.com

Pa however, a description of the analysis methodology, and an affirming statement that no conflicts are identified shall be included. This section will not count against submission page limits.

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. USE OF ARTIFICIAL INTELLIGENCE (AI) DURING PEER REVIEW

• The Government reserves the right to employ AI tools/platforms to assist in specified support tasks

(e.g., summarizing voluminous content, highlighting compliance with basic solicitation requirements, organizing proposal data for evaluator review, etc.);

AI is used as a tool to support decision-makers, but will not be used to make evaluative judgments or selections, or to replace the independent assessment of peer review personnel;

Peer Review and source selection personnel remain exclusively responsible for the accuracy, integrity, and final approval of all acquisition actions, to include final evaluations and selection decisions; and

Any AI platform or tool used by the Government adheres to requirements Department of War (DoW) cybersecurity frameworks at Impact Level 5 (IL5) or higher to safeguard contractor bid, proposal, and proprietary data and prohibits the use of contractor data for training external or commercial AI models.