Glossary

    An enterprise data model is only useful while it matches the warehouse

    An enterprise data model describes the main business entities a company runs on, such as customer, order, invoice and product, the attributes of each, and how they relate. It is the shared reference for every system and report, and it goes stale fast if nobody ties it to the tables that actually hold the data.

    By Rig · Last updated

    Book a call with an architect

    At a glance

    • An enterprise data model names the business entities, their attributes and the relationships between them.
    • It usually has conceptual, logical and physical levels, from business terms down to tables and columns.
    • Rig Map keeps the model tied to the warehouse, as an ontology over your real tables, updated as schemas change.

    What is an enterprise data model?

    It is the agreed picture of a company’s data. At the conceptual level it lists entities such as customer and contract and how they relate: a customer has many contracts. At the logical level it adds attributes and keys. At the physical level it maps those to real tables and columns in each system. The model answers questions like which system owns the customer record, and what counts as an active contract.

    How do teams build one?

    Usually by hand, in a modelling tool or a set of diagrams, during a warehouse build or a migration. The work starts with interviews and the schemas of the main systems, and ends with a model the architects sign off. After that, systems change every week, and a diagram nobody opens does not update itself.

    Why do AI agents need an enterprise data model?

    An agent asked about revenue by customer has to know which table is the customer, how it joins to invoices, and which definition of revenue applies. Without that, it picks whichever table looks right. A data model tied to the physical tables, with meanings and certified metrics attached, gives the agent that knowledge before it writes SQL.

    How Rig does it

    Rig Map is an ontology over the warehouse you already run. It records what each table and column means, how tables join, which business terms and metrics are certified, and which systems and reports depend on them. Rig drafts it from your schemas and the queries your team runs, your data owners certify it, and Rig rereads the warehouse when a schema changes.

    Common questions

    What is an enterprise data model?

    It is a shared description of a company’s main business entities, their attributes and the relationships between them, mapped down to the tables and columns that hold the data.

    What is the difference between an enterprise data model and a semantic layer?

    The data model describes entities and relationships. A semantic layer defines business metrics on top of them, such as revenue or churn, so every tool calculates them the same way.

    How do you keep an enterprise data model current?

    Tie it to the warehouse. Rig Map rereads schemas when they change and flags new or changed tables for your data owners to review.

    Sources and product details

    Vendor information checked on 20 November 2026. Confirm current editions, licence terms and prices with the vendor before buying.

    Talk to Rig

    What work do you want to improve?

    Tell us where your team spends time, loses money or needs better information.
    In a 30-minute call, we’ll discuss the data and systems work that could help.

    Book a call with an architectUse the platform with your team, or add our engineers.