Professional Documents
Culture Documents
REPORTS
It is important to provide relevant reports to both
Shree and Shivani which contain information which
will enable them to take efficient decisions.
Shree is the operations head of the company so the
bottleneck activity for each process must be known to
him and moreover, the activity for each process with
the most fault rate must also be described.
Shivani is the marketing executive so, Customer
relationship data such as order frequency for a
company, order type etc must be known to her.
A. REPORTS FOR SHREE
A report given to Shree must have the following:
Bottleneck activity name for each process, say Hem
Bottom for stitching, assuming equal number of
workers for each process.
Bottleneck activity time for each process, Hem
bottom for stitching takes 0.73 minutes per item.
Activity having the highest fault rate for a
particular process so that faults can be reduced
and optimal quality ensured
Technology to be used: EDW with multidimensional
data analysis
REPORTS FOR SHIVANI
A report given to Shivani must have the following:
Order frequency for different key customers
Order sizes for different key customers
Interesting patterns or relationships in purchase
behavior or purchase cycle for the key accounts for
extension of customized offers
Technology to be used: Analytical and Operational
CRM solutions.
B. REPORT FORMAT FOR SHREE
Activity
Bottleneck Bottleneck
Process having highest
Activity Activity time
fault rate
Fabric Laying
Cutting
Stitching
Production
Folding
Packaging
QUESTION 2
PART A
Tables and ER diagram
TABLES
1. Branch
Attributes: branch_id (primary key), branch_name, city, street
(branch_name can also be used as primary key if we are sure that all branch names
are unique)
2. Customer
Attributes: ssn (primary key), name, address, phone number, age
3. Account
Attributes: account_id (primary key), account_type, startdate, pin,
overdraft_amount (NULL if account_type=savings account), interest_rate (NULL if
account_type = interest_rate)
4. Account-Branch-Map
Attributes: account_id (foreign key from account), branch_id (foreign key from
branch)
TABLES (contd.)
5. Customer-Account-Map
Attributes: ssn (foreign key from Customer), account_id (foreign key from
Account)
6. Transaction:
Attributes: Transaction_reference_no (primary_key), account_id (foreign
key from Account), transaction_type, date, amount
7. Transaction-Account-Map
Attributes: transaction_reference_no (foreign key from Transaction),
account_id (foreign key from Account)
8. Loan:
Attributes: loan_no (primary key), loan_type, duration, interest_rate,
balance.
TABLES (contd.)
9. Customer-Loan-Map
Attributes: ssn1 (foreign key from Customer), ssn2 (foreign key from
Customer), loan_no (foreign key from Loan)
In the case of co-signers, ssn1 and ssn2 are different, else they are same (or
ssn2 is null).
10. Loan-Branch-Map
Attributes: loan_no (foreign key from Loan), branch_id (foreign key from
Branch)
11. Payment
Attributes: payment_no, loan_no (foreign key from Loan), date, amount
payment_no and loan_no together make up the primary key.
ER DIAGRAM
PART B
Account numbers common across different branches
RECOMMENDATION
In the Account Table, account_id can no longer be used as the primary key.