The project will include Arena models (only .doe files) and MSWord document for the report.
Thereport must contain the following sections:
(a) Statement of the problem
(b) Why simulation as opposed to analytical modeling (e.g., uncertainty, complexity, inter-dependency among variables, etc.).This is an important part of the report .Simulationis expensive.
In real-life simulation projects, data may not be available. Furthermore, definitions of the data are sometimes ambiguous. In this section, you needto list all the assumptions that you make for the project. If data neededfor your Arena models are not explicitly mentioned, you can come upwith reasonable assumptions. However, all those assumptions must beexplicitly mentioned in this section.
3. Input data analysis:
Discuss issues in data for your simulation (e.g., data collection, how manydata have been collected, theoretical distribution, empirical distribution, goodness-of-fit test, etc.).
4. Conceptual modeling logic and overview of Arena Modeling:
Discuss whether the system belongs to terminating systems vs. steady-state systems; flow-chart,UML diagram, or any graphical tool to depictoverview of your simulation logic.
5. Verification and Validation:
Discuss how you have verified (error-free) and validated your Arena modelagainst the real system (discuss how you would answer if customers askyou how they can trust that your Arena model is a good representation of their real-system).
6. Experimentation and Results (including output data analysis):
Include results (tables or graphs) of the simulation output and your analyses (number of replications, terminating vs. non-terminating, replicationlength (if non-terminating),determination of warm-up period (if non-terminating), confidence interval, other statistical tests, ensitivity analysis, etc.)
7. Summary and Conclusion:
Include a summary of your simulation results and a summary of yourrecommendations.