B. Course Content - Day 1

DCAM FRAMEWORK
DATA MANAGEMENT CAPABILITY

ASSESSMENT MODEL
COURSE STRUCTURE
Topics
EDM Council Overview
Current State: Data Management Industry and the DCAM Model
C1: DM Strategy & Business Case
C2: DM Program & Funding Model
C3: Business & Data Architecture
C4: Data & Technology Architecture
C5: Data Quality Management
C6: Data Governance
C7: Data Control Environment
Conducting a DCAM Assessment
DCAM Industry Survey
DCAM User Group & DCAM Accreditation & Certification
www.edmcouncil.org
Confidential Copyright
Copyright ©©2021
2021EDM
EDMCouncil
CouncilInc.
Inc. Page 1
DAY 1 Sydney
Section Start Time Finish
Introductions 11:00 AM 11:30 AM
Data Management Industry Overview 11:30 AM 12:15 PM
DCAM Overview 12:15 PM 1:00 PM
Break 1:00 PM 1:30 PM
C1: DM Strategy & Business Case 1:30 PM 2:15 PM
C2: DM Program & Funding Model 2:15 PM 3:00 PM
Break 3:00 PM 3:45 PM
C3: Business & Data Architecture 3:45 PM 4:15 PM
C4: Data & Technology Architecture 4:15 PM 4:45 PM
Conclusion - End Day 1 4:45 PM 5:00 PM
www.edmcouncil.org
Copyright ©©2021
2021EDM
EDMCouncil
CouncilInc.
Inc. Page 2
COPYRIGHT NOTICE
Please take a moment to read.
The Data Management Capability Assessment Model Training Materials (DCAM®) (“Training Materials”) is
being provided to the Recipient, (“Recipient”) as a Member or Guest of the EDM Council, Inc. (“EDM
Council”). The Training Materials and all related materials are the sole property of EDM Council, and all
rights, titles, and interests therein are vested in EDM Council. Recording any or all portions of the DCAM
training (in person or virtual training) is prohibited. The Training Materials, or any portion thereof, may not
be copied by any Recipient and may not be distributed to, or made available for the use by any party other
than Recipient, unless, in each case, Recipient has obtained the prior written authorization of EDM Council.
Except as provided above, the Training Materials, or any portion thereof, may not be used in any way by
Recipient, its officers, employees or agents or by any other party without the prior written consent of EDM
Council. The Training Materials may only be used by Recipient for external purposes if it has entered into a
separate licensing agreement with EDM Council governing the terms for such use. By reviewing or using
the Training Materials, or any portion thereof, the Recipient (and each person reviewing or using the
Training Materials) agrees to the terms set forth above. Any copying or use of the Training Materials except
as set forth above is strictly prohibited.
DCAM® is a registered trademark of the EDM Council, Inc., and may not be used or copied without the
prior written authorization of the EDM Council, Inc.
© 2021 EDM Council Inc., All rights Reserved.
Confidential Copyright © 2021 EDM Council Inc. Page 3

DCAM v2 Component 1
Data Management
Capability Assessment
Data Management Strategy
Model & Business Case
3 Capabilities
13 Sub-capabilities
35 Objectives
CONFIDENTIAL | © 2021 EDM Council Inc. 4

1.0 DATA MANAGEMENT STRATEGY AND BUSINESS CASE
The Data Management Strategy and

Business Case (DMS&BC) determines how
data management is defined, organized,
funded, governed and embedded into the
operations of the organization
• Defines the goals, objectives and scope of the data

initiative as aligned to the business objectives
• Describes how the organization will be mobilized in
order to implement a successful data management
initiative
Importance of the physical documentation should not be underestimated. The

DMS&BS document is the primary internal marketing tool to drive
understanding and support for the Data Management initiative

Articulates the vision

• Articulates the value and opportunity of an organization-wide Data Management initiative
• Rationalizes the business case for Data Management throughout the organization
• Align with the business strategy, objectives, and priorities, including prioritizing data
based on criticality to the business
• Defines the Data Management Target State
Identifies the business value

• The Data Management Business Case is the cost-benefit
realization of a set of activities and deliverables expected from the
Data Management Initiative
• Describes the defensive and offensive benefits of the initiative
• Helps management understand the costs, benefits and risks
associated with the data management initiative

Flows like Water…
The Data Management Strategy and Business

Case is not static
• Your Data Management Strategy must be a living artifact that is visibly endorsed by
executive management, supported and prioritized by stakeholders and enabled by
technology
• Should be routinely revisited and reevaluated
• Must evolve as priorities and needs of the organization change

C
A 1.1
P Data Does a strategy exist? Is it
Management documented? Has it been reviewed by
A Strategy
key stakeholders?
Specified
B and Shared
I
1.2
L Data Defining the data strategy is dependent upon
Management
I Business
understanding and support the business
objectives
T Case is
Defined
I
E
1.3 The DMS & BC must articulate the
S The Data
vision of the data initiative and how it
Management
Vision is will be deployed across the
Defined organization

Capability 1.1 – The DM Strategy (DMS) is Specified and Shared
1.1.1 The DMS is developed, documented • DMS has been aligned with business, technology, and operations
and consolidated • DMS has been documented
• DMS has been published to all stakeholders
• Mapped to the high-level business objectives

1.1.2 The DMS is aligned with the high-level • Approved by the executive committee and stakeholders
organizational objectives • Processes established to ensure future alignment to org objectives
1.1.3 The DMS addresses the core strategy concepts from • Core concepts are captured from each DCAM component
each DCAM component • Prioritization aligns with business objectives
1.1.4 The DMS includes an established • Mechanism in place to capture feedback

• Feedback is collected and incorporated into the DMS
mechanism for approval • Strategy is approved
1.1.5 The DMS has been evaluated and • Internal audit has reviewed and approved
is enforceable. • Internal audit has determined that DM can be enforced via audit examinations
1.1.4 The DMS includes an established mechanism for approval
1.1.5 The DMS has been evaluated and is enforceable

1.1.3 The DMS addresses the core strategy concepts from each DCAM component
Program & Funding Data

Management
Strategy
Business/Data Architecture
Technology
Data Quality
Data Governance

1.1.1 The DMS is developed, documented • DMS has been aligned with business, technology, and operations
and consolidated • DMS has been documented
• DMS has been published to all stakeholders
• Mapped to the high-level business objectives

1.1.2 The DMS is aligned with the high-level • Approved by the executive committee and stakeholders
organizational objectives • Processes established to ensure future alignment to org objectives
1.1.3 The DMS addresses the core strategy concepts from • Core concepts are captured from each DCAM component
each DCAM component • Prioritization aligns with business objectives
1.1.4 The DMS includes an established • Mechanism in place to capture feedback

• Feedback is collected and incorporated into the DMS
mechanism for approval • Strategy is approved
1.1.5 The DMS has been evaluated and • Internal audit has reviewed and approved
is enforceable. • Internal audit has determined that DM can be enforced via audit examinations
1.1.4 The DMS includes an established mechanism for approval
1.1.5 The DMS has been evaluated and is enforceable

C
A 1.1
A Strategy is
key stakeholders?
Specified
B and Shared
I
1.2
Management
I Business
objectives
T Case is
Defined
I
E
S The Data
Management

Capability 1.2 – The DM Strategy Business Case is Defined
1.2.1 High-level business requirements • High-level Enterprise business requirements have been documented,
are documented verified and incorporated into the DMS
1.2.2 Business requirements have been prioritized, approved and • Business requirements have been prioritized
incorporated into the DMS • Regular review cycles have been established
• The DM Business Case is mapped to line-of-business priorities and

1.2.3 The DM business case is mapped to and objectives.
aligned with the DMS • The DM Business Case includes a review of the business
requirements to ensure ethical data practices
1.2.4 Expected DM outcomes are defined • Expected target state business objectives are defined and sequenced
• Current-to-Target State is defined and articulated
and sequenced
• The DM Business Case has been socialized

1.2.5 The DM business case is socialized and • Target objectives have been reviewed and validated
1.2.2 Business requirements have been prioritized, approved and incorporated into the DMS
validated by stakeholders • Outcomes, benefits and targets have been reviewed and approved
1.2.3 The DM business case is mapped to and aligned with the DMS
1.2.4 Expected DM outcomes are defined and sequenced
1.2.5 The DM business case is socialized and validated by stakeholders CONFIDENTIAL | © 2021 EDM Council Inc. 13
C
A 1.1
A Strategy is
key stakeholders?
Specified
B and Shared
I
1.2
Management
I Business
objectives
T Case is
defined
I
E
S The Data
Management

Capability 1.3 – The Strategic Vision is Defined
• Define what data that is needed to achieve the business objectives

1.3.1 The Data Content Strategy • Define the approach to new data sets (alternative data; unstructured; etc.)
is defined
• How will data be modeled? (relational; semantically; knowledge graph, etc.)
1.3.2 The Data Usage Strategy is • Addresses the vision for the use of advanced analytics methods and tools
identified • MUST include a review of the ethical use and outcome of data
1.3.3 The Data Management Deployment • Define the deployment (roll-out) strategy - what data is being
Strategy is communicated addressed first? To what areas of the firm? In what sequence?
1.3.2 The Data Usage Strategy is identified
1.3.3 The Data Management Deployment Strategy is communicated CONFIDENTIAL | © 2021 EDM Council Inc. 15
1.0 Data Management Strategy and Business Case
• In Summary: The Data Management Strategy and Business Case
Capabilities are…
1.1 The Data Management Strategy (DMS) is Specified and Shared
1.2 The Data Management Business Case is Defined
1.3 The Data Management Vision is Defined

DCAM FRAMEWORK
ASSESSMENT MODEL
COURSE STRUCTURE
Topics
Data Management Industry & DCAM Overview
C6: Data Governance
C8: Analytics Management
DCAM Industry Benchmark
DCAM User Group / Tools / Conclusion
www.edmcouncil.org
Copyright ©©2021
2021EDM
EDMCouncil
CouncilInc.
Inc. Page 17
DCAM v2 Component 2
Data Management
Data Management Program
Model & Funding Model
8 Capabilities
27 Sub-capabilities
101 Objectives

2.0 DATA MANAGEMENT PROGRAM & FUNDING MODEL
The Data Management Program and

Funding Model addresses the
capabilities required to
• Establish
• Operate
• Fund
the Data Management initiative
• The Office of Data Management (ODM) is established

• Proper processes are established to ensure sustainable funding
• Data management concepts are embedded into the operational
framework of the organization
DCAM and the Data Management Program
The Data Management Program component is a set of capabilities to manage the Office of
Data Management (ODM) including organizational structure, resource requirements, and
full range of Program Management Office activity.
• Establish roles and responsibilities
• Define the data management execution roadmap
• Engage stakeholders across the ecosystem
• Monitor and socialize data management performance
DCAM and the Data Management Funding Model
The Data Management Funding Model describes the overall framework and high-level
engagement of senior management used to ensure that the objectives and processes of
data management become a sustainably funded activity within the organization.
• Defines the mechanism to generate sustainable program capital
• Establishes cost-allocation methodologies
• Establishes funding prioritization and governance
• Tracks and reports program ROI
C
A
2.1 2.2
P The DM Funding Model
2.3 2.4
Organizational Roadmaps are
A Program is is Established Structure is Developed
Established
B Created
I Data Management Funding is Roles and Responsibilities Plans are

L program is formalized Secured are Defined Communicated
I
T
2.5 2.6 2.8
I Process Stakeholder
2.7
Program
Communications
E Excellence is Engagement and Training
Measured and
Established Established Tracked
S
Adherence to Standards and Enterprise Internal and Program Metrics
Best Practices Accountability External Established
Awareness

Capability 2.1 – The Data Management Program is Established
• Role of the DMP is formally established, supported and

2.1.1 The DMP Strategy and approach are communicated across the organization by executive management
defined and adopted
2.1.2 The DMP PMO is established and roles • Approved, chartered and appropriately staffed
and responsibilities are defined and implemented • Authorized to ensure and enforce alignment of activities
• Formal Data management processes are established

2.1.3 The DMP operational processes • Routines are formally scheduled and are taking place
are defined and implemented • Operational artifacts (topics; plans; minutes; etc.), are produced and shared
2.1.4 The DMP has the authority to enforce • DMP is operating collaboratively with DM stakeholders
adherence and compliance • DMP has the authority to enforce adherence to policy
2.1.2 The DMP PMO is established and roles and responsibilities are defined and implemented
• Data Management Strategy concepts are in-sync with the DMP concepts
2.1.5 The DMP concepts are
2.1.3 The DMP operational processes are defined and implemented • DM Program is aligned with stakeholder plans and roadmaps
reflected in the DMS • DM Program is approved by relevant stakeholders
2.1.4 The DMP has the authority to enforce adherence and compliance
2.1.5 The DMP concepts are reflected in the DMS

C
A
2.1 2.2
2.3 2.4
Established
B Created

I
T
2.5 2.6 2.8
2.7
Program
Communications
Measured and
S
Awareness

Capability 2.2 – The Funding Model is Established
2.2.1 The DM funding model is • The DM business case reflects enterprise and business-line
matched to business requirements, requirements, described in the data management strategy
implementation timelines and • Appropriate funding levels for sustained data operations
operational capabilities have been approved
• DM funding is aligned with organizational cycles

2.2.2 The DM funding model is aligned with the funding
• Funding is mapped to a multi-year implementation plan
processes of the organization
• Resource plans have been reviewed, reconciled and
approved by the DM PMO
2.2.3 Implementation of the DM funding • Funding is allocated by the operating units

• All data budgets are reviewed and approved
model is enforced • Data management organization is empowered to ensure line of business
funding meeting organizational data requirements
2.2.2 The DM funding model is aligned with the funding processes of the organization
2.2.3 Implementation of the DM funding model is enforced

C
A
2.1 2.2
2.3 2.4
Established
B Created

I
T
2.5 2.6 2.8
2.7
Program
Communications
Measured and
S
Awareness

Capability 2.3 – The Organizational Structure is Created
• The function of data management is formally created

2.3.1 The ODM is created • The Office of Data Management (ODM) is chartered
• The ODM is approved and supported by management
• There is an officially appointed owner of the data management program

2.3.2 The ODM has an
• The role is communicated through the organization
executive owner
• The role is backed by executive management
• Funding is approved
2.3.3 The ODM is funded and staffed
• Skillsets have been identified
by individuals with the required skill-set
• There is an approval to hire
2.3.2 The ODM has an executive owner
2.3.3 The ODM is funded and staffed by individuals with the required skill-set
C
A
2.1 2.2
2.3 2.4
Established
B Created

I
T
2.5 2.6 2.8
2.7
Program
Communications
Measured and
S
Awareness

Capability 2.4 – The Roadmaps for the DMP are Developed, Socialized,
and Approved
2.4.1 Program roadmaps are

• Data requirements drive data management roadmaps
defined and aligned with the
• Roadmaps are aligned with all aspects of the data management strategy
DMS
2.4.2 Program roadmaps are • DMP roadmaps are shared and aligned with the roadmaps of the
socialized and agreed to by stakeholders (i.e., architecture, technology, operational roadmaps)
stakeholders. • Stakeholders verify and approve DMP roadmap alignment
2.4.3 Project plans are developed • Project plans are developed and aligned to the programs’
implementation roadmaps
detailing deliverables, timelines, and
• Routine program review procedures are in place to track the
milestones
progress of development plans
2.4.2 Program roadmaps are socialized and agreed to by stakeholders
2.4.3 Project plans are developed detailing deliverables, timelines, and milestones CONFIDENTIAL | © 2021 EDM Council Inc. 28
C
A
2.1 2.2
2.3 2.4
Established
B Created

I
T
2.5 2.6 2.8
2.7
Program
Communications
Measured and
S
Awareness

Capability 2.5 – Data Management Process Excellence Program is

Established
• A centralized process excellence function is created within

2.5.1 Standardized Data Management processes the ODM
are designed and deployed organization-wide • A mechanism is in place to support the creation and adoption
of standard data management processes
• A formal function is established to participate in data mgt

2.5.2 Data Management processes are informed industry activities and events
by industry standards and best practices • Stakeholders are kept abreast of changes and events in
the data management industry
2.5.3 Data Management • Business Data Management performs routine self-assessments (QC)
processes are supported • Enterprise Data Management performs routine QA’s
by policy and are auditable • Internal audit performed routine overall program exams
2.5.2 Data Management processes are informed by industry standards and best practices
2.5.3 Data Management processes are supported by policy and are auditable CONFIDENTIAL | © 2021 EDM Council Inc. 30
C
A
2.1 2.2
2.3 2.4
Established
B Created

I
T
2.5 2.6 2.8
2.7
Program
Communications
Measured and
S
Awareness

Capability 2.6 – Stakeholder Engagement is Established and Confirmed
• Stakeholders are identified

2.6.1 Stakeholders commit to and are held • Responsibilities are communicated
accountable for the DMP deliverables • Stakeholders are held accountable via performance
reviews and compensation
2.6.2 Resource plans are aligned with and • Resources (skillsets) are aligned with data and business requirements
verified against initiative requirements. • Stakeholders have acquired necessary resources
• Stakeholders have allocated appropriate levels of funding

2.6.3 Funds are allocated and aligned to
to the data management program
program roadmaps and workstreams • Funding strategies are reviewed and approved
2.6.2 Resource plans are aligned with and verified against initiative requirements
2.6.3 Funds are allocated and aligned to program roadmaps and workstreams
C
A
2.1 2.2
2.3 2.4
Established
B Created

I
T
2.5 2.6 2.8
2.7
Program
Communications
Measured and
S
Awareness

Capability 2.7 – Communications and Training Programs are Designed

and Operational
• The message of data management is being actively

2.7.1 Internal communication plans
communicated to internal staff
have been defined and approved • Communicate plans are developed, shared and approved
• Communication plans with external regulators have been

2.7.2 Plans for communication with external developed and approved
regulatory bodies are defined and approved. • Regular interactions with regulatory bodies about data
management are taking place
• Formal Data management training programs have been

2.7.3 Formal training programs have
created and are operational
been defined and implemented • Training is mandated as an operational requirement
2.7.2 Plans for communication with external regulatory bodies are defined and approved
2.7.3 Formal training programs have been defined and implemented

C
A
2.1 2.2
2.3 2.4
Established
B Created

I
T
2.5 2.6 2.8
2.7
Program
Communications
Measured and
S
Awareness

Capability 2.8 – The DMP is Measured and Evaluated Against Business

Objectives
2.8.1 Program metrics are defined • Program metrics have been designed
and used to track progress • Stakeholders review/approve plans and approach for outcome metrics
• Metrics are tracked and reported to stakeholders including

2.8.2 Outcome metrics are defined and used executive management
to track against business objectives • Metrics inform and drive program decisions and modifications
• Establish metrics and thresholds

2.8.3 Process metrics are defined and used • Stakeholders review and approve the process metric plans and approach
to drive continuous improvement • Metrics inform and drive program decisions and modifications
• Metrics are tracked/ reported to stakeholders and executive management
2.8.4 Financial metrics for total • Total expense for the data management is captured/maintained and analyzed
• Methodology for capturing the financial benefits of the program is established
program costs and benefits (ROI) • Financial benefits are measured, monitored and used for making program
2.8.2 Outcome metricsare tracked
are defined and used toand reported
track against business objectives
decisions
2.8.3 Process metrics are defined and used to drive continuous improvement
2.8.4 Financial metrics for total program costs and benefits (ROI) are tracked and reported
2.0 Data Management Program and Funding Model
• In Summary: Data Management Program and Funding Model
capabilities are…
2.1 The Data Management Program (DMP) is Established
2.2 The DM Funding Model has been Established, Approved, and Adopted by the Organization
2.3 The Data Management Organizational Structure is Created and Implemented
2.4 The Roadmaps for the DMP are Developed, Socialized, and Approved
2.5 Data Management Process Excellence Program is Established
2.6 Stakeholder Engagement is Established and Confirmed
2.7 Communications and Training Programs are Designed and Operational
2.8 The DMP is Measured and Evaluated Against Business Objectives

DCAM FRAMEWORK
ASSESSMENT MODEL
COURSE STRUCTURE
Topics
C6: Data Governance
www.edmcouncil.org
Copyright ©©2021
2021EDM
EDMCouncil
CouncilInc.
Inc. Page 38
DCAM FRAMEWORK
ASSESSMENT MODEL
COURSE STRUCTURE
Topics
C6: Data Governance
www.edmcouncil.org Copyright © 2021 EDM Council Inc. CONFIDENTIAL | © 2021 EDM Council Inc. 39
DCAM v2 Component 3
Data Management
Business & Data
Model Architecture
4 Capabilities
14 Sub-capabilities
40 Objectives

3.0 BUSINESS & DATA ARCHITECTURE
The Business
BA + DA = IA
Architecture (BA) Information Architecture
and Data
Architecture (DA)
component is a set The path to integrated
Information Architecture
of capabilities to begins with the business,
ensure integration which informs what data is
between the needed, which in turn, informs
business process how technology should be
requirements and enabled
the execution of the
Data Architecture
function.

Business architecture defines the processes

required to meet the objectives of the business.
Business architecture is a discipline that "represents holistic,
multidimensional views of the capabilities, end‐to‐end value delivery,
information, and organizational structure of the business"
https://en.wikipedia.org/wiki/Business_architecture
Data Architecture speaks to the design, definition,

management and control of information content.
• DA identifies data domains, documents metadata, defines critical data
elements, establishes taxonomies and ontologies
• DA ensures that the meaning of data is precise and unambiguous,
and that the usage of data is consistent and transparent.
• DA ensures the requirements of the business are addressed

C
A
P
3.1 Formal focus on data
A Data
architecture is critical to 3.3 Required data is identified (logical),
Architecture Identify the and sources of the required data
B function is a successful data Data are documented (physical)
I established. management program
L
I
T 3.2
I Business
Architecture
E (BA) is
Business processes 3.4
Data is engineered
define and prioritize data Define the
Integrated structurally and semantically
S with Data requirements
Data
Architecture
(DA)

Capability 3.1 – Data Architecture (DA) function is established
• Define data architecture strategy and approach

3.1.1 The Data Architecture strategy and • Secure authority to enforce DA adherence and compliance
approach are defined and adopted through policy and procedure
• Fund and staff the data architecture function

• Secure the authority to enforce alignment with
3.1.2 The Data Architecture stakeholder roles and policy
responsibilities are defined and implemented • Hold individuals accountable and reward excellence
for the DA performance through annual reviews
• Formally establish the DA strategy and approach

• Obtain executive management sanctions for the DA strategy and
3.1.3 The Data Architecture operational approach
processes are defined and implemented • Secure authority to enforce DA adherence and compliance through
policy and procedure
3.1.2 The Data Architecture stakeholder roles and responsibilities are defined and implemented
3.1.3 The Data Architecture operational processes are defined and implemented
C
A
P
A Data
L
I
T 3.2
I Business
Architecture
E (BA) is
Data is engineered
Data
Architecture
(DA)

Capability 3.2 – Business Architecture (BA) is Integrated with Data

Architecture (DA)
• Develop a process optimization framework for the business architecture
3.2.1 Business Architecture defines
function
process input and output data • Identify input and output requirements of the business process
requirements • Engage the data architecture in business process design and optimization
• Define the process to evaluate the data usage restrictions of the

3.2.2 Business Data requirements must include data data
usage, data restrictions and data ethics considerations • Define data restrictions that include the ethics of data, use and
outcome
3.2.3 Business Architecture processes incorporate • Business Architecture collaborates with data
root cause fix of people or process architecture in performing root-cause analysis
3.2.4 Data Architecture governance is • Align Data Architecture governance with Business Architecture governance to
ensure semantic definitions, taxonomies and Critical Data Elements (CDEs) are
aligned with Business Architecture
3.2.2 Business data requirements must include data usage, data restrictions and data ethics considerations properly assigned and maintained
governance • Utilize DA governance to monitor the capture of business metadata
3.2.3 Business Architecture processes incorporate root cause fix of people or process
3.2.4 Data Architecture governance is aligned with Business Architecture governance

C
A
P
A Data
L
I
T 3.2
I Business
Architecture
E (BA) is
Data is engineered
Data
Architecture
(DA)

3.3.1 Logical data domains have been identified, documented, inventoried and authorized
Domains
Libraries
Staff Shelves
Books
George Souris's
Members
Authors
3.3.2 Physical data
3.3.3 repositories
has beenof data have been located, documented and inventoried
catalogued
Libraries
- PII & Sensitive

- Critical
Staff Shelves
Books
📌 Field 1
📌 Field 2
HR System 📌 Field 3
- Oracle Members
- On Premise Authors
Capability 3.3 – Identify the Data
• Identify and prioritize logical data domains (vs. databases)

3.3.1 Logical data domains have been identified, in collaboration with technology and the business owners
documented, inventoried and authorized (or SMEs)
• Physical databases associated with each logical domain

3.3.2 Physical repositories of data have are discovered and inventoried
been located, documented and inventoried • Link underlying physical repositories to the logical data
domains
• Create catalogue of data aligned to data domain

3.3.3 Physical data has been catalogued • Capture basic metadata on the data elements
• Make the data catalogue accessible to stakeholders
3.3.2 Physical repositories of data have been located, documented and inventoried
3.3.3 Physical data has been catalogued

C
A
P
A Data
L
I
T 3.2
I Business
Architecture
E (BA) is
Data is engineered
Data
Architecture
(DA)

Capability 3.4 – Define the Data

• Verify authoritative data domains with business SMEs
3.4.1 Enterprise entities are • Define and document conceptual and logical data
models
identified, defined, modeled and • Capture and document data object relationships
standardized • Publish authoritative data domain taxonomies and
ontologies
3.4.2 Business definitions are composed, • Document and verify business definitions
• Assign approved business definitions to defined
documented and approved by stakeholders
taxonomies
• Define identifiers for critical business elements

3.4.3 Unique identification and classification
• Assign, publish and mandate internal entity ID use
are defined, applied and in use • Align and cross-reference external industry identifiers
3.4.4 Metadata is defined,

• Metadata structures are defined, modeled and maintained across the
modeled and standardized
3.4.2 Business definitions are composed, documented and approved by stakeholders organization
3.4.3 Unique identification and classification are defined, applied and in use
3.4.4 Metadata is defined, modeled and standardized

3.0 Business & Data Architecture
• In Summary: Business & Data Architecture capabilities are…
3.1 Data Architecture (DA) function is Established
3.2 Business Architecture (BA) is Integrated with Data Architecture (DA)
3.3 Identify the Data
3.4 Define the Data

DCAM FRAMEWORK
ASSESSMENT MODEL
COURSE STRUCTURE
Topics
C6: Data Governance
www.edmcouncil.org Copyright © 2021 EDM Council Inc. CONFIDENTIAL | © 2021 EDM Council Inc. 54
DCAM v2 Component 4
Data Management
Data & Technology
Model Architecture
3 Capabilities
10 Sub-capabilities
36 Objectives

4.0 DATA & TECHNOLOGY ARCHITECTURE
The Data & Technology Architecture

component is a set of capabilities to
align the architectural requirements of
the business, data, and technology
across the organization.
• Data Architecture is the strategy and
execution of how data is designed (identified
and described) to support the business
objectives.
• Technology Architecture refers to the
strategy, design and implementation of the
technology infrastructure which supports the
defined business and data architecture.

C
4.1
A Technology
P Architecture
is defined in Technology Architecture enables the goals
A support of and objectives of the data program
the data
B management
I initiative
4.2
L DM Tool The data management tool stack is
Stack is
I Identified
defined and governed by data
management policy and procedure.
T and
Governed
I
E
4.3
S Operational Operational risk preparedness is
Risk shared collaboratively between
Planning is technology and data management
in Place

Capability 4.1 – Technology Architecture is defined in support of the data

management initiative
4.1.1 DM is engaged in the • Design an integrated technology architecture with business, data and technology
Technology vision and strategy • Stay on top of latest technology trends, including use of AI/ML and NLP
• Design and develop an integrated platform

4.1.2 DM is engaged in the definition and development of
infrastructure strategy and roadmap in collaboration
the organization-wide platform infrastructure
with business, data, and technology stakeholders
• Design and develop an integrated data storage strategy and roadmap

4.1.3 DM is engaged in the definition and development of
in collaboration with business, data and technology
the organization-wide data storage infrastructure
• Build and operationalize a storage management infrastructure
4.1.4 DM is engaged in the definition and development of the • Design and implement data distribution infrastructure
organization-wide data distribution infrastructure • Design and implement a data distribution governance
infrastructure
4.1.2 DM is engaged in the definition and development of the organization-wide platform infrastructure
4.1.3 DM is engaged in the definition and development of the organization-wide data storage infrastructure • Develop an integrated governance structure and policies
4.1.5 DM governance is aligned with TA governance
4.1.4 DM is engaged in the definition and development of the organization-wide data distribution infrastructure in alignment with the technology and data strategies
4.1.5 DM governance is aligned with TA governance
C
4.1
A Technology
P Architecture
the data
B management
I initiative
4.2
L DM Tool The data management tools stack is
Stack is
I Identified
defined in governed my data
T and
Governed
I
E
4.3
in Place

Capability 4.2 – DM Technology Tool Stack is Identified and Governed
• Design an integrated DM technology tool strategy

4.2.1 DM technology tool selection strategy • Obtain agreement from business, data and technology
is defined and verified by stakeholders • Socialize and govern the strategy
• Develop an integrated technology tool roadmap

4.2.2 Technology tool roadmap is developed • Include guidelines for new development as well as
and implemented decommission plans for non-standardized legacy tool
implementations
• Technology tool governance is established and enforced

4.2.3 DM technology tool governance is • Processes in place to onboard new tools and/or
integrated into DG decommission old ones
4.2.2 Technology tool roadmap is developed and implemented
4.2.3 DM technology tool governance is integrated into DG

C
4.1
A Technology
P Architecture
the data
B management
I initiative
4.2
L DM Tool The data management tools stack is
Stack is
I Identified
defined in governed my data
T and
Governed
I
E
4.3
in Place

Capability 4.3 – Operational Risk Planning is in Place
4.3.1 Operational risk governance structure

• Operational risk governance structure and policies are
and processes are in place and
operational
implemented
4.3.2 Data infrastructure contingency • Integrated contingency plan is defined

planning is defined and in place • Routine contingency tests are taking place
4.3.2 Data infrastructure contingency planning is defined and in place

4.0 Data & Technology Architecture
• In Summary: Data & Technology Architecture capabilities are…
4.1 Data Architecture (DA) is Integrated with Technology Architecture (TA)
4.2 DM Technology Tool Stack is Identified and Governed
4.3 Operational Risk Planning is in Place

DCAM FRAMEWORK
ASSESSMENT MODEL
CLOSE – DAY 1
www.edmcouncil.org
Copyright ©©2021
2021EDM
EDMCouncil
CouncilInc.
Inc. Page 64

B. Course Content - Day 1

Uploaded by

Copyright:

Available Formats

B. Course Content - Day 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B. Course Content - Day 1

Uploaded by

Copyright:

Available Formats

DCAM FRAMEWORK

DATA MANAGEMENT CAPABILITY

Confidential Copyright © 2021 EDM Council Inc. Page 3

CONFIDENTIAL | © 2021 EDM Council Inc. 4

The Data Management Strategy and

• Defines the goals, objectives and scope of the data

Importance of the physical documentation should not be underestimated. The

CONFIDENTIAL | © 2021 EDM Council Inc. 5

Articulates the vision

Identifies the business value

CONFIDENTIAL | © 2021 EDM Council Inc. 6

Flows like Water…

The Data Management Strategy and Business

CONFIDENTIAL | © 2021 EDM Council Inc. 7

CONFIDENTIAL | © 2021 EDM Council Inc. 8

Capability 1.1 – The DM Strategy (DMS) is Specified and Shared

• Mapped to the high-level business objectives

1.1.4 The DMS includes an established • Mechanism in place to capture feedback

1.1.5 The DMS has been evaluated and is enforceable

Capability 1.1 – The DM Strategy (DMS) is Specified and Shared

Program & Funding Data

CONFIDENTIAL | © 2021 EDM Council Inc. 10

Capability 1.1 – The DM Strategy (DMS) is Specified and Shared

• Mapped to the high-level business objectives

1.1.4 The DMS includes an established • Mechanism in place to capture feedback

1.1.5 The DMS has been evaluated and is enforceable

CONFIDENTIAL | © 2021 EDM Council Inc. 12

Capability 1.2 – The DM Strategy Business Case is Defined

• The DM Business Case is mapped to line-of-business priorities and

• The DM Business Case has been socialized

1.2.4 Expected DM outcomes are defined and sequenced

CONFIDENTIAL | © 2021 EDM Council Inc. 14

Capability 1.3 – The Strategic Vision is Defined

• Define what data that is needed to achieve the business objectives

1.3.2 The Data Usage Strategy is identified

1.2 The Data Management Business Case is Defined

1.3 The Data Management Vision is Defined

CONFIDENTIAL | © 2021 EDM Council Inc. 16

CONFIDENTIAL | © 2021 EDM Council Inc. 18

The Data Management Program and

• The Office of Data Management (ODM) is established

DCAM and the Data Management Funding Model

I Data Management Funding is Roles and Responsibilities Plans are

CONFIDENTIAL | © 2021 EDM Council Inc. 21

• Role of the DMP is formally established, supported and

• Formal Data management processes are established

2.1.5 The DMP concepts are reflected in the DMS

I Data Management Funding is Roles and Responsibilities Plans are

CONFIDENTIAL | © 2021 EDM Council Inc. 23

Capability 2.2 – The Funding Model is Established

• DM funding is aligned with organizational cycles

2.2.3 Implementation of the DM funding • Funding is allocated by the operating units

2.2.3 Implementation of the DM funding model is enforced

I Data Management Funding is Roles and Responsibilities Plans are

CONFIDENTIAL | © 2021 EDM Council Inc. 25

Capability 2.3 – The Organizational Structure is Created

• The function of data management is formally created

• There is an officially appointed owner of the data management program

2.3.2 The ODM has an executive owner

I Data Management Funding is Roles and Responsibilities Plans are