Open Architecture Radar Interface Standard Avatar
  1. OMG Specification

Open Architecture Radar Interface Standard — Open Issues

  • Acronym: OARIS
  • Issues Count: 28
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
OARIS3-35 Transition from Lost to Normal should not rate-aid OARIS 2.0b2 open
OARIS3-45 technical_state_type incorrectly described as class when it is an enumeration OARIS 2.0b2 open
OARIS3-44 service_health_type struct within Subsystem_Control IDL not in keeping with specification documentation. OARIS 2.0b2 open
OARIS3-38 Perform Offline test is in the wrong compliance level OARIS 2.0b2 open
OARIS3-34 Some of the Normative References are not used normatively in the Spec OARIS 2.0b2 open
OARIS3-33 Acquire and Release Mastership missing in PSM OARIS 2.0b2 open
OARIS3-32 Remove ea_guid MethodTags OARIS 2.0b2 open
OARIS3-28 multiple misspellings of "equipment" as "equipement" OARIS 2.0b2 open
OARIS3-25 Incorrect units and range in description of NORTH_DOWN OARIS 2.0b2 open
OARIS3-31 sensor_orientation_type is missing a rotation angle OARIS 2.0b2 open
OARIS3-29 multiple misspellings of "spotting" as "splotting" OARIS 2.0b2 open
OARIS3-30 sensor_orientation_type assumes a single sensor OARIS 2.0b2 open
OARIS3-26 range_rate_type does not allow negative values OARIS 2.0b2 open
OARIS3-55 The state of a simulation session is not apparent on the interface OARIS 2.0b2 open
OARIS3-54 Representation of Ambiguity in Passive Bearings OARIS 2.0b2 open
OARIS3-56 Manage Physical Configuration doesn't use common request response protocol OARIS 2.0b2 open
OARIS3-51 request_id for report_service_health on subsystem intiative OARIS 2.0b2 open
OARIS3-50 PSM mapping for sensor_track_based_on_id_type has unexpected type OARIS 2.0b2 open
OARIS3-52 Mandatory velocity for sensor tracks doesn't work for bearings OARIS 2.0b2 open
OARIS3-48 Inconsistent state condition for Health Service OARIS 2.0b2 open
OARIS3-49 Heartbeat required as the basis for on_requested_deadline_missed for DDS PSM OARIS 2.0b2 open
OARIS3-40 Add sensor performance operation for bias estimation OARIS 2.0b2 open
OARIS3-39 Duplicate Test Target activities for an interface OARIS 2.0b2 open
OARIS3-41 No operation to send system track to sensor unsolicited OARIS 2.0b2 open
OARIS3-37 IFF Sensor Parameter and Assessment issues OARIS 2.0b2 open
OARIS3-42 track_info_type blob contains info in the actual fields OARIS 2.0b2 open
OARIS3-36 Overview activity diagrams are not legal UML OARIS 2.0b2 open
OARIS3-27 system_track_type does not contain identity or classification OARIS 2.0b2 open

Issues Descriptions

Transition from Lost to Normal should not rate-aid


technical_state_type incorrectly described as class when it is an enumeration

  • Key: OARIS3-45
  • Status: open  
  • Source: Naval Combat Systems Integration Support Service ( Matthew Burleigh)
  • Summary:

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

  • Reported: OARIS 2.0b2 — Wed, 3 May 2023 13:25 GMT
  • Updated: Mon, 22 Jul 2024 15:42 GMT

service_health_type struct within Subsystem_Control IDL not in keeping with specification documentation.

  • Key: OARIS3-44
  • Status: open  
  • Source: MCS-IA ( Jez Merchant-Locke)
  • Summary:

    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?

  • Reported: OARIS 2.0b2 — Wed, 21 Jun 2023 08:20 GMT
  • Updated: Mon, 22 Jul 2024 15:37 GMT

Perform Offline test is in the wrong compliance level

  • Key: OARIS3-38
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0b2 — Sat, 23 Sep 2023 12:50 GMT
  • Updated: Mon, 22 Jul 2024 15:23 GMT

Some of the Normative References are not used normatively in the Spec

  • Key: OARIS3-34
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    For example CORBA, ALMAS & AMSM

  • Reported: OARIS 2.0b2 — Thu, 28 Sep 2023 18:47 GMT
  • Updated: Mon, 22 Jul 2024 13:04 GMT

Acquire and Release Mastership missing in PSM

  • Key: OARIS3-33
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Fri, 27 Jan 2023 12:34 GMT
  • Updated: Mon, 22 Jul 2024 12:59 GMT

Remove ea_guid MethodTags

  • Key: OARIS3-32
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    These tags are meaningless in the specification.

  • Reported: OARIS 2.0b2 — Fri, 6 Oct 2023 16:43 GMT
  • Updated: Mon, 22 Jul 2024 12:36 GMT

multiple misspellings of "equipment" as "equipement"

  • Key: OARIS3-28
  • Status: open  
  • Source: RTX ( Dr. David Bainbridge)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Wed, 27 Sep 2023 18:22 GMT
  • Updated: Mon, 22 Jul 2024 07:59 GMT

Incorrect units and range in description of NORTH_DOWN

  • Key: OARIS3-25
  • Status: open  
  • Source: RTX ( Dr. David Bainbridge)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Mon, 30 Oct 2023 19:25 GMT
  • Updated: Mon, 22 Jul 2024 07:58 GMT

sensor_orientation_type is missing a rotation angle

  • Key: OARIS3-31
  • Status: open  
  • Source: RTX ( Dr. David Bainbridge)
  • Summary:

    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

  • Reported: OARIS 2.0b2 — Wed, 27 Sep 2023 13:46 GMT
  • Updated: Mon, 22 Jul 2024 07:58 GMT

multiple misspellings of "spotting" as "splotting"

  • Key: OARIS3-29
  • Status: open  
  • Source: RTX ( Dr. David Bainbridge)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Wed, 27 Sep 2023 18:08 GMT
  • Updated: Mon, 22 Jul 2024 07:58 GMT

sensor_orientation_type assumes a single sensor

  • Key: OARIS3-30
  • Status: open  
  • Source: RTX ( Dr. David Bainbridge)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Wed, 27 Sep 2023 14:01 GMT
  • Updated: Mon, 22 Jul 2024 07:58 GMT

range_rate_type does not allow negative values

  • Key: OARIS3-26
  • Status: open  
  • Source: RTX ( Dr. David Bainbridge)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Mon, 30 Oct 2023 18:40 GMT
  • Updated: Mon, 22 Jul 2024 07:56 GMT

The state of a simulation session is not apparent on the interface

  • Key: OARIS3-55
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Fri, 16 Dec 2022 14:10 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

Representation of Ambiguity in Passive Bearings

  • Key: OARIS3-54
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Fri, 16 Dec 2022 16:04 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

Manage Physical Configuration doesn't use common request response protocol

  • Key: OARIS3-56
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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

  • Reported: OARIS 2.0b2 — Fri, 16 Dec 2022 08:44 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

request_id for report_service_health on subsystem intiative

  • Key: OARIS3-51
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Wed, 8 Feb 2023 15:31 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

PSM mapping for sensor_track_based_on_id_type has unexpected type

  • Key: OARIS3-50
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: OARIS 2.0b2 — Thu, 23 Feb 2023 11:27 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

Mandatory velocity for sensor tracks doesn't work for bearings

  • Key: OARIS3-52
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0b2 — Wed, 11 Jan 2023 18:04 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

Inconsistent state condition for Health Service

  • Key: OARIS3-48
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    (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!

  • Reported: OARIS 2.0b2 — Fri, 24 Feb 2023 10:41 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

Heartbeat required as the basis for on_requested_deadline_missed for DDS PSM

  • Key: OARIS3-49
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0b2 — Thu, 23 Feb 2023 14:42 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

Add sensor performance operation for bias estimation

  • Key: OARIS3-40
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0b2 — Sat, 23 Sep 2023 12:48 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

Duplicate Test Target activities for an interface

  • Key: OARIS3-39
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0b2 — Sat, 23 Sep 2023 12:49 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

No operation to send system track to sensor unsolicited

  • Key: OARIS3-41
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    This is a useful mode of operation ...

  • Reported: OARIS 2.0b2 — Sat, 23 Sep 2023 12:46 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

IFF Sensor Parameter and Assessment issues

  • Key: OARIS3-37
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    to be elaborated ...

  • Reported: OARIS 2.0b2 — Sat, 23 Sep 2023 12:51 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT

track_info_type blob contains info in the actual fields


Overview activity diagrams are not legal UML


system_track_type does not contain identity or classification

  • Key: OARIS3-27
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    system_track_type does not contain identity or classification

  • Reported: OARIS 2.0b2 — Mon, 23 Oct 2023 16:19 GMT
  • Updated: Tue, 9 Jul 2024 14:40 GMT