Library of Congress RFI - Electronic Visitor Counting System.pdf

REQUEST FOR INFORMATION

LIBRARY OF CONGRESS

ELECTRONIC VISITOR COUNTING AND ANALYTICS SYSTEM

1.0 Introduction

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes – it does not constitute a request for proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the U.S.

Government to contract for any supply or service whatsoever. Further, the Library of Congress (“The Library”) is not at this time seeking proposals and will not accept unsolicited proposals. Respondents are advised that the Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense.

Not responding to this RFI does not preclude participation in any future RFP, if any is issued.

2.0 Background

The Library’s existing electronic people counting camera system is antiquated and at the end of life. The Library is looking for commercial off-the-shelf (COTS) solutions to replace the existing system with a new system that may potentially be expanded in future years with additional sensors in additional locations. Through this RFI, the Library intends to explore the capabilities of modern visitor counting, tracking and analytics systems on its Capitol Hill campus in Washington, D.C.

The Library of Congress occupies three buildings on Capitol Hill. The Thomas Jefferson Building (1897) is the original Library of Congress building. The John Adams Building was built in 1938. The James Madison Memorial Building was completed in 1981.

Diverse audiences from around the world make the Library their destination for a variety of reasons. In order to deepen the Center for Learning, Literacy and Engagement’s (CLLE) and the Library’s understanding of these visitors and their interests, staff need to gather and evaluate visitor data and traffic flows at entrances, exits, and throughout exhibition galleries and other discrete spaces.

Data reports from new electronic equipment that counts people as they pass through various locations will provide ways for the Library to analyze information that is essential for assigning staff resources, adjusting hours of operation, and strengthening our visitor service capabilities. Moreover, the data collected will permit the Library to develop an audience-centric strategy for engaging with visitors and fostering lifelong connections to the Library. Finally, an electronic system will help the Library control capacity within spaces to enable visitors to maintain physical distancing given new pandemic guidelines.

The integration of people counting/traffic flow devices with visitor analytics software not only will allow the Library to track how many people visit and to understand which areas (see below) are most popular and control overcrowding, but it will also provide CLLE with the means to understand visitor behavior in real time, rather than requiring hours of preparation and manual data entry before being able to analyze it.

Entrances, exits, and gallery locations are on three floors of the Thomas Jefferson Building (see maps and floorplans at https://www.loc.gov/visit/maps-and-floor-plans). In addition to 3 entrances and 2 exits, specific interior spaces are:

Ground Floor

• Bob Hope Gallery

• Gershwin Room

• Graphic Arts Galleries

• Young Readers Center

First Floor

• Gutenberg Bible

• Mapping a New Nation Gallery

Second Floor

• Exploring the Early Americas

• North Exhibition Gallery

• Main Reading Room Visitor

Gallery

• South Exhibition Gallery

• Southwest Exhibition Gallery

• Thomas Jefferson's Library Gallery

3.0 Requested Information

The Library is seeking information about systems that meet the attached requirements.

(See LIBN_VCSAT_RFI_100720_Requirements.docx). In addition to mapping system features to the Library’s requirements, please include answers to the following questions in the response.

3.1 System

• Does the system serve any purpose other than to analyze footfall or occupancy?

• Describe platform, system architecture, and storage environment. (e.g., on premises, cloud-based, FedRAMP-authorized, etc.)

• Provide detailed hardware, software, network, and technical requirements for services and associated software for Windows and Mac environment. Describe associated local technical requirements including browser configurations and necessary plug-ins.

• Provide an overview of capabilities for administering the system that the Library can perform without vendor assistance.

• Detail storage capacity and increments for upgrades, if applicable.

https://www.loc.gov/visit/maps-and-floor-plans/ https://www.loc.gov/visit/maps-and-floor-plans/ https://www.loc.gov/visit/maps-and-floor-plans/thomas-jefferson-building/ground-floor/ https://www.loc.gov/visit/maps-and-floor-plans/thomas-jefferson-building/first-floor/ https://www.loc.gov/visit/maps-and-floor-plans/thomas-jefferson-building/second-floor/

3.2 Pricing

• Describe the pricing/fee structure for system hardware and software licensing

(both initial base cost and annual maintenance). Please include:

o Hardware cost o Software cost o Licensing cost o Installation and implementation labor cost o Training cost o Other maintenance support costs

• Describe all maintenance options/tiers and whether they vary in cost by time of day, response time, etc.

• What is the Lifecycle Replacement process for all the equipment required? How often would the Library need to upgrade the sensors and/or software and what are the likely costs?

3.3 Installation

• Describe the relative timeline or time required to initially implement the system.

• Describe what hardware, power outlets, and networking ports required to install the system.

• Describe the scalability of the system, including system limitations. In the event that the Library requires additional sensors in additional locations (e.g., multiple buildings), is there a maximum number of sensors or locations the system can support?

3.4 Support

• Describe continued system functionality and recovery in the event of loss of network and/or power connectivity.

• Describe procedures to be followed by customers when reporting issues with the system.

• Describe any warranty options available for the system

• Specify customer support hours and limitations on support outside of normal office hours.

• Describe procedure for handling software upgrades and updates.

• Describe the nature of services and associated software enhancements in development and scheduled for release in the next two years.

• Describe the notification process for scheduled maintenance and upgrade downtime.

• Describe which services and/or capabilities are not available during scheduled maintenance.

• Describe the system’s capabilities for remote support, indicating the required level of access to accounts and systems, and the location from which these activities would occur.

• Describe which services are not covered in the maintenance agreement which may be required in the course of normal operation.

• Describe system support for user accounts including managing user accounts and managing individual and group permissions.

• Describe the recovery procedure utilized in case of data loss or loss of content.

3.5 Training

• Describe training offerings for initial installation and for subsequent training.

• Describe training support for major software upgrades.

3.6 Security

• Describe the operational monitoring of the system.

• Describe security features for the solution, including compatibility for single sign-on logins.

• Is the data collected by the system anonymous or are users able to personally identify occupants by reviewing collected information (e.g., a person's facial features)?

o If the latter, is this personal data processed and stored, either locally or remotely in the cloud?

3.7 Miscellaneous

• Does the system have the capability to take temperatures of visitors and provide an alert to staff or visitor that a temperature above 100.4 degrees F has been detected?

• Provide a list of major clients, preferably cultural and historic institutions with visitor profiles similar to the Library (e.g., ~1.6 million walk in visitors annually visit exhibitions and view the historic building)

4.0 Other Requested Information

1. DUNS

2. Name (a specific contact person)

3. Address

4. Phone (main and cell)

5. Email (a personal email associated with the firm, not, for example, info@...)

5.0 Questions

Questions regarding this announcement shall be submitted in writing by e-mail to the Contracting Officer, Jennifer Zwahlen at jzwa@loc.gov, with a copy to Mojisola Adejuwon at moad@loc.gov. Verbal questions will NOT be accepted. The Government does not guarantee that questions received after October 27, 2020, will be answered.

mailto:jzwa@loc.gov

6.0 Responses

RFI responses are due no later than November 10, 2020, 12:00 Noon EST. Submit responses via email to Jennifer Zwahlen at jzwa@loc.gov, with a copy to Moji Adejuwon at moad@loc.gov. Responses are limited to 25 pages, including attachments.

The response should include “Electronic Visitor Counting and Analytics System” in the subject line. The maximum size of files allowed to come through the Library’s email system is 20MB. If needed, you may send more than one email, ensuring that each is clearly identified. The response should contain proprietary information ONLY if this information is CLEARLY MARKED and segregated. All responses will become the property of the Library and will not be returned. To aid the Library, please crosswalk the response to the numbering system used above in Section 3, Requested Information (3.1 – 3.7). Any supplemental information beyond the Requested Information identified above may be provided as an attachment to the RFI response.