Ontology and the Navy SYSCOMs Systems Engineering Transformation Process: Difference between revisions

From NCOR Wiki
Jump to navigationJump to search
mNo edit summary
mNo edit summary
Line 7: Line 7:
:[https://www.youtube.com/watch?v=vYr5oB1O6ig Video]
:[https://www.youtube.com/watch?v=vYr5oB1O6ig Video]


:[https://buffalo.box.com/s/2hoet9ko03ylaz2o7nrhbl6fj15a4qm8 Slides]:
:[https://buffalo.box.com/s/2hoet9ko03ylaz2o7nrhbl6fj15a4qm8 Slides]


Part Two: '''Ontology for Product Lifecycle Management, or: how to use ontologies to build and fly a plane'''
Part Two: '''Ontology for Product Lifecycle Management, or: how to use ontologies to build and fly a plane'''

Revision as of 14:54, 9 December 2018

NAVAIR, NAVSEA and SPAWAR, the three Navy Systems Commands, have initiated a Systems Engineering Transformation (SET) that is designed to introduce model-based systems engineering into all aspects of their work. Given the extremely broad scope of this project the number and complexity of models that will be generated through this process will be immense, and experiments are already under way to explore the use ontology as a means of enhancing consistency and discoverability of models and their contents.

On September 19, 2018 the first meeting of the Navy SYSCOMs and DoD Ontology was held in Washington DC. In conjunction with this meeting Barry Smith delivered a lecture entitled "Ontology for Systems Engineering", divided into two parts, as follows:

Part 1: Three ways ontologies fail – with lessons learned for the Navy Systems Engineering Transformation

Video
Slides

Part Two: Ontology for Product Lifecycle Management, or: how to use ontologies to build and fly a plane

Video
Slides