SimToken modelling question

[H J]

I have two types of customer streams, each with different arrival statistics (which advocates for two different SimTokes), but once they've arrived they will be treated the same (which advocates for a single SimToken; both client streams share the same attributes, and only some attribute values will identify which stream they belonged to). What's a good way of modelling this? Thanks!

[H J]

I found the solution: just Assemble a new Part (new Token) from the incoming (old) single Part.

[Harry King]

You shouldn't need to use Assemble. Just use the same PrototypeEntity input for two EntityGenerators. The AssignmentsAtStart input can be used to set the value for an attribute that identifies the customer stream.

Harry

[H J]

Indeed, so simple ... Thanks Harry!