How To Specify a Quality Integrator

Designing of a specification for a 100 camera project that will be expanded in future phases (well over 1000 cameras and doors). In my Division 28 section, I am specifying the minimum qualifications necessary to obtain a quality integrator (It's a high risk client). This is a specification and not an RFP. So statements like: “Integrator shall be skilled in all aspects of systems integration and shall provide resume’s of technical personnel assigned to this project” are fine for an RFP (where there is a comparative point value assigned); but not correct for a specification, such as this revised version of the above: “Submit documentation that at least two technical staff assigned to this project have achieved certification for one or more of the following: aaa, bbb, ccc.

In other words, in a spec, there should be no ambiguity (although admittedly there often is). So, in this case therefore there are two essential criteria I need to abide by: 1)A clear statement as to what is expected of the integrator; and 2) a way to prove what the integrator claims. Tell me what YOU think is enough experience. Is it enough to have one tec available that is certified? Or must we have two? Or must he be on site? Etc. etc. What about the company? How long should they be in business? Doing what? What are other quals you think relevant to the matter?

From IPVM there are a number of certifications cited but I would greatly appreciate anything additional you could add from your own experiance. I believe it IS ok to limit competition; you just cannot do it unfairly.

Appologies for the length...

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.
**** **** *** **** ******, *** *** ******** ****** *** future ******* ** *** **** *****. **** ********** ** ********** capability. ** *** ******** *** ******* ** ****** ** ******** integrators (******* / ***** / *-****), **** **** **** **** more **** *** **** ********* **** **** **** * **** of ************* *** **** ****** **** * *****. *'* **** the ********** **** **** *** ** ****.

* *****. ** *** * **** ******* ************* (***** ** fine ** **) ***** ** ******** ** **********?

**** ***** *** ***** ******* ***** * ***** ******* **** acquire *** ************* ***** *** ***** ** ***** **** **** lack *** **********. ** *** ***** **** **** **** **** had *** ************* *** ** **** ** * **** *** version ** *** *******, ******* *** ******** ******. ******* **** 1 ** * ***** ****** **** ******** ****** * *** projects *** ***** ********** *******.