Amendment A0006 Questions 114-138 Final.doc

DOC document 58 KB Posted

Attached to
DeCA Broadband/VSAT
Solicitation number
HC1013-08-R-2004
Issued by

About this file

Vendor Q A 114-138

View the file

Other files

File Type Posted
Questions 139-154.doc DOC document
DSL-VSAT PWS 20080520.doc DOC document
DSL-VSAT Attachment 8B NOC Acceptance Amended 20080520.doc DOC document
SF 30 A0007.doc DOC document
Updated Draft Attachment 13- Section B 20 May 08.xls XLS spreadsheet
DeCA VSAT RFP Amendment 0007.doc DOC document
Pricing pages per site.xls XLS spreadsheet
DSL-VSAT Attachment 4B Store WAN-Amended2.pdf PDF
Pricing pages per site.xls XLS spreadsheet
Updated Draft Attachment 13- Section B 12 May 08.xls XLS spreadsheet
DSL-VSAT Attachment 2 OCD Test Plan-Amended.xls XLS spreadsheet
SF 30 A0006.doc DOC document
Pre-Proposal attendance sheet.doc DOC document
DSL-VSAT Attachment 3 HQ CARTS TB Amended2.pdf PDF
DSL-VSAT PWS 13 May 08.doc DOC document
Pre-proposal minutes-DeCA.doc DOC document
DeCA VSAT RFP Amendment 0006.doc DOC document
DSL-VSAT Attachment 12 Candidate Sites-Amended 20080513-2rw.xls XLS spreadsheet
Questions 93-113.doc DOC document
Amendment A0004 SF30.doc DOC document
DSL-VSAT Attachment 4B Store WAN-Amended.pdf PDF
Attachment 13- Section B-A0003.xls XLS spreadsheet
DeCA VSAT RFP Amendment 0003.doc DOC document
Vendor questions 76-92.doc DOC document
SF 30 Amendment A0003.doc DOC document
Amendment A0002 questions 40 -75.doc DOC document
Amendment A0002 SF 30.doc DOC document
Attachment 1 DeCA PWS-A0002.doc DOC document
DeCA VSAT RFP Amendment 0002.doc DOC document
DSL-VSAT Attachment 3 HQ CARTS TB Amended.pdf PDF
DeCA VSAT RFP Amendment 0001.doc DOC document
Amended DSL-VSAT Attachment 7 Traffic Profile 20080401.pdf PDF
Attachment 13- Section B-040108.xls XLS spreadsheet
Vendor Questions 1-39.doc DOC document
Amendment 0001 SF30.doc DOC document
Amended DSL-VSAT Attachment 4A Store WAN.pdf PDF
DeCAVSATRFP032608.doc DOC document
DSL-VSATAttachment10SampleFloorPlans.pdf PDF
Attachment13-SectionB.xls XLS spreadsheet
DSL-VSATAttachment3HQCARTSTB.doc DOC document
DSL-VSATAttachment11ATInfo.pdf PDF
DSL-VSATAttachment5DeCANetwork.doc DOC document
DSL-VSATAttachment9Samples.pdf PDF
DSL-VSATAttachment7TrafficProfile20071212.doc DOC document
DSL-VSATAttachment12CandidateSites20071212-1jh.xls XLS spreadsheet
DSL-VSATAttachment4AStoreWAN.doc DOC document
1_Attachment14-PPSurvey.doc DOC document
DSL-VSATAttachment8BNOCAcceptance.doc DOC document
DSL-VSATAttachment4BStoreWAN.doc DOC document
Attachment14-PPSurvey.doc DOC document
Show 40 more

Latest 50 of 54 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Questions 114-216, Amendment A0006 Q-114. Many of the telephone numbers and addresses in the CONUS region in particular provided in Attachment 1 are unusable for ascertaining the availability of DSL. We have spoken with three DSL providers who have all come back with the same information – that the information needs correcting (corrected address requested and an analog phone number required) and providing a quote is impossible without corrected information. Could DeCA provide better contact information e.g. an analog telephone number that rings directly at each store instead of a number associated with a DS0 that appears on a T1 that terminates somewhere on the military facility?

A-114. Virtually all commissaries are tenant organizations on military installations. They derive their phone service through the base/post central office. A few of the commissaries may use base phone systems in which case the phones will ring through the base central office to the store. No other information is available.

Q-115. In reference to PWS 2.1.6.2 Are the 90 and 1200 ms requirement for pings meant to be the one way or roundtrip times?

A-115. Roundtrip.

Q-116. Referring to PWS. 2.1.6.2. Given that DSL is not available with guaranteed latency, we assume that the 90 ms ICMP ping requirement only applies to the dedicated terrestrial links. Is that correct?

A-116. No. The requirement is stated in PWS 2.1.6.2, the sentence starting with “The ping results span…” Q-117. PWS 1.1 states that “Where VSAT service is not available at a reasonable cost, no VSAT component of the Broadband /VSAT solution is required.” Please quantitatively define the term “reasonable cost.” We would like to see some real values provided by the Government to understand what is meant by “reasonable cost”.

A-117. Reasonable cost is a subjective determination by the Government that would include factors such as store size, anticipated sales, number of patrons served, impact of not providing the service to both the local community and the Agency, cost of legacy terrestrial transport service, proposed cost of the service. Efforts would be made to establish some type of return on investment within the life of the contract. An unreasonable cost example would be $10,000 to install a dish on a slab in Keflavik for instance. Another example would be $3,000+ for a pair of C-band modems for 3 separate sites in the same location.

Q-118. In PWS Section 2.1.7.1 the table shows that two VPN tunnels are required to each store location, but CLINs 0023 and 0025 have qty. 1. How are the two IPGW links to Ft. Lee and the two links to McClellan Park to be priced?

A-118. Please see PWS Attachments 4B, amended 200800508. The asterisk by the Vendor Teleport and the Broadband Network Hub is defined in the bottom left of the drawing. These 2 components could be co-located and/or could share the same IPGW links to DeCA’s network. For OCONUS the DeCA West and DeCA HQ components would reflect the OCONUS connection points specified in 1.2.2 and 2.1.7.1. Pricing should be based on the size of the connections as determined by the vendor’s traffic analysis of the information provided as part of the PWS.

Q-119. PWS 2.1.6.1: The first paragraph of this section requires IPGW links to the notes listed in Attachment 12, Tab D. The second paragraph implies that Yokosuka and Lakenheath are not a firm requirement. Is this correct?

A-119. Per the PWS, these are optional, based on the vendor solution.

Q-120: Reference RFP: Section 2.1 Paragraph 2.1.1 VSAT dish size constraints: Is there any space constraints or limitations for the installation of the VSAT antenna at each site? If yes what is the maximum antenna size (diameter) that can be accommodated in a commissary or CDC site? The dish, if placed on the roof cannot be seen from the front of Commissary. How far in front of the commissary would one be looking?

A-120. We believe the reference for this question should be PWS section 2.3.1 where installation requirements are provided. Refer to revised PWS section 2.3.1.

Q-121: Reference RFP: Section 2.1 Paragraph 2.1.2 VSAT Multicast: It is required a minimum 15 Mbps user transmission rate to all remote locations for 15 minutes once a week. Please explain the following sentence. Contractor shall ensure data security/encryption during transmission. Is this mean

a) The link (terrestrial + satellite) from the source to remote satellite modem must be encrypted OR

b) The contractor must ensure that only authorized sites can gain access to the information? OR

c) Multicast application must ensure data encryption?

In order to accomplished the multicast from the multicast server installed on DeCA LAN, GFE router must be capable of multicast routing. If end to end security is required for the multicast then a group VPN features must be implemented on GFE router also.

A-121. Any or all of a, b and c listed in the question are possible components of a solution. Solution security requirements are outlined in 2.1.9, 2.1.3, 2.5.5, 5.0 and 6.0. The contractor should design their solution to meet PWS requirements. Refer also to previous questions on multicast which include: 41, 61, 62, 83-87, 91, 93.

Q-122: Reference RFP: Section 2.1 Paragraph 2.1.3 Bandwidth for Internet access: Internet access security

a) The broadband access (DSL/Cable) is connected to internet. Does GFE equipment have the necessary firewall and security protections to avoid attacks from the Internet, or the provider must supply security appliances.

b) Internet access service will be provided to a separate DeCA LAN connected to GFE edge router. The traffic separation between VPN traffic and Internet traffic must be enforced by GFE edge router A-122. PWS 2.1.3 states “to include provisions for direct Internet access”; the requirement specifies a transport service. The government is responsible for security.

Q-123: Reference RFP: Section 2.1 Paragraph 2.1.4 VSAT traffic requirements: VSAT data rate per station type (Large, medium, small).

a) Is the VSAT Up/down bandwidth (512 /1544 Kbps) indicated in the table represent the VSAT network inbound and outbound carriers to be shared by remote stations, or is this the CIR bandwidth requirement per station. If this is the CIR data rate per station, then why the VSAT backup link bandwidth is higher than the primary terrestrial link (512/1024 Kbps) The terrestrial link speed shown, is that duplex, inbound from the remote to DeCA, or DeCA to the remote. The language differs from the VSAT in/out column.

b) We understand from paragraph 2.1.4 that the terrestrial bandwidth is symmetrical with a CIR and Burst rate for each direction.

c) If not what is the CIR and burst rate for each type of store on the VSAT link in both directions

· CIR upstream =

Kbps Burst upstream= Kbps

· CIR Downstream =

Kbps Burst downstream=

Kbps A-123. See Revised PWS.

Q-124: Reference RFP: Section 2.1 Paragraph 2.1.5 Service availability 99.7%:

a) We understand that the uptime for Broadband/VSAT and terrestrial link (IPGW) must be 99.7%. We understand that this availability considers the redundancy of the link (VSAT/DSL) and the stop time representing the agreed time for the provider to restore a failed component, and any interference or circumstances beyond contractor responsibility.

b) Does this availability require for each individual link DSL/Cable and VSAT, or is this an either/or running an aggregate total of reliability ?

A-124 See revised PWS.

Q-125: Packet loss -Reference RFP: Section 2.1 Paragraph 2.1.6.2: There should be no packet loss. May be this should say there will be a minimum packet loss of xxx % A-125. The requirement stands as stated.

Q-126: Pool over-subscription Reference RFP: Section 2.1 Paragraph 2.1.6.5: Does this refer to the satellite link oversubscription or to both terrestrial and satellite portions.

A-126 Both where relevant.

Q-127: Leased VSAT Reference RFP: Section 2.1 Paragraph 2.1.11: PWS called for delivery and operation within 48 hours after DeCA request. In CONUS and specify how in OCONUS if can not be accomplished in 48 Hours. Do you require 4 systems; and if so, how do we charge for these to insure payment for the investment. Can we charge a monthly lease price even if they are not in use, based on a one year contract?

A-127 The amended PWS has changed this requirement to a purchase item with monthly recurring charges for service, maintenance as well as shipping and setup charges. Refer to the revised PWS for additional specifications.

Q-128: Pilot test before full deployment Reference RFP: Section 2.2 Page 8 Paragraph 2.2.1.1: Does this paragraph means that only terrestrial broadband portion will be tested, or both VPNs through satellite and terrestrial links. The Pilot test requires that the basic network be implemented, space segment, multicast and broadband. The start-up cost due to the multicast and space segment for the multicast will make this an expensive CLIN.

A-128 Noted.

Q-129: Site survey, preparation and installation. Reference RFP: Section 2.3 Paragraph 2.3.2: The required schedule of events does not consider the risk and time element for DOIM termination requirements, additional post/camp/station cable, nor Area Facility Engineering for approval of mounts, penetrations and red-line of as-built drawing. The time element could be from 8 to 18 days between survey and installation due to Government Post/Camp and Station requirements that the Contractor should have no liability for. The Demarcation for the Broadband shows the commissary; however, on many Posts, the demark will be the DOIM post cable plant. Who will be responsible for coordinating the use of in place Government cabling between the DoIM and the Commissary if this should occur.

A-129 The amended PWS revises paragraphs 2.1.8, 2.3.2 and 2.3.6 to better define the requirements. The answers to subsequent questions provide additional clarification.

Q-130: SOW, 2.1.6.1. Please clarify that you are requesting vendors to price terrestrial circuits from the six regional network nodes to the vendor teleports.

A-130: Attachment 13 identifies all required pricing.

Q-131: International terrestrial circuits usually have multiple carriers along the entire path and thus quotations for pricing can take 60-90 days and installation can take 6 months. Will the Govt consider pass through pricing on these CLINs?

A-131: No, the pricing structure for these CLINs will remain the same.

Q-132: How much time will the vendor have to accomplish PCI certification?

A-132: PCI certification should be completed within 30 days after site installation acceptance by the Government. The PWS was updated to reflect this.

Q-133: Past performance from the members of a Joint Venture. In this case the controlling member is an 8a firm and the other member is a veteran owned small business. We would like to use the past performance from both of the member companies. Would this be acceptable?

A-133: In accordance with Title 13, Vol 1 of the Code of Federal Regulations, Part 124, Sec 124-513 (a) If approved by SBA, a Participant may enter into a joint venture agreement with one or more other small business concerns, whether or not 8(a) Participants, for the purpose of performing a specific 8(a) contract. Additionally, SBA must receive 8(a) Joint Venture agreement PRIOR TO BID OPENING and SBA must approve 8(a) Joint Venture agreement PRIOR TO AWARD of an 8(a) contract. Joint Ventures that have adhered to all the SBA regulations may submit past performance information on all parties in the Joint Venture.

Q-134: Based on the amount of questions at the Pre Proposal Conference and the expected changes to the subject solicitation I respectfully request an extension until 30 May. The additional 10 days will allow vendors to modify our proposals to include major changes to the technical proposal and pricing proposal. Additionally, will you allow submission of proposals via Email by the required due date; with the hard copy as required by the solicitation arriving within 48 hrs after via FEDEX?

A-134: The Proposal due date has been extended to 28 May 2008, at 2pm CST. Proposals will NOT be accepted via email or fax.

Q-135: The PWS currently states that multicast must take place within a 15 minute window. Can the bidder propose a technically compliant solution in which the window time is extended in order to give the Government a “better value” meaning that there is no downside technically and the price could feasibly be a lot lower?

A-135: The Government requirement is for multicast as stated in the PWS.

Q-136: Given that the file size is not known and reliable (guaranteed) multicast is a requirement, how can we ensure the 15 minutes is enough ? Can you provide guidance on file size?

A-136: The theoretical maximum file transfer size without latency constraints is:

15,000,000 bits per second divided by 8 bits per byte equals 1,875,000 bytes per second.

1,875,000 bytes per second times 60 seconds per minute equals 112,500,000 bytes per minute.

112,500,000 bytes per minute times 15 minutes equals 1,687,500,000 bytes in 15 minutes. or 1.6GB.

Our expectation is to be able to transfer a 1 GB file in 15 minutes.

Q-137: Given that the off-hours time is different per region/location of the world, please provide a better definition of the off-hours window based on the store DeCA commissary open and close time?

A-137: Off hours is site specific.

Q-138: It is our understanding that the terrestrial speed for multicast (from HQ to Satellite Teleport) can be less than 15Mbps but the satellite speed has to be 15Mbps. Can you please explain why the Government has set these specifications like this?

A-138: The vendor multicast solution should incorporate the limitations of the terrestrial connection so the multicast push at 15 Mbps is not constrained by the terrestrial limitation.

PAGE

File details come from the government source that posted it. Updated .