Describe the scenario you propose to analyze. Clarify your creativity in this example.

Develop a model in Arena that reflects your scenario. There are no limits on how you choose to model the system. The model must have at least one of each of the following components (you may have more of each component): o Arrivals
o Decision node or nodes
o Process
o Assign
o A schedule
o Optional1 components are not required, but are worth 0.5 points each ? A variable
? A Record module

1. Explain metrics used to evaluate the system. These could be the default metrics from Arena, or new metrics. You should discuss at least 4 metrics.
2. You may (but are NOT required to) develop a creative metric. This can be a combination of current metrics from Arena, or something else you measure in the simulation.

Run the model for the base case, with at least 100 trials. Discuss key results from the Arena analysis. Make sure to highlight the metrics you proposed earlier.

Suggest a recommendation for improving performance of the system. This recommendation must involve a policy class related to a key parameter or input of the model. Explain the rationale for using this policy class. The purpose of this policy class is to identify the relationship between one aspect of the model and various performance metrics you suggested earlier. (As an example, the policy class might be to change the arrival rate. The levels of the policy are the different arrival rates. This is probably a bad example, because arrival rates are not under your control.)

Analyze this policy class using the Arena PAN tool. The policy class must have at least 10 levels for the policy parameter. (This is called a Control in PAN.)

Develop a table to clearly identify the relationship between different levels of the policy class and the metrics proposed earlier.

Present at least 3 trade-off curves between important metrics of the model.