Workday Integration Architecture
Release 1
Goran Mladenovski
Integration Requirements
• Comply with TietoEVRY CIO Integration strategy
• Legacy Aditro HRM system in xEVRY should be shoutdown and replace with the TietoEVRY target
HCM Solution –Workday
HIP
• All xEVRY consumers of Aditro HRM data must continue to work uninterrupted, same data feed
provided today need to be provided after the Workday Migration
Allow on-premise
• Both new(TietoEVRY) and old(xEVRY) CostCenter codes needs to be supported with the solution for
solutions to seamlessly
WD Release
1
and securely
integrate
with cloud-based
• Secondary applications
Company Position need to be supported for the IFS usage
• xTieto & xEVRY Payroll systems will not be merged in WD Release 1, so old solutions need to be
supported
• MGMT, CORP or evry.onmicrosoft.com system access should be possible to provide even after WD
Relase 1
AS-IS HCM Architecture
TO-BE HCM Architecture
(Transition)
WD Detailed Integration Architecture
Additional WD
fields
• FTE Billable/Not billable to be
moved to WD with Release2.
Release 1 this field will be used
only for xEVRY purposes
• Additional set of 7 fields
added in WD to support current
feed from Legacy HRM system
Worker information + CC(INT101)
Workday
File based integration
INTEGRATOR
HIP
•
Allow on-premise
solutions to seamlessly
TERP
and securely integrate
with cloud-based
Worker dataapplications
= Employee + Externals from both xCompanies
•
Existing Integration to TERP to include all Workers from Workday
•
Company & Location data is taken manually from TERP where the data for both xTieto and xEVRY
is existing
•
WD-Integrator integration will provide all Worker data + CC(based on old codes/structure)
•
Data from Integrator will be provided only to approved solutions
Supervisory Organization (INT102)
Workday
File based integration
INTEGRATOR
HIP
Allow on-premise
TERP
solutions to seamlessly
and securely integrate
with cloud-based
applications
• Supervisory Org will be mastered in WD and feeded to
TERP and INTEGRATOR for further distribution
• Supervisory Org is matching existing Operational Org
feed from Legacy HRM system
Payroll information xEVRY (INT111-NO, 112-SE)
Workday
File based integration
Aditro SE
INTEGRATOR
HIP
Aditro NO
PayrollAllow
by on-premise
solutions to seamlessly
Country
and securely integrate
with cloud-based
applications
• Several Payrolls per country per xCompanies will continue to co-exists in Release 1
• xTieto Payroll feed will remain unchange
• xEVRY Payroll feed will be generated of combination of payroll data and worker info within Integrator
before sending to corresponding country payroll system
INT103-Email,104 Username,UPN 105
6
5
1
Workday
8
HIP
2
3
1.
INTEGRATOR
7
CORP AD
New worker creation is initiated in WD
2. TERP MDM team creates the TERP user
Allow on-premise
TERP
3. Username and email are push back to WD
solutions to seamlessly
and securely integrate
4. AD account is created for the new User
with cloud-based
5. If worker is linked to xEVRY company he will get CORP AD (limited with no email and office) so
applications1.
data is send to INTEGRATOR
4
Tieto AD
6.
INTEGRATOR pushes the data for automatic user creation in CORP AD
7.
Updated Email(to support old xEVRY users),Username and UPN data will be send back to
INTEGRATOR
8.
INTEGRATOR forwards the data to WD where the corresponding fields are updated
Master Data Flow
HIP
Allow on-premise
solutions to seamlessly
and securely integrate
with cloud-based
applications
Secondary Company Position
User Portal for Secondary
Company Position
INTEGRATOR
IFS
HIP
•
•
Allow on-premise
solutions
to seamlessly
A new
user portal
to be created on top on the Integrator to be used as input form for secondary position
and securely integrate
with cloud-based
Secondary
position data is feed to IFS as in old solution been feed from Legacy HRM system
applications
• Secondary position is not used for people linked to xTieto companies