Space System Engineering Database

Integration and Collaboration Platform for the Engineering Domains in the Space Industry

Hans Peter de Koning (ESA) Niklas Lindman (ESA) Harald Eisenmann (EADS Astrium) Matthias Grau (PROSTEP) Outline

„ Requirements arising for engineering data management in the space industry „ ECSS ETM-10-23 „ Overview SSRM Project „ Introduction „ Platform Architecture „ MDA, SOA, BPEL „ Demo Scenarios „ Conclusions ans Outlook

April 07 Engineering Database Current situation (1)

„ In a spacecraft project, many engineering databases do exist, ... „ well designed for their domain „ only fragments „ made for a small section of the space system life cycle „ own database „ no data exchange (time-consuming, error-prone) „ ... otherwise standard office products are used „ covering a significant part of the space craft design and verification information

April 07 Engineering Database Current situation (2)

„ Consistent data management is hard to achieve „ inconsistencies between the databases „ manual work to transfer data between the databases „ difficult to get a consistent data sets needed for simulation tasks from data of more than one database „ no data life-cycle defined • change process • Identification of incomplete/valid data „ validation of data is difficult, often manually „ redundancy

April 07 Why "ready-to-use" Data Management Systems would not solve the Problem

„ Option 1: Document Management Systems „ DMS "think" document based … „ integration required on user data level rather than on administrative level only „ Option 2: PDM Systems „ PDM Systems can support workflows … Æ process level integration „ wrt. data management they function like DMS „ Option 3: DBMS „ DBMS alone would not resolve the data integration issue – semantic transformation needed between to-be- connected tool and DMBS „ DBMS are not process-aware

April 07 Consequence

An "Integration Platform" is needed that has the following characteristics: „ DBMS to store user/admin information in a tool-independent syntax and semantics „ capable to cover both, engineering data and process information „ database structure under control of DB owner „ Network-distributed environment as the basis for tool adoption „ but also the capability for a file-based exchange „ Platform independent integration architecture „ centrally manageable and conforming to industry standards „ Workflows to control exchange and communication processes from the user perspective „ flexible and configurable – not hard-wired

April 07 ECSS ETM-10-23 Rationale and Goals

ECSS-E-10 Part 1B (System engineering - Requirements and process) states: "System Engineering Integration and Control shall establish and control a database as a repository for engineering data from trade-offs, risk assessment, requirements, analysis, design, and verification"

Enable efficient access of project teams to Project DB project information Management Product Assurance DB Reduction of overall project investment in DB data base systems Ensure compatibility between the different Engineering DB phases and activities in a project: Engineering, System Engineering DB Testing and Operations Allow project data exchange across company boundaries Engineering DisciplEningieneering RelatedD DBisciplEningieneering Support implementation of modern system RelatedD DBiscipline engineering approaches including integrated Related DB project teams, distributed collaborative engineering, use of product data management systems etc. April 07 ECSS ETM-10-23 Top-level Data Model

„ System Engineering Data System Engineering Data „ Requirements, Functional, Requirement Verification Matrix Architectural and Physical Design Assembly & Verification Integration „ AIT Data (procedures, logistics, …) Functional Allocation Operational „ Verification Data (description, Design procedures, reports, …) Physical Architecture Accomondation System Allocation Functional Architectural Physical Design „ Operations Data (TM/TC Data, Design Design Planning, Operational Procedures, SystemElement Bus Data, …)

„ Engineering ElementCategory

ElementDefinition Discipline Formal Definition of common characteristics ElementOccurrence Related Data (attributes and properties): Formal Definition of a particular type of an Identifcation and Position of ElementRealisation equipment, device, … : an usage of an item of type ElementDefinition: Realistation of an item of „ Kept as Example data items are: type ElementDefinition - Technical Specification Example data items are: - Design Document references - unique identifier Example data items are: - ICD - position, placement - serial number - Bill of Material - integration constraints - As-built-status its primary - Test Plan - position dependent - test report - Product Number (Catalog) calibration curve - certificate - Geometric Shape data store - Assembly structure - delivery report/sheet - Default Calibration - Integration tree definition

April 07 Space System Reference Model (SSRM)

„ Consortium consisting of „ EADS Astrium „ EADS ST „ PROSTEP

awarded contract January 2007

April 07 SSRM – Study Focus

„ Assessment of the ETM-10-23 approach „ Definition of a methodology for the description of the data model „ Selection of a feasible technology for the transformation of the data model „ Elaboration of a data model for a central Assessment engineering database

„ Validation of the Methodology Technology deployment and usage in an operational context

Oper ational Implementation & Modelling Deployment

April 07 SSRM – Timeline

Task Name 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Qua Dec '06 Jan '07 Feb '07 Mar '07 Apr '07 May '07 Jun '07 Jul '07 Aug '07 Sep '07 Oct '07 Nov '07 Dec '07 Jan '08 Feb '08 Mar '08 Apr '08 WP1000 Project Management

WP 2000 Scenario Definition

WP 2100 Scenario Identification WP 2200 Scenario Description

WP 3000 Data Structure Mapping WP 3100 Assessment of DM Approach WP 3200 Data structure Mapping

WP 4000 Modelling and Translator Generation WP 4100 Implement Code Generator WP 4200 Demonstration Appliation Integration

WP 5000 Demonstration and Evaluation WP 5100 Set-Up/Test

WP 5200 Evaluation

Kick-Off 17.01 Kick-Off

Progress Meeting 1 17.04 Progress Meeting 1

PRR 29.06 PRR

Progress Meeting 2 14.11 Progress Meeting 2

Final Presentation 29.02 Final Presentati April 07 Use Cases for an Engineering Database (examples)

„ Submit data Engineering Database System „ Prepare data for review

„ Extract data Consitency check

„ Consistency check «extends» «extends» Agency Extract data for Engineering Disciplines «extends» review „ Operate data Extract data „ Versioning Submit data

„ Create baseline «extends» «extends»

„ Actors (Roles) Operate data

«extends» «extends» „ Agency SE Integration & Control Prime contractor „ Prime contractor / Subcontractor Versioning Create baseline „ Engineering disciplines Subcontractor „ System Engineering Integration & Control

April 07 Overview of the Technical Solution

TOOL A TOOL B (Virtual) Data Exchange

Tool API Adapter

Mapping Virtual Data Exchange SSR API) Adapter

Draft Meta- Model (ECSS 10)

datamodel approach

Data Structure Data Structure A SSRM B

Modelling

generated platform flexibility generated generated

Format Database Format Description A Definition Description B (e.g. XSD)

specifies format specifies format defines

Data A Data B Neutral exchange and (e.g. as XML) SSR DB integration layer April 07 Architectural Basis Service Oriented Architecture (SOA)

process „ Logic is encapsulated by services process step „ each service Service has a Service public interface with operations and parameters „ Typically, every SOA component (like a BPEL workflow) is a service and can be sub-process used by other Service components

Encapsulate logic with services

April 07 Architectural Basis Model Driven Architecture (MDA)

„ The Model Driven Architecture approach, defined by OMG „ enables the formal specification of a discipline-independent and neutral data model „ supports the ability to apply state- of-the-art development methods and technologies „ enables the transformation of a Computation Independent data model into several platform Model (CIM) specific implementations Platform Independent Model (PIM)

Everything is a Model Platform Specific Platform Specific Model (PSM) Model (PSM)

Implementation Implementation April 07 Basis for the Data Model

Requirements/Concept Analysis Detailed Design/BoM Manufacturing Lifecycle Support

Equipment Coverage Electrotechnical Data Supporting Work activities Components Configuration Operating Support • Power-transmission Systems • Terminals and and resources Assemblies •design requirements states •facilities • Power-distribution • Buildings Interfaces •define •design configuration Behavior •personnel • Power-generation • Plants • Functional •justify •as-built Usage •equipment • Electric Machinery • Transportation Decomposition of •approve •as-maintained •diagnostics • Electric Light and Heat Systems Product •schedule • Control Systems • 3D Cabling and •feedback Administration Harnesses • Cable Tracks and Planning Execution Shape Mounting Instructions Archiving Conformity to the concept of a system Associated Finite System definition data and configuration control Element Analysis (FEA) Electrotechnical Plant Requirements, requirement analysis, and functional allocation • Plant, e.g., Automobile Geometry Analysis results Functional, functional analysis, and functional behaviour • Unit, e.g., Engine Control Dimensions material properties System Physical architecture and synthesis Tolerances • Subunit, e.g., Ignition System Inspection processes AP233, Systems engineering data AP209:2001, Composite and metal AP212:2001, Electrotechnical design representation structural analysis and related design and installation AP219, Dimensional inspection AP239, Product lifecycle support

Physical layout of Components the circuit card Assemblies assembly Machining Description of features logical connections Assembly among the information functional objects Explicit Packaged parts geometry Physical Tolerances interconnections Configuration management Make or buy Parameters for parts Macro process and functional Edition 3 in process to add gear features planning Digital flow field data Future Editions objects Edition 2 in process Surface data Ground test analysis and results AP224:2001, Mechanical product Analysis and computation Flight test analysis and results AP210:2001, Electronic assembly, definition data for process planning Cross Process Utility AP237, Computational fluid dynamics interconnect, and packaging using machining features

Configuration Mirco process Geometry controlled planning Dimensions exchanges between Automated Material Product Data NC Management (PDM) generation systems Links multiple formats Mechanical parts machining Design •milling AP203:1994, Configuration controlled Analysis •turning Manufacturing •electro 3D designs of mechanical parts and Support discharge machining assemblies Sheet metal AP 214:2001, Core data for automotive bending AP232:2002, Technical data packaging: Pipe bending mechanical design processes Related Standards core information and exchange AP238, Computer numerical controllers

Components Geometry NRF (Network-model and All six pumps are the identical FW LT Pump NRF (Network-model and Assemblies Dimensions MGM (Meshed component in the library. FW LT Pump Results Format) When they are placed in the FW LT Pump (Spare) Material Generic engineering-discipline- Geometric Model) product model additional information is provided about FW HT P ump independent foundation module Meshed geometric model for the specific instance. FW HT P ump Maco analysis purposes FW HT P ump (Spare) process Attribute Value planning Equipment: Pump •machining Type: Vertical Centrifugal •fabrication Casing: Cast Iron Impeller: Bronze Shaft: Stainless SKM (Space Kinematic Mfg: Allweiler Marine SMA (Space Mission 3 Model) Q: 200 m /h Mechanical parts Ps bar 3 bar Aspects) Rigid body kinematics specified on RPM: 1750 Structural steel Aspects of a space mission relevant to MGM meshed geometric model Power: 23 kw T 250 Sheet metal bending ther mal and MAX space environment effects analysis Pipe bending AP240, Process plans for machined STEP TAS (currently formalized under ISO) ISO 13584 (Parts Library Exchange) products April 07 Technological Basis Application Server (J2EE)

Web- J2EE Application Server HTML/HTTP browser Web Container EJB Container Resource Connections

Servlet EIS Rich Session J2EE SOAP/HTTP Client Bean Connector

JSP Message Web Driven URL HTTP Java- Server RMI/IIOP Bean Connection Client Security Mail Session Mail Session SMTP Message Provider Bean C++- Connection Server IIOP Client Naming Service Entity Data Bean Database Source SQL-Net J2EE Transaction Monitor -server Application RMI/IIOP Client Application Client Container Java Virtual Machine

Operating System

April 07 Technological Basis Workflow (BPEL)

„ Programming language for business processes combined with graphically representation „ Extensible for new language elements „ Properties of a BPEL process „ Process is a service and itself can be used from other VariablesVariables holdhold data data us useded in in the the ParParttnenerr Li Linksnks busbusinesinesss p proroccesesss placplaceholdereholderss for for p procroceessss services ccaallerllerss and and ser servvicicee prprovideroviderss „ Process can be synchronous or ! ! ! FaulFaultt HandlHandlersers asynchronous encencloslosee ac activittivitiesies that that a arere Correlation Sets performed in cases of error Correlation Sets performed in cases of error ssuppoupportr tp proroccesesss ins instanctancee identifidentificicationation

„ OASIS standard Receive

JavaSnippet AAcctivittivitiieses ssubtaskubtaskss o of ft hethe Invoke ContrControoll LiLinksnks process Wait define the process' control process Assign define the process' control flflooww JavaSnippet Throw Receive Receive

Assign

Invoke April 07 Implementation Architecture Logical Architecture

„ Tools connected via Adapters to the Integration Layer TOOL TOOL „ Adapter Tool API Tool API „ uses the tool API „ performs data transformation „ Integration Layer maps Adapters to Services Adapter Adapter Domain Service „ Services Domain Service „ hide the details from the user XML „ can be used in workflows XML „ Domain Service XML „ provides methods to access or manipulate data for a domain ENGINEERING DATABASE „ data format is XML „ Engineering Database „ a special "tool" „ contains the SSRM as data model Integration Layer

April 07 Tool Implementation Architecture TOOL API From Model to Implementation

Adapter Integration Layer Code Generation From Informational Model Domain Service of XML I/O procedures „ XSD files „ define the structure of the XML Code Generation streams of Services „ XML I/O functionality „ routines to format XML streams

„ Database structure Code Generation XML of XSD files „ tables to accommodate data „ Database access code „ object relational mapping SSRM

Code Generation of XML I/O From Computational Model procedures „ Services Code Generation „ each domain represented by of database access Engineering services (1..n) Database

Code Generation of database structure

April 07 Demonstration Environment Components

„ Integration Application

„ Service Layer Service Service Service Service Service Service Service A B C D E F . . . „ Connector Layer

Security

Business Logic

Integration Application

Mapping Functionality

Core Functionality

Connector Connector Connector Connector System A System B System C System . . . April 07 Demonstration Environment Scenarios

„ Realization of Scenarios „ Combining (orchestrating) services to workflows (business logic)

Start End

Validate „ Business Logic Add Delete „ Complex functions „ repeatedly carried out

GetData Mapping StoreData „ Workflow Service Service Service „ Consumes services Integration Application „ re-uses existing Mapping components Con- Con- Con- Con- nector nector nector nector „ combines them to tailor-made functions Requirement Requirement Eng System A Eng System B

April 07 ... and finally

„ Outlook „ Plan to report on results at PDE 2008

„ Many thanks to the all co-workers in the project: „ Robert Birn (EADS Astrium) „ Emmanuel Cheguillaume (EADS ST) „ Carsten Zerbst (PROSTEP) „ Mirko Theiss (PROSTEP)

„ Thank you!

April 07