-
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
OARIS21 — Initial Emission Control State Undefined in Control_Emissions protocol
- Key: OARIS21-2
- OMG Task Force: Open Architecture Radar Interface Standard (OARIS) 2.1 RTF