The core feature of the GMSEC architecture is standardized messages and formats, defined by the GMSEC team with industry involvement.  By using standard messages, the event-driven architecture facilitates quick and easy integration of functional components for a “plug and play” user experience.

The facility of integration is reinforced by the GMSEC Applications Programming Interface (API), which provides a multi-language, cross-platform, standard communications interface.  It supports message communications between middleware products.

The GMSEC architecture deploys middleware for its communication infrastructure.  Messages are passed between applications by an information software bus using the publish/subscribe paradigm. Application components maintain an interconnection to the software bus that isolates the components from each other. 

By virtue of standardizing messages and interfaces, rather than components, a mission using the GMSEC suite gains the ultimate flexibility to mix-and-match new and custom software, adapted legacy components, as well as government/commercial off-the-shelf (GOTS/COTS) elements, as long as they all are GMSEC-compliant.  Components can also be easily added, deleted, and replaced to suit the evolving needs of a mission. 

GMSEC API Goals

The keys to the GMSEC architecture are standard messages and message formats defined by the GMSEC team with industry involvement to ensure wide support and flexibility. By using standard messages, the event-driven architecture enables quick and easy integration of functional components, in a “plug and play” concept for current and future missions. The system components are selected to meet the unique needs of a mission or user. Messages are passed between applications by an information software bus using the publish/subscribe paradigm. Application components maintain an interconnection to the information software bus that isolates most of the components’ complexity from other components. Since applications communicate using known, defined messages, the architecture also enables the addition, deletion, and exchange of components to meet the changing requirements of missions as they progress through their lifecycles. The GMSEC API provides a multi-language, cross-platform, standard communications interface, which is easily integrated with any application.

Request the GMSEC API 4.7 here: NASA Software

GMSEC Architecture

The GMSEC goal is to promote and maintain a vision and architecture for the continued evolution of ground system software mission support tools at GSFC. GMSEC will continue to make the tools that are thoroughly tested and easy to integrate within the GMSEC architecture. GMSEC provides this support by:

• Maintaining the reference architecture
• Defining standard messages
• Supplying interface software

GMSEC also maintains documentation that explains the guidelines and policies of assembling a system with the GSMEC Architecture. Missions can select components that best fit their operational needs.

In addition, GMSEC branches develop GMSEC-compliant functional components and tools.

By selecting the GMSEC architecture and components, the development organization can build a system compatible with other GSFC systems at a lower cost and reconfigure it as necessary with low risk and minimal integration effort.

GMSEC Lab and Demonstration Facility

The GMSEC Reference Architecture is validated in the GMSEC Development Lab, located in Building 23, Room N305 on the GSFC campus. It provides multiple operating systems, languages, and communications protocols. The lab’s activities include development, benchmarking, demonstrations, evaluations, system integration, functional testing, and what-if scenarios. A local area network enables connectivity of other campus labs facilitating development and testing. Interested missions can leverage the lab to evaluate GMSEC-compliant GOTS and COTS for potential inclusion in flight and ground systems. New components can be augmented with adapters and tested with other components in the lab.

Activities

• One of the most beneficial uses of the GMSEC Development Lab is for interested missions to try out GMSEC compliant GOTS and COTS for evaluating potential flight and ground system components
• Development
• Benchmarking
• Demonstrations
• Evaluations
• Systems Integration
• Functional Testing
• What-if Scenarios

Contact Us

Project Manager: Theresa Beech
Deputy Project Manager: Viva Miller
Senior Systems Engineer: Bill Stanton
Deputy Test Lead: William Posey
Resource Analyst: Kenny Mautino
Administration: Lisa Kane

Request for GMSEC Information or Tech Support: GMSEC-support@lists.nasa.gov