Adaptive Data Access Interface for STEP Model Repositories support AEC product lifecycle management

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

• IFC

• General contractor
• Architect
• Client

• subcontractor

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) Temporal

• Geometry (2D) Functional

• Geometry Functional Behavior Temporal

• Geometry Functional

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