Video Surveillance Systems: What You Should Own at Handover
A video surveillance system is hardware plus a record set, and the record set is the half that decides what the next five years cost. When it is missing, every repair, expansion and evidence request begins with archaeology: tracing a cable to find which switch port feeds a camera nobody can log into. The list below is what KSEDCO hands over, and it is a fair standard to hold any integrator to.
A camera schedule, line by line
One row per camera, covering what it is for and what it is. Location and the stated purpose of the view. Manufacturer, model and firmware version. Lens or field of view, and mounting height. IP address, switch name and port number, and the network segment it sits on. Power over Ethernet class. Without this, adding six cameras next year means rediscovering the system before designing anything.
The retention math, with its assumptions written down
Storage sizing is a calculation, not a number someone remembers. It should state the bitrate per camera, the recording mode, the codec, the number of days and the resulting capacity, so that you can see what changes it. Continuous recording and motion-triggered recording differ by a large factor. H.265 differs from H.264. A quiet warehouse and a busy retail entrance produce very different loads at identical settings. When the retention requirement comes from insurance or a lease, that source belongs in the document too.
Credentials in your name
- An administrator account owned by your organization, not by the installing company.
- Multi-factor authentication enabled where the platform supports it.
- A written recovery path for the day the person holding the account leaves.
- Named accounts for anyone who exports video, so the audit trail identifies people rather than a shared login.
Service accounts used by an integrator should be separate, visible in the user list, and removable by you without a support ticket.
Network and power notes
Which network segment the cameras live on and why, any firewall rules created for remote access, the total wattage available on each switch against what is actually drawn, and the measured runtime of the battery backup carrying the recorder, switch and network equipment together. Grounding and surge protection locations belong here as well, particularly for pole and rooftop cameras, which take the brunt of Georgia’s storm season.
Test evidence, captured once
Sample images from every camera in daylight, after dark, and against backlight where that condition exists. A recorded demonstration of search, playback and export, performed by your staff rather than watched. These take an afternoon at handover and are the only honest record of what the system looked like when it was accepted, which matters when a camera slowly drifts out of focus two years later.
Taking over a system nobody documented
Many Georgia buildings change hands with cameras already on the walls and no paperwork at all. A takeover starts with the same inventory: what is installed, what still receives firmware updates, what is recording and what only appears to be. From there the decisions are usually straightforward. Some cameras are worth keeping on a new recorder; some are past support and should be replaced during the same visit rather than revisited later.
Standardizing across sites
Owners running several Georgia locations, an Atlanta headquarters, a Macon facility on I-75, a Columbus site on I-185 and a Savannah warehouse, gain more from one naming convention, one retention rule and one permission model than from any individual feature. Standard records make a system portable between technicians, which is the point.
To discuss a new system, an expansion, or the takeover of an existing installation, reach KSEDCO at (888) 360-0035 or at 2700 Cumberland Pkwy SE, Suite 410, Atlanta GA 30339.
Commercial camera installation cost and design
Use this parent-company planning resource before Georgia engineering, installation, documentation and lifecycle support.
Discuss installation, maintenance or service
Detailed guide maintained by 360TechnologyGroup.com, the parent-company knowledge center.
IP security camera installation, step by step
An IP security camera installation is a network job as much as a mounting job. Each camera is a small computer on your network with an address, drawing power over the same cable that carries its video. Treated properly that is a large improvement; treated carelessly it is how a camera becomes the weakest device on a business network.
How we run one:
- Survey first. What each camera is for, at what distance, in what light. Pixels per foot at the target decides whether an image identifies a person or merely proves one existed.
- Cable and power. Cat6 to each device, terminated and tested, with results recorded. A PoE switch with enough total wattage — not just enough ports, which is the failure that makes cameras reboot at night when the infrared comes on.
- A separate VLAN. Cameras belong on their own network segment, away from workstations and card payments. Free if decided at the start.
- Recording and retention. Fourteen days suits most incidents; thirty to ninety where insurance or licensing requires it, which roughly doubles storage.
- Commissioning and handover. Focus, exposure and analytics set on site, plus logins that belong to you and documentation you keep.
IP camera installation across Georgia — new systems, expansions, and repair or takeover of existing installations.