2014 Airbus Defence and Space All rights reserved

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. Core concepts from European Space Data Modeling Approaches as input to the Rf. P OMG Technical Meeting La Jolla 2015, 6 th – 11 th December 2015 Harald Eisenmann Airbus DS, Hans Peter de Koning ESA 8 th December 2015

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 • • • 7 December 2015 Confidential Experience from European Data Modeling Approaches as “Other Industry Ontology” input ECSS-E-TM-10 -23 ECSS-E-TM-10 -25 ESA Virtual Spacecraft Design EGS-CC Airbus internal activities 2

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. Objective of the ECSS-E-TM-10 -23/5 data models was to fill a gap in the overall data management approach

Confidential The basis for scoping is to identify SE activities, in the actual context where SE is being performed, which directly leads to… Systems Engineering Customer Supplier Concept of Operations omposit nal Dec Functio ent irem Req u ion 4 tion Domain Discipline Engineering Budgets and Budget Tracking ica 7 December 2015 Domain Discipline Engineering erif Domain Discipline Engineering m. V Interdisciplinary Integration & Coordination Assumption Management ste cture Configuration Control Sy Change Management Archite s. E ngi nee ring Consideration of Life-Cycle Aspects System © 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 System Trades Domain Discipline Engineering

Confidential … the identification of data, which is underlying the SE process and forms the System Model Requirements Engineering Tool Functional Decomposition Data MS Excel Operational Concepts Data Scope of System Data Repository according to ECSS E-TM-10 -23 and 25 Domain Discipline Data 5 PDM (Meta-) data for change management System Verification Data Items As Built AIT Engineering Data Monitoring and Control Data AOC Engineering Data Assembly Tree OBSW Engineering Data Configuration Tree Electrical Engineering Data Product Tree Mechanical Engineering Data Requirements Data Product Structure Interdisciplinary Shared Data 7 December 2015 System Architecture / Specification Tool Sys. ML, Capella, MEGA System Architecture Data Key System Properties (budget, margin, assumptions) PDM (Meta-) data for configuration management © 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Verification Database Domain Discipline Data

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 7 December 2015 Confidential ECSS-E-TM-10 -23 “Space System Data Repository” provided the scoping and definition of the underlying conceptual data model Cost reduction for DB Improve Quality of Data Timely arrival of DB Improve Tool Integration 6 ECSS-E-TM-10 -25 adopted the 10 -23 ideas for concurrent design facilities

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential The concepts delivered by ECSS E-TM-10 -23/5 have been the major driver for new solutions along the lifecycle Agency System Prime ESA Virtual Spacecraft Design (Approach Validation) ÊSA CDF • • CDF supporting conceptual design VSD as MBSE E 2 E demonstrator – blue print • • Range. DB is the operational realization EGS-CC shared G/S segment component ESA-led EGS-CC Airbus DS Range. DB Suppliers 0 System 7 December 2015 A Avionics B C Operation D E Life Cycle Phase 7 F

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. Requirements towards the future system modeling environment

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 7 December 2015 Confidential The data model decomposition follows the data produced along the system development life-cycle 9

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 7 December 2015 Confidential Sample range of multi-disciplinary aspects supported by 10 -23 Functional Aspects Geometric Aspects Product Structure Operational Procedures Operational Modes Electrical Interfaces 10 Monitoring & Control Data

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 7 December 2015 Confidential In 10 -23 “system element” is the core of the CDM – identifying “physical” items of interest along the life-cycle 11

Confidential Mechanical Architecture System Architectural Design Electrical Architecture Configuration Model Product Tree, Specification Model Product structure as the needed element to represent the proper system model along the system life-cycle, with discipline aspects Assembly Models, As-built Models © 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 7 December 2015 Mechanical Design Software Architecture Operational Architecture System Detailed Design (Configuration) Mechanical Design Software Design Operational Design Flight Model #1 System Assembly Flight Model #2 System Assembly 12

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Data modeling related requirements • The conceptual data model shall be defined such that it can be automatically transformed into a runtime representation comprising • Definition of data structures, relations and properties • Definition of model transformation / and mapping rules • Definition of constraints on the data structures • Definition of functional dependencies of data model • For the CDM a single configuration control system shall be in place • Standardization of function-oriented data models like consistency check, version control, …, view models • For official versions of the CDM free data sets for conformance testing shall be available ( cax-if. org) • Widely share quite practical, but essential means to make integration happen e. g. like Long term stable object identifier UUID v 4, identifier mapping, … 7 December 2015 13

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Requirements related to the utilization of the conceptual data model • The CDM shall be defined in a way, allowing the correct and maintainable implementation of the CDM – by means of MDA Formal specification of Data with end user • meaning Function dependent data model shall be standardized with the Sys. ML 2 standard • Transformation of all elements of the CDM (class, CC, transformation, . . . Considering propagation) Function dependent implementation languages and Data models constraints Conceptual Data Model (CIM) Conceptual issues Model Transformation and Technology binding Logical Data Model (PIM) Implementation Constraint Code generation Implemented in the target tool, framework 7 December 2015 Implemented Function dependent Data models Implemented Data Model (PSM) (Source code) 14

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Framework allowing the automated configuration from the conceptual • The runtime framework shall allow data model • Conceptual Data Model • Data Management the automated configuration from an CDM. The runtime framework shall have no dependencies to the CDM Some functions might have the ability to be re-configured from the data model Data Representation and Manipulation Data Representation Data API Consistency Checking Data Transformation Ownership Comparison Branching / Merging Data Patching 7 December 2015 MMI 15 Reporting Scripting Versioning Smart Editing Query Data Propagation

• © 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Methodology for the data modeling Functional Requireme nts Existing Models System Concept Definition CDM Requirements Definition Analysis of the Domain Sample Data Conceptual Data Model Definition Requireme nts Preliminary validation of CDM Data Model Sample from EGS-CC 7 December 2015 16 For the data modeling a dedicated data modeling methodology Confidential shall be defined and applied covering • Data model specification from the end user perspective • Data model definition with an appropriate language • Data model validation Operational Implementation Preliminary Validation Set Validation Data Set

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Meta Model Architecture, including tailoring (kind of profiling) Generic CDM Sys. ML v 2 CDM Domain Specifc Tailorings Sys. ML v 2 CDM Tailoring for Automotive Sys. ML v 2 CDM Tailoring for Aeronautics Sys. ML v 2 CDM Tailoring for Space Sys. ML v 2 CDM Tailoring for ECSS Company specific Tailorings Sys. ML v 2 CDM Tailoring for Airbus 7 December 2015 17 …

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Requirements related to the runtime configuration of the modeling framework (kind of model-libraries) • RDL is similar to UML/Sys. ML Model. Library Semantic Data Model Standard Semantic Data Model “Master Definition of Concepts” addresses “what” not “how” “Reference Data Libraries (RDLs) “ Runtime loadable predefined objects, including QUDV and Categories Automated transformations Generated Derived Logical and Physical Data Models 7 December 2015 Runtime use Software Implementations Database • • Tool • Tool 18 It shall possible to define RDLs It shall be Interoperable possible totools configure the and databases modeling framework with the RDL, (including adapters without need for existing programming around tools) It shall be possible to model the RDL in the same environment as the CDM

Confidential Realizing MBSE – for multi-disciplinary aspects requires to advance the transverse data management functions Operational Engineering Workbench Electrical Engineering Workbench Control Engineering Workbench FSW Engineering Workbench Mechanical Engineering Workbench AIT Engineering Workbench Data Management Systems Engineering Workbench Sharing and Exchange of Data PDM / PLM System Engineering 7 December 2015 Mechanical Engineering Avionics 19 Engineering Workbench Change Control © 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 AIT

Confidential The fine-grained model management requires a conceptual data model, to manage consistency across the domains / life-cycle Engineering Workbench Systems Engineering Workbench Operational Engineering Workbench Electrical Engineering Workbench Control Engineering Workbench FSW Engineering Workbench Mechanical Engineering Workbench AIT Engineering Workbench White box Data Management Sharing, exchange and versioning of (detailed ) data Configuration Control and change management 7 December 2015 Data set is a released set of data used Avionics organization and version control ( close to PLM) System for data Engineering Workbench Conceptual Data Model Black box Data Management © 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 20 Mechanical Engineering AIT

• © 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 • Relation of the different layers of data management • • 7 December 2015 21 It shall be possible to organize data Confidential items into data sets It shall be possible to create data sets according to process constraints It shall be possible to merge, split data sets Data sets shall be loaded along with the model editing constraints

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential In a multi-disciplinary model clear ownership and access rights are needed as integral part of the modeling environment • • Fine-grained explicit Ownership of (or Responsibility for) model elements is needed • up to individual value properties Together with Roles provides basis for access rights management In Sys. ML v 1 Packages are used, but that limits Ownership to course-grained physical partitioning of model In E-TM-10 -25 / OCDT following model is proven to work well: • Person (member of Organization) represents human user (modeled compliant with LDAP) • Domain. Of. Expertise represents discipline / area of expertise • Participant represents a Person-Domain. Of. Expertise combination in a project team / for a model • One Person may be responsible for more than one Domain. Of. Expertise in a given team • More than one Participant may represent one Domain. Of. Expertise • Ownership by Domain. Of. Expertise • is stable in the long term, independent of Person that happens to be on the team at some point in time • Person. Role to define access rights at Modeling Environment level • Participant. Role to define access rights at Model level 7 December 2015 22

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 7 December 2015 Confidential Example E-TM-10 -25 data model for ownership and access rights 23

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential To support comprehensive but scalable capture of analysis / test results (or input) data: “Data. Cube” concept value property types Developed late ‘ 90 s in ESA STEP-NRF, EC GEM project, and ISO 10303 -51 Rich semantic data structure to store large amount of discrete values • Each cell of the Data. Cube is a scalar or tensor property (= quantity value) for a specific combination of observable element, value property and state • Designed for efficient storage and retrieval of massive amounts of structured data • Also mapped to / implemented in open source HDF 5 data format, see https: //www. hdfgroup. org/HDF 5/ observable elements states typically: sampled time or frequency 7 December 2015 24

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Evolved QUDV model in E-TM-10 -25 • • 7 December 2015 25 Separates Value. Property from Value. Property. Type • So that the types can be defined in a RDL/Model. Library and easily re-used by modelers Quantity. Kind integrated with Boolean, Enum, Text, Date/Time types Adds proper support for Measurement Scale (in addition to Measurement Unit): • Ratio. Scale, Cyclic. Ratio. Scale, Interval. Scale, Ordinal. Scale, Logarithmic. Scale Compound and Array Value Property Type • Allows representation of (nested) compound value properties, vectors, matrices, higher order tensors URI Value Property “Element. Reference. Property. Type” unified with Value. Property. Type Automated scale conversion algorithm (including ISO and US units/scales) Can present / demonstrate in a next meeting

OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential © 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. Applying ontology modeling for the definition of standards (Fact-Based Modeling methodology) Very powerful automated “verbalization” into structured natural language that can be validated by subject matter experts Each subservice type is defined within exactly one service type. Each service type defines some subservice type. It is possible that some service type defines more than one subservice type. Each subservice type has exactly one subservice type name. Each subservice type name is of exactly one subservice type. In each population of subservice type realisation is required by tailoring, each subservice type occurs at most once. *Subservice type realisation is implicitly required if and only if it is not true that (that subservice type realisation is required by tailoring). In each population of subservice type realisation is implicitly required, each subservice type occurs at most once. In each population of subservice type allows multiple realisations within a single service, each subservice type occurs at most once. *Service type defines mandatory subservice type if and only if that service type defines that subservice type where that subservice type realisation is implicitly required. Each service type defines some mandatory subservice type. 07/10/2015 Slide provided by Serge Valera (ESA)

Confidential Important for Sys. ML 2. 0 is to be clear on the scope … in terms of supported functions Systems Engineering Workbench Operational Engineering Workbench Electrical Engineering Workbench Control Engineering Workbench FSW Engineering Workbench Mechanical Engineering Workbench AIT Engineering Workbench Transverse Services Control integration of the engineering application Engineering Tools Engineering Workbench Data Integration (Interdisciplinary exchange, sharing and versioning of data ) Process Integration (Dependency management, work-flow, NC data, process management) Transverse Functions © 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Tool independent browsing, viewing, searching and review & annotation of models and data Sys. ML 2. 0 shall be precise in terms of scope of covered functions and assumed functional context PDM / PLM System Engineering 7 December 2015 Mechanical Engineering Avionics 27 AIT

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential … and in terms of supported processes • • The full scope of systems engineering shall comprise • System architecting activities • Life-cycle coverage from requirements through verification • Interface engineering • Interdisciplinary orchestration – integration and control • budget engineering, tracking and control. . . including assumptions and margins • Supply chain integration including ICDs and design consolidation • … For those tasks in the MBSE context the data shall be available 7 December 2015 Sys. ML 2. 0 shall be precise in terms of supported systems engineering process. 28

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Product tree to capture the basic decomposition of a system into its “types” <Element. Definition> Gravity. Sat <Element. Definition> AOCS <Element. Definition> STR • <Element. Definition> CGPS • <Element. Definition> ACT <Element. Definition> OCT <Element. Definition> HPLV <Element. Definition> DHS <Element. Definition> OBC 7 December 2015 29 • • Abstract definition of system elements One item for every system element type Provision of structure for ICDs, documents, etc. Definition of design characteristics “as specified”

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Specification Tree, to capture, the next lower level identification of blocks, functions, modes, parameters, …. <Element. Definition> Gravity. Sat type <Element. Usage> dhs : DHS aocs : AOCS type <Element. Definition> DHS AOCS <Element. Usage> obc : OBC <Element. Usage> cgps-a : CGPS cgps-b : CGPS str-1 : STR str-2 : STR type <Element. Definition> CGPS 7 December 2015 <Element. Usage> act-1 : ACT act-2 : ACT oct-1 : OCT oct-2 : OCT hplv : HPLV 30

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Configuration Tree as (explicit) design representation of blocks, modes, I/F, parameters, monitoring and control data – fully linked!! <Element. Configuration> Gravity. Sat <Element. Configuration> dhs : DHS aocs : AOCS <Element. Configuration> obc : OBC cgps-a : CGPS cgps-b : CGPS str-1 : STR str-2 : STR <Element. Configuration> act-1 : ACT act-2 : ACT hplv : HPLV <Element. Configuration> oct-1 : OCT oct-2 : OCT • • 7 December 2015 Explicit specification and distinction of every single system element Modeling of configuration-dependent aspects, e. g. electrical interfaces between components 31

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Assembly model to support integration, verification and operation is configured by Configuration Model <Element. Configuration> Gravity. Sat Assembly Model < Element. Configuration > < Element. Occurrence > dhs : DHS aocs : AOCS <Element. Occurrence> Gravity. Sat FM 1 <Element. Occurrence> < Element. Occurrence > dhs : DHS aocs : AOCS < Element. Configuration > obc : OBC cgps-a : CGPS cgps-b : CGPS str-1 : STR str-2 : STR is configured by < Element. Occurrence > obc : OBC cgps-a : CGPS cgps-b : CGPS str-1 : STR str-2 : STR <Element. Occurrence> Gravity. Sat FM 3 Assembly Model <Element. Occurrence> Gravity. Sat FM 2 <Element. Occurrence> < Element. Occurrence > dhs : DHS aocs : AOCS < Element. Occurrence > < Element. Occurrence > obc : OBC cgps-a : CGPS cgps-b : CGPS str-1 : STR str-2 : STR 7 December 2015 32

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential The Assembly Models integrate Elements As Built Assembly Model <Element. Occurrence> Gravity. Sat FM 1 <Element. Occurrence> < Element. Occurrence > dhs : DHS aocs : AOCS OBC KX 225_3_485 integrates < Element. Occurrence > cgps-a : CGPS cgps-b : CGPS < Element. Occurrence > str-2 : STR integrates <Element. Realization> < Element. Realization> OBC KX 225_3_485 STR_22 STR_56 <Element. Realization> < Element. Realization> OBC KX 225_3_483 STR_25 STR_35 Realized items (shelf) 7 December 2015 STR_22 33

© 2014 Airbus Defence and Space – All rights reserved. The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design. OMG Technical Meeting La Jolla 2015, 7 - 11 December 2015 Confidential Princinple of Aspects for detailing the system Product Tree <Element. Definition> <Value. Property> STR mass = 0. 70 kg <Element. Definition> AOCS Specification Model <Element. Usage> <Value. Property> str-1 : STR mass = 0. 70 kg <Element. Configuration> Gravity. Sat Configuration Model Defined Aspect <Element. Configuration> aocs : AOCS Propagated Aspect <Element. Configuration> <Value. Property> str-1 : STR mass = 0. 70 kg <Element. Occurence> Gravity. Sat FM 1 Assembly Model As-built Model 7 December 2015 <Element. Occurrence> aocs <Element. Occurrence> <Value. Property> str-1 mass = 0. 694 kg <Element. Realization> <Value. Property> STR-22 mass = 0. 694 kg 34