HME ZOOM Nitro Thru Timer User Guide

FOR HME ZOOM Nitro ® TIMER SOFTWARE
IMPORTANT — READ CAREFULLY:
This HME End-User License Agreement (“EULA”) is a legal agreement between you (either an individual or a single entity) and HM Electronics, Inc. (“HME”). The SOFTWARE is licensed, not sold. All rights reserved.
This EULA is valid and grants the end-user rights ONLY if the SOFTWARE is genuine.
IF YOU DO NOT AGREE TO THIS END-USER LICENSE AGREEMENT (“EULA”), DO NOT USE THE DEVICE. INSTEAD, PROMPTLY CONTACT HM ELECTRONICS, INC. (“HME”) FOR INSTRUCTIONS ON RETURNS OF THE UNUSED DEVICE(S) FOR A REFUND.
ANY USE OF THE SOFTWARE, INCLUDING BUT NOT LIMITED TO USE OF THE DEVICE, WILL CONSTITUTE YOUR AGREEMENT TO THIS EULA (OR RATIFICATION OF ANY PREVIOUS CONSENT).
GRANT OF SOFTWARE LICENSE. This EULA grants you the following license:

You may use the SOFTWARE only on the DEVICE.
RESTRICTED FUNCTIONALITY. You are licensed to use the SOFTWARE to provide only the limited functionality (specific tasks or processes) for which the DEVICE has been designed and marketed by HME. This license specifically prohibits any other use of the SOFTWARE programs or functions, or inclusion of additional software programs or functions that do not directly support the limited functionality on the DEVICE.
SOFTWARE AS A COMPONENT OF THE DEVICE – TRANSFER. This license may not be shared, transferred to or used concurrently on different computers. The SOFTWARE is licensed with the DEVICE as a single integrated product and may only be used with the DEVICE. If the SOFTWARE is not accompanied by a DEVICE, you may not use the SOFTWARE. You may permanently transfer all of your rights under this EULA only as part of a permanent sale or transfer of the DEVICE, provided you retain no copies of the SOFTWARE.
If the SOFTWARE is an upgrade, any transfer must also include all prior versions of the SOFTWARE. The transfer may not be an indirect transfer, such as a consignment. Prior to the transfer, the end user receiving the SOFTWARE
must agree to all the EULA terms.
PRODUCT SUPPORT. For product support, please refer to HME support number provided in the documentation for the DEVICE. Should you have any questions concerning this EULA, or if you desire to contact HME for any reason, please contact us: HM Electronics, Inc., 2848 Whiptail Loop, Carlsbad, California, 92010 U.S.A. Web: www.hme.com. Email: support@hme.com. Phone: 1-800-848-4468.
• RESTRICTED USE. The SOFTWARE is not designed or intended for use or resale in hazardous environments requiring failsafe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, or other devices or systems in which a malfunction of the SOFTWARE would result in foreseeable risk of injury or death to the operator of the device or system, or to others.
NOT FAULT TOLERANT. The SOFTWARE is not fault tolerant. HME has conducted sufficient testing to determine that the SOFTWARE is suitable for use.
NO RENTAL/COMMERCIAL HOSTING. You may not rent, lease, lend, or provide commercial hosting services with the SOFTWARE to others.
SEPARATION OF COMPONENTS. The SOFTWARE is licensed as a single product. Its component parts may not be separated for use on more than one device computer.
LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION, AND DISASSEMBLY. You may not reverse engineer, decompile, or disassemble the SOFTWARE, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.
TRADEMARKS. This EULA does not grant you any rights in connection with any trademarks or service marks of HME.
WEB SERVER APPLICATION FEATURES. The SOFTWARE provides technologies that support web page browsing for data access and reporting from locations remote to the DEVICE.
COPYRIGHT. All title and copyrights in and to the SOFTWARE (including but not limited to its code, appearance, structure, organization along with any documents, forms, text, and images incorporated into the SOFTWARE), the accompanying printed materials, and any copies of the SOFTWARE are owned by HME or its suppliers. All title and intellectual property rights in and to the content that may be accessed through use of the SOFTWARE are the property of the respective content owner and may be protected by applicable copyright or other intellectual property laws and treaties. This AGREEMENT grants you no rights to use such content.
TERMINATION. Without prejudice to any other rights, HME may terminate this EULA if you fail to comply with the terms and conditions of this EULA. In such event, you must destroy all copies of the SOFTWARE and all of its component parts.
EXPORT RESTRICTIONS. You acknowledge that the SOFTWARE is subject to U.S. and European Union export jurisdiction. You agree to comply with all applicable international and national laws that apply to the SOFTWARE, including U.S. Export Administration Regulations, as well as end-user, end-use and destination restrictions issued by U.S. and other governments.
NO LEGAL ADVICE. You agree and acknowledge that HME is not engaged in rendering legal, accounting, or other professional advice. If legal advice or other expert assistance is required, the services of a competent professional person should be sought. Any sample documents included with the SOFTWARE are for illustration only and should not be used as the basis for any transaction or advice.

GOVERNING LAW
(a) If you acquired this SOFTWARE in the United States, this EULA is governed by the laws of the State of California.
(b) If you acquired this SOFTWARE in Canada, unless expressly prohibited by local law, this EULA is governed by the laws in force in the Province of Ontario, Canada; and, in respect of any dispute which may arise hereunder, you consent to the jurisdiction of the federal and provincial courts sitting in Toronto, Ontario. If this SOFTWARE was acquired outside the United States, then local law may apply.
LIMITED WARRANTY
(a) LIMITED WARRANTY FOR SOFTWARES ACQUIRED IN THE U.S. AND CANADA. HME warrants that (a) the SOFTWARE will perform substantially in accordance with the accompanying written materials for a period of ninety (90) days from the date of receipt, and (b) any Support Services provided by HME shall be substantially as described in applicable written materials provided to you by HME, and HME support engineers will make commercially reasonable efforts to solve any problem issues. Some states and jurisdictions do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you. To the extent allowed by applicable law and not disclaimed in this Agreement, implied warranties on the SOFTWARE, if any, are limited to ninety (90) days.
(c) CUSTOMER REMEDIES. HME’s and its suppliers’ entire liability and your exclusive remedy shall be, at HME’s option, either (a) return of the price paid, if any, or (b) repair or replacement of the SOFTWARE that does not meet HME’s Limited Warranty and which is returned to HME with a copy of your receipt. This Limited Warranty is void if failure of the SOFTWARE has resulted from accident, abuse, or misapplication. Any replacement SOFTWARE will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer. Outside the United States, neither these remedies nor any product support services offered by HME are available without proof of purchase from an authorized international source. (d) NO OTHER WARRANTIES. THE LIMITED WARRANTY ABOVE IS EXCLUSIVE AND IN LIEU OF ALL OTHER CONDITIONSAND WARRANTIES FOR THE SOFTWARE AND DOCUMENTATION. HME AND ITS SUPPLIERS MAKE NO OTHER CONDITIONS OR WARRANTIES, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, AND EXPRESSLY DISCLAIM ALL OTHER CONDITIONS AND WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED CONDITIONS OR IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT FOR THE SOFTWARE AND DOCUMENTATION, TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW.
(e) NO LIABILITY FOR CERTAIN DAMAGES. EXCEPT AS PROHIBITED BY LAW, HME AND HME’S SOFTWARE SUPPLIERS SHALL HAVE NO LIABILITY FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL OR INCIDENTAL DAMAGES ARISING FROM OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE SOFTWARE. THIS LIMITATION SHALL APPLY EVEN IF ANY REMEDY FAILS OF ITS ESSENTIAL PURPOSE. IN NO EVENT SHALL HME’S OR HME’S SOFTWARE SUPPLIERS’ LIABILITY EXCEED THE LICENSE FEE PAID BY YOU. THIS LIMITATION OF LIABILITY AND RISKS IS REFLECTED IN THE PRICE OF THE SOFTWARE LICENSE.
U.S. GOVERNMENT RESTRICTED RIGHTS. The SOFTWARE, including accompanying documentation, is deemed to be “commercial computer software” and “commercial computer software documentation”, respectively, pursuant to DFAR Section 227.7202 and FAR Section 12.212, as applicable. Any use, modification, reproduction, release, performance, display or disclosure of the software and accompanying documentation by the U.S. Government shall be governed solely by the terms of this Agreement and shall be prohibited except to the extent expressly permitted by the terms of this Agreement. You must affix the following legend to each copy of the Software:
Use, duplication, reproduction, or transfer of this commercial Software and accompanying documentation is restricted in accordance with FAR 12.212 and DFARS 227.7202 and by a license agreement.
Contact HM Electronics, Inc., 2848
Whiptail Loop, Carlsbad, California, 92010 U.S.A. Web: www.hme.com. Email: support@hme.com.
Phone: 1-800-848-4468.
HME DISCLAIMS ANY REPRESENTATION OR WARRANTY MADE BY ANY DISTRIBUTOR, RESELLER OR DEALER TO YOU WHETHER EXPRESSED OR IMPLIED.

ZOOM Nitro Overview

Congratulations on the purchase of your state-of-the-art ZOOM Nitro® system. This system will help you optimize the efficiency of your store by providing you with a full range of customizable analytics. The ZOOM Nitro system measures customer vehicle events for comparison to your service time goals at up to eight detection points in a drive-thru lane or other locations throughout your premises. It collects detection data, organizes it, and displays it in a clear, easy-to-read visual format on the “Dashboard” (A monitor display of drive-thru and event data). The Dashboard includes total and average event times at any time through an animated display of actual vehicles in the drive-thru lane or other designated locations.
Equipment
Your basic system includes:

Detectors (not shown): These detectors are installed in strategic out-of-sight locations throughout the premises. They are used to detect the presence of vehicles in areas such as drive-thru lanes or reserved parking spaces.
Timer Signal Processor (TSP): This device receives and sorts lane event data from the peripheral detectors, and sends it to the Control Unit for processing. This device is abbreviated throughout this guide as TSP. Fig. 1.1 shows two models TSP60 (front) and TSP50 (rear).
Control Unit (CU): This device receives lane event data from the TSP, processes it, and displays the information in real-time in a visual format on the system monitor. It stores your settings and manages a database of drive-thru activity history that it uses to generate scheduled and on-demand reports. This device is abbreviated throughout this guide as CU. (Fig. 1.2.)
Monitor: This is the primary drive-thru data display for your system. It displays lane event data from the CU. You can customize the layout of the display. The main display on the monitor is known as the “Dashboard.” Other displays on the monitor are available for viewing reports, editing the ZOOM Nitro settings, and performing diagnostics. Your ZOOM Nitro system may have one or more monitors. (Fig. 1.3.)
Back-Office PC (not included and not shown): If your ZOOM Nitro system has been configured to work with your network, all the information displayed on your monitor can also be accessed on your back-office PC. Also, you can use this PC to make changes to your system and print reports.

Drive-Thru Layout
The most common Lane configurations are:

Single Lane type: one entry point detector and one exit point detector.
Y Lane type: two entry point detectors and one exit point detector.
Dual Lane type: two entry point detectors and two exit point detectors.
Tandem Lane type: single entry point with two menu point detectors, one in front of the other, a single exit point detector.
Mobile Lane type: two entry point detectors and one exit point detector, where the designated “mobile” lane will highlight all cars detected by placing a neon blue border around the order/ time label attached to the car.
Mobile Order/Wait Areas: vehicle detection is off to the side of a lane, or in a reserved parking spot designated by the restaurant/store. Fig. 1.4 shows two Wait Areas and two Mobile Order spots.

Figures 1.4, 1.5, 1.6, and 1.7 illustrate possible examples of typical drive-thru layouts. Detection points (indicated by the circular yellow markers) can be installed at various strategic locations. You can label each detection point on your Dashboard. Commonly used examples are: Arrival, Greet, Menu, Order, Cashier, Pay, Present, Service, Mobile Order, Wait Area.

NOTE: In a Tandem Lane configuration, Menu/Order Point 1 is the second detection point from the drive-thru lane entrance, i.e., Menu/Order Point 2 is the first detection point the vehicle arrives at when entering the drive-thru lane. These Menu/Order Points are labeled as such because when a vehicle enters an empty drive-thru lane, it is prompted to pull forward to Menu/Order Point 1 so that Menu/Order Point 2 is now vacant and able to receive a second vehicle.
Overview of Typical Events in a Drive-thru Lane
Figure 1.8 is an example of a Single Lane type configuration with four zones (detection points).

The Dashboard
The ZOOM Nitro system installation is initially configured to your specifications by the installer. Fig.
1.9 is an example of the default Dashboard screen. If you wish to customize your system further or make changes to your current settings, you can connect a mouse to a USB port on the CU (this enables you to access the menu on your Dashboard monitor). Or, if your system is connected to the same network as your back-office PC, you can use the back-office PC to make changes.

Note: The screenshots used in this guide are only for illustrative purposes. The data and values displayed are simulated and do not reflect actual drive-thru data from a real store.
Click on the (menu) icon in the upper left corner of the Dashboard screen. The SECURITY screen opens, select User Type and log in to access the options displayed in the sidebar menu (see Fig. 1.10). Permission levels (determined by the User Type selected) restrict access to specific menu options. Each menu option is assigned a chapter in this guide, as shown here.

Making changes to ZOOM Nitro screens
To return to your main Dashboard at any time, click on the (GO BACK TO DASHBOARD) icon in the upper left corner of the screen (see Fig. 1.10).
Most screens have active areas which are editable; these may include the following:
Direct Access Fields: These are fields you can type directly into. When you click the cursor or tap in this field, a pop-up keyboard opens (see Fig. 1.11). This allows you to enter information using a mouse (without the need for a physical keyboard).

Time/Value Fields: Some active areas, such as time fields, are edited by clicking on the field. When you click the cursor or tap in this field, a popup keypad opens (see Fig. 1.12). Use the “backspace” key to clear the field, the number keys to enter a time value, and the colon key to separate hours and minutes. Click “Copy to All” to apply this value to all active fields in the column. A “Warning” dialog will prompt you to Cancel or Confirm. Click “Confirm” to apply.

ON/OFF Switches: Click on the OFF/ON switch to turn an option ON (if its current status is off) or OFF (if its current status is on). Some fields are invisible in the OFF position but become visible when turned ON (see OPEN TIME and CLOSE TIME columns in Fig. 1.13).

Drop-down Lists: The down arrow in a field indicates there are more options available to choose from. Click in the field or on the arrow to open the drop-down list and select your choice.
Add and Remove Icons: Some active screens have an Add and a Remove icon located next to a table. Clicking on the Add icon (see Fig. 1.14) adds another row to the bottom of the current table. If you want to delete a row, select the row and the Remove icon will appear; click Remove to delete the row. In Fig. 1.15, shift 2 is selected (the circle next to the shift number is checked). Clicking
the Remove icon deletes the selected row.

Some features need to be enabled first to activate. For example indicates that DHCP (a “NETWORK“ settings feature) is enabled. Clicking on this switch again will disable it. Some features are enabled by default or vice versa.
Save and Cancel: Most screens have button located at the bottom of the screen (this may be hidden from view, so you may need to scroll down to the end of the screen to access).
Any changes made must be saved to take effect. New settings are lost and default to the previous state if not saved.
Clicking “Cancel” also returns settings to the previous state if not yet saved.
If you exit a screen but forget to save your changes, a “Warning” prompt appears. This prompt asks you: “Are you sure you want to leave? You will lose changes” Click the button to return to the screen and save your changes or to leave the screen without saving the changes.
NOTE: The following chapters assume that the user now knows that any changes made to a screen must be saved first to take effect. Therefore, to keep our guides lean, instructions prompting the user to save changes will not be repeated hereafter.
Required Fields: Certain fields are mandatory and cannot be skipped. The system will alert you if a field cannot be left blank (see Fig. 1.16). In this example, the field needs to be populated with an option from the drop-down list before proceeding.

+ and – signs: When located next to a field indicates that this section can be expanded or collapsed.
Filter operators <, >, and =: When used with a value field, these indicate less than, greater than, or equal to the value selected, respectively.
Permissions
Different permission levels can be assigned to personnel who use this system. While this guide provides an overview of all features, some features may not be accessible to the user due to permission level controls (see “Chapter 8 – Security” on page 59).
Features only available to installers, or installers and managers, are noted at the beginning of the chapter.

Getting Started

The main Dashboard is the default screen displayed on the monitor (Fig. 2.1). The Dashboard shows real-time lane events for each vehicle in the drive-thru lane. The Dashboard consists of a frame with one to six user-defined Data Sections that display various combinations of measured event data. Fig. 2.1 shows a Single Lane drive-thru setup, with six real-time Data Sections, including a Pull Forward and Mobile Pickup section. The event information displayed is refreshed every second.

To customize and configure your Dashboard, click on the (menu) icon in the upper left corner of the screen. The SECURITY (Login) screen appears (see Fig.1.9). Log in by selecting your assigned User Type and password. This opens the Dashboard Settings screen. The default language is English; to switch to French, click on the Canadian flag icon at the top of the screen (see Fig. 2.2).

Dashboard Settings

Dashboard Layout

What is this screen for? It allows you to edit your main Dashboard screen. Despite the different background color, this screen reflects what is displayed on the main Dashboard.
Why is it needed? You may wish to configure and customize the look and feel of your Dashboard. This includes choosing what measured events you would like to display on your Dashboard. Click on any Data Section to open it for editing. The editable fields for the Data Section are displayed on the right side of the screen. For example, the Lane graphic in Fig. 3.1 was clicked so the Lane Settings fields on the right are available for editing.
Screen details explained: Fig. 3.1 shows a Single Lane layout, Fig. 3.2 shows how a typical Y Lane layout is displayed, while Fig. 3.3 shows what a Dual Lane layout looks like.

NOTE: For Dual Lane layouts, the top lane is always designated as Lane 1, while the bottom lane is Lane 2.
To adjust the layout of the Dashboard screen, click on the icon found in the upper portion of the screen or the adjacent down arrow icon next to it (see Fig. 3.1).
This opens the Dashboard Template menu, which shows various designs that allows you to customize your Dashboard layout (see Fig. 3.4). Click on any layout choice to select that screen.

Checking the “ DO NOT SHOW LANE” box (see Fig. 3.4) removes the Lane, Pull Forward, and Mobile Pickup graphics from the screen. By removing the lane, you will increase the size of the Data Sections on your Dashboard layout. If you wish to redisplay the Lane, Pull Forward, and Mobile Pickup graphics again, click on the “More” button that is now beneath the Data Sections, or click on the Dashboard Template again and uncheck the “ DO NOT SHOW LANE” box.
Some Dashboard Template layouts have a small asterisk next to them, as shown in Fig. 3.5.This indicates that these layouts support a Statistical Summary section (the six-section layout in Fig. 3.5 does not). The Data Section must be large enough to support Statistical Summary data; therefore, only the large rectangular section (Section 1) in Fig. 3.6 can accommodate a Statistical Summary. Click the Data Section to open Section 1 for editing. Then, in the MEASURE field choose “Statistical Summary” from the drop-down list (this option will not appear if other sections are selected because they can’t display this data). You must then enable at least one statistic from the list for the Data Section to populate (see Fig. 3.6).
NOTE: If any changes are made to the Car Detection Settings (such as display name changes, lane layout, adding more detectors, etc.), the Statistical Summary must be disabled and then re-enabled to see the newly added detector option within the settings. Also, if the store is configured as a Dual Lane drive-thru and Car Count is a metric selected for Statistical Summary, the Car Count will display the combined total of Lane 1 and Lane 2 by default.

When the Daypart Bottleneck Ticker option is enabled, a scrolling ticker will appear at the bottom of the Dashboard. Fig. 3.7 shows how it appears in Dashboard Settings and on the Dashboard. The scrolling ticker displays current Daypart information, where the bottleneck occurred for the previous Dayparts, and the Daypart average time of the detection point where the bottleneck occurred.
NOTE: Dayparts must first be configured in STORE settings to enable this option.

With Nitro Video Detection Enabled
If using Nitro Video Detection (NVD) in a drive-thru lane environment, the Drive Offs option is available in Dashboard Settings. To use the Drive Offs feature, first enable it, as shown in Fig. 3.8.
NOTE: The Video Detection Processing Unit option must be enabled under DETECTOR>CAMERA
Footer Drive Off Counter: Enable this to see how many drive offs you have within a specific time period (half hour, hour, daypart, or day). These time periods are selected from the drop-down list of the DRIVE OFF COUNTER TIMER METRIC field. This counter appears below the lane and data section graphics as shown in Fig. 3.8.
Footer Drive Off Notification: Enable this feature if you would like to display real-time notifications of when a vehicle drives off.

The above information can also be displayed in a Data Section. Click on a Data Section (Section 3 is the example used in Fig. 3.9). From the drop-down list of the MEASURE field, select Drive Offs. Label this Data Section in the Title field, and then select the time period from the DRIVE OFF COUNTER TIMER METRIC field. See Fig. 3.9.

Advanced Settings: Click to expand. Here, you can set a range of drive offs expected and color-code this range from green to yellow to red. This allows for easy identification of relative drive offs based on expectations. Green drive offs might indicate less than expected, while red might indicate more than expected.

Danger Zone: This is a Region Of Interest (ROI), which includes the Pre-Menu Zone and is an area of the drive-thru lane where vehicles can still pull out and drive off before reaching the menu ordering point. When this feature is enabled (Fig. 3.11), the Danger Zone is displayed on the main Dashboard as a part of the drive-thru lane (Fig. 3.12).
Lane Settings
To edit what is displayed on your Dashboard, use the column of associated fields on the right. The Dashboard Settings screen defaults to “Lane Settings” when opened.

When “Individual Stall Title” is enabled, the first letter of the name applied to a detector is used along with a stall number (detector names are configured in the DISPLAY NAME fields of CAR DETECTION SETTINGS). For example, if an independent detector uses the display name “Mobile,” then M1 will become the label used for the first individual stall title when this option is enabled. These titles will appear on the Dashboard stall graphic as shown in Fig. 3.14 which in this example consists of two stalls labeled M1 and M2.

Menu Item	Description
	Pull-Forward: Click in this field to edit and give your wait area a descriptive name. This field is for pull-forward detectors.
	Mobile Pickup: Click in this field to edit and give your wait area a descriptive name. This field is for wait areas that are independent detectors (not part of lane events).
	DRIVER POSITION: The default Driver Position is on the Left Side (standard in the United States and other countries). Click on the down arrow and choose Right Side if you need to display it on the right side. Changing the Driver Position changes the orientation of the lane and wait area graphics accordingly.
	DAYPART/SHIFT OPTION: Different combinations of Daypart (DP), Shift, and Time can be selected here to be displayed at the top of your Dashboard screen (see Fig. 3.13).
	LEADERBOARD DISPLAY: Stores using a single monitor may wish to alternate between displaying the Dashboard and Leaderboard. By default, the Leaderboard and Dashboard will alternate. By clicking the toggle, you will disable the Leaderboard and only show the Dashboard. The Leaderboard option is only visible with a cloud connection. The following three fields are visible if the Leaderboard display is enabled.
	Dashboard Display Duration: This sets the length of time the Dashboard is displayed before alternating back to the Leaderboard.
	Leaderboard Display Duration: This sets the length of time the Leaderboard is displayed before alternating back to the Dashboard.
	ONLY SWITCH WHEN LANE IS EMPTY: “Yes” in this field means that the Leaderboard is displayed only when the lane is empty. “No” means the Leaderboard will alternate displays regardless of lane activity.

If you scroll to the bottom of Lane Settings, you will see Advanced Settings. Click to expand and see next section “Advanced Settings – Goals” on page 18
Advanced Settings – Goals

The Lane graphic shows the movement of customer vehicles through your drive-thru lane(s). Vehicles are color-coded based on performance against specific goals (Lane Total 1 for Lane Settings). The color of each animated car in the ane allows you to easily identify how your drive-thru lane is performing against these goals. These goals are user-defined under “STORE” (see “Speed Goals” on page 29). Up to four goals can be set for each event. These goals are labeled A, B, C, and D and assigned values. Values for each letter creates a range of targets for specific events to gauge performance against.
NOTE: Goals under Lane Settings apply only to Lane Total of vehicles in lane, whereas goals under Data Sections 1 through 6 are based on events at individual detection points/zones (unless one of these sections is also used to display the Lane Total value of the animated lane).

Menu Item	Description
	UNDER GOAL COLOR, Green: This color indicates you are exceeding your goals. For example, you are monitoring a detection point/zone labeled “Cashier” in the lane. If the goal selected is “A” (as in the next field of this example) and A has a value of 30 seconds assigned to it, an event happening under 30 seconds will have a green value.
	1ST COLOR GOAL: Selecting goal “A” here sets one end of an event range.
	BETWEEN GOAL COLOR, Yellow: This color indicates you are meeting your goals. When your event happens in between the two goals (A and B in this example), you are on target to meet your goals. For example, if A = 30 seconds and B = 60 seconds, any event happening within this range will yield a yellow value.
	2ND COLOR GOAL: Selecting goal “B” here sets the other end of an event range.
	OVER GOAL COLOR, Red: This color indicates you are not meeting your goals. Continuing our example, if A = 30 seconds, B = 60 seconds, any event taking longer than 60 seconds will yield a red value.

Data Sections – Example 1
Data Sections are Dashboard panes containing user-defined event data. Clicking on the upper left Data Section (Menu Time) opens a column of associated fields on the right (Section1), which allows you to edit what is displayed in the Data Section (see Fig. 3.17).

The editable field associated with each value in the Menu Time Data Section is shown in Fig. 3.18.
The Metric used in this example is Menu (the second field from the top under Section1 in Fig. 3.17); these events are defined under “Chapter 6 – Car Detection Settings” on page 40. The value at the center (0:28 in Fig. 3.18) is green because this event occurred in under 30 seconds, the lower time limit set by goal A (0:30 in Fig. 3.18). The hour average (0:38 in Fig. 3.18) is yellow because it is on target (the value is in the range between goal A and goal B). These goals were set under the Advanced Settings of Section1. Only one goal (A in this example) can be displayed in the Data Section.

Menu Item	Description
	This value is the large number displayed in the center of the Data Section (0:28 in Fig. 3.18). Click the down arrow on the right of the MEASURE field to expand the options menu. The drop-down list provides you with several choices. Other fields in this section change to match the choice selected.
	MEASURE – drop-down list: Time: This is the elapsed time for an event happening, such as a vehicle being detected at a detection point or the Lane Total for a Lane. % Goal: Shows the percentage of vehicles over/under the goal at the select- ed Event. Car Count: The total number of vehicles that have gone through the drive-thru lane and departed from the last detection point. If your store uses a Dual Lane layout, CAR COUNT will also offer you LANE SELECTION options. You can choose a car count for either lane or a combined count for both lanes.
Note: the above dropdown list does not show all options available. It serves only as an example for this field but is not repeated for each field. However, every entry in each drop-down list is defined in this table.	Cars in Lane: This is the total number of vehicles in the lane that have arrived at or passed the first detection point but have not yet departed the last detection point of the lane. If your store uses a Dual Lane layout, CARS IN LANE will also offer you LANE SELECTION options. You can choose cars in lane for either lane or a com- bined count for both lanes. Disastrous Orders: This is the number of vehicles or orders that have ex-ceeded the user-determined Disastrous Orders Goal. For example, if speed goal D has the longest time value of goals A, B, C, and D (where A = 30, B =60, C = 90, D = 120), then any vehicle or order exceeding 120 is considered a Disastrous Order. Drive Offs (if applicable): These are vehicles in the Danger Zone/Pre-menu Zone which drive off before ordering. See details on page 12, Fig. 3.9 and 3.10. This option is only available when using Nitro Video Detection.
	Average Time: The sum of the amount of time, for each vehicle departure within the user-selected periods, divided by the number of vehicle departures. Drive Thru-Put: Calculates the number of cars each hour the drive-thru can serve based on the slowest detection point average and the time remaining in the hour. Period Bottleneck: This shows the bottleneck event for the set time period (Half Hour, Hour, Daypart, Day). Current Bottleneck: This tells you what event/detection point is causing the current bottleneck. Based on the set number of vehicles in the Rolling Avg. settings. Leaderboard Ranking: This shows your store’s ranking based on the num- ber of stores it is monitored against. For example, a “1 of 5” ranking means you are currently in first place out of five stores monitored. Leaderboard List: This shows a list of all the stores monitored beginning with the top ranked store. In the Leaderboard Ranking example (1 of 5), your store will be the first line on the displayed list (see Fig. 3.19). Lead Car Order Summary: This gives you an overview of the order for the lead car in your drive-thru lane. NOTE: The Leaderboard feature is a subscription based option. To modify the Leaderboard ranking and period, sign in to your HME CLOUD account and use the portal to make any changes.
	MEASURE – drop-down list continued: Statistical Summary (if applicable): This shows the selected summary data for the current Hour, Daypart, and Day periods. This option is only available for specific section panes within select Dashboard Templates; see Dashboard Templates under “Dashboard Layout” on page 10 for more details.
	METRIC – drop-down list: Chose your metric to display from the drop-down list. These metrics are defined under the Car Detection Settings section (see Chapter 6 – Car Detection Settings) and user-defined under “DISPLAY NAME” of LANE DETECTORS and INDEPENDENT DETECTORS. Lane Total and Lane Total 2 are also included.
	TITLE Add your title to a Data Section. This title appears on the upper left corner of the Data Section. This is useful if you wish to display the same metric twice but with different data types or measured parameters displayed. Since the same metric label is used twice, you can assign each one a unique title to differentiate them. For example, if the metric you choose to use is labeled Menu 1, you might wish to display a time value in one Data Section and an average value on the other. To differentiate one from the other, you might call one “Menu 1 Time” and the other “Menu 1 Avg”.
	AVG PERIOD – drop-down list: Half hour: This is half of the clock hour, beginning on the half-hour mark. Half hour trailing: This is a continuous rolling half hour of the last 30 minutes trailing the current time and updates every minute. Hour: This is the clock hour and begins on the hour mark. Hour trailing: This is a continuous rolling hour of the last 60 minutes trailing the current time and updates every minute. Daypart: This is a day segment that is user-defined in Store Settings. Day: This is the current store day during hours of operation. OFF: Turns this field off so that it’s not visible in the Data Section.
	DISPLAY GOAL – drop-down list: Goal A, B, C, D: Select the goal* you wish to display in the Data Section. OFF: Turns this field off so that it’s not visible in the Data Section.
Advanced Setting	Clicking the + sign expands this setting and provides you with the same options covered under the Advanced Settings** of Lane Settings.

* Goals are user-defined under “STORE” (see “Speed Goals” on page 29).
** See Advanced Settings under “Lane Settings” on page 16.
Data Sections – Example 2
This Data Section (middle of bottom row) shows a Car Count. Clicking on it opens a column of associated fields on the right (Section5), which allows you to edit what is displayed (see Fig. 3.20). DAYPART – 1 BREAKFAST 1 06:00 09:00 08:50:48 NOVEMBER 4 MONDAY

The row of numbers at the bottom of the Data Section in Fig. 3.21 are as follows:
Prev: This is the result achieved for the previous hour (or whatever period is chosen in the PERIOD field). In this example, it is 5, and the value is red because it didn’t reach the lower limit set by goal B.
Best: This is the best result ever achieved for an hour (or whatever period is chosen in the PERIOD field). In this example, it is 37. Pace: Uses an algorithm to predict the number of transactions you are capable of making based on the current vehicle count for this time period, which may differ to the main value shown. In this example, based on the time left in this hour, Pace predicts that you may reach 27 transactions. Goal: This goal was established in the Car Count Goals section of STORE settings. Only goal A is displayed, even though B is also used to set the lower limit of the range.
In Fig.3.21, 21 is the current vehicle count number for this hour. Since this value is within the range set by goals A (30 vehicles) and B (20 vehicles), it is on target and, therefore, yellow. Since only one goal value can be displayed, goal B is not visible. Goal values are set in “Car Count Goals” on page 31 and then selected in the Advanced Settings of this section (Section5 in this example).
Data Sections – Example 3
This Data Section shows a Curbside-Only dashboard for stores that use reserved parking stalls for mobile orders or curbside pickup instead of a drive-thru lane. Fig. 3.22 shows a store with two stalls reserved for mobile orders.
NOTE: Video Detection is required for a Curbside-Only configuration.

NOTE: Each stall does not need to be configured individually. Once the Dashboard Settings are configured, those same settings are applied to all the active stalls (two in this example). The selected settings are displayed along the top, above the Data Sections as shown in the graphic below, while the actual values for each stall are displayed within each corresponding Data Section (e.g., 0.27 for Mobile 1, 0.04 for Mobile 2).

Menu Item	Description
	This value is the large number displayed in the center of the Data Section MEASURE – drop-down list: TIME, AVERAGE TIME. Time: This is the default option and is the elapsed time for an event happening, beginning when a vehicle is first detected at the stall. When TIME is the selected option, you can enable “Display Average” so that it also displays the AVERAGE TIME option in the Data Section as well, see Fig. 3.22. Average Time: This is the sum of the measured times for each vehicle with- in the user-selected period, divided by the number of vehicle departures.
	This option sets the period you wish to measure. PERIOD – drop-down list: Half-hour, Hour, Daypart, or Day. Daypart is a day segment that is user-defined in STORE settings.
	When Display Goal is enabled, you can select which Goal to display. In this example, it is “Goal A,” which has a value of 0:50 seconds (the value dis- played under “WITH GOAL OF” above the Data Sections in Fig. 3.22).
Advanced Settings	These settings allow you to choose your Goal range. See “Advanced Settings – Goals” on page 18 for more information.

Store

Only Installers and Managers can access and edit the features on this screen.
Details

What is this screen for? This screen allows you to enter store details such as Store Name, Store Number, Store Brand, and Store Address. The Store Number field can accept an alphanumeric entry.
Why is it needed? This information identifies your store, which may be one of several in a given area. Since this information is also stored in the cloud, it enables our technical support personnel to quickly locate and provide you with any requested help.
Example: You are one of five stores owned by the same franchise and located in the same city. You wish to modify or upgrade your system, so you contact us at HME technical support. We can remotely access this information from the cloud and promptly respond to your specific needs as we know who you are, your system specifications, and where you are.
Date/Time

What is this screen for? This Date/Time screen is used to set the local time and current date to match the local settings at your store’s location. These settings are generally completed during installation.
Why is it needed? Most features in this system operate on time-based events. Your daily work activities and monitored parameters such as dayparts and shifts are based on the system time set up here. This screen gives you flexibility as to how this time is configured and displayed.
Example: Fig. 4.2 shows the SYSTEM DATE and TIME. The TIMEZONE in this example is (UTC-08:00) Los Angeles. This would be the time zone chosen if your store is located in a city on the west coast of the United States (UTC-08:00 is Coordinated Universal Time with an offset of minus eight hours). Under CUSTOM TIME FORMAT, the “24 hour” option is selected, which will display times based on a 24hour clock. Select the “12 hour” option if you want AM and PM times. Under DISPLAY TIME FORMAT, the “Minutes: Seconds” option is selected, which will display timed events in minutes and seconds. Select “Seconds” if you want to display timed events in seconds only.
Hours

What is this screen for? This screen allows you to configure your store’s business hours and days.
Why is it needed? Your system only needs to be operational during business hours. Each day can
be configured separately if your business hours differ from one day to another. You can also turn days
on or off if you are closed on certain days.
Example: The store in Fig. 4.3 is open from 5:00 AM to 11:00 PM Monday to Friday, but 5:00 AM to
Midnight on Saturday and is closed on Sunday. To configure this schedule (24-hour clock used):

Click the OFF/ON ( ) switch to turn Sunday off since you are closed on that day. The OPEN TIME and CLOSE TIME fields disappear.
Move on to Monday; click on the time in the OPEN TIME column. This opens the time field. Enter 05:00, then click on the “Copy to All” button to populate all fields in the OPEN TIME column with this time.
Repeat step 2 for the CLOSE TIME column (setting close time to 23:00).
Go to Saturday and adjust the close time to 00:00 (midnight). Click the “Done” button to apply it only to that day.

TIP: If your store Open Time or Close Time is the same for every day of the week, change the first Open or Close Time on the list and then click on the button beneath the time field to populate every other day with this same time.

Dayparts/Shifts

What is this screen for? It allows you to partition your business day into manageable segments.
This screen is divided into two sections, Dayparts and Shifts.
Dayparts are parts of the day you can break into smaller segments to monitor. A daypart end time is not required because it is contiguous, so it automatically ends with the start time of the next daypart segment. The last daypart ends at the store close hour (store close time for a 24-hour store is the same time as its opening time).
Shifts are blocks of time normally attributed to employee work periods, such as morning shift, afternoon shift, and night shift. Unlike dayparts, shifts may overlap with other shifts or begin at a time later to the end of a previous shift; this is why they are assigned a start time and end time.
NOTE: While a shift period can overlap with another shift that began before it, it cannot begin earlier than the shift before it. Also, a start shift can begin at a time later than the store’s opening time but cannot begin before it. Similarly, an end shift can end before the close time of a store but cannot end after close time.
Why is it needed? Dayparts and Shifts enable you to monitor your store’s activity at different times of the day, which can fluctuate from being slow to being busy and vice versa. Monitoring these periods enables you to manage and maximize your store’s efficiency, resources, and output. You will be able to track daily trends, which will enable you to anticipate business activity fluctuation. By being proactive, you will be able to better meet and satisfy your customers’ demands.
Example: In Fig. 4.4 under DAYPARTS, there are six dayparts of various lengths (24-hour clock used). Daypart-2 is labeled “Breakfast 2”. It begins at 09:00 and ends at the beginning of Daypart-3 (i.e., Lunch 1 at noon). Dayparts can be equal periods, or they can also vary in duration. If your day is broken into many small dayparts, you may have to scroll down to see all the dayparts displayed. Fig. 4.4 also shows three 6-hour shift periods under SHIFTS. They begin with the Morning shift at 06:00 and end with the Evening shift, which runs from 18:00 to 00:00 (midnight). The system automatically assigns the sequential number to the DAYPARTS column and SHIFTS column as more dayparts or shifts are added. The START TIME/END TIME and NAME columns are user-defined parameters. To add a daypart or a shift period, click on the Add icon. A new row is added to the bottom of the table with generic labels or values. Click on a field to edit. To remove a daypart or a shift period, check the circle next to the sequential number in the DAYPARTS or SHIFTS column of the row you wish to delete. This causes the Remove icon to appear next to the Add icon. Click on it to delete the selected daypart.
Conditions: Daypart times cannot overlap, while shift times can overlap. Dayparts and Shifts cannot begin before opening time nor end after closing time (see note). Dayparts can be divided into a maximum of 23 segments. Shifts can be divided into a maximum of eight segments.
NOTE: If you have a Leaderboard subscription and you plan on using daypart time periods with your Leaderboard, Dayparts must first be configured here so that the Leaderboard has valid data to display.
Speed Goals

What is this screen for? Speed Goals allows you to set up time goals using adjustable thresholds.
Why is it needed? Setting goals is a great way to monitor and motivate performance for a specific daypart at any event location (detection point) or Lane Total. Goals are assigned letters, and user-defined values are assigned to these letters. Color-coded values are then displayed on your Dashboard to indicate performance levels against these goals.
The color codes are as follows: Green indicates exceeding goals, yellow is meeting a goal or within goal limits, while red indicates not meeting a goal.
Example: Fig. 4.5 shows days of the week followed by dayparts for that day. The table shows events with four different goal values assigned to each of four letters (A, B, C, & D). There are five events listed in the EVENT column for this table: Lane Total 1, 2, Menu, Cashier, Service (two lane total events plus three detection point events).
In this example, the current day of the week is Tuesday. The current daypart is 1 (Breakfast 1 06:00 – 09:00). The first event is Lane Total 1, while the first detection point event is “Menu.” Each event has four goals set (seconds/minutes), which can then be applied to the metric they are associated with. The resulting values are color-coded for easy identification of an event’s performance against these goals (see “Lane Settings” on page 16, and “Data Sections – Example 1” on page 19 for details).
Conditions: Minimum time goal = one second. Maximum time goal = 999 seconds (16 minutes and 39 seconds). Up to four goals can be set for any daypart event. Goal A must be less than or equal to Goal B, B less than or equal to C, C less than or equal to D. For example: if you set a value in Goal A and it is higher than B, it will force B to this same value (it will also force C and/or D to the same value if it is higher than these goals too). These goals must then be readjusted to create a valid range.
TIP: To apply the same event change across all dayparts of a day, all days of the week, or both, enable the “More Application Options” feature and select an option from the drop-down list. See the following explanation of options.

Fig. 4.6 shows the drop-down list of options available when More Application Options is enabled.
These options allow you to apply speed goal changes across multiple dayparts, days, or both, saving you from having to manually repeat the change for each targeted daypart or day. These options are as follows:
This Daypart for All Days: This option allows you to change speed goals for a daypart and apply them only to that same daypart across all active days of the week. For example, if your store operates every day of the week, and you wish to change your Lane Total Goal D to 05:30 but only for Daypart 1 (Fig. 4.6). This change will only be applied to Daypart 1 for all seven days (i.e., Dayparts 2 – 6 in this example will not be affected by the change).
All Dayparts for All Days: This option allows you to change speed goals for a daypart and apply them to all dayparts of all active days in your business week.
For example, if your store operates every day of the week, and each day is split into six dayparts. Your change will then be applied to all 42 dayparts in your business week (7 days x 6 dayparts).
All Dayparts for This Day: This option allows you to change speed goals for a daypart and apply them to all dayparts of that active day only.
For example, suppose your store’s day is divided into six dayparts (as it is in Fig. 4.5 and 4.6).
Then, you change your Lane Total Goal D to 05:30 for the current Daypart 1 (in Fig. 4.6). All Dayparts for that day only (i.e., Tuesday in this example) will have their Lane Total Goal D changed to 05:30; the other days will not be affected.
Car Count Goals

What is this screen for? It allows you to set up car count goals using adjustable thresholds.
Why is it needed? Setting goals are a great way to motivate and monitor performance. Goals are assigned letters, and user-defined values are assigned to these letters. These are then displayed as color-coded values when configured on your Dashboard. Color-coded values allow for easy identification of performance tracked against the goals set.
The color codes are as follows: Green indicates exceeding a goal, yellow is meeting a goal or within goal limits, while red indicates not meeting a goal.
Example: Fig. 4.7 shows days of the week and hours of the day (24-hour clock used, with only a partial table of hours visible). The table on the left is for AM, broken up into 12 one-hour segments; the table on the right is for PM, also broken up into 12 one-hour segments. Both tables show B as the initial goal target (lower value) with A being the preferred goal (higher value indicating greater business). Car count values on your Dashboard are red until goal B is reached. Then, once goal B is reached and exceeded, they become yellow indicating you are meeting your goal. The values between goals A and B remain yellow, and then if goal A is met or exceeded, the value turns green, indicating you are now exceeding your preferred goal.
In this example, the current day of the week is Monday. The hour beginning at 00:00 (first entry in table) has a desired goal of 30 vehicles for A and 20 for B. So, if the count is less than 20 vehicles for this hour, the value displayed is red, 20 to 29 vehicles yields a yellow value, while 30 vehicles or more yields a green value. See the example of “Car Count” (Fig. 3.8) in “Data Sections – Example 2” on page 22.
Conditions: Minimum vehicle count goal = one. Up to two goals can be set for each hour. Unlike speed goals, they do not apply to individual detector points. Goal A must be greater than or equal to goal B. If a lower value is applied to goal A than exists in goal B, then the value in goal B is forced to the same value of goal A. Goal B must then be readjusted to create a valid range.
TIP: To apply the same changes to this field for all active days in the week, click on the button.

NEXEO | HDX Audio Alerts

NOTE: Since these audio alerts are used across two systems, they must also be enabled on the NEXEO | HDX base station to be functional. When successfully connected, the Connection Status at the top of the screen will read “Connected.” If this is not the case, contact HME Technical Support at 1-800-848-4468 for assistance.
What is this screen for? If your store also uses a NEXEO | HDX™ Crew Communication Platform, this option allows you to set audible alerts for crew members using NEXEO | HDX headsets.
Why is it needed? These alerts inform crew members when a parameter or goal limit is reached. It also allows them to quickly respond to resolve an issue if necessary.
Lane Total Alert: Enable this and choose a goal from the drop-down list to receive an audible alert when a vehicle has exceeded the goal selected.
Pull-Forward Area Alerts: Enable this and select a location from the drop-down list to receive an audible alert when a pull-forward is detected. Also see Play Alert below.
Independent Detector Alerts: Enable this and select a location from the drop-down list to receive an audible alert when a vehicle is detected at an independent detector.
Play Alert: This drop-down list provides options for when the alert is played, immediately, or only when the goal threshold is exceeded (this prompts selecting a goal), or both events.

Network

Only Installers can access and edit the features on this screen.

Local Network

What is this screen for? This is where you configure your system when connecting to your local network. Your installer generally configures this screen during the initial installation and setup.
Why is it needed? If you wish to access and control your system from a back-office PC, you will first need to connect your system to the same local network used by your PC. This will allow your back-office PC to interface and communicate with your ZOOM Nitro system. You have a choice of automatic or manual IP configuration.
Control Unit Network:
: Dynamic Host Configuration Protocol allows a network administrator to supervise and distribute IP addresses from a central point. When the DHCP switch is enabled, the system automatically populates the required fields.
IP ADDRESS: Internet Protocol Address. A unique computer address that some electronic devices (such as computers or routers) use to identify and communicate with each other on a computer network.
SUBNET MASK: Splits the network into a series of subgroups or subnets to speed up the delivery of data by the routers.
GATEWAY: A device (usually a router) that connects one or more computers on a network to other networks.
DNS SERVER: Domain Name Server is a directory of domain names with translated Internet Protocol (IP) addresses.
WEB SERVER PORT: The network port used by ZOOM Nitro to connect to the TSP on the network.
MAC ADDRESS: This is the unique identifier for the ZOOM Nitro CU when connected to a network.
Network Time Protocol (NTP) Settings
NTP is a protocol used to synchronize computer clocks across multiple systems. It supports syn- chronization over local area networks and the internet.
NIT Enable: This switch enables/disables NTP settings. When enabled, four Time Server fields are visible with at least one field populated.
TIME SERVER: This is the server computer used to synchronize time.
NOTE: Timers must remain synchronized with each other so that reports from multiple locations can be easily correlated.
When NTP is enabled, the system does not allow the user to edit the date/time.
Conditions: The DHCP and NTP settings are enabled by default. Disabling DHCP requires manual input to populate the associated fields. The NTP Settings allow for up to four servers.
HME CLOUD

What is this screen for? It is used to connect your system to the HME CLOUD. Your installer generally configures this screen during the initial installation and setup.
Why is it needed? Having a cloud connection is useful for sending diagnostic reports, troubleshooting connection issues, and receiving additional support like software upgrades. Also, your records and data history are backed up and stored in the HME CLOUD.
Example: Fig 5.2 shows you have turned the HME CLOUD feature “ON.” The CONNECTION STATUS shows that you are connected to the cloud. The ACCOUNT EMAIL ADDRESS is populated when you are registered. To
change this email address, you must first unregister using the Unregister button. An email address only needs to be entered if you have an account set up. If not, leave blank, and click “Save” to connect.
The CONNECTION STATUS field will then indicate when you are connected. If your system does not connect, click the “Test Connection” button. This connection test will reveal the potential problem. Fig. 5.2 shows an example of what connections are checked when this connection test is performed. In this example, all the connection tests displayed beneath the button have passed.
Conditions: While you do not require a registered account to operate your system, HME does recommend it. A registered account provides access to a range of additional benefits and support.
You can record your account information/email address here for reference:
POS Settings

What is this screen for? It allows you to integrate your ZOOM Nitro timer with a POS system.
Why is it needed? Orders taken at the order point can be associated with the car at the order point and tracked through the lane. The crew can select to display this information on the Dashboard.
Example: An ACTIVATION CODE is required to activate this feature. Call the Technical Support number on this screen and provide them with the FEATURE CODE displayed to receive your activation code. Enter this activation code and click on the Activate button. A screen like the one in Fig. 5.4 will appear. GEOFENCE SETTINGS CONNECTED DEVICES

Once the POS activation is completed, the POS Settings must be configured.
The POS Interface enables or disables the use of POS mode:

Disabled: No POS options are available.
Enabled: POS options can be configured, and the POS data can be displayed on the Dash- board and in Raw Car Data Reports.
The Data IP Port is a configurable port that ZOOM Nitro listens for POS data on – this port is defined by the POS system, and ZOOM Nitro will only receive POS data sent to the specified port.

Conditions: POS integration only works with Single Lane and Y Lane configurations.
This is an optional feature that must be purchased. You must use the Feature Code under POS Activation, call HME Technical Support, and enter the Activation Code provided to activate this feature.
Only POS systems available in the drop-down list of POS Model can be integrated with ZOOM Nitro. This list includes, NewPOS, Oracle Simphony, Xpient, and NCR Radiant.
Dashboard options allows you to choose what information is displayed. The Car Information drop- down list, includes Time Only, Transaction # Only, Time & Transaction, or Time & Order.
Confusion can arise in the case of pullouts:

In the case of a pullout, before an order is tendered, the order number is moved to the next vehicle detected in the queue. All remaining vehicles are sequenced with respective order numbers.
In the case of an undetected pullout where the order taker cancels the order, then the timer must receive a “canceled order” event from the POS system and sequence the vehicles after deleting the order number and the vehicle associated with it.

Geofence Settings (not available for all stores)

NOTE:
Geofence Settings is an optional feature. If not displayed on your screen, it is not available for your store. A store must have an in-app ordering service with location intelligence to use this feature. Contact HME if you would like to know more about this feature.
What is this screen for? If your store uses a geofence for remote or mobile orders, you can configure options here.
Why is it needed? Once a geofence is enabled, you can choose what geofence options are displayed on the Dashboard. Pairing threshold times can also be adjusted here to compensate for latency variables unique to each store.
Geofence Interface Disabled/Enabled: Enable to turn this feature on. Geofence Dashboard Options: These appear in a dialog label next to the associated vehicle displayed on the Dashboard. A geofence label has a neon blue border around the label (see Fig.5.6) to distinguish it from a standard label that does not have this border.

Time: This is the time triggered by the vehicle’s arrival at the detection point. It is displayed next to the animated vehicle on the Dashboard.
Transaction: This is the transaction number associated with a customer’s order. It is displayed next to the animated vehicle on the Dashboard.
Time & Transaction: This is a combination of both time and transaction displayed next to the animated vehicle on the Dashboard.
Pre-Geofence Arrival Pairing Threshold (in sec): There is a latency period involved when using a geofence. Due to varying communication speeds between devices and networks, a geofence message may be sent to the device prior to the vehicle arriving in the geofence perimeter. This message will queue for 1-15 seconds (depending on setting) until the visitor arrives within the geofence perimeter to ensure the message is paired with the correct visitor. Post-Geofence Arrival Pairing Threshold (in sec): Due to varying communication speeds between devices, a geofence message may be sent to the device after the vehicle has arrived and departed from the geofence perimeter.
This will allow the transaction to be paired with the visitor 1-15 seconds (depending on setting) after the vehicle has departed the geofence perimeter.
Conditions: Pairing threshold time can be one to fifteen seconds long.
Connected Devices

What is this screen for? The Connected Devices screen displays all devices connected to the ZOOM Nitro system, which may now include newer technologies like Video Detection. Pertinent information such as MAC and IP addresses from Video Detection components can be viewed here.

Detectors

Only Installers and Managers can access and edit the features on this screen.
Camera

What is this screen for? The system supports two types of detector technology, TSP and Camera (Video Detection). TSP is the standard and most commonly used technology. Vehicle detection using a camera is a newer technology that allows vehicles to be identified and tracked through a drive-thru environment or designated stalls for mobile or curbside pickup. A store must meet a set of prerequisites to have Video Detection installed. Also, for stores using Video Detection, Pull-Forward windows are not currently supported using this technology. Please contact HME if you would like to know more about Video Detection or inquire about having it installed at your site. Additional Video Detection information can also be found online under ZOOM Nitro (click on the link or scan the QR code on the back cover).
TSP50

What is this screen for? The system can support more than one TSP, including different models.
This screen allows you to check the status of your TSP if model TSP50 is used.
Why is it needed? You can check the connection status and rename your TSP here. Options are limited when using a TSP50 with this system; for example, the LOOP HEALTH feature found in TSP Settings (and covered in this chapter) is only available for the TSP60.
NOTE The ZOOM Nitro system is capable of supporting multiple TSPs (a maximum of eight TSP60s). It can also support two models simultaneously (one TSP50 with up to seven TSP60s). Each additional TSP appears at the top of the screen.
Depending on what TSP model your store is using determines what TSP is displayed at the top of the screen. In Fig. 6.2, two TSP models are employed, so both TSP50 and TSP60 #1 are displayed. If, for example, you were to add another TSP60 to your system, it would also be displayed here.
In the NAME field, you can give your TSP a more descriptive name, which is useful if you have more than one TSP connected.
The green indicator next to the TSP50 tab in Fig. 6.2 indicates this TSP50 is physically connected.
If the TSP is physically disconnected, this indicator will turn red, and a prompt will also notify you.
When a TSP is physically disconnected, it is still visible onscreen because it has not been removed from the system yet. Use the button to accomplish this. This button only becomes active when a TSP is disconnected (a safety measure to prevent accidental removals). For example, in Fig. 6.2, TSP50 is connected, so the Remove button is deactivated (indicated by a faded blue color). If TSP50 is disconnected, the green indicator turns red, and the button becomes active. Once clicked, TSP50 will disappear from the top of the screen, leaving only TSP60 #1 displayed. Reconnecting the TSP will cause it to appear again with a green indicator next to it.
TSP60

What is this screen for? The system can support more than one TSP, including different models.
This screen allows you to check the status of your TSP if model TSP60 is used.

Why is it needed? You can check the connection status, rename your TSP and configure detectors here. The green indicator next to TSP60 #1 in Fig. 6.3 indicates it is connected. If an issue arises with your TSP, you can reset it by using the button. Caution! resetting the TSP closes out the lane temporarily. Therefore, all current lane event data is lost if there are vehicles present in the lane when the reset button is used. The TSP will begin monitoring lane events again once it reboots.
NOTE The ZOOM Nitro system is capable of supporting multiple TSPs (a maximum of eight TSP60s). It can also support both models simultaneously (one TSP50 with up to seven TSP60s). Each additional TSP appears at the top of the screen.
Depending on what TSP model your store is using determines what TSP is displayed at the top of the screen. In Fig. 6.3, two TSP models are employed, so both TSP50 and TSP60 #1 are displayed. If for example, you were to add another TSP60 to your system, it would also be displayed here.
In the NAME field, you can give your TSP a more descriptive name, which is useful if you have more than one TSP connected. The SERIAL NUMBER field is a unique identifier for the TSP, it cannot be changed. It correlates to the PCBA SN label found on the physical TSP60 (inside the hinged cover).
The green indicator next to the TSP60 tab in Fig. 6.3 indicates this TSP60 is physically connected.
If the TSP is physically disconnected, this indicator will turn red, and a prompt will also notify you.
When a TSP is physically disconnected, it is still visible onscreen because it has not been removed from the system yet. Use the button to accomplish this. This button only becomes active when a TSP is disconnected (a safety measure to prevent accidental removals). For example, in Fig.
6.3, TSP60 #1 is connected, so the Remove button is deactivated (indicated by a faded blue color).
If TSP60 #1 is disconnected, the green indicator turns red, and the button becomes active.
Once clicked, TSP60 #1 will disappear from the top of the screen, leaving only TSP50 displayed. Reconnecting the TSP will cause it to appear again with a green indicator next to it.

Greet Detectors
The system supports two greets.
Connector type – Audio Greet or Alternate Greet: This switch correlates to how J8 is wired on the TSP. Audio Greet is the default state for standard greet signals received from the audio lines.
Enable switch to select Alternate Greet if your inputs are digital inputs from other sources.
External Detectors
The TSP60 supports up to four external detectors.
Polarity configuration – Negative or Positive: Negative signal polarity is the default state for HME inputs; however, the system can also support signals with positive polarity used by non-HME inputs. Enable switch to select Positive polarity, if required.

On-Board Detectors
Up to four onboard detectors are available. Veh 5 is activated by default. For Veh 6 – 8, click on Activation required and follow the directions to purchase and activate any of these detectors. Use the ACTIVATION screen for this. Once an onboard detector is activated, the button appears next to the Veh #. Click on it to activate that onboard detector. If for any reason an activated onboard detector malfunctions, you can use the same button to deactivate it and choose another onboard to activate (this will also require a physical wiring change on the TSP to match the new onboard detector selected).
External Detector Mode: If you use an external detector instead of the onboard detector, turn this switch on (this action also disables all fields associated with the onboard detector).
Diagnostic Mode: Turn this switch on to test the onboard detector without requiring a vehicle present at the detection point. The associated onboard detector LED on the TSP turns on and off (alternating every 10 seconds). A warning prompt like this EATER 2..cars 2t the tp of the Dashboard. You must then turn Diagnostic Mode off to resume using the detector as normal.
VEHICLE PRESENCE AUTO RESET (No Timeout, After 20 minutes): The default is No Timeout. In the event a vehicle is still detected after already leaving; you can choose to have it reset after a time limit is reached. Caution! when auto reset happens, all current vehicle data is closed out if there are vehicles present in the drive-thru lane.
DETECTION SENSITIVITY (Normal, low): Adjusts the detector sensitivity when the vehicle arrives at the detection point. The factory default setting is Normal. If set to Low, lower detection sensitivity corresponds to slower detection at the risk of small fluctuations causing missed detections.
RELEASE SENSITIVITY (low to extra high): Release sensitivity correlates to how quickly the system will signal vehicle departure. The factory default setting is Medium. Setting it to a higher sensitivity means departures trigger more easily.
DETECTION DELAY (0 to 10 seconds): This sets a delay period, after which the system recognizes a vehicle is at the detection point. It is used to eliminate false detections. This delay is similar to and impacts another delay setting if set for the same detector under Lane Detectors in Car Detection Settings (see “Lane Detectors” on page 47). For example, if 5 seconds is selected here for Veh 6 and a delay of 5 seconds is also selected for Veh 6 in Car Detection Settings, the total delay time applied will be 10 seconds.

Activation

What is this screen for? The Activation screen is used to activate additional onboard detectors if needed and is only present when a TSP60 is connected (i.e., if your system only has a TSP50 connected, this screen will not exist).
Why is it needed? The TSP60 is designed with four onboard detectors. The TSP60 comes with one detector activated by default. You can purchase additional activations if your store uses more than one detector.
Call the number displayed on the screen and provide HME with the code listed in the FEATURE CODE field. HME will provide you with an activation code, which you can enter into the ACTIVATION CODE field.
The number of activations purchased is shown in the NUMBER OF ACTIVATIONS field, and the button appears next to the Veh # under On-Board Detectors on the TSP60 screen. After activating one or more detectors, another row with a new FEATURE CODE appears. This will be used to activate additional detectors at a future date if needed (see Fig. 6.5).

NOTE The ZOOM Nitro system is capable of supporting up to 64 detectors, which requires purchasing additional TSPs, a powered USB hub, and activating the additional detectors.

Loop Health

What is this screen for? Loop Health provides your store with a status of how your detector loops are performing.
Why is it needed? Monitoring the health of your detector loops is important to keeping your system running smoothly and problem-free. Wear and tear will cause loops to eventually deteriorate over time. A change in loop health may signal that maintenance is required. This will enable you to anticipate an eventual failure before it happens, thus minimizing downtime through preventive maintenance.
Color-coded indicators are used to provide you with the status of your loop health.

A green indicator means the loop is in good condition and functioning properly.
An amber indicator means the loop is in moderate condition but functioning okay. If this indicator was initially green, it might indicate that the loop’s condition is starting to deteriorate. Preventive maintenance is recommended at this stage. Allowing the loop to deteriorate more can eventually result in a critical failure if preemptive action is not taken to repair or replace the loop.
A red indicator means the loop is in poor or bad condition and may not be functioning properly or has completely failed. Immediate maintenance is required to repair or replace the loop.
Move the cursor over the blue information circle in the DETAILS column to provide you with additional information.
LOOP STATUS: This checks the loop’s inductance. The resulting indicator ranges from good , to moderate , to bad.
LOOP CONNECTION: This checks the loop’s physical connection. It is either good or bad.
CONDITION: The information presented in this column provides an assessment of both LOOP STATUS and LOOP CONNECTION combined with possible recommendations if necessary. For example, see Veh 5 in Fig. 6.6, a loop with two green indicators means everything is functioning well, your loop is in good health. However, two red indicators is a critical problem that will prompt you to call HME Technical Support for a corrective solution.

Car Detection Settings

Only Installers can access and edit the features on this screen.

Lane Detectors

What is this screen for? The Lane Detectors screen allows you to customize your system based on the unique layout of your store. Use the 1. Select Lane Configuration, 2. Add/Remove Detection Types, and 3. Configure Detector Mappings options and configure them to match the general layout of your store.
Why is it needed? Your store layout must be configured properly to provide meaningful data. Data and measured events on the Dashboard are based on the information entered here. Begin by selecting your lane type from the drop-down list under Select Lane Configuration.
Example: Fig. 7.1 shows a Y Lane store with two menus, one window, and two pull-forward detectors (one of these is a pull-forward window indicated with the PFW acronym). To make adjustments to this Y Lane configuration, you can add or remove detectors in the Add/Remove Detection Types section.
This Y Lane has two menus. To make adjustments to these menus, click on the down-arrow to the right of MENU to expand (see Fig. 7.2). Toggle the Include Greet switch to enable and notice that it is now reflected in the two menu tiles beneath the switch (see Fig. 7.3). Toggle the Include Merge switch to enable if your Y Lanes also use merge detectors.

This Y Lane has one window. To add another window, click on the down arrow to the right of WINDOW to expand and click Add (see Fig. 7.4). Notice a new window (Window 2) is now reflected in the PREVIEW graphic on the right (see Fig. 7.5). To remove Window 2, click in the tile’s upper corner.

To modify your Pull-Forward detectors, click on the down arrow to the right of PULL-FORWARD to ex- pand. If your store uses a pull-forward window, toggle the Include PF Window switch and notice how it is now reflected in the tile beneath and in the PREVIEW graphic (see Fig. 7.6). On the Dashboard, this pull-forward window is displayed above the end of the lane (see Fig. 7.7). For Single Lane and Y Lane configurations, the total number of pull-forward detectors is limited to three and only one of these can be used as a pull-forward window. Dual Lane configurations can have four pull-forward detectors (two per lane), but they do not currently support a pull-forward window since only one is available.

The Configure Detector Mappings section allows you to map your detectors to a Vehicle Number (Veh #). This Veh # correlates to the Veh # on the TSP, so you must map accordingly to match the actual connection. You can assign a descriptive name in the DISPLAY NAME field and choose your QUEUE SIZE from the drop-down list, which is the number of vehicles that can fit between this detection point and the next. For example, in Fig. 7.8, “Menu” (the first detector) is mapped to Veh 1, assigned the display name “Menu 1,” and the queue size selected is “4 Cars.” This indicates that four vehicles can fit between this detection point and the next detection point (Menu 2). The last detection points do not have a queue size because there are no other detection points/zones in the lane beyond this point. If your system uses more than one TSP, use the PROCESSOR field to select the one corresponding to each detector mapped (in this example, only one TSP50 is used).

NOTE: Queue size does not include the vehicles at the detection points, just those in between. Twenty feet (6.1 m) per vehicle is the estimated measurement used.

If a different choice is chosen from the Select Lane Configuration drop-down list, the Add/Remove Detection Types and Detector Mappings sections change accordingly. For example, if you choose a “Single Lane” configuration, the PREVIEW graphic changes to a Single Lane layout graphic.
If Curbside-Only is selected from the Select Lane Configuration drop-down list, there are no further configurations to be made here since Curbside-Only stores do not use drive-thru lanes. You must go to the INDEPENDENT DETECTORS screen to configure Curbside-Only parameters there. These chang- es are then reflected on the Dashboard.
NOTE: The Curbside-Only option is only available for stores using Video Detection. Contact HME if you would like to know more about this option.
Some Y Lane stores dedicate one lane to mobile orders. The lane chosen can be either the inside lane or the outside lane (the inside lane indicates the lane closest to the store building while the outside lane indicates the lane furthest away). Mobile orders can be distinguished from lane-placed orders by the neon blue border included around the order label (see Fig. 7.9). The mobile lane is also labeled as such on the Dashboard. The following is a brief description of different detector types.

Pre-Menu Detector: A detector that tracks vehicles prior to arriving at the menu detectors.
Greet Detector: A detection metric that tracks the time between when a vehicle is detected at the menu detector and when the order taker greets the customer via the headset.
Merge Point Detector: A detector located in each lane of a Y Lane configuration just before the lanes end and merge into a single lane. This helps track the sequence of vehicles merging from either lane into the single lane to help maintain order integrity and prevent confusion.
Pull-Forward Detector: A detection spot after the lane where a vehicle might be requested to pull into while they await their order. A Pull-Forward window functions exactly the same as a Pull-Forward spot but is a window on the building rather than a spot separate from the lane.
The Pull-Forward window detection point is physically located after the last window in the lane.
Advanced Settings ( icon)
* DELAY: This sets a delay period, after which the system recognizes the vehicle is in the queue.
It is used to eliminate false detections (See DETECTION DELAY under “TSP60” on page 42).
* DISCARD: If a vehicle is detected during this time limit but not detected after, it is discarded by the system. For example, a vehicle decides not to wait and pulls out.

Conditions: Detector labels are predetermined during the installation, so you must map using the correct Detector label. For example, if the detector you are configuring is connected to Veh 3 on the TSP, you must assign it Veh 3 from the DETECTOR drop-down list.

Independent Detectors

What is this screen for? The Independent Detectors screen is for detectors that are not part of a drive-thru lane (therefore independent and not dependent on other detectors within the lane).
Why is it needed? Your store may not use drive-thru lanes but have areas for mobile orders or curbside pickup. As standalone detection points, they are configured separately.
Example: Fig. 7.10 shows a TSP50 and Camera in use. Veh 6, for example, is connected to TSP50, is assigned the name Mobile 1 with a detection delay of 2 seconds (available detectors are selected from the DETECTOR drop-down list). The detection delay time enables you to add a delay to eliminate any false or unwanted detections. In Fig. 7.10, the second detector is a camera and therefore, the PROCESSOR is labeled VPU. The order in which the detectors are displayed here also reflects the order in which they appear on the Dashboard.

NOTE: Detector labels are predetermined during the installation, so you must map using the correct Detector label. For example, if the detector you are configuring is connected to Veh 7 on the TSP, you must assign it Veh 7 from the Detector drop-down list. If only one TSP is being used, the number of independent detectors available is dependent on how many lane detectors are already in use elsewhere. For example, if your store uses eight detectors and five are used in the drive-thru lane, then only three are available as independent detectors.
Independent Detectors are not available if Tandem Lane is the Lane Configuration selected under Lane Detectors.

To remove a detector, check the circle to the left of the PROCESSOR field, then click REMOVE . If your system uses more than one TSP, then the number of available independent detectors increases accordingly (excluding lane detectors in use). Click ADD to add another Independent Detector page if configuring more than four independent detectors. Four pages are supported here (16 detectors).

Lane Settings

What is this screen for? The Lane Total for lane events is set here. The Lane Settings screen allows you to define what you want Lane Total to be within a lane. You can choose what detection points you want to start at (START TOTAL) and stop at (STOP TOTAL). Then, at each detection point, you can choose when this time begins (START AT) and ends (STOP AT), i.e., at “Arrival” time, or “Departure” time. Two Lane Totals are available, which can be two separate event totals within the same lane of a Single Lane configuration or the same event total for each lane if two lanes are used.
Ignore Queue : Queue times can be included or excluded in Lane Total, and are included by default. Toggle switch to YES to ignore queue.
Average by Detector Count : This feature is only applicable to Lane Total 2. When this toggle is switched to “Yes,” the NUMBER OF DETECTORS field opens and defaults to the number of detectors configured. However, this number can be manually changed here if another average is desired using a different number of detectors. This field only accepts a number ranging from 2 to 5. For example, if your total time 2 is two minutes and you wish to average this across four detectors, enter 4 into this field (see Fig. 7.11). The average displayed will be 30 seconds.
Pull Forward Settings: When PULL FORWARD DETECTION is set to “Enabled,” the “Pull Forward” time is included as part of the Lane Total. “Pull Forward” reports if a car leaving the lane reaches the pull forward detection point within the set delay time; this feature enables the “Pull Forward” time to be associated with a car record. When “Disabled,” the pull-forward time is excluded from the Lane Total.
“PULL FORWARD DETECTION DELAY (SECS)” sets the time in which a car leaving the lane must reach the Pull Forward detector for the Pull Forward Detection time to be included in the car record for Lane Total. The delay range available from the drop-down list is from 1 to 45 seconds.

Advanced settings

Pullout & Pullin Settings: Pullouts are when a vehicle is detected at one active detection point in the lane but not detected at the next active detection point. Pullins are when a vehicle is detected at one active detection point in the lane but was not detected at the previous active detection point.
MAX SERVICE IDLE TIME (SECS): is the maximum amount of time that the last active detection point can be vacant with cars between other detection points. The range available from the drop-down list is 1 second to 10 minutes.
MAX DELAY TIME (SECS): is the maximum amount of time allowed for a vehicle to leave one active detection point and arrive at the next active detection point. The range available from the drop-down list is 1 second to 10 minutes.
Therefore, IF a vehicle leaves an active detection point but does not reach the next active detection point within the set delay time, AND this next active detection point has been vacant longer than the max service idle time, then it is considered a pullout and removed from the system.
PULLOUT DETECTED NOTIFICATION: choose “Enabled” to receive notifications of pullouts when they occur.
INCLUDE PULLINS: when “Enabled”, the pullin time is included in the Lane Total events. When “Disabled,” the pullin time is excluded from the Lane Total, Dashboard metrics, and summary reports.
However, Raw Car Data (RCD) is not affected (all data is shown regardless of whether enabled or disabled).
Why is it needed? Setting Lane Totals beginning at one active detection point and ending at another allows you to analyze the efficiency of lane events at your store. This helps pinpoint which detection points/zones need adjustments to increase productivity and traffic fluidity. Pullout and Pullin settings also allow you to include or exclude pullouts and pullins from your system calculations.
Example: Fig 7.11 has Lane Total starting when the vehicle arrives at the “Menu” detector point and stopping when the vehicle departs from the “Service” detector point with the queue time included (NO to IGNORE QUEUE). Lane Total 2 includes the same parameters but with the queue time excluded (YES to IGNORE QUEUE).
Conditions: Disabling the PULLOUT DETECTED NOTIFICATION feature removes notifications from your monitor but does not affect how the system handles pullouts.

Reports

Summary

What is this screen for? The Summary screen allows you to generate reports for periods of an Hour, Daypart, Shift, Day, Week, Month, or Year-to-Date.
Why is it needed? You may wish to analyze your measured events for specific periods of time. Use the REPORT and PERIOD drop-down lists to “Filter” your specific request. Then select a date range in the “From” and “To” fields.
Example: Fig. 8.1 shows a one-month report summary for the hour at 09:00 from September 24, 2024, to September 24, 2024.
Under the SUMMARIZED option, select “No” if you want the report for each selected period to be generated on a separate page. Select “Yes” if you want to generate a single page report containing summarized data from all of the selected period.
Under the FORMAT option, select your output format (PDF or CSV), then click on “Get Report” to retrieve it.
Conditions: While a PDF can be generated onscreen, it can only be downloaded using a remote computer or back-office PC, while CSV is only visible using a remote computer or back-office PC. The retrievable records are dependent on the time limits and storage space available. This time limit is listed under CAR DATA START date and time just above the Filter field of this screen (it corresponds to the Database date found under STATUS on page 62).

Raw Car Data

What is this screen for? The Raw Car Data feature allows you to generate a detailed record for every vehicle that passes through the drive-thru lane. It enables the user to filter the results based on a location or event (chosen from the drop-down list) within a specific date/time range.
Why is it needed? You may wish to analyze specific detection locations at specific times or dates based on a filter of choice. This enables you to recognize trends or issues, thus prompting you to make any adjustments if necessary. RCD (Raw Car Data) will also show mobile orders separate to lane placed orders (or orders other than mobile orders).
Example: Fig. 8.2 shows an RCD report for Cars in Lane greater than zero for the hours between 05:00 AM and 10:14 AM of September 18, 2023. PDF is the selected export format.
Conditions: Same as those found in the Summary section of this chapter.

Schedule

What is this screen for? It allows you to set a schedule for automatically generating reports based on user-defined parameters selected in the Summary Report section of this screen.
Why is it needed? You may wish to collect, analyze, and compare business data for specific periods.
This can help you to recognize daily, weekly, monthly, or even yearly trends, thus allowing you to see where any necessary adjustments to your business model or hours of operation are needed.
Email Enabled : The Send Test Email button becomes active when Email is enabled, so you can verify that the email address(es) entered into the Destination Address fields are valid.
The Source Address and Destination Address fields are auto-populated by default, enter a new address to customize.
Source Address: A valid source address is useful to prevent the report from being discarded or ending up in a spam folder.
Destination Address: This is the location where the scheduled report is sent to. More than one destination address can be entered into this field; however, you must separate each address using only a comma with no spaces.
Use SMTP default values Enabled : SMTP (Simple Mail Transfer Protocol) is enabled by default and auto-populated (it assumes that the standard SMTP server configuration is used). Some organizations, however, may wish to use their own SMTP server configuration for security or other reasons.
This will require you to disable this feature and manually configure the new fields that appear once this feature is disabled.
Click on “Summary Report” to expand this option (see Fig. 8.6). Enable any segments of time you would like to schedule a report for and adjust accordingly. If you leave the C Send reports at the end of the day box unchecked for Hour, Dayparts, or Shifts, the report is sent as soon as the time value in the “END” field is met. Check the box if you would prefer to receive the report at the end of the day (e.g., as with the Hour option in Fig. 8.6).
Use the “+“ sign to the right of a field to expand for an additional row of options (e.g., the Hour option in Fig. 8.6).

Security

Only Installers and Managers can access and edit the features on this screen.

Login

What is this screen for? It is used to sign in and gain access to system features.
Why is it needed? Permission rights allow you to restrict access to certain features or screens on your system. This is a security measure that also helps prevent unauthorized users from changing parameters. There are four user levels, each granting permissions to specific features of the ZOOM Nitro system. These user levels are Dashboard, Report, Manager, and Installer.
Dashboard User: allowed access to the Dashboard settings.
Reports User: allowed access to the Dashboard settings and the Reports screen so that reports can be generated.
Manager: allowed access to the Dashboard, Store, Report, Security, and System screens.
Installer: has access to the entire system. This is the highest level of access permitted and is required to configure the system, to perform maintenance, and to upgrade.

Example: Fig. 9.1 shows the Installer option selected. Once logged in, they are shown as the current user (Fig. 9.2). Clicking on “Log Out” logs the current user out and causes the PASSWORD screen to disappear.
Conditions: Your assigned user-level determines what features are accessible on the system. The Manager assigns logins/passwords for Dashboard and Report users. The system only allows one user to be logged in at a time. You must have a password to use this system. The PASSWORD screen only becomes available when the Installer or Manager logs in.

NOTE: If a temporary password is needed to get you started, call HME Technical Support at 1-800-848-4468. The system times out after 15 minutes of inactivity, and your temporary password is only valid within the clock hour you receive it. If you delay using this password and either of these two conditions is met, you will require another temporary password. Therefore, use this temporary password as soon as you receive it and create a new permanent one.
Another user can access the store via the HME CLOUD without requiring the current user to log off.

Automatic Log Out: After eight minutes of inactivity, a dialog box will appear with a three-minute countdown timer (Fig. 9.3). This dialog box prompts the user to select the option Yes stay logged in or No, log me out. If neither option is selected, this timer continues to count down to zero, after which the system automatically logs the current user out.
NOTE: _ If you have changed any settings but have not saved them, they will be lost if you are automatically logged out or you choose the No, logout option.
Your settings will revert to the previously saved settings. Therefore, save your Settings beforehand if you anticipate periods of inactivity.

Password

What is this screen for? It is used to assign or change passwords for users of this system.
Why is it needed? Passwords are a security measure to ensure that only authorized personnel can access your system. It is also used to restrict access to certain features. In Fig. 9.4, the Dashboard password screen is active.
Conditions: Passwords are assigned by the Installer and then by the Manager. Passwords must contain at least eight alphanumeric characters containing a combination of all of the following:

at least one uppercase letter,
at least one lowercase letter,
at least one number.

See “NOTE” under “Login” on page 59 for information on receiving a temporary password if you need it.

System

Only Installers and Managers can access and edit the features on this screen.

Status

What is this screen for? The Status screen is primarily used by HME Technical Support. It provides information about your system such as serial numbers, database records, software, hardware and OS version numbers, etc.
Why is it needed? It is used during the installation process, setup phase, and maintenance. It provides installers and Technical Support with crucial information about your system that may be required when troubleshooting, or upgrading your system.
The Database section lists the current Number of Records stored for the period between the Start and End dates. Start dates begin when the system is first installed and runs continuously. The End date is the most current (if the system is running). The number of records stored is cumulative and dependent on variables such as storage space available, maintenance, etc.

Demo Mode

What is this screen for? This is an installer only feature. Demo Mode allows a customer to see a simulated drive-thru environment without having a complete physical system installed.
Why is it needed? It is primarily used for corporate labs and allows them to simulate a large volume of vehicles to populate their drive-thru, metrics, and reports with the simulated data generated.

Help

If the help provided in this section is not sufficient, please contact our Technical Support team at support@hme.com or call us at 1-800-848-4468. As a valued customer, we are here to help you have the best experience with your product; your success is our success!

TSP50 Diagnostic Lights

The following table gives you an overview of the TSP50 lights. It can help when troubleshooting issues with your system. If any of the lights do not perform as described, it may indicate an issue. If you cannot resolve it with the information presented here, please contact HME Technical Support.

Light ID	Description/Function
EXT Power Light On: EXT Power Light Off:	An external power supply is connected to the TSP. Light Color is Green. No external power supply is connected. If a power supply is connected and the light is not on, check the power supply connections on both ends to make sure they are plugged in properly. Note: An external power supply is only required when two additional Vehicle Detector PCBAs are used (i.e., if more than five detectors are used). Note: Only use the power supply provided by HME.
Power Light On: Power Light Off:	The TSP is connected to the CU, with the CU turned on. Light Color is Green. Not connected to the CU or the CU is off. If not on under these circumstances, check cable connections and make sure the CU is turned on. Note: This light remains on even when powered by an external power supply (i.e., EXT Power Light is also on at the same time).
Vehicle Detect Light On: Vehicle Detect Light Off:	The corresponding detector senses the presence of a vehicle over it. Light Color is Red. There is no vehicle present over the detector, or this light is not used. If, for example, you only have four detectors connected (onboard, and ports VEH2, VEH3, and VEH4 of the TSP). Then, only the Vehicle Detect lights labeled 1 through 4 are active when detecting vehicles (i.e., Vehicle Detect lights 5 – 8 are not in use because there are no detectors connected). If a vehicle is present over a corresponding detector and the light is not on, check TSP port connections and detector functionality. For example, wireless detectors are battery-powered and, over time, weaken and die.
Greet Light On: Greet Light Off:	The Greeter/Order Taker is speaking to a customer. Light Color is Red. There is no dialog between the Greeter/Order Taker and customer or if not in use. Note: Greet lights A and B are usually the only two greet lights used.
Link Light On: Link Light Off:	The CU is on, and you have a hard network connection. Light Color is Green. The CU is off, or if the TSP is not connected to the CU. If Link Light is off when it should be on, ensure that the cable connection between the TSP (inside the TSP) and the CU is properly connected, and the CU is on (the Power Light on the TSP will be on if the CU is on).
Data Light On: Data Light Blinking: Data Light Off:	Solid when there is a data connection, and the system is turned on. Light Color is Green. Blinking when communicating. There is no data connection, or the system is turned off.
Status Light On: Status Light Blinking: Status Light Red: Status Light Off:	Solid when there is a connection but no communication. Light Color is Green. Blinking when communicating with the Control Unit (The Data and Status Light blinks are not synced and blink at different rates). When there is a communication problem. When the system is turned off.

TSP60 Lights

The following table gives you an overview of the TSP60 lights. It can help when troubleshooting issues with your system. If any of the lights do not perform as described, it may indicate an issue. If you cannot resolve it with the information presented here, please contact HME Technical Support.

Light ID	Description/Function
Power Light On: Power Light Off:	The TSP is connected to the CU, with the CU turned on. Light Color is Blue. If not on under these circumstances, check the USB cable connections and make sure the CU is turned on. The TSP is not connected to the CU, or the CU is off.
On-Board Detector Light On: On-Board Detector Light Off:	The corresponding detector senses the presence of a vehicle over it. Light Color is Blue. For example, if you have four detectors connected (onboard). Then, all the On Board Detector lights labeled 5 through 8 are active when detecting vehicles. There is no vehicle present over the detector, or no detector is connected (light not in use).
External Detector Light On: External Detector Light Off:	The corresponding detector senses the presence of a vehicle over it. Light Color is Blue. There is no vehicle present over the detector, or no detector is connected (light not in use).
Greet Light On: Greet Light Off:	The Greeter/Order Taker is speaking to a customer. Light Color is Blue. There is no dialogue between the Greeter/Order Taker and the customer, or if the Greet detector is not in use.

Troubleshooting

If your system malfunctions, first, open the TSP cover and check your connections. Fig. 11.3 shows how to open the TSP60. Also, check your connections at the CU. Try disconnecting and reconnecting the interface cables between the ZOOM Nitro system devices such as the USB cable between the TSP and CU. If that doesn’t resolve the issue, try resetting the system by powering the system off and back on again using the CU power button.

Electrical Power Outage: If your system fails to function properly after an electrical power outage, power the system off and unplug the AC power adapters from their electrical outlets. Wait a few seconds, then plug them back in and power the system back on.
If you cannot resolve problems with the information presented here, please contact HME Technical Support at 1-800-848-4468.

Glossary of Terms

Bottleneck: This is the choke point in a drive-thru lane, or any event/detection point that causes delays, or goals to be missed.
Car Count: The total number of vehicles that have gone through the drive-thru lane and departed from the last detector or detection point.
Cars in Lane: The number of vehicles that have arrived at, or passed, the first active detection point in the drive-thru lane, but have yet to leave the last active detection point.
CSV: Comma-Separated Value, is a file containing values separated by a delimiter, and formatted as a database table. If application software such as Microsoft Excel® is installed on your computer, the CSV will open as a spreadsheet.
CU: Control Unit, or CU, is generally followed by the model number (e.g., CU60 is model 60). The CU receives and processes lane event data from the TSP. The device then sends the real-time information to be displayed in a visual format on the system monitor.
Also, the CU sends information to the HME CLOUD for historical reporting and comparative analysis between other stores. The Control Unit also sends information to the HME CLOUD for comparative analysis with other QSRs/stores and historical reporting.
Danger Zone: If using Nitro Video Detection, this is a region of interest (ROI) before the pre-menu zone of a drive-thru lane where vehicles can still pull out/drive off before reaching the menu point.
Dashboard: The main display on your monitor that shows real-time drive-thru activity.
Database: This is a collection of records electronically organized and filed in a central location.
Data Export: A report feature enables a store to send report data to a local network location.
Data Section: These are square or rectangular panes on your Dashboard displaying user-defined event data or metrics for a detection point or event in a drive-thru lane. For example, see “Data Sections – Example 1” on page 19 or “Data Sections – Example 2” on page 22.
Daypart: A customizable segment of your business day that you would like to monitor. You can set up to 23 Dayparts per day. Each Daypart automatically ends when the next Daypart begins; Dayparts cannot overlap. Common Daypart examples are “breakfast,” “mid-morning,” “lunch,” “dinner,” and “late-night hours.”
Detector/Detection Point: A location, generally in a drive-thru lane, where a vehicle’s presence is sensed by a loop or other detection hardware such as a camera. Detection points are typically located at the Menu Board, Cashier/Pay Window, and Service/Present Window.
These detection points are dependent on other detection points in the lane to provide measured events for the lane. A detection point can also be located outside the lane. Detection points of this type are called “independent detectors” because they exist as standalone detectors. E.g., a mobile pickup or wait area.
Detection Time: The time from a vehicle’s arrival at a specific active detection point until its departure from that point.
DHCP: Dynamic Host Configuration Protocol is a network management protocol used on UDP/IP networks whereby a DHCP server dynamically assigns an IP address and other configuration parameters to each device on a network so they can communicate with other IP networks.
Disastrous Orders: This is the number of vehicles or orders that have exceeded the user-determined Disastrous Orders Goal. For example, if speed goal D has the longest time value of goals A, B,C, and D (where A = 30, B =60, C = 90, D = 120), then any vehicle or order exceeding 120 is considered a Disastrous Order.
This order fails to meet the easiest limit set for a goal.
DNS Server: Domain Name Server is a directory of domain names with translated Internet Protocol (IP) addresses. This is the Internet’s equivalent to a phone book.
Drive Off: This is when a vehicle is in line to order (pre-menu) but then decides to leave or drive off before placing an order. This can be due to long wait times or a change of mind.
Event Time: The time associated with Lane Events, including Queue time, Lane Total, Detection Point time, and Greet time.
Gateway: A device (usually a router) that connects one or more computers on a network to other networks.
Geofence: A virtual geographical boundary or perimeter defined by GPS or RFID technology, that enables software to trigger a response when a mobile device enters or leaves this boundary.
Goals: Ideal service times that you can set as objectives for measurement of efficiency in drive-thru service. For example, you can set goals for Service, Menu, Greet, and Lane Totals.
Greet Time: The time from a vehicle’s arrival at the Menu Board detection point until the order taker begins speaking to the customer.
HME CLOUD: This is an optional service offered by HME that allows your enterprise to correlate data from multiple locations. As a computing term, the cloud refers to servers that are accessed over the Internet and the software and databases that run on those servers.
Independent Detector: These are standalone detectors that are not part of the general drive-thru lane configuration, which relies on dependent detectors. They are generally used for mobile orders and curbside pickups.
IP Address: Internet Protocol Address is a unique computer reference that some electronic devices (e.g., computers or routers) use to identify and communicate with each other on a computer network.
Lane and lane type: A lane is any drive-thru lane. Lane types are generally one of the following:

Single Lane: one entry point detector and one exit point detector.
Y Lane/Mobile Lane: two entry point detectors and one exit point detector.
Dual Lane type: two entry point detectors and two exit point detectors.
Tandem Lane: one entry point, with two in-line ordering points and one exit point detector.

Lane Event: Any drive-thru event or series of events in which time is measured at active detection points. A Lane Event can be measured by lane, Queue time, Lane Total, Detection point time, and Greet time.
Lane Total: The time from a vehicle’s arrival at or departure from the first active Detection Point, until the vehicle’s arrival at or departure from the last active Detection Point.
Leaderboard: This is a visual representation of your store’s specified data and measured events displayed against the same data points of other stores in your area.
MAC Address: (Media Access Control Address) is a unique identifier for a device on a network. It’s a 12-digit alphanumeric attribute that is usually found on the device network interface card (NIC). It ensures that data packages reach the correct destination.
Mobile Pickup: A designated or reserved parking space in the customer parking lot for mobile orders.
Mobile Pickup spaces use independent detectors (not dependent on other detectors).
NTP: Network Time Protocol is a networking standard for clock synchronization between computer systems; NTP is intended to synchronize all participating systems within milliseconds of Coordinated Universal Time (UTC).
NVD: Nitro Video Detection, a newer technology using cameras that allows vehicles to be detected, identified and tracked through a drive-thru environment or designated stalls used for pull-forward, curbside or mobile pickup orders.
PDF: Portable Document Format is a file format designed to present documents consistently across multiple devices and platforms.
POS: Point of Sales is referenced in this guide as a system that generates customer transactions.
ZOOM Nitro can integrate with some industry-standard POS systems.
Pullin: A vehicle that entered the drive-thru lane after the first active detection point, and exited through the last active detection point.
Pullout: A vehicle that entered the drive-thru lane through the first active detection point, but exited the lane before the last active detection point.
Pull-Forward: This term refers to the space offset from the drive-thru lane with a conditional detector point. It only tracks a vehicle from a previous detector point if it reaches this detection point within a set amount of time (selected from the Pull-Forward Detection Delay menu). This detector can either be enabled or disabled for use in Lane Total calculations. A Pull-Forward window is a window on the building rather than a space separate from the lane. The Pull-Forward window detection point is physically located after the last window in the lane Queue Size: This is the number of vehicles that will fit between two detection points (beginning from the front of a vehicle on one detector and ending at the rear of a vehicle on the next detector). Twenty feet (6.1 meters) is the estimate used per vehicle. For example, if the distance between two detection points is sixty feet, then your queue size for this section is three vehicles.
Queue Time: The time from a vehicle’s departure from any active detection point until its arrival at the next active detection point.
QSR: Quick Service Restaurant, an industry-standard term used in the hospitality industry for restaurants specializing in the quick preparation and service of food.
Raw Car Data: Vehicle times automatically stored in the system every time a vehicle leaves the last active detection point. Raw Car Data is collected over a period of time and is used by the system to compile reports.
Report: A generated document that compiles a specific set of data or measured events for a specified period of time. This report can be generated in formats available for that report type (e.g., PDF or CSV).
Service Goals: A time limit that a vehicle should not exceed for a given Lane Event. Service goals can be applied to any Lane Event, such as the time that a vehicle spends at a detection point.
Subnet Mask: Splits the network into a series of subgroups or subnets, to speed up the delivery of data by the routers.
Shift: Scheduled work hours for your store’s crews. Up to eight shifts can be set in a 24-hour period representing a day between opening and closing times. Shifts can overlap. For example, Shift 1 could be set from 6 AM to 2 PM, while Shift 2 could be set from 11 AM to 7 PM. Also, a shift can go past midnight and overlap two days.
SMTP: Simple Mail Transfer Protocol is a communication protocol for electronic mail transmission.
For this protocol, port 25 is the traditional default port used to communicate email across the Internet.
But other ports such as port 587 are also used as SMTP ports.
Statistical Summary: This is a dashboard section pane which shows the selected summary data for the current Hour, Daypart and Day periods.
Store Hours: Your store’s opening and closing times for each day of the week. Store hours for any two days cannot overlap. There can be only one store opening time for each day of the week. Store hours can span midnight. For 24-hour stores, the store open and close times are the same.
System: Refers to all the individual components (such as the CU, Software, TSP, detectors, cables, and monitor, etc.) connected and working as a whole, unless otherwise specified.
Time Server: A server computer that reads the actual time from a reference clock and distributes the time to its clients via a computer network. The Time Server may be set to a local network time server or an Internet time server.
Trailing Hour/Half-hour: This is a continuous rolling hour, or half-hour, of the last 60/30 minutes that updates every minute. As opposed to Hour, or Half-hour, which is based on the clock hour/half-hour time (updates on the hour, or half-hour marks).
TSP: The Timer Signal Processor (aka timer) is generally followed by the model number (e.g., TSP50 is model 50, TSP60 is model 60) receives and sorts Lane Event detection signals from the peripheral detectors and sends the information to the CU for processing.
UNC: Universal Naming Convention, is a standard for identifying servers, printers and other resources in a network.
VPU: Video Processing Unit is a specialized electronic device used for processing image and graphical data intended for output to a display device.
Wait Area: A designated pullover area where vehicles can wait for orders to be fulfilled.
Web Server Port: The network port used by ZOOM Nitro to connect to the TSP via the network.
ZOOM Nitro: ZOOM®is a registered trademark brand name owned by HME. A specialty communications timer system primarily used in the hospitality industry, including QSRs or stores with drive-thru lane environments.

NOTES………………………………

Specifications

CU60
Dimensions	4.33” x 4.57” x 1.93” (110 x 116 x 49 mm)
Power Supply	12 V, 60 W, AC Adapter, US Power Cord
Chipset	Intel® Celeron ®N2930 1.83 GHz, 2.16 GHz Burst Quad-core SoC
Memory	4 GB total memory, Low Voltage 1.35 V Required
Storage	128 GB mSATA Solid State Storage
LAN	Realtek RTL8119I GbE
Front Panel	Power button, Power & HDD LED, 1 x USB 3.0 port, 1 x USB 2.0 port, Serial RS232/422/485 port
Rear Panel	2 x USB 2.0 ports, 2 x HDMI, 2 x RJ45, 9 V – 24 VDC In jack
Compliance	CE, FCC, RoHS, ErP Ready
Temperature	Operating Temperature 0 – 35 °C, Storage Temperature -20 – 85 °C
TSP50
Dimensions	9.25” x 7” x 3.5” (235 x 178 x 89 mm)
Power Supply	(Optional) Eurasia Power, 12 V, 24 W, Wall Mounted
Weight	2 lb (907 g maximum, including 3 VDBs)
Ports	1 x USB 2.0
Miscellaneous	Supports 8 VDBs total and 2 Greet signals. 1 onboard VDB, 1 Internal – from USB power. Alert (requires external power supply)
TSP60
Dimensions	8.8” x 5.95” x 2.01” (224 x 151 x 51 mm)
Power Supply	Power source from CU60 via USB cable, 5 V, Max Current Draw < 300 mA
Weight	13.5 oz (383 g)
Ports	1 x USB type B
Miscellaneous	2 Greet signals, 4 External Detectors, 4 Onboard Detectors

NOTE: For specifications regarding other components like the monitor or cables, please reference the OEM (Original Equipment Manufacturer) documentation.

https://www.hme.com/qsr/drive-thru-user-manuals
A copy of this guide and much more can be found by scanning this QR code
or going to: https://www.hme.com/qsr/drive-thru-user-manuals/
© 2024 HM Electronics, Inc.
The HME logo and product names are registered
trademarks or trademarks of HM Electronics, Inc.
All rights reserved.

Documents / Resources

HME ZOOM Nitro Thru Timer [pdf] User Guide
ZOOM Nitro Thru Timer, ZOOM, Nitro Thru Timer, Thru Timer, Timer

References

User Manual

END-USER LICENSE AGREEMENT (EULA)