(originally reported by Richard Smith - BAE Systems)

(Proivde_Health_State, page 194, para above table 7.185) contains the following description:

“Reason for health state
Each reported health state other than AVAILABLE is accompanied by the reason(s) for that health. In this way the CMS may for instance derive that although the technical state of the subsystem is STANDBY (and NOT AVAILABLE for that reason), there are also faults that would prevent the service to become AVAILABLE when the technical state would be switched to ONLINE.”

This appears perfectly reasonable to me, although it is then followed immediately by:
“Pre-condition: Subsystem technical state The subsystem is in technical state ONLINE or READY.”

This appears to imply, to me, that the report service health is only applicable to the ONLINE or READY technical state, even though the para above suggests it would be of use in the STANDBY state!

Include STANDBY as precondition to Provide_Health_State_CMS

Include STANDBY as precondition to Provide_Health_State_CMS

Within Subsystem_Control.idl the struct service_health_type (line 327) has the member health_state (line 330) declared with type health_state_reason_type. The specification states it should be health_state_type. Believe this is an error?

service_health_type struct is correct in 3.0 beta

service_health_type struct is correct in 3.0 beta and the health_state attribute has been changed to type health_state_type already.

The copyright holders shown at the beginning of the document should include not only the original submitters but also the members of all the subsequent FTFs/RTFs. It seems this list has not been maintained as the following companies are missing:

General Dynamics, Northrop Grumman, SimVentions, Microfocus, Real-Time Innovations,

Copyright holders already updated for 3.0 beta

Copyright holders already updated for 3.0 beta

The IDL files have the wrong interface version in them at the top of the file.

Version has been removed from IDL files in later submissions

Version has been removed from IDL files in later submissions

The description of the interface states that
"It is the CMS's responsibility to initiate the determination of initial state by making a request for information to the subsystem."
However, there is no operation defined to request information from the subsystem.
(Note: the protocol was probably simplified in working towards the v1.0 submission without revising the overall description of this particular interface).

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

there are several instances where the IDL generated from the XMI has String (capitalised) rather than in lower case which causes an error in some DDS IDL compilers. These should be generated as lower case in the following files:
Manage_Network_Participation.idl
Plot_Reporting.idl
Track_Reporting.idl
Label_Tracks.idl

In affected IDL files replace String with string

In the 4 affected IDL files replace the capitalised String with all lower case string and resubmit the zipped IDL files

There are track_priority_type typedefs defined in both the Track_Reporting and Tracking_Control Domain Model packages.

OARIS 3.0 beta has already addressed this

OARIS 3.0 beta has already addressed this by creating a common definition which is then used in specific unions elsewhere

Interface Manage_Physical_Configuration_CMS contains method receive_physical_configuration_success, which is used where receive_acknowledgement from common_use_case_interface would be expected

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

Method report_sim_mode_status does not contain the status of the session e.g. whether it is running, not started, frozen etc. The specification should also describe the overall state machine described by the interface.

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

Some passive sensors are unable to resolve a bearing around the line of symmetry through the sensor. The polar model for positions in the specifications does not allow this ambiguity to be clearly represented.

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

typedef sequence<org::omg::c4i::Domain_Model::Common_Types::subsystem_id_type, 256> sensor_track_based_on_id_type;

Has subsystem_id_type rather than plot_id_type as its value type.

Fixed in OARIS 3.0

Relationship has been changed through a plot association type and so this issue is no longer valid.

METOC RFP (c4i/08-12-02) is referenced in dtc/22-06-03 but does not yet exist on the OMG site in any form.

Reference was removed from 3.0 beta

The missing reference was already removed from 3.0 beta submission

For Service Health Reporting and Subsystem Health Reporting the specification describes two scenarios one on subsystem initiative and another on request.
In both cases the subsystem calls a method on the CMS interface with a request_id. In the 'on subsystem initiative' case it is unclear what value the subsystem should use for the request_id. Any value chosen could potentially be misinterpreted as a value for an actual CMS request.

Add functions to provide health reporting on subsystem initiative

Add functions to provide health reporting on subsystem initiative - i.e. the same as those requested by the CMS but without the request ID.

The Exchange Heartbeat use case supports assurance cases relating to runtime software integrity, in particular that critical functionality continues to be available and has not failed silently.
For the DDS PSM this is currently mapped to the built-in DDS API, but the on_requested_deadline_missed requires a suitable topic definition (which could/should be provided by the Exchange Heartbeat use case).

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

Attribute velocity in class sensor_track_type is mandatory but will not be defined / known for bearings tracks

Make azimuth optional on the polar velocity type

Make azimuth_rate optional on the polar velocity type to allow for sensor which report bearing only tracks

The description of the interface states that
"It is the CMS's responsibility to initiate the determination of initial state by making a request for information to the subsystem."
However, there is no operation defined to request information from the subsystem.
(Note: the protocol was probably simplified in working towards the v1.0 submission without revising the overall description of this particular interface).

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

The description of the interface states that
"It is the CMS's responsibility to initiate the determination of initial state by making a request for information to the subsystem."
However, there is no operation defined to request information from the subsystem.
(Note: the protocol was probably simplified in working towards the v1.0 submission without revising the overall description of this particular interface).

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

...

Issue not present in 3.0 beta

The issue reported in 2.0 does not appear to be present in 3.0 beta

delete_sensor_track is used as an interface in the Tracking_Control service and as a method on the Provide_Sensor_Tracks interface. This is potentially confusing and in principle could cause name clashes.

Rename delete_sensor_track method to end_sensor_track

Rename the delete_sensor_track method in the Provide_Sensor_Tracks_CMS interface to end_sensor_track

Perform Offline test should be compliance level 3A not 3B

Move Perform Offline Test to compliance level 3A

Move Perform Offline Test to compliance level 3A. Text and associated diagrams

The DDS topic types for PIM operations acquire_mastership and release_mastership are both missing from the IDL. Additionally request_id is a missing parameter from these operations, as otherwise the receive_acknowledgement operations in the sequence diagrams have an undefined source of request_id.

Acquire mastership already present in 3.0 IDL

This problem was already fixed in 3.0 beta

An important aspect of sensor performance estimation is to understand bias particularly for atmospheric effects.

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

There are two activities "Define Test Target Scenario" & "Control Test Target Facility" for one interface

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

.

Remove suggested items from additional_information description

Remove suggested items from additional_information description that are already present as attributes on the type:
priority
identification

On page 95 the description of technical_state_type calls it a class while the diagrams stereotype it as an IDLEnum.

Change description of technical_state_type

Change description of technical_state_type to IDLEnum

This is a useful mode of operation ...

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

to be elaborated ...

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

...

Change types from activity to action

types used in the activity diagrams are all activity rather than action which would be preferred in current UML.

For example CORBA, ALMAS & AMSM

Normative References were already updated at 3.0 beta

Normative References were already updated at 3.0 beta with CORBA, ALMAS and AMSM not present

The interaction diagrams for the Control_Emissions service do not provide a mechanism for determining the initial state of the emission control setting.
Possibilities are that the CMS is expected to explicitly set this for all sensors as part of startup of each sensor (e.g. whilst they are in the READY state) or that each sensor has its own default (or persistent) state that it assumes on each startup.
Further information: The description of the ONLINE technical state, requires Control Emissions to occur once the subsystem is in this state and implies that the emission control setting is off when the subsystem enters the ONLINE state.
More information: The description of the Control_Emissions_CMS interface states: "It is the CMS's responsibility to initiate the determination of initial state by making a request for information to the subsystem." However there is no method on the subsystem interface to provide this information.
The description of Control_Emissions_CMS interface should be updated accordingly.

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

The sensor orientation message reports the orientation of the sensor with two angles: azimuth and elevation. But to completely describe orientation, three angles are required. The missing angle is a rotation about the normal from the array. It can becalled a clocking angle. Using azimuth and elevation correspond to Cardan angles, which describe orientation as heading, elevation, and bank. The missing angle in this system is the bank angle. See https://en.wikipedia.org/wiki/Euler_angles

Add bank angle to sensor_orientation_type

Create a new type for bank angle and add to the sensor_orientation_type class.

Searches can potentially take a long time, there is no message/interaction to stop one once its in progress. Suggest adding a stop_cued_search as with stop_surveillance.

Add stop_cued_search operation to Perform_Cued_Search_Sub interface

Add stop_cued_search operation to Perform_Cued_Search_Sub interface. Update the table describing the operation and the sequence diagram to show usage.

The sensor orientation message reports the orientation of the sensor relative to a specified coordinate system. However, if a radar has multiple sensors there is no way to distinguish between them. I suggest adding an optional sensor_id field (type short) to distinguish between multiple sensors.

Add optional sensor_id to sensor_orientation_type

Add optional sensor_id to sensor_orientation_type of type short

Range rate type limited to 0-1e5, this should also accept negative values for closing rates. Also an issue in version 3 beta.

Modify range to allow negative

Change the range on range_rate_type to be -1 e5 .. 1 e5

I am trying to download the OARIS v1.1 XMI file but I am getting a http error 404 - Page not found message when clicking on the link provided (https://www.omg.org/spec/OARIS/20190301/OARIS%20PSM%20XMI.xml) under the OARIS v1.1 page (https://www.omg.org/spec/OARIS/1.1)

Not an OARIS 3.0 FTF Issue

Not an OARIS 3.0 FTF Issue and has been resolved by OMG staff

range_rate_type is used to quantify the rate of change of the range. The range of allowed values is 0.0 to 1e5, but this is too restrictive. Range rate is negative when an object is getting closer to the origin, i.e. the range is decreasing so range rate is negative. The lower bound of range rate should be -1e5, the negative of the maximum value.

Fixed by duplicate issue OARIS3-23

Fixed by duplicate issue OARIS3-23

The specification and Sensor_Assessment.idl have multiple misspellings of "equipment" as "equipement". All of the misspellings are in types and structs related to sensor_plot_equipement_assessment.

Update diagram 7.158 to correct spelling

Update diagram 7.158 to correct spelling

system_track_type does not contain identity or classification

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

These tags are meaningless in the specification.

Remove ea_guid tags from the model

Remove ea_guid tags from methods in the model

The description of the NORTH_DOWN in coordinate_orientation_type says:

Valid for Polar Coordinate Kind
Azimuth has origin (0.0) at North, clockwise positive, measured in the horizontal plane
Elevation has origin (0.0) when pointing directly down, and 180.0 degrees when pointing directly up, measured in the vertical plane.

This would be fine except the elevation_coordinate_type specifically says units are radians with values from -PI/2 to +PI/2.

I suggest changing the maximum value of elevation in the description of NORTH_DOWN from 180.0 degrees to PI radians and change the maximum value of elevation_coordinate_type from +PI/2 to +PI.

Change NORTH_DOWN descriptive text and elevation_coordinate_type max limit

Change the maximum value of elevation in the description of NORTH_DOWN from 180.0 degrees to PI radians and change the maximum value of elevation_coordinate_type from +PI/2 to +PI.

The following is the description of request_id in oaris 2.0 spec:

7.3.12.6 request_id_type
Type: IDLTypeDef unsigned long long
Package: Requests
The purpose of the request_id is to uniquely relate responses of the subsystem (server) to requests of the CMS (client). The request_id is set by the client. It is the responsibility of the client to specify a system-wide unique request_id (e.g. based on a combination of client id and a sequence number / time of request). Here it indicates that CMS as client should specify request_id. But in section 7.7.5.3 Provide_Subsystem_Identification, it documents that it should be the subsystem to initiate the communication to CMS, which implies subsystem will need to specify request_id required in receive_sub_identification_data_type before sending it to CMS.

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

The OARIS 2.0 specification says registration includes information on:

• The service for which the actor wants to register / deregister his interest
• The information within the service for which the actor wants to register / deregister his interest
• The intended (direct or indirect) recipient(s) of the information provided by the subsystem
• Any parameters of the provision needed such as Quality of Service parameters

But according to the IDL, register_interest_type contains a sequence of interest_type, which contains only the registration type (REGISTER or DEREGISTER), the recipent, and quality of service. The message has no way to specify a service or information within a service; the first two bullet points in the requirements above.

Defer to 3.1 RTF

This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

The specification and the file Perform_Splash_Spotting.idl have multiple misspellings of spotting as "splotting". For example, confirm_reposition_splash_splotting_area, receive_splash_splotting_area_position, receive_splash_splotting_area_track.

Correct instances of splotting

Correct instances of splotting to spotting

Sparx Enterprise Architect A (build v 16.1..1626) reports that the OARIS v3 beta (also v2 beta) XMI document is in XMI Version 1.1 - which is no longer supported by recent versions of EA.

Suggest specifying XMI 2.1 schema in source tooling and reissuing for compatibility.

Export XMI in XMI 2.5.1

When publishing from EA, ensure that UML 2.5 (XMI 2.5.1) is chosen as the export format.

The acquire and release mastership messages have only a "count" field. There is no way for the radar to determine which system is requesting or releasing mastership. The radar needs to know the identity of the master when reporting mastership. Suggest adding a subsystem ID to acquire and release mastership messages.

Issue is duplicated by OARIS3-19

Issue is duplicated (in part) by OARIS3-19. The resolution for OARIS 3-19 will resolve this issue.

The notes field for the ONLINE state in the Technical State state machine has a typo - viathe. The notes field has other subtle differences in comparison to the corresponding enumeration attribute.

fix the typo in the notes for the ONLINE state

Fix the typo in the model. This does not affect the generated specification as the diagram and text is not present in the specification document

Can this please be checked. Looking at OARIS v1.1 changebar this documents the changes from v1.0 to v1.1. The changebar document published on v2.0 should therefore be the changes from v1.1 to v2.0. The document published shows the changes from version v2.0 to v3 beta 1

Not an OARIS 3.0 FTF Issue

Not an OARIS 3.0 FTF Issue

The C2INav Model refers to a package defined by OARIS 1.1.
OARIS 2.0 is about to be published and there are 2.1 RTF & 3.0 FTF in progress.

Does not apply to OARIS specification

This is an issue affecting C2INav and does not affect OARIS. There is a separate issue raised on C2INav (https://issues.omg.org/browse/C2INAV13-1)

The syntax for an optional string (parameter_range: string [0..1]) can cause confusion to parsers of the XMI as to whether the syntax is for being optional or fixed length.
Optional strings would be better defined as an optional TypeDef.

This affects parameter_range and typical_value in the descriptor_type struct within Subsystem_Domain -> Subsystem_Control

Create Typedefs for optional strings

replace the parameters which are of type string [0..1] with typedefs in the descriptor_type class

The sequence diagrams for Mastership Acquisition and Mastership Release show receive_acknowledgement and receive_error in response to acquire_mastership and release_mastership. However, acquire and release have no request_id to respond to. Recommend adding request_id and subsystem_id keys to acquire and release mastership.

Add subsystem and request parameters to acquire and release mastership

Add subsystem and request parameters to acquire and release mastership. Update the four sequence diagrams and table descriptions for the methods.

Section 8.2 mandates how topics and partitions should be used to include different subsystems into an OARIS based system.

However the approach mandated is not the only approach and other approaches may be used and be more suitable for a given use case. This section should be re-written to provide some guidance examples rather than mandates

Reword section 8.2

Reword section 8.2 to give guidance to a system integrator rather than mandate a particular approach.

The relationship between plot_association_type and sensor_track_type should be a composition such that the sensor track contains a collection of plot_association_type objects rather than a collection of references which can not be resolved as the plot_association_type does not have an id and is not published separately on another topic.

change plot_association relationship to composition

change the sensor_track_type to be a compostion of plot_association_types

The class plot_summary_type was expected to be a topic type, but it isn’t mapped to an operation in the PIM – so it isn’t. We need to add a suitable operation to the Provide_Plots or Provide_Sensor_Orientation interface.

Add plot_summary_type to method on Provide_Plots_CMS

Add a method write_sensor_plot_summary to the Provide_Plots_CMS interface taking a parameter of type plot_summary_type.

The plot_association_type contains both a plot_subsystem attribute and a plot_id attribute which contains a subsystem_id attribute.

These both refer to the same piece of information and therefore one is redundant and should be removed.

Remove plot_subsystem attribute from plot_association_type

Remove the plot_subsystem attribute from the plot_association_type struct

The exported XMI from the EA model has been generated with the option selected to alphabetically sort the attributes in the model. This does not affect the word specification but does impact the XMI and IDL.

Export XMI without alphabetical sorting enabed

For the 3.0 FTF submission, ensure that the XMI (and hence the generated IDL) has not had alphabetical sorting of attributes applied on export.

The PSM section of the document was omitted from the submission and should be re-instated

Re-insert PSM section

Re-insert the PSM section as written for the 2.0 standard into the 3.0 standard