...
Objective of the application
<describe in a few words the content of application + link with functional or technical specifications (google links) >done with during the project or linked with PPMO>
• Tool Leader + IT leader of the application: <name of project or main leader for the application + reporting coodinator>
Usage information
< How many users? Which user category ? Is there critical period ? Which geographical perimeter?
Describe in one sentence: around 50 users, worldwide or 200 users / European Site>
Roles & Access
Roles and access
...
Dataflow presentation
Overview
...
Below is an example of dataflow.
1 - if no exisiting documentation,Copy and update this example in reporting documentation drive folder : https://drive.google.com/drive/folders/1WfvQ5RwKOs3973K1A_kgb7gucR97l67h
2 - If existing documentation, put it in the right drive folder and update the link
| Embedded Google Drive File | ||
|---|---|---|
|
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 with other application (BW, QV, Externals tools like PVelocity or
...
Dynasis etc...>
Data loadings
Info providers and objects loaded
...
<detail of frequency : monthly; weekly or else>
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
<Give details if any historization is done, example: keep only data greater than beginning of Y-3>
Reporting
Queries Documentation or user guide
<to be done on customer wiki>wiki : My Business Apps>
If not covered by queries documentation
Main queries
<list most important and/or complex queries only>
Main functionnalities
<give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts>
Broadcast .
<give some detail on broadcast settings>
Maintenance
Known bugs
<list recurring bugs and demand from users>
Recurring procedure
< list recurring procedure >
Planned Evolution
<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>