Space System Reference Model – - Prostep AG

Space System Reference Model – 

Integration and Collaboration Platform 

for the Engineering Domains in the Space Industry 

Harald Eisenmann (Astrium Satellites, Germany), 

Matthias Grau (PROSTEP AG, Germany) 

Niklas Lindmann (ESA/ESTEC, Netherlands) 

Hans-Peter de Koning (ESA/ESTEC, Netherlands)

This document is the pr operty of Astrium. It shall not be communicated to third parties without prior written agreement. Its content shall not be disclosed. 

19/12/2006 p2 

Presentation Overview 

Background on SSRM project 

Data Model and MDA 

SSRM Architecture 

Conclusion and next steps

SSRM Project Background


19/12/2006 p4 

Engineering Database – Current Status 

System Engineering data is currently scattered 

between different tools with limited capabilities of 

Data exchange 

Version control 

Application of consistency checks 

Within the scope of a projects “pragmatic” solutions 

are pursued – often by using MS-Office products 

Configuration control is supported by PDM tools 

Comprehensive data management not achieved 

that some exceptions for particular tools, typically 

limited to document management


19/12/2006 p5 

Prime Industry – Simplified Project Tool Architecture 

Project Infrastructure 

Matlab Matlab / / 

Simulink Simulink 

Harness 

SDB Harness 

SDB 

Catia 

Tool 

Catia 

Tool 

System 

Requirements 

Nastran Nastran 

/ / Patran Patran 

Domain Domain Tools Tools 

“System “System Engineering Engineering Tools” Tools” 

Requirements Requirements Management Management Tool Tool 

Verification 

Method 

ESATAN ESATAN 

-RAD -RAD 

Thermica Thermica 

CCS CCS 

…… 

Electrical Electrical I/F I/F 

Testing Testing 

Word Word PowerPoint PowerPoint Excel Excel Visio Visio Access Access 

Next Lower 

Next Lower 

Level 

Level 

Next Reqts 

Reqts 

Lower 

Level Reqts 

…… 

PDM PDM 

Systems 

Systems


19/12/2006 p6 

Derived needs 

Overall framework required allowing: 

Integration of the individual tools 

Data sharing and distribution 

Application sharing 

“Centralized” database which provides: 

Common source of information 

Consistency and completeness checks 

Configuration and version control 

Semantic Definition of Data Items 

Development framework which eases development 

and maintenance


19/12/2006 p7 

SSRM Objective is to 

Prototype an architecture on the SOA principles 

providing 

Dedicated tool integration adaptors 

Data management ‘procedures’ 

DB adapter to a RDBMS 

Validate the approach on how ETM-10-23A model 

is defined with respect to 

Evaluation of data modeling techniques 

Comparison to existing data models (i.e. STEP AP’s) 

Adequacy of data model to facilitate MDA development process 

Develop and demonstrate a prototype with an 

industrial scenario


19/12/2006 p8 

Industrial Consortium 

EADS Astrium Satellites, Germany (Prime) 

Overall Study Management 

Data Modelling / datastructure mapping 

Development of end-user prototype tools 

Implementation / maintainance model transformation 

PROSTEP, Germany 

Assessment on data modeling approach (incl. STEP harvesting) 

SSRM Architecture Definition 

Demonstration scenario development and integration 

Setup demonstration / test execution 

EADS Astrium Space Transportation, France 

Identification and description of demonstration scenario 

Test data preparation


19/12/2006 p9 

Conceptual Architecture 

Adapter 

TOOL A TOOL B 

(Virtual) Data Exchange 

Tool API Adapter 

Mapping 

SSR API) 

Data Structure 

A 

platform flexibility 

Format 

Description A 

(e.g. XSD) 

specifies format 

Data A 

(e.g. as XML) 

generated 

Draft Meta- 

Model 

(ECSS 10) 

datamodel approach 

SSRM 

generated 

Database 

Definition 

defines 

SSR DB 

generated 

Data Structure 

B 

Format 

Description B 

specifies format 

Data B 

Virtual Data Exchange 

Modelling 

Neutral exchange and 

integration layer

Data Model


19/12/2006 p11 

Conceptual Data Model 

Objective 

Provide formal semantic specification on data items 

required to describe S/C design, integration and operation 

data 

Provide a semantic definition of the concepts in use – focus 

is on ‘WHAT’ not on HOW 

Enable subsequent (semi-) automated of development 

process 

Data model is considered being the main driver for 

Tool development / customization 

Overall data and configuration management 

Facilitating transition from document to data orientation 

Improved process description covering process, data and 

view 

Conceptual data modelling vs. knowledge modelling


19/12/2006 p12 

«ConceptPackage» 

ArchitecturalDesign 

«ConceptData» 

ElementCategory 


ElementDefinition 


Requirements 


ArchitecturalDesignElement 


ElementUsage 


Requirement req 

-definition 

: xText 

-type 

: RequirementType 

1..* 


ElementOccurrence 

sysElem 


InterfaceOccurrence 

«ConceptLink» 

ReqSatisfyTrace 


InterfaceCategory 


InterfaceDefinition 


InterfaceUsage 


InterfaceEndUsage 

«ConceptLink» 

ReqArchSatisfy 


InterfaceEndOccurrence 

«Enum» 

RequirementType 

-Functional 

-Mission 

-Interface 

-Environmental 

-Physical 

-Operational 

-HumanFactor 

Data Model Excerpt: Tracing Requirements 

1..* 

-LogisticsSupport 

-ProductAssurance 

-Configuration 

-Design 

-Verification


19/12/2006 p13 




TypeDefinition 



Data Model Excerpt: InterfaceCategory Product Structure 

ElementCategory 


ImplicitProductStructure 

containedInterfaces 


InterfaceUsage 0..* 

0..* 

containedInterfaces 

0..1 

category 


InterfaceDefinition 

type 


InterfaceEndUsage 

containedElements 


ElementUsage 

interfaceEnds 

0..* 

0..* 

interfaceEndTypes 

type 

type 

0..* 

0..1 

type 


ElementDefinition 


PhysicalDesign 

type 


ElementRealisation


19/12/2006 p14 

Data Model Excerpt: E70-41 (PUS) 


ServiceDefinition 


Service_02_1 

-n 

: UnsignedInteger 

-address 

: HardwareAddress[1..*] 

«DataType» 

RegisterDataType 


Service_2 


PUSService 


Service_02_2 

-registerAddress 

: RegisterAddress 

-n 

: UnsignedInteger 

-registerData 

«Enum» 

RegisterAddress 

«Enum» 

HardwareAddress 

-TBD 


Service_02_3 

-n 

«DataType» 

UnsignedInteger 

1..* 


_Service_2_3_Parameter 

parameters -duration 

-outputLineID


19/12/2006 p15 




TypeDefinition 


Data Model: E-50-14 InterfaceDefinition (Discrete Electrical I/F) 


ElectricalInterfaceDefinitions 


DiscreteElectricalInterfaces 


PowerSupplyInterface 


HPCIF 


LPCIF 


BDMIF 


CmdInterface 


FunctionalElectricalInterface 


BiLevelDiscreteIF 


BSMIF 


AnalogueInterface 


TSMIF 


ASMIF 


OSD16IF 


SerialDigitalInterface 


ISD16IF 


BSD16IF


19/12/2006 p16 

Data Model Presentation (1/2)


19/12/2006 p17 

Data Model Presentation (2/2)


19/12/2006 p18 

Applying the MDA 

WP2100 (TN1: Definition of the data sharing scenario) 

WP3200 (TN2: Engineering database reference data model) 

Business and 

requirements 

models 

Analysis 

and design 

models 

Platform Specific 

Model (PSM) 

Computation Independent 

Model (CIM) 

Platform Independent 

Model (PIM) 

Platform Specific 

Model (PSM) 

Platform Platform 

Deployment models 

PSMs in SSRM: Hibernate O/R Mapping and XML scheme generated from SSRM UML


19/12/2006 p19 

MDA is in SSRM applied for 

Data Transformation for the S/W development 

XML-XSD with a dedicated pattern applied 

XML API (Java) for the generated XML schema 

Java POJO (Plain Old Java Classes) as data container 

Mappings XML 2 POJO 

Hibernate schema 

Eclipse EMF for Testing tools 

Data Transformation for documentation 

(X)HTML with SVG for diagrams 

OfficeML 

Wiki

SSRM Architecture


System Engineering 

Control GUI 

19/12/2006 p21 

Elements of the Architecture 

Modular Architecture 

State-of-the art software development paradigms 

Service Oriented Architecture (SOA) 

Model Driven Architecture (MDA) 

Industry Standards 

J2EE 

UML, W3C XML, SOAP and Web Services 

ECSS ETM-10-23 

OMG PLM Services


19/12/2006 p22 

Elements of the Integration Platform 

SSRM Connectors 

Tools, SSRDB 

Webservices 

Basic, Control, Engineering 

Business Logic


19/12/2006 p23 


SSRM Connectors 

Tool Connector (File) 

Read/Write files in 

different formats 

Connector type / File 

format identified by 

MIME type / System 

property 

SSRDB Connector 

Read/Write data in the SSRDB 

Actually implemented actions: 

Read item / item structure 

Write item / item structure 

Create version of item / structure


19/12/2006 p24 


Webservices 

Basic Webservices 

Services to provide basic functionality 

Architecture based on OMG PLM 

Services specification 

Control Webservices 

Services to control data exchange 

between connectors 

Use Basic Webservices to handle 

connections 

Typically a workflow of other services 

Engineering Webservices 

Services to provide (higher-level) 

engineering functionality


19/12/2006 p25 


Implemented Webservices 

Basic Webservices 

Session/Connection handling 

Stub to call implicit to explicit product structure transformation logic 

Control Webservices 

Import/Export Product Tree 

Import IPS 

Create/Update/Export EPS 

Import/Export TMTC Data 

Import/Export MCI Data 

Create Baseline 

Engineering Webservices 

Create EPS out of IPS


19/12/2006 p26 


Business Logic 

Application tier of the platform 

Controlled from the "presentation" (web server) tier 

Represented by functional algorithms to handle information 

exchange between the platform elements 

accesses the data tier (SSR DB) through the SSRDB connector


19/12/2006 p27 

SSR Database 

Database structure generated by Hibernate 

based on the hibernate mappings derived from the data model 

All database systems supported by Hibernate can 

be used 

e.g. MySQL, Oracle, MS SQL Server, Firebird, … 

used for the demonstrator: H2 (in memory DB, easy to use) 

Dataflow between the database and SSRDB 

Connector 

JDBC Connection 

Details hidden by the JDBC driver


19/12/2006 p28 

SSRM Tools 

External Interface of Connectors is XML 

ATV Data is converted to Excel XML files 

Tool integration is supported by the SSRM File Connector 

File Connector can read/write different data formats 

File Connector uses XSLT mapping


19/12/2006 p29 

System Engineering Control GUI 

Eclipse GUI 

Uses SSRM Control Web- 

Services 

Interface automatically generated 

with AXIS based on WSDL 

definitions 

Data Flow to 

System Engineering Control GUI 

Interface described by WSDL 

SOAP over HTTP as protocol


19/12/2006 p30 

Layering Architecture 

(Standard) 

WebServices 

Native Data 

+ Data 

Mapping 

SSRM WebServices (WSDL, …) 

SSRM Platform Base (J2EE) 

SSRM Connector Layer (XML, …) 

PDM VPM ERP 

Project specific 

workflows 

Connectivity 

"Out of the Box" 

existing system 

topography


Step 1 – Read file with product tree 

19/12/2006 p31 

Workflow Example 1 (Import PT Process) 

Call SSRM Webservice 

“Read File” 

PT Data in SSRM Format 

. . . 

Open Connectrion 

To File Connector 

Read Whole File 

Response Data Format is 

SSRM 

Calls to SSRM internal Webservices 

File Connector


Step 2 – Import product tree to SSRDB 

19/12/2006 p32 

Workflow Example 2 (Import PT Process) 

Call SSRM Webservice 

“Import to SSRDB” 

Success Of Import 

. . . 

Open Connectrion 

To SSRDB Connector 

Write Data 

Into SSRDB 

Calls to SSRM internal Webservices 

SSRDB Connector

Conclusion


19/12/2006 p34 

Conclusion 

Assessment of ETM-10-23 data model fully supports 

Semantic data definition 

MDA supported S/W development 

However further refinement of the meta model behind required 

Assessment of re-using STEP models showed 

Current ETM-10-23 as specification model is mandatory – as 

required semantic is not given in considered AP’s 

However selected modeling patterns / concepts may be adopted 

Applied SOA architecture provides a modular 

framework 

SSRM is currently finalizing the integration 

MDA offers many benefits, however …


19/12/2006 p35 

Lessons learnt on MDA 

PRO 

Clear separation between user concepts and implementation 

concepts (and patterns) 

(Semi-) automation of S/W development, shortening 

development life-cycle, decreasing costs and easing 

maintenance 

CONS 

Transformation languages not consolidated – various 

languages 

To extend exploitation of MDA a COMMON transformation 

schema needs to be applied 

Customer – supplier roles need to be iterated


(Domain-) Analysis 

(Domain-) Analysis 

19/12/2006 p36 

Beyond SSRM - VSD 

DRC 

Virtual S/C 

Operation 

Virt.(M)AIT 

Operation 

Virtual Spacecraft Engineering Environment 

Virtual Spacecraft Engineering Environment 

S/C Model-based System Engineering 

S/C Model-based System Engineering 

VSEE Services 

VSEE Services 

SSRDB 

Virtual S/C 

Virtual S/C 

Design 

Browser 

CCS 

(Domain-) Verification 

(Domain-) Verification

Space System Reference Model – - Prostep AG

Create successful ePaper yourself

Delete template?

Save as template?