1. Presentation to Francisco Barreiro.- Engineering Director, Aerosp. Div. Moscow 30th June 2006

2. Interests & Objectives  To present: TCP’s overall company capabilities and expertise (briefly) TCP’s overall activities in the aerospace sector (briefly, also) A brief summary of the results of Phase A activities conducted by TCP, within AE ESP2003-10799-E TCP’s possible contribution and interests

3. TCP Sistemas e Ingeniería  TCP Sistemas e Ingeniería, S.L. is a Spanish independent company in the field of Software Engineering  The company was set up in 1992 by a group of professionals coming from the Informatics, Communications and Aerospace businesses  TCP’s headquarter is placed in Madrid (Spain). Besides, the company has offices in Valladolid (Spain), Ashburn (VA, USA) and Sao Paolo (Brazil)  Currently TCP employs nearly 300 highly skilled professionals (90% university graduates)  The Aeroespace Division represents aprox. a 10% of the company

4. TCP: A bird’s eye view TCP Management systems ITIL Business Processes Requirements Engineering Man-Machine Collaborative Control Systems Mobility Operators& PTTs IT Systems Banks Insurance Co. Aerospace Transport Telecom IRqA SW Factory

5. Aerospace BU  TCP’s expertise in the aerospace field started since the company origin in 1993.  Presently, TCP’s Aerospace Division is formed by 25 engineers working in two main fields of activities: On-board SW Ground Segment: Monitoring and Control (M&C) and Tele-operation applications  Our main customers in this sector are ESA, specially ESOC, and EADS-CASA

6. On-board Software  Our main fields of expertise in on-board SW are: Real-Time Developments Safety-Critical Developments Testing: Test Harness Generation (THG) Certification (RTCA-DO/178B)  Specifically, TCP is working since 2004 in the development, implementation and validation of a adaptive flight control system for UAV (Unmanned Air Vehicles)  Other open areas in this field include autonomy systems for planetary missions, combining on- board capabilities of control, navigation, planning and autonomous decision making, with ground based capabilities

7. Ground Segment: M&C Systems  Stations Management: GMCT: General M&C Tools CSMC: Central Station M&C, allows automatic ground station control and fully remote operations FEC-NT: Antenna Front-End Controller, ESA’s baseline for its EO and DSN stations PPIU: Power Plant Interface Unit, provides station power plant M&C SDAS: Building installations supervisory systems Kiruna (CSMC, PPIU, FEC) Redu (PPIU,FEC) Kourou (FEC, PPIU) Goldstone (NDIU) Malindi (FEC,CSMC) Maspalomas (FEC) ESOC (CSMC, PPIU) ESTEC (SDAS) New Norcia, Perth (FEC) Villafranca (PPIU, FEC, CSMC) Cebreros (FEC)

8. 34.  Scientific Operations SAVIO: SOA framework & components for web- based distributed systems DYNACORE: provides instrument remote operation CMMOC: Multimission Scientific Operations Centre Ground Segment: Tele-operation

9.  Mission requirements and assumptions  Ground Stations Technical requirements  Ground Stations proposed baseline Phase A: Ground Stations System  WP 3400 output documents: Ground Stations part of  Customer Requirements Document  Ground Segment Baseline Definition  Space to Ground Interface Control Document  Final report

10. Ground Segment Structure GROUND SEGMENT Ground Operations Organisation GROUND SYSTEM Mission Control System EGSE´s Ground Communications Subnet Ground Stations System Supporting Infrastructures MOC SOC Space Segment Control Stations Mission Exploitation Stations

11. Mission requirements and assumptions Telecommunications:  L2 orbit (1.6-1.8MKm), 5 years nominal mission  15M antennas, in X-band  ESA’s X-b near-earth transponder (like Hershel-Plank)  Max. data rate downlink 1.5Mbps.  Data production rate: 32 Gbits per day.  8 hours/day for downloading the data  Ground Stations under consideration: oArgentina (Falda del Carmen) oP.R. China (Miyun) oRussia (Facilities TBC) oSouth Africa (Sat. Appli. Centre, CSIR) oSpain (Villafranca, ESA)

12. Mission requirements and assumptions Other:  Minimize need of specific resources  Variable number of centres during the mission lifetime  Minimal requirements on architecture and communications infrastructure. Same configuration HW/SW in each layer  Distributed, international environment, ground segment distributed operations (scientific & mission)  Possible MOCs, SOCs role rotation  Up to 4 ground stations. Normal working hours operations, 2-3 hour-a-day per station

13. Ground Stations Technical Requirements  Functional requirements (15m antenna)  downlink: Xband. G/T=38Db/K  uplink: X band. EIRP=81dBW  ranging: required but not simultaneous TM rng  data rate: DL 1.5 Mbps / UL: 40/400 bps, 4kbps  data processing: CCSDS standard with Reed Solomon and Viterbi coding  Modulation SCD mode, OQPSK or GMSK  S/No 70dBHz  BER 1E-5 or less. 5dB TM recovery

14. Ground Stations Technical Requirements  Cross support and interoperability:  M&C: full station configuration and routine operations automation  SLE services: RAF, RCF, CLTU  Raw data storage & archive  Use of COTS  Design, implementation, maintenance  ECSS recommendations and SLE compliance

15. Ground Stations Technical Requirements  General requirements on Ground Station Network  Need of a GSN Management layer (1 to 4 stations co- ordinated) to ensure 8 h continued operations (routine)  Primary and backup network  TM on line real time transfer to MOC  Science transfer via offline public network  Support systems: operations automation and remote operation. Coordination tools.  Network interface: consider co-located CCs or enough bandwith to fullfill on line comms.

16. Ground Stations Proposed baseline Some TBDs:  Definition of G/S Service provision, to replace the requirement of identical HW/SW cfg (due to heterogeneous G/S)  WSO/UV mission service agreement  QoS TBD  Req. on G/S layer Coordination with MOC/SOC layer

17. Now some questions...  Modifications of the space to ground IF ?  Ground Stations to consider ?  Modifications on ground segment concept ?  Communications infrastructure ?  International standards (SLE) assumed ? ... ?

18. TCPSI possible contribution  Ground Stations  G/S Management (M&C, Automation)  Management of heterogeneous G/S Network:(remote M&C, scheduling and coordination)  Distributed SOC  Science goal tracking tools  planning & scheduling tools  workflow and coordination  remote payload operations via web  simulation framework tools  security tools  Proposals management tools  e-collaboration

19. C/ Fernández Caro, 7 28027 Madrid SPAIN Tel: +34-91-406 27 00; Fax:+34-91-407 71 39 www.tcpsi.com