Enterprise data management

Enterprise Data Management or EDM is:

1. A concept – referring to the ability of an organization to precisely define, easily integrate and effectively retrieve data for both internal applications and external communication.

2. A business objective – focused on the creation of accurate, consistent and transparent data content. EDM emphasizes data precision, granularity and meaning and is concerned with how the content is integrated into business applications as well as how it is passed along from one business process to another.

Enterprise data management should not be viewed as dependent on a specific technology strategy or related to an explicit data type definition. It arose to address circumstances where users within organizations independently source, model, manage and store data. These uncoordinated approaches by various segments of the organization can result in data conflicts and quality inconsistencies – making it difficult for users to trust the data as it is incorporated into models, mapped to applications, used to perform calculations, shared among supply chain participants and relied upon for decision-making.

The goal of enterprise data management is trust and confidence in data assets. Effective EDM has multiple components including:

Strategy and Governance

EDM requires a strategic approach to choosing the right processes, technologies and governance. EDM is often a challenge for organizations because it requires alignment among multiple stakeholders (including IT, operations, finance, strategy and end-users) and relates to an area (i.e. data content management) that has not traditionally had a clear “owner.”

The governance challenge can be a big obstacle to the implementation of an effective EDM strategy because of the difficulties associated with providing a clear business case on the benefits of data management. The core of the challenge is due to the fact that data quality has no intrinsic value. It is an enabler of other processes and the true benefits of effective data management are systematic and intertwined with other processes. This makes it hard to quantify all the downstream implications or upstream improvements.

The difficulties associated with quantification of EDM benefits can translate into challenges with the positioning of EDM as an organizational priority. Achieving organizational alignment on the importance of data management (as well as managing data as an ongoing area of focus) is the domain of governance.

Program Implementation

Implementation of an EDM program encompasses a myriad of processes – all of which need to be coordinated throughout the organization and managed while maintaining operational continuity. Below are some of the major components of EDM implementation that should be given serious consideration:

Stakeholder Requirements

EDM requires alignment among multiple stakeholders (at the right level of authority) who all need to understand and support the EDM objectives. EDM begins with a thorough understanding of the requirements of the end users (and the organization as a whole). Managing stakeholder requirements is a critical, and ongoing, process based in an understanding of workflow, data dependencies and the tolerance of the organization for operational disruption. Many organizations use formal processes such as service level agreements to specify requirements and establish EDM program objectives.

Policies and Procedures

Effective EDM usually includes the creation, documentation and enforcement of operating policies and procedures associated with change management, data models, data cleansing and normalization, data stewardship, security constraints and precedence rules. In many cases, these policies and procedures are documented for the first time as part of the EDM initiative.

Data Definitions and Tagging

One of the core challenges associated with EDM is the ability to compare data that is obtained from multiple internal and external sources. In many circumstances, these sources use inconsistent terms and definitions to describe the data content itself – making it hard to compare data, hard to automate business processes, hard to feed complex applications and hard to exchange data. This frequently results in a difficult process of data mapping and cross-referencing. Normalization of all the terms and definitions at the data attribute level is referred to as the metadata component of EDM and is an essential prerequisite for effective data management.

Platform Requirements

Even though EDM is fundamentally a data content challenge, there is a core technology dimension that must be addressed. Organizations need to have a functional storage platform, a comprehensive data model and a robust messaging infrastructure. They must be able to integrate data into applications and deal with the challenges of the existing (i.e. legacy) technology infrastructure. Building the platform or partnering with an established technology provider on how the data gets stored and integrated into business applications is an essential component of the EDM process.

Enterprise data management as an essential business requirement has emerged as a priority for many organizations. The objective is confidence and trust in data as the glue that holds business strategy together.

See Also

• Master Data Management

References

Enterprise Data Management Council http://www.edmcouncil.org

• Issues in Enterprise Data Management: A Survey Report, 12/06

Information Resource Managers Association - Steps in Building the EDM roadmap

• EDM Roadmap Development

Building and Integrating a Data Management Maturity Model Into the Roadmap - Information Resource Managers Association

• EDM Maturity Model Integration

Data Management Maturity Assessment Tool

• Online Tool to Assess Current State