Human first. Human last.
AI and automation can organise information, surface gaps and recommend work. Material operational, safeguarding, clinical, legal, financial and safety authority remains with people.
WHY OVERWATCH EXISTS
Better information should strengthen human command.
Operational teams rarely suffer from having no information. They suffer because information is fragmented across calls, radios, maps, messages, spreadsheets, people and different levels of command. Overwatch is designed to bring those fragments into a clearer shared picture without pretending software owns the judgement.
Knowledge becomes operational power when the right people can see the same trusted picture, understand what it means and act at the right level.
Strategic overview. Tactical coordination. Operational delivery.Different levels of leadership need different detail — but they should still be working from one coherent operational picture.
DESIGN RULES
Human first. Evidence first. Useful first.
The platform is designed to assist people under pressure, not create another layer of complexity for them to manage.
Evidence before claims.
We distinguish verified capability from prototypes, concepts and planned integrations. A polished screen is not evidence that an integration is operational.
Useful before complicated.
The controller should be able to understand the situation and act quickly. Intelligence can be sophisticated underneath without making the front end difficult to use.
BUILT FROM LEADERSHIP EXPERIENCE
Designed across strategic, tactical and operational thinking.
ORVIA Overwatch is informed by leadership experience at strategic, tactical and operational levels across different sectors and high-pressure environments. That matters because each level needs a different view of the same situation.
Strategic leaders need direction, risk, priorities and consequences. Tactical leaders need coordination, resources, dependencies and decision space. Operational teams need clear tasks, current hazards, communications and a simple way to report what has changed.
Overwatch is therefore not designed as only a tracking map or only a management dashboard. The goal is a connected operational picture that can support leadership from scene level through coordination and onward to strategic oversight.
S
StrategicPurpose, priorities, wider risk, consequences, resilience, escalation and what leadership needs to know next.
T
TacticalHow objectives will be achieved: resources, sectors, coordination, constraints, competing demands and decisions.
O
OperationalWhat needs doing now: task, location, hazard, capability, status, communication and feedback from the field.
↕
One information loopInformation should move up, down and across the command structure without being repeatedly retyped, stripped of context or trapped in one person's view.
INTEROPERABILITY BY DESIGN
Aligned to the way UK emergency services already think about joint working.
Overwatch is designed to complement — not replace — recognised UK emergency-services command and interoperability models. The design philosophy is informed by the publicly available JESIP Joint Doctrine and NARU ambulance command-and-control guidance: clear communication, shared situational awareness, joint understanding of risk, coordination and structured information.
That means the platform should feel familiar to teams that already work with multi-agency command principles, while remaining usable in other sectors where the same problem exists: several organisations, several information sources and one situation that needs a coherent response.
Important: ORVIA does not claim JESIP or NARU accreditation, approval or endorsement. We are describing design alignment with publicly available doctrine and operational principles.
Communicate clearlyUse plain, understandable information and reduce unnecessary duplication between control, command and field teams.
Co-ordinate activityMake roles, priorities, resources, objectives, ownership and dependencies visible so separate teams can work toward the same outcome.
Shared situational awarenessBuild a common understanding of what has happened, what is happening now, what is likely next and what capability is available.
Joint understanding of riskExpose hazards, assumptions, constraints and risk information so commanders can make proportionate human decisions.
Structured incident informationSupport consistent reporting patterns such as M/ETHANE-style incident information where appropriate and configured.
Joint decision supportPresent information, options and consequences in a way that can support human decision-making and preserve the reasoning behind it.
KNOWLEDGE IS POWER — WHEN IT IS SHARED
Better data is only useful if it becomes better understanding.
The point of Overwatch is not to collect more data for the sake of it. The point is to turn information into a usable operational picture: what is known, what is assumed, what has changed, what is missing, who owns the next action and what decision has been made.
That is why the platform direction combines structured data, location, communications, decision logs and human-authorised tasking rather than treating each as a separate system.
1
ReceiveCall, report, sensor, operator or field update enters the operational picture.
2
StructureInformation is organised by incident, location, time, source, role, resource and status.
3
UnderstandIRIS and the wider data layer can help expose gaps, relationships and possible next questions without taking command away from people.
4
Decide + actThe accountable human sets priorities, authorises consequential tasking and records the reason for the decision.
5
ReviewUpdates, outcomes and decision history remain available for handover, learning, assurance and recovery.
PART OF ORVIA
Separate enough to sell clearly. Connected enough to work properly.
Overwatch has its own product identity because command, tracking and operational communications are a distinct buyer problem. Underneath, it is designed to work within the wider ORVIA architecture rather than become another silo.
- ORVIA Oversight remains the parent organisation.
- Command is the controller and operational coordination surface.
- Track provides location-aware field and asset context.
- PTT provides the operational communications direction.
- IRIS is the intelligence and conductor layer.
- ARIA is the voice and access layer.
- VERA / Hive represents the governed truth and persistence direction.
CommandSituation, objectives, roles, actions, resources, decisions and recovery.
TrackTeams, vehicles, hazards, zones, rendezvous points and geospatial context.
PTTField and control-room voice, with contextual linkage where configured.
IRIS + ARIAIntelligence/conductor plus voice/access — assisting people rather than replacing accountable command.
VERA / HiveGoverned records, status history, decisions and provenance direction.
ORVIA OversightWider governance, evidence, VITA and organisational understanding around the technology.
PRACTICAL OPERATIONAL THINKING
Keep the essential command loop visible.
Situation → objectives → people and roles → resources → authorised tasking → decisions → updates → recovery → review.
The platform should support that loop, not bury it underneath technology. Darren is credited for operational workflow design contribution; ORVIA's implementation is being developed as its own governed platform rather than reproducing an organisation-specific external application.
Human authority boundary
Recommendation is not command.
A system can identify a nearby resource, a gap in the picture or a possible course of action. It cannot know every operational constraint. Capability, readiness, current tasking, residual coverage, local rules and command judgement still matter. The accountable human decides.
TEST IT AGAINST REALITY
Judge Overwatch against a real operational problem.
Bring us the workflow, incident structure or multi-agency problem you need to improve. We will show the relevant platform layers and be clear about what is live, what is configured and what remains in development.