Ticketing and Concessions Areas

Code needs to be less then a 150 lines and done in GPSS/H

## Deliverables

**System Description:** The Refined Arts Theater intends to establish a branch operation in Cartsville. Based on data from a similar operation in another area with some adjustments because of population age differences, the management wants your company to develop a M&S analysis as part of the systems engineering analysis supporting the management decision making. The system boundary is drawn from the arrival of customers at the ticket purchase kiosk to the initial exit of customers into the viewing area. This area is described as the concession area. (The focus is on the initial seating activities; no concern is to be addressed to customers coming from the viewing area into the concessions area.) The concessions area, beginning with the ticket purchase kiosk and ending with the exit to the viewing area, is depicted in the attached Figure.

_The inter-arrival time of customers follows an exponential distribution with mean of 2.0 minutes. The time to purchase tickets follows a uniform distribution, with low value of 1.0 minutes and the high value of 2.4 minutes._ _The walk time to the ticket collector is uniformly distributed between 0.10 and 0.16 minutes._ _However, 10 percent of the customers use the restroom irrespective of the line formed for the ticket collector. If the line has more than two customers, 18 percent of the customers use the restroom._ _Assume that customers are equally divided with regard to gender_. _Use of the restroom by males takes a time that is distributed uniformly between two and five minutes._ _Use by females follows a uniform distribution with end points of 4 and 10._ _The Men’s Room can serve three concurrent users;_ _the Ladies’ Room, only two. Restroom users join_ _the queue for the ticket collector following any customers who have joined the line in the interim_. If the ticket collector is available, the collection time is uniformly distributed between three and nine seconds. However, the ticket collector also helps with supplying the concession vendors; and, with probability 0.05, a customer will find the entry turnstile to be locked while the collector spends between one and three minutes (uniformly distributed) helping with supplies. Customers in the concessions area behave according to the following probabilities:

| Buying Behavior | Proportion |

| Buys neither Eats nor Drinks | 0.16 |

| Buys Eats Only | 0.12 |

| Buys Drinks Only | 0.15 |

| Buys Drinks then Eats | 0.25 |

| Buts Eats then Drinks | 0.32 |

The transaction time for each purchase and the walk time to the viewing area is shown in the following table.

| Purchase Behavior | **Time (Distribution)** | Walk Time |

| Neither Eats nor Drinks | NA | Uniform(0.12,0.24) |

| Eats | Exponential(2.5) | Uniform(0.08,0.16) |

| Drinks | Uniform(0.75,1.25) | Uniform(0.10,0.18) |

The time to walk between the Eats and Drink counters is a constant 0.05 minutes in either direction.

Study Objectives

The management is concerned about congestion in the lobby area and would like to have the simulation model provide estimates of the average number of customers in the lobby, the maximum number in the period of 90 minutes of simulation time that constitutes one sample (replicate), and the average length of the queues for each restroom. Do not concern yourself with deletion of any values; empty and idle is a natural assumption for the servers in the ticket and concessions areas. Produce confidence intervals for the average number of customers in the lobby and the average length of the restroom queues based on 20 replicates. Based on management’s belief that over 12 customers in the lobby at one time should occur quite infrequently, do you think that changes are needed?

**Assignment Requirements**

Program this model in GPSS/H. You are expected to use the terminology prescribed in the course in the documentation of your model (e.g. event, activity, process, object, attribute, etc.). Develop a written report that is well organized and gives the following information:

· A model specification beyond the description given above that serves as the communicative model from which you produce the programmed model. You can use the GPSS/H Block Diagram symbols, a Conical Methodology specification, or a systems engineering specification language with which you are familiar. (More than one communicative model is also possible.)

· The procedures used in the verification of your model.

· The procedures used, and the rationale for them, in the validation of your model..

· Estimates of all the values cited in the objectives of the study.

**Submission Requirements**

At least one communicative model representation should be produced and submitted within the five-week period. A brief specification of your experiment design (behavioral variables to be examined, confidence in sample size given, use or non-use of pilot run technique, etc.) should also be prepared and submitted. (Note that you will have to extend your knowledge of GPSS/H beyond what is discussed in the class notes but **not** beyond what is covered in the course text.) The full report is to be submitted by the end of the ten-week period. Your submission should includean executable (.GPS) and an output listing (.LIS) for one replicate.

## Platform

Code needs to be less then a 150 lines and done in GPSS/H


Habilidades: Engenharia, MySQL, PHP, Arquitetura de software, Teste de Software

Veja mais: what is the engineering design process, what is requirements specification, what is engineering all about, what is a probability, what do you mean by data entry, users requirements specification, transaction focus, tickets for less, three line diagram, systems analysis and design, study room design, room specification, restroom design, requirements needed for engineering, requirements and specification, php language study, inter design, high end engineering, find a event time program, experiment design, engineering design process, distributed data entry, design rationale sample, data entry verification and validation, data entry terminology

Acerca do Empregador:
( 0 comentários ) United States

ID do Projeto: #3044223