EIS_RFP_QTA0015THA3003_-_SF30_Amendment_0012_V2.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 #12

Revisions to the EIS RFP

This amendment includes the following:

· A note regarding the dismissed protest.

· Instructions for acknowledging the amendment.

· Changes to the RFP Sections.

· Questions regarding the amendment.

Most of the items in the amendment either relax existing RFP requirements or clarify existing RFP requirements; however, there are additional pricing requirements added in the amendment.

The revisions are listed based on the UCF Sections.

Dismissed Protest

Compuline International filed a pre-award protest at GAO against the terms of the EIS solicitation. The protest was dismissed by GAO on April 7, 2016.

Amendment Acknowledgement

Offerors that make the competitive range will be given instructions at a later date regarding how and when to acknowledge this amendment.

The RFP is amended as follows:

Section B

1. Table B.1.2.1.1 is amended to delete ‘n/a’ from the Mandatory/Optional (M/O) column and to replace the last note below the table with the following: ‘**** NS/EP is listed in this table and is not a service but rather a required set of mandatory CLINs. In the AcquServe portal, the contractor shall select National Security and Emergency Preparedness in the EIS Service Selection tool and shall price the required NS/EP CLINs from B.3.2.2.’

2. Section B.1.2.11, second paragraph, is amended to read as follows:

‘A comprehensive list of auto-sold CLINs (which may include catalog items) shall be incorporated into Table B.1.2.11.1. 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 Table B.1.2.11.1. Contractors shall populate Table B.1.2.11.1 with, at a minimum, the CLIN-to-Auto-sold CLIN relationships listed in reference table B.1.2.11.2 for:

3. The RFP is amended to add Table B.1.2.11.2 Auto-Sold Mandatory Relationships Reference Table. This reference table will support a new error checker rule that will enforce the inclusion of these 37 auto-sold relationships.

4. Section B.1.2.12 is amended to add the following sentence: ‘A combined TUC defined in Table B.1.2.12.1 shall be priced using the TUC price table of the transport service that is bundled into that combined TUC and shall not be priced using General TUC Prices Table B.4.1.14.1.’

5. Section B.1.2.15, second sentence, is amended to read as follows: ‘They allow pricing and ordering of such solutions without requiring a contract modification.’

6. Section B.1.3.1 is amended to add ‘for commercial items’ to the end of the second sentence in the first paragraph. Also, the first sentence in the third bullet from the bottom is changed to read: ‘If the OLP for a particular catalog item is not available, the item shall be considered non-commercial and the price charged shall be agreed upon between the government and the ordering agency at the time of TO award.’

7. Section B.2.1.2.3 is amended to delete the second paragraph.

8. Section B.2.1.3.2 is amended to add the haversine great-circle distance formula to OWS Transport.

9. Tables B.2.1.3.2.3 and B.2.1.3.2.4 are amended to add the word ‘Variable’ to the Price Per Mile column.

10. Table B.2.1.4.1.2 is amended to add the word ‘Variable’ to the Price Per Mile column.

11. Section B.2.1.4.2 is amended to add the haversine great-circle distance formula to PLS.

12. Table B.2.1.7.3.2 is amended to revise CLINs IP10070 and IP10080, and to add CLINs IP10071 and IP10081.

13. Section B.2.2.1.3 is replaced with the following:

‘Contractors shall use the formats specified in Table B.2.2.1.3.1 to provide off-net termination pricing to all OCONUS and non-domestic countries/jurisdictions specified in Table J.1.2.1.

Where the contractor provides voice service to a particular country/jurisdiction, the prices in Tables B.2.2.1.3.1, B.2.2.1.3.2 and B.2.2.1.3.3 cannot be higher than the prices resulting from applying the multiple usage increments applicable to that country/jurisdiction as provided in Table B.2.2.2.1.3. The originating country/jurisdiction is included in Table B.4.2.1.

The price table and instructions for non-domestic mobile terminations are provided in Section B.2.2.1.3.5.’

Off-net termination usage based pricing shall apply to IPVS with or without Managed LAN.’

14. Table B.2.2.1.3.1 is amended to change the title to: ‘IPVS CONUS to OCONUS and Non-Domestic Off-Net Termination Usage Prices Table.’

15. Previous Table B.2.2.1.3.2 is renumbered as Table B.2.2.1.3.4 and renamed as follows: ‘IPVS On-Net to Off-Net Termination Usage Pricing Instructions Table.’

16. Tables B.2.2.1.3.2 IPVS OCONUS or Non-Domestic to CONUS Off-Net Termination Usage Prices Table and B.2.2.1.3.3 IPVS OCONUS or Non-Domestic to OCONUS or Non-Domestic Off-Net Termination Usage Prices Table are added to the RFP.

17. Previous Section B.2.2.1.3.3 is renumbered as Section B.2.2.1.3.5. The paragraph is replaced with the following: ‘Contractors shall provide mobile termination pricing to all non-domestic countries/jurisdictions listed in Table J.1.2.1 except for satellite locations, which are the NONDOM locations in Table B.4.2.1 with no AOW ID. Table B.2.2.1.3.5.1 provides the formats for pricing information for IPVS non-domestic mobile termination add-on prices. Table B.2.2.1.3.5.2 provides applicable charging mechanisms and charging units for IPVS non-domestic mobile termination add-on prices.’

18. Previous Table B.2.2.1.3.3.1 is renumbered as Table B.2.2.1.3.5.1.

19. Previous Table B.2.2.1.3.3.2 is renumbered as Table B.2.2.1.3.5.2.

20. Section B.2.2.1.7 is amended to replace the existing language with the following:

‘Unlimited on-net to on-net and on-net to CONUS off-net calling shall be included with SIP Trunk Basic Service.

Contractors shall use the formats specified in Table B.2.2.1.7.1 to provide off-net termination pricing to all OCONUS and non-domestic countries/jurisdictions specified in Table J.1.2.1.

Where the contractor provides voice service to a particular country/jurisdiction, the prices in Tables B.2.2.1.7.1, B.2.2.1.7.2 and B.2.2.1.7.3 cannot be higher than the prices resulting from applying the multiple usage increments applicable to that country/jurisdiction as provided in Table B.2.2.2.1.3. The originating country/jurisdiction is included in Table B.4.2.1.

The price table and instructions for non-domestic mobile terminations are provided in Section B.2.2.1.3.5.’

21. Previous Table B.2.2.1.7.3 is renumbered as Table B.2.2.1.7.4 and renamed as follows:

‘SIP Trunk On-Net to Off-Net Usage-Based Pricing Instructions Table.’’ Furthermore, the description for CLIN VI33010 is amended to read: ‘SIP Trunk: On-Net to Off-Net Calling.’

22. Table B.2.2.1.7.3 SIP Trunk OCONUS or Non-Domestic On-Net to CONUS Off-Net Usage-Based Prices Table is added to the RFP.

23. Section B.2.2.2 is amended to replace the third paragraph with the following: ‘Usage charges for calls to non-domestic and OCONUS countries/jurisdictions shall be charged at the usage rates provided in Section B.2.2.2.1.1. Contractors shall use Table B.2.2.2.1.6 to 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.’

24. Section B.2.2.2.1.9 is amended to add the following sentence prior to the first sentence as follows: ‘Contractors shall provide mobile termination pricing to all non-domestic countries/jurisdictions listed in Table J.1.2.1 except for satellite locations, which are the NONDOM locations in Table B.4.2.1 with no AOW ID.’

25. Table B.2.3.2.1.2 is amended to rename the fifth column ‘Variable Price.’

26. Table B.2.3.2.2.2 is amended to rename the fifth column ‘Variable Price.’

27. Table B.2.5.2.1 is amended to change the footnotes associated with End of Sale Date and End of Life Date columns.

28. Section B.2.6 is amended to add the following paragraph prior to the last paragraph in the sub-section: ‘A contractor may prohibit unlimited data add-on or data only plans from being purchased for machine-to-machine (M2M) or similar types of applications (e.g., automated video feeds), or as a substitute for a private line or a dedicated data connection. In these cases, the customer may purchase a limited data add-on or data only plan or obtain an M2M plan.’

29. Table B.2.6.5.3 is amended to delete CLIN WL01000.

30. Table B.2.6.6.5 is amended to delete CLIN WL01200.

31. Table B.2.6.7.2 is amended to change the notes for CLINs WL02003 and WL02004.

32. Table B.2.7.2.4 is amended to change the descriptions for CLINs FS00000, FS00002 and FS00004, and change CLINs FS00002 and FS00004 from optional to mandatory.

33. Table B.2.8.1.4.1 is amended to add a Country/Jurisdiction ID column (and note) so that OCONUS CLINs in instruction Table B.2.8.1.4.2 can be priced by OCONUS jurisdiction.

34. Table B.2.8.2.2.1 is amended to rename the fifth column ‘Variable Price.’

35. Table B.2.8.2.2.2 is amended to add the word ‘subscriber’ to the charging unit column.

36. Section B.2.8.2.4 is amended to delete the following words from the end of the paragraph: ‘using the appropriate band from Table B.2.8.2.4.1.’

37. Table B.2.8.2.4.1 is amended to remove the Band Low and Band High columns (and the associated note), and to delete the word ‘Fixed’ from the third column.

38. Table B.2.8.2.4.2 is amended to add CLINs WC00102, WC00104, WC00112 and WC00114, and to change the descriptions for CLINs WC00100 and WC00110.

39. Table B.2.8.3.2.1 is amended to rename the sixth column ‘Variable Price.’

40. Table B.2.8.3.2.2 is amended to rename the seventh column ‘Variable Price.’

41. Table B.2.8.5.2.is amended to change the footnotes associated with End of Sale Date and End of Life Date columns.

42. Table B.2.8.6.2.2 is amended to add the word ‘Device’ to the description of CLIN MM01030.

43. Table B.2.9.1.5 is amended to change the note associated with CLINs AA00001 and AA00101.

44. The RFP is amended to add the following language below Table B.2.9.1.7:

‘Special Access Construction prices shall not be applicable if:

1. A domestic building NSC is mapped to a PHub ID in Table B.4.1.7 for which a price exists on contract in Table B.2.9.1.1, or

2. A non-domestic price exists for the NSC/CLIN combination in Table B.2.9.1.2 unless the contractor proves that sufficient capacity is not available solely for the Government.’

45. Table B.2.10.2.1.is amended to change the footnotes associated with End of Sale Date and End of Life Date columns, and add a footnote that states for each unique case number, the combination of Manufacturer+Model No.+Part No. must be unique.

46. Section B.2.11.5 is amended to add the following sentence: ‘Travel costs shall be priced in Table B.2.11.7.3.1 using a Service Related Labor TUC.’

47. Section B.2.11.6 is amended to add the following sentence: ‘Material costs shall be priced in Table B.2.11.7.3.1 using a Service Related Labor TUC.’

48. Table B.2.11.7.3.2 is amended to add CLIN LA99990 which shall be used to price travel and material costs.

49. Table B.2.12.1 is amended to add a Country/Jurisdiction ID column (and associated note) so that OCONUS CLINs in instruction Table B.2.12.2 can be priced by OCONUS jurisdiction.

50. Section B.4.1.14 is amended to replace the existing paragraph with the following:

Table B.4.1.14.1 provides the format for pricing TUCs for operational or administrative items (e.g., customized ordering, inventory or billing requirements, administrative customization) that are not readily associated with only one of the services defined in Table B.1.2.1.1. General TUCs shall not be used to price new services that are not listed in Table B.1.2.1.1. General TUCs shall be associated with and ancillary to the services in Table B.1.2.1.1, shall not be the primary purpose of a task order, and may only be ordered in conjunction with or in support of the purchase of services in Table B.1.2.1.1. Contractors may be required to provide additional information to support a determination that their proposed ancillary services are offered in support of one or more EIS CLINs. Table B.4.1.14.2 provides pricing instructions. TUCs shall be used as defined in Section B.1.2.15.

Section C

51. Section C.1.8.8 (3) is amended to change the third sentence from:

"As such, any service offering 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 for processing by the latest generation of EINSTEIN capabilities."

To: “As such, specific EIS data service offerings: VPNS, Ethernet Transport, PLS, IPS, Cloud services, which includes IaaS Private Cloud, Paas, and SaaS, MNS Traffic Aggregation Service, MTIPS, and IPSS, and in future implementations could include other externally routed data services(e.g. OWS, SONETS), transporting Internet, Extranet, and Inter-Agency traffic shall identify and route said government traffic through a secure DHS EINSTEIN Enclave for processing by the latest generation of EINSTEIN capabilities.”

52. Section C.2.1.1.1.2 (9) VPNS Standards is amended to change the RFC referenced in item 9 to reflect the most current standard and will now state: “9. Use of PE-PE GRE or RFC 4364 VPN.” The reference ‘IP in RFC2547 VPNs: draft-ietf-l3vpn-gre-ip-2547-00.txt’ is deleted.

Section E

53. Section E.2.1 is amended to add “In support of BSS testing, GSA will provide test parameters as follows: BSS test scenarios are provided in Section E.2.1.2. BSS test cases are provided in Section E.2.1.3. Test metadata (including approximate number of TOs, SOs, and other data sets to be used in testing) will be provided not later than NTP. System reference data, as described in Section J.2.3, will be provided not later than NTP. Test data, as described in Section E.2.1.3, and test verification criteria will be provided at the time of BSS testing.”

54. Section E.2.1 is further amended to add “The BSS testing will be performed during normal business hours, 8:00am-5:00pm Monday-Friday, Eastern Time.”

Section G:

55. Section G.2.3 is amended to add the following as the second sentence of the paragraph “For the purposes of this section (G.2.3), BSS validation testing does not include completion of Assessment and Authorization (A&A) as referenced in Section E.2.1.2.2, Test Scenario BSS-TS13.”

56. Section 4.6 is amended to add the due date for remitting the AGF to GSA.

57. Section G.8.2.1.1.1 is amended to change ‘Ethernet Service’ to ‘Ethernet Transport Service’ and change the acronym from ‘EthS’ to ‘ETS.’

58. Section G.8.2.1.1 to amended to change the last sentence in the first paragraph to: "The KPIs shall be measured and reported for each unique instance of a service which is defined at the most granular level to which the KPI is applicable but never at a level higher than that defined by the UBI service grouping (see Section J.2.10.1.1.2)." vs. “The KPIs shall be measured and reported for each unique instance of a service defined by the UBI."

59. Section G.8.2.2.1 is amended to insert the following at the end of the section: Note: For orders with non-CONUS delivery locations, these services have individual case basis (ICB) provisioning intervals and follow the requirements described in Section G.8.2.2.2 Individual Case Basis Provisioning SLAs.

60. Section G.8.2.2.2 is amended to delete the paragraph that reads “Note: for Ethernet Services, see also Section G.8.2.2.4.2 Bandwidth-on-Demand” and replace it with the following:

Notes:

1. For Ethernet Transport Services, see also Section G.8.2.2.4.2 Bandwidth-on-Demand

2. For Cloud Services; including IaaS, PaaS, SaaS, and CDNS; the ICB provisioning interval must be no greater than the provisioning interval proposed as specified in Section G.8.2.2.4

3. For any services proposed under rapid provisioning that also appear on this list, the ICB provisioning intervals must be no greater than the provisioning interval proposed as specified in Section G.8.2.2.4.

61. Section G.8.2.2.2.1 is amended to change ‘Ethernet Service’ to ‘Ethernet Transport Service’ and change the acronym from ‘EthS’ to ‘ETS.’

62. Section G.8.2.2.4.1, last sentence of the paragraph, is amended to read "If the contractor is proposing cloud services, they shall also propose the associated provisioning KPIs and SLAs." vs. “The contractor shall propose cloud provisioning interval KPIs and SLAs.”

63. Section G.8.2.2.4.2 is amended to change ‘Ethernet Service’ to ‘Ethernet Transport Service.’

64. Section G.8.2.2.4.3 is amended to say “Consistent with the requirements in Section G.3.3.3.2 Rapid Provisioning Orders, if the contractor is proposing specific services for rapid provisioning, they shall also propose associated KPIs and SLAs." vs. “Consistent with the requirements in Section G.3.3.3.2 Rapid Provisioning Orders, the contractor shall propose specific services for rapid provisioning with associated KPIs and SLAs.”

Section J

65. Table J.1.1.1 is amended to add the word ‘Port’ to the header in the third column.

66. Section J.1.2, last paragraph, is amended to read as follows: ‘Non-domestic service is not required except as defined below. Table J.1.2.1 shows countries/jurisdictions where the contractor is required to support OCONUS and non-domestic off-net voice terminations for Internet Protocol Voice Service (IPVS), Circuit Switched Voice Service (CSVS) and Wireless Service (MWS). The contractor is also required to support IPVS and CSVS mobile terminations in the non-domestic countries/jurisdictions listed in Table J.1.2.1 except for satellite locations, which are the NONDOM locations in Table B.4.2.1 with no AOW ID.’

67. The title to Table J.1.2.1 is amended to read as follows: ‘OCONUS and Non-Domestic Countries/Jurisdictions Supporting Off-Net Voice Terminations and Non-Domestic Countries/Jurisdictions Supporting Mobile Voice Terminations Table’

68. Section J.1.3.1.1 is amended to insert a new Item 2 as follows: ‘2. All NSCs within a proposed OCONUS region that are not within any CBSAs, i.e., NSCs where CBSA=1 in the Traffic Model.’

69. Section J.1.3.2.1 is amended to replace the first paragraph with the following: ‘The contractor shall price mandatory access CLINs in the Traffic Model for non-domestic NSCs. Post-award, contractors shall price access as required by the underlying transport requested.’

70. Section J.2.1 is amended to add the following sentence at the end of the first paragraph: “It also includes requirements for contractor interaction with the set of tools used by GSA to manage the contract and TOs issued under the contract (GSA Systems).”

71. Section J.2.3.3.1 is amended to insert four additional rows with the following content:

· Data Set: KPI AQL Operator o Frequency: As required o Transfer Mechanism: Secure FTP

· Data Set: KPI Location Qualifier o Frequency: As required o Transfer Mechanism: Secure FTP

· Data Set: KPI Measurement Unit o Frequency: As required o Transfer Mechanism: Secure FTP

· Data Set: KPI Service Level Qualifier o Frequency: As required o Transfer Mechanism: Secure FTP

72. Section J.2.4.1.5(1) is amended to read “as required in Section J.2.4.3.2” vs “as required in Section J.2.3.3.3.”

73. Section J.2.5.1.5.1 is amended to replace all current text with the following:

The contractor shall support the following proration types:

· Month-Length Proration, defined in Section J.2.5.1.5.1.1

· Normalized 30-Day Month Proration, defined in Section J.2.5.1.5.1.2 Customers select the proration type in their TO. If the TO does not specify a proration type, the contractor shall implement Month-Length Proration. The contractor shall implement and use the selected proration type for each TO at no cost to the government.

The RFP is amended to insert a new section at J.2.5.1.5.1.1 entitled “Month-Length Proration” with the following text:

1. Calculate the Daily Charge: divide the Monthly Recurring Charge (MRC) by the number of days in the billing month to get the Daily Charge [Daily Charge] = MRC / [Days in Month]

2. Find the First Billable Day

a. If the service and pricing to be prorated were in effect on the first day of the billing month, the First Billable Day is 1

b. Otherwise, the First Billable Day is the day the service was installed or the day of the new pricing start (see Section J.2.5.1.5.2)

3. Find the Last Billable Day

a. If the service and pricing to be prorated are in effect on the last day of the billing month, the Last Billable Day is equal to the number of days in the billing month

b. Otherwise, the Last Billable Day is the day the service was disconnected or the day of the pricing end (see Section J.2.5.1.5.2)

4. Calculate the Billable Days: the number of billable days for the service and pricing to be prorated is equal to the Last Billable Day minus the First Billable Day plus 1 [Billable Days] = [Last Billable Day] – [First Billable Day] + 1

a. Example 1: New service installed on March 17th [Billable Days] = 31 [Last Billable Day] – 17 [First Billable Day] +1 = 15

b. Example 2: Service disconnected on June 10th:

[Billable Days] = 10 [Last Billable Day] – 1 [First Billable Day] + 1 = 10

c. Example 3: Service installed May 3rd and disconnected May 27th [Billable Days] = 27 [Last Billable Day] – 3 [First Billable Day] + 1 = 25

5. The billable amount for the service in that month is equal to the daily charge from step 1 multiplied by the billable days from step 2:

[Billable Amount] = [Daily Charge] x [Billable Days]

74. The RFP is amended to insert a new section at J.2.5.1.5.1.2 entitled “Normalized 30-Day Month Proration” with the following text:

1. Calculate the Daily Charge: divide the Monthly Recurring Charge (MRC) by 30 to get the Daily Charge [Daily Charge] = MRC / 30

2. Find the First Billable Day

a. If the service and pricing to be prorated were in effect on the first day of the billing month, the First Billable Day is 1

b. Otherwise, the First Billable Day is the day the service was installed or the day of the new pricing start (see Section J.2.5.1.5.2)

3. Find the Last Billable Day

a. If the service and pricing to be prorated are in effect on the last day of the billing month, the Last Billable Day is equal to the number of days in the billing month

b. Otherwise, the Last Billable Day is the day the service was disconnected or the day of the pricing end (see Section J.2.5.1.5.2)

4. Calculate the Billable Days: the number of billable days for the service and pricing to be prorated is equal to the Last Billable Day minus the First Billable Day plus 1 [Billable Days] = [Last Billable Day] – [First Billable Day] + 1

a. Example 1: New service installed on March 17th [Billable Days] = 31 [Last Billable Day] – 17 [First Billable Day] +1 = 15

b. Example 2: Service disconnected on June 10th:

[Billable Days] = 10 [Last Billable Day] – 1 [First Billable Day] + 1 = 10

c. Example 3: Service installed May 3rd and disconnected May 27th [Billable Days] = 27 [Last Billable Day] – 3 [First Billable Day] + 1 = 25

5. Note: If Billable Days from Step 2 is equal to or greater than 30, proration does not apply; the contractor shall bill the full MRC for that month.

6. The billable amount for the service in that month is equal to the daily charge from step 1 multiplied by the billable days from step 2:

[Billable Amount] = [Daily Charge] x [Billable Days]

74. Section J.2.5.1.9 is amended to clarify the definitions for Billing Invoice and Billing Adjustment deliverables. Specifically, the changes include:

75. Section J.2.10.1.1.2.2(1) is amended to read “The contractor shall create and assign the UBI for each installed service instance in compliance with the UBI Specifications described above, even if there is only one member of the service grouping.” vs. “The contractor shall create and assign the UBI for each service grouping in compliance with the UBI Specifications described above, even if there is only one member of the group.”

76. In addition, Section J.2.10.1.1.2.2(1) is amended to add the following bullets under the item:

· Installed Service Instance Definition: a unique installation of a particular CLIN (or CLIN + ICB Case Number combination, if applicable)

· For SRE, the UBI is assigned as above with each associated SRE Pricing Element using the same UBI (see also Section B.2.10)

77. Section J.2.10.2.3.3, second sentence is amended to read: "The table shall include a separate line for each performance period covered by the TO." vs. “The table shall include a separate line for each fiscal year covered by the TO."

78. Section J.2.10.2.3.3 is amended to insert an additional row with the following content:

· Element Name: proration_type

· Element Description: The type of proration to be used on the TO. Valid values are "Month-Length" and "Normalized" (see also Section J.2.5.1.5.1)

79. Section J.2.10.3.1.1, third bullet, second sub-bullet (Alphanumeric) is amended to read "Alphanumeric: Characters on the standard 104-key US qwerty keyboard excluding the pipe, ‘|’, character" vs. "Alphanumeric: Characters in the standard English alphabet (A-Z and a-z) or numbers (0-9) or standard symbols and punctuation excluding the pipe, ‘|’, character"

80. Section J.2.10.3.1.2 is amended to change the description of Element Name “sla_item_identification” to read “This is used to identify the missed SLA in the SLA credit request and any resulting disputes and/or billing adjustments” vs. “This is used to link a missed SLA to a billing adjustment”

81. Section J.2.10.3.2.1, fourth bullet, second sub-bullet (Alphanumeric) is amended to read "Alphanumeric: Characters on the standard 104-key US qwerty keyboard excluding the pipe, ‘|’, character" vs. "Alphanumeric: Characters in the standard English alphabet (A-Z and a-z) or numbers (0-9) or standard symbols and punctuation excluding the pipe, ‘|’, character"

82. Section J.3 DPA is amended as follows:

The following sentence has been added to paragraph 1 (Compliance): “Reporting requirements are not applicable to agencies exempt from public posting.”

The last sentence in the Fair Opportunity paragraph has been amended to change the dollar threshold from $3000 to $3500.

83. Section J.4 Appendix C Overview, second to last paragraph, is replaced with the following paragraph: ‘A successful contract modification submission will become a contract modification after the contracting officer’s approval. At time of submission, the contractor will assign each submission a submission number in accordance with the “Submission Numbering Scheme” defined in Appendix A. Submissions that include more than one service may be delayed. The contractor shall submit modification submissions, TO-specific submissions, and catalog submissions separately.’

84. Section J.12 is amended to change the definition of ‘service’ to: ‘The term “Service” refers to the primary unit of EIS technical and pricing requirements. It includes all components and functions provided by the contractor to deliver a specific service, including the contractor's network, contractor-provided access arrangements and service related equipment. Individual services are grouped into “Service Types.” Also see “Service Types”’

85. Section J.12 is amended to update the definitions of GSA Conexus and GSA Systems as follows:

· For GSA Conexus, add the sentence “This system is distinct from GSA Systems.”

· For GSA Systems, add the sentence “These systems are distinct from GSA Conexus.”

86. Attachment J.19 Vol 1b Line 854 is amended to add Item 11, ACS Operator Dial Out, which was inadvertently omitted and is inserted into the list of ACS features to be consistent with RFP Section C.2.8.7.2. The subsequent items in the ACS features list (12-15) will be renumbered and a typo corrected to be consistent with RFP Section 2.8.7.2. With these changes, Attachment J.19 vol 1b will now read starting with line 854 as follows:

Section L

87. Section L.9 is amended to add the following sentence: “If the assumption or condition simply restates or agrees with the terms and conditions of the RFP, the Government may waive the requirement for the offeror to provide a detailed resolution.”

88. Section L.10 is amended to update the Contract Specialist and contact information from A. Michelle White to Dinaira M. Borba.

89. The first sentence in Section L.27.2 Number 1 is amended to read as follows: “Microsoft Word 2007 or newer, standard letter size 8.5 x 11 inches, one (1) inch margins and font type Arial with a size standard of no smaller than 12 pt in narrative and not less than Arial 8 pt font in tables. (Font size does not apply to company logos, cover page, table of contents, assumptions and conditions, abbreviations and acronyms table, legends, footers and headers, section titles, and figures).”

90. The last sentence in Section L.27.2 Number 1 is amended as follows: “No other file formats shall be accepted with the following exceptions: PDFs for the signed SF30s, the SF33 as required by Section L.25, copies of the CPARs/eSRS reports as required by Section L.33.2 Subcontracting History, signed CTAs/SBTAs, and the SB Template. PDF files do not need to be in the format specified above for Word. “

91. Section L.27.2 Number 2, letter G is amended to change the numbering format.

92. Section L.27.2 Item 3 (a) (iii) is amended to add the following sentence. “Margin restrictions do not apply to cover pages, SF30s and the SF33, government templates, CTAs/SBTAs, CPARS and eSRS reports, and figures.

Section L.27.2 Item 3(b) is amended to read “Font- see font restrictions in item 1 above.”

Section L.27.2 Item 3(c) is amended to add the following sentence: “Line spacing does not apply to cover pages, the SF33, SF30s, government templates, CTAs/SBTAs, CPARs/eSRS reports, and figures.”

Section L.27.3 is amended to add a sentence after the first sentence: “See Section L.34 for specific submission requirements for the Price Volume.”

93. Section L.29.2.4 is amended to reflect how data requested in Attachment J.19 Vol 1, 1a, and 1b shall be provided. The entire section is replaced with the following: “The offeror shall populate and identify the exact sections in the offeror’s proposal that address each of the proposed services by completing its proposal input in AcquServe, using the EIS Submission Matrix tool. This will be the process for the offeror to provide information requested in Vol 1, Vol 1a and Vol 1b in the EIS Submission Matrix workbook (see Attachment J.19).”

Section L.33.1 number 1 is amended to replace the existing language with the following: “Demonstrate compliance with requirements of FAR Clause 52.219-9, FAR Subpart 19.704, and GSAM Provisions 552.219-72 and 552.219-73.”

Section L.33.2 is amended to require offeror’s to provide the five most recent PPIRS/CPARs reports associated with meeting small business subcontracting goals.

Section L.34 is amended to change the first paragraph to read as follows: “The offeror shall prepare its Price Volume to address all applicable requirements specified in Section B Pricing. All information regarding prices for the proposed services shall be included in this volume. The offeror shall enter its prices in the format of the price tables defined in Section B into the AcquServe price database in accordance with the instructions found in the AcquServe system. No price elements other than those defined in Section B are permitted. Prices will only be evaluated if they are submitted into the AcquServe price database.“ Section L.34 number 2 is amended to add “submitted into the AcquServe price database.”

94. Section L.34.1 number 5 is amended to read: For its geographic coverage strategy, if the offeror has not selected and proposed all CONUS and OCONUS CBSAs via AcquServe, the offeror shall:

a) Explain why the included CBSAs have been selected and proposed for the offeror’s proposal

b) Explain why the excluded CBSAs have not been selected or proposed for this proposal

c) Section L.34.2 is amended to add “into the AcquServe price database” to the first sentence.

95. Section L.34.2 is amended to add “into the AcquServe price database” to the first sentence.

Section L.34.2, second paragraph is amended to read: “For each CBSA the offeror proposes, the offeror shall provide all information necessary to price mandatory traffic and mandatory CLINs as required in Section B and Section J.1. To be considered for evaluation, offerors shall submit prices for the mandatory services and access arrangements in at least 25 of the top 100 CBSAs. If an offeror proposes an optional service, the offeror shall provide all information necessary to price the traffic and mandatory CLINs for that optional service, as required in Section B and Section J.1. Price tables and other pricing information shall be submitted into the AcquServe price database using the AcquServe portal. The AcquServe portal is a secure website that contains detailed instructions for the submission of prices and pricing information for which access permission must be obtained (see Section L.27.3). The offeror shall populate Contractor-Maintained tables (see Section B.1.2.17.1) in the AcquServe price database only by using the AcquServe Table Viewer as described in Section 6.2 of the AcquServe User Instructions for EIS Proposal Submissions, which is available from the Help menu of the AcquServe portal.”

Section L.34.2 after the second paragraph starting at “As part of completing its submission:” is amended to:

1. For mandatory services, the offeror shall use Step 1: Choose Mandatory Service CBSAs, of the AcquServe EIS Service Selection tool to identify the CBSAs for which the offeror is proposing pricing.

2. The offeror shall use Step 2: Choose Voice Services for Mandatory CBSAs, of the AcquServe EIS Service Selection tool to identify which Voice Service (CSVS or IPVS) it is proposing as the mandatory service for each CBSA. The AcquServe tool allows selection of all CBSAs or individual CBSAs. The other Voice Service may be offered as an optional service.

3. The offeror shall use Step 3: Choose Optional Services, of the AcquServe EIS Service Selection tool to identify optional services for which the offeror is proposing pricing.

4. For optional CBSA-dependent service pricing, the offeror shall use Step 4: Choose Optional Service CBSAs, of the AcquServe EIS Service Selection tool to identify the CBSAs the offeror is proposing. The CBSAs for the optional CBSA-dependent services shall be selected from those proposed for the mandatory services.

5. For mandatory or optional location-dependent service coverage in non-domestic and OCONUS countries/jurisdictions, the offeror shall use Step 5: Choose NONDOM and OCONUS Regions, of the AcquServe EIS Service Selection tool to identify any such locations in which an offeror is proposing prices. The offeror shall also complete the appropriate Section B tables.

a. If the offeror selects an OCONUS CBSA in Step 1 for mandatory services, the offeror shall select the corresponding OCONUS region in Step 5 for each of the mandatory services and access arrangements.

b. If the offeror selects an OCONUS CBSA in Step 4 for an optional service, the offeror shall select the corresponding OCONUS region in Step 5 for that optional service.

c. For mandatory services and access arrangements, if the offeror selects an OCONUS region in Step 5 that has CBSAs (i.e., Alaska, Hawaii, or Puerto Rico), the offeror shall select at least one CBSA in that OCONUS region in Step 1.

d. For an optional service, if the offeror selects an OCONUS region in Step 5 that has CBSAs (i.e., Alaska, Hawaii, or Puerto Rico), the offeror shall select at least one CBSA in that OCONUS region for that service in Step 4.

e. The offeror shall not use Step 5 to identify OCONUS or non-domestic regions needed to satisfy the requirements of J.1.2.1, as the AcquServe portal already knows what regions must be priced to satisfy J.1.2.1. For IPVS, CSVS and MWS, the offeror shall use Step 5 to identify only those OCONUS or non-domestic regions where the non-J.1.2.1 requirements of the service are provided for.

6. If offering optional CLINs within a mandatory or optional service, the offeror shall complete the appropriate Section B tables for the optional CLINs.

7. The offeror shall populate Table B.4.1.4 Services Offered by Point of Presence, to indicate where both mandatory and optional services are provided.

8. The offeror shall complete and submit all cross-reference tables defined in Section B. Most of these tables are found in Section B.4.

Section L.35 number 1 is amended as follows: “The offeror shall execute the AcquServe Error Checker prior to final submission of the offeror’s proposal. The Error Checker reports will be submitted automatically. The AcquServe Error Checker exists to assist the offeror in preparing a complete and accurate proposal but it is not exhaustive and its use does not absolve the offeror of its responsibility to submit a complete and accurate proposal.”

Section M

Section M.2.3 is amended to update the numbering sequence from 1 and 1, to 1 and 2.

Section M.2.4 number 1(a), is amended replaced with the following: “Compliance (Acceptable/Unacceptable) The offeror’s subcontracting plan complies with the requirements of FAR Clause 52.219-9, FAR Subpart 19.704, and GSAM Provisions 552.219-72 and 552.219-73.”

Section M is amended to add Provision M.6 as follows:

M.6 Evaluation of Option Year Pricing

In accordance with FAR Subpart 17.206(a), the government is required to evaluate offers for any option periods contained in a solicitation when it has been determined prior to soliciting offers that the government is likely to exercise the options. In order to comply with this requirement, the government will calculate option period pricing by applying a price escalation factor to each offeror’s base period pricing. Prices will be calculated for option periods 1 and 2, and the potential six month option included in Clause 52.217-8 Option to Extend Services. The escalation factor will be applied to all mandatory and optional services prices and will be the same for all offerors. The option period prices calculated by the government will only be used for evaluation purposes. Actual pricing (i.e., post award) for the option periods will be done in accordance with Clause H.19.”

Submission of Questions Regarding the Amendment

1. All questions regarding this amendment must be submitted via the AcquServe repository. The “Instructions for Gaining Access to AcquServe” are included in Section J.16 of the RFP. Section J.17 of the RFP includes “AcquServe User Instructions for EIS RFP.”

2. Answers to questions will be posted only on AcquServe. Questions that were previously asked prior to receipt of proposals will not be answered. Questions that do not pertain to the changes in the amendment will not be answered.