AI Data Model Generator

Build a BI data model from the business, not from the source system

A reporting model is not a copy of ERP tables. It is a structure for questions: facts you measure, dimensions you slice by, and relationships that keep those questions consistent. BiDesignLab designs that model from the brief and the schema you provide.

Star schema without a separate generator page

Star schema, fact tables and dimension tables are parts of one job: make the dashboard calculable. Splitting them into thin pages would repeat the same idea. Here they stay together.

AI proposes which tables behave as facts, which as dimensions, how they should relate, and where a date table is required — so KPIs and DAX have a grain they can use.

What the model is for

The model exists so a KPI such as “margin versus plan by region this year” has a path through the data. If the source schema is transactional and messy, the design still aims at a reporting shape rather than exposing every source table on the canvas.

  • Facts for processes you measure (sales, occupancy, jobs, invoices)
  • Dimensions for how you slice (customer, product, site, time)
  • Relationships that match the grain of the KPIs
  • A calendar when time intelligence is part of the brief

From model to dashboard

Once the model is accepted, KPI design and dashboard pages use it. That is the difference between a data-model sketch and a BI solution: the same structure feeds measures and visuals instead of living in a separate diagram.

Questions

Do I need a perfect warehouse before I start?
No. You need table and column structure. The generator designs a reporting model from that. Physical loading and refresh stay in your BI tool.
Is this only Kimball / star schema?
The default is a reporting-friendly star-style model because dashboards and DAX work best that way. The point is a usable BI model, not a textbook diagram.