PRIZM 4.0DSTA
Viewing C3 design language
Command and Control

PRIZM for C3 systems

The C3 design language emphasises density, high contrast, and operator clarity. Built for tactical interfaces, real-time data, and low-light environments.

Extension packs

Some C3 products are specialised — flying an autonomous robot swarm, fusing an ISR sensor picture, running an electronic-warfare console. Each reaches beyond the general PRIZM system, with capabilities that need their own organisms and a distinct visual and interaction treatment, not just a recolour of the base.

An extension pack is how PRIZM serves a specialised product without fragmenting into separate design systems. It extends the C3 base rather than forking it: the same foundations, tokens, and component primitives carry through unchanged, and the pack adds only what is genuinely unique — a recognisable identity and a set of domain-specific organisms. Specialisation where the product needs it; one shared system everywhere else.

RC3

Robotics & Autonomy

One vocabulary for command and control across the full spectrum — single-platform teleop to swarm and mission-level intent. Signature organisms for safety, comms, autonomy, telemetry, fleet roster, and live 3D perception.

Explore the pack

A pattern, not a one-off

RC3 is the first extension pack, not a special case. A single data-pack attribute switches a pack on, so the next specialised C3 product — counter-UAS, for instance — gets its own identity and organisms through the same mechanism.

Thick-client delivery

Not every C3 surface is a web app — operator consoles often run as native desktop software. C3 ships for that too: a parallel JavaFX library for thick-client applications, rendered natively rather than in a browser.

The design language is shared, not duplicated. The colour tokens are derived from the same canonical source, and the controls are in spec parity with their web counterparts — C3 and its extension packs only.