Command is the nerve center of Omnitracs Drive. In Command you create the workflows the drivers see on their mobile device, as well as setting up the users and user groups, and even changing the text the drivers see on the screen.
Command is broken into the following areas:
The Entitlements area is where you set up your user groups and roles that will be used for Drive. You can also view the users and devices.
Note: Users and devices are added in Roadnet Anywhere, but can be viewed and changed here.
Users - review the drivers that will be using Drive
User Groups - set up and review the groups of users.
Manage Roles - this is currently not used for Drive.
Users are your drivers and others who use Drive or Command. In the user list, the icon indicates if the user is active or inactive; only active users can log into the applications.
Note: Users are created in Roadnet Anywhere, but can be changed in Command. In addition, User Groups and Roles should be defined before updating your Drive users.
- To edit an existing user, click the pencil icon for the user. The Edit User window opens.
- Click the drop-down arrow in the Select User Group field and select the group the user should be a member of. If the user is a Drive user, the user group dictates which workflow the user will see in Drive.
- Change the First Name or Last Name for the user, if appropriate.
- Enter or change the User Email or User Phone. These fields are informational only.
- If the user will be using Drive, enter the Driver Id. This is the ID the user will enter when logging into Drive.
- Device Name and Last Connected are display only; you cannot change them. For drivers, these fields show you the device the driver is using and the last time that device connected to the Omnitracs Drive website.
- Click drop-down arrow in the Select Role field and choose the proper role for the user.
- In the Access Control area, check the Granted box for each application the user should be able to access.
- Click the [Save] button.
User groups are groups of users who have the same roles or permissions in Command or Drive. It is recommended that you create a user group for each workflow you create, and assign the proper users to that group.
Note: You should create your workflows before creating the user groups.
- In Entitlements, click User Groups.
- Click Add Group. The Add Group window opens.
- Enter a Group Name and Group Description.
- Click the drop-down arrow in the Workflow Template field and choose the proper workflow for the group.
Note: If you are using Omnitracs Routing or Dispatching, the workflow selected here must match the default driver workflow selected for the region in Omnitracs Administration.
- Check DRIVE Default if new users should automatically be added to this user group and associated with this user group's workflow.
- Check MA COMMAND Default if new users should automatically be added to this user group.
Note: New users are automatically added to the user group that has Default checked. For instance, if Drive Default is checked for a user group, new users will be added to that group and have access to that workflow. If the user should have access to another workflow, you will need to change their user group after the user is added.
- Check the Granted box for the applications the user group should be able to access.
- Click the [Save] button.
Manage Roles is not currently used with Drive.
The Account Settings are not frequently used. There are three sections: Identity Provider, Manage Licensing, and API Access.
You should not change Identity Provider or Manage Licensing settings. If you are going to use an API to connect with Drive, you will need to .generate a token on the API Access page.
If you are using web services to integrate with Omnitracs Drive, you will need a unique token to connect with Command. You can generate a token on the API Access page, or revoke an existing token.
To generate a token:
- Click Generate Token. A token is generated and displayed on the page.
- Copy and paste this token into your code. Once you leave the API Access page, the token will no longer be available.
To revoke a token:
To revoke a token, you must know the full token value. You cannot select from a list of existing tokens since the tokens are not stored in Command.
- Enter the token you want to revoke in the Specify single token to revoke field.
- Click Revoke Single Token.
If you want to revoke all tokens assigned to your tenant, simply click Revoke All Tokens.
Command Settings lets you specify how Command appears. There are two pages:
Languages & Labels - used to customize the text that appears to people using Command. For instance, if you need to have Command appear in another language, you would add the translated text here.
Universal Config - used to define options that control how Command works for all of the people in your company.
Languages and Labels
The Languages & Labels page lets you specify the text that appears in Command. To change the labels the driver sees in Command, see Languages & Labels in the Workflow area.
The left side of the page lists the available languages you have configured. To add a new language, click Add Language to open the Add Language window. Enter the new language, then click [Save]. A new line for that language appears for each label on the right side of the page.
The right side of the page lists every label in Command. To change a label for an existing language, click the Edit icon to open the Update Custom Content window. Enter the new label and click [Save].
To search for a specific label in the list, enter the label name in Search Labels and press the search icon. The list of labels is filtered to show labels that include the search content you entered.
The Universal Config page under Command Settings lets you choose a couple of options that affect how Command appears and operates.
Core App Settings
- Allow DVIR Modifications - check to allow users to make changes to the Inspections, found under Workflows.
- Dark Theme - check to change the color scheme of Command so that it is darker. This may be helpful if you are using Command at night or in a dark area to reduce the contrast in light levels.
This page shows the location of the Omnitracs Knowledge Base for Command. This is displayed for information-only and cannot be changed.
Workflows define the tasks your drivers perform throughout their day. You can define tasks the driver needs to complete before starting the route, at stops, when completing the route - whatever is needed throughout the day. Command comes with a default workflow - you can edit this workflow to make it work for your company, or you can clone the workflow and use it as the basis for your own workflow. Or, you could even create a workflow from scratch.
Each workflow has six areas you can configure:
Circle of Service - a list of stop types and the associated tasks to be completed at each stop type
Task Library - a list of tasks and their configuration option
Universal Config - application configuration that is unrelated to stop types and tasks, such as HOS settings, Help and Support, and more.
Languages and Labels - change the field label text and configure the application for different languages.
Supporting Data - lookup values for status and type list. For instance, order or stop status, units of measure, etc .
Inspections - configurations for vehicle inspections, vehicle types, and inspection templates. You should not need to change the Inspections page.
Circle of Service
The Circle of Service lets your drivers know quickly and easily the tasks they need to complete at each stop. When creating your circles of service, you create the different stop types the driver may encounter throughout the day, and for each stop type you define the tasks to be completed at that stop type. The driver may not use all possible stop types, while others would likely occur every day. For instance, you most likely would want stop types for the beginning and end of the trip, with delivery and/or pickup stops occurring between. But, you may also want to create stop types for other events the driver may encounter, such as an accident or breakdown, with necessary tasks the driver should complete in those situations.
The first step is to create the stop types.
- Click Add Stop Type; the Add Stop Type window opens.
- Enter the Stop Name and Stop Type.
- If you are using this stop type as a planned stop type in Omnitracs Dispatching, click the Dispatch Stop Type arrow and select the dispatching stop type that corresponds to this stop type. Then, check Set as default for "x" dispatch stop type, where x is the Dispatch Stop Type that was chosen from the list. All stops created in Omnitracs Dispatching with this dispatch stop type will appear in Drive as this Stop Type. For instance, if you have a Stop Type of Rest Break and it is the default for the Dispatch Stop Type of Break, then all breaks created in Omnitracs Dispatching will appear as Rest Breaks in Drive.
Note: Omnitracs recommends that if you are using Omnitracs Dispatching, you do not use the Generic stop type; instead use the stop type that matches the one found in Omnitracs Dispatching. For instance, if creating a stop type that is a form of a break, choose Break as the Dispatch Stop Type.
If you are not using Omnitracs Dispatching and are using a transportation management system (TMS), skip to step 4.
- If the stop type will be a planned stop, check Planned Stop. Examples of planned stops could be start trip or delivery; an example of an unplanned stop type is accident.
If this stop type is similar to an existing stop type and you want to copy the tasks from that type, check Clone tasks from existing stop. Click the Select Stop arrow and choose the stop type to use as the basis. You can then add, delete, or change the tasks on the new stop type.
- If the stop type is a planned stop, and you do not want it included as part of the Completed stops counter in My Day Planner, check Do not include in Trip Header Completed count.
- If you want to add additional stop types, click the [Save+] button.
If you have finished adding stop types, click the [Save] button.
Once you have created the stop type, you need to add the tasks that the driver can complete at those stops. When you add a task to a stop type, you can specify whether it is required, optional, or manual.
- In the stop type list, click on the stop type you want to add tasks to. The right panel lists any tasks already associated with the stop type.
- Click Add Task Type. The Add Task Type window opens.
- Click the Select Task arrow to open a list of available tasks, and then select the task you want to add.
- Click the Choose Task Necessity arrow and choose whether the task is Required, Optional, or Manual.
- Required - the driver cannot complete the stop until the task is completed.
- Optional - the driver can choose whether or not to complete the task. Optional tasks are marked as optional in the driver's circle of service.
- Manual - the driver can add this task to the stop, if necessary. Manual tasks do not appear in the circle of service until the driver adds them.
- Click the [Save] button.
The tasks will appear in the order listed in the circle of service. To change the order of the tasks, click the grabber icon on the left of the task card and, holding down your mouse button, drag the task to the proper place in the list.
The Task Library lists the tasks that you can add to your circle of service. Command comes with several pre-defined common tasks that you can customize to fit your needs. In addition, if you need to add a task that is not in the list, you can add a task, or you can clone an existing task and change it as necessary to fit your needs.
To change an existing task:
- Click the task in the list in the left frame. The information about the task appears in the right frame.
- For each task, there are two tabs in the right frame. The first tab, Breakdown, is the name of the task, and contains the configuration information you are most likely to want to change for that task. If there is an info icon next to a field, hover over the icon for more information. The second tab, Admin tools, contains several fields that are display only - they cannot be changed.
Note: To see how the task will appear to the driver in Drive, click the Show Task icon.
To create a new task based on an existing task:
- Click the task in the list in the left frame. The information about the task appears in the right frame.
- Click the Clone icon. The Clone task window opens.
- If necessary, click the Select Task to Clone arrow and choose the base task.
- In the Name field, enter a name for the new task.
- If you want to add additional tasks, click the [Save+] button.
If you have finished adding tasks, click the [Save] button.
- Make the necessary changes in the new task.
Note: To see how the task will appear to the driver in Drive, click the Show Task icon.
Below are listed the pre-defined tasks:
|Accident||You can add an Accident task which collects specific information about an accident that has occurred. The driver's location is automatically collected. You may configure this task to ask the driver to specify if there are any injuries and how serious, if emergency response is needed, how many vehicles are involved, if the damage has disabled the vehicle or if there is other property damage. You may also require the driver to include at least one photo.|
|Arrive at stop||When drivers arrive at a stop on the trip, they may need to confirm the arrival date and time and location. They may also be allowed to change their HOS Duty Status.|
|Breakdown||You can add a Breakdown task to collect information if the vehicle has problems. The vehicle's location is automatically collected. You may allow the driver to request specific types of assistance, like a tow truck or roadside assistance, and add comments to the task. You can also configure the task to allow drivers to change their HOS Duty Status while they wait for assistance.|
When drivers have a bulk load, you can require them to scan barcodes and provide reasons why an item is manually entered. They may be able to add a new order or be required to enter a quantity for an item. They may or may not be required to complete or change the status of all orders on a stop before they can complete the stop. You can also be required to include at least one note, photo, document, or scale type.
|Bump Dock||After a driver has arrived at a stop, they can be asked to confirm the date and time that they park at the loading dock and are ready to load or unload the vehicle. You can also require them to include a photo.|
|Citation||You may want to add a Citation task that drivers complete if they receive a citation. They will need the citation number. You can also configure this task to require or allow drivers to add comments or a photo before completing the task.|
|Customer Review||The Customer Review allows drivers to have the customer read and agree to your organization's terms and conditions before collecting a signature. The customer is required to mark that they have read and agree to the terms as well as confirm the arrival and unloading times of the delivery.|
The DVIR task lets drivers evaluate the equipment they are about to use for their trip, any equipment they may hook to during the trip, and when they are done the trip, the equipment they used to run it. Drivers may be able to change the equipment that they are evaluating as well as view a previous inspection summary. For each defect that the driver finds, they choose the inspection point or problem from the drop-down menu related to the appropriate inspection category. Drivers may need to sign the DVIR or, if the vehicle is not safe to operate, contact the appropriate individuals. The DVIR options include:
Allow auto signature - if selected, the previous signature for the currently logged in driver will automatically be used for this inspection, with an updated date/time and GPS position. If not selected, the driver will need to sign to indicate the inspection was completed.
Enable CTPAT Confirmation - if selected, the DVIR will include confirmation that a Custom - Trade Partnership Against Terrorism (CTPAT) inspection was completed for the cargo. If not selected, this confirmation will not be part of the inspection.
Enable Task Editing - if selected, the driver will be able to change the task after it is completed. If not selected, the driver will not be able to change the task.
Require License Plate Info - if selected, the license plate number and state/province will be displayed on the DVIR screen; if the license plate information is not displayed, the driver will be prompted to enter it. If not selected, the license plate information will not be displayed.
Driver Can Change Active Assets - if selected, the driver will be asked to confirm if they are picking up or dropping off the inspected trailer. If not selected, the driver will not be asked that question.
Inspection Type - choose what type of inspection to assign to the DVIR. You can have Drive ask the user to choose from the list or you can automatically assign all DVIRs as Pre-Trip, Post Trip, or Mid Trip.
Driver Can Repair defects - if selected, the driver can mark defects as repaired, from the mobile device. Repairs that are certified by the driver are reflected in the Certify Repair module in Omnitracs.
|Delivery||When servicing a stop, drivers can be required to scan barcodes and provide reasons why an item is manually entered. They may be able to add a new order or be required to enter a quantity for an item. They may or may not be required to complete or change the status of all orders on a stop before they can complete the stop. If a driver has over, short, or damaged items, they may be required to include at least one note, photo, or document.|
|Depart||When the driver departs a stop, they may be able to rate the stop, see the next planned top, confirm the data and time of their departure, and see their current HOS Duty Status.|
|Documents||You can use the Add Documents task to allow drivers to include a document throughout their trip. Comments may be required when they add a document.|
|Done||When drivers complete a trip, they may press the Done task. They may need to confirm that they are completing this trip along with a date and time. They can also see your HOS Duty Status.|
|Driver Acknowledgment||If you have a Driver Acknowledgment task in your Circle of Service, drivers may need to check off specific things that they did at the stop, such as following the special driver instructions, have the customer witness the hook-up, or even have the hook-up approved by the customer. Drivers may be required to include a note. Before they can complete the task, they will need to sign an acknowledgment.|
|End||When a driver ends a stop or trip, they can rate the stop or trip, add comments, a well as see and possibly change their HOS Duty Status.|
|Fuel||Use the Fuel task to have drivers add a fuel task when they stop to gas up the vehicle. Drivers enter the amount of fuel dispensed and may be required to include a note or a photo before they can complete the task.|
|Hookup||When drivers are offloading or picking up product and connect your trailer to a connector, you may want the driver to get a customer sign off that it is connected to the correct location before they pump the product out of or into the trailer. The customer may be required to read and acknowledge an agreement.|
|Illness||If a driver stops servicing the trip because he is sick, he can add an Illness task. The driver's location is automatically collected. You can define the task to require the driver to provide a date and time that he will be able to resume driving, as well as comments.|
|Occurrence||When there is a stop that is not planned, such as an accident or breakdown, drivers can use an Occurrence task. The driver's location is automatically collected. The driver may confirm the date and time of the occurrence, the location of the occurrence, and possibly change their current HOS Duty Status.|
|Photos||You can use the Add Photos task to have drivers include a photo throughout the trip. Comments may be required when a driver adds a photo.|
|Pickup||When servicing a stop, drivers may be required to scan barcodes and provide reasons why an item is manually entered. They may be able to add a new order or be required to enter a quantity for an item. They may or may not be required to complete or change the status of all orders on a stop before they can complete the stop. If a driver has over, short, or damaged items, they may be required to include at least one note, photo, or document.|
|Post-Trip||After a driver completes all the stops on a trip, they may need to complete a Post-Trip task. Once the driver confirms the asset he wants to assess, for each defect that he finds, he chooses the inspection point or problem from the drop-down menu related to the appropriate inspection category. The driver may need to sign the inspection or, if the vehicle is not safe to operate, contact the appropriate individuals.|
|Pre-Trip||Before a driver starts a trip, they may need to complete a Pre-Trip task. Once they confirm the asset they want to assess, for each defect that they find, they choose the inspection point or problem from the drop-down menu related to the appropriate inspection category. Drivers may need to sign the inspection or, if the vehicle is not safe to operate, contact the appropriate individuals.|
|Reefer Temp||If you have refrigerated trucks, you may want drivers to record the truck temperature during their trip. The Reefer Temp task allows drivers to enter the temperature reading of the refrigerated unit.|
A Rest Break lets drivers record a break in their work. The driver's HOS Duty Status may display and the driver may be able to change it. Drivers choose the type of break they want to take. When they are done with their break, they can continue the trip.
|Returns||When servicing a stop, drivers may be required to scan barcodes and provide reasons why an item is manually entered. Drivers may be able to add a new order or be required to enter a quantity for an item. They may or may not be required to complete or change the status of all orders on a stop before they can complete the stop. If the driver has over, short, or damaged items, they may be required to include at least one note, photo, or document.|
|Review & Sign||
The Review & Signoff task may be required once an order has been delivered. Drivers may need to have a customer sign for a delivery or may need to mark that the delivery was refused or dropped somewhere at the location. Drivers can choose how the delivery is being finalized, can see an option to get a customer signature, mark that the customer refused delivery, or a different result. Depending on what the driver chooses, they may need to have the customer accept and sign for the delivery or they may need to enter a note as to why the delivery was finalized in the chosen manner.
|Scale||Drivers use the Scale task to capture vehicle and load weights when measured using a truck scale. You may see Tare and Gross weight measurements. You may be required to enter the Steer. Drive, Trailer, and Calculated Total Weights. As well, a photo and/or document may be required before you can complete the task.|
|Seals||To capture Trailer Seal numbers, drivers can scan one or more Top Seals, Bottom Seals, and Other Seals barcodes.|
|Start||When a driver presses the first task on their trip, they are asked "Are you ready to start this Trip?" If they answer yes, they can see and possibly change their HOS Duty Status. There may be other actions the driver needs to perform before they can depart the first stop.|
|Swap Trailers||If a driver swaps trailers on the trip, the Swap Trailers task lets the driver scan the barcode of the trailer being dropped. They may also be able to use a previous signature before they complete the task.|
|Trailer Verification||When a driver changes a trailer on the trip, they may need to verify the change. Drivers can scan or enter the trailer barcode. They may be required to include a photo before they can complete the ask.|
|Weather||When weather interrupts a trip, drivers may be able to enter a Weather task. They select the type of weather causing the disruption and enter the date and time that they will be able to resume the trip. They may be required to include a photo and/or comment before they can complete the task.|
The Universal Config page lets you make changes to what the driver sees when using this workflow. For instance, if you want the driver to be able to add an unplanned stop, or use navigation, you would define these options here. The left side of the Universal Config page lists several categories of settings you can define; when you click one, the right side shows the options in that category.
Hint: If there is an info icon next to a field, hover over the icon for more information on that field. The categories for the Universal Config settings are:
- Adhoc Tasks - enter the number of days that ad hoc tasks will be retained on the device for drivers to reference. Once this expiration is reached, the ad hoc task can not be reviewed on the device. The valid values are 1-30. You can also allow Adhoc Tasks to be seen as a tab on the mobile device.
- Advanced - if your mobile devices are Fixed Display, turn on Drive Device Reset so drivers can easily clear connections to vehicles. Other options on this page should not be changed.
Note: The driver will need to re-enter the Device ID once Drive is reset.
- Core App Settings - allows you to define options that the driver will have on the mobile device, such as whether the driver can add a stop, as well as what features may appear on the device. Hover over the tooltip icon for more information on each option.
- Documents - choose the types of documents the driver will be able to choose from in Drive and the preferred document file format to be captured when the driver scans a document in Drive. The list of documents for the selected Document Types are created in Supporting Data.
- Help & Feedback - lists the links for help and a help desk phone number that drivers will see when they go to the Help & Feedback link in Drive. You can enable feedback and define the types of feedback allowed.
- Hours of Service - if the driver will be using Hours of Service on the device, click the HOS Integration arrow and choose the proper HOS application. You will need to set up additional configuration in Omnitracs Web. If you will be using co-drivers, check Allow Team Driver.
- Location - click the arrows to select where the GPS and In Motion information should come from: the driver's mobile device (Tablet) or the Telematics device. If the In Motion Provider is Use GPS of Tablet, enter the minimum speed at which the vehicle is considered in motion (In Motion Speed Threshold) and the minimum number of pings to use when calculating the speed (In Motion Sample Size).
- Map/Navigation - choose the settings for the maps and Navigation applications.
- Messages - if you are using Centralized Messaging to communicate with your drivers, select Messages Tab in the Messaging Integration field and define the remaining options. You will need to define additional configuration options in Omnitracs Web.
- My Day Planner - select the options the driver can perform from My Day Planner when working in this workflow in Drive.
- Printing - if you want the driver to be able to print receipts or other items, define the configurations for your Brother printer.
- Stop Info Setup - choose options that will be available to the driver at a stop
- Telematics - if there will be a Telematics device in the vehicle, select the Telematics Provider. You will need to set up additional configuration in Omnitracs Web. If the driver must confirm that the proper vehicle is assigned before starting, check Confirm Assigned Truck.
- Text To Speech - if you want the device to verbally alert the driver when specific types of messages are received, use this page. Check Enable Text to Speech Service, and then click the drop-down arrow for each type of message to define when that type of message will be verbalized to the driver.
- User Preferences - choose the proper options to define times and languages the drivers see when using this workflow.
Language and Labels
Note: Changes made here will only appear in the Drive application on the device. If you want to change languages or labels in Command, use the Languages & Labels page under Command Settings.
The Languages & Labels tab lets you change the menu options and messages that your drivers see in Drive when using this workflow. You can also use this section to provide translated text for your drivers to see in the application on the mobile device.
To add a new language:
- Click Add Language icon at the top of the left panel. The Add Language window opens.
- Enter the name of the language, then click [Save]. The new language is added for every label in the list.
To change a label or message:
- Enter the text you are looking for in Search Labels. A list of possible options displays.
- Click the pencil icon to open the Update Custom Content window.
- Enter the new content.
- Click [Save].