HindSight 20/20 User s Guide version 5.4.1

Transcription

1 HindSight 20/20 User s Guide version August 2007 Copyright c 2007 DriveCam, Inc. All rights reserved.

2 TABLE OF CONTENTS INTRODUCTION 3 Read This Before You Begin 3 WORKING IN THE MAIN WINDOW 4 Event View 4 Query View 6 OBJECTS AND THE RESOURCE MANAGER 8 HindSight Groups 9 Users and Roles 10 Event Recorders 12 DriveCam Vehicles 16 Event Movers 17 CONFIGURING GROUP SETTINGS 18 General Group Settings 18 Event Recorder Defaults 19 Triggers 19 Wireless 21 Audio and Video 23 Time Zone 24 Overdue Times 24 Wireless Settings 26 REVIEWING EVENTS 27 Viewing Event Playback 28 Using the Event Graph 29 Interpreting and Scoring the Event 30 Understanding the Event Workflow 32 REPORTING RESULTS 33 Driver Reports 34 Group Reports 34 Overdue Reports 34 Installation and Error Logs 34 A1: EVENT WORKFLOW RULES 35 A2: VIEWING EVENT PLAYBACK 37 A3: USING THE EVENT GRAPH (TUTORIAL) 38 A4: INTERPRETING AND SCORING THE EVENT 40 A5: INHERITING EVENT RECORDER SETTINGS (TUTORIAL) 42 A6: SAFETY ENHANCEMENT MODULE SUPPLEMENT 44 A7: RFID CARDS (DRIVER IDENTIFICATION) 51 INDEX 52 DriveCam Technical Support is available 24 hours / 7 days at (866) For international assistance, please call (858)

3 HINDSIGHT 20/20 SOFTWARE VERSION USER S GUIDE The HindSight User s Guide is a condensed version of HindSight Help. Both are installed on every computer running the HindSight Client. This guide (HindSight Users Guide.pdf) is available through the Start menu >> All Programs >> DriveCam >> HindSight folder. The help file (HindSight.chm) is accessed from within the software, through the Help menu. The HindSight User s Guide provides an introduction to the software and is written for all users. It presents a general study of the user interface in a clean, uncomplicated format. It is not meant to describe all of the software features. HindSight Help details all areas of the software interface every window, every option. This HTMLbased file is similar to a web page, with electronic navigation and search tools. Quite different from reading a book (or guide), concepts are broken down into individual files and rely more heavily on lists, hyperlinks, and examples than on paragraphs of text. These two instructional tools, combined with the user-friendly interface of the HindSight Client v5.4.1 will help you to easily find the information you need, when you need it. Read This Before You Begin There are several additional documents and help files included with this software (eight in all). Each is part of a series designed to assist you in an easy and optimal deployment of the DriveCam Program throughout your organization. The HindSight Quick Start Guide provides you with a roadmap for installation and deployment of the system. This printed and electronic document is included with the HindSight Installation CD. The HindSight Installation Guide details installation of all HindSight software components. Once installation has been completed, you should refer immediately to the HindSight Administrator s Guide. It provides detailed instructions regarding setup and configuration of the system, including initializing event recorders. Both of these documents are available in PDF format on the HindSight Installation CD. Finally, the Admin Tools Help, Event Mover Help and Event Player Help are accessed from within the HindSight Admin Tools, HindSight Event Mover Monitor, and the DriveCam Event Player, respectively. DRC165-B Page 3 HindSight 20/20 v5.4.1 User's Guide

4 WORKING IN THE MAIN WINDOW The HindSight Events View and Query View are very similar in both appearance and function. For most users, the Events View will be the main work area the Query View is used for more detailed searches. Switch between the two by clicking the tab at the lower left of the window. The Events View is displayed when you log on to the HindSight Client. Within the main body of the window is a list of DriveCam Events stored in the database. The window is divided into three main areas: The Results Grid lists events that the logged-on user has permission to view. Drivers will only see their events supervisors, reviewers, and coaches will see events from their assigned groups administrators will see all events in the database. For all users, the events displayed depend upon the filter(s) applied. The Columns Panel allows you to change the look of the Results Grid. Each column represents an aspect of the event (i.e. record date, vehicle, driver, etc.). Columns can be shown, hidden, and moved to suit your viewing preferences. The Filter Panels allow you to search the database. The list of events can be narrowed based upon their group assignment, status, the vehicle in which they were recorded, the driver responsible for them, and the date that they were recorded. Additional event filters are available in the Query View. DRC165-B Page 4 HindSight 20/20 v5.4.1 User's Guide

5 Filtering and Sorting Events There are Five Filter Panels in the Events View that can be used to narrow the list of events displayed in the grid. To activate a panel, select a panel checkbox (e.g. Status) in the panel s header. To use the filter, select or enter a filter option (e.g. New) and click Apply. Any combination of filters can be used. To view all of your assigned events, clear all five panel checkboxes and click Apply. The filter panels will be shaded, though you may notice the filter checkboxes are still selected. The system remembers your filter preferences. As long as the filter panels are not activated, the filters will not be applied. Columns in the grid can be sorted alphabetically or numerically by clicking a column header. Opening Events for Review and Coaching To open a single event, simply double-click the event in the grid. To open multiple events, Shift + click or Ctrl + click to highlight the events in the grid, then click the Open button on the toolbar. The first in the series of selected events will be opened in the Event Review window. Click the Next and Previous buttons at the bottom of the Event Review window to move through the selected events. Customizing the Display The display can be modified to suit your personal viewing preferences. Columns and panels can be resized, rearranged, or hidden from view. Each time you log on to the system, HindSight will remember your most recent settings. This applies to both the Events View and the Query View. The Columns Panel is located (by default) to the left of the window, though it can be moved to the top, bottom, or right using a drag-and-drop operation. It can be hidden from view by clicking the thumb-tack icon at the top of the panel. This can also be done using the Show/Hide command in the View menu. Select or clear the checkboxes in the Columns Panel to display or hide those columns in the grid. To move columns in the grid to the left or right, highlight the selected column to be moved in the Columns Panel and use the up or down arrows. This can also be accomplished using a drag-and-drop operation of the column headers directly in the grid. Use the Show/Hide Filter button to change the display of the Filter Panels. Filters can still be applied when the panels are hidden. An icon will be displayed to indicate which object is being filtered and the specific filter settings will be shown at the top of the screen in text. All panels and columns may be easily resized by using the mouse to expand or reduce their borders. The page and item selectors at the bottom of the window allow you to select or scroll through pages in the grid and to specify the number of items to be displayed per page. DRC165-B Page 5 HindSight 20/20 v5.4.1 User's Guide

6 The Query View allows you to perform detailed searches not only for events, but also HindSight Objects (i.e. vehicles, users, roles, event recorders, Event Movers, and logs). Nearly identical to the Events View, the window is divided into three main areas: the Results Grid, Columns Panel, and Filter Panels. Filtering and Sorting Objects There are Many Filter Panels in the Query View that can be used to narrow the list of objects displayed in the grid. In fact, there are as many filters as there are columns (properties) for each object. Unlike the Events View, the information displayed in the Query View depends upon the object selected. To get started, select an object (Vehicles, Users, Events, etc.) from the drop-down list in the Filter on Columns Panel. Notice how the window changes depending upon the object selected. These are properties of the different objects and each can be used as a search parameter. Within the Filter on Columns Panel will be displayed a list of items and checkboxes corresponding to the available filter panels that can be activated for the selected object. To activate a filter panel, select one or more of the checkboxes in the list. The filter panels will be displayed in the order they are selected. To use a filter, select a filter checkbox and click Apply. Any combination of filters can be used. Events can also be displayed in the Query View just as they are in the Events View. The Query View, however, provides you with many more filters than the standard five filters available in the Event View. In other words, you can perform more detailed searches of events in the Query View. DRC165-B Page 6 HindSight 20/20 v5.4.1 User's Guide

7 The Query View is also where Safety Events are displayed. These are special events recorded through DriveCam s Safety Enhancement Module (SEM). Refer to page 44 for more information. Viewing Object Properties HindSight Objects can be opened for editing through both the Query View and the Resource Manager, including users, vehicles, event recorders, and Event Movers. To open an object in the Query View, simply double-click the object in the grid. Object properties are discussed in the next section: Using the Resource Manager. Monitoring System Performance HindSight can be configured to automatically monitor system performance and to alert you when an item or task requires attention. These are the Overdue Times Settings (page 24). They track vehicles and event recorders overdue for download, Event Movers overdue for synchronization, and events overdue for reviewing and coaching. Overdue items are highlighted in various colors in the Results Grid and summarized on the lower status bar of the Main window. They can also be displayed in reports. Additional Functionality There are many other features and advanced functionality available in the Main window that are not covered in detail in this guide, though they will be introduced here briefly. Refer to HindSight Help for additional information regarding these and other software features. The Menu bar at the top of the window is the primary access point to all other areas of the software. The most commonly used functions and tools are available in the Toolbar. Tool Tips are available in most areas, providing brief descriptions by holding the mouse pointer over the item or button. Right-Click Menus are available throughout the interface and provide fast access to some of the most commonly used commands. The menus change depending upon where in the software you are performing the right-click. The best way to learn right-click menus is through practice. Advanced users will find the Keyboard Shortcuts very helpful. They use the CTRL and ALT buttons in combination with a letter on the keyboard to immediately activate a function or command. Refer to HindSight Help for a detailed description of the available shortcuts. Several Export Options are available in the Main window that enable you to transfer information and events outside of the HindSight interface. Export to CSV creates a text file containing results from the grid in a comma delimited format. These can be easily opened in Excel. Export to AVI allows you to convert an event file from its native (.dce) format to a format (.avi) that can be viewed on most standard media players. Event enables you to send event files and data to others within the interface. DRC165-B Page 7 HindSight 20/20 v5.4.1 User's Guide

8 OBJECTS AND THE RESOURCE MANAGER All HindSight Objects are organized in the Resource Manager. This is a dedicated tool that enables users to view, add, edit, and delete HindSight Groups, Users and Roles, Vehicles and event recorders, and Event Movers. The Resource Manager is available through the Tools menu in the Main window. After you first install HindSight software, a system administrator typically begins working immediately in the Resource Manager preparing the system for use. These first steps involve creating a group hierarchy, adding users and roles, initializing event recorders and assigning them to vehicles. Step-bystep procedures and examples are provided in the HindSight Administrator s Guide. Once the system is up and running, the Resource Manager is used primarily by supervisors maintaining their assigned groups. Group folders enable you view all objects within a particular group. Users and their roles can be easily modified, moved, or deleted. Event recorder settings can be quickly changed and applied to the group or adjusted individually. Vehicles can be taken in and out of service. The following section provides general information about HindSight Objects and the Resource Manager. Specific details regarding adding and editing objects, as well as additional functionality within this window, are available in both the HindSight Administrator s Guide and HindSight Help. General Information The Resource Manager is divided into two main areas: the Group Panel (left) and Object Panel (right). The Group Panel displays the hierarchy of groups in the database. Multiple groups and subgroups may be added (i.e. subgroups, subgroups of subgroups, etc.). The structure is similar to adding folders and subfolders in Windows Explorer. The Object Panel at the right of the window displays the contents of whichever folder is highlighted in the Group Panel at the left of the window. As it is throughout the software, access to groups and objects in the Resource Manager is limited by the user s role. Administrators have full privileges. Supervisors can add, edit, move, or delete objects within the groups to which they are assigned and all of their subgroups. Reviewers and coaches can only view objects within the groups to which they are assigned. These privileges also apply to objects accessed through the Query View. Drivers and Move Managers cannot access the Resource Manager. You will also find a variety of useful shortcuts available in the Resource Manager, including contextsensitive Right-click menus, Toolbar buttons and Keyboard Shortcuts. Drag-and-drop operations of objects in the Resource Manager are commonly used, and are in fact the easiest way to move objects between groups. See HindSight Help for detailed information. DRC165-B Page 8 HindSight 20/20 v5.4.1 User's Guide

9 HindSight Groups Organizing your fleet into groups and subgroups within HindSight allows you to easily manage a growing database of vehicles, users, and events. It also allows you to track performance at every level of your organization, pinpoint problem areas, and assign users responsible for managing specific groups. The approach you take toward building the group structure depends upon the size of your fleet and the manner in which you would like to manage the workflow. Smaller organizations may keep everything together into a single top-level group. Larger organizations may divide their groups into subgroups based on location, vehicle type, or management accountability. The HindSight Administrator s Guide provides numerous examples and sample scenarios dealing with these objects in the Resource Manager. By default, each group contains five object folders: Event Movers Event Recorders Roles Users Vehicles DRC165-B Page 9 HindSight 20/20 v5.4.1 User's Guide

10 Users and Roles Although displayed separately in the Resource Manager, HindSight Users and Roles are inseparable components. Each person exists in the system as one user in one default home group. Each user may then be assigned one or many roles in one or many groups. Users are added to the system by first assigning them to a Default Group. A variety of identifying information and at least one role is entered into the User Properties window. For example, the user Tom has been added to the default group Atlanta in the image above and assigned the role of Driver in the same group. Highlight the Users (Default Group) in the Resource Manager to see this user. Highlight Roles to see this user s driver role (next image). Now assume this user is also a supervisor. Open the User Properties window and Add the role of Supervisor in the same group. Highlight Roles to now see both of this user s roles (next image). Either of these roles could be moved to a different group without moving the user from his default group. Note: It s important to understand and control the level of access (privileges) that each assigned role allows the user. See page 35 for a full list of user privileges. DRC165-B Page 10 HindSight 20/20 v5.4.1 User's Guide

11 This simple example illustrates the relationship between HindSight Users and Roles. An individual user assigned to a default group may be a driver and supervisor in one group, a reviewer in another, or any other combination. Refer to HindSight Help for more detailed information and examples. For users given a login, a User Name, Password, and User Role are all that are required to add the user to the system. For users not being given a login, an Employee Number and User Role is all that is required to add them to the system. The remaining selections are optional. Selecting the Enable User Login checkbox activates the User Name and Password fields. These are used to log on to the software and should be unique to each user. Users can change their own passwords after they log on. The user name identifies the user in the Resource Manager. Users who have not been assigned a user name are identified by their employee number. The First and Last Name identify the user during event review. These are also common identifiers in other areas. The remaining fields (start date, end date, birth date, shift, and gender) can be useful as search criteria (filters) in the Query View and in sorting columns of users in the Results Grid. The DriveCam Card Id is used with the optional RFID card reader installed in the vehicle. See page 51. DRC165-B Page 11 HindSight 20/20 v5.4.1 User's Guide

12 Event Recorders DriveCam Event Recorders are not added to the database in the same manner as other HindSight Objects. That is, you do not simply create them as you would a user or vehicle. Each event recorder must be physically connected to the system via USB connection to an Event Mover. This is referred to as Initializing Event Recorders and is described in the HindSight Administrator s Guide. Initialization only needs to be completed once for each event recorder. Event recorders will then be displayed in the Resource Manager, labeled with their 8-digit serial number. This cannot be changed. It is printed on each event recorder and marked on every event captured with the event recorder. DC3 & DriveCam II Event Recorders HindSight software supports two different event recorder models: DC3 & DriveCam II. Both are displayed with the same icon in the Resource Manager. Use the serial numbers to tell the two models apart (page 15). Additional parameters are available in the Query View that can be used to identify and separate the two models from one another. Serial numbers for DC3 Event Recorders begin with ER followed by a 6-digit code (e.g. ER0000E7). Serial numbers for DriveCam II Event Recorders use an 8-digit number (e.g ). DRC165-B Page 12 HindSight 20/20 v5.4.1 User's Guide

13 Once an event recorder has been added to the database, it can be assigned to a vehicle. This is discussed in the next section and detailed in HindSight Help. By default, event recorders are placed in the same group as the Event Mover on which they were initialized. After that, they can be moved to any group displayed in the Resource Manager, with or without their assigned vehicle, by simply dragging and dropping them in the new group assignment. All events will be downloaded into the group to which the event recorder is assigned. To view or edit the properties of a particular event recorder, double-click the event recorder icon in the Resource Manager. As with all other objects, the properties can also be accessed from the Query View. The four tabbed sections of the Event Recorder Properties window allow you to view and modify the settings affecting the way each individual event recorder functions within the vehicle. Trigger settings affect activation and sensitivity of the event recorder. Wireless settings affect the connection and download of Wireless Event Recorders. Audio/Video settings affect the properties of captured events. Time Zone sets its time. The tabs are identical to those of the Event Recorder Defaults, which are part of the Group Settings. Making changes in the Event Recorder Properties window applies only to one event recorder. Making changes in the Event Recorder Defaults window can be applied to many event recorders. An example is provided on page 42. See page 18 for more information about Group Settings. The Event Recorder Properties Audio/Video Tab allows you to set the parameters that affect how the audio and video portions of an event are captured for the selected event recorder. The Pre-Trigger Time, Audio, and Video Quality can also be set for multiple event recorders in the Group Settings (page 23). DRC165-B Page 13 HindSight 20/20 v5.4.1 User's Guide

14 Event Recorder Properties and the Audio / Video Tab 1 Group: The group to which the event recorder is assigned. 2 Serial Number, Model, & Firmware: Identifying information for the event recorder (see page 15). 3 Safety Mode & Stealth: Allows you to trigger safety events through DriveCam s Safety Enhancement Module (SEM). These settings must be configured in the event recorder prior to installation. See page 44 for more information. The other Record Modes in this window are discussed on the previous page. 4 Pre-Trigger Time: Defines how many seconds will be saved before the event trigger. The event recorder is continually recording and erasing data in a continuous loop. When an event is triggered, the event recorder immediately saves the 10 seconds before the trigger and then continues to record and save the 10 seconds after the trigger (default settings). These values can be changed. For example, if the Record Mode is set for 20 seconds and the Pre-Trigger Time is set for 25%, the recording will include 5 seconds before the trigger and 15 seconds after. The default value is a 50% split. 5 Audio Enabled: Switch audio recording on or off. The default setting is enabled (select the check box). 6 Video Quality: Affects compression (size) of events stored in the event recorder. A low setting allows more events to be stored in the event recorder prior to download but also lowers the quality of the recording. The default value of High is appropriate for most users. 7 Delete Event Recorder: Allows you to remove the event recorder from the system. When the button is clicked, you will be prompted to delete just the event recorder, delete both the event recorder and the vehicle, or cancel. 8 Connection Times: Displays the first and last time the event recorder was connected to the system. 9 Event Recorder Logs: Allows you to view connections and changes that have been made to the event recorder. DRC165-B Page 14 HindSight 20/20 v5.4.1 User's Guide

15 Identifying DC3 & DriveCam II Event Recorders in the Resource Manager The Event Recorder Properties windows shown below are from two different event recorders. These are also shown (at the bottom right) listed in the Query View. DRC165-B Page 15 HindSight 20/20 v5.4.1 User's Guide

16 DriveCam Vehicles Vehicles are managed separately from event recorders in the database. You may add or edit vehicles at any time, with or without their event recorders installed. The settings for each vehicle are displayed in the Vehicle Properties window, including its group assignment and most recent connection time. A detailed history of vehicle connections and database modifications can be viewed in the Vehicle Logs. The Vehicle ID is the primary label for the vehicle in the system and is all that is required to add a new vehicle to the database. It is used to associate drivers and events with a vehicle throughout the system. The License Plate and Vehicle Type are optional, though useful as search criteria (filters) in the Query View and sorting columns of vehicles in the Results Grid. Select a vehicle type from the list or Add your own custom vehicle type. Refer to HindSight Help for information about adding custom vehicle types. Once you know which Event Recorder will be (or has been) installed in the vehicle, assign it to the vehicle by selecting its serial number from the list. All events downloaded from the event recorder will be labeled with this Vehicle ID. The Last Driver assignment is a useful function during event review. When selected, all events downloaded from the vehicle are automatically assigned to this driver. See page 18 for more information. DRC165-B Page 16 HindSight 20/20 v5.4.1 User's Guide

17 Event Movers Event Movers are computers upon which HindSight Event Mover software has been installed. They are the first computers to receive events downloaded from event recorders (via USB, wireless or cellular connection) and then transfer the events to the database for review. Adding an Event Mover to the system involves two distinct steps. First, an Event Mover is created in the Resource Manager. This involves assigning a unique Event Mover Name and Password. Next, the Event Mover software is installed on a computer at the location where event download will take place. It is configured to connect the system with the assigned name and password. This procedure is covered in the HindSight Installation Guide. Once an Event Mover has been properly installed and configured, it will be enabled and available to connect to event recorders. The Event Mover Properties window displays the basic information for the Event Mover, including its group assignment and computer upon which it is installed. Each Event Mover has its own user interface, the HindSight Event Mover Monitor (EMM), available on each computer on which the Event Mover software is installed. The EMM provides information regarding the status of the Event Mover, Event Downloader Services, and the communication service connecting the Event Mover to the system. Use of the EMM is covered in the Event Mover Help file, available through the Help menu. DRC165-B Page 17 HindSight 20/20 v5.4.1 User's Guide

18 CONFIGURING GROUP SETTINGS Each group can be configured with its own set of preferences. These include settings for how the system tracks overdue tasks and how event recorders function within vehicles. The Group Settings windows are available through the Tools menu and can be edited only by administrators and supervisors. Establishing the right settings for your groups depends upon several factors, including your organizational structure and vehicle types. The default values are suitable for many organizations. Refining these settings is usually only accomplished through time and experience. To help you manage settings consistently, HindSight uses a concept called inheritance, represented by a gold or silver star next to the setting. Each setting can be inherited from its parent group and/or passed down to all of its subgroups. A gold star indicates that the setting has been inherited from (is the same as) its parent group. A silver star indicates that it has not. Refer to HindSight Help for information. General, Overdue Times, and Wireless Settings are applied directly from the Group Settings windows. To change the settings for a particular group, click to highlight the group in the left panel of the window, enter the selections, and click Apply. Event Recorder Defaults are applied in a three step process. Once changes are made in the Group Settings window, you must return to the Resource Manager and apply the new settings to the event recorders. Settings must then be uploaded to the event recorders. An example is provided on page 42. General Group Settings The General tab includes two options: allowing events to be deleted from the selected group and remembering the last driver who was assigned to a particular vehicle. DRC165-B Page 18 HindSight 20/20 v5.4.1 User's Guide

19 The Allow Deletes checkbox enables certain users to delete events from the database. This setting is useful for quickly eliminating non-driving related events. To delete an event, highlight it in the Main window or open it for event review and click the Delete button on the toolbar. The default setting is enabled. Deleted events cannot be recovered. See page 35 for a detailed description of who is allowed to delete events when this function is enabled. The Remember Last Driver in Vehicle checkbox is a useful function for reviewers. During event review, events are automatically associated with the vehicle in which the event recorder is installed, but the driver must be assigned from a list. When this option is selected, the system will remember the last driver that was assigned to a particular vehicle and automatically display the driver s name in association with the vehicle and the event. Reviewers should still verify that the correct driver has been assigned to the event the option to reassign a different driver will be available. This setting is useful for fleets that routinely have the same driver assigned to the same vehicle. The default setting is enabled. Event Recorder Defaults The Event Recorder Defaults tab includes are a variety of settings that affect the way event recorders function within vehicles. These are distributed across four additional tabs: Triggers, Wireless, Audio/Video, and Time Zone. Changes made to the Event Recorder Defaults will apply to all event recorders within the selected group. Changes can also be made that will affect only a single event recorder. See Event Recorder Properties on page 12 for more information. Triggers The Event Recorder Defaults Triggers Tab allows you to define the threshold values and trigger options for all event recorders within the selected group. Threshold values are sensitivity settings. DriveCam t-forces (trigger forces) are much the same as g- forces (gravitational forces), in that they describe the force being exerted on the vehicle. If the amount of force exceeds the threshold value, the event recorder will trigger and record an event. The Shock Trigger Threshold defines the t-force level for a shock trigger from any direction. Shock triggers are most often caused by hard impacts. If this level is surpassed, the event recorder will trigger an event and label it as shock. The default setting is DRC165-B Page 19 HindSight 20/20 v5.4.1 User's Guide

20 The Forward Trigger Threshold defines the t-force level required to trigger the event recorder in the forward or reverse direction. Forward triggers may be caused by hard braking or acceleration. If this level is surpassed, the event recorder will trigger an event and label it as erratic. The default setting is The Lateral Trigger Threshold defines the t-force level required to trigger the event recorder in the lateral (side-to-side) direction. Lateral triggers may be caused by hard cornering. If this level is surpassed, the event recorder will trigger an event and label it as erratic. The default setting is The Manual Trigger is the large red button on the bottom of the event recorder. When this button is pressed, the event recorder will trigger an event and label it as manual. Manually triggering an event has many uses if the driver needs to record something happening inside or outside the vehicle at any time, all they have to do is press the manual trigger. The default setting is enabled. The Shock Filter lowers the event recorder's sensitivity to incoming data and helps to minimize the number of non-driving related events caused by stiff vehicle suspension or harsh vibrations in large trucks and buses. The event recorder will still record events at the set threshold values, but it will re-sample shock trigger forces over a broader sampling range, thus decreasing the number of events generated. The default setting is enabled. The External Trigger Polarity is used to control additional components connected to the event recorder (i.e. Remote DriveCam Button, PTM, Universal Module, GPS). Refer to the documentation for these optional components for information on how to set the External Trigger Polarity. For most users, the default setting of Low is appropriate. Finding the ideal settings for vehicles in your fleet requires that your organization test the settings by driving the vehicles and determining which settings accurately define their expectations for how the vehicle should be driven. DRC165-B Page 20 HindSight 20/20 v5.4.1 User's Guide

21 Wireless The Event Recorder Defaults Wireless Tab allows you to set the parameters used to upload settings and download events to and from Wireless DriveCam Event Recorders within the selected group. * * * These settings do not apply to DC3 Event Recorders configured for cellular download * * * The Initial Contact Interval is the amount of time that will pass before the event recorder will attempt to make first contact with an Event Mover to download a saved event. If the Event Mover is unavailable, the event recorder will try again after 15 seconds and continue trying at progressively increasing intervals until the Maximum Backoff Interval is reached. This prevents the event recorder from depleting the vehicle battery when it is away from the Event Mover for an extended period of time. For example (assuming the default values of 15 seconds and 4 hours for the initial contact interval and max backoff interval, respectively), an event recorder with a stored event will attempt to connect with an Event Mover after being motionless (see motion detection below) for 15 seconds. If it cannot find a signal, it will try again after 30 seconds, then again after a minute, two minutes, four minutes, etc. up to 4 hours and then every 4 hours after that. If the vehicle begins moving during this time, the process will immediately restart when the vehicle comes to a stop (drops below the motion detection threshold) and remains there for 15 seconds. These settings ensure that events download as soon as the vehicle comes into range of an Event Mover. The default values are appropriate for most users. The Maximum Contact Interval is the amount of time that will pass before the event recorder (without a stored event) will attempt to connect with the Event Mover to retrieve any uploads that may be available. The start time for countdown of the maximum contact interval is reset each time a connection is established though the value remains constant. DRC165-B Page 21 HindSight 20/20 v5.4.1 User's Guide

22 For example, (default time = 24 hours) an event recorder without an event will wait 24 hours before it tries to connect with the Event Mover. If it is unable to establish a connection (offsite), the event recorder will try again after 15 seconds and continue trying at progressively increasing intervals until the Maximum Backoff Interval is reached and again, will restart the process each time the vehicle comes to a stop (see above). The hour and minute that it finally establishes a connection resets the time for the next connection 24 hours later. In this case, even if the vehicle is offsite when its max contact interval is reached, it will establish a connection after 15 seconds of being parked within range of the Event Mover. It also automatically aligns itself with the times that the vehicle is typically parked within range of the Event Mover. This ensures that the event recorder is always up to date with the latest settings. The default values are appropriate for most users. However, the max contact interval should be less than the Vehicle Overdue Status. The Authentication Tolerance is a security feature used to verify that both the event recorder and the Event Mover are valid (belonging to your network). If their time stamps are out of sync by more than the value set in the Maximum Tolerance, a connection will not be established. The default value of 60 minutes is appropriate for local companies. If your vehicles routinely cross time zones, the value should include a 10 minute margin of error in addition to the time change. For example, if your vehicles cross one zone set the maximum tolerance to 70 minutes, two time zones = 130 minutes, three time zones = 190 minutes, etc. Motion Detection settings define the amount of vehicle movement that will be tolerated before an event recorder will attempt to make contact with an Event Mover. The forward and lateral settings (T-Forces) are identical in function to those influencing DriveCam Triggers. If the event recorder senses movement greater than the threshold values, it will not attempt to establish a connection with the Event Mover until the values drop. It is intended that vehicles be parked before they try to connect with the Event Mover to download events or to upload new settings. However, once a connection is established, it will continue even if the vehicle begins moving. The default values are suitable for most small vehicles, enabling connections when the vehicle is running. However, vehicles with a rough or shaky idle may require higher settings. The Connect to Event Mover field displays the IP Address and the Port Number for the Event Mover. The format of the IP Address is written as 4 numbers separated by periods. These fields are unique to each network and must be entered manually. Consult your system administrator for the information to be entered. DRC165-B Page 22 HindSight 20/20 v5.4.1 User's Guide

23 Audio and Video The Event Recorder Defaults Audio/Video Tab allows you to set the parameters that affect how the audio and video portions of an event are captured within the selected group. The Pre-Trigger Time defines how much data will be saved before the event trigger. The event recorder is continually recording and erasing data in a constant loop. When an event is triggered, the event recorder immediately saves the 10 seconds (for example) before the trigger and then continues to record and save the 10 seconds (for example) after the trigger. These values can be changed. For example, if the record mode is set at 20 seconds and the pre-trigger time at 25%, the event will include the 5 seconds leading up to the trigger and the 15 seconds following the trigger. The default value is a 50/50 split. The Audio Enabled checkbox allows you to switch the audio channel on or off during event recordings. Audio will not be recorded when this is disabled. The default value is enabled. The Video Quality settings affect the compression of event files stored in the event recorder. A lower setting allows more events to be stored in the event recorder prior to download. However, it also affects the quality of the recorded information. For most users, the default setting of best is most useful. Additional Record Modes can be set on a per vehicle basis. However, they cannot be changed from the Group Settings window. They must be changed one event recorder at a time. Most event recorders can be configured to record with the forward facing-camera, the rear-facing camera, or both. They may also be configured for 10, 20, or 30 second recordings. See Event Recorder Properties on page 12 for more information. DRC165-B Page 23 HindSight 20/20 v5.4.1 User's Guide

24 Time Zone The Event Recorder Defaults Time Zone Tab allows you to set the time zone for all event recorders within the selected group. This affects the time stamp on events. Overdue Times The Overdue Times tab allows you to set the amount of time before a particular item or task is marked as "overdue" in the database. These include overdue events, vehicles, and Event Movers. Overdue events are highlighted in the Event View and summarized on the lower status bar. All overdue items can be reported through HindSight Reports. DRC165-B Page 24 HindSight 20/20 v5.4.1 User's Guide

25 To get the most out of the DriveCam System, unsafe driving behavior must be identified and corrected before it leads to an incident or injury. In other words, when a driver triggers an event, it must be downloaded from the vehicle and reviewed for driving errors. If driving errors are found, then the driver must then be coached so that the unsafe behavior is not repeated. This process is most effective when the driving events are still fresh in the mind of the driver. For this reason, tasks such as event review and coaching are tracked in the database with overdue times. When enabled, the system will notify you when a particular task has not been completed within the set time frame. The amount of time that you allow to pass before a particular item is marked as overdue depends upon your workflow and personal preferences. Refer to the HindSight Admin Tools and the Admin Tools Help file for additional information about setting the overdue times. Vehicles Overdue for Download: When a driver triggers an event, it remains stored in the event recorder until it can be downloaded through a USB or wireless connection to the Event Mover. When enabled, the system will notify you when a particular vehicle has not connected to an Event Mover in the specified amount of time. Set vehicles to Out of Service in the Vehicle Properties window, if they will not be driven or are unable to connect to the Event Mover for an extended period of time. This will prevent them from being counted as overdue. Event Movers Overdue for Connection: After an event is downloaded from a vehicle, it is stored briefly in the Event Mover until it can be transferred across the local or wide area network to the HindSight Database. Most of the time, this transfer is immediate. However, if the network connection is disabled, events will remain in the Event Mover. When enabled, the system will notify you when a particular Event Mover has not connected to the database in the specified amount of time. By default, Event Movers will attempt to connect to the database every 10 minutes. Check the Event Mover Monitor (page 17) and Help file installed on the HindSight Event Mover computer for details and troubleshooting. Events Overdue for Review: When an event enters the database, it is marked as "New" until it is analyzed by a reviewer and either resolved immediately or marked for coaching. When enabled, the system will notify you when a particular event has not been reviewed in the specified amount of time. Events Overdue for Coaching: When an event is marked for coaching, the driver must either be selfcoached or coached face-to-face before the event can be resolved. When enabled, the system will notify you when a particular event has not been coached in the specified amount of time. DRC165-B Page 25 HindSight 20/20 v5.4.1 User's Guide

26 Wireless Settings The Wireless Settings tab includes security settings for the wireless local area network(s). They apply to groups using wireless download of their event recorders. Consult with your organization s IT Resource for information to be entered into this window. * * * These settings do not apply to DC3 Event Recorders configured for cellular download * * * The Service Set Identifier (SSID) is the name of the wireless local area network (WLAN). All Wireless Event Recorders attempting to connect to a specific WLAN must use the same SSID. The system supports one SSID for the entire system. This is configured during registration and cannot be modified in this window. The Wired Equivalent Privacy (WEP) Key is a security protocol for the wireless local area network (WLAN) defined in the standard. WEP is designed to provide security by encrypting data over radio waves so that it is protected as it is transmitted to and from the Wireless Event Recorder to the Wireless Access Point and Event Mover. The WEP Key is the only editable parameter available within this window. Enter the WEP Key for your WLAN. Each group may be configured with its own WEP Key. DRC165-B Page 26 HindSight 20/20 v5.4.1 User's Guide

27 REVIEWING EVENTS The Event Review window is the cornerstone of the HindSight System. Within this window, reviewers analyze, coaches teach, and drivers learn from recorded events. Consistent, timely, and effective event review and coaching is the key to a successful program. Event review takes time to learn and master. Sometimes unsafe driving behavior is easy to identify. Other times it is not. Often there are many subtle clues, all of which must be carefully considered in order to determine the series of events that caused the event recorder to trigger. The first step in event review is to watch the video playback. This is often all that is necessary to determine the underlying cause of the event. If more information is required, you can use the event graph. The driver s personal account of the event should also be carefully considered. DRC165-B Page 27 HindSight 20/20 v5.4.1 User's Guide

28 Following review, events should be scored immediately and a course of action selected. If the event is concerning then the driver should be made aware of it and told why the behavior is not acceptable. This can be done face-to-face with a coach or simply sent to the driver for self-coaching. * * * Timely and effective coaching of the driver is critical to the success of the program * * * Opening Events Events are opened from the HindSight Main window and access is limited to only those users with the appropriate privileges. Drivers can log on and open their own events only after the event has been reviewed. They cannot change the event details except to add their own notes. Reviewers, coaches, and supervisors can open events only from their own groups. See page 35 for a full list of user privileges. To open a single event, simply double-click the event in the Results Grid (page 4). To open multiple events, Shift-click or Ctrl-click to highlight the events in the grid. Then click the Open button on the toolbar. The first in the series of selected events will be opened in the Event Review window and playback started. To scroll through multiple events, click the Next and Previous buttons at the bottom of the Event Review window. The events will be played in the order listed in the Results Grid (opening a single event) or the order selected (opening multiple events). If no events are selected in the Results Grid, clicking the Next and Previous buttons will move through all events in the order listed in the Results Grid. All changes made to the event (scoring & notes) will be automatically saved when clicking through the Next and Previous buttons. Viewing Event Playback The Event Player uses a standard set of buttons and sliders to control event playback. Viewing the video component of the event is one of two ways to analyze and interpret the behaviors that caused the event and is by far the most common. See page 37 for more information regarding event playback. There are several viewing options for events. Click the Expand Video or Hide Graph buttons to maximize the display. Use the Step Forward and Rewind buttons to scroll through the event frame by frame. Each frame is equal to (approximately) one-quarter of a second. The forward (FWD) and lateral (LAT) trigger-forces at each time frame are shown just below the video. These values will be highlighted each time the forward and lateral trigger thresholds or the shock trigger threshold is crossed. Vehicle speed will also be displayed when captured. The time ranges from -10 to 0 to +10 seconds for most events. However, these values can be changed. See page 12 for more information regarding changing the recording time of events. DRC165-B Page 28 HindSight 20/20 v5.4.1 User's Guide

29 DC3 Event Recordings & DriveCam II Event Recordings HindSight software supports two different event recorder models: DC3 & DriveCam II (see page 15 for more information). Viewing event playback and the event graph will look slightly different depending upon which model the event was recorded. These differences have very little impact on how the system is used and is typically only noticeable if your fleet is using a combination of these two event recorder models. The descriptions below point out where you might see these differences and why. Within all event recorders are sensors that detect movement in the forward/reverse (FWD) and left/right (LAT) directions. When enough movement is detected in a particular direction (i.e. when the trigger threshold is reached), an event will be recorded. The sensitivity of these sensors can be changed (page 19) so that the event recorder will trigger at a higher or lower level of movement (i.e. raising or lowering the trigger threshold). These thresholds differ slightly between the two event recorder models. DC3 Event Recorders and DriveCam II Event Recorders use the same type of sensors. However, each calculates the trigger threshold in a different way. The DriveCam II will trigger an event when either the FWD or the LAT threshold is reached. The DC3 will trigger an event when a combination of the FWD and LAT thresholds is reached. Therefore, you may notice during event playback that DC3 event recordings are often triggered before the individual FWD or LAT thresholds are actually reached. For example, two event recorders (DC3 & DriveCam II) may both have their FWD and LAT threshold values set to The DriveCam II will record an event when either the FWD force reaches this value or when the LAT force reaches this value. This will be seen during event playback as the FWD or LAT values are highlighted yellow each time the threshold (0.60) is reached. When viewing DC3 event recordings, you may notice that the event was triggered even though the FWD and/or LAT values display a lower value than the threshold. This is because the DC3 calculated the threshold by combining the FWD and LAT movement together. These differences can also be seen in the Event Graph. Using the Event Graph The upper portion of the window contains the Event Graph. The graph provides you with a visual representation of the forward and lateral trigger-forces experienced throughout the duration of the event. The graph uses the same controls that are used to view the video component of the event. Click the Show / Hide Graph button to toggle the display. Position the cursor over the bottom frame of the graph and drag the border to expand or reduce its size. Options in the graph toolbar allow you to modify the information displayed. See page 38 for more information and a tutorial interpreting a graph. The Event Graph can provide you with a great deal of information regarding the movement of the vehicle and the actions of the driver during the event. DRC165-B Page 29 HindSight 20/20 v5.4.1 User's Guide

30 Interpreting and Scoring the Event IMPORTANT: Event review and scoring is only one-half of the process. Without timely and effective driver coaching, this process will not produce the desired results. The approach you take toward event analysis is entirely up to you. Reviewers typically start by watching the full length of the video, carefully observing both the forward and reverse views. If needed, use the Event Graph to provide additional details. The goal is to determine the event s underlying cause. Was the event caused by the driver or by someone else? If the event was caused by the driver, what were the behaviors or circumstances in the seconds leading up to the trigger that led to the event? It s also important to recognize that even if the event was not caused by the driver, was there something more that the driver could have done to avoid the event? And most importantly, if unsafe behavior is observed, can it be changed before it leads to a serious incident? Following event review, you should immediately proceed with event scoring, clearly defining all of the causes of the event and recommending ways to improve. Once an event has been scored and additional notes entered, a course of action is selected. Identify and assign a driver to the event. Select an event trigger and outcome. Use the checkboxes to identify all root causes, risky actions, and other related information. Enter your own personal notes to help the driver clearly understand the problem. Select a course of action (face-to-face coaching or self-coaching) or simply resolve the event. Selections carry an event score ranging from 1-10 Points. Event Score totals are listed at the bottom of the window and can be summarized in reports. When properly reviewed, a driver s event score can be a key indicator of their driving skills, especially when averaged over time. All information entered into the Event Review window is saved in the database as a permanent record of the event s details. Events can be reopened and viewed at any time by users with the appropriate privileges and users may edit their notes at any time. However, once an event has been resolved, its score can no longer be changed. A copy of the event can be saved to a location outside the system in its original (*.dce) format or exported to a standard (*.avi) format. The first of these will preserve all of the original data recorded with the event; the second will preserve only the date, time, serial number, and trigger forces; neither will preserve any of the information entered into the Event Review window. This information can be exported only through reports or ed to others within the system. Refer to HindSight Help for more information. DRC165-B Page 30 HindSight 20/20 v5.4.1 User's Guide

31 Viewing Event Properties Click the Event Properties icon information associated with the event. at the bottom of the Event Review window to see additional Much of this information can also be viewed in columns of the Results Grid in the Query View and Event View (page 4). This allows you to sort and filter the list of events based upon many of the parameters shown in the window above. For example, in the Results Grid you can: Search the database for all events with an event score greater than a certain value. Sort events based on their Record Date, Review Date, or Coach Date. Sort events based upon their driver, reviewer, or coach. The information can be exported from the Results Grid and opened in another spreadsheet program, such as Excel. Refer to HindSight Help for more information. Location & Heading This is the speed, heading, and location information at the time the event was recorded. These features are obtained through DriveCam s optional GPS and OBD modules. Contact DriveCam for information. DRC165-B Page 31 HindSight 20/20 v5.4.1 User's Guide

32 Understanding the Event Workflow All events entering the HindSight system follow a clearly defined lifecycle from New to Resolved. This is tightly controlled by the system to ensure program integrity. All events start with a driver triggering an event which is then downloaded to the system: The event is displayed in the Results Grid and listed as New. A reviewer assigned to the group reviews and scores the event and selects a course of action. If the event is of no concern, the reviewer sets the course of action to Resolved and the cycle is complete. No further action is required. If the event is of low concern, the reviewer can set the course of action to Self-Coaching and the event will be placed back in the Results Grid with this status. It is now the driver s responsibility to learn from and resolve the event. It is also the first opportunity the driver has to view the event. During the self-coaching process, the driver watches the event and reads the reviewer s comments and scoring. The driver cannot make any changes to the event except to add their own comments. When the driver closes the event, its status is automatically changed to Resolved and the cycle is complete. If the event is of high concern, the course of action is set to Face-to-Face Coaching and it is placed back in the Results Grid with this status. It is now the coach s responsibility to resolve the event. During the coaching session, the driver and coach meet to review the event. The coach explains why the event was unsafe or unacceptable behavior and when satisfied that the driver understands the error and will not repeat it, the event can be resolved. Both the coach and the driver may each enter their own notes regarding the event and the topics discussed during the coaching session. These will be saved with the event file. An Event Detail and Coaching Report can be sent to the supervisor or placed in the driver s file. Finally, the coach changes the status to Resolved and the cycle is complete. The event lifecycle helps you maintain the integrity of the system by ensuring that all events are reviewed and coached in the proper manner. See page 35 for a list of user privileges (who can do what and when). DRC165-B Page 32 HindSight 20/20 v5.4.1 User's Guide

33 REPORTING RESULTS HindSight features a powerful array of reporting capabilities that allow you to quickly analyze data across your organization. For convenience, specific reports are available from various locations around the interface, through toolbar buttons and right-click menus, depending upon the object in focus. All reports are available through the Tools menu in the Main window. HindSight Reports share many of the same general settings, available in the Report Criteria window. For most reports, start by selecting the group and the date range to report upon. Depending upon the report type, there may be additional selections (driver, event recorder, etc.). Reports can be printed directly or exported to several different formats, including Crystal Reports (*.rpt), Adobe Acrobat (*.pdf), Microsoft Excel (*.xls), Microsoft Word (*.doc), and Rich Text Format (*.rtf). * * * Refer to HindSight Help for detailed information and sample reports * * * DRC165-B Page 33 HindSight 20/20 v5.4.1 User's Guide

34 Driver Reports The Driver s Event History Report lists the details of events assigned to a driver over a specific time range. It includes the event score and event trigger for each event and the driver s event score average. The Driver Report Card complements this by displaying the driver s event information in a series of charts. The top six root causes of events triggered by the driver and the fundamental unsafe driving behaviors are listed. The Event Details and Coaching Report lists all of the details gathered for a specific event during initial review of the event and coaching of the driver. It provides you with a quick snapshot of an event s details without having to retrieve the event from the database. The Good Driving Award can be a welcome complement to any driver and can be a useful part of the driver s personal records. Group Reports The Cause Analysis Report summarizes all event causes for an entire group over a specific time frame. The report lists all of the possible root causes and the frequency with which they occurred. This can be extremely useful in identifying problem areas within your organization. The Group Report Card complements this by displaying key indicators of problem areas in a several easy-to-interpret charts. For any given group of vehicles and drivers, the report displays the event frequency, average event score, and total event score over time. Also included are the top six root causes of events and unsafe driving behaviors exhibited by the group. Overdue Reports Overdue Reports help you to monitor system performance by summarizing all overdue items and tasks in the database. The Vehicles Overdue for Download Report lists all vehicles and event recorders that are currently overdue for download. The Events Overdue for Review Report and Events Overdue for Coaching Report list all events that are currently overdue. Overdue Reports should be generated regularly to help you keep track of these items and to identify critical issues that may need to be addressed within your organization. See page 24 for detailed information about setting overdue times. Installation and Error Logs The Installation Verification Report provides you with a list of all event recorders that have been installed and the date they were first connected to the system. The Event Recorder Error Log allows you to view connection information associated with a particular event recorder. These include information, error, and warning messages, enabling you to track down details, problems, and tampering. DRC165-B Page 34 HindSight 20/20 v5.4.1 User's Guide

35 A1: EVENT WORKFLOW RULES HindSight incorporates a strict code of event workflow rules that govern who is allowed to access an event, when they are allowed to view or edit an event, and what they are allowed to do to the event. The event workflow rules are quite complex. The ability to act on an event depends upon both the user s role and the status of the event. The following will outline the rules and provide some examples. With the exception of administrator, each role is applied to a user for a specific group. The privileges that a role provides to a user extend from the group in which the role was assigned down through all of that group s subgroups. That is, if a user has the role of reviewer in group A then that role applies to group A and its subgroups only. The role of reviewer for this user does not apply to group B (unless group B is a subgroup of group A). Event Workflow Rules for Drivers Drivers may only see events for which they are the assigned driver. Drivers may not see new events (they must wait for the event to be reviewed). Drivers may not change an event s course of action unless the event s status is self coaching. Drivers may always edit the driver notes for events that are not new. Drivers may not delete events. Event Workflow Rules for Reviewers Reviewers may only see events within groups to which they have been assigned. Reviewers may edit events that are new. Reviewers may not edit events with statuses that aren t new unless the same reviewer was the last person to edit the event. Reviewers may not edit events for which they are the driver. Reviewers may not move events to different groups. Reviewers may not edit the driver or coach notes. Reviewers may not delete events. Event Workflow Rules for Coaches Coaches may edit events that are not new. Coaches may not edit events for which they are the driver. DRC165-B Page 35 HindSight 20/20 v5.4.1 User's Guide

36 Coaches may not edit events that are new. Coaches may not move events to different groups. Coaches may not edit the driver or coach notes. Coaches may not delete events. Event Workflow Rules for Supervisors Supervisors may edit or delete (when enabled) events with any status only in groups for which they are the supervisor. Supervisors may not edit or delete events for which they are the driver. Supervisors may move events to other groups as long as they have privileges in both groups. Supervisors may edit the reviewer or coach notes. Supervisors may not edit the driver notes. Event Workflow Rules for Administrators Administrators may edit, delete (when enabled), or move events with any status in any group. Administrators may not edit or delete events for which they are the driver. Administrators may edit the reviewer or coach notes. Administrators my not edit the driver notes. DRC165-B Page 36 HindSight 20/20 v5.4.1 User's Guide

37 A2: VIEWING EVENT PLAYBACK The following section supplements the information provided on page 28. These are intended as suggestions only. The approach you take toward event review is up to you. Gather Observable Facts Is the driver wearing a seatbelt? Is the driver talking on a telephone? What are the traffic, road, and weather conditions? What are the local traffic laws? Can you see traffic signs or signals in video? Isolate Primary Driving Errors Carefully observe the driver and look for the following: Not paying attention to the road or showing poor observation skills such as a blank stare, not looking far enough ahead, not scanning the roadway or intersection, not checking the mirrors or blind area before changing lanes, following too close. Determine the Following Distance Pick an external marker in the video such as a pole, mailbox, or tree. Stop the video at the moment the rear of the vehicle ahead crosses the marker. Then, click the frame-by-frame button until the front of your vehicle crosses the marker. Each frame is equal to one-quarter of a second. Therefore, four clicks of the button are equal to (approximately) one second. A safe following distance is 2-4 seconds (or more). Determine the Driver's Reaction Time Find the external signal in the video to which the driver reacts (a changing stoplight or the activation of brake lights on the car ahead). Stop the video at the moment the external signal is clearly visible. Then, click the frame-by-frame button until the driver reacts (hitting the brakes or swerving to avoid). This will typically be the moment the event is triggered. Alternatively, you can use the event graph to determine when the brakes were hit as the forward t-forces will quickly drop to a negative value. Each frame is equal to one-quarter of a second. Therefore, four clicks of the button are equal to (approximately) one second. An alert driver will have a typical reaction time of (approximately) threequarters of a second. DRC165-B Page 37 HindSight 20/20 v5.4.1 User's Guide

38 A3: USING THE EVENT GRAPH (TUTORIAL) The following section describes the elements of the event graph. A tutorial on the following page further illustrates interpretation of the graph. The graph shown below is from a DC3 Event Recorder. The X-Axis is Time (seconds) The vertical line in the middle of the graph (time = 0) marks the moment the event was triggered. The left side of the graph (time = -10 to 0 seconds) shows the 10 seconds leading up to the trigger. The right side of the graph (time = 0 to +10 seconds) shows the 10 seconds following the trigger. Most events are 20 seconds long, though some can be 30 seconds (page 12). The Y-Axis is Force (t-force) The jagged red line indicates the forward t-forces experienced during the event. The jagged blue line indicates the lateral t-forces experienced during the event. A yellow line can also be displayed to show the audio track. DriveCam II event recordings display two solid (colored) horizontal lines above and below the centerline. These mark the t-force threshold values set for the event recorder (page 19). The graph shown above is from a DC3 event recording in which the threshold values are not displayed. Positive and Negative Values The forward and lateral t-forces can have both positive and negative values. Positive (+) forward values indicate acceleration. Negative (-) forward values indicate braking. Positive (+) lateral values indicate right turns. Negative (-) lateral values indicate left turns. Applying a Filter The default filter used by the graph is determined by the event's trigger. DriveCam II event filters can be changed to apply a different level of sampling to the data. Select a filter to apply from the drop-down menu on the lower toolbar. The filter options are: shock, erratic, and roughness. Filters cannot be changed for events recorded on DC3 event recorder models. See page 15 for more information about the differences between the two event recorder models. DRC165-B Page 38 HindSight 20/20 v5.4.1 User's Guide

39 Interpreting the Event Graph (tutorial) The event graph shown below is that of a driver making a fast left turn off the road and into a parking lot, triggering the event recorder at the moment the vehicle hit the dip leading into the parking lot. The value of the lateral t-force at time zero (negative blue spike at time zero) is greater than the threshold value it was this spike that triggered the event. The data before and after time zero also shows several spikes in both forward (red) and lateral (blue) t-forces. Notice the red line (forward t-forces) in the region between time minus seven seconds and time minus three seconds it drops down to a negative value, indicating that the driver was beginning to slow down to prepare for the turn. The blue line (lateral t-forces) in the region between time minus three seconds and time zero drops down to a negative value, showing the driver making a left turn into the parking lot. Notice also the red line (forward t-forces) beginning to move up at time minus three seconds the driver is accelerating into the turn and into the parking lot. This is aggressive driving. You can clearly see the driver slowing (red line) and over-correcting slightly to the right (blue line) after moving into the turn lane at time minus seven seconds. Also clear is the hard left turn (blue line) while accelerating (red line) into the parking lot at time minus three seconds. Using the event graph can provide you with information that is not easily seen during playback of the video portion of the event. Accelerating into the turn, for example, is not easy to identify in the video. Not all event graphs will be easy to interpret and it typically takes a little time before reviewers learn to identify the fine details of driver and vehicle behavior that the graph provides. The graph should always be used as a complement to the video portion of the event and will help ensure accurate analysis. Can you see more detail in the graph? The driver is moving steadily (-10 to -8) then pulls left slightly into the middle turn lane (-8 to -7) and has to over-correct, pulling to the right to straighten out (-7 to -4) while slowing. The driver begins his turn while continuing to slow (-4 to -3) and then begins to accelerate. The vehicle enters the parking lot at an angle as seen by the lateral (blue) body roll (-1 to 0) which increases until crossing the lateral threshold and triggering the event. A half second later the forward threshold is crossed as the vehicle jumps up after hitting the dip leading into the parking lot. The driver swerves slightly to the right (+5), hits a small dip (+7), and then turns left (+9). DRC165-B Page 39 HindSight 20/20 v5.4.1 User's Guide

40 A4: INTERPRETING AND SCORING THE EVENT The following section supplements the information provided on page 30. These are intended as suggestions only. The approach you take toward event review is up to you. Refer to HindSight Help for more detailed information regarding these parameters. Identify the Driver Assign a driver responsible for the event. Selections are available in the drop-down menu to the left of the Event Review window. If a driver assignment is already made, verify that it is the correct driver shown in the video. Drivers can be assigned to specific vehicles (page 16) and the system can be configured to remember the last driver assigned to a vehicle (page 19). Select an Event Trigger All new events are marked Not Specified. The scoring criteria are grayed out (not accessible) until an event trigger is selected. Select one of the option buttons to continue. Options: Hard Cornering, Hard Braking, Hard Acceleration, Collision, Rough/Uneven Surface, Other. Select an Outcome The outcome of the event should always be noted before the event is saved and closed. This allows you to track and organize events based upon their severity. It also allows for statistical reporting of driving behaviors, conditions, and their outcomes. Options: No Collision (default selection), Near Collision Unavoidable, Near Collision Avoidable, Collision, Wear and Tear. Score all Root Causes Distractions are common while driving. A driver s attention may be divided between driving, navigating, talking to another person, listening to the radio, and numerous other tasks. However, while distractions are often unavoidable, when they lead to an event trigger you are able to address them. Root causes are divided into three categories: Distractions: Cell Phone, Mapping/Navigation, Other Work Task, Food/Drink, Passenger, Other. Poor Awareness: Not Looking Far Ahead, Blank Stare, Not Scanning Roadway, Not Scanning Intersection, Mirrors Not Checked, Blind Area Not Checked. Demeanor: No Issue (default selection), Judgment Error, Somewhat Aggressive, Aggressive, Willful Misconduct, Drowsy/Falling Asleep. DRC165-B Page 40 HindSight 20/20 v5.4.1 User's Guide

41 As with all driving behaviors and distractions captured during the event, it is the responsibility of the reviewer to determine if it was a cause of the event and/or if it was careless or dangerous it may not be. We recommend that you have policies in place to address these common driving distractions. Mark all Risky Actions Drivers should be made aware of all actions that put themselves and others in jeopardy. Risky actions are divided into two categories: Seatbelts: Driver Unbelted, Passenger(s) Unbelted. Fundamentals: Following Too Close, Traffic Violation, Unsafe Speed, Failed to Keep an Out, Poor Lane Selection, In Other s Blind Area. Note all Adverse Conditions All factors that contributed to the event should be noted. Though none of these are the driver s fault, drivers need to understand that any time one of these factors are present, their focus on driving safely should be especially sharp. Options: Poor Visibility, Poor Road Conditions, Heavy Traffic. Select a Custom Event Detail Custom event details allow you to define your own set of safe driving parameters, customized to suit the unique needs of your organization. These are usually behaviors that occur regularly within your organization and which you would like to make available for event review and reporting. You may have up to five custom event details, each with a title, description, and event score. From the Tools menu in the HindSight Main window, select System Configuration to enter or edit custom event details. Common Selections: Construction Zone, Near School or Bus Stop, Unauthorized Use. Enter Your Notes The tabbed fields allow the driver, reviewer, and counselor to comment on this event in their own words. Notes can be selected for display in the HindSight window and printed with Event Detail and Counseling Reports. There is a maximum of 5000 characters that can be entered into each of these fields. Select a Course of Action This changes the status of the event, moving it through the event cycle. This should be the last selection made before saving and exiting event review. See page 32 for additional information and examples. Options: No Change, Self-Coaching, Face-to-Face Coaching, Resolved. DRC165-B Page 41 HindSight 20/20 v5.4.1 User's Guide

42 A5: INHERITING EVENT RECORDER SETTINGS (TUTORIAL) Changes made to the General, Overdue Times, and Wireless Group Settings apply immediately to the selected groups. However, changes made to the Event Recorder Defaults require a three step process: 1. In the Group Settings, select a group(s) and change the Event Recorder Defaults. 2. In the Resource Manager, apply the new settings to selected event recorders. 3. Connect to the event recorders to upload the new settings. The following tutorial will illustrate this process: Step 1 From the Tools menu in the Main window, select the Group Settings command. Step 2 Highlight a group (e.g. Boston) and select the Event Recorder Defaults >> Triggers tab. Step 3 Change the Forward and Lateral Threshold Values and click Apply. Referring to the images above, notice the gold stars next to the settings before making the changes. These indicate that the settings have been inherited from (are the same as) this group s parent group (e.g. ACME Transportation). After changing the forward and lateral values, a silver star is placed next to each setting indicating that these two settings are now different from their parent group. The Event Recorder Default settings have now been changed for the selected group. However, they have not yet been applied to the event recorders within this group. This is done within the Resource Manager. Exit the Group Settings window. DRC165-B Page 42 HindSight 20/20 v5.4.1 User's Guide

43 Step 4 From the Tools menu in the Main window, select the Resource Manager command. Step 5 Highlight the Event Recorders folder within the group (e.g. Boston). Step 6 Highlight only those event recorders to which you want the new settings to apply. Step 7 Click the Star button on the Toolbar. Step 8 Double-click each event recorder to see the new settings. In this example, the changes made in the Groups Settings window on the previous page were applied to three of the four event recorders within the Boston Group. The settings of the fourth event recorder have not been changed. Step 9 Connect the event recorders to an Event Mover to automatically upload the new settings. As you can see in the Event Recorder Defaults window and the Event Recorder Properties window, there are two separate paths to change event recorder settings. Making changes through the Event Recorder Defaults allows you to apply changes to many event recorders at once. Alternatively, changes can be made directly within the Event Recorder Properties window one event recorder at a time. DRC165-B Page 43 HindSight 20/20 v5.4.1 User's Guide

44 A6: SAFETY ENHANCEMENT MODULE SUPPLEMENT DriveCam s Safety Enhancement Module (SEM) enables users to trigger special events on event recorders through inputs other than the standard t-force driving events or manual triggers. These safety events may be triggered by a door opening or some other physical trigger or switch in the vehicle. The event recordings are snapshots of the interior of the vehicle and are designed to assist users with identifying passengers or other individuals who enter or exit the vehicle. How the SEM Works There are two components that must be in place in order to use the SEM feature. First, the event recorder must be configured with one of the SEM modes. This is set in the event recorder s firmware and cannot be modified by the user through the software. Second, the event recorder must be connected to at least one of the SEM trigger inputs within the vehicle (e.g. doors, switch, etc.). When properly configured, a safety event will be recorded each time one of the SEM triggers is activated. Vehicle doors are typically set as the primary trigger, recording audio and video of each passenger as they enter and exit the vehicle. A secondary trigger input can be connected to almost any other electronic device within the vehicle. Typically, this is connected to a concealed switch that can be silently triggered by the driver in an emergency. About Safety Events There are two different types of safety events: Safety (Open) and Safety (Closed). Each event recorded through the SEM will be labeled with one of these two trigger types. This is similar to driving events labeled Erratic or Shock and manual trigger events labeled Manual or Remote. These labels allow you to easily identify and sort events in the system based on their trigger type. Viewing Safety Events Recall from page 4 that the HindSight Main window is divided into two views: the Event View and the Query View. When events are downloaded from vehicles, driving events and manual trigger events are displayed in the Event View. Safety events are displayed in the Query View. Capturing and Downloading Safety Events Due to the very large number of safety events triggered in a single day, downloading them is optional. This means that unlike driving events where each event is typically downloaded daily for review, safety events are usually only downloaded when an incident of interest occurs. Download options are set in the Event Mover Monitor (EMM). DRC165-B Page 44 HindSight 20/20 v5.4.1 User's Guide

45 SEM Modes Each SEM-capable event recorder is configured to record safety events in one of two modes: Snapshot mode or Motion Capture mode. This is set in the event recorder s firmware and cannot be modified by the user through the software. Snapshot Mode In Snapshot mode, four pictures are captured and combined to create a single video frame which is displayed with fourteen seconds of audio recorded during the event. One picture is of the exterior view at the time of the trigger. Three additional pictures are taken of the interior of the vehicle over time. These pictures are captured based on the following rules: For trigger types of Safety (Open), the first picture is captured nine seconds before the trigger, the second picture is captured at the time of the trigger, and the third picture is captured five seconds after the trigger. Fourteen seconds of audio is recorded. For trigger types of Safety (Closed), the first picture is captured five seconds before the trigger, the second picture is captured at the trigger, and the third picture is captured nine seconds after the trigger. Fourteen seconds of audio is recorded. The safety event combines the four pictures and audio information into a DriveCam Event (*.dce) file. When played, the user sees a single still image consisting of the four pictures and hears audio for the duration of the event. No graph data is included with the event. When an event recorder is configured for Snapshot mode, it does not operate in stealth mode. That is, when standard driving events are triggered, the red and green light on the event recorder will blink to indicate that an event recording is in process. Similarly, when safety events are triggered in Snapshot mode, the red and green light on the event recorder will blink to indicate that an event is being recorded. DRC165-B Page 45 HindSight 20/20 v5.4.1 User's Guide

46 Motion Capture Mode In Motion Capture mode, fifteen pictures are captured at one picture per second beginning five seconds before the time of the trigger. All fifteen pictures are of the interior of the vehicle. Audio is also recorded over the duration of the event. The safety event combines the fifteen pictures and audio information into a DriveCam Event (*.dce) file. When played, the user sees a video at one frame per second for fourteen seconds with full audio. No graph data is included with the event. When an event recorder is configured for Motion Capture mode, it operates in stealth mode. That is, when standard driving events are triggered, the red and green light on the event recorder will blink to indicate that an event recording is in process. When safety events are triggered in Motion Capture mode, the red and green light on the event recorder will not blink. Stealth mode enables users to silently trigger a safety event in a way that the event recorder does not provide any visual or audible clues that it is recording. Identifying SEM-capable Event Recorders Event recorders configured for use with the SEM look and function the same as other event recorders, with the added functionality of being able to record safety events. This is set in the event recorder s firmware and can be identified in several areas of the software. You may view, filter, and/or sort SEM-capable event recorders in the following locations: Details View of the Resource Manager Event Recorder Properties window Query View in the HindSight Main window Safety events are found in the Query View. The figures on the following pages will point out the locations of SEM-capable event recorders and safety events in the software. DRC165-B Page 46 HindSight 20/20 v5.4.1 User's Guide

47 Open the Resource Manager from the Tools menu in the HindSight Main window. Highlight the Event Recorders folder within a specific group and select the Details view from the toolbar. The Safety Mode column shows which event recorders are capable of recording safety events. Double-click an event recorder in the list to see more detail or to modify the settings. The Event Recorder Properties window can be opened from either the Resource Manager or the Query View. DRC165-B Page 47 HindSight 20/20 v5.4.1 User's Guide

48 DRC165-B Page 48 HindSight 20/20 v5.4.1 User's Guide