1 Adaptive Data Access Interface for STEP Model Repositories- support AEC product lifecycle management Frank Wang Donghoon Yang Chuck Eastman.

Slides:



Advertisements
Similar presentations
Introduction to Product Family Engineering. 11 Oct 2002 Ver 2.0 ©Copyright 2002 Vortex System Concepts 2 Product Family Engineering Overview Project Engineering.
Advertisements

ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
ISO TC184/SC4 Future architecture Rotterdam Progress on the Future SC4 Architecture PWI Friday 13 th November 2009.
ITS Ontology-based Learning Resources Repositories Montreal, June 23 rd, 2008 From a Conceptual Ontology to the TELOS Operational System Gilbert.
ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group.
OMG Architecture Ecosystem SIG Federal CIO Council Data Architecture Subcommittee May 2011 Cory Casanave.
© 2005 Prentice Hall6-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
OASIS Reference Model for Service Oriented Architecture 1.0
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Page 1 Building Reliable Component-based Systems Chapter 19 - Industrial Experience with Dassault Système Component Model Chapter 19 Industrial Experience.
The Use of Zachman Framework Primitives for Enterprise Modeling
Architectural Design Principles. Outline  Architectural level of design The design of the system in terms of components and connectors and their arrangements.
Software Issues Derived from Dr. Fawcett’s Slides Phil Pratt-Szeliga Fall 2009.
Lecture Nine Database Planning, Design, and Administration
Systems Engineering Foundations of Software Systems Integration Peter Denno, Allison Barnard Feeney Manufacturing Engineering Laboratory National Institute.
Foundations This chapter lays down the fundamental ideas and choices on which our approach is based. First, it identifies the needs of architects in the.
David Harrison Senior Consultant, Popkin Software 22 April 2004
1212 Management and Communication of Distributed Conceptual Design Knowledge in the Building and Construction Industry Dr.ir. Jos van Leeuwen Eindhoven.
Course Instructor: Aisha Azeem
Software Architecture premaster course 1.  Israa Mosatafa Islam  Neveen Adel Mohamed  Omnia Ibrahim Ahmed  Dr Hany Ammar 2.
Framework for Model Creation and Generation of Representations DDI Lifecycle Moving Forward.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Copyright © 2013 Curt Hill The Zachman Framework What is it all about?
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
SOFTWARE DESIGN.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
Drexel University CS 451 Software Engineering Winter Yuanfang Cai Room 104, University Crossings
Ocean Observatories Initiative Data Management (DM) Subsystem Overview Michael Meisinger September 29, 2009.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Proposed NWI KIF/CG --> Common Logic Standard A working group was recently formed from the KIF working group. John Sowa is the only CG representative so.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
Software Design Process
Cognitive Science and Biomedical Informatics Department of Computer Sciences ALMAAREFA COLLEGES.
STEP Tutorial: “ Fundamentals of STEP” David Briggs, Boeing January 16, 2001 ® PDES, Inc NASA STEP Workshop step.nasa.gov.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Achieving Semantic Interoperability at the World Bank Designing the Information Architecture and Programmatically Processing Information Denise Bedford.
STEP MANAGEMENT OVERVIEW STEP ARCHITECTURE Module 4 Estimated Viewing Time: 60 Minutes.
Chapter 6 Guidelines for Modelling. 1. The Modelling Process 1. Modelling as a Transformation Process 2. Basic Modelling Activities 3. Types of Modelling.
Documenting Software Architectures. Outline  Introduction  Uses of Architectural Documentation  Views  Choosing the Relevant Views  Documenting a.
1 Developing an Ontology of Ontologies for OOR Ontology Summit 2008 April 28-29, 2008 Michael Gruninger and Pat Hayes.
Application of the ISO for BIM Xenia Fiorentini, Engisis.
Architecture Ecosystem SIG March 2010 Update Jacksonville FL.
Developing an IDM Information Delivery Manual Part 1. Industry Workgroup Training, Creating IDMs Alliance NA 2010 Dianne Davis, NA-IDM Coordinator Jan.
SOFTWARE DESIGN & SOFTWARE ENGINEERING Software design is a process in which data, program structure, interface and their details are represented by well.
By Jeremy Burdette & Daniel Gottlieb. It is an architecture It is not a technology May not fit all businesses “Service” doesn’t mean Web Service It is.
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
Dr. Ir. Yeffry Handoko Putra
Building Enterprise Applications Using Visual Studio®
SQA project process standards IEEE software engineering standards
SQA project process standards IEEE software engineering standards
The GEMBus Architecture and Core Components
ONAP Integration Through Information and Data Modeling
Part 3 Design What does design mean in different fields?
Exploring Application Lifecycle Management and Its Role in PLM
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Chapter 2 Database Environment Pearson Education © 2009.
Ontology Reuse In MBSE Henson Graves Abstract January 2011
Database Environment Transparencies
UML profiles.
Ontology-Based Approaches to Data Integration
Presentation transcript:

1 Adaptive Data Access Interface for STEP Model Repositories- support AEC product lifecycle management Frank Wang Donghoon Yang Chuck Eastman

2 AEC (Architecture, Engineering and Construction) PLM integration in AEC industry Projects are for single products that may exist for centuries Supports one-of-a-kind projects – mass customization Developed by teams that come together for the single project Must operate in varied environments

3 Problems Integration impediments across multiple domains Diverse Std. Organizations, practices, usages, schemas Redundant knowledge and concept representations Unfamiliar taxonomy across disciplines Expensive implementation Desire module-based PLM managerial applications General contractor Architect Client subcontractor IFC

4 Scope Modeling context independent Utilizing implementation for PLM integral applications Increase knowledge reusability Multiple standards/models integration

5 Adaptive Representation Modules Combination usage of adaptable presentation modules Geometry (3D) + TemporalGeometry (2D) + Functional Geometry + Functional Geometry + Functional+ Behavior + Temporal

6 Framework and Architecture Framework and architecture Three layers architecture  Existing STEP repositories  Ontology-based semantic model  PLM Managerial applications Ontology-based semantic language Adaptable data access interface

7 Semantic Language Goal Capture modeling concepts and structures Embed semantic and ontology Provide a product data specific modeling language with richer semantic for rigorous data representation Ontology languages from previous work TOVE (TOronto Virtual Enterprise, University of Toronto) Enterprise Ontology OIL (Ontology Interchange Language) KIF (Knowledge Interchange Format) PIF (Process Interchange Format) KACTUS (modeling Knowledge About Complex Technical systems for multiple USe)

8 Criteria for the language reinventing Fundamental criteria Correct purposes Support richer semantic constructs Support complex engineering Required new language constructs Distinctive language (entity & relation) constructs Support referencing external languages Support additional identity and unity

9 Basic constructs of the language Relation Conceptual Object (Entity) Representation Environment setting (unit, dimension)

10 Adaptive Engineering Data Interface Adaptive module-based data access interface, allowing application to be self-tailoring for different PLM integration tasks Modularized presentations: geometry, temporal relations, topological functional relations and general properties Simple implementation Great knowledge reusability

11 Interface Structure example

12 Summary Current Achievement Acknowledgment