CDF Infopack 2015

1CDF Info Pack 2015| Slide 1 ESA UNCLASSIFIED Releasable to Public

The ESA Concurrent Design FacilityConcurrent Engineering Applied to

space mission assessments

CDFESA/ESTECNoordwijk - NL

CDF Info Pack 2015| Slide 2 ESA UNCLASSIFIED Releasable to Public

CDF: what is it?

The ESTEC Concurrent Design Facility is an Integrated Design Environment (IDE) available to all ESA programmes for interdisciplinary and inter-directorate applications, based on Concurrent Engineering methodology

The implementation started in Nov.1998, on an experimental basis with initiative (and support) of the General Studies Programme (GSP)

Initially conceived for the assessment and the conceptual design of future space missions, i.e. internal pre-phase A / feasibility studies

Featuring: Team orientated concurrent engineering Integration of tools, project data, mission and system models Simultaneous participation of all mission domains, incl.

Programmatics/AIV, Operations, Cost Engineering, Risk Analysis, CAD, Simulation


ContractualPackage

SystemRequirements

Update SRDUpdate SRD

ESA Project life cycleESA-CDF record

Sta

keho

lder

s(e

g. S

cien

ceCom

mun

ity)

INDUSTRY

A B1 B2 C/D

Industrial Study / Activity

or

Design work Design work Design work Design work

PRR SRR PDR

= CDF application / quantity

Generation ofMission Idea

CDR

IndustrialStudy

CDFStudy

Phase0

190+

3229

7

2

3

2


So, What is Concurrent Engineering

Concurrent Engineering is a systematic approach to integrated product development that emphasises the response to customer expectations. It embodies team values of cooperation, trust and sharing, in such a

manner that decision making is by consensus,involving all perspectives in parallel, from the

beginning of the product life-cycle.


Teamwork

1. SequentialWhy do we need concurrent engineering?

!


Teamwork

2. Centralised

System Architect

To overcome the communication gaps between the designers (who produce design information) and the users (who utilise the design information)


Teamwork

3. Concurrent

Team LeaderSystem Engineer

All of the people, all of the time, all in the same place


Teamwork - Comparison

Sequential ConcurrentCentralized

Simple Natural Efficiency increase Speed increase Increased system

awareness Better Communication

Efficiency increase Speed increase All aware of the

system

Slow speed Easy divergence from

requirement Not fail safe Poor communication

Control Needs guidance

Relies on 1 central person

Not fail safe

Global Increase of output quality and speed

+

-


Benefits

Performances (typical pre-Phase A study):

Study duration (Design phase): 3-6 weeks (cp. 6-9 months!)

Factor 4 reduction in time

Factor 2 reduction in cost(for the Customer)

Increased nr of studiesper year, compatibly with max 2 parallel studies

Quality improvement, providing quick, consistent and complete mission design, incl. technical feasibility, programmatics, risk, cost

Technical report becomes part of the specs for industrial activity,

(Cost report remains the ESA independent reference)

Capitalisation of corporate knowledge for further reusability

CDF: an essential tool for the ESA Decision Making & Risk Management processes


CDF: the team

1. Team of ESA specialists (senior and junior!)2. Technical disciplines (CDF positions) selected for

Phase 0 studies (according to ESA organisation):

Systems PowerInstruments Command and Data HandlingMission analysis CommunicationsPropulsion Ground Systems & OperationsAttitude and Orbit Control SimulationStructures/Configuration ProgrammaticsMechanisms/Pyros Risk AssessmentThermal Cost Analysis

Note: Instrument design activities have specialised teams with disciplines such as Receiver, Optics etc.

Black: sub-system levelBlue: system levelRed: based on hi-end tools


Process elements

1. Conducted in sessionsa. Plenary meeting where representatives of all space

engineering domains participate from early phases (requirement analysis) to end of design (costing)

b. 6 to 10 sessions / study 4 hours / sessionbi-weekly frequency

c. Team leader co-ordinationd. Customer participation

2. Model driven3. On-line design 4. Highly co-operative & interactive5. Iterations6. Design options comparison and trade-offs


Design process

Environment

Lifetime

Payload

Reliability

Schedule

Mission requirements &

constraints

Products

Study Level

Planning

Study requirements

Studyresults

Conceptual model of mission & spacecraft design process

Resources

Objectives

Technology

Budget

Configuration

Cost

S/C Design

Risk

Simulation

Programmatics

Options

Launcher


1. Model each domain (e.g. s/s) design2. Share data between domain models3. Interface with domain specific tools4. Provide user visibility

Use spreadsheets (MS Excel)

CDF: Integrated Design Model (*)

Replaced by OCDT (Open Concurrent Design Tool) in the course of 2014


CE: iterative processThe Spiral Model

Sub-system Design

Design Verification

Risk Assessment

Cost Analysis

Mission RequirementAnalysis

Mission Analysis

Key parameter X

Key parameter Z

Key parameter Y


Exchanging Data

Process:1. Specialist k performs

an estimate and shares data in CR

2. Data is available to other specialists

System

Cost

Discipline i

Discipline j

Discipline k Central Repository (CR)

Data


Exchanging Data




3. Each specialist can use this data to perform calculations and share the results

System

Cost

Discipline i

Discipline j


Data


Exchanging Data





x. System makes budgets

System

Cost

Discipline i

Discipline j


Data


Exchanging Data





x. System makes budgetsy. Overall process iteratesz. Final design done, all information available in CR

System

Cost

Discipline i

Discipline j


Data

10


Exchanging Datavs. later phases

Concurrent early phases (0, A) Later Phases (B, C, D, E)

time

baseline


ESA-CDF previous solution:Integrated Design Model

Inputs Sheet

Outputs Sheet

Calculation Sheets

Presentation Sheets

Data Parking (matrices)

Domain Specific Tools &

DBs

Data Exchange

(scalars)

Subsystem-1

Subsystem-n

Cost

System

Risk

Programmatics

Large Data Structures

11


PostgreSQLProtocol

over TCP/IP

Web Services Processor(nodejs on Google V8)

Persistent Data Store(PostgreSQL RDBMS) Firewall

(optional)

http(s) REST protocol(on standard ports 80 or 443)

JSON content

ConCORDEConCORDE

ConCORDEConCORDE

ConCORDEConCORDE

ConCORDEConCORDE

DST(Domain Specific Tool)

OCDT Server OCDT Clients

Domain 1

Domain 2

Domain 3

Domain N

ESA-CDF NEW current solution:Open Concurrent Design Tool (OCDT)


Database

ECSS-E-TM-10-23&25 Approach:Standards and Tool Implementations

Semantic Data Model Standard

Semantic Data ModelMaster Definition of Concepts

addresses what not how

Derived Logical and Physical Data Models

Reference Data Libraries (RDLs) Runtime loadable predefined objects,

including QUDV and Categories

Software Implementations

ToolTool

Tool

DatabaseDatabase

Automated transformations

Interoperable tools and databases

(including adapters around existing tools)

Generated

Runtime use

12


OCDT and IDM Differences (1/2)

IDM OCDT

Data Exchange Save & Close Workbook Data Exchange pulls new values in New values available to all participants

Publications Domain owner submits values to Server Team Leader / SE publishes new Publication Values in new Publication available to all participants History of Iterations is kept

(model state at end of each Iteration is stored)

Owned Parameters in Outputs sheet Input Parameters in Inputs sheet

Parameters and ParameterSubscriptionsin Definitions view & worksheet

Fixed, numbered naming convention for architectural items and parameters

Any object has name and short name Any architectural item or parameter can be uniquely referenced by

short name path, e.g.:MySC.sm.str2.P_max\Cruise.On

short name path used as Excel cell-name for calculation sheets


OCDT and IDM Differences (2/2)

IDM OCDT

Fixed naming and structure of decomposition levels System, Element, Equipment,

Instrument,

Configurable Categories and Rules in RDL, adaptable for family of applications Space missions Launchers Instruments System of systems

Support for options Option-specific architecture built by copy-

paste One workbook per Option

Support for options All Options defined in Definitions view Single-source modular definition of re-usable building

blocks Only configure differences per Option Automatically generate fully expanded architecture

worksheet for each Option in Domain workbook One worksheet per Option

13


Deorbit strategies

Future Telecomms

Payload &P/L accommodation

ROSITA instrument on Columbus External Platform

ISS Internal Payload Science Requirements Definition

IMPACT facility inside an ISS rack

Socrates

Hea

vy L

ift

Laun

ch V

ehic

le

Advanced launchers Clean Space and Future Programmes

Telescopes and Technology

FIRI

WiFLY

Diverse range of space missions

Sentinel

ExoMars

Laplace


System of Systems architecture

System of Systems (SoS) studies involve different participants and tools but are still carried out in a concurrent environment.SoS should be distinguished from large but monolithic systems by the independence of their elements, their evolutionary nature, emergent behaviours, and a geographic extent that limits the interaction of their elements to information exchange.

14


System of Systems Architecture Activities Evaluated set of architectures (based on customer preferences/priorities) Identification of potential additional service(s)


CDF layout

Meeting RoomAnnex Design Room

Lobby

Design Room B

Printer RoomCoffee Room

Archive Room

Server Room

Design Room A

Projection Room

15


ESA-CDF FacilityRoom A


ESA-CDF FacilityRoom A

16


17 Concurrent Design Centres inEuropean Space Sector

31

legendAgencyIndustryUniversity

The Netherlands CDF at ESA/ESTEC, Noordwijk

United Kingdom CDF at Univ. of Strathclyde, Glasgow SDO at EADS/Astrium, Stevenage CDF at Univ. of Southampton, Southampton CDF at Harwell Institute, Oxford Germany

CEF at DLR, Bremen SDO at EADS/Astrium, Friedrichshafen

Italy COSE at Thales Alenia Space, Torino ISDEC at Thales Alenia Space, Roma CDF at La Sapienza Univ., Roma CEF at ASI, Roma

Portugal CDF at Univ. Tcnica de Lisboa, Lisbon

Switzerland CDF at EPFL, Lausanne

France CDF at ISU, Strasbourg PASO at CNES, Toulouse SDO at EADS/Astrium, Toulouse CDF at Thales Alenia Space, Cannes


Agencies (Europe)

CNES CIC Inauguration Nov. 2005

DLR (Bremen) CEFInauguration 8 Dec. 2008

17


Agencies (Europe)

ASI CEFopening 13 July 2008


Agencies (USA)

NASA-JPL PDC Team X

18


Industry (Europe)

EADS ASTRIUM (D) - SDO (Satellite Design Office)


Industry (Europe)

TAS-I & F (Turin, Rome, Cannes) - CDF

19


Academia

MelbourneAustralia

Victorian Space Science Education Centre

(VSSEC)


Academia

ISU CDF

EPFL

20


Further information

Provided on the CDF Web site:http://www.esa.int/cdf


CDF Infopack 2015

Documents

Transcript of CDF Infopack 2015