Multi domain product architecture: start integrated, stay integrated

Unrestricted © Siemens AG 2019
Page 2 Siemens Digital Industries Software
Multi-Domain Product Architecture

Domain? Architecture?
Domain: also referenced as “discipline” such as Electrical, Mechanical, Software, Hydraulic, etc
Architecture: product or product line structured representation that is domain and implementation
agnostic. So normally limited to a functional representation but supporting a logical organization
I got it !...this is about an architecture representing all engineering disciplines
…No, it is not …There isn’t such practical single representation satisfying all
This architecture aims to specify the expected functional and non-functional
capabilities across all disciplines, also mapping all disciplines resulting artifacts

1847
A small garage
startup in Berlin,
Germany
Employees
10
Start-up capital
6.842
thalers
1st year revenue
3,420
thalers

Employees
377,000+
Today
Leading position in
Electrification, Automation
and Digitalization
Revenue
€82.9 billion
Net Income1
€6.1 billion
Profit margin Ind. Business
11.2%
Key figures as of Oct 2017 1 Strategic Unit

Software engineers
24,500+
Today
Siemens has become
a major player in
digitalization
Global Software Company
Atop 10
Connected assets
1 million+
Offerings
250+
Including
digital
services
and industrial
applications

Vision 2020+
Siemens Industrial Businesses – Focus drives value creation
Operating Companies Strategic Companies
Service Companies
Gas and Power Smart
Infrastructure
Digital
Industries
Mobility
Financial
Services
Global Business
Services
Real Estate
Services

Digital Industries setup ensures an end to end portfolio
for the digital transformation of process and discrete industries
Factory
Automation
Motion
Control
Process
Automation
Customer
Services
Vertical solutions
Software

In This Webinar
• Integrated MBSE
• Why Does It Matter?
• Taking a Multi-Domain Product
Architecture Approach
• Benefits Summary
Start integrated, stay integrated

Cross-Domain
Dependencies
Integrations
Complexity
Late Issue Discovery
Variations
Digital Thread
Accurate changes
Configured for in-context
Cost of Change
Virtual Vs. Physical testing
Late Vs. early Verification
Large Scale
Fast growing number of V&V
More…more…
Requirements, test
scenarios, features,
functions, etc
Waterfall Vs. Agile
SW content increasing fast
Impact analysis

Integrated Model Based Systems Engineering

Product Definition Starts With Requirements
Performance
Requirements
Product Line
Requirements
System
Requirements
Mechanical
Requirement
Electrical
Requirement
Manufacturing
Requirement
Software
Requirement
Decompose
Cascade
Integration
Requirements
Decompose
Cascade
Guided DecompositionManage DependenciesEnd-to-End Traceability
Domain
Requirements …

Enterprise-Grade Requirements Verification
Orchestrate the 1000’s requirement verifications across domains, track and monitor
Product
Architect
Systems
Engineer
Mechanical
Engineer
Electrical
Engineer
Test/Quality
Engineer
Software
Engineer

Teamcenter OOTB Multi-Domain Information Model
R
F
L
P
Eventually complex and very large scale….Leverage years of Teamcenter industry presence
…and more

Product Definition Comes With Multiple Contributing Facets
System Architecture
(Functional, Logical, Physical)
Parametrics
Requirements
Functional Safety
Functional Behavior
Cyber Security
Domains (SW,EE,HW)
Mass, Cost, Schedule,
Verification, Manufacturing, …
Performance - Simulation
Operational

One-Stop Model Access Connecting System Engineers,
Reviewers, and Stakeholders
Familiar model
content navigation
experience
Properties
Related diagrams
Requirements
traceability
Open in
modeling
tool
Create
traceability
Review & Markup
Workflow
Navigate &
find model
data
Where Used
Navigate relations in
and beyond the model

IMAGE
Customer specific
Product

Automatically Create Engineering Views
Create Recipes to collect the data for specific engineering tasks
Data are automatically identified using:
• Configuration Rules
• Closure Rules
• SQL Queries
RFLP object and relationship model
Configured: Variant, Effectivity, Revision
Dynamic: Encompass last changes

ONE RFLP-System Specification For All Connect Domains
Product Configurator – Parameter Management – Model Catalog
Multi-Domain Information ModelSystem Modeling Integration
Continuous 1D
Simulation
Simulation View
Concept Design Validation
3D CAD
CAE Simulation
3D Validation
Design & Simulation View
EE Design
Functional View
EE Architecture
Allocation optimization
System View
Program & Change Management – Workflow – Traceability
PRODUCT DEFINITION CONNECTED ENGINEERING

IMAGE
Customer specific
Product

Multi domain product architecture: start integrated, stay integrated

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Multi domain product architecture: start integrated, stay integrated

Similaire à Multi domain product architecture: start integrated, stay integrated (20)

Plus de Obeo

Plus de Obeo (19)

Dernier

Dernier (20)

Multi domain product architecture: start integrated, stay integrated