Defence EMC report checklist

A defence EMC test can be technically sound yet become difficult to defend months later because one cable position, equipment setting or calibration reference was never recorded.

The report is not an administrative afterthought. It is the evidence that connects the requirement, test configuration, recorded traces, observed EUT behaviour and engineering decision.

What a defence EMC report needs to establish

A useful defence EMC report should allow a technically competent reviewer to understand what was tested, why it was tested, how the test was performed and whether the resulting evidence supports the stated conclusion. That reviewer may not have attended the test. They may open the report during a design review, platform integration investigation or contractual dispute several years later.

The applicable requirements may come from DEF STAN 59-411, MIL-STD-461, a platform-specific specification, an equipment procurement document or a tailored electromagnetic environmental effects control plan. A standards reference on its own is rarely enough. The report must identify the edition, method, test level, frequency range, limits, performance criteria and any contractual tailoring that were actually applied.

Always verify the latest active edition and the requirements invoked by the contract. Product configuration, installation environment, platform interfaces and customer-specific test plans can change the applicable methods substantially. A high-level summary should never be treated as a substitute for the published standard or contract documentation.

EMC Hire provides defence EMC testing and engineering support, including equipment hire, pre-compliance investigation, access to test facilities and on-site work. Final acceptance testing may need to be performed by an appropriately accredited laboratory where the contract, programme or approving authority requires it.

Defence EMC report checklist

Document identity and approval status

Start with controlled-document information. Record the report title, unique identifier, revision, issue date, page numbering, author, reviewer and approval status. Amendments should be visible through a revision history rather than silently overwritten.

The document should distinguish test results from engineering interpretation. If a reviewer cannot tell whether a statement is a recorded observation, a calculation or an opinion, the report becomes vulnerable during later scrutiny.

Applicable requirements and standards reference

State the precise source of every requirement. Include the standard or specification designation, edition or issue, method identifier and relevant contractual tailoring. Where a customer test plan modifies a standard method, identify both documents and explain which instruction takes precedence.

A requirements matrix is often the clearest approach. For each test, record the applicable port, limit or test level, frequency range, modulation where relevant, dwell or monitoring requirement, EUT performance criterion and report section containing the evidence.

Do not mix emissions and immunity terminology. Conducted emissions concern disturbances leaving the EUT through relevant conductors and are measured using the network or probe required by the selected method. Conducted susceptibility or immunity uses energy coupled into cables, commonly through methods such as current injection where specified. Radiated emissions and radiated susceptibility use antennas, but the instrumentation, calibration process and physical objective are different.

EUT identity and build configuration

Record the equipment nomenclature, manufacturer, model, serial number, hardware revision, firmware and software versions. List external modules, representative loads, simulators, support equipment, power supplies and interface adaptors.

Configuration control matters. A filter capacitor change, revised cable screen termination or firmware update that alters processor activity can change EMC behaviour. If the build state is vague, later testing cannot confirm whether it examined the same article.

For modified prototypes, include a controlled list of temporary fixes. Copper tape, ferrites, feedthrough capacitors and supplementary bonding straps must not disappear into an informal lab notebook. State the part, value, position, number of turns where relevant and whether the modification is intended for production.

Operating modes and functional monitoring

Describe how the EUT was exercised and why the selected mode was considered representative or worst case. Include data rates, switching states, transmitter activity, actuator loads, processor-intensive functions and power conditions where they affect emissions or susceptibility.

For immunity work, define the monitoring method and acceptance criteria before testing begins. A statement such as “no anomalies observed” is weak if no one records which parameters were watched, their tolerances, the observation interval or how transient faults were captured.

Monitoring equipment can also disturb the test. Long unfiltered leads may form unintended antennas, while fibre conversion, optical isolation or filtered feedthroughs can reduce interaction where technically appropriate. Document the arrangement.

Physical setup, bonding and cable routing

Record dimensions rather than relying on phrases such as “configured normally”. Include EUT orientation, ground-plane material, bonding method, support height, cable lengths, cable spacing, harness construction, screen terminations and distances to chamber boundaries or antennas.

Photos should show the complete setup and the details most likely to influence coupling. Useful views include:

• overall EUT and support-equipment arrangement;
• power and signal cable routing;
• bonding points and ground straps;
• connector backshells and screen terminations;
• probe, antenna or injection-device position;
• monitoring and load configurations.

Photographs should be captioned and referenced from the relevant test section. A close-up without context may show a current probe but not where it was placed on the harness. Include a wider view or marked diagram so that position and orientation can be reconstructed.

Test equipment and calibration evidence

List the instruments that materially affect the result, including manufacturer, model, serial number, asset identifier and calibration due date. This may cover receivers, spectrum analysers, signal generators, power meters, amplifiers, antennas, current probes, LISNs, attenuators, directional couplers, field probes and ESD simulators, depending on the test method.

EMC Hire uses test equipment with calibration traceable through an appropriate ISO/IEC 17025 accredited calibration provider. The accreditation applies to the calibration provider or calibration activity, not to the physical instrument. Suitable traceable calibration supports measurement accuracy, repeatability and comparison between development and formal test data.

Calibration status alone does not prove suitability. Check frequency coverage, power handling, detector capability, dynamic range and transducer factors against the method. A calibrated current probe used outside its characterised frequency range still produces unreliable evidence.

Where accreditation status must be examined, the UKAS website and directory provide information on accredited organisations and scopes. The scope should be checked rather than assuming that accreditation covers every calibration or test activity.

Test parameters, corrections and uncertainty

Record receiver detector, resolution bandwidth, video bandwidth where applicable, sweep or dwell parameters, attenuation, preamplifier state and transducer corrections. These settings depend on the selected method and frequency range. Peak, quasi-peak and average detectors are not interchangeable, and no single resolution bandwidth applies across every defence EMC procedure.

For immunity testing, capture applied level, modulation, step size, dwell time, forward power, net power or injected current as required by the method. State how the level was established and monitored. Do not report radiated electric-field strength in units of conducted voltage or treat injected current as though it were V/m.

Where required by the programme, include the measurement uncertainty approach, calculated uncertainty and decision rule. The report should explain how uncertainty was handled when a result lay close to a limit, rather than adding an unexplained number at the end.

Traces, tables and raw data

Every trace needs enough metadata to stand independently. Include test identity, EUT mode, date, frequency span, amplitude unit, detector, bandwidth, limit line, transducer correction status and file reference. Screenshots cropped so tightly that settings disappear are poor evidence.

Preserve native data files where practicable, not only images pasted into a report. Native data allows markers, corrections and settings to be reviewed later. Maintain a controlled link between raw files and report figures through consistent filenames or an evidence index.

Susceptibility events should be tabulated with frequency, applied level, observed effect, performance criterion, recovery behaviour and retest result. If an event cannot be reproduced, say so. Omitting inconvenient or ambiguous observations damages confidence more than documenting them properly.

Deviations, failures and engineering changes

Log every departure from the approved method, including the reason, technical impact and authorisation. Examples include restricted antenna distance, unavailable operating modes, shortened dwell times or support equipment that could not be positioned as planned.

Failed tests need more than a red status box. Record the failing frequency or range, margin, EUT state and investigation performed. If a modification was introduced, separate the original result from the modified result so the evidence trail remains intact.

Conclusion and evidence boundaries

The conclusion should identify the tested configuration and requirements satisfied, not make an unrestricted claim about every production unit or installation. State unresolved deviations, exclusions and conditions affecting interpretation.

Formal evidence can support a technical file, EMC risk assessment, mitigation record, Declaration of Conformity or customer submission where the applicable route permits. Testing alone does not complete every conformity obligation. The manufacturer or responsible economic operator remains responsible for confirming applicable legislation, standards, contractual requirements and documentation.

Typical scenario

Consider an illustrative communications controller being prepared for installation on a defence platform. Early bench work has identified narrowband emissions associated with a switched-mode converter, but the production harness and enclosure bonding arrangement are still being finalised.

The team must decide whether to proceed directly to formal testing or run a controlled pre-compliance investigation. A sensible preliminary setup would reproduce the intended power source, cable construction, loads, grounding and operating modes as closely as development permits. Conducted and radiated investigations would remain separate, using the transducers and configurations required by the relevant procedures.

If the harness layout is changed between scans without recording it, an apparent improvement may be attributed to the converter modification when it actually resulted from altered cable coupling. Photos, dimensions and native traces prevent that mistake.

Accessible EMC pre-compliance testing gives the team room to investigate filters, bonding and cable-screen terminations before a tightly controlled programme test. It can provide calibrated engineering data and reduce late redesign risk, but it does not automatically demonstrate compliance.

EMC Hire can support equipment selection, hire for a defined investigation window, facility bookings, on-site testing and preparation for formal compliance work. Where final testing must be performed by an appropriately accredited laboratory, early evidence can still make that programme more focused and less exposed to avoidable configuration failures.

When to Hire EMC Equipment

Hiring is technically attractive when the required receiver, amplifier, antenna, current probe or coupling equipment is needed for a short development phase rather than continuous use. It avoids committing capital to an instrument whose frequency range, power rating or test-method compatibility may not suit the next programme.

Short-term access also helps teams scale capability during project peaks. Ownership brings storage, servicing, calibration scheduling and the risk of obsolescence. Those costs can be difficult to justify for irregular defence work or a single investigation.

Equipment selection should start from the test method and required evidence. Hiring a spectrum analyser without the correct transducer, characterised cable losses or suitable detector functions may produce an attractive plot that cannot answer the engineering question.

A defined hire window can support bench debugging, witnessed on-site investigation or preparation before a facility booking. EMC Hire can help match equipment to the intended emissions or immunity method and advise on practical setup requirements.

Common EMC Testing Mistakes to Avoid

Treating photographs as decoration

Unlabelled photos rarely establish distance, orientation or cable routing. The result may be impossible to reproduce. Add captions, dimensions and cross-references to the test record.

Recording calibration dates but not instrument identity

A calibration certificate cannot support traceability if the report omits the serial number or uses an ambiguous asset description. The reviewer must be able to connect each influential instrument to the relevant record.

Saving plots without acquisition settings

A trace without detector, bandwidth and correction information can lead to incorrect comparison with a limit. Preserve native files and export plots with settings visible.

Using an unrepresentative EUT mode

An idle processor, inactive transmitter or lightly loaded converter may miss the dominant disturbance mechanism. Define operating modes from product behaviour and the contractual test plan, then record the mode used for each trace.

Changing cable positions during diagnosis

Cable movement changes common-mode coupling and can create false improvement. Mark cable positions, photograph the setup and change one controlled variable at a time.

Failing to document deviations

An unexplained departure from the method weakens the evidence trail even when the measured margin appears generous. State what changed and assess its likely influence.

Frequently Asked Questions (FAQs)

Should every defence EMC report include raw data?

Native data should be retained where practicable, particularly for receiver traces, scans and immunity event logs. The report can present selected evidence, but an indexed archive makes later technical review far more effective.

Is a calibration certificate enough to prove a measurement is valid?

No. Calibration supports traceability, but the equipment must also be suitable for the frequency, level, dynamic range and test method. Setup errors and incorrect corrections can invalidate data from a calibrated instrument.

How much photographic evidence is appropriate?

Include enough to reconstruct influential features without filling the report with repetitive images. Overall views, cable routing, bonding details and transducer positions generally matter most.

Can pre-compliance data be included in a formal report?

It can be included if clearly identified as development or pre-compliance evidence. Do not present it as formal proof unless the method, controls and programme requirements support that interpretation.

Which standards reference should appear in the report?

Identify the exact standard, issue, method and contractual tailoring actually applied. EMC Hire's guide to understanding EMC standards provides useful context, but the current published documents and customer requirements must be checked.

Does defence EMC evidence support CE or UKCA documentation?

Some evidence may be technically relevant, but defence contractual tests do not automatically satisfy every regulatory requirement. The applicable legislation, designated or harmonised standards and conformity route must be assessed separately. See EMC Hire's practical guidance on CE marking and EMC evidence.

Discuss the report before testing starts

The strongest defence EMC report is designed alongside the test plan, not assembled from disconnected screenshots after the equipment has left the facility. Agreeing configuration records, trace formats, photographic coverage and deviation controls early saves considerable reconstruction work.

To discuss equipment hire, on-site testing, pre-compliance support, formal compliance testing where appropriate, or a booking at the EMC Hire test facility, contact the engineering team on +44 (0)1462 817111 or email sales@emchire.co.uk.