88310324RFI00006 Archives I and Presidential Libraries Ticketing System Q and A FINAL.docx

1. QUESTION: REDACTED is not designed to work across different time zones, are you open to licensing multiple databases and eCommerce sites to meet the needs of presidential libraries outside of the eastern time zone?

ANSWER: NARA is open to licensing multiple databases and eCommerce sites outside of the eastern time zone.

2. QUESTION: If the answer to question 1 is yes, is it required that integrations between systems be real-time or are scheduled imports/exports of data acceptable?

ANSWER: NARA requires real-time access to its data across each of its locations.

3. QUESTION: Please describe the integration requirements for NARA’s LDAP for internal user authentication.

ANSWER: The ticketing system shall be compliant with HSPD-12 by either directly accepting Personal Identification Verification (PIV) credentials as the common means of authentication for access for federal employees and contractors or use of NARA’s centralized SAML/LDAP authentication platform which requires compatibility with Security Assertion Markup Language (SAML) and Lightweight Directory Access Protocol (LDAP) protocols. NARA is now using EntraID as its preferred directory service and the new ticketing system should be able to integrate with it. EntraID supports both SAML and LDAP authentication which are standard technologies by which to integrate.

4. QUESTION: If a SaaS is unable to meet those requirements, is multi-factor authentication login acceptable?

ANSWER: The solution must meet the requirements as defined in the answer to question 3.

5. QUESTION: Is hosting in Amazon Web Services (AWS) acceptable?

ANSWER: Reference PWS paragraph 4.2.1.

6. QUESTION: Is NARA open to negotiating contracts based off of our standard license agreement and product and services agreement?

ANSWER: Reference FAR 52.212-4, Contract Terms and Conditions—Commercial Products and Commercial Services paragraphs (s)(4) and (u).

7. QUESTION: What is the estimated operating budget for each location that plans to use the chosen software this fiscal year?

ANSWER: NARA will not be providing the total operating cost estimates or the operating budget estimates per location at this time. Vendors are encouraged to provide rough order of cost estimates for some or all components of its solution with its submission.

8. QUESTION: What is the total number of staff members across all organizations who hope to use the chosen software?

ANSWER: Approximately 150 internal NARA users (i.e. staff members) across Archives I and the Presidential Library and Museum sites would use the ticketing system.

9. QUESTION: Who will require an individual login to our software?

ANSWER: 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.

10. QUESTION: What is the maximum number of users expected during busy hours?

ANSWER: During busy hours, NARA anticipates approximately 58 concurrent NARA users.

11. QUESTION: Select-your-own-seat maps allow your guests to choose reserved seats for performances, lectures, or other seated events…How many select-your-own-seat maps do you require across all organizations that hope to use our software?

ANSWER: NARA does not expect to use the select-your-own-seat functionality.

12. QUESTION: How many access control devices will be needed to scan tickets/member cards across all organizations that hope to use our software?

ANSWER: Currently, NARA anticipates approximately 24 access control devices will be needed across NARA locations.

13. QUESTION: Will you import or migrate any data sources besides ACME and records from past reservations on Recreation.gov to our software?

ANSWER: NARA does not anticipate the need to migrate/import any data from any sources including ACME and Recreation.gov.

14. QUESTION: How customizable do the ticketing interfaces need to be for different user roles (e.g., administrators, staff, visitors)?

ANSWER: For its different user roles, NARA expects minimal customization will be required for its ticketing interfaces. Reference PWS paragraphs 5.1.1, 5.4.3, and 5.1.2. However ,the ticketing system needs to match each respective website’s look and feel.

15. QUESTION: Are there any unique user experience requirements for different types of tickets (e.g., group reservations, special events)?

ANSWER: Yes. The system shall provide functionality that enables dedicated reservation microsites for special events. Additionally, the system shall enable users to reserve a Rotunda time and tours for individual, family, and group reservations.

16. QUESTION: What specific functionalities do you expect from the mobile application and onsite kiosks?

ANSWER: Reference PWS paragraph 2.5 for kiosk functionality requirements. NARA does not anticipate requiring the vendor to build a mobile application. The PWS requirements for mobile applications will be updated accordingly in the solicitation.

17. QUESTION: What are the key performance indicators (KPIs) you track, and how frequently are reports generated?

ANSWER: The KPIs NARA currently track include daily sales and attendance as well as monthly uptime of the ticketing system.

18. QUESTION: What other software tools and systems need to integrate with the new ticketing system?

ANSWER: NARA does not anticipate the need for the new ticketing system to integrate with any other software tools and systems from those referenced in the draft PWS and identified in the answer to Question 3.

19. QUESTION: Reference 4.6.1.4-Interfaces with internal and external systems. Can NARA provide details in terms of what and how many internal and external systems need to be interfaced with?

ANSWER: This is referring to internal and external systems defined throughout the existing Draft PWS and identified in the answer to Question 3.

20. QUESTION: Reference 4.6.1.6 Data export (and import if relevant) mechanisms, API, or SOP as appropriate. Can NARA provide more details on what data needs to be exported and to what systems?

ANSWER: Reference PWS paragraph 5.7 for data export requirements.

21. QUESTION: In addition to interfacing to Microsoft Dynamics Great Plains, are there other key interfaces/integrations that need to be enabled?

ANSWER: There are no other major interfaces/integrations. Also reference the answer to Question #3.

22. QUESITON: Best practices lend towards a proven integration platform as a service (iPaaS) solution to enable secure and scalable interfaces/integrations. Does NARA currently have an iPaaS solution?

ANSWER: No.

23. QUESTION: What was the primary limitation(s) of the current ACME system that influenced NARA to open an RFx process?

ANSWER: NARA respectfully declines to address this question.

24. QUESITON: Can NARA provide more detail on usage statistics such as number of events, number of tickets, etc. in place at PL locations ?

ANSWER: NARA anticipates providing historical user data statistics in the solicitation.

25. QUESTION: Can NARA provide information regarding current fees and pricing models related to the services provided at PL ?

ANSWER: Fees are posted on each library's web site. Visitors under a certain age have free admission, as well as students at some locations. Regular admissions vary depending on the group - adult, senior, military, etc. Currently, admission prices range from $3 to $15 per visitor.

26. QUESTION: Does NARA have a preferred pricing model for the future system?

ANSWER: NARA is open to considering all pricing models and encourages interested vendors to provide any recommendations on the most suitable pricing model for the enterprise ticketing system.