Open Architecture Radar Interface Standard Avatar
  1. OMG Specification

Open Architecture Radar Interface Standard — Open Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
OARIS21-3 Typo in ONLINE state description in the model OARIS 2.0 open
OARIS21-7 contradiction on who (subsystem or CMS) should initiate the identification process and set the request id. OARIS 2.0b1 open
OARIS21-68 acquire and release mastership have no request_id to acknowledge OARIS 2.0 open
OARIS21-67 Getting a 404 error when trying to download the OARIS 1.1 RTF -- Updated XMI file OARIS 1.1 open
OARIS21-66 Changebar document seems to be for v2 to 3.0 beta 1 OARIS 2.0 open
OARIS21-65 No way to cancel a cued search OARIS 2.0 open
OARIS21-64 Range rate type only positive OARIS 2.0 open
OARIS21-63 register_interest_type is missing service information OARIS 2.0 open
OARIS21-62 Incorrect units and range in description of NORTH_DOWN OARIS 2.0b2 open
OARIS21-61 range_rate_type does not allow negative values OARIS 2.0b2 open
OARIS21-60 system_track_type does not contain identity or classification OARIS 2.0b2 open
OARIS21-59 multiple misspellings of "equipment" as "equipement" OARIS 2.0b2 open
OARIS21-58 multiple misspellings of "spotting" as "splotting" OARIS 2.0b2 open
OARIS21-57 sensor_orientation_type assumes a single sensor OARIS 2.0b2 open
OARIS21-56 sensor_orientation_type is missing a rotation angle OARIS 2.0b2 open
OARIS21-55 Remove ea_guid MethodTags OARIS 2.0b2 open
OARIS21-15 Acquire and Release Mastership missing in PSM OARIS 2.0b2 open
OARIS21-45 Some of the Normative References are not used normatively in the Spec OARIS 2.0b2 open
OARIS21-42 Transition from Lost to Normal should not rate-aid OARIS 2.0b2 open
OARIS21-41 Overview activity diagrams are not legal UML OARIS 2.0b2 open
OARIS21-40 IFF Sensor Parameter and Assessment issues OARIS 2.0b2 open
OARIS21-39 Perform Offline test is in the wrong compliance level OARIS 2.0b2 open
OARIS21-38 Duplicate Test Target activities for an interface OARIS 2.0b2 open
OARIS21-37 Add sensor performance operation for bias estimation OARIS 2.0b2 open
OARIS21-36 No operation to send system track to sensor unsolicited OARIS 2.0b2 open
OARIS21-35 track_info_type blob contains info in the actual fields OARIS 2.0b2 open
OARIS3-6 Document in legacy XMI 1.1 version OARIS 3.0b1 open
OARIS3-5 Redundant use of substem_id in plot_association_type OARIS 3.0a1 open
OARIS3-4 plot_association_type relationship to sensor_track_type incorrect OARIS 3.0a1 open
OARIS3-3 Replace optional strings with typedefs OARIS 3.0a1 open
OARIS3-2 plot_summary_type is not mapped to an operation in the PIM OARIS 3.0a1 open
OARIS3-1 PSM Section missing OARIS 3.0a1 open
OARIS21-2 Initial Emission Control State Undefined in Control_Emissions protocol OARIS 2.0 open
OARIS21-27 service_health_type struct within Subsystem_Control IDL not in keeping with specification documentation. OARIS 2.0b2 open
OARIS21-22 technical_state_type incorrectly described as class when it is an enumeration OARIS 2.0b2 open
OARIS21-24 delete_sensor_track used as an interface and a method OARIS 2.0 open
OARIS21-23 Update copyright holders OARIS 2.0 open
OARIS21-21 Inconsistent state condition for Health Service OARIS 2.0b2 open
OARIS21-20 Heartbeat required as the basis for on_requested_deadline_missed for DDS PSM OARIS 2.0b2 open
OARIS21-18 PSM mapping for sensor_track_based_on_id_type has unexpected type OARIS 2.0b2 open
OARIS21-16 request_id for report_service_health on subsystem intiative OARIS 2.0b2 open
OARIS21-14 Mandatory velocity for sensor tracks doesn't work for bearings OARIS 2.0b2 open
OARIS21-13 IDL files are labelled as v1.1 not v2.0 OARIS 2.0 open
OARIS21-11 Representation of Ambiguity in Passive Bearings OARIS 2.0b2 open
OARIS21-10 The state of a simulation session is not apparent on the interface OARIS 2.0b2 open
OARIS21-9 Manage Physical Configuration doesn't use common request response protocol OARIS 2.0b2 open
OARIS21-8 Missing Reference OARIS 2.0 open
OARIS21-4 Description of Manage_Transmission_Sectors protocol is inconsistent OARIS 2.0 open
OARIS21-6 Description of Manage_Tracking_Zones protocol is inconsistent OARIS 2.0 open
OARIS21-5 Description of Control_Battle_Override protocol is inconsistent OARIS 2.0 open
OARIS21-1 Two track_priority_type typedef classes defined OARIS 2.0b1 open
OARIS-85 Typo fixes OARIS 1.0 open

Issues Descriptions

Typo in ONLINE state description in the model

  • Key: OARIS21-3
  • Status: open  
  • 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
  • Updated: Wed, 17 Apr 2024 10:31 GMT

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

  • Key: OARIS21-7
  • Status: open  
  • 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
  • Updated: Wed, 17 Apr 2024 10:30 GMT

acquire and release mastership have no request_id to acknowledge

  • Key: OARIS21-68
  • Status: open  
  • Source: RTX ( Dr. David Bainbridge)
  • Summary:

    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.

  • Reported: OARIS 2.0 — Fri, 29 Mar 2024 02:21 GMT
  • Updated: Wed, 17 Apr 2024 10:28 GMT

Getting a 404 error when trying to download the OARIS 1.1 RTF -- Updated XMI file


Changebar document seems to be for v2 to 3.0 beta 1

  • Key: OARIS21-66
  • Status: open  
  • Source: MCS-IA ( Jez Merchant-Locke)
  • Summary:

    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

  • Reported: OARIS 2.0 — Thu, 4 Jan 2024 13:31 GMT
  • Updated: Wed, 17 Apr 2024 10:24 GMT

No way to cancel a cued search

  • Key: OARIS21-65
  • Status: open  
  • Source: Swordfish Computing ( Cameron Bunge)
  • Summary:

    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.

  • Reported: OARIS 2.0 — Tue, 19 Dec 2023 04:19 GMT
  • Updated: Wed, 17 Apr 2024 10:23 GMT

Range rate type only positive

  • Key: OARIS21-64
  • Status: open  
  • Source: Swordfish Computing ( Cameron Bunge)
  • Summary:

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

  • Reported: OARIS 2.0 — Tue, 19 Dec 2023 04:11 GMT
  • Updated: Wed, 17 Apr 2024 10:22 GMT

register_interest_type is missing service information

  • Key: OARIS21-63
  • Status: open   Implementation work Blocked
  • Source: RTX ( Dr. David Bainbridge)
  • Summary:

    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.

  • Reported: OARIS 2.0 — Tue, 28 Nov 2023 22:00 GMT
  • Updated: Wed, 17 Apr 2024 10:21 GMT

Incorrect units and range in description of NORTH_DOWN

  • Key: OARIS21-62
  • 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: Wed, 17 Apr 2024 10:15 GMT

range_rate_type does not allow negative values

  • Key: OARIS21-61
  • 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: Wed, 17 Apr 2024 10:14 GMT

system_track_type does not contain identity or classification

  • Key: OARIS21-60
  • 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: Wed, 17 Apr 2024 10:13 GMT

multiple misspellings of "equipment" as "equipement"

  • Key: OARIS21-59
  • 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: Wed, 17 Apr 2024 10:12 GMT

multiple misspellings of "spotting" as "splotting"

  • Key: OARIS21-58
  • 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: Wed, 17 Apr 2024 10:10 GMT

sensor_orientation_type assumes a single sensor

  • Key: OARIS21-57
  • 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: Wed, 17 Apr 2024 10:09 GMT

sensor_orientation_type is missing a rotation angle

  • Key: OARIS21-56
  • 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: Wed, 17 Apr 2024 10:06 GMT

Remove ea_guid MethodTags

  • Key: OARIS21-55
  • 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: Wed, 17 Apr 2024 10:03 GMT

Acquire and Release Mastership missing in PSM

  • Key: OARIS21-15
  • 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: Wed, 17 Apr 2024 10:02 GMT

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

  • Key: OARIS21-45
  • 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: Wed, 17 Apr 2024 10:01 GMT

Transition from Lost to Normal should not rate-aid


Overview activity diagrams are not legal UML


IFF Sensor Parameter and Assessment issues


Perform Offline test is in the wrong compliance level

  • Key: OARIS21-39
  • 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: Wed, 17 Apr 2024 09:54 GMT

Duplicate Test Target activities for an interface

  • Key: OARIS21-38
  • 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: Wed, 17 Apr 2024 09:53 GMT

Add sensor performance operation for bias estimation

  • Key: OARIS21-37
  • 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: Wed, 17 Apr 2024 09:52 GMT

No operation to send system track to sensor unsolicited

  • Key: OARIS21-36
  • 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: Wed, 17 Apr 2024 09:51 GMT

track_info_type blob contains info in the actual fields


Document in legacy XMI 1.1 version

  • Key: OARIS3-6
  • Status: open   Implementation work Blocked
  • Source: qinetiq ( ben xavier)
  • Summary:

    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.

  • Reported: OARIS 3.0b1 — Thu, 11 Apr 2024 09:58 GMT
  • Updated: Fri, 12 Apr 2024 19:25 GMT

Redundant use of substem_id in plot_association_type

  • Key: OARIS3-5
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    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.

  • Reported: OARIS 3.0a1 — Wed, 13 Mar 2024 08:39 GMT
  • Updated: Wed, 13 Mar 2024 08:39 GMT

plot_association_type relationship to sensor_track_type incorrect

  • Key: OARIS3-4
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    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.

  • Reported: OARIS 3.0a1 — Wed, 10 Jan 2024 08:51 GMT
  • Updated: Wed, 10 Jan 2024 08:51 GMT

Replace optional strings with typedefs

  • Key: OARIS3-3
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    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

  • Reported: OARIS 3.0a1 — Mon, 9 Oct 2023 09:23 GMT
  • Updated: Mon, 9 Oct 2023 09:23 GMT

plot_summary_type is not mapped to an operation in the PIM

  • Key: OARIS3-2
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    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.

  • Reported: OARIS 3.0a1 — Tue, 5 Sep 2023 11:05 GMT
  • Updated: Tue, 5 Sep 2023 11:05 GMT

PSM Section missing

  • Key: OARIS3-1
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

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

  • Reported: OARIS 3.0a1 — Tue, 5 Sep 2023 11:04 GMT
  • Updated: Tue, 5 Sep 2023 11:04 GMT

Initial Emission Control State Undefined in Control_Emissions protocol

  • Key: OARIS21-2
  • Status: open  
  • 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
  • Updated: Tue, 18 Jul 2023 09:42 GMT

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

  • Key: OARIS21-27
  • 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: Tue, 11 Jul 2023 19:54 GMT

technical_state_type incorrectly described as class when it is an enumeration

  • Key: OARIS21-22
  • 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, 3 Jul 2023 19:24 GMT

delete_sensor_track used as an interface and a method

  • Key: OARIS21-24
  • Status: open  
  • 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
  • Updated: Mon, 3 Jul 2023 19:24 GMT

Update copyright holders

  • Key: OARIS21-23
  • Status: open  
  • 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
  • Updated: Fri, 19 May 2023 05:17 GMT

Inconsistent state condition for Health Service

  • Key: OARIS21-21
  • 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: Fri, 24 Feb 2023 10:41 GMT

Heartbeat required as the basis for on_requested_deadline_missed for DDS PSM

  • Key: OARIS21-20
  • 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: Thu, 23 Feb 2023 14:42 GMT

PSM mapping for sensor_track_based_on_id_type has unexpected type

  • Key: OARIS21-18
  • 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: Thu, 23 Feb 2023 11:27 GMT

request_id for report_service_health on subsystem intiative

  • Key: OARIS21-16
  • 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: Wed, 8 Feb 2023 15:31 GMT

Mandatory velocity for sensor tracks doesn't work for bearings

  • Key: OARIS21-14
  • 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: Wed, 11 Jan 2023 18:04 GMT

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

  • Key: OARIS21-13
  • Status: open  
  • 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
  • Updated: Mon, 9 Jan 2023 11:56 GMT

Representation of Ambiguity in Passive Bearings

  • Key: OARIS21-11
  • 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: Fri, 16 Dec 2022 16:04 GMT

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

  • Key: OARIS21-10
  • 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: Fri, 16 Dec 2022 14:10 GMT

Manage Physical Configuration doesn't use common request response protocol

  • Key: OARIS21-9
  • 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: Fri, 16 Dec 2022 08:44 GMT

Missing Reference

  • Key: OARIS21-8
  • Status: open  
  • 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
  • Updated: Fri, 14 Oct 2022 15:57 GMT

Description of Manage_Transmission_Sectors protocol is inconsistent

  • Key: OARIS21-4
  • Status: open  
  • 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
  • Updated: Wed, 28 Sep 2022 14:55 GMT

Description of Manage_Tracking_Zones protocol is inconsistent

  • Key: OARIS21-6
  • Status: open  
  • 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
  • Updated: Wed, 28 Sep 2022 14:55 GMT

Description of Control_Battle_Override protocol is inconsistent

  • Key: OARIS21-5
  • Status: open  
  • 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
  • Updated: Wed, 28 Sep 2022 14:47 GMT

Two track_priority_type typedef classes defined

  • Key: OARIS21-1
  • Status: open  
  • 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
  • Updated: Mon, 25 Jul 2022 16:51 GMT

Typo fixes

  • Key: OARIS-85
  • Status: open  
  • Source: Airbus Group ( Mr. Oliver M. Kellogg)
  • Summary:

    These findings target the OARIS 2.0 Initial Submission.

    Replace unque by unique :
    Fig. 7.40 association from measurement_element_match_type to measurement_element_type

    1..*

    Unknown macro: {set is unque for each instance}



    Replace activtiy by activity
    in Figures 7.41, 7.44, 7.54 association from platform_type to platform_activity_type



    Replace discete by discrete :
    Table 7.115 2nd row 2nd column (Notes)

    The semantics of the ordering of the elements of the
    discete distribution



    Replace transmision_mode by transmission_mode :
    Table 7.145 last row first column (Attribute)
    Figure 7.50 «idlStruct» transmission_sector_type last attribute



    Replace perfomance_bin_type by performance_bin_type :
    Figure 7.51 «idlStruct» perfomance_bin_type
    7.5.8.5 perfomance_bin_type
    Table 7.157 Attributes of IDLStruct perfomance_bin_type



    Replace initation by initiation :
    Table 7.1642nd row 2nd column (Notes)

    Track initation on external request (e.g. from CMS)



    Replace initiatied by initiated :
    Table 7.165 continuation (page 144) 2nd row 2nd column (Notes)

    initiation_mode initiation_mode_type [0..1] Initiation mode of track (automatic or externally
    initiatied)



    Replace configuraiton_url} by {{configuration_url :
    page 159 bottom table Method change_physical_configuration Parameters

    request_id_type request_id
    configuration_url_type
    configuraiton_url



    Replace acccepted by accepted :
    Figure 7.95 note at bottom right

    request_ack.acccepted
    = true



    Replace metod by method :
    Page 197 top table Method battle_override_setting Notes

    This metod is used by the subsystem



    Replace Altenative by Alternative :
    Table 7.103 sequence diagram box label in upper left corner

    alt Altenative Flows



    Replace plot_concentratrion by plot_concentration :
    Section 7.8.1.1 first table Method receive_plot_concentration() Parameters

    request_id_type request_id
    plot_concentration_report_type
    plot_concentratrion



    Replace subystem by subsystem :
    Section 7.8.1.2 first table Method receive_periodic_clutter_assessment Notes

    Interface used by CMS to receive
    periodic clutter assessment reports
    from the subystem.



    Replace Ammendment by Amendment :
    Figure 7.117 loop

    [Ammendment Required]



    Replace authorative by authoritative :
    Page 226 bottom table every row of column Notes

    The CMS [de]selects [...] match[es] as being the
    authorative assessment for the sensor track



    Replace masterhip by mastership :
    Figure 7.143 Alternative Flow [...] loss of masterhip
    Figure 7.145 Alternative Flow [...] loss of masterhip



    Replace Susbystem by Subsystem :
    Figure 7.153 alt Unsuccessful Request

    [Susbystem unable to calculate requested nominal performance]



    Replace encouters by encounters :
    Figure 7.155 alt Unsuccessful Request

    [Subsystem encouters an irrecoverable error condition [...]



    Replace Ackowledgement by Acknowledgement :
    Figure 7.157 alt Negative Acknowledgement

    [Subsystem processing produces [...] after initial positive Ackowledgement]



    Replace succesfull by succesfully :
    Figure 7.171 sequence diagram inner box label

    opt target succesfull acquired



    Replace fulfil by fulfill (American English) :
    7.9.3.1 page 278 2nd-to-last sentence on page

    If the radar may not fulfil the illumination request, [...]

    7.9.3.3 middle of page 284 standalone sentence

    If the radar may not fulfil the uplink request, this is reported [...]



    Globally replace splotting by spotting :

    • Page 286 confirm_reposition_splash_splotting, receive_splash_splotting_area_position, receive_splash_splotting_area_track
    • Page 288 receive_splash_splotting_area_position
    • Page 289 confirm_reposition_splash_splotting_area, receive_splash_splotting_area_track
    • Page 290 Figure 7.184 Perform Splash Spotting - Report On Splash Splotting
  • Reported: OARIS 1.0 — Sat, 15 Feb 2020 20:30 GMT
  • Updated: Tue, 18 Feb 2020 15:55 GMT