1 / 22

Inducting Subcontractor Process Ontologies

Inducting Subcontractor Process Ontologies. 2003 Construction Research Congress March 21, 2003. William O’Brien Raja. R. A. Issa Rodrigo Castro-Ravent ó s Jaehyun Choi Joachim Hammer. Outline. SEEK project – context & motivation Ontology generation Induction approach Findings

macon
Download Presentation

Inducting Subcontractor Process Ontologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Inducting SubcontractorProcess Ontologies 2003 Construction Research Congress March 21, 2003 William O’Brien Raja. R. A. Issa Rodrigo Castro-Raventós Jaehyun Choi Joachim Hammer

  2. Outline • SEEK project – context & motivation • Ontology generation • Induction approach • Findings • Next steps

  3. Key Assumptions • Heterogeneity of legacy sources • Connections, schema, etc., vary widely • Standards-based approaches (e.g., IFC, aecXML) not a complete solution • Data is/will be accessible • Increasing use of on-line resources • Access layers at firm define security, permissions (i.e., directory services)

  4. Environment & Context supply chain/extended enterprise supplier sub/ supplier coordinator (CM, lead sub) sub/ supplier Firm Legacy Source supply chain analysis (e.g. scheduler) Extractor/ Translator Secure hosting infrastructure Decision/ Negotiation Support Tool SEEK

  5. SEEK Architecture domain expert SEEK Components Secure, value-added extraction of firm knowledge Analysis Module Knowledge Extraction Module Legacy data and systems Wrapper AM = robust mediation – knowledge composition, query analysis W = source connection and translation KEM = directs configuration during build-time; based on data reverse engineering methods

  6. Approaches to Ontology Design • Inspiration – individual effort • Induction – case studies • Deduction – domain principles, logic • Synthesis – merges separateontologies • Collaboration – multiple experts work together (Holsapple & Joshi 2002)

  7. Ontologies • Defined as a formal specification of a conceptualization (Gruber 1993) • Ontologies promote knowledge sharing and reuse • Ontologies generally either • Frame based (most AEC approaches) • Logic based

  8. Ontologies in AEC Arena • IFC, aecXML • Collaboration approach; synthesis for extensions • OCCS • Synthetic approach • Limited exploration of induction • Detailed process/information mapping pre-cursor to ontology induction • Wakefield et al 2001 • Shahid & Froese 1998 • Kosovac et al 2000

  9. Business Process Ontologies • TOVE, ARIS, PSL • Collaboration • Synthesis and deduction to cleanse – PSL in particular • O’CoMMA (Gandon 2001) • Induction of business models for multi-agent systems • Four steps: (1) scenario & data collection (2) translation to semi-formal abstractions (3) ontology development (4) navigation and use

  10. Induction Approach

  11. Miller Electric

  12. Protégé 2000 Implementation

  13. Lessons Learned

  14. Conclusions

  15. Practical IT Problems How do we deploy models (such as subcontractor resource allocation models) to support firm and supply chain operations? Many firms, each with their own computer system and business rules… …how do we get the data out of the firms?

  16. Thank you.Questions?

  17. Industry Involvement • CM Centex Rooney, several subs • Rinker Hall project, UF campus • Building a data testbed • Firms’ legacy dbs • Firms’ process models (how they use their data)

  18. Practical Problems How do we deploy models (such as subcontractor resource allocation models) to support firm and supply chain operations? Enable deployment of decision support tools across an extended enterprise (e.g., supply chain) composed of firms with varying levels of sophistication

  19. SEEK Purpose Enable deployment of decision support tools across an extended enterprise (e.g., supply chain) composed of firms with varying levels of sophistication Why is this hard? Currently need to manually code links between systems; not scalable How do you get the data out of the firms?

  20. Subcontractor Resource Allocation Hong-Long Chen Mohammad El-Mashaleh Luis Silva Bibo Yang, ISE Dr. Joe Geunes, ISE IT for Subs/S-C Mera Faddoul Jae-Hyun Choi Rodrigo Castro-Raventós, BCN Dr. Ray Issa, BCN Dr. Joachim Hammer, CISE Research Team

  21. SEEK & Process/Product Models Integrated Product/process App/view Product model (OO CAD) Decision support (process focus) user Product wrapper SEEK can work with product models to provide an integrated view that removes details of data representation from users

  22. SEEK Key Capabilities • Rapid configuration with limited set-up: SEEK can be rapidly configured to query a wide variety of legacy systems, removing burden of set-up and integration that exists with current techniques. • Connection to physically and semantically heterogeneous sources: SEEK can automatically discover data and knowledge in a wide variety of legacy sources. • Composition of knowledge: SEEK can compose answers to queries, extending the capabilities of underlying legacy sources. • Protection of source-specific, proprietary knowledge:SEEK establishes a layer between the source and end user, protecting details of source representation. Access is also set at the source level, further protecting privacy.

More Related