December 2020 

Data Warehousing and Reporting System 

Specification 
GOALS 
1. Developing a data warehouse to store historical sales data 
2. Developing a multi access administration panel for data upload and configuration 
management 
3. Developing a pre-defined set of graphical reports to assist in operational and strategic 
business analysis 

REQUIREMENT AND FEATURE ANALYSIS 

Nature of Data 
The sales data dump has the following properties: 

1. The data set is a ​time series data​ (where the smallest unit of time is ​day​) 
2. A ​customer​, defined in data set, is a pharmacy/drug store who is the potential customers 
of Pharmaceutical companies 
3. An ​item/brand​ means a specific drug/medicine 
4. Each row indicates the sell of an item to a specific customer on a given day in a particular 
market 
5. Each row of sales data also includes the unit selling price, number of units sold and total 
sales amount 
6. The data set can optionally include bonus quantity and return value 

Account Management Features 

1. Login with email and password (secure and hashed, system would not store passwords) 
2. Password reset with email 
3. Send invitation with email to new user 
4. Access level management (admin and regular user) 
5. Enable/disable user 

1 
  

Data Upload Features 

1. The system will expect xlsx or csv files as inputs 
2. The uploaded data files should contain homogeneous data and without any unexpected 
empty row or column 
3. After uploading a data file, system will auto map the columns if headers are properly 
formatted, or will prompt user to map columns with expected fields 
4. After reviewing and confirmation, the data files will be uploaded and the rows will be 
indexed for analysis 

Data Management Features 

1. System will provide a list of all uploaded files and a mean to enable disable their data in 
analysis (in case of duplication or wrong upload) 
2. System will provide a panel for reviewing, searching and filtering all historical records 
together 
3. Target Input: System admin will be able to set monthly targets per market either in a panel 
or by uploading a xlsx/csv file 

Reports and Dashboards 

A ​Report​ is the answer to a specific question such as what is the average monthly sales or what 
is the contribution of different items in total sale. The output of a report can be a numeric value or 
a table or a chart based visualization like line, bar or pie chart. 

A ​Dashboard​ is a collection of ​Reports ​grouped together in the same question. 

A Report or Dashboard can optionally have ​filters​ such as ​a date range picker​ or ​item selector 
that’ll update the reporting visualization as per users input. 

The system may include the following reports: 

a. Overall sales (units sold and sales value) 

b. Sales trend (day/monthly/quarterly) with comparative growth 
c. Market wise sales (value, trend and heatmap) 
d. Item wise sales (value, trend and heatmap) 
e. Top chemists (filtered by item or market) 
f. Market wise Item penetration 

On top of that, there could be three dashboards focusing on 

a. Items/Brands dashboard 

2 
  

i. Filters 
1. Brand selection 
2. Date Range 
ii. Reports in Brands Dashboard 
1. Average Selling Price 
2. Units Sold 
3. Total Sales 
4. Sales Trend 
5. Top customers and markets for selected brand 
b. Market Dashboard 
i. Filters 
1. Market selection 
2. Date Range 
ii. Reports in Market Dashboard 
1. Units Sold 
2. Total Sales 
3. Sales Trend 
4. Top customers and brands for selected brand 
c. Customer/Chemist Dashboard 
i. Filters 
1. Chemist selection 
2. Date Range 
ii. Reports in Customer Dashboard 
1. Units Sold 
2. Total Sales 
3. Products Sales Trend 
4. Top brands 

   

3 
  

SAMPLE DASHBOARD AND VISUALIZATIONS 

Sales Dashboard 

Growth Chart

4 
  

TECH SPECS 
- The system need to be cloud based and all data will be stored in a remote secured 
database with backup 
- The web application will have to be accessed by using a modern web browser (Google 
Chrome/Firefox/Microsoft Edge/Safari) using a secure connection (SSL enabled) 
- The system will be hosted in a modern data center like Amazon AWS or DigitalOcean 
- A relational database (i.e. MySQL/MariaDB) needs to be used for data persistence, object 
store/nosql databases can’t be used 
- The system should be developed using common and popular web frameworks (i.e. 
PHP/Laravel, Node/ExpressJS, Python/Django along with ReactJS/VueJS and Bootstrap 
etc) 

Backup 
The database needs to be backed up periodically (i.e. daily) to prevent any accidental data loss. 

5