Responses

A response is an output you want an experiment to measure. Every configuration reports the same responses, so you can compare them on equal footing, and one response becomes the objective the search works toward.

The response catalog

Add Response lists everything the experiment can measure, in plain language, grouped by what each measure covers.

Across the whole process:

• Throughput: entities completed in a run.
• Average time in system: time from arrival to done, all types weighted together.
• Cost per entity: what the average entity costs, start to finish.
• Process efficiency: how much of each entity’s journey was real work.
• Work in process: work still in the pipe when the run ends.
• Longest wait anywhere: the worst average wait in the process, wherever it happens.
• Busiest step utilization: how hard the busiest step is working.
• Total run cost: what the whole run cost.
• Highest wasted minutes anywhere and total wasted minutes: time spent on work that adds nothing.

At a step you pick: waiting time, longest queue, and wasted minutes at that step.

By entity type: time in system, completed count, and turned-away count for a chosen type.

You can also track a variable’s end value or a single array cell, for anything you measure with your own logic.

Why some measures are greyed out

A measure that does not apply to your model is shown in grey, with the reason on the row. For example, percent blocked only means something for a step that works on one entity at a time, so if no step in your model does, that measure sits out. This keeps the list honest: everything shown is something your model can actually report.

Choosing responses

Add the responses you care about, then pick one as the primary goal in the objective. The rest are still measured and shown for every configuration, which is what makes the ranked results and trade-off views possible.