A useful commercial video system starts with a documented task: what must the recording show, where, under which conditions, and who will act on it? Camera count and megapixels follow those decisions. This guide provides a planning sequence for Pennsylvania and Mid-Atlantic offices, warehouses, retail properties, industrial facilities and multi-site organizations.
Use the camera and infrastructure hardware hub for equipment decisions, the manufacturer comparison for platform selection and the project worksheets to retain the decisions.
1. Define the operational requirement
Describe an event in practical terms: reconstruct a loading-dock transfer, determine which vehicle entered a gate, follow an incident between entrances, or verify an alarm. Separate general awareness from the ability to recognize a familiar person, obtain identification detail or read a plate. One wide view rarely performs every task. Decide whether someone watches live, reviews after an incident, or receives a verified event.
Record the owner of each requirement and the consequence of missing the scene. Avoid promising that cameras prevent every incident. Recording, detection and human response are separate functions that need separate acceptance tests.
2. Survey the actual property
Walk the site during representative operating periods. Mark people and vehicle routes, doors, loading positions, landscaping, public sidewalks and neighboring property. Note changing racks, stored trailers, forklift movement and seasonal obstructions. Photograph proposed viewpoints with authorization. Survey available lighting after dark; a daytime image does not establish nighttime performance.
| Scene record | Information to retain |
|---|---|
| Purpose and boundary | Target activity, useful detail, distance and areas excluded from recording |
| Conditions | Lighting, target speed, glare, rain, snow, vibration and likely obstruction |
| Infrastructure | Mounting surface, accessible route, cable length, power and network location |
| Acceptance | Day/night sample, subject movement, reviewer and pass criterion |
3. Choose views and cameras together
Draw the target area before choosing the lens. Wider views distribute the available pixels across more space. Digital zoom cannot recover detail that was never recorded. Check lens, sensor, exposure, focus, motion blur, compression and lighting together. Position cameras for useful faces or task detail while considering tampering and service access. High mounting can produce only the tops of heads.
Use fixed overview cameras to retain continuity. A PTZ camera looking elsewhere cannot document the original scene at the same moment. Plates moving through headlights require a deliberate capture design; do not assume an ordinary parking overview will read them. Axis explains the limits of planning by resolution alone in its pixel-density reference. Confirm the applicable design criteria rather than treating one historic threshold as a universal guarantee.
4. Select the recording architecture
Identify where full-resolution video, event clips, metadata, credentials and configuration reside. An NVR, a server-based VMS, edge storage and a cloud-managed service can have very different failure paths. Cloud management does not necessarily mean all video is stored off site. Document what remains available if the internet, a switch, one recorder or the cloud service becomes unavailable.
| Approach | Planning responsibility |
|---|---|
| Local NVR or VMS | Storage health, operating-system support where applicable, backups, remote access and physical protection |
| Cloud-managed or hosted | Upload behavior, local continuity, identity controls, recurring licenses, export and service exit |
| Edge or hybrid | Media endurance, camera loss, recovery of missing recordings and consistency between archives |
5. Size storage and networks from measured workloads
A starting estimate for continuous recording is decimal storage in TB = aggregate bitrate in Mbps × 0.0108 × retention days. For example, sixteen streams averaging 4 Mbps total 64 Mbps, or about 20.7 TB over thirty days before reserve, file-system overhead, redundancy and other streams. This is an illustration, not a capacity guarantee. Motion, noise, codec settings, resolution and frame rate affect actual bitrate.
Validate representative recordings and the usable capacity after RAID or other protection. RAID is not a backup. Event-only recording saves space only when detection, pre-event buffers and event coverage work as required. Include live clients, exports, replication and recovery traffic in network calculations. Cloud backfill after an outage can compete with ordinary business traffic.
6. Engineer cabling, power and continuity
Document switch ports and both per-port and total PoE power budgets. Include infrared illumination, heaters and PTZ movement in worst-case power checks. Specify correct cable, pathways, surge protection and environmental ratings. Fiber is often useful between buildings; copper pathways require a site-specific grounding and surge review. Wireless links need line-of-sight, capacity and interference checks rather than an assumption that a signal indicator proves reliability.
A UPS must support the complete required recording path, including switches, recorders and necessary network equipment. State the target runtime, load, shutdown behavior and battery replacement responsibility. Check recording recovery after controlled power restoration.
7. Establish cybersecurity and ownership
Inventory device models, software versions, licenses and support periods. Use unique accounts, least privilege, multifactor authentication where supported, restricted management networks and approved remote access. Do not expose camera administration directly to the internet by default. Assign responsibility for patches, vulnerability notices, account removal, configuration backups and certificate renewal. CISA’s internet exposure reduction guidance provides a useful baseline.
8. Approve privacy, retention and disclosure rules
Define the purpose and boundaries of each view. Exclude private areas and unnecessary neighboring interiors; verify masks in recordings and exports as well as live views. Set retention by documented organizational, legal and contractual requirements. There is no single retention period appropriate to every Pennsylvania business. Assign an incident-hold process so relevant video is preserved before normal overwrite.
Audio and biometric processing require separate review. Leave these features disabled unless the organization has approved a lawful purpose and configuration. Pennsylvania’s interception statute contains specific consent provisions and exceptions; signage alone should not be assumed to resolve every recording issue. Multi-state organizations must review each location’s rules.
9. Test analytics and operator workflows
Choose one measurable event per rule and define the recipient, schedule and response. Test genuine events and ordinary activity such as foliage, vehicle lights and weather. Record missed events, nuisance events and review workload. AI labels are aids to review, not conclusive identification or grounds for an automatic adverse decision. Follow the analytics evaluation guide.
10. Commission, hand over and maintain
Observe live and recorded samples during day and night operation. Verify timestamp synchronization, playback, retention, export on a separate workstation, user restrictions and incident holds. Disconnect only the components authorized for a controlled outage test. Confirm health alerts, missing-video recovery and return to normal operation. Document exceptions with a responsible person and resolution date.
Retain the final camera schedule, network drawing, approved privacy settings, version inventory, license record, test evidence, backup procedures and operator training record in a controlled repository. Protect credentials separately. Set a review schedule for camera cleanliness, shifted views, changed lighting, storage health and account access. A working live picture is only one part of a successful system.
Related NERSA reference
See NERSA’s security project lifecycle reference for the corresponding applied reference.