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,…
Driver prefer the intuitive dashboard and ease of use. Admin and fleet managers like the single click access to data, quick updates and robust features.
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.
Appian is excellent for use in both the analysis arena and ongoing operations support. The speed to solution and quality of solution is at the top of the market.
The configurability of the system gives the user the flexibility to address almost any route problem imaginable. Analysts have the ability to recreate the "world" to fit their customer's needs rather than forcing the customer into a predetermined framework.
The installation of the software is flexible and can be structured to fit any work group's format, from a centralized core to a distributed mobile analysis team.
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.
Many issues with the system and I will probably recommend other type of software if the question arises. Because of the investment my company has made, I will use the system for now.
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.
Our support team is very responsive but not always helpful. As great as our implementation team and check in team have been, I think there needs to be a middle ground support techs for the physical machinery. I think our support team can have trouble diagnosing past what the device should be doing. However, they have always been eager to help, quick to respond, and do their best to see a resolution is found
The ease of use and features Motive had to offer were hands down a better product. We work with the Motive team providing feedback and constantly feel as if we are building the product with them rather than working with what we have.
Appian was best suited for an analysis environment both functionally and from a cost structure standpoint. Other packages are targeting ongoing operations and their cost structures reflect that goal. The purely analytical environment can underestimated in these situations. There is definitely a need for non operation specific analysis tools in the marketplace.
The speeding data allowed us to create a speeding policy almost a year ago. We went from 5-10 drivers/week "breaking" our policy to 0-2 drivers/week "breaking" it. We have also noticed fewer challenging braking events due to fewer drivers speeding.
On more than one occasion, the video footage has saved us after the accident. In one instance, I was able to send the camera footage to the Trooper while on the scene of the accident, clearing us from any wrongdoing before the police even left the scene.
Improved service to customers by being more aware of ETA's and how they relate to each store's receiving hours.
Reduced transportation costs in dynamic environment where routes are optimized daily using Direct Route.
Better customer service to field by generating e-mail notifications for following day's ETA's, along with notifications when trips are behind schedule.
