EIS_RFP_QTA0015THA3003_-_SF30_-_Amend_04_(1).pdf

OMB Approval 2700-0042

1. CONTRACT ID CODE PAGE OF PAGES

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1 95

2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)

04 1/06/2016

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6)

CODE

General Services Administration/FAS/ITS Office of Acquisition Operations

1800 F Street, NW, 4 th

Floor

Washington DC 20405

8. NAME AND ADDRESS OF CONTRACTOR () 9A. AMENDMENT OF SOLICITATION NO.

QTA0015THA3003

X 9B. DATED (SEE ITEM 11)

1710 H. Street, NW, 7 th

Floor 10/16/2015

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is X extended, __ is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:(a) By completing Items 8 and 15, and returning 1 copy of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE

HOUR AND DATA SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and data specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

() A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor _ is not, _ is required to sign this document and return 1 copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

SEE ADDITIONAL PAGES

Except at provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

Timothy Horan Contracting Officer

15B. CONTRACTOR/OFFEROR 15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 16C. DATE SIGNED

(Signature of person authorized to sign)

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV. 10-83)

PREVIOUS EDITION UNUSABLE Computer Generated Prescribed by GSA

FAR (48 CFR) 53.24

RFP # QTA0015THA3003

Amendment #04

Revisions, Questions, Answers and Clarifications to the EIS RFP

This amendment includes the following:

- An extension of the proposal due date.

- Questions received from potential offerors regarding the RFP. The list does not include all of the questions received thus far.

- Answers to the questions listed. Answers include changes to the RFP Sections and clarifications that do not require changes to the RFP Sections.

The revisions, questions, answers and clarifications are listed based on the UCF Sections. The question numbers are from the Acquserve portal and are not in sequential order. Please note that some answers revise more than one section of the RFP.

Extension of Proposal Due Date

The proposal due date is extended. Proposals are due no later than February 22, 2016, 4:00 PM (Eastern Time Zone). Section L.17 has been amended to reflect this change.

The RFP is further amended as follows:

Question # 111 Section: Section B Section # 2.9.1.5

Question:

Line AA00533. Also 2.1.2.4.2 line EN00720 to EN00800. Shared Ethernet 10 Gbps Access is optional. However, the E-LAN Ethernet - 2 Gbps thru E-LAN Ethernet - 10 Gbps are not optional. The E-LAN Ethernet - 2 Gbps thru E-LAN Ethernet - 10 Gbps require a Shared Ethernet 10 Gbps Access facility. Request that the Government make E-LAN Ethernet - 2 Gbps thru E-LAN Ethernet - 10 Gbps (EN00720 to EN00800) optional so they correspond with the Shared Ethernet 10 Gbps Access requirement.

Answer:

The EIS RFP will be amended to change Shared Ethernet 2 Gbps through 9 Gbps (CLINs AA00425-432, AA00525-532) from mandatory to optional CLINs.

E-LAN port CLINs EN00720 to EN00800 for E-LAN Ethernet - 2 Gbps through E-LAN Ethernet - 10 Gbps are mandatory as defined in the RFP to meet agency requirements. For location(s) requiring the Ethernet service, the access will need to be priced using the optional CLIN where applicable to provide the connectivity. The decision was made by the government to make Shared Ethernet 10 Gbps access (CLIN AA00533) optional to avoid requiring offerors to price 10 Gbps Ethernet access at all NSCs with any ethernet access service in the traffic model as required in Section J.1.3.1.1, #3. To be consistent with 10Gbps access being optional, Shared Ethernet 2 Gbps through 9 Gbps (CLINs AA00425-432, AA00525-532) will be changed to optional.

Section C.2.9.1.4 Item 18 Ethernet Access Arrangements, list numbers 3 and 4 will be amended to read:

3. 100 Mbps through 1 Gbps at 100 Mbps increments

4. (Optional) 2 Gbps through 10 Gbps at 1 Gbps increments

Question # 116 Section: Section B

2.2.1.8.2

Question:

Table: A block of telephone numbers can vary in size from 10 or less to 1000. With a single price to cover any size within a broad range, vendors could price higher to cover the cost of large number blocks. We request the Government consider changing the pricing unit for telephone numbers from blocks to a per number unit?

Answer:

The RFP will be amended to update the Telephone Number Block (DID) CLINs defined in Table B.2.2.1.8.3 (SIP Trunk Standard Feature Pricing Instruction Table) as shown below:

NRC, MRC, Description, Charging Unit VI31425, VI32425, SIP Trunk: Telephone Number Assignment and Maintenance, Number VI31430, VI32430, SIP Trunk: Block of 10 DID Numbers Assignment and Maintenance, Block VI31435, VI32435, SIP Trunk: Block of 100 DID Numbers Assignment and Maintenance, Block VI31440, VI32440, SIP Trunk: Block of 1000 DID Numbers Assignment and Maintenance, Block

The RFP will also be amended to update the Telephone Number Block (DID) CLINs defined in Table B.2.2.2.3.4.2 (CSVS Unlimited CONUS or OCONUS Plan-ISDN PRI Features Pricing Instructions Table) as shown below:

NRC, MRC, Description, Charging Unit VS11215, VS12215, ISDN PRI: Telephone Number Assignment and Maintenance, Number VS11235, VS12235, ISDN PRI: Block of 10 DID Number Assignment and Maintenance, Block VS11240, VS12240, ISDN PRI: Block of 100 DID Number Assignment and Maintenance, Block VS11245, VS12245, ISDN PRI: Block of 1000 DID Number Assignment and Maintenance, Block

Question # 210 Section: Section B

2.1.1.4.2

Question:

Table B.2.1.1.4.2 VPNS Feature Prices. Can the government break CLIN VN9000001 into different speed CLINs to match the port speeds requested?

Answer:

Please see Question 419 for the government response.

Question # 214 Section: Section B

2.1.7.3.2

Question:

Table B.2.1.7.3.2 IPS Port Pricing Instructions Table Can the government explain what port speed they are asking to be priced for 9/10 Mbps and 24/25 Mbps IPS ports?

Answer:

The RFP will be amended to change CLIN IP10013 from "IPS - FT3 - 9/10 Mbps" to "IPS - FT3 - 9 Mbps" and CLIN IP10015 "IPS - FT3 - 24/25 Mbps" to "IPS - FT3 - 24 Mbps".

Question # 221 Section: Section B Section # 2.7

Tables B.2.7.2.3 and B.2.7.2.4. Will the government consider making the CLINs in Tables B.2.7.2.3 and B.2.7.2.4 all optional or ICB, as this service's costs vary greatly based on the requirements of the service which are typically defined by the TO (e.g. operator, satellite, coverage, frequency)?

Answer:

To improve flexibility, the RFP will be amended to make CLIN FS00002 "30 GB per month" optional instead of mandatory. CLIN FS00000 "15 GB per month" and CLIN FS00010 "Data Overage" will remain mandatory.

The government will amend the RFP to state that the pricing is only required to be offered within the domestic U.S. Specifically, the last sentence in the introduction will be changed to the following:

"The indicated amount of data included in the Satellite Internet Service plan shall be able to be used at any time of the day within domestic regions (as defined in Section B.2.6 of Wireless Service)."

Question # 225 Section: Section B

2.9.1.5

Question:

Table B.2.9.1.5. The RFP included Shared Ethernet speeds that are not available at all locations as different access providers have different speed increments. All speeds less than 10Mbps and greater than 1Gbps fall into this category. Will the agency please make all of these speeds these Optional?

Answer:

The EIS RFP will be amended to change Shared Ethernet 2 Gbps through 9 Gbps (CLINs AA00425-432, AA00525-532) from mandatory to optional CLINs.

E-LAN port CLINs EN00720 to EN00800 for E-LAN Ethernet - 2 Gbps through E-LAN Ethernet - 10 Gbps are mandatory as defined in the RFP to meet agency requirements. For location(s) requiring the Ethernet service, the access will need to be priced using the optional CLIN where applicable to provide the connectivity. The decision was made by the government to make Shared Ethernet 10 Gbps access (CLIN AA00533) optional to avoid requiring offerors to price 10 Gbps Ethernet access at all NSCs with any ethernet access service in the traffic model as required in Section J.1.3.1.1, #3. To be consistent with 10Gbps access being optional, Shared

Ethernet 2 Gbps through 9 Gbps (CLINs AA00425-432, AA00525-532) will be changed to optional, Also see the answer to Question #111.

For speeds less than 10Mbps, offerors can propose the same price as their next higher speed that they can offer and thus provide the service at the speed the offeror can support.

Section C.2.9.1.4 Item 18 Ethernet Access Arrangements, list numbers 3 and 4 will be amended to read:

3. 100 Mbps to 1 Gbps at 100 Mbps increments

4. (Optional) 2 Gbps to 10 Gbps at 1 Gbps increments

Question # 272 Section: Section B Section # 2.1

Table B.2.1.4.1.5. Would the government please add 2xT1 speed to Table B.2.1.4.1.5 in order to service CONUS to NON-Domestic E1 service.

Answer:

The RFP will be amended to add PLS FT3 T1 x 2 as follows:

Section B: An MRC CLIN will be added to PLS Table B.2.1.4.1.5 for FT3 T1 x 2 Section C: FT3 T1 x 2 will be added as a mandatory technical capability to PLS Section C.2.1.4.1.4 as item "16) Fractional T3. Two adjacent T1 clear channels over an interface of T3 with a line rate of 44.736 Mbps."

Question # 287 Section: Section B

2.2.1.8.2

Question:

Please provide more details on the Description and Charging Units for SIP Trunk Features. For example how many telephone numbers are included in a "block?" No feature description is provided in B.2.1.8 or C.2.2.1.6.2.

Answer:

Refer to response for question #116. The updated Telephone Number Block CLINs, defined in Table B.2.2.1.8.3, with corresponding descriptions will sufficiently describe the total number of telephone number included in each "block".

Question # 345 Section: Section B

2.2.1.8

Question:

Table B.2.2.1.8.3 (SIP Trunk Standard Feature Pricing Instructions Tables) does not define the Telephone Number Blocks to be priced for DIDs. This service is typically priced based on the number of DID Blocks with a different rate based on the number of DIDs in a block (i.e. rate for

50 versus a different rate for 100). How does the Government want offerors to price this given there isn't an option to differentiate by number of DIDs in a block?

Answer:

The RFP will be amended to update the Telephone Number Block (DID) CLINs defined in Table B.2.2.1.8.3 (SIP Trunk Standard Feature Pricing Instruction Table) as shown below:

NRC, MRC, Description, Charging Unit VI31425, VI32425, SIP Trunk: Telephone Number Assignment and Maintenance, Number VI31430, VI32430, SIP Trunk: Block of 10 DID Numbers Assignment and Maintenance, Block VI31435, VI32435, SIP Trunk: Block of 100 DID Numbers Assignment and Maintenance, Block VI31440, VI32440, SIP Trunk: Block of 1000 DID Numbers Assignment and Maintenance, Block

The RFP will also be amended to update the Telephone Number Block (DID) CLINs defined in Table B.2.2.2.3.4.2 (CSVS Unlimited CONUS or OCONUS Plan-ISDN PRI Features Pricing Instructions Table) as shown below:

NRC, MRC, Description, Charging Unit VS11215, VS12215, ISDN PRI: Telephone Number Assignment and Maintenance, Number VS11235, VS12235, ISDN PRI: Block of 10 DID Number Assignment and Maintenance, Block VS11240, VS12240, ISDN PRI: Block of 100 DID Number Assignment and Maintenance, Block VS11245, VS12245, ISDN PRI: Block of 1000 DID Number Assignment and Maintenance, Block

Question # 362 Section: Section B

2.8.1.4.2

Question:

CONUS and OCONUS wireless Out-of-band access for Managed Network Services are mandatory CLINs in a mandatory service. However, Wireless Service and wireless access are both optional and ICB. Will the Government change the wireless OOB access to optional and

ICB?

Answer:

RFP Section B.2.8.1.4.2 will be amended to make CONUS and OCONUS Wireless Out-of-band access optional. If offered, a fixed price is required.

Question # 384 Section: Section B

B.1.2.4

Question:

Is every banded price table required to contain a row where Band Low = 0?

Answer:

Yes. RFP Section B.1.2.4 will be amended to state: Each banded price table shall include a row where Band Low = 0.

Question # 385 Section: Section B

B.2.6.6

Question:

To propose International Mobile Roaming, must both the International Mobile Roaming Bucket and Unlimited Prices table (B.2.6.6.1) and the International Mobile Roaming Catalog table (B.2.6.6.3) be priced, or is it sufficient to price either B.2.6.6.1 or B.2.6.6.3?

Answer:

It is sufficient to price either Table B.2.6.6.1 or B.2.6.6.3 to propose International Mobile Roaming. The RFP will be amended to provide clarification. The following will be added to the RFP at the end of the introduction to Section B.2.6.6.: Both the International Mobile Roaming Bucket and Unlimited Prices Table and the International Mobile Roaming Catalog Table are optional. Therefore, one of the tables may be offered without offering the other table."

Question # 419 Section: Section B

2.1.1.4.2

Question:

Section C.2.1.1.2 defines features of the VPNS services that relate to high-availability options. The options outlined include Load Sharing - Fail-Over Protection - and Diverse Access. These items correspond to Section B.2.1.1.4.2 whereby the pricing table has a single CLIN related to Port - with no specification of port speed required by that CLIN. The requested options outlined in Section C lend themselves to be priced out at the Task Order level (ICB) as each agency's definitions/requirements associated with Load Sharing - Diverse Access/PoPs -or Fail-over protection may be different for each agency. Would the Government consider changing CLIN VN90001 to ICB?

Answer:

The RFP will be amended in table B.2.1.1.4.2 by deleting the high availability option and adding the following sentence to section B.2.1.1.4:

"The requirement in Section C.2.1.1.2, ID Number 1, high availability options, shall be priced using CLINs from other sections such as B.2.9 (e.g., access diversity) and B.2.10 (e.g., a redundant router) or a TUC."

Question # 436 Section: Section B

1.2.5

Question:

Please clarify what the Government means by "no pass through charges".

Answer:

GSA will amend RFP Section B.1.2.5 to include a definition of these charges. Pass-through charges are defined as the actual cost of the service without markup, overhead, or profit.

Question # 481 Section: Section B Section #

2.8.3.2.3

The term "Unlimited" is used in the Unified Communications Service Instruction Table, but is not defined in either B.2.8.3 or C.2.8.3, In this context, what does "Unlimited" mean, what is unlimited?

Answer:

The RFP will be amended to add a note below table "B.2.8.3.2.3" to include the definition of the word "Unlimited" as described below.

The term "Unlimited" used in the "CLIN Description" column of the table B.2.8.3.2.3 means:

"Unlimited Calls/Fax/SMS/Conferencing."

Question # 484 Section: Section B

B.2.1.3.2

Question:

The traffic table contains rows for metro OWS CLIN OW00104, but those rows do not identify the NSCs. In order to satisfy the requirements for pricing OWS, the NSCs must be included in the gen_ows_metro_locations table B.4.1.12.1. Will the government please identify the NSCs for OW00104?

Answer:

The government will amend the traffic model to identify the applicable NSCs for pricing metro

OWS CLIN OW00104.

Question # 517 Section: Section B

1.2.5

Question:

Please clarify what GSA means by "no pass through charges".

Answer:

GSA will amend the RFP Section B.1.2.5 to include a definition of these charges. Pass-through

Question # 545 Section: Section B

2.8.3.2.2

Question:

RFP table B.2.8.3.2.2 has a column for Country/Jurisdiction, but the Unified Comm Services (UCS) does not appear in the service drop down list for non- domestic locations on the AcquServe portal. Should this service be included in the selection for non-domestic locations?

Answer:

Section B Table B.1.2.1.1 will be amended to show UCS as a CBSA based service. The corresponding service reference table will be amended to characterize UCS as a CBSA based service. This will cause UCS to appear in the service drop down list for non-domestic locations on the AcquServe portal.

Question # 556 Section: Section B

2.4.3.1

Question:

Can you confirm that the NSP CLINs in table B2.4.3.1 should be priced at $0? The AcquServe portal will not allow NSP CLINs in this table to upload without a value of $0. If this is correct, is the value for all NSP CLINs for any table $0?

Answer:

Section B.1.2.2 will be amended to state that if a contractor proposes an NSP CLIN, the contractor shall populate the price table with a price of $0 for that CLIN.

Question # 561 Section: Section B

2.2.2.3.3

Question:

Under B.2.2.2.3.3 CSVS General Features Pricing Instructions Table, CLIN VS14425 (Directory Assistance) is defined as an NRC, yet the charging unit is per call, and the corresponding feature description in C.2.2.2.2, ID No. 7 indicates that this feature is associated with individual calls. We recommend GSA change CLIN VS14425 from an NRC to a usage-based CLIN to support proper billing.

Answer:

The RFP will be amended to add a Usage CLIN column to Table B.2.2.2.3.3 and change the frequency for CLIN VS14425 (Directory Assistance), defined in Table B.2.2.2.3.3, from NRC to Usage.

Question # 564 Section: Section B

2.9.1.5

Question:

Under B.2.9.1.5 Access Pricing Instructions Table, CLINs AA00225/AA00325;

AA00226/AA00326; AA00227/AA00327; and AA00228/AA00328 denote Dedicated Ethernet speeds above 1 Gbps. Dedicated Ethernet speeds above 1 Gbps are not an industry standard commercial offering. We recommend that GSA remain with access speeds of 2.5 and 10G only for customer speeds above 1G, as those are the natural service breaks. These speeds are not universally available due to the requirement of modern fiber being available at the customer premise. We recommend CLINs AA00225/AA00325; AA00226/AA00326; AA00227/AA00327;

and AA00228/AA00328 be designated as ICB as well as Optional.

Answer:

The Government has existing 10Gbps and sub-10Gbps Ethernet Access requirements, so the existing speeds for the Dedicated Ethernet Access will not be changed. The service provider, however, can provision service at a higher speed if needed, as long as the agencies' required speed is provided.

The Government understands that 20Gbps, 30Gbps, and 40Gbps Dedicated Ethernet Access services are new technologies that are not universally available. The CLINs AA00226/AA00326;

AA00227/AA00327; and AA00228/AA00328 will be amended to ICB, in addition to the existing Optional.

Question # 568 Section: Section B

2.2.3.4.2

Question:

Under B.2.2.3.4.2 TFS Feature Pricing Instructions Table, CLIN TF99209 (Custom Reporting) is defined as a usage CLIN, and not as an NRC or MRC CLIN. Commercially, usage based charges are typically used in conjunction with metered services. We recommend GSA amend this CLIN TF99209 to be an NRC and/or MRC.

Answer:

The RFP will be amended to change CLIN TF99209 (Custom Reporting) to an NRC and the CLIN will remain ICB.

Question # 571 Section: Section B

2.1.2

Question:

The traffic model includes Access for all data services. However, B.2.1.2 Ethernet Transport does not include access, while the B tables for other data services do. We recommend that GSA amend B.2.1.2 to add the Access component to EthS to be consistent with the other data services in B (VPNS, Private Line, IPS, etc.)

Answer:

The RFP will be amended. Section B.2.1.2 will be revised to add the following statement, "Access arrangements to connect to the contractor's ETS network shall be provided in accordance with Section B.2.9."

Question # 593 Section: Section B

2.1.2

Question:

The Evaluation Traffic Model includes an Access component. However, B.2.1.2 Ethernet Transport Service does not include an Access component. We request that GSA amend B.2.1.2 to include the Access component.

See answer to question 571.

Question # 599 Section: Section B

2.9.1.5

Question:

Under B.2.9.1.5 Access Pricing Instructions Table, CLINs AA00433/AA00533;

AA00434/AA00534; AA00435/AA00535; and AA00436/AA00536 denote Shared Ethernet at speeds of 10 Gbps through 40 Gbps. These speeds are not universally available due to the requirement of modern fiber being available at the customer premise. We recommend AA00433/AA00533; AA00434/AA00534; AA00435/AA00535; AA00436/AA00536 be marked as ICB and Optional.

Answer:

Shared Ethernet Access CLINs AA00433/AA00533, AA00434/AA00534, AA00435/AA00535, and AA00436/AA00536 are already Optional in both the EIS RFP Sections B.2.9.1.5 and C.2.9.1.4. No change will be required to make these Optional.

The Government has existing requirements for Shared Ethernet for 10Gbps, so fixed pricing will be required. However, the Government understands that Ethernet Access speed of 20Gbps, 30Gbps, and 40Gbps are more advanced access speeds and are not universally available. The EIS RFP will be amended to update these Shared Ethernet Access CLINs AA00434/AA00534, AA00435/AA00535, and AA00436/AA00536 to ICB, in addition to the existing Optional.

Question # 602 Section: Section B

2.9.1.5

Question:

Regarding B.2.9.1.5 Access Pricing Instructions Table, CLINs AA00019 & AA00119, SDSL - up to 1.5 Mbps: SDSL is no longer commercially available across CONUS and has been phased out by most ILECs. We recommend that GSA remove this requirement from Access Arrangements, or make it ICB to reflect the limited availability.

Answer:

The EIS RFP will be amended to change CLINs AA00019 and AA00119 (SDSL - up to 1.5 Mbps) to ICB. Also, see the answer to Question #627.

Question # 603 Section: Section B

2.2.2.3.3

Question:

Under B.2.2.2.3.3 CSVS General Features Pricing Instructions Table, CLIN VS14420 (Internal Agency Accounting Code) is defined as an NRC, yet the charging unit is per call, and the corresponding feature description in C.2.2.2.2, ID No. 6 indicates that this feature is associated with individual calls. We recommend GSA change CLIN VS14420 from an NRC to a usage-based CLIN to support proper billing.

Answer:

The RFP will be amended to change the frequency for CLIN VS14420 (Internal Agency Accounting Code), defined in Table B.2.2.2.3.3, from NRC to Usage.

Question # 609 Section: Section B

2.9.1.5

Question:

Under B.2.9.1.5 Access Pricing Instructions Table, CLINs AA00425/AA00525;

AA00426/AA00526; 00427/AA00527; AA00428/AA00528; AA00429/AA00529; 00430/AA00530;

AA00431/AA00531; AA00432/AA00532 denote Shared Ethernet at speeds of 2 Gbps through 9 Gbps. These speeds are not an industry standard commercial offering. We recommend that GSA remain with access speeds of 2.5 and 10G only for customer speeds above 1G, as those are the natural service breaks. These speeds are not universally available due to the requirement of modern fiber being available at the customer premise. We recommend

AA00425/AA00525; AA00426/AA00526; AA00427/AA00527; AA00428/AA00528;

AA00429/AA00529; AA00430/AA00530; AA00431/AA00531; and AA00432/AA00532 be marked as Optional and ICB.

Answer:

See the answer to question 111. These CLINs will be amended to Optional.

As for the ICB, the Government has existing requirements for these CLINs, so these CLINs need to remain fixed price and will not be changed to ICB.

Question # 617 Section: Section B

2.2.1.2

Question:

Traffic Model - table traffic_1loc_nsc. IPVS CLINs VI21110 and VI22110 in the traffic model (table traffic_1loc_nsc) are associated with the B table with ID 22121 for CONUS, OCONUS and NON-DOMESTIC jurisdictions. B table 2.2.1.2.1 is the IPVS CONUS price table. Will GSA amend the traffic model to associate these OCONUS and NON-DOM entries with table 2.2.1.2.2?

Answer:

GSA will amend traffic table traffic_1loc_nsc to associate CLINs VI21110 and VI22110 with btable_id 22122 when used with OCONUS and NONDOM jurisdictions.

Question # 624 Section: Section B Section # 2.9

Section B.2.9, B.2.9.1.5 Access Arrangement (and the Traffic Model) indicate that E1 and E3 CLINs (NRC AA00012/MRC AA00112 and NRC AA00013/MRC AA00113, respectively) are non-domestic only, however the traffic model includes E1 access requirements for locations in Alaska, Hawaii, Puerto Rico, Guam and Maryland, and E1 access requirements for a location in HI. Will GSA amend the traffic model for consistency with the price structure as defined in Section B.2.9?

Please see the government's response to question #286. In addition, please note that the traffic model included with this Amendment will include revisions to some of the domestic E1 and E3 traffic requirements.

Question # 627 Section: Section B

2.9.1.5

Question:

AA instructions provide mandatory CLINs for xDSL service, not common among non-traditional Offerors and marked as optional for IP service. When a similar issue with OC-3 occurs, the Government allows offerors to only bid OC-3 where it currently exists. Will the Government please consider making xDSL AA CLINs optional except where they currently exist?

Answer:

The EIS RFP will be amended in Section B.2.9.1.5 with the following as ICB:

AA00019/AA00119 SDSL - up to 1.5 Mbps AA00020/AA00120 ADSL - up to 1.5 Mbps download AA00021/AA00121 ADSL - up to 5 Mbps download AA00022/AA00122 ADSL - up to 8 Mbps download

Question # 628 Section: Section B

2.6.7.2

Question:

MWS instructions provide a mandatory Personal Hotspot CLIN for Unlimited Data plans, a feature many Offerors will be prohibited from pricing. Will the Government please consider re-labeling CLIN WL02004 as optional?

Answer:

RFP Table B.2.6.7.2 will be amended as follows. CLIN WL02004 will remain a mandatory feature, however, the Description will change to "Personal Hotspot (5 GB minimum) --applicable only to the Unlimited Data Add-on plan."

Further, the following will be added at the end of the last paragraph under Section B.2.6.2 Domestic Mobile Data Add-on Services:

"The data used for Personal Hotspots will be subtracted from the base Data Add-on plan except in the case of when the Personal Hotspot feature is ordered with the Unlimited Data Add-on plan. In that case, the data used will be subtracted from the Personal Hotspot data allowance (5 GB minimum). Any Personal Hotspot overages may be billed via CLIN WL00020 Pooling Overage for Data Add-on."

Question # 632 Section: Section B

2.8.6.3.2

MMS instructions provide two File Sharing CLINs priced by user, with no upper bound on storage space. Will the Government please establish a maximum level or storage space per user for CLINs MM02010 and MM02000?

Answer:

The RFP Section 2.8.6.3.2 will be amended as follows:

The Description for MM02010 "On Premises File Sharing Per User" will be changed to "On Premises File Sharing Per User with unlimited data storage scalability."

The Description for MM02000 "Cloud File Sharing Per User with unlimited storage" will be changed to "Cloud File Sharing Per User with unlimited storage (minimum of 1 TB of online storage per user)."

Note that only one of these CLINs must be offered for Mobile Content Management. A task order unique CLIN (TUC) can be used for specific storage options.

Question # 636 Section: Section B

2.8.6.1.1

Question:

MMS instructions indicate that Offerors should submit $0 prices for NSP items, which are priced at $0 by definition. Will the Government please clarify that Offerors should submit $0 prices for NSP items contract-wide?

Answer:

Section B.1.2.2 will be amended to state that if a contractor proposes an NSP CLIN, the contractor shall populate the price table with a price of $0 for that CLIN.

(Note that this question is similar to 556.)

Question # 638 Section: Section B

2.8.4.5.2

Question:

MTIPS instructions provide a mandatory Extranet Connection CLIN, priced by node, for 100+ users per node, with no upper bound on number of users. Will the Government please establish a maximum number of users per node for CLIN MT91025?

Answer:

The maximum number of users for CLIN "MT91025" is unlimited.

However, RFP Section 2.8.4.5.2 will be amended to change CLIN "MT91025" (Extranet Connection (CONUS and OCONUS, 100+ users at the node)), and CLIN "MT91019" (Remote Access (CONUS and OCONUS, 101+ seats)) to ICB CLINs. This change will allow flexibility in managing CLINs listed above.

Question # 682 Section: Section B Section # 2.6

Will the Government limit the Non Throttled Unlimited Data requirement to only single user data sessions?

Answer:

For Data Only Unlimited plans, the government will allow contractors to limit the plans to a single user data session, such that only one user may transmit and receive data over the wireless device during each data session.

RFP Section 2.6.3.2 will be amended. The Description for CLIN WL00120 will be changed to the following:

"Unlimited Data Only (may be limited to a single user per data session)."

Question # 691 Section: Section B

2.8.1.3.2

Question:

States CLIN descriptions for 'Managed Network Implementation, Maintenance and Management' integrated WAN ports in multiple sizes (Extra-Small, Small, Medium, Large, and Extra-Large). Will the government please clarify how the sizing relates to integrated WAN port size?

Answer:

The RFP will be amended. The title of Table 2.8.1.3.2 will be changed from "Managed Network Implementation, Management and Maintenance Pricing Instructions Table for Integrated WAN Ports" to "Managed Network Implementation, Management and Maintenance Pricing Instructions Table for Managed Devices."

The government is not defining "small", "medium", etc. The offeror shall describe their approach to device size assignment as required in Section L.34.1 Price Response, bullet #8. In addition, if an offeror decides to propose SREs, then each device shall be classified in the SRE catalog (section B.2.10.2.1 SRE Catalog - Product Specification Table), specifically the field labeled "device size".

Question # 715 Section: Section B

2.2.2

Question:

Under B.2.2.2 Circuit Switched Voice Service states: "Contractors shall provide pricing for all non-domestic and OCONUS countries/jurisdictions specified in Table B.4.2.1." In countries where service is not commercially available or supported, may vendor omit pricing for those locations?

Answer:

Contractors are only required to provide pricing for the OCONUS and non-domestic countries/jurisdictions where they plan to offer the service.

The RFP will be amended to revise Section B.2.2.2 to clarify the requirement as below:

Contractors shall provide off-net termination pricing to all OCONUS and non-domestic countries/jurisdictions specified in Table J.1.2.1. Additionally, contractors shall provide pricing for all the OCONUS and non-domestic countries/jurisdictions, specified in Table B.4.2.1, where the service will be offered.

Question # 732 Section: Section B

2.9.1.5

Question:

Under B.2.9.1.5 Access Pricing Instructions Table includes CLINS AA00808/AA00908 -Shared Ethernet Access 2 Gbps committed, scalable to 10 Gbps; and AA00809/AA00909 -Shared Ethernet Access 3 Gbps committed, scalable to 10 Gbps. These are not industry standard commercial offerings. These speeds are not universally available due to the requirement of modern fiber being available at the customer premise. We ask GSA to provide relief for these services so that they are only priced as ICB and Optional. We recommend CLINS AA00808/AA00908; and AA00809/AA00909 should be marked as optional and ICB as this bandwidth is not an industry standard commercial offering.

Answer:

The RFP will be amended in Section B.2.9.1.5 to make the following CLINs optional:

AA00808/AA00908 Shared Ethernet Access 2Gbps committed, scalable to 10Gbps AA00809/AA00909 Shared Ethernet Access 3Gbps committed, scalable to 10Gbps

Question # 751 Section: Section B

2.2.2.3.4

Question:

Under B.2.2.2.3.4 CSVS Unlimited CONUS to CONUS Plan Features Pricing Instructions, each of the Plan Features pricing tables include only CONUS to CONUS. However, the traffic model for CSVS also includes OCONUS locations. Does GSA expect vendors to price OCONUS as well? If so, please we ask that GSA amend the RFP to include the appropriate pricing tables.

Answer:

The Government requires CSVS Unlimited Plan Features prices for both CONUS and OCONUS to be provided.

The RFP will be amended to revise the headings and instructions for CSVS Unlimited Plan Features, defined in Section B.2.2.2.3.4, to be applicable to both CONUS and OCONUS. The contractors are to use the already defined pricing tables B.2.2.2.3.1 CSVS Features CONUS Prices Table and B.2.2.2.3.2 CSVS Features OCONUS and Non-Domestic Prices Table to provide the corresponding CONUS and OCONUS prices. RFP sections B.2.2.2, B.2.2.2.1, and B.2.2.2.3 will also be amended to clarify the pricing instructions for Unlimited Plans in CONUS and OCONUS regions.

Question # 762 Section: Section B Section #

2.11.3

B.2.11.3 CONUS Pricing refers to J.11 for definitions of CONUS, OCONUS and Non-Domestic.

However, J.11 is only the list of abbreviations. GSA should change this reference of J.11 to J.12 to correct the error.

Answer:

The RFP will be amended to change the reference in Section B.2.11.3 from "Section J.11" to "Section J.12."

Question # 787 Section: Section B Section # 1

A. SF33 Solicitation, Offer and Award. Section 9. Given the large scope and complexity of the pricing proposal we request that the GSA please extend the due date for volume 6, "Price Volume" to February 5, 2016. Under our proposal, all other volumes of the EIS proposal will remain due on January 15 2016. We believe that is necessary and in the best interest of the government as well as industry, because it will provide time for each bidder to ensure that they can accurately and completely integrate all pricing elements in the submission. The ability to perform iterative detailed pricing review and validation during this period prior to submission will reduce the potential for errors, and yield more competitive prices.

Answer:

The entire proposal must be submitted in accordance with the instructions in Section L of the RFP. The due date for receipt of proposals will be extended to February 22, 2016.

Question # 807 Section: Section B

2.9.1.5

Question:

CLINs AA00920 through AA00930 - Will GSA make the referenced service both an optional service and a part of the Managed service offering? Not all vendors will be able to offer this service on a global basis and it requires a management intervention in any case.

Answer:

To be consistent with other sections of the EIS RFP, AA00920, AA00921, AA00922 will remain mandatory. The RFP will be amended to add Optional in Table B.2.9.1.5 in the Notes column for CLIN AA00923. The revised note will read: Optional. Requires scalable Ethernet Access circuit.

The AA00920 to AA00930 CLINs will remain as Access Arrangement, not managed service, requirements. The offerors are encouraged to explain in the proposals how these will be supported and provisioned.

Question # 822 Section: Section B

1.2.5

Please clarify what GSA means by "no pass through charges".

GSA will amend the RFP Section B to include a definition of these charges. Pass-through

Question # 823 Section: Section B

1.2.5

Question:

Does "no pass through charges" pertain to inclusion of the Government Fee?

Answer:

No. GSA will amend the RFP Section B to include a definition of these charges. Pass-through

Question # 837 Section: Section B

2.9.1.5

Question:

Will GSA consider making CLINs A00119 through A00122 optional offerings? xDSL offerings are not globally available from many vendors

Please see the answer for question #627.

Question # 863 Section: Section B

2.9.1.5

Question:

Ethernet bandwidths of 2 through 9 Gbps are not commonly available from carriers, however are part of the mandatory Access Arrangement requirements for Shared Ethernet Access.

These requirements were added with the final RFP. Most carriers this bidder has approached have refused to provide costs for Ethernet bandwidths of 2 through 9 Gbps. Will the Government consider making the Ethernet access bandwidths from 2 to 9 Gbps optional, as it has OC-3 access?

Answer:

Please see the answer for question #111. The RFP will be amended to make Shared Ethernet Access CLINs for 2Gbps through 9Gbps Optional.

Question # 876 Section: Section B

1.2.1.1

National Security and Emergency Preparedness (NS/EP) and General are identified in Table

B.1.2.1.1 as Optional Services, which is not consistent with C.1.8.1. Are NS/EP and General to be included in Section 1 of Volume 6, Price Response, for compliance with the "rationale and strategy, by service" requirement cited in Section L.34.1(5)? If yes, please provide Section C revisions for consistency.

Please see Question #409 for the government's response.

Question # 891 Section: Section B

2.9.1.5

Question:

EXCEPTION REQUEST: Section B.2.9.1.5 provides the list of mandatory and optional access CLINs for the EIS location set. This table includes CLINs AA00525 through AA00532 (MRC) and AA00425 through AA00432 for Shared Ethernet Access at bandwidths between (and including) 2Gbps and 9Gbps. These bandwidths are available on a limited basis nationwide, the access providers that offer this access in limited geographical footprints price it as ICB, and in many cases these are deployed as 10Gbps access circuits. Requiring that these be priced as firm-fixed price for all locations will limit offerors' ability to maximized coverage. Would GSA make these CLINs Optional (consistently with the definition for 10Gbps Shared Ethernet Access)?

Answer:

Please see the answer for question #111. The RFP will be amended to make Shared Ethernet Access CLINs for 2Gbps through 9Gbps Optional.

Question # 136 Section: Section C

2.1.5.1.4

Question:

Item 9a. OC1 is not a commonly used service interface. Recommend changing OC-1 to OC-3

Answer:

The RFP will be amended. Item 9 causes confusion and is redundant as interfaces are identified in C.2.1.5.3. Item 9 language will be removed and marked as Reserved. OC-1 remains an optional interface identified in C.2.1.5.3.

Question # 137 Section: Section C

2.1.5.1.4

Question:

Item 9b. STS-1 is not a commonly used electrical service interface. Recommend changing STS- 1 to DS3

Answer:

The RFP will be amended. Item 9 causes confusion and is redundant as interfaces are identified in C.2.1.5.3. Item 9 will be marked as Reserved. STS-1 and DS3 remain optional interfaces identified in C.2.1.5.3.

Question # 304 Section: Section C

2.1.1.3

Question:

UNI Type 5 specifies 320 Kbps up to 150 Mbps but in Access arrangements section C.2.9.1.4

(19) access only goes to 30 Mbps. Please clarify or correct this inconsistency.

Answer:

The RFP will be amended as follows for consistency between VPNS, IPS, and Access Arrangement specifications for Cable High Speed Access:

Section C.2.1.1.3 UNI Type #5 Cable High Speed Access: 256 Kbps up to 150 Mbps (Standard:

DOCSIS 3.0)

Section C.2.1.7.3 UNI Type #1 Cable High Speed Access: 256 Kbps up to 150 Mbps (Standard:

DOCSIS 3.0)

Section C.2.9.1.4 Item 19 a) 3. From 256 Kbps to 150 Mbps (Standard: DOCSIS 3.0).

Question # 305 Section: Section C

2.1.7.1

Question:

UNI Type 1 specifies 320 Kbps up to 150 Mbps but access in C.2.9.1.4 (19) only requires access to 30 Mbps. Please clarify or correct this inconsistency.

Answer:

Per Q&A #304: The RFP will be amended as follows for consistency between VPNS, IPS, and Access Arrangement specifications for Cable High Speed Access:

Section C.2.1.1.3 UNI Type #5 Cable High Speed Access: 256 Kbps up to 150 Mbps (Standard:

DOCSIS 3.0)

Section C.2.1.7.3 UNI Type #1 Cable High Speed Access: 256 Kbps up to 150 Mbps (Standard:

DOCSIS 3.0)

Section C.2.9.1.4 Item 19 a) 3. From 256 Kbps to 150 Mbps (Standard: DOCSIS 3.0).

Question # 306 Section: Section C

2.1.7.1

Question:

UNI Type 6 specifies 10 to 300 Mbps but access in C.2.9.1.4 (20 ) only requires 150 Mbps.

Please clarify or correct this inconsistency.

The correct Section Number reference is C.2.1.7.3 Item #6.

Section C.2.1.7.3 IPS UNI # 6 for FTTP will be amended to read "256 Kbps up to 150 Mbps".

Section C.2.9.1.4 Item 19 a) will be amended to read: "a) Provide data rates of 256 Kbps up to 150 Mbps."

Question # 321 Section: Section C

1.8.1

Question:

Section C.1.8.1 states that "IT-related products and services listed in the table above may be acquired only if they are associated to an infrastructure or telecommunications solution acquired through this contract." Does this statement allow for the IT-related products and services to be purchased from a different EIS supplier than the infrastructure or telecommunications solution?

Answer:

The last sentence of Section C.1.8.1 will be amended to change "this contract" to "EIS" and will now state:

"IT-related products and services listed in the table above may be acquired only if they are associated to an infrastructure or telecommunications solution acquired through EIS."

Under this scenario the answer to the question is yes.

Question # 324 Section: Section C

2.1.5.3

Question:

Item 9.b) States, " Electrical interfaces shall be supported from DS1 through STS-1". Are these electrical interfaces to be used as part of the Transmux capability? Or is there an implied requirement to implement a Fiber Hub for aggregation?

Answer:

The RFP will be amended. C.2.1.5.1.4 Item 9 causes confusion and is redundant as interfaces are identified in C.2.1.5.3. Section C.2.1.5.1.4 Item 9 technical capabilities will be deleted and will be marked as Reserved.

Question # 353 Section: Section C

2.2.3.2

Question:

C.2.2.3.2, page 102. Requirement is to provide a faxback (or equivalent) service as part of IVR.

Faxback is not widely used by US Gov Agencies and requires a high degree of customization.

Therefore we request that Faxback be made an OPTIONAL service and listed separate from the overall IVR requirements.

Yes. The RFP will be amended to make Section C.2.2.3.2 feature 14 (Interactive Voice

Response), Item 8 optional.

Question # 358 Section: Section C

2.1.2.1.4

Question:

C.2.1.2.1.4 # 24, page 27. GSA may have referenced an incorrect specification for Ethernet Bridging. The IEEE Specification IEEE 802.1X-REV is related to Ethernet security and not to Ethernet bridging. The IEEE 802.1Q (2014) standard provides the specifications for well established LAN to LAN bridging functions. Will GSA amend the solicitation to remove 802.1X- REV as a requirement for Ethernet Bridging and replace it with IEEE 802.1Q (2014)?

Answer:

The RFP Section C.2.1.2.1.4 # 24 will be amended to read "24.The contractor shall support bridging in compliance with IEEE 802.1Q (2014)."

Question # 365 Section: Section C Section # 2.1

Could the government please add the clarification asterics of mandatory services from section B.1.2.1.1 to section C.1.2; where it states that the EIS mandatory services include "Voice Specified in Section C.2.2.1 and C.2.2.2"? All other sections in reference to mandatory services are clear that either/or should be selected on a CBSA by CBSA basis. (B.1.2.1.1, C.2.2, and B.2.2)

Answer:

No additional language is necessary in Section C.1.2. Section C.2.2 incorrectly identifies a reference to pricing which will be amended per Q&A #486.

Question # 366 Section: Section C

2.1.3.1.4

Question:

C.2.1.3.1.4 #2. Could GSA please replace all uses of CONUS in OWS where they intend for it to actually be "Domestic" in alignment with GSAs own definitions? Currently it is written "CONUS Wavelengths This is applicable for inter-city connectivity within the United States and Territories not in the continental US." (CONUS also referenced in #4 and #5 of OWS where we believe GSA might have meant Domestic.)

Answer:

Section C.2.1.3.1.4 Item 2 of the RFP will be amended to refer to Domestic Wavelengths. In Items 4 and 5c, CONUS will be replaced by domestic.

Question # 368 Section: Section C Section #

2.8.7.1.4

#5 Automatic Port Expansion. The requirement for additional port expansion without operator assistance is non- industry standard. Once the bridge is up, additional ports cannot be added.

Additional USERS can be added up to 300, however, physical ports cannot be added. Will the Government please clarify: "ports" should be "users" or callers into the actual conference?

Answer:

C.2.8.7.1.4 #4 Automatic Port Expansion is the correct reference. The RFP will be amended to read automatic expansion 'to support additional users" replacing automatic expansion to 'additional ports."

Question # 376 Section: Section C

2.1.2.3

Question:

Recommend GSA consider making this Signaling Protocol Type/Granularity - 1000Base optional as it is not widely used.

Answer:

The RFP will be amended to make the 1000Base interface optional.

Section C.2.1.2.3 UNIs # 18 and 19 (1000BASE-LX/SX) optical, multi-mode will be made optional. This will make all 1000BASE UNIs (electrical and optical) optional.

Question # 377 Section: Section C

2.1.2.3

Question:

Recommend GSA consider making this Signaling Protocol Type/Granularity - 1000Base-LX optional as it is not widely used.

Answer:

The RFP will be amended to make the C.2.1.2.3 (18) 1000BaseLX interface optional as described in the answer to question #376.

Question # 378 Section: Section C

2.1.2.3

Question:

Recommend GSA consider making this Signaling Protocol Type/Granularity - 1000Base-SX optional as it is not widely used.

Answer:

The RFP will be amended to make the C.2.1.2.3 (19) 1000Base SX interface optional per the answer to question #376.

Question # 405 Section: Section C

2.1.2.4

Question:

Notes # 6 + 7 - Performance Metrics (Ethernet) Last box in the KPI states - Grade of Service (Packet Loss=1-GoS) with Routine and Critical defined in terminate of minutes/ms. The notes aligned to the Grade of Service line imply that the services are resilient services - as they refer to Spanning Tree and Service Restoration. Please clarify what is meant by "Grade of Service" in this context?

Answer:

The RFP will be amended. In C.2.1.2.4. The KPI term "Grade of Service (Packet Delivery) Rate)" will be changed to "Grade of Service (Packet Delivery) ". Additionally, the KPI term "Grade of Service (Packet Loss = 1-GoS)" will be changed to "Grade of Service (Fail Over Time)".

Note 7 will be deleted.

Note 6 will apply to the KPI Grade of Service (Fail Over Time) for both Routine and Critical service levels.

Also, Section G.8.2.1.1.1 Service-Specific SLA Table will be amended for item Ethernet Service to change the following KPIs:

a) Grade of Service (Packet Delivery) instead of Grade of Service (Packet Delivery Rate) ;

b) Grade of Service(Fail Over Time) instead of Grade of Service(Packet Loss).

Question # 422 Section: Section C

2.1.2.4

Question:

Performance Metrics (Ethernet): Last box in the KPI states - Grade of Service (Packet Loss=1- GoS) with Routine and Critical defined in terms of minutes/ms. There are follow-on notes for these line items that imply this line item has to do with restoration of services in high-availability modes. Please clarify what is meant by "Grade of Service" in this context.

The RFP will be amended. Please see the answer to Question 405.

Question # 423 Section: Section C

2.1.1.1

Question:

"The contractor shall accommodate and optimize an agency's applications to enable the network to accurately and consistently allow for traffic prioritization and cost efficiencies": what does Government mean by "optimize an agency's application's"?

The last two paragraphs of Section C.2.1.1.1.1 will be amended to read:

The contractor shall accommodate and optimize an agency's applications to enable the network to accurately and consistently allow for traffic prioritization and cost efficiencies to support the following VPNS traffic types:

1. Time-critical traffic such as voice and video.

2. Business-critical traffic such as transactions.

3. Non-critical traffic such as email.

Question # 425 Section: Section C

2.1.2.3

Question:

UNI Types 1 and 2 reference IEEE standard 802.3z and specify a payload rate of 1.25 Gbps.

Under this standard - the encoded line rate is 1.25 GB but the throughput rate is 1 GB. If the Government wants 1.25GB throughput - it will require the next higher bandwidth: will the Government revise this requirement to be 1.0 Gbps payload rate?

Answer:

The RFP will be amended. Section C.2.1.2.3 UNI Types 1 and 2 Payload Data Rate or Bandwidth requirements will be changed to 1 Gbps.

Question # 485 Section: Section C

2.1.5.1.4

Question:

Item 9 addresses optical interfaces. This is redundant and unnecessary as they are provided in C.2.1.5.3 and generated questions 137 and 324 with offerors trying to read too much into Item 9.

Answer:

The RFP will be amended. Section C.2.1.5.1.4 Item 9 language will be deleted and will be marked as Reserved.

Question # 486 Section: Section C…