The WBP BW QM application is created to follow
Data from Statistics :
By Infoproviders :
| Calendar Year/Month | JAN 2016 | FEB 2016 | MAR 2016 | APR 2016 | MAY 2016 | JUN 2016 | Overall Result | |
| InfoProviders Used | Query Access Counter | Query Access Counter | Query Access Counter | Query Access Counter | Query Access Counter | Query Access Counter | Query Access Counter | |
| Overall Result | 336 | 301 | 571 | 444 | 296 | 424 | 2 372 | |
| ODSO/A/ODS_QM09 | Inspection Results: | 290 | 238 | 463 | 405 | 256 | 365 | 2 017 |
| MPRO/A/MPR_QM001 | WBP_400/MPRO/A/MPR_QM001 | 33 | 22 | 67 | 26 | 25 | 25 | 198 |
| ODSO/A/ODS_QM08 | Inspection Results: | 11 | 25 | 15 | 6 | 5 | 3 | 65 |
| ODSO/A/ODS_QM02 | Notification - Task | 2 | 7 | 2 | 4 | 13 | 28 | |
| ODSO/A/ODS_QM06 | Notification | 2 | 6 | 2 | 4 | 9 | 23 | |
| ODSO/A/DSO_QM10 | QM Preparation Trans | 1 | 5 | 9 | 2 | 1 | 1 | 19 |
| ODSO/A/DSO_QM11 | QM Preparation Trans | 1 | 3 | 1 | 1 | 1 | 2 | 9 |
| ODSO/A/ODS_QM05 | Notification - Item | 0 | 2 | 0 | 0 | 5 | 7 | |
| ISET/A/IFS_QMTR | QM x TR | 4 | 1 | 0 | 1 | 6 |
By Queries :
| Calendar Year/Month | JAN 2016 | FEB 2016 | MAR 2016 | APR 2016 | MAY 2016 | JUN 2016 | Overall Result | |
| Query | Query Access Counter | Query Access Counter | Query Access Counter | Query Access Counter | Query Access Counter | Query Access Counter | Query Access Counter | |
| Overall Result | 336 | 301 | 571 | 444 | 296 | 424 | 2 372 | |
| ELEM/A/BW_QRY_ODS_QM09_0005 | BW - QM Results - Column (Core Query) | 186 | 145 | 350 | 286 | 165 | 262 | 1 394 |
| ELEM/A/BW_QRY_ODS_QM09_9000 | QM - Inspection Results by Lot | 58 | 58 | 87 | 85 | 67 | 52 | 407 |
| ELEM/A/BW_QRY_ODS_QM09_0004 | BW - QM Results (Core Query) | 28 | 21 | 23 | 28 | 18 | 42 | 160 |
| ELEM/A/BW_QRY_MPR_QM001_QVRCSKPI_0000 | RCS QM KPI - Quality Results for Shipment (Core Query) | 25 | 20 | 33 | 21 | 22 | 22 | 143 |
| ELEM/A/BW_QRY_MPR_QM001_0001 | BW - Quality Results for Deliveries (Core Query) | 8 | 2 | 34 | 5 | 3 | 3 | 55 |
| ELEM/A/BW_QRY_ODS_QM09_0002 | BW - QM Statistics (Core Query) | 16 | 13 | 0 | 5 | 4 | 8 | 46 |
| ELEM/A/BW_QRY_ODS_QM02_9001 | BW Brazil - QM - Notification - Tasks | 2 | 7 | 2 | 4 | 12 | 27 | |
| ELEM/A/BW_QRY_ODS_QM08_9003 | QM - Laboratory Billing (by Determinations) | 4 | 13 | 4 | 1 | 1 | 1 | 24 |
| ELEM/A/BW_QRY_ODS_QM06_9000 | BW Brazil - QM - Notifications | 2 | 6 | 2 | 4 | 9 | 23 | |
| ELEM/A/BW_QRY_ODS_QM08_9004 | QM - Laboratory Productivity (by Workcenter) | 4 | 9 | 3 | 3 | 1 | 1 | 21 |
| ELEM/A/BW_QRY_ODS_QM08_9005 | QM - Laboratory Productivity (by Analyst) | 3 | 3 | 8 | 2 | 3 | 1 | 20 |
| ELEM/A/BW_QRY_DSO_QM10_9001 | BW - QM Laboratory's Productivity (Solution's Factorization) | 1 | 5 | 9 | 2 | 1 | 1 | 19 |
| ELEM/A/BW_QRY_ODS_QM09_0001 | BW - Analytical time (Core Query) | 1 | 1 | 3 | 1 | 2 | 1 | 9 |
| ELEM/A/BW_QRY_DSO_QM11_9001 | BW - QM Laboratory's Productivity (Solution's Preparation) | 1 | 3 | 1 | 1 | 1 | 2 | 9 |
| ELEM/A/BW_QRY_IFS_QMTR_0001 | BW - Quality Results for Shipment (Core Query) | 4 | 1 | 0 | 1 | 6 | ||
| ELEM/A/BW_QRY_ODS_QM05_9000 | BW Brazil - QM - Notification - Item | 0 | 0 | 0 | 0 | 4 | 4 | |
| ELEM/A/BW_QRY_ODS_QM05_0002 | BW - QM Notification Items (Core Query) | 2 | 1 | 3 | ||||
| ELEM/A/BW_QRY_ODS_QM09_0003 | BW - QM Lead Time (Core Query) | 1 | 0 | 1 | ||||
| ELEM/A/BW_QRY_ODS_QM02_0001 | BW - QM Notification Tasks (Core Query) | 0 | 0 | 1 | 1 | |||
| ELEM/A/RCS_QRY_ODS_QM09_0007 | BW - QM Results for maintenance PM (Core Query) | 0 | 0 | 0 |
History
Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
https://docs.google.com/presentation/d/1BEtcW74HlAltYo9FWxzcxFPDcIIrIcAr_Xx01JJ2vsI/edit#slide=id.p
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 with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
Detail of frequency : monthly; weekly or else
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
| 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
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
List the most important and complex queries only with a link to the documentation
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