What Is a Derived Model?

In data modeling, derived models are created by reusing components of a core entity model while applying transformations, filters, or perspectives that suit a particular business or technical need. They allow teams to customize data access without duplicating logic, helping ensure consistency, scalability, and reuse across projects.

Key Facts About Derived Models

Derived models extend core entity models to support specialized views without rebuilding from scratch. They enable flexibility while maintaining standardization and reducing effort.

• Foundation on entity models: Built on validated schemas, ensuring consistency and trust in the base structure.
• Specialized use-case support: Designed for unique reporting needs, user roles, or integrations without altering the main model.
• Reusability of logic: Share calculated fields, filters, and joins across different models to reduce redundancy.
• Consistency in definitions: Maintain common KPIs and metrics across teams and tools.
• Adaptability across teams: Easily tweak data views for product, marketing, finance, or operations without starting from scratch. 

Types of Derived Models

Derived models typically fall into two categories depending on how and where they are used:

• DTO (Data Transfer Object) Models: Created from the abstract entity model and used to expose structured, minimal data in services or MVC applications. Ideal for transferring data efficiently between systems.
• Document Models: Also based on the core entity model but adapted for document databases. Useful for representing nested or semi-structured data formats commonly found in NoSQL environments.

Why Use an Entity Model to Build Derived Models?

Using an entity model as the foundation ensures that derived models are consistent, traceable, and built on a shared understanding of the data.

By grounding derived models in an abstract entity model, teams can communicate the logic and intent behind data projections clearly. It offers a transparent view of how business logic is applied, both in design and in code. 

This approach also introduces a dedicated schema layer, which is especially valuable in environments like document databases where schemas are often implicit. An entity model clarifies how data is structured and why, making it easier to govern, reuse, and evolve derived models over time.

Derived models are especially valuable in large-scale data environments where different teams need customized but reliable access to shared data. By extending entity models with purpose-built views, they support faster development, better collaboration, and reduced duplication. Whether you’re modeling marketing funnels or operational KPIs, derived models offer a smart way to scale insights.

OWOX BI SQL Copilot: Your AI-Driven Assistant for Efficient SQL Code

OWOX BI SQL Copilot simplifies how you work with derived models in BigQuery. It provides intelligent SQL recommendations, validates logic in context, and helps automate the creation of structured queries. With Copilot, data analysts and marketers can adapt models quickly while keeping alignment with shared schemas, saving time and reducing the risk of error. 

GlossaryData Modeling

Related terms

Entity Relationship DiagramWhat Is an Entity in Data Modeling? DefinitionWhat Is a Dataset? Definition & ExamplesWhat Is an RDBMS? Definition & ExamplesAbstraction in Data ModelingACID Compliance

Learn more about analytics

data modelingSnowflake Schema in Data ModelingJul 30, 2026→data modelingData Mart Design: Structuring Flat TablesJun 23, 2026→data modelingUnderstanding Star Schema: Guide with ExamplesJun 15, 2026→