Human Resource

Management

Sumit Singh Sumit Singh

Rohit Rana Rohit Rana

Hardeep Kumar Hardeep Kumar

Dhawal Tandel Dhawal Tandel

Mayank Singh Mayank Singh

Saurabh Patil Saurabh Patil

Abhay Singh Abhay Singh

Anwaar Khan Anwaar Khan
What is Data Warehouse???

According to W.H. Inmon “A data
warehouse is:

Subject Oriented

Integrated

Time-variant

Non volatile storage
collection of data in support of
management decision making
process.
Database Lifecycle

Analyze the company situation:
– Analysis means to break up any whole into
parts so as to find out their nature, functions
and so on.

These issues must be resolved:

What is the organization general operating
environment and what is its mission within that
environment.
– What is the organization structure?

Knowing who controls what and who reports
to whom is quite useful when you are trying
to define required information.
Human Resource Management
Database….
Hiring
Recruiting
Education
& Training
Retrention
Benefit
Administration
Potential
Employees
Employees
Retired
Employees
Data Management
Accounting
information
system
Human
resources
research
system
Manufacturing
intelligence
subsystem
Work
force
planning
subsyste
Work force
management
subsystem
Benefits
subsyste
m
User
s
Data
Information
Environmental
reporting
subsystem
HRMS
Databas
e
Recruiting
subsystem
Compensati
on
Subsystem
Define problem and
constraints

Some of the questions to be
answered are:

Has some kind of system in place
already?

How does the existing system function?

What input does the system require?

What documents does the system
generate?

How is the system output used?

by whom?
Data warehouse Requirements
for HRMS

The highest priority business
requirement is to

track and analyze the employee
transactions events accurately

It should provide the answer to every
possible employee profile inquiry.
What are the Objectives???

The initial objective might be to create an
efficient inventory query and management
system.

The database system must be designed to
help solve at least the major problems
identified during the problem discovery
process.

The database designer must begin to
address the following questions:

Will the system interface with other existing
or future systems in the company?

Will the system share the data with the
Define scope and
boundaries

The designer must recognize the
existence of two sets of limits:

Scope

Boundaries

Scope defines the extent of the design
according to the operational
requirements.

The proposed system is also subject to
Boundaries. Which are external to the
system. Boundaries are also imposed
by existing hardware and software.
Dimension Analysis…

Dimensions are qualifying
characteristics that provide
additional perspectives to a given
fact.

For eg:- HRMS has employee,
transaction, job, salary, department etc
dimensions..

Such dimensions are normally stored
in Dimension Tables.
Example of Dimension
Table…
Employee Dimension
Emp_id
Dept_id
First_name
Last_name
Email
Ph_no
Hire_date
Job_id
Salary
Employee Dimension
table…

Each employee has a detailed HR
profile with some attributes including
date of hire, job grade, salary, review
dates, review outcomes, insurance plan
and may others.

Employees are constantly being hired,
transferred and promoted as well as
adjusting their profiles in a variety of
ways. The measurements associated
with the employee transaction are the
changes made to the employee profile
such as a new address or job grade
What are the Facts???

Facts are numeric measurements
(values) that represent specific
business aspect or activity.

Facts commonly used in business
data analysis are units, cost, prices
and revenues.

Facts are normally stored in fact
table

Fact tables are updated periodically
Example of fact table..
Fact Table
Loc_id
Dept_id
Emp_id
Job_id

Star schema
– The star schema is a data modeling technique
use to map multidimensional decision support
data into a relational database.

Reason for developing star schema is that
existing relational modeling techniques, ER
and normalization did not yield a database
structure, that served the advanced data
analysis requirement .

The basis star schema has four components:
• Facts
• Dimensions
• Attributes
• Attribute hierarchies
Data warehouse Schema…
Star Schema for HRMS…
Location
Dimension
Loc_id
Street_addr
Post_code
City
Salary Dimension
Date
Emp_id
Time_in
Time_out
Department
Dimensions
Loc_id
Dept_id
Dept_name
Mgr_id
Performance
Dimension
Emp_id
Prev_yr_ach
Ratin_pm
Ratin_tl
Self_ratin
Final_grd
Employee
Dimension
Emp_id
Dept_id
First_name
Last_name
Email
Ph_no
Hire_date
Job_id
Salary
Job Dimension
Job_id
job_title
Salary
Fact Table
Loc_id
Dept_id
Emp_id
Job_id
Emp_count
Transfer_count
Employee
Transaction Type
Emp_tr_typ_key
Tran_desc
Tr_date
Tr_time
Employee Fact Table
Emp_id
Emp_tr_typ_key(FK)
Emp_type
Emp_name
Emp_addr
Attendance
Dimension
Date
Emp_id
Time_in
Time_out
Schema Contd……
Fact Constellation…
Location Dimension
Loc_id
Street_addr
Post_code
City
Cont_id
Salary Dimension
Emp_id
Date
Fact Table
Emp_tr_typ_key
Loc_id
Dept_id
Emp_id
Job_id
Department Dimensions
Loc_id
Dept_id
Dept_name
Mgr_id
Performance Dimension
Emp_id
Prev_yr_ach
Ratin_pm
Ratin_tl
Self_ratin
Final_grd
Attendance
Date
Emp_id
Time_in
Time_out
Job Dimension
Job_id
job_title
Salary
Emp Dimension Fact
Emp_id
Emp_tr_typ_key
Employee transaction Type
Emp_tr_typ_key
Tran_desc
Tr_date
Tr_time
Snow Flake Schema…
Location
Dim
Loc_id
Street_addr
Post_code
Citykey
Salary Dim
Date
Emp_id
Time_in
Time_out
Department
Dim
Loc_id
Dept_id
Dept_name
Mgr_id
Performance
Dim
Emp_id
Prev_yr_ach
Ratin_pm
Ratin_tl
Self_ratin
Final_grd
Employee
Dim
Emp_id
Emp_type
Dept_id
First_name
Last_name
Email
Ph_no
Hire_date
Job_id
Salary
Job
Dimension
Job_id
job_title
Salary
Fact Table
Loc_id
Dept_id
Emp_id
Job_id
Emp_count
Transfer_count
City
Dimension
City
Citykey
Province
Potential
emp dim
Emp_id
hire_date
Appl_no
Retired
Emp Dim
Emp_id
retr_date
Pension
PC
Data Cube
Date
T
r
a
n
s
a
c
t
i
o
n

T
y
p
e
D
e
p
a
r
t
m
e
n
t
Retrented
Hired
Promoted
1Qtr
2Qtr
3Qtr
4Qtr
Manufacturin
g
Finance
Sales
Slice and Dice
T
r
a
n
s
a
c
t
i
o
n

T
y
p
e
D
e
p
a
r
t
m
e
n
t
Retrented
Hired
Promoted
Manufacturin
g
Finance
Sales
PC
Date
1Qtr
2Qtr
3Qtr
4Qtr
Employee
Transaction in
Manufacturing
Employee Promoted
Employee
Transaction in 3rd Qtr
Employee Transcation
in Manufacturing(3
rd
Qtr)
Employees promoted
in manufacturing(3
rd

Qtr )
Roll up (drill-up) (dimension
reduction example)
Date
su
m
1Qtr
2Qtr
3Qtr
4Qtr
Group by date, department
- reduced product
dimension
Group by department
- reduced date
dimension
T
r
a
n
s
a
c
t
i
o
n

T
y
p
e
D
e
p
a
r
t
m
e
n
t
Retrented
Hired
Promoted
Manufacturin
g
Finance
Sales
Roll up (drill-up)
Group by transaction, department
Date
su
m
su
m
1Qtr
2Qtr
3Qtr
4Qtr
sum
G
r
o
u
p

b
y

d
a
t
e
,

d
e
p
a
r
t
m
e
n
t
Group by
transaction
Group by date
ALL
Group by
department
T
r
a
n
s
a
c
t
i
o
n

T
y
p
e
D
e
p
a
r
t
m
e
n
t
Retrented
Hired
Promoted
Manufacturin
g
Finance
Sales
Drill down (roll-down)
Date
1Qtr
2Qtr
3Qtr
4Qtr
G
r
o
u
p

b
y

d
a
t
e
,

d
e
p
a
r
t
m
e
n
t
ALL
Group by
department
T
r
a
n
s
a
c
t
i
o
n

T
y
p
e
D
e
p
a
r
t
m
e
n
t
Retrented
Hired
Promoted
Manufacturin
g
Finance
Sales
Advantages & Disadvantage

Advantages of Using the Snowflake
Schema

Tnr ovouoioxr o)nrµo:

Iv ooµr )ooro µow iµrpoGr rrpoopµov)r
þr)ouor oµoiirp toþiro opr ¢oivrô, uni)n io
rooirp to µoivtoiv,

It oioo iv)prooro oirciþiiitw.

Aioo ôGovto yro oo Yoivy tnr
Lvou oioxr L) nrµo

Tnr ovouoioxr o)nrµo:

iv)prooro tnr vuµþrp oo toþiro ov rvôuorp
Conclusion

Thus we conclude that “the schema
that is more appropriate for HRMS
data warehouse is the snow flake
schema”.
References…
T
H
A
N
K

Y
O
U

T
H
A
N
K

Y
O
U

F
O
R

Y
O
U
R

F
O
R

Y
O
U
R

V
A
L
U
A
B
L
E

V
A
L
U
A
B
L
E

T
I
M
E

T
O

H
E
A
R

T
I
M
E

T
O

H
E
A
R

U
S

.
.
U
S

.
.

Sign up to vote on this title
UsefulNot useful