Replacing analog monitoring with IP in the company

Replacing analog monitoring with IP does not come down to image quality, but rather concerns the architecture: the method of transmission, power supply, recording and integration possibilities. This article shows what this means when modernising, when the old system is really enough and how to carry out the replacement in stages.

Disclaimer. The article describes the technical side of modernisation. Video monitoring involves obligations arising from personal data protection regulations, and if it covers employees, also from labour law. This is not legal advice. The assessment of a specific case is the responsibility of the lawyer or data protection officer.

The difference is architectural, not pictorial

The conversation about monitoring modernisation usually starts with resolution, although this is the least important of the differences between the two architectures.

In an analog system, the camera sends a signal to the recorder via a separate path, and the recorder becomes the place where decoding, recording and viewing takes place, so the camera remains a simple and dependent device.

In an IP system, a camera is a network device that has its own address and software, encodes the image itself and sends it through the same infrastructure that the company uses for other purposes.

This one difference results in everything else, as the comparison below shows.

Area	Analog	IP
Broadcast	separate track for each camera	shared network
Power supply	separate cable or power supply at the camera	usually over the same cable (PoE)
Intelligence	in the recorder	in the camera
Expansion	limited by the number of recorder inputs	limited by network and recording capacity
Remote access	by the recorder	over the network, at the system level
Integration	limited	possible with other systems

What does this change in practice?

Wiring: IP installation uses the same type of cables as the rest of the company network, which means one standard in the building and the ability to use existing routes, but also a common infrastructure requiring joint planning of cameras and networks.

Power supply: The IP camera is typically powered over the same cable, which simplifies installation and eliminates power supplies at the devices, but shifts the responsibility to the switch, which must have a sufficient power budget. We describe the issue in more detail in the material about PoE in the corporate network.

Image analysis: IP camera can recognise the type of object in the frame and send an event instead of reacting to every movement, which actually reduces the number of false alarms, i.e. the service cost.

Scaling: an analog recorder has a finite number of inputs, so when they are exhausted, a second device must be added, while in an IP system, the limitation remains the recording capacity and bandwidth, which are more flexible, but require calculation.

Network Dependency: is the other side of the coin that is rarely talked about, because IP monitoring shares the fate of the corporate network, and a switch failure disables the cameras it supports. In the analog installation, these were independent tracks, which limited the scope of such a failure.

When the old system is enough

It is worth being candid here, because not every installation requires replacement:

• cameras cover what they are supposed to cover and the image is sufficient for the purpose,
• no need for remote access or integration,
• system works stably and parts are available,
• the company does not plan to expand,
• budget is needed elsewhere and monitoring is not critical.

If the list describes your situation, replacement will be an expense with no measurable return, but it is worth checking whether the record actually works and covers the assumed period and whether anyone has access to the recorder and knows the password.

It sounds trivial, although it is a common problem in older installations: the system is apparently recording, but no one has checked it for a long time, and as a result, only when the event occurs is it revealed that the disk has failed or the retention time is shorter than expected.

When replacing analog monitoring with IP is justified

• the image does not allow you to recognise what the camera was installed for. This is the actual criterion, not the number of megapixels,
• system does not cover areaswhich have been added: new hall, parking lot, ramp,
• no spare parts or no support for the recorder,
• remote access needed or event notifications,
• false alarms generate real costs handling,
• retention is insufficient in relation to the time it takes the company to detect events,
• renovation is planned, where the cabling is many times cheaper.

The last point marks the right moment for this decision, although it is often missed.

Modernisation in stages

Replacement does not have to be a one-off, and usually should not be, because staging reduces risk and allows you to verify assumptions.

Hybrid variant: some solutions allow you to connect analog cameras to the IP system through converters, so you can keep working devices and add new ones where they are needed. The trade-off is that the system inherits the limitations of old cameras and gains an extra element that can break.

Area Exchange: starting from places where the current image is unusable, you can later move to other zones, spreading the cost and verifying assumptions on a smaller scope.

Use of existing routes: if the old cabling runs in pipes that can be used to run new ones, the cost drops significantly, so it is worth checking this before pricing.

The practical order is as follows: first determine what monitoring is for and what retention is needed, then select cameras, and finally count the recording and network, because the opposite approach results in an installation that matches the disk capacity. We describe the method in the article about retention of surveillance recordings.

What replacement alone won't solve

• will not improve the frame. Camera looking at the wrong place in higher resolution looks at the wrong place more precisely,
• will not solve your nighttime problems. The image after dark is determined by lighting and mounting, not camera generation,
• will not replace retention. A better image takes up more space, so for the same capacity, retention decreases,
• will not release you from your obligations. The scope of observation, information and storage period is a technology-independent layer.

What's changing on the network side

This is the part that is most often omitted when modernising monitoring, although it ultimately determines the success of the entire project.

IP cameras enter the company's network infrastructure and require:

• own segment. Cameras should not be able to see accounting computers or vice versa. Basics: corporate network security,
• calculated power budget on the switch,
• bandwidth, especially between cameras and recorder,
• update. An IP camera is a network device with software that receives security patches and is no longer supported,
• access control. A camera with a default password that is accessible from the Internet is a problem regardless of what it shows.

The last point describes a real threat because monitoring devices exposed to the public network become the target of automated scanning.

How we do it

We start by asking what monitoring is for and what the current system does not do, and if the answer is "it works, only the image is poor", we first check the frame and lighting, because replacement may not be necessary.

When modernising, we design monitoring together with the network, not alongside it, taking into account the segment, power budget, bandwidth and recording. We also check whether existing routes can be used, as they usually constitute the largest item in the cost estimate.

We leave the legal layer to a lawyer or data protection officer, preparing the technical description that such a person needs and not declaring compliance with anything.

After implementation, monitoring can be monitored continuously, including checking actual retention, disk condition, recording efficiency, camera updates and access review. This is the element that fails most often in installations left to their own devices, and its failure is only revealed when an incident occurs.

Scope includes building and maintaining corporate networks, including IP monitoring installations designed together with the infrastructure.

Book a free IT review and let's talk about how to see if your current system actually records what it should.