EIS_RFP_QTA0015THA3003_-_SF30_-_Amend_01_Q A_-_FBO.docx

OMB Approval 2700-0042

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

7. ADMINISTERED BY (If other than Item 6)

CODE

General Services Administration/FAS/ITS Office of Acquisition Operations 1800 F Street, NW, 4th Floor Washington DC 20405

QTA0015THA3003

1710 H. Street, NW, 7th Floor

10/16/2015

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

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 |_| extended, X 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.

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.

Timothy Horan Contracting Officer

(Signature of person authorized to sign)

(Signature of Contracting Officer)

RFP # QTA0015THA3003

Amendment #01

Questions, Answers and Clarifications to the EIS RFP

Listed below are the following:

· 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.

· Clarifications to the RFP provided by the Government that were not based on a potential offeror’s question. The Government entered questions into Acquserve in order to document the corresponding clarification.

The RFP questions, answers and clarifications contained herein do not include any changes to the RFP. This document is being issued using an SF30 and amendment number for tracking purposes only; however, the RFP is not being amended as a result of any of the questions, answers or clarifications contained herein.

The Government does anticipate issuing a subsequent SF30 that contains questions and answers that will result in a formal amendment to the RFP.

The 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.

Question:

In 'wdm_eis.btables_ref' table, table name "pls_domestic_transport_prices_icb", the 'btable_no' is "2.1.4.1.2.1". However, the table is referenced in Section B.2.1.4.1.2 of 'EIS_RFP_Section_B_Final'. In this case, did the Government intend for the 'wdm_eis.btables_ref' table and 'EIS_RFP_Section_B_Final' not to be alike? Additionally, the table is referenced in Section B.2.1.4.1.2 of 'EIS_RFP_Section_B_Final' is for ICB and non-ICB pricing.

Answer:

For the purposes of efficiently performing error checking and pricing and to facilitate the storage of fixed prices versus ICB prices, many of the Section B tables have two versions in the EIS AcquServe database. Yes, the Government intend for the ICB version to have a different table number of "2.1.4.1.2.1". There is a table that represents the fixed price version for PLS domestic transport prices - "2.1.4.1.2" in the EIS AcquServe database that the offeror shall use to propose fixed prices. The ICB version may be used for EIS post-award price storage.

Question:

The Networx contract historical pricing information is publicly available at https://released prices.networx.gov. The on-line Networx Unit Pricer tool only allows for searches and data mining on an individual CLIN basis. Would it be possible for the GSA to release the entire Networx historical pricing database to the EIS proposal offeror's?

Answer:

The current year Networx pricing is posted on the Pricer per the T&Cs of the contract and we will not be providing additional information at this time.

Question:

The Government has requested postalized pricing for Optical Wave Services which is not the traditional way that industry prices this services. Should OWS pricing be ICB?

Answer:

OWS pricing on EIS is not postalized.

OWS shall be priced by fixed-price mileage bands. The number of bands and the range of each is at the offeror's discretion. Given the now highly-predictable per-mile costs for OWS (or DWDM), the government is requesting fixed prices for the service. The offeror is encouraged to use this EIS pricing feature to provide agencies simplified ordering at low predictable prices.

Instructions for entering prices defined by bands is found in RFP Section B.1.2.4

The required method for calculating mileage for determining which band an agency's requirement falls into is provided in RFP Section B.2.1.7.

Question:

Is an offeror's Cloud Catalog restricted to the subservices identified in C.2.5.1.1, or may it include other services as well, e.g., Community cloud?

Answer:

Any cloud service that meets the Government's security and compliance requirements may be in the offeror's Cloud Catalog.

Question:

The Government states that vendors are required to associate Physical Concentration Locations (PCLs) to Points of Presence (POPs) using Table B.4.1.5. In many cases, the contractor's POP can also be a PCL so can the PCL NSC code listed in Table B.4.1.5 be the same as the NCS Code listed for the associated POP when they are the same physical location or does the contractor need to assign a POP NSC code that is different from the PCL NSC Code for locations that perform both functions?

Answer:

In those cases where the PCL and the POP are at the same location, the contractor can use the same Network Site Code to represent both.

Question:

The Government has provided a list of 79,809 unique site locations by NSC that contractors are supposed to price against.. If the contractor intends to provide services to facilities in a given CBSA does the contractor have to provide all mandatory services to all facilities listed in the GSA provided location database that reside in that CBSA? This becomes a challenge when providing Access Services as not all access service types are commercially available at all end customer locations. The table used to map end customer locations to a PHub (Table B.4.1.7) only allows for differentiation by broad categories of access type (i.e. Wireline, Ethernet, Cable, FTTP, Wireless) but not specific service types within each category. For example, a given location might have wireline access but not above T3. Since each customer building NSC is mapped to a contractor defined PCL in Table B.4.1.6 and each PCL to POP combination can be defined to support a selected set of bandwidths in Table B.4.1.5.1.1 is that the means by which the Government intended contractors to be able to define which Access Services are available at a given customer location?

Answer:

There are 63,550 NSCs that contractors may propose pricing for. For each CBSA proposed, the contractor is required to price mandatory access CLINs at every NSC according to the requirements in Section B and Section J.1 and specifically J.1.3.1.1.

For a given CBSA, a set of NSCs are identified in the Traffic Model. Only those NSCs will require access pricing for the given CBSA. Only Wireline and Ethernet access types are mandatory. However, the access pricing required for a given NSC within that CBSA depends on the access type(s) found in the traffic model for that NSC.

For example, if an NSC has non-zero traffic quantities defined for only Wireline access, and no Ethernet access types, then Wireline access prices shall be provided in accordance with the instructions in J.1.3.1.1. In this example, however, Ethernet access prices may be provided but are not required.

Within the Wireline Access CLINs found in B.2.9.1.5, note there are both mandatory and optional Wireline Access CLINs as designated in the "Notes" column. Note also that J.1.3.1.1 includes specific instructions for handling the OC-3c CLIN. The OC-3c CLIN may be mandatory or optional depending on whether it has a non-zero traffic quantity for a given NSC. Therefore, continuing with the example where a given NSC has only Wireline traffic found in the Traffic Model, and further assuming that no OC-3c traffic is found as part of that Wireline traffic for that NSC, then the mandatory access pricing required for this example NSC shall be for Wireline access mandatory CLINs only, and may exclude OC-3c, and those marked "ICB", "Optional", and "Non-domestic only."

Only those Access Services where prices are offered in accordance with the instructions in J and priced using the appropriate B.2.9 and B.4 tables are considered "available" at a given NSC.

Table B.4.1.6 (NSC to PCL Relationship Table) indicates which PCL an NSC is mapped to and Table B.4.1.5 (Domestic PCL to POP Relationship Table) defines which bandwidth combinations for a given PCL map to a given POP. Both tables are used to define an offeror's underlying physical infrastructure that supports the access network for various speeds and services. The two tables also indicate which POP is to be used for pricing services such as PLS and OWS. Table B.4.1.7 (NSC to PHub Relationship Table) along with Table B.2.9.1.1 identify the prices for each access speed and type for each Domestic NSC.

Question:

Table B.4.1.7 requires each Building NSC to PHub assignment to list the Access Type provided but does not explain how to populate that field when multiple access types can be offered for a given location. For example, the Government states that the contractor is to use an Array for other tables such as B.4.1.5.1.1 with the numbers separated by commas and enclosed in brackets. For example {1, 2, 3, 4}. Does the Government intend for the contractor to fill in Table 4.1.7 in this same way for the identified access types?

Answer:

In the case where a contractor wants to indicate multiple NSC to PHub relationships with different access types, the contractor should insert a row for each instance of a NSC to PHub and access type combination. For example, the contractor should insert two rows as follows to indicate both wireline and Ethernet are assigned for the same NSC to PHub combination:

Row 1 - NSC A, PHub B, 1 Row 2 - NSC A, PHub B, 2

Do not use arrays for Table 4.1.7.

Question:

The Government has created the concept of a Pricing Hub (PHub) for use on EIS. The contractor is required to price all Access Services by PHub with all access prices at a given PHub the same for each service type; regardless of the customer location. The contractor is required to map each end customer location by Building NSC to a PHub ID in Table B.4.1.7. Since most if not all PHubs are also a POP and a PCL, does the PHub ID need to be unique or can the contractor use the same ID assigned to the POP that is also a PHub?

Answer:

While Phub IDs can be the same as POPs or PCLs or any NSC, they can also be any label the contractor deems best for representing the PHub. For example, a PHub ID may have the ID of "Capital PHub" or "Chicago" or "PHub 1".

In addition, to be clear, the access price at a given PHub is the same for a given access CLIN, and is not necessarily the same across all CLINs.

Question:

Table: There are typically three basic types of lines needed for telephone service. One has a full set of configurable features and voicemail. The other two have minimal features and no voicemail. The full featured lines are typically used for workers, and the other two are used for shared telephones, such as the phone in a lobby or an analog line for fax or other analog device. The three line types can be provided at different price points, which would save the government money when ordering the lower feature set lines. In addition, including voicemail with the worker's lines would simplify ordering and billing. We request the Government consider pricing the IPVS basic service using three options: 1. IP Digital Seat (includes voicemail,) 2. IP Digital Seat, Userless (no voicemail,) 3. IP Analog Seat, Fax and analog phone (no voicemail)? In addition, if the government concurs that the three basic service configurations are proper, we request the Government consider removing the voicemail CLIN?

Answer:

The IPVS Basic service has been specified with an industry standard common feature set, without the voicemail feature. The Government does not intend to define additional variations of the IPVS Basic service nor bundle the voicemail with the service.

Question:

Table: Current industry practices require both setup and monthly maintenance of PS/ALI services. These services are typically provided by third party providers and are not part of the FCC mandated 911/E911 services to which carriers adhere. We request the Government consider adding either a fixed rate, or ICB rate, NRC CLIN to cover the one time setup charges that are incurred with PS/ALI services?

Answer:

The current PSAP charging units have both a NRC and an MRC and indicates that the vendor can have multiple bands using the same CLIN when pricing.

The defined IPVS NRC CLIN IV21420 should be used for the one time setup charge for the PS/ALI service.

Question:

Table: Bandwidth QOS (also known as IP Class of Service) is an IP transport concept using IP routing standards and protocols. In some cases, agencies will want to purchase transport from one vendor (e.g. use existing transport) and purchase SIP trunking from another vendor. Having the Bandwidth QOS tied to the SIP service as opposed to the IP transport will limit the agencies' ability to order the separate QOS function. We request the Government consider moving this priced element to the IP transport services (IP-VPN and IPS)?

Answer:

No. Bandwidth QoS Management is a required feature of the EIS SIP Trunk Service and is independent of other services such as VPNS or IPS.

Question:

Line AA00325.Also 2.1.2.2.2 Line EN00004, also 2.1.2.3.2 Line EN00038 to EN00046. Dedicated Ethernet 10 Gbps Access is optional. However, the 10 Gbps Ethernet E-Line port and associated Ethernet E-Line EVCs are not optional. The 10 Gbps Ethernet E-Line port and associated Ethernet E-Line EVCs require a Dedicated Ethernet 10 Gbps Access. Request that the Government make E-Line Ethernet Network Interface - 10 Gbps optional and the associated E-Line EVCs (2 Gbps thru 10 Gbps) optional so they correspond with the Dedicated Ethernet 10 Gbps Access requirement.

Answer:

E-LINE port CLIN EN00004 for E-LINE Ethernet Network Interface - 10 Gbps and associated E-LINE EVC CLINs (EN00038 to EN00046) 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 Dedicated Ethernet 10 Gbps access (CLINs AA00225 and AA00325) 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, #4.

Question:

Line EN20001 to EN20009. This Ethernet Transport Service requirement is for Bandwidth on Demand. A minimum commitment rate (e.g. 3 Mbps) to the Ethernet Transport Service Bandwidth on Demand port will limit customer options. The Agency customer may wish to scale below the minimum committed bandwidth and not pay for it. We request the Government replace the committed bandwidth ports (CLINS EN20001 to EN20009), and replace them with four Bandwidth on Demand port for 10 Mbps, 100 Mbps, 1 Gbps, and 10 Gbps. Make the 10 Gbps optional.

Answer:

E-LAN scalable CLINs EN20001 to EN20009 were setup as mandatory based on agency requirements. The government has taken the lower speeds into consideration prior to setting the committed limits.

Question:

Under B.3.2 NS/EP Basic Service Prices, the current EIS CLIN structure for TSP does not allow for unique TSP-E costs to be captured appropriately. We recommend GSA create a new CLIN specifically for TSP-E that may be used by the contractor to recover additional costs incurred for emergency service delivery, such as employee overtime, expedited permitting, counter-to-counter equipment shipments and other direct costs (ODCs).

Answer:

The items mentioned as TSP-E examples can be handled via labor CLINs or a TUC. Since the restoration of service is only for emergencies, a separate CLIN beyond those already defined is not necessary.

Question:

B.2.2.1.5.3 Para 3 and Table B.2.2.1.5.3. Managed LAN Pricing Instruction table is not mentioned in the B.2.2.1.5 section introduction. Managed LAN Service with Call Server & Maintenance - Premise Based (second CLIN) is not easily priced on a per seat basis. We recommend that this pricing be based on a "per component (ie, switch, router etc) and that the cost of the equipment and management of the equipment will be covered by the SRE charge. Will GSA please modify the RFP and make these change?

Answer:

The Government requires a per seat banded price for the Managed LAN premises-based solution, due to established market offerings and agency buying behavior/preferences.

Question:

Will the Government please describe the process by which vendors indicate that they are proposing ICB CLINs, especially optional ICB CLINs?

Answer:

The only ICB CLINs that may be proposed are catalog CLINs, which are mandatory if the service is being proposed. All other ICB CLINs are proposed at the task order level only.

Question:

Will the Government add Quantity to Table B.1.2.11.1? If not, how will bidders indicate that multiples of the auto-sold CLIN are required?

Answer:

For auto-sold relationships, the only required information are the CLINs that are Auto-Sold with the base CLIN, not the quantity. The intent of the table is to identify those CLINs that could show up automatically on a bill as a result of some other CLIN being ordered.

Question:

CLINs may be differentiated by Country/Jurisdiction ID, pairs of Country/Jurisdiction IDs or Bands. Will the Government modify Table B.1.2.11.1 to incorporate those differentiations and provide instructions on how to handle the fields if they don't apply to a specific CLIN? If not, how do vendors differentiate between Country/Jurisdiction IDs and Bands?

Answer:

The Auto Sold table is designed for capturing which CLINs are automatically sold with a base service. It is not to capture specific prices. The government does not see a need to vary what CLINs are auto sold based on band or country/jurisdiction.

Question:

High Availability Options is defined as load sharing, fail-over protection, and Diverse access points to service provider's POP(s), and is currently priced on a per port basis. Will the Government please explain how the "High Availability Options" and availability KPI relate, if they do? With multiple options, can GSA please make the price for "High Availability Options" ICB?

Answer:

The "High Availability Option" feature is unrelated to a KPI. This feature is added only if the customer has purchased diverse and/or redundant access arrangements connecting an SDP to a POP. It requires that the contractor actually make use of the special routing as intended by the customer, i.e., that they are actively distributing customer use across the access arrangements such that diversity is maintained as much as possible within the POP making a fail-over as seamless as possible.

Question:

Is it the Government's intent that vendors bid the optional features CNM - Level 1 and CNM - Level 2 (CLINS OW000301 and OW000302, respectively) only where a vendor indicates they have a Metro-Ethernet network serving a NSC in Table B.4.1.12? If not, please explain.

Answer:

This feature applies to any site served by the offeror using OWS where the customer requests CNM.

Question:

Section B.1.3.3 requires the contractor to provide support for end-of-life items at established prices until the government accepts an alternate solution. Offeror recommends the Government give contractors the opportunity to renegotiate prices for all support after end-of-life dates. Can GSA please provide an ICB CLIN for support after end-of-life?

Answer:

Contractors may create a new catalog item to represent the price for support after end-of-life for a catalog service or a service-specific TUC for a non-catalog service. For a catalog service, the contractor should be careful to adequately bound the support provided using the item description and the case description, since catalog items are available to all agencies.

Question:

Access is priced by Phub and can vary widely dependent on whether locations are on-net, near a carrier's POP, or if there's a significant amount of backhaul required. CLINs with embedded access also need to vary by Phub. This can be best done via a TUC table. Otherwise, bidders will have to factor in the risk of a CONUS-wide access rate which will yield a high rate, making the embedded access CLINs more expensive than acquiring the service and access separately. Please eliminate table B.2.1.1.3.3 and provide instructions on how to combine access with transport in the TUC table?

Answer:

Table B.2.1.1.3.3 will be used.

The purpose of providing the embedded access options for VPNS is for convenience to the customer. If this convenience comes at a higher cost, it is at the discretion of the customer whether there is value in purchasing the service in this manner. Note that the embedded access CLINs are optional to offer.

Alternatively, and as the question suggests, the offeror may, at the time of responding to a Task Order requirement, offer what is essentially embedded access by bundling access and VPNS port (transport) CLINs in a TUC.

Question:

The RFP provides for a single, worldwide price (i.e. no Country/Jurisdiction field) for Transport Diversity and Avoidance Routing feature CLINs while the prices of these features are dependent on originating and terminating PLS service locations. Could GSA change the type of Transport Diversity and Avoidance Routing feature CLINs to ICB?

Answer:

The PLS Transport Diversity and Avoidance Routing feature CLINs will not be changed to ICB. As stated in the Notes column of the PLS Feature Pricing Instructions Table B.2.1.4.2.2, each of these PLS Feature CLIN charges are in addition to the transport circuit prices that will apply for each circuit.

In the case of Transport Diversity features, the MRC is in addition to the transport circuit price that will apply to each transport circuit in each diverse relationship pair. Both the primary and diverse circuits are priced using the PLS prices.

In the case of Avoidance Routing, the MRC is in addition to the transport circuit price that will apply without avoidance routing. It applies only to the excess mileage incurred by the avoidance-routed circuit(s).

The PLS Diversity and Avoidance charges apply only to the PLS transport segments, that is from POP to POP. Diversity and Avoidance charges for the Access portions of circuits are ICB and priced in Table B.2.9.1.6 Access Diversity and Avoidance Prices Table.

Question:

The RFP provides for Branch-Off and Drop and Insert feature CLINs while these features are associated with outdated technologies not commonly employed in commercial practice. Could GSA change the type of Branch Off and Drop and Insert feature CLINs to Optional?

Answer:

The government still has significant locations with requirements for these services, so these will remain mandatory.

The offerors are encouraged to propose creative pricing and service offerings in newer services and technologies to help drive the trend towards the newer services and technologies.

Question:

Can GSA please change the charging unit for SONET FB Transport CLINs to Circuit and not on a per channel basis? 2.1.5.2.1.1, 2.1.5.2.1.2, 2.1.5.2.1.4

Answer:

The EIS RFP does not mention "SONET FB" and does not contain the referenced subsections (tables?). Please reconsider the question and resubmit if necessary.

Question:

All Services. Can the government please validate the NRC quantities against the corresponding MRC quantities? In many cases, the NRC quantities do not line up with the MRC quantities (e.g. CHS traffic model).

Answer:

The government confirms that the NRC quantities provided are as the government intended. In the traffic model, the quantity for a service initiation type of NRC CLIN matches the quantity of its corresponding MRC CLIN, but only when you look at all contract years in the aggregate. For example, MRC CLIN CH12003 exists in the traffic table with quantity=211 for each contract year. Rather than residing only in contract year 1 with a quantity of 211, the 211 units of NRC CLIN CH11003 are randomly distributed across five contract years. This approach, where the total NRC CLIN quantity is distributed across multiple contract years of the traffic table, is followed for similar NRC/MRC CLIN pairings.

Question:

Custom solutions are typically required for Contact Center Hosted and Premise Based pricing. Can GSA revise the requirement to make all Contact Center Hosted and Premise Based pricing, including Features, ICB?

Answer:

No the government will not revise Contact Center Hosted and Premise Based pricing, including Features, to ICB. The government understands that Contact Center Service is typically customized to agency requirements and has identified all such CLINs as ICB especially related to service initiation of the solution and to a great extent when it came to features. There are only a few non-ICB CLINs that the government feels did not need customization and can be priced accordingly.

Question:

Table B.2.3.2.3.2. Does GSA intend for respondents to price Call Answering Service as inclusive of all elements necessary to provide the Call Center or limited to the Labor Rates of the FTEs answering the phones?

Answer:

The government’s intent is for CCS Call Answering Service to be priced based on the individual requirements of the ordering agency. The service will be priced as ICB to allow for customization and special requirements. CCS Call Answering Service will be inclusive of all the requirements in Section C.2.3.1.4.3 and in Resources Table C.2.3.1.4.4 including but not limited to labor rates of the FTEs.

Question:

Please explain the relationship between the NRC CLINs and MRC CLINs. As an example, for the traffic data for the Full rack space NRC CLIN (CH11003) the total quantity equals the monthly amount as reflected in the Full rack space MRC CLIN (CH12003). Please clarify this relationship as it is repeated for other CLINs.

Answer:

In the traffic model, the quantity for a service initiation type of NRC CLIN matches the quantity of its corresponding MRC CLIN, but only when you look at all contract years in the aggregate. For example, MRC CLIN CH12003 exists in the traffic table with quantity=211 for each contract year. Rather than residing only in contract year 1 with a quantity of 211, the 211 units of NRC CLIN CH11003 are randomly distributed across five contract years. This approach, where the total NRC CLIN quantity is distributed across multiple contract years of the traffic table, is followed for similar NRC/MRC CLIN pairings.

Question:

For Dedicated burstable Internet bandwidth CLINs, why are there quantities in Year 1 for the MRC and no corresponding quantity on the NRC CLIN.

Answer:

In the traffic model, the quantity for a service initiation type of NRC CLIN matches the quantity of its corresponding MRC CLIN, but only when you look at all contract years in the aggregate. For example, MRC CLIN CH22003 exists in the traffic table with quantity=12 for each contract year. Rather than residing only in contract year 1 with a quantity of 12, the 12 units of NRC CLIN CH21003 are randomly distributed across the contract years, in this case, years 3, 4 and 5. This approach, where the total NRC CLIN quantity is distributed across multiple contract years of the traffic table, is followed for similar NRC/MRC CLIN pairings and is intentional.

Question:

Table B.2.8.1.3.3 Managed Network Implementation, Management and Maintenance Pricing Instructions Table for IP-MPLS Routing includes CLINs MN15003 & MN16003: Unified Communications Features - add on to Base Service. Please confirm these CLINs are correct for B.2.8.1 Managed Network Service and its definition.

Answer:

Yes, these optional CLINs are correct for B.2.8.1. They are available to the contractor as an optional mechanism for pricing the complexity of device management in addition to the base functions a device may have.

Question:

MNS Out-of-Band Access Pricing Table. POTS lines are location specific services. Will the GSA make MNS Out-of-Band Access service be ICB?

Answer:

No. Agencies prefer the current mechanism, which is being used today, therefore, MNS Out-of-Band services will remain as a fixed price.

Question:

Table B.4.2.1. Global Location lists the country: French Southern Territory, Country/Jurisdiction ID 120341. Can the GSA provide further location definition?

Answer:

According to the description by the U.S. Department of State, the French Southern Territory is comprised of Ile Amsterdam, Ile Saint-Paul, Iles Crozet, and Iles Kerguelen in the southern Indian Ocean; the "Iles Eparses" (Bassas da India, Europa Island, Glorioso Islands, Juan de Nova Island and Tromelin Island) in the Mozambique Channel and western Indian Ocean.

This information can be found on the U.S Department of State website: http://www.state.gov/s/inr/rls/10543.htm.

Question:

Table B.4.2.1. Global Location lists the country: Australian External Territory, Country/Jurisdiction ID 120309. Can the GSA provide further location definition?

Answer:

The Australian External Territory is comprised of Ashmore and Cartier Islands, Christmas Island, Cocos (Keeling) Islands, Coral Sea Islands, Australian Antarctic Territory, Territory of the Heard and McDonald Islands, and Norfolk Island. Some of these external territories have been defined as separate country/jurisdictions in Section B.4.2.1.

This information can be found on the Australian Government website: http://www.alrc.gov.au/publications/alrc-80-legal-risk-international-transaction s/10-external-territories and U.S. Department of State website: http://www.state.gov/s/inr/rls/10543.htm.

Question:

Table B.4.2.1. Global Location lists the country: British Indian Ocean Territories, Country/Jurisdiction ID 120313. Can the GSA provide further location definition?

Answer:

According to the description by the U.S. Department of State, the British Indian Ocean Territories is comprised of Chagos Archipelago (including Diego Garcia).

This information can be found on the U.S Department of State website: http://www.state.gov/s/inr/rls/10543.htm.

Question:

Pricing Tables: B.2.10.2.1; B.2.10.2; B.2.10.3.2; B.2.10.4.1; B.2.10.10.1. The traffic model and/or Section J does not define a minimum set of Service Related Equipment (SRE) for the proposal response. It will be roughly 12 months or more after the proposal is submitted that SREs could be ordered from the EIS contract. Over the next 12 or more months, SRE vendors may substantially change their catalog. Therefore, what is the minimum set of SRE entries that is required for proposal evaluation?

Answer:

If SRE is proposed, tables B.2.10.4.1 and B.2.10.10.1 must be fully populated by the offeror.

For the other SRE tables, no minimum number of SRE items is required. Section M.5 establishes the criteria for evaluation of catalog offerings. Moreover, section L.34.1 item 9 requires descriptive material from the offeror that addresses their catalog offerings. Items 9d and 9e specifically address the approach to catalog discount structures.

Discount classes are key to determining the pricing levels to be expected for a given type, manufacturer, or other logical grouping of items as selected by the offeror at the offeror's discretion. The government's evaluation of a catalog offering will consider all information provided by the offeror in response to the solicitation when evaluating a catalog offering.

Accordingly, catalog offerings must include sufficient information and items to enable the government to evaluate catalog offerings as described in M.5 and to enable the government to determine with sufficient confidence that the criteria in M.5 are satisfied.

Question:

Table B.2.9.1.5. Would GSA make the pricing for DS0 and ISDN BRI speeds Optional? DS0 and ISDN BRI are services no longer ordered by most customers. Continuing to require these services will slow down the move toward newer services and technologies.

Answer:

The government still has significant locations with requirements for these services, so these will remain mandatory.

The offerors are encouraged to propose creative pricing and service offerings in newer services and technologies to help drive the trend towards the newer services and technologies.

Question:

Table B.2.9.1.4. NonDomestic NSCs Access. Would GSA please add full address postal code and telephone numbers for all NonDomestic NSCs?

Answer:

The government will not provide any additional information on these NSCs. The information is limited to what iConectiv has provided.

Question:

Table B.2.9.1.5. Access Arrangements in Guam American Samoa Marianas Islands are custom solutions. Would GSA convert the Access Arrangement pricing requirements in Guam American Samoa Marianas Islands to ICB?

Answer:

The Access Arrangement pricing requirements in Guam, American Samoa, and Marianas Islands will not be converted to ICB. The government requires that prices be submitted so that there is a fixed price established for these existing requirements.

Question:

Unlimited data, and without bandwidth throttling, is no longer commercially available. Will the government please remove the requirement for unlimited data?

Answer:

No. Unlimited data is still a requirement for many government agencies. We understand that unlimited data without any throttling is no longer commercially available. However, within the government, unlimited data plans are still prevalent.

Per GSA research, FSSI-W was the first government-wide contract vehicle that had a strong selection of data limited plans, but many customers are still ordering unlimited data plans under that contract vehicle. The EIS program significantly increased the number of GBs that can be purchased under the data limited plans and included personal hotspots at no extra cost with these plans to further encourage the ordering of data limited plans, but unlimited plans are still a requirement.

Question:

Voice Service (B.2.2) allows contractors the option to price either IP or circuit switched voice or both. Will the government allow the TFS(B.2.2.3) IP termination and circuit switched (switched, dedicated) termination CLINs to be Optional to allow contractor to select the service type similar to Voice Service?

Answer:

Although TFS service as a whole is optional, the underlying technologies (switched, dedicated and IP) are all utilized heavily by the agencies and are therefore mandatory CLINs should the contractor choose to offer Toll Free Services.

Providing Voice Service (B.2.2) capability is a mandatory function under the RFP. Offerors are given the choice of providing the service via either IPVS or CSVS as mandatory and the other as optional as part of their overall solution.

Additionally, under Voice Service the contractor is given the option to price Toll Free Service (B.2.2.3) and Circuit Switched Data (B.2.2.4) as optional services.

Question:

Item 4.Would the government please remove Reservation-less CLINS AC21003 and AC21004 from the ACS Reservation Pricing table B.2.8.7.3.2? Reservation-less prices are captured in the ACS Basic Usage Price Table B.2.8.7.2.2.

Answer:

The requirements will remain as-is for Reservation-less CLINS AC21003 and AC21004.The "Reservation-less Automated Dial In (RADI)" CLINs -- (Toll Free - AC21003) and (Caller Paid - AC21004) -- are not included in the section "B.2.8.7.2 - ACS Basic Service Prices".

Question:

Out-of-Band POTS lines all have a charging unit of "Device" and a frequency equal to NRC. Since the CLIN includes the line, would GSA please revise the frequency to MRC?

Answer:

There are two sets of Out-of-Band POTS lines within table B.2.8.1.4.2, (CONUS and OCONUS). Each set already has both an NRC and an MRC CLIN.

Question:

Section B.1.2.11 states that as new capabilities and features are added to the contract for the services that have auto-sold CLINs (such as Audio, Web and Video Conferencing), contractors shall update (in this example) Table B.1.2.11.1. Within this context what is the definition of the "contract"? If an auto-sold CLIN is added to the contract, is the contractor automatically required to add the new auto-sold capabilities and features to all Services across all customers and all task orders? Does this automatically get added to the Billing to each customer? In the case where the parent CLIN of an auto-sold CLIN is a TUC, do only the existing parent CLINs within the Task Order receive the new auto-sold capabilities and features?

Answer:

Contract in this context refers to the EIS contract.. If an auto-sold CLIN is added to the contract via modification, the contractor shall work with each agency to either modify the task order to incorporate this contract change or update Table B.1.2.11.1 to indicate that the new auto-sold CLIN is disabled for the specific task order.

With regard to billing - an auto-sold CLIN is not billed unless the customer utilizes the CLIN. In addition, the CLIN is not billed nor usable by the customer if the auto-sold CLIN is disabled and the CLIN has not been ordered.

TUCs shall not be used for parent CLINs of an auto-sold CLIN.

Question:

Section 4.3 states that VPATs are required 30 days after NTP but VPATs are not listed in F.2.1 as CDRLs. Would the Government please clarify whether VPATs are a CDRL and if so, the associated CDRL details?

Answer:

Section C.4.2 does state "The contractor shall post the Voluntary Product Accessibility Template (VPAT) for each service identified in paragraphs C.4.4 below to its web site, in order to demonstrate that offerings comply with Section 508 standards. The VPAT is required 30 days after NTP and is updated as needed." VPAT is deliverable # 33 in Section F.

Question:

Paragraph 3. Does this mandate require that encrypted tunnels from the Offeror's federal customer portal need to be routed to an Einstein service provider?

Answer:

An offeror's federal customer portal is not a service offering under EIS. Per EIS RFP Section C.1.8.8, service offerings under EIS (VPNS, Ethernet Transport, IPS, Cloud, MTIPS or otherwise) transporting Internet, Extranet, and Inter-Agency traffic shall identify and route said government traffic through a secure DHS EINSTEIN Enclave.

Question:

Interfaces - UNI Type 2 for VPNS is PLS. Would the Government modify the requirement to direct Offerors to Access Arrangements, C.2.9.1.4?

Answer:

No. The Government has interface requirements expressed as UNIs and access arrangement requirements.

Question:

Interfaces - UNI Type 3 for VPNS is IP over SONET. Would the Government modify the requirement to direct Offerors to Access Arrangements, C.2.9.1.4?

Answer:

Question:

Interfaces - UNI Type 4 for VPNS is DSL Service. Would the Government modify the requirement to direct Offerors to Access Arrangements, C.2.9.1.4?

Answer:

Question:

Would the Government please remove satellite access as a requirement?

Answer:

No. The Government requires the flexibility to provide VPNS at remote locations.

Question:

Technical Capabilities -number 1. Since a Private Line is a point to point connection how does it require inspection defined in Section C.1.8.8? Generally private lines are between government facilities and not on the public network side nor cross over to the public side.

Answer:

There are instances of PLS circuits originating at agency locations and terminating at non-agency locations or otherwise meeting the conditions established in Section C.1.8.8. Circuits covered by a memorandum of agreement between the agency and DHS would be subject to being inspected at an EINSTEIN Enclave under a DHS task order.

Question:

Interfaces - UNI Type 3 for IPS is IP over SONET Service. Would the Government modify the requirement to direct Offerors to Access Arrangements, C.2.9.1.4?

Answer:

Question:

Interfaces - UNI Type 4 for IPS is Private Line Service. Would the Government modify the requirement to direct Offerors to Access Arrangements, C.2.9.1.4?

Answer:

Question:

Interfaces - UNI Type 5 for IPS is DSL Service. Would the Government modify the requirement to direct Offerors to Access Arrangements, C.2.9.1.4?

Answer:

Question:

Interfaces - UNI Type 6 for IPS is FTTP Service. Would the Government modify the requirement to direct Offerors to Access Arrangements, C.2.9.1.4?

Answer:

Question:

Standards 8 and 9 refer to future standards. Would the Government clarify that these requirements are applicable when commercially available?

Answer:

The Government understands that future services cannot be delivered until available. However, there may be circumstances when the Government requires technical service scenarios needed to meet mission requirements and those will be articulated in task order solicitations.

Question:

VPNS Capability #1. Please clarify "Ensuring any encrypted tunnels are applied and proxied to allow inspection If encryption is applied it generates cipher text as opposed to clear text. What is the requirement? Are the specific words ensuring any a mandatory requirement for encryption? And if so, what manner of encryption? FIPS-140-2 only? What do the specific words proxied to allow inspection mean? Based on C.1.8.8 this would only apply to Extranet VPNS connections whether secure or trusted, and with trusted there is no encryption. Is this correct?

Answer:

To clarify, the RFP VPNS requirement states: "1. The contractor shall meet applicable routing requirements in Section C.1.8.8 ensuring any encrypted tunnels are applied and proxied to allow inspection":

RFP Section C.1.8.8 states: "...service offerings under EIS (VPNS, Ethernet Transport, IPS, Cloud, MTIPS or otherwise) transporting Internet, Extranet, and Inter-Agency traffic to identify and route said government traffic through a secure DHS EINSTEIN Enclave for processing by the latest generation of EINSTEIN capabilities."

To allow inspection by DHS Einstein, if the traffic is encrypted (e.g, FIPS-140-2) by the offeror as part of its service, it needs to be de-encrypted (i.e., clear) before handing-over to DHS for processing within an Einstein enclave. Upon completion of DHS Einstein processing, the offeror would re-apply encryption to ensure service requirements are met as the offeror delivers the traffic to its final destination. The offeror is not expected (nor required) to be able to decrypt agency-applied encryption.

Question:

ETS Capability #1. Please clarify "Ensuring any encrypted tunnels are applied and proxied to allow inspection If encryption is applied it generates cipher text as opposed to clear text. What is the requirement? Are the specific words ensuring any a mandatory requirement for encryption? And if so, what manner of encryption? FIPS-140-2 only? What do the specific words proxied to allow inspection mean? Based on C.1.8.8 this would only apply to Extranet VPNS connections whether secure or trusted, and with trusted there is no encryption. Is this correct?

Answer:

RFP Section C.1.8.8 requires service offerings under EIS (VPNS, Ethernet Transport, IPS, Cloud, MTIPS or otherwise) transporting Internet, Extranet, and Inter-Agency traffic to identify and route said government traffic through a secure DHS EINSTEIN Enclave for processing by the latest generation of EINSTEIN capabilities. To allow inspection by DHS Einstein, if the traffic is encrypted (e.g, FIPS-140-2) by the offeror as part of its service, it needs to be de-encrypted (i.e., clear) before handing-over to DHS for processing within an Einstein enclave. Upon completion of DHS Einstein processing, the offeror would re-apply encryption to ensure service requirements are met as the offeror delivers the traffic to its final destination. The offeror is not expected (nor required) to be able to decrypt agency-applied encryption.

Question:

PLS Capability #1. Please clarify "Ensuring any encrypted tunnels are applied and proxied to allow inspection If encryption is applied it generates cipher text as opposed to clear text. What is the requirement? Are the specific words ensuring any a mandatory requirement for encryption? And if so, what manner of encryption? FIPS-140-2 only? What do the specific words proxied to allow inspection mean? Based on C.1.8.8 this would only apply to Extranet VPNS connections whether secure or trusted, and with trusted there is no encryption. Is this correct?

Answer:

The RFP Section C.1.8.8 requires service offerings under EIS (VPNS, Ethernet Transport, IPS, Cloud, MTIPS or otherwise) transporting Internet, Extranet, and Inter-Agency traffic to identify and route said government traffic through a secure DHS EINSTEIN Enclave for processing by the latest generation of EINSTEIN capabilities.