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.

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

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

Change as suggested

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

Changed according to suggestion

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?

Update the text to reflect the IDL

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

;

Change as suggested

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

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

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.

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

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

see above, rejected

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

Change as suggested

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

Add the exception

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

Change as suggested

Description of simple_io_home is missing in section 4.2.2.2

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

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() ).

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

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

Change as suggested

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."

Changed according to suggestion

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"

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

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"

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

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);

Changed according to suggestion

OnEvent shalle be OneEvent – rename it

Rename OnEvent to Event and OnEvents to Events

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.

see above

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.

see above

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.

Add documentation describing how a flat namespace is implemented.

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

Rename to ConditionEvent.event_id

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

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

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.

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

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

see above

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.

Describe that the properties relate to the Reason.

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

rejected, see above

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.

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

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

Duplicate 4779

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>

see above

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

see above

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?

rejected, see above

Replace ULongLong with CORBA unsigned long long

Make sure to use the latest version of DAFIdentifiers and DAFDescriptions

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.

see above

Add description of usecase in the specification

Add description of use case in the specification.

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

Describe how the mapping from DAIS to OPC is made.

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

Add a filter specification language.

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

see above

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

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

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

see above

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

see above

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;

const OPCQuality EXQ_SOURCE_NONE = 0x0000;

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.

see above

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

Improve description of alarms and events section 5.

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

Suggestion; const Error ERROR_DAISOK = 0

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

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

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().

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

Add it in DAISNode.idl

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

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

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

Replace the SimpleValue string data type with wstring datatype.

Do note use widestrings. Use UTF-8

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.

see above

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

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

Change to READ_AND_WRITEABLE

Change to READ_AND_WRITEABLE

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

Remove Abstract from interface definitions

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

see above

The schema ResourceID is called node. Rename to schema

Rename to schema.

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

see above

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

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