|
Accesses must be approved by the Macro-Package Team (Procurement)Click here for the Access request form. |
General Description |
|---|
Objectives: This dashboard is result of a Fuel for Growth initiative and therefore has been built to increase transparency on Car Fleet Operational KPIs. The objective of this Dashboard is to allow concerned stakeholders (GBU/Functions, Controlling, Finance, Procurement, HR, Fleet Management, Macro Package Team) to find relevant information about the latest state and evolution of their car fleet to:
A Quick Start Guide is available hereStructure & Content: 4 pages for users + 1 page (data checking) for dashboard management team |
Data Sources |
|---|
Useful information about data:
3 sources of data are feeding the dashboard:
Data sources of this dashboard are managed through the following application named “Car Fleet Source” which will transform raw data given by the team in charge of it, to an adapted file for our dashboard.
1. Costa data: The queries used to extract data from Co$ta are the following:
Extractions details are described in the Cost Transparency documentation: “Cost Transparency – Detailed Technical Documentation” in section 5.2.
2. ARI data: ARI data represents all the data at time T, we will have all information by column. Dropped source file in production environment, the following path: \\acew1pqlikapp01\shared sense\Solvay Data\Apps\CAR FLEET\SOURCE, then we will have to copy/paste these files into the development environment \\acew1pqlikapp02\shared sense\Solvay Data\Apps\CAR FLEET\SOURCE Source used in the dashboard are in the following field: \\acew1pqlikapp02\shared sense\Solvay Data\Apps\CAR FLEET\QVD, all these QVD will be named as: ARI_YYYY_MM
3. Dragintra data: In the DRAGINTRA data source file, we will have information by lines. Principle is the same as described in 2.2 for ARI data. To get more details on specification of the previous section (2.2, 2.3 and 2.4), please go here and see tab “Template #1 Vendors”. 4. Mapping: Transco mapping: These mapping are manage in the tab “TRANSCO MAPPING” from this file. It’s loaded and then converted into QVD file. These mapping are updated by the MP team. This mapping is used for main fields of the Car Fleet dashboard. GBU Function mapping: We also use a mapping already used in the Costs Transparency dashboard which is coming from this file: here, tab “GBU CBS_Cluster”. This file will help us to build the fields: ORIGIN_GBU_KEY and ORIGIN_GBU of Car Fleet dashboard. |
| KPIs description | ||||
|---|---|---|---|---|
1. Executive Summary
The first bar char below display the different measures which can be selected in
Pie chart below represents the number of EV/Hybrid vs total of cars per Fuel type. Here too, analysis axis can be changed in the drop-down list, analysis can be done at Vendors level
2. Fleet MGT & Cost Efficiency
As described in their respective title, the left pie chart represents the number of cars at Vendor level. If needed, the user can display the number of cars at the other level that are present in the drop-down list.
3. Policy compliance & sustainability Page starts with executive summary on our CO2 impact, in terms of trees offsetting (CO2 23kg for 1 tree), achievement vs Solvay One Planet goal (migrate our full fleet to electric and/or hybrid by 2025) and equivalent cost of CO2 (1 ton = 100 EUR).
The other graphics have the same behavior than the ones described previously, except that here we display CO2 emission KPI.
4. My Report MyReport view enable the user to create tables he wants regarding al the dimension of the dashboard. He can see the raw measures and make whatever analysis he wants.
5. Data checking (only to be used by dashboard owner / MP team) This view allow the user to see if dashboard’s dimensions are well mapped or not. We will find one table by mapped dimensions
|