🏢Enterprise Data Model

NEW

Also known as: Enterprise Information Model, EDM

A comprehensive, organization-wide conceptual and logical model defining standard entities, relationships, and data definitions across domains.

DESCRIPTION

An Enterprise Data Model (EDM) provides consistent definitions and structures across business domains. It supports integration, governance, and reuse by creating common vocabularies and canonical structures. EDMs can be realized as conceptual glossaries and logical schemas aligned with MDM and reference data. Centralized EDMs suit highly regulated environments; federated approaches align with domain ownership. Maintenance requires versioning, stewardship, and change control. EDMs often feed semantic layers and integration contracts.

ALTERNATIVE DEFINITIONS

DATAVERSITY

An Enterprise Data Model is a single integrated definition of data, unbiased of any system or application, which is intended to be used for consistent data sharing across the enterprise.

Stresses neutrality from systems and integration for sharing.

Source

erwin by Quest

An enterprise data model is a high-level, holistic data model that shows how an organization’s data is structured and related, providing a common vocabulary and design standards.

Highlights common vocabulary and standards across the organization.

Source

RELATED TERMS

Governance Master Data Management Data Glossary Reference Data Domain Model Data Architecture Semantic Layer Data Discovery Platform Data Integration Data Standards

COMPETING TERMS

Decentralized Data Architecture Federated Domain Model

RELATIONS

• Broader: Model

KNOWLEDGE AREAS

Data Modeling Data Architecture Data Management Metadata Management

TARGET AUDIENCE

Chief Data Officer Data Architect Data Modeler Data Steward Information Analyst Enterprise Architect

EXTERNAL SOURCES

• Wikipedia - Data model
• DATAVERSITY - EDM concept and benefits
• erwin by Quest - Tooling support for EDMs
• DAMA International - DMBOK guidance on data modeling

TOP QUESTIONS

Why adopt an Enterprise Data Model?

It provides consistent definitions and structures, reducing integration friction and supporting governance across systems and domains.

Category: Relevancy

What is the biggest risk of an Enterprise Data Model?

Over-centralization can slow delivery and misfit local needs. Governance must balance standards with domain flexibility.

Category: Risks

How does an Enterprise Data Model relate to Data Mesh?

EDM centralizes standards, while Data Mesh favors federated ownership. Many organizations combine a lightweight EDM with domain autonomy.

Category: Alternatives

Who should own an Enterprise Data Model?

A central data architecture team with domain stewards should co-own it, ensuring alignment and adoption.

Category: Management

How detailed should an Enterprise Data Model be?

Keep it conceptual/logical with reusable patterns; avoid physical details that vary by implementation.

Category: Opinion

What is a common mistake with Enterprise Data Models?

Attempting to model everything upfront; instead, evolve iteratively with governed change management.

Category: Mistakes

How do EDMs support MDM?

They define canonical structures and attributes for master domains, easing matching, survivorship, and integration.

Category: Example

What tools help maintain an Enterprise Data Model?

Modeling repositories, catalogs, and version control with review workflows help scale governance.

Category: Requirements

When is an Enterprise Data Model most valuable?

In regulated or multi-system environments requiring consistent definitions for compliance and reporting.

Category: Example