The BvD integration requires Data model for Customer Data (B2B) - LEGACY to be enhanced with the following additional attributes:

• A BvD identifier attribute, which is a unique identifier of the organization in the Orbis interface.
• A BvD crosswalk source type attribute. The crosswalk type is configuration/sources/BvD.
• A BvD relationship type attribute for an organization’s hierarchy. The relationship type is configuration/relationTypes/BvDHierarchy. It is used to create a hierarchy between organizations.

The process of data enrichment automatically creates an ownership structure between the account being enriched and its parent and branch organizations. In Reltio, this structure is called the Company Hierarchy. The Company Hierarchy facet is displayed for every account that contains the BvD enriched data. It will have the following hierarchies:

• BvD Identifier : The unique BvD identifier that represents the entity being enriched. It is generated for a matched record after a potential match is found.
• HQ BvD ID: The organization that represents the immediate entity above the BvD ID being enriched.
• Domestic Ultimate BvD ID: The domestic ultimate represents the highest member of the hierarchy in a specific country.
• Global Ultimate BvD ID: The global ultimate represents the highest member of the entire family tree. The global ultimate record is at the top of the company hierarchy.

Table 1: Roles describes the roles used in BvD:

Table 1. Roles

Role	Function
ROLE_INTEGRATION_SPECIALIST	Administration and Implementation of the BvD integration.
ROLE_API ROLE_UI	Data Steward in Customer Tenant and Data Tenant. They can do on-demand data enrichment in Reltio's Profile page.
ROLE_ADMIN_TENANT	Batch job scheduling for regular data updates Deploy BvD in the Customer Tenant Deploy BvD in the Data Tenant