36C10A20R0003-0002001.docx

QUESTIONS AND RESPONSES

1. It is not specified that each of the 8 phones (4 SIP and 4 Analog) should have unique phone numbers. Is it expected that 8 unique toll-free numbers are provided for each VMU/MPU?

Response: Correct, there shall be 8 unique toll-free numbers per VMU/MPU. The Performance Work Statement has been revised accordingly.

2. The PWS states "Demodulator Hub Line Cards must support a minimum of 60 simultaneous terminals." Does it matter to the Government the line card supports 60 terminals, or that the hub infrastructure must support 60 simultaneous terminals?

Response: There should be sufficient cards in the hubs to support a minimum of 60 simultaneous terminals.

3. In section 5.2.3.2, the Government specifies incorrectly the transmit frequencies. These are the intermediate frequencies modems utilize to transmit data to the amplifiers. It is requested that these items be removed, as any modem and terminal combination should meet the requirements of Letter H of this same section.

Response: Section 5.2.3.2 has been revised to remove the frequency range from the Performance Work Statement (PWS).

4. There is a new requirement in Volume I to provide proof of FIPS 140-2 Level 1 or better NIST AES-256 encryption for the three segments identified. The PWS states this is to be an attachment to Volume I but does not state whether it is included in the 30- page limit. We recommend that this type of documentation be provided as an attachment at the end of Volume I and be outside the 30-page overall limit.?

Response: The FIPS Level 140-2 NIST Certifications will not be counted against the page limit. The RFP is amended to reflect this change.

5. We request the due date for the updated RFP be moved from Wednesday December 11th, 2019 to at least Monday December 16th, 2019.

Response: The due date for responses to the Request for Proposal 36C10A-20-R-0003 was changed to December 29, 2019, 11:59 PM Central Standard Time in Amendment 0001.

6. What time of day is the Proposal due on the 11th of December?

Response: See response to Question 5.

7. In para 5.2, it indicates that the Contractor can move Hub equipment to new Hub. In para 5.2.2, it indicates contractor shall replace hub equipment. Question: Can we move the equipment during the first transition phase (0-60 calendar days) and then replace during the second transition phase (160 days after first transition phase)?

Response: The Government still has to move the terrestrial VA circuits to the new hub location(s) and this process can take up to 60 days. As long as the legacy VSAT network continues to function as designed during the transition the contractor can make whatever moves required.

8. There would appear to be a typo (i.e. December 1) from an earlier RFP version. Shouldn’t it read 160 days after April 1 or better 160 days after completion of phase one? See below:

5.2.3 - B – 229 VSAT Terminals due incrementally, total 229 no later than 160 calendar days after December 1, 2019.

Response: This was a typo and has been corrected in the revised PWS.

9. Request a 5-page count increase for technical responses to the subject solicitation. The additional pages will allow vendors to fully address the changes made as part of the corrective action without negatively impacting response to the original content.

Response: The total number of pages for Volume I, Technical Proposal will be increased to 35 pages.

10. Is a shared hub allowed for usage?

Response: Section 3.0 and 5.2 of the PWS state the network is for “private dedicated SatCom Services”. No shared equipment will be accepted.

11. What is the expected bandwidth for each location?

Response: There are 229 remote terminals and a requirement for 36 Mhz of transponder bandwidth. As stated in section 5.2.2 of the PWS bandwidth allocation will be dynamic. However, the Government will at times request bandwidth to be dedicated to certain units for important or critical missions. The Government expects the Offeror to provide their own bandwidth allocation information in the technical portion of their proposal.

12. Is this an emergency only backup or is it going to be used all the time?

Response: It will be used all the time.

13. Will MPLS be a requirement?

Response: Multi-Protocol Label switching is not required.

14. Is the requirement for a standard internet connection directly into the internet backbone?

Response: As described in section 5.4.3 of the PWS an internet connection shall be provided for backup path purposes. “The Internet connection shall be offline until the ESPO PM or the Contracting Officer’s Representative directs its activation.” Should the VA network be offline this will allow the VSAT network to connect to an alternate destination over this link. The primary communications path will be via a direct connection to a Government router on premises at the hub location. The Government has up to 60 days to provide the circuits and router to the hub locations.

15. Would consider a Ka solution? If not, why not?

Response: No. There are not many Ka satellites in orbit yet and the VA wants the flexibility that Ku gives in moving services if a satellite fails and the VA deploys units from all over the US/PR/VI to and from different regions of the country with little or no notice.

16. In the document, they want the option to add space segment. It’s not explicitly stated that they want higher speeds available, but that is our current assumption. Is there a specific reason that they want to add the option to add more space segment?

Response: The VA wants the ability to add more units or allocate more bandwidth to units in a disaster situation without dangerously impacting normal operations (by robbing them of bandwidth) on other areas. VA’s concern is with bandwidth, not speed.

17. We have a site list which we can check to determine what speeds are available at each location. We can run this by your team to determine if those speeds would be sufficient for your planning scenarios. Is this an option?

Response: VA requirements are clearly stated in the PWS. All offerors must demonstrate their approach in accordance Section E.1.2.c(1) of the RFP .

18. Can the contract response time be extended?

Response: See response to Question 5.

19. Respectfully request the Government clarify the objective of this requirement. Must each hub be capable of supporting 60 simultaneous terminals, and the offeror may determine the internal configuration of the hub so long as the technical approach is explained in their in their proposal?

Response: Correct. The requirement is to support a minimum of 60 concurrent terminals and the Offeror is to explain their approach.

20. The RFP states that Volume 1, Technical should include “Offeror’s written document that provides proof of FIPS 140-2, level 1 or better NIST certified 256-bit AES certification for terrestrial links to and from the hub, data transmitted over satellite communication links, and wireless access points as required by section 5.2 of the PWS.” Is this certification included in the page count for the Technical volume (30 pages) or can it be included as an Attachment or Appendix to the Technical volume?

Response: See response to Question 4.

21. RFP Proposal instructions requires the offeror to provide written document that provides proof of FIPS 140-2, level 1 or better NIST certified 256-bit AES certification. Because the FIPS 140-2 Certifications are in the format of 8 ½ x 11” certification letters, will the govt allow the FIPS 140-2 Certs be inserted into the Tech in an Appendix and not counted in page count?

Response: See response to Question 4.

22. The government indicates contractor can reuse equipment provided contractor upgrades required router and modem. One of the requirements is FIPS-140-2 level 1 wireless access points. Is the government expecting the contractor to upgrade all wireless access points as well, regardless of the age? If so, will the government modify the requirements to include the replacement of all wireless access points to ensure FIPS 140-2 level 1?

Response: Section 5.2.3.1 of the PWS is amended to clearly state that the Contractor has the option of reusing the VMUs 5 years old or newer providing they upgrade the router, modem, and wireless access points to meet all of the requirements in the PWS, including the fact that wireless access points must be FIPS 104-2 Level 1 NIST certified.

23. Reference Attachment C, VSAT Network Drawing. What is the circled parallel path? What does the Provided Management Router interface go to in the hub as depicted?

Response: The parallel path circled in green depicts the path current taken to manage the non-VA connected side of the VSAT network. This Includes all the items in the dotted blue square labelled “PSTN phones” as well as the hub and non-VA connected hub components. It would also be the path used to perform network scans for the non-VA connected devices. In short, it is the contractors network management path. The Provider Management Router interface connects to any piece of equipment the provider requires in order to manage the contractor operated components at the two demarks (hub locations).

24. PWS section 5.2.1 states “The VA will not accept the usage of a satellite that is past its projected life expectancy and with less than 15% station keeping propellent available“. Percent of remaining station keeping propellent is not a consistent predictor of satellite remaining service life. Remaining station keeping propellent is a function of the initial fuel estimate after orbit raising, the fuel consumption per month and the orbital location. Will the government please change the requirement to “Bidder must clearly indicate the number of months of fuel life on the satellite with a minimum of 60 months from September 1, 2020.”?

Response: No. The statement is conditional where both must be true in order for the Government to disqualify a satellite. We consider each a risk so if both are true we will not accept the satellite.

25. PWS section 5.2 requires Proof of FIPS 140-2, level 1 or better NIST certified 256-bit AES certification for terrestrial links to and from the hub, data transmitted over satellite communication links, and wireless access points to be attached to the proposal. Will the government confirm these attachments will not be page counted.

Response: See response to Question 4.

26. Table B.4 line 5.2.3 refers to December 1, 2019. Will the Government please remove date reference for the due date of the deliverable?

Response: See response to Question 8.

27. Are the satellite hub and satellite modems required to be FIPS 140-2 level 1 compliant, or can the compliance called out in section 5.2 be achieved at the router level before the data reaches the satellite equipment?

Response: To be found technically acceptable, a proposal must have both the requisite certified wireless access points and terrestrial links (as detailed in PWS sections 5.2, 5.2.3.1, and 5.2.3.2), as well as a solution that that ensures FIPS 140-2, Level 1 encryption of all government data transmitted over satellite communication links. Proof of FIPS 140-2, level 1 or better NIST certification for terrestrial links to and from the hub, data transmitted over satellite communication links, and wireless access points must be provided with the proposal.

The Government does not recognize a product that claims to be “compliant” as meeting the Government requirement. We require the data to be encrypted via a NIST certified/validated methodology, and we require proof of that certification. The PWS does not require every piece of communications equipment be individually certified (outside of the terrestrial links and wireless access points), however the burden is on the offeror to demonstrate in their proposal how all data transmitted over satellite communications links will maintain FIPS 140-2, level 1 encryption. Failure to demonstrate as much, to provide the relevant certification, or to explain how non-certified equipment maintain data encryption, could result in an adverse technical evaluation.

28. The VA states that they “will not accept the usage of Chinese or Russian built or operated satellites.” Please describe any additional country of origin restrictions for equipment not considered to be part of the satellite.

Response: Restrictions applicable to this solicitation are found in Section C of the RFP. Specifically, FAR clauses 52.204-23, PROHIBITION ON CONTRACTING FOR HARDWARE, SOFTWARE, AND SERVICES DEVELOPED OR PROVIDED BY KASPERSKY LAB AND OTHER COVERED ENTITIES, and 52.204-25, PROHIBITION ON CONTRACTING FOR CERTAIN TELECOMMUNICATION AND VIDEO SURVEILLANCE, SERVICES OR EQUIPMENT.

29. Paragraph 5.2.2F calls out SCAP or similar service. Please define the capabilities required in a similar service.

Response: Security Content Automation Protocol (SCAP) is a suite of specifications for exchanging security automation content used to assess configuration compliance and to detect the presence of vulnerable versions of software. Our intent in adding it to the PWS is for the contractor to have a system for assessing risk and scanning for vulnerabilities in any SATCOM software. SCAP was chosen as VA currently uses SCAP to scan for vulnerabilities on its own systems. Accordingly, the ability to continuously scan the SATCOM system for vulnerabilities. In addition, the SCAP or similar service should be able to create, document, and maintain checklists that standardize and enable automation of the linkage between computer security configurations and the NIST Special Publication 800-53 (SP 800-53) controls framework. Offerors who propose a SCAP version will be at an advantage as VA currently uses SCAP. However, if a contractor has a vulnerability scanning suite of specifications that can perform equivalent functions, that will be accepted, with the proviso that the burden is on the offeror to demonstrate in their proposal that their alternate suite of specifications can conduct the necessary scans.

30. Can the VA confirm that no fundamental changes to the requirements have been made between the original request (36C10A19R0008) and the current iteration (36C10A20R0003)? If not, could the VA please identify what requirements have changed?

Response: RFP 36C10A20R0003 stands alone. The requirements are defined in the Performance Work Statement.

31. PWS section 5.2.1 has been revised to include the following statement:” The VA will not accept the usage of Chinese or Russian built or operated satellites”. In addition to this restriction does the VA also require proposed satellites to be under FCC license and fully coordinated with adjacent satellite vendors to minimize adjacent satellite interference risk?

Response: No, there are no additional restrictions. However, the Government has set performance metrics and associated penalties for lack of performance. The Offerors must take this type of risk into account before proposing satellites prone to interference.

32. Will the government provide utilization (MHz and duration) of surge bandwidth under the current contract?

Response: No.

33. Section E.1.2.c(1)(c)requires bidders to submit “written documentation that provides proof of FIPS 140-2, level 1 or better NIST certified 256-bit AES…” as part of “Volume 1 – Technical Factor”. Will the Government please clarify that said written documentation may be provided as an Attachment to “Volume 1 – Technical Factor” and be exempt from existing page limitations?

Response: See response to Questions 4 and 9.

34. Performance Work Statement Section 5.3, Two-Phase Enterprise SATCOM Transition and Deployment. Sentence: “…..The new Contractor shall be responsible for operating and maintaining the existing SATCOM system…..) Will the Government please clarify what operational documentation will be provided and made available from the current Contractor and/or the Government upon contract award? Also, can the Government further define this ‘concept of operating’’?

Response: PWS Section 5.1.6.2 of the PWS details the required operational documentation to be provided and made available from the current contractor upon award. Transition phase 1 has a length of 0 to 60 days. It is specifically for the new contractor to take over the existing network. Because it may take 60 days for the VA to move data circuits from the current hub locations to the new hub locations (assuming you are moving them) it would be wise to move only one at a time. This period also allows the new contractor to install, setup, and activate the new VSAT network. Phase 2 has a period of 160 days. Phase 2 is the time allocated to replace all of the terminals required under the contract. This allows for a total of 240 days of transition time. By day 240 the contractor shall have all transitions complete and the network should be in the production and sustainment phase. The government does require the VSAT terminals remain operational during the transition. So if the contractor plans to move both hubs concurrently to locations without VA data circuits, this would be an issue.

35. The solicitation number 36C10A-20-R-0003 is posted as a pre-solicitation notice, please verify if 36C10A-20-R-0003 is a Request for Proposal (RFP).

Response: Yes, 36C10A20R0003 is an RFP.