DISR CSO AOI QA May142025.xlsx

XLSX spreadsheet 22 KB Posted May 14, 2025

Attached to: PEO SDA CSO PM Intel Digital ISR Area of Interest
Solicitation number: H9241525X0002
Issued by: United States Special Operations Command

About this file

Written by GovTribe AI · May 14, 2025

This file is a Questions and Answers (Q&A) document for the United States Special Operations Command's (USSOCOM) Commercial Solutions Opening (CSO) Digital Intelligence, Surveillance and Reconnaissance (D-ISR) Area of Interest (AOI) solicitation. The opportunity seeks innovative commercial software development solutions focused on integrating commercially and publicly available information with classified intelligence data across multiple network domains. Key details include a white paper submission deadline of June 6, 2025 at 5:00 PM EST, with a potential follow-on production award valued up to $100 million.

The Q&A document clarifies technical expectations, including leveraging existing government DevSecOps infrastructure (Platform One, DAFCloudworx, AAP, and Clairvoyant) across NIPR, SIPR, and JWICS networks. The solicitation emphasizes modern software development methodologies such as agile development, DevSecOps pipelines, containerization, and AI/ML integration. Performers are expected to utilize existing government-provided infrastructure and focus on delivering software development capabilities, with a 60-day ramp-up period and an anticipated prototype demonstration schedule of 8 weeks. The government will not meet individually with potential vendors and requires all inquiries to be submitted in writing.

View the file

Other files

File	Type	Posted
DISR CSO AOI QA Final 29 May.xlsx	XLSX spreadsheet	May 29, 2025
DISR CSO AOI QA 19 May.xlsx	XLSX spreadsheet	May 19, 2025
DISR CSO AOI 19 May 2025 - Final.docx	DOCX document	May 19, 2025
DISR CSO AOI 06 May 2025 - Final.docx	DOCX document	May 7, 2025
Attachment 01 Go_ No-Go Matrix 6 May 25.rtf	RTF text file	May 7, 2025

On GovTribe

Work with this file

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Sheet1

		Industry Question	USG Response
		While reviewing the SAM.GOV posting for the subject AoI, I noted a discrepancy between the two documents posted with the opportunity. Specifically, the "DISR+CSO+AOI+06+May+2025+-+Final" indicates the following in the Purpose section: "This Other Transaction Authority (OTA) Agreement is focused on new, novel, or disruptive commercial solutions with architectures and technical attributes that can be demonstrated during an estimated 3 to 5-month period with the intent of a follow-on production award through an agile methodology via the DoD Software Acquisition Pathway (DODI 5000.87)." While the "Go No-Go" document indicates: "Submission of a white paper that demonstrates how the offeror plans to meet an 8-weeks prototype demonstration schedule in accordance with AOI Technical Attributes." Can you please clarify the relationship of the 3 to 5-months stipulated in one document with the 8-weeks listed in the other?	The two documents are referring to different processes, but I see how it can be confusing. The 3-5 month period is meant to reflect the entire process prior to production OTA award including white paper, white paper evals, prototype solicitation and award, and prototype performance. 8 weeks is the intended PoP of the prototype project itself once awarded.
		I am writing to seek clarification regarding the requirements outlined in the CSO for the Digital - Intelligence Surveillance and Reconnaissance (D-ISR) capability. The solicitation emphasizes the importance of leveraging modern software development methodologies, including DevSecOps pipelines, agile development, and human-centered design processes, to accelerate the delivery of integrated solutions. Additionally, the technical attributes highlight the need for containerized applications, data engineering services, and integration of artificial intelligence capabilities. Given the focus on these elements, I would like to confirm whether the Government is seeking a cloud-based software development environment as part of the proposed solution or if the emphasis is solely on the execution of software development activities within existing Government-provided infrastructure. Specifically: 1)	Should the proposal include the design, development, and deployment of a cloud-based environment to support software development activities, such as DevSecOps pipelines, containerization, and AI/ML integration? 2)	Or is the expectation that the performer will utilize existing Government-provided infrastructure and focus exclusively on delivering software development capabilities and services? We are an awardee on two CSOs delivering similar cloud-based capabilities for DevSecOps pipelines so understanding this distinction will help ensure our proposal aligns with the Government’s intent and addresses the requirements effectively.	The expectation is that the performer will leverage existing Government-provided infrastructure and focus exclusively on delivering software development capabilities and services.
		We’re currently evaluating a potential submission and wanted to respectfully request a brief clarification regarding the stated existing DevSecOps infrastructure and pipelines currently supporting the D-ISR program. Specifically, we are interested in understanding:
•	The platforms and tools currently in place for DevSecOps (e.g., CI/CD toolchains, container orchestration platforms, code repositories).
•	The deployment environments required (e.g., cloud, on-prem, and on-platform at the edge).
•	The flexibility available in integrating or adopting alternative secure DevSecOps platforms that are well established in DoD.
This context would help us tailor our proposed capability in a way that ensures the greatest alignment and compatibility with the current mission environment.	The government has established DevSecOps platforms on NIPR, SIPR, and JWICS the performer will use. These have been in use for several years and the government is not looking to migrate to a new solution, but may consider it if the platform is more performant and/or more cost effective. The existing platforms being used are Platform One, DAFCloudworx, AAP, and Clairvoyant. Development is a mixture of cloud based and local development. Staging environments are cloud based and mimic the production environment.
		In reviewing the PEO SDA CSO PM Intel Digital ISR Area of Interest opportunity on SAM, there is a discrepancy between the due date/time of the Phase I white paper submissions. In the cover description on SAM, the due date is listed as Friday, June 6th at 5pm EST.

However, in the first attachment (DISR CSO AOI 06 May 2025-Final) at the bottom of Page 3 under the Event Timeline section the 6-page Phase I whitepaper submission is listed as being due 12 noon EST Friday, June 6th.

Can you please provide confirmation of the correct time the Phase I whitepaper is due on Friday, June 6th?	White paper submissions are due June 6th 2025 at 1700.
		Our team has experience delivering AI/ML-enabled solutions through agile software development pipelines, and we are very interested in learning more about SDA’s goals for this effort.

While we haven’t had the chance to connect before, we would appreciate the opportunity to introduce our technical team and discuss how our experience might align with your mission needs. If you have availability this week, we’d be glad to set up a brief call at your convenience.	Unfortunately, the Government is unable to take individual meetings with regard to the Area of Interest posting. This would be an unfair advantage to other interested parties. If interested in this opportunity, please submit a white paper per the instructions.
		We are evaluating our position with regard to submitting a White Paper for the D-ISR Technical Area of Interest and have a few questions:

1.	When do you anticipate requiring resumes for the "integrated support" and "Requirement Capture and Development" requirement?
2.	Our AI processor is hardware agnostic, Edge compatible and works with legacy systems. It will work with a GPU but it is not necessary. Do you require the use of a GPU?
3.	What timeline is required to "Ramp Up" our capability following award in order to comply with the 20 plus projects per quarter?	1. The Government may request resumes during the production phase but at this time not a requirement. 2. The government team has access to GPU but would entertain a solution that is not GPU dependent. 3. 60 days.
		Quick question about this area of interest. Is the program team open to meeting with industry during the solicitation period? If not, should questions be submitted in writing to the Contracting Officer and Program team? If those instructions are in there and I missed it, my apologies.

We are hoping to gain clarification on a specific requirement in the technical attributes section that appears overly restrictive. Based on our experience deploying on government-provided infrastructure, we are aware of alternative approaches that also meet operational and security needs. We’d appreciate the opportunity to better understand the intent of this requirement as we evaluate the opportunity and determine our next steps.	Please submit your questions to Josh, Nicole and myself cced. At this time, we are not meeting with industry.
		We respectfully request clarification on how the response should be submitted, i.e. email, uploaded into SAM.gov, etc. Can you please provide guidance on how the white paper should be submitted?	White papers may be emailed to Josh Cales and Christie Orlando at Joshua.v.cales.ctr@socom.mil and Christie.r.orlando.civ@socom.mil

File details come from the government source that posted it. Updated Oct 14, 2025.