EN 62676-4:2025 OODPCVS Update Explained (2026)

What changed in EN 62676-4:2025

EN 62676-4 is the European harmonisation of IEC 62676-4 — the international standard that defines how to specify and verify the visual performance of video surveillance systems. The 2014 edition crystallised the four DORI categories (Detect 25, Observe 62.5, Recognize 125, Identify 250 px/m) into the language we have used for a decade. The 2025 amendment does not throw DORI out; it extends it. The headline change is OODPCVS: a parallel seven-step pixel-density ladder that adds three coarser steps below DORI Detect and two finer steps above DORI Identify.

For a CCTV designer, the practical implication is concrete. A bid response in 2026 that simply lists DORI distances ("Identification at 6 m, Recognition at 12 m") will increasingly be flagged incomplete by procurement officers working from EN 62676-4:2025 specifications. The expected response is now framed in OODPCVS terms — "Characterise at 12 m, Validate at 6 m, Scrutinise inside the access vestibule" — because the new ladder lets the tender specify both lower thresholds (Overview/Outline) for wide-area awareness and higher thresholds (Validate/Scrutinise) for biometric capture that DORI Identify alone could not address.

The 2025 update also tightens acceptance testing language. Where the 2014 edition accepted photographic evidence at the four DORI thresholds, the 2025 edition expects each OODPCVS level claimed in the design to be verifiable with a documented pixel-per-metre measurement on the target plane. Two new tiers — Validate (500 px/m) and Scrutinise (1500 px/m) — require purpose-built test targets because they sit far above what a typical commissioning checklist used to demand.

Pre-2025 baseline: the DORI refresher

Before we walk through the seven new modes, the four classic DORI categories deserve a quick refresher because every OODPCVS mode is built on the same pixels-per-metre arithmetic.

Detection — 25 ppm: enough pixels to detect that a person or object is present.
Observation — 62 ppm: enough pixels to characterise (clothing colour, body posture, vehicle type).
Recognition — 125 ppm: enough pixels to recognise a known individual or vehicle.
Identification — 250 ppm: forensic-grade pixels — license plates, faces, evidence quality.

These four numbers do not change in the 2025 amendment. OODPCVS sits next to them: at the lower end it adds Overview (20), Outline (40) and Discern (80) for general awareness and category-distinction cameras; in the middle Perceive (125) and Characterise (250) overlap numerically with DORI Recognize and Identify; at the top Validate (500) and Scrutinise (1500) cover facial verification and passport-grade capture that DORI never specified.

The seven OODPCVS pixel-density levels

Overview — 20 px/m

Overview is the lowest tier on the OODPCVS ladder — coarser even than DORI Detect. It supports situational awareness only: motion is visible, scene activity is legible at a glance, but the camera cannot confirm what kind of object is moving. Wide-area cameras on transport hubs, large car parks and crowd-watch positions live at this density. Acceptance is satisfied when the operator can answer "is the scene normal right now?" without further interpretation.

Outline — 40 px/m

Outline sits halfway between Overview and DORI Detect. The pixel count is enough to resolve coarse object shapes — a standing figure versus a parked vehicle versus a trolley — but not enough to classify the object reliably. Common targets: bay-level coverage in logistics yards, gate approach in industrial sites, peripheral fields of view on a PTZ used primarily for human guidance.

Discern — 80 px/m

Discern is the new mid-low tier that the 2014 ladder skipped entirely. At 80 px/m an operator can reliably distinguish object categories — person from cart from forklift — and broad activity types like walking, running, loading. Retail aisles, transport platforms and the middle bands of perimeter cameras typically fall here. Behaviour-analytics models trained on full-body posture also degrade gracefully at this density.

Perceive — 125 px/m

Perceive is numerically the same as DORI Recognize. The pixel count lets a trained operator read posture and behaviour — gestures, gait, hand position, body language — and recognise a familiar person without forensic certainty. The 2025 amendment keeps the 125 px/m floor unchanged but renames the tier so AI-assisted behaviour-analysis tooling (which routinely measures the same density requirement) has a consistent label across human and machine workflows.

Characterise — 250 px/m

Characterise overlaps numerically with DORI Identify. At 250 px/m a known person can be reliably matched and a European licence plate can be read by an operator. This is the threshold most pre-2025 specifications quote as the evidentiary minimum, and the 2025 amendment keeps it unchanged. The renaming reflects that the workflow at this density is not always identification of strangers — characterisation includes matching repeat visitors, recognising staff, attributing actions to a known individual.

Validate — 500 px/m

Validate is the first OODPCVS tier above the legacy DORI ceiling. 500 px/m is the typical floor for facial-verification systems (1:1 matching against a stored reference) and for high-confidence automatic number-plate recognition (ANPR) at non-axial angles. Border control e-gates, access-control face-on terminals, toll-road ANPR rigs and bank-vestibule capture cameras specify Validate when DORI Identify is not sufficient. Acceptance testing requires a calibrated face-target chart or a known-plate plate at the design distance.

Scrutinise — 1500 px/m

Scrutinise is the top of the OODPCVS ladder — passport-grade biometric capture. 1500 px/m implies very long focal lengths or very short target distances, and is almost never specified outside critical-infrastructure projects: passport-issuance booths, forensic interview rooms, high-security ID enrolment, customs primary-inspection booths. Reaching Scrutinise on a fixed camera typically requires 4K resolution with a 25 mm or longer lens and a target window less than two metres wide.

How modern CCTV design tools should support OODPCVS

A design tool that takes EN 62676-4:2025 seriously needs to do three things. First, every camera must be taggable with one or more OODPCVS modes alongside its DORI level — the data model has to allow both. Second, the tool should be able to render an OODPCVS-aware floor plan: not just a pie-slice FOV but a coloured zone showing where each mode is satisfied. Third, the tool must export the OODPCVS labels into the deliverable PDF so the procurement officer reading the bid response sees the same vocabulary the tender used.

A common mistake is treating OODPCVS as a label-only feature — adding a dropdown but not adjusting any of the rendering or export logic. That fails real-world acceptance because the tender now expects the supplier to demonstrate each level claimed, not just claim it. Tools that pass the test in 2026 carry the OODPCVS level all the way from the camera object through the FOV-cone overlay to the BOM and the PDF deliverable.

Implementation in CCTVplanner

CCTVplanner ships with three complementary entry points for OODPCVS-aware design. The DORI calculator at /calculator/dori gives you the underlying pixel-density maths for the four classic levels. The new OODPCVS calculator at /calculator/oodpcvs runs the same maths for the seven new levels (Overview through Scrutinise) in parallel. The standards-aware calculator at /en-62676-4-calculator wraps both ladders in tender-grade language: pick the target distance, the camera resolution and the focal length, and the calculator returns the highest level each candidate camera satisfies on both ladders.

Inside the designer, every camera has a per-camera Standard toggle — DORI (4 steps) or OODPCVS (7 steps). The choice flips the FOV-cone overlay, the per-camera labels, the multi-page PDF export and the DXF export to the chosen ladder. The system validator also adjusts: an OODPCVS camera whose range exceeds the Overview reach (20 px/m) is flagged the same way a DORI camera that overruns Detect (25 px/m) was flagged before.

Quick links to the OODPCVS-aware tools

For deliverables, the multi-page PDF carries the selected ladder labels into the equipment table and the per-camera elevation views, so a procurement officer reviewing the bid response sees the standard-aware language they expected. The DXF export ships dedicated AutoCAD layers per OODPCVS level (T-CCTV-OODPCVS-OVERVIEW through SCRUTINISE) so downstream BIM toolchains can ingest the metadata without re-keying.

Parity note vs JVSG lens calculator

JVSG's lens calculator added OODPCVS support in a recent update — a welcome move for a long-established Windows desktop tool. CCTVplanner's calculator achieves parity on the same vocabulary in a browser, no install required, with the additional advantage that the OODPCVS metadata flows through to the project, the BOM, the multi-page PDF and the DXF export. For integrators evaluating both tools side-by-side in 2026, the standards-language coverage is comparable; the difference is what happens to the metadata after the calculator step.

If you are evaluating tools against the EN 62676-4:2025 specification, the practical buying criterion is whether the tool can carry OODPCVS labels end-to-end, not just at the calculator. That is the test most procurement officers will apply when reviewing the deliverable.

Frequently Asked Questions

What does OODPCVS stand for in the 2025 EN 62676-4 update?

OODPCVS is the seven-step pixel-density ladder introduced in the IEC/EN 62676-4:2025 amendment. The steps — Overview (20 px/m), Outline (40), Discern (80), Perceive (125), Characterise (250), Validate (500) and Scrutinise (1500) — give procurement teams finer-grained coverage targets than the legacy four-step DORI ladder, including two new tiers above DORI Identify for facial verification and passport-grade biometric capture.

Does OODPCVS replace DORI?

No. The classic DORI thresholds (Detect 25, Observe 62.5, Recognize 125, Identify 250 px/m) remain valid and are still cited by most pre-2025 specifications and many national tenders. OODPCVS is a parallel, more granular ladder published alongside DORI. New EU and CENELEC tenders from 2026 onwards increasingly specify OODPCVS levels in addition to (or instead of) DORI.

Which projects must use OODPCVS in 2026?

Any tender or specification that explicitly cites EN 62676-4:2025 or IEC 62676-4:2025 should describe coverage in OODPCVS terms. In practice this is appearing in EU public-sector tenders, critical-infrastructure RFPs, and large enterprise procurement documents updated in 2026. Smaller installations and legacy projects can continue using DORI-only for now, but new specifications increasingly expect both ladders to be quoted side by side.

Is CCTVplanner compatible with OODPCVS?

Yes. Every camera in the designer has a per-camera Standard toggle — DORI (4 steps) or OODPCVS (7 steps) — and switches the FOV-cone overlay, PDF/DXF exports and the system validator to the chosen ladder. The dedicated /calculator/oodpcvs tool runs the math for all seven steps in parallel from a single lens/sensor/resolution input.

How does the 2025 update affect lens calculators specifically?

Lens calculators must support both ladders. The underlying pixels-per-metre maths is identical: D = horizontal_pixels / (2 × required_px-per-metre × tan(HFOV/2)). What changes is the threshold: OODPCVS Characterise (250 px/m) is numerically the same as DORI Identify, but OODPCVS Validate (500 px/m) and Scrutinise (1500 px/m) are new tiers a 2014-era spec couldn't express at all.

Where can I read the official EN 62676-4:2025 text?

The official standard is published by CENELEC for the European version (EN 62676-4) and IEC for the international version (IEC 62676-4). Both are paywalled documents you purchase through your national standards body (BSI, DIN, PKN, AFNOR, and so on). This article is an educational explainer, not a substitute for the published text — for procurement-grade compliance always consult the official document.

EN 62676-4:2025 OODPCVS Update Explained (2026): What Changed, Who's Affected

Table of Contents