20190405_Attachment1_RequirmentsDescription_Final.pdf

Requirements Description

Web-Scale Library Services Platform (LSP)

The Army University

2 April 2019

Part 1: General Information

1. Overview. This is a non-personal supply contract to provide an UNCLASSIFIED FEDRAMP level-4, cloud-based, web-scale Library Service Platform (LSP) that is COTS for a consortium comprised of thirteen member libraries (with the potential to expand to sixteen libraries) and an administration and management office geographically dispersed across the Continental United States. The LSP will be composed of an Integrated Library System (ILS), a web-scale Discovery Tool, an authentication layer, and electronic resource management tool (ERM).

1.1. Description of work/Introduction. The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personnel services necessary to perform Library Services Platform Hosted Service as defined in this Statement of Work except for those items specified as government furnished property and services. The Contractor shall perform to the standards in this contract.

1.2. Background. In 2016, U.S. Army Training and Doctrine Command (TRADOC) reorganized Army professional military education under a single university-type system called Army University to increase academic rigor, create greater opportunities for accreditation, and enhance the quality of the force. Army

University is aligning Officer, Warrant Officer, Non-Commissioned Officer and Department of the Army

Civilian education Systems across TRADOC under this single academic structure. The TRADOC academic libraries support the schools and Centers of Excellence (CoE) that make-up Army University.

In October 2016, the Army Learning Coordination Council (ALCC) approved a plan to create the Army

University Library Enterprise System (AULES) with the intent to improve findability and accessibility of academic library resources across the Total Force, combine like administrative and operational library processes, and provide the ability for library staffs to work collaboratively to license, manage, discover, use, share and preserve print and electronic collections across Army University libraries. The LSP concept is to combine 13 stand-alone libraries into a unified Library Service Platform that will have a single, shared system environment that will enable Army University to enable and improve rigorous and relevant learning and to maintain its Department of Defense (DOD) and academic accreditations. As a consortium, the libraries will function collectively as the Army University Library Enterprise System while continuing to maintain individuality and autonomy to provide unique support to their associated schools/CoEs.

Specific details on staff size, patron base, collection breakdown, and database/ eResource subscription numbers can be found in Appendix A. The same information for optional future expansion sites can be found in Appendix B. Current migration timeline can be found in Appendix C. Government Peripheral

Equipment List can be found in Appendix D. Additional Information about current library’s setup can be found in Appendix E.

1.3. Requirements. TRADOC/ArmyU requires a fully operational, UNCLASSIFIED, cloud-based web-scale Integrated Library System Platform (LSP). The winning Contractor shall provide an Integrated

Library System Platform (LSP) that incorporates and shares information across the following functional areas within the consortium: Integrated Library System (ILS), a web-scale Discovery Tool, electronic resource management tool (ERM), and authentication layer.

The base year(s) of the requirement will include a one-time implementation task (to include: project manager; project plan with milestones; installation, configuration, single sign-on authentication layer with a wild card SSL for remote database access, staff training, and data migration costs for the 13 member libraries); and an annual subscription for the COTS ILS, Discovery, and authentication layer 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 license(s) with 24/7 help desk, system maintenance and support including software updates and upgrades.

This project will result in a single, shared implementation of the selected ILS software. The platform’s

Integrated Library System (ILS) will be hosted on a FEDRAMP level-4 compliant cloud as a SaaS. The

ILS will operate in a consortium environment for public and staff use that is COTS. Vendor(s) shall provide fully cloud-based architecture that does not require use of any locally-installed vendor-client software on customer equipment.

This platform shall support core library operations to include: patron management; circulation;

cataloging, online public discovery and access, acquisitions, serials control, collection analysis, course reserves, electronic resource and licensing management, and reporting. This project will result in a single, shared implementation of the selected ILS software. ILS must be able to fully integrate with a web-scale

Discovery tool.

The central authentication service (CAS 2) layer must be provided by the winning vendor. The authentication layer must provide access to content within the ILS, and Discovery Tool. The discovery tool must integrate with existing data stores such as digital archival systems and content management systems. The Discovery must include a web portal capability with customizable GUI staff-end and a public-facing site. The Discovery Tool will require 14 iterations of the web-scale Discovery tool software

(i.e., one each for the 13 libraries and one over-arching enterprise (ArmyU) layer with the capability to add up to three additional iterations as the consortium grows).

Vendor bids will include all required pieces of the LSP, as detailed above (ILS, Discovery Tool, electronic resource management tool (ERM) and Authentication Layer), to be considered. No partial solicitations will be considered. Vendors should explain in their responses how their solution(s) would interact with other Vendor’s services such as web-scale Discovery or Authentication system to provide the LSP concept. Vendors should explain in their responses how they would create the LSP that will support a consortium.

The platform must consistently provide the functional requirements, required features, and project deliverables described below. To improve student, faculty, and staff access across TRADOC to the combined resources of the Centers’ and Schools’ Libraries, the library services platform must feature a multitenant architecture, as well as a discovery tool that provides immediate access to both print and electronic resources.

All components of the LSP must be able to operate over both NIPR and Commercial networks provided by the ARMY. Once established, up to three additional Army libraries are projected to migrate to ArmyU

Library Services Platform in the FY19-23 time-frame.

The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the

Contractor who, in turn is responsible to the Government.

1.4. Scope. This contract includes a COTS Integrated Library System (ILS), a web-scale discovery tool, an electronic resource management tool (ERM), an authentication layer, and the services to manage the training, migration, application implementations and continued regular service maintenance.

1.5. Period of Performance. The period of performance shall be for one (1) Base Year and four (4) 12-month option years. The Period of Performance reads as follows:

Base Year 01 July 2019 to 30 June 2020

Option Year I 01 July 2020 to 30 June 2021

Option Year II 01 July 2021 to 30 June 2022

Option Year III 01 July 2022 to 30 June 2023

Option Year IV 01 July 2023 to 30 June 2024

1.6. General Information.

1.6.1. Recognized Holidays. All Federal Holidays

New Year’s Day 1st day of January

Martin Luther King Jr.'s Birthday 3rd Monday of January

Presidents Day 3rd Monday of February

Memorial Day Last Monday of May

Independence Day 4th day of July

Labor Day 1st Monday of September

Columbus Day 2nd Monday of October

Veterans Day 11th day of November

Thanksgiving Day 4th Thursday of November

Christmas Day 25th day of December

1.6.2. Hours of Operation. Contractor will have the platform available for access by government users and researchers 24 hours a day, 7 days a week, and 365 days a year with a 96% operational rate barring scheduled maintenance or emergencies IAW section 5.1 of this SOW. Scheduled maintenance must take place outside of normal library operating hours which are 0600 EST to 0100 EST daily, not including

Federal Holidays.

1.6.3. Place of Performance. The work to be performed under this contract will be primarily performed at the Contractor’s facility except for scheduled training and site visits which will be conducted at the individual library locations during implementation.

1.6.4. Type of Contract. The government Intends to award a Firm Fixed Price Contract.

1.6.5. Security Requirements. N/A

1.6.6. Physical Security. The Contractor shall be responsible for safeguarding all government information stored off site during the course of the contract. (See para. 1.3)

1.6.7. Post Award Conference/Periodic Progress Meetings. The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers

Representative (COR), and other Government personnel, as appropriate, should for the first meeting meet face-to-face and then meet periodically through a mixture of virtual and face to face meetings at the discretion of the Government with the Contractor to review the Contractor's performance. At these meetings the contracting officer will apprise the Contractor of how the government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced.

Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.8. Key Personnel. The following personnel are considered key personnel by the government: The

Contractor shall provide a contract manager who shall be responsible for the performance of the work.

The name of this person and an alternate who shall act for the Contractor when the manager is absent shall be designated in writing to the contracting officer. The contract manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The contract manager or alternate shall be available between 8:00 a.m. to 4:30p.m. CST, Monday thru Friday except Federal holidays.

1.6.9. Data Portability. Three months prior to the termination of this contract, vendor agrees to facilitate the orderly and professional transfer of Government data stored by the vendor for this contract as required by the Government.

Part 2: Definitions and Acronyms

2. Definitions and Acronyms.

2.1. Definitions.

2.1.1. Cannibalize. The action of removing parts from Government property for use or for installation on other Government property.

2.1.2. Contractor. A supplier or Contractor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.3. Contractor Acquired Property. Property acquired, fabricated, or otherwise provided by the

Contractor for performing a contract and to which the Government has title.

2.1.4. Contracting Officer. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.5. Contracting Officer Representative (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the

Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.6. Defective Service. A service output that does not meet the standard of performance associated with the Statement of Work.

2.1.7. Deliverable. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.8. Equipment. A tangible item that is functionally complete for its intended purpose, durable, nonexpendable, and needed for the performance of a contract. Equipment is not intended for sale, and does not ordinarily lose its identity or become a component part of another article when put into use.

Equipment does not include material, real property, special test equipment or special tooling.

2.1.9. Government Furnished Property. Property in the possession of, or directly acquired by, the

Government and subsequently furnished to the Contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes Contractor-acquired property if the Contractor-acquired property is a deliverable under a cost contract when accepted by the Government for continued use under the contract.

2.1.10. Government Property. All property owned or leased by the Government. Government property includes both Government-furnished property and Contractor-acquired property. Government property includes material, equipment, special tooling. Special test equipment, and real property. Government property does not include intellectual property and software.

2.1.11. Key Personnel. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the SOW. When key personnel are used as an evaluation factor in best value procurement, a quote can be rejected if it does not have a firm commitment from the persons that are listed in the quote.

2.1.12. Loss of Government Property. Unintended, unforeseen or accidental loss, damage, or destruction of Government property that reduces the Government’s expected economic benefits of the property. Loss of Government property does not include occurrences such as purposeful destructive testing, obsolescence, normal wear and tear, or manufacturing defects. Loss of Government property includes, but is not limited to—

a) Items that cannot be found after a reasonable search.

b) Theft.

c) Damage resulting in unexpected harm to property requiring repair to restore the item to usable condition.

d) Destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair.

2.1.13. Material. Property that may be consumed or expended during the performance of a contract, component parts of a higher assembly, or items that lose their individual identity through incorporation into an end-item. Material does not include equipment, special tooling, and special test equipment or real property.

2.1.14. Physical Security. Actions that prevent the loss or damage of Government property.

2.1.15. Property. All tangible property, both real and personal.

2.1.16. Property Administrator. An authorized representative of the contracting officer appointed in accordance with agency procedures, responsible for administering the contract requirements and obligations relating to Government property in the possession of a Contractor.

2.1.17. Property Records. The records created and maintained by the Contractor in support of its stewardship responsibilities for the management of Government property.

2.1.18. Provide. The action of furnishing, as in Government-furnished property, or to acquiring, as in

Contractor-acquired property.

2.1.19. Quality Assurance. The government procedures which verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.20. Quality Assurance Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of Contractor performance.

2.1.21. Quality Control. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.22. Subcontractor. One that enters into a contract with a prime Contractor. The Government does not have privity of contract with the subcontractor.

2.1.23. Unit Acquisition Cost.

a) For Government-furnished property, the dollar value assigned by the Government and identified in the contract; and

b) For Contractor-acquired property, the cost derived from the Contractor’s records that reflect consistently applied generally accepted accounting principles.

2.1.24. Work Day. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.25. Work Week. Monday through Friday, unless specified otherwise.

2.2. Acronyms.

ABAC

ACOR

AFARS

AIP

API

AR

ATIS

CAP

CAS

CCE

CFR

CONUS

COR

COTR

Attribute-Based Access Control

Alternate Contracting Officer's Representative

Army Federal Acquisition Regulation Supplement

Archival Information Package

Application Programming Interface

Army Regulation

Army Training Information System

Contractor Acquired Property

Central Authentication Service

Contracting Center of Excellence

Code of Federal Regulations

Continental United States (excludes Alaska and

Hawaii)

Contracting Officer Representative

Contracting Officer's Technical Representative

Commercial-Off-the-Shelf

Comma Separated Values

COTS

CSV

DA

DACS

DAMS

DD250

DD254

DFARS

DMDC

DOD

DMDC

DPX

DRM

EAD

EAMS

EDI

ERMS

FAR

FRBR

FTE

GFP

HIPPA

ILS

KB

KBART

KO

MARC

METS

MODS

NIPR

OAI-PMH

OCI

OCONUS

ODC

PA

PIPO

POC

PRS

PWS

RDA

RFID

Department of the Army

Describing Archives Content Standard

Digital Asset Management System

Department of Defense Form 250 (Receiving

Report)

Department of Defense Contract Security

Requirement List

Defense Federal Acquisition Regulation

Supplement

Defense Manpower Data Center

Department of Defense

Defense Manpower Data Center

Digital Picture Exchange

Digital Rights Management

Encoded Archival Description

Enterprise Asset Management System

Electronic Data Interchange

Electronic Resource Management System

Federal Acquisition Regulation

Functional Requirements for Bibliographic

Records

Full Time Equivalent Students

Government-Furnished Property

Health Insurance Portability and Accountability

Act of 1996

Integrated Library System

Knowledge Base

Knowledge Bases and Related Tools

Contracting Officer

Machine Readable Cataloging

Metadata Encoding and Transmission Standard

Metadata Object Description Schema

Non-Secure Internet Protocol Router

Open Archives Initiative Protocol for Metadata

Harvesting

Organizational Conflicts of Interests

Outside Continental United States (includes

Alaska and Hawaii)

Other Direct Costs

Property Administrator

Phase In /Phase Out

Point of Contact

Performance Requirement Summary

Performance Work Statement

Resource Description and Access

Radio Frequency Identification

Responsive Web Design

Software As A Service

Security Assertion Markup Language

Secure Sockets Layer

Quality Assurance

RWD

SaaS

SAML

SSL

QA

QAP

QASP

QC

QCP

TE

TEI

XML

Quality Assurance System

Quality Assurance Surveillance Plan

Quality Control

Quality Control System

Technical Exhibit

Text Encoding Initiative

Extensible Markup Language

Part 3: Government Furnished Property, Equipment, and Services

3. Government Furnished Items and Services

3.1. Services. The Government will provide a ArmyU POC to assist with each piece of the migration at each location, including facilitating entry to installations and help schedule the migration of existing digital information, databases, excel spreadsheet, and Integrated Library System data into the new system.

Government will provide an additional POC for emergency data breaches, to be contacted in accordance with section 5.2 Server/Security.

3.2. Lost Government Property. Consistent with DFARS 252.245-7002, Reporting Loss of Government

Property, the Contractor shall electronically report property losses to the Property Administrator via the

DCMA Lost, Theft, Damaged and Destroyed (LTDD) eTool (including the “Contractor narrative” section), the information required of FAR 52.245-1(f)(vi)(B)(1) through (13) .

3.3 Government Resources. Government currently maintains OCLC Cataloging subscriptions and

WorldShare memberships for libraries. The Government will provide OCLC cataloging subscriptions and WorldShare memberships for all libraries. The Contractor will not need to provide the subscriptions or memberships. POCs for this are at each library. (See Appendix A for OCLC symbols)

Part 4: Contractor-Furnished Items and Services

4. Contractor Furnished Items, Responsibilities and Deliverables.

4.1. General. The Contractor shall furnish all accesses, training, and facilitate the migration of existing government data into a FEDRAMP level 4 compliant cloud service. Contractor will provide an established, Library Service Platform that integrates and shares information across the following functional areas: library core operations to include: patron management; circulation; cataloging; online public discovery and access; acquisitions; serials control; collection analysis; course reserves; electronic resource and licensing management; and reporting, collection management, archives, authentication and discovery layers.

Upon proposal the contractor shall provide the following:

1. Vendor must provide a list of three references similar in size and scope to Army University LSP concept. References should be clients who have had their system installed (including ILS and

Discovery) within the past 48 months. (Include name, contact, address, telephone, system(s) installed and date of installation, architecture of data storage and redundancy (for example, multi-tenancy, cloud distributed, etc.).

2. The platform’s Integrated Library System (ILS) must provide proof of concept that access is a fully cloud-based architecture that does not require use of any locally-installed vendor-client software on government equipment that is hosted on a FEDRAMP level 4 compliant cloud as a

SaaS.

3. Government currently utilizes these peripherals: Honeywell Voyager MS9520/MS9540;

Honeywell Voyager 1400g; Honeywell Hyperon 1300G; PSC QuickScan 6000/6500; Tech

Econwand IDT1230-U. System must identify if those listed will work with platform or provide a list of scanners that are compatible.

4. Government currently utilizes these RFID systems Envisionware and 3M Bibliotheca. Vendor must identify if those listed will work with platform or provide separate lists for the peripherals which are compatible with the LSP for self-checkout machines, PC reservation manager and

RFID.

5. Vendor must provide a plan to support multiple layers of Access and Authentication to accommodate the various types of documents, information and their required levels of protection

(i.e. username password for access to general DoD published public documents, Two-Factor

Authentication for more sensitive data/information, etc.)

6. Vendor shall provide a parent-child schematic for all LSP components.

7. Vendor must provide a copy of their cyber incident response plan.

8. Vendor must provide screen shots of how publisher’s cover art for materials including books and journals will display within the LSP by their provided enrichment service. (i.e. Syndetics)

9. Vendor project plan shall identify at a minimum the individual Center/School sequence of events

(e.g., planning/training, migration, testing/remediation, and “go live”/remediation phases), and final enterprise-level testing/remediation.

10. The Vendor shall provide a list of content providers that are in their knowledge base and highlight the following providers: ProQuest eBook Central, EBSCO, IHS Jane’s, JSTOR, ProQuest, Elsevier, PubMed, Wolters Kluwer, Taylor & Francis, Sage, Gale, Periscope and digitized content and online archives repositories including OCLC ContentDM.

Upon award the contractor shall provide the following:

1. Vendor shall provide any password, access, and auditing policies that will be used to access the system and explain how those passwords are protected in the system upon time of award.

2. The platform’s central authentication service (CAS 2) layer must be provided by the winning vendor upon time of award.

3. The winning vendor must provide a wild card SSL certification for remote database access upon time of award.

4. The hosted solution shall provide protection at all security levels 1-4 Perimeter; Operating systems and servers; Host Protection; Information Protection) including intrusion detection, reference DoD Cloud Computing Security Requirements Guide

(https://iasecontent.disa.mil/cloud/SRG/index.html).

https://iasecontent.disa.mil/cloud/SRG/index.html

5. Vendor shall have security and access control mechanisms in place to secure government information. If any services are outsourced or managed by a 3rd party, policies on terminations, passwords and how access is granted to government systems by these 3rd party’s at time of award.

6. The winning vendor must provide an enrichment service such as Syndetics at time of award to integrate with ILS and Discovery.

7. Vendor shall have a backup plan for database(s) and files including monthly tests with the backup disks kept offsite of the facility. Those files still must be kept at FedRamped facility as part of their proposal. A copy of the backup plan will be provided at time of the award.

8. Vendor shall provide contact plan for Consortium POC and access to informational resources and

FAQs at time of award.

9. Vendor shall provide access to basic 24/7 help desk support to mitigate and resolve problems quickly and accurately with minimum downtime (not to exceed 4% downtime during business hours on any given day without advance customer notice). Shall accept support requests that do not require contract modifications from any consortium member library and from consortium central staff.

10. Vendor shall provide a screen shots of their library staff customer portal for accessing help documentation as well as describe how the interaction with the Vendor’s help desk and provide screen shots of trouble ticket system process.

11. At time of award, Vendor shall provide POC who will lead and manage the project plan, timeline, data migration, testing, and implementation phases.

12. At time of award, Vendor shall provide the 2 government POCs with an emergency cyber incident response plan that is FedRamp and NIST compliant as specified in 5.2 Server/Security.

13. At the time of migration the Vendor shall provide each location with 4 barcode scanners that will work on the new platform. The Barcode scanners are equipment that will be classified as

Government Property once installed and will remain in the Libraries even after contract expiration.

After award but before migration, Vendor shall provide the government with necessary equipment to perform the inventory function, if specialized equipment is required. Again this property once installed will become Government Property and will remain in the Libraries even after contract expiration.

Part 5: Required Characteristics

5.1. Systems/IT LSP Functionality.

1. The platform must provide fully cloud-based architecture and hosting that does not require use of any locally-installed vendor-client software on customer equipment.

2. The platform must have a Cloud-ready architecture and infrastructure with hosting options on

FEDRAMP level 4 Cloud as a SaaS.

3. The platform must be an in-production, cloud-based system providing core library operations in a consortium environment.

4. The platform and data shall be physically located and operated in the Continental United States.

5. The platform and data shall be managed and operated by U.S. Citizens or approved qualifying contractors and subcontractors.

6. The platform’s must demonstrate full redundancy for all critical components and at critical interfaces and demonstrate 96% uptime outside of emergencies.

7. At the time of the migration the vendor shall provide on-site system consultation, workflow analysis and system training for TRADOC and Army University staff. During migration 3-4 visits expected per location, with total visits not to exceed 55 in-person visits across the consortia in the base year. Option years should include 1 in-person visit to each location, with total visits not to exceed 17 per option.

8. The hosted solution must notify Government of any maintenance of LSP 2 business days prior to taking the system down for maintenance and any time the LSP has to be taken down during

TRADOC normal operating hours. See TRADOC hours of operation in section 1.6.2. In case of emergencies the hosted solution must notify Government POC as soon as possible.

9. The Contractor shall have a backup plan for database(s) and files including weekly differential backups with full backups quarterly with the backup disks kept offsite of the facility. Backup files must be kept at FEDRAMPed facility that is located off-site from the primary data site as part of their proposal. A copy of the backup plan will be made accessible at time of the award. The plan shall include details (i.e. network connectivity between sites, operational management of alternate site, etc…) regarding an Alternate Backup Site that is located geographically outside of a Natural

Disaster Area of the primary site.

10. The platform must provide a means for authenticating all administrative users and systems that access the environment and data. Platform shall allow for the configuration of access capabilities and permissions for each back-end user based on user type, user group, and customization of permissions for discrete elements of the dataset.

11. The platform must provide a Responsive Web Design (RWD) to accommodate various device platforms support for various web browsers across multiple platforms (e.g., Windows, iOS, Android, others) for both Staff and end-users, specifically Internet Explorer and Edge, Mozilla

Firefox, Chrome, and Safari and provide support for two earlier versions of listed browsers.

12. The platform must support continuous operation during the transition.

13. Vendor shall provide help screens and informational resources as a component of their system at time of award.

14. The platform shall provide library staff basic 24/7 help desk support to mitigate and resolve problems quickly and accurately with minimum downtime (not to exceed 4% downtime during business hours on any given day without advance customer notice). Shall accept support requests that do not require contract modifications) from any consortium member library and from consortium central staff.

15. The platform shall provide a library staff portal, including an online help desk, trouble ticket reporting and a “Frequently Asked Questions (FAQ’s)” section.

16. The Platform shall provide technical integration with the following content providers: ProQuest eBook Central, EBSCO, IHS Jane’s, JSTOR, ProQuest, Taylor & Francis, Sage, Gale, and digitized content and online archives repositories including OCLC ContentDM.

17. The platform must allow a single staff user to be in multiple modules at the same time.

18. The platform must support the ability to set password policy specifying: minimum length and require periodic changes.

19. The platform shall prevent the staff/patron user from signing on after invalid logons attempts. The system must provide an option for reset of password for both staff and patron access.

20. The platform shall require any patron accessing their 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).

21. The platform shall default to English and provide each User Account the capability to set individual preferences (i.e. display preferences, etc.…) to be maintained and applied at User

Logon for any additional options.

22. The platform must support the ability to import and export various file types, including but not limited to, TXT, CSV, XML, MARCXML, PDF, Cdda, ISO PCM uncompressed WAV at 96

KHz/24-bit depth rate, MP3, MPEG2, MPEG4 H.264, JPEG2000, Uncompressed AVI, 4K DPX, DOC, PPT, TIF, WMV, GIF, PSD, and HTML.

23. The platform must support the Open Archives Initiative Protocol for Metadata Harvesting (OAI-

PMH) and allow search engine harvesting and indexing.

24. The platform must provide ability to edit and customize all record types and bibliographic fields.

25. The platform must support holdings statements and display of both serial and non-serial multi-part items as defined in ANSI/NISO Z39.71.

26. The platform must support importing and exporting of bibliographic, holding and authority records in MARC 21 Format and future frameworks from OCLC Connexion®.

27. The platform must support non-roman scripts, e.g. Chinese, Japanese, Korean, Cyrillic and bidirectional script display (e.g. Arabic, Hebrew) and the uploading of foreign language bibliographic records in MARC and non-MARC formats.

28. The platform must support multiple classification schema and subject vocabularies including, but not limited to, Library of Congress Classification and Subject Headings, Dewey Decimal

Classification, SuDoc classification numbers, local classification schema, National Library of

Medicine Subject Headings, and LC Genre Form Terms. The platform must enable each library to operate under multiple schema that may differ at each location.

29. The platform must have the ability to import metadata from records such as MARC, EAD, MODS, METS, TEI, KBART, Dublin Core, etc.

30. The platform should have ability for all libraries to be able to login via IP authentication.

31. The platform must have the capability to integrate library data (such as title lists, reserve lists, account information) into the learning management systems Blackboard; as well as for content management systems ContentDM; and guide management systems SpringShare’s LibGuides.

32. The platform must provide ability for individual libraries to customize searches/scopes not available in one library but available in another consortial library such as searching journal titles, reference books, or new books and those displayed results must provide a Responsive Web

Design (RWD).

33. The platform must provide ability for Integrated and seamless user experience without the complication of detailed software coding APIs that free up bibliographic, authority, patron, and transactional data.

34. The platform must have the 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 and usage.

35. The platform must include a service that displays books and journals cover art similar to

Syndetics as an example.

36. The platform must provide the ability to add customizable public notes to items within an ERM such as copyright restrictions, number of views left on limited eBooks etc.

37. The platform will provide each library the ability to brand interfaces at the local and consortium level.

38. The platform must be WCAG 2.0 Level A and Section 508 compliant.

39. The platform must have a link checker for both the ILS and Discovery.

40. The platform must have the ability to create unlimited number of records.

41. The platform’s ILS and Discovery must provide federated search capabilities for online public discovery and at a minimum access via:

Functional Requirements for Bibliographic Records (FRBR)

Faceted searching

Spelling and search suggestion

Z39.50

5.2. Server/Security.

1. All data stored in Vendor’s systems remains the exclusive property of the Government and no copies of data shall be made by Vendor without explicit direction by authorized agents of the

Government. In the event of a migration of the data to a new system, Vendor is required to maintain the data until successful migration is confirmed by the Government, up to a maximum of 180 days from end of contract.

2. The hosted solution shall demonstrate protection at all security levels 1-4 Perimeter; Operating systems and servers; Host Protection; Information Protection) including intrusion detection, reference DoD Cloud Computing Security Requirements Guide

(https://iasecontent.disa.mil/cloud/SRG/index.html).

3. If the platform requires any specific inventory licenses in order to execute inventory functions in any of the functionalities listed for the LSP they must be included in the total cost and provided.

4. Platform’s must operate on machines running current Microsoft Windows (64bit) Operating

Systems or higher in an encrypted environment and provide support for one previous version of the OS.

5. The Vendor shall provide their Cybersecurity and Information Assurance Incident plan that is compliant with FedRamp accreditations and defines an incident and details response and reporting requirements to the customer. The plan will detail the management and reporting of the entire incident, which includes the closeout, cleanup, and damage of the incident.

6. Vendor must provide a protocol to document and rapidly assist customer with expunging from the cloud-based system any bibliographic record(s) and associated full-text content that is deemed to be “restricted/classified” subsequent to said item(s) having been placed into the cloud-based system (such “restricted/classified” spillage may cause significant harm to US national security interests). An automated content and/or document management application augmenting the vendor’s capabilities with an administrative management console for Library Staff’s access to configure application operations is desired and preferred.

7. Vendor must require any patron accessing their 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).

8. Vendor must provide an automated method/application to scan content uploaded for classification markings or other content not authorized. The Method/Application will allow Administrators to

Add/Modify/Remove content to be scanned against.

9. Vendor must provide ongoing library staff customer support to include system troubleshooting and application advice during normal hours of TRADOC operation by telephone, online, or in person.

10. Platform must utilize URL verification for bibliographic records and websites.

11. Platform must be deployed and maintained in accordance with current DOD and industry standards, including:

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 https://iasecontent.disa.mil/cloud/SRG/index.html determined to be inappropriately provisioned in accordance with third party or service provider agreements.

Platform must operate in a Family Educational Rights and Privacy Act of 1974

(FERPA)-compliant environment or a demonstrated equivalent.

Platform must provide encryption of data between server and client.

Platform must provide granularity of security options for library staff and faculty.

5.3. Reporting and Analytics

1. The platform’s Integrated Library System (ILS) must have the ability to tune reports to a granular level appropriate to each facet of the system including but not limited to: Circulation, Acquisitions, error reporting, and Cataloging.

2. The platform must have a customizable advanced reports module which includes:

Templates for commonly used statistics.

Ability to run staff user action statistics, i.e. individual staff member work actions taken by multiple parameters, including date, type of action, type of material, function, etc.

Report generator which allows users to easily query the database by combinations of user-selected fields and criteria.

Ability to run variable date range reports.

Ability to Auto-run as well as scheduled reports.

Ability to tune reports in granular level appropriate to each facet of the system including but not limited to: Circulation, Acquisitions, error reporting, and

Cataloging.

Ability to ingest and present usage statistics in accordance with ANSI/NISO Z39.93-

2014, the Standardized Usage Statistics Harvesting Initiative (SUSHI) Protocol. It must also allow import or manual entry of usage statistics not harvestable via SUSHI, including Counter-compliant and non-compliant data.

Ability to present history data and support trends analysis.

Ability to provide analytics, including location of users, IP addresses, link-through to proprietary databases, bounce rate, number of visitors, browser, OS, mobile device, based on varied date ranges.

5.4. Integrated Library System (ILS)

1. The platform’s Integrated Library System (ILS) must support core library operations to include:

patron management; circulation; cataloging; online public discovery and access; acquisitions;

serials control; collection analysis; course reserves; and reporting.

2. The platform’s Integrated Library System (ILS) must allow for the Minimum of 200 simultaneous staff access points such as user licenses or “seats.”

3. The platform’s Integrated Library System (ILS) must allow for daily data backups.

4. The platform’s Integrated Library System (ILS) must support streamlined function windows. For example, the ability to check in, renew, and view a patron’s record without moving between different windows or renew and view a patron’s record without moving between different windows.

5. The platform’s Integrated Library System (ILS) must have the ability for mobile inventory control in stacks with use of a laptop or mobile device.

6. The platform’s Integrated Library System (ILS) must support self-service circulation workstations identified in Appendix D.

7. The platform’s Integrated Library System (ILS) must support RFID identified in Appendix D.

8. The platform’s Integrated Library System (ILS) must be able to set up user groups with varying privilege levels and access modules.

9. The platform’s ILS must support a tool for printing spine labels.

10. The platform’s ILS must support both electro-magnetic and radio frequency identification (RFID) item security systems.

11. The platforms ILS must allow staff to change the due date for one or more items in checkout mode.

12. The platform’s Integrated Library System (ILS) must have live URLs (from the 856 field) in the display.

13. The platform’s Integrated Library System (ILS) must recognize natural language keyword searches, recognize abbreviations in controlled vocabulary, and recognize DACS, EAD, MARC, and BibFrame schemas simultaneously, while only displaying one unified record.

14. The platform’s Integrated Library System (ILS) must support SQL-based database reporting, non-

SQL based database reporting, and supports metadata schemas with the option of simultaneous use of Dublin Core, EAD, AACR2 and RDA.

15. The platform’s Integrated Library System (ILS) must provide seamless integration with following

OCLC® subscription services: WorldCat, WorldCat Connexion® and ILLiad® /WorldShare

Interlibrary Loan.

16. The platform’s Integrated Library System (ILS) must support authority record creation and automatic authority record updates from either Library of Congress (LC/LOC) or Online

Computer Library Center (OCLC).

17. The platform’s Integrated Library System (ILS) must allow authorized staff to configure various aspects of the ILS without Vendor intervention.

18. The platform’s Integrated Library System (ILS) must support Unique record IDs for patron records.

19. The platform’s Integrated Library System (ILS) must have the capability to easily link or tag patron accounts with a Master patron account.

20. The platform’s Integrated Library System (ILS) must allow for automated holds with ability for staff to manually override the hold, both staff and patron ability to customize criteria to fill a hold, and the ability to put hold on an on order record.

21. The platform’s ILS must have an Inventory Function.

22. The platform’s ILS must support record versioning, including the ability to view and roll back to past versions of that record.

23. The platform’s Integrated Library System (ILS) must provide the ability to prevent patrons from placing holds or recalls on defined item types such as course reserve statuses.

24. The platform’s Integrated Library System (ILS) must provide cataloging function/API

(Application Programming Interface) in order to create localized MARC records.

25. The platform’s Integrated Library System (ILS) must maintain relationships between items, including metadata to item, and items in owing library.

26. The platform’s Integrated Library System (ILS) must have workflow management capabilities that track the movement of collections materials for their entire process of acquisition, accession, cataloging, utilization, and deaccession. This requires the system to track property through its lifecycle.

27. The platform’s Integrated Library System (ILS) must have a statistical dashboard to report the latest tabulated statistics on the number of items in each collection and the usage of items by type and location.

28. The platform’s Integrated Library System (ILS) must have the ability to support global editing with proper user level permissions for bib/item/patron records at both the local and consortium level.

29. The platform’s Integrated Library System (ILS) must have customizable batch requests and actions including uploads, tasks, editing, exports, import of multiple formats in the system

30. The platform’s Integrated Library System (ILS) must provide ability to automate a bulk user load process (i.e., new incoming students each class) to bulk import patron records from an external source using LDAP within Blackboard.

31. The platform’s Integrated Library System (ILS) must have the ability to allow for renewals in patron record (while viewing items out), during both check-out and check-in processes. ILS must allow for renewal of a single item that is checked out as well as multiple selected items checked out to a patron.

32. The platform’s Integrated Library System (ILS) must have the ability to allow multiple staff users to view the same master bibliographic record but only allow one user to update at any time.

33. The platform’s Integrated Library System (ILS) must have an offline module that is compatible with Microsoft Office, preferably Excel for situations where server is not available and offline data must be able to be uploaded when the server becomes available.

34. The platform’s ILS must be able to activate or deactivate patron check out history.

35. The platform’s Integrated Library System (ILS) must be able to create temporary bibliographic and item records “on-the-fly”.

36. The platform’s ILS must automatically generate a notice to patrons when requested items are available.

37. The platform’s ILS must be able to have a process to recall items with automatic notices sent to patrons.

38. The platform’s Integrated Library System (ILS) must support the coexistence of local and consortium lending rules including the capability to customize lending rules such as the ability to determine/provide loan periods and renewal policies when dealing with consortium lending without interfering with local loan, renewal, and hold policies.

39. The platform 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 at the local and consortium levels.

40. The platform must provide ability to upload and edit publisher(s) license documents and view history of edits/versions on the local and consortium levels.

41. The platform’s Integrated Library System (ILS) must provide ability to assign different loan periods at the copy level to individual titles that have multiple copies.

42. The platform’s Integrated Library System (ILS) must provide the ability to assign course reserves to one or more instructors and course numbers at the item/copy level.

43. The platform’s Integrated Library System (ILS) 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, general circulation vs. reserve circulation).

44. The platform’s Integrated Library System (ILS) must provide ability to activate and suppress course reserves on an as needed basis while retaining information and statistics from prior classes.

45. The platform’s Integrated Library System (ILS) must provide ability to batch process course reserve items.

46. The platform’s Integrated Library System (ILS) must fully integrate with a web-scale Discovery tool.

47. The platform’s Integrated Library System (ILS) shall provide access to global, shared authority files without the need for individual libraries to synchronize with the authorizing agency.

5.5. Authentication

1. The authentication layer must provide attribute-based access control (ABAC) to content within the ILS and Discovery Tool.

2. The platform must support multiple layers of Access and Authentication to accommodate the various types of documents, information and their required levels of protection (i.e. username password for access to general DoD published public documents, Two-Factor Authentication for more sensitive data/information, etc.).

5.6 Discovery

1. The platform’s Discovery tool must integrate with existing data stores such as digital libraries and content management systems and databases already in place.