1. Slide 1 ISO JCT1 SC32 WG2 Berlin 2012 The “Knowledge Sharing Challenge” for Partners in European Space Projects Serge Valera European Space Agency

2. Slide 2 ISO JCT1 SC32 WG2 Berlin 2012 The “Knowledge Sharing Challenge” for Partners in European Space Projects Serge Valera - ESA

3. Slide 3 ISO JCT1 SC32 WG2 Berlin 2012 Article 2 of the ESA Convention “To provide for and promote, for exclusively peaceful purposes, cooperation among European states in space research and technology and their space applications.”

4. Slide 4 ISO JCT1 SC32 WG2 Berlin 2012 19 ESA Member States Austria Belgium Czech Republic Denmark Finland France Germany Greece Ireland Italy Luxembourg Norway The Netherlands Portugal Spain Sweden Switzerland United Kingdom Romania

5. Slide 5 ISO JCT1 SC32 WG2 Berlin 2012 ESA’s presence worldwide Houston Washington Kourou Moscow Establishments Offices ESTEC (Noordwijk) Brussels ESA HQ (Paris) Toulouse ESAC (Villanueva de la Cañada) ESRIN (Frascati) EAC (Cologne) ESOC (Darmstadt) Harwell Redu Salmijaervi (Kiruna) Ground stations New Norcia Santa Maria Cebreros (Villafranca) Oberpfaffenhofen Maspalomas Perth Malargüe

6. Slide 6 ISO JCT1 SC32 WG2 Berlin 2012 ESTEC, Noordwijk, The Netherlands

7. Slide 7 ISO JCT1 SC32 WG2 Berlin 2012 ESTEC, Noordwijk, The Netherlands Principal responsibilities Studies, preparation and management of ESA space programmes: Launchers Science Earth observation Telecommunication Navigation Human spaceflight Deep space exploration Technical support to ESA project teams, including preparation and coordination of ESA space technology R&D programme Product assurance and safety for ESA space programmes Management of ESTEC Test Centre and coordination with other test centres in Europe Employs Approx. 2000 staff

8. Slide 8 ISO JCT1 SC32 WG2 Berlin 2012 Knowledge Sharing: the Problem Space system development partners usually differ from project to project Partners are geographically dispersed Different partners participate at different points in time in the project schedule Mother tongues differ (English and French are ESA’s “official” languages) Legacy/proprietary systems are often deployed Development processes and procedures are standardised but their application and interpretation vary Exchange of Information between partners is frequently misinterpreted

9. Slide 9 ISO JCT1 SC32 WG2 Berlin 2012 Typical ESA Project - EarthCARE Base Platform: Astrium Limited Launcher Russian Soyuz (Kourou or Baikonour) Zenit (Baikonour) Satellite Prime Contractor: Astrium GmbH ESA Kiruna Ground Station Star Tracker: Jena-Optronik GmbH Multispectral Imager: SSTL Broadband Radiometer: SEA Ltd. Flight Operation Segment: ESOC Backscatter Lidar: Astrium-SAS Cloud Profiling Radar: JAXA Onboard Computer: RUAG Aerospace Payload Data Segments: ESRIN JAXA for CPR

10. Slide 10 ISO JCT1 SC32 WG2 Berlin 2012 Knowledge exchange: Towards a solution Standardise the space system development and operation processes and their inputs & outputs Established in 1993 Members are European Space Agencies, National Space Agencies and European Industry Objective is to develop standards that address the “WHAT” of space system development and operation (not the “HOW”) More than 100 standards have been developed across 3 branches and 19 disciplines See www.ecss.nl for more detailswww.ecss.nl European Cooperation for Space Standardisation E CSS

11. Slide 11 ISO JCT1 SC32 WG2 Berlin 2012 ES... ES 2 ES 1 US... US 2 US 1 SSC … SSC 2 PSC 1 SSC … SSC 2 SSC 1 Unit Supplier Payload Subcontractor Subsystem Subcontractor Usually ESA Customer – Supplier Network Top-level Customer Customer Supplier Equipment Supplier Network of Customer-Supplier relationships Business Agreement Business Agreements Customer Supplier Customer Supplier Specifications Products and associated information PayloadSubcontractor Subsystem Subcontractor Satellite Prime Contractor PC E CSS

12. Slide 12 ISO JCT1 SC32 WG2 Berlin 2012 ECSS System Project Management Engineering Product Assurance Project planning and implementation Project planning and implementation Configuration and information management Configuration and information management Cost and schedule management Cost and schedule management Integrated logistic support Integrated logistic support Risk management Product assurance management Product assurance management Quality assurance Dependability Safety EEE components Materials, mechanical parts and processes Materials, mechanical parts and processes Software product assurance Software product assurance System engineering Electrical and optical engineering Electrical and optical engineering Mechanical engineering Mechanical engineering Software engineering Software engineering Communications Control engineering Ground systems and operations Ground systems and operations Branches Disciplines ECSS Document Architecture E CSS

13. Slide 13 ISO JCT1 SC32 WG2 Berlin 2012 Applying ECSS Standards to a Project The full set of ECSS documents constitutes the ECSS Universe of Discourse (UoD) A space project “tailors” the ECSS standards to create its Project Universe of Discourse. Tailoring means: selecting which ECSS standards are applicable de-selecting those requirements from each standard that are not applicable to the project exceptionally, modifying existing ECSS requirements adding project-specific requirements E CSS

14. Slide 14 ISO JCT1 SC32 WG2 Berlin 2012 Products within a Space Project For each product developed for and integrated in a Space Project, a Statement of Work (SoW) is generated containing: the product specification; Its interface specifications with the rest of the system. In the course of generating the SoW, the Project Universe of Discourse is further tailored to create a Product Universe of Discourse by: selecting which project-tailored ECSS standards are applicable de-selecting requirements that are not applicable to the product adding product-specific requirements assessing the compliance of the product to the project requirements and justifying deviations E CSS

15. Slide 15 ISO JCT1 SC32 WG2 Berlin 2012 European Space knowledge sharing – The needs = “Working Together” and exploiting “Knowledge” for consistent development and utilisation of the “Overall System” Need: Global Conceptual Modelling Language Promoted approach: Modelling at “GLOBAL” level The Overall System Need: “Engineering” methods and tools to develop “LOCALs” The Products Need: “Re-Engineering” methods and tools to re- engineer existing facilities for compliance with Global E CSS

16. Slide 16 ISO JCT1 SC32 WG2 Berlin 2012 Supplier Customer Utilisation Data Exchanging Knowledge: Toward Semantic Interoperability Requirements Meta-Data Developments Meta-Data Transformation System/User Specification Proposal & Compliance Preliminary Design Detailed Design Critical Design Qualification Delivery & Acceptance Verification At acceptance, Validation

17. Slide 17 ISO JCT1 SC32 WG2 Berlin 2012 Supplier Customer Model at global level to ensure semantic interoperability Implementation specifics Physical layer A formal language for specifying the conceptual models  Fact-Based Modelling Transformation algorithm from “Architecture” to ”Detailed Design/Coding” Technology specifics Logical layer A formal language for specifying the conceptual models  Fact-Based Modelling Transformation algorithm from “Specification” to ”Architecture” A Formal Language for Conceptual Modelling, rich enough to model GLOBAL including all LOCAL views Toward Semantic Interoperability - Engineering Conceptual layer

18. Slide 18 ISO JCT1 SC32 WG2 Berlin 2012 Toward Semantic Interoperability – Re-Engineering Supplier Customer Physical layer Logical layer Conceptual layer Assess the semantic compatibility between the two schemas Remove Implementation specifics Remove Technology specifics A formal language for specifying the conceptual models  Fact-Based Modelling A common formal language for conceptual modelling, rich enough to support compatibility assessment A formal language for specifying the conceptual models  Fact-Based Modelling A transformation algorithm to re-engineer to ”Conceptual Models” A formal language for specifying the conceptual models  Fact-Based Modelling A transformation algorithm to re-engineer to ”logical Models” Logical layer Conceptual layer

19. Slide 19 ISO JCT1 SC32 WG2 Berlin 2012 A Fact Based Modelling Architecture Ecosystem from an Overall System Perspective Standardising the development of Database Systems by: Providing methods and tools for data modelling at conceptual, logical and physical level Integrating data modelling with software engineering (including development of new systems, re-engineering of existing systems) Enabling knowledge exchange by: Providing the means to formally specify the Global Universe of Discourse Providing the means to view the Local Universes of Discourse i.e. managing all Locals at Global level European Space knowledge sharing – A solution FAMOUS = Fact based Modelling Unifying System

20. Slide 20 ISO JCT1 SC32 WG2 Berlin 2012 User /System Requirements Architectural Engineering Software Design Software Requirements Verification SWRR PDR DDR CDR QR AR Coding Testing Delivery & Acceptance Operation & Maintenance Validation √ √ Conceptual Data Model Physical Data Models Logical Data Models FAMOUS Database Software Engineering - 1

21. Slide 21 ISO JCT1 SC32 WG2 Berlin 2012 Logical Models RelationalHierarchical Object Oriented.. XSDXSD SQLSQL … MMIMMI MMIMMI XSDXSD … XMIXMI … Physical Models For Re-engineering FAMOUS Database Software Engineering - 2 Conceptual Model

22. Slide 22 ISO JCT1 SC32 WG2 Berlin 2012 At Global Level –Model the UoD for the System –Validate the global conceptual model At Local Level –Tailor the UoD –Extract the conceptual definitions for the local application –Validate the local conceptual model –Produce the logical and physical models ER DR VR FF FT CD EV Exchange rulesER Derivation rulesDR Validation rulesVR Fact type formsFF Fact typesFT Concept definitionsCD EventsEV Generic Component Domain-specific Component Facts Ground Facts Conceptual Schema FAMOUS Fact Based Conceptual Modelling Fact Based Conceptual Model The Knowledge Triangle The Knowledge Triangle THE KNOWLEDGE TRIANGLE