View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000277710000-007: ProfilesSpecpublic2014-04-10 20:582015-05-26 16:18
ReporterNathan PocockAssigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version1.03Fixed in Version1.03 
Summary0002777: Base Information Underlying System - clarifications needed
Description

While reviewing test-cases for the "Base Information Underlying System" conformance unit we identified a number of questions that we need guidance on:

#1 - What constitutes an 'underlying system'? Does this mean:
(a) exclusively an OPC UA Server of some description
(b) could it refer to a PLC/Device?
(c) both of the above?

#2 - The description specifically mentions the SystemStatusChangeEventType, but if answer to #1 above includes option (b) then would the DeviceFailureEventType be applicable to this conformance unit too?

#3 - Which conformance unit would the DeviceFailureEventType events be applicable for?

#4 - Should a gateway server have its own profile? we struggled with this, but what should a gateway server support? what if it is intended for an embedded device (limited resources)? should there be conformance units based on the # of 'underlying systems'? what about an information model to describe the setup? etc.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0002781 closeduser49 10000-001: Concepts Base Information Underlying System - clarifications needed 

Activities

Jim Luth

2014-04-15 17:41

administrator   ~0005337

Definition for "underlying system" will be added to Part 1.

Need additional CU for DeviceFailureEventType (are there any other missing?)

For now we don't see much value in adding gateway device Profile(s).

Karl Deiretsbacher

2014-08-19 15:33

developer   ~0005439

proposed for v1.03

Paul Hunkar

2015-05-06 15:06

developer   ~0006050

1) Underlying system have been defined in part 1 and includes all of the possible definition listed
2) additional conformance units have been added for device failure (A device failure is for a specific device, which may be part of an underlying system, while the System failure mean the entire underlying system is down or unavailable (my be communication problem).
3) device failure added - but need to discuss how it should be added to the client (what facet - also discovered issue with client facet related to events)
4) propose moving Agregate to a seperate mantis issue 9if one oes not already exist)

Karl Deiretsbacher

2015-05-26 16:18

developer   ~0006092

fixed in draft 12

Jim Luth

2015-05-26 16:18

administrator   ~0006093

Agreed to changes in telecon.

Issue History

Date Modified Username Field Change
2014-04-10 20:58 Nathan Pocock New Issue
2014-04-15 17:33 Jim Luth Issue cloned: 0002781
2014-04-15 17:33 Jim Luth Relationship added related to 0002781
2014-04-15 17:36 Jim Luth Status new => assigned
2014-04-15 17:36 Jim Luth Assigned To => Paul Hunkar
2014-04-15 17:41 Jim Luth Note Added: 0005337
2014-08-19 15:33 Karl Deiretsbacher Note Added: 0005439
2014-08-19 15:33 Karl Deiretsbacher Category (No Category) => Spec
2014-08-19 15:33 Karl Deiretsbacher Target Version => 1.03
2015-05-05 16:37 Jim Luth Target Version 1.03 => 1.04
2015-05-06 15:06 Paul Hunkar Note Added: 0006050
2015-05-19 16:10 Jim Luth Target Version 1.04 => 1.03
2015-05-26 16:18 Karl Deiretsbacher Note Added: 0006092
2015-05-26 16:18 Karl Deiretsbacher Status assigned => resolved
2015-05-26 16:18 Karl Deiretsbacher Fixed in Version => 1.03
2015-05-26 16:18 Karl Deiretsbacher Resolution open => fixed
2015-05-26 16:18 Jim Luth Note Added: 0006093
2015-05-26 16:18 Jim Luth Status resolved => closed