Android Team Awareness Kit
ATAK
ATAK is a tactical situational-awareness and mission-coordination application widely used to support mapping, collaboration, location sharing, and operational information flow in defence and public-safety contexts.
Capture relevance:
If ATAK or ATAK-style workflows matter, the capture team should think about integration, user burden, disconnected operation, security posture, and mission usability rather than treating it as just another app dependency.
Command and mission information stack
C4ISR
C4ISR refers to command, control, communications, computers, intelligence, surveillance, and reconnaissance.
Capture relevance:
This signals complex integration, information flow, and assurance needs across mission systems rather than a simple standalone product sale.
Intelligence, surveillance, reconnaissance
ISR
ISR covers the collection, processing, and use of information to understand activity, threats, or the operating environment.
Capture relevance:
Programmes with ISR content usually need clear thinking on data flow, latency, user decisions, and how information converts into mission effect.
Electronic warfare
EW
EW covers the use of the electromagnetic spectrum to sense, protect, attack, deceive, or disrupt systems and operations.
Capture relevance:
EW programmes often create high assurance, integration, safety, and evidence demands, especially where mission effects and survivability have to be proven.
Uncrewed air systems
UAS / UAV
These terms refer to uncrewed airborne platforms and the wider system around them, including command, control, sensing, payloads, and support.
Capture relevance:
The capture question is usually not the air vehicle alone. It is the wider mission system, autonomy, assurance, integration, and operator workflow around it.
Original equipment manufacturer
OEM
The company that makes the core hardware or major subsystem being supplied into the programme.
Capture relevance:
OEMs can bring credibility, installed-base access, and technical dependency, but also lock-in risk and reduced strategic control.
Concept of operations
CONOPS
CONOPS describes how a capability is expected to be used operationally, by whom, in what sequence, and under what conditions.
Capture relevance:
Weak CONOPS thinking often leads to vague requirements and poor evaluation criteria. Strong capture work helps the customer make operational use explicit.
Operational capability stack
Mission System
A mission system is the integrated combination of hardware, software, communications, data, interfaces, and workflows that enables an operational task.
Capture relevance:
Mission-system pursuits are won on integration, usability, assurance, and delivery confidence, not only on component performance.
Interoperable design approach
Open Architecture
An open-architecture approach aims to reduce lock-in by using manageable interfaces, reuse, interoperability, and extensibility across the programme.
Capture relevance:
This can become a powerful shaping theme when the customer is trying to avoid brittle prime or OEM dependency.
Sustainment model
Through-Life Support
Through-life support covers maintenance, upgrades, configuration control, training, support processes, and long-term sustainment of the capability after delivery.
Capture relevance:
Many programmes are lost because the team focuses on acquisition and underplays the operational and commercial consequences of sustainment.