SOW USCO Index Data 2026-COP-0018.docx
DOCX document 28 KB Posted
- Attached to
- Index Data Support
- Solicitation number
- 030ADV26Q0126
- Issued by
-
Library of Congress
About this file
This is a Statement of Work (SOW) for ongoing software maintenance and support services for the Library of Congress United States Copyright Office. Index Data LLC developed and maintains three custom software systems: the eCO Receipts Public Interface, Masterkey Metasearch Federated Search application, and a Z39.50 gateway that provide search and access functionality for Copyright bibliographic data. The contractor's scope includes reviewing and analyzing defects, modifying software to correct bugs, providing technical support and bug fixes, and updating the interface to add new database targets as needed. The core applications utilize tools including zSQLgate, Z39.50 SRU and SRW protocols, Pazpar2 metasearch engine, YAZ Toolkit, C/C++, Perl, HTML/JavaScript, and XML.
The contract is a firm-fixed-price sole source award with a base year period of performance from June 12, 2026, to June 11, 2027, followed by four optional one-year periods extending through June 11, 2031. Service level agreements establish support hours from 8:30 AM to 5:00 PM EST Monday through Friday (excluding federal holidays), with a 24-business-hour response time and commitment to resolve software maintenance issues through bug fixes, patches, and updates while minimizing system impact. Support is limited to technical how-to questions and bug fixes only, excluding extended instruction beyond 15 minutes, analytical assistance, or enhancements constituting new functionality. All technical staff are designated as key personnel requiring 30 calendar days' advance written notification for any reassignments, with a maximum of three Library points of contact designated for communication, all facilitated through the Contracting Officer's Representative.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Index Data JA USCO FY26_Redacted.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Library of Congress United States Copyright Office (USCO) Index Data
2026-COP-0018
1. OVERVIEW / BACKGROUND
Index Data LLC custom built, developed and successfully implemented two software applications, eCO Receipts Public Interface and AD MetaSearch and a custom Z39.50 gateway to access the underlying Oracle Siebel database for the Library of Congress’ United States Copyright Office in 2009. These applications provide access and search functionality for Library patrons, Copyright staff and LC Recommending Officers to Copyright bibliographic data.
The MasterKey platform, which is the underlying tool in the Metasearch software, was in production in Library Services as a federated search capability serving staff and meeting the needs of the general public searching Library databases.
2. SCOPE
The contractor shall provide ongoing support for Copyright’s maintenance of its customized software installation of two applications and one gateway: eCO Receipts Public Interface and Masterkey Metasearch Federated Search and the Z39.50 gateway.
3. REQUIREMENTS
The contractor shall provide maintenance that includes the following:
• Review and analysis of defects reported, and changes required, scope and level of effort
• Modify existing software to correct bug errors.
• Provide answers to specific technical how-to questions/concerns and bug fixes.
· Update the interface to add new database targets as needed
The core application was developed by Index Data for searching Library bibliographic and Copyright registration data through a customized materialized view Oracle database, The search user interface can be used for multiple search targets. The main searching is done by the Pazpar2 engine that was created and developed by Index Data. The following are tools and software that were used to develop and maintain these core applications:
· zSQLgate program
· Z39.50 SRU and SRW
· Pazpar2 (Metasearch Engine)
· YAZ Toolkit
· C/C++
· Perl
· HTML/JavaScript
· XML
4. SCHEDULE OF EVENTS/DELIVERABLES
| CLIN |
| Description of Event/Deliverable |
| Period of Performance |
| 0001 |
| Software support for Index Data software Base Year |
| 06/12/2026 – 06/11/2027 |
| 1001 |
| Software support for Index Data software Option Yr I |
| 06/12/2027 – 06/11/2028 |
| 2001 |
| Software support for Index Data software Option Yr II |
| 06/12/2028 – 06/11/2029 |
| 3001 |
| Software support for Index Data software Option Yr III |
| 06/12/2029 – 06/11/2030 |
| 4001 |
| Software support for Index Data software Option Yr IV |
| 06/12/2030 – 06/11/2031 |
5. SERVICE LEVEL AGREEMENTS
Support under this contract covers answers to specific technical how-to questions/concerns with bug fixes only. Note: It does not cover extended instruction beyond 15 minutes on how to use the software or perform various administrator functions, analytical help determining the best way to use the software, or enhancements or configuration changes that are considered new functionality.
· Support hours are from 8:30 AM – 5:00 PM EST Monday – Friday (excluding Federal holidays)
· Response Time – within 24 business hours
· Resolve Time – Software maintenance as a product includes the publishing of bug/defect fixes that could be routine or emergency types via patches and updates/upgrades in function and technology to maintain the operability and usability of the software product. Furthermore, the contractor shall provide the greatest amount of lead time as reasonable to minimize the impact to usability and accessibility of the systems.
· The number of Library Technical Points of Contact (POC) shall not exceed three (3) LOC staff.
6. TESTING AND QUALITY ASSURANCE
Quality assurance will be achieved through establishing and agreeing upon scope for each bug deliverable, adhering to LOC SDLC complying with internal contractor review and stakeholder, USCCO, and COR review.
7. KEY PERSONNEL
All technical staff assigned to this effort shall be considered key personnel. In the event of key personnel reassignment, removal, or resignation, the Contractor shall provide written notification at least 30 calendar days in advance to the designated CO and COR. This notification, at a minimum, shall include a justification statement (including proposed replacements/substitutions) in sufficient detail to permit evaluation of the impact of the proposed change on the program and its schedule. The Contractor shall make no replacement of key personnel without prior written consent by the CO. The list of personnel (specified in an attachment to the Schedule of this contract) may, with the consent of both parties to this contract, be amended from time to time during the course of the contract to add or delete personnel, as appropriate.
| The Contractor shall identify individuals who will support the agreement. The contractor shall notify the COR one week prior to non-availability. Contractor’s away-time should not negatively impact the timely completion of a bug fix especially in the event of an emergency fix. |
| To simplify communication, all contact related to the Agreement between Index Data and the Customer must be facilitated by the COR. |
(End of Performance Work Statement / Statement of Work)
File details come from the government source that posted it. Updated .