TORUS-CCISRT turns a facility sensor network into actionable security and infrastructure awareness. It ingests the prioritised event streams from every TORUS-MEG gateway, fuses them into a single geospatial common facility picture, and presents that picture to two kinds of operator at once: the teams monitoring from the security operations center, and the facility response staff acting on campus. 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: AI/HPC data center campuses are rehearsed as digital twins in NVIDIA Isaac Sim, and the validated plan (node positions, gains, alarm policies) is promoted straight into the live facility picture.
| Area | Capability |
|---|---|
| Security | Live common facility picture; node/mast state; thermal & video tiles cued by events |
| Detection | Fusion of seismic, acoustic, visual, and roadmap drone / UAS cues into single tracks with confidence |
| Inspection | On-demand sensor cueing, snapshot requests, and mast slew-to-cue from the operations center or campus |
| Infrastructure | Timeline, forensic replay, operating patterns, and event history across the facility deployment |
| Control | Node configuration, gain and threshold policy, alarm rules, arm/disarm zones |
| Response | Transducer command for facility response actuation under safety interlock - arm, safety-validate, then trigger; trigger refused until validation passes; every action audited |
| Tier | Pre-deployment rehearsal in Isaac Sim; promote a TIA-942 and OCP-aligned plan to the live picture |
| Collaboration | Multi-operator, role-based access, shared annotations, hand-off between security and facilities teams |
| Integration | Northbound integration API with PSIM, DCIM, BMS, VMS, SIEM, and Redfish adapters |
| Aspect | Approach |
|---|---|
| Hosting | On-premises or private cloud; fully air-gapped option for high-security facilities |
| Display system | Security operations center video wall + operator workstations; browser-based clients |
| Campus clients | Android tablets / handhelds for facility response workflows |
| Security | Role-based access control, encrypted transport, signed updates, full audit log; TIA-942 and OCP-aligned evidence exports |
| Resilience | Store-and-forward at the gateway; the campus response 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 operations-layer ready today; the operator applications, northbound API adapters, and fusion core are the next build phase after the facility sensing hardware is finalised. PacketFive Design Services can adapt TORUS-CCISRT workflows and integrations for other customer requirements.
TORUS is an independent platform. Company, product, and system names referenced in this document (including but not limited to NVIDIA (Isaac Sim), and any third-party PSIM, DCIM, BMS, VMS, SIEM, or Redfish 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.