Glossary

operational baseline

An operational baseline is a documented reference point for normal process, system, or performance conditions.

Core Aerospace Operations Execution Lean and Process Improvement (HMLV Aerospace)Lean Manufacturing and Process Optimization

An operational baseline is a defined reference point for how a process, asset, production line, or system normally operates at a given time. It commonly includes the expected settings, conditions, performance ranges, and control context used to compare future operation against a known state.

In manufacturing and regulated operations, an operational baseline may cover items such as standard cycle times, equipment parameters, approved process settings, expected throughput, normal alarm patterns, quality levels, or system configuration details. The exact content depends on what is being baselined: a machine, a production cell, a software environment, a plant utility system, or a broader operation.

The term is descriptive, not necessarily fixed forever. A baseline can be revised when approved changes are made, but at any point in time it serves as the reference for detecting drift, assessing deviations, investigating issues, and evaluating whether current performance or configuration still matches the expected state.

What it includes and excludes

Includes the documented or agreed normal state used for comparison.
Includes operational, technical, or performance attributes that are relevant to monitoring and control.
Excludes temporary conditions such as startup, shutdown, maintenance mode, or known abnormal events unless those are explicitly defined as separate baselines.
Excludes a target or aspiration by itself. A baseline is usually the current or validated reference state, not just a future goal.

How it is used in practice

Operational baselines are commonly used in daily management, process monitoring, quality review, and change control. For example, a plant may compare current machine performance against a baseline established after qualification, or compare current OT network traffic against a baseline of normal communications to identify unusual activity. In MES, ERP, historian, or monitoring environments, the baseline may be reflected in master data, approved recipes, version-controlled settings, or KPI thresholds.

Common confusion

Operational baseline is often confused with a performance target. A target states the desired result, while a baseline states the reference condition used for comparison.

It can also be confused with a configuration baseline. A configuration baseline usually focuses on approved technical components, versions, or settings. An operational baseline is broader and may include how the process or system behaves in use, including expected operating ranges and performance patterns.

In some contexts, people also use the term similarly to standard work or a golden batch, but those are narrower ideas. Standard work defines the approved method for performing tasks, and a golden batch refers to a model production run or parameter profile. An operational baseline may incorporate aspects of both without being limited to either one.

DoE is usually the structured data-generation method that makes AI-based process window optimization credible. It helps identify which inputs matter, quantify interactions, and expose operating limits with fewer trials than one-factor testing. In regulated plants, its value depends on measurement quality, traceability, model validation, and controlled deployment into existing MES, QMS, and historian environments.

What are the 5 M's of manufacturing?

The 5 M’s of manufacturing are Man (people), Machine, Material, Method, and Measurement. They provide a simple way to structure cause-and-effect thinking, for example in fishbone diagrams and root cause analysis. In regulated, high‑consequence environments they must be applied with care, with clear traceability and data to support any conclusions.

Related Glossary