OARIS 3.0b2 FTF Avatar
  1. OMG Issue

OARIS3 — Initial Emission Control State Undefined in Control_Emissions protocol

  • Key: OARIS3-43
  • 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 — OARIS 3.0b2
  • Disposition Summary:

    Defer to 3.1 RTF

    This issue was raised against OARIS 2.0 and transferred into the OARIS 3.0 FTF very recently and after the comment deadline. In order to not delay the OARIS 3.0 FTF it is proposed to defer this issue for resolution in OARIS 3.1 which will be chartered at the successful conclusion of this FTF.

  • Updated: Fri, 20 Dec 2024 23:14 GMT