N6426726Q5006_Questions_Answers.pdf

N6426726Q5006 EWB SSN Questions and Answers

1. After reviewing the DoD Adopted list provided. Can you clarify that bullets 2 and 3 are the same list? Is the

PDF list provided the 90% of the DoD Adopted Listing NAVSEA would require access too?

a. Bullets 2 & 3 should be used to define the same data set. Bullet 2 was used in previous contracts, with the intent of having access to the complete set of standards from each SDO. However, exceptions were noted and not included previously, due to higher cost impacts. Bullet 3 was meant to cover the exception list that had occurred.

b. Bullet 3 is the data set being requested by the user community. We would like to have everything, but there are exceptions within this list as well.

2. Does NAVSEA require only Active DoD Adopted Standards?

a. Example from list: Document ID: AA1, dated 11/30/1990. AA1 was Withdrawn in 2000 and Superseded by

AA-ASD1.

b. Example from list: Document ID: ANSI-A10.3, 4/30/2020. The correct standards ID is ASSP A10.3.

American Society of Safety Professionals owns the Copyright. The standard is ANSI-approved.

i. In both examples above, there are historical versions of the standards. Is the NAVSEA requirement only for the most recent version of the correct standard?

c. NAVSEA would require the historical data set along with the most recent versions. DoD acquisition products are based on the current standards when they achieve full-rate production. Older products will not upgrade to the most recent standards due to the limited cost structure to support legacy products. Engineering needs access to previous versions to support the Fleet. It is understood that eventually the SDOs will cancel and remove standards, and the Contractor will reflect the SDO models.

d. ANSWER: We also require historical versions of our government standards. Our main government repository for the public distribution of military standards and specifications previously decided not to maintain some older versions.

3. Period of Performance – The current contract, N6426721F5090, is set to expire on 9/29/2026. Historically, the PoP has been 9/30/20XX – 9/29/20XX. Is it NAVSEA's intent to change the PoP to 10/1/20XX – 9/30/20XX?

a. No intention to change the historical PoP. We can update with your recommendation, as required.

4. CLIN 0001 Question – Can you provide the potential number of NAVSEA WNY remote users within the DC and Arlington areas?

a. The intent would be to only allow users with a navy.mil email access to the contract. It would be a small bump up from the current user base. Tough to estimate, but we could maybe develop a minimum to maximum increase percentage. We do have a CLIN for a remote user list, which seems to be a solution with limits imposed on that listing.

5. CLIN A002 – Can you provide the potential number of SUPSHIP users at each of the locations listed?

a. Should Anacortus, WA, Brownsville, TX and Quonset, RI be included in this list? If yes, please provide the potential number of users at each.

b. The number of users would continue to be the same from the existing contract. I have an older list that I could develop some estimates; however, we could request the Contractor to provide their current registration listing which would be the same answer that I would provide.

c. ANSWER: We have no insight into the number of users at the detachments.

6. CLIN A004 – Strategic Systems Program (SSP) currently has a contract with [CONTRACTOR] through our Library of Congress (FEDLINK) IDIQ contract. This contract is set to be renewed on 6/21/2026. If SSP plans to merge with the NAVSEA contract, what is the plan to cover the service gap from 6/21/2026, the new start date, to either 9/30/2026 or 10/1/2026?

a. Should Anaheim, CA, Omaha, NE, and Bristol/Abbywood, UK be included as they are listed in the current contract?

b. I will get the correct response from SSP (TBD). SSP is trying to find solutions with filling in this gap, or paying a startup fee if they have to switch to our consolidated contract after the gap period.

c. ANSWER: Depending on the cost to cover the gap, SSP may not cover the service gap from 22 Jun 2026 to 30 Sep 2026. SSP is inquiring to Library of Congress if a 3-month Task Order is viable to cover the gap.

d. ANSWER: Yes, please include. Added to the updated attachment.

7. CLIN A005 – Thread/RMS/API or Connector product. These products are quoted per project, as each one has a different set of requirements, standards, and parameters to meet. However, the license for the standards must be obtained before [CONTRACTOR] can provide a quote for this add-on.

a. The contract would need to have the ability to add additional standards to the subscription as needed to support this option.

b. We will look into this.

8. Deposit Accounts – Does NAVSEA and SSP plan to have the ability to replenish Deposit Account funds once they are used throughout the entire contract period?

a. I will get the correct response from SSP (TBD). The NAVSEA intent would be to replenish funds as required.

b. ANSWER: Yes. We will be able to send financial documents from SSP to NAVSEA Comptroller to apply funds to the contract.

9. Does NAVSEA intend to have a Base plus Option Years?

a. Yes.

10. [CONTRACTOR] has a FEDLINK IDIQ and GSA contract option. Does NAVSEA intend to use GSA, and would they consider using the FEDLINK IDIQ Direct Express option

a. All options can be considered. Contracting vehicles would be a Contracting Officer decision. I am not familiar with these other options, but I have heard that the FEDLINK option is more involved and less flexible.