SAQMMA16R0222_Attachment_B_TORP_1-MPLS.pdf

U.S. Department of State Task Order 1: MPLS Solution

Mission Canada SAQMMA-16-F-XXXX

TASK ORDER REQUEST FOR PROPOSAL (TORP) FOR TASK ORDER 1

U.S. Mission Canada

Contract #: SAQMMA-16-D-XXXX

Task Order #: SAQMMA-16-F-XXXX

Contents

Section 1 Schedule

1.1 Background

1.2 Task Order contract type

1.3 Period of Performance

1.4 Place of Performance

1.5 Pricing

1.6 Statement of Work

1.6.1 Description of Services

1.6.2 MPLS and Virtual Private Network (VPN)

1.6.3 Critical Design Success Factors (Technical or Business)

1.6.4 Current Infrastructure

1.6.5 Customer Design Objectives (Technical and Business)

1.6.6 Transition Strategy

1.6.7 Testing and Deliverable Requirements

1.6.8 High Level Description of Network

1.6.9 Scalability

1.6.10 IP Address Scheme

1.6.11 CE Router to Customer Router Protocol Options

1.6.12 Conceptual Network Drawing

1.6.13 Quality Assurance Plan (QAP)

Section 2 Contract Clauses

Section 3 Solicitation Provisions

3.1 Instructions for proposal submission

3.1.1 Time, Place, and Submission of Offer

3.1.2 Proposal Validity Period

3.1.3 Proposal instructions

3.1.4 Cover Letter

3.1.5 Technical Proposal

3.1.6 Price Proposal

3.1.7 Technical Proposal content

3.1.8 Price proposal content

3.1.9 Pro Forma Commercial Documents

Section 4 Evaluation Criteria

Attachment A – TO1 Pricing Tables

Attachment B - Telecommunication Requirements by Category and Location

Attachment C – Embassy Consulate 7 Digit Dialing Plan (Site to Site Dialing)

Attachment D - Government Furnished Property

Attachment E - Government Furnished Property – Optional Future Sites

Section 1 Schedule

1.1 Background

This Task Order Request for Proposal (TORP) is made under the IDIQ contract SAQMMA-16-

D-XXXX which provides telecommunications services to Mission Canada. Any Task Order

(TO) resulting from this TORP is subject to the terms and conditions of the IDIQ contract. In the event of conflict between a task order and the contract, the contract shall control.

1.2 Task Order contract type

The task order awarded from this TORP will be a fixed price task order which includes firm fixed unit prices.

1.3 Period of Performance

Base Period: TBD at time of TO award

Option Period 1: Ending 12 months from the completion of the Base Period

Option Period 2: Ending 12 months from the completion of the Option Period 1

Option Period 3: Ending 12 months from the completion of the Option Period 2

Option Period 4: Ending 12 months from the completion of the Option Period 3

1.4 Place of Performance

The Contractor must provide private MPLS cloud services to multiple sites in Canada (Ottawa, Vancouver, Calgary, Winnipeg, Toronto, Montreal, Quebec City, and Halifax hereinafter referred to collectively as U.S. Mission Canada.

1.5 Pricing

The ceiling or Not to Exceed (NTE) price for Task Order 1, exclusive of options, is shown in

Table 1 below.

Table 1 – Task Order Ceiling Prices

Performance Period Price

Base Period: $ to be completed at time of award

Option Period 1: $

Option Period 2: $

Option Period 3: $

Option Period 4: $

TOTAL $

See Attachment A – Pricing Tables for details of Task Order 1 ceiling prices.

1.6 Statement of Work

To support the U.S. Mission Canada’s telecommunication requirements, the Contractor must provide comprehensive network connectivity integration services, including a fully redundant mesh MPLS private cloud and all associated services to support an integrated voice, data and video conferencing network. This private MPLS cloud must connect multiple sites within

Canada (See paragraph 1.4) and must be scalable to allow for additional sites to be added at a future date.

Table 1.6.a – Minimum Service and Data Rate Requirements by Site Location

Site Location Minimum Services

CDR / Kbps RT /

Kbps

Video

Kbps

Business

High Kbps

IPT-

Voice

Kbps

Minimum Data Rate

Ottawa

490 Sussex Drive

Ottawa, ON, K1N 1G8

19996

(Note: this circuit will be increased to 30Mbps)

1536 6864 8096 3500

Vancouver

1095 West Pender St.

Vancouver, BC, V6E 2M6

10000 1000 768 6232 2000

Toronto

360 University Avenue

Toronto, ON, M5G 1S4

10000 1000 768 6232 2000

Montreal

1155 Rue Saint-Alexandre

Montréal, QC, H2Z 1Z2

10000 1000 768 6232 2000

Quebec City

2 rue de la Terrasse

Dufferin

Québec, QC, G1R 4T9

10000 500 768 7232 1500

Halifax

1969 Upper Water Street, Halifax, NS, B3J 3R7

10000 500 768 7232 1500

Calgary

615 Macleod Trail, SE

Calgary, AB, T2G 4T8

10000 704 768 6128 2400

Winnipeg

201 Portage Avenue

Winnipeg, MB, R3B 3K6

10000 500 768 7732 1000

All sites must use dedicated fiber from the carrier, when available. The U.S. Government may elect to use other than a fiber medium for a specific site if fiber is not available or in lieu of paying to have fiber installed. Port speeds will be associated with the access type, depending on

E1000 or E100. See Table 1.6.b.

Table 1.6.b Access Types and Bandwidth Requirements

Access Type Description Maximum Bandwidth

E1000 Full (Fiber) Ethernet 1000 Full Duplex over Fiber facilities 1000 Mbps

E100 Full (Fiber) Ethernet 100 Full Duplex over Fiber Facilities 100 Mbps

Attachment B – Telecommunications Requirement by Category and Location, identifies the requirements for each location. Sites designated as “core” locations will be activated upon award of a Task Order. Sites designates as “optional” locations may be activated upon award of a

Task Order or during the period of performance of the Task Order.

1.6.1 Description of Services

The Contractor must ensure that all services are configured in accordance with industry standards and must be uninterrupted, clear and with no static. Network problems must be remedied immediately, and the COR must be immediately informed of any problems and their resolution.

The Contractor must provide the following services and equipment:

Data services (Internet)

Local and long distance telephone service

Free, unlimited local and long distance telephone calls within Canada and U.S. (using both ISDN and VoIP trunking)

SIP Trunking

Video conferencing over IP

International calls

Multi-Protocol Label Switching cloud-based converged network (voice, data, video)

IP-to-IP long distance calling between U.S. Embassy and consulate locations

Static Public IP Addresses on CE Routers

24 hour customer service

1.6.2 MPLS and Virtual Private Network (VPN)

The Contractor must provide a converged cloud-based mesh voice/data/video network for U.S.

Embassy Ottawa and other locations throughout Canada as identified in Attachment B. Services must include telecommunication infrastructure installation, maintenance, and support. The virtual private network or cloud must include official fixed lines, fixed residential lines, data lines, and digital trunks.

1.6.3 Critical Design Success Factors (Technical or Business)

U.S. Mission Canada will consider this project a success when the MPLS network meets the

Customer Design Objectives and maintains or improves current network latency and QoS.

1.6.4 Current Infrastructure

1.6.4.1 High Level Description of Current Infrastructure

U.S. Mission Canada's current network architecture relies on established VPN connectivity using

IPsec technology.

US Mission Canada sites currently use the Internet (World Wide Web) to connect back to the main Ottawa location and/or onward to Washington, DC. Establishing the current connection is done on a VPN platform. A diagram of the current network configuration is available upon request.

1.6.5 Customer Design Objectives (Technical and Business)

The Contractor’s design must:

Maintain the end-to-end IP network supporting current and future applications to industry standard Quality of Service / Class of Service (QoS/CoS). This Class of Service can be explained by Table 1.6.5 below from highest priority to lowest priority:

Table 1.6.5 – Class of Service

Service Priority

Real Time 1 (real time)

Video Class 2 (real time)

Business High 3

Business Low 4

Basic Enhanced 5

Default 6 (best effort)

Ensure access to the Internet is implemented with a dedicated high-speed secure connection, limited to the device requesting access via Media Access Control (MAC) address without firewall interference. Data transport must be fiber optic, terrestrial connectivity when available. Twenty-four (24) hours uplink. Internet Service Provider

(ISP) connection must be “always on” with unlimited usage, and must not require the installation of any custom software on the client side. Bandwidth sharing between other non-Embassy customers is not allowed. ISP must not use Network Address Translation on dedicated leased data lines. ISP must permit installation of customer VPN encryption devices on the circuit.

Achieve cost savings by migrating to VOIP where possible, and maintaining IP trunking between all MPLS sites.

Provide measured latency equal to or better than the current network design for each site.

Maintain the current integrated Dial Plan (i.e. 7-digit dialing for IP calls) within US

Mission Canada. See Attachment C – Embassy Consulate 7 Digit Dialing Plan.

Reduce the number of PRI, ISDN, and dedicated Internet circuits at U.S. Mission Canada serviced locations in order to lower operating costs and migrate to a totally converged network.

o For Optional Locations, the Contractor must provide gateway equipment that is compatible with current Mitel or CISCO gateways in order to facilitate integration with existing telephone switch to implement VOIP, i.e. IP Trunking.

Ensure minimal disruption to the current network operations during the implementation phase.

Meet or exceed the US Mission Canada current architecture and design. The design must ensure that the quality of the existing infrastructure is not diminished.

Implement any new installation in parallel with current MPLS network until testing is successfully completed and final cutover is completed.

Include a burst mode capability as part of the network telecommunication package. Burst mode can be described as a situation when there is a service that requires more bandwidth at a certain moment and other services are not using their allocated bandwidth, thus allowing the service requiring the extra bandwidth to employ the “free” bandwidth as long as it is available. However, if the other services with allocated bandwidth are fully utilizing their bandwidth, then every service will be using its maximum allocated bandwidth and none will be available for “burst mode.” Normally the bandwidth dedicated to say a Digital Video Conference is used for that purpose, yet if they are not utilizing the bandwidth, that bandwidth can be automatically allocated to other services such as VPN or voice.

o Using the aggregate of the line, here is an example of burst mode if four ports are configured as below:

Port Bandwidth

P1 2mb

P2 1.5mb

P3 1.5mb

P4 2mb o The aggregate is the total of all the ports. In this example, the aggregate is 7mb.

If P1 is reserved for video conferencing and is not currently being used, and P4 is running out of bandwidth, the total bandwidth of P1 can be used by P4 to augment the temporary load on P4. Once P1 needs the allotment back, the P4 releases the

2mb back to P1 automatically.

1.6.6 Transition Strategy

The Contractor must complete the entire transition within 90 days after award of the Task Order.

1.6.6.1 Phase 1: Installation and Testing

The Contractor must install a new Customer Edge (CE) router at each location configured as per the specification details for Address Scheme (Paragraph 1.6.10), the Contracted Speed

(Paragraph 1.6), Quality of Service (Paragraph 1.6.13.1) and Class of Service (Paragraph 1.6.5)

The Government will, along with the Contractor technicians, conduct testing to ensure delivery of contracted speed and Quality of Service/Latency.

The Government will ensure the configuration of all IP addresses according to the IP Address

Scheme and accessibility to the Internet from the Static Public IP from the MPLS network.

Testing the Static Public IP may be done using a temporary Static Public IP address and on the cut-over day, move the current live IP block to the new MPLS CE router Data port (Port 1 of the

3 Ports) if the Contractor will be able to move the current IP addresses. The Contractor must coordinate with the incumbent contractor to allow the move of the current STATIC Public Static

IP addresses. If this is not possible, the Contractor must submit evidence that they tried to coordinate the move of the Static Public IP with the incumbent contractor but were unsuccessful and state the reason. Only at this point, the Embassy will accept new static IP address block and start the coordination to switch to use these new Static IP addresses with the State Department

Enterprise Network Management on the cut-over date.

Testing must include successful telephone connectivity of the Mitel Gateway for each of the 7 main locations with Mitel/Nortel configuration (excluding Winnipeg and the Ambassador

Residence). This test must be performed after normal working hours or during a weekend at each location. Normal working hours is Mon to Fri 8:00 am to 4:30 pm excluding holidays. The

Contractor’s work schedule must project for afterhours testing. After successful testing for both

IP trunking within the MPLS network between all 8 core locations and to any outside telephone line using IP, the service will be moved back to the old existing service until all posts are ready for Phase 2 of the implementation.

1.6.6.2 Phase 2: Cutover

When all posts have completed testing of all services, the Government will coordinate with the

Contractor and set a date/time during a weekend where all posts’ IT personnel will be available to switch all services from the old CE router to the new CE router.

The migration/cut-over must be done at the same time at all locations to maintain IP Trunking and in-country tunnels on the VPN side as well as porting all DID numbers into the providers

VOIP network.

The Contractor must have a technician on each site available to assist with the migration from the old service to the new service.

The Contractor must assign a Technical Engineer who must be available at the provider Network

Control Center to help with the migration.

If Public IP address changes are required, the Government will coordinate with the State

Department Enterprise Network Management to be available at that date/time to adjust any configuration changes.

1.6.6.3 Phase 3: Future Enhancements and Additions

The Government may request future enhancements and additions. Such future enhancements and additions may include the following:

If VOIP is now available in Manitoba, and based on the Contractor’s selected protocol, the Contractor and Post will start the process to switch Winnipeg to VOIP and cut the analog business phone lines currently serving Winnipeg IP Phone Switch.

Add Ambassador Residence in Ottawa to the MPLS network as a new node and switch all analog or T1 lines to use IP to connect the existing Mitel IP Phone Switch (SIP required).

Add DCM Residence in Ottawa to the MPLS network as a new node.

Add Ottawa Warehouse to the MPLS network as a new node.

Add USAITC in Ottawa to the MPLS network as a new node.

Add Toronto Law Enforcement Hub to the MPLS network as a new node.

Add ICAO Office in Montreal to the MPLS network as a new node

Add DCMA Annex in Ottawa to the MPLS network as a new node

1.6.7 Testing and Deliverable Requirements

1.6.7.1 Contractor must:

Conduct a site survey for all locations identified in the Statement of Work in order to ensure the Contractor’s ability to complete the installation within the defined timeframe.

Provide technical specifications for U.S. Mission Canada facilities (Space, Power, Grounding, Back Boards, Rack space, Environmental, cabling).

1.6.7.2 US Mission Canada Sites will:

Provide appropriate space, power, grounding, back boards, racks, environment and cabling for all telecommunication facilities

Provide appropriate site access.

Provide applicable Networking and IP addressing information

Provide appropriate personnel for duration of project.

1.6.7.3 Joint Requirements

The Contractor and US Mission Canada will have designated Project

Manager’s/Coordinators for the duration of the project.

Equipment will be delivered in advance of scheduled staging/implementation dates.

All deliverables indicated in this document shall be completed and ready in time for the completion of the project within the one year constraint.

U.S. Embassy will accept responsibility for equipment once shipped to site.

U.S. Embassy will provide access to data/telephony facilities as required.

U.S. Embassy will provide appropriate on-site contacts.

All work efforts will be coordinated with Embassy staff. Except for testing and actual cutover, work must be completed during regular working hours. Testing and actual cutover must be performed after normal business hours (including weekends and holidays).

1.6.8 High Level Description of Network

The solution for US Mission Canada must implement a fully integrated MPLS (Layer 3) private network while optimizing security and minimizing costs over traditional telecommunication services. The solution for the MPLS component must utilize a Layer 3 VPN service which allows for remote site connectivity of customer IP networks. US Mission Canada intends to use the same set of private IP addresses currently in use. The private IP addresses will be provided to the Contractor at the time of project implementation. The traffic for each customer (US

Mission Canada service location) must be separated from each other over the same physical backbone. Traffic separation means that each customer cannot access another customer’s network.

The Contractor must deliver an MPLS solution for 8 locations nationally, interconnecting US

Mission Canada and regional offices and local sites in each region using the carrier’s National

Fiber Network. The network topology must be fully meshed. Special configuration considerations must be given to US Mission Canada's locations.

MPLS service requires peering at Layer 3 (IP routing layer) between the PE and CE Routers. A reference diagram for a customer with 2 single-homed customer sites is given in Figure 1. Each customer site contains one or more IP subnets that are distinct from IP subnets at other sites belonging to the same customer. In the diagram, Customer Site A contains IP Subnet A which is different from IP Subnet B located at Customer Site B.

Figure 1: 2 single-homed customer sites

Level 3 VPN (L3VPN) service offerings cover homing scenarios between the customer network and the Contractor L3VPN infrastructure.

Service Provider

MPLS Backbone

PE RouterPE RouterCustomer

Router

Managed CE

Router

Managed

CE

Router

Customer

Router

Customer IP subnet A

Customer IP subnet B

1.6.8.1 US Mission Canada’s Demarcation

As an example for US Mission Canada, the U.S. Embassy Demarcation Point is shown in Figure

2. The physical circuit connecting the CE Router to the PE Router must have one or more physical segments where each segment can be managed by both the U.S. Embassy’s network personnel (LAN side) and the carrier's Managed Service group on the WAN side.

US Mission Canada's Demarcation Point is a physical Ethernet interface on the CE Router. The media type for the physical interface must be multi-mode fiber or if multi-mode fiber is not available, twisted pair copper. The jack for twisted pair copper must be RJ45. The connector type for multi-mode fiber must be LC or SC depending on the make and model of the router. For

100 megabits per second (mbps) service, the media type must be copper. For 1 gigabit per second (Gbps), the recommended media type is fiber with the alternative being copper. For all media types, the recommended setup will be full duplex with auto negotiation turned on. Auto negotiation must be turned off if the protocol is not negotiating properly.

The data link layer framing used at the Demarcation Point must be Ethernet as defined by IEEE

802.3 standards document. Each of the US Mission Canada sites requires three (3) physical interfaces on the LAN-facing side of the carrier's CE Router installed, but sharing the WAN. US

Mission Canada will provide three (3) separate subnets for each site.

1.6.9 Scalability

The MPLS solution must accommodate growth for additional locations as well as bandwidth.

An important note, as the increase for additional sites and/or bandwidth increases across US

Mission Canada, an increase in bandwidth at the core location (Ottawa) must be considered to accommodate the growth.

1.6.10 IP Address Scheme

IPv4 with the ability to move to IPv6 in the future must be used for addressing in the MPLS solution. The U.S. Embassy will provide the IP addresses and accompanying subnet masks for each Demarcation Point.

CE Router CE Router

Figure 2: U.S. Embassy Site

Embassy’s IP Network

With 3 separate physical Interfaces

Carrier Managed Embassy Managed

PE Router PE Router

Customer

Demark Point Customer

Demark Point

The carrier must use a /30 network between the carrier's deployed router (CE or Customer Edge device) at US Mission Canada locations and the carrier's network edge device (PE or Provider

Edge device).

A mesh routing must be built to ensure a maximum of 4 routers (CE/PE – PE/CE) between any 2 given locations on the MPLS network.

The Contractor must supply the U. S. Embassy with a router on the MPLS cloud with 3 interfaces in all Consulates and 4 Interfaces in Ottawa as per the following IP address schema and specs:

One interface with Internet Connectivity with Public Static IP address block with 5 usable Public IP addresses which will be through the MPLS Cloud to the exit point to the

Internet. The Contractor should advise if they can maintain the current static public IP address, but this is not a requirement, however a Static Public IP address available on the

MPLS interface is a mandatory. Detailed Static Public IP addresses will be shared with the Contractor upon request. The connection between the MPLS Cloud and the

Internet must be a minimum of 30 Mbps.

One interface with no Internet access for the telephone systems. Routing between this segment and VOIP service must be established. Details for Private IP addresses will be shared with Contractor upon request.

One interface with No Internet access in all Consulates for the Digital Video

Conferencing (DVC) equipment. This must use a private 10.30.x.x/24 IP scope (different from the IP scope for the phones and no routing between them). Details for Private IP addresses will be shared with the Contractor upon request.

In Ottawa ONLY, the 4th Port on the CE router must be configured with Internet access using a Static Public IP for the DVC Bridge Internet Connection. Currently configured

Static Public IP addresses will be shared with the Contractor upon request. This Internet connectivity must also share the same Internet pipe for the VPN data portion of the

MPLS cloud (Section 4.8.1 in this block). Maximum bandwidth this port can use on the Internet connection is 1.536 Mbps.

1.6.11 CE Router to Customer Router Protocol Options

The Contractor must support various routing protocols such as BGP, RIP, OSPF, BGP, IGRP, EIGRP, IBGP, IS-IS, and static configurations. The U.S. Embassy and the Contractor will determine the routing protocol at the implementation phase of the MPLS solution. If a US

Mission Canada site does not run a router behind the Contractor’s CE router, then routing protocols will not be required.

1.6.12 Conceptual Network Drawing

The Contractor must prepare a Conceptual Network Design, depicting the design from logical and physical perspectives. IP addressing used for WAN connections and LAN connections will be provided by the U.S. Embassy. These IP addresses and private SAN are required before implementation.

1.6.13 Quality Assurance Plan (QAP)

The QAP plan is a set of processes to measure and assure the quality of contractor performance.

The QAP provides the method for the Contracting Officer’s Representative (COR) and

Government Technical Monitor (GTM) to monitor and evaluate contractor performance, advise the contractor of unsatisfactory performance, and notify the Contracting Officer of unsatisfactory performance. The Contractor, not the Government, is responsible for performance management and quality control to meet the terms of service.

1.6.13.1 Quality of Service (QoS)

A number of network design and operations factors affect Quality of Service (QoS). The contractor must meet or exceed industry standard metrics for packet loss, bandwidth availability, and latency.

1.6.13.2 Network Management

The Contractor shall provide U.S. Mission Canada with monthly network utilization reports.

The Contractor must provide U.S. Mission Canada with a listing of available monthly performance and utilization reports. In addition, the Contractor must provide active network monitoring and notify U.S. Mission Canada whenever a problem is detected anywhere in the

MPLS network. Utilization reports provided to U.S. Mission Canada must include bandwidth utilization by Class of Service as well as availability reports (uptime/downtime).

1.6.13.3 Performance

SURVEILLANCE. The COR will receive and document all complaints from government personnel regarding the services provided. If appropriate, the COR will send the complaints to the Contractor for corrective action.

STANDARD. The performance standard is that the Government receives no more than one (1) customer complaint per month. The COR will notify the Contracting Officer of the complaints so that the Contracting Officer may take appropriate action if any of the services fail to meet the standard.

1.6.13.4 Procedures

The quality assurance procedures are meant to provide the Contractor immediate, actionable feedback to focus Contractor attention to defect prevention and to ensure successful performance of the Task Order requirements. If any Government personnel observe unacceptable services, either incomplete work or required services not being performed they will contact the COR. The

COR will complete appropriate documentation to record the complaint. If the COR determines the complaint is invalid, the COR will advise the complainant. The COR will retain the annotated copy of the complaint for his/her files. If the COR determines the complaint is valid, the COR will, as a minimum, orally inform the Contractor and give the Contractor time to correct the defect, if additional time is available. The COR will determine how much time to remedy a complaint is reasonable. The COR will consider complaints as resolved unless notified otherwise by the complainant.

If the Contractor disagrees with the complaint after investigation and challenges the validity of the complaint, the Contractor must notify the COR. The COR will review the matter to determine the validity of the complaint.

Repeat customer complaints are not permitted for any services. If a repeat customer complaint is received for the same deficiency during the service period, the COR may contact the Contracting

Officer for appropriate action.

1.6.13.5 Circuit Downtime and Credits

Credits may be assessed against the Contractor in those instances where a circuit, during any given month or year, fails to achieve and sustain the minimum acceptance standard.

1.6.13.5.1 Definitions:

CIRCUIT AVAILABILITY ACCEPTANCE LEVEL: Yearly Circuit Availability Acceptance

Level is computed by multiplying 365 calendar days times 24 (hours per day) times 99.5% minimum acceptance standard equals 8,716.20 hours annum. (365 x 24 = 8760 x 99.5% =

8,716.20). Monthly Circuit Availability is computed by the calendar days per month times 24

(hours per day) times 99.5% acceptance level (example: 31 x 24 = 744 x 99.5% = 740.28)

DOWNTIME: That period of time when the circuit becomes non-operational or unusable for communication or transfer of data or failures to meet the minimum acceptance standard. The maximum cumulative annual downtime that shall be acceptable for corrective or preventative maintenance is 43.80 hours (8760 x .5%). The maximum cumulative monthly downtime that shall be acceptable for corrective or preventative maintenance shall be .5% of the total available hours for the month (example: 31 x 24 = 744 x .5% = 3.72).

PERIOD OF DOWNTIME: Downtime shall commence at the time first attempt for contact is made by the Government (or its representative) to the Contractor’s Point of Contact and shall be annotated on the Remedy Ticket and shall continue until the circuit is returned into service by the

Government.

DOWNTIME CREDITS: Monetary value returned to the Government for failure to meet the circuit availability requirements. Downtime Credits shall be assessed based on cumulative downtime time with the minimum assessment being one hour. There are two (2) situations when circuit Downtime Credits can be accumulated:

Below Availability Level, Extended Downtime.

1.6.13.5.2 Credit for Circuit Downtime by Situation

BELOW AVAILABILITY LEVEL: If the downtime accumulated for a circuit adds up to 43.80

(8760 x .5%) cumulative hours or more during any one contract year (365 calendar days) or depending on the number of hours for the month (example 744 x .5%) cumulative hours per month (example: 31 calendar day month), the Contractor shall grant a hourly credit to the U.S.

Government for each hour of downtime. Each additional one hour increment or portion thereof will be assessed as an additional hour.

EXTENDED DOWNTIME CREDIT(S): Cumulative downtime of more than 18 hours but not greater than 24 hours for any one outage shall be assessed at a daily rate. Any increment of 24 hours beyond the initial 24 hours of any one outage shall be assessed at the standards for the hourly rate up to 12 hours; however between 12 and 24 hours, the credit shall be assessed at the daily rate.

1.6.13.5.3 Exceptions to Accumulation of Downtime

Accumulation of circuit downtime shall include all unscheduled downtime deemed to be the responsibility of the Contractor, with the following exceptions:

When the failure to perform arises out of causes beyond the control and without the fault or negligence of the Contractor or Subcontractor.

Malfunction of equipment, frequency fading and interference, errors of commission and/or omission by the Contractor or Sub-contractor, and commercial power surges or failures are considered to be normal hazards of the industry and therefore do not qualify as causes beyond the control of the Contractor or Sub-contractor. The Contractor shall be charged with credits for all reported outages determined “no trouble found” or “came clear while testing” but which exceed 45 minutes.

The Contracting Officer will make final determination as to whether downtime is the responsibility of the Contractor. If requested by the Contracting Officer, the Contractor must provide documentation to support claims of excusable downtime. For downtime determined to be the Contractor’s responsibility, the Contracting Officer may elect to assess a credit for each instance of non-performance.

1.6.13.5.4 Payment Reduction for Downtime Credits

When Circuit Downtime Credit(s) is due the U.S. Government, the total number of creditable hours shall be accumulated for the month and will be deducted from the payment due the

Contractor in the month they accrued.

1.6.13.6 Trouble Escalation Procedure

U.S. Mission Canada will refer problems to the Contractor. Obtain the name of the Contractor test person and a Contractor ticket number, and record this information on the U.S. Mission

Canada’s Remedy Ticket.

After the trouble call has been referred to the Contractor for two (2) hours, U.S. Mission Canada will call the Contractor again for an update on the current trouble. Record the Contractor’s response, the name of the Contractor’s representative, and the Contractor ticket number on the

Remedy Ticket.

After the trouble ticket has been referred to the Contractor for four (4) hours, U.S. Mission

Canada will call the Contractor again for an update on the current status. If the Contractor’s response is not satisfactory, U.S. Mission Canada will escalate the trouble ticket to the

Contractor’s management. Record the Contractor’s response, the name of the Contractor’s representative, and the Contractor ticket number on the Remedy Ticket.

After the trouble ticket has been referred to the Contractor for six (6) hours, U.S. Mission

Canada will escalate the trouble ticket to the Contractor’s senior management. Record the

Contractor’s response, the name of the Contractor’s representative, and the Contractor ticket number on the Remedy Ticket. Also, advise the COR and Contracting Officer that the

Contractor is not meeting the performance standards set forth in the contract.

U.S. Mission Canada will continue to request status updates from the Contractor for the remainder of the outage or until a solid loop from the Contractor’s distant end location is received.

1.6.13.7 Training

The Contractor shall provide, at no additional cost, training to all U.S. Mission Canada employees who will administer and provide technical support for the proposed network.

Training shall include the proper operation of equipment and feature operations. The training must be coordinated with the COR to match the U.S. Mission Canada work schedule.

1.6.13.8 Survivability and Recovery

The Contractor shall provide a mesh network design that clearly identifies alternate voice and data routes if any segment of the MPLS network is down. The Contractor shall have a recovery plan in place that deals with disaster recovery and alternate routes during any outages effecting the proposed network.

Section 2 Contract Clauses

This Task Order is awarded under the terms and condition of the IDIQ contract SAQMMA-16-

D-00XX. This task order incorporates all terms and conditions in the IDIQ contract unless otherwise noted in the task order.

Section 3 Solicitation Provisions

3.1 Instructions for proposal submission

The Contractor must submit all information requested in the TORP. The Government reserves the right to eliminate from the competition any proposal that fails to include all information requested in the TORP.

The Government will not pay for any proposal costs incurred by the Contractor or any costs attributed to the proposal.

3.1.1 Time, Place, and Submission of Offer

The Offeror shall assume the full and total responsibility of ensuring that the proposal is received by 5:00PM (Eastern, UTC-5) on April 18, 2016. Proposals must be submitted electronically to:

U.S. Department of State

Todd Paynter, PaynterMT@state.gov

David Ziemba, ZiembaDE@state.gov

One of the individuals listed above will send out confirmations of receipt.

3.1.2 Proposal Validity Period

All proposals shall be valid for a minimum of 180 calendar days from the closing date for this

RFP.

mailto:LloydAJ@state.gov mailto:ZiembaDE@state.gov

3.1.3 Proposal instructions

The following table summarizes instructions for preparing the technical proposal and the cost proposal.

Volume Volume Title Page Limitation Content

1 TO 1 Technical Proposal 35 See 3.1.5 and 3.1.7 2 TO 1 Price Proposal No limitation See 3.1.6 and 3.1.8

Use the following guidance when preparing proposals:

Margins – 1-inch margins on all sides.

Orientation – Portrait. Diagrams, tables, graphs and worksheets may use landscape orientation if appropriate.

Page Size – Letter (8.5 X 11). Diagrams, tables, graphs and worksheets – may use page size appropriate to view proposal information (i.e. readable at 100% Zoom of the software application.

Columns – One

Font and Font Size – Times New Roman, 12 point font size. Diagrams, tables, graphs and worksheets – may use Arial font, no smaller than 10 point font size.

Headers and Footers – Footers must include the company name (left justified) and the page number (right justified) on each page.

3.1.4 Cover Letter

The cover letter shall contain no pricing information.

A signed and dated cover letter must be included with each volume of the proposal. The cover letter will not count against the technical proposal page limitation. The cover letter shall include the following:

Title of Acquisition (i.e. Task Order 1 MPLS Solution)

TORP number (i.e. SAQMMA-16-F-XXXX)

Issuance Date of TORP

DOS issuing office, location, and contact person

Closing date and time of TORP (for submission of proposals)

Dun & Bradstreet (DUNS) Number, name, address (street, city, state, zip) of offeror

Proposal Category (Technical or Price)

The signature of the official authorized to bind the company to a contract.

An executive summary of the Offeror’s proposal. Technical information provided in the cover letter will simply be provided as an overview and will not be used during the evaluation.

A definitive statement from the offeror as whether or not any exceptions were taken to any of the terms and conditions contained in the solicitation or assumptions were made concerning the technical or pricing portions of this solicitation. All exceptions and assumptions will be briefly listed with location information of where they are found in the proposal. Failure to identify assumptions and exceptions fully and up front in the cover letter, especially as they affect technical approach, management, and/or pricing, will make the proposal determined unacceptable. The penalty for making false statements is prescribed in 18 USC 1001. Failure to furnish current and complete information requested may cause a proposal to be determined unacceptable.

3.1.5 Technical Proposal

Technical Proposal for the IDIQ Contract shall not exceed 35 pages. The Technical proposal shall include the following sections.

1) Cover Letter

2) Technical Proficiency / Approach,

3) Copy of Offeror’s standard commercial contract.

4) Copy of Offeror’s standard commercial service level agreements for the products and services offered. The standard commercial service level agreements may be an annex to the technical proposal and will not count against the page limit.

3.1.6 Price Proposal

The Price Proposal has no page limit. The Price Proposal shall include the following sections.

1) Cover Letter

2) SF 1449 document (completed and signed)

3) Acknowledgement of all amendments

4) Pricing Tables (Attachment A to the TORP 1)

5) Copy of Offeror’s standard commercial contract terms and conditions for the products and services being offered.

6) Copy of Contractor’s standard commercial service level agreements for the products and services offered.

7) Copy of Offeror’s standard commercial price list for the products and services being offered

3.1.7 Technical Proposal content

Proposals must include a compliance checklist directly following the cover letter. The compliance checklist must document the proposal’s compliance with TORP requirements. The compliance checklist must identify, where, in the proposal, each TORP requirement is satisfied.

The compliance checklist is intended to assist the offeror in ensuring a compliant technical proposal. The compliance checklist will assist the Government evaluators in reviewing the proposal. The compliance checklist will not count against the technical proposal page limitation.

Simply repeating or paraphrasing the requirements from the solicitation document or stating the

Offeror can and/or will meet the requirements without a detailed description of how the work will be done is not acceptable and may cause the Government to reject the proposal as unacceptable.

3.1.7.1 Technical Proficiency / Approach

The technical proposal must describe, in detail, how the technical solution meets or exceeds the

TORP requirements.

The proposal must identify all proposed subcontractors and describe the work each subcontractor will perform. The proposal must identify the portion of the work each subcontractor will perform, expressed as a percent of the total proposed amount.

The proposal must provide a detailed description of the products and services to be provided.

The proposal must describe how the offeror’s will perform the service requirements by providing detailed responses to the questions listed below:

How will offeror provide MPLS private cloud, as well as separate data services outside the MPLS cloud to all the following locations?

Site Postal Code

US Embassy Ottawa K1N 1G8

Embassy Warehouse K1G 3V4

DCMA Annex, Ottawa K2P 2L6

US Consulate Toronto M5G 1S4

US Consulate Montréal (current site) H2Z 1Z2

US Consulate General Montreal (new office) H3B 1H4

US Consulate Vancouver V6E 2M6

US Consulate Calgary T2G 4T8

US Consulate Québec G1R 4T9

US Consulate Halifax B3J 3R7

APP Winnipeg R3B 3K6

ICAO Montréal H3C 5H7

Site Postal Code

LEH Toronto M5G 1V2

CMR/DCMR Ottawa K1M 0G1

Will the offeror provide dedicated secured fiber optic connections to each of the locations across U.S. Mission Canada? Wherever possible the offeror shall utilize fiber connections. If fiber connections are not available it shall be outlined in the technical proposal and alternative solution shall be described.

How will the offeror provide Internet access as dedicated high-speed secure connection, using Media Access Control (MAC) address controls without firewall interference?

How will the offeror complete new installation in parallel with the existing infrastructure?

How will the offeror provide automatic dynamic bandwidth allocation where unused bandwidth is made available to high use services (“burst mode” operation)?

How will the offeror provide 24/7 technical support with a 24-hour service ticket escalation and return?

How will the offeror complete all installations within six months and in accordance with the Migration Strategy?

How will the offeror provide accessibility to the Internet from the Static Public IP from the MPLS network?

How will the offeror meet appropriate network media type physical interface?

How will the offeror provide IP address schema to permit upgrade from IPv4 to IPv6?

How will the offeror support various routing protocols such as BGP, RIP, OSPF, BGP, IGRP, EIGRP, IBGP, IS-IS, and static configurations?

Will the offeror provide monthly network utilization reports?

How will the offeror provide network monitoring and notifying the Mission immediately upon detecting a problem with the network?

What tools will be used to monitor and analyze the QOS factors on the proposed MPLS network?

How will the offeror make a technical representative available in Ottawa with sufficient access to all levels of communications infrastructure?

For data services outside of the MPLS network, how will the offeror provide twenty-four

(24) hour per day uplink with Internet Service Provider (ISP) connection “always on” mode with unlimited usage, non-shared with no NAT and permits VPN encryption?

Does the proposed MPLS network configuration diagram demonstrate an understanding of the existing infrastructure? Does the MPLS network configuration diagram offer improvement to the current infrastructure?

How will the offeror provide Voice Over IP connectivity to PSTN? (SIP is required)

3.1.8 Price proposal content

The Price Proposal shall include the following documents

3.1.8.1 Cover Letter

See Section 3.1.4 for detailed description of Cover Letter content.

3.1.8.2 Pricing Tables

See Attachment A to the TORP 1 for Pricing Tables.

The Offeror shall complete Pricing Table 1: Prices by inserting Not-to-Exceed (NTE) prices for each Contract Line Items offered. The NTE prices must include all costs, profit and fees

(inclusive of all direct costs, indirect costs, and profit/fee) to provide the product/services. The

NTE prices shall be in Canadian Dollars and shall include Value Added Tax (VAT). The

Contractor shall identify, in the Pricing Table, the Contract Line Items subject to VAT or local

Canadian Government controlled fees.

3.1.9 Pro Forma Commercial Documents

The Offeror’s Price Proposal shall include copies of following pro forma commercial documents of the offeror:

Offeror’s standard commercial contract terms and conditions for the products and services being offered

Offeror’s standard commercial price list for the products and services being offered

Offeror’s standard commercial service level agreements for the products and services being offered

Section 4 Evaluation Criteria

52.212-2 EVALUATION—COMMERCIAL ITEMS (OCT 2014)

(a) The Government will award a contract resulting from this solicitation to the responsible offerors whose offer conforming to the solicitation will be most advantageous to the

Government, price and other factors considered. The following factors, listed in descending order of importance, shall be used to evaluate offers:

Factor 1: Technical Proficiency / Approach

Factor 2: Price

Factor 1 is significantly more important than Factor 2.

(b) A written notice of award or acceptance of an offer, mailed or otherwise furnished to the successful offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer's specified expiration time, the

Government may accept an offer (or part of an offer), whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.

(End of provision)

52.217-4 EVALUATION OF OPTION EXERCISED AT TIME OF CONTRACT

AWARD (JUN 1988)

Except when it is determined in accordance with FAR 17.206(b) not to be in the Government's best interests, the Government will evaluate the total price for the basic requirement together with any option(s) exercised at the time of award.

(End of provision)

Attachment A – TO1 Pricing Tables

See MS Excel worksheet

Attachment B - Telecommunication Requirements by Category and Location

All listed requirements are considered to be estimated maximum requirements.

Category 1: CORE MPLS LOCATIONS

OTTAWA

DESCRIPTION LOCATION QTY PRIORITY

MPLS:

100Mbps Synchronous Data Line for voice, data and video conferencing

U.S. Embassy 1 Core

Digital IP Trunk (IP-to-IP) U.S. Embassy 25 Core

VoIP Trunks (SIP) U.S. Embassy 50 Core

DID Numbers (Individual Extensions) U.S. Embassy 550 Core

TORONTO

MPLS:

50Mbps Synchronous Data Line for voice, data and video conferencing U.S. Consulate Office Bldg. 1 Core

Digital IP Trunk (IP-to-IP) U.S. Consulate Office Bldg. 25 Core

VoIP Trunk (SIP) U.S. Consulate Office Bldg. 50 Core

DID Extensions U.S. Consulate Office Bldg. 225 Core

MONTREAL:

MPLS:

50Mbps Synchronous Data Line for voice, data and video conferencing –

Includes one tail circuit

U.S. Consulate Office Bldg. 1 Core

Digital IP Trunk (IP-to-IP) U.S. Consulate Office Bldg. 25 Core

VoIP Trunk (SIP) U.S. Consulate Office Bldg. 50 Core

VANCOUVER:

MPLS:

50Mbps Synchronous Data Line for voice, data and video conferencing

U.S. Consulate Office Bldg. 1 Core

Digital IP Trunk (IP-to-IP) U.S. Consulate Office Bldg. 25 Core

VoIP Trunk U.S. Consulate Office Bldg. 50 Core

CALGARY:

MPLS:

50Mbps Synchronous Data Line for voice, data and video conferencing

U.S. Consulate Office Bldg. 1 Core

Digital IP Trunk (IP-to-IP) U.S. Consulate Office Bldg. 25 Core

VoIP Trunk (SIP) U.S. Consulate Office Bldg. 50

QUEBEC CITY:

MPLS:

30Mbps Synchronous Data Line for voice, data and video conferencing

U.S. Consulate Office Bldg. 1 Core

Digital IP Trunk (IP-to-IP) U.S. Consulate Office Bldg. 5 Core

VoIP Trunk (SIP) U.S. Consulate Office Bldg. 10 Core

DID Extensions U.S. Consulate Office Bldg. 20 Core

WINNIPEG:

MPLS:

30Mbps Synchronous Data Line for voice, data and video conferencing

U.S. Consulate Office Bldg. 1 Core

Digital IP Trunk (IP-to-IP) U.S. Consulate Office Bldg. 5 Core

HALIFAX:

MPLS:

30Mbps Synchronous Data Line for voice, data and video conferencing

U.S. Consulate Office Bldg. 1 Core

Digital IP Trunk (IP-to-IP) U.S. Consulate Office Bldg. 5 Core

Category 2: OPTIONAL MPLS LOCATIONS

OTTAWA:

DESCRIPTION LOCATION QTY PRIORITY

GSO WAREHOUSE:

30 Mbps Synchronous Data Line for voice, data and video conferencing

GSO Warehouse 1 Optional

Digital IP Trunk (IP-to-IP) GSO Warehouse 3 Optional

VoIP Trunk (SIP) GSO Warehouse 5 Optional

DID Extensions GSO Warehouse 20 Optional

CHIEF OF MISSION RESIDENCE

(CMR):

30 Mbps Synchronous Data Line for voice, data and video conferencing

CMR 1 Optional

Digital IP Trunk (IP-to-IP) CMR 5 Optional

VoIP Trunk (SIP) CMR 10 Optional

DID Extensions CMR 20 Optional

DCMA Annex

30 Mbps Synchronous Data Line for voice, data and video conferencing

DCMA Annex 1 Optional

Digital IP Trunk (IP-to-IP) DCMA Annex 15 Optional

VoIP Trunk (SIP) DCMA Annex 30 Optional

DID Extensions DCMA Annex 50 Optional

TORONTO:

LAW ENFORCEMENT ANNEX:

50 Mbps Synchronous Data Line for voice, data and video conferencing

LE Annex 1 Optional

Digital IP Trunk (IP-to-IP) LE Annex 10 Optional

VoIP Trunk (SIP) LE Annex 20 Optional

DID Extensions LE Annex 50 Optional

MONTREAL (ICAO):

30 Mbps Synchronous Data Line for voice, data and video conferencing

ICAO 1 Optional

Digital IP Trunk (IP-to-IP) ICAO 5 Optional

VoIP Trunk (SIP) ICAO 10 Optional

DID Extensions ICAO 20 Optional

Attachment C – Embassy Consulate 7 Digit Dialing Plan (Site to Site Dialing)

The XXXX is the last four digit of the DID extension

Location Dialing Digit

Ottawa: 613- xxxx

Montreal: 514- xxxx

Toronto: 416- xxxx

Quebec City: 418- xxxx

Halifax: 772- xxxx

Calgary: 403- xxxx

Vancouver: 604- xxxx

Winnipeg: 204- xxxx

Attachment D - Government Furnished Property The Government shall make the following equipment available to the contractor for the 8 sites across Canada as Government furnished property for performance of services under the contract.

Ottawa

MCD/3300 - Core Hardware and Software

1ea -- 50006271 PWR CRD C1310A 125V - NA PLUG

1ea -- 50006513 3300 MXe III 160G SATA HDD

1ea -- 52002545 3300 MXe Media Gateway

Configuration:

1 : 50001247 3300• 128 CH. ECHO CANCELLOR ROHS5

1 : 50003560 DUAL T1/E1 TRUNK MMC

1 : 50005751 DSP II MMC

1 : 500062693300 MXe III Controller

1 : 50006432 Processor - MXe III Controller

2 : 54000303 MCD Network Link License

1 : 54004963 MCD Enterprise Gateway Software

Mitel Communications Director (MCD) - Solution Licenses

2ea -- 54000650 MCD G729 license (8 channels)

Software Assurance

SW_ASSUR Calculated Software Assurance for 12 Additional Months

Calgary

1ea -- 50006266 3300 CX(i) II Controller 8G SATA SSD

1ea -- 50006271 PWR CRD C13 10A 125V - NA PLUG

1ea -- 52002544 3300 CX Media Gateway

Configuration:

1 : 50005160 T1/E1 COMBO MMC II

1 : 50005751 DSP II MMC ,

1 : 50006093 3300 CX II Controller

1 : 54000303 MCD Network Link License

1 : 54004963 MCD Enterprise Gateway Software

1ea -- SW_ASSUR Calculated Software Assurance for 12 Additional Months

Toronto

1ea -- 50006266 3300 CX(i) II Controilier 8G SATA SSD

1ea -- 50006271 PWR CRD C1310A 125V - NA PLUG

1ea -- 52002544 3300 CX Media Gateway

Configuration:

1 : 50005160 T1/E1 COMBO MMC II

1 :…