Inferensys

Glossary

Hierarchical Time Series

A structured collection of time series organized by aggregation constraints, such as product categories rolling up to departments or regional demand summing to national totals.
Wide-angle shot of a modern WeWork open floor plan with creative walls covered in AI system architecture diagrams, product team collaborating in standing desk area with industrial lighting.
AGGREGATION STRUCTURES

What is Hierarchical Time Series?

A structured collection of time series organized by aggregation constraints, such as product categories rolling up to departments or regional demand summing to national totals.

A hierarchical time series is a structured collection of individual time series linked by linear aggregation constraints, where lower-level series (e.g., SKU-level sales) sum exactly to higher-level nodes (e.g., product category or national totals). This structure imposes a strict mathematical coherence requirement: forecasts generated independently at different levels will almost certainly violate the sum-to-one consistency, necessitating formal forecast reconciliation to align bottom-up and top-down predictions.

The hierarchy is typically defined by a summing matrix that encodes the organizational structure—whether a product taxonomy, geographic rollup, or cross-dimensional lattice combining both. Advanced approaches like the MinT (Minimum Trace) reconciliation method leverage the covariance structure of base forecast errors to produce optimal coherent forecasts that minimize expected loss across all levels simultaneously, ensuring supply chain decisions at any aggregation node are consistent with granular operational plans.

STRUCTURAL PROPERTIES

Key Characteristics

Hierarchical time series impose aggregation constraints that require specialized modeling and reconciliation techniques to ensure coherent, decision-ready forecasts across all levels of the supply chain.

01

Aggregation Constraints

A defining property where lower-level series must mathematically sum to higher-level totals. In supply chains, daily SKU-level demand at a specific warehouse must equal the weekly regional demand for that product category.

  • Summing matrix: A linear operator that maps bottom-level forecasts to all higher aggregation nodes
  • Coherency violation: Occurs when independently generated forecasts at different levels produce conflicting totals
  • Cross-sectional hierarchy: Product, geographic, and temporal dimensions create intersecting aggregation paths
  • Example: National sales forecast ≠ sum of regional forecasts, creating confusion for inventory planners
02

Reconciliation Strategies

Methods for adjusting base forecasts to enforce mathematical coherence across the hierarchy without sacrificing accuracy at any level.

  • Bottom-up: Generate forecasts at the most granular level and aggregate upward—preserves detail but amplifies noise
  • Top-down: Forecast at the highest level and disaggregate using historical proportions—stable but loses local patterns
  • Middle-out: Start at an intermediate level, forecast up and down—balances granularity and stability
  • Optimal reconciliation: Uses generalized least squares to produce coherent forecasts that minimize total error variance across all levels
03

Cross-Level Correlation

The statistical dependencies that exist between series at different hierarchical levels, which naive independent forecasting ignores.

  • Shared shocks: A supply disruption at a regional distribution center simultaneously impacts all downstream store-level series
  • Information pooling: Higher-level aggregates often exhibit more stable patterns, providing useful regularization for noisy bottom-level forecasts
  • Covariance estimation: Optimal reconciliation requires estimating the full covariance matrix of base forecast errors across all nodes
  • Example: A national promotion lifts all regional demand simultaneously, creating correlated forecast errors that reconciliation must account for
04

Temporal Hierarchies

Aggregation constraints that operate across time dimensions, where daily forecasts must sum to weekly, monthly, and quarterly totals.

  • Non-overlapping aggregation: Daily → Weekly → Monthly → Quarterly → Annual
  • Seasonal alignment: Weekly patterns must be preserved when aggregating to monthly buckets
  • Forecast horizon consistency: Short-term daily forecasts and long-term annual projections must not contradict each other
  • Example: A demand sensing model predicting daily sales must reconcile with the S&OP process's monthly volume forecast
05

Probabilistic Coherence

Extending reconciliation beyond point forecasts to ensure that entire predictive distributions are consistent across hierarchy levels.

  • Distributional reconciliation: Adjusts quantile forecasts so that the sum of lower-level distributions matches the upper-level distribution
  • Copula-based methods: Model the dependence structure between hierarchical nodes to preserve joint distributional properties
  • Gaussian aggregation: Under normality assumptions, the mean and variance of aggregated forecasts can be derived analytically
  • Example: The 95th percentile of national demand must equal the convolution of regional demand distributions, not their simple sum
06

Forecast Value Added Analysis

A diagnostic framework for measuring whether hierarchical reconciliation improves or degrades accuracy at each node compared to base forecasts.

  • Node-level metrics: Evaluate reconciliation impact using CRPS or MASE at every aggregation point
  • Reconciliation penalty: Some nodes may experience accuracy loss to achieve global coherence—quantify this trade-off
  • Disaggregation gain: Bottom-level forecasts often improve when informed by stable top-level patterns
  • Example: A retail chain finds that reconciliation reduces regional forecast error by 12% but increases store-level error by 3%, requiring a business decision on acceptable trade-offs
HIERARCHICAL FORECASTING CLARIFIED

Frequently Asked Questions

Clear, technically precise answers to the most common questions about structuring, reconciling, and optimizing hierarchical time series models for enterprise supply chain intelligence.

A hierarchical time series is a structured collection of individual time series organized by aggregation constraints, where lower-level data (e.g., SKU-level daily sales) sums exactly to higher-level data (e.g., category-level monthly totals). The structure works by defining explicit parent-child relationships across multiple dimensions—such as product hierarchies (item → brand → category → division) and geographic hierarchies (store → city → region → country)—creating a tree or lattice topology. Each node in the hierarchy generates its own forecast, but these independent predictions almost never satisfy the aggregation consistency constraint naturally. The core operational challenge is that the sum of bottom-level forecasts rarely equals the independently generated top-level forecast, creating a mathematical incoherence that must be resolved through reconciliation algorithms. In supply chain contexts, this structure enables planners to generate demand signals at the granular SKU-location level while maintaining strategic alignment with aggregate financial and capacity plans at the regional and global levels.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.