Data Acquisition from Industrial Systems Avatar
  1. OMG Specification

Data Acquisition from Industrial Systems — Closed Issues

  • Acronym: DAIS
  • Issues Count: 59
  • Description: Issues resolved by a task force and approved by Board
Open Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
DAIS11-16 Meaning of A&E Reason DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-15 Data type for VT_EMPTY DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-7 Bad parameters exception DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-6 DAIS::DataAccess::GroupEntry::Manager::create_entries() DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-14 The SimpleIO need an own error report struct DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-13 Change user quality from short to long DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-17 Improved A&E error reporting on enable/disable by area and source DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-10 find_by_type to take a node sequence DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-12 OPC_QUALITY_EGU_EXCEEDED twice in table DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-9 Missing exception InvalidFilter DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-11 ItemHome in description shall be just Home DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-8 Missing description of simple_io_home DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-18 A&E Keep alive supervision DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-19 Description of validate_entries DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-5 DAIS::DataAccess::Item::Home::get_ids() DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-2 datatype TypeID. But CORBA 3 was define keyword - typeid. DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-3 clash with keyword "home" in CORBA spec DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-4 DAIS::DataAccess::Item::ItemHome::find_each() DAIS 1.0 DAIS 1.1 Resolved closed
DAIS-28 OnEvent shalle be OneEvent -- rename it DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-27 Improved mapping between OPC and DAIS DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-32 Support HDAIS in DAIS DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-31 Improve documentation on views and flat data access DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-30 ConditionEvent.cookie is a bad name DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-29 Ambigous identification of items DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-18 Server knowledge of leaf Nodes DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-17 Group::Manager::clone_to_public return Manager DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-22 Description of the property_values member DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-21 Relation to 61970 need revision DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-16 validate_entries() return unnessesary information DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-15 Group entry management is inefficient DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-26 Blob data type DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-25 Enabled/disabled conditions DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-20 The views are reported as a sequence of strings DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-19 Replace ULongLong with CORBA unsigned long long DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-24 Event history DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-23 No usecase for Alarms & Events DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-38 Describe mapping to OPC DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-37 Filter specification language DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-36 Server authority check DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-35 Add filter to Node::Home DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-40 Imrove description of condition_logic in A&E DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-39 OPC DA version 3 DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-34 Add support for no data source DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-33 Improved data type compatibility DAIS OPC DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-41 The difference between alarms and events is unclear DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-3 Duplicate use of ERROR_SUCCESS DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-2 Loss of data due to failover DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-12 Type interface does not use the Node pattern DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-11 The member Node.description is lacking DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-7 The ItemError struct cant report detailed errors DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-6 Support for chinese tokens needed DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-5 Quality codes DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-4 Separate Data Access and A&E servers DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-9 Spelling error READ_AND_WRITABLE DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-8 Abstract interface spoil interoperability DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-14 Server internal errors DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-13 Misleading parameter name in find_by_schema() DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-10 Struct sizes on Risc machines DAIS 1.0b1 DAIS 1.0 Resolved closed
DAIS-1 Management of events appearing in a scan cycle DAIS 1.0b1 DAIS 1.0 Resolved closed

Issues Descriptions

Meaning of A&E Reason

  • Key: DAIS11-16
  • Legacy Issue Number: 7086
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The Alarms & Events Reason is claimed to describe the reason behind an event. Reason is mapped to OPC EventCategory. OPC EventCategory is more intended to describe the contents of an event rather than the reason causing the event. Investigate if this shall cause a name change of Reason to EventCategory. This will simplify mapping DAIS A&E to OPC A&E.

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested in section Changes to formal/02-11-07

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Data type for VT_EMPTY

  • Key: DAIS11-15
  • Legacy Issue Number: 7084
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    A new datatype that corresponds to OPC VT_EMPTY is needed to indicate that the server shall use the native data type. SimpleValueType needs a UNSPECIFIED_TYPE

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Bad parameters exception

  • Key: DAIS11-7
  • Legacy Issue Number: 7076
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Bad parameters are signaled with the error code E_INVALIDARG. The corresponding OMG exception is BAD_PARAM. Remove InvalidStateSpecified in E&A Subscription and use BAD_PARAM instead

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Changed according to suggestion

  • Updated: Fri, 6 Mar 2015 20:58 GMT

DAIS::DataAccess::GroupEntry::Manager::create_entries()

  • Key: DAIS11-6
  • Legacy Issue Number: 6336
  • Status: closed  
  • Source: Technical University, Sofia, Bulgaria ( Lubomir Chorbadjiev)
  • Summary:

    When describing: DAIS::DataAccess::GroupEntry::Manager::create_entries() last paragraph on page 4-38 says:

    "both item and pathname specified ->..."

    I think that there is no way to specify both itemID and pathname in this method. Paramethers passed in this method are:

    DAIS::DataAccess::GroupEntry::Description

    where for item identification we use union, described on page 3-3,3-6:

    DAIS::ServerItemIdentification

    So, how we can specify both item ID and pathname?

  • Reported: DAIS 1.0 — Fri, 17 Oct 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Update the text to reflect the IDL

  • Updated: Fri, 6 Mar 2015 20:58 GMT

The SimpleIO need an own error report struct

  • Key: DAIS11-14
  • Legacy Issue Number: 7083
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The SimpleIO need an own error report struct as it can't use the handles in the ItemError struct. Suggestion
    struct ItemError

    { Error err; ServerItemIdentification id; string reason; }

    ;

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Change user quality from short to long

  • Key: DAIS11-13
  • Legacy Issue Number: 7082
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    User quality is currently a unsigned short. This is insufficient and shall be increased to a long

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Refer to dtc/2004-10-05 section 3.1.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Improved A&E error reporting on enable/disable by area and source

  • Key: DAIS11-17
  • Legacy Issue Number: 7137
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The methods enable_conditions() and disable_conditions() at the
    Source::Home and Area::Home does not return error codes for Sources or
    Areas that fails.

  • Reported: DAIS 1.0 — Wed, 10 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Refer to dtc/2004-10-05 sections 5.2.5.2 and 5.2.6.2

  • Updated: Fri, 6 Mar 2015 20:58 GMT

find_by_type to take a node sequence

  • Key: DAIS11-10
  • Legacy Issue Number: 7079
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    find_by_type currently takes a single root node as input. By changing this to a sequence it is possible to use a set of nodes from a previous call as input to a subsequent call

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    see above, rejected

  • Updated: Fri, 6 Mar 2015 20:58 GMT

OPC_QUALITY_EGU_EXCEEDED twice in table

  • Key: DAIS11-12
  • Legacy Issue Number: 7081
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    OPC_QUALITY_EGU_EXCEEDED twice in table describing detailed quality flags for uncertain quality. Remove one entry.

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Missing exception InvalidFilter

  • Key: DAIS11-9
  • Legacy Issue Number: 7078
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Exception InvalidFilter is missing in find_by_parent() and find_by_type() in section 3.1.7.2.

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Add the exception

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ItemHome in description shall be just Home

  • Key: DAIS11-11
  • Legacy Issue Number: 7080
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    In description of Item::Home the interface is called ItemHome, shall be just Home

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Missing description of simple_io_home

  • Key: DAIS11-8
  • Legacy Issue Number: 7077
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Description of simple_io_home is missing in section 4.2.2.2

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    rejected The description is not missing. This is not an issue.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

A&E Keep alive supervision

  • Key: DAIS11-18
  • Legacy Issue Number: 7138
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    When an A&E subscription has a non-zero keep-alive time, the server will
    insure that the client receives a callback on the subscription minimally at
    rate indicated by the keep-alive time, even when there are no new events to
    report. By providing callbacks at a minimum known frequency, the client can
    be assured of the health of the server and subscription without resorting
    to "pinging the server" (the common practice of making periodic calls to a
    server method, e.g. IOPCEventServer::GetStatus() ).

  • Reported: DAIS 1.0 — Wed, 10 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Add a new member keep_alive_time in the AlarmsAndEvents::Subscription::State struct

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Description of validate_entries

  • Key: DAIS11-19
  • Legacy Issue Number: 7085
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The DAIS specification states that validate_entries (on DAISGroupEntry) is: "Used to check if Descriptions a client holds are still valid without effecting the existing group." The OPC specification of ValidateItems (on IOPCItemMgt) states: "Determines if an item is valid (could it be added without error). Also returns information about the item such as canonical datatype. Does not affect the group in any way."
    Update the specification to reflect the behavior according to the OPC specification

  • Reported: DAIS 1.0 — Sat, 20 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

DAIS::DataAccess::Item::Home::get_ids()

  • Key: DAIS11-5
  • Legacy Issue Number: 6335
  • Status: closed  
  • Source: Technical University, Sofia, Bulgaria ( Lubomir Chorbadjiev)
  • Summary:

    When describing DAIS::DataAccess::Item::Home::get_ids() the specification says:

    "Translate a sequence of pathnames to the corresponding sequence of >>node<< identifications. If a pathname fails to translate to >>node<< identification..."

    I suppose that word >>node<< should be replaced with >>item<< because: 1) the IDL definition for this method is: ItemIDs get_ids(in Strings pathnames); 2) description of return values on page 4-22 says: "return The corresponding sequence of >>item<< identifications."

  • Reported: DAIS 1.0 — Fri, 17 Oct 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Changed according to suggestion

  • Updated: Fri, 6 Mar 2015 20:58 GMT

datatype TypeID. But CORBA 3 was define keyword - typeid.

  • Key: DAIS11-2
  • Legacy Issue Number: 6064
  • Status: closed  
  • Source: RNPK ( Eugeny P. Florov)
  • Summary:

    In this idl-file is defined datatype TypeID. But CORBA 3 was define keyword - typeid.

    In result idl compiler write:

    tao_idl: "DAISCommon.idl", line 15: spelling differs from IDL keyword only in case: "TypeID" tao_idl: "DAISCommon.idl", line 20: spelling differs from IDL keyword only in case: "TypeID"

  • Reported: DAIS 1.0 — Sun, 24 Aug 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    To avoid keyword collision in CORBA 3 the existing type ResourceID replaces TypeID

  • Updated: Fri, 6 Mar 2015 20:58 GMT

clash with keyword "home" in CORBA spec

  • Key: DAIS11-3
  • Legacy Issue Number: 6320
  • Status: closed  
  • Source: KU Leuven ( Panagiotis Issaris)
  • Summary:

    Regarding the specification "IDL for Data Acquisition from Industrial Systems": The IDL files define interfaces named Home, which clash with the keyword "home" of the CORBA 3 specification.

    The TAO IDL compiler reports: tao_idl: "DAISNode.idl", line 33: spelling differs from IDL keyword only in case: "Home"

  • Reported: DAIS 1.0 — Mon, 13 Oct 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    "Home" interfaces are renamed to "IHome" the distinguish from the keyword Home

  • Updated: Fri, 6 Mar 2015 20:58 GMT

DAIS::DataAccess::Item::ItemHome::find_each()

  • Key: DAIS11-4
  • Legacy Issue Number: 6334
  • Status: closed  
  • Source: Technical University, Sofia, Bulgaria ( Lubomir Chorbadjiev)
  • Summary:

    When describing what DAIS::DataAccess::Item::ItemHome::find_each() returns, the specification says:

    "return: An >>iterator<< holding the item descriptions"

    I suppose that word >>iterator<< should be replaced with >>sequence<< since the IDL definition is:

    Descriptions find_each(in ItemIDs items) raises (UnknownItemID);

  • Reported: DAIS 1.0 — Fri, 17 Oct 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Changed according to suggestion

  • Updated: Fri, 6 Mar 2015 20:58 GMT

OnEvent shalle be OneEvent -- rename it

  • Key: DAIS-28
  • Legacy Issue Number: 4780
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    OnEvent shalle be OneEvent – rename it

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Rename OnEvent to Event and OnEvents to Events

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Improved mapping between OPC and DAIS

  • Key: DAIS-27
  • Legacy Issue Number: 4779
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The following improvemnts are suggested- the COM iterator requires new methods- introduce server handles to enable simple bridging to OPC, improve perfromace and memory consumption in server.- introduce the OPC blob to enable simple bridging to OPC, improve perfromace and memory consumption in server. Add methods reset() and clone() to the Iterator.Replace ItemID with OPCHandle in all methods but create and validate entries.Add the blob.For more details se discussion below.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Support HDAIS in DAIS

  • Key: DAIS-32
  • Legacy Issue Number: 5256
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The ServerItemIdentification union will be used also by HDAIS.The Quality for HDAIS is an unsigned long. Move the ServerItemIdentification union from DAISGroupEntry.idl to DAISCommon.idlTo make a transparent DAIS/HDAIS to OPC bridge the simplest solution is to extend the DAIS quality from a short to a long.

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Improve documentation on views and flat data access

  • Key: DAIS-31
  • Legacy Issue Number: 5255
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    A DAIS server may support multiple hierarchical organizations. Each hierarchy will then have it's own path names that are valid only within that view.Currently Item::find_by_type() and Node::find_by_type support retreival of flattened out items. Make this clearer in the spec. Add documentation describing how a flat namespace is implemented.

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Add documentation describing how a flat namespace is implemented.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ConditionEvent.cookie is a bad name

  • Key: DAIS-30
  • Legacy Issue Number: 5254
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    ConditionEvent.cookie is a bad nameas it does not say anything about the meaning. Rename to ConditionEvent.event_id

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Rename to ConditionEvent.event_id

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Ambigous identification of items

  • Key: DAIS-29
  • Legacy Issue Number: 4781
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Items are identified by ItemID and pathname in the GroupEntry::Description. It is not clear wich the client shall use and indicate wich of them that are valid to the server. Replace the two members by a union so that only one of them can be specified

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Replace the two members by a union so that only one of them can be specified.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Server knowledge of leaf Nodes

  • Key: DAIS-18
  • Legacy Issue Number: 4770
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    A server knows when leaf nodes has been reached. A possible performance optimisation is to add information on this in the Node::Description struct. Add a short leaf_node member telling the number of childs.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Add a short leaf_node member telling the number of child's.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Group::Manager::clone_to_public return Manager

  • Key: DAIS-17
  • Legacy Issue Number: 4769
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The public group is not allowed to be manipulated and hence shall not be returned. Group::Manager::clone_to_public shall return a Group::PublicGroupDescription. Implemented in DAISGroup.idl

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Description of the property_values member

  • Key: DAIS-22
  • Legacy Issue Number: 4774
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The SourceCondition::Description.property_values and IO::SimpleEvent.property_values documentation must be improved. It is unclear what instance the properties relate to. Describe that the properties relate to the Reason. Do this be making the Reason a Type, i.e. let Reason inherit Type and remove the association between Property and Reason.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Describe that the properties relate to the Reason.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Relation to 61970 need revision

  • Key: DAIS-21
  • Legacy Issue Number: 4773
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Change section 2.5 in the specification and describe the mapping in IEC 61970-403 and -404.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    rejected, see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

validate_entries() return unnessesary information

  • Key: DAIS-16
  • Legacy Issue Number: 4768
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The validate_entries() return all OK entries. A client is interested mainly in the erronous ones and changes to the blob. Add an in parameter telling if the client only want the changed or updated items reported, i.e. the validate_entries() return an empty sequence for the OK entries.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    The parameter is not needed, as the blob will not be re-introduced. No changes.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Group entry management is inefficient

  • Key: DAIS-15
  • Legacy Issue Number: 4767
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    For large groups the memory consumption and LAN traffic is unnessesarily high because the current structs convey lots of unused data.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Duplicate 4779

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Blob data type

  • Key: DAIS-26
  • Legacy Issue Number: 4778
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    For the HDAIS RFP a requirement to have support for blob data has emerged. Add a blob data type and include it in the SimpleValue. The blob shall have the members- type specifier (.avi, .jpg, .gif, .wav etc.)- sequence<octet>

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Enabled/disabled conditions

  • Key: DAIS-25
  • Legacy Issue Number: 4777
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The methods act on all Conditions not a single. Rename Source::Home::enable_condition to Source::Home::enable_conditions

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

The views are reported as a sequence of strings

  • Key: DAIS-20
  • Legacy Issue Number: 4772
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    in Server::find_views(). This does not follow the pattern to use a struct to report information on objects. Replace the string with a sequence of structs with a name and a ResourceID?

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    rejected, see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Replace ULongLong with CORBA unsigned long long

  • Key: DAIS-19
  • Legacy Issue Number: 4771
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Replace ULongLong with CORBA unsigned long long

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Make sure to use the latest version of DAFIdentifiers and DAFDescriptions

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Event history

  • Key: DAIS-24
  • Legacy Issue Number: 4776
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    It is not clear from the specification how the history of events is managed, e.g. how the server store events and make them available for future access.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

No usecase for Alarms & Events

  • Key: DAIS-23
  • Legacy Issue Number: 4775
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Add description of usecase in the specification

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Add description of use case in the specification.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Describe mapping to OPC

  • Key: DAIS-38
  • Legacy Issue Number: 5262
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Mapping to OPCThere is a need to describe how DAIS maps to OPC. Describe how the mapping from DAIS to OPC is made.

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Describe how the mapping from DAIS to OPC is made.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Filter specification language

  • Key: DAIS-37
  • Legacy Issue Number: 5261
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Filter specification languageThe language for specifying filters is missing. Add a filter specification language.

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Add a filter specification language.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Server authority check

  • Key: DAIS-36
  • Legacy Issue Number: 5260
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Server authority checkA DAIS server need to check the user authority when a read, write or acknowledge operation is made. A server shall use middleware and/or operating system services to get information about the user. Add a discussion of this to the DAIS spec and the relation to the OPC security spec

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add filter to Node::Home

  • Key: DAIS-35
  • Legacy Issue Number: 5259
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Add filter to Node::HomeOPC support to do filtering on branch nodes for Data Acccess (DA). This is useful for finding nodes with pathnames matching the filter criteria pattern. Add the filter_criteria string to find_by_type and find_by_parent

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Add the filter_criteria string to find_by_type() and find_by_parent()

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Imrove description of condition_logic in A&E

  • Key: DAIS-40
  • Legacy Issue Number: 5264
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Imrove description of condition_logic in A&E. Investigate if the currently suggested grammar can be replaced by the use of a subset from the XPath specification

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

OPC DA version 3

  • Key: DAIS-39
  • Legacy Issue Number: 5263
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    OPC DA version 3There is a new version 3 of OPC DA. Investigate how this effect the DAIS DA can be updated to accomodate OPC DA 3.0. Provide an investigation on this one

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add support for no data source

  • Key: DAIS-34
  • Legacy Issue Number: 5258
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Add support for no data sourceData points that have no data source may exist. Add a new source defiontion to tell this. const OPCQuality EXQ_SOURCE_NONE = 0x0000;

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    const OPCQuality EXQ_SOURCE_NONE = 0x0000;

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Improved data type compatibility DAIS OPC

  • Key: DAIS-33
  • Legacy Issue Number: 5257
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Improved data type compatibility DAIS OPCOPC support the data type VARIANT. A VARIANT can hold arrays simple data types as well as anys. OPC implementations use arrays of simple types but (probably) not anys. Support sequences of simple values in a SimpleValue. This change shall be implemented in the DAF specification.Descriptive text shall be added to the DAF spec.

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

The difference between alarms and events is unclear

  • Key: DAIS-41
  • Legacy Issue Number: 5265
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The difference between alarms and events is unclear. Improve description of alarms and events section 5.

  • Reported: DAIS 1.0b1 — Thu, 2 May 2002 04:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Improve description of alarms and events section 5.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Duplicate use of ERROR_SUCCESS

  • Key: DAIS-3
  • Legacy Issue Number: 4755
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    const Error ERROR_SUCCESS = 0; is already in use by Microsoft. Name has to be replaced

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Suggestion; const Error ERROR_DAISOK = 0

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Loss of data due to failover

  • Key: DAIS-2
  • Legacy Issue Number: 4754
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    A descrete value may change multiple times within a scan cycle before it is reported to clients. Clients may want to get all the changes but still at a low scan cycle to optimize performance

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    This function is supported by HDAIS. Use HDAIS when needed. No changes to DAIS specification.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Type interface does not use the Node pattern

  • Key: DAIS-12
  • Legacy Issue Number: 4764
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The type herarchy is currently implemented as a reference to childs by the Type::Description.aggregated_types member. In all other browse interfaces it is implemented as a single parent reference and the method find_by_parent().

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    No action because the description struct is different to the other APIs.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

The member Node.description is lacking

  • Key: DAIS-11
  • Legacy Issue Number: 4763
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Add it in DAISNode.idl

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Add descriptive text member in DAIS::Node::Description.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

The ItemError struct cant report detailed errors

  • Key: DAIS-7
  • Legacy Issue Number: 4759
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Extend the ItemError struct with a reason string in the same way as for exceptions.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    There is no member in the ItemError struct to report a description of the error reason

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Support for chinese tokens needed

  • Key: DAIS-6
  • Legacy Issue Number: 4758
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Replace the SimpleValue string data type with wstring datatype.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Do note use widestrings. Use UTF-8

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Quality codes

  • Key: DAIS-5
  • Legacy Issue Number: 4757
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Currently there is no space for user specific quality codes.The mapping between OPC and IEC61850 quality codes shall be made explicit in the DAIS spec.

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Separate Data Access and A&E servers

  • Key: DAIS-4
  • Legacy Issue Number: 4756
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    How to implement only a Data Access server without A&E?

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Keep the current solution and add the HDAIS server by sub classing the DAIS server.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Spelling error READ_AND_WRITABLE

  • Key: DAIS-9
  • Legacy Issue Number: 4761
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Change to READ_AND_WRITEABLE

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Change to READ_AND_WRITEABLE

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Abstract interface spoil interoperability

  • Key: DAIS-8
  • Legacy Issue Number: 4760
  • Status: closed  
  • Source: Cycle Software ( Jeff Robbins)
  • Summary:

    Some ORBs (e.g. TAU) does not support the keword "abstract".

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Remove Abstract from interface definitions

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Server internal errors

  • Key: DAIS-14
  • Legacy Issue Number: 4766
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    It is suggested to have a new error code for reporting of internal server errorsconst Error ERROR_INTERNAL_SERVER = 8;

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Misleading parameter name in find_by_schema()

  • Key: DAIS-13
  • Legacy Issue Number: 4765
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The schema ResourceID is called node. Rename to schema

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    Rename to schema.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Struct sizes on Risc machines

  • Key: DAIS-10
  • Legacy Issue Number: 4762
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    If struct members of different sizes are mixed memory usage on Risc machines will increase due to alignment padding. Put all members of the same type together in the structs. Suggested orderingsIO::ItemStateSimpleValue, ItemID, DateTime, Quality, ClientHandleGroupEntry::DescriptionItemID, ClientHandle, SimpleValueType, active, pathname, access_path

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Management of events appearing in a scan cycle

  • Key: DAIS-1
  • Legacy Issue Number: 4752
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    A descrete value may change multiple times within a scan cycle before it is reported to clients. Clients may want to get all the changes but still at a low scan cycle to optimize performance

  • Reported: DAIS 1.0b1 — Fri, 14 Dec 2001 05:00 GMT
  • Disposition: Resolved — DAIS 1.0
  • Disposition Summary:

    This function is supported by HDAIS. Use HDAIS when needed. No changes to DAIS specification.

  • Updated: Fri, 6 Mar 2015 20:58 GMT