RFP Questions-Answers 22 Jul 21.xlsx
XLSX spreadsheet 19 KB Posted
- Attached to
- Defense Information Systems Network (DISN) Optical Network Enhancements Link 42 - HC101321R0010
- Solicitation number
- HC101321R0010
- Issued by
-
Defense Information Systems Agency
About this file
This document contains questions and answers related to a solicitation for fiber optic cable installation and operations and maintenance services between Ashburn, VA, Washington DC, and Fort Belvoir, VA to support the Defense Information Systems Agency. The total small business set-aside requirement includes installation of four fiber strands in a ring configuration between each location, with all fibers diversely routed. The period of performance is one base year plus nine 1-year option periods for operations and maintenance. Services will include link activations, maintenance of any optical level attenuators and equipment located at colocation facilities. Pricing is to be provided for installation and annual maintenance costs.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| HC101321R00100005.docx | DOCX document | |
| RFP Questions-Answers 26 Jul 21.xlsx | XLSX spreadsheet | |
| Attachment 1 - Performance Work Statement (PWS) Amendment 0002.docx | DOCX document | |
| HC101321R00100004.docx | DOCX document | |
| Attachment 1 - Performance Work Statement (PWS) Amendment 0001.docx | DOCX document | |
| Attachment 3 - Pricing Template Amendment 0001.xlsx | XLSX spreadsheet | |
| HC101321R00100003.docx | DOCX document | |
| RFP Questions-Answers.xlsx | XLSX spreadsheet | |
| Attachment 2 - QASP Amendment 0001.docx | DOCX document | |
| HC101321R00100002.docx | DOCX document | |
| HC101321R00100001.docx | DOCX document | |
| PWS Attachment 1A Fiber Requirements Specifications (FRS).pdf | ||
| Attachment 2 - QASP.pdf | ||
| Attachment 3 - Pricing Template.xlsx | XLSX spreadsheet | |
| HC101321R0010.docx | DOCX document | |
| Attachment 4 - Mission-Essential Services.pdf | ||
| PWS Attachment 1B Site Concurrence Letter (SCL) Template.pdf | ||
| Attachment 1 - Performance Work Statement (PWS).pdf |
Show all 18
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
Sheet1
| # | Document | Section/Page | Industry Questions | Government Response |
| 1 | Will the MBOM be provided to the contractor as GFE? Or are the offerors required to reach directly out to Ciena to obtain the MBOM? | The equipment will be provided as GFE. | ||
| 2 | PWS | Section 6.2 Task 2 | Comment: The PWS indicates the Contractor shall make operational a new fiber path consisting of four fibers and any terminating equipment (junction boxes). The fiber provided must be four fiber optic cable strands between the following locations, with all fiber diversely routed from one another (lists the four Subtasks). Question: For clarity, can the Government confirm the intent is to form a ring design that would accommodate the required diversity: Ashburn – Pentagon – Belvoir – Ashburn? | The Government's intent is to form a ring from Ashburn - Pentagon - Belvor - Ashburn. PWS Updated |
| 3 | RFP/PWS | Comment: Based on the requirement, it appears that this is a fiber only solution. Equipment is mentioned in the PWS, however, it appears to be related to delivering an end to end fiber solution and not Optical Transmission Equipment. Question: Can you confirm that this requirement is to deliver only tested fiber that meets the specifications of the RFP from end to end, along with the Operations and Maintenance of the fiber and that the Government will manage the transmission? | Confirm that this requirement is to deliver a fiber solution that meets the DISA FRS along with the O&M of the fiber. | |
| 4 | Attachment 3: Pricing Worksheet | Comment: In the pricing worksheet, Link Activations Circuit Transitions are included as cost items, however, this appears to be a fiber only requirement and does not include activation of transmission or reference any circuits to migrate. Question: Should these be included in pricing? | There are no customer circuits to migrate; this line item has been removed from the pricing template. | |
| 5 | PWS - Task Area 2 | Comment: In task area 2 of the PWS it states that “Contractor will be responsible for any power requirements at the commercial locations…” Question: Since the power requirements are dependent on what equipment is being installed, which is not stated in the PWS, can you clarify how much power needs to be procured from Equinix? | The sentence referencing power in Task 2 has been removed. | |
| 6 | Question: Will Contractor be expected to order cross-connects from Equinix to connect from Contractor’s FSDP to DISA’s equipment or will this be tasked to the cage owner? | The contractor will be expected to order the cross-connects from the Equinix to connect from their FDP to the FDP in the DISA cage. Added to PWS. | ||
| 7 | PWS | Section 6.2.5 | Comment: In Sec 6.2.5, the location 21715 Filigree Ct is listed as DC6, but is actually DC2. Question: Please clarify whether the correct site is DC6 or DC2. | DC2; PWS updated. |
| 8 | Question: Will site surveys be allowed prior to bid offer submittal to verify the requirements? | Surveys prior to proposal will be allowed at the vendors expense. | ||
| 9 | Question: Is GFE fiber available for the connection between the 2 Pentagon SDNs? If not, is it acceptable to install a new fiber cable inside the building to make the connection? | There will be a single SDN in the North Pop of the Pentagon; the requirements have been updated. | ||
| 10 | Question: Is the Government requesting dark fiber or lit services since there is no equipment requested as part of this RFP? | Dark Fiber | ||
| 11 | PWS | Page 2 | Comment: In the PWS on page 2, the purpose of the SOW states the PWS includes all services and supplies necessary to perform the objective, to include programmatic, engineering, and other technical services and the procurement of all necessary equipment and components. Question: Will the Government procure the end equipment in a separate solicitation? | The Government has procured and installed the MBOM. Attachment 1B has been removed. |
| 12 | Question: How many circuits will be transitioned onto the new fiber links? | This is a fiber only solution. No circuit transitions required. | ||
| 13 | PWS | Page 2; Task Area 2 | Comment: In task areas 2 on page 2, it states Contractor will be responsible for any power requirements at the commercial locations in order to make the system operational. Question: Will the Government remove this requirement since the provider is not responsible for supplying the fiber equipment ? | Yes, the statement has been removed. |
| 14 | Question: How will the SLAs apply for dark fiber leases since dark fiber availability is a bi-product of the equipment installed on the fibers to make them active? | Removed SLA requirement. | ||
| 15 | PWS | Section 6.1.2.1 | Comment: In section 6.1.2.1, the PWS states the CIP shall include a section that details the approach for implementing physical security. The Government requests the dark fibers to terminate at Government locations on Government equipment. Questions: Is the Government responsible for the physical security of the hardware on which the fibers terminate? Does the Government physical security plan encompass the outside plant of the fibers run between the A and Z locations per section 6.2.7.5? | The Government will be responsible for physical security of the hardware and OSP for A-Z locations but, the offeror will need to address in the CIP for the fiber. |
| 16 | PWS | Section 6.3.1 | Comment: In the 6.3.1 Maintenance plan, the Government requires 99.9 % SLA for the dark fibers availability. Question: How does the Government distinguish between the availability of the dark fiber versus the lit service once the lit fibers are handed over to the Government? Question: Does the Government require the Contractor to take over the responsibility of GFE hardware on the edge of the dark fibers? | Removed availability requirement from PWS. |
| 17 | PWS | Section 6.3.1 | Comment: In section 6.3.1, the Contractor shall have no active or passive monitoring capabilities on the OLA equipment. Question: Therefore, how does the Government require the Contractor to notify them within 10 minutes of the time the fiber failure occurs since the DISA DGOC must notify the Contractor of an outage in order for dispatch to occur? | Removed language from PWS. |
| 18 | Question: Does the Government require the Contractor to procure any colocation space from Equinix? | Not required. | ||
| 19 | PWS | Section 14.5 | Comment: In the PWS section 14.5, the embedded EPL worksheet does not open. Question: Is this form required since there is no equipment specified for this RFP? | Not required; removed from PWS. |
| 20 | SF1449 | Page 11 | On the SF1449, under Delivery, it shows a June 11, 2021 delivery date. Will the government update the projected date for delivery? | The delivery dates have been updated to a projected date of 31 Aug 22; however this date could change depending on the award date. |
| 21 | Attachment 3: Pricing Worksheet | Comment: On the pricing template there is only a location for Miscellaneous Installation Related Material. Question: If the SDN equipment procurment is a part of this soliciation will a new row be added or should we price it in the miscellaneous section? | Equipment is not included in this requirement. | |
| 22 | Question: Can you provide the span distance requirement for this link based on the |
optical equipment that will be used. Comment: This would be required to determine if
| any OLA locations are required based on the equipment and technology. Question (part 2): If an OLA site(s) are required, will the Government provide the hardware and installation since there is no equipment BOM listed in the requirement? | May not require an OLA . This should be part of the vendor's proposal. The Government will provide if required. | |||||
| 23 | PWS SF 1449 | PWS - Page 19 and SF 1449 Clauses - Page 65 | Comment: The Outage Credits described in the Clauses Incorporated By Full Text to the SF144 appear to conflict with the credit requirements described in the PWS Sec 8 – Incentives. Question: Please confirm which takes precedent. | Language updated in SF1449. | ||
| 24 | PWS | Section 8; Page 19 | Comment: PWS Sec 8 – Incentives references “Section H.” Question: Please clarify Section H of what document. | Removed reference to Section H. | ||
| 25 | RFP | Clauses Incorporated by Full Text 252.237-7023; Page 57 | Comment: The clause states that "The Mission-Essential Contractor Services Plan submitted by the Contractor, is incorporated in this contract." Submission of a Mission-Essential Contractor Services Plan is not listed as a deliverable in paragraph 11. Delivery Schedule of the PWS. Question: When is the contractor required to submit the Mission-Essential Contractor Services Plan? | The plan should be submitted with the offeror's proposal. Language added in SF1449. | ||
| 26 | RFP | |||||
| PWS | RFP - Page 60; Volume II - Technical/Management PWS - Page 20-21; Section 11. Delivery Schedule | Comment: The RFP list a Section as "All other aspects for the PWS*" At the *, there is a statement the "*Draft deliverables may be submitted as attachments to the Technical Volume and do not count towards the 40 page limitation." Question: Will the Government provide additional guidance on what they desire to be submitted in the "All other aspects of the PWS" section? Does this include "Draft deliverables? | In the Technical/Management volume, address your proposed approach to meeting or exceeding |
the minimum performance or capability requirements of each technical/management subfactor, as well as the risks in your proposed approach in terms of technical/performance, cost, and/or schedule.
Language updated to include draft deliverables.
| 27 | RFP | |||||
| PWS | RFP - Page 60; Volume II - Technical/Management PWS - Page 20-21; Section 11. Delivery Schedule | Comment: The RFP states that "*Draft deliverables may be submitted as attachments to the Technical Volume and do not count towards the 40 page limitation." There are a number of Deliverables in the table in Section 11. Delivery Schedule of the PWS the have a "Due Date" of "Draft with proposal . . " The use of "may" in the RFP suggests that the submission of draft deliverables with the excpetion of the CIP, is optional. Question: Will the Government specify which draft deliverables should be include as part of the proposal submission? | All of the draft deliverables with a "Draft with proposal" due date in the PWS shall be included with the proposal submission. The deliverables may be submitted as attachments to the Technical Volume. | |||
| 28 | RFP | Volume III- Price and Volume IV - Contract Documentation; Page 70-71 | Comment: Volume III instructions include the submission of "Attachment 3, CLIN Pricing Worksheet". Volume IV instructions (D).2 state "2. You must provide completed pricing information in the CLIN spreadsheet." Question: Will the Government please confirm that the CLIN Spreadsheet is to be submitted in both Volumes III and IV? | Language updated in SF1449. | ||
| 29 | RFP | Clauses Incorporated by Full Text; Page 14 | Comment: Several of the Clauses Incorporated by Full Text other than FAR 52.212-3 Alt I have fill-ins, but the RFP Instructions do not direct offerors to complete and submit the clauses other than FAR 52.212-3 Alt I with the proposal. Question: Will the Government confirm that offerors are not required to submit completed Clauses Incorporated by Full Text other than FAR 52.212-3 Alt I with their proposals? | Language added in SF1449. Offerors must submit completed Clauses Incorporated by Full Text with their proposal. Also see FAR 52.252-1, RFP page 45. | ||
| 30 | PWS |
RFP
| RFP | PWS 15. Section 508 Accessibility Standards, Page 26-27; RFP Addendum to 52.212-2(a), Evaluation-Commercial Items, Page 72-73; Addendum to 52.212-1(b), Submission of Offers, Page 68 | Comment: Both the RFP and PWS provide information regarding 508 compliance, with the RFP stating that Seciton 508 complaince does not count against page count. Question: 1. Will the Government provide guidance on the 508 compliance information it would like submitted with the proposal beyond what is listed in Section 15 of the PWS. 2. In which Volume would the Government like 508 compliance documentation? | Please confirm Section 508 compliance in the Technical/Management Volume. | |||
| 31 | PWS | |||||
| RFP | PWS Section 6. Performance Requirements, Task Area - 4: Fiber Relocation, Page 3; RFP Addendum to 52.212-2(a), Evaluation-Commercial Items, Page 73 | Comment: Fiber Relocation is listed as one of the four task areas under Peformance Requirements, but is not listed as one of the areas to be evaluated in the RFP. Question: Does the Government require offerors to address Fiber Relocation? If so, where would the Goverment like to see it addressed? | Offerors do not need to address Fiber Relocation, but rather made aware it may become a future requirement which would be negotiated and added by contract modification. Relocation will not be evaluated with this solicitation. Fiber relocation will be executed as required. | |||
| 32 | PWS | Section 4. Objectives, Page 1 | Comment: "along with the in-stallation of various telecommunications equipment (as required) at the facilities." Question: Will a MBOM for the required equipment be provided for procurement under this contract? | There is no MBOM to be procured for this effort. | ||
| 33 | PWS | Section 4. Objectives, Page 1 | Comment: "along with the in-stallation of various telecommunications equipment (as required) at the facilities." Question: If the required equipment is being procured under a seperate contract vehicle i.e SEWP, is there an estimated date for the procurement to be completed? Will the Government provide a copy of the MBOM so that we can best estimate the level of effort required for installation? | The MBOM has been procurred and is already installed at the Equnix, Belvoir and Pentagon locations. | ||
| 34 | PWS | Section 6. Performance Requirements, Task Area - 2: Implementation of a new 100G Fiber Segment, Page 6 | Comment: From 607 Army Navy Drive Washington, DC 20310-3060 Room BC771, the route must connect to 607 Army Navy Drive Washington, DC 20310-3060 Room 1B488. Question: Can the government confirm if there is existing ISP fiber in place between Room BC771 and Room 1B488 that can be used for this solution? If there is nothing available will a site survey be allowed to determine the run length and level of effort to install cable between these two rooms? | The requirement was re-written as there will only be a SDN in BC771. | ||
| 35 | Task Area - 4: Fiber Relocation | Comment: Fiber relocation cannot be adequately defined for FFP pricing. Each fiber relocation situation is unique, so costs vary depending on how extensive a solution is needed for engineering and construction. For Task Areas 1, 2, and 3, there are evaluated "Subfactors", and corresponding PWS requirements paragraphs. For Task Area 4, there is no evaluated "Subfactor", and no PWS requirements paragraph. Question: How does the Government intend to address fiber relocation and associated undefined costs? | ||||
| Fiber Relocation will not be evaluated with this solicitation. Should the need arise, the requirement would be negotiated and added to the contract via modification. | ||||||
| 36 | PWS | OLA Maintenance (PWS 6.3.2, Table 6.3.2, 7) | Comment: Link 42 requirements do not seem to include Optical Level Attenuators (OLA). |
Question: Will the Government please define where OLA will be used for Link 42, or should the requirement be removed from the PWS?
| The distances are of such that an OLA may not be required. Address in the offeror proposal. | |||
| 37 | PWS | Co-location "Colo" Facility (PWS Task Area-3, Table 6.3.2, 7, 12.4) | Comment: Link 42 requirements do not seem to include Colo Facilities. |
Question: Will the Government please specify what locations are Colo Facilities for Link 42, or should the requirement be removed from the PWS?
| 21721 Filigree Court Ashburn, VA 20147 is the Ashburn Equinix or Colocation facility identified in Table - 1. | |||||
| 38 | Clauses | Comment: FAR 52.219-14, Limitations on Subcontracting (MAR 2020) incorporated by reference. This clause includes a subclause (subclause (d)) for contract set-aside for small business that should indicate whether the limitations on subcontracting apply to (1) By the end of the base term of the contract and then by the end of each subsequent option period or (2) By the end of the performance period for each order issued under the contract. Since the clause is incorporated by reference and therefore no indication is made as to which subclause option applies, we assume that the limitation applies to the entire performance period. Question: (1) Will the Government please confirm our assumption that the ? | |||
| (2) As part of the Technical Acceptability evaluation, will the Government be ensuring each offeror’s compliance with FAR 52.219-14 as presented in each offeror’s Technical and/or Price Proposal? | Clause updated. The Government will ensure each offeror's compliance with FAR 52.219-14 Limitations on Subcontracting (DEVIATION 2020-O0008). | ||||
| 39 | Questions-Answers | Answer 11 | Question: With the equipment being Government installed already, will the supplier still need to fiber the intershelf cabling to connect the new degree to existing degrees and client cards or is this already complete? | Yes | |
| 40 | Questions-Answers | Answer 11 | Question: If inter shelf / system cabling is required, will there also be a requirement to extend the tie fibers from GFE installed client cards to DEMARC fiber panels? | No | |
| 41 | Questions-Answers | Answer 03 | Question: Are hardware maintence callouts for the SDN equipment a part of the O&M of this contract? | No | |
| 42 | Questions-Answers | Answer 04 | Question: Link activation is still in the price template file. Is it assumed the supplier will have smart hands on site during activation with the DGOC to assist and perform the end to end BERT testing? | Yes | |
| 43 | PWS | Section 6.2 Performance Requirements, Task Area - 2: Implementation of a new 100G Fiber Segment | Comment: "The fiber provided must be four-fiber optic cable strands that will form a ring between the follow-ing locations, with all fiber diversely routed from one another" Question: Please verify that the request is for each span to have 2 pair (4 fibers) between each identified site in a ring configuration. | The requirement is for each span to have 2 pairs (4 fibers). | |
| 44 | PWS | Section 6.2.4 Performance Requirements, Task Area - 2: Implementation of a new 100G Fiber Segment, Subtask 4 | Comment: "From 8575 John J Kingman RD Ft Belvoir, VA 22060-5123, the route must connect to DC11 21721 Filigree Court Ashburn, VA 20147" Question: Since the first requested span is from DC2 to DC11, it would appear that the span coming back to Ashburn from Ft Belvoir should land at DC2 in order to create a ring. Please verify. | Confirmed; PWS updated. | |
| 45 | RFP | Question: Will the Government consider a two-week extension (Aug.13) to Link 42 so that we can incorporate the new material into our solution? | The proposal due date has not been extended. |
File details come from the government source that posted it. Updated .