ESA/ESOC - ESAW 2011 - Abstracts

Final Programme & Abstract Book

2

Table of Contents

Committees ..........................................................................................................................................5

Programme

10 May 2011 ................................................................................................................................8

11 May 2011 ..............................................................................................................................10

Poster Session (running parallel to full programme) ................................................................13

Abstracts ........................................................................................................................................17

Biographies (oral presenters, in alphabetical order) .............................................................................53

3

4

Committees

Technical and Organising Committee

Chair: N. Peccia – European Space Operations Centre (ESA/ESOC)

Co‐chair: M. Pecchioli ‐ European Space Operations Centre (ESA/ESOC)

Committee Members

J. Eggleston – European Space Operations Centre (ESA/ESOC)

M. Merri – European Space Operations Centre (ESA/ESOC)

A. Slade – European Space Operations Centre (ESA/ESOC)

5

6

Programme

7

Tuesday 10 May 2011 08:15 Registration

09:00 Welcome and General Address

09:10 Logistics for the 2 days

Plenary Session 1 ‐ Institutional View and GSAW Chair: N. Peccia 09:20 ESOC’s Vision of the future N. Peccia ESA/ESOC 09:30 The European Ground System‐Common Core Initiative Pecchioli, M. ESA, (GERMANY) 09:55 Future Evolution of Mission Data Systems Merri, M ESA, (GERMANY) 10:20 GSAW History and future trends Baldeston, D. Aerospace Corporation 10:45 Coffee Break with Poster/Demo Sessions

Plenary Session 2 – Institutional View Chair: M. Merri 11:15 Current Trends and Outlook of Future Challenges in Mission Operations @ GSOC............................................... 17 Braun, A. Deutsches Zentrum für Luft‐ und Raumfahrt e.V., (GERMANY) 11:40 ASI vision on future Ground Control System Software Ibba, R. ASI, (ITALY) 12:05 Building the Ground Data System for the Mars Science Laboratory (MSL) Project – The Launch/Cuise/EDL System................................................................................................................................ 17 Dehghani, N. Jet Propulsion Laboratory, Caltech, NASA, (UNITED STATES)

12:30 Lunch Break with Poster/Demo Sessions

8

The programme on this afternoon runs in parallel session, series A & B, as noted.

Parallel Session (A) 3 ‐ Architectures Chais: M. Pecchioli

14:00 Architecture Governance........................................................................................................................................ 17 Kolar, M. JPL, (UNITED STATES) 14:25 Creating an Architecture Roadmap for Harmonizing Legacy Ground Systems....................................................... 17 Campbell, A ; Webber, D ; Benator, S The Aerospace Corporation, (UNITED STATES) 14:50 Thales Alenia Space vision on future Ground Control System Software ................................................................ 17 Schmerber, P‐Y. 1; Chiroli, P. 2 1Thales Alenia Space, (FRANCE); 2Thales Alenia Space, (ITALY) 15:15 CS vison on Ground Software Systems D'Hoine, S. CS

15:40 Coffee Break with Poster/Demo Sessions

Parallel Session (A) 4 ‐ Architectures Chair: M. Spada

16:25 Astrium Space Transportation strategy for Ground Data Systems ........................................................................ 18 Brauer, Uwe EADS Astrium, (GERMANY) 16:50 GSOC Ground Segment Challenges......................................................................................................................... 18 Kozlowski, R. DLR / GSOC, (GERMANY)

Parallel Session (B) 5 – Operations Preparation and Automation Chair: J. Eggleston

14:00 Next Generation of Spacecraft Reference Database at Astrium ........................................................................... 19 Eisenmann, H. 1; Cazenave, C. 2 1Astrium Satellites, (GERMANY); 2Astrium Satellites, (FRANCE) 14:25 BASyS: Neo Satellite Database Management System............................................................................................. 20 Garzón, H. GMV, (SPAIN) 14:50 Mission Automation System for the International Space Innovation Centre at Harwell ....................................... 20 Roveda, F. 1; Kay, R. 1; Raper, I. 2 1Logica Deutschland GmbH & Co.KG, (GERMANY); 2Astrium Ltd., (UNITED KINGDOM) 15:15 Ground Segment Autonomy: A Revised Approach................................................................................................. 21 Mueller, H. ; Stoetzel, H. ; Plura, M. ; Lampka, R. ; Foutou, F. ; Henke, M. VCS AG, (GERMANY)


Parallel Session (B) 6 ‐ Operations Preparation and Automation Chair: M. Di Giulio

16:25 How is automation of satellite operations progressing at SES ? Morelli , G. SES‐AStra, (‐ Not specified ‐) 16:50 Inmarsat: Automation of Satellite and Ground Operations ................................................................................... 21 Rossetti, A ; Dickinson, M ; Sansone, C Inmarsat, (UNITED KINGDOM)

17:45 Facilities Tour

18:30 Social Event

9

Wednesday 11 May 2011 The programme on this day runs in parallel session, series A & B, as noted.

Parallel Session (A) 7 ‐ Architectures Chais: A. Ercolani

09:25 European Technology Harmonisation on Ground Software Systems: Update of Reference Architecture ............ 22 Reid, S. 1; Pearson, S. 1; Davies, K. 2; Carvalho, B. 3 1Rhea System S.A., (BELGIUM); 2TERMA, (GERMANY); 3Critical Software, (PORTUGAL) 09:50 CNES Control Centre mock‐up : an evaluation of a standard SOA architecture..................................................... 22 Bornuat, P. 1; Cros, P‐A. 1; Pipo, C. 1; Anadon, M‐L. 2; Gelie, P. 2 1CS Systèmes d’Information, (FRANCE); 2CNES, (FRANCE) 10:15 NOSYCA: the New Operational System for the control of Aerostats...................................................................... 23 Nouvellon, S. Capgemini, (FRANCE)


Parallel Session (A) 8 ‐ Architectures Chair: D. Guerrucci

11:15 Ten Galileo FOC Payload EGSE Systems – Challenges in Design, MAIT and Schedule ............................................ 23 Kubr, H. ; Mader, W. ; Unfried, C. Siemens AG Österreich, (AUSTRIA) 11:40 GSMC ‐ Ground Station Monitoring & Control ....................................................................................................... 24 Riccio, F. 1; Lannes, C. 2 1Logica Deutschland GmbH & Co. KG, (GERMANY); 2 ESA/ESOC, (GERMANY) 12:05 Evolution of FEC architecture ................................................................................................................................. 24 Fernandez‐Ranada, I 1; Fuentes, A 1; Perez, R 1; Droll, P 2 1TCP Sistemas e Ingeniería, (SPAIN); 2ESA/ESOC, (GERMANY)


Parallel Session (A) 9 ‐ Commercialization Chair: J. Eggleston

14:00 Exploiting ESOC infrastructure over the long term................................................................................................. 25 Patrick, R Terma A/S, (DENMARK) 14:25 Satellite Control Systems Provision and Maintenance Choices.............................................................................. 25 Tortosa, M. Eutelsat, (FRANCE) 14:50 Ground Station Network for Micro/Nanosatellite Operation................................................................................. 25 Kurahara, N.

1; Shirasaka, S. 2; Nakasuka, S. 1 1University of Tokyo, (JAPAN); 2Keio University, (JAPAN)

Parallel Session (A) 10 ‐ Security Chair: N. Peccia

15:15 Development of SODAs for Improving Efficiency and Security for Satellite Control .............................................. 26 Techavijit, P. ; Sirikhant, A. ; Detpon, A. ; Tongpan, J. Geo‐Informatics and Space Technology Development Agency (GISTDA), (THAILAND)


16:00 Ground Segment Security: light and shade ............................................................................................................ 26 Vivero, J GMV, (SPAIN) 16:25 Automated Computer Network Defence................................................................................................................ 27 Wiemer, D. Defence R&D Canada, (CANADA)

10

Parallel Session (B) 11 – System Technology Chair: N. Peccia

09:00 SOA4GDS: Evaluating the Suitability of Emerging Service based Technologies in Ground Data Systems.............. 27 Parsons, P 1; Walsh, A 2 1The Server Labs, (SPAIN); 2VEGA, (GERMANY) 09:25 Modern Frameworks ‐ The Fantastic Four.............................................................................................................. 28 Villemos, GV ; James, S. ; Doyle, M. ; Klug, J. Logica, (GERMANY) 09:50 Leveraging EGOS User Desktop and hifly® to evolve SCOS‐2000 ........................................................................... 29 Casas, N ; Estévez, C GMV, (SPAIN) 10:15 Improve Usability of Graphical User Interfaces with New Technologies in Ground Centre Software ................... 29 Marty, S. 1; Volland, S. 1; Cros, P‐A. 1; Bornuat, P. 1; Anadon, M‐L. 2; Gelie, P. 2 1CS Systèmes d’Information, (FRANCE); 2CNES, (FRANCE)


Parallel Session (B) 12 – System Technology Chair: C. Haddow

11:15 Telemetry Archiving: How To Optimise Storage Efficiency, Retrieval Speed And Real‐Time Performance ........... 30 Kumpf, C. ; Foweraker, R. MakaluMedia GmbH, (GERMANY) 11:40 Towards a high performance LEON/GRLIB Emulator ............................................................................................. 30 Marchesi, J.E. Terma GmbH, (GERMANY) 12:05 A Netpdl Based Prototype Implementation of Galileo Attitude Orbit Control System Scoe Controller, and an Overview of Netpdl Utilization in Network Ground Software Components............................................... 30 Bertoli, A. 1; Risso, F. 2 1Carlo Gavazzi Space, (ITALY); 2Politecnico of Turin, (ITALY)


14:00 Integrated Test Concept and Test Automation for Aerospace Projects ................................................................. 31 Hofmann, J. T‐Systems, (GERMANY)

Parallel Session (B) 13 – Standards Chair: M. Merri

14:25 CCSDS Mission Operations Services ‐ Current Status ............................................................................................. 32 Cooper, S ; Thompson, R SciSys, (UNITED KINGDOM) 14:50 Where do we stand with CCSDS SM&C at CNES ? .................................................................................................. 32 Poupart, E. ; Pasquier, H. CNES ‐ Centre Spatial de Toulouse, (FRANCE) 15:15 Space Internetworking and DTN Prototyping: Evolutions in the Space Communications Architecture ................ 33 Fowell, S 1; Wheeler, S 1; Stanton, D 2; Farrell, S 3; Taylor, C 4; Viana Sanchez, A 4 1SciSys UK Ltd, (UNITED KINGDOM); 2Keltik Ltd, (UNITED KINGDOM); 3Tolerant Networks Ltd, (IRELAND); 4ESA ESTEC, (NETHERLANDS)


16:00 Space Data Routers for Exploiting Space DATA ...................................................................................................... 34 Goetzelmann, M. 1; Tsaoussidis, V. 2; Diamantopoulos, S. 2; Amanatidis , T. 3; Daglis , I. 4; Ghita, B. 5 1VEGA Space GmbH, (GERMANY); 2Democritus University of Thrace, (GREECE); 3Space Internetworks, (GREECE); 4National Observatory of Athens, (GREECE); 5University of Plymouth, (UNITED KINGDOM) 16:25 XTCE tailoring for ESA ............................................................................................................................................. 35 del Rey, I. GMV, (SPAIN)

11

12

Posters Recent Applications of Procedure Automation..................................................................................................................... 35 Blake, R SciSys, (UNITED KINGDOM) MUSE ‐ Multi‐Satellite Environnent ...................................................................................................................................... 36 Bonnafous, V. ; Cruz, D. Capgemini, (FRANCE) Introduction to the Architecture Centric Design Method..................................................................................................... 36 Brito, N. 1; Lattanze, A. J. 2 1University of Coimbra, (PORTUGAL); 2Institute for Software Research at Carnegie Mellon University, (UNITED STATES) OCP: Bringing Automation to Operational Control Centers.................................................................................................. 37 Capdevielle, E. ; Berthon, JC. Capgemini, (FRANCE) A Dedicated Space Surveillance Optical Network Cooperates with Radar to assure LEO Debris Catalogue build up and Maintenance ................................................................................................................................................................. 37 Cibin, L

1; Chiarini, M 1; Besso, P 2; Milani, A 3; Bernardi, F 3; Ragazzoni, R 4; Rossi, A 5 1CGS S.p.A., (ITALY); 2ESOC, (GERMANY); 3Dipartimento di Matematica UNIPI, (ITALY); 4INAF, (ITALY); 5IFAC‐CNR, (ITALY) ESTRACK Support for CCSDS Space Communication Cross Support Service Management .................................................. 38 Dreihahn, H. 1; Unal, M. 1; Hoffmann, A. 2 1ESA/ESOC, (GERMANY); 2VEGA Space GmbH, (GERMANY) Evolving a Commercial Satellite Control Center toward a SOA: Lessons Learnt................................................................... 38 Estévez Martín, C. ; Casas Manzanares, N. GMV, (SPAIN) PlanEO .................................................................................................................................................................. 39 Fernandez Garcia, A.J. ; Fernandez, C. Deimos Imaging S.L., (SPAIN) Architecture of the Telemetry Data Management System SpaceMaster ............................................................................. 39 Dr. Thelen, A.

1; Schoenig, S. 1; Koerver, W. 1; Dr. Fischer, H. 2; Dr. Sous, S. 2; Dr. Willnecker, R. 2 1S.E.A. Datentechnik GmbH, (GERMANY); 2DLR‐MUSC, (GERMANY) Mars Express/MARSIS Ground System Architecture. A Pioneer ESA Space Mission: Lessons Learned for the Future ........ 40 Giuppi, S. ; Orosei, R. ; Noschese, R. ; Cartacci, M. ; Cicchetti, A. INAF/IFSI, (ITALY) Operations Planning for the Galileo Constellation................................................................................................................ 40 Hall, S ; Hall, Stewart SciSys UK Ltd, (UNITED KINGDOM) ARES ‐ Efficient SW Integration and Reuse supported by an Agile Project Management Approach.................................... 41 Hauke, A. 1; Santos, R. 2; Unfried, C. 1 1Siemens AG Österreich, (AUSTRIA); 2ESA/ESOC, (GERMANY) Demonstration of the EGOS Data Dissemination System (EDDS) ......................................................................................... 41 Hawkshaw, M 1; Santos, R 2 1Logica, (GERMANY); 2ESA, (GERMANY) Use of Scrum in practice on the EGOS Data Dissemination System (EDDS).......................................................................... 42 Hawkshaw, M 1; Santos, R 2 1Logica, (GERMANY); 2ESA, (GERMANY)

13

Mission Automation at ESOC; finding success with an end‐to‐end approach. ..................................................................... 42 Heinen, W. ; Reid, S. ; Pearson, S. Rhea System S.A., (BELGIUM) Architectures for Integrated Satellite and Ground Operations ............................................................................................ 42 Honold, P. ; Castrillo, I. GMV, (SPAIN) Optimizing Communication Satellite Transponders Operation and Power Consumption with smartHz ............................. 43 Honold, P. ; Godino, E. GMV, (SPAIN) Fast Engineering Archives providing a new future for Mission Analysis............................................................................... 44 James, S. ; Pitaev, A. Logica Deutschland GmbH & Co.KG, (GERMANY) Federated System Architecture for Space Weather Services ............................................................................................... 44 Lawrence, Gareth Rhea System S.A., (BELGIUM) A Collaborative Electronic Logbook for Satellite Operations at Eutelsat .............................................................................. 44 Louro, N. ; Ronsiek, S. ; Foweraker, R. MakaluMedia GmbH, (GERMANY) PlanetExpl: a Framework for the Science and Engineering Assessment of Exploration Missions ........................................ 45 Luengo, O. 1; Kowalczyk, A. 2; Pantoquilho, M. 2 1GMV, (SPAIN); 2ESA, (GERMANY) Building an Open‐Source Community Around Flight dynamics Ground Systems................................................................. 45 Maisonobe, L. ; Fernandez‐Martin, Ch. CS SI, (FRANCE) Use of Open Architecture Middleware in the Satellite Ground Segment Domain. Data Distribution Service ..................... 46 Naranjo, H. GMV, (SPAIN) Can multi‐agent technology be applied to Space Mission Applications ?............................................................................. 46 Ocon, J.

1; Wijnands, Q. 2; Sanchez, A. M. 1; Cesta, A. 3 1GMV, (SPAIN); 2ESA, (NETHERLANDS); 3ISTC/CNR, (ITALY) Cloud Data Systems: Applying the Cloud in ESA Ground Data Systems................................................................................ 47 Parsons, P ; Olias, A The Server Labs, (SPAIN) GABIS: a Generic Build System for GSI applications.............................................................................................................. 48 Penataro, R

1; Zimmer, T 2 1GMV Aerospace and Defence, (SPAIN); 2ESA, (GERMANY) BIRF: How to Improve Software Projects Efficiency and Control using Business Intelligence .............................................. 48 Prieto, JF 1; Marques, P 2; Vieira, M 2; Widegård, K 3; Navarro, V 3 1ISFreelance, (SPAIN); 2University of Coimbra, (PORTUGAL); 3ESA‐ESOC, (GERMANY) SpaceMaster Overview of a Telemetry Data Management System ..................................................................................... 49 Schoenig, S. 1; Dr. Fischer, H.H. 2; Koerver, W. 2; Dr. Sous, S. 2; Dr. Thelen, A. 1; Dr. Willnecker, R. 2 1S.E.A. Datentechnik GmbH, (GERMANY); 2DLR‐MUSC, (GERMANY) The Innovative Rover Operations Concepts ‐ Autonomous Planning (IRONCAP) ‐ Science and Engineering Planning for Rover Operations .................................................................................................................................................................. 49 Steel, R. ; Hoffmann, A. ; Niezette, M. VEGA, (GERMANY)

14

Flexplan, the Adaptable System for Mission Planning & Scheduling .................................................................................... 50 Tejo, J. 1; Barnoy, A. 2; Pereda, M. 1 1GMV Aerospace And Defence, (SPAIN); 2GMV Space Systems Inc, (UNITED STATES) The GNSS Advanced Monitoring Element (GAME) Core....................................................................................................... 50 Villemos, G ; Biamonti, D. ; Edwards, D Logica, (GERMANY) Supporting the Management of Mission Operational Knowledge ‐ a Case Study using Mars Express ................................ 51 Villemos, G

1; Shaw, M 2; Doyle, M. 1; van Zetten, P 1 1Logica, (GERMANY); 2Mars Express OPS‐OPM, Consultant Vega Space GmbH, (GERMANY) Standardisation of Reprocessing Architectures for Future Ground Segments ..................................................................... 51 Williams, I. ; Evens, P. ; Steven, J. Logica Deutschland GmbH & Co.KG, (GERMANY) Cloud and Grid Technologies in Ground Segments............................................................................................................... 51 Williams, I. ; Evens, P. ; James, S. Logica Deutschland GmbH & Co.KG, (GERMANY)

15

16

17

Abstracts

Current Trends and Outlook of Future Challenges in Mission Operations @ GSOC

Braun, A. Deutsches Zentrum für Luft‐ und Raumfahrt e.V.,

GERMANY

Past and recent developments in operations concept and organizational structures at DLR/GSOC are shown. Commercialisation of space‐flight has induced cost pressure. An attempt is made to deduce from current studies to future scenarios. Standardization is a must. New technologies, still in experimental stage, have potential to mean qualitative changes of future operations.

****************

Building the Ground Data System for the Mars Science Laboratory (MSL) Project – The Launch/Cuise/EDL

System Dehghani, N.

Jet Propulsion Laboratory, Caltech, NASA, UNITED STATES

Presentation describes experiences/challenges in developing the GDS for support of Launch at Kennedy Space Center, and Cruise of the MSL to Mars. A description of MSL and science objectives is provided. Main segment provides an overview of GDS architecture and enhancements based on experiences during system tests. System is readied to support launch at KSC, and Launch/Cruise phases of MSL.

MSL is launched in November 2011. After 7 months of cruise, an autonomous EDL is executed landing on a pre‐selected area on Mars in August 2012. The GDS provides new architecture that is used by MSL as its first user. The new architecture provides opportunities that did not exist in the legacy system. Among them are means of monitoring and, to some extent, controlling ATLO functions from remote sites. Remote sites are defined as sites reachable via a local area network as well as via wide area networks spanning long distance geographical areas.

****************

Architecture Governance Kolar, M.

JPL, UNITED STATES

In order to reduce development costs while simultaneously helping to ensure mission success, the Jet Propulsion Laboratory has recognized that a well defined architecture and set of re‐usable design patterns are essential. But how do space agencies go about ensuring that their many projects are compliant

with these architecture standards and design patterns? This presentation discusses the importance of Architecture Governance, the essential elements for practicing governance, and how governance is an effective way to help insure architecture modernization efforts are infused into systems that cross ownership boundaries in a manner that provides maximum benefit while managing risk and cost.

****************

Creating an Architecture Roadmap for Harmonizing Legacy Ground Systems

Campbell, A; Webber, D; Benator, S The Aerospace Corporation, UNITED STATES

A number of spacecraft ground systems that support our customers have been in existence for several decades. In many cases, there are tens to hundreds of systems supporting various space applications, many of them based on legacy software, commercial software, and often unique hardware. The challenge is to define roadmaps to harmonize these legacy ground systems, modernizing and improving commonality and integration, while insuring that these systems can continue to execute their unique space missions and expand to handle additional missions. The presentation will discuss the creation of an architectural roadmap to address modernizing ground systems, harmonizing the systems for better commonality and data sharing, and interfacing with new systems that are being acquired by the government. The presentation will include discussion on a range of topics relevant to the roadmap:

Vision and Goals Challenges Creating the business case for modernizing those

systems Lessons learned Data exchange and sharing Security considerations Software approaches and tools Organizational considerations Interoperability and standards

****************

Thales Alenia Space vision on future Ground Control System Software

Schmerber, P‐Y.1; Chiroli, P.2 1Thales Alenia Space, FRANCE; 2Thales Alenia Space,

ITALY

Today's space market is driven by costs, and by the reduction of non quality costs on space programs. Software reuse is the key in cost reduction and quality improvement, specially when it allows to keep the

system architecture simple. The future systems shall allow reuse of software components accross projects, accross satellite development and operation teams, and accross companies in Europe. The user is at the heart of today's successful software applications, and we belive that the best software solution for tomorrow should be flexible enough to adapt to the different needs of its users, including the yet unknown future needs of the evolving users. In addition, the future system should be open source, as this is already a requirement of the majority of users that want to keep the possibility of an independant software maintenance during their long lived programs. To keep architecture simple, and maximize software reuse, the future system will be service based e.g made of loosely coupled software components working together with interactions defined by the function provided, independently from the actual implementation. Relying on open source frameworks for service based components offer in addition advantages for local Security implementation, high availability deployments, and smooth system scaling.

****************

Astrium Space Transportation strategy for Ground Data Systems Brauer, Uwe

EADS Astrium, GERMANY

Astrium ST has started in 2008 an internal initiative for a new ground software platform called Advanced Integration and Test Services (AITS) as follow‐on for the Common Ground System (CGS) system. CGS was developed with ESA in the context of the Columbus program (EMCS) and then reused for ATV and certain Satellite EGSE (e.g. SWARM, GOCE). AITS shall be the future standard software platform for projects & products in Astrium ST (e.g. launchers, space vehicles, robotics or on equipment level). AITS focus for the next years will be in the area of EGSE but a reuse as mission control system should be in principal possible. AITS project is a trans‐national project between German and France ST units. We have agreed in Astrium ST on a common software system specification end of 2009 and worked in 2010 on demonstrators for different use cases in launcher EGSE domain and performed architectural prototyping. Up to now AITS was fully funded by own funds but in parallel an AITS technology development project in ESA GSTP program is planned with support from Germany, Denmark, Ireland, Netherlands and Austria. The presentation shall give an overview of AITS project status and software architecture.

****************

GSOC Ground Segment Challenges Kozlowski, R.

DLR / GSOC, GERMANY

The Ground System as it is managed by the GSOC department Communications and Ground Stations covers the IT service of all voice , video and data systems and the whole complex of the Weilheim Antenna Ground Stations. The projects for which all the services are provided are the Human Spaceflight Projects Columbus Control Centre / ATV‐CC support and in parallel the satellite projects at GSOC have a huge set of requirements on the Ground System.

FOR GSOC THE FOLLOWING PROJECTS ARE PRESENTED:

M&C Antenna Ground Station SpACE DLR has implemented a new antenna ground station M&C Framework for the Weilheim antennas. It will be the M&C software for the existing 3 S‐Band antennas, the Ku‐Band antenna and the 30 meter dish. Further it will be used for the upcoming Ka‐Band antenna and the EDRS project. The software is based on open and standard technologies like C++, the ACE communications framework, Graphical User Interface Qt. The platforms supported are SuSE Enterprise Linux, Sun Solaris and Windows. The M&C Framework was built by DLR staff and now after successful testing, being implemented at the Weilheim Ground Station. It is planned that the new M&C system will be operational by mid of 2011.

Virtualisation Since more than 3 years DLR is using virtualisation technology within the GSOC control center. Since about 2 years the first network services (e.g. DNS, FTP‐server, Proxies) in the real time environment have been virtualised. The motivation are independence of hardware and software limitations, infra structure cost reductions/optimizations and energy savings. In addition to server virtualization the next step at GSOC is to introduce this technology in the multi mission control rooms with desktop virtualization.

Columbus Decentralised Ground Operations The European decentralized operations concept enables all participating countries to establish a transnational centre of competence that actively cooperates in European participation to the International Space Station (ISS). Operating this Ground Segment is a significant challenge for the Ground Operations Team at Col‐CC, not only due to the vast number of facilities and the related world‐wide distribution, but also because of the number of different users (Columbus and ATV flight control, payload facilities, engineering support, PR) with their specific operational needs and constraints.

Security Security is no longer only seen as IT‐Security but as

18

****************

Next Generation of Spacecraft Reference Database at Astrium

Eisenmann, H.1; Cazenave, C.2 1Astrium Satellites, GERMANY; 2Astrium Satellites,

FRANCE

BACKGROUND The application of databases for engineering data has a long lasting record at Astrium. One of the traditional use cases for databases is to support the processes for the definition, verification and exchange of telecommand and telemetry data. Beyond the classic use case for TM/TC in the frame of model‐based systems engineering, the need for a increased coverage of system engineering data became obvious.

Since the current systems in use have been in operation for more than a decade, the technologies in use are outdated. As result of that, the maintenance and evolution became more tedious and thus labour and cost intensive. Therefore it is planned to replace the current Astrium products for system database with a new product, developed by state of the art technologies.

CONTEXT The development started mustn't be considered as an isolated tool development. Rather for a successful development the different activities concurrently performed have to be carefully analysed and considered. The most important activities which are dependent on the database development vice versa are namely:

ECSS: There are various standards to be considered for the development of a new system database, those comprise E‐70‐41, E‐70‐31, ...Parts of it are stable, but for some of them quite recently an update is in progress, like e.g. E‐70‐41. Although not ECSS, but the MIB model can be considered as a de‐fact standard. It seems that also for the MIB and update is planned.

EGS‐CC: Under the lead of ESA an activity has been started to develop core parts of a future CCS.

Internal EADS standardization on PLM systems. Astrium Projects: It is planned to develop a

common infrastructure which supports all projects covering all different S/C types – for Agencies but also commercial customers. For telecommunication

projects a target mission already has been identified with challenging need dates.

TECHNOLOGIES Traditionally "database" typically means Relational Database Management Systems (RDBMS) for the back‐end part. For the front‐end over the years Java‐based solutions can be considered as de‐facto standard. In particular in the last decade the Java –based Eclipse development provides many free resources for the development of such elements.

More and more the Eclipse developments also cover elements which can be considered as a fully fledged data management kernel. Validation activities performed show very promising results. Those validation activities comprise Astrium internal developments but in particular also activities jointly performed with ESA e.g. Space System Reference Model (SSRM) or Virtual Spacecraft Design (VSD).

Furthermore along the definition of the ECSS E‐T‐10‐23 model based development for database engineering has been identified as a very beneficial technology for database development. The TM also contains a draft conceptual data model, which has been used for the validation. Along the validation and application of model‐based development for database engineering the role of the (conceptual) data model evolved. This also put a focus on how actually the model is defined. There are several technologies available, more or less technology independent, more or less expressive with respect to the semantics.

STATUS In 2010 the developments have been prepared with a definition of user requirements documents, involving the different user domains at Astrium. In parallel to that technology prototyping have been performed i.e. to assess the performance of the envisaged technologies for TM/TC databases. With beginning of 2011 the user requirements are currently consolidated. The development has been started.

STATUS The paper will elaborate on the following:

use cases and key user requirements for the upcoming system database

Selected technologies with trades performed Envisaged overall architecture Model‐based development approach Data model considerations

****************

19

BASyS: Neo Satellite Database Management System Garzón, H. GMV, SPAIN

BASyS is the new multi platform and multi site database management system, developed by GMV for Eutelsat, in charge of managing the whole Eutelsat satellites fleet.

The main objective of the project is the replacement of the current Eutelsat database management tool based on a Microsoft Access by a more robust, reliable and maintainable system based on open source components.

BASyS is based on DABYS Framework and Generic and S2K Data Manager developed by ESA. The principal activity of the deployment is the adaptation and customization of the DABYS Framework and the S2K Data Manager to the Eutelsat specific requirements in the frame of Neo SCS.

BASyS is a 3‐tier application composed mainly of:

MySQL as the database management system providing the data backend.

A Java server providing the data management services.

And an Eclipse RCP client providing the user interface.

BASyS introduces a huge range of new elements with respect to DABYS. The following aspects are the most remarkable ones:

BASyS incorporates the multi mission concept within the system in order to provide a homogeneous management of different satellite platforms. It makes transparent those features of specific satellite families.

It has been customized for accepting the Neo SCS data model and any other database feature required by Neo SCS.

BASYS integrates the on line database distribution system in charge of updating the operational satellite databases in Neo without any loss of telemetry.

BASyS is a high availability system with the introduction of the MySQL replication and Linux High Availability technologies.

BASyS extends the DABYS database consistency checking for including new items required by the Neo SCS model.

The BASyS software development environment has been adapted to the Eutelsat development system and software life cycle.

A significant number of improvements have been also included with respect to the typical database management functions like data editing and

reporting, database configuration control, import, export and user management.

The project has faced several challenges during the deployment phases but the difficulty of defining a set of definitive requirements can be remarked. The migration of a previous tool and the adaption of another system introduced a high level of complexity.

****************

Mission Automation System for the International Space Innovation Centre at Harwell

Roveda, F.1; Kay, R.1; Raper, I.2 1Logica Deutschland GmbH & Co.KG, GERMANY;

2Astrium Ltd., UNITED KINGDOM

When used within the space sector the term "Automation" almost always refers to a spacecraft automation system that automates the execution of flight operations procedures. However, the spacecraft is only one element of the entire space system and that space element must be complemented with complex ground equipment and software systems that allow the overall space mission to be successfully executed. An effective mission automation system should therefore support the simplification and/or automation of the operations of both ground and space system elements.

FoxE is a Mission Automation System specifically designed to support any element of the entire space system using a domain specific language supporting monitoring and controlling statements applicable to any system element.

Simplicity was the primary goal of this project. Every feature, from the language specification to the friendliness of the GUI, has been designed and implemented with the primary goal of simplifying the use of the system and the procedures that it executes.

FoxE was designed and implemented by Logica Deutschland GmbH to achieve the following objectives:

Minimise the complexity of the automation language

One language for both manual and automated procedures

Direct support for monitoring and controlling language constructs

360 degree mission automation system

Simple extendibility to support any type of system elements

Top‐level procedures defining abstracted mission automation tasks

System elements class and/or instance specific procedures to map top‐level procedures' steps into specific system element monitoring and controlling tasks

20

Web based MMI to allow zero deployment and zero configuration of clients

FoxE has been selected by Astrium Ltd. as prime contractor for the establishment of the Earth Observation Hub at the International Space Innovation Centre at Harwell to support the low cost operations concept through high‐degree of automation of both ground and space segments.

This paper presents in detail the objectives, the approach, the challenges and the solutions that Logica has adopted to implement this system within a very tight project schedule and budget. The resulting system is now deployed at ISIC and currently undergoing the end‐to‐end system tests.

****************

Ground Segment Autonomy: A Revised Approach Mueller, H.; Stoetzel, H.; Plura, M.; Lampka, R.; Foutou,

F.; Henke, M. VCS AG, GERMANY

The discussion of possibilities and drawbacks for autonomous systems in space is ongoing. Early breakthroughs have been made in the area of GNC and intelligent sensors, advanced FDIR and smart data handling as implemented in THEMIS. Traditionally much effort has always been spent on planning and scheduling, both, on‐board (e.g. DS1 (RAX), EO1 (ASE)) and ground supported (e.g. MEXAR), whereas in this area mainly the capability of self‐initiated re‐planning and schedule repair contributes to autonomous systems as such.

In this presentation we identify schedule/procedure execution engines as a core asset for ground segment autonomy provided that adequate models like the Space System Model (SSM) are available to support the process of auto‐triggered re‐planning using e.g. predefined alternatives. A relatively new application potentially benefiting from ground based autonomy are

robotic missions implementing telepresence like DEOS or METERON.

For telepresence we highlight possible ways to use ground based physics simulations to support operators and set up early‐warning systems.

****************

Inmarsat: Automation of Satellite and Ground Operations

Rossetti, A; Dickinson, M; Sansone, C Inmarsat, UNITED KINGDOM

Over the past 15 years, Inmarsat's operational concept has changed significantly to make effective and efficient use of automation. Inmarsat has been at the forefront of this area of operations. Using the I4S, the monitoring and control system developed jointly between L‐3 Storm and Inmarsat, it has been possible to implement a highly flexible ground architecture which provides a high level of operational automation. The I4S control system is currently used to autonomously perform all planned celestial operations across the whole Inmarsat fleet ( 12 satellites from 4 different platforms and ground equipment for 7 ground stations) as well as monitor satellite subsystem health conditions , performing the detection and in some cases the rapid recovery from well characterised anomalies.

Automated monitoring and control is achieved in a single manning environment with the satellite controller in a supervisory role to provide full oversight of the scheduled activities, with the ability to take manual control if required, responding to anomalous behaviour as well as executing manual activities. Automation has been deployed in several stages and the development of the I4S has allowed Inmarsat to initially start with the automation of eclipses, blindings, ranging and station keeping operations. This has been extended to include the scheduling and execution of almost all routine operations (e.g. batteries charge control, heaters switching, testing of redundant units, TT&C antenna control ).

Operations are automatically scheduled using request files submitted to the control system with all mandatory details, like start time of activities, unit to be used . These request files are automatically detected and acted upon by specific system tasks, which start the automated procedure for the required operation.

In this workshop we will to present our experience, lesson learnt and describe the tools available to our Satellite Control Centre to support this approach and mitigate possible risks

****************

21

European Technology Harmonisation on Ground Software Systems: Update of Reference Architecture

Reid, S.1; Pearson, S.1; Davies, K.2; Carvalho, B.3 1Rhea System S.A., BELGIUM; 2TERMA, GERMANY;

3Critical Software, PORTUGAL

RHEA leads a consortium of companies that undertaking the latest project for European Technology Harmonisation on Ground Software Systems. The project represents the culmination of a series of earlier activities:

Definition of a Reference Architecture (RA) (led by Critical Software)

Establishing an initial set of standard interfaces (led by Critical Software)

Validation of the initial set of standard interfaces by prototyping (led by Terma)

Harmonisation of Simulation ‐ EGSE Interfaces (Rovsing, Dutch Space)

Control Procedure Execution (CPE) (led by RHEA).

The most recent projects produced a detailed set of recommendations, further augmented by decisions made by the Technology Harmonisation Steering Board (THSB). The purpose of this project is to consolidate those recommendations and update the Reference Architecture (RA) accordingly.

A key element of the work concerns alignment of the Reference Architecture with relevant and emerging standards from ECSS and CCSDS.

Reference architectures for the Operational Control System (OCS) and Electrical Ground Segment Equipment (EGSE) were established and evolved independently, even though a commonality in functionality is universally recognised. A key task of this project is to establish a reference architecture which converges on a 'core' of common functions used in both environments. The design work will therefore establish the core 'building blocks' and their associated interfaces.

The project will also introduce a "Service Oriented View" for the Reference Architecture, not currently implemented. A Service view has been considered in earlier phases, but is now seen as an essential product. It will be especially relevant for establishing service interfaces offered by the 'Common Core' of OCS and EGSE functions and will also play a key role in identifying the relationships between the RA and the ECSS and CCSDS standards.

The project started in March 2011 features a workshop, open to all stakeholders and interested parties. The workshop will present the key challenges for the project, invites debate and aims to achieve consensus on key design decisions that need to be made. The workshop is due to take place in ESOC on 12 May,

immediately after ESAW. The presentation will give an overview of the project and the main topics to be covered at the workshop.

****************

CNES Control Centre mock‐up : an evaluation of a standard SOA architecture

Bornuat, P.1;Cros, P‐A.1;Pipo, C.1;Anadon, M‐L.2;Gelie, P.2 1CS Systèmes d’Information, FRANCE; 2CNES, FRANCE

CNES experience in developing and operating spacecrafts control centres has shown that costs and risks may be significantly reduced by setting up product lines. Accordingly, CNES has decided to develop a new control centre, with an operation deadline in 2016, which should satisfy several main objectives: conform to international space standards (among which CCSDS Mission Operations – MO – standard, and ECSS Packet Utilisation Standard – PUS), reduce possession costs and enhance development process reliability, and aim at some evolutive and re‐usable product line.

The implementation of a control centre mock‐up, has been delegated by CNES to CS as a preparation to future developments in order to evaluate Service‐Oriented Architecture (SOA) together with available technologies and check their suitability to critical subsystems, owing to better agility and interoperability than monolithic systems.

The control centre mock‐up consists of 4 subsystems, composing the Control Centre kernel:

the Command and Control subsystem, in charge of on‐ground/on‐board exchanges i.e. telemetry reception and telecommands uplink;

the DataStore subsystem which offers data storage and retrieval services, and thus plays a central role in data distribution between components;

the Visualisation component giving final users the capability to display, either in real time or offline, any information archived in the DataStore;

the Flight Dynamics component, providing few services, developed to test that MO standard may correspond to Flight Dynamics specific requirements in terms of processing modularity.

Those 4 subsystems compose the heart of a Control Centre, offering solutions to most of major related requirements such as communication with the spacecraft, data archiving and retrieval services together with distribution and visualisation means. Yet, their functionalities have been limited for the mock‐up (reduced PUS services and types of archived data for example).

The control centre mock‐up is entirely based on a service‐oriented architecture in strict accordance with

22

CCSDS MO standard. Fully standardised, adaptable, agile and reusable, it stands as an evaluation platform for new ground segments architecture, and for Control Centres harmonisation question. At last it also enables to validate the interface between ECSS PUS standard for on‐ground/on‐board exchanges and CCSDS MO for ground exchanges.

Although the control centre mock‐up architecture is service‐oriented, it is also module‐oriented; as a matter of fact, all its applications are based on the Equinox OSGi Java‐based framework; moreover, its lifecycle is ruled lying on Eclipse P2 provisioning infrastructure (an OSGi Life‐cycle layer), giving the capability to have bundles installed, started, stopped, updated and uninstalled in this framework.

Both service and module orientations contribute to offering a very agile, scalable and modular resulting system for services providers as well as for client applications.

****************

NOSYCA: the New Operational System for the control of Aerostats Nouvellon, S.

Capgemini, FRANCE

NOSYCA is a fail‐safe ground segment designed to command and control a fleet of stratospheric balloons, operated by CNES. It will allow performing scientific missions, such as atmosphere or astronomical observations. The ground segment includes a Nominal and a Redundant Control Centre (developed by Capgemini), and S band ground stations. A Control Centre allows managing several missions (up to 20 balloons). Two balloons may be monitored and controlled in the meantime. Control Centres may be deployed in mobile units and can withstand frequent installations and de‐installations.

The NOSYCA Control Centres offer the following features:

Remote monitoring and control of balloon equipments, through the high bit rate, S band connection (in nominal mode), and through redundant iridium and inmarstat spacecrafts links;

Complete flight management, including the launch, flight, drift descent of the balloons

Forecast of balloons flight paths, based on aerostat flight dynamics algorithms;

Enhanced MMIs for pilots, operations managers and weather analysts ;

Supply of flight data to scientists and external systems ;

Geographic Information System (GIS) in order to prepare the campaign maps and layers of the various operational sites.

Since the balloons embed heavy scientific payloads (up to several tons), and since the missions may be performed over habited areas, the NOSYCA Ground Segment shall meet strong safety requirements. The ground segment therefore includes critical software, among with: additional software performing double‐checks on the decoded critical Telemetry parameters and double‐checks on the radiation of critical Telecommands. The ground segment also provides a redundant Control Centre, used in case of a general failure of the nominal Control Centre.

The solution provided by Capgemini is based on the following components and COTS:

Octave software components (provided by CNES), which provides the raw Telemetry decommutation software, and MMIs allowing the Monitoring of Telemetry and the radiation of Telecommands.

MDF, which is an Eclipse RCP‐based technology used to develop all Control Centre MMIs

World Wind Java, a Google Earth‐like component, used to display the real‐time trajectories of the monitored balloons.

Cocpit Software (provided by CNES), used to manage the configuration of missions, balloons and Control Centres.

The architecture of NOSYCA is very much based on the reuse of existing software components (traditionally used in the satellite ground segments). This allows providing to the scientific community a reliable, scalable and high‐performance Ground Segment to manage balloon missions, on various operational sites all around the world.

****************

Ten Galileo FOC Payload EGSE Systems – Challenges in Design, MAIT and Schedule

Kubr, H.; Mader, W.; Unfried, C. Siemens AG Österreich, AUSTRIA

Siemens Austria has a long track record in providing EGSE components and subsystems. For Galileo* IOV, apart from Power SCOE and TT&C SCOE, Siemens has been responsible for the Payload Test System (customer Astrium Ltd).

For the FOC phase, Siemens has been selected by Surrey Satellite Technology Limited (SSTL, UK) for the supply of the whole Payload EGSE, which consists of a Service Module Simulator (SMS) covering all the Power‐, Mil‐Bus and Discrete Front‐Ends to the Galileo Payload, as well as the Payload Test System (PTS) covering the RF

23

interfaces to the Payload and providing automated Test sequences to measure critical payload parameters. The PTS Master Test Controller is based on SCOS‐2000, thereby fully exploiting the heritage from the SCOS‐2000 EGSE Reference platform and fully compatible to the SCOS‐2000 based Galileo FOC Core EGSE (provided by Terma to OHB).

The P/L EGSE also provides a high performance Time Reference including Ultra Stable Oscillator with Redundant Active Hydrogen Masers for providing the time reference of the EGSE and measuring the performance of the Payload Clocks (passive Masers). The Thermal SCOE provides heaters/cooling interfaces to the Payload.

Siemens provides the work together with subcontractors, which have as well long experience in EGSE applications: SSBV for the SMS hardware and Terma for the SMS software and Thermal SCOE. The technical challenges are not only to integrate complex subsystems, but also to manage a highly demanding delivery schedule to provide 10 P/L EGSE systems in the course of 2011. 5 Systems will be installed at the P/L integration site in Guildford and 5 at the S/C integration at OHB Systems in Bremen. The P/L EGSE project has been started in March 2010 and has reached CDR in September. The first delivery to SSTL took place in February, 2011 and the shipment of the first system to OHB is scheduled for April 2011.

‐‐‐ * Please note that the term "Galileo" refers to the "satellite‐supported European Navigation System".

****************

GSMC ‐ Ground Station Monitoring & Control Riccio, F.1; Lannes, C.2

1Logica Deutschland GmbH & Co. KG, GERMANY; 2European Space Agency ESA/ESOC, GERMANY

The GSMC Implementation is the implementation and detailed design phase of the Ground Station Monitoring and Control system. As part of the project is also included the Common Monitoring and Control Platform. The project is representing the next generation of the Station Computer2 and Monitoring and Control Station which represent the current system used for monitoring & control Ground Stations. Integration, reuse of existing code, new challenging implementations in new area never explored before (i.e. WAN problems including low bandwidth and delayed communications links) are the key issues of this project. The GSMC will replace systems that have been in use for many years. These existing systems have been continuously maintained and any problems with reliability have long since been ironed out. As such these systems have gained the trust of the ground

station engineers. The driving factor behind the development of the new GSMC is to provide much needed new functionality to allow much more flexibility and provide improved capabilities.

The baseline for development of the Common Monitoring and Control platform is the generic MCS control system SCOS‐2000. While this system has continuously been improved over the years, it has been designed to be used on a Local Area Network. One of the major changes for the GSMC development is that the new system will be distributed over a Wide Area Network with limited bandwidth and high latency. Server components will be located at the ground stations, however the operator workstation may be located at a remote location, typically at the ESTRACK Control Centre at ESOC.

The existing Ground Station Tailoring System (GSTS) is another important aspect considered critical for this project. The GSTS has been in use for a number of years, significant usability improvements can be made when providing its replacement. The main goal is to produce a system that will be a welcome improvement over the current systems in place and with allow engineers to undertake day to day activities in a much more efficient manner.

The EGOS User Desktop as well will be supplying the majority of graphical user interfaces for the GSMC by also including substantial new implementations like MIMICs and Matrix displays.

****************

Evolution of FEC architecture Fernandez‐Ranada, I1; Fuentes, A1; Perez, R1; Droll, P2 1TCP Sistemas e Ingeniería, SPAIN; 2European Space

Agency, ESA/ESOC, GERMANY

The FEC, the Front‐End Controller system, is a key element of ESA's Ground Segment infrastructure. It provides critical functions required for establishing and maintaining the communication with the spacecraft. It is furthermore an intelligent subsystem used for the monitoring and control of the equipment installed in a ground station antenna. The FEC evaluates and combines monitoring information in order to control the equipment according to predefined algorithms. These algorithms have been verified and improved during years of routine operations, LEOP's and spacecraft emergency cases.

The current Front‐End Controller installed in all ESTRACK antennas, is the result of the porting of the FEC MkIII on a Motorola‐VersaDOS platform to a MS‐Windows platform. During the last ten years several new functions have been implemented, which implied the development of many enhancements and

24

improvements in the functionality of the system, but not in its architecture.

One of the major drawbacks of the current system architecture was the insufficient separation of the ground station dependent and ground station independent software modules. Already minor changes related to the monitored devices affected immediately the system code, resulting in undesired side‐effects/ misbehaviour and unnecessary effort for the software maintenance. In order to make the FEC independent from the logical distribution of the devices, the architecture of the system has been modified. E.g. device drivers can now be added, removed or updated from the FEC purely by tailoring the FEC software.

The so called FEC World is the heart of the data representation of the FEC. Previously, the definition of the FEC World tree defining the parameter ID, type, initialisation of values, etc. was hardcoded. Now all these information is read directly from the FEC World database and the FECW tree is automatically initialized.

An important step to make the FEC software independent from the ground station was the introduction of truth tables for the derivation of monitoring parameters. The (logical) relationship between parameters is defined in matrixes, which can be modified without affecting the code.

Another aim in the frame of the FEC enhancement is the harmonisation of the FEC system with the other ESA ground segment software systems, within the EGOS initiative. The future FEC will run on the recommended baseline OS, which is currently Linux SLES 11, 64 bit. In order to ease future porting, it was decided to implement it as a multi‐platform system. All system calls were moved to common libraries, and these were developed to work for Linux and Windows OS. The result is a code capable of working in both platforms.

This paper is aimed at describing the strategy followed for the design and implementation of these architectural enhancements within the FEC. It will discuss the results obtained and the experience gained during this period.

****************

Exploiting ESOC infrastructure over the long term Patrick, R

Terma A/S, DENMARK

It is nearly 10 years now that a wide range companies and organisations have been exploiting ESOC ‐ software ‐ infrastructure products for their own purposes. The most widely used of these is SCOS‐2000. This paper looks at how we at Terma have managed to exploit the opportunities and our experience over the long term of

remaining aligned to the "core" product development within ESOC. We also identify some lessons learned that should be fed into current initiatives for developing such infrastructure products.

****************

Satellite Control Systems Provision and Maintenance Choices

Tortosa, M. Eutelsat, FRANCE

Eutelsat satellite control facilities operate 23 satellites on‐station and permits to supports LEOP operation for new launches. The initial satellite control software was based on European Space Agency technology. New systems and facilities have been implementing taking advantage of the open nature of the the initial deployment. This has permitted to cope with new requirements for the control of more complex and powerful satellite platforms and to enhance operability. In the implementation of these enhancements preference is given to develop on open software rather than on proprietary products that are expensive to procure and even more expensive and difficult to maintain over the long term. This permits to build up infrastructure that can be reused in future implementations. Such an option has the ability to adapt progressively to changes in the operation or the maintenance process. It permits the introduction of new technology or of capabilities than in other circumstances result in adding stress to the operation and to the organisation of the work. Presentation topics will include: ‐ Evolution of the systems used by Eutelsat for satellite control. ‐ Multi‐mission environment: the challenge of reducing complexity and operational costs; ‐ Key topics in the provision and maintenance of ground control systems. ‐ Multi‐purpose design: develop once and use in many ways. ‐ Building up on Web technology. ‐ Lessons learnt: strengths and issues. The presentation will try to encourage the exchange on the above areas to come up with the grounds for successful outcome and with problematical issues.

****************

Ground Station Network for Micro/Nanosatellite Operation

Kurahara, N.1; Shirasaka, S.2; Nakasuka, S.1 1University of Tokyo, JAPAN; 2Keio University, JAPAN

For last decade, satellite research and development in the Universities or small businesses have been getting popular. Dozens of micro/nano‐satellite, which weighs only tens kg, development projects are ongoing in all

25

over the world. The micro/nano‐satellite development cost is a few hundredth of a percent of bigger satellite. Great cost down contributed the quick spread of micro/nano‐satellite development. In the meantime, more than 10 Japanese micro/nano‐satellites launched and successfully operated in space since 2003. In March 2010, governmentally funded program "New Paradigm of Space Development and Utilization by Nano‐satellites" was kicked‐off, and "Innovative Nano Satellite Technology Center (INSTEC)" in University of Tokyo is coordinating the nation‐wide activities to establish an innovative architecture, development process and utilization ways of micro/nano‐satellite, in order to pursue the possibility of making micro/nano‐satellite viable players of space industry and utilizations. Over the next three years, INSTEC aim to develop and launch five satellites with business centered missions. Micro/nano‐satellites have begun to play important roles not only in the field of education, but also for practical applications, including space sciences, signal acquisitions, technology demonstrations, Earth observations, entertainment, etc. However, in order to make micro/nano‐satellites more attractive candidates for such applications, more extensive studies will be needed in the field of subsystem technologies, architecture, systems engineering, and so on. Especially ground system architectures suitable for micro/nano‐satellite application should be considered. Collaborative micro/nano‐satellite operation network is very important to increase the telecommunication time with low cost. Easy and frequent access to the satellite is necessary to increase the number of end user and to commercialize the micro/nano‐satellite. INSTEC started a discussion for standardization of micro/nano‐satellite operation network with world‐wide players. A goal of the discussion is to make a system which provides an easy way to connect collaborative ground stations for all micro/nano‐satellite operators. Data format, protocol, security issue, legal issue etc. are discussed.

****************

Development of SODAs for Improving Efficiency and Security for Satellite Control

Techavijit, P.; Sirikhant, A.; Detpon, A.; Tongpan, J. Geo‐Informatics and Space Technology Development

Agency (GISTDA), THAILAND

Satellite controlling and monitoring are the main responsibility of Satellite Operation and Control team (SOC) at THEOS Control Ground Center, Siracha Chonburi since THEOS (THailand Earth Observation Satellite) was launched on 1st October 2008. SOC Operators perform Telemetry downlink in order to acquire Housekeeping Data, S‐Band control and Telecommand uplink in order to send mission program and specific operational commands to the satellite. This requires precise operations within each visibility (lasts approximately 10 minutes), therefore all SOC Operators

need to be well trained and passed through numerous qualification processes. In order to assist the operator and to reduce human error, specific templates are used while preparing commands and recording real time monitoring of satellite parameters. However there are errors from operators when finding data in limited time, error in log book recording due to the different standard of operators, error during data transferring. Other constraints include data searching, data storage area and operational briefing discrepancy. To address all these issues, SOC team has developed active tool called SODAs (Satellite Operational Dynamic Assistant System) which replaces paper based template. SODAs, developed in Web application and Windows application formats, can be used for preparing set of commands and record real time satellite parameters in electronic form. SODAs is also capable of estimating commands duration, calculating plan number for security and generating operational report. The simplified graphic user interface allows operators to fill in data correctly. All operational data is then archived in electronic database system that allows quick access. SODAs is designed to assist operator in THEOS Operation in order to increase efficiency, and reduce errors. It is designed also for the next generation of THAILAND’s Satellite as well.

****************

Ground Segment Security: light and shade Vivero, J

GMV, SPAIN

Traditionally ground segments design and implementation has been focused on availability: multiple sites, redundant systems and networks, spare equipment, etc. In contrast, confidentiality and integrity dimensions of information security have relied in assumptions that no longer (if ever) apply: physical isolation of the ground segment systems and networks, specialized knowledge only accessible to a few, trustful employees never attempting a malicious action, lack of interest to attackers due to absence of financial transactions, etc.

Nowadays reality is certainly different. Business requires more connections from the outside to provide higher value to customers, outsource more activities to external providers, reduce the time to access for on‐call administrators… Knowledge is, nowadays, easily accessible to anyone with enough interest and time. Motivations for attackers are more varied than ever: they can range from revenge by disgruntled employees to highly organized groups and even governments investing significant quantities of time and effort to reach their goals (e.g. extortion, espionage, cyber sabotage, cyber war...).

26

Space agencies and organizations are progressively gaining awareness about this situation and slowly introducing safeguards to fight these threats. However, there are lights and shade in the introduction of safeguards within ground segments. On the one hand, ground segments provide two very interesting properties from the security point of view. First, all ground segments have the same conceptual design: with modules that provide telecommand and telemetry, mission control, flight dynamics, etc. This enables the definition of a conceptual security framework which would, with some adaptations, suit as a general solution and reduce significantly the effort in a case by case basis. Second, ground segments are typically stable in nature. Once they are implemented, they suffer few changes during their lifetime (that usually spans for decades) and changes are always carefully planned and scheduled. Such property permits a tight definition of the expected behaviour of the ground segment and the enforcement of such behaviour to avoid and detect security anomalies.

On the other hand, safeguards to be efficient require a combination of knowledge which is hard to achieve or find. It requires i) detailed knowledge about ground segments, so that the safeguard integrates smoothly within the environment and does not create more harm than benefit; ii) knowledge about information security management to ensure that the safeguard is aligned with the business; iii) knowledge about security assessment methodologies to target first those threats that introduce the higher risks and finally, iv) wide knowledge about security technologies and solutions to be able to select the best alternative, even if it was initially foreseen for another sector.

The presentation will review all these issues and provide recommendations about the steps to be followed for a consistent information security approach. It will also describe a small example of security solution initially foreseen for a different sector (ATM security) but which fits very well within the Ground Segment: Checker.

Checker enables centralized administration of systems security, including control of which applications are allowed to execute and what resources each application is allowed to access.

****************

Automated Computer Network Defence Wiemer, D.

Defence R&D Canada, CANADA

Information Technology (IT) solutions are essential aspects of critical ground systems supporting space missions. Unfortunately, IT solutions also provide an avenue for cyber attackers to compromise systems and conduct acts of espionage (loss of confidentiality), Tampering (loss of integrity) and denial of service (loss of availability). Without the aid of automation, the complexity of IT solutions makes it increasingly difficult to identify appropriate cyber security courses of action that will optimally mitigate attacker capabilities while minimizing the impact to critical operations. Fortunately, advances are being made in the area of Automated Computer Network Defence (CND) that will significantly improve the ability for security and network operations personnel to optimize and prioritize courses of action to mitigate identified vulnerabilities and respond to cyber security incidents. This presentation will describe some advanced technology and operational concepts supporting Automated CND as well as provide an overview of projects were these concepts are being applied. An illustration and description of a logical architecture supporting Automated CND will be included in the presentation.

****************

SOA4GDS: Evaluating the Suitability of Emerging Service based Technologies in Ground Data Systems

Parsons, P1; Walsh, A2 1The Server Labs, SPAIN; 2VEGA, GERMANY

The SOA4GDS project is an ESA Basic Technology Reseatch Project (TRP) study that has been conducted jointly by The Server Labs and VEGA to evaluate the suitability of emerging service based technologies (i.e. SOA) in the context of ESA/ESOC's griound data systems. Service based technologies have been widely and successfully adopted within computer industry for many years as they provide a means to decouple system components and applications making the system as a whole more flexible. The study focused on the suitability of the Service Component Architecture (SCA) and Java Business Integration (JBI) standards. In addition, the Business Process Execution Language (BPEL) and OSGi standards were also evaluated. The study approach was based on iterative rapid‐prototyping of a representative SOA based Data Distribution System integrating with ESOC's FARC and

27

DARC applications. In order to facilitate the prototyping within the study a Cloud based approach was adopted for both for the SDE tools used within the study and the test and development environment. This also demonstrated that selected parts of the ground segment are suitable candidates for deploying in the Cloud.

Service Component Architecture (SCA) provides a technology agnostic model, both for the composition of services and for the creation of service components. SCA is designed to be heterogenerous, that is to say components can be implemented in several languages (Java, C++, etc) while separating the communication with the component from what the component does.

One of the problems often found in SOA projects is reaching the correct balance between coarse‐grained services that should be consumed over the net and fine‐grained services. SCA solves this with a composition model that supports multiple layer recursive assembly of coarse‐grained components out of fine‐grained tightly coupled components.

The Java Business Integration (JBI) specification defines a standardised integration platform between service consumers and providers that as the name suggests are written in Java. JBI is complementary to SCA and is a good framework for implementing integration logic that can be cleanly separated from applications services. Many JBI based ESB products offer good selection of protocol adaptors which enable the integration of systems using a variety of communication protocols.

We shall present the findings and conclusions of the study, which were generally very positive with regard to the suitability of the SOA technologies considered and which potentially could shape the development of future ESA/ESOC ground data systems.

****************

Modern Frameworks ‐ The Fantastic Four Villemos, GV; James, S.; Doyle, M.; Klug, J.

Logica, GERMANY

Modern space missions of today are gaining rapidly in complexity. The number of organisations both national and international along with their differing systems continues to increase. This complexity is driven by the ever increasing needs to integrate diverse systems, realise differing complex mission requirements and manage efficiently and cost effectively infrastructure baselines.

A key element of achieving this is simplicity and flexibility. Two often cited, frequently claimed, and rarely delivered features of modern IT systems. Yet a new generation of OSS middleware frameworks have emerged, based on new concepts of how to assemble and connect systems, that provide exactly these features. Most of these have been developed as a reaction to the complexity of existing solutions.

At the core of the new paradigm lies a complete decoupling of dependencies; Business components should not know or care where in the processing chain they operate or how they communicate. The routing of message to and from it is managed by the framework, based on the user defined assembly, as well as intelligent algorithms based on convention over configuration, and reflection.

This concept is very similar to the SOA idiom of atomicity of services and loose coupling, but current SOA platforms typically fail to deliver on simplicity and the associated costs can be high. These new frameworks offer an alternative path. They have aimed at delivering simplicity and flexibility, automating as much as possible. They provide proven solutions to meet the challenging integration needs of future missions.

Four OSS middlewares, each complementing the others, have been used extensively by Logica over the last years namely, Spring, Camel, Activemq and Jetty with Cometd. Together these provide an amazingly flexible and powerful framework, facilitating the development of complex systems in a matter of hours. When coupled with libraries that support platform and language independent data structures supporting complex data exchanges a complete development stack emerges.

28

This paper describes the evolution of programming paradigms, from closely coupled systems, over SOA, to extremely loosely coupled, highly configurable and modular systems. Using a concrete example this paper will demonstrate the potential of these frameworks to reliably and cost effectively meet the future needs of missions.

****************

Leveraging EGOS User Desktop and hifly® to evolve SCOS‐2000

Casas, N; Estévez, C GMV, SPAIN

At some point in time, ESOC created the EGOS User Desktop framework, providing a client application platform based on Eclipse RCP Java technology. The EGOS User Desktop (EUD) enables the dynamic composition of user interfaces to access different ESOC systems in a decoupled way.

In parallel, GMV faced the challenge of reengineering its SCOS‐2000‐based satellite control system hifly® to replace the User Interface layer that relied on a proprietary C++ API in favour of Eclipse RCP. GMV took the opportunity to aim at a more ambitious twofold goal: driving the whole system into a Service‐Oriented Architecture (SOA), plus creating a plugin‐oriented application platform that enabled client displays to be composable.

The result of such architectural refurbishment consists of a new C++ service layer that exposes high level domain logic from hifly, a set of Java service adapters that encapsulate the actual transport protocols and a group of Eclipse RCP components and displays to replace the old graphical user interfaces.

Given the high degree of alignment of SCOS‐2000 and hifly, ESA capitalized on GMV's experience to develop the next generation of their MCS user interface layer based on the EGOS User Desktop. The ongoing project S2K2EUD aims at applying to SCOS‐2000 a reengineering analogous to that of hifly, reusing the service layer and user interfaces developed for it, but using EUD as the system foundation. Integration of other Java based source code from other systems such as displays from EUD‐SMH and MICONYS is also foreseen.

An Agile approach has been followed throughout the life‐cycle of the project. Continuous feedback from both users and technical staff at ESOC ensured that displays usability expectations and maximum functionality reuse could be achieved while coordinating with developments in other projects such as Ground Station Monitoring and Control (GSMC) development.

The new system architecture opens up the door to scenarios that were not feasible before, either technically or in terms of effort: displays can be combined in applications to fit the needs of each mission; the fully decoupled user interfaces can now run remotely on machines where SCOS‐2000 is not installed, so in principle even under other operating systems; the isolation of the dependency on CORBA by means of

service adapters makes a future replacement of the protocol in the communications between server and client possible; finally, the Java service adapters could be reused for exposing SCOS‐2000 domain logic via an Enterprise Service Bus (ESB) to boost the interoperability of the service layer.

****************

Improve Usability of Graphical User Interfaces with New Technologies in Ground Centre Software Marty, S.1; Volland, S.1; Cros, P‐A.1; Bornuat, P.1;

Anadon, M‐L.2; Gelie, P.2 1CS Systèmes d’Information, FRANCE; 2CNES, FRANCE

These last years, software and hardware front‐end technologies, meaning technologies in which users directly interact with, have been subject to major changes. Ground segment software may strongly benefit from these technologies, which may improve their usability, and therefore strengthen operators efficiency and satisfaction.

CNES has decided to develop a new control centre product line, so as to significantly reduce development risks and costs. In order to evaluate several emerging technologies, CNES has delegated to CS the implementation of a control centre mock‐up. This mock‐up integrates a telemetry‐monitoring application, designed and developed by CS, which goal is, in terms of look and feel, to simplify user interactions and improve the quality of graphical user interfaces. By bringing more fluidity to the user's workflow and increasing information visibility and accessibility, the user can focus on "what to do" rather than on "how to do". CS has compared two distinct technology mainstreams, on one side a Desktop application, and on the other side, a Web application, including on both sides the same functional scope. The desktop application is based on the future "E4" Eclipse Rich Client Platform (RCP), a cross‐platform application framework based on the Java programming language. The web application is built on top of Google Web Toolkit (GWT) and many other related "Web 2.0" components, taking advantage of both Java and Javascript technologies.

This paper presents the main advantages and drawbacks of each solution. Besides user experience and graphical interfaces, it also focuses on software modularity, programming architecture and real time performance for both approaches. Moreover we also introduce an innovative way of managing and interacting with temporal information in ground segment software.

****************

29

Telemetry Archiving: How To Optimise Storage Efficiency, Retrieval Speed And Real‐Time Performance

Kumpf, C.; Foweraker, R. MakaluMedia GmbH, GERMANY

Over the last two years, Makalumedia GmbH have developed a high performance telemetry data archive for Eutelsat. This archive is the data storage component of the TeleViews System and it stores change‐only telemetry data for all satellites (currently 24) in the Eutelsat fleet on two dedicated servers.

At the beginning of the project we performed a review of existing archive systems. None of these archives exactly matched our requirements or expectations. We made the decision to develop our own system.

In this presentation, promised at the last ESAW Workshop in 2009, we describe the design of this archive. The archive supports very fast data retrieval speeds along with quasi‐live streaming. Data is stored very efficiently compared with other telemetry archives that we have studied.

The design is very scalable and it is straightforward to add new satellites or move data between servers without interrupting the availability of the archived data.

Archived telemetry data is made available to other applications, including the TeleViews web application, via a simple HTTP interface. Data is currently served in either JSON or CSV formats and extension to other formats is straightforward. The archive also supports several statistical calculations, for example minimum, maximum and average, over any desired time interval and sampling period.

****************

Towards a high performance LEON/GRLIB Emulator Marchesi, J.E.

Terma GmbH, GERMANY

The ESOC ERC32 Emulator is a fully functional high‐performance processor emulator implementing the SPARCv7 micro architecture and the devices found in the standard ERC32 chips developed by Atmel. Now that LEON2 and LEON3 based on board computers are being used in ESA missions, the modification of the ESOC Emulator to support those later processors is being considered by Terma. The primary usage of such an emulator would be in Operational Simulators developed by ESOC. This paper is, unlike Gaul, divided into three parts. The first part contains a brief but detailed discussion on the differences between ERC32, LEON2 and LEON3, focusing in the issues having an impact in the emulation. For example, we have to consider the modular nature of LEON3 based systems:

while ERC32 and LEON2 systems are predefined SOCs (system on a chip) LEON3 based computers are constructed by several reusable IP cores distributed around a common on‐chip bus. That means that the entity to be emulated becomes a customizable collection of quite different components. Other examples are the differences introduced by the SPARCv8 micro architecture and the usage of pipelines and the instruction cache. The second part uses that analysis to produce a set of needed and desirable characteristics for a LEON3 emulator. For example, given the modular nature of LEON3 it comes that the emulator suite shall be modular and flexible, allowing the easy addition of new emulator models. Likewise, given the new functionality introduced by the pipeline and the instruction cache, performance becomes an important issue. Finally, the third part applies those generic considerations to the concrete case of the ESOC Emulator, and proposes an architectural solution for turning it into a fully functional LEON/GRLIB Emulator, suitable to satisfy ESOC's needs.

****************

A Netpdl Based Prototype Implementation of Galileo Attitude Orbit Control System Scoe Controller, and an Overview of Netpdl Utilization in Network Ground

Software Components. Bertoli, A.1; Risso, F.2

1Carlo Gavazzi Space, ITALY; 2Politecnico of Turin, ITALY

The SCOE controller is a software component in charge of interfacing SCOE equipments with the EGSE core allowing the remote control of the equipments itself. SCOE equipments include custom subsystems, COTS instrument and specific devices to be interfaced with the unit under test. Since these items have a specific and often custom communication protocol, the SCOE controller must manage the connection and the communication of these devices using different protocols. Protocol with textual or binary packet format should be harmonized, converted and packetized before of routing them to the EGSE Core and managed by SCOS2K. Up to now the protocol diversity of each equipment connected to the SCOE controller induces constraint in the design and problems in the standardization and code reusing of a important component as the SCOE controller. Every SCOE controller must be suited to meet the need of the specific protocol and the related application must be always modified or developed again. Obviously, this way of operating is not efficient: developing everything from scratch is costly, time consuming and it may replicate many features (hence bugs) that are common among different applications and in different network technologies. A prototype work carried out at Carlo Gavazzi Space S.p.A. (Milan, Italy) and Politecnico di Torino (Turin, Italy) may offer a solution to this problem. A new

30

language has been proposed by the Politecnico di Torino that allows to define the format of protocol headers once, to be reused by different applications on different network technologies. This language, called NetPDL (NETwork Protocol Definition Language) is simple, intuitive and XML‐based and it can be used to define the header format and protocol encapsulation for ISO OSI layer 2‐7 protocols. We are progressively extending previous results, obtained in the classical TCP/IP world, to the space domain, by developing NetPDL descriptions of many protocols belonging to the space telemetry and control domains, testing their effectiveness on our applications, and integrating those components in some typical space computation environments (i.e., operating systems, etc.). One of the most recent result refer to the possibility to support multiple instruments or devices (e.g., Antenna Control Unit, AOCS equipments, COTS instruments and more) that transmit their data toward a SCOE controller; a NetPDL‐based protocol translator reads the incoming packets in the native protocol format, translates all the messages into the protocol understood and sends them to the EGSE core usually implemented by SCOS2K. The process is repeated the other way round when the EGSE core delivers a command to the equipment/instrument. A prototype implementation of NetPDL has been performed for Galileo Attitude Control System SCOE. In this realization the SCOE controller is in charge of converting the internal protocol of the AOCS EGSE host computer to EDEN protocol used for SCOS2K data handling. The NetPDL technology has been successfully validated converting a AOCS EGSE textual protocol to the EDEN EGSE core protocol simply describing the exchanged packet by XML at high level and avoiding code implementation and successive direct modification. Moreover, once the protocol has been described, it becomes available for all the application that make use of that protocol database, extending the protocol library supported by the language. Starting from the NetDPL XML is also possible to automatically obtain the SCOS2K Mission information based table to be imported in SCOS2K for SCOE data management. The implementation has also demonstrated the potentiality of the NetPDL language in several network ground software components implementation as follow: network packet sniffer, network packet filtering, network packet classification and packet acknowledgement, network packet error injection and generic network packet translator. The implementation has also demonstrated the potentiality of the NetPDL language in several network ground software components. Particularly, a packet filter is able to select a given subset of traffic (e.g., EDEN packets that have a specific value into a given protocol field), a protocol classifier can detect which application a packet belongs to, a protocol decoder can return the list of all the fields contained into a packet, and a generic network protocol translator can translate the content of a protocol A into a payload formatted

according to the rules of protocol B. Additionally, we are able to generate acknowledgement packets, and perform network packet error injection. This talk aims at giving an overview of the NetPDL technology and to present the recent findings on this topic, highlighting whether (and to what extent) this technology can bring benefits in the space environment. Finally, it will also point out the current limitations of this approach and the possible future directions.

****************

Integrated Test Concept and Test Automation for Aerospace Projects

Hofmann, J. T‐Systems, GERMANY

The European Space Agency (ESA) and its subsequent organisations periodically face great challenges when integrating, testing and verifying new satellites. The situation is intensified when requirement threads and information flows down to test procedures, test reports and test data are disconnected due to different industrial partners involved.

T‐Systems as a strong partner for global companies and European public institutions in the area of Communications and IT Technologies (ICT) have developed an Integrated Test and Automation Approach which has been verified in numerous projects within and outside the aerospace industry. The concept comprises the processes, tools and methods needed during the verification phase of complex development programs and is established by the following principles.

Rigorous analysis of requirements in conjunction with coordinated distribution of derived test requirements to the best suited test levels and stages

Optimized mixture of manual and automated tests in strict consideration of technical and commercial aspects

Early design of integration‐ and acceptance tests (‘end to end tests’) with derived requirements for e.g. the EGSE and other test support tools

Integrated data and document flow system shared between the main contractor and her suppliers, providing a high level of automated documentation and enabling strict configuration control

Effective validation of the satellite system and SW design, considering especially the dependencies within the systems.

The presentation gives details to the above principles and offers an IT architecture which supports the validation and verification process across the borders of companies and organisations.

31

****************

CCSDS Mission Operations Services ‐ Current Status Cooper, S; Thompson, R SciSys, UNITED KINGDOM

The CCSDS Spacecraft Monitor and Control (SM&C) working group is working on the specification of a Mission Operations (MO) service standard.

The working group is standardising three aspects of space services:

A set of application services for the mission operations of spacecrafts : Services currently identified are Monitor & Control (commands, parameters and events), Time, Planning, Automation, Scheduling, Data Product Management…

A set of services for the support of common infrastructure : Services currently under development are Login, Service Directory, Operator Interaction, Historical Replay and Retrieval, Configuration Management.

A Message Abstraction Layer (MAL) (Published CCSDS Standard) : Provides an abstract messaging model that separates the physical representation of messages 'on the wire' from the physical representation in a specific computer implementation language.

The main characteristics of this architecture are:

Extensible Framework: Common and Generic Elements

Distributable: Independent of Deployment Architecture

Protocol Agnostic: Independent of Transport Technology

Language Neutral: Independent of Deployment Language

The central ability that the MO concept is based on is the MAL. This defines an abstract model for basic data types (float, Boolean, integer etc) and how these may be combined together into composite structures and lists. Any service is then defined in terms of the abstract data model and the messaging patterns provided by the MAL.

Mapping transformations from this abstract model to a communications technology allow messages to be transmitted across a specific technology without requiring any knowledge by the transport of the higher applications, and mapping transformations to a programming language allow applications to be developed without requiring knowledge of the underlying messaging technology thus allowing it to change with affecting the applications.

With the publication of the MAL standard by CCSDS, the working group is moving its attention to the application services; this presentation covers the work to date, the status of the standardisation effort, and road map for the future.

Current activities include the development of a standard service template; specification of the first application level service addressing Parameters, Actions and Alerts; and development of technology mappings for Java and Packet TM/TC.

****************

Where do we stand with CCSDS SM&C at CNES ? Poupart, E.; Pasquier, H.

CNES ‐ Centre Spatial de Toulouse, FRANCE

CCSDS Spacecraft Monitor and Control (SM&C) Working Group (WG) is now in a very productive phase with three published books and many prototyping exercises during 2010, and with many others publications expected during 2011.

This presentation will describe CNES involvement in this standardisation effort and the expected benefits for the future software implementations in the new CNES control center product line standardised with ISIS.

MO SERVICES ROADMAP

The presentation will recall the current CCSDS status of those SM&C specifications and CNES involvement in Java MAL API and SM&C generic and specific encoding specifications.

MO SERVICES PROTOTYPES

The formal prototyping required by CCSDS for the MAL has been successfully carried out in cooperation by CNES and ESA. The tests have been completely automated. 2105 tests have been run, in 8 different deployments, for a total of 16840 individual tests. The two implementations interoperated perfectly! In addition, many other prototyping exercises, involving NASA, DLR, CNES and ESA, have been successfully completed and showed validity of concepts and gave answers to performances issues.

The presentation will focus on the most recent feedbacks coming from the different CNES prototypes and studies.

MO SERVICES FOR NEW CNES CONTROL CENTRE PRODUCT LINE

32

CNES has undergone to define a future evolutionary Control Centres product line for its future missions (2015/2030) with CSO as first candidate mission. The foreseen architecture is service‐oriented in accordance with CCSDS MO standards.

Once the first product line architecture elements have been defined, it has been decided to proceed through a mock‐up development in order to focus on various major topics either related to technological issues, real‐time performance requirements or that are at the very heart of the foreseen architecture. Two presentations of this control centre mock‐up are submitted to ESAW 2011.

CONCLUSION This abstract has described the approach adopted by the SM&C WG to standardize the service interfaces between major components of a space mission operations system. The approach allows for software language and technology independence and thus permits in theory reusability, long term maintainability and total cost of ownership reduction.

A key challenge for the future will be to demonstrate how the MO Service framework can coexist with emerging industry standard service frameworks, such as SCA and many others. There may be clear benefits to deploy MO Services over such frameworks, given the number of additional capabilities and technology bindings these frameworks may bring without the need for additional development effort. Such frameworks do not, however, address the application specific service models addressed by the WG. Further work is needed to see how the MO service framework can be deployed over such technologies and whether any further harmonisation is required within emerging industry standard service reference models, such as OASIS. We can hope some answers to this question in a very near future.

Glossary AMS = Asynchronous Messaging Service COM = Common Object Model MAL = Message Abstraction Layer MO = Mission Operations services SM&C = Spacecraft Monitoring and Control SOA = Service Oriented Architecture WG = Working Group ISIS = Iniative for Space Innovative Standards

****************

Space Internetworking and DTN Prototyping: Evolutions in the Space Communications Architecture Fowell, S1; Wheeler, S1; Stanton, D2; Farrell, S3; Taylor,

C4; Viana Sanchez, A4 1SciSys UK Ltd, UNITED KINGDOM; 2Keltik Ltd, UNITED KINGDOM; 3Tolerant Networks Ltd, IRELAND; 4ESA

ESTEC, NETHERLANDS

INTRODUCTION

This paper describes the Space Internetworking and DTN Prototyping project, which is defining a reference space communications architecture with a Network Layer using the CFDP and DTN protocols and providing packet‐ and file‐based operations encompassing prioritised commanding, network management and emergency commanding, under an ESA TRP contract.

EVOLVING SPACE COMMUNICATIONS ARCHITECTURE

Existing file‐based communication with spacecraft has tended to be an ad‐hoc affair using bespoke protocols and operational procedures, without the provision of a clear Network Layer as identified in the OSI communications model, leading to limited flexibility and high levels of effort to manage.

Recent developments in space communication protocols promise to move this to a more capable and, through standardisation, re‐usable basis. The CCSDS File Transfer Protocol (CFDP) is a standardised file transfer protocol for space, encompassing protocols and procedures for transferring files between ground and spacecraft, including via waypoints such as data relay satellites.

Disjoint/delay Tolerant Networking (DTN) represents an evolution from CFDP of its store‐and‐forward capabilities through the introduction of a dedicated bundle protocol, LTP, at the network layer that is tuned for long‐delay and disrupted communication links. DTN and LTP are currently being developed by the IETF and CCSDS.

Together these are enablers for a more automated communications architecture for transfer of data for deep space and planetary missions, as illustrated for example in figure 1.

In support of this, the Interagency Operations Advisory Group’s (IOAG) SISG (Space Internetworking Strategy Group) has recently published an Operations Concept for a Solar System Internetwork (SSI), defining a set of reference missions, operational concepts and an end‐to‐end communications architecture.

However, as with the introduction of any new technology, their impact on existing practises and how

33

they should be exploited must be carefully studied and planned for.

Initial studies have already been performed into defining operational concepts and into defining and profiling the reference communications architectures. Refinements to the resulting recommendations have been identified as being required to address the following areas:

Prioritisation of commanding; Support for emergency commanding of nodes

“beyond the first hop”; Support for network management functions) (e.g.

clearing relay node buffering, command re‐prioritisation);

Better understanding of the performance of the protocols, especially with regard to the effect of individual link availability in end‐to‐end communications and the load placed on relay nodes.

MISSION SCENARIOS

A variety of mission scenarios have been studied, from EO satellites through to science spacecraft at L2 and planetary landers, looking at communication architectures and operational concepts.

REFERENCE SPACE COMMUNICATIONS ARCHITECTURE

The reference space communications architectures from the prior study have been updated, taking account of the identified required refinements.

SPACE COMMUNICATIONS SIMULATOR

To better model the mission scenarios and the performance of the reference mission architectures, the SIMSAT/GSTVi‐based Simulator built in the prior study will be refined as follows:

Additional mission scenarios simulated, e.g. science spacecraft at L2, Lunar landers;

Addition of modelling of resource usage on nodes; Addition of an orbit propagation model; Higher fidelity modelling of orbiter‐to‐lander

communications link; Improved automation of simulation runs and test

result analysis.

Together this will allow investigation and fine‐tuning of the communications architecture for the various mission and operational scenarios and in particular the protocol configurations, so as to provide recommendations as to the optimal configuration of the

reference communications architectures and the expected resulting.

This simulator incorporates a Java implementation of CFDP that SciSys has developing for ESA and DTN2 an open‐source DTN implementation containing major contributions from TCD.

AVIONICS LABORATORY PROTOTYPING

Finally a prototype of the reference communications architecture will be deployed on the RASTA Avionics Test bed in ESTEC’s Avionics Lab, so as to:

Validate results of simulations using flight‐representative hardware and software;

Build demonstrator for integration with future end‐to‐end mission prototypes, e.g. METERON.

This will build on the existing reference SOIS, PUS and CFDP spacecraft configuration that SciSys has developed for ESA and incorporate use of ION, JPL’s open source implementation of DTN.

****************

Space Data Routers for Exploiting Space DATA Goetzelmann, M.1; Tsaoussidis, V.2; Diamantopoulos,

S.2; Amanatidis, T.3; Daglis, I.4; Ghita, B.5 1VEGA Space GmbH, GERMANY; 2Democritus University of Thrace, GREECE; 3Space Internetworks, GREECE;

4National Observatory of Athens, GREECE; 5University of Plymouth, UNITED KINGDOM

"Space‐Data Router (SDR)" is a device specifically designed for the dissemination and exploitation of space data. SDR integrates Delay‐tolerant networking (DTN) software and implements interfaces to both terrestrial and space internetworking protocols. The device enhances the traditional store‐and‐forward architecture of internetworking to allow for permanent storage and assigns intermediate nodes with responsibility of data custody. In this context, space data can be distributed reliably within a designated overlay that interconnects research and academic institutions, but also space‐oriented industry and agencies. Analysis and prototyping of the SDR concept is subject to an EU FP7 Project in the 2010 Space Call performed by the Democritus University of Thrace (DUTH), the National Observatory of Athens (NOA), the University of Plymouth (UoP), Space Internetworks (SI), and VEGA Space GmbH. The project is based on previous work on DTN including DTN/IP Test‐bed Studies performed by DUTH under ESA Contract. The SDR prototyping activities will make use of and enhance this test‐bed but will also include experimental studies of deploying a DTN‐overlay over CCSDS link layer protocols (TM/TC packet protocols and AOS) making use of ESA infrastructure software and commercial

34

equipment. In the presentation we will summarise the work on which the study is based and will present the general SDR concept. We will detail the design characteristics of the device and discuss the expected impact of its deployment, emphasizing on the flexibility of data dissemination, adaptability to space assets and enhancements in inter‐agency operations and space communications in general. Finally we will present the evaluation scenarios already developed in the project and describe the plans for the prototyping activities.

****************

XTCE tailoring for ESA del Rey, I.

GMV, SPAIN

XML Telemetric and Command Exchange (XTCE) is a CCSDS Recommended Standard that defines a model for describing spacecraft telemetry and commanding data, for use during all phases of the lifecycle of a space mission. Its goal is to enable the exchange of TM and TC data without the need for re‐validation or re‐implementation of mission databases in the different organizations and systems involved.

Being developed for a large spectrum of spacecraft (e.g. frame based TM/TC, packet based TM/TC, etc.), XTCE is very general and complex in some areas, as it reflects the different ways of defining TM and TC data by several government and commercial organizations. As a consequence the adoption of XTCE by an organization involves the definition of guidelines and rules for using the standard for its specific needs. This can lead to different implementations across different systems, unless the specific guidelines are standardised as well. NASA has addressed this issue by defining the "XTCE GOVSAT Specialization", a tailoring of XTCE for a particular type of USA Government satellites. It defines rules that either forbid or restrict the use of certain XTCE elements, limiting the scope of the standard. The rules are defined in XPath language, which makes it easy for a software system to process them.

Based on the approach taken by NASA, GMV has recently started a project for ESOC that aims at defining the tailoring of XTCE for ESA missions. The XTCE tailoring for ESA is especially targeted to enabling the conversion of XTCE databases to the format used by SCOS‐2000, the ESA Spacecraft Control and Operations System. This would allow the use of XTCE databases in SCOS‐2000‐based Mission Control Systems and EGSE systems, as well as in other ground systems which are currently handling the SCOS‐2000 database format. The tailoring will be defined to support the conversion between the two formats in both ways without data loss.

As a secondary objective, the XTCE tailoring for ESA is also intended as a specification valid for any satellite based on the ESA Packet Utilisation Standard (PUS), which would be applicable to other European organisations such as CNES or DLR, regardless of whether they use SCOS‐2000 or not. In order to achieve this objective, it is foreseen to distinguish between rules derived from PUS constraints and rules derived from SCOS‐2000 constraints, so that PUS‐specific rules can be applied in isolation.

Finally, the project will also address the development of the software needed to convert between XTCE and SCOS‐2000 formats. This software will be developed as an extension of the the current ESOC infrastructure for managing the SCOS‐2000 database, the DABYS SCOS‐2000 Data Manager.

The SCOS‐2000 Data Manager will be extended to be able to import and export XTCE databases. As part of the import, the correctness of the XTCE database will be verified by checking against the XTCE schema and the new ESA XTCE rules.

****************

Recent Applications of Procedure Automation Blake, R

SciSys, UNITED KINGDOM

The SciSys Operations Automation product APEX is a procedure definition and execution tool designed to support automation of spacecraft testing and spacecraft operations. Previous deployments of APEX (and it’s predecessor UniT) have been aimed at first line automated monitoring and control for customers such as Eutelsat, the UK Ministry of Defence and Eumetsat. More recent applications have demonstrated the flexibility of the APEX product by specific extensions to it’s capabilities. This presentation will provide a brief overview of the core APEX product and a description of new functionality and applications including:

automated procedure generation modelling of commands and system state integration with non‐space M&C protocols import of ECSS PLUTO standard procedures

Automated Procedure Generation

The monitoring and control of sophisticated payloads is a complex task requiring the support of ground based automation. To this end APEX has been deployed to analyse payload reconfiguration requests and to generate the flight operations procedures required to safely conduct the required reconfiguration. The resulting output is suitable for manual or automated execution. This represents a novel deployment of the tool in that APEX generates the procedures that monitor

35

and control the payload for execution elsewhere, rather than performing the monitoring and control directly. Effectively we have a system where procedures generate other procedures, or more specifically where automation procedures generate flight operation procedures for subsequent execution against the spacecraft. Use of the APEX operations automation tool in this way provides for secure and efficient operation of a complex payloads.

Modelling of Commands and System State

Testing and validation of procedures requires access to some form of simulation. Ultimately a high resolution simulation of the system under control is required but to remove the dependency on an external simulator, particularly during the early stages of procedure development APEX now includes system state and command effect modelling.

The APEX state model component provides a facility to monitor the current state of the system under control as seen through telemetry. This is modified via the command effect model which simulates command execution using logic defined using simple Javascript. This use of internal models removes the need for direct connection to a simulator during the generation of automated procedures.

Integration with non‐space M&C protocols

APEX presents a standardised automation interface layer based on the concepts of:

Commands which can be sent. Parameters which can be received. Alerts which can be raised or observed.

For a specific deployment of APEX it is necessary to map the monitoring and control interface presented by the system under control onto the corresponding parameters and commands by constructing a system specific API. An example will be described where APEX has been integrated with a non‐space monitoring and control system using MODBUS, a serial communications protocol originally developed for use with programmable logic controllers (PLCs).

PLUTO Import

The extension of the APEX procedure model to support the constructs defined in the ECSS PLUTO standard will be described. This allows procedures written in PLUTO to be imported.

****************

MUSE ‐ Multi‐Satellite Environnent Bonnafous, V.; Cruz, D. Capgemini, FRANCE

MUSE a multi satellite programming tool allowing to manage Meta Programming Requests at multi satellite level. In the first version, this tool allows to manage Programming Requests for SPOT, FORMOSAT and KOMSAT satellites. In order to achieve his goals, the tool uses a set of Web Services published by Spot Image (SPOT Requests Management, meshes cutting, feasibility studies), and deploys a new Meta Programming Request service allowing to Spot Image users or partners around world to use the tool. The tool will incorporate later other satellites and Spot Image new services.

The Capgemini solution is characterized by :

an iterative approach allowing to Spot Image, by the way of the Capgemini flexibility, to define the good level of ergonomic in order to achieve optimal productivity for the Programming responsible. A usable version of the tool is delivered every 3 weeks, in order to raise feedback from final users and give an opportunity to improve the tool.

a java EE solution using a rich Eclipse RCP client, and World Wind Java allowing to reach a great flexibility for ergonomics choices made by users during workshops,

a Model Driven Approach (MDA), allowing to generate a big part of the application. This approach makes it easy to adapt the tool to new satellites, new services or new data.

a plugging architecture improving the independence of the tool regarding technological choices in order to make durable the Spot Image investments. (For instance the cartographical functionality is a plug‐in build upon WWJ which could be changed later by another cartographical plug‐in, simply by developing the cartographical plug‐in interface).

****************

Introduction to the Architecture Centric Design Method

Brito, N.1; Lattanze, A. J.2 1University of Coimbra, PORTUGAL; 2Institute for Software Research at Carnegie Mellon University,

UNITED STATES

36

It is the case that software intensive systems tend to grow in complexity as the system is modified and extended throughout the lifecycle. Unmanaged complexity impacts directly the cost of maintaining and extending systems and may shorten their useful lifetime.

To better manage the complexity system, and enable engineers to modify and maintain systems in a more cost effect and predictable way, it is necessary to understand the architectural drivers, the mission context, and the needs of system stakeholders.

Architecture designs embody these concerns and can help to guide the initial system development as well as long term maintenance of the system.

Unfortunately, many organizations do not utilize defined architectural design methods and processes. Architectural design methods are a way that enables organizations to create better architectural designs in a cost effective and predictable way, aiding in system construction and maintenance throughout the system lifecycle.

During this presentation, we introduce the Architecture Centric Design Method (ACDM), a methodology that guides the process of architectural design and takes into consideration the technical and human aspects of developing complex systems.

This methodology places the software architecture at the centre of a development effort rather than standalone software processes. Like architectures in the building and construction industries, ACDM prescribes the architecture design to drive not only the technical aspects of the project, but also the programmatic issues of a development effort as well.

The presentation will debut with an introduction of the ACDM, followed by a case study presentation covering a project for an european telecommunication operator developed with resort to the ACDM.

****************

OCP: Bringing Automation to Operational Control Centers

Capdevielle, E.; Berthon, JC. Capgemini, FRANCE

Historically, CNES spacecraft fleet was hand operated by a network of ground stations. Ground stations were locally operated, but with the technological advances, they can be further automated up to the point where today they are remotely monitored and controlled. Nowadays, with the growing numbers of spacecrafts to operate arise the need to automate the scheduling of the ground station activities.

OCP is part of CNES' HOMERE project, which aims to operationally harmonize management and exchanges within CNES' TT&C networks. In this context, existing planning tools are replaced by a unique tool, OCP. The main goal of OCP is to provide a central tool performing stations and multi‐mission resources scheduling

management for operational, qualification and maintenance. In addition, it allows performing simulations, for instance launch postponements scenarios, new spacecraft to operate, etc. Furthermore, the OCP must provide specific output schedules for each center that would interface with the system. Aside from the core operational features, it supplies means to verify the correct sizing of the whole ground network, and to provide statistical reporting tool for analyzing the use of multi‐mission resources.

The solution provided by Capgemini is to define, create and set up a specific system. This system contains a central database which can be accessed by each user via a rich client. This rich client offers an MMI personalized according to the specific user rights. Users define a set of constraints that best suits their needs on shared resources, for example one requires having at least 4 flyovers per day for his mission. The underneath algorithm, based on constraint programming concepts, tries to compute a planning compliant with the whole set of constraints.

First of all, Capgemini solution is characterized by a java EE solution using a rich Eclipse RCP client. The former technology brings a great flexibility for ergonomics choices that can be user‐driven during workshops. The use of MDF (Capgemini own MDA Framework) allows generating a big part of the application. This approach makes it easy to adapt the tool to new resources (spacecrafts, stations, etc.). The algorithm for calculating the schedule is based on constraint programming concepts, using ILOG Solver. The solution interfaces with various internal and external centers, using many different data formats. These formats can be CNES property, such as REGATES, but OCP is also compatible with SCCS‐SM standards.

One of the main key benefits of OCP is that it will allow a more efficient sharing of ground stations resources. It will also help CNES to perform the optimal sizing of resources depending on tracking activity forecast.

****************

A Dedicated Space Surveillance Optical Network Cooperates with Radar to assure LEO Debris Catalogue

build up and Maintenance Cibin, L1; Chiarini, M1; Besso, P2; Milani, A3; Bernardi, F3;

Ragazzoni, R4; Rossi, A5 1Carlo Gavazzi Space Spa, ITALY; 2ESOC, GERMANY;

3Dipartimento di Matematica UNIPI, ITALY; 4INAF, ITALY; 5IFAC‐CNR, ITALY

Carlo Gavazzi Space SpA, INAF (Istituto Nazionale di Astrofisica), DM (Dipartimento di Matematica Pisa) and IFAC‐CNR (Istituto di Fisica Applicata), all members of an Italian Team studying Space Surveillance topics, have been awarded the ESA SSA Feasibility study of an

37

innovative system for debris surveillance. The aim of this paper is to present the architecture of the optical network used for the monitoring of the upper part of the LEO region and to build up and maintain an object catalogue to support the collision avoidance. The proposed Optical Network can in principle increase performances with a relatively small impact on the overall system costs, compared to the radar system so far considered to be the baseline LEO observation methodology. The feasibility of the proposed approach results from an innovative optical telescope architecture with performances tailored for the detection of objects in any Earth orbit (and also of Near Earth Objects). The innovative approach allowed to demonstrate the ‘observability’ of an object passing above a given station horizon despite the combination of demanding interplaying factors such as light, Earth shadow and clouds. The proposed network is able to cooperate with radar allowing the RF technology to limit its application range to the lower part of the LEO. The study also evidenced that there is an orbital belt where both optical and radar observations can overlap , collect data working in a coperative way.

****************

ESTRACK Support for CCSDS Space Communication Cross Support Service Management

Dreihahn, H.1; Unal, M.1; Hoffmann, A.2

1ESA/ESOC, GERMANY; 2VEGA Space GmbH, GERMANY

ABSTRACT The CCSDS Recommended Standard for Space Communication Cross Support Service Management (SCCS SM) published as Blue Book in August 2009 is intended to provide standardised interfaces to negotiate, schedule, and manage the support of space missions by ground station network operators. ESA as a member of CCSDS has actively supported the development of the SCCS SM standard and is obviously interested in adopting it. Support of SCCS SM conforming interfaces and procedures includes:

Provision of SCCS SM conforming interfaces to non ESA missions;

Use of SCCS SM interfaces provided by other ground station operators to manage cross support of ESA missions;

In longer terms potentially use of SCCS SM interfaces and procedures also internally for support of ESA missions by ESTRACK.

In the recent years ESOC has automated management and scheduling of ESA Tracking Network (ESTRACK) services by the specification, development, and deployment of the ESTRACK Management System (EMS), more specifically its planning and scheduling components ESTRACK Planning System and ESTRACK Scheduling System. While full support of the SCCS SM

standard will involve also other elements of the ground segment operated by ESOC such as the Flight Dynamic System, EMS is at the core of service management and it is therefore appropriate to initially focus on the question to what extent EMS can support SCCS SM. This work presents results of the initial analysis phase. After briefly presenting the SCCS SM standard and the relevant components of the ESTRACK management system, we will discuss the initial deployment options, open issues and a tentative roadmap for the way to proceed. Obviously the adoption of a cross support standard requires and discussion and coordination of the involved parties and agencies, especially in the light of the fact that the SCCS SM standard has many optional parts.

****************

Evolving a Commercial Satellite Control Center toward a SOA: Lessons Learnt.

Estévez Martín, C.; Casas Manzanares, N. GMV, SPAIN

For several months, GMV faced one of the most ambitious and complex re‐engineering ever done in its SCOS‐2000‐based satellite control system hifly®: the complete migration of the graphical user interface layer from a proprietary C++ toolkit to Eclipse RCP Java technology.

Although the project was initially conceived as a mere substitution of a COTS, it soon turned into a key architectural refurbishment.

For exposing the domain logic to the new Java interfaces, a service oriented approach was chosen aiming at devising a scalable, robust and interoperable system.

Performance requirements of such an operational system were taken into account in the architectural design process.

However, it was soon realized that following SOA practices like "Services definition and granularity must be aligned with your business" was not as easy as people say. During the development it was collected many interesting lessons learnt as well as we realized that SOA does not relieve you from applying other software engineering practices.

The result of such architectural refurbishment was a full split of business and presentation layers through a middleware; the key elements of such architecture are:

A service layer (C++) that exposes the business logic available in the satellite control center.

A set of service adapters (java) that isolate service consumers from the underlying middleware.

38

A set of Eclipse RCP applications based on a modular plug‐in architecture; Applications use the service adapters for interacting with the services.

The new system architecture opens up the door to scenarios that were not affordable ‐neither technically nor in terms of effort‐ before: Applications could be deployed on different operating systems; Java service adapters allow future replacement of the current middleware (e.g. MoM) without affecting service consumers; A Web Services layer could be created on top of the current services, exposing business logic to web applications and mobile/tablet devices based on different technologies like Apple iOS or Google Android.

****************

PlanEO Fernandez Garcia, A.J.; Fernandez, C.

Deimos Imaging S.L., SPAIN

Soon after the commissioning of the DEIMOS‐1 mission, DEIMOS Imaging (DMI) realized that the MPS provided by the manufacturer did not fulfil a number of important requirements for commercial operation. This would prevent DMI to obtain the maximum return from the mission.

PlanEO is the new DEIMOS‐1 Mission Planning System. It does not incorporate any sophisticated technical features, other than the very advanced visual interface. However, its main feature is that it is designed with business in mind from the very beginning.

The main objective of a planning system is to decide the orders of the tasks in such a way that all of them are successfully executed, within the available resources; time, memory, cpu, etc. Implicitly, users expect the planning system to help them maximize the number of tasks executed and hence the goods (product or service) obtained by the system that is being "planned".

Now, with PlanEO, DMI is acquiring more than 3 million square kilometres per day, more than 65% of them cloud‐free.

PlanEO main features are:

Simplicity. Commercial people or project managers (brokers) must not take care of manoeuvres, FDS events, etc. It plans payload operations only.

Increase return of investment. More than 3 million square kilometres per day acquired and processed with maximum help to avoid clouds.

No automatic decisions. Conflicts must be solved manually between all project managers. PlanEO provides guidance to brokers in order to solve them and a graphical display of the conflicts to help immediate decisions.

Made for campaign / project managers. All features that are not useful or meaningful for a project manager have been removed or hidden. Main features are: o Cloud prediction (up to four days in advance) is inserted in the planning loop. o Integration with the Catalogue to show which part of the area of interest remains to be covered, real‐time. o Very powerful GUI. o Integration with Savoir (from Taitus).

Multi‐user client‐server architecture.

****************

Architecture of the Telemetry Data Management System SpaceMaster

Dr. Thelen, A.1; Schoenig, S.1; Koerver, W.1; Dr. Fischer,

H.2; Dr. Sous, S.2; Dr. Willnecker, R.2 1S.E.A. Datentechnik GmbH, GERMANY; 2DLR‐MUSC,

GERMANY

The presentation describes the modern software architecture for space data processing implemented in the telemetry management platform SpaceMaster. As a result of DLR’s longtime experience with the operation of multi‐purpose experiment facilities on board of SpaceLab and deep space missions, this software was developed during the last 5 years for use at the ground segment of the cornerstone mission Rosetta for the Philae lander satellite. As the facility responsible center for the space station facility Material Science Lab (MSL), the DLR Microgravity User Support Center envisages to use this platform as a generic tool chain for payload and experiment operations.

Additional Information

SpaceMaster is a generic reusable telemetry data management system used to process, store, and to visualize telemetry data. Its running on multiple client workstations connected to a server. The server system consists of small and stable system core software with open plug‐in interfaces. This allows the system to be adapted to new facilities or to react to new requirements and use cases.

An open API based on WebServices is the access point to the system for any standard software language (Java, C#, LabVIEW, ....). The programming interface can be used by external tools for configuring the system as well as to get access to the data stored in the system i. e. for exporting and reporting purposes.

Additionally a full featured graphical user interface based on Eclipse RCP (Rich Client Platform) can be used to operate, configure, and maintain the system setup. Online and offline data can be visualized and evaluated in parallel, with standard table and graphic displays as

39

well as with arbitrarily synoptic displays. Built‐in management tools provide instruments to manage different spacecraft or operational views.

The telemetry process configuration is not limited to basic predefined processing rules taken from a data base definition. The configuration within SpaceMaster is based on a domain specific language (DSL), a programming language specially created for telemetry processing. With this layer in the background simple user interface driven processing rules can be defined as well as complex processing rules for unlimited functionalities.

For web access SpaceMaster uses the Eclipse Rich AJAX Platform (RAP) technology. The comfortable user interface provided by desktop client is hosted into web. Client functionalities are accessible in the same design through a standard web browser without any restrictions.

Note This presentation is supported by the separate poster session “SpaceMaster Overview of a Telemetry Data Management System”. The presentation includes a software demonstration where the audience has the opportunity to see the software in real life and to get additional information about the system.

****************

Mars Express/MARSIS Ground System Architecture. A Pioneer ESA Space Mission: Lessons Learned for the

Future Giuppi, S.; Orosei, R.; Noschese, R.; Cartacci, M.;

Cicchetti, A. INAF/IFSI, ITALY

Mars Express is Europe's first spacecraft to the Red Planet. The spacecraft has been orbiting Mars since December 2003, carrying a suite of instruments that are investigating many scientific aspects of this planet in unprecedented detail. The observations are particularly focused on Martian atmosphere, surface and subsurface. The most innovative instrument on board of Mars Express is MARSIS, a subsurface radar sounder with a 40‐meter antenna. The main objective of MARSIS is to look for water from the martian surface down to about 5 kilometers below the surface. It provides the first opportunity to detect liquid water directly. It is also able to characterize the surface elevation, roughness, and radar reflectivity of the planet and to study the interaction of the atmosphere and solar wind in the Red Planet's ionosphere. A space mission involves a lot of aspects to be taken into account and it is extremely

difficult to design a ground system which meets all the requirements needed. Since the MARSIS instrument was innovative at the time of its conception, its ground system architecture design was based on the Earth observation field, as there was no experience in similar missions. Despite every decision taken seemed logical at the time, the importance of some data processing aspects were underestimated as well as some other important activities connected with a full mission success achievement. After having highlighted the differences between the requirements of a typical Ground Segment of Earth observation and those of a planetary mission experiment, here we describe MARSIS ground system original architecture, the lessons learned and the improvements implemented during over 7 years of experience in the MARSIS ground segment management in order to fulfill the mission requirements and speed up the work. We will provide some guidelines for future space mission ground system architectures.

****************

Operations Planning for the Galileo Constellation Hall, S; Hall, Stewart

SciSys UK Ltd, UNITED KINGDOM

The Spacecraft Constellation Planning Facility (SCPF) has been developed for ESA, and plans operations of all thirty satellites, six ground stations and the control centres of the Galileo constellation. It generates a "Short‐Term Plan" based on the requirements of the navigation service, routine, and non‐routine operations. The plan contains all the scheduling information needed by mission control system to operate all the satellites, including: the complete pass plan, the procedures automation, manual operations and the on‐board timelines. The high performance of the system is designed to support both routine planning, re‐planning and very short‐term emergency re‐planning.

Galileo is Europe's satellite navigation system and will comprise a constellation of up to 30 satellites. A typical week for Galileo consists of 300+ satellite contacts and perhaps 1,500 tasks with 10,000 separately schedulable procedures and on‐board commands to be executed. The SCPF must automatically produce a viable week's plan in just 10 minutes.

Key aspects for SCPF's design are:

Contact/Pass scheduling (4‐30 satellites, 2‐6 ground stations)

Automatic task scheduling based on predicted events, standing orders and one‐off planning requests

Integrated planning of on‐board and ground‐based task schedules

Supports tight coupling with underlying automation

40

Open interface for provision of planning requests which may be submitted at any time

Models resources and resource constraints Detection of schedule conflicts with temporal and

resource planning constraints Can automatically repair schedules to resolve

conflicts Prioritises operations consistency between

planning cycles Can be operated over two synchronised sites.

The tool is designed to be highly configurable to address the evolving mission operations concept. It allows satellites and stations to be added, new satellite resources and new planning rules to be defined, all under version control. This operational flexibility, and the use of state‐of‐the‐art software technology, gives it the potential to be a framework for future ESA mission planning systems.

This paper discusses the key requirements of the constellation's operations planning and how the design of the tool and the technologies used satisfies them. Special focus is given to the planning of the ground station passes needed to support operations versus the ground station utilisation.

****************

ARES ‐ Efficient SW Integration and Reuse supported by an Agile Project Management Approach

Hauke, A.1; Santos, R.2; Unfried, C.1 1Siemens AG Österreich, AUSTRIA; 2ESA/ESOC,

GERMANY

ARES ("Analysis and Reporting System") has been launched as a GSTP study by ESOC, with the goal to provide a common platform at the Mission Control infrastructure in place for the offline analysis and visualization of mission‐relevant data from different mission archives (PARC, FARC or DARC). ARES shall then become the operational demonstrator of the ESA Ground Data System infrastructure platform for off‐line analysis, reporting as well as correlation of operational data.

This shall be achieved by developing interfaces to existing applications such as EDDS (EGOS Data Dissemination System), via extending and integrating other applications such as EUD (EGOS User Desktop) framework or DARC in an optimized way for ARES purposes, and by means of re‐implementing the functionality of legacy SW components as the MUST clients (Grains, JavaGrains) and MUST server for ARES.

The presentation of the ARES project is focused specifically on the following topics:

Aspired high degree of SW reuse in ARES for the harmonisation of mission control infrastructure, supported by an agile project management framework (Scrum) that strongly involves the responsible ESA Technical Officer and key stakeholders (including experts from the SW applications to‐be‐reused);

Pre‐operational benefit of the harmonized MCS infrastructure from an end user perspective. This includes full compliance with the infrastructure baseline, availability of documentation sets as per operational standard and aggregation of key functionality into a single platform (from the existing multiple clients);

Experience report: The experiences which have been made are three‐fold: ___ Experiences related to the used Agile Framework for project organization; ___ Analysis results of other (offline) analysis SW systems in place at ESOC and their impact to ARES integration; ___ Emphasis laid on the analysis of COTS and open source components in order to support the implementation in the shade of licensing problems for future contractors, from the Agency or other Third Parties (e.g. JFreeChart library with GNU LGPL license vs. JavaGrains and its license restrictions for further distribution).

The presentation of ARES is supported by a short demonstration of the current status of the implemented/integrated SW based on an ARES installation in a virtual environment ‐ also containing the needed CFIs and COTS software ‐ deployed on a Notebook.

****************

Demonstration of the EGOS Data Dissemination System (EDDS)

Hawkshaw, M1; Santos, R2 1Logica, GERMANY; 2ESA, GERMANY

The EGOS Data Dissemination System (EDDS) enables users to retrieve data from archives located in the internal ESA network. The current version of the system allows users who do not have direct access to a Mission Control System (MCS) to submit requests for data, without needing to know the technical details from the MCS side. All MCS archives are supported (Packet archive ‐ PARC, File archive ‐ FARC and Parameter archive ‐ DARC). This presentation will include a live demonstration of the EDDS software connected to a live mission, the challenges faced in developing the software (problems found in the PARC, FARC and DARC, the usage of EGOS User Desktop and SMF) and the lessons learnt from this. The presentation will also discuss the future of EDDS and the new planned features. This includes streaming, subscription of data for delivery based on data change and not on batch

41

request and the design on how will the use of open source integration framework software such as Apache ActiveMQ and Camel to quickly create a robust way of delivering streamed data to the client.

****************

Use of Scrum in practice on the EGOS Data Dissemination System (EDDS) Hawkshaw, M1; Santos, R2

1Logica, GERMANY; 2ESA, GERMANY

In the realm of software development, "Agile Development" and "Scrum" are bandied about nowadays but what do they really mean? It might be a good idea on paper, but what about in practice? This paper looks at Scrum from the customer and supplier's side to look at the real benefits and challenges involved in following the Scrum approach on projects. It will also examine the change in mindset required over the traditional approach, and what it actually means to run a project using Scrum within the ESA/ESOC ecosystem.

This is not a presentation on Scrum, instead it's a look at the use of Scrum in practice, rather than on the concept of applying the methodology. The project this presentation will look at is the EGOS Data Dissemination System (EDDS) developed by Logica for ESOC. Basic knowledge of Scrum is required.

This will be a joint presentation between Logica and ESOC to represent both sides. The presentation will discuss:

The change of mindset required on the side of both the contractor and ESOC

The challenges of fitting Scrum in current contracts; The advantages Scrum has brought to ESOC for

EDDS; The advantages Scrum has brought to Logica for

EDDS; The new possibilities this development framework

brings; The major pitfalls Scrum can present; Lessons learned from using Scrum on EDDS.

This presentation will not include a demo on either EDDS or the Scrum process.

****************

Mission Automation at ESOC; finding success with an end‐to‐end approach.

Heinen, W.; Reid, S.; Pearson, S. Rhea System S.A., BELGIUM

MOIS (Manufacturing and Operations Information System) is a key component of ESOC’s evolving automation infrastructure. ESOC Flight Control Teams

are gradually gaining experience and confidence as the infrastructure evolves, . This presentation will reflect on experience and plans through three distinct phases of development, from established automated operations, current activities and plans for the future.

MOIS in‐built end‐to‐end scheduling and procedure execution environment has successfully been introduced to a number of established missions, Envisat, Smart‐1, Cluster, Rosetta and Venus Express. The presentation will give details of the varied scope of automation needs and solutions for these different missions.

Missions currently in development (those using SCOS‐2000 5.x as infrastructure) are using the recently developed MATIS and SMF infrastructure. MOIS has been adapted to prepare procedures in the format required for these systems, based on draft version of ECSS‐E‐ST‐70‐32C.

RHEA is about to undertake a new project (IDEA), who’s purpose of this project is to ensure a single integrated environment for the preparation of all types of procedure: manual, automated, semi‐automated (command stacks) and on‐board control procedures. The intention is to bridge the gap between procedure definition in the offline environment and procedure validation in the run‐time execution environment. It is envisaged to capitalise on the existing generic products used by all missions at ESOC to define procedures: (MOIS) to execute them automatically and (MATIS) to interface with the automated system through a common and generic interface (SMF). The IDEA study will focus enhancing the preparation environment (MOIS) and the execution environment (MATIS/SMF) in order to provide the user with an integrated operations preparation, validation and automation system.

****************

Architectures for Integrated Satellite and Ground Operations

Honold, P.; Castrillo, I. GMV, SPAIN

In recent years, satellite operators worldwide have identified the need to address their control systems infrastructure, both satellite control (SCC) and ground station M&C (MAC), as a whole in order to efficiently support their operations.

Having a single system to deal with both satellite and ground station operations was not rare fifteen years ago, when most of these systems were developed and provided by the satellite manufacturers or, in case of the large operators, developed in‐house. The advent of SCC and MAC COTS solutions from independent suppliers has led to an specialization of these systems

42

that, while has largely improved their capabilities to efficiently support operations in their specific domain, has made it difficult to unify and integrate operations, in particular since each one of systems has been usually developed by different companies often specialized in only one of the domains.

Since GMV began the development and commercialization of satellite control systems for telecom operators, and particularly since we are marketing hifly, a COTS solution for commercial satellites control based on ESA’s kernel for satellite control SCOS‐2000, we have had the opportunity work with and to deliver SCC and MAC systems based on different integration architectures.

The presentation describes three different architectures we have worked with:

‐ A first case, where operations of a large fleet of satellites and ground resources is supported by specific SCC and MAC systems which are coordinated by a high‐level ground resource management protocol allowing to automate most of the operations. In this case, a high availability level is achieved while the complexity of ground operations is hidden to SCC system.

‐ A second case, implemented for several of our customers, where fully integrated systems were required. In this case all the operations both at satellite and ground level are performed and automated from a single system (hifly), providing a unique environment to the operator that simplifies the monitoring and control of the resources and the SW maintenance.

‐ The third case, where hifly and the MAC system were integrated, but low level ground operations are still performed from the MAC system. This is a typical architecture that can be found in many satellite operators, suitable for small to medium fleets, requiring a limited level of ground and satellite operations integration.

The presentation compares and reviews each architecture, provides details on the impact on hifly internal architecture (based on SCOS‐2000) and SW changes that were required. A comprehensive analysis of the pros and cons of each architecture at several levels is also presented: implementation and integration protocols complexity, provided functionality, evaluation of the supported automation possibilities and SW maintainability aspects.

****************

Optimizing Communication Satellite Transponders Operation and Power Consumption with smartHz

Honold, P.; Godino, E. GMV, SPAIN

smartHz is a transponder optimization tool, based on J2EE web technology, allowing payload engineers working in a multi‐user environment to manage frequency plans and optimize the use of the space segment resources. It supports the assignment of frequencies and required power levels to carriers while minimizing the transponder power consumption.

smartHz is part of the suite of GMV products to support communications payloads operations, together with smart rings (for payload path and beams reconfiguration operations) and smart beams (for steerable antennas operations).

The tool implements accurate models for the computation of link budgets and impairments analysis of all the relevant effects, including thermal noise, adjacent satellite interference, co‐channel interference, terrestrial interference, ground station equipment interference (e.g. spurious, harmonics, intermodulation), rain and cloud effects, atmospheric gases, focusing and defocusing, scintillation and multipath. Accurate models of the non‐linear behaviour of transponder amplifiers, such as linearised TWTAs, which causes intermodulation interference when the transponder is operated near saturation, are implemented.

Calculation of interference is supported either from stored space, ground and terrestrial interfering stations automatically selected by the tool based on frequency and orthodromic distance and applying radio propagation models or if enough data is not available for all or some of the interference source types, it can be entered by the user as percentages of the total link noise.

The tool provides the capability to easily simulate different transponder occupancy scenarios and decide the best carrier allocation and transponder configuration enabling payload engineers to optimize the use and transponder operation. It graphically shows the transponder occupancy and relevant data, such as intermodulation interference inside the transponder band.

Link budgets can be calculated either on a transponder Fixed‐IBO basis or on a transponder Free‐IBO basis. In the first case, the transponder IBO is calculated based on worst case scenario according to four possible transponder occupancies: single carrier, dual equal carrier, dual non‐equal carrier and multi‐carrier. In the later, the transponder IBO optimizing the required transponder power is calculated while the required

43

quality of service (in terms of the required carrier Eb/No and availability) is still fulfil.

Link budget reports with different levels of details can be generated, including a full details one providing breakdown of all the C/N and C/I component values and intermediate results and optimization steps.

Different types of footprint maps (EIRP, G/T, Rx G, Tx G) can also generated for a particular transponder or carrier, which may include the representation of the co‐polar or cross‐polar component or the possibility to represent coverage polygons. Footprint maps can be based on a (u,v) or a (Longitude, Latitude) representation.

The product roadmap includes the integration with a transponder occupancy management system supporting automatic temporary access allocation through an external web access.

****************

Fast Engineering Archives providing a new future for Mission Analysis

James, S.; Pitaev, A. Logica Deutschland GmbH & Co.KG, GERMANY

Mission analysts and principal investigators thrive on data. Typically many agencies extract and reprocess telemetry packets. This requires costly reprocessing associated with long delays depending on the volume of data. Having processed engineering data generated by the spacecraft, EGSE or ground equipment at your finger tips can open up new possibilities for mission intelligence.

Logica has developed for ESA/ESOC a high performance engineering archive (DARC) that could pave the way for a new breed of mission intelligence applications. The Archive was developed using an agile methodology in partnership with infrastructure and operations to ensure the features and ergonomics met stakeholders' needs. When archives provide the ability to handle large volumes of data including multi level statistics it opens up the possibility for analysts to perform complex mission analysis queries quickly at any time.

****************

Federated System Architecture for Space Weather Services

Lawrence, Gareth Rhea System S.A., BELGIUM

The Space Weather Element (SWE) of ESA's Space Situational Awareness (SSA) has some unique challenges arising from the wide diversity of scientific, technical geographical and geopolitical constraints.

Although Space Weather Services are packaged together they are in fact federated from a wide range of European Sources.

Within the SSA Preparatory Programme, the SN‐I "Space Weather Precursor Services" project takes some initial steps, including redeployment of a range of existing software systems, each dependent on external data sources. The systems are integrated together under a new Web Portal.

An in‐depth analysis of existing European Expertise and Assets is also being undertaken, in order to establish coverage of SSA user requirements; Finally, RHEA is responsible for identifying a ‘roadmap’ for evolution of SWE Systems and Services existing today into the final SSA SWE architecture. The final Space Weather System architecture is driven predominately by the need to federate a diverse range of services.

The presentation will give an overview of the SN‐I project and a current view of the SSA Space Weather System Architecture.

****************

A Collaborative Electronic Logbook for Satellite Operations at Eutelsat

Louro, N.; Ronsiek, S.; Foweraker, R. MakaluMedia GmbH, GERMANY

At the beginning of 2010, Eutelsat decided to modernize their Satellite Control Centre event logging from a hard‐copy logbook to a fully electronic system in order to streamline their operational processes. The objective of this development was to provide a state‐of‐the‐art collaborative system to support exchange of the information required to operate the Eutelsat fleet safely and efficiently.

MakaluMedia GmbH were tasked with the development of a operational web application (eLogBook) to meet Eutelsat's specific requirements. Satellite operators and engineers can make new log entries from within the SCC

44

& backup SCC and this information can then be viewed from within the SCC and outside it. Engineers are able to comment on specific entries in a collaborative way. The information that is entered in the logbook has become more accurate and consistent now that most of it is selected from configurable templates. Searching and filtering entry and comment text is supported and the spacecraft controllers can easily capture screenshots when posting a new entry or a comment. The reviewing of the daily log entries by the engineering teams is now much more collaborative and is 'gently' enforced. The flow of information within the Control Centre has been improved. The transition from the paper to the electronic logbook went very smoothly and it has been very successful.

This presentation will describe the basic architecture of the eLogBook system and how it has improved information flow within the SCC.

****************

PlanetExpl: a Framework for the Science and Engineering Assessment of Exploration Missions Luengo, O.1; Kowalczyk, A.2; Pantoquilho, M.2

1GMV, SPAIN; 2ESA, GERMANY

The exploration of celestial bodies such as Mars or the Moon is relying (or will rely) more and more on the use of rovers for the surface operations. These have the advantage of a closer presence of the instruments to the scientific targets (in fact opening new opportunities since we are no longer limited to orbital instruments, but we can actually drill, perform in‐situ analysis, manipulation…). But there are also difficulties: the uncertainty of the surface operations is much higher than in orbit. Among the causes of this fact are: the interaction of the rover wheels with the soil cannot be estimated with accuracy (especially the slippage) and there is a high level of uncertainty in the accurate knowledge of the surroundings of the rover (the cameras only provide meaningful information up to 25 meters). Hence, the planning of operations for the following days will be highly dependent on the status and the results obtained from the experiments during the current day (for example, finding biological traces in a zone will most likely restrict the remaining mission to that zone or excessive slippage will cause an energy consumption higher than expected, there are no longer accurate celestial events or precise times of visibility of the scientific targets). Time is a very important constraint in this kind of missions in order to take the maximum advantage of the communication windows over the rover. The amount of time provided to the ground segment to produce the plan for the following day (including analysis of HKTM and basic product processing) ranges from 8 to 24 hours in the case for Mars (depending on the number of communication windows allocated to the rover) which given the uncertainty and the need for simulations could be a

pretty tight schedule. The above reasons make mandatory the use of a different approach for the choice of future scientific targets and activities. The application providing support to the user must allow for a fast analysis (mainly visual, to provide the situational awareness) of the rover surroundings as well as mission (scientific products, progress of overall mission objectives) and internal status (based on HKTM analysis), so targets and experiments can be selected and proposed to the mission planning. It will also provide the means to help to plan the activities of the following period and execute fast simulations to check times and resource consumption under different circumstances (especially regarding soil characteristics). ESA is conscious of these needs and during the last year launched the MMI for Exploration Missions project to study the different options and ways to implement these new requirements. This project is focused mainly on the visual analysis part and on the definition of data types and associated meta‐data (along with their storage), but it also pays attention to relations with other entities of the ground segment (data processing, mission planning). An agile development approach has been chosen in order to maximise interaction with the future users, and to speed up the process of development and testing. The tight schedule (6 months for the development) and budget makes the reuse of existing components and libraries a must.

****************

Building an Open‐Source Community Around Flight dynamics Ground Systems

Maisonobe, L.; Fernandez‐Martin, Ch. CS SI, FRANCE

The space flight dynamics field is one of the many technology fields involving many actors from different organization with different goals: public and private national and international institutions, industry, governmental agencies, academics, defense, SMEs ... Methods, tools and programs have been developed in each of these entities, often with public funding from some space program. Development costs have always been high, given the difficult test and validation steps and the lack of large scale market with thousands or millions of sales.

As funding became scarce, more and more cooperation between the various entities was necessary and a trend towards products standardization appeared. At high architecture level and for interfaces, standardization is mainly a top‐down process, with an officially appointed working group proposing recommendations to be implemented by several competing products. This is still a costly process and as participating to standard bodies has no short‐term return on investment, the working group decisions are often biased towards the more wealthy organizations, small players only participate as long as they get some public funding to do so. At

45

implementation level, there is another way to consider standardization: the open‐source paradigm. According to this paradigm, each and every player is welcome to participate at its own level and contribute to the final product. The product also evolves more in an organic way rather than through major steps. The development occurs openly and every single code change is immediately visible to anyone, without having to wait for a public release. This process is smoother than appointed groups process and leverages the field for every actor, minor ones as well as major ones. Open‐source paradigm does not implies chaos or lack of control. There are governance models for it. One efficient and often use governance model is called the meritocratic one. It is based on a few contribution levels (user, contributor, developer, member of the project management committee). This model is mainly known as the one used by the Apache Software Foundation, one of the world top open‐source player. The Orekit open‐source space flight dynamics library is an example of this approach. Its development methods and governance model have evolved in the last years to become a fully open project. Development occurs on a public site with direct anonymous access to the source code control system, to the issues and features requests trackers. Users, contributors and developers can discuss on archived mailing lists, and a cross‐entities project management committee has been set up. This models is successful, and only one month after the public forge has been opened, some discussions have started about major contribution opportunities between companies that have few former contacts.

****************

Use of Open Architecture Middleware in the Satellite Ground Segment Domain. Data Distribution Service

Naranjo, H. GMV, SPAIN

The European Defence Agency (EDA) promotes some studies for procuring external advice for the common benefit of all participating Member States, notably technical case‐studies and pre‐feasibility studies.

"Architecture for embarked middleware" (EMWARE) is one of these studies being performed for the Agency by an international consortium led by GMV. EMWARE scope included, among others, the definition of a business case fostering progress in the development of open architecture middleware systems with focus on Satellite Ground Segment. Some of its conclusions will be presented on this paper.

The average lifespan of satellite missions reaches more than fifteen years, thus implying obsolescence issues. Adding the lack of interoperability characterizing the ground systems results in increasingly difficulties to maintain and upgrade them to cope with new

requirements, updates or mission changes. This leads to non‐trivial costs in terms of development, deployment, maintenance and evolution.

The lack of interoperability is due to their closed and monolithic architecture not only tightly coupled with the mission and with the model of the satellite platform, but also with the components and the technology. Since the subsystems of the ground segment are typically provided by several vendors, their connection and integration is a challenge, which has usually been solved specifically for each system following ad‐hoc approaches attending to the line of application and the components involved.

Current trends on Satellite Ground Segment are focused on two main aims:

Scalability: switching from the paradigm of the satellite coupled with its specific ground system (mono‐satellite) to a decoupled paradigm where a ground segment can support several satellites (multi‐satellite), and a satellite can be supported by several ground systems (multi‐ground‐system). This can be extended to switch from the mono‐mission paradigm to the multi‐mission paradigm.

Connectivity: leaving the monolithic scheme for an open architecture that supports the interoperability between the components and with external subsystems, thus making it easier the integration of new functionalities and upgrades.

EMWARE project presents a solution based on the cooperation between different middleware technologies to match the heterogeneous communications requirements of the subsystems which coexist in a whole Ground Segment system‐of‐systems. It also brings some considerations about the way to approach this issue, linking it with the concept of Service Oriented Architecture.

Message Buses, Enterprise Service Buses and the Data Distribution Service (DDS) are some of the considered middlewares. Their joint use will be supported by gateways and wrappers with legacy systems. This paper will focus mainly on DDS.

****************

Can multi‐agent technology be applied to Space Mission Applications ?

Ocon, J.1; Wijnands, Q.2; Sanchez, A. M.1; Cesta, A.3 1GMV, SPAIN; 2ESA, NETHERLANDS; 3ISTC/CNR, ITALY

In the last two decades, agent and multi‐agent systems have experienced tremendous growth, and this topic has increasing popularity. The notion of software agents started to be put into practice at the end of the 80,s. During the 90,s agent and multi‐agent systems were

46

fuelled with the birth of the World Wide Web: communities of agents spread through the network started to collaborate. Later on, we witnessed the birth of Multi‐agent frameworks: software assets that provide the infrastructure required to build multi‐agent systems. As of today, we have dozens of multi‐agent frameworks available and in use throughout the world, either as free or commercial software. Agents have been applied successfully in many different business areas. Although some of these multi‐agent developments were developed "ad‐hoc" (i.e., not based in a multi‐agent framework), the use of multi‐agent frameworks eases the development of multi‐agent systems and increases the possibilities of these systems exponentially. In this paper we will discuss the experience that GMV had using multi‐agent frameworks in the DAFA project, and the conclusions obtained for this study. The DAFA project, led by GMV, was devoted to analyze the possibilities of multi‐agent systems in space applications, for both the ground and the space segment. We will describe the methodology that we followed to develop multi‐agent applications, the potential that we found in this technology and also the possible impact of the use of this technology when applied to a set of space mission scenarios.

****************

Cloud Data Systems: Applying the Cloud in ESA Ground Data Systems

Parsons, P; Olias, A The Server Labs, SPAIN

ESA, as many other organisations, is currently looking for models and technologies that simplify and enhance their IT resource utilisation while at the same time reduce costs. The challenges faced by ESA and ESOC in this area are similar to those existing in other organisations, and amongst others we can identify:

Environment tightly bound to physical resources, i.e. hardware, storage and network resources. This makes maintenance of hardware and legacy OS, especially problematic due to the long application lifetimes at ESOC.

Low consolidation and sparse utilisation of resources with the subsequent under‐utilisation.

Lengthy Resource provisioning, imposing time‐frames that might not be adequate for project needs.

Resource reconfiguration can be slow, prone to errors and not reproducible.

It is often difficult to provide standard, proven and reproducible end‐to‐end configurations (OS, Software and configuration).

Geo‐dispersed programmes such as Galileo and SSA require that the data centres are physically distributed

within the boundaries of each member state contributing to these programmes. Furthermore future missions such as ESA's Sentinel‐2 will generate Terrabytes of science data a day that need to be stored and processed by the science community, presenting new problems to be solved.

Cloud computing, in the form of XaaS services delivered over the Internet in Public Clouds, together with the transformation of existing and future data centres to give more flexibility using Private Cloud, represent an attractive alternative for ESA going forward.

We present a number of areas where Cloud computing can be applied to ESA's Ground Segment including but not limited to

SDE ‐ Software Development Environment

Setting up a Software development environment for a new project or study takes time. Cloud computing could provide standard SDE environments in a matter of minutes.

Test/Validation Environments

All developments produced for ESOC must undergo different sets of test/validation campaigns that required on‐demand resources for its execution. In this type of environment there is a great level of under‐utilisation of resources as well as a high degree of reconfiguration required. Cloud computing makes it feasible to provision a test/validation environment exactly when needed. The Public Cloud has already been successfully used on the Gaia project to validate test scenarios that would not have been possible with in‐house equipment.

Complete Ground Segment as a Service

47

The provisioning of a complete Ground Segment infrastructure is currently a task that requires a considerable amount of both installation and configuration time. The usage of virtualisation and public cloud computing technologies provide the tools to define and setup complete configured ground segments that can be provisioned on‐demand and accessed by any user community.

Mission Operations ‐ Optimisation of MCR/DCR usage

An additional area for cloud computing application could be for the optimisation of the MCR/DCR systems usage in the context of mission operations, to service different missions where private cloud technologies could help to facilitate and simplify these tasks, allowing an even more flexible provisioning environment for control rooms.

****************

GABIS: a Generic Build System for GSI applications Penataro, R1; Zimmer, T2

1GMV Aerospace and Defence, SPAIN; 2ESA, GERMANY

GABIS is the generic build system to be used by ESOC ground segment systems, including infrastructure systems, mission control systems, simulation and ground stations.

The various ground data systems belonging to the ESOC infrastructure rely on build systems that: (1) are aged now and therefore far from the latest best practices; (2) have diverged from one another, therefore overlooking the synergies that exist between them; (3) do not integrate the universe of ancillary tools used for e.g. computing software quality checks, continuous integration, test execution and reporting or documentation generation. EGOS strives to define some standard methodologies, and the GABIS Build System should be seen as just another step in the unification of practices across ground segment systems.

The design concept of GABIS is based on the integration of existing tools, rather than developing yet another build system. According to this approach, the GABIS Build System itself would provide only specific software developed to cover the functions that are not provided by the selected tools, basically requirements that are too specific to be found in already existing tools. In a first phase of the project, a careful collection and review of the requirements coming from all potentially involved parts has been done. Then, a survey was done on what tools exist in the market and how well these tools match the set of requirements. The architectural design has been performed based on the selected tools, plus two prototypes that proof the concept and the suitability of the selected tools. GABIS is currently in the implementation and validation phase and will be applied for the first time to the suite of ESA mission control system components, MICONYS 6.0.

It is expected that other ground segment systems can be re‐engineered to adopt the GABIS Build System, what would contribute to the harmonisation across systems and reduce the maintenance effort. Likewise, the new systems developed by GSI are expected to adopt GABIS Build System whenever possible.

The paper will describe in detail this new system, including some key topics, such as the modernisation of SCOS‐2000 build system, the introduction of Hudson for continuous integration, the migration to Mercurial as versioning system, or the usage of Eclipse CDT for improving the software development in C++.

****************

BIRF: How to Improve Software Projects Efficiency and Control using Business Intelligence

Prieto, JF1; Marques, P2; Vieira, M2; Widegård, K3; Navarro, V3

1ISFreelance, SPAIN; 2University of Coimbra, PORTUGAL; 3ESA‐ESOC, GERMANY

Software projects are difficult to manage. In complex environments, like the space programmes, this takes more importance, because they are large projects, involving complex subcontracting structures, and producing critical software. For those reasons, organisations impose software engineering methodologies and standards, which are usually supported by tools to improve the level of visibility and automation. However, those tools are dedicated to specific areas such as requirements, change management, coding, or testing. In addition, project progress reporting is normally based on periodical generation of manual documentation, without following a homogeneous approach for all projects. This situation drives to a proliferation of data about different aspects of the projects, which are difficult to collect and to evaluate from a global point of view in the organisation, and which requires significant routine manual work.

BIRF system has been developed for ESA‐ESOC with the objective of rationalising the reporting interfaces with the contractors, collecting data about different aspects of the project, and evaluating it to provide an integrated view of the status of the projects in the organisation at different levels of responsibility, using key performance indicators (KPIs) and reports.

48

BIRF is a web application using Business Intelligence, which is a mature field in the IT market providing tools for gathering and analysing data to support decision making. It is extensively applied to enterprise business

information and massive data analysis, such as financials, sales, and marketing, but not so much in the context of software projects.

The system has been deployed in ESOC and it is being applied to real projects, providing the following benefits:

Improved control over software projects, formalising interfaces with contractors and providing an accurate evaluation of the status of processes and products for proactive management and better decision making.

Improved productivity, automating time consuming routine tasks for data collection and reporting, as well as providing a quick access to all information related to the projects for all key actors, from technical officers to high managers.

Contribution to improve organisational processes, through the standardisation of best practices and the support to continuous improvement based on measures and evaluation of objectives.

A quick return of investment (ROI) is expected due to the cost savings related to the effective decision making, and the reduction of manual and repetitive work.

This solution has also potential application in order contexts, including:

Large organisations externalising projects or services, to improve control over subcontractors

Software companies, optimising their resources, and facilitating the adoption of mature processes (e.g. CMMi)

Other areas of space missions, in which it is necessary to evaluate the performance of a complex environment, such as non‐software projects, operational systems, etc.

****************

SpaceMaster Overview of a Telemetry Data Management System

Schoenig, S.1; Dr. Fischer, H.H.2; Koerver, W.2; Dr. Sous, S.2; Dr. Thelen, A.1; Dr. Willnecker, R.2

1S.E.A. Datentechnik GmbH, GERMANY; 2DLR‐MUSC, GERMANY

The poster presentation shows solutions covered by the SpaceMaster system for different use cases within an operation centre like facility management, system configuration and operation.

A demonstration of the SpaceMaster system supports the poster presentation. It shows how data is received, processed and visualized by the system. The used data are real mission data received in the scope of the comet

mission Rosetta. The configuration of the processing is demonstrated as well as the user interface components for the mission operation staff, which is used to show, navigate through, and export the data processed by the system. Additionally, the user gets information about the modern web interface based on AJAX and Web 2.0.

The poster presentation in combination with the demonstration will give some impressions how SpaceMaster can be used as central generic software solution for telemetry data management.

Note: This presentation is supported by the oral presentation "Architecture of the Telemetry Data Management System SpaceMaster". The presentation introduces the SpaceMaster system architecture.

****************

The Innovative Rover Operations Concepts ‐ Autonomous Planning (IRONCAP) ‐ Science and Engineering Planning for Rover Operations

Steel, R.; Hoffmann, A.; Niezette, M. VEGA, GERMANY

IRONCAP is an ESA study project to explore and define the concepts, techniques and interactions needed to control and plan the activities of an interplanetary rover by making use of current and future ground segment technologies. Its aim is to develop the requirements for a system that will be demonstrated by a prototype which will support the science and engineering activities and operations of an interplanetary rover using state‐of‐the‐art methods and techniques in planning and scheduling combined with existing and/or developing ground segment systems and technologies. The prototype will have to support the situational analysis of the rover and facilitate the planning and scheduling of activities/observation for the applicable autonomy levels, supporting the different teams in their daily activities.

As with any rover mission, a situational assessment of the location of the rover has to be performed to establish the context in which the planning of operations can be performed. This situational analysis is performed on an engineering level and on a science level both with their own goals and objectives. The science assessment is mainly concerned with the evaluation and assessment of what science has been achieved since the last assessment, what exciting new science could be done from what we see now, the science observations already planned to be performed and how to maximize the scientific return. In contrast to this the engineering assessment looks at the state of the space vehicle, taking a careful look at its health with respect to the last assessment. This would involve an evaluation of any energy sources on the space vehicle (i.e. batteries, solar panels, etc.) and their performance,

49

evaluation of any moving parts on the vehicle (such as wheel motors, camera arms, internal relays, etc.) noting and reacting to any degradation in performance.

Our presentation will outline the aims of the study giving a brief background to why this study is needed, present the current architecture for the prototype detailing the relation and positioning within a ground segment including the expected interactions with the various components of a ground segment, describe the contrast between rover science operations planning and engineering operations planning illustrating any common or conflicting requirements, introduce the planning and scheduling techniques that will be investigated during the study for use within the prototype and finally summarise the synergies with other ESA projects currently under development. We will conclude with a look at the current status of the project and present its current direction and outlook. Through this study we hope to infuse new techniques, concepts and technologies which will potentially benefit current and future rover missions.

****************

Flexplan, the Adaptable System for Mission Planning & Scheduling

Tejo, J.1; Barnoy, A.2; Pereda, M.1 1GMV Aerospace And Defence, SPAIN; 2GMV Space

Systems Inc, UNITED STATES

During the last decade, GMV implemented flexplan, a robust and flexible Customizable Off‐The‐Shelf (COTS) Mission Planning and Scheduling (MPS) system. flexplandemonstrated operational capabilities in Earth‐observing satellite missions like the EUMETSAT Polar System (EPS) or the Soil Moisture and Ocean Salinity (SMOS) operated by ESA as well as Moon Orbiters like the Lunar Reconnaissance Orbiter (LRO) operated by NASA. Each of the operators that use flexplanutilizes different philosophies in the way that they operates their missions and design the ground segment architectures accordingly. The one thing in common between operations of multiple platform fleets and highly specialized spacecraft is that they require a level of adaptability in the planning and scheduling to the ever changing requirements and constraints driven by the mission. Integrated in such missions, flexplan'sprimary goal of offering a flexible solution that can adapt with minor operational impact was achieved and superseded by an increased focus on performance when multiple platforms and complex operations are present. Since its conception, flexplanmatured in operability to support interfaces with a variety of external elements to execute spacecraft and ground operation, including varying levels of system automation, in order to reduce the cost of the operations and to increment the efficiency in its operability. The purpose of this presentation is to describe the flexplanarchitecture and how it makes the

system capable to adapt to different missions and ground segment architectures. Additionally, the incorporation of automation into operations will be described.

****************

The GNSS Advanced Monitoring Element (GAME) Core Villemos, G; Biamonti, D.; Edwards, D

Logica, GERMANY

The GNSS Advanced Monitoring Element (GAME) project develops a navigation data monitoring and evaluation system for OPS‐GN. The system offers near‐real time monitoring of navigation data and the comparison to predicted values, based on a large data warehouse.

At the core of the system the GAME core module provides a highly flexible framework for deploying, starting and managing a distributed, component based system. The core has been developed to offer among others:

‐ Communication protocol encapsulation. All connections are managed through connectors, with a proxy on the consumer side. The system exchange services through HTTP, RMI and JDBC and can change protocol through reconfiguration.

‐ Flexible system assembly. The system is assembled using Spring assemblies. The location of component instances can be changed through one line in a configuration file.

‐ Automatic configuration management. The system will at startup automatically check its installation and install updates to source code files as well as configuration from a central configuration management repository.

‐ Automated resource usage monitoring. Monitoring of used system resources such as threat’s and memory. Alert and notifications. Based on simple configuration rules, log messages can be used to trigger notifications through emails and/or RSS feeds. Local System Site. Local monitoring of component server through an embedded HTML server.

The system is based on mature OSS products such as Spring, JMX, Maven and Grizzly, with an absolute minimum code base ontop; less than 3.500 lines of code.

This paper describes the architecture and capabilities of the GAME core module, through direct demonstrations of the GAME system functionality.

50

****************

51

Supporting the Management of Mission Operational Knowledge ‐ a Case Study using Mars Express

Villemos, G1; Shaw, M2; Doyle, M.1; van Zetten, P1 1Logica, GERMANY; 2Mars Express OPS‐OPM, Consultant

Vega Space GmbH, GERMANY

ESA mission operation teams are supported by highly specialized, complex information systems. The systems offer the operators a wealth of information, critical to ensuring the continued success of the mission. However, these operators regularly face a simple problem: Namely accessing data from multiple, widely disparate, data sources to locate, cross‐correlate, validate and/or archive operational information.

Currently, whenever the operational team accesses their knowledge repositories, they must connect to each data source individually using whatever search functionality is present (where this exists). They must discard incidental information, and consolidate the remainder manually. Anecdotal evidence suggests that the overhead for these processes can be considerable.

More critically, the process is manual. Even for highly skilled teams, the absence of a dedicated tool to perform data retrieval in a coherent and exhaustive manner brings the risk that crucial information sources are overlooked.

In summary, information management is a critical task, but one that costs the mission operation teams valuable time, and may introduce an element of risk by virtue of its incompleteness.

Based on prototype development from a TRP study, Logica have designed a solution in close collaboration with the operational team of MEX. The solution provides a consolidated view of information related to telemetry parameters, tele‐commands and spacecraft generated events, these being consolidated from all relevant data sources and presented in a number of operation specific views. The solution envisages the ability to view references to a specific operational dataset from all data sources (databases, documents, intranet sites, issue tracking applications) via a compact, unified user interface. The goal has been to approach the management of information pragmatically within the complex and inhomogeneous environment of ESA missions, designing a concrete and viable solution on the basis of the identified operational needs of the mission concerned.

This presentation describes a proposed concept for how better to support mission operations, using advanced information management systems already undergoing prototyping within ESOC.

****************

Standardisation of Reprocessing Architectures for Future Ground Segments

Williams, I.; Evens, P.; Steven, J. Logica Deutschland GmbH & Co.KG, GERMANY

Reprocessing is a typical requirement of EO ground segments, whether scientific or operational, however there are several ways in which mission architectures have been adapted to meet these requirements. Today missions are requiring ground segment Architectures that must support the ever increasing data volumes required to handle the on‐board data generated. Much of this is being driven by the ever increasing focus on climatology missions in which reprocessing requirements are a key mission driver. The ESA Climate Change Initiative is an example of such a climatology mission: composed of 11 essential climate variables, most of which are based on existing climatology‐related missions, a key initial task of the systems engineering working group was to review the architectures of existing systems with a view to producing a harmonised logical model.

This paper will examine and compare the ways various CCI‐related systems have addressed reprocessing, including the usage of Cloud and grid technologies and look at how these architectural concepts may evolve in future ground segments.

****************

Cloud and Grid Technologies in Ground Segments Williams, I.; Evens, P.; James, S.

Logica Deutschland GmbH & Co.KG, GERMANY

Users are increasingly interested in using cloud and grid technologies to access and process large volumes of EO data, in order to reduce costs and to provide more flexibility. Cloud technology is very attractive for certain projects including reprocessing, however the cost of transferring data into the cloud or storing it for any length of time can be prohibitive. Grid technology can be an alternative for collaborating with academic or governmental organisations, for example ESA's GPOD grid, provides access to the full ESA and EUMETSAT archives, as well as substantial computing power, for CAT‐1 users. Cloud and grid technologies can be complementary, as the ESA GPOD project has shown by cloud‐bursting to the Amazon cloud when there are no more internal resources available. Other hybrid architectures, mixing cloud, grid, and private resources, are also possible. This paper will contrast the use of cloud, grid, and hybrid architectures for addressing ground segment needs.

52

Biographies Andrea Bertoli COMPAGNIA GENERALE PER LO SPAZIO ITALY Title Presentation: A NetPDL‐BASED PROTOTYPE IMPLEMENTATION OF GALILEO ATTITUDE ORBIT CONTROL SYSTEM SCOE CONTROLLER Past Activities: 1) System engineer of SPIRE, HIFI, PACS EGSE based on SCOS2K (ESA‐ASI project) 2) Software Architect of PERTH station monitoring and control software based on SCOS2K EGSE (ESA project) Present Activities: 1)System Engineer of PRISMA EGSE based on SCOS2K,(PRISMA is a small hyper‐spectral Satellite‐ ASI).

**************** Pierre Bornuat CS Systèmes d’Information France Title Presentation: CNES control centre mock‐up: an evaluation of a standard SOA architecture Past Activities: Pierre Bornuat has been working for 12 years in the space domain. Pierre has acquired a strong experience in leading large software development and I/V projects. In particular, he has managed two major projects for CS: the Monitoring & Control subsystem of the ATV Control Centre for ESA, and the Integration & Validation of PLEIADES spacecraft Secure Dual Ground Centre for CNES. Present Activities: He is currently project director for development and maintenance activities of CS Ground Segments department (which is part of CS Defense, Space and Security Division).

**************** Uwe Brauer Astrium Germany Title Presentation: Astrium Space Transportation Strategy for Ground Data Systems Past Activities: Project management and systems engineering for ESA projects (ground systems and manned operations support systems). EUROSPACE representative in THAG Ground System Harmonization Board Industry support for ESA standardization activities (e.g. ECSS‐E‐TM‐10‐23 System Engineering Database) and European Ground System Core initiative Present Activities: Head of Department Ground System Engineering in Bremen (5 teams, 55 people) Project Lead AITS

**************** Armin Braun DLR Germany Title Presentation: Current trends and outlook of future challenges in mission operations @ GSOC Past Activities: Subsystem and System engineer in Eutelsat II and Eutelsat‐W LEOP services System Engineer in ROSAT project Mission Operations lead for Equator‐S Part of Mission Planning Group (concepts, software development, planning algorithms, requirements engineering) X‐Radar Mission Planning for Shuttle Radar Topographic mission STS‐99 EnMAP project manager for Mission Operations Segment, deputy project manager for EnMAP ground segment. Present Activities: Team lead for application software group in the mission operations department.

****************

53

Noé Casas GMV Spain Title Presentation: Leveraging EGOS User Desktop and hifly® to evolve SCOS‐2000 Past Activities: Part of the task force team for the re‐engineering of EGOS User Desktop and the integration of GMV’s telemetry visualization technology (hiflyViews) into it. Project engineer for the migration of GMV’s hifly® UI layer to Eclipse RCP Technical leader of the adaptation of GMV’s advanced telemetry visualisation tool (hiflyViews) to ESA/ESOC infrastructure (SCOS‐2000, EUD, DARC). Technical leader of the development of GMV’s advanced telemetry visualisation tool (hiflyViews) using Java + Eclipse RCP Present Activities: Technical leader of project S2K2EUD (migration of SCOS‐2000 UI layer to EGOS User Desktop). Technical leader of EGOS User Desktop (EUD) maintenance

**************** Navid Dehghani Jet Propulsion laboratory, California Institute of Technology, NASA United Stated Title Presentation: Ground Data System for ATLO and Launch/Cruise for Mars Science Laboratory (MSL) Past Activities: Program Element Manager for Multi‐Mission Ground System tools and services at JPL Project Element Manager for AIRS science data processing system for EOS PM at JPL Project Manager for the Interferometry Science Center (ISC) at Caltech Present Activities: Ground Data System Manager for the Mars Science Laboratory (MSL) Project at JPL

****************

Isabel del Rey GMV Spain Title Presentation: XTCE Tailoring for ESA Past Activities: Software engineering for ESA projects in the area of satellite monitoring and control (CryoSat/GOCE Mission Control System, SMOS Payload Programming Centre). Present Activities: Project management and software engineering for ESA projects, in the area of ground data systems infrastructure. Latest projects include “Tailoring of XTCE for ESA”, “SCOS‐2000 migration to EGOS User Desktop” and “Implementation of DABYS Framework and SCOS‐2000 Data Manager”.

**************** Sylvain D’Hoine CS Systèmes d’Information France Title Presentation: Trends in space software system integration: CS vision Past Activities: Graduated from the French Ecole Polytechnique and specialised in computer science, Sylvain D’Hoine began his career within Astrium developing operational mission planning software. He has been working for the space business unit of CS group for 10 years. He successfully managed projects for space agencies (CNES and ESA) or French defense industry. Present Activities: Now, he is managing the Space & Intelligence business unit gathering the activities of CS in the domains of space ground systems and space applications. He manages a team of 250 engineers.

****************

54

Inés Fernández‐Rañada TCP SI Spain Title Presentation: Evolution of FEC architecture Past Activities: Master degree on Telecommunications. More than six years involved in the development of Front End software (FEC) in all Ground Stations of ESTRACK and in the deployment and on‐site validation of Front End Controller in Kourou, Maspalomas, Cebreros, Redu and New Norcia Ground Stations Present Activities: Expert Real Time software engineer, responsible for the concept, design and development of the evolution of FEC architecture.

**************** Rob Foweraker MakaluMedia GmbH United Kingdom Title Presentation: Telemetry Archiving: How to optimise storage efficiency, retrieval speed and real‐time performance. Past Activities: Flight Dynamics software and then Simulator Development at Vega. Simulations Officer on Cluster at ESOC. Project support on Stentor with Astrium. MSG Simulator support for Eumetsat. Development and Acceptance Testing of the METOP and Sarlupe ground control system with Integral Systems. Development of Payload Monitoring tools for Eutelsat. Present Activities: Management of space software development projects for Makalumedia GmbH. Design and development of Makalumedia’s web application development projects for Eutelsat.

**************** Hugo Garzón Gutierrez GMV Spain Title Presentation: BASyS: Neo Satellite Database Management System Past Activities: Hugo has been mainly involved in activities related to Neo‐SCS during the last years. Neo‐SCS is the multiplatform Satellite Control System developed by GMV for Eutelsat based on SCOS 2000. He has worked as project engineer in several Neo projects (B23, NeX, S4K, WSO) and more recently he has assumed the role of project manager (maintenance team, system redundancy project, NeoFly). He has also provided customer support for different activities including on site support and support of critical operations like on call support, LEOPs and SVTs Present Activities: He is currently the project manager and coordinator of Neo‐SCS and other related activities. He is also the project manager of BASyS which is charge of the implementation of the new satellite database manager for Eutelsat based on DABYS

**************** Jörg Hofmann T‐Systems Germany Title Presentation: Integrated Test Concept and Test Automation for Aerospace Projects Activities: Since 10 years in a disciplinarian leading position (20 to 60 employees), management of profit centers. Lieutenant Colonel with Deutsche Bundeswehr, Staff Division Special Operations, Artillery.

**************** Michael Kolar Jet Propulsion Laboratory USA Title Presentation: Architecture Governance, The Importance of Architecture Governance for Achieving Operationally Responsive Ground Systems

55

Past Activities: Deputy Section Manager, Integrated Ground Data Systems (GDS), Jet Propulsion Laboratory. Lead and collaborated on the development of GDS engineering best‐practices and procedures, assure program and flight project needs are met, establish training objectives and curriculum, provide mentoring and coaching to management and engineering teams, ensure product quality, and collaborate with JPL projects and initiatives on systems engineering modernization initiatives, such as software architectures (both system of systems and functional applications), mode‐based engineering and standardized IT infrastructures. Present Activities: Project Information Technology Systems Engineer for the Office of the Chief Information Officer (OCIO). Work with the OCIO, line management and project engineering teams to provide architecture and systems engineering support to the planning and deployment of OCIO‐provided IT services for DSN, MGSS and flight project ground systems.

****************

Dr. Rolf Kozlowski DLR GSOC Germany Title Presentation: GSOC Ground Segment Challenges Past Activities: After his doctoral theses in computer networks, Dr. Kozlowski worked 10 years as contractor in the air traffic control, military and space business. He worked as program manager mainly for system critical applications and systems. Present Activities: Dr. Kozlowski is deputy manager of the GSOC department “communications and ground stations” and is project manager for Columbus Control Center Facility Operations & Management and the SatcomBW project.

**************** Christian Kumpf MakaluMedia GmbH Germany Title Presentation: Telemetry Archiving: How to optimise storage efficiency, retrieval speed and real‐time performance. Past Activities: With Makalumedia and EUTELSAT: WiMics ‐ visualization of satellite payload TERES ‐ analysis of raw telemetry archive availability TEDIS ‐ real‐time raw telemetry distribution and archiving SDID Decom ‐ real‐time analysis of SCC network traffic With MM/ESOC: CRS ‐ Configuration Reporting System With ip23: ipgoo ‐ carrier‐grade real‐time aggregation and processing of ip accounting data with Fraunhofer IGD: Evaluation/design of compression algorithms for volumetric image data Present Activities: Lead Software Engineer TeleViews ‐ archiving and real‐time visualization of satellite telemetry TeleChecks ‐ a framework for offline analysis of satellite telemetry

**************** Naomi Kurahara University of Tokyo Japan Title Presentation: Ground Station Network for Micro/Nanosatellite Operation Past Activities: Naomi Kurahara studied the small satellite and space plasma interactions with spacecraft in Kyushu Institute of Technology and University of Surrey. She earned a PhD degree in electrical engineering from Kyushu Institute of Technology in 2010.

56

Present Activities: She joined Nakasuka laboratory, the University of Tokyo, as a research engineer. Her current research topics are Ground Station Network architecting and mission design for the small satellite. .

**************** Jose E. Marchesi Terma GmbH Germany Title Presentation: Towards a high performance LEON/GRLIB emulator Past Activities: ‐ SIMSAT Development. ‐ Maintenance of ESOC's simulation infrastructure. Present Activities: ‐ Emulation of ERC32 and LEON processors.

**************** Sylvain Marty CS Systèmes d’Information France Title Presentation: Improve usability of graphical user interfaces with new technologies in ground centre software Past Activities: Sylvain MARTY has been working for 5 years in the space domain. Sylvain has acquired a strong

experience in the technical management of ground control centre software and is specialized in new communication and information technologies. He has technically managed several projects at CS like Agata : a generic control and missions simulation software or SWWW‐NG a multi missions control centre data web server for mini and micro satellites for CNES.

Present Activities: He is currently project technical manager and also working on the research and development of new technologies to improve ground control centre software in the CS Ground Segments department (which is part of CS Defense, Space and Security Division).

**************** Robert Messaros Siemens AG Austria Title Presentation: Ten Galileo FOC Payload EGSE Systems Challenges in Design, MAIT, and Schedule Past Activities: Started work on space related areas with SCOE systems, pioneer Later on one of the SCOS‐2000 pioneers ESA ground segment, from Mission Control Systems to Groundstations (TMTCS) Present Activities: RF‐SCOEs (Sentinels), EGSEs (Sentinel PDHT) Galileo PL EGSE RF‐Suitcases: Gaia RF Suitcase, GMES X‐Band suitcase

**************** Gianluigi Morelli SES (Société Européenne des Satellites) LUXEMBOURG Title Presentation: Senior Manager, Operations Architecture Past Activities: Satellite engineer (attitude control) of GEO satellites tr Ground Control Systems procurement and deployment. Present Activities: Automation of satellite operations Advanced monitoring of satellite health Payload management software

****************

57

Heiko Müller, Dipl.Inf. VCS AG ‐ A SciSys Company Germany Title Presentation: Ground Segment Autonomy: A revised approach Past Activities: Worked for VCS AG as technical officer for the Central Monitoring&Control Facility (CMCF), part of the Galileo Ground Control Segment. Present Activities: ‐ Working as VCS project manager in the DLR.study “Fast generation of 3D maps for planetary landing and exploration operations” (FASTMAP). ‐ Working for the DLR study “Mission Control Concepts for Robotic Operations” (MICCRO).

****************

Sébastien Nouvellon Capgemini France Title Presentation: NOSYCA: the New Operational System for the control of Aerostats Past Activities: Sub Contractor activities (for CS and Capgemini):

Project Manager of the SLE Sentry Software (ESOC)

Integration and validation of the ARGOS Mission Centre (CLS)

Development of the TMTCS ‐ Telemetry and Telecommand System (ESOC)

Involved in the development of the ATV Control Centre (CNES/ESA). Present Activities: Project Manager for Capgemini:

Project Manager of the NOSYCA Control Centre (CNES)

**************** Paul Parsons The Server Labs Spain Title Presentation: SOA4GDS : Evaluating the Suitability of Emerging Service‐based Technologies in Ground Data Systems

Past Activities: 2001 ‐ 2002 BEA Systems S.A. Architect in the Professional Services department.

As an architect in the Professional Services division, Paul’s main role was to advise clients with their deployments of BEA’s products. The engagements typically ranged from implementing the full project lifecycle to providing architectural assessments and audits and providing specialised training in the form of master classes. Implementation of the full lifecycle involved defining an initial architecture, implementing a prototype to validate that architecture and then following the project through all the cycles of development. Many of the projects he was involved in were to develop multi‐device portals for PDAs, mobile phones and browsers.

2000 ‐ 2001 Uno‐E Bank S.A.

EJB Architect in the R+D department

Paul was heavily involved in defining and implementing the J2EE architecture for the bank’s new projects. Utilising J2EE throughout running under tiered WebLogic Clusters, the architecture was modular, utilising JSP’s and Servlets for the presentation and EJBs for the business logic. Backend systems such as those for funds and share trading were integrated with a Tib/Rendezvous Message Bus.

1999 FDS Finanz Daten Systems Gmbh, Frankfurt – contract

FDS is a daughter firm of the Deutsche Börse (the Frankfurt Stock Exchange)

FDS was developing a new‐generation data‐warehouse for the financial data delivered by the Deutsche Börse to the banks in Germany. The system has a central server based on a data model known as FIDM. The FIDM data model is stored in an Oracle Enterprise database that is mapped into the FDS server using Persistence Powertier. Client applications (written in Java) access the server using a C++ object model known as FIOM over a CORBA interface.

58

1997 ‐ 1998 DG Bank, Frankfurt ‐ contract(renewed)

Working on a large Market Risk Project, Paul developed C++ software to take data from four different trading systems within the bank to populate an Infinity Fin++ security and transaction model. Infinity makes usage of it's own Montage data model based upon a Sybase 11 database.

1996 ‐ 1997 Commerz Financial Products, Frankfurt ‐ contract(renewed)

Working in the Risk Control department, Paul developed a replacement Risk management and reporting system. The new system was developed in C++ using a client server paradigm around a central Sybase database. The client applications run locally on the users’ workstations, while a multi‐threaded daemon running on the central Sybase server distributes notifications of database changes to all the currently connected applications. The interface to the bank´s market data was made using Tibco Tib/Rendezvous.

1992 ‐ 1996 Science Systems Ltd at the European Space Agency (ESA) , Darmstadt, Germany

Senior Software Engineer and later Senior Consultant

Based at the European Space Operations Centre (ESOC), Paul developed application software for the SCOS‐II project, a generic next‐generation Satellite Control System. SCOS‐II is a fully distributed control system, running on a network of Sun Sparcstations and is intended to operate with satellites into the next century. It was developed using object‐oriented analysis and design, implemented in C++ and utilises state of the art commercial toolkits throughout. The system includes telemetry reception, telemetry distribution, retrievals, event logging, alarm handling. telecommand generation and telecommand verification. The project was developed by two teams, an applications team and a technology team, each having had a peak size of seven people. The project has followed the ESOC software development standards PSS‐05.

Two of the key architectural areas of SCOS‐II were a ”network cache” designed to reduce the network usage of the control system by storing the latest telemetry and event information on the local workstation, and an in‐house developed ”object‐oriented database” that contains the mission information and provides transparent access to applications through the use of ”smart pointers” (the application makes the same call whether the object is in memory or needs to be loaded from disk).

Within SCOS‐II, Paul initially developed GUI concepts for the more advanced aspects of the above control system using the Object Builder MMI toolkit. Later on Paul took responsibility for the architecture of the Commanding Chain, including the underlying model used in commanding, and all the commanding applications within SCOS‐II.

Paul developed subsystems for the Commanding Chain, specifically the Commanding Model and the Manual Stack (this term describes the standard operator console at ESOC for sending telecommands). The classes in these subsystems were designed so that missions could derive from them to customise behaviour.

Towards the end of the project Paul provided consultancy to the client for an ITT, and was involved in the technical part of a fixed price proposal, assessing the user requirement feasibility and providing manpower and budget estimates.

1990 ‐ 1992 Science Systems Ltd, Bristol

Paul developed software in ‘C’ for the front‐end workstation platform of a real‐time SCADA system on a unix‐based Intel system. This included MMI software for displaying the real‐time data, a separate subsystem for processing and displaying alarms and a graphical editor to allow the customer to create the displays used in the system.

1986 ‐ 1990 Racal Redac Systems Ltd

Senior Programmer in the “ Computer Aided Engineering” (CAE) team.

Paul’s main role was the development of object‐oriented software for the company’s Visula CAE Product. The Visula system employed an object‐oriented framework on top of the C language but based on the Smalltalk concept. Paul´s first task in the team was to develop an internal cross‐referencing facility to aid the development of the schematic editor. Paul was involved in the development of a new system level framework for the Visula range of CAE products. Paul was involved in the development of software to implement multiple instanced hierarchy

59

Paul was also involved in the development of a next generation CAE system, having responsibility for a package providing an object‐oriented interface on to the underlying electrical model in the system. Paul developed modules for program control, task management and communications (both local and remote), the latter utilising TCP/IP and Apollo’s NCS

Present Activities: Paul is an experienced architect and developer with many years experience in client/server technology and distributed systems, including C++, CORBA and Java EE and .he has taken a lead role in many large and successful projects. . CTO and Founder The Server Labs S.L Founded in 2004, The Server Labs S.L. is an advanced professional services company, specialising in IT architectures and state of the art technologies. The services offered include; architecture definition, IT strategy planning, architecture validation, advanced training and project management and implementation.

As well as the role of CTO, Paul has also been involved in a number of consulting engagements, including:

o ESA: Gaia Satellite – Gaia is a key mission within the European Space Agency to catalogue 1 billion stars in our Galaxy, the Milky Way. Gaia has huge data processing requirements; at the end of the mission the data collected and refined will amount to more than 1 PetaByte. The core data processing is being developed in Madrid at ESAC (European Space Astronomy Centre) using the latest Java 5 technologies running on a large Dell Cluster using an Oracle 10g RAC over an EMC SAN. In the project, Paul is responsible for the performance team, specifically java Performance, Oracle performance and Storage performance. Paul is also a core member of the team, helping define the Overall System Architecture for Gaia.

o Vodafone ‐ Huge EAI project involving more than 50 computers communicating with broadcast/multicast. The project was implemented with TIBCO’s Rendezvous and IntegrationManager solutions. Paul’s involvement included defining the network multicast architecture and topology, helping troubleshoot performance problems and providing advice to the production support team.

****************

Roger Patrick Terma A/S Denmark Title Presentation: Living with ESA infrastructure Past Activities: Software Developer – spacecraft checkout systems (4 years) Project Management – space ground systems projects (5 years) Business Development manager for Terma (Netherlands) (5 years) Present Activities: Business Development manager for Terma (Netherlands) and Terma (Germany) – 15 years

**************** Steve Pearson Rhea System SA Belgium Title Presentation: European Technology Harmonisation on Ground Software Systems: Update of Reference Architecture Past Activities: ESA Mission Control Systems and support tools. Present Activities: The MOIS mission preparation tool in ESOC and European Space Industry

****************

60

Alastair Pidgeon SciSys UK Ltd United Kingdom Title Presentation: Space Internet Working & DTN Prototyping. Present Activities: Manager of the Systems and Ground Segment Business Group with responsibility for managing the group of over 40 staff, maintaining high‐level customer contacts (e.g. with ESA, Eumetsat, Eutelsat, Astrium, ESO), business development, managing the group staff/resources, managing the group budget and reporting to the SciSys board. Business Development Executive responsible for business development in real‐time simulations for space and defence applications, ground control systems and automation for commercial, scientific and navigation space missions. Attend UKISC Galileo Working Group and was editor of the ECSS Modelling and Simulation Working Group. This involves an excellent understanding of the missions, the mission operation needs and what can be done with the technology underlying our solutions (e.g. SCOS‐2000, Java, XML, C++, processor emulators, SIMSAT, Windows NT/2000/XP, LINUX, SMP, and HLA).

**************** Erwann Poupart CNES France Title Presentation: Where do we stand with CCSDS SM&C at CNES ? Activities: Erwann Poupart holds a Master’s Degree in Computer Science Engineering from the Institut National Polytechnique de Grenoble (INPG), France. Since 1990, he is a ground segment software engineer at CNES, Toulouse, France. He has 20 years of experience with many space projects in the area of mission control systems. He is currently responsible for several Research & Technology studies in the area of middleware and modeling, and he is involved in standardisation activities in the CCSDS SM&C (Spacecraft Monitoring & Control) working group.

**************** Furio Riccio Logica Deutschland GmbH & Co. KG Germany Title Presentation: GSMC Implementation Past Activities: Senior software developer and architect for:

EDDS Galileo SCCF System Supervisor Herschel & Planck Mission Planning System TMCR PROBA 2

Project Manager and Configuration Manager for the Herschel Planck Repatriation project Configuration Manager and Team leader for SCOS‐2000 R3.1 Present Activities: Project Manager and Design Authority for the GSMC Implementation project.

**************** Alessandra Rossetti Inmarsat Ltd United Kingdom Title Presentation: Inmarsat: automation of satellite and ground operations Present Activities: Operations Engineer in the Inmarsat Satellite Control Centre and responsible for the engineering of the ground and satellite procedure automation

****************

61

Fausto Roveda Logica Deutschland GmbH Germany Title Presentation: Fox: Mission Automation System for the International Space Innovation Centre Past Activities: Fausto has more than 15 years of experience in software engineering for ground systems; he has been involved with a large number of software development projects and studies for Eutelsat, ESA and EUMETSAT. Before joining Logica he was Site Manager at MakaluMedia GmbH and previously Senior Software Engineer at CS‐Italia Spa. Present Activities: Fausto joined Logica in 2009 assuming the Delivery Manager role at Logica Darmstadt Business Unit with responsibility for the overall project delivery organisation of the unit. He was the Project Manager and Design Authority on the Fox Mission Automation project.

****************

Pierre‐Yves Schmerber Thales Alenia Space France Title Presentation: Thales Alenia Space vision on future Ground Control System Software Past Activities: Participation to the Aspis Esprit project for rule based access control Participation to the Satexpert research project for model based satellite diagnosis Delivery of the Sirius 2, Eurasiasat 1 and Turksat 3A Control centres Leader of internal control centre product line Present Activities: Head of control centres in Thales Alenia Space Member of the Steering Engineering Team for EGS‐CC project

**************** Pirada Techavijit Geo‐Informatics and Space Technology Development Agency (Public Organization) ) Thailand Title Presentation: Development of SODAs for improving efficiency and security for satellite control Past Activities: Master: specialized master of Embedded System from ISAE (Institut supérieur de l'aéronautique et de l'espace) Toulouse, France. Bachelor: computer engineering from KMITL (King Monkut’s Institute of Technology Ladkrabang), the institute in Bangkok, Thailand Present Activities: Satellite Control Engineer Function: satellite control and recovery, satellite monitoring, telemetry Trend analysis

**************** Dr. Andrea Thelen S.E.A. Datentechnik GmbH Germany Title Presentation: Architecture of the Telemetry Data Management System SpaceMaster Past Activities: Research associate at the “Forschungszentrum caesar” in Bonn working on the digitization of holographically stored 3D information. Present Activities: Software developer and architect for the SpaceMaster Telementry Data Management System at S.E.A. Datentechnik GmbH in Cologne

**************** Roger Thompson SciSys UK Ltd United Kingdom Title Presentation: CCSDS Mission Operations Services Overview and current Status Present Activities: An experienced Software Architect, with more than 26 years experience in spacecraft mission control systems. He is a member of international standardisation committees for the Space domain, and is currently active in the specification of service‐oriented reference architectures for space systems.

62

http://www.isae.fr/

http://www.isae.fr/

CCSDS and OMG, BNSC Representative & UK National Expert Representative to CCSDS: the

international committee for space data standardisation, on behalf of British National Space

Centre

Deputy Chair of the CCSDS Mission Operations and Information Management (MOIMS) Area;

Deputy Chair of CCSDS Spacecraft M&C Working Group, developing developing a Service Oriented

Architecture (SOA) for space mission operations and associated standardised services.

Previously the BNSC Representative to Object Management Group (OMG) Space Domain Task Force. A member of the SciSys management team for their Space Division, focussing on strategic technology for Space Systems and Ground Segments.

****************

Miguel Tortosa Eutelsat France Title Presentation: Satellite control systems provision and maintenance choices Activities: Ground Segment Procurement and Engineering

**************** Gert Villemos Logica Germany Title Presentation: The Fantastic Four, ‘Be lazy. Don’t code; Assemble!’ Past Activities: Gert has worked for over 10 years in the space business. He did his time on SCOS as project manager for a series of releases upto release 3.1 and has at some point or other worked on almost all other parts of the ground segment. He has worked extensively with formal methods, reference architectures and reference models and is a certified ‘Enterprise Architect’. The last many years he has primarily focused on new development and the use of novel and innovative technologies in the space domain. He considers himself an Agile evangelist and is a certified ‘Professional Scrum Master’. Present Activities: Gert is currently involved in the development of an operational reference model for space under CCSDS, the development of a data warehouse for GNSS data and a study into the usage of Android OS on small satellites. Due to his fascination of new technologies and unorthodox solutions, Gert have the great honour of holding the title as ‘Chief Lunatic’ at Logica. .

**************** Julio Vivero GMV Spain Title Presentation: Ground Segment Security: light and shade Past Activities: In 2004 I did some post‐doctoral research on network management and security in ad‐hoc networks. I joined GMV in June 2004 to work as security consultant and project manager within a Telecommunications operator.

63

64

Present Activities: Since 2008 I’m responsible of the Information Security Consulting area of GMV in Barcelona where we develop projects linked with information security management, risk assessments, security audits and information security area activities. As part of our activities we have collaborated with satellite operation organizations in the definition, implementation and support of their information security management systems and safeguards. I currently hold the following certifications: BS25999 Lead Auditor, CISM, CISA, CISSP, CSSA, GCIH, PMP

**************** Douglas Wiemer AEPOS Technologies, A Division of the ADGA Group Canada Title Presentation: “Automated Computer Network Defence” Past Activities: Douglas (Doug) Wiemer is a retired Canadian Armed Forces Captain. He graduated with a Bachelor of Engineering in 1990 and a Masters of Engineering in 1995, both from the Royal Military College (RMC) of Canada. As a Communications and Electronics Officer in the Canadian Forces he served a variety of roles, leaving a post specializing in information security for Command, Control, Communications, Computer, Intelligence, Surveillance and Reconnaissance (C4ISR) systems in 1997 to join the private sector. He worked as a security consultant from 1997 to 2000 and then moved to product related Research and Development at Alcatel (now Alcatel‐ Lucent) from 2000 to 2008. During his time at Alcatel he held various research, development and management roles all related to the development of security related products or products with embedded security features. In 2005 he was assigned as the manager of a team delivering a prototype Computer Network Defence (CND) system to the Network Information Operations (NIO) Section of Defence Research and Development Canada (DRDC). Following delivery of the DRDC prototype, Doug was promoted to Director of Software Development and given the responsibility to turn the prototype into a product. In January 2009, Doug started working for AEPOS as the Manager of the IT Security Engineering Group where he continues to provide security engineering services to government, defence and commercial clients. Present Activities: Since July 2010, Doug has been on contract to the Network Information Operations (NIO) Section of Defence Research and Development Canada (DRDC) as the Deputy Project Manager responsible for many aspects of the project scoping, definition and delivery of the Automated Computer Network Defence (ARMOUR) Technology Demonstration (TD) project.