What test standards mean by intended performance

An EUT can remain powered throughout an immunity test and still fail. Equally, a visible disturbance does not always mean non-compliance.

The deciding factor is often whether the equipment maintained its intended performance, including any degradation permitted by the applicable product standard and declared by the manufacturer.

What intended performance means in EMC immunity testing

Intended performance describes the functions and performance characteristics that equipment is expected to provide when used as intended. During electromagnetic immunity testing, those characteristics form the reference against which the equipment under test, or EUT, is assessed.

This is not simply a question of whether the product resets, crashes or suffers permanent damage. The assessment may need to cover measurement accuracy, communication integrity, control stability, audio quality, display behaviour, data retention, response time, safety-related functions and many other product-specific characteristics.

The applicable product or product-family standard usually establishes the immunity phenomena, test levels, port applicability and performance criteria. Basic immunity standards in the IEC 61000-4-x series describe methods for applying phenomena such as electrostatic discharge, radiated RF fields, electrical fast transients, surge and conducted RF disturbances. They do not, by themselves, define every acceptable functional outcome for every product.

That distinction causes problems in laboratories. Applying the disturbance is often straightforward compared with deciding what the EUT must continue doing while exposed to it.

Intended use sets the engineering context

Intended performance cannot be separated from intended use. A brief interruption that is acceptable for a consumer information display could be unacceptable in industrial control equipment if it causes loss of process control. A momentary audible artefact may be permitted in one audio application but not where speech intelligibility is part of the declared function.

The engineering team therefore needs to identify the use case before writing the test plan. Questions should include:

• Which functions are available to the user?
• Which functions must operate during each immunity test?
• What performance limits are stated in the specification, instructions or technical documentation?
• Which operating modes represent the highest immunity risk?
• Can the operator recover the equipment, or must recovery be automatic?
• Would data loss, output movement or a communication error create an unacceptable condition?

If these points are left until the test session, pass or fail decisions become subjective. Retrospective acceptance criteria are particularly difficult to defend when a test result is being used in a technical file or reviewed by a customer.

Functional criteria and permitted degradation

Many immunity standards use performance criteria commonly described as criteria A, B and C, although the exact wording, applicability and permitted behaviour must be checked in the current product standard. The broad engineering distinction is whether performance must remain within defined limits during the test, whether temporary degradation is permitted with automatic recovery, or whether temporary loss of function may be accepted subject to a defined recovery mechanism.

Those categories are not a licence to accept any disturbance. The product standard may narrow the permitted degradation, and the manufacturer still needs objective monitoring parameters. A statement such as “the unit shall work normally” is too vague for a repeatable assessment.

Performance criterion A usually requires continuous operation

Where criterion A applies, the EUT is generally expected to continue operating as intended during and after the test. Some degradation may be permitted if it remains within limits stated by the manufacturer or specified by the relevant standard.

Consider an illustrative temperature measurement system. Merely confirming that its display remains illuminated would be inadequate. The test plan might need to monitor indicated temperature, analogue output, alarm state and digital communications. If RF exposure produces a large but transient measurement error, the equipment may have failed its intended performance even though it never rebooted.

Quantification matters. Measurement uncertainty, normal process variation and monitoring-system accuracy must be considered when setting the acceptance window. Otherwise, normal drift may be mistaken for an immunity response, or a genuine susceptibility may disappear inside an excessively broad tolerance.

Criterion B does not mean faults can be ignored

Criterion B commonly permits temporary degradation or loss of function during the disturbance, provided that the EUT recovers automatically after the test and does not suffer an impermissible change of state or loss of stored data. The applicable standard may impose more specific conditions.

An Ethernet-connected controller, for example, might experience reduced throughput during a transient test. Whether that is acceptable depends on the declared function and product requirements. A dropped packet that is automatically retried may be acceptable in one use case. Loss of a control command, latched output or stored configuration may not be.

Recovery also needs a time definition. “Recovered after testing” could mean milliseconds, several minutes or only after a watchdog timeout. Recording the recovery period makes the result reproducible and exposes behaviour that could be operationally unacceptable.

Criterion C requires controlled interpretation

Criterion C may permit temporary loss of function where recovery requires operator intervention or follows a defined reset sequence. It does not normally justify permanent damage, corrupted firmware or an unsafe state. Nor should it be assumed to apply unless the relevant product standard assigns it to the test in question.

A power cycle may restore a prototype after an electrostatic discharge event, but that fact alone does not establish a pass. The team must check whether manual intervention is permitted, whether stored data remained intact and whether the equipment entered a hazardous or unintended state before recovery.

Turning intended performance into a testable requirement

A useful acceptance criterion names the function, operating mode, monitored quantity, permitted deviation, recovery behaviour and prohibited outcomes. It should be written before exposure begins.

For a variable-speed motor drive system, for example, intended performance could involve commanded speed, actual speed, torque behaviour, status communications and fault handling. IEC 61800-3 may be relevant depending on product scope, but the current edition, installation environment and product configuration need checking. Monitoring only whether the drive remains energised would miss disturbances that alter motor speed or generate an unintended trip.

Good monitoring is electrically and electromagnetically unobtrusive. Long unfiltered oscilloscope leads, poorly screened data cables or additional protective-earth connections can create coupling paths that do not exist in normal service. The monitoring arrangement can then either provoke a false failure or shunt RF energy away from the EUT.

Where optical isolation, fibre communications or screened feedthroughs are used, their influence should still be assessed and documented. Cameras are useful for displays and indicator states, but video alone rarely proves analogue accuracy, packet integrity or timing performance.

Typical scenario

Consider an illustrative industrial controller undergoing conducted RF immunity testing. Its mains input, analogue sensor ports and Ethernet interface are active, while a simulated process exercises the control algorithm. The applicable product standard calls up IEC 61000-4-6 for relevant ports and defines the required performance criterion.

A suitable coupling method must be selected for each applicable cable. A coupling and decoupling network, or CDN, may be specified for a particular port, while another method may be required where a suitable CDN cannot be used. A CDN and a bulk current injection probe are not automatically interchangeable. The method, common-mode impedance, cable type and product-standard requirements determine the correct arrangement.

EMC Hire can support this work with suitable conducted immunity testing equipment, practical setup guidance and access to coupling and decoupling networks. Engineers planning a complete setup can also review the available conducted immunity system information.

The controller remains powered during the sweep, but its analogue input shifts enough to command an incorrect actuator position. A simple alive-or-dead assessment would record a pass. A test plan based on intended performance would identify the control deviation and compare it with the permitted functional limit.

Early investigation gives the design team room to distinguish enclosure coupling from cable-borne susceptibility, inspect filtering and bonding, and repeat specific frequencies after modification. Waiting until formal testing can turn a filter change into a PCB revision, enclosure change or installation-instruction rewrite.

EMC Hire can assist with equipment hire, pre-compliance engineering, on-site testing, formal compliance testing where appropriate and test-facility access. Pre-compliance data does not prove compliance, but calibrated measurements and recorded operating behaviour can improve confidence before a formal programme and support self-certification evidence where legally and technically applicable.

Documentation that supports a defensible decision

The test record should capture more than the generator level and a pass or fail box. Record the EUT hardware and firmware revisions, support equipment, cable types and positions, active ports, operating modes, monitoring method, acceptance limits, observed degradation and recovery process.

Photographs help, particularly where cable layout affects coupling. Screen captures, communication logs and analogue traces can show whether a disturbance was repeatable or coincidental. A clear chronology also distinguishes behaviour occurring during exposure from behaviour found several minutes later.

EMC Hire uses test equipment with calibration traceable through an appropriate ISO/IEC 17025 accredited calibration provider where calibration is relevant to the measurement. Suitable traceable calibration supports measurement accuracy, repeatability and comparison between development and formal testing. It does not remove the need to control setup geometry, coupling devices, software states or monitoring uncertainty.

For CE or UKCA self-certification routes, where applicable, the manufacturer or responsible economic operator remains responsible for confirming the legislation, standards, conformity assessment route and documentation requirements. Robust immunity evidence may support the technical file, EMC risk assessment, Declaration of Conformity, mitigation records and customer review, but testing alone does not complete every conformity obligation.

The EMC standards guidance provides further context on the relationship between basic methods and product requirements. Engineers should verify the latest active edition, product scope, test levels, frequency ranges, equipment configuration, performance criteria and documentation provisions through authorised sources such as the International Electrotechnical Commission and BSI standards services.

When to Hire EMC Equipment

Hiring is technically sensible when immunity demand is short-term, irregular or tied to a defined development window. A conducted immunity system, RF amplifier, CDN set or monitoring arrangement must suit the method and required range. Buying an unsuitable system because it happens to cover one immediate test can leave a business with equipment that does not support the next product programme.

Rental avoids committing capital before the required architecture is understood. It also reduces long-term storage, servicing and calibration overheads, while allowing engineering teams to scale capability during project peaks.

Equipment selection should start with the product standard and test plan, not an isolated generator specification. Required frequency coverage, test level, modulation, amplifier headroom, forward-power monitoring, coupling method, port type and EUT current all affect suitability. A CDN with the wrong connector or current rating can delay a test just as effectively as an underpowered amplifier.

For repeated or strategically important testing, ownership may still make sense. A defined hire period can first establish actual utilisation and expose practical requirements before capital expenditure is approved.

Common EMC Testing Mistakes to Avoid

Using power status as the only performance monitor

A powered indicator says little about data integrity, measurement accuracy or output state. This approach creates false confidence and can miss susceptibility that directly affects the intended function.

Writing acceptance criteria after observing a fault

Changing the permitted degradation after testing makes the result difficult to defend. Functional criteria should be linked to the declared use case and agreed before exposure.

Testing an unrepresentative operating mode

An idle communications port or static analogue input may be less susceptible than an actively switching interface. Testing only the easiest mode can leave the highest-risk condition unexamined.

Using the wrong conducted coupling method

An incorrectly selected CDN, clamp or injection probe changes the coupling path and common-mode conditions. Results may then be non-comparable with the applicable method, regardless of how accurately the generator level was set.

Ignoring cable position and bonding

Cable height, routing, termination and reference-plane bonding influence RF current. Moving a cable between sweeps without recording its position can shift a susceptibility response and prevent meaningful reproduction.

Failing to record recovery behaviour

A note stating “temporary degradation” is incomplete. The record should identify what degraded, when it recovered, whether recovery was automatic and whether data or settings changed.

Frequently Asked Questions (FAQs)

Can the manufacturer define intended performance?

The manufacturer often needs to declare performance limits where the product standard allows this, but those limits must be technically justified and consistent with intended use, published specifications and applicable requirements. An artificially broad tolerance may not provide defensible evidence.

Does any temporary degradation mean failure?

No. The answer depends on the assigned performance criterion and product-specific requirements. Some tests permit controlled temporary degradation, while others require operation within defined limits throughout exposure.

Must every product function be monitored simultaneously?

Not always, but all relevant functions need adequate assessment. Sequential operating modes may be acceptable if they represent intended use and the standard permits the approach. The rationale should be documented.

Can pre-compliance testing establish intended performance?

It can help refine monitoring methods, identify susceptible functions and set realistic acceptance limits before formal testing. It does not automatically prove compliance, especially where the setup or test level differs from the applicable method.

How should intermittent communication errors be assessed?

Define allowable error rate, retry behaviour, latency, lost-message consequences and recovery before testing. Raw packet loss alone may not describe functional impact, particularly where the application has error correction or deterministic timing requirements.

Do defence, automotive and aerospace programmes use the same criteria?

No. Contractual and sector-specific standards may define different functional states, susceptibility thresholds and acceptance processes. EMC Hire can provide pre-compliance support for these sectors, although final testing may require an appropriately accredited laboratory depending on programme requirements.

Discussing the test plan before exposure starts

If intended performance is not yet measurable, the test setup is not ready. EMC Hire's engineering team can help review operating modes, monitoring requirements, coupling equipment and the distinction between pre-compliance investigation and formal compliance evidence.

To request an equipment hire quotation, arrange on-site testing, discuss formal compliance or pre-compliance work, or book space at the EMC Hire test facility, call +44 (0)1462 817111 or email sales@emchire.co.uk.