how to reporting?
TRANSCRIPT
![Page 1: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/1.jpg)
@rastislav.neczli
How start with reporting...
![Page 2: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/2.jpg)
MIKE 2.0
![Page 3: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/3.jpg)
![Page 4: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/4.jpg)
Logical steps for BI development
• requirements
• specifications
Business requirements
• ER model or dimensional model
• Design of reports
Design • Database
• Model of reporting system
System
![Page 5: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/5.jpg)
Information request analysis
Detail design of reporting system
Approving of design
Analysis of source systems
Design of information map
Verification of current status
To be status of information using
Consolidation current vs. To-be
Prioritisation
Homogenisation
Re-prioritisation
Target goup
Information receivers
![Page 6: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/6.jpg)
Phase 1 initialisation of project
1.1 Target group
• Define scope of reporting system and information requirements
• Define basic proces view
• Brief describe target group for information receiving
1.2 Information receivers
• Detail description of receivers (for example: department manager, top management, etc.) and how will be information use (for example: cost analysis, reporting KPI, ...)
• IMPORTANT: Is necessary join processes with copmany goals
Target group
Information receivers
![Page 7: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/7.jpg)
Phase 2 : Current status analysis
step 2.1: Verification of current status
• Description: detail description of report
• Period: periodicity of report (D/M/Q/Y)
• Structure: description of report (for example header a body of report), remarks to report (lack of information, amount of information, difficulty to prepare, etc.) and how is used
• Receivers: who is requesting report
• Responsible: exact identification about responsibility
• Attributes : dill levels
Step 2.2: Design of information map
• According defined processes from phase 1 is necessary define reports with relationship to process and activity
Step 2.3: Analysis of source systems
Analysis of source systems
Design of information map
Verification of current status
![Page 8: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/8.jpg)
![Page 9: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/9.jpg)
![Page 10: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/10.jpg)
![Page 11: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/11.jpg)
![Page 12: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/12.jpg)
Phase 3 TO - BE 1/2
To be status of information using
Consolidation current vs. To-be
Prioritisation
Homogenisation
Re-prioritisation
![Page 13: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/13.jpg)
Phase 3 TO - BE 2/2
Step 3.1: To be status of information using
• požiadavky na ďalšie výkazy, návrhy na korekciu existujúcich výkazov
Step 3.2 : Consolidation current vs. To-be
• sumarizácia všetkých výkazov do finálnej podoby
Step 3.3: Priority setup
• Priradenie dôležitosti a priority k jednotlivým výkazom
Step 3.4: Homogenisation
• Definition of calculation and attributes, granularity and periodicity of information
• Prepare single version of truth
Step 3.5: Re-prioritisation
• Výsledky analýzy zdrojových systémov môžu ovplyvniť priority výkazov (chýbajúce dáta)
![Page 14: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/14.jpg)
Zdroj: Holten, R.: Framework and
Method for Information Warehouse Development Processes
Metodika MetaMIS - elementy
![Page 15: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/15.jpg)
MetaMIS - definícia reportu
![Page 16: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/16.jpg)
ADAPT methodology
![Page 17: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/17.jpg)
Phase 4 Design
Step 4.1: Detail design of reporting system
• Creating of blueprint with exact definition of reports (use cases, design od reports, attributes, data model )
Step 4.2: Blueprint approving
Detail design of reporting system
Blueprint approving
![Page 18: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/18.jpg)
Information request analysis
Detail design of reporting system
Approving of design
Analysis of source systems
Design of information map
Verification of current status
To be status of information using
Consolidation current vs. To-be
Prioritisation
Homogenisation
Re-prioritisation
Target goup
Information receivers
![Page 19: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/19.jpg)
Conclusion
• Analysis is focusing to achieve agragated model of information (“information map”). Based on this is auditing current status of information achieving. For this we use set of our business questions (industry specific) witch understanding for end users
• Requirements are exactly defined in line with company strategy and their processes. Is not depends from supplier knowledge
• With this methodology we make quick projects with longer “durability” solution
19
![Page 20: How to reporting?](https://reader033.vdocuments.us/reader033/viewer/2022052413/55a352231a28abfe478b4818/html5/thumbnails/20.jpg)
Thank you!
Questions?
Feel free to reach out!
rastislav.neczli @itmg.sk