Status

OwnerVAN OS-ext, Nico 
StakeholdersNajaite 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 consider it in the TO-BE landscape.

If this solution is going to be deployed then it should replace Transwide. From a high level it doesn’t make sense to keep Transwide and then also have the option of SAP BNL.

For NAM the decision is solely based on the decision what is going to happen with BluJay (KDD 23). If BluJay stays operational, then it makes sense to integrate with BluJay.

At a certain point in time, when more knowledge and experience has been gathered, it can be re-evaluated if BNL is going to be deployed. If the functionalities are disappointing then it can be removed from project scope. After conceptual design would be a good moment.

If a limited scope is important, then it can be considered to keep BNL for the roadmap or to exclude altogether.


Background & Context

Overview and Background

SAP Business Network for Logistics is SAP's new collaborative cloud network that empowers logistics businesses to work together more easily than ever before. It consists of the solutions and add-ons below. SAP Business Network for Logistics is a cloud-service solution based on SAP Business Technology Platform.

SAP Business Network Freight Collaboration

SAP Business Network Freight Collaboration improves supply chain efficiency by connecting business partners on a collaborative network that supports jointly managing transactions, exchanging documents, and sharing insights across the value chain. For instance, upon invitation from a shipper, a carrier can onboard onto the network and collaborate with shippers on freight tendering, subcontracting, freight settlement, milestone reporting and dock appointment scheduling.

SAP Business Network Global Track and Trace

The aim of SAP Business Network Global Track and Trace is to capture, process and store tracking information about tracked business processes. Then, it allows business users to get real-time transparency of the execution of those processes. They can query any tracked process and display its retrieved data from end to end.

SAP Business Network Logistics Provider

SAP Business Network for Logistics is a cloud-based suite of solutions specifically built to connect logistics business partners to collaborate across companies and jointly manage transactions, exchange documents, and share insights. This page is the central entry point for carriers and data contributors into SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace to find all relevant assets regarding activation, integration and operation of SAP Business Network for Logistics.

SAP Business Network Material Traceability

SAP Business Network Material Traceability improves transparency, visibility, sustainability, and efficiency by connecting the entire supply chain. It is augmented by blockchain technology.

SAP Business Network, Intelligent Insights Add-On

SAP Business Network, intelligent insights add-on is a highly-customizable data visualization and reporting platform that presents real-time insights on your supply chain execution.

SAP Business Network, project44 Add-Ons

With the add-ons for project44 visibility services, SAP Business Network for Logistics users can benefit from the availability of actual shipment execution insights, such as shipment location and event status updates for full truckload, air and ocean shipments, as well as real-time milestone status for less than truckload shipments.


Assumptions

n/a

Constraints

SAP Inputs that are required

Some information is available online, but SAP might be better able to give more insight into the following points.

  • Is there a way to determine which Syensqo carriers are currently using BNL?
  • How does BNL integrate back to TM directly, or should Event Management be included?

Capture any additional constraints that the chosen alternative (i.e. the decision made) might impose on other parts of the overall design, solution, or processes.


Impacts

  • Infrastructure: Integration with cloud based BNL needs to be set up.
  • Project scope: Account for about 30 days of consulting to set up basic BNL integration.


Business Rules

n/a

Options considered

Options

Pros and Cons

Comments

Option 1

Exclude BNL from project scope. SAP TM will be integrated with Transwide and BuJay.

(plus) This will limit project scope

(plus) Users will keep using their current system

(minus) No deployment of TMS functions in LAM and APAC.

  • Integration will be built from Freight Order to Transwide and BluJay.
  • Orders can be placed with truckers using Transport Order Forms and emails.
  • No integration on track and trace.

Option 2

Include BNL as project scope for LAM and APAC. Integrate with Transwide and BluJay

(plus) Option for integrated network for LAM and APAC.

(plus) Flexibility for regions on how to organise their transport.

(minus) Multiple systems that have similar functions.


Option 3

Replace Transwide and deploy BNL to LAM and APAC. Integrate with BluJay

(plus) Transwide can be retired

(plus) Option for integrated network for LAM and APAC.

(plus) NAM can keep using BluJay, which they are familiar with.

(minus) Dual solution.


Option 4

Global rollout of BNL and replace Transwide and BluJay for road freight.

(plus) Transwide can be retired

(plus) Option for integrated network for LAM and APAC.

(minus) Higher scope and project risk for successful deployment.

(minus) Can BNL be a good enough replacement for BluJay?

(minus) Other modes of transport might keep the integration with BluJay necessary.


Evaluation

n/a

Change log

Version 

Date

Author

Change log

0.1

13 Jun 24

Nico van Os

Initial version









Workflow history