KQIs Management
Introduction
Key Quality Indicators (KQIs) Management is a fundamental component of Blindata’s data quality framework that enables organizations to systematically define, monitor, and maintain data quality standards. This comprehensive system allows you to create and manage quality checks that measure various dimensions of data quality, from completeness and accuracy to consistency and timeliness.
The KQI Management module provides a structured approach to data quality governance by offering:
- Flexible Quality Check Creation: Define custom quality checks tailored to your specific data requirements and business rules
- Organized Test Suites: Group related quality checks into logical suites for better organization and maintenance
- Lifecycle Management: Control the development, testing, and publication phases of quality checks through draft and published states
- Granular Control: Enable or disable individual checks or entire suites based on your operational needs
- Comprehensive Monitoring: Track quality metrics through dashboards and reports with configurable thresholds and scoring strategies
Whether you’re establishing initial data quality standards or refining existing quality frameworks, the KQI Management system provides the tools and workflows necessary to ensure your data meets the highest standards of reliability and trustworthiness.
Create or Modify a Quality Check
Quality checks are the building blocks of your data quality framework. Each check defines a specific quality metric that will be evaluated against your data. The creation and modification of quality checks is done through a comprehensive form that captures all necessary information.
The quality check definition form includes the following key fields organized into logical sections:
Basic Information
| Field | Description | Purpose |
|---|---|---|
| Suite | The quality suite that this check belongs to | Groups related checks together for better organization |
| Check Code | A unique external identifier for the check | Used to collect and reference results across the platform |
| Name | A descriptive name for the check | Appears in data catalog dashboards and panels |
| Check Group Code | An optional grouping code | Organizes related checks within a suite |
Quality Definition
| Field | Description | Guidelines |
|---|---|---|
| Description | A clear, functional description of what the quality check measures | Focus on the business meaning rather than technical implementation details |
Threshold Configuration
| Field | Description | Details |
|---|---|---|
| Success and Warning Thresholds | Define the scoring thresholds that determine the traffic light status (green/yellow/red) for the KQI | • Thresholds range from 0 to 100 • Example: A success threshold of 95 means scores above 95 generate a green status • Warning thresholds create yellow status for intermediate scores |
Operational Settings
| Field | Description | Use Case |
|---|---|---|
| Is Enabled | Controls whether the check appears in summary dashboards and reports | Enable to include in monitoring and reporting |
| Manual Insert | Allows manual entry of results through Blindata’s interface | Use when automated collection isn’t available |
Scoring Strategy
| Field | Description | Configuration |
|---|---|---|
| Score Strategy | Defines how the quality score is calculated | Options: Minimum, Maximum, Distance |
| Highest, Lowest, Expected Value | Configuration values used by the selected scoring strategy | Values depend on the chosen scoring strategy |
Advanced Configuration
| Field | Description | Reference |
|---|---|---|
| Additional Properties | Custom properties to further characterize the check | See Custom Properties documentation |
| Physical Associations | Links the check to specific physical data entities being monitored | Associates checks with actual data objects |
Quality Suites
Quality Suites are organizational containers that group related quality checks together for better management, maintenance, and reporting. They provide organized structure, development isolation, granular control, and lifecycle management for quality metrics.
Suite and Check Publishing States
Blindata uses a two-level state management system to provide granular control over quality metrics. Quality checks can be Enabled (active and counted in reports) or Disabled (inactive but still editable), while quality suites can be Draft (development/testing, hidden from general users) or Published (live and accessible to all users).
Quality Check States
| State | Description | Behavior |
|---|---|---|
| Enabled | Check is active and contributing to quality metrics | • Results counted in suite dashboards • Appears in summary reports • Fully functional for monitoring |
| Disabled | Check is inactive but still accessible | • Results visible but not counted • Can be edited and configured • Useful for maintenance or temporary suspension |
Quality Suite States
| State | Description | Behavior |
|---|---|---|
| Draft | Suite is in development/testing phase | • Not visible to general users • Checks automatically created as “Disabled” • Safe environment for testing new quality metrics • Requires QUALITY_EDITOR permission to view |
| Published | Suite is live and accessible to all users | • Visible in reports and dashboards • Checks can be individually enabled/disabled • Full operational status |
Managing Quality Check States
When a suite is Draft, all checks are automatically disabled and cannot be enabled until the suite is published. When a suite is Published, you can manage check states in two ways:
Individual Control: Enable/disable specific checks through the check detail page Bulk Control: Enable/disable all checks at once using the gear icon on the suite detail page
State Management Workflow:
| Suite Status | Check State Control | Available Actions |
|---|---|---|
| Draft | Check states locked (all disabled) | • Create and edit checks • Configure check parameters • Cannot enable checks until suite is published |
| Published | Full check state control | • Enable/disable individual checks • Bulk enable/disable all checks • Full operational control |
Creating and Publishing Quality Suites
Quality suites are created through a simple modal form that allows you to define the suite and set its initial state.
Suite Creation Process:
- Access the Creation Modal: Use the suite creation interface to define your new quality suite
- Set Initial State: Choose between “Draft” (for development) or “Published” (for immediate use)
- Configure Suite Details: Provide name, description, and other organizational information
- Add Quality Checks: Create or associate quality checks within the suite
Suite Visibility and Permissions
| Suite State | Visibility | User Access |
|---|---|---|
| Draft | Hidden from general view | QUALITY_EDITOR users only |
| Published | Visible | All QUALITY_VIEWER users |
Note: As with most Blindata objects, quality suites can benefit from team policy settings to control visibility and access across different teams. Team policies allow you to make suites visible or hidden to specific teams, providing additional granular control beyond the basic draft/published states. For more information, see the Team Documentation .