Motive builds technology to improve the safety, productivity, and profitability of businesses that power the physical economy. The Motive Automated Operations Platform combines IoT hardware with AI-powered applications to automate vehicle and equipment tracking, driver safety, compliance, maintenance, spend management, and more. Motive serves more than 120,000 businesses across industries, including trucking and logistics, construction, oil and gas, food and beverage, field service, agriculture,…
Motive is the ONLY application I will recommend in this industry to other companies needing ELD solutions. I have helped a couple other companies develop their own in house Electronic Logging Device systems and while they were promising initially, the companies lost sight of the important aspects and began to focus on cosmetic details over full functionality.
One of the features I find frustrating to use is adjusting speed limits. Sure, when someone breaks a speed limit and it gives me an event I can go into the event and easily adjust the speed limit, but ONLY FOR THAT SECTION they sped in. If I need to adjust the speed limit for the whole road, thats another matter entirely. We work in the middle of no where so I have noticed there have been more examples of this than I would like. But I also understand they get their speed limit data the same as every other service so its not like Motive is behind, just limited to the data they receive.
I would like to be able to determine event criticality so that any event I want to be automatically assigned as "coachable" will be. Also in regards to the events page, I would like to see a way to select multiple events (maybe some check boxes to select the ones you want) and be able to assign them all to "coachable" or dismissed". Especially during implementation we are getting a lot of "obstructed view" and this is not going to count against their score, we just want to dismiss them after seeing who it is so we can address it. But we get 10 or 12 for each person and have to go into each one individually... It is just a little time consuming and I think the multi select functionality fixes that.
Currently maintenance reminders use engine hours OR miles. I would like to see the capability of using both. for example, a good estimate is 1 hour of engine idle time is equivalent to 30 miles driven. So if we set a 10,000 mile maintenance alert, I would want that to include the actual odometer reading (lets say 7,000 miles) and add the engine hours to miles conversion, lets say it has 100 idle hours (100x30 = 3,000). Hope that makes sense.
When signing into Motive upon entering and starting motor vehicle, the app and the transmitting unit pair immediately. Once paired it is extremely easy and efficiently started to populate the necessary unit information. Then entering the Work Order info is seamlessly entered to the E- log. Doing the pre and post vehicle checks is completed quite accurately.
I don't have any outage issues with Motive. Anything unplanned is typical in the tech world and you have to go with the flow. The good thing is that any outages that would happen with Motive would not stop us from operating. That would be something I would be concerned with if so, otherwise I think we are in a good spot.
The team is always quick to resolve any issues. We have dedicated account representatives we can contact at any point. I work with many software companies and this one is by far the most customer focused out of them all
Our company used Qualcomm before getting Motive several years ago. Unfortunately, I was not working with the ELDs at that point. However, the majority of drivers say they like Motive more than Qualcomm. We have stayed with Motive due to its features, user support, and innovation with AI technology.
