88310326Q00008_Presidential Library Ticketing System RFQ_FINAL.docx

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 Tuesday, February 3, 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. Additionally, the system shall allow internal users to look up ticket sales across all platforms after purchase and be able to print the ticket with a barcode and its associated unique sequence of numbers. The system shall allow internal users to process refunds for purchases made.

3.2.6 All sales platforms shall be able to accept and process VISA, MasterCard, Discover, and American Express credit cards via manual and contactless payments, as needed. All credit card readers shall be Europay, Mastercard, Visa (EMV) compliant. Additionally, the onsite box office POS shall be able to accept cash and checks. The system should also be able to process zero-dollar transactions without requiring a credit card. Zero-dollar transactions should not be submitted to the back-office accounting system.

3.2.7 The solution shall allow NARA to provide the subdomain name to preserve its own branding.

3.2.8 The ticketing system shall at a minimum, send an email and, as requested or authorized by the public user, a Short Message Service (SMS) confirmation of purchases to the customer for transactions which are initiated by the customer online through either the customer’s personal desktop computer, laptop, or mobile device (i.e., smartphones and tablets, at a minimum, both Android and iOS based).

3.2.8.1 The email and/or SMS confirmation shall include the order/transaction number and printable ticket with a barcode and its associated unique sequence of numbers, and any other relevant text or graphics as determined by each site. These messages shall provide notifications and information about their visit and future events.

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. This includes the ability to automatically email booking confirmation, invoices, event cancellation; and email notification to inform users about special exhibitions, events, or library programs. This also includes the ability to set up "rules" so that automated emails are sent to visitors based on certain criteria (send an email with pre-written text to every visitor one (1) week before their visit and/or an email with a survey one (1) day after their visit.).

3.2.8.3 The solution shall be able to accommodate emails to large groups of visitors. Examples include a single email with 1,000 or more recipients (emergency closure notification) or at least 1,000 emails in a day (order confirmations) each to a single recipient.

3.2.9 The ticketing system shall enable customers to manage their reservations and/or ticket purchases online and/or at kiosks. Customers shall be able to look up their online ticket purchases at onsite kiosks and online using their email address and/or order/transaction number, and to print tickets with the barcode and its associated unique sequence of numbers. This function shall not require customer accounts to function.

3.2.10 The ticketing system shall allow all users the ability to make group reservations including multiple group visits in one (1) order. The ticketing system shall provide a barcode and an associated unique sequence of numbers for each individual ticket within the group. Group data shall be accessible at the POS with the ability to create new orders at the POS for existing groups on future dates.

3.2.11 The ticketing system shall notify internal users of group reservations.

3.2.12 The ticketing system must be able to send email invoices and collect payment for custom bookings.

3.2.13 The ticketing system shall have the capability to have two (2) events on one (1) printed or electronic ticket.

3.2.14 The electronic ticket and receipt shall have the capability to display a Uniform Resource Locator (URL) for customers to link to a NARA designated external website.

3.2.15 The ticketing system shall provide functionality that enables dedicated reservation microsites for special events. Additionally, the system shall enable users to reserve a time and tour for individual, family, and group reservations.

3.2.16 The ticketing system’s design shall align with the ‘look and feel’ of each location’s respective website. While users may have to leave the museum homepage to obtain tickets through the ticketing system, the ‘look and feel’ of their experience will be maintained. Once a user has completed their experience with the ticketing system, the system will return them to the appropriate place on the library’s web site. The ticketing system’s website will meet the NARA approved checklist for website requirements. Reference Appendix 15, Website Checklist.

3.2.17 The ticketing system shall support multiple languages in accordance with Attachment 3, RVTM requirement 12.

3.2.18 The ticketing system shall allow the ability for group and facility rental clients to pay for their reservations and services online, similar to how online ticket purchasers pay for their ticket purchases.

3.3 Box Office Point of Sale and Ticket Check In

3.3.1 The system shall maintain a link within available data such as the order/transaction number, the tickets sold, customer information, method of purchase, and credit card information for all online and onsite purchases. Online ticket sale lookup shall be available by using the available data. NARA requires real-time access to its data across each of its locations.

3.3.2 The system shall allow internal users to scan in tickets via barcode or by manually entering its associated unique number.

3.3.3 The system shall enable internal users to manually enter and/or edit data on all orders, including all ticket sales with the associated order/transaction number and credit card information. In this circumstance, “edit” does not include editing past financial transactions. It may include editing the order with unexpired credit card information in order to complete a refund, for example.

3.3.4 Internal users shall also be able to scan in promotional coupons at the onsite box office POS.

3.3.5 The onsite box office POS, onsite hardware, and associated user interfaces shall have and be optimized for touchscreens.

3.3.6 The system shall provide the capability to support automated self-check-in.

3.3.7 The system shall allow for the use of “forms” (or equivalent) at check-in or purchase, where staff may input data gathered from the visitor such as zip code or email, etc.

3.3.8 The system shall include an offline mode for the point of sale and visitor management which accurately records and processes transactions and data upon restoration of internet connectivity.

3.4 Online Sales

3.4.1 The system shall be optimized for use on web-based systems including personal desktop computers, laptops, and mobile devices (i.e., smartphones and tablets, at a minimum, both Android and iOS based) and the site will follow visual design requirements as set forth by NARA.

3.4.2 The customer interface shall be readable and usable on a variety of commercially available desktop computers, laptops, and mobile devices.

3.4.3 Updates (content, design, functionality, etc.) for online ticketing websites for each site shall be optimized for smartphone and tablet experiences (mobile web) using responsive web design (RWD), adhere to US Web Design System principles and components, and comply with Archives.gov branding and style guide, to be reviewed by NARA’s Web Program. Online interface must be Section 508 compliant.

3.4.4 When designing the online sales platform, RWD shall be used with pinch-zoom capability enabled for mobile devices. A barcode and its associated unique sequence of numbers must be available on the mobile device for display at the site.

3.4.5 All online functionality shall be available through mobile devices.

3.5 Event Scheduling, Reservations, and Resource Management

3.5.1 The system shall allow all users to register for tours and events and purchase event tickets across multiple platforms. To facilitate this function the system shall:

3.5.1.1 Enable users to register for an event for multiple visitor categories within one (1) transaction.

3.5.1.2 Print event tickets.

3.5.1.3 Assign a unique identifier for each event transaction.

3.5.2 The system shall allow internal users to scan in tickets via barcode and shall record and maintain event attendee data.

3.5.3 The system shall provide the capability for internal users to schedule an event, including creating, modifying and canceling both future and past events. The system shall enable internal users to:

3.5.3.1 Apply single dates or date ranges to tours and events.

3.5.3.2 View tours and events in a calendar view.

3.5.3.3 Assign a maximum number of attendees for an event.

3.5.3.4 Manage the list of attendees for an event including adding event capacity and managing a waitlist.

3.5.3.5 Send event cancellation notifications to registered attendees.

3.5.4 The system shall maintain an audit history of changes for an event and reportable information for events shall include, but not be limited to the following:

3.5.4.1 Description

3.5.4.2 Maximum capacity

3.5.4.3 List of attendees

3.5.4.4 Customer information

3.5.4.5 Pricing

3.5.5 The system shall provide the capability for internal users to input data manually and print forms and registrations for groups, workshops, tours and other site activities.

3.5.6 The system-generated forms shall contain all or a portion of the line items for events (i.e. attendee list only). The system shall provide the capability for internal users to manage and customize forms.

3.5.7 The system shall enable internal users to process deposits, maintain records, generate invoices, and accept payment of outstanding balances.

3.5.8 The system shall allow for the creation of private links/sites for special events such corporate events/tours that are not available to the general public (the event information and RSVP for these events would be online but not shown on the main ticketing system calendar).

3.6 Data, Reporting, and Management

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.

3.6.2 Data Reporting. The system shall enable internal users to generate reports using all data fields and the associated data, including legacy migrated data, across sites and within individual sites. The system shall enable internal users to export reports to .doc, .docx, .xls, .xlsx, .csv, XML, .rtf and .pdf formats.

3.6.2.1 The system shall generate pre-packaged (canned) reports. These canned reports must be easily run on multiple variables without manually inputting the report name individually. All information should be reportable by hour, day of the week (e.g. Monday, Tuesday, etc.), date, month, and year. The canned reports must include the following:

3.6.2.1.1 Total number of visits by site and in aggregate;

3.6.2.1.2 Number of users;

3.6.2.1.3 Repeat visits;

3.6.2.1.4 Digital tickets versus onsite purchases;

3.6.2.1.5 Metropolitan statistical area by zip code and /county;

3.6.2.1.6 Countries visiting from;

3.6.2.1.7 Tickets sold/reserved by hour;

3.6.2.1.8 Sales by ticket/category; sales by program/event and ticket/category; payment summary; payment detail; and, payment method.

3.6.2.2 The system shall have the capability to create and generate ad-hoc reports using all data fields and associated data.

3.6.2.3 The system should have a “smart” reports function that handles multiple variables in one (1) report such as online sales, credit card sales, cash sales, event sales, etc. The report function must also be able to compile visitation data into reports by daily sales and attendance, zip code, country, and state.

3.6.2.4 The system shall have the ability to display ticket availability on a dashboard.

3.6.3 The system shall maintain an audit history of all activities performed in the system including transactions, event registration, time stamp, and resource (i.e. staff and room) management.

3.6.4 The solution shall scale to handle future data growth without major design or architectural changes.

3.7 User Interfaces

3.7.1 All NARA users will need an individual login to the ticketing system. However, public users purchasing tickets through this system will not require any login information or credentialing.

3.7.2 NARA requires a system with a flexible and/or customizable screen interface to enable its internal users to optimize screen designs to support current, local tasks and workflows, and save screen settings for future use.

3.7.3 The system shall provide the capability for internal users to arrange the icons displayed on the admissions desk touch screen monitor, including assigning functions to icons.

3.7.4 The system shall enable internal users to add, change, or configure the following:

3.7.4.1 Ticket design

3.7.4.2 Ticket prices

3.7.4.3 Ticket categories (e.g. senior, adult, child), including activating ticket categories and rendering selected categories inactive

3.7.4.4 Date range(s) for promotions and discounts

3.7.4.5 Sale items (e.g. brochures, audio tours)

3.7.4.6 Discounts (e.g. senior citizen, student, and veteran)

3.7.4.7 Promotion categories and related discount amounts

3.7.4.8 Schedule events

3.7.4.9 Entry times, durations, and maximum number of visitors/attendees

3.7.5 Each site shall have its specific logo and color theme displayed for all users. The logo and color theme for each site will be furnished by the COR, post award.

3.7.6 The Contractor shall include at least five (5) optional fields in the database for later configuration by NARA.

3.8 Search and Browse

3.8.1 The system shall provide the internal user the ability to browse and search by keyword and/or dates across the database and within fields for:

3.8.1.1 Promotional discounts, including current and past discounts

3.8.1.2 Individual ticket orders

3.8.1.3 Group reservations

3.8.1.4 Tours and Events, by date, time, program, name, attendees, and assigned resources (e.g. personnel, facility space, and equipment).

3.8.2 The system shall provide all users the ability to search and print results by date; order/transaction number and by email address; or by a combination of a customer’s first name, last name, and street address.

3.8.3 The system shall provide internal users the ability to print search results to .doc, .docx, .xls, .xlsx, .csv, .mdb, XML, .rtf and .pdf formats.

3.8.4 The system shall return a message to all users when search results are not found and allow them to try again.

3.9 System Interfaces

3.9.1 The system shall provide the necessary capability for the transfer of sales transaction information to the back office financial accounting system, Microsoft Dynamics Great Plains (GP).

3.9.1.1 The real-time interface must be compatible with and optimized for the Microsoft Dynamics GP Application Programming Interface (API), eConnect, and Microsoft Message Queuing (MSMQ).

3.9.1.2 The system shall only submit transactions with a financial impact to the accounting system. Zero-dollar transactions should not be sent.

3.9.1.3 The system shall utilize unique order numbers across all sites or have the ability to preface the order number with the site name before sending the XML document to the accounting system.

3.9.1.4 The Contractor shall ensure that the XMLs sent should have a unique Label field that identifies the originating site and associated order number.

3.9.1.5 The system shall have the capability to send XML transactions to different database servers and databases per site.

3.9.1.6 The system shall utilize XML acknowledgements for reconciliation purposes between the provided system and Microsoft Dynamics Great Plains.

3.10 Internal User Multifactor Authentication

The system shall utilize a Security Assertion Markup Language (SAML) based Identity Provider (IdP), currently Microsoft Entra ID, to support multi-factor authentication of the internal users.

3.11 Financial Processing Standards

3.11.1 The Contractor shall process credit cards through the Department of Treasury’s Card Acquiring Service (CAS) which is currently, Worldpay, Inc. with NARA being the Merchant of Record. Reference https://fiscal.treasury.gov/cas/ for additional information concerning the Department of Treasury’s CAS.

3.11.2 Each site shall have a separate NARA-owned Merchant ID (as appropriate), which will be provided by the CAS under the coordination and direction of the NARA Contracting Officer’s Representative (COR).

3.11.3 The Contractor shall abide by all card-processing rules as directed and issued by the CAS.

3.11.4 The system shall comply with all payment processing requirements from the Department of Treasury and NARA's cross-service accounting provider the Bureau of the Fiscal Service, which includes but is not limited to:

3.11.4.1 Receipts shall be generated for all transactions and shall adhere to all required data elements printed on the receipts.

3.11.4.2 All transactions shall be logged within the application with the user linked to each transaction processed by that user.

3.11.4.3 Enable internal users to reconcile all daily transactions by user, payment amount, and payment type.

3.11.4.4 Enable internal users the ability to run ad-hoc transaction reports, which include the payment date, transaction total, payment amount, and payment type, by a given date or date range to be used for auditing purposes.

3.11.4.5 The system shall track and report any transaction cancellations, voids, returns, refunds or credits, and identify the user for each of these activities.

4.0 SECTION 508 ACCESSIBILITY STANDARDS

4.1 The following Section 508 Accessibility Standard(s) (Technical Standards and Functional Performance Criteria) are applicable (if box is checked) to the SaaS and not user generated content.

4.1.1 All Electronic and Information Technology components are subject to Section 508 of the Rehabilitation Act (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998. Products, platforms and services delivered as part of this work statement that are information and communications technology (ICT), or contain ICT, must conform to the Revised 508 Standards (located at 36 C.F.R. § 1194.1 & Apps. A, C & D) and are subject to the associated Section 508 Standards as set forth by the U.S. Access Board. Section 508 technical standards and Functional Performance Criteria shall correspond to the WCAG 2,0 Level A and Level AA standards.

Revised 508 Standards and 255 Guidelines

Functional Performance Criteria

Mapping of WCAG 2.0 to Functional Performance Criteria | Section508.gov

4.1.2 The solution shall conform to PWS paragraph 12, GFI, Appendix 6, Information and Communications Technology (ICT) Accessibility Requirements in accordance with the Revised Section 508 of the Rehabilitation Act. The following Section 508 Accessibility Standard(s) (Technical Standards and Functional Performance Criteria) are applicable (if box is checked) to the product and not user generated content.

4.1.3 Technical Standards

☒ 1194.21 – Software Applications and Operating Systems ☒ 1194.22 – Web Based Intranet and Internet Information and Applications ☐ 1194.23 – Telecommunications Products ☒ 1194.24 – Video and Multimedia Products ☐ 1194.25 – Self-Contained, Closed Products ☒ 1194.26 – Desktop and Portable Computers ☒ 1194.41 – Information, Documentation and Support

4.1.4 Functional Performance Criteria (FPC) is a method to determine whether substantially equivalent or greater accessibility and usability is provided to individuals with disabilities, whenever the product may not be fully compliant to the technical standards. FPC are intended to work in close conjunction with the technical standards and must not be viewed as a replacement for the technical standards. FPC can be viewed as a catch-all or fail-safe to address technology change and allow authors and developers creativity in ensuring equal access to information and data. This block is checked to ensure that acceptable electronic and information technology (E&IT) products are proposed even when for some reason a technical standard is not met.

☒ 1194.31 – Section 508 Standards and Functional Performance Criteria

4.1.5 The Contractor shall create an Accessibility Conformance Report (ACR) and a Supplementary Conformance Report (SAR) as described in the following table. The ACR is based on the Voluntary Product Accessibility Template (VPAT) 2.0. For detailed instructions, reference How to Create an Accessibility Conformance Report Using A Voluntary Product Accessibility Template (VPAT®). The Contractor shall keep the ACR updated to reflect any modifications that have changed the Section 508 compliance status of the product – whether enhanced or diminished (if diminished, the Contractor must include the Contractor’s mitigation plan). Any deviation to this requirement as described must be negotiated with NARA Contracting Officer (CO).

The ACR should be based on the VPAT template, but it is not a simple restatement of an OEM’s VPAT. A Contractor or Reseller is required to test its products against the applicable Section 508 Technical Standards and then report in the ACR which standards the product supports, partially supports, or does not support.

To be considered for the award, the ACR must be complete and submitted according to the instructions. A separate ACR is required for each ICT item: software, hardware, documentation, etc.

For detailed instructions, reference How to Create an Accessibility Conformance Report Using a Voluntary Product Accessibility Template (VPAT®) at https://www.section508.gov/sell/how-to-create-acr-with-vpat/

· Descriptions of evaluation methods used to produce the ACR, to demonstrate due diligence in supporting conformance claims;

· Documentation of features that help achieve accessibility and usability for persons with disabilities;

· Information on core functions that can't be used by persons with disabilities;

· Information on how to configure and install the ICT item to support accessibility; and

· Information on how the ICT item enables the creation of accessible electronic content that conforms to the Revised 508 Standards, including the range of accessible user interface elements the tool can create. (Only required for authoring tools that generate content (documents, reports, videos, multimedia, web content, etc.)

5.0 PROJECT MANAGEMENT

5.1 Kickoff Meeting. The Contractor shall lead a Kickoff Meeting with the Government Program Manager, Project Manager, the COR, CO, and System Owner, within five (5) business days after the award date of the contract to prepare NARA and the Contractor for the work described in this PWS.

5.2 Requirements discussion. The Contractor shall meet with the COR and NARA stakeholders to review the requirements prior to system configuration. Changes to the requirements must be submitted to the COR. Any derivation from or changes to the requirements that result in updating or adding to the prescribed scope baseline will be a) communicated to the Contractor via the COR; b) updated according to NARA’s change management process; and c) shall only be finalized through a bilateral contract modification, executed by a warranted NARA CO.

5.3 Project Management Plan (PMP). The PMP shall show how the implementation of the ticketing system will be executed, monitored, and controlled. It shall include references to all tasks listed in this PWS, as well as, draft and final deliverables enumerated in PWS paragraph 11.0, Deliverables. A separate PMP section is required for the deployment phase of each implementation of the ticketing system for each location. The Contractor shall, after the kickoff meeting, provide a PMP that includes at a minimum:

5.3.1 Description of technical approach;

5.3.2 Organizational Resources;

5.3.3 Tasks and deliverables under this PWS, with due dates;

5.3.4 Contractor assignments (resource);

5.3.5 Milestone schedule that shows dependencies and critical path, as…