PWS Attachment 1_Ticketing System RVTM_Contractor Response Sheet FINAL.xlsx
XLSX spreadsheet 116 KB Posted
- Solicitation number
- 88310325Q00018
About this file
This document is a Requirements Verification Traceability Matrix (RVTM) for a ticketing system for the National Archives and Records Administration (NARA). The RVTM outlines 40 key requirements for the ticketing system, including the ability to manage events, process ticket reservations and sales, provide self-service kiosks and point-of-sale services, manage memberships and donations, send notifications, process payments, support multiple languages, maintain audit logs, generate reports, enable role-based access, and comply with various security and accessibility standards.
The RVTM is associated with a draft Request for Quotation (RFQ) for a National Archives in Washington D.C. and Presidential Libraries Ticketing System. This draft RFQ is being provided for informational purposes only, and NARA will not be accepting any quotations or proposals in response to this draft. Interested parties may provide feedback, suggestions or questions for consideration by the November 18, 2024 deadline.
View the file
Other files
Show all 14
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
Title Page
NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)
| Requirements Verification Traceability Matrix |
| (RVTM) |
NARA Ticketing System
&F Page &P of
Requirements
| REQUIREMENTS | MISC | DESIGN | DEVELOPMENT | VERIFICATION | DEPLOYMENT PREPARATION | CONTRACTOR'S RESPONSE | CONTRACTOR'S TIME TO IMPLEMENT | CONTRACTOR'S NOTES | ||||||||||||||
| Req # | Requirement Text | Type | Category | Sub-Category | Feature | Req Priority | Target Release | Process Description | Use Case | Notes | Element | Iteration | Verification Method | Verification Test Case / Step | Verification Status | Verification Criteria | UAT Test Case | UAT Status | Stakeholder Group | 0-4 | Ready at Award through +90 Days | (May be Used for Brief explanations, where applicable) |
| 1.0 | The solution shall provide the capability to manage events. | Business | Event Management | 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. L
PL
| 1.1 | The solution shall provide the capability for an authorized user to manage and customize forms for events. | Business | Event Management | The system-generated forms shall contain all or a portion of the line items for events (i.e. attendee list only). | PL |
| 1.2 | The solution shall provide the capability to manage timed entry schedules for events. | Business | Event Management | Manage means to create, retrieve, edit and delete timed entry schedules for events. | L |
PL
1.3 The solution shall provide the capability to manage the number of attendees for events. Business Event Management Manage means to create, retrieve, edit and delete the minimum and maximum number of attendees for events. L
PL
| 1.4 | The solution shall provide the capability to manage a waitlist for sold-out events. | Business | Event Management | Manage means to create, retrieve, edit and delete the minimum and maximum number of attendees for events. | L |
| 2.0 | The solution shall provide the capability for attendees to manage the reservation of tickets for an event. | Business | Ticket Management | 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. | L |
PL
2.1 The solution shall provide the capability for an authorized user to customize tickets for an event. Business Ticket Management 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. L
PL
2.2 The solution shall provide the capability to assign a Barcode with a unique identifier number to each event ticket. Business Ticket Management L
PL
3.0 The solution shall provide the capability for onsite self-service kiosks. Business Kiosk 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. L
PL
| 4.0 | The solution shall provide the capability for Point-of-Sale (POS) services. | Business | POS | 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. | PL |
| 5.0 | The solution shall provide the capability to manage orders. | Business | Order Management | 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. | L |
PL
| 5.1 | The solution shall provide the capability to process refunds for orders. | Business | Order Management | The order total, amount paid and cost of tickets will be displayed when users are processing refunds. | PL |
| 6.0 | The solution shall provide the capability to support automated self-check in. | Business | Admissions | L |
PL
6.1 The solution shall provide the capability to support timed ticket entry for access to specific areas. Business Admissions L
PL
| 6.2 | The solution shall provide the capability for an authorized user to scan tickets. | Business | Admissions | This includes the capability to scan tickets as visitors enter the rotunda. | L |
| 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 such as zip code or email, etc. | Business | Admissions | The collection of data on-site or ordering tickets online. | PL |
| 7.0 | The solution shall provide the capability to establish memberships. | Business | Memberships | This includes the ability to manage a list of members, contact members and offer discounts to members | L |
PL
| 8.0 | The solution shall provide the capability to collect donations. | Business | Donation Collection | This includes the ability to collect donations online at ticket purchase, at a POS and at an on-site kiosk. | ||
| PL | ||||||
| 9.0 | The solution shall provide the capability to send both manual and automated batch emails with attached documents/URLs to attendees. | Business | Email Notification | 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.) | L |
PL
| 10.0 | The solution shall provide the capability to automatically send batch SMS messages with attached documents/URLs to attendees who subscribe to receiving SMS notifications. | Business | SMS Notification | This will include the ability to automatically send SMS notification about booking confirmation, invoices, renewal reminders for members, notification to inform users about special exhibitions, events, or library programs. | L | |
| 11.0 | The solution shall provide the capability to accept cash and process payment from payment cards. | Business | Payment Processing | 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. | PL | |
| 12.0 | The solution shall provide the capability to support multiple languages. | Business | Multilingual Support | Languages including but not limited to French, German, Spanish, Japanese, and Chinese. | L | |
| 13.0 | The solution shall maintain an audit log of all activities performed in the system. | Business | NA | Auditing | This include keeping a history all payment card transactions, events and orders created in the system. | L |
PL
14.0 The solution shall provide the capability to search for transactions, orders and events. Business Order Management 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. L
PL
15.0 The solution shall provide the capability for an authorized user to manage standard and ad hoc reports. Business Reporting 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. L
PL
| 16.0 | The solution shall provide the capability for an authorized user to manage dashboards. | Business | Dashboard | Manage means to create, retrieve, update, and delete interactive dashboards from reports such as charts, graphs, etc. | |||
| L | |||||||
| 17.0 | The solution shall support role-based access and account management. | ||||||
| Business | Account Management | This will support the ability for a system administrator to manage (create, update, and delete) user accounts and role based permissions. | L | ||||
| 18.0 | The solution shall provide the capability to associate an appropriate records schedule item to electronic records in the system. | Business | Records Management | 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. L
PL
| 19.0 | The solution shall provide the capability for authorized users to configure the external and internal interface of the system. | Business | System Interface | Each Presidential Library and Museum shall have its specific logo and color theme displayed for all users. | L |
| 20.0 | The solution shall have backup and recovery capabilities. | Business | Backup and Recovery | L |
PL
21.0 The solution user interface shall be responsive for use of the system on mobile devices.
Business Supportability 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. L
PL
22.0 The solution shall be accessible to a user via the web. Business Supportability 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. L
PL
22.1 The system shall provide NARA the ability to incorporate their own subdomain name and URL for the ticketing system. Business Supportability L
PL
23.0 The solution shall be in compliance with NARA IT Security Requirements. Business Security L
PL
24.0 The solution shall comply with NARA's Privacy Policy. Business Compliance L
PL
25.0 The solution shall be in compliance with Section 508 Standards for Electronic and Information Technology. Business System Accessibility L
PL
26.0 The solution shall be 99% available, 24 hours a day, 7 days a week, with the exception of scheduled downtime. Business Availability The scheduled downtime shall be no more than four (4) consecutive hours of downtime in a 24 hour period. L
PL
27.0 The solution shall be compatible with NARA's Enterprise Architecture. Business System Architecture L
PL
28.0 The solution shall integrate with internal and external systems. Business System Interoperability L
PL
28.1 The solution shall integrate with Microsoft Dynamics Great Plains (GP) for the submission of sales transaction. Business System Interoperability 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. | PL | ||||||
| 29.0 | The solution shall only submit transactions with a financial impact to the back office accounting system. | BusinessRule | System Interoperability | Zero-dollar transactions should not be submitted to the back office financial accounting system. | PL | ||
| 30.0 | The solution shall be able to interoperate with a POS hardware. | Business | System Interoperability | PL | |||
| 31.0 | The solution shall be able to interoperate with a Kiosk hardware. | Business | System Interoperability | L |
PL
32.0 The solution shall support Internet Protocol version 6 (IPv6). Business Hosting L
PL
33.0 The solution shall scale to handle increase in the number of concurrent users during customer activity peaks. Business Performance L
PL
34.0 The solution shall scale to handle future data growth without major design or architectural changes. Business Elasticity L
PL
| 35.0 | The solution shall provide the capability for NARA users to have access to online training assistance for the solution. | Business | Training | L |
| 36.0 | The solution shall be in compliance with the PCI Data Security Standard (PCI DSS) v3.0. | Business | Compliance | L |
PL
| 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 | Compliance | PL |
| 38.0 | The solution shall be in compliance with requirements for navigation and effective user experience as described at www.usability.gov and www.digitalgov.gov. | Business | Compliance | L |
| 39.0 | The solution shall be in compliance with OMB Memorandum M-15-12, Policy to Require Secure Connections across Federal Websites and Web Services. | Business | Compliance | L |
PL
40 The solution shall allow all users to make group reservations. Business Order Management The ticketing system shall provide a barcode and its associated unique sequence of numbers for each individual within the group. L
&F Page &P of
Standard Values
| Type | Business | Stakeholder | System | BusinessRule | NA | Functional | NonFunctional | Constraint | Constraint. | Priority | |||||||
| Status | Verification Method | Verification Status | UAT Status | ||||||||||||||
| Business | NA | Functional | Functional | Constraint. | NA | NA | Usability | Concerned with characteristics such as aesthetics and consistency in the user interface. | 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. | NA | 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 | NonFunctional | NonFunctional | 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. | 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 | Constraint | Performance | Concerned with characteristics such as throughput, response time, recovery time, start-up time, and shutdown time. | 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 | NA | NA | |||||
| BusinessRule | Supportability | Concerned with characteristics such as testability, adaptability, maintainability, compatibility, configurability, installability, scalability, and localizability. | Physical | Specifies a physical constraint imposed on the hardware used to house the system — shape, size, or weight, for example. | Would | Requirements that do not have a significant impact on project benefits or could be considered as a “would like to have” | Obsolete | Demonstration | |||||||||
| Certification | |||||||||||||||||
| NA |
<Project Name> Requirements Verification Traceability Matrix (RVTM) / &A
&F Page &P of
WARNING! Some of the information in this worksheet is used to implement cascading drop-down lists in the 'Requirements' worksheet, be aware of this when modifying it, and especially when deleting columns! Refer to the 'Notes' worksheet for more information.
Legend for Fillable Values
| Legend | |
| 0 - Cannot Meet | Cannot meet the requirement. Use this value if the solution cannot meet the requirement. |
| 1 - Requires Significant Development | Requires significant customization or development (modification of source). Use this value if the solution will require changes or new development at the source code level to meet the requirement. |
| 2 - Requires Advanced Configuration | Requires advanced configuration or custom development using an SDK or API. Use this value if the solution will customization using an SDK or API to meet the requirement. |
| 3 - Requires Minimal Enhancement | Requires minimal or no special enhancements. Use this value if the solution meets the requirement with minimal configuration. |
| 4 - Requires No Enhancement | Use this value if the solution meets the requirement without configuration or enhancement. |
Include costs as part of your Volume III submission for individual or grouped items in the response for each item marked 1, 2, or 3.
| Time |
| Ready at time of award |
| 30 days from award |
| 60 days from award |
| 90+ days from award |
image1.png
File details come from the government source that posted it. Updated .