QWT BusinessIntelligencePlan
QWT BusinessIntelligencePlan
Copyright 2011 QlikTech International AB, Sweden. Under international copyright laws, neither the documentation nor the software may be copied, photocopied, reproduced, translated or reduced to any electronic medium or machine-readable form, in whole or in part, without the prior written permission of QlikTech International AB, except in the manner described in the software agreement. QlikView is a registered trademark of QlikTech International AB. In the United States of America and Canada, QlikView is a registered trademark of QlikTech , Inc . Microsoft, MS-DOS, Windows, Windows NT, Windows 95, Windows 98, Windows ME, Windows 2000 Windows XP, Windows Vista, SQL Server, FoxPro, Excel, Access, ActiveX, the Internet Explorer logo, and MS Query are trademarks of Microsoft Corporation. IBM, AS/400 and PowerPC are trademarks of International Business Machines Corporation. Borland, Paradox and dBASE are trademarks of Borland International. ORACLE and SQL*Net are trademarks of Oracle Corporation. Apple, TimeType, Macintosh, PowerMacintosh and MacOS are trademarks of Apple Computer, Inc.
Table of contents
1. QWT BUSINESS INTELLIGENCE PROJECT REQUIREMENTS ..............................................II 1.1. BUSINESS NEED .................................................................................................................................II 1.2. DOCUMENT SUMMARY ......................................................................................................................II 2. ANALYSIS REQUIREMENTS ......................................................................................................... III 2.1. KEY MEASURES ............................................................................................................................... III 2.2. KEY PERFORMANCE INDICATORS..................................................................................................... IV 2.3. KEY DIMENSIONS.............................................................................................................................. V 2.4. TRENDS ............................................................................................................................................. V 2.5. KEY SELECTION FILTERS .................................................................................................................. VI 2.6. SECURITY ......................................................................................................................................... VI 3. TABLE OVERVIEW ......................................................................................................................... VII 3.1. CUSTOMERS DATA .......................................................................................................................... VII 3.2. PRODUCTS DATA ........................................................................................................................... VIII 3.3. CATEGORIES DATA .......................................................................................................................... IX 3.4. SHIPPERS DATA................................................................................................................................. X 3.5. SHIPMENTS DATA ............................................................................................................................ XI 3.6. ORDERS DATA ................................................................................................................................ XII 3.7. ORDER DETAILS DATA................................................................................................................... XIII 3.8. DIVISIONS DATA ............................................................................................................................ XIV 3.9. EMPLOYEES DATA .......................................................................................................................... XV 3.10. OFFICES DATA ............................................................................................................................. XVI 3.11. SUPPLIERS DATA......................................................................................................................... XVII 3.12. BUDGETS DATA ......................................................................................................................... XVIII
Page i
1.1.1. Analysis requirements include: Multiple Key Business Indicators (KPIs) Sales geographic analysis Trend analysis covering a minimum of two years of detailed data. Budget to Actual sales comparisons Possibilities to make Budget prognosis
Business analysis must include logical integration across multiple business data sources and functional areas. The presentation layer for this analysis should deliver this integrated data transparently to all users.
Page ii
2. Analysis requirements
This chapter will list the requirements for the users to make the analysis necessary to drive the business. Necessary Key Measures, Key Performance Indicators, Key Dimensions, Trends and Selection filters will be mentioned.
Measure
Description
LineSalesAmount
The Net amount of the sale on the [Order Details] level, calculated as: (UnitPrice * Quantity) * (1-Discount) The Net amount of the Sale on Order level, the LineSalesAmount aggregated up on Order level. The relative percentage of OrderSalesAmount for a single value in a dimension field compared to the total of all other possible values in that field. The cost of the products sold on [Order Details] level, calculated as: Products.UnitCost * [Order Details].Quantity The Margin for products sold, calculated as: (([Order Detail].UnitPrice * [Order Detail].Quantity) * (1-[[Order Detail].Discount)) - (Products.UnitCost * [Order Details].Quantity) The sum of unit quantity over all possible data: Quantity Count of distinct orders: Order.OrderIDCounter Count of distinct products: [Order Details].ProductIDCounter Count of distinct employees: Employee.EmployeeIDCounter Count of distinct employees responsible for sales: Count of distinct employees responsible for sales: [Orders].[EmployeeID] inner join to [Employee].[EmpID] - or [Employee].[Title] Like Sal or President Average of [Employee].[Year Salary]
1.1.2
OrderSalesAmount
1.1.3
OrderSalesAmount %
1.1.4
CostOfGoodsSold
1.1.5
Margin
Total Unit Quantity Total Orders Total Products Sold Total Employees SalesPerson
1.1.11
Page iii
2.1.1. Business Rules 1. The data should include detailed transaction level data for a minimum of 2 years, and preferably four years. 2. The Sales Force Structure is selectable from the Office City down to the Sales Person. This should allow drill down from the National level Possible future enhancements: Market Share
KPI
Description
OrderSalesAmount Change
1.2.2
OrderSalesAmount Change %
The amount of change in Net Sales value from previous year to current year by Customer The amount of change in Net Sales value from previous year to current year by Customer expressed as a percentage The comparison of budget revenue amount to actual revenue amount by year. Actual revenue being OrderSalesAmount
1.2.3
2.2.1. Business Rule Possible future enhancements: Market Share ALERT: Provide Email notification for all products on backorder, along with their backorder amounts ([Products.UnitsOnOrder] [Products.UnitsInStock]) > 0
Page iv
Field
Description
Customers.CompanyName Customers.ContactName Office.City Employee.[First Name] Employee.[Last Name] for employees with sales responsibilities From CategoryID field. ID 5 or 6 =Footwear, rest 0 Clothing Category.CategoryName
1.3.5
Category Type
1.3.6
Category
2.4. Trends
Trends are used for selections and in charts in order to get the correct analysis results. The following table lists the Time Dimension Trending to be included in the analysis application.
No.
1.4.1 1.4.2 1.4.3 1.4.4 1.4.5 1.4.6
Field
Description
Orders.OrderDate Day of Orders.OrderDate Month of Orders.OrderDate Quarter of Orders.OrderDate Year of Orders.OrderDate 24 Rolling Months from last month of data for Orders.OrderDate. Format should be : MMM-YYYY (e.g. Jan-2007)
2.4.1. Business Rules 1. Drill down of Order Date should be possible from Year to Quarter to Month to Day.
Page v
Field
Description
Customer Customer Country Customer City Product Category Year / Quarter / Month / Day / Date Rolling Month SalesPerson
Customers.CompanyName Customers.Country Customers.City Products.ProductName Catagories.CategoryName Based on Orders.OrderDate Based on Orders.OrderDate Employees responsible for sales: Orders.EmployeeID inner join to Employee.EmpID - or Employee.Title begins with Sal or President
2.5.1. Business Rules 1. Drill down of Order Date time should be possible from Year to Quarter to Month to Day.
2.6. Security
This application will be distributed to employees involved in sales. Each salesperson, however, should not have access to data pertaining to their peers. There should also be one or more administrators to manage the document. One of the salespersons, James Bosch, is also the Sales Manager of the company, and he should have access to the entire set of data. In addition, the Sales Coordinator in Lund should have access to the data on all salespersons in the Lund office.
Page vi
3. Table overview
An overview of all the tables in the application is placed in this section. This overview shows the original tables. Alterations may be needed in order to create a good structure when reading the tables into QlikView.
3.1.2.1. Business Rules 1. Customers have single contact 2. State / Province code is optional as required 3. Customer data is updated weekly
Page vii
Page viii
Page ix
Page x
Page xi
3.6.3. Business Rules 1. One-to-many relationship with [Order Details] table 2. Employee link determines company sales by office 3. Orders data is updated daily
Page xii
3.7.3. Business Rules 1. 2. 3. 4. 5. 6. OrderID must exist in [Orders] table ProductID must exist in [Products] table Quantity must be > 0 Discount must be between 0 and 1 Discount applies to [Order Details].[UnitPrice] Order Details data is updated daily
Page xiii
Page xiv
3.9.3. Business Rules 1. Contains current employees only 2. [Reports To] field is subset of [EmpID] field 3. [Extension] is optional
Page xv
Page xvi
Page xvii
3.12.3. Business Rules 1. Office and EmployeeID creates link to Employees table 2. Only Employees that has begun to sell receives a budget
This data file is not used in the exercise, but is included for legacy purposes.
Page xviii