Educause Security Discussion mailing list archives

Re: IP Camera Replacement Budget


From: Barron Hulver <Barron.Hulver () OBERLIN EDU>
Date: Tue, 7 Dec 2010 22:00:44 -0500

We have been using Panasonic cameras and recorders and have found them to be very reliable. (My group handles some of the cameras on campus.) We do not have a formal replacement cycle for our security cameras, but based on our experience I think the replacement time frame will be based on technology rather than warranty expiration or break/fix issues. That is, the quality and features of camera systems will continue to get better and that is what will make your existing equipment obsolete. We started with analog cameras in the mid '90s and started migrating to IP-based cameras in 2006. It is 2010 and we are seeing a huge leap in quality and features in the marketplace as we look to purchase new equipment.


Barron

Barron Hulver
Director of Networking, Operations, and Systems
Center for Information Technology
Oberlin College
148 West College Street
Oberlin, OH  44074
http://www2.oberlin.edu/staff/bhulver/



Chip Greene wrote:
We are in the process of growing our physical security posture and adding more IP cameras across the campus. In trying to plan for future budget requirements a couple of questions have come to the forefront regarding the replacements of cameras and their systems. Currently we have a 5 year replacement plan for servers and the associated hardware, so that budget plan is fairly straight forward and painless. The questions we have are:

1. Is there a standard life cycle for ip cameras (we currently use all Axis)?
2.       What would be a good timeframe to budget for replacements?
3.        Does it make sense to plan for:
a.       replacements every 7 (random number) years for each camera
b.      replacement at the end of the warranty period
c.       plan for individual break-fix?


Thanks for any recommendations that would benefit our budget planning.


Chip Greene
Senior Network Specialist
University of Richmond


Current thread: