How to brief a lab on standards scope

A laboratory cannot resolve an undefined standards scope by measurement. If the product, ports, operating modes and acceptance criteria are ambiguous, even technically sound test data may answer the wrong question.

A good EMC lab brief establishes what is being evaluated, why each test applies and which configuration represents the highest electromagnetic risk. It gives the laboratory enough information to plan equipment, facility time, test methods and reporting without making unsupported assumptions about the product.

What an EMC lab brief needs to establish

The brief should begin with the intended purpose of the work. Pre-compliance investigation, formal compliance testing, design debugging and comparative measurements are different activities. They may use similar equipment, but they do not necessarily require the same test sequence, measurement discipline or documentation.

State whether the objective is to investigate a known problem, assess readiness for a formal programme, produce evidence for a self-certification route where applicable, or satisfy a contractual test plan. Testing alone does not complete every conformity obligation. The manufacturer or responsible economic operator remains responsible for confirming the applicable legislation, standards, conformity assessment route and documentation.

Give the laboratory a concise product description covering function, intended environment, user type, power sources, maximum cable lengths and communication interfaces. Include the target markets. A mains-powered industrial drive, an automotive electronic control unit and domestic multimedia equipment can have markedly different product-family requirements, even where some underlying test methods appear similar.

Define the standards hierarchy, not just a test-method number

A common briefing error is to nominate a basic test method without identifying the product standard that calls it up. The IEC 61000-4-x series describes immunity test methods. It does not, by itself, normally define the complete set of product requirements, port applicability, performance criteria or market-specific obligations.

For example, IEC 61000-4-6 addresses conducted RF immunity using coupling devices such as CDNs where the method and port permit. The relevant product or product-family standard should determine whether the test applies, the required frequency range, test level, modulation, dwell arrangement and performance criterion. A BCI probe belongs to applicable current-injection methods used in automotive, military, aerospace or other product-specific procedures. It should not be substituted for a CDN merely because both introduce RF energy onto cables.

List each proposed standard with its edition, amendment status and role in the programme. Mark it as a product standard, product-family standard, emissions standard, immunity method, customer specification or internal engineering requirement. The laboratory can then identify conflicts and missing links before test time is booked.

The latest active edition is not automatically the edition required by a contract or regulatory transition arrangement. Verify the applicable edition, product scope, test levels, frequency ranges, limits, equipment configurations and documentation requirements. The IEC standards development information explains how international standards are prepared and maintained, but the current published documents still need to be checked directly.

Describe every electrically distinct port

Port information drives the test setup. Provide connector type, electrical function, screening arrangement, cable construction, maximum supported cable length and whether the cable leaves the equipment enclosure. Identify AC mains, DC power, analogue signal, Ethernet, USB, antenna, chassis earth and dedicated protective earth connections separately.

This prevents coupling devices being selected by connector appearance rather than electrical function. A LISN may be required for conducted emissions measurement on a relevant power port. It is not a conducted immunity device. A CDN may be appropriate for conducted RF immunity on a qualifying cable, while a capacitive coupling clamp may be called up for electrical fast transient testing of certain signal or control cables.

Include normal source and load impedances. An unterminated interface can produce a different RF current distribution from the installed system. It may also stop the equipment under test, or EUT, entering the operating state that generates its highest emissions.

Configuration and variants must be controlled

Submitting a product family name is not enough. Record hardware revision, PCB revision, firmware version, enclosure material, power supply option, fitted modules, clock frequencies, memory population and accessories. If more than one variant is to be represented by a single test sample, explain the engineering basis for choosing that sample.

The largest enclosure is not necessarily the worst case. A smaller variant may have poorer shielding, a faster processor or a longer internal cable. Likewise, the highest power version may dominate conducted emissions while a lower power model has the more efficient radiating structure.

A useful variant matrix records:

• features common to every model;
• differences affecting clocks, power conversion, shielding or cable interfaces;
• maximum cable populations and permitted accessories;
• software-controlled operating modes;
• the proposed worst-case variant for each test phenomenon;
• the justification for excluding untested variants.

If the justification is weak, discuss selective measurements across two or more variants. A short comparative pre-scan can be cheaper than discovering later that the nominated sample did not represent the family.

Operating modes need measurable definitions

Descriptions such as “normal operation” are rarely sufficient. State data rates, duty cycles, actuator positions, display content, transmit states, processor load, charging condition and power conversion mode. Explain how the mode will be initiated and monitored throughout the test.

Immunity testing also needs observable performance criteria. Define which functions may temporarily degrade, which must remain within tolerance and which require operator intervention to recover. Quantify tolerances where practical. A statement that the EUT “continues to work” does not tell the test engineer whether a dropped packet, one-second display freeze or reset is acceptable.

Monitoring equipment can itself change the EMC result. Long oscilloscope leads, unfiltered Ethernet cables or unearthed support laptops may introduce coupling paths that are absent in service. Identify auxiliary equipment and agree how it will be positioned, powered, isolated or connected through suitable filtering.

Typical scenario

Consider an illustrative family of industrial controllers with two enclosure sizes, optional Ethernet, 24 V DC power and several firmware-controlled I/O modes. The buyer initially requests “CE EMC testing” and supplies only the model number. That is not yet a usable EMC lab brief.

The engineering team first needs to confirm the intended environment and identify the relevant product or product-family standards. It must then map the power and signal ports, determine which options create the highest cable activity and define representative operating modes. If radiated emissions are required, cable routing, auxiliary equipment and enclosure bonding need to reproduce a credible installation. For conducted emissions on the DC power port, the applicable standard must be checked before selecting a network and measurement arrangement.

On the immunity side, the team should define failure indicators and recovery behaviour before testing starts. Without agreed criteria, an observed communication interruption can trigger an argument after the exposure rather than a technically defensible decision during it.

Early investigation through EMC pre-compliance testing can compare variants, find dominant emissions and expose monitoring weaknesses before a formal programme. Pre-compliance data does not automatically prove compliance, but calibrated engineering measurements can reduce redesign risk and improve confidence in the selected configuration.

EMC Hire can support the scope review, test setup, equipment selection, on-site investigation and facility planning. Where formal compliance testing is appropriate, the resulting evidence may support the technical file, EMC risk assessment, Declaration of Conformity, mitigation records and stakeholder requirements. Some defence, automotive and aerospace programmes may require final testing by an appropriately accredited laboratory, depending on the contract and programme rules.

An engineering checklist for the initial brief

A compact brief can still be complete. Supply the following information before asking the laboratory to confirm time and equipment:

• product description, intended use, environment and target markets;
• proposed standards, editions, amendments and contractual specifications;
• test purpose, including pre-compliance, debugging or formal compliance work;
• schematics or block diagrams showing ports, cable screening and earth arrangements;
• variant matrix with a reasoned worst-case selection for each test;
• hardware, firmware and software revision identifiers;
• operating modes, duty cycles and methods of activation;
• immunity performance criteria and measurable pass or fail indicators;
• support equipment, loads, simulators, cables and specialist connectors;
• known EMC risks, previous results and implemented mitigations;
• required report format, photographs, raw data and traceability records;
• programme dates, sample availability and safe operating instructions.

Flag hazardous voltages, stored energy, moving machinery, pressure systems, lasers, hot surfaces and unusual shutdown sequences. Laboratory personnel need this information before setup begins, not after an interlock has been bypassed or an emergency stop is found to invalidate the operating mode.

When to Hire EMC Equipment

Hiring suits projects where the test window is defined but demand is irregular. It avoids capital expenditure on receivers, analysers, LISNs, probes or immunity generators that may spend most of their life in storage. Ownership also brings servicing, software, storage, repair and calibration obligations.

Equipment choice should follow the EMC lab brief. Buying a receiver that lacks the required frequency coverage, CISPR detector functions or suitable analysis bandwidth creates an expensive limitation for later programmes. Similar problems arise when a coupling device cannot handle the EUT current or does not suit the specified test method.

Short-term hire can scale internal capability during project peaks, support a targeted debugging exercise or provide a replacement during service and calibration. EMC Hire's equipment selection guides can help teams narrow the requirement, while engineering discussion is advisable where cable type, power rating, frequency coverage or software control affects compatibility.

For measurements where calibration is relevant, EMC Hire uses test equipment with calibration traceable through an appropriate ISO/IEC 17025 accredited calibration provider. Suitable traceable calibration supports repeatability, comparison between development and formal measurements, and a stronger evidence trail. The accreditation applies to the calibration provider or activity, not to the physical instrument itself.

Teams without a suitable screened environment can consider EMC laboratory hire or book an appropriate test facility for hire. This can be more controlled than debugging in an electrically noisy workshop, particularly when ambient signals mask low-level emissions.

Common EMC Testing Mistakes to Avoid

Allowing the laboratory to infer the applicable scope

A laboratory may identify obvious gaps, but it cannot know the product's full intended use or contractual obligations without input from the manufacturer. An inferred scope can omit a port, environment or variant and leave technically competent measurements with limited evidential value.

Changing cable routing without recording it

Cable position affects common-mode current and antenna efficiency. Moving an I/O cable between scans can change a radiated emissions plot or immunity susceptibility point. Photograph cable paths, support heights, terminations and excess cable arrangement so that the setup can be reproduced.

Using the wrong detector or receiver settings

Peak, quasi-peak and average detectors serve different purposes in emissions testing. Resolution bandwidth and detector selection must follow the relevant standard and frequency range. A fast analyser sweep with convenient settings may help debugging, but presenting it as a compliant measurement can create false confidence or an apparent failure that cannot be reproduced.

Testing an idle or convenient operating mode

An idle processor, inactive network port or lightly loaded converter may suppress the mechanism under investigation. The resulting margin is not representative of the marketed configuration. Exercise simultaneous functions where that state is credible and document the sequence used.

Leaving acceptance criteria until the test

Undefined immunity criteria make event classification subjective. Agree observable behaviour, permitted degradation, recovery conditions and logging arrangements beforehand. This gives the report a clearer technical basis and reduces disputes between engineering, quality and laboratory teams.

Failing to freeze the tested build

A firmware update or substitute power supply introduced midway through testing breaks configuration traceability. Record serial numbers, revision identifiers and deviations. If a change could affect EMC performance, assess whether earlier tests remain representative rather than assuming continuity.

Frequently Asked Questions (FAQs)

Should the lab select the applicable EMC standards?

The laboratory can provide technical input and identify likely standards, but the manufacturer remains responsible for confirming applicability. Product function, intended environment, markets, radio features and contractual requirements all influence the final scope.

How should multiple product variants be covered?

Build a matrix of EMC-relevant differences and select the likely worst case separately for each phenomenon. One variant may dominate conducted emissions while another is more susceptible to radiated RF. Where the choice is uncertain, comparative pre-compliance measurements can provide evidence for the selection.

Does a pre-compliance report prove conformity?

No. Pre-compliance work supports design decisions and risk reduction, but it does not automatically establish conformity. Its value depends on the setup, equipment suitability, calibration, test coverage and how closely it represents the applicable formal method.

What calibration evidence should be requested?

Ask for calibration status appropriate to the measurement chain, including relevant transducers and coupling devices where their characteristics affect the result. UKAS information on accreditation explains the role of accredited conformity assessment. Do not describe an instrument itself as ISO/IEC 17025 accredited.

How detailed should immunity performance criteria be?

They should be specific enough for an engineer to classify an event without interpretation after the test. Define monitored functions, acceptable tolerances, temporary degradation, automatic recovery and any loss of stored data or safety-related function.

Can the scope change after testing has started?

Yes, but the impact should be controlled. Record the reason, revised configuration, affected tests and whether earlier data remains representative. Unrecorded scope changes weaken repeatability and can leave gaps in the technical file.

Turn the brief into a defensible test programme

A well-constructed EMC lab brief gives both buyer and laboratory a shared technical baseline. It reduces setup changes, avoids testing the wrong variant and produces records that are easier to compare, review and defend.

To review a standards scope, 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, contact the engineering team on +44 (0)1462 817111 or email sales@emchire.co.uk.