Adaption of a generic EGSE Controller Software solution for EGS-CC
Programme
GSTP
Programme Reference
G617-205SW
Prime Contractor
ROVSING A/S
Start Date
End Date
Status
Closed
Country
Denmark
Objectives
The aim of the activity is to adapt a generic EGSE Controller Software solution, that has successfully been used in several EGSE projects for ESA missions, to the EGS-Common Core.
Description
A generic EGSE Controller Software solution, used for several EGSE projects, requires adaptation at different levels (architecture, sub-system) in order to be implemented with the EGS-Common Core.
This adaptation brings benefits by allowing a seamless transition from spacecraft Assembly, Integration and Testing to Mission Operations and reducing costs (by sharing development, sustaining and maintenance of a single infrastructure. It also allows a reduction in the cost and risk associated to the implementation of space projects, as the infrastructure is known from the previous projects and modernizes of legacy Electrical Ground Support Equipment (EGSE) and Mission Control Systems (MCS).
Future users of the EGS-Common Core will benefit from the a common look and feel in the user interface, a common way to analyse logs and to handle archived data and common ways to run scripts and get reports. Persons writing and executing scripts in Common Core, will also be able to write and execute scripts for the EGSE Controller.
The EGSE Controller Software solution EGSE architecture consists of the hardware adaptors, hardware simulators, business logic engine, middleware, a Man Machine Interface, a logger and the OCOE interface (integration into the EGSE infrastructure). It can simulate a full EGSE and is used to validate EGSE software prior to actual hardware availability. In order to validate the EGSE controller software or the generic simulator in a specific configuration, a Test Commander (a software component) is used (to run test scripts). System requirements are analysed and mapped to validation cases (that ensure during the tests that all requirements are met).
To integrate the EGSE Controller Software with the EGS-CC, several modification are required. For service integration, a new interface component is required to use EGS-CC service integration layer (replacing the OCOE interface used). For the scripting language, the script engine is to be update to add support for writing scripts in Groovy (the EGS-CC scripting language), make test API?s usable in Groovy and make EGS-CC test API?s available.
Updates are required for the logging component and for the archiving component (to perform logging and archiving in the same format as EGS). Security requirements the subsystem controller and Man Machine Interface (MMI) are required to be analysed and security points are required to be added. The Man Machine Interface needs to be redesign and re-written and the reporting and data modelling approaches are to be updated.
The work breakdown consists of the following:
- System engineering (covering the pre-study, requirements and systems engineering),
- System detailed design and implementation and
- testing and deployment.;
Application Domain
GEN-Generic Technologies
Technology Domain
8-System Design & Verification
Competence Domain
8-Ground Systems and Mission Operations
Initial TRL
TRL 4
Target TRL
TRL 5
Achieved TRL
TRL N/A
Public Document
Final Presentation