Operational and Evidence Boundaries

ARSVIN is engineering software for IEC 61850 Sampled Values generation, reception, decoding, visualization, diagnostics, and evidence on authorized laboratory or test networks.

What the software can establish

Depending on the workflow and evidence source, ARSVIN can record:

• configured SCL expectations;
• frames generated by the Publisher;
• frames observed by the selected computer and adapter;
• decoded payload values, counters, timing observations, waveform, phasor, and RMS calculations;
• continuity, configuration, and payload-layout findings; and
• reproducible PCAP and Markdown evidence.

What the software does not establish

ARSVIN does not by itself establish:

• that another IED received, accepted, trusted, or acted on a multicast stream;
• calibrated current, voltage, phase, time, or protection-performance accuracy;
• deterministic real-time execution;
• formal IEC 61850 conformance or certification;
• functional-safety approval or cybersecurity certification;
• equipment isolation, switching authority, site authorization, or process safety;
• a replacement for an approved FAT, SAT, commissioning, or maintenance procedure; or
• suitability for unattended production process-bus monitoring.

Live Ethernet use

Raw Ethernet capture and transmission are active network operations. Use them only when:

• the network and connected equipment are explicitly authorized for the test;
• the adapter and test topology have been independently verified;
• an approved test plan and responsible person are in place;
• expected process consequences and recovery steps are understood; and
• evidence is stored without exposing confidential or restricted information.

A dry run, synthetic sample, PCAP import, or isolated point-to-point link should be used before any broader live-network exercise.

Software preflight checks are operational guardrails. They cannot prove that the external test environment is safe, isolated, authorized, or free from process consequences.