Difference between revisions of "uaCap:AlarmsConditions Dialogs"

From UaCapabilities
Jump to: navigation, search
(Created page with "{{CapabilityUri|/Alarms/Dialogs}} '''Description''' <br>An extension of the Alarm model where a server can interact with a client. The client does not need to be programmed...")
 
Line 1: Line 1:
{{CapabilityUri|/Alarms/Dialogs}}
+
{{CapabilityUri|/Condition/Dialogs}}
 
+
 
'''Description'''
 
'''Description'''
<br>An extension of the Alarm model where a server can interact with a client. The client does not need to be programmed to the specific action of the Server, but can just be configured to use the standard information provided by this Alarm 7 condition type.
+
<br>A specialized Condition model where a Server can interact with a User. The information flow starts with the Server sending a message (a dialog prompt) and a number of possible responses. The User selects one of these responses which the Client then sends to the Server.
  
 
'''Usage Considerations'''
 
'''Usage Considerations'''
<br>They are typically used when a Server has entered some state that requires intervention by a Client. For example, a Server monitoring a paper machine indicates that a roll of paper has been wound and is ready for inspection. The Server would activate a Dialog Condition indicating to the user that an inspection is required. Once the inspection has taken place the user responds by informing the Server of an accepted or unaccepted inspection allowing the process to continue. All accomplished via a standard Dialog.
+
<br>Dialogs are typically used in states that require intervention by a Client. For example, a Server monitoring a paper machine indicates that a roll of paper has been wound and is ready for inspection. The Server would activate a Dialog Condition indicating to the user that an inspection is required. Once the inspection has taken place the user responds by informing the Server of an accepted or unaccepted inspection allowing the process to continue.
 
+
{{uaConformance|TBD <
{{uaConformance|TBD <!-- Client -->|
+
[http://opcfoundation.org/UA-Profile/Client/ACDialog '''Client dialog support''']
TBD <!-- Server -->
+
|
<!-- Example
+
[http://opcfoundation.org/UA-Profile/Server/ACDialog '''Server uses dialogs''']
* [http://opcfoundation.org/UA-Profile/Server/GlobalCertificateManagement '''Global Certificate Management Server Profile''']
+
* [http://opcfoundation.org/UA-Profile/Client/GlobalCertificateManagement '''Global Certificate Management Client Profile''']
+
-->
+
 
}}
 
}}

Revision as of 08:56, 13 February 2015

URN:          https://opcfoundation.org/wiki/index.php/Condition/Dialogs

Description
A specialized Condition model where a Server can interact with a User. The information flow starts with the Server sending a message (a dialog prompt) and a number of possible responses. The User selects one of these responses which the Client then sends to the Server.

Usage Considerations
Dialogs are typically used in states that require intervention by a Client. For example, a Server monitoring a paper machine indicates that a roll of paper has been wound and is ready for inspection. The Server would activate a Dialog Condition indicating to the user that an inspection is required. Once the inspection has taken place the user responds by informing the Server of an accepted or unaccepted inspection allowing the process to continue.


Conformance Testing

Client Server

TBD < Client dialog support

Server uses dialogs