This application was made to give and share within the industrial Rhodia family important KPIs to follow.
In addition to the KPIS which were more or less know by all the industrial manager, a new axis was put in place, the Value Stream (VS).
A Value Stream is defined by a consistent set of products manufactured on a given industrial asset.
Reporting coordinator in charge of this application is Célia Gonzalez (from I&P Stream)
460 users are splited in the world.
They are Value Stream manager, plant manager or industrial director.
There is no critical period, this dashboard is uploaded once a month, the first week-end after the 6th working day, which is generaly the second weekend of the month.
This application has been developped in 2007-2008.
The industrial project leader was Jean-Louis Tartarin and the IS project Leader was Sylvie Kramdi.
The two developpers were Olivier Morard (Keyrus) for the data modeling and Nathanaël Quinson (Keyrus) for the Bex query and the dashboard in the workbook.
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M20 | VS - Value Stream | Role for the menu |
| ZBI_RCS_VS_A02 | Value Stream Analysis - Transactional Data - End User role | Applicative role given access to the infoproviders |
| ZR_RCS_VS_P* | Value Stream Analysis - Access to ALL Values Stream | Confidentiality role. One role per Value Stream given access to the VS slice of the cube |
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
WP1 via WBP, there is no direct extraction from WP1 during the process chain, we just use all the DSO already loaded from the different applications
APO for the schedulling adherence
Oracle database of the Pilotages for the Customer OTIF
Flat Files:
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
This industrial dashboard is dependant to:
There are two dedicated process chain to load the industrial dashboard during the weekend.
Today this dashboard is launched manually because we need to make sure that the weekly CO-PC process chain launched friday at 6:00 pm CET is successfully finished.
This dashboard is uploaded once a month, the first week-end after the 6th working day, which is generaly the second weekend of the month.
The time for this process chain is never the same because each month, the selection is different.
Begining of January, we will extract 24 months (full Y and Y-1), so it is the longuest process chain, more than 24 hours.
At the opposite, in february it will be the fastest because only 13 months will be lauded (Jan for Y and full Y-1)
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
The End users are not "playing" with the BEx Analysis/Analyser but with a dashboard developped in an Excel workbook.
All the documentation is in this GDoc document:
All the queries used in the dashboard are documented in the following document:
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016