Is CCTVplanner suitable for designing CCTV for banks?
Yes. The platform is built for the multi-zone, compliance-heavy reality of bank branches. It enforces EN 62676-4 DORI at Identify level for ATM, vault, teller and entry, ships an EN 62305 lightning protection module for outdoor ATMs, generates a GDPR Article 35 DPIA worksheet, flags NDAA §889 compliance per camera, and lets you copy a branch baseline across an entire branch network. Banks from all over the world use the tool.
Why does the ATM camera need to be at DORI Identify level?
EN 62676-4 defines four operator-task levels: Detect (25 px/m), Observe (62.5), Recognise (125), and Identify (250). At Recognise, you can tell that a person is the same person you saw a moment earlier. At Identify, you can name them — or, more importantly, a fraud investigator or court can. ATM fraud is the canonical use case for Identify, and a camera that misses the threshold is functionally useless when it matters. The tool calculates the lens, mounting height and tilt that hit Identify at the user's working distance.
How is the vault overlap calculated?
Vault entry, anteroom and safe-deposit corridor demand dual-camera overlap with no blind spot. The tool's coverage analysis renders the union of all camera fields of view as a heat map and flags any unreached square metre. You see the gap on screen before installation rather than discovering it in incident review.
What about lightning protection on outdoor ATM kiosks?
Standalone outdoor ATMs in petrol stations, shopping-centre forecourts and stand-alone kiosks are the most exposed installations a bank operates. They are LPZ 0A or 0B under EN 62305. The tool classifies the LPZ per camera and produces a Surge Protection Device requirements list with Type 1, 2 and 3 SPDs at the right points in the cable run. The integrator does not have to interpret EN 62305 — the design has done it already.
How does the tool handle GDPR for customer faces?
Banks processing customer faces and transactional behaviour fall squarely into Article 35 DPIA territory. The DPIA worksheet built into the tool records the lawful basis (typically Article 6(1)(c) legal obligation under AML and 6(1)(f) legitimate interest, with the balancing test documented), the retention period per zone, the data subjects, the risks identified and the mitigations applied. It exports straight into the project PDF.
How are AML retention windows reflected in the storage calculation?
AML retention varies by jurisdiction — typically 5 to 7 years for transaction-evidence footage versus 30 days for general lobby coverage. The design lets you set the retention rule per zone, and the storage calculator multiplies the bitrate, frame rate, hours and retention to deliver a per-branch storage requirement that matches reality. No more under-specified NVR.
Does it handle NDAA §889 for federally affiliated branches?
Yes. Federally affiliated branches — government depository banks, federal-grant recipients, branches inside federal buildings — fall under NDAA §889. Every camera in the 65,000-model catalog carries an NDAA flag, and a mixed-compliance validator warns when a banned-vendor camera lands in a federal-related BOM. Issues are caught at design time, not at the procurement audit.
Can I roll one design across an entire branch network?
Yes. Project copy lets you fork a baseline branch design and adjust per-site. A retail bank with 50 branches uses one master template plus per-branch overrides for footprint, ATM count, drive-through presence and parking exposure. The compliance posture (GDPR, AML retention, NDAA, EN 62305) carries forward to every fork.
Where is the tool itself hosted?
DEFENSAR. 100% Engineered and Hosted in EU. No third-country transfers in the default stack. Useful when the bank's procurement origin filter excludes non-EU/non-Western design tools, which is increasingly common in critical-infrastructure tenders.