No abstract

No abstract

Operational procedures are typically initially designed at the spacecraft manufacture site by the system/AIV engineers, tested with the spacecraft database, and then published in the flight operation manual. The Flight Control Team (FCT) takes the delivered procedures to build the LEOP, commissioning and routine operation procedures. These procedures however are not always sufficiently validated, due to lack of time. Testing and validation of procedures is often left as a low priority task performed late in the development process.Once developed, there is the need to allow easy (re)validation of the procedure in an automated or semi-automated manner. This validation is not only necessary for checking the consistency of the procedures during their development, but also to verify that the procedures achieve their objective, are safe, and do not endanger the integrity of the spacecraft. Moreover, automatic regression testing needs to be carried-out whenever the S/C database is updated, Mission Control System (MCS) or operational simulator versions are updated, or when Mission Planning System (MPS) outputs need validation. In order to improve the level of testing and reduce associated effort and costs, ESA has conducted a study the prime objective of which was to develop innovative concepts and tools to automate the validation of operations procedures for current and future missions.The developed concepts allows automatic validation of procedures at all stages of their development: initial development, upgrade to accommodate a new database or On-Board Software (OBSW) version, modification resulting from test campaign activities, and regression testing. Tools using validation models have been designed, prototyped, and evaluated with extensive involvement of perspective users. These tools can be shared between industry, spacecraft manufactures, the operations teams and any party for the validation of procedures such that the effort for procedure development and maintenance is reduced, and that procedures developed by one party can be provided and re-used by the other parties with minimum effort.

No abstract

The ESA METERON (Multi-purpose End-To-End Robotic Operations Network) aims to demonstrate the feasibility of controlling advanced robots on Earth using 'telepresence' control equipment, providing essential experience for planning and preparing real human exploration missions. In this context METERON can be seen as a test-bed forfuture missions to the Moon, Mars and other celestial bodies. The METERON activities are organised in dedicated experiments, which combine testing operations, ground and space systems, technologies, and robotic systems in an environment as realistic as possible. In particular, the "plug & play" METERON Operations Environment (MOE) and METERON Robotic Services (MRS) have been developed. The METERON Operations Environment (MOE) is the term used for referring to the METERON software systems involved in robotic operations on the ground and on-board the ISS. The implementation of the MOE has been heavily based on the reuse of the existing ESA Ground Segment Test and Validation Infrastructure (GSTVi) and selected elements of the EGOS infrastructure. In the last two years, MOE and the MRS have been successfully used in several experiments aiming at validating different technologies, concepts and scenarios (Disruption/Delay Tolerant Networks, real-time mission operations, multi-asset monitoring & control, distributed robotic operations), and conducted in collaboration with different partners, such as ESTEC (Telerobotic & Haptics Laboratory, Planetary Robotics Laboratory), Thales Alenia Space Italia, UKSA, Airbus UK, NASA (Jet Propulsion Laboratory) and the Belgian User Support and Operations Centre (BUSOC). This paper presents the recent METERON developments concerning the METERON Operations Environment (MOE) and METERON Robotic Services (MRS), the most recent experiments, and the technologies that are been used.