${taskforce.name} Avatar
  1. OMG Task Force

GEMS 1.6 RTF — Closed Issues

Open Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

Additional data type of time_duration

  • Key: GEMS16-12
  • Status: closed  
  • Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
  • Summary:

    It would be beneficial if an additional data type were available within GEMS of a time duration (time_duration). This allows for specification of a time offset. The suggested format would be:

    [-]HH:MM:SS[.fffffffff]

    Existing ground equipment solutions currently have time offsets and having this support would enable smoother and more accurate support and integration with GEMS-enabled products. Existing types do not adequately support providing an offset time duration format.

  • Reported: GEMS 1.5 — Fri, 29 Apr 2022 17:29 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: Sat, 22 Jun 2024 21:27 GMT

Clarify use cases and association with implementations

  • Key: GEMS16-8
  • Status: closed  
  • Source: Kratos RT Logic, Inc. ( Mr. Eric Ogren)
  • Summary:

    During the March 23, 2022 GEMS RTF Meeting, the RTF members agreed to:
    1. Add diagrams to sections 6.2.8 (Save Configuration Message), 6.2.9 (Restore Configuration Message), 6.2.11 (Asynchronous Status Message), and possibly 6.2.10 (get device definition file) for consistency with prior sections.
    2. Add references from the PIM and PSM sections back to the use cases.

  • Reported: GEMS 1.5 — Wed, 23 Mar 2022 17:30 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: Sat, 22 Jun 2024 21:27 GMT

Missing GEMS-ASCII PSM specifications

  • Key: GEMS16-17
  • Status: closed  
  • Source: Kratos RT Logic, Inc. ( Mr. Eric Ogren)
  • Summary:

    Add the GEMS-ASCII PSM schemas for the following:

    • PingMessage
    • PingResponse
    • MessageSequence
  • Reported: GEMS 1.5 — Wed, 11 May 2022 14:57 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: Sat, 22 Jun 2024 21:27 GMT

UML message classes with no Use Cases defined

  • Key: GEMS16-11
  • Status: closed  
  • Source: Kratos RT Logic, Inc. ( Mr. Eric Ogren)
  • Summary:

    PingMessage and PingResponse appears in UML but not in Figure 6.1 nor text of Section 6.2.

    GetConfigListMessage and GetConfigListResponse appears in UML but not in Figure 6.1 nor text of Section 6.2.

    DisconnectMessage appears in UML and Figure 6.1 but not in text of Section 6.2.

    MessageSequenceResponse appears in UML but not in Figure 6.1 nor Section 6.2, nor in either PSM

    Update Figure 6.1 (GEMS Use Cases) to include missing messages, and update other sections and figures per above.

  • Reported: GEMS 1.5 — Thu, 24 Mar 2022 17:52 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: Sat, 22 Jun 2024 21:27 GMT

Fix Example GEMS-ASCII Message Lengths