From DORI to OODPCVS: what the new video surveillance standard means for your CCTV system
For years, DORI (Detection, Observation, Recognition, Identification) gave the security industry a shared language for defining what a camera needed to achieve at a given distance. It worked well, and it still shapes how many installers and consultants specify today.
But surveillance technology, operational requirements and the environments cameras are deployed into have all moved significantly since DORI was established. The European standard has now been updated to reflect that, replacing the legacy DORI framework with a more granular approach: OODPCVS (Overview, Outline, Discern, Perceive, Characterise, Validate, Scrutinise).
Whether you specify CCTV systems for a living or you manage security at a school, stadium, warehouse or public space, this blog explains what has changed, why it matters and how to apply the new standard in real-world applications.
What DORI was and why it worked
DORI defined four performance levels for video surveillance, each describing what an operator could achieve with the captured image at a specific pixel density per metre:
- Detection confirmed that something was present in the scene (a person, vehicle or object) without details about what it was doing. Pixel density: 25 px/metre.
- Observation gave enough detail to assess behaviour: a person crouching at a fence line, a vehicle reversing into a restricted bay. Pixel density: 62 px/metre.
- Recognition allowed operators to distinguish one individual from another or confirm a vehicle type. Pixel density: 125 px/metre.
- Identification produced footage detailed enough to confirm who a person was to an evidential standard. Pixel density: 250 px/metre.
Each level was tied to a pixel density threshold, giving consultants and installers a calculable, defensible basis for camera selection, mounting height and positioning. For many projects, DORI provided a consistent way to express performance requirements without vague language.
The framework was widely adopted across the UK and Europe, shaping how CCTV security cameras were specified for town centres, campuses, perimeter deployments and high-security sites.
Why DORI has been replaced with OODPCVS
DORI was developed when the primary question was: Can an operator identify what they are looking at? That still matters, but it is no longer the whole question.
Modern CCTV security cameras do far more than capture images for human review. They feed analytics platforms, trigger automated alerts, count people and vehicles, and support real-time behavioural assessment. DORI had no framework for any of that. It also did not account for the gap between a camera that meets a pixel density threshold under ideal conditions and one that can actually support an operational decision at night, in poor weather or at long range across a perimeter CCTV installation.
OODPCVS addresses those gaps. The new framework adds levels below Detection and above Identification, mapping more precisely to what surveillance systems are now expected to deliver. It also aligns with how a modern surveillance setup is actually used: not only by operators reviewing footage after an incident, but by analytics engines making real-time decisions.
The standard is defined within the European EN 62676-4, which covers video surveillance systems. Specifiers working to this standard now have a more complete toolkit for expressing what a system must achieve, and for holding delivered systems to account.
What each level of OODPCVS means in practice
The seven levels sit on a scale of increasing image detail and operational capability. Pixel density requirements increase at each level, with direct implications for lens choice, sensor size and camera placement.
1. Overview
Something is present and moving. No meaningful detail about what it is. Used for wide-area situational awareness, including open ground on large industrial sites or outer approaches on a perimeter CCTV system. Pixel density needed: 3 px/face to 20 px/metre.
2. Outline
General direction and orientation of movement can be determined. Used for tracking movement across public spaces, transport hubs and large campus environments where direction is operationally significant. Pixel density needed: 6 px/face to 40 px/metre.
3. Discern
A specific type of object can be confirmed, whether a person rather than an animal or a vehicle rather than a trolley. Supports alert triage in analytics systems and alarm verification at perimeter CCTV fence lines. Pixel density needed: 12 px/face to 80 px/metre.
4. Perceive
Behaviour and attributes can be assessed, such as whether someone is carrying an object, moving quickly or acting in a way that warrants a response. Used at loading areas, access routes and fence line confirmation points. Pixel density needed: 20 px/face to 125 px/metre.
5. Characterise
Person type, gait, behaviour and vehicle category can be identified. Relevant for incident response, assessing individuals at access routes and building entrances, and vehicle feature analysis. Pixel density needed: 40 px/face to 250 px/metre.
6. Validate
Specific features can be confirmed, including vehicle make and colour, clothing description and physical build. Used for incident follow-up and response briefing. Pixel density needed: 80 px/face to 500 px/metre.
7. Scrutinise
The image must support confident identification of an individual to an evidential standard. Required at gate entry points, custody suite entrances and any location where footage may be used as evidence. Pixel density needed: 240 px/face to 1500 px/metre.
What this means for CCTV installers and security consultants
OODPCVS changes the starting point for every CCTV system specification conversation. DORI gave you four outcomes to target; now you have seven, with more precise operational definitions at the lower end of the scale.
That means more specific questions need to be asked of the client before camera positions are proposed.
The practical implication is that you need to map each zone of a site to the level it actually requires, rather than applying a single standard across the whole project. A wide-area approach zone on a large industrial site may only need Overview or Outline, while a gate or entry control point needs Scrutinise. Getting that mapping right has direct consequences for lens choice, mounting height and whether a fixed or pan-tilt-zoom (PTZ) camera is the right tool for each location.
Pixel density calculations remain at the heart of OODPCVS compliance, but the thresholds differ from DORI, so existing calculation workflows will need updating. Camera manufacturers and analytics vendors are beginning to publish OODPCVS-aligned datasheets, but specifiers should verify rather than assume that legacy documentation has been updated.
Acceptance testing should now also be structured around OODPCVS outcomes. For each camera, document the required level, the calculated pixel density at the target distance and the test scenario that proves the level is met under the conditions the site actually experiences, including at night and in adverse weather. This protects you professionally and protects the client operationally.
For projects involving public sector CCTV or high-security CCTV cameras, where procurement documentation, compliance evidence and post-incident scrutiny are heightened, OODPCVS alignment is increasingly a procurement expectation rather than a best-practice recommendation. Specifying high-security CCTV cameras without OODPCVS mapping leaves the delivered system open to challenge if performance at a specific location is later questioned.
What you need to ask your CCTV installer
If you manage security at a school, hospital, retail site, stadium or transport facility, you don’t need to know the pixel density thresholds behind OODPCVS. But you do need to know that the standard your CCTV system is specified against directly affects whether it can do what you need it to do.
The most useful thing OODPCVS gives you is a vocabulary for expressing requirements precisely. Rather than asking for ‘good coverage of the car park,’ ask your installer which OODPCVS level is being designed for in each zone, and why. That question will quickly reveal whether the specification has been tailored to your operational needs or applied as a generic template.
Two other practical questions to put to your installer include:
- What OODPCVS level has each camera been designed to achieve, at what distance, and under what lighting conditions?
- Has the specification been tested against realistic night-time scenarios, not just daytime commissioning?
A CCTV system designed and tested against OODPCVS gives you a measurable, defensible basis for knowing your investment delivers what it promised.
Applying OODPCVS across different video surveillance applications
Required levels vary significantly by sector, and every site will need its own zone-by-zone mapping. Think about the decisions your system needs to support, for example:
- For town centre CCTV, wide pedestrian areas typically need Outline or Discern to track movement and direction, while known incident locations, transport interchanges and access control points require Validate or Scrutinise.
- At a school or college, you may need Validate-level footage at entrances to confirm visitor identity during a safeguarding incident, but the playing fields behind the building may only need Overview or Outline.
- A retail or commercial environment needs Characterise-level detail at entrances and public areas to assess person type and behaviour, whereas Scrutinise is required at till points, stockrooms and exit points for evidential footage.
- Sports and leisure venues follow a similar pattern: Discern across concourses during peak attendance, with Scrutinise at turnstiles and sensitive access routes.
- A transport or highways site needs Outline and Characterise for flow monitoring and incident detection, with Scrutinise at enforcement and incident-recording locations.
- For industrial sites, remote perimeter CCTV zones typically need Discern and Perceive for alarm triage, with Scrutinise reserved for access points and security checkpoints.
- High-security sites, including those requiring military CCTV systems and other high-security CCTV cameras, typically need the full range: Overview and Discern across outer approaches, Perceive across internal routes and Validate and Scrutinise at access control points and gates.
Redvision security cameras for an OODPCVS-compliant CCTV system
Redvision is a specialist UK CCTV camera manufacturer with over 25 years of experience, designing and building CCTV security cameras for the full range of environments covered by OODPCVS, from public sector CCTV in town centres to extreme environments, industrial sites and high-security perimeters.
The rugged X-SERIES PTZ cameras are built for deployments where a CCTV system needs to achieve multiple OODPCVS levels across a single site, using optical zoom to move between wide-area Overview capability and close-in Scrutinise-level footage.
All Redvision cameras are ONVIF and NDAA compliant, so you can specify your system with complete confidence.
If you’re updating your specification approach to align with OODPCVS or want guidance on which cameras are best suited to the levels your project requires, speak to our team today at sales@redvisioncctv.com.