- Cisco Meraki
- Axis
- Hanwha Vision
- Avigilon
- Verkada
We aren't tied to any brand. If your drawings call for something else, we'll install to the specification.
What a commercial surveillance system from Telelink includes
Telelink Business Services is a licensed C-7 Low Voltage Systems Contractor, CSLB License #472017. We design, cable, mount, aim and configure IP camera systems for multifamily and senior housing, state and local government facilities, campuses, offices and warehouses across California. Three of our four published projects include surveillance: an occupied multifamily renovation at Little Tokyo Towers in Los Angeles, an occupied senior housing renovation at Horton House in San Diego, and a tenant improvement for the State Controller’s Office in Sacramento.
A complete camera scope from us includes:
- Coverage design from the floor plan, with each camera’s location, field of view, and purpose written down
- Cat6 or Cat6A cabling from every camera to the nearest telecom room, tested and labeled to the building’s scheme
- PoE switching, VLAN segmentation, and bandwidth planning
- Cameras, mounts, junction boxes, and conduit stubs where the architecture calls for them
- Recording on a network video recorder, in the cloud, or a hybrid of the two
- User accounts, retention settings, and integration with access control and intercom
- As-built drawings, a camera schedule, and manufacturer documentation for the compliance file
We regularly install and configure Cisco Meraki MV, and we install Axis, Hanwha Vision, Avigilon, Verkada and Ubiquiti UniFi Protect when your specification calls for them. Whichever platform you use, you get a written coverage plan, a tested cable plant, and a configuration that someone other than us can administer.
Camera types and where each one belongs
Which camera type you pick depends on where it’s mounted and what it needs to see, much more than on how it looks. Each type solves one kind of viewing problem and brings its own mounting issue.
| Type | Where it fits best | Watch for |
|---|---|---|
| Dome | Corridors, lobbies, elevators, anywhere vandal resistance and a discreet look matter | Ceiling height; a dome at 14 feet sees the tops of heads |
| Bullet | Parking lots, building perimeters, long views down a fence line or driveway | Highly visible, which is sometimes what you want; needs a solid mount and a drip loop |
| Multisensor | Building corners, corridor intersections, large open rooms | One drop and one license for three or four views; heavier, so check the mount |
| PTZ | Large yards, loading docks, campuses with staffed monitoring | Only records where it’s pointed; pair with fixed cameras for continuous coverage |
| Fisheye | Small lobbies, break rooms, package rooms, retail floors | 360 degree coverage with dewarping in software; low detail toward the edges |
On most commercial buildings, the bulk of the count is domes inside and bullets or multisensors outside. PTZ cameras are usually only worth their cost where a person is watching them, and fisheyes work in rooms small enough that the edge distortion doesn’t matter much.
Coverage design: resolution, lens and low light in plain terms
Resolution alone doesn’t tell you what a camera will show. What matters is how many pixels land on the subject at the distance you care about. A wide lens spreads a camera’s pixels across a large scene, so each person in that scene gets fewer of them. A narrow lens concentrates the same pixels on a smaller area. A 4 megapixel camera with a wide lens will show you that someone walked through a parking lot at 80 feet, but it probably won’t give you a face you could hand to police.
We plan each view against a simple rule of thumb with three tiers. Detecting activity needs the fewest pixels on target. Recognizing a person you already know needs more. Identifying an unknown person or reading a license plate needs the most. For each camera we write down the purpose of the view (identify at the entry door, detect along the fence, overview of the lot) and pick the resolution, lens and mounting height to match. Our camera coverage calculator works through the same tradeoffs if you want a quick check before a site walk.
Low light is where most disappointing systems fall short. Cameras that look fine at noon produce smeared, noisy footage at 2 a.m. in a parking structure. We check the real light levels where each camera will be mounted and specify sensors and lenses rated for them. We use infrared illumination where color isn’t required, and wide dynamic range (WDR) where a camera faces a glass door with daylight behind it. In a lobby with a bright exterior door, WDR is what lets you see a face instead of a silhouette.
Recording: NVR, cloud, hybrid, and how long to keep footage
The first choice that really moves your budget is where the video gets stored.
Network video recorder. This is an appliance in the telecom room with local storage. It has the lowest ongoing cost, keeps full resolution, and keeps recording if the internet connection drops. Because you own the hardware, you also own drive replacements and firmware updates, plus the risk that the recorder leaves with an intruder unless it sits in a locked room.
Cloud recording. Cameras upload to a hosted platform, and you pay per camera per year. There’s no recorder to maintain, you get remote access from anywhere, and the vendor handles updates. Upload bandwidth becomes a design input, though, and the subscription is a permanent line in the operating budget.
Edge storage with cloud management. Cisco Meraki MV cameras store video on the camera itself and use the cloud for management, search and retrieval. That takes the recorder out of the room and keeps upload traffic low, since only the clips someone asks for leave the building. Several other platforms offer a middle path with a local gateway plus a cloud archive.
How long you keep footage starts as a policy decision and then turns into a storage calculation. Thirty days is a common starting point for commercial properties. Owners with a lender or insurer requirement, agencies with public records obligations, and housing programs with their own standards may need longer. We size storage from the camera count, resolution, frame rate and how much motion the scene sees. Then, once the system has run for two weeks, we confirm the actual retention and adjust it before closeout.
Network: PoE, VLANs, bandwidth and integration
Every IP camera is a network device, and we treat it like one. We put cameras on their own VLAN, separate from staff computers, tenant Wi-Fi and building automation, so a compromised camera has very little else on the network it can reach. Management interfaces aren’t exposed to the internet. We change and record default passwords before the camera leaves the bench, and the credentials go to the owner at turnover.
Power over Ethernet feeds most fixed cameras from the switch at 802.3af or 802.3at levels. PTZ cameras, multisensors with heaters, and cameras with built-in illuminators often need 802.3at or 802.3bt, and a switch budget that was sized for phones may not carry them. We count the PoE budget per switch, not per port, and specify Cat6A on runs that will carry higher power in bundles.
Camera cabling follows the same standard as the rest of the building: ANSI/TIA-568 balanced twisted pair, certified per link and labeled to the same scheme as the data drops. That way a camera run is documented just like a workstation run.
Where video ties into doors, the camera platform receives events from the access control system, so an operator can click a door alarm and see the clip. Intercom calls from a lobby panel can bring up the entry camera the same way. We configure that integration, test it door by door, and show it in the closeout package, instead of leaving it as something the software could do in theory.
NDAA Section 889 and 2 CFR 200.216 on federally funded work
If your project involves federal money, the camera manufacturer is a compliance question before it’s a technical one. Section 889 of the FY2019 NDAA bars federal agencies from procuring covered video surveillance and telecommunications equipment from Huawei, ZTE, Hytera, Hangzhou Hikvision, Dahua, and their subsidiaries and affiliates. 2 CFR 200.216 extends that prohibition to federal grant and loan funds. That’s how it reaches HUD-assisted housing, public agency projects with federal participation, and many campus and clinic projects.
White-label equipment is where people get caught. A large share of low-cost cameras and recorders sold under other brand names are manufactured by Hikvision or Dahua, and the box doesn’t say so. You can avoid that by specifying the actual manufacturer and keeping the paperwork. We provide manufacturer letters and model-level documentation with submittals for Axis, Hanwha Vision, Avigilon, Verkada, Cisco Meraki MV, and Ubiquiti UniFi Protect. We verify each model at the time of submittal, because product lines change. Our guide to NDAA Section 889 compliant cameras in California walks through how to audit an existing system and what language to put in the specification.
Privacy, signage and audio in California
Cameras belong where people don’t have a reasonable expectation of privacy: entrances, corridors, lobbies, parking, loading docks, mail and package rooms, elevators, mechanical rooms, and building perimeters. They don’t belong in restrooms, locker rooms or changing areas, and they shouldn’t be aimed into unit interiors. In multifamily and senior housing we avoid views that look through unit doors or windows. We also document the field of view of every camera, so the owner can show what is and isn’t recorded.
Audio is a separate question. California treats the recording of private conversations differently from video, and consent rules apply. Our default is to leave microphones disabled on commercial camera systems unless the owner’s counsel has reviewed the use, and to note the setting in the closeout.
Posting signs that say the property is under video surveillance is good practice for employee and visitor awareness, and some owner policies and insurers require it. Keep in mind that cameras are only one part of a building’s security plan. They work best alongside access control and a clear plan for who reviews footage and when.
Next step
Share the floor plan, the areas you need covered, and whether federal funds are involved, and we’ll come back with a camera schedule and a bid. You can upload drawings through request a bid. General contractors building a Division 28 bid list can start at for general contractors for our prequalification packet.