Resolve the control object
Normalize the selected reference and verify the Data Object boundary before staging an action.
Control-model-aware validation · explicit guardrails
Control the intended object through the sequence the live IED requires.
ARSAS does not translate a button label into a blind write. It reads the live control model, resolves the command structure, stages the supported Direct or Select-Before-Operate sequence and presents service, termination, timing, error and feedback evidence.
Evidence contract
Keep the observation together with the context that makes it reviewable.
ARSAS treats engineering data as evidence, not just screen output. The exact fields depend on the workflow, but the source and acquisition context should remain visible whenever they exist.
What?Signal, event, packet, file, model or command result
Which IED?Device identity, endpoint and project context
When?IED time, protocol time or ARSAS receive/capture time when available
Quality / state?IEC quality, event state, sequence state or result status when the source provides it
How acquired?Discovery, MMS read, Reporting, GOOSE/SMV capture, file service or control workflow
No invented certainty.Not every workflow exposes every field. ARSAS should preserve what is actually available, identify the acquisition path and keep missing context explicit rather than synthesizing proof.Review field interoperability evidence →Review engineering boundaries →
Direct + SBONormal and enhanced security control models
Live descriptorsNamed ctlVal binding from actual MMS types
Typed familiesDPC, SPC, INC/ISC, BSC and APC
Visible outcomeService, termination, error, timing and feedback
Discovery before dispatch
The command panel is the final step of model resolution.
A semantic action becomes available only when the live evidence can represent the command without positional guessing or a generic write fallback.
Read ctlModel
Determine Direct or SBO and normal or enhanced completion handling from the live model.
Inspect command descriptors
Retrieve Oper, SBOw and optional Cancel types and locate the named ctlVal field.
Bind semantic intent
Represent Open, Close, Boolean, Raise, Lower, counter or setpoint through the discovered live type.
Execute one supported sequence
Preserve origin, ctlNum, timestamp, Test, interlock and synchrocheck values throughout the staged command.
Record completion evidence
Present service results, CommandTermination, ControlError, AddCause, elapsed time and mapped process feedback.
Supported semantic families
Readable engineering actions with type-aware wire handling.
Position / DPC
Open and Close actions with command encoding and process feedback treated as separate evidence.
Boolean / SPC
True and False actions represented through the discovered single-point command structure.
Pulse / BSC
Raise and Lower semantics for supported binary step command types.
Counter / INC or ISC
Typed integer values when the live descriptor is complete and usable.
Setpoint / APC
Explicit value entry and type-aware binding for supported analog control objects.
Per-command checks
Test, interlock and synchrocheck requests remain attached to the exact staged command.
Protocol completion and process response
- Detected control model and selected sequence
- Confirmed MMS service result
- Positive or negative CommandTermination
- ControlError, AddCause and LastApplError where available
- Control number, origin, request flags and timing
- Mapped process feedback where available
Protocol readiness is not switching authority
- Two-step confirmation for Open and Close
- No generic command-write fallback
- Commands disabled when live descriptors are incomplete
- Negative outcomes remain visible
- Isolation, authorization and independent verification remain external requirements
Validation first
Exercise every supported control model before energized commissioning.
Validate positive and negative termination, interlock and synchrocheck rejection, Test mode, timeout, Cancel behavior, association loss, competing-client ownership and process feedback in an approved environment.
Verified stable · ARSAS 1.6.41
Ready for an approved Windows workstation?
Installer and portable packages share the same application scope. Verify the published SHA-256 and review the release boundary before field use.
Release notes, limitations and signing status →