Abstract
Operational limits have meaning within a defined procedure and activity. A software representation needs to preserve that context and make clear how input quality and freshness affect the displayed condition.
Technical field. Conditions and limits
Design considerations
- Each limit needs a source, units, applicable activity and agreed interpretation.
- Signal freshness, missing inputs and evaluation failures require defined presentation and review behaviour.
- Acknowledgement, operational authority and protective systems have distinct responsibilities. Their relationship must be established for the intended use.
Questions for technical evaluation
- Which conditions, signals and limits are evaluated in the demonstrated configuration?
- What happens when an input is missing, stale or outside its expected range?
- Which views receive condition updates, and how is that behaviour tested?
Scope of this note
This note describes workflow design and evaluation considerations. Supported behaviour, interfaces, controls and limitations need to be demonstrated for the proposed product configuration and intended project.