2. RFP 040ADV-26-R-0025.pdf

31b. NAME OF CONTRACTING OFFICER (Type or print) 30c. DATE SIGNED

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30.

1. REQUISITION NUMBER

2. CONTRACT NUMBER

3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER

5. SOLICITATION NUMBER

040ADV-26-R-0025

6. SOLICITATION ISSUE

4/14/26

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

WEBB, JASMIN A

b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

5/14/26 @3:00PM EST

9. ISSUED BY CODE GPO 10. THIS ACQUISITION IS UNRESTRICTED OR SET ASIDE: 0 % FOR:

GPO

732 North Capitol St NW Washington, DC, 20401, US

11. DELIVERY FOR FREE ON

12. DISCOUNT TERMS

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

(SDVOSB)

13a. THIS CONTRACT IS A

WOMEN-OWNED SMALL

BUSINESS (WOSB)

ECONOMICALLY

DISADVANTAGED

WOMEN-OWNED SMALL

BUSINESS (EDWOSB)

8(A)

13b. RATING

NORTH AMERICAN

INDUSTRY CLASSIFICATION

STANDARD (NAICS):

SIZE STANDARD:

BOARD (FOB) DESTINATION RATED ORDER UNDER 14. METHOD OF SOLICITATION REQUEST

UNLESS BLOCK IS MARKED

SEE SCHEDULE

THE DEFENSE PRIORITIES

AND ALLOCATIONS

SYSTEM - DPAS (15 CFR 700)

REQUEST

FOR QUOTE

(RFQ)

INVITATION

FOR BID

(IFB)

FOR

PROPOSAL

(RFP)

15. DELIVER TO

See Schedule

CODE 16. ADMINISTERED BY CODE

Same As Issuing Office

17a. CONTRACTOR/

OFFEROR

CODE FACILITY

CODE

18a. PAYMENT WILL BE MADE BY CODE GPO INVOICES

GPO INVOICES

U.S. Government Publishing Office (GPO) Comptroller, North Capitol & H Streets, NW, Mail Stop: FMCS Washington, DC, 20401, US

TELEPHONE NUMBER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED SEE ADDENDUM

19.

ITEM NUMBER

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA

26. TOTAL AWARD AMOUNT (For Government Use Only)

27a. SOLICITATION INCORPORATES BY REFERENCE (FEDERAL ACQUISITION REGULATION) FAR 52.212-1, 52.212-4. FAR 52.212-3

AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH

AND DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND

ON ANY ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS

SPECIFIED

29. AWARD OF CONTRACT: REFERENCE OFFER

DATED . . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print)

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 11/2021)

Prescribed by GSA - FAR (48 CFR) 53.212

19.

ITEM NUMBER

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED:

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELPHONE NUMBER OF AUTHORZED GOVERNMENT REPRESENTATIVE

32g. EMAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

36. PAYMENT

COMPLETE PARTIAL FINAL

37. CHECK NUMBER

PARTIAL FINAL

STOCK RECORD (S/R) 40. PAID BY

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER

42a. RECEIVED BY (Print)

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE 42b. RECEIVED AT (Location)

42c. DATE RECEIVED (MM/DD/YYYY) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 11/2021) BACK

TABLE OF CONTENTS:

1. Listing of Incorporated Purchase Requisitions

2. Section B - Supplies or Services and Prices/Costs

3. Section C - Description/Specifications/Work Statement

4. Section D - Packaging and Marking

5. Section E - Inspection and Acceptance Terms

6. Section F - Delivery or Performance

7. Section G - Contract Administration Data

8. Section H - Special Contract Requirements

9. Section I - Contract Clauses

10. Section J - List of Documents, Exhibits, and other Attachments

11. Section K - Representations, Certifications, and Other Statements of Offerors

12. Section L - Instructions, Conditions and Notices to Offerors

13. Section M - Evaluation Factors for Award

1. Listing of Incorporated Purchase Requisitions

Incorporated Purchase Requisition Numbers:

2. Section B - Supplies or Services and Prices/Costs

Item Number Base Item

Number Supplies/Services Quantity Unit

0001 Replace the Catalog of U. S.

Publications (CGP) Aleph ILS

System.

12 Mth

Contract Type:Firm Fixed Price Unit Price Extended Price

Description:

Purchase Requisitions

IDC Type: Not Applicable

Supplies/Services Quantity Unit

1001 0001 Post-implementation hosting and technical support

12 Mth

Contract Type:Firm Fixed Price

Option: 1 Option Time Date: 6/1/27 Option Time Duration: 364 Option Time Units: Days

Supplies/Services Quantity Unit

2001 0001 Post-implementation hosting and technical support

12 Mth

Contract Type:Firm Fixed Price

Option: 2 Option Time Date: 6/1/28 Option Time Duration: 364

Supplies/Services Quantity Unit

3001 0001 Post-implementation hosting and technical support

12 Mth

Contract Type:Firm Fixed Price

Option: 3 Option Time Date: 6/1/29 Option Time Duration: 364

Supplies/Services Quantity Unit

4001 0001 Post-implementation hosting and technical support

12 Mth

Contract Type:Firm Fixed Price

Option: 4 Option Time Date: 6/1/30 Option Time Duration: 364

3. Section C - Description/Specifications/Work Statement

The U.S. Government Publishing Office

Library Services & Content Management Catalog of U.S. Government Publications Migration Statement of Objectives

TABLE OF CONTENTS

• Section 1.0: Catalog of U.S. Publications Migration Objectives Overview

• Section 2.0: The Current System and Environment

• Section 3.0: Justification for and the Nature of the Changes

• Section 4.0: Concepts for the Proposed System, including Key Project Objectives and Key Assumptions

• Section 5.0: Key Deliverables

• Section 6.0: Performance Requirements and Expectations

• Section 7.0: Deliverables/Deliverable Schedule

• Section 8.0: Government Furnished Property/Information

• Section 9.0: Attachments

OVERVIEW

This document has been created to describe the current state and the desired state for the Catalog of U.S.

Publications system and application functionality.

Identification

This document outlines the Statement of Objectives (SOO) for migrating the current Catalog of U.S. Publications (CGP) data, existing custom indexes, services, and replace federated search functionality for federal databases (MetaLib). It focuses on replacing outdated systems and improving related work processes.

Document Overview

The purpose of this SOO is to describe the systems and work processes required to replace the Catalog of

U.S. Publications (CGP). The SOO document is intended to communicate to a vendor all the necessary information to submit a proposal for this implementation. It describes the current work processes and legacy systems, desired state, implementation objectives and assumptions, key deliverables, and performance expectations.

1.0 Catalog of U.S. Government Publications Overview

This document has been created to describe the current state and the desired state for the Catalog of U.S.

Publications system and application functionality.

1.1 Identification

This document outlines the Statement of Objectives (SOO) for migrating the current Catalog of

U.S. Publications (CGP) data, existing custom indexes, services, and replace federated search functionality for federal databases (MetaLib). It focuses on replacing outdated systems and improving related work processes.

1.2 Document Overview

The purpose of this SOO is to describe the systems and work processes required to replace the Catalog of U.S.

Publications (CGP). The SOO document is intended to communicate to a vendor all the necessary information to submit a proposal for this implementation. It describes the current work processes and legacy systems, desired state, implementation objectives and assumptions, key deliverables, and performance expectations.

The core sections of the SOO are:

Section 2 – A detailed description of the current system Section 3 – Justification for and the nature of the change Section 4 – System Scope & Objectives of the proposed system Section 5 – List and description of Key deliverables

Section 6 – Performance requirements

Section 7 – Deliverables/Deliverable Schedule

Section 8 – Government furnished property/information Section 9 – Attachments

The intended audience for this document is the management and Library Services and Content Management (LSCM) staff

1.3 The Catalog of U.S. Government Publications

GPO uses the Aleph ILS system as the primary infrastructure for its technical services functions in support of the Cataloging & Indexing (C&I) and Federal Depository Library (FDLP) Programs, as required by Title 44 of the U.S.

Code. The GPO ILS is currently comprised of the cataloging module, and Online Public Access Catalog (OPAC), with capabilities for circulation, serials, and acquisitions. The OPAC, which GPO calls the Catalog of U.S.

Government Publications (CGP), strives to be a comprehensive and authoritative national bibliography of Federal Government publications and is a central destination for both the public and FDLP library searchers. The CGP also serves the Federal Depository Library community through record sharing and services such as the Z39.50, New Titles Reports, FDLP login page, FDLP Data Manager application, and GPO GitHub repository.

The ILS contains MARC21 records, descriptive metadata generated by LSCM staff following international standards, for Federal Government publications dating from the 1700s, and is updated daily with new and enhanced records. In addition, GPO is currently involved in a multi-year project to increase access to approximately 1.2 million pre-1976 titles in the CGP.

The next generation Library Services Platform (LSP) will enable Library Services & Content Management (LSCM) to improve its internal organizational efficiencies, while leveraging new technological features and functionality in its ability to perform the statutorily authorized functions of the Federal Depository Library Program (FDLP) and the cataloging and Indexing Program (C&I) for its global customer-base.

1.4 Attachments

• High-Level Functional Requirements

• Current As-Is To Be System Architecture

• LSCM/CGP Workflow Diagram

2.0 The Current System and Environment

2.1 Current Catalog of U.S. Government Publications

GPO uses the Aleph ILS system as the primary infrastructure for its technical services functions in support of the Cataloging & Indexing (C&I) and Federal Depository Library (FDLP) Programs, as required by Title 44 of the U.S.

Code. The GPO ILS is currently comprised of the cataloging module, and Online Public Access Catalog (OPAC), with capabilities for circulation, serials, and acquisitions. The OPAC, which GPO calls the Catalog of U.S.

Government Publications (CGP), strives to be a comprehensive and authoritative national bibliography of Federal Government publications and is a central destination for both the public and FDLP library searchers.

The CGP’s federated-search tool e.g. MetaLib that searches multiple U.S. Federal government databases (including the CGP), retrieving reports, articles, and citations while providing direct links to selected resources available online. It is an Ex Libris-product backed in part by their Primo Central. Metalib resides on Primo Classic architecture and is currently the underlying technology of LSCMs’ DiscoverGov application.

The CGP also serves the Federal Depository Library community through record sharing and services such as the Z39.50, New Titles Reports, FDLP login page, FDLP Data Manager application, and GPO GitHub repository.

The new Library Services Platform (LSP) will enable Library Services & Content Management (LSCM) to improve its internal organizational efficiencies, while leveraging new technological features and functionality in its ability to perform the statutorily authorized functions of the Federal Depository Library Program (FDLP) and the cataloging and Indexing Program (C&I) for its global customer-base.

2.2 Operational Policies and Constraints

Some of the Government Publishing Office’s policies and constraints include:

• Hours of operations of the system: 24/7

• Type of personnel who use the system: Library and Content Management Staff

• Type and/or quantity of hardware required for system operations: Personal Computers, laptops, networked hardware (e.g., printers), servers

• Operational or user facilities and work areas: GPO Central Office and Regional Procurement offices

• Other Constraints: None noted at this time

2.3 Description of the Current Legacy System

• ILS (Integrated Library System): Our current ILS is a commercial-off-the-shelf (COTS) library services software application based on a multi-tier architecture and client/server model, connecting to the Oracle relational database through a middleware. It is designed to manage library acquisitions, cataloging, circulation, financial, and inventory tracking. The ILS maintains all bibliographic metadata for items in the Cataloging and Indexing Program and items distributed to the depository libraries. The ILS currently contains bibliographic records from approximately 1700s to the present.

• GPO’s bib library is medium sized: currently approximately 2.5 million BIB records, 312,480 AUT records, high 700K Item records, and close to 925K holding records and growing. We have about 325K bibliographic records that have PURLs. We also have a variety of indexes (Keyword, Direct and Heading). For the BIB database we currently have 45 direct indexes, 39 heading indexes, and 78-word indexes in use. We also have 312,480 Authority headings.

• We have about 75-100 staff, public users and contractor staff who may need a variety of levels, permission and access to our ILS system. We average about 50 million hits on the public Catalog of U.S.

Government Publications (CGP) per year, have thousands of users download hundreds of thousands of records via our Z39.50 (some are accessed through the DiscoverGov/MetaLib federated search interface).

• Operational environment o Amazon Web Services approved Federal Risk and Authorization Program (FedRAMP) Third Party hosted system environment o ILS data files reside on the ILS Network provided by PTFS that is hosted in Amazon Web Service’s Elastic Compute Cloud (AWS EC2).

o The Integrated Library System (ILS) is comprised of dynamic HTML pages and a back-end Oracle and MySQL databases. The front-end applications and web pages and the back-end database reside on the Red Hat Linux operating system virtual servers.

o Access to the ILS environment, application and database is only available to authenticated Progressive Technology Federal Systems (PTFS), Ex Libris and Library Services & Content Management (LSCM) users.

LSCM ILS administrators access the ILS system using PuTTY (an SSH client), and VPN with a dedicated IP address.

o ILS data files reside on the ILS Network provided by PTFS that is hosted in Amazon Web Service’s Elastic Compute Cloud (AWS EC2). PTFS administrators manage many of the security aspects of the ILS network. The ILS network provides a security partition that allows authorized PTFS administrators to manage ILS network resources without impacting the AWS EC2 network.

o The ILS network consists of three environments, Testing, Production, and Disaster Recovery (DR), all running on a Linux platform. The hardware and operating system of the ILS network is maintained by the PTFS contractor and housed at Amazon AWS US-East1 cloud facility. Access to the ILS is limited to PTFS, Ex Libris and LSCM ILS Administrators using SSH. AWS Facility hosted firewalls are managed by AWS and PTFS contractor. Specific roles and responsibilities of both PTFS and GPO are described in the ILS hosting contract and Statement of Work (SOW) signed by both PTFS and GPO.

o All Internet-based inbound traffic to ILS is only permitted through a firewall segmented demilitarized zone (DMZ) network provided by Amazon AWS. In all cases, this traffic should be limited to only ports necessary for GPO and PTFS’s business requirements.

• Capabilities, functions and features of the current system o The Online Public Access Catalog (OPAC) is called the Catalog of U.S. Government Publications (CGP) o The z39.50 server, a server that allows depositories to download records o The Apache server, used for the ILS system’s web pages o The circulation module, used for login access to the CGP o The PC server, used for sustaining in-house/staff users’ connections through the Graphical User Interface

(GUI) clients to the ILS server, and execution of various acquisitions o The acquisitions/serials, cataloging, and administration modules o Primo Classic, a web presentation layer with discovery capabilities, is a stand-alone licensed Ex Libris product e.g. Software as Service (SaaS) solution, hosted by Ex Libris in a multitenant environment.

o GPO’s implementation is called DiscoverGov. DiscoverGov interoperates with the CGP data via an automated process using SFTP files and processes and is configured to allow for integration with MetaLib federated searching and is considered a service of the CGP.

MetaLib, a stand-alone licensed Ex Libris product that enables federated searching across databases configured within MetaLib.

2.4 Users and Other Involved Personnel

• LSCM System Librarians

• LSCM personnel who create and maintain U.S. Cataloging Records

• Technical support staff both internal and external

• General Public and Federal Depository Library end-users

2.5 Description of Support Environment

• This application (ILS) is hosted by a contractor (PTFS) under contract to GPO. The underlying computing elements are hosted by Amazon Web Services (AWS).

3.0 Justification for and the Nature of Changes

3.1 Drivers for Change

The Library Services & Content Management Division has a requirement to acquire a Firm/Contractor that shall migrate GPO’s/LSCM’s Catalog of U.S. Government Publications to a more secure third-party supported platform.

The Superintendent of Documents (SuDocs) recognizes the pressing need to migrate and modernize its library infrastructure to ensure the seamless delivery of services and access to information for the Federal Depository Libraries and the American public.

On June 24th, 2025, LSCM management was notified that the current provider of its ALEPH Integrated Library System has decided to transfer the Aleph Library System to Limited Support effective date of June 24th , 2025 and, shall cease full-support at the end of fiscal year 2026. As a result, upcoming renewals for Aleph will only be extended for one year and will require the execution of a Limited Support Addendum which will contain language as follows:

Software Support/Security. Client acknowledges that Clarivate’s Aleph Library System will be entering into limited support. For continued Aleph support, Client agrees that Clarivate will not be responsible for providing any additional Aleph related security certifications, endorsing or complying with VPAT/Accessibility obligations, or investigating or fixing any security related vulnerabilities, bug fixes, and that any Support provided related to Aleph functionality issues will be limited in nature.

To this end, LSCM is currently seeking to migrate from the current technical host platform to a more robust system for continued hosting of the Catalog of U.S. Publications (CGP). This new platform is to provide enhanced functionality, greater sustainability, and future-proof capabilities. This strategic pursuit is not just in response to immediate challenges but a proactive measure to ensure long-term efficiency and security of library operations.

3.2 Description of Desired Changes

Library Services & Content Management is looking for a dependable and skilled vendor to propose, implement, configure, maintain, and support a modern, high-performance Library Services Platform (LSP) for its Catalog of U.S. Government Publications (CGP). Currently, LSCM's CGP operates on ExLibris’s Aleph 500 Integrated

Library System (ILS) platform. This system is crucial for Library Services & Content Management to achieve its mission goals of providing improved services to the Federal Depository Libraries and the general public.

The goal of this request is to identify and acquire a sustainable technical solution for updating and modernizing LSCM’s Catalog of U.S. Government Publications system. Additionally, LSCM aims to redesign and improve internal processes, enhance system security, and replace vulnerable legacy systems in the most cost-effective way.

The intended system shall be a public-facing, online Library Services Platform (LSP) that operates in real-time or near-real-time. This new LSP must feature a graphical user interface for an online catalog, providing access to various print and non-print materials (such as monographs, serials, audio-visual items, manuscripts) available in library collections. It should also offer access to remotely-hosted bibliographic, text-based, and multimedia electronic databases and information resources relevant to users. Additionally, the platform should ensure compatibility with both internal and external systems.

The new LSP must be deployed on a FedRAMP-certified platform, a FedRAMP-compliant SaaS solution, or an equivalent SOC-II certified platform. It should include geographic separation for backup snapshots and support multiple environments: Test, Development, Production, and Disaster Recovery.

4.0 System Scope & Objectives

4.1 Scope and Objectives

The technical solution should be designed to facilitate core LSCM services and cataloging requirements.

Presently, the daily operations of the LSCM system involve the use of specific functions and modules, as outlined below:

• Acquisitions functionality Module and/or Component

• Cataloging Module and/or Component

• Authority and Authority Control

• Serials/Continuing Resources Module and/or Component

• Preservation and Collection Management Module and/or Component

• Online Public Access Catalog (OPAC)/Web Presentation Layer (WPL)/Discovery Module and/or Component

• Indexing Module and/or Component

• Data Reporting Module and/or Component

• Data Statistics Module and/or Component

• Data Analytics Module and/or Component

• External System Interoperability Module and/or Component

• Union Catalog Module and/or Component

• Operating System Reporting Module and/or Component

• Library System Statistics Module and/or Component

• Library System Analytics Module and/or Component

• User Classification and Management Module and/or Component

• Services Sub Module and/or Component

• Metadata Management

• Workflow Management

• Data Export and conversion

• Data Import and Conversion

• Notifications

• Profiles Sub Module and/or Component

4.2 Objectives

The objective of the new system is to deliver a reliable, sustainable technical solution that updates and modernizes LSCM’s Catalog of U.S. Government Publications and proposal should address the following factors:

Technical Upgrades and Performance Goals:

• Adopt modern architectural approaches, utilizing cloud-based, FedRAMP platform to enhance data processing speed and enable cost-effective scalability.

• Facilitate comprehensive system interoperability by aligning the new platform with established discovery layers, institutional repositories, and the Government Publishing Office’s IT infrastructure.

• Strengthen system security and privacy through advanced authentication protocols that safeguard user information.

Ensuring Quality in Data Migration and Integrity

• Comprehensive Data Transfer: Execute a systematic migration of bibliographic and statistical records 99.9% accuracy while reducing the risk of data loss.

• Data Cleansing and Normalization: Evaluate and enhance current datasets to conform with the new system’s formatting standards, including MARC, MARCXML, .MRC, BIBFRAME, Dublin Core, CSV and Items\Holdings formats etc..

• Metadata Preservation: Identify and protect crucial metadata, maintaining the integrity and authenticity of library records.

Enhancing Operational Efficiency and Streamlining existing LSCM Workflow Processes

• Streamline Library Workflows: Reevaluate and optimize processes for acquisitions, cataloging, circulation, and serials management to maximize the benefits of the new system.

• Resource Management Integration: Unify physical and electronic resource management into a single interface.

• Improved Analytics and Reporting: Advance the generation of service-level metrics and turnaround benchmarks through robust reporting functionalities.

Optimizing User Experience and Advancing Service Quality

• Enhanced Discovery: Expand search capabilities for staff and end-users, enabling access to various formats such as electronic resources, federal databases, and digital materials.

• Minimizing Service Downtime: Implement the transition with a deliberate "go live" schedule to reduce disruptions for users engaged in research.

• Mobile-Friendly Access: Deliver a responsive, mobile-accessible Discovery layer for staff and end-users.

Employee Support and Change Management

• Comprehensive Training: Provide a thorough live-training program to ensure all staff are proficient in the new system’s individual modules and overall functionality.

• Change Management Support: Facilitate staff adaptation to the new workflows and processes by offering resources that address operational impacts during the transition.

• Clear Documentation: Create updated internal documentation and service level agreements (SLAs) for the new system environment.

4.3 Operational Policies and Constraints

• Hours of operation: 24/7 because this is the inventory used by IT&S for maintaining all systems within

GPO, it must be available at all times.

• Regulatory Compliance and Administration: The system must comply with statutory and regulatory Requirements when processing transactions and providing decision support capabilities.

4.4 User Classes and Other Involved Personnel

• LSCM Managers and supervisors

• LSCM System Librarians

• LSCM personnel who create and maintain U.S. Cataloging Records

• Technical support staff both internal and external

• General Public and Federal Depository Library end-users

4.5 Key Assumptions

While not all-inclusive, the following is a summary of the key LSCM assumptions that must be considered in the CGP Migration Implementation Plan and applicable implementation tasks and deliverables as it relates to:

resources, timelines, scope, stakeholders.

Key Areas of Assumptions Resources & Team:

It is assumed that skilled team members are available and dedicated.

It is assumed sufficient budget and necessary materials/equipment are accessible. It is assumed that key personnel won't leave or be reallocated during the project.

Scope & Requirements:

• It is assumed that provided Line-Item requirements will be reviewed should be reviewed by the vendor and appropriate LSCM team members and are not expected to change significantly.

• It is assumed that the Project scope shall remain stable and will not be subject to major scope creep.

Timeline & Scheduling:

• Milestones will be met on schedule.

• Key approvals will be received promptly.

Technical:

• Software/hardware compatibility with existing systems holds true.

• Third-party integrations will work as expected.

• Required infrastructure (like internet connectivity) is reliable.

Stakeholders & External Factors:

• Stakeholders have consistent understanding and will provide timely feedback/approvals.

• External factors (market, regulations, vendors) remain stable.

• It is assumed that User training will include general implemented module(s) functionality training and, in the Host Test environment.

5.0 Key Deliverables

5.1 Implementation & Performance Plan

For GPO and LSCM project management and activity surveillance requirements, the successful contractor’s CGP Migration and Implementation plan/schedule will need to be provided and approved prior to implementation commencement. The plan will primarily comprise:

High-Level Project Work Breakdown Structure (PWBS):

Integrated Project Plan: Combine vendor and government project plans and milestones to include timelines and schedule for key activities and deliverables Include:

• Timelines and schedule for key activities and deliverables

• Responsible parties for each activity (e.g., Implementer, GPO/LSCM)

• Legacy systems interface requirements

• FedRAMP/IT Security compliance requirements

• Testing and validation requirements

• User training requirements

• Requirements Review and Validation: Review and validate detailed requirements with assigned LSCM personnel.

• System Design and Architecture: Develop a comprehensive design and architecture plan meeting all stated functional and system requirements.

• Platform Development: Document, build and configure the new platform and system environment based on the approved project plan and functional and system requirements.

• Data Migration: The contractor shall migrate approximately 2.5 million bibliographic records and associate metadata with a minimum data accuracy rate of 99.9%, ensuring preservation of all indexing structures and authority relationships to include Items and Holdings data.

• Testing and Quality Assurance: The vendor shall perform rigorous system testing to identify and resolve issues, prior to conducting user-acceptance testing.

• System Security Plan: Submit a documented system security plan and system characterization document that demonstrates strong security and privacy measures and effective vulnerability management in accordance with federal standards including those related to FISMA, FedRAMP, and NIST.

• Training and Documentation: Prepare detailed instructional materials for users regarding the new platform, accompanied by structured live-training sessions that clearly outline the updated system features.

• Go-Live: Successfully launch the new platform for all users.

• Post-Implementation Support: Provide post migration/implementation support and address any post-launch issues that may arise as latent issues/defects.

5.2 Users

A User Training Plan and requirements will need to be identified in sufficient time to satisfy system and application implementation requirements. Plan should include creation and delivery of all relevant training materials and documentation.

It is assumed that User Training will include general implemented module(s) functionality training and, in the Host Test environment, specific training on pre-production applications.

5.3 Systems and Work Process Documents

• Initial system/application design documentation is to

• Resultant implemented end-to-end CGP system process(es), and system architecture need to be provided

• User training materials

6.0 Performance Requirements

6.1 Orientation Briefing

Within ten (10) working days of award, the Contractor shall conduct an orientation briefing for the Government.

The Government does not want an elaborate orientation briefing nor does it expect the Contractor to expend significant resources in preparation for this briefing. The intent of the briefing is to initiate the communication process between the Government and Contractor by introducing key task participants and explaining their roles, reviewing communication ground rules, GPO work site requirements and assuring a common understanding of task requirements, assumptions, and objectives. The briefing should be essentially viewed as a “working session” with consensus and documented output and Next Steps.

The Orientation Briefing will be held at the Government’s facility (or acceptable Online equivalent), and the date and time will be mutually agreed upon by both parties.

The completion of this briefing will result in the following:

• Introduction of both Contractor and Government personnel performing work under this Task Order.

• The Contractor will demonstrate confirmation of their understanding of the work to be accomplished under this SOO.

• As appropriate, documented roles and responsibilities, Next Steps, and follow-up Action Items.

6.2 Personnel Security Requirements

Security clearance is not required in performance of this effort. GPO Visitor badges, however, will be required for performed site work. Contact the Enterprise Program office for badge assistance, personnel contact information, and facility map/directions, including parking.

6.3 Contractor Interfaces

The Contractor and/or his subcontractors may be required as part of the performance of this effort to work with other Contractors/vendors working for the Government (e.g.,Integrated Library System services). Such other Contractors shall not direct this Contractor and/or their subcontractors in any manner. Also, this Contractor and/or their subcontractors shall not direct the work of other Contractors in any manner.

The Government shall establish an initial contact between the Contractor and other Contractors and shall participate in an initial meeting at which the conventions for the scheduling and conduct of future meetings/contacts will be established. Any COR of other efforts shall be included in any establishment of conventions.

6.4 Disclosure of Information

Information made available to the contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the Contracting Officer.

The contractor agrees to assume responsibility for protecting the confidentiality of Government records, which are not public information. Each contractor or employee of the contractor to whom information may be made available or disclosed shall be notified in writing by the contractor that such information may be disclosed only for a purpose and to the extent authorized herein.

6.5 Limited Use of Data

Performance of this effort may require the contractor to access and use data and information proprietary to a government agency or Government contractor which is of such a nature that its dissemination or use, other than in performance of this effort, would be averse to the interests of the Government and/or others.

Contractor and/or contractor personnel shall not divulge, or release data or information developed or obtained in performance of this effort, until made public by the Government, except to authorized Government personnel or upon written approval of the CO. The contractor shall not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this effort. Nothing herein shall preclude the use of any data independently acquired by the contractor without such limitations or prohibit an agreement at no cost to the Government between the contractor and the data owner which provides for greater rights to the contractor.

6.6 Hours of Work

GPO on-site contractor personnel are expected to conform to normal operating hours. The GPO normal duty hours are 7:30 AM to 4:00 PM, Monday through Friday, with the exception of Federal Government holidays, with an allowance for a one-hour lunch period each day. As appropriate/required, the timeframe can be modified by the COR to accommodate contractor efforts/requirements.

Access and/or contractor personnel site presence outside of normal working hours must first be reviewed and approved by the COR. These exception requests must be made sufficiently in advance so that the COR can arrange for GPO supervision personnel to be presence with the contractor personnel. GPO assumes any performance impacts that may result from COR disapproval of the exception.

6.7 Productive Direct Labor Hours

The contractor can only charge the Government for “Productive Direct Labor Hours”. “Productive Direct Labor Hours” are defined as those hours expended by Contractor personnel in performing work under this effort. This does not include sick leave, vacation, Government or contractor holidays, jury duty, military leave, or any other kind of administrative leave.

6.8 Government Holidays

The following Government holidays are normally observed by Government personnel: New Years Day, Martin Luther King’s Birthday, Presidential Inauguration Day (metropolitan DC area only), President’s Day, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving Day, Christmas Day, and any other day designated by Federal Statute, Executive Order, and/or Presidential Proclamation.

6.9 Payment for Unauthorized Work

No payments will be made for any unauthorized supplies and/or services or for any unauthorized changes to the work specified herein. This includes any services performed by the Contractor of their own volition or at the request of an individual other than a duly appointed Contracting Officer. Only a duly appointed Contracting Officer is authorized to change the specifications, terms, and conditions under this effort.

6.10 Contractor Personnel

The Contractor shall be responsible for managing and overseeing the activities of all Contractor personnel, as well as subcontractor efforts used in performance of this effort. The Contractor's management responsibilities shall include all activities necessary to ensure the accomplishment of timely and effective support, performed in accordance with the requirements contained in the statement of work. Resumes submitted for employees assigned to perform under this statement of work shall contain documented experience directly applicable to the functions to be performed. Further, these prior work experiences shall be specific and of sufficient variety and duration that the employee is able to effectively and efficiently perform the functions assigned.

6.11 Project Manager

The Contractor shall provide a Project Manager to facilitate Government-Contractor communications. The Project Manager shall be the primary technical and managerial interface between the Contractor and the Contracting Officer’s Representative (COR) located at GPO in Washington, D.C. The name of this person, and an alternate or alternates, who shall act for the contractor when the Manager is absent, be designated in writing to the contracting officer. The Manager or alternate will have full authority to act for the contractor on all contract matters relating to daily operations.

The Project Manager or alternate must be available during normal duty hours, as specified herein, and meet with the COR, or their designees, within 24 hours to discuss problems.

The Contractor's Project Manager shall meet with the COR as regularly scheduled and/or necessary to maintain satisfactory performance and to resolve other issues pertaining to Government/Contractor procedures. At these meetings, a mutual effort will be made to resolve any and all problems identified. Written minutes of these meetings shall be prepared by the Contractor, signed by the Contractor's designated representative, and furnished by the Government within two (2) workdays of the subject meeting.

The Project Manager and alternate or alternates must be able to read, write, speak, and understand English.

6.12 Contractor Employees

Contractor personnel shall present a neat appearance consistent with normal GPO business attire and be easily recognized as contractor employees by wearing a Security Identification Badges at all times while on Government premises. When Contractor Personnel attend meetings, answer phones, and work in other situations where their status is not obvious to third parties, they must identify themselves as such to avoid creating the impression that they are government employees.

6.13 Physical Security

The contractor shall be responsible for safeguarding all government property provided for contractor use. At the end of normal duty hours and/or after normal duty hours, all government facilities, equipment and materials must be secured.

6.14 Key Controls

The contractor shall establish and implement methods of making sure all keys issued to the contractor by the government are not lost or misplaced and are not used by unauthorized persons. The contractor shall not duplicate any keys issued by the government. The contractor shall immediately report to the COR, or their designee, any occurrences of lost or duplicated keys.

In the event keys, other than master keys, are lost or duplicated, the contractor may be required, upon written direction of the COR, to re-key or replace the affected lock or locks at no cost to the government. The government may, however, at its option, replace the affected lock or locks or perform re-keying and deduct the cost of such from the monthly payment due the contractor. If a master key is lost or duplicated, the government must replace all locks and keys for that system and the total cost deducted from the monthly payment due the contractor.

The contractor must prohibit the use of keys issued by the government by any persons other than the contractor's employees. Opening of locked areas by contractor employees to permit entrance of persons other than contractor employees engaged in performance of work requirements in those areas is prohibited.

6.15 Place(s) of Performance

The work for this effort shall be performed Online, at the contractor’s location or, as alternately approved, on-site at:

United States Government Publishing Office 732 North Capitol Street NW 20401

7.0 Deliverables/Deliverable Schedule

In fulfillment of this effort, the Contractor shall complete the following deliverables. All deliverables shall be submitted to the COR, unless otherwise agreed upon. Unless otherwise specified, the Government will have a maximum of ten (10) working days from the day the draft deliverable is received to review the document, provide comments back to the contractor, approve or disapprove the deliverable(s). The contractor will also have a maximum of ten (10) working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government. All days identified below are intended to be workdays unless otherwise specified.

7.1 Project Plan (also reference Section 5.0)

The contractor shall prepare a Project Plan describing the technical approach, organizational resources and management controls to be employed to meet the cost, performance and schedule requirements for this effort.

The Project Plan shall detail the key activities and milestones, distance learning technology, allocation of staff and other resources necessary to the for successful completion of this effort. The COR shall receive the Project Plan in both hard copy and electronic form, Microsoft Word/Office Project. Based on the Project Plan, the Contracting Officers Representative (COR) will provide approval to move forward on activities planned. The contractor shall request prior approval on all activities not included in the plan or any modifications to the plan after approval has been given.

7.2 Status Reporting

The contractor shall document the efforts performed in the completion of each task in a detailed bi-Monthly Status Report due on or before the 15th and 30th of each Month.

Weekly status review sessions should also be conducted with the COR, or their designees, on a regularly scheduled basis to review progress and address/resolve any task requirements, problems, etc. The status reports shall include, at a minimum:

• Progress for the period: progress report of findings, activities and accomplishments during the reporting period, and summary of work accomplished during the reporting period and percent complete against the Project Plan.

• Activities planned for the next reporting period: planned activities, as well as the status of any/all deliverables, including planned delivery date(s) and actual and/or anticipated delivery date(s).

• Problems encountered: summary identification of any unresolved/outstanding problems, issues or delays, performance risks, and recommendations as to their resolution.

• Strategy revisions: recommended changes to include any lessons learned

7.3 Final Report

The contractor shall provide a final report to the COR, at the conclusion of this effort. The report will summarize objectives achieved, significant issues, problems and recommendations to improve the process in the future.

7.4 Final Inspection and Acceptance

Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COR.

7.5 General Acceptance Criteria

General quality measures, as set forth below, will be applied to each work product received from the contractor under this statement of work.

• Accuracy - Work Products shall be accurate in presentation, technical content, and adherence to accepted elements of style.

• Clarity - Work Products shall be clear and concise. Any/All diagrams shall be easy to understand and be relevant to the supporting narrative.

• Consistency to Requirements - All work products must satisfy the requirements of this statement of work.

• File Editing - All text and diagrammatic files shall be editable by the Government.

• Format - Work Products shall be submitted in hard copy (where applicable) and in media mutually agreed upon prior to submission. Hard copy formats shall follow any specified Directives or Manuals.

• Timeliness - Work Products shall be submitted on or before the due date specified in this statement of work or submitted in accordance with a later scheduled date determined by the Government.

7.6 Quality Assurance

The COR will review, for completeness, preliminary or draft documentation that the Contractor submits, and may return it to the Contractor for correction. Absence of any comments by the COR will not relieve the Contractor of the responsibility for complying with the requirements of this work statement.

Final approval and acceptance of documentation required herein shall be by letter of approval and acceptance by COR. The Contractor shall not construe any letter of acknowledgment of receipt material as a waiver of review, or as an acknowledgment that the material is in conformance with this work statement. Any approval given during preparation of the documentation, or approval for shipment shall not guarantee the final acceptance of the completed documentation.

7.7 Correspondence

To promote timely and effective administration, correspondence shall be subject to the following procedures:

• Technical correspondence (where technical issues relating to compliance with the requirements herein) shall be addressed to the Contracting Officer’s Representative (COR) with an information copy to the Contracting Officer (CO) and the Contract Administrator (CA).

• All other correspondence, including invoices (which proposes or otherwise involves waivers, deviations or modifications to the requirements, terms or conditions of this SOO) shall be addressed to the Contracting Officer with an information copy to the COR.

The COR is the individual within LSCM’s Project’s & Systems branch function who has overall program, project and financial responsibility for this effort. The COR supports the CO/COR during administration of this effort by:

• Making final decisions regarding any recommended rejection of deliverables

• Providing task/deliverables clarification relative to overall workload matters

• Providing advice and guidance to the Contractor in the preparation of deliverables and services

• Providing acceptance of deliverable products to ensure compliance with requirements

The COR is the individual responsible to provide technical direction to the Contractor, i.e., shifting work emphasis between areas of work; fills in details, or otherwise serves to accomplish the purposes of this effort. Technical direction shall be within the general statement of work for this effort. The COR does NOT have the authority to and may NOT issue any technical direction which:

• Constitutes an assignment of work outside the general scope of this effort

• Constitutes a change as defined in the “Changes” clause in any way causes an increase or decrease in cost or the time required for performance

• Changes to any of the terms, conditions, or other requirements of this effort

• Suspends or terminates any portion of this effort

All technical direction shall be issued in writing by the COR or will be confirmed by the COR in writing within 10 calendar days after verbal issuance. A copy of the written direction shall be furnished to the COR.

In addition to providing technical direction, the COR will:

• Pro-actively monitor the Contractor’s technical progress, including surveillance and assessment of performance, and recommend to the COR and CO, any changes in the requirement

• Assist the Contractor in the resolution of technical problems encountered during performance

• Perform inspection and acceptance or recommendation for rejection of Contractor deliverables and identify deficiencies in delivered items. This does not replace any other quality assurance inspection requirements that are specified elsewhere within this SOO.

If in the opinion of the Contractor, any instruction or direction issued by the COTR is outside of their specific authority, the Contractor shall not proceed but shall notify the COR in writing within 5 working days after receipt of any instruction or direction, with an informational copy to the CO.

8.0 Government Furnished Property/Information (GFI)

Government Furnished Property (Material, Equipment, and/or Information) is to be provided together with required performance under this effort.

As determined by mutual agreement, the Government will provide additional property that may be required in the performance of this effort.

At the request of the Government, or at completion of this effort, the Contractor shall immediately return any Government-provided property, including any…