You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

General presentation

Objective of the application

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)

 

Usage information

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.

History

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.

Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Role CodeRole DescriptionExplanation
ZR_RCS_CA_M20VS - Value StreamRole for the menu
ZBI_RCS_VS_A02Value Stream  Analysis - Transactional Data  - End User roleApplicative role given access to the infoproviders
ZR_RCS_VS_P*Value Stream  Analysis - Access to ALL Values StreamConfidentiality role. One role per Value Stream given access to the VS slice of the cube

Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation
  
  
  

Dataflow overview

Source systems:

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:

  • Overall equipment effectiveness (OEE)
  • JNI

 

The Global overview is the following one:

 

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Dependencies with other applications

This industrial dashboard is dependant to:

  • TIERS for the transportation costs
  • SPRINT for the raw material costs
  • Inventory management for the stock material mouvement
  • Production Planing for the production process Orders
  • CBS for the fixed costs

Data loadings

Info providers and objects loaded

 

 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.

Loading frequency

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.

 

Average performance

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 FigureEstimation
~ Average Process Chain Runtime 
~ Average nb of rows loaded per load 
~ Total nb of rows loaded (if full) 
~ Average Runtime for 10k lines 

Record Keeping

Reporting

Queries End User Documentation

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: 

 

Main queries

All the queries used in the dashboard are documented in the following document: 

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution

 

  • No labels