All about Tickets in Texada Web, Mobile, and SRM.
Quick Reference
- A Ticket is a document indicating that one or more Assets need to be transported from one location to another, usually at the beginning or end of a Contract.
- There are three different types of Ticket:
- Delivery: Deliver Assets from inventory to the Customer’s work site.
- Pickup: Pick up Assets from the Customer’s work site and return them into inventory.
- Task: Move Assets from one location to another.
- Each Ticket has a unique Ticket number used to identify the document. Delivery and Pickup Tickets have a Ticket number format of ###-###, where the portion before the hyphen is the Contract # of the Ticket’s parent Contract.
- Each Ticket has a status which changes as it progresses through its lifecycle. There are eight different Ticket statuses, which are shared by the three Ticket types.
- Tickets can be created in both Texada Web and Texada SRM:
- Texada Web: Tickets of all three types can be created via the Create Ticket tool.
- Texada SRM: Delivery Tickets can be created via the Delivery Console, and Pickup Tickets can be created via the Pickup Console. Task Tickets cannot be created in Texada SRM.
- Once a Ticket has been created and assigned to a Driver for completion, the assigned Driver can use Texada Mobile to progress through the remaining stages of the Ticket’s workflow.
Introduction
A Ticket is a document indicating that one or more Assets need to be transported from one location to another, usually at the beginning or end of a Contract. Tickets can be created in Texada Web or Texada SRM, and are completed by a Driver using Texada Mobile.
About Tickets
Ticket Types
There are three different types of Ticket:
|
Type |
Icon |
Description |
|
Delivery |
|
Deliver Assets from inventory to the Customer’s work site. |
|
Pickup |
|
Pick up Assets from the Customer’s work site and return them into inventory. |
|
Task |
|
Move Assets from one location to another. |
Delivery and Pickup Tickets are both created as a child document to a parent Contract: Delivery Tickets are intended to be used to deliver Assets at the beginning of a Contract, while Pickup Tickets are intended to be used to pick up Assets at the end of a Contract. Task Tickets do not have a parent Contract; they are intended for miscellaneous tasks such as moving Assets from one yard to another.
Tickets of all three types follow the same basic structure, though differences do exist between Delivery/Pickup Tickets and Task Tickets. The similarities and differences between the three Ticket types are summarized in the table below.
|
Delivery Tickets and Pickup Tickets |
Task Tickets |
|
Contain an Origin Address - the address Assets are to be moved from - and a Destination Address - the address Assets are to be moved to. |
|
|
Can be assigned to a Driver for completion. The assigned Driver will complete the Ticket using Texada Mobile. |
|
|
Have a Scheduled date and time - the date and time at which the Ticket is to be completed (i.e. Assets are to be picked up from the Origin Address). |
|
|
Created as a child document of a parent Contract. Much of the information on the Ticket is inherited from the parent Contract and cannot be changed. |
Created as an independent document. A Contract number can be provided, but does not affect the behavior of the Ticket. |
|
Always associated with a Customer, determined by the parent Contract. |
May or may not be associated with a Customer of your choosing. |
|
One or more Assets from the parent Contract can be transported on a single Ticket. Assets from multiple different Contracts cannot be transported on the same Ticket. |
Any number of Products (Assets and Parts) can be transported on a single Ticket. |
|
Additional Service charges can be added. Services will be charged at the time the parent Contract is closed. |
Additional Services cannot be added. |
Ticket Numbers
Each Ticket has a unique Ticket number used to identify the document. Ticket numbers are generated automatically when the Ticket is first created and cannot be changed.
Delivery and Pickup Tickets have a Ticket number format of ###-###, where the portion before the hyphen is the Contract number of the Ticket’s parent Contract, and the portion after the hyphen is the Ticket number itself. For example, a Delivery Ticket with a Ticket number of 626-001 is TIcket #001 for Contract #626. Note that multiple Delivery or Pickup Tickets can be associated with a single Contract.
Task Tickets have a Ticket number format of ######, as they do not have a parent Contract.
Ticket Statuses and Priority Levels
Each Ticket has a status which changes as it progresses through its lifecycle. There are eight different Ticket statuses, which are shared by the three Ticket types: Created, Assigned, Loading, In Progress, Unloading, Completed, Closed, and Canceled.
In addition to its status, each Ticket has a priority level that can be set in Texada SRM or Texada Web. These priority levels are independent of the Ticket’s status and do not affect its behavior; they are intended only as visual indicators of which Tickets should be prioritized.
See “About Ticket Statuses” for more information.
Working With Tickets
Managing Tickets
Tickets can be managed in the following locations in Texada Web, Mobile, and SRM:
Texada Web:
|
Location |
Description |
| The Delivery Tickets List |
View and manage Delivery Tickets. |
| The Pickup Tickets List |
View and manage Pickup Tickets. |
| The Task Tickets List |
View and manage Task Tickets. |
| The Ticket Map |
View Tickets and Drivers on a map. |
| The Ticket Scheduling Page |
Schedule Tickets for a given day using both list and map views. |
| The Create Ticket Tool |
Create a new Delivery, Pickup, or Task Ticket. |
Texada Mobile:
|
Location |
Description |
| The Tickets Module |
Browse assigned Delivery, Pickup, and Task Tickets in list view or map view. |
Texada SRM:
|
Location |
Description |
| The Delivery Console |
View, manage, and create Delivery Tickets. |
| The Pickup Console |
View, manage, and create Pickup Tickets. |
Creating, Assigning, and Scheduling Tickets
Delivery and Pickup Tickets can be created in Texada Web or Texada SRM. Task Tickets can only be created in Texada Web.
- In Texada Web, Tickets of all three types can be created via the Create Ticket tool.
- In Texada SRM, Delivery Tickets can be created via the Delivery Console, and Pickup Tickets can be created via the Pickup Console.
While creating a Ticket, it can be scheduled and assigned to a Driver for completion. This can also be done after the Ticket has been created. See “Assign and Schedule a Ticket in Texada Web” for more information.
Completing Tickets
Once a Ticket has been assigned to a Driver for completion, the assigned Driver can use Texada Mobile to progress through the remaining stages of the Ticket’s workflow: driving to the Origin Address, picking up the designated Assets, then delivering them to the Destination Address. See “Complete a Ticket in Texada Mobile” for more information.
Electronically Signing Tickets
Part of the process of completing a Ticket is having the Customer sign off on the delivery or pickup. This ensures that they are aware of and satisfied with the work that has been completed. Texada Mobile offers eSignature functionality that allows the Customer to sign off on the Ticket directly from the Driver’s mobile device.
- For Delivery and Task Tickets, an electronic signature is required when delivering Assets to the Destination Address.
- For Pickup Tickets, an electronic signature is required when picking up Assets from the Origin Address.
See “Electronically Sign a Document in Texada Mobile” for more information.