Whiz Connect Overview

Overview

When you sign-in to Whiz Connect, you will land on the Overview page displaying three graphs summarizing Whiz usage, assists, and routes. The individual sections will provide more detailed information.

Options

The date range will default to the previous seven days (‘Date Range: Default’). To change the date range, click the bolded date range in the upper right corner and select your new start and ending dates. Please understand that large multi month queries may take 20 seconds or more to complete, as the data sets are large. Generally, date ranges of 3 months or less should generate data quickly. We will be optimizing the performance of loading large date ranges in the future.

Date Grouping: By default, the data is grouped by day, but you can select the Week or Month tabs as well to group the data by week and month, respectively. Notice Target and Calculated lines only display when the Week grouping is selected because our ROI targets (entered on the Locations page) are determined by week.

Coverage or Runtime: Robot usage is measured by Coverage (area cleaned by Whiz) or Runtime (time Whiz ran) by selecting either tab.

Locations: By default, all locations are selected, but you can select one or many locations using the drop-down menu.

Download: Click the blue download button to generate a PDF displaying the overview graphs.

Graphs

  1. Usage (AKA: Actual Usage vs Target Usage)

    This graph displays the robot’s actual usage measured by coverage or runtime. When the data is grouped by week, the title changes to “Actual Usage vs Target Usage,” and notice the “Target Coverage” and “Target Runtime” horizontal lines appear to easily compare actual numbers vs targets. These targets are manually entered by the Customer Success team. For runtime only (not coverage), we have implemented a beta line called “Calculated Runtime,” which could eventually replace the manual Target Runtime estimate, as it is calculated by Target Coverage / Whiz Average Speed (5380 sq ft/hour). This line is turned on and off using a toggle.

    Three summary metrics display below the graph. To the left of each metric, delta % change from the previous period is listed.

     

    Coverage

    1. Total Actual Coverage: Sum of the total square footage Whiz actually covered
      The 2nd and 3rd metrics only appear when the data is grouped by week:
    2. Coverage %: Total Actual Coverage / Total Target Coverage [in the past this has been called “Coverage Utilization” or “% Usage Attainment”]
    3. Total Target Coverage: Estimate of the addressable carpeted floor to be vacuumed by Whiz, in square feet.

     

    Runtime

    1. Total Actual Runtime: Sum of total time Whiz spent cleaning.
      The 2nd and 3rd metrics only appear when the data is grouped by week:
    2. Coverage %: Total Actual Runtime / Total Target Runtime [in the past this has been called “Runtime Utilization” or “% Runtime Attainment”]
    3. Total Target Runtime: Estimate of the time that all routes will run.


  2. Assists (AKA: Assists vs Usage)

    This graph compares assists against usage. Usage is split between autonomous and training mode, as more assists are expected immediately after a new route is trained.

    There are three summary metrics appearing below the graph. Delta % change metrics behave the same way they do in the usage graphs.

     

    Coverage:

    1. Total Assists: Total number of times Whiz required human intervention.
    2. Total Autonomous Coverage: Sum of square feet Whiz covered while running autonomously.
    3. Total Training Coverage: Sum of square feet Whiz covered while in training mode.

     

    Runtime

    1. Total Assists: Total number of times Whiz required human intervention.
    2. Total Autonomous Runtime: Amount of time Whiz spent running autonomously.
    3. Total Training Runtime: Amount of time Whiz spent running in training mode.

     

  3. Route Runs

    This graph displays the total number of route runs. There is only one metric that appears below the graph. Delta % change metrics behave the same way they do in the usage and assist graphs:

    1. Total Route Runs: Sum of route runs.