A useful perimeter plan connects three things: a visible crossing, a recording that explains the route, and a person who can act on it. Start with gates, corners and concealed approaches. Use boundary views for awareness and separate close views where identifying detail matters; buying more resolution alone does not resolve an obstructed route.
Before requesting equipment: draw the boundary, assign a task to each view, mark target distances and night lighting, then trace power, network and recording paths. The example below is a planning exercise, not a customer installation or a guaranteed camera count.
Choose what each boundary view must tell you
“See the fence” is too vague for acceptance. Write a task such as “notice a person crossing the side path after closing” or “obtain useful facial detail at the pedestrian gate.” Observation shows activity and direction. Identifying detail requires a larger, sufficiently clear image of the subject and a useful angle. A long fence view may meet the first task while failing the second.
Axis's image-usability guidance separates overview and identification and explains that target pixel density and angle matter. Its analytics section also requires application-specific installation and testing. Use that distinction to specify tasks; it does not establish a detection distance or analytics capability for a QuarkView model.
Map the routes, then choose the lens and position
Walk both sides of each accessible boundary during normal operation. Mark gaps beneath vegetation, changes in ground level, fence corners, parked trailers and places where a person can move behind a wall. Record the nearest and farthest target positions for each camera. Measure the scene width at the target, not just the camera-to-fence distance.
| Position | Viewing task | Decision and failure check |
|---|---|---|
| Long straight fence | Observe approach and crossing | Look along an unobstructed strip. Check the far end and the space directly below the camera; a narrow lens can lose the near route. |
| Corner or side passage | Connect adjoining routes | Overlap where the subject actually turns. Overlapping sky or empty ground does not prevent a route gap. |
| Pedestrian gate | Detail at a predictable point | Frame the person at the latch or intercom. Very high mounting may show a head rather than a face. |
| Vehicle gate | Approach context and stopped-vehicle detail | Separate the wide approach from close detail. Plate reading needs its own validated capture requirements. |
Example of the width tradeoff: assume a recorded image is 2,560 pixels wide and the target plane spans 20 m. Its average horizontal density is 2,560 ÷ 20 = 128 pixels/m. Narrowing that plane to 8 m gives 320 pixels/m. These are geometric estimates, not identification guarantees: perspective, cropping, compression, angle, blur and darkness still affect the recording. Check a moving test subject at the farthest required point before selecting a fixed lens; a varifocal option can help adjust framing if the chosen model supports it.
Keep continuous fixed views on critical crossing routes. If a movable camera is looking elsewhere, that direction has no current view from it. A PTZ can supplement active investigation, but the coverage plan should state which fixed view retains each important route.
Design alerts around a visible route and an actual responder
Draw an intrusion area or crossing line only if the selected camera and recorder support the required rule. Exclude a public pavement, moving foliage or a routinely occupied loading area where these are outside the purpose. Do not exclude a troublesome strip if it contains the real entry route; change the view or operating plan instead.
AXIS Perimeter Defender's manual documents missed detections in fog, direct light and inadequate light, and false alarms involving partial occlusion, insects and headlights with heavy rain. These are useful test conditions, not promised features or performance for other products. Inspect moving subjects under normal night lighting, with headlights and any reflective fence or wall in view. A bright static night image can still conceal motion blur.
Write the response chain: event reaches the named on-duty receiver; receiver opens the clip and matching live view; they acknowledge it; they follow the site's safe escalation procedure; the incident is preserved if needed. Name a backup receiver for an unacknowledged event. For an unattended home, choose an arrangement the owner can actually monitor; a notification cannot guarantee intervention. For a business, align recipients with opening hours and shifts rather than one employee's personal phone.
Trace power, network and recording for every segment
A wired position needs a protected cable route and a compatible power source, not merely a spare recorder channel. Compare each camera's required PoE type and maximum draw with per-port limits and the switch's total budget, including night operation. Cisco's PoE overview explains the different power types and the 100 m cable-length limit for the standard arrangement it describes. Measure the full routed channel, including patch leads; long fence routes may need another powered network point or an engineered link.
For a remote corner, assess available mains power, the data link and maintenance access separately. A cellular or solar position is an alternative only after its recording mode, data allowance, seasonal energy needs and outage behavior are checked. A claimed outdoor rating does not specify the cable-entry installation: use the selected equipment's mounting and connector instructions and have the installer address local electrical protection requirements.
Choose continuous recording where a complete timeline is required. Event-only recording can save space, but a missed trigger may also remove the footage needed to explain that miss. Confirm supported pre-event and post-event recording before relying on them. Size storage from aggregate recorded bitrate and schedule, then verify the oldest playable recording in service. Extra live streams and other network traffic also need capacity.
Example: a small yard with a gate and a concealed corner
Illustrative assumptions: a 40 m by 30 m yard, one vehicle gate, one side gate, a storage shed blocking part of the rear boundary, existing mains at the office and gate, and a requirement to review all routes continuously. This sketch does not prove every metre is covered; positions and lenses must be surveyed.
- Gate overview: shows vehicle approach and movement into the yard, without using the same broad view as the only entrance detail.
- Gate detail: frames the normal pedestrian or visitor stopping point. Add a separate plate task only if required and demonstrated.
- Side-gate route: follows the passage toward the office with a shared transition into the gate overview.
- Rear route pair: uses a view on each side of the shed so a person does not vanish behind it. If this still leaves a hidden crossing, relocate or add a view.
Storage example: if these five assumed views each record an average 4 Mbit/s continuously for 14 days, video payload is 5 × 4 × 86,400 × 14 ÷ 8 = 3,024,000 MB, or about 3.02 TB in decimal units. This excludes filesystem overhead, audio, extra streams and reserves; measured bitrate can differ. It is an input calculation, not a drive purchase recommendation. Use the storage planning tool for your actual inputs.
Accept the route and response, then maintain both
- Coverage: walk every crossing both directions at near and far points, turn corners and repeat with vehicles in usual parking positions. Replay the sequence across cameras and note gaps.
- Night and nuisance conditions: repeat under normal night lighting. Log each expected crossing, whether an event was raised and whether the saved image fulfilled its task. Separately record unwanted alerts during routine site activity; do not count them as successful detection.
- Response: trigger a planned test event, confirm delivery to the on-duty receiver and backup, and retrieve the lead-in, crossing and following route with aligned timestamps.
- Recovery: during an agreed maintenance window, test the specified link or power interruption. Confirm recording resumes and document any missing interval. Do not infer local storage or automatic backfill unless demonstrated on the selected system.
Keep a camera map, saved test clips, configuration record and unresolved exceptions with the handover. Assign someone to check recording health and alert recipients, trim vegetation, clean lenses and re-test after storms, fence work or changed parking. Review actual retention after setting changes. Use individual accounts and the manufacturer's supported secure remote-access method; limit unnecessary views of neighbours and public areas and check local privacy requirements.
For the next step, use the lens guide or night-lighting guide. Send your boundary map, viewing tasks and response requirements when discussing a project.