88310326Q00008_0001 Presidential Library Ticketing System RFQ Amendment_FINAL.docx

NARA – 88310326Q00008 - Presidential Library Ticketing System – Amendment 0001

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

National Archives & Records Administration Same as Block #6

8601 Adelphi Road - Room 3340

College Park, MD 20740

9B. DATED (SEE ITEM 11)

01/09/2026

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE

FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

[X ]The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers [X] is extended, [] is not extended.

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:

(a) By completing Items 8 and 15, and returning __1__ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY 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 telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

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

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor [ ] is not, [ ] is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Solicitation 88310326Q00008 for Presidential Library Ticketing System is hereby amended as follows:

1. See attached, RFQ Questions and Answers.

2. See attached, updates to RFQ (changes indicated with track changes and/or highlighted in yellow)

3. The due date for quotations is hereby updated to 1:00PM EST on Thursday, February 5, 2026.

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.

Kevin Monahan

Contracting Officer

(Signature of person authorized to sign)

(Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITION UNUSABLE

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA FAR (48 CFR) 53.243

QUESTIONS AND ANSWERS

1. QUESTION: Attach # 13 (Relevant Past Performance Questionnaire) Can you confirm IF this 6-PG form is able to have the same deadline as the RFQ Submission (2/3 - 1PM) OR is the form required to have a separate deadline (1/28 - 4PM)?

ANSWER: The due date for the form has been updated to 2/5/26.

CHANGE: Yes. See updates to RFQ in attachment below

2. QUESTION: Appendix 12 (Voluntary Product Accessibility Template). Can you confirm IF vendors are expected to fill out just "V Review Feedback" column and not the other two columns: "POC Feedback and Tech Feedback"?

ANSWER: The RFQ contained the wrong Appendix number for this document. Appendix 12 is not required to be completed. Appendix 11 has been removed and updated instructions for providing a completed Accessibility Conformance Report (ACR) have been included at Attachment 10, section 1.b.iii.

CHANGE: Yes. See updates to RFQ in attachment below

3. QUESTION: For Attachment 10, section B, subsection iii - how should these questions be answered? ie. On line 17, “The website is included in the List of NARA Websites, with current information about points of contact, hosting, etc.”

ANSWER: Attachment 10, section B, subsection iii has been updated to clarify the 508 Accessibility Conformance Report (ACR) submission requirements.

CHANGE: Yes. See updates to RFQ in attachment below

4. QUESTION: For Attachment 10, section B, subsection v – is the Government requesting a letter from the Hardware companies that Gateway Ticketing Systems is a certified reseller?

ANSWER: Prior to award, NARA, as deemed necessary, will seek verification of authorized reseller status for any quoted hardware or software components of the quoted solution.

CHANGE: NONE

5. QUESTION: On Page 9 of the RFQ 2.6 “ie smartphones and tablets, at a minimum, both android and iOS based” – Are Windows based tablets also an available option?

ANSWER: This reference is for a web application that must be viewable/compatible from a desktop computer, laptop, and mobile device. Any web application that is viewable on a Windows based computer should, by default, be viewable on a windows based tablet.

CHANGE: NONE

6. QUESTION: On Page 2 for submitting these questions, it is noted that “The Government will answer questions or requests for clarification via a written RFQ amendment. “ How will this be communicated out to potential bidders?

ANSWER: It will be posted to SAM.gov as an amendment to the original RFQ posting.

CHANGE: NONE

7. QUESTION: The RFQ states: The Government will not consider any pricing model which requires revenue sharing, “convenience fee”, or other pricing model which would require the public to pay any dollar amount for visiting the Presidential Libraries and Museums. However, if the Contractor’s pricing for the SaaS Licenses incorporates the costs of deployment, hardware, operations and maintenance, or any other separately priced item, then the Contractor shall clearly indicate where these otherwise separately priced items are priced in the CLIN tables provided by the Government. Failure to clearly demonstrate that all items are accounted for and priced may result in rejection of the quotation as unacceptable. (Page 3/107 - RFP Document)

Q: Our pricing model is broken down between a subscription fee and a transaction percentage charged on the gross transaction value processed through the platform. This is not charged to the customer, but to NARA. Is this an acceptable arrangement for NARA?

ANSWER: No. For evaluation purposes, NARA requires a firm fixed price for each CLIN that is not inclusive of a transition percentage fee. For pricing purposes, the annual earned revenue for fiscal year 2025 is provided in Questions # 8 and 25.

8. QUESTION: Can you provide a cumulative (or broken down by location) summary of the annual earned revenue for NARA specific to the museum revenue that would be processed through the platform?

ANSWER: FY2025 is October 1 2024 - September 30 2025.

*Hoover Presidential Library and Museum closed for renovation February 2025 through June 2026. Their fiscal year 2024 (October 1 2023 - September 30 2024) revenue was $112,000.

9. QUESTION: PWS Reference 1.3.1.1. NARA’s existing ticketing system at the Presidential Libraries provides reports in XML format that can be ingested by Microsoft Dynamics Great Plains which NARA uses manage its financial transactions via scripts.

Q: Our platform can integrate with Great Plains and this process can be automated. Is NARA open to other solutions than import/export?

ANSWER: Yes.

10. QUESTION: PWS Reference 3.2.8.2. The solution shall provide the capability to automatically send batch emails containing links and attached documents to attendees based on reservation date or other criteria.

Q: Is it acceptable if these are sent out in real time vs. batching? Our platform does this immediately within seconds of transactions completing.

ANSWER: Yes, real time emails are acceptable (confirmation email, for instance), however NARA also requires the capability to send batch emails based on reservation date or other criteria (notification of closure due to weather event, for instance).

11. QUESTION: PWS Reference 3.5.1.1. Enable users to register for an event for multiple visitor categories within one (1) transaction.

Q: Can you confirm this is just referring to Adult, Child, Senior, Student, etc.? If not, can you provide an example?

ANSWER: This refers to the ability to register for an event that may have multiple options, whether it be multiple ticket types (i.e., child, adult) within one transaction or whether a single user needs to select multiple ticket options (i.e., main gallery ticket plus a boyhood home tour ticket).

12. QUESTION: PWS Reference 3.6.1. Data Import and Export. The system shall enable internal users to import and export data fields and the associated data to and from applicable formats such as, .doc, .docx, .xls, .xlsx, .csv, XML, .rtf and .pdf formats from individual locations and across all sites. The system shall enable users to select fields to be imported and exported with minimal steps and keystrokes. In the example of the Franklin D. Roosevelt Presidential Library and Museum and home, the National Parks Service (NPS) sells tickets using their ticketing system on behalf of NARA. The ticket sales information from the NPS is sent to NARA in a Microsoft Excel .csv file. This information shall be imported into the new ticketing system.

Q: Our platform provides multiple options from sales portals to backend integration with third party ticketing systems that would allow for these third party groups to be able to sell tickets in real time using live inventory and pricing from NARA. Invoicing, ticket delivery, commissions, etc. are all calculated in real time. This avoids all of the manual processing listed in the requirement. Is this an acceptable solution?

ANSWER: The solution must allow for the import/export of data fields and associated data as described in 3.6.1. Vendors are welcome to propose alternative methods. The solution must at a minimum meet the requirements as described in the PWS.

13. QUESTION: PWS Reference 3.2.8.2 – Can the automated emails be sent via an external tool (i.e. Mailchimp, Klaviyo, ActiveCampaign) or is the expectation it would be sent from within the ticketing platform?

ANSWER: Confirmation emails should not require an external tool. NARA currently utilizes HubSpot for email content management. Vendors may propose an approach that includes integration with this tool. However, the integration between the ticketing solution and any external tool should be automated with minimal to no configuration required on the part of NARA.

14. QUESTION: PWS Reference 3.2.11 – Regarding group reservation notifications, can this be managed via a scheduled report?

ANSWER:Yes, the report should be automated and sent in intervals as determined by the internal user.

15. QUESTION: PWS Reference 3.3.6 – Can you elaborate more about your self check-in requirements? Can this be done via a kiosk?

ANSWER: This requirement references the ability of a customer to arrive at the museum and self “redeem” their ticket via their smart phone. This allows flexibility for staff such as times when NARA IT may be down, or during especially busy events/times, etc.

16. QUESTION: PWS Reference 3.3.7 – Regarding the use of “forms” – can this information be collected via a POS device when a transaction is completed for a guest purchasing walk-up tickets?

ANSWER:. Yes, the “forms” feature should be accessible at the POS and via the online ticket reservation process.

17. QUESTION: PWS Reference 3.5.3.5 – Do the event cancellation notifications need to be automated if an event is taken off-sale or cancelled, or can this be managed via a manual process instead?

ANSWER: Users should be able to select the settings for event cancellation notifications, including both automated and manual options.

18. QUESTION: PWS Reference 3.5.6 – Can the system-generated forms be managed as a report that could be scheduled?

ANSWER: Yes. However, the solution, at minimum, shall also provide the capability for on-demand reports.

19. QUESTION: PWS Reference 3.6.2.1 – Can you elaborate on the requirement of running multiple variables “without manually inputting the report name individually.” What does that mean?

ANSWER: The solution should allow users to select a “canned” report type from a list (dropdown, checkbox, etc.) without having to manually type in the name of the report.

20. QUESTION: PWS Reference 3.6.2.1.3 – Regarding repeat visitors, what is it considered to be a repeat visit in a given time frame - when the person comes more than once, when the household comes more than once, how to track if they allow guest checkout?

ANSWER: “Repeat visits” could include any or all of the examples on your list.

21. QUESTION: PWS Reference 3.6.2.3 – Can you elaborate on what you mean by “The system should have a “smart” reports function? What is considered to be a smart report?

ANSWER: A “smart reports” function is a reporting tool that can take user-generated written prompts to generate custom reports.

22. QUESTION: PWS Reference 3.6.3 – Are you looking for audit history with regard to customer behavior or staff behavior in the system, or both?

ANSWER: Staff only.

23. QUESTION: PWS Reference 3.7.2 – Can you provide more information about your requirement to provide a flexible and/or customizable screen interface?

ANSWER: The internal user interface should allow staff some ability to customize what appears on their own interface depending on local needs.

24. QUESTION: PWS Reference 3.8.1.1 – Is this a reporting mechanism or something you require in real-time on the discount creation section?

ANSWER: The requirement to be able to browse and review past and current promotional discounts is both for reporting purposes as well as real-time viewing.

25. QUESTION: Can you provide the total amount of admission’s revenue processed in 2025? And of that amount, how much revenue came from memberships?

ANSWER: The total admissions revenue in fiscal year 2025 (October 1 2024 - September 30 2025) was $4,249,600.00. (*Note: the Hoover Presidential Library and Museum closed February 2025 through June 2026 for renovations). The revenue for fiscal year 2024 for Hoover was $112,000.00. NARA does not sell memberships. Memberships are handled by the presidential libraries’ privately-run support organizations.

26. QUESTION: Can NARA confirm the ACME Technologies Cloud-Based (SaaS) ticketing system is currently in use at the libraries?

ANSWER: Confirmed. See Section 1.3.1 of the PWS.

27. QUESTION: PWS Reference 1.3.1.1. Can NARA confirm Microsoft Dynamics Great Plains is used to manage financial transactions VIA Scripts?

ANSWER: Confirmed.

28. QUESTION: PWS Reference 2.8. What type two-year data does NARA need to have migrated from the legacy ticketing system?

ANSWER: Please see section 6.3.1 for the list of migration requirements.

29. QUESTION: PWS Reference 3.2.8.2. How many total emails do you anticipate the provided solution expects to send during a one (1) year/(12 months period)?

ANSWER: Aside from standard email confirmations, each site may send up to a couple hundred emails per year, each with multiple recipients.

30. QUESTION: PWS Reference 3.10. Can NARA confirm the system shall utilize Microsoft Entra ID to support multi-factor authentication?

ANSWER: Confirmed

31. QUESTION: PWS Reference 3.10. Can NARA confirm NARA will furnish all Microsoft ENTRA ID licenses and connectivity required for enabling user authentication?

ANSWER: Confirmed

32. QUESTION: PWS Reference 3.11.2. Can NARA confirm the Department of Treasury’s Card Acquiring Service (CAS) for credit card transactions, which is WorldPay, Inc. is required to be used?

33. QUESTION: PWS Reference 3.11.3. Can NARA confirm the credit card readers must be EMV compliant and the system shall comply with CAS requirements for financial transactions?

34. QUESTION: PWS Reference 6.4. If minimal SaaS licensing is required for the configuration of NARA specific features to support the contractor’s engagement in the NARA ATO process, will NARA consider that licensing at the time it is required?

ANSWER: As stated in the Pricing Notes section of Attachment 1, Contractors are encouraged to consider SaaS licensing and maintenance duration during the base period based upon implementation timeframes, and shall provide prorated subscription terms as applicable. Incremental or milestone based payments may be authorized by the Contracting Officer. Contractors may propose a payment schedule for consideration, which will be negotiated between the parties at award.

CHANGE: NONE

35. QUESTION: RFQ Reference Pg 91. What level of cryptographic protection does NARA require for data in transit versus data at rest?

ANSWER: The requirements for cryptographic modules are detailed in the Federal Information Processing Standard (FIPS) 140-3.

36. QUESTION: The RFQ describes the need for onsite hardware and kiosks. If the proposed solution does not require unique hardware, outside of a standard laptop or browser-based device, using Windows or iOS, does the Government want the Contractor to supply that standard office equipment?

ANSWER: Yes. The Contractor is required to provide all hardware and software components necessary to operate its proposed solution, including any standard office equipment.

37. QUESTION: Will NARA increase the transition period to enable a new Contractor to effectively implement, integrate, transition, and ATO the new Contractor solution?

ANSWER: NARA requires any new solution to be fully deployed to all sites no later than 5 months after award, or August 28, 2026 (whichever is earlier). In accordance with Attachment 10 of the RFQ, Contractors shall provide a Draft Project Management Plan that includes a proposed milestone schedule for fully transitioning all sites no later than five (5) months after award (if applicable) in accordance with PWS paragraph 6.2.

38. QUESTION: The issued solicitation document contains a watermark labeled, “DRAFT.” Please confirm if this issued solicitation document is in its final form, or if there is a final version that we should be anticipating.

ANSWER: The posted RFQ is the final version

CHANGE: Yes. See updates to RFQ in attachment below

39. QUESTION: Would NARA please consider extending the offer due date (page 2) to allow additional time for quotation submissions to be adjusted based on NARA’s responses to vendor questions submitted?

ANSWER: An extension has been granted to1:00PM EST on Thursday, February 5, 2026.

40. QUESTION: Does NARA have a preferred pricing model for the quotation, such as annual software subscription, per-ticket transaction fees, tiered based on visitor volume, etc.? (Attachment 1)

ANSWER: No. Reference Attachment 1, Pricing Notes.

41. QUESTION: Has NARA established an internal budget range or funding estimate for this project (base year and/or annual recurring costs)? (Attachment 1)

ANSWER: Yes. This information will not be provided.

42. QUESTION: The pricing tables provided in Attachment 1 (pages 3-7) include a $64,000 NTE for the Post-Deployment Onsite Hardware for each year of the contract term. Please confirm that pricing for these hardware components cannot exceed $64,000.

ANSWER: CLINs 0010, 0014, 0018, 0022 and 0026 are for additional hardware above and beyond the base solution requirements. These are optional CLINs that may be exercised at the Government’s discretion during performance for additional hardware and/or kiosks as deemed necessary. For evaluation purposes, the price for these CLINs will be the not-to-exceed amount of $64,000.00 and cannot be exceeded.

43. QUESTION: When does the current ticketing system contract expire? (Attachment 2, section 1.3.1)

ANSWER: The current ticketing system subscriptions expire on March 29, 2026. If a new system is selected, NARA will pursue a short-term bridge contract with the current vendor to allow sufficient time for transition.

44. QUESTION: What is the current annual contract value of the existing ticketing system (software, support, hosting, etc.)? Does the current contract include an annual subscription model, a per-ticket model, or other pricing structure? (Attachment 2, section 1.3.1)

ANSWER: This information cannot be made available at this time.

45. QUESTION: Please confirm the current payment processing system used today. (Attachment 2, section 1.3.1)

ANSWER: Please see section 3.11.1 of the RFQ. NARA’s processing system is WorldPay Vantiv through the U.S. Treasury.

RFQ CHANGE: NONE

46. QUESTION: Does NARA pay payment processing fees directly, or are any fees currently passed on to end users? (Attachment 2, section 1.3.1)

ANSWER: At present, NARA is responsible for any payment processing fees (as and if they exist). External users do not pay any payment processing fees.

47. QUESTION: What are the current payment processing rates (percentage and per-transaction fees) applied to NARA transactions? (Attachment 2, section 1.3.1)

ANSWER: NARA pays credit card processing fees to the U.S. Treasury. The specific fee rate is irrelevant to this RFQ.

48. QUESTION: What are the primary challenges or pain points experienced by NARA staff and/or visitors with the current ticketing system? (Attachment 2, sections 2.1-2.6)

ANSWER: The RFQ details NARA’s requirements for this effort.

49. QUESTION: What is NARA’s desired go-live date for the initial site and for full multi-site deployment? (Attachment 2, section 2.7)

ANSWER: Reference PWS Section 6.2.1. The presidential libraries baseline shall be configured, integrated, tested, and deployed for use starting with the John F. Kennedy Presidential Library and Museum and all remaining Libraries transitioned no later than 5 months after award, or August 28, 2026 (whichever is earlier). Prior to deployment to production at each site, the system shall meet all requirements in PWS paragraph 3.0 and in PWS paragraph 12.0, GFI, Appendix 3, RVTM.

50. QUESTION: What was the total annual revenue generated from ticketing-related sales? (Attachment 2, section 2.10)

ANSWER: See NARA’s response to question #25 in this Q&A document.

51. QUESTION: For the Onsite Hardware listed in Section 6.4.1 (Attachment 2), are vendors to propose new hardware for each of the types listed at each location (e.g. ticketing workstations, barcode scanners, ticket printers, kiosks, receipt printers, credit card readers, etc.)? Or should vendors anticipate that no hardware would be replaced for the initial deployment?

ANSWER: Vendors should propose new hardware for each of the types listed. Vendors should anticipate a complete hardware replacement to implement its proposed solution.

52. QUESTION: If hardware is to be replaced for the initial deployment, should vendors assume one-for-one replacement of existing hardware, or is hardware expansion anticipated? (Attachment 2, section 6.4.1)

ANSWER: The chart in 6.4.1 defines the required new hardware requirements for each site.

53. QUESTION: Page 92 of the solicitation (Attachment 10, section 1.b.iii.) says that a completed VPAT (in accordance with Appendix 12) must be included with the submission. However, in addition to the VPAT, Appendix 12 also lists ACR and SAR. Please clarify if only a VPAT is required for the quotation submission, or if the ACR and SAR are also required at this stage.

ANSWER: See amended RFQ. Appendix 11 has been removed and Attachment 10, section 1.b.iii has been updated to require a “completed Accessibility Conformance Report (ACR) for each commercially available Information and Communication Technology (ICT) item offered through this contract using the Voluntary Product Accessibility Template. Complete each ACR in accordance with the instructions provided in the most recent VPAT template. Each ACR must address the applicable Section 508 requirements referenced in the PWS, Section 4.0.”

54. QUESTION: Page 95 of the solicitation (Attachment 10, section 2.b.) says that references must return the completed survey in Attachment 13 (Relevant Past Performance Questionnaire) by the quotation due date and time (which is currently February 3), however Attachment 13 (page 102) says that the survey must be returned by January 28. Please clarify the correct date and time by which references should return the completed survey in Attachment 13 to the Contracting Officer.

ANSWER: The RFQ has been amended to change the due date for the PPQ to 2/5/26 to align with the quotation due date.

This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR Subpart 12.6, Streamlined Procedures for Evaluation and Solicitation for Commercial Products and Commercial Services as supplemented with additional information included in this notice. The solicitation number is 88310326Q00008. This is a total small business set-aside RFQ under NAICS code 541519, Other Computer Related Services.

The National Archives and Records Administration (NARA) has a requirement to obtain a Ticketing System for the Presidential Libraries. Reference Attachment 2, Performance Work Statement. The period of performance will consist of a base year and four (4) option years. The following Federal Acquisition Regulation (FAR) clauses are incorporated and are to remain in full force in any resultant contract. FAR provisions will be removed prior to award. FAR provision 52.212-1, Instructions to Offerors—Commercial Products and Commercial Services (Sep 2023) Addenda: (1) Change paragraph (c) to read: Period for acceptance of offers. The offeror agrees to hold the prices in its offer firm for 90 calendar days from the date specified for receipt of offers. (In lieu of FAR provision 52.212-2): Evaluation and award will be in accordance with Simplified Acquisition Procedures at FAR 13.106, Soliciting Competition, Evaluation of Quotations or Offers, Award and Documentation authorized by FAR Subpart 13.5, Simplified Procedures for Certain Commercial Products and Commercial Services as prescribed by FAR 12.301(c)(2). Selection of the Contractor for award of this contract will be based on NARA’s assessment of the best overall value to the Government. Reference Attachment 11, Evaluation Factors for Award. The Government reserves the right to make an award on the initial quotation without communicating with contractors. The Government reserves the right to engage all, some, or none of the firms submitting quotations in response to this RFQ to obtain a better understanding of any aspects of its quote and to reach a determination on which quotation is the most advantageous to the Government. FAR provision 52.212-3, Offeror Representations and Certifications—Commercial Products and Commercial Services (May 2024) - The Offeror shall complete only paragraph (b) of this provision if the Offeror has completed the annual representations and certification electronically in the System for Award Management (SAM) accessed through https://www.sam.gov. If the Offeror has not completed the annual representations and certifications electronically, the Offeror shall complete only paragraphs (c) through (v) of this provision. FAR clause 52.212-4, Contract Terms and Conditions - Commercial Products and Commercial Services (Nov 2023) – reference Attachment 7, NARA Terms and Conditions (Addenda to FAR clause 52.212-4). FAR clause 52.212-5, Contract Terms and Conditions Required to Implement Statutes or Executive Orders - Commercial Products and Commercial Services (Nov 2024) - reference Attachment 8, FAR Clauses for the full text of this clause and for additional applicable FAR clauses. The Contractor is required to be registered in the System for Award Management (SAM) and maintain registration until final payment in accordance with FAR provision 52.204-7, System for Award Management (Nov 2024). Full text provisions and clauses can be found at http://www.acquisition.gov.

Questions regarding this RFQ must be submitted in writing to the Contracting Officer, Kevin Monahan at kevin.monahan@nara.gov no later than 1:00PM EST on Tuesday, January 20, 2026 to be considered. Questions submitted in any other manner will not be answered. Contractors are requested to group and submit questions in the same order found in the RFQ while making reference to the particular paragraph number. The Government will answer questions or requests for clarification via a written RFQ amendment.

Quotations must be received by 1:00PM EST on Thursday, February 5, 2026. Failure to submit quotations by the due date and time may result in rejection of the quotation as untimely. Reference Attachment 10, Quotation Submission Instructions.

Attachments:

Attachment 1 – Schedule of Prices Attachment 2 -- Performance Work Statement (PWS)

Attachment 3 – Quality Assurance Surveillance Plan (QASP) Attachment 4 – Performance Requirements Summary (PRS) Attachment 5 – Non-Disclosure Agreement Attachment 6 – Contract Administration Attachment 7 – NARA Terms and Conditions (Addenda to FAR Clause 52.212-4) Attachment 8 – FAR Clauses Attachment 9 – FEDRAMP Terms and Conditions for Hosted Solutions and Cloud Computing Services Attachment 10 – Quotation Submission Instructions Attachment 11 – Evaluation Factors for Award Attachment 12 – Product Demonstration Video Instructions Attachment 13 -- Relevant Past Performance Questionnaire

ATTACHMENT 1

SCHEDULE OF PRICES

PRICING NOTES:

(a) The Contractor shall provide a separate pricing breakout for CLINs 0002 through 0009 that clearly identifies all elements of each FFP CLIN Price for the respective location. Contractors are encouraged to consider SaaS licensing and maintenance duration during the based period based upon implementation timeframes, and shall provide prorated subscription terms as applicable. Incremental or milestone based payments may be authorized by the Contracting Officer. Contractors may propose a payment schedule for consideration, which will be negotiated between the parties at award.

(b) The Contractor shall provide a separate pricing breakout for CLINs 0013, 0017, 0021 and 0025 that clearly identifies the option year price per site. The Government reserves the right to descope individual sites at the start of each option period and reduce the option period price accordingly based on the per site price breakout. While the price schedule requires a monthly unit price for these CLINs, Contractors may propose, for the Contracting Officer’s consideration, an alternate payment schedule for each option period that aligns with its standard commercial practice for its SaaS subscriptions. Any adjustment to the monthly payment schedule for these CLINs will be negotiated between the parties following award.

(c) NARA has included not-to-exceed amounts in CLINs 0010; 0014; 0018; 0022; and 0026. For evaluation purposes, the “Total Price” for these CLINs are the total not-to-exceed amounts. The Contractor shall provide a price catalog for all hardware items which are available to purchase under these CLINs. The pricing must include the make, model, part number and unit price for each hardware item quoted.

(d) The Government will not consider any pricing model which requires revenue sharing, “convenience fee”, or other pricing model which would require the public to pay any dollar amount for visiting the Presidential Libraries and Museums. However, if the Contractor’s pricing for the SaaS Licenses incorporates the costs of deployment, hardware, operations and maintenance, or any other separately priced item, then the Contractor shall clearly indicate where these otherwise separately priced items are priced in the CLIN tables provided by the Government. Failure to clearly demonstrate that all items are accounted for and priced may result in rejection of the quotation as unacceptable.

CLIN = Contract Line Item Number; IAW = In accordance with; MAX= Maximum; Mo. = Month; NSP = Not Separately Priced; NTE = Not to Exceed; and PWS = Performance Work Statement Base Year: Months 1-12

NTE

Option Year I: Months 13-24

NTE

Option Year II: Months 13-24

NTE

Option Year III: Months 13-24

NTE

Option Year IV: Months 13-24

NTE

ATTACHMENT 2

PERFORMANCE WORK STATEMENT

PRESIDENTIAL LIBRARY TICKETING SYSTEM

1.0 BACKGROUND

1.1 The National Archives and Records Administration (NARA) and its Presidential Libraries serve American democracy by safeguarding and preserving the records of our government, ensuring that people can discover, use, and learn from this documentary heritage. NARA ensures ready access to the essential evidence that documents the rights of American citizens, the actions of Federal officials, and the national experience. The agency meets thousands of information needs daily, ensuring access to records on which the entitlements of citizens, the credibility of government, and the accuracy of history depend.

1.2 NARA’s Presidential Libraries and Museums (“Presidential Libraries” or “Libraries”) sites located across the country welcome over 1 million visitors each year and play a critical role in connecting with customers and making access to its records happen.

1.3 Presently some Presidential Libraries use a COTS ticketing system under a NARA contract. The remaining Libraries have ticketing managed by their Foundations, and are not within the scope of this contact.

1.3.1 The current Presidential Libraries ticketing system provided by ACME Technologies is a cloud-hosted Software-as-a-Service (SaaS) ticketing and resource management solution. Eight (8) of the 15 Presidential Libraries use ACME Technologies to support onsite and online ticket sales handled through a “box office” model where NARA personnel manage the transactions using a point-of-sale (POS) system:

· Herbert Hoover Presidential Library and Museum, West Branch, IA

· Franklin D. Roosevelt Presidential Library and Museum, Hyde Park, NY (National Park Service manages on-site and online group reservation sales only.)

· Harry S. Truman Presidential Library and Museum, Independence, MO

· Dwight D. Eisenhower Presidential Library and Museum, Abilene, KS

· John F. Kennedy Presidential Library and Museum, Boston, MA

· Gerald R. Ford Presidential Library and Museum

· Library – Ann Arbor, MI (no ticketing needs)

· Museum – Grand Rapids, MI

· Jimmy Carter Presidential Library and Museum, Atlanta, GA

· George H.W. Bush Presidential Library and Museum, College Station, TX

1.3.1.1 NARA’s existing ticketing system at the Presidential Libraries provides reports in XML format that can be ingested by Microsoft Dynamics Great Plains which NARA uses manage its financial transactions via scripts.

1.3.2 For purposes of this document, internal users of the system will be referred to as "staff," NARA staff," and "users". Internal users with higher level privileges are referred to as "administrators". External users of the system are referred to as "visitors" or "guests".

2.0 SCOPE

2.1 NARA has a requirement for a Commercially Available-Off-the-Shelf (COTS) cloud hosted Software as a Service (SaaS) solution. This COTS solution shall require minimal configuration to implement. The ticketing system must be accessible via the web to all authenticated NARA federal and contractor staff and shall not require additional networking or changes to provide access, except as necessary to comply with security requirements.

2.2 The objective of this program is to provide a configurable solution for an efficient and cost-effective means of providing a high-quality user experience to its visitors. The new ticketing admission and event management system will integrate onsite and online sales, individual and group reservations, resource management, and reporting into a single user friendly and customizable system. The goals of deploying a single, integrated ticketing system are to ensure consistency and automation of the reporting of attendance and sales data; simplifying financial processing; simplifying operations and maintenance of the system; and making visiting a NARA site requiring ticketing as convenient as possible for the general public.

2.3 The ticketing system will allow NARA staff to better manage visitor flow, promote deeper exploration of onsite and online resources, and expand the visitor experience beyond the specific ticketed day by sending via email curated pre-visit and post-visit information such as satisfaction surveys, accessibility information, and other relevant data that allow guests to build an itinerary and customize their experience. Additionally, the ticketing system will assist with managing visitor flow through advanced ticket sales and timed ticketing reservations.

2.4 NARA requires a design that is scalable for concurrent customer use and future capability, fully cloud hosted, and capable of meeting NARA’s needs with minimal modifications to its websites. NARA also requires minimal changes to its business processes and employee workflows.

2.5 NARA requires the ticketing system to collect information which may be used for reporting and planning future programming. This data includes not only visitor counts and demographic information, but also options to provide program feedback and audience evaluations that will allow NARA to better track customer satisfaction and adjust as needed.

2.6 To further enhance the visitor experience, the ticketing system shall provide onsite capabilities such as a kiosk or similar self-service stations to reserve, print, and pay for tickets, and to donate to NARA programming. In addition, a web application that can be viewed from a desktop computer, laptop, and mobile device (i.e., smartphones and tablets, at a minimum, both Android and iOS based) is required for each NARA site that will provide the same ticketing capabilities as its kiosk functionality.

2.7 The Contractor shall be responsible for the full project lifecycle, which includes, but is not limited to: providing and configuring the system; deployment; training of NARA internal users on the operations of the system; operations and maintenance of the system; and periodic enhancements to the system for each site.

2.8 Data from the existing instances of the ticketing systems must be migrated to the new ticketing system prior to the production roll out. The presidential libraries require two (2) years of ticketing data to be migrated for each site.

2.9 Approximately 70 internal users across the presidential libraries will be using the ticketing system (eight per site plus six from HQ). The site-specific onsite hardware requirements are defined in PWS paragraph 6.4, Onsite Hardware and 6.4.1.

2.10 Each presidential library will have admission fees based on the needs of the specific location.

2.11 Place of Performance. A majority of the services required herein shall be performed at the Contractor’s facilities. During the implementation of the system at each site and Operations and Maintenance and Help Desk phases, the Contractor may be required to be onsite at NARA facilities. Meetings, briefings, and presentations shall, to the maximum extent practicable, be held via teleconference or webinar (via either Contractor furnished or NARA furnished telecommunications services). Travel costs will not be reimbursed under this contract.

2.12 Normal Hours of Operation. For the duration of this contract, normal hours of operation at the presidential libraries are between the hours of 7:00 AM ET and 10:00 PM ET, seven days per week, 52 weeks a year except for Thanksgiving, Christmas, and New Year’s Day when these locations are closed. Operations and Maintenance and Help Desk support shall be available when presidential libraries are open for business.

3.0 REQUIREMENTS

3.1 The Contractor shall ensure that the ticketing system meets the requirements described herein. NARA has identified and established baseline requirements. These requirements are defined in PWS Appendix 3, Ticketing System RVTM.

3.1.1 The solution shall provide, at a minimum, the capabilities in PWS Appendix 3, RVTM listed with requirement priority “MUST”.

3.1.2 The solution may provide capabilities listed in PWS Appendix 3, RVTM listed with requirement priority “SHOULD”.

3.1.3 As a part of verifying the ticketing requirements, the Contractor shall develop a System Design Document (SDD) describing the system architecture. At a minimum, the SDD shall address the following:

3.1.3.1 Structure and relationships between components of the system.

3.1.3.2 System design constraints.

3.1.3.3 System human interfaces (input and output).

3.1.3.4 Interfaces with internal and external systems.

3.1.3.5 Functional requirements that the COTS product and other system components meet.

3.1.3.6 Data design including data elements.

3.1.3.7 The level of network support required.

3.1.3.8 Assumptions, constraints, and risks associated with the design and implementation.

3.1.3.9 The Contractor shall facilitate peer review sessions with NARA to understand, refine and decompose the requirements, as needed, to ensure they are clear and testable. After which the Contractor shall deliver an updated RVTM. The Contractor shall update the SDD and RVTM with each implementation of a ticketing site, as required.

3.1.3.10 The Contractor shall maintain an Interface Control Document (ICD) that identifies all interfaces in the system, providing a general characterization of each interface in terms of communicating elements, information communicated, information assurance considerations, usage characteristics, and communication formats and protocols. This information must be included as a section within the SDD.

3.1.3.11 The Contractor shall provide and update the ICDs that specify the functional and technical characteristics of each interface to fully express the technical design of each interface. The ICDs shall reference the functional elements and requirements allocated to each interface design. Each interface must be documented in a unique ICD.

3.2 Sales & Reservations

3.2.1 NARA requires four platforms to be available for customers to purchase tickets and/or reserve free tickets: (1) an onsite box office point of sale; (2) an option for onsite kiosks at a site’s request; (3) online through the customers’ personal desktop computer and/or laptop; and (4) online through the customers’ mobile device. The system must be accessible on all of these four platforms. These platforms must be customizable depending on the ‘look and feel’ and local site needs.

3.2.2 NARA requires at each site the ability to configure the user experience and data field constraints based on each site’s logo, colors, sale categories, ticket prices, and other fields. Furthermore, the system shall display the available museum entry times to all users during purchase.

3.2.3 The ticketing system shall enable transactions for the customers to purchase and/or reserve tickets depending on site needs. Each ticket shall display the ticket category (such as “senior”, “adult”, “military”, “children”, “students”, etc.) along with a barcode (throughout “barcode” means either one-dimensional (1D) or two-dimensional (2D) and its associated unique sequence of numbers. Customers shall be able to include add-on items with their ticket purchase, such as entrance to specific exhibit spaces, audio tours, and brochures. The system shall have the ability to collect donations online, at the POS, and via kiosks. The system shall allow all users to purchase tickets (admissions, tours, and events) for multiple visitor categories within one (1) transaction.

3.2.4 The ticketing system shall allow all users to apply discounts on ticket prices from sales, and promotions. The system shall allow the creation, management, and purchase of timed-entry tickets, and to facilitate group sales.

3.2.5 The ticketing system shall allow internal users to alter ticket prices and apply single dates or date ranges to changes in ticket prices.