Open Architecture Radar Interface Standard Avatar
  1. OMG Specification

Open Architecture Radar Interface Standard — Open Issues

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

Issues Descriptions

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: 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 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

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