End users, i.e., the traffic department, most often generate questions on the 
functionality. The questions' origins are either: 1) Does the software replicate an existing process
(or planned one), or 2) Does your TMS software have the functionality found in some other package?
Because the first type of question is often unique, the focus here is on the second type of question. |
| |
"Does your TMS internally maintain information on a trading partner
(supplier, vendor, customer) and their shipping location?" |
| |
| The module, "Address File" maintains a profile of all locations used by the system covering
contacts, open and close times, carrier equipment restrictions, carrier preferences, accessorial service requirements,
etc. When creating shipment plans the software checks to ensure the specific location conditions are not violated. |
| |
| "Does the TMS allow mode comparison for multiple carriers?" |
| |
| In selecting a carrier, the software costs all carriers with rates supporting the plan. In the Fleet Optimization module,
the system also assigns carriers by availability and type of equipment. The software allows over thirty rate structures
including a spot bid process. Additionally, the rating engine automatically links to internal and external tariffs and
rating engines, e.g., CZAR. |
| |
| "How can carriers update the location or availability of equipment?" |
| |
| The carrier can update the system on the status of their equipment via posting to the Web, EDI or by phone. |
| |
| "Does the system support a vendor's or supplier's notice that they are ready to ship?" |
| |
| The vendor or supplier can enter a pick-up request on the notification Web page or send it as an EDI message. Web entry
involves real time validation of the information entered. If the decision involves an offset charge for transportation,
the system determines if the vendor or supplier should plan the shipment versus the traffic department on the receiving side. |
| |
| "What types of load building and routing routines does your system support?" |
| |
| The major categories of shipment types that our transportation models isolate are, for all modes -- standard inbound and
outbound moves, plans involving pooling / consolidation/ assembly or cross-dock points of transfer, continuous mile,
continuous move, merge-in-transit and closed loop trips characteristic of the management and planning involving a private
or dedicated fleet. |
| |
"Can the software plan against promised customer delivery times,
then trigger a best production schedule?" |
| |
| Several manufacturers use the software's order information to create the optimal shipment plans, with the system
calculating when the order must be on the loading dock. This in turn determines the production cycle. Re-planning of
the shipments then occurs post-production. |
| |
| "Does your software utilize standard mileage programs?" |
| |
| Current users of the software have either ALK Technology's PC*MILER or Rand McNally's MileMaker interfaced for mileage
calculation. PC*MILER's mapping software is also used with . |
| |
| "Is there a "tracking and tracing" capability on shipments?" |
| |
| For both Web and EDI technologies there is an intransit visibility (ITV) of all shipments, with the carrier updating
the status of a shipment via a posting to the Website or through EDI 214 / 212 transactions. The Website provides alerts
signaling, e.g., changes in delivery schedules and material shipped. Traffic can modify the shipment plan based on alerts
through carrier contact and dynamic re-planning of the shipment. |
| |
| "What post-shipment functionality is part of your software?" |
| |
| A major part of is the accounting package specific to transportation. This includes: The audit of carrier
invoices (available as EDI, Web or manual input); the allocation of transportation costs; carrier claims and vendor /
supplier chargebacks. |
