Updated September 2, 2021
Notice ID: W81K0221Q0227
“The contractor shall provide the non-personal services of a Library Services Platform (LSP) for Madigan Army Medical Center’s Medical Library. The Library Services Platform (LSP) shall be authorized by the Federal Risk and Authorization Management Program (FedRAMP) and hosted by a FedRAMP authorized cloud service provider. The LSP shall enable Medical Library staff to conduct customary day-to-day business in a medical research library: circulation, cataloging, acquisitions, serials control, digital rights management/electronic rights management, customized usage reports, links to other vendors’ online resources, and a discovery layer for end users to conduct research. The contractor shall maintain administrative, physical, and software security of the LSP. The contractor shall have a user group or some other mechanism to receive customer feedback on software and services. The contractor shall continue to improve the software with bug fixes, enhancements, and security fixes. The contractor shall install new releases on a predictable, announced schedule. The contractor shall back up all customer data continuously so that in the event of a catastrophic system failure, no data older than one minute will be lost.”
” Requirements- At a minimum, the base system must be commercial off-the-shelf software. It must be a managed, turnkey system in use in other Federal Government medical libraries. It must be capable of managing all types of library resources, e.g., print, digital, online, audio, visual, and other types. For future growth and networking, it must allow linking with other systems, sharing records, and/or creating consortium-like groupings of other Federal Government medical libraries. More specific required functionality follows…”
“Circulation – The proposed LSP must support basic circulation functions: checkout, checkin, renewal, in-house usage, holds, hold reports, and at least seven configurable borrower notices to be sent on a configurable schedule/calendar. It must support a calendar function that allows staff to set closed days that will prevent due dates falling on them…”
“Cataloging – At a minimum, the proposed LSP must be able to import records in a variety of formats from a variety of sources, e.g., OCLC, Library of Congress, National Library of Medicine, MARC, XML, Dublin Core, OAI, BIBFRAME, BISAC, MODS/MADS, RDF, ONIX, and others…”
Performance period: 30 September 2021 – 30 September 2022 TO 1 October 2025 – 30 September 2026.
Posted August 26, 2021
Notice ID W81K0221Q0227
“Description
The Regional Health Contracting Office – Pacific at Tripler Army Medical Center (TAMC), Hawaii intends to award a firm-fixed price contract for the non-personal services Library Service Platform (LSP) for the Medical Library at Madigan Army Medical Center (MAMC), Joint-Base Lewis McChord (JBLM) Washington.
Requirements include, but are not limited to:
- At a minimum, the base system must be commercial off-the-shelf software. It must be a managed, turnkey system in use in other Federal Government medical libraries. It must be FedRAMP-authorized, and it must operate in the contractor’s secure cloud environment, and the contractor must maintain FedRAMP authorization for the term of the contract. It must be capable of managing all types of library resources, e.g., print, digital, online, audio, visual, and other types. For future growth and networking, it must allow linking with other systems, sharing records, and/or creating consortium-like groupings of other Federal Government medical libraries. More specific required functionality follows.
- The proposed LSP must support basic circulation functions: checkout, checkin, renewal, in-house usage, holds, hold reports, and at least seven configurable borrower notices to be sent on a configurable schedule/calendar. It must support a calendar function that allows staff to set closed days that will prevent due dates falling on them. It must allow at a minimum the creation of complex circulation rules based on borrower type and status; item type and status; collection type; and material type. The proposed LSP must accept current barcode symbology (Codabar with check digit) and allow migration to RFID circulation.
- At a minimum, the proposed LSP must be able to import records in a variety of formats from a variety of sources, e.g., OCLC, Library of Congress, National Library of Medicine, MARC, XML, Dublin Core, OAI, BIBFRAME, BISAC, MODS/MADS, RDF, ONIX, and others. The proposed LSP must allow local improvements and customization of bibliographic and item records, e.g., custom 59X, 65X, and 9XX fields in MARC bibliographic records, copy-level and item-level messages in non-bibliographic records.
- The proposed LSP must allow staff to order print and online resources. It must allow at least 100 locally-customizable funds and vendor records. It must allow multiple payment types. It must be able to transmit online orders to vendors and to receive vendor confirmation reports. The proposed LSP must track the order life-cycle: initial request, approval, fund assignment, encumbrance, order, order report, receipt, confirmation, payment, borrower notification, and withdrawal from the collection. It must track all fund deposits (including refunds), encumbrances, and expenditures. It must be able to calculate vendor discounts. It must be able to assign/allocate shipping costs between multiple funds. It must track vendor performance in terms of order-to-delivery time, stated vs. actual discounts received, and number of orders filled/unfilled.
- The proposed LSP must track vendor license agreements, including start- and end-dates, allowable uses, disallowed uses, payment due dates, payment history, authentication methods, and administrator interfaces/logins/passwords.
- The proposed LSP must provide customizable, granular data for analysis of borrower use, collection use, e-resource use, vendor performance, and fund performance. Reports must be configurable by the user, e.g., library wide-collection-by-collection, item-by-item, item-status-by-item status, borrower-category-by-borrower-category, borrower-status-by-borrower-status, borrower-by-borrower, vendor-by-vendor, fund-by-fund, time-of-day-by-time-of-day, day-of-week, and other factors/parameters/combinations. It must provide a “dashboard” for quick-and-easy summary statistics to monitor on-going use, at the least updated to the day, preferably updated to the minute. It must be capable of at least outputting the data in .csv or .tsv files for manipulation in Excel.
- The proposed LSP must provide links to outside systems via APIs. At the least, it must adhere to the ANSI/NISO Z39.88 OpenURL protocol. It must connect to a link-resolver and a knowledge base to provide robust article-level linking capabilities.
- The proposed LSP must provide a modern discovery layer for end users. The discovery layer must permit users to conduct a single search across all library holdings and subscriptions, and it must return a single integrated list of search results. It must integrate with the Medical Library’s online subscriptions and the local catalog of physical books to return a unified list of book, journal, and online resources to end users. The result set must allow sorting and filtering at least by: full text, physical availability, whether or not it is peer-reviewed, whether or not it is open access, format, topic, author, publication date, language, and subject headings (Library of Congress and Medical Subject Headings). Result sets must be exportable or save-able to bibliographies. Citations must be exportable in at least the .ris format. Article and book bibliographies must be linked to results so that users can find sources cited in the resource itself and find other resources that have cited the one found.
This requirement is for a one-year period of performance, 30 September 2021 through 29 September 2022, plus four one-year options, plus the FAR 52.217-8, Option to Extend Services…”
