Differences

This shows you the differences between two versions of the page.

--- support:dispatch:dispatch_screens [2015/04/23 13:30]
edmondsj
+++ support:dispatch:dispatch_screens [2016/09/13 14:54] (current)
seyers
@@ Line 12: / Line 12: @@
 ==== Status columns ====
-^Column header^Values^
-|A (assignment status)|H: held\\ W: waiting for assignment\\ A: assigned|
+=== "A" column ===
-|S (job status)|__For active calls__:\\ AP: approved, awaiting assignment\\ AD: driver assigned or unassigned\\  T: transmitting assignment\\ K: Acknowledged by Driver\\ E: Enroute\\ >A: Approaching Arrived \\ @A: At Arrived per GPS \\ A: Arrived \\ H: Hooked \\ >D: Approaching Dropped \\ @D: At Dropped per GPS \\ D: Dropped \\ P: Awaiting pricing\\ F: Failed to transmit assignment\\ \\ __For closed calls__:\\ C: Cleared\\ G: GOA\\ X: Cancelled|
+  * Indicates assignment status
+^Contents^Description^
+|<html><span style="color:black;background-color:yellow;font-weight:bold;">&nbsp;H&nbsp;</span></html>|Held|
+|S|Scheduled and pre-assigned|
+|W|Waiting for assignment|
+|<html><span style="color:white;background-color:red;font-weight:bold;">&nbsp;W&nbsp;</span></html>|Held and scheduled job nearing scheduled time and waiting for assignment|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;A&nbsp;</span></html>|Assigned|
+|<html><span style="color:black;background-color:#CCCCCC;">&nbsp;X&nbsp;</span></html>|Cancelled|
+=== "AS" column ===
+  * Indicates sortable assignment status
+  * Sort order values are configured on the ''Company/Company setup/General config'' screen
+  * Default values are A=1, W=2, H=3, X=4
+^Contents^Description^
+|<html><span style="color:black;background-color:yellow;font-weight:bold;">&nbsp;3H&nbsp;</span></html>|Held|
+|4S|Scheduled and unassigned|
+|2W|Waiting for assignment|
+|<html><span style="color:white;background-color:red;font-weight:bold;">&nbsp;2W&nbsp;</span></html>|Held and scheduled job nearing scheduled time and waiting for assignment|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;1A&nbsp;</span></html>|Assigned|
+|<html><span style="color:black;background-color:#CCCCCC;">&nbsp;5X&nbsp;</span></html>|Cancelled|
+=== "S" column ===
+  * Indicates job status
+  * __For active calls__:
+^Contents^Description^
+|AP|Approved, awaiting assignment|
+|AD|Driver assigned|
+|<html><span style="color:white;background-color:#FF00FF;font-weight:bold;">&nbsp;T&nbsp;</span></html>|Transmitting assignment|
+|<html><span style="color:white;background-color:#FF00FF;font-weight:bold;">&nbsp;TU&nbsp;</span></html>|Transmitting job update|
+|<html><span style="color:white;background-color:red;font-weight:bold;">&nbsp;F&nbsp;</span></html>|Failed to transmit assignment|
+|<html><span style="color:white;background-color:red;font-weight:bold;">&nbsp;UF&nbsp;</span></html>|Failed to transmit job update|
+|<html><span style="color:white;background-color:#4040C0;font-weight:bold;">&nbsp;K&nbsp;</span></html>|Acknowledged by Driver|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;E&nbsp;</span></html>|Enroute|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;>A&nbsp;</span></html>|Approaching Arrived|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;@A&nbsp;</span></html>|At Arrived per GPS|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;A&nbsp;</span></html>|Arrived|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;H&nbsp;</span></html>|Hooked|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;>D&nbsp;</span></html>|Approaching Dropped|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;@D&nbsp;</span></html>|At Dropped per GPS|
+|<html><span style="color:white;background-color:green;font-weight:bold;">&nbsp;D&nbsp;</span></html>|Dropped|
+|<html><span style="color:white;background-color:#0000FF;font-weight:bold;">&nbsp;P&nbsp;</span></html>|Awaiting pricing|
+|<html><span style="color:black;background-color:#F3A007;font-weight:bold;">&nbsp;PR&nbsp;</span></html>|Pricing returned|
+|UC  |Uncancelled  |
+|CA|Callback accept|
+  * __For closed calls__:
+^Contents^Description^
+|<html><span style="color:black;background-color:#CCCCCC;">&nbsp;C&nbsp;</span></html>|Cleared|
+|<html><span style="color:black;background-color:#CCCCCC;">&nbsp;G&nbsp;</span></html>|GOA|
+|<html><span style="color:black;background-color:#CCCCCC;">&nbsp;X&nbsp;</span></html>|Cancelled|
+=== "$P" column ===
+^Contents^Description^
+|{{:support:dispatch:dollar_sign.gif|}}|Job has a credit authorization that has not yet been captured|
+|Blank|Either no credit authorization was processed or a credit authorization has already been captured|
+=== "V" column ===
+^Contents^Description^
+|<html><span style="color:white;background-color:green;">&nbsp;C&nbsp;</span></html>|VIN has been looked up, is a valid VIN, and has been confirmed by a user|
+|<html><span style="color:black;background-color:yellow;">&nbsp;L&nbsp;</span></html>|VIN has been looked up, is a valid VIN, but has not been confirmed by a user|
+|<html><span style="color:white;background-color:red;">&nbsp;F&nbsp;</span></html>|VIN has been looked up and is NOT a valid VIN|
+|Blank|VIN has not been looked up|
+=== Driver Status ===
+Driver Status is a tool for drivers to notify dispatchers of their current situation.  For example:
+  * Active - actively working on service requests
+  * Standby - on duty, but temporarily unavailable - e.g., on lunch break
+  * On Call - logged in and available if other -- e.g., Active -- drivers are unable to respond
+The exact meaning of the terms can be defined by consensus/procedures within the company
 ===== Create a job =====
 * Click Green "New job" Button above open jobs screen.
 {{:support:dispatch:04_02_from_dispatch_board-rev.png|}}
-Fill in minimum of:
-  - Account name
+  * Fill in the yellow required fields:
-  - Year/Make/Model or other details available on vehicle/owner (can be filled in later)
+    * Account name
-  - Enter incident location
+    * Incident location
-  - Select appropriate pricing template for the Account and the Job
+    * Select pricing template for the Account and the Job
-  - Enter destination (if not a service call)
+    * Bill to account name
-  - Click "Save" button at bottom.
+  * Recommended but not required fields:
-  - Fields will turn red if information is required.
+    * Year/Make/Model or other details available on vehicle/owner (can be filled in later)
-You CANNOT save job if required fields aren't filled in.
+    * Destination (if not a service call)
+  * Click "Save" button at bottom.
+    * Fields will turn red if information is required.
+    * You CANNOT save job if required fields aren't filled in.
 {{:support:dispatch:jobentryREV.png|}}
@@ Line 60: / Line 137: @@
 Be sure to select the appropriate pricing template when assigning the job.  If Account is set to Pricing=Driver, the driver will input and confirm the pricing for the job.
-If any details must be corrected after the call is cleared, the dispatcher (if proper commissions are granted in configuration) may update the job pricing by accessing closed jobs, selecting the job from the greyed out closed jobs, and clicking on the "Job Pricing" Tab to access the pricing details for that job.
+If any details must be corrected after the call is cleared, the dispatcher (if proper permissions are granted in configuration) may update the job pricing by accessing closed jobs, selecting the job from the greyed out closed jobs, and clicking on the "Job Pricing" Tab to access the pricing details for that job.
 ==== Pricing modes ====
-CommLink supports five different modes for pricing calls.  For a summary of the modes, review the [[#comparison|Comparison]].
+CommLink supports six different modes for pricing calls.  For a summary of the modes, review the [[#comparison|Comparison]].
@@ Line 70: / Line 147: @@
 In Pricing Mode NONE, all details of pricing are hidden from the driver.  This is accomplished by hiding the Clear process from the driver thus forcing the driver to use Quick Clear.
-The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Droppped, Quick Clear.
+The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Dropped, Quick Clear.
-Original notes on Pricing Mode NONE from December 19, 2012 email from Joe to team:
-<code>
+=== Mode PD - Preset / Due Only ===
-Jim has asked to add Pricing Mode NONE to the system.   Here's the plan...
+In Preset / Due Only pricing, the call is priced by the mobile application //exactly// according the rules.
-The most straight forward way to get this working is to hide the Clear process in CommLink so that
+The driver cannot see or override any prices.  The only dollar amount visible to the driver is the Amount Due from the motorist.  Note that in the case of a split invoice for a motor club call, the Amount Due is the second invoice amount.
-Quick Clear is the only option for the driver to complete the call.  Quick Clear has no pricing and
-no payment capabilities, so it meets the requirements of the customer.  Quick Clear works with tow
-calls and service calls, so we're covered there.  And since CommLink and the host are already setup
-to process Quick Clear, there shouldn't be any significant downstream effects.
-On the host side, you'll need to add "None" to the Pricing Mode drop-down list with a code value of
+During the Clear process, the pricing calculations are performed automatically.
-"NO" for the <mJIR>.  You'll also want to search your code for all references to Pricing Mode to make
-sure nothing breaks.
-Support for Pricing Mode NONE will be in CommLink V2.84 and higher.  Previous versions of CommLink
+There is no interaction with Dispatcher during the Preset / Due Only pricing process.  The driver can complete Preset pricing while out of coverage.
-default to Pricing Mode DRIVER for unrecognized Pricing Modes.  So we'll just need to make customers
-aware that NONE = DRIVER for CommLink V2.83 and older.  The only place that might be an issue is with
-customers running CommLink for Windows (Mentor devices) since we don't have an upgrade path for them
-(the last port was V2.76).
-On the device side, I'm going to hide Clear from the Status Update list screen for calls with Pricing
+This mode is useful when:
-Mode NONE.  That will force the driver into Quick Clear to complete the call.  I've already searched
+  * A call should be priced strictly according to the pre-configured rules.  For example, it would be useful with a new driver.
-the CommLink code and there are a couple of if/then blocks that need to be updated for Pricing Mode
+  * Pricing details should be hidden from the driver.
-NONE, but it's minor stuff.  The testing effort will be more than the coding effort.
-</code>
+The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Dropped, Quick Clear, Clear.
+=== Sample Screens ===
+In CommLink, these are the first three screens in Clear for Preset / Due Only when there's a split invoice. \\
+For a single invoice, the third screen is omitted.
+<html><center></html>
+{{:support:dispatch:pricing_mode_pd_odo.png?250|PD Odometer}}
+{{:support:dispatch:pricing_mode_pd_summary.png?250|PD Summary}}
+{{:support:dispatch:pricing_mode_pd_split.png?250|PS Split}}
+<html></center></html>
 === Mode PR - Preset ===
 In Preset pricing, the call is priced by the mobile application //exactly// according the rules.
-The driver cannot override any prices<sup>1</sup>.  During the Clear process, the pricing calculations are performed automatically.
+The driver can see the prices, but cannot override any prices.
+During the Clear process, the pricing calculations are performed automatically.
 There is no interaction with Dispatcher during the Preset pricing process.  The driver can complete Preset pricing while out of coverage.
-This mode is useful when a call should be priced strictly according to the pre-configured rules.  For example, it would be useful with a new driver.
+This mode is useful when:
+  * A call should be priced strictly according to the pre-configured rules.  For example, it would be useful with a new driver.
+  * Pricing details should be visible to the driver.
+The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Dropped, Quick Clear, Clear.
-The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Droppped, Quick Clear, Clear.
+=== Sample Screens ===
+In CommLink, these are the first three screens in Clear for Preset when there's a split invoice. \\
+For a single invoice, the third screen is omitted.
+<html><center></html>
+{{:support:dispatch:pricing_mode_pr_odo.png?250|PR Odometer}}
+{{:support:dispatch:pricing_mode_pr_summary.png?250|PR Summary}}
+{{:support:dispatch:pricing_mode_pr_split.png?250|PR Split}}
+<html></center></html>
 === Mode DR - Driver ===
@@ Line 122: / Line 209: @@
 This mode is useful when the driver has some input into call pricing.  For example, it would be useful with an experienced and trusted driver.
-The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Droppped, Quick Clear, Clear.
+The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Dropped, Quick Clear, Clear.
@@ Line 130: / Line 217: @@
 The driver cannot override any prices<sup>1</sup>.  During the Pricing process, the pricing calculations are performed automatically and sent to Ranger Host.
-The dispatcher then has a brief period of time to review the pricing information, make changes (if any), and return the final results to the mobile app.  Note this implies the dispatcher is at their desk and ready to review pricing details immediately upon their arrival.
+The dispatcher then has a brief period of time (180 seconds) to review the pricing information, make changes (if any), and return the final results to the mobile app.  Note this implies the dispatcher is at their desk and ready to review pricing details immediately upon their arrival.
 Because of the interaction with the dispatcher, the mobile app must have network connectivity to finalize pricing.  If the mobile application is offline, only preliminary pricing can be completed.
@@ Line 136: / Line 223: @@
 This mode is useful for dispatchers that want to control the pricing of a call.
-The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Droppped, Pricing, Quick Clear.
+The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Dropped, Pricing, Quick Clear.
-=== Mode CO - Confirmed ===
+=== Mode CO - Confirm By Dispatcher ===
 In Confirmed pricing, the rules provide an initial guideline, but the driver can override those calculations.  When the driver is complete, the information is relayed to the dispatcher for final editing and approval.  You can think of Confirmed pricing as Driver pricing plus dispatcher override.
 During the Clear process, the pricing calculations are performed automatically.  Then, the driver is presented with a menu that allows them to override any of the calculated values.  The final values are sent to Ranger Host.
-The dispatcher then has a brief period of time to review the pricing information, make changes (if any), and return the final results to the mobile app. Note this implies the dispatcher is at their desk and ready to review pricing details immediately upon their arrival.
+The dispatcher then has a brief period of time (180 seconds) to review the pricing information, make changes (if any), and return the final results to the mobile app. Note this implies the dispatcher is at their desk and ready to review pricing details immediately upon their arrival.
 Because of the interaction with the dispatcher, the mobile app must have network connectivity to finalize pricing.  If the mobile application is offline, only preliminary pricing can be completed.
@@ Line 150: / Line 237: @@
 This mode is useful for dispatchers with trusted and experienced drivers that also want to review the pricing of a call.
-The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Droppped, Pricing, Quick Clear.
+The Status Update menu contains the following status items for a new tow call:  Enroute, Arrived, Hooked, Dropped, Pricing, Quick Clear.
 === Comparison ===
 The following table compares pricing modes.
-|                                         ^ None       ^ Preset   ^ Driver   ^ Dispatcher  ^ Confirmed  ^
+|                                         ^ None       ^ Preset/DO   ^ Preset   ^ Driver   ^ Dispatcher  ^ Confirmed  ^
-^ Rules from Ranger to CommLink           | X          | X        | X        | X           | X          |
+^ Rules from Ranger to CommLink           | X          | X             | X        | X        | X           | X          |
-^ Dispatcher post-pricing override        | X          | X        | X        | X           | X          |
+^ Dispatcher post-pricing override        | X          | X             | X        | X        | X           | X          |
-^ CommLink calculates prices              |            | X        | X        | X           | X          |
+^ CommLink calculates prices              |            | X             | X        | X        | X           | X          |
-^ Driver sees prices                      |            | X        | X        | X           | X          |
+^ Driver sees Amount Due                  |            | X             | X        | X        | X           | X          |
-^ Driver can override<sup>1</sup> prices  |            |          | X        |             | X          |
+^ Driver sees prices                      |            |               | X        | X        | X           | X          |
-^ 'Pricing' process in CommLink           |            |          |          | X           | X          |
+^ Driver can override prices              |            |               |          | X        |             | X          |
-^ Dispatcher interactive override         |            |          |          | X           | X          |
+^ 'Pricing' process in CommLink           |            |               |          |          | X           | X          |
+^ Dispatcher interactive override         |            |               |          |          | X           | X          |
 ===== Assign driver to a job =====
@@ Line 186: / Line 274: @@
 ===== Unassign driver from a job =====
-Click on job.  This will take you to "JOB STATUS" folder. Click on "JOB ENTRY" folder and click on "Unasign Driver' button at the bottom of screen
+Click on job.  This will take you to "JOB STATUS" folder. Click on "JOB ENTRY" folder and click on "Unassign Driver' button at the bottom of screen

RangerSST Support Center

User Tools

Site Tools

Differences

Page Tools