01 / FIELD DEVICES
Bring capabilities together
Devices contribute supported functions—movement, sensing, transport, and manipulation—along with video, location, and sensor data.
AI-COORDINATED ROBOTICS FOR DEFENSE
Different robots.One sharedmission.
CoForce is an AI-enabled system in development for coordinating different robots in defense operations. It brings sensing, movement, transport, and manipulation together around operator-defined goals, with a shared view of field conditions and mission progress.
- Combine device capabilities
- See the whole mission
- Adapt to field conditions
ONE SYSTEM. MANY DEVICES.
01 / CONNECTED CAPABILITIESIN DEVELOPMENT
Individual capabilities. A shared mission.
CoForce brings field devices, mission services, and operator views into one system. It connects device capabilities and field information so individual tasks can contribute to the whole mission.
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.
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.
Beyond a shared screen. Toward coordinated work.
CoForce connects device roles and task sequences, using results to coordinate the next step—not just show device status.
INTEGRATION DOMAINS
Air systems
Ground systems
Surface & underwater
Fixed sensors & observation
Air systemsGround systemsSurface & underwaterFixed sensors & observation02 / AI COORDINATIONMISSION DECISIONS. LOCAL DECISIONS.
Coordinate the team. Keep people in control.
CoForce considers device capabilities, task order, and whether work can proceed. Operators set objectives and autonomy limits, with approval required for designated decisions.
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.
TEAM AI · MISSION AGENTCoordinate tasks across the teamDevice assignments · Task order · Shared resources
Tasks & constraints →← Status & results
ON THE DEVICE
ONBOARD AI · CoEgentAssess task feasibility using device and field conditionsDevice functions: movement, sensing, manipulation
Operators define autonomy limits and approval rules. This division of roles works with each device’s own control and autonomy functions.
03 / ADAPTIVE OPERATIONSOBJECTIVES. ACTION. FEEDBACK.
When conditions change, the mission plan can change too.
CoForce feeds results and field conditions back into the plan. Objectives, assignments, execution, and review stay connected so operators can follow the mission as it evolves.
OPERATOR01 / 04
People define the mission.
Operators set the objective, operating area, task conditions, and approval rules. AI uses these to prepare the task plan.
OPERATORS CAN APPROVE OR INTERVENE AT EVERY STAGE
04 / MONITOR, TEST & REVIEWSHARED VIEW. TESTING. REPLAY.
Understand the mission. Prepare for the next one.
Decide from a shared view
Device locations, status, sensor data, and task progress come together in a 2D/3D common operating picture (COP), giving operators shared context for decisions.
Build confidence before field use
Testing progresses from simulation to physical devices and mixed environments. Each stage helps assess integration and mission workflows before field deployment.
Make the record useful
Video, sensor data, events, and task history can be replayed on a shared timeline. After-action review (AAR) helps teams investigate what happened and identify improvements.
05 / INTEGRATE & EXTENDCOMMON RULES. DIFFERENT INTERFACES.
Build on your devices. Extend what they can do together.
Integration starts with the connections existing and new devices provide, and the information needed from command and data systems. Connectivity and local processing needs guide where functions run.
Accommodate different device interfaces
Device Adapters translate shared task requests into device-specific commands and return status and results. Integration scope depends on the connections and capabilities each device provides.
Connect with existing operational systems
External command and data systems connect separately from device control. The information exchanged is defined for each operating environment.
Choose a deployment that fits
Functions can run centrally or, where needed, on a field server. Connectivity and local processing needs guide the setup.
How do different devices connect?Follow a shared task request through to a device-specific command.
Mission services use shared task rules. Device Adapters translate requests into the commands and data formats each device uses, then return status and results.
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.
Choose service placement around connectivity and the functions needed in the field. A field server is not required in every deployment.
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
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 integration around the control and data interfaces, and autonomous functions, that a device provides. Support is not automatic for every device; prerequisites and any required changes need to be 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 conditionsWhat 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.
Start with a focused integration discussion
Share your goals
Outline the work, devices, and operating environment.
Review integration needs
Check device interfaces and the capabilities currently available.
Define a joint test
Agree on what to evaluate first, test conditions, and responsibilities.