SOURCES SOUGHT
70 -- Library Web-scale Discovery Access and Management
- Notice Date
- 5/13/2016
- Notice Type
- Sources Sought
- NAICS
- 511210
— Software Publishers
- Contracting Office
- N00244 NAVSUP Fleet Logistics Center San Diego Regional Contracts Department (Code 200) 3985 Cummings Road Bldg 116 - 3rd Floor San Diego, CA
- ZIP Code
- 00000
- Solicitation Number
- N0024416R0031
- Response Due
- 5/23/2016
- Archive Date
- 5/31/2016
- Point of Contact
- Naima YeldaContract Specialist
- Small Business Set-Aside
- N/A
- Description
- NOTICE: THIS IS ONLY A DRAFT SOW and HAS NOT BEEN FINALIZED; more information will be included as the SOW is finalized. The purpose of this DRAFT SOW is to determine how to proceed with the requirement. INTRODUCTION/DESCRIPTION OF REQUIRMENT The Naval Postgraduate Schools Dudley Knox Library is seeking a vendor to provide an UNCLASSSIFIED turnkey cloud-based, web scale library discovery, access and management system (WDAMS). This system is to be Commercial off the Shelf (COTS) software provided using the model of Software as a Service (SaaS). The Base Year of the requirement will include a one-time implementation task (to include: project manager; project plan with milestones; installation, configuration, CASification, staff training, and data migration); a one-time on-site workflow assessment and training lot; and an annual subscription for the COTS SaaS license with 24/7 help desk, system maintenance and support including software updates and upgrades. The four option years, if exercised, will be for the annual subscription to the COTS SaaS license with 24/7 help desk, system maintenance and support including software updates and upgrades. RequirementQuantityUnit of Measurement Base Year: Implementation. Webscale Discovery, Access and Management System (WDAMS) Commercial Off-the-Shelf Software as a Service (COTS SaaS) - One time implementation fee (includes at a minimum: Vendor implementation manager; project plan with milestones; data migration; system configuration; CASification; platform; and staff training). Period of Performance: Production system/GO LIVE NLT 26 June 2017; completed implementation within 12 months of award.1TASK Base Year: Workflow Assessment and Training. Vendor to provide up to 4 on-site consultations for in-person workflow assessment and configuration training. 1LOT Base Year. WDAMS COTS SaaS - Annual subscription for 1 year from date of Production/GO LIVE (from 26 June 2017) COTS SaaS license with 24/7 help desk, system maintenance and support including software updates and upgrades.1YR Option year 1. WDAMS COTS SaaS - Annual subscription COTS SaaS license with 24/7 help desk, system maintenance and support including software updates and upgrades. 1YR Option Year 2. WDAMS COTS SaaS - Annual subscription COTS SaaS license with 24/7 help desk, system maintenance and support including software updates and upgrades. 1YR Option Year 3. WDAMS COTS SaaS - Annual subscription COTS SaaS license with 24/7 help desk, system maintenance and support including software updates and upgrades. 1YR Option Year 4. WDAMS COTS SaaS - Annual subscription COTS SaaS license with 24/7 help desk, system maintenance and support including software updates and upgrades. 1YR BACKGROUND The Naval Postgraduate School (NPS), located in Monterey, California, is a fully accredited graduate-level university that supports the U.S. Navy, other military branches, and foreign military services with masters and PhD level education for personnel. Additionally, NPS provides significant research capabilities to the Department of Defense (DoD), Department of Homeland Security (DHS), and other agencies. NPS consists of four graduate schools: International Graduate Studies, Business and Public Policy, Operational and Information Sciences, and Engineering and Applied Sciences; three research and education institutes (Meyer Institute of Systems Engineering; Cebrowski Institute; and the Modeling Virtual Environments and Simulation Institute) as well as other NPS research and education centers. Dudley Knox Library (DKL) is the academic library at NPS and provides scholarly content, systems, and associated services relevant to NPS instructional and research needs. DKL has 30 library staff who serve approximately 6,000 active patron accounts in our current integrated library system (ILS). DKL manages and provides access to more than: 600,762 Print and Electronic Books 3,178 Media 18,690 Microforms 10,000 Print and Electronic Serials Machine-Readable Catalogue (MARC) Records plus holdings (active and inactive subscriptions) 75,493 Active Unique Targets in Ex Libris SFX 489 Databases (includes commercial, government and free) OBJECTIVE DKL requires a fully operational, UNCLASSIFIED, turnkey cloud-based, hosted library discovery, access and management system (WDAMS) for public and staff use that is Commercial Off-the Shelf Software as a Service [COTS SaaS]). This system shall support core library operations (including: patron management; circulation; cataloging; online public discovery and access; acquisitions; serials control; collection analysis; course reserves; electronic resource and licensing management; and reporting) in an efficient and streamlined manner. The system must satisfy DKLs 13 functional requirements, which are comprised of 90 required features (85 mandatory features and a minimum of 5 of 7 additional desired features). To improve student, faculty, and staff access to DKL resources, the library services platform must feature a multitenant architecture, as well as an embedded discovery tool that provides immediate access to both print and electronic resources via a comprehensive knowledge base. This project is the pilot for exploring the strategic opportunity for the US Navy to align its three higher education university libraries (NPS, Naval War College, and US Naval Academy) into a common unified WDAMS that preserves local control while also promoting consortial sharing and delivery as well as digital collection initiatives. SCOPE Minimum Requirement I.Core Library Functions The system must be an in-production, turnkey, cloud-based system providing all of the following core library operations: 1.patron management 2.circulation 3.cataloging/metadata 4.acquisitions 5.serials control (including lifecycle and holdings management for print and electronic serials) 6.print and electronic course reserves 7.online public discovery and access 8.collection analysis and evaluation 9.reporting functionality 10.open URL link resolver 11.A-Z journal title search/list 12.electronic resource management 13.licensing management 14.comprehensive knowledge base with automatic publisher and vendor updates II.System Requirements 1.System must not depend on 3rd party applications or providers 2.Must be currently deployed and operational in at least three academic libraries 3.Must support single sign-on authentication such as: Central Authentication Service (CAS), Shibboleth or EZproxy. 4.Must support integration with existing identity stores (e.g. Active Directory and Lightweight Directory Access Protocol (LDAP). 5.Must provide seamless integration with OCLC subscription services including: WorldCat Connexion and ILLiad InterLibrary Loan 6.Must support non-MARC formats, (i.e. Dublin Core, Committee on Scientific and Technical Information (COSATI), Open Archives Initiative (OAI) harvesting and Extensible Markup Language (XML) import 7.Must provide Session Initiation Protocol (SIP) authentication for proprietary 3M (Company) Self-service Checkout systems. 8.Must support managing, discovering, delivering, and preserving digital assets 9.Must provide an Electronic Resource Management (ERM) application to allow for the efficient and effective management of the electronic resource workflow from renewal/purchase to activation, analysis and evaluation of e-resources 10.Must support management and display of license terms and conditions in machine-readable format to include linkage to digital resources; communicating key usage terms to users and staff; and comparing terms across different licenses 11.Must provide ability to upload and edit publisher(s) license documents and view history of edits/versions 12.Must provide a sandbox for testing NPS-specific data and configurations for both staff and public prior to launch 13.Must be able to track staff interaction with patron and bibliographic records III.Web Design Requirements 1.Must provide a responsive web design to accommodate various device platforms 2.Must support various web browsers across multiple platforms (such as Windows, MAC OS, Android, etc.) for both staff and end-users. Must describe any functionality that cannot be successfully completed through a web browser 3.Must provide ability for DKL staff to customize web interface without additional cost 4.Must be Section 508 compliant IV.Discovery Requirements a.Must provide federated search capabilities for online public discovery and at a minimum access via: a. Functional Requirements for Bibliographic Records (FRBR) b. faceted searching c. spelling and search suggestion d. Z39.50 1.Must provide citation tools: a. email b. print c. export to RefWorks citation manager as well as other citation manager software such as: Zotero, EndNote, and Mendeley 2.Must provide knowledge base (that is also library-editable for additions of non-standard resources) for complete integration and indexed discovery and access to all DKL licensed- and local-databases and eBooks V.Circulation Requirements 1.Must provide offline circulation capabilities in the case of server or network outage (this includes the ability to batch upload into system once server/network outage resolved) 2.Must provide ability to automate a bulk user load process (i.e., new incoming students each quarter) to bulk import patron records from an external source 3.Must provide ability to merge two patron accounts (in the case of duplicate records), including ability to preserve patron account, holds, notifications and borrowing activity when merging patron records 4.Must be able to activate or deactivate patron check out history 5.Must provide system override that enables patrons with shortened check out periods to use the 3M Self-service check out system 6.Must support ability for staff to charge and renew multiple items in a single session without the need to enter an override for each item in the same session 7.Must support ability for staff to manually change an items status to lost or missing and to reverse that status when the item is found 8.Must provide a configurable place hold button that does not display if items are non-circulating or on reserve 9.Must provide a link to Interlibrary Loan button for items that are not held and/or unavailable 10.Must support both electro-magnetic and radio frequency identification (RFID) systems 11.Must be able to create bibliographic and item records on the fly VI.Course Reserve Requirements 1.Must provide seamless ability to update bibliographic and item records while working inside the course reserves module 2.Must provide ability to assign different loan periods at the copy level to individual titles that have multiple copies 3.Must provide the ability to retain an item on reserve but reset circulation count on a quarterly basis 4.Must provide the ability to assign course reserves to one or more instructors and course numbers at the item/copy level 5.Must provide the ability to keep patrons from placing holds or recalls on reserve items through the online public access catalog (OPAC) 6.Must provide the ability to manage materials that alternate locations between general circulation and course reserves, while maintaining individual and separate statistics for these items (for example, standard circulation vs. reserve circulation) 7.Must provide ability to run statistical reports for item use at the course level for academic groups and schools VII.Electronic Course Reserve Requirements 1.Must provide ability to link to DKL licensed content (eBooks and articles) at the item level 2.Must provide ability to activate and suppress course reserves on a quarterly basis while retaining information and statistics from prior quarters 3.Must provide ability to enable faculty to upload their own non-library held items onto course reserve 4.Must provide ability do batch uploads of scanned items 5.Must integrate with external e-learning systems (such as Sakai or Moodle) 6.Must provide ability to upload/post documents/articles to external e-learning course sites (such as Sakai or Moodle learning management systems) VIII.Copyright Management Requirements 1.Must provide ability to connect to and integrate with the Copyright Clearance Center or other rights licensing organizations (such as American Society of Composers, Authors and Publishers (ASCAP), Getty Images, SIPX and other organizations) for permissions, usage and royalty payments 2.Must provide ability to reach out to the publisher and individual rights holder as needed for permissions, usage and royalty payments IX.Cataloging/Metadata Requirements 1.Must provide ability to locally edit and customize all record types and all bibliographic fields 2.Must provide ability to batch load and batch edit large sets of MARC records obtained from OCLC WorldShare and publishers 3.Must support batch addition/deletion of bibliographic, copy, or item records 4.Must encode all bibliographic records in MARC 21 Format for Bibliographic Data without limitation on record length 5.Must support holdings statements and display of both serial and non-serial multi-part items as defined in ANSI/NISO Z39.71 6.Must support importing and exporting of bibliographic, holding and authority records in MARC 21 Format and future frameworks from OCLC Connexion. 7.Must support authority control 8.Must support MARC 21 Format for Authority Data and allow all relevant bibliographic fields to be authority controlled. X.Desirable requirements: Vendor shall provide at least five of the following seven features: 1.Automatic staff prompting and alerts for upcoming subscription renewals 2.Customizable patron profiles for search results based on academic field of study or topics of interest 3.Integration of reference tools (such as SpringShare LibGuides) into discovery search and results 4.Ability to customize record details displayed in search results 5.Provide web services Application Program Interface (API) at no additional costs 6.Bibliographic record URL/Link checker 7.Provide two-factor authentication XI.Support Services Requirements 1.Vendor shall provide implementation support and training that include online training, in person training and telephone training 2.Vendor shall provide key personnel who will lead and manage the project plan, timeline, data migration, testing and implementation phases 3.Vendor shall provide data migration from current integrated library system (SIRSI Symphony) and electronic resource knowledge base (Ex Libris SFX) including: a. bibliographic records (print and electronic) b. holdings in all formats (including print and electronic serials and associated holdings) c. patron data (including patron-associated checked out items) 4.Vendor shall provide key personnel to provide on-site system consultation, workflow analysis and system training for DKL staff 5.Vendor shall provide 24/7 help desk support to mitigate and resolve problems quickly and accurately with minimum downtime (not to exceed 0.4% downtime on any given day without advance customer notice) 6.Vendor shall provide tiered-service level support (this is more than basic 24/7 help desk to allow customer to submit questions and issues by phone or email and receive acknowledgement; and allow customer to track status of their issues in a tracking system or monitor log system 7.Vendor shall provide ongoing customer support to include system troubleshooting and application advice during normal hours of DKL operation by telephone, online, or in person 8.Vendor shall provide standalone capabilities and tools to allow DKL to continue core functions during system or network downtime XII.Security Requirements 1.Vendor shall provide cloud-based architecture and hosting that does not require installing software on customer equipment 2.Cloud services must be deployed and maintained in accordance with current DoD security standards, including: a.Service must operate in an environment that is Federal Risk Authorization and Management Program (FEDRAMP)authorized at the DoD Level 2 or higher (final or provisional) or a demonstrated equivalent b.Must provide FEDRAMP sponsor and contact information or provide proof of FEDRAMP compliance c.Service must operate in an environment that has been SSAE 16 SOC 2 certified, such as a WebTrust, or a demonstrated equivalent d.Data must be encrypted with FIPS 140-2 Federal Information Processing Standard Level 2-certified tamper detection e.Third party access to the environment must be vetted and monitored per company policy and access is immediately disabled once no longer needed or when access is determined to be inappropriately provisioned in accordance with third party or service provider agreements f.Service must operate in a Family Educational Rights and Privacy Act of 1974) (FERPA) -compliant environment or a demonstrated equivalent 3.Additional Security Requirements a.Vendor shall provide a protocol to document and resolve unexpected restricted/classified spillages b.Vendor shall require any patron accessing her/his system account information to go through a strongly encrypted authentication method to ensure minimal security risk (such as Secure Hypertext Transfer Protocol connection or HTTP over Secure Socket Layer) XIII.Deliverables The Vendor/offeror is required to provide the following deliverables: 1.Project plan and timeline will be created and documented in collaboration with Customer Contracting Officers Representative. Tentative Timeline -- Proposed Schedule of Events Post award meeting with the Contractor: 15-20 September 2016 Initial Staff Training: 1-15 December 2016 Data Migration Complete: 15 February 2017 Onsite Consultation and Training for Workflows Management and Migration: 20-24 February 2017 Initial System Configuration Complete: 15 March 2017 Staff training and Initial Staff Testing in Local Instance Sandbox: 16 March-16 April 2017 Near-Final Configuration Complete: 15 May 2017 Near-Final Staff Testing for Production Instance: 16 May 9 June 2017 Final Configuration Complete: 25 June 2017 GO LIVE: Launch Production System: NLT 26 June 2017 Post-production System Corrections: within 12 months of award 2.Library Services Platform for initial migration and testing, and for final production (go-live) 3.Progress reports, as needed and documented per project plan 4.On-site consultation (training and workflow management consulting for ~30 staff users) during the base year 5.24/7 maintenance/system support during the base year and included with annual subscription for all option years 6.24/7 tiered ongoing customer support during the base year and included with annual subscription in option years Period of Performance: The period of performance shall be for one Base Year of 12 months and four 12-month option years. The Period of Performance reads as follows: Base Year: One year starting on date of award (on/around 15 September 2016 to 14 September 2017) Option 1: One year starting after the base period Option 2: One year starting after option period one Option 3: One year starting after option period two Option 4: One year starting after option period three NOTICE: THIS IS ONLY A DRAFT SOW and HAS NOT BEEN FINALIZED; more information will be included as the SOW is finalized. The purpose of this DRAFT SOW is to determine how to proceed with the requirement.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVSUP/200/N0024416R0031/listing.html)
- Place of Performance
- Address: NAVAL POSTGRADUATE SCHOOL (NPS), MONTEREY, CA
- Zip Code: 93943
- Zip Code: 93943
- Record
- SN04116214-W 20160515/160513234106-b15dcee9e8b14d0f048745c82a2e4397 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |