-
Key: OARIS3-48
-
Status: closed
-
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
-
Disposition: Resolved — OARIS 3.0b2
-
Disposition Summary:
Include STANDBY as precondition to Provide_Health_State_CMS
Include STANDBY as precondition to Provide_Health_State_CMS
-
Updated: Fri, 20 Dec 2024 23:14 GMT
OARIS3 — Inconsistent state condition for Health Service
- Key: OARIS3-48
- OMG Task Force: Open Architecture Radar Interface Standard (OARIS) 3.0 FTF