1. Reporting Business Intelligence .pptx

kirubaarun 13 views 28 slides Sep 09, 2025
Slide 1
Slide 1 of 28
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28

About This Presentation

Business Intelligence reporting chapter


Slide Content

BUSINESS INTELLIGENCE Unit V MAP Code : G SRI KRISHNA ARTS & SCIENCE COLLEGE [An Autonomous Institution] Ranked 53 rd in NIRF; MHRD: 1 st in Institutional Swachhata Ranking Coimbatore – 641 008 Facilitator Dr.S.Kirubadevi Assistant Professor Commerce BPS & BI SKASC 1

Voice Over Video Reference Video Animation Video SKASC 2

Standardized reporting Standardized reporting is an intricate type of reporting process that aims to produce consistent, reliable, actionable information from disparate systems or sources. A reporting process is standardized if it can be applied across different business units or sub-units in an organization. SKASC 3

Why standards matter Standard project reporting is important for two key reasons: Improved communication Time savings Improved communication is fairly obvious : when you present consistently across different projects, it’s easier for your audience to understand what is going on, and to draw conclusions across projects. SKASC 4

Cont… The time savings are important because a standard project view means that individual project managers aren’t spending several hours dreaming up their own custom formats for reporting. Instead, the format is already defined, and all they have to do is plug and play. SKASC 5

Which report elements to standardize Standardization is easier said than done, especially when you are trying to create a consistent reporting structure across scores of projects. Before you get too hung up on standardizing everything under the sun, remember that no two projects are alike. This means that no matter how strict your reporting standards are, the projects themselves are different, and the reports will be as well. SKASC 6

Here are some examples: Swimlanes :  If you go back to our earlier swimlane article, you know that it’s important to group and sort your project plan consistently. This holds true across your entire portfolio as well. Colors :  Our eyes easily pick up colorful cues in a project presentation. If you use a red color for risky items in one report, you should use red the same way in all reports. SKASC 7

Cont… Units of time :  If you show fiscal years in one report, show fiscal years in all reports. This makes it easier to understand what is happening when. Decorations :  As soon as you show a baseline for one project, your executives will want to see it for all schedules . The same is true for percent complete, and critical path. Think about which decorations your reports really need and then be consistent from one project to the next. SKASC 8

SKASC 9

Establish data consistency -standardized reporting process . Think of standardized reporting as an ongoing process, not a one-off deliverable . As such, the planning phases are critical. But all too often, an organization will skip over the step of defining the goal of the report. To obtain consistent data and unlock all the benefits of a standardized report, an organization can follow these steps: SKASC 10

Ask, “ What are we trying to accomplish with this report?”, “ What decisions are made using this information?”, and “What insights will help the organization achieve its goals?” Within a standardized reporting process, there are many things an organization might decide to track. The first step to getting data consistency is to understand what actually  needs  to be tracked. A holistic understanding of the purpose and what information must be conveyed will dictate the data requirements. SKASC 11 1 . Understand the decisions being supported by a given report .

. To achieve data consistency, there must be a predictable, measurable process in place. For example, the business systems team of a multinational organization wanted to develop a standardized report to understand how employees across 8 countries create internal SharePoint sites. The team wanted to reveal information like how long it takes for sites to be created , how many files are on each site, and how often employees request new sites to be set up. SKASC 12 2. Identify the standardized procedure for how data is generated .

Data may be captured and compiled manually in batches on a simple Excel spreadsheet , automatically in real time using a sophisticated ERP system , or a combination of both. Create an MVP process first to test out various mining approaches before investing in a more robust system. SKASC 13 3. Develop tools for mining the data.

Present the data in a layout that is easy to understand for the intended audience. Just as the data needs to be consistent, the report UI must be consistent to avoid confusion, improve clarity, and establish trust. SKASC 14 4. Design templates for presenting the data. 

Without proper training, human error will create variability in the data. Training and proactive IT support will help employees generate and collect data in a predictable manner and reduce friction from the standardized reporting process. SKASC 15 5. Train employees.

Types of Report Layout SKASC 16

Elements in a block layout band are arranged vertically. Block-level elements span the full width of the parent band. If an element expands, it pushes all other elements down so that no element overlaps any other elements. Master Report and Sub Report elements , as well as Groups, are always block elements. SKASC 17 BLOCK

In an inline formatting context, elements are arranged horizontally, one after the other, beginning at the top of a containing block. Horizontal margins, borders, and padding are respected between these boxes. The boxes may be aligned vertically in different ways: their bottoms or tops may be aligned, or the baselines of text within them may be aligned. The rectangular area that contains the boxes that form a line is called a  line box . SKASC 18 INLINE

The default layout scheme is  canvas , in which report elements have no positioning relationship to one another, and can potentially encroach on the space occupied by other elements in the band. The three other layout types are defined in the sections below. SKASC 19 CANVAS

The row layout scheme positions elements one after each other on the horizontal axis. All elements are printed in a single row , expanding their height as needed. If all elements expand to the height of tallest element, set the min-height to "100%" to even them out. This layout type is a natural match for list reports, where multiple columns of data should be printed per row. When an element expands its width, all other elements get pushed to the right. SKASC 20 ROW

Report Writing Format Title Section  – This includes the name of the author(s) and the date of report preparation.  SKASC 21

Summary  – There needs to be a summary of the major points, conclusions, and recommendations . It needs to be short as it is a general overview of the report . Some people will read the summary and only skim the report, so make sure you include all the relevant information. It would be best to write this last so you will include everything, even the points that might be added at the last minute. SKASC 22 Report Writing Format

Introduction  – The first page of the report needs to have an introduction.   You will explain the problem and show the reader why the report is being made. You need to give a definition of terms if you did not include these in the title section, and explain how the details of the report are arranged.   SKASC 23 Report Writing Format

Report Writing Format Body   – This is the main section of the report .  There needs to be several sections, with each having a subtitle.   Information is usually arranged in order of importance with the most important information coming first .  SKASC 24

Conclusion  – This is where everything comes together. Keep this section free of jargon as most people will read the Summary and Conclusion .        Recommendations   – This is what needs to be done. In plain English, explain your recommendations, putting them in order of priority. SKASC 25 Report Writing Format

Appendices  – This includes information that the experts in the field will read. It has all the technical details that support your conclusions. SKASC 26 Report Writing Format

Check Your IQ SKASC 27

SKASC 28
Tags