ARSVIN GitHub

Sampled Values Conformance and Interoperability Matrix

This matrix is the working control sheet for ARSVIN profile expansion. It records what is known, what remains provisional, and what evidence is required before a behavior becomes part of a supported profile.

Evidence status vocabulary

Status Meaning
Verified-standardConfirmed from a licensed applicable standard and recorded with edition and clause.
Verified-officialConfirmed from an official standards-body or manufacturer document.
Verified-captureConfirmed from an anonymized real-device SCL/PCAP pair.
Verified-labConfirmed by byte-exact or interoperability testing with a real counterpart.
Implemented-genericEngine supports the mechanism, but no profile-specific compliance claim is made.
ProvisionalCandidate behavior awaiting stronger evidence.
UnknownNot yet researched.
Out-of-scopeExplicitly excluded from the current milestone.

Standards source register

Source Public edition baseline Licensed clause review Owner action
IEC 61850-62009 + AMD1:2018 + AMD2:2024 CSVRequiredObtain/access current licensed copy; map SCL requirements.
IEC 61850-7-22010 + AMD1:2020 CSVRequiredMap abstract SV service semantics.
IEC 61850-9-22011 + AMD1:2020 CSVRequiredMap Ethernet/APDU encoding and required fields.
IEC/IEEE 61850-9-32016Required for timing claimsMap PTP profile boundaries and terminology.
IEC 61850-102012 + AMD1:2025 CSVRequired for claim languageMap conformance terminology and test evidence boundaries.
IEC 61869-9Current licensed edition to verifyRequiredMap preferred variants, scaling, sampling, and dataset requirements.
IEC TR 61850-90-52012 public catalogue baselineDeferredSeparate R-SV architecture program.
UCAIug 9-2LE guidelineRevision to identifyRequired for 9-2LE claimObtain authoritative copy and revision history.

Generic Layer-2 SV mapping

Requirement Current ARSVIN state Evidence status Required next evidence
Ethernet EtherType 0x88BAPublisher and Subscriber use Layer-2 SV EtherTypeImplemented-genericClause mapping and byte-exact fixture.
APPID and process-bus headerImplementedImplemented-genericBoundary and malformed-frame vectors.
VLAN tag, ID, and priorityImplementedImplemented-genericStandard clause mapping and tagged/untagged captures.
svID / smvIDParsed and emittedImplemented-genericEdition-specific naming and length tests.
Dataset referenceSCL-drivenImplemented-genericClause mapping and dataset-resolution fixtures.
confRevParsed and emittedImplemented-genericChange/mismatch behavior tests.
smpCntParsed, emitted, monitored, and wrap-testedImplemented-genericProfile-specific wrap rules.
smpSynchCompatibility modes implementedImplemented-genericLicensed semantics and synchronized/unsynchronized captures.
smpRate / smpModParsed and emittedImplemented-genericEdition/profile-specific presence and interpretation rules.
Multiple ASDUs per frameEngine supports 1..8; UI/docs historically emphasize 1/2/4/8Implemented-genericProfile-specific allowed values and nofASDU=6 evidence.
Dataset-driven payloadMultiple integer, float, quality, time, enum, bit-string, and string kinds supportedImplemented-genericValidate permitted SV bTypes, widths, order, and nesting.
Unknown payload elementPreflight can reject unsupported layoutsImplemented-genericCompatible-mode raw preservation design.
PCAP read/writeImplemented and regression-testedImplemented-genericGolden external captures.
Observation windowTransport-independent facts, rate estimation, stable-field checks, and counter-wrap detection implementedImplemented-genericIntegrate with live and PCAP Subscriber pipelines.
Profile matchingEvidence-aware weighted detector with explained matches, conflicts, and unknowns implementedImplemented-genericAdd verified profile definitions after source review.
Configuration versus wireStrict and compatible comparison engine implementedImplemented-genericConnect SCL bindings to observed stream facts in the UI.

9-2LE-style profile research

Topic Current position Status Exit criterion
Profile name and revision9-2LE-style onlyProvisionalIdentify authoritative guideline and revision.
4 current + 4 voltage layoutCurrent primary workflowProvisionalGuideline clause plus golden dataset and captures.
Value representationCurrent workflow uses SCL-derived layoutProvisionalByte-level guideline verification.
Quality ordering and encodingEngine supports quality fieldsProvisionalGuideline vectors and device capture.
Protection sampling variantProduct assumption existsProvisionalStandard/guideline source plus 50 Hz and 60 Hz captures.
High-rate variantRoadmap candidateProvisionalStandard/guideline source and performance fixture.
Nominal-frequency behaviorInfrastructure can evaluate samples-per-cycleProvisionalVerify formula, rate, wrap, and frame-rate behavior.
Scaling conventionNot yet provenance-awareUnknownVerify raw-to-secondary convention and expose source.
Publisher interoperabilityGeneric output worksProvisionalAt least one real counterpart test per claimed variant.
Subscriber detectionExplainable profile detector foundation existsImplemented-genericAdd verified definitions and golden known/unknown/mismatch vectors.

IEC 61869-9 profile research

Topic Current position Status Exit criterion
Preferred variant catalogueNot implementedUnknownLicensed clause matrix.
Configurable dataset behaviorGeneric SCL engine can support itProvisionalStandard requirement and real SCL evidence.
Protection-oriented variantRoadmap candidateProvisionalLicensed rates, packing, payload, and timing requirements.
Measurement/high-rate variantRoadmap candidateProvisionalLicensed requirements and sustained-throughput tests.
Sampling basisDetector supports samples-per-second and samples-per-cycle definitionsImplemented-genericVerify profile-specific semantics.
nofASDU valuesEngine mechanically supports 1..8ProvisionalProfile-specific normative/recommended values.
Dataset shape and channel orderMust not be assumed fixed 4I+4VProvisionalStandard plus device SCL matrix.
Scaling and unitsNot yet profile-provenance-awareUnknownStandard clause, SCL source, and real values.
SynchronizationGeneric smpSynch and PTP tooling existProvisionalStandard linkage and capture evidence.
Public support claimNot supported yetUnknownAll mandatory rows reach verified-standard and fixture/device evidence.

Engineering workflow outcomes

These are product outcomes, not protocol requirements and not references to any proprietary product implementation.

Outcome ARSVIN target
SCL-first system viewImport configured streams and show expected-versus-observed state.
Configuration versus live comparisonCompare addressing, dataset, packing, rates, and profile evidence side by side.
Signal tracingTrace an SCL stream to observed traffic and decoded channels.
Orphan detectionList observed streams absent from SCL and expected streams absent from traffic.
MU parameter verificationValidate fields, rate, packing, payload, synchronization, and quality.
Packet interval statisticsAdd intervals, jitter, gaps, bounded statistics, and evidence export.
Triggered recordingAdd software trigger rules after profile detection is stable.
Redundancy verificationKeep PRP/HSR in a separate evidence-backed milestone.
Reusable tests and reportsUse machine-readable expected-profile fixtures and repeatable reports.

Fast-track implementation gates

Gate 0 — Research register

Complete:

Gate 1 — Profile infrastructure

Complete in engine code:

Remaining Gate 1 integration:

Gate 2 — Formalized 9-2LE-style support

Complete when:

Gate 3 — IEC 61869-9 protection support

Complete when:

Gate 4 — High-rate and redundancy support

Complete when:

Definition of public Supported

A profile can be labeled supported only when all are true:

GPL-3.0-or-later community documentation. Commercial terms require a separate agreement.Review this page on GitHub →