YOUnite Adoption Plan

Once you have an understanding of YOUnite you can begin to plan the steps to implement it.

Introduction

Most organizations have selected multiple vendors for various solutions for good reasons. Divisions often pick the best solution to meet the needs of their operations. For example, the sales organization may select one CRM while accounting uses a different CRM from a different vendor. Both selected the best solution for their own individual needs.

YOUnite has focused on making the processes and implementation of federated data principles as intuitive as possible and allows organizations to ease into the process with features like data domain versions. With data domain versions, an 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.

If you haven’t read it already, you may want to read the Data Analysis Principles of Data Discovery, Cataloging and Synchronization overview. By following the steps in the overview, federated discovery, cataloging, synchronization and governance can be eased into your organization.

Adoption Plan

The steps below outline the YOUnite implementation. These phases include the design, development and implementation phases required to fully integrate the YOUnite Data Fabric into an organizations IT infrastructure.

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
	DESIGN PHASE
1	Identify the Data Governance Steward(s) (DGS).	DGS are person(s) designated as the Data Steward(s) by the governance organization of the tenant. These person(s) are assigned the Data Governance Steward role in the YOUnite system and are responsible for applying the Data Governance Policies primarily as regards to the data taxonomy for the tenant. Please note that actual content control lies with the Zone Data Steward (ZDS). See step 10, below.
2	Identify integration use cases that need to be addressed and the associated Zone Data Stewards (ZDS).	Identify data integration/synchronization use cases, systems, and stakeholders that have YOUnite needs. Equally important in this phase is identifying governance and data event notification requirements.
3	Identify the data that needs to be integrated and the systems that need to connect to the YOUnite Data Fabric.	Formalize the findings from step 2.
4	Identify the Root Admin.	An initial root zone will be created with an Root Admin and DGS (mentioned above). These users are tied users in your organization’s IDP. The Root Admin is responsible for permissions to the system and the DGS’s role is related to data governance. Another key point is that by default, the DGS is NOT in control of the data at the adaptors in the zones.
5	Set expectations and ensure absolute buy-in from all parties responsible for those systems.	Expediting the YOUnite deployment is critical since there are many moving components that need to converge for the overall success of the project. A single stakeholder can stall the effort so its important to get complete buy-in from all parties involved.
6	DGS determines the data domains that need to be modeled.	See Data Analysis Principles of Data Discovery, Cataloging and Synchronization. Step 12 can be started in parallel with the following steps.
7	Plan for the implementation of the YOUnite Data Fabric in a test environment.	Review steps 8-11.
	DEVELOPMENT PHASE
8	Implement a test YOUnite Data Fabric deployment.	Configure the Root Admin and DGS information. When the system initializes it automatically configures the Admin and DGS with this configuration information. This step includes configuring and deploying YOUnite’s Message Bus, logging systems. It also includes integrating with ehe organization’s SSO ID to work with the YOUnite Data Fabric’s services that have UI management features.
9	DGS models data domains using the YOUnite UI.	Follows from Step 6.
10	Create zones and users, groups and/or roles in the YOUnite UI.	Includes the Zone Admin and Zone Data Steward for each zone. Reference here: Zones, Users, Groups, Roles and Permissions.
11	Develop the adaptors using the YOUnite adaptor SDK.	Design and write the appropriate GET/PUT/POST/DELETE methods that map, and often transform, data records in the organizations source systems. The entities in the source systems map to the YOUnite data domains. This includes detecting changes in entities in the source system and sending them to YOUnite. Adaptors are written with the YOUnite Adaptor SDK. This step can be started after step 6. For further details, see: Creating and Managing Adaptors Adaptor SDK Summary
	IMPLEMENTATION PHASE
12	Configure the production YOUnite Data Fabric.	See Step 8 above.
13	Bring federated data under YOUnite control. The DGS and ZDS collaborate to map entities in the systems attached to YOUnite adaptors under YOUnite control.	Leverage the YOUnite Server API to map existing entities in the source systems to a YOUnite Data Fabric deployment’s data records. This phase includes data cleaning and de-duplication of source entities.
14	The DGS and ZDS apply appropriate in-bound and out-bound governance (i.e. Access Controls Lists, or ACLs) to the data to be managed.	The DGS allows you "in-the-door" to the data domain and data record level (federated data record - reference pointers). The ZDS owns the "data at the adaptor" and determines inbound/outbound ACLs for the zone and the adaptors in the zone. (The DGS owns the "reference or pointer to the data" or data stored in YOUnite Server. The ZDS owns the actual data inbound/outbound ACLs).
15	New and legacy applications become YOUnite aware.	Users and new and/or legacy applications can receive Webhook Notifications using the Notification Service when change occur to data records mapped to YOUnite.

Sequence

Step

Summary

DESIGN PHASE

Identify the Data Governance Steward(s) (DGS).

DGS are person(s) designated as the Data Steward(s) by the governance organization of the tenant. These person(s) are assigned the Data Governance Steward role in the YOUnite system and are responsible for applying the Data Governance Policies primarily as regards to the data taxonomy for the tenant. Please note that actual content control lies with the Zone Data Steward (ZDS). See step 10, below.

Identify integration use cases that need to be addressed and the associated Zone Data Stewards (ZDS).

Identify data integration/synchronization use cases, systems, and stakeholders that have YOUnite needs. Equally important in this phase is identifying governance and data event notification requirements.

Identify the data that needs to be integrated and the systems that need to connect to the YOUnite Data Fabric.

Formalize the findings from step 2.

Identify the Root Admin.

An initial root zone will be created with an Root Admin and DGS (mentioned above). These users are tied users in your organization’s IDP. The Root Admin is responsible for permissions to the system and the DGS’s role is related to data governance. Another key point is that by default, the DGS is NOT in control of the data at the adaptors in the zones.

Set expectations and ensure absolute buy-in from all parties responsible for those systems.

Expediting the YOUnite deployment is critical since there are many moving components that need to converge for the overall success of the project. A single stakeholder can stall the effort so its important to get complete buy-in from all parties involved.

DGS determines the data domains that need to be modeled.

See Data Analysis Principles of Data Discovery, Cataloging and Synchronization. Step 12 can be started in parallel with the following steps.

Plan for the implementation of the YOUnite Data Fabric in a test environment.

Review steps 8-11.

DEVELOPMENT PHASE

Implement a test YOUnite Data Fabric deployment.

Configure the Root Admin and DGS information. When the system initializes it automatically configures the Admin and DGS with this configuration information. This step includes configuring and deploying YOUnite’s Message Bus, logging systems. It also includes integrating with ehe organization’s SSO ID to work with the YOUnite Data Fabric’s services that have UI management features.

DGS models data domains using the YOUnite UI.

Follows from Step 6.

Create zones and users, groups and/or roles in the YOUnite UI.

Includes the Zone Admin and Zone Data Steward for each zone. Reference here: Zones, Users, Groups, Roles and Permissions.

Develop the adaptors using the YOUnite adaptor SDK.

Design and write the appropriate GET/PUT/POST/DELETE methods that map, and often transform, data records in the organizations source systems. The entities in the source systems map to the YOUnite data domains. This includes detecting changes in entities in the source system and sending them to YOUnite. Adaptors are written with the YOUnite Adaptor SDK. This step can be started after step 6.

For further details, see:

IMPLEMENTATION PHASE

Configure the production YOUnite Data Fabric.

See Step 8 above.

Bring federated data under YOUnite control.

The DGS and ZDS collaborate to map entities in the systems attached to YOUnite adaptors under YOUnite control.

Leverage the YOUnite Server API to map existing entities in the source systems to a YOUnite Data Fabric deployment’s data records. This phase includes data cleaning and de-duplication of source entities.

The DGS and ZDS apply appropriate in-bound and out-bound governance (i.e. Access Controls Lists, or ACLs) to the data to be managed.

The DGS allows you "in-the-door" to the data domain and data record level (federated data record - reference pointers). The ZDS owns the "data at the adaptor" and determines inbound/outbound ACLs for the zone and the adaptors in the zone. (The DGS owns the "reference or pointer to the data" or data stored in YOUnite Server. The ZDS owns the actual data inbound/outbound ACLs).

New and legacy applications become YOUnite aware.

Users and new and/or legacy applications can receive Webhook Notifications using the Notification Service when change occur to data records mapped to YOUnite.