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 the responses you score become the goal the search works toward. Every checked response counts at its weight in one overall score, and that score also picks the winner.

The response catalog
Section titled “The response catalog”Add Response lists everything the experiment can measure, in plain language, in six groups.
Overall 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: waiting time, longest queue, percent blocked, and wasted minutes at a step you pick.
By entity type: time in system, completed count, and turned-away count for a chosen type.
Resources: utilization, idle cost, and overtime cost for a resource or group you pick, and Resources used, which is listed only where the study changes a resource (below). Where a space in your model hands over, Handed Over % is listed too: how much of the time the resource you pick was handed over, for example being cleaned.
Inventory: service level and inventory cost.
Your data: a variable’s value or a single array cell, for anything you measure with your own logic.
Some measures ask one more thing
Section titled “Some measures ask one more thing”A measure of the whole process, such as Throughput, is added at once. The others open a second step that asks which one to measure:
- A measure at a step, for an entity type, for a resource or for an inventory item asks Which step, Which entity type, Which resource or Which item. Pick one and choose Add Response.
- A variable asks Which value: End value, or, when the variable tracks statistics, Average over time, Lowest or Highest. For a variable that does not, those three are gray, with the note “Turn on Statistics for this variable to measure this.”
- An array asks Which cell: a Row, and a Column and a Layer when the array has them, each a whole number within its size.
A new experiment’s default responses
Section titled “A new experiment’s default responses”The first response you add to an experiment, whichever one it is, brings three more in after it: Total run cost (dollars), Average time in system (minutes) and Resources used (units). Each is checked, lower is better and weighted 1, and they come in once per experiment. An experiment saved before version 7.0.9313 gets the ones it lacks, at the end, when it opens. One you already have is skipped, and one you remove stays removed.
Resources used
Section titled “Resources used”Resources used counts the units of the resources the study changes, never every person and machine in the model. Each resource Quantity factor adds its level: Workers at 5 counts 5, and a second resource at 2 makes 7. Each added resource adds its units on top of the model’s own count where the model already holds a resource of that name: 3 clerks and 2 added make 5, while a brand-new resource counts its units alone. In Add Response it reads “How many units of the resources this study changes a configuration uses.”
Why some measures are grayed out
Section titled “Why some measures are grayed out”A measure that does not apply to your model is shown in gray, 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.
Each response’s row
Section titled “Each response’s row”
Back on Define, every response you added is a row with the same controls:
- A checkbox that says whether the response is in the experiment. The checked responses are measured for every run. An unchecked response leaves the experiment: its box reads “Not included in this experiment. Not measured, and not shown in results”, and it gets no column on Results, All Points, Compare With Baseline, the export or the winner strip.
- A Goal: Lower is better or Higher is better.
- A Weight, shown on every checked response, that sets how much this one pulls the overall score. It starts at 1. A weight has to be above 0: the box says “Enter a weight above 0.” under the row, and the weight you had returns once you type one above 0 or leave the box. An unchecked response shows no weight.
- A Limit checkbox and number, for a bound the result must respect. A configuration that breaks it still runs but cannot win.
- Remove, the trash icon, which takes the response out of the experiment’s list.
A note under the table says “Weights set how much each response counts toward the winner. The Smart Optimizer also uses them to choose what to try next.” No response is primary: the order of the list is display only, and the first checked response is only the lead for display (the Define article says where).
The Define article covers how goals, weights, and limits combine into what best means.

