ARSVIN Documentation

ARSVIN is an IEC 61850 Sampled Values engineering suite for Windows. It includes ARSVIN Publisher for stream generation and ArSubsv Subscriber for live or PCAP reception, decoding, visualization, and receiver-side evidence.

Start here

• Quick Start — install the suite, choose Publisher or Subscriber, and begin with a guarded offline or authorized test workflow.
• Safety Boundaries — laboratory assumptions, authorization, and responsible use.
• Known Limitations — current protocol, timing, evidence, and runtime boundaries.
• Licensing — current GPL community edition, historical Apache boundary, and commercial licensing path.

Sampled Values standards and interoperability

• SV Standards and Evidence Research Gate — authoritative source hierarchy, claim levels, evidence requirements, and research acceptance rules.
• SV Conformance and Interoperability Matrix — implemented, provisional, unknown, and out-of-scope requirements for 9-2LE-style, IEC 61869-9, and generic Layer-2 SV.
• SV Profile Infrastructure — transport-independent observed facts, evidence-aware definitions, confidence detection, and configuration-versus-wire comparison.
• Profile Detection Output Contract — confidence, evidence, and mismatch presentation rules.
• Public Terminology Policy — vendor-neutral public wording and automated validation.
• samples/sv-evidence — synthetic or authorized evidence intake, anonymization rules, metadata, and regression cases.

Publisher workflows

• SV Profile Support — current publishing support and limits.
• Multi-Stream SV Publishing — multiple publisher slots.
• Publisher Session Engine — runtime session model.
• Live Preflight Diagnostics — checks before authorized live transmission.
• P0 Publisher Protocol Roadmap — nofASDU, quality, timing, and PCAP foundation.
• P1 Publisher Evidence Workflow — generated PCAP and Markdown evidence.
• P2 Full Publisher Scenario Engine — repeatable protection and process-bus scenarios.
• Waveform Shape Panel — per-phase and waveform-shaped scenarios.

Subscriber workflows

• Subscriber Verification App — receiver-side stream binding, validation, health, and evidence.
• ArSubsv SV Scout Companion — discovery, waveform, phasor, RMS, and PCAP analysis.

Data sources and timing

• COMTRADE Replay — replaying analog records as Sampled Values.
• PTP and smpSynch Compatibility — timing and synchronization boundaries.
• Sync Compatibility Mode — laboratory smpSynch behavior.

Build, release, and repository governance

• Architecture
• Build and Release
• Public Release Checklist
• SEO and Public Launch Checklist
• GitHub Repository Settings
• Repository Audit
• External IP and Provenance Review — 2026-07-14
• Public Wording and Claim Review — 2026-07-14

Project policies

• Contributing
• Contributor License Agreement
• Developer Certificate of Origin
• Security
• Support
• Community conduct
• GPL license
• Commercial licensing
• Copyright
• Trademark and branding
• Third-party notices

Documentation principles

Public documentation should:

• distinguish configured SCL expectations from observed wire traffic;
• distinguish transmitter evidence from receiver evidence and IED behavior;
• identify whether evidence comes from tests, loopback, laboratory equipment, or an approved commissioning environment;
• avoid universal interoperability, formal conformance, functional-safety, cybersecurity, and deterministic-timing claims;
• use synthetic or contributor-owned examples; and
• exclude confidential customer, employer, station, credential, and restricted network material.