Compiled QA List.xlsx
XLSX spreadsheet 30 KB Posted
- Attached to
- SOFMC TAK Technology AOI
- Solicitation number
- H9241525X0003
- Issued by
-
United States Special Operations Command
About this file
This document is a Compiled Q&A List for a USSOCOM Special Operations Forces Mission Command (SOFMC) Technology Area of Interest (AOI) solicitation focused on developing innovative Tactical Assault Kit (TAK) software capabilities. The government seeks novel commercial solutions for an AI/ML-enabled Gridded Reference Graphic (GRG) prototype to be demonstrated within an 8-week period, with the potential for a follow-on production Other Transactional (OT) agreement. Key technical requirements include developing an AI/ML solution that can detect, identify, confirm, and label buildings/objects on end-user devices within the TAK ecosystem (ATAK, WINTAK, TAKX, WebTAK OASIS), with processing performed entirely on TAK clients.
The solicitation targets non-traditional defense contractors and aims to rapidly enhance mission planning capabilities through innovative software development. Offerors must submit a 6-page white paper addressing technical attributes, DevSecOps processes, and a prototype demonstration schedule, with an anticipated prototype award by the end of FY25 and a potential production agreement no later than 3Q FY26. The government expects a Technology Readiness Level (TRL) 6 prototype that provides Government Purpose Rights, integrates with existing TAK software, and supports disconnected/degraded environments. Foreign-owned businesses may participate through teaming arrangements with U.S. companies, and the prototype demonstration will be unclassified.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SOFMC TAK Technology AOI - SOF ATL-SDA.docx | DOCX document | |
| Question Answer Matrix.xlsx | XLSX spreadsheet | |
| Attachment 02 Epic Statement (AIML Enabled Gridded Reference Graphic (GRG)).docx | DOCX document | |
| Attachment 01 Go_ No-Go Matrix_final.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Question # | Document Referenced | Paragraph Referenced | Question | Answer |
| 1 | Attachment 02 Epic Statement: AI/ML Enabled Gridded Reference Graphic (GRG) | Paragraph reference N/A. | Is attachment 02 defining a specific application that is the focus of the AOI. Meaning are offerors supposed to specifically address the GRG capability. OR is Attachment 2 simply a template / example of an Epic Hypothesis Statement, and offers are supposed to fill out this template for the capability they are proposing? | Yes. This is a specific application the Government is pursuing. Respondents to the AOI should address information in the announcement to include the EPIC within promulgated guidelines. |
| 2 | SOFMC TAK Technology AOI SOF ATL SDA | Sections: 1. Purpose, and 3. Requirements. | Is the Government primarily looking for mission applications (mission planning apps, etc.) that replace, enhance or are new capabilities? OR is the government interested in enabling capabilities that allow existing and/or modernized applications to more easily integrate into the TAK Ecosystem? Is one or the other (or both) acceptable under this AOI. | The initial scope of this CSO is a prototype for a new or novel GRG capability. The Government anticipates a successful prototype may transition to production and require the capacity to support the GRG capability in addition to capabilities developed in support of the broader TAK Enterprise. |
| 3 | SOFMC TAK Technology AOI SOF ATL SDA | Sections: 1. Purpose, and 3. Requirements. | Is the Government primarily looking for mission applications (mission planning apps, etc.) that replace, enhance or are new capabilities? OR is the government interested in enabling capabilities such as a DevSecOps to the Edge ecosystem that allows existing and/or modernized applications to more easily integrate into the TAK Ecosystem? Is one or the other (or both) acceptable under this AOI. | The initial scope of this CSO is a prototype for a new or novel GRG capability. The Government anticipates a successful prototype may transition to production and require the capacity to support the GRG capability in addition to capabilities developed in support of the broader TAK Enterprise. |
| 4 | SOFMC TAK Technology AOI SOF ATL SDA | Description on sam.gov | AOI references this is a “continuous development and fielding of collaborative Tactical Assault Kit (TAK) software” – could you share if this is a follow-on solicitation? | No, the government will solicit, and issue prototype awards to the most qualified offerors. Offerors with successful prototypes may be awarded a follow-on production OT agreement. This is not a follow-on solicitation. |
| 5 | Attachment 2 - Epic Statement | N/A | Is the Government seeking existing, fully developed software solutions that already "provide a common reference graphic for multi-unit coordination on an objective", or will proposals that include the development of a new, innovative solution be considered? If new development is acceptable, can the Government please define the anticipated timeline between Phase I and Phase II to support effective development and delivery? | The initial scope of this CSO is a prototype for a new or novel GRG capability. The Government anticipates a successful prototype may transition to production and require the capacity to support the GRG capability in addition to capabilities developed in support of the broader TAK Enterprise. Anticipate prototype award/agreement by the end of FY25. |
| 6 | AOI SOF ATL SDA | Section 5, Bullet 5 Notional Schedule | The notional schedule appears to focus solely on "performing an operational prototype demonstration to meet the epic statement." Does this imply that offerors are expected to have the software solution fully developed in advance of Phase I? Given that effective deployment requires activities beyond demonstration such as integration with existing systems, user training, and iterative user feedback, would the Government consider expanding the notional schedule to account for these critical tasks? | Phase I involves the Government’s evaluation of White Papers, assessing the offerors' proposed solutions against the required technical attributes, current capabilities relative to desired software developer attributes, and their plans for meeting these attributes. Activities such as integration with existing systems, user training, and iterative feedback are not included in the current notional schedule. Instead, these tasks would be addressed in a follow-on contract after the successful demonstration of a prototype in Phase II. |
| 7 | AOI SOF ATL SDA | Section 5, Bullet 6 Scale Production Teams | The RFI requests a plan for how offerors intend to scale production teams annually to “develop, test, integrate, deploy, and sustain the requested TAK capability (capabilities).” Can the Government clarify whether these production teams are expected to support only the GRG tool described in Attachment 2’s epic statement, or if the scope includes additional TAK capabilities beyond the GRG tool? This clarification is necessary for accurately resourcing and structuring teams to meet the full intent of the requirement. | The initial scope of this CSO is a prototype for a new or novel GRG capability. The Government anticipates a successful prototype may transition to production and require the capacity to support the GRG capability in addition to capabilities developed in support of the broader TAK Enterprise. |
| 8 | Attachment 2 - Epic Statement | N/A | Is the Government only interested in innovative solutions specific to the Epic Statement described in Attachment 2, or are offerors permitted to propose other TAK Development innovations, which include the Technical Attributes listed in the AOI, that will benefit SOFMC? | The government's current scope is limited to the GRG prototype described in the epic statement and does not include additional TAK capabilities or other innovations beyond this scope. |
| 9 | General | NA | We kindly request a week extension to the due date. | An extension will not be granted due to meeting mission requirements. |
| 10 | SOFMC+TAK+Technology+AOI+-+SOF+ATL-SDA | None | Is there a requirement that the processing be done on each TAK client, or can/should it be performed off-device? | All processing needs to be done on each TAK Client. |
| 11 | SOFMC+TAK+Technology+AOI+-+SOF+ATL-SDA | 3. Requirements | The solicitation states that everything be delivered to the government with nothing more constrained than Government Purpose Rights. Is an existing commercial solution that requires purchase of a license for use of the software out of scope? | The government is pursuing full GPR in both prototype and production. |
| 12 | SOFMC+TAK+Technology+AOI+-+SOF+ATL-SDA | 3. Requirements | Is it acceptable that the TAK plugin would be Government purpose rights or Government unlimited rights, but the models remain proprietary/licensed? | The government is pursuing full GPR in both prototype and production. |
| 13 | SOFMC+TAK+Technology+AOI+-+SOF+ATL-SDA | 3. Requirements | Can you define "identifying" in this context? "Provide Artificial Intelligence/Machine Learning assistance in planning to reduce cognitive load through automation for detecting, identifying, confirming, and labeling buildings/objects/routes." | Identifying refers to the ability to further discern between detected structures to accurately "identify" whether the detected object is a building or something else. |
| 14 | SOFMC+TAK+Technology+AOI+-+SOF+ATL-SDA | 4. Event Timeline | What are the evaluation metrics at the end of the prototype period? Is there a desired minimum TRL or minimum accuracy in the building detection capability? | The government expects a successful prototype to be Technology Readiness Level (TRL) 6 at the end of the prototype period. TRL 6 Prototype System Verified: System/process prototype demonstration in an operational environment. |
| 15 | Technology AOI | Section 3, bullet 7 | The text reads, "Ensure integration with SOCOM Mission Planning software. To include but not limited to; ATAK, WINTAK, TAKX and WebTAK OASIS." Should iTAK (Apple iOS) development be included in the scope? | No, iTAK is not part of the scope for this AOI. |
| 16 | SOFMC TAK Technology AOI SOF ATL SDA.pdf | 5. Submission Instructions | We believe we are a Non-Traditional Defense Contractor, Can Australian NTD companies provide their services? | 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 |
| 17 | SOFMC TAK Technology AOI SOF ATL SDA.pdf | 3.a. Technical Requirements - Synthesize Operational Military Battlespace Information | We assume the battlespace data you expect to receive from autonomous vehicles are [images and sensor data] and team users are [images and text], is this true? | The data used to create the GRG can be any data set (image) that is viewable in TAK. |
| 18 | SOFMC TAK Technology AOI SOF ATL SDA.pdf | 3.a. Technical Requirements - Provide Artificial Intelligence/Machine Learning | Do you anticipate the outcome of 8 weeks of work to deliver a prototype of a system that can generate POI, ROI from satellite map information for building / object / route analysis? | The government does not expect the prototype to generate a POI or ROI. The government expects a GRG created in the area of interest identified. |
| 19 | SOFMC TAK Technology AOI SOF ATL SDA.pdf | 3.a. Technical Requirements – Provide Artificial Intelligence/Machine Learning | Do you expect this data product is shared to other devices [Users, Operators] in your TAK team for a common understanding of environment? | The information will be shared across TAK users. |
| 20 | SOFMC TAK Technology AOI SOF ATL SDA.pdf | 3.a. Technical Requirements – Modular Open Systems Architecture | Are you interested in mission planning and control software for the autonomous 1 to many operation of UAS, UGV teams | The question addresses requirements beyond the scope of the CSO AOI. |
| 21 | SOFMC TAK Technology AOI SOF ATL SDA.pdf | 3.a. Technical Requirements – Denied-Disconnected envs | Do you expect real time data sharing in a radio comms denied environment? | The Government anticipates real time data sharing would be impacted in a radio comms denied environment. Due to sensitive nature of Tactics, Training, and Procedures the Government is unable to expound further in this venue. |
| 22 | SOFMC TAK Technology AOI SOF ATL SDA.pdf | 3.a. Technical Requirements | Do we need to respond to all the requirements, or is a solution still suitable if it responds to a subset. | The government will evaluate against the Required Technical Attributes and the Desired Software Developer Technical Attributes |
| 23 | Technology AOI | p. 5, paragraph 3, "Submission Instructions" | The AOI states, "The White Paper shall not exceed a total of six (6) letter-sized (8 ½ x 11) pages and must include appropriate classification markings if necessary. " Given the amount number of requirements to be addressed in the white paper, would the Government consider increasing the page limit to 8 pages? | Per the AOI submission instructions, the government will not evaluate any materials exceeding 6 pages and must use a 12-point font size in an easily readable font, such as Times New Roman or Arial. |
| 24 | Technology AOI | p. 5, paragraph 3, "Submission Instructions" | The AOI states, "Number the pages consecutively and use a 12-point font size in an easily readable font, such as Times New Roman or Arial." Can the Government confirm that 10 point size font is acceptable for tables, diagrams, and figures? | Per the AOI submission instructions, the government will not evaluate any materials exceeding 6 pages and not use a 12-point font size in an easily readable font, such as Times New Roman or Arial. |
| 25 | Technology AOI | p. 5, paragraph 3, "Submission Instructions" | The AOI states, "The 6-page limitation does not include the title page or information necessary to meet the requirements of the go/no go matrix, but if used, a table of contents, definition of acronyms, illustrations, or diagrams will count against the 6-page limit." Would the Government consider allowing Offerors to include a table of contents and definition of acronyms in the white paper that are not included in the page limit? | Per the AOI submission instructions, anything beyond the title page will count against the 6-page limit. Refer to page 5-6 of AOI. |
| 26 | Technology AOI | p. 5, paragraph 5, "Submission Instructions, " number 5 | The AOI states "Provide a notional schedule to perform an operational prototype demonstration to meet the epic statement." Would the Government consider allowing Offerors to use an 11x17" page for the notional schedule? | Per the AOI submission instructions, the government will only accept White Paper not exceeding a total of six (6) letter-sized (8 ½ x 11) page size. Refer to page 5-6 of AOI |
| 27 | Attachment 2, Epic Statement | N/A | Can the Government clarify if Offerors should complete the Epic Statement based on their proposed technology solution within the White Paper? | The Offeror should address their proposed technology solution within the white paper. |
| 28 | Attachment 2, Epic Statement | N/A | Can the Government confirm that Offerors should include completed Attachment 02 Epic Statement with their submission as a separate attachment? | The Offeror should address their proposed technology solution within the white paper. |
| 29 | SOFMC_TAK_Technology_AOI | What contract vehicle does the government plan to utilize? | The Government plans to use an Other Transactional Prototype Agreement leading to a production agreement. | |
| 30 | SOFMC_TAK_Technology_AOI | Is this a follow-on effort? | No this is not a follow-on effort. | |
| 31 | SOFMC_TAK_Technology_AOI | 1.3 | Is the 8 week period mentioned in Section 1 the expected duration of Phase II award up to the demonstration as described in Section 4? | The Period of Performance for the prototype is eight (8) weeks. |
| 32 | SOFMC_TAK_Technology_AOI | 5.5.6 | Is the 14 week Program Planning Increment cycle mentioned in section 5, a period of time after a successful Phase II demonstration? | The Offeror should provide a plan that details the team structure required, processes for managing the team(s), anticipated work location(s) to support SOCOM Enterprise and other DOD Federal entities following a 14-week Program Planning Increment cycle within the white paper if a awarded a follow-on production contract. |
| 33 | SOFMC_TAK_Technology_AOI | 1.2 | Can the government provide a list of the existing suite of SOFMC software? | The TAK Family of software (ATAK, WINTAK, TAKX and WebTAK OASIS) |
| 34 | SOFMC_TAK_Technology_AOI | 3.a.9.1 | What is the planed existing authorized DoD DevSecOps resources that contractors can use for the prototype development? | The government will sponsor Tak.gov military Software Development Kit (SDK) access if awarded a prototype agreement. |
| 35 | SOFMC_TAK_Technology_AOI | 5.5.6 | Is the Whitepaper Requirement 5 "Provide a notional schedule to perform an operational prototype demonstration to meet the epic statement." the same 8 week prototype required in the Go-NoGo Matrix #3? | The Period of Performance for the prototype is eight (8) weeks. |
| 36 | SOFMC TAK Technology AOI | 1.3 "This Technology Area of Interest (AOI) focuses on identifying novel commercial solutions with architectures and technical attributes that can be demonstrated within an estimated 8-week period" | Is the total period of performance for the Prototype 8 weeks or is it longer than 8 weeks but the primary requirement is a tech demo at the 8 week period? | The Period of Performance for the prototype is eight (8) weeks. |
| 37 | SOFMC TAK Technology AOI | 6. Prototype Production Award Requirements | What is the expected timeline between Prototype OT completion to evaluation, notification and continuation into Production OT? | The Government anticipates awarding an Other Transactional production agreement no later than 3QFY26. |
| 38 | SOFMC TAK Technology AOI | 3. DEVSECOPS Pipeline | Are vendors expected to develop and demonstrate prototypes in vendor-owned commercial cloud environments or will the government provide access to cloud infrastructure, resources, tooling, and development/test environments? | The offeror should leverage existing authorized DoD DevSecOps resources, or the offeror must self-certify compliance with NIST SP 800-218 (Secure Software Development Framework) and provide evidence of compliance for their own DevSecOps resources to meet the above requirements. |
Self-certify their software product complies or intends to comply with NIST SP 800-53 (Risk Management Framework) and provide evidence of compliance.
| 39 | SOFMC TAK Technology AOI | 3. Provide Artificial Intelligence/Machine Learning | For the purposes of the prototype, are there any restrictions on using commercially available AI/ML technologies? If the expectation is to transition prototypes to operational use, what available AI/ML technologies exist in operations? Should vendors limit using technologies in prototypes based on what's available in operations? | There are no restrictions on using commercially available AI/ML technologies. The Government is investigating use of new applications and AI/ML technologies vice leveraging an existing technology. The Government anticipates asserting Government Purpose rights. |
| 40 | SOFMC TAK Technology AOI | 1.3 "This Technology Area of Interest (AOI) focuses on identifying novel commercial solutions with architectures and technical attributes that can be demonstrated within an estimated 8-week period" | Is the government looking for already existing, commercial off the shelf (COTS) solutions only or is the government open to commercial service offerings to build custom GOTS solutions? Or open to both? | The Government is looking for innovative COTS/GOTS solutions. The Government anticipates asserting Government Purpose rights. |
| 41 | SOFMC TAK Technology AOI | 3b "Offeror may be required to provide Secret clearance to eligible personnel and provide personnel to perform security related functions to meet other security requirements." | At what classification level is the Prototype demonstration expected to be at? Will vendors need personnel to have Secret clearances for the Prototype phase if developed commercially and at the unclassified level? | The Prototype and demonstration is Unclassified. |
| 42 | SOFMC AOI | 3 | Does the EPIC statement defined in attachment 2 describe the intended deliverable provided in the requirements listed in SOFMC AOI paragraph 3 and are additional plug-ins desired? | The EPIC statement in conjunction with paragraph three describes the intended deliverable; additional plug-ins may be required in the production phase. |
| 43 | SOFMC AOI | 3, Bullet 1 | Is there a list of COPs other than TAK based systems SOF MC is looking to connect with which run non-TAK (CoT) data formats? | This CSO is focused on the TAK (ATAK, WINTAK, TAKX, WebTAK OPASIS) Suite of software |
| 44 | SOFMC AOI | 3, Bullet 2 | Does the user at the phone and the laptop require the same planning capability or different based on echelon? | The GRG should have capability parity whether on laptop or End User Device. |
| 45 | SOFMC AOI | 3, Bullet 3 | is Wargaming part of this mission scenario? | War gamming is not part of the scenario. |
| 46 | SOFMC AOI | 3, Bullet 4 | Are AI/ML capabilities residing on all echelons or specific to edge devices? | The AI/ML capabilities need to reside on edge (laptop, phone) devices |
| 47 | SOFMC AOI | 3, Bullet 4 | Will users be required to ID or verify the detections and offer Tactical labels vs machine generated? | The Government is looking for machine generated labeling |
| 48 | SOFMC AOI | 3, Bullet 4 | Will users be required to update or specify specific "objects" desired for the AI/ML model to search on? | This CSO is focused on the detection, identification, and labeling of buildings |
| 49 | SOFMC AOI | 3, Bullet 4 | With detecting and Identifying part of AI/ML, which robotics/optics platform is desired by the Government? | The CSO is not addressing robotics |
| 50 | SOFMC AOI | 3, Bullet 5 | Are capabilities limited to end user devices or can they include server/enterprise capabilities designed and developed for Disrupted, Degraded, Intermittent, and Low Bandwidth (DDIL) environments? | Capabilities should not require server/enterprise connection to work |
| 51 | SOFMC AOI | 3, Bullet 5 | Can the resulting solution have dependencies on additional hardware components such as unmanned systems or wearable devices? | The solution should not have external dependencies on hardware components. |
| 52 | SOFMC AOI | 3, Bullet 7 | Will the Government accept proposals the provide optimizations and enhancements to existing capabilities found within the TAK ecosystem? | The Government is looking for innovative COTS/GOTS solutions. |
| 53 | SOFMC AOI | 3, Bullet 7 | What weight will power management have in the application of AI intensive applications at the edge? | The government will collaborate with the awarded Performer regarding Size, Weight, and Power requirements of the proposed application. |
| 54 | SOFMC AOI | 3, Bullet 7 | is the data required to travel between security enclaves? (e.g., CUI -> SECRET, SECRET -> TS) | The AI/ML models are not expected to traverse a CDS (Cross Domain Solution). |
| 55 | SOFMC AOI | 3, Bullet 9 | Does the DevSecOps process outlined provide any type of controlled measures for implementing AI as part of the recommended solution? | The government will collaborate with the awarded Performer regarding control measures for implementing AI during the production phase. |
| 56 | Attachment 02 Epic Statement | "Our solution" row | Will USSOCOM please define each of the following: AI/ML detect, identify, confirm, and label? | The AI/ML detects objects in the image, identifies the object, cross validates, and labels the object number automatically. |
| 57 | Attachment 02 Epic Statement | "Our solution" row | Will USSOCOM please confirm how a solution will be measured as successfully accomplishing each of these terms (AI/ML detect, identify, confirm, and label)? | The Government will define success criteria in the prototype agreement. |
| 58 | Attachment 02 Epic Statement | Entire document | Is Attachment 2 and the epic statement for AI/ML Enabled Gridded Reference Graphic the first of many TAK-based applications, or the entirety of this requirement for SOFMC? | The focus is to provide a mission planning application by creating a new capability, enabled by AI, that creates a Gridded Reference Graphic (GRG). The proposed solution shall integrate into the TAK Ecosystem. The Government intends to evaluate the proposed solution. Bring new and novel capabilities to the program. |
| 59 | SOFMC TAK Technology AOI - SOF ATL-SDA | 3. Requirements | One of the required technical attributes for the DevSecOps bullet point is a certification that the software product complies with or intends to comply with NIST SP 800-53. It includes a parenthetical that states this publication is about a Risk Management Framework. However NIST SP 800-53 is about Security and Privacy Controls. NIST SP 800-37 is about Risk Management Frameworks. Which publication is the intended publication to comply with for this technical attribute? | Both publications are directly relevant to this effort. |
| 60 | SOFMC TAK Technology AOI - SOF ATL-SDA | 5. Submission Instructions | What exactly does and does not count towards the 6-page limit? It's clearly identified that the title page and executive summary do not count towards the 6-page limit. It also states "information necessary to meet the requirements of the go/no go matrix" does not count towards the 6 page limit. If we have content describing how we comply with the open-source memo, the required and desired technical attributes, and the prototype demonstration schedule, do these items count towards the 6 pages or is it "information necessary to meet the requirements of the go/no go matrix"? If the former, what then counts as "information necessary to meet the requirements of the go/no go matrix"? | The White Paper shall not exceed a total of six (6) letter-sized (8 ½ x 11) pages and must include appropriate classification markings if necessary. One page equals one side of a sheet of paper. Number the pages consecutively and use a 12-point font size in an easily readable font, such as Times New Roman or Arial. The 6-page limitation does not include the title page or information necessary to meet the requirements of the go/no go matrix, but if used, a table of contents, definition of acronyms, illustrations, or diagrams will count against the 6-page limit. The Government will not evaluate any materials exceeding 6 pages. Go/No-Go requirements will be submitted as a separate attachment to the White Paper and will not be included in the 6-page limitation. Refer to page 5-6 of AOI |
| 61 | SOFMC TAK Technology AOI - SOF ATL-SDA | 2. Background | Does SOFMC already use TAK? If so, which applications? | SOFMC uses the TAK Family of software (ATAK, WINTAK, TAKX and WebTAK OASIS). |
| 62 | Attachment 02 Epic Statement | Entire document | What SOF user group requires the AI/ML Enabled Gridded Reference Graphic (GRG)? | The Government is looking for innovative COTS/GOTS solutions for the Enterprise. |
| 63 | SOFMC TAK Technology AOI - SOF ATL-SDA | 3. Requirements | Is this a new requirement? | This is a new requirement. |
| 64 | Attachment 02 Epic Statement | Entire document | Does USSOCOM have an existing software baseline/tools that are expected to be used as part of developing the AI/ML Enabled Gridded Reference Graphic (GRG) | The TAK Family of software (ATAK, WINTAK, TAKX and WebTAK OASIS) |
| 65 | SOFMC TAK Technology AOI - SOF ATL-SDA | 5. Submission Instructions | Please confirm whether size 8 font can be used for graphics. | The CSO AOI does not specify font size for graphics. |
| 66 | SOFMC TAK Technology AOI - SOF ATL-SDA | 3. Requirements | Please confirm that the prime offeror must possess a Secret Facility Clearance. | The Prototype and demonstration is Unclassified. |
| 67 | SOFMC TAK Technology AOI - SOF ATL-SDA | 3. Requirements | Is classified development at the Secret level expected as part of this requirement? | The Prototype and demonstration is Unclassified. |
| 68 | SOFMC TAK Technology AOI - SOF ATL-SDA | 6. Prototype Production Award Requirements | Does USSOCOM intend to make a minimum or maximum number of prototype awards? | The Government does not have a minimum or maximum number anticipated. |
| 69 | SOFMC TAK Technology AOI - SOF ATL-SDA | 6. Prototype Production Award Requirements | Does USSOCOM intend to make one or multiple production awards? | The Government intends to make a single production award. |
| 70 | SOFMC TAK Technology AOI - SOF ATL-SDA | 5. Submission Instructions | Is it acceptable to place the Overview Diagram within the Executive Summary? | It is acceptable to place an overview diagram within the Executive Summary. |
| 71 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | What ecosystem of products are expected to have interoperability with (e.g., existing mission systems, 3rd party vendors)? | The TAK Family of software (ATAK, WINTAK, TAKX and WebTAK OASIS) |
| 72 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | What container orchestration platforms are required (e.g., Kubernetes, Docker Swarm) or deployment methods (e.g., Helm charts, OCI images)? | No particular requirements. Ensure containerized software solutions are deployable across various platforms and environments. |
| 73 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | Are there media policy documents or exception handling protocols that we should align with? | Media policy documents or handling protocols will be addressed by the Government in the prototype phase. |
| 74 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | What are minimum performance expectations (e.g., response time, data size) when operating in D-DIL environments? | The AOI does not define minimum performance requirements and will be addressed by the Government in prototype phase. |
| 75 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | What planning data sets are most critical to support offline access? | The Government anticipates geographic information systems (GIS) datasets necessary for mission planning . Due to sensitive nature of Tactics, Training, and Procedures the Government is unable to expound further in this venue. |
| 76 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | What specific object types or battlefield features must the AI/ML detect and label? (e.g., buildings, vehicles, routes)? | Artificial Intelligence/Machine Learning is intended to reduce user cognitive load through automatic detection, identification, confirmation, and labeling of buildings. |
| 77 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | What level of automation and human-in-the-loop (HITL) support is expected in your operational workflows? | The government is looking for as much automation as possible with human verification after the fact. |
| 78 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | For Government Purpose Rights (GPR), is source code access required, or is object code with detailed documentation sufficient? | The government requires source code submitted for security scans at completion of prototype phase. |
| 79 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | What version(s) of ATAK/WINTAK/TAKX/WebTAK are currently being used in operational environments? | The Government requirement is to work with latest TAK Family of software versions (ATAK, WINTAK, TAKX and WebTAK OASIS) while maintaining backwards compatibility. |
| 80 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | Which OGC standards are mandatory (e.g., WMS, WFS, GeoJSON, STANAG)? | The government does not have a mandated standard. |
| 81 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | What types of geospatial datasets (e.g., elevation, vector, raster) are expected to be exported and shared? | The government does not expect to share geospatial datasets for this effort. |
| 82 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | Are there approved DoD DevSecOps platforms you prefer us to leverage (e.g., Platform One, Iron Bank)? | The offeror should leverage existing authorized DoD DevSecOps resources, or the offeror must self-certify compliance with NIST SP 800-218 (Secure Software Development Framework) and provide evidence of compliance for their own DevSecOps resources to meet the above requirements. Self-certify their software product complies or intends to comply with NIST SP 800-53 (Risk Management Framework) and provide evidence of compliance. The government will sponsor Tak.gov military Software Development Kit (SDK) access if awarded a prototype agreement. |
| 83 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | What are expectations for continuous authority to operate (cATO) or any prefer on how to manage ATO lifecycle? | The offeror should leverage existing authorized DoD DevSecOps resources per AOI. The government expects for any follow-on production award, any successful prototypes must transition to operational use on USSOCOM networks prior to fielding, which entails obtaining a favorable Authority to Operate (ATO) decision and ongoing cybersecurity risk acceptance for the product, along with other requirements. |
| 84 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | Is there an expected number of cleared personnel required for initial support? | There is no expectation that cleared personnel are required for the initial prototype effort. |
| 85 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | Will the Contractor be expected to support any CONUS or OCONUS classified environments during prototype or production? | The Performer may be expected to support CONUS/OCONUS classified environments during the production phase after transition. |
| 86 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | Any other areas where Contractor can provide innovation concepts beyond the stated requirements, for example, battlefield automation? | The Contractor may provide innovative concepts beyond the stated requirements. However, the Performer will be evaluated based on the required attributes. |
| 87 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | Can the contractor build the Prototype in Contractor environment under IL2 and then later move with IATT to IL3 in Government environment? | The Performer, if awarded the prototype, may build the capability in their IL2 environment and later transition to an identified environment. |
| 88 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | You have mentioned 14 weeks program planning, is that the Period of Performance (PoP) contemplated by SOCOM? | The Period of Performance for the prototype is eight (8) weeks. |
| 89 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | Does the contractor get favorable evaluation if the HW (Edge computing node) is already in use by SOCOM ? | The Performer will be evaluated against the promulgated requirements. |
| 90 | SOFMC_TAK_Technology_AOI_-_SOF_ATL-SDA.docx | Section 3. Requirements | Will SOCOM share sample data going to TAK? | The Government anticipates sharing sample data in the prototype phase. |
| 91 | AOI | 3.a. | Does the offeror have to comply with ALL bulleted technical attributes listed in this section, or should we make clear where we do not and may need to make enhancements for 100% compliance? | Potential offerors SHALL identify their solution’s ability to meet the Government’s required technical attributes. |
| 92 | Epic Statement | "business outcomes" | Does the system need to automate mission planning or enable mission planning based off the GRG product? | The government anticipates automated creation of the GRG product. |
| 93 | AOI | Phase II | I did not see a requirement for pricing or a ROM for system development. Is there a ROM required for a white paper to reference any development costs for a prototype demonstration? | There is no ROM required with white paper submission. |
| 94 | SOO | 3.a. Bullet 3 | Will the government provide example data for the requirement to "Synthesize Operational Military Battlespace Information"? | The Government anticipates sharing sample data in the prototype phase. |
| 95 | SOFMC+TAK+Technology+AOI+-+SOF+ATL-SDA | 5 | Is non-traditional contractor participation required? | White papers must describe how the Offeror meets the Non-Traditional Defense Contractor requirement in accordance with 10 U.S.C 4022. If the Offeror does not meet the definition of Non-Traditional, the Offeror will need to determine the cost share with a Non-Traditional Defense Contractor. |
| 96 | SOFMC+TAK+Technology+AOI+-+SOF+ATL-SDA | 5 | What cost/price information is required in the White Paper? | The Government did not request cost/price information in the White Paper. |
File details come from the government source that posted it. Updated .