diff --git a/D01 Integration of INSEL Models and SimStadt/01 Background_and_Definitions.adoc b/D01 Integration of INSEL Models and SimStadt/01 Background_and_Definitions.adoc
index b53ed2da01e4d77bd26f7b93ac2d13eda9cf0511..407a2f288190117628027f44e7cd0fd9935183c8 100644
--- a/D01 Integration of INSEL Models and SimStadt/01 Background_and_Definitions.adoc	
+++ b/D01 Integration of INSEL Models and SimStadt/01 Background_and_Definitions.adoc	
@@ -13,9 +13,9 @@ The definition of the scope of a WFS is up to the user. Some predefined WFSs as
 
 In general, a workflow step in SimStadt consists of a functional part F, connector to workflow communication part C and a human computer interaction part HCI.
 
-
- 
-Figure 1: the three components of a SimStadt Workflow Step
+[#img_WFS,reftext='{figure-caption} {counter:figure-num}']
+.The three components of a SimStadt Workflow Step
+image::img/WFS.png[align="center"]
 
 The functional part of the Workflow step encapsulates the purpose of a particular workflow step. For example, the calculation of the volume of a building happens here. The functional part has to be independend of the communication between workflow steps as well as the HCI part. Why? Because a workflow step has to have the same functionality in the SimStadt desktop application and as Web Services. In addition, the workflow can be executed as a batch process and as an interactive system.