{"id":5070,"date":"2025-11-03T13:10:59","date_gmt":"2025-11-03T18:10:59","guid":{"rendered":"https:\/\/staging.dcamportal.org\/?p=5070"},"modified":"2026-02-24T15:11:54","modified_gmt":"2026-02-24T20:11:54","slug":"dcam-v3-framework-beta-5-0-data-quality-management","status":"publish","type":"post","link":"https:\/\/staging.dcamportal.org\/fr_ca\/dcam-v3-framework-5-data-quality-management\/","title":{"rendered":"Cadre du DCAM v3 - 5.0 Gestion de la qualit\u00e9 des donn\u00e9es"},"content":{"rendered":"
\r\n
\r\n
\r\n
\r\n
\r\n\r\n\r\n<\/div>\r\n<\/div>\r\n\r\n

\"DCAM<\/p>\r\n\r\n

\r\n
\r\n\r\n

Upper Matter<\/h3>\r\n<\/div>\r\n
\r\n
\r\n

Introduction<\/h3>\nData Quality<\/span> Management defines the goals, approaches and plans of action that ensure data content is of sufficient quality to support defined business objectives of the organization. Data Quality<\/span> Management should be developed in alignment with business requirements, measured against defined data quality dimensions<\/span> and based on an analysis of the current state of Data Quality<\/span>. Data Quality<\/span> Management is a series of processes across the full data life cycle to ensure that the data provisioned meets the needs of its intended consumers.\n\nBy ensuring that data cleansing and validation processes are efficient and effective, Data Quality<\/span> Management enables the organization to maintain a robust data control environment. This ensures that data is fit for its intended purpose, supports informed decision-making, enhances operational efficiency, and delivers measurable value to the business.\n

Definition<\/h3>\r\nData Quality<\/span> Management component<\/b> encompasses a set of capabilities to implement data profiling<\/span>, business-driven quality evaluation, quality control rule development, monitoring, defect management, root cause analysis, and data issue remediation. These capabilities allow the organization to execute data quality<\/span> processes across the data life cycle to ensure and control that data is fit for its intended purpose.\n

Scope<\/h3>\r\n
    \r\n \t
  • Establish a Data Quality<\/span> Management function<\/span>.<\/li>\r\n \t
  • Work with Data Management Program Management Office<\/span> to design and implement sustainable business-as-usual processes and tools for Data Quality<\/span> Management.<\/li>\r\n \t
  • Perform Data Quality<\/span> Management processes against the organization’s prioritized data. Data Quality<\/span> Management processes include profiling<\/span> & grading, rule building, ongoing measurement, defect management, root cause fix, remediation.<\/li>\r\n \t
  • Establish Data Quality<\/span> rules, metrics and reporting routines.<\/li>\r\n \t
  • Ensure that Data Quality<\/span> Management and Data Quality<\/span> Management Governance are integrated into Data Governance.<\/li>\r\n<\/ul>\r\n

    Value Proposition<\/h3>\nOrganizations that build, formalize, and assign data quality<\/span> responsibilities to daily business routine can achieve improved data culture.\n\nOrganizations that effectively implement Data Quality<\/span> Management across the data ecosystem get a ROI from several areas:\n
      \r\n \t
    • Better risk management<\/li>\r\n \t
    • Enhanced analytics<\/li>\r\n \t
    • Better client service and product innovation<\/li>\r\n \t
    • Improved operational efficiencies<\/li>\r\n \t
    • Lower cost of change \/ transformation and quality improvement<\/li>\r\n<\/ul>\r\n

      Overview<\/h3>\nData Quality<\/span> is a broad conceptual term<\/span> that needs to be understood in the context of the organizational processes where data is used. Seeking to create “perfect” data is not always a viable objective. The organization needs to develop a Data Quality<\/span> Management approach and establish overall plans for managing the integrity and relevance of its data. The quality of the data needs to be defined in terms that are relevant to the data consumers to ensure that it is fit for its intended purpose. The overall goal of Data Quality<\/span> is to ensure that data consumers have confidence in the data they receive from data producers. Given that Consumers are using data to support business functions and make decisions, the data must communicate facts that conform with the user’s domain<\/span>, context, and operational requirements. There should be little or no need for reconciliation or manual transformation of the data on the part of the consumer. Data Quality<\/span> is a process<\/span> not a project. One of the essential objectives is to create a shared culture of Data Quality<\/span> stemming from executive management and integrated throughout the operations of the organization.\n\nData quality<\/span> can be segmented into measurable dimensions. Organizations can benefit from using data quality dimensions<\/span> to classify defects, which will enhance proper remediation efforts and enable effective monitoring. The dimensions, such as those presented below, are typical examples for consideration.\n\nDQ can be segmented into dimensions:\n
        \r\n \t
      • Accuracy<\/span><\/b>: the relationship of the content with original intent\r\n
          \r\n \t
        • Example: the correct date associated with a document<\/i><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
        • Completeness<\/span><\/b>: the availability of required data attributes\r\n
            \r\n \t
          • Example: all employees<\/span> have a hire date in an HRIS<\/i><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
          • Consistency<\/span><\/b>: how well the data complies with the required formats and definitions across datasets\r\n
              \r\n \t
            • Example: an address is the same for a business across AP and Vendor Management<\/i><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
            • Coverage<\/span>:<\/b>: the availability of required data records\r\n
                \r\n \t
              • Example: a data set<\/span> includes all the values for the required time period<\/i><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
              • Timeliness<\/span><\/b>: the currency of content representation as well as whether the data is available\/can be used when needed\r\n
                  \r\n \t
                • Example: data is in a data set<\/span>, but was entered too late causing missed deadlines<\/i><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
                • Uniqueness<\/span><\/b>: the degree that no record or attribute is recorded more than once\r\n
                    \r\n \t
                  • Example: multiple records that refer to the same individual in a CRM system<\/i><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
                  • Validity<\/b>: the degree data conforms to its agreed upon definition of syntax, including format, type, and range\r\n
                      \r\n \t
                    • Example: month should be a numeric value between 1 and 12.<\/i><\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\nThe identification and prioritization of data quality dimensions<\/span> foster effective communication about Data Quality<\/span> expectations and provide benefit to the Data Management initiative.\n\nCreating a profile of the current state of data quality<\/span> is an important aspect of the overall Data Quality<\/span> Management function<\/span>.\n\nA new profile should be created when data is onboarded or created, and periodically when data is transformed or there is change within the data ecosystem. The goal is to assess patterns in the data as well as to identify anomalies and commonalities as a baseline of what is currently stored and how actual values may differ from expected values. Once the data profile is established, the organization needs to evaluate the data against the quality tolerances and thresholds defined by the Data Quality<\/span> requirements. The evaluation also examines business requirements to validate that the data is fit-for-purpose.\n\nThe purpose of this evaluation process<\/span> is to measure the quality of the most important business attributes of the existing data and to determine what content needs remediation. The responsibility of the data producer<\/span> and data consumer<\/span> is to identify the data critical to the data consumers’ business processes. Prioritizing the data based on criticality then informs the Data Quality<\/span> Management function<\/span> on which attributes require a heightened level of control and governance. Data that is designated as critical requires the highest level of data quality<\/span> across the identified dimensions. The profile evaluation process<\/span> identifies data that needs remediation to meet data consumer<\/span> requirements. Data cleansing and\/or remediation should be identified based on a predefined set of business rules that identify defects and are linked to business and operational processes.\n\nData remediation should be performed as close to the point of capture or creation as possible. Implementing a root-cause analysis approach for data remediation will address additional factors impacting data quality<\/span> including, business processes, user-interface updates, and other non-data related influences. There should be clear accountability and a defined strategy for data remediation to ensure that rules and processes are known thus avoiding duplicate processing at multiple points in the data life cycle. The overall goal is to remediate data once, based on verifiable documentation and business rules as well as to fix the processes that allowed defective data into the system at the root cause. Data corrections must be communicated to, and aligned with, all downstream repositories and upstream systems. It is important to have a consistent and documented process<\/span> for issue escalation and change verification for both data producers and data vendors.\n\nIt is also important to ensure that data meets quality standards throughout the life cycle so that producers and consumers of data have clearly defined expectations related to how data is managed both at rest and in transit. Standards support the integration of data into operational data stores, the propagation of data across the internal ecosystem, external data exchange with third parties, and expectations related to security, regulatory requirements and risk management.\n\nFor Data Quality<\/span> to be sustained, a strong governance structure with the highest level of organizational support from senior executive management must be in place. This supports Data Quality<\/span> Management activities and ensures compliance with Data Quality<\/span> processes. Data Quality<\/span> processes need to be documented, operationalized and routinely validated via Data Management reviews and formal audit processes.\n\nData Quality<\/span> cannot be achieved through central control. Organization-wide Data Quality<\/span> requires the commitment and participation of a broad set of stakeholders. Data Quality<\/span> is the result of a series of business processes creating a data supply chain. Therefore, stakeholders, along that chain, must be authorized and held responsible for the quality of data as it flows through their respective areas. Data Quality<\/span> requires coordinated organizational support. Data Quality<\/span> Management processes and objectives must be part of the operational culture of an organization for it to be sustained and successful.\n

                      Core Questions<\/h3>\r\n
                        \r\n \t
                      • Is it understood that poor quality data is often an indication of a broken business process<\/span> or technology?<\/li>\r\n \t
                      • Is it understood that instituting a Data Quality<\/span> system is a cultural shift that touches all aspects of business, operations and technology processes?<\/li>\r\n \t
                      • Are roles and responsibilities defined to sustain the Data Quality<\/span> Management function<\/span>?<\/li>\r\n \t
                      • Are the necessary people and funding resources earmarked to implement and operate the Data Quality<\/span> Management function<\/span>?<\/li>\r\n \t
                      • Are the core operational processes formalized and communicated (profiling<\/span>, monitoring, remediation, standards management, change management)?<\/li>\r\n \t
                      • Are Data Quality<\/span> Management standards authored, approved and communicated?<\/li>\r\n \t
                      • Are the necessary resources in place to provide organization-wide training to support a sustainable, Data Quality<\/span> cultural change?<\/li>\r\n \t
                      • Is there senior-level support formalized around a means to escalate and socialize Data Quality<\/span> issues?<\/li>\r\n<\/ul>\r\n

                        Core Artifacts<\/h3>\r\nThe following are the core artifacts<\/b> required to execute an effective Data Quality<\/span> Management capability. Items with an ‘*’ link to published best practice guidelines.\n
                          \r\n \t
                        • Critical Data Element<\/span> Identification Method & Criteria<\/li>\r\n \t
                        • Data Profiling<\/span> Methodology<\/li>\r\n \t
                        • Data Quality Dimensions<\/span> Framework*<\/li>\r\n \t
                        • Data Quality<\/span> Metrics & Dashboards<\/li>\r\n \t
                        • Data Quality<\/span> Rules Inventory<\/li>\r\n \t
                        • Defect Management Methodology<\/li>\r\n \t
                        • Root Cause Analysis Methodology<\/li>\r\n \t
                        • Integration\/Migration\/Migration Impact Assessment<\/li>\r\n<\/ul>\r\n\r\n\r\n<\/div>\r\n<\/div>\r\n\r\n
                          \r\n\r\n

                          5.1 Data Quality Management<\/h3>\r\n<\/div>\r\n
                          \r\n
                          \n\nThe Data Quality<\/span> Management function<\/span> approach and plan must be defined and approved by stakeholders. Roles and responsibilities across the stakeholders must be established with auditable operational processes in place.\n\n\n\n<\/div>\r\n<\/div>\r\n\r\n
                          \r\n\r\n

                          5.1.1 Data Quality Management Approach and Plan<\/h3>\r\n<\/div>\r\n
                          \r\n
                          \r\n
                          Description<\/h5>\nThe approach and plan must be defined for the Data Quality<\/span> Management function<\/span> and reflect the related vision and objectives of the Data Management Approach. Once established, it must be formally empowered by senior management and its role communicated to all stakeholders.\n
                          Objectives<\/h5>\r\n
                            \r\n \t
                          • Formally establish the Data Quality<\/span> Management approach and plan within the organization.<\/li>\r\n \t
                          • Ensure alignment of stakeholder<\/span> roadmaps and plans with the Data Quality<\/span> Management strategy.<\/li>\r\n \t
                          • Communicate the role of the Data Quality<\/span> Management function<\/span> across the organization.<\/li>\r\n \t
                          • Operate the Data Quality<\/span> Management function<\/span> collaboratively with Data Management initiative stakeholders.<\/li>\r\n \t
                          • Secure authority to enforce Data Quality<\/span> Management compliance through policy<\/span> and documented procedures.<\/li>\r\n<\/ul>\r\n
                            Advice<\/h5>\nThe Data Quality<\/span> Management strategy and approach encompasses the what, how, when, who, and why of Data Quality<\/span>. It needs to address what scope of data is to be scrutinized and reviewed, how the Data Quality<\/span> assessments will be performed with defined metrics, when and how often assessments will take place and who will be responsible with defined roles. Data Quality<\/span> Management needs to be closely aligned with the organization's business objectives to ensure that the most important data is properly maintained and monitored, demonstrating how data quality<\/span> initiatives can support business outcomes and avoid the risks and costs of defective data. Data Quality<\/span> Management involves cultural change. It is critical that a documented Data Quality<\/span> Management strategy and approach is socialized with business, data, and technology stakeholders to ensure awareness, support and commitment.\n\nThe rapidly evolving focus on data ethics is introducing new requirements for the Data Quality<\/span> Management function<\/span>. These requirements include an ethical review as part of determining that data produced is fit-for-purpose. Additionally, Data Quality<\/span> Management is one of the areas where the use of techniques and tools such as Artificial Intelligence may assist in the processes used to achieve quality data. These requirements and opportunities should be evaluated in the strategy and approach of the Data Quality<\/span> Management function<\/span>.\n\nAlignment of the Data Quality<\/span> Management approach and the roadmap to the Data Management Strategy and objectives is achieved by agreement between the operating-level data officer<\/span> via the Data Governance structure. The operating-level data officer<\/span> is accountable for establishing priorities across each of the Framework Component requirements.\n
                            Questions<\/h5>\r\n
                              \r\n \t
                            • Has the Data Quality<\/span> Management function<\/span> been formally established?<\/li>\r\n \t
                            • Is there a Data Quality<\/span> Management Approach in place?<\/li>\r\n \t
                            • Are the Data Quality<\/span> Management Approach and roadmap aligned to the Data Management Strategy?<\/li>\r\n \t
                            • Have innovative technologies such as Artificial Intelligence been considered as part of the Data Quality<\/span> Management process<\/span> and infrastructure?<\/li>\r\n \t
                            • Has the Data Quality<\/span> Management function<\/span> been formally communicated to business, technology, operations, finance, and risk stakeholders?<\/li>\r\n \t
                            • Has executive management demonstrated its support?<\/li>\r\n \t
                            • Has authority been granted to the Data Quality<\/span> Management function<\/span> to implement and enforce best practice via policy<\/span> and standards?<\/li>\r\n \t
                            • Has authority been communicated to stakeholders?<\/li>\r\n \t
                            • Is there a functional partnership in place with Internal Audit?<\/li>\r\n \t
                            • Have the integration impacts been reviewed?<\/li>\r\n<\/ul>\r\n
                              Artifacts<\/h5>\r\n
                                \r\n \t
                              • Data Quality<\/span> Management Approach & Plan<\/li>\r\n \t
                              • Communication of specific support from executive management with distribution lists<\/li>\r\n<\/ul>\r\n
                                Scoring<\/h5>\r\n
                                \r\n
                                \r\n
                                \r\n
                                \r\n\r\nNot Initiated\r\n\r\n<\/div>\r\n\r\n
                                \n\nNo formal Data Quality<\/span> Management Approach exists.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                \r\n
                                \r\n\r\nConceptual\r\n\r\n<\/div>\r\n\r\n
                                \n\nNo formal Data Quality<\/span> Management Approach exists, but the need is recognized, and the development is being discussed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                \r\n
                                \r\n\r\nDevelopmental\r\n\r\n<\/div>\r\n\r\n
                                \n\nThe formal Data Quality<\/span> Management Approach is being developed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                \r\n
                                \r\n\r\nDefined\r\n\r\n<\/div>\r\n\r\n
                                \n\nThe formal Data Quality<\/span> Management Approach is defined and has been validated by the directly involved stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                \r\n
                                \r\n\r\nAchieved\r\n\r\n<\/div>\r\n\r\n
                                \n\nThe formal Data Quality<\/span> Management Approach is established and understood across the organization and is being followed by the stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                \r\n
                                \r\n\r\nEnhanced\r\n\r\n<\/div>\r\n\r\n
                                \n\nThe formal Data Quality<\/span> Management Approach is established as part of business-as-usual practice with a continuous improvement routine.\n\nThe Approach is reviewed and updated regularly.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n<\/div>\r\n<\/div>\r\n\r\n
                                \r\n\r\n

                                5.1.2 Data Quality Management Roles and Responsibilities<\/h3>\r\n<\/div>\r\n\r\n
                                \r\n
                                \r\n
                                Description<\/h5>\nData Quality<\/span> Management requires collaboration from a network of individuals within the organization, including but not limited to, data stewards and subject matter experts, to ensure accurate data is properly captured, processed, and delivered. Accountable parties must be identified, and the roles and responsibilities must be clearly communicated.\n
                                Objectives<\/h5>\r\n
                                  \r\n \t
                                • Define and communicate the roles and responsibilities of the Data Quality<\/span> Management function<\/span> throughout the data life cycle.<\/li>\r\n \t
                                • Proper staffing is identified and responsibility understood in the Data Quality<\/span> Management function<\/span>.<\/li>\r\n<\/ul>\r\n
                                  Advice<\/h5>\nData Quality<\/span> Management involves numerous stakeholders who are responsible for data requirement capture, data profiling<\/span>, remediation, definitions, metadata<\/span>, transformation, root cause analysis, and coordination across the full data ecosystem and the data life cycle. These efforts involve the assignment and empowerment of owners, stewards, curators, custodians and others. These accountable parties need to be at the right levels of seniority as well as understand all the internal processes associated with Data Quality<\/span> Management.\n\nWith the addition of a data ethics review in the Data Quality<\/span> Management process<\/span>, subject matter expertise will be required either through the addition of experts or appropriate training of Data Quality<\/span> Management resources. Similarly, to the extent that AI is used to support the Data Quality<\/span> Management process<\/span>, additional skills will need to be added or developed within the stakeholders.\n
                                  Questions<\/h5>\r\n
                                    \r\n \t
                                  • Is the Data Quality<\/span> Management function<\/span> appropriately staffed?<\/li>\r\n \t
                                  • Have the roles and responsibilities of the Data Quality<\/span> Management function<\/span> been defined, documented and socialized?<\/li>\r\n<\/ul>\r\n
                                    Artifacts<\/h5>\r\n
                                      \r\n \t
                                    • RACI matrix<\/span> or other evidence of accountability assignment<\/li>\r\n \t
                                    • Description of the roles and responsibilities of the Data Quality<\/span> Management function<\/span><\/li>\r\n \t
                                    • List of stakeholder<\/span> assignments and bi-directional communication<\/li>\r\n \t
                                    • Gap analysis of skills needed and in place<\/li>\r\n<\/ul>\r\n
                                      Scoring<\/h5>\r\n
                                      \r\n
                                      \r\n
                                      \r\n
                                      \r\n\r\nNot Initiated\r\n\r\n<\/div>\r\n\r\n
                                      \n\nNo formal Data Quality<\/span> Management roles and responsibilities exist.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                      \r\n
                                      \r\n\r\nConceptual\r\n\r\n<\/div>\r\n\r\n
                                      \n\nNo formal Data Quality<\/span> Management roles and responsibilities exist, but the need is recognized, and the development is being discussed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                      \r\n
                                      \r\n\r\nDevelopmental\r\n\r\n<\/div>\r\n\r\n
                                      \n\nThe formal Data Quality<\/span> Management roles and responsibilities are being developed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                      \r\n
                                      \r\n\r\nDefined\r\n\r\n<\/div>\r\n\r\n
                                      \n\nThe Data Quality<\/span> Management roles & responsibilities are defined and have been validated by the directly involved stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                      \r\n
                                      \r\n\r\nAchieved\r\n\r\n<\/div>\r\n\r\n
                                      \n\nThe Data Quality<\/span> Management roles and responsibilities are established, recognized and filled by stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                      \r\n
                                      \r\n\r\nEnhanced\r\n\r\n<\/div>\r\n\r\n
                                      \n\nThe Data Quality<\/span> Management roles and responsibilities are established as part of business-as-usual practice with a continuous improvement routine.\n\nThe roles and responsibilities are reviewed regularly.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n<\/div>\r\n<\/div>\r\n\r\n
                                      \r\n\r\n

                                      5.1.3 Data Quality Management Processes<\/h3>\r\n<\/div>\r\n\r\n
                                      \r\n
                                      \r\n
                                      Description<\/h5>\nFormal processes must be established for the activities of the Data Quality<\/span> Management function<\/span>. These processes align with the Data Management policy<\/span> and standards of the organization and include procedures, tools and routines. The routines are required for steady-state operations.\n
                                      Objectives<\/h5>\r\n
                                        \r\n \t
                                      • Establish formal Data Quality<\/span> Management processes in alignment with the Data Management policy<\/span> and standards.<\/li>\r\n \t
                                      • Ensure processes are engaged and aligned to business, operational, and audit stakeholders.<\/li>\r\n \t
                                      • Integrate the Data Quality<\/span> Management processes into the overall end-to-end processes of the Data Management initiative.<\/li>\r\n \t
                                      • Data Quality<\/span> Management processes are auditable.<\/li>\r\n<\/ul>\r\n
                                        Advice<\/h5>\nThe Data Quality<\/span> Management subject matter experts should work with the business process<\/span> design and optimization service(s) within the Data Management Program team. Together they will create and monitor the implementation of the Data Quality<\/span> Management processes in alignment with the end-to-end process<\/span> across the full Data Management initiative. Data Quality<\/span> Management processes must be implemented to streamline and support organization requirements for review and audit. Audit review processes need to be established and, where appropriate, supported by reporting capabilities to streamline the process<\/span>.\n\nThe Data Quality<\/span> Management process<\/span> design should include the requirements for ethical review as part of determining the data is fit-for-purpose. The design should also incorporate Artificial Intelligence into the process<\/span> if included in the Data Quality<\/span> Management strategy and approach.\n
                                        Questions<\/h5>\r\n
                                          \r\n \t
                                        • Have formal processes been defined and implemented?<\/li>\r\n \t
                                        • Are the procedures, tools and routines in place for implementing the processes?<\/li>\r\n \t
                                        • Has the review of data ethics been included within the defined processes?<\/li>\r\n \t
                                        • Are Data Quality<\/span> Management activities part of the normal operational routine of stakeholders?<\/li>\r\n \t
                                        • Are there standing meetings, planning sessions and regular communication about data initiatives?<\/li>\r\n<\/ul>\r\n
                                          Artifacts<\/h5>\r\n
                                            \r\n \t
                                          • Process<\/span> design artifacts, procedure<\/span> guides, and published routines<\/li>\r\n \t
                                          • Process<\/span> performance metrics reports<\/li>\r\n \t
                                          • Meeting minutes, status reports, and Data Management Program announcements<\/li>\r\n<\/ul>\r\n
                                            Scoring<\/h5>\r\n
                                            \r\n
                                            \r\n
                                            \r\n
                                            \r\n\r\nNot Initiated\r\n\r\n<\/div>\r\n\r\n
                                            \n\nNo formal Data Quality<\/span> Management operational processes exist.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                            \r\n
                                            \r\n\r\nConceptual\r\n\r\n<\/div>\r\n\r\n
                                            \n\nNo formal Data Quality<\/span> Management operational processes exist, but the need is recognized, and the development is being discussed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                            \r\n
                                            \r\n\r\nDevelopmental\r\n\r\n<\/div>\r\n\r\n
                                            \n\nData Quality<\/span> Management operational processes are being developed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                            \r\n
                                            \r\n\r\nDefined\r\n\r\n<\/div>\r\n\r\n
                                            \n\nThe Data Quality<\/span> Management operational processes are defined and have been validated by the directly involved stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                            \r\n
                                            \r\n\r\nAchieved\r\n\r\n<\/div>\r\n\r\n
                                            \n\nThe Data Quality<\/span> Management operational processes are established and recognized and used by stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                            \r\n
                                            \r\n\r\nEnhanced\r\n\r\n<\/div>\r\n\r\n
                                            \n\nThe Data Quality<\/span> Management operational processes are established as part of business-as-usual practice with a continuous improvement routine.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n<\/div>\r\n<\/div>\r\n\r\n
                                            \r\n\r\n

                                            5.2 Data is Profiled and Measured<\/h3>\r\n<\/div>\r\n
                                            \r\n
                                            \n\nProfiling<\/span> and measuring the data includes:\n
                                              \r\n \t
                                            • Prioritizing the data in scope based on criticality and materiality<\/span><\/li>\r\n \t
                                            • Measuring that the data is fit-for-purpose<\/li>\r\n \t
                                            • Defining and testing data quality<\/span> rules based on business rules to validate fit-for-use<\/li>\r\n<\/ul>\r\n\r\n\r\n<\/div>\r\n<\/div>\r\n\r\n
                                              \r\n\r\n

                                              5.2.1 Data Identification and Prioritization<\/h3>\r\n<\/div>\r\n\r\n
                                              \r\n
                                              \r\n
                                              Description<\/h5>\nThe data in scope as defined by the business objectives must be prioritized based on its criticality and materiality<\/span> to the data consumer<\/span> and business process<\/span>.\n
                                              Objectives<\/h5>\r\n
                                                \r\n \t
                                              • Define a process<\/span> for prioritizing in-scope data.<\/li>\r\n \t
                                              • Identify the scope of data subject<\/span> to Data Quality<\/span> Management, both current and historical.<\/li>\r\n \t
                                              • Prioritize the scope of data in alignment with the DS and business priorities.<\/li>\r\n<\/ul>\r\n
                                                Advice<\/h5>\nAn organization may establish data prioritization tiers. The Data Management policy<\/span> and standards should define levels of data control to apply to each prioritization tier. The highest-level tier is a critical data element<\/span>. Designated critical data elements receive the highest level of control to ensure the quality of these attributes is maintained. Critical data element<\/span> designation is a controlled process<\/span>, typically captured in data classifications, to achieve agreement between the data producer<\/span> and data consumer<\/span>.\n
                                                Questions<\/h5>\r\n
                                                  \r\n \t
                                                • Has the process<\/span> to prioritize data been defined?<\/li>\r\n \t
                                                • Has the scope of data subject<\/span> to Data Quality<\/span> Management been identified, prioritized and verified?<\/li>\r\n<\/ul>\r\n
                                                  Artifacts<\/h5>\r\n
                                                    \r\n \t
                                                  • Prioritized critical data element<\/span> inventory related to data domains<\/li>\r\n \t
                                                  • Bi-directional communication about the inventories and data quality<\/span> expectations<\/li>\r\n<\/ul>\r\n
                                                    Scoring<\/h5>\r\n
                                                    \r\n
                                                    \r\n
                                                    \r\n
                                                    \r\n\r\nNot Initiated\r\n\r\n<\/div>\r\n\r\n
                                                    \n\nNo formal scope of data subject<\/span> to Data Quality<\/span> Management has been identified or prioritized.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                    \r\n
                                                    \r\n\r\nConceptual\r\n\r\n<\/div>\r\n\r\n
                                                    \n\nNo formal scope of data subject<\/span> to Data Quality<\/span> Management exists but the need for critical data elements is being discussed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                    \r\n
                                                    \r\n\r\nDevelopmental\r\n\r\n<\/div>\r\n\r\n
                                                    \n\nThe scope of data subject<\/span> to Data Quality<\/span> Management is being identified and shared with stakeholders.\n\nCritical data elements are being defined.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                    \r\n
                                                    \r\n\r\nDefined\r\n\r\n<\/div>\r\n\r\n
                                                    \n\nThe scope of data subject<\/span> to Data Quality<\/span> Management is prioritized and aligned with both strategy and business priorities.\n\nCritical data elements are verified.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                    \r\n
                                                    \r\n\r\nAchieved\r\n\r\n<\/div>\r\n\r\n
                                                    \n\nThe scope of data subject<\/span> to Data Quality<\/span> Management is approved.\n\nCritical data elements are designated and actively maintained.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                    \r\n
                                                    \r\n\r\nEnhanced\r\n\r\n<\/div>\r\n\r\n
                                                    \n\nThe process<\/span> to identify and prioritize all relevant data has a routine in place to identify opportunities for continuous improvement.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                    \r\n\r\n

                                                    5.2.2 Data Profiling<\/h3>\r\n<\/div>\r\n\r\n
                                                    \r\n
                                                    \r\n
                                                    Description<\/h5>\nThe in-scope data must be profiled to determine the full spectrum of data quality dimensions<\/span> for your organization (accuracy<\/span>, completeness<\/span>, coverage<\/span>, conformity<\/span>, consistency<\/span>, timeliness<\/span>, uniqueness<\/span>). Metadata<\/span> must also be reviewed to ensure the description and intended use of data is properly defined.\n
                                                    Objectives<\/h5>\r\n
                                                      \r\n \t
                                                    • Define a process<\/span> for profiling<\/span>, analyzing, and grading data.<\/li>\r\n \t
                                                    • Profile, analyze and grade in-scope data.<\/li>\r\n \t
                                                    • Capture profiling<\/span> results on a routine basis.<\/li>\r\n \t
                                                    • Report profiling<\/span> results to business, data, and technology stakeholders.<\/li>\r\n<\/ul>\r\n
                                                      Advice<\/h5>\nThe Data Quality<\/span> Management function<\/span> is to establish that the data is fit-for-purpose and can be trusted. Data profiling<\/span> creates a quality benchmark for the organization. Evidence of data profiling<\/span> will be expected in any Internal Audit review or regulatory examination. Data needs to be assessed against both fit-for-purpose criteria and the data quality dimensions<\/span>. Certain types of data such as time-series data, need to be evaluated against additional criteria like gaps, spikes and abnormalities.\n\nThe primary stakeholders involved in this process<\/span> are the data producer<\/span> and data consumer<\/span>. Ultimately, quality is defined by the business process<\/span> requirements of the data consumer<\/span> and should be formally agreed to by the data producer<\/span>.\n\nMetrics are used to track Data Quality<\/span> and drive data remediation efforts. Control points along the data supply chain capture Data Quality<\/span> metrics that are used to produce Data Quality<\/span> dashboards. The requirements of the data consumer<\/span> are used to establish quality thresholds for the data. These thresholds permit the grading of the data as to the defined levels of acceptable Data Quality<\/span> based on the minimal requirements of specific data consumer<\/span>.\n\nCreating a standard<\/span> and automated process<\/span> for routinely executing the quality metrics and reporting the results is critical to meet the time constraints of the data supply chain.\n\nA mechanism for executing Data Quality<\/span> rules and generating outcome reports is required to support the data profiling<\/span>, analyzing and grading process<\/span>. The use of Artificial Intelligence may assist in the process<\/span>.\n
                                                      Questions<\/h5>\r\n
                                                        \r\n \t
                                                      • Has the in-scope data been profiled, analyzed and graded?<\/li>\r\n \t
                                                      • Is Data Quality<\/span> profiled against business logic rules as well as for reasonableness against statistical expectations?<\/li>\r\n \t
                                                      • Are the right business, operational, analytical, data, and technical stakeholders involved in the process<\/span>?<\/li>\r\n \t
                                                      • Are innovative technologies such as AI used to identify and suggest rules or perform cleansing operations as part of the process<\/span>?<\/li>\r\n \t
                                                      • Are standard<\/span> criteria for measuring data quality<\/span> defined and verified?<\/li>\r\n \t
                                                      • Are metrics being collected and reported on a routine basis?<\/li>\r\n \t
                                                      • Are the results of data measurement and grading captured as metadata<\/span> in a data catalog?<\/li>\r\n \t
                                                      • Are periodic reviews of data quality<\/span> and business rules being performed for relevance?<\/li>\r\n<\/ul>\r\n
                                                        Artifacts<\/h5>\r\n
                                                          \r\n \t
                                                        • Business rules and data profiling<\/span> measurement criteria<\/li>\r\n \t
                                                        • Data Quality analysis<\/span> results<\/li>\r\n \t
                                                        • Mechanism for assigning and reporting grades for Data Quality<\/span><\/li>\r\n \t
                                                        • Data Quality<\/span> metric reports, dashboards, heat maps, and other forms of output<\/li>\r\n \t
                                                        • List of stakeholders and evidence of bi-directional communication<\/li>\r\n<\/ul>\r\n
                                                          Scoring<\/h5>\r\n
                                                          \r\n
                                                          \r\n
                                                          \r\n
                                                          \r\n\r\nNot Initiated\r\n\r\n<\/div>\r\n\r\n
                                                          \n\nData is not profiled, analyzed or graded for the purpose of assessing Data Quality<\/span>.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                          \r\n
                                                          \r\n\r\nConceptual\r\n\r\n<\/div>\r\n\r\n
                                                          \n\nData is not profiled, analyzed or graded for the purpose of assessing Data Quality<\/span>, but the need is recognized, and the development is being discussed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                          \r\n
                                                          \r\n\r\nDevelopmental\r\n\r\n<\/div>\r\n\r\n
                                                          \n\nData profiling<\/span>, analysis and grading, for the purpose of assessing Data Quality<\/span>, is being developed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                          \r\n
                                                          \r\n\r\nDefined\r\n\r\n<\/div>\r\n\r\n
                                                          \n\nData profiling<\/span>, analysis, and grading, for the purpose of assessing Data Quality<\/span>, has been defined and validated by directly involved stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                          \r\n
                                                          \r\n\r\nAchieved\r\n\r\n<\/div>\r\n\r\n
                                                          \n\nData profiling<\/span>, analysis and grading, for the purpose of assessing Data Quality<\/span>, is established and conducted by stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                          \r\n
                                                          \r\n\r\nEnhanced\r\n\r\n<\/div>\r\n\r\n
                                                          \n\nData profiling<\/span>, analysis and grading, for the purpose of assessing Data Quality<\/span>, is established and automated as part of business-as-usual practice with a continuous improvement routine.\n\nIt is recognized as the normal way of working.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                          \r\n\r\n

                                                          5.2.3 Data Quality Rules<\/h3>\r\n<\/div>\r\n\r\n
                                                          \r\n
                                                          \r\n
                                                          Description<\/h5>\nData quality<\/span> rules based on business rules must be defined and tested to confidently validate the data is fit-for-use throughout its life cycle.\n
                                                          Objectives<\/h5>\r\n
                                                            \r\n \t
                                                          • Define a process<\/span> for the development of data quality<\/span> rules across the data life cycle.<\/li>\r\n \t
                                                          • Define business rules which can be translated into data quality<\/span> rules and used to measure the quality of data.<\/li>\r\n \t
                                                          • Define a process<\/span> for the testing of data quality<\/span> rules.<\/li>\r\n \t
                                                          • Establish an environment and toolset for the running and testing of rules.<\/li>\r\n \t
                                                          • Socialize Data Quality<\/span> rules and test results with stakeholders.<\/li>\r\n<\/ul>\r\n
                                                            Advice<\/h5>\nBusiness rules are the basis for developing data quality<\/span> rules necessary to quantify the quality of the data. A partnership with business subject matter experts is crucial to being able to define quality data. The data quality dimensions<\/span> establish a range of potential rules that may be needed to determine overall Data Quality<\/span>. A critical part of defining quality rules is to test the outcome of the rule. Testing is an iterative activity during the design of an individual rule. Testing and re-testing with each rule refinement is an essential activity for identification of the range of rules across the data quality dimensions<\/span>. These dimensions are required for the data quality<\/span> ruleset to accurately measure quality. Various changes can occur in the data life cycle that necessitate retesting of data quality<\/span> rules, such as the introduction of new data into an existing process<\/span> or changes in data structure. Understanding these changes is essential for determining when data quality<\/span> re-testing is required.\n\nData quality<\/span> rules should be developed to test the various dimensions of quality<\/span>. Not all dimensions are applied to the testing scenario. Care should be taken to ensure as many dimensions have rules as required. There is an art and a science to writing quality rules. The rules and the range of rules will evolve over time. As new quality defects surface, they will guide the design of new rules to detect those issues in the future. A mature data quality rule<\/span> set is a coveted asset of an organization.\n\nData quality<\/span> rules require a testing environment, typically done in a development where rules can be established, tested, and results reviewed for successful outcomes. Additionally, the proper technical infrastructure to write, store, run and analyze rules is needed.\n\nThe skill set required to test rules may include business process<\/span> subject matter expertise, Data Quality<\/span> management expertise, and technical infrastructure and coding expertise. Make sure you assess the skills and available resources carefully as this range of skills may not be available through a single individual.\n
                                                            Questions<\/h5>\r\n
                                                              \r\n \t
                                                            • Is there a defined process<\/span> for the design, testing, and deployment of data quality<\/span> rules?<\/li>\r\n \t
                                                            • Is there a library of business rules that are associated with data sets or products?<\/li>\r\n \t
                                                            • Are the data quality<\/span> rules based on defined business rules?<\/li>\r\n \t
                                                            • Is there a data sandbox and appropriate tools for running data quality rule<\/span> tests?<\/li>\r\n \t
                                                            • How is stakeholder<\/span> feedback and approval captured when running and evaluating data quality<\/span> tests?<\/li>\r\n \t
                                                            • Have the stakeholders validated that the range of data quality dimensions<\/span> applied in the rule set is adequate to determine the Data Quality<\/span>?<\/li>\r\n<\/ul>\r\n
                                                              Artifacts<\/h5>\r\n
                                                                \r\n \t
                                                              • Process<\/span> design artifacts, procedure<\/span> guides, and published routines<\/li>\r\n \t
                                                              • Documented data quality dimensions<\/span><\/li>\r\n \t
                                                              • Criteria used to evaluate Data Quality<\/span><\/li>\r\n \t
                                                              • Data quality<\/span> rules repository<\/li>\r\n \t
                                                              • Data quality<\/span> rules recorded as metadata<\/span><\/li>\r\n \t
                                                              • Testing result reports and dashboards<\/li>\r\n \t
                                                              • Data Quality<\/span> rule-deployment process<\/span><\/li>\r\n<\/ul>\r\n
                                                                Scoring<\/h5>\r\n
                                                                \r\n
                                                                \r\n
                                                                \r\n
                                                                \r\n\r\nNot Initiated\r\n\r\n<\/div>\r\n\r\n
                                                                \n\nNo Data Quality<\/span> rules or testing capability exist.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                \r\n
                                                                \r\n\r\nConceptual\r\n\r\n<\/div>\r\n\r\n
                                                                \n\nNo Data Quality<\/span> rules or testing capability exist, but the need is recognized, and the development is being discussed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                \r\n
                                                                \r\n\r\nDevelopmental\r\n\r\n<\/div>\r\n\r\n
                                                                \n\nData Quality<\/span> rules and testing capability are being developed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                \r\n
                                                                \r\n\r\nDefined\r\n\r\n<\/div>\r\n\r\n
                                                                \n\nData Quality<\/span> rules and testing capability have been defined and validated by directly involved stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                \r\n
                                                                \r\n\r\nAchieved\r\n\r\n<\/div>\r\n\r\n
                                                                \n\nData Quality<\/span> rules and testing capability are established, recognized and used by stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                \r\n
                                                                \r\n\r\nEnhanced\r\n\r\n<\/div>\r\n\r\n
                                                                \n\nData Quality<\/span> rules and testing capability are established as part of business-as-usual practice with a continuous improvement routine.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                \r\n\r\n

                                                                5.3 Data Quality Maintenance<\/h3>\r\n<\/div>\r\n
                                                                \r\n
                                                                \n\nMaintaining the data quality<\/span> includes:\n
                                                                  \r\n \t
                                                                • Implementing data quality<\/span> control points<\/li>\r\n \t
                                                                • Capturing Data Quality<\/span> metrics to identify defective data<\/li>\r\n \t
                                                                • Continuous monitoring of the data<\/li>\r\n<\/ul>\r\n\r\n\r\n<\/div>\r\n<\/div>\r\n\r\n
                                                                  \r\n\r\n

                                                                  5.3.1 Data Quality Controls<\/h3>\r\n<\/div>\r\n\r\n
                                                                  \r\n
                                                                  \r\n
                                                                  Description<\/h5>\r\nData control points must be developed to quantitatively assess the quality of data as it flows through business and technology processes.\r\n
                                                                  Objectives<\/h5>\r\n
                                                                    \r\n \t
                                                                  • Establish a process<\/span> to define Data Quality<\/span> control points.<\/li>\r\n \t
                                                                  • Put Data Quality<\/span> control points in place and bring them to a fully operational state along the data supply chain.<\/li>\r\n \t
                                                                  • Record Data Quality<\/span> controls as metadata<\/span>.<\/li>\r\n<\/ul>\r\n
                                                                    Advice<\/h5>\nData Quality<\/span> is governed by developing control points along the data supply chain. Data Quality<\/span> control points need to be applied at the point of data entry into the organization, the point of entry into the consuming application, and when data moves and transforms along the supply chain. Data Quality<\/span> controls include the implementation of business rules, establishing workflows, setting Data Quality<\/span> tolerances and monitoring data movement.\n
                                                                    Questions<\/h5>\r\n
                                                                      \r\n \t
                                                                    • Are control points defined, verified and documented?<\/li>\r\n \t
                                                                    • Are business rules defined, verified, documented and approved?<\/li>\r\n \t
                                                                    • Are business process<\/span> flows defined and the way they handle exceptions verified?<\/li>\r\n \t
                                                                    • Are control points, business rules and process<\/span> flow operational?<\/li>\r\n \t
                                                                    • Are controls reviewed and updated, as necessary, regularly?<\/li>\r\n<\/ul>\r\n
                                                                      Artifacts<\/h5>\r\n
                                                                        \r\n \t
                                                                      • Documentation of control points, business rules and process<\/span> flows<\/li>\r\n \t
                                                                      • Control process<\/span> review and sign-off<\/li>\r\n<\/ul>\r\n
                                                                        Scoring<\/h5>\r\n
                                                                        \r\n
                                                                        \r\n
                                                                        \r\n
                                                                        \r\n\r\nNot Initiated\r\n\r\n<\/div>\r\n\r\n
                                                                        \n\nNo Data Quality<\/span> control points are defined.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                        \r\n
                                                                        \r\n\r\nConceptual\r\n\r\n<\/div>\r\n\r\n
                                                                        \n\nNo Data Quality<\/span> control points are defined, but the need is recognized, and the development is being discussed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                        \r\n
                                                                        \r\n\r\nDevelopmental\r\n\r\n<\/div>\r\n\r\n
                                                                        \n\nData Quality<\/span> control points are being developed.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                        \r\n
                                                                        \r\n\r\nDefined\r\n\r\n<\/div>\r\n\r\n
                                                                        \n\nData Quality<\/span> control points are defined and validated by directly involved stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                        \r\n
                                                                        \r\n\r\nAchieved\r\n\r\n<\/div>\r\n\r\n
                                                                        \n\nData Quality<\/span> control points are established and recognized by stakeholders.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                        \r\n
                                                                        \r\n\r\nEnhanced\r\n\r\n<\/div>\r\n\r\n
                                                                        \n\nData Quality<\/span> control points are established as part of business-as-usual practice with a continuous improvement routine.\n\nControl points are reviewed for relevance and accuracy<\/span> regularly.\n\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n\r\n\r\n\r\n<\/div>\r\n\r\n\r\n<\/div>\r\n\r\n
                                                                        \r\n\r\n

                                                                        5.3.2 Data Quality Issues Management<\/h3>\r\n<\/div>\r\n\r\n
                                                                        \r\n
                                                                        \r\n
                                                                        Description<\/h5>\nControl points along the data supply chain capture Data Quality<\/span> metrics that are used to produce Data Quality<\/span> dashboards which are used to identify defective data. The Data Quality<\/span> defects must be part of the issue management routine of the Data Management initiative. The Data Quality<\/span> issue management process<\/span> must track an issue to resolution and provide continuous stakeholder<\/span> communication.\n
                                                                        Objectives<\/h5>\r\n
                                                                          \r\n \t
                                                                        • Manage data quality<\/span> issues to resolution.<\/li>\r\n \t
                                                                        • Drive and prioritize remediation efforts using Data Quality<\/span> metric reporting.<\/li>\r\n \t
                                                                        • Establish issue-management reporting routine and infrastructure.<\/li>\r\n<\/ul>\r\n
                                                                          Advice<\/h5>\nStakeholder<\/span> engagement, inclusive of the data consumer<\/span> and data producer<\/span>, is critical for successful and strategic remediation of data issues. The data issues need to be managed through all stages of resolution. These stages include defect triage, prioritization, root-cause analysis, root-cause fix, and remediation of defective data. Remediation of data issues can include permanent solutions through to tactical fixes to enable a critical process<\/span> to continue to operate. It is important to note that best practice is permanent solutions that address root causes. Communication with all stakeholders throughout this process<\/span> is critical. Stakeholders must be made aware of the defective data and its impact on business processes and data consumption. The appropriate stakeholders may need to participate in the analysis and determination of an acceptable resolution.\n\nImportant tools to support the resolution process<\/span> are an issue log and a status tracking system. The link to the issue record should be part of the metadata<\/span> for all instances of defective data. This record will communicate to all users across an organization and can be used to help minimize duplication of effort when an issue is uncovered at multiple points along the data supply chain.\n\nOften, particularly in the early stages of the Data Management initiative, the volume of defective data may be greater than the resources required to resolve the data quality<\/span> issues. Documenting the prioritization process<\/span> in the Data Quality<\/span> issue log, even when it results in a backlog, demonstrates that these issues were known and evaluated, rather than being discovered during a future audit.\n
                                                                          Questions<\/h5>\r\n