View Issue Details

IDProjectCategoryView StatusLast Update
000125410000-009: Alarms and Conditionspublic2012-01-27 16:46
ReporterMatthias Damm Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0001254: Clarifications regarding connection problems to underlying system
Description

The server behaviour is not defined for the case where the UA A&C server is loosing its connection to the underlying system providing the condition information.

(1) Quality field
A clarification should be added that it is not the purpose of the Quality field to indicate the conneciton status of the OPC UA server to the underlying system

(2) Condition indicating the status of the underlying system
The prefered way to indicate the status of the connection to the underlying system is to provide a OffNormal condition with class System to indicate the connection status.
Options for spec enhancements:
(a) We can define a specialized condition class or condition type for this purpose
(b) We can describe the combination in a best practice appendix

(3) Appendix (best practice) for handling connection problems
We should add a new appendix that describes the strategies to inform the client about connection problems to the underlying system.
The problem is that we need to find a way to tell the client which conditions or which part of the system is not available.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0000967 closedPaul Hunkar Need clarification about status codes for Read access to Condition fields 

Activities

Paul Hunkar

2010-07-29 20:10

developer   ~0001981

I also think the text should include a reference to the RequestRefresh event for an action when the connection is restored (or possibly when it is lost depending on what action is taken when losing a connection (may be a way to clean up display lists)

I also think it would be important to have a client cleanup any alarm display and remove stale alarms (i.e. ones that are not longer available from the underlying system, even though they could still be in alarm, but the connection is no longer available).

Randy Armstrong

2011-09-16 00:55

administrator   ~0003019

Add a best pratice condition

Paul Hunkar

2012-01-23 06:20

developer   ~0003221

Added a new event type and text to describe the case of communication problems to other system for alarms.

Jim Luth

2012-01-27 16:46

administrator   ~0003241

Reviewed and agreed after final editing in telecon.

Issue History

Date Modified Username Field Change
2010-06-08 23:10 Matthias Damm New Issue
2010-06-08 23:11 Matthias Damm Relationship added related to 0000967
2010-07-29 20:10 Paul Hunkar Note Added: 0001981
2010-11-16 17:48 Randy Armstrong Status new => assigned
2010-11-16 17:48 Randy Armstrong Assigned To => Paul Hunkar
2011-09-16 00:55 Randy Armstrong Note Added: 0003019
2012-01-23 06:20 Paul Hunkar Status assigned => resolved
2012-01-23 06:20 Paul Hunkar Resolution open => fixed
2012-01-23 06:20 Paul Hunkar Note Added: 0003221
2012-01-27 16:46 Jim Luth Status resolved => closed
2012-01-27 16:46 Jim Luth Note Added: 0003241