Use of Ontologies to Support Design Activities Dr. Oleg Lukibanov - - PowerPoint PPT Presentation

use of ontologies to support design activities
SMART_READER_LITE
LIVE PREVIEW

Use of Ontologies to Support Design Activities Dr. Oleg Lukibanov - - PowerPoint PPT Presentation

Use of Ontologies to Support Design Activities Dr. Oleg Lukibanov DaimlerChrysler AG Vehicle Engineering Goal To design a vehicle To specifications Marketing Competitive benchmarking Regulations Standards On time


slide-1
SLIDE 1

Use of Ontologies to Support Design Activities

  • Dr. Oleg Lukibanov

DaimlerChrysler AG

slide-2
SLIDE 2

2

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Vehicle Engineering Goal

To design a vehicle

To specifications

Marketing Competitive benchmarking Regulations Standards

On time

Shortened time to market

Within budget

slide-3
SLIDE 3

3

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Emerging Engineering Process: Catia V5

Use of Catia V5 features

Parameterized connected templates Embedded checks and validations Templates’ reuse

With the ‘right’ usage strategy

parameterized templates speed- up and simplify engineering process

CV5 templates allow integration

  • f best practices into design

process

slide-4
SLIDE 4

4

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Emerging Engineering Process Problems

Digital Vehicle consists of thousands of

“smart” templates and millions of associated parameters

Relations and dependencies among

templates are complex

Complexity of management CV5

templates within design process is not 100% covered with PDM systems

The question that we want to address is

slide-5
SLIDE 5

Problem: Template Management

slide-6
SLIDE 6

6

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Design Objects

TOP_Y_PIPE TOP_ExhaustResonator TOP_ExhaustSystem …

slide-7
SLIDE 7

7

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Design Object with Attributes

Top_ExhaustTailPipe ATTR: Exhaust_Pipe_WallThickness = 1.8 mm …. GeomAttr: Exhaust_Resonator_A_Exit_Plane = (x, y, z) (x1, y1, z1) …

slide-8
SLIDE 8

8

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Design Object with Attributes

Top_ExhaustTailPipe ATTR: Exhaust_Pipe_WallThickness = 1.8 mm …. GeomAttr: Exhaust_Resonator_A_Exit_Plane = (x, y, z) (x1, y1, z1) …

Design Object with Attributes

Top_ExhaustTailJoint_2Bolt ATTR: Exhaust_Pipe_WallThickness = 1.8 mm …. GeomAttr: Exhaust_Resonator_A_Exit_Plane = (x, y, z) (x1, y1, z1) …

slide-9
SLIDE 9

9

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

TOP_Y_PIPE TOP_ExhaustResonator TOP_ExhaustTailPipe TOP_ExhaustCatalyticConverter TOP_ExhaustFlexJoint_2Bolt TOP_ExhaustMuffler TOP_Exhaust_Pipe_Routing TOP_Exhaust_Oxigen_Sensor TOP_EXHAUST_SYSTEM_CALCULATIONS TOP_ExhaustSystem

Explicit connection through named attributes/paramete Implicit dependencies through the engineering process

slide-10
SLIDE 10

10

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Problem Statement

The example had 10 templates and

more than 4200 parameters (~150 ‘user parameters’)

Thousands of templates and millions

  • f parameters create a maintenance

challenge

Updating templates and distributing

the latest versions making sure that all associated templates still work will be a full-time job

It is necessary to develop a tool that

would assist template creators and support personnel in managing templates

slide-11
SLIDE 11

Solution

slide-12
SLIDE 12

12

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Ontology as a Solution

An ontology can serve as a layer

that represents the knowledge about the templates and their interconnections

Additional development should be

done to ensure the transparent interfaces with Catia V5, PDM systems and ontologies

slide-13
SLIDE 13

13

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Why Ontologies?

Ontologies can represent multiple

type of relations among objects

Ontologies can be integrated with

CV5

Ontologies can be managed

  • utside of CV5

Ontologies can be automatically

processed to find dependencies and detect conflict between

  • bjects
slide-14
SLIDE 14

14

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Critical Success Factors

Ability to automatically transfer Catia

templates into ontology

Ability to visually represent relations

among templates

Ability to visually represent cause-

effect chain of change in a template

  • n other templates

Stretch goals:

Ability to represent rules and formulae on

relations among templates and parameters

Ability to automatically update templates

where such rules or formulae are stated

slide-15
SLIDE 15

Approach to Building Templates’ Ontologies

slide-16
SLIDE 16

16

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Template Ontology Building: From the Source

Start from already developed

Catia V5 templates

Map the templates to knowledge

model

Allow managing templates

  • utside of CV5 Environment

Provide mechanism to

synchronize ontology to CatProducts

CatProducts are the ‘masters of

information’

slide-17
SLIDE 17

17

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

The CATProduct is used to export parameters and relationships as Ontology in OntoWorks

slide-18
SLIDE 18

18

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Browse the CATProduct and

  • utput path
slide-19
SLIDE 19

19

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Show the all the CATParts in the CATProduct and the input parameters in the selected CATPart

slide-20
SLIDE 20

20

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Show the specific parameter Contained in the selected CATPart

slide-21
SLIDE 21

21

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Visualization: Next Design Object

slide-22
SLIDE 22

22

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Visualization: Has Input Parameter

slide-23
SLIDE 23

23

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Ontology in Catia V5

slide-24
SLIDE 24

24

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Business Goals

Develop business process of “how

templates to be managed”

Develop a methodology that supports

business process

slide-25
SLIDE 25

25

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

OntoWorks or specialized Application OntoWorks, Model API Automatically OntoWorks or specialized Application Catia V5 OntoWorks, Model API Automatically atia V5

Business Process (templates update)

emplate development Check dependencies Modify dependent templates if needed Update Template Ontology

Repeat if necessary Integration with Catia V5

Parameter Dependencies Process Dependencie Manual Mapping of parameters if parameter names are not the same Augmenting parameter relations with rules and formulae

Optional

slide-26
SLIDE 26

26

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib Win 2000, Win XP Win 2000, Win XP, AIX, HP, SGI

Proposed Architecture

Template Ontology Database Back-End VPM Vault

VPM/Enovia V5

WebServices Enabled Model API CATIA WebServices ULEO

Catia V5 Template Manager

Use CATIA V5 GUI when possible

Catia V5 Catia V5

Tight Integration using CAA

WebServices Enabled Model API

Catia V5 OntoWorks

Native Integration

Template Ontology Maintenance, Authoring, Verification

Template Development

Expert Template Maintenance and Authoring

Native Integration Web Services

slide-27
SLIDE 27

Future Directions: How Does It Bring Us Closer To the Strategic Goal? Vehicle Structure Knowledge Model

slide-28
SLIDE 28

28

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Development of the “Master Vehicle Ontology”

Integrated Approach

Use globally and locally accepted

vehicle decomposition methods and develop localized ontologies representing sub-systems working-out inter system relationships along the way

slide-29
SLIDE 29

29

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Other Ontologies at DaimlerChrysler

Materials’ Ontology Fasteners and Common

Components Ontology

Ergonomics Rules Ontology Safety Rules Ontology Value Chain Ontology Projects and Systems Ontology …

slide-30
SLIDE 30

30

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Results of Templates Ontologies Activities

slide-31
SLIDE 31

31

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Vehicle Structure 1

Body in White Interior Electrical Chassis PWT Materials Reqs

slide-32
SLIDE 32

32

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Vehicle Structure 2

Dept 2 Dept 3 Dept 1 Dept 7 Dept 6 Dept 5 Dept 4

slide-33
SLIDE 33

33

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Central Ontology Repository

Texts: Word, PDF,

HTML Ontology- based Systems: DHM, KRMS, ODA Systems Web Services Ontoworks OntoWorks Web Services GoldFire Search

Functionality

CATIA INTEGRATED APPLICATIONS Model API Ontologies Model API ULEO Framework ABOK Ontology Systems Ontology e-Portal (Ingo's Ontology) ABOK WebBrowser Frontend: thorugh e Engineering Portal OntoPortal

Special Interfaces

Vehicle Ontology VPM V5 Knowledge Sources: EKF, VIW, ... Systems Web Services General Knowledge as Ontology WebServices

slide-34
SLIDE 34

34

Product Development Lifecycle Management DaimlerChrysler Con D Ol L kib

Questions