GCI III Bidders Conference Vienna, Austria, 30 March 2016
Arcotel Kaiserwasser Wien
BC Organizing Committee: Fernando Araujo, Mensah Solomons, Courtney Linley
PM: Fernando Araujo
Wednesday , March 30 2016
08:30
Registration and Welcome (Badge and Material Distribution)
Introduction, Overview, Timeline
09:30
09:40
09:50
Welcome and Opening Remarks : R. Bell, IDC Director, Project Executive
Introduction, presenters information and conference overview by F. Araujo, PM
The GCI III timeline by F. Araujo, PM
10:00 Coffee Break
Session I: GCI III: Procurement guidelines / the GCI III ToR: Chapters 1-2-5
10:15
11:15
11:30
12:00
The GCI III Procurement Process: Courtney Linley, Acting Chief, Procurement
The current GCI II: A Short overview , Efren Abaya GCI&NO Unit Head, IDC/OPs
The GCI III Statement of Work: Fernando Araujo, Chief Operations , IDC/OPS
Q&A Forum (legal & commercial) Led by Procurement
13:00 Lunch Break (At Hotel Restaurant)
Session II: the GCI III (chapters 3-4): Maintenance, Spares and configuration management- SPT
Engineering and Operations: NMS and Incident Management , Performance monitoring
14:00 The GCI III Site Profile Table, logistics and maintenance: Mensah Solomons, Chief Network and Systems Support, IMS/NSS
14:30 The GCI III: Engineering and design by E. Abaya GCI&NO Unit Head, IDC/OPS
15:15 The GCI III Operations: Performance Monitoring Section 4 : F. Araujo , Chief Operations, IDC/OPS
15:30 Coffee Break
15:45 Q&A Forum (technical ) Led by IDC/OPS and IMS/NSS
16:45 END
GCI III Bidders Conference
Section 1 (Introduction) and Attachment 1 (The Current GCI II)
Presented by:
Efren Abaya, Head, GCI&NO Unit Operations Section, IDC Division
GCI III
Bidders Conference
• To introduce TOR Section 1 (Introduction)
• To introduce TOR Attachment 1 (Technical Description of GCI II)
IDC/OPS Page 2
Purpose
Section 1 – Introduction
Scope and structure of the TOR
Introduction to the Preparatory Commission, Global Communications Infrastructure, International Data Centre, International Monitoring System, and connected networks
Section 2 – Statement of Work
Tasks, deliverables, documentation, activities, reports and schedules to be met
Section 3 – Specification of Requirements
Mandatory and desirable functional, architectural, technical and operational specifications
Section 4 – Service Level Agreement
Key Performance Indicators and metrics; penalty provisions for the project implementation (migration) and post-implementation (operation)
Section 5 – Benchmarking
Optional independent 3rd party benchmark of GCI pricing and service levels from the 3rd year on
Attachment I – Technical Description of GCI II
Attachment II – Site Profile Table (SPT)
Attachment III – Formats and Protocols for Continuous Data CD 1.1
Attachment IV – Formats and Protocols for Messages
IDC/OPS Page 3
GCI III TOR Outline
Preparatory Commission for the Comprehensive Nuclear-Test-Ban Treaty
Organization (PTS/CTBTO or “the Commission”)
Engaged in building up a verification regime including a worldwide
International Monitoring System (IMS) and an International Data
Centre (IDC) in Vienna for the purpose of detecting signs of nuclear
explosions
Global Communications Infrastructure (GCI)
Transports monitoring data in near-real time from IMS stations to the IDC
Transports data and IDC products to Member State National Data Centres
Facilitates remote operation and maintenance of IMS station equipment
International Data Centre (IDC) at the Vienna International Centre (VIC)
Collects, processes, analyzes IMS data and transmits data & products to
Member States (both automated analysis and human analysts)
Data Centre in Vienna is the connection point to the GCI
Possible future backup IDC at another location
IDC/OPS Page 4
TOR Section 1 - Introduction
International Monitoring System (IMS) Facilities
IMS stations & Radionuclide Laboratories (total number: 337)
Send monitoring data continuously or periodically to the IDC
Mix of: staffed or unstaffed/unmanned; normal office environment or remote & harsh environment; easy to difficult/restricted access
Operated by organizations that are independent of PTS/CTBTO (“station operator”), with or without formal contractual arrangement
Network-wise, all stations are TCP/IP devices connected to the GCI
National Data Centre (NDC)
Receives data and IDC products Traffic flow is predominantly from IDC to NDC
Independent organization, separate personnel from the PTS/CTBTO
Considered to be an untrusted node from the network security standpoint
PTS/CTBTO provides the GCI link at no cost to the NDC
CTBTO prefers Internet VPN connection, if possible
IDC/OPS Page 5
TOR Section 1 - Introduction
IDC/OPS Page 7
Distribution of IMS Facilities (CTBTO website)
Station Operator, CTBTO Contractor
Some provided with a GCI connection for remote access to an IMS facility
Requires bandwidth management
Tsunami Warning Centre (TWC)
Receives selected IDC data Traffic flow is from IDC to TWC
Internet VPN connections
Shared User
“Rides on” the GCI for remote access to the same physical location as an IMS facility; or to receive data from that location
IP protocols may be different from what is used at an IMS facility or NDC
Requires bandwidth management
IDC/OPS Page 8
Section 1 – Other facilities connected to GCI
Independent Subnetwork (ISN) and other networks
Entire network of IMS facilities and communications links operated and maintained by a Member State
Connects to the GCI at one designated communications node
May use satellite or terrestrial communication links
Higher data rates than single IMS facilities or NDCs
Considered to be an untrusted network from the network security standpoint
IDC/OPS Page 9
Section 1 – External networks
See CTBTO web site
http://www.ctbto.org/verification-regime/the-global-communications-
infrastructure/page-1-gci/
• In operation since 2007 until mid-2018 with one GCI Contractor
• 24x365 managed service provided by the GCI Contractor:
Network Operations Centre and Service Management Desk
Network Management System (NMS)
Field Service
Parts replacement (door to door)
• Mix of C-/Ku-band VSATs, terrestrial MPLS and Internet VPN services
Full network: 249 VSATs, 6 terrestrial, 45 VPN
Installed now: 217 VSATs, 6 terrestrial, 32 VPN
• Remote sites in ~100 countries on all continents
• Key Performance Indicator targets:
99.5% availability over 12 months for VSAT links
99.95% availability over 12 months for terrestrial links
IDC/OPS Page 10
TOR Attachment I – Technical Description of
GCI II
• Backup arrangements to improve link availability
VSAT + Internet VPN
Dual VSAT
Dual MPLS circuits
Dual MPLS + Internet VPN
• Every remote site has cold spares or hot standby equipment for all electronic
equipment, except the UPS
• Challenging sites: Anti-ice heaters in snow areas; Radomes; High wind
antennas; Overvoltage and surge protectors
• TCP/IP network for both user traffic and monitoring/control
• Traffic primarily directed to the International Data Centre (IDC), but remote-
to-remote connections are supported and controlled
• Different classes of traffic with end-to-end traffic prioritization
• Commission manages the private IP allocation plan
• Point of Contacts appointed by the Commission for every site
IDC/OPS Page 12
TOR Attachment I (Description of GCI II)
GCI III Bidders Conference
The GCI III TIMELINE
Presented by:
Fernando Araujo, Chief of Operations Operations Section, IDC Division
GCI III
Bidders Conference
Chapter 1 – Introduction
Introduction to the Preparatory Commission, Global Communications Infrastructure, International Data Centre, International Monitoring System, and connected networks
Chapter 2 – Statement of Work
Project and Services Schedules (2.3)
Chapter 3 – Specification of Requirements
Project Plans
Design Specifications and other documentation
Technical Requirements for transport, NMS and ticketing systems, Network Operations Center
Provisioning, Integration, Validation and Verification
Other support components for a GCI
Chapter 4 – Service Level Agreement
Key Performance Indicators & Penalty provisions
Annex I – Site Profile Table (SPT)
Annex II – Technical Description of Global Communications Infrastructure II
Page 2
GCI III TOR Outline
The planned contract duration will be 11.5 years and subsequent optional annual
extensions up to a total of 5 years. The duration of the contract is broken down in the
following stages:
– Design and Start-of-Service Migration, 1.5 years
– First 5 years of service management after Start-of-Service Migration Complete
– Next 5 years of service management including End-of-Service Migration (if no extension is exercised)
– Optional annual extensions up to 5 years including End-of-Service Migration.
IDC/OPS Page 4
GCI III Timeline (Proposal validity – Contract stages )
The Proposal shall be valid until 31 January 2017.
An extension of validity may, in exceptional
circumstances, be requested by the Commission.
IDC/OPS Page 6
GCI III Timeline (Pre-Migration to Implementation)
• 8 Months for migration with two major control points
• 5 months for PIVV (Provisioning, Integration, V&V)
• 4 months for Design
• 2 months planning and review
• 19 months
• Not just Project Management but also Change Management
• Introduction of new technology, systems and processes
• People, process, technology
• User perceptions
COVERAGE
CAPACITY
OPERABILITY
IDC/OPS Page 8
GCI II to GCI III
IDC/OPS Page 10
GCI III Timeline Post-Implementation
• 120 month operation
• 18 months Technology refresh phase
• 4 service reviews
• 12 months for end of service phase
Not only Project Management but also Change Management
• Innovative approaches on technology
• Cost Savings
IDC/OPS Page 13
GCI III : The expectations
30 March 2016 Page 1
Request for Proposal No. 2016-0022 for the Provision of the Commission’s Global Communications Infrastructure
Courtney Linley Acting Chief, Procurement Section Preparatory Commission for the Comprehensive Nuclear-Test-Ban Treaty Organization Provisional Technical Secretariat Vienna International Centre P.O. Box 1200 A-1400 Vienna AUSTRIA
30 March 2016 Page 2
RFP Overview
RFP release 17 February 2016
Bidders’ Conference 30 March 2016
Deadline for clarification requests 8 April 2016 (related to ambiguities, omissions or mistakes in the RFP documents only)
Closing Date of RFP 3 May 2016
(17:00 Vienna Time)
Evaluation of Proposals, clarifications, May–Nov, 2016 Additional information, Negotiations and site visits
Notice of award December 2016
Regret letters December 2016
Contract signature and kick-off January 2017
30 March 2016 Page 3
RFP Documents
Letter of Invitation
• RFP Acknowledgement Sheet
Instructions to Invitees
• Appendix 1, List of States Signatories
• Appendix 2, Statement of Confirmation
• Appendix 3, Vendor Profile Form
• Appendix 4, Compliance Matrix of Core Requirements
• Appendix 5, Costing Template
• Appendix 6, RFP Checklist
• Appendix 7, Pro Forma Bid Bond
• Appendix 8, Authorization of Limited Disclosure- for contacting references
30 March 2016 Page 4
RFP Documents
Contract • Annex A, General Conditions of Contract
• Annex B, Contract Price, Options and Payment Schedule [not included, place marker for the final contract]
– Appendix 1 to Annex B (SLA)
• Annex C, Terms of Reference dated 12 February 2016 (TOR), including:
– Attachment 1, Technical Description of GCI II
– Attachment 2, Site Profile Table
– Attachment 3, Formats and Protocols for Continuous Data CD 1.1 (electronic download only)
– Attachment 4, Formats and Protocols for Messages (electronic download only).
• Annex D, the Contractor’s Proposal [not included, place marker for the final contract]
• Annex E, Form of Performance Bank Guarantee
30 March 2016 Page 5
Instructions to Invitees
1. GENERAL In addition to a fully compliant baseline solution, Invitees are welcome
to propose alternatives which will result in better and more economical execution of the work, but which shall, however, meet all functional needs and comply fully with the Service Level Agreement of the Terms of Reference
• ELIGIBLE SERVICES AND EQUIPMENT – Origin shall be in one of the State Signatories of the CTBT
• PROPRIETARY INFORMATION – Documents are proprietary to the Commission
• COSTS OF PREPARATION AND SUBMISSION OF THE PROPOSAL
– Invitees shall bear all the costs
• ETHICAL STANDARDS AND CONFLICT OF INTEREST – The Commission reserves the right to reject a proposal if these standards
are not strictly followed
30 March 2016 Page 6
Instructions to Invitees
2. PREPARATION OF THE PROPOSAL
• REQUESTS FOR CLARIFICATION – Only requests for clarification in writing related to ambiguities, omissions
or mistakes in the RFP documents – Following Bidder’s Conference- one final round of clarifications accepted
by 8 April 2016. Responses by the Commission provided by 15 April 2016.
• AMENDMENT OF RFP DOCUMENTS – RFP may be modified by amendment
• LANGUAGE OF THE PROPOSAL – The Proposal and all correspondence and documents relating to it shall be
written in English
• VALIDITY OF THE PROPOSAL – The Proposal shall be valid until 31 January 2017
30 March 2016 Page 7
Instructions to Invitees
3. FORMAT AND SUBMISSION OF THE PROPOSAL (1) – The Proposal and supporting documentation shall be dated and signed by
an official, clearly legally authorized to enter into contracts on behalf of the Invitee
– The Proposal shall be submitted in two (2) sealed envelopes
– One envelope shall contain the Technical Proposal (without prices and commercial terms). The second envelope shall contain the Financial Proposal (with prices and commercial terms)
– One (1) original, seven (7) hard copies, and one (1) CD (e-form- Must be Word, Excel or PDF -Searchable)
– All sealed envelopes shall be clearly marked as explained in the Instructions to Invitees
– If the envelope is not sealed and marked as required by this RFP, the Commission will assume no responsibility for misplacement or premature opening
30 March 2016 Page 8
Instructions to Invitees
3. FORMAT AND SUBMISSION OF THE
PROPOSAL (2)
– The Proposal must be received by the Commission in the Office of the Chief, Procurement Section, by the Closing Date, Tuesday 3 May 2016 (prior to 17:00 Vienna Local Time)
– Attention is drawn to the security arrangements at the site where the Commission is located, the Vienna International Centre, and to the fact that courier or hand delivery will involve access procedures, which must be considered by Invitees before submission
– Except in the case of responding to an RFP clarification, Invitees shall not contact the Commission on any matter relating to the Proposal after its submission and until the award of the Contract
30 March 2016 Page 9
Instructions to Invitees
7. OPENING OF PROPOSAL
• All Technical proposals
• Financial proposals, subject to technical acceptability – Opening of the proposals are done internally
8. EVALUATION
• Technical evaluation
• Financial evaluation (technical acceptable bidders only)
• Potential bidder presentations/ On-site visits following the first
phase of the technical evaluation- at the discretion of the
Commission
30 March 2016 Page 10
Instructions to Invitees
9. CONTRACT AWARD
• Proposal that provides best value for money
30 March 2016 Page 11
Instructions to Invitees
4. GUIDELINES FOR INVITEES (1/4)
• Contract duration – The planned contract duration will be 11.5 years with subsequent optional annual
extensions up to a total of 5 additional years
• Licence application guidance – The Commission will make available a licence inventory and the files before EDC
for use by the successful bidder
– The licence files should serve as reference for conversion of all of these licences
– Because of the Commission’s license fee exemption in certain jurisdictions,
licence fees charged by regulatory authorities shall not be included in the
Financial Proposal
30 March 2016 Page 12
Instructions to Invitees
4. GUIDELINES FOR INVITEES (2/4)
• Reuse of existing equipment – The existing civil works shall be used. Invitees have the option to reuse any or all of
the GCI equipment at all existing sites – If any equipment is reused it shall be clearly stated in the Proposal. – The successful bidder shall take full ownership of this equipment under the Contract
and be responsible for the service of this equipment
• Off-the-shelf – All hardware, software and firmware to be provided in response to this RFP
shall, to the maximum extent practical, be commercially available, off-the-shelf (COTS) and in current production: » Have been formally introduced into the market before the Closing Date of this RFP » May be demonstrated during the evaluation of Proposals to validate that the items meet
all requirements of this RFP » Are sufficiently available to satisfy the delivery requirements of the Contract, as
described in this RFP
30 March 2016 Page 13
Instructions to Invitees
4. GUIDELINES FOR INVITEES (3/4)
• Satellite frequency band – In consultation with the Commission, the Contractor may choose any convenient
frequency band within a region.
• Terrestrial connection – The Terms of Reference implies that sites will be served by satellite
connections. The Invitees are however free to propose terrestrial connections
instead, if this should prove technically desirable and cost effective.
• VPN over Internet – VPN over Internet shall not be a primary service for the Sites unless discussed
and agreed with the Commission. For all other cases, it may be considered as
part of a back-up service, where a back-up service is proposed, or as a last
resort only for a primary service.
30 March 2016 Page 14
Instructions to Invitees
4. GUIDELINES FOR INVITEES (4/4)
• Assistance at the Sites – Considering the wide range of skills of local operators and a large number of
unmanned Sites, GCI Equipment that requires minimal involvement of local operators by maximizing redundancy, built-in-tests, and capability of remote troubleshooting is preferred
– Invitees shall assume in the Proposal and its costing that the local operators of the Sites will only be available to provide access to the Sites
– The Commission has other arrangements in place for a number of Sites and will negotiate the Site maintenance with the successful bidder, as applicable
• Site survey – Invitees are expected to make use of the information in the Commission’s site
survey reports to minimize the number of visits to the sites
– These reports will be made available after the contract kick-off
30 March 2016 Page 15
Instructions to Invitees
5. PROPOSAL
5.1 Technical Volume Statement of confirmation- To be included with the Technical Volume • Section 1 - Company overview: 5 pages • Section 2 - Executive summary: 3 pages • Section 3 - Detailed technical response: 90 pages • Section 4 - Attachments • Section 5 - Compliance matrix (Appendix 4 to the ITI) • Section 6 - Key personnel • Section 7 - Subcontractor(s) • Section 8 - References • Section 9 - Bid Bond (Appendix 7 to the ITI) • Section 10 – RFP Checklist
– The pages refer to maximum. Invitees are encouraged to be concise and keep the number of pages as low as possible
30 March 2016 Page 16
Technical Proposal Content
• Company Overview (5 pages)
− Snapshot/highlights
− Core business description (relevant experience)
− Management overview
− Achievements
− Customers
− Strategic partners
− Deployments
− Size (revenues, employees, net operating income, etc.)
− Quality certifications
30 March 2016 Page 17
Technical Proposal Content
• Executive Summary (3 pages)
− How does the technical proposal
» Address the requirements
» Meet the time constraints
− Project management methodology
− Service management approach
− Major subcontractors
− Key differentiators
− Demonstrable benefits/advantages
30 March 2016 Page 18
Technical Proposal Content
• Detailed Technical Response (90 pages) − Project Management
− Quality Assurance
− Project Schedule
− Service Migration
− Service Availability
− Service Operation and Management
− Network Operations Centre
− Security Plan
− Network Engineering
− Design Scalabilty
− Site Provisioning
− Power Consumption
− Licensing and Regulatory
− Risk Register
30 March 2016 Page 19
Technical Proposal Content
• Attachments (draft versions)
− Project Management plan
− Quality Assurance plan
− Risk Management Plan
− Project Implementation plan
− Communication Plan
− High Level Design Document
− Project Implementation Plan
− Service Migration Plan
− Training Plan
− Security Plan
30 March 2016 Page 20
Instructions to Invitees
5.2 FINANCIAL VOLUME (1) − Proposal shall be in US dollars and/or in euros and shall be submitted
strictly in accordance with the format of the Costing Template
Section 1 – Statement of Confirmation- To be submitted with Technical Volume
Section 2 - Best customer Confirmation Section 3 – Costing Template(s)- USD, EURO or both
– Firm fixed prices until 30 June 2023 – Ceiling prices for 1 July 2023 until 30 June 2028 and optional annual
extensions – Options, firm fixed until 30 June 2023, thereafter ceiling prices – Service Review (2021 and 2026)
» Contractor provides conversion proposals for 2023-2028 period and optional annual extensions » Commission reviews Contractor’s performance and conversion proposals and examines
competitive situation
– Optional annual extensions » 1 year service extensions up to 5 years » 12 months notice period prior to each extension
30 March 2016 Page 21
Instructions to Invitees
5.2 FINANCIAL VOLUME (2) • Section 4 - Payment Profile Requirements
– Milestone payment schedule during Design and Start-of-Service Migration Phase
» To be proposed by Invitee and negotiated with the Commission
− The remainder of the cost incurred during the Design and Start-of-Service Migration Phase shall be evenly spread over the first five (5) years of full service management, starting when the Start-of-Service Migration is completed.
− Quarterly payments after Start-of-Service Migration Phase » Payment for a given quarter may vary, but shall represent at least the service cost of that
quarter
30 March 2016 Page 22
Instructions to Invitees
5.2 FINANCIAL VOLUME (3)
• Financing details – Applicable interest rate
– Total mark-up for interest charges
– Other financial assumptions
• Ownership – Contractor will remain owner of equipment
– Contractor shall dispose of the equipment at the end of the Contract by arranging for return shipment of all equipment
– Commission shall have right to take over ownership at the expiry of the Contract without charge
30 March 2016 Page 23
Instructions to Invitees
5.2 FINANCIAL VOLUME (4)
• Performance Bank Guarantee – As defined in the Contract
– Template attached as Annex E
• Delivery Duty Unpaid (DDU) door-to-door – Proposal shall include the costs of the equipment/goods, packing and
handling, insurance, transportation and freight, customs clearance (if applicable) and delivery to the office of the Commission or the Sites.
30 March 2016 Page 24
Instructions to Invitees
5.2 FINANCIAL VOLUME (5)
• Taxes – Austrian companies shall list VAT separately
– EU companies shall exclude VAT due to VAT exemption status of the
Commission (EU VAT directive No. 77/388/EC)
– Non EU companies shall list VAT separately, if applicable
• If, in spite of the Commission’s exemption status, taxes,
custom duties, or licence fees are to be paid, these will be
reimbursed based on actual expenditure. – Subject to prior approval by the Commission
– Proof of expenditure to be provided
– No burdening with administrative costs
30 March 2016 Page 26
Costing Template: Key cost elements (1)
• Information – Glossary: Description of the required input
• T1 - Budget summary: Summary of the costs reported in Table 1 to 6
• T2 - Programme management: Includes of costs related to Programme Management
• T3a - Satellite site summary: Costs relating to installation, operation and maintenance of the Sites
• T3b - Site equipment: Cost all equipment to be installed and maintained at a given site
• T3c - Basic equipment package: Cost of basic sets of equipment grouped into packages that could be applied to several sites.
30 March 2016 Page 27
Costing Template: Key cost elements (2)
• T4a - Primary satellite network gateways: Cost relating to the installation, operation and maintenance of the primary satellite network gateways
• T4b - Site Back-up service (if proposed): Cost relating to the installation, operation and maintenance of a back-up service if proposed
• T5 - Terrestrial connections: Cost relating to the installation, operation and maintenance of the terrestrial connections including back-up if proposed
• T6 - Network management and control: Cost relating to the network management and control
• T7a - Options for satellite and terrestrial sites: Additional information and cost of options described in the response to the RFP
• T7b - Cost for installation of new sites, decommissioning and relocation of existing sites: For sites not foreseen in the TOR
• T7c - Summary of labour costs: Daily labour costs for various professional categories
30 March 2016 Page 28
• Tables shall not be modified or edited unless specified − Enough space has been provided to take into account specific proposals
• Cells are colour coded − Green cells are empty and shall be filled (if applicable)
− Orange cells contain formulas and shall be neither filled nor edited
− Grey cells are empty and shall be neither filled nor edited
• Non-recurring costs (NRC) and recurring costs (RC) − NRC should be reported during each migration phase, in accordance with
the installation plan, except for sites whose installation may occur after the
end of the first migration phase
− RC should be reported in accordance with the installation plan and for the
remainder of the contract
Costing Template: Filling the cells
30 March 2016 Page 29
Contract
MAIN SECTIONS 1. Definitions 2. Aim of the Contract 3. Responsibilities of the Contractor 4. Responsibilities of the Commission 5. Contract Price and Terms of Payment 6. Penalties 7. Contractor’s Claims and Remedies 8. General provisions
Annexes A. General Conditions of Contract B. Contract Price, Options, and Terms of Payment C. Terms of Reference D. Contractor’s Proposal E. Form of Performance Bank Guarantee
30 March 2016 Page 30
Contract Penalties (1/2)
If Contractor fails to deliver at the dates specified
1. Initial Project Planning Phase: US$5 000 for each day of delay
2. Project Design and Technical Review Phase: US$10 000 for each day of delay
3. Provisioning, Integration, Validation and Verification Phase: US$10 000 for each day of delay
4. Network Implementation and Migration Phase: US$10 000 for each day of delay
30 March 2016 Page 32
Contract Penalties (2/2)
If Contractor fails to meet Quality of Service
• Unit of penalty shall be based on the sum of inbound and outbound
committed information rates (CIRs) in the Site Profile Table using TOR Table 4.9 (minimum US$2 000 up to 50 kbps, thereafter adding USD500 for every 10 kbps increment of CIR).
• For unavailability of Network Management Data, the unit of penalty shall be US$1 000. If more than one system is used for Network Management, unavailability on any of the systems is subject to penalties.
30 March 2016 Page 33
Contract Changes (Clause 8.3)
• Changes to the Contract, to Annex B and to Annex C may be requested by either Party and shall be implemented by a formal amendment of the Contract in accordance with Clause 8.3
• In case the change is requested by the Commission the possible additional cost/saving shall be borne by/credited to the Commission. In case the change is requested by the Contractor the possible additional cost shall be borne by the Contractor
• All changes leading to de-scoping of Work shall lead to a corresponding Contract Price decrease for the Commission
• The pricing for changes to the Contract shall not exceed the unit pricing of the original Proposal of the Contractor (Annex D). If market prices have decreased the Commission shall receive the full benefit.
30 March 2016 Page 34
Contract Compliance
Invitees shall provide the Commission with a statement that
they have carefully reviewed the Contract and Annexes and
are in full agreement with their terms and conditions
30 March 2016 Page 35
Benchmarking
Due to the length of the Contract and the many potential
changes in the industry over the contract period, the
Commission reserves the right, as indicated in Section 5 of
Annex C (Terms of Reference) to contract an independent
3rd party (reasonably acceptable to the Contractor) to
benchmark costs and service levels for the Work under the
Contract. Should it be determined that costs and levels are
not in line with the market, the Commission shall inform
the Contractor in writing.
GCI III Bidders Conference
Section 2 the Statement of work
Presented by:
Fernando Araujo, Chief Operations Section, IDC Division
GCI III
Bidders Conference
• To introduce significant sections on TOR Section 2
IDC/OPS Page 2
Purpose
Statement of Work.................................................................................................................................. 17 2.1. Scope of Section ..................................................................................................................... 17 2.2. Documentation ........................................................................................................................ 17 2.3. Project and Services Schedules ............................................................................................. 19
2.3.1. Initial Project Planning Phase .................................................................................... 20 2.3.2. Project Design and Technical Review Phase ............................................................ 21 2.3.3. Provisioning, Integration, Validation and Verification Phase ..................................... 21 2.3.4. Network Implementation and Migration Phase .......................................................... 22 2.3.5. Service Operation and Management Phase .............................................................. 22 2.3.6. Training Courses ........................................................................................................ 24
2.4. Key Personnel 24
Section 1 – Introduction
Scope and structure of the TOR
Introduction to the Preparatory Commission, Global Communications Infrastructure, International Data Centre, International Monitoring System, and connected networks
Section 2 – Statement of Work
Tasks, deliverables, documentation, activities, reports and schedules to be met
Section 3 – Specification of Requirements
Mandatory and desirable functional, architectural, technical and operational specifications
Section 4 – Service Level Agreement
Key Performance Indicators and metrics; penalty provisions for the project implementation (migration) and post-implementation (operation)
Section 5 – Benchmarking
Optional independent 3rd party benchmark of GCI pricing and service levels from the 3rd year on
Attachment I – Technical Description of GCI II
Attachment II – Site Profile Table (SPT)
Attachment III – Formats and Protocols for Continuous Data CD 1.1
Attachment IV – Formats and Protocols for Messages
IDC/OPS Page 3
GCI III TOR Outline
IDC/OPS Page 4
TOR Section 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.1. Document Life Cycle and Delivery
Project Management
Design
PIVV
Provisioning
Implementation
Verification
Validation
Operated by organizations that are independent of PTS/CTBTO (“station operator”), with or without formal contractual arrangement
Network-wise, all stations are TCP/IP devices connected to the GCI
Operational Procedures
Periodic reporting
Monthly – Quarterly
Quality Management
Security Documentation -
IDC/OPS Page 5
TOR Section 2 - Documentation
IDC/OPS Page 7
TOR Section 2 – Project and Service 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.2
The 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; (~8 weeks)
Design and technical review phase; (~12 weeks)
Provisioning, integration, validation and verification phase; (~20 weeks)
Implementation and acceptance phase. (8 months)
IDC/OPS Page 8
TOR Section 2 – Reports –Service Operation
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
IDC/OPS Page 9
TOR Section 2 - Training
Tasks and Deliverables
Not Later
Than
[months]
Action/Venue
Satellite and Terrestrial
Technology Seminar
(specific to the
solutions employed
for the GCI)
EDC + 4
EDC + 8 Commission premises (5 days)
GCI Overview and
Stakeholders
Workshop
ICD + 6
ICD + 36
ICD + 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
International Monitoring System (IMS) Facilities
IMS stations & Radionuclide Laboratories (total number: 337)
Send monitoring data continuously or periodically to the IDC
Mix of: staffed or unstaffed/unmanned; normal office environment or remote & harsh environment; easy to difficult/restricted access
Operated by organizations that are independent of PTS/CTBTO (“station operator”), with or without formal contractual arrangement
Network-wise, all stations are TCP/IP devices connected to the GCI
National Data Centre (NDC)
Receives data and IDC products Traffic flow is predominantly from IDC to NDC
Independent organization, separate personnel from the PTS/CTBTO
Considered to be an untrusted node from the network security standpoint
PTS/CTBTO provides the GCI link at no cost to the NDC
CTBTO prefers Internet VPN connection, if possible
IDC/OPS Page 10
TOR Section 2 - Activities
Global Communications Infrastructure Overview
Global Communications
Infrastructure
International
Data Centre
International
Monitoring System
Geostationary
Satellites
VSAT: 220 links commissioned (32 links to be commissioned)
Terrestrial: 8 links (including 2xDSL)
VPN: 37 links commissioned (8 links to be commissioned)
• Site Surveys
• Civil Works
• Site Configuration and Network Planning
• Logistics Assistance and Arrangements for GCI Infrastructure
• VSAT Commissioning
GCI Site Commissioning Activities
.
• GCI VSAT/VPN Installations
• GCI Configuration Updates
• Preventive and Corrective Maintenance for GCI Link/s
• Spare Parts and Replacement for GCI Infrastructure
• GCI Infrastructure & Power Improvements
• GCI Link Redundancy & Availability Improvement
• Site Relocation Assistance
Key GCI Support Activities
Current Components of GCI at the Stations
VSAT Antenna
Antenna Mount
Rx Tx
Block
UpConverter
(BUC)
Low Noise Block
DownConverter
(LNB)
DCPM
DC Site Power
UPS
AC Site Power
24V DC
5V DC
CTBTO Devices
VSAT Antenna
Antenna Mount
Rx Tx
Block
UpConverter
(BUC)
Low Noise Block
DownConverter
(LNB)
iDirect Modem
Type-2
Installation Type-4
Installation
Internet Type-3B
Installation
BGAN System
Type-1
Installation
Type-3A
Installation
Type 1
+
Type 2
iDirect Modem
IPSec
VPN
Type-5
Installation MPLS
Cisco Router
Short-term
solution
Considerations for
various site conditions
• High Wind Antenna
• Radome
• Anti-Ice equipment
• IF Filter
• RF Filter
• Voltage Stabilizer
• UPS
On-Site Inspection (OSI)
• On-site inspections are conducted to verify States Parties’ compliance with the Comprehensive
Nuclear-Test-Ban Treaty (CTBT).
• An on-site inspection is launched to establish whether or not a nuclear explosion has been carried
out.
• If an event detected by the IMS (or by other means) raises concerns about violation of the basic
obligations of the CTBT, an OSI may be conducted to clarify whether a nuclear explosion has
taken place.
• Inspection could take place when the Treaty entry into force.
• An inspection area of up to 1000 square kilometres would be searched by a team of inspectors.
• Initial period of up to 25 days for the various non-intrusive detection techniques.
• Further, for a continuation period of up to 60 days, for more intrusive measurements.
GCI implementation for OSI
• GCI for On-site inspection must be deployed within 6 days when required.
• Sufficient bandwidth must be allocated and provisioned by the GCI Contractor for the collected
data to transport to IDC throughout the OSI exercise period.
• The scope of the exercise can vary from Small, Medium, to Large depends on the mandate
• On-site inspection may take place anywhere around the world.
• Flyaway kit with detailed standard operating procedures and instructions
• Deploy transportable and easy to maintain equipment (e.g. GATR, BGAN, etc.)
GCI III Bidders Conference
TOR Section 3: GCI III Engineering and Design
Presented by:
Efren Abaya, Head, GCI&NO Unit Operations Section, IDC Division
GCI III
Bidders Conference
• To present on overview of portions of Section 3 specifying engineering and
design of GCI III
• Background
The technical proposal is expected to present a clear understanding of the GCI III requirements and to describe in detail the proposed system design, migration plans in the first 1-1/2 years, and service management for the 10-year duration of the operations phase
IDC/OPS Page 2
Purpose
RFP Checklist
Draft level documents included in the Technical Proposal:
(1) Program Management Plan (2) Quality Assurance Plan (3) Project Implementation Plan
Terrestrial Core Network Infrastructure Teleport Infrastructure Generic Site Provisioning and Activation Site Provisioning and Activation (site-by-site)
(4) Risk Management Plan (5) Communication Plan (6) High Level Design Document (7) Training Plan (8) Security Plan (See ToR Sections 3.14.2 & 3.14.3)
IDC/OPS Page 3
Instructions to Invitees, Appendix 6
Chapter 1 – Introduction
Scope and structure of the TOR
Introduction to the Preparatory Commission, Global Communications Infrastructure, International Data Centre, International Monitoring System, and connected networks
Chapter 2 – Statement of Work
Tasks, deliverables, documentation, activities, reports and schedules to be met
Chapter 3 – Specification of Requirements
Mandatory and desirable functional, architectural, technical and operational specifications
Chapter 4 – Service Level Agreement
Key Performance Indicators and metrics; penalty provisions for the project implementation (migration) and post-implementation (operation)
Chapter 5 – Benchmarking
Optional independent 3rd party benchmark of GCI pricing and service levels from the 3rd year on
Attachment I – Technical Description of GCI II
Attachment II – Site Profile Table (SPT)
Attachment III – Formats and Protocols for Continuous Data CD 1.1
Attachment IV – Formats and Protocols for Messages
IDC/OPS Page 4
GCI III TOR Outline
GCI connections to remote sites (IMS facilities, NDCs, etc.) (Section 3.6)
VSAT
Terrestrial dedicated circuit(s)
Internet VPN connections
Transportable station (Section 3.6.9)
Complete list of 305 remote sites is in Attachment 2 (Site Profile Table or
SPT)
Instructions to Invitees (ITI) section 4(g): TOR implies that sites will be served
by satellite connections. The Invitees are however free to propose terrestrial
connections instead, if this should prove technically desirable and cost effective
Core network specifications:
Terrestrial core network infrastructure (Section 3.4)
Teleport infrastructure (Section 3.5)
GCI III will co-exist with GCI II for the migration period. Transfer of remote
sites must be automatic and transparent
IDC/OPS Page 5
TOR Chapter 3 – Specification of Requirements
ITI section 4(e): HW, SW and firmware shall, to the maximum extent practical,
be:
• Recent model/release
• Supported for at least 3 to 5 years
• Commercially available, off-the-shelf (COTS)
All these to be described in the High Level Design bid document (Section M
3.3.1.3)
IDC/OPS Page 6
TOR Chapter 3 – Specification of Requirements
Most important is that end-to-end service must be engineered and designed to
meet the SLA service availability requirements in TOR Section 4.2
• Satellite remote sites: 99.5% within a one year period
• Terrestrial remote sites: 99.95% within a one year period
Service availability must be maintained during the migration of every remote
sites, and during the service operation
• 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
IDC/OPS Page 7
TOR Chapter 3 – End-to-end service
Remote site redundancy, without single point of failure (M 3.6.3.1)
• Both VSAT remote sites and terrestrial remote sites
Backup medium (Internet VPN, VSAT, BGAN, terrestrial lines, etc.) with
automatic failover
• DC conversion equipment should be redundant (M 3.6.4.23)
Cold spares to be kept onsite in the custody of the GCI Point of Contact
Mix of AC and DC remote sites; mix of different AC and DC service voltages
For satellite remote sites, GCI III will be built on the existing civil works
infrastructure or even existing antenna mount; possible to re-use the VSAT
antenna if it is fit for purpose
IDC/OPS Page 8
TOR Chapter 3 – Remote sites (Sec. 3.6)
• The entire supporting network infrastructure used to transport data between
the various teleports and the IDC.
Shall support the transport of IPV4 and IPV6 (Sec. 3.4.1)
• Without restrictions on the kind of user traffic transported (TCP or IP protocols, IP addresses, pings, network monitoring
Redundant network elements and circuits, without single point of failure, with
automatic failover (Sec. 3.4.4)
• In addition, Internet VPN backup
• Geographic diversity of prime and backup circuits
Configured cold spares to be kept onsite
Support contracts for HW and SW
Support Quality of Service (QOS)
Fully redundant connection at the IDC, with routing protocol
IDC/OPS Page 9
TOR Chapter 3 – Terrestrial Core Network
Infrastructure (Section 3.4)
Redundant teleport elements and subsystems, without single point of failure
• Backup connectivity to the Internet
Cold spares to be kept onsite
Spare antenna onsite or at a backup teleport
Scalable and can easily accommodate future growth
Physical and logical security measures (M 3.5.4.3)
• Perimeter fence, gates and barriers • Access control • Video surveillance • Alarm systems
IDC/OPS Page 10
TOR Chapter 3 – Teleport Infrastructure
(Section 3.5)
Capacity, for both current needs and for uture growth
Exclusively non-pre-emptible and restorable satellite capacity
Easy to license in the various countries where satellite remote sites are deployed,
or re-use existing licenses if possible
IDC/OPS Page 11
TOR Chapter 3 – Space Segment (Section 3.5.5)
Network Management System (Section 3.7.2)
Monitors all network elements of the GCI from the IDC end to the remote site end
Monitors and measures compliance with the SLA (See M 4.2.1.11)
Commission staff shall have (read-only) access to the Contractor’s NMS
Trouble Ticketing System
Commission staff shall have (read-only) access to the Contractor’s ticketing system
Configuration Management System (M 3.10.2.1)
Online, interactive logistics tracking system (M 3.6.2.12)
Security requirements (Section 3.14), particularly M 3.14.16 & .17
Follow industry best practice
Mandatory: Stateful firewall, IPSec encryption, logs, DOS/DDOS mitigation
Desirable: two-factor authentication, jamming resistant coding, IDS/IPS
IDC/OPS Page 12
TOR Chapter 3 – Specification of Requirements
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.1 – The Commission shall have access to the (Contractor’s) NMS system
at all times.
M 3.7.2.5.3 - The 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.
Desirable integration scenarios:
• Commission’s JIRA trouble ticket system can read & display tickets held in
the Contractor’s system
• Commission’s JIRA system may be the user interface to update tickets in the
Contractor’s system (if Commission is given write access)
IDC/OPS Page 13
Contractor’s NMS & Trouble Ticket System
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.
• The GCI shall permit access to GCI equipment for the Commission’s
monitoring or provide traps, NetFlows, etc. as requested.
• This is independent of the Contractor’s own monitoring system, to which the
Commission will also have access
IDC/OPS Page 14
PTS/CTBTO NMS
M 3.6.4.8 – additional equipment as follows for the purpose of minimizing
outages and reducing manual intervention
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.
Read the Site Profile Table (Attachment 2)
IDC/OPS Page 15
Equipment for harsh environments
M 3.6.4.25 (DC site)
M 3.6.4.29 (VSAT and terrestrial site)
“As part of the bid the Contractor shall quantify the expected average and
maximum power consumption for the GCI equipment at a … remote site.”
• At some remote sites, the electrical power supply is very limited. The
Commission wishes to evaluate the power drawn by the proposed equipment.
• Examples of power sources
• Solar cells
• Diesel generator
• Batteries to cover days when commercial AC power is out
IDC/OPS Page 16
Power consumption
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.
• Commission wishes to retain the IP addresses used by or assigned to IMS station or NDC equipment or any other user equipment.
• GCI III IP addresses within the network cannot conflict with IP addresses used within GCI II
• Static Network Address Translation (NAT) used in a few remote sites
M 3.6.6.13
The 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.
• Names used in the NMS and trouble ticketing system, and in correspondence and reports, must match the names in the Site Profile Table
IDC/OPS Page 17
IP address and routing; Naming
Section 3.6.7 (Capacity, Performance and Quality of Service)
• GCI III shall classify and prioritize different kinds of traffic
• For example, IDC has operational and test receivers. IMS data sent to an operational receiver has priority over data to a test receiver.
• For example, IMS data going to the IDC has priority over software updates or downloads.
• Queuing and prioritization only significant when capacity is oversubscribed
• SPT specifies sufficient capacity for every remote site
• Commission may use some relatively high bandwidth applications, for
example, VOIP
IDC/OPS Page 18
Quality of Service (QOS) & capacity management
GCI III Bidders Conference
Chapter 4: SLA
Presented by:
Fernando Araujo, Chief Operations Section, IDC Division
GCI III
Bidders Conference
IDC/OPS Page 2
Distribution of IMS Facilities (CTBTO website)
Section 1 – Introduction
Scope and structure of the TOR
Introduction to the Preparatory Commission, Global Communications Infrastructure, International Data Centre, International Monitoring System, and connected networks
Section 2 – Statement of Work
Tasks, deliverables, documentation, activities, reports and schedules to be met
Section 3 – Specification of Requirements
Mandatory and desirable functional, architectural, technical and operational specifications
Section 4 – Service Level Agreement
Key Performance Indicators and metrics; penalty provisions for the project implementation (migration) and post-implementation (operation)
Section 5 – Benchmarking
Optional independent 3rd party benchmark of GCI pricing and service levels from the 3rd year on
Attachment I – Technical Description of GCI II
Attachment II – Site Profile Table (SPT)
Attachment III – Formats and Protocols for Continuous Data CD 1.1
Attachment IV – Formats and Protocols for Messages
IDC/OPS Page 5
GCI III TOR Outline
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.
IDC/OPS Page 6
TOR Chapter 4 - KPIs
• M 4.2.1 The Contractor shall comply with all of the SLA metrics
• 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.5 The 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%.
IDC/OPS Page 7
TOR Chapter 4 – Service Availability
Note also SLA requirements for:
• Replacing spares within 15 days (M 4.2.3.5.1)
• Using alternative technology as a remedial action
• Definitions of cumulative service outage, continuous service outage and
regional service outage
IDC/OPS Page 14
Other SLA requirements