Datenbank-Spektrum

, Volume 13, Issue 3, pp 189–199 | Cite as

On the Integration of Electrical/Electronic Product Data in the Automotive Domain

Challenges, Requirements, Solutions
  • Julian Tiedeken
  • Manfred Reichert
  • Joachim Herbst
Schwerpunktbeitrag

Abstract

The recent innovation of modern cars has mainly been driven by the development of new as well as the continuous improvement of existing electrical and electronic (E/E) components, including sensors, actuators, and electronic control units. This trend has been accompanied by an increasing complexity of E/E components and their numerous interdependencies. In addition, external impact factors (e.g., changes of regulations, product innovations) demand for more sophisticated E/E product data management (E/E-PDM). Since E/E product data is usually scattered over a large number of distributed, heterogeneous IT systems, application-spanning use cases are difficult to realize (e.g., ensuring the consistency of artifacts corresponding to different development phases, plausibility of logical connections between electronic control units). To tackle this challenge, the partial integration of E/E product data as well as corresponding schemas becomes necessary. This paper presents the properties of a typical IT system landscape related to E/E-PDM, reveals challenges emerging in this context, and elicits requirements for E/E-PDM. Based on this, insights into our framework, which targets at the partial integration of E/E product data, are given. Such an integration will foster E/E product data integration and hence contribute to an improved E/E product quality.

Keywords

Product data integration Common integration ontology 

Notes

Acknowledgements

This work has been conducted within the PROCEED6 project funded by Daimler AG.

References

  1. 1.
    ATESST (2008) EAST-ADL2 specification. Tech rep Google Scholar
  2. 2.
    Aumueller D, Do HH, Massmann S, Rahm E (2005) Schema and ontology matching with COMA++. In: Proc of the 2005 ACM SIGMOD international conference on management of data. ACM, New York, pp 906–908 CrossRefGoogle Scholar
  3. 3.
    AUTOSAR (2011) AUTOSAR methodology. Tech rep version 1.2.2, release 3.2, rev 0001 Google Scholar
  4. 4.
    AUTOSAR (2011) Technical overview. Tech rep version 2.2.2, release 3.2, rev 0001 Google Scholar
  5. 5.
    Baumgart A (2010) A common meta-model for the interoperation of tools with heterogeneous data models. In: MDTPI, Paris, France Google Scholar
  6. 6.
    Bestfleisch U, Herbst J, Reichert M (2005) Requirements for the workflow-based support of release management processes in the automotive sector. In: ECEC, pp 130–134 Google Scholar
  7. 7.
    Burmester S, Giese H, Niere J, Tichy M, Wadsack J, Wagner R, Wendehals L, Zündorf A (2004) Tool integration at the meta-model level: the Fujaba approach. Softw Tools Technol Transf 6:203–218 CrossRefGoogle Scholar
  8. 8.
    Chaudhuri S, Dayal U (1997) An overview of data warehousing and OLAP technology. ACM Sigmod Rec 26(1):65–74 CrossRefGoogle Scholar
  9. 9.
    Cooper R (1990) Stage-gate systems: a new tool for managing new products. Bus Horiz 33(3):44–54 CrossRefGoogle Scholar
  10. 10.
    Cruz IF, Antonelli FP, Stroe C (2009) AgreementMaker: efficient matching for large real-world schemas and ontologies. Proc VLDB Endow 2(2):1586–1589 Google Scholar
  11. 11.
    Ehrig M (2007) Ontology alignment: bridging the semantic gap. Springer, Berlin Google Scholar
  12. 12.
    Euzenat J, Shvaiko P (2007) Ontology matching. Springer, Heidelberg MATHGoogle Scholar
  13. 13.
    Forsberg K, Mooz H, Cotterman H (2005) Visualizing project management: models and frameworks for mastering complex systems. Wiley, New York Google Scholar
  14. 14.
    Freude R, Königs A (2003) Tool integration with consistency relations and their visualization. In: Proc workshop on tool-integration in system development (TIS 2003), pp 6–10 Google Scholar
  15. 15.
    Gonçalves RS, Parsia B, Sattler U (2011) Analysing multiple versions of an ontology: a study of the NCI thesaurus. In: Description logics Google Scholar
  16. 16.
    Halevy A, Rajaraman A, Ordille J (2006) Data integration: the teenage years. In: VLDB, pp 9–16 Google Scholar
  17. 17.
    Hallerbach A, Bauer T, Reichert M (2008) Managing process variants in the process life cycle. In: ICEIS (3-2), pp 154–161 Google Scholar
  18. 18.
    Hallerbach A, Bauer T, Reichert M (2010) Configuration and management of process variants. In: Rosemann M, von Brocke J (eds) Handbook on business process management, vol 1. Springer, Berlin, pp 237–255 CrossRefGoogle Scholar
  19. 19.
    International Organization for Standardization (2011) ISO/FDIS ISO 26262-2:2011: road vehicles—functional safety—part 2: management of functional safety Google Scholar
  20. 20.
    Kalfoglou Y, Schorlemmer M (2003) Ontology mapping: the state of the art. Knowl Eng Rev 18(1):1–31 CrossRefGoogle Scholar
  21. 21.
    Königs A, Schürr A (2006) Tool integration with triple graph grammars—a survey. Electron Notes Theor Comput Sci 148(1):113–150 CrossRefGoogle Scholar
  22. 22.
    Lenzerini M (2002) Data integration: a theoretical perspective. In: Proc of the twenty-first ACM SIGACT-SIGMOD-SIGART symposium on principles of database systems. ACM, New York, pp 233–246 CrossRefGoogle Scholar
  23. 23.
    Motik B, Patel-Schneider PF, Parsia B, Bock C, Fokoue A, Haase P, Hoekstra R, Horrocks I, Ruttenberg A, Sattler U et al. (2009) OWL 2 web ontology language: structural specification and functional-style syntax. W3C Recomm 27:17 Google Scholar
  24. 24.
    Mueller M, Hoermann K, Dittmann L, Zimmer J (2012) Automotive SPICE in practice: surviving implementation and assessment. Rocky Nook, Santa Barbara Google Scholar
  25. 25.
    Müller D, Herbst J, Hammori M, Reichert M (2006) IT support for release management processes in the automotive industry. In: BPM, pp 368–377 Google Scholar
  26. 26.
    Müller D, Reichert M, Herbst J (2008) A new paradigm for the enactment and dynamic adaptation of data-driven process structures. In: CAiSE, pp 48–63 Google Scholar
  27. 27.
    Noy N, Klein M (2004) Ontology evolution: not the same as schema evolution. Knowl Inf Syst 6(4):428–440 CrossRefGoogle Scholar
  28. 28.
    Pokraev S, Reichert M (2006) Mediation patterns for message exchange protocols. In: EMOI-INTEROP Google Scholar
  29. 29.
    Pokraev S, Quartel D, Steen MW, Reichert M (2006) Semantic service modeling—enabling system interoperability. In: I-ESA Google Scholar
  30. 30.
    Pratt MJ (2001) Introduction to ISO 10303—the STEP standard for product data exchange. J Comput Inf Sci Eng 1(1):102–103 CrossRefGoogle Scholar
  31. 31.
    Reichert M (2013) Collaboration and interoperability support for agile enterprises in a networked world: emerging scenarios, research challenges, enabling technologies. In: IWEI, pp 4–5 Google Scholar
  32. 32.
    Reichert M, Weber B (2012) Enabling flexibility in process-aware information systems: challenges, methods, technologies. Springer, Berlin CrossRefGoogle Scholar
  33. 33.
    Sheth AP, Larson JA (1990) Federated database systems for managing distributed, heterogeneous, and autonomous databases. ACM Comput Surv (CSUR) 22(3):183–236 CrossRefGoogle Scholar
  34. 34.
    SPEEDS Project (2009) SPEEDS L-1 meta-model: deliverable: rev 1.0.1. Tech rep, Information Society Technologies Google Scholar
  35. 35.
    Stamatis D (2003) Failure mode and effect analysis: FMEA from theory to execution. ASQ Press, Milwaukee Google Scholar
  36. 36.
    Tiedeken J, Herbst J, Reichert M (2013) Managing complex data for electrical/electronic components: challenges and requirements. In: BTW workshops, pp 141–150 Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Julian Tiedeken
    • 1
  • Manfred Reichert
    • 1
  • Joachim Herbst
    • 2
  1. 1.Institute of Databases and Information SystemsUlm UniversityUlmGermany
  2. 2.ITM Group Research & Product Development MBCDaimler AGBöblingenGermany

Personalised recommendations