how to reporting?

@rastislav.neczli

How start with reporting...

MIKE 2.0

Logical steps for BI development

• requirements

• specifications

Business requirements

• ER model or dimensional model

• Design of reports

Design • Database

• Model of reporting system

System

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

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

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

Phase 3 TO - BE 1/2

To be status of information using

Consolidation current vs. To-be

Prioritisation

Homogenisation

Re-prioritisation

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)

Zdroj: Holten, R.: Framework and

Method for Information Warehouse Development Processes

Metodika MetaMIS - elementy

MetaMIS - definícia reportu

ADAPT methodology

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

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

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

Thank you!

Questions?

Feel free to reach out!

rastislav.neczli @itmg.sk