This is why people were disagreeing with me. I said nothing about ORION being used to save or measure time. Even if local management may try to point to the ORION screens to pressure drivers.
I was specifically talking about ORION's programming. The 1's and 0's. The algorithm uses all the time inputs that were placed into it by the ORION team, management, and existing time studies. That all has to play into the solution. It's not as easy as what is the least amount of land we can cover with a certain set of stops. If that was the case, ORION might have you do 75 resi's before your first business. Or your 10:30 commit might be your last stop.
Obviously I know ORION was designed for mileage savings. But it has to accomplish this within the parameters of the time inputs that are put into it. Hopefully this clears up my point.