Feature store

A feature store is a data management layer used in machine learning to create, organize, store, version, and serve features, which are the input variables used by models. It commonly provides a consistent way to use the same feature definitions in model development and in live or near-real-time scoring.

In industrial and manufacturing settings, a feature store may hold engineered inputs derived from historians, MES, ERP, quality systems, lab systems, sensors, and maintenance records. Examples include rolling average temperature, cycle-time variance, recent alarm counts, supplier defect rate, or the number of nonconformances for a part family over a defined period.

What it includes

A feature store commonly includes:

• Feature definitions, including business logic or transformation rules used to derive model inputs
• Storage for historical features used in training and validation
• Serving capabilities for operational use, such as batch or online retrieval for inference
• Metadata and governance, such as lineage, versioning, ownership, freshness, and data quality information

It is not the same thing as a general data lake, historian, or data warehouse, although it often depends on those systems as upstream sources.

Operational meaning

Operationally, a feature store helps teams avoid recreating the same feature logic in multiple notebooks, scripts, or applications. In a manufacturing workflow, this can support repeatable model inputs for use cases such as predictive maintenance, quality prediction, yield analysis, anomaly detection, or schedule risk scoring.

For example, a plant may define a feature such as the last 12-hour vibration trend for a machine, or the count of rework events for a work order. The feature store can make that definition available both for model training on past production data and for current scoring in a monitoring or decision-support workflow.

Common confusion

Feature store vs. data lake: a data lake stores broad raw or curated datasets, while a feature store is focused on model-ready inputs and their reuse.

Feature store vs. model registry: a model registry tracks models and their versions, while a feature store tracks and serves the input features used by those models.

Feature store vs. ETL pipeline: ETL pipelines move and transform data, but a feature store adds a reusable layer for feature management, serving, and governance.

Boundary note

The term usually refers to infrastructure for machine learning operations rather than a user-facing application. Some platforms bundle feature store functions with broader MLOps, analytics, or data engineering tools, so the exact product boundary can vary.