From the outset, MissionSpace sought to develop a flexible integration and data communications management methodology that would help resolve the interoperability dilemma faced by today's communications systems.
To promote interoperability, MissionSpace operates in a non-proprietary fashion. For example, each AME system comes with a simple Application Programmer's Interface (API) with which AME devlopers can use to create new Service Modules.
We provide our customers with this API at no charge, since the operational concept behind the AME is to create a new "plug-and-play" Service Module whenever a new interface is needed. Thus, our clients have the option of independently creating new Service Modules for their system and are not "locked" into having MissionSpace perform the task.
Becoming an AME-compliant Service Module is a straightforward, standardized process. The AME API consists of 3 software routines:
- Configure
- GetStatus
- Process
and 2 text files:
Any software or software-controllable hardware can become a Service Module for the AME. Once a particular process/procedure has been integrated, its capabilities are reuseable and distributable between any other AME-based communication system.
We encourage developers, designers and users to find applications for the AME outside of a spacecraft operations context. Any communications environment requiring local or remote control, data processing, and/or distribution is a potential application for the AME.
