Using the Source–Victim Matrix to Connect RE102 and RS103 in Shipboard EMC
Introduction
Electromagnetic Compatibility (EMC) is not just about passing tests in the lab. On naval platforms, dozens of communication, radar, and navigation systems must operate side by side without interfering with one another.
Two MIL-STD-461G tests cover opposite sides of this challenge:
- RE102 (Radiated Emissions): how much a device radiates.
- RS103 (Radiated Susceptibility): how much a device can withstand.
Individually, they ensure compliance. Together, they help answer the key question: can these systems coexist in the same shipboard environment?
That’s where the Source–Victim (SV) matrix comes in.
RE102 vs RS103 in Plain Terms
- RE102: You sweep across frequencies and measure a device’s emitted field strength (V/m or dBµV/m).
- RS103: You expose the device to known fields and check that it keeps working up to a defined immunity threshold (V/m or dBµV/m).
On their own, these tests are useful. But by combining them, you get a system-level picture of electromagnetic compatibility.
The SV Matrix Concept
The SV matrix compares every emitter (source) against every receiver (victim):
- Source device: generates the field (e.g., SATCOM, VHF radio, radar).
- Victim device: could be disturbed (e.g., GPS, NAVTEX, navigation radar).
- Distance: separation on the ship.
- Emission at 1 m (RE102): baseline radiated level.
- Emission at victim location: adjusted for distance and coupling.
- RS103 immunity level: the victim’s required tolerance.
- Margin (dB):
\text{Margin} = RS103 - Emission\_{at\ victim} - PASS/FAIL: Positive margin = safe. Negative margin = potential interference.
Example from Shipboard Data
From a sample dataset of 338 source–victim pairs, two scenarios stand out:
- Self-coupling (INMARSAT-C → INMARSAT-C)
- Emission at victim ≈ 13.8 MV/m (262 dBµV/m)
- RS103 requirement = 50 V/m (154 dBµV/m)
- Margin = –109 dB → FAIL
- Interpretation: extreme numbers (likely model placeholders), but it reminds us that self-interference is real.
- INMARSAT-C → NAVTEX
- Emission at victim ≈ 0.87 V/m (119 dBµV/m)
- RS103 requirement = 50 V/m (154 dBµV/m)
- Margin = +35 dB → PASS
- Interpretation: NAVTEX is well protected from INMARSAT emissions at this distance.
Workflow (Text Diagram)
Source Device (Tx) --> RE102 Emission at 1 m
|
v
Propagation / Coupling (distance, shielding)
|
v
Predicted Field at Victim (E_at_v, V/m & dBµV/m)
|
+--> Compare with RS103 Immunity Threshold
|
v
Margin = RS103 - E_at_v
|
+---------+----------+
| |
PASS (positive) FAIL (negative)
| |
Record in SV Matrix Apply Mitigation (filter, shield, relocate)
Why It Matters
- Holistic view: Instead of testing devices in isolation, you see how they interact.
- Design guidance: Placement, shielding, or filtering decisions are clearer.
- Early warning: Margins highlight risk areas before integration or deployment.
- Mission reliability: On ships, where space is tight and systems are dense, this method prevents costly surprises.
Example SV Matrix (Text Table)
| Source: VHF | Source: SATCOM | Source: Radar
---------------+----------------+-----------------+----------------
Victim: GPS | +28 dB PASS | +12 dB PASS | -6 dB FAIL
Victim: NAVTEX | +35 dB PASS | +18 dB PASS | +9 dB WARN
Victim: Radar | +42 dB PASS | -3 dB FAIL | +5 dB WARN
- Positive margin = PASS (safe)
- Slightly positive margin = WARN (borderline)
- Negative margin = FAIL (interference risk)
Conclusion
The SV matrix bridges the gap between RE102 (what a system emits) and RS103 (what a system must tolerate). Instead of isolated pass/fail results, you get a system-level compatibility map.
For complex shipboard environments, this method turns EMC analysis from a checkbox exercise into a practical design tool that directly improves mission readiness.
Get in Touch with us
Related Posts
- The Accounting Software Your Firm Uses Is Built for Your Clients, Not for You
- 2026年本地大模型(Local LLM)硬件选型实用指南
- Choosing Hardware for Local LLMs in 2026: A Practical Sizing Guide
- Why Your Finance Team Spends 40% of Their Week on Work AI Can Now Do
- 用纯开源方案搭建生产级 SOC:Wazuh + DFIR-IRIS + 自研集成层实战记录
- How We Built a Real Security Operations Center With Open-Source Tools
- FarmScript:我们如何从零设计一门农业IoT领域特定语言
- FarmScript: How We Designed a Programming Language for Chanthaburi Durian Farmers
- 智慧农业项目为何止步于试点阶段
- Why Smart Farming Projects Fail Before They Leave the Pilot Stage
- ERP项目为何总是超支、延期,最终令人失望
- ERP Projects: Why They Cost More, Take Longer, and Disappoint More Than Expected
- AI Security in Production: What Enterprise Teams Must Know in 2026
- 弹性无人机蜂群设计:具备安全通信的无领导者容错网状网络
- Designing Resilient Drone Swarms: Leaderless-Tolerant Mesh Networks with Secure Communications
- NumPy广播规则详解:为什么`(3,)`和`(3,1)`行为不同——以及它何时会悄悄给出错误答案
- NumPy Broadcasting Rules: Why `(3,)` and `(3,1)` Behave Differently — and When It Silently Gives Wrong Answers
- 关键基础设施遭受攻击:从乌克兰电网战争看工业IT/OT安全
- Critical Infrastructure Under Fire: What IT/OT Security Teams Can Learn from Ukraine’s Energy Grid
- LM Studio代码开发的系统提示词工程:`temperature`、`context_length`与`stop`词详解













