Multi-Mission: SESS will be designed in order to support several missions. The incorporation to SESS of specific models and tools for each one of the new missions added shall not affect the main SESS infrastructure and the rest of the missions already supported.
Mission-Independent: The main SESS capabilities will be designed in order to provide its products with independence of the mission type. The incorporation of new missions to SESS has to be done with minimum changes in these main capabilities.
Multi-User Design: The access to SESS products shall be designed in order to have a public domain (General User) and a private one (Mission Specific Users and Mission Control Centre users).
Secure and Confidential: The private areas of the SESS database dealing with sensitive mission-specific information will only be accessible to the above mentioned Mission Specific Users and Mission Control Centre users.
Modularity: SESS will be designed with a modular architecture in order to provide to the system maximum updating capabilities and the advantage to use the same modules for different Missions.
Expandability: Database, models and tools will be designed with the proper structure to allow new software implementations and hardware upgrading capabilities with minor changes in the system.
Supporting renewal of models and tools: SESS project will provide a renewal and update philosophy to allow SESS future updates with the minor possible changes in the different SESS modules. A complete interface with Tools and modules has to be defined to allow ESA, SESS users, Space Environment Community, etc. the development of new capabilities for a specific mission or for the General Users domain.
Location (site) independent: SESS will allow different installation locations with the minor changes in the system.