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

[Bernd Welter]

Hi there,

as I received some more questions in this context (coming from another SAP driven player) let me extend this thread:

Approach	Matrix Routing API with standard profile	Matrix Routing API with custom profile	AB Routing API with request profile	Matrix Routing API via HSS	AB Routing API via HSS
PRO	no additional costs best performance immediate access supports OPTIFLOW API	customizable via PTV admin best performance supports OPTIFLOW API	customizable via API no additional costs	customizable via PTV admin best performance	As flexible as wrapped by SAP HSS
CON	less flexible	comes with additional costs per profile admin efforts	poor performance does not support OPTIFLOW API	comes with additional costs per profile	poor performance