This is a discussion item, not a technical question thread.
ReadyNAS has a Security Camera app. It is licensed on a per camera basis and looked like it was reasonable but fairly expensive when hundreds of cameras were being deployed. So we looked further.
This approach is an alternative to a dedicated app in the ReadyNAS that may be appropriate based on the target environment and objectives.
We have purchased a variety of IP cameras for deployment internally – near loading docks, shipping areas, assembly points, front desk areas, etc. At any one branch location there are typically twelve to 20 cameras deployed.
Our objective was capturing events that might be important…
Shrinkage
Inappropriate activity
Front desk image capture
Product assembly
etc.
These security cameras are fairly inexpensive and work in low light conditions as well. The image quality is top notch for high resolution cameras and most come with a built-in Lunix type app and network connection capability. Many IP type security cameras have motion sensors and are able to capture and upload information via FTP to a local FTP server without any problem. They can communicate either via Wi-Fi or on the local LAN. Configuring them to capture snapshots of activity triggered by motion eliminated over 80% of the video that had no interest, i.e. no motion.
The question was how to manage the information gathered and discard the unimportant information.
We decided that snapshots of the motion were adequate. In a typical week we gather about 25,000 to 35000 .jpg images per camera. If there is no issue that needs to be investigated then the data can be discarded.
We deployed Beoculus, a light-weight camera viewer that can interface many cameras at the same time. The images are on the desktop and can be viewed by any employee who has a computer. All employees are capable of passive security monitoring.
Employees who witness inappropriate activity (theft, sexual misconduct, etc.) can report anomalously to their management. In the case of shrinkage law enforcement personnel can be involved. In either case the images of the inappropriate activity can be segregated and saved.
We have a weekly PowerShell script that grooms the directories of each camera’s saved data and discards those data over three weeks old.
It took a bit to set it up but now the system has been working for 8+ months without any issues.
This is a good use for any ReadyNAS device and the cost is quite low when compared to typical CCTV installations.
This is a good use for any ReadyNAS device and the cost is quite low when compared to typical CCTV installations.
I agree, thx for sharing.
The decision to allow all employees to browse the cameras is interesting.
I see the potential benefits, but it does allow them to see exactly what the cameras cover and what they don't. Are the cameras mounted in a way that prevents the employees from moving them?
First we started with the premise that all employees want to do the right thing and will follow the rules and intentions of the organization. The cameras were initially deployed to catch the occasional bad guy but primarily outsiders. Later in the initial deployment it was decided to place some internally. At this point all employees know that they are potentially being observed by other employees.
The cameras are up high – eight to 11 feet off the ground and are fixed focal length devices. That means no zoom and in our case no pan or tilt operations. If the employee wants to reposition the camera they would need a ladder.
As a by-product of this deployment we have had several practical jokes caught and memorialized and one engagement.
