Groups

Interface Development

Lead: Anantha Kadur

UCDHS Contact: Mangesh Kamble

  • UCPath PMO is responsible for design and development of all interfaces outbound from UCPath to provide the data to the locations.
  • The UCPath PMO is also responsible for the design and development of the all interfaces inbound that provide data from each location to UCPath.
  • Locations are responsible for development of its corresponding load of that outbound interface into the appropriate local system using the design documents provided by the UCPath PMO for each applicable interface.
  • To meet Inbound interface requirements, locations are responsible for development of its corresponding extract of data from the appropriate local system, using the design documents provided by the UCPath PMO for each applicable inbound interface to format the data.

Secondary Systems (Tier-N

Lead: Linda Durst

UCDHS: Mangesh Kamble

  • UCPath outbound Tier-1 interface data can be utilized to satisfy a location data needs beyond the Tier-1 purpose once it leaves UCPath. These subsequent data transmittals are known as Tier-n interfaces. The local project team should determine if/how to leverage outbound Tier-1 interfaces for its Tier-n systems.
  • The work effort to identify, assess, modify and test Tier n systems and interfaces is significant.
  • The UCPath PMO is limited in the support it can provide for Tier n systems because they are local systems.

DDODS (Data Dissemination Operational Data Store)

Lead: Linda Durst

UCDHS: Mangesh Kamble

  • The Data Dissemination Operational Data Store (DDODS) is a UCPath product. It is designed to cull information from a complex Human Capital Management & Payroll software package containing 20,000 tables, determine change data, and relay pertinent and concise information to multiple UC institutions.
  • The primary objective of the DDODS is to provide and data for the Data Warehousing processing needs of each UC location (campuses, medical centers).
  • All data is transmitted in one file through the DDODS to the local ODS, and loaded in one process.

DATA WAREHOUSE (ODS/Local Warehouse)

Lead: Linda Durst

UCDHS: Mangesh Kamble

  • All data is transmitted in one file through the DDODS to the local ODS, and loaded in one process. All error and recovery issues are resolved as part of this transmission stream.
  • Data can be extracted directly from the ODS to the Tier-1 system upon demand by the location.
  • Locations could take a “service bus” approach and build extractions that will provide any code or reformatting of data to the needs of the location Tier-1 application with one code source. This approach could significantly lower long term maintenance costs. 
  • UC locations work together to create a Common Data Model (CDM) for their local Data Warehouse. See BICG.
  • Data could be pulled from either the ODS directly or the local data warehouse depending upon the data transformations required.
  • All extraction and processing of the data is determined by the location.
  • All Budget and Labor Ledger data will be distributed from the ODS only.

Reporting

Lead: Linda Durst

UCDHS: Mangesh Kamble

  • Operational data is expected to be available directly out of UCPath through a combination of operational reporting, audit reports, and online inquiry screens. This data would be considered “real-time” data, as it is provided directly from UCPath to the user. Analytical reporting from HR Analytics is also provided directly from UCPath, but it is prior day data (similar to the ODS) and is not real time.
  • Common operational and audit reports accessible directly from UCPath will be developed by UCPath. The scope and content of operational reporting is currently under evaluation.
  • HR Analytical reporting will provide trend data. UCPath is currently evaluating the scope and content of this effort.
  • All other local Tier-n extract and reporting requirements are the responsibility of the location, and are expected to be met through a combination of each campus’ local data warehouse and direct access from the local ODS.

Testing

Lead: Anantha Kudar

  • Interface, ODS, and Financial Accounting and Reporting all have testing activities that need to be completed in order to determine that a product is ready for production.