nnhq - anwi

NATO UNCLASSIFIED 

IFB-CO-13300-ANWI-AMD-2 

NATO COMMUNICATIONS AND INFORMATION 

AGENCY 

INVITATION FOR BID 

IFB-CO-13300-ANWI 

NEW NATO HEADQUARTERS 

ACTIVE NETWORK INFRASTRUCTURE 

(NNHQ ANWI) 

BOOK I 

INSTRUCTIONS TO BIDDERS 

VERSION 03 

(issued under IFB Amendment No.2) 

Book I, Page I-1 

NATO UNCLASSIFIED



TABLE OF CONTENTS 

SECTION 1 INTRODUCTION 4 

1.1. Purpose 4 

1.2. Scope 4 

1.3. Overview of the Prospective Contract. 6 

1.4. Governing Rules, Eligibility, and Exclusion Provisions 9 

1.5. Security 10 

1.6. Bidders Conference 10 

1.7. Documentation 12 

SECTION 2 GENERAL BIDDING INFORMATION 13 

2.1. Definitions 13 

2.2. Eligibility and Origin of Equipment and Services 14 

2.3. Bid Delivery and Bid Closing 14 

2.4. Requests for Extension of Bid Closing Date 15 

2.5. Purchaser’s Point of Contact 16 

2.6. Request for IFB Clarifications 16 

2.7. Requests for Waivers and Deviations 17 

2.8. Amendment of the Invitation for Bid 18 

2.9. Modification and Withdrawal of Bids 18 

2.10. Bid Validity 19 

2.11. Bid Guarantee 19 

2.12. Cancellation of Invitation for Bid 21 

2.13. Electronic Transmission of Information and Data 21 

2.14. Supplemental Agreements 22 

2.15. Notice of Limitations on Use of Intellectual Property Delivered to the 

Purchaser 22 

2.16. Mandatory Quality Assurance and Quality Control Standards 23 

SECTION 3 BID PREPARATION INSTRUCTIONS 24 

3.1. General 24 

3.2. Bid Package Content 25 

3.3. Package Marking 25 

3.4. Bid Administration Package 26 

3.5. Price Quotation 27 

3.6. Technical Proposal Package 29 

SECTION 4 BID EVALUATION AND CONTRACT AWARD 40 

4.1. General 40 

4.2. Best Value Award Approach and Bid Evaluation Factors 41 

4.3. Evaluation Procedure 42 

4.4. Evaluation Step 1 - Administrative and Contractual Compliance 43 

4.5. Evaluation Step 2 - Technical Evaluation 45 

4.6. Evaluation Step 3 - Price Evaluation 55 

4.7. Evaluation Step 4 – Calculation of Best Value Scores 58 

Annex A Bidding Sheets 1 

Annex B Prescribed Administrative Forms and Certificates 1 


NATO UNCLASSIFIED



Annex C Bid Guarantee - Standby Letter of Credit 1 

Annex D Clarification Request Form 1 


NATO UNCLASSIFIED



SECTION 1 

INTRODUCTION 

1.1. Purpose 

1.1.1. The purpose of this solicitation is to invite Bids for the provision of 

equipment and services to implement and support the New NATO 

Headquarters Active Network Infrastructure (ANWI) and to provide ANWI 

Integration Test Services (ITS) as per Part IV - Statement of Work and in 

accordance with Part I - Schedule of Supplies and Services. 

1.2. Scope 

1.2.1. The NATO Communications and Information Agency (NCI Agency, 

NCIA), as designated Host Nation responsible for the implementation of 

the New NATO Headquarters (NNHQ) Active Network Infrastructure 

(ANWI) is authorized to award a Contract to a ANWI Implementation 

Contractor (hereinafter referred to as “ANWI Contractor”). 

1.2.2. The delivery of the NNHQ requires a number of different elements 

supporting the various aspects to deliver a working facility. 

1.2.3. The Headquarters Programme Office (HQPO) has overall responsibility 

for the delivery of the NNHQ Programme including the migration of 

systems and services from the current to the NNHQ in support of NATO 

HQ’s planned business functions for 2015 and beyond. In order to 

achieve this, three Host Nations (HNs) have the responsibility of 

executing the necessary projects to deliver a fully functional New NATO 

Headquarters ICT capability. 

1.2.4. HN Belgium will deliver the building and the following building related ICT 

systems and facilities: 

1.2.4.1. its Building Management System (BMS); 

1.2.4.2. its Electronic Security Systems (ESS); 

1.2.4.3. the integrated audio-visual equipment (AVI); 

1.2.4.4. the passive network cabling (PNWI). 

1.2.5. Host Nation Executive Management - Information Communications 

Technology Management (HN EM-ICTM) will migrate their business 

applications, services and data to the ANWI. 

1.2.6. HN NCIA is responsible for delivering the new NATO Headquarters’ 

ANWI which will provide: 


NATO UNCLASSIFIED



1.2.6.1. Infrastructure capabilities (processing, storage) for four security 

domains (NATO SECRET, NATO Business (up to NATO 

RESTRICTED), Euro-Atlantic Partnership Council (EAPC) SECRET, 

and Public/NATO UNCLASSIFIED); 

1.2.6.2. Wired and Wireless LAN switching capabilities for four security 

domains, installed and integrated with building and cabling 

infrastructure; 

1.2.6.3. Communications capabilities consisting of the HQs’ telephone services, 

Video Teleconferencing, site security communications, IPTV services, 

GSM services; 

1.2.6.4. End-user equipment; 

1.2.6.5. Core information services; 

1.2.6.6. Cross domain capabilities to support external networks interconnection 

and information services interoperability services; 

1.2.6.7. Coordination and integration of the ANWI capability with systems/ 

services external to the ANWI scope; 

1.2.6.8. Migration of ANWI identified services from the current building to the 

NNHQ building and support to migration of business applications; 

1.2.6.9. ANWI Integration Test Services (ITS) offers a base-lined reference suite 

of functions that all new building Host Nations will use to test their 

capabilities prior to deployment in the new building. 

1.2.7. HN NCIA will achieve the ANWI scope by means of three different types 

of activities: 

1.2.7.1. Procurement of ANWI functions and services through a primary 

Contract resulting from International Competitive Bid (ICB); 

1.2.7.2. Procurement of ANWI functions, on a sole source basis, from existing 

NATO wide services/systems that will be provided to the ANWI 

Contractor as PFE; 

1.2.7.3. Act as the implementation and design authority for integration of ANWI 

systems and services into NATO wide communication and information 

services. 


NATO UNCLASSIFIED



1.3. Overview of the Prospective Contract. 

1.3.1. ANWI services will be provided to 4,500 users (Staff and Delegations) of 

the New NATO Headquarters (NNHQ) and a subset of services will also 

be available to up to 1,500 conference visitors. 

1.3.2. The ANWI capability will support four different security domains, as 

detailed in 1.2.6.1. 

1.3.3. ANWI Services consist of the following: 

1.3.3.1. Infrastructure Services 

1.3.3.1.1. Processing Services: Spread across two server rooms and four 

classifications, providing high available processing power over a 

scalable and flexible environment for NNHQ ICT functions, taking 

advantage of virtualization technologies; 

1.3.3.1.2. Storage Services: Spread across two server rooms and four 

classifications, providing a high available central storage capability 

and a storage network for NNHQ ICT functions as well as supporting 

the storage requirements for ESS, BMS and AVI; 

1.3.3.1.3. Network Infrastructure Services: A set of services to support the 

NNHQ ICT systems, such as DHCP, DNS, Authentication, Time 

Services, etc.; 

1.3.3.1.4. LAN Services: Wired and Wireless connectivity spread across the 

NNHQ campus for four classifications (Wireless only available for 

NATO RESTRICTED or below classifications), including server room 

active network components and the access layer network 

components; 

1.3.3.1.5. Infrastructure Information Assurance (IA) Services (including Cross 

Domain Services): The subset of overall IA Services for NNHQ, 

related to the Infrastructure Services spread across four 

classifications, such as firewalls, IDS/IDP devices, security agents 

running on servers. Additional Gateway (GW) services will be 

provided to achieve secure controlled cross domain connectivity 

using technologies such as proxies, specific guards and diodes. 

1.3.3.2. Unified Communications and Collaboration (UCC) Services 

1.3.3.2.1. Email: Email services; 

1.3.3.2.2. IM: Instant Messaging Services; 


NATO UNCLASSIFIED



1.3.3.2.3. Voice: Voice Communication Services through dedicated devices 

and/or software clients; 

1.3.3.2.4. Video: Video Communication Services through dedicated devices 

and/or software clients; 

1.3.3.2.5. Presence: Presence Services; 

1.3.3.2.6. Collaboration: Collaboration Services such as screen / window 

sharing, white boarding, collaborative editing; 

1.3.3.2.7. UCC Integrated Session Management: Integrating session 

management services for the above mentioned individual services 

under a single UCC management capability; 

1.3.3.2.8. UCC IA Services: UCC Specific IA Services, such as anti-spam, 

email AV, IM AV, content scanning. 

1.3.3.3. Client Provisioning Services 

1.3.3.3.1. Client Devices: Various client hardware form factors to be provided 

for different classifications / different user groups (such as desktop 

and portable computers, tablet devices, PDAs, VoIP and VoSIP 

phones, dedicated VTC devices, printers, scanners). Current scope 

does not include the provisioning of GSM phones to users, but these 

devices may be able to reach a subset of ANWI services based on 

the security and functional requirements; 

1.3.3.3.2. Software Provisioning: Provisioning of client software and integration 

with Purchaser furnished software. This includes establishing the 

software provisioning infrastructure in a centrally managed but 

flexible way to enable provisioning of OS and applications which will 

include Purchaser Furnished software (such as NATO Desktop 

Baseline), existing functional applications and any other applications 

in support of the overall client functionality; 

1.3.3.3.3. User workspace provisioning and management to provide support to 

multiple form factor devices; 

1.3.3.3.4. Integration of client workspace services with application services 

provisioning; 

1.3.3.3.5. Client Provisioning IA Services: Client specific IA services such as 

client side AV, client firewall software 

1.3.3.4. ANWI Supplementary Services 


NATO UNCLASSIFIED



1.3.3.4.1. GSM: The GSM service will allow the commercial GSM Network 

Operators (MNO) operating in Belgium to provide services to the 

users throughout the NNHQ Campus; 

1.3.3.4.2. GSM Blocking: Capability to block GSM signals in specific parts of 

the campus for a required period of time using active blocking 

equipment; 

1.3.3.4.3. Wireless Blocking: Capability to block wireless signals in specific 

parts of the campus for a required period of time using active 

blocking equipment; 

1.3.3.4.4. Site Security Communications (Radio Communications): Provision of 

dedicated radio communication infrastructure for NNHQ Security 

Staff; 

1.3.3.4.5. IPTV: Provision of TV broadcast services including multiple 

channels, for the NNHQ Campus. 

1.3.3.5. Specific Communities of Interest Services 

1.3.3.5.1. Service Management Capability (SMC): Capabilities of service and 

system management and control for all of the above mentioned 

services; 

1.3.3.5.2. Information Assurance Management: Overall IA management 

covering all specific IA services mentioned above. 

1.3.4. The ANWI capability includes the following network interoperability 

capabilities: 

1.3.4.1. Cross Domain Gateways and network services allowing communication 

between domains, covering interoperability requirements for the NATO 

HQ at both local and global level, subject to security regulations; 

1.3.4.2. Interoperability and integration with NATO-wide secure Automated 

Information System (AIS) capabilities; 

1.3.4.3. Interoperability and integration with NATO-wide Information Assurance 

capabilities. 

1.3.4.4. The ANWI Contractor will provide and support Integration Test Services 

(ITS). The other Host Nations will be required to test and successfully 

pass their installable CIS capabilities through the ITS before the 

capability can be installed on-site. Nations wishing to provide their own 

ICT capability with an interface to ANWI will be able to use the ITS for 

testing the interface (this assumes that the Nation will provide any 


NATO UNCLASSIFIED



needed connectivity between the two environments and fund the 

testing). 

1.3.5. The ANWI Contractor will integrate the ANWI capability with 

systems/services external to the ANWI scope; as such, it will have the 

responsibility to coordinate, synchronise solutions and schedules with the 

other Host Nation Contractors to deliver a fully integrated and useable 

ANWI. 

1.3.6. The ANWI Contractor will migrate the identified ANWI ICT core services 

from the current HQ ICT infrastructure to the ANWI infrastructure inside 

the NNHQ and will provide ANWI migration support to other Host 

Nations. 

1.4. Governing Rules, Eligibility, and Exclusion Provisions 

1.4.1. This solicitation is an International Invitation for Bid and is issued in 

accordance with the procedures for International Competitive Bidding set 

forth in the NATO document AC/4-D/2261 (1996 Edition). 

1.4.2. Pursuant to these procedures, Bidding is restricted to companies from 

participating NATO member nations for which a Declaration of Eligibility 

has been issued by their respective government authorities. 

1.4.3. Best Value Evaluation Method 

The evaluation method to be used in the selection of the successful 

Bidder under this solicitation will follow the Best Value Procedures set 

forth in AC/4-D(2008)0002-REV1 dated 27 April 2009. 

1.4.4. The Bid evaluation criteria and the detailed evaluation procedures are 

described in SECTION 4 

1.4.5. The Bidder shall refer to the Purchaser all queries for resolution of any 

conflicts found in information contained in this document in accordance 

with the procedures set forth in paragraph 2.6 "Request for IFB 

Clarifications”. 

1.4.6. Prospective Bidders shall note that the Purchaser reserves the right to 

exclude the successful Bidder and its prospective Subcontractors from 

the award of this Contract if the successful Bidder or its prospective 

Subcontractors may be in a position to unfairly influence this Contract as 

a result of being selected for the work performed or to be performed 

under other New NATO Headquarters (NNHQ) related Contracts. This 

applies also to the Contractor's/Subcontractor's parent companies or 

subsidiaries unless the parent company or its subsidiaries provide 

evidence in accordance with the prescriptions of paragraph 3.4.4. The 


NATO UNCLASSIFIED



1.5. Security 

1.6.2. The purpose of the Bidders Conference will be to present the Project, 

and present the key members of the NATO project management team, 

as well as to allow the Prospective Bidders to clarify aspects of the 

Invitation for Bid for which they may have questions at that time. 



process described in paragraph 4.4.1.5 will be used to evaluate any such 

evidence provided. 

1.5.1. This Invitation for Bid has been classified as NATO UNCLASSIFIED. 

1.5.2. The Contractor will be required to handle and store classified material to 

the level of “NATO SECRET”, and the Contractor shall have the 

appropriate facility and personnel clearances at the date of Contract 

signature. Should the Contractor be unable to perform the Contract due 

to the fact that the facility clearance has not been provided by their 

respective national security agency, this lack of clearance cannot be the 

basis for a claim of adjustment or an extension of schedule, nor the lack 

of clearance be considered a mitigating circumstance in the case of an 

assessment of Liquidated Damages or a determination of Termination 

For Default by the Purchaser. 

1.5.3. Contractor personnel working at NATO or National sites are required to 

possess a security clearance of “NATO SECRET”. Contractor personnel 

without such a clearance, confirmed by the appropriate national security 

authority and transmitted to the cognisant NATO or National security 

officer at least fourteen (14) days prior to the site visit, will be denied 

access to the site. Denial of such access by the Purchaser may not be 

used by the Contractor as the basis for a claim of adjustment or an 

extension of schedule nor can the denial of access be considered a 

mitigating circumstance in the case of an assessment of Liquidated 

Damages or a determination of Termination for Default by the Purchaser. 

1.5.4. Bidders are advised that Contract signature will not be delayed in order 

to allow the processing of security clearances for personnel or facilities 

and, should the otherwise successful Bidder not be in a position to 

accept the offered Contract within a reasonable period of time, due to the 

fact that its personnel or facilities do not possess the appropriate security 

clearance(s), the Purchaser may determine the Bidder’s Offer to be noncompliant 

and offer the Contract to the next ranking Bidder. In such a 

case, the Bidder who would not sign the Contract shall be liable for 

forfeiture of the Bid Guarantee. 

1.6. Bidders Conference 

1.6.1. Prospective Bidders are invited to a Bidders Conference that will be held 

at NATO Headquarters, Brussels, on 18 July 2012.



1.6.3. The Bidder’s Conference is planned to include a briefing on the bidding 

process; the Bidding Sheets; the prospective contract; and the technical 

and project management aspects of the project. 

1.6.4. The participation to the Conference is limited to a maximum of three (3) 

attendees per Bidder. No exception to this number of attendees will be 

made. A detailed agenda for the Bidder’s Conference will be sent to the 

participating companies in due course. 

1.6.5. Bidders that wish to participate in the Bidders Conference shall indicate 

their intention to attend not later than 7 days prior to the date of the 

Conference to the Point of Contact stated hereafter. NATO Secret 

security clearances are not required for the Bidders Conference. The 

interested Bidders shall provide the following relevant data for each of 

their (maximum of three) staff wishing to attend: 

Name of company, 

Name of attendee, 

Passport/ ID card number, 

Place and date of birth, 

E-mail address. 

1.6.6. All attendee nominations shall be addressed to the IFB POC specified in 

2.5.1 below. 

1.6.7. Any questions which the potential Bidders would like to have answered 

at the Bidders Conference must be submitted in writing not later than 7 

days prior to the date of the Conference to the POC, at the address 

mentioned under paragraph ‎2.5.1 “Purchaser Point of Contact”. 

1.6.8. The Purchaser will respond to these previously submitted questions at 

the Bidders Conference. If any additional questions are asked by the 

potential Bidders at the Conference, the Purchaser may attempt to 

answer pertinent questions at that time, but any answer that may appear 

to amend terms, conditions and/or specifications of the Contract shall be 

considered to be formally included in the Invitation for Bid only when a 

written amendment to the IFB is issued in writing by the Purchaser. 

1.6.9. In any case, a written summary of the Bidders Conference will be issued 

by the Purchaser to all potential Bidders after the Bidders Conference. 

1.6.10. Notwithstanding the written answers provided by the Purchaser after the 

Bidders’ Conference, the terms, conditions and language of the IFB 


NATO UNCLASSIFIED



remains unaltered unless a formal IFB amendment is issued by the 

Purchaser and is identified as such. 

1.7. Documentation 

1.7.1. All documentation, including the IFB itself, all applicable documents and 

any reference documents provided by the Purchaser are solely to be 

used for the purpose of preparing a response to this IFB. They are to be 

safeguarded at the appropriate level according to their classification and 

reference documents are provided “as is“, without any warranty as to 

quality or accuracy. 


NATO UNCLASSIFIED



SECTION 2 

GENERAL BIDDING INFORMATION 

2.1. Definitions 

2.1.1. In addition to the definitions and acronyms set in the Contract Special 

Provisions (Part II) of the prospective Contract, and the definitions and 

acronyms set in the Clause entitled “Definitions of Terms and Acronyms” 

of the Contract General Provisions (Part III) of the prospective Contract, 

the following terms and acronyms, as used in this Invitation for Bid shall 

have the meanings specified below: 

2.1.1.1. "Bidder": a firm, consortium, or joint venture which submits an offer in 

response to this solicitation. Bidders are at liberty to constitute 

themselves into any form of contractual arrangements or legal entity 

they desire, bearing in mind that in consortium-type arrangements a 

single judicial personality shall be established to represent that legal 

entity. A legal entity, such as an individual, Partnership or Corporation, 

herein referred to as the “Principal Contractor”, shall represent all 

members of the consortium with the NCI Agency and/or NATO. The 

“Principal Contractor” shall be vested with full power and authority to act 

on behalf of all members of the consortium, within the prescribed 

powers stated in an irrevocable Power of Attorney issued to the 

“Principal Contractor” by all members associated with the consortium. 

Evidence of authority to act on behalf of the consortium by the “Principal 

Contractor” shall be enclosed and sent with the Bid. Failure to furnish 

proof of authority may be a reason for the Bid being declared noncompliant. 

2.1.1.2. "Compliance": strict conformity to the requirements and standards 

specified in this IFB and its attachments. 

2.1.1.3. "Contractor": the awardee of this solicitation of offers, who shall be 

responsible for the fulfilment of the requirements established in the 

prospective Contract. 

2.1.1.4. “Firm of a Participating Country”: a firm legally constituted or chartered 

under the laws of, and geographically located in, or falling under the 

jurisdiction of a Participating Country. 

2.1.1.5. “IFB”: Invitation for Bid. 

2.1.1.6. “Participating Country”: any of the NATO nations contributing to the 

project, namely, (in alphabetical order): 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, THE UNITED KINGDOM and THE UNITED STATES. 


NATO UNCLASSIFIED



2.1.1.7. “Purchaser”: NATO Communications and Information Agency (NCI 

Agency, NCIA). 

2.1.1.8. “Quotation” or “Bid”: a binding offer to perform the work specified in the 

attached prospective Contract (Book II). 

2.2. Eligibility and Origin of Equipment and Services 

2.2.1. As stated in paragraph 1.4.1 above only firms from a Participating 

Country are eligible to engage in this competitive Bidding process. In 

addition, all Contractors, Subcontractors and manufacturers, at any tier, 

must be from Participating Countries. 

2.2.2. None of the work, including project design, labour and services shall be 

performed other than by firms from and within Participating Countries. 

2.2.3. No materials or items of equipment down to and including identifiable 

Sub-assemblies shall be manufactured or assembled by a firm other than 

from and within a Participating Country. 

2.2.4. Unless otherwise authorised by the terms of the prospective Contract, 

the Intellectual Property Rights to all design documentation and related 

system operating software shall reside in NATO member countries, and 

no license fees or royalty charges shall be paid by the Contractor to 

firms, individuals or governments other than within the NATO member 

community. 

2.3. Bid Delivery and Bid Closing 

2.3.1. All Bids shall be in the possession of the Purchaser at the address given 

below in paragraph 2.3.2 on/or before 13.00 hours (Brussels Time) on 

22 October 2012, at which time and date Bidding shall be closed. 

2.3.2. Bids shall be delivered to the following address: 

2.3.2.1. By Post: 

NCI Agency 

Acquisition and Procurement 

(Attn: Mr. Sven Schumacher) 

Boulevard Leopold III 

1110 Brussels 

Belgium 

2.3.2.2. Hand Carried Service or courier: 

NCI Agency 


(Attn: Mr. Sven Schumacher) 

Bâtiment Z 

Avenue du Bourget 140 

1110 Brussels,Belgium 


NATO UNCLASSIFIED





2.3.3. Bids submitted by electronic means are not permitted and will not be 

considered. Bidders are advised that security or other personnel 

remaining on the premises outside of normal business hours may decline 

to sign or issue receipts for delivered items. 

2.3.4. Late Bids 

2.3.4.1. Bids which are delivered to the Purchaser after the specified time and 

date set forth above for Bid Closing are "Late Bids" and shall not be 

considered for award. Such Bids will be returned unopened to the 

Bidder at the Bidder's expense unless the Purchaser can determine that 

the Bid in question meets the criteria for consideration as specified 

below. 

2.3.4.2. Consideration of Late Bid – The Purchaser considers that it is the 

responsibility of the Bidder to ensure that the Bid submission arrives by 

the specified Bid Closing time. Considering the number and quality of 

express delivery services, courier services and special services 

provided by the national postal systems, a late Bid shall only be 

considered for award under the following circumstances: 

2.3.4.2.1. A Contract has not already been awarded pursuant to the Invitation 

for Bid, and 

2.3.4.2.2. The Bid was sent to the address specified in the IFB by ordinary, 

registered or certified mail not later than ten (10) calendar days 

before the Bid closing date and the delay was due solely to the 

national or international postal system for which the Bidder bears no 

responsibility (the official postmark for ordinary and Registered Mail 

or the date of the receipt for Certified Mail will be used to determine 

the date of mailing), or 

2.3.4.2.3. The Bid was hand carried, or delivered by a private courier service 

and the Bidder can produce a receipt which demonstrates that the 

delivery was made to the correct address and received by a member 

of the NCI Agency and the failure to be received by the Contracting 

Authority was due to mishandling within the Purchaser’s 

organisation. 

2.3.4.3. A Late Bid which was hand-carried, or delivered by a private courier, for 

which a proper receipt cannot be produced, cannot be considered for 

award under any circumstances nor can late Bids which bear no post 

marks or for which documentary evidence of mailing date cannot be 

produced. 

2.4. Requests for Extension of Bid Closing Date 

2.4.1. Bidders are informed that requests for extension to the closing date for 

the IFB shall be submitted by the Bidder only through his respective 

country’s NATO Delegation or Embassy to the Purchaser point of contact





indicated in paragraph 2.5.1 below. In accordance with AC/4-D/2261 

Final (July 1996 Edition) any request for extension shall be submitted by 

the respective NATO Delegation or Embassy no later than fourteen (14) 

days prior to the established Bid closing date. Bidders are advised to 

submit their request in sufficient time as to allow their respective NATO 

Delegation or Embassy to deliver the formal request to the Purchaser 

within the above time limit. 

2.5. Purchaser’s Point of Contact 

2.5.1. The Purchaser point of contact for all information concerning this 

Invitation for Bid is: 

Mr. Sven Schumacher 

Contracting Officer 


Tel: +32 (0)2 707 8576 

Fax: +32 (0)2 707 8770 

E-mail: sven.schumacher@ncia.nato.int 

Alternate: 

Ms. Dimitra Kokkali 

Senior Contracting Assistant 


Tel: +32 (0)2 707 8175 

Fax: +32 (0)2 707 8770 

E-mail: dimitra.kokkali@ncia.nato.int 

2.5.2. All correspondence related to the IFB shall be forwarded to: 

NCI Agency 


Boulevard Leopold III 

1110 Brussels, Belgium 

Attn: Mr Sven Schumacher (contact details stated above) 

2.6. Request for IFB Clarifications 

2.6.1. Bidders, during the solicitation period, are encouraged to query and seek 

clarification of any matters of a contractual, administrative and technical 

nature pertaining to this IFB. 

2.6.2. All requests for clarification shall be forwarded to the Purchaser using the 

Clarification Request Forms provided at Annex D of this Book I. Such 

requests shall be forwarded via email to the point of contact specified in 

paragraph 2.5.1 above and shall arrive not later than twenty eight (28) 

calendar days prior to the stated "Bid Closing Date". The Purchaser is 

under no obligation to answer requests for clarification submitted after



this time. Requests for clarification must address the totality of the 

concerns of the Bidder, as the Bidder will not be permitted to revisit areas 

of the IFB for additional clarification except as noted in 2.6.3 below. 

2.6.3. Additional requests for clarification are limited only to the information 

provided as answers by the Purchaser to Bidder requests for clarification. 

Such additional requests shall arrive not later than fourteen (14) calendar 

days before the established Bid Closing Date. 

2.6.4. The Purchaser may provide for a re-wording of questions and requests 

for clarification where it considers the original language ambiguous, 

unclear, subject to different interpretation or revelatory of the Bidder’s 

identity. 

2.6.5. Bidders are advised that subsequent questions and/or requests for 

clarification included in a Bid shall neither be answered nor considered 

for evaluation. 

2.6.6. Except as provided above, all questions will be answered by the 

Purchaser and the questions and answers (but not the identity of the 

questioner) will be issued in writing to all prospective Bidders. 

2.6.7. Where the extent of the changes implied by the response to a 

clarification request is of such a magnitude that the Purchaser deems 

necessary to issue revised documentation, the Purchaser will do so by 

the means of the issuance of a formal IFB amendment pursuant to AC/4- 

DS-2261 and in accordance with paragraph 2.8 below. 

2.6.8. The Purchaser reserves the right to reject questions and clarification 

requests clearly devised or submitted for the purpose of artificially obtain 

an extension of the bidding time (i.e. clarifications re-submitted using 

different wording where such wording does not change the essence of 

the clarification being requested). 

2.6.9. The published responses issued by the Purchaser shall be regarded as 

the authoritative interpretation of the Invitation for Bid. Any amendment 

to the language of the IFB included in the answers will be issued as an 

IFB Amendment and shall be incorporated by the Bidder in his offer. 

2.7. Requests for Waivers and Deviations 

2.7.1. Bidders are informed that requests for alteration to, waivers or deviations 

from the terms and conditions of this IFB and attached prospective 

Contract (Book II) will not be considered after the request for clarification 

process. Requests for alterations to the other requirements, terms or 

conditions of the Invitation for Bid or the prospective Contract may only 

be considered as part of the clarification process set forth in paragraph 

2.6 above. Requests for alterations to the specifications, terms and 

conditions of the Contract which are included in a Bid as submitted may 


NATO UNCLASSIFIED





be regarded by the Purchaser as a qualification or condition of the Bid 

and may be grounds for a determination of non-compliance. 

2.8. Amendment of the Invitation for Bid 

2.8.1. The Purchaser may revise, amend or correct IFB at any time prior to the 

Bid Closing Date as detailed in paragraph 2.3. Any and all modifications 

will be transmitted to all Bidders by an official amendment designated as 

such and signed by the Purchaser. This process may be part of the 

clarification procedures set forth in paragraph 2.6 above or may be an 

independent action on the part of the Purchaser. 

2.8.2. All such IFB amendments issued by the Purchaser shall be 

acknowledged by the Bidder in its Bid by completing the 

“Acknowledgement of Receipt of IFB Amendments” certificate at Annex 

B-2. Failure to acknowledge receipt of all amendments may be grounds 

to determine the Bid to be administratively non-compliant. 

2.8.3. The Purchaser will consider the potential impact of amendments on the 

ability of prospective Bidders to prepare a Bid within the allotted time. 

The Purchaser may extend the "Bid Closing Date" at its discretion and 

such extension will be set forth in the amendment. 

2.9. Modification and Withdrawal of Bids 

2.9.1. Bids, once submitted, may be modified by Bidders, but only to the extent 

that the modifications are in writing, conform to the requirements of the 

IFB, and are received by the Purchaser prior to the Bid Closing Date as 

detailed in paragraph 2.3. Such modifications will be considered as an 

integral part of the submitted Bid. 

2.9.2. Modifications to Bids which arrive after the Bid Closing Date will be 

considered as "Late Modifications" and will be processed in accordance 

with the procedure detailed in paragraph 2.3.4, except that unlike a "Late 

Bid", the Purchaser will retain the modification until a selection is made. 

A modification to a Bid which is determined to be late will not be 

considered in the evaluation and selection process. If the Bidder 

submitting the modification is determined to be the successful Bidder on 

the basis of the unmodified Bid, the modification may then be opened. If 

the modification makes the terms of the Bid more favourable to the 

Purchaser, the modified Bid may be used as the basis of Contract award. 

The Purchaser, however, reserves the right to award a Contract to the 

apparent successful Bidder on the basis of the Bid submitted and 

disregard the late modification. 

2.9.3. A Bidder may withdraw its Bid at any time prior to Bid Opening without 

penalty. In order to do so, an authorised agent or employee of the 

Bidder must provide an original statement of the firm's decision to 

withdraw the Bid and subsequently remove the Bid from the Purchaser’s 

premises.



2.9.4. Except as provided in paragraph 2.10.4.2 below, a Bidder may withdraw 

its Bid after Bid Opening only by forfeiture of the Bid Guarantee. 

2.10. Bid Validity 

2.10.1. Bidders shall be bound by the term of their Bid for a period of twelve (12) 

months starting from the Bid Closing Date specified in paragraph 2.3.1 

above. 

2.10.2. In order to comply with this requirement, the Bidder shall complete the 

Certificate of Bid Validity set forth in Annex B-4. Bids offering less than 

the period of time referred to above for acceptance by the Purchaser 

may be determined to be non-compliant. 

2.10.3. The Purchaser will endeavour to complete the evaluation and make an 

award within the period referred to above. However, should that period 

of time prove insufficient to render an award, the Purchaser reserves the 

right to request an extension of the period of validity of all Bids which 

remain under consideration for award. 

2.10.4. Upon notification by the Purchaser of such a request for a time 

extension, the Bidders shall have the right to: 

2.10.4.1. accept this extension of time in which case Bidders shall be bound by 

the terms of their offer for the extended period of time and the Bid 

Guarantee and Certificate of Bid Validity extended accordingly; or 

2.10.4.2. refuse this extension of time and withdraw the Bid, in which case the 

Purchaser will return to the Bidder its Bid Guarantee in the full amount 

without penalty. 

2.10.5. Bidders shall not have the right to modify their Bids due to a Purchaser 

request for extension of the Bid validity unless expressly stated in such 

request. 

2.11. Bid Guarantee 

2.11.1. The Bidder shall furnish with his Bid a guarantee in an amount equal to 

Five Hundred Thousand Euro (€500,000). The Bid Guarantee shall be 

substantially similar to Annex C as an irrevocable, unqualified and 

unconditional Standby Letter of Credit (SLC) issued by a Belgian banking 

institution fully governed by Belgian legislation or issued by a non- 

Belgian financial institution and confirmed by a Belgian banking 

institution fully governed by Belgian legislation. In the latter case signed 

original letters from both the issuing institution and the confirming 

institution must be provided. The confirming Belgian bank shall clearly 

state that it will guarantee the funds, the drawing against can be made by 

the NCI Agency at its premises in Belgium. Bid Guarantees shall be 

made payable to the Treasurer, NCI Agency. 


NATO UNCLASSIFIED





2.11.2. Alternatively, a Bidder may elect to post the required Guarantee by 

certified cheque. If the latter method is selected, Bidders are informed 

that the Purchaser will cash the cheque on the Bid Closing Date or as 

soon as possible thereafter. 

2.11.3. If the Bid Closing Date is extended after a Bidder's financial institution 

has issued a Bid Guarantee, it is the obligation of the Bidder to have 

such Bid Guarantee (and confirmation, as applicable) extended to reflect 

the revised Bid Validity date occasioned by such extension. 

2.11.4. Failure to furnish the required Bid Guarantee in the proper amount, 

and/or in the proper form and/or for the appropriate duration by the Bid 

Closing Date may be cause for the Bid to be determined non-compliant. 

2.11.5. In the event that a Bid Guarantee is submitted directly by a banking 

institution, the Bidder shall furnish a copy of said document in the Bid 

Administration Package. 

2.11.6. The Purchaser will make withdrawals against the amount stipulated in 

the Bid Guarantee under the following conditions: 

2.11.6.1. The Bidder has submitted a Bid and, after Bid Closing Date (including 

extensions thereto) and prior to the selection the compliant Bid 

determined to represent the best value, withdraws his Bid, or states that 

he does not consider his Bid valid or agree to be bound by his Bid, or 

2.11.6.2. The Bidder has submitted a compliant Bid determined by the Agency to 

represent the best value, but the Bidder declines to sign the Contract 

offered by the Agency, such Contract being consistent with the terms of 

the Invitation for Bid. 

2.11.6.3. The Purchaser has offered the Bidder the Contract for execution but the 

Bidder has been unable to demonstrate compliance with the security 

requirements of the Contract within a reasonable time, 

2.11.6.4. The Purchaser has entered into the Contract with the Bidder but the 

Bidder has been unable or unwilling to provide the Performance 

Guarantee required under the terms of the Contract within the time 

frame required. 

2.11.7. Bid Guarantees will be returned to Bidders as follows: 

2.11.7.1. to non-compliant Bidders forty-five (45) days after notification by the 

Purchaser of a non-compliant Bid (except where such determination is 

challenged by the Bidder; in which case the Bid Guarantee will be 

returned forty-five (45) days after a final determination of noncompliance); 

2.11.7.2. to all other unsuccessful Bidders within thirty (30) days following the 

award of the Contract to the successful Bidder;





2.11.7.3. to the successful Bidder upon submission of the Performance 

Guarantee required by the Contract or, if there is no requirement for 

such a Performance Guarantee, upon Contract execution by both 

parties. 

2.11.7.4. pursuant to paragraph 2.10.4.2 above. 

2.11.8. “Standby Letter of Credit" or “SLC” as used herein, means a written 

commitment by a Belgian financial institution either on its own behalf or 

as a confirmation of the Standby Letter of Credit issued by a non-Belgian 

bank to pay all or part of a stated amount of money, until the expiration 

date of the letter, upon presentation by the Purchaser of a written 

demand therefore. Neither the financial institution nor the Contractor can 

revoke or condition the Standby Letter of Credit. The term “Belgian 

financial institution” includes non-Belgian financial institutions licensed to 

operate in Belgium, 

2.12. Cancellation of Invitation for Bid 

2.12.1. The Purchaser may cancel, suspend or withdraw for re-issue at a later 

date this IFB at any time prior to Contract award. No legal liability on the 

part of the Purchaser for payment of any sort shall arise and in no event 

will any Bidder have cause for action against the Purchaser for the 

recovery of costs incurred in connection with preparation and submission 

of a Bid in response to this IFB. 

2.13. Electronic Transmission of Information and Data 

2.13.1. The Purchaser will endeavour to communicate answers to requests for 

clarification and amendments to this IFB to the prospective Bidders as 

soon as practicable. 

2.13.2. Bidders are cautioned that except for those cases in which electronic 

transmission of documentation is not permissible (i.e. documents with 

security classification mandating specific transmission methods) the 

Purchaser will rely exclusively on electronic means (i.e. electronic mail 

communication and use of a dedicated IFB webportal) to manage all 

correspondence related to this IFB, including IFB amendments and 

clarifications. 

2.13.3. Notwithstanding paragraph 2.13.2 above and subject to feasibility, 

prospective Bidders may request to be notified also by fax or regular mail 

when IFB correspondence is released to them. Such requests shall be 

submitted to the points of contact specified in paragraph 2.5.1 above. 

Such requested method of notification shall not be construed as the 

Bidders’ right to obtain an extension of the Bid Closing Date. 

2.13.4. Bidders shall note that where voluminous documentation is to be 

transmitted the Purchaser will consider electronic transmission as the 

sole feasible manner to promptly notify all Bidders pursuant to the



prescription is paragraph 2.13.1. Consequently, in such cases, the 

Purchaser will notify the Bidders’ of the impossibility to resort to 

alternative methods of transmissions if this has been requested. 

2.14. Supplemental Agreements 

2.14.1. Bidders are required, in accordance with the certificate at Annex B-7 of 

these Instructions to Bidders, to disclose any prospective Supplemental 

Agreements that are required by national governments to be executed by 

NATO/ NCIA as a condition of Contract performance. 

2.14.2. Supplemental Agreements are typically associated with, but not 

necessarily limited to, national export control regulations, technology 

transfer restrictions and end user agreements or undertakings. 

2.14.3. Bidders are cautioned that failure to provide full disclosure of the 

anticipated requirements and the terms thereof, to the best of the 

Bidder’s knowledge and experience, may result in the Purchaser 

withholding award of the Contract or cancelling an executed Contract if it 

is discovered that the terms of such Supplemental Agreements contradict 

salient conditions of the Prospective Contract to the extent that either key 

objectives cannot be accomplished or basic Contract principles and 

Purchaser rights have been abridged. 

2.15. Notice of Limitations on Use of Intellectual Property Delivered to the 

Purchaser 

2.15.1. Bidders are instructed to review Clause 30 of the Contract General 

Provisions set forth Part III of Book II herein. This Clause sets forth the 

definitions, terms and conditions regarding the rights of the Parties 

concerning Intellectual Property developed and/or delivered under this 

Contract or used as a basis of development under this Contract. 

2.15.2. Bidders are required to disclose, in accordance with Annex B-10, Annex 

B-11, the Intellectual Property proposed to be used by the Bidder that will 

be delivered with either Background Intellectual Property Rights or Third 

Party Intellectual Property Rights. Bidders are required to identify such 

Intellectual Property and the basis on which the claim of Background or 

Third Party Intellectual Property is made. 

2.15.3. Bidders are further required to identify any restrictions on Purchaser use 

of the Intellectual Property that is not in accordance with the definitions 

and rights set forth in Clause 30 of the Contract General Provisions, or 

any other provision of the Contract concerning use or dissemination of 

such Intellectual Property. 

2.15.4. Bidders are reminded that restrictions on use or dissemination of 

Intellectual Property conflicting with Clause 30 of the Contract General 

Provisions or with the objectives and purposes of the Purchaser as 


NATO UNCLASSIFIED



stated in the Prospective Contract shall result in a determination of a 

non-compliant Bid. 

2.16. Mandatory Quality Assurance and Quality Control Standards 

2.16.1. Bidders are requested to note that, in accordance with the Certificate at 

Annex B-8 hereto, Bidders shall provide documentary evidence that the 

Bidder possesses a current certification that is compliant with the 

requirements of Allied Quality Assurance Publication (AQAP) 2110, ISO 

9001:2008, or an equivalent QA/QC regime. 

2.16.2. Bidders shall further demonstrate that such regime is applied within the 

Bidder’s internal organisation, as well as extended to its relationships 

with Subcontractors. 

2.16.3. If the Bidder is offering a QA/QC regime that is claimed to be equivalent 

to AQAP 2110 or ISO 9001:2008, the burden of proof of such 

equivalency shall be on the Bidder and such evidence of equivalency 

shall be submitted with the Certificate at Annex B-8 in the Bid 

Administration Package. 

2.16.4. Failure to execute this Certificate, or failure to provide documentary 

evidence of compliance with this requirement may result in a 

determination of non-compliance for the submitted Bid. 


NATO UNCLASSIFIED



SECTION 3 

BID PREPARATION INSTRUCTIONS 

3.1. General 

3.1.1. Bidders shall prepare and submit their Bid in accordance with the 

requirements and format set forth in this IFB. Compliance with all Bid 

submission requirements is mandatory. Failure to submit a Bid in 

conformance with the stated requirements may result in a determination 

of non-compliance by the Purchaser and the elimination of the Bid from 

further consideration. 

3.1.2. Bidders shall not simply restate the IFB requirements. A Bid shall 

demonstrate that a Bidder understands the terms, conditions and 

requirements of the IFB and its ability to provide all the services and 

deliverables listed in the Schedules of the prospective Contract. 

3.1.3. Bidders are informed that the quality, thoroughness and clarity of the Bid 

will affect the overall scoring of the Bid. Although the Purchaser may 

request clarification of the Bid, it is not required to do so and may make 

its determination on the content of the Bid as written. Therefore, Bidders 

shall assume that inconsistencies, omissions, errors, lack of detail and 

other qualitative deficiencies in the submitted Bid will have a negative 

impact on the final Best Value score. 

3.1.4. Partial Bids will be declared non-compliant. 

3.1.5. Bidders are advised that the Purchaser reserves the right to incorporate 

the successful Bidder’s Offer in whole or in part by reference in the 

resulting Contract. 

3.1.6. If no specific format has been established for electronic versions/ soft 

copies of the Bid documentation to be provided in accordance with 

paragraph 3.2 below, Bidders shall deliver this type of documentation in 

an electronic format which is best suited for review and maintenance by 

the Purchaser (e.g., Project Master Schedule in MS Project format, 

Project Highlight Reports in MS Word). 

3.1.7. In the event of a discrepancy between the soft and hard copies of the Bid 

documentation to be provided in accordance with paragraph 3.2 below, 

the hard copy will be considered as the authoritative bid document for the 

purpose of evaluation and take precedence. 

3.1.8. All documentation submitted as part of the Bid shall be classified no 

higher than “NATO UNCLASSIFIED”. 

3.1.9. All documentation submitted as part of the Bid shall be in English. 


NATO UNCLASSIFIED



3.2. Bid Package Content 

3.2.1. The complete Bid shall consist of three distinct and separated parts 

described in the following subparagraphs. Detailed requirements for the 

structure and content of each of these packages are contained in these 

Bidding Instructions. 

3.2.2. The Bid Administration Package, containing one (1) hard copy and one 

(1) soft copy of the documents specified in paragraph ‎3.4 below. 

3.2.3. The Price Quotation, containing two (2) hard copies and two (2) soft 

copies in MS Excel format of the Price Quotation specified in 

paragraph ‎3.5 below. 

3.2.4. The Technical Proposal Package as specified below. Each Part shall be 

in a separate binder or file for ease of segregation and handling and shall 

each be submitted in two (2) hard copies and three (3) soft copies. 

3.2.4.1. Part 1 - The Bidder Qualification, as described in paragraph 3.6.1 below. 

3.2.4.2. Part 2 - The Key Personnel Proposal, as specified in paragraph 3.6.2 

below. Detailed CVs of proposed personnel shall be included in Part 2. 

3.2.4.3. Part 3 - The Project Management Proposal, as specified in paragraph 

3.6.3 below. 

3.2.4.4. Part 4 - The Initial High Level Design, as specified in paragraph 3.6.4 

below. 

3.2.4.5. Part 5 - The SMC Concept Proposal, as specified in paragraph 3.6.5 

below. 

3.3. Package Marking 

3.3.1. The separate parts of the Bid shall be placed in outer containers for 

delivery. All outer containers into which Bidding documents are placed 

shall be opaque or wrapped in opaque paper, sealed and identified with 

the following markings: 


SEALED BID IFB-CO-13300-ANWI 

BOX X of Y (1 of 3, 2 of 3, etc.) 

NOTIFY MR S. SCHUMACHER (X8576) / MS D. KOKKALI (X8175) 

UPON RECEIPT 

3.3.2. Each of the Bid parts placed in the outer container(s) shall be separately 

wrapped (multiple copies of the same document may be wrapped 

together), and marked as follows: 

3.3.2.1. Name and address of the Bidder, 

NATO UNCLASSIFIED





3.3.2.2. The words “SEALED BID” followed by the reference “IFB-CO-13300- 

ANWI”; 

3.3.2.3. The appropriate package marking, i.e. “Bid Administration”, “Price 

Quotation”, “Technical Proposal”. 

3.4. Bid Administration Package 

3.4.1. The Package must include the original of the Bid Guarantee required by 

paragraph 2.11 of the Bidding Instructions. If the Bid Guarantee is sent 

to the Purchaser directly from the Bidder's bank, a letter, in lieu of the 

actual Guarantee, shall be included specifying the details of the 

transmittal. Bidders are reminded that the Bid Guarantee shall reflect 

any extensions to the Bid Validity Date due to extensions in the Bid 

Closing Date. 

3.4.2. The Package shall include the certificates set forth in the Annex to these 

Bidding Instructions, signed in the original by an authorised 

representative of the Bidder. The text of the certificates must not be 

altered in any way. The certificates are as follows: 

3.4.2.1. Annex B-1 (Certificate of Legal Name of Bidder) 

3.4.2.2. Annex B-2 (Acknowledgement of Receipt of IFB Amendments) 

3.4.2.3. Annex B-3 (Certificate of Independent Determination) 

3.4.2.4. Annex B-4 (Certificate of Bid Validity) 

3.4.2.5. Annex B-5 (Certificate of Exclusion of Taxes, Duties and Charges) 

3.4.2.6. Annex B-6 (Comprehension and Acceptance of Contract Special and 

General Provisions) 

3.4.2.7. Annex B-7 (Disclosure of Requirements for NCIA Execution of 

Supplemental Agreements) with the prospective text of such 

Agreements, as applicable. 

3.4.2.8. Annex B-8 (Certificate of Compliance AQAP 2110 or ISO 9001:2008 or 

Equivalent) with a copy of the relevant quality certification attached to it. 

3.4.2.9. Annex B-9 (List of Prospective Subcontractors) 

3.4.2.10. Annex B-10 (Bidder Background IPR) 

3.4.2.11. Annex B-11(List of Subcontractor IPR) 

3.4.2.12. Annex B-12 (Certificate of Origin of Equipment, Services, and 

Intellectual Property) 

3.4.2.13. Annex B-13 (List of Proposed Key Personnel)



3.4.2.14. Annex B-14 (Certificate of Price Ceiling) 

3.4.2.15. Annex B-15 (Disclosure of Conflict of Interest) with mitigation plan and 

list of business relationships, as applicable 

3.4.2.16. Annex B-16 (Index and Certificate of Compliance of Administrative 

Certificates) 

3.4.3. Documentation Disclosure of Conflict of Interest 

3.4.3.1. A Conflict of Interest means that because of other activities or 

relationships with other persons or entities, a Bidder is unable or 

potentially unable to render impartial assistance or advice to the 

Purchaser or the Bidder’s objectivity in performing the prospective 

Contract work is, or might be otherwise impaired, or the Bidder has an 

unfair competitive advantage. 

3.4.3.2. In compliance with paragraph 4.4.1.5, Bidders and proposed 

Subcontractors detailed at Annex B-9, shall identify at Annex B-15 all 

business relationships with Contractors/Subcontractors performing work 

or having performed work under the New NATO Headquarters (NNHQ) 

Project, including but not limited to those resulting from ownership, 

share of assets, strategic business agreements regardless of their 

nature or financial magnitude of which the Bidders is knowledgeable at 

the time of Bid submission. If any of such relationships could constitute 

a real or apparent conflict of interest, or could otherwise, in any manner 

or form, influence or appear to influence the capacity of the Bidder to 

render unbiased service, Bidders shall submit a plan for the mitigation 

of the conflict at Annex B-15,detailing the measures the Bidder has or 

proposes to put in place for the purpose of preventing unfair advantage 

in relation to the performance associated with the prospective Contract. 

3.4.3.3. If Bidders consider that no conflict of interest exists, they shall include a 

declaration to that effect at Annex B-15, signed by the individual entitled 

to commit the company to such statement. 

3.4.4. No indication disclosing or contributing to disclose the Bid Price shall be 

made part of the Bid Administration Package. Failure to abide to this 

prescription may result in the bid being declared non-compliant. 

3.5. Price Quotation 

3.5.1. Package Contents 

3.5.1.1. This envelope must contain the following documentation and media in 

the quantities provided in paragraph 3.2.3 above: 


NATO UNCLASSIFIED



3.5.1.1.1. The completed set of sheets contained in the electronic file “3_IFB- 

CO-13300-ANWI-AMD-2-Book-I-Bidding-Sheets_v03.xlsx” 

submitted as part of this IFB. 

3.5.1.1.2. CD-ROM or DVD containing an electronic version, in MS Excel 

format, of the documentation stated in paragraph 3.5.1.1.1 above. 

3.5.2. General Rules 

3.5.2.1. Bidders are advised that the total price for CLINs 1, 2, 3, 4, 5, 6, 7, 8, 

9, 10, 11, 12, 13, 14, 15 and 16 shall not exceed a ceiling of EUR 

81,726,023 (eighty-one million seven hundred twenty-six thousand 

twenty-three Euro). Bids submitted in excess of this figure may be 

determined to be non-compliant and eliminated from further 

consideration. 

3.5.2.2. Bidders shall prepare their Price Quotation by completing the Bidding 

Sheets referred in paragraph 3.5.1.1.1 above, in accordance with the 

instructions specified in Annex A-1. 

3.5.2.3. The structure of the Bidding Sheets shall not be changed, other than as 

indicated elsewhere, nor should any quantity or item description in the 

Bidding Sheets. The currency(ies) of each Contract Line Item and subitem 

shall be shown. The prices provided shall be intended as the 

comprehensive total price offered for the fulfilment of all requirements 

as expressed in the IFB documentation including but not limited to those 

expressed in the SOW and SRS. 

3.5.2.4. Bidders shall furnish Firm Fixed Prices for all required items in 

accordance with the format set forth in the Instructions for preparation of 

the Bidding Sheets. This includes Firm Fixed Prices for all optional 

CLINs, both Evaluated Options (CLINs 16, 17, 18 and 19) and 

Non-Evaluated Options (CLIN 20, 21). 

3.5.2.5. Offered prices shall not be “conditional" in nature. Any comments 

supplied in the Bidding Sheets which are conditional in nature, relative 

to the offered prices, may result in a determination that the Bid is noncompliant. 

3.5.2.6. Bidders are responsible for the accuracy of their Price Quotations. Price 

Quotations that have apparent computational errors may have such 

errors resolved in the Purchaser’s favour or, in the case of gross 

omissions, inconsistencies or errors, may be determined to be noncompliant. 

In the case of inconsistencies between the electronic 

version of the Bidding Sheets and the paper “hard copy” of the Bidding 

Sheets, the “hard copy” will be considered by the Purchaser to have 

precedence over the electronic version. 


NATO UNCLASSIFIED



3.5.2.7. Bidders shall quote in their own national currency or in EURO. Bidders 

may also submit Bids in multiple currencies including other NATO 

member states' currencies under the following conditions: 

3.5.2.7.1. the currency is of a "participating country" in the project, and 

3.5.2.7.2. the Bidder can demonstrate, either through Subcontract 

arrangements or in its proposed work methodology, that it will have 

equivalent expenses in that currency. All major subcontracts and 

their approximate anticipated value should be listed on a separate 

sheet and included with the Price Quotation. 

3.5.2.8. The Purchaser, by virtue of his status under the terms of Article IX and 

X of the Ottawa Agreement, is exempt from all direct and indirect taxes 

(incl. VAT) and all customs duties on merchandise imported or 

exported. 

3.5.2.9. Bidders shall therefore exclude from their price Bid all taxes, duties and 

customs charges from which the Purchaser is exempted by international 

agreement and are required to certify that they have done so through 

execution of the Certificate at Annex B-5. 

3.5.2.10. Unless otherwise specified in the instructions for the preparation of 

Bidding Sheets in Annex A-1, all prices quoted in the proposal shall be 

on the basis that all deliverable items shall be delivered “Delivery Duty 

Paid (DDP)” in accordance with the International Chamber of 

Commerce INCOTERMS ® 2010. 

3.5.2.11. The Bidder’s attention is directed to the fact that Price Quotation shall 

contain no document and/or information other than the priced copies of 

the Bidding Sheets. Any other document will not be considered for 

evaluation. 

3.6. Technical Proposal Package 

3.6.1. Bidder Qualifications 

3.6.1.1. The Bidder shall provide an assessment of corporate experience; the 

corporate structure and capabilities; and individual skills and 

experience, including the following factors: 

3.6.1.2. The Bidder shall provide evidence of relevant and recent experience of 

the Bidder in the design and implementation and integration of projects 

similar to the subject procurement, including: 

3.6.1.2.1. The Bidder shall provide relevant and successful corporate 

experience in at least three Contracts within the last three years for 

which the Bidder integrated similar service based/oriented systems 

to meet military or government requirements. 


NATO UNCLASSIFIED



3.6.1.2.2. The Bidder shall provide relevant and successful corporate 

experience of the major Subcontractors for the delivery of critical 

service oriented capabilities. 

3.6.1.2.3. The Bidder shall provide relevant experience and expertise in 

providing ITIL based service management and support for NATO, 

military, government and/or Contractor Owned Contractor Operated 

(COCO) services (warranty, repair-and-replacement service, and 

improvement services) for information systems of large, 

geographically-dispersed organisations. 

3.6.1.3. The Bid shall provide a discussion of the corporate capabilities of the 

Bidder, including: 

3.6.1.3.1. Adequate and appropriate corporate resources available to support 

the Project. 

3.6.1.3.2. A well-established and mature level of capability in its system 

integration and testing practices and tools. 

3.6.1.3.3. Sufficient numbers of individuals with the skill and experience to 

meet the requirements of the Contract, including: 

3.6.1.3.3.1 The resumes and support data to meet or exceed the experience 

and educational criteria stated in the SOW. 

3.6.1.3.3.2 Evidence that the individuals have the expected knowledge, 

capability and experience to meet the requirements of this Contract. 

3.6.2. Key Personnel 

3.6.2.1. The Bid shall provide the resumes / Curricula Vitae (CVs) and 

supporting certification documentation of proposed Key Personnel that 

meet or exceed the experience and educational criteria stated 

hereunder and in SOW paragraph 4.2. 

3.6.2.2. The Bid shall demonstrate that the proposed Key Personnel have the 

required knowledge, capability and experience to meet the 

requirements of this Contract. 

3.6.2.3. ANWI Project Manager (PM) Requirements 

3.6.2.3.1. The ANWI PM shall have a current NATO SECRET security 

clearance 

3.6.2.3.2. The ANWI PM shall have a University Degree in Electronic 

Engineering, Computer Science, Telecommunications, or related 

discipline, preferably equivalent to a Master’s, supported by relevant 

certificates/ diplomas. Exceptionally, extensive relevant experience 

may be considered if the above qualifications are not met. 


NATO UNCLASSIFIED





3.6.2.3.3. The ANWI PM shall have a current Project Management (PRINCE2 

Practitioner and/or PMI Project Management Professional (PMP)) 

certification. 

3.6.2.3.4. The ANWI PM shall have a minimum of ten (10) years’ experience 

as an ICT Project Manager as supported by project references, 

points of contact, and descriptions/scope of the projects managed. 

3.6.2.3.5. The ANWI PM shall have a minimum experience of five (5) years 

gained within ICT procurement, implementation, migration and 

management in projects similar to the ANWI Project, as supported 

by project references, points of contact, and description of 

role/responsibilities/activities executed. 

3.6.2.3.6. The ANWI PM shall have a minimum of one (1) year experience in 

ICT QA activities as well as knowledge and experience with QA 

standards (either AQAP or ISO), supported by project references, 

points of contact, and description of role/responsibilities/activities 

executed. 

3.6.2.3.7. The ANWI PM shall have knowledge and experience with processes 

for integration and testing. 

3.6.2.3.8. The ANWI PM shall have minimum of two (2) years’ experience in 

projects where ICT migration/transition was exercised in a 

managerial role responsible for the planning, designing and 

execution of migration/transition activities, as supported by project 

references, points of contact, and descriptions of the 


3.6.2.3.9. The ANWI PM shall have a demonstrated spoken and written 

fluency in English, at a minimum level of 4343 as defined in 

STANAG 6001. 

3.6.2.4. ANWI Technical Lead (TL) Requirements 

3.6.2.4.1. The ANWI TL shall have a current NATO SECRET security 

clearance. 

3.6.2.4.2. The ANWI TL shall have a University Degree in Electronic 


discipline, preferably equivalent to a Master’s, supported by relevant 



3.6.2.4.3. The ANWI TL shall have demonstrated practical experience in 

Infrastructure (processing, virtualisation, storage, switches), 

supported by valid certification of at least the following areas: 

Microsoft (MCSE), CISCO (CCDP) or valid comparable (products 

used in the ANWI design) certification.





3.6.2.4.4. The ANWI TL shall have a minimum of two (2) years’ experience 

designing and implementing high-availability server rooms as 

supported by project references, points of contact, and technical 

descriptions of the projects implemented. 

3.6.2.4.5. The ANWI TL shall have a minimum of three (3) years’ experience 

designing and implementing local area networks in projects similar 

to the ANWI Project demonstrating a strong network infrastructure 

and network service focus with good knowledge of the Information 

Assurance and provisioning of core applications, as supported by 

project references, points of contact, and description of 

role/responsibilities/activities held in these projects. 

3.6.2.4.6. The ANWI TL shall have a minimum of two (2) years’ experience as 

a technical manager responsible for the planning, designing and 

execution of projects where an Active Directory and subsequent 

application and data migration/transition activities were exercised; as 


description of the role/responsibilities/activities during this time. 

3.6.2.4.7. The ANWI TL shall have a minimum of one (1) years’ experience in 

ICT QA activities, supported by supported by project references, 

point of contact, and description of role/responsibilities/activities. 

3.6.2.4.8. The ANWI TL shall have knowledge and experience with QA 

standards (either AQAP or ISO), processes for integration and (pre) 

migration testing. 

3.6.2.4.9. The ANWI TL shall have a minimum of three (3) years’ experience 

as a team leader or project manager to ensure the technical 

management oversight of a: LAN designer, Server Room designer, 

UCC designer, communications engineer and systems integrator; as 


description of the role/responsibilities/activities. 

3.6.2.4.10. The ANWI TL shall have an up to date ITIL v3 Intermediate Level 

Certification having earned at least 12 points in the Service 

Capability area. 

3.6.2.4.11. The ANWI TL shall have a demonstrated spoken and written fluency 

in English, at a minimum level of 4343 as defined in STANAG 6001. 

3.6.2.5. ANWI Test Director (TD) Requirements 

3.6.2.5.1. The ANWI TD shall have a current NATO SECRET security 

clearance. 

3.6.2.5.2. The ANWI TD shall have a University Degree in Electronic 


discipline, preferably equivalent to a Master’s and supplemented by



relevant postgraduate qualifications, supported by relevant 

certificates/ diplomas. Exceptionally extensive relevant experience 


3.6.2.5.3. The ANWI TD shall have integration and testing engineering skills 

with five (5) years’ experience as part of large ICT projects, 

supported by project references, point of contact, and description of 

role/responsibilities/activities. 

3.6.2.5.4. The ANWI TD shall have demonstrated practical experience in 

planning, conducting and assessing Integration and Testing 

activities in support of large ICT projects for at least three (3) years, 

supported by project references, point of contact, and description of 


3.6.2.5.5. The ANWI TD shall have demonstrated practical experience in 

testing of IT infrastructure, core services where the role of test 

engineer or integration engineer was exercised, supported by project 

references, point of contact, and description of 


3.6.2.5.6. The ANWI TD shall have demonstrated practical experience in ICT 

migrations where the role of test engineer or integration engineer 

was exercised for migration of ICT services (Active Directory, 

business applications and associated data), supported by project 



3.6.2.5.7. The ANWI TD shall have demonstrated practical knowledge and 

experience with QA standards (either AQAP or ISO), processes for 

integration and (pre) migration testing. 

3.6.2.5.8. The ANWI TD shall have a demonstrated spoken and written fluency 

in English, as defined in STANAG 6001 at a minimum level of 4343. 

3.6.3. Project Management Proposal 

3.6.3.1. Project Management Plan (PMP) 

3.6.3.1.1. The Bidder shall provide a project management plan that provides 

detailed information on the management approach to deliver the 

ANWI from Contract award till the end of the 5 year O&M period. 

3.6.3.1.2. The Bidder shall provide a description of its project management 

methodology and approach to be used for this project that is 

coherent with delivering the ANWI’s scope and its objectives. 

3.6.3.1.3. The proposed PMP shall be compliant with Annex K Appendix 3 of 

the SOW. 


NATO UNCLASSIFIED



3.6.3.1.4. The proposed PMP shall serve as the initial ANWI PMP. 

3.6.3.1.5. The proposed PMP shall contain the project management planning 

information so as to constitute a consistent and complete document 

that effectively permits the Purchaser to be able to assess the 

Bidder’s plan to manage to ANWI project. 

3.6.3.1.6. The proposed PMP identifies of the Contractor’s organisation, in 

particular all major Contractor units and any Subcontractors involved 

in meeting the requirements of the Contract, and the portion of the 

overall effort or deliverable item for which they are responsible. 

3.6.3.1.7. The proposed PMP shall describe the organization for the proposed 

Project Team that identifies all the required roles of the team 

members of the PMO, describing the lines of reporting and 

oversight. 

3.6.3.1.8. The proposed PMP shall describe the PMO in terms of 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. 

3.6.3.1.9. The proposed PMP shall describe the project management 

processes; including the stages and their staffing, and schedule 

estimate; project control mechanisms for entering and exiting a 

stage; and the Purchaser involvement in their project management 

process. 

3.6.3.1.10. The proposed PMP describes the relationship of the PMP to other 

project plans: Project Implementation Plan, Change Management 

Plan, Issue Management Plan, Testing and Acceptance Plan, 

Configuration Management Plan, Risk Management Plan, Service 

Delivery Plan, Integrated Logistic Support Plan and Training Plan. 

3.6.3.1.11. The PMP shall detail the mechanism through which the plans will be 

maintained during the lifecycle of the Contract and demonstrates 

that the Bidder can accommodate changes in scope in a controlled 

manner. 

3.6.3.2. Project Implementation Plan 

3.6.3.2.1. General 

3.6.3.2.1.1 The provided PIP shall serve as the ANWI’s initial PIP. 

3.6.3.2.1.2 The proposed PIP shall clearly and accurately identify the Bidder’s 

understanding of the project’s scope, including major deliverables, 

assumptions and constraints. 


NATO UNCLASSIFIED



3.6.3.2.1.3 The proposed PIP shall provide the Bidder’s plans, capabilities, and 

ability to satisfactorily implement the entire project in conformance 

with the requirements as specified in the SOW. 

3.6.3.2.1.4 The proposed PIP shall be consistent with the requirements of the 

SOW and effectively describe the scope, planning, and resources to 

deliver the ANWI requirements. However, differing from the SOW 

requirement, this version of the PIP shall not include associated 

cost information. 

3.6.3.2.2. Schedule 

3.6.3.2.2.1 The proposed schedule shall identify all Contract events and 

milestones, including Contract-related Purchaser deliverables, 

activities and events. 

3.6.3.2.2.2 The proposed schedule shall provide the duration, sequence, and 

resource effort to deliver tasks providing a realistic assessment of 

the scope of work involved. 

3.6.3.2.2.3 The schedule shall be compliant with the milestones in Annex A. 

3.6.3.2.3. Work Breakdown Structure (WBS) 

3.6.3.2.3.1 The Bidder shall provide a WBS to the level of detail reflecting all 

necessary activities (stages and their major tasks/work packages 

as well as the dependencies between the tasks/work packages) for 

the effective planning, management and delivery of the ANWI 

capability and provisioning of ANWI services where this is required. 

3.6.3.2.3.2 The WBS shall be consistent with the requirements for the SOW in 

its description of all engineering efforts for specifying, designing, 

developing, testing, accrediting, installing, integrating and 

supporting the delivery of the ANWI service based solution. 

3.6.3.3. Change Management Plan 

3.6.3.3.1. The Bidder shall provide a Change Management Plan that details 

the change management process that is to be used in the ANWI 

project. 

3.6.3.3.2. The Bidder shall provide the Change Management request process 

that shall be used during the ANWI project including the use and 

control of the change management register requirements and 

process for reviewing and processing changes. 

3.6.3.3.3. The Bidder’s Change Management Plan shall address roles and 

responsibilities of the necessary actors to execute the plan. 

3.6.3.4. Project Risk Register 


NATO UNCLASSIFIED



3.6.3.4.1. The Bidder shall provide an initial ANWI risk register which identifies 

and details the top 10 project risks. 

3.6.3.5. Project Issue Management Plan 

3.6.3.5.1. The Bidder shall provide an Issue Management Plan detailing the 

issue process that is to be used throughout the ANWI project. 

3.6.3.5.2. The Bidder’s Issue Management Plan shall detail how the Bidder 

plans to identify, analyse, manage, act and report on project issues. 

3.6.3.5.3. The Bidder’s Issue Management Plan shall address roles and 

responsibilities of the necessary actors to execute the plan. 

3.6.4. Initial High Level Design 

3.6.4.1. The Bidder shall provide a draft initial High Level Design (HLD) and 

architectural concepts not to exceed 120 pages; system drawings are to 

be included in an annex and will not count against the submitted page 

count. 

3.6.4.2. The Bidder’s submission shall serve as the ANWI’s initial High Level 

Design demonstrating their understanding and maturity of the proposed 

technical solution with respect to the requirements of the ANWI SOW. 

This initial High Level Design document shall be in line with the design 

document structure stated in Annex K Appendix 2 and serve as the 

baseline for further development of this deliverable. 

3.6.4.3. The Bidder’s HLD shall, at a minimum, contain: 

3.6.4.3.1. Design rational against the architectural principles (Annex K 

Appendix 2 Section 3.1) 

3.6.4.3.2. Logical model diagrams (Annex K Appendix 2 Section 3.2) 

3.6.4.3.3. Initial high level system design and how it satisfies the requirement 

for the ANWI services in the different security domains and zones 

and transfer of information between domains/zones. (Annex K 

Appendix 2 Section 4). 

3.6.4.3.4. The proposed HLD shall address the following topics : 

3.6.4.3.4.1 General overview of the required ANWI services per security 

domain including assumptions and dependencies. 

3.6.4.3.5. And for each of the two major infrastructures for the associated 

security domains the HLD shall address: 

3.6.4.3.5.1 Concept of operations - Overview of the different services and 

integration level and interfaces between services. 


NATO UNCLASSIFIED



3.6.4.3.5.2 Initial component level design that shows how a particular service is 

composed of integrated HW and SW components 

3.6.4.3.5.3 Server/ Technical Equipment Room (TER) room and rack designs 

with estimations of power and cooling requirements 

3.6.4.3.5.4 ANWI service design and details on how the service level targets 

shall be met including Service management and Control (SMC) and 

Information assurance (IA) requirements. (Annex E – I). This shall 

include details how the requirements for availability and reliability 

are to be achieved. 

3.6.4.3.5.5 Expanded Service Management & Control (SMC) design that 

explains how the operational status/metrics shall be captured, 

routed, monitored, “billed” and displayed in the Network Operations 

Centre (NOC) to show that the service is meeting its Service Level 

Agreement (SLA). 

3.6.4.3.5.6 Bandwidth design for both the wired and wireless networks; this 

bandwidth design shall incorporate all the ANWI services like 

Unified Communications and Collaboration (UCC), Client 

provisioning and IPTV. 

3.6.4.3.5.7 As there are numerous networks and numerous services, the 

Bidder shall explain how he will deliver and seamlessly integrate the 

ANWI deliverables and NATO PFE into a coherent highly available 

network. 

3.6.4.3.5.8 Detailed design of security mechanisms supporting the Bidder’s 

initial Security Risk Assessment (SRA). 

3.6.4.3.5.9 A SIP (of the bidder’s choosing) for one of the six cross domain 

gateways shall be provided as an appendix to the submitted 

design. 

3.6.4.3.6. Detailed initial design of the Cross-Domain Gateway modules 

(Annex K Appendix 2 Section 4.7) 

3.6.4.3.7. Detailed design of the Integrated Test Service solution (Annex K 

Appendix 2 Section 4.8). This section shall detail the proposed ITS 

components and shall provide full capability to test all required ANWI 

services as well as integration testing with Purchaser Furnished 

Services and Infrastructure (PFS&I) deliverables (e.g. NATO Public 

Key Infrastructure, NATO Enterprise Directory Service, etc.) and 

other new NATO Headquarters projects (e.g. Electronic Security 

Systems, Building Management System, etc.). 

3.6.4.3.8. The HLD shall include the high level concept and discussion of the 

other ANWI services that will be detailed in the later design phases. 


NATO UNCLASSIFIED



3.6.4.4. The Bidder’s HLD shall include technical details about the different 

hardware and software components (note: details shall be provided as 

part of the high level design and any individual datasheets are to be 

provided in a separate binder not included and not counted as part of 

the HLD page count). 

3.6.4.5. The Bidder’s HLD shall provide details on the optimizations to the 

solution for lowering the overall Total Cost of Ownership (TCO) of the 

ANWI while still complying with all requirements in this IFB. 

3.6.4.6. The Bidder shall provide a separate service breakdown document listing 

all the products (hardware and software) per service. This document 

shall be comprehensive and include details of license types and 

quantities which shall not count against the page requirement of the 

HLD. 

3.6.4.7. The Bidder shall address how innovation is embraced in the HLD and 

will be realised in the ANWI solution. 

3.6.4.8. The Bidder shall provide an initial Security Risk Assessment of the 

provided HLD. 

3.6.4.9. The Bidder shall provide a Requirements Traceability Matrix 

documenting the cross-referencing of contractual requirements to the 

contents of the proposed ANWI initial high level design document. 

3.6.5. SERVICE MANAGEMENT & CONTROL CONCEPT 

3.6.5.1. Operational Support Plan 

3.6.5.1.1. The Bidder shall propose an Operational Support Plan (OSP) 

describing the management of ANWI services such that the OSP is 

in line with ITIL v3. 

3.6.5.1.2. The proposal shall serve as the initial OSP (REF SOW 7.4.1). for the 

ANWI project and expanded during the project’s implementation 

phase along with the respective SLA’s. 

3.6.5.1.3. The initial OSP shall detail the different ANWI services and their 

operational procedures; including, but not limited to, service 

requests, change requests, monitoring and reporting and 

configuration management. 

3.6.5.1.4. The Bidder’s OSP shall provide details on the proposed service 

organisation (with detailed function descriptions and support staff 

numbers for each of the described functions) needed to fulfil the 

ANWI’s operational support requirements. 


NATO UNCLASSIFIED



3.6.5.1.5. The Bidder’s OSP shall describe the initial ANWI system capacity 

requirements and how capacity changes shall be implemented and 

managed. 

3.6.5.1.6. The OSP shall be used as the basis to estimate the manpower, 

hardware and software costs for the ANWI’s Total Cost of 

Ownership. 

3.6.5.2. Integrated Logistics Support Plan (ILSP) 

3.6.5.2.1. The Bidder shall provide an initial ILSP that addresses the 

maintenance and warranty concept for NATO owned property and 

identifies the ANWI equipment warranty and maintenance support 

procedures irrespective if the equipment is NATO or Contractor 

operated. 


NATO UNCLASSIFIED



SECTION 4 

BID EVALUATION AND CONTRACT AWARD 

4.1. General 

4.1.1. The evaluation of Bids will be made by the Purchaser solely on the basis 

of the requirements specified in this Invitation for Bid. 

4.1.2. All Bids will be evaluated solely using the formula, evaluation criteria and 

factors contained herein. Technical Proposals will be evaluated strictly 

against the technical criteria and not against other Technical Proposals 

submitted. 

4.1.3. The evaluation of Bids and the determination as to the Best Value Score 

will be based only on that information furnished by the Bidder and 

contained in his Bid. The Purchaser shall not be responsible for locating 

or securing any information that is not identified in the Bid. 

4.1.4. The Bidder shall furnish with his Bid all information requested by the 

Purchaser in Book I, Section 3, Bid Preparation Instructions. Significant 

omissions and/or cursory submissions will result in a reduced Best Value 

Score and may result in a determination of non-compliance without 

recourse to further clarification. The information provided by the Bidder in 

its proposal shall be to a level of detail necessary for the Purchaser to 

fully comprehend exactly what the Bidder proposes to furnish as well as 

his approach and methodologies. 

4.1.5. During the evaluation, the Purchaser may request clarification of the Bid 

from the Bidder and the Bidder shall provide sufficient detailed 

information in connection with such requests as to permit the Purchaser 

to make a final assessment of the Bid based upon the facts. The purpose 

of such clarifications will be to resolve ambiguities in the Bid and to 

permit the Bidder to state his intentions regarding certain statements 

contained therein. The purpose of the clarification stage is not to elicit 

additional information from the Bidder that was not contained in the 

original submission or to allow the Bidder to supplement cursory answers 

or omitted aspects of the Bid. The Bidder is not permitted any cardinal 

alteration of the Bid regarding technical matters and shall not make any 

change to his price quotation at any time. 

4.1.6. The Purchaser reserves the right, during the evaluation and selection 

process, to verify any statements made concerning experience, facilities, 

or existing designs or materials by making a physical inspection of the 

Bidder's facilities and capital assets. This includes the right to validate, 

by physical inspection, the facilities and assets of proposed 

Subcontractors. 

4.1.7. The evaluation will be conducted in accordance with NATO Infrastructure 

Bidding Procedures as set forth in the document, and the Best Value 

evaluation procedures set forth in AC/4-D(2008)0002-REV1, “Procedures 


NATO UNCLASSIFIED





and Practices for Conducting NSIP International Competitive Bidding 

Using Best Value Methodology”. The Bid evaluation methodology to be 

followed, including the top-level evaluation criteria and their weighting 

factors, were agreed by the NATO Infrastructure Committee. 

4.2. Best Value Award Approach and Bid Evaluation Factors 

4.2.1. The Contract resulting from this IFB will be awarded to the Bidder whose 

conforming offer provides the Best Value to NATO, as evaluated by the 

Purchaser in compliance with the requirements of this IFB and according 

to the evaluation method specified in this SECTION 4 . 

4.2.2. The overall score for each compliant Bidder will be derived using the 

following formula: 

Best Value Score = E+M+S+R+P 

where: 

E = Weighted Engineering Score 

M = Weighted Management Score 

S = Weighted Supportability Score 

R = Weighted Risk Score 

P = Weighted Price Score 

4.2.3. The maximum possible Best Value Score is 100; the minimum possible 

is zero. The Bid with the highest Best Value Score will be will be 

recommended to be the Apparent Successful Bidder. 

4.2.4. Only for the purpose of the Best Value evaluation, P (the Weighted Price 

Score) is defined as the Total Cost of Ownership as detailed in the TCO 

Calculation tab of the Bidding Sheets 

4.2.5. Evaluation Criteria. 

4.2.5.1. Price: 50% weight, with the Price Score (P) derived using the following 

formula: 

Price Score = 100 * (1-(Bid Price / (2*Average Bid Price)) 

4.2.5.1.1. Using this formula, a price quotation that is exactly equal to the 

average price of all Bids would receive a score of 25 of the 50 points 

available. A price quotation that is one-half of the average price of 

all Bids would receive a score of 37.5 of the 50 points available, and 

a price quotation of two times the average Bid price would receive a 

score of 0. Price Quotations in excess of two times the average Bid





price would likewise receive a score of 0, even though the formula 

would generate a negative figure. 

4.2.5.1.2. Bidders shall note that any Bid in excess of the stated ceiling price 

set forth in paragraph 3.5.2.1 above may not be scored as the Bid 


4.2.5.2. Technical 50 % weight, with the cumulative Technical Score determined 

by evaluating and scoring the different technical (sub-)criteria in 

accordance with the prescriptions of the paragraphs below. 

4.2.5.2.1. Engineering: 70% weight, based on the following sub-criteria which 

appear in descending order of importance: 

4.2.5.2.1.1 ANWI Service Design 

4.2.5.2.1.2 Integrated Test Service (ITS) design 

4.2.5.2.1.3 Innovation 

4.2.5.2.2. Management: 15% weight, based on the following sub-criteria listed 

in order of descending importance: 

4.2.5.2.2.1 Project Plans 

4.2.5.2.2.2 Bidder Qualifications 

4.2.5.2.3. Supportability: 10% weight, based on the following sub-criteria listed 

in descending order of importance: 

4.2.5.2.3.1 Support Plan 

4.2.5.2.3.2 Design Components 

4.2.5.2.4. Risk: 5% weight based on the following sub-criteria listed in order of 

descending importance: 

4.2.5.2.4.1 Project Risk 

4.2.5.2.4.2 Design Risk 

4.3. Evaluation Procedure 

4.3.1. The evaluation will be done in a four step process, as described below: 

4.3.1.1. Step 1: Administrative and Contractual Compliance 

4.3.1.1.1. Bids received will be reviewed for compliance with the mandatory 

administrative requirements specified in paragraph ‎4.4 and 

contractual compliance. Bids not meeting all of the mandatory 

administrative or contractual requirements may be determined to be 

non-compliant and not considered for further evaluation.



4.3.1.2. Step 2: Technical Evaluation 

4.3.1.2.1. In Step 2 Bids will have their Technical Proposals evaluated against 

predetermined top-level criteria and identified sub-criteria (see 

paragraph 4.2.5.2 above), and scored accordingly. This evaluation 

will result in “raw” or unweighted technical scores against the 

criteria. 

4.3.1.2.2. Bidders are advised that any Bid whose Technical Proposal receives 

a score of less than 20% of the unweighted raw score possible in 

any of the sub-criteria listed in paragraph 4.2.5.2 may be determined 

by the Purchaser to be non-compliant and not considered for further 

evaluation. 

4.3.1.3. Step 3: Price Evaluation 

4.3.1.3.1. The Price Quotations of all Bids not considered non-compliant under 

the previous steps will be opened, evaluated and scored in 

accordance with paragraph 4.6. 

4.3.1.4. Step 4: Determination of Apparent Successful Bidder 

4.3.1.4.1. Upon completion of the Price Evaluation, the Apparent Successful 

Bid will be determined in accordance with paragraph 4.7 hereafter. 

4.4. Evaluation Step 1 - Administrative and Contractual Compliance 

4.4.1. Bids will be reviewed for compliance with the formal requirements for Bid 

submission as stated in this IFB and the content of the Bid Administration 

Package. The evaluation of the Bid Administration Package will be made 

on its completeness, conformity and compliance to the requested 

information. This evaluation is not subject to scoring in accordance with 

Best Value procedures but is made to determine if a Bid complies with 

the requirements of the Bidding Instructions and Prospective Contract. 

Specifically, the following requirements shall be verified: 

4.4.1.1. The Bid was received by the Bid Closing Date and Time, 

4.4.1.2. The Bid is packaged and marked properly, 

4.4.1.3. The Bid Administration Package contains the documentation listed in 

paragraph 3.4 above and complies with the formal requirements 

established in paragraph 3.1 above. 

4.4.1.4. The Bidder has not taken exception to the Terms and Conditions of the 

Prospective Contract or has not qualified or otherwise conditioned his 

offer on a modification or alteration of the Terms and Conditions or the 

language of the Statement of Work. 

4.4.1.5. Evaluation of Conflict of Interest Documentation 


NATO UNCLASSIFIED



4.4.1.5.1. The Purchaser will evaluate the Bidder’s submission as detailed in 

Book I Section III Paragraph 3.4.3 and resort to the disqualification 

of the Bid in those cases in which it is deemed that the Bidder’s 

relationships with Contractors/Subcontractors performing work or 

having performed work under the New NATO Headquarters (NNHQ) 

Project could constitute a real or apparent conflict of interest, could 

in any manner or form influence or appear to influence the capacity 

of the Bidder to render unbiased service or otherwise result in an 

advantage during the course of the performance under the 

prospective Contract and any proposed conflict of interest mitigation 

plan proposed by the Bidder does not satisfactory resolve the 

conflict of interest in place. 

4.4.1.5.2. Conversely, should the Purchaser deem that the Bidder’s conflict of 

interest mitigation plan adequately addresses the concerns relevant 

to any conflict of interest, it will make such plan part of any 

awarded Contract and subject to the stipulation of Clause 25 of the 

prospective Contract Special Provisions. Equally in those cases 

where the Bidder declares that no apparent or real conflict of interest 

exists such condition shall be reflected in any resulting Contract and 

made subject to the prescription of Clause 25 of the prospective 

Contract Special Provisions. 

4.4.1.5.3. In the event that, during the evaluation of the Bids, the Purchaser 

determines or suspects that the Bidder has not disclosed a real or 

apparent conflict of interest of which it was knowledgeable at the 

time of Bid submission, in breach of paragraphs 4.4.1.5.1 and 

4.4.1.5.2, the Purchaser reserves the right to declare the Bid noncompliant. 

4.4.1.6. Contractual compliance will be determined primarily by receipt of an 

unqualified and completed Annex B-6. 

4.4.2. A Bid that fails to conform to the above requirements may be declared 

non-compliant and may not be evaluated further by the Purchaser. 

4.4.3. Bids that are determined to be administratively compliant will proceed to 

Step 2, Technical Evaluation. 

4.4.4. Notwithstanding paragraph 4.4.3, if it is later discovered in the evaluation 

of the Bid Administration Package, Technical Proposal or the Price 

Quotation that the Bidder has taken exception to the Terms and 

Conditions of the Prospective Contract, or has qualified and/or otherwise 

conditioned his offer on a modification or alteration of the Terms and 

Conditions or the language of the Statement of Work, the Bidder may be 

determined to have submitted a non-compliant Bid at the point in time of 

discovery. 


NATO UNCLASSIFIED



4.5. Evaluation Step 2 - Technical Evaluation 

4.5.1. The Technical Proposal will be evaluated against the criteria and subcriteria 

set forth in paragraph 4.2 above. For some sub-criteria, there 

may be additional supporting factors at the next lower level. These lower 

level factors are not published here but are predetermined and included 

in the Technical Evaluation Weighting Scheme sealed before Bid 

Opening. The following paragraphs identify the aspects to be examined 

in the Technical Proposal evaluation and rating. 

4.5.2. Bidder Qualifications 

4.5.2.1. Bidder qualifications will be evaluated based on an assessment of 

corporate experience; the corporate structure and capabilities; and 

individual skills and experience of the prime contractor and his identified 

Subcontractors/partners, including the following factors: 

4.5.2.2. The Bid provides evidence of relevant and recent experience of the 

Bidder in the design and implementation and integration of projects 

similar to the subject procurement, including: 

4.5.2.3. The Bid provides relevant and successful corporate experience in at 

least three contracts within the last three years for which the Bidder 

integrated similar systems to meet military or government requirements. 

4.5.2.4. The Bid provides examples of previous experience of the Prime 

Contractor in designing, integrating, implementing, testing and fielding 

systems that store, process and transmit either NATO (or military or 

governmental) classified or business confidential information, and in 

consequence, subject to security accreditation, in accordance with 

NATO (or military or governmental or business confidential) Security 

Policy and supporting directives and guidance. 

4.5.2.5. The Bid provides relevant and successful corporate experience of the 

major Subcontractors for critical components. 

4.5.2.6. The Bid provides relevant experience and expertise in providing 

warranty support and repair-and-replacement service for information 

systems for large, geographically-dispersed organisations. 

4.5.2.7. The Bid provides evidence of appropriate corporate capabilities of the 

Bidder, including: 

4.5.2.7.1. Adequate and appropriate corporate resources available to support 

the Project. 

4.5.2.7.2. A well-established and mature level of capability in its system 

integration and testing practices and tools. 

4.5.2.7.3. Evidence of sufficient numbers of individuals with the skill and 

experience to meet the requirements of the Contract, including: 


NATO UNCLASSIFIED



4.5.2.7.4. For each role identified including those identified by the Bidder, 

evidence that the resumes and support data provided meet or 

exceed the experience and educational criteria stated in the SOW. 

4.5.2.7.5. Evidence that the proposed individuals have the expected 

knowledge, capability and experience to meet the requirements of 

this contract. The more the resumes of the proposed individuals 

exceed the experience and educational criteria; the more those 

individuals have already faced and accomplished successfully 

challenges similar to those raised by this project; and the more this 

experience is detailed and justified, the better. 

4.5.3. Key Personnel 

The Bid clearly identifies the contractor’s current cleared staff and provides the same 

information required above for the major Subcontractors. 

4.5.3.1. The Bidder has provided the resumes (CVs) and supporting certification 

documentation of proposed Key Personnel that meet or exceed the 

experience and educational criteria stated hereunder and in the SOW 

4.5.3.2. The Bidder explains his vetting process ensuring that the proposed Key 

Personnel have the expected knowledge, capability and experience to 

meet the requirements of this Contract. 

4.5.3.3. ANWI Project Manager 

4.5.3.3.1. The ANWI Contractor has designated an ANWI Project Manager 

(PM) who will direct and co-ordinate the activities of the ANWI 

Contractor's project team. 

4.5.3.3.2. The ANWI PM has a current NATO SECRET security clearance. 

4.5.3.3.3. The ANWI PM is the ANWI Contractor's primary interface to the 

Purchaser’s Project Manager and shall conduct all major project 

design, test, and review meetings. 

4.5.3.3.4. The ANWI PM has a University Degree in Electronic Engineering, 

Computer Science, Telecommunications, or related discipline, 

preferably equivalent to a Master’s, supported by relevant 



4.5.3.3.5. The ANWI PM has a current Project Management (e.g. PRINCE2 

Practitioner and/or PMI Project Management Professional ( PMP)) 

certification. 

4.5.3.3.6. The ANWI PM has a minimum of ten (10) years’ experience as an 

ICT Project Manager as supported by project references, points of 

contact, and descriptions/scope of the projects managed. 


NATO UNCLASSIFIED





4.5.3.3.7. The ANWI PM has a minimum experience of five (5) years (outside 

the time a Project Manager) gained within ICT procurement, 

implementation and management in projects similar to the ANWI 

Project, as supported by project references, points of contact, and 

description of role/responsibilities/activities executed. 

4.5.3.3.8. The ANWI PM has a minimum of 1 year experience in ICT QA 

activities, supported by supported by project references, points of 

contact, and description of role/responsibilities/activities executed. 

4.5.3.3.9. The ANWI PM has minimum of 2 years’ experience in projects 

where ICT migration/transition was exercised in a managerial 

(technical or project) role responsible for the planning, designing and 

execution of migration/transition activities, as supported by project 

references, points of contact, and descriptions of the 


4.5.3.3.10. The ANWI PM has knowledge and experience with processes for 

integration and testing. 

4.5.3.3.11. The ANWI PM has a demonstrated spoken and written fluency in 

English, at a minimum level of 4343as defined in STANAG 6001. 

4.5.3.4. ANWI Technical Lead 

4.5.3.4.1. The ANWI Contractor has designated a Technical Lead (TL) for the 

project to lead the analysis, design, development, integration, and 

follow-on enhancement efforts of the Contractor. 

4.5.3.4.2. The ANWI TL has a current NATO SECRET security clearance. 

4.5.3.4.3. The ANWI TL has a University Degree in Electronic Engineering, 


preferably equivalent to a Master’s, supported by relevant 



4.5.3.4.4. The ANWI TL has demonstrated practical experience in 

Infrastructure (processing, virtualization, storage, switches), 

supported by valid certification of at least the following areas: 

Microsoft (MCSE), CISCO (CCSP) or valid comparable (products 

used in the ANWI design) certification. 

4.5.3.4.5. The ANWI TL has a minimum of two (2) years’ experience designing 

and implementing high-availability server rooms as supported by 

project references, points of contact, and technical descriptions of 

the projects implemented. 

4.5.3.4.6. The ANWI TL has a minimum of three (3) years’ experience 

designing and implementing local area networks in projects similar 

to the ANWI Project, as supported by project references, points of



contact, and description of role/responsibilities/activities held in 

these projects. 

4.5.3.4.7. The ANWI TL has a minimum of two (2) years’ experience as a 

technical manager responsible for the planning, designing and 

execution of projects where an Active Directory and subsequent 

application and data migration/transition activities were exercised; as 


description of the role/responsibilities/activities during this time. 

4.5.3.4.8. The ANWI TL has a minimum of 1 years’ experience in ICT QA 

activities, supported by supported by project references, point of 

contact, and description of role/responsibilities/activities. 

4.5.3.4.9. The ANWI TL has a minimum of three (3) years’ experience as a 

team leader or project manager to ensure the technical management 

oversight of a: LAN designer, Server Room designer, UCC designer, 

communications engineer and systems integrator; as supported by 

project references, points of contact, and technical description of the 


4.5.3.4.10. The ANWI TL has knowledge and experience with QA standards 

(either AQAP or ISO), processes for integration and (pre) migration 

testing. 

4.5.3.4.11. The ANWI TL has a demonstrated spoken and written fluency in 

English, at a minimum level of 4343as defined in STANAG 6001. 

4.5.3.4.12. The ANWI TL has an ITIL v3 Intermediate Level Certification and 

has at least 12 points in the Service Capability Area. 

4.5.3.5. Test Director 

4.5.3.5.1. The ANWI Contractor has designated a qualified individual to serve 

as the ANWI Test Director (TD) for the ANWI Contractor provided 

Integration Test Service (ITS) and responsible for all ANWI testing 

as well as reporting oversight of all NNHQ Host Nation related test 

activities conducted in either the ITS or NNHQ. 

4.5.3.5.2. The ANWI TD oversees the ITS manager (where the ITS manager is 

responsible for providing the ITS as a service (see Section 24.2.7 for 

labour category requirements)). 

4.5.3.5.3. The ANWI TD has a University Degree in Electronic Engineering, 


preferably equivalent to a Master’s and supplemented by relevant 

postgraduate qualifications, supported by relevant certificates/ 

diplomas. Exceptionally extensive relevant experience may be 

considered if the above qualifications are not met. 


NATO UNCLASSIFIED



4.5.3.5.4. The ANWI TD has integration and testing engineering skills with five 

(5) years’ experience as part of large ICT projects, supported by 

project references, point of contact, and description of 


4.5.3.5.5. The ANWI TD has demonstrated practical experience in planning, 

conducting and assessing Integration and Testing activities in 

support of large ICT projects for at least three (3) years, supported 

by project references, point of contact, and description of 


4.5.3.5.6. The ANWI TD has demonstrated practical experience in testing of IT 

infrastructure, core services where the role of test engineer or 

integration engineer was exercised, supported by project references, 

point of contact, and description of role/responsibilities/activities. 

4.5.3.5.7. The ANWI TD has demonstrated practical experience in ICT 

migrations where the role of test engineer or integration engineer 

was exercised for migration of ICT services (Active Directory, 

business applications and associated data), supported by project 



4.5.3.5.8. The ANWI TD has demonstrated practical knowledge and 

experience with QA standards (either AQAP or ISO), processes for 

integration and (pre) migration testing. 

4.5.3.5.9. The ANWI TD has a demonstrated spoken and written fluency in 

English, as defined in STANAG 6001 at a minimum level of 4343. 

4.5.4. Project Management 

4.5.4.1. Project Management Plan 

4.5.4.1.1. The Bidder provides a description of their project management 

approach to be used for this project that is coherent with delivering 

the ANWI’s scope and its objectives. 

4.5.4.1.2. The proposed PMP is compliant with Annex K Appendix 3. 

4.5.4.1.3. The Bid states that the PMP serves as the initial ANWI PMP. 

4.5.4.1.4. The proposed PMP contains the project management planning 

information so as to constitute a consistent and complete document 

that effectively permits the Purchaser to be able to assess the 

Bidder’s plan to manage to ANWI project. 

4.5.4.1.5. The proposed PMP has decomposed the project into manageable 

stages where each stage identifies the required input and exit 

approval criteria. 


NATO UNCLASSIFIED





4.5.4.1.6. The proposed PMP identifies the Contractor’s organisation, in 

particular all major Contractor units and any Subcontractors involved 

in meeting the requirements of the Contract, and the portion of the 

overall effort or deliverable item for which they are responsible. In 

case several Contractor units or Subcontractors are involved, the 

management of these units and Subcontractors are described, 

reasons for this organisation are justified, and expected benefits of 

this organisation for the Purchaser are explained. 

4.5.4.1.7. The proposed PMP describes the organisation for the proposed 

Project Team that identifies all the required roles (key and others) of 

the team members of the PMO, describing the lines of reporting and 

oversight. The description reflects clear lines of responsibility, 

authority, and reporting. For each role identified, the proposed 

individuals meet or exceed the experience and educational criteria 

stated in SOW. 

4.5.4.1.8. The proposed PMP demonstrates that individuals have the expected 

knowledge, capability, and experience to meet the requirements of 

this Contract. The team collectively represents a solid knowledge 

and experience base for carrying out the project. 

4.5.4.1.9. The proposed PMP describes the PMO in terms of 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 proposed resources 

are adequate for the tasks. 

4.5.4.1.10. The proposed PMP describes the project management processes, 

including the phases and their staffing, schedule estimate, project 

control mechanisms, issue management, configuration 

management, security management and the Purchaser involvement 

in the project management. The proposed approach is based on 

recognized project management practices and reflects a mature 

level of management capability. 

4.5.4.1.11. The proposed PMP describes the relationship of the PMP to the 

various project management plans: Project Implementation Plan, 

Testing and Acceptance Plan, Configuration Management Plan, Risk 

Management Plan, Service Delivery Plan, Integrated Logistic 

Support Plan and Training Plan, so that the approach shows a 

coherent and integrated approach to implementation and support. 

4.5.4.1.12. The proposed PMP details the mechanism through which the plans 

will be maintained during the lifecycle of the Contract and 

demonstrates that the Bidder can accommodate changes in scope in 

a controlled manner. 

4.5.4.2. Project Implementation Plan (PIP)



4.5.4.2.1. The Bid states that the provided PIP serves as the ANWI’s initial 

PIP. 

4.5.4.2.2. The proposed PIP clearly and accurately identifies the Bidder’s 

understanding of the project’s scope, including: major deliverables; 

stages with associated activities and resources; assumptions; 

timelines and constraints/dependencies. 

4.5.4.2.3. The proposed PIP provides the Purchaser with insight into the 

Bidder’s plans, capabilities, and ability to satisfactorily implement the 

entire project in conformance with the requirements as specified in 

the SOW. 

4.5.4.3. Schedule 

4.5.4.3.1. The proposed schedule identifies all Contract events and 

milestones, including Contract-related Purchaser activities and 

events. The schedule correlates with the WBS and is traceable to 

performance and delivery requirements of the SOW. 

4.5.4.3.2. The duration, sequence, and resourcing of the tasks reflect a 

coherent approach to execution and a realistic assessment of the 

scope of work involved. The implementation and deployment of 

capabilities support the delivery of ANWI services and are compliant 

with meeting the NNHQ programme milestones such that the project 

shall be complaint with the milestones in Annex A of the SOW. 

4.5.4.3.3. The Purchaser will evaluate the Bidder’s ability to propose an 

effective Project Schedule as part of the Proposed PMP, as 

described in the SOW. 

4.5.4.3.4. The proposed PMP clearly defines the Schedule Control 

mechanisms implemented by the Bidders. 

4.5.4.4. Work Breakdown Structure (WBS) 

4.5.4.4.1. The Bidder provides a WBS that provides the level of detail of all 

necessary activities for the effective planning and management of 

the ANWI project to ensure that the Bidder shall be able to 

effectively control the project. 

4.5.4.4.2. The WBS is consistent with the requirements for the SOW in its 

description of all engineering efforts for specifying, designing, 

developing, testing, accrediting, installing, integrating and supporting 

the delivery of the ANWI solution. 

4.5.4.4.3. The proposed WBS includes a definition of the major tasks/work 

packages and the relationship between the tasks/work packages the 

sub-CLINs. 


NATO UNCLASSIFIED



4.5.4.4.4. The provided WBS is compliant to the SOW and adequately and 

appropriately decomposes the tasks/work packages to a level that 

exposes all project risk factors and allows accurate estimate of each 

work item’s duration, resource requirements, inputs and outputs, and 

predecessors and successors. 

4.5.4.4.5. The Bidder’s WBS incorporates the identified NNHQ programme 

milestones and reflects the time constraints in realising the ANWI 

solution. 

4.5.4.4.6. The Bidder’s WBS incorporates and reflects all Subcontractor ANWI 

tasks and external contractor dependencies. 

4.5.4.4.7. The proposed WBS provides appropriate and sufficient support for 

the Project Management activity and demonstrates that the Bidder 

has a realistic knowledge of the level of effort and labour mix 

associated with the different tasks necessary to complete this 

Contract. 

4.5.4.5. Change Management Plan 

4.5.4.5.1. The Purchaser will evaluate the appropriateness and completeness 

of the change management process against the Bidder’s preferred 

project management methodology. 

4.5.4.5.2. The Bidder reflects the importance of the Change Management Plan 

to the ANWI project. 

4.5.4.6. Risk Register 

4.5.4.6.1. The Purchaser will assess the Bidder’s ability to identify critical 

project risks and to assess and propose technical and organizational 

measures to mitigate these risks. 

4.5.4.7. Issue Management Plan 

4.5.4.7.1. The Purchaser will evaluate the appropriateness and efficiency of 

the proposed Issue Management process. 

4.5.5. ANWI Initial High Level Design 

4.5.5.1. The Purchaser will assess that the Bidder provided draft of the initial 

high level design and architectural concepts does not exceed 120 

pages; system drawings are to be included in an annex and will not 

count against the submitted page count. 

4.5.5.2. The Purchaser will evaluate the quality and adequacy of the proposed 

ANWI initial high level design with respect to its ability to successfully 

satisfy the requirements of the ANWI SOW. 


NATO UNCLASSIFIED





4.5.5.3. The proposed ANWI initial high level design will be evaluated on the 

basis of the comprehensiveness of the approach and the maturity of its 

proposed technical solution for the cross domain gateways, the server 

room and technical equipment room (TER) design, the network 

infrastructure service designs of the four security domains, the ITS 

design solution and approach to other ANWI service designs. 

4.5.5.4. The proposed ANWI initial high level design will be evaluated regarding 

its feasibility and suitability to the requirements. 

4.5.5.5. Specific aspects of the proposed initial high level design address that 

will be assessed: 

4.5.5.5.1. The Bidder’s documented estimate of the power and cooling 

requirements needed for his proposed ANWI design for each 

security domain, the collective installation of each server room and 

for each Technical Equipment Room (TER) to demonstrate that the 

proposed design complies with the design constraints. 

4.5.5.5.2. That the Bidder has mathematically demonstrated how the proposed 

design meets or exceeds the availability and reliability targets for 

each capability and service. 

4.5.5.5.3. The Bidder has provided written proof (calculations) of ANWI 

services meet the performance, capacity, availability requirements. 

4.5.5.5.4. The Bidder has provided a list of components defining the ITS and 

how the provided components will be combined to support all 

possible ANWI tests with 100 simulated users. 

4.5.5.5.5. The Bidder has described the SMC concept design and high level 

outlined processes. 

4.5.5.5.6. The Bidder has provided a detailed cross domain gateway design for 

the various types of gateways. 

4.5.5.5.7. The Bidder has proposed the concepts for the solution for the other 

ANWI services that will be designed later in the ANWI project 

process. 

4.5.5.5.8. The Bidder has addressed how he plans to embrace innovation and 

how innovation will be incorporated and supported in his design thus 

ensuring that a modern capability is provided for the new NATO 

Headquarters building. 

4.5.5.5.9. The Bidder has addressed the bandwidth design for the wired and 

wireless networks. 

4.5.5.5.10. The Bidder has provided a logical model diagram of the proposed 

ANWI Design demonstrating the Bidder’s understanding of the 

SOW’s requirements.





4.5.5.5.11. That the proposed ANWI Design includes an initial Security Risk 

Assessment (SRA of the proposed design) and the description of the 

security mechanisms needed to mitigate the risks of the Bidder’s 

proposed design. 

4.5.5.5.12. The Bid provides the Bidder’s understanding and ability to identify 

and assess critical security design risks, producing security-related 

documentation, conducting security testing activities, delivering 

security hardened solutions implementing (NATO) security settings 

and propose technical and organizational measures to mitigate 

these risks. 

4.5.5.5.13. The Bidder has provided a Requirements Traceability Matrix 

documenting the cross-referencing of Contractual requirements to 

the contents of the proposed ANWI initial high level design 

document. 

4.5.5.5.14. The SIP (of the bidder’s choosing) is one of the six cross domain 

gateways, meets the SIP requirements and is provided as an 

appendix to the submitted design. 

4.5.6. SMC concept 

4.5.6.1. Proposed Operational Support Plan 

4.5.6.1.1. The Bid provides a proposed Operational Support Plan (OSP) 

consistent with the requirements of the SOW (SOW section 7.4) 

describing processes and activities to effectively meet requirements 

for service delivery supporting ANWI FOC. 

4.5.6.1.2. The Purchaser will evaluate how the Bidder proposes to handle: 

service requests, change requests, monitoring and reporting and 

configuration management. 

4.5.6.1.3. The Purchaser will evaluate the details on the proposed service 

organisation offered to fulfil the operational support requirements. 

4.5.6.1.4. The Purchaser will evaluate the detailed functional duty descriptions 

and appropriateness of support staff numbers for each of the 

described service operational functions. 

4.5.6.1.5. Total Cost of Ownership 

4.5.6.1.5.1 The Purchaser will evaluate the Bidder’s ability to propose a 

comprehensible total cost of ownership rationale (as reflected in the 

Operational Support Plan Proposal) with respect to its rationales to 

minimise the total cost of ownership. 

4.5.6.1.5.2 The Purchaser will evaluate the suitability of the proposed 

comprehensible total cost of ownership rationale in the OSP to 

balance costs expenditures and controls between implementation



phase and support phases. Detailed Business Cases for each 

relevant or significant configuration items of the proposed solution 

shall be explicitly given. 

4.5.6.1.5.3 The Purchaser must understand from the Bid the Bidder’s methods 

in selecting the different COTS and/or in executing 

integration/development activities to build their proposed solution 

for ANWI FOC, in order to minimise the total cost of ownership. 

4.5.6.1.6. The Bid addresses how the ANWI service management will be 

performed and addresses the roles and functions with supporting 

process concepts that are aligned with ITIL v3. 

4.5.6.2. Integrated Logistics Support Plan 

4.5.6.2.1. The Purchaser will evaluate the quality and adequacy of the 

proposed life-cycle support planning documentation (i.e., Proposed 

Service Delivery Plan and Proposed Integrated Logistic Support 

Plan) with respect to its ability to successfully satisfy the 

requirements for supportability of the ANWI FOC. 

4.5.6.2.2. The Purchaser will evaluate the proposed life-cycle support planning 

documentation will be evaluated on the basis of the 

comprehensiveness of the approach, its feasibility, and 

appropriateness to the requirements. 

4.5.6.2.3. The proposed life-cycle support documentation will be evaluated in 

its compliance to the requirements for the respective plans specified 

in the SOW and the sufficiency of the detail provided. 

4.6. Evaluation Step 3 - Price Evaluation 

4.6.1. The Bidder’s Price Quotation will be first assessed for compliance 

against the following standards: 

4.6.1.1. The total price for CLINs 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14,15 

and 16 does not exceed EUR 81,726,023 (eighty-one million seven 

hundred twenty-six thousand twenty-three Euro). 

4.6.1.2. The Price Quotation meets the requirements for preparation and 

submission of the Price Quotation set forth in the Bid Preparation 

Section and the Instructions for Preparation of the Bidding Sheets in 

Annex A-1 

4.6.1.3. Detailed pricing information has been provided and is adequate, 

accurate, traceable, and complete. 

4.6.1.4. The Price Quotation meets requirements for price realism and balance 

as described below in paragraph 4.6.4. 


NATO UNCLASSIFIED





4.6.2. A Bid which fails to meet the compliance standards defined in this 

section may be declared non-compliant and may not be evaluated further 

by the Purchaser. 

4.6.3. Basis of Price Comparison 

4.6.3.1. The Purchaser will convert all prices quoted into EURO for purposes of 

comparison and computation of price scores. The exchange rate to be 

utilised by the Purchaser will be the average of the official buying and 

selling rates of the European Central Bank at close of business on the 

last working day preceding the Bid Closing Date. 

4.6.3.2. The Price to be inserted into the formula specified at paragraph 4.2.5.1 

will be derived from the Grand Total of CLINs 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 

11, 12, 13, 14, 15, including Evaluated Options CLIN 16, 17, 18 ,19. 

4.6.3.3. Please see 4.2.4 for clarification of the Total Cost of Ownership 

4.6.4. Price Balance and Realism 

4.6.4.1. In those cases in which the prices quoted in relation with this Invitation 

for Bid appear to be unreasonably low in relation to the performance 

required under the prospective Contract and/or the level of effort 

associated with the tasks, the Purchaser will reserve the right to request 

the Bidder clarifications aimed to demonstrate the rationale for such 

circumstances. 

4.6.4.2. Indicators of an unrealistically low Bid may be the following, amongst 

others: 

4.6.4.2.1. Labour Costs that, when amortised over the expected or proposed 

direct labour hours, indicate average labour rates far below those 

prevailing in the Bidder’s locality for the types of labour proposed. 

4.6.4.2.2. Direct Material costs that are considered to be too low for the 

amounts and types of material proposed, based on prevailing market 

prices for such material. 

4.6.4.2.3. Numerous Line Item prices for supplies and services that are 

provided at no cost or at nominal prices. 

4.6.4.3. If the Purchaser has reason to suspect that a Bidder has artificially 

debased its prices in order to secure Contract award, the Purchaser will 

request clarification of the Bid in this regard and the Bidder shall provide 

explanation on one of the following bases: 

4.6.4.3.1. An error was made in the preparation of the price quotation. In such 

a case, the Bidder must document the nature of the error and show 

background documentation concerning the preparation of the price 

quotation that makes a convincing case that a mistake was made by 

the Bidder. In such a case, the Bidder shall petition the Purchaser to





either remain in the competition or accept the Contract at the offered 

price, or to withdraw from the competition. 

4.6.4.3.2. The Bidder has a competitive advantage due to prior experience or 

industrial/technological processes that demonstrably reduce the 

costs of Bidder performance and therefore the price offered is 

realistic. Such an argument must support the technical proposal 

offered and convincingly and objectively describe the competitive 

advantage and the net savings achieved by this advantage over 

standard market practices and technology. 

4.6.4.3.3. The Bidder recognises that the submitted price quotation is 

unrealistically low compared to its cost of performance and, for 

business reasons, the Bidder is willing to absorb such a loss. Such 

as statement can only be made by the head of the business unit 

submitting the Bid and will normally be made at the level of Chief 

Operating Officer or Chief Executive Officer. In such a case, the 

Bidder shall estimate the potential loss and show that the financial 

resources of the Bidder are adequate to withstand such reduction in 

revenue. 

4.6.4.4. If a Bidder fails to submit a comprehensive and compelling response on 

one of the bases above, the Purchaser may determine the Bid 

submitted as non-compliant. If the Bidder responds on the basis of 

4.6.4.3.1 above and requests to withdraw from the competition, the 

Purchaser may, depending on the nature and gravity of the mistake, 

allow the Bidder to withdraw. 

4.6.4.5. If the Purchaser accepts the Bidder’s explanation of mistake in 

paragraph 4.6.4.3.1 and allows the Bidder to accept the Contract at the 

offered price, or the Purchaser accepts the Bidder’s explanation 

pursuant to paragraph 4.6.4.3.3 above, the Bidder shall agree that the 

supporting pricing data submitted with his Bid will be incorporated by 

reference in the resultant Contract. The Bidder shall agree as a 

condition of Contract signature, that the pricing data will be the basis of 

determining fair and reasonable pricing for all subsequent negotiations 

for modifications of or additions to the Contract and that no revisions of 

proposed prices will be made. 

4.6.4.6. If the Bidder presents a convincing rationale pursuant to paragraph 

4.6.4.3.2 above, no additional action will be warranted. The Purchaser, 

however, reserves its right to reject such an argument if the rationale is 

not compelling or capable of objective analysis. In such a case the Bid 


4.6.4.7. The Agency reserves the right to request prime Contractors, or the 

Subcontractor to separately identify each of the direct/indirect costs, 

advise why each is required, and provide supporting documentation to 

substantiate each charge, such as: 1) catalogue price lists and any 

applicable discounts, 2) copies of the Subcontractor's orders from



others for the same or similar items, including explanations for cost 

variations, 3) Subcontractor's internal cost estimate, or documentation 

of whatever means the Subcontractor used to arrive at the charge. 

4.6.5. Once the offered prices as described in paragraph 4.6.3.2 have been 

calculated and checked, the formula set forth in paragraph 4.2.5.1 above 

will be applied to derive the Price Score of each Bid. 

4.7. Evaluation Step 4 – Calculation of Best Value Scores 

4.7.1. Upon conclusion and approval of the Price Evaluation results, the predetermined 

weighting scheme for the Technical Evaluation will be 

unsealed and the scores for the Engineering, Management, 

Supportability, and Risk factors will be calculated for each compliant Bid. 

Then all partial scores will be fed into the formula stated in paragraph 

4.2.2 in order to obtain the Best Value Score of each Bid. 

4.7.2. The highest scored Bid will be recommended as the Successful Bid. 

4.7.3. In the unlikely event in which the calculation referred in paragraph 4.7.1 

above results in a statistical tie, the Purchaser will recommend as the 

Successful Bid the one with the best cost/technical ratio, defined as the 

lowest cost per technical score, i.e. Bid price divided by technical score. 

For the purpose of this paragraph the term Statistical Tie shall be 

construed to indicate the situation where the total weighted score of the 

highest scoring bid, that is, the weighted score of price and technical 

combined, is within 1.0% of the total weighted score of one or more 

Bidders 


NATO UNCLASSIFIED



Annex A 

Bidding Sheets 


Book I, Annex A, Page A-1



Annex A-1. 

Instructions for the Preparation of the Bidding 

Sheets 

1. INTRODUCTION 

Bid pricing requirements as addressed in this Annex are mandatory. Failure to abide 

to the prescriptions of Bid submission referred in this section may lead to the Bid 

being declared non-compliant and not being taken into consideration for award. 

No alteration of the Bidding sheets including but not limited to quantity indications, 

descriptions or titles are allowed with the sole exception of those explicitly indicated 

as allowed in this document. Additional price columns may be added if multiple 

currencies are Bid, including extra provisions for all totals. 

2. GENERAL REQUIREMENTS 

Bidders are required, in preparing their Price Quotation to utilise the Bidding Sheets 

following the instructions detailed in Section III – Bid Preparation Instructions, 

Paragraph 3.3 – Price Quotation (Part II) and hereunder. 

The prices and quantities entered on the document shall reflect the total items 

required to meet the Contractual requirements. The total price shall be indicated in 

the appropriate columns. 

In preparing the Bidding Sheets, Bidders shall ensure that the prices of the Subitems 

total the price of the major item of which they constitute a part. 

All metrics (e.g., cost associated with labour) will be assumed to be standard or 

normalised to 7.6 hour/day, for a five day working week at NATO and National sites 

and Contractor facilities. 

Should the Best Value Bid be in other than Euro currency, the award of the Contract 

will be made in the currency or currencies of the Bid. 

Bidders are advised that formulae are designed to ease evaluation of the Bidders 

proposal have been inserted in the electronic copies of the Bidding Sheets. 

Notwithstanding this the Bidder remains responsible for ensuring that their figures 

are correctly calculated and should not rely on the accuracy of the formulae 

electronic copies of the Bidding Sheets.. 

If the Bidder identifies an error in the spreadsheet, it should notify the Purchaser who 

will make a correction and notify all the Bidders of the update. 

Prices shall not include any provision for taxes or duties for which the Purchaser is 

exempt. 

Book I, Annex A, Page A-2 

NATO UNCLASSIFIED



3. INSTRUCTIONS FOR COMPLETION OF BIDDING SHEETS 

General 

1. The Excel workbook that comprises the Bidding Sheets consists of multiple 

sheets. The main sheet is the prospective SSS that comprises all the 

pricing information that will establish the Firm Fixed Price offer. 

2. The SSS-sheet also lists optional items that are subject to Purchaser 

approval before actual procurement. Some of the options are taken into the 

total price during the Bid evaluation. These options are clearly marked. 

3. The SSS is built up from different CLINs that are bundled into logical 

groupings. These instructions provide information how to complete the 

different CLIN with pricing information. 

4. Notwithstanding the above Bidders are also required to directly insert a 

“Final Total Price” in the Prospective SSS in column J. This allows a Bidder 

to make business decisions related to his price offer which may modify the 

price generated by the formulae in the Bidding Sheets. If a Bidder uses this 

opportunity a full explanation of the Price variance between the price in 

column I (Total Price) and the price manually entered in column J (Final 

Total Price) must be given. An explanation is not required if both prices are 

identical. For the purpose of the Best Value price evaluation, the prices 

entered in column J (Final Total Price) will be used. 

5. Within the Bidding Sheets the Purchaser has marked the cells requiring 

Bidders input with a yellow colour. The Bidders shall complete all yellow 

cells in the Bidding Sheets. 

6. The "Manpower (ICTM)" worksheet is included for informational purposes 

only. It indicates the current ICTM manpower in place to support NATO 

HQ. Bidder input is not required in this worksheet. 

Specific instruction for every Contract Line Item Number (CLIN) 

CLIN 1: Project Management 

1. Enter Price details in the SSS-sheet per Sub-CLIN. 

2. Provide Cost breakdown details in the “Implementation Services”-sheet 

CLIN 2: ANWI Service and System Design 

1. Enter Price details in the SSS-sheet per Sub-CLIN 


CLIN 3: Site Survey 



CLIN 4: Testing 



CLIN 5: ANWI Implementation and Transition 



CLIN 6: ANWI Service and System Operations 



NATO UNCLASSIFIED





2. The Bidder shall provide pricing for the documentation and implementation of 

the SMC processes in line with the requirement in SOW Section 7 and Annex E 

Appendix 1. The required software shall be listed under CLIN 10. 


CLIN 7: ANWI Service Improvement 


2. The Bidder shall provide pricing for the documentation and implementation of 

the SMC processes in line with the requirement in SOW Section 8 and Annex E 

Appendix 1. The required software shall be listed under CLIN 10. 


CLIN 8: Infrastructure Services Hardware and Software 

CLIN 8.1: Processing Service Equipment 

1. DO NOT enter direct price details in the SSS-sheet because the price 

details are calculated from the Processing-Sheet. 

2. On the processing sheet: 

1. Insert the requested information in the Server baseline Hardware and 

Server baseline Software tables. (this shall cover all security domains 

- NS,EAPC, Business and Public) 

2. In the Hardware baseline table the Bidder is requested to create a 

line item for every unique type of hardware he is offering for the 

ANWI processing service to cover the ANWI processing 

Requirement. - The Bidder is free to add as many rows as required. 

3. The Bidder shall provide details for every line item on: 

a. Description 

b. Part number 

c. Number of units 

d. Expected power requirement (including cooling power) 

e. Unit price 

f. Yearly support cost for up to 5 years 

4. For CLIN 8.1.1.1 - the procurement cost and support cost for 

YEAR 1,2 and 3 are transferred to the SSS-Sheet 

5. In the Software baseline table the Bidder is requested to create a line 

item for every unique type of software he is offering for the ANWI 

processing service to cover the ANWI processing Requirement. - The 

Bidder is free to add as many rows as required. 

6. List and provide price for all required Microsoft software under the 

PFE heading 





b. Unit price 

c. Yearly support cost for up to 5 years 

8. For CLIN 8.1.2.1 - the procurement cost and support cost for 

YEAR 1 are transferred to the SSS-Sheet 

CLIN 8.2: Storage Service Equipment 


details are calculated from the Storage-Sheet.





2. On the Storage sheet: 

1. Insert the requested information in the Storage baseline Hardware 

and Storage Baseline Software baseline tables. (this shall cover all 

security domains - NS,EAPC, Business and Public) 

2. In the Hardware baseline table the Bidder is requested to create a 

line item for every unique type of hardware he is offering for the 

ANWI Storage service to cover the ANWI Storage Requirement. - 

The Bidder is free to add as many rows as required. 





d. Expected power requirement (including cooling power) 

e. Unit price 

d. Yearly support cost for up to 5 years 

4. For CLIN 8.2.1. - the procurement cost and support cost for 

YEAR 1,2 and 3 are transferred to the SSS-Sheet 

5. In the Software baseline table the Bidder is requested to create a line 

item for every unique type of software he is offering for the ANWI 

processing service to cover the ANWI Storage Requirement. 


PFE heading 





b. Unit price 

c. Yearly support cost for up to 5 years 

8. For CLIN 8.2.2. - the procurement cost and support cost for 

YEAR 1 are transferred to the SSS-Sheet 

CLIN 8.3 Print/Scan Services 


details are calculated from the Print-Scan-Sheet. 

2. Print/Scan services is a Contractor Owned/Contractor Operated (COCO) 

Service. Therefore the Purchaser expects a cost for the service instead of 

a procurement cost with support. 

3. The Purchaser expects a monthly service cost per print device/location 

augmented with a cost per page for B/W and Colour. 

4. On the Print/Scan sheet: 

1. Update the quantity of print locations based on the proposed 

print/scan solution (Cross -domain or not) 

Service locations (location where a device is available to 

print/scan/copy up to a certain classification) 

187 MFP Colour printers: 

58 for NS 

107 for NR 

18 for EAPC 

4 for Public



In case of cross domain NR/NS printing nr of printers is reduced to 

129: 

107 Cross-domain NR/NS printers 

18 for EAPC 

4 for Public 

12. Provide a Unit price (per printer/location) price per year. 

3. Provide a per page price for both B/W and Colour print/Copy. 

a. The estimated number of printed/copied pages per year is 

.10.000.000 of which 70% is B/W and 30% is Colour 

4. For CLIN 8.3.1 the quantity, unit price (yearly support price) is 

transferred to the SSS-Sheet. 

5. For CLIN 8.3.2 the unit price per B/W page is transferred to the 

SSS-Sheet 

6. For CLIN 8.3.3 the unit price per Colour Page is transferred to 

the SSS-Sheet 

CLIN 8.4 Network Infrastructure Services 

a. DO NOT enter direct price details in the SSS-sheet because the price 

details are calculated from the ANWI Applications-Sheet. 

b. On the ANWI Applications-Sheet under the Infrastructure Services 

1. list the applications (licenses numbers , cost and support cost) 

required to fulfil the infrastructure network requirements provided in 

SOW Annex F Appendix 5. - The Bidder is free to add as many rows 

as required. - this shall cover all security domains - NS,EAPC, 

Business and Public 

2. Any server or storage hardware needed for the ANWI infrastructure 

services Shall be included in the ANWI processing and ANWI storage 

tables as described for CLIN 8.1 and 8.2 


PFE heading 

4. For CLIN 8.4.1 the total procurement cost of all infrastructure 

services software including the total of 1 year support is 

transferred to the SSS-Sheet 

CLIN 8.5 Wired Network Component Equipment / CLIN 8.6 Wireless LAN 

Component equipment 


details are calculated from the Networking-Sheet. 

b. On the Networking Sheet list all networking components (per type) 

required for the ANWI project in the SOW Annex F Appendix 6. This shall 

cover all security domains - NS, EAPC, Business and Public. 

1. Per Device type the Bidder shall provide information about every 

switch or switch component 


b. Quantity in units and ports 

c. Power/Cooling Requirements 

d. Unit price 

e. Yearly Support/Warranty cost 


NATO UNCLASSIFIED



2. For CLIN 8.5.1 the total procurement cost and Year 1,2 and 3 

support cost of the FO Access switches is transferred to the 

SSS. 

3. For CLIN 8.5.2.the total procurement cost and Year 1,2 and 3 

support cost of the PoE Access switches is transferred to the 

SSS. 


support cost of the Core switches is transferred to the SSS. 


support cost of the Server switches is transferred to the SSS. 


support cost of the Conference Switching is transferred to the 

SSS. 

7. For CLIN 8.6.1 the total procurement cost and Year 1,2 and 3 

support cost of the WLAN hardware is transferred to the SSS. 

CLIN 8.7 Cross-Domain Module Component Equipment 


details are calculated from the CDGW-Sheet. 

b. On the CDGW Sheet list per Type of cross Domain Gateway all 

processing, Storage and networking hardware components as well as the 

Cross domain Software licenses required to fulfil SOW Annex E - 

Appendix 2 requirements. 

1. Per Device the Bidder shall provide information on: 


b. Quantity (units) 

c. Power/Cooling requirement (Not Applicable for Software) 

d. Unit price 

e. Yearly Support/Warranty Cost 


PFE heading 

3. For CLIN 8.7.1 the total procurement cost and Year 1, 2 and 3 

support cost of the CDGW1 Hardware is transferred to the SSS. 

4. For CLIN 8.7.2 the total procurement cost and Year 1 Support 

cost of the CDGW1 Software is transferred to the SSS. 














NATO UNCLASSIFIED











CLIN 9 UCC Services 


details are calculated from the ANWI Applications-Sheet. 

b. On the ANWI Applications-Sheet under the respective UCC service 

1. List the applications (licenses numbers, cost and support cost) 

required to fulfil the respective UCC requirements provided in SOW 

Annex G Appendix 1-11. - The Bidder is free to add as many rows as 

required. - this shall cover all security domains - NS,EAPC, Business 

and Public 

2. Any server or storage hardware needed for the ANWI UCC services 

Shall be included in the ANWI processing and ANWI storage tables 

as described for CLIN 8.1 and 8.2 


PFE heading 

4. For CLIN 9.1.1 the total procurement cost of all Voice and 

Voicemail services software including the total of 1 year support 

is transferred to the SSS-Sheet 

5. For CLIN 9.2.1 the total procurement cost of all e-mail services 

software including the total of 1 year support is transferred to 

the SSS-Sheet 

6. For CLIN 9.3.1 the total procurement cost of all Fax services 


the SSS-Sheet 

7. For CLIN 9.4.1 the total procurement cost of all IM/Chat services 


the SSS-Sheet 

8. For CLIN 9.5.1 the total procurement cost of all Presence 



9. For CLIN 9.6.1 the total procurement cost of all UCC directory 



10. For CLIN 9.7.1 the total procurement cost of all Collaboration 



11. For CLIN 9.8.1 the total procurement cost of all Unified 

Messaging and Mobility Service services software including the 

total of 1 year support is transferred to the SSS-Sheet 


NATO UNCLASSIFIED



CLIN 10 SMC Software 


details are calculated from the SMC-sheet 

b. On the SMC sheet: 

1. Under Service Design - List the applications (licenses numbers and 

cost and support cost) required to fulfil the SMC - Service design 

requirements provides in SOW Annex E Appendix 1. 

2. Under Service Transition: List the applications (licenses numbers 

and cost and support cost) required to fulfil the SMC - Service 

Transition 

Requirements provides in SOW Annex E Appendix 1. 

c. Under Service Operations: List the applications (licenses numbers 


Operation 

Requirements provides in SOW Annex E Appendix 1. 

4. Under Service Improvement: List the applications (licenses numbers 


Improvement requirements provides in SOW Annex E Appendix 1. 

5. Any server, storage or networking hardware needed for the ANWI 

SMC services Shall be included in the ANWI processing and ANWI 

storage tables as described for CLIN 8.1 and 8.2 and 8.5 


PFE heading 

CLIN 11 Client Provisioning Hardware and Software 


details are calculated from the Client-sheet. 

b. On the Client Sheet under the respective type of Client Hardware/Software 

table 

1. List all Hardware components or software licenses needed to fulfil the 

client requirements from the SOW ANNEX H Appendix 1 -3. The 

Bidder is free to add as many rows as required. - this shall cover all 

security domains - NS,EAPC, Business and Public 

2. Per Device/Component the Bidder shall provide information on: 




d. Unit price 


3. NATO provides as PFE: 

a. Office Professional Plus 

b. Enterprise Client Access Licenses (e-CAL) for Windows Server, 

Exchange Server, SharePoint Server, Lync Server, System 

Centre, Forefront and SQL Server. 

4. For CLIN 11.1.1 the total procurement cost of all Standard 

Desktop Client hardware including the total of year 1,2 and 3 

support is transferred to the SSS-Sheet 


NATO UNCLASSIFIED





5. For CLIN 11.1.2 the total procurement cost of all High 

Performance Desktop Client hardware including the total of year 

1,2 and 3 support is transferred to the SSS-Sheet 

6. For CLIN 11.1.3 the total procurement cost of all Network 

Agnostic Desktop Client hardware including the total of year 1,2 

and 3 support is transferred to the SSS-Sheet 

7. For CLIN 11.1.4 the total procurement cost of all Mobile Client 

hardware including the total of year 1,2 and 3 support is 


8. For CLIN 11.1.5 the total procurement cost of all 

PDA/Smartphone Client hardware including the total of year 1,2 

and 3 support is transferred to the SSS-Sheet 

9. For CLIN 11.1.6 the total procurement cost of all IP phone Client 



10. For CLIN 11.1.7 the total procurement cost of all IP phone 

secretariat Client hardware including the total of year 1,2 and 3 


11. For CLIN 11.2.1 the total procurement cost of all Standard 

Desktop Client Software including the total of year 1 support is 


12. For CLIN 11.2.2 the total procurement cost of all High 

Performance Desktop Client Software including the total of year 

1 support is transferred to the SSS-Sheet 

13. For CLIN 11.2.3 the total procurement cost of all Network 

Agnostic Desktop Client Software including the total of year 1 


14. For CLIN 11.2.4 the total procurement cost of all Mobile Client 

Software including the total of year 1 support is transferred to 

the SSS-Sheet 

15. For CLIN 11.2.5 the total procurement cost of all 

PDA/Smartphone Client Software including the total of year 1 


16. For CLIN 11.2.6 the total procurement cost of all IP phone Client 

Software including the total of year 1 support is transferred to 

the SSS-Sheet 

17. For CLIN 11.2.7 the total procurement cost of all IP phone 

secretariat Client Software including the total of year 1support is 


18. For CLIN 11.2.8 the total procurement cost of all UCC Client 

Software including the total of year 1support is transferred to 

the SSS-Sheet 

19. For CLIN 11.2.9 the total procurement cost of all IPTV Client 

Software including the total of year 1support is transferred to 

the SSS-Sheet 

c. On the ANWI Clients Sheet under the respective type of Client 

provisioning Software table 

1. List all Software components or and licenses needed to fulfil the client 

requirements from the SOW ANNEX H Appendix 1 -3. The Bidder is





free to add as many rows as required. - this shall cover all security 

domains - NS,EAPC, Business and Public 

2. Any server or storage hardware needed for the Client Provisioning 

services shall be included in the ANWI processing and ANWI storage 

tables as described for CLIN 8.1 and 8.2 



b. Quantity (units & supported Clients) 

c. Unit price 

d. Yearly Support/Warranty Cost 

4. For CLIN 11.2.10 the total procurement cost of all Client 

Provisioning Software including the total of year 1support is 


CLIN 12.1 GSM Communications 

a. CLIN 12.1.1 - Enter price details in the SSS for the CoCo GSM 

Coverage Service. 

b. For CLIN 12.1.2 and 12.1.3 DO NOT enter direct price details in the SSSsheet 

because the price details are calculated from the other systems- 

Sheet. 

c. On the Other systems Sheet under the respective type of Hardware table 

1. Fill out the GSM HW/SW table to fulfil the requirements is the SOW 

Annex I Appendix 2 

a. Per Device/Component the Bidder shall provide information on: 




d. Unit price 


2. For CLIN 12.1.2 the total procurement cost of all GSM Blocking 



3. For CLIN 12.1.3 the total procurement cost of all WLAN Blocking 



CLIN 12.2 Security Communications 

a. Enter Price details in the SSS-sheet per Sub-CLIN 

b. Provide Cost breakdown detail in the “Implementation Services”-sheet 

CLIN 12.3 IPTV 

a. CLIN 12.3.1 - Enter price details in the SSS for the CoCo IPTV Service 

(Yearly Service Fee) 

b. For 12.3.2 DO NOT enter direct price details in the SSS-sheet because 

the price details are calculated from the Other systems-Sheet. 

c. On the Other systems Sheet under the IPTV Endpoints table 

1. List all required items in the IPTV Endpoint table to fulfil the 

requirements is the SOW Annex I Appendix 6 

a. Per Device/Component the Bidder shall provide information on: 

a. Description







d. Unit price 


2. For CLIN 12.3.2 the total procurement cost of all IPTV endpoint 



CLIN 13 ITS 

a. All Sub-CLINs except 13.2, 13.3 and 13.4.2 - Enter price details in the 

SSS for ITS Services 

b. All Sub-CLINs except 13.2, 13.3 and 13.4.2 - Provide Cost breakdown 

detail in the “Implementation Services”-sheet 

c. For CLIN 13.2, 13.3 and 13.4.2 DO NOT enter direct price details in the 

SSS-sheet because the price details are calculated from the ITS-Sheet. 

d. On the ITS Sheet list all hardware components as well as the Software 

licenses required to fulfil SOW Annex J requirements for the ITS service. 

1. Per Device the Bidder shall provide information on: 




d. Unit price 



PFE heading 

3. For CLIN 13.2 the total procurement cost of all ITS hardware 

including the total of year 1,2 and 3 support is transferred to the 

SSS-Sheet 

4. For CLIN 13.3 the total procurement cost of all ITS Software 

including the total of year 1 support is transferred to the SSS- 

Sheet 

d. On the ITS sheet list all manpower (in man-days) to provide ITS 

sustainment and Test Support to fulfil the ITS requirements in SOW Annex 

J. 

1. For CLIN 13.4.2 the total procurement cost of all ITS manpower 


CLIN 14: Nations and Partners 

a. This section is reserved – do NOT fill out. 

CLIN 15 Remote Sites 

b. DO NOT enter direct price details in the SSS-sheet because the price 

details are calculated from the Remote Sites -Sheet. 

c. On the Remote Sites Sheet under the respective type of 

Hardware/Software table 

1. List all Hardware components or software licenses needed to fulfil the 

client requirements from the SOW ANNEX M. The Bidder is free to 

add as many rows as required. - this shall cover 2 security domains - 

NS both Business 

2. Per Device/Component the Bidder shall provide information on:







c. Unit price 


3. For CLIN 15.1 the total procurement cost of all Remote Site 1 

hardware including the total of year 1,2 and 3 support and all 

Remote site 1 software including the total of year 1 support is 




Remote site2 software including the total of year 1 support is 




Remote site3 software including the total of year 1 support is 










CLIN 16 ANWI Standing Ordering Agreement 


details are calculated from the processing, Storage and networking - 

Sheets. 

b. On the respective excel sheets provide all Hardware and Software 

components that are required to fulfil the capacity requirement from the 

SOW Annex F. For the Standing ordering agreement the additional 

requirements for: 

1. Processing is related to the ICTM business applications processing - 

Ref Annex F Appendix 2 

2. Storage is related to the storage requirement beyond the ANWI 

services - Ref Annex F Appendix 3 

3. Networking is related to the connectivity requirement for additional 

processing and storage resources referenced above. 




c. Unit price 


5. For CLIN 16.1. - the procurement cost and support cost for 

YEAR 1,2 and 3 for processing Hardware is transferred to the 

SSS-Sheet 


YEAR 1 for processing Software is transferred to the SSS-Sheet




YEAR 1,2 and 3 for Storage Hardware is transferred to the SSS- 

Sheet 


YEAR 1 for Storage Software is transferred to the SSS-Sheet 


YEAR 1,2 and 3 for Networking Hardware is transferred to the 

SSS-Sheet 

CLIN 17 - Life-Cycle Support and Warranty 


details are calculated from the processing, storage, networking, CDGW, 

clients, ANWI-Applications, Other systems, ITS and Remote Sites-Sheets. 

b. On the Sheets indicated above a yearly support price for 5 year is 

required. Under the initial procurement a 3 year support for Hardware and 

1 year support for software is included. CLIN 17 - Sub-CLINS contain the 

remaining 2 year support for Hardware and 4 year support for Software. 

c. For the 17.1 Sub-CLINS the sum of the Year 4 and Year 5 hardware 

warranty and Support costs are transferred to the SSS-sheet. 

d. For the 17.2 Sub-CLINs the sum of Year 2 to 5 software warranty and 

support costs are transferred to the SSS-sheet 

CLIN 18 - Service Life-Cycle support - Operation 


details are calculated from the Service Operations sheet 

b. In the Service Operations sheet the Bidder shall provide yearly costing 

details per service to operate the respective service. This shall include a 

indicative manpower expressed in FTE's or man-days. 

1. The SMC Service Support operation shall include the manpower for 

1st level support, incident and problem management. 

2. The SMC Service Transition and management operations shall 

include the manpower for Change and configuration management as 

well as the overall Service Level and service catalogue management. 

3. The other identified services on the Service Operation sheet shall 

include the manpower for day-to-day operations, 2nd level support to 

include Performance and capacity Management 

CLIN 19 – CoCo Services Year 2-5 

a. For CLIN 19.1 – 19.4 DO NOT enter direct price details in the SSS-sheet 

because the price details are calculated from the Print-Scan sheet 

1. Print/Scan services is a Contractor Owned/Contractor Operated 

(COCO) Service. Therefore the Purchaser expects a cost for the 

service instead of a procurement cost with support. 

2. The respective yearly support and per page prices are 

transferred to the SSS-sheet 

b. CLIN 19.5 – 19.8 - Enter price details in the SSS for the CoCo IPTV 

Service (Yearly Service Fee) 


NATO UNCLASSIFIED



CLIN 20 – Optional Hardware and software (non-evaluated) 

a. Do NOT enter price details in the SSS Sheet. 

b. The Bidder shall provide pricing for optional/additional Hardware and 

software in the ANWI IDIQ equipment sheet. 

c. The Bidder shall provide staggered pricing details as indicated in the 

ANWI IDIQ equipment sheet 

CLIN 21: System Administrator training (non-evaluated) 

a. Enter price details for the development and conduct of the different 

administrator trainings satisfying the requirements in the referenced SOW 

sections. 

b. The provided price information shall include training materials. 


NATO UNCLASSIFIED


4. COMPLETING THE PRICING SUMMARY BREAKDOWN 

(Bidding Sheets - Worksheet “Pricing Summary”) 


1. DIRECT MATERIAL 

A. Purchased Parts: Provide a consolidated priced summary of individual 

material quantities included in the various tasks, orders, or Contract line items being 

proposed and the basis for pricing (vendor quotes, invoice prices, etc.). 

B. Subcontracted Items: Show the total cost of Subcontract effort. 

C. Other: 

(1) Raw Material: Consists of material in a form or state that requires further 

processing. Provide priced quantities of items required for the proposal. Show total 

cost. 

(2) Standard Commercial Items: Consists of items that the Bidder normally 

fabricates, in whole or in part, and that are generally stocked in inventory. Provide 

an appropriate explanation of the basis for pricing on attached schedule. 

2. MATERIAL OVERHEAD 

This is the overhead charged to prices for material handling and/or other overhead 

associated with material costs. This may or may not apply to your prices. 

3. DIRECT LABOR 

Show the hourly rate and the total hours for the categories and disciplines of direct 

labour proposed. Indicate whether actual rates or escalated rates are used. If 

escalation is included, state the degree (percent) and rationale used. 

4. LABOUR OVERHEAD 

This is labour overhead. 

5. OTHER DIRECT COSTS 

A. Special Tooling/Equipment. Identify and support specific equipment and 

unit prices. Use a separate schedule if necessary. 

B. Travel. Identify total cost for transportation and per diem rates, including the 

Not To Exceed values of the CLINs. 

C. Individual Consultant Services. Identify and support the proposed 

contemplated consulting. State the amount of services estimated to be required and 

the consultant’s quoted daily or hourly rate. 

D. Other Costs. List all other direct charge costs not otherwise included in the 

categories described above (e.g., services of specialized trades, computer services, 

preservation, packaging and packing, leasing of equipment and provide bases for 

pricing. 

6. GENERAL AND ADMINISTRATIVE EXPENSE 

This is the overhead charged or General and Administrative (G&A) expenses. 

7. FEE OR PROFIT 

Enter the total of all proposed Fee or Profit. 


NATO UNCLASSIFIED



8. OTHER FACTORS 

This would be any other overhead factors applied to Bidders prices. 

9. GRAND TOTAL 

This is the Bidders final Firm Fixed Price total for the identified WP and should in 

essence match the price entered in the corresponding SSS WP in Section 1 of the 

Bidding sheets. 


NATO UNCLASSIFIED



Annex A-2. 

Bidding Sheets – Excel Format 

The Bidding Sheets are contained in the electronic file “3_IFB-CO-13300-ANWI- 

AMD-2-Book-I-Bidding Sheets_v03.xlsx” submitted as part of this IFB. 


NATO UNCLASSIFIED



Annex B 

Prescribed Administrative Forms and Certificates 


Book I, Annex B, Page B-1



Annex B-1. 

Certificate of Legal Name of Bidder 

This Bid is prepared and submitted on behalf of the legal corporate entity specified 

below: 

FULL NAME OF CORPORATION: 

DIVISION (IF APPLICABLE): 

SUB DIVISION (IF APPLICABLE): 

____________________________________ 

____________________________________ 

____________________________________ 

OFFICIAL MAILING ADDRESS 

__________________________________________________________________ 

__________________________________________________________________ 

__________________________________________________________________ 

E-MAIL ADDRESS: 

TELEFAX No: 

____________________________________ 

____________________________________ 

POINT OF CONTACT REGARDING THIS BID: 

NAME: 

POSITION: 

TELEPHONE: 

____________________________________ 

____________________________________ 

____________________________________ 

ALTERNATIVE POINT OF CONTACT: 

NAME: 

POSITION: 

TELEPHONE: 

____________________________________ 

____________________________________ 

____________________________________ 

Date 

Signature of Authorised Representative 

Printed Name 

Title 

Company 

Book I, Annex B, Page B-2 

NATO UNCLASSIFIED



Annex B-2. 

Acknowledgement of Receipt of IFB 

Amendments 

I confirm that the following amendments to Invitation for Bid CO-13300-ANWI 

have been received and the Bid, as submitted, reflects the content of such 

amendments. 

Amendment no. 

Date of 

Issued 

Date of 

receipt 

Initials 

Date 


Printed Name 

Title 

Company 


Book I, Annex B, Page B-3



Annex B-3. 

Certificate of Independent Determination 

It is hereby stated that: 

a. We have read and understand all documentation issued as part of CO-13300- 

ANWI. Our Bid submitted in response to the referred solicitation is fully compliant with 

the provisions of the IFB and the prospective Contract. 

b. Our Bid has been arrived at independently, without consultation, 

communication or agreement, for the purpose of restricting competition, with any 

other Bidder or with any competitor; 

b. The contents of our Bid have not been knowingly disclosed by the Bidder and 

will not knowingly be disclosed by the Bidder prior to award, directly or indirectly to 

any other Bidder or to any competitor; and 

c. No attempt has been made, or will be made by the Bidder to induce any other 

person or firm to submit, or not to submit, a Bid for the purpose of restricting 

competition. 

Date 


Printed Name 

Title 

Company 


NATO UNCLASSIFIED



Annex B-4. 

Certificate of Bid Validity 

I, the undersigned, as an authorised representative of the firm submitting this Bid, do 

hereby certify that the pricing and all other aspects of our Bid will remain valid for a 

period of twelve (12) months from the Bid Closing Date of this Invitation for Bid. 

Date 


Printed Name 

Title 

Company 


NATO UNCLASSIFIED



Annex B-5. 

Certificate of Exclusion of Taxes, Duties and 

Charges 

I hereby certify that the prices offered in the price quotation of this Bid exclude all 

taxes, duties and customs charges from which the Purchaser has been exempted by 

international agreement. 

Date 


Printed Name 

Title 

Company 


NATO UNCLASSIFIED



Annex B-6. 

Comprehension and Acceptance of Contract 

Special and General Provisions 

The Bidder hereby certifies that he has reviewed the Special Contract Provisions and 

the NCIA General Provisions set forth in the Prospective Contract, Book II of this 

Invitation for Bid. The Bidder hereby provides his confirmation that he fully 

comprehends the rights, obligations and responsibilities of the Contractor as set forth 

in the Articles and Clauses of the Prospective Contract. The Bidder additionally 

certifies that the offer submitted by the Bidder is without prejudice, qualification or 

exception to any of the Terms and Conditions and he will accept and abide by the 

stated Special and General Provisions if awarded the Contract as a result of this 

Invitation for Bid. 

Date 


Printed Name 

Title 

Company 


NATO UNCLASSIFIED



ANNEX B-7. 

Disclosure of Requirements for NCIA 

Execution of Supplemental Agreements 

I, the undersigned, as an authorised representative of _______________________, 

certify the following statement: 

All supplemental agreements, defined as agreements, documents and/or 

permissions outside the body of the Contract but are expected to be required by my 

Government, and the governments of my Subcontractors, to be executed by the 

NCIA as a condition of my firm’s performance of the Contract, have been identified, 

as part of the Bid. 

These supplemental agreements are listed as follows: 

(insert list of supplemental agreements or specify “none”) 

Examples of the terms and conditions of these agreements have been provided in 

our Offer. The anticipated restrictions to be imposed on NATO, if any, have been 

identified in our offer along with any potential conflicts with the terms, conditions and 

specifications of the Prospective Contract. These anticipated restrictions and 

potential conflicts are based on our knowledge of and prior experience with such 

agreements and their implementing regulations. We do not certify that the language 

or the terms of these agreements will be exactly as we have anticipated. 

The processing time for these agreements has been calculated into our delivery and 

performance plans and contingency plans made in the case that there is delay in 

processing on the part of the issuing government(s). 

We recognise that additional supplemental agreements, documents and permissions 

presented as a condition of Contract performance or MOU signature after our firm 

would be selected as the successful Bidder may be cause for the NCIA to determine 

the submitted Bid to be non-compliant with the requirements of the IFB; 

We accept that should the resultant supplemental agreements issued in final form by 

the government(s) result in an impossibility to perform the Contract in accordance 

with its schedule, terms or specifications, the Contract may be terminated by the 

Purchaser at no cost to either Party. 

Date 


Printed Name 

Title 


Company 

NATO UNCLASSIFIED



Annex B-8. 

Certificate of Compliance AQAP 2110 or ISO 

9001:2008 or Equivalent 

I hereby certify that _________________________(name of Company) possesses 

and applies Quality Assurance Procedures/Plans that are equivalent to the AQAP 

2110 or ISO 9001:2008 as evidenced through the attached documentation 1 . 

Date 


Printed Name 

Title 

Company 

1 Bidders must attach copies of any relevant quality certification. 


NATO UNCLASSIFIED



Annex B-9. 

List of Prospective Subcontractors 

Name and 

Address of Sub- 

Bidder 

DUNS 

Number 

2 

Primary 

Location of 

Work 

Items/Services to 

be Provided 

Estimated 

Value of 

Subcontract 

Date 


Printed Name 

Title 

Company 

2 Data Universal Numbering System (DUNS). Bidders are requested to provide this data in order to 

help NCIA to correctly identify Subcontractors. If a Subcontractor’s DUNS is not known this field may 

be left blank. 


NATO UNCLASSIFIED



Annex B-10. 

Bidder Background IPR 

I, the undersigned, as an authorised representative of Bidder 

_______________________, warrant, represent, and undertake that: 

a. The Contractor Background IPR specified in the table below will be used for 

the purpose of carrying out work pursuant to the prospective Contract. 

ITEM 

DESCRIPTION 

b. The stated Bidder has and will continue to have, for the duration of the 

prospective Contract, all necessary rights in and to the Background IPR 

specified above. 

c. The Background IPR stated above complies with the terms specified in Clause 

30 of the Contract General Provisions. 

Date 


Printed Name 

Title 


Company 

NATO UNCLASSIFIED



Annex B-11. 

List of Subcontractor IPR 

I, the undersigned, as an authorised representative of Bidder 

_______________________, warrant, represent, and undertake that: 

a. The Subcontractor IPR specified in the table below will be used for the 

purpose of carrying out work pursuant to the prospective Contract. 

ITEM 

DESCRIPTION 

b. The stated Bidder has and will continue to have, for the duration of the 

prospective Contract, all necessary rights in and to the IPR specified above 

necessary to perform the Contractor’s obligations under the Contract. 

c. The Subcontractor IPR stated above complies with the terms Clause 30 the 

Contract General Provisions. 

Date 


Printed Name 

Title 


Company 

NATO UNCLASSIFIED



Annex B-12. 

Certificate of Origin of Equipment, Services, 

and Intellectual Property 

The Bidder hereby certifies that, if awarded the Contract pursuant to this solicitation, 

he will perform the Contract subject to the following conditions: 

(a) none of the work, including project design, labour and services shall be 

performed other than by firms from and within participating NATO member countries; 

(b) no material or items of equipment down to and including identifiable 

sub-assemblies shall be manufactured or assembled by a firm other than from and 

within a participating NATO member country. (A sub-assembly is defined as a 

portion of an assembly consisting of two or more parts that can be provisioned and 

replaced as an entity); and 

(c) The intellectual property rights to all design documentation and related 

system operating software shall reside in NATO member countries, and no license 

fees or royalty charges shall be paid by the Bidder to firms, individuals or 

Governments other than within the NATO member countries. 

Date 


Printed Name 

Title 

Company 


NATO UNCLASSIFIED



Annex B-13. 

List of Proposed Key Personnel 

Position SOW 

Reference 

Labour 

Category 

Name Designation 

Period 

Project Manager 4.2.3 EDC thru 

Contract 

expiration 

date 

Technical Lead 4.2.4 EDC thru 

Contract 

expiration 

date 

Test Director 4.2.5 EDC thru 

Contract 

expiration 

date 

Date 


Printed Name 

Title 

Company 


NATO UNCLASSIFIED



Annex B-14. 

Certificate of Price Ceiling 

I hereby certify that the total price offered in the price quotation of this Bid for CLINs 

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 and 16 of the Bidding Sheets does not 

exceed EUR 81,726,023 (eighty-one million seven hundred twenty-six thousand 

twenty-three Euro) as described in paragraph 3.5.2 of Book I. 

Note: Price information of your Bid shall not be disclosed in the Bid Administration Package, or the 

Technical Proposal Package. 

Date 


Printed Name 

Title 

Company 


NATO UNCLASSIFIED



Annex B-15. 

Disclosure of Conflict of Interest 

I, the undersigned, as an authorised representative of _______________________, 

(company name) certify that 3 : 

(check one of the following statements:) 

☐ a real or apparent conflict of interest as defined in paragraph 3.4.3.1 of the 

Bidding Instructions does not exist. 

☐ 

a real or apparent conflict of interest as defined in paragraph 3.4.3.1 of the 

Bidding Instructions may exist and a plan for the mitigation of the conflict is 

provided in attachment to this Certificate. 

(check one of the following statements:) 

☐ 

☐ 

business relationships as defined under paragraph 3.4.3.2 of the Bidding 

Instructions do not exist. 

business relationships as defined under paragraph 3.4.3.2 of the Bidding 

Instructions exist and have been identified in attachment to this Certificate. 

Date 


Printed Name 

Title 

Company 

3 Bidders are to check the appropriate box(es). 


NATO UNCLASSIFIED



Annex B-16. 

Index and Certificate of Compliance of 

Administrative Certificates 

The Bidder hereby certifies that he complies with, and has duly signed, all 

Administrative Certificates required under this IFB as indexed below. The Bidder 

further certifies that he has submitted the required Administrative Certificates without 

prejudice, qualification or exception, and that he has not made any changes or 

alterations to the original wording of any of the Administrative Certificates. 

Index of Administrative Certificates: 

Annex B-1 (Certificate of Legal Name of Bidder) 

Annex B-2 (Acknowledgement of Receipt of IFB Amendments) 

Annex B-3 (Certificate of Independent Determination) 

Annex B-4 (Certificate of Bid Validity) 

Annex B-5 (Certificate of Exclusion of Taxes, Duties and Charges) 

Annex B-6 (Comprehension and Acceptance of Contract Special and General 

Provisions) 

Annex B-7 (Disclosure of Requirements for NCIA Execution of Supplemental 

Agreements) with the prospective text of such Agreements, as applicable. 

Annex B-8 (Certificate of Compliance AQAP or ISO 9001:2008 or Equivalent) with a 

copy of the relevant quality certification attached to it. 

Annex B-9 (List of Prospective Subcontractors) 

Annex B-10 (Bidder Background IPR) 

Annex B-11(List of Subcontractor IPR) 

Annex B-12 (Certificate of Origin of Equipment, Services, and Intellectual Property) 

Annex B-13 (List of Proposed Key Personnel) 

Annex B-14 (Certificate of Price Ceiling) 

Annex B-15 (Disclosure of Conflict of Interest) 

Annex B-16 (Index and Certificate of Compliance of Administrative Certificates) 

Date 


Printed Name 

Title 

Company 


NATO UNCLASSIFIED



Annex C 

Bid Guarantee - Standby Letter of Credit 

Standby Letter of Credit Number: 

Issue Date: 

Beneficiary: 

___________________________ 

NCI Agency, 

Financial Management Resource Centre, 

Boulevard Leopold III, 

B-1110 Brussels, 

Belgium 

Expiry Date: ___________________________ 

1. We, (issuing bank) hereby establish in your favour our irrevocable standby 

letter of credit number {number} by order and for the account of (NAME AND 

ADDRESS OF BIDDER) in the original amount of € 500,000.00 (Five Hundred 

Thousand Euro). We are advised this Guarantee fulfils a requirement under 

Invitation for Bid IFB-CO-13300-ANWI dated __________________. 

2. Funds under this standby letter of credit are available to you upon first 

demand and without question or delay against presentation of a certificate from the 

NCI Agency Contracting Officer that: 

a) (NAME OF BIDDER) has submitted a Bid and, after Bid Closing Date 

(including extensions thereto) and prior to the selection of the lowest priced, 

technically compliant Bid, has withdrawn his Bid, or stated that he does not 

consider his Bid valid or agree to be bound by his Bid, or 

b) (NAME OF BIDDER) has submitted a Bid determined by the Agency to 

be the lowest priced, technically compliant Bid, but (NAME OF BIDDER) has 

declined to execute the Contract offered by the Agency, such Contract being 

consistent with the terms of the Invitation for Bid, or 

c) The NCI Agency has offered (NAME OF BIDDER) the Contract for 

execution but (NAME OF BIDDER) has been unable to demonstrate 

compliance with the security requirements of the Contract within a reasonable 

time, or 

d) The NCI Agency has entered into the Contract with (NAME OF 

BIDDER) but (NAME OF BIDDER) has been unable or unwilling to provide the 

Performance Guarantee required under the terms of the Contract within the 

time frame required. 

3. This Letter of Credit is effective the date hereof and shall expire at our office 

located at (Bank Address) on __________________. All demands for payment 

must be made prior to the expiry date. 

Book I, Annex C, Page C-1 

NATO UNCLASSIFIED



4. It is a condition of this letter of credit that the expiry date will be automatically 

extended without amendment for a period of sixty (60) calendar days from the current 

or any successive expiry date unless at least thirty (30) calendar days prior to the 

then current expiry date the NCI Agency Contracting Officer notifies us that the Letter 

of Credit is not required to be extended or is required to be extended for a shorter 

duration. 

5. We may terminate this letter of credit at any time upon sixty (60) calendar days 

notice furnished to both (NAME OF BIDDER) and the NCI Agency by registered mail. 

6. In the event we (the issuing bank) notify you that we elect not to extend the 

expiry date in accordance with paragraph 4 above, or, at any time, to terminate the 

letter of credit, funds under this credit will be available to you without question or 

delay against presentation of a certificate signed by the NCI Agency Contracting 

Officer which states 

“The NCI Agency has been notified by {issuing bank} of its election not to 

automatically extend the expiry date of letter of credit number {number} dated {date} 

pursuant to the automatic renewal clause (or to terminate the letter of credit). As of 

the date of this certificate, no suitable replacement letter of credit, or equivalent 

financial guarantee has been received by the NCI Agency from, or on behalf of 

(NAME OF BIDDER), and the NCI Agency, as beneficiary, hereby draws on the 

standby letter of credit number ________ in the amount of € (Amount up to the 

maximum available under the LOC), such funds to be transferred to the account of 

the Beneficiary number ___________________ (to be identified when certificate is 

presented).” 

Such certificate shall be accompanied by the original of this letter of credit and a copy 

of the letter from the issuing bank that it elects not to automatically extend the 

standby letter of credit, or terminating the letter of credit. 

7. The Beneficiary may not present the certificate described in paragraph 6 

above until 20 (twenty) calendar days prior to a) the date of expiration of the letter of 

credit should {issuing bank} elect not to automatically extend the expiration date of 

the letter of credit, b) the date of termination of the letter of credit if {issuing bank} 

notifies the Beneficiary that the letter of credit is to be terminated in accordance with 

paragraph 6 above. 

8. Multiple drawings are allowed. 

9. Drafts drawn hereunder must be marked, “Drawn under {issuing bank} Letter 

of Credit No. {number}“ and indicate the date hereof. 

10. This letter of credit sets forth in full the terms of our undertaking, and this 

undertaking shall not in any way be modified, amended, or amplified by reference to 

any document, instrument, or agreement referred to herein (except the International 

Standby Practices (ISP 98) hereinafter defined) or in which this letter of credit is 

referred to or to which this letter of credit relates, and any such reference shall not be 

deemed to incorporate herein by reference any document, instrument, or agreement. 


Book I, Annex C, Page C-2



11. We hereby engage with you that drafts drawn under and in compliance with 

the terms of this letter of credit will be duly honoured upon presentation of documents 

to us on or before the expiration date of this letter of credit. 

12. This Letter of Credit is subject to The International Standby Practices-ISP98 

(1998 Publication) International Chamber of Commerce Publication No.590. 

Book I, Annex C, Page C-3 

NATO UNCLASSIFIED



Annex D 

Clarification Request Form 

INSERT COMPANY NAME HERE 

INSERT SUBMISSION DATE HERE 

INVITATION FOR BID 




(NNHQ ANWI) 

Annex D - CLARIFICATION REQUEST FORM 


Book I, Annex D, Page D-1





ADMINISTRATION or CONTRACTING 

Serial 

No. 

A.1 

IFB 

REF 

BIDDER’S QUESTION NCIA ANSWER STATUS 

A.2 

A.3 

A.4 

A.5 

Book I, Annex D, Page D-2 

NATO UNCLASSIFIED





PRICE 

Serial 

No. 

P.1 

IFB 

REF 


P.2 

P.3 

P.4 

P.5 







TECHNICAL 

Serial 

No. 

T.1 

IFB 

REF 


T.2 

T.3 

T.4 

T.5 





Book I - Bidding Instructions 

Annex A - Bidding Sheets 


AGENCY 




(NNHQ - ANWI) 

BOOK I - ANNEX A 

BIDDING SHEETS 

VERSION 03 



Book I - Cover - Page 1 of 41





CLIN Description Delivery place Delivery Date Reference 

QTY / Man- 

Days 

1 Project Management 

1.1 Project Management Documentation, containing 4.3; Annex K Appendix 1 

1.1.1 Project Status Report (PSR) NCIA (BEL) EDC+4 weeks 4.5; Annex K Appendix 15 15 

1.1.2 Project Management Plan (PMP) NCIA (BEL) EDC+2 weeks 4.3; Annex K Appendix 3 1 

1.1.3 Project Implementation Plan (PIP) EDC+2 weeks 4.3; Annex K Appendix 4 1 

1.1.3.1 Work Breakdown Structure (WBS) NCIA (BEL) EDC+2 weeks 4.3; Annex K Appendix 4 1 

1.1.3.2 Project Schedule NCIA (BEL) EDC+2 weeks 4.3; Annex K Appendix 4 1 

1.1.4 Change Management Plan NCIA (BEL) EDC+2 weeks 4.4.2 1 

1.1.5 Risk Management Plan (RMP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 5 1 

1.1.6 Quality Assurance Plan (QAP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 6 1 

1.1.7 Test and Acceptance Plan (TAP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 8 

1.1.8 Configuration Management Plan (CMP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 7 1 

1.1.9 Migration Plan (MP) NCIA (BEL) 30-Sep-14 4.3; Annex K Appendix 16 1 

1.1.10 Security Accreditation Documentation 

1.1.10.1 Security Risk Assessment NCIA (BEL) EDC+8 weeks 6.6.1; Annex K Appendix 11 1 

1.1.10.2 System Security Requirement Statement input NCIA (BEL) EDC+8 weeks 6.6.2; Annex K Appendix 13 1 

1.1.10.3 System Interconnection Security Requirement Statement NCIA (BEL) EDC+8 weeks 6.6.2; Annex K Appendix 13 1 

1.1.10.4 Security Test & Evaluation NCIA (BEL) EDC+8 weeks 6.2; Annex K Appendix 12 1 

1.1.11 Logistic Support Plan (LSP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 9 1 

Unit Price 

Total Price 

Final 

Total Price 

Remarks 

1.1.12 

NATO Material Data Sheet 

NCIA (BEL) 

01-Sep-14 

6.10.2.2; Annex K Appendix 10 1 

1.2 Project Progress Review Meeting (PPRM) NCIA (BEL) EDC+2 weeks 4.5; Annex K Appendix 14 15+ 

2 ANWI Service and System Design 

2.1 Preliminary Design Review Meeting NCIA (NLD) EDC+4 weeks 5.2 1 

2.2 Design Document (4 Stages) 

2.2.1 CDGW & Infrastructure & IA NCIA (BEL) EDC+8 weeks 5.3; Annex K Appendix 2 1 

2.2.2 Service Management and Control (SMC) NCIA (BEL) EDC+16 weeks 5.3; Annex K Appendix 2 1 

2.2.3 UCC Services and Client provisioning NCIA (BEL) EDC+24 weeks 5.3; Annex K Appendix 2 1 

2.2.4 GSM & Secure Communications NCIA (BEL) EDC+32 weeks 5.3; Annex K Appendix 2 1 

2.3 Critical Design Review Briefings NCIA (NLD) 5.6 

2.3.1 CDGW & Infrastructure & IA - CDR Briefing NCIA (NLD) EDC+8 weeks 5.6 1 

2.3.2 Service Management and Control (SMC) - CDR Briefing NCIA (NLD) EDC+16 weeks 5.6 1 

2.3.3 UCC Services and Client provisioning - CDR Briefing NCIA (NLD) EDC+24 weeks 5.6 1 

2.3.4 GSM & Secure Communications - CDR Briefing NCIA (NLD) EDC+32 weeks 5.6 1 

2.4 Critical Design Review Feedback Meetings 





2.5 Acceptance of Design Document 

1st PPRM is Kickoff 

Meeting 

ITS included in CLIN 

13.1 

2.5.1 CDGW & Infrastructure & IA - Design Document Acceptance NCIA (BEL) EDC+14 weeks 5.8 1 

2.5.2 

2.5.3 

Service Management and Control (SMC) - Design Document 

Acceptance 

UCC Services and Client provisioning - Design Document 

Acceptance 

NCIA (BEL) EDC+22 weeks 5.8 1 


2.5.4 GSM & Secure Communications - Design Document Acceptance NCIA (BEL) EDC+38 weeks 5.8 1 

3 Site Survey 


Book I - SSS - Page 2 of 41






QTY / Man- 

Days 

3.1 Site survey workbook NCIA (BEL) EDC+52 weeks 6.5.3 1 

3.2 Conduct Site Survey NNHQ EDC+56 weeks 3.10.2; 6.5.3 1 

3.3 Site survey report NCIA (BEL) EDC+58 weeks 6.5.3 1 

4 Testing 

4.1 Test Status Meeting NCIA (BEL) 30-Apr-16 6.7 1 

4.2 Proof of Concept Test (PCT) 

4.2.1 PCT - SMC ITS Site EDC+30 weeks 6.8.3; Annex E Appendix 1 1 

4.2.2 PCT - CDM ITS Site EDC+24 weeks 6.8.3; 14.2.1 1 

4.2.3 PCT - UCC ITS Site EDC+38 weeks 6.8.3; Annex G Appendix 1 1 

4.2.4 PCT - Client Provisioning ITS Site EDC+35 weeks 6.8.3; Annex H Appendix 2 1 

4.3 Capability Acceptance Test 6.8.2 

4.3.1 Processing Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 2 1 

4.3.2 Storage Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 3 1 

4.3.3 Printing and Scanning Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 4 1 

4.3.4 Network Infrastucture Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 5 1 

4.3.5 LAN Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 6 1 

4.3.6 Cross Domain Service NNHQ Campus 30-Jun-15 6.8.2; 6.13; 14.2.1 1 

4.3.7 Voice Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 2 1 

4.3.8 VoiceMail Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 3 1 

4.3.9 VTC Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 4 1 

4.3.10 Email Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 5 1 

4.3.11 Unified Messaging Service Commponent NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 6 1 

4.3.12 FAX Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 7 1 

4.3.13 Instant Messaging/Chat Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 8 1 

4.3.14 Presence Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 9 1 

4.3.15 Directory Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 10 1 

4.3.16 Collaboration Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 11 1 

4.3.17 Mobility Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 12 1 

4.3.18 UCC Client NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 1 1 

4.3.19 Software Provisioning NNHQ Campus 30-Jun-15 6.8.2; Annex H Appendix 2 1 

4.3.20 Client Devices NNHQ Campus 30-Jun-15 6.8.2; Annex H Appendix 3 1 

4.3.21 GSM Blocking NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 3 1 

4.3.22 Wireless Blocking NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 4 1 

4.3.23 Site Security Comms NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 5 1 

4.3.24 GSM Continuity Services NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 2 1 

4.3.25 IPTV services NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 6 1 

4.4 Service Certification Test 6.8.4 

4.4.1 Infrastructure Services NNHQ 30-Jun-15 6.8.4; Annex F Appendix 1 1 

4.4.2 UCC Services NNHQ 30-Jun-15 6.8.4; Annex G Appendix 1 1 

4.4.3 Client Provisioning Service NNHQ 30-Jun-15 6.8.4; Annex H Appendix 1 1 

4.4.4 Supplementary Services NNHQ 

6.8.4; Annex I Appendix 1, 

30-Jun-15 Appendix 2, Appendix 6 

1 

4.4.5 Service Management and Control NNHQ 30-Jun-15 6.8.4; Annex E Appendix 1 1 

4.5 System Activation Test NNHQ 31-Oct-15 6.8.5 1 

4.6 Final Site Test NNHQ 30-Apr-16 6.8.6 1 

4.7 Security Implementation Verification Procedures NNHQ 30-Apr-15 6.8.7, Annex K Appendix 12 1 

4.8 Requirements Traceability Matrix NCIA (BEL) EDC+ 4 weeks 6.8.8 1 

4.9 Test reports NCIA (BEL) 30-Jun-16 3.10.7; Annex K Appendix 8 1 

5 ANWI Implementation and Transition 

5.1 ANWI Installation 

5.1.1 Server rooms NNHQ 31-Mar-15 6.10.2; 6.10.3; 6.10.4 1 

Unit Price 

Total Price 

Final 

Total Price 

Remarks 








QTY / Man- 

Days 

5.1.2 User Area NNHQ 30-Apr-16 6.10.2; 6.10.3; 6.10.4 1 

5.2 Service Activation NNHQ 30-Sep-15 6.10.6 1 

5.3 Service Activation Test NNHQ 31-Oct-15 6.10.7 1 

Unit Price 

Total Price 

5.4 Physical Configuration Audit 

NNHQ 

30-Sep-15 

6.10.8 1 

5.5 Initial Operating Capability NNHQ 31-Oct-15 6.13; 6,14 1 

5.6 Support from IOC to FOC NNHQ 30-Apr-16 6.14 1 

5.7 Migration to ANWI Environment NNHQ 30-Apr-16 6.10.10 1 

5.8 Support during migration NNHQ 30-Apr-16 6.10.12 1 

5.9 Final Operating Capability NNHQ 30-Apr-16 6.15; 6.16 1 

5.10 Support from FOC to FSA NNHQ 30-Oct-16 6.16 1 

5.11 Final System Acceptance NNHQ 30-Oct-16 6.17 1 

5.12 ANWI Knowledge base NNHQ 30-Jun-16 6.12 1 

5.13 Client Environment Training NNHQ 30-Apr-16 6.10.9 1 

6 ANWI Service and System Operations Processes 

6.1 ANWI Operational Support Plan NNHQ 31-Mar-15 7.4.1 1 

6.2 Training Needs Analysis for NONO services and users NCIA (BEL) 31-Mar-15 6.10.9.2 1 

6.3 ANWI Operations Event Management NNHQ 31-Mar-15 7.3.5; Annex E Appendix 1 1 

6.4 ANWI Operations Incident Management & Troubleshooting NNHQ 31-Mar-15 7.3.1; Annex E Appendix 1 1 

6.5 ANWI Request for Service NNHQ 31-Mar-15 7.3.3; Annex E Appendix 1 1 

6.6 ANWI Problem Management NNHQ 31-Mar-15 7.3.2; Annex E Appendix 1 1 

6.7 ANWI Access Management NNHQ 31-Mar-15 7.3.4; Annex E Appendix 1 1 

6.8 ANWI Monitoring NNHQ 31-Mar-15 7.4.3; Annex E Appendix 1 1 

6.9 Operational Procedures/Operating Instructions NCIA (BEL) 31-Mar-15 7.4.2; Annex E Appendix 1 1 

7 ANWI Service Improvement 

7.1 Identification of CSF NCIA (BEL) 30-Apr-15 8.5; Annex E Appendix 1 1 

7.2 Identification of KPIs for ANWI Services NCIA (BEL) 30-Apr-15 8.5; Annex E Appendix 1 1 

7.3 Service Level Agreement Reporting NCIA (BEL) 30-Apr-15 8.6.7.1; Annex E Appendix 1 1 

7.4 Improvement Recommendations change proposal NNHQ 31-Oct-16 8.6.7.2; Annex E Appendix 1 1 

7.5 Implement the Improvements NNHQ 31-Oct-16 8.6.8; Annex E Appendix 1 1 

8 Infrastructure Services Hardware and Software 

8.1 Processing Service Equipment 

8.1.1 Hardware 

8.1.1.1 Processing Hardware (Base Contract) including 3 year Warranty and 

NNHQ 

Annex F Appendix 2 

support 

31-Mar-15 

1 n.a - 

8.1.2 Software 

8.1.2.1 Processing Software Procurement (Base Contract) including 1 year 

NNHQ 


warranty and support 

31-Mar-15 

1 n.a - 

8.2 Storage Services Equipment 


8.2.1.1 Storage Hardware (Base Contract) including 3 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 


8.2.2.1 Storage Software (Base Contract) including 1 year warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 

8.3 Print-Scan Services 

8.3.1 

Contractor Owned / Contractor operated Print/Scan Service for Large 

MFP device 

NNHQ 01-Dec-15 Annex F Appendix 4 

8.3.2 CoCo Print/Scan Service - Price per page B/W NNHQ 01-Dec-15 Annex F Appendix 4 

Final 

Total Price 

Remarks 

Inclucing Batiment Z and 

Remote sites 

187 - - Yearly service Cost 

Price per page - QTY based 

on 1 year estimate printed 

7000000 - - 

pages 








QTY / Man- 

Days 

Unit Price 

Total Price 

8.3.3 CoCo Print/Scan Service - Price per page Colour NNHQ 01-Dec-15 Annex F Appendix 4 

3000000 - - 

8.4 Network Infrastructure Services 

8.4.1 Network Infrastructure Services Software - including 1 year warranty 

NNHQ 


and support 

31-Mar-15 

1 n.a - 

8.5 Wired Network Component Equipment 

8.5.1 Access Switches FO - including 3 year Warranty and support NNHQ 01-Dec-15 Annex F Appendix 6 1 n.a. - 

8.5.2 Access Switches RJ45 PoE - including 3 year Warranty and support 

NNHQ 


01-Dec-15 

1 n.a. - 

8.5.3 Core Switches - including 3 year Warranty and support 

NNHQ 


31-Mar-15 

1 n.a. - 

8.5.4 Server Switches - including 3 year Warranty and support NNHQ 31-Mar-15 Annex F Appendix 6 1 n.a. - 

8.5.5 Wired-Network-Conference Centre - including 3 year Warranty and 

NNHQ 


support 

01-Dec-15 

1 n.a. - 

8.6 Wireless Network Component Equipment 

8.6.1 WLAN - including 3 year Warranty and support NNHQ 01-Dec-15 Annex F Appendix 6 1 n.a. - 

8.7 Cross-Domain Module Component Equipment 

8.7.1 NS-NGCS-HW - including 3 year Warranty and support NNHQ 31-Mar-15 Annex E Appendix 2 1 n.a. - 

8.7.2 NS-NGCS-SW - including 1 year Warranty and support NNHQ 31-Mar-15 Annex E Appendix 2 1 n.a. - 

8.7.3 Business-NGCS/Public -HW - including 3 year Warranty and 

NNHQ 

Annex E Appendix 2 

support 

31-Mar-15 

1 n.a. - 

8.7.4 Business-NGCS/Public -SW - including 1 year Warranty and support 

NNHQ 


31-Mar-15 

1 n.a. - 

8.7.5 Public - Internet Access HW - including 3 year Warranty and support 

NNHQ 


31-Mar-15 

1 n.a. - 

8.7.6 Public - Internet Access SW- including 1 year Warranty and support 

NNHQ 


31-Mar-15 

1 n.a. - 

8.7.7 NS-EAPC-HW - including 3 year Warranty and support NNHQ 31-Mar-15 Annex E Appendix 2 1 n.a. - 

8.7.8 NS-EAPC-SW - including 1 year Warranty and support NNHQ 31-Mar-15 Annex E Appendix 2 1 n.a. - 

8.7.9 NS-Business-Info-Sharing-HW- including 3 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a. - 

8.7.10 NS-Business-Info-Sharing-SW- including 1 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a. - 

8.7.11 CIS Management Info-Sharing HW- including 3 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a. - 

8.7.12 CIS Management Info-Sharing SW- including 1 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a. - 

9 UCC Services 

9.1 Voice & VioceMail Component Equipment 

9.1.1 Voice & Voicemail Software - including 1 year Warranty and 

support 

NNHQ 

Annex G 

Appendix 2 & 3 1 n.a. - 

31-Mar-15 

9.2 Email Service Component Equipment 

9.2.1 E-mail service software - including 1 year Warranty and support NNHQ 31-Mar-15 Annex G Appendix 5 1 n.a. - 

9.3 FAX Service Component Equipment 

9.3.1 Fax service software - including 1 year Warranty and support NNHQ 31-Mar-15 Annex G Appendix 7 1 n.a. - 

9.4 IM/Chat Service Component Equipment 

9.4.1 IM/Chat service software - including 1 year Warranty and supportt NNHQ 31-Mar-15 Annex G Appendix 8 1 n.a. - 

9.5 Presence Service Component Equipment 

9.5.1 Presence service software - including 1 year Warranty and support NNHQ 31-Mar-15 Annex G Appendix 9 1 n.a. - 

9.6 UCC Directory Service Component Equipment 

Final 

Total Price 

Remarks 



pages 








9.6.1 UCC Directory service software - including 1 year Warranty and 

support 

9.7 Collaboration Service Component Equipment 

9.7.1 Collaboration service software - including 1 year Warranty and 

support 

9.8 Unified Messaging and Mobility Service Component Equipment 

NNHQ 

NNHQ 

31-Mar-15 

31-Mar-15 

Annex G Appendix 10 


QTY / Man- 

Days 

Unit Price 

Total Price 

1 n.a. - 

1 n.a. - 

Final 

Total Price 

Remarks 

9.8.1 UM & Mobility service software - including 1 year Warranty and 

Annex G 

NNHQ 

support 

31-Mar-15 


10 SMC Components 

10.1 SMC - Service Design Software - including 1 year Warranty and 

NNHQ 

Annex E Appendix 1 - 13.1.9 

support 

31-Mar-15 

1 n.a - 

10.2 SMC - Service Transition Software - including 1 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 

10.3 SMC - Service Operations Software - including 1 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 

10.4 SMC - Service Improvement Software - including 1 year Warranty 

NNHQ 


and support 

31-Mar-15 

1 n.a - 

11 Client Provisioning Hardware and Software 

11.1 Hardware 

11.1.1 Standard Desktop Client - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 1981 - - 

11.1.2 High Performance Desktop Client - including 3 year Warranty and 

162 

NNHQ 

Annex H Appendix 3 

support 

01-Dec-15 

- - 

11.1.3 Network Agnostic Desktop Client - including 3 year Warranty and 

284 

NNHQ 


support 

01-Dec-15 

- - 

11.1.4 Mobile Client - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 1600 - - 

11.1.5 PDA/SmartPhone - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 573 - - 

11.1.6 IP Phone - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 493 - - 

11.1.7 IP Phone Secretariat - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 246 - - 

11.1.8 ANWI Travel Kit Client Hardware incl 3 year warranty and support NNHQ 01-Dec-15 Annex M 10 - - 

11.1.9 ANWI Travel Kit Back-end Hardware incl 3 year warranty and 

1 

NNHQ 

support 

01-Dec-15 

Annex M 

- - 

11.2 Software 

11.2.1 Software - Standard Client - including 1 year Warranty and support 

NNHQ 


01-Dec-15 

1981 - - 

11.2.2 Software - High Performance Client - including 1 year Warranty and 

NNHQ 


support 

01-Dec-15 

162 - - 

11.2.3 Software - Network Agnostic clients - including 1 year Warranty and 

NNHQ 


support 

01-Dec-15 

284 - - 

11.2.4 Software - Mobile Client - including 1 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 2 1600 - - 

11.2.5 Software - PDA/SmartPhone - including 1 year Warranty and 

NNHQ 


support 

01-Dec-15 

573 - - 

11.2.6 Software - IP Phone - including 1 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 2 493 - - 

11.2.7 Software - IP Phone Secretariat - including 1 year Warranty and 

246 

NNHQ 


support 

01-Dec-15 

- - 

11.2.8 UCC Client Software - including 1 year Warranty and support NNHQ 01-Dec-15 Annex G 1 - - 

11.2.9 IPTV Client Software - including 1 year Warranty and support NNHQ 01-Dec-15 Annex I Appendix 6 1 - - 

11.2.10 Client Provisioning Software Solution - including 1 year Warranty 

1 

NNHQ 

Annex H Appendix 1-2 

and support 

01-Dec-15 

- - 

11.2.11 ANWI Travel Kit Client Software incl 1 year warranty and support NNHQ 01-Dec-15 Annex M 10 - - 

12 Supplementary Services Hardware and Software 








QTY / Man- 

Final 

Unit Price Total Price 

Days 

Total Price 

Remarks 

12.1 GSM Communications 

12.1.1 GSM Coverage NNHQ Campus 01-Dec-15 Annex I Appendix 2 1 

12.1.2 GSM Blocking - including 3 year Warranty and support 

4 

NNHQ 


01-Dec-15 

- - 

12.1.3 Wireless Blocking - including 3 year Warranty and support NNHQ 01-Dec-15 Annex I Appendix 4 4 - - 

12.2 Security Communications 

12.2.1 Tetra secure communication coverage and penetration survey + 

1 

NNHQ 


Report 

31-Mar-15 

12.2.2 Tetra Secure Communications Antenna and Base Station relocation NNHQ 31-Mar-15 Annex I Appendix 5 1 

12.3 IPTV 

12.3.1 CoCo IPTV Service with Basic 30 Channels subscription (max 300) 

NNHQ 01-Dec-15 Annex I Appendix 6 

1 Service cost year 1 

12.3.2 IPTV endpoint - including 3 year warranty NNHQ 01-Dec-15 Annex I Appendix 6 425 - - 

13 Integration and Testing Service (ITS) 

13.1 ITS Design NCIA (NLD) EDC+8 weeks Annex K Appendix 1 1 

13.2 ITS Hardware (including 3 year warranty and support) ITS Site 30-Oct-13 Annex E-F-G-H-I-J 1 n.a. - 

13.3 ITS Software (including 1 year warranty and support) ITS Site 30-Oct-13 Annex E-F-G-H-I-J 1 n.a. - 

13.4 Installation, Operation and Maintenance 

13.4.1 ITS Installation ITS Site 30-Oct-13 Annex J 1 

13.4.2 ITS Sustainment and Test Support (manpower) ITS Site 31-Dec-15 Annex J 1 n.a. - 

13.4.3 Documentation, initial spares ITS Site 30-Oct-13 Annex J 1 

13.5 ITS Acceptance ITS Site 30-Oct-13 Annex J 1 

14 Nations and Partners 

14.1 Nations - RESERVED NNHQ 31-Dec-15 Annex L n.a. n.a. n.a. 

14.2 Partners - RESERVED NNHQ 31-Dec-15 Annex L n.a. n.a. n.a. 

15 Remote Sites 

15.1 Site location 1 - Hardware (including 3 year warranty and support) 

Annex M 

and Software (including 1 year warranty and support) Residence of SG 31-Dec-15 

1 n.a. - 


Annex M 

and Software (including 1 year warranty and support) New-York 31-Dec-15 

1 n.a. - 


Annex M 

and Software (including 1 year warranty and support) Kabul 31-Dec-15 

1 n.a. - 


Annex M 

and Software (including 1 year warranty and support) Moscow 31-Dec-15 

1 n.a. - 


Annex M 

and Software (including 1 year warranty and support) Kiev 31-Dec-15 

1 n.a. - 

Evaluated Options 

16 Standing Ordering Agreement - SOA 

16.1 Processing Hardware(Standing Ordering Agreement) Including 3 

NNHQ 


Year Warranty and Support 

31-Mar-15 

1 n.a - Support Year 1-3 

16.2 Processing Software (Standing Ordering Agreement) Including 1 

NNHQ 



31-Mar-15 

1 n.a - Support Year 1 

16.3 Storage Hardware (Standing Ordering Agreement) including 3 year 

NNHQ 


Warranty and support 

31-Mar-15 


16.4 Storage Software (Standing Ordering Agreement) including 1 year 

NNHQ 



31-Mar-15 


16.5 Networking Hardware(Standing Ordering Agreement) Including 3 

NNHQ 



31-Mar-15 


17 Hardware and Software LifeCycle Support and Warranty 

SUB TOTAL FIRM FIXED PRICE CLINS 1 - 16 (FOR COMPARISON WITH CEILING PRICE) (state currency): 

- 








17.1 Hardware Support and Warranty - Year 4 and 5 

17.1.1 Processing Hardware (Base Contract) 

year 4 - 5 Warranty and support 

17.1.2 Storage Hardware (Base Contract) 


17.1.3 Access Switches FO 


17.1.4 Access Switches RJ45 PoE 


17.1.5 Core Switches 


17.1.6 Server Switches 


17.1.7 Wired-Network-Conference Centre 


17.1.8 WLAN 


17.1.9 NS-NGCS-HW 


17.1.10 Business-NGCS/Public -HW 


17.1.11 Public - Internet Access HW 


17.1.12 NS-EAPC-HW 


17.1.13 NS-Business-Info-Sharing-HW 


17.1.14 CIS Management Info-Sharing HW 


17.1.15 Standard Desktop Client 


17.1.16 High Performance Desktop Client 


17.1.17 Network Agnostic Desktop Client 


17.1.18 Mobile Client 


17.1.19 PDA/SmartPhone 


17.1.20 IP Phone 


17.1.21 IP Phone Secretariat 


17.1.22 GSM Blocking 


17.1.23 Wireless Blocking 


17.1.24 IPTV endpoint 


17.1.25 ITS Hardware 


NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

QTY / Man- 

Days 

Unit Price 

Total Price 

01-Jan-19 Annex K Appendix 9 1 n.a. - 


























Book I - SSS - Page 8 of 41 

Final 

Total Price 

Remarks






17.1.26 Remotes Sites - Hardware 


17.1.27 Processing Hardware(Standing Ordering Agreement) year 4 - 5 


17.1.28 Storage Hardware (Standing Ordering Agreement) year 4 - 5 


17.1.29 Networking Hardware(Standing Ordering Agreement) year 4 - 5 


17.1.30 ANWI Travel Kit Client Hardware 

Year 4 - 5 Warranty and support 

17.1.31 ANWI Travel Kit Back-end Hardware 


17.2 Software Support and Warranty - Year 2 to 5 

17.2.1 Processing Software Procurement (Base Contract) 

year 2-5 warranty and support 

17.2.2 Storage Software (Base Contract) 


17.2.3 Network Infrastructure Services Software 


17.2.4 NS-NGCS-SW 


17.2.5 Business-NGCS/Public -SW 


17.2.6 Public - Internet Access SW 


17.2.7 NS-EAPC-SW 


17.2.8 NS-Business-Info-Sharing-SW 


17.2.9 CIS Management Info-Sharing SW 


17.2.10 Voice & Voicemail Software 


17.2.11 E-mail service software 


17.2.12 Fax service software 


17.2.13 IM/Chat service software 


17.2.14 Presence service software 


17.2.15 UCC Directory service software 


17.2.16 Collaboration service software 


17.2.17 UM & Mobility service software 


17.2.18 Software - Standard Client 


17.2.19 Software - High Performance Client 


NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

QTY / Man- 

Days 

Unit Price 

Total Price 




























Final 

Total Price 

Remarks






QTY / Man- 

Days 


17.2.20 Software - Network Agnostic clients 

NNHQ 



17.2.21 Software - Mobile Client 

NNHQ 



17.2.22 Software - PDA/SmartPhone 

NNHQ 



17.2.23 Software - IP Phone 

NNHQ 



17.2.24 Software - IP Phone Secretarial 

NNHQ 



17.2.25 UCC Client Software 

NNHQ 



17.2.26 IPTV Client Software 

NNHQ 



17.2.27 Client Provisioning Software Solution 

NNHQ 



17.2.28 ITS Software 

NNHQ 



17.2.29 Remotes Sites - Software 

NNHQ 



17.2.30 Processing Software (Standing Ordering Agreement) year 2-5 

NNHQ 



17.2.31 Storage Software (Standing Ordering Agreement) year 2-5 warranty 

NNHQ 

and support 


17.2.32 ANWI Travel Kit Client Software 

NNHQ 

2-5 warranty and support 


17.2.33 SMC - Service Design Software 

NNHQ 



17.2.34 SMC - Service Transition Software 

NNHQ 



17.2.35 SMC - Service Operations Software 

NNHQ 



17.2.36 SMC - Service Improvement Software 

NNHQ 



18 Service Life-Cycle Support - Operation (5 year Lifecycle) 

18.1 Year 1 Service Life-Cycle support - Operations 

18.1.1 SMC Service Support operations NNHQ 01-Dec-15 7.4.1, Annex E Appendix 1 1 - - 

18.1.2 SMC Service Transition and management operations NNHQ 01-Dec-15 7.4.1, Annex E Appendix 1 1 - - 

18.1.3 Processing Service (including Network infrastructure services) NNHQ 01-Dec-15 7.4.1, Annex F Appendix 2/5 1 - - 

18.1.4 Storage Service NNHQ 01-Dec-15 7.4.1, Annex F Appendix 3 1 - - 

18.1.5 Print/Scan Service NNHQ 01-Dec-15 7.4.1, Annex F Appendix 4 1 - - 

18.1.6 LAN Service (wired and Wireless) NNHQ 01-Dec-15 7.4.1, Annex F Appendix 6 1 - - 

18.1.7 UCC service NNHQ 01-Dec-15 7.4.1, Annex G 1 - - 

18.1.8 Client Provisioning/Client Devices services NNHQ 01-Dec-15 7.4.1, Annex H 1 - - 

18.1.9 IPTV service NNHQ 01-Dec-15 7.4.1, Annex I Appendix 6 1 - - 









Final 

Total Price 

Remarks






QTY / Man- 

Days 




































19 CoCo Services Year 2 - 5 

19.1 Print/Scan Service - Year 2 Service Cost 

Final 

Total Price 

Remarks 

19.1.1 Contractor Owned / Contractor operated Print/Scan Service NNHQ 01-Dec-16 Annex F Appendix 4 187.00 

Yearly service Cost 

- - 

19.1.2 CoCo Print/Scan Service - Price per page B/W NNHQ 01-Dec-16 Annex F Appendix 4 7,000,000.00 - - Estimate - volume 

19.1.3 CoCo Print/Scan Service - Price per page Colour NNHQ 01-Dec-16 Annex F Appendix 4 3,000,000.00 - - Estimate - volume 




- - 






- - 









QTY / Man- 

Final 


Days 

Total Price 

Remarks 





- - 



19.5 IPTV Service - Year 2 Service Cost 



1 Service cost/year 













GRAND TOTAL FIRM FIXED PRICE CLINS 1 - 19 (state currency): 

20 Optional Hardware and Software (non Evaluated) 

20.1 Printing 

20.1.1 CoCo Personal/Workgroup Printer (B/W and Colour) NNHQ n.a. Annex F Appendix 4 1 NP NP NP Sheet ANWI IDIQ 

20.2 Switching 

20.2.1 24 Port Access Switch with uplinks- FO - including 3 year Warranty 

NNHQ 


and support 

n.a. 

1 NP NP NP Sheet ANWI IDIQ 

20.2.2 24 Port Access Switch with uplinks- FO 

NNHQ 


n.a. Annex K Appendix 9 1 NP NP NP Sheet ANWI IDIQ 

20.2.3 48 Port Access Switch - RJ45 with uplinks - including 3 year 

NNHQ 



n.a. 


20.2.4 48 Port Access Switch - RJ45 with uplinks 

NNHQ 



20.2.5 WLAN Access Point - including 3 year Warranty and support NNHQ n.a. Annex F Appendix 6 1 NP NP NP Sheet ANWI IDIQ 

20.2.6 WLAN 

NNHQ 



20.3 Clients 

20.3.1 Standard Desktop Client - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 




NNHQ 

support 

n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 



20.3.5 Mobile Client - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 



20.3.7 PDA/SmartPhone - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 



20.3.9 IP Phone - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 

- 








QTY / Man- 

Days 

Unit Price 

Total Price 

Final 

Total Price 


NNHQ 



20.3.11 IP Phone Secretariat - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 



20.3.13 IPTV endpoint - including 3 year warranty and support NNHQ n.a. Annex I Appendix 6 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 



20.3.15 2nd Monitor (21") - - including 3 year warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 

20.3.16 2nd Monitor (21") 

NNHQ 



20.3.17 Monitor Upgrade (24") 

NNHQ 



20.3.18 Monitor Upgrade (24") - including 3 year warranty and support NNHQ n.a. Annex K Appendix 9 1 NP NP NP Sheet ANWI IDIQ 

20.3.19 2nd Monitor (24") - including 3 year warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 

20.3.20 2nd Monitor (24") 


NNHQ 


20.3.21 Softphone Handset - including 3 year warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 

20.3.22 Softphone Handset 

NNHQ 



20.3.23 Client Software baseline - including 1 year warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 

20.3.24 Client Software baseline - year 2 - 5 Warranty and support NNHQ n.a. Annex K Appendix 9 1 NP NP NP Sheet ANWI IDIQ 

20.3.25 UCC Client Software - including 1 year Warranty and support NNHQ n.a. Annex G 1 NP NP NP Sheet ANWI IDIQ 



NNHQ 



NNHQ 


and support 

n.a. 



NNHQ 



20.4 Secure Site Communications - TETRA 

20.4.1 Handset NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.2 Vehicle-based NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.3 Office-based NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.4 Base Station NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.5 Repeater NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.6 Mast NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

21 System Administrator Training 

21.1 Network Service 

21.1.1 Storage (Capacity) Service NNHQ Campus 31-Mar-15 Annex F Appendix 3 1 incl. Training material 

21.1.2 Print/Scan Service NNHQ Campus 31-Mar-15 Annex F Appendix 4 1 incl. Training material 

21.1.3 Cross Domain Services NNHQ Campus 31-Mar-15 Annex E Appendix 2 1 incl. Training material 

21.2 Local Area Network (LAN) Services 

21.2.1 Switching Service NNHQ Campus 31-Mar-15 Annex F Appendix 6 1 incl. Training material 

21.2.2 Wireless Service NNHQ Campus 31-Mar-15 Annex F Appendix 6 1 incl. Training material 

21.2.3 Wireless Blocking Service NNHQ Campus 01-Dec-15 Annex I Appendix 3 1 incl. Training material 

21.2.4 GSM Blocking Service NNHQ Campus 01-Dec-15 Annex I Appendix 4 1 incl. Training material 

21.3 Unified Communications Capability Services 

21.3.1 Voice NNHQ Campus 01-Dec-15 Annex G Appendix 1 1 incl. Training material 

21.3.2 VoiceMail NNHQ Campus 01-Dec-15 Annex G Appendix 2 1 incl. Training material 

21.3.3 E-Mail NNHQ Campus 01-Dec-15 Annex G Appendix 5 1 incl. Training material 

21.3.4 Presence NNHQ Campus 01-Dec-15 Annex G Appendix 9 1 incl. Training material 



Remarks






QTY / Man- 

Final 


Days 

Total Price 

Remarks 

21.3.5 Instant Messaging NNHQ Campus 01-Dec-15 Annex G Appendix 8 1 incl. Training material 

21.3.6 Collaboration (Whiteboard) NNHQ Campus 01-Dec-15 Annex G Appendix 11 1 incl. Training material 

21.3.7 Video Tele-Conferencing (VTC) NNHQ Campus 01-Dec-15 Annex G Appendix 4 1 incl. Training material 

21.3.8 VMR NNHQ Campus 01-Dec-15 Annex G Appendix 4 1 incl. Training material 

21.4 Client Provisioning 

21.4.1 Client provisioning service NNHQ Campus 31-Dec-15 Annex H Appendix 3 1 incl. Training material 

21.5 Supplementary Services 

21.5.1 GSM NNHQ Campus 31-Dec-15 Annex I Appendix 2 1 incl. Training material 

21.5.2 IPTV NNHQ Campus 31-Dec-15 Annex I Appendix 6 1 incl. Training material 

21.5.3 Security Communications (radio) NNHQ Campus 31-Dec-15 Annex I Appendix 5 1 incl. Training material 

TOTAL PRICE FOR BID EVALUATION - CLIN 1 -19 + ESTIMATED ENERGY COST (ref. TCO Calculation Sheet) 

(state currency): - 







TCO 

Acquisition (ca) Commissioning (cc) Operation (co) Support / Service Fees (cs) TOTAL 

TOTAL TCO - - - - - 

TCO = ca + cc + co + cs 

Cost Type Service Cost CLIN Summation 

Cost of Acquisition (CA) 

Cost of Commissioning (CC) 

Cost of Operation (CO) 

SMC - 10 

Processing - 8.1, 16.1, 16.2 

Storage - 8.2, 16.3, 16.4 

Networking - 8.5, 8.6, 16.5 

Cross-Domain gateways - 8.7 

Network Infrastructure Services - 8.4 

Clients & Client provisioning - 11 

UCC - 9 

Print/Scan Service n.a. n.a. 

Remote Sites - 15 

IPTV Service - 12.3.2 

ITS - 13.2, 13.3 

GSM & Blocking - 12.1.2, 12.1.3 

(Manpower and other costs related to design/install/commission 

Manpower, Software and tools & travel - 1, 2, 3, 4, 5, 6, 7, 12.2, 13(excl 13.2 & 13.3) 

(ManPower and Power Cost) 

SMC - 18.1.1, 18.1.2, 18.2.1, 18.2.2,18.3.1, 18.3.2, 18.4.1, 18.4.2, 18.5.1, 18.5.2 

Processing (including network Infrastructure 

and CDGW Services) - 18.1.3, 18.2.3, 18.3.3, 18.4.3, 18.5.3 + Power cost of Processing Sheet & CDGW Sheet 

Storage - 18.1.4, 18.2.4, 18.3.4, 18.4.4, 18.5.4 + Power cost of Storage Sheet 

Networking - 18.1.6, 18.2.6, 18.3.6, 18.4.6, 18.5.6 + Power cost of Networking Sheet 

Clients & Client provisioning (including 

Remote sites) - 18.1.8, 18.2.8, 18.3.8, 18.4.8, 18.5.8 + Power cost of Client Sheet 

UCC - 18.1.7, 18.2.7, 18.3.7, 18.4.7, 18.5.7 

Print/Scan Service - 18.1.5, 18.2.5, 18.3.5, 18.4.5, 18.5.5 + Power cost of Print-Scan Sheet 

IPTV Service - 18.1.9, 18.2.9, 18.3.9, 18.4.9, 18.5.9 + Power cost of IPTV Sheet 

Cost of Support - Service Fees (CS) 

(Support/Maintenance contracts) 

SMC - 17.2.33 - 36 

Processing - 17.1.1, 17.1.27, 17.2.1, 17.2.30 

Storage - 17.1.2, 17.1.28, 17.2.2, 17.2.31 

Networking - 17.1.3 - 8, 17.1.29 

Cross-Domain gateways - 17.1.9 - 14, 17.2.4 - 9 

Network Infrastructure Services - 17.2.3 

Clients & Client provisioning - 17.1.15 - 21, 17.1.26, 17.1.30 - 31, 17.2.18 - 27, 17.2.29, 17.2.32 

UCC - 17.2.10 - 17 

Print/Scan Service - 8.3, 19.1, 19.2, 19.3, 19.4 

IPTV Service - 12.3.1, 19.5, 19.6, 19.7, 19.8, 17.1.24 

ITS - 17.1.25, 17.2.28 

GSM - 12.1.1, 17.1.22 - 23 


Book I - TCO Calculation - Page 15 of 41


Item Profile Profile Description Day Price Month Price Year price 

(Please list all types of manpower resources that are offered for the ANWI Project) 




1 Senior Project Manager 

2 Add Lines - Complete as needed 


Book I - Manpower Resources - Page 16 of 41

Item Description Part Number Vendor SOW Reference 

1 Printing 

CoCo Personal/Workgroup Printer (B/W and Colour) - Yearly 

1.1 Service Cost 


2 Switching 

24 Port Access Switch with uplinks- FO - including 3 year 

2.1 Warranty and support 


24 Port Access Switch with uplinks- FO 

2.2 year 4 - 5 Warranty and support Annex K Appendix 9 

48 Port Access Switch - RJ45 with uplinks - including 3 year 



48 Port Access Switch - RJ45 with uplinks 


WLAN Access Point - including 3 year Warranty and support 


2.5 

WLAN 


3 Clients 

Standard Desktop Client - including 3 year Warranty and 

3.1 support Annex H Appendix 3 

Standard Desktop Client 


High Performance Desktop Client - including 3 year 

3.3 Warranty and support Annex H Appendix 3 

High Performance Desktop Client 


3.5 Mobile Client - including 3 year Warranty and support Annex H Appendix 3 

Mobile Client 


3.7 PDA/SmartPhone - including 3 year Warranty and support Annex H Appendix 3 

PDA/SmartPhone 


3.9 IP Phone - including 3 year Warranty and support Annex H Appendix 3 

IP Phone 

4 year 4 - 5 Warranty and support Annex K Appendix 9 

4.1 IP Phone Secretariat - including 3 year Warranty and support Annex H Appendix 3 

IP Phone Secretariat 


4.3 IPTV endpoint - including 3 year warranty and support Annex I Appendix 6 

IPTV endpoint 


4.5 2nd Monitor (21") - - including 3 year warranty and support Annex H Appendix 3 

2nd Monitor (21") 


Monitor Upgrade (24") 

4.7 year 4 - 5 Warranty and support Annex H Appendix 3 

Monitor Upgrade (24") - including 3 year warranty and 

4.8 support Annex K Appendix 9 

4.9 2nd Monitor (24") - including 3 year warranty and support Annex H Appendix 3 



5.1 Softphone Handset - including 3 year warranty and support Annex H Appendix 3 

Softphone Handset 


Client Software baseline - including 1 year warranty and 


5.4 Client Software baseline - year 2 - 5 Warranty and support Annex K Appendix 9 

UCC Client Software - including 1 year Warranty and support 

Annex G 

5.5 

UCC Client Software 

5.6 year 2-5 warranty and support Annex K Appendix 9 

Client Provisioning Software Solution - including 1 year 



Client Provisioning Software Solution 


4 Secure Site Communications - TETRA 

4.1 Handset Annex I Appendix 5 

4.2 Vehicle-based Annex I Appendix 5 

4.3 Office-based Annex I Appendix 5 

4.4 Base Station Annex I Appendix 5 

4.5 Repeater Annex I Appendix 5 

4.6 Mast Annex I Appendix 5 


Quantity - 1 Quantity - 1 > < 50 

Quantity - 50 > < 100 

Quantity - 50 > < 100 

Unit price 

Unit price 

Unit price 

Unit price 

Year 1 Year 2 Year 3 Year 4 Year 5 Year 1 Year 2 Year 3 Year 4 Year 5 Year 1 Year 2 Year 3 Year 4 Year 5 Year 1 Year 2 Year 3 Year 4 Year 5 





Book I - IDIQ Equipment - Page 17 of 41

CLIN Description Resource type Company 

Instructions: 

Mandays/U 

nit 


Please list under each Top level CLIN all the resources required for ALL Sub-CLIN's 

Manpower resources listed here shall also be listed under the ANWI Manpower Resources sheet 

The bidder shall also indentify the company the resource is from. Sub-contractors shall be named. 

The bidder shall provide the manpower, Software & Tools and travel prices under the respective headers 

Day Price Total Unit price Total Nr Travels Travel Cost 

Manpower Software and tools Travel 

1 Project Management 0.00 0.00 0.00 

Resource (eg. project Manager, 

Software Tool, License Costs) 

- - 

Add Lines - Complete as needed - - 

2 ANWI Service and System Design 0.00 0.00 0.00 



- - 


3 Site Survey 0.00 0.00 0.00 



- - 


4 Testing 0.00 0.00 0.00 



- - 


5 ANWI Implementation and Transition 0.00 0.00 0.00 



- - 


6 ANWI Service and System Operations Processes 0.00 0.00 0.00 



- - 


7 ANWI Service Improvement 0.00 0.00 0.00 



- - 


12.2 Security Communications 0.00 0.00 0.00 



- 

Add Lines - Complete as needed - 

13 Integration and Testing 

Service (ITS) 

0.00 0.00 0.00 



- 


TOTAL 0.00 0.00 0.00 





Book I - Implementation - Page 18 of 41





Ref CLIN Service - Manpower Resource Profile Year 1 Year 2 Year 3 Year 4 Year 5 

TOTAL (O&M) 

FTE Cost FTE Cost FTE Cost FTE Cost FTE Cost 

18.1.1 SMC Service - support 

ex. Service desk engineer - - - - - - 

Add Lines - Complete as needed - - - - - - 

TOTAL - - - - - - - - - - - 

18.1.2 SMC Service - Transition and management 

ex. Service level manager - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.3 Processing Service (including Network infrastructure services & CDGW) 

ex. Server Administrators - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.4 Storage Service 

ex. Storage Administrators - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.6 LAN Service (wired and Wireless) 

ex. Network Administrators - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.8 Client Provisioning/Client Devices services (including Remote Sites) 

ex. Support engineer - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.7 UCC service 

ex. UCC engineer - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.5 Print/Scan Service 



TOTAL - - - - - - - - - - - 

18.1.9 IPTV Service 



TOTAL - - - - - - - - - - - 


Book I - Service Operations - Page 19 of 41


SMC Partnumber Vendor SSS Ref Quantity 

Combined Unit Price Year 1 

Year 2 Year 3 Year 4 Year 5 

TOTAL 

supported Power/ Cooling 

Units clients Requirement 

Procurement Support Support Support Support Support Procurement Support 

SMC - Service Design 10.1 - - - - - - 

Ex. Software ABC 0 0 n.a. - - - - - - - - - 

Add Lines - Complete as needed 0 0 n.a. - - - - - - - - - 

PFE SW 

ex. Microsoft License n.a. n.a. - - - - - - - - 


SMC - Service Transition 10.2 - - - - - - 



PFE SW 



SMC - Service Operations 10.3 - - - - - - 



PFE SW 



SMC - Service Improvement 10.4 - - - - - - 



PFE SW 



TOTAL n.a. - - - - - - - - 




COSTS Year 1 Year 2 Year 3 Year 4 Year 5 TOTAL 

Procurement - n.a. n.a. n.a. n.a. - 

Support - - - - - - 

Power (@0.1182€ KW/h) n.a. n.a. n.a. n.a. n.a. - 

Manpower Cost - - - - - - 

TOTAL - - - - - - 


Book I - SMC - Page 20 of 41


Description Partnumber Vendor SSS Reference Quantity 

Unit price Year 1 





Total 

Units 

Combined Power/ 

Cooling 

Nr of Servers 

(Max) 

Requirement 

(KW/H per year) 


Server Hardware 

Server Baseline Hardware (ANWI) 8.1.1.1 0 - - - - - - 

ANWI Physical Server 0 - - - - - - - - - - 

ANWI VM Host Server 0 - - - - - - - - - - 

Add Lines - Complete as needed 0 0 - - - - - - - - - - 

Server SOA Hardware 16.1 0 - - - - - - 

ICTM Physical Server 0 0 - - - - - - - - - - 

ICTM VM Host Server 0 0 - - - - - - - - - - 

Server Software 

Server Baseline Software (ANWI) 8.1.2.1 - - - - - - 

Virtualisation Software n.a. n.a. - - - - - - - - - 

Add Lines - Complete as needed n.a. n.a. - - - - - - - - - 

PFE SW 

Microsoft OS n.a. n.a. - - - - - - - - 

Add Lines - Complete as needed - - - - - - - - 

Server SOA Software 16.2 - - - - - - 


Add Lines - Complete as needed n.a. n.a. - - - - - - - - 

PFE SW 



TOTAL 0 0 - - - - - - - - - 


Procurement - n.a n.a n.a n.a - 

Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 

Server per FTE 

Avg cost per server (year) 

#DIV/0! 

#DIV/0! 


Book I - Processing - Page 21 of 41





Description Partnumber Vendor SSS Ref Quantity 


Unit price Year 1 Year 2 Year 3 Year 4 Year 5 

TOTAL 

Cooling 

Requirement 

Units TB (KW/H per year) 


Storage Hardware 

Storage Baseline Hardware (ANWI) 8.2.1.1 - - - - - - 

SAN Infrastructure 0 n.a. - - - - - - - - - 

ANWI Tier 1 Storage 0 0 - - - - - - - - - - 


ANWI Tier 3 Storage 0 0 - - - - - - - - - 

Removable Media 0 0 - - - - - - - - - - 


Storage SOA Hardware 16.3 - - - - - - 

SAN Infrastructure - - - - - - - - - 






Storage Software 

Storage Baseline Software (ANWI) 8.2.2.1 - - - - - - 

xxxx 0 n.a. - - - - - - - - - 

Add Lines - Complete as needed 0 n.a. - - - - - - - - - 

Storage SOA Software 16.4 - - - - - - 

xxxx 0 n.a. - - - - - - - - - 


TOTAL 0 1956 - - - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 

Cost per TB - 


Book I - Storage - Page 22 of 41





Description Partnumber Vendor SSS REF Quantity 

Combined Unit price Year 1 


TOTAL 

Power/ Cooling 

Units Ports Requirement 


HARDWARE (Baseline) 

Core Switches 8.5.3 - - - - - - - 

Core switches 0 0 - - - - - - - - - - 


Access Switches FO 8.5.1 - - - - - - - 

Access Switches FO 0 0 - - - - - - - - - - 


Access Switches PoE 8.5.2 - - - - - - - 

Access Switches PoE 0 0 - - - - - - - - 


Server Switches 8.5.4 - - - - - - - 

Server Switches 0 0 - - - - - - - - - - 


Confrence Switching 8.5.5 - - - - - - - 

Agnostic switches 0 0 - - - - - - - - - - 


WLAN Hardware 8.6.1 - - - - - - - 

WLAN Access Points 0 0 - - - - - - - - - - 

WLAN Controllers 0 0 - - - - - - - - - - 


HARDWARE (SOA) 16.5 - - - - - - 

Core Switches - - - - - - - 

Core switch components 0 0 - - - - - - - - - - 


Server Switches - - - - - - - 



TOTAL 0 0 - - - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 

Manpower cost - - - - - - 

TOTAL - - - - - - 

Description Year Month 

Cost Per port #DIV/0! #DIV/0! 


Book I - Networking - Page 23 of 41








TOTAL 


Cooling 

Requirement 

Units (KW/H per year) 


Cross-Domain HW 

CDGW 1 Hardware 8.7.1 0 - - - - - - 

Processing 

ANWI Physical Server 0 n.a. - - - - - - - - - - 

Add Lines - Complete as needed 0 n.a. - - - - - - - - - - 

Storage 


Networking 


CDGW 2 Hardware 8.7.3 0 - - - - - - 

Processing 



Storage 


Networking 


CDGW 3 Hardware 8.7.5 0 - - - - - - 

Processing 



Storage 


Networking 


CDGW 4 Hardware 8.7.7 0 - - - - - - 

Processing 



Storage 


Networking 


CDGW 5 Hardware 8.7.9 0 - - - - - - 

Processing 



Storage 


Networking 


CDGW 6 Hardware 8.7.11 0 - - - - - - 

Processing 



Storage 


Networking 


Cross-Domain SW 

CDGW 1 8.7.2 - - - - - - 

to be completed 0 n.a. n.a. - - - - - - - - - 


PFE SW 


Book I - CDGW - Page 24 of 41








TOTAL 


Cooling 

Requirement 




Add Lines - Complete as needed n.a. - - - - - - - - 

CDGW 2 8.7.4 - - - - - - 



PFE SW 



CDGW 3 8.7.6 - - - - - - 



PFE SW 



CDGW 4 8.7.8 - - - - - - 



PFE SW 



CDGW 5 8.7.10 - - - - - - 



PFE SW 



CDGW 6 8.7.12 - - - - - - 



PFE SW 



TOTAL - - - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 

Manpower Cost n.a n.a n.a n.a n.a - 

TOTAL - - - - - - 


Book I - CDGW - Page 25 of 41



Combined Power Unit Price Year 1 


TOTAL 

Requirement 



CLIENTS -HARDWARE 

Desktop Client - Standard 11.1.1 1981 - - - - - - 

Desktop Client 0 - - - - - - - - - - 

TFT Monitor 0 - - - - - - - - - - 

Multimedia Keyboard 0 - - - - - - - - - - 

Mouse 0 - - - - - - - - - - 

Smart-Card Reader 0 - - - - - - - - - - 

Add Lines - Complete as needed 0 - - - - - - - - - - 

Desktop Client - High Perf 11.1.2 162 - - - - - - 


TFT Monitor 0 - - - - - - - - - - 


Mouse 0 - - - - - - - - - - 



Desktop Client - Agnostic 11.1.3 284 - - - - - - 


TFT Monitor 0 - - - - - - - - - - 


Mouse 0 - - - - - - - - - - 



Mobile Client 11.1.4 1600 - - - - - - 

Mobile Client - Laptop 0 - - - - - - - - - - 

Mobile Client - Tablet 0 - - - - - - - - - - 

Docking solution 0 - - - - - - - - - - 

TFT Monitor 0 - - - - - - - - - - 


Mouse 0 - - - - - - - - - - 



Smartphone/PDA 11.1.5 573 - - - - - - 

Smartphone/PDA 0 - - - - - - - - - - 


UCC phone - Standard 11.1.6 493 - - - - - - 

UCC Phone 0 - - - - - - - - - - 


UCC phone - Secretarial 11.1.7 246 - - - - - - 

UCC secretatial phone 0 - - - - - - - - - - 


CLIENTS -SOFTWARE 

Client Provisioning 11.2.10 - - - - - - 

Client provisioning SW 0 n.a. - - - - - - - - - 


PFE SW 

ex. Microsoft License n.a. - - - - - - - - 




PFE SW 

NATO Desktop n.a. n.a. n.a. 

Desktop Client - High Performance 11.2.2 162 - - - - - - 


PFE SW 




PFE SW 


Mobile Client 11.2.4 1600 - - - - - - 






Book I - Clients - Page 26 of 41





TOTAL 

Requirement 



PFE SW 




PFE SW 


IP Phone 11.2.6 493 - - - - - - 


IP Phone Secretarial 11.2.7 246 - - - - - - 


UCC Client Software 11.2.8 - - - - - - - 

UCC Softphone Client 0 n.a. - - - - - - - - - 


IPTV Client Software 11.2.9 - - - - - - - 


TOTAL 5339 - - - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 

Average Cost per client (year) - 





Book I - Clients - Page 27 of 41





TOTAL 


Units 

clients Requirement 


Infrastructure Services 8.4.1 - - - - - - 

NAC Software 0 0 n.a. - - - - - - - - - 


PFE SW 






TOTAL - - - - - - - - 



Support - - - - - - 


Manpower Cost n.a. n.a. n.a. n.a. n.a. - 

TOTAL - - - - - - 




TOTAL 


Units 



UCC Services 

Voice & Voicemail 9.1.1 - - - - - - 

xxxx 0 0 n.a. - - - - - - - - - 


PFE SW 



E-mail 9.2.1 - - - - - - 

E-mail software 0 0 n.a. - - - - - - - - - 


PFE SW 



Fax Service 9.3.1 - - - - - - 

Fax software 0 0 n.a. - - - - - - - - - 


PFE SW 


Add Lines - Complete as needed 0 - n.a. - - - - - - - - - 

IM/Chat Service 9.4.1 - - - - - - 

IM/Chat software 0 0 n.a. - - - - - - - - - 


PFE SW 



Presence Service 9.5.1 - - - - - - 

Presence software 0 0 n.a. - - - - - - - - - 


PFE SW 



UCC Directory Service 9.6.1 - - - - - - 



PFE SW 



Collaboration Service 9.7.1 - - - - - - 


Book I - Applications - Page 28 of 41





TOTAL 


Units 



collaboration software 0 0 n.a. - - - - - - - - - 


PFE SW 



Unified Messaging and Mobility 

Service 9.8.1 - - - - - - 

UM software 0 0 n.a. - - - - - - - - - 


PFE SW 



TOTAL - - - - - - - - - - - 

Summary Table for UCC Service 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 





Book I - Applications - Page 29 of 41






Unit price Year 1 Year 2 Year 3 Year 4 Year 5 Total 

Units 

n.a. 


Cooling 

Requirement 


Service Cost/ 

per Unit- Page 

Service Cost/ 


Service Cost/ 

per Unit- 

Page 

Service Cost/ 


Service Cost/ per 

Unit- Page 

Lifecycle 

(5 year) 

Print/Scan Baseline 

Print/Scan service MFP printer 8.3.1 187 n.a. - - - - - 

CoCo Print Server - n.a. n.a. n.a. n.a. n.a. n.a n.a. 

CoCo MFP Colour printer - n.a. n.a. n.a. n.a. n.a. n.a n.a. 


- 

Pay-per-page - - - - - 

Price per page B/W 8.3.2 7,000,000.00 n.a. n.a. n.a. - - - - - - 

Price per page Colour 8.3.3 3,000,000.00 n.a. n.a. n.a. - - - - - - 

n.a. n.a. - - 

TOTAL 0 - - - - - - - 


Procurement n.a. n.a. n.a. n.a. n.a. - 

Usage (Pages) - - - - - - 

Service Fee - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 


Book I - Print-Scan - Page 30 of 41








Total 


Cooling 

Requirement 



IPTV Service 

IPTV Endpoints 12.3.2 - - - - - - - 

60" display screens with integrated 

IPTV media player 425 - - - - - - - - 


TOTAL - - - - - - - - - 



Support - - - - - - 


Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 




Total 


Cooling 

Requirement 

(KW/H per unit per 

Units year) 


GSM Service 

GSM Blocking 12.1.2 - - - - - - - 

GSM Blocking Equipment 1 - - - - - - - - 


WLan Blocking 12.1.3 - - - - - - - 

WLan Blocking Equipment 1 - - - - - - - - 


TOTAL - - - - - - - - - 



Support - - - - - - 

Service Fee - NP NP NP NP - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 


Book I - Other Systems - Page 31 of 41








Total 


Cooling 

Requirement 



ITS Hardware 

Hardware 13.2 0 - - - - - - 

Servers - - - - - - - - - - - 

Storage - - - - - - - - - - - 

Networking (including ITS Cabling) - - - - - - - - - - - 

Cross-domain Components - - - - - - - - - - - 

Client Infrastructure - - - - - - - - - - - 

Print Scan - - - - - - - - - - - 

IPTV - - - - - - - - - - - 

Add Lines - Complete as needed - - - - - - - - - - - 


Software 13.3 - - - - - - 

Virtualisation Software - n.a. - - - - - - - - - 

Add Lines - Complete as needed n.a. - - - 

PFE SW 


Add Lines - Complete as needed - n.a. - - - - - - - - - 

TOTAL - - - - - - - - - 

ITS Test Support and sustainment 

Manpower 13.4.2 n.a. - - - - - 

System Engineer - n.a. - - - - - - - - - 


TOTAL - n.a. - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 


Book I - ITS - Page 32 of 41






Combined Power 

Year 1 


TOTAL 

Requirement 

Units (KW/H per year) Unit Price Procurement Support Support Support Support Support Procurement Support 

Remote Locations - Hardware - - 

Location 1 15.1 - - - - - - - - 

NS Workstation 5 - - - - - - - - - - 


Location 2 15.2 - - - - - - - - 



Location 3 15.3 - - - - - - - - 



Location 4 15.4 - - - - - - - - 


NR Workstation 30 - - - - - - - - - - 


Location 5 15.5 - - - - - - - - 




Travel Kits - Clients Hardware 11.1.8 - - - - - - - - 

NS mobile client 1 - - - - - - - - - - 

Small formfactor printer 1 - - - - - - - - - - 


Travel Kits - Back-end Equipment 11.1.9 - - - - - - - - 

VPN Concentrator 0 - - - - - - - - - - 

Switching 0 - - - - - - - - - - 


Remote Locations - Software - - 

Location 1 15.1 - - - - - - - - 


PFE SW 

NATO Desktop n.a. n.a. NATO PFE 

Location 2 15.2 - - - - - - - - 


PFE SW 


Location 3 15.3 - - - - - - - - 


PFE SW 


Location 4 15.4 - - - - - - - - 


PFE SW 


Location 5 15.5 - - - - - - - - 


PFE SW 


Travel Kits - Clients Software 11.2.11 - - - - - - - - 


PFE SW 


TOTAL 77 - - - - - - - - - 


Book I - Remote Sites - Page 33 of 41






Procurement - - - - - - 

Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 



Book I - Remote Sites - Page 34 of 41





CONTRACTOR PRICING SUMMARY 

DETAILED DESCRIPTION OF COST ELEMENTS 

1. DIRECT MATERIAL QUANTITY UNIT COST UNIT COST € TOTAL EST COST € REFERENCE 

A. PURCHASED PARTS 

B. SUBCONTRACTED ITEMS 

C. OTHER- (1)Raw Material 

(2) Standard Commercial Items (COTS) 

2. MATERIAL OVERHEAD (RATE % X TOTAL EST COST € BASE) 

TOTAL DIRECT MATERIAL 

3. DIRECT LABOR (INDICATE LABOR CATEGORIES) EST HRS RATE/HR RATE € TOTAL EST COST € REFERENCE (CLIN) 

TOTAL DIRECT LABOR 

4. LABOR OVERHEAD O.H. RATE (X) BASE 

TOTAL LABOR OVERHEAD 

5. OTHER DIRECT COSTS QUANTITY UNIT COST UNIT COST € TOTAL EST COST € REFERENCE 

A. SPECIAL EQUIPMENT/CFE/NFE 

TOTAL SPECIAL EQUIPMENT 

B. TRAVEL 

(1) TRANSPORTATION 

(2) PER DIEM 

TOTAL TRAVEL 

C. CONSULTANTS OTHER SERVICES 

TOTAL INDIVIDUAL CONSULTANT SERVICES 

D. OTHER 

TOTAL OTHER 

SUBTOTAL DIRECT COST & OVERHEAD 

6. GENERAL & ADMINISTRATIVE (G&A) (RATE % X TOTAL EST COST € BASE) 

7. TOTAL ESTIMATED FEE/ PROFIT % 

8. OTHER FACTORS 

9. GRAND TOTAL 


Book I - Pricing Summary - Page 35 of 41


Nr Org Unit Job Type Nr Staff Main Activities Skill level 

ICTM 

1 ICTM-Ops Manager 1 Manage ICTM-Ops ITIL, Senior ICT manager, PRINCE2 

2 ICTM-Ops Change Manager 1 Change Management process owner ITIL expert 

3 ICTM-Ops Configuration Manager 1 CM process owner ITIL expert 




4 ICTM-Ops-Systems Mngt Manager 1 Manage ICTM-Ops-Systems Management team Managerial level infosec knowledge 

5 ICTM-Ops-Systems Mngt Infosec Analyst 5 

Infosec operations, operate the ICT security 

systems, respond to Infosec incidents 

6 ICTM-Ops-Network Mngt Manager 1 Manage ICTM-Ops Network Management 

7 ICTM-Ops-Network Mngt Network Engineer 1 

Project related network engineering work. 3rd line 

network management support 

8 ICTM-Ops-Network Mngt Network Analysts 2 1st & second line network management support 

LRE CPE installation, 1st line support, modifying 

wiring, install new wiring & patch panels, mounting 

9 ICTM-Ops-Network Mngt Network Data Cabling Engineer 2 physical equipment 

1 Senior and 4 professional level Infosec product 

specialists. Operate and set up infosec systems. Detect 

security incidents. By analysing usage patterns. 

Senior network engineering level knowledge (LAN 

switches, routers, firewall, media conversion, cable 

management, network management, voice, VOIP, WAN). 

PRINCE2, ITIL 



management, network management, voice). PRINCE2, 

ITIL. 

Professional level network engineering knowledge (LAN 


management, network management). ITIL 

Junior LAN engineer, Cabling techniologies (F.O., 

structured cabling, coax) including measurement (OTDR, 

UTP). Cabling management system. 

10 ICTM-Ops-Network Mngt Senior Voice Engineer 2 1st and 2nd line support, PABX system changes 

Senior level TDM-based PABX knowledge (Philips Sopho 

30xx series), voice mail system, tarification system. 

11 ICTM-Ops-Network Mngt junior Voice Engineer 2 1st line voice support, voice installations (IMAC) 

Manage & maintain conference room AV and 

ICTM-Ops-Mulimedia 

interpretation systems, supporting events on and 

12 Systems Mngt Multimedia Engineer 3 off site. 

Management and support on databases and 

Junior level TDM-based PABX knowledge (Philips Sopho 


Senior level AV technical knowledge. 

13 ICTM-Ops-Database Support Database Administrator 2 related infrastructure. 

Advanced DBA & system administrator, MS SQL, Oracle 

Manage the Service Center organisation, ITIL, Incident & problem management, professional ICT 

14 ICTM-Ops-Service Center Manager/Deputy Manager 2 commmunicate with end users 

management level 

ICTM-Ops-Service Center- 

15 Service Desk Team Leader 2 Trouble shooting Broad ICT knowledge 


16 Service Desk Senior Analyst 1 Trouble shooting Broad ICT knowledge 


17 Service Desk Analyst 2 Trouble shooting Broad ICT knowledge 


18 Service Desk Junior Analyst 3 Call intake, Resolve majority calls Broad ICT knowledge 

Patching, Software deployment, User 


administration, Workstation manegment and Altiris knowledge, Deep Active Directory & Microsoft OS, 

19 Workst SW Mngt Team Leader 1 image development 

network administration knowledge 

20 

21 


Workst SW Mngt Senior Analyst 2 


IMAC Team Leader 1 


administration, Workstation manegment and 

image development 

Workstation staging & repair, end user equipment 

deployment 

Altiris knowledge, Deep Active Directory & Microsoft OS, 


ICT hardware knowledge, client OS knowledge, Altiris 

experience, AD experience 


Book I - Manpower (ICTM) - Page 36 of 41




Workstation staging & repair, end user equipment ICT hardware knowledge, client OS knowledge, Altiris 

22 IMAC Analyst 7 deployment 


23 ICTM-Ops-Server Mngt Manager 1 

Manage the Server & Security systems team. 

Deputise for Head ICTM OPS. Role in projects 

related to servers & storage. 

ITIL, PRINCE2, ICT manager, senior system 

administrator, storage management, VM Ware 

virtualisation, multi-vendor servers management 




24 ICTM-Ops-Server Mngt Server Support Assistant 3 

Manage continuously the server, storage and 

virtualisation environment as well as related 

services e.g. Blackberry. Trouble ticket resolution. 

Professional level system administrator, multi-vendor 

server management, VM Ware 


25 ICTM-Ops-Server Mngt Junior Server Support Assistant 2 



Junior system administrator, multi-vendor server 

management, VM Ware 

26 ICTM-Arch Mngt Infrastructure Architect 2 

Infrastructure & ICT security related architecture 

development 

NAF, ICT security architecture training, deep 

infrastructure & ICT security knowledge 

27 ICTM-Arch Mngt CAM Engineer 1 Design of server & storage solutions MCSE, senior level server & storage knowledge 

Sub-total ICTM 54 

COMMCEN 

47 COMMCEN-Video VTC-Technican 3 

48 COMMCEN-Video VTC-Operator 3 

49 COMMCEN-Video VTC-Planner 2 

Technical analysis of functional business 

requirements; 

Develop, install & maintain VTC solutions (NGCS 

and NON NGCS); 

Develop, install & maintain AV systems (NGCS 


Provide support as Second line Service Desk. 

Prepare, test & monitor VTC sessions (NGCS and 

NON NGCS) 

Book and plan VTC request (NGCS and NON 

NGCS) 

Support VTC Testing 

Knowledge of ICT 

ADP Processing, office automation tools 

Knowledge of VTC and AV systems 

Knowledge of ICT architectural design 

System related knowledge of NATO Infosec regulations 

Knowledge of Crypto systems & procedures 







Knowledge of NATO security policies & processes 



50 COMMCEN-Voice System-Engineer 3 

51 COMMCEN-Data Client Support Technician 2 

Install, Maintain and Support all Voice systems 

under Combranch Authority (in NGCS and NON 

NGCS); 

Update and Keying of all Secure Voice Systems 

(NGCS and NON NGCS); 

Provide support as Second line Service Desk 

Support all Client orientated Software/hardware 

applications under Combranch authority; 


Knowledge of Voice communications (Analogue, digital 

and VOIP) 

Knowledge in Data communications (Analogue, digital 

and IP) 




Knowledge of common OS 







requirements 



Develop, install & maintain local and remote LANs Knowledge of common OS 

under Combranch authority; 

Knowledge of Server administration 

52 COMMCEN-Data LAN Manager 2 

Provide support as Second line Service Desk. Knowledge of Network administration 

Knowledge of programming network devices 

Knowledge in DATA Communication (IP) 






53 COMMCEN-Data Network Engineer 2 

54 COMMCEN-Data Software Developper 2 


requirements; 

Support all WAN services under Combranch 

authority; 



requirements; 

Develop, install & maintain Software Applications 







Knowledge of Network administration 








Knowledge of Common programming languages & 

webdesign 


55 COMMCEN-COMCEN Communication Technician 7 

56 COMMCEN-COMCEN Communication Service Desk Operator 7 

Operate and maintain all NGCS and NON-NGCS 

systems installed in NATO HQ (24/7); 

Deliver service desk services and first line support 

for all communication systems under Combranch 

authority; 

Supervise, monitor and troubleshoot on all NGCS 

and NON NGCS transmission trunks and/or 

circuits; 

Install,configurate and program all NGCS Crypto 

Equipment including Key changes. 

Operate NATO HQ's Military Message Handling 

System and distribution on NON-NGCS in the HQ 

(24/7); 



authority; 

Operate the NATO HQ private Switchboard 

outside normal business hours (24/7); 

Deliver transport services within the Combranch 

outside business hours. 


and VOIP) 


and IP) 



Knowledge of formal Msg handling and distribution 








57 COMMCEN-COMCEN COMCEN Duty Communication Officer 7 

58 COMMCEN-COMCEN Dept Head COMCEN 1 

59 COMMCEN-COMCEN Head COMCEN 1 

60 COMMCEN-PABX PABX Operator Assistant 2 

Supervises, operates and support all 

Communication Center activities 



authority, including maintaining an incident 

reporting database (24/7); 

Maintain the 24/7 facilities in coordination with BE 

Administration section outside business hours 

Participate in managing daily operations of the 

Comcentre, including PABX and Service Desk; 

Support quality assurance of all Comcentre 

services and take the appropiate actions if 

required; 

Support the daily people management in the 

Comcentre; 

Support the planning for training activities to bring 

and keep all Comcentre staff at the required 

quality level; 

Participate in overviewing issue and incident 

reporting and initiate problem requests when 

appropriate 

Manage daily operations of the Comcentre, 

including PABX and Service Desk 

Guarantee the quality assurance of all Comcentre 


required; 

Take care of daily people management in the 

Comcentre; 

Plan training activities to bring and keep all 

Comcentre staff at the required quality level; 

Overview issue and incident reporting and initiate 

problem requests when appropriate. 

Operates the NATO Telephone Switchboard 

during business hours 

Knowledge of ACP 127 





Leadership capacities 

Administration processes 



Knowledge of SLA management 












61 COMMCEN-PABX PABX Operator 2 









Maintain all contacts with the business units on 

communication service delivery, including user 

requirements gathering for new systems and 

system modifications. 

Administrate SLA management between the 

Combranch and the business units or other 

62 

COMMCEN- Comms 

service providers. 

Business Demand and Quality Assurance 3 

Supporting Services 

Coordination and development of test procedures 

in support of system acceptance and/or 

accreditation. 

Deliver administrative support for standardization 

of internal processes. 



63 

64 

65 







Communication Security Administrator 1 

Crypto Custodian 2 

Logistic, Contracting and Infra Administrator 2 

Sub-total COMMCEN 54 

66 PASP-ACCS Sr Programmer/Analyst 1 

67 PASP-ACCS Programmer/Analyst 2 

Drafts and evaluates all security documents 

related to systems under Combranch Authority; 

Deliver support in security acreditation testing 

procedures. 

Manage and control all NATO HQ CCI - Mat 

(including Key-distribution and destruction) 

Administrate security clearances for Combranch 

staff; 

Controls all assigned subaccounts 

Deliver Logistic Support for NATO HQ's NGCS: 

Control and inventory of all NGCS material, 

including administation, and maintaining records 

on all transactions including repair, calibration and 

inventory; 

Deliver Logistic Support to NATO HQ's NON- 

NGCS: Control and inventory of all NON-NGCS 

material, including administration and maintaining 

records on all transactions including repair and 

inventory; 

Budget Planning: Participate in the budget 

planning process by administrating the different 

budget lines allocated to the Combranch; 

Budget Execution: Participate in the procurement 

process by prospecting and administation of 

procurement processes; 

Administrate and monitor all NON-NGCS 

maintenance contacts; 

Administer and request maintenance works on 

space allocated to the Combranch including office 

furniture 

PASP 

Senior programmer & system analyst, DBA, 

network administrator, security officer, application 

support, meeting support for Data Management 

Experts Group 

Programmer/Analyst, deputise the roles of the 

above, application support, meeting support for 

Data Management Experts Group. 

Knowledge of business requirement gathering processes 

Knowledge of Program Management Methodologies 








Budgetary and costing model processes 


SME on treaty & arms control. Professional database 

administration, network administration, system 

administration. ITIL, PRINCE2 (scheduled) 



administration. 






68 PASP-ACCS Junior engineer 1 

Sub-total PASP 4 



Taking back-ups, staging of equipment meeting 

support for Data Management Experts Group. 

Professional level system development, professional level 

hardware & OS software, system administration. 








Part I - Schedule of Supplies and Services 


AGENCY 




(NNHQ - ANWI) 

BOOK II - PART I 

SCHEDULE OF SUPPLIES AND SERVICES 

VERSION 03 



Book II - Cover - Page I-1 of 40





QTY / Man- 

Days 

1 Project Management 

1.1 Project Management Documentation, containing 4.3; Annex K Appendix 1 

1.1.1 Project Status Report (PSR) NCIA (BEL) EDC+4 weeks 4.5; Annex K Appendix 15 15 

1.1.2 Project Management Plan (PMP) NCIA (BEL) EDC+2 weeks 4.3; Annex K Appendix 3 1 

1.1.3 Project Implementation Plan (PIP) EDC+2 weeks 4.3; Annex K Appendix 4 1 

1.1.3.1 Work Breakdown Structure (WBS) NCIA (BEL) EDC+2 weeks 4.3; Annex K Appendix 4 1 

1.1.3.2 Project Schedule NCIA (BEL) EDC+2 weeks 4.3; Annex K Appendix 4 1 

1.1.4 Change Management Plan NCIA (BEL) EDC+2 weeks 4.4.2 1 

1.1.5 Risk Management Plan (RMP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 5 1 

1.1.6 Quality Assurance Plan (QAP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 6 1 

1.1.7 Test and Acceptance Plan (TAP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 8 

1.1.8 Configuration Management Plan (CMP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 7 1 

1.1.9 Migration Plan (MP) NCIA (BEL) 30-Sep-14 4.3; Annex K Appendix 16 1 

1.1.10 Security Accreditation Documentation 

1.1.10.1 Security Risk Assessment NCIA (BEL) EDC+8 weeks 6.6.1; Annex K Appendix 11 1 

1.1.10.2 System Security Requirement Statement input NCIA (BEL) EDC+8 weeks 6.6.2; Annex K Appendix 13 1 

1.1.10.3 System Interconnection Security Requirement Statement NCIA (BEL) EDC+8 weeks 6.6.2; Annex K Appendix 13 1 

1.1.10.4 Security Test & Evaluation NCIA (BEL) EDC+8 weeks 6.2; Annex K Appendix 12 1 

1.1.11 Logistic Support Plan (LSP) NCIA (BEL) EDC+4 weeks 4.3; Annex K Appendix 9 1 

Unit Price 

Total Price 

Final 

Total Price 

Remarks 

1.1.12 

NATO Material Data Sheet 

NCIA (BEL) 

01-Sep-14 

6.10.2.2; Annex K Appendix 10 1 

1.2 Project Progress Review Meeting (PPRM) NCIA (BEL) EDC+2 weeks 4.5; Annex K Appendix 14 15+ 

2 ANWI Service and System Design 

2.1 Preliminary Design Review Meeting NCIA (NLD) EDC+4 weeks 5.2 1 

2.2 Design Document (4 Stages) 

2.2.1 CDGW & Infrastructure & IA NCIA (BEL) EDC+8 weeks 5.3; Annex K Appendix 2 1 

2.2.2 Service Management and Control (SMC) NCIA (BEL) EDC+16 weeks 5.3; Annex K Appendix 2 1 

2.2.3 UCC Services and Client provisioning NCIA (BEL) EDC+24 weeks 5.3; Annex K Appendix 2 1 

2.2.4 GSM & Secure Communications NCIA (BEL) EDC+32 weeks 5.3; Annex K Appendix 2 1 

2.3 Critical Design Review Briefings NCIA (NLD) 5.6 





2.4 Critical Design Review Feedback Meetings 





2.5 Acceptance of Design Document 

1st PPRM is Kickoff 

Meeting 

ITS included in CLIN 

13.1 

2.5.1 CDGW & Infrastructure & IA - Design Document Acceptance NCIA (BEL) EDC+14 weeks 5.8 1 

2.5.2 

2.5.3 

Service Management and Control (SMC) - Design Document 

Acceptance 

UCC Services and Client provisioning - Design Document 

Acceptance 



2.5.4 GSM & Secure Communications - Design Document Acceptance NCIA (BEL) EDC+38 weeks 5.8 1 

3 Site Survey 


Book II - SSS - Page I-2 of 40





QTY / Man- 

Days 

3.1 Site survey workbook NCIA (BEL) EDC+52 weeks 6.5.3 1 

3.2 Conduct Site Survey NNHQ EDC+56 weeks 3.10.2; 6.5.3 1 

3.3 Site survey report NCIA (BEL) EDC+58 weeks 6.5.3 1 

4 Testing 

4.1 Test Status Meeting NCIA (BEL) 30-Apr-16 6.7 1 

4.2 Proof of Concept Test (PCT) 

4.2.1 PCT - SMC ITS Site EDC+30 weeks 6.8.3; Annex E Appendix 1 1 

4.2.2 PCT - CDM ITS Site EDC+24 weeks 6.8.3; 14.2.1 1 

4.2.3 PCT - UCC ITS Site EDC+38 weeks 6.8.3; Annex G Appendix 1 1 

4.2.4 PCT - Client Provisioning ITS Site EDC+35 weeks 6.8.3; Annex H Appendix 2 1 

4.3 Capability Acceptance Test 6.8.2 

4.3.1 Processing Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 2 1 

4.3.2 Storage Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 3 1 

4.3.3 Printing and Scanning Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 4 1 

4.3.4 Network Infrastucture Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 5 1 

4.3.5 LAN Service NNHQ Campus 30-Jun-15 6.8.2; Annex F Appendix 6 1 

4.3.6 Cross Domain Service NNHQ Campus 30-Jun-15 6.8.2; 6.13; 14.2.1 1 

4.3.7 Voice Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 2 1 

4.3.8 VoiceMail Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 3 1 

4.3.9 VTC Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 4 1 

4.3.10 Email Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 5 1 

4.3.11 Unified Messaging Service Commponent NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 6 1 

4.3.12 FAX Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 7 1 

4.3.13 Instant Messaging/Chat Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 8 1 

4.3.14 Presence Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 9 1 

4.3.15 Directory Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 10 1 

4.3.16 Collaboration Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 11 1 

4.3.17 Mobility Service Component NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 12 1 

4.3.18 UCC Client NNHQ Campus 30-Jun-15 6.8.2; Annex G Appendix 1 1 

4.3.19 Software Provisioning NNHQ Campus 30-Jun-15 6.8.2; Annex H Appendix 2 1 

4.3.20 Client Devices NNHQ Campus 30-Jun-15 6.8.2; Annex H Appendix 3 1 

4.3.21 GSM Blocking NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 3 1 

4.3.22 Wireless Blocking NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 4 1 

4.3.23 Site Security Comms NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 5 1 

4.3.24 GSM Continuity Services NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 2 1 

4.3.25 IPTV services NNHQ Campus 30-Jun-15 6.8.2; Annex I Appendix 6 1 

4.4 Service Certification Test 6.8.4 

4.4.1 Infrastructure Services NNHQ 30-Jun-15 6.8.4; Annex F Appendix 1 1 

4.4.2 UCC Services NNHQ 30-Jun-15 6.8.4; Annex G Appendix 1 1 

4.4.3 Client Provisioning Service NNHQ 30-Jun-15 6.8.4; Annex H Appendix 1 1 

4.4.4 Supplementary Services NNHQ 

6.8.4; Annex I Appendix 1, 

30-Jun-15 Appendix 2, Appendix 6 

1 

4.4.5 Service Management and Control NNHQ 30-Jun-15 6.8.4; Annex E Appendix 1 1 

4.5 System Activation Test NNHQ 31-Oct-15 6.8.5 1 

4.6 Final Site Test NNHQ 30-Apr-16 6.8.6 1 

4.7 Security Implementation Verification Procedures NNHQ 30-Apr-15 6.8.7, Annex K Appendix 12 1 

4.8 Requirements Traceability Matrix NCIA (BEL) EDC+ 4 weeks 6.8.8 1 

4.9 Test reports NCIA (BEL) 30-Jun-16 3.10.7; Annex K Appendix 8 1 

5 ANWI Implementation and Transition 

5.1 ANWI Installation 

5.1.1 Server rooms NNHQ 31-Mar-15 6.10.2; 6.10.3; 6.10.4 1 

Unit Price 

Total Price 

Final 

Total Price 

Remarks 







QTY / Man- 

Days 

5.1.2 User Area NNHQ 30-Apr-16 6.10.2; 6.10.3; 6.10.4 1 

5.2 Service Activation NNHQ 30-Sep-15 6.10.6 1 

5.3 Service Activation Test NNHQ 31-Oct-15 6.10.7 1 

Unit Price 

Total Price 

5.4 Physical Configuration Audit 

NNHQ 

30-Sep-15 

6.10.8 1 

5.5 Initial Operating Capability NNHQ 31-Oct-15 6.13; 6,14 1 

5.6 Support from IOC to FOC NNHQ 30-Apr-16 6.14 1 

5.7 Migration to ANWI Environment NNHQ 30-Apr-16 6.10.10 1 

5.8 Support during migration NNHQ 30-Apr-16 6.10.12 1 

5.9 Final Operating Capability NNHQ 30-Apr-16 6.15; 6.16 1 

5.10 Support from FOC to FSA NNHQ 30-Oct-16 6.16 1 

5.11 Final System Acceptance NNHQ 30-Oct-16 6.17 1 

5.12 ANWI Knowledge base NNHQ 30-Jun-16 6.12 1 

5.13 Client Environment Training NNHQ 30-Apr-16 6.10.9 1 

6 ANWI Service and System Operations Processes 

6.1 ANWI Operational Support Plan NNHQ 31-Mar-15 7.4.1 1 

6.2 Training Needs Analysis for NONO services and users NCIA (BEL) 31-Mar-15 6.10.9.2 1 

6.3 ANWI Operations Event Management NNHQ 31-Mar-15 7.3.5; Annex E Appendix 1 1 

6.4 ANWI Operations Incident Management & Troubleshooting NNHQ 31-Mar-15 7.3.1; Annex E Appendix 1 1 

6.5 ANWI Request for Service NNHQ 31-Mar-15 7.3.3; Annex E Appendix 1 1 

6.6 ANWI Problem Management NNHQ 31-Mar-15 7.3.2; Annex E Appendix 1 1 

6.7 ANWI Access Management NNHQ 31-Mar-15 7.3.4; Annex E Appendix 1 1 

6.8 ANWI Monitoring NNHQ 31-Mar-15 7.4.3; Annex E Appendix 1 1 

6.9 Operational Procedures/Operating Instructions NCIA (BEL) 31-Mar-15 7.4.2; Annex E Appendix 1 1 

7 ANWI Service Improvement 

7.1 Identification of CSF NCIA (BEL) 30-Apr-15 8.5; Annex E Appendix 1 1 

7.2 Identification of KPIs for ANWI Services NCIA (BEL) 30-Apr-15 8.5; Annex E Appendix 1 1 

7.3 Service Level Agreement Reporting NCIA (BEL) 30-Apr-15 8.6.7.1; Annex E Appendix 1 1 

7.4 Improvement Recommendations change proposal NNHQ 31-Oct-16 8.6.7.2; Annex E Appendix 1 1 

7.5 Implement the Improvements NNHQ 31-Oct-16 8.6.8; Annex E Appendix 1 1 

8 Infrastructure Services Hardware and Software 

8.1 Processing Service Equipment 


8.1.1.1 Processing Hardware (Base Contract) including 3 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 


8.1.2.1 Processing Software Procurement (Base Contract) including 1 year 

NNHQ 



31-Mar-15 

1 n.a - 

8.2 Storage Services Equipment 


8.2.1.1 Storage Hardware (Base Contract) including 3 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 


8.2.2.1 Storage Software (Base Contract) including 1 year warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 

8.3 Print-Scan Services 

8.3.1 

Contractor Owned / Contractor operated Print/Scan Service for Large 

MFP device 

NNHQ 01-Dec-15 Annex F Appendix 4 

8.3.2 CoCo Print/Scan Service - Price per page B/W NNHQ 01-Dec-15 Annex F Appendix 4 

Final 

Total Price 

Remarks 

Inclucing Batiment Z and 

Remote sites 

187 - - Yearly service Cost 



7000000 - - 

pages 







QTY / Man- 

Days 

Unit Price 

Total Price 

8.3.3 CoCo Print/Scan Service - Price per page Colour NNHQ 01-Dec-15 Annex F Appendix 4 

3000000 - - 

8.4 Network Infrastructure Services 

8.4.1 Network Infrastructure Services Software - including 1 year warranty 

NNHQ 


and support 

31-Mar-15 

1 n.a - 

8.5 Wired Network Component Equipment 

8.5.1 Access Switches FO - including 3 year Warranty and support NNHQ 01-Dec-15 Annex F Appendix 6 1 n.a. - 

8.5.2 Access Switches RJ45 PoE - including 3 year Warranty and support 

NNHQ 


01-Dec-15 

1 n.a. - 

8.5.3 Core Switches - including 3 year Warranty and support 

NNHQ 


31-Mar-15 

1 n.a. - 

8.5.4 Server Switches - including 3 year Warranty and support NNHQ 31-Mar-15 Annex F Appendix 6 1 n.a. - 

8.5.5 Wired-Network-Conference Centre - including 3 year Warranty and 

NNHQ 


support 

01-Dec-15 

1 n.a. - 

8.6 Wireless Network Component Equipment 

8.6.1 WLAN - including 3 year Warranty and support NNHQ 01-Dec-15 Annex F Appendix 6 1 n.a. - 

8.7 Cross-Domain Module Component Equipment 

8.7.1 NS-NGCS-HW - including 3 year Warranty and support NNHQ 31-Mar-15 Annex E Appendix 2 1 n.a. - 

8.7.2 NS-NGCS-SW - including 1 year Warranty and support NNHQ 31-Mar-15 Annex E Appendix 2 1 n.a. - 

8.7.3 Business-NGCS/Public -HW - including 3 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a. - 

8.7.4 Business-NGCS/Public -SW - including 1 year Warranty and support 

NNHQ 


31-Mar-15 

1 n.a. - 

8.7.5 Public - Internet Access HW - including 3 year Warranty and support 

NNHQ 


31-Mar-15 

1 n.a. - 

8.7.6 Public - Internet Access SW- including 1 year Warranty and support 

NNHQ 


31-Mar-15 

1 n.a. - 

8.7.7 NS-EAPC-HW - including 3 year Warranty and support NNHQ 31-Mar-15 Annex E Appendix 2 1 n.a. - 

8.7.8 NS-EAPC-SW - including 1 year Warranty and support NNHQ 31-Mar-15 Annex E Appendix 2 1 n.a. - 

8.7.9 NS-Business-Info-Sharing-HW- including 3 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a. - 

8.7.10 NS-Business-Info-Sharing-SW- including 1 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a. - 

8.7.11 CIS Management Info-Sharing HW- including 3 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a. - 

8.7.12 CIS Management Info-Sharing SW- including 1 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a. - 

9 UCC Services 

9.1 Voice & VioceMail Component Equipment 

9.1.1 Voice & Voicemail Software - including 1 year Warranty and 

support 

NNHQ 

Annex G 


31-Mar-15 

9.2 Email Service Component Equipment 

9.2.1 E-mail service software - including 1 year Warranty and support NNHQ 31-Mar-15 Annex G Appendix 5 1 n.a. - 

9.3 FAX Service Component Equipment 

9.3.1 Fax service software - including 1 year Warranty and support NNHQ 31-Mar-15 Annex G Appendix 7 1 n.a. - 

9.4 IM/Chat Service Component Equipment 

9.4.1 IM/Chat service software - including 1 year Warranty and supportt NNHQ 31-Mar-15 Annex G Appendix 8 1 n.a. - 

9.5 Presence Service Component Equipment 

9.5.1 Presence service software - including 1 year Warranty and support NNHQ 31-Mar-15 Annex G Appendix 9 1 n.a. - 

9.6 UCC Directory Service Component Equipment 

Final 

Total Price 

Remarks 



pages 







9.6.1 UCC Directory service software - including 1 year Warranty and 

support 

9.7 Collaboration Service Component Equipment 

9.7.1 Collaboration service software - including 1 year Warranty and 

support 

9.8 Unified Messaging and Mobility Service Component Equipment 

NNHQ 

NNHQ 

31-Mar-15 

31-Mar-15 



QTY / Man- 

Days 

Unit Price 

Total Price 

1 n.a. - 

1 n.a. - 

Final 

Total Price 

Remarks 

9.8.1 UM & Mobility service software - including 1 year Warranty and 

Annex G 

NNHQ 

support 

31-Mar-15 


10 SMC Components 

10.1 SMC - Service Design Software - including 1 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 

10.2 SMC - Service Transition Software - including 1 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 

10.3 SMC - Service Operations Software - including 1 year Warranty and 

NNHQ 


support 

31-Mar-15 

1 n.a - 

10.4 SMC - Service Improvement Software - including 1 year Warranty 

NNHQ 


and support 

31-Mar-15 

1 n.a - 

11 Client Provisioning Hardware and Software 

11.1 Hardware 

11.1.1 Standard Desktop Client - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 1981 - - 


162 

NNHQ 


support 

01-Dec-15 

- - 

11.1.3 Network Agnostic Desktop Client - including 3 year Warranty and 

284 

NNHQ 


support 

01-Dec-15 

- - 

11.1.4 Mobile Client - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 1600 - - 

11.1.5 PDA/SmartPhone - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 573 - - 

11.1.6 IP Phone - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 493 - - 

11.1.7 IP Phone Secretariat - including 3 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 3 246 - - 

11.1.8 ANWI Travel Kit Client Hardware incl 3 year warranty and support NNHQ 01-Dec-15 Annex M 10 - - 

11.1.9 ANWI Travel Kit Back-end Hardware incl 3 year warranty and 

1 

NNHQ 

support 

01-Dec-15 

Annex M 

- - 

11.2 Software 

11.2.1 Software - Standard Client - including 1 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 2 1981 - - 

11.2.2 Software - High Performance Client - including 1 year Warranty and 

NNHQ 


support 

01-Dec-15 

162 - - 

11.2.3 Software - Network Agnostic clients - including 1 year Warranty and 

NNHQ 


support 

01-Dec-15 

284 - - 

11.2.4 Software - Mobile Client - including 1 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 2 1600 - - 

11.2.5 Software - PDA/SmartPhone - including 1 year Warranty and 

NNHQ 


support 

01-Dec-15 

573 - - 

11.2.6 Software - IP Phone - including 1 year Warranty and support NNHQ 01-Dec-15 Annex H Appendix 2 493 - - 

11.2.7 Software - IP Phone Secretariat - including 1 year Warranty and 

246 

NNHQ 


support 

01-Dec-15 

- - 

11.2.8 UCC Client Software - including 1 year Warranty and support NNHQ 01-Dec-15 Annex G 1 - - 

11.2.9 IPTV Client Software - including 1 year Warranty and support NNHQ 01-Dec-15 Annex I Appendix 6 1 - - 


1 

NNHQ 


and support 

01-Dec-15 

- - 

11.2.11 ANWI Travel Kit Client Software incl 1 year warranty and support NNHQ 01-Dec-15 Annex M 10 - - 

12 Supplementary Services Hardware and Software 

12.1 GSM Communications 







QTY / Man- 

Final 


Days 

Total Price 

Remarks 

12.1.1 GSM Coverage NNHQ Campus 01-Dec-15 Annex I Appendix 2 1 

12.1.2 GSM Blocking - including 3 year Warranty and support 

4 

NNHQ 


01-Dec-15 

- - 

12.1.3 Wireless Blocking - including 3 year Warranty and support NNHQ 01-Dec-15 Annex I Appendix 4 4 - - 

12.2 Security Communications 

12.2.1 Tetra secure communication coverage and penetration survey + 

1 

NNHQ 


Report 

31-Mar-15 

12.2.2 Tetra Secure Communications Antenna and Base Station relocation NNHQ 31-Mar-15 Annex I Appendix 5 1 

12.3 IPTV 

12.3.1 CoCo IPTV Service with Basic 30 Channels subscription (max 300) NNHQ 01-Dec-15 Annex I Appendix 6 1 Service cost year 1 

12.3.2 IPTV endpoint - including 3 year warranty NNHQ 01-Dec-15 Annex I Appendix 6 425 - - 

13 Integration and Testing Service (ITS) 

13.1 ITS Design NCIA (NLD) EDC+8 weeks Annex K Appendix 1 1 

13.2 ITS Hardware (including 3 year warranty and support) ITS Site 30-Oct-13 Annex E-F-G-H-I-J 1 n.a. - 

13.3 ITS Software (including 1 year warranty and support) ITS Site 30-Oct-13 Annex E-F-G-H-I-J 1 n.a. - 

13.4 Installation, Operation and Maintenance 

13.4.1 ITS Installation ITS Site 30-Oct-13 Annex J 1 

13.4.2 ITS Sustainment and Test Support (manpower) ITS Site 31-Dec-15 Annex J 1 n.a. - 

13.4.3 Documentation, initial spares ITS Site 30-Oct-13 Annex J 1 

13.5 ITS Acceptance ITS Site 30-Oct-13 Annex J 1 

14 Nations and Partners 

14.1 Nations - RESERVED NNHQ 31-Dec-15 Annex L n.a. n.a. n.a. 

14.2 Partners - RESERVED NNHQ 31-Dec-15 Annex L n.a. n.a. n.a. 

15 Remote Sites 


Annex M 

and Software (including 1 year warranty and support) Residence of SG 31-Dec-15 

1 n.a. - 


Annex M 

and Software (including 1 year warranty and support) New-York 31-Dec-15 

1 n.a. - 


Annex M 

and Software (including 1 year warranty and support) Kabul 31-Dec-15 

1 n.a. - 


Annex M 

and Software (including 1 year warranty and support) Moscow 31-Dec-15 

1 n.a. - 


Annex M 

and Software (including 1 year warranty and support) Kiev 31-Dec-15 

1 n.a. - 

Evaluated Options 

16 Standing Ordering Agreement - SOA 

16.1 Processing Hardware(Standing Ordering Agreement) Including 3 

NNHQ 



31-Mar-15 


16.2 Processing Software (Standing Ordering Agreement) Including 1 

NNHQ 



31-Mar-15 


16.3 Storage Hardware (Standing Ordering Agreement) including 3 year 

NNHQ 



31-Mar-15 


16.4 Storage Software (Standing Ordering Agreement) including 1 year 

NNHQ 



31-Mar-15 


16.5 Networking Hardware(Standing Ordering Agreement) Including 3 

NNHQ 



31-Mar-15 


17 Hardware and Software LifeCycle Support and Warranty 

17.1 Hardware Support and Warranty - Year 4 and 5 

17.1.1 Processing Hardware (Base Contract) 

NNHQ 









17.1.2 Storage Hardware (Base Contract) 


17.1.3 Access Switches FO 


17.1.4 Access Switches RJ45 PoE 


17.1.5 Core Switches 


17.1.6 Server Switches 


17.1.7 Wired-Network-Conference Centre 


17.1.8 WLAN 


17.1.9 NS-NGCS-HW 


17.1.10 Business-NGCS/Public -HW 


17.1.11 Public - Internet Access HW 


17.1.12 NS-EAPC-HW 


17.1.13 NS-Business-Info-Sharing-HW 


17.1.14 CIS Management Info-Sharing HW 






17.1.17 Network Agnostic Desktop Client 










17.1.22 GSM Blocking 


17.1.23 Wireless Blocking 




17.1.25 ITS Hardware 


17.1.26 Remotes Sites - Hardware 


NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

QTY / Man- 

Days 

Unit Price 

Total Price 


























Final 

Total Price 

Remarks 







17.1.27 Processing Hardware(Standing Ordering Agreement) year 4 - 5 


17.1.28 Storage Hardware (Standing Ordering Agreement) year 4 - 5 


17.1.29 Networking Hardware(Standing Ordering Agreement) year 4 - 5 


17.1.30 ANWI Travel Kit Client Hardware 


17.1.31 ANWI Travel Kit Back-end Hardware 


17.2 Software Support and Warranty - Year 2 to 5 

17.2.1 Processing Software Procurement (Base Contract) 


17.2.2 Storage Software (Base Contract) 


17.2.3 Network Infrastructure Services Software 


17.2.4 NS-NGCS-SW 


17.2.5 Business-NGCS/Public -SW 


17.2.6 Public - Internet Access SW 


17.2.7 NS-EAPC-SW 


17.2.8 NS-Business-Info-Sharing-SW 


17.2.9 CIS Management Info-Sharing SW 


17.2.10 Voice & Voicemail Software 


17.2.11 E-mail service software 


17.2.12 Fax service software 


17.2.13 IM/Chat service software 


17.2.14 Presence service software 


17.2.15 UCC Directory service software 


17.2.16 Collaboration service software 


17.2.17 UM & Mobility service software 


17.2.18 Software - Standard Client 


17.2.19 Software - High Performance Client 


17.2.20 Software - Network Agnostic clients 


NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

NNHQ 

QTY / Man- 

Days 

Unit Price 

Total Price 



























Book II - SSS - Page I-9 of 40 

Final 

Total Price 

Remarks





QTY / Man- 

Days 


17.2.21 Software - Mobile Client 

NNHQ 



17.2.22 Software - PDA/SmartPhone 

NNHQ 



17.2.23 Software - IP Phone 

NNHQ 



17.2.24 Software - IP Phone Secretarial 

NNHQ 




NNHQ 



17.2.26 IPTV Client Software 

NNHQ 




NNHQ 



17.2.28 ITS Software 

NNHQ 



17.2.29 Remotes Sites - Software 

NNHQ 



17.2.30 Processing Software (Standing Ordering Agreement) year 2-5 

NNHQ 



17.2.31 Storage Software (Standing Ordering Agreement) year 2-5 warranty 

NNHQ 

and support 


17.2.32 ANWI Travel Kit Client Software 

NNHQ 



17.2.33 SMC - Service Design Software 

NNHQ 



17.2.34 SMC - Service Transition Software 

NNHQ 



17.2.35 SMC - Service Operations Software 

NNHQ 



17.2.36 SMC - Service Improvement Software 

NNHQ 



18 Service Life-Cycle Support - Operation (5 year Lifecycle) 





















Final 

Total Price 

Remarks





QTY / Man- 

Days 


































19 CoCo Services Year 2 - 5 


Final 

Total Price 

Remarks 



- - 






- - 






- - 










QTY / Man- 

Days 

Unit Price 

Total Price 

Final 

Total Price 

Remarks 



- - 




19.5.1 CoCo IPTV Service with Basic 30 Channels subscription (max 300) NNHQ 01-Dec-16 Annex I Appendix 6 1 Service cost/year 







GRAND TOTAL FIRM FIXED PRICE CLINS 1 - 19 (state currency): 

20 Optional Hardware and Software (non Evaluated) 

20.1 Printing 

20.1.1 CoCo Personal/Workgroup Printer (B/W and Colour) NNHQ n.a. Annex F Appendix 4 1 NP NP NP Sheet ANWI IDIQ 

20.2 Switching 

20.2.1 24 Port Access Switch with uplinks- FO - including 3 year Warranty 

NNHQ 


and support 

n.a. 


20.2.2 24 Port Access Switch with uplinks- FO 

NNHQ 



20.2.3 48 Port Access Switch - RJ45 with uplinks - including 3 year 

NNHQ 



n.a. 


20.2.4 48 Port Access Switch - RJ45 with uplinks 

NNHQ 



20.2.5 WLAN Access Point - including 3 year Warranty and support NNHQ n.a. Annex F Appendix 6 1 NP NP NP Sheet ANWI IDIQ 

20.2.6 WLAN 

NNHQ 



20.3 Clients 

20.3.1 Standard Desktop Client - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 




NNHQ 

support 



NNHQ 



20.3.5 Mobile Client - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 



20.3.7 PDA/SmartPhone - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 



20.3.9 IP Phone - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 



20.3.11 IP Phone Secretariat - including 3 year Warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 


NNHQ 



20.3.13 IPTV endpoint - including 3 year warranty and support NNHQ n.a. Annex I Appendix 6 1 NP NP NP Sheet ANWI IDIQ 

- 







QTY / Man- 

Days 

Unit Price 

Total Price 

Final 

Total Price 


NNHQ 



20.3.15 2nd Monitor (21") - - including 3 year warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 

20.3.16 2nd Monitor (21") 

NNHQ 



20.3.17 Monitor Upgrade (24") 

NNHQ 



20.3.18 Monitor Upgrade (24") - including 3 year warranty and support NNHQ n.a. Annex K Appendix 9 1 NP NP NP Sheet ANWI IDIQ 

20.3.19 2nd Monitor (24") - including 3 year warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 

20.3.20 2nd Monitor (24") 


NNHQ 


20.3.21 Softphone Handset - including 3 year warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 

20.3.22 Softphone Handset 

NNHQ 



20.3.23 Client Software baseline - including 1 year warranty and support NNHQ n.a. Annex H Appendix 3 1 NP NP NP Sheet ANWI IDIQ 

20.3.24 Client Software baseline - year 2 - 5 Warranty and support NNHQ n.a. Annex K Appendix 9 1 NP NP NP Sheet ANWI IDIQ 

20.3.25 UCC Client Software - including 1 year Warranty and support NNHQ n.a. Annex G 1 NP NP NP Sheet ANWI IDIQ 



NNHQ 



NNHQ 


and support 

n.a. 



NNHQ 



20.4 Secure Site Communications - TETRA 

20.4.1 Handset NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.2 Vehicle-based NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.3 Office-based NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.4 Base Station NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.5 Repeater NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

20.4.6 Mast NNHQ n.a. Annex I Appendix 5 1 NP NP NP Sheet ANWI IDIQ 

21 System Administrator Training 

21.1 Network Service 

21.1.1 Storage (Capacity) Service NNHQ Campus 31-Mar-15 Annex F Appendix 3 1 incl. Training material 

21.1.2 Print/Scan Service NNHQ Campus 31-Mar-15 Annex F Appendix 4 1 incl. Training material 

21.1.3 Cross Domain Services NNHQ Campus 31-Mar-15 Annex E Appendix 2 1 incl. Training material 

21.2 Local Area Network (LAN) Services 

21.2.1 Switching Service NNHQ Campus 31-Mar-15 Annex F Appendix 6 1 incl. Training material 

21.2.2 Wireless Service NNHQ Campus 31-Mar-15 Annex F Appendix 6 1 incl. Training material 

21.2.3 Wireless Blocking Service NNHQ Campus 01-Dec-15 Annex I Appendix 3 1 incl. Training material 

21.2.4 GSM Blocking Service NNHQ Campus 01-Dec-15 Annex I Appendix 4 1 incl. Training material 

21.3 Unified Communications Capability Services 

21.3.1 Voice NNHQ Campus 01-Dec-15 Annex G Appendix 1 1 incl. Training material 

21.3.2 VoiceMail NNHQ Campus 01-Dec-15 Annex G Appendix 2 1 incl. Training material 

21.3.3 E-Mail NNHQ Campus 01-Dec-15 Annex G Appendix 5 1 incl. Training material 

21.3.4 Presence NNHQ Campus 01-Dec-15 Annex G Appendix 9 1 incl. Training material 

21.3.5 Instant Messaging NNHQ Campus 01-Dec-15 Annex G Appendix 8 1 incl. Training material 

21.3.6 Collaboration (Whiteboard) NNHQ Campus 01-Dec-15 Annex G Appendix 11 1 incl. Training material 

21.3.7 Video Tele-Conferencing (VTC) NNHQ Campus 01-Dec-15 Annex G Appendix 4 1 incl. Training material 

21.3.8 VMR NNHQ Campus 01-Dec-15 Annex G Appendix 4 1 incl. Training material 

21.4 Client Provisioning 

21.4.1 Client provisioning service NNHQ Campus 31-Dec-15 Annex H Appendix 3 1 incl. Training material 



Remarks





QTY / Man- 

Days 

Unit Price 

Total Price 

Final 

Total Price 

21.5 Supplementary Services 

21.5.1 GSM NNHQ Campus 31-Dec-15 Annex I Appendix 2 1 incl. Training material 

21.5.2 IPTV NNHQ Campus 31-Dec-15 Annex I Appendix 6 1 incl. Training material 

21.5.3 Security Communications (radio) NNHQ Campus 31-Dec-15 Annex I Appendix 5 1 incl. Training material 

Remarks 






TCO 

Acquisition (ca) Commissioning (cc) Operation (co) Support / Service Fees (cs) TOTAL 

TOTAL TCO - - - - - 

TCO = ca + cc + co + cs 

Cost Type Service Cost CLIN Summation 

Cost of Acquisition (CA) 

Cost of Commissioning (CC) 

Cost of Operation (CO) 

SMC - 10 

Processing - 8.1, 16.1, 16.2 

Storage - 8.2, 16.3, 16.4 

Networking - 8.5, 8.6, 16.5 

Cross-Domain gateways - 8.7 

Network Infrastructure Services - 8.4 

Clients & Client provisioning - 11 

UCC - 9 

Print/Scan Service n.a. n.a. 

Remote Sites - 15 

IPTV Service - 12.3.2 

ITS - 13.2, 13.3 

GSM & Blocking - 12.1.2, 12.1.3 

(Manpower and other costs related to design/install/commission 

Manpower, Software and tools & travel - 1, 2, 3, 4, 5, 6, 7, 12.2, 13(excl 13.2 & 13.3) 

(ManPower and Power Cost) 

SMC - 18.1.1, 18.1.2, 18.2.1, 18.2.2,18.3.1, 18.3.2, 18.4.1, 18.4.2, 18.5.1, 18.5.2 

Processing (including network Infrastructure 

and CDGW Services) - 18.1.3, 18.2.3, 18.3.3, 18.4.3, 18.5.3 + Power cost of Processing Sheet & CDGW Sheet 

Storage - 18.1.4, 18.2.4, 18.3.4, 18.4.4, 18.5.4 + Power cost of Storage Sheet 

Networking - 18.1.6, 18.2.6, 18.3.6, 18.4.6, 18.5.6 + Power cost of Networking Sheet 

Clients & Client provisioning (including 

Remote sites) - 18.1.8, 18.2.8, 18.3.8, 18.4.8, 18.5.8 + Power cost of Client Sheet 

UCC - 18.1.7, 18.2.7, 18.3.7, 18.4.7, 18.5.7 

Print/Scan Service - 18.1.5, 18.2.5, 18.3.5, 18.4.5, 18.5.5 + Power cost of Print-Scan Sheet 

IPTV Service - 18.1.9, 18.2.9, 18.3.9, 18.4.9, 18.5.9 + Power cost of IPTV Sheet 

Cost of Support - Service Fees (CS) 

(Support/Maintenance contracts) 

SMC - 17.2.33 - 36 

Processing - 17.1.1, 17.1.27, 17.2.1, 17.2.30 

Storage - 17.1.2, 17.1.28, 17.2.2, 17.2.31 

Networking - 17.1.3 - 8, 17.1.29 

Cross-Domain gateways - 17.1.9 - 14, 17.2.4 - 9 

Network Infrastructure Services - 17.2.3 

Clients & Client provisioning - 17.1.15 - 21, 17.1.26, 17.1.30 - 31, 17.2.18 - 27, 17.2.29, 17.2.32 

UCC - 17.2.10 - 17 

Print/Scan Service - 8.3, 19.1, 19.2, 19.3, 19.4 

IPTV Service - 12.3.1, 19.5, 19.6, 19.7, 19.8, 17.1.24 

ITS - 17.1.25, 17.2.28 

GSM - 12.1.1, 17.1.22 - 23 


Book II - TCO Calculation - Page I-15 of 40


Item Profile Profile Description Day Price Month Price Year price 

(Please list all types of manpower resources that are offered for the ANWI Project) 



1 Senior Project Manager 

2 Add Lines - Complete as needed 


Book II - Manpower Resources - Page I-16 of 40

Item Description Part Number Vendor SOW Reference 

1 Printing 

CoCo Personal/Workgroup Printer (B/W and Colour) - Yearly 

1.1 Service Cost 


2 Switching 

24 Port Access Switch with uplinks- FO - including 3 year 



24 Port Access Switch with uplinks- FO 


48 Port Access Switch - RJ45 with uplinks - including 3 year 



48 Port Access Switch - RJ45 with uplinks 


WLAN Access Point - including 3 year Warranty and support 


2.5 

WLAN 


3 Clients 

Standard Desktop Client - including 3 year Warranty and 


Standard Desktop Client 


High Performance Desktop Client - including 3 year 

3.3 Warranty and support Annex H Appendix 3 

High Performance Desktop Client 


3.5 Mobile Client - including 3 year Warranty and support Annex H Appendix 3 

Mobile Client 


3.7 PDA/SmartPhone - including 3 year Warranty and support Annex H Appendix 3 

PDA/SmartPhone 


3.9 IP Phone - including 3 year Warranty and support Annex H Appendix 3 

IP Phone 


4.1 IP Phone Secretariat - including 3 year Warranty and support Annex H Appendix 3 

IP Phone Secretariat 


4.3 IPTV endpoint - including 3 year warranty and support Annex I Appendix 6 

IPTV endpoint 


4.5 2nd Monitor (21") - - including 3 year warranty and support Annex H Appendix 3 



Monitor Upgrade (24") 

4.7 year 4 - 5 Warranty and support Annex H Appendix 3 

Monitor Upgrade (24") - including 3 year warranty and 

4.8 support Annex K Appendix 9 

4.9 2nd Monitor (24") - including 3 year warranty and support Annex H Appendix 3 



5.1 Softphone Handset - including 3 year warranty and support Annex H Appendix 3 

Softphone Handset 


Client Software baseline - including 1 year warranty and 


5.4 Client Software baseline - year 2 - 5 Warranty and support Annex K Appendix 9 

UCC Client Software - including 1 year Warranty and support 

Annex G 

5.5 

UCC Client Software 


Client Provisioning Software Solution - including 1 year 



Client Provisioning Software Solution 


4 Secure Site Communications - TETRA 

4.1 Handset Annex I Appendix 5 

4.2 Vehicle-based Annex I Appendix 5 

4.3 Office-based Annex I Appendix 5 

4.4 Base Station Annex I Appendix 5 

4.5 Repeater Annex I Appendix 5 

4.6 Mast Annex I Appendix 5 




Quantity - 1 Quantity - 1 > < 50 

Quantity - 50 > < 100 

Quantity - 50 > < 100 

Unit price 

Unit price 

Unit price 

Unit price 

Year 1 Year 2 Year 3 Year 4 Year 5 Year 1 Year 2 Year 3 Year 4 Year 5 Year 1 Year 2 Year 3 Year 4 Year 5 Year 1 Year 2 Year 3 Year 4 Year 5 


Book II - IDIQ Equipment - Page I-17 of 40

CLIN Description Resource type Company 

Instructions: 

Mandays/U 

nit 


Please list under each Top level CLIN all the resources required for ALL Sub-CLIN's 

Manpower resources listed here shall also be listed under the ANWI Manpower Resources sheet 

The bidder shall also indentify the company the resource is from. Sub-contractors shall be named. 

The bidder shall provide the manpower, Software & Tools and travel prices under the respective headers 

Day Price Total Unit price Total Nr Travels Travel Cost 

Manpower Software and tools Travel 

1 Project Management 0.00 0.00 0.00 



- - 


2 ANWI Service and System Design 0.00 0.00 0.00 



- - 


3 Site Survey 0.00 0.00 0.00 



- - 


4 Testing 0.00 0.00 0.00 



- - 


5 ANWI Implementation and Transition 0.00 0.00 0.00 



- - 


6 ANWI Service and System Operations Processes 0.00 0.00 0.00 



- - 


7 ANWI Service Improvement 0.00 0.00 0.00 



- - 


12.2 Security Communications 0.00 0.00 0.00 



- 


13 Integration and Testing 

Service (ITS) 

0.00 0.00 0.00 



- 


TOTAL 0.00 0.00 0.00 




Book II - Implementation - Page I-18 of 40




Ref CLIN Service - Manpower Resource Profile Year 1 Year 2 Year 3 Year 4 Year 5 

TOTAL (O&M) 

FTE Cost FTE Cost FTE Cost FTE Cost FTE Cost 

18.1.1 SMC Service - support 

ex. Service desk engineer - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.2 SMC Service - Transition and management 

ex. Service level manager - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.3 Processing Service (including Network infrastructure services & CDGW) 

ex. Server Administrators - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.4 Storage Service 

ex. Storage Administrators - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.6 LAN Service (wired and Wireless) 

ex. Network Administrators - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.8 Client Provisioning/Client Devices services (including Remote Sites) 



TOTAL - - - - - - - - - - - 

18.1.7 UCC service 

ex. UCC engineer - - - - - - 


TOTAL - - - - - - - - - - - 

18.1.5 Print/Scan Service 



TOTAL - - - - - - - - - - - 

18.1.9 IPTV Service 



TOTAL - - - - - - - - - - - 


Book II - Service Operations - Page I-19 of 40


SMC Partnumber Vendor SSS Ref Quantity 



TOTAL 


Units clients Requirement 


SMC - Service Design 10.1 - - - - - - 



PFE SW 



SMC - Service Transition 10.2 - - - - - - 



PFE SW 



SMC - Service Operations 10.3 - - - - - - 



PFE SW 



SMC - Service Improvement 10.4 - - - - - - 



PFE SW 



TOTAL n.a. - - - - - - - - 





Support - - - - - - 



TOTAL - - - - - - 


Book II - SMC - Page I-20 of 40







Total 

Units 


Cooling 

Nr of Servers 

(Max) 

Requirement 



Server Hardware 

Server Baseline Hardware (ANWI) 8.1.1.1 0 - - - - - - 

ANWI Physical Server 0 - - - - - - - - - - 

ANWI VM Host Server 0 - - - - - - - - - - 


Server SOA Hardware 16.1 0 - - - - - - 

ICTM Physical Server 0 0 - - - - - - - - - - 

ICTM VM Host Server 0 0 - - - - - - - - - - 


Server Baseline Software (ANWI) 8.1.2.1 - - - - - - 



PFE SW 



Server SOA Software 16.2 - - - - - - 



PFE SW 



TOTAL 0 0 - - - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 

Server per FTE 

Avg cost per server (year) 

#DIV/0! 

#DIV/0! 


Book II - Processing - Page I-21 of 40






Unit price Year 1 Year 2 Year 3 Year 4 Year 5 

TOTAL 

Cooling 

Requirement 

Units TB (KW/H per year) 


Storage Hardware 

Storage Baseline Hardware (ANWI) 8.2.1.1 - - - - - - 

SAN Infrastructure 0 n.a. - - - - - - - - - 



ANWI Tier 3 Storage 0 0 - - - - - - - - - 



Storage SOA Hardware 16.3 - - - - - - 

SAN Infrastructure - - - - - - - - - 






Storage Software 

Storage Baseline Software (ANWI) 8.2.2.1 - - - - - - 

xxxx 0 n.a. - - - - - - - - - 


Storage SOA Software 16.4 - - - - - - 

xxxx 0 n.a. - - - - - - - - - 


TOTAL 0 1956 - - - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 

Cost per TB - 


Book II - Storage - Page I-22 of 40





Combined Unit price Year 1 


TOTAL 

Power/ Cooling 

Units Ports Requirement 


HARDWARE (Baseline) 

Core Switches 8.5.3 - - - - - - - 

Core switches 0 0 - - - - - - - - - - 


Access Switches FO 8.5.1 - - - - - - - 

Access Switches FO 0 0 - - - - - - - - - - 


Access Switches PoE 8.5.2 - - - - - - - 

Access Switches PoE 0 0 - - - - - - - - 


Server Switches 8.5.4 - - - - - - - 



Confrence Switching 8.5.5 - - - - - - - 

Agnostic switches 0 0 - - - - - - - - - - 


WLAN Hardware 8.6.1 - - - - - - - 

WLAN Access Points 0 0 - - - - - - - - - - 

WLAN Controllers 0 0 - - - - - - - - - - 


HARDWARE (SOA) 16.5 - - - - - - 

Core Switches - - - - - - - 

Core switch components 0 0 - - - - - - - - - - 


Server Switches - - - - - - - 



TOTAL 0 0 - - - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 

Manpower cost - - - - - - 

TOTAL - - - - - - 

Description Year Month 

Cost Per port #DIV/0! #DIV/0! 


Book II - Networking - Page I-23 of 40








Cooling 

Requirement 



Cross-Domain HW 

CDGW 1 Hardware 8.7.1 0 - - - - - - 

Processing 



Storage 


Networking 


CDGW 2 Hardware 8.7.3 0 - - - - - - 

Processing 



Storage 


Networking 


CDGW 3 Hardware 8.7.5 0 - - - - - - 

Processing 



Storage 


Networking 


CDGW 4 Hardware 8.7.7 0 - - - - - - 

Processing 



Storage 


Networking 


CDGW 5 Hardware 8.7.9 0 - - - - - - 

Processing 



Storage 


Networking 


CDGW 6 Hardware 8.7.11 0 - - - - - - 

Processing 



Storage 


Networking 


Cross-Domain SW 

CDGW 1 8.7.2 - - - - - - 



PFE SW 

TOTAL 


Book II - CDGW - Page I-24 of 40








Cooling 

Requirement 





CDGW 2 8.7.4 - - - - - - 



PFE SW 



CDGW 3 8.7.6 - - - - - - 



PFE SW 



CDGW 4 8.7.8 - - - - - - 



PFE SW 



CDGW 5 8.7.10 - - - - - - 



PFE SW 



CDGW 6 8.7.12 - - - - - - 



PFE SW 



TOTAL - - - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 

TOTAL 


Book II - CDGW - Page I-25 of 40





TOTAL 

Requirement 



CLIENTS -HARDWARE 



TFT Monitor 0 - - - - - - - - - - 


Mouse 0 - - - - - - - - - - 



Desktop Client - High Perf 11.1.2 162 - - - - - - 


TFT Monitor 0 - - - - - - - - - - 


Mouse 0 - - - - - - - - - - 





TFT Monitor 0 - - - - - - - - - - 


Mouse 0 - - - - - - - - - - 



Mobile Client 11.1.4 1600 - - - - - - 

Mobile Client - Laptop 0 - - - - - - - - - - 

Mobile Client - Tablet 0 - - - - - - - - - - 

Docking solution 0 - - - - - - - - - - 

TFT Monitor 0 - - - - - - - - - - 


Mouse 0 - - - - - - - - - - 




Smartphone/PDA 0 - - - - - - - - - - 


UCC phone - Standard 11.1.6 493 - - - - - - 

UCC Phone 0 - - - - - - - - - - 


UCC phone - Secretarial 11.1.7 246 - - - - - - 

UCC secretatial phone 0 - - - - - - - - - - 


CLIENTS -SOFTWARE 

Client Provisioning 11.2.10 - - - - - - 

Client provisioning SW 0 n.a. - - - - - - - - - 


PFE SW 





PFE SW 


Desktop Client - High Performance 11.2.2 162 - - - - - - 


PFE SW 




PFE SW 


Mobile Client 11.2.4 1600 - - - - - - 





Book II - Clients - Page I-26 of 40





TOTAL 

Requirement 



PFE SW 




PFE SW 


IP Phone 11.2.6 493 - - - - - - 


IP Phone Secretarial 11.2.7 246 - - - - - - 


UCC Client Software 11.2.8 - - - - - - - 

UCC Softphone Client 0 n.a. - - - - - - - - - 


IPTV Client Software 11.2.9 - - - - - - - 


TOTAL 5339 - - - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 





Book II - Clients - Page I-27 of 40





TOTAL 


Units 



Infrastructure Services 8.4.1 - - - - - - 

NAC Software 0 0 n.a. - - - - - - - - - 


PFE SW 





TOTAL - - - - - - - - 



Support - - - - - - 



TOTAL - - - - - - 




TOTAL 


Units 



UCC Services 

Voice & Voicemail 9.1.1 - - - - - - 

xxxx 0 0 n.a. - - - - - - - - - 


PFE SW 



E-mail 9.2.1 - - - - - - 

E-mail software 0 0 n.a. - - - - - - - - - 


PFE SW 



Fax Service 9.3.1 - - - - - - 

Fax software 0 0 n.a. - - - - - - - - - 


PFE SW 


Add Lines - Complete as needed 0 - n.a. - - - - - - - - - 

IM/Chat Service 9.4.1 - - - - - - 

IM/Chat software 0 0 n.a. - - - - - - - - - 


PFE SW 



Presence Service 9.5.1 - - - - - - 



PFE SW 



UCC Directory Service 9.6.1 - - - - - - 



PFE SW 



Collaboration Service 9.7.1 - - - - - - 


Book II - Applications - Page I-28 of 40





TOTAL 


Units 



collaboration software 0 0 n.a. - - - - - - - - - 


PFE SW 



Unified Messaging and Mobility 

Service 9.8.1 - - - - - - 

UM software 0 0 n.a. - - - - - - - - - 


PFE SW 



TOTAL - - - - - - - - - - - 

Summary Table for UCC Service 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 




Book II - Applications - Page I-29 of 40





Unit price Year 1 Year 2 Year 3 Year 4 Year 5 Total 

Units 

n.a. 


Cooling 

Requirement 


Service Cost/ 


Service Cost/ 


Service Cost/ 

per Unit- 

Page 

Service Cost/ 


Service Cost/ per 

Unit- Page 

Lifecycle 

(5 year) 

Print/Scan Baseline 

Print/Scan service MFP printer 8.3.1 187 n.a. - - - - - 

CoCo Print Server - n.a. n.a. n.a. n.a. n.a. n.a n.a. 

CoCo MFP Colour printer - n.a. n.a. n.a. n.a. n.a. n.a n.a. 


- 

Pay-per-page - - - - - 

Price per page B/W 8.3.2 7,000,000.00 n.a. n.a. n.a. - - - - - - 

Price per page Colour 8.3.3 3,000,000.00 n.a. n.a. n.a. - - - - - - 

n.a. n.a. - - 

TOTAL 0 - - - - - - - 


Procurement n.a. n.a. n.a. n.a. n.a. - 

Usage (Pages) - - - - - - 


Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 


Book II - Print-Scan - Page I-30 of 40







Total 


Cooling 

Requirement 



IPTV Service 

IPTV Endpoints 12.3.2 - - - - - - - 

60" display screens with integrated 

IPTV media player 425 - - - - - - - - 


TOTAL - - - - - - - - - 



Support - - - - - - 


Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 




Total 


Cooling 

Requirement 

(KW/H per unit per 

Units year) 


GSM Service 

GSM Blocking 12.1.2 - - - - - - - 

GSM Blocking Equipment 1 - - - - - - - - 


WLan Blocking 12.1.3 - - - - - - - 

WLan Blocking Equipment 1 - - - - - - - - 


TOTAL - - - - - - - - - 



Support - - - - - - 

Service Fee - NP NP NP NP - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 


Book II - Other Systems - Page I-31 of 40







Total 


Cooling 

Requirement 



ITS Hardware 

Hardware 13.2 0 - - - - - - 

Servers - - - - - - - - - - - 

Storage - - - - - - - - - - - 

Networking (including ITS Cabling) - - - - - - - - - - - 

Cross-domain Components - - - - - - - - - - - 

Client Infrastructure - - - - - - - - - - - 

Print Scan - - - - - - - - - - - 

IPTV - - - - - - - - - - - 

Add Lines - Complete as needed - - - - - - - - - - - 


Software 13.3 - - - - - - 

Virtualisation Software - n.a. - - - - - - - - - 

Add Lines - Complete as needed n.a. - - - 

PFE SW 



TOTAL - - - - - - - - - 

ITS Test Support and sustainment 

Manpower 13.4.2 n.a. - - - - - 

System Engineer - n.a. - - - - - - - - - 


TOTAL - n.a. - - - - - - - 



Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 


Book II - ITS - Page I-32 of 40





Combined Power 

Year 1 


TOTAL 

Requirement 

Units (KW/H per year) Unit Price Procurement Support Support Support Support Support Procurement Support 

Remote Locations - Hardware - - 

Location 1 15.1 - - - - - - - - 



Location 2 15.2 - - - - - - - - 



Location 3 15.3 - - - - - - - - 



Location 4 15.4 - - - - - - - - 




Location 5 15.5 - - - - - - - - 




Travel Kits - Clients Hardware 11.1.8 - - - - - - - - 

NS mobile client 1 - - - - - - - - - - 

Small formfactor printer 1 - - - - - - - - - - 


Travel Kits - Back-end Equipment 11.1.9 - - - - - - - - 

VPN Concentrator 0 - - - - - - - - - - 

Switching 0 - - - - - - - - - - 


Remote Locations - Software - - 

Location 1 15.1 - - - - - - - - 


PFE SW 


Location 2 15.2 - - - - - - - - 


PFE SW 


Location 3 15.3 - - - - - - - - 


PFE SW 


Location 4 15.4 - - - - - - - - 


PFE SW 


Location 5 15.5 - - - - - - - - 


PFE SW 


Travel Kits - Clients Software 11.2.11 - - - - - - - - 


PFE SW 


TOTAL 77 - - - - - - - - - 


Book II - Remote Sites - Page I-33 of 40





Procurement - - - - - - 

Support - - - - - - 

Power (@0.1182€ KW/h) - - - - - - 


TOTAL - - - - - - 



Book II - Remote Sites - Page I-34 of 40



ICTM 

1 ICTM-Ops Manager 1 Manage ICTM-Ops ITIL, Senior ICT manager, PRINCE2 

2 ICTM-Ops Change Manager 1 Change Management process owner ITIL expert 

3 ICTM-Ops Configuration Manager 1 CM process owner ITIL expert 



4 ICTM-Ops-Systems Mngt Manager 1 Manage ICTM-Ops-Systems Management team Managerial level infosec knowledge 

5 ICTM-Ops-Systems Mngt Infosec Analyst 5 

Infosec operations, operate the ICT security 

systems, respond to Infosec incidents 

6 ICTM-Ops-Network Mngt Manager 1 Manage ICTM-Ops Network Management 

7 ICTM-Ops-Network Mngt Network Engineer 1 

Project related network engineering work. 3rd line 

network management support 

8 ICTM-Ops-Network Mngt Network Analysts 2 1st & second line network management support 

LRE CPE installation, 1st line support, modifying 

wiring, install new wiring & patch panels, mounting 

9 ICTM-Ops-Network Mngt Network Data Cabling Engineer 2 physical equipment 

1 Senior and 4 professional level Infosec product 

specialists. Operate and set up infosec systems. Detect 

security incidents. By analysing usage patterns. 



management, network management, voice, VOIP, WAN). 

PRINCE2, ITIL 



management, network management, voice). PRINCE2, 

ITIL. 

Professional level network engineering knowledge (LAN 


management, network management). ITIL 

Junior LAN engineer, Cabling techniologies (F.O., 

structured cabling, coax) including measurement (OTDR, 

UTP). Cabling management system. 

10 ICTM-Ops-Network Mngt Senior Voice Engineer 2 1st and 2nd line support, PABX system changes 

Senior level TDM-based PABX knowledge (Philips Sopho 


11 ICTM-Ops-Network Mngt junior Voice Engineer 2 1st line voice support, voice installations (IMAC) 

Manage & maintain conference room AV and 

ICTM-Ops-Mulimedia 

interpretation systems, supporting events on and 

12 Systems Mngt Multimedia Engineer 3 off site. 

Management and support on databases and 

Junior level TDM-based PABX knowledge (Philips Sopho 


Senior level AV technical knowledge. 

13 ICTM-Ops-Database Support Database Administrator 2 related infrastructure. 

Advanced DBA & system administrator, MS SQL, Oracle 

Manage the Service Center organisation, ITIL, Incident & problem management, professional ICT 

14 ICTM-Ops-Service Center Manager/Deputy Manager 2 commmunicate with end users 

management level 


15 Service Desk Team Leader 2 Trouble shooting Broad ICT knowledge 


16 Service Desk Senior Analyst 1 Trouble shooting Broad ICT knowledge 


17 Service Desk Analyst 2 Trouble shooting Broad ICT knowledge 


18 Service Desk Junior Analyst 3 Call intake, Resolve majority calls Broad ICT knowledge 



administration, Workstation manegment and Altiris knowledge, Deep Active Directory & Microsoft OS, 

19 Workst SW Mngt Team Leader 1 image development 


20 

21 


Workst SW Mngt Senior Analyst 2 


IMAC Team Leader 1 


administration, Workstation manegment and 

image development 

Workstation staging & repair, end user equipment 

deployment 

Altiris knowledge, Deep Active Directory & Microsoft OS, 


ICT hardware knowledge, client OS knowledge, Altiris 



Book II - Manpower (ICTM) - Page I-35 of 40




Workstation staging & repair, end user equipment ICT hardware knowledge, client OS knowledge, Altiris 

22 IMAC Analyst 7 deployment 


23 ICTM-Ops-Server Mngt Manager 1 

Manage the Server & Security systems team. 

Deputise for Head ICTM OPS. Role in projects 

related to servers & storage. 

ITIL, PRINCE2, ICT manager, senior system 

administrator, storage management, VM Ware 

virtualisation, multi-vendor servers management 



24 ICTM-Ops-Server Mngt Server Support Assistant 3 




Professional level system administrator, multi-vendor 

server management, VM Ware 


25 ICTM-Ops-Server Mngt Junior Server Support Assistant 2 



Junior system administrator, multi-vendor server 

management, VM Ware 

26 ICTM-Arch Mngt Infrastructure Architect 2 

Infrastructure & ICT security related architecture 

development 

NAF, ICT security architecture training, deep 

infrastructure & ICT security knowledge 

27 ICTM-Arch Mngt CAM Engineer 1 Design of server & storage solutions MCSE, senior level server & storage knowledge 

Sub-total ICTM 54 

COMMCEN 

47 COMMCEN-Video VTC-Technican 3 

48 COMMCEN-Video VTC-Operator 3 

49 COMMCEN-Video VTC-Planner 2 


requirements; 

Develop, install & maintain VTC solutions (NGCS 


Develop, install & maintain AV systems (NGCS 



Prepare, test & monitor VTC sessions (NGCS and 

NON NGCS) 

Book and plan VTC request (NGCS and NON 

NGCS) 

Support VTC Testing 




Knowledge of ICT architectural design 












50 COMMCEN-Voice System-Engineer 3 

51 COMMCEN-Data Client Support Technician 2 

Install, Maintain and Support all Voice systems 

under Combranch Authority (in NGCS and NON 

NGCS); 

Update and Keying of all Secure Voice Systems 

(NGCS and NON NGCS); 

Provide support as Second line Service Desk 

Support all Client orientated Software/hardware 

applications under Combranch authority; 



and VOIP) 


and IP) 











requirements 



Develop, install & maintain local and remote LANs Knowledge of common OS 



52 COMMCEN-Data LAN Manager 2 

Provide support as Second line Service Desk. Knowledge of Network administration 







53 COMMCEN-Data Network Engineer 2 

54 COMMCEN-Data Software Developper 2 


requirements; 

Support all WAN services under Combranch 

authority; 



requirements; 

Develop, install & maintain Software Applications 







Knowledge of Network administration 








Knowledge of Common programming languages & 

webdesign 


55 COMMCEN-COMCEN Communication Technician 7 

56 COMMCEN-COMCEN Communication Service Desk Operator 7 

Operate and maintain all NGCS and NON-NGCS 

systems installed in NATO HQ (24/7); 



authority; 

Supervise, monitor and troubleshoot on all NGCS 

and NON NGCS transmission trunks and/or 

circuits; 

Install,configurate and program all NGCS Crypto 

Equipment including Key changes. 

Operate NATO HQ's Military Message Handling 

System and distribution on NON-NGCS in the HQ 

(24/7); 



authority; 

Operate the NATO HQ private Switchboard 

outside normal business hours (24/7); 

Deliver transport services within the Combranch 

outside business hours. 


and VOIP) 


and IP) 











57 COMMCEN-COMCEN COMCEN Duty Communication Officer 7 

58 COMMCEN-COMCEN Dept Head COMCEN 1 

59 COMMCEN-COMCEN Head COMCEN 1 

60 COMMCEN-PABX PABX Operator Assistant 2 

Supervises, operates and support all 

Communication Center activities 



authority, including maintaining an incident 

reporting database (24/7); 

Maintain the 24/7 facilities in coordination with BE 

Administration section outside business hours 

Participate in managing daily operations of the 

Comcentre, including PABX and Service Desk; 

Support quality assurance of all Comcentre 


required; 

Support the daily people management in the 

Comcentre; 

Support the planning for training activities to bring 

and keep all Comcentre staff at the required 

quality level; 

Participate in overviewing issue and incident 

reporting and initiate problem requests when 

appropriate 

Manage daily operations of the Comcentre, 

including PABX and Service Desk 

Guarantee the quality assurance of all Comcentre 


required; 

Take care of daily people management in the 

Comcentre; 

Plan training activities to bring and keep all 

Comcentre staff at the required quality level; 

Overview issue and incident reporting and initiate 

problem requests when appropriate. 























61 COMMCEN-PABX PABX Operator 2 









Maintain all contacts with the business units on 

communication service delivery, including user 

requirements gathering for new systems and 

system modifications. 

Administrate SLA management between the 

Combranch and the business units or other 

62 


service providers. 

Business Demand and Quality Assurance 3 


Coordination and development of test procedures 

in support of system acceptance and/or 

accreditation. 





63 

64 

65 







Communication Security Administrator 1 

Crypto Custodian 2 

Logistic, Contracting and Infra Administrator 2 

Sub-total COMMCEN 54 

66 PASP-ACCS Sr Programmer/Analyst 1 

67 PASP-ACCS Programmer/Analyst 2 

Drafts and evaluates all security documents 

related to systems under Combranch Authority; 

Deliver support in security acreditation testing 

procedures. 

Manage and control all NATO HQ CCI - Mat 

(including Key-distribution and destruction) 

Administrate security clearances for Combranch 

staff; 

Controls all assigned subaccounts 

Deliver Logistic Support for NATO HQ's NGCS: 

Control and inventory of all NGCS material, 

including administation, and maintaining records 

on all transactions including repair, calibration and 

inventory; 

Deliver Logistic Support to NATO HQ's NON- 

NGCS: Control and inventory of all NON-NGCS 

material, including administration and maintaining 

records on all transactions including repair and 

inventory; 

Budget Planning: Participate in the budget 

planning process by administrating the different 

budget lines allocated to the Combranch; 

Budget Execution: Participate in the procurement 

process by prospecting and administation of 

procurement processes; 

Administrate and monitor all NON-NGCS 

maintenance contacts; 

Administer and request maintenance works on 

space allocated to the Combranch including office 

furniture 

PASP 

Senior programmer & system analyst, DBA, 

network administrator, security officer, application 

support, meeting support for Data Management 

Experts Group 

Programmer/Analyst, deputise the roles of the 

above, application support, meeting support for 

Data Management Experts Group. 

Knowledge of business requirement gathering processes 

Knowledge of Program Management Methodologies 








Budgetary and costing model processes 




administration. ITIL, PRINCE2 (scheduled) 



administration. 





68 PASP-ACCS Junior engineer 1 

Sub-total PASP 4 



Taking back-ups, staging of equipment meeting 

support for Data Management Experts Group. 

Professional level system development, professional level 

hardware & OS software, system administration. 





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



AGENCY 




(NNHQ - ANWI) 

BOOK II – PART IV 

STATEMENT OF WORK 

VERSION 03 



Book II Page IV-i



SECTION 1. REFERENCE DOCUMENTS ....................................................................... 1 

1.1 Applicable Documents ................................................................................................. 1 

1.1.1 NATO ................................................................................................................... 1 

1.1.2 Non-NATO ........................................................................................................... 5 

SECTION 2. INTRODUCTION .......................................................................................... 6 

2.1 Purpose ......................................................................................................................... 6 

2.2 Background .................................................................................................................. 6 

2.3 Scope ............................................................................................................................ 7 

2.3.1 Geographic Scope ................................................................................................. 7 

2.3.2 Functional Scope ................................................................................................... 7 

2.3.3 Service Provisioning Model .................................................................................. 7 

2.3.4 Overview of Deliverables ..................................................................................... 8 

2.4 NNHQ Key Programme Planning Factors ................................................................... 9 

2.5 Statement of Work (SOW) Organisation ................................................................... 10 

SECTION 3. HIGH LEVEL ANWI STRATEGIC REQUIREMENTS ........................... 12 

3.1 ANWI Business Benefits ........................................................................................... 12 

3.2 Overall NNHQ Programme Structure ........................................................................ 12 

3.3 High Level ANWI Strategic Principles ..................................................................... 13 

3.4 NNHQ Users .............................................................................................................. 13 

3.5 Security Domains ....................................................................................................... 14 

3.6 High Availability ........................................................................................................ 14 

3.7 Life-Cycle and Innovation ......................................................................................... 15 

3.7.1 Life-Cycle ........................................................................................................... 15 

3.7.2 Innovation ........................................................................................................... 16 

3.7.3 Capability to Service Evolution .......................................................................... 17 

3.7.4 Service Level Management (SLM)..................................................................... 17 

3.7.5 Service Provisioning Models .............................................................................. 18 

3.7.6 Contractor ICT Support Following Acceptance ................................................. 19 

3.8 Design ........................................................................................................................ 19 

3.9 Interfacing with NATO Provided Services ................................................................ 22 

3.10 Implementation .......................................................................................................... 23 

3.10.1 General ................................................................................................................ 23 

3.10.2 Site Survey .......................................................................................................... 24 

3.10.3 Installation ........................................................................................................... 24 

3.10.4 Migration and Interoperability ............................................................................ 24 

3.10.5 Service Provisioning ........................................................................................... 24 

3.10.6 Training ............................................................................................................... 26 

3.10.7 Testing & Acceptance ......................................................................................... 27 

3.10.8 Support ................................................................................................................ 27 

3.10.9 Total Cost of Ownership (TCO) Assessment ..................................................... 28 

3.11 Integration and Testing Services ................................................................................ 28 

3.12 Nations and Partners .................................................................................................. 28 


Book II Page IV-ii



Book II Page IV-iii 


SECTION 4. PROJECT MANAGEMENT ....................................................................... 29 

4.1 Introduction ................................................................................................................ 29 

4.2 Organisation ............................................................................................................... 29 

4.2.1 Purchaser Project Organisation and Responsibilities.......................................... 29 

4.2.2 ANWI Contractor Project Management Office .................................................. 29 

4.2.3 ANWI Project Manager (PM)............................................................................. 30 

4.2.4 ANWI Technical Lead (TL) ............................................................................... 31 

4.2.5 ANWI Test Director (TD)................................................................................... 32 

4.2.6 Key Supporting Staff .......................................................................................... 33 

4.3 Project Management Documentation ......................................................................... 33 

4.4 Project Controls .......................................................................................................... 34 

4.4.1 Stages and Transition .......................................................................................... 34 

4.4.2 Change Management .......................................................................................... 35 

4.4.3 Change Requests ................................................................................................. 36 

4.4.4 Off-Specifications ............................................................................................... 36 

4.5 Project-Level Communications .................................................................................. 36 

4.5.1 General ................................................................................................................ 36 

4.5.2 Formal Meetings ................................................................................................. 36 

4.5.3 Informal Meetings ............................................................................................... 38 

4.5.4 Project Status Reports ......................................................................................... 38 

4.5.5 Project Web Space .............................................................................................. 38 

SECTION 5. ANWI SERVICE AND SYSTEM DESIGN ............................................... 40 

5.1 General ....................................................................................................................... 40 

5.2 Preliminary Design Review (PDR) Meeting ............................................................. 40 

5.3 Design Document Package ........................................................................................ 41 

5.3.1 General ................................................................................................................ 41 

5.3.2 Design Document ................................................................................................ 41 

5.3.3 Service Interface Profiles (SIPs) ......................................................................... 45 

5.3.4 Security Design & Accreditation ........................................................................ 45 

5.3.5 Change Request Log ........................................................................................... 45 

5.3.6 Off-Specification Document ............................................................................... 46 

5.3.7 Requirements Traceability and Changes ............................................................ 46 

5.4 Service Management Design ..................................................................................... 46 

5.5 Integrated Test Service (ITS) Design ......................................................................... 46 

5.6 Critical Design Review (CDR) .................................................................................. 46 

5.7 Critical Design Review (CDR) Feedback Meeting .................................................... 47 

5.8 Acceptance of the Design Document ......................................................................... 48 

SECTION 6. ANWI IMPLEMENTATION AND TRANSITION .................................... 49 

6.1 General ....................................................................................................................... 49 

6.2 Transition Planning and Support Process .................................................................. 50 

6.3 Change Management .................................................................................................. 50 

6.3.1 General ................................................................................................................ 50 

6.3.2 Types of Service Change .................................................................................... 51



Book II Page IV-iv 


6.3.3 Change Requests ................................................................................................. 51 

6.3.4 Change Process ................................................................................................... 51 

6.3.5 Change Advisory Board (CAB).......................................................................... 51 

6.3.6 Change Models ................................................................................................... 51 

6.3.7 Change Remediation ........................................................................................... 51 

6.4 Service Asset and Configuration Management .......................................................... 52 

6.5 Release and Deployment Management Process ......................................................... 52 

6.5.1 Release and Deployment Management Process ................................................. 52 

6.5.2 Release and Deployment Planning Phase ........................................................... 53 

6.6 Accreditation Documentation .................................................................................... 56 

6.6.1 Security Risk Assessment ................................................................................... 56 

6.6.2 Security Documentation ...................................................................................... 56 

6.6.3 Server Security Roles .......................................................................................... 56 

6.7 Release Build and Test Phase .................................................................................... 56 

6.8 Testing ........................................................................................................................ 57 

6.8.1 General ................................................................................................................ 57 

6.8.2 Capability Acceptance Testing (CAT)................................................................ 58 

6.8.3 Proof of Concept Testing (PCT) ......................................................................... 59 

6.8.4 Service Certification Tests (SCT)....................................................................... 59 

6.8.5 System Activation Testing (SAT)....................................................................... 60 

6.8.6 Final Site Testing (FST)...................................................................................... 60 

6.8.7 Security Implementation Verification Procedures (SIVP).................................. 60 

6.8.8 Requirements Traceability Matrix ...................................................................... 61 

6.8.9 Test Failures ........................................................................................................ 61 

6.8.10 System Off-Specifications .................................................................................. 62 

6.9 Integration and Testing Service (ITS) ........................................................................ 63 

6.10 Deployment ................................................................................................................ 64 

6.10.1 General ................................................................................................................ 64 

6.10.2 Delivery of Equipment ........................................................................................ 64 

6.10.3 Preparations for Installation ................................................................................ 67 

6.10.4 Capability and Service Implementation .............................................................. 67 

6.10.5 Installation Back Out .......................................................................................... 69 

6.10.6 ANWI Service Activation ................................................................................... 70 

6.10.7 ANWI System Activation Testing ...................................................................... 70 

6.10.8 Physical Configuration Audits ............................................................................ 71 

6.10.9 On-Site Training ................................................................................................. 71 

6.10.10 Migration to the ANWI Environment ................................................................. 72 

6.10.11 ICT Migration Key Milestones ........................................................................... 74 

6.10.12 ANWI Contractor Task ....................................................................................... 74 

6.10.13 Migration Concept and Business Principles ....................................................... 77 

6.11 Review and Close ....................................................................................................... 77 

6.12 Knowledge Management ........................................................................................... 77 

6.13 Initial Operating Capability (IOC milestone) ............................................................ 78 

6.13.1 ANWI System Activation Testing ...................................................................... 78



6.13.2 ANWI Site Activation ......................................................................................... 79 

6.13.3 “As Built” Drawings and Documentation ........................................................... 79 

6.14 Initial Operating Capability (IOC) Acceptance ......................................................... 79 

6.15 Final Operating Capability (FOC milestone) ............................................................. 80 

6.16 Final Operating Capability (FOC) Acceptance .......................................................... 80 

6.17 Final System Acceptance (FSA milestone) ............................................................... 81 

SECTION 7. ANWI SERVICE AND SYSTEM OPERATIONS ..................................... 82 

7.1 ITIL Service Operation .............................................................................................. 82 

7.2 ANWI Service Operation Functions .......................................................................... 82 

7.2.1 Support Overview ............................................................................................... 82 

7.2.2 First Level Support ............................................................................................. 82 

7.2.3 Second Level Support ......................................................................................... 82 

7.2.4 Third Level Support ............................................................................................ 83 

7.2.5 ITIL Mapping ...................................................................................................... 83 

7.2.6 Service Desk ....................................................................................................... 83 

7.2.7 Technical Management ....................................................................................... 84 

7.2.8 IT Operation Management .................................................................................. 84 

7.3 ANWI Service Operations Processes ......................................................................... 84 

7.3.1 Incident Management .......................................................................................... 84 

7.3.2 Problem Management ......................................................................................... 85 

7.3.3 Request Fulfilment .............................................................................................. 86 

7.3.4 Access Management ........................................................................................... 86 

7.3.5 Event Management ............................................................................................. 87 

7.4 ANWI Operational Support ....................................................................................... 89 

7.4.1 Operational Support ............................................................................................ 89 

7.4.2 Operational Procedures/Operating Instructions .................................................. 92 

7.4.3 Monitor and Control ........................................................................................... 93 

7.4.4 Life-Cycle Support .............................................................................................. 93 

SECTION 8. ANWI SERVICE IMPROVEMENT ........................................................... 95 

8.1 ANWI Service Improvement Purpose ....................................................................... 95 

8.2 ANWI CSI Assumptions ............................................................................................ 95 

8.3 CSI Register ............................................................................................................... 96 

8.4 CSI Board ................................................................................................................... 96 

8.5 CSI Metrics ................................................................................................................ 96 

8.6 Seven-Steps Improvement Process ............................................................................ 97 

8.6.1 General ................................................................................................................ 97 

8.6.2 Step-1: Define What Should Be Measured ......................................................... 97 

8.6.3 Step-2: Define What CanBe Measured ............................................................... 97 

8.6.4 Step-3: Gather the Data ....................................................................................... 97 

8.6.5 Step-4: Process the Data ..................................................................................... 98 

8.6.6 Step-5: Analyse the Information and Data .......................................................... 98 

8.6.7 Step-6: Present and Use the Information ............................................................ 99 

8.6.8 Step-7: Implement the Improvements ................................................................. 99 

8.7 CSI Interactions with Other Processes ..................................................................... 100 


Book II Page IV-v



Book II Page IV-vi 


8.8 Win-Win Relationship and Management ................................................................. 101 

SECTION 9. ANNEX A: SCHEDULE OF KEY PROGRAM MILESTONES ............. 102 

9.1 ANWI Schedule ....................................................................................................... 102 

9.2 Integration Test Service ........................................................................................... 103 

SECTION 10. ANNEX B: PURCHASER FURNISHED INFRASTRUCTURE & 

SERVICES (hereafter known as PFE) ................................................................................... 104 

10.1 INTRODUCTION ................................................................................................... 104 

10.2 Global Construction Contract (GCC) Project (HN: Belgium) ................................. 104 

10.2.1 General .............................................................................................................. 104 

10.2.2 Server Rooms .................................................................................................... 104 

10.2.3 Technical Control Facility (TCF) Rooms (Communications Rooms) .............. 105 

10.2.4 Technical Equipment Room (TER) .................................................................. 105 

10.2.5 Power and Cooling ............................................................................................ 105 

10.2.6 Passive Network Infrastructure (PNWI) ........................................................... 106 

10.3 Building Management Services (BMS) Project (HN: Belgium) ............................. 107 

10.4 Electronic Security Services (ESS) PROJECT (HN: Belgium) ............................... 108 

10.5 Audio Visual Infrastructure (AVI) PROJECT (HN: Belgium) ............................... 108 

10.6 NNHQ Office Furniture Project (HN: HQPO) ........................................................ 108 

10.7 NATO General Purpose Segment Communication System (NGCS) Project (HN: 

NCIA) ................................................................................................................................. 109 

10.8 Domain Name System(DNS) Project (HN: NCIA) ................................................. 110 

10.9 Firewalls Project (HN: NCIA) ................................................................................. 110 

10.10 Active Directory AIS Single Forest Single Domain (AD AIS SFSD) Project (HN: 

NCIA) ................................................................................................................................. 110 

10.11 AIS Microsoft Exchange Services Project (HN: NCIA) ......................................... 111 

10.12 Automated Information System Enterprise Management System (AIS EMS) Project 

(HN: NCIA) ........................................................................................................................ 111 

10.13 Current HQ Baseline (HN: HQ ICTM) .................................................................... 111 

10.14 Video Tele Conference(VTC) Project (HN: NCIA) ................................................ 112 

10.15 NATO Enterprise Directory Services(NEDS) Project (HN: NCIA) ....................... 113 

10.16 NATO Cyber Defence Incident Response Centre (NCIRC) FOC Project (HN:NCIA)114 

10.17 NATO Public Key Infrastructure(NPKI) Project (HN: NCIA) ............................... 115 

10.18 Public Internet Access (PIA) Project (HN: NCIA) .................................................. 116 

10.19 Programme Management and Integration Capability(PMIC) Project (HN:NCIA) . 117 

10.20 NATO Messaging Services(NMS) Project (HN: NCIA) ......................................... 117 

10.21 Bâtiment Z Space to Support Integration and Testing Services (ITS) (HN: NCIA) 118 

10.22 Current NATO HQ Security Communications (TETRA) ....................................... 118 

10.23 Enterprise Agreement Software (HN: NCIA) .......................................................... 118 

SECTION 11. Annex C: ANWI Architecture ”Logical View” ......................................... 119 

11.1 Introduction .............................................................................................................. 119 

11.1.1 Purpose .............................................................................................................. 119 

11.1.2 Annex Structure ................................................................................................ 119 

11.2 Architecture Governance and Principles .................................................................. 119 

11.2.1 NNHQ Architecture Governance ...................................................................... 119



Book II Page IV-vii 


11.3 Services Framework ................................................................................................. 124 

11.3.1 Applied Service Framework References........................................................... 124 

11.3.2 C3 Taxonomy Services Framework .................................................................. 124 

11.3.3 Services Framework Main Concepts ................................................................ 124 

11.4 ANWI services ......................................................................................................... 127 

11.4.1 ANWI ICT Technical Services Groupings ....................................................... 127 

11.4.2 ANWI Services Listing ..................................................................................... 127 

11.4.3 Identification of ANWI related End-to-End Services ....................................... 128 

11.5 ANWI Information Infrastructures, Domains, Zoning and User Types .................. 129 

11.5.1 Introduction ....................................................................................................... 129 

11.5.2 ANWI Security Domains .................................................................................. 131 

11.5.3 User Types ........................................................................................................ 133 

11.6 Node Connectivity Diagrams ................................................................................... 136 

11.6.1 NS Infrastructure Node Connectivity ............................................................... 137 

11.6.2 Business Infrastructure Node Connectivity ...................................................... 139 

11.7 Information Exchange Requirements (IERs) ........................................................... 140 

11.7.1 ANWI NS Infrastructure IERs .......................................................................... 140 

11.7.2 ANWI Business Infrastructure IERs ................................................................. 142 

11.8 Overarching Information Assurance Architecture Concept and Requirements ....... 144 

11.8.1 ANWI IA Services Architecture ....................................................................... 144 

11.8.2 Information Assurance Architecture Compliance Approach ............................ 145 

SECTION 12. ANNEX D: ANWI Architecture Initial System and Technical View ....... 166 

12.1 Introduction .............................................................................................................. 166 

12.1.1 Purpose .............................................................................................................. 166 

12.1.2 Annex Structure ................................................................................................ 166 

12.2 Design Drivers ......................................................................................................... 166 

12.2.1 General .............................................................................................................. 166 

12.2.2 Mobility ............................................................................................................. 166 

12.2.3 Identity Management ........................................................................................ 167 

12.2.4 Infrastructure as a Service (IaaS) ...................................................................... 167 

12.2.5 Green IT ............................................................................................................ 167 

12.2.6 Virtualization .................................................................................................... 168 

12.2.7 User Experience ................................................................................................ 169 

12.2.8 Standardization ................................................................................................. 169 

12.2.9 High Available NNHQ ICT Environment ........................................................ 170 

12.2.10 Additional Availability Requirements .............................................................. 170 

12.2.11 Modularity Principle ......................................................................................... 171 

12.2.12 Reduced ICT Capacity ...................................................................................... 171 

12.3 Initial System View .................................................................................................. 173 

12.3.1 ANWI System View ......................................................................................... 173 

12.3.2 External Entities ................................................................................................ 174



Book II Page IV-viii 


12.3.3 Cross Domain Gateways (CDGW) ................................................................... 176 

12.3.4 ANWI NS Infrastructure System View ............................................................ 178 

12.3.5 ANWI NU/NR/Public Level Infrastructure System View ................................ 179 

12.3.6 NATO HQ NS to NU/NR/Public Cross Domain Infrastructure ....................... 181 

12.3.7 Cross Domain Gateway Coherency View ........................................................ 182 

12.4 ANWI Modules and Internal Interfaces Identification ............................................ 183 

12.4.1 ANWI Modules ................................................................................................. 183 

12.4.2 ANWI Module Internal Interface Identification ............................................... 188 

12.5 External Interfaces ................................................................................................... 189 

12.5.1 Facility-Physical Interfaces ............................................................................... 189 

12.5.2 NS Infrastructure External/Internal Interfaces .................................................. 191 

12.5.3 Business Infrastructure External Interfaces ...................................................... 193 

12.6 End to End Services ................................................................................................. 196 

SECTION 13. ANNEX E: SMC and IA SERVICES ........................................................ 202 

13.1 Appendix 1: Service Management and Control ....................................................... 202 

13.1.1 Definition .......................................................................................................... 202 

13.1.2 Scope ................................................................................................................. 202 

13.1.3 Governance ....................................................................................................... 203 

13.1.4 Architecture ....................................................................................................... 204 

13.1.5 Installation ......................................................................................................... 205 

13.1.6 Service Desk ..................................................................................................... 206 

13.1.7 Trouble Ticketing .............................................................................................. 206 

13.1.8 Performance Management ................................................................................ 207 

13.1.9 Service Design Processes .................................................................................. 207 

13.1.10 Service Transition Processes ............................................................................. 212 

13.1.11 Service Operations Processes............................................................................ 215 

13.1.12 Continuous Service Improvement Processes .................................................... 219 

13.1.13 Key Performance Indicators (KPIs) and Metrics .............................................. 220 

13.1.14 End-to-End Scenario Testing ............................................................................ 227 

13.1.15 Training ............................................................................................................. 228 

13.1.16 Cross Domain Requirements ............................................................................ 228 

13.1.17 Future Technology Requirements ..................................................................... 228 

13.1.18 SMC Service Level Agreement/Target ............................................................. 229 

13.1.19 Management and Operational Requirements .................................................... 229 

13.2 Appendix 2: Information Assurance ........................................................................ 231 

13.2.1 Cross Domain Module (CDM) ......................................................................... 232 

13.2.2 AV management ............................................................................................... 260 

13.2.3 NPKI ................................................................................................................. 261 

13.2.4 Incident Management ........................................................................................ 263 

13.2.5 Security Patches and Configuration Management ............................................ 266 

SECTION 14. ANNEX F: INFRASTRUCTURE SERVICES ......................................... 267 

14.1 APPENDIX 1: Introduction to Infrastructure Services ............................................ 267 

14.1.1 Definition .......................................................................................................... 267



Book II Page IV-ix 


14.1.2 Service Overview .............................................................................................. 267 

14.1.3 Scope ................................................................................................................. 267 

14.1.4 Service Requirements ....................................................................................... 268 

14.1.5 Service Level Agreement/Targets ..................................................................... 269 

14.1.6 Service Testing and Reporting .......................................................................... 269 

14.1.7 Dependencies .................................................................................................... 269 

14.2 APPENDIX 2: Processing Services ......................................................................... 271 

14.2.1 Definition .......................................................................................................... 271 

14.2.2 Scope/Scenario .................................................................................................. 271 



14.2.5 Testing ............................................................................................................... 277 

14.2.6 Training ............................................................................................................. 277 

14.3 APPENDIX 3: Storage services ............................................................................... 278 

14.3.1 Definition .......................................................................................................... 278 



14.3.4 Information Assurance ...................................................................................... 281 


14.3.6 Testing ............................................................................................................... 283 

14.3.7 Training ............................................................................................................. 283 

14.4 APPENDIX 4: Printing and Scanning Services ....................................................... 284 

14.4.1 Definition .......................................................................................................... 284 




14.4.5 Training ............................................................................................................. 287 

14.5 APPENDIX 5: Infrastructure Network Services ..................................................... 289 

14.5.1 Definition .......................................................................................................... 289 




14.5.5 Training ............................................................................................................. 296 

14.6 APPENDIX 6: LAN services ................................................................................... 298 

14.6.1 Definition .......................................................................................................... 298 



14.6.4 Conference Room Infrastructure ....................................................................... 302 

14.6.5 Information Assurance ...................................................................................... 302 

14.6.6 Service Management ......................................................................................... 303 


14.6.8 Testing ............................................................................................................... 305 

14.6.9 Training ............................................................................................................. 305 

SECTION 15. ANNEX G: UCC SERVICES .................................................................... 306



15.1 APPENDIX 1: Introduction to UCC Services ......................................................... 306 

15.1.1 Definition .......................................................................................................... 306 

15.1.2 Scope ................................................................................................................. 306 

15.1.3 Logical Model ................................................................................................... 310 

15.1.4 ANWI UCC Architecture.................................................................................. 311 

15.1.5 UCC Services and NNHQ Multiple Classification Networks .......................... 314 

15.1.6 UCC Service Management Requirements ........................................................ 315 

15.1.7 Service Level Agreement/Targets ..................................................................... 316 


15.2 APPENDIX 2: Voice ServiceComponent ................................................................ 321 

15.2.1 Definition .......................................................................................................... 321 

15.2.2 Scope / Scenario ................................................................................................ 321 



15.2.5 Testing ............................................................................................................... 326 

15.2.6 Training ............................................................................................................. 326 

15.3 APPENDIX 3: Voicemail ServiceComponent ........................................................ 327 

15.3.1 Definition .......................................................................................................... 327 




15.3.5 Testing ............................................................................................................... 329 

15.3.6 Training ............................................................................................................. 330 

15.4 APPENDIX 4: VTC ServiceComponent ................................................................. 331 

15.4.1 Definition .......................................................................................................... 331 




15.4.5 Testing ............................................................................................................... 333 

15.4.6 Training ............................................................................................................. 333 

15.5 APPENDIX 5: Email Service Component ............................................................... 335 

15.5.1 Definition .......................................................................................................... 335 




15.5.5 Testing ............................................................................................................... 338 

15.5.6 Training ............................................................................................................. 339 

15.6 APPENDIX 6: Unified Messaging Service Component .......................................... 340 

15.6.1 Definition .......................................................................................................... 340 



15.6.4 Testing ............................................................................................................... 341 

15.6.5 Training ............................................................................................................. 342 

15.7 APPENDIX 7: FAX Service Component ................................................................ 343 


Book II Page IV-x



Book II Page IV-xi 


15.7.1 Definition .......................................................................................................... 343 



15.7.4 Testing ............................................................................................................... 344 

15.7.5 Training ............................................................................................................. 345 

15.8 APPENDIX 8: Instant Messaging/Chat Service Component .................................. 346 

15.8.1 Definition .......................................................................................................... 346 




15.8.5 Testing ............................................................................................................... 347 

15.8.6 Training ............................................................................................................. 348 

15.9 APPENDIX 9: Presence Service Component .......................................................... 349 

15.9.1 Definition .......................................................................................................... 349 




15.9.5 Testing ............................................................................................................... 351 

15.9.6 Training ............................................................................................................. 351 

15.10 APPENDIX 10: UCC Directory Service Component .............................................. 352 

15.10.1 Definition .......................................................................................................... 352 




15.10.5 Testing ............................................................................................................... 353 

15.10.6 Training ............................................................................................................. 354 

15.11 APPENDIX 11: Collaboration Service Component ................................................ 355 

15.11.1 Definition .......................................................................................................... 355 




15.11.5 Testing ............................................................................................................... 357 

15.11.6 Training ............................................................................................................. 357 

15.12 APPENDIX 12: Mobility Service Component ........................................................ 359 

15.12.1 Definition .......................................................................................................... 359 




15.12.5 Testing ............................................................................................................... 360 

15.12.6 Training ............................................................................................................. 361 

SECTION 16. ANNEX H: CLIENT-PROVISIONING SERVICE .................................. 362 

16.1 APPENDIX 1: Introduction to Client Provisioning Services .................................. 362 

16.1.1 Definition .......................................................................................................... 362



Book II Page IV-xii 



16.1.3 Scope ................................................................................................................. 362 


16.1.5 Service Level Agreement / Targets. .................................................................. 367 


16.1.7 Dependencies .................................................................................................... 368 

16.2 APPENDIX 2: Software Provisioning ..................................................................... 369 

16.2.1 Definition .......................................................................................................... 369 


16.2.3 Domains ............................................................................................................ 369 

16.2.4 Location ............................................................................................................ 369 

16.2.5 Client Platform Provisioning ............................................................................ 369 

16.2.6 Application Provisioning .................................................................................. 371 

16.2.7 Client provisioning infrastructure ..................................................................... 372 

16.2.8 Service Level Agreement/Target ...................................................................... 372 


16.2.10 Testing ............................................................................................................... 373 

16.2.11 Training ............................................................................................................. 374 

16.3 APPENDIX 3: Client Devices ................................................................................. 375 

16.3.1 Definition .......................................................................................................... 375 

16.3.2 Scope ................................................................................................................. 375 


16.3.4 ClientDevice’s Information Assurance ............................................................. 380 


16.3.6 Dependencies .................................................................................................... 383 

SECTION 17. ANNEX I: SUPPLEMENTARY SERVICES ........................................... 384 

17.1 APPENDIX 1: Introduction to Supplementary Services ......................................... 384 

17.1.1 Definition .......................................................................................................... 384 


17.1.3 Scope ................................................................................................................. 384 


17.1.5 Service Level Agreement / Targets ................................................................... 385 


17.1.7 Dependencies .................................................................................................... 386 

17.2 APPENDIX 2: GSM Service continuity .................................................................. 387 

17.2.1 Definition .......................................................................................................... 387 




17.2.5 Testing ............................................................................................................... 388 

17.3 APPENDIX 3: GSM Blocking ................................................................................ 388 

17.3.1 Definition .......................................................................................................... 388 


17.3.3 Service Requirements ....................................................................................... 389



Book II Page IV-xiii 




17.3.6 Testing ............................................................................................................... 390 

17.3.7 Training ............................................................................................................. 390 

17.4 APPENDIX 4: Wireless Blocking ........................................................................... 391 

17.4.1 Definition .......................................................................................................... 391 





17.4.6 Testing ............................................................................................................... 392 

17.4.7 Training ............................................................................................................. 392 

17.5 APPENDIX 5: Site Security Comms (TETRA) ...................................................... 393 

17.5.1 Definition .......................................................................................................... 393 





17.5.6 Testing ............................................................................................................... 394 

17.5.7 Training ............................................................................................................. 394 

17.6 APPENDIX 6: IPTV ................................................................................................ 395 

17.6.1 Definition .......................................................................................................... 395 





17.6.6 Testing ............................................................................................................... 400 

SECTION 18. ANNEX J: INTEGRATION AND TESTING SERVICES ....................... 401 

18.1 APPENDIX 1: Introduction to Integration and Testing Services ............................ 401 

18.1.1 Interfaces ........................................................................................................... 401 

18.1.2 Security ............................................................................................................. 401 

18.1.3 Training ............................................................................................................. 401 

18.1.4 Requirements .................................................................................................... 401 

18.1.5 Acceptance ........................................................................................................ 402 

18.1.6 Documentation .................................................................................................. 402 

18.1.7 Architecture and Services ................................................................................. 402 

18.1.8 Location and Facility Context ........................................................................... 403 

18.1.9 Organisational Support Requirements .............................................................. 404 

18.1.10 Management Requirements .............................................................................. 404 

18.1.11 Concept of Operations ...................................................................................... 405 

18.2 APPENDIX 2: ITS Reference Environment ............................................................ 407 

18.2.1 Introduction ....................................................................................................... 407 

18.2.2 Testing ............................................................................................................... 408 

18.2.3 ITS Infrastructure .............................................................................................. 408



18.3 APPENDIX 3: ITS Service Level Agreement (SLA) .............................................. 410 

18.3.1 Introduction ....................................................................................................... 410 

18.3.2 Service Delivery ................................................................................................ 411 

18.3.3 SLA Change Management ................................................................................ 412 

18.3.4 Roles and Responsibilities ................................................................................ 413 

SECTION 19. ANNEX K: DOCUMENTATION AND REPORTS................................. 415 

19.1 Appendix 1: ANWI Document Requirements ......................................................... 415 

19.1.1 Purpose .............................................................................................................. 415 

19.1.2 Format Requirements for Project Documentation ............................................ 415 

19.1.3 Submission of Project Documentation .............................................................. 416 

19.1.4 Delivery and Distribution of Project Documentation ....................................... 416 

19.1.5 Review of Project Documentation .................................................................... 416 

19.1.6 Control Information for Project Documentation ............................................... 417 

19.2 APPENDIX 2: Design Document ............................................................................ 419 

19.2.1 Introduction/Purpose ......................................................................................... 419 

19.2.2 Scope/Assumptions ........................................................................................... 419 

19.2.3 Reporting& Provisioning .................................................................................. 419 

19.2.4 Document Structure .......................................................................................... 419 

19.3 Appendix 3: Project Management Plan (PMP) ........................................................ 445 





19.4 Appendix 4: Project Implementation Plan (PIP) ...................................................... 449 



19.4.3 Reporting & Provisioning ................................................................................. 450 


19.5 Appendix 5: Risk Management Plan (RMP) ........................................................... 455 

19.5.1 Introduction/purpose ......................................................................................... 455 

19.5.2 Scope/assumptions ............................................................................................ 455 



19.6 APPENDIX 6: Quality Assurance Plan (QAP) ....................................................... 464 





19.7 APPENDIX 7: Configuration Management Plan (CMP) ........................................ 470 


19.7.2 Scope/Assumprion ............................................................................................ 470 



Book II Page IV-xiv



Book II Page IV-xv 



19.8 APPENDIX 8: Test and Acceptance Plan (TAP) .................................................... 480 





19.9 APPENDIX 9: Integrated Logistics Support Plan (ILSP) ....................................... 486 





19.10 APPENDIX 10: NATO Material Data Sheet ........................................................... 489 




19.10.4 Data Sheet Structure ......................................................................................... 489 

19.11 APPENDIX 11: Security Risk Assessment ............................................................. 491 





19.12 APPENDIX 12: Security Test and Evaluation (ST&E) Plan .................................. 494 





19.13 APPENDIX 13: Security Documentation Input ...................................................... 498 

19.13.1 Introduction/pPurpose ....................................................................................... 498 



19.14 APPENDIX 14: Project Progress Review Meeting (PPRM) ................................... 504 




19.14.4 Reporting Structure ........................................................................................... 504 

19.15 APPENDIX 15: Project Status Report (PSR) .......................................................... 506 




19.15.4 Reporting Structure ........................................................................................... 506 

19.16 ANNEX K APPENDIX 16: Migration Plan ............................................................ 508







19.17 ANNEX K APPENDIX 17: Service Interface Profile (SIP) ................................... 515 





19.18 ANNEX K APPENDIX 18: Service Level Agreement ........................................... 518 



19.18.3 Reporting &Provisions ...................................................................................... 518 


SECTION 20. ANNEX L: NATIONS AND PARTNERS ................................................ 520 

20.1 Purpose ..................................................................................................................... 520 

20.2 NATO Nation ........................................................................................................... 520 

20.3 Partner Nations ......................................................................................................... 521 

SECTION 21. ANNEX M: REMOTE SITES ................................................................... 522 

21.1 Purpose ..................................................................................................................... 522 

21.2 Remote Sites ............................................................................................................ 522 

21.3 Supporting Additional Remote Needs ..................................................................... 523 

21.3.1 Travel Kits. ....................................................................................................... 524 

SECTION 22. ACRONYMS ............................................................................................. 526 


Book II Page IV-xvi



SECTION 1. 

REFERENCE DOCUMENTS 

1.1 Applicable Documents 

1.1.1 NATO 

1.1.1.1 Allied Quality Assurance Publications (AQAP): 

1.1.1.1.1 AQAP 2070, NATO Mutual Government Quality Assurance (GQA). 

1.1.1.1.2 AQAP 2009, Guidance for the Use of AQAP 2000 series. 

1.1.1.1.3 AQAP 160, NATO Quality Assurance Requirements for Software 

Development. 

1.1.1.2 Allied Configuration Management Publications (ACMP): 

1.1.1.2.1 ACMP 1, NATO Requirements for the Preparation of Configuration 

Management Plans. 

1.1.1.2.2 ACMP 2, NATO Requirements for Configuration Identification. 

1.1.1.2.3 ACMP 3, NATO Requirements for Configuration Control--Engineering 

Changes, Deviations, and Waivers. 

1.1.1.2.4 ACMP 4, NATO Requirements for Configuration Status Accounting. 

1.1.1.2.5 ACMP 5, NATO Requirements for Configuration Audits. 

1.1.1.2.6 ACMP 6, NATO Configuration Management Terms and Definitions. 

1.1.1.2.7 ACMP 7, NATO Configuration Management Guidance on the Application 

of ACMPs 1 to 6. 

1.1.1.3 SECAN Doctrine and Information Publication (SDIP): 

1.1.1.3.1 (NATO RESTRICTED),SDIP-29/1 - Facility Design Criteria and Installation 

of Equipment for the Processing of Classified Information; January 2011. 

1.1.1.4 Standard NATO Guidance (STANAG): 

1.1.1.4.1 STANAG 4107, Mutual Acceptance of Government Quality Assurance and 

Usage of the Allied Quality Assurance Publications. 

1.1.1.4.2 STANAG 4427, Introduction of Allied Configuration Management 

Publications (ACMP), February 2007. 

1.1.1.4.3 STANAG 6001, Language Proficiency Levels. 


Book II Page IV-1 of 532


1.1.1.5 Bilateral Strategic Command (Bi-SC) Documents: 


1.1.1.5.1 Bi SC Automated Information System (AIS) Minimum Hardware 

Procurement Specifications (MHWPS); v5.6, July 2012. 

1.1.1.5.2 NATO Training Directive Bi-SC Directive75-7. 

1.1.1.5.3 Single-Forest Single-Domain Administration SOP; v2.2, August 2006. 

1.1.1.5.4 NCSA Managed Forests Join SOP; v4.8, May 2010. 

1.1.1.6 NATO Security Documents: 

1.1.1.6.1 Guidelines for Security Risk Assessment (SRA) and Risk Management of 

CIS, Ref. AC/35-D/1017-REV2, 26 February 2003. 

1.1.1.6.2 (NATO RESTRICTED),Guidelines for the Development of Security 

Requirement Statements (SRSs), AC/35-D/1015-REV3, 31 January 2012. 

1.1.1.6.3 Guidelines for the Structure and Content of Security Operating Procedures 

(SecOPs) for CIS, AC/35-D/1014-REV3, 31 January 2012. 

1.1.1.6.4 INFOSEC Technical & Implementation Directive for the Interconnection of 

Communication and Information Systems (CIS); AC/322-D/0030-REV5, 

February 2011. 

1.1.1.6.5 (NATO RESTRICTED),INFOSEC Technical & Implementation Directive for 

Computer and Local Area Network (LAN) Security; AC/322-D/0048. 

1.1.1.6.6 (NATO RESTRICTED),INFOSEC Technical & Implementation Directive on 

Cryptographic Security and Cryptographic Mechanisms; AC/322-D/0047- 

REV2, March 2009. 

1.1.1.6.7 (NATO RESTRICTED),NATO INFOSEC Technical Centre (NITC) Cisco 

Switches Hardening Guide; v.1.2, March 2009. 

1.1.1.6.8 Reserved . 

1.1.1.6.9 Reserved . 

1.1.1.6.10 Information Assurance Technical and Implementation Directive on 

Security Management Infrastructure (SMI); Ref.: AC/322-D(2010)0055, 

December 2010. 

1.1.1.6.11 NATO Public Key Infrastructure (PKI) Certificate Policy; AC/322- 

D(2004)0024-REV2-AS1, February 2008 

1.1.1.6.12 INFOSEC Technical and Implementation Guidance for Electronic Labelling 

of NATO Information; AC/322-D(2004)0021, Mar 2004. 





1.1.1.6.13 NATO C3 Board Technical and Implementation Guidance for Consistent 

Marking of NATO Information in C3 Systems; AC/322-D(2004)0022, 

March 2004. 

1.1.1.7 HQPO documents: 

1.1.1.7.1 New NATO Headquarters ICT Target Architecture; v2.0, July 2011. 

1.1.1.7.2 New NATO HQ Security Accreditation Directive; v2.0, June 2011. 

1.1.1.7.3 New NATO HQ Security Accreditation Plan; v1.1, Feb 2011. 

1.1.1.7.4 North Atlantic Treaty Organization (NATO) New NATO Headquarters 

Security Concept of Operations (CONOPS); v2.0, May 2011. 

1.1.1.7.5 New NATO HQ ICT Migration Strategy; v1.1, June 2011. 

1.1.1.7.6 Integrated Logistics Support and Operations & Maintenance Directive; 

May 2011. 

1.1.1.7.7 Green IT Directive; May 2011. 

1.1.1.7.8 Testing & Acceptance Directive; May 2011. 

1.1.1.7.9 HQPO ICT RCN24 IPTV; v1.0, August 2011 

1.1.1.7.10 New NATO Headquarters ICT Target Architecture Directive; v1.1 July 

2011. 

1.1.1.7.11 HQPO ICT RCN24 IPTV; v1.0 August 2011 spreadsheet with initial 

television channels required. 



1.1.1.8 Other NATO documents: 


1.1.1.8.1 NATO Interoperability Management Plan, Volume 2. 

Book II Page IV-4 of 532 


1.1.1.8.2 NATO C3 Board (NC3B) NATO C3 System Interoperability Directive (NID), 

Annex 1; AC/322-D(2004)0001 (INV). 

1.1.1.8.3 PNWI Specs Desk Modules, November 2009. 

1.1.1.8.4 NCSA Approved Fielded Product List (AFPL). 

1.1.1.8.5 (NATO RESTRICTED),NATO HQ ICT Revitalization Network Realignment 

& Robustness (NR2) Target Architecture (TA) Security Mechanisms 

version 2.2”; Ref.: EM(ICT)(2012)0060; dated 28 Feb 2012. 

1.1.1.8.6 NNHQ ANWI Initial Service Catalogue spreadsheet; November 2011. 

1.1.1.8.7 NC3A Technical Design Directive NATO C4ISR System Design Principles; 

November 2011; October 2011. 

1.1.1.8.8 NATO Enterprise Directory Service (NEDS). 

1.1.1.8.9 Public Internet Access (PIA) Gateway Services High level design. 

1.1.1.8.10 Upgraded informal Email: System Design specification; January 2010. 

1.1.1.8.11 Upgraded informal Email: Interface Control Document; January 2010. 

1.1.1.8.12 NCSA EMS SCCM Technical Design; v1.1, January 2010. 

1.1.1.8.13 (NATO RESTRICTED),NGCS Target Architecture 2011; v4.2, November 

2009. 

1.1.1.8.14 Reserved 

1.1.1.8.15 PMIC Integration Facility HLD; v0.9, August 2010. 

1.1.1.8.16 NMS - An Architectural description; v0.99, October 2006. 

1.1.1.8.17 PNWI Cabling Design 

1.1.1.8.18 NCSA EMS SCOM Technical Design; v1.1, January 2010. 

1.1.1.8.19 “NATO Architecture Framework (NAF) Version 3. AC/322(SC/1- 

WG/1)N(2007)0004, August 2007). 

1.1.1.8.20 PNWI Chahier des charges (English version) dated 1 June 2012. 

1.1.1.8.21 Server Room PNWI Design dated 13 January 2009. 

1.1.1.8.22 Approved Fieflded Products List (AFPL) NS20120629 dated 29 June 

2012. 

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



1.1.1.8.23 RD3186 - Collaboration Services Service Interface Profile Proposal 

Version 1.2 Final Draft dated March 2012 

1.1.1.8.24 RD3186 - Annex A: Core and Advanced Instant Messaging Services 

Version 1.2 Final Draft dated March 2012 

1.1.1.8.25 NGTS-56 - Standard Specification for VTC Equipment for use in NATO – 

Issue 2 dated April 2012 

1.1.2 Non-NATO 

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





SECTION 2. 

INTRODUCTION 

2.1 Purpose 

2.1-p1 The purpose of this Statement of Work (SOW) is to define the work that 

needs to be completed in order to deliver the Information and Communication 

Technology (ICT) services of the Active Network Infrastructure (ANWI) for the New 

NATO Headquarters (NNHQ). 

2.1-p2 The Active Network Infrastructure (ANWI) project shall henceforth be 

referred to as ‘ANWI’. 

2.1-p3 The ANWI provides the core infrastructure and NNHQ end user devices, 

supporting all end user services. 

2.1-p4 This SOW defines the required capabilities in terms of services that must 

be provided and leaves the details of the implementation to the Contractor to 

propose. 

2.1-p5 Delivery of the ANWI requires the Contractor to design, procure, 

implement, provide and support the services defined in this SOW. 

2.1-p6 Acceptance of the ANWI’s capability will be based on the Contractor’s 

successful demonstration that all services defined in this SOW are provided per the 

described requirements. The ANWI default condition will be NATO Owned Contractor 

Operated (NOCO) unless otherwise noted. On a service-by-service basis, NATO may 

decide to take ownership and operational control of the delivered services from the 

ANWI Contractor. The determination of which services will be operated by the 

Contractor will be based largely on the ANWI Contractor’s operational support cost. 

2.2 Background 

2.2-p1 At the 50th Anniversary Summit in Washington in April 1999, Heads of 

State and Government agreed to construct a new NATO Headquarters in Brussels: 

"to meet the requirements of the Alliance in the 21st Century". 

2.2-p2 After the concept development and the associated financial authorisation, 

Host Nation Belgium let the construction contract where ground breaking took place 

on 16 December 2010 and the actual construction work began on 18 October 2010, 

two months earlier. The building is planned for handover to NATO at the end of 2015 

(see Annex A). 

2.2-p3 The New NATO Headquarters will reflect the Alliance's core functions and 

activities of supporting formal and informal consultation and co-operation between 

NATO's member countries, between member countries and partners, other countries, 

and other international organisations. To this end, the New NATO Headquarters’ 

campus will provide: 

Up-to-date conference facilities. 

Office accommodation for Delegations, Military Representations, International 

Staff (IS), International Military Staff (IMS), Agencies and Partner Missions. 





 

 

A variety of support service outlets such as restaurants, banks, shops and 

leisure and sports facilities. 

All of the above will be supported by state of the art information, 

communications and technology (ICT) systems. 

2.3 Scope 

2.3.1 Geographic Scope 

2.3.1-p1 The ANWI equipment and service delivery will be to the NNHQ (across 

the street from the current NATO HQ building) and other buildings (including 

Bâtiment Z) that are on the current NATO campus located in Brussels, Belgium. The 

NNHQ and legacy facilities on the current NATO campus will hereafter be called the 

NNHQ campus. 

2.3.1-p2 The ANWI contract also requires the replacement of existing NATO 

equipment and capabilities with ANWI equipment and services installation at five (5) 

remote sites. 

2.3.1-p3 The Integration and Testing Services (ITS) shall be located in the 

basement of Bâtiment Z, which is the current location of NCIA in Brussels. 

2.3.1-p4 The ANWI Contractor will be provided with storage and staging space 

on location on the NNHQ campus and outside space to establish an on-location 

office. 

2.3.1-p5 The support Authority for all NATO-wide services is the NATO 

Communications Information Agency (NCIA). 

2.3.2 Functional Scope 

2.3.2-p1 This SOW defines the required NNHQ capabilities in terms of services 

that the ANWI Contractor shalldeliver .The SOW leaves the details of the design, 

procurement and implementation to the Contractor to propose. 

2.3.2-p2 The ANWI Contractor shall deliver four domains (identified in paragraph 

2.3.4-p2) on the NNHQ campus which provide selected ANWI services to a wide 

range of users located in offices, conference rooms, out buildings and guardhouses 

across the NNHQ campus and connected remote locations. 

2.3.2-p3 The ANWI Contractor shall deliver all ANWI services, operate the suite 

of selected manageable services and offer user consumable services via the NATO 

HQ Service Catalogue so an authorised NNHQ user can request (and national 

delegations possibly procure) and use. 

2.3.3 Service Provisioning Model 

2.3.3-p1 The SOW requires that the ANWI Contractor provides the NNHQ 

functionality as services and envisages three models for long term service 

provisioning: NATO-Owned / NATO-Operated (NONO); NATO-Owned / Contractor 

Operated (NOCO); and Contractor-Owned / Contractor-Operated (COCO). 

2.3.3-p2 The ANWI services shall be bid as either NOCO or COCO (IPTV, GSM 

and Printing/Scanning); where the Purchaser will decide on the final provisioning 

model (based on the cost effectiveness of the offer, needed skills/expertise and 





security considerations) which may result in a NONO service model replacing a 

NOCO offer. 

2.3.3-p3 NATO will have on-site ICT staff (either exclusively ANWI Contractor [if 

services are NOCO/COCO, and NONO option is not exercised] or, if NONO option is 

exercised, a combination of ANWI Contractor [who shall be responsible for all 

NOCO/COCO services] and NATO staff [who shall be responsible only for NONO 

services]) that shall be able to autonomously serve as the NNHQ’s service 

management and control Authority and be called the NNHQ O&M authority. 

2.3.3-p4 NCIA staff located in Mons (NATO’s Operations and Maintenance 

[O&M] Authority) will serve as: the remote administrators for agreed information 

assurance services; enterprise administrators; and the centralised service 

management Authority. 

2.3.4 Overview of Deliverables 

2.3.4-p1 The ANWI Contractor shall design, procure and implement the ANWI 

for the NNHQ campus and remote sites (see Annex M), based on the stated 

requirements herein. 

2.3.4-p2 ANWI Contractor shall deliver: 

A. Infrastructure Services (providing network infrastructure, server 

processing, storage, and print/scan capabilities) to support four security 

domains located in the NNHQ. These domains are named as follows: 

1. NATO SECRET (NS) 

2. Euro Atlantic Partnership Council (EAPC) SECRET. 

3. NATO Business. 

4. Public. 

B. Local Area Network (LAN) services providing on campus: 

1. Wired switching capabilities, supporting the four security domains, 

connecting users with network services via the Purchaser provided 

cabling infrastructure. 

2. Wireless LAN switching and associated Access Points (AP) capabilities 

for the NATO Business and Public domains that use the connectivity of 

the NNHQ’s Purchaser provided cabling infrastructure. 

C. Cross-Domain Gateway (CDGW) Services supporting external network 

interconnection and inter-security domain interconnection & 

interoperability capabilities supporting the following NNHQ 

interconnectivity: 

1. CDGW1: NS LAN to NS Wide Area Network (WAN). 

2. CDGW2: 

a. NATO Business LAN to NR WAN. 

b. NATO Business LAN to NU WAN. 

c. NATO Business LAN to Internet/Public Networks/Public LAN (via 

CDGW3). 

3. CDGW3: 





a. Public LAN to Internet. 

b. Internet/Public Networks/Public LAN to NATO Business LAN (via 

CDGW2). 

4. CDGW4: EAPC SECRET LAN to NS LAN. 

5. CDGW5: NATO Business LAN to NS LAN. 

6. CDGW6: Public LAN to NS LAN. 

E. Unified Communications & Collaboration Services providing integrated: 

1. Voice and voicemail services. 

2. Video TeleConferencing services. 

3. E-mail services. 

4. Unified Messaging services. 

5. Instant Messaging services. 

6. Presence services. 

7. Fax services. 

8. Directory services. 

9. Collaboration services (white boarding and chat). 

10. Mobility services. 

F. Desktop Client provisioning (end-user) services (including portables and 

small footprint devices) 

G. Supplementary services providing: 

1. Internet Protocol (IP) Television (IPTV) services 

2. Global System for Mobile Communications (GSM) services. 

3. Site security communications (radio). 

H. ANWI Integration and Testing Services (ITS) offering a reference suite of 

ANWI Contractor provided and managed functional baselines that the 

ANWI Contractor and all new building Host Nations will use to test their 

deliverables prior to deployment in the new building NNHQ. 

I. Integration of the ANWI capability with NATO’s extant NATO SECRET 

(NS) and NATO RESTRICTED (NR) Automated Information System (AIS) 

and network services that are external to ANWI. 

J. Migration and support transition of ANWI equivalent services from the 

current HQ to the new NATO HQ building NNHQ. 

K. Support the NATO Contractor in the migration of applications and data 

from the current building HQ to the new building’s NNHQ ANWI 

infrastructure. 

L. Provision of on-site support of the ANWI services. 

M. Provision of Service Management and Control of the ANWI services 

2.4 NNHQ Key Programme Planning Factors 

2.4-p1 The NATO Headquarters Programme Office (HQPO) is designated as 

being overall responsible for the NNHQ integration activities. The overall NNHQ 

programme plan coordinates the deliverables for a number of NATO elements and 

Host Nations all working together to deliver the totality of the NNHQ. 







2.4-p2 The HQPO plan for NNHQ addresses the projects identified below: 

A. NATO Projects 

1. NATO General (purpose-segment) Communications System (NGCS) 

2. NATO Public Key Infrastructure (NPKI) 

3. NATO Enterprise Directory Service (NEDS) 

4. NATO Computer Incident Response Capability (NCIRC) 

5. Public Internet Access (PIA) 

6. NATO Video-Teleconferencing service (VTC) 

B. Host Nation Belgium 

1. Global Construction Contract (GCC)supporting the following capabilities 

relevant to ANWI: 

a. Server &technical equipment rooms, power and cooling 

b. Passive Network Infrastructure (PNWI) [cabling and intelligent 

patching system] 

c. Building Management System (BMS) 

2. Electronic Security System (ESS) 

3. Audio/Video Integration (AVI) 

C. Host Nation ICTM 

1. Business Application and Data Migration (BADM) 

2.4-p3 The ANWI Contractor shall adhere to the key milestone dates provided in 

Annex A: Schedule of Programme Milestones, to maintain the overall NNHQ 

programme schedule with the ANWI dependent elements and projects. 

2.5 Statement of Work (SOW) Organisation 

2.5-p1 The remainder of this Statement of Work (SOW) defines the requirements 

for services and supplies to be provided by the Contractor under this contract. 

2.5-p2 The SOW’s main body defines the project scope as well as high level and 

common (across all deliverables) requirements as identified below: 

High Level ANWI Strategic Requirements. 

Project Management. 

ANWI Service and System Design. 

ANWI Implementation and Transition. 

ANWI Service and System Operations. 

ANWI Service Improvement. 

2.5-p3 The SOW Annexes contain information needed for the planning, design 

and implementation of the ANWI. 

Annex A: Schedule of Key Program Milestones. 

Annex B: Purchaser Furnished Equipment. 

Annex C: ANWI Architecture’s “Logical View”. 

Annex D: ANWI Architecture “Initial System and Technical View”. 

Annex E: Specific Community of Interest. 

Annex F: Infrastructure Services. 

Annex G: Unified Communications Capability Services. 

Annex H: Client Provisioning Services. 

Annex I: Supplementary Services.



 

 

 

 

Annex J: Integration Test Service (ITS). 

Annex K: Documentation & Reports. 

Annex L: Nations & Partners. 

Annex M: Remote Sites. 





SECTION 3. HIGH LEVEL ANWI STRATEGIC 

REQUIREMENTS 

3.1 ANWI Business Benefits 

3.1-p1 ANWI will deliver a new modern standards based compliant and futureproof 

infrastructure providing sustainable business effectiveness for the New NATO 

Headquarters. 

3.1-p2 ANWI will provide ITIL based services ensuring that the NNHQ deliverables 

can align with and adapt to evolving NATO HQ business requirements and new 

transformational ways of working, 

3.1-p3 The ANWI project will deliver cost effective and flexible service based 

solutions providing improved performance while concurrently reducing the overall 

operational cost of the headquarters’ ICT; and 

3.1-p4 ANWI will help NATO achieve its strategic interoperability goals by having 

the NNHQ seamlessly connect to the NATO Command Structure’s Wide Area 

Networks and the greater NATO enterprise to easily share both information and 

services. 

3.2 Overall NNHQ Programme Structure 

3.2-p1 To support the delivery of NATO’s business benefits, NATO created a 

program structure that has defined and manages the expectations for the NNHQ; 

outlined the management structure for the NNHQ project programme; generated 

programme guidance and processes; and has delegated decision-rights to specific 

areas of NNHQ responsibility. 

3.2-p2 The applicable constituent parts relating to the NNHQ Programme structure 

are: 

A. The Deputy Permanent Representative Committee (DPRC) is the funding 

authority for the NNHQ programme structure. 

B. The NATO Headquarters Programme Office (HQPO), subordinate to the 

DPRC, represents the NNHQ users and is accountablefor ensuring the 

delivery of the user requirements and serves as the overall NNHQ 

integration Authority. 

C. Subordinate to the HQPO are the Purchaser and two Host Nations 

(Belgium and ICTM) which have the responsibility to deliver various 

elements of the NNHQ project. 

D. NCIA serves as the ANWI Implementation Authority with specific 

responsibility for the design, procurement and implementation of the ANWI 

as well as providing the Integration and Test Service (ITS). 

3.2-p3 As such, any changes to the ANWI (architecture, design, concepts or 

solution) shall be managed by the Implementation Authority, NCIA . 




3.3 High Level ANWI Strategic Principles 


3.3-p1 The NNHQ’s requires a cost effective, modern and innovative ANWI 

solution in order to satisfy NATO’s business benefits. 

3.3-p2 NATO provides its architectural requirements in Annex C and D which the 

ANWI Contractor shall use to support the ANWI design process. 

3.3-p3 The ANWI solution shall embrace the following strategic high level 

principles (they are fully described in the ANWI architecture, Annex C): 

A. Security 

B. Scalability 

C. Commercial Off The Shelf 

E. Reliability, Resilience and Robustness 

F. Flexibility 

G. Management of Facilities Services 

H. Future proof 

I. State-of-the-art Technology 

J. Interoperability 

K. Safety 

L. User Experience 

3.4 NNHQ Users 

3.4-p1 The NNHQ will be a large campus supporting many types of users, with 

varying needs, spread across the NNHQ’s security domains and across a number of 

buildings on and off campus. 

3.4-p2 Understanding and providing for these users’ needs are critical to the 

success of the ANWI implementation and realisation of the NATO business benefit. 

3.4-p3 There are fourteen (14) main types of users that shall be supported; these 

users are identified here and described in the Architecture annex (C): 

A. NATO HQ User 

B. NATO HQ Nation User 

C. NATO HQ Partner User 

D. Conference User 

E. NATO HQ Conference User 

F. NATO HQ Event User (peak) 

G. NATO HQ Mobile User 

H. NATO HQ Remote User 

I. Public User 

J. NATO Remote Office User 

K. NATO HQ System Administrator User 

L. Non-NATO Troop Contributing Nation (NNTCN) User 

M. Non-NATO Nation (7NNN) User 

N. Non-Personal Entity (NPE) User 



3.5 Security Domains 



3.5-p1 To more easily support the various types of users, NATO has identified four 

(4) security domains where these users will operate. 

3.5-p2 Currently, NATO HQ has numerous local area networks on its campus and 

the HQ is currently undergoing consolidation exercises to reduce the number of 

supported LANs into the four (4) security domains identified in paragraph 2.3.3-p7. 

3.5-p3 These security domains shall support information services up to the 

security classification stipulated in the table below: 

Security Domain Name 

NS 

EAPC 

Business 

Public 

Configured to Support a Security Classification up to 

NATO SECRET 

EAPC SECRET 

NATO RESTRICTED 

NATO UNCLASSIFIED Releasable to the Internet 

Table 3.1: ANWI security domains and the maximum security classifications of the 

data that can be stored on the domain 

3.5-p4 The ANWI Project shall design, deliver, integrate and implement the 

hardware and software to implement these NNHQ’s four (4) security domains in the 

NNHQ. 

A. These networks domains shall be provided to those offices, conference 

rooms, and out buildings across the NNHQ campus as well as providing 

remote access to support the distribution of users based on their security 

access needs (see Annex B: PFE for the distribution of users by domain). 

B. NATO external communications and IP services will enter the NNHQ via 

four communications rooms, two for military communications and two for 

commercial communications, where the non-availability of either a military 

or commercial communications room shall not render any of the ANWI 

military or commercial communication services unavailable. 

C. The ANWI Contractor shall provide a domain’s services in a manner, such 

that a network service shall be available to users even if either of NNHQ’s 

two (2) server rooms is not operational. 

3.6 High Availability 

3.6-p1 The ANWI design and implementation shall provide a load balanced 

infrastructure with automatic failover of a server room to the other server room 

without loss of data and minimal delay. 

3.6-p2 The ANWI design and implementation shall provide a load balanced 

infrastructure with automatic failover of its services from one server room to the other 

server room’s services without loss of data and minimal delay. 





3.6-p3 The ANWI Contractor shall support the NATO HQ recovery plan if both 

NNHQ server rooms fail: 

A. The NATO HQ currently uses an alternate facility as its disaster site where 

key NATO HQ staff can operate with reduced ICT capabilities. 

B. The NNHQ will reuse this capability to host the replication of critical ANWI 

services. 

3.6-p4 The ANWI Contractor shall provide data routing from the NNHQ to the 

alternate site ensuring that the replicated critical business data and services are 

available for use in case of disaster. 

3.7 Life-Cycle and Innovation 

3.7.1 Life-Cycle 

3.7.1-p1 The ANWI Contractor shall ensure that all delivered processes follow a 

life cycle process where service improvements are fed back into the requirements 

and processed through a design adjustment and transition for implementation and 

then ultimately supported 

ANWI Service 

Improvement 

ANWI 

Requirements 

ANWI Service 

and System 

Design 

ANWI 

Implementation 

and Transition 

ANWI Service 

and 

Operations 

. 

Figure 3.1 Life cycle process with improvement feedback loop 

3.7.1-p2 For the ANWI project, NATO considers the capability’s life-cycle an 

important part of delivery and requires that the NNHQ have the most modern COTS 

solutions (e.g. the latest version of a product that is proven to be mature from an 

engineering and operations and support perspective) at the time of delivery. 

A. The ANWI Contractor shall deliver the ANWI infrastructure services to 

accommodate the needed capacity and performance requirements without 

over providing infrastructure. 

B. ANWI hardware shall not be end-of-life or targeted for end-of-life (within 18 

months) at acceptance time. 

C. Delivered ANWI hardware configurations shall have the components 

available to expand the storage capacity, processing and memory 

according to the forecasted expansion requirements in Annex F. 





E. Due to the nature of the data, ANWI storage media (e.g. hard disk drives) 

cannot be returned to the OEM maintainer as part of any warranty; the 

Purchaser will destroy any bad or inoperable storage media. 

F. For those services selected to be NONO, the ANWI Contractor shall 

provide training for those services such that NATO trained 1st level 

support engineers can properly add cards to switches, memory and CPUs 

to servers, and disks to storage devices without invalidating the device’s 

hardware warranty. 

3.7.2 Innovation 

3.7.2-p1 The ANWI Contractor shall, as part of the design process, plan for 

innovation and technology updates. 

A. Prior to the Initial Operating Capability (IOC), it is highly probable that at 

least one major technology life cycle and several technological updates 

will occur for the hardware and/or software of ANWI components; 

therefore the ANWI Contractor shall suppport technology confirmation 

points to delivering antiquated hardware. 

B. A technology confirmation point is that point in time where the Purchaser 

and ANWI Contractor shall review the hardware configurations and agree 

that the Contractor shall update the technical hardware configuration(s) 

based on the new technology without increasing the overall cost of the end 

item. 

C. To provide up-to-date technology as part of this project, the ANWI 

Contractor shall address four (4) technology confirmation points defined 

below: 

1. As part of the design review prior to the ANWI Contractor’s ordering of 

the ITS hardware. 

2. After the infrastructure design and 30 days prior to switch and first 

iteration of server and storage purchase. 

3. 60 days prior to wireless Access Point delivery. 

4. 90 days prior to the purchase of user client devices. 

D. The ANWI Contractor shall propose the technology updates at the 

technology confirmation point. 

E. If the Purchaser agrees to the Contractor’s proposal, the Contractor shall 

adjust the hardware and/or software configuration, update the hardware 

and/or software, and update the configuration records. 

3.7.2-p2 The ANWI Contractor shall not deliver all ANWI hardware at the start of 

implementation 

3.7.2-p3 The ANWI Contractor shall support a service capacity paradigm where 

the Schedule of Supplies and Services’ hardware quantities identifies the upper limit 

which is available to support additional capability while being able to concurrently 

provide the new capacity, when needed. 





TB 

or 

CPU 

Typical 

Not yet used 

Desired 

In use & Provisioned 

2014 2015 2016 2020 

Enter 

Building 

IOC FOC FSA 

Time 

Figure 3.2 Phased delivery of ANWI capacity 

3.7.2-p4 Figure 3.2 graphically depicts the provisioning concept described 

above. Over the ANWI life cycle, it is believed that the identified (maximum) numbers 

of processing and storage should be delivered. The yellow ‘curve’ shows that NATO 

wants to deliver capacity based on need vice ‘big bang’ where there is a high 

probability that devices amy become obsolete before they are palced into operation. 

3.7.3 Capability to Service Evolution 

3.7.3-p1 The ANWI Contractor shall scope the ANWI system as a delivery of 

integrated services. 

3.7.3-p2 An ANWI service shall consist of capabilities and functions installed, 

configured by the ANWI Contractor and maintained by either the NATO O&M 

Authority staff or the ANWI Contractor. 

3.7.3-p3 The ANWI Contractor shall provide and maintain (throughout the 

contract’s life) a service catalogue of the ANWI services that NNHQ staff and 

delegations can consume or purchase. 

3.7.3-p4 The ANWI Contractor shall provide tools to support NATO users and 

NATO (Partner) Nation delegation billing/invoicing. 

3.7.3-p5 The ANWI Contractor shall deliver services per the SLAs defined in the 

ANWI contract. 

3.7.4 Service Level Management (SLM) 

3.7.4-p1 Services shall be provided in accordance with agreed Service Level 

Agreements (SLA). 







3.7.4-p2 The ANWI Contractor shall define, document and provide tools to 

monitor the SLAs for each ANWI provided service. 

3.7.4-p3 Within the NNHQ two (2) rooms have been allocated to serve as the 

Network Operations Centre (NOC). Either room shall be capable of monitoring, 

managing and controlling the statuses of services on any of the security domains. 

3.7.4-p4 The NOC shall be equipped with large screen displays (at least 50”) 

where the Service Management’s dashboard of ANWI Key Performance Indicators 

(KPIs) shall be monitored. 

3.7.4-p5 The NATO O&M Authority shall be given access to ANWI Service 

Management and Control (SMC) information to support NNHQ services, as needed. 

3.7.5 Service Provisioning Models 

3.7.5-p1 ANWI shall embrace three service provisioning models: NATO-Owned / 

NATO-Operated (NONO); NATO-Owned / Contractor Operated (NOCO); and 

Contractor-Owned / Contractor-Operated (COCO). 

3.7.5.1 NATO-Owned / NATO-Operated (NONO) 

3.7.5.1-p1 

maintenance. 

NATO will own the service’s hardware and be responsible for its 

3.7.5.1-p2 NATO will operate the service and provide 1st, 2nd and 3rd level 

support, as defined in Section 7. 

3.7.5.1-p3 

training. 

The ANWI Contractor shall provide NATO with operator/maintainer 

3.7.5.2 NATO-Owned / Contractor-Operated (NOCO) 

3.7.5.2-p1 NATO will own the hardware and the ANWI Contractor shall be 

responsible for its maintenance. 

3.7.5.2-p2 The ANWI Contractor shall operate the service and provide 1st, 2nd 

and 3rd level support, as defined in Section 7. 

3.7.5.2-p3 The ANWI Contractor shall provide the service level manager and 

all needed manpower to operate the service within the terms and conditions of the 

SLA. 

3.7.5.3 Contractor-Owned / Contractor-Operated (COCO) 

3.7.5.3-p1 The ANWI Contractor or a sub-Contractor shall own and manage 

the hardware and its life cycle (upgrades and technology refreshes). 

3.7.5.3-p2 The ANWI Contractor shall operate the service and provide 1st, 2nd 

and 3rd level support, as defined in Section 7. 

3.7.5.3-p3 The ANWI Contractor shall provide the service level manager and 

all needed manpower to operate the service within the terms and conditions of the 

SLA. 

3.7.5.3-p4 The ANWI GSM service shall be COCO requiring the provider to not 

only maintain and operate his commercial back-end network and service provisioning



but also the extension of any hardware and software provisioning onto the NNHQ 

campus due to weak GSM signal penetration throughout the NNHQ. 

3.7.5.3-p5 Any provisioning of equipment to extend the GSM signal on the 

NATO campus shall support all locally supported Belgian GSM providers without 

NATO users being charged roaming charges by virtue of the user entering the NNHQ 

building, as specified in Annex I Appendix 2. 

3.7.5.3-p6 

personal GSM. 

NATO or NATO visitors will own the end user’s SmartPhone/PDA or 

3.7.5.3-p7 The ANWI IPTV service, as COCO, shall address the provider’s 

back-end network and signal provisioning as well as the extension of any hardware 

and software on the NNHQ campus needed to support the distribution and 

dissemination of the television signal onto the NNHQ cabling infrastructure. 

3.7.5.3-p8 

Appendix 6. 

NATO will own the user’s IPTV device, as specified in Annex I 

3.7.6 Contractor ICT Support Following Acceptance 

3.7.6-p1 Implementing proper Service Level Management will facilitate NATO’s 

decision whether to in-source or out-source its ICT support. 

3.7.6-p2 The ANWI Contractor may serve as the 1 st , 2 nd and 3 rd level support 

Authority for the delivered ANWI services(see section 7 for support level 

descriptions). 

3.7.6-p3 The Purchaser will decide the final provisioning model of ANWI services 

(based on needed skills/expertise and security reasons) thus replacing NOCO with 

NONO and assuming the 1 st and 2 nd level support role. 

3.7.6-p4 External supplied services (IPTV and GSM) shall be made available 

and supported by their respective third party service provider while the ANWI 

Contractor shall ensure that these services are available throughout the NNHQ 

campus. 

3.7.6-p5 The ANWI Contractor shall provide the ANWI Printing and Scanning 

service in accordance with the COCO model. 

3.8 Design 

3.8-p1 The ANWI contract requires the implementation of components that are 

combined into services where the collective groupings of services provide the overall 

system on a single environment. 

3.8-p2 

below: 

A high level diagram of the NNHQ’s domains and connectivity is shown 





Figure 3.3 High-level diagram of the ANWI 

3.8-p3 The ANWI Contractor's design shall describe the provisioning, for each of 

the NNHQ’s 4 security domains. 

3.8-p4 The ANWI contractor's design shall provide resilience by automating the 

failover of each service from one server room to the other with no loss of data and 

minimal delay (per RPO and RTO times identified in annex F). 

3.8-p5 The ANWI Contractor’s service design shall describe the delivery of 

services, including the physical design as well as the processes and that will be used 

to achieve the overall service levels in accordance with the defined Service Level 

Targets (SLT) stipulated in this SOW. 

3.8-p6 The ANWI Contractor shall implement the following services on the 

appropriate security domain (for ease of understanding, the Business network has 

been decomposed into its constituent parts – NR and NU as some UNCLASSIFIED 

services are provided to the Business domain and the Business domain shall provide 

extranet applications that connect to the Internet). 

No. 

Security Domain (Up to Classification) 

NS EAPC Business Public 

Services NR NU 

1 SMC and Information Assurance Services 

1.1 Service Management and Control(SMC) Y Y 1 Y Y 1 

1.2 Information Assurance (IA) Y Y Y Y 

2 Infrastructure Services 

2.1 Processing Y Y Y Y 4 Y 





No. 




2.2 Storage Y Y Y Y 4 Y 

2.3 Printing & Scanning Y Y Y Y 

2.4 Network Infrastructure Y Y Y Y Y 

2.5a LAN (Wired) Y Y Y Y Y 2 

2.5b LAN (Wireless) 

3 UCC (Unified Communications & Collaboration Services 

3.1 Voice Y Y 3 Y 

3.2 Voicemail Y Y 

3.3 Video-Teleconferencing (VTC) Y Y 

3.4 E-mail Y Y Y 

3.5 Unified Messaging Y 

3.6 FAX Y Y 

3.7 Instant Messaging (IM)/chat Y Y 

3.8 Presence Y Y 

3.9 Directory Service Y Y Y 

3.10 Collaboration Y Y 

3.11 Mobility Y 

4 Client Provisioning Services 

4.1 Software provisioning Y Y Y Y 2 

4.2 Client devices Y Y Y Y 

5 Supplementary Services 

5.1 GSM n.a. 

5.2 GSM Blocking Y 7 

5.3 Wireless Blocking Y 7 

5.4 Site Security Communications (Radio) n.a. 

5.5 IPTV Y 3 Y 5 

Key: 1 limited Management capability; 2 Only for Kiosk PC’s; 3 Software Clients; 4 Extranet Applications & DB (DMZ) – Up to NU security domain only exists 

in the Data Centre.; 5 Shall cover both IPTV streaming and Browser accessible IPTV services; 6 No specific Business WLAN service – Mobile business 

clients shall use the Public WLan to establish secure (VPN) connection with Business security domain.; 7 Static GSM/WLAN Blocking capabilities shall be 

managed from the Business network. Mobile GSM/WLAN Blocking capabilities are not networked. 

Table 3.2: ANWI Services (security domain) mapping of service 

6 

Y 

3.8-p7 The table provides an overview of the services that shall be made available 

for each security domain. This table doesn’t provide details about the classification of 

the information handled by the services. 

3.8-p8 The ANWI design shall define how the ANWI services (described in the 

Annexes of this SOW) are combined to provide a coherent system for the NNHQ. 





3.8-p9 The ANWI approved design shall be achieved through a series of events 

and deliverables that include: 

A. Requirements review. 

B. Design briefing. 

C. Design document. 

E. Design review meeting. 

3.8-p10 The ANWI design process is detailed in SECTION 5. 

3.9 Interfacing with NATO Provided Services 

3.9-p1 An integral part of the ANWI requires interfacing with NATO provided 

services which are identified below. 

3.9.1.1 Host Nation Projects for NNHQ 

3.9.1.1-p1 Global Construction Contractor (GCC) is the New NATO 

Headquarters (NNHQ) Contractor responsible for delivering the building. The ANWI 

shall use the provided server rooms, communications rooms and technical 

equipment rooms while working within the allocated power and cooling constraints for 

those rooms (identified in Annex B). 

3.9.1.1-p2 Passive Network Infrastructure (PNWI) will be provided by the 

GCC and delivers cabling for voice, data and AV, and an active patching system that 

shall be used to deliver ANWI services from the server rooms to the user as identified 

in Annex B, paragraph 10.2.7. 

3.9.1.1-p3 Building Management System (BMS) will be provided by the GCC 

to monitor, manage and control the NNHQ’s building environment and facilities. The 

ANWI shall provide storage for the BMS data as identified in Annex B, paragraph 

10.3. 

3.9.1.1-p4 Electronic Security Systems (ESS) will be provided by a separate 

ESS contractor to provide capabilities for automated access control, visitor handling, 

CCTV and intruder detection systems, as well as Central Security Management and 

Control Services (CSMCS). The ANWI shall provide storage for the ESS data as 

identified in Annex B, paragraph 10.4. 

3.9.1.1-p5 Audio Visual Infrastructure (AVI) will be provided by a separate 

AVI contractor to provide the active and passive components that shall be used in the 

NNHQ’s conference rooms to deliver AV recording, electronic displays, audio 

systems, projectors and video streaming services. The ANWI shall provide storage 

for the AVI data as identified in Annex B, paragraph 10.5; and shall also make ANWI 

processing services available to support the AVI implementation. 

3.9.1.1-p6 Business Applications and Data Migration (BADM) is currently 

planned to be provided and migrated by EM/ICTM as identified in Annex B, 

paragraph 10.3. The ANWI Contractor shall provide AD, adjustment of security 

(settings) roles and software deployment support, based on the ITS results, to this 

activity as part of the ANWI 2 nd level implementation support. 




3.9.1.2 NCIA & NCIA Projects for NATO 


3.9.1.2-p1 NATO General [Purpose Segment] Communication System 

(NGCS): 

A. NGCS provides Wide Area Networking (WAN) access, interconnecting the 

NATO HQ to other NATO or NATO Nation organisations at the NS, NU or 

NR level. The ANWI shall connect to the NNHQ NGCS node providing the 

needed WAN access and is described in Annex B, paragraph 10.5.3. 

B. A small NGCS node will be installed in a second location to support the 

ITS and NNHQ back up communications for the NNHQ. 

3.9.1.2-p2 Public Internet Access (PIA): 

A. PIA provides connectivity to the Internet. 

B. The ANWI Contractor shall connect the ANWI’s Public domain to the PIA 

providing users managed Internet access. The PIA is described in Annex 

B, paragraph 10.6.6. 

3.9.1.2-p3 NATO Enterprise Directory Services (NEDS): 

A. NEDS provides enterprise level directory synchronisation services and is 

described in Annex B, paragraph 10.6.3. 

3.9.1.2-p4 NATO Public Key Infrastructure (NPKI): 

A. Provides all NPKI certificate services for the ANWI per NATO policy, and 

is described in Annex B, paragraph 10.6.5. 

3.9.1.2-p5 NATO Cyber Defence Incident Response Centre (NCIRC) Full 

Operational Capability (FOC): 

A. Provides Tier-3 NCIRC services and is described in Annex B, paragraph 

10.6.4. 

B. Provides Tier-1 Infrastructure (consisting of a few NR and NS 

workstations) and Threat Assessment Cell (2 NU and 2 NS laptops), 

considered as a Business Application, centrally managed by NCIRC. 

3.9.1.2-p6 NATO Messaging Service: 

A. Provides formal military messaging as a NATO enterprise service, 

specified in Annex B paragraph 10.6.8. 

3.9.1.2-p7 Active Directory AIS Single Forest Single Domain services, as 

provided by NATO O&M Authority, specified in Annex B paragraph 10.5.6. 

3.9.1.2-p8 Active Directory AIS based MS Exchange Services, specified in 

Annex B, paragraph 10.5.7. 

3.9.1.2-p9 AIS Enterprise Management Services (EMS), to support AIS 

based Configuration Management, Monitoring and Software Distribution Services, 

specified in Annex B paragraph 10.5.8. 

3.10 Implementation 

3.10.1 General 

3.10.1-p1 

The ANWI implementation shall deliver the active network services. 

3.10.1-p2 Implementation is specified in detail in SECTION 6. 

3.10.1-p3 

A high level discussion on implementation activities is addressed below. 



3.10.2 Site Survey 



3.10.2-p1 Prior to the implementation the ANWI Contractor shall conduct a site 

survey in all relevant NNHQ locations (server rooms, TERs and communications 

rooms) to include the current building’s premises. 

3.10.2-p2 The ANWI Contract is based on the requirement for the procurement 

and implementation of all new equipment. 

3.10.2-p3 The ANWI Contractor shall identify the potential reuse of any existing 

NATO HQ equipment during the site survey. 

3.10.2-p4 Site survey requirements are provided in paragraph 6.5.2.2. 

3.10.3 Installation 

3.10.3-p1 

6.6. 

Delivery of equipment on site shall be in accordance with the paragraph 

3.10.3-p2 The ANWI Contractor shall implement the approved design in 

accordance to the agreed configurations, specified schedules and security 

constraints on each security domain. 

3.10.4 Migration and Interoperability 

3.10.4-p1 The ANWI Contractor shall migrate the NNHQ ICT environment in 

accordance with the HQPO NNHQ ICT migration strategy (ref 1.1.1.7.5). 

3.10.4-p2 Detailed requirements for the migration are found in paragraph 6.11.10. 

3.10.4-p3 During the migration period, the ANWI Contractor shall maintain and 

operate the ANWI environment according to the more detailed requirements in 

paragraphs 5.3.4-p4 and 5.6-p4 and ensure it interoperates with the current HQ 

environment. 

3.10.5 Service Provisioning 

3.10.5.1 Infrastructure Services 

3.10.5.1-p1 The Infrastructure Services provisioning shall provide network 

infrastructure, processing, storage and those capabilities typically supporting network 

access, DNS, printing and scanning for each of the security domains as well as the 

Local Area Networking component (wired and wireless). 

3.10.5.1-p2 This service also addresses cross-domain gateway capabilities that 

shall support the movement of data between the various security domains. 

3.10.5.1-p3 These sub-services are identified below and described in the 

indicated sections of this SOW: 

Annex F Appendix 2. 











3.10.5.1-p4 LAN connectivity for fixed desktops and servers will be via fibre 

optic cables; see Annex B for PNWI cable information. Cabling design details are 

provided as PFE under the Passive Network Infrastructure (PNWI) portion of the 

main building construction contract. 

3.10.5.1-p5 LAN connectivity supporting the switching infrastructure that 

interconnects server rooms and technical equipment rooms (TER, which will host 

ANWI switches and patch panels) will be via fibre optic cables as described in Annex 

B PNWI cable information. 

3.10.5.2 Unified Communications and Collaboration (UCC) Services 

3.10.5.2-p1 UCC shall provide the user the opportunity to integrate voice and 

email and other functions that support collaboration. 

3.10.5.2-p2 These sub-services are identified below and described in the 

indicated sections of this SOW: 

Annex G Appendix 2. 











3.10.5.3 Client Provisioning Services 

3.10.5.3-p1 Client Provisioning Services provide end-user devices to the staff in 

NNHQ offices, out-site buildings and conference rooms. 

3.10.5.3-p2 The ANWI shall provide a variety of end user devices from the 

standard desktop to the small footprint mobile device. 

3.10.5.3-p3 The Client Provisioning Services are identified below and described 

in the appropriate location: 

Annex H Appendix 2. 

Annex H Appendix 3. 

3.10.5.4 Supplementary Services 

3.10.5.4-p1 NNHQ supplementary services shall be provided to NATO using all 

three of the service models. 

3.10.5.4-p2 These services are identified below and described in the indicated 

sections of this SOW: 

Annex I Appendix 2 GSM as COCO. 

Annex I Appendix 3 GSM blocking as NOCO. 

Annex I Appendix 4 Wireless blocking as NOCO.



 

 

Annex I Appendix 5 TETRA (initially) as NONO. 

Annex I Appendix 6 IPTV as COCO. 

3.10.5.5 SMC and IA Services 

3.10.5.5-p1 

services 

The SCOI shall provide services that cross and interface with all 

3.10.5.5-p2 These services are identified below and described in the indicated 

sections of this SOW: 

Annex E Appendix 1. 

Annex E Appendix 2. 

3.10.5.5-p3 Annex E Appendix 2 also addresses cross-domain gateway 

capabilities that shall support the movement of data between the various security 

domains. 

3.10.6 Training 

3.10.6-p1 The ANWI Contractor shall provide SysAdmin level training (per 

paragraph 6.10.9) for those services selected to be NONO. 

3.10.6-p2 The ANWI Contractor shall provide user training for UCC and 

Print/Scan services, as addressed in their respective annexes. 

3.10.6-p3 The specific training requirements are defined in the respective 

service’s area as shown below. 

Service Requiring Training 

SMC 



Location 


Information Assurance Annex E Appendix 2 

Infrastructure Services 

Storage (Capacity) Service Annex F Appendix 3 

Print/Scan Service Annex F Appendix 4 

LAN Services Annex F Appendix 6 

Unified Communications Capability Services 

Voice Service Annex G Appendix 2 

Voicemail Service Annex G Appendix 3 

Video Tele-Conferencing (VTC) Annex G Appendix 4 

E-Mail Service Component Annex G Appendix 5 

Unified Messaging Annex G Appendix 6 

FAX Service Component Annex G Appendix 7 

Instant Messaging/Chat Annex G Appendix 8 

Presence Annex G Appendix 9 

Directory Service Component Annex G Appendix 10 

Collaboration (Whiteboard) Annex G Appendix 11 

Client Provisioning Services 

Software provisioning Annex H Appendix 2 

Client Devices Annex H Appendix 3



Service Requiring Training 

Location 

Supplementary Services 

GSM Annex I Appendix 2 

GSM Blocking Service Annex I Appendix 3 

Wireless Blocking Service Annex I Appendix 4 

Security Communications (radio) Annex I Appendix 5 

IPTV Annex I Appendix 6 

Table3.3: Service training 

3.10.7 Testing & Acceptance 

3.10.7-p1 Testing shall be conducted in accordance with the Test and Acceptance 

Plan (TAP) defined in Annex K. 

3.10.7-p2 Every component shall be tested based on the approved design 

document ensuring that the service meets the Service Level Requirements and 

Targets defined in the SOW’s Annexes. 

3.10.7-p3 The bundling of the components shall then be tested as a service, 

described in the Annexes of this SOW. 

3.10.7-p4 Acceptance shall be achieved in three (3) increments: 

A. Initial Operating Capability (IOC) requirements are described in paragraph 

6.14. 

B. Final Operating Capability (FOC) requirements are described in paragraph 

6.16. 

C. Final System Acceptance (FSA) requirements are described in paragraph 

6.17. 

3.10.8 Support 

3.10.8.1 Migration/Transfer 

3.10.8.1-p1 The ANWI contractor shall migrate all ANWI related services and 

data (e.g. e-mail, windows shares) from the current to the new building and with 

minimum planned disruptions. 

3.10.8.1-p2 A NATO Contractor will install the NATO HQ business applications 

onto the ANWI infrastructure. 

3.10.8.1-p3 The ANWI Contractor shall support the NATO Contractor with any 

required NNHQ server and SAN configurations and ITS testing. 

3.10.8.1-p4 An adjustment to a server configuration (identified in the ITS) will be 

proposed and requested by the NATO Contractor then screened, and/or processed 

and approved by NOS, prior to implementation on the ANWI hardware. 

3.10.8.1-p5 The ANWI Contractor shall be available during NATO Contractor’s 

migration/transfer of the HQs legacy data onto the ANWI provided infrastructure to 

support permission/access right configurations. 





3.10.8.1-p6 The ANWI Contractor shall provide Domain Name System (DNS), 

Active Directory (AD) support and capacity allocation as described in Annex F: 

Infrastructure Services. 

3.10.8.2 Service Desk 

3.10.8.2-p1 As soon as IOC is achieved for the first security domain the ANWI 

Contractor shall provide the NNHQ Service Desk with technical staff supporting the 

implemented capabilities and services. 

3.10.8.2-p2 

The Service Desk augmentation support shall continue to FSA. 

3.10.8.3 Post FOC to FSA support 

3.10.8.3-p1 This support shall commence immediately after successfully 

achieving FOC and last for 6 months. 

3.10.8.3-p2 The ANWI Contractor staff shall support the tuning of the 

implemented services based on the SLA’s Key Performance Indicator (KPI) statistics 

during this period. 

3.10.8.3-p3 The ANWI Contractor shall support the troubleshooting of ANWI 

implemented user –service issues and advise the NATO O&M Authority staff on 

back-end support issues for NNHQ NONO services. 

3.10.9 Total Cost of Ownership (TCO) Assessment 

3.10.9-p1 The ANWI Contractor shall recommend for each service the number 

and skill set of staff needed to support the service for NATO consideration as part of 

the NOCO (outsourcing) service model. 

3.11 Integration and Testing Services 

3.11-p1 The ANWI shall provide Integration and Testing Services; the requirements 

for this are found at Annex J: Integration and Testing Services. 

3.11-p2 The infrastructure for Integration and Testing Services shall be installed in 

Bâtiment Z. 

3.12 Nations and Partners 

3.12-p1 National delegations shall be provided an agreed baseline set of client 

devices as reflected in Annex L: Nations and Partners. 

3.12-p2 Nations and NATO partners located in the NNHQ will be given the 

opportunity to use this contract to order user devices and ANWI services. 





SECTION 4. 

PROJECT MANAGEMENT 

4.1 Introduction 

4.1-p1 This section outlines the Project Management requirements for the 

NNHQ ANWI Contract. 

4.1-p2 The NNHQ ANWI is a complex system, and designing, coordinating, 

implementing, integrating, and supporting it will be a significant project management 

challenge where its success depends upon the implementation and use of a sound 

project management approach. 

4.2 Organisation 

4.2.1 Purchaser Project Organisation and Responsibilities 

4.2.1-p1 The Purchaser’s Project Manager serves as the Purchaser’s 

representative and will be the primary interface between the ANWI Contractor and 

Purchaser after the Effective Date of Contract (EDC). 

4.2.1-p2 The Purchaser Project Manager is supported by the NCIA Project team 

consisting of specialists in certain areas who may be delegated to act on the Project 

Manager’s behalf in their respective area of expertise. 

4.2.1-p3 The Purchaser hascreated an ANWI Project Board, in accordance with 

the PRINCE2 methodology, consisting of the Purchaser’s Project Manager (Project 

Board Executive), HQPO (Senior User),and Purchaser’s Contracting Officer (Senior 

Supplier). 

4.2.1-p4 After Contract Award, the Purchaser will add the ANWI Contractor 

(Senior Supplier)and the ANWI Independent Verification and Validation (IV&V, 

Assurance). 

4.2.1-p5 

The Project Boards will meet monthly at the Purchaser’s facility.. 

4.2.1-p6 Neither the Purchaser’s Project Manager nor any other NATO 

personnel may make changes to the terms and conditions of the Contract; they will 

only provide the Purchaser’s interpretation of technical matters. All obligations and 

changes to the Contract will only be made through the Purchaser’s contracting office. 

4.2.2 ANWI Contractor Project Management Office 

4.2.2-p1 Once the implementation starts, the ANWI Contractor shall establish 

and maintain a Project Management Office (PMO) in the Brussels, Belgium area to 

perform and manage all efforts necessary to discharge the responsibilities under this 

Contract. 

4.2.2-p2 The ANWI Contractor shall ensure the continuity of personnel assigned 

to work on this project. 







4.2.2-p3 The following ANWI Contractor staff shall be identified as key 

personnel: 

A. ANWI Project Manager (PM). 

B. ANWI Technical Lead (TL). 

C. ANWI Test Director (TD). 

4.2.2-p4 The ANWI Contractor shall ensure the continuity of these key positions 

throughout the contract. 

4.2.2-p5 The ANWI PM shall be the ANWI Contractor’s primary interface to the 

Purchaser’s Project Manager. 

4.2.2-p6 

The ANWI TL may also serve as the ANWI site installation manager. 

4.2.2-p7 The ANWI TD shall be responsible for the ANWI Contractor provided 

Integration Test Service (ITS) and responsible for all ANWI testing as well as 

reporting oversight of all NNHQ Host Nation related test activities conducted in either 

the ITS or NNHQ. 

4.2.2-p8 

The ANWI TD shall oversee the management and operation of the ITS. 

4.2.2-p9 The ANWI Contractor shall provide all necessary manpower and 

resources to manage, design, implement and support the ANWI, 

4.2.2-p10 The Purchaser shall review and approve appointments of Contractor 

key personnel, including allowable substitutions need review and approval from the 

Purchaser. 

4.2.2-p11 The ANWI Contractor personnel that need to work on-site shall have at 

least NATO SECRET clearances by the time their respective duty or assigned task 

starts. 

4.2.3 ANWI Project Manager (PM) 

4.2.3-p1 The ANWI Contractor shall designate an ANWI Project Manager (PM), 

who will direct and co-ordinate the activities of the Contractor’s project team. 

4.2.3-p2 The ANWI Project Manager shall, as part of his other duties, conduct all 

major project design, test, and review meetings. 

4.2.3-p3 The ANWI PM shall have a University Degree in Electronic Engineering, 

Computer Science, Telecommunications, or related discipline, preferably equivalent 

to a Master’s, supported by relevant certificates/ diplomas. Exceptionally, extensive 

relevant experience may be considered if the above qualifications are not met. 

4.2.3-p4 The ANWI PM shall have a current Project Management (PRINCE2 

Practitioner and/or PMI Project Management Professional (PMP 1 )) certification. 

4.2.3-p5 The ANWI PM shall have a minimum of ten (10) years’ experience as 

an ICT Project Manager as supported by project references, points of contact, and 

descriptions/scope of the projects managed. 

4.2.3-p6 The ANWI PM shall have a minimum experience of five (5) years 

gained within ICT procurement, implementation, migration and management in 

projects similar to the ANWI Project, as supported by project references, points of 

contact, and description of role/responsibilities/activities executed.





4.2.3-p7 The ANWI PM shall have a minimum of one (1) years’ experience in 

ICT QA activities as well as knowledge and experience with QA standards (either 

AQAP or ISO), supported by project references, points of contact, and description of 


4.2.3-p8 The ANWI PM shall have knowledge and experience with processes for 

integration and testing. 

4.2.3-p9 The ANWI PM shall have minimum of two (2) years’ experience in 

projects where ICT migration/transition was exercised in a managerial role 

responsible for the planning, designing and execution of migration/transition 

activities, as supported by project references, points of contact, and descriptions of 

the role/responsibilities/activities executed. 

4.2.3-p10 The ANWI PM shall have a demonstrated spoken and written fluency in 

English, at a minimum level of 4343 as defined in STANAG 6001. 

4.2.4 ANWI Technical Lead (TL) 

4.2.4-p1 The Technical Lead shall lead the analysis, design, development, 

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

4.2.4-p2 The ANWI TL shall have a University Degree in Electronic Engineering, 


to a Master’s, supported by relevant certificates/ diplomas. Exceptionally, extensive 

relevant experience may be considered if the above qualifications are not met. 

4.2.4-p3 The ANWI TL shall have demonstrated practical experience in 

Infrastructure (processing, virtualisation, storage, switches), supported by valid 

certification of at least the following areas: Microsoft (MCSE), CISCO (CCDP) or valid 

comparable (products used in the ANWI design) certification. 

4.2.4-p4 The ANWI TL shall have a minimum of two (2) years’ experience 

designing and implementing high-availability server rooms as supported by project 

references, points of contact, and technical descriptions of the projects implemented. 

4.2.4-p5 The ANWI TL shall have a minimum of three (3) years’ experience 

designing and implementing local area networks in projects similar to the ANWI 

Project demonstrating a strong network infrastructure and network service focus with 

good knowledge of Information Assurance and provisioning of core applications, as 

supported by project references, points of contact, and description of 

role/responsibilities/activities held in these projects. 

4.2.4-p6 The ANWI TL shall have a minimum of two (2) years’ experience as a 

technical manager responsible for the planning, designing and execution of projects 

where an Active Directory and subsequent application and data migration/transition 

activities were exercised; as supported by project references, points of contact, and 

technical description of the role/responsibilities/activities during this time. 

4.2.4-p7 The ANWI TL shall have a minimum of one (1) years’ experience in 

undertaking ICT QA activities, supported by supported by project references, point of 

contact, and description of role/responsibilities/activities. 

4.2.4-p8 The ANWI TL shall have knowledge and experience with QA standards 

(either AQAP or ISO), processes for integration and (pre) migration testing.



4.2.4-p9 The ANWI TL shall have a minimum of three (3) years’ experience as a 

team leader or project manager to ensure the technical management oversight of a: 

LAN designer, Server Room designer, UCC designer, communications engineer and 

systems integrator; as supported by project references, points of contact, and 

technical description of the role/responsibilities/activities. 

4.2.4-p10 The ANWI TL shall have an up to date ITIL v3 Intermediate Level 

Certification having earned at least 12 points in the Service Capability area. 

4.2.4-p11 The ANWI TL shall have a demonstrated spoken and written fluency in 

English, at a minimum level of 4343 as defined in STANAG 6001. 

4.2.5 ANWI Test Director (TD) 

4.2.5-p1 The ANWI TD shall have a University Degree in Electronic Engineering, 


to a Master’s and supplemented by relevant postgraduate qualifications, supported 

by relevant certificates/ diplomas. Exceptionally extensive relevant experience may 

be considered if the above qualifications are not met. 

4.2.5-p2 The ANWI TD shall have integration and testing engineering skills with 

five (5) years’ experience as part of large ICT projects, supported by project 

references, point of contact, and description of role/responsibilities/activities. 

4.2.5-p3 The ANWI TD shall have demonstrated practical experience in 

planning, conducting and assessing Integration and Testing activities in support of 

large ICT projects for at least three (3) years, supported by project references, point 

of contact, and description of role/responsibilities/activities. 

4.2.5-p4 The ANWI TD shall have demonstrated practical experience in testing 

of IT infrastructure, core services where the role of test engineer or integration 

engineer was exercised, supported by project references, point of contact, and 

description of role/responsibilities/activities. 

4.2.5-p5 The ANWI TD shall have demonstrated practical experience in ICT 

migrations where the role of test engineer or integration engineer was exercised for 

migration of ICT services (Active Directory, business applications and associated 

data), supported by project references, point of contact, and description of 


4.2.5-p6 The ANWI TD shall have demonstrated practical knowledge and 

experience with QA standards (either AQAP or ISO), processes for integration and 

(pre) migration testing. 

4.2.5-p7 The ANWI TD shall have a demonstrated spoken and written fluency in 

English, as defined in STANAG 6001 at a minimum level of 4343. 



4.2.6 Key Supporting Staff 



4.2.6-p1 The following support staff are deemed essential to the ANWI project 

but shall not be identified as key personnel and thus do not require the Purchaser’s 

approval. 

A. ANWI Quality Assurance Manager: the ANWI Contractor shall designate 

a qualified individual to serve as the Quality Assurance Manager for 

activities under this contract. Quality Assurance Manager shall have a 

demonstrated spoken and written fluency in English at a level of 4343, as 

defined in STANAG 6001 

B. Site Implementation and Support Manager: the ANWI Contractor shall 

designate a qualified and experienced individual to serve as the lead for 

site implementation and operational support of the ANWI Service Desk 

throughout the performance of the contract. The Site Implementation and 

Support Manager shall have a demonstrated spoken and written fluency in 

English at a level of 4343, as defined in STANAG 6001. 

C. ANWI Trainers: the ANWI Contractor shall identify qualified individuals 

with at least 2 years proven instructor experience to serve as the trainers 

supporting the contract. Trainers shall have a demonstrated spoken and 

written fluency in English at a level of 4444, as defined in STANAG 6001. 

D. ANWI Security Accreditation Manager. The ANWI contractor shall 

designate a suitably qualified individual to act as the security accreditation 

point of contact, responsible for all elements of production of the ADS 

inputs and to act as the central POC with the Authority on security-related 

matters in respect of the ANWI solutions, including attendance at NATO 

security accreditation meetings, as required 

4.3 Project Management Documentation 

4.3-p1 The ANWI Project Management documentation and plans are required 

to be regularly updated and as such shall be configuration controlled. 

4.3-p2 The ANWI Project Management documentation shall define all the 

aspects of how the ANWI project shall be managed and executed. 

4.3-p3 The ANWI Project Management documentation shall be posted on the 

ANWI project website. 

4.3-p4 The list of ANWI Project Management documentation is identified here 

and fully described in the documentation annex (Annex K): 

Project Management Plan (PMP) 

Project Implementation Plan (PIP) 

Migration Plan (MP) 

Risk Management Plan (RMP) 

Quality Assurance Plan (QAP) 

Test & Acceptance Plan (TAP) 

Integrated Logistics Support Plan (ILSP) 

Configuration Management Plan (CMP) 



4.4 Project Controls 

4.4.1 Stages and Transition 



4.4.1-p1 The ANWI Contractor shall follow the project methodology of the ANWI 

PM’s current project management certification (if the PM holds more than one, the 

ANWI Contractor is at liberty to choose between the methodologies). 

4.4.1-p2 The ANWI Contractor shall identify and describe the ANWI phases of 

the project and the stages within a phase, such that the ANWI stages align with both 

the ITILv3 life cycle and project methodology (the diagram is meant to only provide a 

visual idea of the requirement). 

IOC 

FOC 

FSA 

Design 

Phase 

Transition 

Phase 

Support 

Phase 

Improve 

Phase 

Stage 1 Stage 2 Stage 3 Stage 4 




IOC 

FOC 

FSA 

Figure 4.1 Conceptual view of stage and phase relations 





Design 

Phase 

Transition 

Phase 

Support 

Phase 

Improve 

Phase 

Preliminary Design Review (PDR) 

System Requirements Review (SRR) 

Critical Design Review (CDR) 

Security Risk Assessment (SRA) 

Security Documentation 

ITS implementation 

Site Survey 

Shipping 

Testing & ‘accreditation’ 

Installation & baseline 

Training 

Migration 

IOC, FOC, FSA 

Support Desk 

Service Management & Control 

Monitoring, reporting, auditing 

CMDB 

Service Catalogue 

SLA/SLT reviews 

PKI monitoring, reporting, 

auditing 

1. ITS, CDGW, Switching, 

processing, storage 

2. Service Management & 

Control 

3. UCC & Client Provisioning 

4. GSM & Secure 

Communications 

Figure 4.2 Conceptual Stage Activities and Design Decomposition 

4.4.1-p3 The ANWI Contractor shall ensure that the stages and phases are 

properly reflected in the PIP / Work Breakdown Structure (WBS). 

4.4.1-p4 The ANWI Contractor shall identify the triggers that are to be used to 

request a move between stage and phases. 

4.4.2 Change Management 

4.4.2-p1 The ANWI Contractor shall implement a change management approach 

and process,based on the requirements defined in paragraph 6.3, to be used 

throughout the ANWI project. 

4.4.2-p2 The ANWI Contractor is responsible for executing the change 

management process for each change request. 

4.4.2-p3 The ANWI Contractor’s change management process shall address 

submitting, reviewing, vetting, managing, and communicating change requests. 

4.4.2-p4 The ANWI Contractor shall log all submitted change requests, 

throughout the project’s lifecycle, in a change request register. 

4.4.2-p5 The ANWI Contractor’s change management process shall ensure that 

ANWI change requests are processed according to the defined process and CAB 

decisions reviewed at project meetings. 



4.4.3 Change Requests 



4.4.3-p1 The ANWI Contractor shall establish and maintain a process for 

identifying, reviewing, approving, and tracking all requests for changes to NNHQ 

ANWI baselines. 

4.4.3-p2 As described in ACMP-3, Change Requests shall be categorised as 

follows: 

A. Class 1 Change Requests affect the documentation and baselines 

managed by the Purchaser’s NNHQ ANWI Configuration Control Board. 

B. Class 2 Change Requests affect the baseline managed by the ANWI 

Contractor’s Configuration Control Board and can be approved without 

Purchaser review. 

4.4.4 Off-Specifications 

4.4.4-p1 The ANWI Contractor shall establish and maintain a process for 

reporting, tracking, and resolving Off-specifications on all baselines through Offspecification 

Reports (OSR). 

4.4.4-p2 Off-specification Reports (OSR), which document problems/issues with 

the design, configuration, implementation, or operation of NNHQ ANWI, shall be 

included in the ANWI Contractor’s Issue Management Plan and are distinguished 

from Change Requests, which identify proposed changes to the Functional, 

Developmental, or Product Baselines. 

4.4.4-p3 OSR shall be closed when the identified problem/issue is resolved 

through procedure or other action that does not affect the system baselines, or when 

a corresponding Change Request is opened to correct the Off-specification through a 

change to a baseline. 

4.4.4-p4 All OSR shall be assembled in an Off-specifications Documentand 

tracked in the Issue Management Plan’s issue register. 

4.5 Project-Level Communications 

4.5.1 General 

4.5.1-p1 

4.5.1-p2 

The Purchaser or his designated representative will chair all meetings. 

The ANWI Contractor shall schedule project meetings in the PIP. 

4.5.1-p3 The ANWI Contractor shall produce a draft agenda for the Purchaser’s 

approval at least one week before the meeting. 

4.5.2 Formal Meetings 

4.5.2.1 General 

4.5.2.1-p1 The ANWI PM shall participate in all formal ANWI project meetings 

(kick-off meeting, Project Progress Review Meetings and Design Review meetings,). 

4.5.2.1-p2 

Reserved 





4.5.2.1-p3 The following provisions shall apply to all formal meetings to be held 

under the contract. 

A. The ANWI Contractor shall take meeting notes (capturing main points, 

decisions and action items)and submit them in draft version to the 

Purchaser for approval within 3 working days after the meeting. 

B. The final version of the meeting notes shall be posted on the Project 

Website within 3 working days of receipt of Purchaser approval. 

C. 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. 

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

Purchaser in preparing for Design or Project Progress Review Meetings 

and ensuring efficient discussions during the meetings shall be provided to 

the Purchaser no later than five (5) working days before the meeting. 

4.5.2.2 Kick Off Meeting (1 st PPRM) 

4.5.2.2-p1 

facility. 

The ANW Contractor shall host the project Kick Off meeting at his 

4.5.2.2-p2 The ANWI Contractor shall hold the Kick Off Meeting not later than 

3 weeks after EDC. 

4.5.2.2-p3 The ANWI Contractor shall address the following items: 

A. Project description 

B. Project plan (PMP and PIP) 

C. Project goals & objectives of the ANWI deliverables 

D. Project assumptions and dependencies 

E. Project Management process overview 

F. Introduction of the teams and roles 

G. Communications plan and meetings 

H. Risks 

4.5.2.3 Project Progress Review Meetings (PPRMs) 

4.5.2.3-p1 PPRMs shall be held quarterly in turn at the Purchaser’s and at the 

Contractor’s facilities until the start of the NNHQ server rooms’ installation. 

4.5.2.3-p2 From the start of the server room installation, PPRMs shall be held 

monthly on the NNHQ campus. 

4.5.2.3-p3 

4.5.2.4 Other Meetings 

The PPRMs shall follow the requirements specified in Annex K 

4.5.2.4-p1 The Purchaser or ANWI Contractor will alternate hosting allother 

meetings as agreed by both parties 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. 

4.5.2.4-p2 Upon approval by the Purchaser’s PM, the ANWI Contractor shall 

schedule, organise, and conduct such meetings. 



4.5.3 Informal Meetings 


4.5.3-p1 The ANWI Contractor shall carry out ad-hoc project-level 

communication activities as needed to clarify project issues. 




4.5.3-p2 The Purchaser and ANWI PM shall hold fortnightly contact from the 

Kick off meeting through the remaining contractual period. 

4.5.3-p3 The parties will agree on a day (e.g. Tuesday) and time for the regular 

conference calls. 

4.5.3-p4 The Purchaser and ANWI Contractor shall exchange contact telephone 

numbers and agree on conference call requirements (day and time) during the 

project kick-off meeting. 

4.5.3-p5 Action Items from the conference calls shall be drafted by the ANWI 

Contractor and added to the ANWI Action Item List by the ANWI Contractor within 2 

days of the conference call. 

4.5.3-p6 The ANWI Contractor and Purchaser shall have weekly on-site status 

meetings once Implementation and Transition starts in order to quickly remedy any 

issues dealing with Implementation and Transition. 

4.5.4 Project Status Reports 

4.5.4-p1 The ANWI Contractor shall provide monthly Project Status Reports until 

the start of the NNHQ server rooms’ installation; thereafter shall be replaced by the 

monthly PPRM. The PPRMs shall follow the requirements specified in Annex K. 

4.5.5 Project Web Space 

4.5.5-p1 The ANWI Contractor shall use the Internet based project workspace 

provided and defined by the Purchaser as the project’s website. 

A. The Purchaser will serve as the website’s System Administrator. 

B. The ANWI Contractor shall serve as the content manager for the project’s 

workspaces. The ANWI IV&V Contractor shall have access to all part of 

the project’s web site. 

C. The ANWI Contractor shall be issued permissions to post all relevant 

NATO UNCLASSIFIED ANWI project documentation and datasets. 

D. Handling NATO Restricted Information 

1. The ANWI Contractor shall provide any NATO RESTRCTED (NR) to 

the Purchaser for posting on the Purchaser’s internal NR portal. 

2. The project website’s workspace shall identify (but not store) all relevant 

NR documents with a ‘dummy document’ reflecting the date of issue 

and title unless the title is classified. 

E. The project website shall use email alerts to notify the Purchaser, IV&V 

Contractor and ANWI Contractor of site changes/uploads. 

F. The project website’s workspace will use version control with major and 

minor versions. 

G. The project website’s workspace will provide audit logs for tracking and 

auditing. 

H. Each document shall clearly indicate whether it is part of a baseline or not. 

I. The project website’s workspace shall contain:



1. Purchaser provided documentation: 

a. Background and guidance documents referred to in the SOW. 

b. Entire contract. 

c. Information on other NATO Projects and NNHQ activities. 

2. ANWI Contractor provided and maintained documentation: 

a. All NATO UNCLASSIFIED ANWI project documentation, be it 

management products or specialists products, as soon as it is 

submitted in first draft version to the Purchaser. 

b. ANWI plans. 

c. Issue and Risk Register. 

d. Change Requests regardless of their status. 

e. All design documentation and vendor-provided technical documentation 

pertaining to the COTS. 

f. All test documentation. 

g. Project Schedule design specifications, documentation, and source 

code (installers and executables shall be provided to the Purchaser 

and maintained elsewhere in the Purchaser’s organisation). 

h. Project Status Reports. 

i. All presentation material from all Design Review and other meetings. 

j. Project Progress Review Meeting Minutes and notes of meetings. 

k. Site Survey Report. 

l. Site Installation Specifications. 

m. Network Design and Implementation Plan. 

n. Operator and PTC Network Reference Manuals. 

o. Maintenance Manuals. 

p. Request for Customs Form. 

q. Notice of Shipment. 

r. Inventory of provided Supplies. 

s. Training Material. 

t. Recommended Spare Parts List. 

u. Recommend Tools and Test-equipment list. 

v. Sub-Contracts and/or Purchase orders. 

w. All Baselines. 

x. Initial Operating Capability (IOC) Documentation. 

y. Final Operating Capability (FOC) Documentation. 





SECTION 5. 

ANWI SERVICE AND SYSTEM DESIGN 

5.1 General 

5.1-p1 The ANWI Contractor shall develop the design of the NNHQ ANWI 

(including all interfaces to other systems) to meet the ANWI’s architectural, service 

and system requirementsas described in this Statement of Work. 

5.1-p2 The ANWI Contractor shall initiate the ANWI design process starting with a 

Preliminary Design Review (PDR) Meeting and then provide the ANWI service 

design in 4 stages: 

1) Integrated Test Service, Cross Domain Gateways, switching, infrastructure, 

processing and storage; 

2) Service Management & Control; 

3) UCC Services, client provisioning; and 

4) GSM & secure communications) where each design stage will conclude with 

a Critical Design Review 

5.1-p3 The ANWI Contractor shall establish and maintain the NNHQ ANWI Design 

Documentation Package, consisting of: the ANWI Design Document, ANWI Service 

Interface Profile Documents (specifying all ANWI internal and external service 

interfaces), the security design, the Change Request log (tracing appropriate 

changes in the design document), an Off-specifications Document, and the ANWI 

Requirements Traceability Matrix. 

5.1-p4 Maintainability: All ANWI services shall ensure a minimal Operations and 

Maintenance 'tail' in terms of cost and resources where special attention is given to 

the manpower and skill profiles required to support the services. 

5.1-p5 Quality: The ANWI shall ensure that the Contractor's delivered solutions 

are 'fit for purpose' and adhere to the quality standards agreed in the Quality 

Management Plan, the Target Architecture, etc. 

5.1-p6 Life-Cycle Approach: The ANWI shall provide an estimation of all relevant 

life-cycle parameters relating to the delivered service (e.g. reliability [MTBF, MTTR], 

life-cycle costs, equipment life, etc.) and include Total Cost of Ownership. 

5.2 Preliminary Design Review (PDR) Meeting 

5.2-p1 The ANWI Contractor shall hold a Preliminary Design Review (PDR) 

Meeting at the Purchaser’s facility. 

5.2-p2 The Preliminary Design Review Meeting shall last not more than four (4) 

days. 

5.2-p3 The Preliminary Design Review Meeting shall be based upon the ANWI 

Contractor’s initial design proposal and include a detailed review and discussion of 

how the ANWI Contractor shall meet all the requirements of the contract. 





5.2-p4 The Preliminary Design Review Meeting shall outline the decomposition of 

the ANWI design into the four (4) CDRs to facilitate delivery, testing and acceptance 

of the ANWI. 

5.2-p5 The output of the Preliminary Design Review Meeting shall deepen the 

understanding of the ANWI requirements and guide the evolution of the ANWI 

Design Document into a comprehensive document that shall be used to implement 

the ANWI. 

5.3 Design Document Package 

5.3.1 General 

5.3.1-p1 The ANWI Contractor’s Design Document package shall define the 

NNHQ ANWI deliverables detailing how: 

A. The ANWI services shall be designed and configured. 

B. The requirements processes in the ANWI SOW shall be implemented. 

C. The ANWI security requirements shall be implemented. 

D. The NNHQ ANWI Interoperability Services shall be implemented for the 

duration of the ANWI migration and migration support to Business 

Applications. 

5.3.2 Design Document 

5.3.2-p1 The ANWI Contractor shall deliver the ANWI Design Document in 

accordance with Annex K Appendix 2. 

5.3.2-p2 The ANWI Design Document’s quality shall be reviewed in accordance 

with the ANWI Contractor’s QA process defined in the QAP (Annex K) and released 

by the ANWI Contractor’s PM. 

5.3.2.1 ANWI Design Objectives 

5.3.2.1-p1 The ANWI Contractor’s services’ design shall comply with the ANWI 

service requirements detailed in Annex C and D (logical, system and technical 

architecture requirements), Annexes E through I (ANWI services) and reference 

1.1.1.7.1. (NNHQ ICT Target Architecture). 

5.3.2.1-p2 The ANWI Contractor shall architecturally align all ANWI service 

designs with one another fully supporting integration (i.e. provide services, data, 

information & functionality to interface with other solutions) in accordance with the 

NNHQ Target Architecture. 

5.3.2.1-p3 The ANWI Contractor’s architecture shall adopt the basic principles 

of modularity and interface design. 





5.3.2.1-p4 The ANWI design shall ensure that the following principles are built 

into the ANWI design and implementation: 

A. Performance: providing the processing, memory, storage, and quality of 

services, as defined by the service parameters found in the SOW’s 

annexes. 

B. Reliability: identifying and implementing quality reliable COTS products to 

reduce the length of time between service or component failure and to 

reduce the exposure to software of small user communities. Reliability 

shall be calculated using: 

1. Reliability = (available time hrs. – total downtime hrs.)/number of breaks 

C. Availability: to ensure the availability of NATO information, supporting 

system services and resources, and to provide a robust system that 

minimises downtime versus uptime through the provisioning of highly 

available services and capabilities. Availability shall be calculated using: 

1. Availability = 100 x (agreed service time-downtime)/agreed service time 

D. High availability: the effect of minimising or masking the effect of 

component failure to data, capabilities, services or users. 

E. Scalability: accommodating the growth of processing, memory usage and 

storage capacity and network connectivity as defined in the service 

parameters found in the SOW’s annexes. 

F. Flexibility: supporting the dynamic increase and release of 

server/storage/networking services on demand. 

G. Confidentiality: to ensure the confidentiality of information by controlling 

the disclosure of, and access to, NATO information, supporting system 

services and resources. 

H. Integrity: to ensure the integrity of NATO information, supporting system 

services and resources. 

i. Continuity: ensuring that the average time to restore a service is per 

recovery targets. 

J. Interoperability: Ensure that during the migration phase, the old HQ ICT 

environment and the NNHQ ANWI ICT environment shall be able to exist 

next to each other.As well as ensure that NNHQ ANWI ICT environment 

shall be able to operate in harmony with other NATO and Commercial 

systems and services. 

K. Maintainability: delivering an overall system that minimises the average 

time to repair a service, capability or component. Maintainability shall be 

calculated using: 

1. Maintainability = downtime/number of breaks. 

L. Serviceability: monitoring delivered capabilities to demonstrate that the 

provided services and capabilities are meeting the terms of the service 

contract and agreed with the Purchaser. 

M. Monitoring services shall collect and store all necessary data to compile 

metrics, benchmarks, statistics and all base data needed for billing 

processes. 

5.3.2.1-p5 The ANWI Contractor’s design shall incorporate the design drivers 

as provided in Annex D section 12.2 as key themes in the design. 



5.3.2.2 Standardisation 



5.3.2.2-p1 The ANWI design shall minimize the variation of components and 

products in the ICT infrastructure through the use of a set of well-defined set of 

products that are standardized to the extent possible across the four networks. 

5.3.2.2-p2 The ANWI design shall ensure that components performing the 

same function across different locations and/or domains within ANWI shall be of 

same brand, model, capacity and feature. 

5.3.2.2-p3 The ANWI Contractor shall clearly document the justification and 

the results of exceptional cases where use of same equipment is not possible. 

5.3.2.2-p4 

5.3.2.2-p5 

protocols. 

All physical interfaces shall be based on industry standards. 

All logical interfaces shall be based on industry standards and 

5.3.2.2-p6 Configuration parameters shall be controlled, standardized and 

documented in the design. 

5.3.2.3 Innovation 

5.3.2.3-p1 The ANWI shall be on contract well before its implementation; as 

such, at least two technology life cycles are expected to occur during the ANWI’s 

implementation and the ANWI shall not implement old technology in the NNHQ but is 

expected to deploy proven and up to date modern technologies. 

5.3.2.3-p2 The ANWI Contractor shall incorporate innovation planning and 

assessment into the ANWI design process to overcome the risk of not delivering the 

most modern COTS solutions. 

5.3.2.3-p3 The ANWI Contractor shall make an assessment of state-of-art or 

announced technologies on service and technical maturity from an engineering and 

operations and support standpoint and justify the technology of choice for ANWI at 

the time of deployment and indicate promising technologies to keep track of since 

they may be a candidate for the CSI process. 

5.3.2.3-p4 The ANWI Contractor shall provide a design plan as part of the PIP 

reflecting the ANWI design being delivered in phases so that the design process, 

Purchaser decision and approval cycle are adequately supported in time prior to 

delivery and implementation. 

5.3.2.4 System Integration 

5.3.2.4-p1 The ANWI Contractor shall be responsible for integration of NNHQ 

ANWI components, capabilities, services and systems. 

5.3.2.4-p2 This implies both the integration of all ANWI HW and SW 

components and the integration of NNHQ ANWI with the existing NATO systems 

specified in Annex C and D. 



5.3.2.5 Environmental Considerations 



5.3.2.5-p1 The ANWI design shall include estimates of peak and average 

power consumption, UPS/backup power and cooling as well as the overall data 

centre Power Utilisation Efficiency. 

5.3.2.5-p2 The ANWI Contractor shall optimise the design in order to minimise 

the total cost of ownership, including energy consumption as one parameter. 

5.3.2.5-p3 The ANWI design shall account for the NNHQ environmental 

constraints provided in Annex B: Purchaser Furnished Equipment (PFE). 

5.3.2.5-p4 The ANWI Contractor shall comply with all appropriate Green IT 

regulations including, but not limited to, the use of local regulation compliant 

equipment. 

5.3.2.5-p5 The ANWI Contractor shall provide an efficient solution in terms of 

energy-consumption, use of materials and environmental friendly materials. 

5.3.2.5-p6 The ANWI design shall comply with all relevant local electromagnetic 

compatibility requirements. 

5.3.2.5-p7 The ANWI design shall pay particular attention to compliance with 

any restrictions resulting from low-level over-flight by Zaventem airport traffic. 

5.3.2.6 Capabilities 

5.3.2.6-p1 The ANWI Contractor’s design shall identify COTS hardware and 

software capabilities for use in each ANWI service. 

5.3.2.6-p2 The ANWI Contractor shall identify the intended product and 

version, and note if any modifications, adaptations, or additional elements (such as 

macros or plug-ins) are required. 

5.3.2.6-p3 In the ANWI design document, the ANWI Contractor shall describe 

the design, development, testing, and integration approach for any elements that 

require development. 

5.3.2.7 Capability Extension into ANWI Services 

5.3.2.7-p1 The ANWI Contractor shall use and integrate the ANWI capabilities 

to design and deliver a coherent and integrated set of services that comply with the 

Service Level Targets (SLT) and Requirements (SLR) specified in the Annexes to 

this SOW. 

5.3.2.7-p2 ANWI designed services shall: 

A. Incorporate resilient and secure infrastructure. 

B. Maintain the ANWI’s architecture principles. 

C. Identify the skills necessary to maintain and sustain the service. 

D. Easily scale to support life-cycle changes. 

E. Integrate with PFE services and applications (Annex B). 

5.3.2.7-p3 

Minimise the total cost of ownership, over a five-year life-cycle. 







5.3.2.7-p4 ANWI services shall be designed to leverage the following ITIL 

processes: 

A. Availability management 

B. Catalogue management 

C. Service level management 

D. Capacity & Performance management 

E. Continuity management 

F. Information Security management 

G. Supplier management. 

5.3.2.7-p5 The ANWI design shall ensure that the Service Catalogue’s Service 

Level Agreements are met. 

5.3.2.7-p6 

The ANWI contractor shall document all processes. 

5.3.3 Service Interface Profiles (SIPs) 

5.3.3-p1 Each interface between NNHQ ANWI servicies (ANWI internal 

interfaces) or an interface between a NNHQ ANWI service (ANWI external interface) 

and other capabilities or systems shall be documented in a SIP. Interface 

requirements are identified in each annex of this SOW and the SIPformat is provided 

in Annex K Appendix 17. 

5.3.4 Security Design & Accreditation 

5.3.4-p1 The Design Document package shall include the ANWI Contractor’s 

Security Risk Assessment (SRA) and security configurations (outline is provided in 

Annex K) of the proposed design. 

5.3.4-p2 The design shall identify how Information Assurance (IA) services shall 

be provided in the ANWI per Annex E Appendix 2 and per the IA requirements 

specified for each individual ANWI service (Annexes E through I). 

5.3.4-p3 The ANWI design’s IA section shall provide the security configuration 

settings and features implemented to provide a secure system, based upon the 

agreed SRA. 

5.3.4-p4 The ANWI Contractor shall provide security documentation in 

accordance with Annex K Appendices 11, 12 and 13 to support the security 

accreditation process. 

5.3.4-p5 The Purchaser is responsible for submitting the ANWI’s security 

documentation to the Security Accreditation Authority (SAA). 

5.3.4-p6 The ANWI Contractor shall provide support to the accreditation process, 

as detailed in Reference 1.1.1.7.2. 

5.3.5 Change Request Log 

5.3.5-p1 The ANWI Contractor shall maintain a Change Request Log that tracks 

all requests for change to the ANWI design (paragraph 6.4). 

5.3.5-p2 The ANWI Contractor’s Change Request Log shall trace requirement, 

specification or technical changes made to the ANWI design as a result of a design 

review or test result.





5.3.5-p3 The ANWI Contractor’s Change Request Log shall adhere to the ANWI 

Contractor’s approved change process (paragraph 6.4) 

5.3.6 Off-Specification Document 

5.3.6-p1 The ANWI Contractor shall maintain an Off-Specification Document that 

correlates test results and finding that differ from the approved design to design 

Change Request Log. 

5.3.6-p2 The ANWI Contractor’s Off-Specification Document shall serve as the 

log of service features and/or components that did not meet the expected service’s 

design outcome 

5.3.7 Requirements Traceability and Changes 

5.3.7-p1 The ANWI Contractor shall provide a Requirements Traceability Matrix 

with the design document that establishes a complete cross-reference mapping of 

the ANWI SOW’s requirements to the paragraph numbers of the ANWI Contractor’s 

ANWI Design Document which provides details to the lowest-level Configuration 

Items (CIs). 

5.3.7-p2 The ANWI Contractor shall maintain a design document change log that 

traces approved ANWI requirement changes to the Requirements Traceability Matrix 

and ANWI Design Document. 

5.3.7-p3 The ANWI Contractor shall maintain an Off-specifications Document 

that traces the service or system specification to the Requirements Traceability 

Matrix. 

5.4 Service Management Design 

5.4-p1 The ANWI Contractor shall design and implement an integrated Service 

Management console in accordance with the requirements identified in Annex E 

Appendix 1 

5.5 Integrated Test Service (ITS) Design 

5.5-p1 The ANWI Contractor shall design and implement an Integrated Test 

Service in accordance with Annex J. 

5.5-p2 The ITS shall be used to test all ANWI services, dependent project 

interfaces and other Host Nation deliverables (ESS, BMS, AVI and business 

applications with associated migration tools) that are to use ANWI 

services/components. 

5.6 Critical Design Review (CDR) 

5.6-p1 The ANWI Contractor shall create and present the ANWI Design Brief to 

the Purchaser’s staff. 

5.6-p2 

5.6-p3 

The ANWI Design Briefing shall be held at the Purchaser’s facility. 

The ANWI Design Briefing shall be planned to cover five (5) days.



5.6-p4 The ANWI Contractor shall include the following areas in Design Briefing: 

A. ITS Design and confirmation of equipment and software to be ordered for 

security domains, server rooms, site wide infrastructure equipment, client 

devices and software confirmation for ordering. 

B. NNHQ ANWI overall system, subsystems and interactions. 

C. Subsystem functionality, modularity and interfaces, breakdown into lowestlevel 

Configuration Items. 

D. Off-the-shelf products to be used in the system: the ANWI Contractor shall 

identify the intended product and version, and note if any modifications, 

adaptations, or additional elements (such as macros or plug-ins) are 

required. For any elements that require development, the ANWI 

Contractor shall describe the design, development, testing, and integration 

approach. 

E. Interfaces with other relevant systems, both NATO and non-NATO. 

F. System security design: Presentation of the Security Risk Assessment that 

the ANWI contractor used in creating the ANWI design: Results of the Risk 

Analysis, Definition and implementation of the Security measures to 

counter the risks identified in the Risk Assessment and relate those to the 

security mechanisms as required in section 11.8.2.2. This presentation 

shall be done as a separate item. This presentation shall also address the 

changes to be brought by the ANWI Contractor to any INFOSEC 

documentation which NATO may have provided the ANWI Contractor with. 

G. System migration and interoperability: Migration planning and order, 

migration risks, possible issues during migration, complications expected 

during the interoperability period. 

H. Sequence and scope of system tests of the initial and updated 

Developmental Baseline and any requirements for Purchaser support and 

participation. 

i. Innovation plan to guarantee the most modern COTS technology solutions 

are provided. 

J. Any change request or off-specification. 

K. Requirements traceability matrix. 

L. Any changes to the Project Implementation Plan. 

M. Risk assessment of proposed changes and an update of the Risk log and 

Issue Log. 

5.6-p5 The ANWI Contractor shall deliver the ANWI Design Document to the 

Purchaser at the end of the Design Briefing. 

5.6-p6 The duration of the Purchaser review cycle for the NNHQ ANWI Design 

Documentation Package will not exceed 3 (three) weeks. 

5.6-p7 Three weeks after the ANWI PDR Briefing, a follow-on Critical Design 

Review Meeting shall be held with the Purchaser and ANWI Contractor attending. 

5.7 Critical Design Review (CDR) Feedback Meeting 

5.7-p1 

facility. 

5.7-p2 

The Critical Design Review (CDR) meeting shall be held at the Purchaser’s 

The CDR feedback meeting shall be planned to cover two (2) days. 





5.7-p3 The Purchaser will brief the ANWI Contractor on their comments on the 

design document. 

5.7-p4 At the conclusion of the CDR feedback meeting the Purchaser will issue his 

comments on the design document to the ANWI Contractor. 

5.7-p5 The ANWI Contractor shall have two weeks to make the required changes 

where he shall then submit the design document package for acceptance. 

5.8 Acceptance of the Design Document 

5.8-p1 Purchaser review and acceptance of the ANWI Design Documentation 

package shall imply Purchaser acceptance of the NNHQ ANWI design permitting a 

move to the next stage of the project. It remains the sole responsibility of the ANWI 

Contractor to prove the design through the regime of testing set forth in the Contract 

and it will be the sole responsibility of the ANWI Contractor in the event that the 

system proves deficient in meeting the contractual requirement. 





SECTION 6. 

ANWI IMPLEMENTATION AND TRANSITION 

6.1 General 

6.1-p1 This Section provides the requirements for managing service transitions 

according to agreed service design requirements, with the final aim to meet business 

requirements and user expectations, minimizing risks and maximizing the services' 

effectiveness. 

6.1-p2 This section addresses the requirements related to: 

A. The delivery of equipment and the implementation of services, and 

B. The transitioning to new and modified services that shall meet the user’s 

expectation as defined in the High Level Requirements and the Service 

Design supporting an overall service lifecycle. 

6.1-p3 The project Implementation and Transition phase covers all ANWI activities 

from first access to the site for site surveys through to the fully functional ANWI 

services and handover of the ANWI. 

6.1-p4 The high level implementation and transition timeline shall refer to the 

diagram in Figure 6.1. 

Figure 6.1a ANWI high level implementation and transition timeline 

6.1-p5 The ANWI Contractor shall initiate the Project’s Implementation and 

Transition phase once: 

A. The Service Design Package has being confirmed, 

B. The Configuration Management System has been implemented with all 

Configuration Item baselines, and 

C. The delivery schedule of equipment to site has been agreed with the 

Purchaser. 

6.1-p6 The ANWI Implementation and Transition is underpinned by the following 

six major processes: 

1) Transition Planning and Support, 

2) Change Management, 

3) Service Asset and Configuration Management, 

4) Release and Deployment Management, 




5) Release and Deployment Planning Phase 

6) Knowledge Management. 


6.1-p7 The requirements for each of the six processes are documented in the 

following paragraphs. 

6.2 Transition Planning and Support Process 

6.2-p1 The ANWI Contractor shall support the Transition Planning by: 

A. Leading the Transition Planning and Support Process in cooperation with 

the Purchaser for providing and coordinating the overall plan; 

B. Ensuring that the Implementation and Transition phase is coordinated with 

the Purchaser Project Management office and staff; 

C. Planing and coordinating the resources with the aim to warrant that High 

Level requirements and Service Design requirements are thoroughly 

implemented in Service Operation; 

D. Deploying new and changed services within the established, estimated 

and agreed cost, quality and timeline; 

E. Sustaining multiple transitions at the same time. 

6.2-p2 The ANWI Contractor shall support the transition by: 

A. Ensuring that all the required policies / standards / models for both 

transition activities and processes are respected; 

B. Reviewing and briefing ANWI Contractor staff on NNHQ campus access 

policies; 

C. Reviewing safety procedures for working on the NNHQ campus; 

D. Ensuring that the ANWI Contractor implementation staff are issued access 

badges to the NNHQ campus; 

E. Surveying the Purchaser provided storage and staging areas on the 

NNHQ campus; 

F. Periodically reviewing the plans to improve the transition’s efficiency. 

6.2-p3 The ANWI Contractor Transition/Migration Plan shall include the Security 

Test and Evaluation Plan per Annex K. 

6.3 Change Management 

6.3.1 General 

6.3.1-p1 The ANWI Contractor shall have a fully functioning change 

management process (with defined roles and responsibilities), as required in the 

project management section of this SOW, established to support all changes to the 

configuration items in a configuration management system, change/modify user 

business requirements, and the implementation process. 

6.3.1-p2 The ANWI Contractor shall provide for all service changes (which are 

any changes) to Configuration Items (CIs) (addition, modification, removal) that have 

or could have an operational impact on the operation of ICT services. 



6.3.2 Types of Service Change 



6.3.2-p1 Standard Change: low-risk pre-authorized change with a known 

procedure to implement it 

6.3.2-p2 Emergency Change: change that needs to be implemented as soon as 

possible to resolve an issue (i.e. security incident, major incident, etc.) 

6.3.2-p3 

categories. 

6.3.3 Change Requests 

Normal Change: change belonging to neither of the two previous 

6.3.3-p1 The ANWI Contractor shall submit change requests, as needed, to 

adjust and support the integrity of service assets and configurations as needed to 

deliver the ANWI design. 


rectify issues and mitigate risks. 


support the coordination and installation of the ANWI. 

6.3.4 Change Process 

6.3.4-p1 The ANWI Contractor shall implement a Change Process following the 

ITIL best practice. 

6.3.5 Change Advisory Board (CAB) 

6.3.5-p1 The ANWI Contractor, HQPO and the Purchaser shall be members of 

the ANWI Change Advisory Board to review and process change requests and 

provide assistance to process, evaluate, assess, prioritize and evaluate changes. 

6.3.5-p2 

6.3.6 Change Models 

The ANWI IV&V will observe and monitor the activities of the CAB. 

6.3.6-p1 The ANWI Contractor and the Purchaser will agree on a definite set of 

changes that need to be pre-defined through agreed change models. 

6.3.6-p2 The ANWI Contractor’s change model shall include the steps to be 

taken, their chronological order, the roles and responsibilities during the change 

management processes, the thresholds to assess the completion and performances, 

the escalation procedures. 

6.3.7 Change Remediation 

6.3.7-p1 The ANWI Contractor shall propose a change remediation process 

which includes those pre-defined actions to be taken after a change failed. 

6.3.7-p2 For CAB to grant the change authorization, the ANWI Contractor shall 

propose the Change Remediation options as part of the change documentation. 




6.4 Service Asset and Configuration Management 


6.4-p1 The purpose of this process is to ensure that the required assets to deliver 

the services are systematically controlled and that all the information about those 

assets is updated, reliable, and available when and where requested. 

6.4-p2 The Configuration Management process shall support the lifecycle of any 

service asset, ensuring that baselines are updated, all CIs identified, and that any 

change is documented. 

6.4-p3 The Configuration Management process shall also serve as the interface 

between services and the complete map of the CIs relationships. 

6.4-p4 The ANWI Contractor shall implement this process for the Implementation 

and Transition, and to hand – over to the Support Authority at the end of the phase. 

6.4-p5 The ANWI Contractor shall document the baseline of ANWI configuration 

items (CIs) to include: 

A. ICT Services, 

B. Software, 

C. Hardware, 

D. Facilities, 

F. People, 

G. Formal documents (SLAs, OLAs, Service Catalogue, etc.). 

6.4-p6 The ANWI Contractor shall implement, as part of the configuration 

management process, a set of tools and database(s) [configuration management 

database (CMDB)] to manage all the ICT Services configuration data that is 

interfaced with other ANWI support processes: 

A. Incident, 

B. Problems, 

C. Known errors, 

D. Changes, 

E. Releases. 

6.4-p7 The ANWI Contractor shall implement a Definitive Media Library (DML) in 

accordance with the ITIL definition. 

6.5 Release and Deployment Management Process 

6.5.1 Release and Deployment Management Process 

6.5.1-p1 The ANWI Contractor shall implement a Release and Deployment 

Management process to plan, schedule and control the build, test and deployment of 

the new services, while protecting the integrity of any existing infrastructure. 

6.5.1-p2 The ANWI Contractor shall: 

A. Define and agree a service’s release and deployment plan with the 

Purchaser; 

B. Create test release packages and agree with the Support Authority to 

verify that utility and warranty of services are satisfied and granted; 

C. Deploy Release Package following the agreed plans and schedules; 







D. Record and manage deviations, risks, issues related with the 

implementation of Release Packages and take corrective actions when 

necessary; 

E. Ensure that knowledge transfer is ensured to users, and support Authority 

staff. 

F. The Release and Deployment Management process formally manages 

processes, systems, and functions to package, build, test, deploy, release, 

hand-over any CIs required to implement a release: Physical and Virtual 

assets, Applications and software, Training, Services. 

G. This process has also as objective of eventually handing the services to 

the support Authority. 

6.5.1-p3 The Release and Deployment plan shall ensure that the following four 

principal phases will be satisfied: 

A. Release and Deployment Planning Phase, 

B. Release Build and Test, 

C. Deployment, 

D. Review and Close. 

6.5.2 Release and Deployment Planning Phase 

6.5.2.1 General 

6.5.2.1-p1 At this phase, all the plans for creating and deploying services shall 

be composed and agreed with the Purchaser. The trigger for initiating the phase is 

the change management authorization to compose the plan, and ends with the 

change management authorization to create the Release Package. 

6.5.2.1-p2 

This phase shall be re-iterated for each single Release Package. 

6.5.2.1-p3 The ANWI Contractor shall initiate the implementation and transition 

phase of the project once the design confirmation of capabilities (configuration item 

baselines) and services has been achieved, and the delivery schedule of equipment 

to site has been agreed with the Purchaser. 

6.5.2.1-p4 

The ANWI Contractor shall then proceed to testing the capabilities. 

6.5.2.1-p5 The ANWI Contractor shall, upon successful testing of the 

capability, be permitted to install the capability. 

6.5.2.1-p6 The ANWI Contractor shall, with all required capabilities in place, 

proceed to test and then implement the ANWI infrastructure services (note: this may 

be tested, as practical, in parallel with capability testing). 

6.5.2.1-p7 Upon implementation and acceptance of all capabilities and 

infrastructure services, the ANWI Contractor shall request Initial Operating Capability 

(IOC) per paragraph 6.8. 

6.5.2.1-p8 The ANWI Contractor shall then complete the test and implement 

the remaining elements of ANWI client services. 

6.5.2.1-p9 The ANWI Contractor shall, upon successful installation of all client 

devices and services and support of ICTM application and data migration, request 

Final Operating Capability (FOC) per paragraph 6.10.



6.5.2.1-p10 The ANWI Contractor shall provide 6 months of service 

improvement and technical support between FOC to Final System Acceptance. 

6.5.2.2 Site Survey 

6.5.2.2-p1 The Release and Deployment plan shall envisage a site survey 

consisting of: 

A. General 

1. The ANWI Contractor shall conduct site survey preparatory work, visit 

the old NATO Headquarter Site, the NNHQ ANWI site, Bâtiment Z and 

the NNHQ remote sites (see Annex M), provide an Introductory Briefing 

to the site, survey relevant facilities, interview site personnel, and collect 

data to support site preparation and implementation. 

2. The ANWI Contractor shall identify his intent to conduct a site survey 

and request permission to access the facility at least one (1) month 

before the targeted survey date. 

3. The ANWI Contractor shall identify all required support facilities, 

including modifications or additions required, within one week of a site 

survey. 

B. Site Survey Workbook 

1. The ANWI Contractor shall prepare a site survey workbook of 

checklists, fill-in forms, installation sketches, contact information, 

installation specifications, site data to be collected by the ANWI 

Contractor during the site survey, and any other documentation 

required to perform site surveys. 

2. This workbook shall be available for Purchaser review and comment 

before the first site survey, and shall be maintained and updated as 

necessary during the site survey process. 

3. Upon acceptance of the Site Survey Workbook by the Purchaser, the 

ANWI Contractor shall distribute the Site Survey Workbook to the sites 

for preparation of the Site Surveys. 

4. The ANWI Contractor shall provide the Purchaser with the ANWI 

Contractor’s proposed site survey agenda, the presentation material 

that the ANWI Contractor intends to use, the ANWI Contractor’s 

attendance list. Based on agreement from the Purchaser, the ANWI 

Contractor shall organise and conduct the Site Survey. 

C. Introductory Briefing 

1. The Introductory Briefing shall not assume other than basic knowledge 

of the project by the site personnel. 

2. The Introductory Briefing shall be an introduction to NNHQ ANWI 

outlining the ANWI services, describing the system functionalities, the 

site to be implemented, the project timelines, the goals and objectives 

of the Site Survey process, and the notional implementation identified 

for the surveyed site and to be refined through the Site Surveys 

activities. 





D. Survey of the Site Facilities 

1. During the Site Survey the ANWI Contractor shall determine the 

necessary installation preparation and support arrangements and 

collect all project implementation-relevant information. This shall 

include: 

a. Validation of the numbers of users and administration staff for NNHQ 

ANWI for the NNHQ site. 

b. Validation of the number, location, and network connectivity of any 

remote users. 

c. Analysis of the training needs. 

d. Estimate of the on-site training requirements, based on the numbers 

of First- and Second-Level Support staff and NNHQ ANWI Users 

identified by the Site POC. 

e. Identification of any input (equipment, documentation and 

information) or work required from the Purchaser with indication of 

suspense date. 

f. As per site-provided information, identification of the facilities where 

NNHQ ANWI equipment will have to be installed. 

g. Identification of any piece of equipment available in the NATO HQ 

Site (e.g. servers, racks), that meets the contractual requirements of 

this contract and that the ANWI Contractor deems reusable for the 

purpose of this Contract. Note the ANWI Contract is based on the 

requirement for procurement and deployment of all new equipment. 

However, having knowledge of current HQ existing equipment that 

potentially can be reused, may help with the implementation, 

including the possibility of providing further migration options. Some 

speciality or very new hardware/software suites may have to be 

relocated when the user relocates; the ANWI Contractor shall 

accommodate for this space or connectivity (e.g. graphics lab Apple 

computers) List of all system CIs (nature and quantities) to be 

installed in the site. 

h. All site data relevant to the future site installation (current systems 

configuration data as required). 

i. List of systems and services that are candidates for reuse. 

j. List of interfaces to Specific CoI Services (e.g. Business 

Applications) which will continue to be supported in the new building. 

E. Out Briefing 

1. The ANWI Contractor shall conduct an out briefing of the site survey’s 

findings and recommendations to the Purchaser. 

F. Post Site Survey Report and Action Items 







1. The ANWI Contractor shall present his site engineering and installation 

drawing(s) 2 weeks after the Site Survey to the Purchaser for review. 

2. The ANWI Contractor shall update the Project Management 

Documentation immediately after the Site Survey and no later than two 

(2) weeks before the Site installation. 

3. The ANWI Contractor shall update and re-issue the Project 

Management Documentation to the Purchaser. 

6.6 Accreditation Documentation 

6.6.1 Security Risk Assessment 

6.6.1-p1 The ANWI Contractor shall provide a Security Risk Assessment (SRA) 

in accordance with Annex K Appendix 11. 

6.6.1-p2 The ANWI Contractor shall maintain the ANWI System Security 

Configuration based on the SRA. 

6.6.1-p3 The ANWI Contractor shall review and, as necessary update the SRA 

as changes are made to either the design or a CI’s baseline documentation. 

6.6.2 Security Documentation 

6.6.2-p1 The ANWI Contractor shall provide security documentation in 

accordance with Annex K Appendices 5, 11, 12 and 13. 

6.6.3 Server Security Roles 

6.6.3-p1 ANWI servers, wherever feasible, shall use NATO standard security 

roles (e.g. Domain Controller, DNS) of which the latest guidance documentation will 

be provided at Contract Award. 

6.6.3-p2 The ANWI Contractor shall assess the provided security roles as they 

relate to server performance. 

6.6.3-p3 The ANWI Contractor shall recommend changes to the security roles' 

configuration settings to the Purchaser for approval so long as the recommended 

changes improve performance without compromising security. 

6.6.3-p4 The ANWI Contractor shall ensure that the security roles are addressed 

in the System-specific Security Requirements Statement (SSRS) input. 

6.6.3-p5 The ANWI Contractor shall ensure that the protocols addressed in the 

security roles are reflected in the System Interconnection Security Requirements 

Statement (SISRS) input. 

6.7 Release Build and Test Phase 

6.7-p1 The change management authorization to create the Release Package 

triggers this phase that ends with the change management authorization to baseline 

the Release package into the DML by the Service Asset and Configuration 

Management Process. 

6.7-p2 

This phase shall be re-iterated for each single Release Package.





6.7-p3 The ANWI Contractor shall conduct testing activities to verify a capability or 

service for compliance with the contractual requirements by demonstrating its 

operational suitability, to evaluate its performance and to establish benchmarks for 

future enhancements. 

6.7-p4 Throughout any test session the ANWI Contractor shall organise and 

conduct Test Status Meetings with the Purchaser on a weekly basis to discuss: 

The results of the tests run to date. 

Any new Off-specifications raised. 

Any adjustments to the schedule of test activities within the test session. 

Any other issues. 

6.7-p5 Waivers 

The ANWI Contractor may choose for some specific requirements, rather than 

perform actual tests to provide documentary evidence to show that the stated 

requirements are fulfilled. 

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. 

If the ANWI Contractor intends to rely on previously successfully completed 

qualification testing to national or international standards for assemblies, 

subassemblies, components or parts, the ANWI Contractor shall produce the 

following documentation: 

o The equipment specifications and true manufacturing number to 

demonstrate that the NNHQ ANWI CI for which a test waiver is requested is 

identical to the equipment previously tested. 

o The ANWI Capability Services Requirements, SSRS, SISRS, and CPS 

(Certificate Practice Statement) if the system includes a PKI requirement(s) 

covered by the test waiver. 

o The test standards, procedures and methods employed on the testing. 

o The nationally or internationally certified test results. 

6.7-p6 A Statement in which the ANWI Contractor shall certify that the 

equipment to be implemented is identical to that which was originally tested and 

certified or advice 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. 

6.7-p7 

The Purchaser reserves the right to reject any test waiver request. 

6.7-p8 The ANWI Contractor shall record and log all test waiver requests along 

with their resolution and shall hand-over the records and logs at the FST. 

6.8 Testing 

6.8.1 General 

6.8.1-p1 The ANWI Contractor shall provide a suite of comprehensive tests to 

test service components, proof of concept, service certification, service activation and 

final site testing.



6.8.1-p2 The ANWI Contractor testing shall be conducted in either the 

Integration Test Service (ITS) or NNHQ server rooms. 

6.8.1-p3 All testing activities in the ITS will be monitored by both the Purchaser 

and ANWI IV&V. 

6.8.1-p4 The following figure depicts the relationship between the tests required 

to field the ANWI services. 

Figure 6.1b ANWI test flow 

6.8.2 Capability Acceptance Testing (CAT) 

6.8.2-p1 The ANWI Contractor shall commence this phase of the project with 

Capability Acceptance Tests (CATs). 

6.8.2-p2 Testing shall be in accordance with the approved Test and Acceptance 

Plan (Annex K). 

6.8.2-p3 The ANWI Contractor shall schedule the CAT in either the ITS or other 

Purchaser approved NNHQ campus location that is physically interconnected to the 

ITS to demonstrate that the specific capability, as defined in the SOW, meets the 

operational, functional and technical requirements. 

6.8.2-p4 The ANWI Contractor shall deliver all test documentation required for 

the test (Section 4, Project Management - System Test Documentation Package) for 

the Purchaser’s review (and IV&V validation) at least two weeks prior to the test. 

6.8.2-p5 Before each test session the ANWI Contractor shall confirm to the 

Purchaser that all required hardware, software, test equipment, instrumentation, 

supplies, facilities, and personnel are available, in place and ANWI baseline 

configured to conduct the test session. 





6.8.2-p6 The Purchaser and IV&V will monitor and inspect the ANWI 

Contractor’s test activities to ensure compliance. 

6.8.2-p7 Reserved . 

6.8.2-p8 The Purchaser will review the ANWI Contractor’s test report for 

correctness, completeness, and acceptance. 

6.8.3 Proof of Concept Testing (PCT) 

6.8.3-p1 The ANWI Contractor shall focus on the SMC, UCC, CDM and Client 

Provisioning services with the aim to validate and confirm technical and user-related 

useability features prior to finalising the design of these services. 

6.8.3-p2 The ANWI Contractor shall use the ITS, or other designated facility on 

the NNHQ campus, for all PCT. 

6.8.3-p3 The ANWI Contractor shall undertake PCT for the following ANWI 

services: 

A. CDGW (Annex E Appendix 2). 

B. UCC (Annex G). 

C. SMC (Annex E Appendix 1) 

D. Client Provisioning (Annex H Appendix 2) 

6.8.3-p4 The PCT will be concluded with user- and technical-level testing, 

demonstration and validation. 

6.8.4 Service Certification Tests (SCT) 

6.8.4-p1 The ANWI Contractor shall test the system engineering, integration, and 

monitoring of the services as delivered and monitored in the NNHQ Network 

Operations Centre. 

6.8.4-p2 The ANWI Contractor shall use the SCT to activate an ANWI service for 

use in the NNHQ. 

6.8.4-p3 The ANWI Contractor shall use the SCT to validate that a service is “fit 

for purpose” and assures that it is also “fit for use”. 

6.8.4-p4 The ANWI Contractor shall use the SCT to confirm the ANWI Service 

Catalogue. 

A. Service definition includes the service description and components. 

B. Service utilities, requirements and warranties for correct functioning. 

C. Service’s context, function from utilisation perspective – scenario of use. 

D. Service operation. 

E. Process (repeatable, audit/traceability to requirement) maps, workflow 

diagrams, activity patterns & combination of service assets, context, 

approach, boundaries. 

F. Acceptance criteria & margin of error – to meet Reliability, Maintainability, 

and Availability (RMA) – test activities, specialist tools, people. 

G. Metrics and test measurements are managed, monitored and controlled. 

H. Service’s standards. 

I. Scope, organisation. 

J. Process: management, control, recording, monitoring reporting; planning; 

test preparation, install, perform document. 





K. Identification of the items to test: service package, service level package, 

service model. 

L. Operations and support plan. 

M. Risk assessment for testing and use. 

N. Interfaces. 

O. Approach: test level, regressing, simulation, reuse pieces ID up front. 

P. Criteria – pass/fail, entry, exit, stop/start. 

Q. Deliverables: documentation, plan, spec – design, test case, procedure – 

results/reports, validation, summary. 

R. Functional and operational management. 

S. Technology. 

T. Service’s documentation. 

6.8.4-p5 The ANWI Contractor shall conclude all SCT with the finalisation of the 

specific (whether it is a user [business] or support [technical]) ANWI Service 

Catalogue entry. 

6.8.4-p6 The ANWI Contractor shall request to hold the Initial Operating 

Capability meeting upon completion of SCT. 

6.8.5 System Activation Testing (SAT) 

6.8.5-p1 The ANWI Contractor shall use the SAT to provide the overall 

operational testing of all ANWI integrated services offered on the NNHQ site. 

6.8.5-p2 The ANWI Contractor shall confirm, via this test, that the integrated 

back-end, specific CoI and supplemental services are “fit for purpose”. 

6.8.5-p3 The ANWI Contractor shall request to hold the Final Operating 

Capability meeting upon completion of SAT. 

6.8.6 Final Site Testing (FST) 

6.8.6-p1 The ANWI Contractor shall achieve FST after the installation of all user 

devices and activation of the user’s requested service catalogue choices to the user’s 

device. 

6.8.6-p2 The ANWI Contractor shall support the ICTM staff with infrastructure 

and Active Directory assistance as the ICTM staff installs NATO’s business 

applications and migrates the application’s data onto ANWI storage. 

6.8.6-p3 The ANWI Contractor shall request to hold the Final System 

Acceptance meeting upon completion of FST. 

6.8.7 Security Implementation Verification Procedures (SIVP) 

6.8.7-p1 The ANWI Contractor shall provide and maintain a Security 

Implementation Verification Procedures (SIVP) as part of the testing. 

6.8.7-p2 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 complies with the 

CPS, SSRS and SISRS. 



6.8.8 Requirements Traceability Matrix 



6.8.8-p1 The ANWI 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. 

A. Sequencing of activities for a Test session. 

B. Test Failures. 

C. Classification of Test Failures. 

6.8.9 Test Failures 

6.8.9-p1 

Should a failure occur during testing, a failure report shall be 

raised by the ANWI Contractor and a preliminary investigation shall be immediately 

carried out in order to classify the failure as one of the following: 

A. Class “A”: there is evidence that the cause was an external or transient 

condition. 

B. Class “B”: there is mutual agreement that the cause was an inherent 

design or manufacturing deficiency in the unit under test. 

C. 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. 

6.8.9.1 Class "A" Failures 

6.8.9.1-p1 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. 

6.8.9.1-p2 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. 

6.8.9.1-p3 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. 

6.8.9.2 Class "B" Failures 

6.8.9.2-p1 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 ANWI Contractor determines the specific 

cause of the failure and proposes appropriate remedial action acceptable to the 

Purchaser. 

6.8.9.2-p2 Should the cause of the failure or the effect of the proposed 

remedial action be deemed by the ANWI Contractor to have no influence whatsoever 

on other areas of scheduled testing, the ANWI Contractor may propose to the 

Purchaser to continue testing in the other areas prior to the rectification of the cause 

of the failure. 

6.8.9.2-p3 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 retests, 

to prove they have been successfully completed. 





6.8.9.2-p4 The ANWI 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 ANWI 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. 

6.8.9.2-p5 After remedial action has been taken by the ANWI 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. 

6.8.9.2-p6 The ANWI 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 ANWI Contractor 

providing full details describing the cause of the failure and the recommended 

remedial actions to be taken. 

6.8.9.3 Class "C" Failures 

6.8.9.3-p1 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 ANWI 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. 

6.8.9.3-p2 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. 

6.8.10 System Off-Specifications 

6.8.10-p1 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. 

6.8.10-p2 Throughout any test session the ANWI Contractor shall maintain Offspecifications 

Reports and the Off-specifications Document describing all noted Offspecifications. 

6.8.10-p3 The contents of the required Off-specification Reports are outlined 

below: 

A. Off-specification identification. 

B. Description of the Off-specification. 

C. Related test (if the Off-specification was raised further to a test failure). 

D. Severity (Major if to be corrected before deployment, otherwise Minor). 

E. CIs affected. 

F. Action taken. 

G. Fault Resolution status: 





1. Open=the Off-specification is identified. 

2. Resolved= remedial action has been taken by the ANWI Contractor and 

demonstrated through tests conducted by the ANWI Contractor without 

official witnessing by the Purchaser. 

3. Closed= the resolution was officially demonstrated to the Purchaser. 

H. Comments 

6.8.10-p4 The ANWI Contractor shall provide a list of all Off-specification Reports 

processed since the start of the project, in tabular form, indicating for each of them 

the date is was created and the current status. 

6.8.10-p5 The System Version Definition Document shall include the following: 

A. List of differences between this and the previous System version. 

B. List of capabilities of this System version. 

C. Guidelines on how to install this System version. 

D. Breakdown of the system into CIs and provision of accurate identification 

information for every CI. 

6.8.10-p6 The ANWI Contractor shall record the results of a test in test results 

sheets incorporated in the relevant test procedure and shall be called the Test 

Report. 

A. The ANWI Contractor shall declare a test as ‘passed’ if the entirety of the 

expected results were obtained when running the test. 

B. The ANWI Contractor shall ensure that the test report’s cover sheet clearly 

shows whether the test passed, failed, or was not run and for what 

reasons. 

C. Where the Purchaser or the Purchaser’s IV&V Contractor 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. 

D. The ANWI Contractor’s representative and the Purchaser’s representative 

shall sign after completing the testing. 

E. Each original test report shall be provided to the Purchaser and a PDF-A 

version of the report shall be posted (with an alert for the Purchaser) on 

the ANWI project’s web site for acceptance within 15 (fifteen) working 

days after the completion of the test. 

6.9 Integration and Testing Service (ITS) 

6.9-p1 The ANWI Contractor shall design, install, configure, and support the ITS in 

accordance with Annex J. 

6.9-p2 The ANWI Contractor shall create, manage and maintain the ITS baseline 

configuration to be consistent (in line) with the expected deployed ANWI environment 

and production baseline. 

6.9-p3 The ANWI Contractor shall support the use of the ITS by other Host 

Nations and/or their contractors by restoring the ITS baseline, providing configuration 

points during testing and support in adjusting the ITS’ hardware configuration. 







6.9-p4 The ANWI Contractor shall test all ANWI services through service 

certification testing in the ITS prior to installing the service in the NNHQ server 

room(s), validating the service installation and conducting the remaining ANWI tests. 

6.9-p5 The ANWI IV&V will observe and monitor all ITS activities as the NATO 

Quality Assurance representative. 

6.10 Deployment 


6.10.1-p1 This phase starts with the change management authorization to deploy 

and ends with the hand-over to the support Authority of each release package. 

6.10.1-p2 

This phase shall be re-iterated for each single release package. 

6.10.1-p3 The ANWI Contractor shall consider the following requirements when 

deploying any Release Package. 

6.10.2 Delivery of Equipment 

6.10.2.1 Delivery to site process 

6.10.2.1-p1 The ANWI Contractor shall deliver NNHQ ANWI hardware and 

software as specified in this Contract. This section defines the general requirements 

that shall apply to all NNHQ ANWI equipment delivery. 

6.10.2.1-p2 The ANWI Contractor shall provide the labour involved in the 

packing, unpacking, installation, configuration, and activation of ANWI equipment. 

6.10.2.2 Inventory 

6.10.2.2-p1 The ANWI Contractor shall ensure the provision of an inventory 

down to the Lowest Replaceable Unit (LRU) level of all the equipment, software, 

training and other documentation supplied, not later than ten (10) working days prior 

to the first shipment of the equipment to the Purchaser. 

6.10.2.2-p2 The ANWI Contractor shall use the NATO Material Data Sheet 

(MDS) document as provided in Annex K. 

6.10.2.2-p3 The ANWI Contractor shall post a softcopy of the inventory on the 

portal, in Microsoft Excel or Access database format. 

6.10.2.2-p4 The inventory information shall, as a minimum, include the following 

data elements: 

(1) Contract Line Item Identification Number (CLIN). 

(2) NATO Stock Number (NSN, if known). 

(3) Item Name. 

(4) Expendable or Non-Expendable Code. 

(5) True Manufacturer Part Identification. 

(6) True Manufacturer code or complete name and address. 

(7) Vendor/Contractor Code or complete name and address. 

(8) Vendor/Contractor part number. 

(9) Quantity ordered. 

(10) Serialized item tag.


(11) Serial Number. 

(12) Software Revision Level. 

(13) Hardware Revision Level. 

(14) Serial Number Attributes. 

(15) Accountable Item Flag. 

(16) Currency. 

(17) Price. 

(18) Warranty Expiration Date. 

(19) Extended Line Item Description (if applicable). 

(20) Part Number of Next Higher Assembly. 

(21) Quantity in Next Higher Assembly. 

(22) Location Code. 

6.10.2.3 Transportation 


6.10.2.3-p1 The ANWI Contractor shall ship all supplies to the destinations as 

identified in the Schedule of Supplies. 

6.10.2.3-p2 The ANWI Contractor shall transport all ANWI warranty supplies 

from and to all NNHQ destinations at his expense through FSA. 

6.10.2.3-p3 The Purchaser is not liable for any storage, damage, accessories or 

any other charges involved in such transporting of supplies prior to the actual 

acceptance of such supplies at the sites. 

6.10.2.4 Preservation and Packaging 

6.10.2.4-p1 The ANWI 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. 

6.10.2.4-p2 The ANWI 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. 

6.10.2.4-p3 

These packing lists shall accompany the shipment. 

6.10.2.4-p4 Each individual box from a consignment shall have one packing list 

in weatherproof envelope affixed to the outside of each box that indicates exactly 

what is contained inside. One copy shall also be put inside each box. 

6.10.2.4-p5 The packing lists shall contain all necessary information for easy 

identification of the content by the Consignee and shall also indicate the Contract 

Number, Prime Contractor/Sender and the Purchaser’s names and addresses. 

6.10.2.5 Customs Form 302 

6.10.2.5-p1 

This form is not required for movements within the European Union. 

6.10.2.5-p2 The ANWI Contractor shall ensure the timely request of Customs 

Forms 302 which is required for duty free import/export of supplies. 





6.10.2.5-p3 Following receipt of the request by the Purchaser, normally a 

maximum of three working days is required for the issue of the form. 

6.10.2.5-p4 These forms MUST 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 ANWI Contractor. 

6.10.2.5-p5 The written request for a 302 form, (provided in Annex K) 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. 

6.10.2.5-p6 If a country refuses to accept the Form 302 and requires the 

payment of customs duties, the ANWI 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 ANWI Contractor shall pay these 

customs duties and the Purchaser shall reimburse the ANWI Contractor at actual 

cost against presentation of pertaining documents. 

6.10.2.5-p7 The ANWI 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. 

6.10.2.6 Notice of Shipment 

6.10.2.6-p1 The ANWI Contractor shall, before each shipment of supplies, 

provide the Purchaser with a notice of shipment 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. 

6.10.2.7 Shipment 

6.10.2.7-p1 The ANWI Contractor shall ship all required hardware, software, 

and installation or testing tools to the locations designated by the Purchaser. The 

ANWI Contractor shall be responsible for resolving any loss incurred in shipping. 

6.10.2.8 Delivery to Site 

6.10.2.8-p1 The ANWI Contractor shall be responsible to ensure that the 

deliveries are received, processed and delivered to the installation location. 



6.10.2.9 Security Scanning 





6.10.2.9-p1 The ANWI Contractor shall ensure that all contractor 

hardware/software deliverables are provided to the Purchaser for screening for bugs 

and viruses. 

6.10.2.9-p2 The ANWI Contractor shall ensure that at least 1 week is provided 

for the Purchaser to execute the electronic screening process. 

6.10.2.9-p3 The ANWI Contractor’s on-site staff shall execute the unpacking 

and repacking of the items for electronic screening. 

6.10.3 Preparations for Installation 

6.10.3-p1 The ANWI Contractor shall identify all required support facilities, 

including modifications or additions required, within one week of each site survey. 

This notification shall be in the form of a letter to the site POC, with a copy to the 

Purchaser’s Project Manager, accompanied by engineering drawings, checklists, or 

any other supporting information. Facilities support issues that represent Medium or 

High risk items shall be reflected in the Risk Log. 

6.10.3-p2 The ANWI Contractor shall provide the NNHQ site POC and a list of 

ANWI Contractor personnel who will be involved in site installation and activation, 

with a copy of both to the Purchaser Project Manager. 

6.10.3-p3 The ANWI Contractor shall monitor the progress of any required Site 

facilities preparations, and the progress of any required provision of input by the 

Purchaser and the Site, to ensure timeliness and quality of the preparatory work 

required from the Purchaser. The ANWI Contractor shall ensure that anything that 

may delay installation is brought to the attention of the Purchaser’s Project Manager 

promptly. 

6.10.3-p4 The ANWI Contractor shall prepare and conduct a Site Verification 

Survey no later than 30 (thirty) days prior to installation activities at the site. The 

purpose of the site survey is to verify that the information provided for the site is still 

valid. This is to confirm that the new building construction is in accordance with the 

site plans and drawing in the locations of interest for the ANWI Project. 

6.10.3-p5 The ANWI Contractor shall update and issue the Project Management 

Handbook to reflect provision of input by the Purchaser and the Sites. 

6.10.4 Capability and Service Implementation 

6.10.4-p1 The ANWI Contractor shall hold a daily meeting with the Purchaser’s 

site POC to agree on the work to be conducted during the day. 

6.10.4-p2 The ANWI Contractor shall ensure that the equipment to be installed in 

any of the relevant site facilities (as identified in the SOW, and agreed changes) has 

been tested. 

6.10.4-p3 The ANWI Contractor shall provide relevant acceptance evidence to the 

Purchaser’s site POC before installing any ANWI piece of equipment. 

6.10.4-p4 The ANWI Contractor shall unpack all NNHQ ANWI equipment at the 

installation location and dispose of packing materials as directed by the Purchaser's 

Site POC.



6.10.4-p5 The ANWI Contractor shall install the ANWI equipment supporting the 

ANWI services (as defined in Table 3.2) in the following locations: 

No. Services Installation Location 

1 

1.1 Service Management 

and Control(SMC) 

1.2 Information Assurance 

(IA) 

2 

SMC and IA Services 

Software installed on servers in both server rooms (SRs). 

Software installed on servers in both SRs. 


2.1 Processing Processing servers to be installed in both Server Rooms (SR). Full redundancy between 

the 2 SRs. 

2.2 Storage Storage devices to be installed in both SRs. Full redundancy between the 2 SRs. 

2.3 Printing & Scanning Servers to be installed in both SRs. The locations of the user printing and scanning 

devices are detailed in Annex F, Appendix 4. 

2.4 Network Infrastructure The Network Infrastructure Services will be installed or is (physically) integrated on/to 

all ANWI platforms. 

2.5 LAN LAN services shall be installed in a redundant manner in the two SRs, interconnected 

in a redundant way to the two TCFs and provide redundant services to the network end 

point through the Technical Equipment Rooms (TERs), National TERs(NTERs), and 

the Partner TERs (PTERs) Further details are in Annex F, Appendix 6. 

* The Wireless access points shall be installed across the whole NNHQ main building 

and staff centre to provide full coverage across the campus. 

3 

UCC (Unified Communications & Collaboration Services 

3.1 Voice Software installed on servers in both server rooms. Servers to be installed in both SRs 

and redundantly connected to TCF. 

3.2 Voicemail Software installed on servers in both server rooms. Servers to be installed in both SRs. 

3.3 VTC Software installed on servers in both server rooms. The service shall be available on 

the end user device. This may be a desktop device or a mobile device. 

3.4 E-mail Servers to be installed in both SRs 

3.5 Unified Messaging Software installed on servers in both server rooms. Servers to be installed in both SRs. 

3.6 Fax Software installed on servers in both server rooms. Servers to be installed in both SRs. 

3.7 Instant Messaging (IM) Software installed on servers in both server rooms. The service shall be available on 

the end user device. This may be a desktop device or a mobile device 

3.8 Presence Software installed on servers in both server rooms. The service shall be available on 


3.9 Directory Software installed on servers in both server rooms. Servers to be installed in both SRs. 

3.10 Collaboration Software installed on servers in both server rooms. The service shall be available on 


3.11 Mobility Software installed on servers in both server rooms. 

4 

Client-Provisioning Services 

4.1 Software deployment Software installed on servers in both SRs. 

4.2 Client devices Client devices will be prepared and deployed to the designated user locations (desks or 

remote locations). 

5 


5.1 GSM GSM coverage shall be provided across the NNHQ campus, both within the building 

and externally within the campus. 

5.2 GSM Blocking The GSM blocking capability shall be available at the NAC and EAPC Conference 





No. Services Installation Location 

rooms, and there shall be two mobile units which shall be transportable across the site. 

5.3 Wireless Blocking The Wireless blocking capability shall be available at the NAC and EAPC Conference 

rooms, and there shall be two mobile units which shall be transportable across the site. 

5.4 Site Security 

Communications 

(Radio) 

The mast(s) and associated antennas shall be installed on the campus. The exact 

location will depend on the location which provides full coverage of the campus. 

The security communications management servers shall be located in the two SRs. 

5.5 IPTV Servers to be installed in both SRs. The on-site IPTV service access point will be in 

both SRs. Any IPTV device shall be installed in the identified 425 end user locations. 

Table 6.1: Locations for ANWI services 

6.10.4-p6 The ANWI Contractor shall install all equipment in accordance with the 

applicable SDIP documents (References 1.1.1.3.1 – 1.1.1.3.3). 

6.10.4-p7 The ANWI Contractor shall connect all equipment to electrical power 

and communications interfaces. 

6.10.4-p8 The ANWI Contractor shall turn on all equipment and configure 

hardware and software settings to match the Product Baseline and site infrastructure 

configuration. 

6.10.4-p9 The ANWI Contractor shall ensure that all identified interfaces to 

systems and services as identified in the detailed design are operational. 

6.10.4-p10 The ANWI Contractor shall provide the approved SIVP to the 

Purchaser Site POC. 

6.10.4-p11 The ANWI Contractor shall execute the SIVPs for the NNHQ ANWI 

equipment installed in the site in order to demonstrate to the local Security 

Accreditation Authority (SAA) that the equipment complies with the CPS, SSRS and 

SISRS. 

6.10.4-p12 The ANWI Contractor shall upon completing an installation: 

A. Provide the Purchaser Site POC with a copy of the site installation and 

activation checklist and resolve any discrepancies identified. 

B. Obtain a System Statement of Conformance from the local Security 

Accreditation Authority and provide it to the Purchaser Site POC. 

6.10.4-p13 The ANWI Contractor shall respond within 24 hours to any problems 

reported by the Purchaser with installed but not yet activated NNHQ ANWI site. 

6.10.5 Installation Back Out 

6.10.5-p1 The ANWI Contractor shall uninstall any ANWI component found to be 

interfering with IOC services (table 6.1). 

6.10.5-p2 The ANWI Contractor shall ensure that after uninstalling a capability 

that restoration of the pre-existing services is again operational. 

6.10.5-p3 The ANWI Contractor shall analyse the problematic component and 

after correcting the error retest the component in the ITS before reinstalling it on the 

network. 



6.10.6 ANWI Service Activation 

6.10.6-p1 

Activation. 



Upon Purchaser approval the ANWI Contractor shall conduct Service 

6.10.6-p2 Service Activation shall comprise: 

A. The establishment of live connections and activation of the NNHQ ANWI 

site. 

B. The performance of Service Certification Tests. 

C. The testing of service levels as specified in the SLA. 

6.10.6-p3 The ANWI Contractor shall provide specific service requests to the 

Purchaser to provide the facilities, operational links, and interfaces required for 

System Activation Tests. 

6.10.6-p4 The ANWI Contractor shall conduct Service Certification Tests as 

defined below and in compliance with the overall System Tests Process as identified 

in paragraphs 6.13-16. 

6.10.6-p5 During the Service Certification Testing the ANWI Contractor shall 

demonstrate that the equipment installed at all affected sites complies with the 

operational readiness and performance requirements and complies with the security 

requirements as specified in the of the NNHQ ANWI Capability Service requirements, 

SSRS and SISRS. 

6.10.6-p6 The Service Certification Testing shall include the exchange of test 

traffic between the activated NNHQ ANWI sites and the monitoring of operational 

performance to confirm the operational readiness and reliability of the NNHQ ANWI 

services at affected sites. 

6.10.6-p7 Service Certification Testing shall be conducted for a minimum of two 

weeks, based on the individual test criteria. 

6.10.6-p8 The completion of Service Certification Testing shall be subject to the 

Purchaser's confirmation that all Service Certification Tests have been completed 

successfully for requesting IOC. 

6.10.7 ANWI System Activation Testing 

6.10.7-p1 Upon Purchaser authorisation the ANWI Contractor shall conduct 

service interoperational testing as defined below and in compliance with the overall 

Release Build and Test Phase process as defined in paragraph 6.7. 

6.10.7-p2 The ANWI Contractor shall develop and carry out System Activation 

Tests of NNHQ ANWI services to establish benchmarks for service performance and 

service reliability, maintainability, and availability. 

6.10.7-p3 The ANWI Contractor shall develop and carry out System Activation 

Tests (demonstrating service interoperability) of NNHQ ANWI to prove end-to-end 

services provision to end-users to support FOC. 

6.10.7-p4 The ANWI Contractor shall develop and carry out ANWI System 

Activation Tests to prove that ANWI trained NATO personnel can provide the ANWI 

capability services for NONO services as specified in the SLA. 





6.10.7-p5 The Purchaser shall observe the tests and have the ANWI Contractor 

perform additional selected testing tasks to confirm compliance with ANWI 

requirements. 

6.10.7-p6 The completion of System Activation Tests shall be subject to the 

Purchaser's confirmation that all tests have been completed successfully. 

6.10.8 Physical Configuration Audits 

6.10.8-p1 The ANWI Contractor shall schedule and chair the Physical 

Configuration Audit (PCA) for each site (Main ANWI campus, Bâtiment Z and remote 

sites) following Site Activation. The objective of the PCA is to verify that the delivered 

CIs correspond with the NNHQ ANWI Product Baseline documentation. 

6.10.8-p2 The PCA shall include visual inspection of all hardware and 

documentation CIs, and visual verification of the presence and correct configuration 

of all service and software CIs. 

6.10.8-p3 

Site POC. 

6.10.8-p4 

6.10.9 On-Site Training 

6.10.9.1 User Training 

The ANWI Contractor shall co-ordinate the PCA with the Purchaser's 

Successful completion of PCA establishes the site baseline. 

6.10.9.1-p1 The ANWI Contractor shall provide all users with an appropriate 

clientenvironment training session (as noted below). 

6.10.9.1-p2 The ANWI Contractor’s client environment training session shall not 

exceed 2 hours in length 

6.10.9.1-p3 

The ANWI Contractor shall conduct the training. 

6.10.9.1-p4 The ANWI Contractor’s client environment training session shall be 

tailored to include: 

A. Use and access of the print/scan service 

B. Use of the UCC service (as applicable to the type of user and security 

domain) 

C. Use and access of the mobile client (applicable to mobile Business users) 

6.10.9.1-p5 The ANWI Contractor shall post the client environment training 

material on the ANWI Self-service portal as well as link the material to the 

appropriate service listed in the ANWI service catalogue. 

6.10.9.2 Training Needs Analysis 

6.10.9.2-p1 The ANWI Contractor shall perform a training needs analysis of the 

on-site support staff. 

6.10.9.2-p2 The ANWI Contractor shall use the ANWI capabilities and services 

(Annexes and Appendices) to determine what tasks the NATstaff is able to 

satisfactorily perform. 





6.10.9.2-p3 

report. 

The ANWI Contractor shall report the findings in the site survey’s 

6.10.9.3 NONO Services 

6.10.9.3-p1 The ANWI Contractor shall provide on-site training to System 

Administration personnel designated by the Purchaser’s Site POC on all tasks 

required to operate the system, perform daily maintenance and administration, 

disaster recovery, and first-level problem isolation. 

6.10.9.3-p2 The on-site training shall be structured according to the First- and 

Second-Level support concept. 

6.10.9.3-p3 The on-site training for System Administration personnel shall not 

exceed 3 days per session for First-Level personnel and 5 days per session for 

Second-Level personnel. 

6.10.9.3-p4 The ANWI Contractor shall also provide on-site training for 50 

designated users on the ANWI capabilities. 

6.10.9.3-p5 

The user on-site training shall not exceed 1 day per session. 

6.10.9.3-p6 The Purchaser will provide the following basic facilities to support 

training: Equipment room, power supply, tables, chairs. 

6.10.9.3-p7 The ANWI Contractor shall provide all other facilities, equipment 

and services necessary, to include any necessary servers, workstations etc…, to 

carry out the on-site Training activities. 

6.10.10 Migration to the ANWI Environment 

6.10.10-p1 The ICT migration to the NNHQ is a complex process with a lot of 

interdependencies between the NNQH Programme projects (PNWI, GCC, ESS, AVI, 

BMS), ICTM business applications migration and the ANWI. The migration of the 

ICTM Business Applications and related ESS and AVI services from the old building 

will be dependent on the availability of the ANWI. Also the migration is dependent on 

the installed capabilities services that have been successfully tested. See Figure 6.2. 





Figure 6.2: Migration overview. 

6.10.10-p2 The overall New NATO HQ ICT migration strategy and planning 

requirements, to which the ANWI project is an integrated part, issued by HQPO and 

governed by the DPRC, are provided in reference 1.1.1.7.5. 

6.10.10-p3 The migration of services, applications, configuration settings, and 

data is split into: 

A. ANWI related core and infrastructure services, applications, configuration 

settings, and data. These are within the scope of the ANWI Contractor’s 

direct responsibility. 

B. AVI, BMS and ESS related data and applications are the responsibility of 

HN Belgium. However, the ANWI Contractor shall provide support and 

advice on their migration and integration with ANWI capability services, to 

ensure that the overall migration processing and storage support is 

seamless and successful. 





C. Business Applications, configuration settings and data are the 

responsibility of Host Nation ICTM. However, the ANWI Contractor shall 

provide support and advice on their migration and integration with the 

ANWI capability services, to ensure that the overall migration is seamless 

and successful. 

D. Migration and transition of user communities and business processes will 

be undertaken on a progressive basis, with users being trained “just in 

time” for their migration from their current to their new location. These are 

within the scope of the NNHQ HQPO transition team. The ANWI 

Contractor shall provide support to this process, directly via the ANWI 

related core and infrastructure services provisioning, and indirectly via the 

ANWI Contractor support to business application migration. 

6.10.11 ICT Migration Key Milestones 

6.10.11-p1 The ANWI contractor shall create and implement a migration plan 

that satisfies the key migration milestones as shown in Annex A. 

6.10.12 ANWI Contractor Task 

6.10.12-p1 The ANWI Contractor shall execute the migration in close 

coordination with the Purchaser. 

6.10.12-p2 The ANWI Contractor shall use automated tools for migration and 

migration roll-back. Manual interventions for migration activities will only be allowed 

as an exception that the ANWI Contractor shall offer for approval to the Purchaser. 

6.10.12-p3 The ANWI Contractor shall migrate the Current Systems and 

Services as related to the ANWI Capability Services as specified in table 6.3. The 

current ICT environment that shall be used as the basis for the migration planning is 

specified in Annex B. 

6.10.12-p4 

more detail. 

Table 6.3 Describes the ANWI Capability Services Migration task in 

No. Migration Category Acronym Migration Responsibility 

1 Migration of Core Services. Mig-CS ANWI Contractor Task. 

2 Migration of other services. Mig-O Migration of current capability at the NHQ site to the 

NNHQ site. 

3 New service / capability at NNHQ. NoMig-NS No migration requirement. 

4 Current service / capability that will 

not be migrated. 

NoMig 

Legend for Table 6.3 (below) 

To be clearly identified as a part of the migration 

planning. No migration requirements. 

No. Services Migration Requirement 

1 

1.1 Service Management and 

Control(SMC) 


Mig-O. The extent of the SMC migration requirement will depend on the SMC 

capability and the how much of it will be the same as the current site capability. 

Where the tools are the same they will have the relevant setting migrated, where 

the capability is new the current knowledge base will be migrated. 





1.2 Information Assurance (IA) NoMig-NS. The IAM configuration will have to be developed. 

2 


2.1 Processing NoMig of physical hardware. Detailed service configurations shall be developed 

and implemented by the ANWI Contractor. The NATO setting and configurations 

will be provided by the Purchaser as PFI. 

2.2 Storage NoMig of physical hardware. Detailed setting (including security) setting will be 

provided by the Purchaser as PFI, which the ANWI Contractor shall implement. 

2.3 Printing & Scanning NoMig of physical hardware. This will be a new service. New printer 

configurations will be developed for the new site, as a part of the follow me print 

concept. 

2.4 Network Infrastructure 1.3.1.1 NoMig of physical hardware. 

A new network level connectivity and routing design will need to be provided as a 

part of the overall ANWI design. 

2.5 LAN NoMig of physical hardware. Detailed setting (including security) setting will be 

provided by the Purchaser as PFI, which the ANWI Contractor shall implement. 

3 

UCC (Unified Communications & Collaboration Services 

3.1 Voice Mig-CS. Migration of address lists and current user telephone numbers. 

This applies for NU voice oice as both UCC and as a separate service. 

3.2 Voicemail Goes with voice. 

3.3 VTC Video Desktop - NoMig-NS. New configurations will be developed. 

Video VTC/VMR – existing address books and VTC number shall be migrated. 

3.4 E-mail Mig-CS. E-mail configurations, and constraints (e.g. user maximum size, address 

lists) shall be migrated. If possible individual user configuration and user profiles 

to be migrated. 

3.5 Unified Messaging NoMig-NS. New configurations will be developed. 

3.6 Fax Mig-CS. New configurations will be developed but the current directory need to 

be migrated 

3.7 Instant Messaging (IM) NoMig-NS. New configurations will be developed. 

3.8 Presence NoMig-NS. New configurations will be developed 

3.9 Directory 

3.10 Collaboration NoMig-NS. New configurations will be developed 

3.11 Mobility NoMig-NS. New configurations will be developed 

4 Client-Provisioning Services 

4.2 Software deployment NoMig. New configurations will be developed 

4.1 Client devices NoMig. New configurations will be developed 

5 


5.1 GSM NoMig-NS. New configurations will be developed 

5.2 GSM Blocking NoMig-NS. New configurations will be developed. 

5.3 WiFi Blocking NoMig-NS. New configurations will be developed. 

5.4 Site Security Communications 

(Radio) 

Mig-O. Migration of the current radio device address-list and users numbers. 

Migration of management application settings. 

5.5 IPTV NoMig-NS. IPTV will need configuration to provide the required channels to the 

end users. 

6 Common User Services 

6.1 File services Mig-CS. The file structure, file naming convention shall be migrated. Note that 

ICTM may wish to consolidate file structures before migration. Normally this 

should make the migration process simpler. 

6.2 Web browsing Mig-CS. Browsing configuration for application and user profiles to be migrated. 





Table 6.3: ANWI Capability Services Migration task overview (should be table 2) 

6.10.12-p5 The ANWI Contractor shall provide migration support to each 

application that belongs to the categories of HN BEL related ESS/AVI application or 

HN ICTM business applications as specified in table 6.4. 

6.10.12-p6 The ANWI Contractor shall, for each of the identified applications as 

required in 6.14.4.5, perform the following tasks: 

A. Determine the application migration support requirements with the 

Purchaser and in close cooperation with HN ICTM: 

1. Determine and agree the detailed schedule. 

2. Determine all the ANWI services and interfaces that are affected. 

3. Determine ANWI Contractor integration and customisation efforts for 

each of the affected services/interfaces. 

4. Determine the ANWI Contractor support requirements for CAT, ITS and 

Operational testing. 

5. Determine the ANWI Contractor operations and support requirements 

for the duration of the application migration. 

B. Determine the Migration risk and develop an ANWI roll-back procedure 

derived from the Application Migration roll-back procedure. 

C. Execute the required ANWI Contractor Application migration support 

activities according to the plan. 

6.10.12-p7 Table 6.4 shows the categories of applications for which the ANWI 

Contractor shall provide migration support. 

No Security Domain Descriptions 

Services 

1 ICTM business application Services 


1.1 Specialist Applications Y Y Y Y HQ applications with specific functionality in 

support of specific business processes. A list of 

applications in this category is provided in 

Annex B. 

1.2 EIM applications Y Y Y Y Suite of applications related to Enterprise 

Information Management (EIM). A list of 

applications in this category is provided in 

Annex B. 

1.3 ERP applications Y Y Y Y Suite of applications related to Enterprise 

Resource Planning. A list of applications in this 

category is provided in Annex B. 

2 HN BEL Applications 

2.1 ESS related apps/data - - Y - ESS Access Card ID information migration as 

specified in Annex B as a specialist 

application. 

2.2 AVI related applications /data 

migration 

- - Y Y AV data storage migration as specified in 

Annex B as a specialist application. 

Table 6.4: Application Services Categories that require ANWI support 




6.10.13 Migration Concept and Business Principles 


6.10.13-p1 The ANWI Contractor shall implement the ICT migration concept to 

transfer the existing Headquarters business infrastructure into the NNHQ without 

adverse effect upon NATO’s on-going operational capability. 

6.10.13-p2 The ANWI Contractor shall apply the following business principles 

to both the migration of ANWI related services as well as for the support to Business 

and AVI/ESS related applications: 

6.10.13-p3 There shall be a full continuity of service provision, with no loss of 

service to users. 

6.10.13-p4 There shall be a minimal disruption to the users and migration 

activities will be transparent to all involved stakeholders. 

6.10.13-p5 The migration activities shall preserve the NATO security posture 

and will not adversely compromise NATO classified information pre-, during or after 

migration. 

6.10.13-p6 Each migration activity shall include an input and support to a 

communication campaign. 

6.10.13-p7 Each migration activity will include instructions for the pre- and postmigration 

user involvement. 

6.11 Review and Close 

6.11-p1 This phase aims to collect experience and feedbacks, performance targets 

and achievements. Most commonly this phase happens once, and overlaps with the 

Project Closure phase. 

6.11-p2 The ANWI Contractor shall organize this phase accordingly with the ITIL 

best practice and hand-over all the documentation to the Purchaser. 

6.12 Knowledge Management 

6.12-p1 The purpose of this process is to share ideas, perspective, experience and 

information, ensuring that all of them are available to Contractor’s and Purchaser’s 

decision makers to take at the right time informed decision. 

6.12-p2 The ANWI Contractor shall create a Service Knowledge Management 

database (per Annex E Appendix 1) for the NNHQ O&M Authority that will be used to 

identify risk areas for the various capabilities and services. 

6.12-p3 The ANWI Contractor shall use the Knowledge Management database to 

hold capability and service performance baselines. 

6.12-p4 The ANWI Contractor shall use the Knowledge Management database to 

estimate a service’s cost and the NNHQ O&M Authority’s cost of a service 

(ownership) 

6.12-p5 The ANWI Contractor shall use the Knowledge Management database 

identify service catalogue delivery constraints. 




6.13 Initial Operating Capability (IOC milestone) 


6.13-p1 IOC is the act by which the Purchaser has evaluated the ANWI services 

being provided at the all NNHQ sites and remote sites and has determined that they 

meet the requirements to request IOC. 

6.13-p2 The ANWI Contractor shall have completed the following actions prior to 

requesting IOC: 

A. Successful completion of Site installation and Service Activation, including 

Purchaser approval of the test reports. 

B. Completion of SCT (paragraph 6.8.4). 

C. Completion of the on-site training of NATO personnel involved in 

operations and maintenance of NNHQ ANWI for NONO services (only if 

NONO option is exercised). 

D. Delivery of all required documentation. 

E. Inventory of delivered items. 

6.13-p3 The ANWI contractor shall follow the required steps and responsibilities for 

providing Service Level Targets (SLTs) as specified in their appendices. 

6.13-p4 The ANWI Contractor shall notify the Purchaser in writing that the NNHQ 

ANWI site is offered for IOC and it shall have the installation activation checklist 

attached. 

6.13-p5 After satisfactory completion of the IOC review and the issuing of the 

System Statement of Conformance, the Purchaser will accept delivery of the NNHQ 

IOC ANWI site. 

6.13-p6 Responsibility for system operation and performance shall remain with the 

ANWI Contractor for the duration of the initial and any follow-on Operational Support 

tasks through FSA. 

6.13.1 ANWI System Activation Testing 

6.13.1-p1 The ANWI Contractor shall conduct System Activation Testing as 

defined below and in compliance with the overall ANWI Testing Process. 

6.13.1-p2 The System Activation tests shall verify NNHQ ANWI services 

functionality at the site, demonstrate interfaces with local and external systems as 

required, and evaluate the overall readiness of the site for System activation. 

6.13.1-p3 The Purchaser will provide the facilities, operational links, and 

interfaces required for System Activation Tests. 

6.13.1-p4 The Purchaser will observe the tests and have the ANWI Contractor 

perform additional selected testing tasks to confirm compliance. 

6.13.1-p5 Except for any specialised test equipment such as traffic generators, 

etc., the ANWI Contractor shall only use the site NNHQ ANWI equipment for System 

Activation Testing and no operational traffic shall be authorised. 

6.13.1-p6 

The ANWI Contractor shall check that all services are migrated. 



6.13.2 ANWI Site Activation 





6.13.2-p1 After completion of site installation activities and upon authorisation by 

the Purchaser, the ANWI Contractor shall conduct Final Site Testing . 

6.13.2-p2 The site activation will be achieved in two steps: 

A. Provisional Site Activation (PSA): the ANWI Contractor shall provide the 

ANWI IOC services as specified in table 6.2 

B. Site Activation (SA): The ANWI Contractor shall achieve all ANWI services 

to be operational and where ANWI NONO capabilities and services are 

handed-over to the Purchaser. 

6.13.2-p3 PSA shall consist of: 

A. The establishment of connections between the NNHQ ANWI 

implementation in the site, the NATO operational systems at the old NATO 

Headquarters site, remote NNHQ locations and other NATO locations via 

the NGCS network. 

B. The performance of provisional Final Site Tests. 

6.13.2-p4 SA shall consist of: 

A. The confirmation of connections between the NNHQ ANWI 

implementation in the site, the NATO operational systems at the old NATO 

Headquarters site, remote NNHQ locations and other NATO locations via 

the NGCS network. 

B. The performance of Final Site Tests. 

6.13.2-p5 The ANWI Contractor shall be responsible for integration of NNHQ 

ANWI. This means both the integration of the various HW products and SW products 

that constitute NNHQ ANWI and the integration of NNHQ ANWI with the existing 

NATO systems specified in the Annexes and Appendices. 

6.13.3 “As Built” Drawings and Documentation 

6.13.3-p1 The ANWI Contractor shall provide an “as built” drawing of the installed 

capability at IOC. 

6.13.3-p2 The ANWI Contractor shall document the “as built” physical 

configuration making appropriate changes to the installation and configuration 

document detailing the configuration settings and loaded parameters. 

6.13.3-p3 The ANWI Contractor “as built” drawing and document shall be under 

the Contractor’s configuration control. 

6.14 Initial Operating Capability (IOC) Acceptance 

6.14-p1 The ANWI Contractor shall have successfully completed and/or delivered 

the following to have IOC accepted: 

A. Provision of all supplies and services required for IOC as specified 

(above). 

B. Completion of the Service Certification Tests including approval of the 

operational test reports by the Purchaser. 

C. Successful completion of Site and Service Certification Testing, including 

Purchaser approval of the test reports.



D. Completion of the on-site training of NATO System Administration 

personnel involved in operations and maintenance of ANWI for NONO 

services (only if NONO option is exercised). 

E. Delivery of all required documentation (including ILS documentation and 

Operational Support Plan). 

F. Inventory of delivered items. 

G. The Product Baseline (a link to the current version on the Project Website 

is sufficient). 

H. Report of all outstanding Off-specification Reports related to the site. 

i. Documentation relevant to the IOC (e.g. as-built drawings, handbooks, 

quality assurance reports, manuals). 

J. Integration of all back-end services be they ANWI or NATO PFE provided 

K. Initial or updates to ANWI service & maintenance manuals and SOPs. 

L. A copy of the System Statement of Conformance signed by the local SAA 

for the NNHQ ANWI Site. 

6.14-p2 After satisfactory completion of the IOC review and the issuing of the 

System Statement of Conformance, the Purchaser will accept IOC for the NNHQ 

ANWI back-end capabilities and services. 

6.14-p3 The ANWI Contractor shall be responsible for system operation and 

performance through FOC. 

6.15 Final Operating Capability (FOC milestone) 

6.15-p1 The ANWI Contractor shall request a FOC meeting where the ANWI 

Contractor shall demonstrate that all ANWI services are conformant to the agreed 

SLAs. 

6.15-p2 The ANWI Contractor’s notification shall include the following information: 

A. The Product Baseline (a link to the current version on the Project Website 


B. Report of all outstanding Off-specification Reports related to the site. 

C. Documentation relevant to the Partial System Acceptance (e.g. as-built 

drawings, handbooks, quality assurance reports, manuals). 

D. Initial or updates to User training and Custom NNHQ ANWI manuals. 

E. A copy of the System Statement of Conformance signed by the local SAA 


F. Site Implementation checklist. 

G. Successful completion of System Acceptance Testing including approval 

of the operational test reports by the Purchaser. 

6.16 Final Operating Capability (FOC) Acceptance 

6.16-p1 FOC is the act by which the Purchaser has evaluated the operational ANWI 

NNHQ site and remote sites and has determined that it meets the requirements of 

the Contract. 







6.16-p2 The ANWI Contractor shall have completed the following actions to achieve 

FOC: 

A. Completion of the Client-device installation and testing including approval 

of the Operational Tests report by the Purchaser. 

B. Successful acceptance of the end-to-end user testing of all client services. 

C. Provision of all supplies and services required for FOC. 

D. Completion of the on-site training of NATO staff 

E. Delivery of all client device required documentation 

F. Inventory of delivered items. 

G. The Product Baseline (a link to the current version on the Project Website 


H. Report of all outstanding Off-specification Reports related to the site. 

I. Documentation relevant to the Partial System Acceptance (e.g. as-built 

drawings, handbooks, quality assurance reports, manuals). 

J. Initial or updates to User and Custom NNHQ ANWI training manuals. 

K. A copy of the System Statement of Conformance signed by the local SAA 


L. All actions closed. 

M. No outstanding issues with System Activation Testing. 

N. All risks closed. 

6.16-p3 After satisfactory completion of the FOC review and the issuing of the 

System Statement of Conformance, the Purchaser will accept FOC for the NNHQ 

ANWI site. 

6.16-p4 Responsibility for system operation and performance shall remain with the 

ANWI Contractor for the duration of the initial and any follow-on Operational Support 

tasks. 

6.16-p5 The ANWI Contractor shall maintain a status report of document delivery 

based on the Contract Data Requirements List (CDRL) as part of the Project 

Progress Report. The CDRL shall contain the status of all documentation to be 

provided under the Contract: Title, reference, quantity and status (i.e. draft, 

approved, revision level). A final version of the CDRL shall be delivered to the 

Purchaser prior to Final Operating Capability. 

6.17 Final System Acceptance (FSA milestone) 

6.17-p1 The ANWI Contractor shall request a FSA meeting after he hasdelivered 

and handed-over everything which is part of 6.15 Final Operating Capability (FOC) 

Acceptance: 

A. All contract activities fully executed. 

B. All deliverables acceptedand handed over to the Purchaser. 

C. Provided six (6) months of service support to the NNHQ O&M Authority. 

D. Produced acceptable SLA reports per Section 7. 

E. Validation that warranty was transferred to Purchaser. 

F. Trained NNHQ O&M Authority service staff how to create the SLA reports. 

G. Trained NNHQ O&M Authority how to perform the data capture and trend 

analysis to produce the reports. 

H. No outstanding issues with Final Site Testing.



SECTION 7. 

ANWI SERVICE AND SYSTEM OPERATIONS 

7.1 ITIL Service Operation 

7.1-p1 The Processes that are part of Service Operations are; 

A. Incident Management 

B. Problem management 

C. Request fulfilment 

D. Access Management 

E. Event Management 

7.1-p2 The purpose of Service Operation is the coordination and the conduct of all 

the activities and processes that are necessary for delivering and managing all the 

services at the agreed levels to business users and customers. 

7.2 ANWI Service Operation Functions 

7.2.1 Support Overview 

7.2.1-p1 The ANWI Contractor shall implement three (3) levels of operational 

support following the NATO Support Authority best practice which are identified as: 

First Level, Second Level and Third Level of Support. 

7.2.2 First Level Support 

7.2.2-p1 First Level support shall constitute the routine system operation, system 

administration, and system maintenance tasks required to maintain NNHQ ANWI 

services at a site. These tasks include providing local user support, account 

management, system monitoring, backups, and disaster recovery. 

7.2.2-p2 The NNHQ ANWI First Level Support function shall use the incident 

management and trouble-ticketing system for modifying, tracking, and closing trouble 

tickets in this system. 

7.2.2-p3 The NNHQ First Level Support interfaces with and engages the user to 

resolve user ICT work-orders / trouble tickets. 

7.2.3 Second Level Support 

7.2.3-p1 Second Level Support shall constitute the centralised system operation, 

administration, and management tasks performed at the Primary and Alternate sites 

to maintain NNHQ ANWI services across the Product baseline. 

7.2.3-p2 Second Level Support supports fault isolation, system-wide 

performance monitoring and reporting, and in-depth technical assistance to First- 

Level support staff. 

7.2.3-p3 The NNHQ ANWI Second Level Support function shall be available to 

NNHQ ANWI users and Administration staff by telephone, unclassified facsimile, and 

email (NATO SECRET, NATO RESTRICTED, NATO UNCLASSIFIED, EAPC 

CONFIDENTIAL or Internet mail). 





7.2.3-p4 The NNHQ ANWI Second Level Support function shall use the incident 

management and trouble-ticketing system for opening, modifying, tracking, and 

closing trouble tickets, and log all requests in this system. The ANWI Contractor shall 

summarise trouble ticket statistics, assess trends, and recommend changes to 

improve system performance as part of the System Status Report. 

7.2.3-p5 The NNHQ ANWI Service Desk and Second Level Support function 

shall be manned by the ANWI Contractor on NNHQ business days from 0800 to 

1830 CET Monday-Thursday and from 0800 to 1700 Friday. 

7.2.3-p6 The NNHQ ANWI Service Desk shall be available to NNHQ ANWI 

users and Administration staff by telephone, unclassified facsimile, and email (NATO 

SECRET, NATO RESTRICTED, NATO UNCLASSIFIED, EAPC CONFIDENTIAL or 

Internet mail). 

7.2.3-p7 The ANWI Contractor shall provide 24-hour support when requested by 

the Purchaser to support operational needs or events. A request for 24-hour support 

will be requested by the Purchaser to the ANWI Contractor not less than a week 

before the needed effort. Note, the ANWI Contractor may need to be flexible in 

supporting an urgent 24-hour support request if an emergency situation occurs. 

7.2.3-p8 Unless otherwise specified agreed, support outside NNHQ business 

days shall not exceed a total of 180 hours in a one-year period. 

7.2.4 Third Level Support 

7.2.4-p1 Third Level Support shall maintain the core expertise for all NNHQ 

ANWI components and services, including configuration management of NNHQ 

ANWI components, administration of the NNHQ ANWI, performance assessment, 

Off-specification reporting, and maintenance engineering. 

7.2.4-p2 Third Level Support includes the maintenance and administration of the 

NNHQ ANWI ITS and its use in analysing operational problems and validating 

changes to the Product Baseline as well as the link between the operational Second 

Level Support and factory ANWI corporate technical support staff. Third Level 

Support is provided by the ANWI Contractor’s corporate technical experts and/or 

manufacturer support. 

7.2.5 ITIL Mapping 

7.2.5-p1 The ANWI Contractor shall map the relations between the NATO three 

(3) levels of support and the ITIL V3 framework in the ILSP todetermine the 

manpower needs to support the ANWI contractor based service design where the 

following paragraphs help define the ITIL Service Operation functions: 

A. Service Desk 

B. Technical management 

C. Application Management 

D. IT Operations Management 

7.2.6 Service Desk 

7.2.6-p1 The NNHQ ANWI Service Desk shall be manned by the NNHQ O&M 

Authority as defined in 2.3.3-p3 and represents the single point of contact for users 

for the day-by-day operations. 







7.2.6-p2 The ANWI Contractor shall recommend one of the ITIL standard 

Service Desk models for implementation at NNHQ (Local Service Desk Structure, 

Centralized Service Desk Structure, or Virtual Service Desk Structure) for Purchaser 

approval. 

7.2.7 Technical Management 

7.2.7-p1 The ANWI Contractor shall provide technical management (referred to 

the groups / departments / teams that provide the technical expertise) for the for the 

ANWI services. 

7.2.7-p2 The ANWI Contractor’s Technical Management shall provide support 

for maintaining a stable and resilient ICT infrastructure, with the final aim to support 

the business value to users through plans / decisions / actions support. 

7.2.8 IT Operation Management 

7.2.8-p1 The NNHQ O&M authority as defined in 2.3.3-p3 shall be responsible 

for the ANWI’s IT Operation Management of both ITIL defined Operations and 

Facilities. 

7.3 ANWI Service Operations Processes 

7.3.1 Incident Management 

7.3.1-p1 The purpose of Incident Management is to restore as soon as possible 

the normal service operation, minimizing the operational impact on NNHQ business. 

7.3.1-p2 The ANWI Contractor Incident Management process shall identify all 

those events that disrupt or could disrupt an ANWI service, and can be 

communicated by the users through the service desk or directly through an ANWI 

provided automated tool. 

7.3.1-p3 The ANWI Contractor shall provide a tool for the Service Desk if the 

current HQ’s Service Desk PFE tool is determined to be insufficient. The tool shall 

manage incidents, via trouble tickets, which cause an unplanned interruption to a 

service or reduction in the quality of the service. The technical requirements for the 

service desk tool are provided by the Service Management and Control Specific CoI 

Services, Section 13.1. 

7.3.1-p4 The ANWI Contractor shall configure the Service Desk tool to support 

the Service Desk service and address failures, technical/operational questions or 

user queries. 

7.3.1-p5 The ANWI Contractor shall configure the tool to allow the Service Desk 

to log new incidents, their resolution and adjust timescales for 

resolution/escalation/workarounds. 

7.3.1-p6 Each trouble ticket incident shall: 

A. Be uniquely identified (by a ticketing number system). 

B. Have symptoms described. 

C. Be categorised. 

D. Be prioritised (major incidents, minor, etc.). 

E. Be (optionally) linked to a problem record.



F. Be (optionally) linked to a change. 

G. Have a related CI. 

H. Have a resolution. 

I. Have a date of occurrence. 

J. Add a user with contact information. 

K. Have the status tracked (Open, In Progress, Resolved, closed). 

7.3.1-p7 The ANWI Contractor shall configure the Service Desk tool to be linked 

to the ANWI’s configuration management database and the management’s 

monitoring tool. 

7.3.1-p8 The ANWI Contractor shall configure the tool to track the incident 

response and resolution performance against the target per the agreed SLA. 

7.3.1-p9 The ANWI Contractor shall configure the tool to interconnect, leverage 

and update the Service Knowledge Management System. 

7.3.1-p10 The ANWI Contractor shall configure the tool to provide a visual (stepby-step) 

troubleshooting model on how to handle incidents; time thresholds for 

completion and escalation; and what experts to engage for follow-on actions/queries. 

7.3.1-p11 The ANWI Contractor shall configure the tool to provide and support a 

knowledgebase of previously resolved incidents. 

7.3.1-p12 The ANWI Contractor shall leverage and agreed (with the Purchaser) 

Incident Management Process, with definite steps like: Identification, Logging, 

Categorization, Prioritization, Initial Diagnosis, Escalation, Resolution, and Recovery. 

7.3.1-p13 Any incident that exceeds the targeted timescale shall be automatically 

escalated to higher management for action and prioritisation. 

7.3.2 Problem Management 

7.3.2-p1 The Problem Management tool shall manage the Problems’ lifecycle 

from the first identification, further down to the identification, counter-measures and 

eventual resolution. 

7.3.2-p2 The Problem Management process shall support the ANWI lifecycle by 

preventing problems and their subsequent incidents; minimizing the impact of 

incidents; and elimination of recurring incidents. 

7.3.2-p3 The incident management tool’s records shall be used to provide trend 

analysis of similar problems in order to diagnose the root cause of incidents for the 

resolution of the problem be it reactive or proactive. 

7.3.2-p4 Problem resolutions or workarounds shall be released after being 

successfully tested, approved for release and documented in the change and 

configuration management systems. 

7.3.2-p5 The problem’s resolution shall be assessed against the SLA’s 

availability, capacity and continuity targets. 

7.3.2-p6 The ANWI Contractor shall reflect the resolution of all problems in the 

CI’s documentation, settings and baseline. 





7.3.2-p7 The Problem Management process shall manage all the type-ofproblem 

related entities: Problem, Workaround, Known Error, and Known Error 

Record so that: 

A. The ANWI Contractor shall setup a Known Error Database (KEB) and a 

Problem Management Process, there are identified all the problem 

lifecycle stages: Detection, Logging, Categorization, Prioritization, 

Investigation, and Diagnosis; the process must also identify when and if is 

possible to use a work around, or when a change is needed, or when a 

resolution is found. 

B. The information from the Problem Managementprocess shallfeed the CSI 

process. 

7.3.3 Request Fulfilment 

7.3.3-p1 The purpose of Request Fulfilment is to manage the lifecycle of all 

users’ requests that belong to standard predefined and approved services. 

7.3.3-p2 This process provides a channel to discuss also general information, 

complaints and general queries. 

7.3.3-p3 The ANWI Contractor shall configure the Request Fulfilment tool for the 

Service Desk to process user requests to receive Service Catalogue advertised 

services. 

7.3.3-p4 The Service Desk will need to be able to provide users with information 

about a service’s availability; the procedure to obtain them; to request software; 

provide general service information; address user complaints and user comments on 

offered services. 

7.3.3-p5 The ANWI Contractor shall configure the tool to publish and manage 

the appropriate ANWI security domain’s Service Catalogue on that security domain’s 

network for user consumption. 

7.3.3-p6 The ANWI Contractor shall configure the tool to create a service 

request template, that is accompanied with a simple workflow which requires 

financial and management approval before the request for a service can be 

submitted to ICTM for deployment. 

7.3.3-p7 The approved request shall add the request to the configuration 

management database, note delivery date; add to the SLA reporting and 

management tool. 

7.3.4 Access Management 

7.3.4-p1 The purpose of access management is to manage the rights of users to 

use a service (resource) or groups of services (resources). 

7.3.4-p2 This process shall offers also the functionalities to execute the Active 

Directory policies and granular (file level) security settings defined in the security 

documentation. 

7.3.4-p3 ANWI access management shall be focused on availability (authorised 

times per the SLA), and information security (confidentiality, availability and integrity). 







7.3.4-p4 The ANWI Contractor shall use the Active Directory (AD) or any other 

federated service directory as the primary means of providing confidentiality and 

access to ANWI data. 

7.3.4-p5 Use of means other than that mentioned under 7.1.5.2 to achieve ANWI 

data confidentiality and access shall be authorised by the Purchaser and its 

justification be provided in the Contractor provided ANWI Design, reflected in the 

SSRS, and SRA. 

7.3.4-p6 The ANWI Contractor shall interface with and use the NATO Enterprise 

Directory Service (NEDS), LDAP and NPKI enabled federated Identity and Access 

Management services to grant users outside the NATO Single Forest Single Domain 

access to NATO HQ data. 

7.3.4-p7 The ANWI Contractor shall provide a capability for an authorised NATO 

user to view the names of users/groups having access to the targeted information. 

7.3.4-p8 The ANWI Contractor shall configure the tools to audit and log failed 

logon attempts and access not granted events in the ANWI. 

7.3.5 Event Management 

7.3.5-p1 The purpose of event management is to manage the events in all their 

lifecycle stages, from the detection, identification, and the determination of the 

appropriate control action. 

7.3.5-p2 The scope of Event Management is very large, and shall include: 

A. Software licensing 

B. Software monitoring 

C. Security status 

D. Intrusion detection 

E. Environmental conditions 

F. Any CIs status 

7.3.5-p3 The ANWI Contractor shall ensure that the Service Desk and the 

designated Operations and Support positions inside the NNHQ and at remote 

locations, have access to the ANWI’s configuration items for the purpose of 

generating and detected occurrences that have a negative impact on either the 

infrastructure or other ANWI provided service. 

7.3.5-p4 The ANWI Contractor shall provide a common monitoring capability that 

polls the configuration items (CIs) on every ANWI security domain and determines 

their status and availability. 

7.3.5-p5 The ANWI Contractor shall configure the monitoring tool(s), whether 

PFE or ANWI Contractor provided, to provide the operational alerts of any CI that is 

not operating according to its normal operating (e.g. performance, availability, 

capacity, etc.) parameters to the Network Operating Centre and Service Desk. 

7.3.5-p6 The ANWI Contractor shall use the monitoring tool(s) to detect and 

correlate the operational alerts to support ‘downstream’ troubleshooting and 

assessment of dependent services as defined in the Appendices. 

7.3.5-p7 Following the ITIL definition, an alert is a warning that a threshold has 

been reached, something has been modified, or a failure has occurred.



7.3.5-p8 The events can be categorized in: Informational (“green”), Warning 

(“yellow") or Exception (“red”). 

7.3.5-p9 The ANWI Contractor shall provide a visualisation of the ANWI system’s 

monitoring output showing the status of the reported CIs on the NS security domain 

segment, providing options for zoom-in/zoom-out and based on a colour scheme that 

links to SLT/SLA agreed thresholds(note: the NS domain is where the main SMC is 

located and shows the aggregation of data from the other security domains). 

7.3.5-p10 The monitoring tool(s) shall allow the configuration of the event to be 

identified as being either information notifications (i.e. do not set off alerts) or 

occurrences (i.e. that do set off alerts). 

7.3.5-p11 The ANWI Contractor shall configure warning notifications to report a 

service or capability SLT is approaching a threshold. 

7.3.5-p12 The ANWI Contractor shall configure exception notifications to report a 

service or capability that is not operating properly due to a breach of the SLA or SLT. 

7.3.5-p13 The ANWI Contractor shall configure the monitoring tool(s) to track 

software version, licensing and usage. 

7.3.5-p14 The ANWI Contractor shall configure the monitoring tool(s) to audit 

system, management and security events per the ANWI design, to support data 

collection for SLA monitoring. 

7.3.5-p15 The ANWI Contractor shall configure the monitoring tool to permit the 

Service Desk and designated Operations and Support personnel to filter the 

monitored and reported events. 

7.3.5-p16 The ANWI Contractor shall configure the monitoring tool to collect, track 

and correlate the operational information to the service/capability performance 

standards and metrics for use in assessing the targets and requirements for use in 

the reporting and monitoring of the Service Level Agreements (SLAs). 

7.3.5-p17 The technical requirements for event management support are provided 

in Annex E Appendix 1: Service Management and Control. 

7.3.5-p18 Monitoring 

A. The operations monitoring process shall track, document and record: 

1. All changes made to the service. 

2. Adjustments to a service’s configuration setting(s). 

3. Capacity metrics. 

4. Availability metrics. 

5. Performance metrics 

6. Usage metrics. 

7. Reliability metrics. 

B. The operations monitoring process shall monitor the system baseline 

configuration and replication status of data to support continuity of 

operations. 



7.4 ANWI Operational Support 

7.4.1 Operational Support 




7.4.1-p1 The ANWI Contractor shall produce an Operational Support Plan in 

accordance with ITIL v3 guidelines. 

7.4.1-p2 The Operational Support Plan shall be based on the analysis of the 

operations and maintenance requirements for the ANWI services as derived from: 

A. The ANWI Services Requirements 

B. Service Level Targets and proposed Service Level Agreements 

C. Specific support needs (e.g., maintenance equipment, personnel, repair 

parts, technical orders, manuals and other documentation, training, 

transportation and handling, etc.). 

7.4.1-p3 The ANWI Contractor’s Operational Support Plan (OSP) shall provide 

the organisation, operational support staff job/skill descriptions and operational 

procedures to be used to manage the entire set of ANWI (SMC, Infrastructure, UCC 

and supplemental) services. 

7.4.1-p4 The OSP shall describe how the ANWI Contractor shall perform: day-2- 

day operational management and capacity, availability and performance monitoring 

and management. 

7.4.1-p5 The ANWI Contractor’s OSP shall provide: level 1-2-3 support; system 

maintenance; service level management; SLA reporting and serice billing. 

7.4.1-p5a 

countries. 

The ANWI Contractor’s support staff shall be citizens of NATO 

7.4.1-p5b The ANWI Contractor’s support staff shall hold at least a valid NATO 

Secret Clearance. 

7.4.1-p5c The ANWI Contractor’s System Administrators shall have a 

demonstrated spoken and written fluency in English, at a minimum level of 4343 as 

defined in STANAG 6001. 

7.4.1-p5d The ANWI Contractor’s Service Desk staff shall have a demonstrated 

spoken and written fluency in English and Fench, at a minimum level of 4343 as 

defined in STANAG 6001. 

7.4.1-p6 The ANWI Contractor provided maintenance support shall include 

replacement of any faulty ANWI hardware or software item for the ITS, Training 

System, and operational sites. 

7.4.1-p7 The ANWI Contractor shall provide an on-site support staff to support 

hardware/software maintenance and trouble calls per paragraphs 7.2.2 and 7.2.3. 

7.4.1-p8 The ANWI Contractor shall provide after-hours telephonic assistance for 

urgent maintenance and trouble calls. 

7.4.1-p9 The ANWI Contractor shall be responsible for shipment of faulty items 

for repair or replacement, and of the repaired or replaced item to the affected site. 

7.4.1-p10 In order to achieve TCO there is a need to establish level 1 support 

costs; therefore the ANWI Contractor shall provide the cost for the provisioning of 

level 1 support costs. 






7.4.1-p11 The ANWI Contractor shall: 

A. Consider Annex B which provides the As-Is ICT current ICTM identified 

roles and skills sets information, as input to the ANWI Contractor’s 

estimation of costs. 

B. Provide the level 1-2-3 support needs (based on the additional new 

capabilities or the increase in scale of existing capabilities) to provide the 

support service via the ANWI Contract. 

C. Review the total ANWI operational support requirement (skill sets and 

tasks needed to be undertaken), and determine the manning levels 

needed to provide a complete level 1-2-3 support. 

7.4.1-p12 The below table identifies the ANWI services and the preferred 

Purchaser management approach concept for each service. 

No. Services Centrally managed at another 

NATO or non-NATO location 

1 SMC and IA Services 

1.1 Service Management and 

Control(SMC) 

Managed by The 

NNHQ Site 

Posssibly via escalation Y Y 

1.2 Information Assurance (IA) Y – NCIRC FOC, FW interfaced to 

NATO wide networks 


Y – Other FWs and IDS, 

IDP. 

2.1 Processing Y 

2.2 Storage Y 

2.3 Printing & Scanning Y 

2.4 Network Infrastructure Y (partial for Active Directory) Y 

2.5 LAN Y 


3.1 Voice Y (partial NATO wide VOICE) Y 

3.2 VoiceMail Y 

3.3 VTC Y (partial NATO VTC) Y 

3.4 E-mail Y 


3.6 FAX Y 

3.7 Instant Messaging (IM) Y 

3.8 Presence Y 

3.9 Directory Y (AD related) Y Y 

3.10 Collaboration Y 


4 Client-Provisioning Services 

4.1 OS deployment Y 

4.2 Client devices Y 


5.1 GSM Y (partial for Access) Y 

5.2 GSM Blocking Y 

Contractor 

Managed



No. Services Centrally managed at another 

NATO or non-NATO location 

Managed by The 

NNHQ Site 

5.3 Wireless Blocking Y 

5.4 Site Security Communications 

(Radio) 

5.5 IPTV Y 

Table 7.1: Management approach for ANWI services 

Y 

Contractor 

Managed 

7.4.1-p13 The ANWI Contractor shall establish and maintain a support 

environment to ensure ANWI services meet, at a minimum, the service level targets 

for Reliability, Maintainability, and Availability (RMA) while at the same time 

minimising manpower and support costs. 

7.4.1-p14 The ANWI Contractor shall seek, identify and implement opportunities 

to reduce Operations & Maintenance (O&M) costs through automating or 

streamlining O&M tasks, centralising administration and management, and reducing 

Mean Time to Restore (MTTR).Operational Support during migration 

7.4.1-p15 The ANWI Contractor shall be responsible for the maintenance support 

of NNHQ ANWI services in full cooperation with the NNHQ O&M Authority (for NATO 

projects, Active Directory and Enterprise Administrators) from the moment the 

migration of ANWI services commence. 

7.4.1-p16 The ANWI Contractor shall provide all necessary level 1-2-3 the First, 

Second and Third Level support from the moment the ANWI migration commences 

through till achievement of ANWI FOC.Operational Support and Service 

Management Capability (SMC) 

7.4.1-p17 The relationship between the SMC (based on ITIL v3 based service 

operations) and the proposed ANWI levels of support and is detailed below. 





Figure 7.1: ITILv3 and NATO ILS levels relationship 

7.4.1-p18 The ANWI Contractor shall provide the Service Desk tool set to support 

the Service Desk functionality described in paragraph 7.1. 

7.4.1-p19 The Service Desk shall be the function where all NNHQ service, ANWI 

and others, will use to report any ICT incidents and will be manned by the First Level 

NNHQ O&M Authority staff. 

7.4.1-p20 The Technical Management function shall be provided by the ANWI 

Contractor and covers all of the ANWI services provided. 

7.4.1-p21 The ANWI Contractor shall manage the ANWI provided core 

applications and services while the Business Applications’ support will be provided by 

the NNHQ O&M Authority. 

7.4.1-p22 The ANWI Contractor shall provide the centralized NNHQ monitoring 

and control tools for the ANWI services while the IT Operations and control will be 

undertaken by NNHQ O&M Authority staff. 

7.4.1-p23 The service management capability for each ANWI identified service 

element is detailed in the appendices. 

7.4.1-p24 The ANWI Contractor shall draft a SLA, in accordance with Annex K 

Appendix 18 (SLA), for every ANWI Contractor managed service. 

7.4.1-p25 

The Purchaser will agree the SLAs prior to activation. 

7.4.2 Operational Procedures/Operating Instructions 

7.4.2-p1 The Purchaser has a transition team whose purpose is to develop 

processes/ procedures describing the users’ new ways of working in the 

NNHQ.7.4.4-p2 The ANWI Contractor shall work with the Purchaser’s transition 





team to ensure that the ANWI capability shall support the NNHQ processes and 

procedures being developed. 

7.4.2-p2 The ANWI Contractor shall advise the Purchaser and the transition 

team how the ANWI capability shall function so that the transition team can adjust 

processes as/if required. 

7.4.2-p3 The ANWI Contractor shall develop processes and procedures for the 

ANWI UCC, SMC, and CDM capabilities. 

7.4.2-p4 The ANWI Contractor shall hold a three (3) days workshop to capture 

the needs and provide demonstration mock-ups to demonstrate how the processes 

will work with the ANWI functionality. 

7.4.3 Monitor and Control 

7.4.3-p1 

the service. 

After accepting an ANWI service, the Purchaser will have oversight of 

7.4.3-p2 The failure of a server room, service or capability shall direct an alert to 

the Event Management system and directly to the Event Management’s console. 

7.4.3-p3 The ANWI design shall ensure that service Key Performance Indicator 

metrics are directed to the Network Operations Centre where the service’s current 

status and its service target are clearly visualised in support of any of the NNHQ 

O&M Authority operations and support, as well as those having service management 

responsibilities. 

7.4.3-p4 All ANWI services shall be monitored and managed from the NNHQ 

LAN, Bâtiment Z or any other authorised remote location. 

7.4.4 Life-Cycle Support 

7.4.4-p1 The ANWI Contractor shall provide the ANWI Second and Third Level 

Support for the warranty period, and costed options for the support elements 

provided by NNHQ Staff, as detailed in the Support section. 

7.4.4-p2 The costed support elements options shall cover a full cycle support 

period of 5 years from Final Operating Capability (FOC) . 

7.4.4-p3 The ANWI Contractor shall provide First, Second and Third Level 

Support (as defined in section 7.2) for the period starting at ANWI Initial Operational 

Capability (IOC) through FOC 

7.4.4-p4 The ANWI Contractor shall provide First, Second and Third Level 

Support for the ITS. 

7.4.4-p5 The ANWI Contractor shall deliver the services as defined in this SOW 

for a period sufficient to ensure that all Service Requirements and SLTs are met, all 

SLAs defined are achieved, and full acceptance can be realised. 

7.4.4-p6 The ANWI Contractor shall continue to provide contractor operated 

services, until transition of the services that are designated NATO operated are 

transitioned to NATO staff. 





7.4.4-p7 Contractor owned and operated services (e.g. GSM, IPTV, 

Printing/Scanning) shall continue to be provided by the ANWI Contractor following 

ANWI service acceptance. 

7.4.4-p8 The ANWI Contractor may be asked to continue providing contractor 

operated services throughout the 5-year life cycle should this be determined to be 

cost effective or otherwise deemed to be advantageous to NATO. 





SECTION 8. 

ANWI SERVICE IMPROVEMENT 

8.1 ANWI Service Improvement Purpose 

8.1-p1 According to the ITIL definitions, the Continual Service Improvement (CSI) 

lifecycle stage provides guidance on creating and maintaining value for users through 

better strategy, design, transition and operation of services, following changing 

business needs. 

8.1-p2 The CSI phase of the ANWI project shall begin (see figure 4.1) prior to the 

milestone that the ANWI capability reaches IOC thus establishing the initial baseline, 

and starts service tuning once users are added. The next baseline is at FOC (all 

users on line), ensuring that the delivered services and capabilities are continually 

realigned to the users’ needs through the identification and implementation of ways 

to improve process effectiveness, efficiency and lower costs. After FOC the CSI 

phase will continue until FSA after which the CSI will become an embedded part of 

the ANWI life-cycle and Service Management process. 

8.1-p3 CSI can apply to organizations, resources, technology, partners, training, 

communications, and skills. 

8.1-p4 The ANWI Contractor shall support ANWI CSI by: 

A. Developing the Service Catalogue reports that are delivered to the users 

in accordance with the Service Level Agreement identifying the how the 

terms of the SLA and its targets were or were not met. 

B. Collecting the necessary data for use in generating the Service Catalogue 

reports. 

C. Analysing the data’s trend and comparing the result with the SLA 

baselines, targets and benchmarks. 

D. Recommending service level target adjustments to improve efficiency in 

quality and resource use over the service’s lifecycle. 

E. Reviewing security requirements and suggest ways to improve a 

capability’s performance. 

F. Reviewing the service billing and invoice process. 

G. Reviewing the ANWI installation baselines and procedures and 

recommend changes. 

H. Proposing a plan to the Purchaser on how to implement the ANWI 

Contractor’s suggestions to improve efficiency and availability of ANWI 

capabilities and services. 

8.2 ANWI CSI Assumptions 

8.2-p1 The ANWI Contractor, the Purchaser, NATO Contractors and the other 

NATO National Contractors work together to ensure their mutual success in 

managing and continuously improving all implemented services. 

8.2-p2 The underpinning Contracts shall support the business and provide 

appropriate embedded incentives. 





8.3 CSI Register 

8.3-p1 The ANWI Contractor shall identify all the improvement opportunities in a 

CSI Register that shall be part of the Service Knowledge Management System. 

8.3-p2 The ANWI Contractor shall establish and maintain a CSI register which 

serves as the historical log of each improvement initiative, where it was tried with 

explicit mention to: categories of the improvement, justification benefits to be 

achieved, and evaluation of the benefits achieved. 

8.4 CSI Board 

8.4-p1 A CSI Board shall be established consisting of: User Representative, CSI 

Manager, Service Owner, Reporting Analyst, Purchaser, ANWI PM; and CIS 

Manager. 

8.4-p2 The CSI Board shall review and approve changes to services and/or SLAs. 

CSI Baselines 

8.4-p3 The ANWI Contractor shall establish service baselines for comparing 

service levels of performance. 

8.5 CSI Metrics 

8.5-p1 The ANWI Contractor shall address the following Service Design areas: 

Technology, Processes, and Service when assessing service improvement. 

8.5-p2 The ANWI Contractor shall review the ANWI Critical Success Factors and 

recommend Key Performance Indicators (from Annex E Appendix 1) to better 

measure and assess the ANWI services. 

A. Critical Success Factors (CSF) 

1. The ANWI Contractor shall review the ANWI Service Catalogue’s 

entries and their Service Level Agreements then suggest improvements 

to the CSI Board. 

2. The ANWI Contractor shall base the ANWI Critical Success Factors on 

the ANWI’s vision and high level objectives. 

3. The ANWI Contractor shall identify the Critical Success Factors for 

each ANWI offered service’s SLA. 

B. Key Performance Indicators (KPI) 

1. The ANWI Contractor shall assess the output of the ANWI provided 

element monitoring and reporting tools and provide interpretations of 

their outputs to the Critical Success Factors. 

2. The ANWI Contractor shall identify necessary KPIs to display and 

monitor for each CSF to ensure the SLA can be satisfactorily assessed. 

3. The ANWI Contractor shall recommend other KPIs for measuring future 

service management maturity. 




8.6 Seven-Steps Improvement Process 

8.6.1 General 


8.6.1-p1 The single process of ITIL CSI is focused on identify, define, gather, 

process, analyse, present and implement improvements: 

8.6.2 Step-1: Define What Should Be Measured 

8.6.2-p1 The ANWI Contractor shall produce a list of the possible KPIs that can 

be used to measure each of the ANWI services 

8.6.3 Step-2: Define What CanBe Measured 

8.6.3-p1 The ANWI Contractor shall assess the list of ANWI service KPIs and 

recommend those KPIs that will provide the best information on the respective 

service to determine if the service is performing properly. 

8.6.4 Step-3: Gather the Data 

8.6.4.1.1 Monitoring 

8.6.4.1.1-p1 Once a capability is implemented the ANWI Contractor shall monitor 

the services to identify weak areas in need of remedial action to improve the service. 

8.6.4.1.1-p2 The ANWI Contractor shall review the trouble tickets and issues to 

identify weaknesses in process training and/or areas for culture change to improve 

user working efficiency. 

8.6.4.1.1-p3 

service. 

The ANWI Contractor shall monitor the quality of the end-to-end 

8.6.4.1.1-p4 The ANWI Contractor shall monitor the performance (throughput, 

cycle times, etc.). 

8.6.4.1.1-p5 The ANWI Contractor shall monitor the perceived value of the 

service and associated processes. 

8.6.4.1.1-p6 

8.6.4.1.2 Data Collection 

The ANWI Contractor shall monitor service availability and capacity. 

8.6.4.1.2-p1 The ANWI Contractor shall continuously collect Service Level 

Target data for analysis and reporting every two weeks after FOC for the first two 

months so the Service Level Agreement reporting process can be quality assessed 

and the ANWI tuned. 

8.6.4.1.2-p2 The ANWI Contractor shall focus on the need to measure and 

evaluate the effectiveness of the service when collecting a service’s data. 

8.6.4.1.2-p3 The ANWI Contractor shall identify the linkage between: 

A. Critical Success Factors. 

B. Service Level Targets. 

C. IT duty positions. 





8.6.4.1.2-p4 The ANWI Contractor shall identify what tool, process flow, 

procedure and other source will provide the appropriate data to produce the Service 

Level Agreement reports. 

8.6.4.1.2-p5 The ANWI Contractor shall collect data from the monitoring and 

reporting tools to assess the effectiveness of the: 

A. Technology solution – this metric considers performance, availability, 

reliability, manageability, etc. 

B. Service – concentrates on assessing the end-to-end service where 

component and technology metrics are used. 

C. Organisation – the data reflects the system administration exercises, 

routines and processes impacting availability, continuity, serviceability and 

manageability. 

D. Process – focuses on Key Performance Indicators, Critical Success 

Factors and service desk. 

8.6.4.1.2-p6 The ANWI Contractor shall determine the service’s network path 

and collects data from several points along the path to assess areas that reduce the 

service’s performance. 

8.6.4.1.2-p7 The ANWI Contractor shall identify when and how often data 

measurements are taken and used for analysisand offer it to the Purchaser for 

approval. 

8.6.4.1.2-p8 The ANWI Contractor shall ensure that collected data samples are 

from the same timeframe. 

8.6.5 Step-4: Process the Data 

8.6.5-p1 The ANWI Contractor shall collect the data from the service element 

managers and format the data so that the SMC analysis tool(s) can ingest the data 

8.6.6 Step-5: Analyse the Information and Data 

8.6.6-p1 The ANWI Contractor’s data analysis shall concentrate on the Service 

Level Targets for availability, capacityand other agreed metrics/KPIs. 

8.6.6-p2 The ANWI Contractor shall review the collected data ensuring it is 

consistent and gaps identified. 

8.6.6-p3 The ANWI Contractor shall assess the data to determine if the service 

metrics, Key Performance Indicators (KPIs) and supporting Critical Success Factors 

are correct to evaluate the service. 

8.6.6-p4 The ANWI Contractor shall perform statistical analysis on the metric’s 

data and determine if the metric’s trend supports and shall continue to support the 

Service Level Targets for the periods of 3/6/9/12 months and 1/2/3 years. 

8.6.6-p5 The ANWI Contractor shall look for weak areas in the delivery of the 

capability or service. 

8.6.6-p6 The ANWI Contractor shall use the data to determine the cause of 

issues/problems. 





8.6.6-p7 The ANWI Contractor shall suggest adjusting the SLT if a parameter is 

consistently met or exceeded. 

8.6.6-p8 The ANWI Contractor shall compare the collected data to service and 

capability issues to determine what system actions are causing service faults. 

8.6.6-p9 The ANWI Contractor shall present the data analysis to the Purchaser 

and make recommendations for ANWI service tuning. 

8.6.7 Step-6: Present and Use the Information 

8.6.7.1 Reporting 

8.6.7.1-p1 The ANWI Contractor shall provide the Purchaser ANWI Service 

Level Agreement Reports, as required per the Service Level Agreements, 

regardingthe performance of the ANWI’s Service Catalogue entries. 

8.6.7.1-p2 The ANWI Contractor shall create reports on the analysed data to 

relate meaningful and relevant information on the services’ SLA and SLTs. 

8.6.7.1-p3 ANWI SLAReports shall as a minimum include: 

A. Performance against the Service Level Target benchmarks. 

B. Trend analysis and SLT performance prediction. 

C. Non-compliance with SLA. 

D. Issues and problems reported. 

E. Security issues. 

F. Resource use against target. 

G. Service target trend information. 

8.6.7.2 Correction Recommendations 

8.6.7.2-p1 The ANWI Contractor shall make recommendations to the 

Purchaser based on the collected data as reflected in the SLAreport. 

8.6.7.2-p2 The ANWI Contractor shall recommend process and capability 

changes to tune the ANWI Service. 

8.6.7.2-p3 The ANWI Contractor shall recommend Change Proposals to adjust 

the product baseline. 

8.6.8 Step-7: Implement the Improvements 

8.6.8-p1 

The ANWI Contractor shall document the recommended improvements. 

8.6.8-p2 The ANWI Contractor shall submit the recommendation to the CSI 

Board for consideration and approval. 

8.6.8-p3 

CSI register 

The ANWI Contractor shall document the approved improvement in the 

8.6.8-p4 The ANWI Contractor shall create a new baseline for the service and 

document the baseline in the configuration management database 

8.6.8-p5 

The ANWI Contractor shall implement the approved change 




8.7 CSI Interactions with Other Processes 



8.7-p1 The ANWI Contractor shall consider the following processes when 

considering CSI: 

8.7-p2 The ANWI Contractor shall address the following points relating to security: 

A. Define security monitoring and data collection procedures 

B. Monitor the level of security changes 

C. Analyse responses to the security issues 

D. Generate trend analysis on security breaches 

E. Validate risk mitigation strategies 

F. Analyse data for evaluating the SLA 

8.7-p3 The ANWI Contractor shall address the following points relating to 

availability: 

A. Review components failure impact analysis 

B. Provide fault tree analysis 

C. Manage the IT services demand 


capacity: 

A. Analyse business, service, component against the capacity plan 

B. Gather information about application sizing 

C. Gather SIPs information and provide reports 

D. Manage demand 

8.7-p5 The ANWI Contractor shall address the following points relating to change 

and release: 

A. Manage Requests for Change 

B. Perform post-implementation review 

C. Participate to the CAB 

D. Seek for implementation improvements 


financial: 

A. Monitor and collect data about expenditures vs. budget 

B. Provide input to define whether cost and business targets are met 

C. Monitor the cost per service 

D. Provide support in evaluation the ROI for improvements 

8.7-p7 The ANWI Contractor shall address the following points relating to Service 

Desk and Incident Management: 

A. Document and review incidents trends, services requests, 

B. Compare all results with agreed Service Level and previous months, 

C. Suggest improvement opportunities, 

D. Analysis processed data for accuracy 

8.7-p8 The ANWI Contractor shall address the following points relating to Service 

Level Management: 

A. Interact with executives to determine / validate Service Level 

Requirements 

B. Negotiate terms and responsibilities of Operational Level Agreements 

(OLAs) 




C. Verify that needed contracts are updated and meet the revised business 

requirements 

D. Use service catalogue to negotiate SLAs with executives 

E. Review services achievements and verify where improvements are 

required 


Knowledge: 

A. Analyse Data, Information, knowledge and use results in the CSI 

B. Share CSI knowledge 

C. Include the CSI register in the Service Knowledge management database 

D. Analyse the statistics of user access and permanence per sites/tools of 

the Information Management tools and provide the necessary information 

to improve the knowledge management process 

8.8 Win-Win Relationship and Management 

8.8-p1 The Purchaser encourages the optimization of service delivery, as well as 

the identification of any opportunities for enhanced technical performance due to 

evolution of technology and the optimization of performance including, inter alia, 

utilizing green technologies and business best practises, that offer value both in 

terms of performance and reduction in price for the Purchaser whilst maintaining and 

improving users’ satisfactionthrough hardware, software and process efficiencies as 

agreed with the Purchaser. 

8.8-p2 The ANWI Contractor and Purchaser will develop a process, within the 

scope of the SOW, where the optimization and cost reductions (to the Contractor) 

and consequent price reductions to the Purchaser can be examined and agreed. This 

will be part of the process of development of the agreed SLAss. 

8.8-p3 Bidders shall provide a SLAs for the ANWI services, as part of the 

Operational Support Plan, describing their optimization concept with reference to 

best industry practise and past experience). 

8.8-p4 Any adjustments to the price or SLA will be in accordance with the 

Contract. 





SECTION 9. ANNEX A: SCHEDULE OF KEY PROGRAM 

MILESTONES 

9.1 ANWI Schedule 

9.1-p1 The following table shows the NNHQ dependent project timelines showing 

when ANWI must have capabilities available for other HN use 

Milestone Milestone Description Milestone Date 

PNWI HN Belgium starts PNWI cabling September 2012 

VTC IOC NATO -wide VTC Initial Operating Capability (IOC) June 2013 

VTC FOC NATO-wide VTC Final Operating Capability (FOC) December 2013 

ITS ITS available for use by AVI, ESS and BMS February 2014 

PNWI PNWI cabling works completed September 2014 

ITS ITS available for Business Application and Data Migration testing October 2014 

ANWI-1 ANWI installation in basement part of building (month 49) starts November 2014 

SvrRm Server Rooms available for installation February 2015 

BADM-1 

Business Applications and Data Management ready for migration to 

ANWI 

April 2015 

BADM-2 

ANWI available for ICTM business application migration Core AIS 

ready for AVI, ESS andBMS installation 

July 2015 

ESS/BMS AVI and ESS production tests start in new building September 2015 

IOC 

Server Room installation completed and Provisional Site 

Acceptance Testing completed 

(caveat this is for all ANWI services and readiness of HN BEL 31 

October 2015 

March and ICTM Apps 1 January) 

AVI/ESS New Building handover to building management & HQPO December 2015 

End User 

NNHQ building end user area available for ANWI Contractor 

installation work to start 

January 2016 

Migration ANWI Migration Support to BADM August 2015 –April 2016 

FOC ANWI end user area installation completed April 2016 

Improvement Post Migration and ANWI improvement support May 2016 – October 2016 

FSA Final Acceptance for Handover October 2016 

Table 9.1 NNHQ project timelines 





9.2 Integration Test Service 

9.2-p1 

The following is the timeline for the ITS’ deliverables and readiness 

Milestone Milestone Description Milestone Date 

EDC Effective Date of Contract D 

ITS designed ITS design approval D+2months 

ITS installed ITS hardware installed D+4 months 

ITS Available ITS initial security domain configuration and processes agreed D+5 months 

ANWI infrastructure services baselined 

ANWI ready for AVI, ESS and BMS contractor February 2014 

AVI, ESS & BMS testing completed 

ITS available for Business Application and data migration 

contractor (BADM) 

ITS decommissioned ITS effort completed 

October 2014 

D+26 months 

Table 9.2 timeline for the ITS’ deliverables and readiness 





SECTION 10. ANNEX B: PURCHASER FURNISHED 

INFRASTRUCTURE & SERVICES (hereafter known 

as PFE) 

10.1 INTRODUCTION 

10.1-p1 The totality of the New NATO Headquarters is provided through a number 

of projects and/or contracts. Each contract provides deliverables that will support 

interface (which varies from electronic interfaces between ICT systems to physical 

interfaces such as physical installation location) with the ANWI Capability. 

10.1-p2 Below is a description of the various projects and/or contracts deliverables, 

to be provided by various stakeholders that the ANWI Contractor shall integrate into 

the ANWI capability. 

10.1-p3 Each paragraph relates to one specific project and/or contract. It specifies 

particular requirements for the ANWI Contractor with regards to the related PFE and 

provides references, as appropriate, to Section 12. 

10.2 Global Construction Contract (GCC) Project (HN: Belgium) 


10.2.1-p1 HN Belgium manages the Global Construction Contract (GCC) 

providing the New NATO Headquarters campus facilities. 

10.2.1-p2 The following site drawings are provided at Appendix 1: 

A. NU-09-I-HQ-A-5-208-XX-00-SW section, Issue: 10 Aug 2009. 

B. NU-09-I-L2-I-2-034-00-02-LW-Level 0, Issue: 7 May 2012. 

C. NU-09-I-L2-I-2-035-01-03-LW-Level 1, Issue: 7 May 2012. 

D. NU-09-I-L2-I-2-036-02-02-LW-Level 2, Issue: 10 Aug 2009. 

E. NU-09-I-L2-I-2-037-03-02-LW-Level 3, Issue: 10 Aug 2009. 

F. NU-09-I-L8-I-2-088-04-01-LW-Level 4, Issue: 17 Feb 2012. 

G. NU-09-I-L2-I-2-039-05-01-LW-Level 5, Issue: 13Jun 2012. 

H. NU-09-I-L2-I-2-040-06-00-LW-Level 6, Issue: 10 Aug 2009. 

I. NU-09-I-S2-I-2-100-02-01-typical floor SW, Issue: 08 Dec 2011. 

J. NU-9-I-CC-J-2-140-00-01, Issue 4 Apr 2012. 

K. NU-9-I-CI-J-2-301-00-01, Issue 4 Apr 2012. 

L. NU-11-B-AG-A5-525-XX-00, Issue 30 Mar 2007. 

M. NU-11-B-AG-A5-528-XX-00, Issue 30 Mar 2007. 

N. NU-09-I-S2-N-2-100-02-00, Issue 10 Aug 2009. 

O. NU-09-I-L2-N-2-036-02-00, Issue: 10 Aug2009. 

10.2.2 Server Rooms 

10.2.2-p1 Two server rooms where each provides: 

A. 375 m2 (ICT1) + 462m2 (ICT2) floor space per server room. 

B. Each server room will be provided an elevated floor. 





C. 112 (ICT1) + 126 (ICT2) Rack Positions (not completely filled with empty 

racks). 

D. 5 dual rows of Purchaser provided 800x1000 racks (each dual row 

covered to form a corridor, 12-18 racks per dual row). 

10.2.3 Technical Control Facility (TCF) Rooms (Communications Rooms) 

10.2.3-p1 NATO external communications and IP services will enter the NNHQ 

via four communications rooms. There are two types of TCFs: 

A. Two commercial communications TCFs. 

B. Two military communications TCFs. 

10.2.3-p2 TCFs will include Point of Presence (POP) equipment where external 

communication services are delivered. 

10.2.3-p3 A subset of such POP equipment will be provided by other 

projects/stakeholders (such as NGCS) as PFE. 

10.2.4 Technical Equipment Room (TER) 

10.2.4-p1 There are two types of TERs: 

A. NATO (basement) TERs (TERs). 

B. NATO Nations (Nations’ floor space) TERs (NTERs). 

10.2.4-p2 National TERs will be the responsibility of the particular nations, 

therefore to gain access to these TERs shall require coordination with the national 

POC. 

10.2.4-p3 The repartition of the TERs is described below: 

A. Long wings: 1 x 1 TER + 3 x 2 combined TERs; 

B. Short wings: 1 x 1 TER + 1 x 2 combined TERs (except SW2: 3 x 1 TER); 

C. Basement functions: 2 x 1 TERs; 

D. Conference Centre: 4 x 1 TERs + 4 x 2 combined TERs; 

E. Common Infrastructure: 4 x 1 TER + 2 x 3 combined TERs. 

10.2.4-p4 Technical Equipment Rooms (TER) where each provides: 

A. 20 m 2 (4m x 5m) of floor space for a single TER; 

B. 40 m 2 (8m x 5m) of floor space for a double TER ; 

C. 4 (800x800) Racks (8 in Merged TERs); 

D. 10 kVA UPS and 4 kW cooling capacity. 

10.2.4-p5 The ANWI Contractor shall be responsible for the management and 

control of the Technical Equipment Rooms. 

10.2.4-p6 The ANWI Contractor shall install ANWI switches in the Technical 

Equipment Rooms. 

10.2.5 Power and Cooling 

10.2.5-p1 Power and Cooling will be provided as indicated in Paragraphs 14.2.3.2 

and within the limits indicated in Para 14.1.4. 





10.2.6 Passive Network Infrastructure (PNWI) 

10.2.6-p1 The PNWI project provides fibre and copper cabling within NNHQ 

campus, details are provided in the PNWI Cabling Design (ref 1.1.1.8.17) and in the 

PNWI technical specifications (ref 1.1.1.8.20). The PNWI uses flood cabling 

throughout the building; fibre will be used for secure networks and copper for the 

public network. 

10.2.6-p2 Each end-user point will be supported with a desk module that supports 

the following cabling as outlined in table 10.1. 

Type of Outlet 

HQ, IS/IMS, Conference Center (CC), 

Nations 

Staff Centre (SC), Industrial Infrastructure 

(II), Common Infra 

Number of 

Ports 

Number of fibre 

ports. multimode 

Number of 

Copper RJ-45 

Spare 

6 4 1 1 

4 2 1 1 

Guard House (GH) 4 2 1 1 

Table 10.2: PNWI Desk outlets 

10.2.6-p3 More details about the desk module and connector types can be found 

in reference 1.1.1.8.3. 

10.2.6-p4 The drawing below provides an overview of the TER cabling concept 

delivered by the PNWI. 





Figure 10.1 Overview of TER cabling concept 

10.2.6-p5 The ANWI Contractor shall deliver and install any ANWI POP 

equipment (if needed) into the TCF (Technical Control Facility) Rooms. 

10.2.6-p6 The ANWI Contractor shall connect and configure equipment in Server 

Rooms and TCFs to establish the required integration, in coordination with other 

stakeholders where necessary. 

10.3 Building Management Services (BMS) Project (HN: Belgium) 

10.3-p1 The Building Management Services (BMS) are running on the Business 

network and have a facility management scope. They will interface with the ANWI on 

the infrastructure layer where they will use networking and storage resources of the 

ANWI as well as some specific infrastructure networking services like NTP and 

DHCP. 

10.3-p2 BMS capabilities will be provided by the Purchaser for Integration Testing 

on the ITS and for installation, Integration, Testing and Acceptance on the ANWI 

infrastructure in the New NATO HQ. 

10.3-p3 The ANWI Capability Contractor shall provide 10TB of usable storage per 

server room supporting the BMS storage requirement. 

10.3-p4 The ANWI Business network shall also provide the physical network 

connections for the BMS devices. There will be approximately 170 fibre optic network 

connections required. 

10.3-p5 The BMS shall run on the Business network. 







10.4 Electronic Security Services (ESS) PROJECT (HN: Belgium) 

10.4-p1 The Electronic Security Services (ESS) are running on the Business 

network and have a physical security scope. They will interface with the ANWI on the 

infrastructure layer where the ESS will use networking and storage resources of the 

ANWI as well as some specific infrastructure networking services like NTP and 

DHCP. 

10.4-p2 ESS capabilities will be provided by the Purchaser for integration testing on 

the ITS and for installation, integration, testing and acceptance on the ANWI 

infrastructure in the NNHQ. 

10.4-p3 The ANWI Contractor shall support the Purchaser by providing switched 

connectivity from the ESS device to the server room. 

10.4-p4 The ANWI Capability Contractor shall provide and configure 150 TB 

(online) and 900 TB (offline – archive) usable storage per server room, supporting 

the ESS storage. 

10.4-p5 The ANWI Business network shall provide the physical network 

connections for the ESS devices. There will be approximately 2000 fibre optic 

network connections required for ESS devices. 

10.5 Audio Visual Infrastructure (AVI) PROJECT (HN: Belgium) 

10.5-p1 The AVI capability will be available on all 4 domains. Therefore, the 

interfacing with ANWI shall be on all domains (NATO SECRET, EAPC SECRET, 

BUSINESS and PUBLIC). 

10.5-p2 The Purchaser will provide the NNHQ with AVI capabilities that 

interconnect with the NATO Wide VTC; the interconnection via ANWI assets shall be 

supported by the ANWI Contractor. 

10.5-p3 AVI capabilities will be provided by the Purchaser for integration testing on 

the ITS and for installation, integration, testing and acceptance on the ANWI 

infrastructure in the New NATO HQ. 

10.5-p4 The ANWI Contractor shall provide 20TB online usable storage and 20TB 

offline usable storage per server room and per network supporting the AVI storage 

requirement. 

10.5-p5 The ANWI networks shall provide the physical network connections for the 

AVI devices. 

10.5-p6 The ANWI Contractor shall support the Purchaser with ANWI networking 

connectivity and storage support. 

10.6 NNHQ Office Furniture Project (HN: HQPO) 

10.6-p1 This project will deliver furniture throughout the NNHQ, including specialist 

ICT and AV (conference centre) furniture. 

10.6-p2 The office furniture will be installed and made available for the installation 

of the ANWI client equipment by the Purchaser.



10.6-p3 Early access to the planned office layout and furniture will be made 

available to the ANWI Contractor, as an input to the selection of the client device 

form factor. 

10.7 NATO General Purpose Segment Communication System 

(NGCS) Project (HN: NCIA) 

10.7-p1 NCIA is NATO’s current Communications and Information System 

Operations and Support authority for the management of NATO wide services. NCIA 

is responsible for the NGCS which is the Circuit Emulation Subsystem providing 

Legacy Circuit Services. NGCS provides access to the NATO WAN Environment. 

This currently includes NATO SECRET and NATO UNCLASSIFIED. A NATO 

RESTRICTED WAN is being implemented. 

10.7-p2 The main NGCS interfaces are the edge routers of the different networks. 

Traffic is predominately IP based with the exception of some legacy systems (ex. 

TDM Voice communication). The general architecture is presented in the figure 

below. 

Figure 10.2 Graphical overview of NGCS architecture 

10.7-p3 For each new (or changed) connection for the NATO-wide network an 

official Service Request (SR), that will be managed via the Service Request Tracking 

System (SRTS), shall be prepared by the ANWI Contractor. Handling an SRTS can 

take from 30 to 60 days, this time is needed as part of the security accreditation 

procedure. The Purchaser will provide guidance and support to the ANWI Contractor 





in order for the ANWI Contractor to prepare all necessary information in time for a 

successful SR. 

10.7-p4 The NGCS network services are centrally managed using a network 

management system located in Mons. 

10.7-p5 Access to NGCS will be provided for ITS and the NNHQ. 

10.7-p6 The ANWI Contractor shall request the IP address space needed to 

implement the ANWI design for the NNHQ from the Purchaser. This is applicable for 

all the domains that shall be implemented. This does not include the ESS, BMS and 

AVI equipment. 

10.7-p7 The ANWI Contractor shall prepare all necessary information in time for a 

successful SR. 

10.7-p8 The ANWI shall interface with the NGCS data IP networks at various 

classifications. 

10.7-p9 The ANWI shall interface with the NGCS unclassified voice capability. 

10.7-p10 

The ANWI shall interface with NGCS VTC services. 

10.8 Domain Name System(DNS) Project (HN: NCIA) 

10.8-p1 NCIA is the Naming and Addressing Authority that controls the NATO DNS 

namespaces. Any ANWI DNS changes shall be prepared by the ANWI Contractor as 

part of the SR procedure. 

10.8-p2 DNS will be provided by the Purchaser for the new NATO HQ. 

10.8-p3 The ANWI Contractor shall coordinate all ANWI DNS changes needed to 

support the implementation of their design with the Purchaser. 

10.9 Firewalls Project (HN: NCIA) 

10.9-p1 NCIA centrally manages Firewalls and Guards devices that interconnect to 

the NATO-wide networks. This is specified in Annex E Appendix 2. Firewalls, just as 

any other border protection device, are centrally managed in NATO. The current 

NATO Firewall products in use are Palo Alto branded firewalls. 

10.10 Active Directory AIS Single Forest Single Domain (AD AIS 

SFSD) Project (HN: NCIA) 

10.10-p1 NCIA Enterprise Administers manage the NATO Windows Active 

Directory (AD) Single Forest Single Domain (SFSD) network on the NS and the 

Public Access Network (PAN, operating at NU level). There are plans for NR support 

(for the NR network). 

10.10-p2 More information on the AIS SFSD and joining instructions can be 

found in references 1.1.1.5.3. and 1.1.1.5.4. 

10.10-p3 The ANWI Contractor shall create the NNHQ Active Directory for 

Purchaser approval for the NNHQ. 





10.10-p4 The ANWI Contractor shall coordinate with the Purchaser to join the 

SFSD, for the NU (Public) and for the NR (Business) should it exist at the time of 

implementation. 

10.11 AIS Microsoft Exchange Services Project (HN: NCIA) 

10.11-p1 NCIA is supporting an AIS wide Microsoft Exchange 2007 environment 

on both the NS and PAN. 

10.11-p2 The details can be found in references 1.1.1.8.10 and 1.1.1.8.11. 

10.11-p3 The ANWI Contractor shall coordinate with the Purchaser to join the 

AIS MS Exchange organisations. 

10.12 Automated Information System Enterprise Management 

System (AIS EMS) Project (HN: NCIA) 

10.12-p1 NCIA manages the AIS AD enabled EMS services using Microsoft’s 

System Centre Configuration Manager (SCCM), WSUS, and System Centre 

Operations Manager (SCOM) for AIS wide configuration, software update, and 

monitoring purposes on the NS and the PAN. This central enterprise management 

system is currently based on Microsoft System Centre Enterprise. 

10.12-p2 The EMS details can be found in reference 1.1.1.8.12. 

10.12-p3 The ANWI Contractor shall coordinate with the Purchaser to join and 

integrate the EMS Services. 

10.12-p4 The ANWI SMC shall interface with the NCIA EMS system in order to 

exchange asset and event data. 

10.13 Current HQ Baseline (HN: HQ ICTM) 

10.13-p1 HN ICTM is responsible for the NR-2 capability which will provide ICT 

services at the current NATO HQ. The NR-2 capability is currently under 

development and implementation and will evolve. 

10.13-p2 The planned NR-2 capability is described in the NR-2 Target 

Architecture Document (reference 1.1.1.8.5). 

10.13-p3 HN ICTM is responsible for managing and evolving the current 

application portfolio. In addition to the ANWI related core and infrastructure services 

based applications the following three other categories of applications are identified: 

A. Enterprise Information Management (EIM) based applications primarily 

support the HQ Information and Knowledge Management processes. 

B. Enterprise Resource Management (ERP) based applications primarily 

supporting the resource planning processes related to for example 

financial processes. 

C. Specialist Applications which are related to support specific specialist 

function of Headquarters organisation elements or in support of specific 

Communities of Interest. 





10.13-p4 The following table gives a global overview of the number of 

applications currently used in the HQ. 

Type of application 

Number of applications 

ERP 81 

EIM 121 

Table 10.3: Number of current applications 

10.13-p5 The Business Applications and Data Migration (BDAM) Project will 

install the NATO Headquarters’ business applications on the ANWI provided 

hardware and base software. 

10.13-p6 The BDAM Contractor will migrate the NATO Headquarters user and 

business applications’ data onto ANWI servers and client devices. 

10.13-p7 The ANWI Contractor shall support the BADM Contractor by assisting 

with the adjustment of approved windows security role configuration of the ANWI 

delivered software baseline configuration. 

10.13-p8 The ANWI Contractor shall provide access and advice/assistance to the 

BADM Project with respect to performance tuning of network services. 

10.14 Video Tele Conference(VTC) Project (HN: NCIA) 

10.14-p1 NCIA is the Host Nation for the VTC project that will operate on both NS 

and NU networks. 

10.14-p2 The operational objectives of this project are to: 

A. Provide a centrally managed VTC system through the installed VTC 

Network Operational Centre (VNOC). It will allow the VNOC operators in 

their Headquarter to achieve control of all related systems. This will 

include but not be limited to configuration management, operational 

management and troubleshooting activities as required, 

B. Provide a VTC system scheduling service which allows users to directly 

perform scheduling activities with Outlook and a web-based application, 

C. Upgrade the existing VTC system to the latest industry standards by 

adding state-of-the-art facilities. As a minimum, the system will provide 

Point-to-Point and Multipoint VTC services to static NGCS locations and 

giving the NATO user community a reliable, secure, manageable and 

scalable VTC service, 

D. Provide distributed services through the installed VTC Access Node (VAN) 

managing the VTC services, enabling session recording services and 

videoconferencing with other stakeholders and ISDN VTC terminals, 

E. Provide a reference facility system located at NATO Communications and 

Information Agency (NCIA Belgium). This reference facility will be 

operated by NCIA primarily to perform fault analysis, configuration 

management, upgrades, reporting and migration scenario testing, 

F. Provide a training facility at the NATO CIS School (NCISS, location to be 

confirmed) with the appropriate tools to train technicians and VTC 

facilitators, 





G. Integrate existing VTC equipment into the new and enhanced NATO VTC 

system, 

H. Provide new VTC equipment NATO Wide including High resolution VTC 

terminal equipment, 

I. Support the integration process between various implementation projects. 

10.14-p3 

HQ. 

VTC Capabilities will be provided by the Purchaser for the new NATO 

10.14-p4 The ANWI Contractor shall support the Purchaser with NNHQ 

connectivity issues. 

10.14-p5 The ANWI Contractor shall support the Purchaser by providing 

technical support and storage access. 

10.15 NATO Enterprise Directory Services(NEDS) Project (HN: NCIA) 

10.15-p1 NCIA is the Host Nation for the NEDS project. This project will provide 

Directory synchronisation between different sources as illustrated in the figure below. 

Figure 10.3: NEDS Project Scope 

10.15-p2 The NEDS will be deployed on the NS and Business domains by the 

NEDS Contractor. The NEDS capability supports NPKI needs. 

10.15-p3 The NEDS will act as an information broker between the various NATO 

directory/data repositories, called the “NEDS Affiliates”. Through a ‘Repository’ 

function as well as a filtering and synchronisation function NEDS allows “NEDS 

Affiliates” to make information available for sharing with other directories/data 

repositories, and allows them to subscribe to NEDS information published by other 





directories/data repositories. Each piece of information contained in the NEDS is 

derived from an authoritative NATO source. 

10.15-p4 

Brunssum. 

Two NEDS central admin workstations will be installed at SHAPE and 

10.15-p5 NEDS capabilities will be provided by the Purchaser for the new NATO 

HQ and the NEDS implementation on the ANWI shall be supported by the ANWI 

Contractor. 

10.15-p6 The ANWI shall interface with the NEDS capability on the NS and 

Business domains, acting as a “NEDS affiliate”. The ANWI Contractor shall work with 

the NEDS Contractor to synchronise ANWI directory information within the affiliate 

role. 

10.15-p7 The ANWI Contractor shall interface the ANWI with the NEDS through 

Lightweight Directory Access Protocol (LDAP). 

10.15-p8 The ANWI shall be compatible with the Enterprise Directory Services 

Service Interface Profile (SIP) (reference 1.1.1.8.8). 

10.15-p9 The ANWI shall include the necessary administration tool(s), provided 

by the NEDS, to manage the interface with the NEDS if required by the NEDS 

Agreement. 

10.15-p10 

The ANWI shall be able to use the NEDS Directory as its own Directory. 

10.15-p11 In case the ANWI cannot use the NEDS Directory as its own Directory: 

A. The NEDS Contractor shall establish its own directory or data repository 

on the ANWI with ANWI Contractor supervision; 

B. The ANWI directory or data repository shall interface with the NEDS either 

through the NEDS Meta-tool, or directly by reading/writing into the NEDS 

Directory through LDAP and as required by the agreement. 

10.16 NATO Cyber Defence Incident Response Centre (NCIRC) FOC 

Project (HN:NCIA) 

10.16-p1 The NATO Computer Incident Response Capability (NCIRC) is that part 

of NATO’s Information Assurance effort that provides the capability to respond to 

computer and network security threats and vulnerabilities rapidly and effectively due 

to its preparedness to respond to Information Assurance-related incidents as they 

occur. 

10.16-p2 NCIA is responsible for the NATO Cyber Defence Incident Response 

Centre (NCIRC) Full Operational Capability (FOC) project which will provide the 

central agent for maintaining the end-to-end security of NATO networks by: 

A. Providing NATO-wide protection, detection and response mechanisms to 

cyber-attacks wherever NATO CIS systems are located (static or 

deployed); 

B. Providing “Rapid Reaction Team” (RRT) capability; 

C. Enabling NATO to collaborate with Nations on cyber defence. 

10.16-p3 

The NCIRC functional organization is described in the figure below. 





Figure 10.5: NCIRC Functional Organization 

10.16-p4 This project will prepare the NCIRC services to which the NNHQ ANWI 

will integrate at the tier-3 level. More information can be found in Annex E Appendix 

2. 

10.16-p5 As part of the NCIRC FOC project, N-CIRC Tier-3 sensors including N- 

IDS/IPS, Online computer Forensics, full packet capturing devices, online 

vulnerability assessment tools and log aggregation will be implemented in the new 

NATO HQ by the NCIRC Contractor. 

10.16-p6 The ANWI Contractor shall support the NCIRC FOC Contractor in the 

implementation of the above mentioned hardware and software on the different 

security domains of ANWI where NCIRC will be installed. 

10.17 NATO Public Key Infrastructure(NPKI) Project (HN: NCIA) 

10.17-p1 The NPKI project will achieve a PKI environment for NATO that fully 

complies with reference 1.1.1.6.11 . 

10.17-p2 The purpose of a NPKI is to generate, distribute and manage 

cryptographic keys, electronic certificates and electronic Certificate Revocation Lists 

(CRL), which in turn allows for securing the electronic IT environment. 

10.17-p3 As a part of this NPKI architecture the NNHQ will have its own 

Registration Authority (RA) provided by the NPKI project. 

10.17-p4 Reserved . 

10.17-p5 NPKI will ultimately be fully integrated and interoperable with virtually 

every other NATO CIS system. Interoperability with NATO systems will be achieved 

through implementation of common data structures based on international standards 

(X.509 certificates and Certificate Revocation Lists (CRLs)) and common protocols. 





Final interoperability will be achieved through tight cryptographic integration at the 

operating system level to ensure full compatibility. 

10.17-p6 

HQ. 

NPKI Capabilities will be provided by the Purchaser for the new NATO 

10.17-p7 The ANWI Contractor shall interface the ANWI network services with 

the RA to provide digital signature capability on the ANWI. 

10.17-p8 The ANWI Contractor shall provide support to the NPKI Contractor to 

establish the RA and use the NPKI services to implement NPKI enabled ANWI 

services. 

10.17-p9 The ANWI Contractor shall integrate NPKI issued certificates and 

services in the different ANWI provided services. 

10.17-p10 Public/Private Certificates and CRL need to be integrated with different 

ANWI provided components like: 

A. Active Directory for the Client Authentication with smart cards; 

B. Secure VPN components; 

C. SSL services (Web Services) 

D. Networking services. 

10.17-p11 

NPKI certificates and CRL information is stored in NEDS. 

10.18 Public Internet Access (PIA) Project (HN: NCIA) 

10.18-p1 The PIA Project provides a reliable, secure, resilient and managed 

Internet Services Gateway (ISG) from a commercial service provider to access Public 

Information Services. The ISG includes relay, protect, and filter internet access 

(browsing, web publishing, extranet), and internet e-mail traffic to and from 

Connected commands. The ISG enables remote users to access the network 

services and internal resources provided by the ANWI Business Network. It also 

provides access to the Internet. 

10.18-p2 The scope of the PIA Project is to provide centrally managed Internet 

access for all Bi-SC AIS Commands and other entities that are part of the NUWAN, 

to provide Remote Access for roaming users to their Commands and to provide 

NATO Unclassified / NATO Restricted (NU/NR) WAN Enterprise Services to allow 

NU/NR email exchange and functional services to/from the Internet. 

10.18-p3 The PIA’s Internet Services Gateway will be installed on NATO 

premises and support outsourced to the PIA Contractor. The infrastructure to provide 

the PIA services will be delivered installed and owned by the PIA Contractor. The PIA 

Contractor will be responsible for the provision of the services as well as operation 

and maintenance of the equipment, i.e. the PIA Contractor will be responsible for the 

overall lifecycle of the PIA infrastructure during the period of performance of this PIA 

contract. 

10.18-p4 The PIA Gateway will connect into the NGCS layer and interface with 

the ANWI (Business and Public) domains through the NGCS interfaces. 




10.18-p5 The following services will be provided: 

A. Public Internet Access 

B. Remote user Access 

C. Site-to-Site VPN 

D. External DNS 

E. Proxy Service 

F. Reverse Proxy Service 

G. Email Proxy Service 

H. Web Hosting and Publishing Service 

I. Information Assurance Services 

J. Virtual machine Hosting Service 

K. Mobile Messaging and Web Proxy Service. 


10.18-p6 The initial classification of the PIA will be NATO UNCLASSIFIED but 

may be upgraded to NR. 

10.18-p7 More details on the PIA can be found in reference 1.1.1.8.9. 

10.18-p8 The NNHQ Site will be provided with a PIA node that needs to be fully 

integrated into the ANWI capability. 

10.18-p9 The ANWI will be connected to the NGCS (NU), which will then be 

connected to the PIA capability. The configuration of the Public and Business 

domains of the ANWI will be influenced by the PIA services. 

10.18-p10 The PIA configuration details shall be discussed in detail, and agreed 

by the Purchaser and the ANWI Contractor. 

10.18-p11 The ANWI Contractor shall integrate the PIA node capabilities into the 

ANWI capability. 

10.19 Programme Management and Integration Capability(PMIC) 

Project (HN:NCIA) 

10.19-p1 The PMIC laboratory provides integration test services for NATO wide 

networks, IA and AIS services 

10.19-p2 PMIC details can be found in reference 1.1.1.8.15. 

10.19-p3 

Access to the PMIC will be given by the Purchaser. 

10.19-p4 The ANWI Contractor shall interface the ITS with the PMIC laboratory to 

support end-to-end services testing where integration or interoperability with NATO 

wide network, IA or AIS services is/are required. 

10.20 NATO Messaging Services(NMS) Project (HN: NCIA) 

10.20-p1 The NMS project provides (hardware and software) the NATO Secret 

Bi-SC AIS with formal a messaging infrastructure. The messaging client upgrade is 

not part of the NMS project scope. 

10.20-p2 The NMS will be provided as a NATO wide service that is currently 

available in the NATO HQ 





10.20-p3 The NMS is to be seen as a specific application with multiple interfaces 

into ANWI (Client, Infrastructure) or via ANWI (such as NEDS, NPKI, and NGCS). 

10.20-p4 More details on the NMS can be found in reference 1.1.1.8.16. 

10.20-p5 The Interface requirements are described in Paragraph 12.5.2. 

10.20-p6 The ANWI Contractor shall support the Purchaser to interface the ANWI 

capabilities with the NMS application configuration. 

10.21 Bâtiment Z Space to Support Integration and Testing Services 

(ITS) (HN: NCIA) 

10.21-p1 The Integration and Testing Services (ITS) facility will be installed and 

operated within the NCIA premises inside Bâtiment Z located in the current NATO 

HQ Campus. 

10.21-p2 The Purchaser will provide Power & Cooling, floor space for ITS racks 

and office space for the ITS. 

10.22 Current NATO HQ Security Communications (TETRA) 

10.22-p1 A TETRA Security Communications is currently in operational use on 

the NATO HQ campus. 

10.22-p2 In the case a decision is taken to reuse the current system for the new 

NATO HQ, this system will be PFE to the ANWI Contractor. 

10.22-p3 

5. 

The ANWI Contractor requirements are described in Annex I Appendix 

10.23 Enterprise Agreement Software (HN: NCIA) 

10.23-p1 Microsoft products are subject to a NATO Enterprise Agreement (EA) 

between NATO and Microsoft. 

10.23-p2 All Microsoft products, with the exception of client OEM Operating 

Systems on COTS computers, necessary to support the implementation of the ITS 

and the implementation of the ANWI in the new NATO HQ may be provided by the 

Purchaser under this EA as PFE to the Contractor unless the ANWI Contractor’s cost 

of the software with assurance is able to be provided at a lower cost. 

10.23-p3 The ANWI Contractor shall provide the most current client device 

Windows OEM Professional Operating System at time of delivery. The OS shall be 

pre-installed on all new windows based client devices. 

10.23-p4 The ANWI Contractor shall integrate the NATO provided software 

baseline into the ANWI capabilities. 





SECTION 11. Annex C: ANWI Architecture ”Logical View” 

11.1 Introduction 

11.1.1 Purpose 

11.1.1-p1 The purpose of this technical annex is to provide background 

information about the NNHQ architecture and architecture governance, introduce the 

ANWI services and introduce the architecture logical view by means of certain 

architecture operational views. 

11.1.2 Annex Structure 

11.1.2-p1 This Annex contains the following sections: 

A. Section 11.2 describes the NNHQ architecture governance and introduces 

the architecture principles. 

B. Section 11.3introducesanoverarching services framework based on the C3 

services classification taxonomy. 

C. Section 11.4 introduces the ANWI services and maps those to the 

services framework. 

D. Section 11.5 introduces the key operational information domains and 

NNHQ user types. 

E. Section 11.6 is providing the operational node connectivity showing the 

high-level connectivity of internal and external operational entities to the 

ANWI capability and domains. 

F. Section 11.7 is providing the high-level ANWI driven Information Exchange 

Requirements for each of the domains, and in more detail which user 

types will have access to what ANWI services. 

G. Section 11.8 is providing the overarching Information Assurance 

Architecture concept and requirements 

11.2 Architecture Governance and Principles 

11.2.1 NNHQ Architecture Governance 

11.2.1-p1 NATO HQ CIS architecture governance for this project is covered by: 

A. Various target architectures that detail the technology and solution 

architecture for a specific architecture target. Two main categories of 

target architectures are being governed which are of importance for the 

ANWI project: 

1. Old building 

a. NR-2 TA governing the ICT capabilities that will be implemented under 

the NR-2 project, delivery in the old building. 

2. New Building 





b. NNHQ ICT TA governing what ICT capabilities need to be established 

for the NNHQ [1.1.1.7.1]. The TA includes a comprehensive list of 

ICT services, among which are ANWI and Business Application 

services. 

B. Requirements governance. High level NNHQ programme level 

requirements, called needs and features, are mapped to the TA as well as 

assigned/mapped to the various projects. The requirements statements in 

this SoW (all “shall statements”) map to the overarching needs and 

features as assigned to the ANWI project. 

11.2.1-p2 The various architectures are periodically updated as part of the 

architecture governance scheme. For the NNHQ TA update there is a directive 

(1.1.1.7.10) that requires the inclusion of results from NNHQ projects into the NNHQ 

ICT TA to ensure that the TA remains consistent and coherent with evolving design 

solutions as shown in figure 11.1. Figure 11.1 identifies the interrelationships of the 

various architectures and project design/architecture artefacts. 

Figure 11.1 NATO HQ architecture governance 





11.2.1-p3 The NNHQ ICT projects, and henceforth the ANWI design as specified 

in Sections 2 and 5, shall provide technical information, through the various design 

level products, that include the following information that will help the ANWI Target 

Architecture Authority (HQPO) to compose the following architecture „views‟ (as 

further specified in the NATO Architecture Framework version 3.0 reference 

1.1.1.8.19). 

11.2.1.1 NSV-1 System Interface Description 

11.2.1.1-p1 The purpose of the System Interface Description is to illustrate 

which systems collaborate in which way to support the information exchange needs. 

The following are documented in an NSV-1: 

A. systems and their interfaces 

B. system use dependencies between interfaces 

C. system collaborations (systems interacting with each other through their 

interfaces) 

D. distributions of software systems to hardware systems 

E. connections between hardware systems 

11.2.1.1-p2 NSV-1 is best described as a graphical diagram depicting how 

systems are collaborating through their interfaces to realize the information 

exchanges between different domains. The diagram must be accompanied by a 

textual specification of all the graphical elements included in the diagram. The 

descriptions of systems and system interfaces should also include details concerning 

the functionality provided by each system; the procedures governing system 

implementation; the infrastructure supporting the systems; the quality with which the 

system offers its system services; and the means by which the system processes, 

manipulates, stores, and exchanges data. 

11.2.1.2 NSV-2, Systems Communication Description 

11.2.1.2-p1 The purpose of Systems Communication Description is to provide a 

comprehensive specification of how systems are connected at a detailed 

infrastructural level, what interfaces each system exposes (ports), the hardware 

interfaces used, and the protocols that govern transmission of data across the 

interface. NSV-2 enables acquisition specialists and system engineers to quickly plan 

and visualize how communications between systems are to be implemented. 

11.2.1.2-p2 The NSV-2 view can be split into three sub-views which define the 

communication links between systems. The sub-views are: 

A. NSV-2a System Port Specification: it defines the ports on each system, 

and the protocol / hardware stack that is specified or implemented for each 

of those ports. 

B. NSV-2b System to System Port Connectivity: it defines the connections 

between individual ports and shows the protocols and hardware 

specification used for each connection. 

C. NSV-2c System Connectivity Clusters - defines the bundles of system to 

system connections that go to make up an inter-nodal connection (see 

NSV-1). 




11.2.1.3 NSV-4 System functionality description 


11.2.1.3-p1 The primary purpose of the System Functionality Description is to: 

A. Describe systems that are outlined in NSV-1 in more detail, both in terms 

of structure (functional decomposition of systems) and behaviour (data 

flows between system components that realize certain system functions). 

B. Develop a clear description of the necessary system data flows. 

C. Clearly describe the allocation of system functions to specific systems, 

system components and/or nodes and thus clearly delineate lines of 

responsibility. 

D. Analyse the construction of NSV-1 systems to provide a basis for the 

determination of the quality requirements for systems and making 

decisions about streamlining, combining or omitting system functionality. 

11.2.1.3-p2 The complementary technical views originated by Contractors as 

part of the design phases will become part of future TA releases. For this reason text 

shall be provided as Microsoft word documents and figures in Visio, EA (Enterprise 

Architect) or scalable JPEG format. 

11.2.1.3-p3 The schedule for the Contractor’s inputs to the ICT TA isdriven by 

the schedule of ANWI design and testing products as reflected below: 

ANWI Product 

Initial ANWI Design 

Final ANWI Design 

Initial ANWI Design 



Post solution Design 

Pre-Integration Testing 

Post-Integration Testing 

Type of Input 

Develop High-level Design document, identifying elements 

within the solution having „relevance‟ for the ICT TA. 

Produce & Develop solution Design document, including initial 

version of NSV1. 

Produce & Develop solution Design document, including initial 

version of NSV1, NSV2 and NSV4 views. 

Update/Develop further NSV1, NSV2 and NSV4 views. 

Produce final NSV1, NSV2 and NSV4 views in line with new 

releases of the ICT TA. 

Refine as required NSV1, NSV2and NSV4 views according to 

integration testing results. 

Table 11.1 Provisional schedule Contractor input ICT TA 





11.2.1.3-p4 The ANWI Contractor shall incorporate the following key 

architecture principles for the ANWI design and identify any limitations of his design 

from these perspectives: 

A. Security: All solutions and foreseen services are subject to security 

accreditation by the NATO HQ Security Accreditation Authority. Solutions 

shallbe in accordance with NATO security policies, directives and 

guidelines (references in section 1.1.1.6). 

B. Scalability: All solutions shall be scalable. A change to the number of 

NATO member Nations, number of partnership Nations, number of 

Agencies or a relocation of any of these within the building must be 

facilitated and absorbed by the solution facilities scale up capability as 

provided: The base capacity of the solutions provided shall support at 

least 25% extra capacity expansion in 

numbers/performance/storage/functionality etc. given the estimated 

service capacity requirements for the next 5 years starting to count from 

day-1 operation (FOC), without having to upgrade the components 

provided. Scalability scenario’s beyond the 25% level shall be supported 

preferably through scale up scenario’s but may require scale out level 

upgrade of major components in the infrastructure. 

C. Commercial Off The Shelf (COTS) Products: To ensure satisfactory 

maintainability of the solutions provided, 'Commercial Off The Shelf' 

(COTS) products shall be used as much as possible. Custommade/proprietary 

solutions should be avoided, wherever possible and 

justified whenever proposed. 

D. Reliability, resilience and robustness: The ANWI contractor shall consider 

reliability of components and solutions, resilience and robustness as key 

principles of their solutions in order to guarantee continuity of service 

(even in the case of a major incident). 

E. Flexibility: All provided solutions, services, etc. shall be adaptable with 

minimal effort to change. Changes in technology, technology standards or 

usage of the solutions must be possible without undue adverse effect 

upon the overall design or minimal downtime. 

F. Convergence: In the design and delivery of ANWI services, solutions, 

functions, or networks, etc. consolidation and rationalisation shall be taken 

into account to the maximum extent possible, in order to realize efficiency 

and synergistic savings providing flexibility in utilisation and the 

management of the NNHQ’s services. 

G. Management of Services: All solutions shall include a maximum level of 

automation of Service Management and Control functions providing 

remote management capabilities, to allow full flexibility in the way NATO 

decides to organize the management of the solution (i.e. centrally, 

integrated, stove-piped, etc.) in order to reduce the need for human 

intervention. 

H. Future proofing: To maximise the return on investment, proposed solutions 

shall aim to 'future-proof' the installation by providing easy and sustainable 

'upgrade paths' in terms of: 







1. Adherence to standards (i.e. Non-proprietary solutions). 

2. Capability to exploit technology advances. 

3. Implementation of future improvements supporting performance & 

quality. 

i. State-of-the-art Technology: The ANWI contractor shall exploit the latest 

'state-of-the-art' technology (NB. 'Experimental' or 'Unproven' solutions 

shall NOT be implemented, since they are unlikely to be 'accreditable' in 

the required timescale). 

J. Interoperability: Delivered solutions shall demonstrate an appropriate 

degree of 'interoperability' with both 'local' (on-campus) and 'remote' (offcampus) 

NATO facilities and systems, as indicated within the project 

specifications. 

K. Safety: Safety is a key principle that shall be taken into account when 

designing and delivering solutions. Health and safety risks are to be 

minimized by providing safe and healthful work environments, preventing 

unsafe acts and controlling exposures to health and safety hazards in the 

workplace. 

L. User Experience: All solutions shall be user-friendly and suitably 

'performant' in order to maximize user experience, automation and 

minimize training and change management needs. 

11.3 Services Framework 

11.3.1 Applied Service Framework References 

11.3.1-p1 The NNHQ ANWI services concept is derived from NNHQ ICT target 

architecture (see reference 1.1.1.7.1) and has adopted the NATO C3 services 

taxonomy framework (which is based on the NATO Network Enabled Capability 

NNEC paradigm as high-level template to model and classify ANWI services, show 

their interrelationships, and show the linkage to business applications and business 

processes. 

11.3.2 C3 Taxonomy Services Framework 

11.3.2-p1 Figure 11.2 shows the C3 services taxonomy framework that is used to 

model and classify the ANWI services that will be described and specified in Annexes 

E to I. In the remainder of this section a short introduction into the main concepts and 

principles of the frameworkis provided. 

11.3.3 Services Framework Main Concepts 

11.3.3-p1 The model is based on a producer consumer model of services. The 

main philosophy of the taxonomy framework is to be able to visualise which 

applications or user clients use services as provided by the ICT (technical) Services. 

The model should not be perceived as a strict layered model: applications, clients or 

services can have direct access to any service in the model. 

11.3.3-p2 One of the main objectives of the model is to visualise and analyse the 

(re)use of services by applications to promote capabilities not to develop their own 

solutions for certain common available ICT services.



11.3.3-p3 A key part of the C3 taxonomy framework is composed of the ICT 

technical services, as produced by Information and Communication systems 

equipment, subdivided into three groups: 

A. Communications services, subdivided into: 

1. Transmission Services 

2. Transport Services 

3. Communications Access Services 

B. Core Enterprise Services, subdivided into: 

1. Infrastructure Services 

2. SOA foundation services 

3. Enterprise Support Services 

C. Community of Interest (CoI) services 

11.3.3-p4 The C3 framework identifies Applications and User Appliances (clients). 

These are the user facing capabilities that are using services to get a capability 

function delivered to the end users in support of the business processes. 

11.3.3-p5 Common to these three groups of services are two overarching services 

groupings: 

A. Service Management and Control (SMC) services. 

B. Information Assurance Services. 

11.3.3-p6 Due to the special nature of the SMC and IA services, they should not 

be seen as unique self-contained services, but as services that integrate with all 

other services: 

A. As a part of horizontal integration: 

1. Each of the ICT services will have embedded IA and SMC features. The 

SMC service features are better known as “Element Management 

Services”. 

B. As part of the vertical integration: 

1. All SMC and IA (embedded) features contribute to the NATO ICT 

(SMC) and IA business processes: 

C. ICT related business processes are driven by the ITIL framework. 

1. IA related business processes are driven by the NNHQ Security 

CONOPS and are linked with the NCIRC capability. 

D. Vertical integration of consolidated IA and SMC information will be part of 

SMC and IA Services which are described in Annex E. 





Figure 11.2: C3 Services Framework 



11.4 ANWI services 


11.4.1 ANWI ICT Technical Services Groupings 




11.4.1-p1 To facilitate a coherent approach for services implementation and 

provision the ANWI services have been bundled into the following groups fuly in-line 

with the C3 services taxonomy and will be further specified in Annex E to I: 

A. Annex E: IA and SMC Services: The ANWI IA and SMC Services. This 

grouping is about the specialist CoI IA and SMC services and IA and SMC 

(user) applications to allow ICT and IA capability management and 

planning. Generic services features provided in this area are monitoring, 

reporting, configuration and change management, capacity and 

performance management, analysis, etc. 

B. Annex F: Infrastructure Services: The ANWI infrastructure services are the 

foundation services for all NNHQ ICT services and include processing, 

storage, LAN services and the means to integrate to these foundation 

services. A special element of the infrastructure services are the cross 

domain modules which will enable ICT services from inside the HQ 

perimeter (local) to the external NATO ICT services as well as enabling 

cross security domain services both for internal and external HQ 

purposes. 

C. Annex G: Unified Communications and Collaboration (UCC) Services: The 

ANWI UCC services shall enable a unified and converged capability for all 

users to effectively and efficiently communicate and collaborate via a 

consistent ICT capability. 

D. Annex H: Client Provisioning Service: The ANWI client provisioning 

service shall enable the provisioning of client based services to the end 

user. The client provisioning service shall provide generic services and 

support for many different client device form factors in support of the 

various user profiles. 

E. Annex I: Supplementary services: A bundling of mainly communications 

focused services that enhance the functionality of the ANWI foundation 

services as specified in Annex to H: Wireless and GSM blocking, GSM 

services, IPTV and Secure Site Communications. 

11.4.2 ANWI Services Listing 

11.4.2-p1 Given the groupings as introduced in the precious section the following 

ANWI (technical) services are identified in table 11.2. 

Services 

Short Description 

1 SMC and IA Services See Annex E 

1.1 Service Management and Control(SMC) All management services to ensure monitoring and provisioning 

of ANWI services. 

1.2 Information Assurance (IA) All IA services related to (centralised) security management and 

monitoring of the ANWI related IA element services 

2 Infrastructure Services See Annex F 

2.1 Processing Processing/computing services in support of any other service. 

2.2 Storage Storage services in support of any other service.



Services 

Short Description 

2.3 Printing & Scanning Network enabled printing and scanning services. 

2.4 Network Infrastructure Infrastructure network services that resolve network wide 

infrastructures services (such as naming). 

2.5a LAN (Wired) Network services for LAN and computer room environments 

(wired) 

2.5b LAN (Wireless) in-building Wireless LAN services. 

3 Unified Communications and Collaboration 

Services 

See Annex G 

3.1 Voice Telephony voice services 

3.2 Voicemail Telephony voice mail service 

3.3 Video-Teleconferencing (VTC) Video teleconferencing engaging VTC, VMR and desktop level 

VTC elements. 

3.4 E-mail Email service (with attachments and labelling) 

3.5 Unified Messaging Unified messaging integrating/routing all UCC messaging 

oriented services (IM, chat, mail, voice(mail)). 

3.6 FAX FAX services 

3.7 Instant Messaging (IM)/chat Instant messaging and chat service. 

3.8 Presence On-line presence information of users logged-on (or off) to the 

network. 

3.9 Directory Service Directory services that can help resolve any user entry to a UCC 

supported address on the network. 

3.10 Collaboration Basic collaborations services linked 

3.11 Mobility Service that allows users to access the available services based 

on where they are. 

4 Client Provisioning Annex H 

4.1 Software provisioning Provision of the required application software to become 

available for the applicable user client device. 

4.2 Client devices Various client form factor devices that would allow users to 

consume NNHQ ICT services (to include ANWI services) 

5 Supplementary Services Annex I 

5.1 GSM Provision and extension of public GSM telephony services 

inside the NATO HQ building at authorised locations. 

5.2 GSM Blocking Blocking of GSM signals to prevent GSM access in nonauthorised 

locations at designated time periods (such as 

conference rooms). 

5.3 Wireless Blocking Blocking of any kind of Wireless (LAN) protocols to avoid 

access to Wireless ICT capabilities at non-authorised locations at 

designated time periods (such as conference rooms) 

5.4 Site Security Communications Site security communication services in support of (radio) 

communications for the site security staff covering the NNHQ 

premise. 

5.5 IPTV Provisioning and (re)distribution of TV services (public and 

NATO channels) using IP network services. 

Table 11.2: ANWI Services Overview 

11.4.3 Identification of ANWI related End-to-End Services 

11.4.3-p1 The ANWI services are predominantly services that will be provided to 

other services (business applications) in order to provide an end-to-end user or 





application service. However table 11.3 shows the services where the ANWI project 

is responsible to provide end-to-end user services. Annex D will go in more detail 

showing end-to-end information flows as related to end-to-end services provisioning. 

Service 


SMC services 

IA services 


Web browsing 

File services 

Print services 

UCC services 

Email 

Instant Messaging 

Voice and Voice Mail 

FAX 

VTC 

Collaboration 

Unified Messaging 

Presence 

Client-Provisioning 

(no direct end-user service} 


GSM 

Site Security Comms 

IPTV 

End-to-End Functionality 

Provision of SMC services and information to ICT managers and administrators in support 

of local and enterprise ICT services planning, management and O&M. Provision of SMC 

information interfaces to Business Applications. 

Provision of IA management services to IA managers and administrators in support of the 

local and enterprise IA management functions. 

User web browser based access to web based information services and sources. Provision 

of application based access to web portal or web services through the HTTP protocol. 

User access to file shares (home drive, specialist drives). 

User access to printing via ANWI based MF printer-scanner devices. 

User based email access services via the user email applicationclient (outlook or other 

mail client). Application based SMTP based messaging interface to information transfer. 

User based instant messaging services via user IM application client (today LYNC for the 

desktop). IM application services interface. 

End user voice services available through user client devices that support voice services. 

Automated FAX services interface to send and receive FAX to/from external 

organisations. No physical FAX end devices. 

End user VTC in conference room down to desktop VTC format. 

Calendar, user document or desktop sharing. 

Integration of different electronic messages and media (e-mail, SMS, Fax, Voicemail, 

video messaging) into a single user interface accessible from a variety of different devices. 

User based presence information shared through user collaboration services application 

client (today LYNC for the desktop). 

N/A as clients are provided under the service, other than that the native local client 

services are available through each different client form factor. 

ANWI will assure GSM services are accessible and relayed at authorised locations at the 

NNHQ building premise. 

Site Security Communication Services for NOS. Dedicated service. 

IP television services where users can watch (NATO) television channels 

Table 11.3: ANWI end-to-end services 

11.5 ANWI Information Infrastructures, Domains, Zoning and User 

Types 

11.5.1 Introduction 

11.5.1-p1 The ANWI architecture need to be flexible and expandable to support 

many different Communities of Interest (CoI) and related user types. Following a 

“traditional” approach where each CoI would be hosted on complete separate 





infrastructure (e.g. networks) would create a plethora of numerous segregated 

networks with poor interoperability options, high management complexity and high 

security risk profile. To prevent this from happening NATO has issued a policy for the 

rationalisation of information infrastructures based on their classification levels . The 

policy is providing guidance for NATO to adopt two major Information Infrastructures 

that will be able to support handling information at all required classification levels: 

A. An Infrastructure that can support Secret classification levels. 

B. An Infrastructure that can support NATO Restricted, NATO Unclassified 

and Unclassified (Public) classification levels. 

11.5.1-p2 For the current NR-2 network this approach is followed as is reflected in 

NR-2 Target Architecture Document (Ref. 1.1.1.8.5). The ANWI architecture is taking 

the NR-2 architecture forward in enhancing the capabilities for the two major 

infrastructure and its internal and external interfaces. Once cost effective security 

technologies and mechanisms become available, compliant with the extant NATO 

security policies and guidance, further rationalisation of infrastructures may be an 

option and the ANWI Contractor shall include these in the ANWI design. Initial results 

in sharing LAN, storage and processing infrastructure have been achieved and will 

be addressed in the Infrastructure Services Annex F. 

11.5.1-p3 The concept of Zoning is used to logically or physically segregate and 

protect Communities of Interest or information services. The segregation in Security 

Zones (e.g. Public Security Zone, NATO UNCLASSIFIED Security Zone, etc.) 

enhances security as whole. Dividing the ICT infrastructure into separate logical 

security zones is lessen the burden of security controls in areas with open access 

requirements and high tolerance for downtime and strengthens security for those 

areas that need additional protection and high availability. 

11.5.1-p4 Zoningcan be achieved at one or more network layers (mainly at Layer 

2 and 3 according to the OSI RM), and using one or a combination of different types 

of technology as follows, but not limited to: 

A. Virtual Local Area Network (VLAN) 

B. Private Virtual Local Area Network (PVLAN) 

C. Access Control List (ACL) 

D. VLAN Access Control List (VACL) 

E. Multiprotocol Label Switching (MPLS) 

F. Virtual Private Network (VPN) 

G. Virtual Private LAN Service (VPLS) 

H. Virtual Device Context (VDC) 

i. Firewall and IDS/IPS capabilities distinct at each layer 

j. Distinct Firewall leg and port 

k. Distinct Virtual Switch (vSwitch) 

11.5.1-p5 The concept of User Types is used to diversify different types of users 

that would be involved in NATO HQ business and can be identified as users that 

reside either internal or external to the NATO HQ building. 

11.5.1-p6 A security domain is a special case of a zone where the physical and 

logical zoning is delimiting a specific (NATO HQ) Community (subset of user types) 

for which a set of well-defined security rules and behaviours is defined. 





11.5.1-p7 In addition to the perspective of security domains it is worth introducing 

the concept of Cross Domain: given the fact that CoI’s may reside in one or multiple 

domains, they may have Information Exchange Requirements (IERs), that cause that 

information need to be provided across domains and zones supported by cross 

domain solutions such as firewalls, gateways and proxies. 

11.5.2 ANWI Security Domains 

11.5.2-p1 Figure 11.3 shows the ANWI security domains in the perspective of the 

two major infrastructures as introduced in the previous section and introducing the 

perspective of cross domain to either internal or external domains of the NATO HQ. 

Figure 11.3 ANWI Security Domains. 







11.5.2-p2 There is a need for four different security domains: 

A. NATO SECRET (NS): The NS domain shall provide a local area network 

for use at up to and including the NATO SECRET classification level. It 

also provides interconnectivity to the NS wide area network, used 

throughout NATO for Command and Control. The security classification is 

NATO SECRET.The current NS domain (called Minerva) is the primary 

HQ user domain. Based on the future plans for NATO HQ the NS domain 

shall reduce in size and complexity, many of its functions being transferred 

to the Business domain. However, the authoritative repository for official 

documents, their handling and distribution, shall remain on the NS domain, 

and shall be supported with the appropriate information management 

mechanisms. 

B. EAPC: The EAPC domain shall provide an information sharing capability 

or use at up to and including the EAPC SECRET classification level, 

provided for non-NATO delegation staff to access NATO documents, 

which are releasable to the EAPC. The security classification is EAPC 

SECRET. The EAPC network is a local-only domain for the NATO HQ, the 

authoritative repository for all official documentation of non-NATO EAPC 

Delegation users. 

C. Business (NU/NR): The Business domain shall serve as the primary 

domain for business operations in the NATO HQ Building, providing 

information sharing capability for use up to and including the NATO 

RESTRICTED classification level. This shall also provide connectivity to 

NR networks in NATO and to the Internet, through Public Information 

Access (PIA) Gateways. The Business domain shall service the highest 

number of users of all networks. It shall provide access to the Internet for 

its users. 

D. Public: The Public domain shall have a relatively simple architecture for 

local HQ use only, providing user services coverage of only a part of the 

HQ premise, offering only a limited range of end-user services, including 

web access, services. This domain will primarily support visitors to the 

Headquarters (such as journalists). In addition to its (limited) end-user 

services it provides wireless, IPTV and voice UNCLASSIFIED access 

services throughout the building. 

No. 




1 SMC and IA Services 

1.1 Service Management and Control(SMC) Y Y 1 Y Y 1 

1.2 Information Assurance (IA) Y Y Y Y 


2.1 Processing Y Y Y Y 4 Y 

2.2 Storage Y Y Y Y 4 Y 

2.3 Printing & Scanning Y Y Y Y 

2.4 Network Infrastructure Y Y Y Y Y 

2.5a LAN (Wired) Y Y Y Y Y 2



No. 




2.5b LAN (Wireless) 


3.1 Voice Y Y 3 Y 

3.2 Voicemail Y Y 

3.3 Video-Teleconferencing (VTC) Y Y 

3.4 E-mail Y Y Y 


3.6 FAX Y Y 

3.7 Instant Messaging (IM)/chat Y Y 

3.8 Presence Y Y 

3.9 Directory Service Y Y Y 

3.10 Collaboration Y Y 


4 Client Provisioning Services 

4.1 Software provisioning Y Y Y Y 2 

4.2 Client devices Y Y Y Y 


5.1 GSM n.a. 

5.2 GSM Blocking Y 7 

5.3 Wireless Blocking Y 7 

5.4 Site Security Communications (Radio) N/A 

5.5 IPTV Y 3 Y 5 

Key: 1 limited Management capability; 2 Only for Kiosk PC’s; 3 Software Clients; 4 Extranet 

Applications & DB (DMZ) – Up to NU security domain only exists in the Data Centre. 5 Shall cover 

both IPTV streaming and Browser accessible IPTV services; 6 No specific Business WLAN service – 

Mobile business clients shall use the Public WLan to establish secure (VPN) connection with Business 

security domain; 7 Static GSM/WLAN Blocking capabilities shall be managed from the Business 

network. Mobile GSM/WLAN Blocking capabilities are not networked. 

Table 11.4: Overview Services per security domain 

6 

Y 

11.5.2-p3 The table provides an overview of the services that shall be made 

available each security domain. This table doesn’t provide details about the 

classification of the information handled by the services. 

11.5.3 User Types 

11.5.3-p1 Table 11.5 shows the different types of users identified for access to the 

New NATO HQ ICT and a short description. More elaborate descriptions can be 

found in the NNHQ ICT Target Architecture. 





User Type 

U1 - NATO HQ User 

U2 - NATO HQ Nation User 

U3 - NATO HQ Partner User 

U4 - Conference User 

U5 - NATO HQ Conference User 

U6 - NATO HQ Event User (peak) 

U7 - NATO HQ Mobile User 

U7a NATO HQ Mobile User (NRoI) 

U7b NATO HQ Mobile User (NS) 

U8 - NATO HQ Remote User (RU) 

U8a - NATO WAN Remote User 

U8b - Non-NATO Remote User 

Short description 

individuals who are permanent, temporary or 

contracted employees of NATO, its Agencies and 

Commands 

a User working in a NATO Nation Permanent 

Representation to NATO HQ (a.k.a Delegation) 

or a NATO Nation Military Representation to 

NATO HQ (a.k.a. MilRep). 

an individual associated with Euro-Atlantic 

Partnership Council Nations 

a user who is visiting NATO HQ to participate or 

brief in a meeting or conference and is not 

working at the HQ or has no NATO security 

clearance. Affiliated to NATO member nation. 

a user who is to participate or brief in a meeting 

or conference and is working at the HQ 

present at the NATO HQ site during a Special 

Event e.g. a Summit, Ministerial or exhibition. 

User that is away from the NATO HQ site but 

needs connectivity to certain ICT services. 



delivered at the NATO HQ site up to NR 

(common business service) 



delivered at the NATO HQ site up to NS 

(authorised under exceptional circumstances) 

a User that is located away from the NATO HQ 

Campus. 

a type of user in a NATO location that connects 

to a Network that provides access to the NATO 

WAN in a certain way, at the NS level or at the 

NR level 

A Non-NATO Remote User (U8b) is a type of 

user associated with: 

• NATO Nations (located in Capitals and 

elsewhere), 

• NATO Partners, 

• National Delegations, 

• Military Representatives, 

• Other International Organisations (e.g. EU), 

• NGO and other organisation extranet users 

U8c - Home Worker 

type of NATO HQ Users (U1) accessing 

remotely certain NATO HQ ICT Services from 

the HQ information domain using a non-NATO 

owned device. 





User Type 

U8d - Internet Café User 

U9 - Public User 

U9a - Public User (the Public/Open Source) 

U9b Registered Public User 

U10 - NATO Remote Office User 

U11 - NATO HQ System Administrator User 

U11a NATO HQ Application Administrator 

User 

U12 - Non-NATO Troop Contributing Nation 

(NNTCN) 

U13 - Non-NATO Nation (7NNN) User 

U14 - Non-Personal Entity (NPE) User 

Short description 

type of NATO HQ Users (U1) accessing certain 

services away from the HQ using a non-NATO 

owned device from an Internet Café. 

A public user that connect to the NATO 

(extranet/web publishing services) using a 

public network. 

A public User that 

• accesses publicly available information e.g. the 

NATO public website or 

• exchanges non classified or unclassified e-mail, 

releasable for Internet Transmission, with a HQ 

User. 

A public user that is registered with NATO 

HQ but does not have to proof (NATO) 

identity. 

accesses services at NR or NS classification level 

from a protected environment, defined as a 

Remote Office. 

is usually a permanent employee of NATO. This 

type of user has access to Privileged Accounts 

a permanent NATO employee, who has 

privileged access to a specific Application 

is an individual in possession of a valid Personal 

Security Clearance based on a clearance 

procedure no less rigorous than that required for a 

NATO national in accordance with NATO 

security policy and supporting directives, who 

has access to NATO CIS and NATO/X CIS 

systems for the effectiveness of the Operation, 

Training, and Exercise activities and who has 

access to NATO/X CIS for the effectiveness of 

Transformation or Cooperation activities. 

See above: 7NNN Users are from Australia, 

Austria, Finland, Ireland, New Zealand, Sweden 

and Switzerland. 

is an authorized Communication Information 

System (CIS)‟ component (non-humankind) like 

but not limited to an ICT System, Network 

Device, Application process allow to authenticate 

its identity within a security domain, for various 

purposes, and ensure interoperability across 

security domains through NATO WAN or over 

the Internet with other international organizations 

and partners. 

NPE is most of the time a known CIS component 

authorized to perform automated tasks without 

human intervention on behalf of human 

individuals. 





Security 

Domains 

\ 

Users 

(access) 

Types 

NATO 

Secret 

EAPC 

Secret 

NATO 

Restricte 

d 

NATO 

Unclassif 

ied 

U01 - NATO HQ User 

U02 - NATO HQ Nation User 

U03 - NATO HQ Partner User 

U04 - Conference User 

U05 - NATO HQ Conference User 

U06 - NATO HQ Event User 

U07a - NATO HQ Mobile User (NRoI) 

U07b - NATO HQ Mobile User (NS) 

U08a - NATO WAN Remote User 

U08b - Non-NATO Remote User 

Y O N N Y N N Y Y N N N N N Y Y Y N N Y 

O N Y N O N N N N N N N N N N Y Y Y Y Y 

Y O N N Y N Y N Y 

U08c - Home Worker 

U08d - Internet Café User 

U09a - Public User 

U09a - Registered Public User 

U10 - NATO Remote Office User (U10) 

U11 - NATO HQ System Administrator User 

U11a - NATO HQ Application Administrator User 

U12 - Non-NATO Troop Contributing Nation (NNTCN) 

U13 - 7 Non-NATO Nation (7NNN) User 

U14 - Non-Personal Entity (NPE) User 

O 1 N N N N Y Y Y N N Y 

O O N N O N O N O Y O O N N O Y Y N N Y 

Public 2 Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y Y Y 

Table 11.5 Different types of user 

Legend 

(Y) Access to the security domain is allowed 

(O) Access to the security domain is allowed for limited users 

(N) Access to the security domain is NOT allowed 

1) under condition of usage of NATO (owned) NR approved access mechanisms 

2) used for Wireless and Telephony Access, except for U04 who use it for Public 

Domain User Services (e.g. Internet, Printing,..) 

11.6 Node Connectivity Diagrams 

11.6-p1 The Operational Node Connectivity is modelled from the perspective of the 

bundling’s of two major information infrastructures as explained in section 11.5: 

A. Secret infrastructure which is modelled through 

1. Security Domains: 

i) NS domain 

ii) EAPC domain 





2. Cross Domain Services allowing NS infrastructure Operational Nodes to 

share and exchange information with both internal as well as external 

entities. 

B. Business Infrastructure which is modelled through: 

1. Security Domains: 

i) NR 

ii) Public 

2. Cross Domain Services allowing Business infrastructure Operational 

Nodes to share and exchange information with both internal as well as 

external entities. 

11.6.1 NS Infrastructure Node Connectivity 

Figure 11.4 NATO SECRET node connectivity 

11.6.1-p2 Figure 11.4 subdivides into the following ways of node connectivity: 

A. NATO or NATO Nation users which are authorised ANWI services users 

and have direct LAN access (on premise) to the ANWI NS security domain 

using NATO ANWI provided clients. 

B. Conference users who are authorised to logon (dedicated guest accounts) 

to dedicate ANWI provided workstations in the Conference rooms in order 

to support a conference at the NS or EAPC classification level. 





C. NATO HQ staff users who have ANWI user accounts can logon on the 

conference room client to support and participate in the conference using 

the NATO HQ services authorised to be operated from those user 

locations. In addition, as and when the conference classification and 

arrangement allows, ANWI users can utilise their NS Mobile Client. 

D. NATO HQ Mobile user that is provided with a Mobile NS capable device 

with NS level VPN and uses a controlled public network access 

mechanism where NATO security staffs are convinced the end-to-end 

connectivity is secured. 

E. An ANWI user can logon to ANWI services through the NATO WAN or a 

dedicated NS link (exception) as and when this is facilitated in the remote 

user location. The ANWI user can either use a ANWI provided client or a 

NATO client provided in the remote location that allows the ANWI user to 

logon with his/her ANWI credentials. 

F. Dedicated and specific authorised access for administrators and or 

devices used for system administration or SMC purposes. Support through 

either dedicated logon from designated machines or using mobile devices 

that are be logically or physically connected to the ANWI infrastructure. 

G. Partner Nation users provided with ANWI clients can achieve (on premise) 

LAN based access to the EAPC security domain. 

H. Cross domain interconnection to the Business Infrastructure that support 

controlled information exchange/flows to and from the Business 

infrastructure (NR and Public security domains). 

I. Cross domain interconnection to other NS security domains 

interconnected via the NS WAN. 

J. Cross domain interconnection to other NATO Nation security domains 

interconnected via the NS WAN and the NATO IEG A and B services. 

K. Cross domain interconnection to other Mission Secret security domains 

interconnected via the NS WAN and the NATO IEG C services 

L. NNTC user who uses a ANWI provided client and user account can get 

access to certain designated services on the NS domain that are either 

logically or physically segmented using a cross domain solution. 

M. 7NNN user who uses a ANWI provided client and user account can get 

access to certain designated services on the NS domain that are either 





11.6.2 Business Infrastructure Node Connectivity 


Figure 11.5 Business Infrastructurenode connectivity 

11.6.2-p1 Figure 11.5 subdivides into the following ways of node connectivity: 

A. NATO or NATO Nation users which as authorised ANWI services users 

and have direct LAN access (on premise) to the ANWI NR security domain 

using NATO ANWI provided clients. 

B. Conference users who are authorised to logon (dedicated guest accounts) 

to dedicated ANWI provided workstations in the Conference rooms in 

order to support a conference at the NR or Public classification level. 

C. NATO HQ staff users who have ANWI user accounts can logon on the 

conference room client to support and participate in the conference using 

the NATO HQ services authorised to be operated from those user 

locations. In addition, as and when the conference classification and 

arrangement allows, ANWI users can utilise their NR Mobile Client. 

D. A NATO HQ mobile user, possessing aNRoI mobile client (including NR 

VPN), can get access via the ANWI public WLAN service to the NR 

domain. 





E. An ANWI user can logon to ANWI services through the NATO WAN or a 

dedicated NR VPN over a public network (as an exception) as and when 

this is facilitated in the remote user location. The ANWI user can either 

use a ANWI provided client or a NATO client provided in the remote 

location that allows the ANWI user to logon with his/her ANWI credentials. 

F. Dedicated and specific authorised access for administrators and or 

devices used for system administration or SMC purposes. Support through 

either dedicated logon from designated machines or using mobile devices 

that can be logically or physically connected to the ANWI infrastructure. 

G. Event users, using their own devices, will be granted controlled Internet 

Access using the Public WLAN capability. 

H. Cross domain interconnection to the NS Infrastructure that support 

controlled information exchange/flows to and from the NS infrastructure 

primarily the NS security domain. 

I. Cross domain interconnection to other NR security domains 

interconnected via the NR WAN or using an approved peer-to-peer NR 

VPN connection over a Public Network. 

J. Cross domain interconnection to Public (Internet) Interconnected domains 

representing business, NGO, etc. for. 

K. NATO or non-NATO user, using either its own or Internet café device 

getting access to a extranet portal reachable from the Internet using a 

NATO provided user account. Dependent on the type of usage access to 

various extranet information may be limited. 

L. Internet external user that will use the web browser to get access to the 

NATO external/web publish website: www.nato.int. Based on his/her 

credentials may have access to certain other web based services. 

M. NNTCN user who uses a ANWI provided client and user account can get 

access to certain designated services on the NR domain that are either 


N. 7NNN user who uses a ANWI provided client and user account can get 

access to certain designated services on the NR domain that are either 


11.7 Information Exchange Requirements (IERs) 

11.7-p1 The Information Exchange Requirements are modelled per key 

infrastructure for each of the operational nodes as identified and is compliant with the 

NATO Architectural Framework. 

11.7.1 ANWI NS Infrastructure IERs 

11.7.1-p1 In this section the operational information requirements for the NS 

infrastructure are summarized through Table 11.6. This table identifies the nature of 

the information exchange requirement (function), the involved nodes and the required 

information exchange attributes. The table includes only the IER’s of which the endto-end 

user level is within the responsibility of ANWI. 





Supported 

Operational 

Task 

Specific 

Missions, 

Functions 

or 

Activities 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Operational Elements 

Involved 

Information 

Consuming 

Node 

1-8 All ANWI 

NS 

connected 

users 

1-8 All ANWI 

NS 

connected 

users 

10 Partner 

Nations 

1-8 All ANWI 

NS 

connected 

users 

15-16 

NNTCN and 

7NNN 

1-8 All ANWI 

NS 

connected 

users 

14 Mission, 

domains 

1-8 All ANWI 

NS 

connected 

users 

Information 

Producing 

Node 

1-8 All ANWI 

NS 

connected 

users 

10 Partner 

Nations 

1-8 All ANWI 

NS 

connected 

users 

15-16 

NNTCN and 

7NNN 

1-8 All ANWI 

NS 

connected 

users 

14 Mission, 

domains 

1-8 All ANWI 

NS 

connected 

users 

13 NATO 

Nation, 

domains 

Description of 

Information 

Required Information Exchange Attributes 

Element 

Information Media Quality Type 

Data provided to ANWI Well 

entities to be access connected 

handled/integrate 

d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 

Data provided to 

entities to be 


d in NATO 

SECRET downto 

(NATO) 

UNCLASSIFIED 

processing 




d in 

CONFIDENTIAL 

down to (NATO) 

UNCLASSIFIED 

processing 




d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 




d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 




d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 




d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 




d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 

Cross 

Domain 

Cross 

Domain 

Cross 

domain 

full ANWI 

access 

Cross 

domain 

contained 

ANWI 

access 

Cross 

domain 

(IEG C) 

Cross 

domain 

(IEG C) 

Cross 

domain 

(IEG B) 

Well 

connected 

Well 

connected 

Well 

connected 

Well 

connected 

Well 

connected 

Well 

connected 

Well 

connected 

All UCC 

message, 

portal, file, 

voice, video, 

collaborations 

, directory 

message, file, 

labeled, 

directory 

Portal access, 

message, file, 

database 

access, 

directory 

All UCC 

message, 

portal, file, 

voice, video, 


, directory 

All UCC 

message, 

portal, file, 

voice, video, 


, directory 

message, 

portal, file, 

collaboration 

(chat), 

directory 

message, 

portal, 


(chat), 

directory 

message, 

portal, 


(chat), 

directory 

Capabilitie 

s 

UCC, web 

browsing, 

web access, 

storage-file 

share, 

directory 

Email, 

directory 

email, 

portal, file, 

database 

queries, 

directory 

UCC, web 

browsing, 

web access, 

storage-file 

share, 

directory 

UCC, web 

browsing, 

web access, 

storage-file 

share, 

directory 

email, chat, 

web 

browsing, 

web access, 

storage-file 

share, 

directory 

Email, chat, 

web 

browsing, 

web access, 

directory 

email, web 

browsing, 

web access, 

directory 





Supported 

Operational 

Task 

Specific 

Missions, 

Functions 

or 

Activities 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation, 

Day-to-Day 

Business, 

consultation 


Involved 

Information 

Consuming 

Node 

13 NATO 

nation 

domains 

1-8 All ANWI 

NS 

connected 

users 

12 other 

NATO 

domains 

1-8 All ANWI 

NS 

connected 

users 

11 Business 

Infra 

Domains 

SMC 8-9 

Administrator 

, NPE 

Information 

Producing 

Node 

1-8 All ANWI 

NS 

connected 

users 

12 other 

NATO 

domains 

1-8 All ANWI 

NS 

connected 

users 

11 Business 

Infra 

Domains 

1-8 All ANWI 

NS 

connected 

users 

11 Business 

Infra domain 


Information 


Element 

Information Media Quality Type 

Data provided to Cross Well 

entities to be domain connected 

handled/integrate (IEG B) 

d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 




d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 




d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 




d in NATO 

RESTRICTED 

down to (NATO) 

UNCLASSIFIED 

processing 




d in 

SECRETdown to 

(NATO) 

UNCLASSIFIED 

processing 

Data generated by 

SMC/element 

managers on the 

Business Infra 

Cross 

domain 

Cross 

domain 

Cross 

domain 

Cross 

domain 

Cross 

domain 

Well 

connected 

Well 

connected 

Well 

connected 

Well 

connected 

Well 

connected 

message, 

portal, 


(chat), 

directory 

All UCC 

services, 

portal, 

directory 

All UCC 

services, 

portal, 

directory 

email, portal, 

directory, TV 


directory 

Xml file, 

email, SNMP, 

portal 

Capabilitie 

s 

Email, web 

browsing, 

web access, 

directory 

UCC, web 

browsing, 

web access, 

directory 

Email, chat, 

web 

browsing, 

web access, 

directory 

email, web 

browsing, 

web access, 

directory. 

Email, web 

browsing, 

web access, 

directory 

File, email, 

web 

browsing, 

web access 

SMC 

11 Business 

Infra domain 

8-9 

Administrator 

, NPE 

SMC info reported 

back to Business 

Domains 

Cross 

domain 

Well 

connected 

Email, xml file 

email 

Table 11.6: NS Infrastructure IER table 

11.7.2 ANWI Business Infrastructure IERs 

11.7.2-p1 In this section the operational information requirements for the Business 

Infrastructure is summarized in Table 11.7. This table identifies the nature of the 

information exchange requirement (function), the involved nodes and the required 

information exchange attributes. The table includes only the IER’s of which the endto-end 

user level is within the responsibility of ANWI. 





Supported 

Operational 

Task 

Specific 

Missions, 

Functions 

or 

Activities 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation 

Day-to-Day 

Business, 

consultation, 


Involved 

Information 

Consuming 

Node 

1-8 All ANWI 

NR 

connected 

users 

1-8 All ANWI 

NR 

connected 

users 

19-20 

NNTCN and 

7NNN 

1-8 All ANWI 

NR 

connected 

users 

12 Public 

Connected 

Domains 

1-8 All ANWI 

NR 

connected 

users 

12 other 

NATO WAN 

NR domains 

1-8 All ANWI 

NR 

connected 

users 

Information 

Producing 

Node 

1-8 All ANWI 

NR 

connected 

users 

19-20 

NNTCN and 

7NNN 

1-8 All ANWI 

NR 

connected 

users 

13 Public 

Connected 

domains 

1-8 All ANWI 

NR 

connected 

users 

12 other 

NATO WAN 

NR domains 

1-8 All ANWI 

NRconnected 

users 

11 NS infra 

domain 


Information 


Element 

Information Media Quality Type Capabilities 

Data provided to ANWI Well All UCC UCC, web 

entities to be access Connected services, browsing, 

handled/integrated 

portal, file, web access, 

in NATO 

voice, video, storage-file 

RESTRICTED down 

collaborations, share, 

to (NATO) 

directory directory 

UNCLASSIFIED 

processing 




in NATO 


to (NATO) 

UNCLASSIFIED 

processing 




in NATO 


to (NATO) 

UNCLASSIFIED 

processing 




atUNCLASSIFIED 

processing 




atUNCLASSIFIED 

processing 




in NATO 

RESTRICTEDdown 

to (NATO) 

UNCLASSIFIED 

processing 




in NATO 


to (NATO) 

UNCLASSIFIED 

processing 




in NATO 


to (NATO) 

UNCLASSIFIED 

processing 

Cross 

domain 

full 

ANWI 

access 

Cross 

domain 

full 

ANWI 

access 

Cross 

domain 

Cross 

domain 

Cross 

domain 

Cross 

domain 

Cross 

domain 

Well 

Connected 

Well 

Connected 

Well 

Connected 

Well 

Connected 

Well 

Connected 

Well 

Connected 

Well 

Connected 

All UCC 

services , 

portal, file, 

voice, video, 

collaborations, 

directory 

All UCC 

services, 

portal, file, 

voice, video, 

collaborations, 

directory 

UCC voice 

services 

,message, 

portal, 


(chat), 

directory, TV 

UCC voice 

services, 

message, 

portal, 


(chat), 

directory 

All UCC 

services, 

portal, 

directory 

All UCC 

services, 

portal, 

directory 


directory, 

UCC, web 

browsing, 

web access, 

storage-file 

share, 

directory 

UCC, web 

browsing, 

web access, 

storage-file 

share, 

directory 

UCC voice 

services, 

email, web 

browsing, 

web access, 

directory, 

IPTV 

Email, web 

browsing, 

web access, 

directory, 

UCC, web 

browsing, 

web access, 

directory 

UCCweb 

browsing, 

web access, 

directory 

email, web 

browsing, 

web access, 

directory 





Supported 

Operational 

Task 

Specific 

Missions, 

Functions 

or 

Activities 

Day-to-Day 

Business, 

consultation 

SMC 


Involved 

Information 

Consuming 

Node 

11 NS Infra 

Domain 

11 NS infra 

domain 

SMC 8-9 

Administrator, 

NPE 

Information 

Producing 

Node 

1-8 All ANWI 

NR 

connected 

users 

8-9 

Administrator, 

NPE 

11 NS infra 

domain 


Information 


Element 

Information Media Quality Type Capabilities 

Data provided to Cross Well email, portal, Email, web 

entities to be domain Connected directory browsing, 


web access, 

in NATO 

directory 


to (NATO) 

UNCLASSIFIED 

processing 

Data generated by 

SMC/element 

managers on the 

Business Infra 

(maximum NR level) 

SMC info reported 

back to Business 

Domains (maximum 

NR level) 

Cross 

domain 

Cross 

domain 

Well 

Connected 

Well 

connected 

Xml file, 

email, SNMP, 

portal 

Email, xml file 

File, email, 

web 

browsing, 

web access 

email 

Provision of 

info to public 

sources 

10, 14, 17 

Public users 

1-8 All ANWI 

NR 

connected 

users 

Extranet Portal, 

Public Portal, Email 

at Unclassified level 

Cross 

domain 

Well 

Connected 

email, portal 

email, web 

browsing, 

web access 

Reachback 

with non 

NATO 

owned 

devices 

Exchange of 

information 

with 

registered 

users (ERP) 

15, 16 Home 

worker and 

Internet café 

user 

18 registered 

public user 

1-8 All ANWI 

NR 

connected 

users 

1-8 All ANWI 

NR 

connected 

users 


Email at NATO 

Unclassified level 


email at 

Unclassified level 

Cross 

domain 

Cross 

domain 

Well 

connected 

Well 

connected 

Table 11.7: ANWI Business Infrastructure IER table 

Email, portal 

Email, portal 

Email, web 

browsing, 

web access 

Email, web 

browsing, 

web access 

11.8 Overarching Information Assurance Architecture Concept and 

Requirements 

11.8.1 ANWI IA Services Architecture 

11.8.1-p1 As mentioned in section 11.3.3.5, IA services integrate with all other C3 

services: 

A. Each C3 service has embedded some IA features (as part of the 

horizontal integration). These IA features provided by each ANWI service 

are addressed in the SOW and appropriate Annexes (F to I); 

B. IA services needed to integrate/manage/support the horizontal IA services 

and, if required, integrate into NATO wide IA services and IA services 

management (vertical integration). The (vertical) specific CoI IA services 

and applications are specified in Annex E appendix 2. 





Figure 11.6 IA services architecture 

11.8.2 Information Assurance Architecture Compliance Approach 

11.8.2.1 NNHQ Security Architecture Concept 

11.8.2.1-p1 The HQPO Security CONOPS (Ref. 1.1.1.7.4) states the “Need for 

INFOSEC Control and Management” (N.IA.05) - need to support security 

management mechanisms and procedures that will deter, prevent, detect, and 

recover from the impacts of incidents that affect the NNHQ’s security posture (i.e. 

confidentiality, integrity and availability of NATO classified information and supporting 

system services and resources). The identified business need is to manage the 





implemented security mechanisms in a holistic and fully integrated manner (as far as 

is practical, given the state of the art). 

11.8.2.1-p2 As stated in the HQPO Security CONOPS (Ref. 1.1.1.7.4), the 

solutions shall employ coherent and interoperable technical approaches to ensure 

that all security mechanisms are fully operational, yet are still „trusted‟. 

11.8.2.1-p3 This approach forms the basis for achieving a dynamically 

integrated Security Management Infrastructure (SMI) (Ref. 1.1.1.6.10). 

11.8.2.1-p4 Initially SMI will be based on currently deployed services and will 

comprise of NATO Computer Incident Response Capability (NCIRC), the existing 

NATO IP, ISDN and other NATO cryptographic system management consoles, the 

enterprise systems management consoles operated by NCIA and other system 

management controls operated either directly by NATO or under NATO supervision. 

The Contractor should built/integrate ANWI management infrastructure into existing 

(at the implementation time) SMI. 

11.8.2.1-p5 Given the fact that the SMI concept is not worked out to the full level 

of detail an approach has been selected for the (N)NHQ (see figure 11.7) that 

ensures full traceability of high level security requirements (IER/approved 

countermeasures) down to the implementation level. For this approach 49 Security 

Mechanisms (SM) have been identified for implementation. These Security 

Mechanisms are a bundling of the NSRAG security countermeasures that were 

resulting from an initial Security Risk Assessment. 

11.8.2.1-p6 The ANWI contractor shall execute his own SRA and 

validate/enhance the Security Mechanisms as needed for ANWI. 

11.8.2.1-p7 The list of Current Developed Security Mechanisms is provided in 

section 11.8.2.2. The ANWI contractor shall those as a reference for creating the 

ANWI design and security accreditation work and as and when needed indicate 

where changes are needed given the SRA as to be undertaken by the ANWI 

contractor. 





Figure 11.7 Security flow 

11.8.2.2 NATO HQ ICT Security Mechanisms 

11.8.2.2-p1 

[1.1.1.8.5]. 

The NATO HQ ICT security mechanisms are provided in reference 

11.8.2.2-p2 The purpose of this section is to identify potential security 

mechanisms of NR2 or capabilities provided by the other projects/systems (like 

NCIRC FOC and PIA GW) which can be either re-used by ANWI or ANWI shall 

integrate with them. 

11.8.2.2-p3 The Contractor shall develop a design of ANWI security 

mechanisms on basis of requirements listed in the SOW. These mechanisms may 

correlate with NR2 security mechanisms, but most likely will be richer due to fact that 

ANWI is bringing new services (like UCC) and new services interfaces. 

11.8.2.2-p4 For the current HQ NR2 project, part of a comprehensive IA 

management approach, implementation of 49 security mechanisms are considered of 

which various of those mechanisms will be implemented during the NR2 timeframe. 

Table11.6, lists those security mechanisms, marks whether there is linkage to ANWI 

IA service and indicates the transition/migration requirements. 

11.8.2.2-p5 Column “Transition/migration/future management” indicated 

potential possibility for transition pending earlier assessment or integration with the 





other systems or central management capabilities managed by NCIA or NCIRC. 

Criteria for security mechanism migration shall include, but won’t be limited to: 

A. Software is under warranty, 

B. Software is still supported but near end-of-life ( -> no migration), 

C. Cost of migration, 

D. Easy integration in new environment; 

E. Fading/ emerging technology. 

Note: according to migration requirements listed in section 6.14, no hardware will be 

migrated. 





SM 

ID 

SM 

01 

SM 

02 

SM 

03 

Security 

Mechanisms 

Malware 

Protection for 

Server (File, 

Application, 

Print, 

Database) 

Malware 


Client 

(Desktop, 

Laptop) 

Malware 


Personal 

Digital 

Assistant 

(PDA). E.g. 

Blackberry 

Mapping to 

ANWI 

service 

Processing 

Services; 

Crossdomain 

services 

Client 

Provisioning 

Service 

Client 

Provisioning 

Services 

Current 

product 

NS, NR: 

McAfee Total 

Protection 

NR: McAfee 

for MOSS 

(SharePoint 

only) 

NS, NR: 

McAfee Total 

Protection 

NR: Message 

Labs; McAfee 

Mobile 

Security 

Current 

situation 

NS: Partially 

Implemented 

since not 

100% 

coverage, not 

redundant 

NR: partially 

implemented 

(databases 

not covered) 

NS, NR: fully 

implemented 

NS: N/A 

NR: partially 

done 

Current 

management 

NS, NR: Local 

management 

from ePO – 

no integration 

with 

NIATC/NCIRC 

NS, NR: As 

above 

NS: N/A 

NR: local 

management 

Security 

Risk level 

NS, NR: 

Medium 

(NR: print 

server – 

low, DB – 

high) 

NS: 

Medium 

NR: High 

NS: Low 

NR: 

Medium 

Expected 

NR2 end 

state 

NS, NR: Fully 

implemented 

NS, NR: Fully 

implemented 

NS: N/A 

NR: partially 

implemented 

Transition/ 

migration / future 

management 

Migration possible 

– local 

management (from 

ePO) integrated 

with NIATC (i.a. to 

download 

updates); 

See SM01 

Potential reuse/integration 

with ANWI – local 

management 





SM 

ID 

SM 

04 

SM 

05 

SM 

06 

Security 

Mechanisms 

Malware 


Email server 

- 

SMTP/AV/Spa 

m 

Malware 


Web server 

Messaging 

Content 

Filtering 

(MCF) 

- SMTP Relay 

Mapping to 

ANWI 

service 

Processing 

Services; 

Crossdomain 

services; 

UCC 

Services 

Crossdomain 

module 

Crossdomain 

services 

Integration 

with PIA GW 

(10.6.6.2) 

Current 

product 

NS: Trend 

Micro on MS 

Exchange 

NR: Message 

Labs, 

Trendmicro 

NS, NR: 

McAfee Total 

Protection 

NS: 

Trendmicro 

(offline 

scanning) 

NR: 

Mimesweepe 

r 

+Trendmicro( 

offline only) 

on NR; 

Current 

situation 

Fully 

implemented 

Note: 

MessageLabs 

do not provide 

adequate 

logging 

Fully 

implemented 

NS: Partially 

Implemented 

because of 

7NNN 

improvement 

is required, 

especially to 

avoid human 

errors 

NR: partially 

implemented 

(not 

redundant) 

Current 

management 

NS: local 

management; 

separated 

from ePO 

See SM 01 

Local 

management 

Security 

Risk level 

NS: Low 

NR: High 

NS: Low 

NR: 

medium 

NS: High 

NR: 

Medium 

Expected 

NR2 end 

state 

NS, NR: Fully 

implemented 

NS, NR: Fully 

implemented 

NS: partially 

implemented 

NR: partially 

implemented 

Transition/ 


management 

Migration possible 

– similar as SM01 

See SM 01 

NR: can be 

covered by PIA 

GW 





SM 

ID 

SM 

07 

SM 

08 

SM 

09 

Security 

Mechanisms 

Web Content 

Filtering 

(WCF) 

HTTP AV 

Proxy 

FTP AV Proxy 

Mapping to 

ANWI 

service 

Crossdomain 

services 

Integration 

with PIA GW 

(10.6.6.2) 

Crossdomain 

services 

Integration 

with PIA GW 

(10.6.6.2) 

Crossdomain 

services 

Integration 

with PIA GW 

(10.6.6.2) 

Current 

product 

NR: Bluecoat 

proxy 

(reverse 

proxy – see 

SM 20) 

NS: N/A 

NR: 

Symantec, 

MessageLab 

s security 

cloud; 

Kaspersky on 

BlueCoat 

proxy 

NS: N/A 

NR: Bluecoat 

proxy 

Current 

situation 

NS: not yet 

implemented, 

only Reverse 

Proxy needed 

NR: 

implemented 

(not all 

features 

enabled) 

NS: N/A 

NR: 

implemented 

NS: N/A 

NR: partially 

implemented 

(reverse proxy 

not covered) 

Current 

management 

NR: Local 

management 

NS: N/A 

NR: local 

NS: N/A 

NR: local 

Security 

Risk level 

Medium 

NS: Low 

NR: 

Medium 

NS: Low 

NR: 

Medium 

Expected 

NR2 end 

state 

NS, NR: 

Partially 

implemented 

(NS: reverse 

proxy only) 

NS: N/A 

NR: fully 

implemented 

NS: not 

implemented 

NR: partially 

covered 

Transition/ 


management 

NR: can be 


GW 

NS: N/A 

NR: can be 


GW 

NR: can be 


GW 





SM 

ID 

SM 

10 

SM 

11 

SM 

12 

Security 

Mechanisms 

Integrity 

Checker 

SSL VPN or 

SSL/TLS VPN 

Strong 

Authentication 

also called 

One Time 

Password 

(OTP or 

Medium 


) or Two 

Factors 


(T-FA) 

Mapping to 

ANWI 

service 

Network 

infrastructure 

services 

(Endpoint 

compliance) 

Integration 

with PIA GW 

(10.6.6.2) 

Crossdomain 

services; 

Integration 

with PIA GW 

(10.6.6.2) 

Client 

provisioning 

(two factor 

authenticatio 

n using NPKI) 

Current 

product 

NS, NR: 

Tripwire from 

Red Hat 

(WCM) 

NR: 

Symantec 

Altiris (on 

clients only) 

NS: N/A 

NR: Juniper 

SA4520, 

Cisco ASA 

5520 

NS: RSA for 

WCM 

solution 

administratio 

n 

NR: RSA 

SecureID (for 

WCM and 

NITV 

administratio 

n) 

NU: OTP 

Current 

situation 

Not yet 

implemented, 

essential for 

servers 

accessible for 

public 

NS: N/A” 

NR: 

implemented 

NS: Not yet 

implemented 

NR: 

implemented 

for privileged 

users only 

Current 

management 

NS, NR: N/A 

NS: N/A 

NR: local 

NS: N/A 

NR: local 

Security 

Risk level 

NS, NR: 

Medium 

NS: Low 

NR: High 

NS, NR: 

High 

Expected 

NR2 end 

state 

NS, NR: 

partially 

implemented 

NS: N/A 

NR:fully 

implemented 

NS, NR: 

partially 

implemented 

(implemented 

at least for 

privileged 

accounts) 

Transition/ 


management 

NS: N/A 

NR: can be 

provided by PIA 

GW 

NS, NR: no 

transition (ANWI 

will provide T-FA 

based on smart 

cards and NPKI 

certificates) 





SM 

ID 

SM 

13 

SM 

14 

Security 

Mechanisms 

Enterprise 

Single Sign- 

On (ESSO) 

Firewall (FW) 

for Outer 

Perimeter/ 

Border 

Protection 

Mapping to 

ANWI 

service 

Partially 

covered by 

Network 

Infrastructure 

Services 

(Directory 

services) 

Crossdomain 

services; 

GW3 – 

Integration 

with PIA GW 

(10.6.6.2) or 

re-using PIA 

GW services 

Current 

product 

NS, NR: 

CheckPoint 

Current 

situation 

NS: Partially 

implemented 

(e.g. Active 

Directory) 

NR: as above 

NS: Fully 

Implemented 

but HW 

replacement 

required 

NR: fully 

implemented 

Current 

management 

NS: local 

NR: as above 

NS, NR: local 

management 

Security 

Risk level 

NS: low 

NR: 

medium 

NS, NR: 

medium 

Expected 

NR2 end 

state 

NS, NR: 

partially 

implemented 

NS, NR: fully 

implemented 

Transition/ 


management 

Integration with 

SF/SD to be 

discussed (impact 

on business 

application to be 

analysed – 

currently all apart 

from FINS (for 

AMS only) are 

locally managed) 

NS: Checkpoint – 

can be centrally 

managed by NCIA 

NR: can be 


GW 

FW log monitoring 

to be integrated 

with NCIRC (note: 

FW management 

by NCIA -SMD is 

integrated with 

NCIRC – see 

Annex E, section 

“13.2.1.3.1 Firewall 

management” for 

details) 





SM 

ID 

SM 

15 

Security 

Mechanisms 

Firewall (FW) 

for Inner 

Perimeter 

Mapping to 

ANWI 

service 

Crossdomain 

services; 

Integration 

with PIA GW 

(10.6.6.2) 

Current 

product 

NS: N/A 

NR: Juniper 

Current 

situation 

NS: N/A 

NR: fully 

implemented 

Current 

management 

NS: N/A 

Security 

Risk level 

NS: Low 

NR: High 

Expected 

NR2 end 

state 

NS: N/A 

NR: fully 

implemented 

Transition/ 


management 

NS: N/A 

NR: Can have 

interface with PIA, 

potentially centrally 

managed 

FW log monitoring 

to be integrated 

with NCIRC (note: 

FW management 

by NCIA -SMD is 

integrated with 

NCIRC – see 

Annex E, section 

“13.2.1.3.1 Firewall 

management” for 

details) 





SM 

ID 

SM 

16 

SM 

17 

Security 

Mechanisms 

Intrusion 

Detection and 

Prevention 

System 

(IDS/IPS) 

Network 

Access 

Control (NAC) 

/ Network 

Access 

Protection 

(NAP) and 

Network 

Access 

Quarantine 

(NAQ) 

Mapping to 

ANWI 

service 

Processing 

Services 

(PR060-061) 

– host-based 

IDS; 

Crossdomain 

services; 

Integration 

with PIA GW 

(10.6.6.2); 

Client 

Provisioning 

Service (H- 

IDS) 

Network 


Services – 

Network 

Access 

Control 

(14.5.3.8) 

Integration 

with PIA GW 

(10.6.6.2) 

Current 

product 

NS: Internet 

Security 

Systems 

(ISS); 

McAfee 

NR: ISS, 

McAfee, 

Juniper 

N/A 

Current 

situation 

NS: Partially 

implemented 

NR: fully 

implemented 

NS, NR: not 

yet 

implemented 

Current 

management 

NS, NR: local 

management 

N/A 


Security 

Risk level 

NS: Low 

NR: 

Medium 

NS, NR: 

high 

Expected 

NR2 end 

state 

NS: partially 

implemented 

NR: fully 

implemented 

NS: partially 

implemented 

NR: partially 

implemented 

Transition/ 


management 

N-ID/PS 

management can 

be centralized; 

H-IDS – local 

management due 

to server specific 

policies; 

Integration with 

NCIRC necessary 

Note: certain 

sensors may be 

provided by 

NCIRC FOC 

Assertion 

(13.2.2.6) – IDS (at 

least N-ID/PS) are 

managed by 

NCIRC 

NR: certain 

mechanisms can 

be covered by PIA 

(e.g. NAQ) 




SM 

ID 

SM 

18 

SM 

19 

SM 

20 

Security 

Mechanisms 

IP Filtering 

Network 

Address 

Translation 

(NAT) 

Application 

Firewall 

Mapping to 

ANWI 

service 

Crossdomain 

services - 

Integration 

with PIA GW 

(10.6.6.2) 

Crossdomain 

Services - 

Integration 

with PIA GW 

(10.6.6.2) 

Crossdomain 

Services 

Integration 

with PIA GW 

(10.6.6) 

Current 

product 

NS: N/A 

NR: Juniper, 

CheckPoint 

NS: N/A 

NR: Juniper, 

Checkpoint 

NS: N/A 

NR: 

Barracuda 

Current 

situation 

NS: N/A 

NR: fully 

implemented 

(on routers 

and FWs) 

NS: N/A 

NR: Fully 

implemented 

(in mixed 

mode - on 

router and 

balancer – 

FWs) 

NS: N/A 

NR: partially 

implemented 

(further 

configuration 

required) 

Current 

management 

NS: N/A 

NR: local 

management 

NR: local 

management 

NR: local 

Security 

Risk level 

NS: Low 

NR: 

medium 

NS: Low 

NR: 

Medium 

NS: Low 

NR: High 

Expected 

NR2 end 

state 

NS: N/A 

NR: fully 

implemented 

NS: N/A 

NR: Fully 

implemented 

NS: N/A 

NR: full 

implementati 

on 

Transition/ 


management 

NS: N/A 

NR: can be 


GW 

Assertion: firewalls 

(apart from PIA) 

will be managed 

by NCIA (13.2.2.6) 

NS: N/A 

NR: can be 


GW 

NR: can be 


GW 





SM 

ID 

SM 

21 

SM 

22 

SM 

23 

Security 

Mechanisms 

System and 

Security 

Logging & 

Auditing 

Router and 

Switch 

Voice over 

Internet 

Protocol 

(VoIP) 

protection 

Mapping to 

ANWI 

service 

SMC; Crossdomain 

services; 

integration 

with NCIRC 

Network 


services 

UCC 

Services – 

Voice Service 

Component; 

Client 

Provisioning 

Current 

product 

Current 

situation 

Arcsight NS, NR : 

Partially 

Implemented 

as not all logs 

are captured 

No event 

correlation 

implemented; 

NS and NR – 

events 

(subset) send 

to NCIRC for 

correlation 

NS, NR: 

Juniper, 

Cisco 

NS: N/A 

NR: 

CheckPoint 

(built-in VoIP 

Application 

Intelligence) 

NS, NR : Fully 

implemented 

NS: N/A 

NR: limited to 

public security 

zone 

Current 

management 

NS, NR: Local 

management 

NS: N/A 

NR: local 

management 

Security 

Risk level 

NS, NR: 

High 

NS: Low 

NR: 

Medium 

NS: Low 

NR: High 

Expected 

NR2 end 

state 

NS: Partially 

implemented 

NS, NR: fully 

implemented 

NS: N/A 

Transition/ 


management 

Can be migrated; 

integration with 

NCIRC to be 

improved. 

Note: NCRIC FOC 

project will deploy 

log aggregation at 

NATO HQ and is 

part of ANWI PFE, 

see Annex B 

NS: N/A 





SM 

ID 

SM 

24 

SM 

25 

SM 

26 

Security 

Mechanisms 

Wireless 

Network 

Protection 

Storage 

Compartment 

ed Security 

Mode (SCSM) 

Data Backup, 

Replication 

and Recovery 

(DBRR) 

Mapping to 

ANWI 

service 

Part of LAN 

services 

(14.6.5) 

Storage 

Services 

Partially 

covered by: 

- SMC 

(13.1.6.2) 

- Infrastruct 

ure 

services 

Current 

product 

NS, NR: N/A 

Public: Cisco 

5508 

Wireless LAN 

Controller; 

Access 

Points 3502E 

NS: N/A 

Current 

situation 

NS, NR: N/A 

Public – 

limited to 

public security 

zone; planned 

REACH 

deployment in 

3 blocks of 

main building 

(NR2 


will be used) 

NS: N/A (not 

required) 

NR: the same 

SAN used for 

NR and NU 

NS, NR: 

partially 

implemented 

(upgrade/ 

replacement 

needed) 

Current 

management 

Local 

management 

NS: N/A 

NR: local 

management 

NS, NR: local 

management 

Security 

Risk level 

NS: Low 

NR: high 

NS: Low 

NR: high 

NS: low 

NR: 

medium 

Expected 

NR2 end 

state 

NS: N/A 

NR: partially 

implemented 

NS: N/A 

NR: fully 

implemented 

NS: fully 

implemented 

NR: partially 

implemented 

Transition/ 


management 





SM 

ID 

SM 

27 

SM 

28 

SM 

29 

Security 

Mechanisms 

Network 

Management 

System 

(NMS) / 

Systems 

Management 

System (SMS) 

IT Forensic 

Encryption- 

Decryption 

/Cryptography 

Mapping to 

ANWI 

service 

Service 

Management 

and Control – 

partial 

coverage 

(SM# 

requirements) 

Integration 

with NCIRC 

Client 

Provisioning 

Service (Hard 

disk 

encryption) 

Current 

product 

NS, NR: N/A 

Current 

situation 

NS, NR: not 

yet 

implemented 

Encase NS, NR : 

partially 

implemented 

(access 

limited to 

NOS) 

NS: 

Flagstones 

hard-drive 

NR: N/A 

NS: fully 

implemented 

USB 

encryption – 

to be 

addressed 

NR: not 

implemented 

Current 

management 

NS, NR : N/A 

NS: Local 

management 

by COM 

branch 

Security 

Risk level 

NS: 

Medium 

NR: High 

NS: Low 

NR: 

medium 

NS, NR: 

High 

Expected 

NR2 end 

state 

Implemented: 

(NS - work 

package 

planned for 

2012) 

NS, NR: 

partially 

implemented 

NS: Fully 

implemented 

NR: partially 

implemented 

Transition/ 


management 

Migration to be 

considered; 

Tools will be 

provided by 

NCIRC FOC 

Assertion 

(13.2.2.6) – online 

computer forensic 

and full packet 

capture (FPC) to 

be managed by 

NCIRC 





SM 

ID 

SM 

30 

SM 

31 

SM 

32 

Security 

Mechanisms 

Public Key 


(PKI) 

Security 

Zones 

Policies, 

directives and 

procedures 

(PDP) 

Mapping to 

ANWI 

service 

Support to 

establish RA; 

Client 

provisioning 

(PKI client, 

token and 

token reader) 

All networks 

provided by 

ANWI 

N/A – out of 

scope 

ANWI will 

provide 

solutions 

compliant 

with NATO 

policies 

Current 

product 

NS, NR: 

SafeNet 

Aladdin 

N/A 

Current 

situation 

NS, NR: 

Partially 

implemented 

(Registration 

Authority on 

NS and NR) 

NS: Partially 

implemented 

NR: fully 

implemented 

NS, NR: 

Partially 

implemented 

– update 

needed 

Current 

management 

RA locally 

managed; 

most of the 

network 

devices 

managed with 

NATO 

certificate 

Security 

Risk level 

NS: 

Medium 

NR: High 

NS: High 

NR: 

Medium 

NR: 

medium 

Expected 

NR2 end 

state 

NS, NR: 

partially 

implemented 

NS: partially 

implemented 

NR: fully 

implemented 

NS, NR: 

partially 

implemented 

Transition/ 


management 

N/A 

ANWI 

implementation 

shall be compliant 

with security 

policies valid at the 

time of ANWI 

implementation; 

certain procedures 

may require 

update – out of 

scope of ANWI 





SM 

ID 

SM 

33 

SM 

34 

SM 

35 

SM 

36 

Security 

Mechanisms 

Load 

Balancing / 

Failover 

(LB/FO) 

Classification 

Level / Data 

Labelling 

Data 

Loss/Leak 

Prevention 

(DLP) 

Vulnerability 

Scanning 

Mapping to 

ANWI 

service 

Processing 

Services 

(LB/FO 

between 

server 

rooms); 

Integration 

with PIA GW 

(10.6.6.2) 

Out of scope 

(label 

checking 

CDM) 

Client 

Provisioning 

Service 

(Removable 

Storage 

Management 

System) 

Integration 

only (tools to 

be provided 

by NCIRC) 

Current 

product 

NS, NR: 

McAfee Total 


Data 

Current 

situation 

NS: fully 

implemented 

(dual NS 

connectivity – 

fail-over only; 

no load 

balancing) 

NR: fully 

implemented 

NS, NR: 

partially 

implemented 

NS, NR: 

Partially 

implemented 

for USB 

control 

Partially 

implemented - 

periodical 

tests 

performed by 

other entities 

(e.g. SECAN, 

NIATC) 

Current 

management 

Local 

management 

Local 

management 

N/A 

Security 

Risk level 

NS: Low 

NR: high 

NS, NR: 

High 

NS, NR: 

High 

NS, NR: 

High 

Expected 

NR2 end 

state 

NS, NR: fully 

implemented 

NS, NR: 

partially 

implemented 

NS, NR: 

partially 

implemented 

NS, NR: 

partially 

implemented 

Transition/ 


management 

Connection to 

Internet – can be 


GW 

On-line VA will be 

deployedby 

NCRIC FOC 



SM 

ID 

SM 

37 

SM 

38 

SM 

39 

SM 

40 

SM 

41 

Security 

Mechanisms 

Group Policy 

Object (GPO) 

Quality of 

Service (QoS) 

Preproduction 

Environment 

/Test 

Environment 

Configuration 

Management 

Database 

(CMDB) 

Mapping to 

ANWI 

service 

Possible 

integration 

with AD AIS 

SF/SD 

(10.5.6) 

Partially 

covered by 

LAN services 

Integration 

and test 

services 

SMC – 

Configuration 

Management 

Database 

Current 

product 

NS, NR: MS 

AD 

NS, NR: Infra 

Helpdesk 

(EMC); Altiris 

(Symantec) 


Current 

situation 

Partially 

Implemented 

because not 

100% 

coverage such 

as Mac, UNIX, 

etc 

NS, NR: 

partially 

implemented 

NS : not 

implemented 

NR: partially 

implemented 

(redesign in 

accordance 

with NR2 TA 

needed) 

Partiallyimple 

mented 

CAPTCHA Out of scope NS: N/A (not 

required) 

NR: partially 

implemented 

Current 

management 

Local 

management 

Local 

Security 

Risk level 

NS, NR: 

High 

NS, NR: 

Medium 

NS : 

Medium 

NR : high 

Local NS, NR : 

High 

NS: N/A 

NS, NR: 

low 


Expected 

NR2 end 

state 

NS, NR: 

partially 

implemented 

NS, NR: 

partially 

implemented 

NS, NR : 

fullyimplemen 

ted 

NS, NR : 

fullyimplemen 

ted 

NS: N/A 

NR: partially 

implemented 

Transition/ 


management 

Possible 

integration with 

SF/SD – see SM 

13 





SM 

ID 

SM 

42 

SM 

43 

SM 

44 

Security 

Mechanisms 

Identity & 

Access 

Management 

(IAM) 

Management 

of the Security 

Mechanisms 

Network Time 

Protocol 

(NTP) 

Mapping to 

ANWI 

service 

Part of SMC 

(SM017-22) – 

partially 

covered; 

Where 

possible 

centralized 

capabilities at 

NCIA and 

NCIRC to be 

reused 

NTP – 

integration, 

time server 

for NR and 

EAPC 

Current 

product 

Current 

situation 

NS: partially 

implemented 

NR: partially 

implemented 

(redesign 

needed) 

NS: Not yet 

implemented 

NR: partially 

implemented 

(needs to be 

redesigned) 

NS, NR: Fully 

implemented; 

NATO-wide 

provided 

Current 

management 

Local 

management 

N/A 

Local 

management 

– 

synchronizatio 

n with time 

source at 

NCIA 

Security 

Risk level 

NR: high 

NS, NR: 

High 

Ns, NR: 

High 

Expected 

NR2 end 

state 

NS, NR: 

partially 

implemented 

NS, NR: 

partially 

implemented 

NS, NR: Fully 

implemented 

Transition/ 


management 

Application 

authentication – 

out of scope of 

ANWI, re-used 

from NR2 

synchronization 

with time source at 

NCIA 





SM 

ID 

SM 

45 

SM 

46 

SM 

47 

Security 

Mechanisms 

Logical Unit 

Number 

(LUN) 

Management 

for Storage 

Area Network 

(SAN) 

Data Activity 

Monitoring 

(DAM) using 

the Data 

Scramble 

mechanism 

Data Activity 

Monitoring 

(DAM) and 

File Server 

Activity 

Monitoring 

(FSAM) using 

the Data 

Safeguarding 

mechanism 

Mapping to 

ANWI 

service 

Out of scope 

Out of scope 

Out of scope 

Current 

product 

NS, NR: HP 

EVA 8100 

family 

Current 

situation 

NS: Partially 

Implemented 

because 

configuration 

of LUNs may 

need some 

changes 

NR: fully 

implemented 

NS, NR: Not 

yet 

implemented 

NS, NR: Not 

yet 

implemented 

Current 

management 

Local 

management 

Security 

Risk level 

NS, NR: 

High 

NS, NR: 

Low 

NS, NR: 

High 

Expected 

NR2 end 

state 

NS, NR: fully 

implemented 

NR: will be 

implemented 

if required by 

business 

NS: partially 

implemented 

Transition/ 


management 





SM 

ID 

SM 

48 

SM 

49 

Security 

Mechanisms 

Password 

Management 

Identity & 


, Access 

Control 

(IAAC) 

Mapping to 

ANWI 

service 

Tools 

implemented 

in OS – no 

extra tools 

will be 

provided by 

ANWI 

Partially 

covered: 


Services 

(based on 

MS Active 

Directory/NP 

KI). 

Current 

product 

NS, NR: 

Password 

Policy 

Enforcer 

(PPE); 

NS: Thycotic 

SECRET 

Server (for 

password 

protection) 

Current 

situation 

NS: Partially 

Implemented - 

covers only 

Active 

Directory 

NS, NR: Not 

yet 

implemented 

Current 

management 

NS: Local 

management 

Security 

Risk level 

NS, NR: 

High 

NS: High 

NR: 

medium 

Expected 

NR2 end 

state 

NS: partially 

implemented 

NS: partially 

implemented 

Transition/ 


management

nnhq - anwi

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?