Simplifying Process Flow
I copied your custom code to all machines. but it seems all machines in the model picked Machine001's process time, which is 9.06 s.
Below is Machina003 as an example. how to get this fixed?
Update: I think I am confused the difference between process time and stay time. I appreciate if you can explain the difference.
Hey @jpanY7K8B, I forgot to limit the table to only look at results from the specific product. I added a SQL query to the code to get a sub-table only with a specific product's times.
/**Custom Code*/
Object current = ownerobject(c);
Object item = param(1);
int step = item.Step;
string productName = item.Type;
Table procInfo = Table("ProcessInfo");
Table subTable = Table.query("SELECT * FROM ProcessInfo WHERE ProduceName = $1", productName);
double procTime = subTable.getValueByKey(step, "ProcessTime", 2);
print("Machine: ", current.name, "\tItem: ", productName, "\tStep: ", step, "\tProcTime: ", procTime);
return procTime;You could also modify the SQL statement to just get process time directly without having to do the "getValueByKey" step. Here's more info on sql queries if you're interested.
After running for a bit, you'll notice that your machines' averages don't align with the table values, but the min/max staytimes probably will. For example, on Machine4,
The min aligns with Product002 and the Max aligns with Product001.
This won't always be the case if you have special code that holds items a little longer, does setup time, etc. But at least with this sample model, this is a good way to know if the right products are getting to the right machines and using the right process time.
Hello @kavika_faleumu,
in the Machine process flow, I used scheduled source as Machine asset. I meant to use Quantity column to control Machine qty in each kind. But it seems does not work the way I wanted. For example, I want to change Machine001 to 3 in Quantity column. Any suggestion on how to modify the model? Thank you
(Attached the model file with updated code that you previously suggested. )
I suggest you start by making a group for each Machine you'd like to multiply.
Then you can add a Parameter Table (I renamed mine to "MachineGroups") to set the desired values you want for each group.
If you click on the "Value" and then the drop-down arrow, you can set the Reference to the proper Group. Then, in the On Set section, you set it to Delete and Copy Group Members.
This option will (1) delete all the copies of the machine except the original, (2) create X number of copies of that machine, and finally (3) place them at whatever offset from the original you have set. For example, if I set my param value to 3 with a Y Offset of 3, then my Machine001 group will look like this. (Objects will be deleted and copied On Reset. To see your changes, reset the model).
It looks like your WorkCenter group is setup to add them automatically to the group, so that makes things a little easier.
From here, you'll want to update your Assign Labels activity to choose a WC_Name that probably starts with a particual name (so it chooses any machine in the group). Or you'll have to change your Pull from List activity's query to select something WHERE WC_Name LIKE puller.WC_Name. You'll have to play around with what works for you.
Hope this helps!
Hey @jpanY7K8B,
Regarding the pileup, that's due to your Process Flow pulling the two initial Queues but not Pushing them back onto the list. If you want to make sure that they're always available to be pulled, you can check the "Leave Entries on List" box. That way, even when they get pulled due to a query, they'll stay on the list for other tokens to pull. Then you don't need to worry about pushing them back on.
With regards to your Process, I think I see where the issue is. You're moving boxes to the correct Queue, but then your Wait for Event is waiting for those boxes to exit the Queue after they've already left to be processed. So that token never gets processed.
You don't want to wait for boxes to leave the Queue -- you want them to finish processing first. From there, there are several ways you could move items to their next PreProcessing Queue. You could push them to an ItemList then have the Initial Start pull from that List. You could move the items straight to the next Queue using Process Flow or Input/Output/A-Connections in the 3D view.
Attached is an example model modified to use one of these ways.
Firstly, you've got conflicting logic in 3D and Process Flow. I'll move the incrementing of the "Step" label to Process Flow. That way, when items enter and a new token is created, we can be sure to increment once.
After we've setup the token and we determine that it still has steps to do, we can pull a Queue (while leaving it on the list). Then, we'll let the 3D objects handle it until the last Processor finishes.
It will push it to an ItemList. In Process Flow, we'll wait to pull an item from the ItemList so we can move it back to the Initial Start.
Hope this helps!
Thank you for updating the model with detail explanation. When I test run the model, I encountered issue:
- After successfully processed 21 boxes, processor 1, 2, 3 stopped with processed boxes. and rest of the WIP start pilling up. Also, System console has the follow error message. I guess this error is related to MTBF. Once I disable MTBF, no issue to run the model. But I have to idea how to setup MTBF correctly.
time: 3961.030532 exception: Exception Caught in Processor::onTimerEvent(treenode involved, int code, char *datastr) object: /Processor4
time: 3961.030532 exception: Exception Caught in ObjectFunction246__project_library_FlexSimObject_behaviour_eventfunctions_OnTimerEvent object: /Processor4 class: /Processor4
time: 3961.030532 exception: Exception caught in TreeNode::receivemessage()
time: 3961.030532 exception: Exception caught in Executive::processeventinlist().- Can you please also explain why the model redirect token back to "Delay". In the attached file, I removed MTBF. As you can see I added to other methods to compare with "original Product Creation". Method 2 works. but not method 3. Did I miss something? Please correct me. Thank you very much.
Hey @jpanY7K8B,
To fix the first issue, I believe it was a problem with the "Pull Finished Item" activity. The "Assign To" property was `token.pulled`. I changed it to `token.Item` since the subsequent "Move Item Back to Initial Start" uses `token.Item`. (Of course you could do the opposite as well, changing the variable in the Move activity to be `token.pulled`.
For your second question, the reason we loop back to a Delay is to avoid creating more tokens and to simplify creation. The original item creation method simply created 2 tokens and would use those to create items every `token.Interval`. Of course, it's fine to also used Inter-Arrival Sources to spawn new tokens every X seconds and then send them to a sink. For the 2nd method, you would need an Inter-Arrival Source for every different time interval you want to spawn a token at.
