Presidential Library Ticketing System

Amendment / Modification

This amendment (001) to Solicitation 88310326Q00008 for the Presidential Library Ticketing System introduces several key changes:

• Questions and Answers: Provides responses to vendor inquiries regarding the RFQ.
• RFQ Updates: Includes updates to the RFQ, with changes indicated by track changes or yellow highlighting.
• Due Date Extension: The deadline for receiving quotations has been extended to 1:00 PM EST on Thursday, February 5, 2026.
• Past Performance Questionnaire (PPQ) Due Date: The due date for the PPQ (Attachment 13) has been updated to February 5, 2026, aligning with the RFQ submission deadline.
• Accessibility Requirements: Clarifies that an Accessibility Conformance Report (ACR) is required, updating previous instructions regarding Appendix 12 and VPAT.
• Form Due Date: The due date for the Past Performance Questionnaire form has been updated to February 5, 2026.

• RFQ document (general updates)
• Attachment 10, Section 1.b.iii (Accessibility Requirements)
• Attachment 13 (Relevant Past Performance Questionnaire)
• Solicitation due date

The deadline for submitting quotations has been extended to February 5, 2026. Offerors must acknowledge receipt of this amendment.

Form / Attachment / Pricing Sheet

This document is a Requirements Verification Traceability Matrix (RVTM) for the National Archives and Records Administration (NARA) Ticketing System. It outlines the specific requirements for the system and provides columns for contractors to indicate their response, time to implement, and notes.

• Requirements: Details functional and non-functional requirements for the ticketing system, covering areas such as event management, ticket management, kiosk operations, POS services, order management, admissions, memberships, donation collection, email/SMS notifications, payment processing, multilingual support, auditing, reporting, dashboards, account management, records management, system interface, backup/recovery, supportability, security, compliance, availability, system architecture, and interoperability.
• Contractor's Response: A column for bidders to indicate how they will meet each requirement (e.g., using a scale from 0-4 based on the 'Legend for Fillable Values' sheet).
• Contractor's Time to Implement: A column for bidders to specify the time to implement each requirement (e.g., Ready at Award, +90 Days).
• Contractor's Notes: A column for bidders to provide brief explanations or additional details.
• Standard Values: Defines categories for requirements (Business, Stakeholder, System, BusinessRule, Functional, NonFunctional, Constraint) and their priority levels (Must, Should, Could, Would).

This RVTM is critical for bidders as it directly defines the technical and functional requirements for the NARA Ticketing System. Bidders must use this document to detail their proposed solution's capabilities, how each requirement will be met, and the associated implementation timeline. The responses provided in this matrix will form a key part of the technical proposal and will be used for evaluation.

Other / Unclassified

This document is NARA Directive 804, "Information Technology (IT) Systems Security." It establishes policy and guidance for securing all electronic information and IT systems used or operated by or on behalf of the National Archives and Records Administration (NARA). It defines the role of IT security within NARA's enterprise architecture, outlines the security management program structure, assigns responsibilities, and provides a foundation for measuring progress and compliance.

This directive is relevant to potential bidders as it outlines the security requirements and standards that NARA adheres to for its IT systems. Understanding these requirements is crucial for any vendor providing IT services or solutions to NARA, as compliance with these security policies and procedures will likely be a contractual obligation. The document references numerous external directives, laws, and standards (e.g., FISMA, NIST publications, OMB circulars) that form the basis of NARA's IT security program. It also details various roles and responsibilities within NARA related to IT security, including the Chief Information Officer (CIO), Chief Information Security Officer (CISO), and System Owners, which may be relevant for understanding points of contact and oversight within NARA for IT-related procurements.

Other / Unclassified

This document is NARA Directive 1609, titled "Initial Privacy Reviews and Privacy Impact Assessments." It establishes procedures and requirements for completing Initial Privacy Reviews (IPRs) and Privacy Impact Assessments (PIAs) for NARA's information technology (IT) systems and electronic information collections.

This directive is relevant to potential bidders as it outlines NARA's internal processes for assessing and mitigating privacy risks associated with IT systems and data collection. Understanding these requirements can inform bidders about NARA's data handling policies and security considerations, which may be relevant if their proposed solutions involve handling Personally Identifiable Information (PII) or interacting with NARA's IT infrastructure. It details the authorities, definitions, responsibilities of various NARA roles (CIO, SAOP, CISO, System Owners, etc.), and the specific processes for conducting IPRs and PIAs, including when they are required and what they must cover. The directive also introduces new forms (NA 8011 for IPRs and NA 8012 for PIAs) and specifies how these assessments are reviewed, approved, and published.

Form / Attachment / Pricing Sheet

This document, the "NARA Visual Identity Guide," provides comprehensive guidance on the proper use of the National Archives and Records Administration (NARA) brand and visual identity. It serves as a reference for maintaining a consistent and professional presentation of NARA's brand across all media.

• Logo Usage: Details on sizing, placement, and clear space requirements for the NARA logo.
• Color Palettes: Specifies primary color choices for print and web, including RGB, CMYK, and Hexadecimal values.
• Fonts: Recommends specific fonts (Merriweather and Source Sans Pro) for web and print, adhering to U.S. Web Design System standards.
• Branding Options: Outlines master branding, logo pairing with external organizations, and specific logos for NARA offices and affinity groups.
• Seals: Defines the appropriate use of the National Archives and National Archives Trust Fund seals.
• Graphic Elements: Includes guidance on using "Nate the Eagle" for youth events and specific templates for stationery, signage, digital signs, presentation slides, and email signatures.
• Contact Information: Provides an email address for inquiries regarding NARA's visual brand.

While this document is a style guide and not a solicitation, it is highly relevant for any potential bidder or contractor who will be creating materials for or on behalf of NARA. Adherence to these visual identity guidelines is likely a requirement for any contract involving the creation of NARA-branded content, communications, or products. Understanding these guidelines will help ensure proposals and deliverables meet NARA's branding standards.

Other / Unclassified

This document, "NARA IT Security Requirements Version 7.2," outlines the security requirements for the National Archives and Records Administration (NARA) IT systems. It is based on Federal Information Processing Standards (FIPS) 200 and NIST Special Publication 800-53, providing a comprehensive catalog of security and privacy controls to meet NARA's needs.

This document is crucial for potential bidders as it details the mandatory security and privacy controls that NARA systems must adhere to. Understanding these requirements is essential for developing solutions that meet NARA's security posture and compliance obligations under FISMA, the Privacy Act, and other relevant policies. Bidders should pay close attention to the specific control families and requirements outlined, as these will dictate the security features and functionalities expected in any proposed solution.

Form / Attachment / Pricing Sheet

This document is a template for creating a Test Plan for the National Archives and Records Administration (NARA). It provides a structured framework for outlining testing activities, objectives, roles, and processes for a given project.

• Document Control Sheet: Tracks revisions and versions.
• Table of Contents: Outlines the sections of the test plan.
• Introduction: Includes purpose, program overview, acronyms/definitions, and referenced documents.
• Test Process: Details the test schedule, roles and responsibilities, test objectives, acceptance criteria, defect management, reviews, reporting, test environment, and test data.
• Test and Evaluation: Covers test strategy, tasks, coverage, waivers/deviations, assumptions, constraints, risks, and mitigations.
• Appendices: Includes lists for acronyms, definitions, milestones, and roles/responsibilities.

This template is relevant to bidders as it indicates the expected structure and content for test plans that may be required as part of a Statement of Work (SOW) or Performance Work Statement (PWS). Understanding this template helps bidders anticipate the level of detail required for testing phases of a project and the associated documentation.

Form / Attachment / Pricing Sheet

This document provides a template for a Configuration Management Database (CMDB). It includes various sheets to detail project information, hardware and software configurations, revision history, and infrastructure as code repositories.

• CMDB Template Sheet: Contains sections for Hardware and Software, with columns for details such as Name/Hostname, Location, Manufacturer, Serial Number, Model Number, IP Address, NARA Asset Number, Software Installed, Vendor Name, Version, Patch Level, Operating System, and Instance.
• Project CMDB Cover Page Sheet: Fields for Version Number, Status, Date, Project Name, Order Number, and Contract Number.
• Revision History Sheet: Tracks changes with Date, Release #, Name, and Comment.
• Infrastructure as Code Sheet: Details Repository Name, Location/Path, Description, and Dependencies.
• Des. CMDB Cover page items Sheet: Provides descriptions for the fields on the Project CMDB Cover Tab and Revision History Tab, including guidance on how to fill optional fields like Order Number and Contract Number (use 'N/A' if not applicable).

This template is likely to be used by the awarded contractor to track and manage the project's hardware and software assets throughout the contract lifecycle. Bidders should review the structure and required fields to understand the expected level of detail for configuration management and asset tracking as part of their proposed approach or upon contract award.

Form / Attachment / Pricing Sheet

This document provides a template for test procedures, specifically designed for importing into an ALM (Application Lifecycle Management) system. It outlines the structure and content required for defining and documenting functional tests related to the NARA (National Archives and Records Administration) system.

• Test Name: Identifies the specific test case (e.g., '1.44.1 Images').
• Type: Specifies the testing method (e.g., 'Manual').
• Description: Provides a brief overview of the test's objective.
• Design Steps: Details the sequential actions to be performed during the test, including:
  • Step Name: A label for each step.
  • Description: Instructions for executing the step.
  • Expected Result: The anticipated outcome upon successful completion of the step.
• Requirement(s): Links the test case to specific system requirements.

This template is crucial for bidders to understand the expected format and detail level for test procedures if they are required to develop or execute them as part of the contract. It demonstrates the government's approach to quality assurance and testing for the NARA system, particularly concerning functional aspects like search and display of object designators and descriptions for various image types (JPG, GIF, TIFF).

Form / Attachment / Pricing Sheet

This document is an Excel spreadsheet containing a checklist of requirements for National Archives and Records Administration (NARA) websites. It serves as a guide for ensuring websites meet accessibility, security, legal, design, usability, and efficiency standards. Bidders should use this checklist to understand the NARA's expectations for website development and maintenance if the opportunity involves web-related services.

• Accessibility: Requirements for WCAG compliance, accessible PDFs and multimedia, descriptive alt text for images, high contrast text, identifiable links, clear forms, and an accessibility page.
• Security: Mandates for HTTPS, HSTS, email security, credential saving prevention, inclusion in NARA's website list, IT security scans, and secure hosting agreements.
• Legal: Guidelines for domain names (.gov), DNSSEC, clear indication of external links with disclaimers, privacy pages, FOIA information, and approval of third-party applications.
• Design: Adherence to NARA branding, specific fonts (Source Sans Pro, Merriweather), color palettes, UI components from the U.S. Web Design System, and inclusion of NARA's visual identity header and navigation bar.
• Usability: Requirements for plain language content, NARA Style Guide adherence, mobile-friendliness, clear contact information, search functionality, indication of file types/sizes, and approved forms.
• Efficiency: Quarterly content review, use of approved Content Management Systems (like Drupal), hosting within NARA's environment, and coordination with the National Archives Catalog for digital objects and digitization projects.

This checklist outlines critical compliance and technical requirements for any web-based project or service involving NARA. Bidders should review these requirements to assess their ability to meet NARA's standards for website development, design, security, and accessibility. Understanding these requirements is crucial for accurately estimating effort and proposing compliant solutions.

Other / Unclassified

This document is NARA Directive 1608, "NARA's Privacy Program." It establishes the National Archives and Records Administration's (NARA) privacy program and provides guidance to staff on protecting Personally Identifiable Information (PII) from unauthorized disclosure. It also outlines procedures for the proper disposal of records containing PII.

This directive is relevant to bidders as it details NARA's policies and procedures for handling sensitive information. Understanding these policies can help potential bidders ensure their proposals and operations align with NARA's privacy and data security requirements, particularly if the opportunity involves access to or handling of PII. It also highlights the existence of a "NARA 1608 Supplement" which details changes to the destruction of PII and references to "Datastroyer" and "burn bags" have been removed, with a focus on rendering records "unreadable or unrecoverable."

Solicitation / RFP / RFQ

This is a combined synopsis/solicitation (RFQ) for a Ticketing System for the National Archives and Records Administration (NARA) Presidential Libraries. The requirement is for a commercially available-off-the-shelf (COTS) cloud-hosted Software-as-a-Service (SaaS) solution. The goal is to provide an efficient, cost-effective, and high-quality user experience for visitors by integrating onsite and online sales, reservations, resource management, and reporting into a single system.

• A COTS cloud-hosted SaaS ticketing system with minimal configuration.

• Integration of onsite (box office, kiosks) and online (desktop, mobile) sales channels.

• Features include event scheduling, group reservations, donation collection, and timed ticketing.

• System must support various payment methods (credit cards, cash, checks) and be EMV compliant.

• Data migration of two years of ticketing data from legacy systems.

• Compliance with Section 508 Accessibility Standards.

• Security requirements including FedRAMP authorization and adherence to NARA IT security policies.

• Total small business set-aside.

• NAICS Code: 541519 (Other Computer Related Services).

• Period of Performance: Base year and four (4) option years.

• Questions due by January 20, 2026, 1:00 PM EST.

• Quotations due by February 3, 2026, 1:00 PM EST.

• Evaluation will be based on the best overall value to the Government, considering technical factors (product demonstration, technical understanding, management, past performance) and price. Technical factors are more important than price.

• Total small business set-aside.

• Reference Attachment 2 for the Performance Work Statement (PWS) for detailed requirements.

• Reference Attachment 11 for Evaluation Factors for Award.

Form / Attachment / Pricing Sheet

This document, "Appendix 12 - Accessibility Requirements Tool - Ticketing Requirements," outlines the artifacts vendors are required to provide to demonstrate Section 508 Accessibility Compliance.

Vendors are requested to submit the following three artifacts:

• Voluntary Product Accessibility Template (VPAT)
• Accessibility Conformance Report (ACR)
• Supplemental Accessibility Report (SAR)

This appendix specifies mandatory documentation for ensuring accessibility compliance. Bidders must prepare and submit these reports as part of their response to demonstrate adherence to Section 508 standards.

Form / Attachment / Pricing Sheet

This document is a Requirements Verification Traceability Matrix (RVTM) for the Presidential Library Ticketing System. It outlines the specific requirements for the system, categorized by type, feature, and priority, along with their verification methods and status. Bidders should use this document to understand the detailed functional and non-functional requirements of the ticketing system.

• Requirements: Details specific capabilities the system must possess, such as event management, ticket management, kiosk functionality, POS services, order management, admissions support, donation collection, email/SMS notifications, payment processing, multilingual support, auditing, reporting, dashboards, account management, records management, user interface configuration, backup/recovery, responsiveness for mobile devices, web accessibility, subdomain support, security compliance (NARA IT Security Requirements, PCI DSS), privacy policy compliance, Section 508 standards, availability (99.9%), offline mode, enterprise architecture compatibility, and interoperability with financial systems (Microsoft Dynamics GP).
• Verification: Specifies how each requirement will be verified (e.g., Inspection, Analysis, Test, Demonstration, Certification) and the expected status (Pass/Fail).
• Priorities: Requirements are prioritized as Must, Should, Could, or Would.

This RVTM provides a comprehensive list of mandatory and desired functionalities for the Presidential Library Ticketing System. Bidders must review these requirements to ensure their proposed solution can meet all 'Must' requirements and to understand the scope of work. It serves as a critical reference for developing technical proposals and demonstrating compliance with NARA's needs.

Other / Unclassified

This document is a Tailoring Plan & Stage Gate Approvals form (NA Form 8024) for the "Presidential Libraries Ticketing System" project. It outlines the project's scope, objectives, strategic alignment, development methodology (Waterfall), and the various stage gates and work products required for its lifecycle, including Enterprise Architecture Review, Acquisition Planning, Concept Development, Risk Management, Configuration Management, Project Management, Requirements, Design, Testing, Operations Readiness, Operations and Maintenance, and Security.

While this document is primarily an internal planning and approval tool for the National Archives and Records Administration (NARA), it provides insight into the project's structured approach and the rigorous review processes involved. Bidders may find it useful to understand the project's defined scope, objectives, and the types of deliverables and documentation (e.g., Business Need, Acquisition Strategy, CONOPS, System Design Document, Test Plan) that will be required throughout the project lifecycle. The document also indicates a security categorization of Moderate for Confidentiality, Integrity, and Availability, and specifies Section 508 compliance requirements for the application/website (WCAG 2.0 Level AA standards).