How can a custom Gantt chart accurately separate Setup and Process times?

How can a custom Gantt chart accurately separate Setup and Process times?

andy900526SNZGH
Explorer Explorer
222 Views
3 Replies
Message 1 of 4

How can a custom Gantt chart accurately separate Setup and Process times?

andy900526SNZGH
Explorer
Explorer

【Problem Background】
I am developing a semiconductor/process model using FlexSim 22.2. Currently, the Statistics Collector, named MO record, is used to monitor the work order entry and exit times of four main machines (Thin Film, Photolithography, Etching, Stripping) and to draw custom Gantt charts on the Dashboard.

 

【Core Requirements】

I need a Gantt chart with the Y-axis representing the machine and the X-axis representing time. Each colored block in the chart represents a specific work order (identified by ArrivalOrder).

 

Key Requirement: The colored block for a single work order must consist of two consecutive segments: red (Setup Time) and green (Process Time) to reflect the true ratio of "line changeover preparation" to "actual processing."

Data Logic: Use Using From/To Lookup Table to determine Setup Time (Setup is only generated during product changeover).

 

【Current Technical Challenges】

 

Incorrect Event Log Time Points: Attempts to listen for On Setup Finish or On State Change (to Processing) occur, but the obtained setup finish time always overlaps with the stop time (processing completion), causing the Setup segment to not be reflected in the data table.

 

[Supplementary Explanation: Data Status Comparison Chart]

 

I have attached a comparison chart (2026-05-08 183219.png). The top is a custom Gantt chart, and the bottom is a built-in State Gantt chart.

Status Observation:

From the State Gantt below, it is clear that the machine did indeed enter the Setup (purple) state at a specific time.

However, the Gantt Chart above only displays the complete work order dwell area and cannot show the internal Setup process at all.

0 Likes
Accepted solutions (1)
223 Views
3 Replies
Replies (3)
Message 2 of 4

moehlmann_fe
Collaborator
Collaborator
Accepted solution

My idea would be to number the items, so you can identify the first and last item in a batch (ArrivalOrder). This is easier if the items are created through a Process Flow. The Statistics collector can then react to the "Setup Time", "Process Time" and "Process Finish" events of the processors, but only create/update the row for the first item (setup start, process start) or last item (process finish).

0 Likes
Message 3 of 4

andy900526SNZGH
Explorer
Explorer

Thank you for the detailed reply — it completely solved my issue. Since I’m still a beginner and haven’t really worked with process flow concepts before, could you maybe give a brief explanation of how your setup works and why you configured it that way? I’d really appreciate the insight.

0 Likes
Message 4 of 4

moehlmann_fe
Collaborator
Collaborator

As I said, the Process Flow is only used because its easier to number the created items this way. The arrival table of the 3d source was copied to the Schedule Source so that one token gets created for each row and is assigned the required labels. Each of those tokens then runs through a subflow as many times as items should be created for that row. The subflow tokens are numbered by assiging their creationRank to the "Index" label. That label and the total quantity is also written to the items in the Create Objects activity.

This way I can check in the Statistics collector if an item is the first (Index == 1) or last (Index == TotalQty) for their row.