${taskforce.name} Avatar
  1. OMG Task Force

Open Architecture Radar Interface Standard (OARIS) 2.1 RTF — Closed Issues

Open Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
OARIS21-4 Description of Manage_Transmission_Sectors protocol is inconsistent OARIS 2.0 $issue.fixedSpecification.name Deferred closed
OARIS21-6 Description of Manage_Tracking_Zones protocol is inconsistent OARIS 2.0 $issue.fixedSpecification.name Deferred closed
OARIS21-5 Description of Control_Battle_Override protocol is inconsistent OARIS 2.0 $issue.fixedSpecification.name Deferred closed
OARIS21-1 Two track_priority_type typedef classes defined OARIS 2.0b1 $issue.fixedSpecification.name Deferred closed
OARIS21-10 The state of a simulation session is not apparent on the interface OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-11 Representation of Ambiguity in Passive Bearings OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-9 Manage Physical Configuration doesn't use common request response protocol OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-8 Missing Reference OARIS 2.0 $issue.fixedSpecification.name Deferred closed
OARIS21-16 request_id for report_service_health on subsystem intiative OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-18 PSM mapping for sensor_track_based_on_id_type has unexpected type OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-14 Mandatory velocity for sensor tracks doesn't work for bearings OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-13 IDL files are labelled as v1.1 not v2.0 OARIS 2.0 $issue.fixedSpecification.name Deferred closed
OARIS21-23 Update copyright holders OARIS 2.0 $issue.fixedSpecification.name Deferred closed
OARIS21-22 technical_state_type incorrectly described as class when it is an enumeration OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-24 delete_sensor_track used as an interface and a method OARIS 2.0 $issue.fixedSpecification.name Deferred closed
OARIS21-21 Inconsistent state condition for Health Service OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-20 Heartbeat required as the basis for on_requested_deadline_missed for DDS PSM OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-2 Initial Emission Control State Undefined in Control_Emissions protocol OARIS 2.0 $issue.fixedSpecification.name Deferred closed
OARIS21-27 service_health_type struct within Subsystem_Control IDL not in keeping with specification documentation. OARIS 2.0b2 $issue.fixedSpecification.name Deferred closed
OARIS21-7 contradiction on who (subsystem or CMS) should initiate the identification process and set the request id. OARIS 2.0b1 $issue.fixedSpecification.name Deferred closed
OARIS21-25 C2INav Model refers to an old OARIS Common Types package C2INAV 1.0 $issue.fixedSpecification.name Deferred closed
OARIS21-3 Typo in ONLINE state description in the model OARIS 2.0 $issue.fixedSpecification.name Deferred closed

Issues Descriptions

Description of Manage_Transmission_Sectors protocol is inconsistent

  • Key: OARIS21-4
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0 — Wed, 28 Sep 2022 10:59 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Description of Manage_Tracking_Zones protocol is inconsistent

  • Key: OARIS21-6
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0 — Wed, 28 Sep 2022 14:52 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Description of Control_Battle_Override protocol is inconsistent

  • Key: OARIS21-5
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0 — Wed, 28 Sep 2022 11:58 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Two track_priority_type typedef classes defined

  • Key: OARIS21-1
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0b1 — Mon, 25 Jul 2022 16:51 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

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

  • Key: OARIS21-10
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Representation of Ambiguity in Passive Bearings

  • Key: OARIS21-11
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Manage Physical Configuration doesn't use common request response protocol

  • Key: OARIS21-9
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Missing Reference

  • Key: OARIS21-8
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Paul Marsh)
  • Summary:

    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.

  • Reported: OARIS 2.0 — Mon, 10 Oct 2022 15:11 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

request_id for report_service_health on subsystem intiative

  • Key: OARIS21-16
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

PSM mapping for sensor_track_based_on_id_type has unexpected type

  • Key: OARIS21-18
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Mandatory velocity for sensor tracks doesn't work for bearings

  • Key: OARIS21-14
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

IDL files are labelled as v1.1 not v2.0

  • Key: OARIS21-13
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

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

  • Reported: OARIS 2.0 — Mon, 9 Jan 2023 11:56 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Update copyright holders

  • Key: OARIS21-23
  • Status: closed  
  • Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
  • Summary:

    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,

  • Reported: OARIS 2.0 — Fri, 19 May 2023 05:17 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

technical_state_type incorrectly described as class when it is an enumeration

  • Key: OARIS21-22
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

delete_sensor_track used as an interface and a method

  • Key: OARIS21-24
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: OARIS 2.0 — Tue, 20 Jun 2023 12:29 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Inconsistent state condition for Health Service

  • Key: OARIS21-21
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Heartbeat required as the basis for on_requested_deadline_missed for DDS PSM

  • Key: OARIS21-20
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Initial Emission Control State Undefined in Control_Emissions protocol

  • Key: OARIS21-2
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: OARIS 2.0 — Wed, 28 Sep 2022 09:19 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

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

  • Key: OARIS21-27
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

contradiction on who (subsystem or CMS) should initiate the identification process and set the request id.

  • Key: OARIS21-7
  • Status: closed  
  • Source: BAE Systems ( Jia Liu)
  • Summary:

    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.

  • Reported: OARIS 2.0b1 — Tue, 13 Sep 2022 16:29 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

C2INav Model refers to an old OARIS Common Types package

  • Key: OARIS21-25
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: C2INAV 1.0 — Wed, 21 Jun 2023 10:00 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT

Typo in ONLINE state description in the model

  • Key: OARIS21-3
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    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.

  • Reported: OARIS 2.0 — Wed, 28 Sep 2022 10:49 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jul 2024 14:40 GMT