| Status | Approved |
| Owner | VAN OS-ext, Nico |
| Stakeholders | Najaite Nidboufker |
Issue
For Road Freight order placement, tendering, track and trace and carrier settlement regions utilise the following TMS solutions:
- EMEA - Transwide
- NAM - BlueJay
- LAM - n/a
- APAC - n/a
For these functions SAP offers a cloud based solution: SAP Business Network for Logistics (BNL).
This document is to provide more information on the SAP BNL solution. BNL could be considered to replace Transwide and possibly BluJay for Road Freight.
As LAM and APAC is currently not using a TMS solution, BNL could be utilised in these regions.
Recommendation
As BNL is THE solution for SAP to integrate with trucking companies, it makes sense for Syensqo to include it in the To-Be landscape.
As the functionality of BNL is overlapping with Transwide, then this system will be retired.
For North America the decision is solely based on the decision what is going to happen with BluJay (KDD). If BluJay stays operational, then it makes sense to integrate with BluJay.
Background & Context
Overview of SAP TM with BNL
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.
Alternative 1: 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.
Alternative 2: 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
Option A: SAP TM with BNL | Option B: Integrate SAP TM with Transwide | Option C: Integrate SAP TM with BluJay | |
|---|---|---|---|
Functionality |
|
| |
User experience |
|
|
|
Costs |
|
|
|
Network |
|
|
|
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||


















