HindSight 20/20 Administrator s Guide version 5.4.1

Transcription

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

2 TABLE OF CONTENTS SOFTWARE CONFIGURATION 1 LOGGING ON FOR THE FIRST TIME 1 ADDING A NEW SYSTEM ADMINISTRATOR 2 MODIFYING THE DEFAULT DRIVECAM SYSTEM ADMINISTRATOR 3 Option 1: Changing the Password 3 Option 2: Deleting the DriveCam Login 3 RENAMING THE TOP LEVEL GROUP 4 ADDING SUBGROUPS 5 Building the first sublayer of groups 5 Building the second sublayer of groups 5 ADDING USERS 6 Example: Assigning a Supervisor to a Group 7 Example: Assigning a Reviewer to Multiple Groups 8 Example: Moving Drivers to Different Groups 9 ADDING VEHICLES 10 ASSIGNING EVENT RECORDERS 11 Example: Modifying the Settings of a Single Event Recorder 12 DEFINING GROUP SETTINGS 13 Example: Modifying the Group Settings through Inheritance 13 Example: Applying Event Recorder Defaults 15 Example: Inheriting Settings in the Resource Manager (Reset to Match Group) 17 ADDING EVENT MOVERS 18 FINISHING UP 19 REGISTERING THE SOFTWARE 20 INITIALIZING EVENT RECORDERS 22 Troubleshooting 24 Who should use this document: This document is written primarily for clients using the HindSight System in a self-managed environment. For clients enrolled in DriveCam s Driver Risk Management Program, most of the administrative tasks covered in this document will be taken care of by their DriveCam Program Specialist. Contact Information: DriveCam Technical Support is available 24 hours / 7 days at (866) For international assistance, please call (858)

3 SOFTWARE CONFIGURATION General use of the software is described in the HindSight User s Guide and HindSight Help. For now, a few basic configuration steps should be completed immediately after software installation and before hardware installation and testing. The following procedures define the highest levels of access to the system and should be performed by someone with administrator-level privileges. LOGGING ON FOR THE FIRST TIME Step 1 Open the HindSight Client. Double-click the HindSight Client icon on the computer desktop. Or, on the taskbar, click the Start button and select All Programs >> DriveCam >> HindSight >> HindSight Client. Step 2 The first time you start HindSight 20/20, the user name and password are both drivecam. Enter this in both fields and click Login. As you configure the software for your organization, individual user names and passwords will be set to enable different levels of access to the software. CAUTION: The default drivecam login has administrator level access to the system and should be deleted or its password changed soon after an alternate administrator is assigned. This is optional but highly recommended. DRC155-B Page 1 HindSight Administrator's Guide

4 ADDING A NEW SYSTEM ADMINISTRATOR The first step in configuring HindSight software is to add a new system administrator. The Administrator Role has the highest level of access within the system. Step 1 From the Tools menu in the Main window, select Resource Manager. Step 2 Highlight either Roles or Users under the default group Root If no users have been added to the system thus far, there should be only one user displayed in the window. This is the default drivecam login. Step 3 Click the Add New User / Role button on the Toolbar. Step 4 Select the Enable User Login checkbox and enter a User Name and Password. Step 5 Select the Administrator option button and click OK. The User Name, Password, and Role are all that are required to add a user to the database. The remaining selections are optional. See HindSight Help for more information. Administrators are only allowed one user role. Additional Group Roles are available to other users. These will be discussed on the following pages. DRC155-B Page 2 HindSight Administrator's Guide

5 MODIFYING THE DEFAULT DRIVECAM SYSTEM ADMINISTRATOR Once you have created a unique user name and password for the new system administrator, you should log on to the system with this ID instead of the default drivecam user name and password. Additionally, since the default drivecam user name and password has administrator privileges, it should be deleted or its password changed for security reasons. This is optional. Option 1: Changing the Password Step 1 From the Tools menu in the Main window, select Change Password. Step 2 Enter the old password (drivecam), then select and confirm a new password. The default DriveCam Administrator will remain a user in the system and can be used as a backup login with administrator-level privileges. Or, if you prefer, this user can be deleted from the system entirely. Option 2: Deleting the DriveCam Login Step 1 Close the software then log on using the new administrator s user name and password. Step 2 From the Tools menu in the Main window, select Resource Manager. Step 3 Highlight either Roles or Users under the default group Root There should now be two users displayed: the default DriveCam user and the new administrator added on the previous page (and currently logged on). Step 4 Delete the DriveCam user. DRC155-B Page 3 HindSight Administrator's Guide

6 RENAMING THE TOP LEVEL GROUP When HindSight is first installed, the default top-level group Root is displayed in the Resource Manager. This should be changed to the name of your organization. Step 1 From the Tools menu in the Main window, select Resource Manager. Step 2 Highlight the top-level group (Root) and click the Properties button on the Toolbar. Step 3 Enter a new name for the top-level group (e.g. ACME Transportation) DRC155-B Page 4 HindSight Administrator's Guide

7 ADDING SUBGROUPS 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. The following will provide general guidelines. Refer to HindSight Help for additional information. Building the first sublayer of groups Step 1 Highlight the top-level group and click the New Group button on the Toolbar. Step 2 Enter the Group Name (e.g. Atlanta) of the new subgroup. Step 3 Click OK or Add Another Group (e.g. Boston, Chicago). Building the second sublayer of groups Step 1 Highlight the group (e.g. Chicago) and click the New Group button on the Toolbar. Step 2 Enter the Group Name (e.g. NorthSide) of the new subgroup. Step 3 Click OK or Add Another Group (e.g. SouthSide). Continue adding groups and subgroups until you have completely defined all levels of your organization that will contain objects that you want to set apart from one another. DRC155-B Page 5 HindSight Administrator's Guide

8 ADDING USERS The approach you take toward adding users to the system depends primarily upon personal preference. At its most basic level, all users can be added to one group with the minimum amount of information and modified at a later time. Or, as an administrator, you may decide to add only the group supervisors and let them each add their own drivers, reviewers, coaches, and move managers. The following pages will illustrate the process. Additional information is available in HindSight Help. A User Name, Password, and User Role or Employee Number and User Role are all that are required to add a user 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. Temporary passwords can be assigned during configuration users can then change their own passwords after they log on. Although displayed separately in the Resource Manager, users and roles are inseparable components. Users are added to the system and assigned roles in the same window. Each user must be assigned at least one User Role. Examples are provided on the following pages. The DriveCam Card ID is used with the optional RFID card reader installed in the vehicle. DRC155-B Page 6 HindSight Administrator's Guide

9 Example: Assigning a Supervisor to a Group Users are added by first selecting a group within the Resource Manager. Roles are then assigned and unassigned within the New User / User Properties window. Step 1 Highlight Users (Default Group) within the group to which the supervisor will be assigned. Step 2 Click the New User button on the Toolbar. Step 3 Select the Enable User Login checkbox and enter a User Name and Password. Step 4 In the Group Roles panel, click Add to display the Add Groups & Roles window. Step 5 Highlight the Group (e.g. Chicago), select the Supervisor checkbox, and click OK. The supervisor role will be displayed in the New User window. The driver role is assigned by default and can be removed. This supervisor can also be assigned additional roles using the same procedure (i.e. the supervisor can also be a reviewer, coach, or move manager). In the image above, this user is a supervisor of the Chicago Group. Therefore, he also has supervisor privileges in its subgroups (NorthSide and SouthSide). He does not have any privileges in Atlanta or Boston (though he could be assigned privileges in these groups as well). Refer to the next section for an example of users assigned to multiple groups. DRC155-B Page 7 HindSight Administrator's Guide

10 Example: Assigning a Reviewer to Multiple Groups As shown in the previous example, users are added by first assigning them to a default home group. They are then assigned one or more roles in that same group and/or in other groups. Step 1 Highlight Users (Default Group) within the group that will be the reviewers home group. Step 2 Click the New User button on the Toolbar. Step 3 Select the Enable User Login checkbox and enter a User Name and Password. Step 4 In the Group Roles panel, click Add to display the Add Groups & Roles window. Step 5 Select the Reviewer checkbox for each group assignment and click OK. In the image above, this user has a reviewer role in the Atlanta, Boston, and Chicago Groups; although her default user group is Atlanta. These can be seen in the users and roles folders: The user icon: - is displayed in one location: the Users (Default Group) folder within the group Atlanta. The role icon: - is displayed in three locations: the Roles folder within the groups: Atlanta, Boston, and Chicago. DRC155-B Page 8 HindSight Administrator's Guide

11 Example: Moving Drivers to Different Groups As the past two examples illustrate, each person exists in the system as one user in one default group. Each user may then be assigned one or many roles in one or many groups. In this next example, 15 drivers have been added to the Atlanta Group. Five of them are being transferred to the Boston Group. Step 1 Highlight the Users to be moved (Shift- or Ctrl-click to select multiple users). Step 2 Click the Move button on the Toolbar to display the Change Group window. Step 3 Select the new group to which the users will be assigned and click OK. The users will be moved to the new group. However their driver roles are still assigned to the old group. These must be moved also. Step 4 Selecting the same users in the old group, highlight the Roles to be moved. Step 5 Click the Move button and transfer the roles to the new group. These steps can also be done using a simple drag-and-drop operation from the old group to the new group. Keep in mind that moving the user does not move the user s role, and vice-versa. If a user is being transferred to a new group, decide if you want to move just their role or also their default users group. This will affect several parameters, including group reporting and access to the user information. DRC155-B Page 9 HindSight Administrator's Guide

12 ADDING VEHICLES Vehicles are managed separately from event recorders in the database. You may add and edit vehicles at any time, with or without their event recorders installed. A Vehicle ID is all that is required to add a vehicle to the database and is the primary method of vehicle identification. It is displayed throughout the software and is used to associate vehicles with events and drivers during event review and reporting. Typically, fleet managers will create a list of Vehicle ID s and Event Recorder Serial Numbers prior to physically installing the event recorders within vehicles. As event recorders are delivered to their group locations, they are removed from their shipping containers and arranged on a table. Their serial numbers (labeled on each) are written on the list, assigned to the vehicle in which they will be installed. Event Recorders are then initialized (added to the database). This is discussed on the next page and detailed on page 22. Each vehicle on the list is added to the database and its event recorder assigned through the Vehicle Properties window. If drivers have been added to the database, they may also be assigned to vehicles at this time as well. Finally, the event recorders are given to installers along with the list telling them which event recorder goes in which vehicle. This method of deployment and configuration allows for a smooth and organized rollout of vehicles and event recorders throughout your organization. Alternatively, event recorders may be initialized and installed in vehicles, allowing the installers to create the installation list. This is then returned to the system administrator for configuration in HindSight 20/20. DRC155-B Page 10 HindSight Administrator's Guide

13 ASSIGNING 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 covered in detail on page 22. Initialization only needs to be completed once for each event recorder. They will then be displayed in the Resource Manager, labeled with their 8-digit serial number. This number cannot be changed. It is printed on each event recorder and marked on every event captured with the event recorder. By default, event recorders are placed in the same group as the Event Mover upon 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 into the new group assignment. Once an event recorder has been added to the database, it can be assigned to a vehicle through the Vehicle Properties window, discussed on the previous page. The Event Recorder Properties window allows you to adjust the settings that affect how the event recorder will function within the vehicle (i.e. sensitivity settings, download parameters, record modes, etc.). HindSight supports two different models of event recorders: DriveCam II & DC3. The parameters displayed will be different for each. Refer to the HindSight User s Guide for more information. DRC155-B Page 11 HindSight Administrator's Guide

14 Example: Modifying the Settings of a Single Event Recorder The following example will demonstrate changes made to the settings of an individual event recorder through the Event Recorder Properties window, the method typically used to modify settings one event recorder at a time. Step 1 Highlight the Event Recorders folder within a group (e.g. Atlanta). Step 2 Double-click an event recorder to display the Event Recorder Properties window. The upper portion of the window displays the event recorder s information and provides access to its activity logs, through which you can view all connections, information, and error messages associated with the particular event recorder (these are useful for identifying tampering). The lower portion of the window includes the event recorder s settings, which are distributed across four tabs: Triggers, Wireless, Audio/Video, and Time Zone. Refer to HindSight Help for detailed information about these settings. Step 3 Select a tab (e.g. Audio/Video) and make the desired changes. The changes made will apply only to this event recorder. In fact, in the example above the Record Modes can only be made on an individual basis. The remainder of the settings are typically applied on a group basis for consistency across your organization. This is done through the Group Settings windows. Examples are provided in the next section. DRC155-B Page 12 HindSight Administrator's Guide

15 DEFINING 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. 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 and you may decide to begin with those. Perfecting 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. Examples are provided on the following pages to demonstrate working in the Group Settings windows. Detailed descriptions of the settings are available in the HindSight User s Guide and HindSight Help. Example: Modifying the Group Settings through Inheritance The example on the previous page illustrated changes made to a single event recorder. Most of the time, changes are made to entire groups of event recorders to maintain consistency. Step 1 From the Tools menu in the Main window, select the Group Settings command. Step 2 Highlight the top-level group and select the Event Recorder Defaults >> Triggers tab. Notice the silver stars next to each setting. Since this is the top-level group, it has no parent group from which to inherit settings. However, it can pass settings down to its subgroups. DRC155-B Page 13 HindSight Administrator's Guide

16 Step 3 Highlight a subgroup (e.g. Chicago), disable the Shock Filter, and click Apply. A silver star will be placed next to the Enable Shock Filter setting indicating that it is no longer inheriting the setting from its parent group (e.g. ACME Transportation). Step 4 Select the Replace Settings checkbox at the bottom of the window and click Apply. Step 5 Highlight the next lower subgroup (e.g. SouthSide). Notice that a gold star next to the Enable Shock Filter setting indicating that it has inherited this setting from its parent group (e.g. Chicago). The same would be found in the NorthSide Group. The new changes applied here the have not yet been applied to the event recorders. You must also apply the changes in the Resource Manager. An example is provided on the next page. DRC155-B Page 14 HindSight Administrator's Guide

17 Example: Applying Event Recorder Defaults 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. DRC155-B Page 15 HindSight Administrator's Guide

18 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 3 of the 4 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 upload the new settings. Uploading beings automatically when the connection is established. 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. DRC155-B Page 16 HindSight Administrator's Guide

19 Example: Inheriting Settings in the Resource Manager (Reset to Match Group) When you add or move an event recorder to an existing group, the group s default settings are not automatically applied. In these situations, you must either reapply the group settings from within the Resource Manager or change them manually through the Event Recorder Properties window. In this example, one additional event recorder has been moved to the Atlanta Group. The Event Recorder Defaults have already been modified and applied to the other event recorders within this group. However, the newly moved event recorder still has the same settings from its previous group assignment. Its settings can be easily applied to match those of its new group assignment. Step 1 Highlight the Event Recorders folder within the existing group. Step 2 Highlight the newly added (or moved) event recorder within the group. Step 3 Click the Star button on the Toolbar. The settings of the new event recorder will be changed to match the settings of other event recorders within the group. These are the settings of the Event Recorder Defaults defined in the Group Settings window. An alternative method would have been to open the Event Recorder Properties for the new event recorder and change its settings directly. DRC155-B Page 17 HindSight Administrator's Guide

20 ADDING EVENT MOVERS There should be at least one Event Mover already installed and configured within the system. This was part of the installation process and is described in detail in the HindSight Installation Guide. The following example will repeat the process of adding an Event Mover to the system. The software for the Event Mover must then be installed. Step 1 Highlight the Event Movers folder (if one has not yet been installed in the group). Step 2 Click the New Event Mover button on the Toolbar. Step 3 Enter an Event Mover Name and Password (Remember these for the next section). The new Event Mover will be added to the database and displayed in the Resource Manager. However, it will not function until you have installed and configured the Event Mover software on the actual computer that will server as the Event Mover. This can be the same computer upon which you are currently working or a different one. Step 4 Exit the HindSight Client and refer the HindSight Installation Guide to install the Event Mover. If you have access to the HindSight Installation CD, place it in the computer that will serve as the HindSight Event Mover. Step 5 Install the HindSight Event Mover software. DRC155-B Page 18 HindSight Administrator's Guide

21 FINISHING UP This is all that needs to be completed at this time. The next step in setting up the system will be to install and test your DriveCam Event Recorders. This involves physically installing the units in the vehicles and performing a test event. This event will then be downloaded to an Event Mover and reviewed in HindSight 20/20 to ensure that the installation has been completed correctly before replicating the installation to other vehicles. Initialization of event recorders is discussed in the next section of this guide. Refer to the DriveCam Event Recorder Installation Instructions included with your event recorders for detailed instructions regarding installation within vehicles. If you have not already done so, complete the software registration process. Event recorders cannot connect to the database until the software license is entered and the software registered. The registration window is available in the HindSight Admin Tools. This is discussed in the final section of this guide. DRC155-B Page 19 HindSight Administrator's Guide

22 REGISTERING THE SOFTWARE Software registration must be completed before connecting event recorders to the database. Software configuration (e.g. adding groups, users, etc.) may be completed prior to registration. However, you will not be able to connect and configure event recorders until registration is complete. Typically, the software is registered immediately following installation of the Admin Tools. Instructions are provided in the HindSight Installation Guide. They are repeated here for convenience. Software registration is completed through the HindSight Admin Tools, a standalone component of the software typically installed on a single computer. Registration may be completed either electronically (with an active internet connection) or manually (by contacting DriveCam directly on the telephone). Step 1 Double-click the HindSight Admin Tools icon on the Windows desktop. Step 2 To login, enter an administrator user name and password. If you have not yet added a new administrator, use the default drivecam login (page 3). Step 3 Click Registration in the HindSight Admin Tools window. Step 4 Enter your Company Information Enter the name and address of your company or organization. This information will also be entered into the Company Information section and displayed on DriveCam Reports. The name must be between 3-50 characters - apostrophes (') and quotes (") are not supported. Step 5 Enter the contact information for the person responsible for administering the software. Step 6 Enter your HindSight Serial Number. This is a 16-digit alphanumeric code printed on the cover of the HindSight Installation CD. Enter a unique password for registration purposes. The password must be at least 16 characters in length and can contain any combination of letters and numbers (this is not case sensitive). *** Write down your Registration Password *** Keep the password in a safe, secure location (ideally with the HindSight Installation CD and Serial Number). This password is different from those used to log on to the Admin Tools and to the HindSight Client. It is used by DriveCam to validate your installation in the event you require technical support. DRC155-B Page 20 HindSight Administrator's Guide

23 Electronic Registration If the computer upon which the Admin Tools has been installed has an active internet connection, click Register. The system will take a few moments to contact DriveCam with the registration information. You will receive a confirmation message when it is complete. Manual Registration If you do not have an active internet connection or if electronic registration was unsuccessful, you will need to contact DriveCam over the phone to register manually. This is completed through the Restore Connections window within the HindSight Admin Tools and typically takes only a few minutes. Contact DriveCam to register manually. DriveCam Technical Support is available 24 hours / 7 days at (866) For international assistance, please call (858) You will need the 16-digit Serial Number printed on the cover of the HindSight Installation CD. DRC155-B Page 21 HindSight Administrator's Guide

24 INITIALIZING 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. Event recorders will then be displayed in the Resource Manager, labeled with their serial number, and can be assigned to vehicles. Wireless event recorders must also be connected once via USB for the connection information allowing them to download wirelessly will be uploaded to the units. Following initialization, wireless event recorders will connect automatically to Event Movers through your WiFi Network. Before initializing Wireless Event Recorders, enter the WEP Key in HindSight Client. It will then be uploaded to event recorders during initialization. This enables them to communicate wirelessly with the system. Refer to page 25 for instructions then return to this section when complete. The initialization procedure is always the same. The method depends upon where you are in the installation and deployment process and upon your personal preference. If you have not yet installed event recorders in your vehicles then you can simply line them all up near the computer and quickly initialize them one-by-one. If you have installed event recorders, then you ll have to bring the vehicle to the computer (or vice versa). The image above shows connection of event recorders through the optional USB Docking Station (Download Station and Transceiver). This is not required. You may simply connect the event recorder directly to the Event Mover via USB, bypassing the Download Station and Transceiver. The connection and concept are the same. DRC155-B Page 22 HindSight Administrator's Guide

25 To keep track of event recorders, you may want to make a list of event recorder serial numbers and the vehicles in which they will be installed. Following initialization, you can give the list and the event recorders to the installers for installation in vehicles. See page 10 for Vehicle ID information. HindSight software must be registered before event recorders will initialize. The following section will describe a desktop initialization procedure using the 120V external power supply. The alternative method is to power the event recorders through the vehicle. Step 1 Place the first event recorder on a table near the Event Mover. Step 2 Remove the event recorder s mounting bracket (if attached) to allow connection to power. Step 3 Connect the external power supply to the event recorder and to 120V power. Step 4 Verify that a red or green status light on the event recorder is lit. Step 5 Press the red button on the bottom of the Event Recorder to trigger a test event. Wait for the status lights on the Event Recorder to stop flashing before proceeding. Step 6 Being careful not to trigger another recording, connect the USB cable from the Event Mover to the event recorder. If this is the first event recorder to connect to the Event Mover, you should notice the following: If sound is enabled on the Event Mover, you should hear a USB connection chime (two ascending tones) indicating that the computer has detected a new USB device. This is standard in Windows operating systems. DRC155-B Page 23 HindSight Administrator's Guide

26 There will also likely be some sort of visual indicator on the test computer, including the Found New Hardware Wizard and the appearance of an icon and balloon tip in the Windows notification area (on the lower task bar to the right of the screen). Follow the prompts in the Found New Hardware Wizard, selecting Yes to let Windows search for the driver and install the software automatically. Installation of the drivers only needs to be completed once for each USB port on the Event Mover. After that, event download will begin immediately after an event recorder is connected to the Event Mover. The test event should automatically begin downloading to the database immediately after the drivers have been installed. When download is occurring, the status lights on the event recorder will begin to flash rapidly before returning to solid green. If not, then disconnect and then reconnect the USB cable from the event recorder. Step 7 Connect a USB cable from the computer to the Event Recorder. Step 8 Initialization of the first event recorder is complete. Step 9 Repeat the procedure for the remaining event recorders. Now that the Windows drivers have been installed, the test event should begin to download immediately after the USB connection is established. When download is occurring, the status lights on the Event Recorder will begin to flash rapidly before returning to solid green. Troubleshooting If the test events fail to download, check the following items: Is the software registered? This is required for initialization. Open the Event Mover Monitor (EMM) by clicking the icon on the Windows desktop. Verify that all services are functioning properly. A troubleshooting section is available in the Event Mover Help file which is available through the Help menu in the EMM. Try a different USB port on the Event Mover. DRC155-B Page 24 HindSight Administrator's Guide

27 Setting the WEP Key in the HindSight Client Before initializing Wireless Event Recorders, enter the WEP Key in HindSight Client. It will then be uploaded to event recorders during initialization. This enables them to communicate wirelessly with the system. If you do not complete this procedure before initializing wireless event recorders, you will have to reinitialize them once the WEP Key is set. You do not need to perform this procedure if you are using USB-only event recorders. Step 1 Open the HindSight Client. Double-click the HindSight Client icon on the computer desktop. Or, on the taskbar, click the Start button and select All Programs >> DriveCam >> HindSight >> HindSight Client. Step 2 Log on with the new or default administrator password (page 2). Step 3 Select Group Settings from the Tools menu in the HindSight Main window. Step 4 Select the Wireless tab in the Group Settings window. Step 5 Highlight each group in the left panel of the window and check to see if the Wired Equivalent Privacy (WEP) Key is entered into the field. If the WEP Key is already set for all groups then you may proceed with initialization of your wireless event recorders. Exit the HindSight Client and return to the initialization procedure. If the WEP Key is not set, proceed with the steps below. Step 6 You need to obtain a 128 bit key. There are several sites on the Internet that will generate a random WEP Key for you. This must be 26 characters long (alphanumeric). Talk to your system administrator or contact DriveCam if you need help setting the WEP Key. Step 7 Enter the WEP Key in to the field on the Wireless tab of the Group Settings window. This needs to be done for each group into which wireless event recorders will be initialized so that the settings will be uploaded during the initialization procedure. If you have already set subgroups, you may enter the WEP Key into the top-level group and then select the Replace settings in all subgroups check box at the bottom of the window. Step 8 Make a note of the SSID and WEP Key then click OK to exit the Group Settings window. The wireless access point (WAP) connected to the Event Mover now needs to be configured with this WEP Key. Talk to your system administrator or DriveCam to complete this procedure. DRC155-B Page 25 HindSight Administrator's Guide