Exhibit 6 Questions and Answers AMD 0002 12Sep24.xlsx
XLSX spreadsheet 23 KB Posted
- Attached to
- Commercial Ethernet Gateway (CEG) Hawaii
- Solicitation number
- HC101924R0004
- Issued by
-
Defense Information Systems Agency
About this file
This document contains a set of questions and answers related to a federal contract opportunity for the Commercial Ethernet Gateway (CEG) Hawaii initiative issued by the Defense Information Systems Agency (DISA). The key details include:
The contract will be an indefinite-delivery/indefinite-quantity (ID/IQ) with a 5-year base period and two option periods to migrate to Ethernet-based services and reduce telecommunications costs. The solicitation is being evaluated using the lowest price technically acceptable (LPTA) method. Relevant details are provided on the contract period of performance, NAICS code, and proposal due dates. The questions cover various aspects of the solicitation, including the definition of the base period, pricing, site survey requirements, diversity requirements, accessibility considerations, and the process for handling contract cancellation. The government provides clarifications and updates to the solicitation based on the questions.
View the file
Other files
Show all 21
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
Q&A
| RFP Page | RFP Section/ Paragraph | CLIN/ Clause/Appendix/Attachment/Other | Questions/Comments/Recommendations | Government Reponse | ||
| 1 | General | Question: How does the Government define the base period for year one. Does year one end September 30, 2025 or 12 months after the award date. | 1 year from the effective date of the award. | |||
| 2 | Attachment A | Rows 34 and 35 | Question: In attachment A Row 34 and 35 are both HI-S29. Should row 34 be HI-S28, please clarify | This reference is from the DRAFT solicitation Attachment A. Please be sure to download all the Attachments and Exhibits from the solicitation and solicitation amendments. All previous versions are not valid. | ||
| 3 | PWS | 6.1.1.1 | Yes | Question: If an additional gateway is required, for reasons of growth, expansion or replacement, will the process to build, install and configure follow the current path outlined in 6.1.1.1 and will an CLIN be provided and negotiated at that time for the gateway and assocaited access circuits? | Yes, If additional gateways are required the process for installation and configuration will follow the same design layed out in the PWS section 6.1.1.1. Any additional gateway sites will be negotiated and a new CLIN will be created. | |
| 4 | PWS - 174 | 14 | 14.h | Question: Both 800-53 Federal Systems and 1253 CNSS are baseline citations for accredited US Government systems. For a supply chain risk management plan (SCRM), are the controls different for industry partners. | Any industry partner doing business with the government is expected to implement the same controls outlined in NIST SP 800-53 and 1253 CNSS. | |
| 5 | PWS - 168 | 7 | Question: For a supply chain risk management plan can the government clarify the time between award date and contract receive date; at which point does the 30 days response time begin? | Award date and the date that the Government will transmit the contract to the Awardee will be the same date. | ||
| 6 | Exhibit 1 - Pricing | Question: Are the TBN CLIN's and infrastructure CLIN's part of the $25M max contract value | Yes | |||
| 7 | Attachment A | Question: Can the Government assist with escalating a request to perform a site survey for HI-35 and HI-36 so that a full estimation of costs and build out can be identified | We were unable to identify a point of contact to escalate this request. | |||
| 8 | Attachment A | Question: Can the government confirm the map coordinates for site HI-21 and update on the site list. | Attachment A, HI-S20 and HI-S21 LAT/LONG has been updated to 21.2117, 157.5539 | |||
| 9 | PWS - 174 | 14 | 14.h | Question: We understand that the 20 page limit for the supply chain risk management plan, does not include appendices and similar artifacts and we will submitting as separate items. | Acknowledged | |
| 10 | General | Question: For future growth and build out, Can the government comment, on a high level, what future task orders will look like in terms of circuit size. | Task Order 1 for HI-G1 and HI-G2 are projected to be awarded immediately upon award of Contract. Task Order 2 for HI-S1 though HI-S11 will be awarded soon after within the first year. Any projected circuits beyond those are currently unknown but will be majority 1GB and 10GB, but more usage of this contract is expected going into the future. | |||
| 11 | 146 | ADDENDUM TO 52.212-1(b)(12)(ix)(D)(9) | Exhibit 4 DISA OSBP Subcontracting Plan Checklist | As with prior solicitations, are other than small businesses (i.e., large businesses) that are submitting an approved commercial plan not required to insert dollar values and percentages in items 1 and 2 of the DISA Subcontracting Review Checklist (exhibit 4)? | Contractors submitting approved commercial plans are not required to insert the requested dollars and percentages. | |
| 12 | 145; and, 134 | 52.212-1(b)(12)(ix)(D)6; and, 252.237-7024 | Representations, Certifications, and other Statements of Offerors; and, NOTICE OF CONTINUATION OF ESSENTIAL CONTRACTOR SERVICES (OCT 2010) | Will the government clarify whether the Mission-Essential Contractor Services Plan referred to in 6) Representations, Certifications, and other Statements of Offerors; and the Continuation of Essential Contractor Services Plan referred to in 252.237-7024 NOTICE OF CONTINUATION OF ESSENTIAL CONTRACTOR SERVICES (OCT 2010) are the same plan. | Confirmed to be the same. Removing that reference in Addendum to 52.212-1(b)(12)((ix)(D) Paragraph 6) Representations, Certifications, and other Statements of Offerors and moving it to Paragraph 11) Continuation of Essential Contractor Services. In that reference; renaming from "Mission-Essential Contractor Services Plan" to "Continuation of Essential Contractor Services Plan", also updated the reference from "DFARS 252-237-7024" to "DFARS 252.237-7024" | |
| 13 | Attachment A | Customer Access Site List | Will the government please, confirm Attachment A requires only circuit diversity and does not require physical diversity for : HI-S5, HI-S31, HI-S44 and HI-S47. | We expect physical diversity, but would need to be confirmed/determined by the Mission Partner customer upon Task Order creation. We adjusted all Diversity references in Exhibit 1 Price Schedule to reflect TBN (To Be Negotiated) at the time of task order creation when more details can be provided about the diversity requirements. | ||
| 14 | Exhibit 1 Price Schedule Tab CLINS X001-X008 - HI Circuits | Reference to: Exhibit 1 price schedule, CLINS X001-x008 tab, row 6 & 8 column I | ||||
| Should the two cells read “100GB EVC service” as it currently reads “100GB EVC installation”? | Confirmed that this is incorrect. This has been corrected on Exhibit 1 Rev1 as "CEG Gateway Building" and "CEG Gateway Service". | |||||
| 15 | PWS 6.2.2.4 c.ii | Will the government provide separate entrances where 50 ft of diversity is a requirement? | If the sites require this they will provide seperate entrances/exits to their facilities. We also changed PWS 6.2.2.4.c.ii reference from "50 feet" to "50 meters". | |||
| 16 | SF 1449 | Proposal Due Date | Will the government grant a 30 day extension from the date the questions are answered. | Solicitation will be extended to September 23, 2024, 1000 HST. | ||
| 17 | Exhibit 4 | DISA Subcontracting Plan Checklist | The solicitation states the subcontracting plan--at a minimum--shall address the elements set forth in | |||
| FAR Clause 52-219-9(d)(1) through (15), which states goals shall also be expressed in terms of percentage of total contract dollars. In addition, Exhibit 4 DISA Subcontracting Plan Checklist contains a data field for the Total Contract Price. What is the Total Contract Price or Total Contract Dollars for DISA CEG Expansion (Region 8)? | The Total Contract Price will be the Evaluated Price Total (Exhibit 1, CLIN Summary Tab, Cell F32) | |||||
| 18 | General | Question: Can the government provide an OCI template. | We don't have a template to provide. | |||
| 19 | RFP Page 1 | SF1449 | N/A | In order to provide an appropriate response for HC101924R0004 in a timely manner as possible while providing the lowest price technically acceptable (LPTA) offer, Offeror requests an extension for two weeks from the receipt of answers to questions. This will assist Offeror in ensuring the site list has been appropriately solutioned and all competitors have been provided ample time to meet DISA requirements in a competitive LPTA evaluation. | Solicitation will be extended to September 23, 2024, 1000 HST. | |
| 20 | General | N/A | N/A | Will the Government accept WAVE vs. Native Ethernet for site access? | According to Attachment B CEG Design, only Native Ethernet for site access. | |
| 21 | General | N/A | N/A | Carrier class Metro Ethernet Forum (MEF) 3.0 network is required to support native 100G ethernet. Does the Government require native 100G ethernet or will the Government accept Wave access? | According to Attachment B CEG Design, only Native Ethernet. | |
| 22 | General | N/A | N/A | Is a temporary solution allowed while infrastructure is being built out? | What sort of temporarly solution? Need more details on what is being asked here. | |
| 23 | RFP Page 163 | 6.2.2.3 | N/A | The government has not stipulated the number of ports required for the aggregation device. Please provide the number of ports required. | The ports required will be outlined in the Attachment B CEG Design document. The current minimum requirement is 8 ports. | |
| 24 | RFP Page 163 | 6.2.2.3 | N/A | Will the government provide space and power for the aggregation device at the site? | Yes, the government will provide space an power at government facilities. | |
| 25 | RFP Page 166 | 6.65 | N/A | Circuit cessation in 30 days. How much of the NRC, if any, is recouped, and what is the Process to recoup? Will Carrier be reimbursed for disconnect in services in less than one-year term? | Any Task Order Cancellation would be TBN (To Be Negotiated) on CLIN X020. | |
| 26 | RFP Page 166 | 6.65 | N/A | Circuit cessation in 30 days. Will Carrier be able to recover costs for circuit orders canceled prior to installation | Any Task Order Cancellation would be TBN (To Be Negotiated) on CLIN X020. | |
| 27 | Attachment A, Page 1 | N/A | Attachment A | The government did not state what hub locations the customer access sites should terminate at. Will the government please provide this detail. | This has not been determined. Typically the route would be to the closest hub, but it will be up to the customer and recommendation of the vendor which path or Hub will be best for circuit performance. | |
| 28 | Attachment A, Page 1 | N/A | Attachment A | Pricing cannot be completed without accurate addresses from the Government. Many of the addresses are not complete. Others are list as crossroads. LAT/LONG was provided but it is still not enough to deliver the required service. Will the government please provide accurate addresses for the sites. | These addresses are the best we can identify at this point in time. You may provide feedback and details on missing information for specific circuits/locations that you don’t have enough information on to price within 2 business days of this Q&A posting, for consideration for removal from Attachment A and Exhibit 1 for the purpose of this solicitation. | |
| 29 | Attachment A, Page 1 | N/A | Attachment A | There is no CLIN for diverse service. Will requests for diverse service be priced under the appropriate "Negotiated, TBN" CLINS for that service? | Any unidentified circuits not listed in Attachment A will be negotiated into Attachment A and Exhibit 1 in the future when identified. | |
| 30 | Attachment A | Customer Access Site List | Will the government please provide the type of diversity required (ie. gateway or physical) for the following site reference numbers that show "(diverse route…)" in the address: HI-S5, HI-S7, HI-S25, HI-S36, HI-S47 and HI-S53 | We expect physical diversity, but would need to be confirmed/determined by the Mission Partner customer upon Task Order creation. We adjusted all Diversity references in Exhibit 1 Price Schedule to reflect TBN (To Be Negotiated) at the time of task order creation when more details can be provided about the diversity requirements. | ||
| 31 | 156 | 6.1.1.2 | Paragraph 4 | GFE - Is the use of GFE allowable from a current Commercial Network Demarcation to end point locations if Comercial fiber does not DEMARC in the end point location? | Vendor would deliver to the commercial DEMARC and would do the extension to the end point, but no GFE will be required on this contract. If site does not allow vendor to do a commercial extension, the site will be responsible for the extension to the endpoint. | |
| 32 | 156 | 6.1.1.2 | Paragraph 4 | GFE - Who would maintain O&M on the GFE is allowable | No GFE will be required on this contract. | |
| 33 | 162 | 6.2.2.4 | Paragraph C. ii. | Diversity - What is the government expecting from the bidder if there is no existing diverse infrastructure (e.g., conduits and pathways) on base or to buildings where path diversity is required? | TBN (To Be Negotiated), bidder should be able to provide build and cost associated to meet diversity requirements. | |
| 34 | 162 | 6.2.2.4 | Paragraph C. ii. | Diversity - Will the government be able show the possible diverse infrastructure (e.g., conduits and pathways) on base and to the buildings upon request? | At this time that information has not been provided by site. The vendor will be able to leverage task order 6.5.5 (Onsite site surveys) to conduct infrastructure survey. | |
| 35 | 162 | 6.2.2.4 | Paragraph C. i. | Diversity - For locations with multiple nodes at a location (S50, S51, S52), do they require physical diversity leaving the building and /or also on and leaving the base? | We expect physical diversity, but would need to be confirmed/determined by the Mission Partner customer upon Task Order creation. We adjusted all Diversity references in Exhibit 1 Price Schedule to reflect TBN (To Be Negotiated) at the time of task order creation when more details can be provided about the diversity requirements. | |
| 36 | 162 | 6.2.2.4 | Paragraph C. i. | Diversity - Explain in detail the level of diversity where required (e.g, S45 and S46 must be completely physically diverse from the last location to where)? | We expect physical diversity, but would need to be confirmed/determined by the Mission Partner customer upon Task Order creation. We adjusted all Diversity references in Exhibit 1 Price Schedule to reflect TBN (To Be Negotiated) at the time of task order creation when more details can be provided about the diversity requirements. | |
| 37 | Q&A Question #4 follow on question | Under DFAR 252.204-7012, industry is required to implement the standards in NIST 800-171, Safeguarding Covered Defense Information and Cyber Incident Reporting. |
CNSS 1253 and NIST 800-53 are for Federal Information Systems. Adhering to these standards represents an increase in security standards mandated by the DFAR. As a result, is a request approval for an equitable adjustment for expenditures related to an increase in security standards and a reasonable extension for 30 days.
| Provide clarification to the response to the question or provides the extension based on the need to adhere to 800-53. | SCRM Plan is required 30-90 days after contract award (it is not a proposal requirement, no extension will be provided for proposals). There will be no equitable adjustment, this is a known requirement of the contract and should be priced accordingly. | ||
| 38 | Q&A Question #28 follow on question | CEG-HI Sites that Require Location Correction or Removal from solicitation Attachment A: HI-S1, HI-S2, HI-S8, HI-S16, HI-S17, HI-S21, HI-S22. HI-S23, HI-S43, HI-S44, HI-S45, & HI-S46. |
Will the Government please provide specific, complete addresses for the Sites listed in the attached or remove from Solicitation Attachment A. The attached list only includes CLINS of Sites that are not clear. Please also ensure that the Latitude/Longitude coordinates are correct (e.g., some existing Latitude/Longitude coordinates do not indicate specific buildings). With the exception to HI-S21 and HI-S22 (see below), LAT/LONG and addresses were verified upon generation of Attachment A. The Governmnet has provided as much information as possible on the list of sites and believes there is enough information being provided to vendors for pricing of the circuit locations.
Upon further review, Attachment A and Exhibit 1 has been updated to remove HI-S20, HI-S21, and HI-S22.
39 Q&A Questions #25 & 26 follow on questions Could you please provide more details on what aspects of Non-Recurring Charges (NRC) will be subject to negotiation under CLIN X020?
Are there any predefined guidelines or limitations that will influence the negotiation process for recouping these?
With respect to the early termination of services (before the one-year term), could you clarify how the negotiation process will address potential reimbursements?
| Are there any standard clauses or precedents within CLIN X020 that would guide this negotiation? | Please see PWS paragraph 6.6.6, Task Order Cancellation, for details. | ||
| 40 | General | We are seeking clarification on CUI markings found within the solicitation. The solicitation itself was not marked as CUI (no cover page, no header/footer markings). However, there are paragraphs that are portion marked Controlled Unclassified Information (“CUI”). |
Examples of these makings (all marked as CUI) are on the following sections of Amendment001: Page 16, Section 4, Page 18, Figure 5-1 and Scope; Page 23, Section 6.2, page 24, 6.2.1.1, Page 23, section 6.2 ), page 24, Section 6.2.1.1, Page 26, Section 6.2.2.4, and page 31, section 7.
Would the Government please confirm that these sections are appropriately marked (CUI), or reissue the RFP with revisions to the markings as necessary? This clarification is important so we can mark our response properly. If any of the sections remain CUI, then our response to those sections will also be CUI, and any documents with CUI sections will be marked CUI overall. That would require that our proposal be submitted either as encrypted (if submitting via email), or submitted using DoD Safe. Would the Government please revise the solicitation to include instructions for submitting CUI proposal Documents?
As a final note, it may be necessary for the Government to remove CUI documents from Sam.gov. PWS has been removed as additional text from the solicitation and added to the solicitation as Exhibit 0, marked CUI. Updated addendum instructions on proposal submission to sent via encrypted e-mail marked CUI. All previous solicitations posted on SAM.gov prior to amendment 002 have been marked as controlled access.
File details come from the government source that posted it. Updated .