This article describes a variation of the original "Entrance Flow Management" sample experience. The main difference is that in this experience, Nexmosphere sensors are used to record visitor movement in and out of a facility, whereas in the original experience, hand-held counters or a mobile-accessible webpage were used.
In addition, this experience assumes only a single Entrance and thus does not accommodate additional displays as was possible with the original Entrance Flow Management experience.
The "Entrance Flow Management" experience illustrates how Intuiface can be used to track and communicate the number of people in a location and whether additional people may enter based on the maximum capacity. Although it can be used as-is, we encourage users to treat it as a starting point for creating their own custom solution.
To access the experience for editing, download it from the Marketplace using the like-named tab in Composer's Experiences panel. Alternatively, you can download the experience from its Marketplace webpage.
How it works
As indicated above, most of this experience is identical to the original described here. The difference concerns the counting approach. Rather than the webpage/physical clicker approach in the original experience, here we use two different Nexmosphere sensors (aka "elements"): Presence and Push Button.
Human-assisted counting can be replaced with an automated approach, such as computer vision-enabled or sensor-based entry/exit counts, as long as those counts can be transmitted to Intuiface via local network triggers, web triggers, a Web API, or a custom interface asset. Below are a few examples that can easily be integrated within this reference design:
The main requirement for automated counting in a physical location is to have separate entrance and exit doors, limiting entry to one person at a time, and preventing direct sunlight exposure.
Under these conditions, sensors like the Nexmosphere Presence sensor can be used out of the box with Intuiface.
With this same Experience, instead of taking an automated approach with the Presence sensor, you can choose to have a staff member keeping track of visits using Nexmosphere Push Buttons.
This experience has an interactive "Settings" scene. With this scene, you can change the maximum facility capacity, specify whether you'll be working with Presence Sensors or Push Buttons, and provide the appropriate configuration values in each case.
To access the "Settings" scene when the experience running, use one of two methods.
- click 's' on a physical keyboard attached to the device running Composer/Player. or
- double-tap the white rectangle at the top of the messaging scene
Here is what the Settings scene looks like:
For the details about sensor configuration settings, refer to the Nexmosphere documentation.
If you plan to run this experience on a Brightsign Player, here are two versions of the autorun.brs file that you should use.
- autorun_settings.brs Use this to run in portrait mode with a physical keyboard and a mouse cursor. The keyboard and cursor enable you to work with the Setting scene. Be sure to rename this file to autorun.brs.
- autorun_production.brs Use to run in portrait mode. The assumption here is the Setting scene will never be used so there is no need to accommodate a keyboard or mouse. Be sure to rename this file to autorun.brs
For more details about Intuiface Player on BrightSign, refer this section of our Help Center.
This "Entrance Flow Management" sample uses the Data Tracking Interface Asset to log user actions for analytics. With the collected data you can create a set of charts enabling you to answer any or all of the following questions:
- Capacity percent per hour in a day
- Average number of customer in-store per hour in a day
- Total number of customers in-store
- Average wait time (single value)
- Average occupancy per hour in a day