If you design CCTV for parking lots and weigh whether the IPVM Design Calculator still earns its place, this page is for you. CCTVplanner is the free, EU-hosted alternative integrators are switching to in 2026. Same DORI math, bigger camera catalog, modern UI, vertical-specific workflows built in.
Free tier · No credit card · Open in your browser
Plate capture at 5-15 m needs Identify-DORI (250 px/m) at the right angle. Wrong focal length or mounting height = wrong plate read rate. Drag the Identify ring against the barrier on your plan and verify before specifying the lens.
A 200-bay car park has too many bays to put a camera on each row. Wide-area Detect-DORI (25 px/m) on a mid-height pole covers 8-12 bays — but only if the cone reaches that far in low light.
Driving lanes need 24/7 coverage. IR-enabled bullet with verified IR range matters more than the megapixel count. Datasheet-verified IR range in our catalog tells you the cone actually reaches.
Pedestrian-vehicle conflict zones need Recognize-DORI (125 px/m) so the post-incident review is usable. Set the focal length, drop the camera, drag the Recognize ring against the crossover before mounting.
Drop the ANPR camera, set lens, drag the Identify ring (250 px/m) to the barrier. The IFOV-aware plate-capture math surfaces if your lens is wrong.
Drop a mid-height pole camera. Detect-DORI (25 px/m) cone reaches 30+ m at the right lens. Verify against the bay-row layout, then walk away.
Filter the catalog by datasheet-verified IR range. The bullets that actually reach 30 m at night surface; the marketing-claim ones get filtered out.
Switch the floor plan layer to OpenStreetMap aerial. Trace the actual parking property, drop perimeter cameras, watch cones reach the boundary.
IFOV math validates the plate-capture geometry — focal length × sensor pixel pitch × distance must yield ≥150 px on the plate. CCTVplanner flags violations before you specify.
OpenStreetMap aerial layer + address search. Trace the lot, drop cameras, watch the cones reach actual fencing. No re-tracing the lot in CAD.
Topology graph computes PoE draw across pole switches. The budget surfaces; pick the right switch class before you trench.
US municipal car parks mandate non-Hikvision / non-Dahua. The compliance flag surfaces on every spec card; the mixed-compliance validator catches mistakes.
Everything below is in the product today, on the free tier, and none of it needs an install. Open it in a browser and check it against IPVM Design Calculator on a job you already know.
No install and no workstation. Walk the site from any camera point of view, with DORI silhouettes standing at the Detect, Observe, Recognize and Identify distances so the customer sees what the camera sees. Sun and shadow study for the time of day that matters, and one-click 3D PDF export for the people who will never open a design tool.
Every cone is computed from the sensor, resolution and focal length at the mounting height (1 to 20 m) and tilt you set, then clipped by buildings, fences and real ground elevation on satellite imagery. On a flat indoor floor a 2D tool agrees with us. On a sloped yard or a sunken loading dock it does not, and that gap is exactly where the blind spots are.
Racking, containers, concrete blocks, scaffolding, solar panels, trees, and the machinery a live construction site actually parks in the shot: excavators, cranes, concrete mixers, bulldozers, vans and pickups. Each one carries real dimensions and a vertical range, and the field of view clips against it with the shadow drawn on the plan.
Stack ground floor, mezzanine, plant room and roof as separate levels. Draw walls, close rooms and read the floor area back in square metres. Cabling routes between levels, the topology graph carries across them, and each floor exports as its own DXF sheet and PDF page.
Predictive coverage for access points using ITU-R P.2040 wall transmission and a P.1238 margin, drawn as a heatmap over the same plan the cameras sit on. Point-to-point links are checked for line of sight against the buildings and terrain, so the wireless leg of the design fails on screen rather than on site.
51 specified cable types with PoE budget from loop resistance, DC voltage drop, fibre loss budget with splice and connector allowances, coax attenuation per format, speaker line loading and conduit fill. Route length is measured on the drawn route and carries straight into the bill of materials, the cable schedule and the customer offer.
The plan is validated while you draw it: DORI shortfall, blind spots, perimeter gaps, PoE budget and class escalation, cable length and category headroom, conduit bundling, fibre loss, thermal lens and pairing, EMC and environmental class, lightning protection zones, ONVIF profile mixing, NDAA compliance, bandwidth headroom and switch port capacity.
CAD-grade DXF (AutoCAD R2018 / AC1021) on named layers with BLOCK, INSERT, SPLINE, ELLIPSE, HATCH and DIMENSION preserved, inside an ISO 5457 sheet frame with an ISO 7200 title block. Multi-page PDF with bill of materials, cable schedule, equipment list, elevation views, coverage analysis, acceptance test protocol, maintenance schedule and the GDPR Article 35 DPIA worksheet.
Identify-DORI (250 px/m) at the plate distance, IFOV check passes ≥150 px/plate. CCTVplanner has an ANPR-specific overlay that surfaces both checks on each camera placement.
Typically 6-10: 1 ANPR at the barrier, 2-3 wide-area at the bay-row mid-points, 1-2 driving-lane bullets, 1 at the pedestrian crossover, 1 at the back gate. CCTVplanner free tier covers small lots; Installer handles enterprise-scale.
Yes. 100+ datasheet-verified flagship bullets carry IR range as a first-class spec. Filter the catalog by IR ≥ 30 m to surface lot-grade options.
Yes. CCTVplanner has an OpenStreetMap aerial layer with address search. Trace the actual lot, drop cameras, watch the cones reach across the real property. No CAD re-tracing.
The free tier covers a real small site — no card, no install. Put a plan in, place a camera, and check the first DORI ring against the numbers you already trust.
