Matrix Routing via HSS : level of flexibility

[Bernd Welter]

Hi there,

recently a player mentioned his concerns about the flexibility of the Matrix Routing API:

• On one side, it’s the service integrated by default with HSS, and it’s the one that makes sense to handle bulk requests — like the ones triggered by our TMS.
• The concern is that the Matrix Routing API from PTV does not support the ‘shortest’ (and ‘fastest’) route options, which we use in our agreements with carriers.
• These options are only supported in the Routing API, which we use to get the geo‑route — but the Routing API is not bulk‑enabled, so calling it one‑by‑one will not work for us.

We need a solution for this.
Our SAP setup with xServer included:

• Choice of Fastest/Shortest routes : The ‘shortest route’ option is a business capability we need to keep, as in many scenarios it is directly tied to transport cost calculation.
• Consideration of Truck attributes
• Allow/Avoid tolls and ferries

Let me draw your attention to the article Access to routing parameters (e.g. Avoid tolls,/ Ferries, shortes/fastest) in the PTV Developer Matrix Routing Forum:

• Though you can't parametrize each and every routing option at runtime we offer solutions for this purpose.

Bernd