MassMotion – Modelling ticket gate arrays

Ensure that the Floor is split along the line of the array

Represent each ticket gate with a Link and the machinery with Barriers to ensure that the agents do not approach from the side

Set the Link to “Ignore Barriers” to ease the Agent’s movements if the gates are narrow (i.e. close to 500 mm wide)

Model the Link such that the goal line is in line with the edge of the Barriers to aid the Agents wayfinding

If the gate is for one direction only set the properties to Unidirectional

If the gate is two way set Priority Flow with the priority appropriately

Set a contact delay to represent the time taken to swipe or insert tickets

Bank the Links to ensure full saturation of the gates

To reduce “flip-flop” behaviour at the back of the queues set the Link queuing cost to a low value

Use Tokens to ensure that certain agents use either narrow or wide gate gates. There are two ways to achieve this:

1. give most Agents an “AnyGate” Token; gate the regular Links; create an event that opens the gates at the start of the simulation for Agents carrying the “AnyGate” token
2. give some agents a “WideGate” Token; create an Action that is applied to the Agents as they enter the Floor that tests for possession of that Token; this Action should give those Agents a Route command to use the wide gates