Developing Ontologies for Collaborative Engineering in Mechatronics

21
Salzburg Research Forschungsgesellschaft m.b.H.| Jakob-Haringer-Str. 5/III | A-5020 Salzburg T +43.662.2288-200 | F +43.662.2288-222 | [email protected] | Developing Ontologies for Collaborative Engineering in Mechatronics Violeta Damjanović, Wernher Behrendt, Manuela Plößnig and Merlin Holzapfel Salzburg Research, Salzburg, Austria 4th ESWC 2007, Innsbruck, Austria

description

4th ESWC 2007, Innsbruck, Austria

Transcript of Developing Ontologies for Collaborative Engineering in Mechatronics

Page 1: Developing Ontologies for Collaborative Engineering in Mechatronics

Salzburg Research Forschungsgesellschaft m.b.H.| Jakob-Haringer-Str. 5/III | A-5020 Salzburg T +43.662.2288-200 | F +43.662.2288-222 | [email protected] | www.salzburgresearch.at

Developing Ontologies for Collaborative Engineering in Mechatronics

Violeta Damjanović, Wernher Behrendt,Manuela Plößnig and Merlin Holzapfel

Salzburg Research, Salzburg, Austria

4th ESWC 2007, Innsbruck, Austria

Page 2: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 2© Salzburg Research

Generic Mechatronic Product

Page 3: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 3© Salzburg Research

Mechatronic Domain

Mechanical Engineer

Software Engineer

Electronic Engineer

Page 4: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 4© Salzburg Research

Mechatronic Engineering Lifecycle Ontology

Mec

hani

c E

ngin

eerin

g O

ntol

ogy

DOLCE Foundational Ontology

Cross-domain Engineering Ontology

Sof

twar

e E

ngin

eerin

g O

ntol

ogy

Ele

ctro

nic

Eng

inee

ring

Ont

olog

yMec

hatr

onic

s

ImportNET Ontology Landscape

Page 5: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 5© Salzburg Research

| Collaborative Engineering| Application integration; Knowledge integration;

Process integration

| Mechatronic Engineering| Thramboulidis’ metamodel of Integrated

Mechatronics – Mechatronic processes| Yoshioka’ knowledge structure for the Knowledge

Intensive Engineering Framework (KIEF) – Mechatronic artefacts

| Mechatronic Domain Modeling | e.g. FBA (Functional Block Adapter) stereotype| STEP (Standard for Exchange Product Data)

Research Issues in ImportNET

Page 6: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 6© Salzburg Research

| ImportNET Approach to Mechatronic Domain Modeling

| Ontology Landscape in ImportNET| Methodology for the development of the

Mechatronic Ontology| Ontology Alignment to the DOLCE Foundational

Ontology

Key Ideas

Page 7: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 7© Salzburg Research

Ontology Development Methodologies – Methontology

| Methontology| Glossary of terms| concept taxonomies| ad-hoc binary relation diagrams| concept dictionary| it describes: relations; instance attributes; class

attributes; constants; formal axioms; rules; instances

| Methontology is agnostic about the target ontology representation language

Page 8: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 8© Salzburg Research

Ontology Development Methodologies – DILIGENT

| DILIGENT| addresses collaborative development of an ontology

| DILIGENT steps| BUILD – creates an initial, incomplete ontology| LOCAL ADAPTATION – specific groups can have their

variant of the ontology| ANALYSIS – of the local ontologies | REVISE – re-alignment of the shared ontology with

the local ones| UNDERSTAND the shared ontology| IDENTIFY SIMILARITIES – between local and shared

ontology

| DILIGENT is agnostic about the target ontology representation language

Page 9: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 9© Salzburg Research

Ontology Development Methodologies – On-To-Knowledge (OTK)

| OTK is a high level methodology| Kickoff| Refinement

| gather a seed taxonomy| develop a seed ontology| conceptualisation and formalisation| tool-supported refinement

| Evaluation| Maintenance

| OTK is agnostic about the target ontology representation language

Page 10: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 10© Salzburg Research

Ontology Development Methodologies – DynamOnt

| DynamOnt| Identify the problem; Structure the problem;| Identify concrete purpose and scenarios; | Identify main concepts of domain matter;| Create non-formal methods;| Knowledge design; Community design; Software

design;| Implementation

| DynamOnt is dedicated to uses DOLCE as the target ontology representation language.

| DynamOnt uses DOLCE ontology design patterns

Page 11: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 11© Salzburg Research

DOLCE – A Foundational and Formal Ontology

| Descriptive | Ontology for | Linguistic and | Cognitive | Engineering

| developed in the WonderWeb project

Page 12: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 12© Salzburg Research

| Participation pattern| Description-Situation pattern| Role-Task pattern| Design-Artifact pattern| Agent-Activity pattern| Information-Object pattern

DynamOnt Ontology Patterns

Page 13: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 13© Salzburg Research

Description and Situation Pattern

Page 14: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 14© Salzburg Research

Mechatronic Engineering Lifecycle Ontology

Mec

hani

c E

ngin

eerin

g O

ntol

ogy

DOLCE Foundational Ontology

Cross-domain Engineering Ontology

Sof

twar

e E

ngin

eerin

g O

ntol

ogy

Ele

ctro

nic

Eng

inee

ring

Ont

olog

yMec

hatr

onic

s

Ontology Landscape and Its Alignment to DOLCE

Page 15: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 15© Salzburg Research

Current Work – Modeling the Mechatronic Life-Cycle

| In engineering the V-model defines a generic life-cycle model

| Methodology | Top layer of the V-model in DOLCE| Analyse the actual life-cycle models using Event

Process Chain (EPC) notation (a semi-formal modeling language)

| Translate the EPC diagrams into the task ontology of DOLCE

Page 16: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 16© Salzburg Research

Mechatronic Engineering Lifecycle

A

Page 17: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 17© Salzburg Research

Top Layer of the V-Model

A

Page 18: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 18© Salzburg Research

EPC to Express V-Model

Fatman TLON Prolon

Start

Specify requirements

Customer

Project manager, engineers

Define conceptual

model

Not all functions specified

Requirements incomplete

Mechanical and electronic drawings

Customer requirements,

use cases

Rapid prototype - Mechanical

Design

Update HW requirements

& SW functionalities

HW and SW developer

Basic (electronic)

design

Electronic requirement specification

s

HW requirements& list of SW

functionalities

Working specifiations &

mechanical design

mechanical engineer

Project manager, engineers

XOR

Requirements complete

HW and SW developer, sales

& marketing

Customer

XOR

Conceptual model

accepted

Conceptual model not accepted

V

XOR

All functions specified

Domain specific

engineering

Event

Function

Information material

Roles

XOR

V AND

either / or

Exisitng comonents from

previous projects

Case Study A – requirement specifications and basic design (part 1)

A

Page 19: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 19© Salzburg Research

Life-Cycle Model Ontology – Layers of Specificity

A

Page 20: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 20© Salzburg Research

Summary and Conclusion

| ImportNET is trying to bring the Semantic Web technologies to mechatronic engineering

| Mechatronic engineering is multi disciplinary and therefore needs multiple ontologies

| The engineering process needs process modeling

| The engineering artifacts need structural modeling

| Therefore our ontologies need to capture the dynamic and the static aspects of the domains

Page 21: Developing Ontologies for Collaborative Engineering in Mechatronics

12.04.23 21© Salzburg Research

| Thank you !

| Questions ?

| Contact: | [email protected]| http://www.salzburgresearch.at