question

Cody F avatar image
0 Likes"
Cody F asked Jason Lightfoot edited

How to break down station and reset upon repair in process flow?

ExampleModel.fsm

Hello,

I am using process flow to run my environment and can't understand how to use breakdown and repair in the process flow. I have played with the preemption commands and have been unsuccessful and am not familiar with them.

I have an agv process that involves a testing station with 2 locations to allow for agvs to choose an open lane if one is occupied. The testing needs to have a failure rate of ~15% only when delayed for work in station(testing happening). When a fail happens, I'll need to repair and then re-run the delay for work from the start instead of resuming where it left off. How can I apply break down and repair to my process flow? and how to restart the station test time after fail/repair instead of resuming?

Thanks for any solutions and/or helpful suggestions.

FlexSim 21.2.4
agvprocessflowbreakdownrepair
examplemodel.fsm (65.6 KiB)
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Jason Lightfoot edited

Not sure what you mean by breakdowns - it looks and sounds more like you're doing quality checks are rework rather than breakdowns and repairs.

You just add a percentage decide to your process flow and have it loop back around to your delays if you decide it failed the QC. The problem with this is that in your model, you are modelling all the processes seperately even though they are the same. I propose you change this to a more generic and instance based approach so then you only edit one process definition.

Attached is a solution to the routing using instanced process flows for the control point/station processes and using the NextWorkPoint connections between the CPs to detemine where to travel next. I've added a user command to create an array of connected control points (I found using AGV.Connections is no simpler).

All the control point stations get pushed to a list and are used to know where you can route to next based on the Query - "WHERE value IN puller.nextPositions".

Now that you only have one process flow handling all the control points you can add rework loop as I mentioned before. If the chance is different for each station/position then put that as a label on each CP and read that rather than hard coding the value.


examplemodel_jl.fsm


examplemodel-jl.fsm (61.0 KiB)
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.