Reltio Information Model and Configuration Concepts

An introduction to Reltio's logical model of the business data and configuration validation.

The Reltio Information Model is the unique architecture designed by Reltio to efficiently model the entities, relationships and interactions that form the basis of your business, as well as the classic ideas such as 1:1, 1:M, and M:M for the entities, but in a truly modern manner, freeing you to easily see your business through a Reltio lens, and gain a level of insight not available before.

There is no need to consider tables, foreign keys or any of the low-level physicality of how the data is stored. For example, if your business suggests that retail customers have a relationship with automobiles, then you might simply start with the Solution Accelerator, “Consumer 360” on your tenant. Consumer 360 which provides the consumer entity type, and most of the other objects you’ll need, preconfigured. You, and then simply declare an automobile type and a relationship type that links the automobile type to the consumer type them. That is all. That simple definition supports 1:1, 1:M, and M:M m:m scenarios with no further effort.

These application-level definitions are stored in a tenant configuration and associated with your tenant. As such, the configuration sits in a layer on top of the Reltio platform and natively enjoys all of the capabilities provided by the platform such as matching, merging, cleansing, standardization, workflow, and so on. And all entities you establish in your tenant can easily be associated with interactions you may also choose to bring into the Reltio platform. The ability to hold and link all three kinds of your data: entities, relationships, and interactions in the platform and leverage the confluence of them in one place provides unlimited power to model and understand your business.

Object Inheritance

Reltio metadata configuration is based on a n-layer model. Most customers utilize a 3-layer model which is the default arrangement. Each layer is represented by a JSON file. Of the three layers, only layer 3, known as the “L3” is accessible by the customer. It is the layer that is tightly bound to your tenant. It typically inherits from the L2 layer (a Reltio industry-focused layer) which in turn inherits from the L1 layer (Reltio’s industry-agnostic layer). Any object can be defined in any layer. It is the consolidated configuration resulting from the inheritance between the three layers that is commonly referred to as the “tenant configuration” or “metadata configuration”.

Reltio's metadata configuration consolidates simple, nested, and reference attributes from all the related layers. Values described in the higher layer overrides the values from the lower layers. The number of layers does not affect the inheritance.

Note that only attributes (or attribute parameters) that must be extended or overriden, are set in the next layer. You do not have to duplicate all the attributes and parameters from the previous layers.

Attributes cannot be deleted during inheritance. An attribute is not removed if it is not specified at the next configuration level. However, the attributes can be hidden by setting hidden:true.

To change the sub-attributes you need to specify only those sub-attributes, which must be changed, and the other sub-attributes are inherited from the lower level containers.
Note: The following properties must be inherited:
  • Hidden property
  • Important property
  • System property
  • skinInDataAccess property
If these properties are not defined in the configuration, then false values are considered.

The Reltio L1 Layer

This the root level layer and contains industry-agnostic objects defined and controlled by Reltio Product Management.

The L1 layer contains entities such as Party (an abstract type) and Location. It contains a fundamental relationship type called HasAddress that links the Party type to the Location type. L1 also extends the Party type to Organization and Individual (both are non-abstract types). There is only one L1 layer, and its role is to define industry-agnostic objects that can be inherited and utilized by industry specific layers that sit at the L2 level. This enables Reltio to enhance the objects in the L1 layer, potentially affecting all Reltio customers. For example, if Reltio were to add an additional attribute into the HasAddress relationship type, it would be available for immediate use by any Reltio customer.

The Reltio L2 Containers

L2 containers are configured by Reltio.

The L2 layer inherits the objects from the L1 layer. Whereas there is only a single L1 set of objects, the objects at the L2 level are grouped into industry-specific containers. Like the L1 layer, the containers at the L2 level are also controlled by Reltio Product Management and not accessible by customers. Life Sciences is a good example of an L2 container. It inherits the Organization entity type from L1 and extends it to the Health Care Organization (HCO) type needed in Life Sciences. As such, the HCO type enjoys all of the attribution and other properties of the Organization type, but defines additional attributes and properties needed by an HCO.

The Customer's L3

The L3 layer is a JSON file customers can edit and apply to the tenant.

The L3 layer is a JSON file tightly bound to the customer’s tenant. It is easily retrieved from the tenant, edited and applied back to the tenant using Configuration API. Usually the L3 refers to an L2 container and inherits all objects from the L2 container. However, it is not required that the L3 refer to the L2 container, it can standalone. A standalone configuration requires removed of the L2 reference.
Note: Objects from the L1 layer are also inherited when the L2 is referenced.
Important: It is strongly recommended to configure the L3 to reference one of Reltio’s industry-specific L2 containers. Doing so provides the L3 with all of the L1 industry-agnostic objects, as well as the industry-specific objects from the L2 container. It also ensures your configuration continues to leverage enhancements to the models and objects defined in the L1 and L2 layers.