From: Subject: References Dear Bidders, N ATO UNC LA SSIF IE D ...

N ATO UNC L A SSIF IE D 

Releasable to ISAF 

NA T O Cons ult a tion , Comm and and C o nt rol A gency 

A ge nce d e co nsu lt at ion , d e comm a ndeme nt et d e cont ra le de I' OTA N 

NC3A1ACQ/ASG/2012/431 

15May2012 

To: 

From: 

Subject: 

See Distribution List 

The General Manager, NATO C3 Agency 

Invitation For Bid (IFB) CO 13355-0PL, Provide Enhanced Camp 

Surveillance System for HQ ISAF 

References 

Dear Bidders, 

a) 

b) 

c) 

d) 

e) 

f) 

AC/4-DS(2011 )0031 dated 22 November 2011 

Serial2011 /5VA30641 

Decision Document AC/4(PP) D/26954 

AC/4-D(2011 )0009 -FINAL-AS1 dated 25 July 2011 , Non-Article 

5 NATO Led Operations-NSIP Procurement Regulations 

Framework Document 

AC/4-D(2007)0003 Alliance Operations and Missions Procedure 

Invitation for Bid (IFB-CO-13355-0PL), dated 4 May 2012 

1. The purpose of this amendment is to provide Purchaser responses to Bidders 

clarification requests and to amend the Statment of Work (Book II Part IV). The 

clarification responses are for information only and do not change the 

requirements of the Invitation for Bid (IFB). The NATO C3 Agency responses are 

included in Attachment 1 under (T1 toT2). Annex I of the SOW is hereby 

amended to remove the paragraph at 1.1.4.1.8. The visualisation of monitors is 

now corrected referenced at Annex I. 

2. With respect to the Invitation for Bid (IFB) referenced above, please be informed 

that the Bid Closing Date as indicated in the Bidding Instructions, Paragraph 

2.3.1 , Bid Delivery and Bid Closing, is unchanged and remains 14:00 HOURS 

Central European Time on, Friday 8 June 2012, at which time and date bidding 

shall be closed . 

3. Please note that in accordance with Paragraph 2.9 of the Bidding Instructions - 

Modification and Withdrawal of Bids - Bidders who have submitted their Bid 

before receiving the notification of extension to the Bid Closing Date, have the 

right to modify or withdraw the Bid , as indicated therein. Except as provided 

herein, all other terms and conditions of the Bid documents remain unchanged. 

Cude Waalsdorperweg 61 , 2597 AK The Hague, (P.O. 8 0x 174 2501 CD). The Netherlands. Tel. + 31 (0)70 3743000, Fax. + 31 (0)70 3743239 

Boulevard Leopold III, 1110 Bruxelles. Belgique. Tel. + 32 (0)2 707 4111 or xxxx (4 digit ext.), Fax. + 32 (0)2 707 8770. NCN 255 )()()(X (4 digit ext.) 

NAT O 

UNCLA S SIF IE D 


I

NATO UN CLASSIFIED 

Releasable to rSAF 

4. The Purchaser point of contact for all information concerning this Invitation For 

Bid is: 

Mr. Joseph L. Vitale (ACQ/ASG 

T: +32 (0)2 707 8321/8308 

F : +32 (0)2 707 8770 

E: joseph.vitale@nc3a.nato.int. 

FOR THE GENERAL MANAGER: 

oseph L Vitale 

ior Contracting Officer 

Attachement 1: Purchaser Clarifications 

NATO UNCLASSIFIED 


II



Distribution List for AMD 1 IFB-CO-13355-0PL 

Prospective Bidders (sent separately in electronic version) 

1 

NATO Delegations (Attn: Infrastructure Adviser): 

Albania 

Belgium 

Bulgaria 

Canada 

Croatia 

Czech Republic 

Denmark 

Estonia 

France 

Germany 

Greece 

Hungary 

Iceland 

Italy 

Latvia 

Lithuania 

Luxembourg 

The Netherlands 

Norway 

Poland 

Portugal 

Romania 

Slovakia 

Slovenia 

Spain 

Turkey 

United Kingdom 

United States 

Belgian Ministry of Economic Affairs 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 



III



Embassies in Brussels (Attn: Commercial Attache): 

Albania 

Bulgaria 

Canada 

Croatia 


Denmark 

Estonia 

France 

Germany 

Greece 

Hungary 

Italy 

Latvia 

Lithuania 

Luxembourg 1 

The Netherlands 1 

Norway 1 

~Iand 1 

Portugal 1 

Romania 1 

Slovakia 1 

Slovenia 1 

Spain 1 

Turkey 1 

United Kingdom 1 

United States electronic copy to brussels.office.box@mail.doc.gov 1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

NATO HQ 

NATO Office of Resources 

Management and Implementation Branch - NOR 1 

Director, NATO HQ C3 Staff 

Attn: Executive Co-ordinator 1 

SACTREPEUR 

Attn: Infrastructure Assistant 1 

Strategic Commands 

ACT Attn: ACOS C41 1 

ACO Attn: ACOS J-6 1 

NATO Agencies 

NCSA Attn: Documentation Ctr. 1 

NAMSA Attn: Communications and Calibration Programme 1 



IV

NC3A -Internal Distribution 



ACQ 

NLO (Mr C. Ulsh) 

ACQ/ASG PCO (Mr. P Chulick) 

ACQ/ASG CO (Mr. J Vitale) 

DOP 

CAT9 PM (U Cdr J. Williams) 

CAT9 PMO (Mr M. Brown) 

DOPIILS (Mr. R. Spijkerman) 

DSA 

CRO Programme Manager (Mr Tim Murphy) 

DSA/ACO (Mr. Erick Lesbaupin) 

Legal Office 

Legal Adviser (Mrs. S. Rocchi) 

Deputy General Manager 

Principle Administrative Assistant (Mrs. M.L Le Bourlot) 

Registry 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

NATEX 


Denmark 

France 

Hungary 

Germany 

Greece 

Italy 

The Netherlands 

Norway 

Poland 

Spain 

Turkey 

United Kingdom 

United States 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 

1 



V





VI

N A T O UN C L A S S I F I E D 

Releasable to ISAF I 

IFB-CO-13355-OPL Book I- Annex D 

INVITATION FOR BID 

IFB-CO-13355-OPL 

AMD 1 

Provide Enhanced Camp Surveillance System for HQ ISAF 

Purchaser Clarifications 

N A T O U N C L A S S I F I E D 


Page D-1




ADMINISTRATION or CONTRACTING 

Serial 

NR 

A.1 

IFB 

REF 

QUESTION ANSWER Status 

A.2 

A.3 



Page D-2




PRICE 

Serial 

NR 

P.1 

IFB 

REF 


P.2 

P.3 



Page D-3




TECHNICAL 

Serial 

NR 

IFB 

REF 

T.1 In Book II 

Part 4, 

Section 4. 

Technical 

requirements 

it states 

NetApps, 

Cisco 

specifically, 

T.2 In Book II 

Part 4, 

Section 5. 

Training: 

Listed here is 

NetApps, 

VMware, 

Symantecs, 

OnTap, 

RedHat and 

other 

software 

training. 


Unfortunately, this is written as a brand 

name NetApp requirement. This is clearly 

outlined in the SOW as they even list the 

exact parts numbers and quantities, is this 

NetApps Brand Name procurement Can a 

vendor bid another Hardware solution 

Are there any pre-requisites, i.e. equipment, 

manuals, security Clearances, number of 

participants, etc for this training 



Page D-4 

4.5.2.5 And I.1.5.2.4 (technical annex) specifies 

CISCO or 3COM routers and switches if used within 

the proposed solution. These are the only brands 

currently authorized for use in ISAF as stated in the 

technical annex. 

The purchaser does not understand the bidder’s 

referral to the NetApp requirement. The only brand 

name requirements are for routers and switches. 

The system itself is NATO Unclassified and therefore 

the training material is also NATO unclassified. The 

contractor shall provide training on the operation and 

maintenance of the equipment and for only those 

software applications which are proposed for use. 

This shall be a windows based system that is 

complaint through MS Windows 7. 

There is no requirement for VMWARE, RedHat 

Linux, Symantec, or On Tap software mentioned 

within Book II Part 4. However, if these tools are to 

be used in the proposed design, then training must 

be provided.




TECHNICAL 

Serial 

NR 

T.3 

IFB 

REF 




Page D-5



CO-13355-OPL 

Part IV Statement of Work 

PART IV 

PROVIDE ENHANCED CAMP SECURITY SURVEILLANCE 

SYSTEM - HEADQUARTERS INTERNATIONAL SECURITY 

ASSISTANCE FORCE (HQ ISAF) 

STATEMENT OF WORK (SOW) 


Releasable to ISAF



CO-13355-OPL 


DOCUMENT HISTORY 

Version Author Date Reason for Change Superseded 

Document 

0.1 Williams 1 st Draft - 

0.2 Williams 24/02/12 Spec Review Board 

0.1 

integration 

0.3 Janovszki 24/02/12 SOW ANNEX E & I 

0.2 

Modification 

0.4 Williams 12/03/12 ISAF Project Officers 

0.3 

comment incorporation 

0.5 Williams 11/05/12 Removal of overspecification 

artifacts 

0.4 


Releasable to ISAF



CO-13355-OPL 


TABLE OF CONTENTS 

SECTION 1: Introduction .................................................................................................. 4 

SECTION 2: Applicable documents ................................................................................ 10 

SECTION 3: Project Management .................................................................................. 13 

SECTION 4: System Design, Engineering and Implementation .................................. 26 

SECTION 5: Integrated Logistics Support (ILS)........................................................... 34 

SECTION 6: Quality Assurance and Control ................................................................ 52 

SECTION 7: Documentation ............................................................................................ 55 

SECTION 8: Testing and Acceptance ............................................................................. 59 

SECTION 9: List Of Sites ................................................................................................. 67 

Annex A: Acronyms ............................................................................................................... 69 

Annex B: Proposed camera location map HQ ISAF .......................................................... 72 

Annex C: Notional Equipment configuration diagram ...................................................... 74 

Annex D: Example ResiliEnt IP network plan for IP CCTV ............................................ 75 

ANNEX E General Equipment Description ........................................................................ 76 

Annex F: Approximate Dimensions of the HQ ISAF Compound ..................................... 77 

Annex G: Poles lighting standards ....................................................................................... 78 

Annex H: Poles painting standards ...................................................................................... 80 

Annex I: System Requirements Specification (SRS)........................................................... 81 


Releasable to ISAF



CO-13355-OPL 


SECTION 1: 

INTRODUCTION 

1.1.Purpose 

1.1.1. The purpose of this Contract is to implement and support the Headquarters (HQ) 

International Security Assistance Force (ISAF) Kabul, Closed Circuit TV-based 

Ground Security Surveillance System, henceforth referred to as (CCTV HQ 

ISAF). This is a Requirements Contract for services and supplies to design, 

integrate, test, implement, and provide life-cycle support for the CCTV HQ ISAF 

system to meet an operational availability of 99.9% with regard to full camera 

coverage. 

1.2.Background 

1.2.1. The existing CCTV system at the HQ ISAF compound is rapidly approaching its 

end of life. An updated system that provides day and night vision for the 

perimeter and all points of entry is required. 

1.2.2. The contractor shall deliver the updated CCTV HQ ISAF system that meets the 

requirements specified within this IFB package to augment current force 

protection efforts. 

1.3.Contract Scope 

1.3.1. The Contract shall cover the design and implementation of CCTV HQ ISAF 

System. The CCTV HQ ISAF System shall provide adequate coverage of the 

exterior and all points of access to the HQ ISAF compound. Remote monitoring 

and control of the system shall be performed from the Base Defence Operations 

Centre (BDOC), hosted in the Base Support Group (BSG) HQ building. The 

Entry Control Point (ECP) shall be able to view and control cameras from the 

corresponding gate (e.g. Front Entry Control Point) from the guard house. When 

there is a conflict, the BDOC shall retain control. 

1.3.2. The implementation of CCTV HQ ISAF shall be followed by warranty and 

Contractor Support, for a 12 month period, effective from Final System 

Acceptance (FSA), with options to extend that support by further periods of 12, 

24, or 36 months. 

1.4.Roles 

1.4.1. The Contractor shall be aware of the roles played by the relevant stakeholders, as 

described below, and shall deliver the CCTV HQ ISAF System according to the 

Contract, through direct liaison with: 

1.4.1.1. The Purchaser (the NATO Consultation, Command and Control Agency (NC3A)); 

the NC3A is assigned as the Host Nation (HN) for the Project and is responsible 

for Project Management and technical matters (Project Manager, Technical 



4/104





5/104 

CO-13355-OPL 


Manager), including delivery, information assurance (e.g. security accreditation 

process), acceptance from the Contractor (through FAST, PSA and FSA) handover 

to the end-users during PSA, and handover to the service provisioning authority 

during FSA. 

1.4.1.2. Following the formal handover from NC3A: 

1.4.1.2.1. The CCTV HQ ISAF System users will act as the 1 st level maintenance echelon 

for the System, in theatre, supported by HQ ISAF BSG staff at HQ ISAF (2 nd 

level), and the Contractor (3 rd level, at the factory, or in theatre) 

1.4.1.2.2. Any support activities, beyond the first year following FSA, are to be covered 

under NAMSA’s O&M framework. NAMSA will act as Service Provisioning 

Authority (SPA) for the CCTV HQ ISAF System, in theatre. 

1.5.General requirement 

1.5.1. The Contractor shall complete the work in accordance with Book II Part I: 

Schedule of Supply and Services (SSS). 

1.5.2. The CCTV HQ System will be installed within the confines of the HQ ISAF 

compound. Proposed locations for the installations and the approximate 

dimensions of the HQ ISAF compound are provided, for information purposes, 

and can be found at the following Annexes: 

1.5.2.1. Annex A: Acronym List 

1.5.2.2. Annex B: Proposed camera location map HQ ISAF 

1.5.2.3. Annex C: Notional Equipment Configuration Diagram 

1.5.2.4. Annex D: Resilient IP network plan for CCTV 

1.5.2.5. Annex E: General Equipment Description 

1.5.2.6. Annex F: Approximate Dimensions of the HQ ISAF Compound 

1.5.2.7. Annex G: Poles Lighting Standards 

1.5.2.8. Annex H: Poles Painting Standards 

1.5.2.9. Annex I: System Requirements Specification 

1.5.3. The Contractor shall be responsible for: 

1.5.3.1. Procurement 

1.5.3.2. Shipment to HQ ISAF with the exception of the leg between CLD Brunssum and 

Depot 26, Afghanistan.



CO-13355-OPL 


1.5.3.3. Delivery 

1.5.3.4. Installation 

1.5.3.5. Testing of the CCTV System 

1.5.3.6. Training of HQ ISAF personnel 

1.5.3.7. Provision of One (1) year Contractor Logistic Support (CLS) and One (1) year 

warranty service. 

1.5.4. The Contractor shall perform a site survey within 4 weeks following Effective 

Date of Contract (EDC) with the Purchaser Project Manager (PM) or his in-theatre 

representative, to finalise implementation details. During the site survey the 

contractor shall validate and optimize the design to provide a cost effective 

resilient design that meets the Force Protection requirements. 

1.5.5. The Project Implementation Plan (PIP) shall include a listing of all requirements 

with their associated timelines and any dependencies or risks that must be 

mitigated by the Contractor or Purchaser PM. 

1.5.6. Civil Works. 

1.5.6.1. The contractor shall develop a civil works plan to include required ducting and/or 

trenching. The use of existing ducting and trenching shall be employed where 

possible. From the proposed camera locations, it is estimated an average run to 

interface with base utilities is approximately 10 meters for power and 50 meters 

for communications cabling. 

1.5.6.2. Civil works shall include any required trenching, ducting, cabling, earthing, 

interconnecting with base facilities and services, mounting, and laying of 

foundations. Civil works also involves providing the updates to schematics and 

diagrams for all work performed with “As Built documentation.” 

1.5.6.3. The BDOC is located in BSG HQ and is the primary control point for all security 

cameras for the CCTV HQ ISAF. 

1.5.6.4. Use of local Afghan labor is authorized. However, it is the sole responsibility of 

the contractor to provide cleared escorts at the ratio of 1 cleared escort for every 3 

uncleared contractors. “Cleared escort” refers to an individual in possession of a 

valid NATO security clearance. 

1.5.7. The contractor shall ensure safe and resilient connections to the HQ ISAF power 

grid for all equipment requiring power. Base power shall be available from HQ 

ISAF. The contractor shall ensure that each camera is supported by an UPS and 

surge protection to maintain continuity of operations in the event of power 

disruption, spikes, or temporary loss. 



6/104





7/104 

CO-13355-OPL 


1.5.8. The contractor shall escort uncleared personnel engaged in work for this project. 

1.5.9. An Earth and grounding system shall be provisioned and provide effective 

protection for personnel and equipment. The cameras, masts, UPS, etc. shall be at 

the same equipotential plane by means of bonding. 

1.5.10. The masts, CCTV equipment, UPS and ancillary equipment shall be equipped with 

a lightning protection system. The equipment shall not be damaged and continue 

to operate without degradation when subjected to the standard lightening 

waveforms typical for the Kabul environmental conditions. 

1.5.11. Appropriate surge protection devices (SPD) shall be used to provide sufficient 

protection for the equipment and interfaces. 

1.5.12. It is the contractor’s responsibility to provide all necessary equipment and 

hardware to connect to the CCTV system 

1.5.13. The Contractor shall propose an engineering change based on the Site Survey 

Report (SSR) via the Purchaser PM. The PM shall bring all major deviations 

before the project board for approval. 

1.5.14. The Contractor shall be required to complete the installation work in accordance 

with the updated SSS as agreed upon by the Contractor and Purchaser PM. 

1.5.15. The Contractor shall identify to the Purchaser PM at least 2 weeks before a 

Contractor visit to HQ ISAF all on-site heavy machinery, logistics or other support 

required. 

1.5.16. The Contractor shall perform on-site commissioning and provide training to HQ 

ISAF Force Protection (FP) personnel. 

1.6.Other Requirements 

1.6.1. As an option the contractor shall provide additional Type I, Type II or Type III 

cameras, masts, and installation to support increased physical security 

requirements and base improvements. 

1.6.2. As an option the contractor shall provide an additional monitoring and control 

station to support additional HQ ISAF entry control points i.e. a possible rear entry 

control point. 

1.6.3. As an option the contractor shall integrate the existing CCTV system with the new 

system. Currently, no reuse of existing hardware (cameras, wiring, masts, et 

cetera) is anticipated. 

1.6.4. As an option the contractor shall provide an additional year(s) of Contractor 

Logistics Support (CLS). CLS shall include, but is not limited to: level three (3) 

maintenance where the level of support provided is defined as a maximum of two



CO-13355-OPL 


(2) visits to HQ ISAF during the year, problem and modification analysis, complex 

repairs and/or replacements, detailed calibrations, supply support, overhaul and 

rebuild, implementation of major and/or critical changes, restoration (e.g. 

emergency maintenance) that requires specialised maintenance personnel and 

equipment, monitor and coordinate the transportation of faulty equipment out of 

theatre and replacement equipment back into theatre. 

1.7.Statement of Work 

1.7.1. The Statement of Work (SOW) is organised to follow the outline of activities to be 

conducted during the life of the CCTV HQ ISAF System project as follows: 

1.7.1.1. Applicable Documents, SECTION 2 

1.7.1.2. Project Management, SECTION 3: 

1.7.1.3. System Engineering, Integration, and Implementation, SECTION 4: 

1.7.1.4. Integrated Logistic Support (ILS), SECTION 5: 

1.7.1.5. Quality Assurance and Control, Documentation and Testing and Acceptance, 

SECTION 6: 7 and 8 respectively. 

1.7.1.6. Project Documentation, SECTION 7. 

1.7.1.7. A list of acronyms used in this SOW is provided for reference at Annex A: 

Acronyms. 

1.8.Standards for interpretation of the Statement of Work 

1.8.1. The Contractor shall note that, when the term in-theatre is quoted in this SOW, 

this refers to the HQ ISAF compound in Kabul, Afghanistan and KAIA, 

Afghanistan. Work by the Contractor in theatre is not envisaged at any other 

locations. 

1.8.2. The list of applicable and reference documents detailed in SECTION 2: includes 

a variety of Allied Publications and Military Standards (MIL-STDs). However, the 

following should be noted: 

1.8.2.1. While these are NATO reference documents, there are national and international 

standards that are considered to be equivalent and are cited as such within these 

documents. 

1.8.2.2. Where there is a national or international standard which is not specifically 

referenced in the STANAGs, Allied Publications, or MIL-STDs as being 

equivalent, the Contractor may propose to utilise such a standard. 



8/104



CO-13355-OPL 


1.8.2.3. The Purchaser, however, reserves the right to deny such a request and demand 

performance in accordance with the standard cited in the SOW. 



9/104



CO-13355-OPL 


SECTION 2: 

APPLICABLE DOCUMENTS 

2.1.Compliance Documents 

2.1.1. NATO 

2.1.1.1. Allied Quality Assurance Publications 

2.1.1.1.1. AQAP 110, NATO Quality Assurance Requirements for Design, Development, 

and Production. 

2.1.1.1.2. AQAP 119, NATO Guide to AQAPs -110, -120 and -130 

2.1.1.1.3. AQAP 130, NATO Quality Assurance Requirements for Inspection and Test 

2.1.1.1.4. AQAP 150, NATO Quality Assurance Requirements for Software Development. 

2.1.1.1.5. AQAP 159, Guidance for the Use of AQAP 150. 

2.1.1.2. Allied Configuration Management Publications 

2.1.1.2.1. ACMP 1, NATO Requirements for the Preparation of Configuration Management 

Plans. 

2.1.1.2.2. ACMP 2, NATO Requirements for Configuration Identification. 

2.1.1.2.3. ACMP 3, NATO Requirements for Configuration Control--Engineering Changes, 

Deviations, and Waivers. 

2.1.1.2.4. ACMP 4, NATO Requirements for Configuration Status Accounting. 

2.1.1.2.5. ACMP 5, NATO Requirements for Configuration Audits. 

2.1.1.2.6. ACMP 6, NATO Configuration Management Terms and Definitions. 

2.1.1.2.7. ACMP 7, NATO Configuration Management Guidance on the Application of 

ACMPs 1 to 6. 

2.1.1.3. NATO Standard 

2.1.1.3.1. STANAG 4107, Mutual Acceptance of Government Quality Assurance and Usage 

of the Allied Quality Assurance Publications. 

2.1.1.3.2. STANAG 4159, NATO Materiel Configuration Management Policy and 

Procedures for Multinational Joint Projects. 

2.1.1.3.3. STANAG 6001, Language Proficiency Levels. 



10/104



CO-13355-OPL 


2.1.1.3.4. NATO Security Documents 

2.1.1.3.5. C-M(2002)49, Security within the North Atlantic Treaty Organisation. 

2.1.1.3.6. NATO Security Committee and NATO C3 Board – Primary Directive on 

INFOSEC. 

2.1.1.3.7. Review of the Nature and Extent of the Threats to, and Vulnerabilities of, CIS 

2.1.1.3.8. Guidelines for the Security Approval or Security Accreditation of CIS 

2.1.1.3.9. Guidelines for Security Risk Assessment and Risk Management of CIS 

2.1.1.3.10. Guidelines for the Development of Security Requirement Statements (SRSs) 

2.1.1.3.11. Guidelines for the Structure and Content of Security Operating Procedures 

(SecOPs) for CIS 

2.1.1.4. Other NATO documents 

2.1.1.4.1. ACT Directive 75-10 Bi-SC Education and Individual Training Directive 

2.1.1.4.2. NATO Interoperability Management Plan, Volume 2. 

2.1.1.4.3. AC/322 NATO Architecture Framework V3. 

2.1.1.4.4. NATO Bi-SC Directive 75-7 Education and Individual Training. 

2.1.2. Non-NATO 

2.1.2.1.1. RFC 1883, Internet Protocol, Version 6 (IPv6) Specification. 

2.1.2.1.2. RFC 791, Internet Protocol, Version 4 (IPv4) Specification. 

2.1.2.2. International Standards Organisation 

2.1.2.2.1. ISO/IEC 7810:1995 Identification cards -- Physical characteristics. 

2.1.2.2.2. ISO/IEC 7816-1:1998, Identification cards -- Integrated circuit(s) cards with 

contacts -- Part 1: Physical characteristics. 

2.1.2.2.3. ISO/IEC 7816-2:1999, Information technology -- Identification cards -- Integrated 

circuit(s) cards with contacts -- Part 2: Dimensions and location of the contacts. 

2.1.2.2.4. ISO/IEC 7816-3:1997, Information technology -- Identification cards -- Integrated 

circuit(s) cards with contacts -- Part 3: Electronic signals and transmission 

protocols. 



11/104



CO-13355-OPL 


2.1.2.2.5. ISO/IEC 9126: Information Technology – Software Product Evaluation – Quality 

characteristics and guidelines for their use. 

2.1.2.2.6. ISO 9001:2008, Quality Management Systems: Requirements. 

2.1.2.2.7. MIL-STD-810 Department of Defense Test Method Standard for Environmental 

Engineering Considerations and Laboratory Tests. 

2.2.Reference Documents 

2.2.1. NATO 

2.2.1.1. AC/322(SC/5) N (2005)0005, dated 14 June 2005. 

2.2.1.2. AC/322 D/0030T. 

2.2.1.3. Terminology Clarification for Security Accreditation/Approval/Certification. 

2.2.1.4. AC/4-D/2261, dated 24 March 1998. 

2.2.1.5. NATO International Competitive Bidding (ICB) procedures. 

2.2.1.6. AC/4-D (95)002-ADD3-REV1, dated 17 April 2003. 

2.2.1.7. NATO Infrastructure Committee Urgent Requirements Procedures. 

2.2.1.8. Procedures Governing the Use of Basic Ordering Agreements (BOA(s)) by NC3A. 

2.2.1.9. AC/322-D(2009)0020-AS1. 

2.2.1.10. STANAG 2895 MMS – Climatic conditions 

2.2.1.11. Allied Environmental Conditions and Test Publication (AECTP) 200: 

Environmental conditions. 

2.2.1.12. AECTP-200 Allied Environmental Conditions and Test Publication 

2.2.2. Non-NATO 

2.2.2.1. ICAO Annex 14 Volume 1 Aerodrome design and operations Chapter 6. 

2.2.2.2. ICAO Doc 9157 Aerodrome Design Manual Part 4 Chapter 14. 



12/104



CO-13355-OPL 


SECTION 3: 

PROJECT MANAGEMENT 

3.1.Introduction 

3.1.1. This section outlines the Project Management Area for the CCTV HQ ISAF 

Contract. 

3.1.2. The success of the CCTV HQ ISAF System depends upon a sound project 

management approach. Full and open communication between the Contractor and 

the Purchaser is an essential element of this approach. 

3.1.3. A project cannot be risk-free. Problems will occur. The goal of the Contractor’s 

project management shall not be to eliminate problems, but to ensure that those 

that do occur are identified early, assessed accurately, and resolved quickly in 

partnership with the Purchaser. 

3.2.Organisation 

3.2.1. Purchaser Project Organisation and Responsibilities 

3.2.1.1. The Purchaser Project Manager (PM) will act as the Purchaser’s representative and 

will be the primary interface between the Contractor and Purchaser from the 

Effective Date of Contract (EDC). 

3.2.1.2. The Purchaser PM will be supported by specialists in certain areas who may, from 

time to time, be delegated to act on the PM’s behalf in their area of expertise. 

3.2.1.3. Neither the PM, the specialists, other team members, nor any other NATO 

personnel may make changes to the terms and conditions of the Contract but may 

only provide the Purchaser’s interpretation of technical matters. 

3.2.1.4. All changes to the Contract will be made through the Purchaser's contracting office 

only. 

3.2.1.5. The Purchaser PM, the specialists, and the key Stakeholders representatives 

collectively form the CCTV HQ ISAF Integrated Project Management Team 

(IPMT). The Project Executive chairs the CCTV HQ ISAF IPMT Project Board. 

3.2.1.6. The CCTV HQ ISAF IPMT serves as the primary mechanism for monitoring 

project status, resolving issues or conflicts within the project, and advising the 

Purchaser’s CCTV HQ ISAF PM. 

3.2.1.7. Provided that the Contractor has successfully discharged his duties under this 

contract and made available to the Purchaser the required capability, the Purchaser 

will accept from the Contractor the delivered capability and any associated 

equipment, services, and documentation. 

3.2.2. Contractor Project Management Office 



13/104



CO-13355-OPL 


3.2.2.1. The Contractor shall establish and maintain a Project Management Office (PMO) 

to perform and manage all efforts necessary to discharge all his responsibilities 

under this Contract. The Contractor shall describe their Project Management 

Office (PMO) by providing a comprehensive organisational chart detailing the 

specific roles, responsibilities and authority of each member of the Contractor’s 

Project Team. 

3.2.2.2. The Contractor shall provide a list of “Key Personnel” that are considered to be 

key to the performance of the Contract as defined in Section 26 of Book II, Part II 

(Contract Special Provisions). Key Personnel cannot be replaced without prior 

approval of the Purchaser and shall include at a minimum the Project Manager, 

Deputy Project Manager, Integrated Logistic Support Manager, and the Fielding 

and Support Manager (if different from the Project Manager) with functions as 

defined below. The Contractor shall quantify the qualifications and experience of 

the Key Personnel assigned to the Contract. The Contractor shall demonstrate that 

all Key Personnel have sufficient experience to complete the project. Curriculum 

Vitae shall be submitted for the Project Manager (PM). The PM must have a 

minimum of 2 years experience. A brief summary of the experience for all other 

key personnel shall be submitted. 

3.2.2.3. The Contractor shall also provide all necessary manpower and resources to 

conduct and support the management and administration of operations in order to 

meet the objectives of the program, including taking all reasonable steps to ensure 

continuity of personnel assigned to work on this project. The Contractor shall 

provide a narrative or organizational chart detailing all major Contractor operating 

units and any Sub-Contractors and Suppliers involved in the development of the 

CCTV HQ ISAF system and a description of the portion of the overall effort or 

deliverable items for which they are responsible to be included with the PIP at 

EDC + 2 weeks. This narrative must clearly demonstrate that the Contractor 

possesses the management capability to successfully control and coordinate the 

work of their subcontractors. 

3.2.2.4. Project Manager. The Contractor shall designate a suitably qualified Project 

Manager (PM), who will direct and co-ordinate the activities of the Contractor's 

project team. The Project Manager shall be the Contractor's primary contact for the 

Purchaser’s CCTV HQ ISAF PM and shall conduct all major project design, test, 

and review meetings. 

3.2.2.5. Technical Lead. The Contractor shall designate a suitably qualified Technical Lead 

for the Project. The Technical Lead shall lead the analysis, design, development, 

integration, and follow-on enhancement efforts of the Contractor. 

3.2.2.6. Test Director. The Contractor shall designate a suitably qualified individual to 

serve as the Test Director for all test activities conducted under this Contract. The 

Test Director shall report to a separate manager within the Contractor's 

organisation, at a level equivalent to or higher than the Project Manager. 



14/104



CO-13355-OPL 


3.2.2.7. Quality Assurance Manager. The Contractor shall designate a suitably qualified 

individual to serve as the Quality Assurance Manager for activities under this 

Contract. The Quality Assurance Manager shall report to a separate manager 

within the Contractor's organisation, at a level equivalent to or higher than the 

Project Manager. 

3.2.2.8. Integrated Logistics Support Manager. The contractor shall designate a suitably 

qualified individual to serve as the lead for integrated logistics support. The ILS 

manager shall coordinate all transportation activities of materials to and from 

ISAF. The ILS manager shall report to the project manager. 

3.2.2.9. Fielding and Support Manager. The Contractor shall designate a suitably qualified 

individual to serve as the lead for implementation and operational support at the 

various facilities involved, including those in theatre. 

3.2.2.10. Training Manager. The Contractor shall designate a suitably qualified individual to 

serve as the training manager throughout the performance of the Contract, and 

across the designated training sites. The designated training sites are the Purchaser 

premises ISAF HQ in Kabul. 

3.2.2.11. Two or more of the roles above can be played by the same individual, in which 

case the Contractor shall provide proof that the required qualifications and 

availability requirements can be met to the Purchaser’s satisfaction, throughout the 

period of performance of the Contract. 

3.3.Project Planning 

3.3.1. Project Implementation Plan 

3.3.1.1. The Contractor shall provide a complete Project Implementation Plan (PIP), which 

shall describe how the Contractor will implement the totality of the Project, 

including details of the Project Controls that will be applied. 

3.3.1.2. The PIP shall cover all aspects of the project implementation including its 

management structure and project control processes, personnel assignments, 

external relationships and project control necessary to provide the capability 

required by this Contract. 

3.3.1.3. The PIP shall identify all major Contractor operating units and any Sub- 

Contractors involved in the development of the CCTV HQ ISAF and a description 

of the portion of the overall effort or deliverable item for which they are 

responsible. 

3.3.1.4. The PIP shall contain an organisational chart showing the members of the 

Contractor’s Project Team (including the members of the PMO listed in section 

3.2.2) and showing their respective responsibilities and authority. 



15/104



CO-13355-OPL 


3.3.1.5. The PIP shall be sufficiently detailed to ensure that the Purchaser is able to assess 

the Contractor plans with insight into the Contractor’s plans, capabilities, and 

ability to satisfactorily implement the entire project in conformance with the 

requirements as specified in this SOW. 

3.3.1.6. The PIP shall follow the outline of this SOW, unless otherwise agreed by the 

Purchaser. 

3.3.1.7. The initial version of the PIP shall be provided to the Purchaser for review and 

acceptance within two (2) calendar weeks after Effective Date of Contract (EDC). 

The PIP shall be reviewed by the Purchaser no later than five (5) working days 

after receipt. 

3.3.1.8. Upon Purchaser Acceptance, the PIP shall be placed under the Purchaser’s CCTV 

HQ ISAF CCB. 

3.3.1.9. The acceptance of the PIP by the Purchaser signifies only that the Purchaser agrees 

to the Contractor’s approach in meeting the requirements. This acceptance in no 

way relieves the Contractor from its responsibilities to meet the requirements 

stated in this Contract. 

3.3.1.10. The Contractor shall ensure that the PIP remains current throughout the duration of 

the Project to reflect the actual state of the Contractor's organisation and efforts. 

3.3.1.11. The PIP shall follow the structure of this SOW, and include the sections listed and 

described here below: 

3.3.1.11.1. Section 1: Project Overview 

3.3.1.11.2. Section 2: Applicable Documents 

3.3.1.11.3. Section 3: Project Management 

3.3.1.11.4. Section 4: System Design, Engineering and Implementation 

3.3.1.11.5. Section 5: Integrated Logistics Support 

3.3.1.11.6. Section 6: Quality Assurance and Control 

3.3.1.11.7. Section 7: Documentation 

3.3.1.11.8. Section 8: Testing and Acceptance 

3.3.1.12. The PIP shall be updated throughout the Project, and be subject to review at each 

Project Review Meeting (PRM). 

3.3.2. Project Overview 



16/104



CO-13355-OPL 


3.3.2.1. Section 1 of the PIP shall contain a Project overview, which shall provide an 

executive summary overview of the CCTV HQ ISAF, summarise the main 

features of each of the PIP sections, and indicate how the Project will be executed 

during the full lifetime of the Project. 

3.3.3. Applicable Documents 

3.3.3.1. Refer to section 1.8.2 

3.3.4. Project Management 

3.3.4.1. Section 3 of the PIP shall define the Contractor’s personnel structure and shall 

include: 

3.3.4.1.1. The management structure of the Contractor’s team; 

3.3.4.1.2. A list of Key Personnel assigned to the Contractor’s team and their respective 

roles, responsibilities and authority, as well as their qualifications, experiences and 

security clearances. The Contractor shall demonstrate that they have successfully 

implemented a project of similar scope in an operational environment supporting 

either NATO or National Forces. The Contractor shall identify the similarities of 

the system design and support delivered under previous Contract(s) to the system 

required under this procurement. 

3.3.4.2. This Section shall also include the following: 

3.3.4.2.1. Details of how the Contractor intends to address his responsibilities as defined 

in paragraph 3.2.1; 

3.3.4.3. Details of the Contractor’s methodology for Project Control as defined in 

paragraph 3.5 below. This shall include all aspects of Project Control and shall 

demonstrate how all the critical dates will be met; 

3.3.4.4. Details of how the Project Reporting as identified in paragraph 3.5.1 below will be 

organised; 

3.3.4.5. Details of the Contractor’s Risk Management methodology as defined in 

paragraph 3.6 below; 

3.3.4.6. Details of the Contractor’s Issue Management approach as defined in paragraph 

3.7 below. 

3.3.4.7. The PIP shall identify all major Contractor operating units and any Sub- 

Contractors and Suppliers involved in the development of the CCTV HQ ISAF, 

and a description of the portion of the overall effort or deliverable item for which 

they are responsible. 



17/104



CO-13355-OPL 


3.3.5. System Design, Engineering and Implementation 

3.3.5.1. Section Four of the PIP shall cover the System Design, Engineering and 

Implementation aspects of the Project. 

3.3.5.2. The System Design, Engineering and Implementation section shall include all the 

areas as detailed in SECTION 4: of this SOW. 

3.3.5.3. Section Four (4) shall address all functional, performance and technical 

specifications in the SRS at Annex I of this SOW. 

3.3.6. Integrated Logistics Support 

3.3.6.1. Section Five of the PIP shall cover the Integrated Logistics Support (ILS) aspects 

of the Project. 

3.3.6.2. This Section shall detail the Contractor’s approach to meeting the ILS 

requirements presented at SECTION 5 of this SOW. 

3.3.7. Quality Assurance and Control 

3.3.7.1. Section Six (6) of the PIP shall cover the Quality Assurance and Control aspects of 

the Project detailed at SECTION 6 of this SOW. 

3.3.7.2. This Section shall include details of how the Contractor shall establish, execute, 

document, and maintain an effective Quality Assurance (QA) program, throughout 

the Contract lifetime. 

3.3.8. Documentation 

3.3.8.1. Section Seven (7) of the PIP shall describe the Contractor’s Documentation Plan 

for all of the deliverable documents, including details of when these shall be 

provided. The Documentation Plan shall include the details as described at Section 

7 of this SOW. 

3.3.9. Testing and Acceptance 

3.3.9.1. Section 8 of the PIP shall define the Contractor’s Test and Acceptance Plan, which 

shall include a description of the allocation of personnel and the time schedule to 

accomplish all the test and acceptance activities up to and including Final System 

Acceptance (FSA) as detailed at SECTION 8 of this SOW. 

3.4.Project Master Schedule 

3.4.1.1. The Contractor shall establish and maintain a Project Master Schedule (PMS) that 

contains all contract events and milestones. The Contractor shall describe their 

strategy for implementing the project schedule and the CCTV HQ ISAF capability 

as outlined in the Schedule of Supplies and Services by providing a Project 



18/104



CO-13355-OPL 


Management Schedule (PMS) in Microsoft Project format. For each task, the PMS 

shall be thorough and specifically identify the start and finish dates, duration, 

predecessors, constraints, and resources needed to complete the project in 

accordance with schedule. The PMS shall also provide network, milestone, and 

Gantt views and identify the critical path for the overall project. 

3.4.1.2. The PMS shall show all contractual deliverables, the work associated with them, 

and their delivery dates. 

3.4.1.3. The PMS shall not be cluttered with events or tasks internal to the Contractor, 

unless they are of major importance to the Project. 

3.4.1.4. The PMS shall also be traceable to performance and delivery requirements of this 

SOW. The PMS shall be linked to Contractor resources to enable assessment of 

changes to staff, facilities, event dates, and system requirements. 

3.4.1.5. The PMS shall clearly identify the critical path. 

3.4.1.6. The PMS shall be provided in Microsoft Project format. For each task, the PMS 

shall identify the start and finish dates, duration, predecessors, constraints, and 

resources. The PMS shall provide network, milestone, and Gantt views and 

identify the critical path for the overall project. 

3.4.1.7. The initial version of the PMS shall be provided to the Purchaser for acceptance. 

Upon Purchaser Acceptance, the PMS shall be placed under the Purchaser’s 

CCTV HQ ISAF CCB. The Purchaser PM, without consulting the other HQ ISAF 

CCB members, can approve changes to the PMS, provided they do not affect other 

baseline documents, or incur additional costs. Changes to the PMS do not change 

contractual delivery dates in the SSS. 

3.5.Project Controls 

3.5.1. Project Status Reports (PSR) 

3.5.1.1. The Contractor shall provide, no later than the third business day of each month, a 

Project Status Report (PSR) 

3.5.1.2. The PSR shall summarise activities, including: 

3.5.1.2.1. A summary of contract activities during the preceding month; including the status 

of current and pending activities; 

3.5.1.2.2. Progress of work and schedule status, highlighting any changes since the 

preceding report; 

3.5.1.2.3. Configuration Status Accounting (CSA) report, addressing all products in the 

Project Breakdown Structure; 



19/104



CO-13355-OPL 


3.5.1.2.4. Description of any identified issues and high risk areas with proposed solutions 

and corrective actions; 

3.5.1.2.5. Test(s) conducted and results; 

3.5.1.2.6. Provisional financial status and predicted expenditures; 

3.5.1.2.7. Changes in key Contractor personnel; 

3.5.1.2.8. Summary of Change Requests requested or approve; 

3.5.1.2.9. Plans for activities during the following reporting period; 

3.5.1.2.10. Risk Log. 

3.5.1.3. The PSR, being a monthly document, shall be subject to the following specific 

review process: 

3.5.1.3.1. The Purchaser shall issue comments no later than one (1) week after receipt of the 

document; 

3.5.1.3.2. The Contractor shall issue answers to those comments within one (1) week after 

their receipt. No comment received within that timeframe means that the 

Contractor agrees to the comments issued by the Purchaser. 



20/104



CO-13355-OPL 


3.5.2. Project Meetings 

3.5.2.1. General 

3.5.2.1.1. Except as otherwise stated in the Contract, the following provisions shall apply to 

all meetings to be held under the Contract. 

3.5.2.1.2. The Contractor shall take meeting minutes, submit them in draft version to the 

Purchaser for approval within three (3) working days of the meeting, post the final 

version of them on the Project portal within three (3) working days of receipt of 

Purchaser approval, and notify the Purchaser by email. 

3.5.2.1.3. The participants shall not regard these minutes as a mechanism to change the 

terms, conditions or specifications of the Contract, or as a vehicle to alter the 

design or configuration of equipment or systems. Any such changes shall only be 

made by agreement, amendment or by authorised mechanisms, as set forth in the 

Contract. 

3.5.2.1.4. Any documentation, even in draft format, that may be useful to the Purchaser in 

preparing for meetings and ensuring efficient discussions during the meetings shall 

be provided to the Purchaser no later than ten (10) working days before the 

meeting. 

3.5.2.2. Design Review Meetings 

3.5.2.2.1. The Contractor shall host the Design Reviews. 

3.5.2.2.2. In addition to the scope and requirements for Design Reviews as described in 

SECTION 4: related to contract line number (CLIN) 1.4 of the schedule of 

supplies and services the Contractor shall provide the following, if applicable, at 

all Design Reviews: 

3.5.2.2.2.1 Changes to the PMS; 

3.5.2.2.2.2 Risk assessment of proposed changes, and an update of the Risk Log and Issue 

Logs. 

3.5.2.3. Project Review Meetings 

3.5.2.3.1. The Contractor shall coordinate and hold Project Review Meetings (PRM) with 

the Purchaser. 

3.5.2.3.2. The PRM shall be held at least once a month, throughout the Contract period of 

performance. 

3.5.2.3.3. One (1) week before each PRM, the Contractor shall provide a Project Status 

Report (PSR), in accordance with paragraph 3.5.1. 



21/104



3.5.2.3.4. Problems shall be identified by the Contractor PM and discussed with the 

Purchaser PM promptly; not held until the next PRM. 

CO-13355-OPL 


3.5.2.3.5. The PRM shall be held, at the Purchaser’s discretion, either in Purchaser’s 

premises or via teleconference and, when possible, be scheduled with other project 

meetings. 

3.5.2.4. Other Meetings 

3.5.2.4.1. The Purchaser shall host all other meetings unless there is a specifically agreed 

need to review material, witness technical demonstrations, or perform any other 

activity outside of the Purchaser’s premises, as part of the meeting. 

3.5.2.4.2. The Contractor shall identify to the Purchaser’s PM any other meetings with 

NATO personnel required to support this Contract. 

3.5.2.4.3. Upon approval by the Purchaser’s PM, the Contractor shall schedule, organise, and 

conduct such meetings. 

3.6.Risk Management 

3.6.1. The Contractor shall establish and maintain an overall Risk Management process 

for the project following a formal project management methodology. The 

preferred methodology is Projects in Controlled Environments 2 nd Revision 

(PRINCE2). 

3.6.2. This Risk Management process shall identify all risks (management, technical, 

schedule, and cost risks), evaluate each risk, and select a proposed response for 

each risk. 

3.6.3. Evaluating each risk shall result in the risk being rated as High, Medium, or Low, 

based on its probability and impact. 

3.6.4. For each risk, the proposed response shall be selected from the following list: 

3.6.4.1. Prevention: Terminate the risk - by doing things differently and thus removing the 

risk, where it is feasible to do so. Countermeasures are put in place that either stop 

the threat or problem from occurring or prevent it from having any impact on the 

project or business; 

3.6.4.2. Reduction: Treat the risk - take action to control it in some way where the action 

either reduce the likelihood of the risk developing or limit the impact on the 

project to acceptable levels; 

3.6.4.3. Acceptance: Tolerate the risk – e.g. if nothing can be done at a reasonable cost to 

mitigate it or the likelihood and impact of the risk occurring are at an acceptable 

level; 



22/104



CO-13355-OPL 


3.6.4.4. Contingency: plan and organise actions to come into force as and when the risk 

occurs; 

3.6.4.5. Transference: Pass the management of the risk to a third party (e.g. insurance 

policy or penalty clause), such that the impact of the risk is no longer an issue for 

the health of the project; 

3.6.4.6. The Risk Management data shall be presented in a Risk Log. 

3.6.4.7. The Risk Log shall be a table listing the risks, and indicating for each one the 

following information: 

3.6.4.7.1. Risk identifier: unique code to allow grouping of all information on this risk; 

3.6.4.7.2. Description: brief description of the Risk; 

3.6.4.7.3. Risk category (e.g. commercial, legal, technical); 

3.6.4.7.4. Impact: effect on the Project if this risk were to occur; 

3.6.4.7.5. Probability: estimate of the likelihood of the risk occurring; 

3.6.4.7.6. Proximity: how close in time is the risk likely to occur; 

3.6.4.7.7. Countermeasure(s): what actions have been taken/will be taken to counter this risk; 

3.6.4.7.8. Owner: the individual responsible for monitoring, controlling and reporting on the 

risk; 

3.6.4.7.9. Author: the individual that submitted the risk; 

3.6.4.7.10. Date identified: when was the risk first identified; 

3.6.4.7.11. Date of last update: when was the status of this risk last checked; 

3.6.4.7.12. Status: e.g. dead, reducing, increasing, no change. 

3.7.Issue Management 

3.7.1. An issue is anything that could have an effect on the Project, either detrimental or 

beneficial (change request, problem, error, anomaly, risk occurring, query, and/or 

change in the Project environment). 

3.7.2. The purpose of the Issue Log is to record and track all issues and their status. The 

Issue Log shall be a table and shall comprise the following information: 

3.7.2.1. Project Issue Number; 



23/104



CO-13355-OPL 


3.7.2.2. Project Issue Type (Request for change, Off-specification, general issue such as a 

question or a statement of concern); 

3.7.2.3. Author; 

3.7.2.4. Date identified; 

3.7.2.5. Date of last update; 

3.7.2.6. Description; 

3.7.2.7. Action item; 

3.7.2.8. Responsible (individual responsible for the resolution of the action item); 

3.7.2.9. Suspense date (Suspense date for the action item); 

3.7.2.10. Priority; 

3.7.2.11. Status. 

3.8.Project Portal 

3.8.1. The Purchaser will establish a NATO UNCLASSIFIED project portal for the 

Project. 

3.8.2. The Purchaser will implement an access control mechanism to restrict viewing of 

all contents of the portal to a list of users approved and administered by the 

Purchaser’s PM. 

3.8.3. The Contractor shall upload and maintain on this portal all unclassified CCTV HQ 

ISAF project documentation. 

3.8.4. The Contractor shall maintain on this portal the lists (databases) containing the 

Action Items Log, the Risk Log, and the Issue Log, associated to the Project. The 

databases shall follow the templates presented in paragraph 3.6 (Risk Log), and 

paragraph 3.7.2 (Issue Log). 

3.8.5. The portal shall allow any user to set various alerts in order to be notified (by e- 

mail) each time a specific document, a specific folder, or a specific record in a 

database, is modified. 

3.8.6. The portal shall include the Contract SOW and System Requirements 

Specification (SRS), all presentation material from all Design Reviews and other 

meetings, the draft and final (Purchaser-approved) minutes of any meetings, and 

all background, applicable, reference, and guidance documents referred to in the 

SOW and SRS. 



24/104



CO-13355-OPL 


3.8.7. The portal shall include all vendor-provided technical documentation pertaining to 

any COTS components integrated in the CCTV HQ ISAF. 

3.8.8. The portal shall include other documents, as directed by the Contractor’s PM or 

the Purchaser’s PM. 

3.8.9. The portal shall identify all relevant classified documents by title, unless a title is 

itself classified. 

3.8.10. The portal shall clearly indicate for each document whether it is part of a baseline 

or not. 

3.8.11. After the FSA, the Contractor shall sanitise and replicate this portal to a public 

web server (outside the Purchaser’s facilities). The Contractor shall then keep the 

portal up to date, enable access by the users, or the Purchaser, through the 1-year 

of warranty, and during any subsequent (optional) Support extensions. 

3.8.12. NATO RESTRICTED (NR) documentation shall not be permitted on the portal. 

Instead, transfers of such documentation will rely on optical storage support, 

postal mail, or on the use of dedicated NR laptops that can be leased from the 

purchaser. 

3.8.13. No NATO SECRET or ISAF SECRET documentation relevant to the design, 

configuration, system documentation and training, is anticipated to be required 

during the execution of this Contract. 



25/104



SECTION 4: SYSTEM DESIGN, ENGINEERING AND 

IMPLEMENTATION 

4.1.General 

CO-13355-OPL 


4.1.1. This section outlines the System Design, Engineering and Implementation Area of 

the CCTV HQ ISAF Contract. 

4.1.2. The CCTV HQ ISAF shall largely comprise off-the-shelf products, whether 

commercially available or developed for other customers. However, there may be 

some modifications required to adapt these products to meet the CCTV HQ ISAF 

requirements. 

4.1.3. The CCTV HQ ISAF shall be a standalone system and is not expected to integrate 

with any existing NATO systems. Future modifications or changes in the products 

and technologies employed in the CCTV HQ ISAF shall be anticipated and 

provided for through sound systems engineering practices. For these reasons, the 

Contractor shall be responsible for the overall design, development, integration, 

and system engineering of the CCTV HQ ISAF throughout the contract period of 

performance. 

4.1.4. The contractor shall fully complete the technical proposal cross reference matrix 

table per Book I of the Bidding Instruction. 

4.2.Environmental and Climatic Conditions 

4.2.1. In STANAG 2895 ‘Environmental conditions’, Kabul environmental conditions 

are described as: A3 (intermediate hot) in summer period and C0 (mild cold) in 

winter period. The system shall be fully operational under these conditions. 

4.2.2. All systems shall have a demonstrated capacity to operate under the following 

conditions without any signs of degradation as well as achieve the conditions for 

storage, transit and handling 

4.2.2.1. High Temperature: + 39° C for operation; + 58° C for transport, storage and 

handling. 

4.2.2.2. Low Temperature: - 19° C for operation; - 21° C for transport, storage and 

handling 

4.2.2.3. Temperature shock: 0.12 ° C/min for natural conditions during operation, 

transport, storage and handling. When moved from open environment into an 

acclimatised area, the equipment in the applicable storage/ transport packaging 

shall withstand the maximum expected temperature variation of 63 ° C. 

4.2.2.4. Solar radiation: 1120 W/m² for operation, transport, storage, handling and depot. 



26/104





27/104 

CO-13355-OPL 


4.2.2.5. Sun protection devices for the cameras shall be provided in support of the 

fulfilment of the STANAG 2895 related requirements (mainly A3 compliance). 

4.2.2.6. Humidity: 5 to 100% (saturation) for operation, transport and handling with the 

applicable change of temperature. 

4.2.2.7. Rain and water tightness (only applicable for outside components): The 

equipment shall have a high degree of water tightness when exposed to extended 

periods of rain and shall pass the following criteria: 

4.2.2.7.1. The wind velocity shall be applied during the 2 hour steady-state rain fall 

testing. 

4.2.2.7.2. Droplet sizes should not be smaller than approximately 0.5 mm. 

4.2.2.7.3. Extreme: Duration of 5 min at rate 14 mm/min. 

4.2.2.7.4. High: duration of 25 min at rate 8 mm/min 

4.2.2.7.5. Steady state: duration of 120 min at rate 1.7 mm/ min and wind velocity of 

18m/sec. 

4.2.2.8. Snow load: 

4.2.2.8.1. Large size equipment: 100 kg/m2 during operation, transport, storage and 

handling and depot. 

4.2.2.8.2. Smaller transportable equipment: 50 kg/m2 during operation, transport, storage 

and handling and depot. 

4.2.2.9. Ice with a specific gravity of 0.85: 

4.2.2.9.1. 13 mm for operation, transportation, storage and handling. 

4.2.2.10. Hail 

4.2.2.10.1. Hailstones of up to 25 mm diameter, 0.9 g/m3 density and 58 m/s terminal 

velocity during operation, transport, storage and handling and depot. 

4.2.2.11. Wind 

4.2.2.11.1. Norm: 22 m/s average and 39.6 m/s gustiness during operation, transport, 

storage and handling. 

4.2.2.12. Dust/sand particle size and concentration for external environment: 

4.2.2.12.1. Up to 2.0 g/m3 of 150µm particles for operation, transport, storage and 

handling. Sedimentation rate as high as 2.0 g/m2/day



CO-13355-OPL 


4.2.2.12.2. Up to 1.0 g/m3 of 150µm particles for depot. Sedimentation rate as high as 2.0 

g/m2/day. 

4.2.2.12.3. Note: Average particle hardness of 7 in the Mohs scale, occasionally reaching 

9 on that scale. 

4.2.2.13. Max/min atmospheric pressure 

4.2.2.13.1. Norm: 1,087 to 503 mbar, for all conditions (operation, transport, storagehandling 

and depot. 

4.2.2.14. Acid atmosphere (Method 518) [MIL STD 810]. 

4.2.2.14.1. The CCTV system outside units shall withstand, in the pertaining operating 

configuration (i.e. when properly mounted in the intended assembly), 

occasional exposure to the acid rainfall conditions existing in heavily 

industrialized areas or in the proximity of fuel burning machinery or vehicles 

exhaust systems. 

4.2.2.15. Contamination by fluids 

4.2.2.15.1. The equipment shall withstand occasional contamination by exposure to the 

contaminant fluids listed in table I, method 504 in [MILSTD 810, 2000]. 

4.2.2.16. IP Rating 

4.2.2.16.1. IP65 (Protection against all dust penetration and against water jets from any 

direction) for outdoor enclosures, cables and connectors for operation. 

4.2.2.16.2. IP55 (Protection against internal dust accumulation and against splashing 

water from any direction) when in operation. 

4.2.2.17. Chemical/Fungus/ Salt fog (Corrosion) (Method 504/508/509) [MIL STD 810]. 

4.2.2.18. UV Resistance (Method 505) [MIL STD 810]. 

4.3.System Design Documentation Package 

4.3.1. The Contractor shall establish and maintain the CCTV HQ ISAF Design 

Documentation Package, comprising: 

4.3.1.1. System Design Specification (SDS), as per 4.3.3 

4.3.1.2. Requirements Traceability Matrix (RTM), as per 8.4 

4.3.2. and, if and where applicable: 



28/104



CO-13355-OPL 


4.3.2.1. Change Requests Document (CRD) 

4.3.2.2. Off-specifications Document (OSD) 

4.3.3. The SDS shall adhere to the requirements listed in the System Requirements 

Specification SRS of Annex I, and include the following information: 

4.3.3.1. Functional breakdown of the CCTV HQ ISAF, based on the Functional 

Requirements listed in the SRS; 

4.3.3.2. Physical breakdown of the CCTV HQ ISAF into hardware, software and firmware 

Configuration Items (CI), following the Technical Requirements listed in the SRS. 

The breakdown shall include the number of licenses for each software CI, with 

traceability to the functional breakdown above; 

4.3.3.3. Identification of COTS versus any developmental items; 

4.3.3.4. Configuration Status Accounting (CSA) Reports, addressing all system CIs; 

4.3.3.5. Description of the interworking of all components to meet the system level 

requirements (physical interfaces between components, existing network 

infrastructure); 

4.3.3.6. Deployment and Operation principles of the CCTV HQ ISAF: overview of the 

new system and how the operators will make use of the provided functionality, and 

how administrators will be able to monitor and control the system. 

4.3.3.7. The Contractor shall provide a list of major components and civil works activities 

required to implement the technical solution, in order for the Purchaser to 

determine that the equipment and civil work activities are fit for purpose. 

4.4.Site Survey 

4.5. A site survey shall be performed within 4 weeks of the effective date of contract 

(EDC) to confirm assumptions and mitigate risk. 

4.5.1. The Contractor shall provide the Purchaser PM with an electronic copy of the Site 

Survey Report (SSR) within One (1) week of the completion of the survey. 

4.5.2. The SSR shall contain: 

4.5.2.1. Confirmation of the physical locations of the masts and any cable runs. 

4.5.2.2. Copies of signed agreements with local Site Authorities 

 

 

Approval from BSG Commander 

Approval from ISAF J6 



29/104





30/104 

CO-13355-OPL 


4.5.2.3. An assessment of the in-building requirements with proposed solutions, including 

relevant diagrams and analysis 

4.5.2.4. Optimized mast placement and camera type configuration. The Contractor shall 

determine the appropriate number of retractable masts, type of retractable mast 

systems, and camera types to achieve the required capability. 

4.5.2.5. The Contractor shall develop a stand alone CCTV architecture that can be easily 

expanded to support a minimum of twice (2x) the coverage capability without the 

exchange of server, router and switches, storage, and/or command and control 

software. Take note that there are 2 types of switches authorized for use in ISAF 

– CISCO and 3COM. 

4.5.2.6. The Contractor shall confirm the appropriate amount of civil works required and 

utilize the nearest cabling manhole or hand hole (smaller than a man hole) to 

patch into the existing infrastructure. 

4.5.2.7. The Contractor shall include a map of the grounds within the site survey report 

detailing the locations of required civil works, distance to both electrical power 

and communications man hole and hand hole locations, patch panel availability 

for specific ports, and recommended camera capability and placement. 

4.5.2.8. The Contractor shall specify the capabilities of the camera types that meet the 

requirements. Types I, II, and III are specified in this document. However, other 

camera types defined and if approved by NC3A, may be used to develop an 

inherently secure solution to meet requirement. 

4.5.2.9. The contractor shall validate and optimize the CCTV design to include network 

architecture that ensures a cost effective, efficient, resilient design that meets the 

requirements. The contractor shall submit the validated design as part of the 

preliminary design documentation. 

4.5.2.10. The Contractor shall identify all enablers and critical path to facilitate the project. 

4.6.System Design Reviews 

4.6.1. The Contractor shall deliver the Preliminary Design Documentation to the 

Purchaser within six (6) weeks of the Effective Date of Contract (EDC). The 

Contractor shall host and conduct a Preliminary Design Review (PDR) with the 

purchaser within eight (8) weeks of the EDC. 

4.6.1.1. The Contractor shall specify how redundancy is built into their proposed solution 

that shall notify the BDOC and affected ECP of camera outage while maintaining 

limited surveillance capability. Limited is defined as degraded capability that will 

continue to provide camera coverage until camera is repaired or replaced. 

4.6.1.2. The Contractor shall specify how the system can be connected to a network 

without major upgrade to proposed hardware and software. NOTE: Although the



CO-13355-OPL 


system is designed as a stand alone network, it shall possess the capability within 

the technical control centre to interface with a standard IPv6 network to further 

centralize surveillance capability for future evolution of the CCTV network such 

as interconnection to archive data to an alternate location. 

4.6.2. During the Design Review, the Contractor shall cover the following topics: 

4.6.2.1. System Design, as presented in the System Design Documentation (SDD) 

package, including any change request or off-specification; 

4.6.2.2. Breakdown of the design into lowest-level CI; 

4.6.2.3. Recommended spare parts list (RSPL) and justification, provided as an availability 

analysis and assess the design in relation to RMA design as stated in section 5.3.2; 

4.6.2.4. List of off-the-shelf products to be used in the system: the Contractor shall identify 

the intended product and version, and note if any modifications, adaptations, or 

additional elements are required to meet the requirements set forth by the SRS. For 

any elements that require development, the Contractor shall describe the design, 

development, unit testing, and integration approach; 

4.6.2.5. Steps to mitigate any risks identified in the Risk Log; 

4.6.2.6. Draft Test Plan for FAT, PSA and Operational Test & Evaluation (OT&E). 

4.6.3. The duration of the review period of the CCTV HQ ISAF Design Documentation 

Package by the Purchaser shall be one (1) week, i.e. shall be finished within five 

(5) weeks of the EDC. 

4.6.4. A Critical Design Review (CDR) shall be conducted, if the changes requested after 

the first meeting require the Contractor to re-engineer the solution in any way at 

EDC +8 weeks. 

4.6.5. Purchaser review and acceptance of the SDD package shall not imply Purchaser 

acceptance of the CCTV HQ ISAF design. In particular: 

4.6.6. It remains the sole responsibility of the Contractor to prove the design through the 

regime of testing set forth in the Contract. 

4.6.7. It will be the sole responsibility of the Contractor in the event that the system 

proves deficient in meeting the Contractual requirements. 

4.6.8. As part of the Configuration Management (CM) activities, and like any other 

management product or specialist product, the Contractor shall update the SDD, in 

order to reflect changes, if any, at least at each of the following major milestones: 

4.6.8.1. Second Design Review, if required; 



31/104



CO-13355-OPL 


4.6.8.2. Functional Testing in theatre; 

4.6.8.3. Provisional System Acceptance (PSA); 

4.6.8.4. Final System Acceptance (FSA) of the CCTV HQ ISAF in theatre. 

4.7.System Implementation 

4.7.1. General 

4.7.1.1. The implementation shall span over the following three stages: 

4.7.1.2. Stage 1 

4.7.1.2.1. Site Survey; 

4.7.1.2.2. Factory-based integration and testing (FAT), including testing of the upgrade 

components for the CCTV HQ ISAF; 

4.7.1.2.3. Preparation (packing, including the System Documentation), in preparation for the 

shipment to theatre; 

4.7.1.2.4. Shipment to B-CLD. 

4.7.1.3. Stage 2 

4.7.1.3.1. External/Internal installation of the CCTV HQ ISAF; 

4.7.1.3.2. Site and System Activation Testing (SSAT); 

4.7.1.3.3. OT&E of the CCTV HQ ISAF, after installation; 

4.7.1.3.4. Train-the-user training, in HQ ISAF, attended by ISAF J6, NAMSA, HQ ISAF FP 

Staff and HQ ISAF BSG staff 

4.7.1.3.5. PSA in HQ ISAF; 

4.7.1.3.6. Rectification of deficiencies encountered SSAT and OT&E; 

4.7.1.3.7. Final System Acceptance, FSA (in Brussels); 

4.7.1.4. Stage 3 

. 

4.7.1.4.1. 1-year warranty period (covered by the main Contract); 

4.7.1.4.2. 1-year Contractor Support (under warranty conditions); 



32/104



4.7.1.4.3. Additional (yearly) Support, as an option to the main Contract. 

4.7.2. System Implementation Plan (SIP) 

CO-13355-OPL 


4.7.2.1. The implementation of the above three stages shall be outlined in the System 

Implementation Plan (SIP), which shall be part of the PIP. 

4.7.2.2. The SIP shall detail the following information: 

4.7.2.2.1. the Contractor's approach to all system implementation tasks, following the above 

three stages, and describing the activities at the various facilities involved (factory, 

and HQ ISAF); 

4.7.2.2.2. the overall schedule for the implementation activities (subset of the Project Master 

Schedule, PMS); 

4.7.2.2.3. the Contractor organisation and key personnel involved in the system 

implementation in theatre. 

4.7.2.3. System Implementation Facilities: 

4.7.2.4. The Purchaser will provide the Contractor with access to the facilities necessary to 

test and demonstrate the CCTV HQ ISAF at HQ ISAF: 

4.7.2.5. The Contractor shall bear the responsibility for the system's ownership (excluding 

PFE), operation, support, and performance verification, until the Technical 

Transfer to HQ ISAF BSG. 

4.7.2.6. The Purchaser reserves the right to suspend the Contractor's installation or testing 

work for up to five working days to avoid interfering with or disrupting a critical 

operational event. Only if this suspension exceeds five working days, an 

adjustment of the price can be submitted for consideration by the Purchaser, in 

connection with rescheduling efforts required on the Contractor’s side. 

4.7.2.7. During the implementation activities in theatre, should the Contractor receive any 

indication of a possible requirement for a suspension, this shall be made known 

immediately to the Purchaser. 



33/104



CO-13355-OPL 


SECTION 5: 

INTEGRATED LOGISTICS SUPPORT (ILS) 

5.1.General 

5.1.1. This section outlines the supportability requirements of the project. It addresses 

various Integrated Logistic Support (ILS) elements such as: maintenance, support 

services, spare parts provisioning, transportation, warranty and training. 

5.1.2. The NC3A/ILS PoC for all requests related to ILS is: 

NATO C3 Agency 

Attn.: Mr. Ron Spijkerman 

ILS Officer at NC3A/DOP/ILS 

Ave. du Bourget 141 

B-1110 Brussels 

Belgium 

Tel: +32 (0)2 707 8578 

Fax: +32 (0)2 707 8770 

E-mail: ron.spijkerman@nc3a.nato.int 

5.1.3. The NC3A/ILS PoC for all requests related specifically to supply support, 

management and control of logistics movements, and warranty: 

NATO C3 Agency 

Attn.: Mr. Jackie Robinson 

ILS Assistant at NC3A/DOP/ILS 

Ave. du Bourget 141 

B-1110 Brussels 

Belgium 

Tel: +32 (0)2 707 8498 

Fax: +32 (0)2 707 8770 

E-mail: jackie.robinson@nc3a.nato.int 

5.2.Support planning 

5.2.1. The Contractor shall develop and maintain the Integrated Logistics Support Plan 

(ILSP) that encapsulates all ILS Elements as defined below, covering the period 

starting from deployment to End of Life. 

5.2.2. The ILSP shall be structured as follows, but is not limited to: 

5.2.2.1. Introduction – The introduction shall cover scope and purpose of the ILSP, include 

appropriate references and definitions and include a detailed description of the 

products furnished under this Contract. 



34/104





35/104 

CO-13355-OPL 


5.2.2.2. Maintenance Concept - The Contractor shall describe the Maintenance Concept 

that defines the maintenance environment, constraints, locations, procedures, 

artefacts, organisation and personnel skills to maintain the products furnished 

under this Contract. The Maintenance Concept shall define the 3rd and 4th level 

maintenance tasks in accordance with the Maintenance and Support Concept 

section below. 

5.2.2.3. Support Concept - The Contractor shall describe the Support Concept showing 

how 1st, 2nd and 3rd level support services will be implemented and performed in 

accordance with the Maintenance and Support Concept section below. 

5.2.2.4. Supply Concept – The Contractor shall describe the Supply Concept that defines 

the procedures for the provisioning, procurement, and acquiring of spare/repair 

parts, inventories, and consumable material for the support of the products 

furnished under this Contract. 

5.2.2.5. Training - The Contractor shall describe how training is developed and performed 

during the Contract period. 

5.2.2.6. Configuration Management – The Contractor shall describe how configuration 

management is performed during the Contract period, and especially how the 

Contractor will maintain a Configuration Management Data Base (CMDB). 

5.3.Maintenance and Support 

5.3.1. Maintenance and Support Concept 

5.3.1.1. Level 1 maintenance tasks shall be defined and designed for on-site CCTV HQ 

ISAF users and operators and shall include, but are not limited to: day-to-day 

“housekeeping” tasks, visual inspections, verification of function and performance 

of the provided capabilities, change of configuration settings for adaptation to the 

operational environment or use, routine system operation, routine system 

administration, local user support, system monitoring, and system recovery. 

5.3.1.2. Level 1 support services entail, but are not limited to implementing the incident 

management process in accordance with the ISO/IEC 20000 and ITILv3 

framework or equivalent. As part of the incident management process, a service 

desk function shall be implemented. 

5.3.1.3. First level maintenance and support of the CCTV HQ ISAF will be provided by 

the user after training from the Contractor. 

5.3.1.4. Level 2 maintenance tasks shall be defined and designed for non-specialized 

military maintenance personnel, on-site or remote, and shall include, but are not 

limited to: detailed inspections, limited calibrations, replacement of items without 

specialized equipment or skillset, and minor equipment repairs and modifications, 

centralised system operation, centralised system administration, fault isolation,



CO-13355-OPL 


system-wide performance monitoring and reporting, and in-depth technical 

assistance to level 1 support staff.. 

5.3.1.5. Level 2 support services entail, but are not limited to implementing the problem 

management process in accordance with the ISO/IEC 20000 and ITILv3 

framework or equivalent. As part of problem management the Contractor shall 

perform the following tasks: (re-) evaluation of incident category, criticality and 

priority; identification of the root cause of the issue (e.g. by issue replication 

testing); identification of workarounds; identification and initial planning of 

possible short, medium and long-term solutions (e.g. workarounds, patches, or 

new releases); create change requests incl. schedule of implementation, and 

synchronization with the maintenance and warranty process; and monitor and 

control the approved change request during implementation, delivery of problem 

analysis reports and overall support reports when required. 

5.3.1.6. Second level maintenance and support of the CCTV HQ ISAF will be provided by 

the Base Support Group (BSG) technical staff user after training from the 

Contractor. 

5.3.1.7. Level 3 maintenance tasks shall be defined and designed for specialized military 

maintenance personnel, on-site or remote, and shall include, but are not limited to: 

problem and modification analysis, complex repairs and/or replacements, detailed 

calibrations, supply support, overhaul and rebuild, implementation of major and/or 

critical changes, restoration (e.g. emergency maintenance) that requires specialized 

maintenance personnel and equipment, monitoring and coordination of 

transportation of faulty equipment out of theatre and replacement equipment back 

into theatre. 

5.3.1.8. Level 3 support services implement the deployment and release management 

process in accordance with the ISO/IEC 20000 and ITILv3 framework or 

equivalent. In this process, the Contractor shall develop the solution (e.g. fix, 

repair, replace, patch, or release), test the solution and deliver and deploy the 

solution. Third level of support services shall be established to maintain the core 

expertise for all the CCTV HQ ISAF elements, including configuration 

management of the CCTV HQ ISAF components, administration of the CCTV HQ 

ISAF, performance assessment, off-specification reporting, and maintenance 

engineering. It includes the maintenance and administration of the CCTV HQ 

ISAF Reference System and its use in analysing operational problems and 

validating changes to the baseline as well as the link between the operational and 

factory support staff. 

5.3.1.9. The Purchaser’s existing trouble-ticketing system and existing incident 

management and problem management processes shall be used for opening, 

modifying, tracking, and closing Trouble Tickets, and logging of all requests 

concerning the products furnished under this Contract. 



36/104





37/104 

CO-13355-OPL 


5.3.1.10. As part of the support services provision, the Contractor shall create and 

maintain descriptions of all solutions (Quick solution, Work around, Patch, 

Baseline Release) to known issues in a COTS software database (“Known 

Error Database”). The Known Error Database shall link issues to solutions and 

corresponding documentation and expert POC. 

5.3.1.11. Third level maintenance and support of the CCTV HQ ISAF will be provided by 

the Contractor under a one (1) year CLS package as described below. 

5.3.1.12. Level 4 maintenance tasks shall include, but are not limited to: repair of faulty 

LRU(s) of the CCTV HQ ISAF beyond the capability of level 3 (usually under 

warranty), provisioning of replacement parts (usually under warranty), 

complicated factory adjustments, and provision of maintenance releases at the 

Contractor’s, Vendor’s or Manufacturer’s factory. 

5.3.1.13. Fourth level maintenance and support of the CCTV HQ ISAF will be provided by 

the Contractor, supported by the pertinent OEM-vendors, under a one (1) year 

CLS package as described below. 

5.3.1.14. The maintenance and support concept applies to both hardware and software. 

5.3.1.15. The maintenance and support concept shall be designed, and subsequently 

described in the ILSP, in such a way that the reliability, maintainability and 

availability (RMA) requirements specified below are achievable. 

5.3.2. Reliability, Maintainability and Availability (RMA) requirements 

5.3.2.1. Systems and equipment to be supplied under this Contract shall meet specified 

criteria for availability, reliability, and maintainability. 

5.3.2.2. Reliability, when expressed as Mean Time Between Critical Failures (MTBCF), 

shall be greater than four thousand (4,400) hours. In order to guarantee this 

reliability, the Contractor shall include sufficient redundancy in the design of the 

CCTV system. A critical failure is defined as any event that impairs the total 

camera coverage of the ISAF HQ CCTV system as a whole. 

5.3.2.3. Maintainability, when expressed as Mean Time To Replace/Repair (MTTR), shall 

be less than one (1) hour, with 95% of repairs not exceeding thirty (30) minutes. 

5.3.2.4. The Mean Time Between Corrective Maintenance Actions (MTBCMA) shall be 

greater than five hundred (500) hours. 

5.3.2.5. Operators shall have easy access to any system component in order to facilitate 

visual inspection, and so that any LRU replacement can be achieved within the 

specified time. 

5.3.2.6. Operational Availability (A 0 ), with respect to full camera coverage, shall be 

greater than 99.9%. Operational Availability (A 0 ) is defined as MTBF / (MTBF +



CO-13355-OPL 


MTTR + MLDT) with MLDT and the conditions affecting A 0 contributable to the 

Contractor to be agreed upon. 

5.3.2.7. The Contractor shall organise a Provisioning Conference concurrent with the 

System Design Review meeting. The purpose of the conference is for the 

Purchaser to ascertain whether the Contractor’s designed maintenance and support 

concept (as part of the ILSP) and the Contractor’s recommended spare parts list 

(RSPL) is sufficient to meet the reliability, maintainability and availability 

requirements in this section of the SOW. The Contractor shall make available to 

the Purchaser attendees of the conference all data and documentation relevant to 

ascertain the validity of this purpose statement. 

5.3.3. Contractor Logistics Support (CLS) 

5.3.3.1. From Provisional Site Acceptance (PSA) of each Site to the Final System 

Acceptance (FSA) and during the warranty period from FSA to FSA + one (1) 

year, the Contractor shall provide CLS-services under the Contract, which shall 

cover: 

5.3.3.1.1. 3rd and 4th level maintenance tasks in accordance with the maintenance and 

support concept above. By default, the Contractor furnished 3rd level 

maintenance shall be provided at CLD Brunssum, The Netherlands. The 

Contractor furnished 4th level maintenance shall be provided off-site at 

Contractors’ or product vendors’ premises; 

5.3.3.1.2. 3rd level support services in accordance with the maintenance and support 

concept above. The Contractor furnished 3rd level support services shall be 

provided offsite at the Contractor’s premises; 

5.3.3.1.3. hardware support as defined below; 

5.3.3.1.4. software support and upgrades as defined below; 

5.3.3.1.5. technical assistance as defined below; 

5.3.3.1.6. maintenance of all of the Configuration Management documentation, including 

a Configuration Management Data Base (CMDB) and a Known Error 

Database (KEDB); 

5.3.3.1.7. revision of documentation covering any changes to the site and system level 

operation and maintenance (O&M) documentation and to the As-Built 

documentation. 

5.3.3.2. The CLS services shall be dimensioned to take full advantage of: 

5.3.3.2.1. the on-site NATO technicians, who will carry out 1st and 2nd levels 

maintenance and support services; 



38/104



CO-13355-OPL 


5.3.3.2.2. a limited on-site spares holding, based on the outcome of the provisioning 

conference; 

5.3.3.3. As an Option to this Contract, the contractor may be obligated to enter into a 

Contractor Logistics Support agreement with the Purchaser or his representative 

after the 1-year warranty period. The following considerations apply: 

5.3.3.3.1. The CLS contract may be renewed inline with the options detailed in the 

Schedule of Supplies and Services (SSS). 

5.3.3.3.2. This support agreement is a full Contractor Logistics Support (CLS) Contract 

provided under a Firm Fixed Price. 

5.3.3.3.3. Prices shall remain valid during the period of validity. 

5.3.3.3.4. The price revisions are to be limited to the amounts reflected for each period in 

a governmentally approved inflationary index of the producing country. 

5.3.3.3.5. If the Option of CLS is exercised, the Contractor shall be responsible for the 

CLS for all deliverables furnished under this Contract and shall guarantee the 

provisions of such equipment replacement/repair services including Technical 

Assistance. 

5.3.3.4. CLS hardware support 

5.3.3.4.1. During the CLS-period (and any subsequent period of CLS, if exercised), the 

Contractor shall establish a Logistics Support Programme and be responsible 

for ensuring adequate provision of direct exchange Line Replacement Units 

(LRUs), in terms of both range and quantity, to maintain the reliability and 

availability requirements specified in this SOW. 

5.3.3.4.2. To this end the Contractor shall provide sufficient spares at the site and shall 

ensure a comprehensive range is available to replace any defective LRUs 

returned from the site. 

5.3.3.4.3. The Contractor shall be responsible for the provision of any alternative or 

superseding items should the original part be no longer available ensuring 

form, fit, and functional requirements. 

5.3.3.4.4. The Contractor shall be responsible to provide upon request the necessary 

failure and price data to permit Purchaser selection and separate procurement 

of spare parts to cover any requirements arising during tension, crisis, or other 

emergency. 

5.3.3.4.5. The Contractor shall repair or replace any item returned as unserviceable in 

accordance with current approved specifications and QA requirements. 



39/104





40/104 

CO-13355-OPL 


5.3.3.4.6. The Contractor is to maintain complete records of spares consumption 

including those spares used in the repair of returned LRUs. Such records shall 

be made available to the Purchaser on request. 

5.3.3.4.7. It is at the Contractor’s discretion to introduce any system updates, or parts 

thereof, but always subject to prior approval by the Purchaser 

5.3.3.5. CLS software support and upgrades 

5.3.3.5.1. During the CLS-period, the Contractor shall be responsible for all software 

support including software and firmware upgrades as part of the overall system 

support to ensure that the specified reliability and availability requirements are 

met. 

5.3.3.5.2. The Contractor shall be responsible for correcting in a timely manner all 

software defects identified by the Purchaser which have either a direct or 

potential impact on the operation of the system and of the availability 

requirements. 

5.3.3.5.3. It should be noted that the Purchaser, prior to operational use, normally tests 

the introduction of new software versions. 

5.3.3.5.4. The availability of software modifications and upgrades shall be made known 

to the Purchaser and, if proposed for introduction by the Contractor for 

whatever reason, including any corrective action for an identified fault, shall 

always be subject to Purchaser approval. 

5.3.3.5.5. The Contractor shall supply the associated release notes when supplying new 

hardware, software, and upgrades. 

5.3.3.6. CLS technical assistance 

5.3.3.6.1. During the CLS-period, the contractor shall return to HQ ISAF at a minimum 

of two (2) times per year to support the system to ensure optimal performance 

and operation. During the visits the purchaser may request as an option for the 

contractor to provide additional training to level 1 and 2 technicians and to the 

watch keepers for the proper maintenance (technicians) and operations (watch 

keepers) of the system. 

5.3.3.6.2. During the CLS-period, the Contractor shall be responsible for maintaining a 

technical support capability during normal working hours for support 

accessible via telephone to the NATO Network Control Centre (NNCC) and e- 

mail or Web services. Additionally, higher level support capabilities with 

direct access to the Contractor’s engineering resources shall be available 

during normal working hours for timely resolution of system problems be they 

hardware or software related. In the context of Technical Assistance, the 

“normal working day” is defined as any time from Monday to Friday between 

08:00 hours and 18:00 hours Belgium time, excluding NATO holidays.





41/104 

CO-13355-OPL 


5.3.3.6.3. All problems reported including their agreed corrective action shall be 

maintained in a log which shall be made available on request to the Purchaser. 

5.4.Supply support 

5.4.1. System Inventory/ Material Data Sheet (MDS) 

5.4.1.1. The Contractor shall provide the NC3A/ILS PoC with a Material Data Sheet 

(MDS), in electronic format, ten (10) working days before the first delivery. The 

MDS, as a minimum, shall include the data elements cited with an “M” mandatory 

below, if applicable. The MDS, amended as necessary, shall be used by the 

Purchaser for acceptance purposes and to create data element entries in the NATO 

Accounting system, ahead of delivery of the Final System Inventory. 

5.4.1.2. The Contractor shall provide the NC3A/ILS PoC with a Final System Inventory, 

which shall be based on and be consistent with the MDS, ten (10) working days 

before PSA. The Final System Inventory shall include all data elements listed 

below. The Final System Inventory shall be provided as a hard copy as well as on 

electronic media in Microsoft Excel or Access database format. . Details on the 

exact format of the various data elements to be adopted will be communicated 

following contract award. An inventory template together with a full content 

description for each column (electronic format) shall be provided to the Contractor 

at the request of the Contractor after contract award. For information purposes, the 

minimum inventory/equipment data elements required are as follows: 

a. Contract Customer Line Item Number (CLIN); 

b. NATO Stock Number (NSN - if available); 

c. Nomenclature – M; 

d. Expendable/Repair code XB/ND – M; 

e. True Manufacturer Part Number – M; 

f. True Manufacturer Cage Code – M (or complete name and address); 

g. Vendor/Contractor Cage Number (or complete name and address) – M; 

h. Vendor/Contractor Part Number – M; 

i. Quantity ordered-M; 

j. Order Unit – M; 

k. Serialized Item Tag – M; 

l. Serial number – M; 

m. Serial number software revision level; 

n. Serial number hardware revision level; 

o. Other serial number attributes; 

p. Currency – M;



CO-13355-OPL 


q. Unit Price – M; 

r. Warranty expiration date – M; 

s. Receiving NATO Depot; 

t. Extended Line Item Description; 

u. Part Number of next higher assembly; 

v. Quantity in the next higher assembly. 

5.4.2. Codification 

5.4.2.1. On the basis that an adequate manufacturer’s identification numbering system is in 

place, the NATO codification (as described in Clause 33 of the NC3O General 

Provisions) is not required. 

5.4.3. Initial Spare Parts 

5.4.3.1. The Contractor shall provide a detailed, location-specific, and priced 

Recommended Spare Parts List (RSPL) that shall reflect all individual spare part 

components for the installed equipment. 

5.4.3.2. The RSPL shall as a minimum include the following main subjects: 

a. Item sequence number; 

b. Detailed item description; 

c. True manufacturer's part number; 

d. True manufacturer's identification code (Cage Code) or name; 

e. Mean Time Between Failures (when validated data is available); 

f. Next higher assembly; 

g. Unit price. 

5.4.3.3. Spare Parts shall be provided in adequate packaging, protecting the parts during 

transportation and storage. 

5.5.Management and control of logistics movements 

5.5.1. Transportation 

5.5.1.1. The Contractor shall provide a Transportation Plan twenty (20) working days 

before the first delivery in electronic format. The Transportation Plan shall 

describe all planned (partial-) shipments, locations, point of contact(s), 

transportation stages, schedules, and alternative schedules. 

5.5.1.2. The Contractor shall use the transportation routes identified in the below figure. 



42/104



CO-13355-OPL 


Figure 1 – Overview of Transportation route 

5.5.1.3. All equipment covered under this Contract shall be transported from a NATO 

country to the NATO CIS Logistics Depot (CLD) at Brunssum, The Netherlands 

by the Contractor (Shipment #1) at the expense of the Contractor. 

5.5.1.4. All equipment covered under this Contract shall be transported from the NATO 

CIS Logistics Depot (CLD) at Brunssum, The Netherlands to Depot 26, Kabul by 

the Purchaser (Shipments #2,) at the expense of the Purchaser; 

5.5.1.5. All equipment covered under this Contract shall be transported from Depot 26, 

Kabul to the final destination at ISAF HQ, by the Contractor (Shipments #3) at the 

expense of the Contractor; The Contractor is responsible for providing all required 

equipment to support operations to include cranes, forklifts, etc. 

5.5.1.6. Warranty return of unserviceable equipment from HQ ISAF to CIS Logistics 

Depot (CLD) at Brunssum, The Netherlands, as well as transportation of repaired 

or replacement items under warranty from the CIS Logistics Depot (CLD) at 

Brunssum, The Netherlands to HQ ISAF are the responsibility of the Purchaser at 

the expense of the Purchaser. 

5.5.1.7. Warranty return of unserviceable equipment from CIS Logistics Depot (CLD) at 

Brunssum, The Netherlands to the Contractor’s facilities, as well as transportation 

of repaired or replacement items under warranty from the Contractor’s facilities to 

CIS Logistics Depot (CLD) at Brunssum, The Netherlands are the responsibility of 

the Contractor at the expense of the Contractor. 

5.5.2. Preservation and Packaging 

5.5.2.1. The Contractor shall ensure that the various supplies will be transported, 

packaged, crated, or otherwise prepared in accordance with the best commercial 

practices for the types of supplies involved, giving due consideration to shipping 

and other hazards associated with the transportation of consignments to overseas. 

5.5.2.2. A detailed description of packaging to be used shall be provided by the Purchaser 

at the request of the Contractor. 



43/104



CO-13355-OPL 


5.5.2.3. Any special packaging materials required for the shipment of items shall be 

provided by the Contractor. 

5.5.3. Package Marking 

5.5.3.1. The packages, palettes and/ or containers in which supplies are transported shall, 

in addition to normal mercantile marking, show on a separate nameplate the 

project name, contract number and shipping address. 

5.5.3.2. All hardware packaging supplied shall be marked as applicable with the true 

manufacturer's part number, serial number and revision level as identified in the 

relevant technical documentation. 

5.5.4. Packing Lists 

5.5.4.1. The Contractor shall provide the NC3A/ILS PoC with a packing list in electronic 

format fifteen (15) working days before each shipment. 

5.5.4.2. Copies of the packing lists shall also accompany each shipment. Each individual 

box from a consignment shall have one packing list in weather proof envelope 

affixed to the outside of each box that indicates exactly what is contained inside. 

One copy shall also be put inside each box. 

5.5.4.3. The Contractor shall ensure that packing lists are provided in such a way as to 

permit easy identification of the items to be delivered to destinations. 

5.5.4.4. Packing lists shall as a minimum include the following: 

a. The NC3A contract number; 

b. The NC3A Project Title; 

c. Item description; 

d. Item part number and serial number; 

e. CLIN number as per the SSS; 

f. Name and address of the Contractor/ Sender, the Purchaser and Consignor; 

g. Detailed weight and dimensions per box/pallet/container; 

h. Box number and number of boxes in the consignment. 

5.5.5. Customs Form 302 

5.5.5.1. The Contractor shall ensure the timely request of Customs Form 302 through the 

NC3A/ILS PoC fifteen (15) working days before a shipment. A Customs Form 

302 is required for duty free import/export of supplies. Following receipt of the 

request by the NC3A/ILS PoC, normally a maximum of three working days is 



44/104



CO-13355-OPL 


required for the issue of the form. This form is not required for movements within 

the European Union. 

5.5.5.2. These forms have to be originals and cannot therefore be faxed but have to be 

mailed or sent by mail/express courier. In case that an express courier has to be 

used to ensure that the form is available in time before shipment, all associated 

costs shall be the responsibility of the Contractor. 

5.5.5.3. The written request for a 302 form shall contain the following information: 

a. Purchaser Contract Number. 

b. CLIN, Designation and Quantities. 

c. Destination. 

d. Number and Gross Weight. 

e. Consignors and Consignee’s Name and Address. 

f. Method of Shipment, i.e. road, rail, sea, air, etc. 

5.5.5.4. If a country refuses to accept the Form 302 and requires the payment of customs 

duties, the Contractor shall immediately inform the Purchaser by the fastest means 

available and obtain from the Customs Officer a written statement establishing that 

his country refuses to accept the Form 302. Only after having received Purchaser’s 

approval the Contractor shall pay these customs duties and the Purchaser shall 

reimburse the Contractor at actual cost against presentation of pertaining 

documents. 

5.5.5.5. The Contractor shall inform forwarding agents of the availability of Form 302 and 

how this form is utilised to avoid the payment of customs duties. This Form 302 

shall be added to the shipping documents to be provided to the carrier. 

5.5.6. Notice of Shipment 

5.5.6.1. Ten (10) working days before each shipment of supplies, the Contractor shall 

provide the NC3A/ILS PoC with a Notice of Shipment (NoS) comprising the 

following details: 

a. Shipment Date. 

b. Contract Line Item. 

c. Consignor and Consignee. 

d. Number of Packages/Containers. 

e. Final/Partial Shipment. 

f. Mode of Shipment. 

g. Number of 302 Forms used. 



45/104



CO-13355-OPL 


5.6.Warranty 

5.6.1. The Contractor shall provide Warranty for all Hardware and Software 

Configuration Items procured under this Contract; 

5.6.2. The period of Warranty for the Hardware and Software Configuration Items shall 

be one (1) year, starting at the time of FSA; 

5.6.3. The Contractor shall repair/ replace/ fix all CI’s received through the Support 

and/or Maintenance process as per their internal procedures with the highest 

priority allocated and shall be responsible to return the repaired/ replacement/ 

fixed CI to the NATO CIS Logistics Depot (CLD) in Brunssum, the Netherlands 

through express delivery or electronic submission within five (5) days of receipt; 

5.6.4. The Contractor shall warrant that any developed Hardware or Software CI(s) shall 

perform according to the requirements. If the Contractor becomes aware at any 

time before acceptance by the Purchaser that a defect exists in any Hardware or 

Software CI, the Contractor shall coordinate with the Purchaser and promptly 

correct the defect; 

5.6.5. During the warranty period, the Contractor shall be responsible for the provision 

of any alternative or superseding items, should the original part be no longer 

available, ensuring compliance with the fielded baseline; 

5.6.6. During the warranty period, the Contractor shall be responsible for implementing 

all COTS hardware and/or software upgrades. The availability of COTS hardware 

and/or software upgrades shall be made known to the Purchaser and, if proposed 

for introduction by the Contractor for whatever reason, including any corrective 

action for an identified fault, shall always be subject to Purchaser approval. 

5.6.7. Within ten (10) working days after End of Warranty (EoW) date, the Contractor 

shall submit a Warranty Report that documents all warranty cases, affected CI’s, 

taken activities, cost and schedule. 

5.7.Configuration Management 

5.7.1. The Contractor shall implement a Configuration Management (CM) program in 

accordance with the Allied Configuration Management Publication (ACMP-1 

through ACMP-7). 

5.7.2. The Contractor shall ensure that an effective CM organisation is established and 

maintained to implement the CM program throughout the duration of the contract. 

5.7.3. Under the CM program the Contractor shall maintain and update all project CIs as 

requested by changes within the project or external to the project throughout the 

duration of the contract. 



46/104





47/104 

CO-13355-OPL 


5.7.4. Configuration Item Identification - The Contractor shall identify Configuration 

Items (CIs) in accordance with ACMP-2. The CIs shall be chosen in a way to 

assure visibility and ease of management throughout the development effort and 

the support after acceptance. 

5.7.5. All COTS, adapted and developed hardware and software shall be designated as 

CIs. Every CI shall have a unique identifier. The level of granularity for the CI 

selection shall reach at minimum Line Replaceable Units (LRUs) for hardware CIs 

and software/firmware unit as defined in ACMP-1 for software CIs. 

5.7.6. Hardware CI attributes shall include, but are not limited to, the Material Data 

Sheet (MDS) information described above. Software CI attributes shall include, 

but are not limited to the ACMP-1 definitions. 

5.7.7. The Purchaser reserves the right to modify the CI structure and attributes prior to 

its baselining. 

5.7.8. The Contractor shall ensure that all CIs are persistently stored in a COTS 

Configuration Management Database (CMDB) and that it shall be kept consistent 

and updated. 

5.7.9. Configuration Control - The Contractor shall be fully responsible for the 

Configuration Control of all CIs. Configuration Control shall be exercised in 

accordance with ACMP-3. 

5.7.10. Configuration Status Accounting - The Contractor shall be fully responsible for 

the Configuration Status Accounting (CSA) for all CIs. The Contractor shall 

deliver CSA reports to the Purchaser both as part of management and specialist 

products in this contract and also as standalone documents at the Purchaser’s 

request. At the end of the Contract, the Contractor shall deliver a set of final CSA 

reports for each CI in both hard copy and in electronic media. Configuration Status 

Accounting shall be exercised in accordance with ACMP-4. 

5.7.11. Configuration Verification – During PSA, the Contractor shall support on-site 

auditing of the installed configuration to demonstrate that the as-built actual status 

of all CIs matches the authorised state of CIs as registered in the CMDB and 

pertinent CSA reports. The Contractor shall support auditing effort by providing 

the required Baseline Documentation and answering questions from the 

Purchaser’s Auditor. Configuration Verification shall be exercised in accordance 

with ACMP-5. 

5.7.12. Configuration Management Data Base - The Contractor shall create and maintain a 

COTS based Configuration Management Database (CMDB) that persists the 

Configuration Items, pertinent CI-item attributes, and CI (inter-) relationships. The 

Contractor shall provide the CMDB prior to PSA. The CMDB shall be in a nonproprietary 

standard format such as a CSV or a Microsoft Excel file format to 

ensure compatibility from a variety of applications.



CO-13355-OPL 


5.8.Initial Training Requirements 


5.8.2. The Contractor shall provide training in theatre. Two types of training shall be 

provided: 

5.8.2.1. CCTV HQ ISAF Operator Training Course, for setting up and operating the 

CCTV HQ ISAF (also including Level 1 maintenance training); 

5.8.2.2. CCTV HQ ISAF Maintenance Training Course, for HQ ISAF BSG personnel who 

will conduct level 2 maintenance (consisting of level 1 and 2 maintenance 

training); 

5.8.3. Training material 

5.8.3.1. The Contractor shall provide Course material packages for both types of training 

courses, to include: 

5.8.3.1.1. Student handbooks for each course type, providing the student with necessary 

information on all lesson objectives and contents, guidance for all learning 

activities and cross-references to assist the students in achieving the course 

objectives; 

5.8.3.1.2. Self-training material for each course type, providing the student with all 

necessary information to assist the students in learning the operation of the 

CCTV HQ ISAF without access to a trainer or instructor-led course; 

5.8.3.1.3. Course certificates for each course type to certify students successfully 

completed the course; 

5.8.3.1.4. Trainer guides for each course type, containing all necessary information for 

future trainers to prepare and conduct lessons, and to evaluate students, 

including exercises, quizzes, and examinations (with their corresponding 

answer sheets); 

5.8.3.2. For each training course, the training course package shall provide training 

material in the following quantities: 

Material No. of Copies Media 

Student handbook 10 Printed + CD 

Self-training material 10 Printed + CD 

Course certificates 10 Printed + CD 

Trainer’s guide 2 Printed + CD 

Table 1 Training documentation deliverables 



48/104



CO-13355-OPL 


5.8.3.3. The Maintenance Training Course package shall be based on the Operator 

Training Course package, modified or augmented as follows: 

5.8.3.3.1. Background and context information shall be covered with a higher level of 

detail, to give the trainer a closer view of the CCTV HQ ISAF network 

architecture, through detailed system diagrams; 

5.8.3.3.2. Removal and replacement of major system components; 

5.8.3.3.3. Review of any additional capabilities that the system can provide; 

5.8.3.3.4. Training material specifically build for maintenance personnel to maintain the 

CCTV HQ ISAF in theatre; 

5.8.3.4. The Contractor shall provide the Self-training material, as follows: 

5.8.3.4.1. Electronic media shall be delivered to take the customer step by step through 

the operation and maintenance of CCTV system without an instructor. 

5.8.3.4.2. Electronic media instruction discussing operation of the system shall be 

accompanied with screen shots that clearly show the operator what is expected 

on screen. 

5.8.3.4.3. Electronic media instruction discussing maintenance shall clearly display the 

component, adjacent components, and all interconnections. Images should be 

viewable from various angles while maintaining the aspect ratio. The training 

shall be designed to be understood by the beginner to intermediate level 

technician. 

5.8.3.4.4. Training materials shall describe how to resolve error problems to include 

complete discussions on the indications, probable causes, and course of actions 

to resolve the problems. 

5.8.3.4.5. Electronic media shall contain an index that is linked to the corresponding 

area. The electronic media shall be searchable in order to facilitate keyword 

searches. E.g. if the operator types in the word “cleaning”, all locations that 

involve cleaning shall be listed and the operator selects the appropriate 

reference. 

5.8.3.4.6. Training materials shall detail the method of submission of trouble tickets to 

the contractor during the active CLS period to expedite technical support. 

5.8.3.5. The initial training documentation requirements are, but not limited to: 

5.8.3.5.1. Overview of the CCTV HQ ISAF capabilities, 

5.8.3.5.2. Overview of the CCTV HQ ISAF and its components, 



49/104



CO-13355-OPL 


5.8.3.5.3. Setup of the CCTV HQ ISAF: 

5.8.3.5.4. Basic troubleshooting of the CCTV HQ ISAF: 

5.8.3.5.5. Fault resolution and workarounds, including: 

5.8.3.5.6. Cable replacement, 

5.8.3.5.7. Fuse replacement, 

5.8.3.5.8. Lighting replacement, 

5.8.3.5.9. Retractable Mast Operation, 

5.8.3.5.10. Lens Cleaning Periodicity and requirements, 

5.8.3.5.11. Support processes (including a description of where to ask for support (hotlines, 

if provided by the Contractor) and how to report issues). 

5.8.3.6. All training material shall be written in the English language. 

5.8.3.7. Training material in electronic format must be executable utilizing Microsoft 

Windows 2000, Microsoft Windows XP, Microsoft Windows Vista, and Microsoft 

Windows 7 operating system. Associated viewers must be installed on electronic 

media e.g. Adobe Reader, PPT Viewer, Freewrl, XJ3D, X3D-Edit, et cetera. 

5.8.3.8. All training material delivered under this Contract shall be subject to review and 

approval by the Purchaser. The Contractor shall deliver, at least four (4) weeks 

prior to the delivery of the training, a complete draft of all training material for 

review by the Purchaser. Upon acceptance of the draft version, the Contractor shall 

deliver the final version of the training material in accordance with the Schedule of 

Supplies and Services (SSS). 

5.8.4. Initial training course requirements 

5.8.4.1. The Contractor shall provide instructor led courses at the locations as follows: 

Course Location Frequency 

CCTV HQ ISAF 

HQ ISAF 

Operator Training Course 

1 

CCTV HQ ISAF 

HQ ISAF 

Maintenance Training Course 

1 

Table 2 Training locations 

5.8.4.2. For the instructor led courses it can be assumed that the maximum number of 

students will be eight (8). 



50/104



CO-13355-OPL 


5.8.4.3. The Purchaser can make available the training facilities for the instructor-led 

courses. 

5.8.4.4. The Contractor is responsible for specifying and requesting the training facilities. 

5.8.4.5. The estimated training durations are given below: 

Training 

Duration [Days] 

CCTV HQ ISAF 

2 

Operator Training Course 

CCTV HQ ISAF 

3 

Maintenance Training Course 

Table 3 Training duration 

5.8.4.6. The estimated durations exclude any Contractor training preparation at the two 

locations. 

5.8.4.7. The Contractor shall not assume any knowledge or experience prerequisite for the 

users and future trainers, other than a working-level proficiency in the English 

language, basic user-knowledge of the Microsoft Windows Operating System, of 

the Microsoft ‘Office’ suite, and of the Microsoft Internet Explorer browser. 

5.8.4.8. Instructors shall meet a minimum English language proficiency equivalent to SLP 

4444 (in accordance with NATO STANAG 6001). 

5.8.4.9. The Contractor shall deliver, as part of the ILSP, a Training Plan detailing the 

development of the training deliverables and performing of the training courses. 

5.8.4.10. The Contractor shall evaluate each training course through the use of evaluation 

forms to be filled in by every student. The completed evaluation forms will be 

incorporated in a Training Evaluation Report. This report will be made available to 

the Purchaser within two (2) weeks after conclusion of each training course. 

5.8.4.11. The Contractor shall update the training material when necessary based on the 

outcome of the evaluations. 

5.8.4.12. The Contractor shall update the training material whenever a modification, 

upgrade or version change is implemented to the CCTV HQ ISAF as supplied to 

the Purchaser. 

5.8.4.13. The contractor shall provide instructors for additional CCTV HQ ISAF courses 

following the training in theatre, as options to the contract. 



51/104



CO-13355-OPL 


SECTION 6: 

QUALITY ASSURANCE AND CONTROL 

6.1.Quality Assurance Program 

6.1.1. The Contractor shall establish, execute, document and maintain an effective 

Quality Assurance (QA) program throughout the Contract lifetime. This program 

shall be in accordance with the compliance documents. 

6.1.2. The QA program shall apply to all services and all products (both management 

products and specialist products) to be provided by the Contractor under this 

contract (this includes all hardware and software COTS as well as developed for 

this project – documentation and supplies that are designed, developed, acquired, 

maintained or used, including deliverable and non-deliverable items). 

6.1.3. The QA program shall ensure that procedures are developed, implemented and 

maintained to adequately control the design, development, production, purchasing, 

installation, inspection, testing, configuration management and customer support 

of all services and all products (both management products and specialist 

products), in accordance with the requirements of this Contract. 

6.1.4. The QA Program shall meet the requirements of AQAP-2110. The Contractor 

shall have an ISO 9001 certificate and operate in accordance with AQAP 2110 and 

AQAP 2130. 

6.1.5. The QA program shall be described in detail in the Quality Assurance Plan (QAP). 

6.1.6. The QAP shall clearly indicate the QA activities, responsibilities, and controls for 

the Contractor and any sub-Contractors. The Contractor shall include in the QAP 

the certificates of the same nature for all major sub-Contractors who are expected 

to manufacture and deliver critical elements of the system and show how the 

provisions of the Prospective Contract regarding QA/QC will be inserted in all 

subcontracts and enforced by the Prime Contractor. 

6.1.7. The initial version of the QAP shall be provided to the Purchaser for acceptance. 

Upon Purchaser Acceptance, the QAP shall be placed under the Purchaser’s 

Configuration Control Board. 

6.1.8. The acceptance of the QAP by the Purchaser signifies only that the Purchaser 

agrees to the Contractor’s approach in meeting the requirements. This acceptance 

in no way relieves the Contractor from its responsibilities to meet the requirements 

stated in this Contract. 

6.1.9. The Contractor shall review his QA program periodically and audit it for 

adequacy, compliance and effectiveness. 



52/104





53/104 

CO-13355-OPL 


6.1.10. If the Purchaser detects that the Contractor does not respect the QA program as 

described in the QAP, the Purchaser has the right to suspend the Contractor’s 

activities without any compensation for the Contractor. 

6.2.Purchaser Quality Assurance Representative 

6.2.1. As provided under STANAG 4107, the Purchaser has the right to delegate some 

of the QAR responsibilities to a National Quality Assurance Representative 

(NQAR). 

6.2.2. The Contractor shall agree to provide all necessary assistance to the QAR or his 

delegated National Quality Assurance Representative (NQAR). The Contractor 

shall make his quality records, and those of his sub-Contractors, available for 

evaluation by the QAR/NQAR throughout the duration of the Contract. Quality 

audits at the Contractor or sub-Contractors premises will in principle only be 

executed by the QAR/NQAR if the documents provided by the Contractor do not 

sufficiently guarantee that a valid QA system is available. 

6.2.3. AQAP-2009 will be used by the Purchaser as a guide for the evaluation of the 

Contractor’s QA program. Such evaluations shall not be used by the Contractor to 

avoid his own responsibility for ensuring that the QA requirements are met. The 

QAR will also use AQAP-159 and ISO/IEC 9126 as guides for QA review of 

software that has to be developed under this Contract. 

6.3.Quality Log 

6.3.1. The Quality Log summarises all the quality checks that are planned and that have 

taken place on each product earmarked for quality checking. 

6.3.2. The Quality Log shall be a table and shall comprise the following information: 

6.3.2.1. Reference Number; 

6.3.2.2. Product; 

6.3.2.3. Method of quality checking; 

6.3.2.4. Staff responsible, name, role; 

6.3.2.5. Planned date; 

6.3.2.6. Actual date; 

6.3.2.7. Result; 

6.3.2.8. Number of action items; 

6.3.2.9. Target sign-off date;



CO-13355-OPL 


6.3.2.10. Actual sign-off date. 



54/104



CO-13355-OPL 


SECTION 7: 

DOCUMENTATION 

7.1.Documentation Requirements 


7.1.1.1. The documentation to be provided by the Contractor under this contract falls in 

three groups: System Documentation, ILS Documentation and Project 

Documentation. 

7.1.1.2. The System Documentation shall consist of: 

SDS Document 

System Design Specification 

Test Procedures 

Maintenance Manuals 

OEM Manuals 

Operating Manuals 

Custom Manuals 

System Configuration Files 

As Built Drawings 

Test Reports 

Off-Specification Documents 

Due 

EDC + 8 weeks 

EDC + 8 weeks 

EDC + 18 weeks 








7.1.1.2.1. The System Documentation shall be part of the packaging of the CCTV HQ ISAF 

components, when the system is shipped to theatre. 

7.1.1.3. The ILS Documentation shall consist of: 

ILS Document 

Integrated Logistics Support Plan 

Transportation Plan 

Master Test Plan 

Draft RSPL 

Final RSPL 

Material Data Sheet (MDS) 

Draft Training Material 

Final Training Material 

Final System Inventory 

Configuration Management Database (CMDB) 

Known Error Database (KEDB) 

Notice of shipment 

Packing Lists 

Warranty Report 

Due 

EDC + 2 weeks 

EDC + 2 weeks 

EDC + 2 weeks 

EDC + 5 weeks 

EDC + 8 weeks 

EDC + 8 weeks 






2 weeks before each shipment 

3 weeks before each shipment 

FSA + 12 months 



55/104



CO-13355-OPL 


Training Evaluation Report 

End of Training + 2 weeks 

7.1.1.4. The Project Documentation shall consist of: 

Project Documentation 

Project Implementation Plan (PIP) 

System Implementation Plan (SIP) 

Requirements Traceability Matrix (RTM) 

Project Status Reports 

Due 

EDC + 2 weeks 

EDC + 2 weeks 

EDC + 2 weeks 

Monthly - starting at EDC + 4 weeks 

7.1.2. Documentation Format 

7.1.2.1. All the documentation to be provided under this Contract shall be written in 

English. 

7.1.2.2. The convention to be used for numbers appearing in non-COTS textual documents 

is for a comma to be the thousands separator and a period to be the decimal 

separator (e.g. 1,365,276.24). 

7.1.2.3. The convention to be used for dates appearing in free text (e.g. quoting dates of 

meetings) is day-month-year and not month-day-year. 

7.1.2.4. The security classification of any non-COTS documentation shall follow the NATO 

security guidelines. No Contractor-provided documentation shall bear any non- 

NATO protective markings. 

7.1.2.5. Any contractual documentation shall have a clear title indicating the Contractual 

deliverable it pertains to, a reference and version number, and appropriate signature 

blocks demonstrating that the documentation has been subject to the Contractor’s 

quality process. 

7.1.2.6. Any contractual documentation shall include a ‘version history’ block identifying at 

least for the last version the complete list of changes brought to the document since 

the previous version, and clearly indicating any superseded documents (including 

the previous version of the document). 

7.1.2.7. Each change from the previous version shall be identified at least by Section#, 

Page#, Nature of change. (A summary list is sufficient provided that the changes 

are tracked within the document, e.g. using the ‘change tracking’ mechanism in MS 

WORD, or some equivalent for other applications). 

7.1.3. System Configuration Files 

7.1.3.1. The default configuration of any of the CCTV HQ ISAF component shall be 

documented in the System Configuration Files. 



56/104



CO-13355-OPL 


7.1.3.2. The System Configuration Files shall also contain guidance on how to show, edit 

and save those configurations on the respective devices, together with user or 

administrator passwords. 

7.1.3.3. The System Configuration Files shall be classified and labelled NATO 

UNCLASSIFIED. 

7.1.4. Operator Manual and Maintenance Manual 

7.1.4.1. The Contractor shall provide installation and configuration documentation as part 

of the maintenance manual. 

7.1.4.2. The Contractor shall create, update, maintain and deliver the Operator Manual and 

the Maintenance Manual which shall describe the complete system by the 

explanation of functional blocks and Configuration Items. 

7.1.4.3. The Operator Manual and the Maintenance Manual shall contain descriptions, with 

appropriate drawings, of the mechanical, electrical, and electronic assemblies and 

sub-assemblies that comprise the applicable major product components. 

7.1.4.4. The Operator Manual shall define the in-depth, step by step procedure how to 

operate the system and how to perform operator level maintenance tasks, i.e. the 

pertinent level 1 maintenance tasks as identified in the Maintenance Concept. 

7.1.4.5. The Maintenance Manual shall define the in-depth, step by step procedure how to 

perform the 1st, 2nd and 3rd level maintenance tasks as identified in the 

Maintenance Concept. 

7.1.4.6. For all COTS Configuration Items, the maintenance manual shall take maximum 

advantage of the existing COTS-vendor Original Equipment Manufacturer (OEM) 

manuals and documentation, supplemented with adaptations, and additions relevant 

to the products furnished under this Contract. 

7.1.4.7. The maintenance manual shall define the required maintenance tools and test 

equipment. 

7.1.4.8. At least one hard copy and one soft copy shall be provided for the CCTV HQ ISAF 

of the following: 

7.1.4.8.1. As Build Drawings - As Built drawings shall be self-sufficient and independent of 

any other documents and shall cover Plans of the physical details of all installed 

equipment, apparatus and devices, and details of all interfaces. 

7.1.4.8.2. OE M Manuals - The Contractor shall provide original equipment manufacturer 

manuals for all CCTV HQ ISAF commercial off the shelf (COTS) hardware and 

software installed. 



57/104



CO-13355-OPL 


7.1.4.8.3. Custom Manuals - The Contractor shall provide manuals or operating instructions 

for all custom CIs developed or adapted specifically for the CCTV HQ ISAF 

project. 

7.2.Documentation Delivery and Review 

7.2.1. The documentation shall be available on electronic media using standard software 

packages at least readable on Microsoft based systems (windows 2K, XP, Vista, 

and Windows 7) and allowing ‘cut and paste’ so that the Purchaser can easily 

transfer some of their contents to other documents. 

7.2.2. The Contractor shall submit all documentation in electronic and paper format to 

the Purchaser for review and comments as applicable. 

7.2.3. At each review cycle, the Purchaser will state if the document is or is not likely to 

be accepted in its Final version. 

7.2.4. Except otherwise stated for specific documents, the following provisions shall 

apply for any documentation to be provided by the Contractor under this contract: 

7.2.4.1. The Contractor shall provide a first draft (version 0.1) of each deliverable for 

Purchaser review. The first draft shall be substantially complete and correct. 

7.2.4.2. The Purchaser shall provide comments, corrections, and suggested changes to the 

Contractor within one (1) week of receipt. The Purchaser reserves the right to 

return without review a document that has significant deficiencies (e.g. a document 

only including a table of contents). The Contractor shall not rely on the Purchaser 

review to fill in deficiencies or obtain missing Purchaser information. 

7.2.4.3. The Contractor shall resubmit the document as a revised draft (version 0.2) 

incorporating the Purchaser's comments within one (1) week after receipt. 

7.2.4.4. The Purchaser shall provide comments, corrections, and suggested changes to the 

Contractor within one (1) week of receipt. 

7.2.4.5. The Contractor shall provide the Final (version 1.0) document within one week of 

receipt of the Purchaser's comments on the revised draft. 



58/104



CO-13355-OPL 


SECTION 8: 

TESTING AND ACCEPTANCE 

8.1.General 

8.1.1.1. This section outlines the testing process to be applied to all test activities to be 

performed under this Contract. 

8.2.Testing Approach 

8.2.1. The CCTV HQ ISAF requires a set of testing activities to verify its compliance 

with the contractual requirements, to demonstrate its operational suitability, and to 

evaluate its performance to establish benchmarks for future enhancements. 

8.2.2. All equipment and facilities identified as a configuration item and supplied by the 

Contractor shall be tested under the control of the QA organisation defined in 

SECTION 6: and the special requirements of this specification. 

8.2.3. The Contractor shall have the overall responsibility for meeting the CCTV HQ 

ISAF testing requirements and conducting all related activities. This responsibility 

includes the development of all test documentation required under this contract, 

the provision of all personnel, documentation, equipment and facilities required to 

complete all testing and the evaluation and documentation of the tests results. The 

Contractor shall maintain complete records of all testing. 

8.2.4. The Testing Approach shall comprise three test sessions as follows: 

Test Location Due 

Factory Acceptance Test (FAT) including 

the validation of system expandability Contractor's premises EDC + 8 weeks 

Site and System Activation Testing 

(SSAT) HQ ISAF EDC + 18 weeks 

Operational Test and Evaluation (OT&E) HQ ISAF EDC + 19 weeks 

8.2.5. Before each test session the Contractor shall ensure that its hardware, software, 

test equipment, instrumentation, supplies, facilities, and personnel are available 

and in place to conduct the test session. 

8.2.6. The Purchaser will monitor and inspect the Contractor’s test activities to ensure 

compliance. 

8.2.7. As the supporting documentation for each test session the Contractor shall develop 

the System Test Documentation Package. 

8.3.System Test Documentation Package 

8.3.1. As part of the PIP the contractor shall provide a System Test Documentation 

Package comprising the following documents: 



59/104



CO-13355-OPL 


8.3.1.1. the Project Test Plan (PTP); 

8.3.1.2. the System Version Definition Document; 

8.3.1.3. the test procedures; 

8.3.1.4. any submitted test waivers together with supporting material; 

8.3.1.5. the requirements traceability matrix updated with test-related information; 

8.3.1.6. the updated system Off-specifications Document: 

8.3.1.7. the results of the dry-runs performed by the Contractor as a preparation for the 

upcoming test session. 

8.3.2. The Purchaser will review the Contractor’s System Test Documentation Package 

for correctness, completeness, and acceptance. 

8.3.2.1. Specifically, the Purchaser shall have the right to reject any test waiver. 

8.3.2.2. The Contractor shall record and log all test waiver requests along with their 

resolution. 

8.3.2.3. Upon completion of the test session, the Contractor shall provide the updated 

version of the System Test Documentation Package. 

8.3.3. Project Test Plan 

8.3.3.1. As part of the System Test Documentation Package the Contractor shall provide 

and maintain a Project Test Plan (PTP) covering all tests activities in this Contract, 

describing all tests and supporting tasks to meet the requirements of this SOW 

including the SRS, the CSRS/SSRS, SISRS. The Contractor shall extend the 

Requirements Traceability Matrix to the Product Baseline to maintain full 

traceability between the functional, the developmental, and the product baseline, 

so as to ensure the Purchaser can verify compliance throughout the project. 

8.3.3.2. The PTP shall describe how the Contractor plans to meet the following objectives: 

8.3.3.2.1. Compliance with the requirements of the Contract; 

8.3.3.2.2. Verification that the design produces the capability required; 

8.3.3.2.3. Compatibility among internal system components; 

8.3.3.2.4. Compliance with the requirements of the SRS and with external system interfaces 

as defined in the ICDs; 

8.3.3.2.5. Confidence that system defects are detected early and tracked through to 

correction; 



60/104



CO-13355-OPL 


8.3.3.2.6. Operational readiness and suitability; 

8.3.3.2.7. System characterisation to establish the system’s performance benchmarks. 

8.3.3.3. The PTP shall describe the Contractor’s test organisation and its relationship with 

the Contractor’s Project Management Office and QA functions. 

8.3.3.4. The PTP shall provide a flow diagram that shows the overall sequence of tests, the 

location, and Contractor and Purchaser equipment and personnel involved in each 

test, and the relationship of test events to project milestones. 

8.3.3.5. The PTP shall identify the entry and exit criteria proposed by the Contractor for 

each test session. 

8.3.3.6. The PTP shall identify any specialised or long-lead items required for testing. 

8.3.3.7. The PTP shall identify all the CCTV HQ ISAF Configuration Items (CIs) that are 

subject to the test program and shall indicate by which method the items will be 

tested. 

8.3.3.8. The PTP shall include a detailed description of the design and configuration of the 

Factory Acceptance Testbed and of the Certification Testbed. 

8.3.4. Security Implementation Verification Procedures (SIVP) 

8.3.4.1. The Contractor shall provide and maintain SIVP. The SIVP shall consist of a set of 

software scripts that shall allow a Site System Security Officer to verify that the 

installed system at a site comply with the CSRS, SSRS, SISRS and CPS if the 

system includes a PKI and Security Operating Procedures. 

8.3.5. Test waivers 

8.3.5.1. For some specific requirements, rather than perform actual tests the Contractor may 

choose to provide documentary evidence to show that these requirements are 

fulfilled. 

8.3.5.2. This documentary evidence may either be a rationale based on existing design or 

specification documentation, or rely on previously successfully completed 

qualification testing to national or international standards for assemblies, 

subassemblies, components or parts. 

8.3.5.3. If the Contractor intends to rely on previously successfully completed qualification 

testing to national or international standards for assemblies, subassemblies, 

components or parts, the Contractor shall produce the following documentation: 

8.3.5.3.1. The equipment specifications and true manufacturing number to demonstrate that 

the CCTV HQ ISAF CI for which a test waiver is requested is identical to the 

equipment previously tested, 



61/104



8.3.5.3.2. The SRS, CSRS/SSRS, SISRS requirement(s) covered by the test waiver, 

8.3.5.3.3. The test standards, procedures and methods employed on the testing; and 

8.3.5.3.4. The nationally or internationally certified test results. 

8.5.1. Classification of Test Failures 



62/104 

CO-13355-OPL 


8.3.5.3.5. A Statement in which the Contractor shall certify that the equipment to be 

implemented is identical to that which was originally tested and certified, or advise 

the Purchaser of design/construction changes which affect form, fit or function. In 

the latter case, the Purchaser, after review of such changes and their impact, shall 

have the right to require test and certification of the modified equipment, at no cost 

to the Purchaser. 

8.4.Requirements Traceability Matrix 

8.4.1. The Contractor shall develop and maintain a Requirements Traceability Matrix 

(RTM) that establishes a complete cross-reference between: 

8.4.1.1. the requirements stated in the SRS; 

8.4.1.2. the detailed contents of the SDS in terms of SDS statements and lowest-level CIs; 

8.4.1.3. The test cases (or test waivers), intended to demonstrate compliance to the 

requirements. 

8.4.1.4. The Requirements Traceability Matrix shall include the following data: 

8.4.1.4.1. List of all numbered requirements in the SRS, list of any additional requirements 

identified in the SSRS; 

8.4.1.4.2. For each requirement, two-way traceability between the requirement and the design 

feature that implements the requirement; 

8.4.1.4.3. For each requirement, identification of any Off-specifications associated with the 

requirement; 

8.4.1.4.4. For each requirement already successfully tested: identification of the test(s) or test 

waiver(s) on the basis of which the requirement was demonstrated; 

8.4.1.4.5. For each requirement not yet successfully tested: identification of the test(s) or test 

waiver(s) that are intended to demonstrate the requirement. 

8.4.2. The Contractor shall extend the requirements traceability matrix to reflect the 

results of all previous test sessions, and show how the tests and any test waivers 

relevant to the test session demonstrate the associated requirements. 

8.5.Test Failures



CO-13355-OPL 


8.5.1.1. Should a failure occur during testing, a failure report shall be raised by the 

Contractor and a preliminary investigation shall be immediately carried out in order 

to classify the failure as one of the following: 

8.5.1.1.1. Class “A”: there is evidence that the cause was an external or transient condition; 

8.5.1.1.2. Class “B”: there is mutual agreement that the cause was an inherent design or 

manufacturing deficiency in the unit under test; or 

8.5.1.1.3. Class “C”: When the specific nature of the cause cannot be immediately determined 

and a more detailed investigation is required before a conclusion can be drawn. 

8.5.1.2. Class "A" Failures 

8.5.1.2.1. In the event that a preliminary investigation results in the classification of a failure 

as is described above, the test shall be repeated at least three successive times. 

8.5.1.2.2. If the re-test is successful, the Purchaser will close the observation and testing shall 

be resumed from the point immediately after that where the failure occurred. 

8.5.1.2.3. If a failure is encountered prior to the successful completion of the re-test, the 

failure category shall be changed to class "B" or "C", as described below. 

8.5.1.3. Class "B" Failures 

8.5.1.3.1. In the event that a failure is classified as a Class "B" from above, the equipment 

shall be rejected and all testing related to that particular series of tests shall be 

suspended until such a time as the Contractor determines the specific cause of the 

failure and proposes appropriate remedial action acceptable to the Purchaser. 

8.5.1.3.2. Should the cause of the failure or the effect of the proposed remedial action be 

deemed by the Contractor to have no influence whatsoever on other areas of 

scheduled testing, the Contractor may propose to the Purchaser to continue testing 

in the other areas prior to the rectification of the cause of the failure. 

8.5.1.3.3. If such proposals are accepted by the Purchaser, the Purchaser shall have the right 

to require repetition of any or all tests performed in these circumstances after the 

rectification of the cause of the failure and the subsequent re-tests, to prove they 

have been successfully completed. 

8.5.1.3.4. The Contractor shall be responsible for all costs related to the rectification of 

deficiencies or failures and subsequent re-testing caused by the design or 

production of the deliverables identified during the verification and/or testing 

cycles. The Contractor shall be responsible for any travel, subsistence and other 

incidental expenses incurred by the Purchaser as a result of the requirement for the 

re-performance of tests necessitated by test failures. 



63/104



CO-13355-OPL 


8.5.1.3.5. After remedial action has been taken by the Contractor, the test may be resumed at 

the step during which the deficiency or failure was identified, however, the 

Purchaser shall have the right to require that re-testing includes all of the tests 

related to the verification of that particular specification requirement. 

8.5.1.3.6. The Contractor shall seek the Purchaser's agreement of a mutually suitable time 

when testing shall be resumed, subsequent to the Purchaser having accepted the 

contents of a formal submission by the Contractor providing full details describing 

the cause of the failure and the recommended remedial actions to be taken. 

8.5.1.4. Class "C" Failures 

8.5.1.4.1. In the event that a failure is classified as a Class "C" from above, all testing shall be 

immediately suspended until such a time as the Contractor completes a detailed 

investigation and subsequently recommends to the Purchaser, that the failure should 

be re-classified as either a Class "A” or "B", as appropriate. The actions previously 

described relating to these classifications shall then be commenced. 

8.5.1.4.2. In this context, should it be determined that the test failure was due to a component 

failure and not attributable to a deficiency in equipment design, or a defective 

process during manufacture of the equipment, then the defective component may be 

replaced and the failure re-classified as a Class "A" failure. 

8.5.2. Test Reports 

8.5.2.1. The results of each test called for in the test plan shall be recorded in test results 

sheets incorporated in the relevant test procedure. 

8.5.2.2. The test procedure with attached test results sheets is called the Test Report. 

8.5.2.3. Each test will only be declared ‘passed’ if the entirety of the expected results were 

obtained when running the test. 

8.5.2.4. The test report cover sheet shall clearly show whether the test passed, failed, or was 

not run and for what reasons. 

8.5.2.5. Where the Purchaser or his representative has witnessed the testing, appropriate 

annotations shall be made on each page of the test results to ensure that the test 

report is a true record of test activities and results as witnessed by the Purchaser, 

and the whole test report shall be signed by the Contractor representative and by the 

Purchaser representative on completion of that testing. 

8.5.2.6. Each original test report plus one copy shall be distributed to the Purchaser for 

acceptance within Fifteen (15) working days after the completion of the test. 

8.5.2.7. System Off-specifications 



64/104





65/104 

CO-13355-OPL 


8.5.2.8. Throughout any test session Off-specifications will be identified, either as a result 

of test failures, or noted while running tests regardless of whether the tests 

eventually pass or fail. 

8.5.2.9. Throughout any test session the Contractor shall maintain Off-specifications 

Reports and the Off-specifications Document describing all noted Offspecifications. 

8.5.2.10. The contents of the required Off-specification Reports and Off-specification 

Document are outlined in sections 8.5. 

8.5.2.11. Tests status meetings 

8.5.2.12. Throughout any test session the Contractor shall organise and conduct Tests Status 

Meetings with the Purchaser on a weekly basis to discuss: 

8.5.2.12.1. the results of the tests run to date, 

8.5.2.12.2. any new Off-specifications raised, 

8.5.2.12.3. any adjustments to the schedule of test activities within the test session, 

8.5.2.12.4. any other issues. 

8.6.Provisional System Acceptance 

8.6.1. A Provisional System Acceptance (PSA) shall begin after installation of the CCTV 

HQ ISAF network. PSA is the process by which the Purchaser evaluates the 

delivered and installed CCTV system and associated ILS to ensure that it fulfils all 

requirements and standards as stated in the Contract. 

8.6.2. Prior to system acceptance, the Contractor shall: 

8.6.2.1. prove that the CCTV HQ ISAF can adequately process, display, and show thermal 

imagery for Type I, Type II, and Type III cameras; 

8.6.2.2. demonstrate the archival, data retrieval, and analysis capability of the system under 

test; 

8.6.2.3. deliver all training to the operator and level 1 & 2 maintenance personnel; 

8.6.2.4. deliver all training material and electronic self training aids to the customer; 

8.6.2.5. deliver all as built documentation to include technical manuals to the customer; 

8.6.2.6. deliver all software licenses for associated with the CCTV system to the customer. 

8.6.3. PSA requirements;



CO-13355-OPL 


8.6.4. Successful completion of agreed testing. 

8.6.5. Delivery of all required spares, special tools and test equipment and consumable 

items and accomplishment of complete inventory taking. 

8.6.6. Delivery of all required site-level/as-built documentation. 

8.6.7. PSA marks the start of operational testing. Operational testing will proceed for a 

minimum of 30 days during time issues shall be identified, and documented. 

8.7.Final System Acceptance 

8.7.1. A FSA meeting will be convened and chaired by the Purchaser when the Purchaser 

considers that all the required deliverables of the contract have been supplied by the 

Contractor and that all deficiencies identified at PSA have been rectified. 

8.7.2. The contractor shall verify and validate that all deficiencies identified during PSA 

operational testing have been corrected. 

8.7.3. FSA will be achieved following satisfactory completion of all of the requirements 

of the Contract consisting of at least the following: 

8.7.4. Inventory list: A deliverables inventory has been provided and verified by the 

Purchaser, which details all of the deliverables to be supplied under the terms of the 

Contract. 

8.7.5. As-Built Documentation: The Contractor shall provide As-Built Installation 

Drawings which reflect the entire installation. The documentation shall include a 

layout drawing that identifies the physical details of the installed equipment as per 

the SSS. 

8.7.6. The Contractor has provided Certificates of Conformity (CoC) that the equipment 

conforms to the regulatory standards defined in the Contract or otherwise legally 

required. 

8.7.7. The Purchaser has received all Contract deliverables including training. 

8.7.8. The Contractor has shown all equipment to be operational to SOW specifications 

upon delivery, and installation at HQ ISAF. 

8.7.9. The Contractor shall provide the Purchaser a FSA report stating that all items under 

this SOW have been completed. 



66/104



CO-13355-OPL 


SECTION 9: 

LIST OF SITES 

9.1.The CCTV HQ ISAF will be installed within the confines of the HQ ISAF compound. 

9.2.The following nominal locations for the proposed installations and the approximate 

dimensions of the HQ ISAF compound can be found at the following Annexes: 

9.2.1. Annex A: Acronyms 

9.2.2. Annex B: Proposed Camera Location Map HQ ISAF 

9.2.3. Annex C: Resilient IP network plan for CCTV 

9.2.4. Annex D: Notional Equipment Configuration Diagram 

9.2.5. Annex E: General Equipment Description 

9.2.6. Annex F: Approximate Dimensions of HQ ISAF Compound 

9.2.7. Annex G: Pole Lighting Standards 

9.2.8. Annex H: Poles Painting Standards 

9.2.9. Annex I: System Requirements Specification 

9.3.The final system configuration, including system locations and component numbers, will 

be agreed during the project site survey of HQ ISAF. 



67/104



CO-13355-OPL 




68/104



CO-13355-OPL 


ANNEX A: ACRONYMS 

ACO 

ACP 

ACT 

AEDC 

AIS 

AMSG 

AQAP 

AOC 

BDOC 

BSG 

CC 

CCB 

CDR 

CIS 

CI 

CLI 

CLIN 

CLS 

CM 

CMB 

CoC 

CONOPS 

COTS 

CPS 

CSA 

CSRS 

CSV 

DFAC 

EDC 

EMS 

ECP 

ESTO 

ESTP 

ESTR 

FAT 

FP 

FPR 

FSA 

Gym 

HQ 

HTML 

IATO 

ICAO 

ICD 

IFB 

ILS 

ILSP 

IOC 

IPMT 

Allied Command Operations 

Allied Communication Publication 

Allied Command Transformation 

After Effective Date of Contract 

Automated Information System 

Allied Military Security Guideline 

Allied Quality Assurance Publications 

Air Operations Centre 

Base Defence Operations Centre 

Base Support Group 

Common Criteria 

Configuration Control Board 

Critical Design Review 

Communication and Information Systems 

Configuration Items 

Command Line Interface 

Contract Line Item 

Contractor Logistic Support 

Configuration Management 

Configuration Management Board 

Certificate of Conformity 

Concept of Operations 

Commercial Off The Shelf 

Certification Practice Statement (only if the Project deals with PKI) 

Configuration Status Accounting 

Community Security Requirements Statement 

Comma Separated Value 

Dining Facility 

Effective Date of Contract 

Enterprise Management System 

Entry Control Point 

Equipment and System Test Objectives 

Equipment and System Test Procedures 

Equipment and System Test Report 

Factory Acceptance Tests 

Force Protection 

Formal Progress Report 

Final System Acceptance 

Gymnasium 

Headquarters 

Hypertext Mark-up Language 

Interim approval To Operate 

International Civilian Aviation Organisation 

Interface Control Document 

Invitation for Bid 

Integrated Logistics Support 

Integrated Logistics Support Plan 

Initial Operational Capability 

Integrated Project Management Team 



69/104



CO-13355-OPL 


ISAF 

LRU 

MIB 

MIL-STD 

MWA 

NATO 

NC3A 

NCSA 

NS WAN 

NPKI 

ORs 

O&M 

OT&E 

PA 

PBS 

PDF 

PDR 

PFD 

PFE 

PFP 

PIP 

PM 

PMP 

PMO 

PMS 

PRM 

PSA 

PTP 

QA 

QAP 

RAR 

ROM 

RSPL 

SAT 

SDS 

SHAPE 

SIP 

SISRS 

SIVP 

SOW 

SRS 

SSAT 

SSS 

SSR 

SSRS 

STANAG 

STP 

TBA 

TBD 

TT 

T & E 

WBS 

International Security and Assistance Force 

Line Replaceable Unit 

Management Information Base 

Military Standard 

Main Welfare Area 

North Atlantic Treaty Organisation 

NATO Consultation Command and Control Agency 

NATO Communications Services Agency 

NATO SECRET WAN 

NATO PKI (only if the project deals with PKI) 

Off-specification Reports 

Operation and Maintenance 

Operational Test & Evaluation 

Public Address 

Product Breakdown Structure 

Portable Document Format 

Preliminary Design Review 

Product Flow Diagram 

Purchaser-furnished equipment 

Purchaser-furnished property 

Project Implementation Plan 

Project Manager 

Project Management Plan 

Project Management Office 

Project Master Schedule 

Project Review Meeting 

Provisional Site Acceptance 

Project Test Plan 

Quality Assurance 

Quality Assurance Plan 

Risk Assessment Report 

Rough Order of Magnitude 

Recommended Spare Parts List 

Site Acceptance Tests 

System Design Specification 

Supreme Headquarters Allied Powers Europe 

System Implementation Plan 

System Interconnection Security Requirements Statement 

Security Implementation Verification Procedures 

Statement of Work 

System Requirements Specification 

Site and System Activation Testing 

Schedule of Supply and Services 

Site Survey Report 

System Security Requirements Statement 

Standards NATO Agreement 

Security Test Plan 

To Be Advised 

To Be Determined 

Technical Transfer 

Test and Evaluation 

Work Breakdown Structure 



70/104



CO-13355-OPL 




71/104



CO-13355-OPL 


ANNEX B: PROPOSED CAMERA LOCATION MAP HQ ISAF 

Cameras monitor all activity along the perimeter and entry points of HQ ISAF 

Satellite Imagery for this location available on Google Earth: 34º31’48.32”N 69º11’25.69”E 



72/104



CO-13355-OPL 


Type I Camera System 

5, 8, 10 

Type II Camera System 

3, 11, 12 

Type III Camera System 

1, 2, 4, 6, 7, 9, 13, 14, 15, 16 

NOTE: The term system denotes that additional assets may be required to meet the 

requirements as specified in the technical annex. 

NOTE: The above information specifies the area of coverage. Contractors shall 

develop low cost innovative designs that meet the requirement. 



73/104



CO-13355-OPL 


ANNEX C: NOTIONAL EQUIPMENT CONFIGURATION DIAGRAM 



74/104



CO-13355-OPL 


ANNEX D: EXAMPLE RESILIENT IP NETWORK PLAN FOR IP CCTV 



75/104



CO-13355-OPL 


ANNEX E GENERAL EQUIPMENT DESCRIPTION 

THIS SECTION INTENTIONALLY LEFT BLANK SEE APPENDIX I FOR TECHNICAL DESCRIPTION 



76/104



CO-13355-OPL 


ANNEX F: APPROXIMATE DIMENSIONS OF THE HQ ISAF COMPOUND 



77/104



CO-13355-OPL 


ANNEX G: POLES LIGHTING STANDARDS 

All poles lighting shall be installed according to Medium Intensity Type C lighting (steady red) as described in the table below. 

One or more low-, medium- or high-intensity obstacle lights shall be located as close as practicable to the top of the object. The top lights shall 

be so arranged as to at least indicate the points or edges of the object highest in relation to the obstacle limitation surface. 

All lights must be able to switch off using only one master switch located in the BDOC for compound security reasons. 



78/104



CO-13355-OPL 


Examples of marking and lighting of tall 

structures 



79/104



CO-13355-OPL 


ANNEX H: POLES PAINTING STANDARDS 

Painting shall be completed in accordance with the principles: 

Painting: Red – White – stripes paintings on them. The stripes shall be 1/7 of longest dimension (20/7=2.8m wide). The lower and the higher 

stripes should be red. 

Medium Intensity lighting 



80/104



CO-13355-OPL 


ANNEX I: SYSTEM REQUIREMENTS SPECIFICATION (SRS) 

I.1 General 

I.1.1 

I.1.1.1 

I.1.1.2 

I.1.1.3 

I.1.1.3.1 

I.1.1.3.2 

I.1.1.3.3 

I.1.1.3.4 

I.1.1.3.5 

I.1.1.3.6 

I.1.1.3.7 

I.1.2 

Scope of this Annex 

This Annex to the CCTV HQ ISAF SOW provides the minimum functional and technical requirements for the CCTV HQ ISAF. 

The requirements in the Annex are organised in six categories, as follows: 

System requirements; 

Functional Requirement; 

Operational Requirement; 

Technical Requirement; 

Security Requirement; 

Environmental Requirement; 

Physical Requirement; 

Remote administration, management requirement. 

System Requirements 

I.1.2.1 The Contractor shall design and implement a surveillance system including Cameras distribution systems, cabling Network and control 

elements. 



81/104



CO-13355-OPL 


I.1.3 

I.1.3.1 

I.1.3.1.1 

I.1.3.1.2 

Functional Requirements 

The enhanced IP CCTV HQ ISAF System shall meet the following functional requirements detailed below: 

Central control and operation of the IP CCTV HQ ISAF from the BDOC and ECP; 

Remotely controlled Pan Tilt Zoom (PTZ) controllers. 

I.1.3.1.3 Complete ground surveillance coverage of the perimeter and points of entry of HQ ISAF compound as shown at ANNEX A; 

I.1.3.1.4 

I.1.3.1.5 

I.1.3.1.6 

I.1.4 

I.1.4.1 

I.1.4.1.1 

Support for wide range of IP cameras and/or 3 rd party IP cameras 

Picture in Picture and Multiple monitor display of IP cameras 

Installation of retractable masts that are designed to last for a minimum of 10 years; 

Operational Requirements 

The enhanced IP CCTV HQ ISAF System shall meet the following operational requirements: 

Provide a Microsoft Windows based Operational & Maintenance GUI, application compatible with MS XP Pro, MS Vista, and MS 

Windows 7 operating 64 bit systems. 

I.1.4.1.1.1 User and device registration, administration 

I.1.4.1.1.2 Operational status display of CCTV components: network links’ status; network alarms, notifications; cameras’ status; CCTV system 

performance data; storage status 

I.1.4.1.2 

The server room equipment cabinets shall have sufficient cooling to support all equipment installed therein. 



82/104



CO-13355-OPL 


I.1.4.1.3 

I.1.4.1.4 

I.1.4.1.5 

I.1.4.1.6 

I.1.4.1.7 

I.1.4.1.8 

I.1.4.1.9 

The system shall be remotely configurable and controllable from the BDOC. 

The system shall be remotely controllable (PTZ) from ECP and BDOC installed digital keyboard, workstations; 

The system shall provide coverage in low light conditions. 

Have dual field of view thermal and daylight/lowlight capability. 

The system shall provide clear, high contrast imagery in total darkness, through smoke, and fog. 

The system shall provide camera coverage as specified in Annex B and allow for future expansion of up to twice the proposed 

cameras without system degradation; A camera subsystem contains all photo optical equipment required to achieve the capability. 

Audio and video recording synchronization where applicable (if there is voice input); 

I.1.4.1.10 The system shall provide 30 days of video storage capacity for the highest configured resolution of the cameras for the proposed 

solution; 

I.1.4.1.11 The system shall allow future expansion of cameras capable of both day, low light, and night vision; 

I.1.4.1.12 The system towers and masts shall conform to the International Civilian Aviation Organisation (ICAO) aerodrome marking 

requirements; 

I.1.4.1.13 The IP transport network shall be robust, resilient and has fast convergence between redundant links 

I.1.4.1.14 The system shall handle unclassified information only and is not expected to interface with any other NATO or non-NATO systems. 

I.1.4.1.15 The systems and its components shall meet the environmental requirements detailed in this document; 

I.1.4.1.16 The system components shall be maintained under a three (3) tier Operation & Maintenance (O&M) contract. 



83/104



CO-13355-OPL 


I.1.5 

I.1.5.1 

I.1.5.1.1 

I.1.5.1.2 

I.1.5.1.3 

I.1.5.1.4 

I.1.5.1.5 

I.1.5.2 

I.1.5.2.1 

I.1.5.2.2 

Technical Requirements 

Global requirement 

All network components, devices shall support AAA RADIUS settings 

All components shall have NTP server feature for system clock adjustment, setting 

All components shall be UPS protected. I.1.5.5.6 

All server and network equipments shall have dual power supply ( 1 connected directly to power and second one directly to UPS, this 

way UPS can be maintained without service disruption) 

Live viewing shall be supported on a variety of client platforms, including standard Internet browsers. 

External Equipment Requirements 

Be resistant to local environment as stipulated in section 4.2 and able to operate without any degradation 

Rugged ethernet cables for outdoor use which withstand: 

I.1.5.2.2.1 Cable pull to ensure proper strain relief (50 pounds) not loosing electrical connectivity; 

I.1.5.2.2.2 All cables shall be labelled and given adequate protection in accordance with NATO SPID-29 

I.1.5.2.3 

External cabinets 

I.1.5.2.3.1 Shall be capable housing 19” rackable devices 

I.1.5.2.3.2 Shall include a battery back-up power system (UPS) for equipments inside. 



84/104



CO-13355-OPL 


I.1.5.2.3.3 Shall have patch panel for fibre, copper cable support 

I.1.5.2.3.4 Shall have protection against EMI, and electrical surges 

I.1.5.2.3.5 External cabinets shall be robust and lockable to block unauthorised access 

I.1.5.2.3.6 Shall have EN1303 class. code 16-0-13 or equivalent lock 

I.1.5.2.3.7 Shall have earth bond strap on metal door 

I.1.5.2.3.8 Operating temperature for the external box install shall be inline with section 4.2. 

I.1.5.2.4 

Ethernet switch requirements 

I.1.5.2.4.1 Shall be remotely manageable, controllable and be either CISCO or 3COM. CISCO and 3COM are the 2 types of routers and 

switches authorized for use in ISAF. 

I.1.5.2.4.2 Shall have RADIUS centralized password management 

I.1.5.2.4.3 Shall have Web based management, Command Line Interface (CLI) capability 

I.1.5.2.4.4 Shall be remotely manageable, controllable 

I.1.5.2.4.5 Shall have RADIUS centralized password management 

I.1.5.2.4.6 Support user authentication 

I.1.5.2.4.7 Shall have Web based management, Command Line Interface (CLI) capability 



85/104



CO-13355-OPL 


I.1.5.2.4.8 Shall support IP v4, v6 (unicast, multicast); shall comply with the NATO Policy on the Internet Protocol Version 6 (IPv6) AC/322- 

D(2007)0039 

I.1.5.2.4.9 Shall support SSHv2, SNMPv1,v2,v3, IGMPv1/v2, NTP,FTP,TFTP 

I.1.5.2.4.10 Shall have port enable/disable capability, MAC address restriction 

I.1.5.2.4.11 Shall have port rate, broadcast storm limiting 

I.1.5.2.4.12 Shall have logging, alarm, status and watchdog capability 

I.1.5.2.4.13 Shall support 802.1x,802.1Q,802.1p,STP,RSTP 

I.1.5.2.4.14 Shall support dynamic VLAN configuration protocol(VTP/GVRP/MVRP) 

I.1.5.2.4.15 Shall have dual power supply. 

I.1.5.2.4.16 Shall support IP v4, v6; shall comply with the NATO Policy on the Internet Protocol Version 6 (IPv6) AC/322-D(2007)0039 

I.1.5.2.4.17 Shall support SSHv2, SNMPv1,v2,v3, IGMPv1/v2, NTP, FTP, TFTP 

I.1.5.2.4.18 Shall comply with the NCIRC-TC guidance for hardening CISCO Switches used on NATO networks version 1.3 of 25 Nov 2010 

I.1.5.2.4.19 Shall comply with the NCIRC-TC guidance for hardening CISCO routers used on NATO networks version 1.3 of 05 Mar 2009 

I.1.5.2.4.20 Shall support dynamic VLAN configuration protocol(VTP/GVRP/MVRP) 



86/104



I.1.5.2.4.21 Shall have a minimum IP65 certification (temporary immersion of dust and water) or the external housing shall have IP65 

certification for outdoor operational usage and a minimum IP55 certification for indoor use. 

I.1.5.2.4.22 Shall have an operational availability of 99.9%. 

CO-13355-OPL 


I.1.5.2.5 

Masts 

I.1.5.2.5.1 The Contractor shall be responsible for purchasing, delivering and installing the all required masts and ancillary equipment. 

I.1.5.2.5.2 Masts shall be adjustable to a height of 15m. 

I.1.5.2.5.3 Masts shall be able to withstand the continuous wind load conditions applicable to the environmental conditions in Kabul, 

Afghanistan. 

I.1.5.2.5.4 Masts shall have a self-powered obstruction light fitted that meets the requirements of the ICAO. (See Annex G: Poles lighting 

standards)The mast shall be of the retractable type (foldable, telescopic, etc) to avoid climbing. It shall be able to be lowered by 

mechanical means (pulley system, etc) to facilitate routine maintenance without the need of cherry pickers, ladders, etc. Due to the 

environmental and climatic conditions of Afghanistan, hydraulic systems shall not be implemented for the CCTV project. The 

system shall be considered fixed 

I.1.5.2.5.5 Shall include mountings for the external equipment control cabinets. 

I.1.5.2.5.6 There shall be two types of mast provided for this project: 

I.1.5.2.5.6.1 Type 1 mast: Overhangs the perimeter wall by 5 meters and retracts within ISAF HQ for maintenance without the need for a 

Cherry Picker or ladder 

I.1.5.2.5.6.2 Type 2 mast: Vertical mast that retracts for maintenance with the need of cherry pickers or ladders. 



87/104



CO-13355-OPL 


I.1.5.2.5.7 Type 1 and Type 2 masts shall be able to support a minimum of 3 cameras to include the capability to provide sufficient emergency 

power to all cameras and supporting equipment in accordance with reference I.1.4.5.6 Uninterruptible Power Supply to ensure an 

inherent operational availability of 99.9%.. 

I.1.5.2.5.8 Painting shall then be according to ICAO Doc 9157 Part 4 Chapter 14 as described at Annex H. 

I.1.5.2.5.9 Camera Stanchion Requirement: 

I.1.5.2.5.9.1 Obstacle Light 

I.1.5.2.5.9.1.1 Medium-Intensity Type C 

I.1.5.2.5.9.1.2 Red Fixed Signal Light ANNEX G 

I.1.5.2.5.9.1.3 Vertical Beam Spread 3º min 

I.1.5.2.5.9.1.4 Minimum Intensity 2000 candelas + 25% 

I.1.5.2.5.10 Pole Painting Standard 

I.1.5.2.5.10.1 Red & White stripe marking band ANNEX H 

I.1.5.2.5.11 Retractable 

I.1.5.2.5.11.1 Supports maintenance without the need of a cherry picker or extension ladder 

I.1.5.2.5.11.2 Can be ground or wall mountable 

I.1.5.2.5.12 Outdoor box/cabinet for 



88/104



CO-13355-OPL 


I.1.5.2.5.12.1 Fiber, copper patch panel, cable support 

I.1.5.2.5.12.2 Robust Ethernet switch 

I.1.5.2.5.12.3 UPS which supports both Camera, switch and Stanchion lighting 



89/104



CO-13355-OPL 


. 

I.1.5.2.6 

Cameras 

I.1.5.2.6.1 Following cameras performance requirements shall be met: 

I.1.5.2.6.1.1 20 X optical zoom 

I.1.5.2.6.1.2 Pan speed 90 degree / sec 

I.1.5.2.6.1.3 Minimum 15 fps 

I.1.5.2.6.1.4 Minimum 1.3 Megapixel (1280X1024) for the fix view 60 degree view angle 

I.1.5.2.6.1.5 Minimum 2.0 or 3.2 Megapixel (4X 800x600) for the 180 degree view angle PTZ 

I.1.5.2.6.1.6 Thermal resolution 320x240, 640x480 with PTZ 

I.1.5.2.6.1.7 shall have ruggedized, robust enclosur 

I.1.5.2.6.1.8 Cameras shall have sunshield 

I.1.5.2.6.1.9 Have M-JPEG,H.264,MPEG-4 stream format and jpeg snapshot capability 

I.1.5.2.6.1.10 Have IPv4 and IPv6 protocol support 

Figure 2 Notional depiction of a possible camera stantion 

I.1.5.2.6.1.11 Have user authentication support 



90/104



CO-13355-OPL 


I.1.5.2.6.2 All CCTV camera systems shall: 

I.1.5.2.6.2.1 Be resistant to local environment (see paragraphs 2.2.1.10, 4.2). 

I.1.5.2.6.2.2 Be delivered in rugged Pan/Tilt/Zoom (PTZ) enclosure. 

I.1.5.2.6.2.3 Be provided with pole mounting adapter. 

I.1.5.2.6.2.4 Be remotely controlled. 

I.1.5.2.6.2.5 Have a ‘snapshot’ capability 

I.1.5.2.6.2.6 Allow situation awareness through a wide angle capability. 

I.1.5.2.6.2.7 Have dual field of view and daylight/lowlight capability using existing technology such as Infrared Night Vision. 

I.1.5.2.6.2.8 Provide clear, high contrast imagery in total darkness, through smoke, and fog using existing technology such as Thermal vision 

capability. 

I.1.5.2.6.2.9 Be packaged in a rugged, precision PTZ enclosure that can slew at up to a minimum 90 degrees per second for type I and type II 

camera systems. 

I.1.5.2.6.2.10 Support network operations under IP v4 and v6 

I.1.5.2.6.2.11 Be remotely configurable 

I.1.5.2.6.2.12 Shall be Open Network Video Interface Forum (ONVIF) compliant and STANAG 4586 

I.1.5.2.6.2.13 Support for centralised user authentication 



91/104



CO-13355-OPL 


I.1.5.2.6.3 Type 1 CCTV cameras shall: 

I.1.5.2.6.3.1 Have a long range capability that can detect a man sized target at 500 m, and read a license plate at 200 m. 

I.1.5.2.6.3.2 Have auto-pivot and auto-scaling capability. 

I.1.5.2.6.3.3 Have a 360º degrees vision capability. 

I.1.5.2.6.3.4 Have motion tracking capability. 


I.1.5.2.6.4.1 Have a range capability that can detect facial features at 100 m. 

I.1.5.2.6.4.2 Have a 180 deg. pan capacity. 

I.1.5.2.6.4.3 Have motion tracking capability. 


I.1.5.2.6.5.1 Be of the fixed type – no pan required 

I.1.5.2.6.5.2 Have a range capability that can detect facial features at 10 m (horizontal distance from mast). 

I.1.5.2.6.5.3 Be able to continually monitor an area of 100 m2. 

I.1.5.3 

I.1.5.3.1 

Entry Control Points. 

IP matrix video switch component 

I.1.5.3.1.1 Shall drive the COP display wall of LCD screens at ECP 



92/104



CO-13355-OPL 


I.1.5.3.1.2 Shall support minimum two (2) Type II LCD screens 

I.1.5.3.2 

Common Operational Picture (COP) display wall shall have: 

I.1.5.3.2.1 The video wall shall contain two (2) Type 2 monitors and one video controller to allow the watchkeepers to clearly view imagery 

from multiple cameras simultaneously and zoom in on areas of interest to the highest resolution. Refer to I.1.5.4.5.6 Visualization 

monitors 

I.1.5.3.2.2 Live view of all ECP area camera feeds on the LCD screens 

I.1.5.3.2.3 The video wall setup shall have an easily customizable layout configuration manager (drag & drop, move or relocate, click to select 

zoom setup) 

I.1.5.3.2.4 COP display shall incorporate a overall status of the system I.1.4.1.1.2 

I.1.5.3.2.5 The Entry Control Point location(s) shall have a remote capability to control cameras (PTZ) within the vicinity of the gate (via Video 

Management Client and/or PTZ keyboard) 

I.1.5.3.2.6 The master control station shall remain the BDOC which shall have override authority 

I.1.5.3.2.7 The ECP shall have an visual indication when the BDOC overrides 

I.1.5.3.3 

Video Management Client ( workstation application UI ) shall have: 

I.1.5.3.3.1 manual bookmarking feature where the operator can create searchable tags with descriptions and send references via email to 

recipients 

I.1.5.3.3.2 timeline, scrub bar, thumbnail search features 

I.1.5.3.3.3 multiple channel (archive) search and simultaneous (synchron) playback of selected video files, cam feeds 



93/104



CO-13355-OPL 


I.1.5.3.3.4 manual function to run, execute analytics on selected feed 

I.1.5.3.3.5 Support user authentication I.1.5.5.5 

I.1.5.4 

I.1.5.4.1 

I.1.5.4.2 

Base Defence Operating Centre 

The operating centre equipment shall provide the control elements of the system in accordance with the following requirements: 

IP matrix video switch component 

I.1.5.4.2.1 Shall drive the COP display wall of LCD screens at BDOC 

I.1.5.4.2.2 Shall support minimum three (3) Type I LCD screens 

I.1.5.4.3 

Common Operational Picture (COP) display wall shall have: 

I.1.5.4.3.1 The video wall shall contain three (3) Type I LCD screens to allow the watch keepers to clearly view imagery from multiple cameras 

simultaneously and zoom in on areas of interest to the highest resolution 

I.1.5.4.3.2 Live view of all camera feeds on the LCD screens 

I.1.5.4.3.3 The video wall setup shall have an easily customizable layout configuration manager (drag & drop, move or relocate, click to select 

zoom setup) 

I.1.5.4.3.4 COP display shall incorporate a overall status of the system I.1.4.1.1.2 

I.1.5.4.4 

I.1.5.4.5 

The BDOC shall have a remote capability to control all cameras in the network via 2 watchstander consoles (utilizing Video 

Management Client and/or PTZ keyboard) . 

Video Management Client ( workstation application UI ) shall have: 



94/104



CO-13355-OPL 


I.1.5.4.5.1 Manual bookmarking feature where the operator can create searchable tags with descriptions and send references via email to 

recipients 

I.1.5.4.5.2 Timeline, scrub bar, thumbnail search features 

I.1.5.4.5.3 Multiple channel (archive) search and simultaneous (synchronize) playback of selected video files, cam feeds 

I.1.5.4.5.4 Manual function to run, execute analytics on selected feed 


I.1.5.4.5.6 The Visualization Monitors 

I.1.5.4.5.6.1 

Type 1 monitors 

I.1.5.4.5.6.1.1 46-inch monitor minimum 

I.1.5.4.5.6.1.2 Shall be able to view at least six (6) cameras on each monitor 

I.1.5.4.5.6.2 Type 2 monitors 

I.1.5.4.5.6.2.1 24 inch monitors 

I.1.5.4.5.6.2.2 Shall be able to simultaneously view four (4) imagery / video from a minimum of cameras simultaneously on each monitor. 

I.1.5.4.5.6.3 Shall possess Dual camera control 

I.1.5.4.5.6.3.1 Shall be able to manipulate PTZ for all cameras 

I.1.5.4.5.6.3.2 The keyboard controls shall be fully redundant and provide the ability to take control of each monitor display. 



95/104



CO-13355-OPL 


I.1.5.4.5.6.4 Monitors to display 

I.1.5.4.5.6.4.1 Video wall shall display permanent display of all camera feeds 

I.1.5.4.5.6.4.2 Selective display for feed from specific camera(s) of interest 

I.1.5.4.5.6.5 Digital Keyboard Control (Pan Tilt Zoom Controller): 

I.1.5.4.5.6.5.1 The keyboard controls shall be fully redundant and provide the ability to take control of each monitor display 

I.1.5.4.5.6.5.2 Each keyboard shall be delivered with a variable speed joystick 

I.1.5.4.5.6.6 Cabling 

I.1.5.4.5.6.6.1 High quality shielded cabling shall be used that is suitable for the environment for which it shall be used. Refer to Section 4.2 for 

environmental and climatic conditions for cabling that shall be exposed to the elements. 

I.1.5.4.5.6.6.2 Shall be properly labelled at each end (origin and termination points) in accordance with AC_35-D_1016-REV1 

I.1.5.4.5.6.6.3 Shall be properly crimped 

I.1.5.4.5.6.6.4 Shall adhere to standard cabling guidelines 

I.1.5.4.5.6.6.5 Shall be managed responsibly with with a cable management system e.g. cabling must be secured and positioned neatly to 

facilitate proper maintenance. 

I.1.5.4.5.6.6.6 

I.1.5.5 

Technical Centre. 



96/104



CO-13355-OPL 


I.1.5.5.1 

The Technical Centre server room shall house the IP CCTV HQ ISAF system control hardware in accordance with the 

following requirements 

I.1.5.5.1.1 Equipments shall provide remote control, management capability 

I.1.5.5.1.2 Equipments shall be manageable from local console ( KVM, LCD in rack) 

I.1.5.5.1.3 42U high equipment cabinet rack(s) to mount system control equipment (19 inch standard) 

I.1.5.5.1.4 Rack(s) shall have fibre and copper cable patch panels and cable supporters; 

I.1.5.5.1.5 All rack elements shall be corrosion-resistant; 

I.1.5.5.1.6 Racks shall have sufficient cooling or fan installation to support installed components; 

I.1.5.5.1.7 Power outlet installation is European standard and power rate is 230 V; 

I.1.5.5.1.8 Rack(s) shall have a rack mountable UPS device(s) for the CCTV System components. 

I.1.5.5.2 

NTP time server 

I.1.5.5.2.1 System shall have a NTP server with GPS (stratum 0) time source 

I.1.5.5.2.2 NTP server shall support NTPv3 and NTPv4 

I.1.5.5.3 

DNS service 

I.1.5.5.3.1 The system shall have a DNS service 

I.1.5.5.3.2 All devices shall be registered in DNS zone(s) of system domain 



97/104



CO-13355-OPL 


I.1.5.5.4 

RADIUS service 

I.1.5.5.4.1 The system shall have a centralized RADIUS authentication service for the network devices 

I.1.5.5.5 

User authentication service 

I.1.5.5.5.1 The system shall have a centralized user authentication service for the IP CCTV system and its components 

I.1.5.5.6 

Uninterruptible Power Supply (UPS). 

I.1.5.5.6.1 All components shall be protected by real-time UPS. 

I.1.5.5.6.2 UPS power backup for 30 minutes and shall be expandable to 60 minutes timeframe with additional battery pack module; 

I.1.5.5.6.3 The UPS shall be On-Line double conversion technology (AC/DC/AC) with zero time transfer 

I.1.5.5.6.4 The UPS shall have Harmonic distortion of less than 5% Total Harmonic Distortion (THD) 

I.1.5.5.6.5 The batteries shall be of sealed maintenance free type, replacement of the batteries shall be possible without powering down the UPS. 

I.1.5.5.6.6 UPS shall provide remote power monitoring capability from BDOC; 

I.1.5.5.7 

Network Video Recorder (NVR) System 

I.1.5.5.7.1 IP CCTV System shall have a dual, redundant NVR recorder setup; 

I.1.5.5.7.2 Shall have a minimum of one (1) month recording capability for the entire CCTV network. 

I.1.5.5.7.3 NVR Servers shall have dual power supply 

I.1.5.5.7.4 Shall have minimum 3 Gigabit Ethernet interfaces (1 management, 2 network connectivity) 



98/104



CO-13355-OPL 


I.1.5.5.7.5 Shall have internal or external RAID 5 storage or storage cluster (with gigabit interfaces). External storage server shall have dual 

power supply. 

I.1.5.5.7.6 Recording capability ( video channels ) shall meet the number of cameras of the Contractor’s system design ( containing extension ) 

I.1.5.5.7.7 Shall support M-JPEG,H.264,MPEG-4 stream format and jpeg snapshot recording capability 

I.1.5.5.7.8 Shall support IP v4 and v6, (unicast, multicast) 

I.1.5.5.7.9 Shall support multiple client platform for streaming 

I.1.5.5.7.10 Shall support transfer of recorded archived data via optical media (CD and DVD), HDD, Secure USB thumb drive, and network 

drive. 


I.1.5.5.8 

NVR management application shall support the following requirements: 

I.1.5.5.8.1 Record continuously all camera feeds 

I.1.5.5.8.2 Search recorded camera files 

I.1.5.5.8.3 View, replay camera files 

I.1.5.5.8.4 Digital zoom 20X 

I.1.5.5.8.5 Remote search and replay on workstation for authenticated user 

I.1.5.5.8.6 video analytics facial, license plate recognition integration 



99/104



CO-13355-OPL 


I.1.5.5.8.7 backup camera files to USB,DVD, Network media 

I.1.5.5.8.8 free space requirement calculation for camera setup 

I.1.5.5.8.9 time stamps for video feeds 

I.1.5.5.9 

Video Management Software (VMS) shall have: 

I.1.5.5.9.1 Virtual desktop environment, predefined work area with saved positions of application windows 

I.1.5.5.9.2 Integration with NVR, analytics, authentication 

I.1.5.5.9.3 Support 64 cameras, camera setup, configuration 

I.1.5.5.9.4 Support 3 rd party cameras and Network Video Recorder servers 

I.1.5.5.9.5 Support analytics software (facial, licence plate) 

I.1.5.5.9.6 ONVIF compliance 

I.1.5.5.9.7 Timeline, scrub bar, thumbnail search features 

I.1.5.5.9.8 Archive video export utility (to USB stick and HDD, CD,DVD) 


I.1.5.5.9.10 Capability to control, monitor and assign rights to CCTV HQ operators, clients (Video Management Clients). The master control 

station shall remain the BDOC which shall have override authority for operations. 

I.1.5.5.10 Distribution and access switches 



100/104



CO-13355-OPL 


I.1.5.5.10.1 Shall meet the requirements set forth in I.1.2.5.4 

I.1.5.6 

Connectivity 

I.1.5.6.1 The Contractor shall be responsible for the cabling between each camera/mast system and the ECP, BDOC, and technical centre. 

Where possible, the contractor shall utilise the installed site-wide cable infrastructure accessed through existing distribution nodes. 

I.1.5.6.2 It is estimated that the distance between camera placement and the nearest existing ducting is < 50m. 

I.1.5.6.3 The contractor shall utilize existing ducting, cabling and patch panels to the greatest extent possible to connect the CCTV system. 

Existing installed cabling is predominantly multimode fibre (50um) with SC connector patch panels, however a limited number of 

distribution nodes have only single-mode fibre connectivity. 

I.1.5.6.4 The contractor shall ensure that all cables are properly secured and labelled at both termination points to facilitate ease of 

maintenance. Cable labelling shall follow best commercial practice, and inline with the cable labelling standards already in use at 

HQ ISAF. 

I.1.5.6.5 The contractor shall ensure that all cabling is properly shielded and crimped. No copper or fiber shall be exposed to the 

environment. 

I.1.5.6.6 The contractor shall take appropriate precautions to minimize the build up of dust and other debris within or between devices and 

associated equipment. All cabling to/through external devices shall be hermetically sealed to prevent dust or debris build up in 

cabinets and boxes. 

I.1.5.6.7 The contractor shall ensure that run off drains are properly installed to prevent/minimize water collection on the equipment or at the 

based of support structures such as mast. 

I.1.5.6.8 The delivered as-built documentation shall include full details of all cabling installed. 



101/104



CO-13355-OPL 


I.1.5.6.9 

Any needed connectivity between the supporting technical equipment and main connectivity patch panels shall be the Contractor’s 

responsibility e.g. where possible existing infrastructure can be used. 

I.1.5.6.10 The Contractor shall connect each camera system to the facility power. 

I.1.5.7 

I.1.5.7.1 

I.1.5.7.2 

I.1.5.8 

I.1.5.8.1 

I.1.5.8.2 

I.1.5.9 

I.1.5.9.1 

I.1.6 

I.1.6.1 

Performance 

IP transport network shall support all quality video feeds without interruption and frame loss, gigabit speed 

NVR system and storage shall be capable handling, recording all parallel IP camera streams, searching and replaying and analyze 

(facial, licence plate recognition) video files within set, specified recorded timeframes. 

Scalability and Sizing 

The system shall be scalable and it shall allow future expansions. The Contractor shall specify the maximum number IP cameras 

subsystems (such as additional Type I, Type II, and Type III cameras within the boundaries or the perimeter of HQ ISAF) the 

delivered system can handle without further investment and expansion of the core components; 

Contractor shall describe, document the delivered system scalability and feature set; 

Mobility. 

All cameras shall be installed on retractable masts. A retractable mast is a mast that can be lowered by mechanical means (e.g. 

hydraulics, pulley system, etc) to facilitate routine maintenance without the need of cherry pickers, ladders, etc. The system is 

considered fixed. 

Security Requirements 

Classification 



102/104



CO-13355-OPL 


I.1.6.1.1 

I.1.6.1.2 

I.1.7 

The CCTV HQ ISAF shall process unclassified video data only and shall be controlled, managed by the BDOC. Archived data of 

interest may be transferred from the NVR download terminal onto optical media for further analysis and reclassification. 

Capability from this SOW shall meet NATO Security and Information Security (INFOSEC) directives and policies per section 

2.1.1.3.6 and AC/322-D/0030 – Rev 5, and AC/35-D/2005 Rev 2. 

Environmental and Climatic requirements 

I.1.7.1 Refer to section 4.2 

I.1.8 

I.1.8.1 

I.1.8.2 

I.1.8.3 

I.1.8.4 

I.1.8.5 

I.1.8.6 

I.1.8.7 

I.1.8.7.1 

Remote administration, management requirement 

The system shall have a management application to configure, administrate the IP CCTV System (server – client model) 

The management application shall provide remote access for the clients 

The system shall support management clients on additional remote locations over the IP network (with strict access rules as limited IP 

address access, limited user access, ...) 

Remote management client shall have to work through WAN environments (typically available bandwidth in theatre is 1Mbit/s to E3 

line but as shared bandwidth) 

Remote management client shall work over typical one satellite hop connection (300ms one way delay) 

Management application shall support the following protocols, data types, management objects: 

HTTPS, TLS 

SSHv1,SSHv2 



103/104



CO-13355-OPL 


I.1.8.7.2 

I.1.8.7.3 

I.1.8.7.4 

I.1.8.7.5 

I.1.8.8 

I.1.8.8.1 

I.1.8.8.2 

I.1.8.8.3 

I.1.8.8.4 

I.1.8.8.5 

I.1.8.8.6 

I.1.8.8.7 

I.1.8.8.8 

I.1.8.8.9 

SNMPv1, SNMPv2,SNMPv3 

related data types ASN.1, SMI (Structure of Management Information) 

MIB, MIB II (Management Information Base) 

vendor provided MIB files 

Management application(s) shall be able: 

Load and use vendor provided MIB files 

Poll, collect performance data from the IP CCTV network devices, elements (switches, routers, IP cams, servers, storage) 

Display IP CCTV System visual network map with the components and their status (with colour codes e.g.: green, yellow, red as 

service status OK, DEGRADED, FAILED) 

Handle, process SNMP Trap messages, alarms, notifications 

Log and display events 

Forward, send SNMP traps, events to other management system 

Integrate external management application into its GUI interface (e.g: a management application or web interface of a specific 

network component shall be executed, called from the GUI menu) 

Provide configuration management functionality for network elements ( labelled, tagged, branched versions of configuration files) 

Support user authentication I.1.5.5.5 



104/104

From: Subject: References Dear Bidders, N ATO UNC LA SSIF IE D ...

Create successful ePaper yourself

Delete template?

Save as template?