PARKING SYSTEM MODELLING

of Mall Ambassador

Group 7
Anindya Alfi Septyanti (1306448110)
Anggi Hazella (1306370051)
Felisa Fitriani (1306369945)
Nadila Aristiaputri (1306393023)
Natasya Sheba S (1306370146)
Timotius Alfin (1306409633)

Dosen Pembimbing : Arry Rahmawan, ST, MT

 2

Mall Ambassador

Capacity
360 parking spots.
Location
Jl. Prof. Dr. Satrio No. 14,
Kuningan, Jakarta Selatan,
Banten 15810, Indonesia

Working Hours
10.00 – 22.00

Parking Lot
Has 3 basement levels of
parking lot.
 3

Mall Ambassador is one of the most favorite place for people in

the terms of buying electronics and shopping clothes. Among other
malls and shopping centers that also sell variety of electronics,
Mall Ambassador gives more affordable prices than other places.
Branded cheap clothes can also be found here.
 4

Formal System Modelling Methods

1 2 3 4 5 6

Problem Model Data Collection and Model Construction Validation and Project Repor t and
Formulation Conceptualization Analysis Verification Presentation
Problem Formulation
 6

Problem Statement

With such high visitors coming to Mall

Ambassador and many of them drive cars,
this Mall only provides small spaces for
parking – only 360 parking spots available
– causing a queue when entering the parking
spot and difficulties in finding the parking
spot, especially on peak time.
 7

Objectives

Make the model based on the data we

obtained from observation. Based on the
model we can conclude whether the
parking system of Mall Ambassador is
already optimum and met the criteria that
had given previously.
Model Conceptualization
9
Data Collection and Analysis
 11

Step of Data Collection

Source of data

Determining data Analyze the data

requirement using software
 12

Data Requirement
What do we need to do simulation?

Arrival time Duration time at the Mall Distribution

Arrival rate Number of servers Pattern of parking area

Service time Working hour Quantity of parking area

Searching time Peak hour

 13

Resource of Data
Where are the data come from?

Personal Observation Personal Interviews

System Documentation
We did personal observation
We made a documentation of We interviewed Mr. Zaeni as
such as direct observation and
layout and quantity parking Head of Parking Area at
made a questionnaire
area Ambassador Mall
 14

Observation

Place Date Time

Mall Ambassador Jakarta 26 September 2015 10.00 am – 10.00 pm
 15

Result of Data Observation

 16

Data Processing in Observation

Number  of  Car
300
255
228
We observed from 10.00 am 250
195 187
200
until 22.00 (12 hours), then we 150 131
158
144
127
processed data to determine 100 83 79
66 Arrival  Rate
peak hours in Ambassador Mall. 50
35

The result is from 11.00-17.00 0

is peak hours in Ambassador

Mall
 17

Data Processing in Observation

Service  Time  in  P eak  Hour Inter  Arrival  Time  in  Peak  Hour
Arrival  Rate  in  P eak  Hour  
8.00 7.20
7.00 6.24 30.00
300 5.44 22.76 24.95
250 187 6.00 25.00
158 5.00 15.79 18.44
200 255 144 avg  arrival   5.40 5.51 5.84 20.00 avg  inter  
150 228 4.00
195 rate 3.00 avg   service   15.00 19.04 arrival  t ime  
100 2.00 time   10.00 14.07
50 1.00
0 0.00 5.00
0.00
 18

Spreadsheet
 19

Data Analysis in Observation

Arrival Rate Service Time

 20

Data Analysis in Observation

Searching Time Inter Arrival Time

 21

Questionnaire
The questionnaire consists of:

01 How often do they go to Mall Ambassador

02 Time interval in entering the Mall Ambassador

03 Duration of parking time in Mall Ambassador

04 The length of waiting time in queue

 22

Result of Questionnaire

Questionnaire Arrival  Time Time  Duration

Arrival  Time
60
10.00-­‐1 2.00 20 50
12.00-­‐1 5.00 44 45 44 50 50
40
15.00-­‐1 8.00 21 40
35
18.00-­‐2 1.00 8
30 30
27
25
Time  Duration 21 20
20 20 16
1-­‐2  j am 27 15 10
2-­‐3  j am 50 10
8 0
>3  jam 16 5
1-­‐2  jam 2-­‐3  jam >3  jam
0
10.00-­‐12.00 12.00-­‐15.00 15.00-­‐18.00 18.00-­‐21.00
 23

Data Analysis in Questionnaire

This distribution shows the

distribution of data from
questionnaire is normal
distribution.
1 3 9 8 5
2 4 7 6
 25

Attachments

Form Online Questionnaire

Model Construction
 27

Model Construction

1 2 3 4 5 6

Put a layout as Build location and Build Entities and Build Process and Build Arrivals and Run the model
background for the Location Logic for Entities Logic for the Process Logic for Arrival Logic for
model the model model the model the model
Entrance
Queue
Locket
Parking Area
Exit
 28

Put a layout as background for the model

 29

Build Location and Location Logic for the model

 30

Build Location and Location Logic for the model

 31

Build Entities and Entities Logic for the model

 32

Build Process and Process Logic for the model

 33

Build Arrivals and Arrivals Logic for the model

 34

Run the model

Click to watch the video of model simulation

Validation and Verification
 36

Validation
We use these following techniques
for validating the model:
01 Watching the animation

02 Comparing with other models

03 Conducting degeneracy and

extreme condition test

04 Performing sensitivity
analysis

05 Running trace
 37

Watching the Animation

After the model was done, we have to

run the model to see whether the model
is correct or not.
 38

Comparing with Other Models

We have to make sure the model is correct by

comparing with the excel data. After we run the model,
we can see the statistic, if the number is the same with
the excel calculating, then our model is finally correct
39
Conducting Degeneracy and
40

Extreme Condition Test

In conducting degeneracy and extreme condition test
we can change the arrival rate. Assume that we
change the arrival rate to 0 (zero) following with the
accuracy, then the result should be:

No car arrive in the entry queue. If

it is happened, then our model is
finally correct
 41

Performing Sensitivity Analysis

In performing sensitivity analysis, we can try to change the service

time, if we change into the smaller number of service time there
will be no queue, if we change into bigger number there will be
queue. After we try, our model adjust with the changing of
numbers, it means the model is correct
 42

Running Trace
Running trace will show all of the event on the discrete model.

There is no error on our model, based on the trace results

 43

Verification
In order to verified the model, we use some techniques:

01 Reviewing model code

02 Checking for reasonable input

and output

03 Watching the animation

04 Using trace and debugging

facilities
 44

Reviewing Model Code

 45

Checking for Reasonable Input and Output

The number of entry car is same as the number of exit car and
the number of car at the current location, so input and output
are reasonable.
 46

Watching the Animation

We can know that the model is correct if the model is running
until it’s done correctly and without bug.
 47

Using Trace and Debugging Facilities

We use trace and debugging facilities to make sure we build the
model correctly implemented with good input and structure.

There is no error on our model, based on the trace results. There is no

debugging in our model.
Results and Recommendations
 49

Results
Our Result is: 01 The peak time is at 11.00-17.00
-Arrival Rate at peak Time:

02
P(195;41.8) sec
-Service Time at peak Time:
L(5.94;0.69) sec

03 Average waiting time in

queue: 0.15 sec

04 Average cars in queue: 0.01

The data from spreadsheet is

05 same with the data from

promodel
 50

Recommendation
Our Recommendation is:

01
The capacity should be
increased by 25 parking slot to
meet the requirement.

02
The number of ticket locket is
enough to meet the
requirement.
THANK YOU!