KENYA STANDARD                                                          KS 2110-2:2009 
© KEBS 2009 — All rights reserved     First Edition 2009                         
   
  
  
 
 
  
 
 
 
 
 
 
 
 
 
 
 
 
    CCTV surveillance systems for use in security a pplications — 
 
    Part 2: Operational requirements 
 
 
 
 
 
 
 
 
 
 
                       PUBLIC REVIEW DRAFT,MARCH 20 09 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
       KENYA STANDARD                                                          KS 2110-2:2009 
© KEBS 2009 — All rights reserved     First Edition 2009                         
   
  
TECHNICAL COMMITTEE REPRESENTATION 
 
The following organizations were represented on the  Technical Committee:  
 
Eveready Batteries Kenya Ltd. 
Associated Battery Manufacturers 
Kenya Railways Corporation 
Securicor Alarms (K) Ltd. 
Department of Defence 
Ministry of Roads and Public Works  
Kenya Power & Lighting Company Ltd.  
Automotive Industrial Battery Manufacturers (A.I.B. M) (K) Ltd . 
Ministry of Energy 
Jomo Kenyatta University of Agriculture and Technol ogy — Electrical Engineering Department. 
Kenya Bureau of Standards — Secretariat 
 
 
 
 
 
REVISION OF KENYA STANDARDS 
 
In order to keep abreast of progress in industry, K enya Standards shall be regularly reviewed. Suggest ions for 
improvements to published standards, addressed to t he Managing Director, Kenya Bureau of Standards, ar e 
welcome. 
 
 
 
 
 
© Kenya Bureau of Standards, 2009 
 
Copyright:  Users are reminded that by virtue of se ction 6 of the Copyright Act, Cap. 130 of the Laws of Kenya, copyright subsists in all 
Kenya Standards and except as provided under sectio n 7 of this Act, no Kenya Standard produced by Keny a Bureau of Standards may 
be reproduced, stored in a retrieval system in any form or transmitted by any means without prior perm ission in writing from the Managing 
Director. 
 
 
 
 
 
 
 
 
 
ISBN 
 
KENYA BUREAU OF STANDARDS (KEBS) 
 
Head  Office: P.O. Box 54974 Nairobi,Tel.: (+ 254  0 20) 605490, 603433, 602350/1, 603352 ,Fax: (+ 254 020)  604031 
E-Mail: info@kebs.org, Web:http ://www.kebs.org   
Coast Regional Office Western Kenya Regional Office  Rift Valley Regional Office  
P.O. Box 99376, Mombasa P.O. Box 2949, Kisumu P.O. Box 811 1, Eldoret 
Tel.: (+254  041) 229563, 230939/40 Tel.: (+254 057 ) 23549, 22396 Tel.: (+254 053) 33151, 63377 
Fax: (+254  041) 229448 Fax: (+254 057) 21814 Fax: (+254 053) 33150  
       KENYA STANDARD                                                          KS 2110-2:2009 
© KEBS 2009 — All rights reserved     First Edition 2009                         
   
  
Foreword 
 
This Kenya Standard was developed by the Technical Committee on Extra-low Voltage Equipment and is in 
accordance with the procedures of the Bureau. 
 
In the preparation of this Kenya Standard, referenc e was made to SANS 10222-5-1-1:2007, Electrical sec urity 
installations Part 5-1-1: CCTV installations - CCTV  surveillance systems for use in security applicati ons - 
Operational requirements. 
 
Acknowledgement is hereby made for assistance deriv ed from this source. 
 
The purpose of this part of Kenya Standard is to pr ovide guidance to those responsible for establishin g 
operational requirements that can be used in the pr eparation of specifications for, and the selecting,  installing, 
commissioning, operating, evaluating and maintainin g of CCTV surveillance systems. 
 
The operational requirement development process enc ourages clear thinking about the what , where , when, 
why  and by whom  with relation to a CCTV surveillance system. The f inal design specification should clearly 
state what the end user expects from the system. Wi thout an operational requirements document and 
associated test procedures there will be no guarant ee that the system will fulfill its intended purpos e. 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 KENYA STANDARD  KS 2110-2:2007  
© KEBS 2009 FIRST EDITION, 200 9            
 
 
CCTV surveillance systems for use in security appli cations —  
         Part 2: Operational requirements 
         1 Scope 
 
This Kenya Standard provides a method for analysing  and documenting the needs of the end users 
of CCTV surveillance systems. 
 
The objectives of this part of Kenya Standard are: 
a) To provide a statement of needs based on a thoro ugh and systematic assessment of the 
problems to be solved and the resultant desired sol utions; 
b) To provide guidance on writing information check lists 
c) To illustrate how these checklists can be applie d to the acquisition, installation and management 
of a CCTV surveillance system. 
           2 Definitions and abbreviations  
For the purpose of this part of Kenya Standard, the  following definitions and abbreviations apply  
2.1 Definitions  
 2.1.1  
CCTV camera  
A unit that contains an imaging device that produce s a video signal from an optical image 
 
2.1.2  
CCTV surveillance system  
A system that consists of one or more CCTV cameras,  monitoring and associated equipment for 
transmission and controlling purposes, which might be necessary for the surveillance of a defined 
security zone 
 
2.1.3  
Operational requirements document  
A statement of needs based on a thorough and system atic assessment of the problems to be solved 
and the required solution  
 
2.2 Abbreviations  
2.2.1 CCTV:  Closed-circuit television 
 
3 Attributes of the operational requirements docume nt  
 
The operational requirements document should have a ttributes which enable it to: 
 
a) Be applicable to any size or type of system at a ny time of its life, from initial concept to review , 
b) Provide a framework for discussion and collation  of the views of all the stakeholders, 
c) Identify the role that CCTV will play in the ove rall security strategy, 
d) Identify relevant and realistic performance goal s, KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved  e) Define key factors to be included in a test spec ification and act as a reference point for the 
analysis of test results, 
f) Expose conflicts of opinion, especially in multi -agency schemes, 
g) Allow priorities to be set for the acquisition, implementation and operation of the CCTV 
surveillance system, 
h) Identify future needs for system expansion at th e outset, 
i) Provide a basis for planning, phased implementat ion and investment appraisal, 
j) Separate operational decision-making from techni cal decision-making, 
k) Reassure, through commissioning tests and routin e audits, that performance is linked to current 
or anticipated needs, and 
l) Provide an audit trail for decision-making. 
4 Producing the operational requirements document  
 
4.1  The first step in the development of the operationa l requirements is documenting 
 
a) The problems being faced, 
b) The areas in which activities that cause problem s can occur, and 
c) The desired, ideal and likely responses to these  activities. 
 
The analysis involves each of the role players work ing with checklists and site plans. The 
checklists provide a framework for assembling in co mmon format information as set out in 4.1.1 to 
4.1.5. 
4.1.1 Area to be observed  
This includes information on the area to be covered  and the purpose of the coverage. 
4.1.2 Response to the activity  
 
This includes the desired response to an activity a nd the conditions under which the CCTV 
surveillance system is expected to operate. 
 
4.1.3 Observer interface  
 
This includes information on where the observation is to take place and who will make it, what 
quality of picture and magnification is needed for success, and how the observer is expected to 
perform in response to the activity. 
 
4.1.4 Risk analysis  
 
This includes a list of the risks, benefits and pri orities and the requirements for success. 
 
4.1.5 Collation of evidence  
 
This covers all aspects of the recording of evidenc e that need to be addressed, such as equipment 
performance, multiplexing, alarm activation, review ing and the handling thereof after an activity has 
occurred. 
  
 4.2  Information on an operational requirement will need  to be drawn from several sources. The  
completion of checklists enables each stakeholder t o analyse and document his own needs in a  
uniform way and is especially valuable where severa l different groups are entering into a partnership  
to address the particular problem for the first tim e.  
  
 4.3  Where a partnership is to be part of the process of  addressing the problem, it is important to 
establish a common vocabulary at the outset. A comm on vocabulary contributes to an early 
understanding of the views of others and strengthen s the sense of ownership and partnership. 
  
 4.4  The accuracy of the analysis of the operational req uirements depends on asking the right KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved  questions to the right people. Therefore, depending  on the application, typical stakeholders in a 
system will include the following interest groups o r persons: 
 
a) Managers (project and any others who are interes ted); 
b) Financial controllers; 
c) Security advisors; 
d) Police and other security services (to advise on  the criminal viewpoint and the appropriate 
response to an activity); 
e) Employees; 
f) General public; 
g) Neighbours (residential or business); 
h) Operators;  
i) Technical advisors on procurement, installation and maintenance. 
 
Having established the initial need and identified persons who should be involved, the next step 
will be to complete an operational requirements doc ument. 
 
5 Methodology for completing the operational requir ements document  
   
5.1  It is recommended that the methodology given in 5.2  to 5.10 be used in conjunction with the 
information checklist given in annex A to assist in  the preparation of an operational requirements 
document. 
 
The checklist is developed specifically with a view  to designing public domain CCTV surveillance 
systems. However, the majority of the questions and  responses are applicable to most other 
situations and the remaining ones can be adapted to  meet specific applications. The checklist 
contains twenty defined questions in tabulated form at to ensure that all pertinent information is 
obtained in respect of a specific area. This type o f information is essential to an effective operatio nal 
requirements document. 
            5.2  Obtain a site plan and a supply of blank informatio n checklists. 
 
5.3  On a separate sheet, list the issues of concern in the identified area and give each issue an 
initial priority ranking of "essential" or "desirab le". 
  
 5.4 Clearly define, on the site plan, each area where t he activities that cause problems can occur. 
Note any important dimensions that define the area to be covered. 
 
5.5  For complex systems the first pass may be at a high  level, stating only the broad outlines of the 
problem. A more detailed analysis is produced by su bsequent subdivision. This detailed analysis 
might include identifying known problem areas, zone s related to areas that have alarms, high-risk 
areas, likely points of entry and potential weak sp ots. 
  
5.6  Use a separate information checklist for each defin ed area. Information can be entered in any 
order. Boxes left blank owing to insufficient infor mation will identify areas that require further 
investigation. 
  
5.7  Give the purpose of observation of each area (box 3  of the checklist; see annex A) as one or 
more of the purposes shown in figure 1. A more deta iled image is obtained by having each CCTV 
camera cover a smaller area. Since higher performan ce is thus more expensive and difficult to 
achieve, it should be specified only when necessary . 
 
 
 
 
 
 
 KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved  
 
 
 
 
 
 
 
 
Figure 1 — Examples of image size relevant to image  detail 
 
5.8  If any area is to be observed for more than one pur pose, a separate checklist should be 
completed for each purpose. 
 
5.9  Each stakeholder should initially compile their own  set of checklists. When these are 
combined they provide a comprehensive view, which e nables potential conflicts to be resolved and 
priorities to be agreed on, based on factors such a s threat and risk assessments. Special needs 
can be kept confidential, if necessary. 
 
 
5.10  After prioritization, rationalization, feasibility studies and budgetary studies, a structured 
analysis of the problems and anticipated solutions can be produced. 
 
6 Guidelines to completing the information checklis t  
 
6.1 General  
This section provides guidance on completing the ch ecklist with a view to providing pertinent 
information when compiling the operational requirem ents document. The heading for each box and 
examples of typical information responses are given . 
 
6.2 Area reference and type  
Shade in, on the site plan, each area where a targe t will need to be observed and draw up a 
checklist that has a unique area reference code tha t corresponds to and identifies each area. Give 
the type of area at the top of the checklist (see a nnex A). 
 
6.3 Boxes 1 to 5 — Problem definition  
 
6.3.1 Box 1 — Target to be observed  
a) Persons. 
b) Groups of individuals. 
c) Objects (items of equipment, etc.) 
d) Individual vehicles. 
e) Traffic. 
f) Police or emergency services. 
g) Other, not specified above. 
 
If appropriate, define the target as stationary or moving. (Note the speed, in kilometers per hour, if  
applicable.) 
 
6.3.2 Box 2 — what activity of the target is of con cern?  
 
a) Damage to property, litter or graffiti. 
b) Robbery, burglary. 
c) Changing hands of drugs, money or weapons. 
d) Drug abuse. 
e) Fighting, assault. KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved  f) Handling stolen property. 
g) Loitering or pick-pocketing. 
  h) Bogus collectors, bogus officials. 
  i) Traffic offences, accidents. 
  j) Car crime (theft or damage). 
  k) Suspicious actions (define). 
  l) Anti-social behaviour (drinking, vandalism). 
  m) Other (specify). 
 
             6.3.3 Box 3 — Purpose of the observati on  
 
   a) Monitor 
b) Detect 
   c) Recognize 
   d) Identify 
 
The targets and activities are identified in boxes 1 and 2 above. 
 
 This box suggests four purposes of observation (ca tegories of observer tasks). The   following   
definitions and minimum performance guidelines are applicable (see figure 1): 
 
a)  Monitor:  The observer can determine the number, direction a nd speed of movement of people 
whose presence is known to him. In other words, it is not necessary to search for them. 
b)  Detect: Following the alert, the observer can, after a sea rch, ascertain with a high degree of 
certainty whether or not a person is visible in the  pictures displayed to him. 
c)  Recognize:  The observer can say with a high degree of certain ty whether or not the individual 
shown is the same person as someone he has seen bef ore. 
d) Identify:  The picture quality and detail should be sufficien t to enable the identity of a subject to be 
established beyond reasonable doubt. 
 
             6.3.4 Box 4 — Picture quality and cont ent factors needed to achieve success  
 
                a) Clear view of suspect's body lan guage to identify potential problems. 
   b) Ability to follow the progress of a target. 
                c) True colour. 
                d) Real time. 
   e) Clarification of actions (for example, is the  suspect using a key or an implement?) 
   f) Automatic display of the area covered by the alarm. 
   g) Overall view of the scene. 
 
6.3.5 Box 5 — Spare  
 
This box can be used according to specific needs, f or example: 
a) Threat assessment. 
b) Rating by assessment panel. 
   c) Ability of the supplier to comply with the re quirements, given as a percentage. 
 
           6.4 Boxes 6 to 10 — Operational response  
 
6.4.1 Box 6 — Required result of a successful respo nse to the activity  
 
a) Calmness restored. 
b) Dispersal or control of the situation. 
c) Prevent or minimize injury and damage. 
d) Reduce crime or disorder (or both). 
e) Improve safety and reassure the public. 
f) Identify suspects and exclude innocent parties. 
g) Gather intelligence to assist in the subsequent apprehension of offenders. 
h) Apprehend suspect with evidence. KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved  i) Response has been of an appropriate level. 
j) Public safety through effective evacuation. 
k) Restore traffic flow. 
l) Secure the area. 
 
6.4.2 Box 7 — who makes the response?  
 
a) Uniformed police patrol. 
b) Traffic police. 
c) Armed or specialist response team. 
d) Plain-clothes personnel. 
e) Traffic officer. 
f) Observer. 
g) Private security staff employed by the owner. 
   h) Store detectives. 
 i) Key holder (owner of the premises or the vehicl e). 
 
6.4.3 Box 8 — Time scale of the response for it to be successful  
 
a) As soon as possible. 
b) Within minutes. 
c) Within hours. 
d) Within days. 
e) Once a video result has been obtained. 
f) In accordance with graded response. 
 
6.4.4 Box 9 — When is observation needed?  
 
a) Until arrest or curtailment. 
b) During the activity, as initiated by the soundin g of the alarm. 
c) 24 hour, continuous basis. 
d) Between particular times (for example, rush hour , licensing hours). 
e) Specific days or periods (for example, on Monday s, Wednesdays, Saturdays; during school 
holidays). 
f) During or outside trading hours. 
g) During pre-organized events based on advance inf ormation or special intelligence. 
h) When a few or when many people are about. 
i) When requested by the police controller. 
j) When police are responding to incidents. 
k) During the day or at night. 
 
6.4.5 Box 10 — Conditions under which the system ne eds to be effective  
 
a) State normal or special weather conditions (for example, rain or fog). 
b) All likely conditions during the applicable time s. 
c) Fire or flood. 
d) With up to 1, 2, 3, etc. simultaneous activities  of the same priority. 
e) Changing light levels (for example, nightclub do ors opening and closing). 
f) Using existing lighting only. 
g) Lighting may be enhanced (designer to specify). 
 
6.5 Boxes 11 to 15 — Observer role  
 
6.5.1 Box 11 — what will the observer do when the a ctivity occurs?  
 
a) Switch on a video recorder. 
b) Follow the action (obtain close-ups). 
c) Identify the location of the object or activity.  
d) Notify the response team by radio or telephone. KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved  e) Investigate personally. 
f) Give instructions to resources. 
g) Describe the incident to the controller. 
h) Alert the police and direct pictures to police m onitors. 
i) Search for the target. 
j) Follow set operational procedures. 
 
6.5.2 Box 12 — How will the observer know when and where to look  
(be cued or prompted)?  
 
a) Direct request by the police controller. 
b) Telephone or alarm system. 
 
6.5.2.1 By strategy  
 
a) Rely on past experience, training, culture. 
b) Briefing of specific or daily events. 
c) Monitoring, for example, a radio channel or tele phone calls. 
d) Analysing local crime figures. 
 
6.5.2.2 By chance  
 
a) Constant monitoring. 
b) Automatic sequencing of pictures. 
c) Random picture monitoring. 
 
6.5.3 Box 13 — How quickly does the observer need t o act, search for and detect the  target?  
 
a) Immediately. 
b) Within minutes. 
c) Within hours. 
d) Within days. 
e) Depends on each individual case or in accordance  with action plan already drafted. 
 
6.5.4 Box 14 — who makes the observation on which t he response is based?  
 
a) Police controller. 
b) Car park attendant. 
c) Traffic officer. 
d) Private security company 
e) Store detective. 
f) Civilian (for example, employee). 
g) Investigator. 
h) Casual staff. 
 
6.5.5 Box 15 — where will the observations take pla ce?  
 
a) Police control room. 
b) Control room. 
c) Private security premises. 
d) Police video facility. 
e) Police incident control. 
f) From a mobile or remote location. 
g) Replay or review facility separate from control room. 
 
NOTE: Use a "P" to indicate a primary observation p oint and an "S" to indicate a secondary 
observation point. 
 
 KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved   
 
6.6 Boxes 16 to 20 — Miscellaneous  
 
6.6.1 Box 16 — Stakeholders  
These are the views of ... (enter names or organizat ion).  
 
Additional opinions might also be sought from ... ( enter names or organization). 
a) Local authority. 
b) Community groups, the public. 
c) Police. 
d) Owners of the property. 
e) Other emergency services. 
f) Occupants. 
g) Insurers. 
h) Retailers. 
i) Car park owners and users. 
j) Tourism Board. 
 
6.6.2 Box 17 — what priority is assigned to this ta sk?  
 
a) Essential: Use sub classification high, medium o r low, or rate on a scale of 1 to 5, for example E3 . 
b) Desirable:Use sub classification high, medium or  low, or rate on a scale of 1 to 5, for example D2.  
c) Threat-dependent. 
 
6.6.3 Box 18 — Likelihood of an activity occurring and how often  
 
 Likelihood                  Frequency  
 Very                                                         High Continuous 
 High                                                         Hourly 
 Medium                                                    Daily 
 Low                                                          Monthly 
 Monthly 
 
 
6.6.4 Box 19 — how effectively does the task have t o be done?  
 
a) Right first time, every time. 
b) Initially effectively but less effectively as ti me passes. 
c) Standard high enough to meet the needs of the in vestigation. 
d) Effectively, once or twice, is sufficient. 
e) Detect ... % of incidents. 
 
6.6.5 Box 20 — Benefits of doing the action versus not doing it at all  
 
a) Safer prosecutions (less written evidence and be tter documentary evidence). 
b) Enhanced police credibility. 
c) Reduced crime. 
d) Enhanced public safety. 
e) Reduced investigation time. 
f) Increased public confidence, higher trade level and reduced fear of crime. 
g) Improved policing. 
h) Reduced insurance premiums. 
i) Complaints dealt with effectively. 
 
  6.7 Performance guidelines  
 
6.7.1 General  KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved   
Performance guidelines are related to the image hei ght of a standing man (defined as 1.6 m). 
When the image of the man fills the screen vertical ly the image height is said to be 100 %. The 
figures are based on a 625 line CCIR standard syste m and assume that all equipment is correctly 
adjusted and operated within the design range (see figure 1). 
 
6.7.2 Monitor  
The image occupies at least 5 % but less than 10 % of the monitor screen height. 
 
6.7.3 Detect  
  The image occupies at least 10 % but less than 50  % of the monitor screen height. 
NOTE:  In respect of 6.7.2 and 6.7.3 it is assumed that the image contrast of the target is 
sufficiently above the threshold of human sensitivi ty and that the picture is not unduly cluttered wit h 
non-targets. 
 
6.7.4 Recognize  
The image occupies at least 50 % but less than 120 % of the monitor screen height. 
 
6.7.5 Identity  
The image would occupy at least 120 % of the monito r screen height. 
 
6.7.6 Reading a car license plate  
 
A saloon car image should not occupy less than 50 %  of the monitor screen height if the license 
plate is to be read. 
NOTE:  In respect of 6.7.4, 6.7.5 and 6.7.6 it is a ssumed that the angles of view and lighting are 
suitable and that no significant degrading effects,  such as image blur owing to motion or poor 
focus, is evident. 
 
6.8 Completed checklist  
 
When completed accurately by each stakeholder, the information checklist will 
a) Help to ensure that the extent of the problem, p erceived or otherwise, is really understood, 
b) Allow technically skilled persons to determine w hether or not the system can be built and 
operated effectively and economically, 
c) Provide a basis for dialogue and partnership bet ween the many, often disparate, parties involved 
in security, 
d) Act as a planning document (help prioritize need s and establish performance criteria), 
e) Help determine the needs of those who will use t he pictures to fulfil their role as the interface 
between the activities that cause problems and the response teams or investigators, 
f) Make it easier to assess and compare the various  views expressed, and 
g) Give a complete view that allows the full costs of ownership to be established and the expected 
benefits to be defined. 
A design specification can be formulated by making use of the data from all the completed 
information checklists. 
 
7 Design review  
 
7.1 General  
While many of the technical issues are capable of d efinition, providing high quality pictures will be 
of no value if they are of the wrong scene or if th ey are not seen by the observer. Many people who 
purchase CCTV surveillance systems fall into the tr ap of believing they are buying a simple alarm 
system when they are actually buying a sophisticate d command-and-control system. Whatever the 
original perception, careful analysis will reveal a  mixture of security, safety and management 
needs. 
When designing the system it is important to recogn ize all the relevant issues. 
 
 KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved  7.2 Illumination  
 
Adequate lighting has to exist in the area to be ob served otherwise pictures will be of a poor 
quality. If the identification of persons is a requ irement, the provision of adequate lighting might n ot 
be achieved cost-effectively. Testing is done by me asuring the available light using a lux meter 
during the period when observation is required. If the lighting is inadequate for the purpose of 
observation, appropriate stakeholders need to be in cluded and additional finances set aside for 
upgrading the lighting. 
 
   7.3 Areas or targets or activities to be observe d  
 
This information is obtained from the information s heets submitted by all the role players. 
 
7.4 Responses to the activities  
 
It is important to understand that system design wi ll include facilitating some response. The precise 
response can be ascertained from the information ch ecklist. 
 
7.5 CCTV equipment selection  
 
Determine the type of cameras, lenses, enclosures, brackets, the transmission medium, recording 
and  methods, etc. to be used.  
 
7.6 Control point considerations  
 
The layout of the control room, the configuration o f the operator equipment, the environmental 
conditions, and the selection and training of opera tors are important issues to be considered. 
 
A specification can be produced by analyzing and qu antifying the information checklists of all the 
stakeholders. 
 
8 Determining the design and specification  
 
8.1  The information checklists will define a wide range  of key specification points, such as the 
scope and level of effectiveness required, factors related to image quality and contents based on 
performance. 
 
8.2  Nearly every element of the checklist can be measur ed in some way, which ensures not only 
that it can be specified, but also that it can be t ested at the commissioning stage. The design has 
to take into account a wide range of factors, such as the need for communication between the 
scene to be viewed and the observation point, mecha nisms for ensuring that the operator is 
effectively cued when incidents occur, artificial l ighting considerations, etc. In some cases there 
might be technical constraints, such as existing co mmunication systems. 
 
8.3  Although the checklist might include many explicit requirements, the methodology allows the 
development of technical specifications to be ident ified as a separate task. The system designer 
can be given full responsibility for defining both the mechanisms to be used to meet the 
requirements and for the choice of equipment. 
 
8.4  A design specification can be either: 
a) Exclusively needs-based (the operational require ments based tender), which will require the firm 
that tenders to provide all the technical informati on. This is the desired format since the end user 
then only has to stipulate his needs. The what, whe re, why and how are stipulated by the firm, or 
b) Partially needs-based or technically based, whic h requires minimum input from the tendering 
firm, or 
c) Technically based, which requires only a cost-ba sed response from the tendering firm   
 KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved  9 Tender based on operational requirements  
 
9.1 By inviting tenders on the basis of the operational  requirements contained in the design              
specification, it is clearly indicated to industry that bids for the project will be judged on the bas is of 
performance, functionality and costs. It enables bi dders to be clear about the needs and 
requirements of the customer and to know that their  proposals will be compared on a like-for-like 
basis. This leveling of the playing field is a freq uently stated prerequisite by suppliers if they are  
expected to put significant effort into their propo sals. A lack of clarity at this stage leads to 
 
a) Vague statements by suppliers and customers, and  
b) Under pricing to get the business, followed by i nevitable dissatisfaction owing to corners being 
cut, cost overruns or performance shortfalls. 
 
9.2  Bids can be compared using a compliancy matrix agai nst the requirements of each design 
specification. Both performance and price can be as sessed in this way. In drawing up contracts, 
careful attention to detail will be needed if unsui table bidders are to be excluded or their bids 
declared non-compliant. Often the compliancy matrix  will reveal bidders who declare their 
compliance but are in fact unable to comply. 
 
9.3  A contract should be strengthened by the inclusion of appropriate standards and codes of 
practice. 
 
10 Functional and performance test requirements  
 
10.1  The information checklist leads direct to functiona lity and performance test requirements that 
can be included in the design specification, thereb y providing a straightforward means of applying 
a range of pass or fail criteria. If the installed system passes, it is put into service. If it fails,  a 
number of routes are open. It might be that signifi cant changes have occurred that are beyond the 
control of the security contractor and have a mater ial effect on the operational requirements. For 
instance, building lines might have changed causing  blind spots. Whatever the reason for failure, a 
review of the operational requirements will help de termine the seriousness of the performance 
shortfall and the impact on security. 
 
10.2  A revised design specification can form the basis o f a remedial contract if that is the chosen 
solution. If the cause of failure is within the con tractor's control, remedial action can be requested  
against a clearly stated performance improvement. A lternatively, the design specification could be 
reviewed to see if any local or general easement is  possible without sacrificing the operational 
objectives.  
 
11 Management of the CCTV surveillance system  
 
It is essential that once the CCTV surveillance sys tem has been put into service it is managed 
effectively to ensure that it continues to meet the  original operational requirements and is suitably 
adapted to meet any changing needs when required. P art of this management process will be to 
make sure that every aspect of the system is mainta ined at high operating standards to ensure that 
the system is optimally used.  
 
 
 
 
 
 
 
 
 
 KENYA STANDARD  KS 2110-2:2009  
© KEBS 2009— All rights reserved             Annex A 
 
Information Checklist 
 
CCTV operational requirements 
Problem definition  Operational response       Observer role          Miscellaneous  
1.Target to be observed: 6. Required result of a 
successful response to 
the activity: 11. What will the 
observer do when the 
activity occurs? 16. Stakeholders 
2. What activity of the    
target is of concern? 7. Who makes the 
response? 12. How will the 
observer 17. What priority is 
assigned  to this task 
3. Purpose of the 
observation: 8. Timescale of the 
response for it to be 
successful. 13. How quickly does 
the observer need to 
act, search for and 
detect the target 18. Likelihood of an 
activity occurring and 
how often 
4. Picture quality and 
content factors needed to 
achieve success: 9. When is observation 
needed? 14.Who makes the 
observation on which 
the response is based 19. How effectively does 
the task have to be done 
5. Spare 10. Conditions under 
which the system needs 
to be effective: 15. Where will the 
observations take 
place? 20. Benefits of doing the 
action versus not doing 
at all