Status

OwnerVAN OS-ext, Nico 
StakeholdersNajaite Nidboufker

Issue

A Geographic Information System (GIS) provides GEO location coordinates for locations, it can calculate real life transportation distance and duration between locations, and provides visual representation on a map for routes. This data is necessary for the following business functions:

Milk run validation - During manual planning a milk run can be created. The milk run can be validated with actual travel duration, loading and unloading duration, and maximum number of working hours for the driver. Users can then more precisely determine if a normal delivery can be turned into a milk run. Potentially increase the number of milk runs planned and ordered.

Automatic planning - To implement automatic planning that includes milk run planning, actual transportation duration is essential. Similar as with milk run validation, the system has to determine actual durations to be able to generate correct milk run planning results.

Charge Calculation - For a small number of shipments charges are calculated based on actual distance. With GIS this distance can be determined automatically. This makes the charge calculation automatic. Also, the distance returned by GIS can be compared with the distance as provided by the carrier. This can then be challenged if the discrepancies are too big.

Sustainability - For CO2 reporting it is necessary to have the actual distance travelled.


Recommendation

Having SAP TM integrated with a GIS services is definitely a move to a more mature solution. The benefits to it are described in this document. If these benefits will mature into a return on investment is hard to state for sure. Many companies using TM are not investigating this integration option. The companies that did build the integration are happy with the result.

It should be on Syensqo business representatives, that know their business best, to estimate what their preferred approach is here: do not integrate with GIS / have integration with GIS on the road map / at go-live have GIS integration.


Background & Context


Technical Background

There are three main functions in SAP TM where a Geographic Information System (GIS) is being called:

  1. Location Master Data creation

  2. Distance and Duration Determination

  3. Visualisation


Location Master Data creation

During the creation of Location Master Data, the system stores the geographical data of the location. On default the system is taking country code level coordinates as stored in the system. When GIS server integration is activated, then the system will pass the address data to the GIS server which will return the geographical coordinates based on this address data.

 
Distance and Duration Determination

There two main processes where distance and duration is being determined;

  1. Freight Order creation

  2. Optimizer Planning

The system doesn't execute a call to the GIS server for each determination. Instead the system will check the buffer table first: Distance and Duration Determination table (DDD). When the combination between two locations is unknown, then the system will do a call to the GIS server to determine distance and duration. Once received, the system will store the result in the buffer table. 

 
Visualisation

With the use of SAP Visual Business, a visual representation on a map can be displayed in the Freight Order and Transportation Cockpit.

 


Business Benefits

Milk run validation

During manual planning a milk run can be created. The milk run can be validated with actual travel duration, loading and unloading duration, and maximum number of working hours for the driver. Users can then more precisely determine if a normal delivery can be turned into a milk run. Potentially increase the number of milk runs planned and ordered.

Automatic planning
To implement automatic planning, actual transportation duration is essential. Similar as with milk run validation, the system has to determine actual durations to be able to generate correct milk run planning results.

Sustainability reporting
The Corporate Sustainability Reporting Directive (CSRD) strengthens the rules concerning the social and environmental information that companies have to report. The rules ensure that investors and other stakeholders have access to the information they need to assess the impact of companies on people and the environment and for investors to assess financial risks and opportunities arising from climate change and other sustainability issues. Companies subject to the CSRD will have to report according to European Sustainability Reporting Standards (ESRS).

With actual distances in the system, Syensqo will better capable to have accurate CO2 reporting and it will be easier to comply with the CSRD.

Charge Calculation
Where charges are calculated based on actual distance, when the system has determined the actual distance based on a GIS result, the system can automatically calculate the correct charges. This calculated amount can be used for validating the invoice. When there are large discrepancies, the carrier can be challenged to justify the difference.

Sustainability in planning
When optimizing transportation planning, CO2 impact can be taken into account by preferring more sustainable routes and means of transport in the transportation network.


Assumptions

Number of milk run orders

As part of transportation optimisation, Syensqo would like to increase the number of milk run orders as they have a cost benefits.

Automatic planning
Transportation planning is mostly a manual process within Syensqo, however for a future proof system automatic planning could be considered within the current scope of the ERP Rebuild project, or as a future improvement.

Charge Calculation
Most agreements with carriers are based pick-up and delivery location. However, when milk run orders are provided then these kind of charges are not applicable and charges need to be calculated per (additional) stop and milage.

Most freight agreements are setup with pick-up and delivery location, due to limitations on charge calculation capabilities at shipper.

Agreements in North America are more prone to be calculated based on milage. When North America is scoped for SAP Transportation Management then correct distance determination is important. For more detail on North America scope see TM KDD Way Forward with BluJay.

Sustainability
Not only does Syenqo would like to comply with CSRD regulations, it is part of Syensqo's strategy to have a positive impact on climate and nature. Optimizing transportation capacity and reducing CO2 emissions fit into that strategy. 


Constraints

When the GIS provider doesn't cover all countries

Not all GIS servers cover the whole world. Especially China GIS integration is best serviced with a Chinese provider. SAP TM configuration caters for this, but it requires extra setup time to make this integration as another set of interfaces is required.


Automatic planning

When initially setting up SAP Transportion Management, it is always preferred to have a solid solution for supporting manual planning. This keeps control with the user that have the best understanding of the business process. Some planning steps could be automated, but a careful approach is advised. When users have a solid understanding of the system's functionality then more and more automation and optimisation can be implemented to return better planning results, like milk run orders.


Impacts

  • GIS server is a 3rd party offering. If GIS integration is decided.
  • Implementing a GIS server takes about 10-15 consulting days.


Business Rules

Loading / unloading duration - Loading and unloading durations need to be setup to cater for correct total duration calculation.

Maximum shift duration - To limit the full duration of a Freight Order, business rules are to be defined during detailed design. Maximum duration can be different per region and per scenario.

Manually planning - Transportation planner needs to be mindful of milk run opportunities during planning. When consolidation opportunities exist then shipments should planned together.

Automated planning - During setup of optimizer planning, the system should optimize combining shipments into a milk run where possible.


GIS service providers

For consideration, the following GIS service providers are among of the most well known:


Evaluation

GIS integration makes the SAP TM solution much more mature. There are definitely some business benefits, especially when milk run planning is involved.

However, the system can run without this feature. It should be on Syensqo business representatives, that know their business best, to estimate what their preferred approach is here: do not integrate with GIS / have integration with GIS on the road map / at go-live have GIS integration.



Option A: Use TM without GIS

Option B: Integrate with GIS

Costs

(plus) No additional license costs

(minus) License costs

(minus) Development effort for integration

Optimisation

(minus) Milk run planning based on transportation planner judgement

(plus) Support for manual planning to build milk run shipments

(plus) Option to include automatic planning with milk run optimisation

Charge Calculation

 

(plus) Possibility to calculate charges based on actual distance

(minus) Agreements are mostly made based on source and destination location

Sustainability

 

(plus) CO2 reporting based on means of transport and actual distance.

(plus) Possibility to include CO2 into consideration during transportation planning.

User friendliness

(plus) No need to learn and understand complex automated planning logic and results

(plus) Map display with actual route gives users the feeling of a mature solution

(plus) Having actual distance and duration on the Freight Order provides better identification of real world representation


Change log



Workflow history