ORVIA Command
The controller surface for incidents, objectives, roles, tasks, resources, decisions, recovery and review.
- Current operating picture
- Actions + owners
- Resource allocation review
- Decision trail
COMMAND-LED OPERATIONAL PICTURE
See the operation. Command the response.
Overwatch brings incidents, objectives, resources, field positions, communications and decisions into one governed operating picture — while keeping consequential tasking with a human controller.
Command is the control surface. Track adds geospatial context. PTT carries operational voice. IRIS and ARIA help organise information. VERA / Hive provides the governed record beneath it.
ORVIA COMMAND · CURRENT OPERATING PICTURE
3 active issues8 resources visibleHuman authority on
Team Alpha · READYRVP North · OPENPriority task · REVIEW
Current situationStructured summary of what is known, what changed and what is still unclear.Last update 22:14
ObjectivesProtect people · Stabilise incident · Preserve coverage · Record decisions.
ResourcesCapability, readiness, location and current tasking reviewed before allocation.
Decision logController actions and rationale kept in the operational record.
01 · ORVIA COMMAND
The controller surface for the whole operation.
Command is designed to answer the questions a control room actually needs to answer: What is happening? What matters most? Who owns it? What resources are available? What has been decided? What is still unresolved?
It can support multiple concurrent incidents or workstreams while keeping human authority visible. The platform can suggest, organise and surface information; the controller decides what gets tasked.
Incident + situation pictureCurrent issue, status, objectives, roles, sectors, hazards, dependencies and latest update in one place.
Actions + ownersVisible tasks, priority, assigned owner, due state and whether the action is open, blocked or complete.
Resource readinessCapability, location, current tasking and readiness reviewed before a human authorises allocation.
Decision logTimestamped operational decisions and rationale so the record can be reviewed later, not reconstructed from memory.
Concurrent operationsRun several incidents or operational threads without forcing everything into one undifferentiated board.
Recovery + reviewMove from response into stabilisation, recovery, close-out and after-action learning without losing the operational trail.
FROM FIRST REPORT TO ACCOUNTABLE CLOSE-OUT
A simple front end with human control at the important points.
Overwatch is intended to reduce fragmentation, not add another layer of complexity. The controller gets a current picture; the system keeps the evidence and status underneath it.
01
Receive
A report, call, operator update or field message enters the operational picture.
02
Understand
Build the current situation, expose gaps and identify what must be verified.
03
Decide
The human controller sets priorities, objectives and operating intent.
04
Task
Resources are reviewed and explicitly authorised for consequential allocation.
05
Record + review
Updates, outcomes and decisions remain visible for recovery, governance and learning.
THE OVERWATCH MODULES
Command in the centre. Specialist layers around it.
Use only what an operation needs, or join the modules into a common operating picture. Capabilities that are still directional or customer-configured are described that way rather than being presented as universally live.
ORVIA Track
The geospatial layer for teams, vehicles, hazards, zones, RVPs, objectives and field context.
- Common operational map
- Field positions + status
- Zones + hazards
- ATAK-compatible direction of travel
ORVIA PTT
Operational voice across field and control environments, designed to work alongside existing communications rather than forcing one hardware estate.
- Field + control-room use
- Configurable talkgroups
- Cross-platform direction
- Record linkage where configured
IRIS + ARIA
IRIS is the conductor/intelligence layer. ARIA is the voice/access layer. They help prepare, organise and communicate information while consequential decisions stay human-authorised.
- Missing-information prompts
- Situational synthesis
- Voice + communication assistance
- Recommendation support
HOW THE ORVIA SYSTEM JOINS
Operational simplicity at the front. Governed truth underneath.
Overwatch is part of the wider ORVIA architecture. The design direction is for each layer to do one clear job rather than making one interface pretend to be everything.
ARIAVoice and access layer. Receives or supports communications where configured.
→
IRISConductor/intelligence layer. Organises context, gaps and recommended next steps.
→
COMMANDHuman operational control surface for priorities, objectives, tasks and decisions.
→
VERA / HIVEGoverned record layer for canonical incidents, resources, actions and status history.
Evidence-first status rule: the diagram explains the architecture and direction of travel. It does not mean every integration is automatically enabled for every deployment. Customer-specific connections are only represented as live once configured and verified.
WHERE COMMAND FITS
Built around real control-room decisions.
Maintain one current picture across issues, sectors, teams, actions and resources while preserving a decision trail.
COMMAND + TRACK + PTTSee teams, vehicles, hazards and objectives in context, then keep tasking explicitly human-authorised.
TRACK + COMMANDUse the same controller logic for non-emergency work: current situation, ownership, dependencies, actions and recovery.
COMMAND + IRISSEE THE PLATFORM WORKING AS ONE
Put your own operation on the screen.
We can demonstrate Command, Track and the wider Overwatch model using your terminology, roles and operating structure so you can see what adds value before any deployment decision.