...
YOUnite has focused on making the processes and implementation of data integration and MDM as intuitive as possible and allows organizations to ease into the process with features like data domain versions. With data domain versions, the organization can start with a small set of data to be shared between systems and organizations and can organically grow the set with new versions of the same data domain. Before starting read the quick overview Data Analysis Principles of the Federated Master Data Management Process. By following the step in the overview,, MDM can be eased into your organization.
It is assumed that the appropriate stakeholders in your organization have committed to the process of integrating data with a cohesive solution (see step 4 below):
| Sequence | Step | Summary |
|---|---|---|
| 1 | Identify integration use cases that need to be addressed | This includes identifying scope |
| 2 | Identify the data that needs to be integrated | |
| 3 | Identify systems to connect together | |
| 4 | Ensure absolute buy-in from all parties responsible for those systems | |
| 5 | Identify the MDM Admin and DGS. | A root zone is created with a MDM Admin and Data Governance Steward (DGS). These users are tied users in your organization's IDP. Its important to note that the MDM Admin is responsible for permissions to the system and the DGS's role is more related to data governance (scope). Another key point is that by default, the DGS is NOT in control of the data at at the adaptors in the zones. |
| 6 | Initialize the YOUnite MDM/Data Hub system. | Configure YOUnite, the MDM admin & DGS information. When the system initializes it automatically configures the MDM admin and DGS it with this information. |
| 7 | DGS determines which data domains that need to be modeled | See the Data Analysis Principles of the Federated Master Data Management Process. |
| 8 | DGS Models data domains using the YOUnite UI | |
| 9 | Create Zones and Users/Roles in the YOUnite UI | Includes ZDS and Zone Admin for each zone. |
| 10 | Load data into the YOUnite Data Store if any of the domains are defined to use it. | This is generally reference data available to everyone across the system |
| 11 | Develop the adaptors using the YOUnite adaptor SDK | Writing the appropriate GET/PUT/POST/DELETE methods that map to the elements in the domains that are in the application attached to the adaptor |
| 12 | DGS & ZDS collaborate to bring data in the systems under YOUnite control | Leverage YOUnite API to seed data record pointers between native source and YOUnite Data Hub/MDM. Intention is to collaborate with Experis/Infinity team to build command-line utilities. Goes through de-duplication/data quality checks in YOUnite. |
| 13 | DGS & ZDS apply appropriate in-bound and out-bound scope to the data to be managed. Other data designations as master data and level 2 data are defined at this time. | DGS allows you "in-the-door" to the data domain and data record level (federated data record - reference pointers). ZDS owns the data at the adaptor and determines inbound/outbound scope for the zone and the adaptors in the zone. (DGS owns the reference to the data or data stored in YOUnite data hub. ZDS owns the actual data inbound/outbound scope) |