This simulator has been prepared by the National Protective Security Authority (NPSA) and is intended to help users simulate security checkpoints.
The user can customise a range of parameters to describe their security checkpoints and customer profiles. The tool then uses these inputs to predict how the queue behaves - such as waiting times, queue lengths and bottlenecks in the process.
There are ten pre-programmed scenarios available, representing a range of common security checkpoint layouts:
Customers with bags proceed to a search table, where their bags are manually searched. Customers without bags can enter the venue directly. The percentage and size of bags searched (e.g. large bags only) can be configured to reflect available screening resources.
Customers proceed to a search table for manual search of both their person and (if present) their bag. As above, the user can restrict the percentage of searches and bag sizes searched.
Customers with bags proceed to a ‘Bag’ lane for a manual search of their bag (and person, if specified). Customers without bags are directed to a different lane for a manual person search.
Customers’ bags are screened using a bag screening technology. Any bags that trigger an alarm are manually searched. Customers without bags can enter the venue directly. The percentage of bags screened can be configured to reflect operational policies (e.g. not screening children’s bags).
Customers’ and their carried bags are screened using a person-and-bag screening technology. Any alarms are resolved with a manual search of the person and, where applicable, their bag. The percentage of customers directed to manual search instead of screening (e.g. for medical reasons) can be configured.
Customers with bags leave them at a search table for manual inspection before passing through the person screening technology. After screening, they collect their bags and enter the venue. Customers without bags proceed directly to the person screening technology before entering the venue. Any alarms are resolved with a manual search of the person.
Customers with bags proceed to a search table, where their bags are manually searched. The sizes of bags manually searched can be configured (e.g. large bags only). The customer and their carried bag are then screened using a screening technology. Customers without bags proceed directly to the screening technology before entering the venue. Any alarms are resolved with a manual search of the person.
Customers with bags present them for screening using a bag screening technology. Any bags that trigger an alarm are manually searched. After bag screening, customers proceed with their bags through a screening technology that simultaneously screens both the person and any carried bags. Customers without bags proceed directly to the person-and-bag screening technology. Any alarms generated during screening are resolved through a manual search of the customer and, where applicable, their bag.
This scenario most closely resembles a typical airport security checkpoint. Customers divest any carried bags, which are screened with a bag screening technology. Customers then proceed through a person screening technology before collecting their bags. Any alarms on the bag or the person are resolved with a manual search.
Customers with bags proceed to dedicated ‘Bag’ lanes, where they divest their carried bags for screening before passing through a person screening technology. Customers without bags proceed to dedicated ‘No Bag’ lanes, which contain only the person screening technology. Any alarms are resolved through a manual search at separate search tables within each lane.
How to use the tool
The tool is split into three parts: Configuration, Setup and Simulations.
Configuration allows the user to customise a security process, risk appetite and key details about the venue. The Setup tab provides additional options to fine-tune how customers arrive and what types of bags they are carrying. Finally, the Simulations tab shows the results of the simulation.
For venues with multiple entrances, with different demographics, arrival rates or other restrictions, consider simulating each entrance separately.
Configuration
Scenario
A scenario represents the security process a customer follows to enter a venue. This process can include a mix of screening technologies and manual searches, with different configurations such as the number of security lanes, search tables, etc. Each element of the process is called a 'resource'.
Ten different scenarios are available, which can be selected from the dropdown menu. A flowchart is provided to illustrate the selected security set-up.
Detection priorities
The detection priorities allow users to select the search focus, which influences the time required for different search operations. The three preset levels are:
The focus is on searching for mass-casualty threats only e.g. large firearms and large IEDs. A resolution search on a person and their bag will take between 7 and 12 seconds on average, depending on the bag size.
The focus is on searching for all firearms, large and medium IEDs and large knives. A resolution search on a person and their bag will take between 8 and 12 seconds on average, depending on the bag size.
The focus is on searching for all threat types, including firearms, IEDs and knives down to small knives. A resolution search on a person and their bag will take between 13 and 24 seconds on average, depending on the bag size.
Arrival window (hours)
This is the duration (in hours) over which the search and screening process is simulated. This should reflect the time period during which customers are entering the venue.
Total number of customers
The user can specify the total number of customers arriving at the entry checkpoint over the arrival window. To limit the runtime of the simulation, this is currently restricted to a maximum of 25,000 customers.
Customising your scenario and estimating resources
Each selected scenario presents a different set of simulation controls in the Configuration panel. These controls can be used to modify the exact setup for that scenario, such as changing the number of search tables. Hover over the text box for each parameter for a more detailed explanation.
For some scenarios, the user can specify the percentage of bags to be searched or screened, and/or restrict searches to certain bag sizes (e.g. only large bags). These options have been included.
Users should then proceed to the Setup tab.
Setup tab
The Setup tab allows the user to customise venue throughput and the distribution of bag sizes carried by customers, and provides visualisations of each of these profiles.
Customer arrival profile
Customers may arrive at varying rates throughout the operating hours, for example with a peak at the start. The customer arrival profile describes how the arrival rate changes over time.
The arrival rate can be set using five preset profiles, or adjusted manually to a ‘Custom’ profile using the sliders.
Bag size distribution
The distribution of bag sizes carried by customers will vary depending on the venue and event. The proportions of customers carrying no bag, small bags, medium bags or large bags can be adjusted using the drop-down menu or the sliders.
Examples of bags of each size are as follows:
- Large bag – sports holdall, duffel bag, cabin size suitcase, small hiking rucksack.
- Medium bag – day-bag size rucksack (15 to 30 litres), small holdall, courier-style cross-body bag or satchel, laptop bag.
- Small bag – handbag, tote bag, small cross-body bag or bumbag, small rucksack (less than 15 litres).
Estimate resources
The Estimate resources button provides a quick calculation of how many of each type of resource (e.g. bag scanner, or search table) are likely to be required to get every customer into the venue. This estimate is intended as a starting point, not a definitive answer, so may need further adjustment.
Adjusting any parameter (e.g. bag size distribution or total customers) will likely impact the resources required, so users should re-estimate as needed.
Calculate
Once the security process and venue characteristics have been configured, the Calculate button runs the simulation. Simulation results are not saved, but can be exported for later viewing using the Export Report button.
After running the simulation, the simulation parameters can be adjusted and the simulation rerun.
Simulations tab
Once the simulation has finished, the simulations tab shows the results.
The simulation results are not automatically saved, but can be exported (see below) for later viewing.
The overall customer experience provides a summary of queuing times for visitors. The results are divided into four categories:
- Quick entry – under 5 minutes.
- Acceptable wait – 5-15 minutes of queuing.
- Long wait – over 15 minutes of queuing.
- Missed start – not in the venue at the end of the designated arrival window.
The graph shows:
- in blue: the length of the queue over time
- in orange: the number of customers in the venue over time.
The Bottleneck Analysis table shows the different parts of the security process (different resources), how heavily these are used (the capacity used), the maximum queue here at any point in the operating hours and the average service time. Potential bottlenecks in the process are highlighted in red (> 95% capacity) or orange (> 85% capacity) where appropriate.
The capacity to aim for will vary depending on the venue and the type of resource. For example, screening staff at 100% capacity will have very little scope for wider situational awareness.
Export report
Once the simulation has completed, the user may want to export the results for later viewing. The Export Report button exports the simulation setup and associated results to a date- and time-stamped report, which is saved to the user’s Downloads folder.