Skip to content

Report Tabs

Every run opens the results with a tab for each part of your model. A row of key figures sits across the top, and each tab is a table you can sort, filter, and search.

The report Summary tab

The report has thirteen tabs, shown left to right. A tab appears only when your model has that kind of element, and the row of key figures across the top changes with the tab you are on.

Summary · Activities · Entities · Gates · Process Tables · Resources · Routes · Variables · Arrays · Costs · Impact Analysis · Queue Diagnostics · AI Analysis

Two structural columns appear automatically when they apply and are left out of the tables below: a Scenario column when the model has scenarios, and a replication indicator when you run several replications (figures then show as a mean with a confidence interval). Some numeric columns are hidden by default behind a visual bar; you can switch them on from the column menu, and they are all listed here.

The run at a glance, plus a comparison across scenarios.

Simulation info

FieldWhat it showsWhere it comes from
Run LengthHow long the model ran, in simulated minutesThe simulation clock at the end of the run
Events ProcessedTotal discrete events the engine executedCounted by the engine
Execution TimeWall-clock time the run tookTimed while the engine ran
SimulatedWhen the run finishedThe completion timestamp

Scenario comparison (one row per scenario, Baseline first)

ColumnWhat it showsHow it is derived
ScenarioScenario nameThe scenario label
ThroughputEntities that exitedCount of exits
Avg Throughput TimeAverage time an entity was in the systemEntity cycle times, weighted by how many exited and remain
In SystemEntities still present at the endCount at run end
CreatedEntities createdCount of creations
EventsDiscrete events processedCounted by the engine

Key figures across the top: Total Throughput, Avg Throughput Time, Bottleneck (the highest-utilization location), Absorbed, and In System.

One row per activity, with expandable input-queue (InQ) and output-queue (OutQ) sub-rows. The state columns split by capacity: an activity with capacity 1 reports Operation / Idle / Waiting / Blocked; capacity above 1 reports Empty / Partial / Full.

The report Activities tab

ColumnWhat it showsHow it is derived
NameActivity name (InQ = input queue, OutQ = output queue)The activity name
UtilizationPercentage of capacity in use, on averageAverage contents ÷ capacity × 100
State MixBar splitting time into working, waiting, blocked, idle (or full / partial / empty)The percent-of-state figures below
FillBar of average contents against capacity, with the peak and the end valueAverage, maximum, and ending contents against capacity
FlowBar of entities that exited versus those still stuckEntries and exits
Avg TimeAverage time an entity spent hereMeasured per entity, averaged
Scheduled HoursTotal time the activity was scheduled to be availableFrom the activity’s shift
EntriesEntities that enteredCounted as entities enter
ExitsEntities that leftCounted as entities leave
Avg ContentsAverage number of entities present over timeTime-weighted average
CapacityMost entities allowed at onceFrom the activity’s properties
Cap MaxMost entities present at any pointThe observed peak
Cap CurrentEntities present when the run endedCount at run end
% OperationShare of time actively processing (capacity 1)Time in the operating state ÷ scheduled time
% IdleShare of time empty but available (capacity 1)Time idle ÷ scheduled time
% WaitingShare of time waiting for a resource or dependency (capacity 1)Time waiting ÷ scheduled time
% BlockedShare of time an entity could not move on because the next place was full (capacity 1)Time blocked ÷ scheduled time
% EmptyShare of time with no entities (capacity above 1)Time empty ÷ scheduled time
% PartialShare of time partly occupied (capacity above 1)Time partly full ÷ scheduled time
% FullShare of time at capacity (capacity above 1)Time full ÷ scheduled time

Key figures: Total Activities, Avg Utilization, Most Utilized, Highest WIP.

One row per entity type, plus an “All Entities” summary row. The cost columns are hidden by default.

ColumnWhat it showsHow it is derived
Entity TypeEntity type nameThe entity name
CreatedEntities of this type createdCount of creations
CompletedFinished the whole process and exited as themselves (true throughput)Count of completions
AbsorbedBecame part of another entity that exitedCount of absorptions at attach
In SystemStill present at the endCount at run end
FlowBar of completed, absorbed, and in-systemThe three counts above
Time MixBar of value-added, required non-value-added, and non-value-added timeThe average time figures below
Cost MixBar of touch, non-value-added, required non-value-added, and other costThe average cost figures below
BalkBar of entities turned away, by reasonThe balk counts below
Avg Throughput TimeAverage time from creation to exitAveraged per entity
Avg VA TimeAverage time in value-added activitiesAveraged per entity
Avg NVA TimeAverage time in non-value-added states: queues, NVA activities, transitAveraged per entity
Avg RNVA TimeAverage time in required non-value-added activitiesAveraged per entity
Avg Total CostAverage total cost per entity, everything includedSum of all cost categories, per entity
Avg Touch-time CostAverage value-added cost per entityValue-added processing, moves, and resource use
Avg NVA CostAverage non-value-added cost per entityNVA processing, moves, and queue cost
Avg RNVA CostAverage required non-value-added cost per entityRNVA processing and moves
Balk (No Entry)Turned away because the queue and capacity were full on arrivalCounted on arrival
Balk (Shift)Turned away because the resource went off shiftCounted at shift change
Process EfficiencyValue-added share of total timeVA ÷ (VA + NVA + RNVA) × 100

Key figures: Total Created, Total Exited, Avg Throughput Time, In System.

One row per gate. The Kanban columns appear only when a gate uses Kanban cards.

ColumnWhat it showsHow it is derived
Gate NameName of the gateThe gate name
Default StateNormally open or normally closedFrom the gate’s setting
EntriesEntities that arrived at the gateCounted as entities arrive
ReleasedEntities that passed throughCounted as entities pass
BlockedEntities that had to waitCounted when held
FlowBar of released versus blockedThe two counts above
Avg WaitAverage wait, including entities still waiting at the endAveraged over waiting entities
Max WaitThe longest single waitThe observed maximum
WaitBar of average against maximum waitThe two figures above
Avg QueueAverage number waiting at the gateTime-weighted average
Max QueuePeak number waitingThe observed peak
% OpenShare of run time the gate was openTime open ÷ run length
State ChangesTimes the gate flipped open or closedCounted

Kanban columns (when Kanban is used): Cards Sent, Avg Cards Available, Avg In Transit, Card Utilization, Starvation Events, and Blocked (No Cards).

Key figures: Total Gates, Total Blocked, Avg Wait Time, Max Queue.

A two-level table. The outer row is one Process Table; expand it to see one inner row per table row.

ColumnWhat it showsHow it is derived
Process TableThe table’s nameAs authored
EvaluationsTimes the table was checked during the runCounted
Rows FiredTotal matching-row hits across all checksCounted

Inside, each row shows its match condition, its Match Count (times the condition matched), and its Execution Count (times it ran).

One row per resource, with a Resource Groups sub-table when the model defines groups.

ColumnWhat it showsHow it is derived
Resource NameName of the resourceThe resource name
UtilizationShare of scheduled time busy (can exceed 100% with overtime)Busy time ÷ scheduled time
State MixBar: in use, waiting, overtime, on break, down, idle, off-shiftThe percent figures below
Cost MixBar: used, overtime, break, downtime, unusedThe cost figures below
UnitsQuantity of this resource availableFrom the resource’s properties
Scheduled HoursTotal scheduled hours, breaks includedFrom the resource’s shift
Overtime HoursHours worked past shift endMeasured
Wait HoursHours in setup or travel before starting workMeasured
Times UsedTimes the resource was usedCounted
Avg Time Per UsageAverage length of one usageAveraged
Cost UsedCost while in use during scheduled timeRate × time in use
Cost UnusedCost while on shift but idleRate × idle time
Cost BreakCost during scheduled breaksRate × break time
Cost DowntimeCost while downRate × downtime
Cost OvertimeCost for overtimeOvertime rate × overtime
Total CostAll cost categories added upSum of the costs above
% In UseShare of scheduled time in use, overtime excludedIn-use time ÷ scheduled time
% WaitShare of scheduled time assigned but waitingWait time ÷ scheduled time
% OvertimeShare of scheduled time in overtimeOvertime ÷ scheduled time
% IdleShare of scheduled time idleIdle time ÷ scheduled time
% On BreakShare of scheduled time on breakBreak time ÷ scheduled time
% DownShare of scheduled time downDowntime ÷ scheduled time
% Off-ShiftOff-shift time as a share of the whole runOff-shift time ÷ run length
Off-Shift TimeMinutes off shiftMeasured
Busy TimeMinutes in useMeasured
Idle TimeMinutes available but idleAvailable minus busy, break, and off-shift
Available TimeMinutes available (on shift, not down)Measured
Lost UnitsWork preempted when a shift endedCounted at shift-off

Resource Groups sub-table (when groups are defined): Group Name, Members, Utilization, Units, Times Used, % In Use, Scheduled Hours, and Total Cost, each rolled up across the group’s members.

Key figures: Total Resources, Avg Utilization, Most Utilized, Total Cost.

One row per route (a connector from one place to the next).

ColumnWhat it showsHow it is derived
RouteThe path, source to targetThe connected activity or queue names
ClassificationValue-added, required non-value-added, or non-value-addedFrom the route’s setting
Usage CountTimes entities traveled this routeCounted
Move TimeTotal travel time on the routeSummed
VA TimeValue-added time on the routeSummed
NVA TimeNon-value-added time on the routeSummed
RNVA TimeRequired non-value-added time on the routeSummed
Total CostCost of using the routeUsage × cost per move

Key figures: Total Routes, Most Used Route, Total Usage, Total Cost.

One row per variable. The history columns (Total Assignments, Avg Time / Assignment, Average, Std Dev) fill in only when the variable has statistics tracking switched on in the Logic Sheet.

ColumnWhat it showsHow it is derived
VariableVariable nameAs defined
TypeData type (Real, Integer, Descriptive, DateTime)From the definition
InitialValue at the startFrom the definition
Total AssignmentsTimes the value changed (tracked variables)Counted
Avg Time / AssignmentAverage time the value held between changes (tracked)Span of changes ÷ number of changes
MinLowest value heldThe observed minimum
MaxHighest value heldThe observed maximum
Current ValueValue at the endThe final value
RangeBar of min, max, average, and spreadMin, max, mean, and standard deviation
AverageTime-weighted average value (tracked)Value weighted by how long it was held
Std DevTime-weighted spread (tracked)Standard deviation over time
FinalValue when the run endedThe final value

Rows open a drill-down with the full history and a step chart. Key figures: Total Variables, Tracked, Total Changes, Active Variables.

One row per array.

ColumnWhat it showsHow it is derived
ArrayArray nameAs defined
TypeData type (Integer, Real, Descriptive, Date)From the definition
DimensionsRows, rows by columns, or rows by columns by depthFrom the definition
Total CellsNumber of cellsProduct of the dimensions
Cells ChangedDistinct cells written during the run (needs tracking)Counted
UsageBar of cells changed against total cellsThe two figures above
Min ValueSmallest value across cellsScanned
Max ValueLargest value across cellsScanned
Import SourceFile the data came from, if importedFrom the definition

Rows open a drill-down with the array contents and change history. Key figures: Total Arrays, Total Cells, Cells Changed, Tracked.

Not a single table: a cost breakdown chart plus four sub-tables. Costs are worked out from the run’s results and your model’s cost settings.

Location costs, Location, Type (activity or queue), Processing cost, Per-Entity cost, Total, and Entries.

Resource costs, Resource, Cost Mix, Cost Used, Cost Unused, Cost Break, Cost Downtime, Cost Overtime, Total Cost, Units, and Times Used.

Route costs (when routes carry a cost), Route, Usage Count, Cost Per Move, and Total Cost.

Entity costs, Entity Type, Count, Initial Cost, Waiting Cost, Touch-time Cost, and Total Cost.

Key figures: Total Cost, Activity Cost, Resource Cost, Entity Cost. See Costs for more.

One row per activity, ranking where time is spent. See Impact Analysis for the full view.

ColumnWhat it showsHow it is derived
Activity NameActivity nameThe activity name
StatusValue-added, required non-value-added, or non-value-addedFrom the activity’s setting
EntriesEntities that enteredCounted
Total VA MinValue-added time here (value-added activities)Entries × average processing time
Total RNVA MinRequired non-value-added time hereEntries × average processing time
Total NVA MinNon-value-added time, including all queue waitSummed
Total ImpactAll three added together for this activityVA + RNVA + NVA
% of VAThis activity’s share of all value-added timeIts VA ÷ total VA
% of RNVAThis activity’s share of all required non-value-added timeIts RNVA ÷ total RNVA
% of NVAThis activity’s share of all non-value-added timeIts NVA ÷ total NVA
% of TotalThis activity’s share of the grand totalIts total ÷ grand total
% VA of TotalValue-added share of this activity’s own timeIts VA ÷ its total
% RNVA of TotalRequired non-value-added share of its own timeIts RNVA ÷ its total
% NVA of TotalNon-value-added share of its own timeIts NVA ÷ its total

Key figures: Activities, Total VA Time, Total NVA Time, Process Efficiency.

A ranked view rather than a plain table, showing where and when work piles up. See Queue Diagnostics for the full view. The Top Queue Problems table ranks the worst queues:

ColumnWhat it showsHow it is derived
RankPosition 1 to 5Ordered by non-value-added time
QueueQueue nameThe queue name
ImpactShare of total queue delayThis queue’s NVA ÷ all queue NVA
Max QueuePeak lengthThe observed peak
PatternThe kind of build-up (for example steady or peak-hour)Classified from the run

Selecting a queue adds a header (rank, share, peak, pattern, and the worst time window) and a heatmap of severity by day and time.

Not a stats table: an assistant that reads the run and explains it in plain language. See AI Analysis. It is part of Professional; it is turned off in the free Personal mode.

LegacyHow this worked in the previous version

Ten general reports automatically expose information to identify system problems. The reports include:

  • General

  • Entities

  • Activities

  • Activity by % (Multi Cap)

  • Activity by % (Single Cap)

  • Resources

  • Resource by %

  • Variables

  • Impact Analysis

  • Hotspot Evaluator

  • Output from: Name and location of the model data

  • Date: Date the model was simulated

  • Time: Time the model was simulated

  • Total Cost: Represents the sum of all the cost to run the process plus the addition of all unused resource costs

  • Scenario: Type of scenario run. It will list the scenario name when scenarios are run or “Normal Run” when a single scenario is simulated.

  • Replication: Type of replication. When single replication is done only average report is shown. When multiple replications are run, average report as well as individual replication results are shown separately.

  • Simulation Time: Total simulation time of the model.

What are different tabs on the General Report?

What are different tabs on the General Report?

  • **Entity Name: **Names of all the entities that have been added to the model with statistics enabled.

  • Qty Processed: The total number of entities processed through the model. Only exiting entities count in Qty Processed.

  • **Average Cycle Time: **The average time each entity spent in the model.

  • Cycle Time is the total elapsed time to move a unit of work from the beginning to the end of a process. Cycle time includes process time, during which a unit is acted upon to bring it closer to an output, and delay time, during which a unit of work is spent waiting to take the next action.

  • Average VA Time: Average value-added time each entity spent being processed in activities or moved from one activity or storage to the next, does not include the time waiting or time at any activity that is declared as NVA (Non-Value Added).

  • Activity time begins as soon as an entity enters the capacity of the activity, and ends when the entity leaves the capacity, either by moving to the output queue or to the next location in the model. Value-added time is accrued only from a TIME statement in the action logic or from the General tab’s Time field.

  • Average RNVA Time: Average time each entity spent being in activities set to RNVA. RNVA activities include actions that are required but do not add value (as defined by the customer). An example of a RNVA activity might include a governmental inspection that neither the producer nor the customer identifies as value-adding.

  • Average NVA Time: Average Non-value-added time each entity spent at an activity declared as NVA, the time an entity spends being idle, waiting for a resource, in storage, traveling on a route, waiting in an input queue or when a Wait Until statement holds it.

  • Average Touch Time Cost: The average cost of the entity. This is based on how much work was done on the entity by activities, resources etc that have an associated cost. Unused resource cost is not applied to the average cost, to see cost with unused resource cost added, see the Average Total Cost.

  • Average Total Cost: The total cost for each entity. Total Cost represents the sum of all the costs to run the process plus the addition of all unused resource costs. Includes sum of;

  • Used / Unused Resource cost.

  • VA, NVA, and RNVAcosts for each entity.

  • Initial entity cost.

  • Entity waiting cost.

  • **Process Efficiency: **Formula: Average VA Time / Average Throughput Time

  • Weighted Overall Process Efficiency: Becomes accessible when two or more part or entity types exit the model. The weighting factor is the quantity of entities exiting the system. Entities having more exits provide a higher contribution to the weighted efficiency. The formula follows (Process Efficiency Entity X1 * Qty Processed Entity Y1) + (Process Efficiency Entity X2 * Qty Processed Entity Y2) + / (Qty Processed Entity X1 + Qty Processed Entity X2 + ).

Only entities that exit the model have statistics collected for them and reported. If an entity is renamed at some point in the model, the original entity will not report statistics. Only the new name will show stats. Another instance when the entity summary will show 0’s is when one entity is attached to another without detaching them before they exit the model.

What are different tabs on the General Report?

  • Activity Name: Names of all the activities that have been added to the model with statistics enabled.

  • **Scheduled Hours: **The total number of hours the activity was scheduled to be available, as the result of any shift file it uses, defined in the properties dialog.

  • Capacity: Capacity of the activity, defined in the properties dialog.

  • **Total Entries: **The total number of entities that entered the activity, not including entities arriving to be attached. Entities arriving that have been previously grouped or have entities attached to them to form a single entity only count as one entry.

  • Average (Sec/Min/Hrs/Days) Per Entry: Average time an entity spent at the activity, time value is based on what is selected in the Simulation Options window. This time may include partial times from the beginning and end of the actual run time.

  • Average Contents: Average entities in the activity at the same time.

  • Maximum Contents: The maximum number of entities that occupied the activity at the same time, over the course of the simulation.

  • Current Contents: The number of entities remaining at the activity when the simulation ended.

  • **% Utilization: **The percentage of capacity occupied, on average, during the simulation.

What are different tabs on the General Report?

  • Activity Name: Names of all the activities that have been added to the model with statistics enabled and have a capacity of more than 1.

  • **Scheduled Hours: **Scheduled hours for the activity, defined in the properties dialog.

  • **% Empty: **Percentage time the activity was empty.

  • **% Partially Occupied: **The percentage of time the activity had entities but was not filled to capacity. (100% of time - %Full - %Empty)

  • **% Full: **The percentage of time the activity was filled to capacity with entities.

What are different tabs on the General Report?

  • Activity Name: Names of all the activities that have been added to the model with statistics enabled and have a capacity of 1.

  • Scheduled Hours: Scheduled hours for the activity, defined in the properties dialog.

  • % Operation: The percentage of time the activity was actually processing an entity.

  • % Idle: The percentage of time that no entities were at the activity, but the activity was not down.

  • **% Waiting: **The percentage of time the activity was waiting for a resource or another entity in order to begin processing or move to the next activity. Any delays in processing routing Action logic are counted as waiting time.

  • **% Blocked: **The percentage of time entities spent waiting for a freed destination. “Blocked” means that an entity cannot move downstream in the model due to insufficient capacity at the next location. The entity has to sit at the current location after the normal processing time is complete until there is room available for it to move.

What are different tabs on the General Report?

  • Resource Name: Names of all the resources that have been added to the model.

  • Units: Number of resources assigned, defined in the properties dialog.

  • Scheduled Hours: The total number of hours the resource was scheduled to be available, as determined by the assigned shift file, defined in the properties dialog.

  • Number of Times Used: The total number of times the resource has been acquired to transport or process an entity.

  • Average (Sec/Min/Hrs/Days) Per Usage: The average time the resource is used by an entity. Time value is based on what is selected in the Simulation Options window.

  • **% Util: **The percentage of time the resource spent moving or processing an entity. (100 * (Number of Time Used * Average Minutes Per Usage)) / (Scheduled Hours * 60 min/hr)

  • **Cost of Used: **The total cost of used resources. If the resource is on break, no cost is charged.

  • **Cost of Unused: **Total cost of unused resources. Represents the time you must pay for, even though the resource may not be actively working on entities. The column helps you quantify the resource waste in your process. Unused costs are not included in the report which uses ABC costing.

Resources are reported both by unit and collectively. The collective unit (aggregate) report for a resource totals the first three fields and averages the next two fields discussed above.

  • **Resource Name: **Names of all the resources that have been added to the model.

  • Scheduled Hours: Total scheduled hours for the resource during simulation, defined in the properties dialog.

  • % in Use: The percentage of time the resource was being used by entities.

  • % Idle: The percentage of time the resource was available but not in use.

  • % Down: The percentage of time the resource was unavailable due to shifts or options selected in the Availability tab for the resource.

  • Variable Name: Names of all the variables that have been added to the model with statistics enabled.

  • **Total Changes: **The total number of times that the value of the given variable changed during the simulation.

  • Average (Sec/Min/Hrs/Days) Per Change: The average time that a given variable remained at any one value. Time value is based on what is selected in the Simulation Options window.

  • Minimum Value: The lowest value of the variable during the simulation.

  • **Maximum Value: **The highest value of the variable during the simulation.

  • **Current Value: **The final value of the variable when the simulation ended.

  • **Average Value: **The average value of the variable during the simulation.

  • **Std Dev.: **The standard deviation value of the variable during the simulation.

  • **Activity Name: **All the activities that have been added to the model with statistics enabled.

  • Status: Type of activity.

  • **Entries: **Total entities that passed from the activity.

  • **Total VA Min: **Is based on the time an entity has spent in the capacity of the activity, even if an entity is waiting for a resource, since the activity space is being utilized. Based on the total time all entities that have passed through, are currently in the activity, or are in the activity queue.

  • Total RNVA Min: Is based on the time an entity has spent in the capacity of the activity that is declared RNVA, even if an entity is waiting for a resource, since the activity space is being utilized. Based on the total time all entities that have passed through, are currently in the activity, or are in the activity queue.

  • Total NVA Min: Is based on the time an entity has spent in the input or the output queue of an activity (depends upon an input/output queue cap). Based on the total time all entities that have passed through, are currently in the activity, or are in the activity queue.

  • Total Min: Total time spent by an entity in an activity. Based on the total time all entities that have passed through, are currently in the activity, or are in the activity queue.

  • % of VA: (Total VA of the activity / Sum of VA of all activities) * 100

  • % of RNVA: (Total RNVA of the activity / Sum of RNVA of all activities) * 100

  • **% of NVA: **(Total NVA of the activity / Sum of NVA of all activities) * 100

  • **% of Total: **(Sum of ‘Total VA’, ‘Total RNVA’, and ‘Total NVA’ of the activity / Sum of ‘Total VA’, ‘Total RNVA’, and ‘Total NVA’ of all activities) * 100

  • **% VA of Total: **(Total VA of the activity / Total Min) * 100

  • **% RVA of Total: **(Total RNVA of the activity / Total Min) * 100

  • % NVA of Total: (Total NVA of the activity / Total Min) * 100

Learn More: What is Impact Analysis?

The Hotspot Evaluator leverages robust Impact Analysis to visually pinpoint the top 10 areas that will deliver the most significant results.

The Hotspot evaluator shows you the following:

  • NVA: Non Value Adding

  • VA: Value Adding

  • **RNVA: ** Required Non-Value-Added