startTime in Bing MIO RRS feed

  • Question

  • i'm using a asynchronous request for several agents.

    agend "A" start's the shift at 09:00 to 18:00

    There are several waypoint's with oppening time 09:00 to 19:00

    After response, it tells me that the fist instruction start time is 10:50:21 why?

    This means 1h:50m:21s without doing nothing...

    Friday, March 6, 2020 2:57 PM

All replies

  • Hi PSantos79,

    My assumption would be based on the shift given, 09:00 to 18:00, that is the optimal travel window based on time and traffic.  Likely this maximizes their time available in the office before and after the travel portion of their shift to complete paperwork or other tasks that are not related to driving/site visits.



    Tuesday, March 10, 2020 4:35 PM
  • Thank you IoTGirl.

    The thing is that in our company we prefer workers to star their driving exactly at 09h and than complete paperwork in the end of the day...

    Is there a way to do this?

    Wednesday, March 11, 2020 10:50 AM
  • Hi PSantos79,

    At 9am the traffic would be higher than later in the day but you could certainly lessen their shift window to force different behavior but this would not be optimal.

    Another option would be to use the same route provided by MIO but earlier in the day and understand that a delay will likely be incurred. 

    Rather than using MIO, if you are not interested in the optimal time, you could investigate using Distance Matrix for your scenario. It is not as comprehensive as MIO but it does the basic "Traveling Salesman" routing but without time windows.



    Wednesday, March 11, 2020 5:05 PM
  • Hi PSantos79,

    In speaking to an Engineer that worked on MIO, another reason you might not get all agents to leave at 9AM is that you do have multiple agents.  MIO will optimize based on both Agent and Customer availability windows.  This means that the most optimal solution is likely not going to have all agents leave at the same time but rather accommodate all availability windows.



    Thursday, March 12, 2020 10:29 PM
  • Hi Psantos79, 

    To add to what IoTGirl has shared in her reply, when you call MIO, there are some parameter values that may impact the itinerary results, for example: 

    • Type:
      • SimpleRequest [Default]: No traffic data is used.
      • TrafficRequest: Traffic data is used.
    • Costvalue: Default is Travel time 
      • TravelTime: Optimize according to travel time
      • Distance: Optimize according to distance traveled

    Which values did you use in your request? If you would like, you could also share with us a sample request so that we could look into what options can be used to best serve your use case.


    Thursday, March 19, 2020 1:33 AM