Glossary/Semantic Layer & Metrics

Dimension

A dimension is a categorical or descriptive attribute used to slice, filter, and organize metrics, such as product, region, customer segment, or date.

Dimensions are the business categories by which metrics are analyzed. While metrics answer "how much" (revenue, count, duration), dimensions answer "by what lens" (by product, by region, by customer cohort). A dimension is typically non-additive: summing revenue by product makes sense, but summing a customer's region does not. Dimensions usually come from dimension tables in a star schema or are calculated attributes derived from fact tables.

Dimensions solve the need to slice metrics across multiple perspectives. Without dimensions, you can only report aggregate metrics: total revenue. With dimensions, you can analyze revenue by product category, region, and customer segment simultaneously. Dimensions typically have hierarchies: date rolls up from day to week to month to year; product rolls from SKU to product line to category.

In semantic models and metric layers, dimensions are formally defined: their values, hierarchies, relationships to metrics, and any transformations (category mapping, fiscal vs. calendar time). Not all dimensions apply to all metrics: a metric like "infrastructure uptime" wouldn't sensibly filter by product dimension. The semantic layer documents valid dimension combinations.

Key Characteristics

  • Typically categorical or descriptive in nature
  • Non-additive: values don't meaningfully sum
  • Often organized in hierarchies
  • Used to filter, group, and segment metrics
  • Formally defined in semantic models
  • Linked to specific fact tables or metrics

Why It Matters

  • Flexibility: Slice metrics across business perspectives
  • Analysis: Compare metric performance across segments
  • Drill-down: Navigate from summary to detail across hierarchies
  • Consistency: Standardized dimension definitions prevent misalignment
  • Performance: Pre-computed dimensions enable fast aggregations

Example

A revenue metric has valid dimensions: product category (Electronics, Services), region (North America, Europe, APAC), customer segment (Enterprise, Mid-Market, SMB), and date (day, month, quarter). Valid queries include revenue by product and region, or revenue by customer segment over time. Invalid queries (revenue by product and infrastructure uptime customer) are caught by the semantic model.

Coginiti Perspective

SMDL dimensions are typed as text, number, date, datetime, or bool, which enforces valid operations at query time. Dimensions can reference physical columns directly or define calculated expressions for derived attributes. Hidden dimensions allow intermediate calculations that other dimensions or measures reference without exposing them to analysts. Semantic SQL resolves dimension references across entity relationships automatically, so analysts filter or group by dimensions from related entities without writing explicit joins.

See Semantic Intelligence in Action

Coginiti operationalizes business meaning across your entire data estate.