Questions and Answers 2 - 4Jun2026.pdf

PDF 122 KB Posted

Attached to
Call 002 DSO CSO 2 Step Call TAK (Team Awareness Kit)
Solicitation number
FA8730-22-S-C001-0002
Issued by

About this file

This is a Questions and Answers document dated 2-4 June 2026 addressing inquiries related to a new federal contract effort involving TAK (Tactical Awareness Kit) plugin development for C2IMERA integration.

The project is a brand-new initiative (not a recompete) focused on developing capabilities built on the TAK framework to feed data into C2IMERA, enabling improved data collection and increased data sharing to edge TAK nodes. The scope concentrates on high-priority items from core capabilities requirements, with multiple capabilities potentially supported by a single plugin sharing the same persona/workflow. Available C2IMERA endpoints for data integration include Aircraft, Base Conditions, Incident Reports, Custom/Flex Pages, and Airfield discrepancies with sensor/video feeds. TAK plugins must be open source only; non-open source or non-commercial plugins are not acceptable. The solution will utilize TAK Cursor on Target messages connecting to a TAK server, which then connects to C2IMERA, with connectivity available through commercial cell networks, Starlink/Shielded networks, and other means. The intended architecture employs a combination of TAK client mesh connectivity and TAK servers at user locations, with the government remaining agnostic regarding peer-to-peer versus user-to-server solutions as long as data is collected and reaches C2IMERA. Data collection focuses on incident reports and alerts plotted on the Common Operating Picture through flexpage endpoints. Specific details regarding writable C2IMERA endpoints and interface documentation will be provided by the government at a later time, potentially to those who submitted White Papers or Pitch Decks.

View the file

Other files

File Type Posted
Questions and Answers 1 - 2Jun2026.pdf PDF
Atch 2_Evaluation Criteria_21May26.pdf PDF
DSO CSO 2 Step Call_21May26.pdf PDF
Atch 1_AOI_21May26.pdf PDF

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

QUESTIONS ANSWERS

Is there any incumbent/recompete or this is a brand-new project? If yes, could you please provide us with their award number or even if the customer bought similar services in the past.

This is a new project we would like to see the " specific C2IMERA endpoints [which] are currently writable and available for integration under this effort"?

No responses at this moment. The Government will determine at a later time, if further details will be provided to those that submitted a White Paper or Pitch Deck.

Can you help scope the effort you're asking for a

ROM? Anything would help - number of APIs provided by Leidos, number of personas, etc.

Thanks in advance

The scope is focused on the high priority items listed in the core capabilities requirements. Of those capabilities share the same persona/ workflow and as such can have one plugin that supports multiple capabilities. We are not intending on this being a solution or replacement for the wing staff workflows that C2IMERA supports, but rather a capability built on top of the TAK framework that feeds C2IMERA that allows for better and easier data collection into C2IMERA and increased data sharing to edge TAK nodes.

Endpoints that are available in C2IMERA to send data to include but are not limited to:

• Aircraft

• Base Conditions

• Incident Reports

• Custom / Flex Pages

• Airfield discrepancies and sensor/video feeds

When referencing "This technology would be leveraging potentially pre-existing TAK plugins that are either open source or commercially available." Does this mean the plugins need to be open source or commercially available? Could we leverage a non-open source, non-commercial plugin as well?

Yes, this will be open source only.

1. Which C2IMERA endpoints are currently writable and available for integration under this effort; and

2. Whether any interface documentation or an endpoint/API reference for those endpoints is available to interested parties at the Solution Brief stage (or, if not until Step 2, confirmation of that timing).

No responses at this moment. The Government will determine at a later time, if further details will be provided to those that submitted a White Paper or Pitch Deck.

What type of connectivity will be available at the airfields?

TAK connects via Cursor on Target messages to a TAK server, and then that server will connect to C2IMERA. Will also use commercial cell networks, starlink/starshield, etc.

What type of data do you intend to collect at the user interface level?

The type of data we would collect would benefit incident reports and alerts and plot it on the COP through the flexpage endpoints.

Is the intended solution to utilize TAK client mesh connectivity, a TAK server at the user location, or both?

Believe it would be a combination of both, we are not locked in/shouldn't be prescriptive- as long as the data is able to be collected and gets to C2IMERA we can be agnostic of the peer to peer solution vs user to server.

Questions and Answers 2 - 4 June 2026

File details come from the government source that posted it. Updated .