Equipment State

Equipment state commonly refers to the current operating condition or status of a specific piece of equipment, asset, or line as recognized and tracked by control systems, manufacturing execution systems (MES), maintenance systems, or other monitoring tools.

In industrial and regulated manufacturing environments, equipment states are usually represented as a defined set of codes or labels that describe what the equipment is doing at a point in time. These can be used for control logic, production tracking, quality decisions, maintenance planning, and performance metrics such as OEE.

Typical examples of equipment states

Exact state models vary by site, standard, or vendor, but common categories include:

• Running / Operating: The equipment is producing or executing its intended process.
• Idle / Waiting: The equipment is capable of running but not currently executing work (for example waiting for material, operator, or authorization).
• Down / Faulted: The equipment cannot run due to a failure, alarm, interlock, or other fault condition.
• Setup / Changeover: The equipment is being adjusted between products, batches, or formats.
• Maintenance: The equipment is in planned or unplanned maintenance, cleaning, or calibration.
• Offline / Powered down: The equipment is not available to the production system, often powered off or disconnected.
• Hold / Locked: The equipment is prevented from use due to a quality, safety, or compliance hold or authorization requirement.

How equipment state is used in operations

Equipment state information is typically generated and consumed across multiple layers of industrial systems:

• Control and OT systems: PLCs, DCS, and SCADA systems detect conditions (for example interlocks, sensor states) and set or infer the equipment state for real-time control and alarms.
• MES and production systems: MES applications capture equipment states for scheduling, dispatching, batch execution, electronic batch records (eBR), and production event logs.
• Maintenance and asset systems: CMMS/EAM tools may consume state data to trigger work orders, track run hours, or schedule preventive maintenance.
• Performance monitoring: OEE and other analytics use equipment state to segment time into productive, planned, and unplanned loss categories.

In regulated environments, equipment state can also be relevant for determining whether equipment is qualified, within calibration, or permitted for use in a specific process or lot, with related evidence recorded in quality or validation systems.

Common confusion

• Equipment state vs. equipment mode: “Mode” often refers to how equipment is being controlled (for example automatic, manual, local, remote). “State” typically describes what the equipment is currently doing or its availability. Some systems combine both, but they serve different purposes.
• Equipment state vs. equipment condition: “Condition” is often used for health or degradation (for example good, worn, needs service). “State” is more about operational status at a point in time.
• Equipment state vs. batch or process state: Batch or process state focuses on the product or procedure (for example charging, reacting, filling), while equipment state focuses on the asset itself. They are related but not identical.

Relation to standards and models

Industry standards and reference models often define or influence equipment state models, including:

• Manufacturing operations models that define equipment status categories for availability and performance calculations.
• ISA-95 style hierarchies where equipment state is part of the information exchanged between control systems and MES/ERP.
• Vendor-specific state models in packaging, process, or discrete equipment that map into plant-wide OEE and downtime structures.

When integrating systems, it is common to map vendor- or site-specific equipment states to a standardized set used for plant-wide reporting and compliance documentation.