ESA Design Resource Centre

1
ESA Design Resource Centre

• A Model Based Engineering Database
• Data Exchange Project
• Don de Wilde ESA/ESTEC
• Harald Eisenmann EADS Astrium
• Michael Scheuble EADS Astrium

2
Overview

• Systems Engineering
• Process Challenges
• ESA Design Resource Centre
• Project Framework
• Objectives of the Project
• Processes Use Cases
• Mission System Conceptual Data Model
• S/C Equipment conceptual data model
• CMM- Data the ESA DRC Architecture
• External Interfaces of the ESA DRC
• Conclusion
• Outlook

3
Systems Engineering
Mission Design
Validation
Phase E
Feasibility
Verification
Phase A
Integration
SystemDesign
Phase B
Assembly
Phase D
DetailedDesign
Phase C
Development
4
Todays Challenges for Systems Engineering

• Shrinking Budgets
• Reduced development time
• Increasing complexity
• Complexity shift towards operations software
• Increasing distributed collaboration
• Systems Engineering helps to meet the challenges
  with
• improved processes (e.g. concurrent engineering)
• an integrated SE infrastructure supporting a
  seamless transition of results from project phase
  to project phase under consideration of
• tools (commercial and in-house developed)
• engineering databases
• data exchange standards for the technical and
  project management data
• ? Engineering the System Engineering
  Infrastructure is precondition to meet the
  challenges

5
ESA DRC Project Framework

• ESA Design Resource Centre is a Technology
  Research Project (TRP) of ESA/ESTEC
• The objective is to define, implement and install
  a System Engineering database for mission,
  system, sub-system equipment data of past
  projects or to store data provided by equipment
  suppliers
• Duration of the project is 18 month
• EADS Astrium is prime contractor of the study
  supported by two sub-contractors for
• XML/WSDL data exchange
• Portal document management system interface
• Due to the large need to have a web-based
  database covering the equipments used in past
  projects, Astrium supports this TRP contract with
  internal money and generates in parallel a copy
  of the database in-house called Astrobus
  Equipment Database

6
ESA Design Resource CentreObjectives

• The ESA Design Resource Centre is ought to be an
  up to date and reliable source for S/C mission,
  system, sub-system and equipment data
• It shall support System Engineering tasks
  throughout the design phase of missions or S/C
• It will provide information categories of
  equipments such as
• budget data (kg, W, dimensions, etc.)
• management data (cost, schedule, etc.)
• in flight verification data (performance, etc.)
• ICD respectively simulation models
• Web-based technology

7
Phase A V-Model for CDF or SDO the relation to
ESA DRC
ESA DRC
Requirements Analysis
Decomposition
Design Verification
Model Based Verification
through Model Execution
Mission, P/L Orbit Analysis
Model Based Development
Design Iterations
Operational Concept
Physical Architecture
Functional Architecture
Decomp-osition
Decomposition
8
Use Cases of the ESA DRC Astrobus Equipmend
Database for CDF SDO

• As support to CE process
• Mission design
• S/C design
• Models for Simulations
• Either at ESTEC or at Industry
• As support to the detailed design (Phase B)
• Detailed equipment data
• Simulation models for OBC
• Simulation models for OB-SW (if applicable)
• Lessons learned

CDF Concurrent Design Facility _at_ ESTEC (Mission
Payload designs) SDO (5) Satellite Design
Offices _at_ Astrium (Platform designs)
9
Mission System conceptual data model
Satellite 1 (e.g. generic Earth Ops) Satellite 2
(e.g. specific Telecom) Satellite 3 Mission 1
(e.g. 3 different satellites, METOP 1 2 3)
Scenarios
System
Mission Data
Users
Generic Standard Sub-systems Applied
Sub-systems Possible combinations of
equipment Availability Etc

• Functional data
• Mechanical
• Electrical

Sub-systems
Simulations
Performance data Availability Etc
Covered in detail in the Equipment Data Model
Equipment
General View
Source ESA/ESTEC, Don de Wilde
10
S/C Equipment Conceptual Data Model

• Data Model Logic
• DRC class represents main page
• Discipline class represents all disciplines
  within the DRC
• Equipment Category represents all kinds of
  equipment stored within the DRC
• Equipment Type represents the specific equipment
• Equipment represents all the data of the specific
  equipment
• 5 General Classes
• Budget Data
• Interface Data
• Special Characteritics Data
• Commercial Data
• Change Log Data
• Comment
• Equipment specific attributes attached directly
  to different equipment types (e.g. Star Sensor,
  Reaction Wheel a.s.f.)

11
Maturity Level Definition for Data (not documents)
Astrobus Equipment DB
Typical current status
12
Database Integration Layers
MS Office Solution
Client / Server
J2EE
XML / STEP
Enterprise Integration
Application
Application
Application
Collaboration Layer
Application
Data Exchange Layer (neutral)
Application
Data Access Layer
Data Storage Layer
Application
13
DRC Architecture

• Presentation Layer
• handles lay outing, formatting and displaying of
  data to the user
• Data Access Layer
• contains the Web Service Module, Proxy Tier
  Data Tier
• Data Storage Layer
• contains the Database, link to the document
  management system

Analysis
Detailed
Browser
Application
Application
Simulations
Application
Application
Tools
Web Service Client
Web Service Client
/

P
L
T
M
T
T
Extranet
H
H
Presentation
Intranet
Portal
Layer
Oracle 9i AS
/
/


P
L
P
L
T
T
M
M
T
T
T
T
H
H
P
P
H
H
A
A
O
O
S
S


/
/


L
L
text
text
M
M
text
text
View
View
text
text
X
X
Apache Struts
Servlet Engine
Apache Tomcat
P
P
A
A
O
O
S
S


/
/


L
L
M
M
X
X
Web Services (XML, SOAP)
GLUE / AXIS (Apache SOAP)
Client /
Analysis Tools
Detailed
Browsing
Browsing
View
Simulations
Transformation
System
Data
Performance
Costs
Budget
...
Access
P
A
O
S

Layer
/

I
I
I
I
L
M
M
M
M
M
R
R
R
R
X
Update
Delete
Controller
Insert
Select
Controller
Persistence
CMP
BMP
Persistence
EJB 2.0 Container /
JBoss
C
B
D
J
Sapienza DMS
GLUE / AXIS
Data
Database
Database
Storage
Database
Other datasource
Other datasource
(Web Services,...)
Other datasource
(Web Services,...)
Layer
(Web Services,...)
File System / DMS
Database Oracle 9i

14
External Interface Conceptual Data Model

• A user of an external tool browses the DRC
  searches for specific (predefined) equipments
• He can choose the equipment and export the
  relevant data to an XML/Soap file
• The layout of the XML/Soap file is defined
  through the XML Schema Definition File (XSD)
  the Web Service Definition Layer (WSDL)
• The data model of the interface is a subset of
  the DRC data model and is based on the
  requirements from SDO/CDF SimVis

15
Conclusion

• ESA DRC respectively Astrobus Equipment DB as
  proof of concept for model based development of
  databases
• Statistics
• 200 classes/1000 parameters
• 100 auto code (except application layer)
• 100 Tables /400 Relations
• Consistency between different appearances of data
  (RDMS, Browser, XML, Applications)
• Significant improvement of development life cycle
  
• Integration of experts with dedicated views
• Improved maintenance of product
• Similar approach as MDVE simulator

16
Outlook

• if one put in pieces a living organism, in such
  a way that each piece is isolated, it is done
  only to ease the experimental analysis and not to
  understand it separately. Indeed, to understand
  the physiological property, its value and its
  true meaning, it is a must to relate it to the
  whole and one must draw the final conclusions
  only in combination with its action on the whole
• Claude Bernard (1865), found in Pocket Atlas of
  Physiology 4th Edition, 1991
• ESA DRC respectively the Astrobus Equipment
  Database is a living part of the whole SE
  infrastructure. It supplies open standards as
  interface (XML, SOAP) to its environment and it
  is scaleable due to its data model respectively
  the technology behind
• It is seen to be a start for improving the SE
  infrastructure supporting modern SE approaches
  like Concurrent Engineering (CDF SDO) or
  (System) simulators ( e.g. MDVE)
• As seen the database has been evolved by taking
  the whole product life cycle, the SE challenges (
  e.g. distributed teams, information flow) and the
  vision to have a seamless transition of results
  from project phase to project phase and from
  discipline to discipline into account
• It can be seen as a prototype/platform for future
  improvements or harmonizations of SE
  infrastructures for example on customer side
  (ESA/ESTEC) and industry