{"id":5080,"date":"2025-11-03T13:39:56","date_gmt":"2025-11-03T18:39:56","guid":{"rendered":"https:\/\/staging.dcamportal.org\/?p=5080"},"modified":"2026-02-24T15:14:32","modified_gmt":"2026-02-24T20:14:32","slug":"dcam-v3-framework-beta-8-0-analytics-management","status":"publish","type":"post","link":"https:\/\/staging.dcamportal.org\/fr_ca\/dcam-v3-framework-8-analytics-management\/","title":{"rendered":"DCAM v3 Framework – 8.0 Analytics Management"},"content":{"rendered":"
\r\n\r\n\t
\r\n\r\n
\r\n\r\n\r\n
\r\n\r\n
\r\n\r\n \r\n <\/div>\r\n\r\n <\/div> \r\n\r\n \r\n\r\n

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

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

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

Introduction<\/h3>\r\n\r\n

The Analytics Management component, the eighth element of the DCAM<\/span> framework, plays a dual role within data management processes by acting as both a data creator and consumer. As a data creator, Analytics Management must adhere to the principles set out by the first seven components of DCAM<\/span>; which define the core capabilities necessary for effective Data Management. This ensures consistency<\/span> and accuracy<\/span> in the way data is consumed, and insights are generated, supporting the organization's decision-making processes. To assist analytics professionals, there must be clear processes that govern how the Analytics Management function<\/span> is structured and managed. These processes must outline the necessary governance frameworks for designing, executing, validating, and delivering models, including those related to Large Language Models, to meet organizational needs.<\/p>\r\n\r\n

The Analytics Management component, the eighth element of the DCAM<\/span> framework, plays a dual role within data management processes by acting as both a data creator and consumer. As a data creator, Analytics Management must adhere to the principles set out by the first seven components of DCAM<\/span>; which define the core capabilities necessary for effective Data Management. This ensures consistency<\/span> and accuracy<\/span> in the way data is consumed, and insights are generated, supporting the organization's decision-making processes. To assist analytics professionals, there must be clear processes that govern how the Analytics Management function<\/span> is structured and managed. These processes must outline the necessary governance frameworks for designing, executing, validating, and delivering models, including those related to Large Language Models, to meet organizational needs.<\/p>\r\n\r\n

The primary objective of Analytics Management is to formalize how analytics activities are structured, governed, and executed within an organization. This ensures that these activities align with the broader Data Management practices. The organizational structure, whether the Analytics teams are centralized or distributed, will depend on the organization's culture. However, a coherent framework for analytics can enhance synergies, maximize efficiencies, and improve overall effectiveness when aligned with a comprehensive Analytics Strategy.<\/p>\r\n\r\n\r\n

Definition<\/h3>\r\n\r\n

The Analytics Management<\/b> component is an integral part of Data Management. It is a set of capabilities required to structure and manage the analytics activities of an organization. The capabilities align Analytics Management with Data Management in support of business and functional priorities. They address the culture, skills, platform, and governance required to enable the organization to obtain business value from analytics.<\/p>\r\n\r\n

The Analytics component outlines the necessary capabilities for success but does not address the different organizational structures that may exist, nor will it delve into the factors to consider when choosing the most suitable structure. Each organization will need to design an appropriate structure to support their analytical needs and capabilities based on their unique resources and capacity.<\/p>\r\n\r\n\r\n

Scope<\/h3>\r\n\r\n
    \r\n\r\n
  • Develop an Analytics Strategy that aligns with the overarching Business Strategy.<\/li>\r\n
  • Ensure the Analytics Strategy is aligned with the Data Management Strategy.<\/li>\r\n
  • Establish the Analytics Management function<\/span>.<\/li>\r\n
  • Ensure clear accountability for the analytics created and for their uses throughout the organization.<\/li>\r\n
  • Work with Data Management to align analytics with all DCAM<\/span> components, especially Data Architecture<\/span> and Data Quality<\/span> Management.<\/li>\r\n
  • Establish an analytics platform that provides flexibility and controls to meet the needs of the different stakeholder<\/span> roles in the Analytics Operating Model<\/span>.<\/li>\r\n
  • Design and deploy effective governance over the data analysis life cycle including tollgates for model<\/span> reviews, testing, approvals, documentation, release plans, monitoring, and regular review of processes, adjustments and retiring.<\/li>\r\n
  • Ensure that Analytics follows established guidelines for privacy, data ethics, regulatory compliance, model<\/span> bias, and model<\/span> explainability requirements and constraints.<\/li>\r\n
  • Manage the cultural change and education activities required to support the Analytics Strategy.<\/li>\r\n\r\n <\/ul>\r\n \r\n\r\n

    Value Proposition<\/h3>\r\n\r\n

    Organizations that excel in managing their Analytics functions and resources are adept at harnessing the power of analytical methods, advanced algorithms, and high-quality data. By improving the speed and efficiency of converting data into actionable insights, they not only enhance their ability to make quick, informed decisions but also ensure adherence to ethical and legal standards. This process<\/span> boosts overall performance and competitiveness.<\/p>\r\n\r\n\r\n

    Overview<\/h3>\r\n\r\n

    At its core, analytics is about enhancing decision-making. It goes beyond just crunching numbers; it's about extracting practical insights that can guide strategic decisions. This approach prioritizes the importance of actionable knowledge derived from data, rather than just the analytical process<\/span> itself.<\/p>\r\n\r\n

    Analytics-driven, real-time decision making has emerged as a crucial business differentiator, powered by swift advancements in technology, increased data accessibility and processing capabilities, and advanced analytical techniques that cater to stakeholder<\/span> requirements.<\/p>\r\n\r\n

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

    Diagram 8.1: Analytics Enablers & Stakeholders<\/p>\r\n\r\n

    Advances in technology and data include:<\/p>\r\n\r\n

      \r\n
    • NoSQL and graph database technologies enabling greater varieties and quantities of both structured and unstructured data to be accessed and processed efficiently.<\/li>\r\n
    • The falling costs of processing, coupled with faster processing speeds and the scalability of cloud computing, are making sophisticated analytics techniques more affordable and accessible.<\/li>\r\n
    • Availability of ‘“all-in-one” solutions democratize access to analytical techniques.<\/li>\r\n
    • Lower data storage costs and increased storage limits, increase the quantity of data available to analytics.<\/li>\r\n
    • New sources of data such as sensors, telematics, and satellite imagery, enable new data sets and new combinations of data sets to be analyzed.<\/li>\r\n
    • Advanced data visualization simplifies how people explore and interpret exceptionally large volumes of analytics results.<\/li>\r\n
    • Increased acceptance and use of Machine Learning in model<\/span> development has been enabled by an audience of professionals that have embraced and accepted Artificial Intelligence as a productivity enhancer and by the progress made towards a legal and regulatory framework to support it.<\/li>\r\n <\/ul>\r\n\r\n

      To successfully implement and manage their analytical capabilities in alignment with business objectives, organizations must follow the discipline and fundamental principles set forth in the DCAM<\/span> Analytics Management best practices, which encompass:<\/p>\r\n\r\n

        \r\n
      • An Analytics Strategy supporting business needs<\/b>. The growing volume and diversity of data available to organizations has expanded the potential applications of advanced analytics. As the demand for these analytics increases, it becomes crucial for organizations to prioritize projects based on their significance. To effectively leverage analytics in support of business objectives, organizations need a clear Analytics Strategy to deliver business needs supported by a Funding Model<\/span> established to sustain the effort.<\/li>\r\n
      • A clear Analytics Operating Model<\/span><\/b>. In many organizations, analytics practitioners often work more closely with business units than with traditional technology teams. It's essential for the organization to have a clear operating model<\/span> that ensures consistency<\/span> and efficiency in their activities. Those designing this model<\/span> must ensure it remains aligned with the stakeholders and maintains the necessary agility.<\/li>\r\n
      • Analytics Management aligned to Data Management<\/b>. In the absence of effective data management, a significant amount of an analytics practitioner’s time is spent manipulating, cleansing, and transforming data in preparation for the analytics. It is important for Analytics to be aligned with the Data Management initiative. Data Analytics Management should ensure that data is understood and that authoritative sources are used where these are available. Data Quality<\/span> Management will provide measures of data quality<\/span> that Analytics practitioners should reference and use to manage data quality<\/span> issues as they prepare data for their models.<\/li>\r\n
      • An Analytics Platform to meet comprehensive needs<\/b>. Not all analytics activities will involve the creation of models that, once successfully tested, will run as production processes or services. Some analytics will be one-time exercises to investigate historical issues or to address current, specific questions. There may also be experiments with new data sources or new analytical techniques. The appropriate analytical technique or approach will need to be selected for each problem statement to ensure the organization maximizes the benefits and considers the related. The platform that supports analytics must be designed to accommodate these different types of activity and the specific needs of different stakeholders.<\/li>\r\n
      • Analytics Governance and discipline<\/b>. Model<\/span> governance and transparency are essential for the responsible development and deployment of advanced analytics, including Machine Learning and Artificial Intelligence. Compliance with privacy regulations is crucial when models are operationalized. There is a growing need for explainability in model<\/span> decisions, which may also be a regulatory requirement, making it important to address these aspects early in the model<\/span> development process<\/span>. Additionally, identifying and controlling potential bias in training data is vital to prevent prejudicial outcomes against specific groups. Ongoing oversight is necessary for data encountered in production as well. Finally, adherence to the organization's Code of Data Ethics is critical to ensure that data usage within models is ethical and appropriate, guiding how organizations act on model-generated decisions and recommendations.<\/li>\r\n
      • Analytics Education to support Analytics Culture<\/b>. Effectively addressing the challenges of creating an analytics-driven organization requires significant changes in both culture and behavior. It is crucial for everyone involved to obtain the necessary understanding of the benefits that analytics can provide, and conversely, the possible negative repercussions that may result from its application. <\/li>\r\n <\/ul>\r\n\r\n\r\n

        Core Questions<\/h3>\r\n\r\n
          \r\n\r\n
        • Does the Analytics Strategy clearly articulate the role that Analytics will play in delivering the business strategy?<\/li>\r\n
        • Is the Analytics Strategy aligned with the Data and Data Management Strategy?<\/li>\r\n
        • Is there organizational alignment and support for the Analytics Strategy, operating model<\/span>, and funding approach? Are analytics activities prioritized according to business priorities?<\/li>\r\n
        • Is the value of analytics understood and measured?<\/li>\r\n
        • Are Data Management Governance and Analytics Management Governance aligned?<\/li>\r\n
        • Does the analytics platform support the needs of the Analytics practitioners?<\/li>\r\n
        • Are processes in place to control the release of analytics models into production?<\/li>\r\n
        • Is approval and release of models aligned with privacy and data ethics governance?<\/li>\r\n
        • Are there initiatives in place to address the cultural change and analytics practitioner education to enable Analytics success?<\/li>\r\n\r\n <\/ul>\r\n\r\n\r\n

          Core Artifacts<\/h3>\r\n\r\n
            \r\n\r\n
          • Analytics Strategy<\/li>\r\n
          • Analytics Classification System<\/li>\r\n
          • Analytics Operating Model<\/span><\/li>\r\n
          • Analytics Methodology<\/li>\r\n
          • Model<\/span> Documentation Standard<\/span><\/li>\r\n
          • Data Obfuscation Strategies<\/li>\r\n
          • Model<\/span> Testing, Approval, Release, Regular Reviews, Monitoring, Adjusting, and Sunsetting processes or procedures<\/li>\r\n
          • Cultural Behaviors Gap Analysis and Initiatives Backlog<\/li>\r\n
          • Analytics Skills Gap Analysis<\/li>\r\n\r\n <\/ul>\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
            \r\n \r\n \r\n

            8.1 Analytics Function<\/h3>\r\n <\/div>\r\n\r\n
            \r\n \r\n
            \r\n\r\n\r\n

            For an Analytics function<\/span> to be sustainable, it must be formally established and recognized. It must be approved by management and supported by an approved Funding Model<\/span> and an effective governance structure. Roles and responsibilities must be established, and an analytics methodology must be adopted.<\/p>\r\n\r\n \r\n \r\n\r\n <\/div>\r\n <\/div> \r\n\r\n\r\n\r\n

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

            8.1.1 Analytics Strategy and Approach<\/h3>\r\n <\/div>\r\n\r\n
            \r\n \r\n
            \r\n\r\n\r\n
            Description<\/h5>\r\n\r\n

            The Analytics Strategy must be defined based on the organization’s strategic objectives and goals while also considering existing analytics capabilities and advances. The role of the Analytics function<\/span> must be communicated to stakeholders and the Analytics Strategy should be formally empowered by senior management.<\/p>\r\n\r\n\r\n

            Objectives<\/h5>\r\n\r\n
              \r\n
            • Formally establish the organization’s Analytics strategy.<\/li>\r\n
            • Obtain executive management support for the Analytics strategy.<\/li>\r\n
            • Communicate the role of Analytics across the organization through formal organizational channels.<\/li>\r\n <\/ul>\r\n\r\n\r\n
              Advice<\/h5>\r\n\r\n

              The Analytics Strategy must be aligned to the business and operational objectives of the organization and aligned with the Data Management Strategy.<\/p>\r\n\r\n

              The strategy presents the vision for Analytics, addressing the organization, leadership, techniques, platform, processes, and culture. It describes how to address the gaps and realize the vision. The goal of developing the Analytics Strategy is to capture high-level objectives and translate them into achievable analytics solutions.<\/p>\r\n\r\n

              Achieving stakeholder<\/span> and executive buy-in is critical to the success of the strategy. A well-documented Analytics Strategy is both a statement of approach and a marketing document to present to stakeholders and executive management. Effective communication of the strategy is key to empowering a coordinated approach across the organization and avoiding inconsistencies and inefficiencies of different business areas taking different approaches.<\/p>\r\n\r\n\r\n

              Questions<\/h5>\r\n\r\n
                \r\n
              • Is there a formal, documented strategy and approach for Analytics?<\/li>\r\n
              • Have stakeholders been identified and involved in the creation and approval of the strategy?<\/li>\r\n
              • Are the Analytics Strategy and the vision of the Data Management Strategy aligned?<\/li>\r\n
              • Does the Analytics Strategy support the high-level objectives of the organization?<\/li>\r\n
              • Has executive management support for the strategy been obtained?<\/li>\r\n
              • Has the role of Analytics been formally communicated throughout the organization?<\/li>\r\n
              • Are the different types of analytics documented that are relevant to the organization?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                Artifacts<\/h5>\r\n\r\n
                  \r\n
                • Vision statement of the target state for Analytics and how it supports the organization’s objectives<\/li>\r\n
                • Prioritized approach to the initiatives required to realize the Analytics vision<\/li>\r\n
                • Documented alignment of the Analytics Strategy and vision of the Data Management Strategy<\/li>\r\n
                • List of stakeholders and evidence of bi-directional communication<\/li>\r\n
                • Evidence of formal communication of the strategy and approach<\/li>\r\n
                • Formal approval of the strategy by executive management<\/li>\r\n <\/ul>\r\n\r\n\r\n
                  Scoring<\/h5>\r\n \r\n
                  \r\n\r\n
                  \r\n \r\n
                  \r\n
                  \r\n

                  Not Initiated<\/p>\r\n <\/div> \r\n

                  \r\n

                  No formal Analytics Strategy exists.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                  \r\n
                  \r\n

                  Conceptual<\/p>\r\n <\/div> \r\n

                  \r\n

                  No formal Analytics Strategy exists, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                  \r\n
                  \r\n

                  Developmental<\/p>\r\n <\/div> \r\n

                  \r\n

                  The formal Analytics Strategy is being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                  \r\n
                  \r\n

                  Defined<\/p>\r\n <\/div> \r\n

                  \r\n

                  The formal Analytics Strategy is defined and has been validated by the stakeholders.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                  \r\n
                  \r\n

                  Achieved<\/p>\r\n <\/div> \r\n

                  \r\n

                  The formal Analytics Strategy is established and understood across the organization and is being followed by the stakeholders.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                  \r\n
                  \r\n

                  Enhanced<\/p>\r\n <\/div> \r\n

                  \r\n

                  The formal Analytics Strategy is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n

                  The strategy and approach are reviewed and updated at least annually.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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 \r\n \r\n

                  8.1.2 Analytics Operating Model<\/h3>\r\n <\/div> \r\n
                  \r\n \r\n
                  \r\n\r\n \r\n
                  Description<\/h5>\r\n\r\n

                  An operating model<\/span> is defined to describe how Analytics will be structured within the organization. It establishes the scope and coverage<\/span> of the different aspects and types of Analytics and designs how they should work together to serve the needs of the business and support the Data Management Strategy. The Analytics Operating Model<\/span> addresses analytics organization structure, role-level responsibilities, governance structure, funding processes, and technology platforms and is integrated with the Data Management Operating model<\/span>.<\/p>\r\n\r\n\r\n

                  Objectives<\/h5>\r\n\r\n
                    \r\n
                  • Define the Analytics team's structure within the organization, delineating the scope and coverage<\/span>.<\/li>\r\n
                  • Define the roles and responsibilities within each type of Analytics team.<\/li>\r\n
                  • Define the interrelationships between the various Analytics teams, between Analytics teams and the Data Management Program and data teams, and between Analytics teams and the business functions.<\/li>\r\n
                  • Align the Funding Model<\/span> with the overall funding approach of the organization.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                    Advice<\/h5>\r\n\r\n

                    The Analytics Operating Model<\/span> encompasses disciplines from different areas such as IT, business functions, and Analytics. It provides clarity on how these areas work together to provision the required data through analytical techniques and models, and to deliver the models into production. The Analytics Operating Model<\/span> designers must ensure it is informed by the business requirements and business architecture<\/span> and is kept current with developing input from business leaders.<\/p>\r\n\r\n

                    The Analytics Operating Model<\/span> clarifies the ownership of line-of-business Analytics, cross-business functions, and any overarching Analytics program. It is aligned with other operating models within the organization. If there is a strong culture of federated operating models, this should be embraced. Conversely, if there is a strong centralized operating model<\/span> culture, carefully consider the benefits before deviating from this approach.<\/p>\r\n\r\n

                    Best practices suggest that the ideal make-up of an Analytics team includes people with mathematical, analytical, and technical skills, as well as strong business acumen and project management experience. In practice, there are often multiple localized analytics teams within an organization, each with varying skill levels and delivery approaches. Whether Analytics is operated in a centralized, decentralized or federated model<\/span>, ensure processes and routines are in place to develop and maintain analytics best-practice standards consistently across the organization. The goal is to develop a discipline around Analytics that instills confidence and level-sets expectations in the user community. Analytics becomes proficient at providing solutions through organization-wide awareness, collaboration, sharing, and best practices.<\/p>\r\n

                    The Funding Model<\/span> must address all aspects of Analytics. Types of work beyond business-driven Analytics projects should be addressed. These include experimentation, foundational work, creation of re-usable data assets, ad-hoc high-priority analysis, and more. Funding of software licenses, platform, and infrastructure costs must be considered. When addressing people costs, consider the differentials in costs of Analytics specialists. Alignment with the overall funding approach of the organization may require the model<\/span> to distinguish between Analytics initiatives aligned with operating units and aspects of the operating model<\/span> that are not operating-unit specific.<\/p>\r\n\r\n

                    Ensure that Analytics is funded as a sustainable function<\/span>. Use the Funding Model<\/span> to distinguish aspects of funding that are discretionary from those that are non-discretionary. Stakeholder<\/span> involvement in the creation of the Funding Model<\/span> is critical to obtaining a financial commitment that can be sustained.<\/p>\r\n\r\n

                    Having buy-in from stakeholders is key if the Analytics organization is to be effective. Stakeholders should be involved throughout the creation of the operating model<\/span> to avoid misaligned expectations.<\/p>\r\n\r\n\r\n

                    Questions<\/h5>\r\n\r\n
                      \r\n
                    • Has the structure of the Analytics teams within the organization been defined?<\/li>\r\n
                    • Have the roles and responsibilities of each type of Analytics team been defined?<\/li>\r\n
                    • Do each of the team structures delineate the scope and coverage<\/span> of each?<\/li>\r\n
                    • Are the interactions of Analytics teams, the Data Management initiative, and the business defined?<\/li>\r\n
                    • Is the Funding Model<\/span> consistent with the established funding approaches and budget processes of the organization?<\/li>\r\n
                    • Does the Funding Model<\/span> address how Analytics will be funded in an ongoing, sustainable function<\/span>?<\/li>\r\n
                    • Are measurable benefits from Analytics initiatives used as support for the funding requirements?<\/li>\r\n
                    • Have stakeholders approved the operating model<\/span>?<\/li>\r\n
                    • Has the functional structure described in the operating model<\/span> been implemented?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                      Artifacts<\/h5>\r\n\r\n
                        \r\n
                      • Operating Model<\/span> Terms of Reference<\/li>\r\n
                      • Organizational structure of Analytics teams<\/li>\r\n
                      • Role definitions and RACIs (both between Analytics teams and between Analytics and other functions)<\/li>\r\n
                      • Process<\/span> models for Analytics, Data Management and business interactions<\/li>\r\n
                      • Documented Funding Model<\/span><\/li>\r\n
                      • A written process<\/span> to review, modify, and validate resource plans<\/li>\r\n
                      • Evidence of alignment with budget processes and organizational cycles<\/li>\r\n
                      • Documentation of measured benefits<\/li>\r\n
                      • Funding plans and budget allocation<\/li>\r\n
                      • List of stakeholders and evidence of bi-directional communication<\/li>\r\n
                      • Documented formal approval of the operating model<\/span> and provisions to review and refresh as needed<\/li>\r\n <\/ul>\r\n\r\n\r\n
                        Scoring<\/h5>\r\n \r\n
                        \r\n\r\n
                        \r\n \r\n
                        \r\n
                        \r\n

                        Not Initiated<\/p>\r\n <\/div> \r\n

                        \r\n

                        The operating model<\/span> for Analytics does not exist.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                        \r\n
                        \r\n

                        Conceptual<\/p>\r\n <\/div> \r\n

                        \r\n

                        The operating model<\/span> for Analytics does not exist, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                        \r\n
                        \r\n

                        Developmental<\/p>\r\n <\/div> \r\n

                        \r\n

                        The operating model<\/span> for Analytics is being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                        \r\n
                        \r\n

                        Defined<\/p>\r\n <\/div> \r\n

                        \r\n

                        The operating model<\/span> for Analytics has been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                        \r\n
                        \r\n

                        Achieved<\/p>\r\n <\/div> \r\n

                        \r\n

                        The operating model<\/span> for Analytics has been implemented, and the organization structure was established.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                        \r\n
                        \r\n

                        Enhanced<\/p>\r\n <\/div> \r\n

                        \r\n

                        The operating model<\/span> and organization structure for Analytics is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                        8.1.3 Analytics Governance<\/h3>\r\n <\/div> \r\n
                        \r\n \r\n
                        \r\n\r\n\r\n
                        Description<\/h5>\r\n\r\n

                        Explicit governance of analytics should be established for an organization. The governance structure oversees implementation and sustains the operating model<\/span> for Analytics, implementation of the analytics platform, and ongoing initiatives to shape the analytics culture of the organization. It ensures alignment of analytics with business strategy, data ethics, and the Data Management Program.<\/p>\r\n\r\n\r\n

                        Objectives<\/h5>\r\n\r\n
                          \r\n
                        • Define the governance structure for analytics.<\/li>\r\n
                        • Create policies to enforce analytics governance implementation.<\/li>\r\n
                        • Establish governance forums with written and approved charters.<\/li>\r\n
                        • Implement operating governance structures.<\/li>\r\n
                        • Identify and engage with stakeholders.<\/li>\r\n
                        • Communicate stakeholder<\/span> roles and responsibilities.<\/li>\r\n
                        • Hold stakeholders accountable for their participation in analytics via performance reviews and compensation considerations.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                          Advice<\/h5>\r\n\r\n

                          The governance structure should complement and align with the Analytics Operating Model<\/span>. Care should be taken to ensure the governance structure does not constrain timely decision making. Members of the Analytics governance structure need to be clear about their roles and empowered to drive change. Ensure there is representation from all the disciplines required to resolve issues arising from identification of opportunities, data collection and provisioning, and model<\/span> deployment.<\/p>\r\n\r\n

                          Analytics will have dependencies on other areas of the organization for deliverables such as data collection and model<\/span> deployment. It is particularly important to agree in advance to clear hand-offs and escalation paths. Consider having members of the governance organization reporting to senior management, such as the Chief Operating Officer, to gain this empowerment.<\/p>\r\n\r\n

                          Tool selection should be aligned with the business strategy and not driven just by what tooling or expertise exists in the organization.<\/p>\r\n\r\n

                          Ethics and privacy are central themes in the governance of analytics. Start by building on the ethics and privacy data governance processes, and structures already in place. Governance processes need to demonstrate fairness, transparency, and security of data usage.<\/p>\r\n\r\n\r\n

                          Questions<\/h5>\r\n\r\n
                            \r\n
                          • Do terms of reference for analytics governance exist?<\/li>\r\n
                          • Do policies exist that enforce analytics governance implementation?<\/li>\r\n
                          • Are there metrics for what is governed and measures of successful compliance?<\/li>\r\n
                          • Is there a tooling inventory with usage recommendations available?<\/li>\r\n
                          • Is there RACI (Responsible, Accountable, Consulted, Informed) documentation for all stakeholders and participants in the analytics governance process<\/span>?<\/li>\r\n
                          • Is the governance process<\/span> demonstrating that ethics and privacy are governed?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                            Artifacts<\/h5>\r\n\r\n
                              \r\n
                            • Analytics governance terms of reference<\/li>\r\n
                            • Evidence of policies written, implemented, and enforced to show that analytics is properly governed<\/li>\r\n
                            • Analytics governance metrics and measurements<\/li>\r\n
                            • Analytics project tracking<\/li>\r\n
                            • Model<\/span> inventory, including model<\/span> reviews and updates<\/li>\r\n
                            • Tooling inventory and recommendations<\/li>\r\n
                            • Analytics governance RACI<\/li>\r\n <\/ul>\r\n\r\n\r\n
                              Scoring<\/h5>\r\n \r\n
                              \r\n\r\n
                              \r\n \r\n
                              \r\n
                              \r\n

                              Not Initiated<\/p>\r\n <\/div> \r\n

                              \r\n

                              No governance structures for Analytics exist.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                              \r\n
                              \r\n

                              Conceptual<\/p>\r\n <\/div> \r\n

                              \r\n

                              No governance structures for Analytics exist, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                              \r\n
                              \r\n

                              Developmental<\/p>\r\n <\/div> \r\n

                              \r\n

                              Analytics governance structures are being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                              \r\n
                              \r\n

                              Defined<\/p>\r\n <\/div> \r\n

                              \r\n

                              Analytics governance structures have been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                              \r\n
                              \r\n

                              Achieved<\/p>\r\n <\/div> \r\n

                              \r\n

                              Analytics governance structures are established and operational.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                              \r\n
                              \r\n

                              Enhanced<\/p>\r\n <\/div> \r\n

                              \r\n

                              Analytics governance structures are established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                              8.1.4 Analytics Development Life Cycle<\/h3>\r\n <\/div> \r\n
                              \r\n \r\n
                              \r\n\r\n\r\n
                              Description<\/h5>\r\n\r\n

                              An analytics development life cycle or methodology provides a framework for the activities performed through the analytics life cycle. The life cycle begins with understanding the business problem and runs through deployment, operation, and review of the solution. The framework provides a common language and structure for stakeholders to refer to the different stages and aspects of analytics activities.<\/p>\r\n\r\n

                              The spectrum of analytics (e.g., Management Information, Business Intelligence, Artificial Intelligence, Descriptive, Diagnostic, Predictive, Prescriptive) employed by the organization is defined. Names and descriptions of the different types of analytics relevant to the organization are formalized in a categorization system. It provides a common language for the organization to refer to analytics and helps avoid confusion and misunderstanding.<\/p>\r\n\r\n

                              A standard<\/span> for model<\/span> documentation ensures consistency<\/span> across the organization in the way that model<\/span> provenance, assumptions, inputs, outputs, parameters, and limitations are captured and communicated.<\/p>\r\n\r\n\r\n

                              Objectives<\/h5>\r\n\r\n
                                \r\n
                              • Select or develop an analytics methodology that defines the analytics life cycle for the organization.<\/li>\r\n
                              • Define and adopt a standard<\/span> for model<\/span> documentation.<\/li>\r\n
                              • Formally document the analytics methodology and model<\/span> documentation standard<\/span>.<\/li>\r\n
                              • Ensure the methodology, categorization system, and model<\/span> documentation standards are understood and adopted by analytics practitioners.<\/li>\r\n
                              • Provide feedback mechanisms for ongoing refinement and improvement of the methodology and model<\/span> documentation standard<\/span>.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                Advice<\/h5>\r\n\r\n

                                Whether the organization should buy or outsource analytics solutions as opposed to internally developing them will depend on the maturity and culture of the organization. Most organizations follow a hybrid approach where for some problems they develop the analytics solution internally (in-house) and for others they outsource or procure externally. For each challenge faced, the organization needs to carefully review the benefits and cost of developing the solution in-house vs. outsourcing and select the most beneficial to the organization.<\/p>\r\n\r\n

                                The analytics methodology should focus on significant steps in the end-to-end process<\/span> rather than specific analytical or modeling techniques. Analytics tools come and go, while analytics methodology should be sustainable and stable. However, to reach a long-term stable analytics methodology, the organization must be open to methodology improvements based on experience. The analytics methodology should accommodate innovation as well as business use-case-driven analytics.<\/p>\r\n\r\n

                                There will be more flexibility to define and specify the analytics methodology for internally developed analytics than for externally developed analytics. However, in both cases, it may be worthwhile considering external best practice methodologies and adapting them to the organization.<\/p>\r\n\r\n

                                In defining the spectrum of analytics, examples will bring clarity. The boundaries of the analytics spectrum determine the activities to which the analytics governance and best-practice frameworks apply. For example, an organization may define its lowest boundary of analytics such that static (i.e., not automatically refreshable) Management Information reports are out-of-scope, whereas self-service Business Information reports may be considered in-scope.<\/p>\r\n\r\n

                                The categorization system for levels of analytics will not be static. It will work best by allowing for emerging levels of sophistication as Analytics matures and evolves.<\/p>\r\n\r\n

                                To ensure that the analytics methodology and categorization systems are appropriate to the organization and to get stakeholder<\/span> buy-in, key influencers and stakeholders should be involved in the selection or development of the analytics methodology and categorization system. Form a community of “champions” to act as owners of the methods and drivers of improvement.<\/p>\r\n\r\n\r\n

                                Questions<\/h5>\r\n\r\n
                                  \r\n
                                • Has an analytics methodology that defines the analytics life cycle of the organization been selected or developed?<\/li>\r\n
                                • Has a model<\/span> documentation standard<\/span> been created?<\/li>\r\n
                                • What types of analytics has the organization developed historically?<\/li>\r\n
                                • What types of analytics does the organization foresee using in the future?<\/li>\r\n
                                • What types of analytics are being used by other organizations?<\/li>\r\n
                                • Which stakeholders should be approached for input into the categorization system for levels of analytics?<\/li>\r\n
                                • Has it been confirmed that the analytics methodology, categorization system, and model<\/span> documentation standard<\/span> have been understood and adopted by analytics practitioners?<\/li>\r\n
                                • Have the analytics methodology and model<\/span> documentation standard<\/span> been formally documented?<\/li>\r\n
                                • Have feedback mechanisms for ongoing refinement and improvement of the analytics methodology, categorization systems and model<\/span> documentation standard<\/span> been developed and made available to stakeholders?<\/li>\r\n
                                • Is there a register of analytics projects with up-to-date status available?<\/li>\r\n
                                • Is there a model<\/span> register with review dates and update history?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                  Artifacts<\/h5>\r\n\r\n
                                    \r\n
                                  • Analytics methodology and terminology document<\/li>\r\n
                                  • Model<\/span> documentation standard<\/span><\/li>\r\n
                                  • Records of stakeholder<\/span> approval of the analytics methodology and model<\/span> documentation standard<\/span><\/li>\r\n
                                  • Analytics categorization approach<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                    Scoring<\/h5>\r\n \r\n
                                    \r\n\r\n
                                    \r\n \r\n
                                    \r\n
                                    \r\n

                                    Not Initiated<\/p>\r\n <\/div> \r\n

                                    \r\n

                                    No formal analytics development life cycle exists.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                    \r\n
                                    \r\n

                                    Conceptual<\/p>\r\n <\/div> \r\n

                                    \r\n

                                    No formal analytics development life cycle exists, but the need is recognized, and development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                    \r\n
                                    \r\n

                                    Developmental<\/p>\r\n <\/div> \r\n

                                    \r\n

                                    Analytics development life cycle is being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                    \r\n
                                    \r\n

                                    Defined<\/p>\r\n <\/div> \r\n

                                    \r\n

                                    Analytics development life cycle has been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                    \r\n
                                    \r\n

                                    Achieved<\/p>\r\n <\/div> \r\n

                                    \r\n

                                    Analytics development life cycle is established and in use.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                    \r\n
                                    \r\n

                                    Enhanced<\/p>\r\n <\/div> \r\n

                                    \r\n

                                    Analytics development life cycle established as part of business-as-usual practice with a continuous improvement routine and reviewed regularly.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                    8.1.5 Analytics Processes<\/h3>\r\n <\/div> \r\n
                                    \r\n \r\n
                                    \r\n\r\n\r\n
                                    Description<\/h5>\r\n\r\n

                                    Analytic processes have been documented, communicated and implemented across the organization. The success of an analytics program requires standard<\/span> organization-wide processes that are repeatable, sustainable and measurable. The organization should leverage existing industry standards and best practice. The use of the standard<\/span> processes must be required by policy<\/span>.<\/p>\r\n\r\n\r\n

                                    Objectives<\/h5>\r\n\r\n
                                      \r\n
                                    • Establish standardization across all analytics processes and practitioners.<\/li>\r\n
                                    • Ensure analytics processes are aligned and leverage standard<\/span> data management processes.<\/li>\r\n
                                    • Ensure compliance with data management policies.<\/li>\r\n
                                    • Ensure data created by Analytics integrates into Data Management ecosystem.<\/li>\r\n
                                    • Analytics is an active participant in and aligned with data management practices where appropriate (e.g., data quality<\/span>, data governance, metadata management<\/span>, data controls, issue management)<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                      Advice<\/h5>\r\n\r\n

                                      Analytics management must establish standardized processes to ensure that practitioners consistently and regularly document requirements, findings, adjustments, assumptions, and decisions while keeping up with ongoing changes. These standards should account for interactions with stakeholders, the data management team, and other relevant business units within the organization.<\/p>\r\n\r\n

                                      Analytics management and data management will depend on one another to effectively support the business in achieving its goals and objectives. This collaboration will require data and analytics practitioners to engage collectively in the established standard<\/span> practices. The analytics and data management teams must work together to share and leverage processes, avoiding duplication, particularly in areas such as data quality<\/span> and issue management.<\/p>\r\n\r\n

                                      Additionally, it is crucial for analytics practitioners to be aware of and understand the data management policies that pertain to the data they are using in their analyses. The Analytics team will not only utilize existing data resources but will also generate new data through their models, which must be managed according to organizational data management practices. <\/p>\r\n\r\n\r\n

                                      Questions<\/h5>\r\n\r\n
                                        \r\n
                                      • Are standard<\/span> analytics processes defined?<\/li>\r\n
                                      • Are analytics practices aligned and coordinated with data management practices?<\/li>\r\n
                                      • Do analytics practices reference data<\/span> management practices where appropriate?<\/li>\r\n
                                      • Are the analytics processes supported by policy<\/span>?<\/li>\r\n
                                      • Are the appropriate stakeholders engaged in the analytics practices?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                        Artifacts<\/h5>\r\n\r\n
                                          \r\n
                                        • Documented processes for analytics practitioners<\/li>\r\n
                                        • Evidence of analytics and data management collaboration<\/li>\r\n
                                        • Evidence of stakeholder<\/span> involvement in the standard<\/span> analytics processes as appropriate<\/li>\r\n
                                        • Policies in support of analytics standards<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                          Scoring<\/h5>\r\n \r\n
                                          \r\n\r\n
                                          \r\n \r\n
                                          \r\n
                                          \r\n

                                          Not Initiated<\/p>\r\n <\/div> \r\n

                                          \r\n

                                          Analytics processes are not documented.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                          \r\n
                                          \r\n

                                          Conceptual<\/p>\r\n <\/div> \r\n

                                          \r\n

                                          Analytics processes are not documented, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                          \r\n
                                          \r\n

                                          Developmental<\/p>\r\n <\/div> \r\n

                                          \r\n

                                          Analytics processes are being developed in alignment with all data management requirements.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                          \r\n
                                          \r\n

                                          Defined<\/p>\r\n <\/div> \r\n

                                          \r\n

                                          Analytics processes have been developed, reviewed and approved and are in alignment with all data management requirements.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                          \r\n
                                          \r\n

                                          Achieved<\/p>\r\n <\/div> \r\n

                                          \r\n

                                          Analytics processes have been adopted and are successfully meeting data management requirements.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                          \r\n
                                          \r\n

                                          Enhanced<\/p>\r\n <\/div> \r\n

                                          \r\n

                                          Analytics processes have been adopted and are successfully meeting data management requirements as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                          8.1.6 Analytics Monitoring<\/h3>\r\n <\/div> \r\n
                                          \r\n \r\n
                                          \r\n\r\n\r\n
                                          Description<\/h5>\r\n\r\n

                                          The objective of Analytics is to synthesize data, create views and provide insights that are used to support the business needs (e.g. satisfy regulatory requirements, conduct critical activities such as closing of books, deliver outcomes of business value). The organization should document the performance indicators to be used to routinely measure the impact and effectiveness of their analytics solutions and tie them back to business and data management strategies.<\/p>\r\n\r\n\r\n

                                          Objectives<\/h5>\r\n\r\n
                                            \r\n
                                          • Measure and communicate business value created by analytics.<\/li>\r\n
                                          • Engage the stakeholders to create shared accountability and buy-in to quantified benefits driven by analytics.<\/li>\r\n
                                          • Measure the business impact of analytics use cases, projects, and experiments.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                            Advice<\/h5>\r\n\r\n

                                            Organizations should consider in advance how to define and measure the success of the outcome(s) of any analytical solution. A useful starting point is to establish reliable comparison benchmarks from which to measure incremental impacts. Control groups and randomized experimental methods are good ways to establish these benchmarks. These tools become especially important to diagnose cause and effect in situations where actions based on analytics insight do not result in the anticipated benefits. For example, the failure of an analytics-based marketing campaign that does not deliver expected benefits may not simply result from failed analytics models, it may arise from other factors such as poor execution or low-quality marketing data.<\/p>\r\n\r\n

                                            There can be analytics where the benefits cannot be quantified. In this case, the qualitative benefits of these should be documented and recognized. The value of analytics that informs the decisions should also be recognized.<\/p>\r\n\r\n

                                            When the incremental value of analytics can be measured, the successful benchmarking approaches can be applied to a whole portfolio of analytical solutions. The Analytics teams quantify the business value of their actions to the organization at large, justifying the initial and additional investments in analytical capabilities. The systematic quantification and communication of business value supports the development of a data-driven culture of inquiry.<\/p>\r\n\r\n\r\n

                                            Questions<\/h5>\r\n\r\n
                                              \r\n
                                            • Do analytics specification documents define key performance indicators to evaluate the analytics?<\/li>\r\n
                                            • Are key performance indicators, control groups, or other experimental methods routinely used to prove the incremental value of analytics against a benchmark?<\/li>\r\n
                                            • Do the control groups or other experimental methods in use successfully isolate the impact of analytic insights versus the impacts of other related business actions?<\/li>\r\n
                                            • Are the benefits of analytics communicated and understood by senior management and validated by an independent third party\/function<\/span> (e.g., Finance)?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                              Artifacts<\/h5>\r\n\r\n
                                                \r\n
                                              • Analytics specification documents<\/li>\r\n
                                              • Evidence of the ROI of analytics solutions<\/li>\r\n
                                              • Evidence of experimental design to evaluate the incremental value of analytics<\/li>\r\n
                                              • Post-implementation benefits evaluations<\/li>\r\n
                                              • Analytics key performance indicator documentation or metadata<\/span><\/li>\r\n
                                              • Evidence of communication of analytics benefits to senior management<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                Scoring<\/h5>\r\n \r\n
                                                \r\n\r\n
                                                \r\n \r\n
                                                \r\n
                                                \r\n

                                                Not Initiated<\/p>\r\n <\/div> \r\n

                                                \r\n

                                                Analytics usage is not measured or understood to be driving business value.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                \r\n
                                                \r\n

                                                Conceptual<\/p>\r\n <\/div> \r\n

                                                \r\n

                                                Analytics usage is not measured or understood to be driving business value, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                \r\n
                                                \r\n

                                                Developmental<\/p>\r\n <\/div> \r\n

                                                \r\n

                                                Measurement of analytics usage and business value is being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                \r\n
                                                \r\n

                                                Defined<\/p>\r\n <\/div> \r\n

                                                \r\n

                                                Measurement of analytics usage and business value has been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                \r\n
                                                \r\n

                                                Achieved<\/p>\r\n <\/div> \r\n

                                                \r\n

                                                Measurement of analytics usage and business value is being performed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                \r\n
                                                \r\n

                                                Enhanced<\/p>\r\n <\/div> \r\n

                                                \r\n

                                                Measurement of analytics usage and business value is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                8.2 Analytics & Business Alignment<\/h3>\r\n <\/div>\r\n\r\n
                                                \r\n \r\n
                                                \r\n\r\n

                                                The Analytics and Business functions must be aligned and both functions must support business goals together. Analytics activities must be prioritized to meet the needs of business strategy and drive business value.<\/p>\r\n\r\n\r\n \r\n\r\n <\/div>\r\n <\/div> \r\n\r\n\r\n\r\n

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

                                                8.2.1 Analytics and Business Architecture Collaboration<\/h3>\r\n <\/div> \r\n
                                                \r\n \r\n
                                                \r\n\r\n
                                                Description<\/h5>\r\n\r\n

                                                The business architecture<\/span> of an organization defines its structure, governance, processes and information for decision making. The Analytics organization understands the business architecture<\/span> of the organization and uses it as an input to define the Analytics strategy and requirements of the organization.<\/p>\r\n\r\n

                                                The Analytics organization engages frequently with the business stakeholders to understand their needs. To execute on this vision, the organization has a well-defined process<\/span> to capture business requirements, estimate and understand the impact on analytics, prioritize them and develop and execute the roadmap to deliver them.<\/p>\r\n\r\n\r\n

                                                Objectives<\/h5>\r\n\r\n
                                                  \r\n
                                                • Review the business\/functional architecture (e.g., strategy, structure, governance, processes) regardless of the degree of formalization.<\/li>\r\n
                                                • Understand and document key analytical requirements appropriate for the business and functions.<\/li>\r\n
                                                • Align the Analytics capabilities and processes with business requirements.<\/li>\r\n
                                                • Communicate and anchor analytical requirements to stakeholders.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                  Advice<\/h5>\r\n\r\n

                                                  Businesses do not all function<\/span> identically, and decision-making priorities can differ across various segments of the same organization. To effectively address these differences, analytics leaders must collaborate with business leaders to grasp their needs and determine how analytics can best integrate with the overall business architecture<\/span>, which encompasses a wide range of components beyond just IT systems.<\/p>\r\n\r\n

                                                • Designers of the Analytics Operating Model<\/span> should ensure that it reflects both business requirements and the broader business architecture<\/span>, maintaining alignment with ongoing input from business leaders. Given the close relationship between analytics and senior decision-making, certain elements of the analytics organization may need to be decentralized and integrated within various business units or functional areas. Conversely, some analytics functions could be most effectively supported by a centralized center of excellence.<\/li>\r\n\r\n
                                                • The most successful analytics organizations focus on projects that align with business objectives and the overarching business architecture<\/span>. Engaging deeply with these objectives ensures a well-balanced analytics portfolio that considers strategic and tactical initiatives, compliance alongside performance, business-as-usual support versus innovation, and various metrics.<\/li>\r\n\r\n
                                                • Thorough documentation of analytical requirements fosters a clear and consistent understanding among stakeholders. Continuous engagement with the shifting dynamics of business needs allows Analytics to remain focused on pressing priorities.<\/li>\r\n\r\n\r\n
                                                  Questions<\/h5>\r\n\r\n
                                                    \r\n
                                                  • Is the Analytics Operating Model<\/span> and plan documented?<\/li>\r\n
                                                  • Have key dependencies been considered in the design of the Analytics organization and its connectivity to decision making?<\/li>\r\n
                                                  • Does the Analytics plan include specific reference to business requirements?<\/li>\r\n
                                                  • Have the senior executive and line-of-business executive teams endorsed the Analytics plan?<\/li>\r\n
                                                  • Is there a defined process<\/span> for ongoing updates of the Analytics plan?<\/li>\r\n
                                                  • Does the analytics organization understand the business requirements?<\/li>\r\n
                                                  • Can the analytics teams show connectivity between their business requirements and the business architecture<\/span>?<\/li>\r\n
                                                  • Are gaps consistently captured and is there a process<\/span> for acting on them?<\/li>\r\n
                                                  • Does the business understand the connection between their business architecture<\/span> and the analytics design?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                    Artifacts<\/h5>\r\n\r\n
                                                      \r\n
                                                    • Evidence of alignment of Analytics with business strategy and plan<\/li>\r\n
                                                    • Documented alignment of Analytics, Business Architecture<\/span> and business requirements<\/li>\r\n
                                                    • Details of business analytics requirements<\/li>\r\n
                                                    • Evidence of senior executive input and approval<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                      Scoring<\/h5>\r\n \r\n
                                                      \r\n\r\n
                                                      \r\n \r\n
                                                      \r\n
                                                      \r\n

                                                      Not Initiated<\/p>\r\n <\/div> \r\n

                                                      \r\n

                                                      Dependencies between Analytics and Business Architecture<\/span> are not understood.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                      \r\n
                                                      \r\n

                                                      Conceptual<\/p>\r\n <\/div> \r\n

                                                      \r\n

                                                      Dependencies between Analytics and Business Architecture<\/span> are not understood, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                      \r\n
                                                      \r\n

                                                      Developmental<\/p>\r\n <\/div> \r\n

                                                      \r\n

                                                      Dependencies between Analytics and Business Architecture<\/span> are being determined.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                      \r\n
                                                      \r\n

                                                      Defined<\/p>\r\n <\/div> \r\n

                                                      \r\n

                                                      Dependencies between Analytics and Business Architecture<\/span> have been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                      \r\n
                                                      \r\n

                                                      Achieved<\/p>\r\n <\/div> \r\n

                                                      \r\n

                                                      Dependencies between Analytics and Business Architecture<\/span> are understood and are being addressed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                      \r\n
                                                      \r\n

                                                      Enhanced<\/p>\r\n <\/div> \r\n

                                                      \r\n

                                                      Understanding and addressing the dependencies between Analytics and Business Architecture<\/span> is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                      8.2.2 Business Driven Analytics Prioritization<\/h3>\r\n <\/div> \r\n
                                                      \r\n \r\n
                                                      \r\n\r\n
                                                      Description<\/h5>\r\n\r\n

                                                      The business strategy drives the Analytics Roadmap and activities. This fact keeps the focus on analytics investments and how they can maximize business outcomes. The Analytics organization should be aligned and in collaboration with business stakeholders.<\/p>\r\n\r\n\r\n

                                                      Objectives<\/h5>\r\n\r\n
                                                        \r\n
                                                      • Understand leadership expectations and explore how analytics can support strategic value creation.<\/li>\r\n
                                                      • Work collaboratively with leadership to build a comprehensive list of current business opportunities and analytics use cases.<\/li>\r\n
                                                      • Co-create an analytics vision and roadmap that helps the alignment with business priorities, recognize short- and long-term focus areas, and creates senior management buy-in.<\/li>\r\n
                                                      • Develop benefits use cases for all analytics and rank them based on their business value using the analytics prioritization process<\/span>.<\/li>\r\n
                                                      • Communicate the Analytics vision and the prioritization of analytics use cases to stakeholders.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                        Advice<\/h5>\r\n\r\n

                                                        Align the Analytics Roadmap with the business strategy establishing a forum, across the business, to supervise prioritization of analytics use cases. Review and prioritization must be a regular activity performed on a regular basis.<\/p>\r\n\r\n

                                                        A framework to assess the benefits of analytics use cases should have clear dimensions for scoring and grading them. Scoring and grading prioritization should include, but not be limited to, the complexity, feasibility, regulatory requirements, and business value of the analytics solution, alignment to the organization’s business objectives, the number of data sources involved, and the size of the user community impacted. The framework should be transparent, allowing the fair assessment of analytics use cases and the communication of use case prioritization with the business stakeholders.<\/p>\r\n\r\n

                                                        The organization should ensure that analytics activities include both those that drive business outcomes as well as those that develop the foundational and future state of analytics capabilities. Create a roadmap that contains a detailed list of initiatives that are sequenced to help the organization deliver on its strategic objectives and establish processes to revisit sequencing as business priorities and market conditions change.<\/p>\r\n\r\n\r\n

                                                        Questions<\/h5>\r\n\r\n
                                                          \r\n
                                                        • Is there a formal, documented, and prioritized roadmap for Analytics?<\/li>\r\n
                                                        • Does a process<\/span> exist to ensure prioritizations are revisited and modified by accountable stakeholders?<\/li>\r\n
                                                        • Does the Analytics Roadmap articulate its support of the organization in its strategic business objectives and does it capture what is needed to support business as usual?<\/li>\r\n
                                                        • Has the Analytics vision and roadmap received appropriate high-level review and approval?<\/li>\r\n
                                                        • Do the analytics use cases document the assessments of their business value as well as their feasibility?<\/li>\r\n
                                                        • What is the process<\/span> to capture the business strategy and the demand\/impact to analytics?<\/li>\r\n
                                                        • Are there clear grading criteria for assessing or scoring the potential business value and feasibility of analytics use cases?<\/li>\r\n
                                                        • Has communication support been established so business stakeholders can prioritize the use cases?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                          Artifacts<\/h5>\r\n\r\n
                                                            \r\n
                                                          • Analytics vision statement or plan<\/li>\r\n
                                                          • Prioritized roadmap of Analytics<\/li>\r\n
                                                          • Details of use case benefits<\/li>\r\n
                                                          • Evidence of high-level sponsorship and support<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                            Scoring<\/h5>\r\n \r\n
                                                            \r\n\r\n
                                                            \r\n \r\n
                                                            \r\n
                                                            \r\n

                                                            Not Initiated<\/p>\r\n <\/div> \r\n

                                                            \r\n

                                                            Prioritization of Analytics is not driven by business strategy.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                            \r\n
                                                            \r\n

                                                            Conceptual<\/p>\r\n <\/div> \r\n

                                                            \r\n

                                                            Prioritization of Analytics is not driven by business strategy, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                            \r\n
                                                            \r\n

                                                            Developmental<\/p>\r\n <\/div> \r\n

                                                            \r\n

                                                            The approach to business strategy driving the prioritization of Analytics is being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                            \r\n
                                                            \r\n

                                                            Defined<\/p>\r\n <\/div> \r\n

                                                            \r\n

                                                            The approach to business strategy driving the prioritization of Analytics has been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                            \r\n
                                                            \r\n

                                                            Achieved<\/p>\r\n <\/div> \r\n

                                                            \r\n

                                                            Prioritization of Analytics is driven by business strategy.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                            \r\n
                                                            \r\n

                                                            Enhanced<\/p>\r\n <\/div> \r\n

                                                            \r\n

                                                            Prioritization of Analytics driven by business strategy is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                            8.2.3 Analytics Support for Business Needs<\/h3>\r\n <\/div> \r\n
                                                            \r\n \r\n
                                                            \r\n\r\n
                                                            Description<\/h5>\r\n\r\n

                                                            Analytics activities properly aligned to business objectives can deliver value in multiple ways. Examples include, informing decisions, validating understanding, identifying process<\/span> effectiveness, or suggesting actions. Analytics teams drive innovation, taking new ideas to the business as well as responding to business-led use cases. Appropriate analytics insights should be embedded in business information and processes. In many cases, this will include automation of analytics with technology for greater speed and efficiency.<\/p>\r\n\r\n\r\n

                                                            Objectives<\/h5>\r\n\r\n
                                                              \r\n
                                                            • Clarify which business questions, decisions, actions or processes would be impacted by the analytical solution in the formulation of a new analytics use case.<\/li>\r\n
                                                            • Early in the design of any analytics solution, establish which user community will benefit from the analytical solution.<\/li>\r\n
                                                            • Co-develop analytics solutions with relevant business teams.<\/li>\r\n
                                                            • Ensure access to analytics outputs and that their visualizations are readily available.<\/li>\r\n
                                                            • Communicate and deploy outputs in ways the business users can easily consume them, including the development of good visualizations and user interfaces to ensure the explainability of the analytics outputs.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                              Advice<\/h5>\r\n\r\n

                                                              Analytics should both respond to business needs and proactively generate new insights. In each case, there is a responsibility to ensure the business can use the analytics outputs to support its decisions and act on the new insight.<\/p>\r\n\r\n

                                                              Regular communication between the business and Analytics teams is critical for success. Interaction allows the analytic solutions to be co-developed so that they are focused on the right needs and delivered in a way that is most effective for the users to act. During this process<\/span>, Analytics can add value by considering a broader array of data inputs and insights that may be derived from a mix of internal and external sources.<\/p>\r\n\r\n

                                                              When designing new analytics use cases or initiatives, it is important to consider the actionability of insights. In some instances, limits on actionability may arise from ethical, legal, or commercial considerations. For example, while it may be technically feasible to predict which customers<\/span> are most likely to churn, the business must be extremely careful when deciding whether to act on this insight to avoid unintended consequences of contacting them. The use of personally identifiable information<\/span> often requires special care for ethical and regulatory reasons.<\/p>\r\n\r\n

                                                              All Analytics activities must have a purpose. Some analysis is likely to be investigative and so not directly actionable in a business process<\/span>. However, these analyses should fit into a decision process<\/span> where exploratory analysis helps the business choose the next course of action.<\/p>\r\n\r\n

                                                              Analytics teams have multiple options for the deployment of insights depending on the context and time-sensitivity of the use case. For example, the ability to automate or centralize critical algorithms while minimizing manual manipulation is likely to be more appropriate for high volume, close to real-time decision making. In contrast, ongoing business processes with humans in the loop are more likely to need analytic outputs using visualizations and integrated business intelligence tools. In both scenarios, it is important to ensure the explainability of the analytics outputs so that stakeholders can gain trust in using the analytics.<\/p>\r\n\r\n\r\n

                                                              Questions<\/h5>\r\n\r\n
                                                                \r\n
                                                              • Do formal procedures exist for documenting the purpose, scope, and delivery of analytics use case insights?<\/li>\r\n
                                                              • Does the analytics specification document identify the specific user community impacted?<\/li>\r\n
                                                              • Does the analytics specification document identify how the outputs will be delivered, acted on, or embedded in the business process<\/span>?<\/li>\r\n
                                                              • Is the analytics tooling readily available to all potential beneficiaries in the organization?<\/li>\r\n
                                                              • Has the organization demonstrated the benefits of automating analytics that supports business processes?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                Artifacts<\/h5>\r\n\r\n
                                                                  \r\n
                                                                • Analytics governance policies<\/li>\r\n
                                                                • Analytics specification documents<\/li>\r\n
                                                                • Evidence of alignment with privacy and ethics policies<\/li>\r\n
                                                                • Evidence of analytics automation<\/li>\r\n
                                                                • Analytics output visualizations<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                  Scoring<\/h5>\r\n \r\n
                                                                  \r\n\r\n
                                                                  \r\n \r\n
                                                                  \r\n
                                                                  \r\n

                                                                  Not Initiated<\/p>\r\n <\/div> \r\n

                                                                  \r\n

                                                                  The means of ensuring that Analytics support and influence business needs, and are actionable where required, does not exist.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                  \r\n
                                                                  \r\n

                                                                  Conceptual<\/p>\r\n <\/div> \r\n

                                                                  \r\n

                                                                  The means of ensuring that Analytics support and influence business needs, and are actionable where required, does not exist, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                  \r\n
                                                                  \r\n

                                                                  Developmental<\/p>\r\n <\/div> \r\n

                                                                  \r\n

                                                                  The means of ensuring that Analytics support and influence business needs, and are actionable where required, is being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                  \r\n
                                                                  \r\n

                                                                  Defined<\/p>\r\n <\/div> \r\n

                                                                  \r\n

                                                                  The means of ensuring that Analytics support and influence business needs, and are actionable where required, has been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                  \r\n
                                                                  \r\n

                                                                  Achieved<\/p>\r\n <\/div> \r\n

                                                                  \r\n

                                                                  The means of ensuring that Analytics support and influence business needs, and are actionable where required, is implemented.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                  \r\n
                                                                  \r\n

                                                                  Enhanced<\/p>\r\n <\/div> \r\n

                                                                  \r\n

                                                                  The means of ensuring that Analytics support and influence business needs, and are actionable where required, is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                                  8.3 Analytics Management & Data Management Ecosystem Alignment<\/h3>\r\n <\/div>\r\n\r\n
                                                                  \r\n \r\n
                                                                  \r\n\r\n\r\n

                                                                  Analytics Management and Data Management must be aligned to ensure they function<\/span> as an integrated part of the organization's data ecosystem, supporting business goals. Since analytics relies on upstream data and generates insights for decision-making, alignment with Data Management is essential to maintain data reliability and foster confidence in data-driven decisions. Analytics must understand data lineage<\/span>, adhere to approved business definitions, and follow identification and classification standards.<\/p>\r\n\r\n\r\n \r\n\r\n <\/div>\r\n <\/div> \r\n\r\n\r\n\r\n

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

                                                                  8.3.1 Analytics Alignment with Data Management and Data Architecture Standards<\/h3>\r\n <\/div> \r\n
                                                                  \r\n \r\n
                                                                  \r\n\r\n\r\n
                                                                  Description<\/h5>\r\n\r\n

                                                                  Data Management and Data Architecture<\/span> play a crucial role in supporting Analytics Management by ensuring data completeness<\/span>, quality, and traceability.<\/p>\r\n\r\n\r\n

                                                                  Objectives<\/h5>\r\n\r\n
                                                                    \r\n
                                                                  • Ensure that Analytics Management, Data Management and Data Architecture<\/span> are in collaboration to establish and maintain quality data sources for consumption.<\/li>\r\n
                                                                  • Ensure that all Data Management and teams are utilizing standard<\/span> data architecture<\/span> structures (e.g., business glossary<\/span> definitions, data catalog, metadata<\/span>, taxonomies, ontologies).<\/li>\r\n
                                                                  • Ensure policy<\/span> and standards for Analytics Management and Data Management are aligned and understood by both organizations.<\/li>\r\n
                                                                  • Align the development life cycles of Analytics Management and Data Management.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                    Advice<\/h5>\r\n\r\n

                                                                    Data Management and Data Architecture<\/span> play a crucial role in supporting Analytics Management by ensuring data completeness<\/span>, quality, and traceability. Authoritative data sources must be used whenever possible, but when alternative sources are required, they should be recorded to maintain integrity. Data lineage<\/span> provides transparency, enabling trust in analytical products and business decisions by ensuring data can be traced from source to final output, with all transformations and aggregations understood and agreed upon. Consistent data mapping to clear business definitions is essential for reliable decision making. In a mature data environment, these definitions are maintained in authoritative sources, captured in metadata<\/span> and lineage, and governed by data management policies and standards to ensure quality, controlled access, and appropriate usage.<\/p>\r\n\r\n

                                                                    The Analytics Management and Data Management organizations must collaborate directly and have a clear understanding of each other's roles and responsibilities within the data ecosystem of the organization. Without alignment between the teams, it will be challenging for either team to contribute effectively towards achieving the business objectives.<\/p>\r\n\r\n\r\n

                                                                    Questions<\/h5>\r\n\r\n
                                                                      \r\n
                                                                    • Does Analytics Management use data sources supported and published for consumption by Data Management?<\/li>\r\n
                                                                    • Is Analytics Management participating in the use and maintenance of the standard<\/span> data architecture<\/span> structures and tools (e.g., catalog, glossary, metadata<\/span>)?<\/li>\r\n
                                                                    • Are the policy<\/span> and standards established for Data Management and Analytics Management aligned and not conflicting?<\/li>\r\n
                                                                    • Are the Analytics Management and Data Management teams aware of roles and responsibilities each has related to data management?<\/li>\r\n
                                                                    • Is there a regular cadence of both teams participating together in support of the business objectives?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                      Artifacts<\/h5>\r\n\r\n
                                                                        \r\n
                                                                      • Analytics Management and Data Management Alignment Approach<\/li>\r\n
                                                                      • Analytics Management Policy<\/span> and Standards<\/li>\r\n
                                                                      • Data Management Policy<\/span> and Standards<\/li>\r\n
                                                                      • Data Architecture<\/span> Standards<\/li>\r\n
                                                                      • Data Management Tool Standards<\/li>\r\n
                                                                      • Meeting artifacts supporting collaboration<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                        Scoring<\/h5>\r\n \r\n
                                                                        \r\n\r\n
                                                                        \r\n \r\n
                                                                        \r\n
                                                                        \r\n

                                                                        Not Initiated<\/p>\r\n <\/div> \r\n

                                                                        \r\n

                                                                        No formal approach for alignment exists between Analytics Management and Data Management.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                        \r\n
                                                                        \r\n

                                                                        Conceptual<\/p>\r\n <\/div> \r\n

                                                                        \r\n

                                                                        No formal approach for alignment exists between Analytics Management and Data Management but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                        \r\n
                                                                        \r\n

                                                                        Developmental<\/p>\r\n <\/div> \r\n

                                                                        \r\n

                                                                        The approach for alignment of Analytics Management and Data Management is being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                        \r\n
                                                                        \r\n

                                                                        Defined<\/p>\r\n <\/div> \r\n

                                                                        \r\n

                                                                        The approach for alignment of Analytics Management and Data Management has been defined, reviewed, and approved by stakeholders.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                        \r\n
                                                                        \r\n

                                                                        Achieved<\/p>\r\n <\/div> \r\n

                                                                        \r\n

                                                                        The approach for alignment of Analytics Management and Data Management is established and supports ongoing collaboration.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                        \r\n
                                                                        \r\n

                                                                        Enhanced<\/p>\r\n <\/div> \r\n

                                                                        \r\n

                                                                        The approach for alignment of Analytics Management and Data Management established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                                        8.3.2 Analytics Data Preparation Standards<\/h3>\r\n <\/div> \r\n
                                                                        \r\n \r\n
                                                                        \r\n\r\n
                                                                        Description<\/h5>\r\n\r\n

                                                                        Data preparation is the process<\/span> of collecting, structuring, cleansing, and transforming data so it can be readily and accurately analyzed for business purposes. The data preparation process<\/span> must be defined, and all process<\/span> steps applied consistently to achieve fit-for-purpose data. Data preparation must be subject to the organization’s Data Governance policy<\/span> and standards, including the use of the business glossary<\/span> and metadata<\/span>. The data must be based on authoritative data sources, where relevant. Data preparation must be performed in a way that preserves data lineage<\/span> and integrity.<\/p>\r\n\r\n\r\n

                                                                        Objectives<\/h5>\r\n\r\n
                                                                          \r\n
                                                                        • Define standards for data preparation that include the identification of data required for the analysis, available authoritative data sources, and data accessibility.<\/li>\r\n
                                                                        • Define standards for specification of data elements, data quality<\/span>, need for data cleansing (including defect tracking and root cause fix), and conformance, transformation, and aggregation.<\/li>\r\n
                                                                        • Ensure data preparation follows the organization’s Data Management policy<\/span> and Data Management standards and preserves data lineage<\/span> and integrity.<\/li>\r\n
                                                                        • Create and maintain adequate documentation on data definitions, data sources and lineage, data usage, and data owners.<\/li>\r\n
                                                                        • Maximize the re-usability of any prepared data and data preparation processes to create efficiencies and time to market improvements for future data-preparation needs.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                          Advice<\/h5>\r\n\r\n

                                                                          Data preparation processes leverage authoritative data sources, business glossary<\/span>, and metadata<\/span> to provide accurate, well-defined data for consumption. When new data sets or data elements are sourced, documentation should be completed to ease reuse. A well-documented data catalog supports and significantly accelerates future data sourcing and wrangling processes.<\/p>\r\n\r\n

                                                                          Understanding data quality<\/span> and determining whether the data is fit-for-purpose must be a key activity of the Analytics practitioners in the data preparation process<\/span>. Data of higher quality can be reused in other processes more readily. Profiling<\/span> data can support data sourcing decisions. Profiling<\/span> provides a statistics-based understanding of data content and data quality<\/span> across multiple data sources.<\/p>\r\n\r\n

                                                                          Data preparation should be a repeatable process<\/span> and a formalized best practice. Preference should be given to the use of self-service data preparation solutions versus spreadsheets. Spreadsheets are affordable but error-prone, difficult to control, and maintenance heavy. Data-preparation tools can provide an effective and controlled data preparation process<\/span> and the ability to integrate structured and unstructured data more efficiently. Strategies for agile creation of re-usable data sets should be considered to foster efficiency by reducing the need for internal approvals via obfuscation techniques.<\/p>\r\n\r\n\r\n

                                                                          Questions<\/h5>\r\n\r\n
                                                                            \r\n
                                                                          • Do data preparation standards cover the identification of data required for the analysis, available (authoritative) data sources, data accessibility, specification of data elements, data quality<\/span> metrics, data cleansing, and conformance, transformation, and aggregation?<\/li>\r\n
                                                                          • Does data preparation follow the organization’s Data Management policy<\/span> and Data Management standards and preserve data lineage<\/span> and integrity?<\/li>\r\n
                                                                          • Is adequate documentation maintained on data definitions, data sources, data lineage<\/span>, data usage, and data owners?<\/li>\r\n
                                                                          • Are any prepared data or data preparation processes leveraged across multiple analytical processes, tools, or teams?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                            Artifacts<\/h5>\r\n\r\n
                                                                              \r\n
                                                                            • Data preparation and analytics guidance and design documentation<\/li>\r\n
                                                                            • Evidence of adoption of data preparation processes by Analytics teams<\/li>\r\n
                                                                            • Documentation of data architecture<\/span> and data lineage<\/span>, including changes made through data preparation<\/li>\r\n
                                                                            • Data definition, sourcing, lineage, usage, and ownership documentation supporting data-preparation decisions<\/li>\r\n
                                                                            • Evidence of re-use of data sets and data preparation processes<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                              Scoring<\/h5>\r\n \r\n
                                                                              \r\n\r\n
                                                                              \r\n \r\n
                                                                              \r\n
                                                                              \r\n

                                                                              Not Initiated<\/p>\r\n <\/div> \r\n

                                                                              \r\n

                                                                              No data preparation standards exist.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                              \r\n
                                                                              \r\n

                                                                              Conceptual<\/p>\r\n <\/div> \r\n

                                                                              \r\n

                                                                              No data preparation standards exist, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                              \r\n
                                                                              \r\n

                                                                              Developmental<\/p>\r\n <\/div> \r\n

                                                                              \r\n

                                                                              Data preparation standards are being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                              \r\n
                                                                              \r\n

                                                                              Defined<\/p>\r\n <\/div> \r\n

                                                                              \r\n

                                                                              Data preparation standards have been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                              \r\n
                                                                              \r\n

                                                                              Achieved<\/p>\r\n <\/div> \r\n

                                                                              \r\n

                                                                              Data preparation standards are being applied consistently.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                              \r\n
                                                                              \r\n

                                                                              Enhanced<\/p>\r\n <\/div> \r\n

                                                                              \r\n

                                                                              The consistent application of data preparation standards is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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\r\n

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

                                                                              8.4 Analytics Platform<\/h3>\r\n <\/div>\r\n\r\n
                                                                              \r\n \r\n
                                                                              \r\n\r\n\r\n

                                                                              For Analytics to be effective and efficient, it must be supported by a platform that is designed and implemented to meet its needs. The operating model<\/span> drives many of these needs. The different requirements of production and non-production environments must be addressed, and there must be a version-control regime for models that is appropriate for each of these environments. Strategies for anonymization of sensitive data are required to maximize the reusability of data sets. The platform should provide appropriate flexibility to scale up and down. Both production and non-production environments should be aligned with ethics and privacy governances.<\/p>\r\n\r\n\r\n \r\n\r\n <\/div>\r\n <\/div> \r\n\r\n\r\n\r\n

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

                                                                              8.4.1 Analytics Platform Supports Analytics Operating Model<\/h3>\r\n <\/div> \r\n
                                                                              \r\n \r\n
                                                                              \r\n\r\n \r\n
                                                                              Description<\/h5>\r\n\r\n

                                                                              The analytics platform is a combination of tools, applications, and infrastructure that enables analytics to be created and executed in an organization. It must have the necessary capabilities to support the way that Analytics teams are structured and operated, and the way they engage with the business and stakeholders. It must enable Analytics to develop, test, govern, socialize, maintain, and mature analytical models.<\/p>\r\n\r\n

                                                                              The platform must support data operation activities and be flexibl• Ensure the platform design takes account of the agreed requirements.e enough to enable a variety of individuals to access data, conduct analyses, and create visualizations as needed. These interactions must implement any required segregation of duties and the ability to set access rights to different users of the system.<\/p>\r\n\r\n

                                                                              Beyond the Analytics teams, business users will need to validate and utilize the results of the analytics models.<\/p>\r\n\r\n\r\n

                                                                              Objectives<\/h5>\r\n\r\n
                                                                                \r\n
                                                                              • Understand the platform requirements of the different roles defined in the operating model<\/span><\/i>.<\/li>\r\n
                                                                              • Identify stakeholders and obtain agreement to the requirements to be supported.<\/li>\r\n
                                                                              • Ensure the platform design takes account of the agreed requirements.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                Advice<\/h5>\r\n\r\n

                                                                                The functional and non-functional requirements to support the Analytics Operating Model<\/span> must be understood before the procurement or development of the platform commences. Any pre-existing infrastructure and solutions should not constrain the requirements.<\/p>\r\n\r\n

                                                                                Facilitation of segregation of duties, and support and control of different levels of access, must be part of the design. The platform design should ensure ease of access and use. It should support the need for platform users to understand both the data being used and the results being produced.<\/p>\r\n\r\n

                                                                                It is advisable to design the platform to support data operations, ensuring efficient data throughput from applications through various stages to the end user. As data consumption by diverse stakeholders increases, it is crucial to manage data as a continuous flow, integrating seamlessly across different organizational verticals.<\/p>\r\n\r\n\r\n

                                                                                Questions<\/h5>\r\n\r\n
                                                                                  \r\n
                                                                                • Have the platform requirements of different roles described in the operating model<\/span> been defined?<\/li>\r\n
                                                                                • Have platform requirements been discussed and agreed with business and Analytics stakeholders?<\/li>\r\n
                                                                                • Are the requirements understood by those responsible for the procurement and implementation of the platform?<\/li>\r\n
                                                                                • Has the platform design been reviewed to confirm it addresses the agreed requirements?<\/li>\r\n
                                                                                • Has platform support of enforcement of access rights been validated?<\/li>\r\n
                                                                                • Can stakeholders easily review the outputs of the platform?<\/li>\r\n
                                                                                • Can the platform support users beyond the data analysts who produce the outputs?<\/li>\r\n
                                                                                • Can the platform support data operations?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                  Artifacts<\/h5>\r\n\r\n
                                                                                    \r\n
                                                                                  • Documented assessment of the platform design support for the operating model<\/span><\/li>\r\n
                                                                                  • Policies relating to segregation of duties and evidence of their review and approval<\/li>\r\n
                                                                                  • Evidence of bi-directional communication with the stakeholders\/business on the requirements of use of the platform<\/li>\r\n
                                                                                  • Policies relating to the management of access<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                    Scoring<\/h5>\r\n \r\n
                                                                                    \r\n\r\n
                                                                                    \r\n \r\n
                                                                                    \r\n
                                                                                    \r\n

                                                                                    Not Initiated<\/p>\r\n <\/div> \r\n

                                                                                    \r\n

                                                                                    The requirement for the platform design to meet the needs of the Analytics Operating Model<\/span> has not been identified.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                    \r\n
                                                                                    \r\n

                                                                                    Conceptual<\/p>\r\n <\/div> \r\n

                                                                                    \r\n

                                                                                    The platform design does not meet the needs of the Analytics Operating Model<\/span>, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                    \r\n
                                                                                    \r\n

                                                                                    Developmental<\/p>\r\n <\/div> \r\n

                                                                                    \r\n

                                                                                    The design of the platform to meet the needs of the Analytics Operating Model<\/span> is being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                    \r\n
                                                                                    \r\n

                                                                                    Defined<\/p>\r\n <\/div> \r\n

                                                                                    \r\n

                                                                                    The design of the platform to meet the needs of the Analytics Operating Model<\/span> has been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                    \r\n
                                                                                    \r\n

                                                                                    Achieved<\/p>\r\n <\/div> \r\n

                                                                                    \r\n

                                                                                    The platform design meets the needs of the Analytics Operating Model<\/span>.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                    \r\n
                                                                                    \r\n

                                                                                    Enhanced<\/p>\r\n <\/div> \r\n

                                                                                    \r\n

                                                                                    Platform design support for the needs of the Analytics Operating Model<\/span> is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                                                    8.4.2 Analytics Platform Supports Innovation and Production<\/h3>\r\n <\/div> \r\n
                                                                                    \r\n \r\n
                                                                                    \r\n\r\n \r\n
                                                                                    Description<\/h5>\r\n\r\n

                                                                                    A separate environment is needed for data discovery, development and testing before delivering models into production. Testing in this low risk, sandbox environment ensures appropriate testing takes place before the model<\/span> is used and relied upon by the organization. The sandbox must provide appropriate capacity for its computational requirements determined by the business needs. A sandbox environment requires proper security rules to ensure data protection and controlled user access.<\/p>\r\n\r\n\r\n

                                                                                    Objectives<\/h5>\r\n\r\n
                                                                                      \r\n
                                                                                    • Define and support the requirements for the innovation environments.<\/li>\r\n
                                                                                    • Define and support the requirements to segregate the development and test sandbox from the production environment.<\/li>\r\n
                                                                                    • Establish distinct design and change control processes for the sandbox, development, and production aspects of the platform.<\/li>\r\n
                                                                                    • Establish required data protection and controlled user access.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                      Advice<\/h5>\r\n\r\n

                                                                                      The nature of analytics is based on iterative experimentation, so development environments need a degree of agility that supports the ability to fail fast and fail safely. Non-production environments, especially a sandbox\/innovation environment, need a greater level of flexibility made possible by a sufficiently agile change management process<\/span> that can address multiple scenarios.<\/p>\r\n\r\n

                                                                                      There must be clear segregation of environments to ensure the change management process<\/span> is appropriate for each level. It is change management that enables the Analytics teams to be productive. Change management processes for sandbox environments must be flexible enough to support adequate turnaround times for experimentation. A rigidly separate environment must be provided for non-production model<\/span> testing, with clear demarcation separating it from production. The change management process<\/span> for production must be appropriately robust in comparison to the more flexible non-production environments.<\/p>\r\n\r\n

                                                                                      It is crucial to ensure that the innovation or sandbox environment is adequately set up to handle data that resembles production data and complies with all relevant data protection standards. This preparation allows for the migration and testing to be finalized before deploying to a production environment.<\/p>\r\n\r\n\r\n

                                                                                      Questions<\/h5>\r\n\r\n
                                                                                        \r\n
                                                                                      • Are there documented requirements distinguishing the sandbox\/innovation environments and production environments?<\/li>\r\n
                                                                                      • Are the memory, storage, and processing capabilities of the different environments documented?<\/li>\r\n
                                                                                      • Have the stakeholders (business, analytics) approved that the environments meet their requirements?<\/li>\r\n
                                                                                      • Has the design process<\/span> for each environment been assessed and put into operation?<\/li>\r\n
                                                                                      • Are different change control processes in place for each environment to support the business requirements and risk appetite of the organization?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                        Artifacts<\/h5>\r\n\r\n
                                                                                          \r\n
                                                                                        • Production and non-production environments strategy<\/li>\r\n
                                                                                        • Documented designs of sandbox, development and production environments<\/li>\r\n
                                                                                        • Documented change control processes for the sandbox<\/li>\r\n
                                                                                        • Evidence of engagement with stakeholders of policy<\/span> review\/implementation<\/li>\r\n
                                                                                        • Evidence of communication of strategy and policies<\/li>\r\n
                                                                                        • Evidence of user-access rights to productive and non-productive environments<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                          Scoring<\/h5>\r\n \r\n
                                                                                          \r\n\r\n
                                                                                          \r\n \r\n
                                                                                          \r\n
                                                                                          \r\n

                                                                                          Not Initiated<\/p>\r\n <\/div> \r\n

                                                                                          \r\n

                                                                                          The separate needs for innovation and production are not understood.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                          \r\n
                                                                                          \r\n

                                                                                          Conceptual<\/p>\r\n <\/div> \r\n

                                                                                          \r\n

                                                                                          The separate needs for innovation and production are not understood, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                          \r\n
                                                                                          \r\n

                                                                                          Developmental<\/p>\r\n <\/div> \r\n

                                                                                          \r\n

                                                                                          The separate needs for innovation and production are being defined.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                          \r\n
                                                                                          \r\n

                                                                                          Defined<\/p>\r\n <\/div> \r\n

                                                                                          \r\n

                                                                                          The separate needs for innovation and production have been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                          \r\n
                                                                                          \r\n

                                                                                          Achieved<\/p>\r\n <\/div> \r\n

                                                                                          \r\n

                                                                                          The platform addresses the separate needs for innovation and production.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                          \r\n
                                                                                          \r\n

                                                                                          Enhanced<\/p>\r\n <\/div> \r\n

                                                                                          \r\n

                                                                                          The need for the platform to address the separate needs for innovation and production is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                                                          8.4.3 Analytics Platform Version Management<\/h3>\r\n <\/div> \r\n
                                                                                          \r\n \r\n
                                                                                          \r\n\r\n \r\n
                                                                                          Description<\/h5>\r\n\r\n

                                                                                          There must be controlled management of change to all models developed within the analytics platform and a documented process<\/span> for recording the changes. Effective governance and change control of the models must be in place and must be auditable.<\/p>\r\n\r\n\r\n

                                                                                          Objectives<\/h5>\r\n\r\n
                                                                                            \r\n
                                                                                          • Ensure that changes to the analytics models are made with appropriate authorization.<\/li>\r\n
                                                                                          • Ensure that changes are tracked and the nature of each change is documented and auditable.<\/li>\r\n
                                                                                          • Ensure that models are only released into the production environment through the controlled process<\/span> of the appropriate test-environments release mechanisms.<\/li>\r\n
                                                                                          • Ensure that appropriate versioning and archiving are in place for data sets used to train and validate models.<\/li>\r\n
                                                                                          • Address requirements to re-run analytics on historical data with the version of the model<\/span> used at that point in time.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                            Advice<\/h5>\r\n\r\n

                                                                                            Analytical models should follow the change control process<\/span> and the organization’s software development life cycle process<\/span>. Seek concurrence through discussion with the Technology function<\/span>, the change management function<\/span>, and connected business functions.<\/p>\r\n\r\n

                                                                                            Maintain documentation that explains changes made to models. This documentation must trace version history to know which versions of which models are used in which implementations.<\/p>\r\n\r\n

                                                                                            Document the process<\/span> for the creation and storage of retrievable backups of previous versions of code and data sets. These backup files are needed in the event of errors in the upgrade or if the analysis provided by previous versions needs to be validated.<\/p>\r\n\r\n

                                                                                            While this section focuses on the need for version control for all analytical models, an Analytics organization needs to ensure that there is version control in all analyses designed and deployed on the platform including those with simple calculations or data aggregations. This will ensure that the most recent number is referenced and that if there are changes to the analytical approach, the Analytics practitioners and their stakeholders understand them and are aware of them.<\/p>\r\n\r\n\r\n

                                                                                            Questions<\/h5>\r\n\r\n
                                                                                              \r\n
                                                                                            • Is there a change control process<\/span> for amendments to analytics models on the platform?<\/li>\r\n
                                                                                            • Is the defined change control process<\/span> in place and understood by the responsible individuals within the company?<\/li>\r\n
                                                                                            • Does documentation exist to show and explain the changes made to models? <\/li>\r\n
                                                                                            • Are previous code versions and data sets available to ensure understanding of previous model<\/span> analyses?<\/li>\r\n
                                                                                            • Does the change control process<\/span> ensure appropriate authorization for changes?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                              Artifacts<\/h5>\r\n\r\n
                                                                                                \r\n
                                                                                              • Model<\/span> specifications<\/li>\r\n
                                                                                              • Policies and procedures associated with version control for models and data sets<\/li>\r\n
                                                                                              • Model<\/span> release protocols and policies<\/li>\r\n
                                                                                              • Evidence of model<\/span> review and approval<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                Scoring<\/h5>\r\n \r\n
                                                                                                \r\n\r\n
                                                                                                \r\n \r\n
                                                                                                \r\n
                                                                                                \r\n

                                                                                                Not Initiated<\/p>\r\n <\/div> \r\n

                                                                                                \r\n

                                                                                                No version-control regime exists.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                \r\n
                                                                                                \r\n

                                                                                                Conceptual<\/p>\r\n <\/div> \r\n

                                                                                                \r\n

                                                                                                No version control regime exists, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                \r\n
                                                                                                \r\n

                                                                                                Developmental<\/p>\r\n <\/div> \r\n

                                                                                                \r\n

                                                                                                A version control regime is being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                \r\n
                                                                                                \r\n

                                                                                                Defined<\/p>\r\n <\/div> \r\n

                                                                                                \r\n

                                                                                                A version control regime has been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                \r\n
                                                                                                \r\n

                                                                                                Achieved<\/p>\r\n <\/div> \r\n

                                                                                                \r\n

                                                                                                The version control regime has been put in place and is being followed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                \r\n
                                                                                                \r\n

                                                                                                Enhanced<\/p>\r\n <\/div> \r\n

                                                                                                \r\n

                                                                                                Adherence to the version control regime is established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                                                                8.4.4 Data Anonymization Strategy<\/h3>\r\n <\/div> \r\n
                                                                                                \r\n \r\n
                                                                                                \r\n\r\n \r\n
                                                                                                Description<\/h5>\r\n\r\n

                                                                                                Data anonymization strategies can help to ensure that data used during the development phases of models complies with the appropriate regulatory regimes governing the organization and best practices regarding data privacy. Data anonymization also applies to commercially sensitive confidential data, such as company results before their release.<\/p>\r\n\r\n

                                                                                                The obfuscation capability is important for non-production testing environments and, in some cases, can also be relevant to production environments. Where external professional testers have access to test environments, non-production environments must store the minimum amount of personally identifiable or commercially sensitive information.<\/p>\r\n\r\n\r\n

                                                                                                Objectives<\/h5>\r\n\r\n
                                                                                                  \r\n
                                                                                                • Implement all relevant policies and develop the process<\/span> and procedures to identify the data that should be classed as commercially sensitive or personally identifiable information<\/span>, using the organization’s data classification<\/span> system to help determine the level and sophistication of obfuscation that is required.<\/li>\r\n
                                                                                                • Develop methods to obfuscate data by masking or blurring it, as needed by the business and approved by the compliance and regulatory teams.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                  Advice<\/h5>\r\n\r\n

                                                                                                  Collaborating within a cross-functional team that encompasses Privacy, Legal, Compliance, and other appropriate departments, determine the data classifications that define which information is considered commercially sensitive or classified as Personally Identifiable Information<\/span> in accordance with the applicable regulatory framework. These classifications will dictate the extent of obfuscation or deletion required for the data. Confirm whether data anonymization is needed for production and non-production models and whether it applies to model<\/span> outputs as well as inputs.<\/p>\r\n\r\n\r\n

                                                                                                  Questions<\/h5>\r\n\r\n
                                                                                                    \r\n
                                                                                                  • Are data anonymization requirements understood?<\/li>\r\n
                                                                                                  • Is there a process<\/span> documented and followed to ensure regulatory compliance in the use of sensitive data (personal and\/or commercial)?<\/li>\r\n
                                                                                                  • Have obfuscation techniques been established and adopted?<\/li>\r\n
                                                                                                  • If sensitive data needs to be used to ensure accurate reporting and prediction optimization, is there a process<\/span> to ensure that the sensitive or restricted data utilized is obscured or deleted after use?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                    Artifacts<\/h5>\r\n\r\n
                                                                                                      \r\n
                                                                                                    • Evidence of data anonymization policies, referencing data types and detailing specific requirements for production and non-production environments<\/li>\r\n
                                                                                                    • Non-production environments strategy including the management of data replication across environments<\/li>\r\n
                                                                                                    • List of stakeholders and evidence of bi-directional communication and recognition of relevant policies<\/li>\r\n
                                                                                                    • Documentation of obfuscation techniques with guidance on how and when to apply them<\/li>\r\n
                                                                                                    • Evidence of data obfuscation\/anonymization of relevant models\/model<\/span> outputs<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                      Scoring<\/h5>\r\n \r\n
                                                                                                      \r\n\r\n
                                                                                                      \r\n \r\n
                                                                                                      \r\n
                                                                                                      \r\n

                                                                                                      Not Initiated<\/p>\r\n <\/div> \r\n

                                                                                                      \r\n

                                                                                                      No data anonymization strategies exist.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                      \r\n
                                                                                                      \r\n

                                                                                                      Conceptual<\/p>\r\n <\/div> \r\n

                                                                                                      \r\n

                                                                                                      No data anonymization strategies exist, but the need is recognized and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                      \r\n
                                                                                                      \r\n

                                                                                                      Developmental<\/p>\r\n <\/div> \r\n

                                                                                                      \r\n

                                                                                                      Data anonymization strategies are being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                      \r\n
                                                                                                      \r\n

                                                                                                      Defined<\/p>\r\n <\/div> \r\n

                                                                                                      \r\n

                                                                                                      Data anonymization strategies have been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                      \r\n
                                                                                                      \r\n

                                                                                                      Achieved<\/p>\r\n <\/div> \r\n

                                                                                                      \r\n

                                                                                                      Data anonymization strategies are supported and are being used.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                      \r\n
                                                                                                      \r\n

                                                                                                      Enhanced<\/p>\r\n <\/div> \r\n

                                                                                                      \r\n

                                                                                                      The use and support of data anonymization strategies are established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                                                                      8.4.5 Platform Scalability Management<\/h3>\r\n <\/div> \r\n
                                                                                                      \r\n \r\n
                                                                                                      \r\n\r\n \r\n
                                                                                                      Description<\/h5>\r\n\r\n

                                                                                                      Business requirements change rapidly. The analytics model<\/span> environment must have the flexibility to cope with new data without requiring significant redesign. The model<\/span> environment needs to be able to provide an increase in data computing power requirements to address forecasted business growth and the growing sophistication of models. The costs of computational power need to be tracked. There must be an understanding of how additional requirements could be accommodated, and potential costs must be estimated in advance.<\/p>\r\n\r\n\r\n

                                                                                                      Objectives<\/h5>\r\n\r\n
                                                                                                        \r\n
                                                                                                      • Understand the processing power capacity and flexibility potentially needed for the analytics model<\/span> environment.<\/li>\r\n
                                                                                                      • Support the ability to scale up and down to accommodate planned requirements.<\/li>\r\n
                                                                                                      • Establish a mechanism for estimating and tracking model<\/span> processing costs.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                        Advice<\/h5>\r\n\r\n

                                                                                                        A process<\/span> should be established for stakeholders to provide direction on what future requirements the analytics models may be required to support. These requirements provide input for capacity planning. They should include data volumes and an estimate of the analytical workloads.<\/p>\r\n\r\n

                                                                                                        The scalability requirements should be reflected in the technology roadmap for Analytics. They should establish a position for the use of both on-premises and cloud infrastructure as appropriate for the organization.<\/p>\r\n\r\n

                                                                                                        The costs of the analytics platform should be tracked and reviewed against expectations by the stakeholders to ensure the environments are sized appropriately. Assess and quantify the business benefits obtained from the model<\/span> outputs to determine if the costs of the models and processing and the costs of idle capacity that supports scalability are justified.<\/p>\r\n\r\n\r\n

                                                                                                        Questions<\/h5>\r\n\r\n
                                                                                                          \r\n
                                                                                                        • Is there business direction on future requirements and strategy that the analytics models are required to support?<\/li>\r\n
                                                                                                        • Are future data volumes and workloads understood and quantified?<\/li>\r\n
                                                                                                        • Are volume and workload requirements documented and reviewed by Analytics?<\/li>\r\n
                                                                                                        • Can the models accommodate increased data volumes or variables without requiring a complete redesign and the related costs?<\/li>\r\n
                                                                                                        • Are the costs of the analytics platform tracked and reviewed against expectations to ensure that environments are sized appropriately?<\/li>\r\n
                                                                                                        • Does the assessment include the costs of idle capacity?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                          Artifacts<\/h5>\r\n\r\n
                                                                                                            \r\n
                                                                                                          • Documentation evidencing production and non-production and low-level, non-functional requirements<\/li>\r\n
                                                                                                          • Non-production environments strategy<\/li>\r\n
                                                                                                          • Cost tracking of both non-production and production environments, including any utility computing<\/li>\r\n
                                                                                                          • Evidence of spending reviews and ROI for production and non-production environments<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                            Scoring<\/h5>\r\n \r\n
                                                                                                            \r\n\r\n
                                                                                                            \r\n \r\n
                                                                                                            \r\n
                                                                                                            \r\n

                                                                                                            Not Initiated<\/p>\r\n <\/div> \r\n

                                                                                                            \r\n

                                                                                                            Environment scalability requirements are not understood.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                            \r\n
                                                                                                            \r\n

                                                                                                            Conceptual<\/p>\r\n <\/div> \r\n

                                                                                                            \r\n

                                                                                                            Environment scalability requirements are not understood, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                            \r\n
                                                                                                            \r\n

                                                                                                            Developmental<\/p>\r\n <\/div> \r\n

                                                                                                            \r\n

                                                                                                            Environment scalability requirements are being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                            \r\n
                                                                                                            \r\n

                                                                                                            Defined<\/p>\r\n <\/div> \r\n

                                                                                                            \r\n

                                                                                                            Environment scalability requirements have been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                            \r\n
                                                                                                            \r\n

                                                                                                            Achieved<\/p>\r\n <\/div> \r\n

                                                                                                            \r\n

                                                                                                            Environment scalability requirements are understood and supported.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                            \r\n
                                                                                                            \r\n

                                                                                                            Enhanced<\/p>\r\n <\/div> \r\n

                                                                                                            \r\n

                                                                                                            Understanding and support of environment scalability requirements are established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                                                                            8.5 Model Development Life Cycle<\/h3>\r\n <\/div>\r\n\r\n
                                                                                                            \r\n \r\n
                                                                                                            \r\n\r\n\r\n

                                                                                                            While some analytics activities will be exploratory or one-off, Analytics must be able to deploy models into production in a controlled and governed manner. Testing, approval, and release processes are central to this, along with processes for regular review of deployed models. These must be aligned with the organization’s governance approaches for data ethics and privacy. Requirements to understand and control model<\/span> bias must be addressed, as must the need to be able to explain how model<\/span> decisions have been reached.<\/p>\r\n\r\n\r\n \r\n\r\n <\/div>\r\n <\/div> \r\n\r\n\r\n\r\n

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

                                                                                                            8.5.1 Model Development Processes<\/h3>\r\n <\/div> \r\n
                                                                                                            \r\n \r\n
                                                                                                            \r\n\r\n \r\n
                                                                                                            Description<\/h5>\r\n\r\n

                                                                                                            Before release into an operational environment, models must be tested to ensure that they are performing as expected and in consonance with all model<\/span> specifications. Model<\/span> validation should include thorough review and testing of assumptions and analytical techniques and reviews to ensure that the data are not misused and remain easily auditable. This validation includes alignment with the code of data ethics and data privacy governance. The satisfactory outcome of testing and approval for release should be formalized by the official designated for this purpose. The model<\/span> should be released following established release protocols.<\/p>\r\n\r\n

                                                                                                            The performance of the model<\/span> may change as ingested data changes over time, potentially affecting the efficacy of the model<\/span>’s original intent. Its performance and its continued adherence to model<\/span> specifications must be reviewed periodically, and any time there is a change to model<\/span> specifications.<\/p>\r\n\r\n\r\n

                                                                                                            Objectives<\/h5>\r\n\r\n
                                                                                                              \r\n
                                                                                                            • Define formal processes for model<\/span> testing, validation, approval, release, and periodic review.<\/li>\r\n
                                                                                                            • Ensure the authority for model<\/span> approval is clear and appropriate.<\/li>\r\n
                                                                                                            • Ensure that models (released or pending) deployed into production environments are performing as expected and in consonance with each model<\/span>’s specifications.<\/li>\r\n
                                                                                                            • Establish safeguards to ensure model<\/span> release into production minimizes disruption to the organization’s operations and protects against data breaches and corruption of data.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                              Advice<\/h5>\r\n\r\n

                                                                                                              As part of the model<\/span> testing, a wide range of inputs must be run through the model<\/span> to ensure that it is performing as expected. Such input sets may include test data, current data, and artificially created representative samples of input data that could theoretically, even if rarely, arise in operations. Model<\/span> outputs should be checked for any unintended consequence arising from using the model<\/span>, such as unfair bias or undesirable business outcomes. Model<\/span> testing and controls should be automated where possible.<\/p>\r\n\r\n

                                                                                                              The individuals authorized to approve a model<\/span> should have input to the specifications of the portfolio of evidence to be provided for review in the approval. They should understand how the model<\/span> works and the business objectives it is designed to meet. They should also have a broader awareness of the overall business function<\/span> context in which the model<\/span> will operate and of governance and ethical parameters.<\/p>\r\n\r\n

                                                                                                              To ensure responsible use of data, it is essential to validate all data in models prior to their release into production environments, preventing potential misuse. Additionally, the processes of model<\/span> development, validation, approval, and release must align with established data ethics governance and privacy governance structures and guidelines. This includes ensuring that all stakeholders involved in the approval and release of models have a clear understanding of privacy governance requirements. Ultimately, a cohesive framework that integrates both data ethics and privacy considerations is crucial for the integrity and compliance of model<\/span> operations.<\/p>\r\n\r\n

                                                                                                              Consideration of data ethics needs to be embedded in the end-to-end process<\/span> of model<\/span> development and management.<\/p>\r\n\r\n

                                                                                                              Compliance of a model<\/span> with privacy requirements must be understood and confirmed before a model<\/span> is released but should already be considered at the design stage.<\/p>\r\n\r\n\r\n

                                                                                                              Questions<\/h5>\r\n\r\n
                                                                                                                \r\n
                                                                                                              • Do formal procedures exist for model<\/span> testing, approval, release, and periodic review?<\/li>\r\n
                                                                                                              • Is the authority for model<\/span> approval designated at the appropriate level of seniority?<\/li>\r\n
                                                                                                              • Have stakeholders approved the enforcement of the procedures for testing, approval, release, and review?<\/li>\r\n
                                                                                                              • Do models perform as expected and in consonance with their specifications?<\/li>\r\n
                                                                                                              • Have safeguards been established to ensure model<\/span> release minimizes disruption to operations and protects against data corruption and breaches?<\/li>\r\n
                                                                                                              • Is there a process<\/span> in place to ensure a formal Code of Data Ethics and associated guidance are reviewed and remain up to date?<\/li>\r\n
                                                                                                              • Is there a process<\/span> in place to review all models in production when the privacy requirements change?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                                Artifacts<\/h5>\r\n\r\n
                                                                                                                  \r\n
                                                                                                                • Model<\/span> specifications<\/li>\r\n
                                                                                                                • Model<\/span> testing, approval, and review procedures<\/li>\r\n
                                                                                                                • Evidence of automation of model<\/span> tests<\/li>\r\n
                                                                                                                • Model<\/span> release protocols and policies<\/li>\r\n
                                                                                                                • Details of model<\/span> input datasets and outputs<\/li>\r\n
                                                                                                                • Schedule of periodic model<\/span> reviews<\/li>\r\n
                                                                                                                • Evidence of model<\/span> review and approval<\/li>\r\n
                                                                                                                • List of stakeholders and evidence of approval of enforcement of procedures<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                                  Scoring<\/h5>\r\n \r\n
                                                                                                                  \r\n\r\n
                                                                                                                  \r\n \r\n
                                                                                                                  \r\n
                                                                                                                  \r\n

                                                                                                                  Not Initiated<\/p>\r\n <\/div> \r\n

                                                                                                                  \r\n

                                                                                                                  No model<\/span> testing, approval, release, and regular review processes exist.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                  \r\n
                                                                                                                  \r\n

                                                                                                                  Conceptual<\/p>\r\n <\/div> \r\n

                                                                                                                  \r\n

                                                                                                                  No model<\/span> testing, approval, release, and regular review processes exist, but the need is recognized and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                  \r\n
                                                                                                                  \r\n

                                                                                                                  Developmental<\/p>\r\n <\/div> \r\n

                                                                                                                  \r\n

                                                                                                                  Model<\/span> testing, approval, release, and regular review processes are being developed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                  \r\n
                                                                                                                  \r\n

                                                                                                                  Defined<\/p>\r\n <\/div> \r\n

                                                                                                                  \r\n

                                                                                                                  Model<\/span> testing, approval, release, and regular review processes have been defined, reviewed, and approved.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                  \r\n
                                                                                                                  \r\n

                                                                                                                  Achieved<\/p>\r\n <\/div> \r\n

                                                                                                                  \r\n

                                                                                                                  Model<\/span> testing, approval, release, and regular review processes are in place and effective.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                  \r\n
                                                                                                                  \r\n

                                                                                                                  Enhanced<\/p>\r\n <\/div> \r\n

                                                                                                                  \r\n

                                                                                                                  Effective model<\/span> testing, approval, release, and regular review processes are established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                                                                                  8.5.2 Model Bias Management<\/h3>\r\n <\/div> \r\n
                                                                                                                  \r\n \r\n
                                                                                                                  \r\n\r\n \r\n
                                                                                                                  Description<\/h5>\r\n\r\n

                                                                                                                  Analytics stakeholders need to be aware of any prejudices and unfairness of models and any unintended consequences they may cause. This type of model<\/span> bias is a governance issue and must be addressed with appropriate checks and balances that include awareness, mitigation, and controls. Models must be subject to active management of bias that provides for ongoing assessment and validation of algorithms, data sets, and model<\/span> outcomes.<\/p>\r\n\r\n\r\n

                                                                                                                  Objectives<\/h5>\r\n\r\n
                                                                                                                    \r\n
                                                                                                                  • Establish processes and controls to ensure that input data sets do not introduce model<\/span> bias.<\/li>\r\n
                                                                                                                  • Ensure that model<\/span> bias and its effects are identified.<\/li>\r\n
                                                                                                                  • Establish procedures for addressing model<\/span> bias once identified.<\/li>\r\n
                                                                                                                  • Ensure that the shortcomings of algorithms are understood, and they are not applied to questions where answers will be invalidated by algorithmic bias.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                                    Advice<\/h5>\r\n\r\n

                                                                                                                    Analytics model<\/span> results are based on the data inputs to the model<\/span>, either when created and trained or when running in production. Bias arises when that data is not representative of the real world, whether missing key variables that would lead to different decisions or including human-produced content that incorporates biases of those persons. Many organizations are establishing Data Ethics committees charged with reviewing models and their outcomes for signs of intended or unintended bias.<\/p>\r\n\r\n

                                                                                                                    To minimize the harmful effects of bias, stakeholders need to be aware of the possible bias in any model<\/span>. They must understand the various types of bias and how each can impact data, analysis, and decisions.<\/p>\r\n\r\n

                                                                                                                    Identification and management of bias must be incorporated in the formal procedures for model<\/span> approval and regular review. Regular reviews of models must include monitoring for sudden or creeping bias being introduced as the models are exposed to new data in production.<\/p>\r\n\r\n\r\n

                                                                                                                    Questions<\/h5>\r\n\r\n
                                                                                                                      \r\n
                                                                                                                    • Are stakeholders aware of the potential sources of model<\/span> bias?<\/li>\r\n
                                                                                                                    • Is the analysis of model<\/span> bias included in the analytics methodology and model<\/span> documentation standard<\/span>?<\/li>\r\n
                                                                                                                    • Are there procedures and controls to address bias in model<\/span> input data?<\/li>\r\n
                                                                                                                    • Are model<\/span> shortcomings documented and considered in decisions on the application of the model<\/span>?<\/li>\r\n
                                                                                                                    • Is model<\/span> bias addressed in procedures of model<\/span> approval and regular review?<\/li>\r\n
                                                                                                                    • Are judgment-based decisions on model<\/span> bias risk made at an appropriate level of seniority?<\/li>\r\n
                                                                                                                    • Is there a regular review with appropriate specialists to determine if there is drift in the model<\/span> resulting in bias?<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                                      Artifacts<\/h5>\r\n\r\n
                                                                                                                        \r\n
                                                                                                                      • Stakeholder<\/span> education material on model<\/span> bias<\/li>\r\n
                                                                                                                      • Procedures for the analysis of model<\/span> bias<\/li>\r\n
                                                                                                                      • Procedures and controls for review of bias in input data sets<\/li>\r\n
                                                                                                                      • Documented analysis of model<\/span> bias<\/li>\r\n
                                                                                                                      • Documentation of model<\/span> shortcomings and limitations<\/li>\r\n
                                                                                                                      • Evidence of model<\/span> bias and shortcomings considered in model<\/span> deployment decisions<\/li>\r\n
                                                                                                                      • Procedures for regular audit of models to ensure bias has not arisen<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                                        Scoring<\/h5>\r\n \r\n
                                                                                                                        \r\n\r\n
                                                                                                                        \r\n \r\n
                                                                                                                        \r\n
                                                                                                                        \r\n

                                                                                                                        Not Initiated<\/p>\r\n <\/div> \r\n

                                                                                                                        \r\n

                                                                                                                        Model<\/span> bias is not understood or managed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                        \r\n
                                                                                                                        \r\n

                                                                                                                        Conceptual<\/p>\r\n <\/div> \r\n

                                                                                                                        \r\n

                                                                                                                        Model<\/span> bias is not understood or managed, but the need is recognized, and the development is being discussed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                        \r\n
                                                                                                                        \r\n

                                                                                                                        Developmental<\/p>\r\n <\/div> \r\n

                                                                                                                        \r\n

                                                                                                                        Processes are being developed to ensure model<\/span> bias is understood and managed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                        \r\n
                                                                                                                        \r\n

                                                                                                                        Defined<\/p>\r\n <\/div> \r\n

                                                                                                                        \r\n

                                                                                                                        Processes have been defined, reviewed, and approved to ensure model<\/span> bias is understood and managed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                        \r\n
                                                                                                                        \r\n

                                                                                                                        Achieved<\/p>\r\n <\/div> \r\n

                                                                                                                        \r\n

                                                                                                                        Processes have been established and implemented to ensure that model<\/span> bias is understood and effectively managed.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n

                                                                                                                        \r\n
                                                                                                                        \r\n

                                                                                                                        Enhanced<\/p>\r\n <\/div> \r\n

                                                                                                                        \r\n

                                                                                                                        Understanding and effective management of model<\/span> bias are established as part of business-as-usual practice with a continuous improvement routine.<\/p>\r\n <\/div> \r\n <\/div> \r\n \r\n <\/div> \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

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

                                                                                                                        8.5.3 Model Requirements Traceability<\/h3>\r\n <\/div> \r\n
                                                                                                                        \r\n \r\n
                                                                                                                        \r\n\r\n \r\n
                                                                                                                        Description<\/h5>\r\n\r\n

                                                                                                                        Requirements for explaining how a model<\/span> works and reaches its outcomes should be precise and must be incorporated into the modeling process<\/span> and the operational processes that support the models. Transparency of how a model<\/span> works is critical to recognizing bias and aligning business processes and activities to achieve non-biased outcomes.<\/p>\r\n\r\n\r\n

                                                                                                                        Objectives<\/h5>\r\n\r\n
                                                                                                                          \r\n
                                                                                                                        • Define requirements for model<\/span> explainability in business terms.<\/li>\r\n
                                                                                                                        • Assign accountability for model<\/span> explainability during the requirements phase of the modeling process<\/span>.<\/li>\r\n
                                                                                                                        • Perform additional steps to mitigate ambiguity in requirements for model<\/span> explainability.<\/li>\r\n
                                                                                                                        • Incorporate processes to ensure requirements for model<\/span> explainability result in a clear understanding of how a model<\/span> works and for model<\/span> transparency.<\/li>\r\n <\/ul>\r\n\r\n\r\n
                                                                                                                          Advice<\/h5>\r\n\r\n

                                                                                                                          Model<\/span> explainability requirements must specify how easily models can be understood and how easy it must be to understand the cause of decisions in a model<\/span>. The goal is for stakeholders to be able to explain what models do and how they do it, to both internal and external audiences. Model<\/span> explainability must be able to stand up to Internal Audit or external regulatory reviews. Explanations should be consistent.<\/p>\r\n\r\n

                                                                                                                          Identify and consult the stakeholders who can understand and discuss the requirements for model<\/span> explainability.<\/p>\r\n

                                                                                                                          Include requirements for model<\/span> explainability in the organization’s analytics methodology and model<\/span> documentation standard<\/span>. Embedding standards into the fabric of an organization is a critical step in achieving model<\/span> explainability.<\/p>\r\n

                                                                                                                          Update the organization’s processes, standards, and policies as the adoption of requirements for model<\/span> explainability increases. Keep documentation and processes current. The alternative results in tribal knowledge, operational silos, and increased risk that intellectual property and knowledge are lost, making model<\/span> explainability more difficult.<\/p>\r\n\r\n

                                                                                                                          Establish methods to monitor and continuously improve model<\/span> explainability. The goal of continuous improvement is to provide opportunities for stakeholders to enhance model<\/span> explainability to meet business objectives. Sources of improvement ideas include surveys, interviews and peer reviews, success stories, and analysis of gaps highlighted by monitoring and measurement. Bring new ideas and thinking into the organization by keeping pace with emerging and waning industry standards, technology improvements, and by comparing processes and outcomes to those of competitors, allies, and other industries.<\/p>\r\n\r\n\r\n

                                                                                                                          Questions<\/h5>\r\n\r\n