2.0 Business Process

2.1. Introduction

The Transportation Costs analysis was developed in 2007 to attend the Rhodia users of Logistic processes. The solution had usage several DSO’s and just one cube with many detailed information. The number of tickets about inconsistency of data and bad performance some of triggers to develop a new application, in this case much more robust and covering also the Solvay data and its users.

The TIERS project was started in the begin of 2015, using a remodelling by layers Layered Scalable Architecture (LSA), in our case: propagation, business, reporting and virtual layers. The current transportation datasources from Rhodia were reused with low change and all datasources from Solvay were activated with low enhancements. Some additional master data were created to avoid duplication of data in different providers, like shipment document, shipment cost item and delivery item. The development of project was request by the logistic areas in April/2015 and was deployed in December/2015.

2.2. Objective of application

The objectives of this application is as follows:

• To create One unique, common and consolidated reporting space and solution for the Solvay group
• The rationalization of the “live” solutions and reduction of evolutions requested 
• To have a solution which is maintainable and sustainable.
• To streamline and Enable productivity actions on Shipment costs
• To implement a Drillable solution which allows the possibility to detect and analyse problems by showing the link from aggregated figures down to document in SAP.
• Few “core” queries/workbooks design for application (=> Use BW analysis functionalities and not just as extractor).

2.3. Benefits

The benefits of creating this solution was 

• To create revamped BW reporting solution based on RCS (WBP-TR002) but built on old historical architecture (no project on this application for years) - mainly designed for cost reporting.
• To have only aggregated monthly data available on PF1.
• To have a specific solution (cross legacies) built for CO2 footprint with activation of some standard extractors on PQ1.
• To help maintain queries in an effective way. 
• Some previous experiences of common transversal reporting tools : WISE (working cap.) and SPRINT (Purchasing and Procurement).

2.4. Core Business Processes??

The key associated business processes

The TIERS project consists in implementing a simplified global reporting solution for transport  process, from planning to invoice to meet the requirements from GBUs users, SBS users and transport buyers, including processes from both companies (Solvay & Rhodia).

This solution will provide:

• automatic & consolidated BW reports on shipment costs
• based on data coming from the ERPs from both legacies (Solvay – PF1, Rhodia – RCS)
• enabling to drill-down to the ECC object at the origin of the detailed figures 
• updated on daily basis 

2.5. Accessing Queries

To access the queries follow the below steps

1. Go to BW Analysis
2. Select WBP
3. Select Role (Tiers)
4. Select Query

1. Input relevant prompts
2. Wait for data to load

3.0 Application Feature Overview

This section contains Information about the existing Workbooks and the respective BW queries.

3.1 Query Overview

The below lists the Query/Workbooks for this application

4.0 Functional Specification

This section approaches the concepts/definitions used in all the reports and required to understand the data from the reports.

4.1 General Data

1 - Shipment cost details analysis

• Propose a detailed analysis of shipment cost accruals, detailled by materials. Make shipment costs accruals understandable.
• Allows benchmarking between materials, between customers.
• Gives some possibilities of drill down to get details on a macro figure.
• Public: sites log managers / GBU log process teams, base for Qlikview reportings

2 - Shipment cost vs invoice analysis 

• Propose advanced cost analysis functionalities including invoice / accrual comparision and other ratios that can't be available at material level.
• Detect / evaluate unbilled payables.
• Audit tarif calculation
• Public: finance / controlling, sites & GBU logistics managers, data log and support teams

3 - Shipment status and events

• Propose tracking of events on shipments. without cost considerations.
• Propose a reporting on volumetry : number of files (delivery or shipment) per flow, average value on some indicators...
• Load plan of shipping points

• Public: LOG data and support teams, GBUs sites log managers and sites operations supervisors, Transport managers

4 - CO²  Emissions

• The propose is to show the calculations about quantity of carbonic gas that is released in atmosphere considering all the shipments by zone
• Public: users that manage the environment effects and reports to governments

5 - Shipment Events 

• The propose is to show the events (problems) involving the hauliers that happened during the logistic process 

• Public: GBUs sites log managers and sites operations supervisors, transport managers

4.1.2. Perimeter

Currently the WBP Tiers Application contains data coming from the  PF1 and WP1 ERP server.

4.1.3. Access

Access to the Tiers Application has to be requested (See Getting an account). Access is managed at company level, which you will need to precise when requesting the access 

4.2 Process Detail 

This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.

Targeted users have been grouped in 3 user profiles depending on the reporting activities they will handle.

Cost analysis needs :

• Detailed mapping of calculated costs (accruals)

• By haulier

• By site / plant

• By ship_to (customers)

• By shipment or shipment attribute like shipment departure point / destination point / mode / type)

• By delivery or delivery attribute like shipping condition, shipping point...

• Accrual versus invoiced value

• By shipment or shipment attributes.

• By haulier

• Time analyses

• By month of shipment completion (planned / actual)

• By shipment cost posting date

• Detailed accrual analysis by nature of cost

• Accrual net value by shipment cost item category

• Valuated condition by cost condition

• Ratio calculation

• Value per ton

• Value per KM

• Value per To/KM

• Value per container

• Value per shipment

Operation reporting needs:

• Volumetry (number of shipment & number of deliveries)

• Per GBU/plant

• Per Shipment Departure point/Shipment Destination point

• Per date (Year / Year-Month)

• Average payload per shipment

• Volumetry (number of containers)

• Per GBU/plant

• Per Shipment Departure point/Shipment Destination point

• Per date (Year / Year-Month)

• Average payload per container

• Haulier evaluation 

• % OTS shipment (planned completion = actual completion) 

• % OTD shipments (planned shipment end = actual shipment end)

• Number of event / Type of event / Number of shipment

• Leadtime analyses

• % of shipments with calculable transit time

• % of shipments with calculable queue time

• % of shipments with calculable “on site time”

• Average Actual transit time (shipment end - shipment completion)

• Average “queue time” (loading start - check in)

• Average “on-site” time (completion - check in)

• Average booking leadtime (shipment start - planification date)

C02 Footprint :

• Tons and Distances by mode

• CO2 emission (by mode, by GBU…)

4.2.2.  Calculations

The below illustrates the key figures required for each query and the respective figures required to how they are calculated

• C02 Footprint: 

For CO2 Footprint calculations, the required figures are 

• Gross Weight Distance

  • This figure refers to a formula or calculation used to estimate or calculate the carbon dioxide (CO2) emissions associated with transporting goods based on the weight of the cargo and the distance it travels.

• Gross weight x distance 

  • This figure refers to a formula used to estimate or calculate the carbon dioxide (CO2) emissions associated with the transportation of goods. This formula takes into account the gross weight of the cargo (the total weight of the goods and their packaging) and the distance the goods are transported.

• CO2 emission factor

  • This figure represents the amount of carbon dioxide (CO2) emissions generated per unit of a specific activity or resource. It is used to estimate the CO2 emissions associated with various processes, transportation modes, or energy sources.

• CO2 emission

  • This figure involves measuring or estimating the actual CO2 emissions produced from various activities within the supply chain.

• Shipment costs detailed analysis: 

For Shipment costs detailed analysis calculations, the required figures are 

• Net Value

  • Net value calculation involves a multi-level data aggregation process, data is initially collect from the "stored at shipment" stage, then "cost item x delivery item level" and then a summation or aggregation of this data is performed.

• Net/Gross Weight 

  • Net/Gross weight calculation involves a two-step process. First, data is calculated at the "delivery item x shipment stage level," and then summed at the "delivery item x shipment" level, But not on shipment stages, providing a higher-level view of the delivery process.

• Distance in KM 
  • Distance in KM calculation involves a two-step data aggregation process. First, data is collected or stored at the "shipment stage" and "delivery item" levels. Then, the data is aggregated at two higher levels: "stages" and "shipments." But not on delivery items nor deliveries. The output is a higher-level summary that can offer insights into the performance or metrics associated with different stages and overall shipments within the delivery process.

• Detailed cost condition value 
  • This calculation involves then "stores at delivery item x shipment stage x condition type". Then a summation of all data is performed.

• Accrual costs vs invoice analysis: 

For Accrual costs vs invoice analysis calculations, the required figures are :

•  Net Value

  • Net value calculation involves a multi-level data aggregation process, data is initially collect from the "stored at shipment" stage, then "cost item x delivery item level" and then a summation or aggregation of this data is performed.

• Invoiced Value

  • This figure involves adding up the data associated with all the purchase orders within each shipment. The calculation is "Shipment" x "Purchase Order" (PO) levels.

• Net/Gross weight
  • Net/Gross weight calculation involves a two-step process. First, data is calculated at the "delivery item x shipment stage level," and then summed at the "delivery item x shipment" level, But not on shipment stages, providing a higher-level view of the delivery process.

• Distance in Km
  • Distance in KM calculation involves a two-step data aggregation process. First, data is collected or stored at the "shipment stage" and "delivery item" levels. Then, the data is aggregated at two higher levels: "stages" and "shipments." But not on delivery items nor deliveries. The output is a higher-level summary that can offer insights into the performance or metrics associated with different stages and overall shipments within the delivery process.

• Detailed cost condition value
  • Data is calculated by adding "stored at delivery item" x "shipment stage", x "condition type", then perform a summation or aggregation of this data.

• Number of containers
  • Data for "stored at shipment level" is the aggregated data required for this key figure. This data relates to shipment-specific details such as shipment tracking information, delivery dates, quantities, contents.   

• Number of Hus
  • This figures aggregation "stored at shipment x delivery level but presented only at shipment level then summed" combines the data for each shipment. This means that all the data for individual delivery items within a shipment is summarized to provide a higher-level view of the entire shipment's data.

• Shipment events

For Shipment events calculations, the required figures are :

• Counter on event
  • This figure is used to monitor and record the number of times a particular event or milestone occurs.

• Event duration
  • This figure is a measure of the time it takes for a specific event to be completed based on actual dates and time when registered.

• Shipment status and events calculations

For Shipment status and events calculations, the required figures are : 

• Nb "number" of shipments
  • This figure refers to the quantity or count of individual shipments
• Nb "number" of deliveries
  • This figure refers to the number or count of individual delivery actions.
• Nb  "number" of shipment stage
  • This figure refers to the number or count of these distinct stages within a specific shipment. 
• Nb "number" of shipment relevant for transit time calculation
  • This figure refers to the number of shipments to calculate or analyze transit times.
• Transit time

  • This figure measures the duration or elapsed time that a shipment is in transit.

• On site time
  • This figure refers to the amount of time that a shipment or delivery vehicle spends at a specific location or destination during its journey.
• Queue time
  • This figure refers to the amount of time that a shipment spends in a queue or waiting area before it moves on to the next stage of its journey or is processed
• Booking lead-time
  • This figure refers to the amount of time between the booking or reservation of a shipment and the actual shipment's departure or execution
• HOTD
• HOTS

4.2.3.  Data 

4.2.4.  Data Flows

The data flow below are from the service provider MVSDTR02 - TR Vir: Shipment Events (Solvay & Rhodia)

4.2.5.  Service Provider - MVSDTR01

The below are the Calculated and Restricted key figures associated with MVSDTR01

4.2.5.  Currency Conversion

• The X rate considered is the Daily Month Average (M) rate (table managed by finance team, source ECB - European Central Bank) based on Document creation date.

5.0 Non-functional Descriptions 

Please populate the relevant section and delete those that are not applicable.

5.8 Availability

5.9 Refresh of the Data

The data is updated daily around ~5 am Paris Time using delta process via process chain schedule.