Search
6 result(s) for ConditionTypes
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions4.2 Conditionsmany industries. It is expected that vendors or other standardisation groups will define additional ConditionTypes deriving from the common base types defined in this part. The ConditionTypes supported
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions4.7 DialogsDialogs Dialogs are ConditionTypes used by a Server to request user input. They are typically used when a Server has entered some state that requires intervention by a Client
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.5.2 ConditionTypeConditionType The ConditionType defines all general characteristics of a Condition . All other ConditionTypes derive from it. It is formally defined in Table 8 and Table 9 . The False state
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditionssystems where Conditions are not available as instances, the ConditionSource can reference the ConditionTypes instead. This is illustrated with the example in Figure B.6 . Figure B.6 - HasCondition reference
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics12.1 OverviewConditionType for maintenance activities. Companion specifications or vendors might define their own 0: ConditionTypes for specific types of maintenance activities. It is recommended to create those as subtypes ... information. This specification defines an interface (see 12.2 ) that should be implemented by all ConditionTypes used as maintenance activities. For a recurring maintenance activity it is recommended
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management BasicsIMaintenanceEventType The IMaintenanceEventType is an interface and should be applied to 0: ConditionTypes . It is formally defined in Table 35 . Table 35 - IMaintenanceEventType Definition Attribute Value BrowseName IMaintenanceEventType IsAbstract True