Video Surveillance Commissioning / Install Checklist

By Ethan Ace, Published Feb 08, 2016, 12:00am EST

This 60+ point checklist helps end users, integrators and consultants verify that video surveillance installation is complete.

It covers the following sections:

  • Camera Physical Setup
  • Camera View Setup
  • Camera Network / Security settings 
  • Camera Configuration Changes
  • VMS Hardware
  • VMS Security
  • VMS General Settings
  • Workstation Setup
  • Network Setup
  • Cable Verification

Download *** *** ***** ********

********:

*********: ** ********* **** person ***** **** ********* the **** *** ***** own ***** / **********. There ** ** '*** size **** ***' ********* but **** **** ** meant ** ***** ** a ******** ***** ** make ** ****** *** quicker ** ***** **** own.

******

**** ******* ****** ************* of ******* (** *** otherwise), ********* ******** *** physical **************, ***/***** ******* concerns, *** *******/******** *****.

********

  • ******* ******* *** ***** fasteners *** ******
  • ************ ******* ****** (*** our ************* ************ ******)
  • ***** ****, ****, ***/** housing ***** ********
  • ***** ******* (** ********)

****** **** *****

  • *** *** ***** ****** (using **** ***/** ****** fine *****; *** *** ******** ******** ** **** ** ******* ********* ********)
  • **** ***/**** ***** ******** (all ****** **, ** full ***, ***.)
  • ****** ******** ******** ** daytime ***** ** ****
  • **** ***** ******** (***** worst **** ********, *.*., all ****** *** ********, if ******** ****** ***** ********)
  • ****** ******** ********* *********** meets ******** **************/************; *** our ******* *** ***** ** Image ******* ****** *** *** ****** / ******* Illumination *****
  • **** ***** ***** ******** if ******* (**** ** sunrise/sunset ** ****/**** ****** cameras, ******** *** ******* when *** ** **** direct, ***.); *** *** *** ********
  • ****** ******** ***/***** ***** performance ***** ******** **************/************

*******/******** ********

************* *******

**** **** **** ** these ********, **** ** resolution, *********, ***********, ****** detection, ***., *** ** configured ** *** ***, though **** ****** ********* on *** ******/*** *********** used. ******** ******** **** as ***, ***** **, analytics, *** ***** ****** are ****** ******** *** the *** *** **** be ********** ******* *** camera *** *********.

***/*********

**** ******* ****** ************* of *** ******* *** NVRs/DVRs, ********* **** ********/******* setup ** **** ** OS *** ********. **** of ***** ***** *** not ** **** ********* on ** *** *** platform. *** *******, ******** recorders ********* ** *** require ** *******.

********/********

******* ********

  • ****** ********/********* ** ****** version
  • ****** ***** ******** **** default
  • ****** ********/**** ******
  • *** *** ****** *** verify **** *** ****
  • ********* ******* ******* (******** drives, ***, ***)
  • ********* ******* ****** (******* recording ******)
  • ********* ********* ******** (*.*., 24/7, ***-***, ***-*****, ********, etc.)

************

**** **** ******** ****** workstations, ********* ********, **, and *** ****** ***** and *************. **** ** these ***** *** ** omitted ** ***** ******* on ******** ********* ** used.

  • ******** *** *******(**) ** each ***********
  • ****** *** ******** ** address(es)
  • ***** ****** ** ******* (unless *** *********** ** manufacturer)
  • ****** ****** ***** ********
  • ****** ********** ***** ** specified
  • ******* *** ****** *** update ** ****** *******
  • ********* ****** ***** ** required; *** *** *** **** ***** ********
  • ********* **** *****/********* ** required
  • ********* *** ***** ** *********; see *** *** ******* ********
  • ********* *****/***** ***** ** required
  • **** *** ********* *** runtime (** ********)

*******

**** ******* ******** ************* of ******* ********, ********* switches, *******, *********, ***. Some ** ***** ******* may *** ** **** in *** *******, ** managed ** *** ********** integrator.

*******

**** ******* ****** ************* of *** ************ ******* system, ********* ********, ********, aesthetic ********, *** *******. See *** ******* ******* *** ***** Surveillance ***** *** ******* ** ***** topics *** ****.

  • ***** *** ******, ***** panels, **** *******, ***., as ********* (*** *** ***** ********* **** *********)
  • ****** ****** *** ******* to ******** (*-*****, ******* truss, ***.)
  • ******* ****** ***** ********/********
  • ***** ******** ****** *** dressed ******* ***** ** camera ******** *** **** end ** ********; 
  • **** *** ************ *** document ******* ** ********* (*** our ******* ***** ******* *****)
  • ******** ***** **** ******* as ********* (** ************* is ********)

Comments (23)

Carla Calk

02/08/16 02:49pm

This is a great document, thanks

Avatar

Chris Daniels

IPVMU Certified | 02/08/16 03:39pm

Very helpful starting/ reference, must have info for every VMS specification set.

Thank you IPVM!

Chris Daniels, HAWA Incorporated

Avatar

Armando Perez

IPVMU Certified | 02/08/16 05:19pm

In the past we had line items for techs to write down ip and credential info for each camera. since moving to in-house instead of on-site programming that all happens on the build bench, but simply having that info months after the install is a boon to serviceability. The next step for us is saving a copy of the VMS config file and storing it for future service restore, etc and even remote service on the fly. The checklist is a critical first step though. nice job!

Tom Sorrell

02/08/16 08:19pm
Nice points list. Thanks
Avatar

Jason Neubauer

IPVMU Certified | 02/08/16 08:49pm

Great reference. This is why i don't mind paying dues!!!

Undisclosed Manufacturer #1

02/08/16 09:27pm

When you assign the network address, it would be good to gather all serial numbers from the products. It makes returns and repairs easier AND it can handle a dispute where the customer purchased materials and added to the system from another source which involves warranty support.

As a comment, I had a dealer who arrived at a site and several of his cameras went missing. He replaced them and when someone returned, there were additional cameras of the same type added by the customer. Now, who wants to call a customer a thief....but a little proof would have gone a long way.

Avatar

Ethan Ace

IPVM | In reply to Undisclosed Manufacturer #1 | 02/08/16 09:31pm

Excellent point and I can't believe I left that out.

Thanks for the suggestions, we'll update this this week.

Undisclosed Integrator #2

In reply to Ethan Ace | 02/09/16 07:10pm
I thank you for building this list, I'm going to make an Excel sheet out of it!

Undisclosed Integrator #2

02/09/16 03:26pm

You missed one of the most imporant thing: backup configuration of VMS/NVR/DVR which contains not only camera configurtion but user permissions, priviliges, schedules, etc.

Avatar

Ethan Ace

IPVM | In reply to Undisclosed Integrator #2 | 02/09/16 05:35pm

Thanks for pointing that out! It was actually in there but things got moved around and it got lost in the shuffle. I'll get it back in.

Andrew Thomas

02/09/16 05:39pm

This reads as if this is an "AS-BUILT" document as opposed to an installation plan.

Tariq Saleh

02/10/16 10:50am

I believe you have forgot the following

1) make and model of the cameras, NVR's, and servers

2) VMS software version

3) License information

Thanks

Jason Welin

02/19/16 04:54pm

Any idea of when the document might be ready??

johan Schorreel

03/03/16 02:51pm

this is nice but I wonder if there already is a Excel document available ?

Jason Welin

03/06/16 08:42pm

Still eagerly anticipating the word/excel documents!!

John Honovich

IPVM | 03/07/16 09:08pm

Sorry about the delay on the excel document, I dropped the ball on this. I just queued this up with our graphics person. I am not exactly sure the best way to lay this out but we will do a version and then share with you all for feedback.

John Honovich

IPVM | 03/11/16 02:48pm

Added:

Download:

Let us know what you think of them.

johan Schorreel

03/11/16 03:39pm

thanks !

Undisclosed Integrator #3

05/09/17 02:06am

May I ask what is the purpose of document the MAC address?

David Shepherd

In reply to Undisclosed Integrator #3 | 05/09/17 02:22am

In my experience it depends on the customer, sometimes the IT staff will require it, for example if they are running port security. Regardless its still a good idea to make a note of it.

Undisclosed Manufacturer #1

In reply to Undisclosed Integrator #3 | 05/09/17 02:50am

It's like documenting a hidden junction box in a remodel, you only know you need it when you really need it.  If you document anything, document everything.

Undisclosed Integrator #2

In reply to Undisclosed Integrator #3 | 05/09/17 11:41am

It can help IT department to locate network issues. Better to have on-hand than going out to the site, climb to the ladder to read it or check it on a workstation (if available). 

Mendy lewis

05/09/17 03:11am

What about DDNS, static ip ,port that opened 

also, if it's a take over job, or upgrading very important to document and photograph , existing condition  of systems before any new work starting, soon as you touch the system the costumer can blame you for pre-existing issues that you didn't plann to repair

 

 

Read this IPVM report for free.

This article is part of IPVM's 6,665 reports, 897 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now
Loading Related Reports