L1 - Solicitation Questions and Answers - Round 1 Government Response.xlsx
XLSX spreadsheet 55 KB Posted
- Attached to
- Defense Research Engineering Network - DREN4
- Solicitation number
- HC101319R0006
- Issued by
-
Defense Information Systems Agency
About this file
This is a request for proposal for the Defense Research Engineering Network (DREN4) program. Proposals are due no later than January 27, 2020, with questions due by December 16, 2019. The Defense Information Systems Agency is seeking network services including transport, security, operations, and management to support research and collaboration activities. The contractor will provide services on a 24/7 basis across approximately 60 sites in the continental U.S. and overseas locations. Pricing terms and evaluation criteria are detailed in attachments provided upon request to U.S. nationals only.
View the file
Other files
Show all 48
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
Instructions
| Q&A INSTRUCTIONS: The purpose of these specific instructions is to expedite the process of answering questions. Please do not change the format of this document. |
| Complete the spreadsheet tab below named "Q&A" with all questions, comments, and recommendations about the RFP. Examples provided in the spreadsheet. **Please delete the examples before submitting your questions. |
COLUMN A: Complete the "Page" column. This is the page number from the RFP located in the upper right hand corner of the page. Do not include the total page number. Enter only the page number where the topic begins.
COLUMN B: Complete the "Section/Paragraph" column with the applicable section and paragraph number (if applicable) of the RFP. For example: B2, C, or L5.1.2. For a section and paragraph number reference do not place a dot between the letter and the first number. Additional subparagraph references should be separated with a dot regardless of the format in the RFP, for example, L5.1.2.a. Do not including any other extraneous identifiers or other information other then instructed here. If the reference is to a CLIN, Clause, Appendix, or Attachment etc. the entry goes in the next column. At a minimum you will always insert at least the Section letter A through J in this column.
COLUMN C: Complete the "CLIN/Clause/Other" column. Insert the CLIN, Clause, Provision, Appendix, or Attachment number. For example: CLIN 0001, 52.217-8, Appendix A, or Attachment L3. Insert the section letter only in the Column B. This column will be completed only when there is not a more precise RFP reference number. NOTES: CLINs are in Section B. Most sections contain clauses so ensure you reference the correct section.
COLUMN D: Complete the Questions/Comments/Recommendations column. Start the question by referencing the topic. This may help the sort process. For example: Minimum Qualifications Checklist or Performance Area 10. Then insert the question or comment.
Issues must be submitted to the Contracting Officer and Contract Specialist listed in the FBO Announcement.
Q&A
| Question Number | RFP Page | RFP Section/ Paragraph | CLIN/ Clause/Appendix/Attachment/Other | Questions/Comments/Recommendations | Government Response | |
| 1 | 28 | C6.1.3.6.3 | If the Government requests a retest, how much time does the contractor have to set up and perform this retest? Contractor recommends that interval should allow dispatch of test equipment and tests are not overlapping. Retesting of this nature is service disruptive. | Amendment_0001 modifies PWS paragraphs 6.1.3.6.3 and 6.1.3.6.5 to indicate that any retest after IPC shall be performed within 10 days of the Government’s request. | ||
| 2 | 28 | C6.1.3.6.3 | Is simultaneous testing required? | As stated in the PWS (adjusted in Amendment_0001) paragraph 6.1.3.6.3, "Pairwise TCP Tests (6.1.3.6.2) shall be performed simultaneously between all pairs of nodes to achieve this demonstration." This indicates that all nodes must be involved and that the testing is performed simultaneously. | ||
| 3 | 28 | C6.1.3.6.4 | If the Government requests a retest, how much time does the contractor have to set up and perform this retest? | PWS paragraph 6.1.3.6.4 does not have a requirement for repeated tests. Amendment_0001 modifies PWS paragraphs 6.1.3.6.3 and 6.1.3.6.5 to indicate any retest after IPC shall be performed within 10 days of the Government’s request. | ||
| 4 | 29 | C6.1.3.7 | In reference to declaration of an outage due to degradation, which party is responsible for making the declaration? | An "Outage" exists if any of the required service parameters for a DREN Node is not within the requirements specified in the PWS. Reducing an Outage to degraded status is solely at the discretion decision of the Government. The Contracting Officer will make such a declaration. | ||
| 5 | 73 | C6.5.2.3 | Re: "The time the change is completed is only when proper the requestor validates operation of the Change Request." This wording would seem to hold the contractor responsible for delays caused by the requestor. Recommend wording like "The time the change is completed is only when the Contractor completes the change and informs the requestor, who subsequently validates operation of the Change Request." | The referenced section is PWS paragaph 6.5.2 (paragraph three). Amendment_0001 clarifies the section. Any delay by the Government (time to respond validating the change was successful or not) does not apply toward the time to accomplish the requirement. | ||
| 6 | 79 | C6.5.5 | To help offerors size the level of effort, can the Government provide any estimate of the quantity and types of anticipated calls to the Help Desk? | The quantity and types of calls to the DREN Help Desk are affected by numerous factors, including the reliability of the Wide Area Network service. The number of contacts has varied throughout DREN's history. Over the last 13 months, there has been an average of 200 contacts per month. This number should not be relied upon for future design. DREN does not have detailed information on types of calls. | ||
| 7 | 81 | C6.5.5.1.1 | Are automated calls acceptable for security outage notation's? | Automated telephone calls for security outage notifications will not fully meet the Government’s requirement. Such calls must be initiated by a human to confirm that these notifications are received and acknowledged by appropriate point(s) of contact. | ||
| 8 | 83 | C6.5.5.1.4 | Re: "Subscriber POCs shall advise the DREN NOC on all scheduled maintenance events that could affect a DREN Node. At a minimum, the DREN site POC shall provide the following information:" These "shall "statements are requirements on the Subscribers, not the contractor. Recommend rewording to convey that Help Desk/NOC should expect the listed information from the Subscriber POC. | Amendment_0001 has modified PWS paragraph 6.5.5.1.4 replacing "shall" with "will" as appropriate. | ||
| 9 | 84 | C6.5.6 | Re: "The Contractor shall resolve/correct all reported and non-reported problems affecting the DREN Service as specified in this PWS…" Is it correct to conclude that any problems that do not affect DREN service (e.g., because of redundancy) are outside of the scope of the PWS section? | Yes, it is correct. "Problems affecting the DREN Service" indicates that anything which does NOT affect DREN Service does NOT require resolution nor correction. | ||
| 10 | 102 | C6.5.14 | To help offerors size the level of effort, can the Government provide any estimate of the frequency and quantity of anticipated updates to DNS? | The Government is unable to provide an estimate of the frequency and quantity of updates to DNS. DREN.NET Domain Name Service provides naming for all addresses for network-based resources (all router interfaces, NOC systems, etc). Changes to the DNS are usually related to the addition of new equipment interfaces or NOC systems, provided the conventions and implementation of current entries are correct. DREN.NET does not cover DREN subscriber/user DNS entries. | ||
| 11 | 5 | C6 | How many Government users will there be of the online portal? | The "online portal" is also referred to as the "Dynamic Data Site" (PWS paragraph 6.5.9.1). Currently, the total number of accounts is approximately 1000. Typically 5-10 accounts are accessing the system at any point in time. There is no guarantee these numbers will be the same for DREN4. | ||
| 12 | 90 | C6.5.9.1 | How many Government users will there be of the Dynamic Data Site? | The "online portal" is also referred to as the "Dynamic Data Site" (PWS paragraph 6.5.9.1). Currently, the total number of accounts is approximately 1000. Typically 5-10 accounts are accessing the system at any point in time. There is no guarantee these numbers will be the same for DREN4. | ||
| 13 | Pricing Table | all tabs | Are all prices to be listed in the Pricing table to be reflective of applicable Taxes, fees & surcharges for CONUS & Future sites which are inclusive of International sites? | All prices shall include all applicable taxes, fees and surcharges for current and future sites, CONUS and OCONUS. | ||
| 14 | 16 | 6.1.2.8 | Best practice is to use non-public addresses for management communications? May private addressing be used for a Management VLAN? | No, private addressing may not be used for a Management VLAN, (See PWS paragraph 6.1.2.8). "Private address space (RFC1918), [or] Unique Local Addresses (ULA) ... shall not be used on any IP networks." Global Unicast Addresses (GUA) will be assigned by the Government for management networks. Amendment_0001 modifies the PWS to identify ULA as not permissible. | ||
| 15 | 5 | 6.1 | For RMF considerations, please confirm that the security boundary is SDP provided devices, the DCN and DXP infrastructure. NOC infrastructure if shared would be outside the security boundary and defined as an interface to the security boundary. | The DREN4 NOC and Help Desk, as described in PWS paragraph 6.5.5, is within the security boundary and must be accredited in accordance with RMF requirements enumerated in PWS paragraph 6.3.1. Where there is any sharing of NOC infrastructure, DREN4 components of the NOC must be sufficiently separated in order to meet all RMF and associated security requirements. | ||
| 16 | 56 | 6.3.3 | Please confirm that in the case of DOS attack mitigation, if the closest security component to the source, and it is government furnished, the contractor expects DREN to take the mitigating action. | Responding to cyber-attacks such as DoS and DDoS is a shared responsibility. While the Government may implement protections in the Security Gateways (PWS paragraph 6.1.2.9.5) or other components managed by the Government, the Contractor is required to facilitate attack mitigation through application of protections in the components it provides. Blocking of traffic through manual or automated application of an ACL in a router is such a mechanism. Rate limiting of particular flows is another mechanism. If such attacks cause the network to fail to meet requirements, the Contractor shall use such mechanisms, in close coordination with the Government, to quickly respond and restore network performance within requirements. | ||
| 17 | 8 | 6.0.2 | "All deliverable materials and documents under this PWS shall be the property of the Government. All materials and documents provided online shall be available for download and unrestricted use by the Government at no additional cost " | |||
| Please confirm that infrastructure providing the service is not considered materials and not to be owned by the government. | The deliverable materials and documents for this contract are listed in PWS paragraph 11., DELIVERABLES. | |||||
| 18 | 3 | 5.1 | "The corresponding network traffic to support these HPC and distributed collaborative environment capabilities is projected to require constant increases in bandwidth throughout the life of the contract." Section IV. Rationale provided the anticipated number of sites and when it will require upgrades for current and future SDP and DXP sites but didn't specify the site addresses? Can the Government provide the specific site addresses? | The "SDP and DXP Locations" spreadsheet, which is available from the KO/CS via encrypted email upon request, contains addresses except at certain DXP locations and future sites where the Government is unable to provide them at this time. | ||
| 19 | 59 | 6.4.1.1 | Four positions for key designated personnel. Where does the Government expect the key personnel base location to be? Please confirm that the minimum normal business hours for the key personnel shall be Monday through Friday from 8:00 AM to 5:00 PM Eastern Time (ET). | There is no specific location requirement for key personnel identified in the PWS. Key Personnel must be able to meet all requirements in the PWS, including appropriate security considerations to meet user access requirements for DREN. Key personnel in the PMO are expected to be available during normal business hours as stated in PWS paragraph 6.4.1.2. "The minimum normal business hours for the PMO shall be Monday through Friday from 8:00 AM to 5:00 PM Eastern Time (ET)." | ||
| 20 | 60 | 6.4.1.2 | "The PMO and NOC shall have video-teleconferencing (VTC) capabilities fully interoperable with VTC capabilities used by DREN" What is the VTC system used by DREN PMO? | The DREN PMO uses Cisco IP-based endpoints and conference/bridge infrastructure that supports both the SIP and H.323 standards. The Government intends to place three desktop and one small room endpoints for use by the Contractor. | ||
| 21 | 21 | 6.1.2.11.2.2 | Where in the Section B Pricing Schedule will include pricing for outreach transport? Is included as part of the ITS? | Outreach transport is included as part of the ITS pricing. | ||
| 22 | 32 | 6.2.0.3 | Table 6.1 Line rates depicts "NxLine Rates". Section B Pricing Schedule for DREN sites depicts Additional Bonded line item. Can N > 1 and use the same CLINS for ordering and pricing more than one bonded access link for the same site? Is the Government equally satisfied using LAG for aggregation or FlexE bonding is also required? | When N is greater than one, the Government will order the quantity one Initial or Upgrade CLIN plus quantity N-1 Additional Bonded CLINs. It is up to the Offeror to propose the method(s) of aggregation/bonding used or available and how that selection is of value to the Government (e.g. more effective load balancing). | ||
| 23 | 39 | 6.2.5.1 | "The Government will apply control ranging from simple configuration control to full NFV Infrastructure (NFVI) management." Is the Government intention to use the Contractor provided Orchestrator platform to configure and manage the DREN Nodes or the Separately Orderable elements or both? | The orderable Orchestrator would control only designated separately orderable Functions of DREN Nodes. | ||
| 24 | 39 | 6.2.5.1 | "The Government may order one or more Orchestrator instances. Each Orchestrator instance will control a collection of one or more DREN Node Functions, designated by the Government. The Government will directly control those designated Functions via a GUI and/or API provided by the Orchestrator" Is the Government intention to control specific DREN Nodes? Does this include a DCN node as well? | Any separately orderable Functions of any DREN Node, including at DCNs, may be controlled by an ordered Orchestrator. | ||
| 25 | 13 | 6.1.1.4 | It is stated that each VLAN will be totally separated from each other. Will the ethernet broadcast and multicast mentioned earlier only include one vlan and one set of encryption keys e.g. if a broad cast is needed that involves multiple vlans, it will be the responsibility of the source to initiate a broadcast on each vlan? | The separation of VLANs includes having completely separate broadcast and multicast domains. The design and configuration of MACsec are up to the Offeror to propose, including the relationship of VLANs to keys. | ||
| 26 | 9 | 6.1.2 | It is understood by the contractor that DREN will form groups and vlans over the time of the contract as needs change. The contractor will provide a backbone of nodes and capacity for each hop that provides the best capacity for the cost to the customer. The requirement of always using the shortest path for traffic would infer that capacity would have to be adjusted as the aforementioned dynamic occurs. It will be possible for the alternatives to the shortest route will still satisfy the performance requirements. For practical reasons, may some of the traffic traverse a path that is not the shortest but still maintains the performance requirements? | No. The Government reaffirms the requirement that the traffic "shall be transported through the shortest path available that maintains the Transport Performance requirements, the security requirements, and other policy characteristics." | ||
| 27 | 10 | 6.1.0.1.5 | For the separation requirement specified, is it expected that there will be some mechanism provided by the vendor to implement this, or is the function overlaid by Government used to enforce this separation? | Separation mechanisms are expected to be provided by the Contractor. A primary mechanism is encryption (PWS paragraph 6.1.1.5), but includes mechanisms such as VLAN separation in switching functions, in order to ensure confidentiality and integrity of individual DREN4 networks among and between themselves, and from the underlying provider transport. | ||
| 28 | General | Are all addresses used in this solution GFE or vendor provided? | Per PWS paragraph 6.1.2 "All network addressing (prefixes) in use on DREN4 will be provided by the Government, with the exception of the Outreach service (PWS paragraph 6.1.2.11.2)." | |||
| 29 | 10 | 6.1.0.1 | Is the current AS used in DREN4? Are new AS's required? Is the AS simultaneously used by DREN3 and DREN4? | Yes, the current AS will be used in DREN4. No new AS(s) are anticipated at this time. The AS will be used simultaneously in both DREN III and DREN4. | ||
| 30 | 11 | 6.1.0.2.1 | "The ability to transfer data between DREN Nodes shall be possible at the DREN Node rate mutually available between the two DREN Nodes." | |||
| Is a node's availability defined as that which is not consumed by communications with other nodes? | No. In this statement the rate available is the line rate of the Node. For example, if one DREN Node has a line rate of 10Gbps and the other Node has 1Gbps, then the mutually available rate is 1Gbps. | |||||
| 31 | 11 | 6.1.0.2.2 | Is the customer requiring transport pre-built in excess of what is actually needed or going to be used? If so, how much excess transport needs to be deployed? Will the DREN program office involve vendor resources in the capacity planning process to ensure sufficient transport in planning and deployment at all times? | q1: It is up to the Offeror to propose a transport solution which meets the full requirements of all active Nodes; there is no requirement to build in excess transport capacity. |
q2: Throughout the lifecycle of the DREN4 contract, the Government will hold communications with the Contractor and share as much information as possible. These discussions will not commit the Government, only an order for service will authorize any expenditures.
| 32 | 13 | 6.1.1.4.1 | Is the vendor providing unique vlan identifiers or is customer assigning them? | The Government intends to reuse VLAN identifiers that exist on DREN III. The Government will work with the Contractor to jointly assign individual and ranges of VLAN identifiers after contract award. | |
| 33 | 13 | 6.1.1.5 | Is there a key rotation requirement for the encryption? Are the keys vendor provided or GFE? | It is up to the Offeror to propose how it will implement MACsec, and provide a rationale for selected features, profiles, etc. The Government will evaluate any provided information per RFP Section M, Table M3, Subfactor 1-1 Network Architecture and Performance, and Subfactor 1-3 Security. | |
| 34 | 37 | 6.2.4.1.1 | In order to ensure that there is sufficient space in the DCN to support the compute function, is there a maximum number of compute functions that the customer will order at a DCN? | There is no limit to the number of any of the functions ordered at a DCN. The Government does not have sufficient data, including the price of the Compute Functions, to provide any bound on the number to be ordered. The Government does not anticipate ordering more than 10 Compute Functions at a single DREN Node. | |
| 35 | 38 | 6.2.4.2 | In order to ensure that there is sufficient space in the DCN to support the DAMP function, is there a maximum number of DAMP functions that the customer will order at a DCN? | There is no limit to the number of any of the functions ordered at a DCN. In general, the Government anticipates a single Node will have at most one DAMP Compute Function, but some Nodes may require up to three. | |
| 36 | 38-39 | 6.2.4.3 | In order to ensure that there is sufficient space in the DCN to support the DJS function, is there a maximum number of DJS functions that the customer will order at a DCN? | There is no limit to the number of any of the functions ordered at a DCN. The Government does not have sufficient data, including the price of the Compute Functions, to provide any bound on the number to be ordered. The Government does not anticipate ordering more than 10 DJS Compute Functions at a single DREN Node. | |
| 37 | 39-40 | 6.2.5.1.1 | "The Government may order one or more Orchestrator instances. Each Orchestrator instance will control a collection of one or more DREN Node Functions, designated by the Government." | ||
| Does the customer anticipate that more than one orchestrator will control functions in the same DCN? Orchestration often factors in the available resources in the infrastructure. If more than one orchestrator is involved in the DCN, is it acceptable that resources will be statically allocated to each orchestrator? | The control relationship is between an Orchestrator and a Function. Only one Orchestrator will be in control of any one Function, i.e., two Orchestators will never control the same Function. The Government will specify which Orchestrator will control a given Function. | ||||
| 38 | 93-94 | 6.5.10 a) | "a) | Implement POTS modem based secure Out-of-Band (OOB) capability on all Contractor-deployed DREN Node systems and maintain the access throughout the life of the contract. The capability shall include at minimum all components necessary to restore in-band management network access to the Node." | |
| Cell-based out-of-band modems are available. Can they be substituted for POTS modems? | Cell service is not available at many DREN Node locations. Some SDPs are located in facilities which prohibit the use of cellular technologies. This same prohibition on the use of cellular technologies may also exist at DXP or DCN locations. The Contractor shall support Plain Old Telephone Service (POTS) for OOB connectivity. It is up to the offeror to propose a comprehensive OOB solution which may also use other technologies at locations where the Offeror knows the technology is viable. |
After contract award, if there are alternative OOB methodologies which can be implemented with the same or higher reliability and security, the Contractor can prepare and submit a Technology Insertion Proposal (TIP) per PWS paragraph 6.4.3.1. A TIP is a contract tool available to the DREN4 Contractor when it wishes to propose an improvement to DREN.
| 39 | 5 | 6.2 | What does the Government mean by a SDP-to-SDP trunk? | The Government does not use the phrase "SDP-to-SDP trunk" in the PWS. The reference to "trunk" in PWS paragraph 6, is a reference to technologies such as 802.1Q, PB, PBB, or Ethernet Virtual Private LAN. |
| 40 | 35 | 6.2.1.4 | Are the devices managed by the Contractor and providing read-only for the Government other than the devices managed by the Government? | Yes. All Contractor IT Systems within the DREN Authorization Boundary shall have the ability to allow for Government read-only access. |
| 41 | 66 | 6.4.3.1.1 | PWS Section 6.4.3.1.1 CSfC as written is non-actionable. |
Each solution is a highly custom solution based on customer requirements.
Can DREN specify which CSfC Capability Packages are required?
https://www.nsa.gov/Resources/Everyone/csfc/Capability-Packages/
-Mobile Access Capability Package -Campus WLAN Capability Package -Multi-Site Connectivity Capability Package -Data at Rest Capability Package -Enterprise Gray Implementation Requirements Annex
| -Key Management Requirements Annex | The PWS does not require CSfC capabilities. If a CSfC TIP is requested in the future, the specific requirements will be provided by the Government at that time. All TIP actions (e.g., request, submission, evaluation) occur after initial contract award. | |||
| 42 | 66 | 6.4.3.1.1 Table 1 | If Multi-Site Connectivity Capability Package, which tunnel encryption layering option configuration is required from Table 1 of pdf link? | |
| https://www.nsa.gov/Portals/70/documents/resources/everyone/csfc/capability-packages/MSCCPv1.1_20180626.pdf | The PWS does not require CSfC capabilities. If a CSfC TIP is requested in the future, the specific requirements will be provided by the Government at that time. All TIP actions (e.g., request, submission, evaluation) occur after initial contract award. | |||
| 43 | 66 | 6.4.3.1.1 Table 1 | Table 1: |
Configuration Inner Tunnel Outer Tunnel 1 IPSec IPSec 2 IPSec MACsec 3 MACsec IPSec 4 MACsec MACsec
| How many different security levels are to be supported ? | The PWS does not require CSfC capabilities. If a CSfC TIP is requested in the future, the specific requirements will be provided by the Government at that time. All TIP actions (e.g., request, submission, evaluation) occur after initial contract award. | |||||
| 44 | 66 | 6.4.3.1.1 Table 1 | What is the highest level of security? | The PWS does not require CSfC capabilities. If a CSfC TIP is requested in the future, the specific requirements will be provided by the Government at that time. All TIP actions (e.g., request, submission, evaluation) occur after initial contract award. | ||
| 45 | 66 | 6.4.3.1.1 Table 1 | How many RED Inner VPNs are required? | The PWS does not require CSfC capabilities. If a CSfC TIP is requested in the future, the specific requirements will be provided by the Government at that time. All TIP actions (e.g., request, submission, evaluation) occur after initial contract award. | ||
| 46 | 66 | 6.4.3.1.1 Table 1 | How many RED Enclaves total? | The PWS does not require CSfC capabilities. If a CSfC TIP is requested in the future, the specific requirements will be provided by the Government at that time. All TIP actions (e.g., request, submission, evaluation) occur after initial contract award. | ||
| 47 | 66 | 6.4.3.1.1 Table 1 | Are there external to DREN endpoints for CSfC nodes? | The PWS does not require CSfC capabilities. If a CSfC TIP is requested in the future, the specific requirements will be provided by the Government at that time. All TIP actions (e.g., request, submission, evaluation) occur after initial contract award. | ||
| 48 | 66 | 6.4.3.1.1 Table 1 | Is any CSfC traffic going over Public Internet? | The PWS does not require CSfC capabilities. If a CSfC TIP is requested in the future, the specific requirements will be provided by the Government at that time. All TIP actions (e.g., request, submission, evaluation) occur after initial contract award. | ||
| 49 | 66 | 6.4.3.1.1 Table 1 | What is the maximum encrypted throughput required? | The PWS does not require CSfC capabilities. If a CSfC TIP is requested in the future, the specific requirements will be provided by the Government at that time. All TIP actions (e.g., request, submission, evaluation) occur after initial contract award. | ||
| 50 | Pricing Schedule CLIN | Current/Future Tabs | Please provide valid addresses for the list of sites attached spread sheet sent with email sent with our L.1 submission. | Most addresses reported as invalid were completely valid. Some adjustments have been made to the Address List which is available from the KO. Several addresses submitted as invalid did not exist in the list provided by the Government. | ||
| 51 | 6.3.1 | Please confirm that Security tools listed in this section will be procured, provided, provisioned, hosted and managed by the Government and Contractor will provide access to the Contractor's networking CPE equipment. | PWS paragraph 6.3.1 enumerates the "Government provided security monitoring and vulnerability assessment tools." These tools will be provided by the Government to the Contractor for implementation and hosting as required, and detailed in this section. The requirement for access to Network Components ("Contractor CPE") is detailed in PWS paragraph 6.2.0.1.5 "Government Access to Network Components." | |||
| 52 | 95 of 98 | M2.6 | Price Completeness, Reasonableness and Balance | Since 400G is not generally available in any service provider enterprise network. How will the Government establish price reasonableness for the 400G service? | The Government expects each Offeror to provide their most competitive pricing for each CLIN. Per RFP Section M2.6.(5)a., "Price reasonableness will be determined using price analysis techniques defined in FAR 15.404." All CLINS will be evaluated. | |
| 53 | 50 | Section L | Will the government provide a 30 day extension upon distribution of final question responses, in order to permit quoters time to evaluate answers, and adjust their offer with fair, complete, and reasonable pricing? Additonal support for extension request as follows: 1) Request for Attachment 6 still pending, 2) Government's pending reconciling of locations with inaccurate addresses to enable vendors to request accurate quotes from access providers, 3) Many access vendors will not be available during the holidays. | A second round of questions are due on 13 Feb 2020 at 5:00 pm CT. Proposals are due on 23 Mar 2020 at 5:00 pm CT. | ||
| 54 | DXP Site List | Section B | Pricing Schedule List | In the DXP Site List tab – there are specific Site Locations and Site Addresses that the Government have provided. In most cases the offeror has ability to provide physical colocation, cross connects, cloud providers peering at those sites and site addresses. In two locations e.g. Mclean, VA and Chicago/Starlight – the offeror does not have data centers at those exact addresses. Can we provide alternate DATA CENTER locations in the same city with ability to cross connect to both carriers and cloud providers? | No. If the Government specifies a specific address for a DREN Node then the DREN Node must be offered at that address. An updated "SDP and DXP Locations," which is available from the KO/CS via encrypted email upon request, provides multiple possible buildings for some locations. | |
| 55 | DXP Site List | Section B | Pricing Schedule List | For Honolulu, Hawaii and Las Vegas, NV – does the Government need to colocation at the exact same address with same provider i.e. Switch for Vegas and Fortress for Hawaii or can we propose alternate address in the same city? | Yes. If the Government specifies a specific address for a DREN Node then the DREN Node must be offered at that address. An updated "SDP and DXP Locations," which is available from the KO/CS via encrypted email upon request, provides multiple possible buildings for some locations. Las Vegas is removed from the DXP list. | |
| 56 | DXP Site List | Section B | Pricing Schedule List | At these colocation sites – what type of services would the Government need to cross connect? e.g. CSP peering, CSP Cloud Exchange etc.? | The cross connect is a physical connection (e.g., single-mode dark fiber) from DREN to neighboring non-DREN equipment at these facilities, and is neither specific nor restricted to any type of service. | |
| 57 | Section B | Pricing Schedule List | For the site at 15160 SAMUEL C PHILLIPS PKWY (BLDG 1641). Will the Governemnt contract with Cape Canaveral Air Force Station (CCAFS) for CCAFS fibers from the demarc to their site. | No, the Contractor is responsible for the delivery of service all the way to the Service Delivery Point (SDP). Per PWS paragraph 6.5.12.4, the Contractor shall "Coordinate with the organization responsible for the facility in which the DREN Node is to be installed and the access link provider(s) to identify and document any site readying requirements, … that must be addressed to support delivery of the local access link ..." | ||
| 58 | 37 | C6.2.4 | Compute Functions (Separately Orderable) - Will the Compute Functions (Generic, DAMP, DJS) be orderable at any DREN Node (SDP, DXP, DCN). It is not clearly specified in this section as it is in section 6.2.1, 6.2.2 and 6.2.3. | A Compute Function can be ordered for any DREN Node | ||
| 59 | 37 | C6.2.4 | Compute Functions (Separately Orderable) - Are there any requirements for providing backups to the compute systems deployed as (separately orderable) | The Compute function must be maintained to meet the performance and security requirements of the PWS. The Government OS and data is not the responsibility of the Contractor with respect to backups. | ||
| 60 | 37 | C6.2.4.1 | Compute Functions (Separately Orderable) - Can Compute Functions be delivered outside of a DREN Node, such as an AWS GovCloud or Google GovCloud FedRamp High Environment | The Compute Function shall be installed at the DREN Node at the location ordered by the Government. | ||
| 61 | 37 | C6.2.4.1 | Generic Compute Functions - For each DREN Node that Generic Compute is separately orderable from, is there any available information about initial compute needs by platform size. | The quantity, size and location of the Generic Compute Function(s) to be ordered is dependent on many variables, including the prices from the awarded Offeror. As a result, there is no available information to compute initial needs by platform size | ||
| 62 | 37 | C6.2.4.1 | Generic Compute Functions - For each DREN Node that Generic Compute is separately orderable from, are there any spare capacity requirements by platform size. | The solution must meet the resource requirements as specified in the PWS. No additional capacity nor capability above those identified in the PWS are required. | ||
| 63 | 37 | C6.2.4.1 | Generic Compute Function - Are there any requirements for application monitoring services for applications that are implemented by the Government onto Contractors Generic Compute Function. | No. The Government will manage all aspects within theVM/ platform (OS, Application Software, Software maintenance of same, monitoring of same). The Contractor is responsible for all aspects of delivering and ensuring the VM/platform service meets the requirements of the PWS. | ||
| 64 | 37 | C6.2.4.1 | Generic Compute Function - Are Operating System Licensing and Operating System Maintenance Costs for Generic Compute Virtual Machines the responsibility of the Government. | Yes. The Government will manage all aspects within theVM/ platform (OS, Application Software, Software maintenance of same, monitoring of same). The Contractor is responsible for all aspects of delivering and ensuring the VM/platform service meets the requirements of the PWS. | ||
| 65 | 37 | C6.2.4.1 | Generic Compute Function - Is there a requirement for the contractors system to detect a failed government deployed application or virtual machine and automatically fail over to another contractor system or is the governments deployed application responsible for recovering a single virtual machine failure? | The Government will manage all aspects within the VM/platform (OS, Application Software, Software maintenance of same, monitoring of same). The Contractor is responsible for all aspects of delivering and ensuring the VM/platform service meets the requirements of the PWS. | ||
| 66 | 38 | C6.2.4.2 | DAMP Compute Function - Are there any requirements for operating system or application monitoring for DAMP Servers | No. The Government will manage all aspects within theVM/ platform (OS, Application Software, Software maintenance of same, monitoring of same). The Contractor is responsible for all aspects of delivering and ensuring the VM/platform service meets the requirements of the PWS. | ||
| 67 | 38 | C6.2.4.2 | DAMP Compute Function - Are Operating System Software Licensing and Operating System Software Maintenance costs for DAMP Servers the responsibility of the Government | Yes. The Government will manage all aspects within theVM/ platform (OS, Application Software, Software maintenance of same, monitoring of same). The Contractor is responsible for all aspects of delivering and ensuring the VM/platform service meets the requirements of the PWS. | ||
| 68 | 38 | C6.2.4.3 | DJS Compute Function - Are there any requirements for operating system or application monitoring for DJS Servers | No. The Government will manage all aspects within theVM/ platform (OS, Application Software, Software maintenance of same, monitoring of same). The Contractor is responsible for all aspects of delivering and ensuring the VM/platform service meets the requirements of the PWS. | ||
| 69 | 38 | C6.2.4.3 | DJS Compute Function - Are Operating System Software Licensing and Operating System Software Maintenance costs for DJS Servers the responsibility of the Government | Yes. The Government will manage all aspects within theVM/ platform (OS, Application Software, Software maintenance of same, monitoring of same). The Contractor is responsible for all aspects of delivering and ensuring the VM/platform service meets the requirements of the PWS. | ||
| 70 | 31 | C6.2.0.1.5 | Government Access to Network Components - What is the average monthly estimated amount of active accounts that will require CLI access to the network systems or central controller. What is the estimated total amount of accounts that will be created over 10 years. | The Government expectation is from 5-10 accounts at any point during the life of the DREN4 contract. The Government anticipates a small number of additions and subtractions over the life of the DREN4 contract. | ||
| 71 | 90 | C6.5.9.1 | DREN Network Dynamic Data - What is the average monthly estimated amount of active accounts that will require administrative access to the Contractor maintained Data. What is the estimated total amount of accounts that will be created over 10 years. | Currently, the total number of accounts is approximately 1000. Typically 5-10 accounts are accessing the system at any point in time. There is no guarantee this number will be the same for DREN4. |
The access is not "administrative" in terms of being a privileged access. The Government has no specific view on the number of changes over the life of the DREN4 contract. It is expected to be consistent with normal workforce turnover.
| 72 | 58 | C6.3.8.h | SDREN PKI - DOD PKI/CaC will provide authentication services. Is there a DoD system or tool for providing Authorization such as LDAP or Active Directory that the contractors system will leverage. | No authorization system or tool will be provided by the Government. |
| 73 | 75 | C6.5.3.d | Service Management System - DOD PKI/CaC will provide authentication services. Is there a DoD system or tool for providing Authorization such as LDAP or Active Directory that the contractors system will leverage. | No authorization system or tool will be provided by the Government. |
| 74 | 90 | C6.5.9.1 | DREN Network Dynamic Data - What is the average monthly estimated amount of active accounts that will require general user access to the Contractor maintained Data. What is the estimated total amount of accounts that will be created over 10 years. | Currently, the total number of accounts is approximately 1000. Typically 5-10 accounts are accessing the system at any point in time. There is no guarantee this number will be the same for DREN4. |
The access is not "administrative" in terms of being a privileged access. The Government has no specific view on the number of changes over the life of the DREN4 contract. It is expected to be consistent with normal workforce turnover.
| 75 | 90 | C6.5.9.1.c | DREN Network Dynamic Data - DOD PKI/CaC will provide authentication services. Is there a DoD system or tool for providing Authorization such as LDAP or Active Directory that the contractors system will leverage. | No authorization system or tool will be provided by the Government. | ||
| 76 | RFP 58 | |||||
| RFP 63 | L | L2.2. references a minimum 4 past performance contracts, whereas L7.2. references a minimum 3 contracts. What is the minimum number of past performance contracts? | Amendment_0001 corrects L7.2. to reflect the data in L2.2. which states four contacts. | |||
| 77 | RFP 73-74 | Section L | Attachment L3 and L4 | Please provide the contact name, address, email address, and fax number for the person responsible for receiving the past and present performance questionnaires. | Amendment_0001 provides the contact information in Attachments L3 and L4. The documents will be updated with Amber McKee's contact information including email but no fax number. | |
| 78 | PWS 45 | 6.3.m | Cannot publicaly obtain CJCSM 6510.02, "Information Assurance Vulnerability Management (IAVM) Program," November 5, 2013. Please provide access to the document. | The subject document can now be obtained from the KO/CS by encrypted email upon request. | ||
| 79 | PWS 45 | C 6.3.p | Cannot publicaly obtain Strategic Instruction (SI) 527-01 27, March 2015, "Department of Defence (DoD) Information Operations Condition (INFOCON) System Procedures". Please provide access to the document. | The subject document can now be obtained from the KO/CS by encrypted email upon request. | ||
| 80 | PWS 55 | 6.3.2.a | Cannot publicaly obtain DREN CCB Charter (Defense Research and Engineering Network Change Control Board). Please provide access to the document. | A redacted copy of the subject document can now be obtained from the KO/CS by encrypted email upon request. | ||
| 81 | RFP 96 | M1 Price Evaluation Model | Will Attachment M1, the evaluation model, referenced as "Attachment M1 DREN4 Price Model Decription", be provided to the Contractors. | Yes, Attachment M1, the "Description" is provided. However, the Price Evaluation Model (spreadsheet) will not be released to Offerors until contract award (including the resolution of bid protests). To provide Offerors some insight into the Price Evaluation Model, a description of the Model is contained in RFP Attachment M1. The Government will not provide any additional information about the Price Evaluation Model. The Price Evaluation Model is a tool to evaluate Offerors' DREN4 price proposals. It should not be viewed as the Government's plan for any future DREN service orders (e.g., sites, bandwidths, services). | ||
| 82 | RFP 84 | M1.1.4 | Is IDIQ pricing to be inclusive of all taxes, fees, and surcharges? | All prices shall include all applicable taxes, fees and surcharges for current and future sites, CONUS and OCONUS. | ||
| 83 | RFP 59 | |||||
| RFP 66 | L2.2.3 | |||||
| L9.1.3 | Section B | In our submission Can we address the same matter (pricing information) or are we allowed to self/internally reference within our response? L9.1.3 notes thats the Contract volume should have pricing, but L2.2.3 notes that all pricing information should only be an the Price volume. | All pricing information "shall be submitted with Volume VI - Price" (L9.1.3). | |||
| 84 | RFP 15 | Key Personnel | Is the timing of approval by the Contracting Officer that has been stated as working days is in fact calendar days? | PWS paragraph 5.3. states "Since every calendar day is a working day, no distinction is made in this PWS between them. All reference to days indicates calendar (which is also working days)." | ||
| 85 | RFP 17 | H | If the labor provided in the performance of the contract is a shared resource across the orders and branches is their labor reported in its entirety in each of the eCMRA tools or prorated across all tools? | Labor will be reported in eCMRA by contract number. Data to be entered in eCMRA (Order Number, Funding Agency, Funding Office UIC, etc.) will be provided to the Contractor after award. | ||
| 86 | RFP 20 | I | When would the compliance evaluation under 52.222-24 be conducted? | The compliance evaluation will take place prior to contract award during preaward clearance procedure under FAR 22.805. | ||
| 87 | RFP 86 | M2.3 | Why is the TAV small business participation plan set at $495,000,000 and not $250,000,000 which is the minimum contract value? | The minimum order is $250,000 per Section B Contract Minimum/Maximum, Page 4. The TAV for an ID/IQ is the ceiling amount. | ||
| 88 | PWS 105 | Figure 6.2 | Figure 6 2 ImplementationTransitionGantt (PWS Reference Document) | Figure 6.2 titled "Implementation and Transition Gantt Chart" identifies a contract award date of 1-1-20. Is an updated Gantt available with an updated Award Date and subsequent milestones? | No, an updated figure will not be published. The Offeror should not use the dates on the Figure for any purpose other than illustration and should rely on the PWS text for time requirements. Per PWS paragraph 6.6 (sub-paragraph 3): "NOTE: The actual dates used are for illustrative purposes only; the focus should be on the dependencies and durations" | |
| 89 | PWS 106 | Figure 6.3 | Figure 6 3 ImplementationTransitionTimeline (PWS Reference Document) | Figure 6.3 titled "Implementation and Transition Timeline" identifies a contract award date of 1-20-20. Is an updated Timeline available? | No, an updated figure will not be published. The Offeror should not use the dates on the Figure for any purpose other than illustration and should rely on the PWS text for time requirements. Per PWS paragraph 6.6 (sub-paragraph 3): "NOTE: The actual dates used are for illustrative purposes only; the focus should be on the dependencies and durations" | |
| 90 | PWS 5 | 6. Performance Requirements, | ||||
| Paragraph 1 | Original Text: …will evolve to include higher bandwidths, organic encryption, faster provisioning…. |
| Question: Will the Government please provide a clearer definition of “Organic” encryption? | The Outreach services delivered by the Contractor must not be "associated with US Government" (reference PWS paragraph 6.1.2.11.2). This includes at least the IPs, ASNs, Registrations, Databases, and DNS names used to meet the requirements of delivering Outreach per PWS paragraph 6.1.2.11.2. It is up to the offeror to propose a solution that meets these requirements. | ||
| 91 | PWS 5 | 6. Performance Requirements, | |
| Paragraph 3 | Original Text: These IP and Ethernet networks will be grouped into "Collectives" (a DRENunique term) based on governance, routing architecture, encryption, and other attributes. Interconnects between Collectives will include a Security Gateway (SG) function administered by the Government. |
| Question: How does the Ethernet Access circuit participate on the “Collective” security group administered by the Government SG? | The "Collectives" concept applies only to the DREN4 networks, not to the underlying access links nor any part of the provider core. The "Government SG" is not "administered" by the Collective nor does it directly interact with the Ethernet Access circuit. The SG is a Government function providing a controlled interconnect between networks in different Collectives. | |||
| 92 | PWS 7 | 6. Performance Requirements | Original Text: DREN Nodes will all include a switch function, to provide bridging of Ethernet segments, and to provide VLAN support. DREN Nodes will optionally include a router function, to provide routing between IP network segments, and to support routing protocols. |
Question: Will the Government please provide clarification to the Rolling of Ethernet traffic management between the NJP and the DCN? Both are identified as Ethernet management points. The NJPs (in the provider backbone) are bridging decision points for DREN traffic without knowledge of its payload.
The DCN's Switch Function will decrypt MACsec frames and make bridging decisions based on the frame including payload examination (e.g., MLD snooping, PWS paragraph 6.1.1.2). Forwarding may involve MACsec encryption to another DREN Node.
It is likely that not all NJPs will have DCNs located at them. Some frames may pass from DREN Node to DREN Node without passing through a DCN at all, only through NJPs (PWS paragraph 6.1.1.5).
| 93 | PWS 7 | 6. Performance Requirements | Original Text: … enough interfaces to support the access link and all independent Subscribers at that site. | |
| Question: Will the Government be able to provide guidance on the number of independent Subscribers per site to assist contractors with sizing SDP equipment per location? | The quoted section of the PWS is in the introductory discussion of the tasking requirement. The sentence does not imply that the Contractor is responsible for any more interfaces than the Government specifically orders. In general the Government will order interfaces sufficient to service local Subscribers. Most Nodes have three or less Subscribers, but on a handful of nodes it is as many as a dozen. The Government may order multiple interfaces for a given Subscriber or aggregate multiple Subscribers into a single interface. Amendment_0001 updates the PWS to define "interface" as the switch port which may or may not include a pluggable module. | |||
| 94 | PWS 8 | 6.0.1 Hardware and Software, | ||
| Paragraph 2 | Original Text: … Partnership (NIAP) Product Compliant List… |
| Question: Can the Government verify if the NIAP requirement applies to third party access equipment required to supply last mile access circuits to each SDP sites? | Amendment_0001 modifies the PWS to apply the NIAP requirement only on the Firewall Function. | ||
| 95 | PWS 13 | 6.1.1.4 VLAN, | |
| Paragraph 1 | Original Text: …shall be protected from accidental leakage between them through automated and/or administrative mechanisms. |
| Question: If this is an evaluation criteria, can the government provide the “mechanisms” or functional against which it will evaluate a proposal. | VLAN leakage is defined as frames appearing on any switch port which are not in the correct destination VLAN or the appearance of a MAC address in the table for a VLAN of which that MAC is not a member. It is up to the Offeror to propose and describe capabilities to prevent VLAN leakage. One example of assurance would be the use of commercially available test suites which includes modules to test for this happening and specifically put known vulnerable patterns to the device to look for flaws. The Government will evaluate any provided information per RFP Section M, Table M3 subfactor 1-1 Network Architecture and Performance. | ||
| 96 | PWS 17 | 6.1.2.3 IP Routing, | |
| Paragraph 1 | Original Text: Routers may filter or modify the IP packets in any number of ways before processing them. |
| Question: If this is an evaluation criteria, can the government provide more information on how Ip “packet processing” will be evaluated. | The quoted sentence is introductory to the section on IP Routing (PWS paragraph 6.1.2.9). It summarizes requirements that are detailed in subelements 6.1.2.9.1 through 6.1.2.9.6. It is the specifc requirements there that will be evaluated. | ||
| 97 | PWS 21 | 6.1.2.11.2. Outreach, | |
| Paragraph 1 | Original Text: non-attributable (not associated with US Government) service to the Internet from any DREN node. |
| Question: There are many industry definition to “non-attributable” service. Can the Government clarify the level at attribution that should be obfuscated? | The Outreach services delivered by the Contractor must not be "associated with US Government" (reference PWS paragraph 6.1.2.11.2). This includes at least the IPs, ASNs, Registrations, Databases, and DNS names used to meet the requirements of delivering Outreach per PWS paragraph 6.1.2.11.2. It is up to the offeror to propose a solution that meets these requirements. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .