alltechnicalresponses3_10_08.rtf

Solicitation Number: RTAS-RFP-08002 March 10, 2008 Questions and Responses

QUESTIONS AND RESPONSES

Regional Telecommunications Acquisition Services (RTAS) RFP

1. Question: We respectfully ask the Government to extend the due date of this RFP response from March 14, to April 25, 2008, an additional six weeks. This time is needed to allow offerors sufficient time to receive answers from the GSA to all industry questions, and to prepare complete responses for submission of a compliant response.

Response: The RFP due date has been extended to 04/16/2008.

SECTION B

B.1.2 Pricing of Orders Paragraph two states the Government requires that mandatory federal, state, and local taxes be identified separately from the base price of the service. It goes on to say that, “Offerors shall use the jurisdictional rates in existence at the time of proposal submission for all years of the contract.” Mandatory federal, state, and local taxes from which the federal Government is not exempt, may be charged; however, they must be identified as firm fixed rates for the duration (eight years) of the contract. These said mandatory federal, state, and local taxes are charges beyond the control of the Offeror and vary by quarter and/or year.

2. Question: Will the Government reconfirm that it is its intent to have the Offeror “fix” these charges at current rates for the duration of the contract – whether or not the charges fluctuate and that fluctuation may be to the benefit of the Government (taxes are lowered or removed during course of contract)?

Response: This is a FFP contract, prices provided shall remain fixed throughout the contract length, prices can increase option year to year, and decreases can be made at any time.

B.1.2; C.1.1.1; C.8.2; H.9; L.31.5; Pricing Sheets

3. Question: The Government has defined the terms of this contract as having a four year base with four one-year options and also as a contract term of five years. Will the Government please define the Government’s performance period and update the solicitation as needed?

Response: This is a 4 year contract with four 1 year options. References have been corrected.

B.1.3.1 4)a NPA/NXX Groups. (Numbering scheme is unclear)

4. Question: Will the Government please provide further direction on pricing sensitivity? The Pricing workbook accommodates for NPA to NPA, yet the directions in B.1.3.1 4 provide direction to price by NPA/NXX. Note: Industry practice is to price by NPA/NXX. The Offeror requests authority to modify workbook to accommodate for NPA/NXX pricing (By Zones/Access Areas).

Response: Is this response going to be limited by tariff or will thinking outside of the box be a standard to go by. We prefer NPA/NPA, we prefer point to point service without segmented phases of service each priced differently. Provide pricing both ways, if possible.

B.1.3.2 Price Elements, Usage Charge

5. Question: Item #5 states that, “Pricing shall be provided in six second increments reflected in the Pricing Tables.” Would the Government entertain an Offeror proposing a different usage increment if it was to the benefit of the Government, i.e., per second increment?

Response: Yes, we encourage alternative pricing on all items within this RFP.

B.1.4 Instructions for Pricing The second paragraph states that, “…the Offeror may not propose any additional price elements not included in the formatted structure.” However, in B.5, Optional Services Proposed by Offeror, the Government states, “…Offeror may propose optional services for inclusion in the RTAS contract and provide pricing….” There seems to be some contradictions within the RFP scope regarding additional products/services not identified in the RFP. B.1.3 and B.5 allow optional products. B.1.4, B.5, and L.31.4 do not allow optional products.

6. Question: Can we put additional products on the pricing worksheets?

Response: Yes, additional products can be added but unless the Government sees value in them they will or will not be assigned CLIN’s.

7. Question: Will the Government provide further explanation of what is not allowed and/or define “price elements”?

Response: The price elements are the charges developed for each CLIN (SIC and MRC). The SIC and MRC would be the raw rate of the service, the tax portion will include all taxes, surcharges and fees associated with the SIC or MRC and the Total Inclusive Price is the total of those two amounts.

B.1.6 Organization of this Section There is no reference to Broadcast Access Services (BAS) in this section.

8. Question: Will the Government include this service?

Response: Check section and add reference required.

B.1.6.1-8 Organization of this Section There are no examples of service types shown for Broadcast Access Service (BAS) or for SONET Ring Service (SRS).

9. Question: Will examples of these service types be provided?

Response: Reference B.1.6.1-8, these are CLIN examples, BAS and SRS will not be added.

B.1.6.1.1. Voice Services (VS) The analog line and ISDN BRI lines, as shown, are to terminate at SDP3 and include voice mail / 6-way conferencing as a feature.

10. Question: Will the Government confirm that it is its intent that ALL analog lines and ISDN BRI lines will be ordered to SDP3 and should include all relevant charges for delivery to this service point?

Response: Yes the majority of services will be ordered to SDP3 (analog line and ISDN BRI, etc.) the SIC shall include all cross connects required to deliver service to the SDP.

B.2 Organization of Pricing Columns – Pricing Tables This section describes the pricing columns for each pricing table.

11. Question: Will the Government provide pricing column descriptions and Pricing Tables for the Broadcast Access Service (BAS) and SONET Ring Service (SRS) sections that are missing in this section?

Response: Yes, we will provide the required information.

B.2.1.1 and throughout the solicitation The Government begins referring to the term NETPOP in Section B.2.1.1 and then continues to reference NETPOP throughout this solicitation. However, on the existing MAA contracts, the Government referred to the NID.

12. Question: Will the Government please provide the Government’s definition of NETPOP?

Response: The definition has been added. The Network Point of Presence (NETPOP) and the Network Interface Device (NID) are the same.

13. Question: Will the Government please detail if and how the NETPOP may differ from the NID as detailed on other MAA/RLSC contracts?

Response: The Network Point of Presence (NETPOP) and the Network Interface Device (NID) are the same.

B.2.1.2 Recurring Line Charge Column Within the second paragraph the requirement states, “…reflect applicable prices for access connections that terminate at the Network Point of Presence (NETPOP) of the building.”

14. Question: Will the Government further define NETPOP? This term is not shown in the Glossary of Terms. Will the Government further define NETPOP in relation to the GSA’s Type I and Type II building format? And, will the Government provide surveys of each agency’s delivery point in order for the Offeror to develop appropriate pricing?

Response: The term will be added to the Glossary of Terms. The NETPOP is the vendor/customer interface, usually located within a reasonable distance from the entrance of vendor facilities into a building. In some cases the NETPOP can be extended beyond the entrance to an agreed upon location (between vendor and customer) within the building. No the Government will not provide surveys. The vendor will be given all information available, it will be required that the vendor work with the incumbent vendor to verify deliver point information. GSA will provide a Letter of Agency to assist with the gathering of this required information. The vendor will deliver service to the SDP requested.

SECTION C

C.1.1.1 The Government asks offerors to provide a stable platform for users to migrate to Networx Universal and Networx Enterprise.

15. Question: Will the Government please provide specifics for what the Government means by “a stable platform” as referenced in C.1.1.1?

Response: A platform capable of providing access to all long distance vendors awarded a Networx’s contract. Also, sufficient access to those carriers to allow for unblocked service.

C.1.1.2; C.3.3.5.3.7; and M.2.3 3:

State no loss of service functionality or disruption of service as they transition from the MAAs and RLSC to RTAS.

16. Question: A step by step process must be provided by the Government to all offerors for the RTAS opportunity to explain how this will be accomplished, particularly when moving from one network/infrastructure to another.

Response: The vendor should have the experience to accomplish this transition of services with a minimal of downtime. We will change to reflect minimal disruption of service.

C.1.3.2.1 Geographic Boundaries This section defines the six state footprint of IL, IN, MI, MN, OH and WI, but does not have any exclusion.

17. Question: Will the Government please detail its plans for incorporating or excluding the recently awarded contract in Chicago and the active solicitation in Cincinnati?

Response: The RTAS solicitation covers all Regional locations, the services in Chicago and Cincinnati will be re evaluated after RTAS is awarded to determine the best price for the service required.

C.1.3.3.1 States that there are three mandatory voice services to be eligible for an RTAS award. However, in C.1.3.3.1.2, a fourth service group is identified (CSDS). L.31.3.1, references IAS as an optional service.

18. Question: Will the Government please clarify what product categories are mandatory?

Response: L.34.4 reference to optional service for IAS removed.

C.2.1.2.1 The Government details that all inside wiring for all orders will be part of the basic service up to the required SDP. However in C.3.3.4 and in the Pricing Workbooks, labor rates are identified for cable installation and cable pricing.

19. Question: In order for Offerors to provide the most competitive basic service MRC, the Government must provide, specifically, what cabling is to be included as part of the basic service up to the required SDP. Additionally, clarify when the labor rates to be provided in response to Section C.3.3.4 and in the Pricing Tables will apply.

Response: A table defining the SDP and the responsibilities of the vendors has been included (See Attachment J-4, RTAS SDP Requirements). The SIC includes pricing to the required SDP, this will include any cross connects from the NETPOP to the riser, the cross connect at the IDF and the test for dial tone at the instrument. If the cable/wire required for that connection does not meet industry standards the vendor will alert GSA and the labor rates will then apply to correct the problem. GSA has the right to use any vendor for the correction of the identified problem.

C.2.1.2.2 The Government asks offerors to “…demonstrate, with appropriate engineering specifications and evidence, that the connection is unsatisfactory.”

20. Question: What specific “appropriate engineering specifications and evidence” is the Government asking for?

Response: If dial tone cannot be passed to the end user telephone is an example.

C.2.1.2.4 Is duplicated on pages C-5 and C-6.

21. Question: In order for an Offeror’s response to this opportunity to be clear, will the Government update the solicitation with separate sections?

Response: The paragraphs have been renumbered.

C.2.1.2.6 The Government states: “…Each federal building shall be reviewed individually for this requirement by the offeror and any questions or concerns about its applicability shall be discussed with the COTR and CO.”

22. Question: Will the Government please provide details on how the Government expects each building to be reviewed individually?

Response: In order to transition the services at each building, GSA will provide the existing quantity of services and the RTAS vendor shall work with the incumbent vendor regarding delivery of those required services. A transition plan will then be developed by all parties involved.

23. Question: Will the Government please provide details on when the Government expects each building to be reviewed individually?

Response: Prior to transition each building shall be reviewed.

24. Question: Will the surveys be accomplished post-award via TOPS orders using a Systems Engineer?

Response: A TOPS order will be issued for the transition of services. GSA will not issue a TOPS order just for the survey of the building. It shall be the RTAS vendor’s choice of who will survey the building.

C.2.1.2.9 The Government states they “…may require the Offeror to perform a system certification of the inside wiring…prior to acceptance.”

25. Question: What specific system certification may the Government require for inside wiring?

Response: As an example, the existing wiring can meet industry standards by providing dial tone to the end user.

26. Question: What acceptance is referenced in “…prior to acceptance.”? Acceptance of the order?

Response: Acceptance of the TOPS service order.

C.2.1.2.4 and C.2.1.2.4.1 Will the Government clarify “…The Offeror shall be responsible for maintaining any cable owned by others when the Offeror has used the existing infrastructure to deliver service. The Offeror shall be responsible for maintaining any cable the Offeror installs or uses in a building…”

27. Question: Please define what the Government means by “…maintaining…” the cable owned by others.

Response: Regarding both installation and maintenance of the service requested, the vendor shall use the existing infrastructure and complete the delivery of services required. If the infrastructure does not meet industry standards then the vendor will alert GSA and identify the problem, its resolution and the charges to correct the problem. GSA has the option to determine how best to correct the problem. GSA is not requiring the vendor to maintain the existing infrastructure only to use it and notify us of problems.

28. Question: Please clarify how this relates to Section C.2.1.10.3 Warranty Period “…All equipment and components procured as a unit under this contract shall be warranted for a period not less than the time specified in the original equipment manufacturer's warranty.…”

Response: In regards to equipment ordered under this contract the original equipment warranty shall apply. As far as cable or wire installed by the vendor the industry standard warranty applies.

C.2.1.2.4.2 The Government asks offerors to ensure numbers are available for use when requested.

29. Question: Unless the numbers are owned by the Offeror, how can the Offeror ensure their availability? Will the Government further describe its expectations under this requirement?

Response: This applies to vacant Centrex and DID numbers in the GSA number range available for use. Our expectation is for the vendor to maintain a list of vacant numbers for our future use.

C.2.1.7 Interoperability The Government states: “The GSA recognizes that different levels of interoperability (i.e., partial or full) exist commercially, particularly in the area of data networking.”

30. Question: Will the Government please clarify what is meant by different levels of interoperability?

Response: See Interoperability in Glossary of terms.

31. Question: How does the Government expect compliance with this requirement given that some services have no interoperability between platforms or across industry providers?

Please provide examples.

Response: Please clarify, GSA does not understand “given that some services have no interoperability between platforms or across industry providers?” Provide examples of services which have no interoperability between platforms or across industry providers.

32. Question: “The Offeror shall support interoperability for service offerings to allow a user of a service from one RTAS contract to be able to communicate with users of services from other service providers, RTAS and others, with equivalent service.” So Offerors better understand the requirement, will the Government please provide clarity on “…and others…” in this sentence?

Response: RTAS is a multi award contract; we are looking for interoperability between all RTAS awarded vendors and the vendors of other GSA contracts, such as Networx.

C.2.1.8.1 Numbering Plan and Dialing Plan This paragraph references the NXX blocks in Section J.3.1. When reviewing Section J.3.1, it is the NXX listing from CALSC.

33. Question: Will the Government provide a new list of NXXs and revise Section J.3.1?

Response: Yes, a list of NXXs related to the RTAS area has been provided in Attachment J-5.

C.2.1.10.1 Reliability The requirement states, “The maintainable design life of all Offeror-provided components, circuits, and equipment shall be at least seven years.” The term of the contract is four-year base period and four, one-year options for a total of eight years.

34. Question: Will the Government change the reliability requirement to also be eight years?

Response: The requirement has been changed to eight years.

C.2.1.10.2 Robustness The Offerors infrastructure shall be sufficiently robust that failure of any single system, sub system or component will not cause loss of service to more than 10% of their RTAS subscribers at any given geographic location.

35. Question: What is the Government’s definition of infrastructure?

Response: Infrastructure includes all components required to deliver the services ordered by GSA, cross connects, riser cable, tie cable, inside wire, jack, are some examples of infrastructure.

C.2.1.10.5 – Network Synchronization Addresses timing requirements

36. Question: How will timing requirements be detailed when ordered by the Government?

Response: If specific requirements other than industry standard are needed it will be placed on the TOPS service order.

C.2.1.10.6 Network Architecture In Section C.2.1.10.6 the Government states "a Performance Based Statement of Work". The RTAS solicitation is a FFP contract for local telecommunications services. Performance Based contracts usually entail Research & Development and Engineering, etc.

37. Question: Will the Government please clarify what it means by "Performance Based Statement of Work" and how that phrase applies to this particular solicitation?

Response: The Government requires the assistance of vendors to recommend services that will be of benefit to the government in regards to service delivery of the requested RTAS services, new ways to do business, increase the service capacity to the desktop (broadband, etc.). GSA is not looking for just a like for like change. A PBSOW provides the governments requirements and requires the vendor to develop the means to achieve the task and suggest possible alternatives and/or solutions.

C.2.1.10.8 This requirement refers to Section J, Attachment J-2 for feature information. Attachment J-2 is Wage Determinations.

38. Question: Will the Government provide the feature information attachment? Is this referenced feature information the same as the detail shown on page C-12, Table C.2-2?

Response: This has been corrected to reference Table C.2.2.

C.2.1.10.8 This RFP is a request for a menu of services, products, and equipment.

39. Question: Will the Government further define the “solution” it is seeking and provide the criteria and/or parameters of the solution being sought?

Response: See response to question 37. The services offered shall be services presently commercially available by the offeror.

C.2.1.10.11 Transmission Service Video and Voice Over IP (VOIP) are referenced and included in this requirement; however, these services are not listed on Table C.1-1.

40. Question: Will the Government add these two service categories to the list of services to be offered under this proposal?

Response: No, both the VoIP and video services can be provided over the various service offerings requested in this RFP. The Government would encourage offerings for these services priced along with the delivery service.

C.2.2.1.1 The Government has a requirement for feature bundles.

41. Question: Is the Government looking for bundles for all network access products, or only on a subset of all network access products, IE: Analog, EKL and ISDN Centrex?

Response: The Government is open to all packaging options offered, for example a voice mail box bundled with call forwarding features and message waiting features. An analog line with one or several bundled package features.

42. Question: Will the Government please define specific bundle packages rather than give bundle example generalities?

Response: One was provided in the previous response (question 41) for voice mail (VM) service, another is an analog line with 3way calling, call forward busy / don’t answer, caller ID, call hold, call pickup group, speed calling, another is an analog line with VM, etc. Under a PBSOW the vendor should offer bundled services based on past experience.

Table C.2-2 FEATURES

43. Question: BAC, Due to the limitations of this product, will the Government explain further the use and purpose of this feature?

Response: The Government utilizes this feature to provide individual billing to each of its client agencies. This information with be on the TOPS order and will be carried on the RTAS vendor invoice to ensure proper payment is rendered for the service requested. This has been lined out on Table C.2-3.

Intercom Dial:

Within the definition of Intercom Dial the Government used the term Intercom Group.

44. Question: Will the Government further define Intercom Group and its meaning as a part of Intercom Dial?

Response: As an example, all stations within a Centrex system are in the same Intercom Group, those same stations can then Intercom Dial (abbreviated dialing) each other.

Remote Access Call forwarding

45. Question: Please provide examples of Government applications for this service so Offerors are certain to deliver the feature the Government is looking for.

Response: As an example, for COOP operations this feature is used by primary COOP assigned personnel to remotely access their office telephone (from a telephone not on the Government system) to forward all future calls to another location outside of the existing Centrex system for a temporary length of time. This may be a designated COOP site or another site.

46. Question: Voice Mail #3 has a strikethrough over the number. Does that represent a feature not required or is the strikethrough a typo?

Response: This is a typo and the strike through has been removed.

Table C.2-3 Required VS Basic Capabilities and Features

47. Question: Will the Government provide a further breakdown structure on the capabilities and functionalities for the various types of lines? Offeror requires further definition of an RTAS line and an RTAS trunk.

Response: A RTAS line is any of the following; analog line (Centrex or POTS), ISDN BRI, a RTAS trunk refers to a DOD or DID trunk as well as PRI.

Response: Definitions can be found in Section C, Table C.2-2.

49. Question: Can the Government provide a detailed explanation of how station-to-station dialing will function with trunks? Provide examples.

Response: Table C.2-2 has been changed to indicate Station to Station Dialing is N/A for RTAS trunks.

Response: Table C.2-2 has been changed to show a strike through for the items ISDN BRI lines, ISDN PRI lines and ISDN Secondary Number.

C.2.2.5.6 Offeror shall provide Call Detail Reports (CDR) as a minimum standard for all outgoing and incoming traffic upon request. The CDR shall be provided at the end of the billing period and show the detail of all outbound calls made from RTAS locations each month.

51. Question: Will the Government provide an example of the minimum standards needed to meet the requirement of incoming traffic as part of the Call Detail Reports?

Response: The incoming reference will be removed from the RFP.

C.2.2.5.6 There are two paragraph requirements with this number.

52. Question: Will the Government re-number the RFP document?

Response: The paragraphs have been numbered.

Table C.2-7 CSDS User Network Interface Types The Government has identified two #5 UNI Types.

53. Question: Is this a sequential error? Will the second #5 be adjusted to #6?

Response: This has been corrected, the second #5 was changed to #6.

C.2.4.1.1 The Government states: “DTS shall provide dedicated transmission bandwidth between SDPs within the RTAS service area.”

54. Question: This is a local service contract. Is the Government requirement of DTS to provide dedicated transmission bandwidth between SDPs within each LATA of the RTAS service area?

Response: Yes, this RFP addresses only intra lata services.

C.2.4.2.1.1 The Government listed all OCx services as OCx and OCxc with the exception of OC48 which has been listed twice.

55. Question: Does the Government intend to ask for OC48 and OC48c services?

Response: This reference has been corrected.

C.2.5.3.8 Seems to be out of sequence

56. Question: Is this a typo?

Response: This item was removed.

C.2.5.2 Features

C.2.5.2 through C.2.5.2.1.8 Seems to be missing for the Features section of the RFP

57. Question: Will the Government provide requirements for this Features section of the RFP?

Response: This has been changed, the reference to C2.5.2.1.9 Service Level Guarantee / Restoration of Service has been moved to C3.5.4.4 and a reference added to C.2.1.10.4. The other paragraphs have been removed.

C.2.5.2.2.2.1 This requirement paragraph is missing or is mis-numbered.

58. Question: Will the Government confirm whether the requirement was removed on purpose, is missing, or is mis-numbered?

Response: This has been corrected.

C.3 States “The Offeror shall incorporate state-of-the-art web-enabled commercial Business Support Systems (BSS) and Operational Support Systems (OSS) in accomplishing these functions.” However, C.1.2.1.3 states these systems are to be provided “…where commercially available.”

59. Question: Will the Government please define the Government’s requirements for BSS/OSS? Is it as stated in C.1.2.1.3, where commercially available?

Response: Yes, where commercially available.

C.3.2.1 Service Order Process This section does not include a requirement to “Initiate Service Orders.”

60. Question: Will the Government confirm this requirement was removed intentionally?

Response: This reference has been added to C.3.2.1.2 “Accept and initiate service orders”.

C.3.2.4 Provide Price Quotes This requirement states the Offeror will provide price quotes to an agency (DODB) or to a GSA representative.

61. Question: Will the Government confirm whether the Offeror will be required to provide price quotes to GSA representatives for Centrally-Billed orders? If so, will the Government provide the GMF that is to be incorporated into the quoted rate?

Response: Yes, the offeror will need to provide the contract price quote. The GMF is not required to be quoted.

C.3.2.11.1 Service Order Completion and Acceptance The Government states: “…The Offeror shall be responsible for coordinating with any other Offerors who may be involved in activating the service to ensure that everything necessary to complete the service order has been accomplished. If we provide service and have tested to SDP1, then a hand-off will occur and installation requirements will have been satisfied.

62. Question: Will the Government please offer suggestions on how one Offeror ensures that another Offeror’s service is satisfactorily completed?

Response: This is determined by the SDP, in a closed building at an SDP 3, testing from the jack indicates service is good through both vendors facilities.

63. Question: Will the Government please define what is meant by “…shall be responsible for coordinating….”

Response: The RTAS vendor issued the TOPS order shall coordinate services to the SDP requested.

C.3.4.1 Submission Requirements

64. Question: Is it the intention of the Government to receive one, single monthly Centralized invoice for all items billing under the RTAS contract (not counting Direct Billed invoices)? If not, please identify the expectations concerning the number of Centralized invoices.

Response: Bills shall be received for each TOPS board based on where the service was ordered.

C.3.4.3.2.7 Requirement states that, “The Offeror shall itemize all mandatory state and local taxes, surcharges, and fees on the invoice….”

65. Question: Will the Government provide clear explanation for how this itemization should appear given the requirements in Section B to include the surcharges in the base price of the service?

Response: The taxes, surcharges and fees shall be included in the service (CLIN) MRC not individually on the invoice; this has been changed in C.3.4.3.2.7.

C.3.4.3.3.1 Each invoice shall reflect all charges from the first to the last day of the previous billing cycle. The Offeror shall charge for all services, features, and equipment within three billing cycles after the services were rendered. All charges not submitted within three billing cycles shall be borne by the Offeror unless a request for extension is formally approved by the ACO.

66. Question: Will the Government please clarify and define the time period for “billing cycles”? Will the Government please clarify when it considers a billing cycle to start and to end?

Response: The billing cycle length is 30 days. The start date shall be agreed upon by the vendor and GSA.

C.3.4.3.4.1 “The Offeror shall submit an electronic invoice for all goods and services within 10 calendar days of the period being billed to the customer….” In order to accommodate some of the unique billing requirements on this contract, it will most likely be necessary for industry to design a more customized bill for the Government and its users.

67. Question: Please define location code and identify how this would be communicated to the Offeror, and how the information is expected to be maintained.

Response: The codes in C.3.4.3.4.1 determine the TOPS board to be billed, the agency code determines the agency requesting the service, and the location code provides the worksite information. All of this information will be on the TOPS order sent to the RTAS vendor. It shall be maintained by the vendor for future use.

68. Question: Will the Government be willing to accept a longer bill interval in order to accommodate customized invoice preparation?

Response: No.

Figure C.3-3 The Government’s figure deviates from that as provided on the MAAs and on the RLSC.

69. Question: Please elaborate on the differences between the existing MAA/RLSC SDP delivery and that of RTAS.

Response: The RTAS has fewer SDP’s than the MAA to eliminate the number of vendors involved in the delivery of the requested service. SDP’s 1 (NETPOP) and 2 PBX/MUX telco room) are the same, SDP 3 (desktop jack) on the RTAS is SDP 5 on the MAA, SDP 4 (RTAS SDP 3 with a telephone) in RTAS is the same as SDP 6 in the MAA. The RLSC has no SDP references.

70. Question: Please detail hand off specifics to each SDP.

Example: Is the hand off to a PBX next to the PBX or is the Government expecting cross-connects onto the PBX (which may void manufacturers’ warranty)?

Response: SDP 1 handoff at the NETPOP, SDP 2 handoff next to the PBX/MUX, no connection to the equipment is required; SDP 3 handoff at the jack and SDP 4 handoff includes the telephone.

71. Question: For SDP4, which seems to include the handset, is the Government asking for the CPE to be built into the line rate? If so, will the Government determine the handset to be included? Would the Government consider the handset price as an ala carte item so the agency user could select the appropriate set to satisfy its customer’s need?

Response: The Handset shall be a separate from the line MRC; it will have its own charges associated with it depending on the type of equipment required. Yes multiple handsets and pricing can be provided.

72. Question: Also, on SDP4, is the Government asking for maintenance on the CPE? Would the Government consider ala carte handset maintenance pricing so its agencies have a choice on maintenance?

Response: Yes.

C.5.4.2.1.1.1 – C.5.4.2.1.1.5 There are duplicate numbers with different topics between pages C-51 and C-52.

73. Question: Please adjust the numbering scheme so there are no duplicate numbers.

Response: This reference has been changed.

C.5.4.2.1.1.5 (The first one) on page C-51 is followed by C.4.5.2.1.1.6.

74. Question: Please clarify if this is a numbering error and will be adjusted or if the number is correct and will be placed in sequential order in the RFP.

Response: This has been corrected.

C.5.4.2.1.1.2 Service and features This Requirement references Section J, Attachment J-2. This attachment is the Wage Determinations documents and does not include the list of existing services.

75. Question: Will the Government provide the list of existing services in a different attachment?

Response: The information has been provided in an Attachment J-2, RTAS List of Historical Buildings.

C.5.4.2.1.1.3 The Government states: “All services deemed critical to the transitioning agency shall be identified and tested for operation prior to and immediately after the transition.

76. Question: Please define “critical” as stated in the requirement above.

Response: Emergency numbers, hotlines, published numbers, upper management numbers within the agency, COOP numbers, etc.

C.5.4.2.1.1.4 Coordination of any CPE Vendors

77. Question: The requirement seems to indicate that the Agency would be responsible for notifying any CPE vendors that would be required during a transition. Will the Government confirm this?

Response: CPE vendor notification will be the responsibility of the agency owning the equipment.

SECTION E

E.3.2 Verification Testing of Contractor’s OSS Table E.3-1 OSS Verification Test Cases Test Case #1 requires the Offeror to accept (for test purposes) an order for each of the services specified in Section C that the contractor is contracted to provide. This can be a very time consuming work effort since it also is a requirement that the contractor cannot accept any other orders until the test order has been completed.

78. Question: Would the Government consider changing “for each of the services specified in Section C” to read, “for key, primary services as agreed to with the COTR from the services specified in Section C”?

Response: The testing will not be waived. This maybe reviewed again after award.

SECTION F– Deliveries Deliverable for H.8, Schedule B Pricing Tables: Frequency of 30 calendar days does not match the requirement in Section H.8 of 20 days.

79. Question: Will the Government consider changing the H.8 requirement to 30 calendar days to match the frequency shown in the Deliverables schedule?

Response: This requirement has been changed to 30 calendar days.

80. Question: Further, will the Government provide explanation for why the pricing tables are to be resubmitted monthly?

Response: This requirement has been changed in Table F.2-1.

SECTION G

G.2.1.4. Technology Refreshment Plan The annual Technology Refreshment Plan (Section C.2.1.10.12.1.) shall describe changes in domestic and international standards that may impact the RTAS network and shall recommend actions to incorporate certain changes. It shall also discuss new or emerging technology that is commercially available in the Chicago service area and the contractor’s plan to implement this technology.

81. Question: The last sentence of the requirement above requests that the plan “...discuss new or emerging technology that is commercially available in the Chicago service area….” Will the Government clarify if it wants discussion of emerging technology only in Chicago?

Response: This has been corrected to reference “…the RTAS service area...”.

SECTION H

H.1 Type and Term of Contract and L.5 Requirements H.1 and L.5 both state that RTAS is a “firm price” type of contract which contradicts Sections B.1.2 and H.27 that says “firm fixed price” type of contract.

82. Question: Will the Government confirm which contract type is applicable for RTAS and make needed corrections to the inconsistencies?

Response: This has been corrected to show “firm fixed price” in both sections.

H.9 Protection of Proposal and Contract Information In the last sentence, the Government states, “…during the full contract period (up to 5 years)….”

83. Question: Will the Government clarify whether this reference to five (5) years is correct or whether it should match the total period of performance earlier specified as eight (8) years?

Response: This has been changed to eight years.

H.12.1 Performance, Tables H.12-2 and H.12-3 Within this requirement outlining Performance Requirements and Credit Allowances for Outages there are no references to the product categories of Broadcast Access Service (BAS) or SONET Ring Service (SRS).

84. Question: Should these two product categories be included here and, if so, will the Government make the required revisions to include them?

Response: The changes have been made to both tables.

H.25 Associated Government Fee(s), item #3

85. Question: Would the Government consider submission of the Associated Government Fee on DODB accounts on a quarterly basis instead of monthly as is done on MAA contracts today?

Response: No.

H.25 Associated Government Fee(s) The contractor shall collect the RTAS Associated Government Fee(s) from Direct Billed Customers on a monthly basis throughout the life of the contract. This fee represents any direct or indirect costs incurred by the Government associated with the RTAS program such as, but not limited to, the contract management fee.

86. Question: Will the Government please clarify the difference between the Contract Management Fee shown above and the Associated Government Fee?

Response: The two fees are different, The AGF is associated with the services billed to an agency Direct Order Direct Bill (DODB), the other is the fee GSA charges for management and delivery of the RTAS services.

H.29 Historical Buildings The Government requires all work in historical buildings to conform to a set of special requirements.

87. Question: Please confirm that all 599 buildings identified on the Excel workbook titled “Copy of RTAS-Reg5-Historical Buildings. List,” which includes buildings like 230 S. Dearborn St., Chicago, IL., is a list of historical buildings.

Response: The list provided is GSA most current list of historical.

SECTION I

I.7 (c) States the total duration of this contract, including the exercise of any options under this clause, shall not exceed seven years. This contradicts the period of performance earlier indicated as eight (8) years in sections B.1.2 and H.1.

88. Question: Will the Government review this requirement and clarify the total years of duration?

Response: This has been changed to eight years.

SECTION J

J.3 RTAS Service and Location Information Seems to only address Chicago, IL, yet this contract is for six states. Further, J.3.1 suggests the Government provides a listing of current NPA-NXXs served by RTAS, but Table J.3-1 RTAS NPA-NXXs only has the metro-Chicago NPAs listed.

89. Question: Please provide the appropriate NPA-NXXs for RTAS.

Response: Attachment has been added in Section J. See Attachment J-5.

90. Question: The current table, although titled as an NPA-NXX table, only offers the NPAs. Will this be table be updated to also include the NXXs?

Response: Attachment has been added in Section J. See Attachment J-5.

J.3 RTAS Service and Location Information Also within J.3, the Government states “…Additionally, customer location and quantities are provided by service. Refer to Attachment J-1. Yet, when J-1 is checked on the List of Attachments, Attachment J-1, the document is RTAS List of Historical Buildings. Further, when the attachment was checked, there are no quantities of circuits detailed by customer location.

91. Question: Will the Government please provide updates to J.3 and Attachment J-1 or provide an additional attachment detailing the information described in section J.3?

Response: Attachment has been provided. See Attachment J-1, Region 5 Existing Services by State.

J.3.2 MAA Location and Quantity Information This requirement refers to Attachment J-2 as providing the current MAA network service requirements by location and quantity. Attachment J-2 is Wage Determinations.

92. Question: Will the Government provide the current list of network service locations and quantities as another attachment? This requirement refers to the current MAA network service requirements.

Response: Attachment has been provided. See Attachment J-1. This has been changed to reflect regional.

93. Question: Will the Government also provide network service requirements that are not currently under an MAA but are included in the scope of RTAS?

Response: Yes

J.6.1 Product/Service Categories Items 2.a. and 3.a. both reference record types of “Product Only Category;” however, there is no “Product Only Category” shown in this requirement.

94. Question: Will the Government confirm these references should read “Service Only”?

Response: Both references have been changed.

SECTION L

L.21 Delivery of Proposal Offerors shall submit hard copy proposals to be received by the time and date specified in SF 33 (Boxed Offers Only). Any proposals received after the time and date specified for receipt will be considered LATE.

Markings. It is important that the outer envelope or wrapping of each offer be addressed as shown below. Failure to properly address the outer cover could cause an offer to be misdirected and received too late at the required destination.

Offeror’s Return Address Contracting Officer’s Address:

Mara E. Shultz RTAS Contracting Officer General Services Administration c/o Kim Brown 230 S. Dearborn Street, Room 3280 Chicago, IL 60604 Office Phone: 312.886.8906 Facsimile: 312.886.3805

95. Question: In Section L.3, the Government indicates that Ms. Thomas is CO, but in Section L.21 (see above), Ms. Shultz is listed as RTAS CO. Will the Government please clarify which person is the RTAS CO?

Response: This has been corrected, Tawanda Thomas is the CO.

L.30 General Proposal Instructions The purpose of this section is to specify the general requirements for the contents of proposals. The proposal shall be submitted in hard copy original and four copies and electronic media. The offeror shall submit items such as annual reports, brochures, or oversize charts in hardcopy, only, if unavailable electronically. The specific requirements for the general proposal contents are presented in the following sections.

96. Question: Will the Government consider eliminating the requirement for an Offeror to provide an Annual Report in the hard copies of its submission and allow the Offeror to provide the Annual Report in only the electronic submissions via CD-Rom? The Annual Report’s size is prohibitive within the page count limitations of this RFP.

Response: This information can be provided via CD-ROM.

L30.

Spacing. The Past Performance, Technical, Management, and Price sections shall have line spacing of one-and-a-half.

97. Question: Will the Government please clarify what the line spacing should be between the Government's requirements which are to be embedded in the proposal and the Offeror's response? We understand that Past Performance, Technical, Management, and Price sections shall have line spacing of 1.5.

Response: This has been changed to a line spacing of one.

L.31.2.1 Technical Response Under “Technical Support Services.”

98. Question: Will the Government further define what is meant by its use of “Technical Support Services” and provide examples of same?

Response: These are RTAS vendor services that support the vendor infrastructure and switching capabilities which provide the RTAS services to the Government. Examples would be central office or switching engineers, cable and fiber technicians, translations support, etc.

L.31.4 Price Section Offerors are required to submit workbooks identified as part of its Price Proposal. The workbooks listed do not include Broadcast Access Service (BAS) or SONET Ring Service (SRS).

99. Question: Will the Government clarify how Offerors are to submit pricing for these two product categories that are required in Section C.?

Response: Reference to the BAS and SRS workbooks have been added.

L.31.4 Price Section The offeror shall prepare its Price Section to address all applicable requirements specified in Section B, Pricing. All information regarding prices, including that contained on electronic media, for the proposed services shall be logically presented in this section. The offeror shall enter its prices in the format of the price tables defined in Section B. No other price elements beyond those defined in Section B are permitted.

100. Question: The last sentence of the Government’s requirement requests that no other price elements beyond those defined in Section B are permitted. We interpret this to mean the Government does not want any line items added to the price tables. This is mentioned also in Section B.1.4. Will the Government please clarify what it means by the last sentence of its requirement, and how it would suggest an offeror account for any missing price elements or additional price elements needed for accuracy?

Response: See response to question 7. There is a distinction between CLIN’s and pricing elements. If an additional element is needed to provide the service requested, then a CLIN would allow for the pricing of that element.

L.31.5 Computational Rules The offeror shall submit complete prices for all five years of the contract period.

101. Question: The sentence shown above from the Government’s requirement states that the offeror shall submit prices for all five years of the contract. In Section B.1.2, the Government states that the RTAS opportunity is “…a four year base with four option years.” Will the Government please clarify which is correct for the RTAS opportunity?

Response: This has been changed to read eight years.

The remainder of this requirement references the application of surcharges into the Total Evaluated Discounted Cost. Surcharges are to be included in the base price of service.

102. Question: Why, then, would surcharges also be applied to quantities again?

Response: The surcharges, taxes and fees for each service required are referenced with that service and its associated CLIN. Show them as they apply to each CLIN not in quantities.

103. Question: Will the Government provide further explanation or remove surcharges from this computation?

Response: The surcharges, taxes and fees for each service required are referenced with that service and its associated CLIN. Show them as they apply to each CLIN not in quantities.

SECTION M

M.2.2 (under 2. d.)

As part of Technical Approach / Network Architecture and Services / Service Coverage – The Government discusses the Offerors’ abilities for broad service coverage in the Metropolitan Chicago service area, yet this is a six-state solicitation.

104. Question: Request the Government update the Network Architecture and Services / Service Coverage area to align with RTAS.

Response: This reference has been changed.

Pricing Workbooks The Government has asked for SONET Ring Services (SRS), yet the only pricing accounted for in the Pricing workbook is on the DTS tab for Dedicated Transmission Service, which is really tailored to point-to-point circuits. Further, no SRS “elements” are identified for pricing anywhere (like PORT charges and NODE charges).

105. Question: Will the Government allow Offerors the ability to add a pricing worksheet on each State-specific workbook for SRS in support of the Government’s interest in these services?

Response: The pricing worksheet has been added. See Pricing Tables.

The Government has provided on the DTS tab, NPA to NPA pricing for mileage associated with DTS. This is not an industry practice, nor commercially available.

106. Question: Request Offerors have the ability to add a pricing worksheet on each State-specific workbook for mileage related components associated with VS-CSDS Dedicated Access Service.

Response: The government is encouraging full pricing for services orders not piecemeal pricing. CO mileage and local loops are not the standard used by all vendors, be innovative. If that cannot be done then add a worksheet.

The Government has the same NPA to NPA coverage for all 6 states, where the CLIN XXXXXX0500 has an originating and terminating NPA of 224. The next one is XXXXXX0501 with an originating NPA of 224 and terminating of 312. These are IL NPAs.

107. Question: These are not accurate as they don’t apply to all six states that are included in the RTAS opportunity. Will the Government please provide revised, complete and accurate pricing tables?

Response: Use worksheet as a guideline. Offerors shall list Originating NPA and Terminating NPA based on how they plan to propose pricing.

On the FEATURES worksheet of each State-specific pricing workbook:

The Government has asked for pricing on Voicemail with 30 message length and 60 message length. This is not a requirement as detailed on Table C.2-2 Definition of VS Basic Capabilities and Features. Additionally, there are basic feature/requirements for Automated Attendant/Call Tree and Enhanced Voice Mail.

108. Question: Will the Government provide Offerors updates to the state-specific FEATURES worksheets to accommodate for the actual Basic Capabilities/Features requested?

Response: This feature table covers the region, it is not state specific.

On the Indiana, Michigan, Ohio, Wisconsin and Minnesota Pricing Workbooks:

There are inaccurate RFP solicitation numbers in the headers of all workbooks. Additionally, on the Usage worksheet of all six states, the Charge Type is CLSC area usage.

109. Question: Please provide definition of CLSC so Offerors understand how to price for…