| Status | Approved |
| Owner | VAN OS-ext, Nico |
| Stakeholders | Najaite Nidboufker |
Issue
During the process of arranging transport with carriers there are several business functions that require integration with carriers. These business functions are:
- Tendering
- Order placement
- Slot Scheduling
- Track and Trace
- Charge Settlement
To cater for these functions, SAP provides an online platform: SAP Business Network for Logistics (BNL).
Currently Syensqo uses two TMS solutions that are catering for these business functions: Transwide (in EMEA countries) and BuJay (in North America). As BluJay is scoped to be replaced, there is a separate KDD focused on the decision of the way forward with BluJay: KDD048 - Way Forward with BluJay.
This KDD will focus on the standard solution for Syensqo globally. Here the decision is to be made which online platform Syensqo should use to integrate with carriers other than the scope of KDD048.
Recommendation
With the seamless integration with SAP TM and SAP BNL, it would be recommended to have SAP BNL as the standard global solution to integrate with carriers. This would be using both the Freight Collaboration and Global Track & Trace (GTT) modules of BNL.
With SAP BNL users can do all their tasks in SAP TM, and can monitor and track all business functions of BNL from SAP TM. There are some other possible benefits of SAP BNL, like end-to-end tracking of Sales Orders and Purchase Orders. And resources can be tracked on their lifecycle. This can be useful for tracking of Syensqo managed trucks and containers.
As integration of SAP TM and SAP BNL is standard, it will be easier to configure and setup than building integration with other third party TMS solutions.
The biggest downside of transitioning to SAP BNL is that the carriers with also need to support SAP BNL. They can use the BNL online launchpad, or they can integrate their system with available API or EDI connection. For this integration, if carriers are not connected yet with SAP BNL then this would require them to do an initial investment. With SAP being such a dominant market player, it is possible that Syensqo might be the first, but maybe not the only client with that request. And for having Syensqo as a customer, you would imagine that carriers are willing to accommodate.
Background & Context
Overview of SAP TM with BNL (Option A)
To be be able to assess if SAP TM with integration to BNL is a fitting solution for Syensqo, an understanding of the SAP TM processes is essential. In this section a more detailed explanation is provided how the process works in this system configuration.
SAP Business Network for Logistics and Syensqo's Business Partners
SAP has been requested to analyse, from the list of business partners that Syensqo uses to purchase freight services, which business partners are connected to SAP Business Network for Logistics. For analysing the data, we take into account the known business with these business partners in the total in net KG.
On the full list there are 261 carriers, with a total of 2.8 million ton of cargo. Of these carriers, 109 were not on the initial request of which a new request has been send for 58 carriers. A big part of these 58 carriers were shipping liners. The amount of cargo for these 58 carrier is 683,000 ton. The remaining 51 carriers with a share of 2,000 ton, will remain unknown.
The remaining list has 152 carriers with a business share of 2.1 million ton. Of these carriers 51 are identified as connected with BNL, with a total business share of 1,478,000 ton. That leaves 101 carriers that are currently not connected, with a business share of 611,000 ton. Counted in number of carriers 34% is connected, counted in business share 71% is connected.
For more detail please see attached excel file. Data analysis carriers connected with BNL.xlsx
Option B: SAP TM integrated with Transwide
Transwide is the current TMS solution used in Europe and a few countries outside of Europe. The features used in from Transwide are:
- Tendering
- Carrier Determination
- Slot Scheduling
- Status Tracking
- Exception Management
- Additional Cost and Settlement
Transwide is currently only used for road transportation, but can be extended to other modes of transport.
Transwide is owned by Alpega and the solution has been renamed to Alpega TMS. Alpega TM is a combination of Inet and Transwide.
When integrating with Transwide, the integration objects will be Freight Order and Freight Booking. Once these documents are created, they are interfaced to Transwide for further processing.
For track and trace functions the design will follow similar design as with BNL, where Project 44 is integrated with Transwide and Syensqo internal systems also send updates to Transwide where required. From Transwide the updates are propagated to SAP system.
*Note: decision for North America for replacement of old BluJay is not taken into account in this KDD. Next to Transwide new BluJay could be part of system landscape.
Option C: SAP TM integrated with BluJay deployed internationally
BluJay is the current TMS solution used in North America. BluJay is a complete, integrated software solution that manages the entire logistics operation from front to back, handling multiple languages, currencies, and time zones. It allows shippers to manage all multimodal transportation activities for one shipment. BluJay is used by most GBU's in North America region.
Features:
- Contracts & tariffs management
- Load optimisation
- Mode and carrier determination
- Electronic booking
- Freight cost calculation (planned & unplanned costs)
- Collaborative status tracking
- Transport reporting (carrier compliance, freight costs, KPIs…)
- Freight audit
- Freight payment
Part of this KDD is to consider new BluJay version to be deployed globally. In that case Transwide would be replaced and all Freight Orders and Freight Bookings are integrated with new BluJay version.
More detail on BluJay and BluJay replacement is provided in KDD048 - Way Forward with BluJay.
Assumptions
Execution systems can report events to portal
Execution systems owned by Syensqo, like Selfy, FDTMS or other mobile apps, can be integrated with the chosen portal solution. This can be SAP BNL, Transwide or BluJay. If this integration is not possible, then it will be considered to integrate these systems directly with SAP TM (this will be custom development). This decision will be taken during detail design.
Project 44
Project 44 will be included in project scope to receive shipment updates from ocean shipping liners.
Carriers can adopt SAP BNL
With the information provided by SAP, carriers are able to utilise the launchpad online, or they can use API's provided by SAP.
Constraints
Way Forward with BluJay
With the replacement of BluJay, would it be beneficial to have new BluJay, Transwide and SAP TMS all operational within Syensqo? As North America has to make a decision on what the future solution is going to be, there is a dependency between this KDD and KDD048 - Way Forward with BluJay.
Impacts
Carriers to adopt SAP BNL
Carriers that are currently not using SAP BNL will have to use the SAP BNL Launchpad, or invest in integration using the BNL API or EDI interfaces.
User experience
With the use of SAP TM in combination with SAP BNL, Syensqo users will work only in SAP TM and they can monitor progress of Tendering, Carrier Selection and Execution in the SAP TM system. When other systems are involved then users will need to switch between SAP and third party systems.
Resource Tracking
SAP BNL has the option do to resource tracking. For trucks and containers it is then possible to do full lifecycle tracking.
Business Rules
Freight charges to be updated in SAP TM
In either solution, freight charges have to be reported back to SAP TM transportation documents. This is to cater for accrual postings. The charges are distributed over the cargo and are posted as accruals in accounting.
Evaluation
Evaluating the functionalities between SAP BNL and Transwide, then there doesn't seem to be a lot of differences. The integration between SAP TM and SAP BNL is then a unique selling point. Transportation planners can work from SAP TM and don't have to switch systems. The integration between the two systems is existing, making the configuration and setup of the landscape easier from a project perspective.
The biggest downside for switching from Transwide to SAP BNL is for the carriers. Those that don't have SAP BNL integration will need to invest in making this integration work. However, this will be a one-time investment. A software provider as SAP has such a market dominance, that a new solution like SAP BNL will require more and more carriers to support the platform.
The replacement system of old BluJay might be another candidate to replace Transwide in Europe, however the seamless integration with SAP TM and SAP BNL make the SAP BNL solution a more capable, efficient and user friendly solution.
Option A: SAP TM with BNL | Option B: Integrate SAP TM with Transwide | Option C: Integrate SAP TM with BluJay | |
|---|---|---|---|
Functionality |
|
| |
User experience |
|
|
|
Costs |
|
|
|
Risks |
|
|
|
Network |
|
|
|
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||

















