brief explanation how build reporting system

1. How start with reporting...
@rastislav.neczli

2. MIKE 2.0

4. Logical steps for BI development
Design
• requirements • Database
• specifications • ER model or • Model of
dimensional reporting system
model
• Design of reports
Business
System
requirements

5. Information request analysis
Verification of current
status
Target goup
Design of information
map
Information receivers
Analysis of source
systems
To be status of Consolidation current vs.
information using To-be
Prioritisation
Homogenisation
Re-prioritisation
Detail design of
reporting system
Approving of design

6. Phase 1 initialisation of project
1.1 Target group
• Define scope of reporting system and
information requirements
Target group
• Define basic proces view
• Brief describe target group for
information receiving
1.2 Information receivers
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

7. 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) Verification of current
status
• Structure: description of report (for example
header a body of report), remarks to report
(lack of information, amount of information, Design of information
difficulty to prepare, etc.) and how is used map
• Receivers: who is requesting report
Analysis of source
• Responsible: exact identification about systems
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

12. Phase 3 TO - BE 1/2
To be status of Consolidation current vs.
information using To-be
Prioritisation
Homogenisation
Re-prioritisation

13. 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)

14. Metodika MetaMIS - elementy
Zdroj: Holten, R.: Framework and
Method for Information Warehouse Development Processes

15. MetaMIS - definícia reportu

16. ADAPT methodology

17. 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

18. Information request analysis
Verification of current
status
Target goup
Design of information
map
Information receivers
Analysis of source
systems
To be status of Consolidation current vs.
information using To-be
Prioritisation
Homogenisation
Re-prioritisation
Detail design of
reporting system
Approving of design

19. 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

20. Thank you!
Questions?
Feel free to reach out!
rastislav.neczli @itmg.sk