Changes to QC logging parameters

Just talked to our corp safety for the Refrigerated side for Knight, he knows of no changes coming to Omni. He gets a email from them monthly stating if the system will be updated and so far he said nothing has come across his desk and the nothing was brought up in the monthly meeting. Something tells me this is more SNI then Omni.

Just me 2 cents.

 

It records your last known event before it goes down and assumes that was what you were doing the entire time.

 

It's amazing how this is a DOT mandated upgrade and they were given 10 days notice. Well we were given what 6 days.

Funny I see they waited til all the new contracts were signed and I bet it was intentional on their part.

 

If it walks like a duck and smells like an outhouse it has to be a SNI change.

 

Of course I'm just theorycrafting here, but here is how I see it:

Yes, Navigo often craps out and thinks you're driving off the road, etc., but Navigo appears to be just an application that runs on top of/alongside the main Omnitracks application. While it may not be communicating all the time, it still does have many internal logging functions. If you look around in some of the diagnostic screens, you can see all the different components it can interface with and lots of the data it pulls from the ECM such as odometer readings. The black box also has a backup battery inside of it that will power the unit (probably the black box only, not the handheld part) for some unknown amount of time should it lose it's main power connection from the trucks' batteries. I discovered that when I removed the unit from my truck to send back to Schneider. I'm sure the unit also logs its failures like any computer does, and could easily tell if it was a power failure, hardware failure, software failure, etc. that occurred. On Schneiders end, I'm sure Omnitracks provides them with the ability to look at these failures and would alert them if a certain set of errors occurred, such as a driver rebooting through the handheld unit at 2050 and then when it completed the reboot at 2057 the ECM mileage had increased by 7 miles, compared to a normal software related crash that would cause the unit to reboot.

Some form of technology is always watching these days...

 

What I saw, but don't remember where, was that this change was tacked onto a spending bill that Congress recently passed, just like the suspension of the restrictions on when and how often you could take a 34-hour reset. Congress is good at sneaking things that might cause controversy by themselves into bills that they know will pass. It's how millions of dollars get diverted to things like a coast guard station in West Virginia (that's true btw - it actually oversees the Port of New Orleans... From West Virginia...)

 

on your last point, you understand that a lot of barge traffic traverses those waters from the ohio on down to the mississippi? So its not exactly wasteful spending.

 

I just heard a message while on hold for my DBL that says that this new drive time thing won't happen until a driving threshold is met. Meaning, the log won't retroactively record drive time until you meet a driving threshold. Still don't know what the driving threshold actually is though.

I would believe that if the base was on a river and not inland (it's in Martinsburg)...