PKB LIBRARY MANAGEMENT SYSTEM SOCOM_Questions_Response.pdf
PDF 101 KB Posted
- Attached to
- PKB LIBRARY MANAGEMENT SYSTEM SOCOM Federal contract opportunity
- Solicitation number
- FA481425TF051
About this file
This document is a set of Questions and Answers (Q&A) for a Library Management System solicitation for SOCOM (Special Operations Command). The document provides detailed responses about the EOS.Web library system, including key specifications such as requiring 3 concurrent staff users, basic module package of Cataloging, Circulation, and OPAC, and no additional module requirements. The system will not require FedRAMP hosting, single sign-on, or special data conversion. This is a follow-on contract previously awarded to Sirsi Corporation under contract #FA481420P0043 with a total aggregate amount of $67,127.12. The solicitation allows for potential automatic patron record import via CSV and XML files if no additional cost is incurred, with a manual upload alternative. The library management system appears to be for a military library, specifically associated with the Department of the Air Force Air Mobility Command, with the specific solicitation number FA481425TF051.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Combined Synopsis Soliciation_ RFQ FA481425TF051.pdf | ||
| Attch 2_Provision and Clauses_FA481425TF051 (2).pdf | ||
| Attch 1_Salient Characteristics.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Questions
1. What corporate name (the legal entity) and address that should appear on the quotation?
Answer: RFQ instructions were added to sam.gov after accidently being left off.
2. EOS.Web is offered in a number of packages, each of which can have extra modules added. In terms of the basic module package – which of the following would be the most appropriate?
Answer: Cataloging, Circulation, and OPAC (“Cataloging” includes all the other system basics system and user setup, reporting, etc.)
3. We offer a number of additional modules to add various forms of functionality to EOS.Web. To provide a starting point – the most common modules added include Indexer, IP Authentication, Classification Management, and SIP2/3M Self Check. Are any of these extra modules desired?
Answer: NONE
4. Should the EOS.Web system be hosted in our FedRAMP data center rather than our standard data center? (is FedRAMP hosting a requirement?)
Answer: No requirement
5. Part of our pricing structure is related to how many “concurrent library staff users” are allowed. In other words – a maximum number of library staff that can be logged in and using the EOS.Web staff modules at one time. There is no limitation on the number of library staff user accounts created – only on the number logged in at the same time (there’s also no limit on the number of users accessing the OPAC). As an example – it’s not uncommon that if a particular library had 5 library staff, they may only need 3 concurrent users, perhaps 1 for handling the Circ Desk and the other two logged in to handle various activities. How many “concurrent library staff users” (or “seats” in the software) would be needed?
Answer: Attachment 1, salient characteristics has been revised from 5 to 3 concurrent staff users.
6. What data will need to be converted?
a. Cataloging data – would we be importing bibliographic data in MARC format, or would the cataloging data be in a different format? Will it be sufficient for EOS.Web to generate author, subject, and series authority headings from the related entries in that bibliographic data – or would it be necessary to also import authority data (and if so, in MARC format or another format)? What type of ILS will the data be exported from?
b. Circulation data – can the borrower/end-user information be provided in a spreadsheet format, or would the data be provided in a different format? Would any current checkout information need to be converted? (if so – roughly how many checkouts would this include)
c. Are there any files that should be linked to converted cataloging records (PDFs, Word documents, images, etc.)? If so – roughly how many, how much storage space do they occupy, and how can the relationship between the filename and record be identified?
How much would the storage space be expected to grow in the next several years?
d. Is there any other data that should be converted?
Answer: Currently setup in a non-FedRamp Saas Environment. No change required
7. Would Single Sign-On be needed for the OPAC? (typically, this is achieved using SAML 2.0, when desired)
Answer: No requirement
8. It is possible to automate the nightly upload of patron/borrower/end-user records. After the initial load of this data into the system (question 6B above) – would the library staff manage these records manually (adding/deleting the records themselves), or would it be preferred that this process be automated via a nightly upload?
Answer: If no additional cost is accrued enable Automatic Patron Import for .CSV and .XML files. If there is an additional cost continue with manual upload.
9. We would like to know if this is a brand-new contract OR if there is (was) an incumbent performing these services. If not brand new, could you please provide the current / previous contract number?
Answer: This is a follow-on contract previously awarded to Sirsi Corporation under contract # FA481420P0043 for a total aggregate amount of $67,127.12.
File details come from the government source that posted it. Updated .