Simulations in security checkpoints: Three Use Cases

Every security checkpoint is under constant pressure of changing situations. These can be triggered by a change in spacing due to construction plans, as well as policy changes looking at new procedures for screening passengers, or potentially an upgrade in screening technologies. Point FWD sees the security checkpoint as a coherent system of technologies, processes and people in which balance is the key to success at every unique location. Our challenge in this puzzle is to transition from a rather uncertain situation – i.e. getting surprised by external changes that impact checkpoint operations – to a situation where airports, airport operators and suppliers are in good shape for any upcoming change.

In this blog we like to give a short introduction about 3D simulations in security checkpoints by which digital representations of security operations can act as a “Sand-Box” to experiment with planned, or even unplanned changes. We believe that for a majority of changes to the security checkpoint, costly trial projects and time efforts could be reduced by building a digital model of the operational situation, but only when there is a sufficient level of operational detail.

Specifically we take a look at three main application areas in where simulations show great benefits, being:

1. Checkpoint redesign and technology upgrades;

2. Checkpoint resilience testing; and

3. Security process optimisation.

---

1. Checkpoint redesign and technology upgrades

A first area of application in which simulations can provide great benefit - and certainly all aviation professionals are most familiar with – is in design and planning projects. For example terminal expansion programs or security checkpoint redesign projects, which are often combined with technology upgrades such as ATRS, CT scanners or Security Scanners. However, most design simulations delivered for projects like mentioned mainly focus on generic passenger flows, which are modelled based on rather generic dynamics about security checkpoints. This is done by looking at acceptable security input and output values providing a good sense of passenger flows and queue areas.

Point FWD’s view in these projects is that for gaining the most accurate representation of a future checkpoint situation, more detail such as process anomalies, operational variations and airport specifics are required to understand different design scenarios for security checkpoints. Discrete event simulations can provide a visual representation of the detailed process and can provide further insight on how and where passengers precisely accumulate in the process itself and how a design could be altered to potentially resolve this. It also provides a dynamic component to the process by showing how lane and checkpoint throughputs are constantly varying over time and during peak hours. Below a simulation example based on the transition from x-ray to CT scanners and the impact thereof on process performance is included.

Design use case: Moving from standard X-ray to CT scanners. This video shows an example of the level of detail by which CT implementations can be tested, validated and successfully prepared by means of accurate simulations.

---

2. Checkpoint resilience testing

As of recent years, more and more airports adopt digital strategies to manage challenges that relate to operational stability. These include platforms for accurately forecasting actual passenger demand, based on real-time flight schedules and passenger data, increasingly with use of AI engines to detect anomalies. For the purpose of flexibly, both up- and down-scaling resources and assets during operational hours - especially capacity intensive terminal processes such as check-in, baggage reclaim and security - can benefit.

In case of the security checkpoint situation, on a different level than these real-time monitoring and planning systems, resilience levels can be tested, validated and improved greatly by a simulated environment. By doing so, exploring what-if scenarios in terms of common and uncommon events that happen in the checkpoint environment is possible, such as security lane errors or high threat procedures. Virtual representations of security lanes can then help in testing stress levels of checkpoint environments with regards to the number of lanes available for operation at maximum, versus passenger demand and key performance metrics. Eventually, a simulation of potential disruptions help in preparing for future threats to operation, and help to implement robust operational plans.  

Resilience use case: Outage of a security lane during peak times. This video exemplifies an operational situation that focuses on testing and validating operational plans for checkpoint situations, really looking at the impact on capacity and passenger flow.

---

3. Security process optimisation

Ideally, security checkpoints should accommodate for an environment to securely and swiftly process significant numbers of actual passengers. Often, the operation is not running  optimally and it is key to determine what is causing problems in the checkpoint so that these problems can be understood and solved.

Optimisation issues that can be assessed and fixed with simulations include, among other things, large queues with high queue times, low throughput, or the occurrence of bottlenecks. To recreate this operational situation in a digital twin environment, it is essential to have accurate and reliable input. This specific process data, such as processing times, reject rates and X-ray analysis times, are obtained both by extracting machine data, as well as manually collected measurements. Using this as input for the simulation, the process can be imitated and issues like mentioned can be tracked down. In doing so, experiments can be run which are testing different solution possibilities, such as changes in CONOPS or resources, delivering a better understanding of how this would effect, and potentially optimize the process, before ultimately implementing these changes in real-life operation.

Optimisation use case. In this video an example focused on the impact of the tray per passenger rate is simulated. It may help to simulate the operational impact of policy adjustments and CONOP changes in optimisation projects.

---

The importance of accurate input parameters

Simulation can be an excellent tool to create a virtual model of a security checkpoint. This environment can be manipulated and changed to either visualize the impact of certain changes or to see where bottlenecks are likely to occur. However, to create a digital twin of a specific security checkpoint, it is essential that the input parameters of the checkpoint represent the actuals. If the input is not correct, the output including the solutions to the initial issue, may not have the desired effect.

Point FWD’s Checkpoint Insight Tool

Data that is often required for complete simulations include screening system outputs, arrival patterns of passenger flows, but also more specific passenger data that often differentiates across airports. The latter is much often hard to capture with machine efforts, and therefore needs manual capturing. Point FWD’s Checkpoint Insight Tool is a tooling platform to help airport operators and OEMs to do just that.

---

Checkpoint Simulations by Point FWD

Has this blog made you curious or are you already contemplating about running a simulation for your business? At Point FWD, we are happy to help and answer in case specific questions about simulations in security checkpoints arise. We are open for demo requests and like to think with you in the solutions that can be brought with our security checkpoint simulation capability.

Process implementation of APIDs into security checkpoints.

While most airports are currently on the verge of transitioning towards modern screening equipment such as Explosives Detection Systems for Cabin Baggage (EDS CB), Automated lanes and Security Scanners; Airport Managers will soon be presented with value adding components to further streamline security operations. As touched upon in previous blogs, APIDS acts as an important solution to orchestrate the security operation in terms of human resources, operating costs and eventually to influence waiting times for security in a positive manner. In fact, implementation of APIDS might even brighten up the business case for moving towards EDS CB equipped security operations in parallel.

As operational APIDS trials are currently being prepared and performed, legislative outlines start to become visible to the industry and the first ECAC approval standards are expected early 2023, APIDS now take place on the near-term roadmap for implementation. But how do you start planning for APIDS implementation? Point FWD assists airports and security companies in security change projects and in this blog share their thoughts on the most important steps to take for APIDS consideration.

1.       Understand the impact and formulate a strategy

When looking at APIDS – and any other type of technology change in the checkpoint environment basically – it is of utmost and primary importance to fully understand every characteristic and capability of the technology, most importantly to assess the impact on current security operations. For APIDS specifically, it is expected that full system capability in combination with EDS CB screening could go in direction of HBS-like automation levels. In that perspective, changing towards EDS systems for the checkpoint become even more beneficial for the airport, and studying what solution (C-1, C-2 or C-3) best fits the airport requirements is then essential. For those involved in security change projects, it goes without saying; checkpoint (re)design requires a great amount of efforts to achieve a balanced and successful new process.

The success of APIDS implementation goes hand in hand with the introduction of Open Architecture of systems in Aviation Security screening setups. APIDS solutions will also be developed by highly competent companies other than screening equipment OEMs and for this reason flexibility and interoperability between systems is key to enable new-entrant companies develop smart solutions that interoperate within the security landscape. Hence, when tendering for solutions as such, it is very important to look at it from the broader checkpoint operation with regards to data exchange, interoperability, CONOPs, checkpoint layouts and other operational implications.

2.       Create functional and operational designs of the new checkpoint process

A holistic view is key when upgrading or re-designing the security checkpoint with any technology or security measure. It is certainly not a matter of replacing a machine or adding an algorithm. Moreover, it is about rebalancing all processes to accommodate for the technology implementation(s) as initiated, and obviously this is no different for APIDS implementation. The expectation (and promise) of APIDS is that less screeners per lane are required to screen the same number of images, but with the requirement that centralized image analysis – or networked screening – is in place to be able to gain the potential.

The optimal security lane and checkpoint design is unique for every airport and can even vary across the airport for the different checkpoints. For this reason, using process characteristics from the local situation is essential when developing for a future lane concept. Together with assumptions for future operation of APIDS systems and CONOPs, functional lane designs can be modelled and simulated to assess the impact on output figures such as passenger and tray throughput, (decreased) staffing of personnel and expected workloads. Doing so, various functional design scenarios can act as input for operational business case assessments, resulting in confidence and accuracy in strategic decision-making.

3.       Validate APIDS setups and start optimization

Trialing a new combination of systems and CONOPs in a real airport environment will always be the best step towards solution validation. That is, we can model and calculate the best we can, however, the true value (and pitfalls) of APIDS systems should be concluded in a real-life operational environment with all uncertainties present. It should always be the step in between initial design and final roll-out of a solution. Furthermore, in the trial setup, end-users are confronted with APIDS and will get trained or become known how to adapt to the new way of working. The insights that were gained during an APIDS trial should of course serve as input for simulations of final checkpoint design, lane concept development or even tender specification.

One of the main focus points to trial APIDS solutions in the AvSec checkpoints is to closely monitor every part of the coherent security process. Data capture and analysis helps to critically assess whether, where in the process and to what extend changes have occurred. Monitoring of APIDS technology trials can best be done using omni-source data collection – including machine, manual or sensor data. The reason for doing this is to be able to tackle any differentiation in process performance that might be present, including bottleneck shifting, decreased alarm resolution times or increased IPP due to seasonal change.            

4.       Start implementation and continuous monitoring of APIDS solutions.

The start of deployment of APIDS systems should be seen as the start of various other projects. Fully dependent on the CONOPs in which APIDS will be implemented, it is expected that new waves of technology will get certified and that other process CONOPs become available to the early airports adopting the primary APIDS technology. Therefore, continuous monitoring the operation remains key to be able to optimize for the most beneficial process including staffing and work instructions.

Furthermore, benefits of algorithm-based systems such as APIDS are expected to continue to grow, even outside of the checkpoint space and across airports. Via the Open Architecture of systems, airports with algorithms deployed should be able to work together by autonomously adapting to emerging threats, and mitigating security risks even further in the future.

---

Point FWD owns a core capability in planning for security checkpoint change related to technology upgrades, process improvements and terminal redesign or expansion projects. Point FWD assists with expert operational knowledge, fully supported with a comprehensive security process analysis and design platform. Contact the team for more info.