General presentation

Objective of the application

The application loads data of the Plant Maintenance domain from ECC into BW. It takes every week snapshots based on the current state of the data to calculate the KPI. The snapshots are loaded into a Qlikview dashboard.

Main documentation:

List of contacts:

Usage information

Around XX key users on BW and XXX end users on QV. The tools is used by five plants worldwide during the PoC and the first deployment, it will be opened progressively to new plants.

Roles & Access

Roles and access

Authorisation objects

Dataflow presentation

Overview

Functional and Technical rules on Workbench + Reporting

<detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way

Dependencies :

Data loadings

Info providers and objects loaded + Loading frequency

Jobs WP1 + PF1 for GWOS KPI. Every night from Monday to Friday, and every Sunday at 23:00 GMT+1. Duration 10 minutes.
PC_PM_MECANO_01 (MECANO 01:00). Daily data loadings in BW. Every night from Sunday to Thursday at 20:00 GMT+1. Duration 3 hours.
PC_PM_MECANO_02 (MECANO 02:00). Weekly calculation of KPI. Every Monday at 01:00 GMT+1. Duration 1 hours and a half. It sends an email at the end.
PC_PM_MECANO_03 (MECANO 03:00) : Daily and Weekly loadings of GWOS KPI (2.4, 2.10, 2.14, 2.15, 2.16). Every night at 01:00 GMT+1. Duration 10 minutes.
PC_PM_MECANO_04 (MECANO 04:00) : Daily loadings of maintenance costs. Every night after FI loadings in RSP_DAILY. Duration 30 minutes.

Loadings start every Monday at 05:00 GMT+1.

Average performance

<if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube

The purpose is to give a general overview of the volume of data managed y the application>

Historization

We keep all the data in the Up to Date DSO, and we keep only one year of history for Snapshots in DSO and cubes. 

The deletion of old Snapshots is done in process chain based with deletion programs, it has been generated as described here : https://drive.google.com/open?id=0B6UtwJUYvmgTWjhHY0k0RG5xZjA

The programs have been modified to fill automatically the parameter C_SNAPWK for the deletion from the setting RET_WEEK from master data C_GBLFILT.

Reporting

Queries Documentation or user guide

Main queries

Main workbookrs :

Main functionnalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution

Actions to plan for a deployment on a new plant: