Response to Questions 4-29-26 rev.xlsx
XLSX spreadsheet 25 KB Posted
- Attached to
- Catalog of U. S. Publications System Migration
- Solicitation number
- 040ADV-26-R-0025
- Issued by
-
Government Publishing Office
About this file
This is a Questions and Answers (Q&A) document responding to 29 questions submitted by potential offerors regarding the Catalog of U.S. Government Publications System Migration solicitation (040ADV-26-R-0025) issued by the Government Publishing Office's Library Services & Content Management (LSCM) division. The Q&A clarifies requirements for replacing the current Aleph Integrated Library System (ILS) with a new ILS or Library Services Platform (LSP), including migration of bibliographic, authority, holdings, and item records along with related metadata and indexing systems.
Key clarifications include: the Government will not disclose budget information, and offerors must propose pricing based on their technical approach; implementation is anticipated to begin June 1, 2026, with system launch targeted for end of FY26; offerors are not required to meet every requirement in Attachment J3 to be considered for award, but compliance degree will be evaluated; "Should" indicates desired but non-mandatory capabilities, while "Priority" indicates greater importance; the proposed solution must be hosted in a FedRAMP-authorized environment, though the SaaS application itself does not require separate FedRAMP certification if operating within an authorized environment; three past performance references via questionnaires are required; supplementary materials may be submitted as attachments without counting toward page limits; the contract requires Operations, Maintenance, System Administration, and Library Services Platform administration services; and offerors must clearly identify which requirements are fully met, partially met, or not met with associated assumptions or proposed alternatives in their technical proposals.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Amendment 040ADV-26-R-0025-C0001.pdf | ||
| Attachment J4_DiscGov-Combined Appendices.pdf | ||
| Updated 4-21-26 RFP 040ADV-26-R-0025.pdf | ||
| Attachment J3_ CGPM DiscoverGov Func-Reqs Appd_A.pdf | ||
| 2. RFP 040ADV-26-R-0025.pdf | ||
| 4. Attachment J1_Pricing Sheet.xlsx | XLSX spreadsheet | |
| Attachment J.2 Past Performance Questionnaire.docx | DOCX document |
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
Sheet1
| Page Number | Document Section | Sub-Section | Paragraph | Question | Government Response |
| Could you please extend the question deadline? | The Government will review and may revise the solicitation schedule via amendment | ||||
| Would the site consider a submission deadline? | The Government will review and may revise the solicitation schedule via amendment | ||||
| Can you please confirm when the new system needs to be live? The RFP states end of FY26. | The Government anticipates system implementation and transition to occur within the base year, with a target of end of FY26; however, Offerors shall propose a realistic implementation schedule as part of their technical approach. | ||||
| Is implementation expected to begin on June 1, 2026? | Yes. The anticipated period of performance start date is June 1, 2026 or date of award the project kickoff would be within ten (10) business days post award. | ||||
| Do you have a budget for this project? | The Government will not disclose budget information. Offerors shall propose pricing based on their technical approach and understanding of the requirement. | ||||
| Can you elaborate on Attachment 3 requirements "should" vs. "priority" vs. "new feature/function" - if there is an aspect we cannot meet - will our bid still be considered? Should we note this within the technical proposal. | The Government provided Attachment J3 requirements to communicate desired system capabilities and priorities. |
“Should” indicates a desired capability and is not a mandatory requirement. “Priority” identifies capabilities of greater importance and will be given more consideration during the evaluation. “New Feature/Function” represents capabilities that are not currently available but are desired for the future state.
Offerors are not required to meet every requirement to be considered for award. However, the degree to which the proposed solution meets or exceeds the identified requirements will be evaluated as part of the Technical Approach factor.
Offerors shall clearly identify within their technical proposal which requirements are fully met, partially met, or not met, and provide any associated assumptions or proposed alternatives.
| How many references would you like us to provide? The instructions indicate a ten-page limit for J2but not a set number of references | Three (3) References via Past Performance Questionnaires that should be completed by the who was awarded the contract by your company. | ||||||
| Can we submit supplementary materials (such as contract terms and conditions) as attachments to the proposal without those counting towards the page limit? | Yes. Supplemental materials such as standard terms and conditions may be submitted as attachments and will not count toward page limitations unless otherwise specified. | ||||||
| Can you describe the data that you would like to migrate to the new system? Only bibliographic records are referenced in Section 5.0, for example, do you have acquisitions, or circulation data that you would like to migrate? | The Government plans to transfer bibliographic, authority, holdings, and item records, along with related metadata and indexing systems. Offerors are expected to submit a thorough data migration strategy. Migration of specific circulation, order/acquisition, or patron record data is not currently anticipated. | ||||||
| Can you describe your preservation needs? For example, do you require digital preservation, or a means to track physical preservation activities? | The Government requires APIs that enable interaction with its current digital preservation system, as well as tracking physical materials. Offerors should explain how their API solutions fulfill these requirements. The Digital Preservation System itself is already in-service, so a new one is not necessary or required. | ||||||
| Can you provide the following metrics: • | Total number of unique e-journal titles. • | What is the total number of end users and patrons (that is, FTEs) who need access to library online services? | GPO/LSCM does not have “e-journal” in traditional sense. We have Electronic Serial/Periodical/Intergraded Resources in the CGP as Bibliographic record with Items and Holdings records. We have 46K bibs with approximately 700k number of Items records. 100 GPO/LSCM Internal Staff; 1,200 login OPAC/Discovery Users, using a 500 concurrent public access OPAC/Discovery end users license. | ||||
| 7 | 1.0 Catalog of U.S. Government Publications Overview | 1.4 Attachments | 2,3 | These paragraphs list the following items as Attachments: |
• Current As-Is To Be System Architecture
| • LSCM/CGP Workflow Diagram. These items do not appear to be provided. Will the Government please provide these items? | The Government will provide the referenced attachments via amendment. (will send additional documentation) | |||||
| 7 | 2.9 The Current System and Environment | 2.1 Current Catalog of U.S. Government Publications | 2 | Will GPO contract separately for Primo, independent of the outcome of this ILS replacement procurement? | The outcome is contingent upon the technical solution chosen. GPO remains receptive to considering a more modern alternative, should it be included in the proposed options. In the absence of a superior proposal, GPO may decide to retain Primo Classic as its public web presentation and discovery layer. | |
| 8 | 2.3 Description of the Current Legacy Environment | Operational Environment | 4,5 | These dot-points state: These dot-points state: | ||
| 1. "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. 2. 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 Is this work to be done on this migration contract? | The architecture described in the question outlines the current setup for the Catalog of U.S. Government Publications and its Aleph backend, which is hosted on the ILS network managed by PTFS within AWS EC2. During the migration contract, this existing architecture will remain operational while the new solution is developed and deployed. Once the migration is complete, the current setup will be retired. The main work associated with this contract involves migrating data and, potentially, some architectural information. Other than these elements, there should be minimal interaction with the existing architecture as part of this migration contract. | |||||
| 10 | 3 | 3.2 | 4 | If the platform is FedRAMP If the platform is FedRAMP | ||
| certified but the SaaS software is not, is this approach acceptable to the GPO? | The proposed solution should be hosted in a FedRAMP-authorized environment. The SaaS application does not need separate FedRAMP authorization if it operates within an authorized environment and meets federal security standards. The solution must be FedRAMP authorized or compliant, or have an acceptable equivalent listed in the SOO. Ideally, solutions are hosted on FedRAMP-authorized infrastructure at minimum, with any SaaS offering classified as "Low-Impact SaaS" or higher. | |||||
| 11,12 | 4.0 System Scope & Objectives | 4.1 Scope and Objectives | All | The SOO does not appear to require system administration, operation and/or maintenance. Are these services to be acquired on this migration contract? | Yes- The contract requires offerors to provide Operations, Maintenance, and System Administration and Security Services for the hosted platform. However, detailed, hands-on Application Administration for daily system operations is not needed. | |
| 14 | 6.0 Performance Requirement | 6.3 Contractor Interfaces | 1 | Are LSP Library System Administration services required under this contract? | Yes. Offerors shall include Library Services Platform (LSP) system administration as part of their proposal. | |
| 18 | 8.0 Government Furnished Property/Information (GFI) | All | This section does not list any Government Furnished Property or Information, it just discusses access to the Government's facilities. If there is any Government Furnished Property or Information, will the Government please identify what it is? | Beyond what is discuss in the SOO (data, configuration, policies, and architecture information), other than applicable updates. GFP might be provided for data and backup configuration purposes, if applicable. | ||
| 27 | L.3 Submission/ Delivery Instructions | 1) The Technical Proposal | 2 | This paragraph states, “The Government’s estimated staffing levels are provided for planning purposes only.” This information does not appear to be provided. Will the Government please provide these staffing levels? | The Government does not prescribe staffing levels. Offerors shall propose staffing levels sufficient to meet the requirements. For the estimated number of GPO/LSCM's internal users is one hundred and ten (110). For external number of end users 1,200 login OPAC/Discovery Users, using a 500 concurrent public access OPAC/Discovery end users license. | |
| 29 | L.4 Formatting Requirements | (b) Content of the Technical Proposal | 4. Contractors PFQ | It appears that the only information required for this section of the proposal is the 4. Contractor Past Performance Questionnaires. Will the Government please confirm this? If this is not the case, will the Government please provide guidance on what information is required? | Offerors shall provide completed past performance questionnaires and may include additional relevant past performance information to support their proposal. | |
| 30 | M.3 Business Price Cost Proposal Evaluation | a | 1 | This paragraph states, “The evaluation will be based upon the required Price Matrix (Attachment J.1) and the supporting narrative provided by the Offeror.” What specific information is required in the narrative” | The price narrative shall describe the basis of estimate, including pricing assumptions, cost drivers, and how the proposed pricing aligns with the technical approach and CLIN structure. The narrative should demonstrate that all required elements of the SOO are included. | |
| 30 | M5. Technical Evaluation Criteria | 1. Technical and Management Approach -Factor 1 | 1 | This section identifies topics to be addressed in proposal’s technical and management approach. Will the Government please provide guidance regarding the specific items to be discussed regarding: regarding: 1) system capabilities and architecture; and 2) platform capabilities? An example of the requested guidance is an indication of the sections of the SOO and/or “CGPM-DiscoverGov Functional Requirements” that are to be addressed. | Offerors shall address all applicable sections of the SOO and the CGPM-DiscoverGov Functional Requirements. Proposals shall clearly describe system capabilities, architecture, platform capabilities, and how the proposed solution meets or exceeds the stated requirements. | |
| 30 | M5. Technical Evaluation Criteria | 1. Technical and Management Approach -Factor 2 | 1 | There are no project management items cited in the list of topics to be addressed. Will the Government please confirm that project management does not need to be addressed, or provide guidance on what needs to be addressed, and where to place it. | Offerors shall include project management as part of their Management Approach. This includes planning, execution, oversight, and coordination of all contract activities and related documented plans and deliverables. | |
| 31 | M5. Technical Evaluation Criteria | 2. Key Personnel-Factor 2 | The last sentence of this paragraph states, “Resumes are required.” We have three questions: 1. Are resumes required for all proposed persons, or just those that the offeror deems key? 2. What specific information is required in the resumes? 3.If resumes are required for all proposed persons, will the Government please increase the page count to 20 pages? | Resumes are required for key personnel only. Resumes shall include relevant qualifications, experience, and certifications. Page limitations remain unchanged. | ||
| 31 | M5. Technical Evaluation Criteria | 4. Price Factor 4 | This paragraph states, “The Government will evaluate price reasonableness, price completeness, and alignment with technical approach.” As there is only one CLIN for the entire Implementation & | |||
| Migration solution, it is unclear how the Government will assess “price completeness” and “alignment with the technical approach”. If we are to address this in the narrative section of the Price Spreadsheet, what specific information is required to address price completeness and the alignment with the technical approach? | Price completeness will be evaluated based on whether the proposed pricing includes all elements required to meet the SOO. Alignment with the technical approach will be evaluated based on whether the proposed pricing reasonably supports the proposed solution. | |||||
| Prising sheet | Can offerors propose additional optional CLINs? | Offerors may propose optional CLINs; however, such CLINs will not be evaluated as part of the award decision. | ||||
| Pricing Sheet | In order to obtain comparable suites of training for all offerors, will the Government please provide estimates of the numbers of users, by type (i.e., LSCM Managers and supervisors, LSCM |
System Librarians, LSCM personnel who create and maintain U.S. Cataloging Records, and Technical support staff both internal and
| external) for the base year and each option year? | The Government does not currently provide detailed user estimates. Offerors shall propose training approaches based on their recommended solution and assumptions. For the estimated staffling levels of GPO/LSCM's internal staffing levels related to the proposal that may be working in and with the proposed solution would be approximately one hundred and ten (100) staff may need to access the backend. This number is just an estimate for planning purposed of number of potential users and possible training attendees. Up to five (5) GPO/LSCM Systems Admins; up to fourty (40) GPO/LSCM Metadata specailist; up to 35 other GPO/LSCM staff in various roles. For external end users about 1,200 login OPAC/Discovery Users, using a 500 concurrent public access OPAC/Discovery end users license. | |||||
| Sep-59 | Attachment J3 | Are entries listed as New Feature/Function mandatory or preferred for the new solution | “New Feature/Function” entries represent desired future-state capabilities are preferred and are not mandatory at time of award. | |||
| Sep-59 | Attachment J3 | Will the Government please explain how offerors are to use the new Feature/Function inforamtion in their proposals ( e.g., if they are not already available, are these required or preferred to be developed)? | Offerors shall identify whether such capabilities are currently available, planned, or proposed as enhancements. | |||
| Sep-59 | Attachment J3 | All items(requirements) are cited as "should" We have 3 questions:1. Is this to be interpreted that all the requirements are mandatory, or are they all Preferred (i.e., a proposal that doesn’t have to include all requirements in order to be deemed acceptable)? 2. If all items do have to be proposed, ow long does the offeror have to provide all of them (ie. is delivery within 180 days acceptable?)3. What does it mean when items are also cited as “Priority” (i.e., they are mandatory, and/or they must be delivered within a shorter timeframe than other items – 120 days for Priority items versus 180 days for others)? | “Should” indicates a desired capability and is not mandatory. Offerors are not required to meet all requirements to be considered for award; however, the degree of compliance will be evaluated. “Priority” identifies capabilities of greater importance and will be given additional consideration during evaluation. Offerors shall propose realistic delivery timelines as part of their implementation approach. | |||
| 6 | Objective | Attachment J3 | 2 | Does GPO require that the SaaS software is certified by FedRAMP, or only the platform | The proposed solution should be hosted in a FedRAMP-authorized environment. The SaaS application does not need separate FedRAMP authorization if it operates within an authorized environment and meets federal security standards. The solution must be FedRAMP authorized or compliant, or have an acceptable equivalent listed in the SOO. Ideally, solutions are hosted on FedRAMP-authorized infrastructure at minimum, with any SaaS offering classified as "Low-Impact SaaS" or higher. | |
| 6 | Objective | Attachment J3 | 2 | Does GPO require that the SaaS solution be certified by FedRAMP or Moderate Level? | The proposed solution should be hosted in a FedRAMP-authorized environment. The SaaS application does not need separate FedRAMP authorization if it operates within an authorized environment and meets federal security standards. The solution must be FedRAMP authorized or compliant, or have an acceptable equivalent listed in the SOO. Ideally, solutions are hosted on FedRAMP-authorized infrastructure at minimum, with any SaaS offering classified as "Low-Impact SaaS" or higher. |
File details come from the government source that posted it. Updated .