1 Hour Online Training

Data Management
Body of Knowledge
Mulyana
mulyana@brainmatics.com
http://brainmatics.com
08118228992

1
Mulyana
• SMK Negeri 1 Rangkasbitung
• S1 STMIK Eresha, Jakarta
• Chief Training Officer
PT Brainmatics Cipta Informatika
• Data Analyst dan Data Architect
PT IlmuKomputerCom Braindevs Sistema
• Industrial IT Certifications: TOGAF 9 Foundation, Applications &
Use Cases Professional Certification
• Data Architecture and Analysis Consultant: KPK, RistekDikti, INSW,
LIPI, Kemenkeu (DJPK, Itjend, Bea Cukai, DJPB), Kemsos, BPK,
Pertamina EP, PT PJBI, etc.

2
Course Outline
1.1 Introduction
1.2 Data and Information
1. Data Management 1.3 Data Management Frameworks
1.4 DAMA and the DMBOK

2.1 Introduction
2. Data Handling Ethics 2.2 Essential Concepts
2.3 Establishing an Ethical Data Culture

3
1. Data Management
1.1 Introduction
1.2 Data and Information
1.3 Data Management Frameworks
1.4 DAMA and the DMBOK

4
1.1 Introduction

5
 Perusahaan Bergantung pada Sumber Daya

Penarikan Penyimpanan

Perencanaan Utilisasi

Sumber Daya
Perusahaan

Mengelola Sumber Daya agar Efektif

6
Perusahaan Bergantung pada Sumber Daya
Keuangan

Orang

Mengelola Sumber
Daya

Inventori

Waktu
7
Tidak Tepat Waktu
Kualitas Buruk

Sulit Diakses Tidak Lengkap

8
Perubahan Kultur dan Perilaku

9
Introduction
• Data Management is the development, execution, and
supervision of plans, policies, programs, and practices that
deliver, control, protect, and enhance the value of data and
information assets throughout their lifecycles
• A Data Management Professional is any person who works in
any facet of data management to meet strategic
organizational goals
• Data management professionals fill numerous roles, from
the highly technical (e.g., database administrators, network
administrators, programmers) to strategic business (e.g.,
Data Stewards, Data Strategists, Chief Data Officers)

11
12
Business Drivers
• High quality data about their customers, products,
services, and operations can make better decisions
• Failure to manage data is similar to failure to
manage capital
• To enable organizations to get value from their data
assets, just as effective management of financial
and physical assets enables organizations to get
value from those assets

13
Goals
• Understanding and supporting the information needs of
the enterprise and its stakeholders, including
customers, employees, and business partners
• Capturing, storing, protecting, and ensuring the
integrity of data assets
• Ensuring the quality of data and information
• Ensuring the privacy and confidentiality of stakeholder
data
• Preventing unauthorized or inappropriate access,
manipulation, or use of data and information
• Ensuring data can be used effectively to add value to
the enterprise

14
1.2 Data and Information

15
16
Data
• Data is also understood as information that has been stored
in digital form
• The New Oxford American Dictionary defines data as “facts
and statistics collected together for analysis.”
• Data is means of representation. Data stands for things other
than itself (Chisholm, 2010)
• Data is both an interpretation of the objects it represents
and an object that must be interpreted (Sebastian-Coleman,
2013)

17
Data and Information
• Data has been called the “raw material of
information” and information has been called “data
in context”.
• Layered pyramid is used to describe the relationship
between data (at the base), information,
knowledge, and wisdom (at the very top).
• While the pyramid can be helpful in describing why
data needs to be well-managed, this representation
presents several challenges for data management

18
19
Data as an Organizational Asset
• An asset is an economic resource, that can be
owned or controlled, and that holds or produces
value
• In the early 1990s, some organizations found it
questionable whether the value of goodwill should
be given a monetary value
• Now, the ‘value of goodwill’ commonly shows up as
an item on the Profit and Loss Statement (P&L)
• Businesses use data to understand customers,
create new products and services, and improve
operational efficiency by cutting costs and
controlling risks

20
Data as an Organizational Asset
• Government agencies, educational institutions, and
not-for-profit organizations also need high quality
data to guide their operational, tactical, and
strategic activities
• Many organizations identify themselves as ‘data-
driven’, face of business today means that change is
no longer optional; digital disruption is the norm

21
 Data Management Principles
• Data is an Asset with Unique Properties
Data is Valuable • The Value of Data Can and Should be Expressed in
Economic Terms

• Managing Data Means Managing the Quality Data

Data Management • It Takes Metadata to Manage Data
Requirements are Business • It Takes Planning to Manage Data
Requirement • Data Management Requirement Must Drive
Information Technology Decisions

• Data Management is Cross-Functional

Data Management • Data Management Requires and Enterprise Perspective
Depends on Diverse Skill • Data Management Must Account for a Range of
Perspective

• Different Types of Data Have Different Lifecylce

Data Management is Life Characteristic
Cycle Management • Managing Data Includes Managing the Risks Associated
with Data 22
1.2.1 Data Management
Challenges

23
Data Differs from Other Assets
• Can not be pointed to, touched, and moved around, placed
at a time
• Not tangible
• Easy to copy and transport, but it is not easy to reproduce if
it is lost or destroyed.
• Dynamic and can be used for multiple purposes
• The same data can even be used by multiple people at the
same time
• An organization’s data is unique to itself
• Most operational business transactions involve the exchange
of information
• Most information is exchanged electronically, creating a data
trail

24
Data Valuation
• Value is the difference between the cost of a thing
and the benefit derived from that thing
• Data calculations are more complicated, because
neither the costs nor the benefits of data are
standardized
• Approach to data valuation needs to begin by
articulating general cost and benefit categories that
can be applied consistently within an organization.
• Value of data is contextual (what is of value to one
organization may not be of value to another) and
often temporal (what was valuable yesterday may
not be valuable today)

25
Data Valuation-General Cost and Benefit
Categories
• Cost of obtaining and storing data
• Cost of replacing data if it were lost
• Impact to the organization if data were missing
• Cost of risk mitigation and potential cost of risks associated
with data
• Cost of improving data
• Benefits of higher quality data
• What competitors would pay for data
• What the data could be sold for
• Expected revenue from innovative uses of data

26
Data Quality
• Poor quality data will have a negative impact on decisions
• Poor quality data is simply costly to any organization.
Estimates differ, but experts think organizations spend
between 10-30% of revenue handling data quality issues.
• IBM estimated the cost of poor quality data in the US in
2016 was $3.1 Trillion.

27
 Data Quality
Costs Source Benefits of High Quality
Scrap and rework Improved customer experience
Work-arounds and hidden correction
Higher productivity
processes
Organizational inefficiencies or low
Reduced risk
productivity
Organizational conflict Ability to act on opportunities
Low job satisfaction Increased revenue
Competitive advantage gained from
Customer dissatisfaction insights on customers, products,
processes, and opportunities
Opportunity costs, including inability to
innovate
Compliance costs or fines
Reputational costs 28
Metadata and Data Management
• Metadata includes not only the business, technical,
and operational, but also the Metadata embedded
in Data Architecture, data models, data security
requirements, data integration standards, and data
operational processes
• Metadata describes what data an organization has,
what it represents, how it is classified, where it
came from, how it moves within the organization,
how it evolves through use, who can and cannot
use it, and whether it is of high quality
• The challenge is that Metadata is a form of data and
needs to be managed as such
29
Data Management is Cross-functional
• Data management requires design skills to plan for
systems, highly technical skills to administer
hardware and build software, data analysis skills to
understand issues and problems, analytic skills to
interpret data, language skills to bring consensus to
definitions and models, as well as strategic thinking
to see opportunities to serve customers and meet
goals
• The challenge is getting people with this range of
skills and perspectives to recognize how the pieces
fit together so that they collaborate well as they
work toward common goals

30
Establishing an Enterprise Perspective
• Managing data requires understanding the scope
and range of data within an organization
• Data is not only unique to an organization, it is
unique to a department or other sub-par of an
organization
• Different departments may have different ways of
representing the same concept (e.g., customer,
product, vendor)
• Enterprise Architecture is the way to have
enterprise perspective to the organization

31
The Data Lifecycle
• The data lifecycle is based on the product lifecycle
• Understanding the data lineage requires documenting
the origin of data sets, as well as their movement and
transformation through systems where they are
accessed and used
• The better an organization understands the lifecycle and
lineage of its data, the better able it will be to manage
its data
• Creation and usage are the most critical points in the
data lifecycle
• Data Management efforts should focus on the most
critical data and minimizing data ROT (Data that is
Redundant, Obsolete, Trivial) (Aiken, 2014)

32
 Identify objectives, plan information architecture, develop
standards and definition.

Assessing data, Plan Modeling, designing

create policy and and developing
procedure application, database,
Design process
Enhance &
Achieves Enable
information, delete
data or records

Dispose

Retrieve data, Create/ Create records,

Use
use Obtain purchase data, load
information. external files
Store/
Maintain

Store data electronically in database, store as hardcopy

Share information about the resource through networks, enterprise service
bus, email Update, change, manipulate, parse, validate, transform,
consolidate
33
records
Different Types of Data
• Data can be classified by type of data (e.g., transactional
data, Reference Data, Master Data, Metadata; alternatively
category data, resource data, event data, detailed
transaction data) or by content (e.g., data domains, subject
areas) or by format or by the level of protection the data
requires
• Data can also be classified by how and where it is stored or
accessed
• Because different types of data have different requirements,
are associated with different risks, and play different roles
within an organization, many of the tools of data
management are focused on aspects of classification and
control (Bryce, 2005)

34
Data and Risk
• The increased role of information as an organizational asset
across all sectors has led to an increased focus by regulators
and legislators on the potential uses and abuses of
information
• Sarbanes-Oxley (focusing on controls over accuracy and
validity of financial transaction data from transaction to
balance sheet)
• Solvency II (focusing on data lineage and quality of data
underpinning risk models and capital adequacy in the
insurance sector),
• Data privacy regulations
• The regulatory environment increasingly expects to see it on
the risk register, with appropriate mitigations and controls
being applied
35
1.2.2 Data Management Strategy

36
Data Management Strategy
• A strategy is a set of choices and decisions that together
chart a high-level course of action to achieve high-level
goals.
• A strategic plan is a high-level course of action to achieve
high-level goals
• A data strategy should include business plans to use
information to competitive advantage and support
enterprise goals
• Data strategy must come from an understanding of the data
needs inherent in the business strategy: what data the
organization needs, how it will get the data, how it will
manage it and ensure its reliability over time, and how it will
utilize it

37
Data Management Strategy
• Data strategy requires a supporting Data Management
program strategy – a plan for maintaining and improving the
quality of data, data integrity, access, and security while
mitigating known and implied risks
• Data management strategy is owned and maintained by the
CDO and enacted through a data governance team,
supported by a Data Governance Council
• CDO will draft an initial data strategy and data management
strategy even before a Data Governance Council is formed,
in order to gain senior management’s commitment to
establishing data stewardship and governance

38
 Data Management Strategy
Components Deliverable
Compelling vision for data management

A summary business case for data management,

with selected examples
Guiding principles, values, and management
Data Management Charter
perspectives
The mission and long-term directional goals of data
management

Proposed measures of data management success

Short-term (12-24 months) Data Management

program objectives that are SMART (specific, Data Management Scope Statement
measurable, actionable, realistic, time-bound)

A prioritized program of work with scope

boundaries
Data Management Implementation Roadmap
A draft implementation roadmap with projects and
action items 39
Data Management Strategy

40
Data Management Strategy

41
1.3 Data Management
Frameworks

42
Data Management Frameworks
• Data management involves a set of interdependent
functions, each with its own goals, activities, and
responsibilities
• Frameworks developed at different levels of
abstraction provide a range of perspectives on how
to approach data management
• These perspectives provide insight that can be used
to clarify strategy, develop roadmaps, organize
teams, and align functions

43
Data Management Frameworks: Lenses
1. The Strategic Alignment Model and the
Amsterdam Information Model
Show high-level relationships that influence how an
organization manages data
2. The DAMA DMBOK Framework (The DAMA Wheel,
Hexagon, and Context Diagram)
Describes Data Management Knowledge Areas, as defined
by DAMA, and explains how their visual representation
within the DMBOK
3. DAMA Wheel
Starting point and rearrange the pieces in order to better
understand and describe the relationships between them

44
Strategic Alignment Model

45
The Amsterdam Information Model

46
The DAMA-DMBOK Framework
• DAMA Wheel presents the set of
Knowledge Areas at a high level

• The Hexagon recognizes

components of the
structure of Knowledge
Areas

• The Context Diagrams present the

detail within each Knowledge Area

47
Three visuals depict DAMA’s Data Management Framework
The DAMA Wheel

48
The Environmental Factors Hexagon

49
Knowledge Area Context Diagram
Definition: High-level description of the knowledge area
Goals: Purpose of the Knowledge Area
1. Goal 1
2. Goal 2
Business Driver

Inputs: Activities: Deliverables:

• Input 1 1. Planning Activity/Activity Group (P) • Deliverable 1
• Input 2 1. Sub activity • Deliverable 2
• Input 3 2. Sub activity • Deliverable 3
2. Control Activity/Activity Group (C)
Inputs are generally 3. Develpment Activity/Activity Group Deliverable are generally
outputs from other (D) inputs to other
knowledge Areas 4. Operational Activity/Activity Group Knowledge Area
(O)

Suppliers: Participants: Consumers:

• Supplier 1 • Role 1 • Role 1
• Supplier 2 • Role 2 Technical Driver
• Role 2

Techniques: Metrics: Tools:

• Methods and procedures to • Measurable result of the • Software package types to
excute activities process support activities
(P0 Planning, (C) Control, (D)50Development, (O) Operations
DMBOK Pyramid (Aiken): Phase
• Phase 1: The organization purchases an application
that includes database capabilities.
• Phase 2: Find challenges with the quality of data,
Metadata and consistent Data Architecture.
• Phase 3: Disciplined practices for managing Data
Quality, Metadata, and architecture require Data
Governance
• Phase 4: The organization leverages the benefits of
well-managed data and advances its analytic
capabilities

51
 DMBOK Pyramid (Aiken)

Phase 4

Phase 3
Phase 1

Phase
52
2
DAMA Functional Area Dependencies

53
DAMA Data Management Framework
Evolved

54
1.4 DAMA and the DMBOK

55
DAMA Wheel Evolved

56
DAMA’s Mission
• Providing a functional framework for the
implementation of enterprise data management
practices;
• Establishing a common vocabulary for data
management concepts and serving as the basis for
best practices for data management professionals
• Serving as the fundamental reference guide for the
CDMP (Certified Data Management Professional)
and other certification exams

57
 Data Governance provides direction and oversight
for data management by establishing a system of
decision rights over data that accounts for the needs
of the enterprise
Data Modeling and Design is the process of discovering,
Data Architecture defines the blueprint for
analyzing, representing, and communicating data
managing data assets by aligning with organizational
requirements in a precise form called the data model
strategy to establish strategic data requirements and
designs to meet these requirements

Data Quality includes the planning Data Storage and Operations

and implementation of quality includes the design, implementation,
management techniques to measure, and support of stored data to maximize
assess, and improve the fitness of data its value
for use within an organization

Metadata includes planning,

implementation, and control
activities to enable access to high Data Security ensures that data
quality, integrated Metadata, privacy and confidentiality are
including definitions, models, maintained, that data is not
data flows, and other information breached, and that data is
critical to understanding data and accessed appropriately
the systems through which it is
created, maintained, and
accessed

Data Integration and

Data Warehousing and Business Interoperability includes
Intelligence includes the planning, processes related to the movement
implementation, and control processes and consolidation of data within
to manage decision support data and and between data stores,
to enable knowledge workers to get applications, and organizations
value from data via analysis and
reporting
Document and Content Management
Reference and Master Data includes includes planning, implementation, and
ongoing reconciliation and maintenance of control activities used to manage the
core critical shared data to enable lifecycle of data and information found in a
consistent use across systems of the most range of unstructured media, especially
accurate, timely, and relevant version of documents needed to support legal and
truth about essential business entities 58
regulatory compliance requirements
DAMA Addition Chapter
• Data Handling Ethics describes the central role that data ethics
plays in making informed, socially responsible decisions about
data and its uses.
• Big Data and Data Science describes the technologies and
business processes that emerge as our ability to collect and
analyze large and diverse data sets increases
• Data Management Maturity Assessment outlines an approach to
evaluating and improving an organization’s data management
capabilities
• Data Management Organization and Role Expectations provide
best practices and considerations for organizing data management
teams and enabling successful data management practices
• Data Management and Organizational Change Management
describes how to plan for and successfully move through the
cultural changes that are necessary to embed effective data
management practices within an organization

59
 Integrated Standard Compliance
Business Architecture

Framework Proses Bisnis Pemodelan Proses Bisnis Analisis Proses Bisnis Manajemen Risiko (ISO
(APQC) (BPMN) (BABOK) 31000)

Data Architecture Tata Kelola dan Technology Architecture

Arsitektur Bisnis
Taksonomi Teknologi
Tata Kelola dan
(TRM)
Arsitektur Teknologi
Manajemen Data
(DMBOK)

Architecture Governance
Tata Kelola dan and Implementation
Arsitektur Data Penentuan Architecture
Implementation dan Roadmap IT Manajemen Proyek
(PMBOK)
Analisis Data Elemen
(ISO 11179)
Monitoring dan Monitoring
Evaluasi Penerapan IT dan Evaluasi IT
Tata Kelola dan (COBIT)
Arsitektur Aplikasi

Application Architecture
Sistem Pemerintahan
Analisis dan Desain Manajemen Software Manajemen Layanan IT Penilaian Kualitas
Berbasis Elektronik
Software (UML) (SWEBOK) (ITIL) Software (ISO 25010)
(SPBE)
60
@brainmatics.id facebook.com/Brainmatics.id @brainmatics_id

PT Brainmatics Cipta Informatika

Menara Bidakara, Suite 0205 Jl. Gatot Subroto Kav. 71-73 Jakarta 12870
Phone: +62283793383, 83793384, 83793260, 83793261
https://brainmatics.com info@brainmatics.com