Appendix 2 - Presidential Libraries Ticketing System RVTM.xlsx

XLSX spreadsheet 51 KB Posted Jan 9, 2026

Attached to: Presidential Library Ticketing System
Solicitation number: 88310326Q00008
Issued by: National Archives and Records Administration

About this file

Written by GovTribe AI · Jan 9, 2026

This document is a Requirements Verification Traceability Matrix (RVTM) for the National Archives and Records Administration's (NARA) Presidential Library Ticketing System. The comprehensive matrix details 39 specific system requirements across multiple functional categories, including event management, ticket management, point-of-sale services, admissions, payment processing, and system architecture. Key requirements include capabilities such as managing event reservations, supporting self-service kiosks, processing payments, sending automated notifications, supporting multiple languages, maintaining an audit log, and ensuring system availability of 99.9% with responsive web and mobile interfaces.

The system must comply with numerous technical and regulatory standards, including NARA IT Security Requirements, Section 508 accessibility standards, PCI Data Security Standard, and compatibility with NARA's enterprise architecture. Critical technical specifications include exporting financial data to Microsoft Dynamics Great Plains, supporting IPv6, handling concurrent users during peak times, and interoperating with point-of-sale and kiosk hardware. The ticketing system is designed to support multiple Presidential Libraries, with each library able to customize its logo and color theme, and the system must provide role-based access control, training assistance, and robust reporting capabilities.

View the file

Other files

File	Type	Posted
88310326Q00008_0001 Presidential Library Ticketing System RFQ Amendment_FINAL.docx	DOCX document	Jan 28, 2026
Appendix 6 - Test Plan Template.pdf	PDF	Jan 9, 2026
Appendix 10 - Configuration Management Database Template.xlsx	XLSX spreadsheet	Jan 9, 2026
PWS Attachment 1_Ticketing System RVTM_Contractor Response Sheet FINAL.xlsx	XLSX spreadsheet	Jan 9, 2026
Appendix 8 - Test Report Template.docx	DOCX document	Jan 9, 2026
Appendix 13 - NARA Visual Identity Guide.pdf	PDF	Jan 9, 2026
Appendix 1 - NARA IT Security Requirements.pdf	PDF	Jan 9, 2026
Appendix 11 - Accessibility Requirements Tool - Ticketing Requirements.pdf	PDF	Jan 9, 2026
Appendix 7 - Test Procedures Template.xlsx	XLSX spreadsheet	Jan 9, 2026
88310326Q00008_Presidential Library Ticketing System RFQ_FINAL.docx	DOCX document	Jan 9, 2026
Appendix 4 - NARA Directive 1608_NARAs Privacy Program and Supplement.pdf	PDF	Jan 9, 2026
Appendix 3 - NARA Directive 804_Information Technology System Security.pdf	PDF	Jan 9, 2026
Appendix 5 - NARA Directive 1609_Initial Privacy Reviews and Privacy Impact Assessment.pdf	PDF	Jan 9, 2026
Appendix 9 - NARA SDLC Tailoring Plan for Presidential Libraries Ticketing System.pdf	PDF	Jan 9, 2026
Appendix 12 - NARA Website Requirements Checklist.xlsx	XLSX spreadsheet	Jan 9, 2026

Show all 15

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Title Page

NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)

Requirements Verification Traceability Matrix

(RVTM)

Presidential Library Ticketing System

Version: 1.0 FINAL

Prepared by the NARA Requirements & Risk Management Division (IR)

&F Page &P of

Requirements

REQUIREMENTS

MISC

DESIGN

DEVELOPMENT

VERIFICATION

DEPLOYMENT PREPARATION

Req #

Requirement Text

Type

Category

Sub-Category

Feature

Req Priority

Status

Target Release

Notes

Element

Iteration

Verification Method

Verification Test Case / Step

Verification Status

Verification Criteria

UAT Test Case

UAT Status

1.0

The solution shall provide the capability to manage events.

Business

N/A

Event Management

Must

Approved

Manage means to create, retrieve, edit and delete events.

Authorized users will be able to promote events online, customize event types including free events and paid events, seating charts, RSVP management etc.

1.1	The solution shall provide the capability for an authorized user to manage and customize forms for events.	Business	N/A	N/A	Event Management	Must	Approved	The system-generated forms shall contain all or a portion of the line items for events (i.e. attendee list only).
1.2	The solution shall provide the capability to manage timed entry schedules for events.	Business	N/A	N/A	Event Management	Must	Approved	Manage means to create, retrieve, edit and delete timed entry schedules for events.
1.3	The solution shall provide the capability to manage the number of attendees for events.	Business	N/A	N/A	Event Management	Must	Approved	Manage means to create, retrieve, edit and delete the minimum and maximum number of attendees for events.
1.4	The solution shall provide the capability to manage a waitlist for sold-out events.	Business	N/A	N/A	Event Management	Must	Approved	Manage means to create, retrieve, edit and delete the minimum and maximum number of attendees for events.
2.0	The solution shall provide the capability for attendees to manage the reservation of tickets for an event.	Business	N/A	N/A	Ticket Management	Must	Approved	Attendees will be able to buy or reserve a free or paid ticket, print a ticket, edit the ticket and cancel tickets online or at a kiosk at the venue.
2.1	The solution shall provide the capability for an authorized user to customize tickets for an event.	Business	N/A	N/A	Ticket Management	Must	Approved	System Administrators will be able to create different ticket categories (e.g., general admission, guided tour, special exhibition), pricing tiers including free tickets, offer add-ons, discounts, promo codes, and group rates to accommodate various visitor preferences and promotions.
2.2	The solution shall provide the capability to assign a Barcode with a unique identifier number to each event ticket.	Business	N/A	N/A	Ticket Management	Must	Approved
3.0	The solution shall provide the capability for onsite self-service kiosks.	Business	N/A	N/A	Kiosk	Must	Approved	Attendees will be able to buy or reserve tickets, look up their prior online ticket purchases and print tickets using the barcode at the kiosk.
4.0	The solution shall provide the capability for Point-of-Sale (POS) services.	Business	N/A	N/A	Point of Sale (POS)	Must	Approved	The POS will support the ability to create group sales, access group data, create new orders for existing groups on future dates (Backoffice abilities on iPad POS to include suspended events functionality), ability to book multiple group visits in one order and add promotional coupons to orders.
5.0	The solution shall provide the capability to manage orders.	Business	N/A	N/A	Order Management	Must	Approved	Manage means to create, retrieve (including events with a past date), update, and delete orders. This includes the ability to book multiple group visits in one order, print orders and invoices.
5.1	The solution shall provide the capability to process refunds for orders.	Business	N/A	N/A	Order Management	Must	Approved	The order total, amount paid and cost of tickets will be displayed when users are processing refunds.
5.2	The solution shall allow all users to make group reservations.	Business	N/A	N/A	Order Management	Must	Approved
6.0	The solution shall provide the capability to support automated self-check in.	Business	N/A	N/A	Admissions	Must	Approved
6.1	The solution shall provide the capability to support timed ticket entry for access to specific areas.	Business	N/A	N/A	Admissions	Must	Approved
6.2	The solution shall provide the capability for an authorized user to scan tickets.	Business	N/A	N/A	Admissions	Must	Approved	This includes the capability to scan tickets.
6.3	The system shall allow for the use of “forms” at on-site check-in or purchase, where staff may input data gathered from the visitor.	Business	N/A	N/A	Admissions	Must	Approved	The collection of data on-site or ordering tickets online. For example, zip code, email, etc.
7.0	REMOVED	Business	N/A	N/A	REMOVED	Would	Obsolete	REMOVED
8.0	The solution shall provide the capability to collect donations.	Business	N/A	N/A	Donation Collection	Must	Approved	This includes the ability to collect donations online at ticket purchase, at a POS and at an on-site kiosk.
9.0	The solution shall provide the capability to send both manual and automated batch emails containing links and attached documents to attendees.	Business	N/A	N/A	Email Notification	Must	Approved	This includes the ability to automatically email booking confirmation, invoices, event cancellations; email notifications 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 week before their visit and/or an email with a survey link one day after visit.)
10.0	The solution shall provide the capability to automatically send batch text messages containing links and attached documents to attendees who subscribe to receiving text message notifications.	Business	N/A	N/A	SMS Notification	Must	Approved	This will include the ability to automatically send text message notifications about booking confirmation, invoices, notification to inform users about special exhibitions, events, or library programs.
11.0	The solution shall provide the capability to accept cash and process payment from payment cards.	Business	N/A	N/A	Payment Processing	Must	Approved	This includes the ability to process payment online, at the kiosk and at the POS using gift cards, credit and debit (Visa/MC/Discover/Amex) with bluetooth.
12.0	The solution shall provide the capability to support multiple languages.	Business	N/A	N/A	Multilingual Support	Must	Approved	Languages including but not limited to French, German, Spanish, Japanese, and Chinese.
13.0	The solution shall maintain an audit log of all activities performed in the system.	Business	N/A	N/A	Auditing	Must	Approved	This include keeping a history all payment card transactions, events and orders created in the system.
14.0	The solution shall provide the capability to search for transactions, orders, and events.	Business	N/A	N/A	Search	Must	Approved	This includes the ability to perform a keyword search and partial keyword search for orders and events using order/transaction number, event name, event date, customer information, or credit card information (last four digits), group reservations information etc.
15.0	The solution shall provide the capability for an authorized user to manage standard and ad hoc reports.	Business	N/A	N/A	Reporting	Must	Approved	Manage means to create, retrieve, update, and delete reports. This also includes exporting reports in various formats, e.g., .csv, .pdf, .xls, and .xlsx formats.
16.0	The solution shall provide the capability for an authorized user to manage dashboards.	Business	N/A	N/A	Dashboard	Must	Approved	Manage means to create, retrieve, update, and delete interactive dashboards from reports such as charts, graphs, etc.

17.0	The solution shall support role-based access and account management.
Business	N/A	N/A	Account Management	Must	Approved		This will support the ability for a system administrator to manage (create, update, and delete) user accounts and role based permissions.
18.0	The solution shall provide the capability to associate an appropriate records schedule item to electronic records in the system.	Business	N/A	N/A	Records Management	Must	Approved	All federal records including those produced by the National Archives and Records Administration (NARA) are subject to the Federal Records Act, relevant sections of the Code of Federal Regulations, and NARA guidance and must be managed accordingly.

Associating records schedules with electronic records provides an inherent link between the NARA records schedule and an electronic records object. The records schedule item is 'associated' with the managed record objects as a rule, which determines the retention of the object.

19.0	The solution shall provide the capability for authorized users to configure the external and internal interface of the system.	Business	N/A	N/A	User Interface	Must	Approved	Each Presidential Library and Museum shall have its specific logo and color theme displayed for all users.
20.0	The solution shall have backup and recovery capabilities.	Business	N/A	N/A	Backup and Recovery	Must	Approved
21.0	The solution user interface shall be responsive for use of the system on mobile devices.

Business	N/A	N/A	Supportability	Must	Approved		This means the system has been designed to be responsive to the devices it’s viewed on, adjusting and resizing elements in order to optimally display across a broad range of devices, including desktop computers, laptops, tablets, and smartphones. Responsive design provides the best viewing experience independent of a user’s device.
22.0	The solution shall be accessible to a user via the web.	Business	N/A	N/A	Supportability	Must	Approved	The solution shall be accessible to a user using Mozilla Firefox, MS Edge, Google Chrome.

The browser versions to be supported will be dependent upon when the system is deployed into production and the browser versions supported in the NARA baseline at that time.

22.1	The system shall provide NARA the ability to incorporate their own subdomain name and URL for the ticketing system.	Business	N/A	N/A	Supportability	Must	Approved
23.0	The solution shall be in compliance with NARA IT Security Requirements.	Business	N/A	N/A	Security	Must	Approved	NARA IT Security Requirements are included in NARA IT Security Requirements, Version 7.4, 11/18/2023; and Security and Privacy Requirements for IT Acquisitions, Version 1.2, 12/19/2023.
24.0	The solution shall comply with NARA's Privacy Policy.	Business	N/A	N/A	Compliance	Must	Approved
25.0	The solution shall be in compliance with Section 508 Standards for Electronic and Information Technology.	Business	N/A	N/A	System Accessibility	Must	Approved
26.0	The solution shall be 99.9% available, 24 hours a day, 7 days a week, with the exception of scheduled downtime.	Business	N/A	N/A	Availability	Must	Approved	The scheduled downtime shall be no more than four (4) consecutive hours of downtime in a 24 hour period.
26.1	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.	Business	N/A	N/A	Availability	Must	Approved	The solution shall continue operating in the event of loss of internet connectivity and automatically sync all transactions and data upon restoration of internet connectivity.
27.0	The solution shall be compatible with NARA's Enterprise Architecture.	Business	N/A	N/A	System Architecture	Must	Approved
28.0	The solution shall export financial data in XML format to Microsoft Dynamics Great Plains (GP) for all sales transactions, except Zero-Dollar transactions.	Business	N/A	N/A	System Interoperability	Must	Approved	Microsoft Dynamics Great Plains (GP) is the back office financial accounting system.

The solution shall utilize unique order numbers across all libraries that identifies the originating library or have the ability to preface the order number with the library name before sending the XML document to the accounting system.

29.0	The solution shall only submit transactions with a financial impact to the back office accounting system.	Business Rule	Constraint	N/A	System Interoperability	Must	Approved	Zero-dollar transactions should not be submitted to the back office financial accounting system.
30.0	The solution shall be able to interoperate with Point of Sale (POS) hardware.	Business	N/A	N/A	System Interoperability	Must	Approved
31.0	The solution shall be able to interoperate with Kiosk hardware.	Business	N/A	N/A	System Interoperability	Must	Approved
32.0	The solution shall support Internet Protocol version 6 (IPv6).	Business	N/A	N/A	Hosting	Must	Approved
33.0	The solution shall scale to handle an increase in the number of concurrent users during customer activity peaks.	Business	N/A	N/A	Performance	Must	Approved
34.0	The solution shall scale to handle future data growth without major design or architectural changes.	Business	N/A	N/A	Elasticity	Must	Approved
35.0	The solution shall provide the capability for NARA users to have access to online training assistance for the solution.	Business	N/A	N/A	Training	Must	Approved
36.0	The solution shall be in compliance with the PCI Data Security Standard (PCI DSS) v3.0.	Business	N/A	N/A	Compliance	Must	Approved
37.0	The solution shall be in compliance with the payment processing requirements from the Department of Treasury's Bureau of the Fiscal Service.	Business	N/A	N/A	Compliance	Must	Approved
38.0	The solution shall be in compliance with requirements for navigation and effective user experience as described at https://digital.gov.	Business	N/A	N/A	Compliance	Must	Approved
39.0	The solution shall be in compliance with OMB Memorandum M-15-13, Policy to Require Secure Connections across Federal Websites and Web Services.	Business	N/A	N/A	Compliance	Must	Approved

&F Page &P of 4

Standard Values

Type	Category	Sub-Category			Priority
	Status	Verification Method		Verification Status		UAT Status
Business	Functional	Design	Specifies or constrains the options for designing a system. For example, if you specify that a relational database is required, that's a design constraint.		Must	Requirements that are CRITICAL to meeting the project's objectives and ensuring all core business needs are met. Not meeting a Must Have requirement will cause the project to be considered unacceptable to end users and/or a failure by key stakeholders	Approved	Inspection	Pass	Pass
Stakeholder	Non-Functional	Implementation	Specifies or constrains the coding or construction of a system. Examples might include required standards, implementation languages, and resource limits.		Should	Requirements that are of high value to end users and stakeholders and that should be included, but which can be excluded especially if a workaround exists that enables the core business needs to be met	Deferred	Analysis	Fail	Fail
System	Constraint	Interface	Specifies an external item with which a system must interact, or constraints on formats or other factors used within such an interaction.		Could	Requirements that are part of the project's scope and add or enhance project benefit	Draft	Test	N/A	N/A
Business Rule	N/A	Performance	Concerned with characteristics such as throughput, response time, recovery time, start-up time, and shutdown time.		Would	Requirements that do not have a significant impact on project benefits or could be considered as a “would like to have”	Obsolete	Demonstration
		Physical	Specifies a physical constraint imposed on the hardware used to house the system - shape, size, or weight, for example.					Certification
		Reliability	Concerned with characteristics such as availability (the amount of system "up time"), accuracy of system calculations, and the system's ability to recover from failure.					N/A
		Supportability	Concerned with characteristics such as testability, adaptability, maintainability, compatibility, configurability, installability, scalability, and localizability.
		Usability	Concerned with characteristics such as aesthetics and consistency in the user interface.
		N/A	Used for Business and Stakeholder requirements, as only Non-Functional requirements are assigned a Sub-Category.

<Project Name> Requirements Verification Traceability Matrix (RVTM) / &A

&F Page &P of

Column Descriptions

	Column Name	Column Descriptions	Required (Y/N?)
	Req #	A unique identifier for the requirement.	Yes
	Requirement Text	The text of the requirement.	Yes
	Type	The type of the requirement, such as "Business" or "Stakeholder".
Values: Business, Stakeholder, System, Business Rule	Yes
	Category	The category of the requirement, such as "Functional" or "Non-Functional".
Values: Functional, Non-Functional, Constraint, N/A	Yes; Use "N/A" for business requirements.
	Sub-Category	The sub-category of requirement that applies to Non-Functional requirements only. Values: Usability, Reliability, Supportability, Performance, Design, Implementation, Interface, Physical	Yes
	Feature	The high-level function, capability, feature or other grouping that has meaning for the stakeholders.	Yes
	Req Priority
	The priority of the stakeholder requirement as assigned by the stakeholders. Values: Must, Should, Could, Would	Yes
	Status	The status of the requirement. Values: Approved, Deferred, Draft, Obsolete	Yes
	Target Release	The release in which the requirement will be developed. Note that this column may be blank and hidden from view upon the initial documentation of the requirements, but should be updated during the appropriate phase of the project.	No
	Source	The source of the stakeholder requirement, such as "Business Case" or "Interview".	No
	Notes	Pertinent additional information about the requirement.	Yes; do not do not delete this column, just leave it empty if notes are not needed.
	Element	Used to indicate mapping of design elements (e.g., subsystem or class) that are relevant to the requirement. Requirements may map to more than one design element, in which case abbreviations or IDs are preferred over names when appropriate to the project, you may use multiple columns, one per type of design entity (e.g., subsystem).	Yes; when design elements are generated for the project. Use "N/A" for business requirements and at least one column (tracing) is required.
	Iteration	The iteration in which the requirements will be/is developed.

Yes, when iterations are used for the project. "N/A" for business requirements when the column is not needed, delete it.

Verification Method	The method used to verify the requirement. Values: Inspection, Analysis, Test, Demonstration, or Certification
Yes; Use "N/A" for business requirements.
Verification Test Case / Step	The test cases to be used by NARA to verify the requirement.
Yes; Use "N/A" for business requirements.
Verification Status	The output or final status after performing a verification test case on a requirement. Values: Pass, Fail	Yes; Use "N/A" for business requirements.
UAT Test Case	The test case used by NARA to validate the requirement.
Yes; Use "N/A" for business requirements.
UAT Status	The output or final status after performing a UAT test case on a requirement. Values: Pass, Fail, N/A	Yes; Use "N/A" for business requirements.
Verification Criteria	The attributes used to verify or determine if the system element meets the requirement and satisfies the design.	No

<Project Name> Requirements Verification Traceability Matrix (RVTM) / &A

&F Page &P of image1.png

File details come from the government source that posted it. Updated Jan 11, 2026.