1. OPIM 5272
Business Process Project
Team
Ruchi Karania, Nupur Gandhi, Muniba Masood
Romit Patel, Harsh Chheda, Liz Gendreau
Ruby Lu

2. Agenda
• Business Problems
• Recommendations
• Entity Relationship Design
• Database Design
• Queries and Outputs
• Conclusion

3. Business Process Issues
Big project
awareness
meeting
Unstandardized
intake from
partners
Unclear
timeframe of
returning
deliverables

4. Current Process

5. Recommendations
Cut the initial
awareness meeting
down to a few select
individuals who can
more precisely identify
the technology impacts
for a specific project
Small
awareness
project
meeting
Responsible
list
Standardized
intake forms
Enforce
timeframe
commitment
Centralized
database for
project
managers
Maintain a list of individuals
responsible for assessing
impact to each area, so the
project manager does not
have to rely on asking co-
workers who to contact and
what the estimate intake
process is
Standardize the intake
forms to request the same
data for every IT area,
rather than different forms
with different data. Store
the project intake request
data in a centralized
location
Store project estimates
and assumptions for each
IT area in a centralized
location, which can be
accessed by project
managers and used to
more accurately estimate
future projects
Create and
enforce
timeframes for
returning
estimates to
project managers

6. Process Improvement

7. Entity Relationship Design
Project
Sponsor
Enterprise
Project
Manager
Employee
Application
Owner
Project
Estimate
IT
Departments
Application /
Business Sr.
Leader
0:M
1:1
0:M 0:N
1:1 0:M
0:N
1:M
1:1
0:M
0:M 0:1 0:M 1:1 1:1 0:M
0:N0:M
1:M 0:1
1:M 1:1
1:1
1:M
1:1
0:M

8. Database Design
G6_EMPLOYEES
EMP_ID (PK)
DEPT_ID (FK)
FIRST_NAME
LAST_NAME
EMAIL
PHONE
G6_SPONSOR
SPONSOR_ID (PK)
EMP_ID (FK)
G6_PROJECT
PROJECT_ID (PK)
PROJECT_MANAGER_ID (FK)
SPONSOR_ID (FK)
START_DATE
PROJECT_TYPE
END_DATE
STATUS
G6_IT_DEPARTMENTS
DEPT_ID (PK)
DEPT_NAME
SRLEADER_ID (FK)
G6_SRLEADER
SRLEADER_ID (PK)
BUSINESS_GROUP
EMP_ID (FK)

9. Table Data

10. Database Design
G6_ENTERPRISE_PM
PROJECT_MANAGER_ID (PK)
EMP_ID (FK)
G6_APPOWNER_PROJECTESTIMATE
ESTIMATE_ID (FK)
APPOWNER_ID (FK)
G6_PROJECTESTIMATE
ESTIMATE_ID (PK)
PROJECT_ID (FK)
COST_ESTIMATE
ASSUMED_RD
ASSUMED_SD
ESTIMATE_ED
G6_APPOWNER
APPOWNER_ID (PK)
EMP_ID (FK)
DEPT_ID (FK)
G6_APPOWNER_PROJECT
PROJECT_ID (FK)
APPOWNER_ID (FK)
(PK)
(PK)
G6_SRLEADER_PROJECT
PROJECT_ID (FK)
SRLEADER_ID (FK)
(PK)

11. Table Data

12. Queries
• For open projects, which application
owners have not submitted estimates?
• For a given project, how many application
owners are impacted?
• How many days on average, maximum,
and minimum is it taking to get estimates
for a specific project?

13. Outputs
• Demonstrate in vPC

14. Queries
• Which of the IT departments is impacting
the project the most in terms of volume or
dollar amount?
• For a given business sponsor, which
senior leaders are they interacting with for
all their projects?
• How many of each project type are there,
ordered from highest to lowest?

15. Outputs
• Demonstrate in vPC

16. Queries
• For closed projects, what’s the total cost
estimate for each project?

17. Outputs
• Demonstrate in vPC

18. Conclusion
Problems Solutions