When making multiple runs, the output reports for the runs are appended one after another in a single file. If more than just a few runs are to be made, it is best to create a customized output report using the RunOutputList keyword for Simulation. This keyword allows the user to specify the set of outputs needed to analyse the results from the runs. Each output is entered as a separate expression enclosed by curly braces. For example, if the desired outputs are the average utilisation of Server1 and average waiting time in hours for Queue1, then the input to the RunOutputList keyword would be as follows:
{ [Server1].Utilisation } { [Queue1].AverageQueueTime/1[h] }
To make the custom output file easier to input to Excel, it is best to record only dimensionless values such as [Queue1].AverageQueueTime/1[h] in the above example. In this way, the value will be converted into the desired unit (hours in this case) and the unit will not appear in the entries for this column.
Prepare this input using the Input Builder, which can be opened from the dropdown menu in the Input Editor.
At the end of each run, the specified outputs are collected in a single output file with the name <configuration file name>.dat. The file has one row for each simulation run that was performed and is tab-delimited, which allows it to be opened in Excel for analysis. Each row in the output file is labelled with the scenario number and the replication number. An extra row is added after the runs for each scenario containing the average values and 95% confidence intervals for each output value.
The RunOutputList report can be generated with or without the main report, as specified by the PrintReport keyword. The keywords PrintReplications, PrintConfidenceIntervals, and PrintRunLabels allow the contents of the output file to be customized as desired.