Qualcomm elogs, accessing data

Most trucks equipped with electronic engines already have all the data you speak of (miles driven, idle time, total hrs, etc.) You don't need an ancillary device to get that data

 

I understand but do you have some requirements that you were given about the project and the needed data definitions to understand exactly what you really need?

Why would you think that?

Most of the drivers who work for companies don't need that, and the companies already have access to the needed data for forecasting and other management or performance metrics to make business decisions.

Again going back to the requirements of the project, was there any research into the data from the ECM (where this data is coming from) and how that data is derived for each engine manufacturer?

Society of Automotive Engineering is the place to start to understand the J1939 and other protocols that are used to extract the data from the ECM. They have a couple great resources that are used for application/hardware development.

Have you actually contacted Qualcomm to see what levels of company data is kept or purged?

That may be true but again contact Qualcomm.

Qualcomm can only answer that, most of the people here are end users and don't have a lot to do with the backend of the management system.


My question to you is what can be made or created or written that would actually be a huge benefit for any of us?

 

Sounds like an EOBR programmer... Thhppppt!

 

I understand about the NDA but here is the problem, what market study was done to actually see if it is needed. What I mean is we get all kinds of data that we can use, most of which has been derived from people who have been in the business for a long time and know what is worth for different levels of operations (driver/Owner Operator/fleet owner) and what is not. Most of which the qualcomm data can offer is not what you are looking for from my assumption that you are maybe looking at operational trends which can pick out performance metrics to improve driving skills - this is already out in the market (I don't remember the name of it). The same goes for the actual operational revenue creation side of things, taking the info from qualcomm and putting into a form that can be used to drill down into the data but that isn't helpful for drivers and many O/Os.

I think before you continue, you need to see what definitions are in the requirements document that your customer has given you to see where the sources of data you need can come from because when you or anyone else mentions truck data and qualcomm in the same paragraph, it shows your customer hasn't done much homework or knows what's going on. As a programmer you need to know what they are thinking and how to fix these issues.

 

The QC driver data is archived for 3 total years by Q.C. Carriers can access 6 rolling months on the co. site before it's compressed and archived presumable in a encripted can...(or hopefully) then they have to pay big to get it researched and restored.

I'm unsure if the entire trip or just the driver activity gets compressed at this point.

I can't really tell what product you want to develop with the data however like others have said most everything thinkable with truck and driver metrics is already on the market. Carriers are also a tough nut to crack. Margins are tight so the first thing your product has to deliver is a clear ROI.

One last point, carriers are drifting away from Qualcomm. They had the same issue with Cadec had back in the 80's which is to hook a carrier on the concept and then bleed him with updates and add ons.

Peoplenet has the lead right now as they can interface their product with most dispatch and billing software meaning the driver punches the delivery key and a bill is generated / mailed before the truck leaves the dock. That's not new because Cadec had it but what is new is the instant transmission from the site vs waiting for the driver to return to the terminal and download the data.

Read the latest fleet manager rag. There is an article on the very subject, trends and carrier response to data mining. There are privacy concerns and concerns about competitive data. The author writes about particular lane performance being targeted for mining and selling that but again, carriers are unwilling to share at this point.

Good luck
0101110010110101010110

 

Todd, I am wondering about something. After posting on this forum and a couple others about trucking applications, I am wondering if any of you software developers are actually freelance people who work without requirement documents or any sort of game plan from the customer or if you are part of a software house and this is for an in-house customer where the documents should be thoroughly maintained?

The reason I ask is that it seems that many programmers, no matter where they are working or how seem to be lost and without a clue of what is needed to fulfill the customer's needs. After discussing these threads with people who, like me were involved with IT projects, we came to a conclusion that there is something missing when people turn to forums seeking answers. Not bashing you or your project but pointing out there is something missing.

 

I already have it all and as an Independent O/O, the last thing I want or need is another POS software muddling up my ECM and truck electronics. I have already had wiring screw up my truck, I don't want or need anymore.