Running a Mixed-Brand Camera Fleet in One SSMS Console

Many sites grow over the years. One branch buys Hikvision, another buys Dahua, and an older building still has Axis cameras. This is called a mixed fleet. SSMS shows the listed brands side by side on one live wall. This guide explains how to keep a mixed fleet tidy and easy to run.

What SSMS does with a mixed fleet

SSMS has native support for these brands: Hikvision, Dahua, Axis, Uniview, Bosch, Hanwha (Wisenet), Vivotek, Reolink and TP-Link VIGI. It also works with other cameras through ONVIF or an RTSP stream.

• ONVIF is an open standard. It lets cameras and software from different makers work together.
• RTSP is a stream address that starts with rtsp://. Many cameras and NVRs publish one for live video.

For example, Hikvision cameras at head office and Dahua cameras in the branches can sit next to each other on the same wall. Operators no longer switch between each brand's own viewer.

What differs between brands

Even on one wall, cameras from different makers do not look or behave the same. Expect differences in:

• Picture: colour, sharpness and brightness vary.
• Night view: some cameras switch to black and white earlier than others.
• Field of view: how wide a camera sees depends on its lens.
• Default settings: each maker ships its own stream and time settings.

These differences are normal. The goal is to make the important things the same everywhere: names, clocks and stream settings.

Use one naming rule for every camera

Operators read camera names all day. Mixed naming styles slow them down. Agree one rule, and ask your Skyline engineer to name cameras that way.

A simple rule is site, then area, then number. For example: HQ-Gate-01 or BR2-Store-03. Keep the brand and model out of the name. Put them in the camera register instead.

Keep every clock the same

Every camera, every NVR and the SSMS server has its own clock. If the clocks differ, one event shows different times on different cameras. That makes reviews and evidence confusing.

Use NTP on every device. NTP (network time protocol) keeps device clocks in step with one time source. Ask IT to point all cameras, NVRs and the server at the same source. Check the clocks again after a power cut or a firmware update.

Agree the stream settings

Two settings matter most:

• Bitrate: how much data a camera sends each second, measured in Mbps (megabits per second). A higher bitrate gives more detail, but needs more storage and network capacity.
• Codec: the method used to compress video. H.264 is common. H.265 is newer and usually needs less bitrate for a similar picture.

Each brand ships different defaults. Agree target settings for each camera type with IT and Skyline. Your storage estimates then stay accurate. See estimating storage and bandwidth.

Keep a camera register

A camera register is a simple table of every camera you own. It speeds up support calls, upgrades and checks. Firmware means the software inside the camera.

Keep the register where IT and supervisors can find it. Update it every time a camera is added, moved or replaced.

Update firmware safely

1. Read the maker's release notes first.
2. Update one camera as a test.
3. Check that it still shows on the live wall and that its recording plays back.
4. Tell Skyline before you update many cameras at once.
5. Record the new firmware version in the register.

Replacing a camera with a different brand

Before you buy, check the new model against the supported list. If it is not one of the named brands, check that it supports ONVIF or offers an RTSP stream. Then tell your Skyline engineer, so the new camera is added and named by your rule. See choosing new cameras.

Quick checklist

• Every brand is on the supported list, or connects through ONVIF or RTSP.
• One naming rule is used for every camera.
• Every device uses the same NTP time source.
• Stream settings are agreed for each camera type.
• The camera register is up to date.
• Firmware is tested on one camera before a wider update.