UCPath SOA Business Architecture
Information Technology Services
Page 1 of 21
01/20/2012
Table of Contents
UCPath SOA Business Architecture ........................................................................... 1
Revision History............................................................................................................ 4
1.
Introduction .......................................................................................................... 5
1.1
Overview ............................................................................................................................. 5
1.2
Total Interfaces ................................................................................................................... 5
1.2.1
Inbound Interfaces to HCM.......................................................................................... 6
1.2.2
Outbound Interfaces from HCM .................................................................................. 7
2.
Business Architecture ......................................................................................... 8
2.1
Overview ............................................................................................................................. 8
2.1.1
GL/Financial integration interfaces .............................................................................. 8
2.1.2
IDM .............................................................................................................................. 8
2.1.3
Data Warehouse interfaces ......................................................................................... 9
2.1.4
IT Services interfaces .................................................................................................. 9
2.1.5
Third-party interfaces ................................................................................................... 9
2.1.6
Campus departments interfaces ................................................................................. 9
2.2
Scope ................................................................................................................................ 10
2.3
Current State..................................................................................................................... 10
2.3.1
Campus Departments:............................................................................................... 10
2.3.2
Hospital: ..................................................................................................................... 11
2.3.3
UCOP: ....................................................................................................................... 11
2.3.4
CHR: .......................................................................................................................... 11
2.3.5
Student Records: ....................................................................................................... 11
2.3.6
UC Merced: ............................................................................................................... 11
2.3.7
California Casualty Insurance: .................................................................................. 11
2.3.8
IRS: ............................................................................................................................ 11
2.3.9
NACHA/Well Fargo Bank: ......................................................................................... 11
2.3.10
UCSF: ........................................................................................................................ 11
2.3.11
Credit Union: .............................................................................................................. 11
2.3.12
Financial System: ...................................................................................................... 11
2.3.13
ERS: .......................................................................................................................... 12
2.3.14
QDB/CDW: ................................................................................................................ 12
2.3.15
CTS:........................................................................................................................... 12
Page 2 of 21
01/20/2012
2.3.16
Bruin Card: ................................................................................................................ 12
2.3.17
FASM: ........................................................................................................................ 12
2.3.18
PAC: .......................................................................................................................... 12
2.4
Future State ...................................................................................................................... 13
2.4.1
Overview .................................................................................................................... 13
2.4.2
Inbound to HCM Overview ........................................................................................ 15
2.4.3
Outbound from HCM ................................................................................................. 16
2.5
GL/Financial integration interfaces ................................................................................... 17
2.6
IDM ................................................................................................................................... 17
2.7
Data Warehouse interfaces .............................................................................................. 17
2.8
IT Services Interfaces ....................................................................................................... 18
2.9
Campus Departments ....................................................................................................... 19
3.
References.......................................................................................................... 21
Page 3 of 21
01/20/2012
Revision History
Date
05/18/2012
Version
0.1
Author
UCPath Team
Description
Page 4 of 21
01/20/2012
1. Introduction
1.1 Overview
As part of the UCPath project, one of the key objectives is to integrate PeopleSoft HCM with
existing UCLA processes and legacy systems. This integration will allow PeopleSoft to transfer
data to and receive data from campus systems. The data transfer will be achieved in a real-time
(synchronous), near real-time (asynchronous) or in batch environment, depending on the interface
needs and the target or source system capabilities.
For the UCPath project, an interface is defined as the transfer of data between the PeopleSoft
HCM system and any external system. In this document our focus is on “Tier-1” interfaces. Tier-1
is an interface that connects with PeopleSoft HCM, while Tier-2 is a downstream interface that
does not directly interface with PeopleSoft HCM.
1.2 Total Interfaces
Interfaces
#
Total Inbound to HCM
22
Total Outbound from HCM
51
Total
73+
Note: Third Party will be developed by UCOP
Page 5 of 21
01/20/2012
1.2.1 Inbound Interfaces to HCM
An inbound is an interface that initiates from UCLA and data is transmitted to PeopleSoft
HCM. This section grouped the complexity of each interface from Easy to Very Complex,
and moreover it indicates the interface business requirements for Real Time/Near Real
Time vs. Batch.
Third Party
UCLA
IT Services
(UCOP)
Total Inbound
Campus
Depts
Easy
0
0
1
1
Moderate
2
1
4
7
Complex
5
4
0
9
Very Complex
4
1
0
5
Total
11
6
5
22
Real Time
4
1
2
7
Batch-Flat File
7
5
3
15
Page 6 of 21
01/20/2012
1.2.2 Outbound Interfaces from HCM
An outbound is an interface that initiates from PeopleSoft HCM and data is transmitted to
UCLA. This section groups the complexity of each interface from Easy to Very Complex,
and moreover it indicates the interface business requirements for Real time vs. Batch.
Third Party
UCLA
IT Services
(UCOP)
Total
Outbound
Campus Depts
Easy
2
4
7
13
Moderate
5
1
12
18
Complex
2
5
5
12
Very Complex
8
0
0
8
Total
17
10
24
51
Real Time
6
0
0
6
Batch-Flat File
11
10
24
45
Page 7 of 21
01/20/2012
2. Business Architecture
2.1 Overview
The following table provides detail of the 44 interfaces that were estimated to be processed by the
campus systems.
Campus Interfaces
(excluding base)
Real-Time/ Near
Real-Time
Batch
Total
Inbound
5
12
17
Outbound
6
21
27
11
33
44
Total
At a high level, the interfaces are broadly categorized into:

GL/Financial integration interfaces

IDM

Data Warehouse interfaces

IT Services Interfaces

Third Party Interfaces

Campus Departments
2.1.1 GL/Financial integration interfaces
Real-Time/ Near
Real-Time
Batch
Total
Inbound
1
1
2
Outbound
2
2
4
Total
3
3
6
2.1.2 IDM
Real-Time/ Near
Real-Time
Batch
Total
Inbound
2
0
2
Outbound
2
0
2
Total
4
0
4
Page 8 of 21
01/20/2012
2.1.3 Data Warehouse interfaces
Real-Time/ Near
Real-Time
Batch
Total
Inbound
0
0
0
Outbound
0
(many interface
files/model) 8
8
Total
0
8
8
2.1.4 IT Services interfaces
Real-Time/ Near
Real-Time
Batch
Total
Inbound
1
6
7
Outbound
3
9
11
Total
4
15
19
2.1.5 Third-party interfaces
Real-Time/ Near
Real-Time
Batch
Total
Inbound
2
3
5
Outbound
0
24
24
Total
2
27
29
2.1.6 Campus departments interfaces
Real-Time/ Near
Real-Time
Batch
Total
Inbound
0
5
5
Outbound
0
10
10
Total
0
15
15
Page 9 of 21
01/20/2012
2.2 Scope
Define the boundaries of the system being developed, what kind of data flows into/out of
the system. Identify the business requirements to develop a SAO based middleware
system facilitating the data exchange between HCM and various campus systems
2.3 Current State
The following diagram represents the current state of the system. It is a shared database
accessed by different external systems
Campus
Departments
Hospital
Pay Transactions
Time File
Deductions
Expense Distribution/EDB Downloading
Downloading file from previous
and current reversal files
UCOP
IVR New Hire transactions
Range Adjustment Payscale Table
University Title Code Table
Benefit/Retirement etc
Training file
1099
Pay Transactions
Leave Transactions
PAR
App/Dist
Student
Records
AIS
TimeSheet
CHR
Pay Transactions
Work Study Limits
FICA/Unit (SIS)
FICA/Unit
(SIS)
UC Merced
California
Casualty
Insurance co.
Benefit/Retirement
UI file
EDB Transactions
IRS
W2/FICA
PAC
1099
UCLA Personnel
Payroll System
1099/Rush Check
FASM
SurePay
NACHA
Graduate Students Fee Remissions
Work Study Limits
Recon
PAR
Deduction UCOP data
Employee id,phone and
Separated employee file
BruinCard
PPS,FS,WOS,
User, Dept
& DACSS file
FTE
FTE
OFC
CTS
FS table data for ERS
Budget data for Staffing
Payroll Data
QDB CDW
Well Fargo
Bank
General Ledger
Budget file
ERS
Financial
System
Credit Union
UCSF
In brief, descriptions of the above referenced interfaces are:
2.3.1 Campus Departments:
Inbound Pay transactions and time files from various departments and Outbound Expense
distributions, EDB information etc.
Page 10 of 21
01/20/2012
2.3.2 Hospital:
Inbound 1099 file, Pay transactions and time files from Hospital and Medical Center and Payroll
Audit Record (PAR) file after pay compute process.
2.3.3 UCOP:
New Hire, Employee self-update transactions, Pay scale and title code tables inbound interfaces
and Benefits, retirement and Unemployment Insurance files are few outbound interfaces.
2.3.4 CHR:
Fastrax application a dash board reports for executives has direct outbound interface from current
UCLA PPS system.
2.3.5 Student Records:
Inbound FICA exempt for student employees.
2.3.6 UC Merced:
Inbound FICA exempt for UCM student employees, pay transactions, work study limits etc. from
UCM systems.
2.3.7 California Casualty Insurance:
Inbound EDB update transactions from California Casualty Insurance Company.
2.3.8 IRS:
W2/1042’s and FICA reporting to IRS as per federal law.
2.3.9 NACHA/Well Fargo Bank:
Pay files to get the employees pay into banks.
2.3.10 UCSF:
HR related data for UCOP employees sent to UCSF as UCSF supports UCOP HR system.
2.3.11 Credit Union:
Deductions outbound file to University Credit Union.
2.3.12 Financial System:
Outbound GL interface after every pay compute process and Budget file is interfaces with
Financial Systems. Inbound Dept data, Chart Fields for positions and budget data for staffing
interfaces from Financial Systems.
Page 11 of 21
01/20/2012
2.3.13 ERS:
Effort Reporting System depends on the PPS data for creating the Effort Reports for federal funds
which require certification.
2.3.14 QDB/CDW:
Payroll data gets refreshed into Campus Data Warehouse to support various tier-2 applications
around the campus and reporting purposes.
2.3.15 CTS:
Former CTS (IT Services) requires the Full Time Employees information for telephone recharge
process to departments.
2.3.16 Bruin Card:
EDB information is sent to Bruin office daily to support the bruin card system.
2.3.17 FASM:
Financial Aid System inbounds Graduate Fee Remission and Work study limits information into
current PSS system. Payroll Audit Record (PAR) data related to student employees is outbound to
FA office.
2.3.18 PAC:
Rush checks transactions and bank information table are outbound for off cycle pay checks for
employees and 1099 information file is interfaced to reconcile the pay related information of
employees.
Page 12 of 21
01/20/2012
2.4 Future State
2.4.1 Overview
UCLA will implement a centralized model and build a service bus that provides various
services to the interfaces being developed.
UCLA Systems
UCPath SOA Business Architecture
GL/Financial
Integration
IT Services
(Enterprise Service Bus)
IT Services
Interfaces
Oracle on Demand
Transformation
Routing
Campus Dept.
Interfaces
Monitoring
Queuing and
staging
Security
Data
Enrichment
PeopleSoft HCM
Service
Orchestration
IDM
UCLA
DW
ODS
IT Services ESB Requirements
The middleware acts as a gateway between HCM (Oracle Service Bus) and various campus
systems. It provides the following services depending on the business requirements of the
interface
1. Routing
Page 13 of 21
01/20/2012
a. A routing service is the key component provided by service bus to move a
message from its entry point to its exit point.
2. Data transformation
a. Change fixed length file into a pipe delimited file
b. Change a pipe delimited file into a fixed length file
c.
Transform XML to a fixed length or pipe delimited format
d. Transform a flat file format to XML
e. Translations based on table values or defaults
f.
Truncate data elements
3. Data enrichment
a. Append Employee Id for inbound and/or outbound interfaces
b. Append UID for outbound interfaces
c.
Adding additional columns or removing columns from a file
d. Append data elements
4. Messaging
a. To support more reliable and scalable messaging service bus can be configured
with JMS endpoints
5. Security
a. PII
b. HIPPA
c.
Web services security (WS-Security) that identifies the sender and authenticates
its identity to the web service provider will be implemented on the service bus for
inbound and outbound integrations with HCM
d. The communication between HCM and service bus will be encrypted
6. Management and Monitoring
a. A dashboard displaying the details of the interface, when it is processed and its
status (success or failure) etc.
Page 14 of 21
01/20/2012
2.4.2 Inbound to HCM Overview
There are three ways transmitting data to HCM.
1. Real time - through Web Services.
2. Near real time – Event driven through Message Broker
3. Batch flat files - sFTP
Inbound to HCM
UCLA Dept.
Interface
UCLA on Demand
Managed File Transfer
and Queue
Oracle on Demand
Batch pushing
Pushing
WS
Message
PeopleSoft HCM
(Oracle Service Bus)
Polling
Listener
Event driven
Routing
Security
Transformation
Monitoring
Data Enrichment
Service
Orchestration
Queuing and
staging
Web Service Call
IT Services
( Service Bus)
IDM
UCLA
Page 15 of 21
01/20/2012
2.4.3 Outbound from HCM
There are three ways transmitting data from HCM.
1. Real time - through Web Services.
2. Near real time – Event driven through Message Broker
3. Batch flat files - sFTP
Outbound from HCM
UCLA Dept.
Interface
UCLA on Demand
Managed File Transfer
and Queue
Polling
Oracle on Demand
Pushing
WS
Polling
Message
Pushing
Routing
Transformation
Monitoring
PeopleSoft HCM
(Oracle Service Bus)
Security
Event driven
Data Enrichment
Service
Orchestration
Queuing and
staging
Web Service Call
IDM
UCLA
Page 16 of 21
01/20/2012
2.5 GL/Financial integration interfaces
Real-Time/
Near RealTime
Batch
Inbound
Account/Fund
Profile (Chart of
Accounts)
X
X
Blood Donation
X
X
FS Payroll
Expense Transfer
X
Outbound
FDD
Reference
X
Committed
Salaries data from
GL
X
X
Costing – Transfer
of funds file
X
X
Par Earnings File
X
X
Encumbrances
X
X
I-308
2.6 IDM
RealTime/
Near RealTime
Account
Provisioning
System
X
Security and Role
Definition
X
PCD (Payroll
Control Data)
database ARSM
related tables
X
Employee Changes
X
Batch
Inbound
Outbound
FDD
Reference
X
X
X
2.7 Data Warehouse interfaces
Page 17 of 21
01/20/2012
HCM data gets disseminated grouped at high level with eight models. Each model will constitute
of numerous tables which will be one flat file for each table coming down in Data Dissemination.
Interface Name
Real-Time/
Near RealTime
Batch
Inbound
Outbound
Person Model
X
X
Job Group Model
X
X
Benefits Group
Model
X
X
Payroll Group
Model
X
X
Leave Group
Model
X
X
Look Up Group
Model
X
X
ID’s Group Model
X
X
Other
X
X
FDD
Reference
2.8 IT Services Interfaces
Interface Name
Real-Time/
Near RealTime
Batch
Inbound
Outbound
FDD
Reference
Managing
Investigator
X
X
I-163
Checks payroll data
(Emp Status, Fed
Tax Excempt,
Employment Appt
for certain title
codes) in real time
from BAR system
X
X
I-265
SIS – Financial Aid
Application
X
Bank Info Query
X
X
X
Graduate Student
Extract
X
ERS – Effort
Reporting
X
Page 18 of 21
I-266
X
X
I-302
I-116
X
I-129
01/20/2012
Staffing Master File
X
FICA Status
X
Pay Calendar to
Viper
X
X
I-157
Work Study
Students PAR file
X
X
I-158
Work Study
interface from
Financial Aid system
X
X
I-159
Graduate Remission
Fee file from
Financial Aid
system.
X
X
I-160
Garnishment/EFT
X
X
X
Creates ASUCLA
PAR file to CTS
interface TIF file
Imputed Income
I-154
I-156
X
I-185
X
I-237
X
I-301
Employee Bank Info
Batch
X
X
I-303
Costing file for
budget system
(Outbound
X
X
I-307
Fastrax
X
X
I-352
Outbound
FDD
Reference
2.9 Campus Departments
Real-Time/
Near RealTime
Batch
Inbound
All Time Entry
X
X
I-181
Balances and
Adjustments
X
X
I-295
Takes Time Entry
X
X
I-313
Employee
Department Info
(Outbound)
X
X
I-300
Balances
X
X
I-298
Page 19 of 21
01/20/2012
Kronos
X
X
I-299
Time Interface
X
X
I-168
Tax Reporting –
1042 S
X
X
I-151
Department Code
Lookup LMS
X
X
I-152
Cal Rec Payroll
Deduction
Transactions
X
X
I-171
Parking
Deduction Update
X
X
I-176
Extract for
Institutional
Planning
X
X
I-190
Roster Info to
BOL
X
X
I-231
BruinCard
Deduction
X
X
I-232
Employee Job
Organization
Detail
X
X
I-357
Page 20 of 21
01/20/2012
3. References
Page 21 of 21
01/20/2012