0% found this document useful (0 votes)
948 views

QWT BusinessIntelligencePlan

QV Project Requirements

Uploaded by

Luis De Hoyos
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
948 views

QWT BusinessIntelligencePlan

QV Project Requirements

Uploaded by

Luis De Hoyos
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Qlik Wholesale Trade (QWT) Business Intelligence Plan

QlikView Developer Course

December 2011 Release QlikView Version: 11.00 English

1996-2011 QlikTech International

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.

This release: December 2011

1996-2011 QlikTech International

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

1996-2011 QlikTech International

Page i

1. QWT Business Intelligence Project Requirements


QWT provides high quality sports and leisure clothing products for men, women, and children to a wide range of wholesale customers located throughout the world. QWT is divided into different Sales offices with Sales representatives that focus on different customers. The products are divided into different categories of clothing.

1.1. Business Need


QWT Business Intelligence should provide summary to detail level sales data analysis through an easy-to-use, yet robust and flexible interface capable of handling multiple levels of user expertise and requirements.

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.

1.2. Document Summary


This document contains general reporting requirements, key measurements, and available data element types and descriptions. Critical axis dimensions and filters are also listed. It should be noted that not all data elements are located in standard database format.

1996-2011 QlikTech International

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.

2.1. Key Measures


Key measures are numbers that have a significant impact on the operation of the business. The following table lists the Key Measures to be included in the analysis application. Some of these measures will require calculation.
No.
1.1.1

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

1.1.6 1.1.7 1.1.8 1.1.9 1.1.10

Total Unit Quantity Total Orders Total Products Sold Total Employees SalesPerson

1.1.11

Average Annual Salary

1996-2011 QlikTech International

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

2.2. Key Performance Indicators


Key Performance Indicators (KPIs) are metrics used to reflect the critical success factors of the business. They help the business to measure progress towards the organizational goals. The following table lists the primary (KPIs) to be included in the analysis application. Ideally, these measurements will indicate compliance with business goals through an overall dashboard view, as well as detailed comparisons between company geography, customers, and products.
No.
1.2.1

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

Budget Actual Revenue

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

1996-2011 QlikTech International

Page iv

2.3. Key Dimensions


Key Dimensions are used in charts in order to get the correct analysis results. The following table lists the Key Dimensions to be included in the analysis application.
No.
1.3.1 1.3.2 1.3.3 1.3.4

Field

Description

Customer Customer Contact Sales Office SalesPerson

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

Order Date Day Month Quarter Year YearMonth

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.

1996-2011 QlikTech International

Page v

2.5. Key Selection filters


Key selection filters are used for selecting values to perform necessary analysis. The following table lists the Key Selection Filters to be included in the analysis application.
No.
1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.5.6 1.5.7 1.5.8

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

1.5.9 1.5.10 1.5.11 1.5.12

Sales Title Sales Office Supplier Division

Employee.Title begins with Sal or President Office.City Suppliers.CompanyName Divisions.DivisionName

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.

1996-2011 QlikTech International

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. Customers Data


3.1.1. File Information
Data Type ---------------------------------------------------------- MS Access Database ------------------------------------------------------------ QWT.mdb Table name --------------------------------------------------------- Customers Estimated Number of Records ----------------------------------- 100

3.1.2. Record Information


Field Name CustomerID CompanyName ContactName Address City StateProvince PostalCode Country Phone Fax Division Data Type (Max Size) Autonumber (Long Integer) Text (40) Text (40) Text (60) Text (20) Text (15) Text (10) Text (20) Text (24) Text (24) Integer Y Y Y Indexed Y Y Customer ID Full name of customer Name of primary contact at customer (First Last) Street or PO Box mailing address of customer City for mailing address of customer State or Province code for mailing address of customer Postal code for mailing address of customer Country for mailing address of customer Phone number includes country code or area code Phone number includes country code or area code Which Division a customer belongs to Comment

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

1996-2011 QlikTech International

Page vii

3.2. Products Data


3.2.1. File Information
Data Type ---------------------------------------------------------- MS Access Database ------------------------------------------------------------ QWT.mdb Table name --------------------------------------------------------- Products Estimated Number of Records ----------------------------------- 75

3.2.2. Record Information


Field Name ProductID ProductName SupplierID CategoryID QuantityPerUnit UnitCost Data Type (Max Size) Autonumber (Long Integer) Text (40) Long Integer Long Integer Long Integer Double Fixed 2 decimal Double Fixed 2 decimal Long Integer Long Integer Indexed Y Y Y Y Product ID Full name of product Link to Supplier Link to product category Count of product per unit Current cost of product, including manufacturing costs plus Selling, General and Administrative (SG&A) expenses Current unit price (List) of product Number of units in stock as of latest inventory Number of units on order Comment

UnitPrice UnitsInStock UnitsOnOrder

3.2.3. Business Rules 1. Units on backorder defined as [UnitsOnOrder UnitsInStock] > 0

1996-2011 QlikTech International

Page viii

3.3. Categories Data


3.3.1. File Information
Data Type ---------------------------------------------------------- MS Access Database ------------------------------------------------------------ QWT.mdb Table name --------------------------------------------------------- Categories Estimated Number of Records ----------------------------------- 10

3.3.2. Record Information


Field Name CategoryID CategoryName Description Data Type (Max Size) Autonumber (Long Integer) Text (25) Memo Indexed Y Y Comment Product Category ID Category name Category description

3.3.3. Business Rules 1. One-to-many relationship with [Products] table

1996-2011 QlikTech International

Page ix

3.4. Shippers Data


3.4.1. File Information
Data Type ---------------------------------------------------------- MS Access Database ------------------------------------------------------------ QWT.mdb Table name --------------------------------------------------------- Shippers Estimated Number of Records ----------------------------------- 5

3.4.2. Record Information


Field Name ShipperID CompanyName Data Type (Max Size) Autonumber (Long Integer) Text (40) Indexed Y Shipper ID Shipper name Comment

3.4.3. Business Rules 1. One-to-many relationship with [Orders] table

1996-2011 QlikTech International

Page x

3.5. Shipments Data


3.5.1. File Information
Data Type ---------------------------------------------------------- MS Access Database ------------------------------------------------------------ QWT.mdb Table name --------------------------------------------------------- Shipments Estimated Number of Records ----------------------------------- 17,000

3.5.2. Record Information


Field Name OrderID LineNo ShipperID CustomerID ProductID EmployeeID ShipmentDate Data Type (Max Size) Long Integer Integer Long Integer Long Integer Long Integer Long Integer Date Indexed Y Y Y Y Y Comment Link to [Order Details] Link to [Order Details] Link to Orders Link to Orders Link to [Order Details] Link to Orders Date for shipment to leave QWT

3.5.3. Business Rules 1. Has a one to one relationship to [Order Details]

1996-2011 QlikTech International

Page xi

3.6. Orders Data


3.6.1. File Information
Data Type ---------------------------------------------------------- MS Access Database ------------------------------------------------------------ QWT.mdb Table name --------------------------------------------------------- Orders Estimated Number of Records ----------------------------------- 7,000

3.6.2. Record Information


Field Name OrderID CustomerID EmployeeID OrderDate ShipperID Freight Data Type (Max Size) Autonumber (Long Integer) Long Integer Long Integer Medium Date Long Integer Double Fixed 2 decimal Indexed Y Y Y Y Y Order ID Link to Customers Link to Employee Date order was placed (DD-MMM-YY) Link to Shipper Freight charges associated with this order Comment

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

1996-2011 QlikTech International

Page xii

3.7. Order Details Data


3.7.1. File Information
Data Type ---------------------------------------------------------- MS Access Database ------------------------------------------------------------ QWT.mdb Table name --------------------------------------------------------- Order Details Estimated Number of Records ----------------------------------- 17,000

3.7.2. Record Information


Field Name OrderID LineNo ProductID UnitPrice Quantity Discount Data Type (Max Size) Long Integer Integer Long Integer Double Fixed 2 decimal Integer Single Percent (0 decimals) Y Link to Products Product unit price for this order Quantity of product ordered Percent discount Indexed Y Link to Orders Comment

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

1996-2011 QlikTech International

Page xiii

3.8. Divisions Data


3.8.1. File Information
Data Type ---------------------------------------------------------- MS Access Database ------------------------------------------------------------ QWT.mdb Table name --------------------------------------------------------- Products Estimated Number of Records ----------------------------------- 5

3.8.2. Record Information


Field Name DivisionID DivisionName Data Type (Max Size) Long Integer Text (15) Indexed Y DivisionID Division name Comment

3.8.3. Business Rules 1. Has a one-to-many relationship with Customers

1996-2011 QlikTech International

Page xiv

3.9. Employees Data


3.9.1. File Information
Data Type ---------------------------------------------------------- MS Excel Database ------------------------------------------------------------ EmpOff.xls Table name --------------------------------------------------------- Employee Estimated Number of Records ----------------------------------- 50

3.9.2. Record Information


Field Name EmpID Last Name First Name Title Hire Date Office Extension Reports To Year Salary Data Type (Max Size) Integer Text Text Text Date (MM/DD/YY) Integer Integer (3 digits) Integer Fixed 2 decimal Indexed Comment Employee ID Employee last name Employee first name Employee title Date of hire for employee Link to Office Telephone extension of employee Employee ID of Supervisor Annual salary of employee

3.9.3. Business Rules 1. Contains current employees only 2. [Reports To] field is subset of [EmpID] field 3. [Extension] is optional

1996-2011 QlikTech International

Page xv

3.10. Offices Data


3.10.1. File Information
Data Type ---------------------------------------------------------- MS Access Database ------------------------------------------------------------ QWT.mdb Table name --------------------------------------------------------- Office Estimated Number of Records ----------------------------------- 5

3.10.2. Record Information


Field Name Office OfficeAddress OfficePostalCode OfficeCity OfficeStateProvince OfficePhone OfficeFax OfficeCountry Data Type (Max Size) Integer Text Text Text Text Text Text Text Indexed Comment Office ID Street or PO Box mailing address of office Postal code for mailing address of office City for mailing address of office State or Province code for mailing address of office Phone number includes country code or area code Phone number includes country code or area code Country for mailing address of office

3.10.3. Business Rules 1. State / Province code is optional as required

1996-2011 QlikTech International

Page xvi

3.11. Suppliers Data


3.11.1. File Information
Data Type ---------------------------------------------------------- XML Database ------------------------------------------------------------ Suppliers.xml Table name --------------------------------------------------------- Suppliers Estimated Number of Records ----------------------------------- 30

3.11.2. Record Information


Field Name SupplierID CompanyName ContactName Address City PostalCode Country Phone Fax Data Type (Max Size) Integer Text Text Text Text Text Text Text Text Indexed Comment Supplier ID Full name of supplier Name of primary contact at supplier (First Last) Street or PO Box mailing address of supplier City for mailing address of supplier Postal code for mailing address of supplier Country for mailing address of supplier Phone number includes country code or area code Phone number includes country code or area code

3.11.3. Business Rules 1. Suppliers have single contact

1996-2011 QlikTech International

Page xvii

3.12. Budgets Data 1


3.12.1. File Information
Data Type ---------------------------------------------------------- MS Excel Database ------------------------------------------------------------ Budget.xls Table name --------------------------------------------------------- Sheet 1 Estimated Number of Records ----------------------------------- 10

3.12.2. Record Information


Field Name Office EmployeeID Year Budget rev. Data Type (Max Size) Integer Integer Date - Year (YYYY) Integer Indexed Office ID Link to Employees Budget Year Budgeted yearly revenue Comment

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.

1996-2011 QlikTech International

Page xviii

You might also like