030ADV22R0036 0004 .pdf

5. PROJECT NUMBER (if applicable)

CODE7. ADMINISTERED BY

2. AMENDMENT/MODIFICATION NUMBER

CODE

6. ISSUED BY

8. NAME AND ADDRESS OF CONTRACTOR

4. REQUISITION/PURCHASE REQ. NUMBER3. EFFECTIVE DATE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED

PAGE OF PAGES

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED

BPA NO. 1. CONTRACT ID CODE

FACILITY CODECODE

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

E. IMPORTANT:

is extended,

(a) By completing Items 8 and 15, and returning __________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY is not extended.

12. ACCOUNTING AND APPROPRIATION DATA

(REV. 11/2016)

is required to sign this document and return ___________ copies to the issuing office.is not, A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

15C. DATE SIGNED

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER

Contractor

16C. DATE SIGNED

14. DESCRIPTION OF AMENDMENT/MODIFICATION

16B. UNITED STATES OF AMERICA

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER 16A. NAME AND TITLE OF CONTRACTING OFFICER

15B. CONTRACTOR/OFFEROR

STANDARD FORM 30 PREVIOUS EDITION NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.243

(Type or print) (Type or print)

(Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

(Number, street, county, State and ZIP Code)

(If other than Item 6)

(Specify type of modification and authority)

(such as changes in paying office, appropriation date, etc.)

(If required)

(SEE ITEM 11)

(SEE ITEM 13)

(X)

CHECK

ONE

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

(Signature of person authorized to sign) (Signature of Contracting Officer)

1 14

0004 RQLGD20220073

Contracts and Grants Directorate Library of Congress

101 Independence Ave. SE LA 325 Washington DC 20540-9411

Contracts & Grants Directorate Library of Congress

LA 325

101 Independence Av SE Washington DC 20540-9411

To all Offerors/Bidders

030ADV22R0036

X

X X

See CONTINUATION Page

X

The purpose of Amendment -0004 is to:

1) Add Attachments J13.1 and J14 to the solicitation. These documents answer questions that the Library has deemed useful for vendors to provide well-informed proposals and solutions.

2) Update the security requirements under C.3.13.8.

The proposal due date remains June 15th, 2022 at 5:00pm ET.

Schuman, Michael

6/6/22

CONTINUATION PAGE

030ADV22R0036 0004 Section C

SECTION C - DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK

Library of Congress Collections Access Platform (LCAP) Statement of Work (SOW)

C.1. BACKGROUND

The Library of Congress (Library) is an unparalleled world resource with a collection of more than 171 million items includes more than 40 million cataloged books and other print materials in 470 languages; more than 74 million manuscripts; the largest rare book collection in North America; and the world's largest collection of legal materials, films, maps, sheet music and sound recordings.

The mission of the Library Collections & Services Group (LCSG) is to develop, acquire, organize, provide access to, maintain, secure, and preserve the Library's universal collections, which document the history and further the creativity of the American people. These collections record and contribute to the advancement of civilization and knowledge throughout the world. Unlike most other national libraries, the Library's extensive collections are universal in scope. More than half of its books and serials are in languages other than English including more than 3 million items in non-roman scripts. More than half of the Library’s holdings are in special formats. Among them are the most comprehensive collections of Chinese, Japanese, and Russian language books outside Asia and Europe; general collections of the arts, humanities, science and technology; legal materials essential for study and understanding of American and foreign law; and the most extensive collection in the Western Hemisphere of books printed before 1501. The Library's manuscript collections relate to manifold aspects of American history and cultural heritage. The music collections contain volumes and pieces, both manuscript and published, from classic works to the newest popular compositions. Other research materials include an extensive collection of cartographic materials; vast arrays of photographic records, prints, drawings and posters; music and non-music sound recordings; government documents, newspapers, and periodicals from all over the world; microforms; motion pictures and video recordings; and Braille materials.

Increasingly, the Library has prioritized digitization and providing access to its digitized collections online.

For over 20 years the Library has relied on its Voyager integrated library system (ILS) to support the acquisition, description, management, discovery, and delivery of this diverse and extensive collection. Today more than 2,000 staff rely on the ILS to do their work and to date, the Library’s Online Public Access Catalog is the most frequently visited page of the Library’s website.

The ILS Program Office (ILSPO) manages the ILS, as well as other enterprise systems, in support of the Library’s operations and mission to provide access to the collections. ILSPO staff also manage projects and collaborate with the Office of the Chief Information (Officer OCIO) and other stakeholders to implement technology solutions for staff and users. As the Library’s needs have evolved, the ILSPO has supplemented the functionality of the ILS with additional library systems such as the Millennium Electronic Resource Management System (ERMS) and a variety of tools and custom applications. To achieve its goals for the next 20 years and beyond, the Library requires next generation technology that is better suited to fulfill these needs.

C.1.1. OVERVIEW OF THE INTEGRATED LIBRARY SYSTEM (ILS)

The Library's Integrated Library System (ILS) serves a number of internal stakeholders, including nine special format divisions and three area studies divisions, the U.S. Copyright Office, the Congressional Research Service, the Law Library of Congress, the National Library Service for the Blind and Physically Handicapped, and the Cataloging Distribution Service. Externally, the ILS’s major stakeholders are Congress and the American public, which includes researchers spanning elementary school students to specialized academic researchers. The Acquisition and Deposit Division in the U.S. Copyright Office relies on the ILS to describe physical and digital collections materials received on deposit as a result of Copyright registration or demand. In addition, the ILS supports critical services to the larger library community, publishers, and metadata service providers.

The ILS provides a wide variety of national and international services. These include a centralized cataloging program, whereby the Library acquires material published all over the world, catalogs it, and distributes cataloging information in machine-readable form; a cooperative cataloging program in which name, series, and subject authority records are prepared by the Library of Congress and other libraries become part of the Library of Congress database and are distributed to other institutions; the Cataloging-In-Publication (CIP) program in cooperation with American publishers for printing cataloging information in current publications; participation in the CONSER (Cooperative Online Serials) Program, whereby the Library shares serial cataloging with libraries around the world; the National Serials Data Program, the national center that maintains a record of serial titles to which International Standard Serial Numbers have been assigned; the development of general schemes of classification (Library of Congress and Dewey Decimal) and subject headings as well as specialized schemes for particular types of materials and genre/form lists; interlibrary loan of materials in its collections to other institutions; the exchange of duplicates with other institutions; and the reproduction of materials in its collections. In addition, the Library works with other standards-setting organizations; publishes print catalogs and bibliographies; circulates items from the Library's collections in travelling exhibits;

provides books in Braille and "talking book" recordings for the blind and print disabled; and is a leader in efforts to digitize retrospective American collections. The Library shares its high quality metadata with librarians and institutions around the world and manages the largest corpus of authority records that comprise the LC/NACO Authority File. The Library makes those authority records available to users via an online catalog as well as via the Z39.50 inter-site search protocol. The Library’s leadership role in the cultural heritage community requires support to make the data in the LC/NACO Authority File available.

Because authority control is one of the most resource-intensive aspects of catalog management for libraries, access to the LC/NACO Authority File is an indirect support to the nation’s libraries.

The Library’s Voyager ILS has six different production databases with a total of over 63 million bibliographic records. The largest of these six databases is Library of Congress Database (LCDB), which holds over 19 million bibliographic records, 21 million holdings records, 27 million item records and 11 million authority records. The annual growth rate for bibliographic data is typically between 400,000 and 600,000 records per year for the Voyager ILS primary production database alone. The Voyager ILS includes acquisitions, cataloging, circulation, interlibrary loan and inventory control, patron account management, reporting, Online Public Access Catalogs (OPACs) for the Library (including Law Library), Handbook of Latin American Studies, Congressional Research Service, and National Library Service for the Blind and Physically Handicapped, and metadata exchange with internal partners, and external partner libraries around the world. Other systems managed by the ILSPO include an Innovative Interfaces Millennium Electronic Resource Management System (ERMS) with over 1.6 million bibliographic records and coverage information for over 2 million licensed and freely-available electronic resources. ERMS is the central access point for e-journal and e-book content and provides coverage information and links to e-content maintained on publisher platforms and displays license information for legal use of e-content. ILSPO supports other related systems: Ex Libris’ SFX OpenURL Resolver and Primo Central; the locally-developed EAD Finding Aid System; and a number of critical workstation applications that have been developed locally to meet the Library’s evolving functional needs. The Library also relies on a number of other systems that interface directly with the ILS but are managed outside of the ILSPO.

Many of the Library's systems are at, near, or past obsolescence; in order to continue critical work, we must modernize business systems necessary to manage the national collection and support the Library’s operations efficiently and effectively. In partnership with the Office of the Chief Information Officer (OCIO), ILSPO will embark on a multi-year effort to modernize digital collections systems and infrastructure, in support of the Library's Strategic Plan and Digital Strategy. OCIO follows an Agile process using two-week sprints for other major modernization projects. The Library has a requirement to provide unified access to search functionality across the collections, enabling easier navigation and discovery for users. This next generation https://loc.gov/about/ technology must address aging technology, reduce maintenance costs, improve features and tools for users and staff, and simplify access and use for the Library.

C.2. SCOPE

The contractor shall provide a Library Collections Access Platform (LCAP) to support centralized management of the entire lifecycle of the Library’s acquisitions, bibliographic control and cataloging, electronic resource management, inventory and circulation, search and discovery, and library cards / researcher management data and processes, while providing the greatest efficiency and value to the Library's operations. The solution may be composed of one or more proven, mature systems or services from one or more vendors and must at a minimum, include a Library Service Platform (LSP) and Discovery Layer.

LCAP functionality will be delivered in task orders on this IDIQ. Details for the Library's intended Discovery Layer are included in Tab 9 of the RTM.

C.3. REQUIREMENTS

C.3.1. LCAP Functional Requirements

The Contractor shall provide all personnel, administration, software subscriptions, hosting, management, DevOps, and support services necessary to provide operational support for an LCAP solution that meets the Library’s business and functional requirements.

C.3.1.1. The Contractor shall provide a solution to support streamlined management of the entire lifecycle of the data and processes in the following areas:

• Acquisitions

• Cataloging and Bibliographic Control

• Electronic Resource Management

• Inventory and Circulation

• Library Cards & Researcher Management

• Search & Discovery

The contractor will work with the Library to analyze and refine the Requirements Traceability Matrix (RTM) provided in Attachment J4 - Requirements Traceability Matrix (RTM) for Analysis. The contractor will work with the Library to analyze and refine these requirements and develop a product backlog and roadmap in Task Order 1. Additional requirements may be developed or refined with each subsequent task order.

For the first task order, the Contractor must meet all requirements detailed in Attachment J3 - Mandatory Requirements for Task Order.

C.3.1.2. The solution will be required to be a FedRAMP-certified software as a service (SaaS) solution and must interface with other systems both internal and external to the Library via API. Solutions that are not yet FedRAMP-certified may submit a Service Organization Control (SOC) SOC-1 report for review before or after award. It may be composed of one or more systems or services including a Library Service Platform (LSP), Discovery Layer, and other supporting tools or applications. The solution must include test and staging environments that replicate the production environment and can be refreshed as needed to support specific projects such as fiscal period closeout. The solution must also include a training environment that includes a copy of the Library’s production data. The contractor’s hosting environment shall be required to be FedRAMP-certified.

C.3.1.3. The Contractor shall analyze requirements, produce plans and designs for system development, configuration, and feature implementation to determine how the solution will meet the functional requirements. The contractor shall indicate the expected minimum viable product (MVP) criteria for each requirement. As such, an MVP shall be provided by the contractor for each feature but will be defined between the Library and the contractor during the course of development.

The Contractor shall propose a solution and then, using the Agile methodology, the contractor will work with Library stakeholders to develop, test, and refine the system, and will work with the Library’s Office of the Chief Information Officer (OCIO) and Integrated Library Systems Program Office (ILSPO) to implement the system in compliance with Library IT policies. The contractor shall implement a training program to facilitate in-person and web-based training for Library staff.

C.3.2. Analysis and Solution Design The contractor shall deliver technical and functional analysis, recommendations, and solution designs to meet the Library's needs, as required by task orders.

C.3.3. Implementation & Testing Services

The contractor shall provide implementation services to support LCAP, including implementation planning, configuration, deployment in secure development, test, and staging environments, deployment to production, and integration into the Library’s current IT and training environments. The Contractor shall coordinate with Library staff to ensure implementation is conducted in an orderly and efficient manner that takes into account any priorities or dependencies identified by the Library.

The Contractor shall conduct and document functional, user acceptance, and performance testing to collect and resolve issues and defects and obtain written acceptance of required functionalities.

At a minimum, the contractor shall provide the following during the testing and implementation:

• Test plans and test cases;

• User acceptance testing (UAT) in non-production environment and report results;

• Troubleshooting and issue resolution;

• Final user acceptance testing and submit final test report.

C.3.4. Data Migration Requirements

The contractor shall execute the data migration tasks necessary to migrate data from the Library’s legacy systems to LCAP. Specific data migration tasks will be defined at the task order level.

C.3.6. Licenses

Federal Acquisition Regulation (FAR) 52.227-14 Rights In Data-General, will apply to this contract. However, if the contactor is providing a customer developed component under section C.3.13.3.1 of this SOW, the contractor will provide the Library with a license for unlimited use of the component. Furthermore, the contractor shall provide any licenses required for the proposed solution(s) and on-going support for the duration of the contract. Contractors can submit more than one alternative for the Library to consider.

C.3.7. Maintenance, Issue and Problem Resolution

The contractor shall track, identify and resolve issues and problems with the LCAP solution in the Library’s JIRA application or an alternate application to be hosted by the contractor. The contractor shall work with end users and subject matter experts to validate issues and develop a resolution plan that includes correction, rollout, training and communication.

C.3.8. Support

The contractor shall provide ongoing maintenance and production support for the system which includes at least quarterly releases, updates, and bug fixes, as well as upgrades and enhancements to the system.

The Contractor shall provide a Service Level Agreement (SLA) to include:

• 24X7 99%+ Uptime for SaaS solutions production environment o Contractor shall ensure that the environment will not be down between 6am - 6pm ET Monday - Friday, unless agreed upon by the Library. Maintenance windows are to be preferred after 6pm or on weekends

• Infrastructure support:

o Prior notification for patch windows o Service Disruption Notification within 24 hours

• Application support:

o Minimal down time for deployments, updates, and patches o Deployments, patches, and updates executed only in approved maintenance window o Planned Service Disruption Notification within 48 hours o Maintenance Window notification 48 hours o Software support (online, phone, email) including tiered response times: within 1 hour of being contacted for

Critical issues, 4 hours for all other issues o Work stoppages or downtimes will be resolved within 4 hours after initial contact (at the latest).

C.3.9. Project Management Life Cycle (PMLC) and Systems Development Life Cycle Requirements (SDLC)

The contractor shall comply with the Library’s Project Management Life Cycle (PMLC) and System Development Life Cycle (SDLC) policies, as defined in LCD 5-310.1 and LCD 5-310.2, respectively, which provide the guiding principles and practices needed to successfully execute an Agile software development project. These guidelines are detailed in Attachment J6 – Library PMLC and SDLC.

The contractor shall provide project management services to support LCAP. The contractor shall develop and execute a Project Management Plan (PMP) that includes a technical approach, organizational resources, and management controls. Additionally, the Contractor shall deliver status reports for each sprint. The Contractor shall provide task updates and task resolution information to the COR and ILSPO.

C.3.10. Training Requirements

The Contractor shall develop and deliver training on LCAP to Library staff stakeholders. The Contractor shall develop training materials in coordination with designated Library of Congress staff and shall deliver training via in-person sessions, recorded live webinars, and pre-recorded tutorial videos. The Contractor shall make recordings of live webinars available to the Library for internal distribution via the Library’s internal platforms, no later than the next business day after the training. The number, schedule, and type of trainings to be delivered will be determined at the start of the project.

C.3.11. Exit/Transition Plan Requirements

The Contractor shall create an Exit/Transition Plan to ensure an immediate and stable transition of the proposed solution (or incremental functionality) and any data it holds.

C.3.12. Access to the Library’s IT Systems

Personnel that require access to Library IT Systems (on premise or cloud) will need to meet these minimum qualifications at the time the task order begins:

• U.S. Citizenship with a minimum of Public Trust security clearance

• Ability to communicate both orally and in writing

• Ability to meet critical deadlines

• Expertise in execution and oversight of major federal IT programs

All individuals with access to Library IT Systems will be required to take IT Security Training on an annual basis to retain access to Library Systems. They must also complete the Records Management Basic Awareness Course on an annual basis.

C.3.13. LCAP Technical Requirements

The contractor shall provide an LCAP solution that includes:

• A cloud-based Software as a Service (SaaS) solution;

• A detailed and published Product Roadmap;

• An enhancement process that enables the Library to propose enhancements to the product(s).

Additionally, the Contractor shall provide a solution that fully complies with the following:

C.3.13.1. Administrative Access Requirements

The Contractor shall provide administrative access to Library administrators, via Library approved equipment over a secure VPN Connection.

C.3.13.2. Alerting / Monitoring Requirements

The contractor shall meet the following alerting and monitoring requirements:

• Alerting or monitoring functionality that will provide real-time up/down alerts, as well as time-based availability metrics

• 24/7 real-time monitoring and incident response/resolution for the various components of their systems: hardware, OS, database, application performance, security, etc.

• Ongoing performance trend analysis and forecasting future resource allocations to meet the performance metrics of the

SLA

• Regular reports of SaaS system availability and performance metrics against the SLA requirements

• Dashboard for customers to monitor real-time status of the SaaS systems, view scheduled maintenance and service disruption notifications, and include the ability to receive email status alerts

• Ability for customers to quickly document and report real-time performance and system stability issues to the vendor’s support team

C.3.13.3. Solution Interface & APIs

The system shall include the ability for bi-directional data exchange with other Library managed systems. This data exchange is preferred to be via interactive Application Programming Interface (API), but can also be a bulk style interface. These exchanges must be schedulable, auditable, fully instrumented and access controlled. The format of the data is preferred to be in open standards such as JSON or XML.

The solution shall include fully documented APIs that allow the Library to expose data to external users and systems.

The use of APIs must not be restricted in any way that prevents the Library from conducting business at scale.

C.3.13.3.1. Open Source

For any custom developed components that are not elements of the vendor’s proprietary core system, the contractor shall maximize the use of open-source code, open APIs, and modular design. The system must integrate into the Library’s information technology architecture and applicable data management models. The application architecture must be as platform-agnostic as possible and allow for vertical or horizontal scaling. Individual application components shall be built to reduce tight coupling and maximize re-use. APIs should be built to abstract interfaces between components and those APIs should be the primary communication mechanism between components. The contractor shall also provide a plan for maintenance and upgrades for custom developed components that covers the duration of the contract.

C.3.13.4. Customizations and Configuration Requirements

If the solution offers the ability to extend features/configuration via user-defined configuration items, these configurations must not interfere with future platform upgrades. These user configurations must be version controlled either via an internal tool, or via an external repository such as GIT.

C.3.13.5. Data Movement Requirements

Data movement requirements for the LCAP must include, but are not limited to:

• Ability to extract/bulk export our data from platform o Ability to support encrypted connection from the Library to the SaaS platform via Virtual Provider Network, transit gateway or equivalent technology

• Ability to bulk import our data from on premise to the platform o Ability to support encrypted connection from the Library to the SaaS platform via Virtual Provider Network, Transit Gateway or equivalent technology

C.3.13.5. Data Ownership Requirements

The Library shall retain ownership of any user created/loaded data including data loaded by the contractor at the Library’s request into the implemented solution without regard to location or infrastructure/software ownership and maintains the right to request full copies of the data at any time. The Library shall retain unrestricted rights with unfettered access to all Library data. Further, the Library retains ownership of any system generated metadata and/or descriptive data, giving structure, context, relationship and/or meaning to Library user generated and loaded data.

C.3.13.6. User Interface Requirements

The contractor shall provide a user interface that includes, but is not limited to, the following elements:

• Primary non-administrative user interface via web browser

• Administrative access can be provided over Secure Web Browser or Command Line Interface

• Support most recent versions of Google Chrome, Firefox, Safari and Microsoft Edge (Chromium based)

• Support for mobile access via responsive design

The Library has a responsibility to ensure an equitable user experience for both staff and researchers with disabilities. At a minimum the solution and all submitted documentation must:

· Meet or exceed applicable Revised Section 508 Standards and WCAG 2.1 A and AA standards0F

1 without the use of accessibility overlay technology. Overlays include third-party applications which use Javascript to alter the product interface.

· Support the creation of accessible content. Any parts of the solution that allow for content creation must meet or exceed ATAG.1F

· Allow seamless compatibility with assistive technology, including screen readers like Jaws, NVDA, VoiceOver, etc.

· Include reference guides and/or customer service support for users of assistive technology using the platform.

The vendor must:

• Designate a point of contact for accessibility issues

• Provide Voluntary Product Accessibility Template (VPAT) or similar accessibility conformance report in requested format within 90 days of request.

• Fix accessibility issues found after contract award within 90 days of reporting

• Fix accessibility issues found after deployment of new versions, features, and other changes to the product. Issues must be resolved within 90 days of reporting.

C.3.13.8. Security Requirements

The LCAP solution must meet the following security requirements:

• Security controls that are confirmed to meet the most current version of the LC Enterprise Security Standards and Guidance

• NIST SP 800-53 with an accepted Assessment and Authorization (A&A)

• FedRAMP Moderate certified cloud hosting environment. Solutions that are not yet FedRAMP-certified may submit a Service Organization Control (SOC) SOC-1 report for review.

• Vendor must support ATO process for Library Applications

• Zero Trust Remote access Model for user access across internet

• Vendor must provide Patches to Mitigate Security Findings within the Time Specified (high/critical= 30 days;

mediums=180 days; low=365 days to remediate).

C.3.13.9. Development

1 See: https://www.access-board.gov/ict and https://www.w3.org/TR/WCAG21

2 See: https://www.w3.org/TR/ATAG20 https://www.w3.org/TR/WCAG21 https://www.w3.org/TR/ATAG20

The Contractor shall provide development services as needed to meet the Library’s requirements. Development shall be conducted following an iterative methodology with regular opportunities for communication, application review, and feedback in accordance with the contractor’s proposed Project Plan and Quality Assurance Surveillance Plan. The Contractor shall maintain, execute, and provide updates to a product backlog accessible to the COR and product owner within the Library’s JIRA application or an alternate application to be hosted by the contractor. The application will include all technical and functional user stories, bugs, and tasks to determine required subject matter experts or other resources needed to participate in upcoming sprints and to track successful completion of all work.

C.3.13.10 Quality Assurance

The Contractor shall propose and adhere to a Quality Assurance Surveillance Plan (QASP) to address the roles and responsibilities of all members of the LCAP implementation team, identifies the performance objectives, defines the methodologies used to monitor and evaluate the contractor’s performance, describes quality assurance documentation requirements, and describes the analysis of quality assurance monitoring results. The QASP will be incorporated into the resulting contract and/or order(s).

C.3.13.11. Business Continuity and Disaster Recovery

The LCAP solution must meet the following business continuity and disaster recovery standards:

• Implement processes and procedures to verify business continuity in the event of any interruption of services.

• Be recoverable within the 24-hour Recovery Time Objective (RTO) and the 24 hour Recovery Point Objective (RPO).

• Undergo an annual Disaster Recovery (DR) tabletop exercise to verify the steps necessary to recover the system within the 24 hour RTO and the 24 hour RPO.

• Undergo an annual DR exercise to verify it can be recovered within the 24-hour RTO and the 24-hour RPO.

• Have a Disaster Recovery Plan which is reviewed and updated annually based on the results of the annual DR exercise and DR tabletop exercise. The system shall have an After Action report that details the results of the annual DR exercise including any incidents and/or corrective actions made to the DR plan.

• Undergo technical and functional validations during the annual DR exercise to verify all network, data and application configurations are operational prior to handing it over for client testing.

C.3.13.12. System Performance Requirements

The Contractor shall identify system performance targets agreed to by the stakeholders such as:

• Availability or uptime – the application availability to the end user for example ‘at all times, except during planned maintenance.’ It must not fail within the target level of concurrency or throughput.

• Concurrency – calculated based on an hourly figure

• Throughput – measured in hits or page views per-minute or per second

The Contractor shall identify session data requirements such as:

• a proof of concept (POC) exercise creating a performance test script that exercises key transactions to gain session data

• scripting test data requirements

• provides a technical evaluation of the performance testing tool

C.5. Other Pertinent Information

C.5.1. Government Furnished Property

The Library shall provide identification cards for contractor staff to enable their access the Library of Congress buildings. The Library shall provide work space, telephone and computer as defined at the task order level. Network access will be made available as needed for discovery of interface requirements.

C.6. Key Personnel

The following positions are considered key personnel for the LCAP:

Program Manager. The contractor shall provide a Program 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 Program Manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The program manager or alternate shall be available between 8:00 a.m. to 4:30 p.m. EST Monday through Friday except Federal holidays or when the government facility is closed for administrative reasons.

The Contractor shall provide program management of this contract and all task orders issued hereunder to include, but not limited to:

o Quality control of services and deliverables.

o Planning, implementation, and reporting on task orders.

o Monthly detailed invoicing by account numbers.

o Periodic meetings with business owner staff and the Contracting Officer Representative (COR) to discuss contract issues and the status of the work streams, documentation and minutes of key discussion points/decisions.

o Management of contractor and subcontractor on-boarding and exiting processes based on Library procedures, including any required background investigations.

o The contractor will provide a Quarterly Status Report (QSR) to the COR regarding performance on each active order under this contract. The QSR may be in a contractor chosen format, but shall include at minimum a summary description of each active order, the obligated value and potential value (including any options), period of performance, schedule of deliverables identifying which have been completed and which are due, and any outstanding issues.

030ADV22R0036 0004 Section J

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

SECTION J - LIST OF ATTACHMENTS

Below is a table listing all attachment included with this solicitation and the category/submission volume they are associated with:

End of Document

Title Date # of pages

Solicitation

Attachment J1- Questions 04/05/2022 N/A

Attachment J13 - Answers 05/23/2022 N/A

Attachment J13.1 - Additional Answers 06/06/2022 N/A

Technical Approach Volume

Attachment J2 – Statement of Objectives for Task Order 05/23/2022 7

Attachment J3 – Mandatory Requirements for Task Order 04/04/2022 N/A

Attachment J4 – Additional Requirements Analysis RTM 04/04/2022 N/A

Attachment J5 - Agile SDLC at the Library 04/05/2022 4

Attachment J6 – Library PMLC and SDLC 04/05/2022 11

Attachment J7 – QASP Information 04/05/2022 6

Attachment J8 – Task Order SOW (Example) 04/05/2022 9

Attachment J9 - Selected Library Statistics and Projections 04/11/2022 2

Attachment J12 - Sample Layout and Content for Notices and Print Products 05/19/2022 3

Attachment J14 - Attachment J14 - Information Technology Security Directive 5- 410-1_v3.7_12072021 06/06/2022 143

Past Performance Volume

Attachment J10 - Past Performance Questionnaire_LCAP 04/05/2022 8

Price Volume

Attachment J11 - Pricing Workbook 04/05/2022 N/A