IP Camera Rollout: 12-Point Pre-Installation Checklist

1. Verify Network Bandwidth and Switch Capacity

Before purchasing a single lens or housing, confirm the existing network can handle the traffic. IP cameras generate continuous streams. A single 4K stream can consume several megabits of bandwidth, and a single 1080p stream typically uses 4 to 8 megabits. Multiply this by the total camera count and add the overhead for management traffic.

If the site relies on a single core switch, check the port speed and the switch capacity. A 100 megabit switch is insufficient for a modern HD deployment. You need gigabit ports on the backbone and at the edge.

Red flags:

• Existing switches have only 10/100 megabit ports.
• The core switch is already at 70 percent or higher utilization during peak hours.
• No spare ports are available on the edge switches.

2. Confirm Power Delivery Method

Decide how you will power the cameras. The two standard methods are Power over Ethernet and dedicated AC power. PoE is preferred for simplicity, but it has limits. A camera with a high-wattage heater or a high-resolution sensor may exceed the 30-watt budget of PoE+ on a single cable.

If you choose PoE, verify that the switches support the required power class. If you choose AC, plan for conduit runs, junction boxes, and surge protection. AC power adds labor and cost but provides reliability in harsh environments.

Red flags:

• Long cable runs exceeding 100 meters without PoE extenders.
• No ground fault protection on AC circuits.
• Mismatched power adapters between cameras and switches.

3. Inspect Conduit and Cable Lengths

The physical path of the cable determines signal integrity. Ethernet cables have a maximum transmission distance of 100 meters from the switch port to the camera. Exceeding this limit causes packet loss and video freezing.

Measure every run. Use a cable tester to check for continuity and pinout. Ensure the conduit is free of sharp edges that can crush the cable jacket.

Red flags:

• Cable runs longer than 100 meters without active extenders.
• Conduit bends with a radius smaller than 4 times the cable diameter.
• Cables sharing conduit with high-voltage power lines without proper shielding.

4. Review Physical Mounting Points

Cameras must be mounted securely to withstand weather and vandalism. Check the structural integrity of walls, poles, and brackets. A camera that falls off after a storm creates a security gap and a repair cost.

For outdoor units, ensure the mounting location provides shade from direct sun to prevent lens fogging. Check the angle of view. A camera pointed at a bright sky will produce a black image.

Red flags:

• Mounting points on painted drywall without anchors.
• Brackets that are not rated for the camera weight.
• No access to the camera for maintenance or cleaning.

5. Check IP Addressing and Subnet Configuration

Every IP camera needs a unique IP address. If the network uses DHCP, ensure the DHCP pool has enough addresses for the cameras, switches, NVR, and management tools. If you use static IPs, document them in a spreadsheet.

Check the subnet mask and gateway. A mismatch between the camera and the NVR causes communication failure. Ping every camera IP address from the NVR before finalizing the configuration.

Red flags:

• IP address conflicts between cameras and other network devices.
• Subnet mismatch between the camera VLAN and the NVR.
• No DHCP reservation for the NVR and management PC.

6. Validate Video Encoder and Storage Requirements

The NVR or VMS must be sized for the total video load. Calculate the storage needs based on the desired retention period. A 4K camera with a 30% compression ratio may require 100 to 200 GB per day. Multiply by the number of days you need to store footage.

Check the NVR input capacity. A NVR with 16 inputs cannot handle 32 cameras. Ensure the NVR has enough CPU power to decode the streams if you plan to view multiple cameras simultaneously.

Red flags:

• NVR input count lower than the camera count.
• Storage capacity insufficient for the required retention period.
• NVR fan failure due to overheating in a confined cabinet.

7. Test Network Segmentation and VLANs

Isolate the camera traffic from the office network. Use a dedicated VLAN for the cameras. This prevents malware on an office PC from accessing the camera management interface. It also reduces bandwidth competition.

Configure the switch ports to assign the correct VLAN ID to the cameras. Ensure the NVR is on the same VLAN or has a gateway to reach it. Test connectivity between the NVR and each camera.

Red flags:

• Camera traffic on the same VLAN as the guest Wi-Fi.
• No firewall rules restricting access to the camera ports.
• Management interface exposed to the public internet.

8. Confirm Lens and Sensor Compatibility

The lens must match the sensor size. A 1/2.8-inch sensor requires a different lens than a 1/1.8-inch sensor. Mismatched lenses cause image distortion or a black field of view.

Check the focal length. A 2.8 mm lens provides a wide field of view, suitable for parking lots. A 6 mm lens provides a narrower view, better for doorways. Choose based on the scene, not just the camera model.

Red flags:

• Lens cover not removed before installation.
• Lens cap left on the front of the camera.
• Mismatched focal length for the application.

9. Verify Firmware and Security Settings

Update the firmware on every camera before connecting them to the network. Outdated firmware contains known vulnerabilities. Change the default admin password immediately. Use a strong password with mixed characters and numbers.

Disable Telnet and enable SSH if available. Disable UPnP. Use a static IP address for each camera to avoid address conflicts.

Red flags:

• Default admin username and password still in use.
• Telnet service enabled on the management interface.
• Outdated firmware version with known security patches.

10. Document the Network Topology

Create a diagram of the network. Show the switches, the NVR, the cameras, and the VLANs. Label every cable run with its destination. This document is critical for future maintenance and troubleshooting.

Include the IP addresses of every device. Note the MAC address of each camera. This helps identify faulty devices quickly.

Red flags:

• No cable labels.
• Missing documentation of the VLAN configuration.
• No record of the IP address assignments.

11. Test Video Quality and Storage

Connect the first batch of cameras and record video for 24 hours. Check the video quality at night. Adjust the IR illuminators and the exposure settings. Ensure the video is stored correctly on the NVR.

Review the footage. Look for dropped frames, compression artifacts, and color issues. Verify that the storage is being written to correctly. Check the disk health.

Red flags:

• Video freezes or drops frames.
• Night vision is too bright or too dark.
• No video is saved to the NVR.

12. Prepare for Commissioning and Handover

Prepare a commissioning report. Include the list of all cameras, their locations, and their IP addresses. Include the network diagram and the storage configuration. Provide the admin credentials to the end user in a secure document.

Train the end user on how to access the video, how to check the storage, and how to report issues. Schedule a follow-up visit to check for any issues after 30 days.

Red flags:

• No commissioning report.
• No training provided to the end user.
• No follow-up visit scheduled.

13. Common Mistakes to Avoid

• Assuming the network can handle the load. Always verify bandwidth.
• Ignoring cable length limits. 100 meters is the maximum for standard Ethernet.
• Forgetting to change default passwords. This is a major security risk.
• Not documenting the network. Future problems become impossible to solve.
• Skipping the 24-hour test. Issues appear after a day of continuous recording.