Alert Management Service Avatar
  1. OMG Specification

Alert Management Service — Open Issues

  • Acronym: ALMAS
  • Issues Count: 13
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

No standard DDS key specification

  • Key: ALMAS14-2
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The DDS-Xtypes specification now provides a standard way of specifying keys. This specification should use that mechanism

  • Reported: ALMAS 1.1 — Mon, 7 Feb 2022 18:37 GMT
  • Updated: Tue, 26 Sep 2023 15:40 GMT

Standardisation of Logging

  • Key: ALMAS14-6
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The specification does not standardise the logging mechanism. This could be achieved by PSM specific means.

  • Reported: ALMAS 1.1 — Sat, 5 Feb 2022 16:10 GMT
  • Updated: Thu, 6 Apr 2023 15:01 GMT

Unable to override extra attributes in alert template when raising an alert

  • Key: ALMAS14-9
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The extra attribute mechanism is a useful extension mechanism for providing additional information and/or functionality relating to an alert. However, in the current specification there isn't a way to do this using predefined alert templates with runtime parameters.

  • Reported: ALMAS 1.2b1 — Tue, 7 Feb 2023 17:22 GMT
  • Updated: Thu, 6 Apr 2023 15:01 GMT

CallStatus Reason should be an enumeration not an int

  • Key: ALMAS14-8
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The semantics of the reason attribute of the CallStatus call should be encapsulated as an enumeration. Also the formatting of the description of the attribute doesn't help clarity.

  • Reported: ALMAS 1.1b1 — Sat, 5 Feb 2022 15:22 GMT
  • Updated: Thu, 6 Apr 2023 15:01 GMT

Operation tables for interfaces aren't easy to read

  • Key: ALMAS14-7
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The formatting of tables for operations for interface classes doesn't aid readability

  • Reported: ALMAS 1.1 — Sat, 5 Feb 2022 16:04 GMT
  • Updated: Thu, 6 Apr 2023 15:01 GMT

Register and Unregister Receiver are unnecessary in the DDS PSM

  • Key: ALMAS14-1
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    Topic types ALMAS_RegisterReceiver and ALMAS_UnregisterReceiver are not required as this functionality is covered by the statndard (DCPS) DDS Subscription Model.

  • Reported: ALMAS 1.1 — Tue, 8 Feb 2022 10:00 GMT
  • Updated: Thu, 6 Apr 2023 15:01 GMT

Meaning of Categorization Rules not clear when referenced

  • Key: ALMAS14-4
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The summaries for operations AttachCategorisationRule and DetachCategorisationRule refer to Categorization Rules. Whilst there is some description in section 6.4 there is no overview of purpose prior to this point or forward sign-posting to section 6.4, so the purpose of these methods is left somewhat opaque.

  • Reported: ALMAS 1.1 — Mon, 7 Feb 2022 11:33 GMT
  • Updated: Thu, 6 Apr 2023 15:01 GMT

No mechanism to feedback alternative action choice

  • Key: ALMAS14-3
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The spec does not appear to offer an interface for an alert client to be informed of the alternative or non-standard choice that has been made in response to an alert.

  • Reported: ALMAS 1.1 — Mon, 7 Feb 2022 18:12 GMT
  • Updated: Thu, 6 Apr 2023 15:01 GMT

The role of ALMAS Manager is unclear

  • Key: ALMAS14-5
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The description of ALMAS Manager does not give a clear picture of where it fits into the ALMAS system.

  • Reported: ALMAS 1.1 — Sat, 5 Feb 2022 16:12 GMT
  • Updated: Thu, 6 Apr 2023 15:01 GMT

Inconsistent use of underscores in XSD (templates)

  • Key: ALMAS11-49
  • Status: open  
  • Source: BAE SYSTEMS ( Peter Evans)
  • Summary:

    Alert_Template
    Alert_Category
    ....
    ConfirmationRequried
    TimeoutAction

  • Reported: ALMAS 1.0 — Wed, 25 Mar 2020 15:13 GMT
  • Updated: Fri, 3 Apr 2020 19:32 GMT

Inconsistencies between XSD enums and text

  • Key: ALMAS11-50
  • Status: open  
  • Source: BAE SYSTEMS ( Peter Evans)
  • Summary:

    The enumerations in the XSD and the body are inconsistent.
    See Timeout Action and Acknowledgement Model in the XSD and table 7.2.2.1

  • Reported: ALMAS 1.0 — Wed, 25 Mar 2020 15:11 GMT
  • Updated: Fri, 3 Apr 2020 19:32 GMT

form throws away submissions on errors

  • Key: ALMAS11-51
  • Status: open  
  • Source: BAE SYSTEMS ( Peter Evans)
  • Summary:

    Pleas fix this form so it doesn't wipe data on verification errors and keep unchecking the agree box

  • Reported: ALMAS 1.0 — Wed, 25 Mar 2020 15:08 GMT
  • Updated: Fri, 3 Apr 2020 19:32 GMT

Inconsistencies between enum values in tables and XSD (alert templates)

  • Key: ALMAS11-52
  • Status: open  
  • Source: BAE SYSTEMS ( Peter Evans)
  • Summary:

    Timeout Action:
    7.2.2.1

    {cancel, notify, cancel & notify}

    XSD CancelOnly, NotifyOnly, CancelWithNotify

    AcknowledgementModel
    7.2.2.1

    {none, anyone, all}

    XSD AckByNone, AckByAnyone, AckByAll

    Also inconsistencies in the element naming in that some use underscores between words and others do not
    Alert_Template
    Alert_Category
    Secondary_Grouping
    ...
    TimeoutAction
    ReliablyDistributed
    MessageText
    ...

  • Reported: ALMAS 1.0 — Wed, 25 Mar 2020 15:05 GMT
  • Updated: Fri, 3 Apr 2020 19:32 GMT