1. OMG Mailing List
  2. Open Architecture Radar Interface Standard 2.0 (OARIS) 1.1 Revision Task Force mailing list

Open Issues

  • Issues not resolved
  • Name: oaris-2-rtf
  • Issues Count: 8

Issues Descriptions

Missing Reference

  • Key: OARIS21-8
  • Status: open  
  • Source: BAE SYSTEMS ( 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

contradiction on who (subsystem or CMS) should initial 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, 5 Oct 2022 15:07 GMT

Description of Manage_Transmission_Sectors protocol is inconsistent

  • Key: OARIS21-4
  • Status: open  
  • Source: BAE SYSTEMS ( 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 ( 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 ( 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

Typo in ONLINE state description in the model

  • Key: OARIS21-3
  • Status: open  
  • Source: BAE SYSTEMS ( 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, 28 Sep 2022 10:49 GMT

Initial Emission Control State Undefined in Control_Emissions protocol

  • Key: OARIS21-2
  • Status: open  
  • Source: BAE SYSTEMS ( 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.

  • Reported: OARIS 2.0 — Wed, 28 Sep 2022 09:19 GMT
  • Updated: Wed, 28 Sep 2022 10:39 GMT

Two track_priority_type typedef classes defined

  • Key: OARIS21-1
  • Status: open  
  • Source: BAE SYSTEMS ( 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