1 - TMW Systems
TotalMail PeopleNet interface setup and operation
This manual covers usage of TotalMail with the PeopleNet mobile communication system. For general information on the setup and operation of the TotalMail application, or for specific information on using TotalMail with other mobile communication vendors, see the appropriate TotalMail documentation.
Introduction 4
Pre-installation checklist 5
Installing the PeopleNet Interface 6
Web proxy server settings 6
Configuring the TMW PeopleNet Interface poller parameters 6
Configuring the PeopleNet dispatch component parameters 12
Auto-start polling setup 13
PeopleNet forms setup 13
TMWSuite 14
TL2000 16
TotalMail 2000 Configuration Utility setup 17
Adding a mobile communication unit 17
Enabling auto reply 19
TotalMail Transaction Agent 19
TMWSuite 19
TL2000 19
Operation 21
Operating the TMW PeopleNet Interface 21
Operations performed by the TMW PeopleNet Interface 22
Process Log scroll area 24
Operations Countdown 24
Statistics 25
Operational notes 26
Inbound form messages 26
PerformX Report example 27
Mailbox Housekeeping 27
Customization 28
Configuration of the interface program 28
General configuration panel 28
Polling Session configuration panel 30
PeopleNet Requester configuration panel 32
PeopleNet Mail Reader configuration panel 33
PACOS Trip configuration panel 34
Forms 35
Procedure to add or customize a form 35
Form customization notes 36
Driver Log 44
Setup 44
Operation 45
PACOS 47
Features 47
PeopleNet Dispatch Message 47
PACOS Stop Event messages 47
Lat-Long tuning 49
On-demand status request 49
Auto-prompt form 49
Geocoding 50
PACOS 2.6 enhancements 50
Configuring for PACOS 50
TMWSuite 50
TL2000 55
TotalMail 55
Operation of PACOS 59
Circle of Service Example 59
Trip Editing 64
On-Demand Dispatch Status Request 64
PACOS Trips 65
Begin Trip and End Trip 65
Cancel All PACOS Assignments 66
Customization of PACOS 66
Geofence parameters 66
Auto-prompt form 66
Lat-Long tuning 67
EDI Auto-214’s 70
Driver-initiated PACOS dispatch 71
PACOS Assignment form 71
City Stops 72
Clear PACOS dispatches 73
Geocoding 74
Stop Groups 76
Stop Name Format 79
Changing a custom load assignment form to use PACOS 80
TL2000 PACOS 82
Dispatch 82
Geocoding 82
Event History 82
Running Late 82
Lat-Long Tuning 83
Stop Time Zones 83
Load Assignment Switches 83
Driver Requesting Next Load 83
Maintenance and troubleshooting 83
Error handling 83
Error messages 84
Outbound message failure 86
Editing Pending Data 86
Pending outbound messages 86
Pending On-Demand Position Request 87
Current PACOS Dispatches 88
Pending Driver Log Hours Available Requests 89
Process Log 90
The About window 91
Technical notes 92
Verifying the POP3 e-mail account 92
Switching dispatch systems 93
Additional Location Data 94
Decision Tree Forms 95
Setup 95
Form Editing 96
Form Properties 96
Field Properties 97
Branching and Looping 100
Form Enabling 104
Procedure 104
Error Reporting 105
Revision log 106
Note: TotalMail must be purchased from TMW separately from TMWSuite or TL2000. Unless otherwise noted, all TotalMail interfaces to third-party software products are add-ons that must also be purchased from TMW. For details, contact TMW Sales at 216-831-6606 x259.
1 Introduction
The TotalMail interface to the PeopleNet mobile communication system allows drivers and dispatchers to electronically exchange messages with each other using PeopleNet as the mobile communication vendor. As with TotalMail interfaces to other mobile communication systems, dispatchers use PCs to compose, send, and receive messages, while drivers use onboard MCT/MCU terminals. The PeopleNet Control Center communicates with the dispatch system via the Internet, and with trucks via the cellular network. The PeopleNet system includes the sending of GPS (Global Positioning System) messages (check calls) to the dispatcher.
Note: PeopleNet was formerly known as Intouch, and appears in earlier versions of TotalMail as Intouch. This manual uses the name PeopleNet. However, information in this guide should be understood to apply to the product under either name.
Before attempting to run PeopleNet under your version of TotalMail, make sure your version supports PeopleNet.
The TotalMail Interface to PeopleNet works with the TMWSuite and TL2000 dispatch systems. PeopleNet runs on a Windows computer, and normally is left running in the background. The program passes messages between the dispatch system mail facility and the PeopleNet message center at predetermined intervals.
The PeopleNet interface provides the following services and benefits:
• Periodic GPS updates of truck locations from the PeopleNet Control Center. Thus, dispatchers can easily track a driver's movements.
• Position updates when requested by the dispatcher.
• Timely communications between dispatchers and drivers. A dispatcher sends and reads messages from within TotalMail or the dispatch system, and has the option to ask for immediate or next-call transmission of a message to the truck. The dispatcher can also ask for an immediate reply.
• Message delivery feedback. The message reader shows the date and time of message delivery and display on the onboard console.
• Support for forms.
• Maintenance and troubleshooting, including these features:
o Logging of interface program activity to a text file. You can configure the amount and type of logged messages. On the interface screen, a scrolling view shows the most recent log messages for a polling session.
o Configurable polling rates for message history, location history, outbound messages, message status checking, and position request status checking.
o Error reporting from the interface to a specified dispatcher or all dispatchers. Error handling includes automatic retry and restart.
o Viewing of, and the option to delete, pending outbound messages and position requests.
1 Pre-installation checklist
• A PC having the following specifications is required:
o Pentium (or equivalent) processor and at least 128MB RAM.
o Single processor (not multi-processor).
o Microsoft® Windows NT 4, Windows® 2000, or Windows XP operating system.
o Microsoft Internet Explorer v.3.01 or later.
o A persistent (not dial-up) Internet connection with http support. You can verify this by running a web browser and accessing .
o Access to a POP3 e-mail account with support for the TOP command. The e-mail account should be only for the TMW PeopleNet Interface. Contact your Internet Service Provider, or your network support department if you have an in-house e-mail system, to set up the POP3 account. For more information, see the Verifying the POP3 E-Mail Account section of this document.
o A PeopleNet account with a separate login for the TMW PeopleNet Interface. Contact your PeopleNet representative to set up that account. The login for the TMW PeopleNet Interface must have sufficient user rights (fleet overview display, message, reports, filter, options, map, settings, find, and forms management). You can verify access to the account by running a web browser from the PC. Browse to and log in to the PeopleNet account. The account needs to be enabled for API access from the internet (IP) address that the TMW PeopleNet Interface will be using. Give the IP address to your PeopleNet representative to set up.
o It is recommended that the PC be dedicated to the TMW PeopleNet Interface and TotalMail, and not be running any other server program.
• The dispatcher should be familiar with documentation describing TotalMail poller requirements.
• Drivers and dispatchers should receive adequate training on how to send and receive messages.
2
3 Installing the PeopleNet Interface
The following sections describe the installation and setup of the PeopleNet Interface. Generally, once you have completed the setup procedures, you do not need to do anything else with the PeopleNet interface.
Note: You will need the TotalMail installation CD for some of the following procedures.
The PeopleNet Interface is installed as part of TotalMail. See the TotalMail documentation for information on installing or updating TotalMail.
1 Web proxy server settings
If using a web proxy server, make sure of the following settings:
1. On the web proxy server, disable caching for the PeopleNet domain, .
2. On the PeopleNet poller PC, select the Use HTTP 1.1 through proxy connections option on the Advanced tab of the Internet Options window. To open the Internet Options window, select the Tools menu of Internet Explorer and click the Internet Options command.
2 Configuring the TMW PeopleNet Interface poller parameters
Set the program parameters as follows:
1. Run the TMW PeopleNet Poller. If PeopleNet has been installed as a part of TotalMail, a shortcut should be located in the TotalMail program group on your system.
Note: On older TotalMail versions, this shortcut may be named TMW Intouch Poller. In this document, the term PeopleNet refers to either Intouch or PeopleNet.
2. The first time you run the PeopleNet Poller, the Interface Data Path window displays. Click the Browse button to navigate to the PeopleNet data directory, or manually type in the path to this directory in the Interface Data Path field. Click OK when finished:
[pic]
3. If the folder specified in the PeopleNet Interface Data Path does not exist, the program asks if you want to create the folder. Click the Yes button:
[pic]
4. The first time the PeopleNet poller runs, the Dispatch System window may display. Select the appropriate Dispatch System radio button, and click OK:
[pic]
The TMW PeopleNet Poller window displays:
[pic]
5. From the Edit menu, select Poller Configuration. The Configuration window displays:
[pic]
The Interface Data Path field shows the path you entered in Step 2. If necessary, you can change the path here.
The Dispatch Office Time Zone and Observe Daylight Time fields have automatically been set to the Windows operating system values. If theses fields are not correct, run the Date/Time program in the Windows Control Panel and set the correct time zone. Then correct these two fields to match the new system setting.
6. Go through each tab in the configuration window to review and set options as needed. You should leave most fields at their default values, but you should change the ones discussed below.
7. Click the Polling Session tab, then review the following fields and change as needed:
[pic]
The fields in the Operation Polling Intervals section control the frequency of the named operation.
Note: To turn off the Get Position History, Get Current Positions, Get PerformX Data, Get Driver Log Days or Get Driver Log Hrs Avail operations, set the interval field for that operation to 0:00:00.
• Recent Message: If a message reaches this age without being read by the driver, it is then considered an Older Message.
• Older Message: If a message reaches this age without being read by the driver, it is then deleted from the pending list and will never reach Read status.
• Position Request: If a position request reaches this age without a new fix being reported on the truck, it is canceled and no position report is returned.
8. Click the PeopleNet Requester tab, then review the following fields, and change as needed:
[pic]
• Enter your PeopleNet Customer ID and PeopleNet Password.
• Set the PeopleNet URL to .
9. Click the PeopleNet Mail Reader tab, then review the following fields and change as needed:
[pic]
• Enter your mail server’s POP3 Host Name (e.g., mail.).
• The POP3 Port field most likely needs to remain at the default of 110.
• Enter your specific information in the Mailbox User Name and Mailbox Password fields.
Note: If you do not want to setup e-mail at this time, leave the Mailbox User Name field blank. E-mail processing will not occur, and you will not get on-demand position reports.
• For normal operation, where there is a separate mailbox for the PeopleNet interface, select the Delete irrelevant e-mail? check box. All e-mail messages will be deleted from the mailbox when the program checks pending on-demand position requests.
Note: The only purpose of the Mail Reader is to process pending on-demand position requests. The Mail Reader checks for an e-mail indicating that a new fix has been taken on a truck. After finding that e-mail, it gets the new position report from the PeopleNet control center.
10. The PACOS Trip tab is used exclusively for PACOS. See the Configuring for PACOS section of this document for more information:
[pic]
11. Click OK to save the settings.
12. To close the TMW PeopleNet Poller window, click the Exit button. This step must be performed to start the log file in the specified PeopleNet data directory.
3 Configuring the PeopleNet dispatch component parameters
1. Run the TMW PeopleNet Poller, and then select Dispatch System Configuration from the Edit menu. The TotalMail Xfc Configuration window appears. Set the parameters as described in the TotalMail documentation:
[pic]
2. Make sure the Basic TimeZone Adjustments check box is selected.
3. Make sure the Ignore External ID Warnings and Hide from MComm Vendor check boxes are checked.
4. Make sure the Batched Message Retrieval check box is selected.
5. If necessary, clear the check box for the Send outbounds by priority field.
6. On the Priorities tab, set each of the Outbound priority codes according to these rules. The recommended setting for the Med Priority Code is 1:
• 0 or less: The message will be sent to the truck upon the next call.
• 1 or greater: The message will be sent to the truck immediately, i.e., a call will be made.
7. Set the GPS Request Priority according to the following rules. The recommended setting is 1:
• 0 or less: The last known position will be retrieved.
• 1 or greater: A new fix of the truck’s position will be obtained.
Note: All inbound messages from PeopleNet have a Priority Code of 0.
4 Auto-start polling setup
To set up the PeopleNet Poller to automatically start polling when the program is started, create a shortcut to the program TmwItPll.exe, and add the A=TRUE parameter to the command line. For example:
"C:\Program Files\TMW Systems, Inc\TotalMail\TmwItPll.exe" A=TRUE
5 PeopleNet forms setup
Standard forms are loaded onto the PeopleNet system. Contact your PeopleNet support representative and ask to have the forms group loaded for your dispatch system (either TMWSuite or TL2000). If customizations are made to an inbound form in the dispatch system, you will have to re-enter that form through the PeopleNet web interface to match.
To delete and re-enter a changed form, it is necessary to log in to your PeopleNet account using an administrator’s password. Contact your system administrator to make the changes.
1 TMWSuite
For TMWSuite, import the PeopleNet form set as follows:
Note: The following steps assume that you are using the standard Form Editor. To confirm this setting, select Viewer Options from the TotalMail Tools menu, and make sure the Use advanced form editor check box is not selected. If necessary, clear this check box and click the Save button.
1. Run the TotalMail Viewer, logging in as an administrator.
2. In the TotalMail Viewer, select Form Definition from the Compose menu.
3. Right-click in the form definition window and select Import Macros.
4. Browse to the TmwsPnetFormSet.xml file.
5. In the Import Forms window, select the Import Mobile Communication Types check box.
6. In the For Form ID Interaction area of the Import Forms window, select the Add New Version but preserve Form IDs radio button.
7. In the Import forms with status as area of the Import Forms window, select the Current radio button.
Note: A form’s MobileComm Version should be blank, and the Status should be Current or Pending.
8. When the import completes, you should have the following forms list:
• 01 PRE ASSIGNMENT
• 02 LOAD ASSIGNMENT
• 03 BEGIN TRIP
• 04 ARRIVE AT SHIPPER
• 05 DEPART SHIPPER
• 06 ARRIVE AT CONSIGNEE
• 07 EMPTY AT CONSIGNEE
• 08 ARRIVE AT EXTRA STOP
• 09 UNLOAD AT EXTRA STOP
• 10 PICKUP AT EXTRA STOP
• 11 BEGIN DEADHEAD MOVE
• 12 END DEADHEAD MOVE
• 13 DRIVER HOURS OF SERVICE
• 14 CUSTOMER INFO REQUEST
• 15 CUST INFO REPLY
• 16 STREET ROUTE INFO REQUEST
• 17 STREET ROUTE INFO REPLY
• 18 BREAKDOWN/TROUBLE
• 19 ACCIDENT
• 20 DECLINE TRIP
• 21 EMAIL FROM TRUCK
• 22 CANCEL PACOS ASSIGNMENT
• 23 PACOS ASSIGNMENT
• 24 ASSIGN DEADHEAD MOVE
• 25 CANCEL ALL PACOS ASSN’S
• 31 PICKUP INFO (PACOS)
• 32 TRAILER INFO (PACOS)
• 33 STOP INFO (PACOS)
• 90 PACOS EVENT
• 91 PACOS ARRIVAL
• 92 PACOS DEPARTURE
• 93 PACOS BEGIN TRIP
• 94 PACOS END TRIP
• 96 GEOCODE REQUEST
• 97 GEOCODE RESPONSE
• 98 DRIVER LOG DAY SUMMARY
• 99 DRIVER LOG HOURS AVAILABLE
• 201 DRIVER LOG EVENT
9. Click the Close button.
10. The standard form set is designed to use PACOS. For more information, see the PACOS section of this guide. If you are not using PACOS, please make the following form changes:
A. Edit the Load Assignment form to change the UsePacos field’s Default value to 0. This will prevent the Load Assignment message from triggering a PACOS dispatch to be sent to the mobile communications unit. Change the form’s Priority to Med.
B. Edit the Decline Trip form to change the UsePacos field’s Default value to 0. This will prevent the Decline Trip message from triggering an attempt to remove a PACOS dispatch from the mobile communications unit.
For a description of the TotalMail standard forms, see the TotalMail Dispatch User Guide. There are differences between the TotalMail standard forms and the PeopleNet standard forms:
• The PeopleNet forms are made to fit the 19-character width limit of the mobile terminal display.
• The PeopleNet inbound forms have position information appended. Each inbound form message results in a new position report
2 TL2000
For TL2000, import the PeopleNet form set as follows:
1. Run the TotalMail Viewer, logging in as an administrator.
2. In the TotalMail Viewer, select Form Definition from the Compose menu.
3. Right-click in the form definition window and select Import Macros.
4. Browse to the Tl2kPnetFormSet.xml file.
5. In the Import Forms window, select the Import Mobile Communication Types check box.
6. In the For Form ID Interaction area of the Import Forms window, select the Overwrite Form IDs with identical Form IDs and Versions radio button.
7. In the Import forms with status as area of the Import Forms window, select the Current radio button.
6 TotalMail 2000 Configuration Utility setup
Two folders in the TotalMail 2000 Configuration Utility are used to configure the PeopleNet interface.
1 Adding a mobile communication unit
The ID numbers for mobile communication units (MCUs/MCTs) are entered and assigned to trucks using the TotalMail 2000 Configuration Utility. To add an MCU/MCT:
1. Open the TotalMail 2000 Configuration Utility, which is available in the TotalMail program group. Enter the password for full configuration access when prompted.
2. In the folder list of the TotalMail 2000 Configuration Utility window, select the Truck Mobile Unit folder, as shown below:
[pic]
3. Click the Add Unit button. The Properties window for a new truck mobile unit displays.
4. Enter the MCU/MCT Unit ID, without leading zeroes. The Unit ID must match PeopleNet’s Vehicle Number.
Note: The Unit ID must match PeopleNet’s Vehicle Number. The Vehicle Number is specified in the PeopleNet Fleet Manager (PFM) web program. Upon login to the PFM, it is the number shown in the Vehicle column in the Fleet Overview frame.
5. In the selection grid for the Mobile Communication Unit section, select PeopleNet.
6. In the selection grid for the Truck section, select the truck to be assigned to the MCU/MCT’s UnitID.
Note: If necessary, you can create a new truck by clicking the Add Truck button.
The Properties window for a sample truck mobile unit is shown below:
[pic]
7. Click OK to close the window.
2 Enabling auto reply
1. Open the TotalMail 2000 Configuration Utility.
2. In the folder list of the TotalMail 2000 Configuration Utility window, select the Messages folder, as shown below:
[pic]
3. Select the Set auto reply when creating a message in Viewer check box.
4. Click Apply to save your changes.
5. Click Close to exit the TotalMail 2000 Configuration Utility.
7 TotalMail Transaction Agent
The PeopleNet Interface configuration requirements for the TotalMail Transaction Agent are different for TMWSuite and TL2000.
1 TMWSuite
No special setup is needed for the TotalMail Transaction Agent.
2 TL2000
Configure the TotalMail Transaction Agent as follows:
1. Select Properties from the Options menu
2. Click the Dispatch System tab.
3. In the upper section of the tab, select the check box for the following fields only:
• Enable Agent Sourcing of dispatch messages
• Send Text Messages to Dispatch System
• Transfer all Position Reports to Dispatch System
• Old Style Checkcall Transfer
4. In the lower section of the Dispatch System tab, select the Other radio button, and enter the following in the text field to the right:
TL2KXact_TEST.clsTL2Kxact
The tab should look like this:
[pic]
4 Operation
The TMW PeopleNet Interface provides the communication between your dispatch system’s mobile messaging facility and the PeopleNet Control Center.
• The TMW PeopleNet Interface polls the PeopleNet Control Center at pre-determined intervals, looking for incoming messages. If there are messages, the TMW PeopleNet Interface processes them for the message viewer in the dispatch system, and for the dispatch system’s database.
• If there are outgoing messages, the TMW PeopleNet Interface transfers them to the PeopleNet Control Center at different pre-determined intervals.
One PC at your company must run the TMW PeopleNet Interface in the background under Windows. Leave this machine on with the TMW PeopleNet Interface running to receive messages in the dispatch system.
To start the TMW PeopleNet Interface, double-click the TMW PeopleNet Poller icon in the TotalMail program group. Alternately, you can put a shortcut to the PeopleNet Poller in the Windows Startup program group so that it will start automatically when Windows loads.
1 Operating the TMW PeopleNet Interface
The main TMW PeopleNet Poller Interface window resembles this example:
[pic]
❑ The Processing Log area records the actions of the PeopleNet Poller. This information is written to a log file in the Data Interface folder you specified when you configured the poller (refer back to the section entitled Installing the PeopleNet Interface).
❑ The Operations Countdown and Statistics areas are for information only. Clicking the [pic] button in the Operations Countdown area sets the corresponding countdown to 0:00:00, so that the polling session will select the operation immediately.
❑ Message processing occurs during a polling session. Normally, you will need only to click the Start Polling button to commence a polling session. The main functions of the interface include:
o Start Polling: To start message processing, click the Start Polling button (this function is also available from the Run menu). You will see messages start to fill the Process Log box and the countdown numbers decreasing in the Operations Countdown fields.
o Stop Polling: To stop message processing, click the Stop Polling button (this function is also available from the Run menu).
o Exit: To close the PeopleNet Poller, click the Exit button (this function is also available from the Run menu). If you click the Exit button while a polling session operation is active, you will get a warning message:
[pic]
To prevent data loss, click No to permit the polling operation finish. If you really need to abort, press Yes to exit the program.
2 Operations performed by the TMW PeopleNet Interface
During a polling session, the TMW PeopleNet Interface repetitively performs seven different operations, each at its own specified interval (see Polling Session Configuration later in this guide). Each operation is shown in the Operations Countdown panel of the main window. The seven operations are:
• Get Inbound Messages: The TMW PeopleNet Interface issues a Message History request to the PeopleNet Control Center, asking for any new messages from drivers. The PeopleNet Control Center responds by sending all the new messages. The TMW PeopleNet Interface then delivers the messages to the dispatch system.
• Get Position History: The TMW PeopleNet Interface issues a Location History request to the PeopleNet Control Center. The PeopleNet Control Center responds by sending all the location records that have arrived since the last Location History request was serviced. The TMW PeopleNet Interface then delivers the position reports to the dispatch system.
• Get Current Positions: The TMW PeopleNet Interface issues a Location Overview request to the PeopleNet Control Center. The PeopleNet Control Center responds by sending the latest location record that it has for each vehicle. The TMW PeopleNet Interface then delivers the position reports to the dispatch system.
• Get PerformX Reports: The TMW PeopleNet Interface issues a Get PerformX request to the PeopleNet Control Center. The PeopleNet Control Center responds by sending all PerformX data that has arrived since the last Get PerformX request was serviced. The TMW PeopleNet Interface then delivers a PerformX report for each truck that has data to TotalMail as a message from the truck.
• Get Driver Log Days: The TMW PeopleNet interface issues a Get Driver Log Days request to the PeopleNet Control Center. The PeopleNet Control Center responds by sending all Driver Log Days data that is available since the last Get Driver Log Days request was serviced. The TMW PeopleNet Interface then creates a Driver Log Day form message for each driver – day received.
• Get Driver Log Hrs Avail: The TMW PeopleNet interface issues a Get Driver Log Hours Available request for all drivers to the PeopleNet Control Center. The PeopleNet Control Center responds by sending the current Driver Log Hours Available data that it has. The TMW PeopleNet Interface then creates a Driver Log Hours Available form message for each driver in the data received..
• Send Outbound Messages: The TMW PeopleNet Interface gets unsent messages for drivers from the dispatch system and processes them one by one. It issues a Message Send request to the PeopleNet Control Center. The PeopleNet Control Center then sends the message text to the mobile display in the specified truck. The TMW PeopleNet Interface records the sent message and will check periodically to get an update of the message’s status. (See the Check Recent Messages and Check Older Messages information below.) This pending outbound message record can be viewed by selecting Pending Outbound Messages from the PeopleNet Poller Edit menu.
Note: You must stop the PeopleNet Poller to make the Pending Outbound Messages menu option available. When the poller is running, this option is disabled.
• Check Recent Messages: The TMW PeopleNet Interface goes through its list of pending outbound messages. For recently issued messages (messages younger than the Recent Message Age Limit set in the Polling Session configuration panel), the program issues a Message Check request to the PeopleNet Control Center. The PeopleNet Control Center responds by sending the status of the message from its database.
• If the status of the pending outbound message has changed, the TMW PeopleNet Interface delivers the updated status to the dispatch system.
• If the status indicates that the driver has read the message, the program deletes that message’s record from the pending outbound messages list.
• Check Older Messages: The TMW PeopleNet Interface goes through its list of pending outbound messages. For messages older than the Older Message Age Limit in the Polling Session configuration panel, the program deletes that message’s record from the pending outbound messages list, and will no longer check the message’s status. It creates and sends a new message to the dispatch system that the outbound message has not been read.
For messages older than the Recent Message Age Limit in the Polling Session configuration panel, the program issues a Message Check request to the PeopleNet Control Center. The PeopleNet Control Center responds by sending the status of the message from its database.
• If the status of the pending outbound message has changed, the TMW PeopleNet Interface delivers the updated status to the dispatch system.
• If the status indicates that the driver has read the message, the program deletes that message’s record from the pending outbound messages list.
• Check Position Requests: The TMW PeopleNet Interface checks its mailbox for messages from the PeopleNet Control Center that show a completed on-demand position request and the location record is available on the PeopleNet Control Center’s database. The program:
• Issues a Location for One Truck request to the PeopleNet Control Center
• Gets the new position report
• Sends the report to the dispatch system.
1 Process Log scroll area
The Process Log scroll area shows what the PeopleNet poller is doing during a polling session. It also helps in testing and troubleshooting. It is not necessary to read the process log to check for problems. Any problems that might need attention are reported in a message to the dispatch system.
As message processing runs, the program adds messages to the Process Log area. Each message written to the Process Log area is also written to a process log file (Pnet.log) located in your Data Interface folder. You can use the scroll bar to view prior messages; but if a new message is added after you have scrolled up, the box will scroll back and display the last message. To scroll the Process Log without it jumping to the bottom, click the Stop Polling button. When you are finished viewing and scrolling, click the Start Polling button to resume message processing. Whenever message processing begins, the Process Log area clears.
Five types of messages can appear in the Process Log box. The five types have a different color and starting character.
[pic]
For further details on the message types, see the Process Log section later in this guide.
2 Operations Countdown
This Operations Countdown frame of the main TMW PeopleNet Interface window shows when each of the ten polling operations is scheduled to start, and which operation will start next. It also enables you to select one of the polling operations to start immediately.
The Operation Countdown fields show as hours:minutes:seconds (0:00:00).
One of the Operation Countdown fields shows in bold type (e.g., 0:00:23) to indicate that it will be the next to start. The next-to-start countdown also appears in the upper right of the main TMW PeopleNet Interface window.
To start an operation immediately, click the [pic] button to the left of the desired countdown field for the operation. The countdown sets to 0:00:00 so that the polling session will select the operation immediately.
After an operation runs, the countdown is reset to the interval specified in polling session configuration. These intervals can be changed by selecting Poller Configuration from the PeopleNet Poller Edit menu, and then clicking the Polling Session tab.
When you stop the polling session, the TMW PeopleNet Interface remembers the last time that each operation ran. When you start the next polling session, the program calculates each countdown based on the last time the operation ran and its specified interval. This occurs even if the program is closed, or restarts itself in between. For example: the Get Position History Interval is set to 4:00:00 (4 hours), and you stop polling at 10:00 when the countdown reads 2:10:00. If you start polling again at 12:00, the program calculates the Get Position History countdown to be 0:10:00.
3 Statistics
The Statistics frame of the main TMW PeopleNet Interface window shows information about the current polling session. The information is updated whenever an operation completes. When a new polling session starts, the information is reset so that the counts and duration fields show 0.
A description of each field follows:
• Polling Duration: shows the amount of time the current polling session has been running. The field shows as hours:minutes:seconds (0:00:00).
• Pending Outbounds: shows how many messages have been sent that the driver has not yet read and have not expired. After the driver reads a message, that fact will be sent to the PeopleNet Control Center. When the TMW PeopleNet Interface runs a Check Recent Messages or Check Older Messages operation, it gets the message status, deletes the pending outbound message record, and subtracts 1 from the Pending Outbounds count. When the program sends a message, it adds 1 to the Pending Outbounds count. The number in this field will be the number of records that appear in the Pending Outbound Messages window, which can be accessed via the PeopleNet Poller Edit menu. This count persists between polling sessions; it is not zeroed.
• Pending Pos. Req’s: shows how many on-demand position requests have been sent but so far without response. When the PeopleNet Control Center gets an on-demand position request, it calls the truck, gets a new GPS reading from the truck, and adds the truck’s location record to its database. The PeopleNet Control Center then sends an e-mail to the TMW PeopleNet Interface’s mailbox indicating that the new location is available. When the TMW PeopleNet Interface runs the Check Position Requests operation, it reads the e-mail and gets the new location. It then deletes the pending on-demand position request record and subtracts 1 from the Pending Pos. Req’s count. When the program sends an on-demand position request, it adds 1 to the Pending Pos. Req’s count. The number in this field will be the number of records that appear in the Pending On-Demand Position Requests window, which can be accessed via the PeopleNet Poller Edit menu. This count persists between polling sessions; it is not zeroed.
• Pending Hrs Avl Req’s: shows how many hours available requests have been sent but so far without a response with recent enough data. If the TMW PeopleNet Interface gets a response with data older than that specified in Hrs Avail Req Age Limit, it issues a position request for the truck to PeopleNet, to cause a data call. Then it issues another hours available request each time outbound messages are sent, until it gets recent enough hours available data or until the Position Request Age Limit is reached. When either of those cases occurs, the program subtracts 1 from the Pending Hrs Avl Req’s count. The number in this field will be the number of records that appear in the Pending Hours Available Requests window, which can be accessed via the PeopleNet Poller Edit menu. This count persists between polling sessions; it is not zeroed.
• Inbound Messages: shows how many messages from drivers have been received and delivered to the dispatch system during the current polling session. This count returns to zero when a new polling session begins.
• Position Reports: shows how many locations of trucks have been received and delivered to the dispatch system during the current polling session. This count returns to zero when a new polling session begins.
• PerformX Reports: shows how many reports of PerformX data have been received and delivered to the TotalMail Viewer during the current polling session. This count returns to zero when a new polling session begins.
• Driver Log Days: shows how many driver log day messages have been received and delivered to the TotalMail Viewer during the current polling session. This count returns to zero when a new polling session begins.
• Driver Log Hrs Avail: shows how many driver log hours available messages have been received and delivered to the TotalMail Viewer during the current polling session. This count returns to zero when a new polling session begins.
• Outbound Messages: shows how many messages from the dispatch system have been sent to the PeopleNet Control Center during the current polling session. This count returns to zero when a new polling session begins.
• Position Requests: shows how many position requests, both on-demand and last-known, have been sent to the PeopleNet Control Center during the current polling session. This count returns to zero when a new polling session begins.
• Acknowledgements: shows how many new message statuses have been received and delivered to the dispatch system during the current polling session. This count returns to zero when a new polling session begins.
3 Operational notes
1 Inbound form messages
The standard inbound form messages are appended with PeopleNet auto-location information. This information is used to create a position report for each inbound message. These fields can be ignored by the dispatcher when reading the message. Example, auto-location information appears below the dashed line:
* DRIVER HOURS *
DATE 04/21/03
SLEEPER 08:00
DRIVING 10:00
NOT DRVING 03:00
-------------------
Cleveland, OH and
In Bedford, OH On
I-271 (No GPS signal)
41.3704;-81.5280
PerformX Report example
* PerformX Report for Vehicle 9999 *
Parameters:
Long Idle Threshold: 900 secs.
RPM Threshold: 1,800 rpm's
Over Speed: 65 mph
Excess Speed: 80 mph
Dates from 01/01/02 to 01/08/02
Odometer from 120000.0 to 123589.0
Engine Time: 199,951 secs.
Moving Time: 198,775 secs.
Over RPM Time: 310 secs.
Over Speed Time: 2,048 secs.
Excess Speed Time: 0 secs.
Long Idle Time: 612 secs.
Long Idles: 4
Short Idle Time: 564 secs.
Short Idles: 64
Fuel Used: 652.250
3 Mailbox Housekeeping
Though the poller only looks for position request status e-mails, PeopleNet sends many other kinds of messages to the poller’s mailbox. To ensure that the mailbox does not get overly cluttered, the poller periodically cleans the mailbox by starting mail reader processing. The poller does this on the first Check Position Requests operation after a Check Older Messages operation, even if there are no pending position requests. Therefore, the cleaning will occur on about the Check Older Messages processing interval.
5 Customization
1 Configuration of the interface program
All configuration parameters for the TMW PeopleNet Interface can be edited using the poller Configuration window. To open this window:
1. Run the TMW PeopleNet Poller.
2. From the poller’s Edit menu, select Poller Configuration.
Four tabs appear for the four configuration panels. The General panel is displayed initially. To select a different panel, click its tab.
The buttons on the Configuration window work as follows:
❑ OK: Saves the configuration parameters of all panels and exits the edit session.
❑ Cancel: Exits the edit session without saving changes.
❑ Apply: Saves the configuration parameters of all panels, but does not exit.
1 General configuration panel
The General configuration panel is shown here:
[pic]
Settings on the General configuration panel include:
• Interface Data Path: The TMW PeopleNet Interface’s data files and the process log files are stored in the directory specified here. You can use the Browse button next to the field to navigate to and select a directory. If a desired directory does not exist, you can browse to the root for the directory, and then append a folder name to the path. The folder will be created.
• Dispatch Office Time Zone: The TMW PeopleNet Interface uses the time zone specified in this field, along with the Observe Daylight Time field for converting times between the PeopleNet Control Center (where times are specified in GMT) and the dispatch system. If the value does not agree with the time zone setting in the Windows operating system, you will not be able to start polling. Instead, an error message will appear:
[pic]
You can set the Windows operating system time zone by using the Windows Date/Time utility, which is available in the Windows Control Panel.
• Observe Daylight Time: Select this check box to agree with your locale. This setting must match the setting in the Windows control panel. You can verify and set the Windows time using the Date/Time utility in the Windows Control Panel.
• Form verification logging level: Specifies which warnings will be included in the form verification report (see “Form verification” section). The possible settings are:
Low: No warnings are included.
Medium: All but field name warnings and field editability for non-bidirectional form warnings are included. (This is the default setting.)
High: All warnings are included.
• Max log size (Kb): the maximum size of the log file, before the poller renames it for backup and starts a new process log file.
• Number of log files to keep: the maximum number of process log files (one active + backup) to keep. (See “Process Log” section.)
• Failed delivery msg to dispatch?: When an outbound message fails, TotalMail marks the message with error information and forwards it to Admin. Select this check box to also have the TotalMail – PeopleNet interface send an error message to the dispatcher.
• Pacos Dispatch lat-long warning?: Select this check box to warn the dispatcher if a company in the PACOS dispatch is missing the lat-long. When selected, TotalMail puts a warning message giving the company ID(s) with the missing lat-long into the error info of the message. The message is then highlighted as having an error (usually it appears in red in the mailbox), but the PACOS dispatch is still sent out.
• Hide Message To Web User?: The TotalMail – PeopleNet interface receives messages from drivers that may be addressed to PeopleNet users other than the poller. Select this check box to keep such text messages from going to the dispatcher’s inbox, and to just have them go to history. Only text messages are affected by this setting.
• PNet Poller User ID: When Hide Message to Web User? is selected, enter the poller’s user ID as it appears in the PeopleNet PFM web program. Any text messages from a driver addressed to a user other than the one entered here, will not go to the dispatcher’s inbox.
• Form Script Usage: To specify your usage of PeopleNet form scripts, including decision tree form (DTF) capability, choose from the drop-down list one of the following:
o None: TotalMail will not support PeopleNet forms created by script.
o Accept Inbound: Allows TotalMail to receive form messages of script-defined forms. We recommend not using this setting, but using the Full setting.
o Full: Full support for PeopleNet script-created forms, including defining the form scripts from the TotalMail Advanced Form Editor.
See the Decision Tree Forms section of this document for more details.
2 Polling Session configuration panel
The Polling Session configuration panel is shown here:
[pic]
All of the Interval and Age Limit fields are in hours:minutes:seconds (0:00:00). See the Operations Performed by the TMW PeopleNet Interface section earlier in this guide for a description of the operations to which these fields apply. Normally, you can leave the Interval and Age Limit fields at their default values, but you may want to change them for fine-tuning or troubleshooting purposes. Many of the fields have a range of valid, acceptable values. The program will notify you if you attempt a setting that is out of the valid range.
Fields on the Polling Session configuration panel include:
❑ Get Inbound Messages Interval: the amount of time between starts of the Get Inbound Messages operation.
❑ Get Position History Interval: the amount of time between starts of the Get Position Reports operation.
❑ Get Current Positions Interval: the amount of time between starts of the Get Current Positions operation.
❑ Get PerformX Data Interval: the amount of time between starts of the Get PerformX Data operation.
❑ Send Outbound Messages Interval: the amount of time between starts of the Send Outbound Messages operation.
❑ Get Driver Log Days: The frequency at which the poller will check for driver log daily hours information. Set to 0:00:00 to disable driver log day summary messages.
❑ Get Driver Log Hrs Avail: The frequency at which the poller will get driver log hours available information for all drivers. The minimum value is 15 minutes. Set to 0:00:00 to disable driver log hours available messages.
❑ Check Recent Messages Interval: the amount of time between starts of the Check Recent Messages operation.
❑ Check Older Messages Interval: the amount of time between starts of the Check Older Messages operation.
❑ Check Position Requests Interval: the amount of time between starts of the Check Position Requests operation.
❑ (Daily) Down Time From: the time of day at which the polling session suspends itself to allow for backup of the dispatch system and to avoid unnecessary use of the PeopleNet Control Center’s web server when the dispatch office is closed. This field is in 24-hour clock format, from 00:00 to 23:59. To specify that the polling session not suspend itself, enter 00:00 in both the From and To fields.
❑ (Daily) Down Time To: the time of day at which the polling session resumes operation, after suspending itself. Set this to a time that allows the system to catch up on message processing before the dispatch office opens. This field is in 24-hour clock format, from 00:00 to 23:59.
❑ PACOS Disp Age Limit: the amount of time after a PACOS dispatch is sent, before it is deleted from the Current PACOS Dispatches list (see Current PACOS Dispatches).
❑ Recent Message Age Limit: the amount of time after a message is sent during which its status will be checked by the Check Recent Messages operation. After this time has elapsed, the status will be checked by the Check Older Messages operation.
❑ Older Message Age Limit: the amount of time after a message is sent during which its status will be checked. After this time has elapsed, the message’s status will no longer be checked.
❑ Position Request Age Limit: the amount of time after which an on-demand position request is issued that the TMW PeopleNet Interface will wait for a location update from the PeopleNet Control Center. After this time has elapsed, the program will no longer check for the location update.
❑ Hours Avail Req Age Limit: Oldest acceptable age of driver log hours available data received from a hours available request. If received data is older, the poller will issue a position request to ping the truck and try again.
❑ Default Button: Click the Default button to set Interval and Age Limit fields to default values.
3 PeopleNet Requester configuration panel
The PeopleNet Requester configuration panel is shown here:
[pic]
Settings in the PeopleNet Requestor configuration panel include:
❑ PeopleNet Customer ID: the number assigned by PeopleNet that identifies your account dedicated to the TMW PeopleNet Interface.
❑ PeopleNet Password: the password for the TMW PeopleNet Interface’s PeopleNet account. This field shows a string of asterisks (*), instead of the actual password value.
❑ PeopleNet URL: the Internet URL string for the PeopleNet Control Center’s web server program.
❑ Request Time Out: the amount of time the TMW PeopleNet Interface will wait for the PeopleNet Control Center to respond to a request before it gives up and logs an error. If the program reports frequent PeopleNet Requester time-out errors during operations, increase the value of this field to allow time for the longest operations (Get Inbound Messages and Get Position History) to finish.
❑ Max Stops per Msg: Normally you can leave this at the default value of 15. If you have PACOS dispatch messages that fail because they are too long, lower this number to break the dispatch message into multiple shorter messages.
❑ Last Msg Serial#: the number of the last inbound message received from the PeopleNet Control Center. The poller maintains this field, so normally you will not need to touch this field. If for some reason you lost some messages received from PeopleNet, you can retrieve them again by setting this field to the number of the last message received before those messages. You can always set this field to 0 to direct the poller to resume retrieving new messages only.
❑ Last Drv Log Evt Pkt#: the number of the last driver log event packet received from the PeopleNet Control Center. The poller maintains this field, so normally you will not need to touch it. Once a packet is successfully received, it is no longer available to be retrieved again.
❑ PACOS Event Form ID’s: See “Configuring for PACOS” > “TotalMail.”
❑ PACOS Geocode Form ID: See “Configuring for PACOS” > “TotalMail.”
❑ Default Button: Click the Default button to set the Request Time Out and PeopleNet URL fields to the default values.
❑ Driver Logs - Day Summary: Mobilecomm vendor form ID of the Driver Log Day Summary form. This field is initialized to the standard form set value of 396. You normally would not have to change this.
❑ Driver Logs – Hours Available: Mobilecomm vendor form ID of the Driver Log Hours Available form. This field is initialized to the standard form set value of 397. You normally would not have to change this.
❑ Driver Logs – Login: Mobilecomm vendor form ID of the Driver Login form. This field is initialized to 0, which disables creation of this message. To enable this message, create a form using Driver Logs – Gen’l as a model, assign it a Mobilecomm vendor form ID less than 400, and enter that number here.
❑ Driver Logs – Logout: Mobilecomm vendor form ID of the Driver Logout form. This field is initialized to 0, which disables creation of this message. To enable this message, create a form using Driver Logs – Gen’l as a model, assign it a Mobilecomm vendor form ID less than 400, and enter that number here.
❑ Driver Logs – Gen’l: Mobilecomm vendor form ID of the general driver log event form. This field is initialized to 0, which disables creation of this message. To enable this message, enter the the standard DRIVER LOG EVENT form’s Mobilecomm vendor form ID, which is delivered as 399.
PeopleNet Mail Reader configuration panel
The PeopleNet Mail Reader configuration panel is shown here:
[pic]
Settings on the PeopleNet Mail Reader configuration panel include:
❑ POP3 Host Name: name of the POP3 mail server.
❑ POP3 Port: the mail server machine’s port number for POP3 access. The convention is to use the number 110.
❑ Mailbox User Name: the TMW PeopleNet Interface’s user name for logging in to the mail server and accessing its mailbox.
Note: If you do not want to setup e-mail, leave the Mailbox User Name field blank. E-mail processing will not occur, and you will not get on-demand position reports.
❑ Mailbox Password: the password for logging in to the mail server and accessing the TMW PeopleNet Interface’s mailbox.
❑ Request Time Out: the amount of time the TMW PeopleNet Interface will wait for the e-mail server to respond to a request before it gives up and logs an error. If the program reports frequent time out errors during the Check Position Requests operation, increase the value of this field to allow time for the e-mail server to respond to requests during periods where the server is slow.
❑ Delete irrelevant e-mail?: Select this check box to delete all e-mail from the mailbox when the program checks pending on-demand position requests. For normal setup, this option should be checked. If the PeopleNet interface is sharing a mailbox with another application or person, clear this option.
❑ Default Button: Click the Default button to set the POP3 Port and Request Time Out fields to the default values.
PACOS Trip configuration panel
The PACOS Trip configuration panel is shown here:
[pic]
The settings in this panel are used exclusively for PACOS. See the Configuring for PACOS section of this document for more information.
2 Forms
The TotalMail Interface to PeopleNet comes with a standard form set. The form set has two parts: the PeopleNet part and the TotalMail part. These were installed with the installation procedure (see PeopleNet Forms Setup earlier in this guide). A standard form may be deleted or customized, or a new custom form may be added.
Note: The TotalMail – PeopleNet Interface now supports PeopleNet Decision Tree Forms (DTF) and PeopleNet form creation scripts. See the Decision Tree Forms section of this document for more details.
1 Procedure to add or customize a form
An outbound TotalMail form does not require a matching PeopleNet form. The form message would be sent as a text message, formatted to appear on the driver’s mobile communication terminal the same as it appears in the TotalMail Viewer. If the outbound TotalMail form does have a matching PeopleNet form, the form message would appear on the mobile communication terminal as a PeopleNet form message. A PeopleNet form message has two lines for each field: one line for the label, and one for the value.
An inbound form always requires both a TotalMail and a PeopleNet form definition.
To add or customize an outbound form with no PeopleNet form definition:
1. Design the form using the TotalMail form editor. If you are customizing an existing form, create a new form version.
2. Set the form as Pending in TotalMail and enter the mobile comm form ID as a number less than 400. The PeopleNet interface regards a form with a mobile comm form ID less than 400 as one that has no PeopleNet form definition.
3. With the PeopleNet Poller running, the prior step triggers a TotalMail form definition message.
4. The PeopleNet Poller processes the form definition message, changing the form version status from Pending to Current.
To add or customize an inbound form, or an outbound form that has a PeopleNet part:
1. Design the form using the TotalMail form editor. If you are customizing an existing form, create a new form version.
2. Print out the TotalMail form.
3. Enter the form in PeopleNet using the printout.
4. Jot down the PeopleNet form ID.
5. Set the form as Pending in TotalMail and enter the PeopleNet form ID.
6. With the PeopleNet Poller running, the prior step triggers a TotalMail form definition message.
7. Look for a successful transmission of the form definition, or an error message, in the TotalMail Viewer Admin Inbox. If successful, the form version status changes from Pending to Current. If in error, the form version status changes from Pending to Working.
8. If an error message was returned, note the mismatches and correct the form in TotalMail, or in PeopleNet as needed.
9. In the PeopleNet forms manager, select the In use check box for the form. If customizing an existing form, deselect the In use box for the old version of the form. Click the Submit button.
2 Form customization notes
1 Maximum lines
A PeopleNet form in TotalMail may be designed to have up to 100 lines. Note that a TotalMail form that is mapped to a PeopleNet form is subject to the PeopleNet limit of 60 fields.
2 Maximum columns
The PeopleNet form in TotalMail has a restriction of 19 characters per line to match the display of the PeopleNet mobile terminal. However, this restriction is only necessary for an outbound form that is not mapped to a PeopleNet form. In that case, the form will be sent to the PeopleNet mobile terminal as it appears in TotalMail. On the other hand, a form that is mapped to a PeopleNet form may appear differently in the TotalMail Viewer, and may be wider.
To make a form wider, you can use the TotalMail Advanced Form Editor or Standard Form Editor.
To make a form wider using the TotalMail Advanced Form Editor:
1. From the TotalMail program group, run the Advanced Form Editor application. Alternately, you can click the Compose menu in the TotalMail Viewer, then select Form Definition.
Note: The availability of the advanced form editor depends on whether you have selected the Use advanced form editor check box in TotalMail Viewer Options. To use the Advanced Form Editor, you will need to have your system administrator set up a Form Definition password for you in the Security section of the TotalMail Configuration.
The Advanced Form Editor opens:
[pic]
2. Select a form to edit, and double click the name.
3. In the form properties, select the Dimension property, then click the [pic] button.
[pic]
4. Select the Custom radio button, type in the desired number of columns in the Columns field, and click OK.
[pic]
To make a form wider using the standard form editor:
1. Run the TotalMail Viewer. Click the Compose menu, then select Form Definition. The standard Available Form Definitions listing opens:
[pic]
2. Select form to edit, and click the Edit button. The Form View window opens:
[pic]
3. Click the Set Dimension button
4. Select the maximum columns and rows from the Available Dimensions list, then click OK.
[pic]
3 Text field
For fields that can exceed the form width, use the TotalMail Text field type, and define the height of the field to be 2 or more. On the mobile terminal, the field will show just as many lines as are needed to hold the text. The same is true for the display of the field in the TotalMail Viewer preview area. In the TotalMail Viewer form, if the actual text exceeds the number of lines specified for field height, click in the field and use the down-arrow to scroll and see the rest of the text.
When the dispatcher types into a text field and hits the ENTER key to start a new line, the text in the resulting message on the mobile terminal will also start on a new line.
4 Special PeopleNet fields
Some special PeopleNet fields can be placed on the form in TotalMail.
PeopleNet Date–Time field: The PeopleNet Date–Time field displays a Date–Time field from a PeopleNet form as mm/dd/yy hh:mm, for example: 04/30/03 13:30.
PeopleNet Lat–Long field: The PeopleNet Lat–Long field displays the automatic Lat–Long field from a PeopleNet form as latDegrees;longDegrees, for example:
41.3269;-81.4827
When the PeopleNet Poller gets an inbound message with a PeopleNet Lat–Long field, it creates a position report for the truck that sent the message. The each inbound form of the standard form set contains a PeopleNet Lat–Long field.
5 Forced reply
You can specify use of PeopleNet’s forced reply feature from the TotalMail form editor. For example, to specify a forced reply with an immediate return, edit the outbound form and set the Reply Form ID field by selecting the form to reply with from the list of inbound forms. You may also select Freeform to reply with. Then edit the reply form and set the Priority field to a priority that would generate an immediate call (usually med or high)
[pic]
When you create a message with that form, you can override those settings if you want. Similarly, when you create a text message, you can specify the reply form and priority.
[pic]
6 Form field mapping
Forms that are mapped between TotalMail and PeopleNet must agree in field sequence and type. The tables below list acceptable field type mappings.
1 Outbound field type mappings
|TotalMail |PeopleNet |
|Date |Text |
|Generic |Text |
|Monetary |Text (contains $) |
|Phone Number |Text |
|Positive Integer |Numeric |
|Real Number |Numeric |
|SSN |Text |
|Time |Time |
|Yes/No |Text |
|Zip Code + 4 |Text |
|PNet:DateTime |DateTime |
|PNet:MultiChoice |Multiple Choice (see Note) |
Note: The PNet:MultiChoice field must be in one of the following formats:
•
•
• -
If a choice-number is available, it will be sent to PeopleNet, otherwise the choice-text will be sent.
2 Inbound field type mappings
|PeopleNet |TotalMail: Recommended |TotalMail: Accepted |
|Number |Real Number, Positive Integer, Generic |Text |
|Text |Text, Generic |Phone Number, SSN, Zip Code + 4|
|Multiple Choice |Generic |Text, Yes/No |
|Password |Generic |Text |
|Time |Time, Generic |Text |
|Date & Time |Pnet:DateTime, Generic |Text, Date (see Note 1) |
|Auto Driver Name |Generic |Text |
|Auto Location |Generic |Text |
|Auto Lat-Long |Pnet:LatLong |Generic, Text |
|Auto Odometer |Positive Integer, Real Number, Generic |Text |
|Signature Capture |Positive Integer, Real Number, Generic |Text |
|Barcode Scan |Generic |Text |
|Display Text |Generic |Any other |
|Auto Date-Time | Pnet:DateTime, Generic |Text, Date (see Note 1) |
|Auto Vehicle Fuel |Real Number, Positive Integer, Generic |Text |
|Numeric Enhanced |Real Number, Positive Integer, Generic |Text |
|Date |Date, Generic |Text |
Notes:
1. The Date field must not be followed by a Time field. In that case, the TMW PeopleNet Interface would split the PeopleNet Date & Time field into the TotalMail Date and Time fields, throwing off the field mapping. Instead of a TotalMail Date field, use a Pnet:DateTime field. This does not apply when customizing forms for automatically-generated form messages.
2. The PeopleNet Display Text type field maps into TotalMail but does not contain data. Map this field type to a one-character generic field, as a place-holder.
7 Form verification
When you set a TotalMail form version to Pending, the interface will verify it against the form entered into PeopleNet (see Procedure to Add or Customize Form). If OK, the form version will be set to Current. If not OK, the form version will be set back to Working. In either case, a form verification report will be created and delivered to the Admin Inbox showing each error or warning, and indicating failure or success.
Here are examples of the form verification report:
From PeopleNet Poller 04/29 14:44:27:
Form ID 6194 verification PASSED.
Form: 6194 PRE ASSIGNMENT - Shipper and consignee information about an order
From PeopleNet Poller 04/29 14:44:17:
Form ID 6186 verification passed with a WARNING:
Form: 6186 CUSTOMER INFO REQUEST - Request information about a company.
Fld# 1: Warning: Field driver options differ. TMW = editable; PNet = required.
Fld# 2: Warning: Field names are dissimilar - one is blank. TMW = LocationDesc; PNet = .
Fld# 3: Warning: Field names are dissimilar - one is blank. TMW = LatLong; PNet = .
From PeopleNet Poller 05/09 17:24:22:
Form ID 6185 verification FAILED:
Form: 6185 DRIVER HOURS OF SERVICE - Allow driver to send in log hours
Fld# 1: Warning: Field driver options differ. TMW = editable; PNet = required.
Fld# 2: Warning: Field driver options differ. TMW = editable; PNet = required.
Fld# 3: Warning: Field driver options differ. TMW = editable; PNet = required.
Fld# 4: Failure: Data types mismatch - TotalMail type not acceptable for this PNet type on an inbound form. Recommend Duration, String. TMW = Positive; PNet = Time.
Fld# 4: Warning: Field names are dissimilar. TMW = fldOnDuty--NotDriving; PNet = ON DUTY-NOT DRIVNG.
Fld# 4: Warning: Field driver options differ. TMW = editable; PNet = required.
Fld# 5: Warning: Field names are dissimilar - one is blank. TMW = LocationDesc; PNet = .
Fld# 6: Warning: Field names are dissimilar - one is blank. TMW = LatLong; PNet = .
8 Automatically Generated Form Messages
You can customize certain automatically-generated forms. For example, you can delete fields or change field sequence, as long as you keep the field names the same. The PACOS event forms (PACOS Event, PACOS Arrival, PACOS Departure, PACOS Begin Trip & PACOS End Trip) can be customized only if the poller PACOS Trip, Use Trips check box is selected. If the Use Trips is not selected, then you must use the standard, un-customized PACOS event forms. The Driver Log Day Summary, Driver Log Hours Available and Driver Log Event forms can be customized. The Geocode Response form cannot be customized.
3 Driver Log
1 Setup
1 TotalMail 2000 Configuration Utility
Follow these steps to enable the interface to create Driver Log Day Summary and Driver Log Hours Available messages:
1. In the Truck Mobile Unit folder, create a Mobile Comm Unit with the Unit ID !PeopleNet and Mobile Comm Vendor PeopleNet.
2. Click the Add Truck button.
3. Create a truck with the name !PeopleNet and assign the !PeopleNet Mobile Comm Unit to it. Do not enter a Dispatch ID for the truck.
The !PeopleNet truck is used as the sender for automatically created Driver Log Day Summary messages, and for Driver Log Hours Available messages that were not requested for a specific truck.
The standard driver log forms expect the Driver ID from PeopleNet to match the TMWSuite Driver ID. The PeopleNet Driver ID is entered in the PeopleNet PFM web program.
2 Planning Worksheet
If using driver log hours available, add the hours available fields, if not already there, to the Driver asset table. Change the column headers to describe the data, something like:
• mpp_dailyhrsest: Drv Hrs Avail Today
• mpp_weeklyhrsest: OnDuty Hrs Avail Today
• mpp_estlog_datetime: Hrs Avail As-Of
3 Poller Configuration
To enable the poller to receive driver log day summary, driver log hours available, driver login, logout and other log events, see the Polling Session configuration panel and PeopleNet Requester configuration panel sections in this document.
2 Operation
1 Driver Log Day Summary
When the poller Polling Session, Get Driver Log Days setting is not 0:00:00, TotalMail automatically creates the Driver Log Day Summary form message, which updates the TMWSuite driver logs. One message is created for each driver + day record that was received from PeopleNet. This feature would replace the manual Driver Hours of Service form.
2 Driver Log Hours Available
When the poller Polling Session, Get Driver Log Hrs Avail, setting is not 0:00:00, TotalMail automatically creates the Driver Log Hours Available form message, which updates hours available fields on the TMWSuite driver profile. These fields, Daily Hours Estimate (mpp_dailyhrsest) and Weekly Hours Estimate, (mpp_weeklyhrsest) can be seen in the Planning Worksheet. TotalMail requests hours available for all drivers, and creates a message for each driver hours available record received from PeopleNet. The standard Driver Log Hours Available form maps the data from the first hours available rule in the table. It maps the Driving Hours Available into the Daily Hours Estimate field, and the On Duty Hours Available into the Weekly Hours Available field.
Driver log hours available can be requested for a specific truck:
1. Select New Special Message from the Compose menu in the TotalMail Viewer.
2. Select PeopleNet Driver Log Hours Available Request and click Create.
[pic]
3. Select or type a driver or tractor and click OK.
4. When TotalMail gets the response from PeopleNet, it will create a Driver Log Hours Available message for the driver.
6 PACOS
PACOS stands for PeopleNet Automatic Cycle of Service.
Note: Paragraphs applying only to TMWSuite or TL2000 are preceded by TMWSuite or TL2000.
1 Features
1 PeopleNet Dispatch Message
The PeopleNet Dispatch Message is sent by the dispatch system to describe the stops of a trip to PACOS. The message is sent whenever the regular Load Assignment message is sent.
TMWSuite: The parameters used to compose this message are maintained in TMWSuite at these possible levels: system-wide, company, event code, and company–event code. Also, the Arriving event type’s radius and timeout values can be overridden at the actual stop level. Parameters not specified at a lower level are set to the next higher level.
TL2000: The parameters used to compose this message are maintained in TL2000 at the customer and dispatch event levels.
A PeopleNet dispatch can be updated by sending a new Load Assignment for the trip segment. The old dispatch is replaced by the new.
2 PACOS Stop Event messages
The TotalMail PeopleNet Poller issues a request to get all new PACOS stop event messages. The interval for this request is configurable, as are the other polling operations.
The types of PACOS stop event messages are implemented as described here.
1 Late Arriving
Receipt of this message from PACOS results in this system behavior:
1. The standard TotalMail PACOS stop event form message is created by the TotalMail PeopleNet Poller.
2. The message is delivered to the dispatcher’s Inbox in TotalMail.
3. The message is highlighted in TotalMail Viewer.
4. The TotalMail Have Mail icon in the Windows system tray changes to notify of an important message, or a warning pops up, as specified in the TotalMail Viewer Options.
5. TMWSuite: In the Planning Worksheet, the Late indicator (green, yellow, red) turns orange.
TL2000: The event, like all PACOS events, may be stored in a history file that has support for maintenance and reporting.
6. TMWSuite: In the Trip Folder, the Mobile Comm Status field shown on the Order Header reads Late to arriving pt..
7. TMWSuite: If mapped, a late arrival EDI shipment status message is sent to the specified trading partners.
2 Late Arrived, Late Departed
Receipt of this message from PACOS results in this system behavior:
1. The standard TotalMail PACOS stop event form message is created by the TotalMail PeopleNet Poller.
2. The message is delivered to the dispatcher’s inbox in TotalMail.
3. TMWSuite: In the Trip Folder, the Mobile Comm Status field shown on the Order Header reads Late to arrived pt. or Late to Departed pt..
TL2000: The event, like all PACOS events, may be stored in a history file that has support for maintenance and reporting.
3 Arriving
Receipt of this message from PACOS results in this system behavior:
1. The standard TotalMail PACOS stop event form message is created by the TotalMail PeopleNet Poller.
2. The message is delivered to the dispatcher’s inbox in TotalMail.
3. TMWSuite: In the Trip Folder, the Mobile Comm Status field shown on the Order Header reads Arriving.
TL2000: The event, like all PACOS events, may be stored in a history file that has support for maintenance and reporting.
4. TMWSuite: If mapped, an Arriving EDI shipment status message is sent to the specified trading partners.
4 Arrived
Receipt of this message from PACOS results in this system behavior:
1. The standard TotalMail PACOS Arrived form message is created by the TotalMail PeopleNet Poller.
2. The message is delivered to the dispatcher’s Inbox in TotalMail.
3. TMWSuite: In the Trip Folder, the stop status changes to Actual.
TL2000: The stop is marked Arrived. The event, like all PACOS events, may be stored in a history file that has support for maintenance and reporting.
4. TMWSuite: If mapped, the normal Arrived EDI shipment status message is sent to the specified trading partners.
5 Departed
Receipt of this message from PACOS will result in this system behavior:
1. The standard TotalMail PACOS Departed form message is created by the TotalMail PeopleNet Poller.
2. The message is delivered to the dispatcher’s Inbox in TotalMail.
3. TMWSuite: In the Trip Folder there is a new Mobile Comm Status field shown on both the Order Header and the Stop Details. The value of the field in the Order Header and the relevant stop shows Departed.
TL2000: The stop is marked Departed. The event, like all PACOS events, may be stored in a history file that has support for maintenance and reporting.
4. TMWSuite: If mapped, a Departed EDI shipment status message is sent to the specified trading partners.
3 Lat-Long tuning
With PACOS’ capability to detect arrival at a stop, TotalMail can use the resulting Arrived message to tune the lat-long of the TMWSuite company file. This feature is designed into TotalMail’s standard PACOS Arrived form. A system administrator may modify the Arrived form to disable this feature.
4 On-demand status request
Using PACOS’ capability to return the current dispatch status events for a PeopleNet dispatch, TotalMail enables the dispatcher to issue an on-demand status request. This request can only be issued from the TotalMail Viewer. After the request is processed, a formatted text message showing the dispatch status events appears in the dispatcher’s TotalMail Inbox.
5 Auto-prompt form
This has been called the “turn-around arrived form.” The system provides an option to send a filled-out auto-prompt form message with the PACOS dispatch for each Arrived event. A form ID can be specified as a geofence parameter at any level. When set, the form specified is auto-filled by TotalMail for each stop. Each resulting message is included in its stop within the PeopleNet dispatch message. When the driver sends in the message, TotalMail performs its usual update processing.
6 Geocoding
For an automatic PACOS Stop Event message to be created, a lat-long is required for that stop with the PACOS Dispatch message. PACOS provides a facility to retrieve lat-longs for a company by address. When configured to do so, the TMW PeopleNet Interface checks a stop for a lat-long that is not set, requests the PACOS facility to retrieve the lat-long, and updates the dispatch system company (or customer) record. Alternatively, a geocode request can be issued for a company from the TotalMail Viewer.
7 PACOS 2.6 enhancements
The PACOS 2.6 enhancements add PACOS Trip features:
• PACOS trip
• PACOS stop sequence
• Detention warning
• Driver prompts: audible, negative
• Auto-prompt form reply options
• Additional PACOS event data shown in form message
2 Configuring for PACOS
1 TMWSuite
1. In order to trigger the first PACOS Arrived event at a certain stop, latitude and longitude values must exist in the company profile in Company File Maintenance. Make sure these values are reasonably accurate in your company profile. The values will be fine-tuned as PACOS Arrived events occur.
2. Set default geofence parameters.
A. From the System Administration Edit menu, select GeoFence Setup. The Setup GeoFence Defaults window displays:
[pic]
TotalMail will use the most specific geofence record it finds in the GeoFence Setup file. For example, to look up the geofence parameters for Company ID = ACME,
Event Code = LLD, Type = Arriving, TotalMail would search in the following sequence for a matching geofence parameters record:
|Sequence |Company ID |Event Code |Type |
|1 |ACME |LLD |Arriving |
|2 |ACME |LLD |UNKNOWN |
|3 |ACME |ALL |Arriving |
|4 |ACME |ALL |UNKNOWN |
|5 |UNKNOWN |LLD |Arriving |
|6 |UNKNOWN |LLD |UNKNOWN |
|7 |UNKNOWN |ALL |Arriving |
|8 |UNKNOWN |ALL |UNKNOWN |
B. During the upgrade procedure, three records for the default geofence parameters were added. These records have the following values for Company ID, Event Code, and Type:
|Company ID |Event Code |Type |
|UNKNOWN |ALL |Arriving |
|UNKNOWN |ALL |Arrived |
|UNKNOWN |ALL |Departed |
These records will be used for geofence parameters when there is no record for a specific Company ID or Event Code.
Make the changes you want for these three default records.
The meaning of each field in the Setup GeoFence Defaults window is as follows:
Type: The type of geofence. A geofence is a circle of a specified radius around a geographic location. There are three possible values: Arriving, Arrived, and Departed. When a vehicle reaches the Arriving geofence, it is considered to be approaching the location. When it reaches the Arrived geofence, it is considered to be at the location. When the vehicle is going away from the location and reaches the Departed geofence, it is considered have left the location.
Radius: Specifies the size of the geofence. Both the Arriving geofence and the Departed geofence must be a bigger circle than the Arrived geofence. To specify that no geofence is to be used, enter a value of -1.
Radius Units: The unit of measure for the Radius value.
Timeout: The interval in minutes between the latest time a vehicle should reach a geofence and the scheduled time of arrival or departure at the location. This value is subtracted from the appropriate scheduled time to get a deadline time, after which the vehicle would be considered late. The timeouts for any stop must be set such that the Arriving deadline occurs before the Arrived, and the Arrived deadline occurs before the Departed. Otherwise, PACOS would reject the dispatch message.
The default method of selecting the appropriate scheduled time is as follows:
• If the Earliest and Latest times are set for the stop, then the timeout interval is subtracted from the Latest time.
• If the Earliest and Latest times are not set for the stop:
• For the Arriving and Arrived types, the timeout interval is subtracted from the stop’s arrival time.
• For the Departed type, the timeout interval is subtracted from the departure time.
This method can be overridden to always select the Earliest and Latest times. See Step 6c in the Upgrade Instructions section of this document.
Example:
• Arriving Radius = 60 miles
• Timeout = 50 minutes
• Scheduled Arrival Time = 08:00
• Stop = Acme Corp
At 7:10, the vehicle is still 65 miles away from Acme Corp. The PACOS system triggers a Late Arriving notification.
If this field is set to -1, then no late messages or events will be created.
Call Occur: A Yes/No field that specifies whether a data call should be made from the vehicle when it reaches the geofence.
Form ID Occur: The TotalMail form ID of the form to be presented to and sent in by the driver when his vehicle arrives at a specified stop. TotalMail will auto-fill the form with information and send it out with the PeopleNet dispatch message, when the load assignment is sent. If a minus sign precedes the form ID, then the form will not be auto-filled and sent out, but PACOS will present a blank form to the driver. This field only applies to the Arrived geofence type. It has no effect for the Arriving and Departed types.
Email Occur: A Yes/No field that specifies whether PACOS will send a canned e-mail message when a vehicle reaches the geofence. The message will be sent to TotalMail and to the address list specified in Email List Occur.
Email Late: A Yes/No field that specifies whether PACOS will send a canned e-mail message when a vehicle reaches the geofence. The message will be sent to TotalMail.
Email List Occur: A comma-separated list of e-mail addresses to which to send canned PACOS e-mail messages when a vehicle reaches the geofence.
Call Late: This field has no effect. PACOS always makes a call when it detects a late condition.
Form ID Late, Email List Late: These fields have no effect. PACOS does not support the actions these fields would imply.
C. Add defaults by event code, as desired. For example:
|Company ID |Event Code |Type |
|UNKNOWN |LLD |Arriving |
|UNKNOWN |LLD |Arrived |
|UNKNOWN |LLD |Departed |
D. Add defaults by company, as desired. For example:
|Company ID |Event Code |Type |
|SUPSHA |ALL |Arriving |
|SUPSHA |ALL |Arrived |
|SUPSHA |ALL |Departed |
E. Add specific parameters by company and event code, as desired. For example:
|Company ID |Event Code |Type |
|ACMATL |LLD |Arriving |
|ACMATL |LLD |Arrived |
|ACMATL |LLD |Departed |
3. Use of PACOS can be limited to certain tractors by setting the Use Geofencing field in Tractor File Maintenance.
Note: The TMWSuite database field is trc_useGeofencing in the tractorprofile file. Valid values are:
|V |Use Vendor geofencing. Use this value to enable PACOS. |
|T |Use TMWSuite AAD geofencing. |
|Y |Use both Vendor and TmwSuite AAD geofencing. |
|N |Do not use any geofencing. |
.
2
Since 10/21/2005, the following fields have been added to the Geofence Setup records:
• Reply Form ID Occur: The form ID and method to use when replying to a PACOS auto-prompt form. The valid options are:
o -2: Forces the driver to reply with the same form message. The only menu option on the MCT will be REPLY.
o -1: Forces the driver to reply with a text message. The only menu option on the MCT will be REPLY.
o 0: default value. Allows the driver to reply with the same form message. The menu options on the MCT will be DELETE, SAVE, REPLY.
o Any positive number: Forces the driver to reply with the form indicated by this TotalMail form ID. If the number is different from the TotalMail form ID of the auto-prompt form and is a valid TotalMail form ID, an empty form will be prompted to the driver, otherwise the behavior is the same as for -2. The only menu option on the MCT will be REPLY.
• Reply Form ID Late: Not used.
• Detention Warning Interval: Minutes of detention until a warning prompt displays in cab.
• Detention Warning Method: Controls whether and how a detention warning is issued in cab. Any invalid value results in no in-cab detention warning.
o -1: Use TMWSuite rules, and get detention warning minutes from TMWSuite, instead of from Detention Warning Interval. The rules are based on the value of cmp_det_start:
▪ 0 acts like 0, that is, none.
▪ 1 acts like 1.
▪ 2 or 3 acts like 2.
o 0: default value. No in-cab detention warning.
o 1: Detention time calculated from actual arrival at stop until actual depart.
o 2: Detention time calculated from the later of actual arrival time or ETA until actual depart.
• Driver Audible Prompt: If Yes, any in-cab prompt for the event will be accompanied by a beep.
• Driver Negative Prompt: If Yes, the MCT will prompt the driver when the event occurs. The event will be automatically accepted after a brief period of time, if the driver does not cancel it.
• Form ID Occur 2: The TotalMail form ID of a PACOS auto-prompt form that may be used, depending on Form ID Occur Rule.
• Form ID Occur 3: The TotalMail form ID of a PACOS auto-prompt form that may be used, depending on Form ID Occur Rule.
• Form ID Occur Rule:
o 0: default value. Use the form specified in Form ID Occur.
o 1: Same as 0.
o 2: If first stop, use Form ID Occur 2; if last stop, use Form ID Occur 3; otherwise, use Form ID Occur.
o 3: If first pick-up type stop, use Form ID Occur 2; if last drop type stop, use Form ID Occur 3; otherwise, use Form ID Occur.
o > 1000: Custom rule. Pick the form to use based on the results of stored proc tmail_gfc_pickform9999, where 9999 is this rule number value. Note: The template for this stored proc is tmail_gfc_pickform1000.
3 TL2000
1. In order to trigger the first PACOS Arrived event at a certain stop, the latitude and longitude values must exist in the Customer record. Make sure these values are reasonably accurate in your Company file. The values will be fine-tuned as PACOS Arrived events occur.
2. Set default geofence parameters. See the description in the TMWSuite section above. Similar fields exist in TL2000.
3. Use of PACOS can be limited to certain tractors by setting a field in Tractor File Maintenance.
4 TotalMail
1. Open the TMW PeopleNet Poller on the TotalMail agent computer.
2. From the Edit menu, select Poller Configuration.
3. Select the PeopleNet Requester tab:
[pic]
4. Enter values in the following fields:
|PACOS Events Form ID’s |These are used for the mobile communication vendor form ID’s of the dispatch event forms.|
| |Using the standard PeopleNet form set imported with mobile comm information, the values |
| |for these fields would be: General = 390, Arrive = 391 and Depart = 392, Begin Trip = |
| |394, End Trip = 395. The value must be a number less than 400, because the form exists |
| |in TotalMail only. |
|PACOS Geocode Form ID |This is used for the mobile communication vendor form ID of the geocode response form. |
| |Using the standard PeopleNet form set imported with mobile comm information, the value |
| |for the field would be 393. The value must be a number less than 400, because the form |
| |exists in TotalMail only. |
5. Select the PACOS Trip tab:
[pic]
Note: All of these settings (except for Clear PACOS Dispatches from MCT) must be made by opening the PeopleNet Poller on the TotalMail agent computer. This applies even if you are running the PeopleNet Poller on a different computer than the TotalMail agent computer. Use Trips and Replace only stop on disp edit must also be set on each PeopleNet Poller that you are running. Clear PACOS Dispatches from MCT need only be set on each PeopleNet Poller that you are running.
6. Select the desired options::
• Use Trips: Select this box to cause a PACOS Dispatch to be sent as a trip. Clear this box to send PACOS Dispatches the old way, not as a trip. When this box is cleared, none of the settings that are indented from this one in the window will be in effect.
Note: Before selecting this option, make sure you have updated your PACOS event forms (PACOS Arrival, PACOS Departure, PACOS Event) to the PACOS 2.6 version (TotalMail version 6.4.1384) or later.
• Call on trip start.: Causes an immediate data call from the MCT when the MCT creates a PACOS Trip Start event.
• Call on trip end.: Causes an immediate data call from the MCT when the MCT creates a PACOS Trip End event.
• Auto Start: Causes the MCT to start a trip automatically at the planned trip start time.
• Auto End: Causes the MCT to end a trip automatically when all events (approaching, arrived, departed) have occurred on the last stop. The MCT prompts the driver to confirm the end of trip.
Note: At least one of Auto End and Driver End should always be selected.
• Driver End: Enables the driver to manually end a trip.
Note: At least one of Auto End and Driver End should always be selected.
• Trip Start Driver Neg GUF: Causes the prompt to the driver for starting a trip to be accepted after a brief period of time, if the driver does not cancel it. If this box is cleared, the driver must respond to the trip start prompt.
• Enforce stop sequence: Select this box to prevent automatic PACOS events (approaching, arrived, departed) from occurring on a stop, until all the events from the prior stop have occurred. This does not prevent the driver from manually arriving and departing from any stop. Clear this box to use the old method where all stops events are always eligible to automatically occur. Note: TMWSuite does not allow stops to actualize out of sequence, so we recommend setting this box ON.
• Clear PACOS Dispatches from MCT: Select this box to clear all PACOS dispatches from the MCT, before a new PACOS dispatch is sent to the MCT. The main purpose of this option was to keep trips separate on the MCT. If Use Trips is set, then this option is not needed for that purpose, but you may still want to use it to have just the last load assignment sent on the truck.
• Replace only stops on disp edit: Select this box to keep the same PACOS dispatch on the MCT when updating the PACOS dispatch, and to only replace the stops. If this box is not selected, the entire PACOS dispatch would be replaced, which could cause an extra PACOS Begin Trip message to be created.
• Use stop city time zone: Select this box if your dispatch system is set to keep arrival and departure times in terms of the stop’s time zone.
• Scheduled Time Method: Specifies how to set scheduled time on the stops for a PACOS Dispatch message. The scheduled time affects when late events are created, and is shown to the driver on the PACOS stop display. The possible settings and their meanings are:
➢ Form Flag field: Defined on load assignment form. The standard load assignment form is set to use Scheduled Latest if set, otherwise use Planned Arrival.
➢ Latest Scheduled Time: Always uses Scheduled Latest.
➢ Planned Time: Always uses Planned Arrival.
➢ Latest Scheduled or Planned: Uses Scheduled Latest if set, otherwise uses Planned Arrival.
7. From the TotalMail Viewer Tools menu, select Viewer Options, and then the Priority Handling tab. The settings in this tab allow you to configure how your PC will notify you that mail of a certain priority has arrived in your TotalMail mailbox:
[pic]
For example, to cause high priority messages (such as late warning events from PACOS) to put a red mailbox icon in the system tray, perform the following actions:
A. In the Show Notification section at the top of the tab, select Specific Priorities.
B. In the drop-down list field immediately underneath the Show Notification section, select high.
C. Select the Show Icon in Tray check box.
D. In the drop-down list for the Icon to use in Tray field, select .
3 Operation of PACOS
1 Circle of Service Example
The following example is based on using the standard PeopleNet forms supplied with TotalMail, and some of the example settings described above.
Note: Unless otherwise noted, similar actions occur in either TMWSuite or TL2000.
1. TotalMail receives an Empty at Consignee form message, which triggers it to automatically create the next Load Assignment message for the truck.
2. TotalMail processes the Load Assignment’s views to fill the fields. In doing so, it encounters the Trigger Special Message view, which directs it to create a separate PACOS Dispatch message. The PACOS dispatch message goes out with the following parameters:
|Evt |CompID |
|TMUpdCmpLatLong Tolerance |This setting determines: |
| |The allowed distance from a company’s current position a GPS sighting to be considered to be in |
| |tolerance. |
| |If a GPS sighting is out of tolerance, whether the system will generate an error in TotalMail. |
| |Your entry in the Int1 field specifies the maximum number of miles a GPS sighting may be from a |
| |company’s currently recorded location to be considered in tolerance. Only those GPS sightings that |
| |are in tolerance will be used to auto-tune the company’s latitude and longitude data. An out of |
| |tolerance sighting will not be averaged into the current lat-long. |
| |–1 |
| |Turn off tolerance checking. (default) |
| |Your entry in the String 1 field controls whether a GPS sighting that is out of tolerance will |
| |trigger an error in TotalMail. The options are: |
| |E |
| |Generate an error if the GPS sighting is out of tolerance. |
| |I |
| |Ignore an out of tolerance GPS sighting. (default) |
1
2 Operation
When a driver arrives at a company destination, the PeopleNet mobile communication terminal prompts the driver to confirm the arrival. When the driver confirms the arrival, the standard PACOS Arrived macro, containing a GPS sighting, is sent to TotalMail. The lat-long tuning process works as follows:
• If the company lat-long is set to -1, no tuning occurs.
• If the GPS sighting is out of tolerance, no tuning occurs. If String1 in the TMUpdCmpLatLong Tolerance key is set to E, the Arrived message is failed by TotalMail and set with error information.
• If the GPS sighting is within tolerance and a lat-long does not exist for the company, the GPS sighting is set as the new lat-long.
• If the GPS sighting is within tolerance and a lat-long exists for the company, the value in the Times Verified field increments, and the company lat-long is averaged to include the new lat-long, weighted according to the verifications count.
2 EDI Auto-214’s
This function applies to TMWSuite only.
You can set up customer-defined EDI events to automatically create an EDI 214 (shipment status) message when a PACOS event occurs. For example, to define a 214 to be sent to a particular trading partner whenever a running late condition to a drop location is detected, follow these steps:
1. In System Administration, go to the Edit menu and select GeneralInfo Table.
2. In the GeneralInfo Table window, scroll down to the TMStatEDICode_LTARVG key.
3. For that key, set the String1 column to the value for an unused customer-defined EDI event code, e.g., CUST1.
Note: There are six available customer-defined EDI event codes, CUST1 through CUST6.
4. Click Save, then close the GeneralInfo Table window.
5. In File Maintenance, go to the Edit menu and select EDI Codes.
6. In the EDI Codes Maintenance window, enter the ID of the trading partner in the Company field.
7. Go to the Auto 214 tab.
8. Click the Add button to enter a new auto-214 condition.
9. In the Activity field, select Custom Event 1 from the drop-down list.
10. In the Stop Type field, select Drop Locations from the drop-down list.
11. Set the rest of the columns as desired, and click Save.
Note: 1 Set Per Stop is not applicable.
3 Driver-initiated PACOS dispatch
This function applies to TMWSuite only. For TL2000, see the Driver Requesting Next Load section of this document.
The standard form set is designed to send the PACOS dispatch to the mobile communications unit (MCU) along with the Load Assignment form message. You may want to allow the driver to initiate delivery of the PACOS dispatch to his MCU, if for example you send all of a truck’s Load Assignments for the day at once. In that case, several PACOS dispatches would be on the MCU, which could result in confusion, especially if some of the stops were the same. The following procedure allows for driver-initiated PACOS dispatches, instead of delivering them with the Load Assignment. The driver would request a PACOS dispatch by sending in the Begin Trip form message.
1. Import the Begin Trip form from the file TmwsPnetBeginTripPacosDispatch.xml, replacing your current Begin Trip form. During the import, select these settings:
• Import Mobile Communication Types
• Add New Version but preserve Form ID’s
• Current
The form’s status will go from Pending to Current upon the next cycle of the TotalMail PeopleNet Poller.
2. Edit your Load Assignment form to delete the Trigger Special Message view. Click Create to create a new version. Set the version’s status to Current.
4 PACOS Assignment form
This function applies to TMWSuite only.
The PACOS Assignment form is available with the standard TMWSuite PeopleNet form set. It is used to trigger a PACOS dispatch from an inbound form message, such as the Begin Trip (see the Driver-initiated PACOS dispatch section above). This form message can also be sent by the dispatcher to send a PACOS dispatch without a Load Assignment message. The PACOS Assignment form message does not go to the driver; instead, it triggers the PACOS dispatch. If you want the driver to also see the PACOS Assignment form, edit the form as follows:
1. At the top of the Mapping tab, select the General display option.
2. Select the Trigger Special Message view.
3. Find the Replace the Original Msg check box and clear it.
[pic]
5 City Stops
This function applies to TMWSuite only.
With the standard forms, the TotalMail-PeopleNet interface sends only stops at company locations to PeopleNet. If you have stops that do not have a known company and you would like to include them among the PACOS stops using city data, modify your forms that trigger the geofence special message as described here. The driver would then see the city stops along with the company stops in the PACOS stops list. You could configure the system so that upon arrival at a city stop, the driver would select the stop and manually send an arrival. Alternately, you could configure the system so that the driver gets the arrived prompt when stopped within the city.
1 Setup
1. In the form editor, add a pair of invisible fields to the form that triggers the geofence special message, e.g., the Load Assignment or PACOS Assignment form.
2. Map the fields to a Field Name/Field Value view field pair in the Trigger Special Message view. For example, the Field 3 Name and Field 3 Value view field pair could be used. Enter the default properties to set a value for the CityRadiusAdd field.
3. Set the Default property of the Field Name to CityRadiusAdd.
4. Set the Default property of the Field Value as follows:
• OFF
Do not use city stops.
• 0
Use feature with 0,0 lat-long.
• Greater than 0
Use feature with city record lat-long.
The default Field Value is OFF.
If CityRadiusAdd = 0, a lat-long of 0,0 will be used for the PACOS stop. The effect would be that PACOS occur events would never be created automatically, since the vehicle would never get to the geofence centered at 0,0. Also, the timeout fields from the geofence parameter records would be set to -1, which means that no PACOS late events would be created.
If CityRadiusAdd is a value greater than 0, the lat-long of the city record will be used for the PACOS stop. Also, the Radius fields from the geofence parameter records would be increased by the value of this field.
For example, assume the following Radius values from geofence parameter records:
• Arrived = .5
• Departed = .6
• Arriving = 60
If CityRadiusAdd = 20, the Radius values would be changed to:
• Arrived = 20.5
• Departed = 20.6
• Arriving = 80
The effect would be that the PACOS events would be triggered as usual. The larger radius values allow for the fact that the lat-long of the stop is approximate.
The standard forms that would need to be modified are the Load Assignment and the PACOS Assignment.
When the driver does the manual arrival, the lat-long would not cause any update in TMWSuite.
The geofence special message program will check for existence of the CityRadiusAdd parameter, and process according to its value as indicated above.
When the program encounters a stop without a company, and the CityRadiusAdd value is greater than or equal to 0, the geofence special message program will use data from the city record (instead of the company record) for the PACOS stop name and description. The city name will appear in the PACOS stops list on the mobile communication terminal (MCT).
Other geofence parameters will be taken from the geofence parameter records for all companies (Company = UNKNOWN) as usual.
6 Clear PACOS dispatches
Stops from a prior PACOS dispatch may be left on the MCT while the vehicle is running its current trip. That may occur, for example, if a driver failed to respond to an Arrived prompt, or if the final depart event did not occur. To ensure that no stops from a prior dispatch are left on the MCT, select the Clear PACOS Dispatches from MCT check box on the PeopleNet Requester tab of the Poller Configuration window. For more information, see the PeopleNet Requester configuration panel section of this document.
The TotalMail - PeopleNet poller checks the Clear PACOS Dispatches from MCT setting before it sends a PACOS dispatch. If set, then for each current dispatch of the vehicle, the poller issues a request to PeopleNet to delete the dispatch. That request will be sent to PeopleNet just before the new PACOS dispatch.
7 Geocoding
This description applies to TMWSuite only. See the TL2000 PACOS Features section of this document for a description of geocoding with TL2000.
1 Setup
1. To use the PACOS geocoding feature, upgrade to TotalMail version 6.4.925 or later.
2. To enable automatic creation of a geocode request when a stop is saved, e.g., in Order Entry, upgrade to TMWSuite version 2003.03_03.0549 or later. Without this upgrade, geocoding can still be done by sending a geocode request message for a company from the TotalMail Viewer.
3. For automatic creation of a geocode request when a stop is saved, select the Enable Agent Sourcing of dispatch messages field on the Dispatch System tab of the Transaction Agent Properties window.
4. Check the TotalMail form editor to make sure your forms include the Geocode Request and Geocode Response forms. If not, import them from TmwsPnetFormSet.xml (version 6.4.925 or later). If the default form IDs are available, import with new version preserving form IDs; otherwise import renumbering form IDs. Select the Import Mobile Communication Types check box, and import with status as Pending.
5. Allow the TotalMail PeopleNet poller to cycle to make the two imported forms current.
6. In TotalMail Configuration, add a mobile communication unit with an ID such as !GeocodeServer. Select PeopleNet as the Mobile Communication Type. This unit will be used for addressing geocoding messages only. It does not have a corresponding Vehicle in the PeopleNet PFM web program.
7. Add a TotalMail truck of the same name (!GeocodeServer) as the mobile communication unit from the previous step, and assign that mobile communication unit to it. Put the truck into a dispatch group.
8. In TMWSuite System Administration, open the General Info Table and configure the TMGeocoding key as follows:
A. Set the value of the String1 field to the form ID for Geocode Request (96, if imported preserving form ID's).
B. Set the value of the String2 field to the TotalMail truck name for geocoding messages (!GeocodeServer).
2 Operation
1 Automatic creation of a Geocode Request message
In TMWSuite, whenever a stop is saved, a trigger procedure checks whether a geocode request message should be created. The procedure requests TotalMail to create the message if both of the following conditions exist:
• The String1 field of the TMGeocoding key in the General Info Table contains a valid, positive number. This is the TotalMail Geocode Request form ID.
• The company’s Lat and Long are not set or are 0, or its Times Verified field is not set or is 0.
If Enable Agent Sourcing of dispatch messages is selected, the TotalMail Transaction Agent creates a Geocode Request message.
2 Manual creation of a Geocode Request message
You can manually create a Geocode Request message to geocode a single company.
1. Select the Geocode Request form from the New Form Message selection on the Compose menu of the TotalMail Viewer.
2. Address the message to the geocoding TotalMail truck (for example, !GeocodeServer).
3. Enter the Company ID.
4. Select Auto-fill from the File menu of the composition form. The system will respond by displaying the company’s address.
5. Select Send from the File menu to send the message.
3 Processing of the Geocode Request
1. The Transaction Agent processes the Geocode Request message, creates a PACOS Geocode Request special message, and deletes the original Geocode Request message.
2. The TotalMail - PeopleNet poller processes the PACOS Geocode Request message, requests and receives geocoding from PeopleNet, then creates a Geocode Response message.
3. The Transaction Agent processes the Geocode Response message, updates the Lat and Long fields of the TMWSuite company profile, and increments the profile’s Times Verified field, e.g., if it was 0, it would be increment to 1.
4. After processing is complete, the PACOS Geocode Response message resides in the dispatch group’s Inbox. In addition to latitude and longitude, the message contains a Quality field that indicates how good the address match was. The possible Quality values are:
• 0
Matched the exact address.
• 1
Matched to the vicinity of the street.
• 2
Matched to the postal code.
8 Stop Groups
This function applies to TMWSuite only.
If, at dispatch time, you have cases where a stop can occur at any of several locations, and you do not know which, you might want to configure stop groups. The dispatcher could plan to the group or any one of its member companies. When the truck arrives, PACOS sends in the actual location and, if different from planned, TotalMail switches that company’s stop from planned to actual.
1 Setup
To get the PACOS Stop Group feature, upgrade to TotalMail version 6.4.942 or later.
Import the new versions of the PACOS EVENT, PACOS ARRIVAL, and PACOS DEPARTURE forms from TmwPnetFormSet.xml, dated 9/7/04 or later, and make them current.
Notes:
1. De-select all forms other than the three listed above.
2. If your current forms have the standard TotalMail form ID’s (90, 91 and 92) and PeopleNet ID’s (390, 391 and 391), select Import Mobile Communication Types, Add New Version but preserve Form ID’s, and Import with current status as Pending.
Modify the new current PACOS ARRIVAL form as follows:
1. Add the Switch Stop Company view as the first for the form.
Instructions using the old form editor:
A. Bring up the standard PACOS ARRIVAL form in the form editor.
B. Click Select Views, and add the Switch Stop Company view to the Selected Views list.
C. Use the UP ARROW key to make the Switch Stop Company view the first one in the list.
D. Click OK.
2. Map the Company ID field in the form to the Company ID field in the Switch Stop Company view.
Instructions using the old form editor:
A. Select the Company ID field in the form image pane.
B. Select the Field/Label tab, and the Browse button to the right of the Mapping field.
C. From the Map Form Field box, expand the Switch Stop Company view, and put a checkmark on the Company ID field. Click OK.
3. Map the Stop Number field in the form to the Stop Number field in the Switch Stop Company view..
4. Save the form version and make it Current.
Instructions using the old form editor:
A. Click Save to create the new form version.
B. From the form list, expand the PACOS ARRIVAL form, right-click on the new working version and select "Set to Current.”
C. After the next PeopleNet poller cycle, the modified version of the PACOS ARRIVAL form will become Current.
5. Set the system to carry only one PACOS dispatch at a time on a mobile unit:
A. Select Poller Configuration from the Edit menu of the PeopleNet poller.
B. Click the PeopleNet Requester tab.
C. Put a checkmark in the Clear PACOS Dispatches from MCT field.
D. Click OK.
Make sure that you do not inadvertently already have stop groups set:
1. From Query Analyzer, run the following query:
select cmp_billto, cmp_mastercompany, * from company
where isnull(cmp_billto,'') 'y'
and isnull(cmp_mastercompany,'')''
and isnull(cmp_mastercompany,'')'unknown'
2. For any company shown in the query results, edit it in company file maintenance to either change the DivOf/Parent field to UNKNOWN or change the Bill To field to checked.
Set up a Stop Group as follows:
1. Define a stop group as a parent company in TMWSuite. In Company File Maintenance, add a company to represent the stop group, for example, GRPKC, Kansas City Group. Under Switches on the right of the screen, check Parent.
2. Bring up each company that will be a member of that group. Make sure that Bill To (under Switches) is not checked; otherwise, TotalMail will not include it in the group.
Note: In TMWSuite, the Parent Switch and DivOf/Parent fields are used for billing rates and the Customer Service report in Order Entry. Those usages only apply to a company that is a Bill To. The requirement for PACOS Stop Groups that the member company not be a Bill To avoids a conflict with those usages of the fields.
3. Type the company ID (for example, GRPKC) of the stop group (parent) company into the DivOf/Parent field.
4. Save the company record.
Finally, turn on the PACOS Stop Group feature:
1. In System Administration, select GeneralInfo Table from the Edit menu. Scroll down to the TMSwitchStpCmpWithinGrp key.
2. Set the value of the String1 field to Y.
2 Operation
In Order Entry or Dispatch, when use of a stop group is needed, enter either the stop group (parent) company or a member company of the group. You may want to enter a member company, for example, if it is the preferred or most likely location among the member companies.
Note: When you use a stop group, you cannot override the Arriving radius and timeout parameters for that stop from Dispatch. The original Geofence Default parameter record will be used.
When TotalMail creates the PACOS Dispatch message (usually when the load assignment is sent), it includes all of the member companies of that stop group.
After the PACOS Dispatch message is delivered to the mobile unit, each of the companies of the stop group could be seen as a separate stop through the PACOS Stops selection of the Menu on the mobile unit.
When the truck arrives at one of the stops of the group, upon confirmation from the driver, a PACOS Arrival event is sent in for that stop.
Note: If an auto-prompt form is presented to the driver, any pre-filled stop data will be that of the stop originally planned in dispatch, not necessarily that of the stop actually arrived at.
When TotalMail processes the PACOS Arrival message, it updates the TMWSuite trip segment’s stop, switching from the planned company to the company actually arrived at, if different.
When the next PACOS Dispatch message is sent, the stops left over from the previous trip, including those of the stop group that were not arrived at, are cleared from the mobile unit.
9 Stop Name Format
When the driver selects the PACOS stops item from the mobile terminal’s menu, he sees a list containing the stop name of each stop on the unit. The system sends the stop name along with the other stop data in the PACOS dispatch message. By default, the stop name is set to the company name. You can specify a different stop name to make it more meaningful to the driver. For example, you may want to indicate, the company ID, the trailer ID, and whether the stop is a pickup or drop.
1 Setup
1. In the form editor, add a pair of invisible fields to the form that triggers the geofence special message, e.g., the Load Assignment or PACOS Assignment form.
2. Map the fields to a Field Name/Field Value view field pair in the Trigger Special Message view. For example, the Field 3 Name and Field 3 Value view field pair could be used. Enter the default properties to set a value for the StopNameFormat field.
3. Set the Default property of the Field Name to StopNameFormat.
4. Set the Default property of the Field Value as follows:
• Enter a string of alphabetic characters for the data that you want to appear. Make the string as long as the maximum amount of characters that you want to show of that data. Place the string in the position where you want the data to appear. The alphabetic characters that can be used to represent data are:
• a: address 1; company.cmp_address1 (1)
• b: address 2; company.cmp_address2 (1)
• c: company ID; stops.cmp_id
• d: scheduled arrival date in mm/dd format; stops.stp_arrivaldate or stops.stp_schdtlatest
• e: stop event; stops.stp_event
• h: scheduled arrival time in hh:nn format; stops.stp_arrivaldate or stops.stp_schdtlatest
• i: city name, state county; city.cty_nmstct
• n: company name, or if a city only stop, city name; company.cmp_name or city.cty_nmstct
• t: trailer ID; event.evt_trailer1
• y: stop type; stops.stp_type
• any other alpha character: nothing displayed
• Enter non-alphabetic characters (like a space or a dash) that you want to have displayed in the position where you want the data to appear.
• Remember that the PeopleNet mobile terminal displays the stop name on one line that is a maximum of 19 characters long.
2 Example of a format string
To display the first character of the stop type, a dash, the company ID, a space, and the trailer ID, use this format string:
y-cccccccc ttttttttttttt
The table below illustrates the data that would display on a terminal if the above format string was used for two sample stops:
|Stop Type |Event |Company ID |Trailer |Data displayed on terminal |
|PUP |LLD |ACME |T0123456789 |P-ACME T0123456789 |
|DRP |LUL |ZAXXON |T0123456789 |D-ZAXXON T012345678 |
Notes:
1. Only the first character of the stop type is displayed, because there is only one y in the format string.
2. The full company ID is displayed with no additional spaces added, even though there are eight c’s in the format string.
3. The trailer ID is not completely displayed for the second stop, because the mobile terminal only shows up to 19 characters on a line.
10 Changing a custom load assignment form to use PACOS
If you have a custom Load Assignment form, you can upgrade it to work with PACOS.
1. We recommend using the advanced form editor. From the TotalMail Viewer Tools menu, select Viewer Options. Select the Use advanced form editor check box.
2. Bring up the standard Load Assignment form that you imported as Working.
3. Scroll to the bottom of the form, and note the six invisible fields. You will need to duplicate these fields on your custom Load Assignment form. The properties of these six fields are:
Name: fldSpecial Message Type ID
Default: TmwGeoFn.GeoFenceSpclMsg
Mapping: Trigger Special Message.Special Message Type ID
Name: fldField 1 Name
Default: LegHeaderNumber
Mapping: Trigger Special Message. Field 1 Name
Name: fldField 1 Value
Mappings:
Trigger Special Message. Field 1 Value
Load Assignment.Leg Header Number
Name: fldSubject
Default: PACOS Dispatch
Mapping: Trigger Special Message.Subject
Name: fldPageOneOnly
Mapping: Trigger Special Message.Page 1 Only
Name: fldPriority
Default: 2
This evaluates to medium priority, which is usually set for immediate delivery.
Mapping: Trigger Special Message.Priority
If your custom Load Assignment maps the Load Assignment.Flags field, you should also map that field to the Trigger Special Message view, to keep dates consistent between the load assignment and PACOS dispatch. The Trigger Special Message view recognizes only the +32 flag, Old Earliest/Latest Times. Set two invisible fields as follows:
Name: fldField 2 Name
Default: Flags
Mapping: Trigger Special Message. Field 2 Name
Name: fldFlags
(This is the existing field mapped to Load Assignment.Flags.)
Mappings:
Load Assignment.Flags
Trigger Special Message. Field 2 Value
4. Bring up your custom Load Assignment form.
5. Add the Trigger Special Message view to your custom Load Assignment form.
6. Add the invisible fields to your form.
7. Click the Save or Create button to save the form as a new version.
8. Right-click on the new version and select Set to Current.
9. The form status will change to Pending. After the PeopleNet Poller cycles, the form status will change to Current.
4 TL2000 PACOS
This section describes the unique features and operations of the TL2000 PACOS implementation.
1 Dispatch
The successful load assignment will trigger the creation of the PACOS dispatch message (from the assigned load message) and the needed PACOS dispatch edits (from the additional stops message).
In creating the PACOS dispatch message and dispatch edits, TotalMail will look up the form definitions for the specified auto-prompt forms, and pre-fill the specified data from the load assignment.
Note: PACOS allows just one auto-prompt form per stop.
A PACOS dispatch can be updated by sending a new load assignment.
A PACOS dispatch can be cancelled by sending a cancel dispatch message from TL2000.
2 Geocoding
If the load assignment does not include all the needed lat-long data, the message will fail. The error will trigger a geocoding request(s) to PeopleNet to return the needed lat-long data. The geocoding response message will be sent to TL2000, which will update the customer record with the returned lat-long. Also, the geocoding response message will include the manifest# from the load assignment. Upon receiving the successful geocode response message, TL2000 will re-send the load assignment for the same manifest#.
Note: Alternatively, a geocoding request can be sent manually from TotalMail.
If the geocode request fails to return a lat-long, TotalMail will send a message indicating the failure back to the TL2000 dispatcher.
At customer maintenance, when a customer record is saved and a lat-long does not exist, TL2000 will send a geocoding request to TotalMail. A TL2000 setting enables this feature.
3 Event History
PACOS events can be stored in a history file in TL2000. TL2000 supports maintenance of and reporting from the history file.
4 Running Late
The Late Approaching event triggers a message to be sent to the driver. The message is intended to ask the driver to respond to the late message, for example, by sending in a Reason Late form message.
The Reason Late form message causes TL2000 to update to the PACOS event history record for the stop with the description entered by the driver on the Reason Late form.
5 Lat-Long Tuning
The lat-long for a customer can be tuned by successive arrivals at the customer site. There will be a TL2000 system setting for maximum number of tunings. After reaching that number, tuning will stop, and the lat-long value will be fixed.
6 Stop Time Zones
If time zone fields are set for a TL2000 customer record, they would be included in the load assignment data for the stop.
TotalMail will use the time zone data to return the PACOS event message times in terms of the time zone for the stop.
If no time zone data is configured for a TL2000 customer record, TotalMail will treat the time as being in the local time zone of the TotalMail agent machine.
7 Load Assignment Switches
TL2000 provides switches to control whether the text message and/or a PACOS dispatch is sent with a load assignment. If no PACOS dispatch is sent, then PACOS processing and events will not occur. Using these switches, you can configure for the following situations:
• Enabling or disabling PACOS for the system.
• Phasing-in PACOS by truck.
• Sending several load assignment test messages to a truck, but sending the PACOS dispatch for only the first.
• Enabling a driver to request and receive the next PACOS dispatch via an Empty at Consignee type form.
8 Driver Requesting Next Load
The system can be configured for the driver to request his next load using an auto-prompt form such as the supplied Consignee Stop Info form. When TL2000 receives the message with the next manifest# (Next Load# + Next Leg#) filled in by the driver, it will send a load assignment for that manifest#. If there is no next manifest#, and the tractor has not run the loads out of sequence, TL2000 will send the next planned load assignment. If there is no next manifest#, and the tractor has run a load out of sequence, TL2000 will not send a load assignment.
7 Maintenance and troubleshooting
After the TMW PeopleNet Interface is configured, there is no need for any regular maintenance. However, when problems arise, you can use the facilities described here to identify and correct them.
1 Error handling
When an error of a certain type (such as a communication error with the web or e-mail server) occurs in an operation, the polling session tries to give the condition a chance to clear itself. To that end, the polling session takes the following steps:
1. The program immediately retries the operation.
2. If the operation still fails, the program waits five minutes and then tries again.
3. The program repeats step 2 until the operation succeeds or until six tries have been made.
4. If the operation did not succeed in six tries, the program reports the error by creating and sending a message to the dispatch system. The TMW PeopleNet Interface then exits, leaving an error message window on the screen, and starts another run of itself. The new run of the program automatically starts a polling session and continues processing.
To summarize, if an operation fails continually with a certain kind of error for about 20 to 25 minutes, the program will report the condition to the dispatch system and restart itself.
For other types of errors, the TMW PeopleNet Interface immediately exits, leaving an error message window on the screen. The interface then restarts, and automatically resumes polling. Here is an example of the error window:
[pic]
Error messages
When a significant problem occurs with the mobile comm system, the TMW PeopleNet Interface sends notification to the dispatch system. The notification is in the form of a program-generated inbound message. There are several categories of these inbound error messages:
• Warnings of data failure. If need be, you can take action to resolve these warning situations. Examples:
From PeopleNet Interface 12/07 13:16:25:
Warning: Message checking cancelled.
Expired after 72.0 hours.
Driver did not read message.
Msg#: 12345678; Status: D
Trk#: 9999
Txt: HELLO – THIS IS A TEST
From PeopleNet Interface 12/07 14:16:25:
Warning: Message delivery failed.
Msg#: 12345679; Status: D
Trk#: 9999
Txt: HELLO – THIS IS TEST 2
PeopleNet could not deliver.
From PeopleNet Interface 12/07 14:46:25:
Warning: Position Request cancelled.
PeopleNet server could not process.
Trk#: 9999
Issued: 12/07 08:30
From PeopleNet Interface 12/07 14:56:25:
Warning: Possible dispatch data problem.
Please check & correct dispatch data.
…
• PeopleNet Control Center web server failure. You may need to contact PeopleNet support to resolve the problem. Example:
From PeopleNet Interface 12/07 15:16:25:
Web server has failed for 20 minutes.
Check your web connection to PeopleNet.
Contact PeopleNet or your ISP for help.
PeopleNet Interface program restarting.
Error 2203 in PeopleNetRequester.CleanResponse:
Invalid response code from PeopleNet server.
Internet connection may be down.
Please check by trying to bring-up a web page in your browser.
• POP3 e-mail server failure. You may need to contact your ISP to resolve the problem. Example:
From PeopleNet Interface 12/31 15:22:05:
E-mail server has failed for 20 minutes.
Please check your e-mail connection.
Contact your ISP for help.
PeopleNet Interface program restarting.
Error 2004 in PeopleNetMailReader.Connect:
Attempt to connect to e-mail server failed. E-mail server may be down.
iErrCode = 24110
• Dispatch data server failure. Please check your dispatch data server and connection. Example:
From PeopleNet Interface 12/31 14:49:20:
Error occurred in PeopleNet Interface.
Data server has failed for 20 minutes.
Please check your data connection.
PeopleNet Interface program restarting.…
• Other failures. You may need to contact TMW support. Example:
From PeopleNet Interface 12/31 15:49:20:
Error occurred in PeopleNet Interface.
Please notify TMW Support and send
Pnet.log & numbered .log files.
PeopleNet Interface program restarting.
…
• Interface down. This occurs when the program restarts, then fails again within one minute of when it started. Another error message precedes this one. Look at that message to determine the cause of the error. After the problem is resolved, you will need to start the TMW PeopleNet Interface manually.
From PeopleNet Interface 12/31 16:00:50:
PeopleNet Interface is DOWN!" _
Too soon since last restart.
Last restart was at 12/31/99 16:00
2 Outbound message failure
If an outbound message shows an error in the TotalMail Viewer, you can right-click and select Error Information to read a description of the error. TotalMail will also create an inbound warning message to the Administrator containing the error description.
1 Message size limit
PeopleNet limits the size of outbound messages to 2000 characters. If this limit is exceeded, TotalMail will mark the message in error and send a warning message to the Administrator.
2 Editing Pending Data
The TMW PeopleNet Interface keeps three files of pending transaction records: outbound messages waiting for status updates, position requests waiting for location updates and current PACOS dispatches waiting for the trip to be completed. You can view the contents of each of these files through the Edit menu. Although the program deletes expired records automatically, it provides the capability for you to select and delete records.
1 Pending outbound messages
Pending outbound messages are messages that have been sent but have not yet displayed on the mobile terminal. When the TMW PeopleNet Interface receives a message status of Read from the PeopleNet Control Center, it deletes the pending message record.
To view the pending outbound messages, from the Edit menu select Pending Outbound Messages. The program displays a window resembling the following:
[pic]
[pic]
The window shows the following fields:
• Serial#: message identification number assigned by the PeopleNet Control Center.
Truck#: PeopleNet’s identification number for the truck.
Status: contains one of the following codes:
P: pending, not yet delivered to the mobile unit.
D: delivered to the mobile unit, not yet read by the driver.
❑ Status Time: time that the current status was first attained.
❑ Pending Since: time that the message first attained Pending status, i.e., when the message was sent. The program calculates expiration time from this value.
❑ Delivery: type of delivery specified for the message. Contains one of the following values:
later: message was sent with store-and-forward delivery specified.
now: message was sent with immediate delivery specified.
❑ Text: content of the message.
To see more of the Text field, press the RIGHT ARROW key until it reaches the Text field. Press the LEFT ARROW key to return to view the other columns.
If there are more records than fit in the window, a scroll bar appears and allows you to view all the records.
To delete a record, first select it by clicking on the record or using the UP ARROW and DOWN ARROW keys. The left-most column shows an arrow on the selected record. Then, click the Delete button to remove the record from the view.
To close the window and save any record deletions, click the OK button.
To close the window without saving record deletions, click the Cancel button.
2 Pending On-Demand Position Request
An on-demand position request is a request for PeopleNet to get a new fix on the truck and add the new location record to the PeopleNet Control Center’s database. The request is pending until the new location record has been received by the TMW PeopleNet Interface. To view the pending on-demand position requests, select Pending On-Demand Position Requests from the Edit menu. The program displays a window like the following:
[pic]
The window shows the following fields:
❑ Truck#: PeopleNet’s ID number for the truck.
❑ Request Time: time the on-demand position was requested. The program calculates expiration time from this value.
If there are more records than fit in the window, a scroll bar appears and allows you to view all the records.
To delete a record, first select it by clicking on the on the record or using the UP ARROW and DOWN ARROW keys. The left-most column shows an arrow on the selected record. Then, click the Delete button to remove the record from the view.
3 Current PACOS Dispatches
The TotalMail - PeopleNet poller uses the list of current PACOS dispatches for deleting old dispatches, and for clearing dispatches from the MCT before a new one is sent. The list would be synchronized with the actual dispatches on the MCT, when a dispatch status request is issued. A dispatch remains in the list until one of those three operations deletes it. There is no function to delete the dispatch from the list when the last PACOS event from it occurs, as that is unknown to the TotalMail - PeopleNet interface.
To view the pending on-demand position requests, select Pending On-Demand Position Requests from the Edit menu. The program displays a window like the following:
[pic]
The window shows the following fields:
❑ TMWTripSegNum: The TMWSuite Trip Segment Number.
❑ TruckNum: PeopleNet’s ID number for the truck.
❑ PNetDispID: PeopleNet’s PACOS dispatch ID.
❑ Sent Time: time the dispatch was sent to PeopleNet. The program calculates expiration time from this value by adding the PACOS Dispatch Age Limit (see Polling Session configuration panel).
The records may be edited or deleted, but this would not be a normal case. Having extra dispatches in the list does not hurt operation of the system.
4 Pending Driver Log Hours Available Requests
A dispatcher can issue a driver log hours available request for a driver or to a truck from the Viewer. Until the TMW PeopleNet Interface gets driver log hours available data that is recent enough, or until a time limit has passed, that request will be pending and will show in this list. To view the pending on-demand position requests, select Pending Hours Available Requests from the Edit menu. The program displays a window like the following:
[pic]
To delete a record, first select it by clicking on the on the record or using the UP ARROW and DOWN ARROW keys. The left-most column shows an arrow on the selected record. Then, click the Delete button to remove the record from the view.
3 Process Log
The TMW PeopleNet Interface keeps a log of its activity. The log is kept in a file and is visible in the program’s main window (see Process Log Box earlier in this guide). The process log is valuable for resolving system problems.
When the TMW PeopleNet Interface starts, it opens the process log file. The process log file is a text file named Pnet.log and resides in the directory specified in the configuration window (see General Configuration Panel).
Periodically, the TMW PeopleNet Interface checks the size of the process log file. If the file size exceeds the configured maximum, the program renames it for back up and creates a new log file named Pnet.log. The program renames the log file to a name based on a number, for example, 00000000.log. If more than the configured maximum number of backup logs file exist, the program deletes the oldest.
The Process Log can use six kinds of messages:
❑ Basic: A basic message shows that a main event has occurred.
Example: ~16:38:28 12/28/99 - Polling session started.
❑ Detail: A detail message shows that a normal event has occurred.
Example: .16:49:50 Sending outbound messages and position requests ...
❑ Data: A data message shows that data is being sent or has been received, what the data contains, and its destination or origin. Examples are a message showing that a message history request is being sent to PeopleNet, and a message showing that inbound messages have been received from PeopleNet.
Example: >16:50:24 OUT - To PeopleNet: ******&service=mes_history&lastasn=10141915
❑ Debug: A debug message shows data useful for troubleshooting a problem.
❑ Example: =16:56:00 Loading saved polling session status.
❑ Warning: A warning message shows that an event occurred that might indicate a problem.
❑ Example: *16:35:33 Warning: Blank message (one with no text) received from PeopleNet. Skipping message.
❑ Error: An error message shows that a program operation failed or that bad data was found.
❑ Example: !16:38:48 Error occurred during 'Get Inbound Messages'. "Will retry operation on next tick of the polling timer. Error count: 1
The message types are distinguished by a starting character. In the process log box, they are identified by color (see chart). You can specify which message types to log through the Log Detail window. From the Edit menu, select Log Detail to bring-up the window:
[pic]
The checked fields indicate the message type that will be logged. Click the message type field to add or remove the check mark. Click OK to save the changes and close the window, or click Cancel to close the window without saving the changes.
What to log? During the start-up phase of using the PeopleNet system, keep a more detailed process log; for example, select the Basic, Detail, Data, Warnings, and Errors fields. After the startup phase, you can reduce the amount of messages logged; for example, select the Basic, Warnings and Errors fields. Basic and Error messages should always be logged, so the Basic and Errors fields should always be selected. Select the Debug field only under direction from TMW support personnel.
4 The About window
The About window shows the version number of the TMW PeopleNet Interface and provides links to TMW. To access the About window, select About from the menu.
[pic]
The version number is located in the upper right corner of the window.
To go to the TMW web site, click the Web Site link. To send an e-mail to TMW Support, click the E-mail link. Click OK to close the window.
8 Technical notes
The TMW PeopleNet Interface uses the Windows operating system registry for storing configuration parameters and some status information. The path to the program’s registry keys are:
❑ For the PeopleNet component: /HKEY_CURRENT_USER/Software/VB and VBA Program Settings/TMW Intouch Poller program parameters.
❑ For basic TotalMail: /HKEY_CURRENT_USER/Software/VB and VBA Program Settings/TotlMail/GenTMXfc-IntouchTmw.IntouchTmwDispatchXfc.
1 Verifying the POP3 e-mail account
1. From the Windows Start menu, select Run ... and enter telnet . For example:
telnet mail. 110
Note: The port# for POP3 is 110, by convention.
A window like the following will be displayed:
[pic]
Note: When you type the following commands, your keystrokes may not be visible in the window. If you mistype, the program responds as follows:
-ERR Protocol Error
In that case, simply enter the command again.
2. Enter a user name, for example:
user peoplenet
The system responds: +OK
3. Enter a password, for example:
pass shazam1
The system responds: +OK User successfully logged on.
4. Enter top 9999 0:
top 9999 0
The system responds: -ERR Message 9999 does not exist.
Note: Make sure the response is not a statement like Command not supported: TOP.
5. Enter quit to close the connection and window:
quit
The system responds: +OK
2 Switching dispatch systems
The following procedure switches the dispatch system that the PeopleNet Poller connects to. For example, to switch from TTS to TMWSuite:
1. From the Windows Start menu, select Run ... and type in regedit.
2. Navigate to HKEY_CURRENT_USER\Software\VB and VBA Program Settings\TMW Intouch Poller\PollingSession.
3. On the right side, find the value Name DispatchSystem.
4. Right-click on the value Name DispatchSystem, then select Delete.
5. At the prompt Are you sure you want to delete this value, click Yes.
6. Run the TotalMail PeopleNet Poller.
7. A window will pop up:
[pic]
• Make a selection in the Dispatch System area, for example, TMWSuite, and click OK.
8. The PeopleNet Poller runs. From the Edit menu, select Dispatch System Configuration, and, for TMWSuite, enter the parameters as described in Configuring the PeopleNet Dispatch Component Parameters earlier in this guide.
3 Additional Location Data
Since the PACOS 2.6 version of the TotalMail PeopleNet Interface, additional location data fields are available for queries in the position report files: tlblatlongs in TotalMail and checkcall in TMWSuite.
|tblLatLongs Field |Checkcall Field Name |Description |
|Name | | |
|Odometer |Ckc_odometer |ECM odometer reading, when available; otherwise holds the GPS odometer reading. 0 = |
| | |undefined. |
|Odometer2 |Ckc_odometer2 |GPS odometer reading, when ECM reading is available. -1 = not available. |
|Speed |Ckc_speed |ECM speed reading, when available, otherwise holds the GPS reading. -1 = not available. |
|Speed2 |Ckc_speed2 |GPS speed reading, when ECM reading is available. -1 = not available. |
|heading |Ckc_heading |In degrees, where 0 = N, 90 = E, 180 = S, 270 = W, 22.5 = NNE. -1 = not available. |
|Gps_type |Ckc_gps_type |0=breadcrumb, 1=other than breadcrumb, 2=vehicle start, 3=vehicle stop, +4=ecm odometer |
| | |exists, +8=ecm speed exists; -1 = not available |
|Gps_miles |Ckc_gps_miles |Miles traveled since last GPS fix. -1 = not available |
|Fuel_meter |Ckc_fuel_meter |Vehicle cumulative fuel consumption. -1=not available |
|Idle_meter |Ckc_idle_meter |Vehicle cumulative idle time in minutes. -1 = not available |
9
10 Decision Tree Forms
Draft; TotalMail version 6.4.1815
The TotalMail-PeopleNet Interface’s support for PeopleNet Decision Tree Forms (DTF) provides these features:
• Capability to define a PeopleNet form from the TotalMail Advanced Form Editor. You no longer have to enter a form in the PeopleNet PFM (web program) field-by-field.
• Branching: The driver can decide which sections of a form to fill out, without having to skip through all fields.
• Looping: The driver can fill in multiples of a set of fields, and stop without having to skip through unused sets of fields.
• Support for all driver sending options (forced urgent, forced deferred, optional) in PACOS auto-prompted forms.
1 Setup
To enable DTF support, set Form Script Use to Full on the General tab of the Poller Configuration window on the PeopleNet Poller Edit menu.
[pic]
The options in the Form Script Usage field are:
• None
TotalMail will not support PeopleNet forms created by script.
• Accept Inbound
Allows TotalMail to receive form messages of script-defined forms. We recommend not using this setting, but using the Full setting.
• Full
Full support for PeopleNet script-created forms, including defining the form scripts from the TotalMail Advanced Form Editor.
2 Form Editing
You can use the TotalMail Advanced Form Editor to define a PeopleNet form script by setting form and field properties.
1 Form Properties
[pic]
• Bi-Directional: For a PACOS auto-prompted form, or other form that the driver can read and reply with, set this to True; otherwise set this to False.
• Description: This becomes the PeopleNet form Description.
• Dimension: This defaults to 100 rows and 19 columns. For a return form or a forward form that is not to be displayed as text, you can widen the form by upping the columns. You may also increase the number of rows, if needed.
• Direction: For a forward (outbound) form, set to Forward. For a return (inbound) form or a PACOS auto-prompted form or other bi-directional form, set to Return.
• Force Priority: If you want to force the return form message to be sent urgent or deferred, without the driver choosing, set to True. Otherwise, to let the driver choose, set to False.
• Name: This becomes the PeopleNet form Name.
• Priority: For a return form, if Forced Priority is True, set to low for the message to be sent as deferred; or set to med, high or panic for the message to be sent as urgent. For a forward form, set to low for TotalMail to default sending the message deferred; or set to med, high or panic for TotalMail to default to sending the message urgent.
2 Field Properties
[pic]
• Branch To: For a return or auto-prompted PACOS form or other bi-directional form, you can use this property for either branching or looping (but not both).
• For branching, enter the Name of the field to branch to. After the driver enters this field, the PeopleNet mobile unit will skip to the field named here. See the “Branching and Looping” section below.
Note: For the branch to take effect, you must set Driver Edit to Optional or Required.
• For looping, you can enter begin cycle or end cycle commands. To begin a cycle on the field enter LOOP plus a loop ID, for example, LOOP1. To end a cycle on the field enter
-LOOP plus a loop ID, for example –LOOP1. To enter several loop commands for one field, separate them with a / (slash). For example, to end a (nested) inner loop 12, and an outer loop 1 on the same field, enter –LOOP12/–LOOP1. See the “Branching and Looping” section below.
• Description: This becomes the PeopleNet field Description.
• Dispatcher Edit: Pick No, if data should never be present when sent from TotalMail to the driver. Pick Optional, if you do not want PeopleNet to check for data present. Pick Required, if you want PeopleNet to reject the message if no data is present.
• Driver Edit: Pick No, if you do not want the field to appear to the driver when he fills out the form. Pick Optional, if you want the driver to have a choice in whether to put in data when he fills out the form. Pick Require, if you want to force the driver to put in data when he fills out the form.
• Extended Type: This property appears when you set Type to Extended Type. Between the Type and Extended Type properties, you can specify any PeopleNet field type:
|Type |Extended Type |PeopleNet Type |
|Date |- |Date |
|Generic |- |Text |
|Monetary |- |Text |
|Phone Number |- |Text |
|Positive Integer |- |Number (Enhanced) |
|Real Number |- |Number (Enhanced) |
|SSN |- |Text |
|Text |- |Text |
|Time |- |Time |
|Yes/No |- |Text |
|Zip Code |- |Text |
|Extended Type |Pnet:AutoDateTime |Auto date and time |
|Extended Type |Pnet:AutoFuel |Auto Fuel |
|Extended Type |Pnet:AutoLocation |Auto location |
|Extended Type |Pnet:AutoOdometer |Auto Odometer |
|Extended Type |Pnet:AutoVehicle |Auto driver name |
|Extended Type |Pnet:Barcode |Barcode scan |
|Extended Type |Pnet:DateTime |Date and time |
|Extended Type |Pnet:DisplayText |Display text |
|Extended Type |Pnet:LatLong |Auto lat / long |
|Extended Type |Pnet:MultiChoice |Multiple choice |
|Extended Type |Pnet:Password |Password |
|Extended Type |Pnet:SignatureCapture |Signature capture |
Notes:
1. All Auto fields must occur as a bunch at the end of the form.
2. A Pnet:DisplayText field requires the Description field to be set. The Description becomes the content of the PeopleNet Display text field.
3. A Pnet:MultiChoice field must have the Driver Edit field set to Required.
• Format String: Use this field with certain Field Types from this list:
• Positive Integer, Real Number: Enter four values, separated by commas. The four values are:
• 1st value: Show commas in number? 0 = no, 1 = yes.
• 2nd value: A prefix character that appears when the driver enters the number,
for example, $.
• 3rd value: Number of decimal places. 0 = none.
• 4th value: Justification when the driver enters the number. L = left, R = right.
Example: 0,,2,L means no commas, no prefix character, two fixed decimal places, left-justified. Leaving this field blank defaults to 0,,0,L.
• Extended Type - Pnet:MultiChoice: Enter the possible choices in quotes, separated by commas. If you want a particular choice to cause a branch, follow the choice by parentheses containing the Name of the field to branch to in quotes. For example: “Yes”,”No”(“EventCode”). See the “Branching and Looping” section below.
• Extended Type - Pnet:Barcode: Enter three values, separated by commas. The three values are:
• 1st value: Allow multiples barcodes to scanned into the field?: 0 = no, 1 = yes.
• 2nd value: If multiples are allowed, are duplicates allowed?: 0 = no (prevents barcode from being scanned twice), 1 = yes.
• 3rd value: If multiples are allowed, maximum number that can be scanned into the field.
• Max Value: Use this field for certain field types from this list:
• Positive Integer, Real Number: The maximum value allowed for the number.
• Extended Type - Pnet:Barcode: The maximum length of bar code allowed. 0 = any length, no maximum.
• Min Value: Use this field for certain field types from this list:
• Positive Integer, Real Number: The minimum value allowed for the number.
• Extended Type - Pnet:Barcode: The minimum length of bar code allowed. 0 = minimum length of one character.
• Name: This becomes the PeopleNet field Name.
• Prompt: This becomes the PeopleNet field Prompt. If blank, the system uses the Caption of the prior label on the form – if there is no intervening field and the label is on the same or prior line. If there is no such label or the label’s Caption is blank, the system uses the field Name as the PeopleNet field Prompt.
• Subject Flag: Use the value of the field as the PeopleNet form Subject? True = yes, False = no. This only applies to a field that is dispatcher editable (Dispatcher Edit = Optional or Required). The program will try to use the first field on the form that has this property set to True, in the case where more than one field is set to True.
3 Branching and Looping
1 Branching
A branch can be specified to always occur after a particular driver editable field, or a branch can occur after a multiple choice field depending on the choice the driver made.
The branched to field must be further on in the form (to the right on the same line, or on a following line). The branched to field cannot be inside of a loop that the branching field is not inside of, that is, you cannot branch into a loop from outside.
Example:
[pic]
In this example the driver would enter either Pieces and Weight, or Commodities, but not both. The mobile unit presents the prompt “Commodities?” to the driver. If the driver picks Yes, the unit skips to the “CommodityCode” field. If the driver picks No, the unit presents the next field, which is the “Pieces” field.
[pic]
After entering the Weight, the unit skips past the commodities fields, to the “EventCode” field. However that field and all of the following are not driver editable, so the form entry would be finished.
2 Making a loop
A loop consists of multiple cycles. A cycle consists of a group of fields, defined by a begin cycle command (for example LOOP1) in the Branch To property of the first field and an end cycle command having the same loop ID (for example –LOOP1) in the Branch To property of the last field. Create the first cycle of the loop, then make copies of the cycle (with the same loop ID) following the first cycle, until you have the maximum number of cycles that the driver can fill out. There can be no fields between cycles of a loop.
TotalMail uses the first cycle of the loop to create the form script lines for the fields of the loop – so the first cycle must have the exact specification. The other cycles need not have the exact specification, except for these rules:
• The first field of the cycle must have the same begin cycle command and loop ID as that of the first cycle.
• The cycle must have the same number of fields as the first cycle.
• The cycle’s fields must have the same field Type as the first cycle, or the Generic field Type.
• Numeric fields must have the same Format String as in the first cycle.
Example:
[pic]
First field of first cycle of loop 1.
[pic]
Last field of first cycle of loop 1. It is a multiple choice field that prompts the driver, “MORE?”. If the driver enters No, the mobile unit branches out of the loop to the “EventCode” field.
There are four cycles in loop 1. That is the maximum number of commodities, in this example, that the driver could enter.
3 Nested Loops
You can put a loop inside of a loop, such that all of the cycles of the inner loop are within each cycle of the outer loop.
It is possible that the inner loop would begin its first cycle on the first field of the outer loop’s cycle, or end its last cycle on the last field of the inner loop’s cycle. In these cases, there would be more than one loop command in the Branch To property.
For the first example, inner loop 12 is inside of outer loop 1 and begins its first cycle on the first field of the outer loop’s cycle. Branch To must contain: LOOP1/LOOP12.
For the second example, inner loop 12 is inside of outer loop 1 and ends its last cycle on the last field of the outer loop’s cycle. Branch To would contain: –LOOP12/–LOOP1.
3 Form Enabling
1 Procedure
To enable a form for use, you must:
• Create the form script.
• Enter the form script in the PeopleNet PFM program.
• Apply the PeopleNet form number to the TotalMail form.
1 Creating the form script
• From the TotalMail form editor, right-click on your new form version and select Set to Current. Enter 0 for the PeopleNet form ID and click OK.
• Allow for the TotalMail-PeopleNet poller to send messages.
• In the TotalMail Viewer, check the Admin Inbox. If the poller created the form creation script successfully, you will see two messages: MComm system wouldn't take form definition and FORM CREATION SCRIPT. You can ignore the MComm system wouldn't take message – it is just informing you that the TotalMail form’s status has been set back to Working, which is the normal occurrence.
• View the FORM CREATION SCRIPT message. Its content is the form creation script. Copy the form creation script to the system clipboard.
2 Entering the form script in the PeopleNet PFM
• In the PeopleNet PFM web program, click the Forms button, and click Create form via script to bring up the page to create a form from a script.
• Paste in the script from the system clipboard.
• Click the button to create the form.
• Bring up the main forms page. Find the new form and check the In-Use column. If the form is a new version of an existing in-use form, uncheck the In-Use column on the old version. Then click the Submit button.
Note: If the old version exists in any active or preplanned PACOS dispatches, unchecking the In-Use column will prevent the driver from completing those messages.
• Find the new form again in the list, and hover the mouse over the form name. Read and note down the form number at the lower left corner of the browser window. Alternatively, open the form and read the form number on the form display page.
3 Applying the PeopleNet form number to the TotalMail form
• From the TotalMail form editor, again right-click on your new form version and select Set to Current.
• Enter the PeopleNet form number noted in the prior procedure, and click OK.
• Allow for the TotalMail-PeopleNet poller to send messages.
• Check the TotalMail form editor. In a little while the form status will turn to Current. The form is now ready for use.
2 Error Reporting
During the “Creating the form script” procedure, if TotalMail detects an error that would prevent a good PeopleNet form script from being created, TotalMail reports the error. Instead of getting the regular two messages (MComm system wouldn't take form definition and FORM CREATION SCRIPT) in the Admin Inbox, you would instead get a Form Definition Failed message. The message contains three sections, separated by dashed lines. The first section contains the regular TotalMail error traceback information, the second contains a message for each error detected, and the third contains the (bad) form script that would be created. For example, if there were a backward branch, and a branch to a non-existent field name, you would get a message like:
Form Definition Send Problem
Form ID:202 (Version: 18):: MComm System: IntouchTmw.IntouchTmwDispatchXfc
MComm system wouldn't take form definition:IntouchOutboundMsg.Create:
Form definition error:
TmwPnetI(6.4.1806).PnetFormDef.Fdl (Property Get):
TmwPnetI(6.4.1806).PnetFormFdl.Text (Property Get):
Could not create form definition script:
----------------------------------------
Field# 6: Backward branch to field# 5, name fldPieces.
Field# 10: Branch-to field name EventCodeXXX not found.
----------------------------------------
Script: form_header_info("FDL: PICKUP INFO (PACOS)","Stop Update (Arrive at Shipper)",can_send,can_send_force_deferred)
field_text("Order#","",not_editable,required)
field_text("TRAILER#:","",optional,optional)
field_text("BOL#:","",optional,optional)
field_multiple_choice("Commodites?","",required,not_editable,"Yes"("CommodityCode"),"No")
field_number("Pieces:","",optional,optional,0,999999999999,0,"",0,left-justify)
field_number("Weight:","",optional,optional,0,999999999999,0,"",2,left-justify)
branch_to("EventCode")
branch_target("CommodityCode")
loopstart(4)
field_multiple_choice("COMMODITY CODE","",required,not_editable,"Apples"("Quantity"),"Bananas"("Quantity"),"Cantaloupes"("Quantity"),"Dried Apricots"("Quantity"),"Figs"("Quantity"),"Other")
field_text("Description:","",optional,optional)
branch_target("Quantity")
field_number("QUANTITY","",required,not_editable,0,999999999999,0,"",0,left-justify)
field_multiple_choice("MORE?","",required,not_editable,"Yes","No"("EventCodeXXX"))
loopend
branch_target("EventCode")
field_text("Event:","",not_editable,optional)
field_text("Company:","",not_editable,optional)
field_number("Stop#:","",not_editable,required,-999999999999,999999999999,0,"",0,left-justify)
field_auto_location
field_auto_latlong
Form Definition Failed
11 Revision log
❑ 08/21/02: Added to “PeopleNet Forms Setup”, “PowerSuite”: Note: A form’s MobileComm Version should be blank, and the Status should be “Current”. Added: “TotalMail Configuration Utility” section with “The MobileComm Unit ID should be entered as a numeric, without leading zeroes.” Changed domain name to . Added to “PeopleNet Poller Program Parameters”: “To avoid extra processing on the first run of the interface, you may want to set the Last Audit Serial No. to a recent value. Contact PeopleNet to get the value.” Change “Process Log” to: “the program keeps 1 backup log file of about 1MB”
❑ 09/27/02: Removed references to TTS – separate TTS manual should be used. Changed “PowerSuite” to “TMWSuite”. Changed to: “Make sure that you have received the TotalMail installation CD.”
❑ 04/30/03: Added Imessage enhancements.
❑ 01/19/04: Added PACOS upgrade section. Revised Imessage upgrade section. Added a procedure, Switching Dispatch Systems.
❑ 02/12/04: Added Dispatcher-initiated PACOS dispatch and added a step to Imessage Upgrade for not using PACOS.
❑ 03/16/04: “Enabled Extended Properties” removed with version 6.4.785. TMWSuite version 2003_03.151 required for PACOS. Geofence support license required. Imessage Upgrade procedure: request PACOS forms from PeopleNet too.
❑ 03/19/04: Added Get Current Positions operation.
❑ 03/30/04: Add Radius = -1, and Keeping events and stops out of PACOS.
❑ 04/05/04: Add City Stops section to Customization of PACOS.
❑ 04/21/04: Add to Polling Session configuration panel, PACOS Disp Age Limit. Add to PeopleNet Requester configuration panel, PACOS Event Form ID’s and Clear PACOS Dispatches from MCT. Add to On-Demand Dispatch Status Request, description of Current PACOS dispatches synch function. Add Clear PACOS dispatches & Current PACOS dispatches.
❑ 08/16/04: Corrected Lat-Long tuning section heading. Added warning note about date-time field mapping. Added: Unit ID must match PeopleNet’s Vehicle Number. Added new forms to standard forms import. Added “Upgrading from Older Versions” section and put Imessage and move PACOS upgrade instructions there. Added Lat-Long tuning tolerance documentation. Added Geocoding sections.
❑ 09/08/04: Added PACOS Customization, Stop Groups.
❑ 09/13/04: Added TMWS version# for Geocoding.
❑ 01/06/05: Advise against setting Last Audit Serial No. to 0.
❑ 01/07/05: Add instruction to disable PACOS to installation procedure. Add user rights and IP address requirements to PNet account setup. In circle of service example show PACOS Arrival and Departure messages.
❑ 02/08/05: Add TMSwitchCmpStpWithinGrp General Info setting in PACOS Stop Groups.
❑ 03/14/05: Stop Groups: instruction about avoiding stop group was backwards for bill-to setting.
❑ 05/02/05: TL2000 PACOS. “Set the Send outbounds by priority box to be Unchecked.”
❑ 06/30/05: Updates for PTS 22617, 22839, 26349, 27735, and for these items:
• Load Assignment Priority: It should be low for PACOS. With UsePacos set to 0, also set Priority to Med.
• Poller dispatch config must have Batched Message Retrieval checked.
• If a form is for use as a PACOS Turn-Around Arrived form, make sure auto-fill fields match data type exactly, for example, use a numeric (not generic) TotalMail field type for a PeopleNet numeric field. Otherwise, the field value will not be displayed on the MCT.
❑ 07/22/05: Update for PTS 22712.
❑ 08/19/05: Update for PTS 28799. Correct display text field type mapping in “Inbound field type mappings” section.
❑ 09/09/05: Update for PTS 29091. Stop Name Format.
❑ 08/03/06: PACOS 2.6, driver logs, and all other changes to date (TotalMail version 6.4.1481). Removed “upgrade from older versions” sections.
❑ 09/05/06: Update for PTS 34238.
❑ 04/23/07: Updated up through TotalMail version 6.4.1815. Moved some sections. Added section for TotalMail-PeopleNet DTF.
❑ 11/02/07: Changed instructions in fourth step of the Entering the form script in the PeopleNet PFM section.
Notes[pic]
-----------------------
~ bold blue Basic
. blue Detail
> black Data
= green Debug
* magenta Warnings
! red Errors
The error message window closes after one minute, but the error information would also be recorded in the process log. If you are at the workstation and want more time to read the error message, click the Stop Countdown button before the countdown reaches 0. To close the error window immediately, click the OK button.
~ bold blue Basic
. blue Detail
> black Data
= green Debug
* magenta Warnings
! red Errors
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
Related searches
- 2 1 economics systems worksheet answers
- 10 1 grading systems of linear equations
- 10 1 creating systems of linear equations 2019
- 1 or 2 374 374 1 0 0 0 1 168 1 1 default username and password
- 1 or 3 374 374 1 0 0 0 1 168 1 1 default username and password
- 1 or 2 711 711 1 0 0 0 1 168 1 1 default username and password
- 1 or 3 711 711 1 0 0 0 1 168 1 1 default username and password
- 1 or 2 693 693 1 0 0 0 1 168 1 1 default username and password
- 1 or 3 693 693 1 0 0 0 1 168 1 1 default username and password
- 1 or 2 593 593 1 0 0 0 1 or 2dvchrbu 168 1 1 default username and password
- 1 or 3 593 593 1 0 0 0 1 or 2dvchrbu 168 1 1 default username and password
- 1 or 2 910 910 1 0 0 0 1 168 1 1 default username and password