Differences

This shows you the differences between two versions of the page.

--- en:handbuch:kapitel_2:2.01.16_basic_-_verkaufstrichter [2009/12/09 15:53]
admin
+++ en:handbuch:kapitel_2:2.01.16_basic_-_verkaufstrichter [2019/10/25 14:11] (current)
@@ Line 1: / Line 1: @@
 [[2.01.15_basic_-_kampagnenziel|{{|previous}}]] [[en:handbuch:handbuch|{{|Home}}]] [[2.01.17_basic_-_entscheidungstraeger|{{|next}}]]
-====== 2.01.16 Sales Pipeline======
+====== 2.01.15 Sales Pipeline======
@@ Line 8: / Line 8: @@
 **Tip:** For more on this subject see chapter [[en:handbuch:kapitel_3:3.11.04_das_kontaktsystem_-_crm |3.11.04 The Contact System]].
-{{:en:handbuch:kapitel_2:salespipeline.gif?direct}}
+{{:en:handbuch:kapitel_2:salespipeline1.png|}}
-{{:en:handbuch:kapitel_2:salespipeline2.gif?direct}}
 The form consists of the following elements:
@@ Line 15: / Line 14: @@
 On the "Main" tab:
+    * **Customer:** This field assigns to the corresponding contact the sales pipeline.
+    * **Employee:** This field specifies the publisher of the sales pipeline. The emplyees can be difined or changed in the dokument [[en:handbuch:kapitel_2:2.01.24_basic_-_mitarbeiter|Employee]].
     * **Number:** The element "Number" specifies distinctly the sales pipeline in System.
-    * **Date:** This field specifies the compilation/start date of the sales pipeline.
+    * **Reference:** The doposited reference types of the collection can be selected and defined in the field reference  (e.g. training, workshops, etc.).
-    * **Customer:** This field assigns the corresponding contact to the sales pipeline.
-    * **Employee:** This field specifies the publisher of the sales pipeline. The employee can be defined and modified in the document type Employee.
-    * **Reference:** The customer's, in the Collections (see Administration Guide) defined references (e.g. training, workshops, etc), can be assigned in the field Reference.
     * **Potential:** The in the Collections (see Administration Guide) defined gradation, regarding the quality of the business contact (e.g. A-contact, B-contact or C-contact) can be stored in the field Potential.
-    * **Need for Action:**  The in the Collections (see Administration Guide) defined gradation, regarding the need for action (e.g. low, significant or mandatory) can be stored in the field need for action.
+    * **SalesPhase:** The in the Collections (see Administration Guide) defined distribution phase(e.g. first contact, qualified contact, information material, presentation, offer, etc.) can be stored in the field distribution phase.
-    * **Sales Phase:** The in the Collections (see Administration Guide) defined distribution phase(e.g. first contact, qualified contact, information material, presentation, offer, etc.) can be stored in the field distribution phase.
+    * **NeedForAction:** The in the Collections (see Administration Guide) defined gradation, regarding the need for action (e.g. low, significant or mandatory) can be stored in the field need for action.
-    * **Offer:** The offer of the sales pipeline can (e.g. starting from the distribution phase "Offer") be assigned here.
+    * **SalesProbability:** The offer probability of the distribution activity is stored here.
-    * **Sales Probability:** The offer probability of the distribution activity is stored here.
+    * **Hours:** In service projects the potential work/input in hours can be stored here.
-    * **Incoming Order:** The time of the probable incoming order of the distribution activity is stored here.
+    * **BilledVolume:** In service projects this value is the product of the work/input in hours and the hourly rate.
-    * **Work/Effort in Hours:** In service projects the potential work/input in hours can be stored here.
+    * **Budget:** The total budget of the distribution activity is stored here.
-    * **Hourly Rate:** The potential hourly rate with service products can be stored here.
+    * **P.O. date:** This field specifies the creation date of the sales pipeline.
-    * **Calculated Order Value:** In service projects this value is the product of the work/input in hours and the hourly rate.
+    * **Price:** The potential hourly rate with service products can be stored here.
-    * **Order Value:** The potential order value of the distribution activity is stored (or calculated) here. In the example, an order of EUR 40.000,00 to the possibility of 75% is calculated in the beginning of February 2009.
+    * **VolumeOfSales:** The potential order value of the distribution activity is stored (or calculated) here. In the example, an order of EUR 40.000,00 to the possibility of 75% is calculated in the beginning of February 2012.
-    * **Budget:** The total budget of the distribution activity is stored here.
+    * **WeightedBudget:**
-    * **Comment:** Comments concerning the sales pipeline can be entered here.
+    * **Note:** Notes concerning the sales pipeline can be entered here.
-    * **Decision-Board:** As many decision-makers as needed, including their settings for the sales pipeline, can be stored here. These persons and their settings can be defined in the document decision-maker.
+    * **DecisionBoard:** As many decision-makers as needed, including their settings for the sales pipeline, can be stored here. These persons and their settings can be defined in the document decision-maker.
-{{:en:handbuch:kapitel_2:salespipeline3.gif?direct}}
+{{:en:handbuch:kapitel_2:salespipeline2.png|}}
 On the "Project Fields " tab:
     * **Project Name:** This field identifies the upcoming project.
+    * **Project Time Span from/to:** The field "from" defines the prospective project begin and the field "to" defines the prospective project end of the potential project.
+    * **Priority:** This field specifies the priority of the potential project.
     * **Unit:** In this field the responsible unit for the upcoming project is specified (usually a location or a department. Units can be modified in the **Unit** form.
     * **Project Manager:** This field specifies the potential project manager for the upcoming project.
-    * **Priority:** This field specifies the priority of the potential project.
+    * **Project category:**
-    * **Project Time Span from/to:** The field "from" defines the prospective project begin and the field "to" defines the prospective project end of the potential project.
+    * **Product:**
+    * **Strategy:**
+{{:en:handbuch:kapitel_2:salespipeline3.png|}}
+On the "Skills" tab:
+    * **IT skills:**
+    * **Other IT skills:**
+    * **Language skills:**
+    * **Other language skills:**
+    * **Soft skills:**

Projectile-Online-Handbuch

User Tools

Site Tools

Differences

Page Tools