document title / titre du document TRP W ORK PLAN ... - emits - ESA
document title / titre du document TRP W ORK PLAN ... - emits - ESA
document title / titre du document TRP W ORK PLAN ... - emits - ESA
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>TRP</strong> Work Plan 2005-2007<br />
Description of Activities<br />
TEC-SB/7935/dc<br />
12/Feb/09<br />
<strong>TRP</strong> Reference:<br />
Title:<br />
T605-09GI<br />
N-Tier architectures applied to Ground Operations Systems<br />
The current generation of Ground Operations Systems used at ESOC is based on client-server architecture, which is more<br />
generically referred to as a '2-Tier' architecture. In particular in the telemetry processing subsystem, the current<br />
implementation leads to severe requirements about the procurement and maintenance of all H/W workstations, including the<br />
large number of users workstations. The purpose of this study is therefore to investigate the possible benefits that can be<br />
achieved by adopting 'N-Tier' architectures to Mission Control Systems. In particular, the 3-Tier architecture should be looked<br />
at for the most critical subsystems i.e. the telemetry processing, the commanding and the On-Board Software Maintenance<br />
(OBSM). The 3-Tier architecture consists of a data server, implementing the management of the data; an application server,<br />
implementing most of the data processing functionality and a client, supporting the visualisation of the processed data to the<br />
end user. It attempts to overcome some of the limitations of the 2-Tier architecture by enabling a complete separation of the<br />
data presentation, the data processing and the data management using distinct entities. The different tiers interact via<br />
standard protocols such as CORBA, HTTP or standard database protocols. The middle-tier servers are typically coded in a<br />
highly portable, non-proprietary language such as C++ or Java. Middle-tier functionality servers may be multithreaded and can<br />
be accessed by multiple clients, not necessarily all under manual user control, thus enabling the automation of user actions.<br />
The analysis phase of the study shall identify the most suitable technology to be used for N-Tier implementations of Ground<br />
Operations Systems in general (e.g. code language of the application servers, data storage technology, interaction protocols).<br />
The design phase shall cover the architectural design of 'new generation' monitoring and control subsystems heavily involving<br />
data processing and visualisation (at least telemetry processing, commanding, OBSM and Station Monitoring and Control).<br />
The prototyping phase shall migrate an existing subsystem to the 3-Tier architecture and the assessment phase shall evaluate<br />
the benefits of the 3-Tier architecture at system level (including scalability, portability, flexibility, maintainability and<br />
performance) and provide recommendations for the future generations of Ground Operations System infrastructure S/W.<br />
Deliverables:<br />
Under review ------------------ Technical doc. (outputs of the analysis activities). Architectural design <strong>document</strong> (3-Tier<br />
architecture of the MCS most critical subsys). Model implementation of the 3-Tier architecture (selected MCS subsys). Final<br />
report.<br />
Current TRL: - Target TRL: TRL2 Application Need/Date: N/A<br />
Application/Mission:<br />
Contract Duration:<br />
SW Clause : - Dossier0 Ref.: T-7842<br />
Consistency with Harmonisation<br />
Roadmap and Conclusions:<br />
<strong>TRP</strong> Reference: T605-17GI<br />
European Technology Harmonisation on Ground Systems Software - First Set of<br />
Title:<br />
Standard Interfaces<br />
The European Technology Harmonisation on Ground Systems Software is supported through standardisation of functions and<br />
interfaces. It has been agreed to broaden the scope of this harmonisation (initially Mission Control and EGSE) to include the<br />
other ground system components (Flight Dynamics, simulators, Data archiving and mission planning);A three-phase approach<br />
has been adopted (medium term strategy) with: phase 1(System level): define, with the user community, a common system<br />
standard architecture and common requirement for identified mo<strong>du</strong>les to become ECSS standards; Phase 2: Define standard<br />
interfaces between mo<strong>du</strong>les (to become ECSS standards); Phase 3: Contracts to re-engineer, as needed, solutions compliant<br />
with requirements and standard interfaces, re-using as far as possible existing pro<strong>du</strong>cts. In this proposal, phase 2, it is<br />
proposed to pro<strong>du</strong>ce the definition of the standard interfaces between the mo<strong>du</strong>les of the Ground Systems Reference<br />
architecture, which is key for the future work. Examples of standard interface definition are TM monitoring and Commanding,<br />
Operational Database, On-Board Software management function, Mission Planning System, although the final list of<br />
interfaces to be standardised and its priorities will be defined at the end of Phase 1 (March 2004). This proposal covers the<br />
first set of interfaces (i.e. 5). A second proposal will cover the remaining interfaces (See Proposal T605-18GI /<br />
TOS-GI-ETH-GSSW-002).<br />
Deliverables:<br />
A set of standard interface definition (to be detailed at the end of Phase 1) between the mo<strong>du</strong>les of the Ground Systems<br />
reference Architecture.<br />
Current TRL: Target TRL: TRL1-2 Application Need/Date:<br />
Application/Mission:<br />
Contract Duration:<br />
SW Clause : - Dossier0 Ref.: T-7842<br />
Consistency with Harmonisation<br />
Roadmap and Conclusions:<br />
Page 177 of 227