-
Key: C2MS12-43
-
Status: closed
-
Source: Kratos RT Logic, Inc. ( Mr. Mike Anderson)
-
Summary:
The Log Message in 1.0 is vague in the sense of what it is supposed to be used for. Is it an application-level log (similar to Log4j or is it an event alerting mechanism for ground and/or satellite events. It might be useful to split it into application logging vs ground or satellite alerting. Need to analyze its intended and current use to the extent possible and recommend a way forward that clearly demarcates event alerts from logging.
There also needs to be an Event that is to capture AWEs or state change... something to do with teh operational state of the system (Mission Data).
-
Reported: C2MS 1.0 — Sun, 14 Apr 2024 23:36 GMT
-
Disposition: Resolved — C2MS 1.2b1
-
Disposition Summary:
Add Event Message, Specify the Correct Use for Log Message
Add Event Message, Specify the Correct Use for Log Message.
The latter includes deprecating the SPACECRAFT-TIME in the current Log Message, and indicating that the use of Log Message for spacecraft or ground systems events is deprecated.
We add SATOPS to the Acronyms and Abbreviations so as to use that term when discussing Events.
Note that this is an isolated change to the model diagrams, showing only the changes for this issue. Other issues may change the same diagrams in different ways. Because of this, a consolidating issue will be created at the end of this C2MS 1.2 effort to combine changes from multiple issues where needed.
-
Updated: Mon, 30 Mar 2026 14:00 GMT
-
Attachments:
- C2MS12-43_1_new.svg 14 kB (image/svg+xml)
- C2MS12-43_2_original.bmp 1.67 MB (image/bmp)
- C2MS12-43_2_revised.svg 16 kB (image/svg+xml)
- Event Message Subject Naming Table New.bmp 266 kB (image/bmp)
- Log Message Subject Naming Table Updates.bmp 336 kB (image/bmp)
- Telemetry Limit Occurrence Types.png 20 kB (image/png)
C2MS12 — Rework Log Message
- Key: C2MS12-43
- OMG Task Force: Command and Control Message Specification (C2MS) 1.2 RTF