questions.docx

Questions

1. As per “212-1 212-2 FULL TRADEOFF.docx” in Section B, 2., should any nonconcurrence with any portion of the terms and conditions, PWS, or contract type be identified, how would USAHEC prefer the Contractor to indicate any revisions?

a. In-line with the requirement in Contractor’s response?

b. Submitted as a separate document with each revision referencing language in the contract?

Separate Document for any revision referencing the paragraph and/or contract.

General

1. In 1.6.1 Quality Assurance, where is the Quality Assurance Plan defined? Would like to get a clear understanding of: what the performance standards are that must be adhered to, the frequency of surveillance, and the minimum acceptable defect rate(s).

A vendor submits a Quality Assurance Plan. This determines how the vendor measures progress against the work of the PWS under "Performance Requirements Summary."

2. In the previous contract, we have completed standard form 1449. As this is a draft in the existing RFP, can you please confirm if this should be exempt and will be completed upon contract award?

This is a draft to the writing system having technical issues. Upon award this will not have the draft watermark on it and will be an official document signed by the Contracting Officer.

Library Functionality

1) USAHEC currently uses the Overdrive e-book platform.

2) USAHEC is not presently using RFID. (Note: RFID is being explored as a property accountability and circulation (i.e. check-out) option, there is the possibility it may be implemented during the base year or option years, so RFID compatibility is included as a requirement)

System-wide Functionality

1) All users shall be able to modify parameters for native reports. Should a third-party tool / report writer such as Crystal Reports be required to generate custom reports, USAHEC expects a total of 10 users with custom report creation access.

Systems Infrastructure

1) The requirement specifies a minimum of 100 concurrent users across the system. Should multiple systems be involved, expected number of concurrent users required for each component is:

a. Collections Management / Museum software: 25 total: 20 general, 5 administrative

b. Archives Software: 75 total: 70 general, 5 administrative

c. Library Software: 30 total: 25 general, 5 administrative

d. Public Interface: total and general users unknown, as this will consist primarily of the general public accessing and searching USAHEC collections, 5 administrative

Discovery / Search Functionality (Public Interface)

1) The USAHEC user/volunteer agreement is a fillable / signable PDF document that outlines proper handling of materials, restrictions, etc., and is required to be completed before a library card is issued and collection handling privileges granted. The intent of "upload" is that the individual has a means to electronically transfer the completed / signed agreement to the USAHEC staff for validation and record-keeping.

Just to clarify as per “212-1 212-2 FULL TRADEOFF.docx” in Section C, 1., is this 35 pages for each volume or for every volume in total? Could it be requested that this page limit is increased to ensure a comprehensive response?

Yes due to space restrictions on space for other systems that we use.

3. Should the DRAFT contract “W91QF023Q3003 SOL.pdf” be completed for the Volume 1 submission response? a. Looking for further clarification of what document should be referred to for that Volume (considering this document is a draft) and what exact contents the Volume should have especially with page limits in mind.

Volume 1 is General Information about the vendor/contractor. Reference the RFQ W91QF023Q3003. The Document is a draft due to our system issues.

How many SIP2 connections are required for things like security gates, self-check kiosks, patron authentication, etc.?

SIP2 connections: USAHEC requires a minimum of 3 connections. USAHEC presently has 2 self-service kiosks and a mobile checkout app that use SIP2 connections.

The URL http://iasecontent.disa.mil/cloud/SRG/#CloudComputingSecurityRequirementsG uide seems to be unreachable as per requirement (c) – are we able to get a copy of this guide or an alternative URL?

Correct link is: https://public.cyber.mil/dccs/dccs-documents/

3. As per (ii), does USAHEC see this dedicated representative to be someone outside of USAHEC’s account manager and specific for each software component involved in the entire product suite?

It is not required that this individual be distinct from the USAHEC account manager, and the representative would not need to be specific for each software component. USAHEC seeks a primary (i.e. centralized / single) point of contact to perform the functions enumerated in the requirement.