IM Relationship Resolution Information Center, Version 4.2

Load Summary Report

The Load Summary report summarizes statistics and quality characteristics by data source. It contains information about the data source files. Use this report to determine performance load statistics, the number of entity resolutions and alerts generated by this load, general information about the data quality of the files loaded, a summary of the actions about the UMF document for this load, and any UMF exceptions generated by this load. The report is sorted by load group, data source, data file, and then date loaded.

For each data file and date loaded within data source and load group, the report breaks the statistics into sections:

Load Summary

You can use this section to help determine how long it took to process a particular file, as well as to give you a general idea of how useful this data source file is in overall entity resolution and relationship detection.

Date and Time Started
Date and time that the data load began.
Date and Time Completed
Date and time that the data load ended
UMF Record Count
Total number of records loaded from this data file within the Date and Time Started and Date and Time Completed range.
The Date and Time Completed number minus the Date and Time Started number is the number of minutes it took to load this particular file, which can give you an idea of system performance. It may also indicate that a larger data source file should be split into smaller files for quicker processing.
New Identities
Total number of new identities loaded within the Date and Time Started and Date and Time Completed time frame.
New Identity %
Percentage of total identities in this data load that are new identities (not seen before by the system)
New Entities
Total number of new entities resolved in the Date and Time Started and Date and Time Completed time frame.
New Entity %
Percentage of total entities that are newly resolved entities as a result of this data load.
The number of new identities and new entities can provide you a general idea of how valuable this data source is in overall entity resolution and relationship detection. If these numbers are low and remain low over a period of time, it may be that this data source is not useful in meeting your organization's entity resolution goals.

Role Alert Summary

Use this section to see the resolution rules and resolution scores common to the relationships detected that resulted in role alerts. Each row represents the number of role alerts that were generated, based on the criteria listed.

Resolution Rule
Name of the resolution rule used to evaluate the identity and entity during entity resolution and relationship detection.
Alert Description
Name of the role alert rule that triggered the role alert.
Severity
User-defined indicator to measure the priority or importance of this role alert.
Resolution Score
Resolution score (0-100) for the resolution rule given to the identity and entity involved in the role alert.
This score indicates the degree of likeness between the identity and the entity. A score of 100 means the identity record resolved to the entity.
Alert Count
Total number of role alerts generated based on the role alert rule description, resolution rule, and resolution score.

Relationship Summary

Use this section to see the attributes common to detected relationships that did not generate a role alert. Each row represents the number of relationships that were detected, based on the criteria listed.

Resolution Rule
Name of the resolution rule used to evaluate the identity and entity during entity resolution and relationship detection.
Resolution Score
Resolution score (0-100) for the resolution rule given to the identity and entity involved in the role alert.
This score indicates the degree of likeness between the identity and the entity. A score of 100 means the identity record resolved to the entity.
Relationship Score
Relationship score (0-100) for the resolution rule given to the identity and entity involved in the role alert. This score indicates the degree of relationship between the identity and the entity.
A score of 100 means the identity record resolved to the entity. The higher the relationship score, the more closely related the identity and entity are, based on matching attributes.
Relationship Count
Total number of relationships that are detected based on the resolution rule, resolution score, and relationship score.

Quality Summary

Use the information in this section to evaluate the quality of the data in each data source file. The section indicates the quality by attribute type within a UMF segment and UMF document type. By reviewing the Quality summary with the UMF exceptions summary, you can see which data source files have quality issues or malformed UMF that need to be addressed. Typically, you can resolve these issues through ETL or DQM/data source configuration before processing the data source file.

In some cases, this section can indicate that a data source is of such poor quality, that it should no longer be processed for entity resolution.

Document Type
Name of the UMF document type that contains the data type listed in Data Type. Usually, this value is UMF_ENTITY.
Table Name
Name of the database table that stores UMF segment data for the data type listed in Data Type.
Data Type
Actual data type, as listed in the incoming records attribute type UMF tags. This type corresponds to a UMF segment listed in Table Name. For example, if the Table Name is ADDRESS and the Data Type listed is H, the quality information is evaluating the address type of Home.
If you do not recognize a data type, it may indicate that the data source file is not correctly mapped to the appropriate combination of UMF documents, segments, and tags. Check the Exception Summary section to see if a matching UMF segment and UMF tag caused one or more segment exceptions. If the problem is incorrect UMF, the numbers in the Low Quality Count in the Quality Summary section and the Segment Exception Count in the UMF Exception section often match.
Record Count
Total number of incoming identity records containing this data type.
Generic Count
Total number of all incoming identity records where records with this value (for this type) are considered generic.
Low Quality Count
Total number of all incoming identity records where values for this data type are considered of poor quality. This number may indicate a data entry or ETL transformation problem in the data source file.
Usable Percent
Percentage of the incoming identity records of this UMF segment and data type that are usable for entity resolution and relationship detection. (Record Count minus Generic Count minus Low Quality Count) divided by record count equals Usable Percent.)
Identity Percent
Percentage of the incoming identity records in this data source that contained this data type.

Attribute Summary

Use this section to see the attributes in the data source file that helped to detect relationships and generate role alerts. Each attribute maps to a specific UMF segment, and this section shows the number of relationships detected and role alerts generated, based on the data in the incoming UMF segment.

Segment Name
Name of the UMF segment, which directly maps to an attribute.
Data Type
Lists the attribute type (or data type) within the UMF segment corresponding to the Precision Description. The report might list a specific attribute type or list ALL, indicating all attribute types in the UMF segment.
Precision Description
Description of the matching threshold between an attribute from an inbound identity and an attribute from an existing entity.
Role Alerts
Total number of role alerts generated based on this UMF segment, data type, and precision description.
Relationships
Total number of relationships detected based on this UMF segment, data type, and precision description

UMF Document Summary

You can use this section to validate the total number of incoming records in a data source file, based on what action is to be taken to the record: new/add, change, or delete. You can reconcile these numbers to the Record Count in the Load Summary section.

Document Type
Name of the UMF document type. Usually, this value is UMF_ENTITY.
Action
Type of action for the incoming identity record:
  • A for add
  • C for change
  • D for delete
As part of the ETL process, identity records are typically tagged through UMF to indicate how to act on each incoming record during system processing.
UMF Record Count
Total number of records processed for each action type within document type.
Percent
Percentage of the total records loaded that the Record Count represents. (The sum should not exceed 100%.)

Exception Summary

Use this information to help pinpoint bad identity records, such as those with malformed UMF. The exception describes the problem, while the table name and element show which segment and record are bad. The count shows how many of the records in the file contained this bad UMF.

Document Type
Name of the UMF document type. Usually, this value is UMF_ENTITY.
Action
Type of action for the incoming identity record:
  • A for add
  • C for change
  • D for delete
As part of the ETL process, identity records are typically tagged through UMF to indicate how to act on each incoming record during system processing.
Segment
Name of the UMF segment where the exception occurred.
UMF Tag
Value of the UMF tag that caused the UMF exception.
Exception
Message ID or other exception code to indicate the type of UMF exception that occurred and give information about how to resolve the exception. This information is also available in the UMF_EXCEPT table.
Segment Exception Count
Total number of this type of UMF exception.
Check the Low Quality Count in the Quality Summary section to see if a matching data type is reported as being of poor or unusable quality. If the problem is incorrect UMF, the numbers in the Low Quality Count in the Quality Summary section and the Segment Exception Count in the UMF Exception section often match for the same UMF segment and UMF tags.


Feedback

Last updated: 2009