Car acquisition - Revision history

Mico00: /* Conclusion */

2021-01-20T18:22:40Z

‎Conclusion

Mico00: /* Results */

2021-01-20T17:50:52Z

‎Results

Mico00: v7

2021-01-19T21:46:14Z

Mico00: v6

2021-01-19T21:26:32Z

Mico00: v6

2021-01-19T21:13:17Z

Mico00: v5

2021-01-19T21:09:29Z

Mico00: v4

2021-01-19T20:48:35Z

Mico00: v3

2021-01-19T20:27:54Z

Mico00: v2

2021-01-19T19:59:31Z

Mico00 at 19:53, 19 January 2021

2021-01-19T19:53:40Z

@@ Line 162: / Line 162: @@
 =Conclusion=
 =Code=
 [[File:Car-aquission-model.spm]]

← Older revision		Revision as of 17:50, 20 January 2021
Line 136:		Line 136:

	=Results=		=Results=
		+
		+	In first run, car delivery was set to 20 cars a day. This resulted in unfulfilled demand, as customers remained in the system in the car transfer:
		+
		+	<pre>
		+	Total Remaining Total Total
		+	Activity Names Entity Names Accepted In Act. Exited Not Processed
		+	car transfer11 car 8738 0 8738 0
		+	car transfer11 customer driving c 0 0 8738 0
		+	car transfer11 customer 10598 1860 8738 0
		+	</pre>
		+
		+	On second run, car delivery was planned for 30 cars per day to even out the excess demand. This resulted in a different outcome, where cars remained in the system:
		+
		+	<pre>
		+	Total Remaining Total Total
		+	Activity Names Entity Names Accepted In Act. Exited Not Processed
		+	car transfer11 car 12859 2556 10303 0
		+	car transfer11 customer driving c 0 0 10303 0
		+	car transfer11 customer 10303 0 10303 0
		+	</pre>
		+
		+	Car driving is 0 on accepted in these results, as they were on the output of this activity. What is more interesting, SIMPROCESS sees the entities which were input for the assembly (customer and car) on the output, however these entities were consumed in the process of assembly.
		+
		+	On additional (manual) runs these results were similar - either too many cars, or too little customers. 25 cars per day seemed like the optimum for this simulation.

	=Conclusion=		=Conclusion=

@@ Line 82: / Line 82: @@
 [[File:Low-inqury.PNG]]
 ==Lower level - car delivery==
 [[File:Low-car-delivery.PNG]]
 ===Branch===
-In car delivery process,car and customer are both input entities. for this reason, they must be firstly split
+In the car delivery process, car and customer are both input entities. for this reason, they must be firstly split
 ===Delay - car wash===
-The car gets a quick outside wash before handed to the customer. It takes the external company about 2 hours to do so.
+The car gets a quick outside wash before handed to the customer. It takes the external company for about 2 hours to do so.
 ===Assemble - car transfer===

@@ Line 86: / Line 86: @@
 [[File:Low-car-delivery.PNG]]
 ==Lower level - car return==
 [[File:Low-car-return.PNG]]

@@ Line 23: / Line 23: @@
 The Model is divided into two layers. The first layer incorporates the basic activities, and also three subprocesses which are on the lower level.
-==higher level==
+==Higher level==
 At the higher level, two entity generators are located, 10 other activities and the three subprocesses mentioned previously.
@@ Line 79: / Line 79: @@
 To archive the most satisfaction, the car must be delivered clean and ready, so after it is returned, the car is given a wash, which is processed by an external company and takes 3 hours.
-==lower level - inquiry==
+==Lower level - inquiry==
-==lower level - car delivery==
-==lower level - car return==
+[[File:Low-inqury.PNG]]
 =Results=
@@ Line 88: / Line 96: @@
 =Code=

@@ Line 45: / Line 45: @@
 ===Branch - visit===
-At the start of the customer introduction to the business process, the customer himself must create the inquiry, so that the company can walk him down the conversion tunel, closer to a successful deal. The interesting part is, that about 10% of visits actually create an initial inquiry. the rest of the
+At the start of the customer introduction to the business process, the customer himself must create the inquiry, so that the company can walk him down the conversion funnel, closer to a successful deal. The interesting part is, that about 10% of visits actually create an initial inquiry. The rest of the visits are customers that leave the website without any desire to drive cars of the company.
 =Results=

@@ Line 17: / Line 17: @@
 As a tool to model the system and then analyze different scenarios, SIMPROCESS was used. There are multiple reasons for this, mainly that the system is an array of intertwined processes where at the start there is a customer which wants a car, and at the end, there is a customer that returned the car and has a pleasant experience the whole time. A hierarchical modelling tool that combines process mapping and discrete-event simulation surely find usage for this case.
-As the company currently works in year-ahead planning, the simulation was set to run in a one-year window, from 1.1.2021 until 1.1.2022. the data applied in the model are mostly based on outputs from systems the company uses daily, and so the values are based on datasets with a certain degree of accuracy. Some of the data come from plans for the following year - this includes the car delivery schedule and personal changes in the company.
+As the company currently works in year-ahead planning, the simulation was set to single run in a one-year window, from 1.1.2021 until 1.1.2022. the data applied in the model are mostly based on outputs from systems the company uses daily, and so the values are based on datasets with a certain degree of accuracy. Some of the data come from plans for the following year - this includes the car delivery schedule and personal changes in the company.
 =Model=
@@ Line 31: / Line 31: @@
 [[File:High.PNG]]
-===Generator - customer ===
+To explain the model in detail, firstly the generators will be described, and then all the other activities through the red path of the model - this means that if the entity goes off the red path, its outcome will be described on last red path activity. each lower level subprocess will be explained in its separate chapter.
-===Generator - car ===
+===Generator - customer===
 =Results=

← Older revision		Revision as of 20:27, 19 January 2021
Line 22:		Line 22:

	The Model is divided into two layers. The first layer incorporates the basic activities, and also three subprocesses which are on the lower level.		The Model is divided into two layers. The first layer incorporates the basic activities, and also three subprocesses which are on the lower level.
		+
		+	==higher level==
		+
		+	At the higher level, two entity generators are located, 10 other activities and the three subprocesses mentioned previously.
		+
		+	The customer flow is merged with car flow at the car delivery, where also returned cars are reused. This merge is then split when the car is returned, and the customer leaves the system, and the car is reused is usable.
		+
		+	[[File:High.PNG]]
		+
		+	===Generator - customer ===
		+
		+	===Generator - car ===

	=Results=		=Results=

@@ Line 1: / Line 1: @@
-Introduction
+So upon choosing the car he dreams about, the customer fills the inquiry form, signs some papers and leaves with the car.
-'''WIP'''
+Well, sort of. On the background, there are many steps that ensure customer happiness with the service, and also the whole process which ensures that the customer is reliable enough to temporarily leave him with a car - this car might be worth hundreds of thousands CZK, or even one or two million CZK.
-=Problem definition=
+This paper describes problems of the current setup and analyzes potential bottlenecks of the system. Worth mentioning is also the capabilities of the system, required to predict the necessary steps for the future development of the company.
 =Method=
 =Model=