Governance - Precisely Data Integrity Suite

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

Data Integrity Suite provides a high level of flexibility for customizing the system to provide a solution to match the specific data governance requirements of any organization. The Governance tab lets you define business and technical asset types, specify data types, and provide field definitions. This gives the system the context it needs to interpret what each field means and how it behaves.

You'll also integrate models and policies that control how your data is used and managed. Models standardize data handling across your organization and ensure compliance with regulatory requirements. Policies guide data stewardship practices, building accountability and maintaining data integrity. Together, they ensure all your data assets are well-defined, properly categorized, and managed to support your organizational goals.

Go to Governance to configure the following:

  • Domains: Organize and categorize your data assets into logical groupings. Domains help you structure your governance framework, manage asset ownership, and establish clear data stewardship responsibilities across your organization. For more information, see Domains.
  • Business assets: Lists the following details business asset types and description, asset count for each type, click an asset type name to create or manage business assets for that type. For more information, see Business assets.
  • Models: Model assets represent the structural and behavioral aspects of data within your organization. They are used to define and visualize data relationships, constraints, and processes, facilitating better data management and quality. For more information, see Models.
  • Policies: Policy assets are guidelines or rules that govern how data is handled within the organization. They ensure compliance with legal, regulatory, and internal standards, and help in maintaining the integrity and security of data. For more information, see Policies.
  • Rules: Governance rules help you evaluate assets in the catalog based on metadata and asset type. Each rule defines how assets are scored and which asset types it applies to. For more information, see Rules.

Required permissions for Governance features

The following table provides a high-level overview of the actions you can perform from the assigned permissions in the Governance service. It outlines the permissions needed for actions such as viewing, managing, or deleting assets and related capabilities within this service.

Feature Permissions Actions
Relationships View View the existing relationships
Manage
  • Create relationship type
  • Edit the existing relationships
  • Delete existing relationships
Technical Asset View View asset and assignment
Manage
  • Create and edit assets
  • Create and manage assignments
Delete Delete assets
Business Asset View View asset and assignment
Manage
  • Create and edit assets
  • Create and manage assignments
Delete Delete assets

Asset management and types

Every cataloged asset is assigned to a responsible party, such as a business owner or data steward, and its relationship to other assets is thoroughly documented. This provides a comprehensive understanding of the data and its relationships with other business assets, such as reports, applications, or policies. For example, a data steward might manage the customer database and document its relationship with the CRM system.

Asset types in the Data Integrity Suite can be configured to meet organizational needs:

  • Business assets, such as customer reports, can be defined and customized, with change history tracked.
  • Technical assets, such as database servers, can also be defined and customized, with changes tracked.
  • Models provide hierarchical grouping for business assets.
  • Policies govern business assets and data quality rules.

For example, a business asset type for "Customer Reports" can be created, and changes to these reports can be tracked. Similarly, a technical asset type for "Database Servers" can be defined, and changes to server configurations can be tracked.

Importance of asset management components

Assets require specific components such as fields, relationships, predicates, and reference lists to ensure effective management and integrity of data.

  • Fields are essential for capturing specific information about assets, allowing for customization based on asset types. This ensures that relevant data, such as timestamps or updates, is accurately recorded and easily accessible.
  • Relationships define the connections between different assets, which is crucial for understanding how they interact with one another.
  • Predicates serve to clarify the functional types of relationships between assets. They help in establishing dependencies and impacts, which are vital for understanding how changes in one asset can affect others.
  • Reference Lists provide a structured way to categorize and manage data consistently. By creating reference lists with defined fields, organizations can maintain clarity and organization within their data, facilitating better data governance and retrieval.

Together, these components form a comprehensive framework that supports the effective management of assets, ensuring data integrity and enhancing overall operational efficiency.

Workflows

Workflows bridge the gap between the data governance framework and day-to-day activities by allowing users with different responsibilities to collaborate on assets. The Data Integrity Suite includes various workflow features:

  • Trigger types define what initiates a workflow, such as scheduled events or rule-based changes.
  • Conditions specify conditions that must be met for a workflow to proceed.
  • Transitions manage the movement from one workflow state to another.
  • Activities define the tasks and actions within a workflow.
  • Assignments assign tasks to users and manage their completion.
  • Requests handle requests related to data governance.