Wrapping around the Control Hub are the COGS units – a ring of pluggable modules, each corresponding to a specific data domain or source type. These COGS act as the interface between the  control hub and the external world of data streams.

 

They are termed “COGS” to evoke the idea of gear wheels that can be added or removed; each cog turns data input into a form usable by the hub, and in turn, can also relay outputs or commands outward. The modular COGS architecture is technically significant because it encapsulates domain-specific input/output logic in dedicated units.

​

For example, a video COG handles video feeds from cameras and video streams. One or more video data collectors can ingest RTSP or similar video streams. These collectors feed raw video frames or metadata into the video COGS module. The video COG may perform initial processing such as decoding, frame sampling, or even edge AI tasks (e.g. preliminary object detection at the source).

 

The output from the video COG (video data or detected events) is forwarded to the video perception module in the hub. Video COGs bridge CCTV cameras or video sensors with the central AI, ensuring video data is continuously streamed and analyzed. They may also manage multiple video sources, buffer streams, and handle video-specific protocols, isolating those concerns from the rest of the system.

Other COGs are designed for mobile device and telematics data, human-centric data where privacy is imperative, IoT devices where MQTT is required and event based systems publish discrete events  such as emergency calls or weather warnings.