88310324RFI00006 Request for Information - Market Research Archives I and PL Ticketing System.docx
DOCX document 339 KB Posted
- Solicitation number
- 88310324RFI00006
About this file
This document is a Request for Information (RFI) issued by the National Archives and Records Administration (NARA) to obtain information about commercially available software-as-a-service (SaaS) cloud-hosted ticketing and visitor management solutions for NARA's Archives I in Washington, D.C. and its Presidential Libraries across the country.
NARA is seeking a single, integrated ticketing system that can handle online and onsite sales, individual and group reservations, memberships, resource management, and reporting for both the Archives I and the Presidential Libraries. The goals are to ensure consistency and automation of attendance and sales data, simplify financial processing and system maintenance, and provide a convenient visitor experience. NARA is interested in SaaS solutions that are FedRAMP authorized at the moderate level, focused on small to mid-sized organizations, and do not require extensive configuration or integration. Responses to this RFI should be submitted by July 9, 2024, and NARA may choose to engage with respondents to clarify aspects of their responses. This RFI is for market research and planning purposes only and does not constitute a solicitation.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 88310324RFI00006 Archives I and Presidential Libraries Ticketing System Q and A FINAL.docx | DOCX document | |
| NARA Ticketing System RFI RVTM 2024June07.xlsx | XLSX spreadsheet | |
| L and P Ticketing System Performance Work Statement DRAFT Working Copy.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
NATIONAL ARCHIVES AND RECORDS ADMINISTRATION
REQUEST FOR INFORMATION
National Archives in Washington, D.C. and Presidential Libraries Ticketing System
NAMA-24-RFI-0006
1.0 Introduction
The National Archives and Records Administration (NARA) is an independent Federal agency that helps safeguard and preserve our nation's history by overseeing the management of all Federal records. The stories of our nation and our people are told in the records and artifacts cared for in NARA facilities around the country and people can discover, use, and learn from this documentary heritage. The mission is to ensure ready access to the essential evidence that documents the rights of American citizens, the actions of Federal officials, and the national experience.
This Request for Information (RFI) is intended strictly for market research. It is issued for information and planning purposes only and does not constitute a solicitation. Potential solutions presented may or may not lead to a solicitation. Any decision to proceed with a solicitation would be based, in part, on available funding.
NARA is a small agency with limited internal information technology (IT) development and systems engineering resources, we are interested in SaaS solutions that:
| • | Are focused on small to mid-sized organizations; |
| • | Do not require extensive technology configuration and integration efforts; and |
| • | Are FedRAMP Authorized at the moderate level or, at a minimum, hosted in infrastructure-as-a-service (IaaS) and / or platform-as-a-service (PaaS) cloud services which are FedRAMP Authorized at the moderate level. |
2.0 Description/Objective
NARA’s Public Museum Engagement and Legislative Archive (L) operates and manages the Rotunda, exhibit spaces, and learning space at the National Archives in Washington, D.C. (Archives I) and the Office of Presidential Libraries (PL) operates and manages the Presidential Libraries and Museums around the country. Nearly two million visitors each year come to the physical sites of the National Archives, primarily Archives I and the Presidential Libraries, to view exhibits or participate in education and public programs.
Presently visitors to the Archives I and the Presidential Libraries use separate ticketing systems. Archives I uses Recreation.gov for its online ticketing capabilities. Recreation.gov is the federal government’s centralized travel planning and reservation platform that allows users to find and reserve experiences at 14 federal agencies. Admission to Archives I is free but an advance reservation convenience fee of $1 is charged for each ticket to those using Recreation.gov to reserve tickets before their visit. Tickets reserved online allow users to have a timed entry thereby bypassing potentially long lines waiting to enter the exhibits. The exhibit space and learning space in Archives I are currently undergoing renovations that are planned to be completed in the summer of 2025. NARA’s objective is to enhance the visitor experience through updated ticketing capability to coincide with the completion of the renovations.
NARA’s PL use a paid entry ticketing system that is provided by ACME Technologies, referred to as the Visitor Services System (VSS). VSS is a software as a service (SaaS) ticketing, payment, event, and resource management solution that integrates with NARA’s implementation of Microsoft Dynamics Great Plains to manage its financial transactions. The SaaS application includes tenants for 13 of the Presidential Libraries and Museums. The Eight (8) libraries listed below use the system to support onsite ticket sales, handled through a “box office” model where NARA personnel handle the transactions onsite at a point of sale (POS) system; reserve school groups and other group tours; and manage facility rentals and equipment reservations for those rentals.
· 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
· Museum – Grand Rapids, MI
· Jimmy Carter Presidential Library and Museum, Atlanta, GA
· George H.W. Bush Presidential Library and Museum, College Station, TX The remaining Presidential Libraries that do not use the POS front-end, use an alternative ticketing system not within the scope of this contract. However, they do use VSS to manage the sharing and storage of visitor statistics collected via the alternative ticketing systems. The Libraries that use the system to collect third-party ticketing information for statistical review include:
● Lyndon Baines Johnson Presidential Library and Museum, Austin, TX
● Richard Nixon Presidential Library and Museum, Yorba Linda, CA
● Ronald Reagan Presidential Library and Museum, Simi Valley, CA
● William J. Clinton Presidential Library and Museum, Little Rock, AR
● George W. Bush Presidential Library, Dallas, TX NARA’s existing contract with ACME Technologies has one option period remaining which will end in September of 2025.
As a component of the Archives I renovation effort, NARA would like to combine its ticketing capabilities into one configurable solution for a more efficient and cost-effective means of providing a high quality user experience to all of its visitors. NARA issues this RFI to obtain technical information about commercially available SaaS cloud hosted products that can be used by NARA as an enterprise ticketing, admission and visitor, and event management system for both the Archives I and the Presidential Libraries. NARA requires a system that will integrate onsite and online sales, individual and group reservations, add, manage, and track memberships, provide resource management and reporting into a single user-friendly and configurable system for both the Archives I and the Presidential Libraries. 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.
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. A ticketing system will also assist with managing visitor flow through advanced ticket sales and timed ticketing reservations.
NARA requires a Contractor to furnish, configure and deploy a SaaS ticketing system that is scalable; cloud-hosted; capable of meeting NARA’s needs with minimal integration and configuration modifications; and does not require significant changes to business processes or employee workflows. The Contractor shall be responsible for the full project lifecycle, which includes, but is not limited to: migration of legacy data to the new system (if applicable), reconciliation of all legacy data, configuration of the system; deployment; training of the NARA internal users on the operations of the system; operations and maintenance of the system; periodic enhancements to the system for Archives I and each of NARA’s Presidential Libraries; and eventual migration at the end of the period of performance. The working draft of the Performance Work Statement (PWS) for this requirement is included as an attachment to this RFI. NARA’s draft system requirements are included in the attached Requirements Verification Traceability Matrix (RVTM). Reference attached excel spreadsheet entitled “L Ticketing System_RVTM_ 2024June7”.
3.0 Response Instructions
3.1 Content
Briefly describe your company, products and services, history, ownership, financial information, and other information you deem relevant. Provide points of contact, company address, phone/fax number, email, website, and business size and type (i.e. large business, small business, small disadvantaged business, HUBZone small business, woman-owned small business, service-disabled veteran-owned small business). Include any appropriate copyrighted, patented, trademark, or sensitive information markings. Additionally, provide your Unique Entity Identifier (UEI) for validation of your www.sam.gov registration.
You are encouraged to provide information on your company’s products and services in support of the stated need. Respond only if you can provide the total solution. Indicate whether your product is commercially available or is on the General Services Administration Federal Supply Schedule or other Government-wide Acquisition Contract (GWAC). Specifically provide comments on any stated requirements that you believe cannot be implemented with a SaaS solution. Furthermore, please include substantive responses to the following questions:
| 1. | How many years has your company been in the SaaS ticketing solution business? |
| 2. | Who are some of your clients and have you worked with federal government agencies? |
| 3. | Do your clients tend to use your whole system, or if not, what parts of your system do they use and which ones do they not use? |
| 4. | Is your ticketing solution a SaaS, cloud-hosted system? |
| 5. | Is your ticketing solution a commercial-off-the-shelf (COTS) service? |
| 6. | Is your SaaS FedRAMP Authorized at the moderate impact level? |
| 7. | If your SaaS is not FedRAMP Authorized, is it hosted in a FedRAMP Authorized infrastructure-as-a-service (IaaS) or platform-as-a-service (PaaS) at the moderate impact level? |
| 8. | How does your system protect PII data? |
| 9. | Identify which cloud service provider (CSP) hosts your SaaS. |
| 10. | Does your SaaS have redundancy/backup capabilities? If so, describe how your backup ensures continuous operations for the end users. |
| 11. | Can your system continue to process transactions if internet connectivity is disrupted? If so, please describe how. |
| 12. | Does your ticketing solution provide for a point of sale (POS) device (on site at multiple separate, physical locations across the United States), a business-to-business (B2B), back office (also accessible on site through individual URLs for 13 individual libraries), a sandbox, test environment of each back office tenant and each POS for testing, and an online ticketing sales portal that mimics the look and feel of an institutions’ multiple websites? |
| 13. | Note that all credit card activity must be processed using the bank and processor contracted by the Department of Treasury. NARA does not have any control over this aspect of the requirements as it is mandated by the Department of Treasury. The platform is currently WorldPay and NARA has integrated with that using Element. Is your solution compatible with WorldPay/Element for credit card processing across all three ticket sales platforms (POS, B2B, Online)? |
| 14. | Our agency is required by the Department of Treasury to be the merchant of record for all credit card purchases and processing. Does your solution allow for this? |
| 15. | At what frequency are vulnerability scans performed by your company on your customer’s platforms and what information is collected? |
| 16. | Does your company share vulnerability scan results with your customer’s IT Security departments? |
| 17 | Describe your security program. What is your process to minimize vulnerabilities and risks to your system/solution? |
| 18. | Login access to any cloud service must pass through NARA’s internal Lightweight Directory Access Protocol (LDAP). Access to the use of the system is controlled through NARA’s procedures (authorization use form for each user, including access by the vendor/contractor to NARA’s instance). Does your solution support the integration of an LDAP environment? |
| 19. | NARA requires all devices processing sensitive personally identifiable information (PII) and payment transactions (regardless of method of payment) to be connected to NARA’s Network through wired Ethernet connections (i.e. wireless network connections are not permitted). What hardware and/or peripherals work with your ticketing solution for POS/Front Desk Admissions? |
| 20. | Are your peripherals and SaaS Europay, Mastercard, and Visa (EMV)-compliant and compatible? |
| 21. | Please describe what is and is not included in your product support. |
| 22. | What hours and levels of support do you provide? |
| 23. | Do you charge fees per transaction and how is this captured? |
| 24. | Entrance into the National Archives in Washington, D.C. exhibit space and Rotunda is free. What is your pricing model for free admissions? |
| 25. | What is your pricing model for paid entry tickets? (e.g. fee per ticket / transaction added to the price of the ticket and paid by the customer, fixed price to the agency per ticket sold based on volume, etc.) |
| 26. | Are you able to migrate data provided by a prior vendor that includes ticket categories, quantities, payments, revenues, organization names, and addresses (tour companies, school groups, client, corporation personal and non-profit organizations), events, dates, zip codes and other pertinent information, into your system as legacy data? |
| 27. | Does your solution have the capability to import monthly ticket categories, quantities and program names/types, using a .CSV or similar file? |
| 28. | Are you able to accept supplementary visitor information such as email, zip code, phone number, etc., and does your reporting allow for Metropolitan Statistical Area (MSA) reporting? |
| 29. | What is the uptime / downtime of your system? |
| 30. | Does your ticketing SaaS provide the capability to customize the styling and branding to align with NARA agency brand and style guide and the US Web Design System principles, including mobile-friendly interfaces? |
| 31. | Is your system Section 508-compliant? Do you have proof and can provide that information? |
| 32. | Does your ticketing SaaS provide the capability to customize the visitor experience by having the visitor select events and/or exhibit areas of interest to them from a list so they can reserve a time and/or space? |
| 33. | Does your solution provide the option for on-site ticketing kiosks for use by visitors? If so, what possible actions can be performed at a kiosk? |
| 34. | Does your ticketing solution allow the public to self-edit their reservation day/time? Can users cancel? |
| 35. | Does your ticketing system allow visitors to complete self check-in and/or check-in via a ticket scanner? |
| 36. | Does your solution allow for the collection of public donations, both online at ticket purchase and/or via on-site kiosks? |
| 37. | Does your solution allow for manual and/or automated sending of batch emails to guests based on reservation date or other criteria? |
| 38. | Can your system send email invoices and collect payments for custom bookings? |
| 39. | Can your system provide private weblinks for private events/rentals with custom pay portals? |
| 40. | NARA would like to provide the subdomain name and URL. How would your ticketing system accommodate this? |
| 41. | Please describe your reports functionalities and the process for running reports. Can your reports function compile data into counties using zip code data? |
| 42. | Can any of your public-facing features be translated into other languages as necessary by guests? |
| 43. | Do you provide software and hardware support for all related devices? |
| 44. | If not, for which components do you provide support? |
| 45. | What is your realistic, estimated, time frame for implementation of the Archives I ticketing system from date of award in units of Months and Days based on the requirements as stated in this RFI? |
| 46. | What risks or dependencies may impact the estimated implementation timeframe to meet NARA’s requirements for Archives I? |
| 47. | What is your realistic, estimated, time frame for implementation of the Presidential Libraries in units of Months and Days based on the requirements as stated in this RFI? |
| 48. | What risks or dependencies may impact the estimated implementation timeframe to meet NARA’s requirements for Presidential Libraries? |
Additionally, Contractors are encouraged to provide recommendations concerning the requirements in the PWS and the RVTM enclosed with this RFI.
3.2 Format
Responses shall be submitted electronically in Microsoft Word or Portable Document Format (PDF). Supplemental product brochures or marketing materials outlining specifications and capabilities may also be submitted.
3.3 Due Date
Each RFI response should be e-mailed to the Points of Contact listed below. The subject of the email should be "National Archives and PL Ticketing System RFI Response (88310324RFI00006)". Responses to this RFI should be received by 4:00 PM ET on July 9, 2024. Responses submitted after this date and time may not be accepted. Firms submitting via e-mail are cautioned to allow one extra business day for delivery and confirm receipt of response as the e-mail will need to pass through IT security.
3.4 Questions
Questions regarding this RFI shall be submitted in writing via email to the Points of Contact listed below by 12:00 PM ET on June 21, 2024. Verbal questions will not be accepted.
4.0 Disclaimer
This RFI is issued for information and planning purposes only and does not constitute a solicitation. The Government does not intend to award a contract on the basis of this RFI or to otherwise pay for information received in response to this RFI. All information received in response to this RFI that is marked “Proprietary” will be handled accordingly. Responses to the RFI will not be returned. Information provided in response to this RFI will be used to assess tradeoffs and alternatives available for determining how to proceed in the acquisition process and may lead to the development of a work statement. Responders are solely responsible for all expenses associated with responding to this RFI.
5.0 Industry Engagement
NARA may choose to engage with responders. However, such engagement is intended to clarify aspects of the response.
6.0 Points of Contact
James Philiposian (Contractor), Contract Specialist james.philiposian@nara.gov and
Kevin Monahan, Contracting Officer kevin.monahan@nara.gov
File details come from the government source that posted it. Updated .