LADY.

Chapter 1. Data management

Data characteristics:

 Metadata originates from the processes derived from its creation, processing and use,
including architecture, modeling, administration, governance, data quality management,
systems development, IT, and business operations and analytics.
 Data management is cross-functional, requiring a lot of skills and experience.
 It requires a business perspective, which is why data management and governance are
intertwined.
 Different types of data have different lifespans.
 Being an asset, they represent risks in the organization, organizations must consider the
ethical implications of the use of data.
 Effective data management requires committed executives.
 The value of the data is contextual, since it is not of equal use to other organizations and is
sometimes temporary.
 Data quality is essential, if you store bad information you will waste your money.
 You must ensure that it meets the needs of the institution by working with data users to
define their needs, including characteristics so that the data is of the highest quality.
 Using data includes learning why it is applied to learn and create value.

The benefits of quality data are:

  Improving customer satisfaction.
 High productivity.
 Risk reduction.
 Ability to act on opportunities.
 Income increase.
 Competitive improvement related to customers, products, processes, and opportunities.

Other data characteristics

 Planning for better data requires a strategy in architecture, modeling and a collaboration
strategy between business and IT leaders.
 The life cycle of the data is related to the life cycle of the products, additionally there is a
“lineage” (The path along which it moves from one point of origin to another where it is
used, sometimes of called data string).
 Life cycle and lineage intersect and can be understood in relation to each other.
 The data must be classified by data type:
o transactional,
o Reference,
o master data,
o metadata,
o Alternative category,
o Of resource,
o Event,
o detailed transaction),
o By context (domain, assigned area),
o Due to the format or the level of protection required,
o In addition to how and where it is stored or how it is entered.

Because different types of data have different requirements, are associated with different risks,
and play different roles, many data management tools focus on classification and control aspects.

Data quality refers to:

 Availability,
 Reliability,
 Complete,
 Precision,
 Consistency,
 Chance,
 Utility,
 Understandability.

The information is frequently associated with business strategy and operational use of data.
Data is associated with IT and processes that make it accessible for use.

Around these concepts are the main domains:

1. Business strategy.
2. Information technology strategy.
3. Infrastructure, organizational and processes.
4. Information technology infrastructure and processes.

Data Management Framework

Hexagon of environmental factors

Strategic alignment model:

Information governance
Business YOU

Business strategy and Strategic information IT Strategy and

governance and governance Governance
Strategic

Organization and Information IT architecture

Aiken Pyramid

Phase 1.

The organization purchases an application with a database. It means it requires data design and
modeling, storage, security. To achieve the functioning of the system, work on integration and
interoperability is required.

Phase 2.

Once bootstrapping is achieved, you will encounter data quality challenges. Reliable metadata and
consistent data architecture are required to achieve the highest quality. This gives clarity, data is
obtained from different systems working together.

Phase 3.

Disciplines to manage quality, metadata and architecture required for data governance that
provide the structure for data management activities. Additionally, data governance enables the
execution of strategic initiatives such as documentation and context management, reference data
management, master data, data warehousing and business intelligence.

Phase 4.
The benefits of taking advantage of good data management in the organization and advancing its
analytical capabilities.
Episode 2. Data handling ethics

Describes the primary role that data ethics plays in generating reporting, socially responsible
decisions about data use. Awareness of ethics in obtaining, analyzing and using data that a
professional must observe.
Chapter 3. Data Governance

Provides direction and oversight by establishing a system of good data decisions that considers the
needs of the company.

Data governance is defined as an exercise of authority and control (Plan, monitor, enforce) over
data management.

The scope and focus should include:

 Strategy. Definition, communication and direct execution.

 Policy. Adjustment and reinforcement of policies related to metadata, access, use, security
and quality.
 Standards and quality. Adjustment and reinforcement of quality and architectural
standards.
 Surveillance. Practical observation, audit and correction in key areas, policy, and data
management.
 Compliance. Regulatory.
 Problem management. Identification, definition, escalation and resolution of problems
related to security, access, quality, regulatory compliance, ownership, policies, standards,
or procedures.
 Data management projects. Leadership effort to implement data practices.
  Valuation in data assets. Set of standards and processes consistent in defining the data
asset.

To achieve the objective, the data governance program must develop policies and procedures,
generate management practices at different levels of the organization, complementing the
organization's change process. Requires a change management process.

Goals and principles.

It provides principles, policies, processes, framework, metrics, and administration of data

management as an active guide for activities at all levels, to achieve the objectives it must be:

 Sustainable. It is a continuous process, it requires business leadership, sponsorship and

ownership of the process.
  Embedded. It should be incorporated into software development, use of data for analytics,
master data management, and risk management.
 Measured. It gives a positive financial impact, but to demonstrate it requires
understanding from the beginning and planning to improve your performance.

Data management activities should focus on:

 Creation and management of metadata. Definition and management of business

terminology, validating values. He is responsible for the data glossary.
 Document rules and standards.
 Management of data quality issues.
 Execution of governance activities.

Activities:

1. Defines data governance for the organization.

2. Conduct a readiness assessment:
 Maturity in data management.
 Capacity for change of the organization.
 Collaborative preparation. Organization's ability to collaborate.
 Business alignment.
3. Business discovery and alignment.
4. Generate points of contact.
5. Data governance strategy. Initiation letter, operational framework, implementation map
and plan for successful operation.
6. Defines the operational framework of digital government.

7. Develop goals, principles and policies.

8. Generate data management projects.
9. Participate in change management.
10. Participate in problem management.
 11. Participates in compliance with regulatory requirements.
12. Implement data governance.
13. Data standards and procedures.
14. Develop the business glossary.
15. Coordinate with architecture groups
16. Valuation of data assets.
17. Get into data governance.

Tools and techniques

1. Online presence and websites.

2. Glossary of business techniques.
3. Flows.
4. Documentation tools.
5. Data governance scorecar.

Chapter 4. Data Architecture Management

Define the project for active data management by aligning the organization's strategy to the
required strategic data and design to meet those requirements.

Data architecture is considered from the following perspectives:

 Results.
 Activities.
 Behavior.

In an organization it is described by the integration of a set of master design documents, including

governance standards for how data was obtained, storage, arrangements, uses and movements.

1. Business drivers.

The goal of data architecture is to be the bridge between business strategy and technology
execution. As part of enterprise architecture, data architecture is:
  The strategy prepares the organization for rapid evolution of products, services, and
provides an advantage of business opportunities inherent in emerging technologies.
 Translate business needs into data and system requirements, processes have data they
require.
 Facilitates alignment between business and IT.
 Acts as an agent of change, transformation and agility.

2. Results of practical architectures.

Data architecture results include:

 Data storage and processing requirements.

 Design of structures and plans to meet the short and long-term data requirements of the
company:

3. Essential concepts.
 Enterprise architecture domains.

4. Enterprise data architecture

Contains:

 Business data model. It includes key enterprise data entities, their relationships, critical
business rules, and critical attributes. Every data model must be based on the EDM.
 Data flow design. Definition of requirements and the master map for storage and processing
through the database, applications, platform and network. Manages data on business
processes, location, roles, and technical components.

Enterprise Data Model (EDM)

It requires a good investment even when acquired, it requires definition and documentation of
organizational vocabulary, business rules and business knowledge.
Data flow design
 Activities

1. Establish the data architecture practice.

 Evaluates existing data architecture specifications.
 Develop a map.

 Management of business requirements in projects.

Enterprise data architecture projects include the following activities:

 o Definition of scope.
o Understanding of business requirements.
o Detailed design specifications, including business rules in the data in the life cycle
perspective.
o Implementation, when it is purchased, when data is reused, when it is built.
The construction process of architectural activities in projects also differs according to the method:
 Waterfall. Understanding of requirements and construction of the system in sequential
phases as a general part of business design.
 Incremental. Learn and build in gradual steps.
 Agile and iterative. Learn, build and test on deliverable packages.

Integration with enterprise architecture

The work of developing enterprise data architecture specifications for the subject area in greater
detail.

Tools

 Data modeling tools.

 Management software.
 Graphic design applications

Techniques

 Life cycle projection.

 Diagram clarity.
 Linear symmetry.

Implementation guide

 Risk assessment.
 Lack of administrative support.
 No proven records.
 Apprehensive responsible.
 Culture shock.
 Inexperience of the project leader.

Data architecture governance

 Supervised projects.
 Architectural design administration.
 Definition of standards.
 Creation of data artifacts.

Chapter 5. Data design and modeling.

It is the process of discovery, analysis, presentation and communication of data requirements
called data modeling.

Business drivers

 Provide a common vocabulary about data.

 They capture and document explicit knowledge about organizational data and systems.
 Serve as a priority communication tool.
 Provide the starting point for customization, integration, even change in the application.

Goals and principles

The goal of data modeling is to confirm and document an understanding of different perspectives
that drive applications in closer alignment with current and future business requirements, creating
the foundation to successfully broadly complement master data management initiatives. and data
governance programs.

Essential concepts

Explains the different types of data that can be modeled, the data model components, the types of
data models that can be developed, and the reason for choosing different types of situations.

 Data modeling and data model.

It describes an understanding of the organization or what the organization wants to be. It is the
way to document the data requirements and the results of the process model data definitions. The
data model is the main instrument for communicating business data requirements to IT and with
IT generating the analysis, modeling, architecture to designers and developers.

 Types of data to be modeled.

Four types of data can be modeled:

o Information category. The use of data to classify and assign types of things. Ex. Products
classified by color, model, size.
o Resource information. Basic profile of resources required to conduct operational
processes such as products, clients, suppliers.
o Business event information. Creation of data while operation processes are in processes.
o Detail of transactional information. It is frequently generated by the point of sale system,
by the social networks system, interaction with the Internet, usually referred to as big
data.

 Data model components:

o Entity. Outside of data modeling, the definition of “entity” is a thing that exists separately
from other things. In data modeling, “entity” is something about which an organization
collects information. Entities are referred to as the substance of an organization.
Alias entities.

Basic entity representation:

Definitions of “entities”:
It is an essential contribution to business value in any data model.
Helps IT professionals to generate business intelligence and design decision applications. Should
have:
 o Clarity.
o Accuracy.
o Completeness, integrity.
 Relationship

It is the relationship between entities.

 Alias relationship

It can vary basically in the scheme or level of detail.

 Graphic representation of relationship

Cardinal relationship

In the relationship between two entities, cardinal captures how many times one entity participates
in the relationship with how many of the other entities.

 Arity of relationships

The most common are unary, binary, and trinary relationships.

  Foreign key

 Attribute

It is a property that identifies, describes or measures an entity.

o Construction keys

A simple key is an attribute that identifies a unique entity.

A surrogate key is a unique identifier for a table, serves technical functions and should not be
visible to end users.

A business key is one or more attributes that business professionals will use as a single entity.

 Domain
In data modeling, a domain is a complete set of possible values that an attribute can be assigned.
It can be articulated in different ways. A domain provides the standardization meaning of attribute
characteristics.

You can restrict a domain with different rules, called restrictions. Rules can relate to formats, logic,
or both.

Domains can be defined in different ways:

Data type, Data format, List, Range, Rule-base.

 Data modeling scheme.

 Relational
Relational theory provides a systematic way to organize data that reflects its meaning. This
approach has the additional effect of reducing redundancy in data storage.

 Dimensional

In dimensional models, data is structured to optimize the query and analysis of a large amount of
data.

 Fact tables

In a dimensional scheme, the rows of the fact table of a particular measure and are numerical,
such as amounts, quantities. Some measurements are the result of algorithms in which case
Metadata is critical to providing understanding and use.

 Dimension table

They represent the important objects of the business and contain mainly textual descriptions.

 Snowflake

It is the term used to normalize the plane, simple table, dimensional structure in a starting scheme
in the representation of hierarchical components or in network structures.

 Grain

The term grain shelf from the meaning or description of a column in the de facto table.
  Dimensional shaping

It is built by the entire organization rather than a single particular project.

 Goal orientation.

The Unified Modeling Language (UML) is a graphical language for modeling software.

 Factual Base Modeling (FBM)

This language is based on the analysis of natural verbalization that can occur in the business
domain.

 Object Role Modeling (ORM)

 Activities

1. Data modeling plan

The deliverables of the data modeling process:

 diagrams,
 Definitions.
 Exceptional problems and questions.
 Lineage.
Build the data model:

1. Advanced engineering

The process of building new applications starting with the requirements.

 Conceptual data model. (CDM)

o Select the scheme.
o Select the notation.
o Complete the initial CDM.
 Collect high-level concepts, time, geography, customers, products.
 Collect the activities (Verbs) that connect with the concepts.
o Incorporates company terminology.
o Obtain the closing signature.
2. Logical data modeling.
 Analyze information requirements.
 Analyze existing documentation.
 Add associated entities.
 Add attributes.
 Assign domains.
 Assign keys.
 Physical data modeling.
 Solve logical abstractions.
 Add attribute details.
 Add data object references.
 Assignment of substitute keys.
 Denormalization for performance.
 Performance by index.
 Partition for performance.
 Create views.
reverse engineering
It is the documentation process when a database exists.

3. Review of the data model.

4. Maintenance of the data model.

Tools

1. Data modeling tools.

2. Lineage tools.
3. Data profile tools.
4. Metadata repository.
5. Data model patterns.
6. Industrial data model.

Better practices

1. At conventions.
2. In data design.

Data governance model

1. Data model and quality management design.

2. Data model metrics.

Chapter 6. Data storage and operation.

It includes the design, implementation and support of data storage to maximize its value.
Operations provides support throughout the data lifecycle by planning data disposition.

Two subdivisions:

Data Support and technological data support.

 Business drivers

Companies rely on their information systems to run their operations. Business continuity is the
first driver.

Goals and principles

 Manage data availability throughout the life cycle.

 Ensure data integrity.
 Manage the performance of transient data.

It is required to follow the following principles.

 Identify and act on automation opportunities.

 Build with re-use in mind.
 Understands and appropriates the application of best practices.
 Connect database standards to support requirements.
 Set of expectations for the DBA role in project work.

Essential concepts

1. Database terms.
2. Data cycle management.
3. Database administrator.
 DBA producer.
  DBA application.
 DBA procedures and development.
 NSA.
4. Types of data architecture:

DBAs, in coordination with network and systems administrators, need to establish a systematic
comprehensive project to include standardizations, consolidation, virtualization and automation of
data backup and recovery functions, as well as security of those functions.
 5. Types of database processing
 ACID.
o Atomicity. The operations are carried out so that if one of the parts of the
transaction fails, the entire transaction fails.
o Consistency. The transaction must follow all the rules defined by the system and
every time.
o Isolation. Each transaction is independent on its own.
o Durability. Once completed, the transaction cannot be undone.
 BASE
o Available in basic form. The system guarantees some levels of data availability
even when nodes fail.
o Soft state. Data is in constant flow, while a response is given, the data is not
guaranteed to be available.
o Eventually consistent. Data will eventually be consistent across all nodes, but not
all transactions will be consistent at all times.

The BASE system is common for big data:

 CHAP
o Consistency. The system must operate as designed at all times.
o Availability. It must be available when required and must respond to each requirement.
o Distributed tolerance. The system must be available to continue operations even in the
event of failures.
 6. Data storage media

The most common are disks and network area storage (SAN).

7. Database environment. Productive, pre-productive,

8. Database organization

9. Database specialization.
10. Common database process.
 Activities

1. Administration of database technologies.

It must follow the same principles and administration standards of any methodology.

 Understanding the characteristics of database technology.

Data professionals must first identify companies' characteristics before determining what
recommendation to make.

Most companies have database tools installed to perform ranges or functions, for data
management. Only a few of those tools have mandatory standards.

2. Database Technology Assessment

Select the strategic software DBMS (Database Management System. is a set of programs that
allow the storage, modification and extraction of information in a database , in addition to
providing tools to add, delete, modify and analyze the data. Users can access information
using specific query and reporting tools, or through applications for this purpose ) is very
important. DBMS has its greatest impact on integration, application performance and business
productivity. Some factors to consider:

o Architecture and complexity of the product.

o Volume and speed limit.
o Application profile such as transaction processing, business intelligence and personal
profile.
o Specific functionalities such as temporal calculation support.
o Scalability.

Database administration

 Understand requirement.
o Define storage requirements.
o Identify usage patterns.
o Defines access requirements.
o Business continuity planning.
o Generate backups.
o Data recovery.
o Manage access controls.
o Create data containers.
o Implement physical data models.
 o Load data.

Tools

o Data modeling tool.

o Data monitoring tool.
o Data management tool.
o Development support tool.
Techniques
o Test in a reduced environment.
o Named physical standards.
o Using scripts for changes.

Implementation guide

o Preparatory assessment / Risk assessment.

o Organizational and cultural change.

Metrics

 Database account by type.

 Transaction statistics added.
 Metric capacity as:
o Amount of storage used.
o Number of warehouse containers.

Information movement
Compliance with licensing agreements and regulatory requirements.

Chapter 7. Data security management

Ensures data privacy, confidentiality is maintained, data is not breached and access to data is
appropriate.
 Business drivers

Risk reduction and business growth are the main ones.

 1. Risk reduction:

Information security begins with the classification of the organization's data to identify which data
requires protection. The following steps are considered:

o Identify and classify sensitive data.

o Locate sensitive data in the organization.
o Determine each asset how it needs to be protected.
o Identify how information interacts with business processes.

Business infrastructure with a reliable information system has become a differentiator.

2. Business growth.

The growth of e-Commerce has changed the way we offer products and services. Reliable e-
Commerce leads to profits and growth.

Secure and robust information management enables transactions and security with the client.

3. Security is an asset.

One approach to managing data sensitivity is metadata. Developing a master repository of data
characteristics means that the entire company can know precisely what level of protection
sensitive information requires.

Goals and principles

1. Goals
o Enable appropriate access and prevent inappropriate access to company data.
o Enable compliance with regulations and privacy, protection and confidentiality policies.
o Ensure that user requirements for privacy and reliability are met.
2. Beginning
o Collaboration.
o Business focus.
o Proactive administration.
o Clear responsibilities.
o Metadata boost.
o Risk reduction by reducing exposure.

Essential concepts

o Vulnerability. It is the weakness or defect in a system.

o Threat. Potential offensive action that can occur against an organization.
o Risk. It can be calculated by any of the following factors:
o Probability of a threat occurring and its frequency.
 o Type and amount of damages and the cause thereof, including damage to reputation.
o The costs of fixing the damage and preventing.

Can be prioritized:

1. Risk classification
o Critical risk (CRD).
o High risk (HRD).
o Moderate risk (MRD).
2. Organizational data security

Data stewards must be active with technology developers and cybersecurity professionals.

3. Security processes
o The 4 “As”. Access, auditable, authentication, authorization and entitlement.
o Monitoring.
4. Data integrity
5. Encryption. Hash, private key, public key.
6. Masking.
7. Network security terms. Backdoor, zombie, cookie, firewall, perimeter, DMZ, super-user
account, logger, penetration test, private network, types of data security, security device,
security credentials, identity management system
8. Types of data security restrictions.
9. Security risk system.
10. Social threats to security. Identity fraud.
11. Malware.

Activities

1. Identification of data security requirements.

2. Definition of data security policy.
3. Definition of data security standards.
4. Definition of security roles.
5. Implementation of controls and procedures.

Tools

1. Antivirus software.
2. HTTPS.
3. Identity management technology.
4. Intrusion detection and prevention software.
5. Firewalls.
6. Metadata tracking.
 7. Encryption.

Techniques

1. Use of CRUD matrix. (Creation, reading, updating and updating).

2. Immediate security patch deployment.
3. Data security attributes in matadata.
4. Metrics.
5. Security needs in project requirements.
6. Efficient search for encrypted data.
7. Document cleaning.

Implementation guide

1. Evaluation Preparation.
2. Organization and culture of change.
3. Visibility in data use rights.
4. Data security in an outsourced world.
5. Data security in a cloud world.

Data security governance

Data security and enterprise architecture.

Chapter 8. Reference and Master Data Management

It includes processes related to the movement and consolidation of data and between
warehouses, applications and the organization.

Business drivers

The trend of organizations purchasing applications rather than developing them expands the need
for data integration and interporality.
Data centers such as warehouses and master data help solve by consolidating data needs for
applications and providing applications with consistent views of data.

Goals and principles

Have data available, lower data warehouse costs, lower costs and complexity in managing
solutions, make sense of events/opportunities automatically, support business intelligence,
analytics, master data management, and operational efficiency efforts.

Essential concepts

1. Extract, transform and Load.

Business services BUS

Data as a service (DaaS)

Software as a Service (SaaS) is a licensed deliverable and model.

Data exchange standards

Formal rules for structuring data elements. (ISO)

 Data integration activities

1. Plan and analysis.

o Defines data integration and lifecycle requirements.
o Data discovery performance.
o Data lineage document.
o Data profile.
o Collective business rules.
o Design of integrated data solutions.
o Implementation and monitoring.

Tools

1. Data transformation engine. ETM

2. Data virtualization server.
3. BUS of business services.
4. Business rules engine.
5. Data and process modeling tools.
6. Data profiling tools.
7. Metadata repository.

Implementation guide

1. Risk evaluation.
2. Organizational and cultural change.

DLL governance

1. Data Sharing Agreements.

2. DLL and data lineage.
3. Data integration metrics.

Chapter 9. Document and content management.

It includes the planning, implementation, and control of activities used to manage the life cycle of
data and information found in an unstructured range of data, especially documents necessary for
legal support and regulatory compliance.
 Business drivers

Regulatory compliance, respond to litigation and business continuity requirements.

Goals and principles

Implementation with good practices of documents and content management.

Essential concepts

1. Content.
o Content management.
o Metadata content.
o Modeling content.
o Content of delivery methods.
o Vocabulary control.
2. Content and recordings
 3. Information architecture

It is the process of creating the structure by the body of information and context.

4. Search Engine
 Activities

1. Plan for life cycle management.

2. Life cycle management.
3. Advertising and content.

Tools

1. Content management systems.

2. Collaboration tools.
3. Metadata and vocabulary control tools.
4. Image Standards.
5. e-Discovery technology.

Implementation guides

1. Risk evaluation.
2. Organizational and cultural change.

Governance

1. Information reference framework

2. Information proliferation.
3. Governance for quality content.
4. Metrics.
Chapter 10. Reference and master data

Includes in-process reconciliations and maintenance of critical shared data information available
through the use of systems to provide the most accurate, timely and relevant version of the truth
about business entities.

Business drivers

Find organizational data requirements, manage data quality, data integration cost management,
risk reduction.

Goals and principles

o Ensure that the organization has consistently, current, and authoritatively completed the
master and organizational process through reference data.
o Enable master and reference data to be shared across business functions and applications.
o Reduce the cost and reduce the complexity of data use and integration through standards,
common data models and integration patterns.

Essential concepts
 1. Differences between master data and reference data.
 Master data management (MDM). It involves control over master data values and
identifiers for consistent use of enablers throughout the system, the most cumulative and
timely data on essential business entities.

The goals of MDM include ensuring accurate and timely availability of data while reducing
the risks associated with ambiguous identifiers (those identifiers with more than one
entity and those references to more than one entity).

 Reference data management (RDM). It involves control over the values of defined
domains and their definitions. The goals of RDM is to ensure that organizations have
access to the full set of current and cumulative values of each represented concept.

2. Reference Data

It is any data used to characterize or classify other data or release information to an external
party. The most basic reference data are codes and descriptions, but some reference data can be
more complex, incorporating mapping and hierarchies.

They involve control and maintenance of values of defined domains and relationships through
dominant values. The goal of baseline value management is to ensure that values are consistent
and current across different functions and that data is accessible to the organization.

3. Master data

It is data about a business entity (Employees, customers, products, financial structures, assets)
that provides transaction context and analysis.

Assessing MDM in an organization includes identifying:

  Which roles, organization, places and things are repeatedly referenced.
 What data is used to describe people, organizations, places and things.
 How data is defined and structured.
 Where the data was created, stored, available and accessed.
 How data changes and moves in the system.
 Who uses the data and for what purpose.
 What criteria is used to understand the quality and reliability of the data.

Planning for master data management includes many steps, mastering:

 Identify candidate sources that can provide a comprehensible view of the master data
entities.
 Development of exact and precise rules and data fusion.
 Establish a focus on reliable distribution of data to systems across the enterprise.

4. Shared data architecture

 Activities

1. MDM Activities
 Defines MDM enablers and requirements.

Each organization has different MDM enablers and obstacles, derived from the number and type
of systems, age, support of business processes, and how data is used for transactions and analysis.
Enablers often include opportunities to improve customer service and operational efficiency, as
well as reduce risk related to privacy and compliance. Obstacles include differences in data
meaning and structure between systems.

It is relatively easy to define requirements for master data in an application. It is more difficult to
define standard requirements through the application.

 Evaluate data sources.

 Defines the approach to architecture.
 Defines administration and maintenance process.
 Establishes government policies to enforce master data.
2. Reference to Data Activities
 Define facilitators and requirements.
  Enter data sources.
 Defines the approach to architecture.
 Referenced data set model.
 Defines administration and maintenance process.
 Establishes government policies to enforce master data.

Tools and techniques

MDM requires special designed tools to enable entity management. MDM can be implemented
through data integration tools, data remediation tools, operational data warehouses (ODS).
Shared data HUB or specialized MDM applications.

Implementation guide

They cannot be implanted overnight. Solutions require business specialists and technical
knowledge. Organizations should expect to implement master and reference data solutions
incrementally across a series of projects according to a project map.

 Adhere to the master data architecture.

 Monitor data movement.
 Manage changes to reference data.
 Data sharing agreements.

Master data governance

The governance process will determine:

 The sources to be integrated.

 Data quality rules to be enforced.
 Conditions of use rules to be followed.
 The activities to be monitored and the frequency.
 The priority and levels of responsibility for the data management effort.
 How information will be represented to meet the needs of users.

Chapter 11. Data Storage and Business Intelligent

It includes the planning, instrumentation and control of processes to support decisions and
establish knowledge for workers to obtain the value of the data through analysis and reporting.
 Business facilitators

The main thing is to support operational functions, compliance with requirements and business
intelligence activities.

Goals and principles

Organizations implement warehouses to:

 Support business intelligence activities.

 Enable effective business analysis and decision making.
 Find paths to innovate based on insights from your data.

The following implementation principles should be followed:

 Focus on business goals.

 Start with the end in mind.
 Think and design globally.
 Essential concepts

1. Business Intelligence.

Has two meanings. The first is to direct data analysis to understand the activities and opportunities
of the organization. The results of the analysis are used to improve the success of the organization.
When people say that data holds the key to competitive advancement, they mean the inherent
promise of business intelligence activities: This is if the organization asks the right questions of its
own data. This can fall internally into products, services and customers, which enable you to make
better decisions such as meeting your specific objectives.

Second. Business intelligence refers to a set of techniques that support this type of data analysis.
An evolution of tools supporting decisions. BI tools enable questioning, data mining, statistical
analysis, reporting, scenario modeling, data visualization, and data dashboards. They are used for
all of the advanced analytics budget.

2. Data warehouse

It is the combination of two components: a comprehensive decision supported by a database and

the software programs used to collect, clean, transform and store data from a variety of
operations and external sources. To support analytics and BI requirements, the data warehouse
may also include dependent data flags, which may be a subset of data copies of the warehouse. A
data warehouse includes any stored data or extracts used to support artificial intelligence-related
data deliverables.

3. Data storage

It is the operation of extracting, cleaning, transforming, controlling and loading processes that
maintain data in a data warehouse.

4. Approaches to data storage

 Stores store data from other systems.
 The act of storing includes organizing data in order to increase its value.
 Warehouses make data accessible and enable it for analysis.
 Organizations make warehouses because they make them trustworthy, integrating data
available to authorized users.
 They serve many purposes from supporting the operations management flow to predictive
analytics.

5. Corporate information factory (Inmon)

Differences between warehouses and operation systems:

 Subject-oriented, integration, time variable, non-volatile, aggregates and details data,

history.
6. Dimensional DW (Kimball)

7. DW architecture components
 Activities

1. Understanding of requirements.
2. Define and maintain the DW/BI architecture.
3. Development of data warehouse and marked data.
4. Data warehouse population.
5. Implementation of the business intelligence portfolio.
6. Product data maintenance.
 Tools

1. Metadata repository.
2. Data integration tools.
3. Types of business intelligence tools.

Techniques

1. Prototypes for requirements management.

Rapid prioritization of requirements prior to implementation activities by creating a set of data

demonstrations and applying discovery steps in the effort to achieve a prototype.

2. BI self-service

Visualization and statistical analysis tools allow you to quickly explore and discover data.

3. Audit of data that may be questionable.

Implementation guide

1. Risk assessment.
2. Map release.
3. Configuration management.
4. Organization and cultural change.

Governance
 1. Business acceptance.
2. User satisfaction.
3. Service level agreements.
4. Reporting strategy.
5. Metrics.

Chapter 12. Metadata management

It includes the planning, instrumentation and control of activities to establish access to high quality
data by integrating metadata, including definitions, models and flows and other information
critical to understanding data and the system created, kept accessible.

Data on data, classified as broad in scope. It includes technical and business process information,
data rules and constraints, and physical and logical data structures. It describes the data itself, the
concepts that the data represents (business processes, system applications), and the connections
between data and concepts. Metadata helps an organization understand its data, its systems and
its flow of information.

Metadata management is not only a challenge in knowledge management, it is also a necessary

risk. Without metadata, an organization cannot manage its data as an asset.

Business drivers
Data cannot be managed without metadata. Additionally, metadata itself must be manageable,
reliable, and help with good metadata management.

Data quality depends on governance, metadata is critical in governance. If metadata is a guide to

the data in the organization, then it must be well managed. Poor metadata management causes:

 Data redundancy and data management processes.

 Replication and redundancy of dictionaries, repositories and metadata stores.
 Inconsistent definitions of data elements and risks associated with misuse.
 Competing and conflicting with sources and versions of metadata reduces trust among
data consumers.
 Doubts about the reliability of metadata and data.

Goals and principles

Goals include:

 Documentation and organizational knowledge management of related data business

terminology to ensure that people understand the context and can use the data
consistently.
 Collect and integrate metadata from different sources to ensure that people understand
similarities and differences between data from different parts of the organization.
 Ensure the quality, consistency, timeliness and security of the metadata.
 Provide standard paths to make metadata accessible to consumers.
 Establish or reinforce the use of standard metadata techniques to enable data exchange.

Successful metadata implementation follows the following principles:

 Organizational commitment.
 Strategy.
 Business perspective.
 Socialization.
 Access.
 Quality.
 Audit.
 Improvement.

Essential concepts

1. Metadata VS data
The organization should not worry about the philosophy, it should focus on the requirements
being focused on what they need from the metadata (creating new data, understanding existing
data, enabling movements between systems, access data, sharing data) and data sources. to
respond to the requirements.

2. Types of metadata
 Business metadata. Focused largely on data context and condition, it includes data
governance details. It includes the non-technical part such as names, and definition of
concepts, areas, entities and attributes, range, description, calculations, algorithms and
business rules, valid domain values and their definitions.
 Technical metadata. Technical details of the data, the data warehouse system, and the
process that moves between systems.
 Operational Metadata. Describes details of the process and data accessibility.
3. ISO/IEC 11179 Metadata registration standard

Provides a frame of reference for the definition of a matadata record. It is designed to enable
metadata-driven data exchange, starting with data elements.

4. Metadata for unstructured data

By its nature, all data has a structure, however, not all data is formally structured in rows, columns
and stored in a relational database. Any data that is not in a database or data file, including
documents or other media, is considered unstructured data.

Metadata for unstructured data includes description metadata, as well as a description catalog,
keywords, structured metadata such as tags, field structure, formats, managed metadata, as well
as sources, updated programs, access rights, navigation information.

5. Metadata sources

Metadata can collect information from different sources, as long as they are well managed. Most
organizations manage metadata well at the tiers because metadata is often created as a by-
product of an application in progress rather than a finished product.

To give an idea of the breadth of metadata in an organization, the range of sources is outlined
here in alphabetical order:

1. Metadata repository application.

2. Business glossary.
3. Business intelligence tools.
4. Configuration of management tools.
5. Data Dictionary.
6. Data integration tools.
7. Systems catalog database administration.
8. Data mapping management tools.
9. Data quality tools.
10. Dictionaries and catalogues.
11. Event messaging tools.
12. Modeling tools and repositories.
13. Reference data repository.
14. Registry services.
15. Other warehouses detected
16. Types of metadata architecture
 Activities

1. Defines metadata strategy.

The strategy includes the definition of the future state of the company's metadata architecture
and the implementation phases required to meet the strategic objectives:

 Strategic metadata planning initiative.

 Conduct interviews with key users.
 Evaluate existing metadata and information architecture strengths.
 Development of future metadata architecture.
 Development of the phases of the implementation plan.
2. Understanding metadata requirements.
3. Define metadata architecture.
 Creation of metamodel.
 Application of metadata standards.
 Management of metadata stores.
4. Create and maintain metadata
 Integrated metadata.
 Distribute and send metadata.
5. Query, report and analysis of metadata

Tools

1. Metadata repository management tool.

 Techniques

1. Data lineage and impact analysis.

 Business focus. Limits lineage discovery to prioritizing data elements for the business.
 Technical approach. Start with the source system and identify all immediate consumers.
2. Metadata for big data ingestion

Implementation guide

1. Risk assessment.
2. Organizational and cultural change.

Metadata governance

1. Control processes.
2. Documentation of metadata solutions.
3. Metadata standard and guides.
4. Metrics.

Chapter 13. Data Quality Management

It includes planning and implementing data management measurement techniques, assets, and
improving the organization's data use capability.

Effective data management involves a complex set of interrelated processes that enables an
organization to use data to achieve strategic goals. Data management includes the ability to design
for applications, storage and entry securely, sharing appropriately, learning from it, and ensuring
business needs are met. An underlying premise about the value of data is the reliability and
trustworthiness of the information, in other words “high quality.”

All management disciplines contribute to data quality, and high data quality supports the
organization in achieving the goal of the data management disciplines.

Business facilitators

 Increase in the value of the organization .

 Reduction of risk and value associated with poor data quality.
 Improving organizational efficiency and productivity.
 Protection and improvement of the organization's reputation.
 Goals and principles

Data quality programs focus on general goals:

 Developing government approaches to make purposeful adjustments based on consumer

data.
 Definition of standards and specifications for data quality control as part of the data life
cycle.
 Definition and implementation of processes to measure, monitor and report data quality
levels.
 Identification and defense of opportunities to improve data quality, through changes in
processes and systems, and attractions in activities to improve data quality indicators
based on consumer data requirements.

Data quality programs should be guided by:

 Criticality.
 Life cycle management.
 Prevention.
 Root cause remediation.
 Governance.
 Standard drivers.
 Objective and transparent measurement.
 Embed business processes.
 Systematic effort.
 Connection with service levels.

Essential concepts

1. Data quality.
2. Critical data.
3. Data quality dimensions.

The term dimensions is used to make the connection of dimensions in the measurement of
physical objects.

In order to measure data, the organization needs to establish characteristics that are both
important: business processes and measurable.

15 dimensions across 4 data quality categories:

 Intrinsic data quality.

o Accuracy.
o Objectivity.
o Credibility.
 o Reputation.
 Contextual data quality
o Value added.
o Relevance.
o Chance.
o Complete.
o Appropriate amount of data.
 Representational data quality
o Timelessness.
o Easy to understand.
o Consistent presentation.
o Concise presentation.
 Affordable data quality
o Accessibility.
o Security access.
 4. Data and metadata quality.
5. ISO standards in data quality.

The intent of ISO 8000 is to help organizations define what data quality is and is not, enabling the
use of standards conventions, and verifying that they have received data quality using the
standards. When the standards are followed, the requirements are met when using computer
programs.

6. Implementation of the data quality life cycle.

The cycle begins with the identification of data that does not match consumer requirements and
questionable data that are obstacles in relation to the strategic objective of the business. The Data
needs to be evaluated again by the quality dimension keys and meet the business requirements.

The plan generates the scope, impact and priority of the known problems and evaluates
alternatives to solve them.

In “do” you direct the cause-effect paths of the problems identified in the plan.

“Review” involves quality monitoring activities by reviewing the requirements again.

The cost of fixing data the first time is less than using bad data and fixing it later.

7. Types of data quality business rules

Some common business rules are:

 Conformation of definitions.
 Present value and complete data.
 Compliance format.
 8. Common causes of data quality problems:
 Problems caused by lack of leadership.
 Problems caused by data loading process.

 Changes in business processes.

 Inconsistencies in the execution of business processes.
 Processes caused the functions of data processes.
 Problems caused by system design.
 Problems caused by problems fixed.
9. Data profile

Use statistical techniques to discover the real structure, content and quality of data collection.

10. Data quality and data processing.

While the focus is on error prevention, data processing can also be improved in some way.

 Data cleaning.
 Data improvement.
 Data formatting and analysis.
 Data transaction and standardization.

Activities

1. Definition of high data quality.

2. Definition of data quality strategy.
3. Definition of critical data and business rules.
4. Perform an initial data quality assessment.
5. Identification and prioritization of potential improvements.
6. Define goals for data quality improvement.
7. Development and deploy data quality operation.
 Administration of data quality rules.
 Data quality measurement and monitoring.

 Operational development of procedures for managing data problems.

 Establish data quality service level agreements.
 Development of data quality reports.

Tools

1. Data profile tool.

2. Data query tool.
3. Modeling and ETL tools.
4. Data quality rule templates.
5. Metadata repository.

Techniques

1. Prevention actions.
2. Corrective actions.
 3. Quality review and audit code modules.
4. Effective data quality metrics.
5. Static process control.
6. Route cause analysis.

Implementation guide

1. Risk evaluation.
2. Cultural and organizational change.

Data quality and data governance

1. Data quality policy.

2. Metrics.

Chapter 14. Big Data and Data Science.

It describes the technology and business processes that emerge as our ability to obtain and
analyze a large and diverse set of data.

Big data refers not only to the volume of data, but also structured and unstructured, documents,
files, audios, videos, transition data and the speed at which it is produced. People who develop
predictive, machine learning, and predictive models and analytics and generate analysis results for
stakeholders are called Data Scientists.

Data scientists have integrated models from mathematics, statistics, computer science, signal
processing, probabilistic models, pattern recognition, machine learning, uncertainty modeling, and
data visualization in order to obtain information and predict behavior in a big data set. Data
scientists have found new ways to analyze and derive value from data.

Business drivers

Decide to find and act on business opportunities that can be discovered through the set of data
generated through the diversification of processes.
 Essential concepts
1. Data science

It combines data mining, statistical analysis and machine learning with data integration and data
modeling capabilities, to build predictive models that explore the patterns contained in the data.
Developing predictive models sometimes called Data Science because data analysis or data
scientist uses the scientific method to evaluate.

Data science includes:

 Rich data source.

 Aligned information and analysis.
 Shipment information.
 Presentation of discoveries and data vision.
 2. The data science process

3. big data

It is characterized by the Vs:

 Volume. They generally contain thousands of entities or elements with millions of records.
 Speed. The speed at which data is captured, generated, shared. It can be generated and
analyzed in real time.
 Variety/variability. Refers to the way data is captured and sent. Big Data requires storage
in multiple ways. The structure is often inconsistent with data crossing.
 Goo. How difficult it is to use or integrate data.
 Volatility. How frequently changes occur and then how long the data is used.
 Veracity. How reliable is the data?
 4. Big Data Architecture Components

The selection, installation and configuration of the Big Data and Data Science environment
requires expert specialists. End to End architecture must be generated and rationalized from
existing data exploratory tools.

5. Big data sources

It is the product of emails, social, online requests and online video games. Data is not only
generated by telephone and point-of-sale devices, but also by surveillance systems, sensors in
transportation systems, medical monitoring systems, industrial and monitoring systems, satellites,
and military equipment.

6. data lake

It is a medium where a large amount of data of various types of structure can be ingested, stored,
and analyzed. They can serve several purposes:

 A means for mine data scientists to analyze data.

 A central repository area for raw data, with no or some transformation.
 Alternate store with historical data store details.
 Online archive for recordings.
 A means of transmitting with automatic pattern identification.
7. Architecture-based services

8. Machine learning

Explore construction and study learning algorithms. It can be seen as the union of unsupervised
learning methods, more commonly referred to as data mining, and supervised learning methods
deeply rooted in mathematical theory, specialized statistics, combinatorics, and optimization. The
third brand is now called reinforcement learning, where actualized goals are earned, but not
especially recognized by teachers.

Machine learning exploits the construction and study of learning algorithms, which fall into three
types:

 Supervised learning.
 Unsupervised learning.
 Reinforcement learning.

9. Sentiment analysis
It is used to understand what people say and feel about brands, products and services. Using
natural language processing (NLP) or partial phrases or sentences, semantic analysis can detect
feelings and also reveal changes in feelings and predict possible scenarios. IBM Watson.

10. Text and data mining

It is a type of analysis that reveals patterns in the use of data by various algorithms. Text Mining
analyzes documents with text analysis and data mining techniques to automatically classify
content in a guided workflow.

They use a range of techniques including:

 Profile
 Data reduction.
 Association.
 Grouping.
 Self-organizing maps.
11. Predictive analysis.

It is a part of supervised learning where users attend to a model of data elements and predict the
future through estimated probability evaluations.

12. Prescriptive analytics.

13. Analysis of unstructured data.

It combines text mining data analysis, association, clustering, and other unsupervised learning
techniques to encode large data sets.

14. Operational analysis

The concept of operational analytics (Known as operational BI or streaming analytics, is obtained

from the integration of real-time analysis into operations. It includes activities such as user
segmentation, sentimental analysis, geo-coding, and other techniques applied to data sets for
analysis of marketing campaigns, sales penetration, product adoption, asset optimization, and risk
management.

15. Data visualization

It is a process of interpreting concepts, ideas, and factors through the use of photographs or
graphic representations.

16. Data mashups

Combine and services to create visualization for analysis.

 Activities

1. Defines big data strategy and business needs

Must include evaluation criteria:

 What organizational problems are they trying to solve?

 What data source to use or acquire?
 The timing and extent of data provision.
 The impact and relationship with other data structures.
 Influence to the existence of data modeler.

The strategy will direct the scope and time of the organization in the map of Big Data capabilities.

2. Choose data sources.

Review the available sources and the processes that create those resources and manage the plan
for new sources:

 Fundamental data.
 Granularity.
 Consistency.
 Reliability.
 Inspection/profile new sources.
3. Acquire and ingest data sources.

Once sources are identified, they need to be found, sometimes purchased, and ingested (Loaded)
into the big data environment.

4. Development of data hypotheses and methods.

5. Data integration/alignment for analysis.
6. Exploit data using models.
 Populate data using models.
 Try the model.
 Evaluate the model.
 Create data visualizations.
7. Deploy and monitor.
 Presents vision and findings.
 Iterative with additional data sources.

Tools

The advancement in technology has created big data and the data science industry. To understand
the industry one must understand the enablers. The tools and techniques that enable big data
science to emerge will be explained.
 1. MPP non-shared technologies and architectures.

Massively parallel processing (MPP) has become a standard scientifically oriented data analysis
platform for big data sets.

2. Distributed file-based database.

Like open source Hadoop, it is a cheap way to store a large amount of data in different formats. It
is ideal for secure data storage, but has challenges when it comes to entering structured data or
data type mechanisms (SQL).

The language used is MapReduce, it has three main steps:

 Map.
 Deck of cards.
 Reduction.
3. Database algorithms.
4. Cloud database solutions.
5. Computational statistics and graphical languages.
6. Data visualization tools.

Techniques

1. Analytical modeling.

It is associated with different depth of analysis:

 Model description.
 Explanatory modeling.
2. Big data modeling.
Implementation guide
1. Strategic alignment.
Every big data/data science program must be strategically aligned with the organization's
objectives. Establishing a big data strategy, data security, metadata management, including
lineage and data quality management.
The strategy should document governance goals and principles. The ability to balance big data
with the skills and capabilities requirements of the organization.
The deliverables strategy must consider:
 Life cycle information.
 Metadata.
 Data quality.
 Data acquisition.
 Data access and security.
 Data governance.
 Data privacy.
 Learning and adoption.
 Operations.
2. Risk evaluation.
 Business relevance.
 Business preparation.
 Economic viability.
 Prototype.
3. Organization and culture of change.

The implementation of Big data will generate the following roles:

 Big data architecture platform.

 Ingestion architect.
 Metadata specialist.
 Analytical designer.
 Direct analytical design.
 Data science.

Governance

Sources, source analysis, ingestion, enrichment, and publication require business procedures, as
well as technical controls and addressing.

1. Channel management display.

2. Data science and visualization standards.
3. Data security.
4. Metadata.
5. Data quality.
6. Metrics.
 Techniques for using metrics.
  Loading and scanning metrics.
 Learning.

Chapter 15. Data Management maturity assessment.

Outline and approach to evaluating and implementing data management capabilities in an

organization.

Capability Maturity Assessment (CMA) is an approach based on the implementation of processes

within the framework of the capability maturity model, which describes how the characteristics of
processes evolve over an optimal design.

Maturity models are defined in terms of a progression of levels that describe process
characteristics. When an organization gains an understanding of process characteristics, its
maturity level can be assessed and a plan to improve its capabilities can be put in place. You can
also measure improvements and compare yourself or other companies, guided by the levels of the
model.

Before beginning any DMMA, the organization must establish a baseline understanding of its
current capabilities, assets, goals and priorities. A certain level of maturity in the organization is
required to conduct the evaluation initially, as well as respond effectively to the expected results
by establishing objectives.

Business facilitators

 Regulatory.
 Data governance.
 Organizational preparation for implementation processes.
 Organizational change.
 New technology.
 Problems in data management.
 Goals and principles

The first goal is to evaluate the current state of critical data management activities to plan for
implementation. The evaluation puts the organization on a maturity scale classifying strengths and
weaknesses. Helps the organization identify, prioritize and implement opportunities.

DMMA can have positive impacts on culture, helping in:

 Helping users with data management concepts, principles and practices.

 Clarifying user roles and responsibilities in relation to the organization's data.
 Emphasis on data management as a critical asset.
 Expand recognition of data management activities across the organization.
 Contribute to implementing the collaboration necessary for effective data governance.

DMMA helps the organization clarify priorities, crystallize objectives and develop a comprehensive
plan to implement.

Essential concepts
1. Evaluation of levels and characteristics.
 Level 0: Absence of capabilities.
  Level 1. Initial. Success depends on individual fulfillment.
 Level 2. Repeatable. Minimal project discipline is in place.
The roles are defined and the processes depend on a specific expert.
There is awareness in the organization about problems in the quality of data and concepts.
The concepts of master data are beginning to be known.
The evaluation criterion may include the presence of some control process, such as the
entry into quality problems.
 Level 3. Definite. The standards are in place and in use. The roles are defined.
See the introduction and institutionalization on a scale of management processes and DM
to a facilitator. Features include data replication across the organization with some
controls in place, and generally increasing data quality, just with defined policy
coordination and management.
Evaluation criteria may include the existence of data management policies, the use of
scalable processes, and the consistency of data model and control systems.
 Level 4. Administered. The processes are quantified and controlled. Institutionalization of
knowledge achieved at levels 1 to 3, allowing the organization to predict results, when
new projects and tasks approach and begin to manage risks related to data, metrics are
included. Standardization of data management tools from the desktop to the
infrastructure, coupled with a well-formed centralized planning and governance function.
Evaluation criteria may include metrics related to successful projects, system operation
metrics, and data quality.
 Level 5. Optimized. Implementation of process goals are quantified. When data
management practices are optimized, they are highly predictable through automated
processes and change management technologies.
Evaluation criteria may include change management artifacts and metrics in process
implementation.

2. Evaluation criteria.

At each level the evaluation criteria will be used independent of the scale of 1. Not started, 2. In
process, 3. Working and 4 effectively.
Categories in the conceptual diagram:

 Activity.
 Tool.
 Standards.
 People and resources

3. Existing DAMA Framework

 CMMI. Data Management Maturity Model .

The Capability Maturity Models Institute (CMMI) develops a maturity model with the following
criteria:

o Data management strategy.

o Data governance.
o Data quality.
o Platform and architecture.
o Data operations.
o Supported processes.

 EDM board DCAM

 IBM Data Governance Maturity Council
o Departures. Data risk management and compliance, value creation.
o Enablers. Organizational structure and awareness, policies and administration.
 o Core disciplines.
o Support disciplines
 Stanford Data Maturity Model.
 Gartner's enterprise information management maturity model.

Activities

1. Define objectives.
 Choose a frame of reference.
 Defines the scope of the organization.
 Defines interaction approach.
 Communication plan.
2. Evaluate maturity.
 Gather information.
 Perform the evaluation.
3. Interpret results.
 Evaluation results report.
 Development of execution instructions.
4. Create a program of objectives to implement.
 Identify actions and create a roadmap.
5. Re-evaluate maturity.

Tools

 Data Maturity Framework (DMM).

 Communication plan.
 Collaboration tools.
 Knowledge of data management and repository.

Techniques

1. Choose a DMM framework.

2. Use the DAMA framework.

Guide to DMMA

1. Risk evaluation
 2. Organization and cultural change.

Maturity in maturity management

1. Monitoring of the DMMA process.

2. Metrics.

Chapter 16. Data management organization and role of the viewer.

Provides best practices and considerations for the data management team and enables successful
data management practices.

It describes the set of principles that should be considered when putting data management and
data governance together in an organization.

Understand the existing organization and cultural norms

Awareness, ownership and responsibility are the keys to activating and engaging people in data,
policy and process management initiatives.
Once you take a snapshot of the current state, you evaluate the level of satisfaction and
organizational data management needs and prioritization.

The data management organization must align with the organization's hierarchy and its resources.
Finding the right people requires an understanding of the functional and political role of data
management in the organization. The object should be to find multifunctional personnel:

 Identifies employees who are currently developing data management activities. Identify
and involve them first. Hire additional resources only such as data and governance
administrator if required.
 Examines the methods the organization uses to manage data and determines how the
processes can be implemented. Determine how much change is required to implement
data management practices.
 Roadmap of the type of organizational changes needed to meet the requirements.

Building the data management organization

1. Decentralized operating model.

2. Network operation model.

3. Centralized operation model.

4. Hybrid operating model.

 5. Federated operation model.

6. Identify the best model for a company.

Identify the current organizational structure, whether it is centralized or decentralized, how

independent is it divisions, regions, does it operate in a self-sufficient manner?

It tries to determine how decisions are made, as well as how they are implemented.

The answer will provide a starting point to understand the location of the organization.

7. DMO alternatives and design considerations.

Most organizations start with a decentralized model before starting with a formal organizational
model. As an organization you have to visualize the impact on data quality, this can start with a
RACI data management matrix and move towards a network model.
Consider the following recommendations:

 Determines the starting point based on the current state.

 Link the operating model to the organizational structure.
 Take into account:
o Organizational complexity and maturity.
o Domain complexity and maturity.
o Scalability.
 Get an executive sponsor.
 Consider a pilot program.
 Focus on high impact value, higher impact domains.
 Use what already exists.

Critical factors of success

1. Executive sponsor.
2. Clear vision.
3. Proactive change management.
4. Alignment with leadership.
5. Communication.
6. Commitment to users.
7. Guidance and training.
8. Measurement adoption.
9. Adherence to guiding principles.
10. Evolution not revolution.

Building the data management organization

1. Identifies current data management involvement.

2. Identify the committee participants.
3. Identify and analyze users.
4. Involve users.
 Interaction between DMO and other data-oriented bodies

Once the model is established and the participants are identified, it is time to move people into
the new authorized roles.

1. Head of the data office.

2. Data governance body.
3. Data quality.
4. Business architecture.

Data governance

It is the organizational framework to establish the strategy, objectives, and policies for effective
corporate data management. It consists of processes, policies, organization and technologies
required to manage and ensure the availability, usability, integrity, consistency, audibility and
security of data.

Enterprise architecture

 Technological architecture.
 Application architecture.
 Data architecture.
 Business architecture.
 Manage a global organization

Special attention on:

 Adhere to standards.
 Process synchronization.
 Aligned accounting.
 Training and communication.
 Effective monitoring and measurement.
 Development of economies of scale.
 Reduction of duplication of effort.

Data management roles

1. Organizational roles.
2. Individual roles.
 Executives.
 Business.
 YOU.
 Hybrids.

Chapter 17. Data management and organizational change management.

Describes how to plan through the cultural changes that are necessary to introduce data
management practices into the organization.

Laws of change

 Organizations don't change, people change.

 People don't resist change.
 Things are the way they are.
 Unless you push for change, things will keep you where you are.
 The change will be easy and it is for everyone.

Don't manage the change, manage the transition

 8 mistakes in change management

1. Allowing too much complacency.

2. Failure to create enough power in the coalition guide.

3. Underestimate the power of vision.
4. Low vision communication.
5. Allow obstacles in vision.
6. Failing to create short-term achievements.
7. Declaring victory too soon.

8. Negligence in anchoring channels in the corporate culture.

The formula of change
Diffusion of innovations and sustainable changes
 Sustainable change

1. Sense of urgency / Dissatisfied.

2. Flame the vision.
3. Guide the coalition.
4. Progress and relative observance.

Communicating data management values

1. Communication of principles.
2. Audience evaluation and preparation.
3. The human element.
4. Communication plan.
5. Keep in contact.