Skip to main content
Article thumbnail
Location of Repository

A metamodel to annotate knowledge based engineering codes as enterprise knowledge resources

By Pablo Bermell-Garcia


The encoding of Knowledge Based Engineering (KBE) software applications is becoming a prominent tool for the automation of knowledge intensive tasks carried out using Computer Aided Design (CAD) technology. However, limitations exist on the ability to manage the engineering knowledge models embedded in these executable KBE applications. This research proposes a metamodel to annotate encoded KBE applications. Resulting from the annotation, XKMs become explicit knowledge resources whose content can be better accessed and managed. The attachment of metadata to data sets in enterprise repositories is a necessary step to identify and index them so they can be queried, browsed and changed. The sophistication of metadata models for these data “items” ranges from the simple indexing using numbers to more sophisticated representations describing their context information (i.e. author, creation date, etc.), their internal structure and their content. Current engineering data repositories like Product Data Management and Product Lifecycle Management systems offer predefined metamodels to annotate a range of engineering data items including CAD files or special types of documents. At the moment, there is no metadata model specifically designed to annotate KBE codes. In this situation, an undifferentiated metadata model needs to be used for XKMs. However, in this case the only information retained by the system about them would be context metadata. Once an instance of the metadata is attached to an XKM, it can be used as its identifier within an enterprise data repository. The proposed metamodel contains abstract entities to annotate XKMs. The resulting descriptive model for an XKM pays attention to its internal structure and its operation at different levels of granularity. The particular design of the proposed metamodel positions it at a level of abstraction between non executable domain knowledge models and executable KBE applications. This design choice is made to support the use of the metadata not only as an informative model but also as an executable one. The achievement of this target is becoming possible through the emergence of semantic modelling standards that allow the description of data models independently from the language of implementation. Using this approach, the generation of code and metadata is made automatically using mapping rules resulting from the semantic agreement between models and specific syntax rules. The immediate application of the developed metamodel is to annotate XKMs within PLM systems. The approach shall contribute not only to systematically store instances of XKMs but also to manage the lifecycle of the engineering knowledge encoded within them. The proposed representation provides a more comprehensive approach for non KBE language experts to understand the code. On this basis, the change on the metamodels can be automatically traced back to the code and vice-versa. During the research, evidence has been gathered from the community of KBE technology users and vendors on the need to support this research effort. In the long term, the research contributes to the use of PLM systems as a platform for engineering knowledge management

Publisher: Cranfield University
Year: 2007
OAI identifier:
Provided by: Cranfield CERES

Suggested articles


  1. (2008). A standardized set of extensions and constraints that tailors UML to particular use. dtc/2005-09-11
  2. (2008). Architecture (MDA) - An approach to IT system specification that separates the specification of functionality from the specification of the implementation of that functionality on a specific technology platform. dtc/2005-09-11 OMG RFP April 23,
  3. Are you aware of the OMG’s Model Driven Architecture and the software standards associated with it? X If affirmative, which ones do you know?
  4. (2005). Depends upon the amount and type of heterogeneity that is present. However, a type of interchange that uses ‘web semantics’ might help handle the disparity. Has the OMG seen progress in this area? “KBE services for PLM” RFP feedback questionnaire
  5. (2005). KBE services for PLM” RFP feedback questionnaire
  6. (2005). KBE services for PLM” RFP feedback questionnaire October
  7. (2005). Related to #27, the need for an EKL as well. Is MDA sufficient? Or will it provide an extensive (and extensible) framework for handling roles and behaviours? “KBE services for PLM” RFP feedback questionnaire October
  8. see this proposal as very important to future developments in, and interoperability between KBE tools within a PLM environment.
  9. standard functionalities (*) Authentication and start up of a session Start node identification Browsing part structure Browsing document structure Download single digital file Download of product structure metadata Metamodel
  10. (2002). The questionnaire has been created using Microsoft Word
  11. This questionnaire is stored as an OMG document in the OMG’s document server. The URL to access the questionnaire is:
  12. (2005). to RFP Editors: Append additional appendices if needed here and update the list and brief description of appendices in Chapter 1.
  13. (2000). What is the size of the organisation that you belong to? Less than 500 employees. Less than 1000 employees. Less than doi
  14. (2000). What is the size of the organisation that you belong to? X Less than 500 employees. Less than 1000 employees. Less than doi
  15. (2005). Would you be interested in becoming part of the submission team for the “KBE services for PLM” OMG standard? (Notice that only “contributing”, “domain” and “platform” OMG members can become standard submitters). x Comments:

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.