· Web viewAbbreviations6. Glossary8. 1.Introduction9. 1.1.Scope of the Document9. 1.2.Structure of the Document9. 1.3.The Preparatory Commission and the Role of the Global Communications

Annex C

Terms of Reference

Global Communications Infrastructure III

Annex C 12/02/2016

Terms of Reference- Annex CGlobal Communications Infrastructure

Table of Contents

Abbreviations.......................................................................................................................................... 6Glossary................................................................................................................................................. 81. Introduction........................................................................................................................................ 9

1.1. Scope of the Document...........................................................................................................91.2. Structure of the Document.......................................................................................................91.3. The Preparatory Commission and the Role of the Global Communications

Infrastructure Network...........................................................................................................101.3.1. The Preparatory Commission for the Comprehensive Nuclear-Test-Ban Treaty

Organization.............................................................................................................101.3.2. Global Communications Infrastructure......................................................................101.3.3. International Data Centre..........................................................................................121.3.4. National Data Centre................................................................................................121.3.5. International Monitoring System Facilities.................................................................131.3.6. Communications Nodes............................................................................................141.3.7. Other Facilities..........................................................................................................151.3.8. External Networks.....................................................................................................15

1.3.8.1. Independent Subnetworks.........................................................................161.3.8.2. Other Networks..........................................................................................16

2. Statement of Work........................................................................................................................... 172.1. Scope of Section................................................................................................................... 172.2. Documentation...................................................................................................................... 172.3. Project and Services Schedules............................................................................................19

2.3.1. Initial Project Planning Phase...................................................................................202.3.2. Project Design and Technical Review Phase...........................................................212.3.3. Provisioning, Integration, Validation and Verification Phase.....................................212.3.4. Network Implementation and Migration Phase.........................................................222.3.5. Service Operation and Management Phase.............................................................222.3.6. Training Courses......................................................................................................24

2.4. Key Personnel.......................................................................................................................243. Specification of Requirements.........................................................................................................27

3.1. Scope of Section................................................................................................................... 273.2. Project Planning....................................................................................................................27

3.2.1. Project Management Plan.........................................................................................283.2.2. Quality Assurance Plan.............................................................................................283.2.3. Risk Management Plan.............................................................................................303.2.4. Communication Plan.................................................................................................303.2.5. Project Implementation Plan.....................................................................................313.2.6. Business Continuity Planning and Disaster Recovery..............................................313.2.7. Kick-Off Meeting.......................................................................................................323.2.8. Project Review Meeting............................................................................................333.2.9. Project Approval Meeting..........................................................................................33

3.3. Design and Technical Review Phase....................................................................................333.3.1. High Level Design.....................................................................................................353.3.2. Detailed Design........................................................................................................353.3.3. Proof of Concept.......................................................................................................363.3.4. Design Start Meeting................................................................................................373.3.5. Design Checkpoint Meeting......................................................................................383.3.6. Design End Meeting..................................................................................................38

3.4. Terrestrial Core Network Infrastructure.................................................................................383.4.1. Terrestrial Core Network Functionality......................................................................393.4.2. Terrestrial Core Network Specifications....................................................................393.4.3. Terrestrial Core Network Capacity and Performance................................................393.4.4. Terrestrial Core Network Redundancy and Resiliency..............................................403.4.5. Terrestrial Core Network Quality of Service..............................................................413.4.6. Terrestrial Core Network Interface with the Commission..........................................42

Page 2 of 116 12/02/016


3.4.6.1. Terrestrial Core Network Interface with the International Data Centre.......423.4.6.2. Terrestrial Core Network Interface with Remote Sites...............................423.4.6.3. Terrestrial Core Network Interface with the Backup International

Data Centre...............................................................................................433.4.7. Terrestrial Core Network Configuration Management...............................................433.4.8. Terrestrial Core Network Documentation..................................................................44

3.5. Teleport Infrastructure...........................................................................................................443.5.1. Antenna and RF Subsystems...................................................................................453.5.2. Hub and Teleport Local Network Infrastructure........................................................453.5.3. Terrestrial Core Network and Backup Internet Connectivity.....................................463.5.4. Teleport Supporting Infrastructure and Personnel....................................................463.5.5. Space Segment........................................................................................................47

3.6. Remote Sites.........................................................................................................................473.6.1. Licensing and Regulatory Compliance......................................................................473.6.2. Logistics and Strategic Deployment Stock................................................................493.6.3. Remote Station Redundancy and Resiliency............................................................503.6.4. Local Infrastructure and Environmental Conditions...................................................523.6.5. Satellite Outdoor Subsystem....................................................................................563.6.6. Routing and Remote Site Network............................................................................573.6.7. Capacity, Performance and Quality of Service.........................................................593.6.8. Remote Sites and ISNs Connected Directly to the Terrestrial Core Network............623.6.9. Transportable Stations..............................................................................................623.6.10. Monitoring Command and Control............................................................................643.6.11. Remote Site Network Documentation.......................................................................643.6.12. Security 65

3.7. Network Management System...............................................................................................653.7.1. Network Operations Centre Staffing.........................................................................653.7.2. Network Management System..................................................................................65

3.7.2.1. Performance Data......................................................................................673.7.2.2. Operational Status.....................................................................................683.7.2.3. High Availability Server..............................................................................683.7.2.4. Management Data Requirements..............................................................683.7.2.5. Integration of the Network Management System of the Contractor

with the Incident Tracking System of the Commission...............................703.8. Provisioning, Integration, Validation and Verification.............................................................70

3.8.1. Provisioning, Integration, Validation and Verification Plan........................................70Preliminary Provisioning, Integration, Validation and Verification Plan.....................70Final Provisioning, Integration, Validation and Verification Plan...............................70

3.8.2. Unit Verification Testing............................................................................................713.8.3. Subsystem Validation and Verification Testing.........................................................72

Terrestrial Core Network Infrastructure.....................................................................73Teleport Network Infrastructure................................................................................73Teleport Antenna and Radio Frequency...................................................................74Teleport Hub and Hub Network Monitoring System..................................................75International Data Centre Network (Provider Side)...................................................75Network Management System..................................................................................76

3.8.4. System Validation and Verification Testing...............................................................763.8.5. Documentation and Procedures for Operations and Maintenance...........................773.8.6. Provisioning, Integration, Validation and Verification Start Meeting..........................783.8.7. Provisioning, Integration, Validation and Verification Checkpoint Meeting................783.8.8. Provisioning, Integration, Validation and Verification End Meeting...........................79

3.9. Network Implementation and Migration.................................................................................793.9.1. Migration Perquisites................................................................................................803.9.2. Provisioning Plan......................................................................................................823.9.3. Coordination and Site Preparation............................................................................833.9.4. Site Installation, Migration, Verification and Validation..............................................843.9.5. Implementation Start Meeting...................................................................................863.9.6. Implementation Checkpoint Meetings.......................................................................86

Page 3 of 116 12/02/016


3.9.7. Implementation End Meeting....................................................................................873.10. Service Operation and Management.....................................................................................87

3.10.1. Event, Incident and Problem Management...............................................................883.10.2. Configuration and Change Management..................................................................903.10.3. Service Level Management......................................................................................923.10.4. Service Review Meetings..........................................................................................94

3.11. Service Review and Technology Refresh..............................................................................953.12. Training................................................................................................................................. 96

3.12.1. Satellite and Terrestrial Technology Seminars.........................................................963.12.2. Global Communications Infrastructure Overview and Stakeholders Workshop........973.12.3. On-Site Station Maintenance Training......................................................................973.12.4. Training Reports.......................................................................................................98

3.13. End of Service Phase............................................................................................................983.13.1. Start of Decommissioning Meeting.........................................................................1003.13.2. End of Service Meeting...........................................................................................100

3.14. Security............................................................................................................................... 1014. Service Level Agreement...............................................................................................................103

4.1. Scope of Section................................................................................................................. 1034.2. Performance Metrics and Key Performance Indicators.......................................................103

4.2.1. Service Availability..................................................................................................1034.2.2. Service Outages.....................................................................................................1044.2.3. Other Performance Metrics.....................................................................................106

4.2.3.1. Major Failures..........................................................................................1064.2.3.2. Critical Failures........................................................................................1074.2.3.3. Minor Failures..........................................................................................1074.2.3.4. Spare Equipment.....................................................................................1084.2.3.5. Spare Equipment at Remote Sites...........................................................1084.2.3.6. Spare Equipment at Teleports, the International Data Centre and in

the Terrestrial Core Network Infrastructure..............................................1084.2.3.7. Planned Service Outages........................................................................1084.2.3.8. Network Monitoring Data.........................................................................109

4.3. Remedial Actions.................................................................................................................1094.4. Performance Penalties........................................................................................................109

4.4.1. Cumulative Service Outages..................................................................................1094.4.2. Continuous Service Outages..................................................................................1104.4.3. Regional Service Outages......................................................................................1104.4.4. Failure to Replace Spare Equipment and Restore Redundancy.............................111

Spare Equipment for Remote Sites.........................................................................111Spare Equipment for Teleports, the Core Network Infrastructure and the IDC.......111

4.4.5. Network Monitoring Data........................................................................................1124.4.6. Calculation of the Unit of Penalty............................................................................112

4.5. Contract Non-Conformance and Chronic Breaches of Service Level Agreement................1135. Benchmarking................................................................................................................................ 114Attachment I: Technical Description of GCI II.....................................................................................115

Scope............................................................................................................................................ 115Technical Description.................................................................................................................... 115

Page 4 of 116 12/02/016


Tables

Table 1.1. Reference Documents........................................................................................................9Table 2.1. Document Life Cycle and Delivery...................................................................................17Table 2.2. Project Planning Meetings and Deliverables....................................................................21Table 2.3. Design and Technical Review Meetings and Deliverables...............................................21Table 2.4. Provisioning, Integration, Validation and Verification Meetings and Deliverables............22Table 2.5. Network Implementation and Migration Meetings and Deliverables.................................22Table 2.6. Service Operation and Management Phase Meetings and Deliverables..........................23Table 2.7. Schedule of Ongoing Activities During the Service Delivery Phase.................................24Table 2.8. Training Tasks and Deliverables......................................................................................24Table 4.1. End to End Service Performance Metrics.......................................................................104Table 4.2. Performance Penalties for Cumulative Service Outages................................................110Table 4.3. Performance Penalties for Continuous Service Outages...............................................110Table 4.4. Performance Penalties for Regional Service Outages...................................................111Table 4.5. Penalties for Delays in Replacing Spare Equipment at Remote Sites............................111Table 4.6. Penalties for Delays in Replacing Spare Equipment for Teleports, the Terrestrial

Core Network Infrastructure and the International Data Centre.....................................111Table 4.7. Performance Penalties for Network Monitoring Data......................................................112Table 4.8. Performance Penalties for Network Monitoring Access..................................................112Table 4.9. Unit of Penalty Dollar Value...........................................................................................112

Figures

Figure 1.1. Concept for the Global Communications Infrastructure Network......................................11Figure 1.2. Distribution of International Monitoring System Facilities.................................................14Figure 2.1. Project Implementation Schedule.....................................................................................20Figure 2.2. Post-Implementation Schedule........................................................................................20

Page 5 of 116 12/02/016


Abbreviations

AADR average anticipated data rateAC alternating currentACL access control listACU antenna control unitARP Address Resolution ProtocolBGP Border Gateway ProtocolBUC block up-converterCD continuous dataCIR committed information rateCMS configuration management systemCOS class of serviceCP checkpointCRC cyclic redundancy checkCTBT Comprehensive Nuclear-Test-Ban TreatyCTBTO Preparatory Commission for the Comprehensive Nuclear-Test-Ban Treaty OrganizationDC direct currentDOS Denial of ServiceDDOS Distributed Denial of ServiceDNS domain name serviceEDC effective start date of contractEBGP External Border Gateway ProtocolFTP File Transfer Protocol GCI I Global Communications Infrastructure from 1999 to 2008GCI II Global Communications Infrastructure from 2008 to 2018GCI III Global Communications Infrastructure from 2018 to 2028HTTP Hypertext Transfer ProtocolHTTPS Hypertext Transfer Protocol (secure)ICD implementation completion dateICMP Internet Control Message Protocol IDC International Data CentreIDS Intrusion Detection SystemIDU indoor unitIFL inter-facility linkIEEE Institute of Electrical and Electronics EngineersIMS International Monitoring SystemIP Internet ProtocolIPS Intrusion Prevention SystemIPv4 Internet Protocol version 4IPv6 Internet Protocol version 6ISN independent subnetworkIT information technologyITS incident tracking systemKPI key performance indicatorLACP Link Aggregation Control ProtocolLAN local area networkMPLS multiprotocol label switchingNAT network address translationNDC National Data CentreNMS network management systemNOC Network Operations CentreODU outdoor unitPDF Portable Document FormatPEP Protocol Enhancing ProxyPIP Project Implementation PlanPIR peak information rate

Page 6 of 116 12/02/016


PIVV provisioning, integration, validation and verificationPMTUD Path Maximum Transmission Unit DiscoveryPTS Provisional Technical SecretariatQOS quality of serviceRF radio frequencyRFC Request for CommentSLA Service Level AgreementSMTP Simple Mail Transport ProtocolSNMP Simple Network Management ProtocolSNR signal-to-noise ratioSOR specification of requirementsSOW statement of workSTD Internet StandardTCP Transport Control ProtocolTOR terms of referenceUDP User Datagram ProtocolUPS uninterruptible power supplyUTC Coordinated Universal TimeVLAN virtual local area networkVTP VLAN Trunking ProtocolVoIP Voice over Internet ProtocolVPLS virtual private LAN servicesVPN virtual private networkVSAT very small aperture terminalWAN wide area network

Page 7 of 116 12/02/016


Glossary

existing siteAn IMS facility, communications node, NDC or other entity directly connected to the GCI (included in the Site profile table document) that will be installed prior to the Start-of-Service Migration.

IMS facilityAn IMS station or radionuclide laboratory consisting of one or more central processing facilities and monitoring and/or sensing equipment that collects measurement data.

independent subnetwork A set of IMS facilities that are connected indirectly to the GCI via a communications node or an NDC. Measurement data from the IMS facilities pass through an independent subnetwork and are aggregated at a communications node or an NDC for transmission to the IDC.

National Data CentreA data centre that is operated and maintained by a State Signatory. Its functions may include forwarding data from IMS facilities to the IDC and/or receiving data and IDC products.

new siteA site that will not be installed prior to the Start-of-Service Migration. (it is included in the Site profile table document) Network Operations CentreThe collection of facilities and personnel provided by the GCI Contractor to implement systems and processes such as the network management system, a service desk and other service delivery and support functions.

response timeThe amount of time required for an IP packet to travel from the GCI‒IDC interface to the GCI‒site interface and back to the GCI‒IDC interface (i.e. round trip). The response time is measured in milliseconds.

service deskThe point of contact of the GCI Contractor for personnel of the Commission with respect to all operational matters.

site, remote siteThe location where a station, consisting of GCI equipment, is installed and operated.

stationA satellite or terrestrial equipment that is not part of the GCI network infrastructure.

Page 8 of 116 12/02/016


1. Introduction

1.1. Scope of the Document

These Terms of Reference (TOR) define the functional, technical and operational requirements for the third generation of the Global Communications Infrastructure (GCI III) and the tasks that the GCI Contractor shall perform in order to design, provide, install, migrate, commission, operate, maintain and decommission the GCI III network. These requirements and tasks are the basis for a set of services that the GCI Contractor shall be obliged to provide to the Preparatory Commission for the Comprehensive Nuclear-Test-Ban Treaty Organization (CTBTO).

This section describes the structure of the TOR document, lists applicable and reference documents and provides background information on the Commission, the GCI and the entities to which the GCI connects, including the International Monitoring System (IMS), the International Data Centre (IDC) and National Data Centres (NDCs).

1.2. Structure of the Document

This document includes the following components:

Introduction;

Statement of Work (SOW);

Specification of Requirements (SOR);

Service Level Agreement (SLA).

Benchmarking

Sections 2, 3 and 4 describe the required tasks, deliverables and documentation.

All of the primary requirements in the TOR are numbered and boxed. “M” is used to denote requirements that are mandatory. “D” is used to denote requirements that are desirable. “MD” is used to denote mandatory definitions supporting other requirements.

Table 1.1 lists all reference documents concerning these TOR.

Table 1.1. Reference Documents

Document Description Version

Attachment I Technical Description of Global Communications Infrastructure II

2.0

Page 9 of 116 12/02/016


1.3. The Preparatory Commission and the Role of the Global Communications Infrastructure Network

1.3.1. The Preparatory Commission for the Comprehensive Nuclear-Test-Ban Treaty Organization

The Preparatory Commission was founded in 1996 with the objective of establishing the verification regime of the Comprehensive Nuclear-Test-Ban Treaty (CTBT).1 Its two main tasks are to build up the verification regime in preparation for the Treaty’s entry into force and to promote universality of the Treaty.

The verification regime includes the IMS and the IDC. When complete, the IMS2 will consist of 337 monitoring stations and radionuclide laboratories located in 89 countries around the globe.3 Approximately 280 facilities are currently in place and sending monitoring data continuously via the GCI to the IDC at the headquarters of the Commission in Vienna, Austria.

The IDC4 is a central element of the Treaty’s verification mechanism. It collects, processes and analyses monitoring data originating from the IMS facilities. Raw and processed data, as well as IDC data products, are sent to the States Signatories to the Treaty continuously, periodically or on demand. On the basis of this information, the States Signatories are able to make judgements about evidence of possible nuclear explosions and verify compliance with the Treaty.

Further information on the Treaty is available on the CTBTO public web site: www.ctbto.org/the-organization.

1.3.2. Global Communications Infrastructure

The principal role of the GCI is the effective transport of data from IMS facilities to the IDC and from the IDC to all States Signatories. The IMS and the IDC depend on a reliable communications system for the timely and accurate transmission of data and data products. The GCI is designed to be cost effective and highly available.

The GCI is a communications system of truly global character. It is designed to transport data from the IMS facilities around the world in near real time to the IDC in Vienna, where the data is processed and analysed. The GCI also distributes raw data from IMS stations as well as IDC data products to the NDCs of States Signatories. Equally important, the GCI serves as the communications medium through which station operators remotely operate and maintain IMS monitoring facilities. In addition, the GCI is used to forward raw data from IMS stations to tsunami warning centres that have cooperative agreements with the Commission.

Figure 1.1 illustrates the GCI network concept. Solid lines represent dedicated GCI links of any technology (e.g. satellite or terrestrial). The dashed lines at the top of the figure represent Internet virtual private network (VPN) connections, while the dashed lines at the bottom represent individual links or entire networks that are outside the responsibility of the GCI Contractor. Communications nodes are NDCs or similar facilities where the GCI connects to another network. GCI hubs denote any communications facility or aggregation point within the GCI that is operated by the GCI Contractor. The remote sites can be IMS stations, NDCs or other facilities or communications nodes. These entities are described in subsequent sections. It should be noted that Figure 1.1 is a simplified illustration of the GCI network and shows separate connections between individual entities and the GCI. In reality, a combination of entities may connect with the GCI at one physical location.

1 http://www.ctbto.org/the-treaty/.2 http://www.ctbto.org/verification-regime/ .3 http://www.ctbto.org/fileadmin/content/reference/outreach/ims_mapfront.pdf.4 http://www.ctbto.org/verification-regime/the-international-data-centre/history-of-theinternational-data-centre/page-1-history-of-

idc/.

Page 10 of 116 12/02/016

http://www.ctbto.org/the-organization

http://www.ctbto.org/the-organization


Furthermore, although the figure shows a tree network topology rooted in the IDC, other topologies, such as a mesh network, are also possible.

Figure 1.1. Concept for the Global Communications Infrastructure Network

For the purposes of these TOR, the term “Global Communications Infrastructure” comprises all facilities, equipment and network connections provided by or through the GCI Contractor, which includes but is not limited to the following components:

Network Operations Centre (NOC), service management desk, help desk;

Network management system (NMS) and associated SLA computation tools;

Trouble ticket system;

Facilities for configuration management, backup and archiving;

Terrestrial gateways, points of presence and their network connections;

Terrestrial remote site equipment and circuits;

Equipment and terrestrial circuits at the IDC, including the connection to the Internet interface but excluding the Internet circuit;

Satellite teleports, hubs, gateways and network connections;

Satellite or very small aperture terminal (VSAT) remote site equipment;

Transportable remote site equipment;

Internet VPN remote site equipment and connection to the Internet interface, excluding the Internet circuit.

The first GCI network (GCI I) was implemented in 1999 and operational until 2008, when it was replaced by the second generation network (GCI II). GCI II is a hybrid terrestrial and satellite network

Page 11 of 116 12/02/016


infrastructure designed to provide a cost effective data communication service with high data availability. The technical description of GCI II is included as Attachment I.

GCI III will replace the GCI II network. GCI III is expected to leverage recent advances in telecommunications technology and further enhance the functionality and availability of the current GCI while remaining cost effective.

As was the case with GCI II, GCI III may be primarily a hub and spoke network (with some possible exceptions), with the IDC serving as its hub. A backup IDC will be implemented at a later stage and require similar connectivity to the IDC.

IMS facilities connect to the GCI directly or through an intermediary network such as an independent subnetwork.

1.3.3. International Data Centre

The IDC collects, processes and analyses monitoring data sent from IMS monitoring facilities via the GCI and transmits raw and processed data, as well as IDC data products, continuously to States Signatories through the GCI and the public Internet. The IDC operates several network management systems that monitor the status of the GCI, the connected IMS facilities and its own processing systems. The IDC is generally staffed during business hours (09:00-17:00 CET) from Monday through Friday, except for United Nations holidays.

All connections between the GCI and the IDC take place at the Computer Centre at the Provisional Technical Secretariat (PTS), which has controlled temperature and backup electrical power to ensure continuous operation. The IDC provides redundant high speed Internet connections for the Internet VPN circuits that are part of the GCI. The GCI connects to the IDC network at the PTS–GCI gateway routers, a pair of redundant gateway routers administered by the PTS. The GCI contractor network device directly connected to the gateway routers is referred to as the “GCI node at the IDC”. Through the GCI node at the IDC and the PTS–GCI gateway routers, Internet Protocol (IP) packets flow between the GCI and the IDC, or between the GCI and the public Internet (for VPN traffic). The IDC maintains a firewall between the PTS‒GCI gateway routers and between its internal network and the Internet.

In order to monitor and to regulate the traffic flows on this private network, all GCI traffic passes through both the GCI node at the IDC and the PTS–GCI gateway routers. The PTS–GCI gateway routers perform packet filtering to permit or block any traffic flows.

IDC hosts and network devices are assigned IP addresses in a /23 private IP address range and a /26 public IP address range. The IDC firewall blocks access to these ranges from the public Internet. Remote sites are assigned private IP addresses generally in Class C blocks or larger. GCI devices are assigned their own block of private IP addresses.

1.3.4. National Data Centre

An NDC is operated and maintained by a State Signatory. Its functions may include receiving data and products from the IDC and/or forwarding measurement data from IMS facilities to the IDC. The types of organizations that are designated as NDCs are government offices under the civilian or military branches or research institutions of the government or academic institutions. An NDC is independent from the Commission and has its own staff and processing facilities. In general, the Commission does not have a formal contractual relationship with an NDC. The Commission provides a GCI link to an NDC at no cost.

The majority of NDCs receive data and products, such that the IP traffic is predominantly towards the NDC. A few NDCs (to be described later) also forward measurement data to the IDC. The data rates for each NDC are different and depend on the subset of IMS data being received or forwarded. For some NDCs, the data rate increases with time as more data are requested. The Commission assigns

Page 12 of 116 12/02/016


each NDC remote site its own Class C (/24) or larger private IP address range. A few NDCs operate with individual legacy /28 private IP address ranges.

Since the NDC network is considered to be untrusted from the point of view of network and information technology (IT) security, the security of the GCI link is an important concern.

At this time, some States Signatories have not designated an NDC. Therefore the number of NDCs is expected to increase slowly as more States designate NDCs and request GCI connections. In addition, States occasionally change the designation of their NDC, or the physical location of an NDC may change. This usually requires relocation of the GCI link.

The Commission has developed an application for analysis of radionuclide data by which an NDC can download large data sets on demand (i.e. several gigabytes). Under the most stringent conditions this application requires a download time frame of a few hours and a download speed of approximately 1 megabit per second or more over an Internet VPN link. More realistically, these amounts of data are downloaded over a time frame of several days. It is estimated that between 15 and 30 NDCs could use this application, although there are no definite plans at this time.

1.3.5. International Monitoring System Facilities

IMS facilities search for, detect and provide evidence of possible nuclear explosions to States Signatories to verify compliance with the Treaty. The number and location of IMS facilities are fixed in the Treaty to provide uniform global coverage. At present, there are 321 monitoring stations and 16 radionuclide laboratories. Many IMS facilities are located in remote, hard to reach locations. They are often unstaffed, and a few stations are in areas where access is restricted or there is no commercial transportation. From time to time, it is necessary to rebuild or to move an IMS facility to a different physical location, requiring relocation of the GCI link. Figure 1.2 shows the distribution of IMS facilities. An online version is available at http://www.ctbto.org/verification-regime/building-theinternational-monitoring-system/1994-1996-reaching-critical-mass/. An interactive list of IMS facilities and their locations is available at http://www.ctbto.org/verification-regime/station-profiles/.

Seismic, hydroacoustic and infrasound monitoring stations detect transient signals created when energy is released in underground, underwater and/or atmospheric environments. The stations send digital waveforms or time series to the IDC that provide diagnostic information to detect, locate and characterize the energy source. Radionuclide monitoring stations use air samplers to collect and analyse atmospheric particulate matter deposited on collection filters and noble gases. Radionuclide laboratories assist radionuclide stations in identifying any radioactive substances collected at the stations. The analysis of the radionuclide content uniquely confirms a nuclear explosion.

For most facilities, the IMS data senders and the GCI remote site equipment are at the same physical location. However, there are cases where the IMS data sender is in a different location and connects to the GCI over another link that is part of the IMS facility (as opposed to the GCI). This link, which may comprise a terrestrial cable medium, a terrestrial radio medium and/or a satellite medium, constitutes a simple network, which entails IP routing and addressing considerations. In these cases GCI security is also a concern because the link is considered an untrusted network.

In principle, the data volume transmitted by an IMS facility is known. There are three traffic patterns:

Continuous transmission at a more or less steady data rate using a proprietary Transport Control Protocol (TCP/IP) application;

Periodic transmission of emails (SMTP);

On-demand transmission of emails.

In addition, Commission staff and other maintenance personnel may connect remotely to an IMS facility for interactive sessions, e.g., with ssh, Remote Desktop and similar protocols, or for batch file uploads and downloads, e.g., with FTP, scp and similar protocols.

Page 13 of 116 12/02/016

http://www.ctbto.org/verification-regime/station-profiles/

http://www.ctbto.org/verification-regime/building-theinternational-monitoring-system/1994-1996-reaching-critical-mass/

http://www.ctbto.org/verification-regime/building-theinternational-monitoring-system/1994-1996-reaching-critical-mass/


IMS facilities belong to individual States Signatories, which designate an organization, known as a station operator, to manage and operate the facility and to be a point of contact for the Commission. The organization can be a government office under the civilian or military branches, a research institution of the government or an academic institution, or a commercial organization. The Commission maintains formal contractual arrangements with the station operators of primary seismic stations, hydroacoustic stations, infrasound stations, radionuclide stations and radionuclide laboratories. However, the station operators of auxiliary seismic stations, which comprise approximately one third of the total IMS facilities, do not have any formal contractual arrangements and cooperate with the Commission on the basis of voluntary support from their respective institutions.

For a large number of IMS facilities, the station operator is not located at the IMS facility or at the GCI connection location. In these cases, the station operator travels to the IMS facility periodically to conduct maintenance or as needed for unplanned maintenance. The working hours of a station operator range from a 5 day business week to fully staffed 24 hour operations. The business week can be Monday to Friday or Sunday to Thursday, depending on the country. The working language varies, and command of the English language cannot be assumed.

The Commission assigns each IMS facility its own Class C (/24) private IP address range. A small number of facilities operate with individual legacy /28 private IP address ranges.

Since an IMS facility is considered to be untrusted from the point of view of network and IT security, the security of the GCI link is an important concern.

Figure 1.2. Distribution of International Monitoring System Facilities

1.3.6. Communications Nodes

Communications nodes are the interface points between the GCI and other networks that are not part of the GCI (see Figure 1.1). These other networks are directly connected to approximately one third of

Page 14 of 116 12/02/016


the IMS facilities. The data from an IMS facility must pass through the other network and the communications node to enter the GCI and arrive at the IDC. These networks are described in Section 1.3.8 (External Networks).

A communications node is independent of the Commission and has its own staff and processing facilities. Generally, the Commission maintains a formal contractual arrangement with each organization that owns and manages a communications node. Working hours at a communications node range from a 5 day business week to fully staffed 24 hour operations. The business week can be Monday to Friday, or Sunday to Thursday depending on the country. The working language varies, and command of the English language cannot be assumed.

1.3.7. Other Facilities

Four other types of facilities are connected to the GCI:

Station operator;

CTBTO contractor;

Tsunami warning centre;

Shared user.

Station operators that are not physically present at the IMS facility or at the GCI connection location are provided online access (which may include interactive access) to the IMS facility and to the GCI, usually via an Internet VPN link.

CTBTO contractors include third party entities (e.g. universities, private businesses, institutes, individual contractors) engaged to build IMS facilities, develop software or deliver another service to the Commission. They may require online access (usually interactive) to an IMS facility or to station data for the duration of their contract. They may be provided a GCI connection to their office location, usually via an Internet VPN link.

Tsunami warning centres authorized to receive IMS data are sent a continuous feed from the IDC.5 The GCI connection to a tsunami warning centre is an Internet VPN link. The Commission is currently providing data from almost 100 IMS facilities to regional and national tsunami warning centres in 13 countries. (See https://www.ctbto.org/verification-regime/spin-offs-for-disaster-warning-and-science/ for the locations of tsunami warning centres.)

A shared user is a third party which operates equipment that is collocated with an IMS facility. The GCI may transmit data from shared user equipment to the IDC, where the data are forwarded via an Internet VPN to another shared user location. The shared user data use the IP protocol but otherwise employ communications protocols that may be different from those used by IMS facilities, NDCs and the IDC. The data sent to a shared user are different from the IMS monitoring data sent to the IDC. Therefore it is necessary to implement bandwidth management to share the same bandwidth used by the IMS facility.

1.3.8. External Networks

This section describes networks outside the boundary in Figure 1.1 that are connected to the GCI at communications nodes.

5 http://www.ctbto.org/press-centre/press-releases/2011/ctbto-contributes-to-tsunamiwarning-following-the-devastatingearthquake-in-japan.

Page 15 of 116 12/02/016

https://www.ctbto.org/verification-regime/spin-offs-for-disaster-warning-and-science/


1.3.8.1. Independent Subnetworks

An independent subnetwork (ISN) is a collection of IMS facilities that is operated, maintained and networked by one State Signatory. Approximately one third of the IMS facilities are within ISNs. In these TOR, ISN networks are outside of the scope of the GCI, as they deploy their own networking and telecommunications systems. ISN communications technologies may include satellite, terrestrial and Internet media. An ISN interfaces to the GCI either at the NDC of a State Signatory or at a communications node designated by the State Signatory. The data from an IMS facility must pass through both the ISN and the GCI in order to arrive at the IDC. Some of these ISNs have interconnections causing a satellite double hop between the IMS facility and the IDC if the GCI uses a VSAT connection.

Each ISN is covered by an ISN agreement (referred to as an agreement, an arrangement or a contract, depending on the country) between the Commission and the State Signatory. The ISN agreement defines the responsibilities of both parties. This includes inter alia the requirement that the ISN links should be monitored from the NMS of the GCI by means of either an Internet Control Message Protocol (ICMP) or a Simple Network Management Protocol (SNMP).

Each ISN is assigned its own private IP address range with a /20 netmask.

Since an ISN is a collection of IMS facilities its data throughput requirements are generally higher. The security of the GCI link is also an important consideration because an ISN is considered an untrusted network.

1.3.8.2. Other Networks

The GCI is connected to the following other networks:

A network managed by the United States National Science Foundation that connects Denver, Colorado, and Antarctica;

A network managed by the Australian NDC that connects Canberra and Antarctica;

A network managed by a German institute (AWE) that connects Bremerhaven and Antarctica;

A network managed by the South African NDC that connects Cape Town and Antarctica.

In each case, the Commission has a contract with the network operator for the use of the network. Each of these networks is assigned its own private IP address range and includes at least one satellite link.

Page 16 of 116 12/02/016


2. Statement of Work

2.1. Scope of Section

This SOW describes the tasks, deliverables and documentation to be delivered by the Contractor in accordance with the established schedule. The deliverables include, but are not limited to, project management, validation activities, minutes of meetings, quality assurance, training and all required documentation. This SOW also describes the schedule for the delivery of these items. The specifications for these deliverables are included in Section 3 (Specification of Requirements).

2.2. Documentation

M 2.2.1 The Contractor shall provide all required documentation at least 15 days prior to the associated meeting or review unless otherwise agreed with the Commission.

M 2.2.2 The Contractor shall provide the minutes of meetings on the next working day at the latest.

M 2.2.3 The Contractor shall provide all documentation in accordance with Table 2.1.

Table 2.2. Document Life Cycle and Delivery

Document Maturity Required

Project Management Plan Quality Assurance Plan Risk Management Plan Communication Plan

Initial Bid proposal

Preliminary for review Kick-Off Meeting input

Preliminary for approval Kick-Off Meeting output

Final for review Project review meeting input

Final for approval Project review meeting output

Future changes Periodic project review

Feasibility Study Preliminary for review Kick-Off Meeting input


Final for review Design Start Meeting input

Final for approval Design Start Meeting output

High Level Design Document Preliminary for review Bid proposal


Final for review Design Start Meeting input

Final for approval Design Start Meeting output

Future changes Technology refresh checkpoint (CP)

Provisioning, Integration, Validation and Verification (PIVV) Plan

Preliminary for review Kick-Off Meeting input


Final for review PIVV Start Meeting input

Final for approval PIVV Start Meeting output

Future changes At all major architectural and design changes

Page 17 of 116 12/02/016



Proof of Concept Testing Preliminary for review Design Start Meeting input

Preliminary for approval Design Start Meeting output

Final for review Design CP Meeting input

Final for approval Design CP Meeting output

Project Implementation Plan, including:– Terrestrial Core Network

Infrastructure– Teleport Infrastructure– Generic Site Provisioning and

Activation– Site Provisioning and Activation

(site by site)– Concept of Operations– Service Desk, Network

Operations Centre and Network Management System Provisioning and Implementation

– Service Migration Plan

Initial Bid proposal

Preliminary for review Project Review Meeting input

Preliminary for approval Project Review Meeting output

Final for review Project Approval Meeting input

Final for approval Project Approval Meeting output

Future changes Configuration management

Revised Site Provisioning Plan Final for review Implementation Start Meeting input

Final for approval Implementation Start Meeting output

Implementation Report 1 Final for review Implementation CP 1 Meeting input

Final for approval Implementation CP 1 Meeting output

Implementation Report 2 Final for review Implementation CP 1 Meeting input

Final for approval Implementation CP 1 Meeting output

Training Plan Initial Bid proposal

Final for review Kick-Off Meeting input

Final for approval Kick-Off Meeting output

Future changes At major changes

Kick-Off Meeting Report Final Kick-Off Meeting output

Future changes Not applicable

Detailed Design Preliminary for review Design CP Meeting input

Preliminary for approval Design CP Meeting output

Final for review Design End Meeting input

Final for approval Design End Meeting output

Future changes Configuration management

Final Design Report Final Design End Meeting output

Unit Compliance Testing Report Final for review PIVV CP Meeting input

Final for approval PIVV CP Meeting output

Page 18 of 116 12/02/016



Subsystem Verification Test Reports– Terrestrial Core Network– Teleport Infrastructure– Network Management System

Final for review PIVV CP Meeting input

Final for approval PIVV CP Meeting output

System Verification Test Report Final for review PIVV End Meeting input

Final for approval PIVV End Meeting output

Operations and Maintenance Procedures and Documentation

Final for review PIVV End Meeting input

Final for approval PIVV End Meeting output

Site Acceptance Report Final for review At the implementation of each site

Final Implementation Report Final for review Implementation Completion Meeting input

Final for approval Implementation Completion Meeting input

Changes and Upgrades Rolling Throughout the contracttechnology refresh CP

Decommissioning Report Final for approval End of contract

2.3. Project and Services Schedules

M 2.3.1 The Contractor shall perform all tasks and provide all deliverables and documentation in accordance with the schedules in Figure 2.1 and Figure 2.2.

M 2.3.2The Contractor shall record the start, completion and approval dates for each task, deliverable and document. These records shall be available to the Commission upon request.

The principal implementation phases are:

Initial project planning phase;

Design and technical review phase;

Provisioning, integration, validation and verification phase;

Implementation and acceptance phase.

Page 19 of 116 12/02/016


Figure 2.3. Project Implementation Schedule

Figure 2.4. Post-Implementation Schedule

2.3.1. Initial Project Planning Phase

M 2.3.1.1 The Contractor shall deliver all documents and perform all associated actions in accordance with the project implementation schedule in Figure 2.1 and in Table 2.2.

Page 20 of 116 12/02/016


Table 2.3. Project Planning Meetings and Deliverables

Meetings and Checkpoints Deadline[weeks]

Deliverables

Effective Start Date of Contract (EDC)

EDC

Kick-Off Meeting EDC + 3 Preliminary Project Management PlanPreliminary Quality Assurance PlanPreliminary Risk Management PlanPreliminary Communication PlanPreliminary Provisioning, Integration, Validation and Verification PlanFinal Training PlanKick-Off Meeting Report

Project Review EDC + 6 Final Project Management PlanFinal Quality Assurance PlanFinal Risk Management PlanFinal Communication PlanPreliminary Project Implementation Plan including all components specified in Table 2.1

Project Approval EDC + 9 Final Project Implementation Plan including all components specified in Table 2.1

2.3.2. Project Design and Technical Review Phase

M 2.3.2.1The Contractor shall deliver all documents and perform all associated actions in accordance with the design and technical review schedule in Figure 2.1 and in Table 2.3.

Table 2.4. Design and Technical Review Meetings and Deliverables


Deliverables

Design Start Meeting EDC + 10 Final Feasibility StudyPreliminary proof of concept testing DocumentFinal High Level Design Document

Design CP Meeting EDC + 16 Final proof of concept testing DocumentFinal detailed design

Design End Meeting EDC + 24 Final Design Report

2.3.3. Provisioning, Integration, Validation and Verification Phase

M 2.3.3.1The Contractor shall deliver all documents and perform all associated actions in accordance with the provisioning, integration, validation and verification schedule in Figure 2.1 and in Table 2.4.

Page 21 of 116 12/02/016


Table 2.5. Provisioning, Integration, Validation and Verification Meetings and Deliverables


Deliverables

PIVV Start Meeting EDC + 24 Final Provisioning, Integration, Validation and Verification Plan

PIVV CP Meeting EDC + 34 Unit Compliance Testing ReportSubsystem Verification Test Reports including all associated components specified in Table 2.1Activation of entire teleport, terrestrial core network and NMS infrastructure

PIVV End Meeting EDC + 44 System Verification Test ReportActivation of all test sitesOperations and maintenance procedures and documentation

2.3.4. Network Implementation and Migration Phase

M 2.3.4.1The Contractor shall deliver all documents and perform all associated actions in accordance with the network implementation and migration schedule in Figure 2.1 and in Table 2.5.

Table 2.6. Network Implementation and Migration Meetings and Deliverables


Deliverables

Implementation Start Meeting EDC + 44 Revised Site Provisioning PlanActivation of the supporting network and teleport infrastructureInitial operational handover

Implementation CP Meeting 1 EDC + 54 Implementation Report 1

Implementation CP Meeting 2 EDC + 64 Implementation Report 2

Implementation End Meeting EDC + 78 Final Implementation Report

2.3.5. Service Operation and Management Phase

M 2.3.5.1The Contractor shall deliver all documents and perform all associated actions in accordance with the service management schedule in Figure 2.2, Table 2.6 and Table 2.7.

Page 22 of 116 12/02/016


Table 2.7. Service Operation and Management Phase Meetings and Deliverables

Meetings and Checkpoints Deadline[months]

Deliverables

Implementation Completion Date (ICD)

ICD

Service Review Meeting 1 ICD + 24 Service Review Report 1


Technology Refresh Proposal Meeting

ICD +51 Technology Refresh Proposal including High Level Design and Project Plan

Technology Refresh Approval Meeting

ICD + 60 Provisioning, Integration, Validation and Verification Plan for the technology refreshMigration Plan for the implementation of the technology refresh

Technology Refresh Approval Meeting End of Implementation Meeting

ICD + 68 Technology Refresh Implementation ReportUpdate of all affected documentation



Start of Decommissioning Meeting

ICD + 108 Project Plan for decommissioning

End of Service Meeting ICD + 120 End of Service ReportHandover of all documentationHandover of all monitoring data

M 2.3.5.2 Extension options are solely at the discretion of the Commission. The Contractor is requested to confirm their acceptance.

M 2.3.5.3The Commission will inform the Contractor at least 1 year before the end of the contract if extension options will be exercised. The Contractor is requested to confirm their acceptance.

M 2.3.5.4 The service operation and management phase shall be updated by the Contractor accordingly if extension options are exercised.

The service operation and management phase consists of a system of tasks and processes continually applied throughout the operating life of the GCI.

M 2.3.5.5All meetings and teleconferences shall be scheduled in advance and take place only on official United Nations work days between 09:00 and 17:00 CET. The Contractor is requested to confirm their acceptance.

M 2.3.5.6 If the Contractor fails to meet the technical requirements outlined under Section 2 (Statement of Work), the Commission may opt to terminate the contract.

Page 23 of 116 12/02/016


Table 2.8. Schedule of Ongoing Activities During the Service Delivery Phase

Tasks, Deliverables and Meetings Frequency Action/Venue

Operational Status Review Twice a week Teleconference

Operational Escalation Meetings

As required Teleconference

Service Status Review Twice a month Teleconference

Periodic Performance Review Monthly 8 teleconferences (video)4 on-site at the Commission premises

Planning and Approval Meeting

Quarterly Commission premises

Mid-Year Review Yearly (July) Commission premises

Annual Review Yearly (January) Commission premises

2.3.6. Training Courses

M 2.3.6The Contractor shall provide training to the designated representatives and personnel of the Commission and the GCI points of contact as indicated in Error:Reference source not found2.8.

Table 2.9. Training Tasks and Deliverables

Tasks and Deliverables Not Later Than [months]

Action/Venue

Satellite and Terrestrial Technology Seminar (specific to the solutions employed for the GCI)

EDC + 4EDC + 8

Commission premises (5 days)

GCI Overview and Stakeholders Workshop

ICD + 6ICD + 36ICD + 72

Commission premises (2 days)

Station Maintenance Training (on-site)

- 1 day of training at each site after commissioning and 2 hours of refresher training at each maintenance visit

Training Reports 1 week after course completion

Approval

2.4. Key Personnel

M 2.4.1The Contractor shall allocate all the necessary resources and personnel necessary to implement, maintain and operate the GCI network, achieve the SLA targets and comply with all contractual requirements.

M 2.4.2As part of the bid the Contractor shall identify and present to the Commission for its review and approval the key personnel and key teams necessary for the successful completion of the GCI network implementation and its subsequent operation.

M 2.4.3The Contractor shall specify in the bid the allocation of key personnel and their associated roles and responsibilities for both the implementation and post-implementation phases.

Page 24 of 116 12/02/016


M 2.4.4As part of the bid the Contractor shall present to the Commission for its review and approval the curricula vitae and a list of relevant industry certifications for all key personnel specified in articles M 2.4.2 and M 2.4.3.

M 2.4.5

Should the Contractor need to replace a key personnel member it shall inform the Commission thereof in writing at least 30 days in advance of such a planned replacement and present to the Commission for its review and approval the curricula vitae and relevant industry certifications of the new key personnel member. The Contractor shall ensure that a suitable knowledge transfer and handover of documentation takes place such that the new key personnel member is able to fully perform all associated duties from the start of appointment.

M 2.4.6

The list of key personnel as specified in articles M 2.4.2 and M 2.4.3 shall include but is not limited to:

For the implementation phase: Programme Manager: responsible for managing the entire GCI programme

through its lifetime. The Programme Manager shall be the principal manager responsible for the GCI III network and shall have oversight of the purpose and status of all projects and activities within the GCI III programme.

Project Manager: responsible for managing the implementation of the GCI III network and the migration from GCI II to GCI III. It is expected that the Project Manager will report to the Programme Manager directly on all GCI implementation related subprojects and activities.

Chief Engineer for the GCI: responsible for the design of the GCI III network and the coordination of the activities of all other technical teams, including but not limited to the GCI testing and design teams. The Chief Engineer will serve as the most senior technical point of contact to the Commission.

Senior Network Engineers for the GCI: responsible for the design, testing and implementation of the GCI network and shall have relevant experience in the field. It is expected that the Senior Network Engineers will report directly to the Chief Engineer.

For the post-Implementation phase: Programme Manager: responsibilities as defined for the implementation

phase. Service Manager: responsible for interfacing with the Commission on all

service and operational issues. It is expected that the Service Manager will directly report to the Programme Manager.

Chief Engineer for the GCI: responsibilities as defined for the implementation phase.

M 2.4.7

Should the Contractor allocate any of the key personnel partially to the GCI, the Contractor shall clearly specify as part of the bid the amount of time, as a percentage, that will be dedicated under this contract for each key personnel during each phase. Non-specification of the fraction of time shall mean that the key personnel shall allocate 100% of their time to the GCI for the entire duration of the contract.

M 2.4.8The Commission reserves the right to audit the allocation of key personnel to GCI III. Upon the request of the Commission the Contractor shall provide all reports and timesheets necessary to prove the allocation of key personnel and their time expenditure in accordance with the contract.

M 2.4.9For each GCI phase in addition to the key personnel the Contractor shall provide as part of the bid the teams allocated to the different phases, their composition and the allocated percentage time.

M 2.4.10 The teams specified in article M 2.4.9 shall include but are not limited to:

Page 25 of 116 12/02/016


For the implementation phase: Project Team: responsible for the project planning phase and overall

implementation of the GCI III project. It is expected that the Project Team will report to the Project Manager.

Design Team: responsible for the design phase and the design of the solution. It is expected that the Design Team will report to the Chief Engineer.

Testing and Validation Team: responsible for the PIVV phase. It is expected that the Testing and Validation Team will report to the Chief Engineer.

Migration Team: responsible for the migration from GCI II to GCI III. It is expected that the Migration Team will report to the Project Manager.

For the post-implementation phase: GCI Maintenance and Operations Team: responsible for the maintenance and

operation of the GCI III network following implementation. It is expected that the Maintenance and Operations Team will report to the Service Manager.

GCI Engineering Team: responsible for engineering changes, continual technical improvement of the GCI III network and the design and testing components of the Technology Refresh Phase. It is expected that the GCI Engineering Team will report to the Chief Engineer.

M 2.4.11The Contractor shall provide to the Commission for review the curricula vitae and a list of relevant industry certifications for all team personnel specified in article M 2.4.10 prior to their appointment.

M 2.4.12 The Contractor shall introduce the team members for each team to the Commission at the first meeting of each associated phase.

M 2.4.13Should the Contractor allocate personnel only partially to the GCI the Contractor shall clearly specify as part of the bid the amount of time, as a percentage, that each member of the team will dedicate to each phase under this contract.

M 2.4.14The Commission reserves the right to audit the allocation of team personnel to GCI III. Upon the request of the Commission the Contractor shall provide all reports and timesheets necessary to prove the allocation of team personnel and their time expenditure in accordance with the contract.

M 2.4.15Should the Contractor need to replace a member of the technical team it shall inform the Commission at least 15 days in advance and present to the Commission for review and approval the curriculum vitae and relevant industry certifications of the new team member.

D 2.4.1 It is desirable that the key personnel of the Contractor will have up to date industry specific certifications at an expert level.

Page 26 of 116 12/02/016


3. Specification of Requirements


This section on the Specification of Requirements defines the functional, architectural, technical and operational requirements of the GCI in terms of the services to be delivered. It also describes the services the Contractor shall provide to the Commission as well as the tasks the Contractor shall perform for the Commission.

This section describes the requirements to be met by the Contractor for the following services and products:

Documentation

Project planning

Design specification

Terrestrial core network infrastructure

Teleport infrastructure

Remote sites

NMS

PIVV activities

Service migration

Service operation

Technology refresh

Training

Service retirement

Configuration Management

Security.

3.2. Project Planning

The scope of project planning is to cover the initial phase, when the project scope is defined together with the appropriate methods and planning needed for the completion of the project.

It is envisaged that the project planning phase will be completed within the first 9 weeks after the EDC in accordance with the SOW detailed in Section 2 (Statement of Work).

M 3.2.1 The Contractor shall provide all documents and deliverables for project planning in accordance with the specifications and schedules in the SOW.

D 3.2.1The Commission prefers the employment of PRINCE2 project management methodology. Therefore the use of PRINCE2 project management methodology will constitute an advantage.

The project planning phase will include three major meetings, with all of their associated deliverables:

Kick-Off Meeting

Project Review Meeting

Page 27 of 116 12/02/016


Project Approval Meeting.

M 3.2.2The Kick-Off Meeting, Project Review Meeting and Project Approval Meeting shall be scheduled by the Contractor with the Commission’s approval and be held on the premises of the Commission.

M 3.2.3The Contractor shall appoint a project management team prior to the Kick-Off Meeting. The team will fully represent the Contractor and be responsible for all aspects of project planning.

M 3.2.4 The Contractor shall provide to the Commission for review the curricula vitae of all project management team personnel prior to their appointment.

M 3.2.5Should the Contractor need to replace a member of the project management team it shall inform the Commission at least 30 days in advance and present to the Commission for review and approval the curriculum vitae of the new project team member.

3.2.1. Project Management Plan

M 3.2.1.1The Contractor shall provide to the Commission a Project Management Plan defining the quality goals and metrics for each deliverable in conformance with the contractual requirements.

M 3.2.1.2The Contractor shall provide, implement and maintain throughout the duration of the contract a comprehensive Project Management Plan which includes all deliverables and milestones.

M 3.2.1.3 The Contractor shall provide the Commission a detailed work breakdown structure as part of the Project Management Plan.

M 3.2.1.4

The work breakdown structure shall include but is not limited to: Scope of work undertaken by subcontractors; Products to be delivered by subcontractors; Details of all suppliers and all external service providers; Other external project resources.

M 3.2.1.5The work breakdown structure shall include all deliverables in terms of the work to be completed, including internal, external and interim deliverables and aspects of project management.

M 3.2.1.6 There shall not be any overlap in scope definition between different elements of the work breakdown structure.

M 3.2.1.7 The Contractor shall deliver a product breakdown structure and a product flow diagram as part of the work breakdown structure.

3.2.2. Quality Assurance Plan

M 3.2.2.1The Contractor shall provide the Commission a Quality Assurance Plan defining quality goals and metrics for each deliverable in conformance with the contractual requirements.

M 3.2.2.2 The scope of the Quality Assurance Plan shall cover all phases, activities, services and products of the project including but not limited to:

Project planning; Design activities; Technical specifications; PIVV activities;

Page 28 of 116 12/02/016


Service migration; Service operation; Configuration management; Documentation; Training; Reporting activities; Shipping and logistics; Licence management; Subcontractor services and products; Incident resolution and escalation; Network monitoring; Incident tracking and review; Security.

M 3.2.2.3 The Quality Assurance Plan shall define the quality criteria, quality methods and processes for all products to be delivered as part of the project.

M 3.2.2.4 The Quality Assurance Plan shall define, in relation to quality assurance, the roles and responsibilities of personnel appointed by the Contractor.

M 3.2.2.5 The Contractor shall provide and maintain a Quality Register throughout the duration of the contract.

M 3.2.2.6 The Quality Register shall be available to the Commission at all times.

M 3.2.2.7The Contractor shall update the Quality Register with the status of all quality checking activities and ensure that all products are complete and have met their quality criteria and that the agreed quality assurance processes have been observed.

M 3.2.2.8The Contractor shall maintain all product approval records and ensure that the quality records showing that each product has met its quality requirements are time-stamped.

M 3.2.2.9 The Contractor shall maintain all product acceptance records and ensure that they are time-stamped and versioned.

M 3.2.2.10 The approval and acceptance records shall be available to the Commission at all times.

M 3.2.2.11 The Contractor shall record in the Quality Register and time-stamp any off-specification or failure to meet the agreed quality criteria.

M 3.2.2.12The Contractor shall inform the Commission via an exception report of any off-specification and/or failure to meet quality criteria that might impact the project tolerance with regard to scope, risk or schedule.

M 3.2.2.13 The Contractor shall be fully responsible for the quality management of all products and services to be delivered by subcontractors or any external parties.

M 3.2.2.14During the implementation phase of the project, including the project planning, design, PIVV and service migration phases, the Contractor shall submit a weekly Quality Report detailing all quality and testing activities performed and their associated outcomes.

M 3.2.2.15During the post-implementation phase of the project the Contractor shall submit a quarterly Quality Report detailing all quality activities performed and their associated outcomes.

M 3.2.2.16The Quality Assurance Plan shall document all mechanisms and processes to address any off-specification, failure to meet quality criteria and non-conformance issues.

Page 29 of 116 12/02/016


3.2.3. Risk Management Plan

M 3.2.3.1 The Contractor shall submit to the Commission for review and approval a Risk Management Plan in accordance with the specifications and schedules in the SOW.

M 3.2.3.2

The scope of the Risk Management Plan shall cover all phases of the project, including but not limited to:

Design activities; Technical specifications; PIVV activities; Service migration; Service operation; Shipping and logistics; Licence management; Subcontractor services and products; Incident resolution and escalation; Network monitoring; Security.

M 3.2.3.3 The Risk Management Plan shall identify the risks to the project, assess and estimate the impacts of the risks and define a response strategy.

M 3.2.3.4 The Contractor shall provide a Risk Register at the beginning of the project and maintain the Risk Register throughout the duration of the project.

M 3.2.3.5 The Risk Register shall be available to the Commission at all times.

M 3.2.3.6 The Contractor shall update the Risk Register with any newly identified risks including their estimated probability and impact and mitigation actions.

M 3.2.3.7

The Contractor shall provide an in-depth risk analysis for all identified risks, including but not limited to:

Risk cause; Risk effect; Cause and effect diagram; Probability trees; Probability impact grid; Possible actions.

M 3.2.3.8 Should a risk materialize the Contractor shall be responsible for taking action as necessary to address it and record it in the Risk Register.

3.2.4. Communication Plan

Given the complexity of the GCI project the Contractor is expected to establish an effective communication management strategy which shall be detailed in the Communication Plan.

M 3.2.4.1The Contractor shall submit to the Commission for review and approval a Communication Plan in accordance with the specifications and schedules in the SOW.

M 3.2.4.2

The Communication Plan shall describe: Specific communication management procedures; Communication tools and techniques; Schedule of key communication activities; Records to be kept; Roles and responsibilities to carry out communication activities.

Page 30 of 116 12/02/016


3.2.5. Project Implementation Plan

Given the time criticality and associated deadlines with regard to project implementation the Contractor is expected to institute an effective project implementation and scheduling strategy which shall be detailed in the Project Implementation Plan.

M 3.2.5.1The Contractor shall submit to the Commission for review and approval a Project Implementation Plan in accordance with the specifications and schedules in the SOW.

M 3.2.5.2

The scope of the Project Implementation Plan shall cover the planning of critical actions, activities and phases with their associated schedules and resources necessary for the project implementation, including but not limited to:

Terrestrial Core Networks Infrastructure Plan Teleport Infrastructure Plan Network Operations Centre Plan Service Desk Plan Network Management System Plan Provisioning Integration Verification and Validation Plan Design Plan Generic Site Provisioning and Activation Plan. Site by Site Provisioning and Activation Plan Site Survey Plan including the associated reviews Concept of Operations Plan Service Migration Plan Shipping and Logistics Plan Licence Management Plan

M 3.2.5.3The Project Implementation Plan shall identify the schedules, timelines and milestones for each of the activities and phases specified in article M 3.2.5.2 with the allocated resources and personnel together with their associate roles and responsibilities.

M 3.2.5.4The Project Implementation Plan and its associated plans shall conform to the schedules defined Section 2 (Statement of Work) and in the rest of the requirements.

M 3.2.5.5As part of the Project Implementation Plan the Contractor shall include a Critical Path Analysis and the associated Critical Success Factors Analysis for review and approval by the Commission in accordance with the schedules defined in Section 2 (Statement of Work).

M 3.2.5.6

As part of the bid the Contractor shall provide sufficient documentation in the Project Implementation Plan to demonstrate that the project is achievable in accordance to the requirements and the schedule defined in Section 2 (Statement of Work) and that there is sufficient tolerance in the schedule to accommodate unforeseen events with a potential negative impact on the project and on product delivery.

M 3.2.5.7 The Contractor shall provide the Project Implementation Plan as part of the bid and update the plan as necessary throughout the Implementation Phase.

M 3.2.5.8 The Project Implementation Plan shall be available to the Commission at all times.

3.2.6. Business Continuity Planning and Disaster Recovery

Given the key role of the GCI in fulfilling the mission of the Commission, business continuity planning and disaster recovery are essential.

Page 31 of 116 12/02/016


M 3.2.6.1The Contractor shall have in place all necessary business continuity planning and disaster recovery mechanisms to ensure the recovery of full service within a maximum of 15 days regardless of the disaster or force majeure event affecting the service.

M 3.2.6.2

Events that shall be covered in business continuity planning and disaster recovery include but are not limited to:

Loss of satellite used for GCI III service; Loss of a teleport owing to a natural disaster or other force majeure event; Loss of the terrestrial core network owing to a natural disaster or other force

majeure event; Any event which could negatively impact the delivery of service, such as

supply chain interruption and loss of or damage to critical infrastructure.

M 3.2.6.3The business continuity planning and disaster recovery document shall be submitted by the Contractor to the Commission for review and approval within 2 months of the EDC.

M 3.2.6.4The Contractor shall update the business continuity planning and disaster recovery document with any changes in the GCI III network throughout the duration of the contract.

3.2.7. Kick-Off Meeting

The intended scope of the Kick-off Meeting is to launch the project planning phase, introduce the project management team and review the associated documents and plans.

M 3.2.7.1 The Contractor shall organize and document the Kick-Off Meeting.

M 3.2.7.2 The Kick-Off Meeting shall be scheduled in accordance with the relevant article in the SOW.

M 3.2.7.3

As part of the Kick-Off Meeting the Contractor shall deliver to the Commission the following documents:

Preliminary Project Management Plan; Preliminary Quality Assurance Plan; Preliminary Risk Management Plan; Preliminary Communication Plan; Preliminary Provisioning Integration, Validation and Verification Plan; Final Training Plan.

M 3.2.7.4The documents delivered in accordance with article M 3.2.7.3 shall be reviewed by the Commission with the assistance of the Contractor at the Kick-Off Meeting, and the outcomes of the review shall be recorded.

M 3.2.7.5The actions resulting from the review specified in article M 3.2.7.4 shall be recorded by the Contractor in an action plan together with the responsible personnel and associated deadlines.

M 3.2.7.6The Contractor shall submit to the Commission for review and approval a Kick-Off Meeting Report. The report shall incorporate the action plan, the minutes of the meeting and the outcomes of the document review.

M 3.2.7.7As part of the Kick-Off Meeting the Contractor shall appoint and introduce to the Commission the project management team, including the roles and responsibilities of each member.

Page 32 of 116 12/02/016


3.2.8. Project Review Meeting

The intended scope of the Project Review Meeting is mainly the review of the associated documents and plans.

M 3.2.8.1 The Contractor shall organize and document the Project Review Meeting.

M 3.2.8.2 The Project Review Meeting shall be scheduled in accordance with the relevant article in the SOW.

M 3.2.8.3

As part of the Project Review Meeting the Contractor shall deliver to the Commission the following documents:

Final Project Management Plan; Final Quality Assurance Plan; Final Risk Management Plan; Final Communication Plan; Preliminary PIP.

M 3.2.8.4The documents delivered in accordance with article M 3.2.8.3 shall be reviewed by the Commission with the assistance of the Contractor at the Project Review Meeting and the outcomes of the review shall be recorded.


3.2.9. Project Approval Meeting

The intended scope of the Project Review Approval Meeting is mainly the finalization of all documents and plans associated with project planning and the conclusion of the project planning phase.

M 3.2.9.1 The Contractor shall organize and document the Project Approval Meeting.

M 3.2.9.2 The Project Approval Meeting shall be scheduled in accordance with the relevant article in the SOW.

M 3.2.9.3 As part of the Project Approval Meeting the Contractor shall deliver to the Commission the Final PIP with all associated components.

M 3.2.9.4The Final PIP shall be reviewed by the Commission with the assistance of the Contractor at the Project Approval Meeting and the outcomes of the review shall be recorded.

M 3.2.9.5The actions resulting from the review of the Final PIP shall be recorded by the Contractor in an action plan together with the responsible personnel and associated deadlines.

M 3.2.9.6The Project Approval Meeting shall conclude the project implementation phase and all the associated actions, documents, plans and other deliverables shall be finalized by the Contractor.

3.3. Design and Technical Review Phase

The scope of the Design and Technical Review Phase is to produce the detailed technical design by transferring Commission’s requirements into a fit for purpose and cost effective solution.

It is envisaged that the Design and Technical Review Phase will be completed within the first 24 weeks after the EDC in accordance with the SOW detailed in Section 2 (Statement of Work).

Page 33 of 116 12/02/016


M 3.3.1The Contractor shall provide all documents and deliverables for the Design and Technical Review Phase in accordance with the specifications and schedules in the SOW.

D 3.3.1The Commission prefers the employment of ITIL and/or systems engineering methodologies. Therefore the use of ITIL and/or systems engineering methodologies will constitute an advantage.

The Design and Technical Review Phase will include three major meetings, with all of their associated deliverables:

Design Start Meeting

Design CP Meeting

Design End Meeting

M 3.3.2The Design Start, Design CP and Design End meetings shall be scheduled by the Contractor with the approval of the Commission and be held on the premises of the Commission.

M 3.3.3 The Contractor shall appoint a technical design team prior to the Design Start Meeting. The team will be responsible for all technical design aspects.

M 3.3.4The Contractor shall provide to the Commission for review the curricula vitae and a list of technical certifications for all the technical design team personnel prior to their appointment.

M 3.3.5Should the Contractor need to replace a member of the technical design team it shall inform the Commission at least 15 days in advance and present to the Commission for review and approval the curriculum vitae and relevant industry certifications of the new design team member.

D 3.3.2 It is desirable that the personnel in the Contractor’s technical design team will have up to date industry specific certifications at an expert level.

M 3.3.6All the documentation of the Design and Technical Review Phase including but not limited to the High Level Design Document, Detailed Design Document, Proof of Concept Testing Document and all other associated documents shall be placed under a version controlled Document Management System.

M 3.3.7All the documentation of the Design and Technical Review Phase and access to its associated Document Management System shall be available to the Commission at all times.

M 3.3.8As part of the Design and Technical Review Phase the Contractor shall perform all proof of concept testing necessary to prove the viability of the proposed solution and its ability to meet the Commissions requirements.

M 3.3.9The Contractor shall submit the Preliminary Proof of Concept testing document to the Commission for review and approval as part of the Design Start Meeting in accordance with the schedules in the SOW.

M 3.3.10The Contractor shall cooperate with the Commission and make all the arrangements necessary ensuring that, upon request, a representative of the Commission will be able to witness all proof of concept testing activities.

M 3.3.11 At the end of the Design and Technical Review Phase the contract shall document all design related activities and their associated outcomes in the Final Design

Page 34 of 116 12/02/016


Report.

3.3.1. High Level Design

M 3.3.1.1 As part of the bid the Contractor shall deliver to the Commission the High Level Design Document for the GCI network.

M 3.3.1.2The High Level Design Document shall take into the consideration the requirements of the Commission and provide high level analysis with regard to critical success factor and how the KPIs and requirements will be met.

M 3.3.1.3

The High Level Design Document specified in article M 3.3.1.1 shall include, but is not limited to, the following:

Overview of the proposed solution. Architecture of the proposed GCI network (including but not limited to high

level architecture, terrestrial core network infrastructure, teleport infrastructure, remote sites and transportable stations).

Decomposition of systems and subsystems. Scalability analysis. Vital business functions (including but not limited to high availability and fault

tolerance, continuous operations and service availability). Concept of operations. Business continuity and disaster recovery. Business impact analysis including risk mitigation. Service, technology and tools to be employed. Platforms to be employed. Products and services including any products and service employed by the

Contractor from external parties. High Level Security Plan (including at least but not limited to confidentiality,

integrity and availability). Assumptions. Constraints.

M 3.3.1.4

The Contractor shall update the High Level Design Document specified in article M 3.3.1.1, throughout the duration of the GCI contract, with changes including but not limited to changes resulting from: lessons learned in the design process, proof of concept testing, PIVV phase, upgrades and improvements and the Technology Refresh Phase.

M 3.3.1.5 The High Level Design Document shall be available to the Commission at all times.

3.3.2. Detailed Design

M 3.3.2.1 As part of the Design Checkpoint Meeting the Contractor shall deliver to the Commission the High Level Design Document for the GCI network.

M 3.3.2.2 The Detailed Design Document specified in article M 3.3.2.1 shall include, but is not limited to, the following:

Detailed architecture of the proposed solution including detailed diagrams containing individual components, subsystems and communications links.

Detailed architecture and design for the terrestrial core network infrastructure. Detailed architecture and design for the teleport infrastructure (including but

not limited to teleport antennas, teleport antenna redundancy, site diversity, power infrastructure, teleport local network, teleport interface with external telecommunications providers, hubs, RF chains, teleport and hub NMS systems, physical security).

Detailed architecture and design for the remote sites (including but not limited

Page 35 of 116 12/02/016


to routers, local remote site network, satellite equipment, interfaces with external providers, interface with the station equipment and redundancy and resilience architecture).

Detailed architecture and design for the transportable stations (including but not limited to routers, local transportable site network, satellite equipment, interface with the local equipment and redundancy and resilience architecture).

Detailed architecture and design for the Network Monitoring System. Detailed architecture of the document and configuration management systems

(CMSs). Detailed security architecture (including but not limited to encryption protocols,

layer 2 security, layer 3 security, hashing, VPN, firewalling, threat prevention and mitigation, system hardening, authentication, authorization and accounting, timestamping, logging and physical security).

Detailed IP routing and switching architecture (including but not limited to detailed protocol configuration, routing policies, timers, route distribution and tagging, route dampening, physical interface specification, first hop redundancy protocols, VLANs, switching redundancy mechanism, link aggregation, layer 2 optimization, wide area network optimization and traffic engineering).

Detailed quality of service (QOS) architecture (including but not limited to traffic classes, classification and marking, layer 2 QOS mechanisms, queuing, shaping, policing, bandwidth enforcement, random early detection (RED), call admission control, header compression and bandwidth optimization).

Detailed specification for all the individual components and subsystems. Detailed specifications for subcontracted services. Detailed interface specifications between all the systems and subsystems. Detailed configuration templates for all the individual elements wherever

applicable. Detailed link budget and availability analysis for all regions. Detailed redundancy and resiliency architecture (including but not limited to

component failure impact analysis, fault tree analysis, single point of failure analysis).

Detailed capacity planning. Constraints and limitations.

M 3.3.2.3The Contractor shall update the Detailed Design Document specified in article M 3.3.2.1 throughout the lifetime of the GCI contract with changes including but not limited to changes resulting from the PIVV phase, upgrades and improvements and the Technology Refresh Phase.

M 3.3.2.4 The Detailed Design Document shall be available to the Commission at all times.

3.3.3. Proof of Concept

The goal of proof of concept testing is to demonstrate, during the Design Phase, in a laboratory environment the viability of the proposed technical solution and ensure that it is fit for purpose.

M 3.3.3.1 As part of the Design Start Meeting the Contractor shall deliver to the Commission the Preliminary Proof of Concept Document.

M 3.3.3.2The Contractor shall deliver the Final Proof of Concept Document to the Commission for review as part of the Design Checkpoint Meeting in accordance with the specifications and schedules in the Statement of Work.

M 3.3.3.3The Final Proof of Concept Document shall be based on the Preliminary Proof of Concept Document and incorporate all changes and updates resulting from the design and technical review phase.

Page 36 of 116 12/02/016


M 3.3.3.4

The Proof of Concept Document shall include but is not limited to: Detailed description of the test environment (including but not limited to

detailed diagrams and configurations); All relevant tests needed to demonstrate the feasibility of the proposed

platforms and solutions with the design requirements; Methodology and tools to be used for each test; Step by step description of the activities for each test and the expected

outcomes; Pass and fail criteria for each test; Criticality level for each associated test.

M 3.3.3.5 The Proof of Concept Document shall be reviewed by the Commission with the assistance of the Contractor.

M 3.3.3.6

The Contractor shall update the Final Design Report with the proof of concept testing results including but not limited to:

Results of the test; Values of the measured parameters; Error messages and warnings produced during the test; Logs from the associated elements to be tested ; Screenshots; Time stamps for each of the activities included in the tests; Other relevant information.

M 3.3.3.7 The Proof of Concept Document shall be available to the Commission at all times.

M 3.3.3.8The Contractor shall inform the Commission in writing via an exception report of any failed proof of concept test with a potential impact on the scope, schedule or functionality of the GCI network and update the Risk Register accordingly.

M 3.3.3.9The Contractor shall present to the Commission for review a mitigation plan and a risk analysis for any failed proof of concept test with a potential impact on the GCI network.

3.3.4. Design Start Meeting

The intended scope for the Design Start Meeting is to launch the Design and Technical Review Phase, introduce the technical design team and to review the associated plans and schedules.

M 3.3.4.1 The Contractor shall organize and document the Design Start Meeting.

M 3.3.4.2 The Design Start Meeting shall be scheduled in accordance with the relevant articles in the SOW.

M 3.3.4.3

As part of the Design Start Meeting the Contractor shall deliver to the Commission the following documents:

Final Feasibility Study Preliminary Proof of Concept Document Final High Level Design Document

M 3.3.4.4 The documents delivered in accordance with article M 3.3.4.3 shall be reviewed at the Design Start Meeting and the outcomes of the review shall be recorded.

M 3.3.4.5The actions resulting from the review specified in article M 3.3.4.4 shall be recorded by the Contractor in an action plan, which will include the personnel responsible for these actions and deadlines.

M 3.3.4.6The Contractor shall submit to the Commission for review and approval a Design Start Meeting Report. The report shall incorporate the action plan, minutes of the meeting and outcomes of the document reviews.

Page 37 of 116 12/02/016


3.3.5. Design Checkpoint Meeting

The intended scope for the Design Checkpoint Meeting is to verify the design process, review the associated proof of concept testing and the associated reports.

M 3.3.5.1 The Contractor shall organize and document the Design Checkpoint Meeting.

M 3.3.5.2 The Design Checkpoint Meeting shall be scheduled in accordance with the relevant articles in the SOW.

M 3.3.5.3

As part of the Design Checkpoint Meeting the Contractor shall deliver to the Commission the following documents:

Final Proof of Concept Document Final detailed design Document

M 3.3.5.4The documents delivered by the Contractor in accordance with article M 3.3.5.3 shall be reviewed at the Design Checkpoint Meeting by the Commission together with the Contractor and the outcomes of the review shall be recorded.


M 3.3.5.6The Contractor shall submit to the Commission for review and approval a Design Checkpoint Meeting Report. The report shall incorporate the action plan, the minutes of the meeting and the outcomes of the document reviews.

3.3.6. Design End Meeting

The intended scope for the Design End Meeting is to conclude the design phase, determine readiness to start of the PIVV phase, review the associated design reports and documents.

M 3.3.6.1 The Contractor shall organize and document the Design End Meeting.

M 3.3.6.2 The Design End Meeting shall be scheduled in accordance with the relevant articles in the SOW.

M 3.3.6.3As part of the Design End Meeting the Contractor shall deliver to the Commission the following document:

Final Design Report

M 3.3.6.4The document delivered by the Contractor in accordance with M 3.3.6.3 shall be reviewed by the Commission together with the Contractor at the Design End Meeting and the outcomes of the review shall be recorded.


M 3.3.6.6The Contractor shall submit to the Commission for review and approval a Design End Meeting Report. The report shall incorporate the action plan, the minutes of the meeting and the outcomes of the document reviews.

3.4. Terrestrial Core Network Infrastructure

The terrestrial core network is comprised of the entire supporting network infrastructure used to transport data between the teleports of the Contractor and the headquarters of the Commission in Vienna.

Page 38 of 116 12/02/016


The terrestrial core network can also be used to support connectivity between the IDC and specific ISN networks or other remote sites. Possible remote sites for which direct terrestrial core network connectivity could be employed include are but not limited to: ISN-NO, ISN-RU, ISN-CN, ISN-FR, SG-US7 and ISN-CA.

At a later stage a backup IDC site will be connected to the terrestrial core network. It is expected to have the same functionality and requirements as those of the headquarters of the Commission.

Special emphasis is put on the redundancy and resiliency of this network because failure of the terrestrial core network infrastructure would have a significant impact on the Commission.

M 3.4.1 Prior to deployment into service the terrestrial core network system shall pass all agreed acceptance tests and demonstrate full compliance with all requirements.

3.4.1. Terrestrial Core Network Functionality

M 3.4.1.1 The Contractor shall provide the terrestrial core network necessary to connect all teleports, remote sites, ISNs, the IDC and backup IDC sites.

M 3.4.1.2The terrestrial core network shall support the transport of Internet Protocol version 4 (IPv4) data, including all underlying protocols and ports between all connected locations.

M 3.4.1.3The terrestrial core network shall support the transport of Internet Protocol version 6 (IPv6) data, including all underlying protocols and ports between all connected locations.

M 3.4.1.4The terrestrial core network shall support the effective transport of IPv4 and IPV6 multicast data including all underlying protocols and ports between all connected locations.

3.4.2. Terrestrial Core Network Specifications

M 3.4.2.1 The terrestrial core network shall employ only non-proprietary dynamic routing protocols.

M 3.4.2.2 No network address translation (NAT) shall be implemented within the terrestrial core network.

M 3.4.2.3

For the implementation of the terrestrial core network the Contractor shall employ telecommunications equipment from major vendors such as Cisco Systems, Juniper Networks, Alcatel Lucent, Huawei, Arista Networks, Broadcom, Ericsson, Ciena, ECI, Palo Alto Networks and Fortinet. The use of equipment from any other vendor must be justified and is subject to the approval of the Commission.

M 3.4.2.4 The terrestrial core network infrastructure shall not restrict any protocols, ports or IP addresses for the Commission’s traffic.

3.4.3. Terrestrial Core Network Capacity and Performance

M 3.4.3.1 The terrestrial core network links shall be provisioned with enough capacity to support all traffic of the Commission without congestion.

M 3.4.3.2The Contractor shall design the terrestrial core network with adequate scalability in order to accommodate, on request by the Commission, an increase in throughput capacity of at least 100% from the initial values.

M 3.4.3.3 As part of the design documentation the Contractor shall submit to the Commission for review and approval a scalability study documenting how the presented solution

Page 39 of 116 12/02/016


is able to accommodate the required throughput capacity of the terrestrial core network and a 100% increase in bandwidth capacity.

M 3.4.3.4 The terrestrial core network shall introduce a round trip time delay of less than 500 milliseconds.

M 3.4.3.5 The Contractor shall submit to the Commission for review and approval a capacity test plan demonstrating compliance with the requirements.

M 3.4.3.6The Contractor shall perform long term stability and packet loss testing prior to deployment of the terrestrial core network in order to demonstrate compliance with SLA specifications. The testing period shall cover at least 72 hours.

3.4.4. Terrestrial Core Network Redundancy and Resiliency

M 3.4.4.1 The Contractor shall implement the terrestrial core network without any single point of failure and all network elements and circuits shall be redundant.

MD 3.4.4.1The terrestrial core network shall consist of two interoperable parts:

Main terrestrial core network infrastructure; Internet backup for the main terrestrial core network infrastructure.

M 3.4.4.2The main terrestrial core network infrastructure shall be implemented with dedicated circuits other than Internet circuits or circuits reliant on the Internet infrastructure.

M 3.4.4.3The main terrestrial core network infrastructure shall be fully redundant by itself and be designed without any single point of failure. This shall include both redundant links and redundant network elements to automatically restore service in case of failure.

M 3.4.4.4

The following technologies that can be employed for the main terrestrial core network infrastructure circuits are:

Dedicated leased lines, Multiprotocol label switching (MPLS) Layer 3 VPNs, Virtual private LAN services (VPLS), MPLS pseudo-wires.

Any other link technology used for the implementation of the main terrestrial core network infrastructure shall be reviewed and approved by the Commission prior to implementation.

M 3.4.4.5 In the case of failure of the main terrestrial core network infrastructure traffic shall be automatically routed to the Internet backup.

M 3.4.4.6 The Commission shall allocate a pool of four IPv4 addresses for the Contractor’s use in order to terminate Internet backup and IP VPN connectivity.

M 3.4.4.7The Contractor shall provide the Commission a list of all necessary ports and protocols to be allowed through the firewall for the IPv4 and IPv6 addresses specified in article M 3.4.4.6.

M 3.4.4.8 The Contractor shall be responsible for implementation of all necessary security measures on their devices at the IDC.

M 3.4.4.9The Contractor shall ensure enough Internet capacity at all teleport sites to support full GCI functionality in the case of failure of the main terrestrial core network infrastructure.

M 3.4.4.10 The Internet connectivity of the Contractor shall be fully redundant.

M 3.4.4.11 The Contractor shall ensure that all prime and backup circuits of the main terrestrial core network infrastructure are geographically diverse in order to minimize the

Page 40 of 116 12/02/016


possibility of single events affecting both prime and backup circuits.

M 3.4.4.12 The Contractor shall provide to the Commission all necessary information to verify the diverse geographical routing of circuits.

M 3.4.4.13

The terrestrial core network shall be designed and implemented to ensure that the convergence time (time necessary to restore operational traffic) in the event of failure of a single network element or link in the terrestrial core network shall be no longer than 3 minutes. The Contractor shall submit to the Commission for review and approval a validation test plan demonstrating compliance.

M 3.4.4.14 The links in the terrestrial core network shall have enough capacity to transport all required data, even in the event of a single failure, without congestion.

M 3.4.4.15In addition to the online prime and standby elements of the terrestrial core network, the Contractor shall have at least 1 configured cold spare for each network element at every site in order to be able to restore redundancy in a timely fashion in case of failure.

M 3.4.4.16The Contractor shall ensure that it has in place all necessary site access arrangements to permit performance of all preventive and reactive maintenance needed to meet SLA targets.

M 3.4.4.17The terrestrial core network hardware and software shall be covered by appropriate support contracts through the operating life of the system. The Commission reserves the right to audit these contracts on an ad hoc basis.

M 3.4.4.18The Contractor shall maintain the hardware and software for the terrestrial core network and ensure that the hardware and software are supported and can be maintained as part of vendor support contracts.

M 3.4.4.19The Contractor shall report to the Commission at least 6 months in advance when terrestrial core network hardware and software subsystems are reaching ‘end of life’ or ‘end of support’ and present an upgrade plan to the Commission for review and approval.

M 3.4.4.20 The Contractor shall provide to the Commission for review and approval a Disaster Recovery Plan for the terrestrial core network before the network enters operation.

3.4.5. Terrestrial Core Network Quality of Service

M 3.4.5.1The Contractor shall implement end to end QOS across the terrestrial core network using at least five traffic classes in accordance with the specifications provided by the Commission.

M 3.4.5.2 Each traffic class shall have its bandwidth capacity enforced and guaranteed throughout the network.

M 3.4.5.3 Any unused bandwidth shall be made available to other traffic classes on a best effort basis.

M 3.4.5.4The terrestrial core network infrastructure shall preserve the QOS markings throughout the network unless a policing and ‘mark down’ mechanism has been previously agreed with the Commission. Should such a mechanism be agreed the QOS marking change shall be made in accordance with the specific agreement.

M 3.4.5.5Any random early detection (RED) QOS mechanisms in the terrestrial core network shall be reviewed and approved by the Commission prior to implementation by the Contractor.

M 3.4.5.6Any deployment of ‘TCP spoofing’, Protocol Enhancing Proxy (PEP) or WAN optimization in the terrestrial core network shall be reviewed and approved by the Commission prior to implementation by the Contractor.

Page 41 of 116 12/02/016


M 3.4.5.7 Should any tunnelling protocols be employed in the terrestrial core network, all QOS markings shall be copied over to the tunnel header.

M 3.4.5.8 Should MPLS technology be deployed in the terrestrial core network, all QOS markings shall be mapped to the MPLS experimental bits field accordingly.

3.4.6. Terrestrial Core Network Interface with the Commission

3.4.6.1. Terrestrial Core Network Interface with the International Data Centre

M 3.4.6.1.1 The interface point of the terrestrial core network and the IDC shall be on the premises of the IDC at the headquarters of the Commission in Vienna.

M 3.4.6.1.2The Commission shall reserve the right to request the Contractor to relocate the terrestrial core network interface point with 3 months’ notice. The Contractor shall implement the relocation in a manner that ensures no interruption of services for more than 1 hour.

M 3.4.6.1.3The terrestrial core network shall interface with the IDC network using RJ45 Gigabit Ethernet 1000Base-T ports. Subject to prior approval by the Commission, the terrestrial core network may also interface with the IDC using optical Gigabit Ethernet connectivity.

M 3.4.6.1.4The Interconnection with the Commission’s IDC shall be fully redundant. The network elements at the IDC shall be redundant and connect to both the main terrestrial core network infrastructure and the Internet backup infrastructure.

M 3.4.6.1.5The terrestrial core network shall exchange all necessary routing information with the Commission using the external border gateway protocol (EBGP) (Request for Comment (RFC) 4271).

M 3.4.6.1.6

The Contractor shall provide two fully redundant routers, each one peering, using the EBGP protocol, with a designated router of the Commission. The Contractor shall configure the EBGP peering routers in accordance with the EBGP session specification details provided by the Commission and will include but are not limited to: Autonomous System (AS) numbers, IP address interface points, address families, timers, Bidirectional Forwarding Detection (BFD) and authentication.

M 3.4.6.1.7 The terrestrial core network shall distribute all remote sites or other GCI networks via EBGP protocol without any route summarization.

M 3.4.6.1.8In the event of a remote site or GCI network becoming unavailable through the terrestrial core network the Contractor shall withdraw the Border Gateway Protocol (BGP) route advertising of that network within 5 minutes of the event.

M 3.4.6.1.9 The Contractor shall implement BGP route refresh capability at the interface point with the Commission in accordance with RFC 2918.

M 3.4.6.1.10 The terrestrial core network shall support BGP community transparency in the route advertisements.

3.4.6.2. Terrestrial Core Network Interface with Remote Sites

M 3.4.6.2.1The terrestrial core network interface point with the remote sites of the Commission, i.e. sites other than those at the headquarters of the Commission or at the backup IDC (e.g. some of the ISNs), shall be at the designated location of the remote site.

M 3.4.6.2.2The terrestrial core network shall interface with remote sites using RJ45 Gigabit Ethernet 1000Base-T ports. Subject to prior approval by the Commission the terrestrial core network may also interface with the remote sites using optical Gigabit Ethernet connectivity.

Page 42 of 116 12/02/016


M 3.4.6.2.3The interconnection with the remote sites of the Commission shall be fully redundant. All network elements at the remote site shall be redundant and connect to the main terrestrial core network infrastructure and the Internet backup infrastructure.

M 3.4.6.2.4

The following options shall be available for the terrestrial core network routing exchange with the remote sites:

EBGP interfacing as described in articles M 3.4.6.1.5, M 3.4.6.1.6, M 3.4.6.1.7, M 3.4.6.1.8, M 3.4.6.1.9 and M 3.4.6.1.10 in the same manner as for the interface point with the IDC of the Commission.

The network elements present at the remote site for the terrestrial core network will provide a Virtual Router Redundancy Protocol IP address which should act as a gateway to the remote site network infrastructure. Static routing will be employed as specified by the Commission. It is the responsibility of the Contractor to ensure that the static routes are correctly redistributed within the terrestrial core network in compliance with the rest of the requirements.

The Commission shall decide on a site by site basis which of the two solutions will be implemented.

3.4.6.3. Terrestrial Core Network Interface with the Backup International Data Centre

M 3.4.6.3.1 The Contractor shall implement at the request of the Commission connectivity to the backup IDC site.

M 3.4.6.3.2The interface point of the terrestrial core network with the backup IDC of the Commission shall be on the backup IDC premises at a location designated by the Commission.

M 3.4.6.3.3Backup IDC connectivity to the terrestrial core network shall be implemented in manner similar to that for IDC connectivity to the terrestrial core network. Articles M 3.4.6.1.2 to M 3.4.6.1.10 also apply to the backup IDC.

3.4.7. Terrestrial Core Network Configuration Management

M 3.4.7.1Following acceptance the terrestrial core network elements shall be put under configuration management and control. Change requests shall be submitted to the Commission for review and approval at least 30 days in advance.

M 3.4.7.2The terrestrial core network elements shall be integrated with and continuously monitored by the NMS in accordance with Section 3.7 (Network Management System).

M 3.4.7.3

Should the Commission consider the changes to the terrestrial core network to be major, it shall reserve the right to request a full or partial re-run of the acceptance testing for the terrestrial core network infrastructure. Should this acceptance testing fail to meet all of the criteria the Contractor shall immediately roll back to the previous working configuration.

M 3.4.7.4 The Contractor shall provide SNMP read-only access to all network elements in the terrestrial core network infrastructure.

M 3.4.7.5

The Contractor shall provide the Commission, wherever applicable, login access to the network elements in the terrestrial core network with the capability to extract directly all details on the operational status of a particular element including but not limited to: active configuration, environmental parameters, traffic levels, errors, routing information, counters, security parameters, uptime and inventory.

M 3.4.7.6 The Commission shall reserve the right to audit the design and configuration of the

Page 43 of 116 12/02/016


entire terrestrial core network infrastructure including all of its subsystems. The Contractor shall deliver all of the information requested by the Commission as part of the audit within 3 working days of receiving the request.

3.4.8. Terrestrial Core Network Documentation

M 3.4.8.1The Contractor shall submit to the Commission for review and approval all terrestrial core network design documentation together with the test acceptance plan prior to implementation.

M 3.4.8.2 Prior to deployment the Contractor shall submit to the Commission the configuration of all network elements in the terrestrial core network.

M 3.4.8.3The Contractor shall submit to the Commission all user manuals, specifications and any other relevant vendor documentation for all subsystems in the terrestrial core network.

3.5. Teleport Infrastructure

Special emphasis is put on the redundancy and resiliency of the teleport infrastructure because the failure of a component within it would have a significant impact on the Commission.

M 3.5.1 The Contractor shall provide all of the teleport infrastructure necessary to connect all satellite remote sites to the IDC and the backup IDC.

M 3.5.2 Prior to the deployment into service the teleport infrastructure shall pass all agreed acceptance tests and demonstrate full compliance with all requirements.

M 3.5.3The Contractor shall provide as part of the bid sufficient documentation in the High Level Design to demonstrate that the teleport infrastructure and all of its associated subsystems have sufficient redundancy and resiliency built in such that they can achieve the required availability figures and have no single point of failure.

M 3.5.4The Contractor shall provide as part of the bid sufficient documentation in the High Level Design to demonstrate that the teleport infrastructure is scalable and can easily accommodate future growth.

M 3.5.5 The entire teleport infrastructure and all of its associated subsystems shall be included in the business continuity and disaster recovery planning.

M 3.5.6 The Contractor shall maintain sufficient cold spares on site in order to establish redundancy in a timely manner in case of teleport component failure.

M 3.5.7All elements and subsystems of the teleport infrastructure shall be monitored and whenever possible integrated with the NMS system specified in Section 3.7 (Network Management System).

M 3.5.8The Contractor shall deploy all the layered security mechanisms in the teleport infrastructure necessary to ensure confidentiality, integrity, availability and compliance with Section 3.14 (Security).

M 3.5.9The teleport infrastructure hardware and software shall be covered by appropriate support contracts throughout the operating life of the system. The Commission reserves the right to audit these contracts on an ad hoc basis.

M 3.5.10The Contractor shall maintain the hardware and software for the teleport infrastructure and ensure that the hardware and software are supported and can be maintained as part of vendor support contracts.

M 3.5.11 The Contractor shall report to the Commission at least 6 months in advance when teleport infrastructure hardware and software subsystems are reaching end of life

Page 44 of 116 12/02/016


or end of support and present an upgrade plan to the Commission for review and approval.

M 3.5.12The Contractor shall provide to the Commission for review and approval a Disaster Recovery Plan for the teleport infrastructure before the GCI network enters into operation.

M 3.5.13 The Contractor shall have the necessary HVAC and fire protection facilities.

3.5.1. Antenna and RF Subsystems

M 3.5.1.1All the elements in the Antenna RF chains shall be fully redundant and the contractor shall provide all the necessary documentation in the High Level Design Document proving compliance.

M 3.5.1.2 The contractor shall have a spare antenna on site or an antenna in a backup teleport able to take over service in case of antenna failure for any of the regions.

M 3.5.1.3 Wherever applicable the Contractor shall have spare antenna control units (ACUs).

D 3.5.1.1 Redundant teleports with site diversity shall be considered an advantage.

D 3.5.1.2 Teleport antennas with high figures of merit are considered an advantage because of cost efficiencies and scalability considerations.

3.5.2. Hub and Teleport Local Network Infrastructure

M 3.5.2.1All the elements in the Teleport Hub and Local Network Infrastructure and its associated subsystems shall be fully redundant and the Contractor shall provide in the High Level Design Document all documentation necessary to prove compliance.

M 3.5.2.2The Contractor shall monitor all the elements of the Teleport Hub and Local Network Infrastructure and the Commission shall have access to the monitoring data.

M 3.5.2.3The Teleport Hub and Local Network Infrastructure shall support the transport of Internet Protocol version 4 (IPv4) data, including all underlying protocols and ports between all connected locations.

M 3.5.2.4The Teleport Hub and Local Network Infrastructure shall support the transport of Internet Protocol version 6 (IPv6) data, including all underlying protocols and ports between all connected locations.

M 3.5.2.5The Teleport Hub and Local Network Infrastructure shall support the effective transport of IPv4 and IPv6 multicast data including all underlying protocols and ports between all connected locations.

M 3.5.2.6The Contractor shall implement QOS in the Teleport Hub and Local Network Infrastructure using at least five traffic classes in accordance with the specifications provided by the Commission

M 3.5.2.7 Each traffic class shall have its bandwidth capacity enforced and guaranteed.

M 3.5.2.8 Any unused bandwidth shall be made available to other traffic classes on a best effort basis.

M 3.5.2.9 The Teleport Hub and Local Network Infrastructure shall preserve the QOS markings unless a policing and mark down mechanism has been previously agreed with the Commission. Should such a mechanism be agreed the QOS marking

Page 45 of 116 12/02/016


change shall be made in accordance with the specific agreement.

M 3.5.2.10 Any RED QOS mechanisms in the terrestrial core network shall be reviewed and approved by the Commission prior to implementation by the Contractor.

3.5.3. Terrestrial Core Network and Backup Internet Connectivity

M 3.5.3.1 All the Teleports shall have redundant and physically diverse connections to the Terrestrial Core Network Infrastructure.

M 3.5.3.2 All the teleports shall have the backup connectivity to the Internet independent of the Terrestrial Core Network infrastructure.

M 3.5.3.3The interconnection between teleport and the Terrestrial Core Network shall be fully redundant. The network elements shall be redundant and connect to both the main terrestrial core network infrastructure and the Internet backup infrastructure.

M 3.5.3.4

Both the Terrestrial Core Network Infrastructure connection and the teleport Internet connection shall have sufficient capacity in order to accommodate all the required services and provide sufficient margin for growth. The contractor shall provide all the necessary documentation in the High Level Design Document proving compliance.

D 3.5.3.1 It is desirable that the Teleport circuits connecting to the Terrestrial Core Network terminate on different and physically diverse service provider POPs.

D 3.5.3.2 Connectivity of the teleport to multiple telecommunication service providers and carriers is considered an advantage.

3.5.4. Teleport Supporting Infrastructure and Personnel

M 3.5.4.1The contractor shall have in place all the necessary on call support personnel in order to be able to restore service in a timely fashion in case of outage and meet the availability requirements.

M 3.5.4.2

The teleport infrastructure shall have a highly resilient power supply system including but not limited to:

Teleport equipment shall be connected to redundant UPS systems. The UPS system shall be backed up by redundant generators and/or local

power plants with automatic transfer switch. The UPS system shall have enough capacity to permit the generators and/or

local power plants to kick in.The teleport shall have enough fuel supply on site for the generators and/or local power plants in order to guarantee continuity of service during extend power outages.

M 3.5.4.3

The Contractor shall have all necessary physical and logical security measures in place including but not limited to:

Perimeter fence, gates and barriers, Access control, Video surveillance, Alarm systems.

D 3.5.4.1 It is desirable that the personnel in the teleport teams of the Contractor will have up to date and relevant industry specific certifications.

D 3.5.4.2 It is highly desirable that the teleports are manned 24/7.

Page 46 of 116 12/02/016


D 3.5.4.3 It is desirable that the teleport is connected to independent commercial power sources/providers.

D 3.5.4.4 It is desirable that the teleports have 24/7 manned security on site.

3.5.5. Space Segment

M 3.5.5.1The Contractor shall provision sufficient satellite capacity in order to meet the requirements of the Commission and accommodate future growth. The Contractor shall provide sufficient documentation in the High Level Design, as part of the bid, in order to demonstrate compliance.

M 3.5.5.2The Contractor shall provision exclusively non-pre-emptible and restorable satellite capacity for the GCI network. The Contractor shall provide sufficient documentation in order to demonstrate compliance.

M 3.5.5.3 The Contractor shall provision the initial satellite capacity on satellites with at least 3 years of expected lifetime left.

M 3.5.5.4Should a satellite approach its expected end of life during the GCI lifetime the Contractor shall make all arrangements necessary to transfer the service to a different satellite in a timely manner and minimize the impact on GCI availability and service.

D 3.5.5.1 The employment of easy to license satellite frequencies or pre-existing licences shall be considered an advantage.

D 3.5.5.2 The use of advance modulation techniques and error correction mechanisms shall be considered an advantage.

D 3.5.5.3 The use of adaptive coding modulation is desirable.

D 3.5.5.4 The implementation of jamming resistant coding techniques such as CDMA is highly desirable and shall be considered an advantage.

3.6. Remote Sites

The scope of this section is the definition of requirements for remote sites.

Special emphasis is put on the redundancy and resiliency of the remote sites because many of them are in remote and environmentally harsh environments and long term failures of the connectivity of these sites have a significant impact on the Commission’s delivery of data.

3.6.1. Licensing and Regulatory Compliance

Depending on the proposed solution, some of the licences may be reused but the expectation is that the majority of licences will not be applicable. The Contractor shall be required to obtain local frequency licences from regulatory authorities on behalf of the Commission, where applicable.

It shall be noted that the Commission has a licence fee exemption in certain States Signatories.

M 3.6.1.1

The Contractor shall be responsible to prepare and submit all necessary licencing and regulatory information in accordance with the local laws, rules and regulations of the individual States Signatories and their telecommunications authorities. Where English is not an official language the application shall be submitted in the local official language.

M 3.6.1.2 The Contractor shall be the sole party responsible for obtaining all the necessary licences and permits to import, possess, install and operate all GCI equipment.

Page 47 of 116 12/02/016


M 3.6.1.3The Contractor shall be the sole party responsible for maintaining and renewing all licences and permits throughout the duration of the contract as well as all possible extensions in accordance with local laws and regulations, including the timelines for such renewal.

M 3.6.1.4The Contractor shall be the sole party responsible for homologation testing, type approval testing and any other necessary certification for the GCI equipment including all of the associated costs.

M 3.6.1.5The licensing and regulatory process may be lengthy in certain States Signatories. The Contractor shall be the sole party responsible for the timely completion of the licensing and regulatory process which shall be completed prior to the starting of migration for the respective remote site.

M 3.6.1.6The Contractor shall have demonstrated experience with the licencing and regulatory rules in the Commission’s States Signatories and shall be able to start the licencing process immediately after the Effective Start Date of the Contract.

M 3.6.1.7

Failure of the Contractor to migrate an existing site or to commission a new site within the required period as a result of not obtaining the necessary permits and licences shall result in the application of SLA penalties, including a continuous outage penalty, starting on the agreed commissioning date. If the Contractor implements at its own expense an alternative technology or service which is compliant with the requirements of the Commission until the licensing process is complete, the Commission may decide to waive the SLA penalties.

M 3.6.1.8Wherever possible the frequency licences shall be obtained in the name of the Commission. Where it is not possible to obtain the licence in the name of the Commission the licence shall be obtained in the name of local operator or the Contractor in accordance with local rules and regulations.

M 3.6.1.9

The Commission has been granted exemptions for licence fees, other tariffs and import duties in many of its States Signatories. Should licensing fees be nevertheless required they will be reimbursed by the Commission upon presentation of the proof of payment. Only fees directly related to the licence itself will be reimbursed. Associated administrative costs shall not be reimbursed. The Contractor shall make the necessary payments and shall receive reimbursement for the licensing fees only upon presentation of the appropriate documentation and provided that the Commission has given prior approval to the application and fees.

M 3.6.1.10

If necessary and if requested by the Contractor in exceptional cases, the Commission may unilaterally decide to provide assistance to the Contractor during the licensing process provided that the Contractor submits the request with appropriate documentation at least one month in advance. The responsibility for obtaining the licences and permits remains with the Contractor.

M 3.6.1.11The Contractor shall inform the Commission of any licensing issue with the potential to delay or block GCI network delivery or operation. The Contractor shall notify the Commission in writing via an exception report and update the licence section of the Risk Register accordingly.

M 3.6.1.12

The Contractor shall store all licence documentation in an online and interactive version-controlled document management system which shall be available to the Commission at all times. The system shall be capable of providing status reports on demand for one or more selected States Signatories or one or more selected remote sites.

Page 48 of 116 12/02/016


3.6.2. Logistics and Strategic Deployment Stock

The logistics and sparing strategies are very important for the Commission given the global distribution of the GCI network and the requirement of continuous operations for the International Monitoring System.

The Commission has customs fee exemption in some States Signatories and it is expected that the Contractor shall make full use of this benefit by applying for all associated exemptions.

M 3.6.2.1 The Contractor shall be the sole party responsible for the end to end logistics and shipping of materials with regard to all GCI aspects as well as all associated costs.

M 3.6.2.2

The Contractor shall be responsible for preparing and submitting all the necessary regulatory information and documentation of conformity and adhere to all import/export procedures in accordance with local laws, rules and regulations of the host countries for the remote sites. Where English is not an official language, the documentation shall be submitted in the local official language or the language accepted by the applicable agency.

M 3.6.2.3The Contractor shall coordinate, cooperate and follow the instructions of the representatives of the Commission and station operators with regard to logistics and shipping activities whenever necessary or as requested by the Commission.

M 3.6.2.4The import/export process may be lengthy in certain States Signatories. The Contractor shall be the sole party responsible for the timely completion of the logistics, shipping, import/export and custom clearances and should factor in sufficient lead time for the successful completion of the process.

M 3.6.2.5The Commission has exemptions for custom duties and other taxes in many of the States Signatories. The Contractor shall apply for exemption of customs duties and taxes on the basis of the status of the Commission.

M 3.6.2.6

Should import fees nevertheless be required, they will be reimbursed by the Commission upon presentation of the proof of payment. Such actual fees shall not be burdened with any administrative costs. The Contractor shall make all necessary payments and shall receive reimbursement for customs fees only upon presentation of appropriate documentation and provided that the Commission has received information on the fees and given its prior approval.

M 3.6.2.7

In certain States Signatories, it may be necessary to donate equipment to local institutions and/or the representatives of the Commission within the host country in order to be exempt from customs taxes. Upon the request of the Commission the Contractor shall make the respective donation in accordance with the local rules and regulations.

M 3.6.2.8

The Contractor shall have extensive experience with the logistics, shipping, import/export rules and other related regulations in States Signatories. The Contractor shall initiate the logistics and shipping process immediately after the Effective Start Date of the Contract. This is especially important as some sites are located in remote locations that are difficult to access.

M 3.6.2.9

Failure of the Contractor to migrate an existing site or to commission a new site within the required period as a result of shipping, logistics and import/export processes shall result in the application of SLA penalties, including a continuous outage penalty, starting on the agreed commissioning date. If the Contractor implements at its own expense an alternative technology or service which is compliant with the requirements of the Commission until the shipping, logistics and import/export processes are completed the Commission may decide to waive the SLA penalty.

M 3.6.2.10 Subsequent to a timely request by the Contractor, the Commission may in

Page 49 of 116 12/02/016


exceptional cases unilaterally decide to provide assistance to the Contractor for logistics, shipping, import/export processes and custom clearances. The Contractor remains solely responsible for the end to end logistics and shipping of materials.

M 3.6.2.11

The Contractor shall inform the Commission of any logistics, shipping, import/export, custom clearance process or any other related activity with the potential to delay or block GCI network delivery or operation. The Contractor shall inform the Commission in writing via an exception report and update the Risk Register accordingly.

M 3.6.2.12The Contractor shall track all shipment and logistics activities in an online interactive tracking system and make the tracking information available to the Commission at all times.

M 3.6.2.13The Contractor shall prepare weekly logistics and shipment reports. These reports shall be placed in a version controlled document management system which shall be available to the Commission at all times.

M 3.6.2.14 The Contractor shall integrate the logistics and shipment tracking system with the internal trouble ticketing system of the Commission (currently JIRA based).

M 3.6.2.15 The Contractor shall insure all shipments against theft, loss or damage within transit.

M 3.6.2.16

Prior to shipment it is the sole responsibility of the Contractor to: Test the equipment; Label the equipment in conformity with standards to be provided by the

Commission; Pack the equipment in suitable containers; Prepare the bill of materials and any other required documentation; Exercise due diligence with regard to shipment and logistics.

M 3.6.2.17The Contractor shall maintain sufficient spares in a Strategic Deployment Stock to ensure immediate shipment and comply with the requirements of the Commission with regard to the restoration of spares and the restoration of redundancy.

M 3.6.2.18

The Contractor shall present to the Commission for review and approval a Sparing Strategy Document prior to the start of the migration phase which shall include but is not limited to:

Composition of the Strategic Deployment Stock; Replenishment threshold for the Strategic Deployment Stock; Failure rate analysis for different components; Risk analysis with regard to sparing.

M 3.6.2.19 The Contractor shall report the status of the spares and the composition of the GCI strategic deployment stock on a monthly basis or on demand by the Commission.

3.6.3. Remote Station Redundancy and Resiliency

M 3.6.3.1The remote site network infrastructure shall be fully redundant by itself and be designed without any single point of failure. This shall include both redundant links and redundant network elements to automatically restore service in case of failure.

M 3.6.3.2 All satellite remote sites shall have a reliable satellite based link which shall act as a primary link unless otherwise specified by the Commission.

M 3.6.3.3 For the satellite remote sites, whenever possible the Contractor shall implement a backup Internet VPN connection, compliant with the specifications in Section 3.14 (Security). The Internet VPN backup shall be implemented wherever an Internet connection is available on site or is possible to procure. The Contractor shall be

Page 50 of 116 12/02/016


obliged to pursue multiple technical solutions with regard to the local Internet connection including for example:

xDSL, FTTH, Cable Internet, 3G/GPRS/UTMS/HSPA/LTE, WiMAX, PSTN/ISDN, Other emerging technologies.

The Contractor shall be responsible for all costs associated with the installation, maintenance and operation of the backup Internet link throughout the duration of the contract.

M 3.6.3.4 The Commission shall allocate one or more IPv4 addresses for the use of the Contractor in order to terminate Internet backup and IP VPN connectivity.

M 3.6.3.5Internet connectivity may already be present at some of the remote sites. The Commission and/or its representatives may, on a case by case basis, make this available to the Contractor at no cost, in order to implement the backup Internet VPN connection.

M 3.6.3.6In the case of failure of the primary link traffic shall be automatically routed to the backup link. When the primary link is restored the traffic shall be automatically routed through the primary link.

M 3.6.3.7The Contractor shall provide the Commission a list of all necessary ports and protocols to be allowed through the firewall for the IPv4 and IPv6 addresses specified in article M 3.6.3.4.

M 3.6.3.8The Internet connection specified in article M 3.6.3.5 is provided on a best effort basis. If the satellite link fails and if the Internet connection is not available or does not meet SLA specifications as defined in Section 4 (Service Level Agreement), the Contractor shall be subject to penalties.

M 3.6.3.9

Wherever it is not possible to deploy Internet connectivity at a remote site, the Contractor shall implement a different technology for the redundant connection, such as:

BGAN; VSAT connection; SCPC; Leased line; MPLS.

The Contractor may also implement such a technology as an alternative to an Internet VPN backup.

M 3.6.3.10

The remote site network shall be designed and implemented to ensure that the convergence time (time necessary to restore operational traffic) in the event of failure of a single network element or link shall be no longer than 5 minutes. The Contractor shall submit to the Commission for review and approval a validation test plan demonstrating compliance.

M 3.6.3.11Wherever the Contractor is implementing a secondary VSAT as a backup link it shall be independent of the primary VSAT and no single point of failure shall be present.

D 3.6.3.1It is highly desirable that wherever the Contractor is implementing a secondary VSAT as a backup link for business continuity purposes the secondary link will use a different satellite and/or teleport.

Page 51 of 116 12/02/016


M 3.6.3.12In addition to the online prime and standby elements of the remote site network, the Contractor shall have at least 1 cold spare for each network element at every site in order to be able to restore redundancy in a timely fashion.

M 3.6.3.13The Contractor shall maintain the cold spares mentioned in article M 3.6.3.12 and ensure that they are up to date with configuration and software changes or be able to update them remotely whenever a spare is replaced.

M 3.6.3.14The remote site network hardware and software shall be covered by appropriate support contracts through their operating lifetime. The Commission reserves the right to audit these contracts on an ad hoc basis.

M 3.6.3.15The Contractor shall report to the Commission at least 6 months in advance when remote site network hardware and software subsystems are reaching end of life or end of support and present an upgrade plan to the Commission for review and approval.

M 3.6.3.16 The Contractor shall provide to the Commission for review and approval a generic Disaster Recovery Plan for the remote sites before the network enters operation.

M 3.6.3.17 For specific sites, as mentioned in the Site Profile Table, only an Internet VPN connection will be required.

M 3.6.3.18 For Internet VPN connections articles M 3.6.3.12 and M 3.6.3.13 regarding cold spares apply as well.

3.6.4. Local Infrastructure and Environmental Conditions

M 3.6.4.1With regard to the GCI equipment at remote sites, the Contractor shall comply with all relevant local rules and regulations including but not limited to those pertaining to installation, equipment standards, disposal, health and safety.

M 3.6.4.2 In addition to the local rules and regulations specified in article M 3.6.4.1 the Contractor shall comply with industry health and safety best practices.

M 3.6.4.3

Given the global distribution of the GCI network some of the remote sites operate in environmentally harsh conditions including but not limited to:

High temperature (e.g. deserts, jungle); Low temperature (e.g. artic conditions); High altitude; High humidity (e.g. jungle); High wind conditions; High salinity; High precipitation (e.g. snow and rain); Locations exposed to lightning.

It is the sole responsibility of the Contractor to provide suitable indoor and outdoor equipment, on a case by case basis, that will be able to operate in the environmental conditions at the remote site.

M 3.6.4.4The Contractor shall deliver as part of the bid an analysis of the environmental conditions at remote sites. The analysis shall propose equipment that is suitable to the specific environmental conditions in extreme environments.

M 3.6.4.5Should equipment fail or the service not meet the SLA criteria owing to local environmental operating conditions, the Contractor shall not be exempt from SLA penalties.

M 3.6.4.6It is the sole responsibility of the Contractor to deploy, wherever needed, additional equipment to sustain operation under local environmental conditions on the basis of the analysis specified in article M 3.6.4.4.

Page 52 of 116 12/02/016


M 3.6.4.7The Contractor shall deliver as part of the project planning phase a detailed plan for deploying the extra equipment mentioned in article M 3.6.4.6 for review and approval by the Commission. The plan shall address the specific environmental conditions at each remote site.

M 3.6.4.8

The equipment mentioned in article M 3.6.4.6 shall include but is not limited to: De-icing equipment; Radomes; High wind antennas; Corrosion resistant mounts and antennas; Animal deterrent kits and measures; Lightning protection equipment; Armoured and shielded cables; Equipment enclosures; Other ruggedized equipment.

M 3.6.4.9

The Site Profile Table includes information on some of the additional equipment as specified in article M 3.6.4.8 that is currently installed at the remote sites. The Contractor may choose to take into consideration this additional information in terms of local operating conditions. However, it is the sole responsibility of the Contractor to make its own determinations and deploy suitable equipment and measures for the remote sites.

M 3.6.4.10On the basis of the lessons learned during the installation and operation of GCI III the Contractor shall update, enhance or deploy new equipment, as mentioned in article M 3.6.4.8, throughout the duration of the contract.

M 3.6.4.11Some of the remote sites do not have heating, ventilation and air conditioning (HVAC) systems or have HVAC systems that are unreliable. The Contractor shall ensure that all indoor GCI equipment is installed with proper ventilation.

M 3.6.4.12 The Contractor shall provide all necessary connectors, adaptors and power cables for GCI equipment in accordance with the conditions at each remote site.

M 3.6.4.13The indoor GCI equipment shall be delivered with rack mounting kits and wherever an equipment rack is available at the remote site the Contractor shall install the equipment in accordance with the instructions of the Commission and/or its representatives.

M 3.6.4.14The Contractor shall install, maintain and operate the GCI equipment in compliance with industry best practices and standards and take into consideration that some sites are remote and very difficult to access.

D 3.6.4.1Given the remoteness of some sites it is highly desirable that the Contractor install de-icing equipment at all remote sites where snowfall may occur, unless a radome is installed.

M 3.6.4.15

Depending on the selected GCI solution some of the radomes which are already installed at remote sites may be reused by the Contractor. The decision to do so shall be taken on a case by case basis with the agreement of the Commission. However, it is the sole responsibility of the Contractor in such cases to ensure that the radomes are in good working condition and suitable to the proposed GCI solution for the duration of the contract.

M 3.6.4.16 It is the responsibility of the Contractor to ensure that all GCI equipment is properly grounded in accordance with vendor specifications.

M 3.6.4.17 The Contractor shall install lightning arrestors for the IF/RF cables to prevent damage to the connected electronic devices from lighting or related incidents.

Page 53 of 116 12/02/016


M 3.6.4.18The Contractor shall install reliable surge protection with adequate grounding for the GCI equipment at remote sites to prevent damage to the equipment from power and lightning related hazards, including but not limited to overvoltage, spikes and surges.

D 3.6.4.2It is desirable that the Contractor considers additional lightning and surge protection in addition to the protection measures described in articles M 3.6.4.16, M 3.6.4.17 and M 3.6.4.18 (e.g. lightning and surge protection for RJ45 cables).

D 3.6.4.3

The electrical power at some remote sites is supplied by generators or by unfiltered and unregulated commercial power sources. Therefore, it is desirable that the Contractor considers installing automatic voltage regulators as needed. The decision to do so shall be taken on a case by case basis with the prior agreement of the Commission.

M 3.6.4.19Remote sites have DC or AC power infrastructure. The power infrastructure for each remote site is included in the Site Profile Table. The Contractor shall provide DC or AC powered equipment that is suitable to operate under the existing power infrastructure at each remote site.

M 3.6.4.20

It is expected that at the start of the migration to GCI III the majority of remote sites will retain their AC or DC specification as described in the Site Profile Table. However, the specifications will be reviewed as part of project planning phase and updated as necessary. The Contractor shall deploy the equipment for the remote sites in accordance with the updated specifications.

M 3.6.4.21The local power infrastructure for a remote site may change during the lifetime of the GCI. The Contractor shall change its equipment accordingly upon the request of the Commission.

M 3.6.4.22Typically the remote sites with DC power infrastructure provide a voltage range of 12-48 volts. However, in special cases the voltage may be outside this range. The Contractor shall provide all power conversion equipment necessary to adjust the voltage to the GCI equipment requirements.

M 3.6.4.23Two units of the conversion equipment mentioned in article M 3.6.4.22 shall be deployed in operation: one powering the primary chain of GCI equipment and another powering the redundant chain of GCI equipment to avoid a service outage in the event of failure of conversion equipment.

M 3.6.4.24In addition to the active power conversion equipment specified in articles M 3.6.4.22 and M 3.6.4.23 the Contractor shall maintain a cold spare on site for the purpose of timely redundancy restoration.

D 3.6.4.4 It is highly desirable that the equipment specified in articles M 3.6.4.22, M 3.6.4.23 and M 3.6.4.24 is commercially available as an off the shelf product.

M 3.6.4.25 As part of the bid the Contractor shall quantify the expected average and maximum power consumption for the GCI equipment at a DC remote site.

M 3.6.4.26 The Commission may choose to unilaterally waive the active redundancy requirement in order to conserve power for a very small number of remote sites, especially remote sites using solar power. Such a decision shall be taken by the Commission on a case by case basis. The Contractor shall implement initially only a non-redundant link upon the request of the Commission. Following an infrastructure upgrade the Commission may require the Contractor to implement an active redundancy strategy in accordance with Section 3.6.3 (Remote Station Redundancy and Resiliency) and the Contractor shall comply with such a request

Page 54 of 116 12/02/016


from the Commission.

M 3.6.4.27The Contractor shall provide an analysis, as part of the High Level Design, with regard to the proposed GCI equipment power consumption and its compliance with article M 3.6.4.25.

D 3.6.4.5The employment of equipment with an average power consumption that is considerably less than the specification in article M 3.6.4.25 will be considered an advantage.

M 3.6.4.28Typically the remote sites with AC power operate in accordance with the power standards and specifications of the host country. The Contractor shall be the sole party responsible for ensuring that equipment operates in accordance with local power conditions.

D 3.6.4.6

The electrical power at some remote sites is supplied by generators or by unfiltered and unregulated commercial power sources. Therefore it is desirable that the Contractor considers installing automatic voltage regulators as needed. The decision to do so shall be taken on a case by case basis with the prior agreement of the Commission.

M 3.6.4.29 As part of the bid the Contractor shall quantify the expected average and maximum power consumption for the GCI equipment at a remote site.

M 3.6.4.30Most of the remote sites will be provided with a station UPS at the start of migration. However, this is not always the case. Therefore whenever required by the Commission the Contractor shall provide a single UPS in accordance with the specifications in articles M 3.6.4.32 to M 3.6.4.37. No redundant UPS is required.

M 3.6.4.31The Commission shall provide during the project planning phase an initial list of sites where a UPS in accordance with articles M 3.6.4.32 to M 3.6.4.37 shall be required. The Contractor shall deploy UPSs in these sites in accordance with specifications.

M 3.6.4.32

The Contractor shall offer three types of UPS for remote sites: A UPS that is able to maintain the operation of the GCI equipment for at least

2 continuous hours from the starting time of the power outage; A UPS that is able to maintain the operation of the GCI equipment for at least

6 continuous hours from the starting time of the power outage; A UPS that is able to maintain the operation of the GCI equipment for at least

12 continuous hours from the starting time of the power outage.Should the UPS fail to provide power to the GCI equipment in accordance to the specified backup time the resulting GCI service outage up to the required backup time shall be subject to penalties.

M 3.6.4.33 The UPS shall restore its operation automatically following a power outage without the need for manual intervention.

D 3.6.4.7 It is highly desirable that the UPS has the capability to detect anomalous power conditions and provide reliable continuous power to the GCI equipment.

M 3.6.4.34The Contractor shall have enough spare UPSs and battery packs in the Strategic Deployment Stock and replace UPSs and battery packs when they no longer meet the required backup time specified in article M 3.6.4.32.

M 3.6.4.35 The Commission shall specify the UPS requirements for newly installed sites or

Page 55 of 116 12/02/016


changes in the UPS requirements for existing sites. The Contractor shall comply with requests of the Commission to install, uninstall or upgrade UPSs and battery packs.

M 3.6.4.36 The Contractor shall connect all primary GCI equipment (usually the VSAT chain) either to the IMS station UPS or to the UPS provided by the Contractor.

M 3.6.4.37The Contractor shall connect all standby equipment to commercial power and/or generator, whenever available, in order to avoid single points of failure and minimize the energy draw from UPS batteries.

D 3.6.4.8It is highly desirable that the Contractor provide at every remote site a remotely controllable power distribution unit in order to be able to power cycle individual equipment remotely. Such remotely controllable power distribution units shall be in compliance with the security requirements defined in Section 3.14 (Security).

3.6.5. Satellite Outdoor Subsystem

M 3.6.5.1 The Contractor shall install all satellite communication subsystems at remote sites in accordance with local rules and regulations.

M 3.6.5.2

Depending on the proposed solution, the satellite outdoor subsystem and components at a remote site may include but are not to limited to:

Antenna reflector; Antenna mount; Antenna feed horn and covers; OMT; Wave guides; Power amplifier; BUC; LNA/LNB; RF filters; IF filters; IFL cables; Connectors; Installation kits.

M 3.6.5.3With the exception of the antenna mount and antenna reflector the Contractor shall maintain cold spares on site for all satellite subsystems/components as mentioned in article M 3.6.5.2.

M 3.6.5.4The Contractor shall have enough antenna reflectors and antenna mounts readily available in the Strategic Deployment Stock in order to achieve timely restoration of service and/or redundancy following antenna damage.

D 3.6.5.1 Remote site antennas with high figures of merit are considered an advantage because of cost efficiency and scalability considerations.

D 3.6.5.2 The use of LNA/LNB with low noise values at the remote site is considered an advantage.

M 3.5.1.5The Contractor shall provide BUCs at remote sites with sufficient power margin in order to ensure suitable uplink power control, adaptive coding modulation (where applicable) and to accommodate future capacity expansions.

M 3.5.1.6 Wherever a dual VSAT solution is employed, the Contractor shall ensure that the risk of a common failure is minimized by adhering to industry best practices and

Page 56 of 116 12/02/016


standards, including but not limited to: Running the IFL cables via physically diverse paths; Maintaining sufficient spatial diversity between antennas; Using different satellites wherever possible.

M 3.5.1.7 Antennas and indoor equipment shall use common grounding wherever possible.

M 3.5.1.8 Wherever possible the antennas at remote sites shall be deployed in such a manner that they are shielded from the prevailing winds.

M 3.5.1.9 It is the sole responsibility of the Contractor to suitably weather-seal and waterproof all cables, connectors and feed horns using suitable and UV resistant materials.

M 3.5.1.10The Contractor shall have available on site sufficient spare weather-sealing and waterproofing materials (including feed covers and gaskets) as described in article M 3.5.1.9.

M 3.5.1.11 The Contractor shall provide suitable cables and connectors taking into account local environmental conditions.

D 3.6.5.3 It is desirable to employ suitable radomes or high wind antennas in locations with very high winds (e.g. arctic conditions).

M 3.5.1.12 The Contractor shall deploy RF and/or IF filters wherever needed in order to mitigate local radio interference at the remote sites.

M 3.5.1.13

The Site Profile Table provides information on remote sites where RF/IF filters are currently installed. The Contractor may choose to take into consideration this additional information in terms of local operating conditions. Depending on the proposed solution and the frequency bands to be used, this information may not be applicable. It is the sole responsibility of the Contractor to make its own determinations and deploy suitable RF/IF filters and other measures (e.g. physical shielding).

M 3.5.1.14 The Contractor shall have RF and IF filters spares on site wherever applicable.

3.6.6. Routing and Remote Site Network

M 3.6.6.1The Contractor shall provide all necessary end to end connectivity and routing between the remote sites, the IDC and the backup IDC (if applicable) in accordance with the requirements.

M 3.6.6.2 The remote site network infrastructure shall employ only non-proprietary routing and first hop redundancy protocols.

M 3.6.6.3The GCI network equipment shall interface with remote stations using RJ45 Ethernet connectivity to the local infrastructure. The RJ45 connectivity shall support 10/100 Mbps full duplex connectivity with auto-negotiation in accordance with the relevant IEEE 802.3 standards.

M 3.6.6.4 The GCI interface specified in article M 3.6.6.3 shall support auto medium dependent interface crossover (MDI-X).

M 3.6.6.5The GCI interface specified in article M 3.6.6.3 shall provide at least 8 ports for station connectivity excluding any GCI contractor devices and components. The ports shall be equally divided between the primary and standby routers.

M 3.6.6.6 In the case of router redundancy failure the Contractor shall be able to provide at least 6 ports for station connectivity until redundancy is restored.

M 3.6.6.7 The Contractor shall support Ethernet switching functionality for the access ports

Page 57 of 116 12/02/016


mentioned in articles M 3.6.6.3 to M 3.6.6.6.

M 3.6.6.8

The switching functionality as specified in article M 3.6.6.7 shall be able to support the following features, as applicable:

VLAN access port allocation; 802.1q VLAN trunking; Possibility to configure multiple VLANs across the two routers; Storm control; Broadcast control; Spanning tree protocols; LACP port aggregation; Port security; VTP transparency.

M 3.6.6.9The Commission shall instruct the Contractor on the configuration and functionality of access ports as specified in article M 3.6.6.8 for individual remote sites on a case by case basis. The Contractor shall comply with instructions of the Commission with regard to the functionality and configuration of station interface ports.

M 3.6.6.10 The Commission shall provide the Contractor with the IP addressing plan. The Contractor shall comply with and implement the IP addressing plan.

M 3.6.6.11 The Contractor shall implement and maintain an IP Address Management System and update with any changes throughout the duration of the contract.

M 3.6.6.12 The IP Address Management System shall be available to the Commission at all times.

M 3.6.6.13The Commission shall provide the Contractor with the naming convention for the GCI III network. The Contractor shall comply with the naming convention as provided by the Commission.

M 3.6.6.14The network elements present at the remote site shall provide a Virtual Router Redundancy Protocol (VRRP) IP address for each of the VLANs configured in accordance with articles M 3.6.6.8 and M 3.6.6.9 to act as default gateways in each VLAN to the remote site equipment.

M 3.6.6.15The Contractor shall implement a ‘keep alive’ mechanism to detect failures in the primary or secondary redundancy chains and shall adjust the VRRP priority accordingly.

M 3.6.6.16

The Contractor shall implement all required VRRP functionality, as instructed by the Commissions, including but not limited to:

Preemption; Interface tracking; Priority; Group; Authentication (in accordance with Commission specifications); Timer adjustment.

M 3.6.6.17The Contractor shall interoperate with other VRRP cable devices at remote sites in accordance with Commission specifications on a case by case basis as required by the Commission.

M 3.6.6.18If the primary and secondary redundancy chains fail at the same time, the VRRP priority shall be reduced to the lowest value and the routes that are no longer reachable through the primary and secondary chains shall be automatically removed from the routing/forwarding table.

D 3.6.6.1 The use of non-proprietary dynamic routing protocols at remote sites is highly desirable and shall be considered an advantage. If a routing protocol is used, the

Page 58 of 116 12/02/016


Contractor shall distribute all remote site routes and any other associated GCI routes without any route summarization.

M 3.6.6.19If a dynamic routing protocol is deployed at a remote site the Contractor shall take into account the capacity of the link and optimize the routing protocol in terms of bandwidth consumption.

M 3.6.6.20In certain cases, the Commission and/or its representatives may have routing equipment at the remote site. The Contractor shall implement the associated routing and peering in accordance with Commission specifications upon request by the Commission.

M 3.6.6.21 The Contractor shall ensure that the routing information is correctly redistributed within the GCI network in compliance with the requirements.

M 3.6.6.22The Contractor shall implement policy based routing in accordance with Commission specifications upon request by the Commission and on a case by case basis.

M 3.6.6.23When requested by the Commission, on a case by case basis, The Contractor shall implement NAT in accordance with Commission specifications upon request by the Commission and on a case by case basis.

M 3.6.6.24 The remote site GCI network shall support the transport of Internet Protocol version 4 (IPv4) data, including all underlying protocols and ports.

M 3.6.6.25 The remote site GCI network shall support the transport of Internet Protocol version 6 (IPv6) data, including all underlying protocols and ports.

M 3.6.6.26 The remote site GCI network shall support the effective transport of IPv4 and IPV6 multicast data including all underlying protocols and ports.

M 3.6.6.27The backup internet connectivity, as defined in Section 3.6.3 (Remote Station Redundancy and Resiliency), shall be encrypted and secured in accordance with the specifications in Section 3.14 (Security).

M 3.6.6.28The Contractor shall support the implementation of backup VPN connectivity as defined in Section 3.6.3 (Remote Station Redundancy and Resiliency), using either statically or dynamically assigned IP addresses at the remote site in accordance with the Commission’s request.

M 3.6.6.29The Contractor shall support the implementation of backup VPN connectivity, as defined in Section 3.6.3 (Remote Station Redundancy and Resiliency), that is capable of using NATed IP addresses including private IP addresses in accordance with RFC1918.

D 3.6.6.2 The employment of dynamic multipoint tunnelling protocols is desirable.

D 3.6.6.3 The employment of performance based edge routing optimization is desirable.

3.6.7. Capacity, Performance and Quality of Service

The GCI network capacity, performance and QOS aspects are very important to the Commission given the mission criticality and timeliness aspects of the International Monitoring System data, products and maintenance activities.

M 3.6.7.1 The Contractor shall be the sole party responsible for meeting specifications with regard to capacity, performance and QOS for the GCI network.

M 3.6.7.2 The Contractor shall provide in the High Level Design Document an end to end QOS architecture which shall include all specific details for all remote sites.

Page 59 of 116 12/02/016


M 3.6.7.3The Contractor shall provide as part of the bid sufficient documentation in the High Level Design Document to demonstrate that the remote sites and all of their associated subsystems meet the requirements for capacity, performance and QOS.

M 3.6.7.4The Contractor shall provide as part of the bid sufficient documentation in the High Level Design Document to demonstrate that the remote site infrastructure is scalable and can easily accommodate future growth.

M 3.6.7.5

The Contractor shall deploy all necessary end to end QOS mechanisms to meet the requirements of the Commission. The QOS mechanisms may include but are not limited to:

Traffic classification and marking; Layer 2 QOS mechanisms; Layer 3 QOS mechanisms; Queuing; Shaping; Policing; RED; Call admission control; Header compression; Bandwidth optimization; Other bandwidth enforcement mechanisms.

M 3.6.7.6

The Commission specifies the required minimum guaranteed bandwidth for each remote site as the committed information rate (CIR) values in the Site Profile Table. The Contractor shall ensure that at any given time and under any circumstances the bandwidth available to any remote site shall not fall below the specified CIR value.

M 3.6.7.7 The CIR is specified for both transmit and return directions and the Contractor shall meet all specifications for both cases.

M 3.6.7.8 The Contractor shall provision enough satellite capacity to support all traffic of the Commission at the defined CIR rates without congestion.

M 3.6.7.9 Failure to meet the requirements specified in articles M 3.6.7.6 to M 3.6.7.8 shall result in SLA penalties in accordance with Section 4 (Service Level Agreement).

M 3.6.7.10The Commission may adjust the CIR values for some remote sites, throughout the duration of the contract, by shifting capacity from one site to another within a region. The Contractor shall comply with the request of the Commission and shall have sufficient flexibility in its design to accommodate such requests.

M 3.6.7.11The Contractor shall have sufficient flexibility to accommodate requests from the Commission to increase capacity by at least 100% per region and be able to distribute this extra capacity to remote sites in accordance with Commission specifications.

M 3.6.7.12The Contractor shall have sufficient flexibility to accommodate requests from the Commission to decrease capacity within a region and be able to redistribute the remaining capacity to remote sites in accordance with Commission specifications.

M 3.6.7.13The Contractor shall have sufficient flexibility to accommodate requests from the Commission to add or remove new sites and be able to adjust capacity allocation accordingly.

M 3.6.7.14 The Commission specifies the burstable bandwidth rate for each specific remote site as the PIR value in the Site Profile Table.

M 3.6.7.15 The PIR is specified for both transmit and return directions to the remote site and the Contractor shall meet all specifications for both cases.

M 3.6.7.16 The Contractor shall provision sufficient satellite capacity for each inroute, outroute

Page 60 of 116 12/02/016


or region (depending on the technical solution) such that if all the sites are transmitting at their defined CIR capacity at least one of the sites shall be able to burst at least up to its PIR specification.

M 3.6.7.17Any unused bandwidth below the CIR value for a remote site shall be made available to other remote sites on the same inroute, outroute or region, (depending on the technical solution) on a best effort basis.

M 3.6.7.18As part of the High Level Design Document the Contractor shall submit to the Commission for review and approval a scalability study demonstrating how the presented solution is able to accommodate the requirements specified in articles M 3.6.7.5 to M 3.6.7.17.

M 3.6.7.19 The Contractor shall submit to the Commission for review and approval a capacity test plan demonstrating compliance with the requirements.

M 3.6.7.20

The Contractor shall implement end to end QOS at remote sites using at least five traffic classes including but not limited to:

1 Expedite Forwarding class in accordance with RFC 3246; 3 distinct Assured Forwarding classes in accordance with RFC 2597; 1 Best Effort class.

M 3.6.7.21

The allocation of traffic flows (including source and destination IP addresses, protocols and ports) to the specific traffic classes as mentioned in article M 3.6.7.20 will be provided by the Commission as part of the project planning phase. The Contractor shall implement the appropriate traffic marking and associated QOS mechanisms in accordance with Commission specifications.

M 3.6.7.22The Commission shall specify, as part of the project planning phase, the allocation of bandwidth for each traffic class at the remote sites. Each traffic class shall have its bandwidth capacity enforced and guaranteed throughout the GCI network.

M 3.6.7.23The Contractor shall implement a mark down mechanism so that traffic exceeding the allocation for its specific QOS class shall be re-marked as Best Effort and the policies for Best Effort class shall apply.

M 3.6.7.24The remote site network infrastructure shall preserve the QOS markings throughout the GCI network unless a policing and mark down mechanism has been previously agreed with the Commission.

M 3.6.7.25The remote site GCI equipment shall implement an ingress policy to strip off the QOS markings for incoming packets and re-mark it according to the traffic policy specified by the Commission unless otherwise agreed on case by case basis.

M 3.6.7.26 Any RED QOS mechanisms at remote sites shall be reviewed and approved by the Commission prior to implementation by the Contractor.

M 3.6.7.27 Should any tunnelling protocols be employed all QOS markings shall be copied over to the tunnel header.

D 3.6.7.1

It is desirable that the Contractor deploy WAN optimization functionality on the remote site routers such as, but not limited to:

TCP flow optimization/latency optimization; Compression; Data redundancy elimination/deduplication/caching.

It shall be possible to exclude and pass through certain traffic flows specified by the Commission from such WAN optimization.

M 3.6.7.28 Any deployment of TCP spoofing, PEP or WAN optimization at a remote site shall be reviewed and approved by the Commission prior to implementation by the

Page 61 of 116 12/02/016


Contractor.

M 3.6.7.29The Contractor shall not be expected to provide a VoIP service or VOIP equipment. However, the GCI network should be able to transport the VoIP data of the Commission in accordance with the requirements.

M 3.6.7.30 The GCI network shall support VoIP traffic introduced by remote sites or the IDC. None of the VoIP/RTP and signalling protocols shall be blocked in the GCI network.

M 3.6.7.31 The Contractor shall mark the VoIP/RTP and signalling traffic on the basis of specifications provided by the Commission.

M 3.6.7.32 The Contractor shall assign the VoIP traffic to the Expedite Forwarding QOS traffic class in accordance with RFC 3246.

M 3.6.7.33The Contractor shall allocate all necessary bandwidth capacity in the network to enable each remote site to support 1 call using the G.729 codec or any other VOIP codec, including protocol, signalling and encapsulation overheads. This does not imply that all remote sites will have the calls at the same time.

M 3.6.7.34The Contractor shall allocate all necessary bandwidth capacity in the network to enable at least 3 simultaneous calls using the G.729 codec or any other VOIP codec, including protocol, signalling and encapsulation overheads within the same region at the same time without quality degradation.

D 3.6.7.2 It is desirable that the Contractor implement measures in the GCI network to minimize the delay and jitter (delay variation) for VoIP traffic.

3.6.8. Remote Sites and ISNs Connected Directly to the Terrestrial Core Network

M 3.6.8.1The interface to the terrestrial core network infrastructure is defined in Section 3.4.6.2 (Terrestrial Core Network Interface with Remote Sites). The solution shall be compliant with all the associated requirements.

M 3.6.8.2In terms of redundancy and resiliency, articles M 3.6.3.1, M 3.6.3.4 to M 3.6.3.4, M 3.6.3.10 and M 3.6.3.12 to M 3.6.3.16 also apply for the remote sites and ISNs connected to the terrestrial core network.

M 3.6.8.3In terms of capacity, performance and QOS, articles M 3.6.5.1 to M 3.6.5.7, M 3.6.5.9 to M 3.6.5.11, M 3.6.5.13 to M 3.6.5.15, M 3.6.5.18 to M 3.6.5.28 also apply for the remote sites and ISNs connected to the terrestrial core network.

M 3.6.8.4In terms of routing and the station/ISN network, Section 3.6.6 (Routing and Remote Site Network) also applies for the remote sites and ISNs connected to the terrestrial core network. The solution shall be compliant with all associated requirements

3.6.9. Transportable Stations

M 3.6.9.1Upon request by the Commission, the Contractor shall provide transportable telecommunication stations (flyaway kit), to enable data communication between the IDC and a Commission field team operating in a specified location that can be anywhere in the world.

M 3.6.9.2The transportable network equipment shall interface with the local network using RJ45 Ethernet connectivity. The RJ45 connectivity shall support 10/100 Mbps full duplex connectivity with auto-negotiation in accordance with the relevant IEEE 802.3 standards.

M 3.6.9.3 The GCI interface specified in article M 3.9.6.2 shall support auto MDI-X (medium

Page 62 of 116 12/02/016


dependent interface crossover)

M 3.6.9.4 The GCI interface specified in article M 3.9.6.2 shall provide at least 8 ports for station connectivity excluding any GCI Contractor devices and components.

M 3.6.9.5 The provider shall support Ethernet switching functionality for the access ports mentioned in articles M 3.9.6.2 to M 3.9.6.4.

M 3.6.9.6

The switching functionality as specified in article M 3.9.6.5 shall be able to support the following features but is not limited to:

VLAN access port allocation; 802.1q VLAN trunking; Possibility to configure multiple VLANs across the two routers; Storm control; Broadcast control; Spanning Tree Protocols; LACP Port aggregation; Port security; VTP transparency (where applicable).

M 3.6.9.7The Commission shall instruct the Contractor, on a case by case basis, on the configuration details and functionality as specified in article M 3.6.9.6 for the access ports. The Contractor shall comply with the instructions of the Commission with regard to the functionality and configuration of transportable station interface ports.

M 3.6.9.8 The Commission shall provide the Contractor with the IP addressing plan. The Contractor shall comply and implement the IP addressing plan accordingly.

M 3.6.9.10 The Contractor shall provide cold spares for all transportable station GCI equipment.

M 3.6.9.11The Contractor shall provide a dual voltage UPS with at least 2 hours of backup time. The electrical power at the remote site shall be assumed to be unfiltered and unregulated and the Contractor shall deploy the necessary surge protection and voltage regulation measures.

M 3.6.9.12

A transportable station will normally be assembled by Commission staff and/or representatives. However, it is the responsibility of the Contractor to provide all necessary documentation, including but not limited to:

Installation manuals; Standard operating procedures; Troubleshooting guides; Health and safety instructions.

M 3.6.9.13The Contractor shall provide in a timely manner all necessary remote assistance to the Commission and/or its representatives for the commissioning, operation, maintenance and decommissioning of transportable stations as requested by the Commission.

M 3.6.9.14 The Contractor shall provide all necessary components for transportable stations (flyaway kit).

M 3.6.9.15 It shall be possible to commission or decommission a transportable station in less than 4 hours.

M 3.6.9.16 As part of the bid the Contractor shall quantify the expected average and maximum power consumption for the GCI equipment at a transportable station.

M 3.6.9.17A transportable station shall be able to provide a communication link to the IDC with a capacity ranging from 512 kbps to 4 mbps for a determined period of time. The exact capacity and time period will be specified by the Commission on a case by case basis. The Contractor shall comply with the Commission specifications.

Page 63 of 116 12/02/016


M 3.6.9.18 The Contractor shall provide the QOS mechanisms as specified by the Commission in order to be able to prioritize data and support VoIP traffic.

M 3.6.9.19The Contractor shall be able to provide a transportable station and associated satellite capacity as specified by the Commission within 1 week of a request from the Commission.

M 3.6.9.20The Contractor shall specify in the High Level Design Document the proposed solution for transportable stations and how the proposed solution meets requirements.

3.6.10. Monitoring Command and Control

M 3.6.10.1The remote site network elements shall be integrated with and continuously monitored by the NMS in accordance with Section 3.7 (Network Management System).

M 3.6.10.2 The Contractor shall provide SNMP read-only access to all network elements in the terrestrial core network infrastructure.

M 3.6.10.3The Contractor shall provide the Commission, wherever applicable, remote login access to the network elements at the remote sites with the capability to extract directly all details on the operational status of a particular element.

M 3.6.10.4

Upon request by the Commission to change the preferred active redundancy chain, the Contractor shall change all the necessary parameters of the routing and redundancy protocols including but not limited to weight, cost, priority, MED, local preference, BGP communities, distribution policies, tagging, alter AS PATH and ecmp parameters.

D 3.6.10.1It is highly desirable that the Contractor provide access for the Commission and/or a tool to allow the Commission to perform by itself, whenever needed, the action associated with article M 3.6.10.4.

M 3.6.10.5Following acceptance of a remote site all the associated network elements shall be put under configuration management and control. Change requests shall be submitted to the Commission for review and approval at least 10 working days in advance.

M 3.6.10.6Should the Commission consider the changes to the remote network to be major, it may request a full or partial re-run of the acceptance testing for the terrestrial core network infrastructure. Should this acceptance testing fail to meet all of the criteria the Contractor shall immediately roll back to the previous working configuration.

M 3.6.10.7The Commission may audit the design and configuration of the entire remote site network infrastructure including all of its subsystems. The Contractor shall deliver all of the information requested by the Commission as part of the audit within 5 working days of receiving the request.

D 3.6.10.2 It is highly desirable that the network elements at the remote sites implement not only NMS integration but local logging on the device as well.

3.6.11. Remote Site Network Documentation

M 3.6.11.1The Contractor shall submit to the Commission for review and approval all remote site design documentation together with the test acceptance plan prior to the migration of a remote site.

Page 64 of 116 12/02/016


M 3.6.11.2 Prior to migration of a remote site the Contractor shall submit to the Commission the configuration of all network elements of the remote site.

M 3.6.11.3 The Contractor shall submit to the Commission all user manuals, specifications and any other relevant vendor documentation for all subsystems at the remote sites.

M 3.6.11.4

All of the remote site related documentation shall be available to the Commission at all times. The documentation shall include but is not limited to:

Configuration files; Diagrams; Inventory details; Licence information; Support arrangements; Regulatory compliance documentation; Logistics logs and documentation; Known error database; Change management documentation; Standard operating procedures and work instructions.

3.6.12. Security

M 3.6.12.1 The remote sites shall be compliant with all the security requirements as defined in Section 3.14 (Security).

3.7. Network Management System

3.7.1. Network Operations Centre Staffing

M 3.7.1.1 The Contractor shall provision and staff the NOC in accordance with Section 3.10.1 (Event, Incident and Problem Management).

3.7.2. Network Management System

M 3.7.2.1In addition to the service management components of the NOC the Contractor shall implement and operate the specified NMS solution in accordance with the requirements. The Commission shall have access to the NMS system at all times. The access shall be guaranteed for at least 5 concurrent users of the Commission.

M 3.7.2.2The Contractor shall ensure that the NMS, the trouble ticketing system and all other time stamps, including email correspondence, are accurate and use the Coordinated Universal Time (UTC) time system.

M 3.7.2.3 The Contractor shall be responsible for monitoring the status and performance of all network elements, circuits and other services in the GCI.

M 3.7.2.4Any outages of network elements or deviations from the performance levels specified in the SLA shall be reported to the Commission in accordance with the requirements for ticketing, reporting and escalation.

M 3.7.2.5The Contractor shall generate all reporting, including detailed and summary network performance data, necessary to verify that the GCI network is compliant with the SLA and meets the performance requirements. These reports shall be produced on a monthly basis or on an ad hoc basis as required by the Commission.

M 3.7.2.6 The Contractor shall ensure its NMS supports the integrated and comprehensive monitoring and management of all network elements, links, virtual circuits, satellite communications systems including the different geographic hubs and coverage

Page 65 of 116 12/02/016


beams, terrestrial communication infrastructure including provider networks elements and links, VPNs, Internet access infrastructure and all of the associated network services.

M 3.7.2.7 The NMS shall be able to measure all performance and SLA compliance metrics from the Commission’s premises in Vienna.

M 3.7.2.8 The Contractor shall submit to the Commission for review and approval the NMS design documentation together with the test acceptance plan.

M 3.7.2.9

Prior to deployment into service the NMS shall successfully pass the agreed system acceptance tests. System acceptance testing shall demonstrate the following capacities, amongst others:

Ability to collect all data and fulfil all agreed functionality requirements; System design free of any single point of failure; Ability to recover following a complete system failure such as an extended

power outage; Ability to restore full NMS functionality and data from backup.

M 3.7.2.10

As part of the design documentation the Contractor shall submit to the Commission for review and approval a scalability study documenting that the presented solution is able to collect, store and analyse the monitoring data of the entire GCI network, including all sites and subsystems, for the entire duration of the contract as well as possible extensions.

M 3.7.2.11Following acceptance the NMS shall be put under configuration management and control. Any change requests shall be submitted to the Commission for review and approval at least 15 days in advance.

M 3.7.2.12Should the Commission consider the changes to be major, it shall reserve the right to request a full or partial rerun of acceptance testing for the NMS. Should this acceptance testing fail to meet all of the specifications the Contractor shall immediately roll back to the previous working configuration.

M 3.7.2.13NMS hardware and software shall be covered by appropriate support contracts throughout the operating life of the system. The Commission shall reserve the right to audit these contracts on an ad hoc basis.

M 3.7.2.14 The Contractor shall maintain an adequate number of spares locally to ensure the required availability and restoration time in case of failure.

M 3.7.2.15The Contractor shall maintain the hardware and software of the NMS and ensure that they are still supported and can be maintained as part of vendor support contracts.

M 3.7.2.16The Contractor shall report to the Commission at least 6 months in advance when NMS hardware and software subsystems are reaching end of life or end of support and present an upgrade plan to the Commission for review and approval.

M 3.7.2.17The NMS of the Contractor shall store all collected measurement data in an agreed open format, or shall be capable of being exported to other commercially available databases, with reliable backup, long term archiving and continuous retrieval (by the Contractor and by the Commission) functionality.

M 3.7.2.18The NMS shall preserve all raw historical data at the measurement intervals specified in articles M 3.7.2.19, M 3.7.2.20, M 3.7.2.21, M 3.7.2.22, M 3.7.2.23 and M 3.7.2.24 for the entire duration of the contract.

M 3.7.2.19 At the end of the GCI contract the Contractor shall deliver all collected measurement data in the agreed open format.

M 3.7.2.20 For all network elements not located at a remote site (e.g. IDC, core terrestrial network), the NMS shall measure network element status, link packet loss and link

Page 66 of 116 12/02/016


data rate with a resolution of less than 1 minute. All other monitoring parameters for these network elements shall be monitored with a resolution of less than or equal to 5 minutes.

M 3.7.2.21For all network elements not located at a remote site, the NMS shall store the data at the highest resolution for at least 60 days in order to facilitate post factum diagnosis of incidents.

M 3.7.2.22For all network elements not located at a remote site, after 60 days the monitoring data shall be aggregated to a resolution of 30 minutes for a period of 1 year, after which the data can be further aggregated to a resolution of 6 hours.

M 3.7.2.23For all network elements located at a remote site, the NMS shall measure network element status, link packet loss and link data rate with a resolution of less than 3 minutes. All other monitoring parameters for these network elements shall be monitored with a resolution of 15 minutes or less.

M 3.7.2.24For all network elements located at a remote site, the NMS shall store the data at the highest resolution for at least 90 days in order to facilitate post factum diagnosis of incidents.

M 3.7.2.25For all network elements not located at a remote site, after 90 days the monitoring data shall be aggregated to a resolution of 60 minutes for a period of 1 year, after which the data shall be further aggregated to a resolution of 24 hours.

M 3.7.2.26The NMS shall provide a real time graphical display of the network topology where the status of individual network elements, links and traffic routing shall be clearly visible.

M 3.7.2.27 The NMS shall be configured and capable of automatically identifying, recording and handling intermittent outages.

M 3.7.2.28 The Contractor shall configure all network management data interchange with the Commission to communicate via the GCI‒IDC interface.

M 3.7.2.29 The Contractor shall include the NMS in business continuity planning.

3.7.2.1. Performance Data

M 3.7.2.1.1The Contractor shall continually monitor and produce reports on the GCI network resources, traffic patterns, network response times and all other network performance parameters to be monitored.

M 3.7.2.1.2 Network performance parameters to be monitored shall include but are not limited to:

End to end packet delay; Packet delay to all the intermediate network elements; Aggregate bandwidth throughput; Bandwidth throughput for individual TCP/IP flows; Bandwidth throughput per individual traffic class at each interface; Packet loss; Packet jitter; Interface state transitions; Routing protocols adjacency changes; Individual network elements, memory usage, central processing unit usage

and environmental parameters (e.g. temperature, fan status, voltage); On all the network elements for all of the interfaces individual interfaces:

cyclical redundancy check (CRC) errors, collisions (where applicable), packet drops due to congestion, traffic rate inbound/outbound, packet rate inbound/outbound and interface state;

NetFlow v9 statistics;

Page 67 of 116 12/02/016


Lower level protocol parameters including Eb/N0 with an accuracy of at least 0.1 for the satellite links, signal to noise ratio (SNR) statistics, TX and RX power levels.

3.7.2.2. Operational Status

M 3.7.2.2.1The Contractor shall continually and on demand monitor and produce alerts and reports on GCI network resources in order to obtain the status of all network elements and interfaces.

M 3.7.2.2.2

Network device resource status information shall include but is not limited to: Time stamps of status changes; Exact type of parameter being measured; Value of the parameter measured; Criticality value associated with the event.

3.7.2.3. High Availability Server

M 3.7.2.3.1 The Contractor shall ensure that its NMS has sufficiently high availability functionality to meet the required availability specified in the SLA.

3.7.2.4. Management Data Requirements

M 3.7.2.4.1

The Commission shall reserve the right to operate its own NMS, which shall be provided with all access necessary to monitor the performance and status of data from the GCI. This shall include but is not limited to:

Read-only access to the entire SNMP management information base of all the network elements;

Ability to ping all of the various network elements; Ability to perform end to end traceroute diagnostics; Ability to log in and pull the active configuration of all network elements; Ability to log in to the network elements and display all status and runtime

information available.

M 3.7.2.4.2All network elements shall be configured to send NetFlow v9, SNMP traps and logs to the designated NMS of the Commission. The network elements that do not support these protocols shall be exempt from this requirement.

M 3.7.2.4.3The Contractor shall provide continuous network status, configuration and performance data at intervals stated from all edge and infrastructure network elements, including but not limited to satellite modems/routers, routers, switches and UPSs via interface(s) between the GCI and the NMS of the Commission.

M 3.7.2.4.4 This data shall include but is not limited to: Equipment status, events and configuration for each network device:

Equipment status; Serial number or unique identifier; IP and media access control addresses; System uptime; All alarms and events, specifically including link up/down alarms or

routing protocol adjacency changes; Traffic levels including source, destination IP addresses and QOS

markings; Status of each site LAN port (e.g. administratively enabled or disabled,

operationally up or down).

Page 68 of 116 12/02/016


Satellite remote site equipment status, events and configuration in addition to the above: Received signal quality at the satellite terminal; Received signal quality at the satellite gateway; Buffer overflows at the satellite terminal; Frames or packets discarded or not sent; Power and bandwidth utilization; TCP spoofing or emulation statistics.

Terrestrial remote site equipment status, events and configuration in addition to the above: Indication of primary or backup service activation for links with backup; Terrestrial circuit capacity utilization in both directions for each terrestrial

circuit; Terrestrial circuit packet loss and CRC errors.

Network congestion indicators. Network routing information at each site and at the IDC:

Routing table contents; Address Resolution Protocol (ARP) cache contents; Router interface status (e.g. administratively enabled or disabled,

operationally up or down); IP addresses administratively refused (e.g. by access control lists).

UPS equipment status and configuration in addition to the equipment status, events and configuration above: Input voltage; Input frequency; Input current; Input power consumption in watts or volt-amperes; Output voltage; Output current; Output power consumption in watts or volt-amperes; Battery charge level; Autonomous alert; Power restored alert; Bypass alert; Bypass status (source of output power).

Power supply at DC sites: Applicable parameters taken from the list for UPS equipment status and

configuration. Network performance data:

Average and peak transmit and receive throughput per remote site, in both bits per second and packets per second;

Transmit and receive data rates at the remote data port, in both bits per second and packets per second;

Transmit and receive data rates at the IDC data port, in both bits per second and packets per second;

End to end packet/frame loss; Packet/frame loss or discards at the remote equipment; End to end two way delay times; Breakdown of site traffic by protocol.

Page 69 of 116 12/02/016


3.7.2.5. Integration of the Network Management System of the Contractor with the Incident Tracking System of the Commission

M 3.7.2.5.1 The NMS of the Contractor shall have the ability to automatically open trouble tickets in the trouble ticketing system of the Contractor.

M 3.7.2.5.2 The NMS shall open trouble tickets using the appropriate severity levels.

M 3.7.2.5.3The Commission shall have access to the trouble ticketing system of the Contractor. The access shall be guaranteed for at least 5 concurrent users of the Commission.

M 3.7.2.5.4 The trouble ticketing system of the Contractor shall integrate with the (currently JIRA) based internal trouble ticketing system of the Commission.

3.8. Provisioning, Integration, Validation and Verification

The PIVV phase covers all activities related to the provisioning and testing of the infrastructure and includes:

Provisioning

System Integration

Validation

Verification

Testing.

3.8.1. Provisioning, Integration, Validation and Verification Plan

Preliminary Provisioning, Integration, Validation and Verification Plan

M 3.8.1.1The Contractor shall deliver the Preliminary PIVV Plan to the Commission for review as part the Kick-Off Meeting in accordance with the specifications and schedules in the SOW.

M 3.8.1.2

The Preliminary PIVV plan shall include but is not limited to: A definition of the integration testing objectives; A breakdown of the interfacing subsystems and components; An Interface Control Document to be populated with the interface

specifications between different parties; A draft schedule for the building and provisioning of all supporting

infrastructure elements including e.g. the terrestrial core network infrastructure, teleport infrastructure, NMS, test remote sites;

A list of external or subcontractor delivered products and their schedule for provisioning and testing;

A preliminary schedule for all testing activities during the PIVV phase; A Preliminary Test Plan.

Final Provisioning, Integration, Validation and Verification Plan

M 3.8.1.3The Contractor shall deliver the Final PIVV Plan to the Commission for review as part of the PIVV Start Meeting in accordance with the specifications and schedules in the Statement of Work.

M 3.8.1.4 The Final PIVV Plan shall be based on the Preliminary PIVV Plan and incorporate all changes and updates resulting from the design and technical review phase.

Page 70 of 116 12/02/016


M 3.8.1.5

The Final PIVV Plan shall include but is not limited to: Detailed system hierarchy showing the relationship and interfaces between all

system elements in accordance with the Detailed Design Document; Interface Control Document populated with all the interface specifications

between different parties in accordance with the Detailed Design Document; Revised schedule for the building and provisioning of all supporting

infrastructure elements including e.g. the terrestrial core network infrastructure, teleport infrastructure, NMS and test remote sites;

Specifications for all external or subcontractor products, the revised schedule for provisioning and testing of these products and their acceptance criteria;

Final schedule for all testing activities; Detailed Test Plan incorporating the test plans for equipment, subsystems and

end to end system testing.

M 3.8.1.6

The Detailed Test Plan shall include but is not limited to: All relevant tests needed to prove compliance with the design requirements; Methodology and tools to be used for each test; Step by step description of the activities for each test and the expected

outcomes; Pass and fail criteria for each test; Criticality level for each associated test.

M 3.8.1.7 The Detailed Test Plan as defined in articles M 3.8.1.5 and M 3.8.1.6 shall be reviewed and approved by the Commission with the assistance of the Contractor.

M 3.8.1.8

The Contractor shall update the Detailed Test Plan with the results, where applicable, of all performed tests including:

Results of the test; Values of the measured parameters; Error messages and warnings produced during the test; Logs from the associated elements to be tested ; Screenshots; Time stamps for each of the activities included in the tests; Other relevant information.

M 3.8.1.9 The Detailed Test Plan shall be available to the Commission at all times.

M 3.8.1.10 The Contractor shall update the Quality Register with all test results on a weekly basis.

M 3.8.1.11The Contractor shall inform the Commission in writing via an exception report of any failed test with a potential impact on the scope, schedule or functionality of the GCI network and update the Risk Register accordingly.

M 3.8.1.12 The Contractor shall present to the Commission for review a mitigation plan and a risk analysis for any failed test with a potential impact on the GCI network.

M 3.8.1.13 During the PIVV phase the Contractor shall provide to the Commission a weekly Highlight Report detailing all activities performed and their outcomes.

M 3.8.1.14The Contractor shall cooperate with the Commission and make all the arrangements necessary to ensure that a representative of the Commission will be able to witness all PIVV testing activities.

3.8.2. Unit Verification Testing

M 3.8.2.1 As part of the Detailed Test Plan the Contractor shall provide a Unit Test Plan.

M 3.8.2.2 The goal of unit testing is to isolate each subcomponent and verify that the individual parts and subcomponents meet the requirements and are fit for purpose.

Page 71 of 116 12/02/016


The Contractor shall include in the Unit Test Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.8.2.3The Contractor shall submit the Unit Test Plan to the Commission for review and approval as part of the PIVV Start Meeting in accordance with the schedules in the SOW.

M 3.8.2.4 The Unit Test Plan shall be available to the Commission at all times.

M 3.8.2.5

The components and subcomponents that the Contractor tests in the unit testing process shall include but are not limited to:

Routers Switches Firewalls Satellite modems Satellite hubs Antennas BUCs Frequency up/down converters RF switches ACUs (where applicable) Servers Network storage elements UPSs Power converters Power backup systems such as generators.

M 3.8.2.6The Contractor shall deliver a Unit Compliance Test Report to prove the compliance of all associated subcomponents as part of the PIVV Checkpoint Meeting in accordance with the specifications and schedules in the SOW.

3.8.3. Subsystem Validation and Verification Testing

M 3.8.3.1 As part of the Detailed Test Plan the Contractor shall provide a Subsystem Test Plan.

M 3.8.3.2

The goal of subsystem validation and verification is to test the interaction between the units forming a distinct subsystem and verify that the subsystem as a whole meets the requirements and is fit for purpose. The Contractor shall include in the Subsystem Test Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.8.3.3The Contractor shall submit the Subsystem Test Plan to the Commission for review and approval as part of the PIVV Start Meeting in accordance with the schedules in the SOW.

M 3.8.3.4

The subsystems the Contractor shall test in the subsystem testing process include are but not limited to:

Terrestrial core network infrastructure; Teleport antenna subsystems including the RF chains and the ACU for each

teleport; Teleport network infrastructure for each teleport; Teleport hub and hub NMS; IDC provider network infrastructure; NMS.

M 3.8.3.5 The Contractor shall deliver a Subsystem Compliance Test Report for each of the subsystems to prove compliance of all associated subsystems as part of the PIVV Checkpoint Meeting in accordance with the specifications and schedules in the

Page 72 of 116 12/02/016


SOW.

Terrestrial Core Network Infrastructure

M 3.8.3.6 As part of the Subsystem Test Plan the Contractor shall deliver a Terrestrial Core Network Infrastructure Test Plan.

M 3.8.3.7The scope of the Terrestrial Core Network Infrastructure Test Plan is to verify the compliance of the terrestrial core network infrastructure with requirements. The Contractor shall include in the Terrestrial Core Network Infrastructure Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.8.3.8The Contractor shall submit the Terrestrial Core Network Infrastructure Test Plan to the Commission for review and approval as part of the PIVV Start Meeting in accordance with the schedules in the SOW.

M 3.8.3.9 The Terrestrial Core Network Infrastructure Test Plan shall be available to the Commission at all times.

M 3.8.3.10

As part of the terrestrial core network infrastructure testing the Contractor shall test as a minimum the following features, capabilities and specifications and their compliance with requirements:

IPv4 and IPv6 connectivity over the terrestrial core network infrastructure. IP multicast transport over the terrestrial core network infrastructure. Packet loss over the terrestrial core network infrastructure from all teleports to

the IDC over a period of at least 24 hours. Latency and jitter (delay variation) over the terrestrial core network

infrastructure for each of the traffic classes. QOS marking and bandwidth allocation for all traffic classes over the terrestrial

core network infrastructure. The capability to distribute the unused capacity from one traffic class to the

other traffic classes on a best effort basis. Capacity measurements from all teleports to the IDC over a 24 hour period. All redundancy and resiliency testing necessary to prove that there is no single

point of failure in the terrestrial core network infrastructure. Redundancy and resiliency testing shall be performed under full network load.

Stability testing under full network load for a period of at least 72 hours. The ability to monitor all network elements and links which are part of the

terrestrial core network infrastructure and the interfaces between the terrestrial core network infrastructure and other subsystems.

All other tests necessary to prove the conformance of the terrestrial core network infrastructure with requirements.

M 3.8.3.11The Contractor shall deliver a Terrestrial Core Network Testing Report, proving the compliance with requirements, as part of the PIVV Checkpoint Meeting in accordance with the specifications and schedules in the SOW.

Teleport Network Infrastructure

M 3.8.3.12 As part of the subsystem test plan the Contractor shall deliver a Teleport Network Infrastructure Test Plan.

M 3.8.3.13The scope of the Teleport Network Infrastructure Test Plan is to verify the compliance of the teleport network infrastructure with requirements. The Contractor shall include in the Teleport Network Infrastructure Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.8.3.14 The Contractor shall submit the Teleport Network Infrastructure Test Plan to the Commission for review and approval as part of the PIVV Start Meeting in

Page 73 of 116 12/02/016


accordance with the schedules in the SOW.

M 3.8.3.15 The Teleport Network Infrastructure Test Plan shall be available to the Commission at all times.

M 3.8.3.16

As part of the teleport network infrastructure testing the Contractor shall test as a minimum the following features and capabilities and their compliance with requirements:

IPv4 and IPv6 functionality. IP multicast functionality. QOS marking and priority enforcement for each of the traffic classes. All redundancy and resiliency testing necessary to prove that there is no single

point of failure in the teleport network infrastructure. The redundancy and resiliency testing shall also be performed under network load.

Stability testing under full network load for a period of at least 72 hours. The ability to monitor all the network elements and links which are part of the

teleport network infrastructure and the interfaces between the teleport network Infrastructure and other subsystems.

All other tests necessary to prove conformance with requirements.

M 3.8.3.17The Contractor shall deliver a Teleport Network Testing Report, proving the compliance with requirements, as part of the PIVV Checkpoint Meeting in accordance with the specifications and schedules in the SOW.

Teleport Antenna and Radio Frequency

M 3.8.3.18 As part of the Subsystem Test Plan the Contractor shall deliver a Teleport Antenna and RF Test Plan.

M 3.8.3.19The scope of the Teleport Antenna and RF Test Plan is to verify compliance of the Teleport Antenna and RF with requirements. The Contractor shall include in the Teleport Antenna and RF Test Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.8.3.20The Contractor shall submit the Teleport Antenna and RF Test Plan to the Commission for review and approval as part of the PIVV Start Meeting in accordance with the schedules in the SOW.

M 3.8.3.21 The Teleport Antenna and RF Test Plan shall be available to the Commission at all times.

M 3.8.3.22

As part of the Teleport Antenna and RF testing the Contractor shall test as a minimum the following features and capabilities and their compliance with the requirements:

Gain and noise figures for the antenna and the RF subsystem. ACU (where applicable). All redundancy and resiliency testing necessary to prove that there is no single

point of failure in the teleport antenna and RF infrastructure. Signal and noise stability testing for a period of at least 24 hours. Ability to monitor all components of the RF system. All other tests necessary to prove conformance with requirements.

M 3.8.3.23The Contractor shall deliver a Teleport Antenna and RF Test Plan Testing Report, proving the compliance with requirements, as part of the PIVV Start Meeting in accordance the specifications and schedules in the SOW.

M 3.8.3.24The Contractor may substitute part of the teleport and RF subsystem test results with the results of a recent certification of the teleport. The results of the certification report shall be reviewed by the Commission and the decision on which tests can be substituted is at the sole discretion of the Commission.

Page 74 of 116 12/02/016


Teleport Hub and Hub Network Monitoring System

M 3.8.3.25 As part of the Subsystem Test Plan the Contractor shall deliver a Teleport Hub Test Plan.

M 3.8.3.26The scope of the Teleport Hub Test Plan is to verify compliance of the Teleport Hub and its associated NMS with requirements. The Contractor shall include in the Teleport Hub Test Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.8.3.27The Contractor shall submit the Teleport Hub Test Plan to the Commission for review and approval as part of the PIVV Start Meeting in accordance with the schedules in the SOW.

M 3.8.3.28 The Teleport Hub Test Plan shall be available to the Commission at all times.

M 3.8.3.29

As part of teleport hub testing the Contractor shall test as a minimum the following features and capabilities and their compliance with requirements:

IPv4 and IPv6 functionality. IP multicast functionality. QOS marking and bandwidth allocation for all traffic classes. The capability to distribute the unused capacity from one traffic class to the

other traffic classes on a best effort basis. All redundancy and resiliency testing necessary to prove that there is no single

point of failure in the teleport hub. The redundancy and resiliency testing shall exercise the redundancy of all the hub subsystems and subcomponents including e.g. line cards, protocol processors, power supplies and modulator and demodulator subsystems.

All redundancy and resiliency testing necessary to prove that there is no single point of failure in the teleport hub NMS subsystem.

Site diversity and teleport swapping (where applicable). All other tests necessary to prove conformance with requirements.

M 3.8.3.30The Contractor shall deliver a Teleport Hub Test Plan Testing Report, proving the compliance with requirements, as part of the PIVV Checkpoint Meeting in accordance with the specifications and schedules in the SOW.

International Data Centre Network (Provider Side)

M 3.8.3.31As part of the Subsystem Test Plan the Contractor shall deliver an IDC Network Test Plan. The IDC Network Test Plan shall focus on the network of the Contractor at the IDC and its interface with the Commission.

M 3.8.3.32The scope of the IDC Network Test Plan is to verify compliance of the part of the IDC network provided by the Contractor with requirements. The Contractor shall include in the IDC Network Test Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.8.3.33The Contractor shall submit the IDC Network Test Plan to the Commission for review and approval as part of the PIVV Start Meeting in accordance with the schedules in the SOW.

M 3.8.3.34 The IDC Network Test Plan shall be available to the Commission at all times.

M 3.8.3.35 As part of the IDC Network Test Plan the Contractor shall test as a minimum the following features and capabilities and their compliance with requirements:

IPv4 and IPv6 functionality. IP multicast functionality. QOS marking and bandwidth allocation for all traffic classes. All redundancy and resiliency testing necessary to prove that there is no single

Page 75 of 116 12/02/016


point of failure in the IDC network provided by the Contractor. The redundancy and resiliency testing shall be performed under full network load.

Stability testing under full network load for a period of at least 72 hours. The ability to monitor all the network elements and links which are part of the

IDC network and the interfaces between the IDC network and other subsystems.

All other tests necessary to prove conformance with requirements.

M 3.8.3.36The Contractor shall deliver a Teleport Hub Test Plan Testing Report, proving the compliance with requirements, as part of the PIVV Checkpoint Meeting in accordance the specifications and schedules in the SOW.

Network Management System

M 3.8.3.37 As part of the Subsystem Test Plan the Contractor shall deliver an NMS Test Plan.

M 3.8.3.38The scope of the NMS Test Plan is to verify compliance of the NMS with requirements. The Contractor shall include in the NMS Test Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.8.3.39The Contractor shall submit the NMS Test Plan to the Commission for review and approval as part of the PIVV Start Meeting in accordance with the schedules in the SOW. The NMS Test Plan shall be available to the Commission at all times.

M 3.8.3.40

As part of the NMS Test Plan the Contractor shall test as a minimum the following features and capabilities and their compliance with the requirements:

Ability to monitor all GCI network elements and links. All redundancy and resiliency testing necessary to prove that there is no single

point of failure in the NMS subsystem including e.g. network interface failure, failure of supporting network elements, storage failure, power supply failure and server failure.

Automatic recovery from a complete power outage. Recovery and restoration of data from backup. All other tests necessary to prove conformance with requirements.

M 3.8.3.41The Contractor shall deliver a NMS Plan Testing Report, proving compliance with requirements, as part of the PIVV Checkpoint Meeting in accordance the specifications and schedules in the SOW.

3.8.4. System Validation and Verification Testing

M 3.8.4.1 As part of the Detailed Test Plan the Contractor shall provide a System Test Plan.

M 3.8.4.2

The goal of system validation and verification testing is to verify the end to end functionality of the GCI and that the GCI as a whole meets the requirements and is fit for purpose. The Contractor shall include in the System Validation and Verification Test Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.8.4.3 The System Test Plan shall be available to the Commission at all times.

M 3.8.4.4The Contractor shall initiate system validation and verification testing only after the successful completion of subsystem testing and its review and acceptance by the Commission.

M 3.8.4.5 At the start of system validation and verification testing the Contractor shall have successfully tested and have in place all necessary supporting infrastructure, including but not limited to:

Page 76 of 116 12/02/016


Terrestrial core network infrastructure; IDC network; All teleports; Satellite capacity in all regions; Test sites at the IDC as defined in article M 3.8.4.7; A remote test site in each region as defined in article M 3.8.4.8; NMS; NOC; Trouble ticketing system; CMS; Server backup infrastructure.

M 3.8.4.6

At the start of system validation and verification testing the Contractor shall have in place all necessary testing tools, including but not limited to:

RF spectrum analysers; Network sniffers; Packet generators; Logging servers; Vulnerability scanning tools.

M 3.8.4.7

For the purpose of system validation and verification testing the Contractor shall deploy test remote sites at the IDC for each technology including:

VSAT site with Internet backup connectivity; One site for each VSAT plus alternative backup connectivity combination; An Internet only connected site (VPN site).

M 3.8.4.8

For the purpose of system validation and verification testing the Contractor shall deploy one remote VSAT remote site with Internet backup connectivity in each of the regions. The GCI infrastructure for these remote sites shall be deployed in parallel with the existing GCI II without affecting the existing service. The Contractor shall submit as part of the PIVV Plan a proposal for the remote sites to be used for testing including the schedule for deployment.

M 3.8.4.9End to end testing for system validation and verification shall be performed between the IDC and all the remote test sites (IDC test sites and regional test sites) as specified in articles M 3.8.4.7 and M 3.8.4.8.

M 3.8.4.10

As part of system validation and verification testing the Contractor shall test as a minimum the following features and capabilities and their compliance with the requirements:

End to end IPv4 and IPv6 functionality; End to end IP multicast functionality; End to end QOS marking and bandwidth allocation for all traffic classes; End to end capacity testing; End to end redundancy testing; End to end stability testing under load for at least 72 hours; Recovery from complete system outage; NMS integration; All the interfaces between subsystems.

M 3.8.4.11The Contractor shall deliver a System Validation and Verification Report, proving the compliance with requirements, as part of the PIVV End Meeting in accordance the specifications and schedules in the SOW.

3.8.5. Documentation and Procedures for Operations and Maintenance

M 3.8.5.1 The Contractor shall deliver to the Commission before the PIVV Start Meeting all of

Page 77 of 116 12/02/016


the technical specifications, manuals, configuration guides and any other relevant documentation for all equipment used in the GCI network.

M 3.8.5.2 The Contractor shall deliver to the Commission before the PIVV End Meeting all of the maintenance and operational procedures for the GCI network.

M 3.8.5.3 The Contractor shall deliver to the Commission before the PIVV End Meeting all configuration files for all GCI equipment.

M 3.8.5.4 The Contractor shall provide the Commission access to the CMS for the GCI network.

3.8.6. Provisioning, Integration, Validation and Verification Start Meeting

The intended scope for the PIVV Start Meeting is to launch the PIVV phase and to review the associated plans and schedules.

M 3.8.6.1 The Contractor shall organize and document the PIVV Start Meeting.

M 3.8.6.2 The PIVV Start Meeting shall be scheduled in accordance with the relevant article in the SOW.

M 3.8.6.3

As part of the PIVV Start Meeting the Contractor shall deliver to the Commission the following documents:

Final PIVV Plan; Preliminary Test Plan; Unit Test Plan; Subsystem Test Plan.

M 3.8.6.4 The documents delivered in accordance with article M 3.8.6.3 shall be reviewed at the PIVV Start Meeting and the outcomes of the review shall be recorded.


M 3.8.6.6The Contractor shall submit to the Commission for review and approval a PIVV Start Meeting Report. The report shall incorporate the action plan, minutes of the meeting and outcomes of the document reviews.

3.8.7. Provisioning, Integration, Validation and Verification Checkpoint Meeting

The intended scope for the PIVV Checkpoint Meeting is to verify the PIVV process and review the unit and subsystem test results and the associated reports.

M 3.8.7.1 The Contractor shall organize and document the PIVV Checkpoint Meeting.

M 3.8.7.2 The PIVV Checkpoint Meeting shall be scheduled in accordance with the relevant article in the SOW.

M 3.8.7.3

As part of the PIVV Checkpoint Meeting the Contractor shall deliver to the Commission the following documents:

Final Unit Compliance Testing Report; Final Subsystem Verification Test Reports; Interface Control Document; Detailed Test Plan.

M 3.8.7.4The documents delivered by the Contractor in accordance with article M 3.8.7.3 shall be reviewed at the PIVV Checkpoint Meeting by the Commission together with the Contractor and the outcomes of the review shall be recorded.

Page 78 of 116 12/02/016



M 3.8.7.6The Contractor shall submit to the Commission for review and approval a PIVV Checkpoint Meeting Report. The report shall incorporate the action plan, the minutes of the meeting and the outcomes of the document reviews.

3.8.8. Provisioning, Integration, Validation and Verification End Meeting

The intended scope for the PIVV End Meeting is to conclude the PIV phase, determine readiness for start of the migration, review system test results and the associated reports and documents.

M 3.8.8.1 The Contractor shall organize and document the PIVV End Meeting.

M 3.8.8.2 The PIVV End Meeting shall be scheduled in accordance with the relevant article in the SOW.

M 3.8.8.3

As part of the PIVV End Meeting the Contractor shall deliver to the Commission the following documents:

Final System Validation and Verification Test Report; Operations and maintenance procedures and documentation; A record of all the lessons learned as part of the PIVV process.

M 3.8.8.4The documents delivered by the Contractor in accordance with article M 3.8.8.3 shall be reviewed by the Commission together with the Contractor at the PIVV Checkpoint Meeting and the outcomes of the review shall be recorded.


M 3.8.8.6The Contractor shall submit to the Commission for review and approval a PIVV Checkpoint Meeting Report. The report shall incorporate the action plan, the minutes of the meeting and the outcomes of the document reviews.

3.9. Network Implementation and Migration

The scope of this section is the planning, implementation, testing, verification, validation and acceptance for the migration of remote sites to GCI III.

Special emphasis is put on the timeliness and the validation for the implementation of remote sites given that a delay during the migration phase would have a significant impact on the Commission.

The Contractor shall account in the planning for the fact that many remote sites are located in remote and difficult to access locations.

M 3.9.1The Contractor shall provide all documents and deliverables for the Network Implementation and Migration Phase in accordance with the specifications and schedules in Section 2 (Statement of Work).

D 3.9.1The Commission prefers the employment of ITIL and/or systems engineering methodologies. Therefore the use of ITIL and/or systems engineering methodologies will be considered an advantage.

D 3.9.2 The Commission prefers the employment of PRINCE2 project management methodology for the Network Implementation and Migration Phase. Therefore the use of PRINCE2 project management methodology will be considered an

Page 79 of 116 12/02/016


advantage.

The Network Implementation and Migration Phase will include four major meetings, with all of their associated deliverables:

Implementation Start Meeting;

Implementation Checkpoint Meeting 1;

Implementation Checkpoint Meeting 2;

Implementation End Meeting.

M 3.9.2During the Network Implementation and Migration Phase the Contractor shall provide to the Commission a weekly Highlight Report detailing all activities performed and their associated outcomes.

M 3.9.3The Implementation Start, Implementation Checkpoint Meeting 1, Implementation Checkpoint Meeting 2, Implementation End meetings shall be scheduled by the Contractor with the approval of the Commission. All meetings will be held on the premises of the Commission.

M 3.9.4The Contractor shall appoint a migration and implementation team prior to the Implementation Start Meeting. The team shall be responsible for all migration and implementation aspects and activities.

M 3.9.5The Contractor shall provide to the Commission for review the curricula vitae and technical certifications of all personnel on the migration and implementation team prior to their appointment.

M 3.9.6Should the Contractor need to replace a member of the migration and implementation team it shall inform the Commission at least 15 days in advance and present to the Commission for review and approval the curriculum vitae and technical certifications of the new team member.

M 3.9.6All documentation of the Network Implementation and Migration Phase shall be placed in a version controlled Document Management System and shall be available to the Commission at all times.

M 3.9.7At the end of the Network Implementation and Migration Phase the Contractor shall document all installation and migration related activities and their associated outcomes in the Final Implementation Report.

M 3.9.8The Contractor shall be fully responsible for the coordination and management of all products and services to be delivered by subcontractors or any other external parties.

3.9.1. Migration Perquisites

M 3.9.1.1The Contractor shall be responsible for ensuring that all of the prerequisite products, services, processes, plans, documents, supporting contracts, infrastructure and any other resources necessary to commence the Network Implementation and Migration Phase are in place in accordance with requirements.

M 3.9.1.2Prior to the start of the Network Implementation and Migration Phase the Contractor shall successfully complete the Provisioning, Integration, Validation and Verification Phase with all its associated activities in accordance with Section 3.8 (Provisioning, Integration, Validation and Verification).

M 3.9.1.3 The entire necessary supporting infrastructure shall be fully tested, validated, deployed, placed under configuration management and handed over to operations.

Page 80 of 116 12/02/016


This shall include but is not limited to: Teleport infrastructure (including the associated satellite space segment); Terrestrial core network infrastructure; IDC network infrastructure; Network Monitoring System; NOC; Service desk; Ticketing system; Service Asset and CMS; Document Management System; Service Knowledge Management System; Associated support and maintenance contracts for GCI III systems and

subsystems.

M 3.9.1.4

All of the prerequisite documentation and procedures necessary for the operation of the GCI network and the supporting infrastructure shall be delivered for review and acceptance by the Commission according to the schedules specified in Section 2 (Statement of Work). These shall include but is not limited to:

Service catalogue; Standard operating procedures; Operation and maintenance procedures; Escalation procedures; Training materials (including troubleshooting guides); Technical manuals and documentation for GCI III network elements and

supporting infrastructure.

M 3.9.1.5

In accordance with the Project Plan requirements for the Network Implementation and Migration Phase, the Contractor shall fully document in the Site Provisioning Plan the following:

Scope of work undertaken by subcontractors (including subcontracted field services, installation and commissioning services);

Products and services to be delivered by subcontractors (including telecommunication and Internet service providers);

Shipping, logistics and insurance services; Licensing and regulatory approval service; Civil work and construction services (where applicable); Other consulting services; Details of all other suppliers and all other external service providers; Other external project resources.

M 3.9.1.6In accordance with Section 3.6.1 (Licencing and Regulatory Compliance) the Contractor shall be the sole party responsible for the timely completion of the licensing and regulatory processes which shall be initiated immediately after the end of the Project Planning Phase.

M 3.9.1.7 The licensing and regulatory processes shall be completed before the start of the Network Implementation and Migration Phase.

M 3.9.1.8 The Contractor shall submit monthly Highlight Reports to the Commission detailing progress on the all licensing and related activities.

M 3.9.1.9

In accordance with Section 3.6.1 (Licencing and Regulatory Compliance), the Contractor shall inform the Commission of any delayed licence process that may have a potential impact on GCI network delivery or operation. The Contractor shall inform the Commission in writing via an exception report and update the Risk Register accordingly.

M 3.9.1.10 In accordance with Section 3.6.2 (Logistics and Strategic Deployment Stock), the Contractor shall inform the Commission of any delayed shipping and logistics

Page 81 of 116 12/02/016


process that may have a potential impact on GCI network delivery or operation. The Contractor shall inform the Commission in writing via an exception report and update the Risk Register accordingly.

M 3.9.1.11

The Contractor shall complete all the coordination and site preparation activities as detailed in Section 3.9.3 (Coordination and Site Preparation), including but not limited to:

Site access coordination; Coordination with POC and the Commission; Site survey (where applicable); Civil works (where applicable); Activities related to conformity and local rules (including environmental

concerns); Other local site infrastructure (where applicable); Backup/Internet VPN.

M 3.9.1.12

The Contractor shall inform the Commission of any delays in the coordination and site preparation activities as detailed in Section 3.9.3 (Coordination and Site Preparation) that may have a potential impact on GCI network delivery or operation. The Contractor shall inform the Commission in writing via an exception report and update the Risk Register accordingly.

M 3.9.1.13At the Installation Start Meeting the Contractor shall provide a Site Acceptance Test Plan and Site Acceptance Report template for review and approval by the Commission.

3.9.2. Provisioning Plan

M 3.9.2.1

The Contractor shall provide as part of the bid sufficient documentation in the Site Provisioning Plan, included in the Project Implementation Plan, to demonstrate that the project is achievable in accordance with the requirements and the schedule defined in Section 2 (Statement of Work) and that there is sufficient tolerance and schedule margin built in to accommodate unforeseen events with a potential negative impact on project and product delivery.

M 3.9.2.2 The Site Provisioning Plan shall conform with the rest of the Project Plan and the Project Implementation Plan.

M 3.9.2.3

The Contractor shall provide for review and approval by the Commission the Site Provisioning Plan updated with all changes and lessons learned from Project Planning, Design and PIVV phases. The revised Site Provisioning Plan shall be delivered as part of the Implementation Start Meeting in accordance with the schedule and requirements as defined in Section 2 (Statement of Work).

M 3.9.2.4 The Site Provisioning Plan shall contain all of the necessary activities for the migration of the GCI network, including the associated schedules, time lines, milestones and resources allocated. The activities detailed in the Site Provision Plan shall include but are not limited to:

Licensing activities; Activities related to conformity and local rules; Site survey activities; Logistics and shipment activities; Civil work activities; Installation and provisioning activities; Transfer of service to GCI III activities; Acceptance testing, verification and validation activities; Handover to operation activities; On-site training activities;

Page 82 of 116 12/02/016


Reporting activities.

M 3.9.2.5 The Site Provisioning Plan shall incorporate the critical success factors and KPIs for all related activities, including those specified in article M 3.9.2.4.

M 3.9.2.6 The Contractor shall maintain and update the Site Provisioning Plan throughout the Network Installation and Migration Phase.

M 3.9.2.7The Contractor shall perform risk assessment for all associated site provisioning activities and incorporate the associated risk mitigation and remediation actions into the Site Provisioning Plan.

M 3.9.2.8 The Site Provisioning Plan shall be available to the Commission at all times.

M 3.9.2.9 The Contractor shall integrate the Site Provisioning Plan into the version controlled Document Management System.

M 3.9.2.10Following the Implementation Start Meeting the Contractor shall inform the Commission of any required changes to the Site Provisioning Plan in writing via an exception report. Such changes shall be made only after the review and approval of the Commission.

3.9.3. Coordination and Site Preparation

M 3.9.3.1The Contractor shall be responsible for coordinating with the Commission and/or its representatives and performing all of the necessary actions in relation to site preparation activities.

M 3.9.3.2 The Contractor shall complete site preparation activities prior to the start of the Network Installation and Migration Phase.

M 3.9.3.3The Contractor shall coordinate, cooperate and follow the instructions of the representatives of the Commission with regard to logistics and shipping activities as necessary and as requested by the Commission.

M 3.9.3.4If requested by the Commission, the Contractor shall manage site preparation activities as sub-projects for individual sites and document the sub-project accordingly.

M 3.9.3.5 The Contractor shall provide to the Commission a detailed work breakdown structure for each site preparation sub-project.

M 3.9.3.6

The work breakdown structure shall include but is not limited to: Scope of work undertaken by subcontractors; Products and services to be delivered by subcontractors; Details of all suppliers and all external service providers; Other external project resources.

M 3.9.3.7 The Contractor shall be fully responsible for the quality management of all products and services to be delivered by subcontractors or any external parties.

M 3.9.3.8The Contractor shall coordinate in a timely manner with the Commission and/or its representatives the necessary site access arrangements and permits needed for site preparation activities. The Contractor shall provide all the required documentation for site access.

M 3.9.3.9All site preparation activities or activities which may require assistance from local representatives of the Commission shall be scheduled in agreement with the Commission and/or its local representatives during normal local working hours.

M 3.9.3.10 All site preparation activities shall be carried out in accordance with local rules and regulations and take into account environmental concerns.

Page 83 of 116 12/02/016


M 3.9.3.11If requested in a timely manner by the Contractor, the Commission may in exceptional circumstances decide to provide assistance to the Contractor with regard to site preparation activities.

M 3.9.3.12The Commission and the Contractor shall jointly review and agree on the suitability of available site surveys for the site preparation and network installation and migration. The Contractor shall proceed with activities following joint acceptance of a site survey.

M 3.9.3.13

The Commission may on a case by case basis request the Contractor to perform site surveys. The Contractor shall comply with the request of the Commission and deliver the site survey documentation to the Commission for review. The site survey shall contain all information necessary for site preparation, civil works, network installation and migration.

M 3.9.3.14The Commission may on a case by case basis request the Contractor to perform civil works for specific sites. The Contractor shall comply with the request of the Commission and perform all civil works necessary for site preparation, network installation and migration.

3.9.4. Site Installation, Migration, Verification and Validation

M 3.9.4.1 The Contractor shall be the sole party responsible for installation, migration, verification and validation activities and their associated costs.

M 3.9.4.2The Contractor shall ensure that there is sufficient tolerance and schedule margin built in to accommodate unforeseen events with a potential negative impact on activities related to site installation, migration, verification and validation and the overall service, project and product delivery.

M 3.9.4.3

The Contractor shall include in the Site Provisioning Plan a schedule for all installation, migration, verification and validation activities to ensure achievement of the following goals:

At least 40% of remote sites successfully migrated, accepted and put into operation before Implementation Checkpoint Meeting 1 in accordance with the schedule in Table 2.5 of Section 2 (Statement of Work);

At least 80% of remote sites successfully migrated, accepted and put into operation before Implementation Checkpoint Meeting 2 in accordance with the schedule in Section 2 (Statement of Work);

All remote sites successfully migrated, accepted and put into operation within 10 weeks of the Implementation Checkpoint Meeting 2 in accordance with the schedule in Section 2 (Statement of Work).

M 3.9.4.4The Contractor shall inform the Commission of any delays in installation, migration, verification and validation activities that may have a potential impact on GCI network delivery. The Contractor shall inform the Commission in writing via an exception report and update the Risk Register accordingly.

M 3.9.4.5Should a risk materialize during the Network Installation and Migration Phase the Contractor shall be responsible for taking all appropriate actions as necessary and record the risk in the Risk Register.

M 3.9.4.6The Contractor shall install in a timely manner an alternative telecommunication solution (e.g. BGAN, IP VPN) for remote sites that are at risk of not meeting the agreed schedule. The installation shall be carried out in consultation and coordination with the Commission and in accordance with requirements.

M 3.9.4.7The Contractor shall be responsible for coordination with the Commission and its representatives and perform all of the necessary actions in relation to site installation activities.

Page 84 of 116 12/02/016


M 3.9.4.8The Contractor shall coordinate in a timely manner with the Commission and/or its representatives the necessary site access arrangements needed for installation and migration activities. The Contractor shall provide all of the documents required for site access.

M 3.9.4.9All on-site installation activities or activities that may require assistance from the local representatives of the Commission shall be scheduled in agreement with the Commission and/or its local representatives during normal local working hours.

M 3.9.4.10 All installation activities shall be carried out in accordance with local rules and regulations and take into account environmental concerns.

M 3.9.4.11The Contractor shall plan, coordinate and execute the remote site installation and migration process and ensure that the impact of transferring a remote site from GCI II to GCI II on IMS operational traffic is minimized.

M 3.9.4.12 SLA penalties shall apply for any outages exceeding a cumulative 8 hours of downtime for a remote site during its transfer from GCI II to GCI III.

M 3.9.4.13The Contractor shall plan and execute the installation and migration process and ensure that no more than 5 remote sites simultaneously experience downtime as a result of the migration.

M 3.9.4.14The Contractor shall distribute the migration/installation of remote sites geographically in order to minimize the number of sites with simultaneous downtime in any specific region.

M 3.9.4.15The Contractor shall assign sufficient and appropriate personnel with relevant training and/or qualification in order to migrate each site in conformance with articles M 3.9.4.11 to M 3.9.4.14.

M 3.9.4.16Following the installation of a remote site the Contractor shall perform all of the necessary testing, verification and validation activities as described in the Site Acceptance Test Plan.

M 3.9.4.17The goal of the Site Acceptance Test Plan is to verify the end to end functionality of remote sites and ensure that remote sites are in compliance with requirements and are fit for purpose. The Contractor shall include in the Site Acceptance Test Plan all tests necessary to prove compliance, with clear pass and fail criteria.

M 3.9.4.18

As part of Site Acceptance Testing the Contractor shall test as a minimum the following features and capabilities and their compliance with the requirements:

End to end IP functionality; End to end QOS marking and bandwidth allocation for all traffic classes; End to end capacity testing; End to end redundancy testing; Recovery from complete system outage; NMS integration; All the interfaces between subsystems.

M 3.9.4.19The Contractor shall deliver a Site Acceptance Test Report to document compliance with requirements at the end of each site migration. All Site Acceptance Test Reports shall be placed in the version controlled Document Management System and be available to the Commission at all times.

M 3.9.4.20The Contractor shall update the Quality Register with the status of all quality checking activities for site installation and migration and ensure that all products are complete and have met their quality criteria and that the agreed quality assurance processes have been observed.

M 3.9.4.21 Following the completion of an installation the Contractor shall ensure that the remote site is installed in accordance with industry best practices and standards, the site is left in proper working condition and any residual materials are disposed

Page 85 of 116 12/02/016


of in accordance with local rules, regulations and environmental concerns.

M 3.9.4.22

Following the completion of an installation the Contractor shall deliver to the Commission a Site Installation Report containing all relevant information regarding local conditions at the remote site, including but not limited to:

Detailed electrical and cabling diagram; Photos of all GCI equipment (indoor and outdoor) and associated connectivity,

cable paths, points of entry, grounding points and all other relevant aspects; Line of site documentation including relevant photos and diagrams; Photos and documentation of the local site infrastructure and its environment; Inventory details (including the location of spares); Other local conditions at the site.

M 3.9.4.23

The Contractor shall deliver all implementation reports to the Commission for review and approval, including Implementation Checkpoint Reports (1 and 2) and the Final Implementation Report. The Implementation Reports shall be placed in the version controlled Document Management System and be available to the Commission at all times.

3.9.5. Implementation Start Meeting

The intended scope of the Implementation Start Meeting is to launch the Network Installation and Migration Phase, introduce the installation and migration team and review the associated documents and plans.

M 3.9.5.1 The Contractor shall organize and document the Implementation Start Meeting.

M 3.9.5.2 The Implementation Start Meeting shall be scheduled in accordance with the relevant article in Section 2 (Statement of Work).

M 3.9.5.3As part of the Implementation Start Meeting the Contractor shall deliver to the Commission the following documents:

Revised Site Provisioning Plan.

M 3.9.5.4The documents delivered in accordance with article M 3.9.5.3 shall be reviewed by the Commission with the assistance of the Contractor at the Implementation Start Meeting, and the outcomes of the review shall be recorded.


M 3.9.5.6The Contractor shall submit to the Commission for review and approval the Implementation Start Meeting Report. The report shall incorporate the action plan, the minutes of the meeting and the outcomes of the document review.

M 3.9.5.7As part of the Implementation Start Meeting the Contractor shall appoint and introduce to the Commission the installation and migration team, including the roles and responsibilities of each member.

3.9.6. Implementation Checkpoint Meetings

The intended scope of the Implementation Checkpoint Meetings is mainly to review the progress of the migration and the associated documents and plans.

M 3.9.6.1 The Contractor shall organize and document the Implementation Checkpoint Meetings.

M 3.9.6.2 The Implementation Checkpoint Meetings shall be scheduled in accordance with

Page 86 of 116 12/02/016


the relevant article in Section 2 (Statement of Work).

M 3.9.6.3

As part of the Project Review Meeting the Contractor shall deliver to the Commission the following documents:

Implementation Report 1; Implementation Report 2.

M 3.9.6.4The documents delivered in accordance with article M 3.9.6.3 shall be reviewed by the Commission with the assistance of the Contractor at the Implementation Checkpoint Meetings and the outcomes of the review shall be recorded.


3.9.7. Implementation End Meeting

The intended scope of the Implementation End Meeting is to conclude the Network Installation and Migration Phase and the finalization of all documents and plans associated with Network Installation and Migration.

M 3.9.7.1 The Contractor shall organize and document the Implementation End Meeting.

M 3.9.7.2 The Implementation End Meeting shall be scheduled in accordance with the relevant article in the Section 2 (Statement of Work).

M 3.9.7.3 As part of the Implementation End Meeting the Contractor shall deliver to the Commission the Final Implementation Report for the GCI III network.

M 3.9.7.4 The Final Implementation Report shall be reviewed by the Commission with the assistance of the Contractor and the outcomes of the review shall be recorded.

M 3.9.7.5The Implementation End Meeting shall conclude the Implementation Phase and all associated actions, documents, plans and other deliverables shall be finalized by the Contractor.

3.10. Service Operation and Management

The scope of this section is the operation and management for the GCI network including all of the associated activities throughout the duration of the contract.

M 3.10.1The Contractor shall provide all documents and deliverables for the Service Operation and Management Phase in accordance with the specifications and schedules in Section 2 (Scope of Work).

D 3.10.1 The Commission prefers the employment of ITIL methodology. Therefore the use of ITIL methodology will be considered an advantage.

M 3.10.2 The Contractor shall provide as part of the bid a preliminary Service Operations and Management Plan for review and evaluation by the Commission.

M 3.10.3 The Contractor shall provide sufficient documentation in the Service Operations and Management Plan to demonstrate full compliance with the requirements.

M 3.10.4The Contractor shall update the Service Operations and Management Plan with the changes and lessons learned during the Design Phase, PIVV Phase and Migration Phase.

M 3.10.5 The Contractor shall update the Service Operations and Management Plan with

Page 87 of 116 12/02/016


any changes throughout the duration of the contract.

M 3.10.6 The Service Operation and Management Plan shall be placed in a version controlled Document Management System.

M 3.10.7 The Service Operation and Management Plan shall be available to the Commission at all times.

M 3.10.8The Contractor shall ensure that the Service Operations and Management Plan and its associated processes shall take into account Confidentiality, Integrity and Availability aspects and be compliant with Section 3.14 (Security).

3.10.1. Event, Incident and Problem Management

The goal of the event, incident and problem management process is the restoration of service and the resolution of underlying issues in a timely manner in order to mitigate and minimize the impact and ensure that the levels of service quality and availability are maintained.

M 3.10.1.1 The Contractor is the sole party responsible for addressing all incidents and restoring service in a timely manner.

M 3.10.1.2 The Contractor shall proactively implement actions and measures to prevent potential incidents and service outages from occurring.

M 3.10.1.3 The Contractor shall implement a NOC available 24 hours a day, 365 days a year.

M 3.10.1.4The Contractor shall implement a Service Desk which shall be the primary liaison for the Commission in relation to service maintenance and operation. The Service Desk shall be available 24 hours a day, 365 days a year.

M 3.10.1.5The Contractor shall provision and staff the NOC and Service Desk with appropriately qualified personnel in order to operate, maintain and improve performance of the GCI and provide technical feedback and support to the Commission whenever requested.

M 3.10.1.6The Contractor shall be responsible for training NOC and Service Desk personnel to the appropriate level in order to keep up with the developments required for the operation of the GCI III network.

M 3.10.1.7A list of the NOC and Service Desk personnel assigned to GCI III operations, including their curricula vitae, shall be delivered to the Commission and updated as necessary.

D 3.10.1.1It is highly desirable that NOC and Service Desk staff have active ITIL certification and have undergone recent ITIL training. Such certifications will be considered an advantage.

M 3.10.1.8The NOC of the Contractor shall monitor the GCI network, detect events and analyse them to determine in a timely manner the appropriate control action in accordance with the event management process as part of the Service Operations and Management Plan.

M 3.10.1.9

If notified by the Commission and/or its representatives of any anomalous events or incidents in the GCI network the Contractor shall investigate and perform all required actions and report back to the Commission and/or its representatives on the actions taken and the associated outcomes. Such an event or incident shall be recorded in all of the associated processes and tools including the Contractor’s Trouble Ticketing System and the Known Error Database.

M 3.10.1.10 The Contractor shall investigate all incidents affecting service or incidents that have

Page 88 of 116 12/02/016


the potential to affect service .

M 3.10.1.11The Contractor shall have in place all of the necessary escalation processes, tools, training and resources for timely resolution of major and critical incidents in accordance with Section 4.2.3 (Other Performance Metrics).

M 3.10.1.12Should any events be determined to be anomalous, the NOC of the Contractor shall classify, prioritize and take the necessary reporting and escalation actions in accordance with Section 4.2.3 (Other Performance Metrics).

M 3.10.1.13 The Contractor shall record all events and incidents in the Trouble Ticketing System and all records shall be UTC time-stamped.

M 3.10.1.14 The Trouble Ticketing System of the Contractor shall integrate with the (currently JIRA based) ticketing system of the Commission.

M 3.10.1.15The Contractor shall record the associated outcomes and actions taken to restore service and any other relevant information in the Contractor’s Ticketing System and/or the Known Error Database/Service Knowledge Management System accordingly.

M 3.10.1.16The Contractor shall integrate the Incident Management System with the associated processes and tools contained in the Service Level Management, Service Asset and Configuration Management, Change Management and Problem Management processes.

M 3.10.1.17 The Contractor shall investigate, as part of the problem management process, all recurring incidents with a potential common cause.

M 3.10.1.18 The Contractor shall perform a root cause analysis and a fault tree analysis for all recurring or interrelated incidents.

M 3.10.1.19 The Contractor shall perform a root cause analysis for all Major and Critical incidents in accordance with Section 4.2.3 (Other Performance Metrics).

M 3.10.1.20The Contractor shall make available to the Commission and record accordingly all of the results and documentation for problem investigation including but not limited to logs, output from monitoring tools, monitoring data, operational conditions, troubleshooting actions and service recovery actions.

M 3.10.1.21The Contractor shall monitor for and identify patterns and trends within the GCI network and proactively perform all necessary problem management tasks and activities.

M 3.10.1.22

The Contractor is responsible for making full use of the resources and tools at its disposal to diagnose, report and address all incidents and problems. This shall include but is not limited to:

Service, Assets and CMS; Known Error Database; Service Knowledge Management System; Vendor notifications, announcements and alerts; Historical trouble ticketing information; Reports and notifications from the Commission and/or its representatives; Industry best practices and vendor troubleshooting guides.

M 3.10.1.23The Contractor is responsible for liaising with the vendors and/or subcontractors on issues and problems related to the products and services employed in the GCI network. Should problems, issues and risks be announced the Contractor shall address them as part of the incident and/or problem management processes.

M 3.10.1.24If as part of the problem management process an underlying issue which cannot be immediately resolved is identified the Contractor shall take all necessary mitigation measures to minimize the impact.

Page 89 of 116 12/02/016


M 3.10.1.25All of the relevant information about problems must be recorded in the appropriate system in order to maintain a full historic record of incidents. The record(s) shall be UTC time-stamped. A problem report shall contain cross-references to the associated incidents and Known Errors.

M 3.10.1.26The NOC and Service Desk shall respond in a comprehensive and timely manner to requests from the Commission and/or its representative for information and status updates.

M 3.10.1.27 The NOC and Service Desk shall record all service related requests for information in the Contractor’s Trouble Ticketing System.

M 3.10.1.28 The NOC and Service Desk shall always copy the Commission in service related email correspondence regarding with the representatives of the Commission.

M 3.10.1.29

The Contractor shall send a summary of other communications (e.g. phone conversations, instant messages, sms) between Contractor personnel and the representatives of the Commission, by email to both the Commission and the relevant representatives. The summary shall also be recorded in the associated tickets.

3.10.2. Configuration and Change Management

M 3.10.2.1The Contractor is responsible for implementing change and configuration management systems and processes following industry best practices and standards.

M 3.10.2.2The Contractor shall put under configuration and change management all the network elements, software, remote site equipment, NMS, documentation, teleport elements and any other relevant components.

M 3.10.2.3

The Contractor shall create configuration items for all of the relevant elements specified in article M 3.10.2.2. The configuration items shall contain all relevant information, data and relationships including but not limited to:

Unique identifier; Version; History of changes; Classification; Manufacturer; Serial number (where applicable); Licence information; Location information; Relationship to other configuration items, documents and services; Emergency related information; Inventory related information; Other associated documentation.

M 3.10.2.4 All configuration items shall be created and placed under strict change and configuration control prior their operational deployment.

M 3.10.2.5 The Contractor shall implement a Configuration Management Database and integrate all configuration items and associated elements into it.

M 3.10.2.6 The CMS and its associated subsystems shall be included in the business continuity and disaster recovery planning.

M 3.10.2.7 The Commission shall have access at all times to the CMS and all of its associated subsystems.

M 3.10.2.8 The Contractor shall perform periodic audits of the configuration items and the Configuration Management Database in order to maintain integrity, identify and

Page 90 of 116 12/02/016


address any discrepancies and/or errors.

M 3.10.2.9The Contractor shall record the outcomes of any configuration items and Configuration Management Database audit in an associated report. The report shall be available to the Commission at all times.

D 3.10.2.1 It is highly desirable for the Contractor to integrate the CMS with the associated systems of the Commission.

M 3.10.2.10 All changes in the GCI network are subject to the change management process and need to be approved by the Change Management Board.

M 3.10.2.11 The Contractor shall appoint its representatives to Change Management Board for the GCI network and specify their associated roles and responsibilities.

M 3.10.2.12All changes shall be compliant with the confidentiality, integrity and availability aspects and the associated security requirements specified in Section 3.14 (Security).

M 3.10.2.13 The Contractor shall submit change requests to the Commission for review and approval at least 30 days in advance.

All change requests shall contain all of the necessary information needed to evaluate the requests. This information shall include but is not limited to:

Unique identifier; Purpose and justification of the change; Associated risk analysis; Affected CIs and services; Date of submission; Initiator; Change owner; Estimated resources for implementation; Proposed change priority; Proposed date of implementation; Documentation to be updated as result of the change; Associated validation and verification testing; Rollback criteria and procedure; Any other relevant information.

M 3.10.2.14 The Contractor shall record all relevant change information and outcomes in an associated Change Record as part of the Change Management System.

M 3.10.2.15Should the Commission consider the changes to be major, it shall reserve the right to request a full or partial re-run of the acceptance testing for the associated system/sub-system. Should this acceptance testing fail to meet all of the criteria the Contractor shall immediately roll back to the previous working configuration.

M 3.10.2.16The Commission reserves the right to audit the configuration for any configuration items. The Contractor shall deliver all of the information requested by the Commission as part of the audit within 3 working days of receiving the request.

M 3.10.2.17 The Contractor shall evaluate all change requests of the Commission in a timely manner and provide feedback accordingly.

M 3.10.2.18The Contractor shall implement all changes requested and approved by the Commission in a timely manner, in accordance with the instructions of the Commission, while ensuring service availability and continuity.

M 3.10.2.19 The Contractor shall submit to the Commission for review and approval a list of standard changes which are limited in scope and risk. Once approved by the Commission, standard changes can be implemented without the approval of the

Page 91 of 116 12/02/016


Change Management Board until further notice.

M 3.10.2.20Emergency changes needed to restore service and address or mitigate ongoing service outages can be carried out without the explicit approval of the Change Management Board.

M 3.10.2.21 All changes, including standard and emergency changes, shall be reflected in the CMS and the associated configuration items.

M 3.10.2.22Following the implementation of a change, including emergency changes, the Contractor shall be responsible for carrying out all of the associated testing, validation and verification activities and organizing a post-implementation review.

M 3.10.2.23 The Document Management System and all of the associated documentation shall be integrated and subject to the change management process.

M 3.10.2.24 The Contractor shall implement a notification mechanism for the Commission with regard to the change management process.

D 3.10.2.2 The use of automated configuration management processes wherever possible and applicable is highly desirable and shall be considered an advantage.

M 3.10.2.25If changes at the remote site require a visit, the Contractor shall coordinate in a timely manner with the Commission and/or its representatives the necessary site access arrangements and permits. The Contractor shall provide all of the required documentation.

M 3.10.2.26All site maintenance activities or activities which may require assistance from the local representatives of the Commission shall be scheduled in agreement with the Commission and/or its local representatives during normal local working hours.

M 3.10.2.27 All site maintenance activities shall be carried out in accordance with local rules and regulations and take into account environmental concerns.

M 3.10.2.28

The Contractor shall deliver a Site Visit Report within 1 week, documenting the activities carried out at the site and containing any other relevant information with regard to local conditions at the remote site, including but not limited to:

Detailed electrical and cabling diagram; Photos of GCI equipment (indoor and outdoor) and associated connectivity,

cable paths, points of entry, grounding points and all other relevant aspects; Line of site documentation including relevant photos and diagrams; Photos and documentation of the local site infrastructure and its environment; Inventory details (including location of the spares); Other local conditions at the site.

M 3.10.2.29

Following the completion of maintenance the Contractor shall ensure that the remote site work has been performed in accordance with industry best practices and standards, the site is left in proper working condition and any residual materials are disposed of in accordance with local rules, regulations and environmental concerns.

3.10.3. Service Level Management

M 3.10.3.1The Contractor shall implement a comprehensive service level management strategy ensuring that all agreed services are delivered in accordance with the requirements and the agreed critical success factors and key performance indicators.

M 3.10.3.2 The Contractor shall appoint a Service Manager who shall be fully responsible for

Page 92 of 116 12/02/016


all service level management aspects.

D 3.10.3.1 It is highly desirable for the Service Manager to have ITIL expert level certification and at least 5 years of proven relevant experience.

M 3.10.3.3 The Contractor shall comply with all SLA requirements as defined in Section 4 (Service Level Agreement) and ensure that all service level targets are met.

M 3.10.3.4As part of the service level management the Contractor shall continuously monitor SLA compliance, identify any potential risks with regard to SLA breaches, implement mitigation actions and report to the Commission in a timely manner.

M 3.10.3.5The Contractor shall aim for continuous service improvement and propose for review and approval by the Commission service improvement plans including the Service Availability Improvement Plan.

M 3.10.3.6The Contractor shall deliver to the Commission all necessary information, reports and documentation proving that all SLA targets are met in accordance with the specification in Section 4 (Service Level Agreement).

M 3.10.3.7

The Contractor shall deliver to the Commission for review and approval all necessary service availability and performance statistics including but not limited to:

GCI monthly availability statistics; GCI 12 month rolling availability statistics; Rolling 12 month availability statics for each individual site; Traffic level statistics; Packet loss statics; QOS related statistics; Monthly event and incident statistics including meantime to respond and mean

time to restore metrics; Problem management related statics; Equipment failure statistics; Monthly inventory reports (including sparing); Monthly logistics and shipping reports; Regulatory compliance reports.

M 3.10.3.8The Contractor shall perform all of the necessary trend analyses with regard to performance and service level compliance in order to identify underlying issues and possible threats to achieving SLA targets.

M 3.10.3.9 The Contractor shall provide to the Commission with regular trend analysis reports and place them in the Document Management System.

M 3.10.3.10 The Contractor shall follow industry best practices and standards with regard to quality control and assurance for all services delivered to the Commission.

M 3.10.3.11The Contractor shall maintain all quality assurance documentation in the Document Management System. The quality assurance documentation shall be version controlled and available to the Commission at all times.

M 3.10.3.12 The Contractor shall provide to the Commission a comprehensive Service Catalogue detailing all of the available services, including but not limited to:

Site migration, installation and relocation; Site decommissioning; Site survey; Civil works and other site preparatory activities; UPS installation; Capacity commissioning and changes; Equipment acquisition and upgrades;

Page 93 of 116 12/02/016


Logistics services.

M 3.10.3.13 The Contractor shall update the Service Catalogue as required with any new services as agreed with the Commission.

M 3.10.3.14The Service Catalogue shall be maintained by the Contractor, placed in the version controlled Document Management System and be available to the Commission at all times.

M 3.10.3.15The Contractor shall implement and maintain all necessary capacity management information systems and tools necessary to monitor, report and analyse capacity management related aspects.

M 3.10.3.16 The Contractor shall deliver to the Commission for review and approval a Capacity Management Plan for the GCI network.

M 3.10.3.17 The Contractor shall update the Capacity Management Plan as required throughout the duration of the contract.

M 3.10.3.18

The Capacity Management Plan shall encompass the capacity analysis aspects with regard to the entire GCI network and its associated subsystems. The Contractor shall provide sufficient documentation in the Capacity Management Plan to demonstrate that the capacity allocated to the GCI network is sufficient and the requirements of the Commission are met.

M 3.10.3.19The Capacity Management Plan shall be periodically reviewed and the Contractor shall perform all necessary trending and forecast analyses. The trending and forecast analyses shall be delivered as a report for review by the Commission.

M 3.10.3.20The Contractor shall implement and maintain all necessary Availability Management Information Systems and tools to monitor and report on availability and SLA compliance.

M 3.10.3.21

As part of the Service Availability Improvement Plan the Contractor shall take into account and analyse all necessary aspects with regard to GCI service availability including but not limited to:

Projected life time and mean time between failures for individual components; Observed component failure rates; Mean time to repair; Fault tolerance, redundancy aspects and component failure impact analysis; Mean time to replace spares; Risk analysis; Other maintenance aspects; Link budget and power margins; Security aspects; Known Errors; Business continuity and disaster recovery aspects.

M 3.10.3.22The Contractor shall continuously update the Service Availability Improvement Plan throughout the duration of the contract and the Service Availability Improvement Plan shall be available to the Commission at all times.

M 3.10.3.23The Contractor shall implement all necessary actions and be compliant with all aspects of business continuity and disaster recovery as specified in Section 3.2.6 (Business Continuity Planning and Disaster Recovery).

3.10.4. Service Review Meetings

M 3.10.4.1 The Contractor shall organize all meetings and deliver all documents in accordance with the specifications in Section 2.3.5 (Service Operation and Management

Page 94 of 116 12/02/016


Phase).

3.11. Service Review and Technology Refresh

The scope of the Technology Refresh Phase is to implement up-to-date industry technology changes, resolve and address any obsolesce issues and ultimately achieve better cost efficiency for the GCI network.

M 3.11.1The Contractor shall provide all documents and deliverables for the Technology Refresh Phase in accordance with the specifications and schedules in Section 2 (Statement of Work).

D 3.11.1The Commission prefers the employment of ITIL and/or systems engineering methodologies. Therefore the use of ITIL and/or systems engineering methodologies will be considered an advantage.

D 3.11.2The Commission prefers the employment of PRINCE2 project management methodology for the Technology Refresh Phase. Therefore the use of PRINCE2 project management methodology will be considered an advantage.

The Technology Refresh Phase will include there major meetings, with all of their associated deliverables:

Technology Refresh Proposal Meeting;

Technology Refresh Approval Meeting;

Technology Refresh End of Implementation Meeting.

M 3.11.2The Technology Refresh Proposal, Technology Refresh Approval and Technology Refresh End of Implementation meetings shall be scheduled by the Contractor with the approval of the Commission and be held on the premises of the Commission.

M 3.11.3The Contractor shall submit a Technology Refresh Proposal to the Commission for review at least 60 days before the Technology Refresh Proposal Meeting in accordance with the schedules defined in Section 2 (Statement of Work).

M 3.11.4

The Technology Refresh Proposal shall include but is not limited to: Project Management Plan; Feasibility Study; Risk Management Plan; Quality Assurance Plan; High Level Design and Architecture for the proposed solution; Proof of Concept Test Plan; Integration, Verification and Validation Plan (including acceptance); Preliminary Implementation and Migration Plan.

M 3.11.5As part of the Technology Refresh Proposal the Contractor shall include a critical path analysis and associated critical success factors analysis for the review by the Commission.

M 3.11.6

The Contractor shall provide sufficient documentation in the Technology Refresh Proposal to demonstrate that the project is achievable in accordance with the requirements and the schedule in Section 2 (Statement of Work) and that there is sufficient tolerance built into the schedule accommodate unforeseen circumstances with a potential negative impact on the Technology Refresh project and product delivery.

Page 95 of 116 12/02/016


M 3.11.7Subsequent to review and approval of the Technology Refresh Proposal and its associated documents by the Commission, the Contractor shall commence the Technology Refresh Implementation Phase.

M 3.11.8

The Contractor shall implement the Technology Refresh Implementation Phase in a similar manner as for the migration/implementation of the GCI network. Implementation shall include all of the associated Project Planning, Design and PIVV phases. The respective phases shall be compliant with the requirements in Sections 3.2 (Project Planning), 3.3 (Design and Technical Review Phase) and 3.8 (Provisioning, Integration, Validation and Verification).

M 3.11.9During the Technology Refresh Phase the Contractor shall provide to the Commission a weekly Highlight Report detailing all activities performed and their associated outcomes.

M 3.11.10The Contractor shall provide a Technology Refresh Report to the Commission for review and approval with following the completion of the associated Project Planning, Design and PIVV phases.

M 3.11.11The Contractor shall provide satisfactory documentation as part of the Technology Refresh Report to demonstrate that the proposed solution is compliant with all GCI requirements and the proper process and methodology were followed.

M 3.11.12The Contractor shall deliver the Technology Refresh Report as part of the Technology Refresh Approval Meeting in accordance with the schedule in Section 2 (Statement of Work)

M 3.11.13Following approval of the Technology Refresh Report by the Commission, the Contactor shall deploy the technology refresh solution in the GCI network in accordance with the schedule in Section 2 (Statement of Work).

M 3.11.14The Contractor shall minimize service interruption to the GCI network during the Technology Refresh Migration Phase and comply with the requirements in Section 3.9.

M 3.11.15 The Contractor shall organize and document the Technology Refresh End of Implementation Meeting.

M 3.11.16 The Technology Refresh End of Implementation Meeting shall be scheduled in accordance with the relevant articles in Section 2 (Statement of Work).

M 3.11.17 As part of the Technology Refresh End of Implementation Meeting the Contractor shall deliver to the Commission the Technology Refresh Implementation Report.

M 3.11.18The Technology Refresh Implementation Report shall be reviewed by the Commission with the assistance of the Contractor and the outcomes of the review shall be recorded.

M 3.11.19The Technology Refresh End of Implementation Meeting shall conclude the Technology Refresh Phase and all associated activities, documents, plans and other deliverables shall be finalized by the Contractor.

3.12. Training

M 3.12.1 The Contractor shall provide training as described in the SOW on the specified dates.

3.12.1. Satellite and Terrestrial Technology Seminars

M 3.12.1.1 The Contractor shall provide 2 satellite and terrestrial technology seminars specific to the solutions employed for the GCI III network in accordance with the schedules

Page 96 of 116 12/02/016


in the SOW.

M 3.12.1.2Both satellite and terrestrial technology seminars shall be organized by the Contractor and delivered to the designated Commission personnel on the premises of the Commission in Vienna.

M 3.12.1.3The Contractor shall provide all documentation and training material for the satellite and terrestrial technology seminars to the Commission at least 15 days in advance for review and approval.

M 3.12.1.4 The Contractor shall provide during the satellite and terrestrial technology seminars demonstrations and hands-on sessions using live equipment.

M 3.12.1.5 The Contractor shall provide, configure and set up all necessary equipment for the satellite and terrestrial technology seminars.

M 3.12.1.6 The first satellite and terrestrial technology seminar shall comprehensively cover the solution as proposed by the Contractor in the High Level Design Document.

M 3.12.1.7The second satellite and terrestrial technology seminar shall be updated with all information contained in the Detailed Design Document and with any changes resulting from the design and PIVV phases.

3.12.2. Global Communications Infrastructure Overview and Stakeholders Workshop

M 3.12.2.1The Contractor shall provide 3 GCI overview and stakeholders workshops. The workshops shall provide a high level overview of the technologies used in the GCI, the system architecture and specific technological challenges.

M 3.12.2.2All 3 GCI overview and stakeholders workshops shall be organized by the Contractor and delivered to the designated Commission personnel on the premises of the Commission in Vienna. The workshops shall be scheduled in accordance with the relevant articles in the SOW.

M 3.12.2.3The Contractor shall provide all documentation and training material for the GCI overview and stakeholders workshops to the Commission at least 15 days in advance for review and approval.

M 3.12.2.4 The GCI overview and stakeholders workshops shall be updated by the Contractor to reflect any changes during the operating life of the GCI.

3.12.3. On-Site Station Maintenance Training

M 3.12.3.1 The Contractor shall prepare training materials, documentation and first level troubleshooting guides for the representatives of the Commission at remote sites.

M 3.12.3.2 All materials described in article M 3.12.3.1 shall be provided to the Commission for review and approval within 6 months of the EDC.

M 3.12.3.3The Contractor shall be responsible for updating the materials described in article M 3.12.3.1 with any changes in the GCI and distributing them to the representatives of the Commission at remote sites within 2 months of changes.

M 3.12.3.4The Contractor shall have all training materials described in article M 3.12.3.1 available in all of the official United Nations languages (English, Russian, French, Spanish, Chinese and Arabic).

M 3.12.3.5 At the commissioning of every site the Contractor shall deliver 1 day of on-site training to the representatives of the Commission. Training topics shall include but are not limited to:

Tutorial for communications technologies employed in the GCI III network;

Page 97 of 116 12/02/016


Overview of the GCI III network architecture; Presentation of the network elements present on site; First level troubleshooting training; Equipment replacement training.

M 3.12.3.6 At each on-site maintenance visit the Contractor shall provide a 2 hour refresher course to representatives of the Commission.

3.12.4. Training Reports

M 3.12.4.1 The Contractor shall provide to the Commission a training report within 2 weeks of completion of each training course.

3.13. End of Service Phase

The scope of the End of Service Phase is to cover the final phase of the GCI III network including service decommissioning and the associated activities.

It is envisaged that the End of Service Phase will start 1 year before the end of the contract, in accordance with the SOW schedule in Section 2 (Statement of Work).

M 3.13.1 The Contractor shall provide all documents and deliverables for the End of Service Phase in accordance with the specifications and schedules in the SOW.

M 3.13.2The Contractor shall manage the End of Service Phase as a separate project and shall present to the Commission for review and approval the associated Project Plan for Decommissioning in accordance with the specifications and schedules in the SOW.

D 3.13.1The Commission prefers the employment of PRINCE2 project management methodology for the End of Service Phase. Therefore the use of PRINCE2 project management methodology will be considered an advantage.

The end of service phase will include 2 major meetings, with all of their associated deliverables:

Start of Decommissioning Meeting;

End of Service Meeting.

M 3.13.3

The Project Plan for Decommissioning shall cover all actions and schedules for all decommissioning activities including but not limited to:

Site by site decommissioning; GCI infrastructure decommissioning; Handover of documentation; Handover of proprietary data; Handover of licences and other legal documents; Handover and/or disposal of assets (hardware, software); Knowledge transfer; Risk management; Reporting; Legal considerations; Confidentiality considerations with regards to the data and documents of the

Commission; Coordination Plan.

Page 98 of 116 12/02/016


M 3.13.4The Contractor shall decommission the GCI III network in a controlled manner in consultation with the Commission with regard to specific activities. All activities shall be carried out only with the prior approval of the Commission.

M 3.13.5The Project Plan for Decommissioning shall define, in relation to decommissioning activities, the roles and responsibilities of personnel appointed by the Contractor for the End of Service Phase.

M 3.13.6 The Project Plan for Decommissioning shall be available to the Commission at all times.

M 3.13.7

The Contractor shall maintain a Decommissioning Register containing all decommissioning records and ensure that the associated activities to decommission each product/system/subsystem in accordance with requirements has been recorded. The Decommissioning Register shall be available to the Commission at all times.

M 3.13.8 The Contractor shall maintain the Decommissioning Register and ensure that all records are time-stamped and versioned.

M 3.13.9Should a risk materialize during the End of Service Phase the Contractor shall be responsible for taking action as necessary to address it and record it in the Risk Register.

M 3.13.10

The Commission will specify, on a case by case basis, if the equipment at the remote sites shall be disposed in accordance with local rules and regulations (and/or environmental considerations) or transferred to the Commission and/or its representatives. The Contractor shall comply with the request of the Commission and follow local rules and regulations accordingly regarding both disposal and transfer.

M 3.13.11 The Contractor shall deliver all access and administrative credentials for all equipment and its associated software specified in article M 3.13.10.

M 3.13.12 The Contractor is required to decommission all the remote sites, IDC and backup IDC GCI equipment in accordance with the Project Plan for Decommissioning.

M 3.13.13The Contractor shall deliver all GCI III related documentation to the Commission. The documentation shall be the property of the Commission together with its associated intellectual property rights.

M 3.13.14

The Contractor shall deliver the GCI III Knowledge Management Database, including but not limited to:

Best practices, Known errors, Standard operating procedures, Wiki information, Lessons learned, Troubleshooting guides.

The Knowledge Management Database shall be delivered to the Commission in an open standard format.

M 3.13.15

The Contractor shall deliver the GCI III specific data, including but not limited to: NMS data (including traffic flow data), Configuration management data, Configuration files, Logs.

The GCI III specific data shall be delivered to the Commission in an open standard format.

M 3.13.16 Flowing the handover of GCI III specific data as specified in article M 3.13.15 the Contractor shall destroy and dispose in a secure manner all copies of the GCI III

Page 99 of 116 12/02/016


specific data.

M 3.13.17The Contractor shall deliver all GCI III related frequency licences to the Commission. The licences shall be the property of the Commission and/or its representatives depending on local rules and regulations.

M 3.13.18The Contractor shall fully cooperate with the Commission and/or its representatives in accordance with the instructions for the Commission for the purpose of migrating the GCI III network and handing over operations at the end of the contract.

3.13.1. Start of Decommissioning Meeting

The intended scope of the Start of Decommissioning Meeting is mainly the initiation of the Decommissioning Phase and the review of associated documents and plans.

M 3.13.1.1 The Contractor shall organize and document the Start of Decommissioning Meeting.

M 3.13.1.2 The Start of Decommissioning Meeting shall be scheduled in accordance with the relevant article in the SOW.

M 3.13.1.3As part of the Project Review Meeting the Contractor shall deliver to the Commission the following documents:

Project Plan for decommissioning.

M 3.13.1.4The documents delivered in accordance with article M 3.13.1.3 shall be reviewed by the Commission with the assistance of the Contractor at the Start of Decommissioning Meeting and the outcomes of the review shall be recorded.


3.13.2. End of Service Meeting

The intended scope of the End of Service Meeting is mainly the finalization of the End of Service Phase and the handover of service, documentation and GCI III specific data to the Commission.

M 3.13.2.1 The Contractor shall organize and document the End of Service Meeting.

M 3.13.2.2 The End of Service Meeting shall be scheduled in accordance with the relevant article in the SOW.

M 3.13.2.3 As part of the End of Service Meeting the Contractor shall deliver to the Commission the End of Service Report with all associated components.

M 3.13.2.4The End of Service Report shall be reviewed by the Commission with the assistance of the Contractor at the End of Service Meeting and the outcomes of the review shall be recorded.

M 3.13.2.5 Prior to the End of Service the Contractor shall deliver all the documentation and GCI III specific data to the Commission in accordance with the requirements.

M 3.13.2.6The End of Service Meeting shall conclude the End of Service Phase and all the associated actions, documents, plans and other deliverables shall be finalized by the Contractor.

Page 100 of 116 12/02/016


3.14. Security

M 3.14.1The Contractor shall have in place a security policy which is conformant with either ISO 27000 and/or National Institute of Standards and Technology (NIST) security standards.

M 3.14.2 As part of the bid the Contractor shall deliver to the Commission a Security Plan for the GCI network.

M 3.14.3

The Security Plan specified in article M 3.14.2 shall include, but is not limited to, the following:

Contractor key personnel for GCI security and their associated roles and responsibilities;

Confidentiality, integrity and availability aspects; Security control mechanisms with a special focus on boundary security and

interfaces between different parties; Specification of security products and services including those delivered by

subcontractors; Access Control Policy; Identification and Authentication Policy; Security Risk Management Plan; Security Incident Response Plan; Security Contingency Plan; Configuration management (security related); Training and Security Awareness Plan; Security Test Plan; Security Information and Event Management (SIEM).

M 3.14.4 The Contractor shall update the Security Plan specified in article M 3.14.2 as necessary.

M 3.14.5 The Security Plan shall be available to the Commission at all times.

M 3.14.6

During the PIVV phase, in accordance with the schedules specified in the Section 2 (Statement of Work), the Contractor shall perform all security testing specified in the Security Test Plan including, but not limited to:

Network scanning; Vulnerability scanning; Penetration testing.

M 3.14.7 The Contractor shall record the results of all security testing in the Quality Register.

M 3.14.8Should any tests that have a potential impact on the delivery of the GCI network fail, the Contractor shall inform the Commission in writing via an exception report and update the Risk Register accordingly.

M 3.14.9The Contractor shall deliver a Security Test Report documenting the results of the security testing at the PIVV End Meeting for review and approval by the Commission in accordance with the specifications and schedule detailed in the Statement of Work.

M 3.14.10 The Contractor shall perform periodic security assessments and audits for the GCI network.

M 3.14.11The security assessments and audits specified in article M 3.14.10 shall be performed by an independent organization and the results shall be made available to the Commission.

M 3.14.12 The Commission shall reserve the right to perform an independent security audit and the Contractor shall provide all necessary support.

Page 101 of 116 12/02/016


M 3.14.13 The security assessments and audits specified in article M 3.14.10 shall be performed at least every 3 years.

M 3.14.14As part of the Technology Refreshment Proposal the Contractor shall submit an updated Security Plan in accordance with the schedule defined in the Section 2 (Statement of Work), covering all the proposed changes.

M 3.14.15 The Contractor shall retest the new security solution resulting from the implementation of the Technology Refreshment Proposal.

M 3.14.16 The Contractor shall follow all industry security best practices throughout the duration of the contract.

M 3.14.17

The best practices as specified in article M 3.14.16 shall include but are not limited to the following:

The Contractor shall implement stateful firewall functionality at each remote site and at each security boundary for the GCI network.

The Contractor shall implement end to end encryption between the remote sites, the IDC and any other GCI entities, using the IPsec protocol.

The minimal encryption standard for the end to end IPsec encryption shall be AES with a key length of at least 256 bits and a hashing SHA-2 family of hash algorithm. Other implementations shall be agreed beforehand with the Commission.

The Contractor shall log all security incidents and the logs shall be available to the Commission at all times.

All the authentication and management of the GCI network elements shall be encrypted.

The Contractor shall log all authentication and configuration changes to any of the GCI network elements. All authentication and configuration logs shall be available to the Commission at all times.

The Contractor shall implement DOS and DDOS mitigation mechanisms.

D 3.14.1 A valid ISO 27000 certification is desirable and shall be considered an advantage.

D 3.14.2It shall be considered an advantage if Contractor personnel in the GCI III team hold active Certified Information Systems Security Professional (CISSP) and Certified Information Security Manager (CISM) certification.

D 3.14.3 Two-factor authentication for the GCI network elements is desirable and shall be considered an advantage.

D 3.14.4 Supplementary encryption with no overhead added on the satellite path is desirable and shall be considered an advantage.

D 3.14.5 Jamming resistant coding techniques (e.g. CDMA) over the satellite segment are highly desirable and shall be considered an advantage.

D 3.14.6 IDS/IPS and threat prevention functionality at the remote sites is desirable and shall be considered an advantage.

Page 102 of 116 12/02/016


4. Service Level Agreement


The SLA defines the specific performance metrics and key performance indicators (KPIs) for GCI III. Service availability is the principal quantitative measure of network and service performance. Tasks that require specific actions to be taken by the Contractor include the following:

Identification and resolution of critical, major, minor and redundancy failures;

Computation of SLA penalties;

Replacement of spare equipment;

Escalation of incidents in accordance with established procedures;

Planned maintenance;

Resolution of non-conformance issues;

Notification of planned service outages;

Delivery of network monitoring data;

Response to change requests from the Commission;

Response to requests for information from the Commission.

The SLA also defines actions to be taken by the Contractor in specific circumstances and the penalties to be imposed on the Contractor if the performance metrics are not attained or the requisite actions are not taken.

4.2. Performance Metrics and Key Performance Indicators

M 4.2.1 The Contractor shall comply with all of the SLA metrics.

4.2.1. Service Availability

M 4.2.1.1 Service availability and the associated performance criteria shall be monitored continuously for each remote site, each satellite region and each ISN link.

MD 4.2.1.1Service at a remote site shall be defined as ‘available’ if all performance metrics in Table 4.1 are satisfied simultaneously and if the GCI link is capable of transporting user traffic in all traffic classes.

M 4.2.1.2Service availability is the amount of time the service is SLA compliant within a 1 year period. It is expressed as a percentage. Pursuant to the requirements described in the SLA, the Contractor shall calculate and report the service availability metrics.

M 4.2.1.3 The Contractor shall provide service management to ensure performance metrics as specified in Table 4.1.

M 4.2.1.4 The Contractor shall guarantee that the service availability for all satellite remote sites is equal to or greater than 99.5%.

M 4.2.1.5The Contractor shall guarantee that the service availability for terrestrial remote sites and all other connections to the terrestrial core network infrastructure is equal to or greater than 99.95%.

M 4.2.1.6 The Contractor shall calculate service availability on a site by site basis at the end

Page 103 of 116 12/02/016


of each month over a rolling 1 year period.

M 4.2.1.7 The Contractor shall calculate regional service availability on a region by region basis at the end of each month over a rolling 1 year period.

M 4.2.1.8 The Contractor shall calculate the availability of the NMS at the end of each month over a rolling 1 year period.

M 4.2.1.9 The Contractor shall calculate the availability of terrestrial links at the end of each month over a rolling 1 year period.

M 4.2.1.10 The Contractor shall provide for review and acceptance by the Commission a Web based tool for the calculation of all SLA penalties.

M 4.2.1.11 Input for the calculation tool shall be exclusively based on NMS reports and the trouble ticket system of the Contractor.

M 4.2.1.12The calculation tool specified in article M 4.2.1.10 shall be available to the Commission at all times and the penalty assessment shall be performed by the Commission.

M 4.2.1.13 The calculation tool specified in article M 4.2.1.10 shall maintain a history of all calculations. These calculations shall be available to the Commission at all times.

M 4.2.1.14The calculation tool specified in article M 4.2.1.10 shall be validated before deployment. The associated validation report shall be reviewed and approved by the Commission prior to the start of operations.

M 4.2.1.15Following acceptance by the Commission the calculation tool specified in article M 4.2.1.10 shall be placed under strict configuration management. Any changes to the calculation tool shall be validated, and the associated validation report shall be reviewed and approved by the Commission.

M 4.2.1.16 Maintenance, configuration and upgrades of the calculation tool specified in article M 4.2.1.10 shall be the sole responsibility of the Contractor.

M 4.2.1.17Maintenance and operation of the calculation tool specified in article M 4.2.1.10 shall be included in business continuity and disaster recovery planning of the Contractor.

Table 4.10. End to End Service Performance Metrics

Network Infrastructure Connecting Site

Satellite Remote Sites

Terrestrial Remote Sites

Performance Criteria Performance Metrics

Packet Loss Rate* 0.1% 0.05%

Response Time (two way) 5 seconds 1 second

Guaranteed Minimum Average Throughput for both transmit and receive respectively *

Minimum of CIR**

* The packet loss rate, response time and the guaranteed minimum average throughput shall be calculated over a 5 minute measurement interval.

** The transmit and receive CIRs for each site are specified in the Site Profile Table.

4.2.2. Service Outages

MD 4.2.2.1 A service outage is defined as the time period when service does not meet all of

Page 104 of 116 12/02/016


the performance specifications defined in Table 4.1 or when a GCI link is not able to transport user traffic. A service outage ends when all of the performance specifications in Table 4.1 are met and the GCI link is capable of transporting user traffic.

MD 4.2.2.2An intermittent service outage is defined as a series of correlated service outages that occur at least twice within a 1 hour sliding window. The duration of an intermittent service outage is the time between the start of the first event and the end of the last event as derived from the trouble ticket system and NMS reports.

MD 4.2.2.3

The start of an outage shall also be derived from the following indirect measurements, but is not limited to:

Failure of a link or network element to pass operational traffic where redundancy was not present or it did not successfully take over. The start of the outage shall also be determined from e.g. NMS measurements, log time stamps or SNMP traps issued by the affected network element or adjacent ones.

Change in a routing protocol adjacency that prevents operational data from reaching the IDC. The start of the outage shall also be determined from e.g. NMS measurements, log time stamps or SNMP traps issued by the affected network element or adjacent ones.

A measured packet error rate at an interface passing operational traffic that exceeds the specified packet loss criteria.

The moment in which the measured Eb/N0 for a satellite link falls under the official vendor specified value for a BER of 10E-8, given the specific modulation and error correcting algorithms used for that particular link.

The general inability of a GCI link to transmit data as a result of, e.g., failed configuration changes, design failures or human error.

M 4.2.2.1 The NMS shall be configured and capable of automatically identifying, recording and handling intermittent outages.

M 4.2.2.2

The Contractor shall be accountable for all service outages with only the following exemptions:

Loss of AC power at a remote site. If the Contractor is requested to deploy a UPS at the site the Contractor will only be exempted AC power loss time that exceeds the contracted UPS backup time.

Loss of DC power at a remote site. The Contractor is expected to have full redundancy with no single point of

failure at remote sites. If the Contractor is denied access to a remote site for more than 15 days and as a result is unable to restore redundancy following an outage the Contractor will be exempt from associated SLA penalties from the 15th day onwards until access is granted. For remote sites where the Commission waives the full redundancy requirement the Contractor will be exempt from penalties after 24 hours. However, the Contractor’s inability to travel, e.g. owing to lack or refusal of a visa, shall not be considered denial of access to a remote site.

M 4.2.2.3The exemptions specified in article M 4.2.2.2 shall be taken into consideration by the Commission only after the Contractor submits a formal written request to the Commission. Such a request shall be submitted as soon as possible after the potential exemption conditions occur.

M 4.2.2.4When requesting an exemption for a service outage as defined in article M 4.2.2.2 the Contractor shall submit all of the necessary documentary evidence for review and approval by the Commission within 15 days of the restoration of service. Failure to do so will nullify the right of the Contractor to an exemption.

M 4.2.2.5 If an exemption is awarded, the exemption period shall begin at the start of the outage or on the first day of the month for outages that cross month boundaries for

Page 105 of 116 12/02/016


the purpose of SLA penalty calculations.

M 4.2.2.6The Contractor shall include all intermittent service outages and all outages derived from the measurement of indirect parameters specified in article MD 4.2.2.3 in the calculation of service availability.

M 4.2.2.7SLA penalties shall be calculated on the basis of service availability as defined in articles MD 4.2.2.3 and M 4.2.2.3, to which the exemptions as defined in article M 4.2.2.2 are applied.

4.2.3. Other Performance Metrics

4.2.3.1. Major Failures

MD 4.2.3.1.1 Major failures are all failures that affect the service availability of individual remote sites.

MD 4.2.3.1.2

Major failures are also failures that result in the loss of redundancy and have the potential to develop into a critical failure should a single network element or link fail, for:

Terrestrial network infrastructure; Teleports; NOC or help desk access to GCI resources; IDC; NMS.

M 4.2.3.1.1 The Contractor shall resolve all major failures within 24 hours.

M 4.2.3.1.2

Should the Contractor fail to resolve a major failure within 24 hours, the Contractor shall present to the Commission a root cause analysis report including but not limited to:

Cause of the outage; Remedial actions taken; Reasons for delayed service restoration; Future action to be taken by the Contractor to improve the service restoration

time.

M 4.2.3.1.3 The NOC shall report to the Commission all major failures in the network within 30 minutes from the start of the failure.

M 4.2.3.1.4 The NOC shall provide to the Commission an initial diagnosis for all major failures within 2 hours from the start of the failure.

M 4.2.3.1.5

If a major failure is not resolved within 24 hours from the start of the major failure, the NOC manager shall issue a written statement to the Commission including:

Reasons for the delay in restoration; Remedial actions taken; Resources allocated to address the failure.

M 4.2.3.1.6 The NOC shall provide daily status updates for all major failures until the respective major failures have been resolved.

M 4.2.3.1.7

If a major failure is not resolved within 15 days the Programme Manager of the Contractor shall issue a written statement including:

Actions taken to restore service; Actions currently under way to restore service; Follow-up actions to be taken to minimize the duration of the major failure.

M 4.2.3.1.8 If a major failure is not resolved within 30 days it shall be treated as non-

Page 106 of 116 12/02/016


conformance to the contract and the issue shall be escalated to the designated high level management of the Contractor.

4.2.3.2. Critical Failures

MD 4.2.3.2.1Critical failures are all failures that affect service availability for more than 50% of the remote sites in one region or more than 20% of the remote sites in the GCI network.

MD 4.2.3.2.2 Failure of the NMS to collect monitoring data shall be considered a critical failure.

M 4.2.3.2.1 The Contractor shall resolve all critical failures within 1 hour.

M 4.2.3.2.2

Should the Contractor fail to resolve a critical failure within 1 hour the Contractor shall present to the Commission a root cause analysis report including but not limited to:

Cause of the outage; Remedial actions taken; Reasons for the delay in service restoration; Future action to be taken by the Contractor to improve the service restoration

time.

M 4.2.3.2.3 The NOC shall report to the Commission all critical failures within 15 minutes from the start of the failure.

M 4.2.3.2.4 The NOC shall provide an initial diagnosis for all critical failures within 45 minutes from the start of the failure.

M 4.2.3.2.5

If not resolved within 1 hour from the start of the critical failure the NOC manager shall issue a written statement to the Commission including:

Reasons for the delay in service restoration; Remedial actions taken; Resources allocated to address the failure.

M 4.2.3.2.6 The NOC shall provide hourly status updates for all critical failures until the respective critical failures have been resolved.

M 4.2.3.2.7

If a critical failure is not resolved within 3 hours the Programme Manager of the Contractor shall immediately issue a written statement to the Commission including:

Actions taken to restore service; Actions currently under way to restore service; Follow-up actions to be taken to minimize the duration of the critical failure.

M 4.2.3.2.8If a critical failure is not resolved within 6 hours it shall be treated as non-conformance to the contract and the issue shall be escalated to the designated high level management of the Contractor.

4.2.3.3. Minor Failures

MD 4.2.3.3.1 Minor failures are all other failures which do not affect service availability and do not present a risk of developing into a critical failure.

M 4.2.3.3.1 The Contractor shall resolve all minor failures within 15 days.

M 4.2.3.3.2 The NOC shall report to the Commission all minor failures within 4 hours from the start of the failure.

M 4.2.3.3.3 The NOC shall provide an initial diagnosis for all minor failures within 24 hours from the start of the failure.

Page 107 of 116 12/02/016


M 4.2.3.3.4

If not resolved within 15 days from the start of a minor failure the NOC manager shall issue a written statement containing:

Reasons for the delay in service restoration; Remedial actions taken; Resources allocated to address the failure.

M 4.2.3.3.5 If not resolved within 15 days from the start of a minor failure the NOC shall provide weekly status updates until the respective minor failure has been resolved.

M 4.2.3.3.6

If a minor failure is not resolved within 90 days the Programme Manager of the Contractor shall issue a written statement containing:

Actions taken to restore service; Actions currently under way to restore service; Follow-up actions to be taken to minimize the duration of the minor failure.

4.2.3.4. Spare Equipment

M 4.2.3.4.1The Contractor shall provide a monthly report detailing the current status of spare equipment for all remote sites, teleports, the IDC, the NMS and the terrestrial core network infrastructure.

4.2.3.5. Spare Equipment at Remote Sites

M 4.2.3.5.1

The Contractor shall replace all spare equipment at remote sites that has been damaged within 15 days of being identified or substituted. Replacement is considered complete when the spare equipment is in the possession of the remote site point of contact or of the Commission if the Commission decides to receive the spare equipment.

4.2.3.6. Spare Equipment at Teleports, the International Data Centre and in the Terrestrial Core Network Infrastructure

M 4.2.3.6.1The Contractor shall replace spare equipment at teleports, the IDC or in the terrestrial core network infrastructure that has been damaged within 24 hours of being identified or substituted.

4.2.3.7. Planned Service Outages

M 4.2.3.7.1The Contractor shall notify the Commission in writing of any planned service outage by submitting a service outage request to the Commission for review and approval at least 15 days in advance of any planned service outage.

M 4.2.3.7.2

The service outage request shall include but is not limited to the following: Changes and/or actions to be taken; Expected duration of the service outage and the services impacted; Risk analysis; Rollback criteria should the changes and/or actions not proceed as planned.

M 4.2.3.7.3 Written approval shall be obtained from the Commission prior to proceeding with the planned service outage.

M 4.2.3.7.4 The Commission shall assess whether planned service outages were planned and documented in a timely manner during its quarterly assessment of activities.

Page 108 of 116 12/02/016


4.2.3.8. Network Monitoring Data

M 4.2.3.8.1 The Contractor shall ensure that network monitoring data are available at the GCI‒IDC interface at least 99.99% of the time.

M 4.2.3.8.2 The Contractor shall provide network monitoring data at the GCI‒IDC interface within 10 seconds of real time.

4.3. Remedial Actions

M 4.3.1In the event of recurring service failures at a remote site that result in a non-conformance issue, the Contractor shall implement at its own expense an alternative technology or service and restore the remote site to full service availability.

M 4.3.2The remedial action specified in article M 4.3.1 shall be implemented within 60 days of the Commission’s request and maintained until the underlying problem and the non-conformance issue have been successfully resolved.

M 4.3.3All costs resulting from the implementation of the remedial action specified in article M 4.3.1 are the responsibility of the Contractor and shall not be reimbursed by the Commission.

M 4.3.4

In the event of the Contractor failing to migrate any remote site by the end of the service migration period as defined in the SOW, the Contractor shall implement at its own expense an alternative technology or service by the end of the service migration period. The alternative technology or service will remain in place until the remote site is migrated and accepted by the Commission.

M 4.3.5

In the event of the Contractor failing to commission a new site within the required period the Contractor shall implement at its own expense an alternative technology or service within the required period. This alternative technology or service will remain in place until the new site is commissioned and accepted by the Commission.

M 4.3.6Failure to satisfactorily comply with articles M 4.3.4 and M 4.3.5 shall result in the application of SLA penalties, including a continuous outage penalty starting on the agreed commissioning date.

M 4.3.7In the event of the Contractor failing to relocate an existing site within the required period the Contractor shall implement at its own expense an alternative technology or service until the site is relocated and accepted by the Commission.

M 4.3.8Failure to satisfactorily comply with article M 4.3.7 shall result in the application of SLA penalties, including a continuous outage penalty starting on the agreed relocation date.

M 4.3.9In the event of the Contractor failing to decommission a remote site within the required period the Contractor shall forfeit the full monthly cost of that site starting on the agreed decommissioning date.

4.4. Performance Penalties

M 4.4.1 The Contractor shall be subject to penalties for failure to meet the performance criteria.

4.4.1. Cumulative Service Outages

M 4.4.1.1 The Contractor shall calculate the cumulative service outage for the previous 1 year

Page 109 of 116 12/02/016


period at the end of each month on a site by site basis.

M 4.4.1.2 The Contractor shall be subject to a performance penalty for each site where the cumulative service outage threshold specified in Table 4.2 is exceeded.

MD 4.4.1.1Each time the Contractor pays a cumulative service outage penalty, the equivalent number of penalized outage hours shall be deducted from future calculations of cumulative service outages.

Table 4.11. Performance Penalties for Cumulative Service Outages

Cumulative Service Outage Threshold (hours) Performance Penalty

First 43.8 hours – for satellite remote sites or Internet VPN remote sites

1 × P

Every additional complete 43.8 hours following the first 43.8 hours – for satellite remote sites or Internet VPN remote sites

1 × P

First 4.38 hours – for terrestrial remote sites 1 x P

Every additional complete 4.38 hours following the first 4.38 hours - for terrestrial remote Sites

1 x P

4.4.2. Continuous Service Outages

M 4.4.2.1 The Contractor shall be subject to a performance penalty for each site where the continuous service outage threshold specified in Table 4.3 is exceeded.

Table 4.12. Performance Penalties for Continuous Service Outages

Continuous Service OutageThreshold (hours)

Performance Penalty

First 72 hours 4 × P

Every additional complete 12 hours following the first 72 hours until 168 hours

1 × P

Every additional complete 6 hours following the first 168 hours

1 × P

M 4.4.2.2 The continuous service outage penalty shall be in addition to the cumulative service outage SLA penalty incurred as a result of the outage.

4.4.3. Regional Service Outages

MD 4.4.3.1A regional service outage represents an event or time period where more than 50% of the remote sites in a single region do not meet one of the end to end service performance metrics as defined in Section 4.4.2 (Continuous Service Outages), including service degradation.

MD 4.4.3.2 The regional service outage penalty shall be in addition to the cumulative service outage penalty incurred as a result of the outage.

Page 110 of 116 12/02/016


M 4.4.3.1The Contractor shall be subject to performance penalties for all remote sites in the affected region where the regional service outage threshold specified in Table 4.4 is exceeded.

Table 4.13. Performance Penalties for Regional Service Outages

Regional Service OutageThreshold (hours)

Performance Penalty

First 2 hours 0.25 × P for each site in the affected region

Every additional complete hour following the first 2 hours

0.1 × P for each site in the affected region

4.4.4. Failure to Replace Spare Equipment and Restore Redundancy

Spare Equipment for Remote Sites

M 4.4.4.1 In the event that the Contractor fails to replace spare equipment at remote sites within 15 days the Contractor shall be subject to penalties specified in Table 4.5.

Table 4.14. Penalties for Delays in Replacing Spare Equipment at Remote Sites

Threshold for Delays in the Replacement of Spare Equipment at Remote Sites (days)

Performance Penalty

First 15 days 0.25 × P

Every additional 7 days thereafter 0.25 × P

Spare Equipment for Teleports, the Core Network Infrastructure and the IDC

M 4.4.4.2In the event that the Contractor fails to replace within 48 hours spare equipment for the network elements in the teleports, the terrestrial core network infrastructure and the IDC that have the potential to impact multiple sites in case of failure, the Contractor shall be subject to penalties as specified in Table 4.6.

Table 4.15. Penalties for Delays in Replacing Spare Equipment for Teleports, the Terrestrial Core Network Infrastructure and the International Data Centre

Threshold for Delays in the Replacement of Spare Equipment for Teleports, the Terrestrial Core Network Infrastructure and the IDC (hours)

Performance Penalty

First 48 hours 4 × Pmin*

Every additional 6 hours following the first 48 hours

1 × Pmin*

* Pmin is the minimum penalty unit as defined in article M 4.4.6.3.

Page 111 of 116 12/02/016


4.4.5. Network Monitoring Data

M 4.4.5.1 The Contractor shall be subject to penalties if network monitoring data is unavailable for more than the number of hours specified in Table 4.7.

Table 4.16. Performance Penalties for Network Monitoring Data

Network Monitoring DataUnavailability (hours)

Performance Penalty

N (N-1) × PNMS*

* PNMS is the unit of penalty defined in article MD 4.4.6.2. N is the number of hours that the network monitoring data is unavailable. A fraction of an hour shall be counted as 1 hour.

M 4.4.5.2

In the event of an NMS outage where monitoring data has not been permanently lost, the Contractor has a grace period of 5 days to restore the monitoring data to avoid penalties. All data missing from the NMS after the 5 day grace period shall be considered lost for all intents and purposes and the Contractor shall be penalized as specified in article M 4.4.5.1.

M 4.4.5.3In the event that the NMS is collecting all monitoring data but the Commission does not have access to the NMS the Contractor shall be subject to a performance penalty as specified in Table 4.8.

Table 4.17. Performance Penalties for Network Monitoring Access

Network Monitoring AccessUnavailability (hours)

Performance Penalty

N (N-1)/2 × PNMS

4.4.6. Calculation of the Unit of Penalty

MD 4.4.6.1The unit of penalty P dollar value shall be calculated for each remote site as a function of the remote site specific sum of CIR values for the inbound and outbound traffic as specified in Table 4.9.

Table 4.18. Unit of Penalty Dollar Value

CIR (inbound + outbound) (kbps)

Performance Penalty

Between 0 and 50 kbps P = 2000 USD

Over 50 kbps P = 2000 USD + 500 USD for every 10 kbps increment in CIR

MD 4.4.6.2 The unit of penalty PNMS dollar value is 1000 USD.

MD 4.4.6.3 The unit of penalty Pmin dollar value is 500 USD.

Page 112 of 116 12/02/016


4.5. Contract Non-Conformance and Chronic Breaches of Service Level Agreement

M 4.5.1 The Contractor shall identify all non-conformance issues and escalate them to the Commission and to the designated high level management of the Contractor.

M 4.5.2 The Contractor shall take all necessary remedial actions as specified in Section 4.3 (Remedial Actions) in order to address and mitigate all non-conformance issues.

M 4.5.3

For all non-conformance issues the Contractor shall issue a periodic report to the Commission until the non-conformance issue is successfully addressed. The report shall include but is not limited to:

Impact analysis; Associated risk analysis; Remedial actions taken; Resources allocated to address the issue; Designated contact persons and their roles and responsibilities; Estimated time lines for the implementation of the remedial actions; Mitigation actions taken to reduce the impact.

The periodicity of the report will be specified by the Commission and the Contractor shall comply with the specifications of the Commission.

M 4.5.4 All major failures as defined in Section 4.2.3.1 which are not resolved within 30 days shall be considered and addressed as a non-conformance issue.

M 4.5.5 All critical failures as defined in Section 4.2.3.2 which are not resolved within 6 hours shall be considered and addressed as a non-conformance issue.

M 4.5.6 If more than 20% of the remote sites are in breach of the SLA within a 6 rolling month period it shall be considered and addressed as a non-conformance issue.

M 4.5.7 If the availability figure for the GCI network in a 12 month rolling period falls under 99.5% it shall be considered and addressed as a non-conformance issue.

M 4.5.8If the monthly availability figure for the GCI network fails to meet 99.5% for 3 consecutive months it shall be considered and addressed as a non-conformance issue.

M 4.5.9 If the availability figure for any single remote site in a 12 month rolling period falls under 90% it shall be considered and addressed as a non-conformance issue.

M.4.5.10In the event that the Contractor continuously fails to meet the SLA requirements and/or is in non-conformance with the technical requirements outlined in this Section 4 (Service Level Agreement), the Commission may opt to terminate the Contract.

Page 113 of 116 12/02/016


5. Benchmarking

M 5.1

To ensure that the Commission is obtaining competitive pricing and levels of service for the Work, after the Contract has been in force for twenty-four (24) months the Commission shall have the right, at its own cost and expense and no more frequently than once during any twelve (12) month period, to obtain the services of an independent third party reasonably acceptable to the vendor and subject to the confidentiality requirements contained in Section 12 of Annex A, to benchmark the costs for the Work provided under this Contract (including initial investments, performance, service levels, and charges) against other vendors performing similar Work

M 5.2

If such benchmarking results in an indication that the Commission is paying more than market competitive pricing and/or receiving less than competitive service levels, the Commission shall inform the Contractor thereof in writing and request the Contractor to adjust the pricing and levels of Work to the Commission’s benchmark (based on the outcome of the independent third party’s evaluation mentioned above) within 30 days of receipt of the Commission’s request.

Page 114 of 116 12/02/016


Attachment I Technical Description of GCI II

Scope

This attachment provides a high level description of the current generation of the Global Communications Infrastructure (GCI). A description of GCI II is also available on the CTBTO public web site:http://www.ctbto.org/verification-regime/the-global-communications-infrastructure/page-1-gci/.

Technical Description

GCI II has been in operation since 2007, after a successful migration from the first generation GCI. Currently the entire GCI network is provisioned and operated by a single Contractor. The GCI II network:

Uses Internet Protocol (IP) based network infrastructure;

Uses terrestrial and satellite communications including the Internet;

Operates in approximately 100 countries;

Connects more than 250 remote sites to the International Data Centre (IDC) Connects 5 to 10 high bandwidth National Data Centres (NDCs) or communications nodes to the IDC;

The current service availability targets for GCI II are 99.5% for remote sites connected using VSAT and 99.95% for remote sites connected via terrestrial links.

Connects remote sites located in isolated, extreme environments;

Supports near real time data transport;

Currently transports data volumes up to 36 gigabytes (GB) per day

Provides end to end quality of service for several classes of service;

Provides proactive network monitoring from a 24×7×365 network operations centre (NOC);

Uses commercial off the shelf technology (hardware and software) supplemented by custom network management system (NMS) software components.

The GCI is currently built on a C band and Ku band VSAT infrastructure, complemented by 6 dedicated terrestrial circuits and slightly more than 30 public Internet virtual private network (VPN) connections. Satellite technology has proven its value to reach remote and underdeveloped locations lacking infrastructure. Terrestrial technology is used when it is feasible and more economical solution than satellite technology is available. Internet VPN technology is currently used when the first two options are not technically feasible or when it can deliver the same performance at a considerably lower cost.

Considering the difficulty and cost of sending personnel to maintain remote sites, a number of remote sites are provided with automatic failover to a backup circuit in the following combinations:

Dual VSATs, i.e. hot standby VSAT backup;

One VSAT and one Internet VPN connection;

Redundant dedicated terrestrial circuits in primary/secondary configuration;

One or two dedicated terrestrial circuit(s) plus one backup Internet VPN connection.

Page 115 of 116 12/02/016

http://www.ctbto.org/verification-regime/the-global-communications-infrastructure/page-1-gci/


The VSAT infrastructure is divided into six satellite regions landing at two teleports located in Europe and North America. The teleports are interconnected by dedicated Multiprotocol Label Switching (MPLS) terrestrial backbone backed up by Internet VPN. The remote site equipment consists of iDirect 3000 based VSATs (operating C band and Ku band), Prodelin antennas, and Cisco routers which provide embedded Ethernet switch ports to interconnect to the International Monitoring System Facilities or to National Data Centres equipment. Both alternating current (AC) and direct current (DC) equipment is supplied depending on the present power infrastructure. For AC sites, an uninterruptible power supply (UPS) with capacity of either 2 or 12 hours is supplied.

The dedicated terrestrial circuits to six remote sites employ redundant MPLS network infrastructure for the interconnectivity with IDC. Internet VPN links are currently terminated using Cisco routers. The Internet access is currently provided by the remote site.

To address the availability requirement, every remote site is provided with a complete set of spares. Spares coverage includes the remote iDirect equipment, outdoor equipment and Cisco routers. The UPS and antennas are currently not spared. Were available GCI points of contact are providing basic 1st line troubleshooting on a best effort basis.

The Commission manages the IP allocation plan for both private (RFC 1918) and public IP addresses. The majority of the traffic flows are between the IDC and remote sites. In addition, the GCI supports connectivity between any two remote sites on a case by case basis.

A single NOC in North America manages the network on a 24×7 basis and handles network incidents, new installations and configuration changes. The NOC also records incident details in the trouble ticket system.

Network monitoring is performed commercial off the shelf software employing Simple Network Management Protocol (SNMP) and NetFlow. Both the GCI Contractor and the Commission have access to the network monitoring systems. In addition, they both have access to the built-in NMS software iDirect. A custom software application developed by the GCI Contractor is providing the monitoring of the service level agreement (SLA) and calculates the SLA penalties.

Page 116 of 116 12/02/016