User Tools

Site Tools


gems

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
gems [2013/10/11 16:06]
andzik
gems [2022/10/03 08:39] (current)
justin.boss
Line 1: Line 1:
-{{gems-logo.png|}} +{{gems-logo.png|}}
  
- +====== Ground Equipment Monitoring Service (GEMS) ======
- +
-====== GEMS (Ground Equipment Monitoring Service) ======+
  
 Welcome to the GEMS homepage. The GEMS (//Ground Equipment Monitoring Service//) specification was developed within the OMG Space Domain Task Force. It focuses on standardizing the model for device control and defines simple protocols that will hopefully reduce system integration costs. Welcome to the GEMS homepage. The GEMS (//Ground Equipment Monitoring Service//) specification was developed within the OMG Space Domain Task Force. It focuses on standardizing the model for device control and defines simple protocols that will hopefully reduce system integration costs.
  
 +===== Current Status =====
  
 +The latest version of GEMS is 1.4.
  
 +GEMS Versions:
  
 +  * [[https://www.omg.org/spec/GEMS/1.4/|GEMS 1.4]]
 +  * [[https://www.omg.org/spec/GEMS/1.3/|GEMS 1.3]]
 +  * [[https://www.omg.org/spec/GEMS/1.2/|GEMS 1.2]]
 +  * [[https://www.omg.org/spec/GEMS/1.1/|GEMS 1.1]]
 +  * [[https://www.omg.org/spec/GEMS/1.0/|GEMS 1.0]]
  
 +All versions of the GEMS specification can be found here: https://www.omg.org/spec/GEMS/
  
- +For a list of open issues click [[https://issues.omg.org/issues/lists/gems-rtf|here]].
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
-===== Current Status ===== +
- +
-GEMS 1.3 has been approved by the OMG Architecture Board. We will post a link to the document as soon as it is available. +
- +
-The latest posted version of the GEMS specification is version 1.2. All versions of the GEMS specification can be found here: http://www.omg.org/spec/GEMS/ +
- +
-For a list of open issues click [[http://www.omg.org/issues/gems-rtf.open.html|here]]. +
  
 ===== GEMS Example Messages ===== ===== GEMS Example Messages =====
Line 53: Line 38:
  
 This is the //problem// GEMS is attempting to solve. GEMS seeks to define a simple solution for what __should be__ a simple problem. It bases the solution around the OMG MDA approach using a standard model for device control and then maps that model to specific protocols and platforms. The real value in GEMS is the standard model and the mappings to specific protocols. The standard Platform Independent Model – or PIM provides the abstract device control concepts. It defines the use cases, message classes, parameters types and expected behaviors for setting and getting parameters, invoking directives and saving and restoring configurations. This is the //problem// GEMS is attempting to solve. GEMS seeks to define a simple solution for what __should be__ a simple problem. It bases the solution around the OMG MDA approach using a standard model for device control and then maps that model to specific protocols and platforms. The real value in GEMS is the standard model and the mappings to specific protocols. The standard Platform Independent Model – or PIM provides the abstract device control concepts. It defines the use cases, message classes, parameters types and expected behaviors for setting and getting parameters, invoking directives and saving and restoring configurations.
- 
- 
- 
- 
- 
- 
- 
  
 ===== The GEMS Platform Independent Model (PIM) ===== ===== The GEMS Platform Independent Model (PIM) =====
Line 65: Line 43:
 The GEMS PIM defines the basic message structure and interaction between a user and a GEMS device. This includes messages that allow users to set and get the current device configuration, save and restore parameters and even some basic connection logic. The messages are defined in UML and contain only the information the we found to be necessary for controlling a device.  The GEMS PIM defines the basic message structure and interaction between a user and a GEMS device. This includes messages that allow users to set and get the current device configuration, save and restore parameters and even some basic connection logic. The messages are defined in UML and contain only the information the we found to be necessary for controlling a device. 
  
-The PIM represents the abstract, or high level design, for GEMS. By itself, it isn't directly implementable. Instead, it is meant to be the reference point for actual implementations of the GEMS specification to map to (such as ASCIIXML and in the future CORBA, SNMP etc). This provides several key benefits. First, as implementable mappings of the GEMS PIM are developed, automatic translations from one mapping to another can be created. So, if you like to use XML, but that darn device vendor only wants to use ASCII, don't worry. A translator can be created that converts from one protocol to another. Another benefit is that by following the GEMS model, all devices take a similar shape. In other words, they all allow for parameters to be set and get in a similar fashion. For more sophisticated capabilities, GEMS devices provide directives and save/restore capability using common message types and behaviors.    +The PIM represents the abstract, or high level design, for GEMS. By itself, it isn't directly implementable. Instead, it is meant to be the reference point for actual implementations of the GEMS specification to map to (such as ASCII and XML). This provides several key benefits. First, as implementable mappings of the GEMS PIM are developed, automatic translations from one mapping to another can be created. So, if you like to use XML, but that other device vendor only wants to use ASCII, don't worry. A translator can be created that converts from one protocol to another. Another benefit is that by following the GEMS model, all devices take a similar shape. In other words, they all allow for parameters to be set and get in a similar fashion. For more sophisticated capabilities, GEMS devices provide directives and save/restore capability using common message types and behaviors.    
  
 It is important to keep in mind that the GEMS specification does not specify the exact parameters, types or ranges for any specific device or device type. That is beyond the scope of this specification. Instead, the GEMS PIM defines the approach to use when defining device specific parameters. The device vendor provides custom device information in a format compliant with the PIM and PSM used. It is important to keep in mind that the GEMS specification does not specify the exact parameters, types or ranges for any specific device or device type. That is beyond the scope of this specification. Instead, the GEMS PIM defines the approach to use when defining device specific parameters. The device vendor provides custom device information in a format compliant with the PIM and PSM used.
Line 72: Line 50:
  
 {{complete-uml.jpg?1024}} {{complete-uml.jpg?1024}}
- 
- 
- 
- 
- 
  
 ===== GEMS Platform Specific Models (PSMs) ===== ===== GEMS Platform Specific Models (PSMs) =====
 The precise mapping of the GEMS PIM to concrete protocols is captured in the Platform Specific Models (PSM). Initially two PSMs are available. As you will see, these are not complex protocols and can be easily implemented in a variety of devices. The precise mapping of the GEMS PIM to concrete protocols is captured in the Platform Specific Models (PSM). Initially two PSMs are available. As you will see, these are not complex protocols and can be easily implemented in a variety of devices.
- 
- 
- 
- 
- 
  
 ==== GEMS-XML ==== ==== GEMS-XML ====
Line 115: Line 83:
  
 </code> </code>
- 
  
 ==== GEMS-ASCII ==== ==== GEMS-ASCII ====
Line 127: Line 94:
  
 ===== On Going Work ===== ===== On Going Work =====
- 
- 
  
  
 ==== Known Implementations ==== ==== Known Implementations ====
   * [[http://www.amergint.com|Amergint Technologies]]: Amergint utilizes the GEMS interface on all of their products.   * [[http://www.amergint.com|Amergint Technologies]]: Amergint utilizes the GEMS interface on all of their products.
-  * [[http://www.rtlogic.com|Real Time Logic Inc. (RT Logic)]]: RT Logic provides a GEMS API on all of their T3-based systems.  +  * [[https://www.kratosdefense.com/about/divisions/space-training-and-cybersecurity/space|Kratos Defense]]: Kratos provides a GEMS API on all of their T3/T4-based systems. 
  
-Because of the nature of these products, GEMS is also used by many software applications related to the space industry, in essence any of AMERGINT's or RT Logic'customers. +Because of the nature of these products, GEMS is also used by many software applications related to the space industry, in essence any of AMERGINT's or Kratos' customers. 
  
 ==== Questions / Issues ==== ==== Questions / Issues ====
-Please email any issues to [email protected]. Any questions can be passed to [email protected].+Please email any issues to [[[email protected]]]. Any questions can be passed to [[[email protected]]].
  
 ===== Thanks ===== ===== Thanks =====
gems.1381521983.txt.gz · Last modified: 2013/10/11 16:06 by andzik