Defense operations & unmanned systems

The direction and coordination of forces and activities toward an objective.

Connection to CoForceCoForce mission management is distinguished from integration with external C2 systems. Specific military-network connections and standards compliance require verification.

The connected functions of command, control, communications, computing, intelligence, surveillance, and reconnaissance.

Keep in mindC2 focuses on command and control; C4ISR also covers the communications, computing, and ISR functions that support it.

A U.S. defense approach to connecting sensing, data, and decisions across services and operational domains.

Keep in mindIt is an approach and broader effort, not a single software product or device.

Coordinating activities across operational domains such as land, maritime, air, space, and cyberspace to create combined effects.

Keep in mindConnecting different robot types alone does not constitute a complete multi-domain operations capability.

A shared view of relevant operational information. Also referred to as a Common Operating Picture.

Connection to CoForceCoForce is designed to connect device positions, status, observations, and task progress in 2D and 3D views.

Understanding relevant conditions and their significance. A COP supports situational awareness; it is not the same thing.

Connection to CoForceDevice state, observations, and mission progress provide context for operator understanding.

Collecting observations through surveillance and reconnaissance, then analyzing and combining information to inform decisions.

Connection to CoForceObservation collection, sharing, and analysis are application areas under development, not a claim of a complete intelligence capability.

An iterative decision cycle: observe, interpret the situation, decide, act, and use feedback to adapt.

Connection to CoForceThe operational concept connects device observations, AI-assisted understanding, operator authority, and field execution.

A possible plan or alternative for achieving an objective.

Connection to CoForceOperators can review proposed tasks, assignments, and sequences. This does not imply a formal military COA analysis or wargaming capability.

A command approach built on shared intent and objectives, enabling decentralized execution within defined authority and constraints.

Connection to CoForceIt informs the separation between human-defined objectives, server-side coordination, and local device execution.

Coordinating crewed assets and uncrewed systems so their capabilities contribute to a shared mission.

Connection to CoForceCoForce is being developed to connect roles, tasks, and results. Integration with specific crewed platforms requires separate assessment.

People, AI, and autonomous systems working together through complementary roles and shared information.

Connection to CoForceOperators define intent and authority. Mission agents support planning and coordination; CoEgent connects tasks to device-side execution.

Integrating people, robotic systems, and autonomy into the way formations organize, train, and operate.

Keep in mindHere HMI means Human-Machine Integration, not Human-Machine Interface.

A category covering robotic systems and systems with varying degrees of autonomy.

Keep in mindUncrewed does not automatically mean autonomous. Distinguish remote operation from autonomous task execution.

An operating mode in which a person remotely controls a device or continuously provides incremental goals through a communications link.

The ability of a system to perceive conditions and make some decisions or take actions within assigned goals and constraints.

Keep in mindAutonomy is task-specific. Autonomous movement does not imply autonomous sensing, manipulation, or every other task.

A person reviews, provides input, or approves a defined decision or action before it proceeds. The approval boundary must be explicit.

Connection to CoForceOperators review and approve AI-proposed tasks and device assignments.

A system acts within preauthorized bounds while a person supervises and can intervene. Intervention mechanisms and connectivity are part of the design.

Connection to CoForcePreauthorized routine tasks are paired with operator paths to stop or adjust execution.

An aircraft operated without a pilot onboard, using remote control, autonomous functions, or a combination.

A system encompassing the aircraft and supporting elements such as control stations, communications, and operational support.

Keep in mindUAV refers to the aircraft; UAS refers to the wider operating system.

A ground platform operated without a person onboard, through remote operation, autonomy, or a combination.

An uncrewed platform that navigates and performs tasks on the water’s surface.

An uncrewed underwater platform used for movement, observation, and other tasks.

An underwater vehicle that carries out missions autonomously. As a type of UUV, it operates with underwater communication and navigation constraints.

Connection to CoForceUnderwater integration requires distinguishing continuous remote control from mission dispatch and subsequent result retrieval.

A training concept connecting live, virtual, and constructive environments for repeatable training and mission rehearsal. Constructive simulation models the activity of simulated units or entities; STE extends beyond a 3D display.

Connection to CoForceThe design connects CoSpace simulation, physical-device and mixed trials, and AAR to test AI and heterogeneous-device collaboration. This does not imply a complete LVC training system or integration with the U.S. Army STE program.

Live uses real people and equipment; virtual involves people operating simulated systems; constructive models the activity of simulated units or entities.

Keep in mindLVC describes training environments; STE is a broader direction for connecting them.

Representing a system or phenomenon in a model and exercising it for understanding, testing, or training.

A digital representation linked to a physical counterpart through data, supporting activities such as operation, testing, and maintenance.

Keep in mindA visually similar 3D model without a data connection to the real counterpart is not, by itself, a digital twin.

Reviewing intended and actual outcomes after an activity to identify lessons and improvements.

Connection to CoForceThe design links video, sensors, events, and task history on a shared timeline for review and analysis.

Operating conditions where network access is denied, disrupted, intermittent, or constrained by bandwidth.

Connection to CoForceCentral and field-server deployments treat central-link loss separately from device disconnection. Continuity depends on deployed services, device capabilities, and operating rules.

A communications condition based on a direct propagation path between endpoints, influenced by terrain, obstructions, and antenna height.

Communications beyond a direct line-of-sight path, using options such as satellite links or relays.

Keep in mindBLOS describes reach and communications paths, not guaranteed link quality or uninterrupted operation.

Communications using satellites as a relay path, often supporting wide-area and beyond-line-of-sight connectivity.

The functions that provide position, navigation, and a reliable time reference.

Keep in mindPNT matters not only for location but also for aligning sensors, video, and events in time.

A general term for satellite navigation systems providing positioning and timing; GPS is one GNSS.

A network of mobile nodes that forms routes without relying solely on fixed infrastructure. Range, relay placement, and interference affect connectivity.

Connection to CoForceA candidate field-network approach for devices and local servers. Mesh connectivity alone does not guarantee availability or latency.

An approach to evolving military capabilities through continuous software development, validation, and improvement, rather than relying only on long hardware replacement cycles. It is not a single product specification or certification.

Connection to CoForceShared task rules, device Adapters, and mission agents are intended to build on existing hardware and validate new ways of working together. Updated capabilities are intended to be tested and approved before use.

The ability of different systems to exchange information and work together.

Connection to CoForceShared task and status rules connect through device-specific Adapters. This does not imply STANAG certification or compliance with a particular military standard.

A technical and business approach using modular designs and defined interfaces to support component replacement, evolution, and competition.

Keep in mindAn open system is not the same as open-source software. Interface access and source-code licensing are separate questions.

Commercially available hardware, software, or other products used rather than developed entirely for a single program.

Keep in mindCommercial availability does not establish military suitability; environment, security, and support requirements still need assessment.