Electrical AIT and EGSE

1. Electrical AIT and EGSE Author: Bryan Melton 2nd ESA Space System Design, Verification and AIT Workshop

2. Outline • Scope • Objectives of R&D in this domain • Relevant technologies • Major R&D activities envisaged 2nd ESA Space System Design, Verification and AIT Workshop

3. Scope • AIT comprises a very significant part of the space system development programme and is subject to many pressures to decrease costs and schedule. • need to identify the activities to be performed in order to introduce new technologies, methods and tools to the domain. • EGSE comprises all facilities required to monitor and control a space system during electrical integration and test, across all levels of testing, from equipment to system level. • A major element in AIT and EGSE technology is software engineering and the supporting informatics tools. • The Agency is embarking upon a new class of mission that requires a fleet a spacecraft to implement the GALILEO services. 2nd ESA Space System Design, Verification and AIT Workshop

4. Objectives • To harness Information technology to the benefit of the AIT engineer • To provide the necessary tools to support the trends in space system development towards more loosely coupled systems, especially in the early phases of integration. • To support European industrial competitiveness, in moving towards genuine COTS products in the EGSE domain • To provide methods, tools and working practices that implement European Space Standards (and contribute to their development) 2nd ESA Space System Design, Verification and AIT Workshop

5. Information systems EGSE architecture Spacecraft design AIT tools Spacecraft model philosophy ECSS standards Earlier & ongoing work Virtual Integration New class of missions INPUTS MAIN SECTORS 2nd ESA Space System Design, Verification and AIT Workshop

6. Information systems EGSE architecture Spacecraft design AIT tools Spacecraft model philosophy ECSS standards Earlier & ongoing work Virtual Integration New class of missions • FDIR assistance • test coverage analysis • Test reporting • ECSS E-70 compliance (test procedures) INPUTS MAIN SECTORS 2nd ESA Space System Design, Verification and AIT Workshop

7. AIT Tools • Test engineers demand more sophisticated tools to support their task of AIT procedure specification, development and reporting. • Early detection of faults together with the associated reason for a failure is essential to maintaining cost and schedule. • Capturing knowledge of the intended behaviour of a space system and utilising it to predict the cause of failure is required. • Validation of this knowledge is needed in order to bring a coherent and validated set of data to the flight operations domain to assist in rapid fault diagnosis. 2nd ESA Space System Design, Verification and AIT Workshop

8. AIT tools • Capture of FMECA data has already been proven to aid fault investigation. • Information systems that provide tools to assess the level of test coverage through gathering of statistics from test sessions, together with the ability to generate reports directly from executed tests are requested. • Commonality of monitoring and control data (e.g.procedure definition) between test and operations as defined in ECSS-E-70 standards will enable: Fly as you test Test as you fly 2nd ESA Space System Design, Verification and AIT Workshop

9. FDIR assistance • test coverage analysis • Test reporting • ECSS E-70 compliance (test procedures) Information systems EGSE architecture Spacecraft design AIT tools Spacecraft model philosophy ECSS standards Earlier & ongoing work Virtual Integration New class of missions • Interconnection without integration • Local integration • Remote integration • Networking ( Fixed, Wireless, Bridging • to on-board networks) • EMC issues MAIN SECTORS INPUTS 2nd ESA Space System Design, Verification and AIT Workshop

10. Virtual Integration • Model philosophies are tending towards bench level integration of important elements. • Supports early integration and test of equipment containing flight software and provides an ideal test bed for development and rehearsal of test procedures to be employed in the testing of the flight model. • Allows interface and protocol verification both for the avionics elements and for early models of instruments or experiments • Move towards “virtual satellite” 2nd ESA Space System Design, Verification and AIT Workshop

11. Virtual Integration • To support a concept of “loosely integrated elements” it is intended to study:- • the application of wireless network technology in an AIT context. • “Data integration” so that elements of space systems can be logically integrated without being physically integrated. • Synergy with “teletesting” approach 2nd ESA Space System Design, Verification and AIT Workshop

12. FDIR assistance • test coverage analysis • Test reporting • ECSS E-70 compliance (test procedures) Information systems EGSE architecture Spacecraft design AIT tools Spacecraft model philosophy ECSS standards Earlier & ongoing work Virtual Integration New class of missions • Interconnection without integration • Local integration • Remote integration • Networking ( Fixed, Wireless, Bridging • to on-board networks) • EMC issues • Space System Model • Design knowledge • Test procedure and results • Model descriptions • Planning and scheduling • ECSS E-70 compliance and extension MAIN SECTORS INPUTS 2nd ESA Space System Design, Verification and AIT Workshop

13. Information systems • The complexity of space systems is such that informatics tools are required to collect, organise, publish and utilise information related to the system under development. • Functional testing is performed to ensure that once integrated with other elements, an element of the space system continues to work as expected • This testing requires utilisation of knowledge that describes the behaviour of a system. • Existence of this knowledge base will facilitate the development of more sophisticated tools to be put at the disposal of AIT engineers. 2nd ESA Space System Design, Verification and AIT Workshop

14. Information systems • Ability of Space System Model (as defined in ECSS-E-70) to capture space system element knowledge required for AIT and Operations. • Design knowledge representation (e.g for intelligent monitoring and control) • Integration and consistency of all EGSE information • Tracking of spacecraft models (especially for series) and units • Validation of ECSS-E-70 Ground systems and operations), E-70-31 (Monitoring and Control data definition) and E-70-32 Procedure Definition Language 2nd ESA Space System Design, Verification and AIT Workshop

15. FDIR assistance • test coverage analysis • Test reporting • ECSS E-70 compliance (test procedures) Information systems EGSE architecture Spacecraft design AIT tools Spacecraft model philosophy ECSS standards Earlier & ongoing work Virtual Integration New class of missions • Interconnection without integration • Local integration • Remote integration • Networking ( Fixed, Wireless, Bridging • to on-board networks) • EMC issues • Space System Model • Design knowledge • Test procedure and results • Model descriptions • Planning and scheduling • ECSS E-70 compliance and extension • Web based architectures • Interfaces using XML • MMI portable devices • PUS service based EGSE • E70 compliance • Commonality across mission phases • Ground System harmonisation MAIN SECTORS INPUTS 2nd ESA Space System Design, Verification and AIT Workshop

16. EGSE architecture • Use of “serviced based” on-board software architectures demands equivalent, mirrored services in ground systems • Architectures of EGSE where elements are viewed as service providers and service users in an environment based on web addressing and communication • will promote “remote testing” capability using available commercial technologies (especially in the domain of safety and security) 2nd ESA Space System Design, Verification and AIT Workshop

17. EGSE architecture • More mobility in AIT through portable MMI devices • Use of PDAs or tablet PCs • Use of wireless networks • Use of web services • Standardisation of information transfer (e.g. through use of XML) 2nd ESA Space System Design, Verification and AIT Workshop

18. EGSE architecture • Commonality between all phases of the project life cycle (pre-and post-launch) • The availability of a combined EGSE and Mission Control System (EMCS) software brings considerable benefit. • Common approach can ensure a smoother and more efficient transition from AIT activities to operations activities (transfer of databases, procedures etc). • Commonality of MCS and EGSE leads also to commonality of tools. • Harmonisation will lead to adaptation or emergence of new systems in long term 2nd ESA Space System Design, Verification and AIT Workshop

19. Information systems EGSE architecture Spacecraft design AIT tools Spacecraft model philosophy ECSS standards Earlier & ongoing work Virtual Integration New class of missions • FDIR assistance • test coverage analysis • Test reporting • ECSS E-70 compliance (test procedures) • Interconnection without integration • Local integration • Remote integration • Networking ( Fixed, Wireless, Bridging • to on-board networks) • EMC issues • Space System Model • Test procedure and results • Model descriptions • Planning and scheduling • Design knowledge • ECSS E-70 compliance and extension • Specification and architecture • Web based architectures • Interfaces using XML • MMI portable devices • PUS service based EGSE • E70 compliance • Commonality across mission phases MAIN SECTORS INPUTS 2nd ESA Space System Design, Verification and AIT Workshop