CoForce.AI
Contact us
DEFENSE AI · MANNED-UNMANNED TEAMING (MUM-T)

Different robots.One sharedmission.

AI-coordinated teamwork for the next generation of defense operations.

CoForce is in development to coordinate sensing, movement, transport, and manipulation across different robots under human-defined objectives and authority. Field conditions and results inform what happens next.

  • Combine device capabilities
  • See the whole mission
  • Adapt to field conditions
Explore CoForceExplore in 3D
ONE SYSTEM. MANY DEVICES.
EXPLORE
01 / CONNECTED CAPABILITIESIN DEVELOPMENT

Individual capabilities. A shared mission.

CoForce connects field devices, mission services, and operator tools around a shared objective. Its design brings role coordination and shared information to manned-unmanned teaming (MUM-T), helping different devices work together under human direction.

SYSTEM OVERVIEW / CONCEPT
01 / FIELD DEVICES

Bring capabilities together

Devices contribute supported functions—movement, sensing, transport, and manipulation—along with video, location, and sensor data.

Device capabilities · Sensor data
02 / MISSION SERVICES

Make the work fit together

Mission services coordinate task order and dependencies across devices, using each result to inform what happens next.

Planning · Assignment · Progress
03 / OPERATOR TOOLS

Decide with the whole picture

Operators review device locations and task progress in one place, with controls to approve, change, or cancel work.

Set goals · Review · Intervene

SDW · SOFTWARE-DEFINED WARFARETurn tested software into new mission capabilities.

CoForce is designed to add new tasks and robot teaming capabilities through software, with changes tested in simulation and field trials before use. This is its approach to software-defined warfare (SDW).

INTEGRATION DOMAINS
Air systems · UAV / UAS
Ground systems · UGV
Surface & underwater · USV / UUV
Fixed sensors & observation
02 / AI COORDINATIONMISSION DECISIONS. LOCAL DECISIONS.

Coordinate the team. Keep people in control.

Mission agents propose assignments and task order using device capabilities and current status. Onboard AI assesses local execution conditions. Operators set objectives and approval rules: a human-machine teaming (HMT) approach with clear roles.

Match capabilities to the work

Roles are assigned around device capabilities and availability, helping operators bring the right capabilities to the mission.

Coordinate the handoffs

The system accounts for task dependencies and shared resources, coordinating handoffs so operators can focus on the overall workflow.

Keep plans grounded in the field

CoEgent, the device-side AI, shares status and execution constraints. When work cannot proceed as requested, that feedback informs the next assignment or sequence.

Keep authority with the operator

Operators set objectives and approval conditions. The system is designed to distinguish delegated work from decisions requiring human input, with options to change or cancel tasks.

How do team planning and onboard decisions work together?See what mission agents and onboard AI each contribute.

Mission agents coordinate the team. CoEgent assesses each request onboard, using device and field conditions. The two roles exchange tasks, status, and results.

When a device reports that work cannot proceed, mission agents reassess task order and assignments.

03 / THE OODA LOOPOPERATIONAL CONCEPT · OODA

From observation to insight. From decisions to coordinated action.

CoForce connects observation, understanding, decisions, and action. AI helps operators make sense of the field and plan tasks. Results from different devices feed the next decision.

Human command and oversight

Operators set objectives and limits, approve or adjust plans, and intervene when needed.

Results feed the next observation

Observation and interpretation continue during execution. Progress, outcomes, and field changes inform revised plans and assignments within operator-defined objectives and approval rules.

ROBOTS · UNCREWED SYSTEMS · FIXED SENSORS

Bring observations together.

Share video, location, and status so operators and AI can work from the same field information. Observations from intelligence, surveillance, and reconnaissance (ISR) feed this workflow.

Explore defense concepts and terminology
04 / SHARED CONTEXT · TESTING · IMPROVEMENTSEE TOGETHER. TEST FIRST. LEARN FROM RESULTS.

Share the picture. Learn through testing and review.

Concept of a shared 2D/3D view of multiple devices and their status
COP · COMMON OPERATIONAL PICTURE

One picture from many sources

A 2D/3D common operational picture (COP) brings device locations, status, observations, and task progress together. Operators can spend less effort reconciling separate views and make decisions from shared context.

Concept of progressive testing with virtual models and physical devices
STE · SYNTHETIC TRAINING ENVIRONMENT

Test the teamwork before field use

Rehearse task plans and device teamwork in the CoSpace simulation environment, then extend toward trials linking physical and virtual systems. This synthetic training environment (STE) approach helps teams examine roles and operating conditions before field use.

Concept of reviewing video, sensor data, and events on a shared timeline
AAR · AFTER-ACTION REVIEW

Use each mission to improve the next

Review video, sensor data, events, and task history on a shared timeline. After-action review (AAR) compares plans with actual outcomes to improve the next training cycle and mission plan.

05 / INTEGRATE & EXTENDCOMMON RULES. DIFFERENT INTERFACES.

Build on your devices. Extend what they can do together.

Build on existing device control and autonomy while connecting tasks across the team. Exchange relevant information with operational systems, and place services centrally or in the field to suit connectivity and local needs.

Concept of connecting different unmanned systems and fixed observation equipment with mission coordination, field services, and external systems

Bring existing device capabilities together

Device Adapters translate shared task requests into device commands and return status and results. This interoperability provides a foundation for testing new devices, tasks, and teaming approaches.

Connect with command and control (C2) systems

Information exchange with command and control (C2) systems is separate from device control. Integration partners agree on the systems, data, and access conditions needed for each operating environment.

Choose a deployment that fits

Plan for denied, disrupted, intermittent, or limited-bandwidth (DDIL) conditions. Place functions centrally or in the field according to onboard capabilities and local processing needs.

How do different devices connect?Follow a shared task request through to a device-specific command.

Mission services request work in a shared format, regardless of device type. The diagram follows that request through device-specific commands and back to a reported result.

SHARED TASKS, DEVICE-SPECIFIC CONNECTIONS / CONCEPT
COFORCEMission services

Request tasks and track progress through common rules

Task requests Status & results
ADAPTERDevice Adapters

Translate between shared rules and device commands and data

DEVICE LINK
INTEGRATION DOMAINS
  • Air systems
  • Ground systems
  • Surface & underwater
  • Fixed sensors & observation
DEVICE INTERFACES

Connect through the interfaces a device provides, such as ROS, MAVLink, or a manufacturer’s SDK/API.

Do you need a field server?A field server is optional. Compare two approaches for your operating environment.

When links are denied, disrupted, intermittent, or bandwidth-limited (DDIL), consider which functions belong in the field. Selected coordination and recording services can run on a field server.

DIRECT TO CENTRAL

Connect without a field server

Devices connect directly to central mission services, with device control and autonomy remaining onboard.

WHEN TO CONSIDER ITCoordination through a connection to central services
Devices↔Central services
WITH A FIELD SERVER

Run selected functions locally

Place selected coordination or recording services on a field server while keeping a connection to central services.

WHEN TO CONSIDER ITConnectivity constraints or local processing requirements
Devices↔Field services↔Central services

Before you get in touch

Integration scope depends on device capabilities, available interfaces, and operating conditions.

Is CoForce ready to deploy or available for a demo?

CoForce is in development. Contact us to confirm current capabilities and whether a demonstration or test is available. We welcome discussions about application fit, device integration, and joint testing.

Can existing devices and their autonomy be used?

We assess the control interfaces, data interfaces, and autonomous functions available on each device. Integration requirements and any necessary changes are reviewed together.

Is a field server required?

No. The choice depends on connectivity and the functions needed in the field.

Compare deployments and connection-loss conditions
What should we prepare for an initial discussion?

Share your objectives, device types and available interfaces, and operating environment. It is fine if some details are undecided; we can identify what to check first and define a joint test scope together.

MISSION FIT · DEVICE INTEGRATION · JOINT TESTING

Explore what your team could accomplish together.

We welcome defense teams, system integrators, and device developers to explore mission fit. Share your objectives, target devices, and operating environment to discuss integration and joint testing.

Contact our teamadmin@teamgrit.kr

Start with a focused integration discussion

  1. Share your goals

    Outline the work, devices, and operating environment.

  2. Review integration needs

    Check device interfaces and the capabilities currently available.

  3. Define a joint test

    Agree on what to evaluate first, test conditions, and responsibilities.

CoForce.AI — AI Robotics Coordination for Defense