SESP Solution Center · Video Surveillance

Commercial IP Video SurveillanceThe Professional Guide to System Design, Management, and Lifecycle Value

A practical guide for security dealers, integrators, and commercial decision-makers. It covers architecture, cameras, video management, storage, networking, analytics, cloud services, and the service models that keep systems performing over time.

  • 10 chapters
  • Featured MyDW case study
  • For dealers, integrators & commercial stakeholders
Isometric cutaway of a commercial building with an integrated IP video surveillance system A three-story commercial building drawn in isometric projection, with its front corner cut away to reveal a ground-floor operations room and the floor slabs above. Four IP cameras, at the main entrance, on the front facade, inside the operations room and on a parking-lot pole, each show a discreet coverage zone. Concealed cable runs return to an equipment rack containing PoE network switches, recording servers and a UPS, beside an on-site video management workstation. A network riser carries the uplink through the roof to an off-site remote monitoring console that shows camera and system health status. 01 02 03 04
Integrated IP video system — conceptual cutaway
  1. IP cameras & coverage zones
  2. PoE network switching
  3. Recording & video management
  4. Remote system health monitoring
Concealed cable runsNetwork riser & uplink
Overview

What is commercial IP video surveillance?

Commercial IP video surveillance is a network-based security system. Cameras send digital video over an IP network to recording and management software. Authorized users can then view, search, export, and analyze that video from wherever they work. A professional system is more than cameras and a recorder. It is designed infrastructure: imaging, networking, storage, video management software (VMS), cybersecurity controls, and an ongoing service plan, all chosen to fit one organization’s risks and operations.

That last part is where most systems succeed or fail. Two buildings can have the same camera count and the same brands and still get very different results. The difference usually comes from design choices made before installation, and from whether anyone watches the system’s health afterward. A camera that went offline in March is no help when an incident happens in June.

This guide is written for the people who design, sell, install, and support these systems: security dealers and systems integrators. It is also written for the facility owners, security directors, IT teams, and consultants who work with them. It is vendor-neutral where the principles are universal. Where a specific product helps explain a real design or business decision, we use examples from Digital Watchdog (DW), a manufacturer that Southeast Security Products (SESP) represents across the Southeast.

How this guide is organized

The ten chapters follow the way a system comes together and then lives on. Chapters 01 through 05 cover the foundation: architecture, cameras, video management, storage, and the network. Chapters 06 through 08 cover intelligence and scale: analytics, cloud and hybrid models, and multi-site enterprise operations. Chapter 09 covers what happens after commissioning: maintenance, lifecycle services, and how dealers build legitimate recurring revenue. It includes a featured case study on cloud-connected health monitoring across an installed base of DW recorders. Chapter 10 brings it together with application guidance, modernization strategy, and a platform evaluation checklist.

Chapter 01 · Foundations

Understanding Professional IP Video Surveillance

Modern surveillance is a software-defined network application. It is no longer a closed loop of cameras wired to a box. That change alters how systems are designed, who has to take part, and what customers should expect after installation.

From analog CCTV to network video

For most of its history, commercial video was closed-circuit television (CCTV). Analog cameras sent a signal over coaxial cable to a monitor, and later to a digital video recorder (DVR). The DVR digitized the video and wrote it to local hard drives. Resolution was limited, each camera needed its own cable home, and growing the system meant adding more recorders.

HD-over-coax technologies later raised analog resolution a great deal and extended the life of coaxial infrastructure. Many of these hybrid and HD analog systems are still in service. They matter to the strategy in this guide because they are part of the installed base that dealers support.

IP cameras changed the model. An IP camera digitizes and compresses video itself, then sends it as data over a standard Ethernet network. The network video recorder (NVR) arrived as the IP equivalent of the DVR: an appliance that records network cameras. As systems grew, recording moved onto general-purpose servers running video management software (VMS). VMS separates the recording logic from any single piece of hardware. It adds multi-server management, user permissions, integrations, and analytics.

The newest layer is cloud connectivity. It covers remote access, centralized administration, health monitoring, and, for some deployments, cloud-hosted recording. Chapter 07 explains why these cloud functions are different from each other. For now, the key point is that today’s systems are rarely isolated. They are connected, managed assets.

The core components and how they interact

A professional system has five layers, and each one depends on the others.

  1. Connectivity & servicesRoleExtends access and visibility beyond the siteTypical componentsRemote access, cloud management, health monitoring, integrations
  2. ManagementRoleControls devices, users, recording rules, playback, and eventsTypical componentsVMS software, client applications, mobile apps
  3. Recording & storageRoleWrites, protects, and retains videoTypical componentsNVRs, recording servers, storage arrays, edge storage
  4. TransportRoleMoves video and power between devicesTypical componentsPoE switches, cabling, fiber uplinks, routers, firewalls
  5. CaptureRoleConverts a scene into compressed digital videoTypical componentsIP cameras, encoders for analog cameras, edge analytics
The five layers of a professional IP video system, shown from the capture layer (bottom) to connectivity and services (top).

A weakness in any layer limits the whole system. A sharp camera on an undersized switch drops frames. A well-designed VMS on undersized storage keeps fewer days of video than the customer was promised. A healthy system with no monitoring can fail quietly. Professional design means engineering each layer for the others.

Professional systems vs. consumer camera systems

Consumer and small-office camera kits have made video familiar and inexpensive. They are designed for convenience: quick setup, an app, and often cloud clips. Commercial systems answer to different requirements.

Consumer / DIY systems vs. professional commercial systems
RequirementConsumer / DIY systemsProfessional commercial systems
Design basisProduct defaultsSite assessment, risk, and operational goals
Users and permissionsOne account or a few shared loginsMany users with role-based access and audit trails
RetentionWhatever the device or plan providesDefined by policy, insurance, counsel, or regulation, then verified
NetworkShares the business or home networkPlanned bandwidth, segmentation, and IT coordination
IntegrationLimitedAccess control, intrusion, alarms, and business systems
SupportSelf-serviceService agreements with defined responsibilities
LifecycleReplace when it breaksPlanned updates, maintenance, and modernization

The gap is not mainly about image quality. It is about accountability. A commercial system has to produce usable evidence when it matters, and someone has to be responsible for making sure it can.

Five principles that run through this guide

  • Design comes first. Camera choice, storage, and network capacity all follow from what the system must accomplish. Chapters 02 through 05 develop this.
  • Reliability is engineered. It comes from proper power, redundancy where it is justified, and verified recording behavior. It does not come from specifications alone.
  • Scalability is cheapest at the start. Choosing a platform and infrastructure with room to grow costs far less than migrating later. Chapters 03 and 08 cover this.
  • Cybersecurity is a lifecycle job. Cameras and recorders are network devices with firmware, credentials, and remote access paths. They must be hardened at installation and maintained after. Chapter 05 covers this.
  • Systems need continuous care. Drives wear out, cameras get bumped or blocked, firmware ages, and settings drift. A system nobody watches gets worse over time. Chapter 09 shows how proactive service changes that.

With that foundation in place, the next chapter turns to the capture layer, where most design decisions start: the camera, and the scene it must cover.

Chapter 02 · Capture

Cameras, Imaging Technology & Coverage Design

The right camera is the one that produces the detail an operator needs, in the scene’s real lighting, at the distance that matters. Resolution is one input to that decision. It is never the whole answer.

Camera types and form factors

Camera form factors compared
Form factorStrengthsTypical usesDesign considerations
Dome / turretDiscreet, vandal-resistant options, flexible mountingInteriors, corridors, retail floors, entrancesDome bubbles can catch IR reflection; turrets avoid this
BulletLong-range lenses, visible deterrentPerimeters, parking, building exteriorsMore exposed to tampering and spider webs near IR
PTZ (pan-tilt-zoom)Operator-directed coverage, optical zoomLarge open areas, campuses, monitored sitesCovers one view at a time; pair with fixed cameras for continuous coverage
Multisensor panoramicWide coverage from one mount and one cableIntersections, lots, warehouses, large roomsCheck per-sensor resolution and VMS licensing per stream
Fisheye (360°)Full-room awareness from a ceiling mountRetail, lobbies, open officesDetail falls off toward the edges; dewarping support varies
SpecialtyPurpose-built performanceLicense plate recognition, thermal, explosion-proofUsually justified by a specific requirement

PTZ cameras deserve one caution. A PTZ pointed the wrong way records nothing useful about the area it isn’t facing. Unless an operator controls it, or presets and tours are planned carefully, a PTZ should add to fixed coverage, not replace it.

Sensors, resolution, and lenses

The image sensor converts light into an electrical signal. Sensor size and pixel size affect low-light sensitivity: larger pixels gather more light. Resolution describes how many pixels the sensor produces, such as 2 MP (1080p), 4 MP, 5 MP, or 8 MP (4K). More pixels spread across the same field of view give more detail. The same pixels spread across a wider field of view give less detail per subject.

The lens decides that trade-off. Focal length sets the field of view: shorter focal lengths see wider, longer ones see narrower and farther. Varifocal lenses let installers adjust the view on site. Motorized varifocal lenses allow remote adjustment and refocusing. Fixed lenses cost less and work well when the scene is predictable.

Why megapixels alone don’t determine evidence quality

Useful evidence depends on pixel density: how many pixels land on the subject. It also depends on the conditions in which those pixels are captured. A 4K camera covering a wide parking lot may put fewer pixels on a face at 60 feet than a 2 MP camera aimed at a doorway puts on a face at 10 feet. Higher resolution also brings costs. It increases bitrate and storage, and it can perform worse in low light if smaller pixels gather less light.

The practical approach is to define the task for each camera, then design for the pixel density the task needs.

DORI: detect, observe, recognize, identify

DORI is a framework from the IEC 62676-4 standard for video surveillance systems. It ties operational tasks to pixel density on the subject, measured in pixels per meter (px/m) at the target distance.

DORI levels and pixel density (IEC 62676-4)
DORI levelWhat the operator can doPixel density (IEC 62676-4)
DetectTell that a person or vehicle is present25 px/m
ObserveSee general characteristics such as clothing and activity62 px/m
RecognizeDecide with confidence whether a person is someone already known125 px/m
IdentifyEstablish identity beyond reasonable doubt250 px/m

Manufacturers often publish DORI distances for each camera and lens setting. Treat these as best-case figures, measured in good conditions. Lighting, angle, motion, compression, and weather all reduce effective detail. A scene that needs identification at an entrance should be designed with margin, not at the limit of a data sheet. Design calculators can estimate pixel density during planning. A test image during commissioning confirms it.

Frame rate, compression, and motion

Frame rate is the number of images per second (fps). Many commercial scenes record well at 10 to 15 fps. Fast-moving subjects, cash handling, and gaming environments may justify more. Higher frame rates increase bitrate and storage roughly in proportion, so they should match the task. Shutter speed matters as much as frame rate for capturing moving subjects without blur.

Compression (H.264, H.265, and manufacturer “smart codec” variants) is covered in Chapter 04 because its biggest effect is on storage. At the camera, compression settings decide how much detail survives in busy or low-light scenes. Over-aggressive compression is a common cause of blurry footage from capable cameras.

Low light, infrared, and wide dynamic range

Lighting causes more disappointing footage than any other factor. Built-in infrared (IR) illuminators let cameras record in darkness, usually in monochrome. IR range claims assume ideal reflectivity. Glass, rain, and nearby surfaces that reflect IR back into the lens all reduce it. Some cameras use larger sensors and image processing to keep producing color at night when some ambient light is available.

Wide dynamic range (WDR) handles scenes with bright and dark areas at once. Examples include a lobby facing sunlit glass doors or a loading dock opening onto daylight. Without effective WDR, the subject in the doorway turns into a silhouette. True multi-exposure WDR and digital enhancement perform differently, so real-scene testing is worth the effort for critical entrances.

Site assessments should look at lighting by zone and time of day. Sometimes the best camera upgrade is a supplemental light fixture.

Environmental and durability ratings

Outdoor and harsh-environment cameras carry ratings that matter for reliability:

  • IP rating (ingress protection): resistance to dust and water. IP66 and IP67 are common for outdoor cameras.
  • IK rating: resistance to impact. IK10 is the common vandal-resistance benchmark.
  • Operating temperature range: important in direct sun, unconditioned spaces, and cold storage.
  • Corrosion resistance: relevant in coastal, industrial, and chemical environments.

In the Southeast, heat, humidity, salt air, and severe storms make these ratings, and surge protection for outdoor runs, practical concerns rather than spec-sheet details.

Practical camera-selection examples

Main entrance, identification required

A fixed camera at a modest angle and close distance, sized to reach identification-level pixel density on faces. Strong WDR is needed if the entrance faces daylight. A second, wider camera gives context on the approach.

Parking lot, general awareness

Multisensor or wide-angle cameras for detection and observation, plus dedicated cameras at the entrances and exits where people and vehicles are funneled. Expecting identification across an entire open lot is usually unrealistic and expensive.

Vehicle gate

A purpose-built license plate recognition camera with proper shutter control and a narrow view, separate from the overview camera. General-purpose cameras rarely read plates reliably at speed or at night.

Warehouse aisles

Cameras with corridor-format (vertical) image orientation, which fills more of the frame with the long, narrow aisle and wastes fewer pixels on racking.

Once the cameras are selected, the next question is how their video will be managed, searched, and used. That is the job of the VMS.

Chapter 03 · Management

Video Management Systems & Platform Architecture

The VMS is the operating system of a surveillance deployment. It decides how well a system scales, how easily operators find what they need, and how long the investment stays supported. Choosing a platform is one of the most consequential decisions in any project.

What a VMS does

At its core, a VMS does six jobs:

  • Device management: discovers cameras, applies settings, manages firmware where supported, and tracks status.
  • Recording: applies recording rules (continuous, scheduled, motion- or event-based) and manages where video is stored and for how long.
  • Viewing and playback: delivers live and recorded video to desktop, web, and mobile clients, with timeline search, multi-camera playback, and video walls.
  • Users and permissions: controls who can see which cameras and who can play back, export, or change settings.
  • Events and alarms: turns motion, analytics, input triggers, and integrated-system events into alerts, bookmarks, and actions.
  • Evidence handling: exports video in usable formats with watermarking, verification, or audit information where the platform supports it.

Platforms vary widely in how well they do each job. In a demonstration, the differences show up fastest in search and playback, the tasks operators repeat every day.

On-premises architecture: appliances and servers

Recording on site takes two main forms.

Embedded NVRs are purpose-built appliances with an integrated operating system, storage bays, and often built-in PoE ports. They are simple to deploy and well suited to small and mid-sized single sites. Their limits are fixed channel counts and processing power, and they tend to be less flexible for integrations.

Server-based VMS runs on general-purpose or purpose-built server hardware. It scales by adding servers, supports larger camera counts and storage arrays, and usually offers deeper integration and multi-site capabilities. Many manufacturers sell pre-configured servers with their VMS installed. These reduce deployment variables while keeping server-class architecture.

Many platforms separate the recording server (which ingests and stores video) from the client (the application operators use). Some also run management or directory services that let many recording servers act as one system. Knowing how a platform divides these roles explains how it behaves when a server or network link fails.

Users, permissions, and accountability

Commercial organizations need more than a shared admin password. A capable VMS supports role-based access control. A front-desk user might view lobby cameras live but not export. An investigator might search and export across a site. An administrator manages configuration. Integration with directory services such as Active Directory, where supported, makes onboarding and offboarding easier. Audit logs that record who viewed, exported, or changed what are increasingly expected in privacy-sensitive environments.

Interoperability and the reality of ONVIF

ONVIF is an industry forum that publishes interface specifications, organized as profiles, for IP security products. Profile S covers basic video streaming. Profile T covers advanced video streaming, including H.265 and metadata. Profile G covers edge storage and retrieval. Profile M covers analytics metadata. A product conformant to the same profile as the VMS should support that profile’s baseline functions.

ONVIF’s limits are practical ones:

  • Conformance covers only the profile’s defined functions. Manufacturer-specific features often fall outside it.
  • Advanced analytics events, special PTZ behaviors, and camera-specific configuration may need a native driver or a validated integration.
  • Two conformant products can still behave differently in the field, especially across firmware versions.

The working rule: ONVIF is a safety net for interoperability, not a guarantee of full functionality. For cameras that matter, confirm the integration level with the VMS manufacturer, and test before committing a large deployment.

Integrations

Video becomes more valuable when it connects to other systems. Common integrations include access control (video linked to door events), intrusion panels (alarm verification), intercoms, license plate recognition, point-of-sale transaction overlays, and building systems. Integration depth varies. It can be anything from a simple event trigger to a full two-way, bidirectional integration. Evaluate the platform’s certified integrations and open APIs against the systems the customer already runs.

Scalability, licensing, and long-term support

Three platform questions decide total cost of ownership more than the opening price does.

Can it grow without migrating?

A platform that fits a 16-camera site should be able to add servers, sites, and users without being replaced. Ask about practical limits, multi-server behavior, and failover options.

How is it licensed?

Common models include perpetual per-camera licenses, subscriptions, and hybrid models that bundle software with hardware or cloud services. Each has different effects on upfront cost, renewal cost, and expansion cost. Model total cost over the expected life of the system, not just year one.

How is it supported?

Look at the manufacturer’s update cadence, backward compatibility, end-of-life policies, cybersecurity disclosure practices, and technical support access. A VMS that stops receiving updates becomes both an operational and a security liability.

DW Spectrum as an example of open VMS architecture

DW Spectrum Professional is Digital Watchdog’s VMS. Before version 6.0 it was known as DW Spectrum IPVMS. It is a useful example of several principles in this chapter. The platform uses an open, cross-platform architecture. Servers run on Windows or Ubuntu Linux, and client applications are available for desktop, web, and mobile. Remote access runs through DW Cloud. Multiple servers can be merged into one system with centralized administration, custom user roles, and video wall capabilities.

DW pairs the software with its Blackjack server line, which ships with DW Spectrum preloaded. That gives integrators a server-class option without assembling hardware and software separately. Multi-site, cloud-managed operation through DW Spectrum Enterprise is covered in Chapter 08. To see how SESP supports the DW line, visit our Digital Watchdog manufacturer page.

No single VMS fits every project. The point of the example is the questions it raises: whether the platform is open, how it scales, how it is licensed, and whether its maker will support it for the life of the system.

A VMS can only keep what the storage behind it can hold. The next chapter covers recording infrastructure and retention planning.

Chapter 04 · Recording

Recording Infrastructure, Storage & Retention

Storage is where the promises made in a proposal meet reality. Size it too small and footage gets overwritten before anyone asks for it. Size it without real assumptions and nobody can explain why a 30-day system holds only 19 days. Good storage design starts with the retention requirement and works backward.

Where video gets recorded

Recording approaches compared
ApproachHow it worksStrengthsLimitations
Embedded NVRAppliance records cameras to internal drivesSimple, cost-effective for smaller sitesFixed capacity and channel count
Server-based recordingVMS recording servers write to internal or attached storageScales, supports RAID and failover optionsMore design and IT involvement
Edge storageCamera records to an onboard SD card or SSDKeeps recording during network or server outagesLimited capacity; retrieval and management at scale are harder
Cloud / hybrid recordingSome or all video is stored off siteOff-site copy, less on-site hardwareDepends on bandwidth and subscription terms (see Chapter 07)

Edge storage works best as redundancy for critical cameras, not as the main recording method for a commercial system. Where the camera and VMS support it, cameras record locally during an interruption and the VMS retrieves the gap once the connection returns. That pairing closes an important failure gap at modest cost.

What drives storage demand

Storage use comes from bitrate multiplied by recording time. Bitrate depends on several variables that interact:

  • Resolution: more pixels means more data, all else equal.
  • Frame rate: storage rises roughly in proportion to fps.
  • Compression codec and settings: covered below.
  • Scene activity and complexity: moving foliage, traffic, rain, and low-light noise all raise bitrate, sometimes sharply. A quiet hallway compresses far better than a busy parking lot at night.
  • Recording mode: continuous recording is predictable. Motion- or event-based recording saves space but is harder to forecast.

That is why a single “GB per camera per day” number from a data sheet rarely matches the field. The most reliable inputs are measured bitrates from similar cameras in similar scenes, or bitrates observed during commissioning.

Compression: H.264, H.265, and smart codecs

H.264 (AVC) has long been the most widely supported codec in surveillance. H.265 (HEVC) is designed to reach comparable image quality at a meaningfully lower bitrate, which reduces both storage and bandwidth. Actual savings vary with the scene, the encoder, and the settings. H.265 also asks more of decoding hardware, so confirm support across the whole chain: cameras, VMS, servers, and client workstations or mobile devices.

Manufacturer “smart codecs” go further. They vary bitrate and frame structure based on scene activity, which can cut storage a great deal in low-activity scenes. Because they behave differently in busy scenes, size storage using conservative assumptions, not the best case.

Storage resilience: RAID

RAID combines drives so the array can survive a drive failure.

Common RAID levels for surveillance storage
RAID levelDrive-failure toleranceCapacity efficiencyNotes for surveillance
RAID 5One driveHighRebuilds on large drives take a long time; a second failure during rebuild loses the array
RAID 6Two drivesModerately highCommon choice for larger surveillance arrays
RAID 10One drive per mirrored pair50%Strong write performance; higher cost per usable terabyte

Use surveillance-rated or enterprise drives built for continuous writing. Monitor drive health actively. RAID protects the recording only if someone notices and replaces a degraded drive before the next one fails.

Redundancy is not backup

This distinction causes real losses in the field:

Redundancy

RAID, failover recording servers, and edge recording keep a system recording through component failures.

Backup

A separate copy of selected video, kept somewhere else, that survives the loss of the primary system.

Disaster recovery

The plan for restoring operations after a major event such as fire, flood, theft, or ransomware.

RAID does not protect against a stolen recorder, a server fire, corruption, or an administrator mistake. Customers with high-value evidence needs should define which video gets backed up, where it goes, and how quickly it must be recoverable.

Retention: start with the requirement

Retention needs come from the customer’s own circumstances. These include internal policy, insurance requirements, legal counsel’s guidance, contractual obligations, and, in some industries or jurisdictions, regulation. No single retention period is right for every commercial facility. The dealer’s job is to make sure the requirement is identified, written down, and confirmed by the customer before storage is sized. Then the system must be verified to actually meet it.

The design sequence is straightforward:

  1. Confirm the required retention period, in writing.
  2. Estimate the realistic average bitrate per camera, by camera type and scene.
  3. Calculate daily storage per camera, then for the whole system.
  4. Multiply by the retention period.
  5. Add a planning margin for scene variability and growth.
  6. Account for RAID overhead and usable versus raw capacity.
  7. After commissioning, check actual retention against the requirement.

Storage-planning example

The example below shows the method. Its numbers are teaching assumptions, not a recommendation for any real site.

Assumptions

  • 40 cameras recording continuously.
  • Average bitrate of 4 Mbps per camera (assumed blended average across scenes, using H.265).
  • Required retention: 30 days (example only).
  • Planning margin: 25%.

Calculation

Storage calculation, 40-camera example
StepCalculationResult
Total recording bitrate40 cameras × 4 Mbps160 Mbps
Data per day160 Mbps × 86,400 seconds ÷ 8 bits per byte1,728,000 MB ≈ 1.73 TB per day
Retention requirement1.73 TB × 30 days≈ 51.8 TB
With 25% planning margin51.8 TB × 1.25≈ 64.8 TB usable

That 64.8 TB is usable capacity, after RAID. In a RAID 6 array, two drives’ worth of capacity goes to parity. For example, twelve 8 TB drives in RAID 6 give about 80 TB of nominal usable space before file-system overhead. Drive makers quote capacity in decimal terabytes, while operating systems often report binary units, so the displayed figure will look smaller.

Now change one assumption. If nighttime noise and rain push the real average to 6 Mbps, the same system needs about 97 TB usable for the same 30 days. Without that headroom, it would hold roughly 20 days. This is why measured bitrates and post-commissioning checks matter.

Storage and cameras both depend on the network that connects them. That is the subject of Chapter 05.

Chapter 05 · Transport & security

Network Infrastructure & Cybersecurity

An IP video system is a high-bandwidth, always-on network application, and it is only as reliable as the network under it. It is also a set of connected devices that attackers look for. This chapter covers the network decisions that matter most for video, and the security practices that need to last the life of the system.

Power over Ethernet

PoE sends data and power over one Ethernet cable, so cameras don’t need a local power circuit. IEEE standards define the power classes:

IEEE PoE power classes for video devices
StandardCommon namePower at the switch portPower available at the deviceTypical video uses
IEEE 802.3af (Type 1)PoE15.4 W12.95 WMany fixed dome and bullet cameras
IEEE 802.3at (Type 2)PoE+30 W25.5 WCameras with strong IR, heaters, or motorized lenses; many PTZs
IEEE 802.3bt (Type 3)PoE++60 W51 WMultisensor cameras, larger PTZs
IEEE 802.3bt (Type 4)PoE++90 W71.3 WHigh-power PTZs and devices with heaters or blowers

Check each camera’s real worst-case draw, including IR at night and heaters in cold weather. Then check two separate switch limits: the power each port can deliver and the switch’s total PoE budget. A 24-port switch with PoE+ on every port can’t power 24 cameras at full PoE+ load unless its total budget reaches 720 W. Running out of budget is a common cause of cameras that reboot at night or never power up.

Copper Ethernet is limited to 100 meters (328 feet) per channel. Longer runs need fiber, PoE extenders, or an intermediate switch.

Managed switching and why it matters

Unmanaged switches can work for very small, isolated systems. Commercial video benefits from managed switches, which provide:

  • VLAN support to separate video traffic.
  • IGMP snooping where multicast is used.
  • Quality of Service (QoS) controls.
  • Port-level PoE control and monitoring, including remote power-cycling of an unresponsive camera.
  • Visibility into link status, errors, and traffic, which helps with troubleshooting and proactive service.
  • Redundancy protocols such as Rapid Spanning Tree and link aggregation for resilient topologies.

Signamax, a networking manufacturer SESP represents, makes managed and unmanaged PoE switches, industrial-temperature switches for harsh locations, fiber media converters, and related connectivity products used in IP surveillance designs. Whatever the brand, the selection criteria are the same: PoE budget, port count with spare capacity, uplink speed, environmental rating, and manageability.

Fiber, uplinks, and topology

Fiber handles distances and electrical environments that copper can’t. Single-mode fiber covers long campus and building-to-building runs. Multimode fiber suits shorter runs inside buildings. SFP ports on switches make it easy to add fiber uplinks.

Uplink capacity is easy to overlook. Edge switches gather camera streams and send them to recording servers through uplinks. Add up the bitrates of every camera behind each uplink, add live-viewing traffic, and make sure the uplink and core links have real headroom. As camera counts grow, 1 Gbps uplinks can become bottlenecks well before edge ports run out.

  1. CamerasOn a dedicated video VLAN
  2. PoE edge switchesManaged; power budget with headroom
  3. Fiber / uplinksSized for every stream behind them
  4. Core & recordingRecording servers or NVRs; VMS
  5. FirewallRestricted routing; outbound-only to required cloud services
  6. Cloud relay / VPNSecured remote access; no inbound port forwarding
A segmented video network: camera traffic stays on its own VLAN, uplinks carry aggregated streams to recording, and remote access leaves through a secured, outbound-only path.

Bandwidth planning

Plan for peak load, not average load. During an incident, several operators may pull live and recorded video from many cameras at once. Remote viewers over the internet add upstream demand at the site. Most VMS platforms reduce this with multiple streams: a high-resolution stream for recording and a lower-resolution stream for multi-camera viewing and remote access.

Unicast vs. multicast. With unicast, each viewer gets a separate stream. That is fine for most commercial deployments. Multicast sends one stream that many viewers can receive, which helps in large monitoring centers. It needs network configuration and support from the camera and VMS.

Segmentation and VLANs

Cameras and recorders should sit on their own network segment, typically a dedicated VLAN, with tightly controlled routing to other networks. Segmentation:

  • Keeps video traffic from competing with business applications.
  • Limits how far an attacker can move from a compromised camera.
  • Simplifies firewall rules and traffic policies.
  • Matches the IoT segmentation policies many IT departments already require.

When cloud services are used, restrict outbound internet access from the video segment to the specific services the system needs.

Power resilience

A camera is only as available as its power. Put uninterruptible power supplies (UPS) on PoE switches, recorders, and core network equipment. Size runtime to the customer’s continuity needs. In storm-prone parts of the Southeast, surge protection on outdoor camera runs and on incoming service lines also prevents a common category of failures.

Working with IT

On most commercial projects, IT is a stakeholder, not a gatekeeper to get past. Coordinate early on:

  • VLAN and IP addressing plans (static, reserved DHCP, or managed ranges)
  • Firewall rules for remote access and cloud-connected services
  • Server hosting, virtualization, and patching responsibilities
  • Directory integration for user authentication
  • Change-management and update windows

Integrators who show up with a clear network design document earn credibility and move faster through approvals.

Device hardening and lifecycle cybersecurity

Security cameras and recorders are network computers. Treat them that way at installation and for as long as they are in service.

At installation

  • Change every default password. Use unique, strong credentials, stored securely.
  • Disable unused services, protocols, and ports.
  • Apply current firmware and software before go-live.
  • Configure role-based user accounts. Avoid shared admin logins.
  • Enable encryption for management and video transport where supported.
  • Set accurate time synchronization. Evidence depends on reliable timestamps.

Remote access

  • Never expose cameras or recorders directly to the internet through port forwarding.
  • Use the manufacturer’s secured cloud relay, a VPN, or another IT-approved method.
  • Require multi-factor authentication for remote and administrative access where the platform supports it.

Throughout the lifecycle

  • Track firmware and software versions, and apply security updates on a defined schedule.
  • Review user accounts periodically. Remove access for people who leave.
  • Watch for end-of-support announcements on devices and operating systems.
  • Document the configuration so it can be restored after a failure.

The last point leads into a recurring theme: cybersecurity can’t be finished at commissioning. It is an ongoing service, and Chapter 09 treats it as one.

With the infrastructure in place, the system can do more than record. The next chapter looks at analytics.

Security Manufacturer Representatives

Let Southeast Security Help You

Trusted security manufacturer representatives serving the Southeast U.S., connecting dealers and endu-users with top-tier security and access control equipment brands.

Security Manufacturer Representatives

Make an appointment

Get a free demonstration

Call us

954.786.5900

Get Trained In the Latest Technology

The security industry always has new leading-edge technology. We offer training on a number of products and technologies. If you would like to learn more, contact us today!

Camera Systems

IP video security and high-definition analog systems have the best resolution in the market.  We represent some of the leading manufacturers and can put your whole solution together for your next job. 

Door Entry Systems

Access control enables higher security with reporting events of people going through entry and exit points. Explore the latest technology including facial recognition and wireless access.

Fire & Alarm Systems

Keep your loved ones and belongings safe by exploring our exceptional range of fire and alarm systems. 

All Applications

To do any job properly, you need the right tools Make your next job a snap with tools designed for the low voltage industry.

How can we help you

Bring In the Security Experts

It is crucial to understand the requirements of the customer before designing a system. Our salespeople are trained in assisting with live demonstrations for end-users in the commercial, government, and high-end residential markets, and are available to assist in learning more about some of the leading manufacturers in the world.

About us

Who we are

We are a professional sales organization representing manufacturers in the commercial security market. Our expertise includes Video Surveillance, Access Control, Audio/Video, Intrusion and Home/Commercial Automation

Our mission is to contribute to the development and growth of our represented brands through the utilization of demonstrated sales, marketing and technical expertise. We concentrate on increasing the profits of companies we work with by increasing revenues and decreasing expenses.

Get a copy of our pricebook

Get EXCLUSIVE ACCESS to our catalogue of products when you sign up now

News

Blog

Boost Your Jobsite Efficiency with the DYMO Rhino 4200 Label Maker

Boost Your Jobsite Efficiency with the DYMO Rhino 4200 Label Maker

Improve jobsite efficiency with the DYMO Rhino 4200 Industrial Label Maker. Built for security integrators and low-voltage contractors, this rugged labeling solution helps technicians identify cables, organize panels, and produce durable, professional labels that simplify installation, troubleshooting, and future maintenance.

read more
Master Cable Organization with the Jonard Cable Comb® Tool

Master Cable Organization with the Jonard Cable Comb® Tool

Simplify cable management with the Jonard Cable Comb Tool. Designed for structured cabling, security, and low-voltage installations, this practical tool helps technicians organize cable bundles, improve installation quality, and reduce jobsite labor while delivering cleaner, more professional results.

read more

Reviews

What our clients say

David, Henry

I always have the Southeast team with me on job sites.  They always have the right product for my customer’s application!

Driver, Lisa

When I need my sales staff trained on the latest products Southeast delivers. Their knowledge of the industry shines through.

Jenkins, Jackson

Southeast Security Products is the company I turn to when I need a quality product.   As always, they represent premier manufacturers