Open Platform Software Library (OPSL)

Open Platform Software Library (OPSL)

Description

OPSL: The Airport Security Platform

The Open Platform Software Library (OPSL) offers a cross-platform software development kit (SDK) that facilitates collaboration between application and algorithm developers, equipment providers, system integrators, and airport operators to elevate airport security and improve the passenger screening experience.

OPSL offers a plug and play, vendor-neutral, standardized platform that opens up access to the airport security market for application developers. The SDK contains implementation examples and testing infrastructure tools that enable the development and seamless integration of third-party algorithms into airport security systems.

Funded and developed by Sandia National Laboratories in conjunction with Stratovan, under contract with the Transportation Security Administration (TSA), the OPSL platform:

  • Enables innovation and collaboration through standardized interfaces
  • Reduces operational costs for TSA and airport operations by better leveraging existing hardware
  • Facilitates the seamless introduction of new, innovative capabilities and best-of-breed components

Developed under the OTAP (Open Threat Assessment Platform) effort, the OPSL SDK can be downloaded by clicking here.

 

Request access to OPSL

 

More Information

Helps TSA and Airport Operators select the most efficient, accurate and interoperable systems so that airports can achieve the highest level of security possible and deliver the quickest and most efficient passenger experience.

Enables Algorithm Developers to Work on a Common Platform to:

  • Create algorithms and instantly become compatible with any equipment vendor
  • Gain access to the airport security market
  • Eliminate the headaches of integration and deployment

Gives Security Vendors the ability to expand their portfolio of customer offerings by incorporating new applications into systems, which prior to OPSL could not be conceived of nor integrated, with the potential for global adoption into new markets.

Gives Passengers the most seamless, most efficient, fastest and safest security processing experience possible, including shorter lines, speedier security checks and reduced manual scans.

The OPSL framework integrates third-party applications such as automated threat recognition algorithms (ATRs), graphical user interfaces, and risk-based security (among other functionalities) on baggage screening devices. The OPSL framework allows for configurable risk-based screening (RBS) workflows based on passenger risk scores to ensure that screening information is routed to the right devices dynamically within a screening lane. OPSL also integrates and leverages the Digital Imaging and Communications in Security (DICOS) standard format for moving image data between screening devices in a standardized way.

OPSL decouples screening capabilities into OPSL Roles (i.e., what Role does each capability play within the screening workflow) and defines interfaces to those capabilities so that heterogenous systems can be constructed. To date, third-party ATRs, on-screen viewers, data archiving, risk-based screening functions, and dynamic workflow capability have all been successfully demonstrated on ATXs and CTs using OPSL. In addition, OPSL demonstrations utilizing third-party ATRs on HD-AIT data and third-party multi-energy detectors designed for ATXs have also been performed.

Integration

This initial OPSL release includes a cross-platform software development kit (SDK) to be integrated with vendor software and ultimately installed onto TSA computers; this will occur both at the checkpoints and within the broader TSA network to facilitate standardized communication and to allow for standardized configuration, command, and control of TSE. This SDK provides access to core screening services and enables the OPSL network for OPSL aware devices. The OPSL Role definitions allow vendors to add capabilities into this ecosystem via a plug-in framework. To make your system OPSL aware, OPSL integration is implemented via one of three different models:

  1. Adapter Model: Recommended for learning, demonstrations, and legacy devices. OPSL software is packaged and installed as a separate executable which can run on the same or different computer from the screening device; is set up with a listening function (e.g. FTP, file share, proprietary transmission, etc.) to access screening files as they are collected. This model is designed to minimize impact and changes to existing system configurations, while compromising some OPSL capability. This may not require re-compiling existing TSE software, but would require creating at least a new software executable that can pull data from the existing system.
  2. Static Model: Recommended for most newer systems. The OPSL SDK is linked into TSE software and fulfills OPSL interfaces; requires a re-compile of vendor TSE software if integrated into existing software. This requires a small amount of software development in order to integrate the OPSL SDK into existing TSE software systems.
  3. Dynamic Model (available in the next OPSL release): Recommended for highly-configurable systems. Dynamically-linked libraries (DLLs) are used to encapsulate capabilities at a low-level within TSE. Individual capabilities are compartmentalized into plugin DLLs, such as source/detector interfaces, TSE control, low-level algorithms, and higher-level algorithms such as ATR. The plugin DLLs are loaded by a plugin manager executable provided within the OPSL SDK and are configured using a configuration file. This mode allows for fine grained decoupling and integration of low-level algorithms “inside the box.”

Related Products

Encircle
--
Maxillo
$9,999 (USD)
Checkpoint
$499 (USD)
Pro Surgical 3D
Free