What are the limitations of process flow?

[erin_dooley]

There are a lot of pros to using process flow such as easier and faster modeling of complex logic, being able to see flow decisions, doesn't require written code, etc. What I am wondering is what are the drawbacks? When should I be using the standard 3D modeling without process flow?

[matt_long · Accepted solution]

The only real limitation I can see with Process Flow is also one of its strengths. When you go to add Process Flow to your model, you start with a blank canvas. There's no canned functionality like there is using 3D. Yes we do have a few templates you can start with, if these meet your needs, but for the most part, you have to build in your logic one activity at a time. This can be a limitation if you don't know exactly what needs to be done, or you're not sure where to start. But it's also a strength in that process flow doesn't limit you to doing things a specific way. You can customize your logic to your heart's content.

As far as when should you be using the standard 3D modeling without process flow? I'd say if the default 3D objects do exactly what you need, then just use them. If your system requires additional control and logic, then add in process flow.

[JordanLJohnson]

I use both kinds of objects; they integrate very will together. 3D objects allow you to very naturally define layout and spatial relationships. Also, some 3D logic would be very difficult to reproduce in Process Flow.

For example, in Process Flow, to get a TaskExecuter to move around, you just give it a travel task, that basically means "get from wherever you are to where I want you to go." But how does it travel? If that TE is attached to an AStar grid, it will find the shortest path, accounting for obstacles. If it is on an AGV network, it will use the AGV paths. The ProcessFlow doesn't really care how the object is travelling, just that it is.

As another example, take conveyors. It would be very, very difficult to use ProcessFlow to recreate conveyor logic. So I use conveyors to be conveyors. As far as decisions made at decision points and photo eyes, I generally use process flow.