Flexibility of Data-Driven Process Structures

  • Dominic Müller
  • Manfred Reichert
  • Joachim Herbst
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4103)


The coordination of complex process structures is a fundamental task for enterprises, such as in the automotive industry. Usually, such process structures consist of several (sub-)processes whose execution must be coordinated and synchronized. Effecting this manually is both ineffective and error-prone. However, we can benefit from the fact that these processes are correlated with product structures in many application domains, such as product engineering. Specifically, we can utilize the assembly of a complex real object, such as a car consisting of different mechanical, electrical or electronic subcomponents. Each sub-component has related design or testing processes, which have to be executed within an overall process structure according to the product structure. Our goal is to enable product-driven (i.e., data-driven) process modeling, execution and adaptation. We show the necessity of considering the product life cycle and the role of processes, which are triggering state transitions within the product life cycle. This paper discusses important issues related to the design, enactment and change of data-driven process structures. Our considerations are based on several case studies we conducted for engineering processes in the automotive industry.


State Transition Data Object Product Life Cycle Process Structure Process Execution 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Müller, D., Herbst, J., Hammori, M., Reichert, M.: IT support for release management processes in the automotive industry. In: Dustdar, S., Fiadeiro, J.L., Sheth, A.P. (eds.) BPM 2006. LNCS, vol. 4102, pp. 368–377. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  2. 2.
    Aalst, W., Weske, M., Grünbauer, D.: Case handling: A new paradigm for business process support. DKE 53(2), 129–162 (2005)CrossRefGoogle Scholar
  3. 3.
    Aalst, W., Berens, P.J.S.: Beyond workflow management: Product-driven case handling. In: GROUP, pp. 42–51 (2001)Google Scholar
  4. 4.
    Reijers, H., Limam, S., Aalst, W.: Product-based workflow design. Management Information Systems 20(1), 229–262 (2003)Google Scholar
  5. 5.
    Mentink, R., Wijnker, T., Lutters, D., Kals, H.: Supporting manufacturing environments (2002)Google Scholar
  6. 6.
    Beuter, T., Dadam, P., Schneider, P.: The WEP model: Adepquate workflow-management for engineering processes. In: ECEC (1998)Google Scholar
  7. 7.
    Jäger, D., Schleicher, A., Westfechtel, B.: AHEAD: A graph-based system for modeling and managing development processes. In: Münch, M., Nagl, M. (eds.) AGTIVE 1999. LNCS, vol. 1779, pp. 325–339. Springer, Heidelberg (2000)CrossRefGoogle Scholar
  8. 8.
    Crnkovic, I., Asklund, U., Dahlqvist, A.P.: Implementing and Integrating Product Data Management and Software Configuration Management. Artech House Publishers (2003), ISBN 1-58053-498-8Google Scholar
  9. 9.
    WFMC: Workflow reference model. Technical report, Workflow Management Coalition, Brussels (1994)Google Scholar
  10. 10.
    Reichert, M., Dadam, P.: ADEPTflex: Supporting dynamic changes of workflow without loosing control. JIIS 10(2), 93–129 (1998)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Dominic Müller
    • 1
    • 2
  • Manfred Reichert
    • 1
  • Joachim Herbst
    • 2
  1. 1.Information Systems GroupUniversity of TwenteThe Netherlands
  2. 2.Dept. REI/IDDaimlerChrysler AG Research and TechnologyGermany

Personalised recommendations