View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000803910000-005: Information ModelSpecpublic2022-06-10 15:102023-07-24 07:08
ReporterMohit Agarwal Assigned ToJeff Harding  
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.01 
Target Version1.05.02 RC1Fixed in Version1.05.02 
Summary0008039: Support ConditionClassId and ConditionSubClassId feature for BaseEventType
Description

Hello,

We have a very useful mechanism using ConditionClassId, ConditionClassName and ConditionSubClassId in the ConditionType model. While defining events model for OPC 40451-1 for Tightening Systems, we wanted to reuse the similar filtering mechanism for simple event types since this concept is applicable even for various types of events which DOES NOT need any states or acknowledgement and helps the end user applications in filtering the events based on the classification.

Proposal:
Add the similar properties for ConditionClassId, ConditionClassName, ConditionSubClassId and ConditionSubClassNames as part of Event model in BaseEventType.
It can be added as a separate interface and both BaseEventType and ConditionType can implement it or move those properties to BaseEventType which will ensure that both the options are available.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0008050 closedPaul Hunkar 10000-009: Alarms and Conditions Support ConditionClassId and ConditionSubClassId feature for BaseEventType 
related to 0009052 closedRandy Armstrong NodeSets, XSDs and Generated Code NodeSet does not match specification 

Activities

Mohit Agarwal

2022-06-10 15:16

reporter   ~0016818

This topic was discussed with Wolfgang Mahnke and based on the discussion we agreed that multiple domains and specifications can utilize this feature.

Jim Luth

2022-06-14 16:15

administrator   ~0016841

Agreed to move the 4 properties to the BaseEventType in Part 5 (as optional). We will leave the ConditionClassType stuff in Part 9 with a forward reference from Part 5.

Jeff Harding

2022-06-20 14:57

developer   ~0016913

The ConditionClassId, ConditionClassName, ConditionSubClassId, and ConditionSubClassName Properties, originating from OPC 10000-9, have now been generalized to also apply to Events. To preserve backward compatibility the names have been preserved.

This issue should be reviewed together with issue 8050 for Part 9.

Jim Luth

2022-06-22 12:36

administrator   ~0016980

Agreed to changes edited in Munich F2F.

Issue History

Date Modified Username Field Change
2022-06-10 15:10 Mohit Agarwal New Issue
2022-06-10 15:16 Mohit Agarwal Note Added: 0016818
2022-06-14 16:15 Jim Luth Note Added: 0016841
2022-06-14 16:16 Jim Luth Target Version => 1.05.02 RC1
2022-06-14 16:17 Jim Luth Issue cloned: 0008050
2022-06-14 16:17 Jim Luth Relationship added related to 0008050
2022-06-14 16:18 Jim Luth Assigned To => Jeff Harding
2022-06-14 16:18 Jim Luth Status new => assigned
2022-06-20 14:57 Jeff Harding Status assigned => resolved
2022-06-20 14:57 Jeff Harding Resolution open => fixed
2022-06-20 14:57 Jeff Harding Fixed in Version => 1.05.02
2022-06-20 14:57 Jeff Harding Note Added: 0016913
2022-06-22 12:30 Jim Luth Issue cloned: 0008068
2022-06-22 12:36 Jim Luth Status resolved => closed
2022-06-22 12:36 Jim Luth Note Added: 0016980
2023-07-24 07:08 Randy Armstrong Relationship added related to 0009052