One tip that I can give you is to think about what a token is going to represent.
If you create a token whenever an item enters a queue, then this token will, in a way, be a representation of that item. As a result, the logic and actions you build in the Process Flow should be from the perspective of the item. For example, the item waits until a specific event happens and then the item acquires an operator to move it to its next destination.
By design, an Object Process Flow lends itself much more to be build from the perspective of that object, i.e. the processor. And since the processor is a persistent object, it makes sense that tokens in the Process Flow would also be persistent. So you'd create a single token at the start of the model run and that token now represents the processor and controls what it will do. It might acquire/pull an item, have it transported to the processor and then wait until the process is finished, for example.
You don't have to do it that way, but at least for me it helps to think in terms of the token's 'perspective'.