View Issue Details

IDProjectCategoryView StatusLast Update
001028710000-007: ProfilesSpecpublic2025-06-10 15:26
ReporterPaul Hunkar Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.05 RC2 
Target Version1.05.06Fixed in Version1.05.05 RC2 
Summary0010287: Optional twostaeVariable Properties missing ConformanceUnits
Description

The twostateVariable type has the following optional properties

  • TransitionTime specifies the time when the current state was entered.
  • EffectiveTransitionTime specifies the time when the current state or one of its sub states was entered. If, for example, a LevelAlarm is active and – while active – switches several times between High and HighHigh, then the TransitionTime stays at the point in time where the Alarm became active whereas the EffectiveTransitionTime changes with each shift of a sub state.
  • EffectiveDisplayName from the StateVariableType is used if a state has sub states. It contains a human readable name for the current state after taking the state of any SubStateMachines in account. As an example, the EffectiveDisplayName of the EnabledState could contain “Active/HighHigh” to specify that the Condition is active and has exceeded the HighHigh limit.

The alarm model utilise TwoStateVariables in a number of places, and for all place where it make senses additional conformanceUnits should be defined indicate that the specific twoStatevariable (say Enable) expose the optional property All three may not be required in all cases (i.e. if the given state does not have SubStates defined ten it might not need effectiveTRansitionTime or EffectiveDisplayName.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Paul Hunkar

2025-05-25 02:56

developer   ~0022772

CReated new conformance units for optional properties and associated them with the Facets that reference the related variables

Jim Luth

2025-06-10 15:26

administrator   ~0022999

Agreed to rewording for each CU in the meeting and agreed to mark them "Release" in the database.

Issue History

Date Modified Username Field Change
2025-04-19 05:19 Paul Hunkar New Issue
2025-05-13 16:15 Jim Luth Assigned To => Paul Hunkar
2025-05-13 16:15 Jim Luth Status new => assigned
2025-05-25 02:56 Paul Hunkar Status assigned => resolved
2025-05-25 02:56 Paul Hunkar Resolution open => fixed
2025-05-25 02:56 Paul Hunkar Fixed in Version => 1.05.05 RC2
2025-05-25 02:56 Paul Hunkar Note Added: 0022772
2025-06-10 15:26 Jim Luth Status resolved => closed
2025-06-10 15:26 Jim Luth Note Added: 0022999