Guess who gets to go on Workflow...

Sitting at the Detroit O.C and still waiting for workflow to assign a load...

 

Whos your TE? I had Jeff out of that drop yard.

 

Bob is mine. Real good guy.

 

I thought they closed the detroit OC?

 

The garage is already closed and the whole thing shuts down at the end of the month.

 

They said that it will remain as a drop yard with no facilities until they are able to sell the property. I'm sure they won't be selling it anytime soon in the Detroit market.

Anyway, Workslow is definitely having it's problems so far. The biggest problem is the NAT function, and the fact that we can't set it to when we are available. The stupid ETD (estimated time of departure) is a computer generated time that never makes any sense whatsoever. For example, the last load I had had an ETA of 0044 (they close at 1900???) and an ETD of 0815. Then the ETA randomly changed to 1815 for no apparent reason (I put in the correct ETA, but the system decided to override the ETA I put in to some random figure that makes no sense), and the ETD stayed at 0815. I guess the computer thinks I'm going to sit there for 14 hours?

Anyway, you can't set your NAT any earlier than the ETD. In this case, my arrival was at 1500 and I departed at 1545, but I still can't change my NAT any earlier than 0816 tomorrow morning because the computer knows better than a driver as to when his availability is. Also, it keeps resetting your available hours that you enter in the NAT macro to a bunch of random figures that make no sense. Entered those figures 4 times today and they were overridden a 5th time.

I sat for 20 hours waiting for a load on Tuesday, sat 2 hours today waiting for a load before I gave up and went to the OC for an extended 16+ hour break. Nothing but a bunch of wasted time so far on this system. They have a lot of work to do to fix the few but big annoyances.