Rules For Use
Security cameras are governed by i3Detroit's Security Camera policy.
Use of security cameras was approved originally in 2012. The policy was updated in 2015 to be included in the standing rules. The discussion of the 2015 proposal happened largely in Slack, in the archived channel #camera-policy. The standing rules section was modified in early 2016 to replace the 4-person viewing team with the Board of Directors. It was again modified in early 2017 to expand the viewing team to consist of at least one director and either one other director, officer, or zone coordinator.
List of Current Cameras
|Location||View (not live)|
|Commons Area & Snack Zone|
|Front & Garage Doors|
|Front Door Exterior|
|Machine Shop 1|
|Machine Shop 2|
|Suite B Rear Doors|
|Suite B Rear Doors|
|Suite B Shop Doors|
|West Shop (Bike, Vinyl, & Jewelry zones|
|Wood Shop North|
|Wood Shop South & Tool Crib benches|
History of Camera Location Approval
- Original list from Board_Meeting_Minutes_20121113
- Slightly modified list voted on via email vote: Membership Proposal 20121115 Allow Placement of Cameras
- List updated in early 2016
- List updated again: Meeting Minutes 20160517#Request for additional security camera
- Another update: Meeting Minutes 20170307#Camera Placements
- Note: The outside camera was in the original list, but not in the actual voted-on list. However, at the time of the 2016 update, the outside camera was presumed to be approved. It's not super relevant since we don't have an outdoor camera set up (as of 2-17-16), but it should probably be officially re-approved.
- Approved Media Lab camera at Minutes:Meeting Minutes 20180605
- Approved three cameras in Suite B at []
Status Report from Project Lead
- 18 of 18 approved planned cameras have been installed. See below for technical details.
- (10/19/17) System is in working order and has been for several months now.
- (6/9/2018) System still working well, no major issues. 15/18 cameras have 240+ days continuous uptime.
|Reconfigure Network for camera VLAN||Move all the cameras over to their own VLAN separate from the main public network.||3|
|Install GPU in VMServer||Install an Nvidia 6xx or newer GPU to enable GPU accelerated h.264 encoding for archived video.||5|
Technical Details of Zoneminder & IP Camera System
- Zoneminder v1.32.1 running on VMServer
- 1x 4TB Western Digital Purple Surveilance, 1x 4TB Western Digital Red hard disks installed in the VMServer
- 18 wired PoE IP cameras
- 13xHikvision 4.1MP DS-2CD2042WD-I 4mm IP Camera
- 5xHikvision DS-2CD2432F-IW 3MP Indoor 2.8mm IP Camera
Sometimes the build of ZoneMinder that we're using (1.34.1--old, but historically upgrading has had mixed results, and nothing's currently broken...) has a bug where the process that writes the diskspace used per event to the database breaks, leaving NULL in place of the real value. This is problematic as summing the diskspace used by all events then returns the wrong total, which breaks some things. It's normal to have some events showing NULL diskspace since the process doesn't run constantly, so this script runs as a cron job once an hour which is often enough to fix things before there are any problems. It seems to be triggered on average once a day.