Representing Mechatronic Products in Interorganizational Information Systems

  • Joern Kaack
  • Joerg Leukel
  • Stefan Kirn
Part of the IFIP International Federation for Information Processing book series (IFIPAICT, volume 255)


Representing mechatronic products in interorganizational information systems requires means for capturing characteristics of this type of products. This role is fulfilled by mechatronic product models which are subject of this paper. A mechatronic product consists of three components: software, electronics, and mechanics. The challenge is that diverse interrelations between their components and with other products exist; these interrelations need to be considered in respective models. The problem of current modeling approaches, however, is that they either do not provide the required richness for expressing interrelations or focus engineering tasks only by describing the product behavior. We view mechatronic product models from a logistic perspective which allows us answering two questions: What is the scope of a mechatronic product model for interorganizational information systems? Which information is required in this model (i.e., determined by the goal of logistics)? We design a mechatronic product model from this perspective. We validate our model by studying an interorganizational scenario in an automotive supply chain.


Logistics operations Inter-organizational enterprise systems Product data management systems Product life cycle systems Supply chain management (SCM) 


  1. 1.
    M. Broy, Automotive Software Engineering, in 25th International Conference on Software Engineering (IEEE Computer Society: Los Alamitos, CA, 2003), pp.719–720.CrossRefGoogle Scholar
  2. 2.
    O. Larses, Modern Automotive Electronics from a Dependable Systems Perspective, Technical Report (Royal Institute of Technology: Stockholm, 2003).Google Scholar
  3. 3.
    S. Burmester, H. Giese, and M. Tichy, Model-Driven Development of Reconfigurable Mechatronic Systems with Mechatronic UML, in LNCS 3599 (Springer: Berlin 2005), pp.47–61.Google Scholar
  4. 4.
    M. Tiechem, M. Storm, M. Andreasen, and M.K.J. Callum, Product structuring — an overview, in Proc. of 11th International Conference on Engineering Design (1997).Google Scholar
  5. 5.
    G. Moncelet et al., Analysing a mechatronic system with coloured Petri nets, Intern. Journal of Software Tools for Technology Transfer. Volume 2, Number 2, pp.160–167, (1998).zbMATHCrossRefGoogle Scholar
  6. 6.
    D.J. Chen and M. Törngren, Towards A Framework for Architecting Mechatronics Software Systems, in Proc. of 7th IEEE International Conference on Engineering of Complex Computer Systems (IEEE Computer Society: Los Alamitos, Cam, 2001), pp.170–179.CrossRefGoogle Scholar
  7. 7.
    T. Männistö, H. Peltonen, T. Soininen, and R. Sulonen, Multiple abstraction levels in modelling product structures, Data & Knowledge Engineering. Volume 36, Number 1, pp.55–78, (2001).zbMATHCrossRefGoogle Scholar
  8. 8.
    T.K. Peng and A.J.C. Trap, A step toward STEP-compatible engineering data management: the data models of product structure and engineering changes, Robotics and Computer-Integrated Manufacturing. Volume 14, Number 2, pp.89–109, (1998).CrossRefGoogle Scholar
  9. 9.
    M. Hepp, Products and Services Ontologies: A Methodology for Deriving OWL Ontologies from Industrial Categorization Standards, International Journal on Semantic Web & Information Systems. Volume 2, Number 1, pp.72–99, (2006).Google Scholar
  10. 10.
    T. Lee, J. Shim, H. Lee, and S.G. Lee, A Pragmatic Approach to Model and Exploit the Semantics of Product Information, in LNCS 4244 (Springer: Berlin, 2006), pp.242–266.Google Scholar
  11. 11.
    J. Leukel, Standardization of Product Ontologies in B2B Relationships-On the Role of ISO 13584, in Proc. of 10th Americas Conference on Information Systems (AIS, 2004), pp.4084–4091.Google Scholar
  12. 12.
    S. Virtanen, Reliability in product design — Specification of dependability requirements, in Proc. of Annual Reliability and Maintainability Symposium (1998), pp.82–88.Google Scholar

Copyright information

© International Federation for Information Processing 2008

Authors and Affiliations

  • Joern Kaack
    • 1
  • Joerg Leukel
    • 1
  • Stefan Kirn
    • 1
  1. 1.Information Systems IIUniversity of HohenheimStuttgartGermany

Personalised recommendations