Skip to content

README.md

Latest commit

 

History

History
63 lines (49 loc) · 3.9 KB

README.md

File metadata and controls

63 lines (49 loc) · 3.9 KB
Raw

ARSAS Documentation

This directory contains the engineering, validation, licensing, provenance, and operating-boundary documents for the ARSAS Windows IEC 61850 engineering workstation.

Start here

Document Purpose
Project README Product overview, feature summary, quick start, build instructions, and public claim boundary.
IO List FAT Evidence Testing Imported SDI test plans, OFF → ON → OFF evidence, Excel/PDF export, portable .arsas projects, integrity checks, and cross-laptop continuation.
Architecture Multi-IED ownership, model identity, report-first acquisition, runtime scaling, and timestamp semantics.
GOOSE Subscriber Read-only Npcap capture, ARIEC61850 GOOSE decoding, SCL/live-discovery DataSet binding, ordered allData leaf semantics, diagnostics, and field validation.
Validation checklist Discovery, reporting, monitoring, recovery, evidence, and control acceptance checks.
UI validation Windows scaling, keyboard workflow, accessibility, multi-IED, and command-panel checks.
Engine compatibility Required ARIEC61850 source contracts and project-reference layout.

Evidence and project workflows

Document Purpose
IO List FAT Evidence Testing Dedicated one-IED FAT workspace, exact TestPointId mapping, ordered transition evidence, durable journal, .xlsx, native .pdf, and .arsas output.
Phase progress Historical signal-selection behavior and validation records.
Connection diagnostic audit Example route and connection-failure reasoning.
Changelog Public application, documentation, website, and release history.

Control engineering

Document Purpose
ARIEC61850 Smart Control integration Application-to-engine control service integration.
Smart Control feedback audit Control completion, feedback mapping, and evidence boundaries.
Close feedback event verification Event-driven feedback confirmation workflow.

Licensing and provenance

Document Purpose
Licensing model GPL community edition, historical boundary, and separate commercial licensing path.
License and provenance audit Repository-evidence review and remaining manual checks.
Clean-room and interoperability policy Independent-development, test-fixture, UI, and external-material boundaries.
External IP and provenance review Repository evidence concerning external implementation and proprietary-asset contamination.

Project policies

Documentation principles

Public documentation should:

  • distinguish configured SCL context from the live MMS model;
  • distinguish protocol readiness from switching authority and operational safety;
  • distinguish current main development behavior from the latest published stable installer;
  • state whether evidence comes from unit tests, deterministic fixtures, loopback, simulator, laboratory IEDs, or field use;
  • avoid universal interoperability, formal conformance, document-signature, or acceptance claims;
  • use synthetic or contributor-owned examples;
  • exclude confidential customer, employer, station, credential, signal-list, and project material.