TORUS-CCISRT turns a field of sensors into a decision. It ingests the prioritised event streams from every TORUS-MEG gateway, fuses them into a single geospatial common operating picture (COP), and presents that picture to two kinds of operator at once: the coordinators planning and watching from an operations room, and the field operators acting on the ground. Both see the same live state; each sees it in the form their job needs.
The same environment is used before deployment, not just during it: sites are rehearsed as digital twins in NVIDIA Isaac Sim, and the validated plan (node positions, gains, alert policies) is promoted straight into the live C2 picture.
| Area | Capability |
|---|---|
| Surveillance | Live common operating picture; node/mast state; thermal & video tiles cued by events |
| Detection | Fusion of seismic, acoustic, and (roadmap) visual/air cues into single tracks with confidence |
| Reconnaissance | On-demand sensor cueing, snapshot requests, and mast slew-to-cue from the room or field |
| Intelligence | Timeline, forensic replay, pattern-of-life and event history across the deployment |
| Control | Node configuration, gain and threshold policy, alert rules, arm/disarm zones |
| Transducer | Effect-node command under a safety interlock: arm, safety-validate, then trigger; trigger refused until validation passes; every action audited |
| Planning | Pre-deployment rehearsal in Isaac Sim; promote validated plan to the live picture |
| Collaboration | Multi-operator, role-based access, shared annotations, hand-off room↔field |
| Integration | API and standard messaging to push tracks to existing C2 / SIEM / VMS systems |
| Aspect | Approach |
|---|---|
| Hosting | On-premises or private cloud; fully air-gapped option for high-security sites |
| Display system | Operations-room video wall + operator workstations; browser-based clients |
| Field clients | Rugged Android tablets / handhelds; interoperable with ATAK-style workflows |
| Security | Role-based access control, encrypted transport, signed updates, full audit log |
| Resilience | Store-and-forward at the gateway; the field app degrades gracefully when offline |
TORUS-CCISRT is at concept / design-study stage. The node-side event schema is defined so that TORUS-SN and TORUS-MEG are C2-ready today; the operator applications and fusion core are the next build phase after the ground domain hardware is finalised.
TORUS is an independent platform. Company, product, and system names referenced in this document (including but not limited to NVIDIA (Isaac Sim), ATAK, and any third-party C2, VMS, or SIEM products) are used solely for descriptive, engineering, and interoperability identification. Their use does not imply any affiliation with, sponsorship by, or endorsement by those companies or projects. Supply or licensing of any such third-party product to the designers, integrators, operators, or evaluators of the TORUS platform remains at the sole discretion of the respective owning company, organisation, or legal entity. All trademarks are the property of their respective owners.