Ontology Engineering for Systems Engineering -- low hanging fruits

4,410 views

Published on

Slides for Ontology Summit 2nd February 2012 online session.

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
4,410
On SlideShare
0
From Embeds
0
Number of Embeds
3,277
Actions
Shares
0
Downloads
32
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ontology Engineering for Systems Engineering -- low hanging fruits

  1. 1. Ontology Engineering for Systems EngineeringLow Hanging Fruits: PLM Data Models Ontology Summit 2-feb-2012
  2. 2. Levels of matter * levels of realization • Engineering specialties/professions/domains: multiple in every cell – systems engineering needed • Integration in a end product: all the table Requirements Architecture Design Implementation OperationMacro (plant)Meso (piplinenetwork)Micro (pipe)Nano (steel) 2
  3. 3. Contemporary PLM architecture life cycle: levels of realization (configuration baselines) requirements architecture As designed As build • Enabling system Actions Project model (engineering enterprise) Product model • System-of-interest • Systems in operation environment subprojectMechanical Electrical … GIS PLM 2…N subsystem ALL THE MATRIX Domains (aspect oriented modeling): structure, behavioral 3
  4. 4. Problems in definition of ontology for system-of- interest and system in operation environment (PLM “repository”, product model)• ontology of system components and modularity (system with subsystems, interfaces, catalogs)• Geometry (shapes and mereotopology)• UoMs• Causality, mapping, “meta”, requirements, etc.• trace relations, deontic modalities• Configuration baselines, design/solution variants (modalities as possible worlds)• risk modeling and assurance case• Socio-technical systems representation (enterprise engineering, see next slide about ogranization modeling)• Real-time behavioral modeling (multi-physics). Example: Simantics software platform: not too similar to ordinary PLM in ontology part but very similar in data integration architecture• Multiparadigm Software and computers (cyber-physical systems)• … (multiple other domains of contemporary engineering) 4
  5. 5. Problems in definition of ontology for enabling system (PLM workflow/issue tracking, “project model”)• situational method engineering (SME): systems engineering as a specific method of work (BoK)• System life cycle models, adaptive case and issue management, process and project management, organograms: enterprise architecture. Processes defined at design time and at run-time.• Motivational models for human action in enabling systems/systems of systems/extended organizations/eco-systems (praxeology) 5
  6. 6. Syntactic problems (languages and expressivenes)• Object with attributes (“what an object in one project is an attribute in another”), not fact- oriented• OWL is considered harmful.• Architecture language (systems engineering ontology-based language) needed. SysML is considered harmful. 6
  7. 7. Ontology evolution• Multiple enabling systems  multiple PLM, multiple ontologies.• complex engineering project lasts 10 years and more. Ontologies of all authoring tools and PLM will be changed during project.• Contemporary reference data will be legacy reference data. Needs international standardization for representation, record keeping and maintenance.• We need inherit and adopt/re-engineer reference data (ontology) from legacy systems as a first step in evolutionWhat to do with distributed reference data configurationmanagement while witnessing of massively parallel evolutionof ontological «eternal classes»? 7
  8. 8. Legacy standards, regulations, prototypesLegacy standards, regulation and prototypedesigns and projects are mix of natural languagesentences, semiformal and formal (oftengraphic) languages.We need new type of NLP parsers: engineeringlanguage (diagrams, drawings, texts with tablesand formulae) processing.This needs combined usage ofterminology/semiotics and ontology. 8
  9. 9. Education• We have bad experience of work with IT people and engineers: they expect 3 day courses should fit for ontology-based data integration.• How to teach people for ontology-based data modeling in 3 days? (not tell me that this is impossible!) 9
  10. 10. Questions?Anatoly Levenchuk,ailev@asmp.msk.suVictor Agroskin,vic5784@gmail.comTechInvestLab.ru+7 (495) 748-53-88 10

×