Car acquisition

From Simulace.info
Revision as of 20:53, 19 January 2021 by Mico00 (talk | contribs)
Jump to: navigation, search

When a regular person wants to rent or lease a car, he usually does not usually know how much work does it take on the background. From his point of view, he has the need to use a car, so he decides whether to buy one or lease one if this is a long term need. In such cases, a long term solution is needed.

So upon choosing the car he dreams about, the customer fills the inquiry form, signs some papers and leaves with the car.

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

As mentioned in the introduction, there are many steps on each part of the system, and that is the customer and the lessor. Some of these steps need both parties to cooperate (exchange of documents, car delivery) or are cared about by one or another party. The lessor can wash the car, and the customer for example uses the car.

Leasing a car is basically a car-subscription model. Instead of the common approach where one buys a car and scrapes it after ten years, or even the approach of buying a used one and selling it in few months, a subscription is something that many companies choose over one-time payments. This way people are not forced to save money or to get into debt, but they can give part of their monthly income to consume a product. The car industry is not common for such new-school approaches, but time goes on, and so does the trends.

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

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 modeling 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.

Model

Results

Conclusion

Code