at à 02 :00 PM on le August 19, 2013 / 19 aôut 2013

(1)

RETURN BIDS TO: Bid Receiving – SSC 700 Montreal Road, Ottawa, Ontario K1A 0P7

RETOURNER LES SOUMISSIONS À

:

Réception des Soumissions – SPC 700, chemin Montréal,

Ottawa, Ontario K1A 0P7

REQUEST FOR RESPONSES FOR EVALUATION AMENDMENT

MODIFICATION DE LE DEMANDE DE RÉPONSES POUR L’ÉVALUATION

The referenced document is hereby revised; unless otherwise indicated, all other terms and conditions of the RFRE remain the same.

Ce document est par la présente révisé; sauf indication contraire, les modalités de la DRPE demeurent les mêmes.

Comments - Commentaires

This document contains Security Requirements.

Ce document contient des exigences sécuritaires.

Issuing Office – Bureau de distribution

SSC | SPC

Procurement and Vendors Relationships | Achats et relations avec les fournisseurs

11 Laurier Street | 11, rue Laurier Place du Portage, Phase III, 12C1 Gatineau, Quebec

K1A OS5

Title – Sujet

Local Internet Access Service (LIAS)/ Service d’accès Internet local (SAIL)

Solicitation No. – N° de l’invitation

10030128/A

Amendment No. – N° de modif.

001

Client Reference No. – N° référence du client

13-0602

Date

July 29, 2013 / 29 juillet 2013

File No. – N° de dossier

CAB10030128

RFRE Closes – La DRPE prend fin

at – à 02 :00 PM

on – le

August 19, 2013 / 19 aôut 2013

Time Zone Fuseau horaire

Eastern Daylight Saving Time (EDT) Heure avancée de l'Est (HAE)

F.O.B. - F.A.B.

Plant-Usine: Destination:

Other-Autre: Address Inquiries to : - Adresser toutes questions à:

Melissa Ho

Buyer Id – Id de l’acheteur

CAB

Telephone No. – N° de téléphone :

819-956-1389

FAX No. – N° de FAX

Not applicable

Delivery required - Livraison exigée

See Herein

Delivered Offered – Livraison proposée Destination – of Goods, Services, and Construction:

Destination – des biens, services et construction :

See Herein

Vendor/firm Name and address

Raison sociale et adresse du fournisseur/de l’entrepreneur

Facsimile No. – N° de télécopieur Telephone No. – N° de téléphone

Name and title of person authorized to sign on behalf of Vendor/firm

(type or print)-

Nom et titre de la personne autorisée à signer au nom du fournisseur/de l’entrepreneur (taper ou écrire en caractères d’imprimerie)

Signature Date

(2)

This amendment is raised to answer Industry questions and to modify the draft RFP and draft SOW.

Question 1:

For the purposes of a complete analysis, can you provide either a breakdown by region or a detailed list of the sites to be serviced? The list does not need to be finalized but will allow suppliers to study the number of potential sites on the basis of their network and CRTC Regulations. In addition, without the exact transit addresses, clause 7.3.6, “Refusal of Service Order,” of the draft RFP is extremely restrictive and risky.

Answer 1:

A detailed list of sites cannot be provided, however a sample list at the province and city level has been provided. Please see Attachment 2.1.

Canada will remove clause 7.3.6. Please see Modification 009.

Question 2:

Can you specify whether the duration of the contracts is 24 months (Attachment 4.1) or 3 years + 1 option year (draft RFP)?

Answer 2:

The 24 months is used for evaluation purposes only. The actual contract term is 3 years + 1 option year.

Question 3:

Annex A – Section 2 – Point 5

Can you confirm that the suppliers will be able to provide some of their services, that is, for the sites they choose (“pick and choose”)?

Answer 3:

No, Bidders must be able to deliver the full set of LIAS requirements across the province or territory covered by their bid.

Question 4:

Annex A – Section 3.2 – Point 25.2

Industry standards do not guarantee that the DSCP will be intact for Internet traffic. Can you specify whether you are referring to the DSCP values contained in an IPsec encapsulated header?

Answer 4:

This requirement will be removed. Please see Modification 001.

Question 5:

Annex A – Section 3.2 – Point 25.4

Please specify what type of network discovery protocol this refers to.

Answer 5:

This requirement will be removed. Please see Modification 002.

Question 6:

Annex A – Section 4 – Point 27.3

Dial-up Internet access services are being phased out in the telecommunications market and are no longer offered by some suppliers. Can you confirm that this type of service is optional or will be removed from the bid solicitation?

Answer 6:

Dial-up is part of the optional services and is not mandatory to provide.

Question 7:

(3)

Can you specify the requirements for “denial-of-service attacks”?

Answer 7:

Denial-of-service attacks is part of the optional services and is not mandatory to provide. If a vendor offers this service and if SSC decides to add this service to the contract, it will be based on the vendor’s commercially available service description.

Question 8:

Annex A – Section 7.1.1 – Point 43

Transit Delay or Latency / Packet Data Loss: These objectives are achievable and measurable for symmetrical services but do not apply to asymmetrical services because of the technology used. Can you confirm that these service levels apply only to symmetrical services?

Answer 8:

The Transit Delay or Latency and the Packet Data Loss service level objectives apply to Symmetrical services only. Please see Modification 004.

Question 9:

Availability: Do you mean “In the event of an outage, the Contractor must restore Asymmetrical services within 24 hours and Symmetrical services within 4 hours beginning at the recorded outage start time in the trouble ticket”? Also, industry standards allow 4 hours to restore symmetrical services in large urban areas and 8 hours outside such areas. Can you confirm that these standards are acceptable?

Answer 9:

The Mean Time To Repair (MTTR) Objective for Symmetrical Services will remain at 4 hours.

Question 10:

For “IP traffic data,” can you specify what type of data is involved?

Answer 10:

This is meant to facilitate the monitoring of the actual utilization for capacity management purposes. Reports are required to capture the volume (in Megabits per second (Mbps)) of all types of transmitted (sent and received) data on the SIP.

Question 11:

Can you define “aggregate data” and specify what type of data you would like to store?

Answer 11:

This requirement is referring to the monitoring and storing the actual IP traffic utilization (sent and received) data on the LIAS SIP. For clarification:

On page 9 of the draft SOW:

Paragraph 51.1) 5-minute aggregate IP traffic data for the last 14 days;

Aggregate IP traffic data means the aggregate of all bandwidth utilization polls or readings taken every 5 minutes for the last 14 days.

Paragraph (51.2) 30-minute aggregate IP traffic data for the last 8 weeks;

Aggregate IP traffic data means the aggregate of all bandwidth utilization polls or readings taken every 30 minutes for the last 8 weeks.

Paragraph (51.3) 2-hour aggregate IP traffic data for the last 6 months.

Aggregate IP traffic data means the aggregate of all bandwidth utilization polls or readings taken every 2 hours for the last 6 months.

(4)

Question 12:

Annex A – Section 7.3 – Point 60

Can you confirm that “issues detected or reported” means a call from a site / client reporting a malfunction?

Answer 12:

This refers to all issues or troubles that degrade and/or impact the proper operation of the service whether detected by the supplier or reported by the client.

Question 13:

Annex C – Section 7.3.3

Table 1 on page 18: “Adding new or relocating a SIP to a new location where the required Contractor’s service facilities (such as Copper) do not exist but can be built and delivered”: A standard turnaround time would be 60 FGWDs in order to allow construction permits to be obtained. Would SSC be able to correct this requirement?

Answer 13:

Canada will make the requested change. Please see Modification 003.

Question 14:

Item l: For asymmetrical services, no circuit number is assigned and the contract number is the configuration reference number. Is this acceptable?

Answer 14:

Each LIAS SIP must be assigned a unique identifier. The contract number is common to all LIAS services provided by a specific Supplier and cannot be used as unique identifier for individual LIAS SIPs; however the unique Service Order number issued by SSC for a single SIP can be used as the identifier of that SIP.

Question 15:

Annex C – Section 7.10

You mention that the invoice must “include billing details for all installed LIAS Service Interface Points”: Can you specify what details need to be included on the invoice?

Answer 15:

For billing details, please see General Conditions 2035 (2013-04-25) – Higher Complexity – Services, article 12:

(5)

Modification 001:

On page 4 of 10 of the draft SOW, paragraph 25, article 25.2: Delete in its entirety.

On page 4 of 10 of the draft SOW, paragraph 25, article 25.4: Delete in its entirety.

On page 18 of 65 of the draft RFP, Table 1 – Service Delivery Interval Requirements, 4th row, second column:

Delete: Within 40 FGWDs Insert: Within 60 FGWDs

On page 7 of 10 of the draft SOW, 7.1.1 Service Level Objective Table, first column, second row: Delete: Transit Delay or Latency

Insert: Transit Delay or Latency for Symmetrical Services

On page 7 of 10 of the draft SOW, 7.1.1 Service Level Objective Table, first column, third row: Delete: Packet Data Loss

Insert: Packet Data Loss for Symmetrical Services

On page 7 of 10 of the draft SOW, 7.1.1 Service Level Objective Table, third column, second row: Delete: exced

Insert: exceed

(6)

Delete: telque défini à la Insert: as defined in

On page 7 of 65 of the draft RFP after section 2.5 Improvement of Requirement During Solicitation Period:

Insert:

2.6 Volumetric Data

The data provided in Attachment 2.1 - Volumetric Data, has been provided to bidders for background information only. The inclusion of this information in this bid solicitation does not represent a commitment by Canada that Canada’s future usage of the services or products described in this bid solicitation will be consistent with this information. It is provided purely for information purposes.

On page 20 of 65 of the draft RFP, section 7.3.6, Refusal of Service Orders: Delete in its entirety.

On page 17 of 65 of the draft RFP, section 7.3.3, Contractor’s Response to a Service Order, item b: Delete: SOR

Insert: SO

On page 19 of 65 of the draft RFP, section 7.3.3, Contractor’s Response to a Service Order, item q: Delete: SOR

Insert: SO