Space System Engineering Database

Integration and Collaboration Platformfor the Engineering Domainsin the Space Industry

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

April 07

Outline

Requirements arising for engineering data management in the space industryECSS ETM-10-23Overview SSRM Project

IntroductionPlatform ArchitectureMDA, SOA, BPELDemo Scenarios

Conclusions ans Outlook

April 07

Engineering DatabaseCurrent situation (1)

In a spacecraft project, many engineering databases do exist, ...

well designed for their domainonly fragmentsmade for a small section of the space system life cycleown databaseno data exchange (time-consuming, error-prone)

... otherwise standard office products are usedcovering a significant part of the space craft design and verification information

April 07

Engineering DatabaseCurrent situation (2)

Consistent data management is hard to achieveinconsistencies between the databasesmanual work to transfer data between the databasesdifficult to get a consistent data sets needed for simulation tasks from data of more than one databaseno data life-cycle defined

• change process• Identification of incomplete/valid data

validation of data is difficult, often manuallyredundancy

April 07

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

Option 1: Document Management SystemsDMS "think" document based …integration required on user data level rather than on administrative level only

Option 2: PDM SystemsPDM Systems can support workflows …

process level integrationwrt. data management they function like DMS

Option 3: DBMSDBMS alone would not resolve the data integration issue – semantic transformation needed between to-be-connected tool and DMBSDBMS 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 informationdatabase 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 architecturecentrally 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-23Rationale 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 information

Reduction of overall project investment in data base systems

Ensure compatibility between the different phases and activities in a project: Engineering, Testing and Operations

Allow project data exchange across company boundaries

Support implementation of modern system engineering approaches including integrated project teams, distributed collaborative engineering, use of product data management systems etc.

Project DB

Engineering DB

System Engineering DB

EngineeringDiscipline

Related DBEngineeringDiscipline

Related DBEngineeringDiscipline

Related DB

ManagementDB

ProductAssurance DB

April 07

ECSS ETM-10-23Top-level Data Model

System Engineering Data Requirements, Functional, Architectural and Physical DesignAIT Data (procedures, logistics, …)Verification Data (description, procedures, reports, …)Operations Data (TM/TC Data, Planning, Operational Procedures, Bus Data, …)

System Engineering Data

Physical Architecture

Requirement

FunctionalDesign

ArchitecturalDesign

Verification

FunctionalAllocation

System Allocation Physical Design

OperationalDesign

Assembly &Integration

Verification Matrix

Accomondation

SystemElement

Engineering Discipline Related Data

Kept as references its primary data store

Formal Definition of aparticular type of anequipment, device, … :

Example data items are:- Technical Specification- Design Document- ICD- Bill of Material- Test Plan- Product Number (Catalog)- Geometric Shape- Default Calibration

Identifcation and Position ofan usage of an item of typeElementDefinition:

Example data items are:- unique identifier- position, placement- integration constraints- position dependent calibration curve- Assembly structure- Integration tree definition

Realistation of an item oftype ElementDefinition

Example data items are:- serial number- As-built-status- test report- certificate- delivery report/sheet

Formal Definition ofcommon characteristics(attributes and properties):

ElementCategory

ElementDefinition

ElementOccurrence

ElementRealisation

April 07

Space System Reference Model (SSRM)

Consortium consisting of

EADS AstriumEADS STPROSTEP

awarded contract January 2007

April 07

SSRM – Study Focus

Assessment

Technology

Operational Implementation &DeploymentModelling

Methodology

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 datamodel for a centralengineering database

Validation of thedeployment and usagein an operational context

April 07

SSRM – Timeline

17.01 Kick-Off

17.04 Progress Meeting 1

29.06 PRR

14.11 Progress Meeting 2

29.02 Final Presentati

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 '081st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd QuaTask Name

WP1000 Project Management

WP 2000 Scenario Definition

WP 2100 ScenarioIdentificationWP 2200 ScenarioDescription

WP 3000 Data StructureMapping

WP 3100 Assessment ofDM ApproachWP 3200 Data structureMapping

WP 4000 Modelling andTranslator Generation

WP 4100 Implement CodeGeneratorWP 4200 DemonstrationAppliation Integration

WP 5000 Demonstration andEvaluation

WP 5100 Set-Up/Test

WP 5200 Evaluation

Kick-Off

Progress Meeting 1

PRR

Progress Meeting 2

Final Presentation

April 07

Use Cases for an Engineering Database (examples)

Submit dataPrepare data for reviewExtract dataConsistency checkOperate dataVersioningCreate baseline

Actors (Roles)AgencyPrime contractor / SubcontractorEngineering disciplinesSystem Engineering Integration & Control

Engineering Database System

Engineering Disciplines

Submit dataExtract data

Operate data

Versioning

Consitency check

Agency

«extends»

Create baseline

«extends»Prime contractor

«extends» «extends»

«extends»

Subcontractor

«extends»

SE Integration & Control

Extract data forreview«extends»

April 07

Overview of the Technical Solution

Adapter

TOOL A TOOL B

Data StructureB

Data StructureA

(Virtual) Data Exchange

Draft Meta-Model

(ECSS 10)

SSRM

datamodel approach

Tool API Adapter

Data A(e.g. as XML) Data B

generatedgenerated

FormatDescription A

(e.g. XSD)

specifies format

FormatDescription B

specifies format

Mapping

SSR API)

SSR DB

DatabaseDefinition

generated

defines

platform flexibility

Virtual Data Exchange

Modelling

Neutral exchange andintegration layer

April 07

Architectural BasisService Oriented Architecture (SOA)

Logic is encapsulated by services

each servicehas apublicinterface with operations and parameters

Typically, every SOA component (like a BPEL workflow) is a service and can be used by other components

processstep

Service

Service

Service

sub-process

process

Encapsulate logic with services

April 07

Architectural BasisModel Driven Architecture (MDA)

Computation IndependentModel (CIM)

Platform IndependentModel (PIM)

Platform Specific Model (PSM)

Platform Specific Model (PSM)

Implementation Implementation

Computation IndependentModel (CIM)

Platform IndependentModel (PIM)

Platform Specific Model (PSM)

Platform Specific Model (PSM)

Implementation Implementation

The Model Driven Architecture approach, defined by OMG

enables the formal specification of a discipline-independent and neutraldata modelsupports the ability to apply state-of-the-art development methods and technologiesenables the transformation of a data model into several platform specific implementations

Everything is a Model

April 07

Basis for the Data ModelAnalysis

AP237, Computational fluid dynamics

Digital flow field dataSurface dataAnalysis and computation

Electrotechnical Plant• Plant, e.g., Automobile• Unit, e.g., Engine Control System• Subunit, e.g., Ignition System

Electrotechnical Systems• Buildings • Plants• Transportation Systems

Equipment Coverage• Power-transmission• Power-distribution• Power-generation• Electric Machinery• Electric Light and Heat• Control Systems

Data Supporting• Terminals and Interfaces• Functional Decomposition of Product• 3D Cabling and Harnesses• Cable Tracks and Mounting Instructions

AP212:2001, Electrotechnical design and installation

Requirements/Concept

Physical layout of the circuit card assemblyDescription of logical connections among the functional objectsPackaged partsPhysical interconnectionsConfiguration managementParameters for parts and functional objects

AP210:2001, Electronic assembly, interconnect, and packaging

Work activities and resources•define•justify•approve•schedule•feedback

AP239, Product lifecycle supportAP209:2001, Composite and metal

structural analysis and related design

ShapeAssociated Finite Element Analysis (FEA)Analysis resultsmaterial properties

AP233, Systems engineering data representation

Lifecycle Support

FW LT PumpFW LT PumpFW LT Pump (Spare)FW HT PumpFW HT PumpFW HT Pump (Spare)

All six pumps are the identical component in the library. When they are placed in the product model additional information is provided about the specific instance.

Attribute Value

Equipment: PumpType: Vertical CentrifugalCasing: Cast IronImpeller: BronzeShaft: StainlessMfg: Allweiler MarineQ: 200 m3/hPs bar 3 barRPM: 1750Power: 23 kwTMAX 250

ISO 13584 (Parts Library Exchange)

AP219, Dimensional inspection

ComponentsAssemblies

Manufacturing

Conformity to the concept of a systemSystem definition data and configuration controlRequirements, requirement analysis, and functional allocationFunctional, functional analysis, and functional behaviourPhysical architecture and synthesis

Detailed Design/BoM

AP232:2002, Technical data packaging: core information and exchange

AP232:2002, Technical data packaging: core information and exchange

Configuration controlled exchanges between Product Data Management (PDM) systemsLinks multiple formats

AP224:2001, Mechanical product definition data for process planning

using machining features

AP238, Computer numerical controllers

Machining featuresAssembly informationExplicit geometryTolerances

GeometryDimensionsMaterial

AP240, Process plans for machined products

Related Standards

AP203:1994, Configuration controlled 3D designs of mechanical parts and

assembliesAP 214:2001, Core data for automotive

mechanical design processes

Cross Process Utility

Future EditionsGround test analysis and resultsFlight test analysis and results

Edition 2 in process

DesignAnalysisManufacturingSupport

AdministrationPlanningExecutionArchiving

GeometryDimensionsTolerancesInspection processes

ComponentsAssemblies

Make or buyMacro process planningEdition 3 in process to add gear features

Mircoprocess planningAutomated NC generation

Mechanical parts machining•milling•turning•electro discharge machiningSheet metal bendingPipe bending

GeometryDimensionsMaterial

Mechanical partsStructural steelSheet metal bendingPipe bending

Macoprocess planning•machining•fabrication

ComponentsAssemblies

Configuration•design requirements•design configuration•as-built•as-maintained

Operating statesBehaviorUsage

Support•facilities•personnel•equipment•diagnostics

NRF (Network-model and Results Format)Generic engineering-discip line-independent foundation module

MGM (Meshed Geometric Model)Meshed geometric model for analysis purposes

SKM (Space KinematicModel)

Rigid body kinematics specified on MGM meshed geometric model

SMA (Space Mission Aspects)

Aspects of a space mission relevant to thermal and

space environment effects analysis

STEP TAS (currently formalized under ISO)

Analysis

AP237, Computational fluid dynamics

Digital flow field dataSurface dataAnalysis and computation

Electrotechnical Plant• Plant, e.g., Automobile• Unit, e.g., Engine Control System• Subunit, e.g., Ignition System

Electrotechnical Systems• Buildings • Plants• Transportation Systems

Equipment Coverage• Power-transmission• Power-distribution• Power-generation• Electric Machinery• Electric Light and Heat• Control Systems

Data Supporting• Terminals and Interfaces• Functional Decomposition of Product• 3D Cabling and Harnesses• Cable Tracks and Mounting Instructions

AP212:2001, Electrotechnical design and installation

Requirements/Concept

Physical layout of the circuit card assemblyDescription of logical connections among the functional objectsPackaged partsPhysical interconnectionsConfiguration managementParameters for parts and functional objects

AP210:2001, Electronic assembly, interconnect, and packaging

Work activities and resources•define•justify•approve•schedule•feedback

AP239, Product lifecycle supportAP209:2001, Composite and metal

structural analysis and related design

ShapeAssociated Finite Element Analysis (FEA)Analysis resultsmaterial properties

AP233, Systems engineering data representation

Lifecycle Support

FW LT PumpFW LT PumpFW LT Pump (Spare)FW HT PumpFW HT PumpFW HT Pump (Spare)

FW LT PumpFW LT PumpFW LT Pump (Spare)FW HT PumpFW HT PumpFW HT Pump (Spare)

All six pumps are the identical component in the library. When they are placed in the product model additional information is provided about the specific instance.

Attribute Value

Equipment: PumpType: Vertical CentrifugalCasing: Cast IronImpeller: BronzeShaft: StainlessMfg: Allweiler MarineQ: 200 m3/hPs bar 3 barRPM: 1750Power: 23 kwTMAX 250

ISO 13584 (Parts Library Exchange)

AP219, Dimensional inspection

ComponentsAssemblies

Manufacturing

Conformity to the concept of a systemSystem definition data and configuration controlRequirements, requirement analysis, and functional allocationFunctional, functional analysis, and functional behaviourPhysical architecture and synthesis

Detailed Design/BoM

AP232:2002, Technical data packaging: core information and exchange

AP232:2002, Technical data packaging: core information and exchange

Configuration controlled exchanges between Product Data Management (PDM) systemsLinks multiple formats

AP224:2001, Mechanical product definition data for process planning

using machining features

AP238, Computer numerical controllers

Machining featuresAssembly informationExplicit geometryTolerances

GeometryDimensionsMaterial

AP240, Process plans for machined products

Related Standards

AP203:1994, Configuration controlled 3D designs of mechanical parts and

assembliesAP 214:2001, Core data for automotive

mechanical design processes

Cross Process Utility

Future EditionsGround test analysis and resultsFlight test analysis and results

Edition 2 in process

DesignAnalysisManufacturingSupport

AdministrationPlanningExecutionArchiving

GeometryDimensionsTolerancesInspection processes

ComponentsAssemblies

Make or buyMacro process planningEdition 3 in process to add gear features

Mircoprocess planningAutomated NC generation

Mechanical parts machining•milling•turning•electro discharge machiningSheet metal bendingPipe bending

GeometryDimensionsMaterial

Mechanical partsStructural steelSheet metal bendingPipe bending

Macoprocess planning•machining•fabrication

ComponentsAssemblies

Configuration•design requirements•design configuration•as-built•as-maintained

Operating statesBehaviorUsage

Support•facilities•personnel•equipment•diagnostics

NRF (Network-model and Results Format)Generic engineering-discip line-independent foundation module

MGM (Meshed Geometric Model)Meshed geometric model for analysis purposes

SKM (Space KinematicModel)

Rigid body kinematics specified on MGM meshed geometric model

SMA (Space Mission Aspects)

Aspects of a space mission relevant to thermal and

space environment effects analysis

NRF (Network-model and Results Format)Generic engineering-discip line-independent foundation module

MGM (Meshed Geometric Model)Meshed geometric model for analysis purposes

SKM (Space KinematicModel)

Rigid body kinematics specified on MGM meshed geometric model

SMA (Space Mission Aspects)

Aspects of a space mission relevant to thermal and

space environment effects analysis

STEP TAS (currently formalized under ISO)

April 07

Technological BasisApplication Server (J2EE)

RichClient SOAP/HTTP

Web-browser HTML/HTTP

C++-Client IIOP

Java-Client RMI/IIOP

Application ClientContainer

J2EEApplication

ClientRMI/IIOP

J2EE Application ServerEJB ContainerWeb Container

Transaction Monitor

Security

Naming Service

ResourceConnections

J2EEConnector

DataSource

MailSession

Connection

URLConnection

SessionBean

SessionBean

EntityBean

MessageDrivenBean

Message Provider

Servlet

JSP

HTTP

SMTP

SQL-Net

EIS

WebServer

MailServer

Database-server

Java Virtual Machine

Operating System

April 07

Technological BasisWorkflow (BPEL)

! ! !

JavaSnippet

Wait

JavaSnippet

Receive

Assign

Assign

Receive

Invoke

Receive

Invoke

Throw

Partner Linksplaceholders for process

callers and service providers

Partner Linksplaceholders for process

callers and service providers

Variableshold data used in the

business process

Variableshold data used in the

business process

Fault Handlersenclose activities that are

performed in cases of error

Fault Handlersenclose activities that are

performed in cases of error Correlation Setssupport process instance

identification

Correlation Setssupport process instance

identification

Activitiessubtasks of the

process

Activitiessubtasks of the

process Control Links

define the process' control flow

Control Linksdefine the process' control

flow

Programming language for business processes combined with graphically representationExtensible for new language elementsProperties of a BPEL process

Process is a serviceand itself can beused from otherservicesProcess can besynchronous orasynchronous

OASIS standard

April 07

Implementation ArchitectureLogical Architecture

Tools connected via Adapters to the Integration LayerAdapter

uses the tool APIperforms data transformation

Integration Layer maps Adapters to ServicesServices

hide the details from the usercan be used in workflows

Domain Serviceprovides methods to access or manipulate data for a domaindata format is XML

Engineering Databasea special "tool"contains the SSRM as data model

Integration Layer

TOOLTool API

XML

ENGINEERINGDATABASE

TOOLTool API

XML

DomainService

DomainService

Adapter Adapter

XML

April 07

Implementation ArchitectureFrom Model to Implementation

EngineeringDatabase

ToolTOOL API

XML

Integration LayerDomain Service

Adapter

SSRM

Code Generationof XML I/Oprocedures

Code Generationof XSD files

Code Generationof XML I/Oprocedures

Code Generationof database

structure

Code Generationof Services

Code Generationof database

access

From Informational ModelXSD files

define the structure of the XML streams

XML I/O functionalityroutines to format XML streams

Database structuretables to accommodate data

Database access codeobject relational mapping

From Computational ModelServices

each domain represented by services (1..n)

April 07

Demonstration EnvironmentComponents

Integration Application

Service Layer

Connector Layer

ConnectorSystem A

ConnectorSystem B

ConnectorSystem C

ConnectorSystem . . .

Integration Application

ServiceA

Service. . .

ServiceB

ServiceC

ServiceD

ServiceE

ServiceF

Security

Core Functionality

Business Logic

Mapping Functionality

April 07

Demonstration EnvironmentScenarios

Start

StoreDataService

MappingService

GetDataService

End

ValidateAdd

Delete

Integration ApplicationMapping

RequirementEng System A

Con-nector

RequirementEng System B

Con-nector

Con-nector

Con-nector

Realization of ScenariosCombining (orchestrating) services to workflows (business logic)

Business LogicComplex functionsrepeatedly carried out

WorkflowConsumes servicesre-uses existingcomponentscombines them totailor-madefunctions

April 07

... and finally

OutlookPlan 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!