DISR CSO AOI QA Final 29 May.xlsx

XLSX spreadsheet 33 KB Posted May 29, 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 29, 2025

This document is a comprehensive Q&A file for the United States Special Operations Command (USSOCOM) PEO SDA CSO PM Intel Digital ISR Area of Interest (AOI) solicitation. The opportunity seeks innovative commercial solutions to support Digital Intelligence, Surveillance and Reconnaissance (D-ISR) capabilities, focusing on agile software development solutions for intelligence mission software. Key requirements include developing software using React, Python, Flask/FastAPI/Streamlit frameworks, implementing DevSecOps pipelines, and integrating artificial intelligence capabilities across multiple network domains and classification levels.

The solicitation requires interested vendors to submit a 6-page white paper by June 6, 2025, at 5:00 PM EST, demonstrating their current solution against specified technical and software developer attributes. The AOI is structured as a Commercial Solutions Opening (CSO) with a potential follow-on production award valued up to $100 million through FAR-based contracts or Other Transaction (OT) Agreements. A key requirement is that at least one Non-Traditional Defense Contractor (NTDC) must be involved, with the expectation of executing approximately 20 projects per quarter across 15 locations. Selected vendors will undergo a phased evaluation process, including white paper submission and prototype demonstrations, with successful prototypes potentially leading to production contracts.

View the file

Other files

File	Type	Posted
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 QA May142025.xlsx	XLSX spreadsheet	May 14, 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
		As a COTS Program, I’m in a bit of weird spot sometimes, so when I saw “Non-Traditional Defense Contractor Requirement” verbiage in the RFI, I was curious if all respondents must meet the NTDC requirement against this RFI.

I also saw this was an AOI against the 2025 CSO, but this had some vague language about a possible OT or FAR based award down the road. So I was also wondering if this is a CSO or an OTA.

This action would be for an OT. It is nice to have the flexibility to award a FAR contract but that is not the intent for this action.

This is a new requirement supporting program management office Intel under PEO-SDA and J2. This is capability based to enhance the D-ISR requirement.

		In regard to
•	Paragraph 2a. Required Technical Attributes
o	sub-bullet #4 Software Development

why does it appear that React, Python, and Flask, Application Programming Interface (FastAPI), and Streamlit the only options allowed?

Will the government consider a submission that includes other containerized, modern, enterprise programming languages that meet DOD security standards, meet the functional needs of the platform or mission, and supports the interoperability requirements of SOCOM?

TLDR:

shouldn't mainstream enterprise programming languages that meet the DOD security standards be allowed? If the solution meets the functional or operations needs of the platform, and it supports any interoperability requirements SOCOM has, then isn't the goal of real modernization achieved for the SOCOM mission?

Additional context Great programming is about using the right language for the right job. An enterprise solution necessitates using a few languages. We use Python and understand why this would be one of the preferred languages; however, SOCOM should know that best-of-breed engineers are polyglots and optimize code utlized by workload. Other languages that are extremely common in the DoD/enterprise world include:

1.	Go (Golang)
2.	NodeJS
3.	Typescript
4.	...all of which are used in DoD/IC for TS/SCI applications today.

•	For ML-based solutions Python is the best choice because of the speed at which you can get the solution built.
•	For distributed systems, APIs, and micro servicesm then Go is the best choice. Go is built around those things, and while you won’t be able to slap together quick solutions as Python might let you for smaller-scale stuff, in the long run Go will stay consistently manageable while Python libraries might begin to trip over themselves and become increasingly hard to trace/maintain.

2.	As part of this area of interest, is SOCOM considering COTS purpose-built by a govtech for this type of mission?	1.	The government already has the security posture for these languages/frameworks and CtF’s/ATO’s in place. Getting new ATO’s is a time consuming and laborious process that is not conducive the rapid development and fielding required by SOCOM’s mission. The government is also not interested in refactoring dozens of existing applications into a new code base.
2.	Software developed under this OTA will be considered GOTS.
		1.	Will this new requirement be expected to develop completely new applications and software, or develop enhancements and tools against existing baseline software utilized by the TSOCS and the D-ISR program?

2. With respect to this being Software development work against the D-ISR program and requirements, what are the existing Software baseline/tools that are expected to be developed against on this program?

3. Will the government entertain software as part of the submission (ie existing ISR software utilized and deployed by SOCOM that the D-ISR program can develop against to enhance emerging ISR data and capability requirements?)

4. Will the DevSecOps team be developing against GOTS or COTS software? 1. Both

2. Existing tools are built with the following frameworks and technologies (not exhaustive but representative) – React, Streamlit, FastAPI, Flask, Ollama, Postgres, Elastic.

3. Yes, but the program has a substantial preference for GOTS software

4. GOTS

Based on the requirements for the white paper, along with the Go/No Go criteria, we believe the current page count may be insufficient to meet the government’s requirements and provide an easy-to-understand solution. For example, Go/No Go Criteria #3 (Software Component Assessment) requires a “comprehensive assessment” for 7 distinct functional requirements that on its own could take 6 pages to properly cover. Also, Go/No Go Criteria #4 (SBOM) requires a "detailed inventory of all software components," a list that could take up several pages by itself. We don’t question the need for this information, however, adequately complying with these and all the other requirements will take more than 6 pages.

We would recommend one of three COAs:

1. Remove the criteria to provide the detailed information for the Go/No-Go criteria until after the submission of an initial white paper and after down selection.

2. Exclude the information required for the Go/No-Go criteria from the page count, and have offerors develop their own method or template to cover it. This would be like a configuration management plan that would be expected from a company during the execution of the contract.

3. Increase the page limit to 25 pages.

In all cases, would the government consider allowing offerors to provide the SBOM in MS Excel Spreadsheet format?	We will exclude information necessary to meet the requirements of the go/no go matrix from the page count.
		For ease of readability and formatting, would the government please consider allowing graphics and tables to be presented in a smaller font such as 8pt ?	No
		Can we include the SBOM (including naming each OSS component) -but- only summarize the assessments as a collective set? This would allow us to meet the page count requirement.	We will exclude information necessary to meet the requirements of the go/no go matrix (ie the SBOM) from the page count.
		The notice appears to describe two distinct capabilities:
1.	A DevSecOps pipeline for multi-enclave software delivery.
2.	An AI-enabled platform for fusing CAI, PAI, and classified data.

Is USSOCOM seeking:

•	A single solution that does both, or
•	Is it acceptable to propose a solution focused on just one?	SOCOM already has a DevSecOps pipeline, we need the capability to build on top of the existing architecture.
		Are software vendors with an established commercial off-the-shelf (COTS) solution able to respond, or is this contract opportunity only intended to fund the development of prototypes?	Any vendors can submit white papers to this Area of Interest to fulfill the capability requirement. There are more requirements to this announcement than just software purchases.
		Would you be open to a brief 15-minute call to determine whether it makes sense for us to submit a response focused solely on those areas? Our solution can provide real impact to USSOCOM, but I want to ensure we're aligned before proceeding.	Unfortunately, we are not able to take calls regarding this effort. Please forward any questions you have in an email.
		1.	Could you identify any existing GOTS and/or COTS applications within the current architecture that the software development team is expected to integrate with or enhance?
2.	What specific ISR data types are anticipated to be supported or processed by the development team? For example, will the system need to handle Satellite Imagery, Full Motion Video (FMV), GMTI, SAR, SIGINT, ELINT, OPIR, MOVINT, OSINT, or others?	There are 50+ GOTS applications within the current architecture developed with Python, React, and Streamlet. All ISR data types are supported other than Satellite Imagery and FMV.
		Is ROM pricing expected for the phase I white paper?	No a ROM is not required at the white paper stage.
		Are there any restrictions on teaming for the CSO response? i.e. Being on multiple teams responding separately to the RFP?	There are no restrictions on Teamings. If you are a foreign owned business, please review the FY25 SDA CSO on sam.gov

“Foreign-Owned businesses may be a submitter alone or through some form of teaming arrangement with one or more United States-owned businesses. However, the ability to obtain an agreement based upon a submission may depend upon the ability of the Foreign Owned business to obtain necessary export clearances and approvals to obtain AOI information.”

		The listing states an expectation of completing 20 projects each quarter. Could you please give any additional information on the typical size, complexity, and estimated level of effort (LOE) for an individual project within that volume?	Typical project will include frontend/backend requirements capture, design, software development, data pipelining, database creation, deployment, and maintenance. Not all projects will include each of these areas and some projects will include the use of Artificial Intelligence which will require model development/selection/deployment on government architecture.
		We are interested in how many awards that the US SPECIAL OPERATIONS COMMAND (USSOCOM) plans on awarding.	I do not have an exact number of prototypes we will be awarding after white paper submissions.
		Will the Government please confirm which environment D-ISR will be deployed on? Cloud, On-prem, hybrid?	Hybrid
		Are there pre-approved or provided AI/ML model frameworks or will vendors select and accredit models?	Vendor will need to build/select and accredit model if models for the specific task do ot already exist on government systems.
		Does the J2 use C2S?	Yes
		"D-ISR depends on core services that will be developed and maintained under this AOI." Can the government clarify A) if the core services already exist or are intended to be built as part of this initiative and B) what those core services are?	These services already exist and include but are not limited to data pipeline, cross domain solutions, data services, software applications, virtual machines, data bases, etc.
		I have noticed a conflict in the due times for the RFI Response due on May 19th. The due date is listed as June 6th, 2025 at 17:00 in the QA document, but on SAM.gov, the time has been changed to 12:00 on the same date. Could you please confirm which time is correct?	Responses are due at 1700 ET on June 6th. We have updated the SAM posting accordingly.
		It is stated in the file DISR+CSO+AOI+06+May+2025+-+Final that, “Number the pages consecutively and use a 12-point font size in an easily readable font, such as Times New Roman or Arial.”
Will you consider a font smaller than 12 point for tables and figures?	No, 12 point font must be used throughout for legibility reasons.
		In para 2.b.1., the RFI document mentions "the ability to execute a minimum of 20 projects per quarter." This is listed as one of six "Desired Software Developer Attributes." The word “projects” also is used elsewhere in the context of management and prototypes. Can the Government clarify what defines one project under Para 2.b.1., and how that fits into the context of "20 projects per quarter"? For example, is this referring to the number of projects the Government would expect a Contractor to execute per quarter, or does it mean the number of projects multiple contractors may potentially fulfill across the enterprise each quarter?	20 Projects per quarter refers to the number multiple contractors may fulfill in a quarter.
		Please let me know how to submit the White Paper response for 'PEO SDA CSO PM Intel Digital ISR Area of Interest'. Do we email it to all of you or is there a portal to upload it? If there is a portal, kindly provide the link	Please email to the listed POCs in the AOI.
		Are we able to submit as a joint venture to meet requirements as a "Non-Traditional Defense Contractor"?	Yes, you may propose as a joint venture to meet the requirements of an NTDC.
		For clarification regarding what the government is requesting - Are we to describe what capabilities we currently have or are we demonstrating our ability to create prototypes for implementation into legacy systems?	Offerors should be proposing their solution to meet the requirements of the technical attributes and desired software developer attributes outlined in the AOI.
		Is this effort interested in offerors that propose to integrate a single existing COTS product (like Seerist) to support PM-Intel’s mission?

Or is this effort broader in scope and interested in vendors who deliver software development capabilities and services to work on a variety of projects that both adapt existing GOTS tools and develop novel solutions based on Government priorities?	No, the government is looking for the capability to develop and deploy GOTS solutions for D-ISR.
		In review of the Digital ISR solicitation must we propose to each Technical attribute or can we propose to one, two, three? We assume the Government requires wants us to hit each attribute but wanted to confirm.	yes, please address all in your white paper
		Does the Government expect a use case along with technical supporting attributes or will the use case come if selected for the prototype?	If selected for Prototype
		Go/No-Go Matrix. The Government has a requirment for industry to lay out a plan to meet the 8 week prototype demonstration plan. However, no details or use case is provided to industry to determine the level of effort. Does the Government require a milestone list for these 8 weeks of development? Would the Government consider the 8 week plan not to be included in the 6 page requirment?	No a plan of how you would attack a problem statement in general is required.
		Regarding Data Sources and Integration, can the Government provide additional details on the specific data formats, APIs, and classification levels of the existing intelligence systems that D-ISR must integrate with? Understanding the current technical landscape will help us propose the most effective integration approach.	D-ISR requires the use of APIs from a broad spectrum of partners across multiple classification level to include commercial sources. D-ISR is exectued at all classficiation levels and on multiple networks.
		For AI/ML Infrastructure Requirements, the AOI mentions that "the government will provide Graphics Processing Unit (GPU) access for AI/ML capabilities." Can you clarify the GPU specifications, availability, and any restrictions on AI/ML frameworks or libraries that must be used in the government-provided environment?	AI/ML Frameworks are authorized on a case by case basis through appropriate security channels. The government is not willing to provided technical details about infrastructure it is using to execute sensitve missions via this means of communication.
		React/Python Framework Flexibility - while the AOI specifies React (frontend) and Python with Flask/FastAPI/Streamlit (backend), would the Government consider equivalent modern frameworks that provide superior performance or security capabilities, or are these technology stacks mandatory?	These technology stacks are already approed and include many applications. The government is not willing to refactor all of the existing applications to fit into a new tech stack but would be willing to consider new frameworks going forward if there is a demonstrated value, can be cleared through security pipelines/framworks, and does not require extensive refactoring of existing capabilities.
		Specific to Cross-Domain Solution Requirements, can the Government provide more specifics about the cross-domain solutions currently in use across the 15 locations? What are the data transfer protocols, security requirements, and bandwidth limitations that D-ISR must accommodate?	These are technical details not appropriate for this means of communication due to sensitive nature of the missions this supports.
		As a COTS Program, I’m in a bit of weird spot sometimes, so when I saw “Non-Traditional Defense Contractor Requirement” verbiage in the RFI, I was curious if all respondents must meet the NTDC requirement against this RFI.

I also saw this was an AOI against the 2025 CSO, but this had some vague language about a possible OT or FAR based award down the road. So I was also wondering if this is a CSO or an OTA.

I had spoken to a few folks at SOF Week when this dropped last week, but trying to understand if this is against a current program as it does mention its aim is to “enhance the velocity of the program”. Is that Program the D-ISR Program of record, and is the request essentially asking for software and capabilities AND engineering services against those capabilities to enhance the D-ISR program? All Respondents must meet NTDC requirements as a prime offeror. NTDC is defined as "Is not currently performing and has not performed, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards (CAS) prescribed pursuant to section 1502 of title 41, United States Code, for at least the one-year period preceding the solicitation of sources by the Department of Defense." As a COTS program, I would assume you are not performing any work subject to full cas coverage.

This is a CSO. The CSO responses (white papers) will be evaluated and used to select prototype OTA awardees. Once prototype projects are completed they will be evaluated and may lead to a follow on production OTA or FAR based contract.

Yes this is the D-ISR program of record. The request is for the development of software/capabilties and engineering services to support D-ISR.

Can you provide more information about the "government provided infrastructure" mentioned in the AOI? Specifically:

Cloud provider(s) and regions Container orchestration platforms (Kubernetes, OpenShift, etc.)

Network security requirements and constraints

Available development and staging environments	The government is using infrastruture accros several environments including cloud and on prem solutions. These include development, staging, and production environments.
		The AOI mentions 15 locations supporting TSOCs and Components. Can the Government clarify:

Which locations require on-site support vs. remote support?

Are there specific security or connectivity requirements that vary by location?

What are the expected travel requirements for on-site support?	All locations will require on-site support, there will be no remote support due to the classified nature of the work. While there may be some minor differences, the entire team will leverage the same infrastructure so difference will be minor if they exist at all.
		Can the Government provide guidance on the preferred deployment approach? Should capabilities be rolled out incrementally across locations, or is a simultaneous deployment across all 15 locations preferred?	Government does not have a preference as it will depend on the capability. Some capabilities are applicable to all locations, some are only applicable to specific location/elements. Governmetn does prioritize the rapid deployment of a MVP as quickly as possible and then iterating from there.
		The AOI states that D-ISR requires "a minimum of 20 projects per quarter ranging from medium to high complexity." Can the Government provide:

Examples of recent medium and high complexity projects?

Typical project duration and resource requirements?

Expected mix of new development vs. enhancement/maintenance work?	This will vary significantly as all development efforts do. D-ISR takes requirements from the field as they come in, prioritizes them for development and executes that development. The duration of a project varies but on average projects are completed in 30-60 days.
		Among the core services mentioned (data services/APIs, AI services, data pipelines, cross domain solutions, development infrastructure, platform security, consolidated software development), which are the highest priority for initial implementation?	These services work together and are all esstenial for successful implementation. There is not one that is more important than another.
		What legacy intelligence systems must D-ISR integrate with, and are there specific modernization requirements or constraints for these integrations?	D-ISR has several applications currently deployed. Those will need to me maintaned. Additionally, D-ISR is leveraging existing development/deployment platforms with both service and IC partners.
		Beyond the Non-Traditional Defense Contractor requirement, are there specific small business participation goals or requirements for this OTA? Would a prime small business contractor with large business subcontractors be viewed favorably?	Offerors simply need to be NTDCs to receive a prototype OTA. Evaluations will be performed based on the merits of the white paper rather than a particular teaming arrangement or lack thereof
		Can the Government provide more details about the Phase II prototype demonstration requirements? Specifically:

Will demonstrations be conducted at government facilities or contractor facilities?

What type of data or scenarios should be prepared for the demonstration?

Are there specific metrics or performance criteria that will be evaluated?	This information will be provided to those selected for the protyping effort.
		Are there any incumbent contractors currently providing D-ISR services? If so, will there be knowledge transfer requirements or transition periods for selected contractors?	Yes. Knowledge transfer is planned for no less than 30 days with 60 being perferred.
		The AOI mentions that contractor teams will require TS/SCI with access to FGI, NATO, SAP, and ACCM material "after Production OTA award." Can you clarify:

What clearance level is required for Phase I and Phase II activities?

What is the expected timeline for obtaining required clearances?

Are there interim clearance requirements that would allow work to begin?	The government intends for prototpying efforts to occur on TS/SCI networks in addition to unclassified environments. Obtaining the required security clearance is the responsibility of the vendor. Interim clearances will not be eligible for access.
		Given the DoD CIO Memo requirements in the Go/No-Go matrix, can the Government provide guidance on:

Preferred or approved open source software registries?

Specific OSS components already approved for use in the USSOCOM environment?

The process for obtaining approval for new OSS components?	The process is simlar to or the same process as all other DoD networks. The approved software list is too large to post here in the forum.
		If an offeror meets the Non-Traditional Defense Contractor definition, are there any expected cost share requirements for Phase I or Phase II, or would this be a fully funded effort?	Offerors would not be required to cost share if they are an NTDC, however offerors may propose a cost share when responding to solicitations for OTAs. If a TDC would like to participate, one way they may become eligible is through a cost share.
		Can the Government provide guidance on the expected scope and budget range for Phase II prototype awards to help inform our approach and team sizing?	Scope of prototpye will include the need for all the core services listed in the CSO.
		The AOI mentions follow-on production contracts "valued at up to approximately $100,000,000." Is this value:

Per awardee or total across all awardees?

Expected to be divided among multiple contractors or awarded to a single provider?

Inclusive of all 15 locations or focused on specific geographic areas?	The dollar value is the total across all awardee(s). It could be split among multiple production vehicles or a single vehicle. It would include all locations
		Would partnerships with universities be viewed favorably in the evaluation? Are there specific research capabilities or facilities that would enhance a proposal?	No preference.
		Are there opportunities for collaboration with other D-ISR contractors, or is each award expected to be independently executed? Would the Government facilitate coordination among selected contractors?	Offerors may certainly team with other vendors. The Government will not be coordinating teaming arrangements.
		Can you provide details about the government-provided Jira instance mentioned in the AOI? Specifically:

What plugins or integrations are available?

Are there templates or workflows that must be followed?

What reporting and metrics are expected to be maintained?	The government is open to workflows and metric suggestions from the vendor as long as the work is adequately tracked and reported.
		What specific metrics will the Government use to evaluate contractor performance during prototype and production phases? Are there quantitative targets for analyst cognitive load reduction, processing speed improvements, or other operational metrics?	These will be developed prior to the solicitation for prototype/production efforts.
		What is the expected data size and volume of intelligence information to be processed and handled within this AOI?	Data size will vary depending on a project by project basis. The majority of the data is text, however there are some image, audio and video requirements as well.
		What are the scope and operational scale for the technologies to be developed, specifically regarding geographical coverage and deployment environments?	Deployments will be to provide access to users that are positioned globally.
		Can you specify the key technical requirements and performance metrics, such as latency, accuracy, and real-time processing capabilities?	This will vary on a project by prject basis depending on the user requirements in the project request.
		What are the constraints and security considerations related to data transmission, storage, and access within this AOI?	System must comply with DoD, IC and USGOV standards.
		Are technical demonstrations provided prior to USSOCOM making prototype awards or after USSOCOM makes prototype awards?	After.
		Does the technical demonstration take place as part of the 8 week prototype? If so, is it immediately following prototype award or at the conclusion of the 8 week prototype period?	At the conclusion.
		Is the representative problem set provided prior to the technical demonstration or after the technical demonstration?	Prior to.
		Please provide clarification for Technical Attributes #3: Provide metrics, goals or further define “high performance API”, Provide metrics, goals or further define “near-time thruput”, Define unacceptable time, and Define desired response time. What specifically is the Government looking for an offeror to provide in response?	The government does not have a defined metric for this at this time.
		Does the Government have metrics goals to aim for with "near realtime throughput" and "high performing (APIs)	The government does not have a defined metric for this at this time.

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