Friday, October 24, 2003
What's New for October 24th, 2003
Highlights from the Past Week from MTI Technology Marketing
Messaging and Trailer Tracking
Aether Messaging
A few new wrinkles have been added into our Aether messaging strategy where instead of sending freeform messages to provide details about Load Assignments, we will be sending out macro forms. This isn't the easiest approach to deal with but it will happen. We've also seen a few issues with sending out messages that are being addressed. There are a number of internal procedures on how Aether handles messaging - search for Aether and you will find them.
PeopleNet and PACOS
Further discussions with PeopleNet have shown a brand new spec for their PACOS functionality. They've added in a bunch of great new features including Geocoding of addresses which fits in nicely with some of the things we'll be doing. I've written up a description of the planned functionality for Automated Dispatch with PeopleNet and you can read about it at http://www.mtihorizon.com/blogs/2003_10_24_andrewarchive.htm.
SMS Messaging
For those who haven't seen the acronym, SMS stands for Short Messaging Service and is also known as text -messaging for cell-phones. Brad James and I have been working on a few iterations of this and you can read about them here: http://www.mtihorizon.com/blogs/2003_10_22_andrewarchive.htm
It works very well - right now, the plan is to make all messages customizable by the user.
New Features for Existing Clients
The Custom Data Center is really very cool and there is now documentation online about it. Check out: http://www.mtihorizon.com/documentation/doc444.asp
I also added a procedure on how you can use LKUP with it. - http://www.mtihorizon.com/supportkb/proc1049.asp. This is a tool that lets us create custom data fields when working with customers. We no longer have a need to go around creating extra files when we need to track more data.
I've also done up a number of new reports for customers. These will be made available online for Download Center subscribers. Some cool new ones include a way for tracking System Code Activity in VME, Customer Activity by Week and more. Slowly but surely, I'm closing out all those open report requests. Visit http://www.mtihorizon.com/repcenter.asp to see them. They are listed by date.
For those wondering about Marathon Cheese, Jerry was apparently out this week so that's why we haven't heard back from him. He's back next week so that should be very exciting to see what we can there.
Waccamaw is requesting a number of changes including new Integration into the new MAS 90 package. The proposals on this are small but many.
New and Coming Back Clients
Accurate Express goes live on November 1. I will be doing final data conversions on 10/31 so do not plan for me being available much on that day at all.
Four Truckers is moving forward as well. They have signed on again. I will be testing the ODBC Link to their Aurora system next week for their Go Live by 10/31.
New Prospects and Sales Demos
Fresh Delmonte (who has put us through a number of demos) seems to be getting closer to making a decision. We should be hearing from them next week. They may be looking at a 30 day trial with the hosted server approach, which would be very exciting. There would be a number of import and export updates there but since they are a 200 truck fleet, this would be a very big sell if it goes through.
Also did some new demos for a larger Vehicle Maintenance shop showcasing the new Preventative Maintenance Builder (see email What's New for October 10th for more details). Not sure how that's going to go but the new tool is very cool to work with.
Features you may not be aware of
These weren't worked on but are in play at various customers as proof of concepts and are available for customers. My recommendation about how customers pay for it is indicated in the parentheses around the title.
Tanker Gross/Net (Not Free but included with Tanker purchases which includes MultiProduct)
For those customers who are tired of dealing with their HUGE multi-product file and want to track Gross and Net capacities, check out Tanker Gross/Net. http://www.mtihorizon.com/documentation/doc374.asp
AutoFill (Not Free but included with Tanker purchases which includes MultiProduct)
AutoFill is an accompanying service for Multi-Product designed for Tanker customers who want to pre-define the products put into the MultiProduct screen based on each customer. It saves dispatchers huge amounts of time and includes features such as Safe Level and Maximum levels to ensure that incorrect entries are NOT put onto loads.
Full Checkcall Edit (included with product)
Full Checkcall Edit allows users to modify all aspects of a checkcall. It is based on Checkcall History and will replace checkcall history (CKHIST.APP) if it is loaded.
VME Bar Code Scanning (included with VME)
The VME Bar Code scanning service adds a new button to the VME Toolbar that lets users use a bar-code scanner to add new items into inventory. This greatly speeds up the process of updating the inventory. Enhancements are being made to allow this tool to be used when working with work orders as well.
Plans for PeopleNet and PACOS
Much of this functionality is in my testing environment, awaiting the new unit that I will plug into my vehicle's adapter for further testing.
I, for one, am very happy with the new additions to the PACOS specification that were originally not going to be there (like geocoding of addresses).
Our primary goal is to provide automatic Circle of Service functionality with as minimal effort from our customers as possible. To this end, we will likely NOT be using PeopleNet's implementation of landmarks in the first set of implementation. However, we will be using your pnet_geocode_address to a huge extent. For existing PeopleNet customers, we will be pulling in their landmarks using the landmark_view call and updating it accordingly.
Question: Is there any benefit to using the landmark definition vs. the Lat/Long? I have not seen one based on our discussions to date.
Setting up PeopleNet
The main criteria for setting up PeopleNet for our customers will be to define a Stop Profile. If one is not present, we will need to set one up. (note: this would be a very useful new feature to allow developers to create profiles online). Depending on our customers needs, we will likely disable the existing Arrive Shipper, etc messages for their account, however, they will be able to send custom messages or Load Modification messages as required.
Horizon Setup
When setting up Horizon for PeopleNet, users will be able to specify a default Profile ID for Shippers, Consignees, Stops as well as a generic entry. We are looking at the possibility of allowing users to set up individual profiles for customers as well.
Booking A Load
When a load is booked on a PeopleNet PACO enabled customer, we will verify that we have a Lat/Long for the shipper, consignee and any stops along the way. This information will be stored on the user's computer. If the information is not available, we will do a pnet_geocode_address call and retrieve this information. We may also be implementing this geocoding when a customer is added into the system for the first time.
Assigning a Load
When a load has been assigned to a driver, the pnet_dispatch will be called with all of the existing stops noted. If NO generic profile is provided, we will be using some defaults that may be configured by the user. When the assignment has been successfully added, it will be added to a Automated Dispatch table that will be used for tracking the events that occur on this dispatch. At this stage, our monitor will only be responding to events and inbound messages.
Options would be set up on both a global and a per shipment basis to control the drvr_form_msg as a free-form message. For customers who require a more specific form to appear, this is under further development.
Monitoring Messages
On a regular basis, we will be calling pnet_dispatch_events to retrieve the status of all dispatches in the Automated Dispatch table and updating the data as it comes in. A separate monitor will be processing the messages as they come in. If the user has chosen to forego the use of existing messages, when an event occurs, the monitor will generate the messages for our Circle of Service software so the load will be marked as Picked up, Enroute, or delivery.
Some customers will be requiring their drivers to send more details (such as signatures, etc). in those cases, we will be setting up THOSE messages to automatically update the information as it comes in. An example of this would be Tidewater where the driver may send the full details about the gross/net gallons delivered for various products. In a case like this, this would be handled by the drvr_form_msg detail. I am waiting for my unit to work on more detailed requirements for this feature and see it in action.
Using the Automated Dispatch event table, customers will be able to modify their Dispatcher view to highlight loads that are past due or that are pending, without any other modifications required. The email feature currently found in PACOS may be used based on the profile but otherwise we may implement it further later on.
Changes to Dispatch
If changes have been made to the Dispatch and the user resends, we will be calling pnet_dispatch_edit and modifying the details to add new stops and details about the pnet.
Thursday, October 23, 2003
Planned Dispatch Table
For use with any mobilecommunications system that can handle EXPECTED and ACTUAL delivery dates/times etc
PACOS Definitely
Individual for records for each stop
Stop 0 is Pickup
Stop 99 is Delivery
Stops in between are actual
Have a Scheduled Arrive
Actual Arrive
Scheduled Arrived
Actual Arrived
Scheduled Depart
Actual Depart
Not all are required but get filled in as the things take place
When a load has been delivered, it gets archived or deleted from this table (keeping it small)
Loadnumber
Stop Numb
SchedArr
ActArr
SchedArrd
ActArrd
SchedDept
ActDept
System - specifies type of system that logged it
Driver
Tractor
PACOS Definitely
Individual for records for each stop
Stop 0 is Pickup
Stop 99 is Delivery
Stops in between are actual
Have a Scheduled Arrive
Actual Arrive
Scheduled Arrived
Actual Arrived
Scheduled Depart
Actual Depart
Not all are required but get filled in as the things take place
When a load has been delivered, it gets archived or deleted from this table (keeping it small)
Loadnumber
Stop Numb
SchedArr
ActArr
SchedArrd
ActArrd
SchedDept
ActDept
System - specifies type of system that logged it
Driver
Tractor
Wednesday, October 22, 2003
Horizon Integration with NextTel
Melody asked me to give you some information regarding linking Horizon with NextTel phones.
Horizon's current integration is based on text-based messaging on any cellular phone based service. The way it currently works is that when a load is assigned to a driver who is set up as being a "cell" customer, a message is sent to the phone with the details of the load in one message and then a followup message that says
"Please reply when you have arrived at the shipper"
When the driver arrives, all he needs to do is reply to the message or he can actually type in a new message with the words AS xxxxx where xxxx is the load number. There are a number of other keywords they can use for making changes as well.
When the system receives the AS message, it sends another message that says
"Please reply when you have departed the shipper". When the driver replies, this acts as the "Pickup" checkcall (and sends it to Circle of Service and Horizon). A subsequent message is sent saying:
"please reply when you have arrived at the consignee?" When the driver replies, this is managed as the AC or Arrive Consignee checkcall. A subsequent message is sent saying:
"Please reply when you have delivered the load?". Upon receipt of this message, the load is updated as delivered and any future planned loads then are sent to the driver.
The benefit of this approach is that the driver actually has to do VERY LITTLE to make the system succeed. In most cases, they can reply to the message with approximately 3 clicks on the phone.
If the driver does NOT reply to these messages, they can alternately send new messages to the email address edispatch@mtihorizon.com. This email address is capable of handling the following content in the message:
CKCODE: indicates a checkcall code such as AS (arrive shipper) , DS (depart shipper) , AT (Arrive Stop), DT (Depart Stop), AC (Arrive Consignee), DC (Depart consignee) and AK (load acknowledgement)
CITY: Current City
STATE : Current State
NOTE: Comments
LOAD: Load #
MACRO: Macro #
We are looking at expanding this functionality so if you would like to discuss this further, please give me a call or respond to amacneill@mtihorizon.com
Thanks
Andrew MacNeill
Technology Marketing Manager
Technology Marketing Manager
MTI Horizon Team
http://www.mtihorizon.com
Email: amacneill@mtihorizon.com
Phone: 613-851-4496
Phone: 613-851-4496
Fax: 1-425-944-0467
(The following numbers are for the main NC MTI office. Call the above numbers if you are attempting to contact me directly)
MTI Office: 336-659-0815
MTI Fax: 336-659-9406
MTI Fax: 336-659-9406
View seminars on http://mtihorizon.webex.com
Thoughts Regarding OutSourcing
(Some ideas gleaned from 5 small specs that were outsourced to an overseas programmer)
1. Always keep an idea as to how much time it would take to do it yourself and make sure the time and effort it takes to write it down and discuss it is worth it.
Example: I outsourced a project because it shouldn't have taken that much time but I didn't have that time. When our O/S company told me they hadn't done it yet (see next point), I had to put the time in. As it turns out, it only took me an hour to fulfill the functionality. Now I have testing to do but it really only took a little bit of time. I easily wasted that hour with emails asking about its status. (Note: the hour to spec it was worthwhile because it ensures the functionality is documented)
Example: I outsourced a project because it shouldn't have taken that much time but I didn't have that time. When our O/S company told me they hadn't done it yet (see next point), I had to put the time in. As it turns out, it only took me an hour to fulfill the functionality. Now I have testing to do but it really only took a little bit of time. I easily wasted that hour with emails asking about its status. (Note: the hour to spec it was worthwhile because it ensures the functionality is documented)
2. Only give away ONE task at a time. They might complain that there is a lag between the work but it's the only way to ensure prompt delivery of stuff.
Example: Our O/S company had a project spec for over 2 weeks yet when I asked where they were, they said "it's coming". Then I find out they hadn't even touched it yet. As a result, the client started screaming for it and I had to put in the time to do it myself.
Example: Our O/S company had a project spec for over 2 weeks yet when I asked where they were, they said "it's coming". Then I find out they hadn't even touched it yet. As a result, the client started screaming for it and I had to put in the time to do it myself.
3. Be 100% specific. Be ready for the company to come back and say "it wasn't in the spec" as a way of getting out of completing stuff. Many companies are willing to make minor changes but changes that are more "creative" can sometimes lead to problems.
4. Tell them how you plan on testing it. This gives a much better scope for their final work because it has to actually DO it when you test it.
5. Put down a timeline. See #2 for reasoning but if you give them a timeline, you can actually hold back funds if they don't provide the work for you.
