Space System Reference Model Integration and Collaboration Platform for the Engineering Domains in t

1
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)

2
Presentation Overview

• Background on SSRM project
• Data Model and MDA
• SSRM Architecture
• Conclusion and next steps

3
SSRM Project Background
4
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

5
Prime Industry Simplified Project Tool
Architecture
Project Infrastructure
Domain Tools
Nastran / Patran
ESATAN -RAD
Thermica
Matlab / Simulink

Harness Tool
SDB
Catia

CCS
Electrical I/F Testing
System Engineering Tools
Word
PowerPoint
Excel
Visio
Access
PDM Systems
6
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

7
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
  APs)
• Adequacy of data model to facilitate MDA
  development process
• Develop and demonstrate a prototype with an
  industrial scenario

8
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

9
Conceptual Architecture
10
Data Model
11
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
  vs. ontology's,

12
Data Model Excerpt Tracing Requirements
13
Data Model Excerpt Product Structure
14
Data Model Excerpt E70-41 (PUS)
15
Data Model E-50-14 (Discrete Electrical I/F)
16
Data Model Presentation (1/2)
17
Data Model Presentation (2/2)
18
Applying the MDA
Business and requirements models
Analysis and design models
WP2100 (TN1 Definition of the data sharing
scenario)
Deployment models
WP3200 (TN2 Engineering database reference data
model)
PSMs in SSRM Hibernate O/R Mapping and XML
scheme generated from SSRM UML
19
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

20
SSRM Architecture
21
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

22
Elements of the Integration Platform

• SSRM Connectors
• Tools, SSRDB
• Webservices
• Basic, Control, Engineering

• Business Logic

23
Elements of the Integration PlatformSSRM
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

24
Elements of the Integration PlatformWebservices

• 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

25
Elements of the Integration PlatformImplemented
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

26
Elements of the Integration PlatformBusiness
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

27
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

28
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

29
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

30
Layering Architecture
(Standard) WebServices
Native Data Data Mapping
31
Workflow Example 1 (Import PT Process)
32
Workflow Example 2 (Import PT Process)
33
Conclusion
34
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 APs
• 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

35
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

36
Beyond SSRM - VSD
Virtual Spacecraft Engineering Environment
DRC
S/C Model-based System Engineering
VSEE Services
SSRDB
Design Browser
Virtual S/C Operation
(Domain-) Verification
(Domain-) Analysis
Virtual S/C
CCS
Virt.(M)AIT Operation