Lehrstuhl für Virtuelle Produktentwicklung - PDT Europe 2013
Lehrstuhl für Virtuelle Produktentwicklung - PDT Europe 2013
Lehrstuhl für Virtuelle Produktentwicklung - PDT Europe 2013
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
ENGINEERING CONSULT<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
The Convergence of PLM and MBSE –<br />
Will This Decrease or Increase the Risk with<br />
PLM Projects<br />
Perspectives on<br />
PLM and Model Based System Engineering<br />
University of Kaiserslautern<br />
Institute for Virtual Product Engineering<br />
EIGNER Engineering CONSULT<br />
Prof. Dr.-Ing. Martin Eigner<br />
VPE Folie: 1
ENGINEERING CONSULT<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Prof. Dr.-Ing. Martin Eigner<br />
Institut for Virtual Product Engineering (VPE)<br />
+<br />
EIGNER Engineering Consult<br />
CV Martin Eigner:<br />
1968 – 1971 Tool Maker<br />
1971 – 1976 University of Karlsruhe<br />
Mechanical Engineering, Economy<br />
1980 PhD in Applied Informatics<br />
1980 - 1985 Robert Bosch GmbH<br />
Technical Organization and IT / EE Development<br />
1985 Founding EIGNER+PARTNER<br />
PDM/PLM Solution Provider<br />
1999 Founding EIGNER Inc. Burlington (Headquarter)<br />
2001/2003 Company sold to Agile (now ORACLE) President<br />
since 2003<br />
since 2004<br />
since 1980<br />
since 1985<br />
since 1987<br />
since 2005<br />
Founding EIGNER Engineering Consult<br />
University of Kaiserslautern<br />
Institute for Virtual Product Engineering<br />
13 books related to CAD, PLM and IT<br />
Honored Member of German Engineering Association<br />
Founding and Board Member of ProSTEP Association<br />
Member of the WiGeP (Berliner Kreis), acatech TN<br />
Product Creation<br />
.<br />
ENGINEERING CONSULT<br />
VPE Folie: 2
ENGINEERING CONSULT<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Agenda<br />
…<br />
1 | Interdisciplinary and Integrated Products and Processes<br />
2 | Modell Based Systems Engineering / Frontloading<br />
3 I The Role of PLM in an MBSE Environment<br />
4 I Summary<br />
VPE Folie: 3
Disciplines<br />
ENGINEERING CONSULT<br />
PLM Vision<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ Integrated and federated product and process model along<br />
- Product lifecycle,<br />
- Disciplines and<br />
- Supply Chain<br />
Services<br />
Software<br />
Electronics<br />
Mechanics<br />
OEM<br />
Requirements<br />
Definition<br />
Product<br />
Planning<br />
Product<br />
Design<br />
Process<br />
Planning<br />
Production Operation Recycling<br />
1 st Tier<br />
Product Lifecycle<br />
2 nd Tier<br />
…<br />
VPE Folie: 4
ENGINEERING CONSULT<br />
Software Becomes a Dominant Factor of the Product<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ Mechatronic…<br />
Mechanic<br />
Mechatronic<br />
IT<br />
Mechatronic<br />
Mechanic<br />
IT<br />
Mechanik<br />
Source: vgl. [me] 2.2010<br />
Electronic<br />
Electronic<br />
□<br />
…yesterday (1968)<br />
…tomorrow<br />
When Software becomes dominant, why should we use methods from<br />
Mechanic & Hierarchical Requirements and Function Structure?<br />
VPE Folie: 6
ENGINEERING CONSULT<br />
Managing Interdiciplinary Complexity<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ Managing complexity of technical systems<br />
Now..<br />
- Increase of Software and personal interactions<br />
- Different engineering disciplines required<br />
- More fragmented and specialized systems<br />
- Organizations involved<br />
□ Interconnectivity among Subsystems<br />
- No longer treated as stand alone<br />
- Part of a larger Whole behavior<br />
[Source: Systems Engineering Handbook (INCOSE)]<br />
Services<br />
Software<br />
Mechanics<br />
Electronics<br />
[Based on: execpastor.com]<br />
VPE Folie: 7
ENGINEERING CONSULT<br />
New Products: Beyond Mechatronic: Cybertronic<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ Autonomeous Parking and Driving<br />
User Interaction (UML)<br />
act [Activity] ParkhausApp [ ParkhausApp ]<br />
Gebäudeausrüstung<br />
Allocation of Parkingslot<br />
Dauerparker<br />
KundenID<br />
übertragen<br />
KundenID<br />
übermitteln<br />
Standort<br />
ermitteln<br />
Kundenkonto?<br />
Standardparkplatz<br />
Anmeldung am<br />
Parkhaus<br />
KundenID<br />
„Eigner<br />
BMW Z4“<br />
übermitteln<br />
Academic Version for Teaching Only<br />
Commercial Development is strictly Prohibited<br />
KundenID<br />
übermitteln<br />
Parkhaus<br />
Check-in-App<br />
bdd [Model]<br />
Data [ autonomes Parksystem<br />
]<br />
«Log ical System Element»<br />
autonomes Parksystem<br />
parts<br />
Datenbank : Benutzerverwaltung<br />
Parkhaus Kaiserslautern<br />
IPhoneApp<br />
«Log ical System Element»<br />
«block»<br />
cybertroninisches Parkhaus<br />
ParkhausApp<br />
Benutzerdaten<br />
parts<br />
values<br />
Benutzerdaten<br />
: Einfahrtkontrolle<br />
KundenID : String<br />
: ParkplatzZuweisung<br />
Position : String<br />
: Einfahrtkontrolle<br />
: Fahrzeug leitsystem<br />
Wegpunkte<br />
Wegpunkte<br />
BMW<br />
«Log ical System Element»<br />
Fahrzeugsteuerung<br />
parts<br />
: Antrieb<br />
: Lenkung<br />
: Bremssystem<br />
Academic Version for Teaching Only<br />
Commercial Development is strictly Prohibited<br />
“Waypoints {(12.4,12.5), …}“<br />
Autonomeous Parking<br />
Ihr Fahrzeugdaten<br />
Automatisches<br />
Guten zugewiesener Tag,<br />
ubermitteln?<br />
Herr Einparken Parkplatz: Eigner<br />
starten? 1453<br />
akzeptieren<br />
Logical Building Blocks (SysML)<br />
„Parkingslot #: 1453“<br />
8<br />
8<br />
SW Entwicklung<br />
„Length < 5 m“<br />
Automobilbau<br />
VPE Folie: 8
ENGINEERING CONSULT<br />
Beyond Mechatronic: CYBERTRONIC<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ Many mechatronical products, system and subsystems, communicating each<br />
other…….<br />
□ Example: Airplane: status landing behavior reverse engine / Flaps (10%)<br />
…<br />
…<br />
VPE Folie: 9
ENGINEERING CONSULT<br />
Challenges for the Manufacturing Industry<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Software Intensive Products<br />
Connectivity<br />
Regulation<br />
Servitization<br />
Digitization<br />
Globalization<br />
Personalization<br />
Source: PTC<br />
MBSE: Model Based Systems Engineering<br />
VPE Folie: 10
ENGINEERING CONSULT<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Agenda<br />
…<br />
1 | Introduction Interdisciplinary and Integrated Products and Processes<br />
2 | Modell Based Systems Engineering<br />
3 I The Role of PLM in an MBSE Environment<br />
4 I Summary<br />
VPE Folie: 11
ENGINEERING CONSULT<br />
Model Based Systems Engineering + PLM<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Requirements<br />
Definition<br />
Product<br />
Planning<br />
Design<br />
Process<br />
Planning<br />
Production<br />
System Model<br />
System<br />
Model<br />
Simulation<br />
Model<br />
CASE M-CAD E-CAD<br />
PLM Backbone<br />
Targets<br />
Validation<br />
R<br />
F<br />
Requirements Engineering and Specification<br />
(Requirements, Functions and Behavior)<br />
<strong>Virtuelle</strong><br />
Tests<br />
Physical<br />
Tests<br />
Simulation Model<br />
L<br />
Logical System Design and<br />
multiphysical Simulation<br />
Simuation<br />
Testing<br />
CASE Model<br />
E-CAD Model<br />
M-CAD Model<br />
P<br />
Dicipline Specific<br />
Design<br />
Dienstleistung<br />
Hybride<br />
Tests<br />
(z.B. HIL)<br />
Mechanik<br />
Disciplin Specific<br />
E/E<br />
Detailling<br />
Software<br />
Modellbildung und -analyse<br />
Source: VPE Research Project mecPro² (T. Gilz)<br />
VPE Folie: 12
ENGINEERING CONSULT<br />
The „old“ Product Development Process (PDP)<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ Document centric PDP<br />
Concept<br />
Specification<br />
System<br />
Specification<br />
Subsystem<br />
Specification<br />
Function<br />
Specification<br />
Design<br />
Specification<br />
Implementation<br />
□ Many non integrated SW Tools<br />
Word, Excel, Visio, Powerpoint, etc.<br />
□ No consistency and traceability of<br />
documents<br />
□ Gaps between different development<br />
phases and stakeholder<br />
□ No guaranteed Quality<br />
□ No traceability regarding international<br />
standards (ISO 26262, EN50128,<br />
DO178B)<br />
Quelle: nach VIF Graz<br />
VPE Folie: 13
ENGINEERING CONSULT<br />
Model Based Product Development Process<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Concept<br />
Specification<br />
System<br />
Specification<br />
Requirements<br />
model<br />
Technical<br />
System<br />
Model<br />
□ IT based Models are the basic of<br />
all development phases and they<br />
are transferable to the next phase<br />
□ The integration is based on formal<br />
models and not on documents<br />
□ Traceability is guaranteed<br />
(ISO 26262, EN50128, DO178B)<br />
Subsystem<br />
Specification<br />
Behavioral<br />
Model<br />
□ The documentation is derivated<br />
from the model<br />
Function<br />
Specification<br />
Design<br />
Specification<br />
Behavioral<br />
Model<br />
Implementation<br />
□ The models must be administrated<br />
(versioning, revisioning,<br />
configuration)<br />
Quelle: nach VIF Graz<br />
VPE Folie: 14
ENGINEERING CONSULT<br />
□ Specification (e.g. in SysML)<br />
req Beispielanforderungsdiagramm<br />
«DeveloperRequirement»<br />
Winkel<br />
Id=“EF_06“<br />
Text=“Der Endwinkel soll 90 Grad<br />
betragen.“<br />
Text=<br />
Id=<br />
«DeveloperRequirement»<br />
...<br />
«DeveloperRequirement»<br />
Masse Schlitten<br />
Id=“EF_07“<br />
Text=“Der Schlitten soll maximal 1kg<br />
wiegen.“<br />
Anforderungen<br />
bdd Beispiel Blockdefinition<br />
Struktur<br />
«trace»<br />
«block»<br />
Controller<br />
SollWinkel = 90<br />
SollGeschwindigkeit = 0<br />
MotorStellen()<br />
ibd Inverses Pendel<br />
«trace»<br />
Multi-Physical Description and Simulation Models<br />
«UserRequirement»<br />
vertikale Position<br />
Id=“BF_04“<br />
„Der<br />
«block»<br />
Pendelstab soll in vertikaler<br />
«block»<br />
Position<br />
Motor<br />
gehalten werden.“<br />
Pendelstab<br />
«block»<br />
«block»<br />
Rotationssensor<br />
Drehgelenk<br />
Induktivität = 0.005<br />
Länge = 1<br />
Trägheitsmoment = Verhalten<br />
...<br />
Masse = 0.9<br />
w<br />
phi<br />
Schwerpunkt = ...<br />
«trace» «block»<br />
Controller<br />
«block»<br />
v s<br />
Schlitten<br />
steuert<br />
«UserRequirement»<br />
Masse<br />
«block» Länge = 0.1<br />
Translationssensor Id=“BF_05“ Höhe = 0.05<br />
„Das System soll Schwerpunkt eine Gesamtmasse = ...<br />
von 4 kg nicht überschreiten.“<br />
liefert Information<br />
stm Zustände<br />
«block»<br />
Inverses Pendel<br />
Schlitten in<br />
Mittelposition<br />
«block»<br />
Pendelstab<br />
Pendel aufschwingen<br />
Schlitten nach<br />
links<br />
Position < max. links /Motor(rechts)<br />
«block»<br />
Schlitten<br />
Position > max. rechts /Motor(links)<br />
Pendel<br />
senkrecht<br />
stellen<br />
Pendel halten<br />
«block»<br />
Motor<br />
«Block»<br />
Rotationssensor<br />
Winkel 90°<br />
Winkel<br />
Winkelgeschwindigkeit<br />
WinkelMessen()<br />
Geschwindigkeit<br />
WinkelgeschwindigkeitMessen()<br />
...<br />
«block»<br />
Rotationsgelenk<br />
«block»<br />
Translationsgelenk<br />
Startwinkel = 70<br />
...<br />
Schlitten nach<br />
rechts<br />
Winkel > 70°<br />
Schlitten regeln<br />
Winkel 110<br />
Pendel nicht<br />
mehr haltbar<br />
□ First simulations (e.g. Matlab/Simscape/Modelica)<br />
Simulation<br />
models<br />
CASE<br />
models<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
System<br />
model<br />
E-CAD<br />
models<br />
M-CAD<br />
models<br />
Library<br />
Mapping of requirements,<br />
functions und logical solution elements<br />
link analysis models, ports and parameters<br />
VPE Folie: 15
ENGINEERING CONSULT<br />
System Model – CASE Model<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ Specification (e.g. in SysML/ModelicaML)<br />
req Beispielanforderungsdiagramm<br />
«DeveloperRequirement»<br />
Winkel<br />
Id=“EF_06“<br />
Text=“Der Endwinkel soll 90 Grad<br />
betragen.“<br />
Text=<br />
Id=<br />
«DeveloperRequirement»<br />
...<br />
«DeveloperRequirement»<br />
Masse Schlitten<br />
Id=“EF_07“<br />
Text=“Der Schlitten soll maximal 1kg<br />
wiegen.“<br />
Anforderungen<br />
bdd Beispiel Blockdefinition<br />
Struktur<br />
«trace»<br />
«block»<br />
Controller<br />
SollWinkel = 90<br />
SollGeschwindigkeit = 0<br />
MotorStellen()<br />
«trace»<br />
«trace»<br />
«UserRequirement»<br />
vertikale Position<br />
Id=“BF_04“<br />
„Der<br />
«block»<br />
Pendelstab soll in vertikaler<br />
Position<br />
Motor<br />
gehalten werden.“<br />
Induktivität = 0.005<br />
Trägheitsmoment = ...<br />
«block»<br />
Schlitten<br />
steuert<br />
«UserRequirement»<br />
Länge<br />
Masse<br />
= 0.1<br />
Id=“BF_05“ Höhe = 0.05<br />
„Das System soll Schwerpunkt eine Gesamtmasse = ...<br />
von 4 kg nicht überschreiten.“<br />
liefert Information<br />
«block»<br />
Inverses Pendel<br />
«block»<br />
Pendelstab<br />
Länge = 1<br />
Masse = 0.9<br />
Schwerpunkt = ...<br />
«Block»<br />
Rotationssensor<br />
Winkel<br />
Winkelgeschwindigkeit<br />
WinkelMessen()<br />
WinkelgeschwindigkeitMessen()<br />
...<br />
«block»<br />
Rotationsgelenk<br />
Startwinkel = 70<br />
...<br />
□ Discipline specific Development (e.g. CASE)<br />
Simulations<br />
models<br />
CASE<br />
models<br />
System<br />
model<br />
E-CAD<br />
models<br />
M-CAD<br />
Models<br />
VPE Folie: 16
ENGINEERING CONSULT<br />
M-CAD – Multi-Physical Simulation Models<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ Bridging of M-CAD with multi-physical simulation models<br />
- Takeover of information of<br />
▪ Assemblies<br />
▪ Kinematic relations<br />
▪ 3D geometry<br />
Kinematic relations<br />
3D geometry<br />
Simulation<br />
models<br />
CASE<br />
models<br />
System<br />
model<br />
E-CAD<br />
models<br />
M-CAD<br />
models<br />
F1_300_InvPendel.ASM<br />
F3_300_Pendelstab.PRT<br />
F3_300_Schlitten.PRT<br />
F3_300_RotGelenk.PRT<br />
F3_300_Motor.PRT<br />
F3_300_Schlitten.PRT<br />
Baugruppenstruktur<br />
M-CAD<br />
Multiphysikalische<br />
Simulationen mit Detailgeometrie<br />
VPE Folie: 17
ENGINEERING CONSULT<br />
System Model Must be Administrated by PLM<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Source: Discussions with Chris Paredis, Georgia Tech<br />
System Models + PLM = SysLM<br />
VPE Folie: 18
ENGINEERING CONSULT<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Agenda<br />
…<br />
1 | Introduction Interdisciplinary PDP<br />
2 | Modell Based Systems Engineering / Frontloading<br />
3 I The Role of PLM in an MBSE Environment<br />
4 I Summary<br />
VPE Folie: 19
ENGINEERING CONSULT<br />
Product and Process Centric Backbone for SysML<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Plan Concept Design Validate Production Support<br />
Requirements BOM System /Functional BOM Engineering BOM Simulation/Testing BOM Manufacturing BOM Service BOM<br />
Focus<br />
Systems Lifecycle Management<br />
(SysLM)<br />
Production Systems<br />
(ERP/MES)<br />
VPE Folie: 20
ENGINEERING CONSULT<br />
MBSE as an integrated part of a SysLM concept<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Plan Concept Design …<br />
Engineering (authoring systems in concept design, M-CAD, E-CAD, CASE)<br />
Requirements structure System /Functional BOM (e.g. SysML) Engineering BOM<br />
Requirements management tools<br />
System requirements<br />
System structure<br />
CAD/CASE authoring systems<br />
4XX_200.ASM<br />
System behavior<br />
L224_300_200_HS.ASM<br />
F1_300_200_G.ASM<br />
F3_300_211_B.PRT<br />
F3_300_238_F.PRT<br />
…<br />
Requirements structure<br />
Deriving Product hierarchical Lifecycle Management structure information (PLM)<br />
(e.g. via XML)<br />
System /Functional BOM<br />
System requirements System structure<br />
Engineering BOM<br />
All data in one PDM system<br />
System requirements model<br />
System structure model<br />
System behavior model<br />
VPE Folie: 21
ENGINEERING CONSULT<br />
MBSE as an integrated part of a SysLM concept<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Plan Concept Design …<br />
Engineering (authoring systems in concept design, M-CAD, E-CAD, CASE)<br />
Requirements structure System /Functional BOM (e.g. SysML) Engineering BOM<br />
Requirements management tools<br />
System requirements<br />
System structure<br />
CAD/CASE authoring systems<br />
4XX_200.ASM<br />
System behavior<br />
L224_300_200_HS.ASM<br />
F1_300_200_G.ASM<br />
F3_300_211_B.PRT<br />
F3_300_238_F.PRT<br />
…<br />
Product Lifecycle Management (PLM)<br />
Requirements structure<br />
System /Functional BOM<br />
System requirements System structure<br />
A change in system requirements<br />
Engineering BOM<br />
All data in one PDM system<br />
System requirements model<br />
System structure model<br />
System behavior model<br />
VPE Folie: 22
ENGINEERING CONSULT<br />
MBSE as an integrated part of a SysLM concept<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Plan Concept Design …<br />
Engineering (authoring systems in concept design, M-CAD, E-CAD, CASE)<br />
Requirements structure System /Functional BOM (e.g. SysML) Engineering BOM<br />
Requirements management tools<br />
System requirements<br />
System structure<br />
CAD/CASE authoring systems<br />
4XX_200.ASM<br />
System behavior<br />
L224_300_200_HS.ASM<br />
F1_300_200_G.ASM<br />
F3_300_211_B.PRT<br />
F3_300_238_F.PRT<br />
…<br />
Product Lifecycle Management (PLM)<br />
Requirements structure<br />
System /Functional BOM<br />
System requirements System structure<br />
A change in E-BOM structure<br />
Engineering BOM<br />
All data in one PDM system<br />
System requirements model<br />
System structure model<br />
System behavior model<br />
VPE Folie: 23
ENGINEERING CONSULT<br />
Core concept of SE VPE data model<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ Reduced data schema (co<br />
VPE Folie: 24
ENGINEERING CONSULT<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Agenda<br />
…<br />
1 | Introduction Interdisciplinary PDP<br />
2 | Modell Based Systems Engineering / Frontloading<br />
3 I The Role of PLM in an MBSE Environment<br />
4 I Summary<br />
VPE Folie: 25
ECM related Items (Configured Items)<br />
(orange new MBSE itrems)<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Supply Chain<br />
Simulations<br />
Documents/<br />
Documentation<br />
Software<br />
Function/<br />
Behavior<br />
Manufacturing/<br />
Assembly<br />
Resources/<br />
Process<br />
Planning<br />
4711<br />
Requirements<br />
Simulation/DMU<br />
Test/PMU<br />
Maintenance<br />
Customer<br />
Feedback<br />
Classification/<br />
Commonality/<br />
reUse<br />
Where Used?<br />
Items (M,E,SW)<br />
E-BOM<br />
M-BOM<br />
VPE Folie: 26
ENGINEERING CONSULT<br />
Summary<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
□ There are existing IT-Tools for all phases of an integrated interdisciplinary<br />
Product Development Process<br />
(SysML, Simulink/Simscape/Matlab, Modelica, MKS, CAD-M/E, Case)<br />
□ There is no accepted, integrated and interdisciplinary design theory and<br />
customers have no experiences with this new approach<br />
□ The integration of the System Model and their artifacts Requirements, Functions,<br />
Behavior and Logical Building Blocks with PLM/SysLM is absolutely necessary<br />
because of traceability regarding international standards (ISO 26262, EN50128,<br />
DO178B)<br />
□ The completeness, usability and acceptance of these new tools and processes is<br />
not existing but f.e.SysML is a worldwide Standard (OMG) and we should focus<br />
on further development<br />
□ The Integration of Mechanic, Electronic and Software along<br />
the Product Lifecycle even without the early phases is real challenging…..and<br />
very seldom realized in industry<br />
□ The risk with the PLM/SysLM project becomes higher with more objects to<br />
administrate…. But the real problems of unsuccessful PLM implementation is not<br />
the quantity of objects, but….<br />
VPE Folie: 27
ENGINEERING CONSULT<br />
Typical PDM/PLM scenarios<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
- Jump as a tiger … land as a carpet runner<br />
- No vision no budget, vision but no budget, no vision but budget<br />
- No Champion, no leadership<br />
- MyPLM = „I need my own PDM/PLM Solution“<br />
- To many own developed or over customized PDP/PLM solutions<br />
- Missing milestone plan, missing long term perspective<br />
- Redundancy and overlapping with legacy systems (ERP), who is master?<br />
- No PDM/PLM awareness on management level („no father, no mother“)<br />
- Wrong people to execute the PDM/PLM project<br />
- No balance between central defined and executed functions (f.e. engineering<br />
item master, ECM process, multi-disciplinary E-BOM) and flexible regional,<br />
product or discipline dependent solutions (f.e. TDM,....)<br />
- Customers want 150%, suppliers promise 120% and deliver 68%<br />
- No guidance from the Solutions Provider and from Management<br />
- IT drives processes and not vice versa.....<br />
- Detailed analysis of technique (System A 3,34 points, System B 3,29<br />
points,...)<br />
- Missing user acceptance<br />
VPE Folie: 28
ENGINEERING CONSULT<br />
<strong>Lehrstuhl</strong> <strong>für</strong> <strong>Virtuelle</strong> <strong>Produktentwicklung</strong><br />
Further questions<br />
VPE Folie: 29
Change language