How to Select the Right Industrial Fan: The Complete Buyer’s Guide

Choosing an industrial fan sounds simple until you realize that a fan rated at 8,000 CFM in a catalog can deliver a fraction of that once it is pushing air through ductwork, a filter, or a hot control cabinet.

Pick the wrong one, and you get hot spots, tripped motors, noisy workspaces, wasted electricity, and in the worst cases, a ventilation system that cannot keep a hazardous atmosphere under control.

This guide walks through every factor that matters when you select an industrial fan: airflow, pressure, fan type, motor, environment, safety, noise, controls, and total cost. For each fan type you will also find a recommended product on Amazon.

Affiliate disclosure

As an Amazon Associate, controlcircuitry.com earns from qualifying purchases. Recommendations are based on the specifications and the application fit described below. Always confirm current specs, voltage, and price on the product page before buying.

 How to Choose an Industrial Fan

Define the job

Cooling people, moving air through a space, exhausting fumes, drying surfaces, or cooling equipment are different problems.

Calculate required airflow (CFM)

From room volume and the air changes per hour you need.

Check static pressure

If air must travel through ducts, filters, or louvers, you need a fan that holds its flow against resistance.

Match the fan type to the job

Axial for free air, centrifugal for pressure, and inline for ducts.

Match the motor, enclosure and certification to the environment

Voltage, phase, dust, moisture, temperature, corrosive or explosive atmosphere.

Plan the controls

Speed control, VFD, thermostat, or BMS/PLC integration.

Compare total cost

Not just purchase price.

Understand the Three Numbers That Define Fan Performance

Airflow (CFM)

Airflow is the volume of air a fan moves, measured in cubic feet per minute (CFM) in the US or m³/h in most of the world (1 CFM ≈ 1.7 m³/h). Most catalog CFM figures are measured in free air, with zero resistance. Real installations almost always have some.

Static pressure

Static pressure is the resistance the fan has to overcome, measured in inches of water gauge (in. w.g.) or pascals.

Ducts, bends, filters, screens, dampers, and even a dirty cabinet filter add pressure. A fan with a high free-air CFM but a weak pressure capability will deliver much less airflow once it is connected to a system.

Power and speed

Fan speed (RPM) and motor power determine both performance and cost. This is where the fan affinity laws help:

  • Airflow changes in proportion to speed
  • Pressure changes with the square of speed
  • Power changes with the cube of speed

Reducing fan speed by 20% cuts airflow by 20% but cuts power use by roughly 49%. That relationship is the reason variable speed control pays for itself so often.

Read the fan curve

Every serious fan has a fan curve plotting airflow against pressure. Your system has a system curve (resistance rises with airflow).

The point where the two curves cross is where the fan will actually operate. If a datasheet only lists one CFM number, treat it as a best case.

How to Calculate the Airflow You Need

Method 1: Air changes per hour (ACH)

For general ventilation:

Required CFM = (Room volume in cubic feet × ACH) ÷ 60

Example: a workshop is 40 ft × 30 ft × 12 ft = 14,400 cu ft. At 10 air changes per hour:

14,400 × 10 ÷ 60 = 2,400 CFM

Typical starting points (always verify against local codes and your safety assessment):

SpaceTypical ACH
Warehouse / storage2 to 6
General workshop6 to 10
Welding or paint areas10 to 20 or more (code driven)
Battery rooms, chemical storageSet by code and hazard analysis
Commercial kitchens15 to 30

Method 2: Heat removal

For rooms with heat-producing equipment (compressors, drives, transformers):

CFM = (Heat load in watts × 3.16) ÷ ΔT in °F

where ΔT is the allowed temperature rise between supply air and exhaust air. This is a standard sensible heat approximation at sea level.

Example: 3,000 W of heat with an allowed 15 °F rise needs about 3,000 × 3.16 ÷ 15 = 632 CFM.

Method 3: Enclosure and panel cooling

For control cabinets, use the same heat formula with the internal heat dissipation of drives, power supplies, and PLC racks, then add a safety margin of 20 to 30% for filter loading.

Method 4: Spot cooling and drying

For cooling people or drying floors, you care about air velocity at the target (measured in feet per minute) more than total room CFM. A high-velocity fan aimed correctly beats a bigger fan that is placed poorly.

Industrial Fan Types and When to Use Each

Industrial fans split into two physical families:

  • Axial fans move air parallel to the shaft. High flow, low to moderate pressure. Used for general circulation, wall exhaust, and enclosures.
  • Centrifugal (radial) fans and blowers throw air outward and turn it 90 degrees. Lower flow for the same size, but much higher pressure. Used for ducted systems, drying, and filtration.

Below are the main types, with a recommended product for each.

High-Velocity Floor and Wall-Mount Fans

Best for

Garages, workshops, gyms, light manufacturing, drying wet floors, directed spot cooling.

These are compact axial fans with metal blades and a pivoting head, designed to throw a concentrated stream of air.

Many convert between floor and wall mounting, which saves floor space in busy areas. Look for a steel guard that meets OSHA guarding expectations, a grounded cord, and rubber feet.

Recommended product

Lasko 20″ Max Performance High Velocity Floor Fan, Model 2264QM

  • 20-inch metal blades, 3 speeds, pivoting head
  • QuickMount bracket for floor or wall use
  • Published at roughly 2,750 CFM

Why it works

Strong value for light-duty spot cooling and floor drying. It is not a continuous-duty, three-shift fan, so for 24/7 environments, step up to a pedestal or drum fan with a larger motor.

Check it on Amazon: Lasko 2264QM 20″ High Velocity Fan

Pedestal Fans (Oscillating)

Best for

Gyms, warehouses, assembly lines, event spaces, anywhere you want broad coverage of a work area at head height.

Pedestal fans combine a large-diameter blade (24 to 30 inches) with an adjustable stand and often an oscillating head.

Larger diameter means more air at a lower speed and lower noise than a small high-speed fan moving the same air.

Recommended product

Air King 9135 30″ 1/4 HP Oscillating Pedestal Fan (industrial grade)

  • 30-inch blade, 1/4 HP totally enclosed, permanently lubricated motor
  • Industrial grade construction, ETL listed, OSHA-compliant guard per manufacturer
  • Alternate: the HiCFM 30″ heavy duty oscillating pedestal fan (1/3 HP, advertised at around 8,300 CFM)

Why it works

The totally enclosed motor and ball bearings tolerate dusty environments, and oscillation reduces dead zones.

Check it on Amazon

Air King 9135 30″ Industrial Oscillating Pedestal Fan | HiCFM 30″ Heavy Duty Pedestal Fan

Drum (Barrel) Fans

Best for

Large workshops, greenhouses, loading docks, agricultural buildings, construction sites, long-throw air movement.

A drum fan puts the blade inside a cylindrical housing. The housing tames the airflow into a tighter, longer stream and protects people from the blades.

Drum fans typically use more powerful motors and are built for harder duty cycles than consumer floor fans.

Recommended product

Hurricane Pro Heavy Duty Adjustable Tilt Drum Fan (24″ or 30″)

  • All-metal housing, aluminum blades, 3 speeds, adjustable tilt
  • Published figures of about 7,195 CFM (24″) and 9,295 CFM (30″) at 850 RPM

Why it works: Excellent for moving large volumes of air in open buildings. Choose 30″ or larger for big bays; choose 24″ for tighter work cells.

Check it on Amazon: Hurricane Pro Heavy Duty Adjustable Tilt Drum Fan

Air Movers and Centrifugal Blowers (Carpet Dryers, Confined Spaces)

Best for

Drying floors and structures after water damage, spot ventilation, moving air through short flexible ducts, confined-space ventilation support.

Air movers are compact centrifugal-style blowers that generate high velocity across the floor or through a duct. They are stackable, portable and have rugged rotomolded housings.

Recommended product

XPOWER P-230AT Pro Air Mover (1/3 HP)

  • Multi-position housing (floor, angled, ducted)
  • Rugged molded housing, built-in outlets on many models for daisy chaining

Why it works

It delivers pressure that an open axial fan cannot, so it works with short duct runs and gives focused airflow.

Safety note

A portable blower is not a substitute for a confined-space entry program. If workers will enter a tank, vessel or pit, ventilation must be paired with continuous atmospheric monitoring and a proper permit system.

Check it on Amazon: XPOWER P-230AT Air Mover

Inline Duct Fans

Best for

Exhausting fumes or heat from a room through ducting, supplying fresh air, ventilating small enclosures, battery or equipment rooms (where code permits non-hazardous fans).

An inline fan sits in the duct run. Mixed-flow designs balance pressure and flow, which suits real duct systems with bends and filters.

Because they handle static pressure far better than an open wall fan, they are the right choice whenever ducting is involved.

Recommended product

AC Infinity CLOUDLINE series inline duct fan (EC motor with speed controller)

  • EC motor with variable speed control and a temperature/humidity-capable controller on the Cloudline T models
  • Available in 4, 6, 8, 10 and 12-inch duct sizes

Value alternative

VIVOSUN inline duct fan (6″ or 8″)

  • Lower purchase price, basic speed controller

Why it works

Speed control lets you tune airflow instead of oversizing and throttling with a damper. Match the duct diameter to the CFM you calculated, and keep duct runs short with gentle bends.

Check it on Amazon: AC Infinity CLOUDLINE Inline Duct Fan | VIVOSUN Inline Duct Fan

Control Panel and Enclosure Cooling Fans

Best for

PLC cabinets, VFD enclosures, motor control centers, junction boxes, power supply cabinets, server and network racks in plants.

Heat is the silent killer of drives, power supplies and PLC I/O. As a rule of thumb, electronic component life shortens substantially with sustained high temperature, so enclosure cooling is a reliability decision, not a comfort one.

Cabinet fans are small axial or blower fans, in AC or DC versions, usually with a filter on the intake.

What to look for:

  • Voltage match: 24 VDC is convenient in control panels; 120/230 VAC fans are common for larger enclosures.
  • Ball bearings for long life at high temperature
  • Filtered intake and an exhaust vent positioned high on the cabinet
  • Ingress protection: a fan with a filter does not make the enclosure NEMA 4X or IP66. If you need sealed enclosures, look at heat exchangers or air conditioners instead.

Recommended product (DC cabinet cooling)

Noctua NF-A12x25 PWM 120 mm fan

  • Premium 12 V DC axial fan, high static pressure for its size, long rated life
  • Needs a 12 V supply (use a DC/DC converter from your 24 V rail)

Recommended product (AC cabinet cooling)

AC Infinity AXIAL series or a 120 V 120 mm AC axial fan

  • Direct 120 V operation, suitable for larger cabinets without a DC supply

Why it works

Both give strong airflow in a small footprint. Check your enclosure’s heat load, add a thermostat, and monitor temperature as an alarm input in your PLC.

Check it on Amazon: Noctua NF-A12x25 PWM | AC Infinity AXIAL 120 mm AC fan

Explosion-Proof and Hazardous-Location Fans

Best for

Paint booths, chemical storage, fuel handling, battery charging rooms with hydrogen risk, solvent areas, anywhere a classified hazardous area exists.

This is the one category where you should not buy based on price or a consumer marketplace listing.

A fan used in a classified area must be certified for that area’s classification (for example NEC Class I Division 1 or 2, Group, and temperature class in North America, or ATEX/IECEx zone ratings elsewhere). A general-purpose fan has an ignition source: brushes, switches, a hot motor surface, or a blade that can spark.

What to do:

  • Get the area classification from your safety engineer or hazardous-area drawing.
  • Specify a fan with a matching certified motor and non-sparking blade and housing.
  • Buy through an industrial distributor that supplies certificates and documentation.

Amazon note

Certified explosion-proof fans are generally sold through industrial suppliers rather than Amazon, and I do not recommend buying a safety-critical certified product from a general marketplace listing without verifying the certification label and documentation.

If you do browse, search for the certification, not just the keyword: explosion proof fan Class I Division 1

HVLS (High-Volume Low-Speed) Ceiling Fans

Best for

Warehouses, distribution centers, gyms, hangars, large agricultural buildings with 20+ ft ceilings.

HVLS fans move huge volumes of air at low speed, giving a gentle breeze across a very large footprint and helping to destratify warm air near the ceiling.

They are a facility-level investment: structural mounting, VFD or controller, and installation by qualified technicians.

Motor, Voltage and Drive Considerations

Voltage and phase

Small fans run on single-phase 120 V (North America) or 230 V. Larger industrial fans use three-phase 208, 230, 460 or 575 V. Verify what your facility has before you buy.

Motor type

  • PSC (permanent split capacitor): common, reliable, modest efficiency, limited speed range.
  • Three-phase induction: the workhorse for larger fans, ideal with a VFD.
  • EC (electronically commutated): high efficiency and built-in speed control, and common in modern inline and cabinet fans.
  • DC brushless: compact fans for panels and enclosures.

Enclosure and cooling

TEFC (totally enclosed fan cooled) motors suit dusty environments. Open drip-proof motors are only for clean, dry areas.

Duty rating

A fan that runs 24/7 needs a continuous-duty motor and quality bearings. Consumer-grade fans are not rated for that.

Thermal protection

Look for built-in thermal overload protection on motors.

Bearings

Ball bearings tolerate heat and heavy duty better than sleeve bearings.

Environment, Enclosure and Materials

Dust and debris

Choose enclosed motors and consider guards with finer mesh. Accumulated dust unbalances blades and overheats motors.

Moisture and washdown

Look for IP/NEMA ratings that match the exposure. Food plants may need stainless steel and washdown-rated motors.

High temperature

Check the motor’s maximum ambient temperature and the insulation class, especially near ovens, furnaces and rooftops.

Corrosive atmospheres

Chemical plants, coastal sites and wastewater facilities need coated, stainless, or fiberglass-reinforced plastic (FRP) fans.

Altitude

Air is thinner at altitude, so the same fan delivers less mass flow and its motor cools less effectively.

Outdoor use

Confirm the fan’s weather rating, UV resistance and cord type.

Hazardous Areas and Safety Compliance

Fan selection is a safety decision in several situations:

Guarding

Rotating blades must be guarded. In the US, OSHA’s machine guarding rules require guards that prevent contact with moving parts; guard openings are commonly specified as 1/2 inch or smaller for fans within reach (confirm the current requirements with your safety team).

Listings

Look for UL, ETL or CSA listings for electrical safety, and CE/UKCA marks in other markets.

Hazardous locations

See the explosion-proof discussion above. A ventilation fan is not a gas detector, and a gas detector is not a ventilation system.

Where flammable or toxic gases can accumulate, ventilation and fixed gas detection should work together, for example with a detector alarm that starts or ramps up exhaust fans.

For more on how detection is designed in industrial plants, read our sister site Safeguard Sense.

Confined spaces

Portable blowers support confined-space entry but never replace atmospheric testing, permits and rescue planning.

Fire

In some buildings, exhaust fans must integrate with the fire alarm system (shutdown or smoke-control operation). Check local fire code.

    Noise, Vibration and Placement

    Noise

    Larger diameter fans at lower RPM are quieter than small fans at high RPM for the same airflow. Look for dBA ratings where available.

    Workers exposed to high noise levels over a shift may require hearing protection, so noise is also an occupational health issue.

    Vibration

    Blade imbalance from dust or damage causes bearing wear. Use vibration-isolating mounts for fixed installations.

    Placement

    Don’t place a fan where it recirculates the same hot air. For exhaust, put the fan at the high point; for supply, make sure make-up air has a clear, clean path.

    A building that has exhaust fans but no make-up air creates negative pressure, which reduces fan performance and can pull in dust or backdraft combustion appliances.

    Airflow direction

    Push-pull layouts (supply on one side, exhaust on the opposite side) clear a space more effectively than a single fan.

    Controls and Automation

    Since this is a controls and automation site, this is where the upgrade path matters.

    Basic controls

    Multi-speed switches, thermostats, timers and humidistats.

    Variable frequency drives (VFDs)

    For three-phase motors, a VFD gives soft starting, variable airflow and big energy savings thanks to the affinity laws. If you work with VFDs, see our guide on VFD fault codes and how to fix them .

    EC and PWM fans

    Many EC fans accept a 0-10 V or 4-20 mA analog signal, or a PWM signal, so a PLC or controller can modulate speed directly.

    Some also support Modbus RTU. Compare Modbus RTU vs TCP when planning network integration.

    BMS integration

    In commercial and industrial buildings, fans are often controlled from a BMS using BACnet or Modbus points: run command, speed reference, status feedback, and fault alarm. See our BACnet and BMS guides.

    Monitoring

    Add airflow or differential-pressure sensors on critical fans so you can detect belt failure, blocked filters or a stopped motor, rather than finding out when equipment overheats.

    Energy Use and Total Cost of Ownership

    Purchase price is often the smallest part of what a fan costs over its life. For a fan that runs many hours a year:

    Annual energy cost = kW × hours per year × electricity rate

    Example: a 0.75 kW fan running 6,000 hours a year at $0.12/kWh costs 0.75 × 6,000 × 0.12 = $540 per year.

    If a higher-efficiency EC fan or VFD reduces average power by 30%, you save roughly $160 a year on a single fan, and the savings multiply across a facility.

    Also consider:

    • Maintenance (bearing lubrication, belt replacement, cleaning)
    • Expected service life and warranty
    • Spare parts availability
    • Downtime cost if a critical fan fails

    Comparison Table: Industrial Fan Types at a Glance

    Fan typeBest forPressure capabilityTypical airflowNoiseNotes
    High-velocity floor/wallSpot cooling, dryingLow2,000 to 5,000 CFMModerate to loudBudget friendly, not for 24/7 duty
    Pedestal (oscillating)Wide area coolingLow4,000 to 9,000 CFMModerateGood coverage at head height
    Drum / barrelLarge open baysLow to moderate7,000 to 18,000 CFMModerateLong throw, rugged
    Air mover / blowerDrying, short ductsModerate to highVariesLoudPortable, stackable
    Inline duct fanDucted exhaust/supplyModerate100 to 2,000 CFMLow to moderateNeeds proper duct sizing
    Panel / enclosure fanCabinet coolingLow to moderate10 to 300 CFMLowUse filters, monitor temperature
    Explosion-proofClassified areasVariesVariesVariesMust carry correct certification
    HVLS ceilingLarge buildingsVery lowVery large coverageVery lowInstalled by specialists

    Industrial Fan Selection Checklist

    Before you buy, make sure you can answer every one of these:

    • What is the purpose: cooling people, ventilating air, exhausting contaminants, cooling equipment, drying?
    • What airflow (CFM) is required, and how did I calculate it?
    • Is there ducting, filtering or other static pressure to overcome?
    • Which fan type fits (axial, centrifugal, inline, drum, panel)?
    • What voltage, phase and frequency does the site provide?
    • Is the duty continuous or intermittent?
    • What are the dust, moisture, temperature and corrosion conditions?
    • Is the area classified as hazardous, and does the fan carry the right certification?
    • Is the guarding compliant with local safety rules?
    • What noise level is acceptable at the work position?
    • How will it be controlled (switch, thermostat, VFD, BMS/PLC)?
    • What is the total cost of ownership over the expected life?

    Top Picks Summary

    NeedOur pickWhere to check it
    Garage / workshop spot coolingLasko 20″ 2264QM High Velocity FanAmazon
    Warehouse / gym air circulationAir King 9135 30″ Oscillating Pedestal FanAmazon
    Large bays, long throwHurricane Pro Heavy Duty Drum FanAmazon
    Drying / high velocity blowingXPOWER P-230AT Air MoverAmazon
    Ducted exhaust / supplyAC Infinity CLOUDLINE Inline FanAmazon
    Control panel cooling (DC)Noctua NF-A12x25 PWMAmazon
    Control panel cooling (AC)AC Infinity AXIAL 120 mm AC FanAmazon
    Hazardous areasCertified explosion-proof fan from an industrial supplierSpecify by classification, not by price

    Frequently Asked Questions

    What is the difference between an axial fan and a centrifugal fan?

    An axial fan moves air in a straight line along the shaft and is best for high airflow at low resistance, such as general circulation.

    A centrifugal fan throws air outward and turns it, creating higher pressure for ducted systems, filters and drying applications.

    How many CFM do I need for an industrial fan?

    Multiply room volume in cubic feet by the air changes per hour you need and divide by 60.

    For heat removal, divide the heat load in watts times 3.16 by the allowed temperature rise in °F. Then add a margin for filters, ducting and dirt buildup.

    Is a drum fan better than a pedestal fan?

    It depends on the space. Drum fans produce a tighter, longer-reaching airflow and are usually more rugged, so they suit large open areas.

    Pedestal fans spread air over a wider area at head height, which suits gyms, assembly floors and offices.

    Can I use a regular fan in a hazardous location?

    No. A standard fan can create sparks or hot surfaces that ignite flammable gases, vapors or dust.

    In classified areas, use a fan certified for the area classification (such as Class I Division 1/2 or ATEX/IECEx zone ratings), and verify the certification documents.

    How do I cool a control panel with a fan?

    Calculate the heat load of the components, determine the allowed internal temperature rise, and size the fan using the heat-removal formula with a margin for filter loading.

    Use a filtered intake, a high exhaust vent, a thermostat, and consider wiring a temperature input to your PLC for alarms.

    Should I use a VFD on my industrial fan?

    For three-phase motors on fans with variable load, usually yes. Because fan power changes with the cube of speed, even a modest speed reduction produces large energy savings, and you also get soft starting and better process control.

    How loud are industrial fans?

    Noise varies widely. Large-diameter fans running at lower speeds are quieter than small, high-speed fans moving the same air.

    Look for dBA ratings, and if the fan will run next to workers, check your local occupational noise requirements.

    How often should industrial fans be maintained?

    Inspect guards, mounts and blades regularly, clean dust buildup, check for vibration or unusual noise, and lubricate bearings according to the manufacturer’s schedule.

    Cabinet fan filters often need monthly or quarterly cleaning depending on the environment.

    Final Thoughts

    The right industrial fan is the one that matches the job, not the one with the biggest CFM number.

    Start with the application, calculate the airflow, check static pressure, pick the fan type that suits it, then verify motor, environment, safety rating, noise and controls.

    In hazardous areas, treat the fan as part of your safety system and specify it properly.

    If you are building automation around your ventilation, from VFD speed control to BMS integration, keep exploring the guides on controlcircuitry.com.

    Disclosure

    This article contains affiliate links. If you buy through them, controlcircuitry.com may earn a commission at no extra cost to you.

    This article is general guidance and does not replace a site-specific engineering or safety assessment.

    IEC 61131-10 Explained: The PLC XML Exchange Format Engineers Need to Know

    If you’ve spent any time programming PLCs across different vendor platforms, you already know the pain: a ladder logic program built in one environment doesn’t just drop into another.

    Every vendor’s IDE stores projects in its own proprietary format, which means switching tools or even just archiving a project for the long term often means starting from scratch.

    IEC 61131-10 exists to fix that. It’s the least talked-about part of the IEC 61131 series, but for engineers dealing with legacy migrations, multi-vendor plants, or long asset life cycles, it’s one of the more practically useful ones.

    What Is IEC 61131-10?

    IEC 61131-10, titled “Programmable controllers Part 10: PLC open XML exchange format,” defines a standardized XML-based format for exporting and importing IEC 61131-3 projects.

    Rather than defining a new programming language, it defines how an existing IEC 61131-3 project its configuration elements, data types, and Program Organization Units (POUs) can be packaged into a vendor-neutral file that another compliant tool can read back in.

    It covers all five IEC 61131-3 languages

    – Instruction List (IL): textual

    – Structured Text (ST): textual

    – Ladder Diagram (LD): graphical

    – Function Block Diagram (FBD): graphical

    – Sequential Function Chart (SFC)

    Critically, the format doesn’t just capture the logic itself. It also preserves graphical layout information where function blocks sit on the canvas, how they’re wired together, sizing, and positioning so an imported FBD or LD program doesn’t come back as an unreadable mess.

    Where It Came From: PLCopen and TC6

    IEC 61131-10 didn’t start life inside the IEC. It began as PLCopen XML, developed by PLCopen’s Technical Committee 6 (TC6).

    PLCopen an independent vendor association focused on IEC 61131-3 created the XML schema specifically to let development environments, simulators, debuggers, version control systems, and documentation tools talk to each other around a shared project format.

    In 2014, PLCopen handed its intellectual property on the schema over to the IEC through Germany’s DKE.

    That handoff triggered formal standardization work, which had to account for the significant object-oriented extensions introduced in the 3rd edition of IEC 61131-3 (2013).

    The result, published in April 2019, is IEC 61131-10 Edition 1.0 effectively PLCopen XML formalized as an international standard.

    Why It Matters for Automation Engineers

    Reduced vendor lock-in

    A PLC project isn’t just logic, it’s years of tuning, commented rungs, tested edge cases, and institutional knowledge.

    Without a portable format, that investment is tied to whichever brand of PADT (Programming and Debugging Tool) it was built in.

    IEC 61131-10 gives engineering teams a documented path to move a project between compliant tools instead of re-engineering it from a printout.

    Life cycle management

    Plants run equipment for decades, but software tools get discontinued, acquired, or deprecated long before the hardware does.

    An XML export in a standardized format is a more durable artifact for long-term archiving, redesign, and device replacement projects than a binary project file tied to a specific software version.

    Interoperability between supporting tools

    IEC 61131-3 only standardizes the programming languages, it says nothing about simulation, version control, or documentation tooling.

    IEC 61131-10 fills that gap by giving third-party tools (Git-based version control, static analysis tools, documentation generators) a common format to parse, instead of requiring vendor-specific plugins for each PLC brand.

    Easier multi-vendor audits and reviews

    On projects involving more than one PLC brand, common in retrofits and expansions, having a shared exchange format makes it far easier for a reviewing engineer to inspect logic across platforms without owning a license for every vendor’s software.

    What IEC 61131-10 Does Not Do

    This is where a lot of confusion comes in, so it’s worth being precise

    It does not guarantee 1:1 functional compatibility

    The standard explicitly does not define a required functional subset that every PADT must support.

    If Vendor A’s tool uses an extended instruction set that Vendor B’s tool doesn’t implement, that logic may not translate cleanly on import, you may need to manually adjust and retest the program.

    It is not a new programming language

    It’s a container format for projects already written in the five IEC 61131-3 languages.

    It doesn’t replace vendor project files

    Most PADTs still use their own native project format day-to-day. The XML export is an interchange layer, not a replacement for the tool’s internal storage.

    In practice, this means IEC 61131-10 gets you most of the way there on a migration or archive, but it’s not a substitute for validation testing after import.

    IEC 61131-10 vs. Related Standards

    IEC 61131-3

    Defines the PLC programming languages (LD, FBD, ST, IL, SFC).

    IEC 61131-10

    Defines the XML exchange format for moving IEC 61131-3 projects between tools.

    IEC 62443

    Industrial cybersecurity, unrelated in scope, sometimes confused due to numbering proximity.

    PLCopen XML

    The pre-standardization name for what is now formally IEC 61131-10.

    Practical Use Cases

    Tool migration

    Moving a legacy project off a discontinued PADT into a currently supported platform.

    Version control integration

    Exporting logic as XML so it can be diffed and tracked in Git alongside the rest of a project’s codebase, rather than relying on a vendor’s built-in (and often limited) versioning.

    Documentation automation

    Feeding the XML export into scripts or reporting tools that auto-generate I/O lists, cross-reference tables, or logic documentation.

    Third-party static analysis

    Running standardized code-quality or safety checks across logic exported from different vendor tools.

    FAQ

    Is IEC 61131-10 the same as PLCopen XML?

    Yes. IEC 61131-10 is the formal IEC standardization of what was originally developed and maintained as PLCopen XML by PLCopen’s TC6 working group.

    Does every PLC vendor support IEC 61131-10?

    Support varies by vendor and by tool version. Even among tools that support export/import, the specific instructions and extensions supported can differ, so imported logic should always be verified before deployment.

    When was IEC 61131-10 published?

    Edition 1.0 was published in April 2019, following work that began after PLCopen transferred its schema IP to the IEC in 2014.

    Can IEC 61131-10 export graphical logic like Ladder Diagram, not just text-based code?

    Yes. The format captures graphical layout data, block position, size, and wiring, in addition to the underlying logic, for both Ladder Diagram and Function Block Diagram.

    Does IEC 61131-10 guarantee my program will run identically after import into another tool?

    No. The standard defines the exchange format itself, not a required functional subset across all tools, so behavior after import should be tested rather than assumed.

    The Bottom Line

    IEC 61131-10 won’t eliminate the practical friction of working across PLC vendors, but it gives engineers and integrators a standardized, documented way to move IEC 61131-3 projects between tools instead of relying on manual re-entry or vendor-specific converters.

    For anyone managing long-lived automation assets or multi-vendor plants, understanding what this standard does, and its limits, is worth the half hour it takes to read this page.

    IQOQ Explained: IQ/OQ Guide for Automation & Control Systems

    If you work anywhere near pharmaceutical manufacturing, biotech, food production, or any regulated industrial environment, you’ve run into the term IQOQ.

    It shows up on equipment purchase orders, in validation master plans, and in emails from quality assurance asking, “Where’s the IQOQ documentation for this skid?”

    For control systems engineers coming from a general industrial automation background, IQOQ can feel like a different language layered on top of familiar work.

    Commissioning, testing, and documenting a system you already know how to build. That’s not far off.

    IQOQ is essentially rigorous, auditable commissioning, done in a specific order, with paper trails that regulators can trust.

    This guide breaks down what IQOQ means, how it applies to PLCs, HMIs, and building/process control systems, and where engineers commonly trip up.

    What Does IQOQ Stand For?

    IQOQ is shorthand for Installation Qualification (IQ) and Operational Qualification (OQ), two phases in the equipment and system validation lifecycle used in regulated industries such as pharmaceuticals, medical devices, food and beverage, and biotechnology.

    • Installation Qualification (IQ) confirms that equipment and systems are installed correctly, according to the manufacturer’s specifications and the approved design documentation.
    • Operational Qualification (OQ) confirms that the equipment operates as intended, across its specified operating ranges, once it’s installed.

    Together, IQ and OQ form documented, objective evidence that a piece of equipment a PLC-controlled skid, an HVAC system, a filling line, or a cleanroom air handler was built right and works right before it’s ever used to make or handle a regulated product.

    IQOQ almost always sits inside a broader validation framework that also includes:

    • DQ: Design Qualification: confirms the design meets user requirements before anything is built or installed
    • PQ: Performance Qualification: confirms the system performs consistently under real production conditions, with real product, over time

    So the typical sequence an automation engineer will encounter is DQ → IQ → OQ → PQ, sometimes bundled and referred to loosely as “IQOQ” or “IQ/OQ/PQ” depending on the site’s quality system.

    Why IQOQ Exists

    Regulators, the FDA, EMA, and equivalent bodies, don’t take a manufacturer’s word that a system works.

    They require documented proof. This comes from Good Manufacturing Practice (GMP) requirements and, in the US, guidance from 21 CFR Part 211 for pharmaceutical manufacturing and process validation expectations under the FDA’s process validation guidance.

    For control systems specifically, IQOQ answers two blunt questions an auditor will ask:

    1. Is this system built the way it was supposed to be built?
    2. Does it perform as intended, reliably, across its full operating range?

    If you can’t answer both with signed, dated, reviewed documentation, the system and potentially the product it touches aren’t considered validated, regardless of how well it actually runs on the floor.

    Installation Qualification (IQ): What Gets Checked

    IQ is a physical and documentation-level verification. It happens after installation but before the system is powered up and tested functionally. A typical IQ protocol for a control system or automated skid verifies the following.

    • Equipment identification: correct model, serial numbers, and revision levels match purchase specifications
    • Component verification: PLCs, HMIs, sensors, actuators, VFDs, and I/O modules match the approved bill of materials
    • Installation conditions: wiring, grounding, panel layout, and enclosure ratings meet the design drawings and applicable codes (NEC, NFPA 70, or local equivalents)
    • Utilities and services: power supply specifications, compressed air, network connections, and instrument air match design requirements
    • Software and firmware: Correct PLC program version, HMI application version, and firmware revisions are installed and match the released, version-controlled source
    • Calibration status: instruments (sensors, transmitters, gauges) have current, traceable calibration certificates
    • Drawing accuracy: as-built P&IDs, electrical schematics, and network architecture diagrams match what’s physically installed
    • Documentation package: manuals, spare parts lists, and vendor certificates are on file

    IQ is asking, “Is this exactly what we specified, exactly where and how we specified it?” Nothing is tested for function yet. This step is purely about installed correctness.

    Operational Qualification (OQ): What Gets Checked

    Once IQ is signed off, OQ verifies the system actually functions correctly across its intended operating range.

    For control systems, this phase is where an automation engineer’s normal commissioning instincts map directly onto the qualification protocol. OQ typically covers:

    Functional testing of control logic

    Every interlock, alarm, permissive, and sequence step is tested against the functional specification, including edge cases.

    Alarm and interlock verification

    High/low setpoints, safety interlocks, and critical alarms trigger correctly and at the correct thresholds.

    Operating range testing

    The system is exercised across its full specified range (temperature, pressure, speed, flow), not just at nominal setpoints.

    Failure mode testing

    What happens on power loss, sensor failure, communication loss, or E-stop, and whether the system fails to a safe state.

    User access and security

    Login levels, audit trails, and electronic records comply with requirements like 21 CFR Part 11 where applicable

    Recipe and setpoint verification

    For systems with recipe-driven control, confirming parameters load and execute correctly

    Data integrity checks

    Confirming logged data, alarms, and audit trails are accurate, timestamped, and tamper-evident.

    If IQ confirms “it’s built right,” OQ confirms “it does what it’s supposed to do, every time, across the full range it’s designed for.”

    A system can pass IQ and still fail OQ. For example, wiring and components match the drawings perfectly, but an interlock doesn’t trip at the specified setpoint because of a logic error or a miscalibrated sensor.

    IQOQ vs. PQ: Where the Line Is

    This distinction trips people up constantly, so it’s worth being precise.

    Qualification StageCore QuestionWhen It HappensTypical Test Conditions
    IQ (Installation)Is it installed correctly?Right after installation, before power-up testingStatic visual/documentation checks
    OQ (Operational)Does it function correctly across its range?After IQ passes, before production useDynamic system run empty or with test media, across full operating range
    PQ (Performance)Does it perform consistently in real production?After OQ passes, using real product/processDynamic real product, real production conditions, multiple runs

    OQ tests the system’s capability to maintain setpoints, while PQ assesses whether the batch consistently meets specifications during operation.

    OQ is largely engineering-driven; PQ usually pulls in process and quality teams more heavily.

    A Simplified IQOQ Protocol Structure

    Most IQOQ protocols, regardless of industry, follow a similar document skeleton:

    1. Purpose and scope: what system, what boundaries.
    2. Roles and responsibilities: who executes, who reviews, who approves.
    3. Prerequisites: training completed, documentation available, calibration current.
    4. IQ test cases: numbered, with acceptance criteria and space for actual results.
    5. OQ test cases: numbered, with acceptance criteria, expected results, and actual results.
    6. Deviation log: any failed test case, its root cause, and resolution.
    7. Summary and approval: sign-off from engineering, quality, and often the equipment owner.

    Every test case needs a predefined, objective acceptance criterion written before testing starts. “Alarm triggers at 85°C ± 1°C and displays on HMI within 2 seconds” is a testable criterion. “Alarm works correctly” is not a testable criterion, and an auditor will flag it.

    Common Places Engineers Get Tripped Up on IQ/OQ

    Here are a few recurring issues from the field, especially for engineers new to validated environments.

    Testing before documentation is finalized

    If drawings or the functional specification changes after OQ testing starts, the protocol needs a formal deviation or revision. You can’t just quietly retest and move on.

    Vague acceptance criteria

    Every test step needs a specific, measurable pass/fail condition. “The system should respond appropriately” will get rejected in review.

    Skipping failure mode testing

    It’s tempting to only test the happy path. OQ specifically wants to see what happens when something goes wrong sensor failure, network dropout, power interruption and that the system fails safely.

    Software version mismatches

    The PLC program or HMI application tested during OQ must be the exact version that goes into production.

    Any post-OQ code change, even a minor tweak, typically requires re-qualification of the affected functions.

    Treating IQOQ as a one-time event

    Significant changes to a validated system, a firmware update, a new sensor, or a logic change generally trigger a re-validation assessment, not just a change request in the maintenance log.

    Who’s Involved in IQOQ Execution

    IQOQ isn’t usually a solo effort. A typical execution team includes:

    • Automation/controls engineer: executes functional and logic testing, often writes the OQ test scripts.
    • Quality assurance: reviews and approves protocols and results and ensures compliance with the site’s validation master plan.
    • Equipment vendor/OEM: frequently supports or co-executes IQ, especially for skid-mounted or packaged systems.
    • Metrology/calibration team: provides calibration certificates and may execute instrument-specific checks.
    • Process/production engineering: defines operating ranges and acceptance criteria tied to actual process needs.

    FAQ

    Is IQOQ the same as commissioning?

    No, though they overlap. Commissioning is the general process of getting a system running correctly.

    IQOQ is the formal, documented subset of that work required for regulatory compliance in validated environments.

    You can commission a system without ever generating IQOQ paperwork, but you can’t complete IQOQ without effectively commissioning the system first.

    Does every control system need IQOQ?

    No, IQOQ is required for equipment and systems that touch a regulated product or process in pharmaceutical, biotech, medical device, and certain food/beverage applications.

    A general industrial or building automation system outside a regulated GxP environment typically doesn’t require formal IQOQ, though many companies apply similar rigor voluntarily for critical systems.

    Who writes the IQOQ protocol, engineering or quality?

    It’s usually collaborative. Engineering typically drafts the technical test cases based on design and functional specifications, while quality assurance reviews, standardizes format, and ensures the protocol meets the site’s validation procedures before execution.

    What happens if a test case fails during OQ?

    It gets logged as a deviation, investigated for root cause, corrected, and retested either the specific failed case or, depending on the site’s SOP, the full test sequence. The deviation and resolution become part of the permanent validation record.

    Can IQ and OQ be combined into one document?

    Yes, this practice is common, especially for smaller systems or less complex equipment. Hence the combined term “IQOQ.”

    Larger or higher-risk systems often keep them as separate protocols executed sequentially.

    The Bottom Line

    IQOQ isn’t a separate skill set from good controls engineering. It’s controls engineering with the documentation discipline that regulated industries require.

    If you already write clear functional specifications, test interlocks methodically, and version-control your PLC code, you’re most of the way to IQOQ-ready work.

    The remaining gap is almost always documentation rigor: predefined acceptance criteria, traceable version control, and a paper trail an auditor who’s never met you can follow from design intent to tested result.

    21 CFR Part 11 Explained: What It Means for Industrial Control Systems

    If you work on control systems for a pharmaceutical, biotech, or medical device manufacturer, you’ve probably heard the phrase “the system needs to be Part 11 compliant” tossed around in a project kickoff meeting, usually without much explanation of what that actually means for your PLC program, your HMI, or your historian.

    What is 21 CFR Part 11 about?

    21 CFR Part 11 is the FDA regulation that governs when electronic records and electronic signatures can be treated as equivalent to paper records and handwritten signatures.

    It doesn’t dictate how you build a control system, but it does dictate what your system has to be able to prove about the data it creates, stores, and lets people sign off on.

    This article breaks down what Part 11 actually requires, who it applies to, and, since this is a controls-focused site, what it means in practice for the PLCs, SCADA platforms, and MES/historian layers you’re specifying or programming.

    What Is 21 CFR Part 11?

    21 CFR Part 11 is Title 21, Part 11 of the U.S. Code of Federal Regulations, issued by the FDA in 1997.

    It applies to any organization regulated by the FDA pharmaceutical manufacturers, biologics and biotech companies, medical device makers, and food producers falling under FDA oversight, that chooses to keep records electronically instead of on paper or that uses electronic signatures instead of wet-ink ones.

    The regulation exists because electronic records are trivially easy to alter without leaving a trace, unless the system is specifically designed to prevent that.

    Part 11 sets the baseline controls that make an electronic record trustworthy enough to stand in for a paper one during an FDA inspection or a product liability dispute.

    It’s split into two main subparts.

    • Subpart B covers electronic records, creation, modification, maintenance, retention, and retrieval.
    • Subpart C covers electronic signatures, how a system verifies who signed something and binds that signature to the specific record.

    Who Does Part 11 Apply To?

    Part 11 applies to FDA-regulated companies and, by extension, to their suppliers and integrators. In practice, that means.

    • Pharmaceutical and biopharmaceutical manufacturers (batch records, cleaning validation, environmental monitoring).
    • Medical device manufacturers (device history records, quality records).
    • Biotech and cell/gene therapy producers.
    • Food and beverage companies subject to FDA rules (less commonly, but it does happen).
    • The systems integrators, OEM machine builders, and controls engineers who build or program equipment for the above are also involved.

    If you’re building a skid, a filling line, or a bioreactor control panel that will run under a GxP quality system, Part 11 compliance is your customer’s problem, but it becomes your problem the moment they hand you a validation requirements document.

    The Core Requirements, in Plain Language

    Part 11 is written in regulatory language, but the requirements translate into a fairly specific set of engineering features. Here’s what a compliant system actually has to do.

    Audit Trails

    Every creation, modification, or deletion of a regulated electronic record has to be captured automatically in a secure, computer-generated, time-stamped audit trail.

    The audit trail must record who made the change, what was changed, and when, and, critically, it must not overwrite or obscure the previous data.

    You need the old value, the new value, and the reason for the change if the system prompts for one.

    For a controls engineer, this means your historian, MES, or batch execution system needs audit trail functionality built in and enabled, not bolted on after the fact.

    Most modern SCADA and historian platforms (Ignition,