Skip to content
Labs
Sign inRequest a demo

RCC platform

Built as one platform, not a bundle of products

Five parts, one identity, one event model and one audit trail. Every RCC solution plugs into the same core, so adding a solution never adds another system to run.

Book a control-room walkthroughSolutions
The layers of RCCFive layers stacked from your systems at the bottom through RCC Edge, RCC Core and RCC AI to RCC Command at the top, with data rising through them.Your systemscameras, doors, alarms, sensors, business systemssourcesRCC Edgeingest, recording and analytics next to the camerascaptureRCC Coreevents, workflows and SOPs, maps, identity, auditconnectRCC AIanalytics, copilot and plain-language searchexplainRCC Commandoperators, supervisors, video walls, field teamsoperate
  1. RCC Edge captures next to the cameras and keeps a site working on its own.
  2. RCC Core connects every event, workflow, identity and record.
  3. RCC Command is where people work; RCC Studio configures it all.

The parts

Studio, Command, Core, AI and Edge

  • RCC Studio

    Administrators set up every site, camera, rule and SOP from one place.

    • Sites, servers, roles and licences
    • Cameras, recording and analytics policies
    • SOP and workflow authoring
    • Upgrades from signed releases

  • RCC Command

    Operators see each alarm with its video and work it through to a close.

    • Live monitoring and video walls
    • Maps, incidents and investigations
    • Dispatch, push-to-talk and broadcast
    • Shift handover and supervision

  • RCC Core

    Every solution shares one event model, so nothing needs another integration.

    • One event model and fabric
    • Workflow and SOP engine
    • GIS, insights and KPIs
    • Identity, licensing, governance, audit

  • RCC AI

    Operators get answers and drafts with their sources attached.

    • Investigation summaries and shift briefings
    • Plain-language search
    • Every sentence cited to its evidence
    • Agent runs recorded in the audit trail

  • RCC Edge

    Sites keep recording and analysing next to the cameras, even offline.

    • Ingest and recording
    • Video analytics in cells
    • Device and camera configuration
    • Keeps working when the link is down

  • Federation

    Head office sees every site, and each site still runs on its own.

    • Each site autonomous
    • One view in RCC Command
    • Events catch up after outages
    • Cross-site correlation

RCC Studio

Configure every site from one place

Studio’s home groups a site’s infrastructure, devices, roles, security and governance under one search, beside the site’s health and the items that need attention.

RCC deployment
RCC Studio home for site HQ-Bengaluru: a searchable index of every setting, grouped into site and platform, devices, roles and deployments, security and governance, beside a summary of the site’s devices, seats, licence and guardrails and the items that need attention.

Workflows and SOPs

Your procedures, run the same way every time

Workflows chain on any event: decision and acknowledge steps by role, waits for other events, and a dry run on real history before a rule goes live. SOPs written in RCC Studio guide operators step by step in RCC Command.

A rule fires a workflow, which guides an operator through an SOP and records each stepFour stages run left to right: an event, a versioned rule, the workflow with its steps, and the audit record.eventany solutionruleversioned · dry runworkflowdecide · acknowledgeauditevery step
  1. Rules are versioned and tested on real history before they go live.
  2. Workflow steps are assigned by role and wait for the events they need.
  3. Every step, decision and reason is recorded.

Federation

Every site on its own feet, every site in one view

Each site runs RCC on its own servers and keeps recording, analysing and deciding when its link to the centre fails. RCC Command shows the whole estate, and events catch up when links return.

Sites reporting to one RCC command centre, one of them working offlineFive sites are linked to RCC Command in the middle; events travel from each site to the centre. One site’s link is down, and it keeps recording locally.Head officevideo · accessPlant 2PPE · zonesWarehousedocks · yardsDepotfleet · gatesBranch 14alarms · videolink down · recording locallyRCC Commandone estate
  1. Every site runs on its own servers.
  2. Events and their video reach central command.
  3. A site whose link fails keeps working and catches up later.

RCC AI

Analytics, copilot and search on one layer

RCC AI sits between RCC Core and RCC Command. Analytics are placed on servers beside the cameras, and the copilot works over the same events and records operators see, with every run audited.

QuantineliQ AI

  • Analytics in cells

    Each analytic is placed on a cell with the right model and hardware; more servers add more cells.

  • A copilot over the record

    Summaries and briefings drawn from the incident record, each sentence citing its source.

  • One search for everything

    Questions in plain words across video, events and records, with the translation shown first.

  • A model lab

    Datasets, training, evaluation and deployment for your own models.

Open by design

Standards RCC speaks

ONVIF S · G · TRTSPWebRTCBACnetModbusOPC UAKNXMQTTSparkplug BLoRaWANSIA DC-09OSDPCAP 1.2NTCIPOCPINGSI-LDSensorThingsOIDCSAML 2.0SCIMML-KEMML-DSA

See the platform working

A walk through RCC Studio and RCC Command on your own use case.

Book a control-room walkthroughDeployment