| Excerpt |
|---|
Workday illustrated with all other systems at a very high level. Not illustrated is whether or not an Integration Broker would be in the middle of all a2a interfaces. |
with a focus on IdMgmt related systems and point-to-point integrations. Picture changes with PS people data hub. |
Group | # | Name Content Description | Timing | Use of data or Business Process Supported | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
A | 1 | Workday /PS | Batch and/or real-time | To pass/maintain basic employee bio/demo data and create emplid. | ||||||||||
| 2 | PeopleSoft | Batch and/or real-time | To pass employee emplid. | Employee Biographical Data, Employee status and affiliation, transaction data to support PS Campus Solutions | Realtime for new employees, updates and deletes | new Employee creation with duplicate avoidance |
| 2 | PS/Workday | Employee ID creation | Realtime for new employees, updates and deletes | new Employee creation with duplicate avoidance | |
| 3 | IdCard | Student and Employee ID data | Daily Batch and Real-time components | ID Card generation | Active Directory | Batch and/or real-time | To support the authentication function. Undergraduate students, graduate/professional students, and alumni/trustee data is sent to Active Directory |
| 4 | Library | Student and Employee data | Daily Batch | Library patron privileges. |
| 5 4 | ELM | Campus Community data for all students and employees | Daily Batch | To provide courses to Human Resources, EHS, Cash Management, KFS, Gannett (and others in future) a person's bio/demo data must exist in ELM. | |||||||||
| 6 | IdMgmt | Just Student ID data (Employee data has to be taken out of the existing feed) | Daily Batch | To keep the Directory current, Reference Groups providing access, WhoIam and NETID management tools operating. | |||||||||
SunOne Directory | Batch | To support the authorization function. Authorization function for PeopleSoft. When a user authenticates to PeopleSoft a lookup is performed in the SunOne directory to retrieve the emplid. This emplid is then used to map the session to the data the user is permitted to access according to PS internal tables. Student must be able to authenticate to PeopleSoft. | ||||||||||||
| 5/6 | NetId Admin | Batch and/or real-time | To support the creation/maintenance of the Network ID (or NetID). Used along with a password, to obtain access to online services, such as email and administrative systems. The custom built NetId application creates and distributes netid information |
| 7 | EMN | Just Student Emergency data (Employee data has to be taken out of the existing feed) | Daily Batch | To feed the 3rd party EMN system. | ||||
B | 1 | SES | Student Employment/Work Study | Daily Batch | To support Financial Aid's work study tracking and award processing. Send student data and eligibility information to Workday from Student Records and Financial Aid (I9s). | |||||||||
| 2 | Workday/Kronos | Hourly employees and their supervisors | Daily Batch | To support pay for hourly staff. | |||||||||
| 3 | Kronos/Workday | Time collection detail for hourly employees | Daily Batch | To support pay for hourly staff. | |||||||||
| 4 | KFS/Workday | Account, Org and department data | Daily Batch and Real-time | Support for financial processes involving labor data. Requires the correct account, org and department | |||||||||
| 5 | Workday/KFS | Liability, position, salary earnings detail, gross pay encumbrance data | Daily Batch | To support accounting of labor related transactions. | |||||||||
| 6 | 3rd Parties | Banks and benefits providers | Unknown | TBD | |||||||||
| 7 | Warehouses | HR and Payroll detail | Daily Batch | All analytical and reporting needs for HR/Payroll required for the University's analysis and operational reporting not provided by Workday, particularly for historical needs starting with the first use of Workday. Conversion of old HR/Payroll data to a new Workday Era warehouse is yet to be defined in scope. | |||||||||
| 8 | Transportation | Names of employees, permit withholdings for Payroll | Daily Batch | Transportation tickets, permit creation and change processes require employee data. This interface is expected to be a Transportation office and HR/Workday responsibility and is not included in the CIT estimates. CIT is not expecting to own or steward this interface. | |||||||||
| 9 | ELM | Employee job data (workforce and position) | Daily Batch | To provide courses to Human Resources, EHS, Cash Management, KFS, Gannett (and others in future) a person's job/position data must exist in ELM. | |||||||||
| 10 | EMN | Employee ID data | Daily Batch | To feed the 3rd party Emergency Mass Notification system . | |||||||||
| 11 | IdMgmt | Emergency phone number, text enabled or not flag, and emergency contact table. | Daily Batch | To keep the Directory current, Reference Groups providing access, WhoIam and NETID management tools operating. | |||||||||
| 12 | Grad Earnings | Emergency phone number, text enabled or not flag, and emergency contact table. | Daily Batch | To provide the Grad School with a complete picture of a student's financial picture. Provides a summarized view of Students Charges, Financial Aid, Academic data and Payroll Earnings data. | |||||||||
| 13 | SES | Student Employment/Work Study | Daily Batch | To support Financial Aid's work study tracking and award processing. Send gross earning for student employees into PeopleSoft Financial Aid system for tracking against overall award amounts. | |||||||||
C | 1 | Other Systems | Systems downstream from the HR/Payroll warehouse will be indirectly affected and are not included in scope. | periodic batch | One example is Digital Measure's Activity Insight, which extracts some HR data for the Academic Reporting processes the software support |
| 2 | IdMgmt | Systems downstream of the Directory that use HR attributes will be affected and are not included in the scope. | batch or real time | One example is Vivo, which pulls basic HR data from the directory. If the attributes change or are removed these systems will be affected. ||||
Active Directory | Batch and/or real-time | To support the authentication function. Employee data is sent to Active Directory. Additionally, the department structure defined currently defined within PeopleSoft must be replaced by the organizational model defined by Workday. | ||||||||||||
| 2 | SunOne Directory | Batch | To support the authorization function. When a user authenticates to PeopleSoft a lookup is performed in the SunOne directory to retrieve the emplid. This emplid is then used to map the session to the data the user is permitted to access according to PS internal tables. Student must be able to authenticate to PeopleSoft. | ||||||||||
| 3/4 | NetId Admin | Batch and/or real-time | To support the creation/maintenance of the Network ID (or NetID). Used along with a password, to obtain access to online services, such as email and administrative systems. The custom-built NetId application creates and distributes netid information. | ||||||||||
C | 1 | Active Directory | Batch and/or real-time | Data is propagated to downstream applications. |
| |||||||||
| 2 | NetId Admin | Batch and/or real-time | Data is propagated to downstream applications. |
|
What is Active Directory used for?
IdMgmt system for the entire campus. Authenticates various campus groups giving them appropriate access to campus services and resources.
Active Directory is a non-public directory supporting enterprise applications within the institution. It is very Microsoft specific and is required for some MS applications such as Exchange. It also serves a function referred to as a network operations system (NOS) function. It is designed to manage network objects such as desktops, printers, servers, files.
What is SunOne Directory used for?
SunOne is the public facing directory (i.e. anonymous attributes are available to any individual and application). It is the repository that serves as the backend for the University white pages (People Search).
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|